Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 24.501  Word version:  18.0.1

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.4.16  SSC modep. 868

The purpose of the SSC mode information element is to indicate SSC mode.
The SSC mode information element is coded as shown in Figure 9.11.4.16.1 and Table 9.11.4.16.1.
The SSC mode is a type 1 information element.
Reproduction of 3GPP TS 24.501, Fig. 9.11.4.16.1: SSC mode information element
Up
SSC mode value (octet 1, bit 1 to bit 4)
Bits
3 2 1
0 0 1SSC mode 1
0 1 0SSC mode 2
0 1 1SSC mode 3
1 0 0unused; shall be interpreted as "SSC mode 1", if received by the network
1 0 1unused; shall be interpreted as "SSC mode 2", if received by the network
1 1 0unused; shall be interpreted as "SSC mode 3", if received by the network
All other values are reserved.
Up

9.11.4.17  Re-attempt indicator |R16|p. 868

The purpose of the Re-attempt indicator information element is to indicate a condition under which the UE is allowed in the current PLMN or its equivalent PLMN(s) for the same DNN, to re-attempt a session management procedure (see TS 24.301) corresponding to the 5GS session management procedure which was rejected by the network.
The Re-attempt indicator information element is coded as shown in Figure 9.11.4.17.1 and Table 9.11.4.17.1.
The Re-attempt indicator is a type 4 information element with a length of 3 octets.
Reproduction of 3GPP TS 24.501, Fig. 9.11.4.17.1: Re-attempt indicator
Up
RATC (octet 3, bit 1)
0UE is allowed to re-attempt the procedure in S1 mode
1UE is not allowed to re-attempt the procedure in S1 mode
EPLMNC (octet 3, bit 2)
0UE is allowed to re-attempt the procedure in an equivalent PLMN
1UE is not allowed to re-attempt the procedure in an equivalent PLMN
Bits 3 to 8 of octet 3 are spare and shall be encoded as zero.
Up

9.11.4.18  5GSM network feature support |R16|p. 869

The purpose of the 5GSM network feature support information element is to indicate whether certain session management related features are supported by the network.
The 5GSM network feature support information element is coded as shown in Figure 9.11.4.18.1 and Table 9.11.4.18.1.
The 5GSM network feature support is a type 4 information element with a minimum length of 3 octets and a maximum length of 15 octets.
Reproduction of 3GPP TS 24.501, Fig. 9.11.4.18.1: 5GSM network feature support information element
Up
5GSM network feature support contents
Ethernet PDN type in S1 mode (IEPT-S1) (octet 3, bit 1)
This bit indicates network's capability for Ethernet PDN type in S1 mode.
0Ethernet PDN type in S1 mode not supported
1Ethernet PDN type in S1 mode supported
All other bits in octet 3 to 15 are spare and shall be coded as zero, if the respective octet is included in the information element.
Up

9.11.4.19Void

9.11.4.20  Serving PLMN rate control |R16|p. 869

9.11.4.21  5GSM congestion re-attempt indicator |R16|p. 869

The purpose of the 5GSM congestion re-attempt indicator information element is to indicate whether the back-off timer is applied in the registered PLMN or all PLMNs, and additionally to indicate whether the back-off timer is applied in the current access type or both 3GPP access type and non-3GPP access type.
The 5GSM congestion re-attempt indicator information element is coded as shown in Figure 9.11.4.21.1 and Table 9.11.4.21.1.
The 5GSM congestion re-attempt indicator is a type 4 information element with a length of 3 octets.
Reproduction of 3GPP TS 24.501, Fig. 9.11.4.21.1: 5GSM congestion re-attempt indicator
Up
ABO (All PLMNs Back-off timer) (octet 3, bit 1)
0The back-off timer is applied in the registered PLMN.
1The back-off timer is applied in all PLMNs.
CATBO (Current Access Type Back-off Timer) (octet 3, bit 2)
0The back-off timer is applied in both 3GPP access type and non-3GPP access type
1The back-off timer is applied in the current access type.
Bits 3 to 8 of octet 3 are spare and shall be encoded as zero.
Up

9.11.4.22  ATSSS container |R16|p. 870

