4.4.11 Contents of files at the DF_5GS level

31.1023GPPCharacteristics of the Universal Subscriber Identity Module (USIM) applicationRelease 17TS

4.4.11.1 Introduction

This clause describes the files that are specific for 5GS.

DF_5GS shall be present at the ADF_USIM level if any of the following services are "available" in EF_UST (USIM Service Table):

Service n°122	5GS Mobility Management Information
Service n°123	5G Security Parameters
Service n°124	Subscription identifier privacy support
Service n°125	SUCI calculation by the USIM
Service n°126	UAC Access Identities support
Service n°127	Control plane-based steering of UE in VPLMN
Service n°128	Call control on PDU Session by USIM
Service n°129	5GS Operator PLMN List
Service n°130	Support for SUPI of type NSI or GLI or GCI
Service n°132	Support for URSP by USIM
Service n°133	5G Security Parameters extended
Service n°134	MuD and MiD configuration data
Service n°135	Support for Trusted non-3GPP access networks by USIM
Service n°136	Support for multiple records of NAS security context storage for multiple registration
Service n°137	Pre-configured CAG information list
Service n°138	SOR-CMCI storage in USIM
Service n°140	Storage of disaster roaming information in USIM
Service n°141	Pre-configured eDRX parameters
Service n°142	5G NSWO support
Service n°144	Multiplier Coefficient for Higher Priority PLMN search via NG-RAN satellite access
Service n°145	KAUSF derivation configuration

4.4.11.2 EF_5GS3GPPLOCI (5GS 3GPP location information)

If service n°122 is "available" in EF_UST, this file shall be present.

This EF contains the following 5GS location information for 3GPP access:

‑ 5G-Globally Unique Temporary Identifier (5G-GUTI);

‑ Last visited registered Tracking Area Identity in 5GS (TAI);

‑ 5GS update status.

Identifier: ‘4F01’		Structure: transparent			Optional
SFI: ’01’
File size: 20 bytes			Update activity: high
Access Conditions: READ PIN UPDATE PIN DEACTIVATE ADM ACTIVATE ADM
Bytes	Description			M/O		Length
1 to 13	5G-GUTI for 3GPP access			M		13 bytes
14 to19	Last visited registered TAI in 5GS for 3GPP access			M		6 bytes
20	5GS update status for 3GPP access			M		1 byte

‑ 5G-GUTI for 3GPP access.

Contents:

5G-Globally Unique Temporary Identifier for 3GPP access.

Coding:

as the 5G-GUTI part of the 5GS mobile identity information element defined in TS 24.501 [104]. Byte 1 corresponds to "octet 2" of an 5GS mobile identity information element containing a 5G-GUTI. Byte 13 corresponds to "octet 14" of an 5GS mobile identity information element information element containing a 5G-GUTI.

Byte 1: first byte of 5G-GUTI for 3GPP access

b8

b7

b6

b5

b4

b3

b2

b1

MSB

‑ Last visited registered TAI in 5GS for 3GPP access

Contents:

Last visited registered Tracking Area Identity in 5GS for 3GPP access.

Coding:

as the content of the tracking area identity information element defined in TS 24.501 [104]. Byte 14 corresponds to "octet 2" of a tracking area identity information element. Byte 19 corresponds to "octet 7" of a tracking area identity information element.

Byte 14: first byte of last visited registered TAI for 3GPP access

b8

b7

b6

b5

b4

b3

b2

b1

MSB

‑ 5GS update status for 3GPP access.

Contents:

status of 5GS update for 3GPP access according to TS 24.501 [104].

Coding:

byte 20:

Bits: b3 b2 b1.

0 0 0 : 5U1 UPDATED.

0 0 1 : 5U2 NOT UPDATED.

0 1 0 : 5U3 ROAMING NOT ALLOWED.

0 1 1 : reserved.

1 0 0 : reserved.

1 0 1 : reserved.

1 1 0 : reserved.

1 1 1 : reserved.

Bits b4 to b8 are RFU (see TS 31.101 [11]).

Unused bytes shall be set to ‘FF’.

4.4.11.3 EF_5GSN3GPPLOCI (5GS non-3GPP location information)

If service n°122 is "available" in EF_UST, this file shall be present.

This EF contains the following 5GS location information for non-3GPP access:

‑ 5G-Globally Unique Temporary Identifier (5G-GUTI);

‑ Last visited registered Tracking Area Identity in 5GS (TAI);

‑ 5GS update status.

Identifier: ‘4F02’		Structure: transparent			Optional
SFI: ’02’
File size: 20 bytes			Update activity: high
Access Conditions: READ PIN UPDATE PIN DEACTIVATE ADM ACTIVATE ADM
Bytes	Description			M/O		Length
1 to 13	5G-GUTI for non-3GPP access			M		13 bytes
14 to19	Last visited registered TAI in 5GS for non-3GPP access			M		6 bytes
20	5GS update status for non-3GPP access			M		1 byte

For content and coding see clause 4.4.11.2 for EF_5GS3GPPLOCI.

4.4.11.4 EF_5GS3GPPNSC (5GS 3GPP Access NAS Security Context)

If service n°122 is "available" in EF_UST, this file shall be present.

This EF contains the 5GS 3GPP access NAS security context as defined in TS 24.501 [104], consisting of K_AMF with the associated key set identifier, the UE security capabilities, and the uplink and downlink NAS COUNT values. This EF also contains the EPS NAS security algorithms to be used when the UE goes to EPS, either by means of connected mode handover in a network that supports N26 interface, or by the means of idle mode mobility performed by the UE from 5GS to EPS, as specified in TS 33.501 [105]. This file shall contain one record.

