Content for TS 31.102 Word version: 19.1.0

0… 3… 4… 4.2.9… 4.2.17… 4.2.26… 4.2.34… 4.2.44… 4.2.52… 4.2.60… 4.2.68… 4.2.76… 4.2.85… 4.2.93… 4.2.101… 4.2.107… 4.3… 4.4.2… 4.4.2.4… 4.4.3… 4.4.4… 4.4.5… 4.4.6… 4.4.8… 4.4.8.7… 4.4.9… 4.4.11… 4.4.11.7… 4.4.11.17… 4.4.12… 4.5… 4.6… 4.6.5… 4.6.6… 4.7 5… 5.2… 5.3… 5.4… 5.9… 6… 7… 7.1.2… 7.3… A B… D E… G H… I… L… M…

4.6 Contents of DFs at the TELECOM level 4.6.0 List of DFs at the TELECOM level 4.6.1 Contents of files at the DF GRAPHICS level 4.6.1.1 EF_IMG (Image) 4.6.1.2 EF_IIDF (Image Instance Data Files) 4.6.1.3 EF_{ICE_graphics} (In Case of Emergency - Graphics) 4.6.2 Contents of files at the DF PHONEBOOK under the DF TELECOM 4.6.3 Contents of files at the DF MULTIMEDIA level 4.6.3.1 EF_MML (Multimedia Messages List) 4.6.3.2 EF_MMDF (Multimedia Messages Data File) 4.6.4 Contents of files at the DF MCS level 4.6.4.1 EF_MST (MCS Service Table) 4.6.4.2 EF_{MCS_CONFIG} (MCS configuration data)
...

4.6 Contents of DFs at the TELECOM level p. 258

4.6.0 List of DFs at the TELECOM level |R14| p. 258

DFs may be present as child directories of DF_TELECOM. The following DFs have been defined:

DF_GRAPHICS '5F50'.
DF_PHONEBOOK '5F3A'.
(DF for public phone book. This DF has the same structure as DF_PHONEBOOK under ADF USIM).
DF_MULTIMEDIA '5F3B'.
DF_MMSS '5F3C'
(The contents of DF for MMSS are defined in C.S0074-A [53]. This DF for MMSS is not applicable to 3GPP only terminals).
DF_MCS '5F3D'.
DF_V2X '5F3E'.
DF_A2X '5F3F'.

4.6.1 Contents of files at the DF GRAPHICS level p. 258

The EFs in the Dedicated File DF_GRAPHICS contain graphical information.

4.6.1.1 EF_IMG (Image) p. 259

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 in the UICC, 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, (n ≥ 1)

Update activity: low

Access Conditions:

READ	PIN
UPDATE	ADM
DEACTIVATE	ADM
ACTIVATE	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 (see TS 31.101)	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:

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 B;
'21' - colour image coding scheme as defined in Annex B;
'22' - colour image coding scheme with transparency as defined in Annex B;
other values are reserved for future use.

Bytes 4 and 5: Image Instance Data File Identifier

Contents:

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

Coding:

byte 4: high byte of Image Instance Data File Identifier;
byte 5: low byte of Image Instance Data File Identifier.

Bytes 6 and 7: Offset into Image Instance Data File

Contents:

these bytes specify an offset into the transparent Image Instance Data File identified in bytes 4 and 5. The data for this image instance is found starting at this offset in the Image Instance Data File.

Coding:

byte 6: high byte of offset into Image Instance Data File;
byte 7: low byte of offset into Image Instance Data 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 B, 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.

4.6.1.2 EF_IIDF (Image Instance Data Files) p. 260

Residing under DFGRAPHICS, there may be several image instance data files. Each Image Instance Data File contains data for one or more image instances. These EFs containing image instance data shall have the following attributes:

Identifier: '4FXX'

Structure: transparent

Optional

File size: Y bytes

Update activity: low

Access Conditions:

READ	PIN
UPDATE	ADM
DEACTIVATE	ADM
ACTIVATE	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 clause 4.6.1.1).

The identifier '4FXX' shall be different from one image instance data file to the other. For the range of 'XX', TS 31.101. The length Y may be different from one image instance data file to the other.

4.6.1.3 EF_{ICE_graphics} (In Case of Emergency - Graphics) |R9| p. 261

This EF contains ICE graphical information, according to TS 22.101.

This file shall be deactivated if the user does not wish the ICE information contained in this file to be available and activated if the user wishes the ICE information in this file to be available.

For this EF the Total File Size data object shall be present within the FCP template in order for the ME to fit the picture to the available memory.

Structure of EFICE_graphics at DFgraphics-level

Identifier: '4F21'

Structure: BER-TLV

Optional

SFI: Optional

Record length: X

Update activity: low

Access Conditions:

