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

Content for  TS 31.102  Word version:  18.3.0

Top   Top   Up   Prev   Next
0…   3…   4…   4.2.9…   4.2.17…   4.2.26…   4.2.34…   4.2.44…   4.2.52…   4.2.60…   4.2.68…   4.2.76…   4.2.85…   4.2.93…   4.2.101…   4.2.107…   4.3…   4.4.2…   4.4.2.4…   4.4.3…   4.4.4…   4.4.5…   4.4.6…   4.4.8…   4.4.8.7…   4.4.9…   4.4.11…   4.4.11.7…   4.4.11.17…   4.4.12…   4.5…   4.6…   4.7   5…   5.2…   5.3…   5.4…   5.9…   6…   7…   7.1.2…   7.3…   A   B…   D   E…   G   H…   I…   L…   M… 
4.4.11.7 EFUAC_AIC (UAC Access Identities Configuration)  4.4.11.8 EFSUCI_Calc_Info (Subscription Concealed Identifier Calculation Information EF)  4.4.11.9 EFOPL5G (5GS Operator PLMN List)  4.4.11.10 EFSUPI_NAI (SUPI as Network Access Identifier)  4.4.11.11 EFRouting_Indicator (Routing Indicator EF)  4.4.11.12 EFURSP (URSP)  4.4.11.13 EFTN3GPPSNN (Trusted non-3GPP Serving network names list)  4.4.11.14 EFCAG (Pre-configured CAG information list EF)  4.4.11.15 EFSOR-CMCI (Steering Of Roaming - Connected Mode Control Information) 
...

 

4.4.11.7  EFUAC_AIC (UAC Access Identities Configuration)  p. 209

If service No. 126 is "available" in EFUST, 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 and TS 24.501.
Identifier: '4F06'Structure: transparentOptional
SFI: '06'
File size: 4 bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to 4UAC access identities configurationM4 bytes
UAC access identities configuration
Contents:
Configuration of certain Unified Access Control (UAC) access identities specified in clause 4.5.2 ofTS 24.501.
Coding:
Each access identity configuration is coded on one bit.
Byte 1:
b8 b7 b6 b5 b4 b3 b2 b1
RFU 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.
 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.
 
Bytes 2 to 4:
Bits b1 to b8 are RFU.
Up

4.4.11.8  EFSUCI_Calc_Info (Subscription Concealed Identifier Calculation Information EF)  p. 210