If Service n°136 is not "available" in EF_UST, the file shall contain one record.

If service n°136 is "available" in EF_UST, the file shall contain two records. As specified in TS 33.501 [105] clause 6.3.2.1, in case of multiple registrations in different PLMNs, each record shall store 5GS 3GPP access NAS security context for each different PLMN (Refer to Annex O for examples),

Identifier: ‘4F03’		Structure: linear fixed			Optional
SFI: ’03’
Record size: X bytes (X≥57)			Update activity: high
Access Conditions: READ PIN UPDATE PIN DEACTIVATE ADM ACTIVATE ADM
Bytes	Description			M/O		Length
1 to X	5GS NAS Security Context TLV Object			M		X bytes

5GS NAS Security Context tags

Description	Tag Value
5GS NAS Security Context Tag	‘A0’

5GS NAS Security Context information

Description	Value	M/O	Length (bytes)
5GS NAS Security Context Tag	‘A0’	M	1
Length (length of all subsequent data)	Y	M	Note 1
ngKSI Tag	’80’	M	1
Length	K	M	Note 1
ngKSI	—	M	K
KAMF Tag	’81’	M	1
Length	L	M	Note 1
KAMF	—	M	L
Uplink NAS count Tag	’82’	M	1
Length	M	M	Note 1
Uplink NAS count	—	M	M
Downlink NAS count Tag	’83’	M	1
Length	N	M	Note 1
Downlink NAS count	—	M	N
Identifiers of selected NAS integrity and encryption algorithms Tag	’84’	M	1
Length	S	M	Note 1
Identifiers of selected NAS integrity and encryption algorithms	—	M	S
Identifiers of selected EPS NAS integrity and encryption algorithms for use after mobility to EPS Tag	’85’	M	1
Length	U	M	Note 1
Identifiers of selected EPS NAS integrity and encryption algorithms for use after mobility to EPS	—	M	U
PLMN identifier tag	’86’	C (see Note 2)	1
Length	3	C (see Note 2)	Note 1
PLMN identifier	—	C (see Note 2)	3
Note 1: The length is coded according to ISO/IEC 8825-1 [35] Note 2: If service n°136 is "available", PLMN identifier shall be included to identify the PLMN of the 5GS NAS Security Context stored in record 2 for the access. The PLMN identifier is not applicable for record 1 and is mandatory for record 2.

– ngKSI Tag ’80’

Contents:

The ngKSI (Key Set Identifier in 5G) as defined in TS 33.501 [105] is coded on 1 byte.

Coding:

b8

b7

b6

b5

b4

b3

b2

b1

ngKSI

bits b4 to b8 are coded 0

– K_AMF Tag ’81’

Contents:

The K_AMF as defined in TS 33.501 [105] is coded on 32 bytes. The ME shall treat any K_AMF values stored in this EF as invalid if the ngKSI indicates that no K_AMF is available or if the length indicated in the K_AMF TLV is set to ’00’,

Coding:

The most significant bit of K_AMF is the most significant bit of the 1^st byte of this TLV value field. The least significant bit of K_AMF is the least significant bit of the last byte of this TLV value field.

– Uplink NAS count Tag ’82’

Contents:

The uplink NAS count as defined in TS 33.501 [105] is coded on 4 bytes.

Coding:

The most significant bit of the uplink NAS count is the most significant bit of the 1^st byte of this TLV value field. The least significant bit of the uplink NAS count is the least significant bit of the last byte of this TLV value field.

– Downlink NAS count Tag ’83’

Contents:

The downlink NAS count as defined in TS 33.501 [105] is coded on 4 bytes.

Coding:

The most significant bit of the downlink NAS count is the most significant bit of the 1^st byte of this TLV value field. The least significant bit of the downlink NAS count is the least significant bit of the last byte of this TLV value field.

– Identifiers of selected NAS integrity and encryption algorithms Tag ’84’

Contents:

The identifiers of selected NAS integrity and encryption algorithms as defined in TS 33.501 [105] and TS 24.501 [104]. In this release the identifiers of selected NAS integrity and encryption algorithms are coded as 4-bit identifiers.

Coding:

Coding is same as the content of the NAS security algorithms information element defined in TS 24.501 [104].

Byte 1 of this TLV value field: first byte of the value part of the NAS security algorithms information element

b8

b7

b6

b5

b4

b3

b2

b1

MSB

– Identifiers of selected EPS NAS algorithms for use after mobility to EPS Tag ’85’

Contents:

The identifiers of selected EPS NAS integrity and encryption algorithms to be used when the UE goes to EPS, either by means of connected mode handover in a network that supports N26 interface, or by the means of idle mode mobility performed by the UE from 5GS to EPS, as specified in TS 33.501 [105] and TS 24.501 [104]. These identifiers are coded as 4-bit identifiers.

Coding:

Coding is same as the content of the EPS NAS security algorithms information element specified in TS 24.301 [51].

Byte 1 of this TLV value field: first byte of the value part of the EPS NAS security algorithms information element in TS 24.301 [51].

b8

b7

b6

b5

b4

b3

b2

b1

MSB

– PLMN identifier Tag ’86’

Contents:

The PLMN identifier comprising MCC and MNC defined in TS 23.003 [25] is coded on 3 bytes.

Coding:

The PLMN identifier is coded according to TS 24.008 [9].

Unused bytes shall be set to ‘FF’.

In order to mark the stored 5GS NAS security context as invalid:

– the record bytes shall be set to ‘FF’, or

