3GPP 24.501 v20.0.0 — the document's own text
9.11.3.39 Payload container
Taught in 4. Inside TS 24.501, the document at the centre (CT1 — the group that writes what your phone says, overview).
The purpose of the Payload container information element is to transport one or multiple payloads. If multiple payloads are transported, the associated information of each payload are also transported together with the payload.
The Payload container information element is coded as shown in figure 9.11.3.39.1, figure 9.11.3.39.1A, figure 9.11.3.39.1B, figure 9.11.3.39.2, figure 9.11.3.39.3, figure 9.11.3.39.4 and table 9.11.3.39.1.
The Payload container information element is a type 6 information element with a minimum length of 4 octets and a maximum length of 65538 octets.
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| Payload container IEI | octet 1 | |||||||
| Length of payload container contents | octet 2 | |||||||
| octet 3 | ||||||||
| octet 4 | ||||||||
| Payload container contents | ||||||||
| octet n |
Figure 9.11.3.39.1: Payload container information element
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| Number of event notification indicators | octet 4 | |||||||
| Event notification indicator 1 | octet 5octet j | |||||||
| Event notification indicator 2 | octet j+1*octet k* | |||||||
| … | octet k+1*…octet l* | |||||||
| Event notification indicator n | octet l+1*octet m* |
Figure 9.11.3.39.1A: Payload container contents with Payload container type "Event notification"
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| Type of event notification indicator n | octet l+1 | |||||||
| Length of event notification indicator n | octet l+2 | |||||||
| Value of event notification indicator n | octet l+3*octet m* |
Figure 9.11.3.39.1B: Even notification indicator n
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| Number of entries | octet 4 | |||||||
| Payload container entry 1 | octet 5octet x2 | |||||||
| Payload container entry 2 | octet x2+1octet x3 | |||||||
| …… | … | |||||||
| Payload container entry i | octet xi +1octet n |
Figure 9.11.3.39.2: Payload container contents with Payload container type "Multiple payloads"
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| Length of Payload container entry | octet xi +1octet xi +2 | |||||||
| Number of optional IEs | Payload container type | octet xi +3 | ||||||
| Optional IE 1 | octet xi +4octet y2 | |||||||
| Optional IE 2 | octet y2+1octet y3 | |||||||
| … | ||||||||
| Optional IE j | octet yj+1octet z | |||||||
| Payload container entry contents | octet z+1octet n |
Figure 9.11.3.39.3: Payload container entry
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| Type of optional IE | octet xi +4 | |||||||
| Length of optional IE | octet xi +5 | |||||||
| Value of optional IE | octet xi +6octet y2 |
Figure 9.11.3.39.4: Optional IE
Table 9.11.3.39.1: Payload container information element
| Payload container contents (octet 4 to octet n); max value of 65535 octets | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| If the payload container type is set to "N1 SM information" and is included in the UL NAS TRANSPORT or DL NAS TRANSPORT message, the payload container contents contain a 5GSM message as defined in clause 8.3.If the payload container type is set to "SOR transparent container" and is included in the DL NAS TRANSPORT message, the payload container contents are coded the same way as the contents of the SOR transparent container IE (see clause 9.11.3.51) for SOR data type is set to value "0" except that the first three octets are not included.If the payload container type is set to "SOR transparent container" and is included in the UL NAS TRANSPORT message, the payload container contents are coded the same way as the contents of the SOR transparent container IE (see clause 9.11.3.51) for SOR data type is set to value "1" except that the first three octets are not included.If the payload container type is set to "UE policy container" and is included in the DL NAS TRANSPORT, UL NAS TRANSPORT or REGISTRATION REQUEST message, the payload container contents are coded as defined in Annex D.If the payload container type is set to "UE parameters update transparent container" and is included in the DL NAS TRANSPORT message, the payload container contents are coded the same way as the contents of the UE parameters update transparent container IE (see clause 9.11.3.53A) for UE parameters update data type is set to value "0" except that the first three octets are not included.If the payload container type is set to "UE parameters update transparent container" and is included in the UL NAS TRANSPORT message, the payload container contents are coded the same way as the contents of the UE parameters update transparent container IE (see clause 9.11.3.53A) for UE parameters update data type is set to value "1" except that the first three octets are not included.If the payload container type is set to "SMS" and is included in the UL NAS TRANSPORT or DL NAS TRANSPORT message, the payload container contents contain an SMS message (i.e. CP-DATA, CP-ACK or CP-ERROR) as defined in clause 7.2 in 3GPP TS 24.011 [13].If the payload container type is set to "CIoT user data container" and is included in the UL NAS TRANSPORT, DL NAS TRANSPORT or CONTROL PLANE SERVICE REQUEST message, the payload container contents are coded the same way as the contents of the user data container IE (see clause 9.9.4.24 in 3GPP TS 24.301 [15]) except that the first three octets are not included.If the payload container type is set to "SMS" and is included in the CONTROL PLANE SERVICE REQUEST message, the payload container contents are coded the same way as the contents of the NAS message container IE (see clause 9.9.3.22 in 3GPP TS 24.301 [15]) except that the first two octets are not included.If the payload container type is set to "Location services message container" and is included in the UL NAS TRANSPORT, DL NAS TRANSPORT or CONTROL PLANE SERVICE REQUEST message, the payload container contents include location services message payload.If the payload container type is set to "LTE Positioning Protocol (LPP) message container" and is included in the UL NAS TRANSPORT or DL NAS TRANSPORT message, the payload container contents include LPP message payload.If the payload container type is set to "SLPP message container" and is included in the UL NAS TRANSPORT or DL NAS TRANSPORT message, the payload container contents include SLPP message payload.If the payload container type is set to "Service-level-AA container" and is included in the UL NAS TRANSPORT or DL NAS TRANSPORT message, the payload container contents are coded the same way as the contents of service-level-AA container (see clause 9.11.2.10).If the payload container type is set to "Event notification", the payload container contents include one or more event notification indicators. | |||||||||
| Type of event notification indicator n (octet l+1)Bits | |||||||||
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | ||
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | "SRVCC handover cancelled, IMS session re-establishment required" indicator | |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | ||
| to | Unused, shall be ignored if received by the UE | ||||||||
| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||
| If the type of an event notification indicator is set to "SRVCC handover cancelled, IMS session re-establishment required" indicator, the value of the event notification indicator shall not be included. | |||||||||
| If the payload container type is set to "UPP-CMI container" and is included in the UL NAS TRANSPORT or DL NAS TRANSPORT message, the payload container contents include UPP-CMI messages as specified in 3GPP TS 24.572 [64]. | |||||||||
| If the payload container type is set to "Multiple payloads", the number of entries field represents the total number of payload container entries, and the payload container entry contents field is coded as a list of payload container entry according to figure 9.11.3.39.2, with each payload container entry is coded according to figure 9.11.3.39.3 and figure 9.11.3.39.4. | |||||||||
| The coding of Payload container contents is dependent on the particular application. | |||||||||
| Payload container entryFor each payload container entry, the payload container type field represents the payload container type value as described in clause 9.11.3.40, the coding of payload container contents field is dependent on the particular application, and the number of optional IEs field represents the total number of optional IEs associated with the payload container entry contents field in the payload container entry. The error handlings for optional IEs specified in clauses 7.6.3 and 7.7.1 shall apply to the optional IEs included in the payload container entry.The receiving entity shall ignore Optional IEs with type of optinal IE parameter field containing an unknown IEI. | |||||||||
| Optional IEsType of optional IE (octet xi +4)This field contains the IEI of the optional IE.Length of optional IE (octet xi+5)This field indicates binary coded length of the value of the optional IE entry.Value of optional IE (octet xi+6 to octet y2)This field contains the value of the optional IE entry with the value part of the referred information element based on following optional IE reference. If the Request type is included, the value part of the Request type shall be encoded in the bits 1 to 4 and bits 5 to 8 shall be coded as zero. If the Release assistance indication is included, the value part of the Release assistance indication shall be encoded in the bits 1 to 4 and bits 5 to 8 shall be coded as zero. If the MA PDU session information is included, the value part of the MA PDU session information shall be encoded in the bits 1 to 4 and bits 5 to 8 shall be coded as zero. | |||||||||
| IEI | Optional IE name | Optional IE reference | |||||||
| 12 | PDU session ID | PDU session identity 2 (see clause 9.11.3.41) | |||||||
| 24 | Additional information | Additional information (see clause 9.11.2.1) | |||||||
| 58 | 5GMM cause | 5GMM cause (see clause 9.11.3.2) | |||||||
| 37 | Back-off timer value | GPRS timer 3 (see clause 9.11.2.5) | |||||||
| 59 | Old PDU session ID | PDU session identity 2 (see clause 9.11.3.41) | |||||||
| 80 | Request type | Request type (see clause 9.11.3.47) | |||||||
| 22 | S-NSSAI | S-NSSAI (see clause 9.11.2.8) | |||||||
| 25 | DNN | DNN (see clause 9.11.2.1B) | |||||||
| F0 | Release assistance indication | Release assistance indication (see clause 9.11.3.46A) | |||||||
| A0 | MA PDU session information | MA PDU session information (see clause 9.11.3.31A) |