READ	ALWAYS
UPDATE	PIN
DEACTIVATE	PIN or Issuer Specified PIN (see Note)
ACTIVATE	PIN or Issuer Specified PIN (see Note)

Bytes	Description	M/O	Length
1 to X	ICE graphics Data object	M	X bytes

ICE graphics Data Object

Coding of the ICE graphics Data Objects

Length	Description	Coding	Status
1 to T bytes (T ≤ 3)	ICE graphics Data Object tag	As defined in TS 31.101 for BER-TLV structured files	M
1 to L (L ≤ 4)	ICE graphics Data Object length	As defined in TS 31.101 for BER-TLV structured files	M
X-L-T bytes	ICE graphics Content	JPEG format	M

4.6.1.4 Void

4.6.1.5 Void

4.6.2 Contents of files at the DF PHONEBOOK under the DF TELECOM p. 261

This DF has the same structure as DFPHONEBOOK under the ADFUSIM.

4.6.3 Contents of files at the DF MULTIMEDIA level |R6| p. 261

The EFs in the Dedicated File DFMULTIMEDIA contain multimedia information. This DF shall be present if service No. 67 is available, i.e. if the card supports MMS storage.

4.6.3.1 EF_MML (Multimedia Messages List) p. 261

If service No. 67 is "available", this file shall be present.

This file contains information about the MM data stored in EFMMDF. MM information are encapsulated in a BER-TLV data object. Each data object in EFMML points to a corresponding MM in EFMMDF.

Identifier: '4F47'

Structure: BER-TLV

Optional

Update activity: low

Access Conditions:

READ	PIN
UPDATE	PIN
DEACTIVATE	ADM
ACTIVATE	ADM

Bytes	Description	M/O	Length
1 to X	MM Descriptor Data Object(s)	M	X bytes

MM Descriptor Data Object

The content and coding are defined below:

Coding of the MM Descriptor Data Objects

Length	Description	Coding	Status
1 to A bytes (A ≤ 3)	MM Descriptor Data Object tag	As defined in TS 31.101 for BER-TLV structured files	M
1 to B bytes (B ≤ 4)	MM Descriptor Data Object length	As defined in TS 31.101 for BER-TLV structured files	M
1 byte	MMS Implementation tag '80'		M
1 byte	MMS Implementation length		M
1 byte	MMS Implementation	See below	M
1 byte	MM File Identifier / SFI tag '81'		M
1 byte	MM File Identifier / SFI length		M
1 or 2 bytes	MM File Identifier / SFI	See below	M
1 byte	MM Content Data Object Tag tag '82'		M
1 byte	MM Content Data Object Tag length		M
1 to C bytes (C ≤ 3)	MM Content Data Object Tag	See below	M
1 byte	MM Size tag '83'		M
1 byte	MM Size length		M
1 to D bytes (D ≤ 4)	MM Size in bytes	See below	M
1 byte	MM Status tag '84'		M
1 byte	MM Status length		M
2 bytes	MM Status	See below	M
1 byte	MM Alpha Identifier tag '85'		M
1 byte	MM Alpha Identifier length		M
1 to E bytes	MM Alpha Identifier	See below	M

MMS Implementation

Contents:

The MMS Implementation indicates the used implementation type, e.g. WAP.

Coding:

Allocation of bits:

Bit number, Parameter indicated

WAP implementation of MMS

2 to 8

Reserved for future use

Bit value, Meaning

Implementation not supported.

Implementation supported.

MM File Identifier / SFI

Contents:

file identifier or SFI of EFMMDF which contains the actual MM message. If the length of this TLV object is equal to 1 then the content indicates the SFI of the EFMMDF, the SFI is coded on b1 to b5. Otherwise the TLV contains the file identifier.

Coding:

according to TS 31.101.

MM Content Data Object Tag

Contents:

tag indentifying a MM (i.e. identifying a data object) within EFMMDF.

Coding:

according to TS 31.101.

MM Size

Contents:

size of the corresponding MM stored in EFMMDF.

Coding:

according to TS 31.101.

MM Status

Contents:

The status bytes contain the status information of the stored Multimedia Message.

Coding:

First byte:

bit b1 indicates whether the MM has been read or not. Bit b2 indicates the MM forwarding status. Bit b3 indicates whether it is a received MM or an originated MM. Bits b4 to b8 are reserved for future use.

Second byte:

Coding of the second byte depends on whether the MM has been identified as a received MM or originated MM in the first byte:

Received MM coding:
bits b1 and b2 are used to provide information on Read-reply reports. Bits b3 to b8 are reserved for future use.
Originated MM coding:
bit b1 is used to provide information on Delivery-report. Bits b2 to b8 are reserved for future use.

First byte:

b8	b7	b6	b5	b4	b3	b2	b1
RFU, bit = 0					Received MM, bit = 1 / Originated MM, bit = 0	MM forwarded, bit = 1	MM read, bit = 1 / MM not read, bit = 0

