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.4  5GS session management (5GSM) information elementsWord‑p. 771

9.11.4.1  5GSM capabilityWord‑p. 771

The purpose of the 5GSM capability information element is to indicate UE capability related to the PDU session management.
The 5GSM capability information element is coded as shown in Figure 9.11.4.1.1 and Table 9.11.4.1.1.
The 5GSM capability 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, Figure 9.11.4.1.1: 5GSM capability information element
Up
5GSM capability value
RqoS (octet 3, bit 1)
This bit indicates the 5GSM capability to support reflective QoS.
0Reflective QoS not supported
1Reflective QoS supported
Multi-homed IPv6 PDU session (MH6-PDU) (octet 3, bit 2)
This bit indicates the 5GSM capability for Multi-homed IPv6 PDU session.
0Multi-homed IPv6 PDU session not supported
1Multi-homed IPv6 PDU session supported
Ethernet PDN type in S1 mode (EPT-S1) (octet 3, bit 3)
This bit indicates UE's 5GSM capability for Ethernet PDN type in S1 mode.
0Ethernet PDN type in S1 mode not supported
1Ethernet PDN type in S1 mode supported
Supported ATSSS steering functionalities and steering modes (ATSSS-ST) (octet 3, bits 4 to 7)
These bits indicate the 5GSM capability of ATSSS steering functionalities and steering modes
Bits
4 3 2 1
0 0 0 0ATSSS not supported
0 0 0 1ATSSS Low-Layer functionality with any steering mode supported
0 0 1 0MPTCP functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode supported
0 0 1 1MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode supported
All other values are reserved.
Transfer of port management information containers (TPMIC) (octet 3, bit 8)
This bit indicates the 5GSM capability to support transfer of port management information containers
0Transfer of port management information containers not supported
1Transfer of port management information containers supported
Access performance measurements per QoS flow rule (APMQF) (octet 4, bit1)
This bit indicates the 5GSM capability to support access performance measurements using the QoS flow of the non default QoS rule, that is used by the service data flow (SDF) traffic.
0Access performance measurements per QoS flow not supported.
1Access performance measurements per QoS flow supported.
All other bits in octet 4 to 15 are spare and shall be coded as zero, if the respective octet is included in the information element.
Up

9.11.4.2  5GSM causeWord‑p. 772

