Tech-invite  3GPPspace  IETF RFCs  SIP
index  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 24.501  Word version:  18.2.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… 
9.11.3.50 Service type  9.11.3.50A SMS indication  9.11.3.51 SOR transparent container  9.11.3.51A Supported codec list  9.11.3.52 Time zone  9.11.3.53 Time zone and time 
...

 

9.11.3.50  Service type  p. 832

The purpose of the service type information element is to specify the purpose of the service request procedure.
The service type is a type 1 information element.
The service type information element is coded as shown in Figure 9.11.3.50.1 and Table 9.11.3.50.1.
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.50.1: Service type information element
Figure 9.11.3.50.1: Service type information element
Up
Service type value (octet 1)
Bits
4 3 2 1
0 0 0 0signalling
0 0 0 1data
0 0 1 0mobile terminated services
0 0 1 1emergency services
0 1 0 0emergency services fallback
0 1 0 1high priority access
0 1 1 0elevated signalling
0 1 1 1unused; shall be interpreted as "signalling", if received by the network
1 0 0 0unused; shall be interpreted as "signalling", if received by the network
1 0 0 1unused; shall be interpreted as "data", if received by the network
1 0 1 0unused; shall be interpreted as "data", if received by the network
1 0 1 1unused; shall be interpreted as "data", if received by the network
All other values are reserved.
Up

9.11.3.50A  SMS indication  p. 832

The purpose of the SMS indication information element is to indicate that the ability for the UE to use SMS over NAS has changed.
The SMS indication information element is coded as shown in Figure 9.11.3.50A.1 and Table 9.11.3.50A.1.
The SMS indication is a type 1 information element.
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.50A.1: SMS indication
Figure 9.11.3.50A.1: SMS indication
Up
SMS availability indication (SAI) (octet 1)
Bit
1
0SMS over NAS not available
1SMS over NAS available
Bits 2, 3 and 4 are spare and shall be coded as zero.
Up

9.11.3.51  SOR transparent container  p. 833

The purpose of the SOR transparent container information element in the REGISTRATION ACCEPT message is to provide the list of preferred PLMN/access technology combinations (or HPLMN indication that 'no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided'), or a secured packet (see TS 23.122 Annex C) and optional indication of an acknowledgement request, SOR-CMCI, request the storage of the received SOR-CMCI in the ME, and SOR-SNPN-SI (or subscribed SNPN or HPLMN indication that 'no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided'). The purpose of the SOR transparent container information element in the REGISTRATION COMPLETE message is to indicate the UE acknowledgement of successful reception of the SOR transparent container IE in the REGISTRATION ACCEPT message as well as to indicate the ME support of SOR-CMCI and the ME support of SOR-SNPN-SI.
The SOR transparent container information element is coded as shown in Figure 9.11.3.51.1, Figure 9.11.3.51.2, Figure 9.11.3.51.3, Figure 9.11.3.51.4, Figure 9.11.3.51.5, Figure 9.11.3.51.6, Figure 9.11.3.51.7, Figure 9.11.3.51.8, Figure 9.11.3.51.9, Figure 9.11.3.51.10, Figure 9.11.3.51.11, Figure 9.11.3.51.12, Figure 9.11.3.51.13, Table 9.11.3.51.1, Table 9.11.3.51.2, Table 9.11.3.51.3, Table 9.11.3.51.4, Table 9.11.3.51.5 and Table 9.11.3.51.6.
The SOR transparent container is a type 6 information element with a minimum length of 20 octets.
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.51.1: SOR transparent container information element for list type with value
Figure 9.11.3.51.1: SOR transparent container information element for list type with value "0" and SOR data type with value "0"
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.51.2: SOR transparent container information element for list type with value
Figure 9.11.3.51.2: SOR transparent container information element for list type with value "1", SOR data type with value "0", and additional parameters with value "0"
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.51.2A: SOR transparent container information element for list type with value
Figure 9.11.3.51.2A: SOR transparent container information element for list type with value "1", SOR data type with value "0", additional parameters with value "1"
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.51.3: PLMN ID and access technology list (m=22+5*n)
Figure 9.11.3.51.3: PLMN ID and access technology list (m=22+5*n)
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.51.4: SOR transparent container information element for SOR data type with value
Figure 9.11.3.51.4: SOR transparent container information element for SOR data type with value "1"
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.51.5: SOR header for SOR data type with value
Figure 9.11.3.51.5: SOR header for SOR data type with value "0"
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.51.6: SOR header for SOR data type with value
Figure 9.11.3.51.6: SOR header for SOR data type with value "1"
Up
SOR-MAC-IAUSF (see NOTE 1), SOR-MAC-IUE (see NOTE 2) and CounterSOR (see NOTE 1) are coded as specified in TS 33.501.
SOR data type (octet 4, bit 1)
0The SOR transparent container carries steering of roaming information.
1The SOR transparent container carries acknowledgement of successful reception of the steering of roaming information.
List indication (octet 4, bit 2) (see NOTE 1 and NOTE 5)
0 HPLMN indication that 'no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided'
1list of preferred PLMN/access technology combinations is provided
List type (octet 4, bit 3) (see NOTE 1)
0The list type is a secured packet.
1 The list type is a "PLMN ID and access technology list".
Acknowledgement (ACK) value (octet 4, bit 4) (see NOTE 1)
0acknowledgement not requested
1acknowledgement requested
Additional parameters (AP) value (octet 4, bit 5)
0Additional parameters not included
1Additional parameters included (see NOTE 3)
If the SOR data type is set to value "0", the list type bit is set to value "1", and the additional parameters bit is set to value "1" then:
  • the octet o is present.
  • if the list indication bit is set to "0" then the PLMN ID and access technology list field and the length of PLMN ID and access technology list field are absent.
  • if the list indication bit is set to "1" then the PLMN ID and access technology list field and the length of PLMN ID and access technology list field are present.
