3GPP 24.501 v20.0.0 — the document's own text
9.11.3.46 Rejected NSSAI
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 Rejected NSSAI information element is to identify a collection of rejected S-NSSAIs.
The Rejected NSSAI information element is coded as shown in figure 9.11.3.46.1, figure 9.11.3.46.2 and table 9.11.3.46.1.
The Rejected NSSAI is a type 4 information element with a minimum length of 4 octets and a maximum length of 42 octets.
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| Rejected NSSAI IEI | octet 1 | |||||||
| Length of Rejected NSSAI contents | octet 2 | |||||||
| Rejected S-NSSAI 1 | octet 3octet m | |||||||
| Rejected S-NSSAI 2 | octet m+1*octet n* | |||||||
| … | octet n+1*octet u* | |||||||
| Rejected S-NSSAI n | octet u+1*octet v* |
Figure 9.11.3.46.1: Rejected NSSAI information element
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| Length of rejected S-NSSAI | Cause value | octet 3 | ||||||
| SST | octet 4 | |||||||
| SD | octet 5*octet 7* |
Figure 9.11.3.46.2: Rejected S-NSSAI
Table 9.11.3.46.1: Rejected NSSAI information element
| Value part of the Rejected NSSAI information element (octet 3 to v) | |||||
|---|---|---|---|---|---|
| The value part of the Rejected NSSAI information element consists of one or more rejected S-NSSAIs. Each rejected S-NSSAI consists of one S-NSSAI and an associated cause value. The length of each rejected S-NSSAI can be determined by the 'length of rejected S-NSSAI' field in the first octet of the rejected S-NSSAI. | |||||
| The UE shall store the complete list received (NOTE 0). If more than 8 rejected S-NSSAIs are included in this information element, the UE shall store the first 8 rejected S-NSSAIs and ignore the remaining octets of the information element. | |||||
| Rejected S-NSSAI: | |||||
| Cause value (octet 3) | |||||
| Bits | |||||
| 4 | 3 | 2 | 1 | ||
| 0 | 0 | 0 | 0 | S-NSSAI not available in the current PLMN or SNPN | |
| 0 | 0 | 0 | 1 | S-NSSAI not available in the current registration area | |
| 0 | 0 | 1 | 0 | S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization | |
| All other values are reserved. | |||||
| Slice/service type (SST) (octet 4) | |||||
| This field contains the 8 bit SST value. The coding of the SST value part is defined in 3GPP TS 23.003 [4]. (NOTE 2) | |||||
| Slice differentiator (SD) (octet 5 to octet 7) | |||||
| This field contains the 24 bit SD value. The coding of the SD value part is defined in 3GPP TS 23.003 [4]. (NOTE 3) | |||||
| NOTE 0: The number of rejected S-NSSAI(s) shall not exceed eight.NOTE 1: If octet 5 is included, then octet 6 and octet 7 shall be included.NOTE 2: If the Cause value is "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization", this field shall contain the 8 bit SST value of an S-NSSAI in the S-NSSAI(s) of the HPLMN.NOTE 3: If the Cause value is "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization", this field, if included, shall contain the 24 bit SD value of an S-NSSAI in the S-NSSAI(s) of the HPLMN. |