3GPP 24.501 v20.0.0 — the document's own text
9.11.4.2 5GSM 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 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 a length of 2 octets.
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| 5GSM cause IEI | octet 1 | |||||||
| Cause value | octet 2 |
Figure 9.11.4.2.1: 5GSM cause information element
Table 9.11.4.2.1: 5GSM cause information element
| Cause value (octet 2) | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| Bits | |||||||||
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | ||
| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | Operator determined barring | |
| 0 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | Insufficient resources | |
| 0 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | Missing or unknown DNN | |
| 0 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | Unknown PDU session type | |
| 0 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | User authentication or authorization failed | |
| 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | Request rejected, unspecified | |
| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | Service option not supported | |
| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | Requested service option not subscribed | |
| 0 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | PTI already in use | |
| 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | Regular deactivation | |
| 0 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 5GS QoS not accepted | |
| 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | Network failure | |
| 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | Reactivation requested | |
| 0 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | Semantic error in the TFT operation | |
| 0 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | Syntactical error in the TFT operation | |
| 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | Invalid PDU session identity | |
| 0 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | Semantic errors in packet filter(s) | |
| 0 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | Syntactical error in packet filter(s) | |
| 0 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | Out of LADN service area | |
| 0 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | PTI mismatch | |
| 0 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | PDU session type IPv4 only allowed | |
| 0 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | PDU session type IPv6 only allowed | |
| 0 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | PDU session does not exist | |
| 0 | 0 | 1 | 1 | 1 | 0 | 0 | 1 | PDU session type IPv4v6 only allowed | |
| 0 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | PDU session type Unstructured only allowed | |
| 0 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | Unsupported 5QI value | |
| 0 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | PDU session type Ethernet only allowed | |
| 0 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | Insufficient resources for specific slice and DNN | |
| 0 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | Not supported SSC mode | |
| 0 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | Insufficient resources for specific slice | |
| 0 | 1 | 0 | 0 | 0 | 1 | 1 | 0 | Missing or unknown DNN in a slice | |
| 0 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | Invalid PTI value | |
| 0 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | Maximum data rate per UE for user-plane integrity protection is too low | |
| 0 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | Semantic error in the QoS operation | |
| 0 | 1 | 0 | 1 | 0 | 1 | 0 | 0 | Syntactical error in the QoS operation | |
| 0 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | Invalid mapped EPS bearer identity | |
| 0 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | UAS services not allowed | |
| 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | QoS differentiation for non-3GPP device identifier(s) not available | |
| 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 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". |