Scribd
Upload
252 views3 pages

UICC Data Object Structure Overview

This document provides specifications for the proprietary template that can be included in the Answer to Reset (ATR) response from a UICC. It defines several Tag-Length-Value (TLV) data objects that may be included, such as the UICC characteristics, application power consumption, memory details, and supported system commands. The TLV objects provide information about the capabilities and requirements of the UICC and any applications on it. The document establishes which TLV objects are mandatory or optional for different types of files and applications on the UICC.

Uploaded by

sdfksd irorooo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
252 views3 pages

UICC Data Object Structure Overview

This document provides specifications for the proprietary template that can be included in the Answer to Reset (ATR) response from a UICC. It defines several Tag-Length-Value (TLV) data objects that may be included, such as the UICC characteristics, application power consumption, memory details, and supported system commands. The TLV objects provide information about the capabilities and requirements of the UICC and any applications on it. The document establishes which TLV objects are mandatory or optional for different types of files and applications on the UICC.

Uploaded by

sdfksd irorooo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

89 ETSI TS 102 221 V17.1.

0 (2022-02)

b8 b7 B6 b5 b4 b3 b2 b1 Meaning
1 X X X X X X X RFU

• Data coding byte.

Coding: The data coding byte is coded according to ISO/IEC 7816-4 [12]. The actual value shall not be
checked nor used by the terminal.

• Record length.

Contents: Record length specifies the length of a record when a record structured file has been selected.

Coding: The record length shall be present if a record structured file (i.e. for linear fixed or cyclic files) is
selected. In this case it indicates the length the records on 2 bytes. Most significant byte comes
first in the value field.

• Number of records.

Contents: Number of records specifies the number of records in a record structured file.

Coding: The number of records shall be present if a record structured file (i.e. for linear fixed or cyclic
files) is selected. In this case it indicates the number of records on 1 byte.

[Link].4 File identifier


Byte(s) Description Value Length
1 Tag '83' 1
2 Length '02' 1
3 to 4 File identifier 2

[Link].5 DF name
Byte(s) Description Value Length
1 Tag '84' 1
2 Length 1 X 16 1
3 to 2+X DF name X

DF name is a string of bytes, the AID, which is used to uniquely identify an application dedicated file in the card.

[Link].6 Proprietary information

[Link].6.0 Data object structure

This is a constructed TLV object.

Byte(s) Description Length


1 Proprietary information constructed Tag = 'A5' 1
2 Length 1
3 to 2+X Proprietary data, constructed X

The following TLV objects are defined for the proprietary template (tag 'A5'). Additional private TLV objects (bits b7
and b8 of the first byte of the tag set to '1') may be present after the TLV objects defined in clause [Link].6. For
example, a manufacturer, issuer, or application provider specific TLV object may be present. If more than one TLV
object with the same tag is indicated in this constructed TLV they shall be grouped together as the order in which they
appear is used to specify the usage.

ETSI
90 ETSI TS 102 221 V17.1.0 (2022-02)

Description Tag Status Clause


UICC characteristics '80' C1 [Link].6.1
Application power consumption '81' C2 [Link].6.2
Minimum application clock frequency '82' C3 [Link].6.3
Amount of available memory '83' C4 [Link].6.4
File details '84' C5 [Link].6.5
Reserved file size '85' C5 [Link].6.6
Maximum file size '86' C6 [Link].6.7
Supported system commands '87' C7 [Link].6.8
Specific UICC environmental conditions '88' C8 [Link].6.9
Platform to Platform CAT Secured APDU '89' C9 [Link].6.10
C1: The UICC characteristics are mandatory for the MF.
C2: Application power consumption, is optional for ADFs. This TLV object shall not be present for
the MF, an EF or DF.
C3: This TLV object shall not be present for the MF, DF or an EF. For an ADF, it is optional.
C4: This TLV object shall not be present for a transparent, linear fixed or cyclic EF. It is
mandatory for BER-TLV structured Efs. For an ADF, DF or the MF, it is optional.
C5: This TLV object shall only be present for BER-TLV structured Efs, for which it is mandatory.
C6: This TLV object shall only be present for BER-TLV structured Efs, for which it is optional.
C7: This TLV object is mandatory for the MF and optional for any other DF.
C8: This TLV object shall be present for the MF only if the UICC supports specific UICC
environmental conditions. It shall not be present for an ADF, DF or an EF.
C9: This TLV object shall not be present for a DF, an ADF or an EF. For the MF, it is optional.

