Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 24.501  Word version:  17.5.0

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…

 

9.11.3.75  Extended rejected NSSAI |R17|Word‑p. 762

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, Figure 9.11.3.75.1: Extended rejected NSSAI information element
Up
Reproduction of 3GPP TS 24.501, Figure 9.11.3.75.2: Partial extended rejected NSSAI list - type of list = 000
Up
Reproduction of 3GPP TS 24.501, Figure 9.11.3.75.3: Partial extended rejected NSSAI list - type of list = 001
Up
Reproduction of 3GPP TS 24.501, Figure 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 1 02 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 4)
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 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".
Up

9.11.3.76  UE request type |R17|Word‑p. 766

9.11.3.77  Paging restriction |R17|Word‑p. 766

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, Figure 9.11.3.77.1:	Paging restriction information element for Paging restriction type =
Up
Reproduction of 3GPP TS 24.501, Figure 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|Word‑p. 767

9.11.3.80  PEIPS assistance information |R17|Word‑p. 767

9.11.3.81  5GS additional request result |R17|Word‑p. 768

9.11.3.82  NSSRG information |R17|Word‑p. 769

9.11.3.83  List of PLMNs to be used in disaster condition |R17|Word‑p. 769

9.11.3.84  Registration wait range |R17|Word‑p. 770

9.11.3.85  PLMN identity |R17|Word‑p. 771


Up   Top   ToC