Content for TS 24.501 Word version: 18.0.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.75 Extended rejected NSSAI
9.11.3.76 UE request type
9.11.3.77 Paging restriction
9.11.3.79 NID
9.11.3.80 PEIPS assistance information
9.11.3.81 5GS additional request result
9.11.3.82 NSSRG information
9.11.3.83 List of PLMNs to be used in disaster condition
9.11.3.84 Registration wait range
9.11.3.85 PLMN identity
9.11.3.86 Extended CAG information list
9.11.3.87 NSAG information
9.11.3.88 ProSe relay transaction identity
9.11.3.89 Relay key request parameters
9.11.3.90 Relay key response parameters
9.11.3.91 Priority indicator
...
...
9.11.3.75 Extended rejected NSSAI |R17| p. 823
The purpose of the Extended rejected NSSAI information element is to identify a collection of rejected S-NSSAIs if UE supports extended rejected NSSAI.
The Extended rejected NSSAI information element is coded as shown in Figure 9.11.3.75.1, Figure 9.11.3.75.2 and Table 9.11.3.75.1.
The Extended rejected NSSAI is a type 4 information element with a minimum length of 5 octets and a maximum length of 90 octets.
| Value part of the Extended rejected NSSAI information element (octet 3 to v) | |
| The value part of the Extended rejected NSSAI information element consists of one or more partial extended rejected NSSAI lists. The length of each partial extended rejected NSSAI list can be determined from the 'type of list' field and the 'number of elements' field in the first octet of the partial extended rejected NSSAI list. Each rejected S-NSSAI consists of one S-NSSAI and an associated cause value. Each rejected S-NSSAI also includes the mapped HPLMN S-NSSAI if available. 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. | |
| Partial extended rejected NSSAI list: | |
| Number of elements (octet 3, bits 1 to 4) | |
| Bits
4 3 2 1 | |
| 0 0 0 0 | 1 element |
| 0 0 0 1 | 2 element |
| … | |
| 0 1 1 0 | 7 element |
| 0 1 1 1 | 8 element |
| All other values are unused and shall be interpreted as 8, if received by the UE. | |
| Type of list (octet 3, bits 5 to 7) (NOTE 7) | |
| Bits
7 6 5 | |
| 0 0 0 | list of S-NSSAIs without any associated back-off timer value |
| 0 0 1 | list of S-NSSAIs with one associated back-off timer value that applies to all S-NSSAIs in the list |
| All other values are reserved. Bit 8 of octet 3 is spare and shall be coded as zero. | |
| Back-off timer value (octet 4): | |
| Back-off timer value is coded as the value part of GPRS timer 3 in subclause 10.5.7.4a in TS 24.008. | |
| Rejected S-NSSAI: | |
| Cause value (octet 4) | |
| 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 |
| 0 0 1 1 | S-NSSAI not available due to maximum number of UEs reached |
| All other values are reserved. | |
| Slice/service type (SST) (octet 5) | |
| This field contains the 8 bit SST value. The coding of the SST value part is defined in TS 23.003. (NOTE 5) | |
| Slice differentiator (SD) (octet 6 to octet 8) | |
| This field contains the 24 bit SD value. The coding of the SD value part is defined in TS 23.003. (NOTE 6) If the SST encoded in octet 4 is not associated with a valid SD value, and the sender needs to include a mapped HPLMN SST (octet 8) and a mapped HPLMN SD (octets 9 to 11), then the sender shall set the SD value (octets 5 to 7) to "no SD value associated with the SST". | |
| mapped HPLMN Slice/service type (SST) (octet 9) | |
| This field contains the 8 bit SST value of an S-NSSAI in the S-NSSAI(s) of the HPLMN to which the SST value is mapped. The coding of the SST value part is defined in TS 23.003. | |
| mapped HPLMN Slice differentiator (SD) (octet 10 to octet 12) | |
| This field contains the 24 bit SD value of an S-NSSAI in the S-NSSAI(s) of the HPLMN to which the SD value is mapped. The coding of the SD value part is defined in TS 23.003. | |
|
NOTE 0:
The number of rejected S-NSSAI(s) shall not exceed eight.
NOTE 1:
Octet 4 and octet 5 shall always be included.
NOTE 2:
If the octet 6 is included, then octet 7 and octet 8 shall be included.
NOTE 3:
If the octet 9 is included, then octets 10, 11, and 12 may be included.
NOTE 4:
If the octet 10 is included, then octet 11 and octet 12 shall be included.
NOTE 5:
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 and octets 9, 10, 11, and 12 shall not be included.
NOTE 6:
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 24 bit SD value of an S-NSSAI in the S-NSSAI(s) of the HPLMN and octets 9, 10, 11, and 12 shall not be included.
NOTE 7:
The partial extended rejected NSSAI with type of list = 001 shall only be used for rejected S-NSSAI(s) with the rejection cause "S-NSSAI not available due to maximum number of UEs reached".
|
|
9.11.3.76 UE request type |R17| p. 827
9.11.3.77 Paging restriction |R17| p. 827
The purpose of the Paging restriction information element is to request the network to restrict paging.
The Paging restriction information element is coded as shown in Figure 9.11.3.77.1, Figure 9.11.3.77.2 and Table 9.11.3.77.1.
The Paging restriction is a type 4 information element with a minimum length of 3 octets and a maximum length of 35 octets.
| Paging restriction type (bits 4 to 1 of octet 3) | |
| Bits
4 3 2 1 | |
| 0 0 0 0 | reserved |
| 0 0 0 1 | All paging is restricted |
| 0 0 1 0 | All paging is restricted except for voice service |
| 0 0 1 1 | All paging is restricted except for specified PDU session(s) |
| 0 1 0 0 | All paging is restricted except for voice service and specified PDU session(s) |
| All other values are reserved. Bits 5 to 8 of octet 3 are spare and shall be coded as zero. | |
| PSI(x) (bits 8 to 1 of octet 4 and octet 5): | |
| This field indicates the PDU session identity of the PDU session for which paging is restricted. | |
| PSI(0): (bit 1 of octet 4) | |
| Spare and shall be coded as zero. | |
| PSI(1) - PSI(15): | |
| 0 | indicates that paging is restricted for the PDU session associated with the PDU session identity. |
| 1 | indicates that paging is not restricted for the PDU session associated with the PDU session identity. |
| All bits in octet 6 to 35 are spare and shall be coded as zero, if the respective octet is included in the information element. | |
9.11.3.78 Void
9.11.3.79 NID |R17| p. 828
9.11.3.80 PEIPS assistance information |R17| p. 828
The purpose of the PEIPS assistance information, information element is to transfer the required assistance information to indicate the paging subgroup used when paging the UE.
The coding of the information element allows combining different types of PEIPS assistance information.
The PEIPS assistance information, information element is coded as shown in Figure 9.11.3.80.1, Figure 9.11.3.80.2, Figure 9.11.3.80.3 and Table 9.11.3.80.1.
The PEIPS assistance information is a type 4 information element, with a minimum length of 3 octets.
| Value part of the PEIPS assistance information information element (octets 3 to n) The value part of the PEIPS assistance information information element consists of one or several types of PEIPS assistance information. PEIPS assistance information type: | |
| Type of information (octet 1) | |
| Bits
8 7 6 | |
| 0 0 0 | Paging subgroup ID |
| 0 0 1 | UE paging probability information |
| All other values are reserved. | |
| Paging subgroup ID value: (octet 1, bits 1-5) | |
| This field contains the value (in decimal) of paging subgroup ID that is assigned by the AMF for paging the UE. This field has a valid range of values from (0-7). All other values are reserved and shall be interpreted as 0 by this version of the protocol. | |
| UE paging probability information value: (octet 1, bits 1-5) | |
| This field contains the value of UE paging probability information provided by the UE to the AMF. It represents the probability of the UE receiving the paging. | |
| Bits
5 4 3 2 1 | UE paging probability information value |
| 0 0 0 0 0 | p00 (UE calculated paging probability is 0%) |
| 0 0 0 0 1 | p05 (UE calculated paging probability > 0% and ≤ 5%) |
| 0 0 0 1 0 | p10 (UE calculated paging probability > 5% and ≤ 10%) |
| 0 0 0 1 1 | p15 (UE calculated paging probability > 10% and ≤ 15%) |
| 0 0 1 0 0 | p20 (UE calculated paging probability > 15% and ≤ 20%) |
| 0 0 1 0 1 | p25 (UE calculated paging probability > 20% and ≤ 25%) |
| 0 0 1 1 0 | p30 (UE calculated paging probability > 25% and ≤ 30%) |
| 0 0 1 1 1 | p35 (UE calculated paging probability > 30% and ≤ 35%) |
| 0 1 0 0 0 | p40 (UE calculated paging probability > 35% and ≤ 40%) |
| 0 1 0 0 1 | p45 (UE calculated paging probability > 40% and ≤ 45%) |
| 0 1 0 1 0 | p50 (UE calculated paging probability > 45% and ≤ 50%) |
| 0 1 0 1 1 | p55 (UE calculated paging probability > 50% and ≤ 55%) |
| 0 1 1 0 0 | p60 (UE calculated paging probability > 55% and ≤ 60%) |
| 0 1 1 0 1 | p65 (UE calculated paging probability > 60% and ≤ 65%) |
| 0 1 1 1 0 | p70 (UE calculated paging probability > 65% and ≤ 70%) |
| 0 1 1 1 1 | p75 (UE calculated paging probability > 70% and ≤ 75%) |
| 1 0 0 0 0 | p80 (UE calculated paging probability > 75% and ≤ 80%) |
| 1 0 0 0 1 | p85 (UE calculated paging probability > 80% and ≤ 85%) |
| 1 0 0 1 0 | p90 (UE calculated paging probability > 85% and ≤ 90%) |
| 1 0 0 1 1 | p95 (UE calculated paging probability > 90% and ≤ 95%) |
| 1 0 1 0 0 | p100 (UE calculated paging probability > 95% and ≤ 100%) |
| All other values shall be interpreted as 10100 by this version of the protocol. | |
9.11.3.81 5GS additional request result |R17| p. 830
The purpose of the 5GS additional request result information element is to inform the UE about the result of additional request.
The 5GS additional request result information element is coded as shown in Figure 9.11.3.81.1 and Table 9.11.3.81.1.
The 5GS additional request result is a type 4 information element with a length of 3 octets.
| Paging restriction decision (PRD) (bits 2 to 1 of octet 3) | |
| Bits
2 1 | |
| 0 0 | no additional information |
| 0 1 | paging restriction is accepted |
| 1 0 | paging restriction is rejected |
| All other values are reserved. | |
| Bits 3 to 8 of octet 3 are spare and shall be coded as zero. | |
9.11.3.82 NSSRG information |R17| p. 831
The purpose of the NSSRG information information element is to identify one or more NSSRG values associated with each of the HPLMN S-NSSAIs in a configured NSSAI.
The NSSRG information information element is coded as shown in Figure 9.11.3.82.1, Figure 9.11.3.82.2 and Table 9.11.3.82.1.
The NSSRG information is a type 6 information element with minimum length of 7 octets and maximum length of 65538 octets.
| Value part of the NSSRG information information element (octet 4 to v) | |
| The value part of the NSSRG information information element consists of one or more NSSRG values for each S-NSSAI in the Configured NSSAI IE. | |
| S-NSSAI value (octet 5 to w) (see NOTE 2) | |
| S-NSSAI value is coded as the length and value part of S-NSSAI information element as specified in subclause 9.11.2.8 starting with the second octet. See NOTE 1. | |
| NSSRG value for the S-NSSAI (octet w+1) | |
| This field contains the 8 bit NSSRG value. | |
|
NOTE 1:
If a mapped HPLMN SST is included in a S-NSSAI value, then the NSSRG value(s) are associated with the Mapped HPLMN SST, and the Mapped HPLMN SD, if included.
NOTE 2:
The NSSRG information IE shall contain the complete set of S-NSSAI(s) included in the configured NSSAI.
|
|
9.11.3.83 List of PLMNs to be used in disaster condition |R17| p. 832
The purpose of the list of PLMNs to be used in disaster condition information element is to provide the "list of PLMN(s) to be used in disaster condition" associated with the serving PLMN to the UE.
The list of PLMNs to be used in disaster condition information element is coded as shown in Figure 9.11.3.83.1 and Figure 9.11.3.83.2 and Table 9.11.3.83.1.
The list of PLMNs to be used in disaster condition is a type 4 information element, with a minimum length of 2 octets.
| MCC, Mobile country code (octet q+1 and bits 1 to 4 octet q+2) | |
| 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 q+2 and octet q+3) | |
| 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 q+2 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 TS 24.008. | |
|
NOTE:
The PLMN IDs are provided in decreasing order of priority, i.e. PLMN ID 1 indicates highest priority and PLMN ID n indicates lowest priority.
|
|
9.11.3.84 Registration wait range |R17| p. 833
The purpose of the registration wait range information element is to provide the disaster roaming wait range or the disaster return wait range to the UE.
The registration wait range information element is coded as shown in Figure 9.11.3.84.1 and Table 9.11.3.84.1.
The registration wait range is a type 4 information element, with a length of 4 octets.
| Minimum registration wait time (octet 3) | |
| The minimum registration wait time contains the minimum duration of the registration wait time, encoded as octet 2 of the GPRS timer information element (see TS 24.008, subclause 10.5.7.3). | |
| Maximum registration wait time (octet 4) | |
| The maximum registration wait time contains the maximum duration of the registration wait time, encoded as octet 2 of the GPRS timer information element (see TS 24.008, subclause 10.5.7.3). | |
9.11.3.85 PLMN identity |R17| p. 833
The purpose of the PLMN identity information element is to provide a PLMN identity.
The PLMN identity information element is coded as shown in Figure 9.11.3.85.1, and Table 9.11.3.85.1.
The PLMN identity is a type 4 information element.
| MCC, Mobile country code (octet 3, octet 4 bits 1 to 4) | |
| The MCC field is coded as in ITU-T Recommendation E.212 [42], Annex A. | |
| MNC, Mobile network code (octet 4 bits 5 to 8, octet 5) | |
| 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 4 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 TS 24.008. | |
9.11.3.86 Extended CAG information list |R17| p. 834
The purpose of the Extended CAG information list information element is to provide "CAG information list" or to delete the "CAG information list" at the UE.
The Extended CAG information list information element is coded as shown in Figure 9.11.3.86.1 and Figure 9.11.3.86.2 and Table 9.11.3.86.1.
The Extended CAG information list is a type 6 information element, with a minimum length of 3 octets.
| Value part of the Extended CAG information list information element (octet 4 to h) | |
| The value part of the Extended CAG information list information element consists of one or more entries. | |
| Entry n: | |
| Length of entry contents (octet q and q+1) | |
| MCC, Mobile country code (octet q+2 and bits 1 to 4 octet q+3) | |
| 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 q+3 and octet q+4) | |
| 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 q+2 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 TS 24.008. | |
| Indication that the UE is only allowed to access 5GS via CAG cells (CAGonly) (bit 1 of octet q+5) | |
| Bit
1 | |
| 0 | "Indication that the UE is only allowed to access 5GS via CAG cells" is not set (i.e., the UE is allowed to access 5GS via non-CAG cells) |
| 1 | "Indication that the UE is only allowed to access 5GS via CAG cells" is set (i.e., the UE is not allowed to access 5GS via non-CAG cells) |
| CAG-ID m (octet q+4m+2 to octet q+4m+5) | |
| This field contains the 32 bit CAG-ID. The coding of the CAG-ID is defined as the CAG-Identifier in TS 23.003. | |
|
NOTE 1:
The Length of Extended CAG information list contents shall be 0 if no subscription data for CAG information list exists.
NOTE 2:
The Length of entry contents shall be 4 if there is no allowed CAG-ID for the PLMN.
NOTE 3:
For a given PLMN ID, there shall be up to one Entry containing the MCC value and the MNC value of the PLMN ID.
|
|
9.11.3.87 NSAG information |R17| p. 836
The purpose of the NSAG information information element is to provide NSAG information to the UE.
The NSAG information information element is coded as shown in Figure 9.11.3.87.1, Figure 9.11.3.87.2, Figure 9.11.3.87.3 and Table 9.11.3.87.1.
The NSAG information information element can contain a maximum of 32 NSAG entries.
The NSAG information is a type 6 information element, with a minimum length of 10 octets.
| NSAG part of the NSAG information information element (octet 4 to m) | |
| Each entry of the NSAG information information element consists of one NSAG in the NSAG information IE. | |
| NSAG identifier(octet 6) | |
| NSAG identifier field contains an 8 bits NSAG ID value. | |
| S-NSSAI list of NSAG (octet 7 to j) | |
| S-NSSAI list of NSAG field consists of one or more S-NSSAIs in the configured NSSAI. Each S-NSSAI in S-NSSAI list of NSAG field is coded as the length and value part of S-NSSAI information element as specified in subclause 9.11.2.8 starting with the second octet, without the mapped HPLMN SST field and without the mapped HPLMN SD field. | |
| NSAG priority (octet j+1) | |
| The NSAG priority field indicates the priority of NSAG for cell reselection (see TS 38.304) and random access (see TS 38.321). | |
| TAI list (octet j+2 to m) | |
| The TAI list field is coded as the length and value part of the 5GS tracking area identity list IE defined in subclause 9.11.3.9 starting with the second octet. | |
9.11.3.88 ProSe relay transaction identity |R17| p. 837
The purpose of the ProSe relay transaction identity (PRTI) information element is to uniquely identify an authentication and key agreement procedure for 5G ProSe UE-to-network relay. The PRTI allows distinguishing up to 254 different bi-directional messages.
The ProSe relay transaction identity information element is coded as shown in Figure 9.11.3.88.1 and Table 9.11.3.88.1.
The ProSe relay transaction identity is a type 3 information element with a length of 2 octets.
| ProSe relay transaction identity value (octet 2) | |
|
Bits
8 7 6 5 4 3 2 1 | |
| 0 0 0 0 0 0 0 0 | No ProSe relay transaction identity assigned |
| 0 0 0 0 0 0 0 1 | |
| to | ProSe relay transaction identity value |
| 1 1 1 1 1 1 1 0 | |
| 1 1 1 1 1 1 1 1 | Reserved |
9.11.3.89 Relay key request parameters |R17| p. 837
The purpose of the relay key request parameters information element is to transport the parameters of the key request for 5G ProSe UE-to-network relay as specified in TS 33.503.
The relay key request parameters information element is coded as shown in Figure 9.11.3.89.1, Figure 9.11.3.89.2 and Table 9.11.3.89.1.
The relay key request parameters is a type 6 information element.
| Relay service code (octet 4 to 6) | |
| The relay service code contains 24-bit relay service code as defined in TS 24.554. | |
| Nonce_1 (octet 7 to 22) | |
| Nonce_1 is the 128-bit nonce value as defined in TS 24.554. | |
| Remote UE ID type (RUIT) (octet 23, bit 1) | |
| Bit
1 | |
| 0 | SUCI |
| 1 | 5GPRUK ID |
| Remote UE ID (octet 23+1 to n) | |
| Remote UE ID indicates the value of the 5G ProSe remote UE identity. If the Remote UE ID type is set to SUCI, the Remote UE ID is coded as 5GS mobile identity IE starting from octet 2 with the Type of identity set to "SUCI" (see subclause 9.11.3.4). If the Remote UE ID type is set to 5GPRUK ID, the Remote UE ID is coded as the 5GPRUK ID as defined in TS 33.503.. | |
9.11.3.90 Relay key response parameters |R17| p. 838
The purpose of the relay key response parameters information element is to transport the parameters of the key response for 5G ProSe UE-to-network relay as specified in TS 33.503.
The relay key response parameters information element is coded as shown in Figure 9.11.3.90.1 and Table 9.11.3.90.1.
The relay key response parameters is a type 6 information element.
| 5GPRUK ID indication (5GPII) (octet 4, bit 1) | |
| Bit
1 | |
| 0 | 5GPRUK ID not included |
| 1 | 5GPRUK ID included |
| Key KNR_ProSe (octet 5 to 36) | |
| Key KNR_ProSe contains a 256-bit root key that is established between the two entities that communicating using NR PC5 unicast link as defined in TS 33.503. | |
| Nonce_2 (octet 37 to 52) | |
| Nonce_2 is the 128-bit nonce value as defined in TS 24.554. | |
| 5GPRUK ID (octet 53 to m) | |
| The 5GPRUK ID is defined in TS 33.503. | |
9.11.3.91 Priority indicator |R17| p. 839
The purpose of the Priority indicator information element is to convey a priority indication to the UE.
The Priority indicator information element is coded as shown in Figure 9.11.3.91.1 and Table 9.11.3.91.1.
The Priority indicator is a type 1 information element.
| MPS indicator (MPSI) (octet 1, bit 1) | |
| Bit
1 | |
| 0 | Access identity 1 not valid |
| 1 | Access identity 1 valid |
| Bits 2, 3, 4 are spare and shall be coded as zero. | |
