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  5GS mobility management (5GMM) information elementsWord‑p. 664

9.11.3.1  5GMM capabilityWord‑p. 664

The purpose of the 5GMM capability information element is to provide the network with information concerning aspects of the UE related to the 5GCN or interworking with the EPS. The contents might affect the manner in which the network handles the operation of the UE.
The 5GMM capability information element is coded as shown in Figure 9.11.3.1.1 and Table 9.11.3.1.1.
The 5GMM 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.3.1.1: 5GMM capability information element
Up
EPC NAS supported (S1 mode) (octet 3, bit 1)
0S1 mode not supported
1S1 mode supported
ATTACH REQUEST message containing PDN CONNECTIVITY REQUEST message for handover support (HO attach) (octet 3, bit 2)
0 ATTACH REQUEST message containing PDN CONNECTIVITY REQUEST message with request type set to "handover" or "handover of emergency bearer services" to transfer PDU session from N1 mode to S1 mode not supported
1 ATTACH REQUEST message containing PDN CONNECTIVITY REQUEST message with request type set to "handover" or "handover of emergency bearer services" to transfer PDU session from N1 mode to S1 mode supported
LTE Positioning Protocol (LPP) capability (octet 3, bit 3)
0LPP in N1 mode not supported
1LPP in N1 mode supported (see TS 36.355)
Restriction on use of enhanced coverage support (RestrictEC) (octet 3, bit 4)
This bit indicates the capability to support restriction on use of enhanced coverage.
0Restriction on use of enhanced coverage not supported
1Restriction on use of enhanced coverage supported
Control plane CIoT 5GS optimization (5G-CP CIoT) (octet 3, bit 5)
This bit indicates the capability for control plane CIoT 5GS optimization.
0Control plane CIoT 5GS optimization not supported
1Control plane CIoT 5GS optimization supported
N3 data transfer (N3 data) (octet 3, bit 6)
This bit indicates the capability for N3 data transfer.
0N3 data transfer supported
1N3 data transfer not supported
IP header compression for control plane CIoT 5GS optimization (5G-IPHC-CP CIoT) (octet 3, bit 7)
This bit indicates the capability for IP header compression for control plane CIoT 5GS optimization.
0IP header compression for control plane CIoT 5GS optimization not supported
1IP header compression for control plane CIoT 5GS optimization supported
Service gap control (SGC) (octet 3, bit 8)
0service gap control not supported
1service gap control supported
5G-SRVCC from NG-RAN to UTRAN (5GSRVCC) capability (octet 4, bit 1)
05G-SRVCC from NG-RAN to UTRAN not supported
15G-SRVCC from NG-RAN to UTRAN supported (see TS 23.216)
User plane CIoT 5GS optimization (5G-UP CIoT) (octet 4, bit 2)
This bit indicates the capability for user plane CIoT 5GS optimization.
0User plane CIoT 5GS optimization not supported
1User plane CIoT 5GS optimization supported
V2X capability (V2X) (octet 4, bit 3)
This bit indicates the capability for V2X, as specified in TS 24.587.
0V2X not supported
1V2X supported
V2X communication over E-UTRA-PC5 capability (V2XCEPC5) (octet 4, bit 4)
This bit indicates the capability for V2X communication over E-UTRA-PC5, as specified in TS 24.587.
0V2X communication over E-UTRA-PC5 not supported
1V2X communication over E-UTRA-PC5 supported
V2X communication over NR-PC5 capability (V2XCNPC5) (octet 4, bit 5)
This bit indicates the capability for V2X communication over NR-PC5, as specified in TS 24.587.
0V2X communication over NR-PC5 not supported
1V2X communication over NR-PC5 supported
Location Services (5G-LCS) notification mechanisms capability (octet 4, bit 6)
0LCS notification mechanisms not supported
1LCS notification mechanisms supported (see TS 23.273)
Network slice-specific authentication and authorization (NSSAA) (octet 4, bit 7)
This bit indicates the capability to support network slice-specific authentication and authorization.
0Network slice-specific authentication and authorization not supported
1Network slice-specific authentication and authorization supported
Radio capability signalling optimisation (RACS) capability (octet 4, bit 8)
0RACS not supported
1RACS supported
Closed Access Group (CAG) capability (octet 5, bit 1)
0CAG not supported
1CAG supported
WUS assistance (WUSA) information reception capability (octet 5, bit 2)
0WUS assistance information reception not supported
1WUS assistance information reception supported
Multiple user-plane resources support (multipleUP) (octet 5, bit 3)
This bit indicates the capability to support multiple user-plane resources in NB-N1 mode.
0Multiple user-plane resources not supported
1Multiple user-plane resources supported
Ethernet header compression for control plane CIoT 5GS optimization (5G-EHC-CP CIoT) (octet 5, bit 4)
0Ethernet header compression for control plane CIoT 5GS optimization not supported
1Ethernet header compression for control plane CIoT 5GS optimization supported
Extended rejected NSSAI support (ER-NSSAI) (octet 5, bit 5)
This bit indicates the capability to support extended rejected NSSAI.
0Extended rejected NSSAI not supported
1Extended rejected NSSAI supported
ProSe direct discovery (ProSe-dd) (octet 5, bit 6)
This bit indicates the capability for ProSe direct discovery.
0ProSe direct discovery not supported
1ProSe direct discovery supported
ProSe direct communication (ProSe-dc) (octet 5, bit 7)
This bit indicates the capability for ProSe direct communication.
0ProSe direct communication not supported
1ProSe direct communication supported
ProSe Layer-2 UE-to-network-relay (ProSe-l2relay) (octet 5, bit 8)
This bit indicates the capability to act as a layer-2 ProSe UE-to-network relay
0Acting as a ProSe layer-2 UE-to-network relay not supported
1Acting as a ProSe layer-2 UE-to-network relay supported
ProSe Layer-3 UE-to-network-relay (ProSe-l3relay) (octet 6, bit 1)
This bit indicates the capability to act as a layer-3 ProSe UE-to-network relay
0Acting as a ProSe layer-3 UE-to-network relay not supported
1Acting as a ProSe layer-3 UE-to-network relay supported
ProSe Layer-2 UE-to-network-remote (ProSe-l2rmt) (octet 6, bit 2)
This bit indicates the capability to act as a layer-2 ProSe UE-to-network remote UE
0Acting as a ProSe layer-2 UE-to-network remote UE not supported
1Acting as a ProSe layer-2 UE-to-network remote UE supported
ProSe Layer-3 UE-to-network-remote (ProSe-l3rmt) (octet 6, bit 3)
This bit indicates the capability to act as a layer-3 ProSe UE-to-network remote UE
0Acting as a ProSe layer-3 UE-to-network remote UE not supported
1Acting as a ProSe layer-3 UE-to-network remote UE supported
bits 4-8 in octet 6 and bits in octets 7 to 15 are spare and shall be coded as zero, if the respective octet is included in the information element.
Up