The purpose of the 5GSM cause information element is to indicate the reason why a 5GSM request is rejected.
The 5GSM cause information element is coded as shown in Figure 9.11.4.2.1 and Table 9.11.4.2.1.
The 5GSM cause is a type 3 information element with 2 octets length.
Reproduction of 3GPP TS 24.501, Figure 9.11.4.2.1: 5GSM cause information element
Up
Cause value (octet 2)
Bits
8 7 6 5 4 3 2 1
0 0 0 0 1 0 0 0Operator determined barring
0 0 0 1 1 0 1 0Insufficient resources
0 0 0 1 1 0 1 1Missing or unknown DNN
0 0 0 1 1 1 0 0Unknown PDU session type
0 0 0 1 1 1 0 1User authentication or authorization failed
0 0 0 1 1 1 1 1Request rejected, unspecified
0 0 1 0 0 0 0 0Service option not supported
0 0 1 0 0 0 0 1Requested service option not subscribed
0 0 1 0 0 0 1 1PTI already in use
0 0 1 0 0 1 0 0Regular deactivation
0 0 1 0 0 1 0 15GS QoS not accepted
0 0 1 0 0 1 1 0Network failure
0 0 1 0 0 1 1 1Reactivation requested
0 0 1 0 1 0 0 1Semantic error in the TFT operation
0 0 1 0 1 0 1 0Syntactical error in the TFT operation
0 0 1 0 1 0 1 1Invalid PDU session identity
0 0 1 0 1 1 0 0Semantic errors in packet filter(s)
0 0 1 0 1 1 0 1Syntactical error in packet filter(s)
0 0 1 0 1 1 1 0Out of LADN service area
0 0 1 0 1 1 1 1PTI mismatch
0 0 1 1 0 0 1 0PDU session type IPv4 only allowed
0 0 1 1 0 0 1 1PDU session type IPv6 only allowed
0 0 1 1 0 1 1 0PDU session does not exist
0 0 1 1 1 0 0 1PDU session type IPv4v6 only allowed
0 0 1 1 1 0 1 0PDU session type Unstructured only allowed
0 0 1 1 1 0 1 1Unsupported 5QI value
0 0 1 1 1 1 0 1PDU session type Ethernet only allowed
0 1 0 0 0 0 1 1Insufficient resources for specific slice and DNN
0 1 0 0 0 1 0 0Not supported SSC mode
0 1 0 0 0 1 0 1Insufficient resources for specific slice
0 1 0 0 0 1 1 0Missing or unknown DNN in a slice
0 1 0 1 0 0 0 1Invalid PTI value
0 1 0 1 0 0 1 0Maximum data rate per UE for user-plane integrity protection is too low
0 1 0 1 0 0 1 1Semantic error in the QoS operation
0 1 0 1 0 1 0 0Syntactical error in the QoS operation
0 1 0 1 0 1 0 1Invalid mapped EPS bearer identity
0 1 0 1 1 1 1 1Semantically incorrect message
0 1 1 0 0 0 0 0Invalid mandatory information
0 1 1 0 0 0 0 1Message type non-existent or not implemented
0 1 1 0 0 0 1 0Message type not compatible with the protocol state
0 1 1 0 0 0 1 1Information element non-existent or not implemented
0 1 1 0 0 1 0 0Conditional IE error
0 1 1 0 0 1 0 1Message not compatible with the protocol state
0 1 1 0 1 1 1 1Protocol error, unspecified
Any other value received by the UE shall be treated as 0001 1111, "Request rejected, unspecified". Any other value received by the network shall be treated as 0110 1111, "protocol error, unspecified".
Up

9.11.4.3  Always-on PDU session indicationWord‑p. 774

The purpose of the Always-on PDU session indication information element is to indicate whether a PDU session is established as an always-on PDU session.
The Always-on PDU session indication information element is coded as shown in Figure 9.11.4.3.1 and Table 9.11.4.3.1.
The Always-on PDU session indication is a type 1 information element.
Reproduction of 3GPP TS 24.501, Figure 9.11.4.3.1: Always-on PDU session indication
Up
Always-on PDU session indication (APSI) (octet 1)
Bit
1
0Always-on PDU session not allowed
1Always-on PDU session required
Bits 2, 3 and 4 are spare and shall be coded as zero.
Up

9.11.4.4  Always-on PDU session requestedWord‑p. 774

The purpose of the Always-on PDU session requested information element is to indicate whether a PDU session is requested to be established as an always-on PDU session.
The Always-on PDU session requested information element is coded as shown in Figure 9.11.4.4.1 and Table 9.11.4.4.1.
The Always-on PDU session requested is a type 1 information element.
Reproduction of 3GPP TS 24.501, Figure 9.11.4.4.1: Always-on PDU session requested
Up
Always-on PDU session requested (APSR) (octet 1)
Bit
1
0Always-on PDU session not requested
1Always-on PDU session requested
Bits 2, 3 and 4 are spare and shall be coded as zero.
Up

9.11.4.5  Allowed SSC modeWord‑p. 774

The purpose of the Allowed SSC mode information element is to indicate the SSC modes allowed to be used by the UE for the PDU session.
The Allowed SSC mode information element is coded as shown in Figure 9.11.4.5.1 and Table 9.11.4.5.1.
The Allowed SSC mode is a type 1 information element.
Reproduction of 3GPP TS 24.501, Figure 9.11.4.5.1: Allowed SSC mode information element
Up
SSC1 (octet 1, bit 1)
Bit
1
0SSC mode 1 not allowed
1SSC mode 1 allowed
SSC2 (octet 1, bit 2)
Bit
2
0SSC mode 2 not allowed
1SSC mode 2 allowed
SSC3 (octet 1, bit 3)
Bit
3
0SSC mode 3 not allowed
1SSC mode 3 allowed
Bit 4 is spare and shall be encoded as zero.
Up