If "SUCI calculation is to be performed by the ME" (i.e. service No. 124 is "available" in No. 125 is not "available" in No. 124 is "available" in No. 125 is "available" in No. 124 is not "available" in EFUST, this file shall not be available to the ME.
Identifier: '4F07'Structure: transparentOptional
SFI: '07'
File size: X bytes (X ≥ 2)Update activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to ZProtection Scheme Identifier List data objectMZ bytes
Z+1 to Y+ZHome Network Public Key List data objectCY 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'M1
Protection Scheme Identifier List data object lengthL1MNote 1
Protection Scheme Identifier 1 (Highest priority)--O1
Key Index 1--C (Note 2)1
Protection Scheme Identifier 2--O1
Key Index 2--C (Note 2)1
…
Protection Scheme Identifier N (Lowest priority)--O1
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 TS 33.501 and it is coded in one byte as follows:
b8 b7 b6 b5 b4 b3 b2 b1
RFU, bit = 0 Protection Scheme identifier coded as described in TS 24.501
 
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'C1
Home Network Public Key List data object lengthL1CNote 1
Home Network Public Key 1 Identifier tag'80'C1
Home Network Public Key 1 Identifier lengthL2CNote 1
Home Network Public Key 1 Identifier--CL2
Home Network Public Key 1 tag'81'C1
Home Network Public Key 1 lengthL3CNote 1
Home Network Public Key 1--CL3
…
Home Network Public Key N Identifier tag'80'O1
Home Network Public Key N Identifier lengthL4ONote 1
Home Network Public Key N Identifier--OL4
Home Network Public Key N tag'81'O1
Home Network Public Key N lengthL5ONote 1
Home Network Public Key N--OL5
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 TS 23.003 and it is coded in one byte as described in TS 24.501.
The Home Network Public Key is coded in hexadecimal digits as described in RFC 7748 (for Protection Scheme Profile A) and in RFC 5480 (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).
Up

4.4.11.9  EFOPL5G (5GS Operator PLMN List)  p. 212

If service No. 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 EFPNN or EFPNNI with the TAI. The ME shall use this EF in association with the EFPNN 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. The PLMN Network Name may also be provided in a graphical format in EFPNNI. 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 fixedOptional
SFI: '08'
Record length: X bytes, (X ≥ 10)Update activity: low
Access Conditions:
READALWAYS
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to 9Tracking Area IdentityM9 bytes
10PLMN Network Name Record IdentifierM1 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
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
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
A value in the range '01' to 'FE' indicates the record number in EFPNN that shall be displayed as the registered PLMN name. It also indicates the record number in EFPNNI that may be displayed as the registered PLMN name icon.
Up

4.4.11.10  EFSUPI_NAI (SUPI as Network Access Identifier)  p. 213

If service No. 130 is "available", this file shall be present.
This EF contains the SUPI in NAI format consisting of a:
The SUPI contained in this EF shall not be an IMSI.
Identifier: '4F09'Structure: transparentOptional
SFI: '09'
File size: Z bytes (Z ≥ X)Update activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XNetwork Access Identifier TLV data objectMX 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'M1
LengthLMNote
Network Specific Identifier--ML
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 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'M1
LengthLMNote
Global Line Identifier--ML
NOTE:
The length is coded according to ISO/IEC 8825-1 [35].
The Global Line Identifier as specified in clause 28.16.2 of TS 23.003.
When SUPI type is Global Cable Identifier (GCI):
Description Value M/O Length (bytes)
Global Cable Identifier Tag'82'M1
LengthLMNote
Global Cable Identifier--ML
NOTE:
The length is coded according to ISO/IEC 8825-1 [35].
The Global Cable Identifier as specified in clause 28.15.2 of TS 23.003.
Up

4.4.11.11  EFRouting_Indicator (Routing Indicator EF)  p. 214

If service No. 124 is "available" in EFUST, this file shall be present. This EF contains Routing Indicator needed by the ME or by the USIM for SUCI calculation.
Identifier: '4F0A'Structure: transparentOptional
SFI: '0A'
File size: 4 bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to 4Routing IndicatorM4 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 TS 23.003.
Coding:
Bytes 1 to 2:
The Routing Indicator is coded in 2 bytes as specified in TS 24.501. 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 TS 24.501.
Bytes 3 to 4:
RFU.
Up

4.4.11.12  EFURSP (URSP) |R16|  p. 215

If service No. 132 is "available" in EFUST, 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 TS 24.526.
Identifier: '4F0B'Structure: BER-TLVOptional
SFI: Optional
File size: > (L0 + X1+X2+…+XN +L1+L2+…+LN + 3 x N) bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to L0 +1 +X1+X2+…+XN +L1+L2+…+LN + 3 x NURSP Rules data objectOL0 +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'O1 byte
URSP Rules lengthX1+X2+…+XN +L1+L2+…+LN + 3 x NOL0 bytes (note)
PLMN 1O3 bytes
Total length of URSP rules for PLMN 1X1OL1 bytes (note)
UE Route Selection Policy rules for PLMN 1OX1 bytes
PLMN 2O3 bytes
Length of URSP rules for PLMN 2X2OL2 bytes (note)
UE Route Selection Policy rules for PLMN 2OX2 bytes
…
PLMN NO3 bytes
Length of URSP rules for PLMN NXNOLN bytes (note)
UE Route Selection Policy rules for PLMN NOXN 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.
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 TS 24.526.
Up

4.4.11.13  EFTN3GPPSNN (Trusted non-3GPP Serving network names list) |R16|  p. 216

If service No. 135 is "available" in EFUST, 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 (see clause 7.1a).
Identifier: '4F0C'Structure: transparentOptional
SFI: '0C '
File size: Z (≥1) bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1Number of Serving network name TLV data objects (n)M1
2 to X1+11st Serving network name TLV data objectOX1 bytes
…
2+X1+..+Xn-1Nth Serving network name TLV data objectOXn 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'M1
LengthXMNote
Serving network name--MX
NOTE:
The length is coded according to ISO/IEC 8825-1 [35].
 
The serving network name is defined as specified in TS 33.501 (see clauses 6.1.1.4) and shall be encoded to an octet string according to UTF-8 encoding rules as specified in RFC 3629.
Up

4.4.11.14  EFCAG (Pre-configured CAG information list EF) |R17|  p. 217

If service No. 137 is "available" in EFUST, this file shall be present. This EF contains a pre-configured CAG information list used by the ME as specified in clause 3.8 of TS 23.122.
Identifier: '4F0D'Structure: transparentOptional
SFI: '0D'
File size: Z (≥2) bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to 2Length of CAG information list entriesM2
3 to 2+X11st CAG information list entryOX1 bytes
…
3+X1+..+XN-1
to
2+X1+…+XN		Nth CAG information list entryOXN bytes
Length of CAG information list entries
Total length of all the CAG information list entries that follow
CAG information list entry
Each CAG information list entry contains either:
  1. an entry in the CAG information list , the coding of which is specified in clause 9.11.3.18A of TS 24.501, Figure 9.11.3.18A.2 and Table 9.11.3.18A.1; or
  2. an entry for HPLMN or EHPLMN including a CAG-ID range, the coding of which is as shown below.
    b8 b7 b6 b5 b4 b3 b2 b1
    Length of entry including a CAG-ID range contentsoctet 3+X1
    +...+Xm-1
    MCC digit 2MCC digit 1octet 4+X1
    +...+Xm-1
    MNC digit 3MCC digit 3octet 5+X1
    +...+Xm-1
    MNC digit 2MNC digit 1octet 6+X1
    +...+Xm-1
    0
    Spare    		0
    Spare    		0
    Spare    		0
    Spare    		0
    Spare    		0
    NOTE 2    		1
    NOTE 1    		CAG
    only    		octet 7+X1
    +...+Xm-1
    CAG-ID rangeoctet 8+X1
    +...+Xm-1
    octet 15+X1
    +...+Xm-1
     
    where:
    1. 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
    2. a CAG-ID range contains two CAG-IDs. The coding of the CAG-ID is defined as the CAG-Identifier in TS 23.003. 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.
Up

4.4.11.15  EFSOR-CMCI (Steering Of Roaming - Connected Mode Control Information) |R17|  p. 218

If service No. 138 is "available" in EFUST, this file shall be present.
This EF contains SOR-CMCI parameters as specified in TS 24.501
Identifier: '4F0E'Structure: transparentOptional
SFI: '0E'
File size: Z bytes (Z ≥ X)Update activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XSOR-CMCI data objectOX bytes
SOR-CMCI data object
Coding
Length Description Coding Status
1SOR-CMCI data object tag'80'O
1 to L (L ≤ 4)SOR-CMCI data object lengthAs defined in TS 31.101 for BER-TLV structured filesO
X-1-L bytesSOR-CMCI parameters As specified in clause 9.11.3.51 of TS 24.501 and start from octet (o+3) of SOR-CMCI as defined in Figure 9.11.3.51.7 of TS 24.501. O
As defined in clause C.4.1 of TS 23.122, '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 clause C.4.2 of TS 23.122 applies.
Up

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

Up   Top   ToC