The purpose of the ATSSS container information element is to transfer parameters associated with ATSSS.
The ATSSS container information element is coded as shown in Figure 9.11.4.22.1 and Table 9.11.4.22.1.
The ATSSS container is a type 6 information element with a minimum length of 3 octets and a maximum length of 65538 octets.
Reproduction of 3GPP TS 24.501, Fig. 9.11.4.22.1: ATSSS container information element
Up
ATSSS container contents are defined in TS 24.193.

9.11.4.23  Control plane only indication |R16|p. 870

The purpose of the control plane only indication information element is to indicate that a PDU session is only for control plane CIoT 5GS optimization.
The control plane only indication information element is coded as shown in Figure 9.11.4.23.1.
The control plane only indication is a type 1 information element.
Reproduction of 3GPP TS 24.501, Fig. 9.11.4.23.1: Control plane only indication information element
Up
Control plane only indication value (CPOI) (octet 1)
Bit
1
0reserved
1PDU session can be used for control plane CIoT 5GS optimization only
The value 0 is reserved. If received, it shall be interpreted as if the control plane only indication IE was not included in the message.
Bits 4 to 2 of octet 1 are spare and shall be all encoded as zero.
Up

9.11.4.24  IP header compression configuration |R16|p. 871

The purpose of the IP header compression configuration information element is to negotiate ROHC channel setup parameters specified in RFC 5795 and, optionally, provide additional header compression context setup parameters.
The IP header compression configuration information element is coded as shown in Figure 9.11.4.24.1 and Table 9.11.4.24.1.
The IP header compression configuration is a type 4 information element with a minimum length of 5 octets and a maximum length of 257 octets.
The optional Additional IP header compression parameters container field conveys the additional header compression context setup parameters as specified in TS 23.501 in a generic container. This field corresponds to the profile-specific information in the header of the ROHC IR packet type in RFC 5795.
Reproduction of 3GPP TS 24.501, Fig. 9.11.4.24.1: IP header compression configuration information element
Up
ROHC Profiles (octet 3)
The ROHC Profiles shall indicate which of the ROHC profiles is supported. When a particular bit is set to 1, this indicates that the corresponding profile is supported. The No Compression profile 0x0000 (see RFC 5795) shall always be supported. When all the bits are set to 0, this indicates that only the No Compression profile 0x0000 is supported.
Profile 0x0002 support indicator (see RFC 3095 and RFC 4815) (octet 3 bit 1)
0RoHC profile 0x0002 (UDP/IP) is not supported
1RoHC profile 0x0002 (UDP/IP) is supported
Profile 0x0003 support indicator (see RFC 3095 and RFC 4815) (octet 3 bit 2)
0RoHC profile 0x0003 (ESP/IP) is not supported
1RoHC profile 0x0003 (ESP/IP) is supported
Profile 0x0004 support indicator (see RFC 3843 and RFC 4815) (octet 3 bit 3)
0RoHC profile 0x0004 (IP) is not supported
1RoHC profile 0x0004 (IP) is supported
Profile 0x0006 support indicator (see RFC 6846) (octet 3 bit 4)
0RoHC profile 0x0006 (TCP/IP) is not supported
1RoHC profile 0x0006 (TCP/IP) is supported
Profile 0x0102 support indicator (see RFC 5225) (octet 3 bit 5)
0RoHC profile 0x0102 (UDP/IP) is not supported
1RoHC profile 0x0102 (UDP/IP) is supported
Profile 0x0103 support indicator (see RFC 5225) (octet 3 bit 6)
0RoHC profile 0x0103 (ESP/IP) is not supported
1RoHC profile 0x0103 (ESP/IP) is supported
Profile 0x0104 support indicator (see RFC 5225) (octet 3 bit 7)
0RoHC profile 0x0104 (IP) is not supported
1RoHC profile 0x0104 (IP) is supported
Bit 8 is spare and shall be set to 0.
MAX_CID (octet 4 and octet 5)
This is the MAX_CID value as specified in TS 36.323. It is encoded in binary coding with a value in the range from 1 to 16383.
Additional IP header compression context parameters type (octet 6).
The Additional IP header compression context parameters type octet indicates the profile associated with the profile-specific information in the Additional IP header compression context parameters container.
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 00x0000 (No Compression)
0 0 0 0 0 0 0 10x0002 (UDP/IP)
0 0 0 0 0 0 1 00x0003 (ESP/IP)
0 0 0 0 0 0 1 10x0004 (IP)
0 0 0 0 0 1 0 00x0006 (TCP/IP)
0 0 0 0 0 1 0 10x0102 (UDP/IP)
0 0 0 0 0 1 1 00x0103 (ESP/IP)
0 0 0 0 0 1 1 10x0104 (IP)
0 0 0 0 1 0 0 0Other
0 0 0 0 1 0 0 1
toSpare
1 1 1 1 1 1 1 1
Additional IP header compression context parameters container (octets 7 to n).
Additional IP header compression context parameters container carries the profile-specific information (see RFC 5795). The maximum size is 251 octets.
NOTE:
If the Additional IP header compression context setup parameters container is included, then the Additional IP header compression context parameters type shall be included in the octet 6.
Up