– the ngKSI is set to ’07’, or

– the length indicated in the K_AMF TLV is set to ’00’.

4.4.11.5 EF_5GSN3GPPNSC (5GS non-3GPP Access NAS Security Context)

If Service n°122 is "available" in EF_UST, this file shall be present.

This EF contains the 5GS non-3GPP access NAS security context as defined in TS 24.501 [104], consisting of K_AMF with the associated key set identifier, the UE security capabilities, and the uplink and downlink NAS COUNT values. This EF also contains the EPS NAS security algorithms to be used when the UE goes to EPS, either by means of connected mode handover in a network that supports N26 interface, or by the means of idle mode mobility performed by the UE from 5GS to EPS, as specified in TS 33.501 [105]. .

If Service n°136 is not "available" in EF_UST, the file shall contain one record.

If service n°136 is "available" in EF_UST, the file shall contain two records. As specified in TS 33.501 [105] clause 6.3.2.1, in case of multiple registrations in different PLMNs, each record shall store 5GS non-3GPP access NAS security context for each different PLMN (Refer to Annex O for examples).

Identifier: ‘4F04’		Structure: linear fixed			Optional
SFI: ’04’
Record size: X bytes (X≥57)			Update activity: high
Access Conditions: READ PIN UPDATE PIN DEACTIVATE ADM ACTIVATE ADM
Bytes	Description			M/O		Length
1 to X	5GS NAS Security Context TLV Object			M		X bytes

For content and coding see clause 4.4.11.4 for EF_5GS3GPPNSC.

4.4.11.6 EF_5GAUTHKEYS (5G authentication keys)

If Service n°123 is "available" in EF_UST, this file shall be present. This EF contains K_SEAF for 3GPP access and the K_AUSF that are generated on the ME using CK and IK as part of AKA procedures as described in TS 33.501 [105].

If Service n°133 is not "available" in EF_UST, the file size is at least 68 bytes.

If Service n°133 is also "available" in EF_UST, this EF additionally contains K_SEAF for non-3GPP access, SOR counter and UE parameter update counter and the file size is at least 110 bytes.

Identifier: ‘4F05’	Structure: transparent				Optional
SFI: ’05’
File size: >= 68 or 110 bytes			Update activity: high
Access Conditions: READ PIN UPDATE PIN DEACTIVATE ADM ACTIVATE ADM
Description		Value		M/O		Length
KAUSF Tag		’80’		M		1
Length		K (Note2)		M		Note1
KAUSF		—		M		K (Note2)
KSEAF for 3GPP access Tag		’81’		M		1
Length		L (Note2)		M		Note1
KSEAF for 3GPP access		—		M		L (Note2)
KSEAF for non-3GPP access Tag		’82’		C		1
Length		M (Note2)		C		Note1
KSEAF for non-3GPP access		—		C		M (Note2)
SOR counter Tag		’83’		C		1
Length		N		C		Note 1
SOR counter		—		C		N (Note 3)
UE parameter update counter Tag		’84’		C		1
Length		O		C		Note 1
UE parameter update counter		—		C		O (Note 3)
Note 1: The length is coded according to ISO/IEC 8825-1 [35]
Note 2: As per TS 33.501 [105], the length of keys KAUSF and KSEAF is 32 bytes each
Note 3: As per TS 33.501 [105], the length of SOR counter and UE parameter update counter is 2 bytes each

‑ K_AUSF Tag ’80’.

Contents:

– K_AUSF as described in TS 33.501[105]).

Coding:

– The most significant bit of K_AUSF is the most significant bit of the 1st byte of this TLV value field. The least significant bit of K_AUSF is the least significant bit of the last byte of this TLV value field.

‑ K_SEAF for 3GPP access Tag ’81’.

Contents:

– K_SEAF for 3GPP access as described in TS 33.501[105]. If there is no valid K_SEAF for 3GPP access, the contents (Value part of the TLV) shall be ‘FF…FF’.

Coding:

– The most significant bit of K_SEAF for 3GPP access is the most significant bit of the 1st byte of this TLV value field. The least significant bit of K_SEAF for 3GPP access is the least significant bit of the last byte of this TLV value field.

‑ K_SEAF for non-3GPP access Tag ’82’.

Contents:

– K_SEAF for non-3GPP access as specified in TS 33.501[105]. If there is no valid K_SEAF for non-3GPP access, the contents (Value part of the TLV) shall be ‘FF…FF’.

Coding:

– The most significant bit of K_SEAF for non-3GPP access is the most significant bit of the 1st byte of this TLV value field. The least significant bit of K_SEAF for non-3GPP access is the least significant bit of the last byte of this TLV value field.

– SOR counter Tag ’83’

Contents:

– The SOR counter as defined in 3GPP TS 33.501 [105] clause 6.14.2.3. In this release the SOR counter is coded on 2 bytes. If there is no valid SOR counter, the contents (Value part of the TLV) shall be ‘FF…FF’.

Coding:

– The most significant bit of the SOR counter is the most significant bit of the 1^st byte of this TLV value field. The least significant bit of the SOR counter is the least significant bit of the last byte of this TLV value field.

– UE parameter update counter Tag ’84’

Contents:

– The UE parameter update counter as defined in 3GPP TS 33.501 [105] clause 6.15.2.2. In this release the UE parameter update counter is coded on 2 bytes. If there is no valid UE parameter update counter, the contents (Value part of the TLV) shall be ‘FF…FF’.

Coding:

– The most significant bit of the UE parameter update counter is the most significant bit of the 1^st byte of this TLV value field. The least significant bit of the UE parameter update counter is the least significant bit of the last byte of this TLV value field.

