3GPP 24.501 v20.0.0 — the document's own text

9.11.3.51 SOR transparent container

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 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 3GPP TS 23.122 [5] annex C) and optional indication of an acknowledgement request, SOR-CMCI, request the storage of the received SOR-CMCI in the ME, 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'), and SOR-SNPN-SI-LS. 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, the ME support of SOR-SNPN-SI and the ME support of SOR-SNPN-SI-LS.

NOTE 1: When used in NAS transport procedure, the contents of the SOR transparent container information element in the Payload container IE of the DL NAS TRANSPORT message are used to provide the list of preferred PLMN/access technology combinations and optional indication of an acknowledgement request, SOR-CMCI, request the storage of the received SOR-CMCI in the ME, SOR-SNPN-SI, and SOR-SNPN-SI-LS. The contents of the SOR transparent container information element in the Payload container IE of the UL NAS TRANSPORT message are used to indicate the UE acknowledgement of successful reception of the SOR transparent container IE in the DL NAS TRANSPORT message as well as to indicate the ME support of SOR-CMCI, the ME support of SOR-SNPN-SI and the ME support of SOR-SNPN-SI-LS.

NOTE 2: The "Operator controlled signal threshold per access technology" content to update the USIM file EFOCST (see 3GPP TS 31.102 [22]) can be included in the secured packet of the SOR transparent container.

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.9A, figure 9.11.3.51.10, figure 9.11.3.51.11, figure 9.11.3.51.11A, figure 9.11.3.51.11B, figure 9.11.3.51.11C, figure 9.11.3.51.11D, figure 9.11.3.51.11E, figure 9.11.3.51.11F, figure 9.11.3.51.11G, figure 9.11.3.51.11H, figure 9.11.3.51.11I, 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.4A, 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.

8	7	6	5	4	3	2	1
SOR transparent container IEI	octet 1
Length of SOR transparent container contents	octet 2octet 3
SOR header	octet 4
SOR-MAC-IAUSF	octet 5-20
CounterSOR	octet 21-22
Secured packet	octet 23* - n*

Figure 9.11.3.51.1: SOR transparent container information element for list type with value "0" and SOR data type with value "0"

8	7	6	5	4	3	2	1
SOR transparent container IEI	octet 1
Length of SOR transparent container contents	octet 2octet 3
SOR header	octet 4
SOR-MAC-IAUSF	octet 5-20
CounterSOR	octet 21-22
PLMN ID and access technology list	octet 23-m

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"

8	7	6	5	4	3	2	1
SOR transparent container IEI	octet 1
Length of SOR transparent container contents	octet 2octet 3
SOR header	octet 4
SOR-MAC-IAUSF	octet 5octet 20
CounterSOR	octet 21octet 22
Length of PLMN ID and access technology list	octet 23*
PLMN ID and access technology list	octet 24octet m
0Spare	0Spare	0Spare	0Spare	SSSLI	SSSI	SSCMI	SI	octet o
SOR-CMCI	octet (o+1)octet p
SOR-SNPN-SI	octet (p+1)octet u
SOR-SNPN-SI-LS	octet (u+1)octet v

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"

PLMN ID 1	octet 23- 25
access technology identifier 1	octet 26- 27
…
PLMN ID n	octet (18+5n)-(20+5n)
access technology identifier n	octet (21+5n)-(22+5n)

Figure 9.11.3.51.3: PLMN ID and access technology list (m=22+5*n)

8	7	6	5	4	3	2	1
SOR transparent container IEI	octet 1
Length of SOR transparent container contents	octet 2octet 3
SOR header	octet 4
SOR-MAC-IUE	octet 5 - 20

Figure 9.11.3.51.4: SOR transparent container information element for SOR data type with value "1"

8	7	6	5	4	3	2	1
0Spare	0Spare	0Spare	AP	ACK	List type	List indication	SOR data type	octet 4

