Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 24.501  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   3…   4…   4.4…   4.4.3…   4.5…   4.5.3…   4.6…   4.7…   4.9…   4.15…   5…   5.2…   5.3…   5.3.2…   5.3.7…   5.3.19…   5.4…   5.4.1.3…   5.4.2…   5.4.4…   5.4.5…   5.4.6…   5.5…   5.5.1.2.4   5.5.1.2.5…   5.5.1.3…   5.5.1.3.4   5.5.1.3.5…   5.5.2…   5.6…   5.6.2…   6…   6.1.4…   6.2…   6.3…   6.3.2…   6.3.3…   6.4…   6.4.1.4…   6.4.2…   6.5…   7…   8…   8.2.9…   8.3…   9…   9.11.2…   9.11.2.10…   9.11.3…   9.11.3.4…   9.11.3.8…   9.11.3.14…   9.11.3.18C…   9.11.3.29…   9.11.3.33…   9.11.3.39…   9.11.3.45…   9.11.3.50…   9.11.3.53A…   9.11.3.68…   9.11.3.75…   9.11.4…   9.11.4.10…   9.11.4.13…   9.11.4.16…   9.11.4.30…   9.12   10…   A…   B…   C…   D…   D.6…   D.6.3…

 

9.11.3.39  Payload containerWord‑p. 724

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.2, Figure 9.11.3.39.3, Figure 9.11.3.39.4 and Table 9.11.3.39.1.
The Payload container is a type 6 information element with a minimum length of 4 octets and a maximum length of 65538 octets.
Reproduction of 3GPP TS 24.501, Figure 9.11.3.39.1: Payload container information element
Up
Reproduction of 3GPP TS 24.501, Figure 9.11.3.39.2: Payload container contents with Payload container type
Up
Reproduction of 3GPP TS 24.501, Figure 9.11.3.39.3: Payload container entry
Up
Reproduction of 3GPP TS 24.501, Figure 9.11.3.39.4: Optional IE
Up
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 subclause 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 subclause 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 subclause 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 subclause 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 subclause 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 subclause 7.2 in TS 24.011.
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 subclause 9.9.4.24 in TS 24.301) 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 subclause 9.9.3.22 in TS 24.301) 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 "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 subclause 9.11.2.10).
The coding of Payload container contents is dependent on the particular application.
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.
Payload container entry
For each payload container entry, the payload container type field represents the payload container type value as described in subclause 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 subclauses 7.6.1, 7.6.3 and 7.7.1 shall apply to the optional IEs included in the payload container entry.
Optional IEs
Type 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.
IEIOptional IE nameOptional IE reference
12PDU session IDPDU session identity 2 (see subclause 9.11.3.41)
24Additional informationAdditional information (see subclause 9.11.2.1)
585GMM cause5GMM cause (see subclause 9.11.3.2)
37Back-off timer valueGPRS timer 3 (see subclause 9.11.2.5)
59Old PDU session IDPDU session identity 2 (see subclause 9.11.3.41)
80Request typeRequest type (see subclause 9.11.3.47)
22S-NSSAIS-NSSAI (see subclause 9.11.2.8)
25DNNDNN (see subclause 9.11.2.1B)
F0Release assistance indicationRelease assistance indication (see subclause 9.11.3.46A)
A0MA PDU session informationMA PDU session information (see subclause 9.11.3.31A)
Up

9.11.3.40  Payload container typeWord‑p. 729

The purpose of the Payload container type information element indicates type of payload included in the payload container information element.
The Payload container type information element is coded as shown in Figure 9.11.3.40.1 and Table 9.11.3.40.1.
The Payload container type is a type 1 information element.
Reproduction of 3GPP TS 24.501, Figure 9.11.3.40.1: Payload container type information element
Up
Payload container type value (octet 1)
Bits
4 3 2 1
0 0 0 1N1 SM information
0 0 1 0SMS
0 0 1 1LTE Positioning Protocol (LPP) message container
0 1 0 0SOR transparent container
0 1 0 1UE policy container
0 1 1 0UE parameters update transparent container
0 1 1 1Location services message container (see TS 23.273)
1 0 0 0CIoT user data container
1 0 0 1Service-level-AA container
1 1 1 1Multiple payloads
All other values are reserved.
NOTE:
The value "Multiple payloads" is only used when the Payload container contents in Figure 9.11.3.39.1 contains multiple payloads as shown in Figure 9.11.3.39.2.
Up

