3GPP 24.501 v20.0.0 — the document's own text
9.11.3.2 5GMM cause
Taught in 4. Inside TS 24.501, the document at the centre (CT1 — the group that writes what your phone says, overview).
The purpose of the 5GMM cause information element is to indicate the reason why a 5GMM request is rejected.
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.
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| 5GMM cause IEI | octet 1 | |||||||
| Cause value | octet 2 |
Figure 9.11.3.2.1: 5GMM cause information element
Table 9.11.3.2.1: 5GMM cause information element
| 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 | 0 | 1 | 0 | 0 | IAB-node operation not authorized | |
| 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 | 0 | User plane positioning not authorized | |
| 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". |