Content for TS 24.501 Word version: 18.2.1
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 elements
9.11.3.1 5GMM capability
9.11.3.2 5GMM cause
9.11.3.2A 5GS DRX parameters
9.11.3.3 5GS identity type
...
...
9.11.3 5GS mobility management (5GMM) information elements p. 754
9.11.3.1 5GMM capability p. 754
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.
| EPC NAS supported (S1 mode) (octet 3, bit 1) | |
| 0 | S1 mode not supported |
| 1 | S1 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) | |
| 0 | LPP in N1 mode not supported |
| 1 | LPP in N1 mode supported (see TS 37.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. | |
| 0 | Restriction on use of enhanced coverage not supported |
| 1 | Restriction 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. | |
| 0 | Control plane CIoT 5GS optimization not supported |
| 1 | Control plane CIoT 5GS optimization supported |
| N3 data transfer (N3 data) (octet 3, bit 6) | |
| This bit indicates the capability for N3 data transfer. | |
| 0 | N3 data transfer supported |
| 1 | N3 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. | |
| 0 | IP header compression for control plane CIoT 5GS optimization not supported |
| 1 | IP header compression for control plane CIoT 5GS optimization supported |
| Service gap control (SGC) (octet 3, bit 8) | |
| 0 | service gap control not supported |
| 1 | service gap control supported |
| 5G-SRVCC from NG-RAN to UTRAN (5GSRVCC) capability (octet 4, bit 1) | |
| 0 | 5G-SRVCC from NG-RAN to UTRAN not supported |
| 1 | 5G-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. | |
| 0 | User plane CIoT 5GS optimization not supported |
| 1 | User 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. | |
| 0 | V2X not supported |
| 1 | V2X 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. | |
| 0 | V2X communication over E-UTRA-PC5 not supported |
| 1 | V2X 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. | |
| 0 | V2X communication over NR-PC5 not supported |
| 1 | V2X communication over NR-PC5 supported |
| Location Services (5G-LCS) notification mechanisms capability (octet 4, bit 6) | |
| 0 | LCS notification mechanisms not supported |
| 1 | LCS 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. | |
| 0 | Network slice-specific authentication and authorization not supported |
| 1 | Network slice-specific authentication and authorization supported |
| Radio capability signalling optimisation (RACS) capability (octet 4, bit 8) | |
| 0 | RACS not supported |
| 1 | RACS supported |
| Closed Access Group (CAG) capability (octet 5, bit 1) | |
| 0 | CAG not supported |
| 1 | CAG supported |
| WUS assistance (WUSA) information reception capability (octet 5, bit 2) | |
| 0 | WUS assistance information reception not supported |
| 1 | WUS 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. | |
| 0 | Multiple user-plane resources not supported |
| 1 | Multiple user-plane resources supported |
| Ethernet header compression for control plane CIoT 5GS optimization (5G-EHC-CP CIoT) (octet 5, bit 4) | |
| 0 | Ethernet header compression for control plane CIoT 5GS optimization not supported |
| 1 | Ethernet 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. | |
| 0 | Extended rejected NSSAI not supported |
| 1 | Extended rejected NSSAI supported |
| 5G ProSe direct discovery (5G ProSe-dd) (octet 5, bit 6) | |
| This bit indicates the capability for 5G ProSe direct discovery. | |
| 0 | 5G ProSe direct discovery not supported |
| 1 | 5G ProSe direct discovery supported |
| 5G ProSe direct communication (5G ProSe-dc) (octet 5, bit 7) | |
| This bit indicates the capability for 5G ProSe direct communication. | |
| 0 | 5G ProSe direct communication not supported |
| 1 | 5G ProSe direct communication supported |
| 5G ProSe layer-2 UE-to-network-relay (5G ProSe-l2relay) (octet 5, bit 8) | |
| This bit indicates the capability to act as a layer-2 5G ProSe UE-to-network relay UE | |
| 0 | Acting as a 5G ProSe layer-2 UE-to-network relay UE not supported |
| 1 | Acting as a 5G ProSe layer-2 UE-to-network relay UE supported |
| 5G ProSe layer-3 UE-to-network-relay (5G ProSe-l3relay) (octet 6, bit 1) | |
| This bit indicates the capability to act as a layer-3 5G ProSe UE-to-network relay UE | |
| 0 | Acting as a 5G ProSe layer-3 UE-to-network relay UE not supported |
| 1 | Acting as a 5G ProSe layer-3 UE-to-network relay UE supported |
| 5G ProSe layer-2 UE-to-network-remote (5G ProSe-l2rmt) (octet 6, bit 2) | |
| This bit indicates the capability to act as a layer-2 5G ProSe UE-to-network remote UE | |
| 0 | Acting as a 5G ProSe layer-2 UE-to-network remote UE not supported |
| 1 | Acting as a 5G ProSe layer-2 UE-to-network remote UE supported |
| 5G ProSe layer-3 UE-to-network-remote (5G ProSe-l3rmt) (octet 6, bit 3) | |
| This bit indicates the capability to act as a layer-3 5G ProSe UE-to-network remote UE | |
| 0 | Acting as a 5G ProSe layer-3 UE-to-network remote UE not supported |
| 1 | Acting as a 5G ProSe layer-3 UE-to-network remote UE supported |
| NR paging subgroup support indication (NR-PSSI) (octet 6, bit 4) | |
| This bit indicates the capability to support NR paging subgrouping | |
| 0 | NR paging subgrouping not supported |
| 1 | NR paging subgrouping supported |
| N1 NAS signalling connection release (NCR) (octet 6, bit 5) | |
| This bit indicates whether N1 NAS signalling connection release is supported. | |
| 0 | N1 NAS signalling connection release not supported |
| 1 | N1 NAS signalling connection release supported |
| Paging indication for voice services (PIV) (octet 6, bit 6) | |
| This bit indicates whether paging indication for voice services is supported. | |
| 0 | paging indication for voice services not supported |
| 1 | paging indication for voice services supported |
| Reject paging request (RPR) (octet 6, bit 7) | |
| This bit indicates whether reject paging request is supported. | |
| 0 | reject paging request not supported |
| 1 | reject paging request supported |
| Paging restriction (PR) (octet 6, bit 8) | |
| This bit indicates whether paging restriction is supported. | |
| 0 | paging restriction not supported |
| 1 | paging restriction supported |
| NSSRG (octet 7, bit 1) | |
| This bit indicates the capability to support the NSSRG. | |
| 0 | NSSRG not supported |
| 1 | NSSRG supported |
| Minimization of service interruption (MINT) (octet 7, bit 2) | |
| This bit indicates the capability to support Minimization of service interruption (MINT) | |
| 0 | MINT not supported |
| 1 | MINT supported |
| Event notification (EventNotification) (octet 7, bit 3) | |
| This bit indicates the capability to support event notification for upper layers | |
| 0 | Event notification not supported |
| 1 | Event notification supported |
| SOR-SNPN-SI (SOR SNPN SI) (octet 7, bit 4) | |
| This bit indicates the capability to support SOR-SNPN-SI | |
| 0 | SOR-SNPN-SI not supported |
| 1 | SOR-SNPN-SI supported |
| Extended CAG information list support (Ex-CAG) (octet 7, bit 5) | |
| This bit indicates the capability to support extended CAG information list. | |
| 0 | Extended CAG information list not supported |
| 1 | Extended CAG information list supported |
| NSAG (octet 7, bit 6) | |
| This bit indicates the capability to support NSAG. | |
| 0 | NSAG not supported |
| 1 | NSAG supported |
| Equivalent SNPNs indicator (ESI) (octet 7, bit 7) | |
| This bit indicates the capability to support equivalent SNPNs. | |
| 0 | Equivalent SNPNs not supported |
| 1 | Equivalent SNPNs supported |
| UN-PER (octet 7, bit 8) | |
| This bit indicates the capability to support unavailability period. | |
| 0 | Unavailability period not supported |
| 1 | Unavailability period supported |
| Slice-based N3IWF selection support (SBNS) (octet 8, bit 1) | |
| This bit indicates the capability to support slice-based N3IWF selection. | |
| 0 | Slice-based N3IWF selection not supported |
| 1 | Slice-based N3IWF selection supported |
| UAS (octet 8, bit 2) | |
| This bit indicates the capability to support UAS services. | |
| 0 | UAS services not supported |
| 1 | UAS services supported |
| MPS indicator update (MPSIU) (octet 8, bit 3) | |
| This bit indicates the capability to support MPS indicator update via the UE configuration update procedure. | |
| 0 | MPS indicator update not supported |
| 1 | MPS indicator update not supported |
| ECI (octet 8, bit 4) | |
| This bit indicates the capability to support enhanced CAG information. | |
| 0 | Enhanced CAG information not supported |
| 1 | Enhanced CAG information supported |
| Reconnection to the network due to RAN timing synchronization status change (RANtiming) (octet 8, bit 5) | |
| This bit indicates the capability to support Reconnection to the network due to RAN timing synchronization status change. | |
| 0 | Reconnection to the network due to RAN timing synchronization status change not supported |
| 1 | Reconnection to the network due to RAN timing synchronization status change supported |
| LADN per DNN and S-NSSAI support (LADN-DS) (octet 8, bit 6) | |
| This bit indicates the capability to support LADN per DNN and S-NSSAI. | |
| 0 | LADN per DNN and S-NSSAI not supported |
| 1 | LADN per DNN and S-NSSAI supported |
| Network slice replacement (NSR) (octet 8, bit 7) | |
| This bit indicates the capability to support network slice replacement. | |
| 0 | Network slice replacement not supported |
| 1 | Network slice replacement supported |
| Slice-based TNGF selection support (SBTS) (octet 8, bit 8) | |
| This bit indicates the capability to support slice-based TNGF selection. | |
| 0 | Slice-based TNGF selection not supported |
| 1 | Slice-based TNGF selection supported |
| A2X over E-UTRA-PC5 (A2XEPC5) (octet 9, bit 1) | |
| This bit indicates the capability for A2X over E-UTRA-PC5, as specified in TS 24.577 [60]. | |
| 0 | A2X over E-UTRA-PC5 not supported |
| 1 | A2X over E-UTRA-PC5 supported |
| A2X over NR-PC5 (A2XNPC5) (octet 9, bit 2) | |
| This bit indicates the capability for A2X over NR-PC5, as specified in TS 24.577 [60]. | |
| 0 | A2X over NR-PC5 not supported |
| 1 | A2X over NR-PC5 supported |
| Bits 3-8 in octet 9 and bits in octets 10 to 15 are spare and shall be coded as zero, if the respective octet is included in the information element. | |
9.11.3.2 5GMM cause p. 761
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 length of 2 octets.
| Cause value (octet 2) | |
| Bits
8 7 6 5 4 3 2 1 | |
| 0 0 0 0 0 0 1 1 | Illegal UE |
| 0 0 0 0 0 1 0 1 | PEI not accepted |
| 0 0 0 0 0 1 1 0 | Illegal ME |
| 0 0 0 0 0 1 1 1 | 5GS services not allowed |
| 0 0 0 0 1 0 0 1 | UE identity cannot be derived by the network |
| 0 0 0 0 1 0 1 0 | Implicitly de-registered |
| 0 0 0 0 1 0 1 1 | PLMN not allowed |
| 0 0 0 0 1 1 0 0 | Tracking area not allowed |
| 0 0 0 0 1 1 0 1 | Roaming not allowed in this tracking area |
| 0 0 0 0 1 1 1 1 | No suitable cells in tracking area |
| 0 0 0 1 0 1 0 0 | MAC failure |
| 0 0 0 1 0 1 0 1 | Synch failure |
| 0 0 0 1 0 1 1 0 | Congestion |
| 0 0 0 1 0 1 1 1 | UE security capabilities mismatch |
| 0 0 0 1 1 0 0 0 | Security mode rejected, unspecified |
| 0 0 0 1 1 0 1 0 | Non-5G authentication unacceptable |
| 0 0 0 1 1 0 1 1 | N1 mode not allowed |
| 0 0 0 1 1 1 0 0 | Restricted service area |
| 0 0 0 1 1 1 1 1 | Redirection to EPC required |
| 0 0 1 0 1 0 1 1 | LADN not available |
| 0 0 1 1 1 1 1 0 | No network slices available |
| 0 1 0 0 0 0 0 1 | Maximum number of PDU sessions reached |
| 0 1 0 0 0 0 1 1 | Insufficient resources for specific slice and DNN |
| 0 1 0 0 0 1 0 1 | Insufficient resources for specific slice |
| 0 1 0 0 0 1 1 1 | ngKSI already in use |
| 0 1 0 0 1 0 0 0 | Non-3GPP access to 5GCN not allowed |
| 0 1 0 0 1 0 0 1 | Serving network not authorized |
| 0 1 0 0 1 0 1 0 | Temporarily not authorized for this SNPN |
| 0 1 0 0 1 0 1 1 | Permanently not authorized for this SNPN |
| 0 1 0 0 1 1 0 0 | Not authorized for this CAG or authorized for CAG cells only |
| 0 1 0 0 1 1 0 1 | Wireline access area not allowed |
| 0 1 0 0 1 1 1 0 | PLMN not allowed to operate at the present UE location |
| 0 1 0 0 1 1 1 1 | UAS services not allowed |
| 0 1 0 1 0 0 0 0 | Disaster roaming for the determined PLMN with disaster condition not allowed |
| 0 1 0 1 0 0 0 1 | Selected N3IWF is not compatible with the allowed NSSAI |
| 0 1 0 1 0 0 1 0 | Selected TNGF is not compatible with the allowed NSSAI |
| 0 1 0 1 1 0 1 0 | Payload was not forwarded |
| 0 1 0 1 1 0 1 1 | DNN not supported or not subscribed in the slice |
| 0 1 0 1 1 1 0 0 | Insufficient user-plane resources for the PDU session |
| 0 1 0 1 1 1 0 1 | Onboarding services terminated |
| 0 1 0 1 1 1 1 1 | Semantically incorrect message |
| 0 1 1 0 0 0 0 0 | Invalid mandatory information |
| 0 1 1 0 0 0 0 1 | Message type non-existent or not implemented |
| 0 1 1 0 0 0 1 0 | Message type not compatible with the protocol state |
| 0 1 1 0 0 0 1 1 | Information element non-existent or not implemented |
| 0 1 1 0 0 1 0 0 | Conditional IE error |
| 0 1 1 0 0 1 0 1 | Message not compatible with the protocol state |
| 0 1 1 0 1 1 1 1 | Protocol 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". | |
9.11.3.2A 5GS DRX parameters p. 763
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.
| 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 0 | DRX value not specified |
| 0 0 0 1 | DRX cycle parameter T = 32 |
| 0 0 1 0 | DRX cycle parameter T = 64 |
| 0 0 1 1 | DRX cycle parameter T = 128 |
| 0 1 0 0 | DRX 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. | |
9.11.3.3 5GS identity type p. 763
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.
| Type of identity (octet 1) | |
| Bits
3 2 1 | |
| 0 0 1 | SUCI |
| 0 1 0 | 5G-GUTI |
| 0 1 1 | IMEI |
| 1 0 0 | 5G-S-TMSI |
| 1 0 1 | IMEISV |
| 1 1 0 | MAC address |
| 1 1 1 | EUI-64 |
| All other values are unused and shall be interpreted as "SUCI", if received by the UE. | |