Figure 9.11.3.51.5: SOR header for SOR data type with value "0"

8	7	6	5	4	3	2	1
0Spare	0Spare	0Spare	0Spare	MSSSNPNSILS	MSSNPNSI	MSSI	SOR data type	octet 4

Figure 9.11.3.51.6: SOR header for SOR data type with value "1"

Table 9.11.3.51.1: SOR transparent container information element

SOR-MAC-IAUSF (see NOTE 1), SOR-MAC-IUE (see NOTE 2) and CounterSOR (see NOTE 1) are coded as specified in 3GPP TS 33.501 [24].

SOR data type (octet 4, bit 1)
0	The SOR transparent container carries steering of roaming information.
1	The 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'
1	list of preferred PLMN/access technology combinations is provided

List type (octet 4, bit 3) (see NOTE 1)
0	The 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)
0	acknowledgement not requested
1	acknowledgement requested

Additional parameters (AP) value (octet 4, bit 5)
Bit
5
0	Additional parameters not included
1	Additional 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 3GPP TS 31.115 [22B]. (see NOTE 1)

The PLMN ID and access technology list consists of PLMN ID and access technology identifier and are coded as specified in 3GPP TS 31.102 [22] clause 4.2.5. 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)
0	SOR-CMCI not supported by the ME
1	SOR-CMCI supported by the ME
ME support of SOR-SNPN-SI indicator (MSSNPNSI) value (octet 4, bit 3) (see NOTE 2, NOTE 6)
0	SOR-SNPN-SI not supported by the ME
1	SOR-SNPN-SI supported by the ME

MS support of SOR-SNPN-SI-LS indicator (MSSNPNSILS) value (octet 4, bit 4) (see NOTE 2)
Bit
4
0	SOR-SNPN-SI-LS not supported by the ME
1	SOR-SNPN-SI-LS supported by the ME
SOR-CMCI indicator (SI) value (octet o, bit 1)Bit
1
0	SOR-CMCI absent
1	SOR-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)Bit
2
0	Do not store SOR-CMCI in ME
1	Store 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)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'
1	SOR-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.

SOR-SNPN-SI-LS indicator (SSSLI) value (octet o, bit 4)Bit
4
0	SOR-SNPN-SI-LS absent
1	SOR-SNPN-SI-LS present

If the SSSLI bit is set to "SOR-SNPN-SI-LS present", the SOR-SNPN-SI-LS field is present. If the SSSLI bit is set to "SOR-SNPN-SI-LS absent", the SOR-SNPN-SI-LS 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, SOR-SNPN-SI or SOR-SNPN-SI-LS, and the list type bit is set to value "1". The ME supporting SOR-SNPN-SI-LS supports SOR-SNPN-SI as specified in 3GPP TS 23.122 [5].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 6: 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.

8	7	6	5	4	3	2	1
Length of SOR-CMCI contents	octet (o+1)octet (o+2)
SOR-CMCI rule 1	octet (o+3)octet q
SOR-CMCI rule 2	octet (q+1)octet r
...	octet (r+1)octet s
SOR-CMCI rule n	octet (s+1)octet p

Figure 9.11.3.51.7: SOR-CMCI

Table 9.11.3.51.2: SOR-CMCI

SOR-CMCI rule:The SOR-CMCI rule is coded according to figure 9.11.3.51.8 and table 9.11.3.51.3.

8	7	6	5	4	3	2	1
Length of SOR-CMCI rule contents	octet q+1octet q+2
Tsor-cm timer value	octet q+3
Criterion type	octet q+4
Criterion value	octet (q+5)octet r

Figure 9.11.3.51.8: SOR-CMCI rule

Table 9.11.3.51.3: SOR-CMCI rule

