5.5.10 Common MCS test USIM parameters

36.579-13GPPMission Critical (MC) services over LTEPart 1: Common test environmentRelease 15TS

5.5.10.1 General

The format and coding of elementary files of the USIM are defined in 3GPP TS 31.102 [73]. Those of the ISIM are defined in 3GPP TS 31.101 [79] and 3GPP TS 31.103 [80].

The present clause defines default MCS relevant parameters for programming the elementary files of the test USIM when running conformance test cases defined in TS 36.579-2 [2], TS 36.579-6 [84], or TS 36.579-7 [85].

For requirements to the test USIM/ISIM needed for the E-UTRA/EPC and MCS off-network ProSe operation see 3GPP TS 36.508 [6], clause 4.9.

5.5.10.2 Default settings for the Elementary Files (EFs)

EFUST (USIM Service Table)

Services

Discription

Activated

Version

Service n°109

Mission Critical Services

Yes

NOTE: Only the relevant MCS related services indicated.

EFMST (MCS Service Table)

This file shall be present. This EF indicates the coding of the MCS management objects and which MCS services are available.

Coding of the MCPTT management objects = ’00’ (XML format).

Services

Discription

Activated

Version

Service n°1:

MCPTT UE configuration data

Yes

Service n°2:

MCPTT User profile data

Yes

Service n°3:

MCS Group configuration data

Yes

Service n°4:

MCPTT Service configuration data

Yes

Service n°5:

MCS UE initial configuration data

Yes

Service n°6:

MCData UE configuration data

Yes

Service n°7:

MCData user profile data

Yes

Service n°8:

MCData service configuration data

Yes

Service n°9:

MCVideo UE configuration data

Yes

Service n°10:

MCVideo user profile data

Yes

Service n°11:

MCVideo service configuration data

Yes

EFMCS_CONFIG (MCS configuration data)

This file shall be present.

Encoded in XML format (as specified in the MCS Service Table).

MCPTT configuration data objects

Tag Values

Condition

MCPTT UE configuration data

’80’

Shall be present.

The content of the MCPTT UE configuration data object shall be as specified in Table 5.5.8.2-1.

MCPTT user profile data

’81’

Shall be present.

The content of the MCPTT User configuration data object shall be as specified in Table 5.5.8.3-1.

MCS Group configuration data

’82’

Shall be present.

The content of the MCS Group configuration data object shall be as specified in Table 5.5.7.1 for MCPTT, Table 5.5.7.2-1 for MCVideo, and Table 5.5.7.3-1 for MCData.

MCPTT Service configuration data

’83’

Shall be present.

The content of the MCPTT Server configuration data object shall be as specified in Table 5.5.8.4-1.

MCS UE initial configuration data

’84’

Shall be present.

The content of the MCS UE initial configuration data object shall be as specified in Table 5.5.8.1-1 for MCPTT, Table 5.5.8.5-1 for MCVideo, and Table 5.5.8.9-1 for MCData,

MCData UE configuration data

’85’

Shall be present.

The content of the MCData UE configuration data object shall be as specified in Table 5.5.8.10-1.

MCData user profile data

’86’

Shall be present.

The content of the MCData user profile data object shall be as specified in Table 5.5.8.11-1.

MCData service configuration data

’87’

Shall be present.

The content of the MCData service configuration data object shall be as specified in Table 5.5.8.12-1.

MCVideo UE configuration data

’88’

Shall be present.

The content of the MCVideo UE configuration data object shall be as specified in Table 5.5.8.6-1.

MCVideo user profile data

’89’

Shall be present.

The content of the MCVideo user profile data object shall be as specified in Table 5.5.8.7-1.

MCVideo service configuration data

‘8A’

Shall be present.

The content of the MCVideo service configuration data object shall be as specified in Table 5.5.8.8-1.