9.11.4.6  Extended protocol configuration optionsWord‑p. 775

9.11.4.7  Integrity protection maximum data rateWord‑p. 775

The purpose of the integrity protection maximum data rate information element is for the UE to indicate to the network the maximum data rate per UE for user-plane integrity protection for uplink and the maximum data rate per UE for user-plane integrity protection for downlink that are supported by the UE.
The integrity protection maximum data rate is coded as shown in Figure 9.11.4.7.1 and Table 9.11.4.7.2.
The integrity protection maximum data rate is a type 3 information element with a length of 3 octets.
Reproduction of 3GPP TS 24.501, Figure 9.11.4.7.1: Integrity protection maximum data rate information element
Up
Maximum data rate per UE for user-plane integrity protection for uplink (octet 2)
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 064 kbps (NOTE 3)
0 0 0 0 0 0 0 1NULL (NOTE 1)
1 1 1 1 1 1 1 1Full data rate (NOTE 2)
All other values are spare and shall not be used by a UE compliant to the present version of this specification. If received they shall be interpreted as "64 kbps".
Bits
8 7 6 5 4 3 2 1
Maximum data rate per UE for user-plane integrity protection for downlink (octet 3)
0 0 0 0 0 0 0 064 kbps (NOTE 3)
0 0 0 0 0 0 0 1NULL (NOTE 1)
1 1 1 1 1 1 1 1Full data rate (NOTE 2)
All other values are spare and shall not be used by a UE compliant to the present version of this specification. If received they shall be interpreted as "64 kbps".
NOTE 1:
This value shall be used when N3 data transfer is not supported by the UE.
NOTE 2:
If the UE supports N3 data transfer and supports standalone NR connected to 5GCN (this includes UEs supporting NR-NR dual connectivity, NR-E-UTRA dual connectivity with MN terminated bearers or both of them as described in TS 37.340), then the UE shall use this value.
NOTE 3:
The network can receive this value from a UE compliant to an earlier version of this specification or when the UE supports N3 data transfer and does not support standalone NR connected to 5GCN.
Up

9.11.4.8  Mapped EPS bearer contextsWord‑p. 776

The purpose of the mapped EPS bearer contexts information element is to indicate a set of EPS bearer contexts for a PDU session, as described in subclause 6.1.4.1.
The mapped EPS bearer contexts information element is a type 6 information element with a minimum length of 7 octet and a maximum length of 65538 octets.
The mapped EPS bearer contexts information element is coded as shown in Figure 9.11.4.8.1, Figure 9.11.4.8.2, Figure 9.11.4.8.3 and Table 9.11.4.8.1.
Reproduction of 3GPP TS 24.501, Figure 9.11.4.8.1: Mapped EPS bearer contexts
Up
Reproduction of 3GPP TS 24.501, Figure 9.11.4.8.2: Mapped EPS bearer context
Up
Reproduction of 3GPP TS 24.501, Figure 9.11.4.8.3: EPS parameters list
Up
EPS bearer identity (octet 4)
Bits 5 to 8 contain the EPS bearer identity, and are coded as specified in subclause 9.3.2 of TS 24.301. Bits 1 to 4 are spare and shall be coded as zero.
Operation code (bits 8 to 7 of octet 7)
Bits
8 7
0 0Reserved
0 1Create new EPS bearer
1 0Delete existing EPS bearer
1 1Modify existing EPS bearer
Bit 6 of octet 7 is spare and shall be coded as zero.
E bit (bit 5 of octet 7)
For the "create new EPS bearer" operation, the E bit is encoded as follows:
Bit
5
0parameters list is not included (NOTE)
1parameters list is included
For the "modify existing EPS bearer" operation, the E bit is encoded as follows:
Bit
5
0extension of previously provided parameters list
1replacement of all previously provided parameters list
If the E bit is set to "parameters list is included", the number of EPS parameters field has non-zero value. If the E bit is set to "extension of previously provided parameters list" or "replacement of previously provided parameters list", the number of parameters field has non-zero value.
For the "create new EPS bearer" operation and "delete existing EPS bearer" operation, bit 5 of octet 7 is ignored.
Number of EPS parameters (bits 4 to 1 of octet 7)
The number of EPS parameters contains the binary coding for the number of EPS parameters in the EPS parameters list field. The number of EPS parameters field is encoded in bits 4 through 1 of octet 7 where bit 4 is the most significant and bit 1 is the least significant bit.
EPS parameters list (octets 8 to u)
The EPS parameters list contains a variable number of EPS parameters.
Each EPS parameter included in the EPS parameters list is of variable length and consists of:
  • an EPS parameter identifier (1 octet);
  • the length of the EPS parameter contents (1 octet); and
  • the EPS parameter contents itself (variable amount of octets).
