4.2.57 EFNETPAR (Network Parameters)
31.1023GPPCharacteristics of the Universal Subscriber Identity Module (USIM) applicationRelease 17TS
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 [28], 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 [33], 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.
NOTE: Currently there is no inter frequency cell information required for the TDD case.
|
Identifier: ‘6FC4’ |
Structure: transparent |
Mandatory |
||||
|
File size: X bytes, (X ≥ 46) |
Update activity: high |
|||||
|
Access Conditions: READ PIN UPDATE PIN DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to X |
TLV object(s) containing GSM/FDD/TDD cell information |
O |
X |
|||
– 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 |
|||