Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 24.501  Word version:  19.1.1

Top   Top   Up   Prev   Next
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…   D.6.8   D.7…

 

9.11.3.75  Extended rejected NSSAI |R17|p. 987

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.
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.75.1: Extended rejected NSSAI information element
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.75.2: Partial extended rejected NSSAI list - type of list = 000
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.75.3: Partial extended rejected NSSAI list - type of list = 001
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.75.4: Rejected S-NSSAI
Up
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 01 element
0 0 0 12 element
0 1 1 07 element
0 1 1 18 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 0list of S-NSSAIs without any associated back-off timer value
0 0 1list 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 x) (NOTE 8)
Bits
4 3 2 1
0 0 0 0S-NSSAI not available in the current PLMN or SNPN
0 0 0 1S-NSSAI not available in the current registration area
0 0 1 0S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization
0 0 1 1S-NSSAI not available due to maximum number of UEs reached
All other values are reserved.
Slice/service type (SST) (octet x+1)
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 x+2 to octet x+4)
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 x+1 is not associated with a valid SD value, and the sender needs to include a mapped HPLMN SST (octet x+5) and a mapped HPLMN SD (octets x+6 to x+8), then the sender shall set the SD value (octets x+2 to x+4) to "no SD value associated with the SST".
mapped HPLMN Slice/service type (SST) (octet x+5)
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 x+6 to octet x+8)
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 x and octet x+1 shall always be included.
NOTE 2:
If the octet x+2 is included, then octet x+3 and octet x+4 shall be included.
NOTE 3:
If the octet x+5 is included, then octets x+6, x+7, and x+8 may be included.
NOTE 4:
If the octet x+6 is included, then octet x+7 and octet x+8 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 x+5, x+6, x+7, and x+8 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 x+5, x+6, x+7, and x+8 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".
NOTE 8:
Octet x can be 4 or 5.
Up

9.11.3.76  UE request type |R17|p. 991

9.11.3.77  Paging restriction |R17|p. 991

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.
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.77.1: Paging restriction information element for Paging restriction type =
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.77.2: Paging restriction information element for Paging restriction type =
Up
Paging restriction type (bits 4 to 1 of octet 3)
Bits
4 3 2 1
0 0 0 0reserved
0 0 0 1All paging is restricted
0 0 1 0All paging is restricted except for voice service
0 0 1 1All paging is restricted except for specified PDU session(s)
0 1 0 0All 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):
0indicates that paging is restricted for the PDU session associated with the PDU session identity.
1indicates 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.
Up

9.11.3.78Void

9.11.3.79  NID |R17|p. 992

9.11.3.80  PEIPS assistance information |R17|p. 992

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.
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.80.1: PEIPS assistance information information element
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.80.2: PEIPS assistance information type - type of information=
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.80.3: PEIPS assistance information type - type of information=
Up
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 0Paging subgroup ID
0 0 1UE 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 unused 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 0p00 (UE calculated paging probability is 0%)
0 0 0 0 1p05 (UE calculated paging probability > 0% and ≤ 5%)
0 0 0 1 0p10 (UE calculated paging probability > 5% and ≤ 10%)
0 0 0 1 1p15 (UE calculated paging probability > 10% and ≤ 15%)
0 0 1 0 0p20 (UE calculated paging probability > 15% and ≤ 20%)
0 0 1 0 1p25 (UE calculated paging probability > 20% and ≤ 25%)
0 0 1 1 0p30 (UE calculated paging probability > 25% and ≤ 30%)
0 0 1 1 1p35 (UE calculated paging probability > 30% and ≤ 35%)
0 1 0 0 0p40 (UE calculated paging probability > 35% and ≤ 40%)
0 1 0 0 1p45 (UE calculated paging probability > 40% and ≤ 45%)
0 1 0 1 0p50 (UE calculated paging probability > 45% and ≤ 50%)
0 1 0 1 1p55 (UE calculated paging probability > 50% and ≤ 55%)
0 1 1 0 0p60 (UE calculated paging probability > 55% and ≤ 60%)
0 1 1 0 1p65 (UE calculated paging probability > 60% and ≤ 65%)
0 1 1 1 0p70 (UE calculated paging probability > 65% and ≤ 70%)
0 1 1 1 1p75 (UE calculated paging probability > 70% and ≤ 75%)
1 0 0 0 0p80 (UE calculated paging probability > 75% and ≤ 80%)
1 0 0 0 1p85 (UE calculated paging probability > 80% and ≤ 85%)
1 0 0 1 0p90 (UE calculated paging probability > 85% and ≤ 90%)
1 0 0 1 1p95 (UE calculated paging probability > 90% and ≤ 95%)
1 0 1 0 0p100 (UE calculated paging probability > 95% and ≤ 100%)
All other values shall be interpreted as 10100 by this version of the protocol.
Up

9.11.3.81  5GS additional request result |R17|p. 994

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.
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.81.1: 5GS additional request result information element
Up
Paging restriction decision (PRD) (bits 2 to 1 of octet 3)
Bits
2 1
0 0no additional information
0 1paging restriction is accepted
1 0paging restriction is rejected
All other values are reserved.
Bits 3 to 8 of octet 3 are spare and shall be coded as zero.
Up

9.11.3.82  NSSRG information |R17|p. 995

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 4099 octets.
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.82.1: NSSRG information information element
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.82.2: NSSRG values for S-NSSAI
Up
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.
NOTE 3:
The number of NSSRG values associated with an S-NSSAI cannot exceed 16. If there are more than 16 NSSRG values for an S-NSSAI in the NSSRG information, then the UE shall retain only the first 16 NSSRG values and ignore the rest.
Up

9.11.3.83  List of PLMNs to be used in disaster condition |R17|p. 996

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.
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.83.1: List of PLMNs to be used in disaster condition information element
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.83.2: PLMN ID n
Up
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 Tempora