3GPP 24.501 v20.0.0 — the document's own text
9.11.3.100 S-NSSAI location validity information
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 S-NSSAI location validity information information element is to provide the S-NSSAI location validity information to the UE.
The S-NSSAI location validity information information element is coded as shown in figures 9.11.3.100.1, 9.11.3.100.2, 9.11.3.100.3, and 9.11.3.100.4 and table 9.11.3.100.1.
The S-NSSAI location validity information information element can contain per-S-NSSAI location validity information for maximum 16 S-NSSAIs.
The S-NSSAI location validity information information is a type 6 information element with a minimum length of 17 octets and a maximum length of 38611 octets.
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| S-NSSAI location validity information information IEI | octet 1 | |||||||
| Length of S-NSSAI location validity information contents | octet 2octet 3 | |||||||
| Per-S-NSSAI location validity information for S-NSSAI 1 | octet 4octet a | |||||||
| Per-S-NSSAI location validity information for S-NSSAI 2 | octet (a+1)*octet b* | |||||||
| … | octet (b+1)*octet c* | |||||||
| Per-S-NSSAI location validity information for S-NSSAI n | octet (c+1)*octet d* |
Figure 9.11.3.100.1: S-NSSAI location validity information information element
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| Length of Per-S-NSSAI location validity information for S-NSSAI | octet 4octet 5 | |||||||
| S-NSSAI | octet 6octet e | |||||||
| NS-AoS | octet e+1octet a |
Figure 9.11.3.100.2: Per-S-NSSAI location validity information for S-NSSAI
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| Number of NR CGIs | octet (e+1)octet (e+2) | |||||||
| NR CGI 1 | octet (e+3)octet (e+10) | |||||||
| NR CGI 2 | octet (e+11)*octet (e+18)* | |||||||
| … | octet (e+19)*octet f* | |||||||
| NR CGI w | octet (f+1)*octet a=(f+8)* |
Figure 9.11.3.100.3: NS-AoS
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| NR Cell ID | octet (e+3)octet (e+7) | |||||||
| MCC digit 2 | MCC digit 1 | octet (e+8) | ||||||
| MNC digit 3 | MCC digit 3 | octet (e+9) | ||||||
| MNC digit 2 | MNC digit 1 | octet (e+10) |
Figure 9.11.3.100.4: NR CGI
Table 9.11.3.100.1: S-NSSAI location validity information information element
| S-NSSAI (octet 6 to e)S-NSSAI value is coded as the length and value part of S-NSSAI information element as specified in clause 9.11.2.8 starting with the second octet. |
|---|
| NS-AoS (octet e+1 to octet a) |
| NS-AoS field consists of the Number of NR CGIs field and at least one NR CGI. |
| Number of NR CGIs (octet e+1 to octet e+2) |
| The field indicates the number of NR CGIs included in octets e+3 to octet a. (NOTE). |
| NR CGI (octet e+3 to e+10) |
| The NR CGI globally identifies an NR cell. It contains the NR Cell ID and the PLMN ID of that cell. |
| NR Cell ID (octet e+3 to e+7) |
| The NR Cell ID consists of 36 bits identifying an NR Cell ID as specified in clause 9.3.1.7 of 3GPP TS 38.413 [31], in hexadecimal representation. Bit 8 of octet e+3 is the most significant bit and bit 5 of octet e+7 is the least significant bit. Bits 1 to 4 of octet e+7 are spare and shall be coded as zero. |
| MCC, Mobile country code (octet e+8 and bits 1 to 4 octet e+9)The MCC field is coded as in ITU-T Recommendation E.212 [42], annex A. |
| MNC, Mobile network code (bits 5 to 8 of octet e+9 and octet e+10)The coding of this field is the responsibility of each administration but BCD coding shall be used. The MNC shall consist of 2 or 3 digits. If a network operator decides to use only two digits in the MNC, bits 5 to 8 of octet e+9 shall be coded as "1111". |
| The MCC and MNC digits are coded as octets 6 to 8 of the Temporary mobile group identity IE in figure 10.5.154 of 3GPP TS 24.008 [12]. |
| NOTE: In this version of the specification, the maximum number of NR CGIs is 300. |