Second byte coding for Received MM:

b8	b7	b6	b5	b4	b3	b2	b1
RFU, bit = 0			Delivery report creation allowed, bit = 1	Delivery report requested, bit = 1	Read-reply report created, bit = 1	Read-reply report sent, bit = 1	Read-reply report requested, bit = 1

Second byte coding for Originated MM:

b8	b7	b6	b5	b4	b3	b2	b1
RFU, bit = 0			MM sent, bit = 1	Read-Reply report received, bit = 1	Read-Reply report requested, bit = 1	Delivery report requested, bit = 1	Delivery report received, bit = 1

MM Alpha Identifier

Contents:

information about the MM to be displayed to the user (e.g. sender, subject, date etc).

Coding:

this alpha identifier shall use either:

either:

the SMS default 7-bit coded alphabet as defined in TS 23.038 with bit 8 set to 0. The alpha identifier shall be left justified. Unused bytes shall be set to 'FF'.

one of the UCS2 coded options as defined in Annex A of TS 31.101.

4.6.3.2 EF_MMDF (Multimedia Messages Data File) p. 264

If service No. 67 is "available", this file shall be present.

Residing under DFMULTIMEDIA, this EF contains Multimedia Messages data. The structure of this EF is BER-TLV (see TS 31.101). Each MM in this file is identified by a tag. The tag value for a particular MM in this file is stored in EFMML.

Identifier: '4F48'

Structure: BER-TLV

Optional

Update activity: low

Access Conditions:

READ	PIN
UPDATE	PIN
DEACTIVATE	ADM
ACTIVATE	ADM

Bytes	Description	M/O	Length
1 to X	MM Content Data Object(s)	M	X bytes

MM Content Data Object

The content and coding are defined below:

Coding of the MM Content Data Objects

Length	Description	Coding	Status
1 to T bytes (T ≤ 3)	MM Content Data Object tag	As defined in TS 31.101 for BER-TLV structured files	M
1 to L (L ≤ 4)	MM Content Data Object length	As defined in TS 31.101 for BER-TLV structured files	M
X-L-T bytes	MM Content	According to MMS Implementation	M

Contents:

The Multimedia Message content consists of MM headers and a message body. The content of the Multimedia Message data depends on whether the MM has been identified as a received MM or an originated MM:

For a received message, the stored Multimedia Message data consists of the information elements (i.e. relevant MM control information and MM content) of the MM1_retrieve.RES (see TS 23.140).
For an originated message, the stored Multimedia Message data consists of the information elements (i.e. relevant MM control information and MM content) of the MM1_submit.REQ (see TS 23.140).

Coding:

The MM data encapsulation scheme and encoding rules are defined by the MMS Implementation.

4.6.4 Contents of files at the DF MCS level |R13| p. 265

The EFs in the Dedicated File DFMCS contain management objects related to Mission Critical Services (including MCPTT, MCS, MCData, MCVideo), as specified in TS 24.483.

4.6.4.1 EF_MST (MCS Service Table) p. 265

If service No. 109 is "available" in the USIM Service Table or service No. 15 is "available" in the ISIM Service Table, this file shall be present. This EF indicates the coding of the MCS management objects and which MCPTT, MCS, MCData or MCVideo services are available. If a service is not indicated as available in the MCS Service Table, the ME shall not select this service.

Identifier: '4F01'

Structure: transparent

Optional

SFI: '01'

File size: X bytes, (X ≥ 2)

Update activity: low

Access Conditions:

READ	PIN
UPDATE	ADM
DEACTIVATE	ADM
ACTIVATE	ADM

Bytes	Description	M/O	Length
1	Coding of the MCS management objects	M	1 byte
2	Services No. 1 to No. 8	M	1 byte
3	Services No. 9 to No. 16	O	1 byte
etc.
X	Services No. (8X-7) to No. (8X)	O	1 byte

Coding of the MCS management objects

Contents:

Indicates the coding used for all the MCS management objects stored in the DFMCS.

Coding:

A value of '00' indicates the XML format described in TS 24.483. All other values are reserved.

The EF shall contain at least one byte for services. Further bytes may be included, but if the EF includes an optional byte, then it is mandatory for the EF to also contain all bytes before that byte. Other services are possible in the future and will be coded on further bytes in the EF.

Services

Contents:

Service No. 1

MCPTT UE configuration data

Service No. 2

MCPTT User profile data

Service No. 3

MCS Group configuration data

Service No. 4

MCPTT Service configuration data

Service No. 5

MCS UE initial configuration data

Service No. 6

MCData UE configuration data

Service No. 7

MCData user profile data

Service No. 8

MCData service configuration data

Service No. 9

MCVideo UE configuration data

Service No. 10

MCVideo user profile data

Service No. 11

MCVideo service configuration data

Coding:

Same as coding of USIM Service Table.

4.6.4.2 EF_{MCS_CONFIG} (MCS configuration data) p. 265

If at least one of the services is "available" in the MCS Service Table, this file shall be present.

This EF contains zero, one or more configuration data objects, as specified in TS 24.483.

Identifier: '4F02'

Structure: BER-TLV

Optional

SFI: '02'

File size: X bytes

Update activity: low

Access Conditions:

READ	PIN
UPDATE	ADM
DEACTIVATE	ADM
ACTIVATE	ADM

Bytes	Description	M/O	Length
1 to Y	Mission Critical Services configuration data object	O	Y bytes

The MCS configuration data is encoded as specified in the MCS Service Table.

Unused bytes shall be set to 'FF'.

Mission Critical Services configuration data object tag:

MCPTT configuration data objects	Tag Values	Condition
MCPTT UE configuration data	'80'	Shall be present if service No. 1 is "available" in the MCS service table
MCPTT user profile data	'81'	Shall be present if service No. 2 is "available" in the MCS service table
MCS Group configuration data	'82'	Shall be present if service No. 3 is "available" in the MCS service table
MCPTT Service configuration data	'83'	Shall be present if service No. 4 is "available" in the MCS service table
MCS UE initial configuration data	'84'	Shall be present if service No. 5 is "available" in the MCS service table
MCData UE configuration data	'85'	Shall be present if service No. 6 is "available" in the MCS service table
MCData user profile data	'86'	Shall be present if service No. 7 is "available" in the MCS service table
MCData service configuration data	'87'	Shall be present if service No. 8 is "available" in the MCS service table
MCVideo UE configuration data	'88'	Shall be present if service No. 9 is "available" in the MCS service table
MCVideo user profile data	'89'	Shall be present if service No. 10 is "available" in the MCS service table
MCVideo service configuration data	'8A'	Shall be present if service No. 11 is "available" in the MCS service table

Content for TS 31.102 Word version: 19.1.0

4.6 Contents of DFs at the TELECOM level p. 258

4.6.0 List of DFs at the TELECOM level |R14| p. 258

4.6.1 Contents of files at the DF GRAPHICS level p. 258

4.6.1.1 EF_IMG (Image) p. 259

4.6.1.2 EF_IIDF (Image Instance Data Files) p. 260

4.6.1.3 EF_{ICE_graphics} (In Case of Emergency - Graphics) |R9| p. 261

4.6.1.4 Void

4.6.1.5 Void

4.6.2 Contents of files at the DF PHONEBOOK under the DF TELECOM p. 261

4.6.3 Contents of files at the DF MULTIMEDIA level |R6| p. 261

4.6.3.1 EF_MML (Multimedia Messages List) p. 261

4.6.3.2 EF_MMDF (Multimedia Messages Data File) p. 264

4.6.4 Contents of files at the DF MCS level |R13| p. 265

4.6.4.1 EF_MST (MCS Service Table) p. 265

4.6.4.2 EF_{MCS_CONFIG} (MCS configuration data) p. 265

4.6.4.3 Void

4.6.4.4 Void

4.6.4.5 Void

Content for TS 31.102 Word version: 19.1.0

4.6 Contents of DFs at the TELECOM level p. 258

4.6.0 List of DFs at the TELECOM level |R14| p. 258

4.6.1 Contents of files at the DF GRAPHICS level p. 258

4.6.1.1 EFIMG (Image) p. 259

4.6.1.2 EFIIDF (Image Instance Data Files) p. 260

4.6.1.3 EFICE_graphics (In Case of Emergency - Graphics) |R9| p. 261

4.6.1.4 Void

4.6.1.5 Void

4.6.2 Contents of files at the DF PHONEBOOK under the DF TELECOM p. 261

4.6.3 Contents of files at the DF MULTIMEDIA level |R6| p. 261

4.6.3.1 EFMML (Multimedia Messages List) p. 261

4.6.3.2 EFMMDF (Multimedia Messages Data File) p. 264

4.6.4 Contents of files at the DF MCS level |R13| p. 265

4.6.4.1 EFMST (MCS Service Table) p. 265

4.6.4.2 EFMCS_CONFIG (MCS configuration data) p. 265

4.6.4.3 Void

4.6.4.4 Void

4.6.4.5 Void

4.6.1.1 EF_IMG (Image) p. 259

4.6.1.2 EF_IIDF (Image Instance Data Files) p. 260

4.6.1.3 EF_{ICE_graphics} (In Case of Emergency - Graphics) |R9| p. 261

4.6.3.1 EF_MML (Multimedia Messages List) p. 261

4.6.3.2 EF_MMDF (Multimedia Messages Data File) p. 264

4.6.4.1 EF_MST (MCS Service Table) p. 265

4.6.4.2 EF_{MCS_CONFIG} (MCS configuration data) p. 265