9.11.4.25  DS-TT Ethernet port MAC address |R16|p. 874

The purpose of the DS-TT Ethernet port MAC address information element is to signal the MAC address of the DS-TT Ethernet port used for a PDU session of "Ethernet" PDU session type.
The DS-TT Ethernet port MAC address information element is coded as shown in Figure 9.11.4.25.1 and Table 9.11.4.25.1.
The DS-TT Ethernet port MAC address is a type 4 information element with a length of 8 octets.
Reproduction of 3GPP TS 24.501, Fig. 9.11.4.25.1: DS-TT Ethernet port MAC address information element
Up
DS-TT Ethernet port MAC address contents (octets 3 to 8)
The DS-TT Ethernet port MAC address contents consist of the binary representation of the MAC address of the DS-TT Ethernet port used for the PDU session, starting with the LSB bit of the first octet of the MAC address included in bit 1 of octet 3.
Up

9.11.4.26  UE-DS-TT residence time |R16|p. 874

The purpose of the UE-DS-TT residence time information element is to signal the time taken within the UE and DS-TT to forward a packet between the UE and the DS-TT port.
The UE- DS-TT residence time information element is coded as shown in Figure 9.11.4.26.1 and Table 9.11.4.26.1.
The UE-DS-TT residence time is a type 4 information element with a length of 10 octets.
Reproduction of 3GPP TS 24.501, Fig. 9.11.4.26.1: UE-DS-TT residence time information element
Up
UE-DS-TT residence time contents (octets 3 to 10)
The UE-DS-TT residence time contents contain the UE-DS-TT residence time encoded as specified for the correctionField in IEEE Std 1588-2019 [43B], with the LSB bit of the first octet of the UE-DS-TT residence time included in bit 1 of octet 3. If the UE-DS-TT residence time.is too big to be represented, all bits of octets 3 to 10 shall be coded as "1" except the MSB bit of octet 10.
Up

9.11.4.27  Port management information container |R16|p. 875

The purpose of the Port management information container information element is to transport a port management service message as specified in clause 8 of TS 24.539.
The Port management information container information element is coded as shown in Figure 9.11.4.27.1 and Table 9.11.4.27.1.
The Port management information 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, Fig. 9.11.4.27.1: Port management information container information element
Up
Port management information container (octet 4 to n)
A port management service message as specified in clause 8 of TS 24.539.
Up

9.11.4.28  Ethernet header compression configuration |R16|p. 875

The purpose of the Ethernet header compression configuration information element is to negotiate the use of EHC and the length of the CID field in the EHC packet (see TS 38.323).
The Ethernet header compression configuration information element is coded as shown in Figure 9.11.4.28.1 and Table 9.11.4.28.1.
The Ethernet header compression configuration is a type 4 information element with the length of 3 octets.
Reproduction of 3GPP TS 24.501, Fig. 9.11.4.28.1: Ethernet header compression configuration information element
Up
Length of CID field value (CID Length) (octet 3 bits 1 and 2)
Bits
2 1
0 0Ethernet header compression not used
0 17 bits
1 015 bits
All other values shall be interpreted as "7 bits".
Bits 3 to 8 of octet 3 are spare and shall be coded as zero.
Up

9.11.4.29  Remote UE context list |R17|p. 876

