10.6 DFs at the telecom level

11.113GPPRelease 1999Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) InterfaceTS

DFs may be present as child directories of DFTELECOM. The following has been defined.

DFGRAPHICS ‘5F50’

10.6.1 Contents of files at the telecom graphics level

The EFs in the Dedicated File DFGRAPHICS contain graphical information.

10.6.1.1 EFIMG (Image)

Each record of this EF identifies instances of one particular graphical image, which graphical image is identified by this EF’s record number.

Image instances may differ as to their size, having different resolutions, and the way they are coded, using one of several image coding schemes.

As an example, image k may represent a company logo, of which there are i instances on SIM, of various resolutions and perhaps encoded in several image coding schemes. Then, the i instances of the company’s logo are described in record k of this EF.

Identifier: ‘4F20’

Structure: linear fixed

Optional

Record length: 9n+1 or 9n+2 bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1

Number of Actual Image Instances

M

1 byte

2 to 10

Descriptor of Image Instance 1

M

9 bytes

11 to 19

Descriptor of Image Instance 2

O

9 bytes

:

9 (n-1) + 2 to 9n + 1

Descriptor of Image Instance n

O

9 bytes

9n + 2

RFU

O

1 byte

‑ Number of Actual Image Instances

Contents: this byte gives the number of actual image instances described in the following data items (i.e. unused descriptors are not counted).

Coding: binary

‑ Image Instance Descriptor

Contents: a description of an image instance

Coding: see below

Byte 1: Image Instance Width

Contents:

this byte specifies the image instance width, expressed in raster image points.

Coding:

binary.

Byte 2: Image Instance Height

Contents:

this byte specifies the image instance height, expressed in raster image points.

Coding:

binary.

Byte 3: Image Coding Scheme

Contents:

this byte identifies the image coding scheme that has been used in encoding the image instance.

Coding:

’11’ – basic image coding scheme as defined in annex G;

’21’ – colour image coding scheme as defined in annex G;

other values are reserved for future use.

Bytes 4 and 5: Image Instance File Identifier

Contents:

these bytes identify an EF which is the image instance data file (see subclause 10.6.1.2), holding the actual image data for this particular instance.

Coding:

byte 4: high byte of Image Instance File Identifier;

byte 5: low byte of Image Instance File Identifier.

Bytes 6 and 7: Offset into Image Instance File

Contents:

these bytes specify an offset into the transparent Image Instance File identified in bytes 4 and 5.

Coding:

byte 6: high byte of offset into Image Instance File;

byte 7: low byte of offset into Image Instance File

Bytes 8 and 9: Length of Image Instance Data

Contents:

these bytes yield the length of the image instance data, starting at the offset identified in bytes 6 and 7. For the colour image coding scheme, as defined in annex G, the length of image instance data excludes the CLUT.

Coding:

byte 8: high byte of Image Instance Data length;

byte 9: low byte of Image Instance Data length.

NOTE: Transparent image instance data longer than 256 bytes may be read using successive READ BINARY commands.

10.6.1.2 Image Instance Data Files

Residing under DFGRAPHICS, there may be several image instance data files. These EFs containing image instance data shall have the following attributes.

Identifier: ‘4FXX’

Structure: transparent

Optional

Record length: Y bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to Y

Image Instance Data

M

Y bytes

Contents and coding:

Image instance data are accessed using the image instance descriptors provided by EFIMG (see subclause 10.6.1.1).

The identifier ‘4FXX’ shall be different from one image instance data file to the other. For the range of ‘XX’, see subclause 6.6. The length Y may be different from one image instance data file to the other.