4.4.11.7 EF_{UAC_AIC} (UAC Access Identities Configuration)

If service n°126 is "available" in EF_UST, this file shall be present.

This EF contains the configuration information pertaining to access identities allocated for specific high priority services that can be used by the subscriber. The assigned access identities are used, in combination with an access category, to control the access attempts. For more information see TS 22.261 [106] and TS 24.501 [104].

Identifier: ‘4F06’		Structure: transparent			Optional
SFI: ’06’
File size: 4 bytes			Update activity: low
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM
Bytes	Description			M/O		Length
1 to 4	UAC access identities configuration			M		4 bytes

‑ UAC access identities configuration

Contents:

‑ Configuration of certain Unified Access Control (UAC) access identities specified in TS 24.501 [104] clause 4.5.2.

Coding:

‑ Each access identity configuration is coded on one bit.

Byte 1:

b8

b7

b6

b5

b4

b3

b2

b1

b1=0: UE is not configured for Multimedia Priority Service in the HPLMN,EHPLMN or a visited PLMN of the home country. b1=1: UE is configured for Multimedia Priority Service in the HPLMN,EHPLMN or a visited PLMN of the home country.

b2=0: UE is not configured for Mission Critical Services in the HPLMN,EHPLMN or a visited PLMN of the home country. b2=1: UE is configured for Mission Critical Services in the HPLMN,EHPLMN or a visited PLMN of the home country.

RFU

Bytes 2 to 4:

Bits b1 to b8 are RFU.

NOTE 1: Access Identities 11 to 15 (as specified in TS 24.501 [104]) are configured as Access Classes 11 to 15 in EF_ACC, specified in clause 4.2.15_.

NOTE 2: The home country is defined as the country to which user subscription is associated (e.g. the MCC part of the IMSI, see the definition in TS 24.301[51]).

4.4.11.8 EF_{SUCI_Calc_Info} (Subscription Concealed Identifier Calculation Information EF)

If "SUCI calculation is to be performed by the ME" (i.e. service n°124 is "available" in EF_UST and service n°125 is not "available" in EF_UST), this file shall be present. This EF contains information needed by the ME for the support of subscription identifier privacy as defined in 3GPP TS 33.501[105].

If "SUCI calculation is to be performed by the USIM" (i.e. service n°124 is "available" in EF_UST and service n°125 is "available" in EF_UST), this file shall not be available to the ME.

If service n°124 is not "available" in EF_UST, this file shall not be available to the ME.

Note: How the file is made "not available to the ME" is implementation specific, e.g. the file may not be present, the file may be present but not readable by the ME, or the file may be present but deactivated.

Identifier: ‘4F07’		Structure: transparent			Optional
SFI: ’07’
File size: X bytes (X ≥ 2)			Update activity: low
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM
Bytes	Description			M/O		Length
1 to Z	Protection Scheme Identifier List data object			M		Z bytes
Z+1 to Y+Z	Home Network Public Key List data object			C		Y bytes

‑ Protection Scheme Identifier List data object.

Contents:

This data object shall always be present. If Protection Scheme Identifier List data object length is not zero, this data object contains a list of the Protection Scheme Identifier and the corresponding Key Index. The first Protection Scheme Identifier entry has the highest priority and the last Protection Scheme Identifier entry has the lowest priority. The Key Index value indicates the position of the Home Network Public Key in the Home Network Public Key List, that is applicable to the Protection Scheme.

Coding:

Description	Value	M/O/C	Length (bytes)
Protection Scheme Identifier List data object tag	‘A0’	M	1
Protection Scheme Identifier List data object length	L1	M	Note 1
Protection Scheme Identifier 1 (Highest priority)	—	O	1
Key Index 1	—	C (Note 2)	1
Protection Scheme Identifier 2	—	O	1
Key Index 2	—	C (Note 2)	1
…	…	…	…
Protection Scheme Identifier N (Lowest priority)	—	O	1
Key Index N	—	C (Note 2)	1
Note 1: The length is coded according to ISO/IEC 8825-1 [35] Note 2: This field is present only if the corresponding Protection Scheme Identifier field is present

The Protection Scheme Identifier represents a protection scheme as described in 3GPP TS 33.501 [105] and it is coded in one byte as follows:

b8

b7

b6

b5

b4

b3

b2

b1

Protection Scheme identifier coded as described in 3GPP TS 24.501 [104]

RFU, bit = 0

The Key Index is coded in one byte such that its value indicates the position of the Home Network Public Key in the Home Network Public Key List data object, that is applicable to the Protection Scheme. A Key Index with a value of "1" refers to the first Network Public Key entry in the Home Network Public Key List, and so on. A Key Index with a value of "0" indicates that there is no Home Network Public Key associated with that Protection Scheme (e.g., in the case of null-scheme).

‑ Home Network Public Key List data object.

Contents:

This data object contains a list of the Home Network Public Key and the corresponding Home Network Public Key Identifier that shall be used by the ME to calculate the SUCI.

This data object may not be present if none of the protection scheme profiles identified by the Protection Scheme Identifiers included in the Protection Scheme Identifier List data object use the Home Network Public Key (e.g. null-scheme). If this data object is present, it shall contain at least one Home Network Public Key and the corresponding Home Network Public Key Identifier.

Coding:

Description	Value	M/O/C	Length (bytes)
Home Network Public Key List data object	‘A1’	C	1
Home Network Public Key List data object length	L1	C	Note 1
Home Network Public Key 1 Identifier tag	’80’	C	1
Home Network Public Key 1 Identifier length	L2	C	Note 1
Home Network Public Key 1 Identifier	—	C	L2
Home Network Public Key 1 tag	’81’	C	1
Home Network Public Key 1 length	L3	C	Note 1
Home Network Public Key 1	—	C	L3
…	…	…	…
Home Network Public Key N Identifier tag	’80’	O	1
Home Network Public Key N Identifier length	L4	O	Note 1
Home Network Public Key N Identifier	—	O	L4
Home Network Public Key N tag	’81’	O	1
Home Network Public Key N length	L5	O	Note 1
Home Network Public Key N	—	O	L5
Note 1: The length is coded according to ISO/IEC 8825-1 [35]

The Home Network Public Key Identifier may have any value in the range from 0 to 255 as described in 3GPP TS 23.003 [25] and it is coded in one byte as described in 3GPP TS 24.501 [104].

The Home Network Public Key is coded in hexadecimal digits as described in IETF RFC 7748 [108] (for Protection Scheme Profile A) and in IETF RFC 5480 [107] (for Protection scheme Profile B). The length of the Home Network Public Key depends on the Protection Scheme and the form of the Home Network Public Key (e.g. compressed or uncompressed).

4.4.11.9 EF_OPL5G (5GS Operator PLMN List)

If service n°129 is "available", this file shall be present.

This EF contains a prioritised list of Tracking Area Identity (TAI) identities for NG-RAN that are used to associate a specific operator name contained in EF_PNN or EF_PNNI with the TAI. The ME shall use this EF in association with the EF_PNN in place of any network name stored within the ME’s internal list and any network name received when registered to the PLMN, as defined by TS 24.501 [104]. The PLMN Network Name may also be provided in a graphical format in EF_PNNI. The ME shall use the text format or the graphical format or both to display the service provider name according to the rules defined in clause 4.2.89.

Identifier: ‘4F08’		Structure: linear fixed			Optional
SFI: ’08’
Record length: X bytes, (X ≥ 10)			Update activity: low
Access Conditions: READ ALWAYS UPDATE ADM DEACTIVATE ADM ACTIVATE ADM
Bytes	Description			M/O		Length
1 to 9	Tracking Area Identity			M		9 bytes
10	PLMN Network Name Record Identifier			M		1 byte

– Tracking Area Identity

Contents:
Tracking Area Identity for NG-RAN, this comprises of the MCC, MNC and TAC

Coding:
PLMN: according to TS 24.501 [104]
A BCD value of ‘D’ in any of the MCC and/or MNC digits shall be used to indicate a "wild" value for that corresponding MCC/MNC digit

TAC: according to TS 24.501 [104]

Two values for the TAC are stored in order to allow a range of TAC values to be specified for a given PLMN. A value of ‘000000’ stored in bytes 4 to 6 and a value of ‘FFFFFE’ stored in bytes 7 to 9 shall be used to indicate the entire range of TACs for the given PLMN. In the case where only a single TAC value is to be specified then the value stored in bytes 4 to 6 shall be identical to the value stored in bytes 7 to 9 for the given PLMN. If a range of TAC values are to be specified, then the value stored in bytes 4 to 6 shall be the start of the TAC range and the value stored in bytes 7 to 9 shall be the end of the TAC range for the given PLMN.

– PLMN Network Name Record Identifier

Contents:
Identifier of operator name to be displayed

Coding:
A value of ’00’ indicates that the name is to be taken from other sources, see TS 22.101 [24]

A value in the range ’01’ to ‘FE’ indicates the record number in EF_PNN that shall be displayed as the registered PLMN name. It also indicates the record number in EF_PNNI that may be displayed as the registered PLMN name icon.

NOTE: The intent of this file is to provide exceptions to the other sources of a network name. Care should be taken not to introduce too many PLMN entries. An excessive number of entries could result in a longer initialisation period.

4.4.11.10 EF_{SUPI_NAI} (SUPI as Network Access Identifier)

If service n°130 is "available", this file shall be present.

This EF contains the SUPI in NAI format consisting of a:

– network specific identifier(NSI), as specified in TS 23.003 [25], when SUPI type is NSI or

– Global Line Identifier (GLI), as specified in TS 23.003 [25] clause 28.15.2, when SUPI type is GLI or

– Global Cable Identifier (GCI), as specified in TS 23.003 [25] clause 28.16.2, when SUPI type is GCI,

The SUPI contained in this EF shall not be an IMSI.

Identifier: ‘4F09’		Structure: transparent			Optional
SFI: ’09’
File size: Z bytes (Z ≥ X)			Update activity: low
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM
Bytes	Description			M/O		Length
1 to X	Network Access Identifier TLV data object			M		X bytes

– Network Access Identifier TLV data object:

Contents:

– This data object contains the Subscription Permanent Identifier in NAI format consisting of a:

– network specific identifier (NSI) or

– Global Line Identifier (GLI) or

– Global Cable Identifier (GCI).

Coding:

When SUPI type is network specific identifier:

Description	Value	M/O	Length (bytes)
Network Specific Identifier Tag	’80’	M	1
Length	L	M	Note
Network Specific Identifier	—	M	L
Note: The length is coded according to ISO/IEC 8825-1 [35]

The Network Specific Identifier in NAI format is a NAI constructed as specified in IETF RFC 7542 and encoded as UTF-8 string.

When SUPI type is Global Line Identifier:

Description	Value	M/O	Length (bytes)
Global Line Identifier Tag	’81’	M	1
Length	L	M	Note
Global Line Identifier	—	M	L
Note: The length is coded according to ISO/IEC 8825-1 [35]

