4.4.1 Contents of files at the DF SoLSA level
31.1023GPPCharacteristics of the Universal Subscriber Identity Module (USIM) applicationRelease 17TS
This only applies if the Support of Localised Service Areas is supported, as indicated by Service Number 23 in the USIM Service Table and specified in TS 23.073 [23] .
The Efs contain information about the users subscribed local service areas.
4.4.1.1 EFSAI (SoLSA Access Indicator)
This EF contains the ‘LSA only access indicator’. This EF shall always be allocated if DFSoLSA is present.
If the indicator is set, the network will prevent terminated and/or originated calls when the MS is camped in cells that are not included in the list of allowed LSAs in EFSLL. Emergency calls are, however, always allowed.
The EF also contains a text string which may be displayed when the MS is out of the served area(s).
|
Identifier: ‘4F30’ |
Structure: transparent |
Optional |
||||
|
File size: X + 1 bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 |
LSA only access indicator |
M |
1 byte |
|||
|
2 to X+1 |
LSA only access indication text |
M |
X bytes |
|||
‑ LSA only access indicator
Contents: indicates whether the MS is restricted to use LSA cells only or not.
Coding:
|
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
||||||||||||
|
b1=0: LSA only access not activated b1=1: LSA only access activated |
|||||||||||||||||||
|
RFU |
|||||||||||||||||||
‑ LSA only access indication text
Contents: text to be displayed by the ME when it’s out of LSA area.
Coding: the string shall use either
– the SMS default 7‑bit coded alphabet as defined in TS 23.038 [5] with bit 8 set to 0. The alpha identifier shall be left justified. Unused bytes shall be set to ‘FF’; or
– one of the UCS2 coded options as defined in the annex of TS 31.101 [11].
4.4.1.2 EFSLL (SoLSA LSA List)
This EF contains information describing the LSAs that the user is subscribed to. This EF shall always be allocated if DFSoLSA is present.
Each LSA is described by one record that is linked to a LSA Descriptor file. Each record contains information of the PLMN, priority of the LSA, information about the subscription and may also contain a text string and/or an icon that identifies the LSA to the user. The text string can be edited by the user.
|
Identifier: ‘4F31’ |
Structure: linear fixed |
Optional |
||||
|
Record length: X + 10 bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE PIN DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to X |
LSA name |
O |
X bytes |
|||
|
X+1 |
Configuration parameters |
M |
1 byte |
|||
|
X+2 |
RFU |
M |
1 byte |
|||
|
X+3 |
Icon Identifier |
M |
1 byte |
|||
|
X+4 |
Priority |
M |
1 byte |
|||
|
X+5 to X+7 |
PLMN code |
M |
3 bytes |
|||
|
X+8 to X+9 |
LSA Descriptor File Identifier |
M |
2 byte |
|||
|
X+10 |
LSA Descriptor Record Identifier |
M |
1 byte |
|||
‑ LSA name
Contents: LSA name string to be displayed when the ME is camped in the corresponding area, dependant on the contents of the LSA indication for idle mode field.
Coding: the string shall use either
– the SMS default 7‑bit coded alphabet as defined in TS 23.038 [5] with bit 8 set to 0. The alpha identifier shall be left justified. Unused bytes shall be set to ‘FF’; or
– one of theUCS2 code options defined in the annex of TS 31.101 [11].
‑ Configuration parameters
Contents: Icon qualifier, control of idle mode support and control of LSA indication for idle mode.
Coding:
|
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
||||||||||||
|
Icon qualifier |
|||||||||||||||||||
|
Idle mode support |
|||||||||||||||||||
|
LSA indication for idle mode |
|||||||||||||||||||
|
RFU |
|||||||||||||||||||
Icon qualifier:
Contents: The icon qualifier indicates to the ME how the icon is to be used.
B2, b1: 00: icon is not to be used and may not be present
01: icon is self-explanatory, i.e. if displayed, it replaces the LSA name
10: icon is not self-explanatory, i.e. if displayed, it shall be displayed together with the LSA name
11: RFU
Idle mode support:
Contents: The idle mode support is used to indicate whether the ME shall favour camping on the LSA cells in idle mode.
B3 = 0: Idle mode support disabled
b3 = 1: Idle mode support enabled
LSA indication for idle mode:
Contents: The LSA indication for idle mode is used to indicate whether or not the ME shall display the LSA name when the ME is camped on a cell within the LSA.
B4 = 0: LSA indication for idle mode disabled
b4 = 1: LSA indication for idle mode enabled
Bits b5 to b8 are RFU (see clause 9.3).
– Icon Identifier
Contents: The icon identifier addresses a record in EFIMG.
Coding: binary.
‑ Priority
Contents: Priority of the LSA which gives the ME the preference of this LSA relative to the other LSAs.
Coding:
|
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
||||||||||||
|
Priority |
|||||||||||||||||||
|
RFU |
|||||||||||||||||||
‘0’ is lowest priority, ‘F’ is highest.
‑ PLMN code
Contents: MCC + MNC for the LSA.
Coding: according to TS 24.008 [9] and EFLOCI.
– LSA Descriptor File Identifier:
Contents: these bytes identify the EF which contains the LSA Descriptors forming the LSA.
Coding: byte X+8: high byte of the LSA Descriptor file;
byte X+9: low byte of the LSA Descriptor file.
– LSA Descriptor Record Identifier:
Contents: this byte identifies the number of the first record in the LSA Descriptor file forming the LSA.
Coding: binary.
4.4.1.3 LSA Descriptor files
Residing under DFSoLSA, there may be several LSA Descriptor files. These Efs contains one or more records again containing LSA Descriptors forming the LSAs. LSAs can be described in four different ways. As a list of LSA Ids, as a list of LAC + Cis, as a list of Cis or as a list of LACs. As the basic elements (LSA ID, LAC + CI, CI and LAC) of the four types of lists are of different length, they can not be mixed within one record. Different records may contain different kinds of lists within the Efs. Examples of codings of LSA Descriptor files can be found in annex F.
|
Identifier: ‘4FXX’ |
Structure: linear fixed |
Optional |
||||
|
Record length: n*X+2 bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 |
LSA descriptor type and number |
M |
1 byte |
|||
|
2 to X+1 |
1st LSA Descriptor |
M |
X bytes |
|||
|
X+2 to 2X+1 |
2nd LSA Descriptor |
M |
X bytes |
|||
|
: |
: |
: |
: |
|||
|
(n-1)*X+2 to n*X+1 |
nth LSA Descriptor |
M |
X bytes |
|||
|
n*X+2 |
Record Identifier |
M |
1 byte |
|||
– LSA descriptor type and number:
Contents: The LSA descriptor type gives the format of the LSA descriptor and the number of valid LSA Descriptors within the record.
Coding:
|
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
||||||||||||
|
LSA descriptor type |
|||||||||||||||||||
|
Number of LSA Descriptors |
|||||||||||||||||||
LSA descriptor type:
Contents: Gives the format of the LSA Descriptors.
B2, b1: 00: LSA ID.
01: LAC + CI
10: CI
11: LAC
Number of LSA Descriptors:
Contents: Gives the number of valid LSA Descriptors in the record.
Coding: binary, with b8 as MSB and b3 as LSB leaving room for 64 LSA Descriptors per record.
‑ LSA Descriptor
Contents: Dependant of the coding indicated in the LSA descriptor type:
– in case of LSA ID the field length ‘X’ is 3 bytes;
– in case of LAC + CI the field length ‘X’ is 4 bytes;
– in case of CI the field length ‘X’ is 2 bytes;
– in case of LAC the field length ‘X’ is 2 bytes.
Coding: according to TS 24.008 [9].
– Record Identifier:
Contents: This byte identifies the number of the next record containing the LSA Descriptors forming the LSA.
Coding: record number of next record. ‘FF’ identifies the end of the chain.
This file utilises the concept of chaining as for EFEXT1.
The identifier ‘4FXX’ shall be different from one LSA Descriptor file to the other and different from the identifiers of EFSAI and EFSLL. For the range of ‘XX’, see 3GPP TS 31.101 [11].