4.4.9 Contents of files at the DF ACDC level
31.1023GPPCharacteristics of the Universal Subscriber Identity Module (USIM) applicationRelease 17TS
4.4.9.1 Introduction
This clause describes the additional files that are used for ACDC configuration.
DFACDC shall be present at the ADFUSIM level if service nº108 is "available" in EFUST (USIM Service Table).
4.4.9.2 EFACDC_LIST (ACDC List)
If service n°108 is "available", this file shall be present.
This EF contains the link to EFs containing the ACDC for each operating system identifier. The ME parses the content of the EFACDC_LIST and retrieves the file id and optionally the SFI to further access the relevant ACDC configuration.
|
Identifier: ‘4F01’ |
Structure: transparent |
Optional |
||||
|
SFI: ’01’ |
||||||
|
File size: Z bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to L1 |
ACDC OS TLV data object 1 |
M |
L1 bytes |
|||
|
L1+1 to L1+L2 |
ACDC OS TLV data object 2 |
O |
L2 bytes |
|||
|
: |
: |
: |
: |
|||
|
L1+L2+…+L(n-1)+1 to L1+L2+…+Ln |
ACDC OS TLV data object n |
O |
Ln bytes |
|||
ACDC OS TLV data object
|
Description |
Value |
M/O/C |
Length (bytes) |
|
ACDC OS tag |
‘A0’ |
M |
1 |
|
Length |
X+19 |
M |
Note |
|
OS Id |
— |
M |
16 |
|
File Id |
— |
M |
2 |
|
SFI |
— |
M |
1 |
|
RFU |
— |
O |
X |
|
Note: The length is coded according to ISO/IEC 8825-1 [35] |
|||
– OS Id
Contents:
The Operating System identifier
Coding:
A Universally Unique IDentifier (UUID) as specified in IETF RFC 4122 [80].
– File Id
Contents:
File Id of the EF containing the ACDC configuration for the Operating System
Coding:
According to TS 31.101 [11]
– SFI
Contents:
Short File Identifier of the EF containing configuration for the Operating System
Coding:
According to TS 31.101 [11]. The value ‘0’ indicates that SFI is not allocated for the file.
Unused bytes shall be set to ‘FF’.
4.4.9.3 EFACDC_OS_CONFIG (ACDC OS configuration)
This EF contains the ACDC configuration for a specific Operating System. The ME retrieves ths file id or the SFI of the file from the EFACDC_LIST.
|
Identifier: ‘4FXX’ |
Structure: transparent |
Optional |
||||
|
SFI: ‘XX’ (optional) |
||||||
|
File size: Z bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to L1 |
ACDC App Id 1 |
M |
L1 bytes |
|||
|
L1+1 to L1+L2 |
ACDC App Id 2 |
O |
L2 bytes |
|||
|
: |
: |
: |
||||
|
L1+L2+…+L(n-1)+1 to L1+L2+…+Ln |
ACDC App Id n |
O |
Ln bytes |
|||
ACDC App Id
|
Description |
Value |
M/O/C |
Length (bytes) |
|
ACDC App Id tag |
‘A0’ |
M |
1 |
|
Length |
X |
M |
Note |
|
ACDC category tag |
’80’ |
M |
1 |
|
Length |
1 |
M |
1 |
|
ACDC category |
— |
M |
1 |
|
OS App Id tag |
’81’ |
M |
1 |
|
Length |
L |
M |
Note |
|
OS App Id |
— |
M |
L |
|
Note: The length is coded according to ISO/IEC 8825-1 [35] |
|||
– ACDC category
Contents:
The ACDC category indicates the category to which the identified application belongs.
Coding:
As the ACDCCategory leaf in 24.105 [81]
– OS App Id
Contents:
indicates an OS specific application identifier
Coding:
As the OSAppId leaf in 24.105 [81]
Unused bytes shall be set to ‘FF’.