9.11.3.2  5GMM causeWord‑p. 669

The purpose of the 5GMM cause information element is to indicate the reason why a 5GMM request from the UE is rejected by the network.
The 5GMM cause information element is coded as shown in Figure 9.11.3.2.1 and Table 9.11.3.2.1.
The 5GMM cause is a type 3 information element with 2 octets length.
Reproduction of 3GPP TS 24.501, Figure 9.11.3.2.1: 5GMM cause information element
Up
Cause value (octet 2)
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 1 1Illegal UE
0 0 0 0 0 1 0 1PEI not accepted
0 0 0 0 0 1 1 0Illegal ME
0 0 0 0 0 1 1 15GS services not allowed
0 0 0 0 1 0 0 1UE identity cannot be derived by the network
0 0 0 0 1 0 1 0Implicitly de-registered
0 0 0 0 1 0 1 1PLMN not allowed
0 0 0 0 1 1 0 0Tracking area not allowed
0 0 0 0 1 1 0 1Roaming not allowed in this tracking area
0 0 0 0 1 1 1 1No suitable cells in tracking area
0 0 0 1 0 1 0 0MAC failure
0 0 0 1 0 1 0 1Synch failure
0 0 0 1 0 1 1 0Congestion
0 0 0 1 0 1 1 1UE security capabilities mismatch
0 0 0 1 1 0 0 0Security mode rejected, unspecified
0 0 0 1 1 0 1 0Non-5G authentication unacceptable
0 0 0 1 1 0 1 1N1 mode not allowed
0 0 0 1 1 1 0 0Restricted service area
0 0 0 1 1 1 1 1Redirection to EPC required
0 0 1 0 1 0 1 1LADN not available
0 0 1 1 1 1 1 0No network slices available
0 1 0 0 0 0 0 1Maximum number of PDU sessions reached
0 1 0 0 0 0 1 1Insufficient resources for specific slice and DNN
0 1 0 0 0 1 0 1Insufficient resources for specific slice
0 1 0 0 0 1 1 1ngKSI already in use
0 1 0 0 1 0 0 0Non-3GPP access to 5GCN not allowed
0 1 0 0 1 0 0 1Serving network not authorized
0 1 0 0 1 0 1 0Temporarily not authorized for this SNPN
0 1 0 0 1 0 1 1Permanently not authorized for this SNPN
0 1 0 0 1 1 0 0Not authorized for this CAG or authorized for CAG cells only
0 1 0 0 1 1 0 1Wireline access area not allowed
0 1 0 0 1 1 1 0PLMN not allowed to operate at the present UE location
0 1 0 0 1 1 1 1UAS services not allowed
0 1 0 1 1 0 1 0Payload was not forwarded
0 1 0 1 1 0 1 1DNN not supported or not subscribed in the slice
0 1 0 1 1 1 0 0Insufficient user-plane resources for the PDU session
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 mobile station shall be treated as 0110 1111, "protocol error, unspecified". Any other value received by the network shall be treated as 0110 1111, "protocol error, unspecified".
Up