An application may supply more than one application power consumption or minimum application clock frequency
Data Object (DO).

[Link].6.1 UICC characteristics


Byte(s) Description Value Length
1 Tag '80' 1
2 Length '01' 1
3 UICC characteristics byte (see table 11.6) 1

Table 11.6: UICC characteristics byte


b8 b7 b6 b5 b4 b3 b2 b1 Meaning
- - - - X X - 1 Clock stop allowed
- - - - 0 0 - 1 No preferred level
- - - - 0 1 - 1 High level preferred
- - - - 1 0 - 1 Low level preferred
- - - - 1 1 - 1 RFU
- - - - X X - 0 Clock stop not allowed
- - - - 0 0 - 0 Never
- - - - 0 1 - 0 Unless at high level
- - - - 1 0 - 0 Unless at low level
- - - - 1 1 - 0 RFU
- - - X - - - - Supply voltage class A
- - X - - - - - Supply voltage class B
- X - - - - - - Supply voltage class C
X - - - - - - - Supply voltage class D
- - - - - - X - RFU (shall be set to 0)

If bit b1 is coded '1', stopping the clock is allowed at high or low level. In this case bit b3 and b4 give information about
the preferred level (high or low, respectively) at which the clock may be stopped.

If b1 is coded '0', the clock may be stopped only if the mandatory condition b3 = '1' (i.e. stop at high level) or b4 = '1'
(i.e. stop at low level) is fulfilled. If all 3 bits are coded '0', then the clock shall not be stopped.

A supply voltage class, as defined in clause 6.2.1, is supported if the bit is coded as a '1'. If the voltage class is not
supported the bit is coded as '0'.

ETSI
91 ETSI TS 102 221 V17.1.0 (2022-02)

[Link].6.2 Application power consumption

The application power consumption is indicated by tag '81' within the constructed TLV object. The first byte indicates
the supply voltage at which the power consumption is measured. The coding of this byte is the same as for the supply
voltage class indication in the ATR, see table 6.1. Unused bits are set to RFU. The second byte indicates the power
consumption in mA. Bits b8 to b7 are RFU. Bits b6 to b1 indicates the power consumption of the application in mA.
The power consumption is measured at the frequency indicated in the "Power consumption reference frequency" field
for the application, averaged over 1 ms or at the maximum clock frequency supported by the UICC if no indication is
given. The terminal shall ignore the application power consumption values '00' and 'FF'. A value higher than 3C shall
not be interpreted by the terminal and is not to be used. The terminal may still accept the application.

The terminal shall evaluate the power consumption value given in the response. If the power supply class indicated in
the response is not the currently used the terminal shall recalculate the value to the currently used supply voltage class.
The terminal shall accept the application if the recalculated value is within the specification limits set for the currently
used supply voltage class. The terminal may accept an application that exceeds the specified value if it can support the
power consumption indicated by the application.

Byte(s) Description Value Length


1 Tag '81' 1
2 Length '03' 1
3 Supply voltage class at which the power 1
consumption is measured
4 Application power consumption '01' to '3C' 1
5 Power consumption reference frequency '0A' to 'FF' 1

The power consumption reference frequency is coded in Hexadecimal format. The resolution is 0,1 MHz, i.e. '0A' is
1 MHz and 'FE' is 25,4 MHz. The value 'FF' indicates that no reference frequency is indicated.

[Link].6.3 Minimum application clock frequency

The application minimum clock frequency is indicated by tag '82' within the constructed TLV object. This TLV object
indicates to the terminal the minimum clock frequency required by the application. It is up to the application to specify
a value that is required for commands or procedures to be executed within the required time. An application may
indicate one or more application minimum clock frequencies if required. In case that more than one TLV object is
indicated it is up to the application to specify for what purpose the different values are used, i.e. the order of the TLV
objects within the constructed TLV is relevant.