Tsor-cm timer valueThe Tsor-cm timer value field is coded according to octet 2 of the GPRS timer information element as specified in 3GPP TS 24.008 [12] clause 10.5.7.3 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
Bits8 7 6 5 4 3 2 10 0 0 0 0 0 0 1 DNN0 0 0 0 0 0 1 0 S-NSSAI SST0 0 0 0 0 0 1 1 S-NSSAI SST and SD0 0 0 0 0 1 0 0 IMS registration related signalling0 0 0 0 0 1 0 1 MMTEL voice call0 0 0 0 0 1 1 0 MMTEL video call0 0 0 0 0 1 1 1 SMS over NAS or SMSoIP0 0 0 0 1 0 0 0 SOR security check not successful1 1 1 1 1 1 1 1 match allAll 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 is coded as the length and value part of DNN information element as specified in clause 9.11.2.1B starting with the second octet.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 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 3GPP TS 23.122 [5] annex C.

8	7	6	5	4	3	2	1
Length of SOR-SNPN-SI contents	octet (p+1)octet (p+2)
0Spare	0Spare	0Spare	0Spare	0Spare	0Spare	CLGI	CLSI	octet (p+3)
CH controlled prioritized list of preferred SNPNs	octet (p+4)octet t
CH controlled prioritized list of GINs	octet (t+1)octet u

Figure 9.11.3.51.9: SOR-SNPN-SI

Table 9.11.3.51.4: SOR-SNPN-SI

CH controlled prioritized list of preferred SNPNs indicator (CLSI) value (octet p+3, bit 1)Bit
1
0	CH controlled prioritized list of preferred SNPNs absent
1	CH 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)Bit
2
0	CH controlled prioritized list of GINs absent
1	CH 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.

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.

8	7	6	5	4	3	2	1
Length of SOR-SNPN-SI-LS contents	octet (u+1)octet (u+2)
0Spare	0Spare	0Spare	0Spare	0Spare	0Spare	CLGLSI	CLSLSI	octet (u+3)
CH controlled prioritized list of preferred SNPNs for access for localized services in SNPN	octet (w+1)octet x
CH controlled prioritized list of preferred GINs for access for localized services in SNPN	octet (x+1)octet v

Figure 9.11.3.51.9A: SOR-SNPN-SI-LS

Table 9.11.3.51.4A: SOR-SNPN-SI-LS

CH controlled prioritized list of preferred SNPNs for access for localized services in SNPN indicator (CLSLSI) value (octet u+3, bit 1)Bit
1
0	CH controlled prioritized list of preferred SNPNs for access for localized services in SNPN absent
1	CH controlled prioritized list of preferred SNPNs for access for localized services in SNPN present

If the CLSLSI 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 for access for localized services in SNPN field is present. If the CLSLSI 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 for access for localized services in SNPN field is absent.

CH controlled prioritized list of preferred GINs for access for localized services in SNPN indicator (CLGLSI) value (octet u+3, bit 2)Bit
2
0	CH controlled prioritized list of preferred GINs for access for localized services in SNPN absent
1	CH controlled prioritized list of preferred GINs for access for localized services in SNPN present

If the CLGLSI bit is set to " CH controlled prioritized list of preferred GINs for access for localized services in SNPN present", the CH controlled prioritized list of preferred GINs for access for localized services in SNPN field is present. If the CLGLSI bit is set to " CH controlled prioritized list of preferred GINs for access for localized services in SNPN absent", the CH controlled prioritized list of preferred GINs for access for localized services in SNPN field is absent.

If the length of SOR-SNPN-SI-LS contents field indicates a length bigger than indicated in figure 9.11.3.51.9A, receiving entity shall ignore any superfluous octets located at the end of the SOR-SNPN-SI.

8	7	6	5	4	3	2	1
Length of CH controlled prioritized list of preferred SNPNs contents	octet p+4octet p+5
SNPN identity 1	octet (p+6)octet (p+14)
SNPN identity 2	octet (p+15)octet (p+23)
...	octet (p+24)octet (p+n9-2)*
SNPN identity n	octet (p+n9-3)octet (p+n9+5) = octet t*