9.11.3.41  PDU session identity 2Word‑p. 730

The purpose of the PDU session identity 2 information element is to indicate the identity of a PDU session in a 5GMM message.
The PDU session identity 2 information element is coded as shown in Figure 9.11.3.41.1 and Table 9.11.3.41.1.
The PDU session identity 2 is a type 3 information element with a length of 2 octets .
Reproduction of 3GPP TS 24.501, Figure 9.11.3.41.1: PDU session identity 2 information element
Up
PDU session identity 2 value (octet 2)
The coding of the DU session identity 2 value is identical to the coding of the PDU session identity value as defined in TS 24.007.
Up

9.11.3.42  PDU session reactivation resultWord‑p. 730

The purpose of the PDU session reactivation result information element is to indicate the result of establishments of user-plane resources of PDU sessions.
The PDU session reactivation result information element is coded as shown in Figure 9.11.3.42.1 and Table 9.11.3.42.1.
The PDU session reactivation result is a type 4 information element with minimum length of 4 octets and maximum length of 34 octets.
Reproduction of 3GPP TS 24.501, Figure 9.11.3.42.1: PDU session reactivation result information element
Up
PSI(x) shall be coded as follows:
PSI(0):
Bit 0 of octet 3 is spare and shall be coded as zero.
PSI(1) - PSI(15):
0indicates establishment of user-plane resources of the PDU session was not requested in the Uplink data status IE or establishment of user-plane resources of the PDU session was not allowed in the Allowed PDU session status IE or establishment of user-plane resource of the PDU session is successful.
1indicates either establishment of user-plane resources of the PDU session was requested in the Uplink data status IE but establishment of user-plane resource of the PDU session is not successful or indicates establishment of user-plane resources of the PDU session was allowed in the Allowed PDU session status IE but establishment of user-plane resource of the PDU session is either not performed or not successful.
All bits in octet 5 to 34 are spare and shall be coded as zero, if the respective octet is included in the information element.
Up

9.11.3.43  PDU session reactivation result error causeWord‑p. 731

The purpose of the PDU session reactivation result error cause information element is to indicate error causes for PDU session ID(s) where there was a failure to establish the user-plane resources.
The PDU session reactivation result error cause information element is coded as shown in Figure 9.11.3.43.1 and Table 9.11.3.43.1.
The PDU session reactivation result error cause is a type 6 information element with a minimum length of 5 octets and a maximum length of 515 octets.
Reproduction of 3GPP TS 24.501, Figure 9.11.3.43.1: PDU session reactivation result error cause information element
Up
PDU session ID is coded same as PDU session ID IE (see subclause 9.4).
The cause value is coded same as second octet of 5GMM cause information element (see subclause 9.11.3.2).
Up

9.11.3.44  PDU session statusWord‑p. 731

The purpose of the PDU session status information element is to indicate the state of each PDU session that can be identified by a PDU session identity.
The PDU session status information element is coded as shown in Figure 9.11.3.44.1 and Table 9.11.3.44.1.
The PDU session status information element is a type 4 information element with minimum length of 4 octets and a maximum length of 34 octets.
Reproduction of 3GPP TS 24.501, Figure 9.11.3.44.1: PDU session status information element
Up
PSI(x) shall be coded as follows:
PSI(0):
Bit 1 of octet 3 is spare and shall be coded as zero.
PSI(1) - PSI(15):
0indicates that the 5GSM state of the corresponding PDU session is PDU SESSION INACTIVE.
1indicates that the 5GSM state of the corresponding PDU session is not PDU SESSION INACTIVE
All bits in octet 5 to 34 are spare and shall be coded as zero, if the respective octet is included in the information element.
Up

Up   Top   ToC