The secure packet is coded as specified in TS 31.115. (see NOTE 1)
The PLMN ID and access technology list consists of PLMN ID and access technology identifier and are coded as specified in subclause 4.2.5 of TS 31.102. The PLMN ID and access technology identifier are provided in decreasing order of priority, i.e. PLMN ID 1 indicates highest priority and PLMN ID n indicates lowest priority. The PLMN ID and access technology list contains at minimum zero and at maximum 16 (decimal) PLMN IDs and access technology identifiers. (see NOTE 1)
ME support of SOR-CMCI indicator (MSSI) value (octet 4, bit 2) (see NOTE 2, NOTE 4)
0SOR-CMCI not supported by the ME
1SOR-CMCI supported by the ME
ME support of SOR-SNPN-SI indicator (MSSNPNSI) value (octet 4, bit 3) (see NOTE 2, NOTE 6)
0SOR-SNPN-SI not supported by the ME
1SOR-SNPN-SI supported by the ME
MS support of SOR-SNPN-SI-LS indicator (MSSNPNSILS) value (octet 4, bit 4) (see NOTE 2)
0SOR-SNPN-SI-LS not supported by the ME
1SOR-SNPN-SI-LS supported by the ME
SOR-CMCI indicator (SI) value (octet o, bit 1)
0SOR-CMCI absent
1SOR-CMCI present
If the SOR-CMCI indicator bit is set to "SOR-CMCI present", the SOR-CMCI field is present. If the SI bit is set to "SOR-CMCI absent", the SOR-CMCI field is absent.
Store SOR-CMCI in ME indicator (SSCMI) value (octet o, bit 2)
0Do not store SOR-CMCI in ME
1Store SOR-CMCI in ME
SOR-CMCI (octet o+1 to octet p)
The SOR-CMCI field is coded according to Figure 9.11.3.51.7 and Table 9.11.3.51.2.
SOR-SNPN-SI indicator (SSSI) value (octet o, bit 3)
0 subscribed SNPN or HPLMN indication that 'no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided'
1SOR-SNPN-SI present
If the SSSI bit is set to "SOR-SNPN-SI present", the SOR-SNPN-SI field is present. If the SSSI bit is set to "subscribed SNPN or HPLMN indication that 'no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided'", the SOR-SNPN-SI is absent.
NOTE 1:
This bit or field applies for SOR header with SOR data type with value "0".
NOTE 2:
This bit or field applies for SOR header with SOR data type with value "1".
NOTE 3:
Additional parameters can be set to value "1" only when the ME supports SOR-CMCI or SOR-SNPN-SI, and the list type bit is set to value "1".
NOTE 4:
The "SOR-CMCI supported by the ME" is not set by a UE compliant to an earlier release of the specification.
NOTE 5:
This bit or field applies for SOR header with list type with value "1".
NOTE 5:
The "SOR-SNPN-SI supported by the ME" may only be set by a UE which supports access to an SNPN using credentials from a credentials holder and which is not operating in SNPN access operation mode.
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.51.7: SOR-CMCI
Figure 9.11.3.51.7: SOR-CMCI
Up
SOR-CMCI rule:
The SOR-CMCI rule is coded according to Figure 9.11.3.51.8 and Table 9.11.3.51.3.
If the length of SOR-CMCI contents field indicates a length bigger than indicated in Figure 9.11.3.51.7, receiving entity shall ignore any superfluous octets located at the end of the SOR-CMCI.
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.51.8: SOR-CMCI rule
Figure 9.11.3.51.8: SOR-CMCI rule
Up
Tsor-cm timer value
The Tsor-cm timer value field is coded according to octet 2 of the GPRS timer information element as specified in subclause 10.5.7.3 of TS 24.008 and indicates the Tsor-cm timer value. When the unit field of the Tsor-cm timer value field indicates that the timer is deactivated, the receiving entity shall consider that Tsor-cm timer value is set to the infinity value.
Criterion type
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 1DNN
0 0 0 0 0 0 1 0S-NSSAI SST
0 0 0 0 0 0 1 1S-NSSAI SST and SD
0 0 0 0 0 1 0 0IMS registration related signalling
0 0 0 0 0 1 0 1MMTEL voice call
0 0 0 0 0 1 1 0MMTEL video call
0 0 0 0 0 1 1 1SMS over NAS or SMSoIP
0 0 0 0 1 0 0 0SOR security check not successful
1 1 1 1 1 1 1 1match all
All other values are spare.
The receiving entity shall ignore SOR-CMCI rule with criterion of criterion type set to a spare value.
For "DNN", the criterion value field shall be encoded as a DNN length-value pair field.
For "S-NSSAI SST", the criterion value field shall be encoded as one octet SST field.
For "S-NSSAI SST and SD", the criterion value field shall be encoded as a sequence of one octet SST field and three octets SD field. The SST field shall be transmitted first.
The DNN length-value pair field shall be encoded as a sequence of one octet DNN value length field and a DNN value field. The DNN value length field shall be transmitted first. The DNN value length field indicates the length in octets of the DNN value field. The DNN value field contains an APN as specified in TS 23.003.
The SST field contains SST of HPLMN's S-NSSAI.
The SD field contains SD of HPLMN's S-NSSAI.
For "match all", "SOR security check not successful", "IMS registration related signalling", "MMTEL voice call", "MMTEL video call", and "SMS over NAS or SMSoIP", the criterion value field is zero octets long.
If the length of SOR-CMCI rule contents field indicates a length bigger than indicated in Figure 9.11.3.51.8, receiving entity shall ignore any superfluous octets located at the end of the SOR-CMCI rule.
The UE applies SOR-CMCI rules as described in TS 23.122 Annex C.
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.51.9: SOR-SNPN-SI
Figure 9.11.3.51.9: SOR-SNPN-SI
Up
CH controlled prioritized list of preferred SNPNs indicator (CLSI) value (octet p+3, bit 1)
0CH controlled prioritized list of preferred SNPNs absent
1CH controlled prioritized list of preferred SNPNs present
If the CLSI bit is set to "CH controlled prioritized list of preferred SNPNs present", the CH controlled prioritized list of preferred SNPNs field is present. If the CLSI bit is set to "CH controlled prioritized list of preferred SNPNs absent", the CH controlled prioritized list of preferred SNPNs field is absent.
CH controlled prioritized list of GINs indicator (CLGI) value (octet p+3, bit 2)
0CH controlled prioritized list of GINs absent
1CH controlled prioritized list of GINs present
If the CLGI bit is set to "CH controlled prioritized list of GINs present", the CH controlled prioritized list of GINs field is present. If the CLGI bit is set to "CH controlled prioritized list of GINs absent", the CH controlled prioritized list of GINs field is absent.
CH controlled prioritized list of preferred SNPNs for access for localized services in SNPN indicator (CLSI2) value (octet p+3, bit 3)
0CH controlled prioritized list of preferred SNPNs for access for localized services in SNPN absent
1CH controlled prioritized list of preferred SNPNs for access for localized services in SNPN present
If the CLSI2 bit is set to "CH controlled prioritized list of preferred SNPNs for access for localized services in SNPN present", the CH controlled prioritized list of preferred SNPNs field is present. If the CLSI2 bit is set to "CH controlled prioritized list of preferred SNPNs for access for localized services in SNPN absent", the CH controlled prioritized list of preferred SNPNs field is absent.
CH controlled prioritized list of GINs for access for localized services in SNPN indicator (CLGI2) value (octet p+3, bit 4)
0CH controlled prioritized list of GINs for access for localized services in SNPN absent
1CH controlled prioritized list of GINs for access for localized services in SNPN present
If the CLGI2 bit is set to "CH controlled prioritized list of GINs for access for localized services in SNPN present", the CH controlled prioritized list of GINs field is present. If the CLGI2 bit is set to "CH controlled prioritized list of GINs for access for localized services in SNPN absent", the CH controlled prioritized list of GINs field is absent.
If the length of SOR-SNPN-SI contents field indicates a length bigger than indicated in Figure 9.11.3.51.9, receiving entity shall ignore any superfluous octets located at the end of the SOR-SNPN-SI.
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.51.10: CH controlled prioritized list of preferred SNPNs
Figure 9.11.3.51.10: CH controlled prioritized list of preferred SNPNs
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.51.10A: CH controlled prioritized list of preferred SNPNs for access for localized services
Figure 9.11.3.51.10A: CH controlled prioritized list of preferred SNPNs for access for localized services
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.51.10B: SNPN info
Figure 9.11.3.51.10B: SNPN info
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.51.11: SNPN identity
Figure 9.11.3.51.11: SNPN identity
Up
Mobile country code (MCC):
The MCC field is coded as in ITU-T Recommendation E.212 [42], annex A.
Mobile network code (MNC):
The coding of MNC 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, MNC digit 3 shall be coded as "1111".
NID assignment mode
NID assignment mode is coded as specified in TS 23.003.
NID value
NID value is coded as specified in TS 23.003.
Time indication (bit1 of octet p+8)
0Time validity information is not included
1Time validity information is included
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.51.12: CH controlled prioritized list of GINs
Figure 9.11.3.51.12: CH controlled prioritized list of GINs
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.51.12A: CH controlled prioritized list of GINs for access for localized services
Figure 9.11.3.51.12A: CH controlled prioritized list of GINs for access for localized services
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.51.12B: GIN info
Figure 9.11.3.51.12B: GIN info
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.3.51.13: GIN
Figure 9.11.3.51.13: GIN
Up
Mobile country code (MCC):
The MCC field is coded as in ITU-T Recommendation E.212 [42], annex A.
Mobile network code (MNC):
The coding of MNC 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, MNC digit 3 shall be coded as "1111".
NID assignment mode
NID assignment mode is coded as specified in TS 23.003.
NID value
NID value is coded as specified in TS 23.003.
Time indication (bit1 of octet t+5)
0Time validity information is not included
1Time validity information is included
Up

9.11.3.51A  Supported codec list |R16|  p. 845

See subclause 10.5.4.32 in TS 24.008.

9.11.3.52  Time zone  p. 845

See subclause 10.5.3.8 in TS 24.008.

9.11.3.53  Time zone and time  p. 845

See subclause 10.5.3.9 in TS 24.008.

Up   Top   ToC