Content for  TS 31.102  Word version:  18.5.0

This EF contains the maximum value of STARTCS or STARTPS. This value is used to control the lifetime of the keys (see TS 33.102).

If service No. 42 is "available", this file shall be present. This EF contains the coding for n PLMNs where n is determined by the operator. This information is determined by the operator and defines the preferred PLMNs in priority order. The first record indicates the highest priority and the nth record indicates the lowest. The EF also contains the Access Technologies for each PLMN in this list. (see TS 23.122)

If service No. 43 is "available", this file shall be present. The HPLMN Selector with access technology data field shall contain the HPLMN code, or codes together with the respected access technology (see TS 23.122).

This EF contains the access rules for files located under the USIM ADF in the UICC. If the security attribute tag '8B' is indicated in the FCP it contains a reference to a record in this file. Structure of EFARR at ADF-level

This EF contains one or more records containing access rule information according to the reference to expanded format as defined in ISO/IEC 7816-4 [20]. Each record represents an access rule. Unused bytes in the record are set to 'FF'. If the card cannot access EFARR , any attempt to access a file with access rules indicated in this EFARR shall not be granted.

This EF contains information concerning the cell frequencies Network Parameter storage may reduce the extent of the terminal search of FDD, TDD or GSM carriers when selecting a cell. The network parameters stored in the USIM shall be in accordance with the procedures specified in this clause. The RF carrier frequency information is stored on 2 bytes and coded on 16 bits starting from 0,0 MHz. Each increment of the 16 bit value is an increment of 200 kHz in frequency. This allows the exact channel frequency to be stored in this data field making it independent of any band information. It is up to the terminal to associate the indicated frequency with a particular band, e.g. GSM 900, GSM 1800 etc. This means that a range from 0 to 13,1 GHz can be covered, with the resolution of 200 kHz. The frequency indicated is always the terminal receiver carrier frequency. The EF provides a minimum storage capacity of 46 bytes in order to provide the capability of storing at least two cell information TLV objects, e.g. GSM/FDD or FDD/TDD in its minimum configuration, i.e. the terminal can rely on the required memory space for storing at least two cell information lists offering 8 GSM neighbour carrier frequencies and 8 Intra/Inter frequencies, respectively. In what configuration the available memory actually is being used is up to the terminal. A terminal shall ignore a TLV object or the value of a carrier frequency which is beyond its capabilities, i.e. an FDD only terminal shall ignore the GSM related frequency information. When updating this file, the terminal shall update it with the current values available in the terminal. Updating of this file shall start from the beginning of the file. The terminal need not respect the structure of any information previously stored, i.e. an FDD only terminal may overwrite the GSM parameters stored in this file by another terminal. The GSM cell information constructed TLV object contains the information of the BCCH channel frequency that the terminal is currently camped on, indicated by tag '80'. The constructed TLV object also contains an indication of up to 32 neighbour BCCH carrier frequencies indicated by tag '81'. In order to store a complete set of GSM network parameters, a total of 72 bytes is required. The terminal shall convert the BCCH channel information, as specified in TS 44.018, received from the network into the corresponding frequency before storing it in the USIM. The FDD cell information constructed TLV object contains the scrambling code information for the intra frequency carrier, tag '80', and the inter frequency scrambling codes, tag '81'. The intra frequency carrier information may contain up to 32 scrambling codes (m) while there is a limitation of the number of inter frequency scrambling codes (n1, n2, n3). The number of inter frequencies that can be indicated is limited to three and the total amount of scrambling codes for the inter frequencies is limited to 32 (n1+n2+n3 ≤ 32), i.e. if only one inter frequency carrier is indicated, it can contain up to 32 scrambling codes. If two or more inter frequency carriers are indicated, a total of 32 scrambling codes can be provided. How the information is split between the inter frequency carriers is determined by the terminal. In order to store a complete set of FDD cell information a total of 146 bytes is required. The terminal shall convert the UARFCN information, as specified in TS 25.101, received from the network into the corresponding frequency before storing it in the USIM. The TDD cell information constructed TLV object has the same structure as the FDD cell information TLV object.