The Global Line Identifier as specified in TS 23.003 [25] clause 28.16.2.

When SUPI type is Global Cable Identifier (GCI):

Description	Value	M/O	Length (bytes)
Global Cable Identifier Tag	’82’	M	1
Length	L	M	Note
Global Cable Identifier	—	M	L
Note: The length is coded according to ISO/IEC 8825-1 [35]

The Global Cable Identifier as specified in TS 23.003 [25] clause 28.15.2.

NOTE 1: The length is coded according to ISO/IEC 8825-1 [35]

4.4.11.11 EF_{Routing_Indicator} (Routing Indicator EF)

If service n°124 is "available" in EF_UST, this file shall be present. This EF contains Routing Indicator needed by the ME or by the USIM for SUCI calculation.

Identifier: ‘4F0A’		Structure: transparent			Optional
SFI: ‘0A’
File size: 4 bytes			Update activity: low
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM
Bytes	Description			M/O		Length
1 to 4	Routing Indicator			M		4 bytes

‑ Routing Indicator

Contents:

This EF contains Routing Indicator that allows together with the MCC and MNC to route network signalling with SUCI to AUSF and UDM instances capable to serve the subscriber, as specified in 3GPP TS 23.003 [25].

Coding:

Bytes 1 to 2:

The Routing Indicator is coded in 2 bytes as specified in 3GPP TS 24.501 [104]. This EF shall contain at least one valid digit of Routing ID even if that only digit is set to 0 (which is the case when the HPLMN intends to not configure a valid Routing Indicator in the USIM), as specified in 3GPP TS 24.501 [104].

Bytes 3 to 4:

RFU.

4.4.11.12 EF_URSP (URSP)

If service n°132 is "available" in EF_UST, this file shall be present. This EF contains UE Route Selection Policies per PLMN. The format of the UE Route Selection Policies are specified in 3GPP TS 24.526 [109].

Identifier: ‘4F0B’		Structure: BER-TLV			Optional
SFI: Optional
File size: > (L0 + X1+X2+…+XN +L1+L2+…+LN + 3 x N) bytes			Update activity: low
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM
Bytes	Description			M/O		Length
1 to L0 +1 +X1+X2+…+XN +L1+L2+…+LN + 3 x N	URSP Rules data object			O		L0 +1 +X1+X2+…+XN +L1+L2+…+LN + 3 x N

– URSP Rules data object coded as follows:

Description	Value	M/O	Length
URSP Rules data object tag	’80’	O	1 byte
URSP Rules length	X1+X2+…+XN +L1+L2+…+LN + 3 x N	O	L0 bytes (note)
PLMN 1		O	3 bytes
Total length of URSP rules for PLMN 1	X1	O	L1 bytes (note)
UE Route Selection Policy rules for PLMN 1		O	X1 bytes
PLMN 2		O	3 bytes
Length of URSP rules for PLMN 2	X2	O	L2 bytes (note)
UE Route Selection Policy rules for PLMN 2		O	X2 bytes
…
PLMN N		O	3 bytes
Length of URSP rules for PLMN N	XN	O	LN bytes (note)
UE Route Selection Policy rules for PLMN N		O	XN bytes
Note: The length is coded according to ISO/IEC 8825-1 [35].

‑ PLMN

Contents:

– Mobile Country Code (MCC) followed by the Mobile Network Code (MNC).

Coding:

– According to TS 24.008 [9].

– Total length of URSP rules

Contents:

– This field contains the Total length of URSP rules for this PLMN.

Coding:

– The length is coded according to ISO/IEC 8825-1 [35].

– UE Route Selection Policy rules for this PLMN

Contents:

– UE Route Selection Policies used by the UE to determine how to route outgoing traffic.

Coding:

– The coding of the URSP rules is specified in clause 5.2 and URSP rule is encoded as shown in figures 5.2.1 to 5.2.4 and table 5.2.1 of 3GPP TS 24.526 [109].

4.4.11.13 EF_TN3GPPSNN (Trusted non-3GPP Serving network names list)

If service n°135 is "available" in EF_UST, this file shall be present.

This EF contains the coding for n Serving network name TLV data objects, n is determined by the operator.

This information is determined by the home network operator as specified in TS 33.501 [105] (see clause 7.1a).

Identifier: ‘4F0C’		Structure: transparent			Optional
SFI: ‘0C ‘
File size: Z (>=1) bytes			Update activity: low
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM
Bytes	Description			M/O		Length
1	Number of Serving network name TLV data objects (n)			M		1
2 to X1+1	1st Serving network name TLV data object			O		X1 bytes
…
2+X1+..+Xn-1	Nth Serving network name TLV data object			O		Xn bytes

– Number of Serving network name TLV data objects

Contents:

– Number of TLV data objects coded in the file

– Serving network name TLV data object

Contents:

– This data object contains Serving network name for Trusted non-3GPP access network

Coding:

Description	Value	M/O/C	Length (bytes)
Serving network name tag	’80’	M	1
Length	X	M	Note
Serving network name	—	M	X
Note: The length is coded according to ISO/IEC 8825-1 [35]

– The serving network name is defined as specified in TS 33.501 [105] (see clauses 6.1.1.4) and shall be encoded to an octet string according to UTF-8 encoding rules as specified in IETF RFC 3629 [48]

4.4.11.14 EF_CAG (Pre-configured CAG information list EF)

If service n°137 is "available" in EF_UST, this file shall be present. This EF contains a pre-configured CAG information list used by the ME as specified in 3GPP TS 23.122 [31] clause 3.8.