Figure 9.11.3.51.10: CH controlled prioritized list of preferred SNPNs

8	7	6	5	4	3	2	1
Length of CH controlled prioritized list of preferred SNPNs for access for localized services in SNPN contents	octet u+1octet u+2
SNPN info 1	octet (u+3)octet u1
SNPN info 2	octet (u1+1)octet u2
...	octet (u2+1)octet u3
SNPN info n	octet (u3+1)octet v

Figure 9.11.3.51.10A: CH controlled prioritized list of preferred SNPNs for access for localized services in SNPN

8	7	6	5	4	3	2	1
Length of SNPN info	octet u+3octet u+4
0Spare	0Spare	0Spare	0Spare	0Spare	LVII	LAII	Time Ind	octet u+5
SNPN identity	octet (u+6)octet (u+14)
Time validity information	octet (u+15)octet s
Location assistance information	octet (s+1)octet q
Location validity information	octet (q+1)octet u1

Figure 9.11.3.51.10B: SNPN info

8	7	6	5	4	3
MCC digit 2	MCC digit 1	octet p+15
MNC digit 3	MCC digit 3	octet p+16
MNC digit 2	MNC digit 1	octet p+17
0Spare	0Spare	0Spare	0Spare	NID assignment mode	octet p+18
NID value digit 2	NID value digit 1	octet p+19
NID value digit 4	NID value digit 3	octet p+20
NID value digit 6	NID value digit 5	octet p+21
NID value digit 8	NID value digit 7	octet p+22
NID value digit 10	NID value digit 9	octet p+23

Figure 9.11.3.51.11: SNPN identity

8	7	6	5	4	3	2	1
Number of time periods	octet (p+18) or (t+15)
Time period 1	octet (p+19) or (t+16)octet (p+34) or (t+31)
Time period 2	octet (p+35)* or (t+32)octet (p+50) or (t+47)*
...	octet (p+51)* or (t+48)octet (p+2+o16)* or (t-1+o16)
Time period o	octet (p+3+o16) or (t+o16)octet (p+18+o16)* or (t+15+o16) = octet s

Figure 9.11.3.51.11A: Time validity information

8	7	6	5	4	3	2	1
0Spare	0Spare	0Spare	0Spare	0Spare	TAISI	TAIPI	GADI	octet (s+1)
Geographical area descriptions	octet (s+2)octet s3
Tracking area information of PLMNs	octet (s3+1)octet s4
Tracking area information of SNPNs	octet (s4+1)octet s5 = octet q*

Figure 9.11.3.51.11B: Location assistance information

8	7	6	5	4	3	2	1
Number of geographical area descriptions	octet (s+2)
Type of shape 1	octet (s+3)
Shape description 1	octet (s+4)octet s1
…	octet (s1+1)octet s2
Type of shape n	octet (s2+1)*
Shape description n	octet (s2+2)octet s3

Figure 9.11.3.51.11C: Geographical area descriptions

8	7	6	5	4	3	2	1
Number of tracking area information of PLMNs	octet s3+1
Tracking area information of PLMN 1	octet (s3+2)octet s8
Tracking area information of PLMN 2	octet (s8+1)octet s9
...	octet (s9+1)octet s10
Tracking area information of PLMN n	octet (s10+1)octet s4

Figure 9.11.3.51.11D: Tracking area information of PLMNs

8	7	6
MCC digit 2	MCC digit 1	octet s8+1
MNC digit 3	MCC digit 3	octet s8+2
MNC digit 2	MNC digit 1	octet s8+3
TAC list	octet s8+4octet s9

Figure 9.11.3.51.11E: Tracking area information of PLMN

8	7	6	5	4	3	2	1
Number of TACs	octet s14 = octet s8+4 or octet s11+10
TAC 1	octet s14+1octet s14+3
TAC 2	octet (s14+4)octet (s14+6)
...
TAC m	octet (s14+m3-2)octet (s14+m3) = octet s9 or octet s12