Byte(s) Description Value Length


1 Tag '82' 1
2 Length '01' 1
3 Application minimum clock frequency '0A' to 'FF' 1

The minimum clock frequency is coded in Hexadecimal format. The resolution is 0,1 MHz, i.e. '0A' is 1 MHz and 'FE'
is 25,4 MHz. If this TLV object is not present or the value is 'FF', no minimum application clock frequency is indicated.

[Link].6.4 Amount of available memory

Amount of memory which is available for DFs or Efs creation under the selected DF (and ADFs under the MF) or for
creation of TLV objects in a BER-TLV structured EF.

Byte(s) Description Value Length


1 Tag '83' 1
2 Length X, X 2 1
3 to 2+X Number of data bytes X

The most significant byte comes first in the value field.

For BER-TLV structured EF this value shall be the maximum amount of bytes that is available in the EF for the next
TLV object to be created. This shall include the space required for the tag and the length field. If a maximum file size is
defined for the file, it shall not be exceeded, if an object is created with the indicated available size.

ETSI

Common questions

Powered by AI

UICC characteristics, identified by the tag '80', are mandatory for the Master File (MF), indicating its fundamental configuration, such as clock stop preferences and supported voltage classes. For Application Dedicated Files (ADFs), these characteristics can be optional, allowing flexibility depending on the application's requirements and the end-use scenario the application is designed for .

The UICC characteristics byte determines the clock stop feature based on bits b1, b3, and b4. If b1 is set to '1', clock stops are allowed variably with preferences indicated by b3 and b4 for high or low levels. If b1 is '0', then stopping is conditional upon the high or low level conditions expressed by b3 or b4, ensuring controlled cessation of the clock relative to dynamic voltage levels .

The TLV structure allows for dynamic memory allocation by specifying the amount of available memory for TLV object creation. This is recorded using Tag '83', indicating the maximum bytes available in the EF, including space for the tag and length field. It ensures efficient memory management by not exceeding defined file sizes and allocating just enough space for new TLV objects .

The Minimum Application Clock Frequency TLV object, tagged '82', must specify a frequency in hexadecimal (from '0A' 1 MHz to 'FE' 25.4 MHz). It lays out minimum operating conditions for application commands, ensuring reliable execution within defined time limits. Its optional nature allows adaptability for differing application needs, indicating a flexible design to accommodate various operational requirements .

In ETSI TS 102 221, data coding bytes conform to ISO/IEC 7816-4 standards, providing an interoperable framework crucial for secure and standardized data handling in smart card applications. While their specific values remain unchecked by terminals, their presence underpins all data transactions, ensuring consistency across different systems .

The Specific UICC Environmental Conditions TLV object is optional, aimed at supporting unique operational conditions for applications dependent on their physical environment. It only appears in the Master File if the UICC is explicitly designed to handle such conditions, emphasizing adaptability to particular environmental stressors, enhancing reliability and lifecycle under specified use scenarios .

The Application Power Consumption TLV object, tagged '81', is critical as it specifies the power requirements at specific supply voltage classes, impacting terminal compatibility. By stipulating power consumption and recalibrating if necessary, terminals can determine if applications can be supported without exceeding their power provisions. This ensures optimal performance without damaging circuitry due to incorrect power settings .

The Proprietary Information TLV object may include additional private TLV objects if bits b7 and b8 of the first byte of their tag are set to '1'. Their sequence is critical because it specifies their usage. When multiple TLV objects with the same tag appear, they must be grouped together, allowing the order to dictate how they are to be applied or interpreted .

Supply voltage class indicators determine the voltage context in which application power consumption is measured. Each voltage class corresponds to a particular bit setting in the application power consumption byte. This direct relationship ensures the terminal recalculates power needs according to current voltage settings, allowing accurate assessment of sustainable application operations .

The record length is determined based on the selection of a record-structured file, such as linear fixed or cyclic files. It is indicated over two bytes with the most significant byte coming first in the value field. This parameter is significant because it specifies the length of each record, which is essential for data organization and retrieval within the file .

You might also like