Identifier: ‘4F0D’		Structure: transparent			Optional
SFI: ‘0D’
File size: Z (>=2) bytes			Update activity: low
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM
Bytes	Description			M/O		Length
1 to 2	Length of CAG information list entries			M		2
3 to 2+X1	1st CAG information list entry			O		X1 bytes
…
3+X1+..+XN-1 to 2+X1+…+XN	Nth CAG information list entry			O		XN bytes

Length of CAG information list entries

Contents:

– Total length of all the CAG information list entries that follow

– CAG information list entry

Contents:

– Each CAG information list entry contains either:

i) an entry in the CAG information list , the coding of which is specified in 3GPP TS 24.501 [104] clause 9.11.3.18A, Figure 9.11.3.18A.2 and Table 9.11.3.18A.1;or

ii) an entry for HPLMN or EHPLMN including a CAG-ID range, the coding of which is as shown below.

8	7	6	5	4	3	2	1
Length of entry including a CAG-ID range contents								octet 3+X1+…+Xm-1
MCC digit 2				MCC digit 1				octet 4+X1+…+Xm-1
MNC digit 3				MCC digit 3				octet 5+X1+…+Xm-1
MNC digit 2				MNC digit 1				octet 6+X1+…+Xm-1
0 Spare	0 Spare	0 Spare	0 Spare	0 Spare	0 Spare	1 NOTE 1	CAG only	octet 7+X1+…+Xm-1
CAG-ID range								octet 8+X1+…+Xm-1 octet 15+X1+…+Xm-1

where:

a) MCC digits 1 to 3, MNC digits 1 to 3, and CAG only bit, are encoded as corresponding fields of an entry in the CAG information list; and

b) a CAG-ID range contains two CAG-IDs. The coding of the CAG-ID is defined as the CAG-Identifier in 3GPP TS 23.003 [25]. It shall be considered that all CAG-IDs in the CAG-ID range between the first CAG-ID and the second CAG-ID including the first and second CAG-IDs are allowed.

NOTE 1: Bit 2 in octet 7+X₁+…+X_m-1 is set to ‘1’ to indicate a range of CAG ID’s see 3GPP TS 24.501 [104].

4.4.11.15 EF_SOR-CMCI (Steering Of Roaming – Connected Mode Control Information)

If service n°138 is "available" in EF_UST, this file shall be present.

This EF contains SOR-CMCI parameters as specified in 3GPP TS 24.501 [104]

Identifier: ‘4F0E’		Structure: transparent			Optional
SFI: ‘0E’
File size: Z bytes (Z ≥ X)			Update activity: low
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM
Bytes	Description			M/O		Length
1 to X	SOR-CMCI data object			O		X bytes

‑ SOR-CMCI data object

Coding of the SOR-CMCI data object

Length	Description	Coding	Status
1	SOR-CMCI data object tag	‘80’	O
1 to L (L ≤ 4)	SOR-CMCI data object length	As defined in TS 31.101 [11] for BER-TLV structured files	O
X-1-L bytes	SOR-CMCI parameters	As specified in TS 24.501 [104] clause 9.11.3.51 and start from octet (o+3) of SOR-CMCI as defined in Figure 9.11.3.51.7 of TS 24.501 [104].	O

As defined in 3GPP TS 23.122 [31] clause C.4.1, ‘no SOR-CMCI rule’ is defined when:

– SOR-CMCI data object is not present; or

– SOR-CMCI data object is zero length

Then UE behaviour described in 3GPP TS 23.122 [31] clause C.4.2 applies.

4.4.11.16 Void

4.4.11.16.1 Void

4.4.11.16.2 Void

4.4.11.16.3 Void

4.4.11.16.4 Void

4.4.11.16.5 Void

4.4.11.16.6 Void

4.4.11.17 EF_DRI (Disaster roaming information EF)

If service n°140 is "available" in EF_UST, this file shall be present.

This EF contains the indication of whether disaster roaming is enabled in the UE as specified in 3GPP TS 23.122 [31].
In addition it contains disaster roaming parameters indicating availability of each related information field.
Further it contains disaster roaming wait range as specified in 3GPP TS 23.122 [31], disaster return wait range as specified in 3GPP TS 23.122 [31] and the indication of ‘applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN’ from the USIM into the ME, as specified in 3GPP TS 24.501 [104] annex C.

Identifier: ‘4F0F’		Structure: transparent			Optional
SFI: ‘0F’
File size: ≥ 7 bytes			Update activity: low
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM
Bytes	Description			M/O		Length
1	Disaster roaming is enabled			M		1 byte
2	Disaster roaming parameters indicator status			M		1 byte
3 to 4	Disaster roaming wait range			M		2 bytes
5 to 6	Disaster return wait range			M		2 bytes
7	Applicability indicator for "list of PLMN(s) to be used in disaster condition" provided by VPLMN			M		1 byte

Storage is allocated for all of the possible disaster roaming parameters, regardless of whether they are present or absent. Any bytes unused, due to parameters not requiring all of the bytes, or due to absent parameters, shall be set to ‘FF’.

‑ Disaster roaming is enabled

Coding:

The indication of whether disaster roaming is enabled, it is coded in one byte as follows:

b8

b7

b6

b5

b4

b3

b2

b1

Indication of whether disaster roaming is enabled as described in 3GPP TS 24.501 [104]

RFU, bit = 0

‑ Disaster roaming parameters indicator status

Contents:

Each of the disaster roaming information parameters which can be stored in the remainder of the record are marked absent or present by individual bits within this byte.