9.11.3.2A  5GS DRX parametersWord‑p. 670

The purpose of the 5GS DRX parameters information element is to indicate that the UE wants to use DRX and for the network to indicate the DRX cycle value to be used at paging.
The 5GS DRX parameters is a type 4 information element with a length of 3 octets.
The 5GS DRX parameters information element is coded as shown in Figure 9.11.3.2A.1 and Table 9.11.3.2A.1.
The value part of a DRX parameter information element is coded as shown in Table 9.11.3.2A.1.
Reproduction of 3GPP TS 24.501, Figure 9.11.3.2A.1: 5GS DRX parameters information element
Up
DRX value (bits 4 to 1 of octet 3)
This field represents the DRX cycle parameter 'T' as defined in TS 38.304 or TS 36.304.
Bits
4 3 2 1
0 0 0 0DRX value not specified
0 0 0 1DRX cycle parameter T = 32
0 0 1 0DRX cycle parameter T = 64
0 0 1 1DRX cycle parameter T = 128
0 1 0 0DRX cycle parameter T = 256
All other values shall be interpreted as "DRX value not specified" by this version of the protocol.
Bits 5 to 8 of octet 3 are spare and shall be coded as zero.
Up

9.11.3.3  5GS identity typeWord‑p. 671

The purpose of the 5GS identity type information element is to specify which identity is requested.
The 5GS identity type is a type 1 information element.
The 5GS identity type information element is coded as shown in Figure 9.11.3.3.1 and Table 9.11.3.3.1.
Reproduction of 3GPP TS 24.501, Figure 9.11.3.3.1: 5GS identity type information element
Up
Type of identity (octet 1)
Bits
3 2 1
0 0 1SUCI
0 1 05G-GUTI
0 1 1IMEI
1 0 05G-S-TMSI
1 0 1IMEISV
1 1 0MAC address
1 1 1EUI-64
All other values are unused and shall be interpreted as "SUCI", if received by the UE.
Up

Up   Top   ToC