• EFNETPAR Cell Information tags

  Description	Value	Information Element size bytes
  GSM Cell Information Tag	'A0'	1
  Camping Frequency Tag	'80'	1
  Camping Frequency Information		2
  Neighbour Frequency Tag	'81'	1
  Neighbour Frequency Information		2*m (8 ≤ m ≤ 32)
  FDD Cell Information Tag	'A1'	1
  Intra Frequency Information Tag	'80'	1
  Scrambling code Information		2*m (8 ≤ m ≤ 32)
  Inter Frequency Information Tag	'81'	1
  Scrambling code information		2*(n1+n2+n3) (8 ≤ n1+n2+n3 ≤ 32)
  TDD Frequency information Tag	'A2'	1
  Intra Frequency Information Tag	'80'	1
  Cell parameters ID		2*m (8 ≤ m ≤ 32)
  Inter Frequency Information Tag	'81'	1
  Cell parameters ID		2*(n1+n2+n3) (8 ≤ n1+n2+n3 ≤ 32)

 

• GSM Cell Information, if tag 'A0' is present in this EF the content of this TLV is as follows:

  Description	Value	M/O	Length
  GSM Cell Information Tag	'A0'	M	1
  Length	'4+ (2+2*m) (≤70)'	M	1
  Current camped cell BCCH frequency information tag	'80'	M	1
  Length	'02'	M	1
  Current camped BCCH frequency		M	2
  Neighbour Cell BCCH Frequency information tag	'81'	O	1
  Length	2*m (=< 32)	O	1
  Neighbour BCCH carrier frequencies		O	2*m (8 ≤ m ≤ 32)

 

• FDD Cell Information. If tag 'A1' is present in this EF the content of this TLV is as follows:

  Description	Value	M/O	Length
  FDD Cell Information Tag	'A1'	M	1
  Length	4+(2*m)+(4+2*n1)+(4+2*n2)+(4+2*n3) (≤144)	M	1
  FDD Intra Frequency information tag	'80'	M	1
  Length	2+2*m	M	1
  Intra Frequency carrier frequency		M	2
  Intra Frequency scrambling codes		M	2*m (8 ≤ m ≤ 32)
  FDD Inter Frequency information tag (see NOTE 1)	'81'	O	1
  Length	2+2*n (NOTE 2)	O	1
  Inter Frequency carrier frequencies		O	2
  Inter Frequency scrambling codes		O	2*n (NOTE 2)
  NOTE 1: This TLV object may occur up to 3 times within the constructed TLV object depending how many inter frequencies are indicated NOTE 2: n is in this case n1, n2 or n3, 8 ≤ (n1+n2+n3)≤32

 

• TDD Cell Information: If tag 'A2' is present in this EF the content of this TLV is as follows:

  Description	Value	M/O	Length
  TDD Cell Information Tag	'A2'	M	1
  Length	4+(2*m)+(4+2*n1)+(4+2*n2)+(4+2*n3) (≤144)	M	1
  TDD Intra Frequency information tag	'80'	M	1
  Length	2+2*m	M	1
  Intra Frequency carrier frequency		M	2
  Intra Frequency scrambling codes		M	2*m (8 ≤ m ≤ 32)
  TDD Inter Frequency information tag (see NOTE 1)	'81'	O	1
  Length	2+2*n (NOTE 2)	O	1
  Inter Frequency carrier frequencies		O	2
  Inter Frequency scrambling codes		O	2*n (NOTE 2)
  NOTE 1: This TLV object may occur up to 3 times within the constructed TLV object depending how many inter frequencies are indicated NOTE 2: n is in this case n1, n2 or n3, 8 ≤ (n1+n2+n3)≤32

If service No. 45 is "available", this file shall be present. This EF contains the full and short form versions of the network name for the registered PLMN. The ME shall use these versions in place of its own versions of the network name for the PLMN (stored in the ME's memory list), and also in place of the versions of the network name received when registered to the PLMN, as defined by TS 24.008. This file may also contain PLMN additional information to be displayed to the user during the Manual Network Selection procedures as defined in TS 23.122. If the UE is registered in NG-RAN and EFOPL5G is not present, or if the UE is registered in other technologies and EFOPL is not present, then the first record in this EF is used for the default network name when registered in the HPLMN (if the EHPLMN list is not present or is empty) or an EHPLMN (if the EHPLMN list is present).

If service No. 46 is "available", this file shall be present. This EF contains a prioritised list of Location Area Information (LAI) or Tracking Area Identity (TAI) identities that are used to associate a specific operator name contained in EFPNN or EFPNNI with the LAI/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.008 or TS 24.301. 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.