Coding:

allocation of bits:

bit number Parameter indicated.

1 Disaster roaming wait range.

2 Disaster return wait range

3 Applicability indicator for "list of PLMN(s) to be used in disaster condition" provided by VPLMN.

4 reserved, set to 1.

5 reserved, set to 1.

6 reserved, set to 1.

7 reserved, set to 1.

8 reserved, set to 1.

Bit value Meaning.

0 Parameter present.

1 Parameter absent.

‑ Disaster roaming wait range

Coding:

The disaster roaming wait range is coded as specified in 3GPP TS 24.501 [104] clause 9.11.3.84 and starts from octet 3 of the registration wait range as defined in Figure 9.11.3.84.1 of 3GPP TS 24.501 [104].

‑ Disaster return wait range

Coding:

The disaster return wait range is coded as specified in 3GPP TS 24.501 [104] clause 9.11.3.84 and starts from octet 3 of the registration wait range as defined in Figure 9.11.3.84.1 of 3GPP TS 24.501 [104].

‑ Applicability indicator for "list of PLMN(s) to be used in disaster condition" provided by VPLMN

Coding:

The applicability indicator for "list of PLMN(s) to be used in disaster condition" provided by VPLMN is coded as specified in 3GPP TS 24.501 [104].

4.4.11.18 EF_5GSEDRX (5GS eDRX Parameters)

If service n°141 is "available" in EF_UST, this file shall be present.

This EF contains the following 5GS eDRX parameters:

‑ ratType: Radio Access Technology Type;

‑ edrxValue: Extended idle mode DRX cycle length.

Identifier: ‘4F10’		Structure: transparent			Optional
SFI: ’10’
File size: X bytes, (X ≥ 2)			Update activity: low
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM
Bytes	Description			M/O		Length
1	5GS ratType			M		1 byte
2	The extended idle mode DRX cycle length value			M		1 byte

‑ 5GS ratType.

Contents:

The NG-RAN rat type which eDRX values are applicable to.

Coding:

b8

b7

b6

b5

b4

b3

b2

b1

1:the rat type is NG-RAN 0:RFU

1:the rat type is Satellite NG-RAN 0:RFU

RFU

‑ The extended idle mode DRX cycle length value.

Contents:

The extended idle mode DRX cycle length value.

Coding:

This data object contains the extended idle mode DRX cycle length value, the coding of which is specified in 3GPP TS 24.008 table 10.5.5.32.

4.4.11.19 EF_{5GNSWO_CONF} (5G Non-Seamless WLAN Offload configuration)

If service n°142 is "available", this file shall be present.

This EF contains 5G Non-Seamless WLAN Offload configuration related information.

If the 5G Non-Seamless WLAN Offload usage Indicator is enabled ME shall always use 5G NSWO as in TS 33.501 [105] (i.e., it shall not use EPS NSWO).

Identifier: ‘4F11’		Structure: transparent			Optional
SFI: ’11’
File size: >= 1 byte			Update activity: low
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM
Bytes	Description			M/O		Length
1	5G Non-Seamless WLAN Offload usage Indicator			M		1byte

– 5G Non-Seamless WLAN Offload usage Indicator:

Contents:

5G Non-Seamless WLAN Offload usage Indicator

Coding:

– ’00’ – 5G Non-Seamless WLAN Offload usage Indicator is disabled

– ’01’ –5G Non-Seamless WLAN Offload usage Indicator is enabled

– All other values are RFU

4.4.11.20 EF_MCHPPLMN (Multiplier Coefficient for Higher Priority PLMN search)

If service n°144 is "available" in EF_UST, this file shall be available.

This EF contains a multiplier coefficient which is used together with timer interval configured in EF_HPPLMN to adjust the interval of time between two searches for a higher priority PLMN via NG-RAN satellite access (see 3GPP TS 23.122 [31]).

Identifier: ‘4F15’		Structure: transparent			Optional
SFI: ’15’
File size: X bytes, (X ≥ 1)			Update activity: low
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM
Bytes	Description			M/O		Length
1	Multiplier coefficient for higher priority PLMN search			M		1 byte

‑ Multiplier coefficient.

Contents:

The multiplier coefficient to adjust the time interval for higher priority PLMN search.

Coding:

For UEs supporting satellite NG-RAN access as specified in 3GPP TS 23.122 [31], the multiplier coefficient is coded as an unsigned byte. The range is from one to a maximum value of 255. The encoding is:

‑ ’00’: Not defined.

‑ ’01’: 1;

‑ ’02’: 2;

‑ : :

‑ ‘FF’: 255; (maximum value).

4.4.11.21 EF_{KAUSF_DERIVATION} (K_AUSF derivation configuration)

If service n°145 is "available", this file shall be present. This EF contains the configuration parameter for K_AUSF derivation, as defined in TS 33.501 [105].

Identifier: ‘4F16’		Structure: transparent			Optional
SFI: ‘16’
File size: X bytes (X ≥ 1)			Update activity: low
Access Conditions: READ PIN UPDATE ADM ACTIVATE ADM DEACTIVATE ADM
Bytes	Description			M/O		Length
1	KAUSF derivation configuration			M		1 byte
2 to X	RFU			O		X bytes

Contents:

Configuration for K_AUSF derivation

Coding:

b8

b7

b6

b5

b4

b3

b2

b1

KAUSF derivation configuration in SNPN: b1=0 Use EMSK for derivation of KAUSF in SNPN b1=1 Use MSK for derivation of KAUSF in SNPN

RFU (see TS 31.101 [11])