Figure 9.11.3.51.11F: TAC list

8	7	6	5	4	3	2	1
Number of tracking area information of SNPNs	octet s4+1
Tracking area information of SNPN 1	octet (s4+2)octet s11
Tracking area information of SNPN 2	octet (s11+1)octet s12
...	octet (s12+1)octet s13
Tracking area information of SNPN n	octet (s13+1)octet s5

Figure 9.11.3.51.11G: Tracking area information of SNPNs

8	7	6	5	4	3	2	1
SNPN identity	octet s11+1octet s11+9
TAC list	octet s11+10octet s12

Figure 9.11.3.51.11H: Tracking area information of SNPN

8	7	6	5	4	3	2	1
0Spare	0Spare	0Spare	0Spare	0Spare	0Spare	0Spare	TACI	octet (q+1)
TAC list	octet (q+2)octet u1

Figure 9.11.3.51.11I: Location validity information

Table 9.11.3.51.5: CH controlled prioritized list of preferred SNPNs and CH controlled prioritized list of preferred SNPNs for access for localized services in SNPN

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 (see NOTE 1)
NID assignment mode is coded as specified in 3GPP TS 23.003 [4].

NID value (see NOTE 1)
NID value is coded as specified in 3GPP TS 23.003 [4].

Time indication (bit1 of octet u+5)Bit
1
0		Time validity infomation not included
1		Time validity infomationinformation is included

Location assistance information indicator (LAII) (bit 2 of octet u+5)Bit
2
0		Location assistance information not included
1		Location assistance information included

Location validity information indicator (LVII) (bit 3 of octet u+5)Bit
3
0		Location validity information not included
1		Location validity information included

Tracking area code list indicator (TACI) (bit 1 of octet q+1) (see NOTE 2)Bit
1
0		TAC list not included
1		TAC list included

Geographical area descriptions indicator (GADI) (bit 1 of octet s+1)Bit
1
0		Geographical area descriptions not included
1		Geographical area descriptions included

Tracking area information of PLMNs (TAIPI) (bit 2 of octet s+1)Bit
2
0		Tracking area information of PLMNs not included
1		Tracking area information of PLMNs included

Tracking area information of SNPNs (TAISI) (bit 3 of octet s+1)Bit
3
0		Tracking area information of SNPNs not included
1		Tracking area information of SNPNs included


Location assistance information
Location assistance information field contains the geographical area descriptions field, the tracking area information of PLMNs field, the tracking area information of SNPNs field. or any combination of them.

Time period
The time period field is coded as the route selection descriptor component value field for "time window type" specified in 3GPP TS 24.526 [19] table 5.2.1.

Type of shape
Type of shape is coded as specified in Table 2a in 3GPP TS 23.032 [4B].

Shape description
Shape description is coded as specified in clause 7.3 in 3GPP TS 23.032 [4B].
Tracking area information of PLMNs
Tracking area information of PLMNs field contains one or more tracking area information of PLMN fields.

Tracking area information of PLMN
Tracking area information of PLMN field contains an MCC and MNC of a PLMN identity and a TAC list field containing one or more tracking area code fields, each indicating a TAC of a PLMN identified by the PLMN identity.
Tracking area information of SNPNs
Tracking area information of SNPNs field contains one or more tracking area information of SNPN fields.If the tracking area information of SNPNs field is included in a location assistance information field of an SNPN info field, the SNPN identity field in each tracking area information of SNPN field of the tracking area information of SNPNs field is different from the SNPN identity field in the SNPN info field.

Tracking area information of SNPN
Tracking area information of SNPN field contains SNPN identity and a TAC list containing one or more tracking area code fields, each indicating a TAC of an SNPN identified by the SNPN identity.
Tracking area code (TAC)
In the TAC field bit 8 of the first octet is the most significant bit and bit 1 of third octet the least significant bit.The coding of the tracking area code is the responsibility of each administration. Coding using full hexadecimal representation may be used. The tracking area code consists of 3 octets.