The EPS parameter identifier field is used to identify each EPS parameter included in the EPS parameters list and it contains the hexadecimal coding of the EPS parameter identifier. Bit 8 of the EPS parameter identifier field contains the most significant bit and bit 1 contains the least significant bit. In this version of the protocol, the following EPS parameter identifiers are specified:
  • 01H (Mapped EPS QoS parameters);
  • 02H (Mapped extended EPS QoS parameters); and
  • 03H (Traffic flow template).
  • 04H (APN-AMBR).
  • 05H (extended APN-AMBR).
If the EPS parameters list contains an EPS parameter identifier that is not supported by the receiving entity the corresponding EPS parameter shall be discarded.
The length of EPS parameter contents field contains the binary coded representation of the length of the EPS parameter contents field. The first bit in transmission order is the most significant bit.
When the parameter identifier indicates mapped EPS QoS parameters, the length and parameter contents field are coded as specified in subclause 9.9.4.3 of TS 24.301.
When the parameter identifier indicates mapped extended EPS QoS parameters, the length and parameter contents field are coded as specified in subclause 9.9.4.30 of TS 24.301.
When the parameter identifier indicates traffic flow template, the length and parameter contents field are coded from octet 2 as shown Figure 10.5.144 and Table 10.5.16.2 of TS 24.008.
When the parameter identifier indicates APN-AMBR, the length and parameter contents field are coded as specified in subclause 9.9.4.2 of TS 24.301.
When the parameter identifier indicates Extended APN-AMBR, the length and parameter contents field are coded as specified in subclause 9.9.4.29 of TS 24.301.
NOTE:
This value shall not be used In this version of the specification.
Up

9.11.4.9  Maximum number of supported packet filtersWord‑p. 780

The purpose of the Maximum number of supported packet filters information element is for the UE to indicate to the network the maximum number of packet filters, associated with signaled QoS rules, that can be supported by the UE for the PDU session that is being established, when the PDU session type "IPv4", "IPv6", "IPv4v6" or "Ethernet".
The Maximum number of supported packet filters is coded as shown in Figure 9.11.4.9.1 and Table 9.11.4.9.1.
The Maximum number of supported packet filters is a type 3 information element with a length of 3 octets.
Reproduction of 3GPP TS 24.501, Figure 9.11.4.9.1: Maximum number of supported packet filters information element
Up
Maximum number of supported packet filters (octet 2 to 3)
In the Maximum number of supported packet filters field bit 8 of the first octet is the most significant bit and bit 6 of second octet is the least significant bit. Bit 5 to bit 1 of the second octet are spare bits and shall be coded as zero.
The number of supported packet filters shall be in the range of 17 to 1024.
Up

Up   Top   ToC