The purpose of the Remote UE context list information element is to provide identity and optionally IP address of a 5G ProSe remote UE connected to, or disconnected from, a UE acting as a 5G ProSe layer-3 UE-to-network relay.
The Remote UE context list information element is coded as shown in Figure 9.11.4.29.1, Figure 9.11.4.29.2, Table 9.11.4.29.1 and Table 9.11.4.29.2.
The Remote UE context list is a type 6 information element with a minimum length of 16 octets and a maximum length of 65538 octets.
Reproduction of 3GPP TS 24.501, Fig. 9.11.4.29.1: Remote UE context list
Up
Remote UE context (octet 5 etc)
The contents of remote UE context are applicable for one individual UE and are coded as shown in Figure 9.11.4.29.2 and Table 9.11.4.29.2.
Reproduction of 3GPP TS 24.501, Fig. 9.11.4.29.2: Remote UE context
Up
Remote UE ID type (bits 1 to 3 of octet 6)
Bits
3 2 1
0 0 0PRUK ID
0 1 05GPRUK ID
All other values are reserved.
Remote UE ID format (bit 4 of octet 6) (NOTE)
Bit
4
0Network access identifier (NAI)
164-bit string
Bits 5 to 8 of octet 6 are spare and shall be coded as zero.
Remote UE ID (octet 8 to octet j)
The PRUK ID or the 5GPRUK ID of the 5G ProSe Remote UE.
Protocol used by remote UE (octet j+1, bits 1 to 3)
Bits
3 2 1
0 0 0No IP info
0 0 1IPv4
0 1 0IPv6
1 0 0Unstructured
1 0 1Ethernet
All other values are reserved.
TCP port range for IPv4 indicator (TPRI4I) (octet j+1, bits 4)
Bit
4
0TCP port range for IPv4 absent
1TCP port range for IPv4 present
UDP port range for IPv4 indicator (UPRI4I) (octet j+1, bits 5)
Bit
5
0UDP port range for IPv4 absent
1UDP port range for IPv4 present
Bits 6 to 8 of octet j+1 are spare and shall be coded as zero.
If the Protocol used by remote UE indicates IPv4 and:
  • TPRI4I bit indicates "TCP port range for IPv4 absent" and UPRI4I bit indicates "UDP port range for IPv4 absent", the Address information in octet j+2 to octet j+5 contains the IPv4 address.
  • TPRI4I bit indicates "TCP port range for IPv4 present" and UPRI4I bit indicates "UDP port range for IPv4 absent", the Address information in octet j+2 to octet j+9 contains the IPv4 address followed by the TCP port range field.
  • TPRI4I bit indicates "TCP port range for IPv4 absent" and UPRI4I bit indicates "UDP port range for IPv4 present", the Address information in octet j+2 to octet j+9 contains the IPv4 address followed by the UDP port range field.
  • TPRI4I bit indicates "TCP port range for IPv4 present" and UPRI4I bit indicates "UDP port range for IPv4 present", the Address information in octet j+2 to octet j+13 contains the IPv4 address followed by \endul the UDP port range field followed by the TCP port range field.
    See NOTE.
    The UDP port range field consists of the lowest UDP port number field followed by the highest UDP port number field, of the UDP port range assigned to the remote UE in the NAT function of 5G ProSe layer-3 UE-to-network relay.
    The TCP port range field consists of the lowest TCP port number field followed by highest TCP port number field, of the TCP port range assigned to the remote UE in the NAT function of 5G ProSe layer-3 UE-to-network relay.
    Each port number field is two octets long and bit 8 of first octet of the port number field represents the most significant bit of the port number and bit 1 of second octet of the port number field the least significant bit.
    If the Protocol used by remote UE indicates IPv6, the Address information in octet j+2 to octet j+9 contains the /64 IPv6 prefix of a remote UE. Bit 8 of octet j+2 represents the most significant bit of the /64 IPv6 prefix and bit 1 of octet j+9 the least significant bit.
    If the Protocol used by remote UE indicates Ethernet, the Address information in octet j+2 to octet j+7 contains the remote UE MAC address. Bit 8 of octet j+2 represents the most significant bit of the MAC address and bit 1 of octet j+7 the least significant bit.
    If the Protocol used by remote UE indicates Unstructured, the Address information octets are not included.
    If the Protocol used by remote UE indicates No IP info, the Address information octets are not included
    If the Remote UE ID type field indicates "PRUK ID" and the Remote UE ID format field indicates "64-bit string", then the HPLMN ID field is present otherwise the HPLMN ID field is absent. The HPLMN ID field indicates HPLMN ID of the 5G ProSe remote UE and is coded as value part of the PLMN ID information element as specified in TS 24.554 subclause 11.3.33 starting with the second octet.
NOTE:
In the present release of the specification, providing information for IP protocols other than UDP or TCP is not specified.
Up

Up   Top   ToC