NOTE 1: NID coding deviates from coding of value part of NID IE as specified in clause 9.2.7 of 3GPP TS 24.502 [18], coding of the NID field of the SNPN list IE as specified in clause 9.11.3.92, and coding of the NID field of the SNPN list with trusted 5G connectivity IE as specified in clause H.2.4.7 of 3GPP TS 24.302 [16].NOTE 2: If the location validity information indicator is set to 'Location validity information included' but TAC list indicator is set to 'TAC list not included', the UE shall ignore the location validity information.

8	7	6	5	4	3	2	1
Length of CH controlled prioritized list of GINs contents	octet t+1octet t+2
GIN 1	octet (t+3)octet (t+11)
GIN 2	octet (t+12)octet (t+20)
...	octet (t+21)octet (t+n9-5)*
GIN n	octet (t+n9-6)octet (t+n9+2) = octet u*

Figure 9.11.3.51.12: CH controlled prioritized list of GINs

8	7	6	5	4	3	2	1
Length of CH controlled prioritized list of preferred GINs for access for localized services in SNPN contents	octet v+1octet v+2
GIN info 1	octet (v+3)octet v1
GIN info 2	octet (v1+1)octet v2
...	octet (v2+1)octet v3
GIN info n	octet (v3+1)octet w

Figure 9.11.3.51.12A: CH controlled prioritized list of preferred GINs for access for localized services in SNPN

8	7	6	5	4	3	2	1
Length of GIN info	octet v+3octet v+4
0Spare	0Spare	0Spare	0Spare	0Spare	LVII	LAII	Time Ind	octet v+5
GIN	octet (v+6)octet (v+14)
Time validity information	octet (v+15)octet s
Location assistance information	octet (s+1)octet q
Location validity information	octet (q+1)octet v1

Figure 9.11.3.51.12B: GIN info

8	7	6	5	4	3
MCC digit 2	MCC digit 1	octet t+12
MNC digit 3	MCC digit 3	octet t+13
MNC digit 2	MNC digit 1	octet t+14
0Spare	0Spare	0Spare	0Spare	NID assignment mode	octet t+15
NID value digit 2	NID value digit 1	octet t+16
NID value digit 4	NID value digit 3	octet t+17
NID value digit 6	NID value digit 5	octet t+18
NID value digit 8	NID value digit 7	octet t+19
NID value digit 10	NID value digit 9	octet t+20

Figure 9.11.3.51.13: GIN

Table 9.11.3.51.6: CH controlled prioritized list of GINs and CH controlled prioritized list of preferred GINs for access for localized services in SNPN

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 (see NOTE)
NID assignment mode is coded as specified in 3GPP TS 23.003 [4].

NID value (see NOTE)
NID value is coded as specified in 3GPP TS 23.003 [4].

Time indication (bit1 of octet v+5)Bit
1
0		Time validity information not included
1		Time validity information included

Location assistance information indicator (LAII) (bit 2 of octet v+5)Bit
2
0		Location assistance information not included
1		Location assistance information included

Location validity information indicator (LVII) (bit 3 of octet v+5)Bit
3
0		Location validity information not included
1		Location validity information included

Time period
The time period field is coded as the route selection descriptor component value field for "time window type" specified in 3GPP TS 24.526 [19] table 5.2.1.

Location assistance information (oct(s+1)* to (q)*)
The Location assistance information is coded according to Figure 9.11.3.51.11B and Table 9.11.3.51.5.

NOTE: NID coding deviates from coding of value part of NID IE as specified in clause 9.2.7 of 3GPP TS 24.502 [18], coding of the NID field of the SNPN list IE as specified in clause 9.11.3.92, and coding of the NID field of the SNPN list with trusted 5G connectivity IE as specified in clause H.2.4.7 of 3GPP TS 24.302 [16].