27.22.4 Proactive UICC commands

31.1243GPPMobile Equipment (ME) conformance test specificationRelease 16TSUniversal Subscriber Identity Module Application Toolkit (USAT) conformance test specification

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

27.22.4.1 DISPLAY TEXT

27.22.4.1.1 DISPLAY TEXT (Normal)

27.22.4.1.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.1.1.2 Conformance requirements

The ME shall support the DISPLAY TEXT command as defined in the following technical specifications:

TS 31.111 [15], clause 5.2, clause 6.4.1, clause 6.5.4, clause 6.6.1, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 8.31.

27.22.4.1.1.3 Test purpose

To verify that the ME displays the text contained in the DISPLAY TEXT proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.1.1.4 Method of test

27.22.4.1.1.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.1.1.4.2 Procedure

Expected Sequence 1.1 (DISPLAY TEXT normal priority, Unpacked 8 bit data for Text String, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.1.1.4.2, Expected Sequence 1.1.

Expected Sequence 1.2 (DISPLAY TEXT normal priority, Unpacked 8 bit data for Text String, screen busy)

See ETSI TS 102 384 [26] in clause 27.22.4.1.1.4.2, Expected Sequence 1.2.

Expected Sequence 1.3 (DISPLAY TEXT, high priority, Unpacked 8 bit data for Text String, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.1.1.4.2, Expected Sequence 1.3.

Expected Sequence 1.4 (DISPLAY TEXT, Packed, SMS default alphabet, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.1.1.4.2, Expected Sequence 1.4.

Expected Sequence 1.5 (DISPLAY TEXT, Clear message after delay, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.1.1.4.2, Expected Sequence 1.5.

Expected Sequence 1.6 (DISPLAY TEXT, Text string with 160 bytes, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.1.1.4.2, Expected Sequence 1.6.

Expected Sequence 1.7 (DISPLAY TEXT, Backward move in UICC session, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.1.1.4.2, Expected Sequence 1.7.

Expected Sequence 1.8 (DISPLAY TEXT, session terminated by user)

See ETSI TS 102 384 [26] in clause 27.22.4.1.1.4.2, Expected Sequence 1.8.

Expected Sequence 1.9 (DISPLAY TEXT, icon and text to be displayed, no text string given, not understood by ME)

See ETSI TS 102 384 [26] in clause 27.22.4.1.1.4.2, Expected Sequence 1.9.

27.22.4.1.1.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1 to 1.9.

27.22.4.1.2 DISPLAY TEXT (Support of "No response from user")

27.22.4.1.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.1.2.2 Conformance requirement

The ME shall support the DISPLAY TEXT command as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.1, clause 6.6.1, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.15, clause 8.15.1, clause 8.15.2 and clause 8.15.3.

27.22.4.1.2.3 Test purpose

To verify that the ME displays the text contained in the DISPLAY TEXT proactive UICC command, and returns a "No response from user" result value in the TERMINAL RESPONSE command send to the UICC.

27.22.4.1.2.4 Method of test

27.22.4.1.2.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

ME Manufacturers shall set the "no response from user" period of time as declared in table A.2/1..

The USIM simulator shall be set to that period of time.

27.22.4.1.2.4.2 Procedure

Expected Sequence 2.1 (DISPLAY TEXT, no response from user)

See ETSI TS 102 384 [26] in clause 27.22.4.1.2.4.2, Expected Sequence.

2.1.27.22.4.1.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 2.1.

27.22.4.1.3 DISPLAY TEXT (Display of extension text)

27.22.4.1.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.1.3.2 Conformance requirement

The ME shall support the DISPLAY TEXT command as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.1, clause 6.6.1, clause 6.8, clause 6.11, clause 8.6, clause 8.15.

27.22.4.1.3.3 Test purpose

To verify that the ME displays the extension text contained in the DISPLAY TEXT proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.1.3.4 Method of test

27.22.4.1.3.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.1.3.4.2 Procedure

Expected Sequence 3.1 (DISPLAY TEXT, display of the extension text)

See ETSI TS 102 384 [26] in clause 27.22.4.1.3.4.2, Expected Sequence 3.1.

27.22.4.1.3.5 Test requirement

The ME shall operate in the manner defined in expected sequence 3.1.

27.22.4.1.4 DISPLAY TEXT (Sustained text)

27.22.4.1.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.1.4.2 Conformance requirement

The ME shall support the DISPLAY TEXT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.1, clause 6.6.1, clause 6.8, clause 6.11, clause 8.6, clause 8.15, clause 8.15.

27.22.4.1.4.3 Test purpose

To verify that the ME displays the text contained in the DISPLAY TEXT proactive UICC command, returns a successful result in the TERMINAL RESPONSE command send to the UICC and sustain the display beyond sending the TERMINAL response.

27.22.4.1.4.4 Method of test

27.22.4.1.4.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.1.4.4.2 Procedure

Expected Sequence 4.1 (DISPLAY TEXT, sustained text, unpacked data 8 bits, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.1.4.4.2, Expected Sequence 4.1.

Expected Sequence 4.2 (DISPLAY TEXT, sustained text, clear message after delay, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.1.4.4.2, Expected Sequence 4.2.

Expected Sequence 4.3 (DISPLAY TEXT, sustained text, wait for user MMI to clear, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.1.4.4.2, Expected Sequence 4.3.

Expected Sequence 4.4 (DISPLAY TEXT, sustained text, wait for high priority event to clear, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: DISPLAY TEXT 4.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: DISPLAY TEXT 4.4.1	[wait for user to clear message]
4	ME → USER	Display "Toolkit Test 4"
5	ME → UICC	TERMINAL RESPONSE: DISPLAY TEXT 4.4.1	[Command performed successfully]
6	UICC → ME	PROACTIVE UICC SESSION ENDED
7	ME → USER	Display of "Toolkit Test 4"	Text shall sustain until – a higher priority event occurs.
8	USS → ME	INCOMING MOBILE TERMINATED CALL

PROACTIVE COMMAND: DISPLAY TEXT 4.4.1

Logically:

Command details

Command number: 1

Command type: DISPLAY TEXT

Command qualifier: normal priority, wait for user to clear message

Device identities

Source device: UICC

Destination device: Display

Text String

Data coding scheme: unpacked, 8 bit data

Text: "Toolkit Test 4"

Immediate Response

Coding:

BER-TLV:	D0	1C	81	03	01	21	80	82	02	81	02	8D
	0F	04	54	6F	6F	6C	6B	69	74	20	54	65
	73	74	20	34	AB	00

TERMINAL RESPONSE: DISPLAY TEXT 4.4.1

Logically:

Command details

Command number: 1

Command type: DISPLAY TEXT

Command qualifier: normal priority, wait for user to clear message

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.1.4.5 Test requirement

The ME shall operate in the manner defined in expected sequences 4.1 to 4.4.

27.22.4.1.5 DISPLAY TEXT (Display of icons)

27.22.4.1.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.1.5.2 Conformance requirement

The ME shall support the DISPLAY TEXT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.1, clause 6.5.4, clause 6.6.1, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 8.31.

27.22.4.1.5.3 Test purpose

To verify that the ME displays the icons which are referred to in the contents of the DISPLAY TEXT proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.1.5.4 Method of test

27.22.4.1.5.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME screen shall be in its normal stand-by display.

27.22.4.1.5.4.2 Procedure

Expected Sequence 5.1A (DISPLAY TEXT, display of basic icon, self-explanatory, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.1.5.4.2, Expected Sequence 5.1A.

Expected Sequence 5.1B (DISPLAY TEXT, display of basic icon, self-explanatory, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.1.5.4.2, Expected Sequence 5.1B.

Expected Sequence 5.2A (DISPLAY TEXT, display of colour icon, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.1.5.4.2, Expected Sequence 5.2A.

Expected Sequence 5.2B (DISPLAY TEXT, display of colour icon, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.1.5.4.2, Expected Sequence 5.2B.

Expected Sequence 5.3A (DISPLAY TEXT, display of basic icon, not self explanatory, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.1.5.4.2, Expected Sequence 5.3A.

Expected Sequence 5.3B (DISPLAY TEXT, display of basic icon, not self explanatory, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.1.5.4.2, Expected Sequence 5.3B.27.22.4.1.5.5 Test requirement

The ME shall operate in the manner defined in expected sequences 5.1A to 5.3B.

27.22.4.1.6 DISPLAY TEXT (UCS2 display in Cyrillic)

27.22.4.1.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.1.6.2 Conformance requirement

The ME shall support the DISPLAY TEXT command as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.1, clause 6.5.4, clause 6.6.1, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 8.31.

The ME shall support the UCS2 alphabet for the coding of the Cyrillic alphabet, as defined in the following technical specification: ISO/IEC 10646 [17].

27.22.4.1.6.3 Test purpose

To verify that the ME displays the text contained in the DISPLAY TEXT proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.1.6.4 Method of test

27.22.4.1.6.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.1.6.4.2 Procedure

Expected Sequence 6.1 (DISPLAY TEXT, UCS2 coded in Cyrillic)

See ETSI TS 102 384 [26] in clause 27.22.4.1.6.4.2, Expected Sequence 6.1.

27.22.4.1.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.1.

27.22.4.1.7 DISPLAY TEXT (Variable Time out)

27.22.4.1.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.1.7.2 Conformance requirement

The ME shall support the DISPLAY TEXT command as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.1, clause 6.5.4, clause 6.6.1, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.8, clause 8.15, clause 8.31 and clause 8.43.

The ME shall support the variable time out for the display text.

27.22.4.1.7.3 Test purpose

To verify that the ME displays the text contained in the DISPLAY TEXT proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.1.7.4 Method of test

27.22.4.1.7.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.1.7.4.2 Procedure

Expected Sequence 7.1 (DISPLAY TEXT, variable timeout of 10 seconds)

See ETSI TS 102 384 [26] in clause 27.22.4.1.7.4.2, Expected Sequence 7.1.

27.22.4.1.7.5 Test requirement

The ME shall operate in the manner defined in expected sequence 7.1.

27.22.4.1.8 DISPLAY TEXT (Support of Text Attribute)

27.22.4.1.8.1 DISPLAY TEXT (Support of Text Attribute – Left Alignment)

27.22.4.1.8.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.1.8.1.2 Conformance requirement

The ME shall support the DISPLAY TEXT command as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.1, clause 6.5.4, clause 6.6.1, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.8, clause 8.15, clause 8.31, clause 8.43 and clause 8.70.

The ME shall support the text attribute with Left Alignment for the display text.

27.22.4.1.8.1.3 Test purpose

To verify that the ME displays the text formatted according to the left alignment text attribute configuration contained in the DISPLAY TEXT proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.1.8.1.4 Method of test

27.22.4.1.8.1.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.1.8.1.4.2 Procedure

Expected Sequence 8.1 (DISPLAY TEXT, Text Attribute with Left Alignment)

See ETSI TS 102 384 [26] in clause 27.22.4.1.8.1.4.2, Expected Sequence 8.1.

27.22.4.1.8.1.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.1.

27.22.4.1.8.2 DISPLAY TEXT (Support of Text Attribute – Center Alignment)

27.22.4.1.8.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.1.8.2.2 Conformance requirement

The ME shall support the DISPLAY TEXT command as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.1, clause 6.5.4, clause 6.6.1, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.8, clause 8.15, clause 8.31, clause 8.43 and clause 8.70.

The ME shall support the text attribute with Centre Alignment for the display text.

27.22.4.1.8.2.3 Test purpose

To verify that the ME displays the text formatted according to the center alignment text attribute configuration contained in the DISPLAY TEXT proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.1.8.2.4 Method of test

27.22.4.1.8.2.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.1.8.2.4.2 Procedure

Expected Sequence 8.2 (DISPLAY TEXT, Text Attribute with Center Alignment)

See ETSI TS 102 384 [26] in clause 27.22.4.1.8.2.4.2, Expected Sequence 8.2.

27.22.4.1.8.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.2.

27.22.4.1.8.3 DISPLAY TEXT (Support of Text Attribute – Right Alignment)

27.22.4.1.8.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.1.8.3.2 Conformance requirement

The ME shall support the DISPLAY TEXT command as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.1, clause 6.5.4, clause 6.6.1, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.8, clause 8.15, clause 8.31, clause 8.43 and clause 8.70.

The ME shall support the text attribute with Right Alignment for the display text.

27.22.4.1.8.3.3 Test purpose

To verify that the ME displays the text formatted according to the right alignment text attribute configuration contained in the DISPLAY TEXT proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.1.8.3.4 Method of test

27.22.4.1.8.3.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.1.8.3.4.2 Procedure

Expected Sequence 8.3 (DISPLAY TEXT, Text Attribute with Right Alignment)

See ETSI TS 102 384 [26] in clause 27.22.4.1.8.3.4.2, Expected Sequence 8.3.

27.22.4.1.8.3.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.3.

27.22.4.1.8.4 DISPLAY TEXT (Support of Text Attribute – Large Font Size)

27.22.4.1.8.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.1.8.4.2 Conformance requirement

The ME shall support the DISPLAY TEXT command as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.1, clause 6.5.4, clause 6.6.1, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.8, clause 8.15, clause 8.31, clause 8.43 and clause 8.70.

The ME shall support the text attribute with large font size for the display text.

27.22.4.1.8.4.3 Test purpose

To verify that the ME displays the text formatted according to the large size font text attribute configuration contained in the DISPLAY TEXT proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.1.8.4.4 Method of test

27.22.4.1.8.4.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.1.8.4.4.2 Procedure

Expected Sequence 8.4 (DISPLAY TEXT, Text Attribute with Large Font Size)

See ETSI TS 102 384 [26] in clause 27.22.4.1.8.4.4.2, Expected Sequence 8.4.

27.22.4.1.8.4.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.4.

27.22.4.1.8.5 DISPLAY TEXT (Support of Text Attribute – Small Font Size)

27.22.4.1.8.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.1.8.5.2 Conformance requirement

The ME shall support the DISPLAY TEXT command as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.1, clause 6.5.4, clause 6.6.1, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.8, clause 8.15, clause 8.31, clause 8.43 and clause 8.70.

The ME shall support the text attribute with small font size for the display text.

27.22.4.1.8.5.3 Test purpose

To verify that the ME displays the text formatted according to the small size font text attribute configuration contained in the DISPLAY TEXT proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.1.8.5.4 Method of test

27.22.4.1.8.5.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.1.8.5.4.2 Procedure

Expected Sequence 8.5 (DISPLAY TEXT, Text Attribute with Small Font Size)

See ETSI TS 102 384 [26] in clause 27.22.4.1.8.5.4.2, Expected Sequence 8.5.

27.22.4.1.8.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.5.

27.22.4.1.8.6 DISPLAY TEXT (Support of Text Attribute – Bold On)

27.22.4.1.8.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.1.8.6.2 Conformance requirement

The ME shall support the DISPLAY TEXT command as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.1, clause 6.5.4, clause 6.6.1, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.8, clause 8.15, clause 8.31, clause 8.43 and clause 8.70.

The ME shall support the text attribute with bold on for the display text.

27.22.4.1.8.6.3 Test purpose

To verify that the ME displays the text formatted according to the bold text attribute configuration contained in the DISPLAY TEXT proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.1.8.6.4 Method of test

27.22.4.1.8.6.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.1.8.6.4.2 Procedure

Expected Sequence 8.6 (DISPLAY TEXT, Text Attribute with Bold On)

See ETSI TS 102 384 [26] in clause 27.22.4.1.8.6.4.2, Expected Sequence 8.6.

27.22.4.1.8.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.6.

27.22.4.1.8.7 DISPLAY TEXT (Support of Text Attribute – Italic On)

27.22.4.1.8.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.1.8.7.2 Conformance requirement

The ME shall support the DISPLAY TEXT command as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.1, clause 6.5.4, clause 6.6.1, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.8, clause 8.15, clause 8.31, clause 8.43 and clause 8.70.

The ME shall support the text attribute with italic on for the display text.

27.22.4.1.8.7.3 Test purpose

To verify that the ME displays the text formatted according to the italic text attribute configuration contained in the DISPLAY TEXT proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.1.8.7.4 Method of test

27.22.4.1.8.7.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.1.8.7.4.2 Procedure

Expected Sequence 8.7 (DISPLAY TEXT, Text Attribute with Italic On)

See ETSI TS 102 384 [26] in clause 27.22.4.1.8.7.4.2, Expected Sequence 8.7.

27.22.4.1.8.7.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.7.

27.22.4.1.8.8 DISPLAY TEXT (Support of Text Attribute – Underline On)

27.22.4.1.8.8.1 Definition and applicability

See clause 3.2.2.

27.22.4.1.8.8.2 Conformance requirement

The ME shall support the DISPLAY TEXT command as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.1, clause 6.5.4, clause 6.6.1, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.8, clause 8.15, clause 8.31, clause 8.43 and clause 8.70.

The ME shall support the text attribute with underline on for the display text.

27.22.4.1.8.8.3 Test purpose

To verify that the ME displays the text formatted according to the underline text attribute configuration contained in the DISPLAY TEXT proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.1.8.8.4 Method of test

27.22.4.1.8.8.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.1.8.8.4.2 Procedure

Expected Sequence 8.8 (DISPLAY TEXT, Text Attribute with Underline On)

See ETSI TS 102 384 [26] in clause 27.22.4.1.8.8.4.2, Expected Sequence 8.8.

27.22.4.1.8.8.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.8.

27.22.4.1.8.9 DISPLAY TEXT (Support of Text Attribute – Strikethrough On)

27.22.4.1.8.9.1 Definition and applicability

See clause 3.2.2.

27.22.4.1.8.9.2 Conformance requirement

The ME shall support the DISPLAY TEXT command as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.1, clause 6.5.4, clause 6.6.1, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.8, clause 8.15, clause 8.31, clause 8.43 and clause 8.70.

The ME shall support the text attribute with underline on for the display text.

27.22.4.1.8.9.3 Test purpose

To verify that the ME displays the text formatted according to the strikethrough text attribute configuration contained in the DISPLAY TEXT proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.1.8.9.4 Method of test

27.22.4.1.8.9.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.1.8.9.4.2 Procedure

Expected Sequence 8.9 (DISPLAY TEXT, Text Attribute with Strikethrough On)

See ETSI TS 102 384 [26] in clause 27.22.4.1.8.9.4.2, Expected Sequence 8.9.

27.22.4.1.8.9.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.9.

27.22.4.1.8.10 DISPLAY TEXT (Support of Text Attribute – Foreground and Background Colours)

27.22.4.1.8.10.1 Definition and applicability

See clause 3.2.2.

27.22.4.1.8.10.2 Conformance requirement

The ME shall support the DISPLAY TEXT command as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.1, clause 6.5.4, clause 6.6.1, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.8, clause 8.15, clause 8.31, clause 8.43 and clause 8.70.

The ME shall support the text attribute with different foreground and background colours for the display text.

27.22.4.1.8.10.3 Test purpose

To verify that the ME displays the text formatted according to the foreground and background colour text attribute configuration contained in the DISPLAY TEXT proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.1.8.10.4 Method of test

27.22.4.1.8.10.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.1.8.10.4.2 Procedure

Expected Sequence 8.10 (DISPLAY TEXT, Text Attribute with Foreground and Background Colours)

See ETSI TS 102 384 [26] in clause 27.22.4.1.8.10.4.2, Expected Sequence 8.10.

27.22.4.1.8.10.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.10.

27.22.4.1.9 DISPLAY TEXT (UCS2 display in Chinese)

27.22.4.1.9.1 Definition and applicability

See clause 3.2.2.

27.22.4.1.9.2 Conformance requirement

The ME shall support the DISPLAY TEXT command as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.1, clause 6.5.4, clause 6.6.1, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 8.31.

The ME shall support the UCS2 alphabet for the coding of the Chinese characters, as defined in the following technical specification: ISO/IEC 10646 [17].

27.22.4.1.9.3 Test purpose

To verify that the ME displays the text contained in the DISPLAY TEXT proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.1.9.4 Method of test

27.22.4.1.9.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.1.9.4.2 Procedure

Expected Sequence 9.1 (DISPLAY TEXT, UCS2 coded – Chinese characters)

See ETSI TS 102 384 [26] in clause 27.22.4.1.9.4.2, Expected Sequence 9.1.

27.22.4.1.9.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.1.

27.22.4.1.10 DISPLAY TEXT (UCS2 display in Katakana)

27.22.4.1.10.1 Definition and applicability

See clause 3.2.2.

27.22.4.1.10.2 Conformance requirement

The ME shall support the DISPLAY TEXT command as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.1, clause 6.5.4, clause 6.6.1, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 8.31.

The ME shall support the UCS2 alphabet for the coding of the Katakana characters, as defined in the following technical specification: ISO/IEC 10646 [17].

27.22.4.1.10.3 Test purpose

To verify that the ME displays the text contained in the DISPLAY TEXT proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.1.10.4 Method of test

27.22.4.1.10.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.1.10.4.2 Procedure

Expected Sequence 10.1 (DISPLAY TEXT, UCS2 coded – Katakana characters)

See ETSI TS 102 384 [26] in clause 27.22.4.1.10.4.2, Expected Sequence 10.1.

27.22.4.1.10.5 Test requirement

The ME shall operate in the manner defined in expected sequence 10.1.

27.22.4.2 GET INKEY

27.22.4.2.1 GET INKEY(normal)

27.22.4.2.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.1.2 Conformance Requirement

The ME shall support the GET INKEY command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.2, clause 6.6.2, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.15, clause 8.15.1, clause 8.15.2 and clause 8.15.3.

27.22.4.2.1.3 Test purpose

To verify that the ME displays the text contained in the GET INKEY proactive UICC command, and returns the single character entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.1.4 Method of test

27.22.4.2.1.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be set to a display other than the idle display.

27.22.4.2.1.4.2 Procedure

Expected Sequence 1.1 (GET INKEY, digits only for character, Unpacked 8 bit data for Text String, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.2.1.4.2, Expected Sequence 1.1.

Expected Sequence 1.2 (GET INKEY, digits only for character set, SMS default Alphabet for Text String, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.2.1.4.2, Expected Sequence 1.2.

Expected Sequence 1.3 (GET INKEY, backward move)

See ETSI TS 102 384 [26] in clause 27.22.4.2.1.4.2, Expected Sequence 1.3.

Expected Sequence 1.4 (GET INKEY, abort)

See ETSI TS 102 384 [26] in clause 27.22.4.2.1.4.2, Expected Sequence 1.4.

Expected Sequence 1.5 (GET INKEY, SMS default alphabet for character set, Unpacked 8 bit data for Text String, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.2.1.4.2, Expected Sequence 1.5.

Expected Sequence 1.6 (GET INKEY, Max length for the Text String, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.2.1.4.2, Expected Sequence 1.6.

27.22.4.2.1.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1 to 1.6.

27.22.4.2.2 GET INKEY (No response from User)

27.22.4.2.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.2.2 Conformance requirement

The ME shall support the GET INKEY command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.2, clause 6.6.2, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.15, clause 8.15.1, clause 8.15.2 and clause 8.15.3.

27.22.4.2.2.3 Test purpose

To verify that the ME displays the text contained in the GET INKEY proactive UICC command, and returns a "No response from user" result value in the TERMINAL RESPONSE command send to the UICC.

27.22.4.2.2.4 Method of test

27.22.4.2.2.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

ME Manufacturers shall set the "no response from user" period of time as declared in table A.2/2.

The USIM Simulator shall be set to that period of time.

27.22.4.2.2.4.2 Procedure

Expected Sequence 2.1 (GET INKEY, no response from the user)

See ETSI TS 102 384 [26] in clause 27.22.4.2.2.4.2, Expected Sequence 2.1.

27.22.4.2.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 2.1.

27.22.4.2.3 GET INKEY (UCS2 display in Cyrillic)

27.22.4.2.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.3.2 Conformance requirement

The ME shall support the GET INKEY command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.2, clause 6.6.2, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.15, clause 8.15.1, clause 8.15.2 and clause 8.15.3.

Additionally, the ME shall support the UCS2 facility for the coding of the Cyrillic alphabet, as defined in the following technical specifications: ISO/IEC 10646 [17].

27.22.4.2.3.3 Test purpose

To verify that the ME displays the text contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.3.4 Method of test

27.22.4.2.3.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.2.3.4.2 Procedure

Expected Sequence 3.1 (GET INKEY, Text String coding in UCS2 Alphabet in Cyrillic, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.2.3.4.2, Expected Sequence 3.1.

Expected Sequence 3.2 (GET INKEY, max length for the Text String coding in UCS2 Alphabet in Cyrillic, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.2.3.4.2, Expected Sequence 3.2.

27.22.4.2.3.5 Test requirement

The ME shall operate in the manner defined in expected sequence 3.1 to 3.2.

27.22.4.2.4 GET INKEY (UCS2 entry in Cyrillic)

27.22.4.2.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.4.2 Conformance requirement

The ME shall support the GET INKEY command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.2, clause 6.6.2, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.15, clause 8.15.1, clause 8.15.2 and clause 8.15.3.

Additionally, the ME shall support the UCS2 facility for the coding of the Cyrillic alphabet, as defined in the following technical specifications: ISO/IEC 10646 [17].

27.22.4.2.4.3 Test purpose

To verify that the ME displays the text contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.4.4 Method of test

27.22.4.2.4.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.2.4.4.2 Procedure

Expected Sequence 4.1 (GET INKEY, characters from UCS2 alphabet in Cyrillic, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.2.4.4.2, Expected Sequence 4.1.

27.22.4.2.4.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.1.

27.22.4.2.5 GET INKEY ("Yes/No" Response)

27.22.4.2.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.5.2 Conformance requirement

The ME shall support the GET INKEY command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.2, clause 6.6.2, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.15, clause 8.15.1, clause 8.15.2 and clause 8.15.3.

27.22.4.2.5.3 Test purpose

To verify that the ME displays the text contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.5.4 Method of test

27.22.4.2.5.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.2.5.4.2 Procedure

Expected Sequence 5.1(GET INKEY, "Yes/No" Response for the input, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.2.5.4.2, Expected Sequence 5.1.

27.22.4.2.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 5.1.

27.22.4.2.6 GET INKEY (display of Icon)

27.22.4.2.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.6.2 Conformance requirement

The ME shall support the GET INKEY command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.2, clause 6.5.4, clause 6.6.2, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 8.31.

27.22.4.2.6.3 Test purpose

To verify that the ME displays the Icon contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.6.4 Method of test

27.22.4.2.6.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME screen shall be in its normal stand-by display.

27.22.4.2.6.4.2 Procedure

Expected Sequence 6.1A (GET INKEY, Basic icon, self-explanatory, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.2.6.4.2, Expected Sequence 6.1A.

Expected Sequence 6.1B (GET INKEY, Basic icon, self-explanatory, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.2.6.4.2, Expected Sequence 6.1B.

Expected Sequence 6.2A (GET INKEY, Basic icon, non self-explanatory, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.2.6.4.2, Expected Sequence 6.2A.

Expected Sequence 6.2B (GET INKEY, Basic icon, non self-explanatory, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.2.6.4.2, Expected Sequence 6.2B.

Expected Sequence 6.3A (GET INKEY, Colour icon, self-explanatory, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.2.6.4.2, Expected Sequence 6.3A.

Expected Sequence 6.3B (GET INKEY, Colour icon, self-explanatory, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.2.6.4.2, Expected Sequence 6.3B.

Expected Sequence 6.4A (GET INKEY, Colour icon, non self-explanatory, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.2.6.4.2, Expected Sequence 6.4A.

Expected Sequence 6.4B (GET INKEY, Colour icon, non self-explanatory, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.2.6.4.2, Expected Sequence 6.4B.

27.22.4.2.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.1A to 6.4B.

27.22.4.2.7 GET INKEY (Help Information)

27.22.4.2.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.7.2 Conformance requirement

The ME shall support the GET INKEY command as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.2, clause 6.5.4, clause 6.6.2, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 8.31.

27.22.4.2.7.3 Test purpose

To verify that the ME displays the text contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.7.4 Method of test

27.22.4.2.7.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.2.7.4.2 Procedure

Expected Sequence 7.1 (GET INKEY, help information available)

See ETSI TS 102 384 [26] in clause 27.22.4.2.7.4.2, Expected Sequence 7.1.

27.22.4.2.7.5 Test requirement

The ME shall operate in the manner defined in expected sequence 7.1.

27.22.4.2.8 GET INKEY (Variable Time out)

27.22.4.2.8.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.8.2 Conformance requirement

The ME shall support the GET INKEY command as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.2, clause 6.5.4, clause 6.6.2, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.8, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 8.31.

27.22.4.2.8.3 Test purpose

To verify that the ME displays the text contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.8.4 Method of test

27.22.4.2.8.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.2.8.4.2 Procedure

Expected Sequence 8.1 (GET INKEY, variable time out of 10 seconds)

See ETSI TS 102 384 [26] in clause 27.22.4.2.8.4.2, Expected Sequence 8.1.

27.22.4.2.8.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.1.

27.22.4.2.9 GET INKEY (Support of Text Attribute)

27.22.4.2.9.1 GET INKEY (Support of Text Attribute – Left Alignment)

27.22.4.2.9.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.9.1.2 Conformance requirement

The ME shall support the GET INKEY command as defined in the following technical specifications:

27.22.4.2.9.1.3 Test purpose

To verify that the ME displays the text formatted according to the left alignment text attribute configuration contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.9.1.4 Method of test

27.22.4.2.9.1.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.2.9.1.4.2 Procedure

Expected Sequence 9.1 (GET INKEY, Text attribute with Left Alignment )

See ETSI TS 102 384 [26] in clause 27.22.4.2.9.1.4.2, Expected Sequence 9.1.

27.22.4.2.9.1.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.1.

27.22.4.2.9.2 GET INKEY (Support of Text Attribute – Center Alignment)

27.22.4.2.9.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.9.2.2 Conformance requirement

The ME shall support the GET INKEY command as defined in the following technical specifications:

27.22.4.2.9.2.3 Test purpose

To verify that the ME displays the text formatted according to the center alignment text attribute configuration contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.9.2.4 Method of test

27.22.4.2.9.2.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.2.9.2.4.2 Procedure

Expected Sequence 9.2 (GET INKEY, Text attribute with Center Alignment)

See ETSI TS 102 384 [26] in clause 27.22.4.2.9.2.4.2, Expected Sequence 9.2.

27.22.4.2.9.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.2.

27.22.4.2.9.3 GET INKEY (Support of Text Attribute – Right Alignment)

27.22.4.2.9.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.9.3.2 Conformance requirement

The ME shall support the GET INKEY command as defined in the following technical specifications:

27.22.4.2.9.3.3 Test purpose

To verify that the ME displays the text formatted according to the right alignment text attribute configuration contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.9.3.4 Method of test

27.22.4.2.9.3.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.2.9.3.4.2 Procedure

Expected Sequence 9.3 (GET INKEY, Text attribute with Right Alignment)

See ETSI TS 102 384 [26] in clause 27.22.4.2.9.3.4.2, Expected Sequence 9.3.

27.22.4.2.9.3.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.3.

27.22.4.2.9.4 GET INKEY (Support of Text Attribute – Large Font Size)

27.22.4.2.9.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.9.4.2 Conformance requirement

The ME shall support the GET INKEY command as defined in the following technical specifications:

27.22.4.2.9.4.3 Test purpose

To verify that the ME displays the text formatted according to the large font size text attribute configuration contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.9.4.4 Method of test

27.22.4.2.9.4.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.2.9.4.4.2 Procedure

Expected Sequence 9.4 (GET INKEY, Text attribute with Large Font Size)

See ETSI TS 102 384 [26] in clause 27.22.4.2.9.4.4.2, Expected Sequence 9.4.

27.22.4.2.9.4.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.4.

27.22.4.2.9.5 GET INKEY (Support of Text Attribute – Small Font Size)

27.22.4.2.9.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.9.5.2 Conformance requirement

The ME shall support the GET INKEY command as defined in the following technical specifications:

27.22.4.2.9.5.3 Test purpose

To verify that the ME displays the text formatted according to the small font size text attribute configuration contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.9.5.4 Method of test

27.22.4.2.9.5.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.2.9.5.4.2 Procedure

Expected Sequence 9.5 (GET INKEY, Text attribute with Small Font Size)

See ETSI TS 102 384 [26] in clause 27.22.4.2.9.5.4.2, Expected Sequence 9.5.

27.22.4.2.9.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.5.

27.22.4.2.9.6 GET INKEY (Support of Text Attribute – Bold On)

27.22.4.2.9.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.9.6.2 Conformance requirement

The ME shall support the GET INKEY command as defined in the following technical specifications:

27.22.4.2.9.6.3 Test purpose

To verify that the ME displays the text formatted according to the bold text attribute configuration contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.9.6.4 Method of test

27.22.4.2.9.6.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.2.9.6.4.2 Procedure

Expected Sequence 9.6 (GET INKEY, Text attribute with Bold On)

See ETSI TS 102 384 [26] in clause 27.22.4.2.9.6.4.2, Expected Sequence 9.6.

27.22.4.2.9.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.6.

27.22.4.2.9.7 GET INKEY (Support of Text Attribute – Italic On)

27.22.4.2.9.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.9.7.2 Conformance requirement

The ME shall support the GET INKEY command as defined in the following technical specifications:

27.22.4.2.9.7.3 Test purpose

To verify that the ME displays the text formatted according to the italic text attribute configuration contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.9.7.4 Method of test

27.22.4.2.9.7.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.2.9.7.4.2 Procedure

Expected Sequence 9.7 (GET INKEY, Text attribute with Italic On)

See ETSI TS 102 384 [26] in clause 27.22.4.2.9.7.4.2, Expected Sequence 9.7.

27.22.4.2.9.7.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.7.

27.22.4.2.9.8 GET INKEY (Support of Text Attribute – Underline On)

27.22.4.2.9.8.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.9.8.2 Conformance requirement

The ME shall support the GET INKEY command as defined in the following technical specifications:

27.22.4.2.9.8.3 Test purpose

To verify that the ME displays the text formatted according to the underline text attribute configuration contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.9.8.4 Method of test

27.22.4.2.9.8.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.2.9.8.4.2 Procedure

Expected Sequence 9.8 (GET INKEY, Text attribute with Underline On)

See ETSI TS 102 384 [26] in clause 27.22.4.2.9.8.4.2, Expected Sequence 9.8.

27.22.4.2.9.8.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.8.

27.22.4.2.9.9 GET INKEY (Support of Text Attribute – Strikethrough On)

27.22.4.2.9.9.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.9.9.2 Conformance requirement

The ME shall support the GET INKEY command as defined in the following technical specifications:

27.22.4.2.9.9.3 Test purpose

To verify that the ME displays the text formatted according to the strikethrough text attribute configuration contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.9.9.4 Method of test

27.22.4.2.9.9.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.2.9.9.4.2 Procedure

Expected Sequence 9.9 (GET INKEY, Text attribute with Strikethrough On)

See ETSI TS 102 384 [26] in clause 27.22.4.2.9.9.4.2, Expected Sequence 9.9.

27.22.4.2.9.9.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.9.

27.22.4.2.9.10 GET INKEY (Support of Text Attribute – Foreground and Background Colour)

27.22.4.2.9.10.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.9.10.2 Conformance requirement

The ME shall support the GET INKEY command as defined in the following technical specifications:

27.22.4.2.9.10.3 Test purpose

To verify that the ME displays the text formatted according to the foreground and background colour text attribute configuration contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.9.10.4 Method of test

27.22.4.2.9.10.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.2.9.10.4.2 Procedure

Expected Sequence 9.10 (GET INKEY, Text attribute with Foreground and Background Colour)

See ETSI TS 102 384 [26] in clause 27.22.4.2.9.10.4.2, Expected Sequence 9.10.

27.22.4.2.9.10.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.10.

27.22.4.2.10 GET INKEY (UCS2 display in Chinese)

27.22.4.2.10.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.10.2 Conformance requirement

The ME shall support the GET INKEY command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.2, clause 6.6.2, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.15, clause 8.15.1, clause 8.15.2 and clause 8.15.3.

Additionally, the ME shall support the UCS2 facility for the coding of the Chinese characters, as defined in the following technical specifications: ISO/IEC 10646 [17].

27.22.4.2.10.3 Test purpose

To verify that the ME displays the text contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.10.4 Method of test

27.22.4.2.10.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.2.10.4.2 Procedure

Expected Sequence 10.1 (GET INKEY, Text String coding in UCS2 Alphabet – Chinese characters, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.2.10.4.2, Expected Sequence 10.1.

Expected Sequence 10.2 (GET INKEY, max length for the Text String coding in UCS2 Alphabet – Chinese characters, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.2.10.4.2, Expected Sequence 10.2.

27.22.4.2.10.5 Test requirement

The ME shall operate in the manner defined in expected sequence 10.1 to 10.2.

27.22.4.2.11 GET INKEY (UCS2 entry in Chinese)

27.22.4.2.11.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.11.2 Conformance requirement

The ME shall support the GET INKEY command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.2, clause 6.6.2, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.15, clause 8.15.1, clause 8.15.2 and clause 8.15.3.

Additionally, the ME shall support the UCS2 facility for the coding of the Chinese character, as defined in the following technical specifications: ISO/IEC 10646 [17].

27.22.4.2.11.3 Test purpose

To verify that the ME displays the text contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.11.4 Method of test

27.22.4.2.11.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.2.11.4.2 Procedure

Expected Sequence 11.1 (GET INKEY, characters from UCS2 alphabet – Chinese characters, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.2.11.4.2, Expected Sequence 11.1.

27.22.4.2.11.5 Test requirement

The ME shall operate in the manner defined in expected sequence 11.1

27.22.4.2.12 GET INKEY (UCS2 display in Katakana)

27.22.4.2.12.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.12.2 Conformance requirement

The ME shall support the GET INKEY command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.2, clause 6.6.2, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.15, clause 8.15.1, clause 8.15.2 and clause 8.15.3.

Additionally, the ME shall support the UCS2 facility for the coding of the Katakana characters, as defined in the following technical specifications: ISO/IEC 10646 [17].

27.22.4.2.12.3 Test purpose

To verify that the ME displays the text contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.12.4 Method of test

27.22.4.2.12.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.2.12.4.2 Procedure

Expected Sequence 12.1 (GET INKEY, Text String coding in UCS2 Alphabet – Katakana characters, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.2.12.4.2, Expected Sequence 12.1.

Expected Sequence 12.2 (GET INKEY, max length for the Text String coding in UCS2 Alphabet – Katakana characters, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.2.12.4.2, Expected Sequence 12.2.

27.22.4.2.12.5 Test requirement

The ME shall operate in the manner defined in expected sequence 12.1 to 12.2.

27.22.4.2.13 GET INKEY (UCS2 entry in Katakana)

27.22.4.2.13.1 Definition and applicability

See clause 3.2.2.

27.22.4.2.13.2 Conformance requirement

The ME shall support the GET INKEY command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.2, clause 6.6.2, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.15, clause 8.15.1, clause 8.15.2 and clause 8.15.3.

Additionally, the ME shall support the UCS2 facility for the coding of the Katakana characters, as defined in the following technical specifications: ISO/IEC 10646 [17].

27.22.4.2.13.3 Test purpose

To verify that the ME displays the text contained in the GET INKEY proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.2.13.4 Method of test

27.22.4.2.13.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.2.13.4.2 Procedure

Expected Sequence 13.1 (GET INKEY, characters from UCS2 alphabet – Katakana characters, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.2.13.4.2, Expected Sequence 13.1.

27.22.4.2.13.5 Test requirement

The ME shall operate in the manner defined in expected sequence 13.1

27.22.4.3 GET INPUT

27.22.4.3.1 GET INPUT (normal)

27.22.4.3.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.1.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2 and clause 8.15.3.

27.22.4.3.1.3 Test purpose

To verify that the ME displays the text contained in the GET INPUT proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.3.1.4 Method of test

27.22.4.3.1.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.3.1.4.2 Procedure

Expected Sequence 1.1 (GET INPUT, digits only, SMS default alphabet, ME to echo text, ME supporting 8 bit data Message)

See ETSI TS 102 384 [26] in clause 27.22.4.3.1.4.2, Expected Sequence 1.1.

Expected Sequence 1.2 (GET INPUT, digits only, SMS default alphabet, ME to echo text, packing SMS Point-to-point required by ME)

See ETSI TS 102 384 [26] in clause 27.22.4.3.1.4.2, Expected Sequence 1.2.

Expected Sequence 1.3 (GET INPUT, character set, SMS Default Alphabet, ME to echo text, ME supporting 8 bit data Message)

See ETSI TS 102 384 [26] in clause 27.22.4.3.1.4.2, Expected Sequence 1.3.

Expected Sequence 1.4 (GET INPUT, digits only, SMS default alphabet, ME to hide text, ME supporting 8 bit data Message)

See ETSI TS 102 384 [26] in clause 27.22.4.3.1.4.2, Expected Sequence 1.4.

Expected Sequence 1.5 (GET INPUT, digits only, SMS default alphabet, ME to echo text, ME supporting 8 bit data Message)

See ETSI TS 102 384 [26] in clause 27.22.4.3.1.4.2, Expected Sequence 1.5.

Expected Sequence 1.6 (GET INPUT, backwards move)

See ETSI TS 102 384 [26] in clause 27.22.4.3.1.4.2, Expected Sequence 1.6.

Expected Sequence 1.7 (GET INPUT, abort)

See ETSI TS 102 384 [26] in clause 27.22.4.3.1.4.2, Expected Sequence 1.7.

Expected Sequence 1.8 (GET INPUT, digits only, SMS default alphabet, ME to echo text, ME supporting 8 bit data Message)

See ETSI TS 102 384 [26] in clause 27.22.4.3.1.4.2, Expected Sequence 1.8.

Expected Sequence 1.9 (GET INPUT, digits only, SMS default alphabet, ME to echo text, ME supporting 8 bit data Message)

See ETSI TS 102 384 [26] in clause 27.22.4.3.1.4.2, Expected Sequence 1.9.

Expected Sequence 1.10 (GET INPUT, null length for the text string, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.3.1.4.2, Expected Sequence 1.10.

27.22.4.3.1.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1 to 1.10.

27.22.4.3.2 GET INPUT (No response from User)

27.22.4.3.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.2.2 Conformance requirement

The ME shall support the GET INPUT command as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2 and clause 8.15.3.

27.22.4.3.2.3 Test purpose

To verify that the ME displays the text contained in the GET INPUT proactive UICC command, and returns a "No response from user" result value in the TERMINAL RESPONSE command send to the UICC.

27.22.4.3.2.4 Method of test

27.22.4.3.2.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

ME Manufacturers shall set the "no response from user" period of time as declared in table A.2/3.

The USIM Simulator shall be set to that period of time.

27.22.4.3.2.4.2 Procedure

Expected Sequence 2.1 (GET INPUT, no response from the user)

See ETSI TS 102 384 [26] in clause 27.22.4.3.2.4.2, Expected Sequence 2.1.

27.22.4.3.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 2.1.

27.22.4.3.3 GET INPUT (UCS2 display in Cyrillic)

27.22.4.3.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.3.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2 and clause 8.15.3.

Additionally the ME shall support the UCS2 facility for the coding of the Cyrillic alphabet, as defined in the following technical specifications: ISO/IEC 10646 [17].

27.22.4.3.3.3 Test purpose

To verify that the ME displays the text contained in the GET INPUT proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.3.3.4 Method of test

27.22.4.3.3.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.3.3.4.2 Procedure

Expected Sequence 3.1 (GET INPUT, text string coding in UCS2 in Cyrillic, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.3.3.4.2, Expected Sequence 3.1.

Expected Sequence 3.2 (GET INPUT, max length for the text string coding in UCS2 in Cyrillic, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.3.3.4.2, Expected Sequence 3.2.

27.22.4.3.3.5 Test requirement

The ME shall operate in the manner defined in expected sequences 3.1 to 3.2.

27.22.4.3.4 GET INPUT (UCS2 entry in Cyrillic)

27.22.4.3.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.4.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2 and clause 8.15.3.

Additionally the ME shall support the UCS2 facility for the coding of the Cyrillic alphabet, as defined in ISO/IEC 10646 [17].

27.22.4.3.4.3 Test purpose

To verify that the ME displays the text contained in the GET INPUT proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.3.4.4 Method of test

27.22.4.3.4.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.3.4.4.2 Procedure

Expected Sequence 4.1 (GET INPUT, character set from UCS2 alphabet in Cyrillic, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.3.4.4.2, Expected Sequence 4.1.

Expected Sequence 4.2 (GET INPUT, character set from UCS2 alphabet in Cyrillic, Max length for the input, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.3.4.4.2, Expected Sequence 4.2.

27.22.4.3.4.5 Test requirement

The ME shall operate in the manner defined in expected sequences 4.1 to 4.2.

27.22.4.3.5 GET INPUT (default text)

27.22.4.3.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.5.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 8.23.

27.22.4.3.5.3 Test purpose

To verify that the ME displays the text contained in the GET INPUT proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.3.5.4 Method of test

27.22.4.3.5.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.3.5.4.2 Procedure

Expected Sequence 5.1(GET INPUT, default text for the input, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.3.5.4.2, Expected Sequence 5.1.

Expected Sequence 5.2 (GET INPUT, default text for the input with max length, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.3.5.4.2, Expected Sequence 5.2.

27.22.4.3.5.5 Test requirement

The ME shall operate in the manner defined in expected sequences 5.1 to 5.2.

27.22.4.3.6 GET INPUT (display of Icon)

27.22.4.3.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.6.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.5.4, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 12.31.

27.22.4.3.6.3 Test purpose

To verify that the ME displays the Icon contained in the GET INPUT proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.3.6.4 Method of test

27.22.4.3.6.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME screen shall be in its normal stand-by display.

27.22.4.3.6.4.2 Procedure

Expected Sequence 6.1A (GET INPUT, Basic icon, self-explanatory, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.3.6.4.2, Expected Sequence 6.1A.

Expected Sequence 6.1B (GET INPUT, Basic icon, self-explanatory, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.3.6.4.2, Expected Sequence 6.1B.

Expected Sequence 6.2A (GET INPUT, Basic icon, non self-explanatory, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.3.6.4.2, Expected Sequence 6.2A.

Expected Sequence 6.2B (GET INPUT, Basic icon, non self-explanatory, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.3.6.4.2, Expected Sequence 6.2B.

Expected Sequence 6.3A (GET INPUT, Colour icon, self-explanatory, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.3.6.4.2, Expected Sequence 6.3A.

Expected Sequence 6.3B (GET INPUT, Colour icon, self-explanatory, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.3.6.4.2, Expected Sequence 6.3B.

Expected Sequence 6.4A (GET INPUT, Colour icon, non self-explanatory, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.3.6.4.2, Expected Sequence 6.4A.

Expected Sequence 6.4B (GET INPUT, Colour icon, non self-explanatory, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.3.6.4.2, Expected Sequence 6.4B.

27.22.4.3.6.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 6.1A to 6.4B.

27.22.4.3.7 GET INPUT (Help Information)

27.22.4.3.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.7.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2 and clause 8.15.3.

27.22.4.3.7.3 Test purpose

To verify that the ME displays the text contained in the GET INPUT proactive UICC command, and returns a ‘help information required by the user’ result value in the TERMINAL RESPONSE command sent to the UICC if the user has indicated the need to get help information.

27.22.4.3.7.4 Method of test

27.22.4.3.7.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.3.7.4.2 Procedure

Expected Sequence 7.1 (GET INPUT, digits only, ME to echo text, ME supporting 8 bit data Message, help information available)

See ETSI TS 102 384 [26] in clause 27.22.4.3.7.4.2, Expected Sequence 7.1.

27.22.4.3.7.5 Test requirement

The ME shall operate in the manner defined in expected sequence 7.1.

27.22.4.3.8 GET INPUT (Support of Text Attribute)

27.22.4.3.8.1 GET INPUT (Support of Text Attribute – Left Alignment)

27.22.4.3.8.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.8.1.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 8.70.

27.22.4.3.8.1.3 Test purpose

To verify that the ME displays the text formatted according to the left alignment text attribute configuration contained in the GET INPUT proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.3.8.1.4 Method of test

27.22.4.3.8.1.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.3.8.1.4.2 Procedure

Expected Sequence 8.1 (GET INPUT, Text attribute – Left Alignment)

See ETSI TS 102 384 [26] in clause 27.22.4.3.8.1.4.2, Expected Sequence 8.1.

27.22.4.3.8.1.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.1.

27.22.4.3.8.2 GET INPUT (Support of Text Attribute – Center Alignment)

27.22.4.3.8.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.8.2.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 8.70.

27.22.4.3.8.2.3 Test purpose

To verify that the ME displays the text formatted according to the center alignment text attribute configuration contained in the GET INPUT proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.3.8.2.4 Method of test

27.22.4.3.8.2.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.3.8.2.4.2 Procedure

Expected Sequence 8.2 (GET INPUT, Text attribute – Center Alignment)

See ETSI TS 102 384 [26] in clause 27.22.4.3.8.2.4.2, Expected Sequence 8.2.

27.22.4.3.8.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.2.

27.22.4.3.8.3 GET INPUT (Support of Text Attribute – Right Alignment)

27.22.4.3.8.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.8.3.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 8.70.

27.22.4.3.8.3.3 Test purpose

To verify that the ME displays the text formatted according to the right alignment text attribute configuration contained in the GET INPUT proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.3.8.3.4 Method of test

27.22.4.3.8.3.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.3.8.3.4.2 Procedure

Expected Sequence 8.3 (GET INPUT, Text attribute – Right Alignment)

See ETSI TS 102 384 [26] in clause 27.22.4.3.8.3.4.2, Expected Sequence 8.3.

27.22.4.3.8.3.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.3.

27.22.4.3.8.4 GET INPUT (Support of Text Attribute – Large Font Size)

27.22.4.3.8.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.8.4.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 8.70.

27.22.4.3.8.4.3 Test purpose

To verify that the ME displays the text formatted according to the large font size text attribute configuration contained in the GET INPUT proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.3.8.4.4 Method of test

27.22.4.3.8.4.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.3.8.4.4.2 Procedure

Expected Sequence 8.4 (GET INPUT, Text attribute – Large Font Size)

See ETSI TS 102 384 [26] in clause 27.22.4.3.8.4.4.2, Expected Sequence 8.4.

27.22.4.3.8.4.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.4.

27.22.4.3.8.5 GET INPUT (Support of Text Attribute – Small Font Size)

27.22.4.3.8.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.8.5.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 8.70.

27.22.4.3.8.5.3 Test purpose

To verify that the ME displays the text formatted according to the small font size text attribute configuration contained in the GET INPUT proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.3.8.5.4 Method of test

27.22.4.3.8.5.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.3.8.5.4.2 Procedure

Expected Sequence 8.5 (GET INPUT, Text attribute – Small Font Size)

See ETSI TS 102 384 [26] in clause 27.22.4.3.8.5.4.2, Expected Sequence 8.5.

27.22.4.3.8.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.5.

27.22.4.3.8.6 GET INPUT (Support of Text Attribute – Bold On)

27.22.4.3.8.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.8.6.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 8.70.

27.22.4.3.8.6.3 Test purpose

To verify that the ME displays the text formatted according to the bold text attribute configuration contained in the GET INPUT proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.3.8.6.4 Method of test

27.22.4.3.8.6.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.3.8.6.4.2 Procedure

Expected Sequence 8.6 (GET INPUT, Text attribute – Bold On)

See ETSI TS 102 384 [26] in clause 27.22.4.3.8.6.4.2, Expected Sequence 8.6.

27.22.4.3.8.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.6.

27.22.4.3.8.7 GET INPUT (Support of Text Attribute – Italic On)

27.22.4.3.8.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.8.7.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 8.70.

27.22.4.3.8.7.3 Test purpose

To verify that the ME displays the text formatted according to the italic text attribute configuration contained in the GET INPUT proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.3.8.7.4 Method of test

27.22.4.3.8.7.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.3.8.7.4.2 Procedure

Expected Sequence 8.7 (GET INPUT, Text attribute – Italic On)

See ETSI TS 102 384 [26] in clause 27.22.4.3.8.7.4.2, Expected Sequence 8.7.

27.22.4.3.8.7.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.7.

27.22.4.3.8.8 GET INPUT (Support of Text Attribute – Underline On)

27.22.4.3.8.8.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.8.8.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 8.70.

27.22.4.3.8.8.3 Test purpose

To verify that the ME displays the text formatted according to the underline text attribute configuration contained in the GET INPUT proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.3.8.8.4 Method of test

27.22.4.3.8.8.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.3.8.8.4.2 Procedure

Expected Sequence 8.8 (GET INPUT, Text attribute – Underline On)

See ETSI TS 102 384 [26] in clause 27.22.4.3.8.8.4.2, Expected Sequence 8.8.

27.22.4.3.8.8.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.8.

27.22.4.3.8.9 GET INPUT (Support of Text Attribute – Strikethrough On)

27.22.4.3.8.9.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.8.9.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 8.70.

27.22.4.3.8.9.3 Test purpose

To verify that the ME displays the text formatted according to the strikethrough text attribute configuration contained in the GET INPUT proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.3.8.9.4 Method of test

27.22.4.3.8.9.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.3.8.9.4.2 Procedure

Expected Sequence 8.9 (GET INPUT, Text attribute – Strikethrough On)

See ETSI TS 102 384 [26] in clause 27.22.4.3.8.9.4.2, Expected Sequence 8.9.

27.22.4.3.8.9.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.9.

27.22.4.3.8.10 GET INPUT (Support of Text Attribute – Foreground and Background Colour)

27.22.4.3.8.10.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.8.10.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2, clause 8.15.3 and clause 8.70.

27.22.4.3.8.10.3 Test purpose

To verify that the ME displays the text formatted according to the fore- and background colour text attribute configuration contained in the GET INPUT proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.3.8.10.4 Method of test

27.22.4.3.8.10.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.3.8.10.4.2 Procedure

Expected Sequence 8.10 (GET INPUT, Text attribute – Foreground and Background Colour)

See ETSI TS 102 384 [26] in clause 27.22.4.3.8.10.4.2, Expected Sequence 8.10.

27.22.4.3.8.10.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.10.

27.22.4.3.9 GET INPUT (UCS2 display in Chinese)

27.22.4.3.9.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.9.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2 and clause 8.15.3.

Additionally the ME shall support the UCS2 facility for the coding of the Chinese character, as defined in the following technical specifications: ISO/IEC 10646 [17].

27.22.4.3.9.3 Test purpose

To verify that the ME displays the text contained in the GET INPUT proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.3.9.4 Method of test

27.22.4.3.9.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.3.9.4.2 Procedure

Expected Sequence 9.1 (GET INPUT, text string coding in UCS2 – Chinese characters, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.3.9.4.2, Expected Sequence 9.1.

Expected Sequence 9.2 (GET INPUT, max length for the text string coding in UCS2 – Chinese characters, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.3.9.4.2, Expected Sequence 9.2.

27.22.4.3.9.5 Test requirement

The ME shall operate in the manner defined in expected sequences 9.1 to 9.2

27.22.4.3.10 GET INPUT (UCS2 entry in Chinese)

27.22.4.3.10.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.10.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2 and clause 8.15.3.

Additionally the ME shall support the UCS2 facility for the coding of the Chinese character, as defined in ISO/IEC 10646 [17].

27.22.4.3.10.3 Test purpose

To verify that the ME displays the text contained in the GET INPUT proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.3.10.4 Method of test

27.22.4.3.10.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.3.10.4.2 Procedure

Expected Sequence 10.1 (GET INPUT, character set from UCS2 alphabet – Chinese characters, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.3.10.4.2, Expected Sequence 10.1.

Expected Sequence 10.2 (GET INPUT, character set from UCS2 alphabet – Chinese characters, Max length for the input, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.3.10.4.2, Expected Sequence 10.2.

27.22.4.3.10.5 Test requirement

The ME shall operate in the manner defined in expected sequences 10.1 to 10.2

27.22.4.3.11 GET INPUT (UCS2 display in Katakana)

27.22.4.3.11.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.11.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2 and clause 8.15.3.

Additionally the ME shall support the UCS2 facility for the coding of the Katakana characters, as defined in the following technical specifications: ISO/IEC 10646 [17].

27.22.4.3.11.3 Test purpose

To verify that the ME displays the text contained in the GET INPUT proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.3.11.4 Method of test

27.22.4.3.11.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.3.11.4.2 Procedure

Expected Sequence 11.1 (GET INPUT, text string coding in UCS2 in Katakana, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.3.11.4.2, Expected Sequence 11.1.

Expected Sequence 11.2 (GET INPUT, max length for the text string coding in UCS2 in Katakana, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.3.11.4.2, Expected Sequence 11.2.

27.22.4.3.11.5 Test requirement

The ME shall operate in the manner defined in expected sequences 11.1 to 11.2

27.22.4.3.12 GET INPUT (UCS2 entry in Katakana)

27.22.4.3.12.1 Definition and applicability

See clause 3.2.2.

27.22.4.3.12.2 Conformance requirement

The ME shall support the GET INPUT command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.11, clause 8.15, clause 8.15.1, clause 8.15.2 and clause 8.15.3.

Additionally the ME shall support the UCS2 facility for the coding of the Chinese character, as defined in ISO/IEC 10646 [17].

27.22.4.3.12.3 Test purpose

To verify that the ME displays the text contained in the GET INPUT proactive UICC command, and returns the text string entered in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.3.12.4 Method of test

27.22.4.3.12.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.3.12.4.2 Procedure

Expected Sequence 12.1 (GET INPUT, character set from UCS2 alphabet in Katakana, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.3.12.4.2, Expected Sequence 12.1.

Expected Sequence 12.2 (GET INPUT, character set from UCS2 alphabet in Katakana, Max length for the input, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.3.12.4.2, Expected Sequence 12.2.

27.22.4.3.12.5 Test requirement

The ME shall operate in the manner defined in expected sequences 12.1 to 12.2.

27.22.4.4 MORE TIME

27.22.4.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.4.2 Conformance requirement

The ME shall support the MORE TIME command as defined in:

– TS 31.111 [15] clause 6.4.4, clause 6.6.4, clause 5.2, clause 8.6 and clause 8.7.

27.22.4.4.3 Test purpose

To verify that the ME shall send a TERMINAL RESPONSE (OK) to the UICC after the ME receives the MORE TIME proactive UICC command.

27.22.4.4.4 Method of test

27.22.4.4.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.4.4.2 Procedure

Expected Sequence 1.1 (MORE TIME)

See ETSI TS 102 384 [26] in clause 27.22.4.4.4.2, Expected Sequence 1.1.

27.22.4.4.5 Test requirement

The ME shall operate in the manner defined in expected sequence 1.1.

27.22.4.5 PLAY TONE

27.22.4.5.1 PLAY TONE (Normal)

27.22.4.5.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.5.1.2 Conformance requirement

The ME shall support the PLAY TONE command as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.5, clause 6.6.5, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.16 and clause 8.8.

27.22.4.5.1.3 Test purpose

To verify that the ME plays an audio tone of a type and duration contained in the PLAY TONE proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

To verify that the ME plays the requested audio tone through the earpiece whilst not in call and shall superimpose the tone on top of the downlink audio whilst in call.

To verify that the ME displays the text contained in the PLAY TONE proactive UICC command.

27.22.4.5.1.4 Method of test

27.22.4.5.1.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table. The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.5.1.4.2 Procedure

Expected Sequence 1.1 (PLAY TONE)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: PLAY TONE 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: PLAY TONE 1.1.1
4	ME → USER	Display "Dial Tone" Play a standard supervisory dial tone through the external ringer for a duration of 5 s
5	ME → UICC	TERMINAL RESPONSE: PLAY TONE 1.1.1	[Command performed successfully]
6	UICC → ME	PROACTIVE UICC SESSION ENDED
7	UICC → ME	PROACTIVE COMMAND PENDING: PLAY TONE 1.1.2
8	ME → UICC	FETCH
9	UICC → ME	PROACTIVE COMMAND: PLAY TONE 1.1.2
10	ME → USER	Display "Sub. Busy" Play a standard supervisory called subscriber busy tone for a duration of 5 s
11	ME → UICC	TERMINAL RESPONSE: PLAY TONE 1.1.2	[Command performed successfully]
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13	UICC → ME	PROACTIVE COMMAND PENDING: PLAY TONE 1.1.3
14	ME → UICC	FETCH
15	UICC → ME	PROACTIVE COMMAND: PLAY TONE 1.1.3
16	ME → USER	Display "Congestion" Play a standard supervisory congestion tone for a duration of 5 s
17	ME → UICC	TERMINAL RESPONSE: PLAY TONE 1.1.3	[Command performed successfully]
18	UICC → ME	PROACTIVE UICC SESSION ENDED
19	UICC → ME	PROACTIVE COMMAND PENDING: PLAY TONE 1.1.4
20	ME → UICC	FETCH
21	UICC → ME	PROACTIVE COMMAND: PLAY TONE 1.1.4
22	ME → USER	Display "RP Ack" Play a standard supervisory radio path acknowledgement tone
23	ME → UICC	TERMINAL RESPONSE: PLAY TONE 1.1.4	[Command performed successfully]
24	UICC → ME	PROACTIVE UICC SESSION ENDED
25	UICC → ME	PROACTIVE COMMAND PENDING: PLAY TONE 1.1.5
26	ME → UICC	FETCH
27	UICC → ME	PROACTIVE COMMAND: PLAY TONE 1.1.5
28	ME → USER	Display "No RP" Play a standard supervisory radio path not available / call dropped tone for a duration of 5 s	[Note: The ME will only play three bursts as specified in TS 22.001 [2]]
29	ME → UICC	TERMINAL RESPONSE: PLAY TONE 1.1.5	[Command performed successfully]
30	UICC → ME	PROACTIVE UICC SESSION ENDED
31	UICC → ME	PROACTIVE COMMAND PENDING: PLAY TONE 1.1.6
32	ME → UICC	FETCH
33	UICC → ME	PROACTIVE COMMAND: PLAY TONE 1.1.6
34	ME → USER	Display "Spec Info" Play a standard supervisory error / special information tone for a duration of 5 s
35	ME → UICC	TERMINAL RESPONSE: PLAY TONE 1.1.6	[Command performed successfully]
36	UICC → ME	PROACTIVE UICC SESSION ENDED
37	UICC → ME	PROACTIVE COMMAND PENDING: PLAY TONE 1.1.7
38	ME → UICC	FETCH
39	UICC → ME	PROACTIVE COMMAND: PLAY TONE 1.1.7
40	ME → USER	Display "Call Wait" Play a standard supervisory call waiting tone for a duration of 5 s
41	ME → UICC	TERMINAL RESPONSE: PLAY TONE 1.1.7	[Command performed successfully]
42	UICC → ME	PROACTIVE UICC SESSION ENDED
43	UICC → ME	PROACTIVE COMMAND PENDING: PLAY TONE 1.1.8
44	ME → UICC	FETCH
45	UICC → ME	PROACTIVE COMMAND: PLAY TONE 1.1.8
46	ME → USER	Display "Ring Tone" Play a standard supervisory ringing tone for duration of 5 s
47	ME → UICC	TERMINAL RESPONSE: PLAY TONE 1.1.8	[Command performed successfully]
48	UICC → ME	PROACTIVE UICC SESSION ENDED
49	USER → ME	Set up a voice call	[ User dials 123456789 to connect to the network manually]
50	ME → USS	Establish voice call	[Voice call is established]
51	UICC → ME	PROACTIVE COMMAND PENDING: PLAY TONE 1.1.1
52	ME → UICC	FETCH
53	UICC → ME	PROACTIVE COMMAND: PLAY TONE 1.1.1
54	ME → USER	Display "Dial Tone" Superimpose the standard supervisory dial tone on the audio downlink for the duration of 5 s
55	ME → UICC	TERMINAL RESPONSE: PLAY TONE 1.1.1	[Command performed successfully]
56	UICC → ME	PROACTIVE UICC SESSION ENDED
57	USER → ME	The user ends the call
58	UICC → ME	PROACTIVE COMMAND PENDING: PLAY TONE 1.1.9
59	ME → UICC	FETCH
60	UICC → ME	PROACTIVE COMMAND: PLAY TONE 1.1.9
61	ME → USER	Display "This command instructs the ME to play an audio tone. Upon receiving this command, the ME shall check if it is currently in, or in the process of setting up (SET‑UP message sent to the network, see GSM"04.08"(8)), a speech call. – If the ME I" Play a general beep
62	ME → UICC	TERMINAL RESPONSE: PLAY TONE 1.1.9a or TERMINAL RESPONSE: PLAY TONE 1.1.9b	[Command performed successfully] or [Command beyond ME’s capabilities]
63	UICC → ME	PROACTIVE UICC SESSION ENDED
64	UICC → ME	PROACTIVE COMMAND PENDING: PLAY TONE 1.1.10
65	ME → UICC	FETCH
66	UICC → ME	PROACTIVE COMMAND: PLAY TONE 1.1.10
67	ME → USER	Display "Beep" Play a ME proprietary general beep
68	ME → UICC	TERMINAL RESPONSE: PLAY TONE 1.1.10a Or TERMINAL RESPONSE: PLAY TONE 1.1.10b	[Command performed successfully] or [Command beyond ME’s capabilities]
69	UICC → ME	PROACTIVE UICC SESSION ENDED
70	UICC → ME	PROACTIVE COMMAND PENDING: PLAY TONE 1.1.11
71	ME → UICC	FETCH
72	UICC → ME	PROACTIVE COMMAND: PLAY TONE 1.1.11
73	ME → USER	Display "Positive" Play a ME proprietary positive acknowledgement tone
74	ME → UICC	TERMINAL RESPONSE: PLAY TONE 1.1.11a or TERMINAL RESPONSE: PLAY TONE 1.1.11b	[Command performed successfully] or [Command beyond ME’s capabilities]
75	UICC → ME	PROACTIVE UICC SESSION ENDED
76	UICC → ME	PROACTIVE COMMAND PENDING: PLAY TONE 1.1.12
77	ME → UICC	FETCH
78	UICC → ME	PROACTIVE COMMAND: PLAY TONE 1.1.12
79	ME → USER	Display "Negative" Play a ME proprietary negative acknowledgement tone
80	ME → UICC	TERMINAL RESPONSE: PLAY TONE 1.1.12a or TERMINAL RESPONSE: PLAY TONE 1.1.12b	[Command performed successfully] or [Command beyond ME’s capabilities]
81	UICC → ME	PROACTIVE UICC SESSION ENDED
82	UICC → ME	PROACTIVE COMMAND PENDING: PLAY TONE 1.1.13
83	ME → UICC	FETCH
84	UICC → ME	PROACTIVE COMMAND: PLAY TONE 1.1.13
85	ME → USER	Display "Quick" Play a ME proprietary general beep
86	ME → UICC	TERMINAL RESPONSE: PLAY TONE 1.1.13a or TERMINAL RESPONSE: PLAY TONE 1.1.13b	[Command performed successfully] or [Command beyond ME’s capabilities]
87	UICC → ME	PROACTIVE UICC SESSION ENDED
88	UICC → ME	PROACTIVE COMMAND PENDING: PLAY TONE 1.1.14
89	ME → UICC	FETCH
90	UICC → ME	PROACTIVE COMMAND: PLAY TONE 1.1.14
91	ME → USER	Display "<ABORT>" Play an ME Error / Special information tone until user aborts this command (the command shall be aborted by the user within 1 minute)
92	ME → UICC	TERMINAL RESPONSE: PLAY TONE 1.1.14	[Proactive UICC session terminated by the user]
93	UICC → ME	PROACTIVE UICC SESSION ENDED
94	UICC → ME	PROACTIVE COMMAND PENDING: PLAY TONE 1.1.15
95	ME → UICC	FETCH
96	UICC → ME	PROACTIVE COMMAND: PLAY TONE 1.1.15	[No alpha identifier, no tone tag, no duration tag]
97	ME → User	ME plays general beep, or if not supported any (defined by ME-manufacturer) other supported tone	[ME uses default duration defined by ME‑manufacturer]
98	ME → UICC	TERMINAL RESPONSE: PLAY TONE 1.1.15	[Command performed successfully], [ME uses general beep, or if not supported any (defined by ME-manufacturer) other supported tone, uses default duration defined by ME‑manufacturer]
99	UICC → ME	PROACTIVE UICC SESSION ENDED

For coding, see ETSI TS 102 384 [26] in clause 27.22.4.5.1.4.2, Expected Sequence 1.1.

27.22.4.5.1.5 Test requirement

The ME shall operate in the manner defined in expected sequence 1.1.

27.22.4.5.2 PLAY TONE (UCS2 display in Cyrillic)

27.22.4.5.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.5.2.2 Conformance requirement

The ME shall support the PLAY TONE command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.2, clause 8.16 and clause 8.8.

Additionally the ME shall support the UCS2 facility for the coding of the Cyrillic alphabet, as defined in ISO/IEC 10646 [17].

27.22.4.5.2.3 Test purpose

To verify that the ME displays the text contained in the PLAY TONE proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

To verify that the ME plays the requested audio tone through the earpiece.

27.22.4.5.2.4 Method of test

27.22.4.5.2.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.5.2.4.2 Procedure

Expected Sequence 2.1 (PLAY TONE, character set from UCS2 alphabet in Russian, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.5.2.4.2, Expected Sequence 2.1.

27.22.4.5.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 2.1.

27.22.4.5.3 PLAY TONE (display of Icon)

27.22.4.5.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.5.3.2 Conformance requirement

The ME shall support the PLAY TONE command as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.5, clause 6.6.5, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.16, clause 8.8 and clause 8.31.

27.22.4.5.3.3 Test purpose

To verify that the ME plays the requested audio tone through the earpiece.

To verify that the ME displays the icon contained in the PLAY TONE proactive UICC command.

27.22.4.5.3.4 Method of test

27.22.4.5.3.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.5.3.4.2 Procedure

Expected Sequence 3.1A (PLAY TONE, Basic icon, self-explanatory, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.5.3.4.2, Expected Sequence 3.1A.

Expected Sequence 3.1B (PLAY TONE, Basic icon, self-explanatory, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.5.3.4.2, Expected Sequence 3.1B.

Expected Sequence 3.2A (PLAY TONE, Basic icon, non self-explanatory, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.5.3.4.2, Expected Sequence 3.2A.

Expected Sequence 3.2B (PLAY TONE, Basic icon, non self-explanatory, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.5.3.4.2, Expected Sequence 3.2B.

Expected Sequence 3.3A (PLAY TONE, Colour icon, self-explanatory, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.5.3.4.2, Expected Sequence 3.3A.

Expected Sequence 3.3B (PLAY TONE, Colour icon, self-explanatory, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.5.3.4.2, Expected Sequence 3.3B.

Expected Sequence 3.4A (PLAY TONE, Colour icon, non self-explanatory, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.5.3.4.2, Expected Sequence 3.4A.

Expected Sequence 3.4B (PLAY TONE, Colour icon, non self-explanatory, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.5.3.4.2, Expected Sequence 3.4B.

27.22.4.5.3.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 3.1A to 3.4B.

27.22.4.5.4 PLAY TONE (Support of Text Attribute)

27.22.4.5.4.1 PLAY TONE (Support of Text Attribute – Left Alignment)

27.22.4.5.4.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.5.4.1.2 Conformance requirement

The ME shall support the PLAY TONE command as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.5, clause 6.6.5, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.16, clause 8.8, clause 8.31 and clause 8.70.

27.22.4.5.4.1.3 Test purpose

To verify that the ME displays the text formatted according to the left alignment text attribute configuration contained in the PLAY TONE proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.5.4.1.4 Method of test

27.22.4.5.4.1.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.5.4.1.4.2 Procedure

Expected Sequence 4.1 (PLAY TONE, Text Attribute – Left Alignment)

See ETSI TS 102 384 [26] in clause 27.22.4.5.4.1.4.2, Expected Sequence 4.1.

27.22.4.5.4.1.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 4.1.

27.22.4.5.4.2 PLAY TONE (Support of Text Attribute – Center Alignment)

27.22.4.5.4.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.5.4.2.2 Conformance requirement

The ME shall support the PLAY TONE command as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.5, clause 6.6.5, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.16, clause 8.8, clause 8.31 and clause 8.70.

27.22.4.5.4.2.3 Test purpose

To verify that the ME displays the text formatted according to the center alignment text attribute configuration contained in the PLAY TONE proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.5.4.2.4 Method of test

27.22.4.5.4.2.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.5.4.2.4.2 Procedure

Expected Sequence 4.2 (PLAY TONE, Text Attribute – Centre Alignment)

See ETSI TS 102 384 [26] in clause 27.22.4.5.4.2.4.2, Expected Sequence 4.2.

27.22.4.5.4.2.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 4.2.

27.22.4.5.4.3 PLAY TONE (Support of Text Attribute – Right Alignment)

27.22.4.5.4.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.5.4.3.2 Conformance requirement

The ME shall support the PLAY TONE command as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.5, clause 6.6.5, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.16, clause 8.8, clause 8.31 and clause 8.70.

27.22.4.5.4.3.3 Test purpose

To verify that the ME displays the text formatted according to the right alignment text attribute configuration contained in the PLAY TONE proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.5.4.3.4 Method of test

27.22.4.5.4.3.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.5.4.3.4.2 Procedure

Expected Sequence 4.3 (PLAY TONE, Text Attribute – Right Alignment)

See ETSI TS 102 384 [26] in clause 27.22.4.5.4.3.4.2, Expected Sequence 4.3.

27.22.4.5.4.3.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 4.3.

27.22.4.5.4.4 PLAY TONE (Support of Text Attribute – Large Font Size)

27.22.4.5.4.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.5.4.4.2 Conformance requirement

The ME shall support the PLAY TONE command as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.5, clause 6.6.5, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.16, clause 8.8, clause 8.31 and clause 8.70.

27.22.4.5.4.4.3 Test purpose

To verify that the ME displays the text formatted according to the large font size text attribute configuration contained in the PLAY TONE proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.5.4.4.4 Method of test

27.22.4.5.4.4.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.5.4.4.4.2 Procedure

Expected Sequence 4.4 (PLAY TONE, Text Attribute – Large Font Size)

See ETSI TS 102 384 [26] in clause 27.22.4.5.4.4.4.2, Expected Sequence 4.4.

27.22.4.5.4.4.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 4.4.

27.22.4.5.4.5 PLAY TONE (Support of Text Attribute – Small Font Size)

27.22.4.5.4.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.5.4.5.2 Conformance requirement

The ME shall support the PLAY TONE command as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.5, clause 6.6.5, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.16, clause 8.8, clause 8.31 and clause 8.70.

27.22.4.5.4.5.3 Test purpose

To verify that the ME displays the text formatted according to the small font size text attribute configuration contained in the PLAY TONE proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.5.4.5.4 Method of test

27.22.4.5.4.5.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.5.4.5.4.2 Procedure

Expected Sequence 4.5 (PLAY TONE, Text Attribute – Small Font Size)

See ETSI TS 102 384 [26] in clause 27.22.4.5.4.5.4.2, Expected Sequence 4.5.

27.22.4.5.4.5.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 4.5.

27.22.4.5.4.6 PLAY TONE (Support of Text Attribute – Bold On)

27.22.4.5.4.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.5.4.6.2 Conformance requirement

The ME shall support the PLAY TONE command as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.5, clause 6.6.5, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.16, clause 8.8, clause 8.31 and clause 8.70.

27.22.4.5.4.6.3 Test purpose

To verify that the ME displays the text formatted according to the bold text attribute configuration contained in the PLAY TONE proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.5.4.6.4 Method of test

27.22.4.5.4.6.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.5.4.6.4.2 Procedure

Expected Sequence 4.6 (PLAY TONE, Text Attribute – Bold On)

See ETSI TS 102 384 [26] in clause 27.22.4.5.4.6.4.2, Expected Sequence 4.6.

27.22.4.5.4.6.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 4.6.

27.22.4.5.4.7 PLAY TONE (Support of Text Attribute – Italic On)

27.22.4.5.4.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.5.4.7.2 Conformance requirement

The ME shall support the PLAY TONE command as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.5, clause 6.6.5, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.16, clause 8.8, clause 8.31 and clause 8.70.

27.22.4.5.4.7.3 Test purpose

To verify that the ME displays the text formatted according to the italic text attribute configuration contained in the PLAY TONE proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.5.4.7.4 Method of test

27.22.4.5.4.7.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.5.4.7.4.2 Procedure

Expected Sequence 4.7 (PLAY TONE, Text Attribute – Italic On)

See ETSI TS 102 384 [26] in clause 27.22.4.5.4.7.4.2, Expected Sequence 4.7.

27.22.4.5.4.7.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 4.7.

27.22.4.5.4.8 PLAY TONE (Support of Text Attribute – Underline On)

27.22.4.5.4.8.1 Definition and applicability

See clause 3.2.2.

27.22.4.5.4.8.2 Conformance requirement

The ME shall support the PLAY TONE command as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.5, clause 6.6.5, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.16, clause 8.8, clause 8.31 and clause 8.70.

27.22.4.5.4.8.3 Test purpose

To verify that the ME displays the text formatted according to the underline text attribute configuration contained in the PLAY TONE proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.5.4.8.4 Method of test

27.22.4.5.4.8.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.5.4.8.4.2 Procedure

Expected Sequence 4.8 (PLAY TONE, Text Attribute – Underline On)

See ETSI TS 102 384 [26] in clause 27.22.4.5.4.8.4.2, Expected Sequence 4.8.

27.22.4.5.4.8.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 4.8.

27.22.4.5.4.9 PLAY TONE (Support of Text Attribute – Strikethrough On)

27.22.4.5.4.9.1 Definition and applicability

See clause 3.2.2.

27.22.4.5.4.9.2 Conformance requirement

The ME shall support the PLAY TONE command as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.5, clause 6.6.5, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.16, clause 8.8, clause 8.31 and clause 8.70.

27.22.4.5.4.9.3 Test purpose

To verify that the ME displays the text formatted according to the strikethrough text attribute configuration contained in the PLAY TONE proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.5.4.9.4 Method of test

27.22.4.5.4.9.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.5.4.9.4.2 Procedure

Expected Sequence 4.9 (PLAY TONE, Text Attribute – Strikethrough On)

See ETSI TS 102 384 [26] in clause 27.22.4.5.4.9.4.2, Expected Sequence 4.9.

27.22.4.5.4.9.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 4.9.

27.22.4.5.4.10 PLAY TONE (Support of Text Attribute – Foreground and Background Colour)

27.22.4.5.4.10.1 Definition and applicability

See clause 3.2.2.

27.22.4.5.4.10.2 Conformance requirement

The ME shall support the PLAY TONE command as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.5, clause 6.6.5, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.16, clause 8.8, clause 8.31 and clause 8.70.

27.22.4.5.4.10.3 Test purpose

To verify that the ME displays the text formatted according to the foreground and background colour text attribute configuration contained in the PLAY TONE proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.5.4.10.4 Method of test

27.22.4.5.4.10.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.5.4.10.4.2 Procedure

Expected Sequence 4.10 (PLAY TONE, Text Attribute – Foreground and Background Colour)

See ETSI TS 102 384 [26] in clause 27.22.4.5.4.10.4.2, Expected Sequence 4.10.

27.22.4.5.4.10.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 4.10.

27.22.4.5.5 PLAY TONE (UCS2 display in Chinese)

27.22.4.5.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.5.5.2 Conformance requirement

The ME shall support the PLAY TONE command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.2, clause 8.16 and clause 8.8.

Additionally the ME shall support the UCS2 facility for the coding of the Chinese characters, as defined in ISO/IEC 10646 [17].

27.22.4.5.5.3 Test purpose

To verify that the ME displays the text contained in the PLAY TONE proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

To verify that the ME plays the requested audio tone through the earpiece.

27.22.4.5.5.4 Method of test

27.22.4.5.5.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.5.5.4.2 Procedure

Expected Sequence 5.1 (PLAY TONE, character set from UCS2 alphabet in Chinese, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.5.5.4.2, Expected Sequence 5.1.

27.22.4.5.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 5.1.

27.22.4.5.6 PLAY TONE (UCS2 display in Katakana)

27.22.4.5.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.5.6.2 Conformance requirement

The ME shall support the PLAY TONE command as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.3, clause 6.6.3, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.2, clause 8.16 and clause 8.8.

Additionally the ME shall support the UCS2 facility for the coding of the Katakana characters, as defined in ISO/IEC 10646 [17].

27.22.4.5.6.3 Test purpose

To verify that the ME displays the text contained in the PLAY TONE proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

To verify that the ME plays the requested audio tone through the earpiece.

27.22.4.5.6.4 Method of test

27.22.4.5.6.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.5.6.4.2 Procedure

Expected Sequence 6.1 (PLAY TONE, with UCS2 in Katakana, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.5.6.4.2, Expected Sequence 6.1.

27.22.4.5.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.1.

27.22.4.6 POLL INTERVAL

27.22.4.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.6.2 Conformance requirement

The ME shall support the POLL INTERVAL command as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.6, clause 6.6.6, clause 5.2, clause 8.6, clause 8.7 and clause 8.8.

27.22.4.6.3 Test purpose

To verify that the ME shall send a TERMINAL RESPONSE (OK) to the UICC after the ME receives the POLL INTERVAL proactive UICC command.

To verify that the ME gives a valid response to the polling interval requested by the UICC.

To verify that the ME sends STATUS commands to the UICC at an interval no longer than the interval negotiated by the UICC.

27.22.4.6.4 Method of test

27.22.4.6.4.1 Initial conditions

The ME is connected to the USIM Simulator.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.6.4.2 Procedure

See ETSI TS 102 384 [26] in clause 27.22.4.6.4.2, Expected Sequence 1.1.

Note: If the requested poll interval is not supported by the ME, the ME is allowed to use a different one as stated in TS 31.111 [15], clause 6.4.6.

27.22.4.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 1.1.

27.22.4.7 REFRESH

27.22.4.7.1 REFRESH (normal)

27.22.4.7.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.7.1.2 Conformance requirement

The ME shall support the REFRESH command as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.7, clause 6.6.13, clause 5.2, clause 8.6, clause 8.7 and clause 8.18.

Consequently the ME shall support the USIM Initialization procedure as defined in:

– TS 31.102 [14] clause 5.1.1.2 and ETSI TS 102 221[13] clause 11.1.2

27.22.4.7.1.3 Test purpose

To verify that the ME performs the Proactive Command – REFRESH in accordance with the Command Qualifier. This shall require the ME to perform:

– the UICC and USIM initialization,

– a re-read of the contents and structure of the EFs on the UICC that have been notified as changed and are either part of initialization or used during the test,

– a restart of the card session,

– a successfull return of the result of the execution of the command in the TERMINAL RESPONSE command send to the UICC.

27.22.4.7.1.4 Method of test

27.22.4.7.1.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table..

The elementary files are coded as Toolkit default except for expected sequence 1.3.

For expected sequence 1.3 the global phonebook shall be present.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

These values might be overwritten with values defined in the expected sequences itself.

Prior to the execution of expected sequence 1.2 the FDN service shall be enabled.

27.22.4.7.1.4.2 Procedure

Expected Sequence 1.1 (REFRESH, USIM Initialization)

Step	Direction	MESSAGE / Action	Comments
1	UICC→ ME	PROACTIVE COMMAND PENDING: REFRESH 1.1.1	[To inform the ME that FDN becomes enabled]
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: REFRESH 1.1.1
4	UICC	EF EST contents states FDN enabled	[New EF EST value: 01]
5	ME → UICC	USIM Initialization including send STATUS[P1=’01’]	[ME performs USIM initialization in accordance with TS 31.111 [15] clause 6.4.7]
6	ME → UICC	TERMINAL RESPONSE: REFRESH 1.1.1A Or TERMINAL RESPONSE: REFRESH 1.1.1B	[normal ending] [additional EFs read]
7	UICC → ME	PROACTIVE UICC SESSION ENDED
8	USER → ME	Call setup to "321"
9	ME → USER	Call set up not allowed
10	USER → ME	Call setup to "123"
11	ME → USS	Setup	Called party BCD number shall be "123"

PROACTIVE COMMAND: REFRESH 1.1.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: USIM Initialization

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

TERMINAL RESPONSE: REFRESH 1.1.1A

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: USIM Initialization

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

TERMINAL RESPONSE: REFRESH 1.1.1B

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: USIM Initialization

Device identities

Source device: ME

Destination device: UICC

Result

General Result: REFRESH performed with additional EFs read

Coding:

BER-TLV:

Expected Sequence 1.2 (REFRESH, File Change Notification)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: REFRESH 1.2.1	[To inform the ME that EF FDN will be in an updated state, FDN service already enabled]
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: REFRESH 1.2.1
4	UICC	Update EF FDN RECORD 1	[EF FDN record 1 updated to contain the dialling string "0123456789"]
5	ME → UICC	TERMINAL RESPONSE: REFRESH 1.2.1A Or TERMINAL RESPONSE: REFRESH 1.2.1B	[normal ending] [additional EFs read]
6	UICC → ME	PROACTIVE UICC SESSION ENDED
7	USER → ME	Call setup to "123"
8	ME → USER	Call set up not allowed
9	USER → ME	Call setup to "0123456789"
10	ME → USS	Setup	Called party BCD number shall be "0123456789"

PROACTIVE COMMAND: REFRESH 1.2.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: File Change Notification

Device identities

Source device: UICC

Destination device: ME

File List: EF FDN

Coding:

BER-TLV:	D0	12	81	03	01	01	01	82	02	81	82	92
	07	01	3F	00	7F	FF	6F	3B

TERMINAL RESPONSE: REFRESH 1.2.1A

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: File Change Notification

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

TERMINAL RESPONSE: REFRESH 1.2.1B

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: File Change Notification

Device identities

Source device: ME

Destination device: UICC

Result

General Result: REFRESH performed with additional EFs read

Coding:

BER-TLV:

Expected Sequence 1.3 (REFRESH, USIM Initialization and File Change Notification)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: REFRESH 1.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: REFRESH 1.3.1
4	UICC	Update EF ADN in the global phonebook	[EF ADN entry 1 of the global phonebook to contain the the new and previously unused alpha identifier "Changed"
5	ME → UICC	USIM Initialization including sending STATUS [P1=’01’]	[ME performs USIM initialization in accordance with TS 31.111 [15] clause 6.4.7]
6	ME → UICC	TERMINAL RESPONSE: REFRESH 1.3.1A Or TERMINAL RESPONSE: REFRESH 1.3.1B	[normal ending] [additional EFs read]
7	UICC → ME	PROACTIVE UICC SESSION ENDED
8	USER → ME	Use an MMI dependent procedure to display the entry with the alpha identifier "Changed" stored in record 1 of EF ADN in the global phonebook	[To ensure that EF ADN in the global phonebook has been read after issuing the Refresh command]
9	ME → USER	The ME shall display the alpha identifier "Changed" for record 1 of EF ADN in the global phonebook

PROACTIVE COMMAND: REFRESH 1.3.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: USIM Initialization and File Change Notification

Device identities

Source device: UICC

Destination device: ME

File List: ADN in the global phonebook

Coding:

BER-TLV:	D0	12	81	03	01	01	02	82	02	81	82	92
	Note 1

Note 1: Length and data of the file list TLV depend on the card configuration used in this test. The global phonebook shall be used. The number of changed files shall be set to ’01’.

TERMINAL RESPONSE: REFRESH 1.3.1A

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: USIM Initialization and File Change Notification

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

TERMINAL RESPONSE: REFRESH 1.3.1B

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: USIM Initialization and File Change Notification

Device identities

Source device: ME

Destination device: UICC

Result

General Result: REFRESH performed with additional EFs read

Coding:

BER-TLV:

Expected Sequence 1.4 (REFRESH, USIM Initialization and Full File Change Notification)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: REFRESH 1.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: REFRESH 1.4.1
4	UICC	EF EST contents states FDN enabled	[New EF EST value: 01]
5	UICC	Update EF FDN	[EF FDN record 1 updated to contain the dialling string "0123456789"]
6	ME → UICC	USIM Initialization including send STATUS[P1=’01’]	[ME performs USIM initialization in accordance with TS 31.111 [15] clause 6.4.7]
7	ME → UICC	TERMINAL RESPONSE: REFRESH 1.4.1A Or TERMINAL RESPONSE: REFRESH 1.4.1B	[normal ending] [additional EFs read]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	Call setup to "321"
10	ME → USER	Call set up not allowed
11	USER → ME	Call setup to "0123456789"
12	ME → USS	Setup	Called party BCD number shall be "0123456789"

PROACTIVE COMMAND: REFRESH 1.4.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: USIM Initialization and Full File Change Notification

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

TERMINAL RESPONSE: REFRESH 1.4.1A

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: USIM Initialization and Full file Change Notification

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

TERMINAL RESPONSE: REFRESH 1.4.1B

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: USIM Initialization and full File change Notification

Device identities

Source device: ME

Destination device: UICC

Result

General Result: REFRESH performed with additional EFs read

Coding:

BER-TLV:

Expected Sequence 1.5 (REFRESH, UICC Reset)

Step	Direction	MESSAGE / Action	Comments
1	UICC→ ME	PROACTIVE COMMAND PENDING: REFRESH 1.5.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: REFRESH 1.5.1
4	ME → UICC	STATUS[P1=’02’]	ME indicates to USIM that the termination procedure is starting
5	ME → UICC	ME resets the UICC, performs USIM initialisation, including send STATUS[P1=’01’] and no TERMINAL RESPONSE shall be sent

PROACTIVE COMMAND: REFRESH 1.5.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: UICC Reset

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

Expected Sequence 1.6 (REFRESH, USIM Initialization after SMS-PP data download)

Step	Direction	MESSAGE / Action	Comments
1	ME	The ME shall be in its normal idle mode	[Start a sequence to verify that the ME returns the RP-ACK message back to the USS, if the UICC responds with ’90 00′]
2	USS → ME	SMS-PP Data Download Message 1.6.1
3	ME → USER	The ME shall not display the message or alert the user of a short message waiting
4	ME → UICC	ENVELOPE: SMS-PP DOWNLOAD 1.6.1
5	UICC → ME	SW1/SW2 of ’90 00′
6	ME  USS	RP-ACK
7	UICC → ME	PROACTIVE COMMAND PENDING: REFRESH 1.1.1
8	ME → UICC	FETCH
9	UICC → ME	PROACTIVE COMMAND: REFRESH 1.1.1
10	UICC	EF EST contents states FDN enabled	[New EF EST value: 01]
11	ME → UICC	USIM Initialization including send STATUS[P1=’01’]	[ME performs USIM initialization in accordance with TS 31.111 [15] clause 6.4.7]
12	ME → UICC	TERMINAL RESPONSE: REFRESH 1.1.1A Or TERMINAL RESPONSE: REFRESH 1.1.1B	[normal ending] [additional EFs read]
13	UICC → ME	PROACTIVE UICC SESSION ENDED
14	USER → ME	Call setup to "321"
15	ME → USER	Call set up not allowed
16	USER → ME	Call setup to "123"
17	ME → USS	Setup	Called party BCD number shall be "123"

SMS-PP (Data Download) Message 1.6.1

Logically:

SMS TPDU

TP-MTI SMS-DELIVER

TP-MMS No more messages waiting for the MS in this SC

TP-RP TP-Reply-Path is not set in this SMS-DELIVER

TP-UDHI TP-UD field contains only the short message

TP-SRI A status report will not be returned to the SME

TP-OA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "1234"

TP-PID (U)SIM Data download

TP-DCS

Coding Group General Data Coding

Compression Text is uncompressed

Message Class Class 2 (U)SIM Specific Message

Alphabet 8 bit data

TP-SCTS: 01/01/98 00:00:00 +0

TP-UDL 13

TP-UD "Short Message"

Coding:

Coding	04	04	91	21	43	7F	16	89	10	10	00	00
	00	00	0D	53	68	6F	72	74	20	4D	65	73
	73	61	67	65

ENVELOPE: SMS-PP DOWNLOAD 1.6.1

Logically:

SMS-PP Download

Device identities

Source device: Network

Destination device: UICC

Address

TON International number

NPI "ISDN / telephone numbering plan"

Dialling number string "112233445566778"

SMS TPDU

TP-MTI SMS-DELIVER

TP-MMS No more messages waiting for the MS in this SC

TP-RP TP-Reply-Path is not set in this SMS-DELIVER

TP-UDHI TP-UD field contains only the short message

TP-SRI A status report will not be returned to the SME

TP-OA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "1234"

TP-PID (U)SIM Data download

TP-DCS

Coding Group General Data Coding

Compression Text is uncompressed

Message Class Class 2 (U)SIM Specific Message

Alphabet 8 bit data

TP-SCTS: 01/01/98 00:00:00 +0

TP-UDL 13

TP-UD "Short Message"

Coding:

BER-TLV:	D1	2D	82	02	83	81	06	09	91	11	22	33
	44	55	66	77	F8	8B	1C	04	04	91	21	43
	7F	16	89	10	10	00	00	00	00	0D	53	68
	6F	72	74	20	4D	65	73	73	61	67	65

Expected Sequence 1.7 (REFRESH, USIM Application Reset)

Step	Direction	MESSAGE / Action	Comments
1	UICC→ ME	PROACTIVE COMMAND PENDING: REFRESH 1.7.1	[To inform the ME that FDN becomes enabled]
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: REFRESH 1.7.1	No UICC reset shall be performed between steps 3 and 9.
4	ME → UICC	STATUS[P1=’02’]	ME indicates to USIM that the termination procedure is starting
5	ME → UICC	Select AID=USIM (P2=’44’) OR (P2=’4C’)	Application termination
6	UICC	EF EST contents states FDN enabled	[New EF EST value: 01]
7	ME → UICC	USIM Initialization, including send STATUS[P1=’01’]	[ME performs USIM initialization]
8	ME → UICC	TERMINAL RESPONSE: REFRESH 1.7.1	[normal ending]
9	UICC → ME	PROACTIVE UICC SESSION ENDED
10	USER → ME	Call setup to "321"
11	ME → USER	Call set up not allowed
12	USER → ME	Call setup to "123"
13	ME → USS	Setup	Called party BCD number shall be "123"
14	USS → ME	The ME receives the CONNECT message from the USS.
15	USER → ME	The user ends the call after a few seconds.

PROACTIVE COMMAND: REFRESH 1.7.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: USIM Application Reset

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

TERMINAL RESPONSE: REFRESH 1.7.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: USIM Application Reset

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.7.1.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1 to 1.7.

27.22.4.7.2 REFRESH (IMSI changing procedure)

27.22.4.7.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.7.2.2 Conformance requirement

The ME shall support the REFRESH command as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.7, clause 6.4.7.1, clause 6, clause 6.6.13, clause 5.2, clause 8.6, clause 8.7 and clause 8.18.

Additionally the ME shall support the USIM Initialization and USIM application closure procedure as defined in:

– TS 31.102 [14] clause 5.1.2 and Annex I.

27.22.4.7.2.3 Test purpose

To verify that the ME performs the Proactive Command – REFRESH in accordance with the Command Qualifier and the IMSI changing procedure. This may require the ME to perform:

– the USIM initialization

– a re-read of the contents and structure of the IMSI on the USIM

– a restart of the card session

– a successful return of the result of the execution of the command in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.7.2.4 Method of test

27.22.4.7.2.4.1 Initial conditions

The ME is connected to the USIM Simulator and connected to the USS and registered in idle mode.

The USS uses Network Mode of Operation II according to TS 34.108 [12] clause 7.2.2.

The GERAN or UTRAN parameters of the USS are:

– Mobile Country Code (MCC) = 246;

– Mobile Network Code (MNC) = 81;

– Location Area Code (LAC) = 0001;

– Routing Area Code (RAC) = 05;

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ATT flag broadcast in the SYSTEM INFORMATION BLOCK TYPE 1 on the BCCH is set to "UEs shall apply IMSI attach and detach procedure" for Expected Sequences 2.1 to 2.7.

27.22.4.7.2.4.2 Procedure

Expected Sequence 2.1 (REFRESH, UICC Reset for IMSI Changing procedure)

Step	Direction	MESSAGE / Action	Comments
1	UICC→ ME	PROACTIVE COMMAND PENDING: REFRESH 2.1.1	[To inform the ME that IMSI has changed]
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: REFRESH 2.1.1
4	ME → USS	IMSI DETACH INDICATION and/or DETACH REQUEST	Indicates IMSI detach and/or GPRS detach, depending on if the ME is CS and/or PS registered according to its capabilities Note: this step can be performed in parallel or after step 5.
5	ME → UICC	STATUS[P1=’02’]	ME indicates to USIM that the termination procedure is starting
6	ME → UICC	ME performs UICC reset	Both cold and warm resets are allowed
7	UICC	Update EF IMSI, EF LOCI and EF PSLOCI	Update the content of EF IMSI to "246813579", TMSI in EF LOCI and P-TMSI in EF PSLOCI be set to ‘FF FF FF FF’
8	ME → UICC	ME performs USIM Initialization, including send STATUS[P1=’01’] and no TERMINAL RESPONSE shall be sent
9	ME → USS	LOCATION UPDATING REQUEST and/or ATTACH REQUEST	The ME will register using IMSI "246813579" in CS and/or PS depending on its capabilities
10	USS → ME	LOCATION UPDATING ACCEPT and/or ATTACH ACCEPT
11	ME → USS	TMSI REALLOCATION COMPLETE and/or ATTACH COMPLETE

PROACTIVE COMMAND: REFRESH 2.1.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: UICC RESET

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

Expected Sequence 2.2 (REFRESH, USIM Application Reset for IMSI Changing procedure )

Step	Direction	MESSAGE / Action	Comments
1	UICC→ ME	PROACTIVE COMMAND PENDING: REFRESH 2.2.1	[To inform the ME that IMSI has changed]
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: REFRESH 2.2.1
4	ME🡪USS	IMSI DETACH INDICATION and/or DETACH REQUEST	Indicates IMSI detach and/or GPRS detach, depending on if the ME is CS and/or PS registered according to its capabilities (performed in parallel or after step 5 and 6)
5	ME → UICC	STATUS[P1=’02’]	ME indicates to USIM that the termination procedure is starting
6	ME → UICC		Application termination
7	UICC	Update EF IMSI, EF LOCI and EF PSLOCI	The 3G session termination procedure has been completed by the ME. The content of EF IMSI has been updated to "246813579" and TMSI in EF LOCI and P-TMSI in EF PSLOCI are updated to ‘FF FF FF FF’
8	ME → UICC	SELECT AID=USIM (P2=’0x’)	Application selection
9	ME → UICC	USIM Initialization, including send STATUS[P1=’01’]	[ME performs USIM initialization]
10	ME → UICC	TERMINAL RESPONSE: REFRESH 2.2.1	[normal ending]
11	UICC → ME	PROACTIVE UICC SESSION ENDED
12	ME  USS	LOCATION UPDATING REQUEST and/or ATTACH REQUEST	The ME will register using IMSI "246813579" in CS and/or PS depending on its capabilities
13	USS  ME	LOCATION UPDATING ACCEPT and/or ATTACH ACCEPT
14	ME  USS	TMSI REALLOCATION COMPLETE and/or ATTACH COMPLETE

PROACTIVE COMMAND: REFRESH 2.2.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: USIM Application Reset

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

TERMINAL RESPONSE: REFRESH 2.2.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: USIM Application Reset

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 2.3 (REFRESH, 3G Session Reset for IMSI Changing procedure)

Step	Direction	MESSAGE / Action	Comments
1	UICC→ ME	PROACTIVE COMMAND PENDING: REFRESH 2.3.1	[To inform the ME that IMSI has changed]
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: REFRESH 2.3.1
4	ME→USS	IMSI DETACH INDICATION and/or DETACH REQUEST	Indicates IMSI detach and/or GPRS detach, depending on if the ME is CS and/or PS registered according to its capabilities Note: this step can be performed in parallel or after step 5.
5	ME → UICC	STATUS[P1=’02’]	If A.1/172 is supported, then the ME indicates to USIM that the termination procedure is starting,. completes the 3G session termination procedure and resets the application via SELECT by DF name command with the AID. The ME performs the USIM initialization.
6	UICC	Update EF IMSI, EF LOCI and EF PSLOCI	The content of EF IMSI has been updated to "246813579" and TMSI in EF LOCI and P-TMSI in EF PSLOCI are updated to ‘FF FF FF FF’
7	ME → UICC	TERMINAL RESPONSE: REFRESH 2.3.1A Or TERMINAL RESPONSE: REFRESH 2.3.1B	[normal ending]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	ME→ USS	LOCATION UPDATING REQUEST and/or ATTACH REQUEST	The ME will register using IMSI "246813579" in CS and/or PS depending on its capabilities
10	USS → ME	LOCATION UPDATING ACCEPT and/or ATTACH ACCEPT
11	ME → USS	TMSI REALLOCATION COMPLETE and/or ATTACH COMPLETE

PROACTIVE COMMAND: REFRESH 2.3.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: UICC

Destination device: ME

File list

Number of files: 3

File: EF IMSI

File: EF PSLOCI

File: EF LOCI

Coding:

BER-TLV:	D0	1E	81	03	01	01	06	82	02	81	82	92
	13	03	3F	00	7F	FF	6F	07	3F	00	7F	FF
	6F	73	3F	00	7F	FF	6F	7E

TERMINAL RESPONSE: REFRESH 2.3.1A

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

TERMINAL RESPONSE: REFRESH 2.3.1B

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: ME

Destination device: UICC

Result

General Result: REFRESH performed with additional EFs read

Coding:

BER-TLV:

Expected Sequence 2.4 (REFRESH, reject 3G Session Reset for IMSI Changing procedure during CS call)

Step	Direction	MESSAGE / Action	Comments
1	USER → ME	MO Call setup
2	ME → USS	Call established and maintained
3	UICC → ME	PROACTIVE COMMAND PENDING: REFRESH 2.4.1
4	ME → UICC	FETCH
5	UICC → ME	PROACTIVE COMMAND: REFRESH 2.4.1
6	ME → UICC	TERMINAL RESPONSE: REFRESH 2.4.1A Or TERMINAL RESPONSE: REFRESH 2.4.1B	ME rejects REFRESH proactive command
7	UICC → ME	PROACTIVE UICC SESSION ENDED	Note: EF IMSI, EF LOCI and EF PSLOCI are not updated by the UICC, see TS 31.111[15], cl. 6.4.7.1
8	USER → ME	The MO call is terminated

PROACTIVE COMMAND: REFRESH 2.4.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: UICC

Destination device: ME

File list

Number of files: 3

File: EF IMSI

File: EF PSLOCI

File: EF LOCI

Coding:

BER-TLV:	D0	1E	81	03	01	01	06	82	02	81	82	92
	13	03	3F	00	7F	FF	6F	07	3F	00	7F	FF
	6F	73	3F	00	7F	FF	6F	7E

TERMINAL RESPONSE: REFRESH 2.4.1A

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: ME

Destination device: UICC

Result

General Result: ME currently unable to process command
Additional information on result: ME currently busy on call

Coding:

BER-TLV:	81	03	01	01	06	82	02	82	81	83	02	20
	02

TERMINAL RESPONSE: REFRESH 2.4.1B

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: ME

Destination device: UICC

Result

General Result: ME currently unable to process command
Additional information on result: Screen is busy

Coding:

BER-TLV:	81	03	01	01	06	82	02	82	81	83	02	20
	01

Expected Sequence 2.5 (REFRESH, reject UICC Reset for IMSI Changing procedure during CS call)

Step	Direction	MESSAGE / Action	Comments
1	USER → ME	CS MO Call setup
2	ME → USS	Call established and maintained
3	UICC → ME	PROACTIVE COMMAND PENDING: REFRESH 2.5.1
4	ME → UICC	FETCH
5	UICC → ME	PROACTIVE COMMAND: REFRESH 2.5.1
6	ME → UICC	TERMINAL RESPONSE: REFRESH 2.5.1A Or TERMINAL RESPONSE: REFRESH 2.5.1B	ME rejects REFRESH proactive command
7	UICC → ME	PROACTIVE UICC SESSION ENDED	Note: EF IMSI, EF LOCI and EF PS LOCI are not updated by the UICC, see TS 31.111[15], cl. 6.4.7.1
8	USER → ME	The CS MO call is terminated

PROACTIVE COMMAND: REFRESH 2.5.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: UICC RESET

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

TERMINAL RESPONSE: REFRESH 2.5.1A

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: UICC RESET

Device identities

Source device: ME

Destination device: UICC

Result

General Result: ME currently unable to process command
Additional information on result: ME currently busy on call

Coding:

BER-TLV:	81	03	01	01	04	82	02	82	81	83	02	20
	02

TERMINAL RESPONSE: REFRESH 2.5.1B

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: UICC RESET

Device identities

Source device: ME

Destination device: UICC

Result

General Result: ME currently unable to process command
Additional information on result: Screen is busy

Coding:

BER-TLV:	81	03	01	01	04	82	02	82	81	83	02	20
	01

Expected Sequence 2.6 (REFRESH, UICC Reset for IMSI Changing procedure during active PDP context)

Step	Direction	MESSAGE / Action	Comments
1	USER→ ME	Data Call setup	PDP context will be established
2	ME →USS	PDP context established and maintained
3	UICC→ ME	PROACTIVE COMMAND PENDING: REFRESH	[To inform the ME that IMSI has changed]
4	ME → UICC	FETCH
5	UICC → ME	PROACTIVE COMMAND: REFRESH 2.6.1 or 2.6.2	IF terminal supports PD_ Refresh_Enforcement_Policy use PROACTIVE COMMAND: REFRESH 2.6.2, ELSE 2.6.1.
6	ME→USS	Deactivate PDP context	Mobile will deactivate the PDP context Note 1: this step is performed locally and may not reflect on the interface to the USS. Note 2: this step can happen after step 8.
7	ME→USS	IMSI DETACH INDICATION and/or DETACH REQUEST	Indicates IMSI detach and/or GPRS detach, depending on if the ME is CS and/or PS registered according to its capabilities. Note: this step can happen after step 8
8	ME → UICC	STATUS[P1=’02’]	ME indicates to USIM that the termination procedure is starting
9	ME → UICC	ME performs UICC reset	Both cold and warm resets are allowed
10	UICC	Update EF IMSI, EF LOCI and EF PSLOCI	The content of EF IMSI has been updated to "246813579" and TMSI in EF LOCI and P-TMSI in EF PSLOCI are updated to ‘FF FF FF FF’
11	ME → UICC	ME resets the UICC, perform USIM Initialization, including send STATUS[P1=’01’] and no TERMINAL RESPONSE shall be sent	[ME resets and performs USIM initialization]
12	ME→ USS	LOCATION UPDATING REQUEST and/or ATTACH REQUEST	The ME will register using IMSI "246813579" in CS and/or PS depending on its capabilities
13	USS → ME	LOCATION UPDATING ACCEPT and/or ATTACH ACCEPT
14	ME → USS	TMSI REALLOCATION COMPLETE and/or ATTACH COMPLETE

PROACTIVE COMMAND: REFRESH 2.6.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: UICC RESET

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

PROACTIVE COMMAND: REFRESH 2.6.2

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: UICC RESET

Device identities

Source device: UICC

Destination device: ME

Refresh enforcement policy: Force immediate REFRESH even if the terminal is busy on data call

Coding:

BER-TLV:	D0	0C	81	03	01	01	04	82	02	81	82	3A
	01	02

Expected Sequence 2.7 (REFRESH, 3G Session Reset for IMSI Changing procedure during active PDP context)

Step	Direction	MESSAGE / Action	Comments
1	USER → ME	Data Call setup	PDP context will be established
2	ME → USS	PDP context establishedand maintained
3	UICC→ ME	PROACTIVE COMMAND PENDING: REFRESH	[To inform the ME that IMSI has changed]
4	ME → UICC	FETCH
5	UICC → ME	PROACTIVE COMMAND: REFRESH 2.7.1 or 2.7.2	IF terminal supports PD_ Refresh_Enforcement_Policy use PROACTIVE COMMAND: REFRESH 2.7.2, ELSE 2.7.1.
6	ME→USS	Deactivate PDP context	Mobile will deactivate the PDP context Note: this step can be performed in parallel or after step 8.
7	ME→USS	IMSI DETACH INDICATION and/or DETACH REQUEST	Indicates IMSI detach and/or GPRS detach, depending on if the ME is CS and/or PS registered according to its capabilities Note 1: this step is performed locally and may not reflect on the interface to the USS. Note 2: this step can be performed in parallel or after step 8.
8	ME → UICC	STATUS[P1=’02’]	If A.1/172 is supported, then the ME indicates to USIM that the termination procedure is starting, completes the 3G session termination procedure and resets the application via SELECT by DF name command with the AID. The ME performs the USIM initialization.
9	UICC	Update EF IMSI, EF LOCI and EF PSLOCI	The content of EF IMSI has been updated to "246813579" and TMSI in EF LOCI and P-TMSI in EF PSLOCI are updated to ‘FF FF FF FF’
10	ME → UICC	TERMINAL RESPONSE: REFRESH 2.7.1A Or TERMINAL RESPONSE: REFRESH 2.7.1B	[normal ending]
11	UICC → ME	PROACTIVE UICC SESSION ENDED
12	ME→ USS	LOCATION UPDATING REQUEST and/or ATTACH REQUEST	The ME will register using IMSI "246813579" in CS and/or PS depending on its capabilities
13	USS → ME	LOCATION UPDATING ACCEPT and/or ATTACH ACCEPT
14	ME → USS	TMSI REALLOCATION COMPLETE and/or ATTACH COMPLETE

PROACTIVE COMMAND: REFRESH 2.7.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: UICC

Destination device: ME

File list

Number of files: 3

File: EF IMSI

File: EF PSLOCI

File: EF LOCI

Coding:

BER-TLV:	D0	1E	81	03	01	01	06	82	02	81	82	92
	13	03	3F	00	7F	FF	6F	07	3F	00	7F	FF
	6F	73	3F	00	7F	FF	6F	7E

PROACTIVE COMMAND: REFRESH 2.7.2

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: UICC

Destination device: ME

File list

Number of files: 3

File: EF IMSI

File: EF PSLOCI

File: EF LOCI

Refresh enforcement policy: Force immediate REFRESH even if the terminal is busy on data call

Coding:

BER-TLV:	D0	21	81	03	01	01	06	82	02	81	82	92
	13	03	3F	00	7F	FF	6F	07	3F	00	7F	FF
	6F	73	3F	00	7F	FF	6F	7E	3A	01	02

TERMINAL RESPONSE: REFRESH 2.7.1A

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

TERMINAL RESPONSE: REFRESH 2.7.1B

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: ME

Destination device: UICC

Result

General Result: REFRESH performed with additional EFs read

Coding:

BER-TLV:

27.22.4.7.2.5 Test requirement

The ME shall operate in the manner defined in expected sequences 2.1 to 2.7.

27.22.4.7.3 REFRESH (Steering of roaming)

27.22.4.7.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.7.3.2 Conformance requirement

The ME shall support the REFRESH command as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.7, clause 6.6.13, clause 5.2, clause 8.2, 8.6, clause 8.7 and clause 8.90.

Consequently the Rel-7 or later ME shall support the steering of roaming procedure as defined in:

– TS 23.122 [29] clause 4.4.6.

27.22.4.7.3.3 Test purpose

To verify that the ME performs the Proactive Command – REFRESH in accordance with the Command Qualifier. This shall require the ME to perform:

– the steering of roaming procedure,

– a successfull return of the result of the execution of the command in the TERMINAL RESPONSE command send to the UICC.

27.22.4.7.3.4 Method of test

27.22.4.7.3.4.1 Initial conditions

For sequences 3.1 and 3.2 the ME is connected to the USIM Simulator and connected to the USS/SS.

For sequence 3.3 the ME supporting E-UTRAN/NB-IoT is connected to the USIM Simulator and connected to the E-USS/NB-SS.

For sequences 3.1 and 3.2:

The elementary files are coded as Toolkit default with the following exceptions:

EF_FPLMN

Logically: PLMN1: 254 002 (MCC MNC)

PLMN2: 254 003

PLMN3: 254 004

PLMN4: 234 004

PLMN5: 234 005

PLMN6: 234 006

Coding:	B1	B2	B3	B4	B5	B6	B7	B8	B9	B10	B11	B12
Hex	52	24	00	52	34	00	52	44	00	32	44	00

	B13	B14	B15	B16	B17	B18
	32	54	00	32	64	00

EF_OPLMNwACT

Logically: 1^st PLMN: 254 001 (MCC MNC)

1^st ACT: UTRAN

2^nd PLMN: 254 001

2^nd ACT: GSM

3^rd PLMN: 274 002

3^rd ACT: UTRAN

4^th PLMN: 274 003

4^th ACT: UTRAN

5^th PLMN: 274 004

5^th ACT: UTRAN

6^th PLMN: 274 005

6^th ACT: UTRAN

7^th PLMN: 274 006

7^th ACT: UTRAN

8^th PLMN: 274 007

8^th ACT: UTRAN

Coding:	B01	B02	B03	B04	B05	B06	B07	B08	B09	B10
Hex	52	14	00	80	00	52	14	00	00	80

	B11	B12	B13	B14	B15	B16	B17	B18	B19	B20
	72	24	00	80	00	72	34	00	80	00

	B21	B22	B23	B24	B25	B26	B27	B28	B29	B30
	72	44	00	80	00	72	54	00	80	00

	B31	B32	B33	B34	B35	B36	B37	B38	B39	B40
	72	64	00	80	00	72	74	00	80	00

For sequence 3.3:

The default E-UTRAN UICC, the default E-USS/NB-SS parameters and the following parameters are used:

EF_FPLMN

Logically: PLMN1: 254 002 (MCC MNC)

PLMN2: 254 003

PLMN3: 254 004

PLMN4: 234 004

PLMN5: 234 005

PLMN6: 234 006

Coding:	B1	B2	B3	B4	B5	B6	B7	B8	B9	B10	B11	B12
Hex	52	24	00	52	34	00	52	44	00	32	44	00

	B13	B14	B15	B16	B17	B18
	32	54	00	32	64	00

EF_OPLMNwACT

Logically: 1^st PLMN: 254 001 (MCC MNC)

1^st ACT: E-UTRAN, UTRAN

2^nd PLMN: 254 001

2^nd ACT: GSM

3^rd PLMN: 274 002

3^rd ACT: E-UTRAN

4^th PLMN: 274 003

4^th ACT: E-UTRAN

5^th PLMN: 274 004

5^th ACT: E-UTRAN

6^th PLMN: 274 005

6^th ACT: E-UTRAN

7^th PLMN: 274 006

7^th ACT: E-UTRAN

8^th PLMN: 274 007

8^th ACT: UTRAN

Coding:	B01	B02	B03	B04	B05	B06	B07	B08	B09	B10
Hex	52	14	00	C0	00	52	14	00	00	80

	B11	B12	B13	B14	B15	B16	B17	B18	B19	B20
	72	24	00	40	00	72	34	00	40	00

	B21	B22	B23	B24	B25	B26	B27	B28	B29	B30
	72	44	00	40	00	72	54	00	40	00

	B31	B32	B33	B34	B35	B36	B37	B38	B39	B40
	72	64	00	40	00	72	74	00	80	00

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.7.3.4.2 Procedure

Expected Sequence 3.1 (REFRESH, Steering of roaming, UTRAN)

Step	Direction	MESSAGE / Action	Comments
1	USS	The first UMTS USS transmits on BCCH, with the following network parameters: – Attach/detach: disabled. – LAI (MCC/MNC/LAC): 254/001/0001. – Access control: unrestricted. The second UMTS USS transmits on BCCH, with the following network parameters: – Attach/detach: disabled. – LAI (MCC/MNC/LAC): 254/002/0001. – Access control: unrestricted.
2	ME → USS	The ME registers to the first USS.
3	UICC  ME	PROACTIVE COMMAND PENDING: SET UP EVENT LIST 3.1.1	[Setting up LOCATION STATUS Event]
4	ME  UICC	FETCH
5	UICC  ME	PROACTIVE COMMAND: SET UP EVENT LIST 3.1.1
6a	ME  UICC	TERMINAL RESPONSE: SET UP EVENT LIST 3.1.1
6b	ME  UICC	ENVELOPE: EVENT DOWNLOAD – Location Status 3.1.2	This step applies only if A.1/171
7	UICC → ME	PROACTIVE COMMAND PENDING: REFRESH 3.1.1
8	ME → UICC	FETCH
9	UICC → ME	PROACTIVE COMMAND: REFRESH 3.1.1	Note: Step 11 can occur at any time during execution of steps 10a to 10d
10a	UICC	Void
10b	ME → UICC	Update of EF FPLMN	[Deletion of the entries with PLMN 254/003 and PLMN 254/004]
10c	ME	Update of ME’s internal memory	[Not explicitly verified: Deletion of the FPLMN entries with PLMN 254/003 and PLMN 254/004]
10d	ME → USS	From steps 9 -13: The ME does not register to another USS than the currently selected and shall not send new LOCATION STATUS event to the UICC.
11	ME → UICC	TERMINAL RESPONSE: REFRESH 3.1.1	[normal ending] Note: For a pre-release 11 ME, the UICC simulator does not need to evaluate the response
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13		Wait approx. 180 seconds	[The ME does not register to another USS than the currently selected.]
14	UICC → ME	PROACTIVE COMMAND PENDING: REFRESH 3.1.2
15	ME → UICC	FETCH
16	UICC → ME	PROACTIVE COMMAND: REFRESH 3.1.2	Note: Step 18 can occur at any time during execution of steps 17a to 17c
17a	UICC	Void
17b	ME → UICC	Update of EF FPLMN	[Deletion of the entry with PLMN 254/002]
17c	ME	Update of ME’s internal memory	[Not explicitly verified: Deletion of the FPLMN entry with PLMN 254/002]
18	ME → UICC	TERMINAL RESPONSE: REFRESH 3.1.2	[normal ending]
19	UICC → ME	PROACTIVE UICC SESSION ENDED
20	ME → USS	The ME registers to the second USS.	Note: The ME might have registered to the second USS also before steps 18/19.
21	ME → UICC	ENVELOPE: EVENT DOWNLOAD – Location Status 3.1.1	PLMN MCC/MNC: 254/002, Normal service Note: The ME send the Envelope after registration to the second USS, thus might have sent the Envelope also before steps 18/19.
22	UICC → ME	PROACTIVE COMMAND PENDING: REFRESH 3.1.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: REFRESH 3.1.3	Note: Step 26 can occur at any time during execution of steps 25a to 25c
25a	UICC	Void
25b	UICC	EF FPLMN	[PLMN entries 254/003 and PLMN 254/001 not existent in EF FPLMN]
25c	ME	ME’s internal memory	[Not explicitly verified: PLMN entries 254/003 and PLMN 254/001 not existent in FPLMN list]
26	ME → UICC	TERMINAL RESPONSE: REFRESH 3.1.2	[normal ending]
27	UICC → ME	PROACTIVE UICC SESSION ENDED
28	ME → USS	The ME registers to the first USS.	Note: The ME might have registered to the first USS also before steps 26/27.
29	ME → UICC	ENVELOPE: EVENT DOWNLOAD – Location Status 3.1.2	PLMN MCC/MNC: 254/001 Note: The ME send the Envelope after registration to the first USS, thus might have sent the Envelope also before steps 26/27.
30	UICC  ME	PROACTIVE COMMAND PENDING: SET UP EVENT LIST 3.2.1
31	ME  UICC	FETCH
32	UICC  ME	PROACTIVE COMMAND: SET UP EVENT LIST 3.2.1	[Event LOCATION STATUS download removed]
33	ME  UICC	TERMINAL RESPONSE: SET UP EVENT LIST 3.2.1	The content of the Terminal Response is not part of the evaluation of the test case
34	USER  ME	SWITCH OFF ME

PROACTIVE COMMAND: SET UP EVENT LIST 3.1.1

Same as PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1 in clause 27.22.7.4.1.4.2.

TERMINAL RESPONSE: SET UP EVENT LIST 3.1.1

Same as TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1 in clause 27.22.7.4.1.4.2.

PROACTIVE COMMAND: SET UP EVENT LIST 3.2.1

Same as PROACTIVE COMMAND: SET UP EVENT LIST 1.3.2 in clause 27.22.4.16.1.4.2.

TERMINAL RESPONSE: SET UP EVENT LIST 3.2.1

Same as TERMINAL RESPONSE: SET UP EVENT LIST 1.3.2 in clause 27.22.4.16.1.4.2.

PROACTIVE COMMAND: REFRESH 3.1.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: Steering of roaming

Device identities

Source device: UICC

Destination device: ME

PLMNwACT List

1stPLMN: 254/003

1stACT: UTRAN

2ndPLMN: 254/004

2ndACT: GERAN

Coding:

BER-TLV:	D0	15	81	03	01	01	07	82	02	81	82	72
	0A	52	34	00	80	00	52	44	00	00	80

TERMINAL RESPONSE: REFRESH 3.1.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: Steering of roaming

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

PROACTIVE COMMAND: REFRESH 3.1.2

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: Steering of roaming

Device identities

Source device: UICC

Destination device: ME

PLMNwACT List

1stPLMN: 254/002

1stACT: UTRAN/GERAN

2ndPLMN: 254/001

2ndACT: UTRAN/GERAN

Coding:

BER-TLV:	D0	15	81	03	01	01	07	82	02	81	82	72
	0A	52	24	00	80	80	52	14	00	80	80

TERMINAL RESPONSE: REFRESH 3.1.2

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: Steering of roaming

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

EVENT DOWNLOAD – LOCATION STATUS 3.1.1

Logically:

Event list: Location status

Device identities

Source device: ME

Destination device: UICC

Location status: normal service

Location Information

MCC & MNC the mobile country and network code (254/002)

LAC the location Area Code (0001)

Cell ID Cell Identity Value (0001)

Extended Cell ID RNC-id value, see also Note 1

Coding:

BER-TLV:	D6	15	19	01	03	82	02	82	81	1B	01	00
	13	09	52	24	00	00	01	00	01	Note 1

NOTE 1: The Extended Cell Identity Value is present. The values of the two bytes shall not be verified.

PROACTIVE COMMAND: REFRESH 3.1.3

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: Steering of roaming

Device identities

Source device: UICC

Destination device: ME

PLMNwACT List

1stPLMN: 254/003

1stACT: UTRAN/GERAN

2ndPLMN: 254/001

2ndACT: UTRAN/GERAN

Coding:

BER-TLV:	D0	15	81	03	01	01	07	82	02	81	82	72
	0A	52	34	00	80	80	52	14	00	80	80

EVENT DOWNLOAD – LOCATION STATUS 3.1.2

Logically:

Event list: Location status

Device identities

Source device: ME

Destination device: UICC

Location status: normal service

Location Information

MCC & MNC the mobile country and network code (254/001)

LAC the location Area Code (0001)

Cell ID Cell Identity Value (0001)

Extended Cell ID RNC-id value, see also Note 1

Coding:

BER-TLV:	D6	15	19	01	03	82	02	82	81	1B	01	00
	13	09	52	14	00	00	01	00	01	Note 1

NOTE 1: The Extended Cell Identity Value is present. The values of the two bytes shall not be verified.

Expected Sequence 3.2 (REFRESH, Steering of roaming, InterRAT)

Step	Direction	MESSAGE / Action	Comments
1	USS	The UMTS USS transmits on BCCH, with the following network parameters: – Attach/detach: disabled. – LAI (MCC/MNC/LAC): 254/001/0001. – Access control: unrestricted. The GSM SS transmits on BCCH, with the following network parameters: – Attach/detach: disabled. – LAI (MCC/MNC/LAC): 254/002/0001. – Cell ID: 0001 – Access control: unrestricted.
2	ME → USS	The ME registers to the UMTS USS and achieves updated idle mode.
3	UICC  ME	PROACTIVE COMMAND PENDING: SET UP EVENT LIST 3.1.1	[Setting up LOCATION STATUS Event]
4	ME  UICC	FETCH
5	UICC  ME	PROACTIVE COMMAND: SET UP EVENT LIST 3.1.1
6	ME  UICC	TERMINAL RESPONSE: SET UP EVENT LIST 3.1.1	IF A.1/171 THEN ME sends a ENVELOPE: EVENT DOWNLOAD – Location Status 3.2.2
7	UICC → ME	PROACTIVE COMMAND PENDING: REFRESH 3.2.1
8	ME → UICC	FETCH
9	UICC → ME	PROACTIVE COMMAND: REFRESH 3.2.1	Note: Step 11 can occur at any time during execution of steps 10a to 10c
10a	UICC	Void
10b	ME → UICC	Update of EF FPLMN	[Deletion of the entry with PLMN 254/002]
10c	ME	Update of ME’s internal memory	[Not explicitly verified: Deletion of the FPLMN entry with PLMN 254/002]
11	ME → UICC	TERMINAL RESPONSE: REFRESH 3.1.2	[normal ending]
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13	ME → USS	The ME registers to the GSM SS and is in updated idle mode.	Note: The ME might have registered to the second USS also before steps 11/12.
14	ME → UICC	ENVELOPE: EVENT DOWNLOAD – Location Status 3.2.1	PLMN MCC/MNC: 254/002, Normal service Note: The ME send the Envelope after registration to the GSM SS, thus might have sent the Envelope also before steps 11/12.
15	UICC → ME	PROACTIVE COMMAND PENDING: REFRESH 3.2.2
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: REFRESH 3.2.2	Note: Step 19 can occur at any time during execution of steps 18a to 18c
18a	UICC	Void
18b	UICC	EF FPLMN	[Entries with PLMN 254/002 and PLMN 254/001 not existent in EF FPLMN]
18c	ME	ME’s internal memory	[Not explicitly verified: FPLMN entries with PLMN 254/002 and PLMN 254/001 not existent in FPLMN list]
19	ME → UICC	TERMINAL RESPONSE: REFRESH 3.1.2	[normal ending]
20	UICC → ME	PROACTIVE UICC SESSION ENDED
21	ME → USS	The ME registers to the UMTS USS and is in updated idle mode.	Note: The ME might have registered to the first USS also before steps 19/20.
22	ME → UICC	ENVELOPE: EVENT DOWNLOAD – Location Status 3.2.2	PLMN MCC/MNC: 254/001 Note: The ME send the Envelope after registration to the first USS, thus might have sent the Envelope also before steps 19/20.
23	UICC → ME	PROACTIVE COMMAND PENDING: SET UP EVENT LIST 3.2.1
24	ME → UICC	FETCH
25	UICC → ME	PROACTIVE COMMAND: SET UP EVENT LIST 3.2.1	[Event LOCATION STATUS download removed]
26	ME → UICC	TERMINAL RESPONSE: SET UP EVENT LIST 3.2.1	The content of the Terminal Response is not part of the evaluation of the test case
27	USER → ME	SWITCH OFF ME

PROACTIVE COMMAND: REFRESH 3.2.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: Steering of roaming

Device identities

Source device: UICC

Destination device: ME

PLMNwACT List

1stPLMN: 254/002

1stACT: GERAN

2ndPLMN: 254/001

2ndACT: UTRAN

Coding:

BER-TLV:	D0	15	81	03	01	01	07	82	02	81	82	72
	0A	52	24	00	00	80	52	14	00	80	00

PROACTIVE COMMAND: REFRESH 3.2.2

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: Steering of roaming

Device identities

Source device: UICC

Destination device: ME

PLMNwACT List

1stPLMN: 254/003

1stACT: GERAN

2ndPLMN: 254/001

2ndACT: UTRAN

Coding:

BER-TLV:	D0	15	81	03	01	01	07	82	02	81	82	72
	0A	52	34	00	00	80	52	14	00	80	00

EVENT DOWNLOAD – LOCATION STATUS 3.2.1

Logically:

Event list: Location status

Device identities

Source device: ME

Destination device: UICC

Location status: normal service

Location Information

MCC & MNC the mobile country and network code (254/002)

LAC the location Area Code (0001)

Cell ID Cell Identity Value (0001)

Coding:

BER-TLV:	D6	13	19	01	03	82	02	82	81	1B	01	00
	13	07	52	24	00	00	01	00	01

EVENT DOWNLOAD – LOCATION STATUS 3.1.2

Logically:

Event list: Location status

Device identities

Source device: ME

Destination device: UICC

Location status: normal service

Location Information

MCC & MNC the mobile country and network code (254/001)

LAC the location Area Code (0001)

Cell ID Cell Identity Value (0001)

Extended Cell ID: RNC-id value, see also Note 1

Coding:

BER-TLV:	D6	15	19	01	03	82	02	82	81	1B	01	00
	13	09	52	14	00	00	01	00	01	Note 1

Note 1: The Extended Cell Identity Value is present. The values of the two bytes shall not be verified.

Expected Sequence 3.3 (REFRESH, Steering of roaming, E-UTRAN)

Step	Direction	MESSAGE / Action	Comments
1	E-USS/NB-SS	The first E-USS/NB-SS transmits on BCCH, with the following network parameters: – Attach/detach: disabled. – TAI (MCC/MNC/TAC): 254/001/0001. – Access control: unrestricted. The second E-USS/NB-SS transmits on BCCH, with the following network parameters: – Attach/detach: disabled. – TAI (MCC/MNC/TAC): 254/002/0001. – Access control: unrestricted.
2	ME → E-USS/NB-SS	The ME registers to the first E-USS/NB-SS.
3	UICC  ME	PROACTIVE COMMAND PENDING: SET UP EVENT LIST 3.1.1	[Setting up LOCATION STATUS Event]
4	ME  UICC	FETCH
5	UICC  ME	PROACTIVE COMMAND: SET UP EVENT LIST 3.1.1
6	ME  UICC	TERMINAL RESPONSE: SET UP EVENT LIST 3.1.1	IF A.1/171 THEN ME sends a ENVELOPE: EVENT DOWNLOAD – Location Status 3.3.3
7	UICC → ME	PROACTIVE COMMAND PENDING: REFRESH 3.3.1
8	ME → UICC	FETCH
9	UICC → ME	PROACTIVE COMMAND: REFRESH 3.3.1	Note: Step 11 can occur at any time during execution of steps 10a to 10d
10a	UICC	Void
10b	ME → UICC	Update of EF FPLMN	[Deletion of the entries with PLMN 254/003 and PLMN 254/004]
10c	ME	Update of ME’s internal memory	[Not explicitly verified: Deletion of the FPLMN entries with PLMN 254/003 and PLMN 254/004]
10d	ME → E-USS/NB-SS	From steps 9 -13: The ME does not register to another E-USS/NB-SS than the currently selected and shall not send new LOCATION STATUS event to the UICC.
11	ME → UICC	TERMINAL RESPONSE: REFRESH 3.3.1	[normal ending] Note: For a pre-release 11 ME, the UICC simulator does not need to evaluate the response
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13		Wait approx. 180 seconds	[The ME does not register to another E-USS/NB-SS than the currently selected.]
14	UICC → ME	PROACTIVE COMMAND PENDING: REFRESH 3.3.2
15	ME → UICC	FETCH
16	UICC → ME	PROACTIVE COMMAND: REFRESH 3.3.2	Note: Step 18 can occur at any time during execution of steps 17a to 17c
17a	UICC	Void
17b	ME → UICC	Update of EF FPLMN	[Deletion of the entry with PLMN 254/002]
17c	ME	Update of ME’s internal memory	[Not explicitly verified: Deletion of the FPLMN entry with PLMN 254/002]
18	ME → UICC	TERMINAL RESPONSE: REFRESH 3.3.2	[normal ending]
19	UICC → ME	PROACTIVE UICC SESSION ENDED
20	ME → E-USS/NB-SS	The ME registers to the second E-USS/NB-SS.	Note: The ME might have registered to the second E-USS/NB-SS also before steps 18/19.
21	ME  UICC	ENVELOPE: EVENT DOWNLOAD – Location Status 3.3.2	PLMN MCC/MNC: 254/002 Note: The ME send the Envelope after registration to the second E-USS/NB-SS, thus might have sent the Envelope also before steps 18/19.
22	UICC → ME	PROACTIVE COMMAND PENDING: REFRESH 3.1.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: REFRESH 3.3.3	Note: Step 26 can occur at any time during execution of steps 25a to 25c
25a	UICC	Void
25b	UICC	EF FPLMN	[PLMN entries 254/003 and PLMN 254/001 not existent in EF FPLMN]
25c	ME	ME’s internal memory	[Not explicitly verified: PLMN entries 254/003 and PLMN 254/001 not existent in FPLMN list]
26	ME → UICC	TERMINAL RESPONSE: REFRESH 3.3.2	[normal ending]
27	UICC → ME	PROACTIVE UICC SESSION ENDED
28	ME → E-USS/NB-SS	The ME registers to the first E-USS/NB-SS.	Note: The ME might have registered to the first E-USS/NB-SS also before steps 26/27.
29	ME  UICC	ENVELOPE: EVENT DOWNLOAD – Location Status 3.3.3	PLMN MCC/MNC: 254/001 Note: The ME send the Envelope after registration to the second E-USS/NB-SS, thus might have sent the Envelope also before steps 26/27.
30	UICC → ME	PROACTIVE COMMAND PENDING: SET UP EVENT LIST 3.2.1
31	ME → UICC	FETCH
32	UICC → ME	PROACTIVE COMMAND: SET UP EVENT LIST 3.2.1	[Event LOCATION STATUS download removed]
33	ME → UICC	TERMINAL RESPONSE: SET UP EVENT LIST 3.2.1	The content of the Terminal Response is not part of the evaluation of the test case
34	USER → ME	SWITCH OFF ME

PROACTIVE COMMAND: REFRESH 3.3.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: Steering of roaming

Device identities

Source device: UICC

Destination device: ME

PLMNwACT List

1stPLMN: 254/003

1stACT: E-UTRAN, UTRAN

2ndPLMN: 254/004

2ndACT: GERAN

Coding:

BER-TLV:	D0	15	81	03	01	01	07	82	02	81	82	72
	0A	52	34	00	C0	00	52	44	00	00	80

TERMINAL RESPONSE: REFRESH 3.3.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: Steering of roaming

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

PROACTIVE COMMAND: REFRESH 3.3.2

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: Steering of roaming

Device identities

Source device: UICC

Destination device: ME

PLMNwACT List

1stPLMN: 254/002

1stACT: E-UTRAN/UTRAN/GERAN

2ndPLMN: 254/001

2ndACT: E-UTRAN/UTRAN/GERAN

Coding:

BER-TLV:	D0	15	81	03	01	01	07	82	02	81	82	72
	0A	52	24	00	C0	80	52	14	00	C0	80

TERMINAL RESPONSE: REFRESH 3.3.2

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: Steering of roaming

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

EVENT DOWNLOAD – LOCATION STATUS 3.3.2

Logically:

Event list: Location status

Device identities

Source device: ME

Destination device: UICC

Location status: normal service

Location Information

MCC & MNC the mobile country and network code (254/002)

TAC 0001

E-UTRAN cell id: 0001 (28bits)

Coding:

BER-TLV:	D6	15	19	01	03	82	02	82	81	1B	01	00
	13	09	52	24	00	00	01	00	00	00	1F

PROACTIVE COMMAND: REFRESH 3.3.3

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: Steering of roaming

Device identities

Source device: UICC

Destination device: ME

PLMNwACT List

1stPLMN: 254/003

1stACT: E-UTRAN/UTRAN/GERAN

2ndPLMN: 254/001

2ndACT: E-UTRAN/UTRAN/GERAN

Coding:

BER-TLV:	D0	15	81	03	01	01	07	82	02	81	82	72
	0A	52	34	00	C0	80	52	14	00	C0	80

EVENT DOWNLOAD – LOCATION STATUS 3.3.3

Logically:

Event list: Location status

Device identities

Source device: ME

Destination device: UICC

Location status: normal service

Location Information

MCC & MNC the mobile country and network code (254/001)

TAC 0001

E-UTRAN cell id: 0001 (28bits)

Coding:

BER-TLV:	D6	15	19	01	03	82	02	82	81	1B	01	00
	13	09	52	14	00	00	01	00	00	00	1F

27.22.4.7.3.5 Test requirement

The ME shall operate in the manner defined in expected sequences 3.1 to 3.3.

27.22.4.7.4 REFRESH (AID)

27.22.4.7.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.7.4.2 Conformance requirement

The ME shall support the REFRESH command as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.7, clause 6, clause 6.6.13, clause 5.2, clause 8.6, clause 8.7, clause 8.18 and clause 8.60.

The ME shall support the IMS related requirements as defined and tested in:

– TS 24.229 [38] clause 5.1.1.7 and Annex C.4

– TS 34.229-1 [36] clause 8.15, Annex C.2, C.17 and C.18

The ME shall support the USIM Initialization procedure as defined in:

– TS 31.102 [14] clause 5.1.2 and Annex I.

27.22.4.7.4.3 Test purpose

To verify that the ME performs the Proactive Command – REFRESH in accordance with the Command Qualifier and additionally correctly takes into account the Application Identifier if present in the Refresh command.

– Verification of correct Refresh command execution within the application executed on a any logical channel if the corresponding AID is present in the Refresh command

This may require the ME to perform:

– a USIM or ISIM initialization

– a re-read of the contents and structure of the ISIM on the USIM

– a successful return of the result of the execution of the command in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.7.4.4 Method of test

27.22.4.7.4.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as defined for the E-UTRAN/EPC ISIM-UICC in clause 27.22.2C.

For sequence 4.1 the ME is connected to the E-USS or the USS.

27.22.4.7.4.4.2 Procedure

Expected Sequence 4.1 (REFRESH with AID)

Step	Direction	MESSAGE / Action	Comments
1	USER → ME	The ME is switched on	ME will perform Profile Download, USIM and ISIM initialisation
2	ME → NWS	ME activates the required bearer, discoveres P-CSCF and registers with the values from the ISIM to IMS services	For E-UTRAN: The EPS bearer context activation according to the procedures defined in TS 34.229-1 [36], Annex C.2 and C.18 is performed For UTRAN: A PDP context activation according to the procedures defined in TS 34.229-1 [36], Annex C.2 and C.17 is performed.
3	UICC→ ME	PROACTIVE COMMAND PENDING: REFRESH 4.1.1	To inform the ME that EF_FPLMN shall be re-read.
4	ME → UICC	FETCH
5	UICC → ME	PROACTIVE COMMAND: REFRESH 4.1.1	EF_FPLMN shall be read by the UE, but this might occur even after the Terminal Response. An update of EF_FPLMN by the UICC is not required in this test.
6	ME → UICC	TERMINAL RESPONSE: REFRESH 4.1.1A Or TERMINAL RESPONSE: REFRESH 4.1.1B	[normal ending] [additional EFs read]
7	UICC → ME	PROACTIVE UICC SESSION ENDED
8		Continue with steps 1 – 4 of the "Expected Sequence" of test 8.15 of TS 34.229-1 with the following parameters: REFRESH command: PROACTIVE COMMAND: Refresh 4.2.1 Initial Home Domain name = Updated Home Domain name New IMPI in EF_IMPI= 00101555666@test.3gpp.com New IMPU in record 1 of EF_IMPU= 00101555666@ims.mnc246.mcc081.3gppnetwork.org	The following requirements shall be verified: After step 1 and before step 4 of the "Expected Sequence" of test 8.15 of TS 34.229-1the ME shall have sent TERMINAL RESPONSE: REFRESH 4.2.1A or TERMINAL RESPONSE: REFRESH 4.2.1B The ME shall have fulfilled the test requieremnts defined in TS 34.229, clause 8.15.5

PROACTIVE COMMAND: REFRESH 4.1.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: File Change Notification

Device identities

Source device: UICC

Destination device: ME

File List

File 1: EF FPLMN

Application Identifier

Content: The 3GPP USIM AID used in the test system configuration

Coding:

BER-TLV:	D0	24	81	03	01	01	01	82	02	81	82
	92	07	01	3F	00	7F	FF	6F	7B	2F	10
	A0	00	00	00	87	10	02	xx	xx	xx	xx
	xx	xx	xx	xx	xx

PROACTIVE COMMAND: REFRESH 4.2.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: ISIM Initialization

Device identities

Source device: UICC

Destination device: ME

Application Identifier

Content: The 3GPP ISIM AID used in the test system configuration

Coding:

BER-TLV:	D0	1B	81	03	01	01	03	82	02	81	82
	2F	10	A0	00	00	00	87	10	04	xx	xx
	xx	xx	xx	xx	xx	xx	xx

TERMINAL RESPONSE: REFRESH 4.1.1A/4.2.1A

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: USIM/ISIM Initialization

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

TERMINAL RESPONSE: REFRESH 4.1.1B/ 4.2.1B

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: USIM/ISIM Initialization

Device identities

Source device: ME

Destination device: UICC

Result

General Result: REFRESH performed with additional EFs read

Coding:

BER-TLV:

27.22.4.7.4.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.1.

27.22.4.7.5 REFRESH (IMSI changing procedure, E-UTRAN)

27.22.4.7.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.7.5.2 Conformance requirement

The ME shall support the REFRESH command as defined in:

TS 31.111 [15] clause 6.1, clause 6.4.7, clause 6.4.7.1, clause 6.6.13, clause 5.2, clause 8.6, clause 8.7 and clause 8.18.

Additionally, the ME shall support the USIM Initialization and USIM application closure procedure as defined in:

TS 31.102 [14] clause 5.1.2 and Annex I.

27.22.4.7.5.3 Test purpose

To verify that the ME performs the Proactive Command – REFRESH in accordance with the Command Qualifier and the IMSI changing procedure. This may require the ME to perform:

– the USIM initialization

– a re-read of the contents and structure of the IMSI on the USIM

– a restart of the card session

– a successful return of the result of the execution of the command in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.7.5.4 Method of test

27.22.4.7.5.4.1 Initial conditions

The ME is connected to the USIM Simulator and connected to the E-USS/NB-SS, registered and has the default PDN connection established.

The E-UTRAN/NB-IoT parameters of the E-USS/NB-SS are:

– Mobile Country Code (MCC) = 246;

– Mobile Network Code (MNC) = 81;

– Tracking Area Code (TAC) = 0001;

The elementary files are coded as the default E-UTRAN/EPC UICC,

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.7.5.4.2 Procedure

Expected Sequence 5.1 (REFRESH, UICC Reset for IMSI Changing procedure, E-UTRAN)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: REFRESH 5.1.1	[To inform the ME that IMSI has changed]
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: REFRESH 5.1.1 or 5.1.2	IF terminal supports PD_Refresh_Enforcement_Policy use PROACTIVE COMMAND: REFRESH 5.1.2, ELSE 5.1.1.
4	ME → E-USS/ NB-SS	Deactivate PDN Connection	ME will deactivate the PDN Connection Note 1: this step is performed locally and may not reflect on the interface to the E-USS/ NB‑SS Note 2: if the ME supports pc_NB this step is performed only in case pc_AttachWithPDN is supported by the ME.
5	ME → E-USS/ NB-SS	DETACH REQUEST	Indicates EPS detach or combined EPS/IMSI detach. Note: this step can be performed in parallel or after step 6.
6	ME → UICC	STATUS[P1=’02’]	ME indicates to USIM that the termination procedure is starting
7	ME → UICC	ME performs UICC reset	Both, cold and warm resets are allowed
8	UICC	Update EF_IMSI and EF_EPSLOCI	The content of EF_IMSI has been changed to "246813579" and the GUTI in EF_EPSLOCI is updated to ‘FF FF FF FF FF FF FF FF FF FF FF FF’
9	ME → UICC	ME performs USIM Initialization, including send STATUS[P1=’01’] and no TERMINAL RESPONSE shall be sent	[ME resets and performs USIM initialization]
10	ME → E-USS/ NB-SS	ATTACH REQUEST	The ME will register using IMSI "246813579".
11	E-USS/ NB‑SS → ME	ATTACH ACCEPT
12	ME → E-USS/ NB-SS	ATTACH COMPLETE

PROACTIVE COMMAND: REFRESH 5.1.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: UICC RESET

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

PROACTIVE COMMAND: REFRESH 5.1.2

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: UICC RESET

Device identities

Source device: UICC

Destination device: ME

Refresh enforcement policy: Force immediate REFRESH even if the terminal is busy on data call

Coding:

BER-TLV:	D0	0C	81	03	01	01	04	82	02	81	82	3A
	01	02

Expected Sequence 5.2 (REFRESH, 3G Session Reset for IMSI Changing procedure, E-UTRAN)

Step	Direction	MESSAGE / Action	Comments
1	UICC→ ME	PROACTIVE COMMAND PENDING: REFRESH 5.2.1	[To inform the ME that IMSI has changed]
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: REFRESH 5.2.1 or 5.2.2	IF terminal supports PD_ Refresh_Enforcement_Policy use PROACTIVE COMMAND: REFRESH 5.2.2, ELSE 5.2.1.
4	ME→E-USS/NB-SS	Deactivate PDN Connection	ME will deactivate the PDN Connection Note 1: this step is performed locally and may not reflect on the interface to the E-USS/NB-SS Note 2: if the ME supports pc_NB this step is performed only in case pc_AttachWithPDN is supported by the ME. Note 3: this step can be performed in parallel or after step 6.
5	ME→E-USS/NB-SS	DETACH REQUEST	Note: this step can be performed in parallel or after step 6.
6	ME → UICC	STATUS[P1=’02’]	If A.1/172 is supported, then the ME indicates to USIM that the termination procedure is starting, completes the 3G session termination procedure and resets the application via SELECT by DF name command with the AID. The ME performs the USIM initialization.
7	UICC	Update EF IMSI and EF EPSLOCI	The content of EF IMSI has been updated to "246813579" and GUTI in EF EPSLOCI is updated to ‘FF FF FF FF FF FF FF FF FF FF FF FF’
8	ME → UICC	TERMINAL RESPONSE: REFRESH 5.2.1A Or TERMINAL RESPONSE: REFRESH 5.2.1B	[normal ending]
9	UICC → ME	PROACTIVE UICC SESSION ENDED
10	ME→ E-USS/NB-SS	ATTACH REQUEST	The ME will register using IMSI "246813579" in PS.
11	E-USS/NB-SS → ME	ATTACH ACCEPT
12	ME → E-USS/NB-SS	ATTACH COMPLETE

PROACTIVE COMMAND: REFRESH 5.2.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: UICC

Destination device: ME

File list

Number of files: 2

File: EF IMSI

File: EF EPSLOCI

Coding:

BER-TLV:	D0	18	81	03	01	01	06	82	02	81	82	92
	0D	02	3F	00	7F	FF	6F	07	3F	00	7F	FF
	6F	E3

PROACTIVE COMMAND: REFRESH 5.2.2

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: UICC

Destination device: ME

File list

Number of files: 2

File: EF IMSI

File: EF EPSLOCI

Refresh enforcement policy: Force immediate REFRESH even if the terminal is busy on data call

Coding:

BER-TLV:	D0	1B	81	03	01	01	06	82	02	81	82	92
	0D	02	3F	00	7F	FF	6F	07	3F	00	7F	FF
	6F	E3	3A	01	02

TERMINAL RESPONSE: REFRESH 5.2.1A

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

TERMINAL RESPONSE: REFRESH 5.2.1B

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: ME

Destination device: UICC

Result

General Result: REFRESH performed with additional EFs read

Coding:

BER-TLV:

27.22.4.7.5.5 Test requirement

The ME shall operate in the manner defined in expected sequences 5.1 to 5.2.

27.22.4.7.6 REFRESH (IMSI changing procedure, NG-RAN)

27.22.4.7.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.7.6.2 Conformance requirement

The ME shall support the REFRESH command as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.7, clause 6.4.7.1, clause 6, clause 6.6.13, clause 5.2, clause 8.6, clause 8.7 and clause 8.18.

Additionally, the ME shall support the USIM Initialization and USIM application closure procedure as defined in:

– TS 31.102 [14] clause 5.1.2, clause 5.1.3 and Annex I.

27.22.4.7.6.3 Test purpose

To verify that the ME performs the Proactive Command – REFRESH in accordance with the Command Qualifier and the IMSI changing procedure. This may require the ME to perform:

– the USIM initialization

– a re-read of the contents and structure of the IMSI on the USIM

– a restart of the card session

– a successful return of the result of the execution of the command in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.7.6.4 Method of test

27.22.4.7.6.4.1 Initial conditions

The ME is connected to the USIM Simulator and connected to the NG-SS.

The NG-RAN parameters of the NG-SS are:

– Mobile Country Code (MCC) = 001;

– Mobile Network Code (MNC) = 01;

– Tracking Area Code (TAC) = 000001;

The default NG-RAN UICC is used.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.7.6.4.2 Procedure

Expected Sequence 6.1 (REFRESH, UICC Reset for IMSI Changing procedure, NG-RAN)

Step	Direction	MESSAGE / Action	Comments
1	ME → NG-SS	ME successfully REGISTER with NG-RAN cell.
2	UICC → ME	PROACTIVE COMMAND PENDING: REFRESH 6.1.1 or REFRESH 6.1.2	[To inform the ME that IMSI has changed]
3	ME → UICC	FETCH
4	UICC → ME	PROACTIVE COMMAND: REFRESH 6.1.1 or REFRESH 6.1.2	IF terminal supports PD_Refresh_Enforcement_Policy use PROACTIVE COMMAND: REFRESH 6.1.2 ELSE REFRESH 6.1.1.
5	ME→NG-SS	Deregistration Request
6	ME → UICC	STATUS[P1=’02’]	ME indicates to USIM that the termination procedure is starting
7	ME → UICC	ME performs UICC reset.	Both cold and warm resets are allowed
8	UICC	Update EF_IMSI and EF_5GS3GPPLOCI.	The content of EF_IMSI has been changed to "246813579" and the 5G-GUTI in EF_5GS3GPPLOCI is updated to ‘FF FF FF FF FF FF FF FF FF FF FF FF FF’.
9	ME→UICC	ME performs USIM Initialization, including send STATUS[P1=’01’] and no TERMINAL RESPONSE shall be sent.	[ME resets and performs USIM initialization]
10	ME→NG-SS	Registration Request	The ME will register using IMSI "246813579" in NG-RAN.
11	NG-SS→ME	Registration Accept
12	ME→NG-SS	Registration Complete

PROACTIVE COMMAND: REFRESH 6.1.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: UICC RESET

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

PROACTIVE COMMAND: REFRESH 6.1.2

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: UICC RESET

Device identities

Source device: UICC

Destination device: ME

Refresh enforcement policy: Force immediate REFRESH even if the terminal is busy on data call

Coding:

BER-TLV:	D0	0C	81	03	01	01	04	82	02	81	82	3A
	01	02

Expected Sequence 6.2 (REFRESH, 3G Session Reset for IMSI Changing procedure, NG-RAN)

Step	Direction	MESSAGE / Action	Comments
1	ME → NG-SS	ME successfully REGISTER with NG-RAN cell.
2	UICC→ ME	PROACTIVE COMMAND PENDING: REFRESH 6.2.1 or REFRESH 6.2.2	[To inform the ME that IMSI has changed]
3	ME → UICC	FETCH
4	UICC → ME	PROACTIVE COMMAND: REFRESH 6.2.1 or REFRESH 6.2.2	IF terminal supports PD_Refresh_Enforcement_Policy use PROACTIVE COMMAND:REFRESH 6.2.2 ELSE REFRESH 6.2.1.
5	ME→NG-SS	Deregistration Request
6	ME → UICC	STATUS[P1=’02’]	If A.1/172 is supported, then the ME indicates to USIM that the termination procedure is starting, completes the 3G session termination procedure and resets the application via SELECT by DF name command with the AID. The ME performs the USIM initialization.
7	UICC	Update EF_IMSI and EF_5GS3GPPLOCI	The content of EF_IMSI has been updated to "246813579" and 5G-GUTI in EF_5GS3GPPLOCI is updated to ‘FF FF FF FF FF FF FF FF FF FF FF FF FF’
8	ME → UICC	TERMINAL RESPONSE: REFRESH 6.2.1A or TERMINAL RESPONSE: REFRESH 6.2.1B	[normal ending]
9	UICC → ME	PROACTIVE UICC SESSION ENDED
10	ME→NG-SS	Registration Request	The ME will register using IMSI "246813579" in NG-RAN.
11	NG-SS→ME	Registration Accept
12	ME→NG-SS	Registration Complete

PROACTIVE COMMAND: REFRESH 6.2.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: UICC

Destination device: ME

File list

Number of files: 2

File: EF IMSI

File: EF 5GS3GPPLOCI

Coding:

BER-TLV:	D0	1A	81	03	01	01	06	82	02	81	82	92
	0F	02	3F	00	7F	FF	6F	07	3F	00	7F	FF
	5F	C0	4F	01

PROACTIVE COMMAND: REFRESH 6.2.2

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: UICC

Destination device: ME

File list

Number of files: 2

File: EF IMSI

File: EF 5GS3GPPLOCI

Refresh enforcement policy: Force immediate REFRESH even if the terminal is busy on data call

Coding:

BER-TLV:	D0	1D	81	03	01	01	06	82	02	81	82	92
	0F	02	3F	00	7F	FF	6F	07	3F	00	7F	FF
	5F	C0	4F	01	3A	01	02

TERMINAL RESPONSE: REFRESH 6.2.1A

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

TERMINAL RESPONSE: REFRESH 6.2.1B

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: ME

Destination device: UICC

Result

General Result: REFRESH performed with additional EFs read

Coding:

BER-TLV:

27.22.4.7.6.5 Test requirement

The ME shall operate in the manner defined in expected sequences 6.1 to 6.2.

27.22.4.7.7 REFRESH (SUPI_NAI changing procedure, NG-RAN)

27.22.4.7.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.7.7.2 Conformance requirement

The ME shall support the REFRESH command as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.7, clause 6.4.7.1, clause 6, clause 6.6.13, clause 5.2, clause 8.6, clause 8.7 and clause 8.18.

Additionally the ME shall support the USIM Initialization and USIM application closure procedure as defined in:

– TS 31.102 [14] clause 5.1.1.2, clause 5.1.3 and Annex I.

27.22.4.7.7.3 Test purpose

To verify that the ME performs the Proactive Command – REFRESH in accordance with the Command Qualifier and the SUPI_NAI changing procedure. This may require the ME to perform:

– the USIM initialization

– a re-read of the contents and structure of the SUPI_NAI on the USIM

– a restart of the card session

– a successful return of the result of the execution of the command in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.7.7.4 Method of test

27.22.4.7.7.4.1 Initial conditions

The ME is connected to the USIM Simulator and connected to the NG-SS.

The NG-RAN parameters of the system simulator are:

– Mobile Country Code (MCC) = 001;

– Mobile Network Code (MNC) = 01;

– Tracking Area Code (TAC) = 000001;

The elementary files are coded as the default NG-RAN UICC with the following exceptions:

EF_UST (USIM Service Table)

Logically:

User controlled PLMN selector available

Fixed dialling numbers available

The GSM Access available

The Group Identifier level 1 and level 2 not available

Service n 33 (Packed Switched Domain) shall be set to ‘1’

Enabled Services Table available

EPS Mobility Management Information available

Allowed CSG Lists and corresponding indications

5GS Mobility Management Information available

5G Security Parameters available

Subscription identifier privacy support available

SUCI calculation by the USIM not available

Support for SUPI of type NSI or GLI or GCI available

Byte:

Binary:

xxxx xx1x

xxxx xxxx

xxxx 1×00

xxxx x1xx

xxxx xx11

xxxx xxxx

B10

B11

B16

B17

xxxx xxxx

xx11 xxxx

…..

xxx0 111x

xxxxxx1x

The coding of EF_UST shall conform with the capabilities of the USIM used.

EF_{SUPI_NAI} (SUPI as Network Access Identifier)

Logically:

Network Access Identifier TLV data object: 80 14 75 73 65 72 69 64 31 38 40 65 78 61 6D 70 6C 65 2E 63 6F 6D

Coding:	B1	B2	B3	B4	B5	B6	B7	B8
Hex	80	14	75	73	65	72	69	64
	B9	B10	B11	B12	B13	B14	B15	B16
	31	38	40	65	78	61	6D	70
	B17	B18	B19	B20	B21	B22
	6C	65	2E	63	6F	6D

EF_IMSI (IMSI)

This file shall not be available.

EF_AD (Administrative Data)

Logically: Type approval operations

OFM to be deactivated by the Terminal

Length of MNC in the IMSI: 0

Coding:	B1	B2	B3	B4
Hex	80	00	00	00

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.7.7.4.2 Procedure

Expected Sequence 7.1 (REFRESH, UICC Reset for SUPI_NAI Changing procedure, NG-RAN)

Step	Direction	MESSAGE / Action	Comments
1	ME → NG-SS	ME successfully REGISTER with NG-RAN cell.	The ME registers using SUPI_NAI "userid18@example.com" in NG-RAN
2	UICC	Update EF SUPI_NAI and EF 5GSN3GPPLOCI.	The content of EF SUPI_NAI has been changed to "userid19@example.com" and the 5G-GUTI in EF 5GSN3GPPLOCI is updated to ‘FF FF FF FF FF FF FF FF FF FF FF FF FF’.
3	UICC → ME	PROACTIVE COMMAND PENDING: REFRESH 7.1.1	[To inform the ME that SUPI_NAI has changed]
4	ME → UICC	FETCH
5	UICC → ME	PROACTIVE COMMAND: REFRESH 7.1.1 or 7.1.2	IF terminal supports PD_ Refresh_Enforcement_Policy use PROACTIVE COMMAND: REFRESH 7.1.2, ELSE 7.1.1.
6	ME→NG-SS	Deregistration Request
7	ME → UICC	ME performs UICC reset.	Both cold and warm resets are allowed
8	ME→NG-SS	Registration Request	The ME will register using SUPI_NAI "userid19@example.com" in NG-RAN.
9	NG-SS→ME	Registration Accept
10	ME→NG-SS	Registration Complete

PROACTIVE COMMAND: REFRESH 7.1.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: UICC RESET

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

PROACTIVE COMMAND: REFRESH 7.1.2

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: UICC RESET

Device identities

Source device: UICC

Destination device: ME

Refresh enforcement policy: Force immediate REFRESH even if the terminal is busy on data call

Coding:

BER-TLV:	D0	0C	81	03	01	01	04	82	02	81	82	3A
	01	02

Expected Sequence 7.2 (REFRESH, 3G Session Reset for SUPI_NAI Changing procedure, NG-RAN)

Step	Direction	MESSAGE / Action	Comments
1	ME → NG-SS	ME successfully REGISTER with NG-RAN cell.	The ME registers using SUPI_NAI "userid18@example.com" in NG-RAN
2	UICC	Update EF SUPI_NAI and EF 5GSN3GPPLOCI.	The content of EF SUPI_NAI has been changed to "userid19@example.com" and the 5G-GUTI in EF 5GSN3GPPLOCI is updated to ‘FF FF FF FF FF FF FF FF FF FF FF FF FF’.
3	UICC→ ME	PROACTIVE COMMAND PENDING: REFRESH 7.2.1	[To inform the ME that SUPI_NAI has changed]
4	ME → UICC	FETCH
5	UICC → ME	PROACTIVE COMMAND: REFRESH 7.2.1 or 7.2.2	IF terminal supports PD_ Refresh_Enforcement_Policy use PROACTIVE COMMAND: REFRESH 7.2.2, ELSE 7.2.1.
6	ME→NG-SS	Deregistration Request
7	ME → UICC	STATUS[P1=’02’]	If A.1/172 is supported, then the ME indicates to USIM that the termination procedure is starting, completes the 3G session termination procedure and resets the application via SELECT by DF name command with the AID. The ME performs the USIM initialization.
8	ME → UICC	TERMINAL RESPONSE: REFRESH 7.2.1A or TERMINAL RESPONSE: REFRESH 7.2.1B	[normal ending]
9	UICC → ME	PROACTIVE UICC SESSION ENDED
10	ME→NG-SS	Registration Request	The ME will register using SUPI_NAI "userid19@example.com" in NG-RAN.
11	NG-SS→ME	Registration Accept
12	ME→NG-SS	Registration Complete

PROACTIVE COMMAND: REFRESH 7.2.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: UICC

Destination device: ME

File list

Number of files: 2

File: EF SUPI_NAI

File: EF 5GSN3GPPLOCI

Coding:

BER-TLV:	D0	1C	81	03	01	01	06	82	02	81	82	92
	11	02	3F	00	7F	FF	5F	C0	4F	09	3F	00
	7F	FF	5F	C0	4F	02

PROACTIVE COMMAND: REFRESH 7.2.2

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: UICC

Destination device: ME

File list

Number of files: 2

File: EF SUPI_NAI

File: EF 5GSN3GPPLOCI

Refresh enforcement policy: Force immediate REFRESH even if the terminal is busy on data call

Coding:

BER-TLV:	D0	1F	81	03	01	01	06	82	02	81	82	92
	11	02	3F	00	7F	FF	5F	C0	4F	09	3F	00
	7F	FF	5F	C0	4F	02	3A	01	02

TERMINAL RESPONSE: REFRESH 7.2.1A

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

TERMINAL RESPONSE: REFRESH 7.2.1B

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: 3G Session Reset

Device identities

Source device: ME

Destination device: UICC

Result

General Result: REFRESH performed with additional EFs read

Coding:

BER-TLV:

27.22.4.7.7.5 Test requirement

The ME shall operate in the manner defined in expected sequences 7.1 to 7.2.

27.22.4.8 SET UP MENU and ENVELOPE MENU SELECTION

27.22.4.8.1 SET UP MENU (normal) and ENVELOPE MENU SELECTION

27.22.4.8.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.8.1.2 Conformance requirement

The ME shall support the SET UP MENU command as defined in:

– TS 31.111 [15] clause 5, clause 6.4.8, clause 6.6.7, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.2, clause 8.9 and clause 9.4.

The ME shall support MENU SELECTION as defined in:

– TS 31.111 [15] clause 4.4, clause 5.2, clause 6.4.8, clause 6.9, clause 7.2, clause 8.7 and clause 8.10.

27.22.4.8.1.3 Test purpose

To verify that the ME correctly integrates the menu items contained in the SET UP MENU proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

To verify that the ME replaces the current list of menu items with the list of menu items contained in the SET UP MENU command.

To verify that the ME removes the current list of menu items following receipt of a SET UP MENU command with no items.

To verify that the ME correctly passes the identifier of the selected menu item to the UICC using the ENVELOPE (MENU SELECTION) command.

To verify that when the help is available for the command and the user gas indicated the need to get help information on one of the items, the ME informs properly the UICC about an HELP REQUEST, using the MENU SELECTION mechanism.

27.22.4.8.1.4 Method of test

27.22.4.8.1.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.8.1.4.2 Procedure

Expected Sequence 1.1 (SET UP MENU and MENU SELECTION, without Help Request, Replace and Remove a Toolkit Menu)

See ETSI TS 102 384 [26] in clause 27.22.4.8.1.4.2, Expected Sequence 1.1.

Expected Sequence 1.2 (SET UP MENU, Large Menu with many items or with large items or with Large Alpha Identifier)

See ETSI TS 102 384 [26] in clause 27.22.4.8.1.4.2, Expected Sequence 1.2.

The following table details the test requirements with relation to the tested features:

	Proactive UICC Command Facilities
Proactive UICC Command Number	Alpha Identifier Length	Number of items	Maximum length of item
1.1.1	12	4	6
1.1.2	12	2	3
1.1.3	10	0	–
1.2.1	10	30	8
1.2.2	10	7	37
1.2.3	235	1	1

27.22.4.8.1.5 Test requirement

The ME shall operate in the manner defined in expected sequence 1.1 and in expected sequence 1.2.

27.22.4.8.2 SET UP MENU (help request support) and ENVELOPE MENU SELECTION

27.22.4.8.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.8.2.2 Conformance requirement

Requirements are the same as in clause 27.22.4.8.1.1, with an additional one:

– TS 31.111 [15] clause 8.21.

27.22.4.8.2.3 Test purpose

To verify that the ME correctly integrates the menu items contained in the SET UP MENU proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

To verify that when the help is available for the command and the user has indicated the need to get help information on one of the items, the ME informs properly the UICC about an HELP REQUEST, using the MENU SELECTION mechanism.

To verify that the ME correctly passes the identifier of the selected menu item to the UICC using the ENVELOPE (MENU SELECTION) command.

27.22.4.8.2.4 Method of test

27.22.4.8.2.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.8.2.4.2 Procedure

Expected Sequence 2.1 (SET UP MENU and MENU SELECTION, with Help Request, Replace and Remove a Toolkit Menu)

See ETSI TS 102 384 [26] in clause 27.22.4.8.2.4.2, Expected Sequence 2.1.

27.22.4.8.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 2.1.

27.22.4.8.3 SET UP MENU (next action support) and ENVELOPE MENU SELECTION

27.22.4.8.3.1 Definition and applicability

See clause 3.2.2.

If the UICC provides an Items Next Action Indicator data object, the comprehension required flag shall be set to ‘0’.

27.22.4.8.3.2 Conformance requirement

Requirements are the same as in clause 27.22.4.8.1.1, with an additional one:

– TS 31.111 [15] clause 8.24.

27.22.4.8.3.3 Test purpose

To verify that the ME correctly integrates the menu items contained in the SET UP MENU proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

To verify that the next action indicator is supported.

To verify that the ME correctly passes the identifier of the selected menu item to the UICC using the ENVELOPE (MENU SELECTION) command.

27.22.4.8.3.4 Method of test

27.22.4.8.3.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.8.3.4.2 Procedure

Expected Sequence 3.1 (SET UP MENU, next action indicator "Send SM", "Set Up Call", "Launch Browser", "Provide Local Information", successful)

See ETSI TS 102 384 [26] in clause 27.22.4.8.3.4.2, Expected Sequence 3.1.

27.22.4.8.3.5 Test requirement

The ME shall operate in the manner defined in expected sequence 3.1.

27.22.4.8.4 SET UP MENU (display of icons) and ENVELOPE MENU SELECTION

27.22.4.8.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.8.4.2 Conformance requirement

Requirements are the same as in clause 27.22.4.8.1.1, with an additional one:

– 3GPP 31.111 [15] clause 6.5.4, 8.31 and 8.32.

27.22.4.8.4.3 Test purpose

To verify that the ME correctly integrates the menu items contained in the SET UP MENU proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

To verify that icons are displayed with the command Set Up Menu in the Alpha Identifier and Items Data Objects. To verify that the ME correctly passes the identifier of the selected menu item to the UICC using the ENVELOPE (MENU SELECTION) command.

27.22.4.8.4.4 Method of test

27.22.4.8.4.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.8.4.4.2 Procedure

Expected Sequence 4.1A (SET UP MENU, BASIC ICON NOT SELF EXPLANATORY in ALPHA ID and ITEMS DATA OBJECTS, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.8.4.4.2, Expected Sequence 4.1A.

Expected Sequence 4.1B (SET UP MENU, BASIC ICON NOT SELF EXPLANATORY in ALPHA ID and ITEMS DATA OBJECTS, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.8.4.4.2, Expected Sequence 4.1B.

Expected Sequence 4.2A (SET UP MENU, BASIC ICON SELF EXPLANATORY in ALPHA ID and ITEMS DATA OBJECTS, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.8.4.4.2, Expected Sequence 4.2A.

Expected Sequence 4.2B (SET UP MENU, BASIC ICON SELF EXPLANATORY in ALPHA ID and ITEMS DATA OBJECTS, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.8.4.4.2, Expected Sequence 4.2B.

27.22.4.8.4.5 Test requirement

The ME shall operate in the manner defined in expected sequences 4.1A to 4.2B.

27.22.4.8.5 SET UP MENU (soft keys support) and ENVELOPE MENU SELECTION

27.22.4.8.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.8.5.2 Conformance requirement

Requirements are the same as in clause 27.22.4.8.1.1.

27.22.4.8.5.3 Test purpose

To verify that the ME correctly integrates the menu items contained in the SET UP MENU proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

To verify that if soft key preferred is indicated in the command details and soft key for SET UP MENU is supported by the ME and the number of icon items does not exceed the number of soft keys available, then the ME displays those icons as soft key.

To verify that the ME correctly passes the identifier of the selected menu item to the UICC using the ENVELOPE (MENU SELECTION) command.

27.22.4.8.5.4 Method of test

27.22.4.8.5.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.8.5.4.2 Procedure

Expected Sequence 5.1 (SET UP MENU, SOFT KEY PREFERRED, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.8.5.4.2, Expected Sequence 5.1.

27.22.4.8.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 5.1.

27.22.4.8.6 SET UP MENU (support of Text Attribute) and ENVELOPE MENU SELECTION

27.22.4.8.6.1 SET UP MENU (support of Text Attribute – Left Alignment) and ENVELOPE MENU SELECTION

27.22.4.8.6.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.8.6.1.2 Conformance requirement

Requirements are the same as in clause 27.22.4.8.1.1, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.8.6.1.3 Test purpose

To verify that the ME correctly integrates the menu items contained in the SET UP MENU proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

To verify that text is displayed according to the left alignment text attribute configuration within the command Set Up Menu and the ME correctly passes the identifier of the selected menu item to the UICC using the ENVELOPE (MENU SELECTION) command.

27.22.4.8.6.1.4 Method of test

27.22.4.8.6.1.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.8.6.1.4.2 Procedure

Expected Sequence 6.1 (SET UP MENU, Text Attribute – Left Alignment, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.8.6.1.4.2, Expected Sequence 6.1.

27.22.4.8.6.1.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.1.

27.22.4.8.6.2 SET UP MENU (support of Text Attribute – Center Alignment) and ENVELOPE MENU SELECTION

27.22.4.8.6.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.8.6.2.2 Conformance requirement

Requirements are the same as in clause 27.22.4.8.1.1, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.8.6.2.3 Test purpose

To verify that the ME correctly integrates the menu items contained in the SET UP MENU proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

To verify that text is displayed according to the center alignment text attribute configuration within the command Set Up Menu and the ME correctly passes the identifier of the selected menu item to the UICC using the ENVELOPE (MENU SELECTION) command.

27.22.4.8.6.2.4 Method of test

27.22.4.8.6.2.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.8.6.2.4.2 Procedure

Expected Sequence 6.2 (SET UP MENU, Text Attribute – Center Alignment, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.8.6.2.4.2, Expected Sequence 6.2.

27.22.4.8.6.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.2.

27.22.4.8.6.3 SET UP MENU (support of Text Attribute – Right Alignment) and ENVELOPE MENU SELECTION

27.22.4.8.6.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.8.6.3.2 Conformance requirement

Requirements are the same as in clause 27.22.4.8.1.1, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.8.6.3.3 Test purpose

To verify that the ME correctly integrates the menu items contained in the SET UP MENU proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

To verify that text is displayed according to the right alignment text attribute configuration within the command Set Up Menu and the ME correctly passes the identifier of the selected menu item to the UICC using the ENVELOPE (MENU SELECTION) command.

27.22.4.8.6.3.4 Method of test

27.22.4.8.6.3.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.8.6.3.4.2 Procedure

Expected Sequence 6.3 (SET UP MENU, Text Attribute – Right Alignment, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.8.6.3.4.2, Expected Sequence 6.3.

27.22.4.8.6.3.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.3.

27.22.4.8.6.4 SET UP MENU (support of Text Attribute – Large Font Size) and ENVELOPE MENU SELECTION

27.22.4.8.6.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.8.6.4.2 Conformance requirement

Requirements are the same as in clause 27.22.4.8.1.1, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.8.6.4.3 Test purpose

To verify that the ME correctly integrates the menu items contained in the SET UP MENU proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

To verify that text is displayed according to the large font size text attribute configuration within the command Set Up Menu and the ME correctly passes the identifier of the selected menu item to the UICC using the ENVELOPE (MENU SELECTION) command.

27.22.4.8.6.4.4 Method of test

27.22.4.8.6.4.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.8.6.4.4.2 Procedure

Expected Sequence 6.4 (SET UP MENU, Text Attribute – Large Font Size, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.8.6.4.4.2, Expected Sequence 6.4.

27.22.4.8.6.4.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.4.

27.22.4.8.6.5 SET UP MENU (support of Text Attribute – Small Font Size) and ENVELOPE MENU SELECTION

27.22.4.8.6.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.8.6.5.2 Conformance requirement

Requirements are the same as in clause 27.22.4.8.1.1, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.8.6.5.3 Test purpose

To verify that the ME correctly integrates the menu items contained in the SET UP MENU proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

To verify that text is displayed according to the with small font size text attribute configuration within the command Set Up Menu and the ME correctly passes the identifier of the selected menu item to the UICC using the ENVELOPE (MENU SELECTION) command.

27.22.4.8.6.5.4 Method of test

27.22.4.8.6.5.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.8.6.5.4.2 Procedure

Expected Sequence 6.5 (SET UP MENU, Text Attribute – Small Font Size, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.8.6.5.4.2, Expected Sequence 6.5.

27.22.4.8.6.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.5.

27.22.4.8.6.6 SET UP MENU (support of Text Attribute – Bold On) and ENVELOPE MENU SELECTION

27.22.4.8.6.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.8.6.6.2 Conformance requirement

Requirements are the same as in clause 27.22.4.8.1.1, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.8.6.6.3 Test purpose

To verify that the ME correctly integrates the menu items contained in the SET UP MENU proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

To verify that text is displayed according to the text attribute configuration within the command Set Up Menu and the ME correctly passes the identifier of the selected menu item to the UICC using the ENVELOPE (MENU SELECTION) command.

27.22.4.8.6.6.4 Method of test

27.22.4.8.6.6.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.8.6.6.4.2 Procedure

Expected Sequence 6.6 (SET UP MENU, Text Attribute – Bold On, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.8.6.6.4.2, Expected Sequence 6.6.

27.22.4.8.6.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.6.

27.22.4.8.6.7 SET UP MENU (support of Text Attribute – Italic On) and ENVELOPE MENU SELECTION

27.22.4.8.6.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.8.6.7.2 Conformance requirement

Requirements are the same as in clause 27.22.4.8.1.1, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.8.6.7.3 Test purpose

To verify that the ME correctly integrates the menu items contained in the SET UP MENU proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.8.6.7.4 Method of test

27.22.4.8.6.7.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.8.6.7.4.2 Procedure

Expected Sequence 6.7 (SET UP MENU, Text Attribute – Italic On, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.8.6.7.4.2, Expected Sequence 6.7.

27.22.4.8.6.7.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.7.

27.22.4.8.6.8 SET UP MENU (support of Text Attribute – Underline On) and ENVELOPE MENU SELECTION

27.22.4.8.6.8.1 Definition and applicability

See clause 3.2.2.

27.22.4.8.6.8.2 Conformance requirement

Requirements are the same as in clause 27.22.4.8.1.1, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.8.6.8.3 Test purpose

To verify that the ME correctly integrates the menu items contained in the SET UP MENU proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.8.6.8.4 Method of test

27.22.4.8.6.8.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.8.6.8.4.2 Procedure

Expected Sequence 6.8 (SET UP MENU, Text Attribute – Underline On, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.8.6.8.4.2, Expected Sequence 6.8.

27.22.4.8.6.8.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.8.

27.22.4.8.6.9 SET UP MENU (support of Text Attribute – Strikethrough On) and ENVELOPE MENU SELECTION

27.22.4.8.6.9.1 Definition and applicability

See clause 3.2.2.

27.22.4.8.6.9.2 Conformance requirement

Requirements are the same as in clause 27.22.4.8.1.1, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.8.6.9.3 Test purpose

To verify that the ME correctly integrates the menu items contained in the SET UP MENU proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.8.6.9.4 Method of test

27.22.4.8.6.9.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.8.6.9.4.2 Procedure

Expected Sequence 6.9 (SET UP MENU, Text Attribute – Strikethrough On, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.8.6.9.4.2, Expected Sequence 6.9.

27.22.4.8.6.9.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.9.

27.22.4.8.6.10 SET UP MENU (support of Text Attribute – Foreground and Background Colour) and ENVELOPE MENU SELECTION

27.22.4.8.6.10.1 Definition and applicability

See clause 3.2.2.

27.22.4.8.6.10.2 Conformance requirement

Requirements are the same as in clause 27.22.4.8.1.1, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.8.6.10.3 Test purpose

To verify that the ME correctly integrates the menu items contained in the SET UP MENU proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.8.6.10.4 Method of test

27.22.4.8.6.10.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.8.6.10.4.2 Procedure

Expected Sequence 6.10 (SET UP MENU, Text Attribute – Foreground and Background Colour, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.8.6.10.4.2, Expected Sequence 6.10.

27.22.4.8.6.10.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.10.

27.22.4.8.7 SET UP MENU (UCS2 display in Cyrillic) and ENVELOPE MENU SELECTION

27.22.4.8.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.8.7.2 Conformance requirement

The ME shall support the SET UP MENU command as defined in:

– TS 31.111 [15] clause 5, clause 6.4.8, clause 6.6.7, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.2, clause 8.9 and clause 9.4.

The ME shall support MENU SELECTION as defined in:

– TS 31.111 [15] clause 4.4, clause 5.2, clause 6.4.8, clause 6.9, clause 7.2, clause 8.7 and clause 8.10.

– Additionally the ME shall support the UCS2 facility for the coding of the Cyrillic alphabet, as defined in ISO/IEC 10646 [17].

27.22.4.8.7.3 Test purpose

To verify that the ME correctly integrates the menu items in UCS2 coding contained in the SET UP MENU proactive UICC command, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

To verify that the ME replaces the current list of menu items with the list of menu items contained in the SET UP MENU command.

To verify that the ME removes the current list of menu items following receipt of a SET UP MENU command with no items.

To verify that the ME correctly passes the identifier of the selected menu item to the UICC using the ENVELOPE (MENU SELECTION) command.

27.22.4.8.7.4 Method of test

27.22.4.8.7.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.8.7.4.2 Procedure

Expected Sequence 7.1 (SET UP MENU and MENU SELECTION, without Help Request, Replace and Remove a Toolkit Menu, with UCS2 in Cyrillic Characters)

See ETSI TS 102 384 [26] in clause 27.22.4.8.7.4.2, Expected Sequence 7.1.

27.22.4.8.7.5 Test requirement

The ME shall operate in the manner defined in expected sequence 7.1.

27.22.4.8.8 SET UP MENU (UCS2 display in Chinese) and ENVELOPE MENU SELECTION

27.22.4.8.8.1 Definition and applicability

See clause 3.2.2.

27.22.4.8.8.2 Conformance requirement

The ME shall support the SET UP MENU command as defined in:

– TS 31.111 [15] clause 5, clause 6.4.8, clause 6.6.7, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.2, clause 8.9 and clause 9.4

The ME shall support MENU SELECTION as defined in:

– TS 31.111 [15] clause 4.4, clause 5.2, clause 6.4.8, clause 6.9, clause 7.2, clause 8.7 and clause 8.10.

– Additionally the ME shall support the UCS2 facility for the coding of the Chinese characters, as defined in ISO/IEC 10646 [17].

27.22.4.8.8.3 Test purpose

To verify that the ME replaces the current list of menu items with the list of menu items contained in the SET UP MENU command.

To verify that the ME removes the current list of menu items following receipt of a SET UP MENU command with no items.

To verify that the ME correctly passes the identifier of the selected menu item to the UICC using the ENVELOPE (MENU SELECTION) command.

27.22.4.8.8.4 Method of test

27.22.4.8.8.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.8.8.4.2 Procedure

Expected Sequence 8.1 (SET UP MENU and MENU SELECTION, without Help Request, Replace and Remove a Toolkit Menu, with UCS2 – Chinese characters)

See ETSI TS 102 384 [26] in clause 27.22.4.8.8.4.2, Expected Sequence 8.1.

27.22.4.8.8.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.1.

27.22.4.8.9 SET UP MENU (UCS2 display in Katakana) and ENVELOPE MENU SELECTION

27.22.4.8.9.1 Definition and applicability

See clause 3.2.2.

27.22.4.8.9.2 Conformance requirement

The ME shall support the SET UP MENU command as defined in:

– TS 31.111 [15] clause 5, clause 6.4.8, clause 6.6.7, clause 6.8, clause 6.11, clause 8.6, clause 8.7, clause 8.2, clause 8.9 and clause 9.4.

The ME shall support MENU SELECTION as defined in:

– TS 31.111 [15] clause 4.4, clause 5.2, clause 6.4.8, clause 6.9, clause 7.2, clause 8.7 and clause 8.10.

– Additionally the ME shall support the UCS2 facility for the coding of the Katakana characters, as defined in ISO/IEC 10646 [17].

27.22.4.8.9.3 Test purpose

To verify that the ME replaces the current list of menu items with the list of menu items contained in the SET UP MENU command.

To verify that the ME removes the current list of menu items following receipt of a SET UP MENU command with no items.

To verify that the ME correctly passes the identifier of the selected menu item to the UICC using the ENVELOPE (MENU SELECTION) command.

27.22.4.8.9.4 Method of test

27.22.4.8.9.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

The ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.8.9.4.2 Procedure

Expected Sequence 9.1 (SET UP MENU and MENU SELECTION, without Help Request, Replace and Remove a Toolkit Menu, with UCS2 in Katakana Characters)

See ETSI TS 102 384 [26] in clause 27.22.4.8.9.4.2, Expected Sequence 9.1.

27.22.4.8.9.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.1.

27.22.4.9 SELECT ITEM

27.22.4.9.1 SELECT ITEM (mandatory features for ME supporting SELECT ITEM)

27.22.4.9.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.1.2 Conformance requirement

The ME shall support the Proactive UICC: Select Item facility as defined in the following technical specifications:

– TS 31.111 [15] clause 5, clause 6.4.9, clause 6.6.8, clause 6.8, clause 8.6, clause 8.7, clause 8.2, clause 8.9, clause 9.4 and clause 10.

27.22.4.9.1.3 Test purpose

To verify that the ME correctly presents the set of items contained in the SELECT ITEM proactive UICC command, and returns a TERMINAL RESPONSE command to the UICC with the identifier of the item chosen.

To verify that the ME allows a SELECT ITEM proactive UICC command within the maximum 255 byte BER-TLV boundary.

To verify that the ME returns a TERMINAL RESPONSE with "Proactive UICC application session terminated by the user", if the user has indicated the need to end the proactive UICC session.

To verify that the ME returns a TERMINAL RESPONSE with "Backwards move in the proactive UICC application session requested by the user", if the user has indicated the need to go backwards in the proactive UICC application session.

27.22.4.9.1.4 Method of test

27.22.4.9.1.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.1.4.2 Procedure

Expected Sequence 1.1 (SELECT ITEM, mandatory features, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.1.4.2, Expected Sequence 1.1.

Expected Sequence 1.2 (SELECT ITEM, large menu, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.1.4.2, Expected Sequence 1.2.

Expected Sequence 1.3 (SELECT ITEM, call options, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.1.4.2, Expected Sequence 1.3.

Expected Sequence 1.4 (SELECT ITEM, backward move by user, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.1.4.2, Expected Sequence 1.4.

Expected Sequence 1.5 (SELECT ITEM, "Y", successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.1.4.2, Expected Sequence 1.5.

Expected Sequence 1.6 (SELECT ITEM, Large menu, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.1.4.2, Expected Sequence 1.6.

The following table details the test commands with relation to the tested features:

	Proactive UICC Command Facilities
Proactive UICC Command SELECT ITEM Number	Alpha Identifier Length	Number of items	Maximum length of item
1.1	14	4	6
1.2	10	30	8
1.3	10	7	43
1.4	11	2	3
1.5	236	1	1
1.6	10	7	37

27.22.4.9.1.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1, 1.2, 1.3, 1.4, 1.5 and 1.6 (SELECT ITEM, mandatory features).

27.22.4.9.2 SELECT ITEM (next action support)

27.22.4.9.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.2.2 Conformance Requirement

Same as clause 27.22.4.9.1.2.

27.22.4.9.2.3 Test purpose

To verify that the mobile supports next action indicator mode.

27.22.4.9.2.4 Method of test

27.22.4.9.2.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.2.4.2 Procedure

Expected Sequence 2.1 (SELECT ITEM, next action indicator, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.2.4.2, Expected Sequence 2.1.

27.22.4.9.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 2.1

27.22.4.9.3 SELECT ITEM (default item support)

27.22.4.9.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.3.2 Conformance requirement

Same as clause 27.22.4.9.1.2.

27.22.4.9.3.3 Test purpose

To verify that the mobile supports "default item" mode.

27.22.4.9.3.4 Method of test

27.22.4.9.3.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.3.4.2 Procedure

Expected Sequence 3.1 (SELECT ITEM, default item, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.3.4.2, Expected Sequence 3.1.

27.22.4.9.3.5 Test requirement

The ME shall operate in the manner defined in expected sequence 3.1

27.22.4.9.4 SELECT ITEM (help request support)

27.22.4.9.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.4.2 Conformance requirement

Same as clause 27.22.4.9.1.2.

27.22.4.9.4.3 Test purpose

To verify that the mobile supports "help request" for the command Select Item.

27.22.4.9.4.4 Method of test

27.22.4.9.4.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.4.4.2 Procedure

Expected Sequence 4.1 (SELECT ITEM, help request, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.4.4.2, Expected Sequence 4.1.

27.22.4.9.4.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.1

27.22.4.9.5 SELECT ITEM (icons support)

27.22.4.9.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.5.2 Conformance requirement

Same as clause 27.22.4.9.1.2 and TS 31.111 [15] clause 8.31 and clause 8.32.

27.22.4.9.5.3 Test purpose

To verify that the mobile displays icons with the command Select Item.

27.22.4.9.5.4 Method of test

27.22.4.9.5.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.5.4.2 Procedure

Expected Sequence 5.1A (SELECT ITEM, BASIC ICON NOT SELF EXPLANATORY, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.5.4.2, Expected Sequence 5.1A.

Expected Sequence 5.1B (SELECT ITEM, BASIC ICON NOT SELF EXPLANATORY, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.9.5.4.2, Expected Sequence 5.1B.

Expected Sequence 5.2A (SELECT ITEM, BASIC ICON SELF EXPLANATORY, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.5.4.2, Expected Sequence 5.2A.

Expected Sequence 5.2B (SELECT ITEM, BASIC ICON SELF EXPLANATORY, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.9.5.4.2, Expected Sequence 5.2B.

27.22.4.9.5.5 Test requirement

The ME shall operate in the manner defined in expected sequences 5.1A to 5.2B.

27.22.4.9.6 SELECT ITEM (presentation style)

27.22.4.9.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.6.2 Conformance requirement

Same as clause 27.22.4.9.1.2.

27.22.4.9.6.3 Test purpose

To verify that the mobile supports the "presentation style" with the command Select Item.

27.22.4.9.6.4 Method of test

27.22.4.9.6.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.6.4.2 Procedure

Expected Sequence 6.1 (SELECT ITEM, PRESENTATION AS A CHOICE OF NAVIGATION OPTIONS, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.6.4.2, Expected Sequence 6.1.

Expected Sequence 6.2 (SELECT ITEM, PRESENTATION AS A CHOICE OF DATA VALUES, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.6.4.2, Expected Sequence 6.2.

27.22.4.9.6.5 Test requirement

The ME shall operate in the manner defined in expected sequences 6.1 and 6.2.

27.22.4.9.7 SELECT ITEM (soft keys support)

27.22.4.9.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.7.2 Conformance requirement

Same as clause 27.22.4.9.1.2.

27.22.4.9.7.3 Test purpose

To verify that the mobile supports the "soft keys" with the command Select Item.

27.22.4.9.7.4 Method of test

27.22.4.9.7.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.7.4.2 Procedure

Expected Sequence 7.1 (SELECT ITEM, SELECTING USING SOFT KEYS PREFERRED, successful, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.7.4.2, Expected Sequence 7.1.

27.22.4.9.7.5 Test requirement

The ME shall operate in the manner defined in expected sequence 7.1.

27.22.4.9.8 SELECT ITEM (Support of "No response from user")

27.22.4.9.8.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.8.2 Conformance requirement

Same as clause 27.22.4.9.1.2.

27.22.4.9.8.3 Test purpose

To verify that after a period of user inactivity the ME returns a "No response from user" result value in the TERMINAL RESPONSE command sent to the UICC.

27.22.4.9.8.4 Method of test

27.22.4.9.8.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME Manufacturer shall have defined the "no response from user" period of time as declared in table A.2/4.

The USIM Simulator shall be set to that period of time.

27.22.4.9.8.4.2 Procedure

Expected Sequence 8.1 (SELECT ITEM, no response from user)

See ETSI TS 102 384 [26] in clause 27.22.4.9.8.4.2, Expected Sequence 8.1.

27.22.4.9.8.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.1.

27.22.4.9.9 SELECT ITEM (Support of Text Attribute)

27.22.4.9.9.1 SELECT ITEM (Support of Text Attribute – Left Alignment)

27.22.4.9.9.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.9.1.2 Conformance requirement

Requirements are the same as in clause 27.22.4.9.1.2, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.9.9.1.3 Test purpose

To verify that the ME displays text formatted according to the left alignment text attribute configuration within the command Select Item.

27.22.4.9.9.1.4 Method of test

27.22.4.9.9.1.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.9.1.4.2 Procedure

Expected Sequence 9.1 (SELECT ITEM, Text Attribute – Left Alignment)

See ETSI TS 102 384 [26] in clause 27.22.4.9.9.1.4.2, Expected Sequence 9.1.

27.22.4.9.9.1.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.1.

27.22.4.9.9.2 SELECT ITEM (Support of Text Attribute – Center Alignment)

27.22.4.9.9.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.9.2.2 Conformance requirement

Requirements are the same as in clause 27.22.4.9.1.2, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.9.9.2.3 Test purpose

To verify that the ME displays text formatted according to the center alignment text attribute configuration within the command Select Item.

27.22.4.9.9.2.4 Method of test

27.22.4.9.9.2.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.9.2.4.2 Procedure

Expected Sequence 9.2 (SELECT ITEM, Text Attribute – Center Alignment)

See ETSI TS 102 384 [26] in clause 27.22.4.9.9.2.4.2, Expected Sequence 9.2.

27.22.4.9.9.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.2.

27.22.4.9.9.3 SELECT ITEM (Support of Text Attribute – Right Alignment)

27.22.4.9.9.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.9.3.2 Conformance requirement

Requirements are the same as in clause 27.22.4.9.1.2, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.9.9.3.3 Test purpose

To verify that the ME displays text formatted according to the right alignment text attribute configuration within the command Select Item.

27.22.4.9.9.3.4 Method of test

27.22.4.9.9.3.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.9.3.4.2 Procedure

Expected Sequence 9.3 (SELECT ITEM, Text Attribute – Right Alignment)

See ETSI TS 102 384 [26] in clause 27.22.4.9.9.3.4.2, Expected Sequence 9.3.

27.22.4.9.9.3.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.3.

27.22.4.9.9.4 SELECT ITEM (Support of Text Attribute – Large Font Size)

27.22.4.9.9.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.9.4.2 Conformance requirement

Requirements are the same as in clause 27.22.4.9.1.2, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.9.9.4.3 Test purpose

To verify that the ME displays text formatted according to the large font size text attribute configuration within the command Select Item.

27.22.4.9.9.4.4 Method of test

27.22.4.9.9.4.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.9.4.4.2 Procedure

Expected Sequence 9.4 (SELECT ITEM, Text Attribute – Large Font Size)

See ETSI TS 102 384 [26] in clause 27.22.4.9.9.4.4.2, Expected Sequence 9.4.

27.22.4.9.9.4.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.4.

27.22.4.9.9.5 SELECT ITEM (Support of Text Attribute – Small Font Size)

27.22.4.9.9.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.9.5.2 Conformance requirement

Requirements are the same as in clause 27.22.4.9.1.2, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.9.9.5.3 Test purpose

To verify that the ME displays text formatted according to the small font size text attribute configuration within the command Select Item.

27.22.4.9.9.5.4 Method of test

27.22.4.9.9.5.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.9.5.4.2 Procedure

Expected Sequence 9.5 (SELECT ITEM, Text Attribute – Small Font Size)

See ETSI TS 102 384 [26] in clause 27.22.4.9.9.5.4.2, Expected Sequence 9.5.

27.22.4.9.9.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.5.

27.22.4.9.9.6 SELECT ITEM (Support of Text Attribute – Bold On)

27.22.4.9.9.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.9.6.2 Conformance requirement

Requirements are the same as in clause 27.22.4.9.1.2, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.9.9.6.3 Test purpose

To verify that the ME displays text formatted according to the bold text attribute configuration within the command Select Item.

27.22.4.9.9.6.4 Method of test

27.22.4.9.9.6.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.9.6.4.2 Procedure

Expected Sequence 9.6 (SELECT ITEM, Text Attribute – Bold On)

See ETSI TS 102 384 [26] in clause 27.22.4.9.9.6.4.2, Expected Sequence 9.6.

27.22.4.9.9.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.6.

27.22.4.9.9.7 SELECT ITEM (Support of Text Attribute – Italic On)

27.22.4.9.9.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.9.7.2 Conformance requirement

Requirements are the same as in clause 27.22.4.9.1.2, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.9.9.7.3 Test purpose

To verify that the ME displays text formatted according to the italic text attribute configuration within the command Select Item.

27.22.4.9.9.7.4 Method of test

27.22.4.9.9.7.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.9.7.4.2 Procedure

Expected Sequence 9.7 (SELECT ITEM, Text Attribute – Italic On)

See ETSI TS 102 384 [26] in clause 27.22.4.9.9.7.4.2, Expected Sequence 9.7.

27.22.4.9.9.7.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.7.

27.22.4.9.9.8 SELECT ITEM (Support of Text Attribute – Underline On)

27.22.4.9.9.8.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.9.8.2 Conformance requirement

Requirements are the same as in clause 27.22.4.9.1.2, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.9.9.8.3 Test purpose

To verify that the ME displays text formatted according to the underline text attribute configuration within the command Select Item.

27.22.4.9.9.8.4 Method of test

27.22.4.9.9.8.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.9.8.4.2 Procedure

Expected Sequence 9.8 (SELECT ITEM, Text Attribute – Underline On)

See ETSI TS 102 384 [26] in clause 27.22.4.9.9.8.4.2, Expected Sequence 9.8.

27.22.4.9.9.8.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.8.

27.22.4.9.9.9 SELECT ITEM (Support of Text Attribute – Strikethrough On)

27.22.4.9.9.9.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.9.9.2 Conformance requirement

Requirements are the same as in clause 27.22.4.9.1.2, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.9.9.9.3 Test purpose

To verify that the ME displays text formatted according to the strikethrough text attribute configuration within the command Select Item.

27.22.4.9.9.9.4 Method of test

27.22.4.9.9.9.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.9.9.4.2 Procedure

Expected Sequence 9.9 (SELECT ITEM, Text Attribute – Strikethrough On)

See ETSI TS 102 384 [26] in clause 27.22.4.9.9.9.4.2, Expected Sequence 9.9.

27.22.4.9.9.9.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.9.

27.22.4.9.9.10 SELECT ITEM (Support of Text Attribute – Foreground and Background Colour)

27.22.4.9.9.10.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.9.10.2 Conformance requirement

Requirements are the same as in clause 27.22.4.9.1.2, with an additional one:

– 3GPP 31.111 [15] clauses 6.5.4, 8.70 and 8.71.

27.22.4.9.9.10.3 Test purpose

To verify that the ME displays text formatted according to the foreground and background colour text attribute configuration within the command Select Item.

27.22.4.9.9.10.4 Method of test

27.22.4.9.9.10.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.9.10.4.2 Procedure

Expected Sequence 9.10 (SELECT ITEM, Text Attribute – Foreground and Background Colour)

See ETSI TS 102 384 [26] in clause 27.22.4.9.9.10.4.2, Expected Sequence 9.10.

27.22.4.9.9.10.5 Test requirement

The ME shall operate in the manner defined in expected sequence 9.10.

27.22.4.9.10 SELECT ITEM (UCS2 display in Cyrillic)

27.22.4.9.10.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.10.2 Conformance requirement

The ME shall support the Proactive UICC: Select Item facility as defined in the following technical specifications:

– TS 31.111 [15] clause 5, clause 6.4.9, clause 6.6.8, clause 6.8, clause 8.6, clause 8.7, clause 8.2, clause 8.9, clause 9.4 and clause 10.

– Additionally the ME shall support the UCS2 facility for the coding of the Cyrillic characters, as defined in ISO/IEC 10646 [17].

27.22.4.9.10.3 Test purpose

To verify that the ME correctly presents the set of items in UCS2 coding contained in the SELECT ITEM proactive UICC command, and returns a TERMINAL RESPONSE command to the UICC with the identifier of the item chosen.

To verify that the ME allows a SELECT ITEM proactive UICC command within the maximum 255 byte BER-TLV boundary.

To verify that the ME returns a TERMINAL RESPONSE with "Proactive UICC application session terminated by the user", if the user has indicated the need to end the proactive UICC session.

27.22.4.9.10.4 Method of test

27.22.4.9.10.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.10.4.2 Procedure

Expected Sequence 10.1 (SELECT ITEM with UCS2 in Cyrillic characters, 0x80 UCS2 coding, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.10.4.2, Expected Sequence 10.1.

Expected Sequence 10.2 (SELECT ITEM with UCS2 in Cyrillic characters, 0x81 UCS2 coding, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.10.4.2, Expected Sequence 10.2.

Expected Sequence 10.3 (SELECT ITEM with UCS2 in Cyrillic characters, 0x82 UCS2 coding, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.10.4.2, Expected Sequence 10.3.

27.22.4.9.10.5 Test requirement

The ME shall operate in the manner defined in expected sequences 10.1 to 10.3.

27.22.4.9.11 SELECT ITEM (UCS2 display in Chinese)

27.22.4.9.11.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.11.2 Conformance requirement

The ME shall support the Proactive UICC: Select Item facility as defined in the following technical specifications:

– TS 31.111 [15] clause 5, clause 6.4.9, clause 6.6.8, clause 6.8, clause 8.6, clause 8.7, clause 8.2, clause 8.9, clause 9.4 and clause 10.

– Additionally the ME shall support the UCS2 facility for the coding of the Chinese characters, as defined in ISO/IEC 10646 [17].

27.22.4.9.11.3 Test purpose

To verify that the ME allows a SELECT ITEM proactive UICC command within the maximum 255 byte BER-TLV boundary.

To verify that the ME returns a TERMINAL RESPONSE with "Proactive UICC application session terminated by the user", if the user has indicated the need to end the proactive UICC session.

27.22.4.9.11.4 Method of test

27.22.4.9.11.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.11.4.2 Procedure

Expected Sequence 11.1 (SELECT ITEM with UCS2 in Chinese characters, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.11.4.2, Expected Sequence 11.1.

27.22.4.9.11.5 Test requirement

The ME shall operate in the manner defined in expected sequence 11.1.

27.22.4.9.12 SELECT ITEM (UCS2 display in Katakana)

27.22.4.9.12.1 Definition and applicability

See clause 3.2.2.

27.22.4.9.12.2 Conformance requirement

The ME shall support the Proactive UICC: Select Item facility as defined in the following technical specifications:

– TS 31.111 [15] clause 5, clause 6.4.9, clause 6.6.8, clause 6.8, clause 8.6, clause 8.7, clause 8.2, clause 8.9, clause 9.4 and clause 10.

– Additionally the ME shall support the UCS2 facility for the coding of the Katakana characters, as defined in ISO/IEC 10646 [17].

27.22.4.9.12.3 Test purpose

To verify that the ME allows a SELECT ITEM proactive UICC command within the maximum 255 byte BER-TLV boundary.

To verify that the ME returns a TERMINAL RESPONSE with "Proactive UICC application session terminated by the user", if the user has indicated the need to end the proactive UICC session.

27.22.4.9.12.4 Method of test

27.22.4.9.12.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.9.12.4.2 Procedure

Expected Sequence 12.1 (SELECT ITEM with UCS2 in Katakana characters, 0x80 UCS2 coding, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.12.4.2, Expected Sequence 12.1.

Expected Sequence 12.2 (SELECT ITEM with UCS2 – Katakana characters, 0x81 UCS2 coding, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.12.4.2, Expected Sequence 12.2.

Expected Sequence 12.3 (SELECT ITEM with UCS2 – Katakana characters, 0x82 UCS2 coding, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.9.12.4.2, Expected Sequence 12.3.

27.22.4.9.12.5 Test requirement

The ME shall operate in the manner defined in expected sequences 12.1 to 12.3.

27.22.4.10 SEND SHORT MESSAGE

27.22.4.10.1 SEND SHORT MESSAGE (normal)

27.22.4.10.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.10.1.2 Conformance requirement

The ME shall support the Proactive UICC: SEND SHORT MESSAGE facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.10, clause 6.6.9, clause 8.1, clause 8.2, clause 8.6, clause 8.7, clause 8.13, clause 8.31 and clause 5.2.

27.22.4.10.1.3 Test purpose

To verify that the ME correctly formats and sends a short message to the network (USS) as indicated in the SEND SHORT MESSAGE proactive UICC command, and returns a TERMINAL RESPONSE command to the UICC indicating the status of the transmission of the Short Message.

27.22.4.10.1.4 Method of test

27.22.4.10.1.4.1 Initial conditions

The ME is connected to the USIM Simulator and connected to the USS.

27.22.4.10.1.4.2 Procedure

Expected Sequence 1.1 (Void)

Expected Sequence 1.2 (Void)

Expected Sequence 1.3 (Void)

Expected Sequence 1.4 (Void)

Expected Sequence 1.5 (Void)

Expected Sequence 1.6 (Void)

Expected Sequence 1.7 (Void)

Expected Sequence 1.8 (Void)

Expected Sequence 1.9 (Send Short Message over CS/PS, UTRAN/GERAN)

In case A.1/157 is supported perform the "CS related procedure" and continue with "Generic Test Procedure 1 (SEND SHORT MESSAGE)" as defined clause 27.22.4.10.7.4.2 as "Expected Sequence 1.9" with the following parameters:

– Used Network Simulator (NWS): USS (UMTS System Simulator or System Simulator)

– CS domain is used to send and receive short messages

– ME supports UTRAN or GERAN

CS related procedure:

Step	Direction	MESSAGE / Action	Comments
1	USER → ME	The ME is switched on	ME will perform Profile Download and USIM initialisation
2	ME → NWS	ME performs CS/PS or CS registration.
3		CONTINUE WITH STEP 4 Generic Test Procedure 1 (SEND SHORT MESSAGE) in clause 27.22.4.10.7.4.2

In case A.1/157 is not supported but A.1/159 is supported perform the "PS related procedure" and continue with "Generic Test Procedure 1 (SEND SHORT MESSAGE)" as defined clause 27.22.4.10.7.4.2 as "Expected Sequence 1.9" with the following parameters:

– Used Network Simulator (NWS): USS (UMTS System Simulator or System Simulator)

– PS domain is used to send and receive short messages

– ME supports UTRAN or GERAN

PS related procedure:

Step	Direction	MESSAGE / Action	Comments
1	USER → ME	The ME is switched on	ME will perform Profile Download and USIM initialisation
2	ME → NWS	ME performs CS/PS or PS registration.
3		CONTINUE WITH STEP 4 Generic Test Procedure 1 (SEND SHORT MESSAGE) in clause 27.22.4.10.7.4.2

27.22.4.10.1.5 Test requirement

The ME shall operate in the manner defined in expected sequence 1.9.

27.22.4.10.2 SEND SHORT MESSAGE (UCS2 display in Cyrillic)

27.22.4.10.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.10.2.2 Conformance requirement

The ME shall support the Proactive UICC: SEND SHORT MESSAGE facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.10, clause 6.6.9, clause 8.1, clause 8.2, clause 8.6, clause 8.7, clause 8.13, clause 8.31 and clause 5.2.

Additionally, the ME shall support the UCS2 facility for the coding of the Cyrillic alphabet, as defined in the following technical specifications: ISO/IEC 10646 [17].

27.22.4.10.2.3 Test purpose

27.22.4.10.2.4 Method of test

27.22.4.10.2.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.10.2.4.2 Procedure

Expected Sequence 2.1 (SEND SHORT MESSAGE, packing not required, UCS2 (16-bit data in Cyrillic))

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 2.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 2.1.1	[packing not required, 16-bit data]
4	ME → USER	Display "ЗДРАВСТВУЙТЕ"	[Alpha Identifier] "Hello" in Russian, 0x80 coding of UCS2 format
5	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 2.1	Cyrillic
6	USS → ME	SMS RP-ACK
7	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 2.1.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "01"
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 2.1.2
10	ME → UICC	FETCH
11	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 2.1.2
12	ME → USER	Display "ЗДРАВСТВУЙТЕ"	[Alpha Identifier] "Hello" in Russian, 0x81 coding of UCS2 format
13	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 2.2
14	USS → ME	SMS RP-ACK
15	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 2.1.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "02"
16	UICC → ME	PROACTIVE UICC SESSION ENDED
17	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 2.1.3
18	ME → UICC	FETCH
19	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 2.1.3	[UCS2 alphabet]
20	ME → USER	Display "ЗДРАВСТВУЙТЕ"	[Alpha Identifier] "Hello" in Russian, 0x82 coding of UCS2 format
21	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 2.3
22	USS → ME	SMS RP-ACK
23	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 2.1.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "03"
24	UICC → ME	PROACTIVE UICC SESSION ENDED

PROACTIVE COMMAND: SEND SHORT MESSAGE: 2.1.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "ЗДРАВСТВУЙТЕ"

Address

TON: International number

NPI: "ISDN / telephone numbering plan"

Dialling number string "112233445566778"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding 16-bit data

Message class class 0

TP-UDL 24

TP-UD "ЗДРАВСТВУЙТЕ"

Coding:

BER-TLV:	D0	55	81	03	01	13	00	82	02	81	83	85
	19	80	04	17	04	14	04	20	04	10	04	12
	04	21	04	22	04	12	04	23	04	19	04	22
	04	15	86	09	91	11	22	33	44	55	66	77
	F8	8B	24	01	00	09	91	10	32	54	76	F8
	40	08	18	04	17	04	14	04	20	04	10	04
	12	04	21	04	22	04	12	04	23	04	19	04
	22	04	15

SMS-PP (SEND SHORT MESSAGE) Message 2.1

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "01"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding UCS2 (16-bit data)

Message class class 0

TP-UDL 24

TP-UD "ЗДРАВСТВУЙТЕ"

Coding:

Coding	01	01	09	91	10	32	54	76	F8	40	08	18
	04	17	04	14	04	20	04	10	04	12	04	21
	04	22	04	12	04	23	04	19	04	22	04	15

SMS-PP (SEND SHORT MESSAGE) Message 2.2

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "02"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding UCS2 (16-bit data)

Message class class 0

TP-UDL 24

TP-UD "ЗДРАВСТВУЙТЕ"

Coding:

Coding	01	02	09	91	10	32	54	76	F8	40	08	18
	04	17	04	14	04	20	04	10	04	12	04	21
	04	22	04	12	04	23	04	19	04	22	04	15

SMS-PP (SEND SHORT MESSAGE) Message 2.3

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "03"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding UCS2 (16-bit data)

Message class class 0

TP-UDL 24

TP-UD "ЗДРАВСТВУЙТЕ"

Coding:

Coding	01	03	09	91	10	32	54	76	F8	40	08	18
	04	17	04	14	04	20	04	10	04	12	04	21
	04	22	04	12	04	23	04	19	04	22	04	15

PROACTIVE COMMAND: SEND SHORT MESSAGE: 2.1.2

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "ЗДРАВСТВУЙТЕ"

Address

TON: International number

NPI: "ISDN / telephone numbering plan"

Dialling number string "112233445566778"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding 16-bit data

Message class class 0

TP-UDL 24

TP-UD "ЗДРАВСТВУЙТЕ"

Coding:

BER-TLV:	D0	4B	81	03	01	13	00	82	02	81	83	85
	0F	81	0C	08	97	94	A0	90	92	A1	A2	92
	A3	99	A2	95	86	09	91	11	22	33	44	55
	66	77	F8	8B	24	01	00	09	91	10	32	54
	76	F8	40	08	18	04	17	04	14	04	20	04
	10	04	12	04	21	04	22	04	12	04	23	04
	19	04	22	04	15

PROACTIVE COMMAND: SEND SHORT MESSAGE: 2.1.3

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "ЗДРАВСТВУЙТЕ"

Address

TON: International number

NPI: "ISDN / telephone numbering plan"

Dialling number string "112233445566778"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding 16-bit data

Message class class 0

TP-UDL 24

TP-UD "ЗДРАВСТВУЙТЕ"

Coding:

BER-TLV:	D0	4C	81	03	01	13	00	82	02	81	83	85
	10	82	0C	04	10	87	84	90	80	82	91	92
	82	93	89	92	85	86	09	91	11	22	33	44
	55	66	77	F8	8B	24	01	00	09	91	10	32
	54	76	F8	40	08	18	04	17	04	14	04	20
	04	10	04	12	04	21	04	22	04	12	04	23
	04	19	04	22	04	15

TERMINAL RESPONSE: SEND SHORT MESSAGE 2.1.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.10.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 2.1.

27.22.4.10.3 SEND SHORT MESSAGE (icon support)

27.22.4.10.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.10.3.2 Conformance requirement

27.22.4.10.3.3 Test purpose

27.22.4.10.3.4 Method of test

27.22.4.10.3.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as Toolkit default.

The ME screen shall be in its normal stand-by display.

27.22.4.10.3.4.2 Procedure

Expected Sequence 3.1A (SEND SHORT MESSAGE, basic icon self-explanatory, packing not required, 8-bit data, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 3.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 3.1.1	[packing not required, 8-bit data]
4	ME → USER	Displays the icon and not the alpha identifier	[basic icon self-explanatory]
5	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 3.1
6	USS → ME	SMS RP-ACK
7	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 3.1.1A	[Command performed successfully]

PROACTIVE COMMAND: SEND SHORT MESSAGE 3.1.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "NO ICON"

Address

TON: International number

NPI: "ISDN / telephone numbering plan"

Dialling number string "112233445566778"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding 8bit-data

Message class class 0

TP-UDL 12

TP-UD "Test Message"

Icon Identifier

Icon Qualifier self-explanatory

Icon Identifier 1 (number of record in EF IMG)

Coding:

BER-TLV:	D0	3B	81	03	01	13	00	82	02	81	83	85
	07	4E	4F	20	49	43	4F	4E	86	09	91	11
	22	33	44	55	66	77	F8	8B	18	01	00	09
	91	10	32	54	76	F8	40	F4	0C	54	65	73
	74	20	4D	65	73	73	61	67	65	9E	02	00
	01

SMS-PP (SEND SHORT MESSAGE) Message 3.1

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "01"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding 8-bit data

Message class class 0

TP-UDL 12

TP-UD "Test Message"

Coding:

Coding	01	01	09	91	10	32	54	76	F8	40	F4	0C
	54	65	73	74	20	4D	65	73	73	61	67	65

TERMINAL RESPONSE: SEND SHORT MESSAGE 3.1.1A

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 3.1B (SEND SHORT MESSAGE, basic icon self-explanatory, packing not required, 8-bit data, requested icon could not be displayed)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 3.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 3.1.1	[packing not required, 8-bit data, basic icon self-explanatory]]
4	ME → USER	Displays the alpha identifier without the icon
5	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 3.1
6	USS → ME	SMS RP-ACK
7	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 3.1.1B	[Command performed successfully, but requested icon could not be displayed]

TERMINAL RESPONSE: SEND SHORT MESSAGE 3.1.1B

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully, but requested icon could not be displayed

Coding:

BER-TLV:

Expected Sequence 3.2A (SEND SHORT MESSAGE, basic icon non-self-explanatory, packing not required, 8-bit data, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 3.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 3.2.1	[packing not required, 8-bit data]
4	ME → USER	display the icon and "Send SM"	[basic icon non-self-explanatory]
5	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 3.2
6	USS → ME	SMS RP-ACK
7	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 3.2.1A	[Command performed successfully]

PROACTIVE COMMAND: SEND SHORT MESSAGE 3.2.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha Identifier "Send SM"

Address

TON: International number

NPI: "ISDN / telephone numbering plan"

Dialling number string "112233445566778"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding 8bit-data

Message class class 0

TP-UDL 12

TP-UD "Test Message"

Icon Identifier

Icon Qualifier non-self-explanatory

Icon Identifier 1 (number of record in EF IMG)

Coding:

BER-TLV:	D0	3B	81	03	01	13	00	82	02	81	83	85
	07	53	65	6E	64	20	53	4D	86	09	91	11
	22	33	44	55	66	77	F8	8B	18	01	00	09
	91	10	32	54	76	F8	40	F4	0C	54	65	73
	74	20	4D	65	73	73	61	67	65	1E	02	01
	01

SMS-PP (SEND SHORT MESSAGE) Message 3.2

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "01"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding 8-bit data

Message class class 0

TP-UDL 12

TP-UD "Test Message"

Coding:

Coding	01	01	09	91	10	32	54	76	F8	40	F4	0C
	54	65	73	74	20	4D	65	73	73	61	67	65

TERMINAL RESPONSE: SEND SHORT MESSAGE 3.2.1A

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 3.2B (SEND SHORT MESSAGE, basic icon non-self-explanatory, packing not required, 8-bit data, requested icon could not be displayed)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 3.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 3.2.1	[packing not required, 8-bit data, basic icon non-self-explanatory ]
4	ME → USER	display "Send SM" without the icon
5	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 3.2
6	USS → ME	SMS RP-ACK
7	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 3.2.1B	[Command performed successfully, but requested icon could not be displayed]

TERMINAL RESPONSE: SEND SHORT MESSAGE 3.2.1B

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully, but requested icon could not be displayed;

Coding:

BER-TLV:

27.22.4.10.3.5 Test requirement

The ME shall operate in the manner defined in expected sequences 3.1A to 3.2B.

27.22.4.10.4 SEND SHORT MESSAGE (Support of Text Attribute)

27.22.4.10.4.1 SEND SHORT MESSAGE (Support of Text Attribute – Left Alignment)

27.22.4.10.4.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.10.4.1.2 Conformance requirement

The ME shall support the Proactive UICC: SEND SHORT MESSAGE facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.10, clause 6.6.9, clause 8.1, clause 8.2, clause 8.6, clause 8.7, clause 8.13, clause 8.31, 8.67 and clause 5.2.

27.22.4.10.4.1.3 Test purpose

To verify that the ME correctly formats and sends a short message to the network (USS) and display the alpha identifier according to the left alignment text attribute configuration as indicated in the SEND SHORT MESSAGE proactive UICC command, and returns a TERMINAL RESPONSE command to the UICC indicating the status of the transmission of the Short Message.

27.22.4.10.4.1.4 Method of test

27.22.4.10.4.1.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.10.4.1.4.2 Procedure

Expected Sequence 4.1 (SEND SHORT MESSAGE, alpha identifier with Text attribute – Left Alignment, packing not required, SMS default alphabet, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.1.1	[packing not required, SMS default alphabet]
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with left alignment]
5	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.1
6	USS → ME	SMS RP-ACK
7	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.1.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "01"
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.1.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.1.2	[packing not required, SMS default alphabet]
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted without left alignment. Remark: If left alignment is the ME’s default alignment as declared in table A.2/11, no alignment change will take place]
12	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.2
13	USS → ME	SMS RP-ACK
14	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.1.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "02"

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.1.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2C	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8B	09	01	00	02	91	10
	40	F0	01	20	D0	04	00	10	00	B4

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.1.2

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Coding:

BER-TLV:	D0	26	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8B	09	01	00	02	91	10
	40	F0	01	20

SMS-PP (SEND SHORT MESSAGE) Message 4.1

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "01"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Coding:

Coding

SMS-PP (SEND SHORT MESSAGE) Message 4.2

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "02"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Coding:

Coding

SMS-PP (SEND SHORT MESSAGE) Message 4.3

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "03"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Coding:

Coding

SMS-PP (SEND SHORT MESSAGE) Message 4.4

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "04"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Coding:

Coding

TERMINAL RESPONSE: SEND SHORT MESSAGE 4.1.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.10.4.1.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.1.

27.22.4.10.4.2 SEND SHORT MESSAGE (Support of Text Attribute – Center Alignment)

27.22.4.10.4.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.10.4.2.2 Conformance requirement

The ME shall support the Proactive UICC: SEND SHORT MESSAGE facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.10, clause 6.6.9, clause 8.1, clause 8.2, clause 8.6, clause 8.7, clause 8.13, clause 8.31, 8.67 and clause 5.2.

27.22.4.10.4.2.3 Test purpose

To verify that the ME correctly formats and sends a short message to the network (USS) and display the alpha identifier according to the center alignment text attribute configuration as indicated in the SEND SHORT MESSAGE proactive UICC command, and returns a TERMINAL RESPONSE command to the UICC indicating the status of the transmission of the Short Message.

27.22.4.10.4.2.4 Method of test

27.22.4.10.4.2.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.10.4.2.4.2 Procedure

Expected Sequence 4.2 (SEND SHORT MESSAGE, alpha identifier with Text attribute – Center Alignment, packing not required, SMS default alphabet, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.2.1	[packing not required, SMS default alphabet]
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with center alignment]
5	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.1
6	USS → ME	SMS RP-ACK
7	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.2.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "01"
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.2.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.2.2	[packing not required, SMS default alphabet]
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted without center alignment. Remark: If center alignment is the ME’s default alignment as declared in table A.2/11, no alignment change will take place]
12	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.2
13	USS → ME	SMS RP-ACK
14	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.2.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "02"

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.2.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Center Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2C	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8B	09	01	00	02	91	10
	40	F0	01	20	D0	04	00	10	01	B4

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.2.2

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Coding:

BER-TLV:	D0	26	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8B	09	01	00	02	91	10
	40	F0	01	20

TERMINAL RESPONSE: SEND SHORT MESSAGE 4.2.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.10.4.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.2.

27.22.4.10.4.3 SEND SHORT MESSAGE (Support of Text Attribute – Right Alignment)

27.22.4.10.4.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.10.4.3.2 Conformance requirement

The ME shall support the Proactive UICC: SEND SHORT MESSAGE facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.10, clause 6.6.9, clause 8.1, clause 8.2, clause 8.6, clause 8.7, clause 8.13, clause 8.31, 8.67 and clause 5.2.

27.22.4.10.4.3.3 Test purpose

To verify that the ME correctly formats and sends a short message to the network (USS) and display the alpha identifier according to the right alignment text attribute configuration as indicated in the SEND SHORT MESSAGE proactive UICC command, and returns a TERMINAL RESPONSE command to the UICC indicating the status of the transmission of the Short Message.

27.22.4.10.4.3.4 Method of test

27.22.4.10.4.3.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.10.4.3.4.2 Procedure

Expected Sequence 4.3 (SEND SHORT MESSAGE, alpha identifier with Text attribute – Right Alignment, packing not required, SMS default alphabet, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.3.1	[packing not required, SMS default alphabet]
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with right alignment]
5	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.1
6	USS → ME	SMS RP-ACK
7	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.3.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "01"
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.3.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.3.2	[packing not required, SMS default alphabet]
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted without right alignment. Remark: If right alignment is the ME’s default alignment as declared in table A.2/11, no alignment change will take place]
12	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.2
13	USS → ME	SMS RP-ACK
14	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.3.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "02"

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.3.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Right Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2C	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8B	09	01	00	02	91	10
	40	F0	01	20	D0	04	00	10	02	B4

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.3.2

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Coding:

BER-TLV:	D0	26	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8B	09	01	00	02	91	10
	40	F0	01	20

TERMINAL RESPONSE: SEND SHORT MESSAGE 4.3.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.10.4.3.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.3.

27.22.4.10.4.4 SEND SHORT MESSAGE (Support of Text Attribute – Large Font Size)

27.22.4.10.4.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.10.4.4.2 Conformance requirement

The ME shall support the Proactive UICC: SEND SHORT MESSAGE facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.10, clause 6.6.9, clause 8.1, clause 8.2, clause 8.6, clause 8.7, clause 8.13, clause 8.31, 8.67 and clause 5.2.

27.22.4.10.4.4.3 Test purpose

To verify that the ME correctly formats and sends a short message to the network (USS) and display the alpha identifier according to the large font size text attribute configuration as indicated in the SEND SHORT MESSAGE proactive UICC command, and returns a TERMINAL RESPONSE command to the UICC indicating the status of the transmission of the Short Message.

27.22.4.10.4.4.4 Method of test

27.22.4.10.4.4.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.10.4.4.4.2 Procedure

Expected Sequence 4.4 (SEND SHORT MESSAGE, alpha identifier with Text attribute – Large Font Size, packing not required, SMS default alphabet, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.4.1	[packing not required, SMS default alphabet]
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with large font size]
5	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.1
6	USS → ME	SMS RP-ACK
7	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.4.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "01"
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.4.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.4.2	[packing not required, SMS default alphabet]
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with normal font size]
12	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.2
13	USS → ME	SMS RP-ACK
14	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.4.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "02"
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.4.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.4.1	[packing not required, SMS default alphabet]
18	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with large font size]
19	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.3
20	USS → ME	SMS RP-ACK
21	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.4.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "03"
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.4.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.4.3	[packing not required, SMS default alphabet]
25	ME → USER	Display "Text Attribute 3"	[Message shall be formatted with normal font size]
26	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.3
27	USS → ME	SMS RP-ACK
28	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.4.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "04"

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.4.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Large Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2C	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8B	09	01	00	02	91	10
	40	F0	01	20	D0	04	00	10	04	B4

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.4.2

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2C	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8B	09	01	00	02	91	10
	40	F0	01	20	D0	04	00	10	00	B4

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.4.3

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 3"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Coding:

BER-TLV:	D0	26	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	33	8B	09	01	00	02	91	10
	40	F0	01	20

TERMINAL RESPONSE: SEND SHORT MESSAGE 4.4.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.10.4.4.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.4.

27.22.4.10.4.5 SEND SHORT MESSAGE (Support of Text Attribute – Small Font Size)

27.22.4.10.4.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.10.4.5.2 Conformance requirement

The ME shall support the Proactive UICC: SEND SHORT MESSAGE facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.10, clause 6.6.9, clause 8.1, clause 8.2, clause 8.6, clause 8.7, clause 8.13, clause 8.31, 8.67 and clause 5.2.

27.22.4.10.4.5.3 Test purpose

To verify that the ME correctly formats and sends a short message to the network (USS) and display the alpha identifier according to the small font size text attribute configuration as indicated in the SEND SHORT MESSAGE proactive UICC command, and returns a TERMINAL RESPONSE command to the UICC indicating the status of the transmission of the Short Message.

27.22.4.10.4.5.4 Method of test

27.22.4.10.4.5.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.10.4.5.4.2 Procedure

Expected Sequence 4.5 (SEND SHORT MESSAGE, alpha identifier with Text attribute – Small Font Size, packing not required, SMS default alphabet, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.5.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.5.1	[packing not required, SMS default alphabet]
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with small font size]
5	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.1
6	USS → ME	SMS RP-ACK
7	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.5.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "01"
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.5.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.5.2	[packing not required, SMS default alphabet]
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with normal font size]
12	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.2
13	USS → ME	SMS RP-ACK
14	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.5.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "02"
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.5.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.5.1	[packing not required, SMS default alphabet]
18	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with small font size]
19	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.3
20	USS → ME	SMS RP-ACK
21	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.5.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "03"
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.5.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.5.3	[packing not required, SMS default alphabet]
25	ME → USER	Display "Text Attribute 3"	[Message shall be formatted with normal font size]
26	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.4
27	USS → ME	SMS RP-ACK
28	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.5.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "04"

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.5.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Small Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2C	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8B	09	01	00	02	91	10
	40	F0	01	20	D0	04	00	10	08	B4

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.5.2

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2C	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8B	09	01	00	02	91	10
	40	F0	01	20	D0	04	00	10	00	B4

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.5.3

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 3"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Coding:

BER-TLV:	D0	26	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	33	8B	09	01	00	02	91	10
	40	F0	01	20

TERMINAL RESPONSE: SEND SHORT MESSAGE 4.5.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.10.4.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.5.

27.22.4.10.4.6 SEND SHORT MESSAGE (Support of Text Attribute – Bold On)

27.22.4.10.4.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.10.4.6.2 Conformance requirement

The ME shall support the Proactive UICC: SEND SHORT MESSAGE facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.10, clause 6.6.9, clause 8.1, clause 8.2, clause 8.6, clause 8.7, clause 8.13, clause 8.31, 8.67 and clause 5.2.

27.22.4.10.4.6.3 Test purpose

To verify that the ME correctly formats and sends a short message to the network (USS) and display the alpha identifier according to the bold text attribute configuration as indicated in the SEND SHORT MESSAGE proactive UICC command, and returns a TERMINAL RESPONSE command to the UICC indicating the status of the transmission of the Short Message.

27.22.4.10.4.6.4 Method of test

27.22.4.10.4.6.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.10.4.6.4.2 Procedure

Expected Sequence 4.6 (SEND SHORT MESSAGE, alpha identifier with Text attribute – Bold On, packing not required, SMS default alphabet, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.6.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.6.1	[packing not required, SMS default alphabet]
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with bold on]
5	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.1
6	USS → ME	SMS RP-ACK
7	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.6.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "01"
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.6.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.6.2	[packing not required, SMS default alphabet]
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with bold off]
12	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.2
13	USS → ME	SMS RP-ACK
14	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.6.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "02"
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.6.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.6.1	[packing not required, SMS default alphabet]
18	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with bold on]
19	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.3
20	USS → ME	SMS RP-ACK
21	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.6.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "03"
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.6.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.6.3	[packing not required, SMS default alphabet]
25	ME → USER	Display "Text Attribute 3"	[Message shall be formatted with bold off]
26	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.4
27	USS → ME	SMS RP-ACK
28	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.6.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "04"

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.6.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold On, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2C	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8B	09	01	00	02	91	10
	40	F0	01	20	D0	04	00	10	10	B4

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.6.2

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2C	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8B	09	01	00	02	91	10
	40	F0	01	20	D0	04	00	10	00	B4

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.6.3

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 3"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Coding:

BER-TLV:	D0	26	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	33	8B	09	01	00	02	91	10
	40	F0	01	20

TERMINAL RESPONSE: SEND SHORT MESSAGE 4.6.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.10.4.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.6.

27.22.4.10.4.7 SEND SHORT MESSAGE (Support of Text Attribute – Italic On)

27.22.4.10.4.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.10.4.7.2 Conformance requirement

The ME shall support the Proactive UICC: SEND SHORT MESSAGE facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.10, clause 6.6.9, clause 8.1, clause 8.2, clause 8.6, clause 8.7, clause 8.13, clause 8.31, 8.67 and clause 5.2.

27.22.4.10.4.7.3 Test purpose

To verify that the ME correctly formats and sends a short message to the network (USS) and display the alpha identifier according to the italic text attribute configuration as indicated in the SEND SHORT MESSAGE proactive UICC command, and returns a TERMINAL RESPONSE command to the UICC indicating the status of the transmission of the Short Message.

27.22.4.10.4.7.4 Method of test

27.22.4.10.4.7.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.10.4.7.4.2 Procedure

Expected Sequence 4.7 (SEND SHORT MESSAGE, alpha identifier with Text attribute – Italic On, packing not required, SMS default alphabet, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.7.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.7.1	[packing not required, SMS default alphabet]
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with italic on]
5	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.1
6	USS → ME	SMS RP-ACK
7	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.7.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "01"
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.7.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.7.2	[packing not required, SMS default alphabet]
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with italic off]
12	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.2
13	USS → ME	SMS RP-ACK
14	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.7.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "02"
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.7.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.7.1	[packing not required, SMS default alphabet]
18	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with italic on]
19	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.3
20	USS → ME	SMS RP-ACK
21	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.7.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "03"
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.7.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.7.3	[packing not required, SMS default alphabet]
25	ME → USER	Display "Text Attribute 3"	[Message shall be formatted with italic off]
26	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.4
27	USS → ME	SMS RP-ACK
28	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.7.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "04"

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.7.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic On, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2C	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8B	09	01	00	02	91	10
	40	F0	01	20	D0	04	00	10	20	B4

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.7.2

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2C	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8B	09	01	00	02	91	10
	40	F0	01	20	D0	04	00	10	00	B4

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.7.3

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 3"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Coding:

BER-TLV:	D0	26	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	33	8B	09	01	00	02	91	10
	40	F0	01	20

TERMINAL RESPONSE: SEND SHORT MESSAGE 4.7.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.10.4.7.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.7.

27.22.4.10.4.8 SEND SHORT MESSAGE (Support of Text Attribute – Underline On)

27.22.4.10.4.8.1 Definition and applicability

See clause 3.2.2.

27.22.4.10.4.8.2 Conformance requirement

The ME shall support the Proactive UICC: SEND SHORT MESSAGE facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.10, clause 6.6.9, clause 8.1, clause 8.2, clause 8.6, clause 8.7, clause 8.13, clause 8.31, 8.67 and clause 5.2.

27.22.4.10.4.8.3 Test purpose

To verify that the ME correctly formats and sends a short message to the network (USS) and display the alpha identifier according to the underline text attribute configuration as indicated in the SEND SHORT MESSAGE proactive UICC command, and returns a TERMINAL RESPONSE command to the UICC indicating the status of the transmission of the Short Message.

27.22.4.10.4.8.4 Method of test

27.22.4.10.4.8.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.10.4.8.4.2 Procedure

Expected Sequence 4.8 (SEND SHORT MESSAGE, alpha identifier with Text attribute – Underline On, packing not required, SMS default alphabet, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.8.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.8.1	[packing not required, SMS default alphabet]
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with underline on]
5	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.1
6	USS → ME	SMS RP-ACK
7	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.8.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "01"
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.8.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.8.2	[packing not required, SMS default alphabet]
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with underline off]
12	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.2
13	USS → ME	SMS RP-ACK
14	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.8.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "02"
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.8.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.8.1	[packing not required, SMS default alphabet]
18	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with underline on]
19	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.3
20	USS → ME	SMS RP-ACK
21	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.8.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "03"
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.8.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.8.3	[packing not required, SMS default alphabet]
25	ME → USER	Display "Text Attribute 3"	[Message shall be formatted with underline off]
26	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.4
27	USS → ME	SMS RP-ACK
28	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.8.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "04"

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.8.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline On, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2C	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8B	09	01	00	02	91	10
	40	F0	01	20	D0	04	00	10	40	B4

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.8.2

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2C	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8B	09	01	00	02	91	10
	40	F0	01	20	D0	04	00	10	00	B4

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.8.3

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 3"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Coding:

BER-TLV:	D0	26	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	33	8B	09	01	00	02	91	10
	40	F0	01	20

TERMINAL RESPONSE: SEND SHORT MESSAGE 4.8.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.10.4.8.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.8.

27.22.4.10.4.9 SEND SHORT MESSAGE (Support of Text Attribute – Strikethrough On)

27.22.4.10.4.9.1 Definition and applicability

See clause 3.2.2.

27.22.4.10.4.9.2 Conformance requirement

The ME shall support the Proactive UICC: SEND SHORT MESSAGE facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.10, clause 6.6.9, clause 8.1, clause 8.2, clause 8.6, clause 8.7, clause 8.13, clause 8.31, 8.67 and clause 5.2.

27.22.4.10.4.9.3 Test purpose

To verify that the ME correctly formats and sends a short message to the network (USS) and display the alpha identifier according to the strikethrough text attribute configuration as indicated in the SEND SHORT MESSAGE proactive UICC command, and returns a TERMINAL RESPONSE command to the UICC indicating the status of the transmission of the Short Message.

27.22.4.10.4.9.4 Method of test

27.22.4.10.4.9.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.10.4.9.4.2 Procedure

Expected Sequence 4.9 (SEND SHORT MESSAGE, alpha identifier with Text attribute – Strikethrough On, packing not required, SMS default alphabet, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.9.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.9.1	[packing not required, SMS default alphabet]
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with strikethrough on]
5	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.1
6	USS → ME	SMS RP-ACK
7	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.9.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "01"
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.9.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.9.2	[packing not required, SMS default alphabet]
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with strikethrough off]
12	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.2
13	USS → ME	SMS RP-ACK
14	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.9.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "02"
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.9.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.9.1	[packing not required, SMS default alphabet]
18	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with strikethrough on]
19	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.3
20	USS → ME	SMS RP-ACK
21	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.9.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "03"
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.9.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.9.3	[packing not required, SMS default alphabet]
25	ME → USER	Display "Text Attribute 3"	[Message shall be formatted with strikethrough off]
26	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.4
27	USS → ME	SMS RP-ACK
28	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.9.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "04"

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.9.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough On

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2C	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8B	09	01	00	02	91	10
	40	F0	01	20	D0	04	00	10	80	B4

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.9.2

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2C	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8B	09	01	00	02	91	10
	40	F0	01	20	D0	04	00	10	00	B4

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.9.3

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 3"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Coding:

BER-TLV:	D0	26	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	33	8B	09	01	00	02	91	10
	40	F0	01	20

TERMINAL RESPONSE: SEND SHORT MESSAGE 4.9.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.10.4.9.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.9.

27.22.4.10.4.10 SEND SHORT MESSAGE (Support of Text Attribute – Foreground and Background Colour)

27.22.4.10.4.10.1 Definition and applicability

See clause 3.2.2.

27.22.4.10.4.10.2 Conformance requirement

The ME shall support the Proactive UICC: SEND SHORT MESSAGE facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.10, clause 6.6.9, clause 8.1, clause 8.2, clause 8.6, clause 8.7, clause 8.13, clause 8.31, 8.67 and clause 5.2.

27.22.4.10.4.10.3 Test purpose

To verify that the ME correctly formats and sends a short message to the network (USS) and display the alpha identifier according to the foreground and background colour text attribute configuration as indicated in the SEND SHORT MESSAGE proactive UICC command, and returns a TERMINAL RESPONSE command to the UICC indicating the status of the transmission of the Short Message.

27.22.4.10.4.10.4 Method of test

27.22.4.10.4.10.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.10.4.10.4.2 Procedure

Expected Sequence 4.10 (SEND SHORT MESSAGE, alpha identifier with Text attribute – Foreground and Background Colour, packing not required, SMS default alphabet, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.10.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.10.1	[packing not required, SMS default alphabet]
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with foreground and background colour according to text attribute configuration]
5	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.1
6	USS → ME	SMS RP-ACK
7	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.10.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "01"
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 4.10.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 4.10.2	[packing not required, SMS default alphabet]
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with ME’s default foreground and background colour]
12	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 4.2
13	USS → ME	SMS RP-ACK
14	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 4.10.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "02"

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.10.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2C	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8B	09	01	00	02	91	10
	40	F0	01	20	D0	04	00	10	00	B4

PROACTIVE COMMAND: SEND SHORT MESSAGE 4.10.2

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "01"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 1

TP-UD " "

Coding:

BER-TLV:	D0	26	81	03	01	13	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8B	09	01	00	02	91	10
	40	F0	01	20

TERMINAL RESPONSE: SEND SHORT MESSAGE 4.10.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.10.4.10.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.10.

27.22.4.10.5 SEND SHORT MESSAGE (UCS2 display in Chinese)

27.22.4.10.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.10.5.2 Conformance requirement

The ME shall support the Proactive UICC: SEND SHORT MESSAGE facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.10, clause 6.6.9, clause 8.1, clause 8.2, clause 8.6, clause 8.7, clause 8.13, clause 8.31 and clause 5.2.

Additionally, the ME shall support the UCS2 facility for the coding of the Chinese characters, as defined in the following technical specifications: ISO/IEC 10646 [17].

27.22.4.10.5.3 Test purpose

27.22.4.10.5.4 Method of test

27.22.4.10.5.4.1 Initial conditions

27.22.4.10.5.4.2 Procedure

Expected Sequence 5.1 (SEND SHORT MESSAGE, packing not required, UCS2 (16-bit data in Chinese))

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 5.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 5.1.1	[packing not required, 16-bit data]
4	ME → USER	Display "中一"	[Alpha Identifier] "Middle 1" in Chinese, 0x80 coding of UCS2 format
5	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 5.1
6	USS → ME	SMS RP-ACK
7	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 5.1.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "01"
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 5.1.2
10	ME → UICC	FETCH
11	UICC → ME	PROACTIVE COMMAND SEND SHORT MESSAGE 5.1.2
12	ME → USER	Display "中一"	[Alpha Identifier] "Middle 1" in Chinese, 0x81 coding of UCS2 format
13	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 5.2
14	USS → ME	SMS RP-ACK
15	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 5.1.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "02"
16	UICC → ME	PROACTIVE UICC SESSION ENDED
17	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 5.1.3
18	ME → UICC	FETCH
19	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 5.1.3	[UCS2 alphabet]
20	ME → USER	Display "中一"	[Alpha Identifier] "Middle 1" in Chinese, 0x82 coding of UCS2 format
21	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 5.3
22	USS → ME	SMS RP-ACK
23	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 5.1.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "03"
24	UICC → ME	PROACTIVE UICC SESSION ENDED

PROACTIVE COMMAND: SEND SHORT MESSAGE: 5.1.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "中一"

Address

TON: International number

NPI: "ISDN / telephone numbering plan"

Dialling number string "112233445566778"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding 16-bit data

Message class class 0

TP-UDL 24

TP-UD "中一"

Coding:

BER-TLV:	D0	2D	81	03	01	13	00	82	02	81	83	85
	05	80	4E	2D	4E	00	86	09	91	11	22	33
	44	55	66	77	F8	8B	10	01	00	09	91	10
	32	54	76	F8	40	08	04	4E	2D	4E	00

SMS-PP (SEND SHORT MESSAGE) Message 5.1

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "01"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding UCS2 (16-bit data)

Message class class 0

TP-UDL 24

TP-UD "中一"

Coding:

BER-TLV:	01	01	09	91	10	32	54	76	F8	40	08	04
	4E	2D	4E	00

SMS-PP (SEND SHORT MESSAGE) Message 5.2

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "02"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding UCS2 (16-bit data)

Message class class 0

TP-UDL 24

TP-UD "中一"

Coding:

BER-TLV:	01	02	09	91	10	32	54	76	F8	40	08	04
	4E	2D	4E	00

SMS-PP (SEND SHORT MESSAGE) Message 5.3

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "03"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding UCS2 (16-bit data)

Message class class 0

TP-UDL 24

TP-UD "中一"

Coding:

BER-TLV:	01	03	09	91	10	32	54	76	F8	40	08	04
	4E	2D	4E	00

PROACTIVE COMMAND: SEND SHORT MESSAGE: 5.1.2

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "中一"

Address

TON: International number

NPI: "ISDN / telephone numbering plan"

Dialling number string "112233445566778"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding 16-bit data

Message class class 0

TP-UDL 24

TP-UD "中一"

Coding:

BER-TLV:	D0	2D	81	03	01	13	00	82	02	81	83	85
	05	81	02	9C	AD	80	86	09	91	11	22	33
	44	55	66	77	F8	8B	10	01	00	09	91	10
	32	54	76	F8	40	08	04	4E	2D	4E	00

PROACTIVE COMMAND: SEND SHORT MESSAGE: 5.1.3

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "中一"

Address

TON: International number

NPI: "ISDN / telephone numbering plan"

Dialling number string "112233445566778"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding 16-bit data

Message class class 0

TP-UDL 24

TP-UD "中一"

Coding:

BER-TLV:	D0	2E	81	03	01	13	00	82	02	81	83	85
	06	82	02	4E	00	AD	80	86	09	91	11	22
	33	44	55	66	77	F8	8B	10	01	00	09	91
	10	32	54	76	F8	40	08	04	4E	2D	4E	00

TERMINAL RESPONSE: SEND SHORT MESSAGE 5.1.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.10.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 2.1.

27.22.4.10.6 SEND SHORT MESSAGE (UCS2 display in Katakana)

27.22.4.10.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.10.6.2 Conformance requirement

The ME shall support the Proactive UICC: SEND SHORT MESSAGE facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.10, clause 6.6.9, clause 8.1, clause 8.2, clause 8.6, clause 8.7, clause 8.13, clause 8.31 and clause 5.2.

Additionally, the ME shall support the UCS2 facility for the coding of the Katakana characters, as defined in the following technical specifications: ISO/IEC 10646 [17].

27.22.4.10.6.3 Test purpose

27.22.4.10.6.4 Method of test

27.22.4.10.6.4.1 Initial conditions

27.22.4.10.6.4.2 Procedure

Expected Sequence 6.1 (SEND SHORT MESSAGE, packing not required, UCS2 (16-bit data, in Katakana))

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 6.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 6.1.1	[packing not required, 16-bit data]
4	ME → USER	Display "80ル0"	[Characters in katakana]
5	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 6.1
6	USS → ME	SMS RP-ACK
7	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 6.1.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "01"
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 6.1.2
10	ME → UICC	FETCH
11	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 6.1.2	[packing not required, 16-bit data]
12	ME → USER	Display "81ル1"	[Characters in katakana]
13	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 6.2
14	USS → ME	SMS RP-ACK
15	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 6.1.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "02"
16	UICC → ME	PROACTIVE UICC SESSION ENDED
17	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 6.1.3
18	ME → UICC	FETCH
19	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 6.1.3	[packing not required, 16-bit data]
20	ME → USER	Display "82ル2"	[Characters in katakana]
21	ME → USS	Send SMS-PP (SEND SHORT MESSAGE) Message 6.3
22	USS → ME	SMS RP-ACK
23	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 6.1.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "03"
24	UICC → ME	PROACTIVE UICC SESSION ENDED

PROACTIVE COMMAND: SEND SHORT MESSAGE: 6.1.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "80ル0"

Address

TON: International number

NPI: "ISDN / telephone numbering plan"

Dialling number string "112233445566778"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept a SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding 16-bit data

Message class class 0

TP-UDL 10

TP-UD "80ル1"

Coding:

BER-TLV:	D0	35	81	03	01	13	00	82	02	81	83	85
	09	80	00	38	00	30	30	EB	00	30	86	09
	91	11	22	33	44	55	66	77	F8	8B	14	01
	00	09	91	10	32	54	76	F8	40	08	08	00
	38	00	30	30	EB	00	31

SMS-PP (SEND SHORT MESSAGE) Message 6.1

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "01"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding UCS2 (16-bit data)

Message class class 0

TP-UDL 10

TP-UD "80ル1"

Coding:

Coding	01	01	09	91	10	32	54	76	F8	40	08	08
	00	38	00	30	30	EB	00	31

TERMINAL RESPONSE: SEND SHORT MESSAGE 6.1.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

PROACTIVE COMMAND: SEND SHORT MESSAGE: 6.1.2

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "81ル1"

Address

TON: International number

NPI: "ISDN / telephone numbering plan"

Dialling number string "112233445566778"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept a SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding 16-bit data

Message class class 0

TP-UDL 10

TP-UD "80ル2"

Coding:

BER-TLV:	D0	33	81	03	01	13	00	82	02	81	83	85
	07	81	04	61	38	31	EB	31	86	09	91	11
	22	33	44	55	66	77	F8	8B	14	01	00	09
	91	10	32	54	76	F8	40	08	08	00	38	00
	30	30	EB	00	32

SMS-PP (SEND SHORT MESSAGE) Message 6.2

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "02"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding UCS2 (16-bit data)

Message class class 0

TP-UDL 10

TP-UD "80ル2"

Coding:

Coding	01	02	09	91	10	32	54	76	F8	40	08	08
	00	38	00	30	30	EB	00	32

PROACTIVE COMMAND: SEND SHORT MESSAGE: 6.1.3

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "82ル2"

Address

TON: International number

NPI: "ISDN / telephone numbering plan"

Dialling number string "112233445566778"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept a SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding 16-bit data

Message class class 0

TP-UDL 10

TP-UD "80ル3"

Coding:

BER-TLV:	D0	34	81	03	01	13	00	82	02	81	83	85
	08	82	04	30	A0	38	32	CB	32	86	09	91
	11	22	33	44	55	66	77	F8	8B	14	01	00
	09	91	10	32	54	76	F8	40	08	08	00	38
	00	30	30	EB	00	33

SMS-PP (SEND SHORT MESSAGE) Message 6.3

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "03"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding UCS2 (16-bit data)

Message class class 0

TP-UDL 10

TP-UD "80ル3"

Coding:

Coding	01	03	09	91	10	32	54	76	F8	40	08	08
	00	38	00	30	30	EB	00	33

27.22.4.10.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.1.

27.22.4.10.7 SEND SHORT MESSAGE (IMS)

27.22.4.10.7.1 Definition and applicability

See clause 3.2.2.

That the UE correctly implemented the role of an SMS-over-IP sender is tested in clause 18.1 of TS 34.229-1 [36].

27.22.4.10.7.2 Conformance requirement

The ME shall support the Proactive UICC: SEND SHORT MESSAGE facility for SMS over IP according to:

– TS 31.111 [15] clause 6.1, clause 6.4.10, clause 6.6.9, clause 8.1, clause 8.2, clause 8.6, clause 8.7, clause 8.13, clause 8.31 and clause 5.2.

– TS 31.103 [35].

– TS 34.229-1 [36], Annexes C.2, C.17 and C.18.

– TS 24.341 [37], clause 5.3.1.

27.22.4.10.7.3 Test purpose

1) To verify that the ME correctly formats and sends a short message via IMS to the E-USS/USS as indicated in the SEND SHORT MESSAGE proactive UICC command, and returns a TERMINAL RESPONSE command to the UICC indicating the status of the transmission of the Short Message.

2) To verify that the ME uses the default service address as indicated in EF SMSP if no service center address is available in the Send Short Message command.

3) To verify that a device of Class ND does not reject the Send Short Message command if the proactive Send Short Message command contains an alpha identifier.

27.22.4.10.7.4 Method of test

27.22.4.10.7.4.1 Initial conditions

The ME is connected to the USIM Simulator. The elementary files are coded as defined for the E-UTRAN/EPC ISIM-UICC in clause 27.22.2C.

For sequence 7.1 the ME is additionally connected to the E-USS.

For sequence 7.2 the ME is additionally connected to the USS.

27.22.4.10.7.4.2 Procedure

Expected Sequence 7.1 (SEND SHORT MESSAGE, SMS-over-IP, E-UTRAN)

Perform the "IMS related procedure 1" and continue with "Generic Test Procedure 1 (SEND SHORT MESSAGE)" as defined in this clause as "Expected Sequence 7.1" with the following parameters:

– Used Network Simulator (NWS): E-USS

– SMS-over-IP is used to send and receive short messages

– ME supports eFDD or eTDD and SMS-over-IP

Expected Sequence 7.2 (SEND SHORT MESSAGE, SMS-over-IP, UTRAN)

Perform the "IMS related procedure 1" and continue with "Generic Test Procedure 1 (SEND SHORT MESSAGE)" as defined in this clause as "Expected Sequence 7.2" with the following parameters:

Used Network Simulator (NWS): USS (UMTS System Simulator only)
SMS-over-IP is used to send and receive short messages
ME supports UTRAN and SMS-over-IP

IMS related procedure 1:

Step	Direction	MESSAGE / Action	Comments
1	USER → ME	The ME is switched on	ME will perform Profle Download, USIM and ISIM initialisation
2	ME → NWS	ME activates the required bearer, discoveres P-CSCF and registers with the values from the ISIM to IMS services	For E-UTRAN: The EPS bearer context activation according to the procedures defined in TS 34.229-1 [36], Annex C.2 and C.18 is performed For UTRAN: For SMS-over-IP a PDP context activation according to the procedures defined in TS 34.229-1 [36], Annex C.2 and C.17 is performed.
3		CONTINUE WITH STEP 4 Generic Test Procedure 1 (SEND SHORT MESSAGE)

Generic Test Procedure 1 (SEND SHORT MESSAGE)

Step	Direction	MESSAGE / Action	Comments
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 7.1.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 7.1.1	[packing not required, SMS default alphabet]
7	ME → NWS	Send RP-DATA containing SMS-PP (SEND SHORT MESSAGE) Message 7.1	See Note 1. In case of SMS-over-IP the RP-Destination Address (SM Service Center Address within the RP-DATA) is taken from the ISIM (EF SMSP)
8	NWS → ME	RP-ACK	See Note 2.
9	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 7.1.1	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "01"
10	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 7.1. 2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 7.1.2	[packing required, 8 bit data]
13	ME → USER	Display "The address data object holds the RP_Destination_Address "	[Alpha Identifier not to be displayed by Terminals of Class_ND]
14	ME → NWS	Send RP-DATA containing SMS-PP (SEND SHORT MESSAGE) Message 7.2	See Note 1.
15	NWS → ME	RP-ACK	See Note 2.
16	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 7.1.2	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "02"
17	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 7.1.3
18	ME → UICC	FETCH
19	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 7.1.3	[packing not required, SMS default alphabet]
20	ME → USER	Display "The address data object holds the RP Destination Address "	[Alpha Identifier not to be displayed by Terminals of Class_ND]
21	ME → NWS	Send RP-DATA containing SMS-PP (SEND SHORT MESSAGE) Message 7.3	See Note 1.
22	NWS → ME	RP-ACK	See Note 2.
23	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 7.1.3	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "03"
24	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 7.1.4
25	ME → UICC	FETCH
26	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 7.1.4	[packing not required, 8-bit data]
27	ME	No information to user	[Alpha identifier length ’00’]
28	ME → NWS	Send RP-DATA containing SMS-PP (SEND SHORT MESSAGE) Message 7.4	See Note 1.
29	NWS → ME	RP-ACK	See Note 2.
30	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 7.1.4	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "04"
31	UICC → ME	PROACTIVE COMMAND PENDING: SEND SHORT MESSAGE 7.1.5
32	ME → UICC	FETCH
33	UICC → ME	PROACTIVE COMMAND: SEND SHORT MESSAGE 7.1.5	[packing not required, 8-bit data]
34	ME → USER	May give information to user concerning what is happening	[No Alpha Identifier]
35	ME → NWS	Send RP-DATA containing SMS-PP (SEND SHORT MESSAGE) Message 7.5	See Note 1.
36	NWS → ME	RP-ACK	See Note 2.
37	ME → UICC	TERMINAL RESPONSE: SEND SHORT MESSAGE 7.1.5	[Command performed successfully] The UE shall have updated Last-Used-TP-MR of EF SMSS to "05"
38	USER → ME	The ME is switched off
Note 1: In case of IMS the RP-DATA is contained in the SIP MESSAGE which is built according to TS 24.341 [37], clause 5.3.1.2 including PSI of the SMSC from EF PSISMSC. Note 2: In case of IMS the RP-ACK message is contained in the message body of the SIP MESSAGE.

PROACTIVE COMMAND: SEND SHORT MESSAGE 7.1.1

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 13

TP-UD "Short Message"

Coding:

BER-TLV:	D0	23	81	03	01	13	00	82	02	81	83	8B
	18	01	00	09	91	10	32	54	76	F8	40	F0
	0D	53	F4	5B	4E	07	35	CB	F3	79	F8	5C
	06

SMS-PP (SEND SHORT MESSAGE) Message 7.1

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "01"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 13

TP-UD "Short Message"

Coding:

Coding	01	01	09	91	10	32	54	76	F8	40	F0	0D
	53	F4	5B	4E	07	35	CB	F3	79	F8	5C	06

TERMINAL RESPONSE: SEND SHORT MESSAGE 7.1.1/7.1.3/7.1.4, 7.1.5

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

PROACTIVE COMMAND: SEND SHORT MESSAGE 7.1.2

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "The address data object holds the RP_Destination_Address"

Address

TON: International number

NPI: "ISDN / telephone numbering plan"

Dialling number string "112233445566778"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding 8 bit data

Message class class 0

TP-UDL 160

TP-UD "Two types are defined: – A short message to be sent to the network in an SMS‑SUBMIT message, or an SMS-COMMAND message, where the user data can be passed transp"

Coding:

BER-TLV:	D0	81	FD	81	03	01	13	01	82	02	81	83
	85	38	54	68	65	20	61	64	64	72	65	73
	73	20	64	61	74	61	20	6F	62	6A	65	63
	74	20	68	6F	6C	64	73	20	74	68	65	20
	52	50	11	44	65	73	74	69	6E	61	74	69
	6F	6E	11	41	64	64	72	65	73	73	86	09
	91	11	22	33	44	55	66	77	F8	8B	81	AC
	01	00	09	91	10	32	54	76	F8	40	F4	A0
	54	77	6F	20	74	79	70	65	73	20	61	72
	65	20	64	65	66	69	6E	65	64	3A	20	2D
	20	41	20	73	68	6F	72	74	20	6D	65	73
	73	61	67	65	20	74	6F	20	62	65	20	73
	65	6E	74	20	74	6F	20	74	68	65	20	6E
	65	74	77	6F	72	6B	20	69	6E	20	61	6E
	20	53	4D	53	2D	53	55	42	4D	49	54	20
	6D	65	73	73	61	67	65	2C	20	6F	72	20
	61	6E	20	53	4D	53	2D	43	4F	4D	4D	41
	4E	44	20	6D	65	73	73	61	67	65	2C	20
	77	68	65	72	65	20	74	68	65	20	75	73
	65	72	20	64	61	74	61	20	63	61	6E	20
	62	65	20	70	61	73	73	65	64	20	74	72
	61	6E	73	70

SMS-PP (SEND SHORT MESSAGE) Message 7.2

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "02"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 160

TP-UD "Two types are defined: – A short message to be sent to the network in an SMS‑SUBMIT message, or an SMS-COMMAND message, where the user data can be passed transp"

Coding:

Coding		01	02	09	91	10	32	54	76	F8	40	F0
	A0	D4	FB	1B	44	CF	C3	CB	73	50	58	5E
	06	91	CB	E6	B4	BB	4C	D6	81	5A	A0	20
	68	8E	7E	CB	E9	A0	76	79	3E	0F	9F	CB
	20	FA	1B	24	2E	83	E6	65	37	1D	44	7F
	83	E8	E8	32	C8	5D	A6	DF	DF	F2	35	28
	ED	06	85	DD	A0	69	73	DA	9A	56	85	CD
	24	15	D4	2E	CF	E7	E1	73	99	05	7A	CB
	41	61	37	68	DA	9C	B6	86	CF	66	33	E8
	24	82	DA	E5	F9	3C	7C	2E	B3	40	77	74
	59	5E	06	D1	D1	65	50	7D	5E	96	83	C8
	61	7A	18	34	0E	BB	41	E2	32	08	1E	9E
	CF	CB	64	10	5D	1E	76	CF	E1

TERMINAL RESPONSE: SEND SHORT MESSAGE 7.1.2

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing required

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

PROACTIVE COMMAND: SEND SHORT MESSAGE 7.1.3

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "The address data object holds the RP Destination Address"

Address

TON: International number

NPI: "ISDN / telephone numbering plan"

Dialling number string "112233445566778"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 160

TP-UD "Two types are defined: – A short message to be sent to the network in an SMS‑SUBMIT message, or an SMS-COMMAND message, where the user data can be passed transp"

Coding:

BER-TLV:	D0	81	E9	81	03	01	13	00	82	02	81	83
	85	38	54	68	65	20	61	64	64	72	65	73
	73	20	64	61	74	61	20	6F	62	6A	65	63
	74	20	68	6F	6C	64	73	20	74	68	65	20
	52	50	20	44	65	73	74	69	6E	61	74	69
	6F	6E	20	41	64	64	72	65	73	73	86	09
	91	11	22	33	44	55	66	77	F8	8B	81	98
	01	00	09	91	10	32	54	76	F8	40	F0	A0
	D4	FB	1B	44	CF	C3	CB	73	50	58	5E	06
	91	CB	E6	B4	BB	4C	D6	81	5A	A0	20	68
	8E	7E	CB	E9	A0	76	79	3E	0F	9F	CB	20
	FA	1B	24	2E	83	E6	65	37	1D	44	7F	83
	E8	E8	32	C8	5D	A6	DF	DF	F2	35	28	ED
	06	85	DD	A0	69	73	DA	9A	56	85	CD	24
	15	D4	2E	CF	E7	E1	73	99	05	7A	CB	41
	61	37	68	DA	9C	B6	86	CF	66	33	E8	24
	82	DA	E5	F9	3C	7C	2E	B3	40	77	74	59
	5E	06	D1	D1	65	50	7D	5E	96	83	C8	61
	7A	18	34	0E	BB	41	E2	32	08	1E	9E	CF
	CB	64	10	5D	1E	76	CF	E1

SMS-PP (SEND SHORT MESSAGE) Message 7.3

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "03"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding SMS default alphabet

Message class class 0

TP-UDL 160

TP-UD "Two types are defined: – A short message to be sent to the network in an SMS-SUBMIT message, or an SMS-COMMAND message, where the user data can be passed transp"

Coding:

Coding	01	03	09	91	10	32	54	76	F8	40	F0	A0
	D4	FB	1B	44	CF	C3	CB	73	50	58	5E	06
	91	CB	E6	B4	BB	4C	D6	81	5A	A0	20	68
	8E	7E	CB	E9	A0	76	79	3E	0F	9F	CB	20
	FA	1B	24	2E	83	E6	65	37	1D	44	7F	83
	E8	E8	32	C8	5D	A6	DF	DF	F2	35	28	ED
	06	85	DD	A0	69	73	DA	9A	56	85	CD	24
	15	D4	2E	CF	E7	E1	73	99	05	7A	CB	41
	61	37	68	DA	9C	B6	86	CF	66	33	E8	24
	82	DA	E5	F9	3C	7C	2E	B3	40	77	74	59
	5E	06	D1	D1	65	50	7D	5E	96	83	C8	61
	7A	18	34	0E	BB	41	E2	32	08	1E	9E	CF
	CB	64	10	5D	1E	76	CF	E1

PROACTIVE COMMAND: SEND SHORT MESSAGE 7.1.4

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Alpha identifier:

Address

TON: International number

NPI: "ISDN / telephone numbering plan"

Dialling number string "112233445566778"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding 8-bit data

Message class class 0

TP-UDL 12

TP-UD "Test Message"

Coding:

BER-TLV:	D0	30	81	03	01	13	00	82	02	81	83	85
	00	86	09	91	11	22	33	44	55	66	77	F8
	8B	18	01	00	09	91	10	32	54	76	F8	40
	F4	0C	54	65	73	74	20	4D	65	73	73	61
	67	65

SMS-PP (SEND SHORT MESSAGE) Message 7.4

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "04"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding 8-bit data

Message class class 0

TP-UDL 12

TP-UD "Test Message"

Coding:

Coding	01	04	09	91	10	32	54	76	F8	40	F4	0C
	54	65	73	74	20	4D	65	73	73	61	67	65

PROACTIVE COMMAND: SEND SHORT MESSAGE 7.1.5

Logically:

Command details

Command number: 1

Command type: SEND SHORT MESSAGE

Command qualifier: packing not required

Device identities

Source device: UICC

Destination device: Network

Address

TON: International number

NPI: "ISDN / telephone numbering plan"

Dialling number string "112233445566778"

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "00"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding 8-bit data

Message class class 0

TP-UDL 12

TP-UD "Test Message"

Coding:

BER-TLV:	D0	2E	81	03	01	13	00	82	02	81	83	86
	09	91	11	22	33	44	55	66	77	F8	8B	18
	01	00	09	91	10	32	54	76	F8	40	F4	0C
	54	65	73	74	20	4D	65	73	73	61	67	65

SMS-PP (SEND SHORT MESSAGE) Message 7.5

Logically:

SMS TPDU

TP-MTI SMS-SUBMIT

TP-RD Instruct the SC to accept an SMS-SUBMIT for a SM

TP-VPF TP-VP field not present

TP-RP TP-Reply-Path is not set in this SMS-SUBMIT

TP-UDHI The TP-UD field contains only the short message

TP-SRR A status report is not requested

TP-MR "05"

TP-DA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "012345678"

TP-PID Short message type 0

TP-DCS

Message coding 8-bit data

Message class class 0

TP-UDL 12

TP-UD "Test Message"

Coding:

Coding	01	05	09	91	10	32	54	76	F8	40	F4	0C
	54	65	73	74	20	4D	65	73	73	61	67	65

27.22.4.10.7.5 Test requirement

The ME supporting eFDD or eTDD shall operate in the manner defined in expected sequence 7.1.

The ME supporting UTRAN shall operate in the manner defined in expected sequence 7.2.

27.22.4.10.8 SEND SHORT MESSAGE (over SGs in E-UTRAN)

27.22.4.10.8.1 Definition and applicability

See clause 3.2.2.

27.22.4.10.8.2 Conformance requirement

The ME shall support the Proactive UICC: SEND SHORT MESSAGE facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.10, clause 6.6.9, clause 8.1, clause 8.2, clause 8.6, clause 8.7, clause 8.13, clause 8.31 and clause 5.2.

– TS 24.301 [32] clause 5.6.3.1, 5.6.3.3 and 9.9.3.22

27.22.4.10.8.3 Test purpose

To verify that the ME correctly formats and sends a short message to the network (E-USS/NB-SS) using SMS over SGs as indicated in the SEND SHORT MESSAGE proactive UICC command, and returns a TERMINAL RESPONSE command to the UICC indicating the status of the transmission of the Short Message.

27.22.4.10.8.4 Method of test

27.22.4.10.8.4.1 Initial conditions

The ME is connected to the USIM Simulator and connected to the E-USS/NB-SS.

27.22.4.10.8.4.2 Procedure

Expected Sequence 8.1 (Send Short Message over SGs, E-UTRAN)

Perform the "SMS over SGs procedure" and continue with "Generic Test Procedure 1 (SEND SHORT MESSAGE)" as defined clause 27.22.4.10.7.4.2 as "Expected Sequence 8.1" with the following parameters:

Used Network Simulator (NWS): E-USS/NB-SS
SMS over SGs (DOWNLINK NAS TRANSPORT and UPLINK NAS TRANSPORT messages)
is used to send and receive short messages
ME supports eFDD or eTDD or NB-IoT
ME supports SMS-over-SGs.

SMS over SGs related procedure:

Step	Direction	MESSAGE / Action	Comments
1	USER → ME	The ME is switched on	ME will perform Profile Download and USIM initialisation
2	ME → NWS	ME performs regular network registration.	UE is afterwards in state Registered, Idle Mode (state 2) according to TS 36.508 [33].
3		CONTINUE WITH STEP 4 Generic Test Procedure 1 (SEND SHORT MESSAGE) in clause 27.22.4.10.7.4.2

27.22.4.10.8.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.1.

27.22.4.11 SEND SS

27.22.4.11.1 SEND SS (normal)

27.22.4.11.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.11.1.2 Conformance requirement

The ME shall support the Proactive UICC: Send SS facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.11, clause 6.6.10, clause 8.12.1, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.14, clause 8.31 and clause 6.5.

27.22.4.11.1.3 Test purpose

To verify that the ME correctly translates and sends the supplementary service request indicated in the SEND SS proactive UICC command to the USS.

To verify that the ME returns a TERMINAL RESPONSE command to the UICC indicating the status of the transmission of the SS and any contents of the SS result as additional data.

27.22.4.11.1.4 Method of test

27.22.4.11.1.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.The elementary files are coded as USIM Application Toolkit default. Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.11.1.4.2 Procedure

Expected Sequence 1.1A (SEND SS, call forward unconditional, all bearers, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 1.1.1
4	ME → USER	Display "Call Forward"
5	ME → USS	REGISTER 1.1A
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.1A	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 1.1.1A

Expected Sequence 1.1B (SEND SS, call forward unconditional, all bearers, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 1.1.1
4	ME → USER	Display "Call Forward"
5	ME → USS	REGISTER 1.1B
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.1B	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 1.1.1B

PROACTIVE COMMAND: SEND SS 1.1.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Call Forward"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Coding:

BER-TLV:	D0	29	81	03	01	11	00	82	02	81	83	85
	0C	43	61	6C	6C	20	46	6F	72	77	61	72
	64	89	10	91	AA	12	0A	21	43	65	87	09
	21	43	65	87	A9	01	FB

Logically (only SS argument):

SS-Code:

– Call Forwarding Unconditional

TeleserviceCode

– All Tele Services

ForwardedToNumber

– nature of address ind.: international

– numbering plan ind.: ISDN/Telephony (E.164)

– TBCD String: 01234567890123456789

– longFTN-Supported

Coding:

BER-TLV	30	15	04	01	21	83	01	00	84	0B	91	10
	32	54	76	98	10	32	54	76	98	89	00

Logically (only SS argument):

SS-Code:

– Call Forwarding Unconditional

TeleserviceCode

– All Tele Services

ForwardedToNumber

– nature of address ind.: international

– numbering plan ind.: ISDN/Telephony (E.164)

– TBCD String: 01234567890123456789

Coding:

BER-TLV	30	13	04	01	21	83	01	00	84	0B	91	10
	32	54	76	98	10	32	54	76	98

RELEASE COMPLETE (SS RETURN RESULT) 1.1A

Logically (only from operation code):

ForwardingInfo

SS-Code

– Call Forwarding Unconditional

ForwardFeatureList

ForwardingFeature

TeleserviceCode

– All Tele Services

SS-Status

– state ind.: operative

– provision ind.: provisioned

– registration ind.: registered

– activation ind.: active

longForwardedToNumber

– nature of address ind.: international

– numbering plan ind.: ISDN/Telephony (E.164)

– TBCD String: 01234567890123456789

Coding:

Coding	0A	A0	1A	04	01	21	30	15	30	13	83	01
	00	84	01	07	89	0B	91	10	32	54	76	98
	10	32	54	76	98

RELEASE COMPLETE (SS RETURN RESULT) 1.1B

Logically (only from operation code):

ForwardingInfo

SS-Code

– Call Forwarding Unconditional

ForwardFeatureList

ForwardingFeature

TeleserviceCode

– All Tele Services

SS-Status

– state ind.: operative

– provision ind.: provisioned

– registration ind.: registered

– activation ind.: active

Coding:

Coding	0A	A0	0D	04	01	21	30	08	30	06	83	01
	00	84	01	07

TERMINAL RESPONSE: SEND SS 1.1.1A

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Additional information: Operation Code and SS Parameters

Coding:

BER-TLV:	81	03	01	11	00	82	02	82	81	03	1E
	00	0A	A0	1A	04	01	21	30	15	30	13
	83	01	00	84	01	07	89	0B	91	10	32
	54	76	98	10	32	54	76	98

TERMINAL RESPONSE: SEND SS 1.1.1B

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Additional information: Operation Code and SS Parameters

Coding:

BER-TLV:	81	03	01	11	00	82	02	82	81	03	11
	00	0A	A0	0D	04	01	21	30	08	30	06
	83	01	00	84	01	07

Expected Sequence 1.2 (SEND SS, call forward unconditional, all bearers, Return Error)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 1.1.1
4	ME → USER	Display "Call Forward"
5	ME → USS	REGISTER 1.1A Or REGISTER 1.1B
6	USS → ME	RELEASE COMPLETE (SS RETURN ERROR) 1.1	[Return Error]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 1.2.1

RELEASE COMPLETE (SS RETURN ERROR) 1.1

Logically (only from error code):

Error Code: Facility not supported

Coding:

Coding

TERMINAL RESPONSE: SEND SS 1.2.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: SS Return Error

Additional information: Error Code

Coding:

BER-TLV:	81	03	01	11	00	82	02	82	81	03	02
	34	15

Expected Sequence 1.3 (SEND SS, call forward unconditional, all bearers, Reject)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 1.1.1
4	ME → USER	Display "Call Forward"
5	ME → USS	REGISTER 1.1A Or REGISTER 1.1B
6	USS → ME	RELEASE COMPLETE (SS REJECT) 1.1.	[Reject]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 1.3.1

RELEASE COMPLETE (SS REJECT) 1.1

Logically (only from problem code):

Problem Code:

– General problem

– Unrecognized component

Coding:

Coding

TERMINAL RESPONSE: SEND SS 1.3.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: SS Return Error

Additional information: No specific cause can be given

Coding:

BER-TLV:	81	03	01	11	00	82	02	82	81	03	02
	34	00

Expected Sequence 1.4A (SEND SS, call forward unconditional, all bearers, successful, SS request size limit)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 1.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 1.4.1
4	ME → USER	Display "Call Forward"
5	ME → USS	REGISTER 1.2A
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.2A	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 1.4.1A

Expected Sequence 1.4B (SEND SS, call forward unconditional, all bearers, successful, SS request size limit)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 1.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 1.4.1
4	ME → USER	Display "Call Forward"
5	ME → USS	REGISTER 1.2B
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.2B	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 1.4.1B

PROACTIVE COMMAND: SEND SS 1.4.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Call Forward"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*0123456789012345678901234567*11#"

Coding:

BER-TLV:	D0	2D	81	03	01	11	00	82	02	81	83	85
	0C	43	61	6C	6C	20	46	6F	72	77	61	72
	64	89	14	91	AA	12	0A	21	43	65	87	09
	21	43	65	87	09	21	43	65	A7	11	FB

Logically (only SS argument):

RegisterSSArg

SS-Code

Call Forwarding Unconditional

TeleserviceCode

See Note 1

ForwardedToNumber

nature of address ind.: international

numbering plan ind.: ISDN/Telephony (E.164)

TBCD String: 0123456789012345678901234567

longFTN-Supported

Coding:

BER-TLV	30	19	04	01	21	83	01	Note 1	84	0F	91	10
	32	54	76	98	10	32	54	76	98	10	32	54
	76	89	00

Note 1: TeleserviceCode is ’11’ for "Telephony" or is ’10’ for "allSpeechTransmissionServices"

Logically (only SS argument):

RegisterSSArg

SS-Code

Call Forwarding Unconditional

TeleserviceCode

See Note 1

ForwardedToNumber

nature of address ind.: international

numbering plan ind.: ISDN/Telephony (E.164)

TBCD String: 0123456789012345678901234567

Coding:

BER-TLV	30	17	04	01	21	83	01	Note 1	84	0F	91	10
	32	54	76	98	10	32	54	76	98	10	32	54
	76

Note 1: TeleserviceCode is ’11’ for "Telephony" or is ’10’ for "allSpeechTransmissionServices"

Logically (only from operation code):

ForwardingInfo

SS-Code

– Call Forwarding Unconditional

ForwardFeatureList

ForwardingFeature

TeleserviceCode

– See Note 1

SS-Status

– state ind.: operative

– provision ind.: provisioned

– registration ind.: registered

– activation ind.: active

longForwardedToNumber

– nature of address ind.: international

– numbering plan ind.: ISDN/Telephony (E.164)

– TBCD String: 0123456789012345678901234567

Coding:

Coding	0A	A0	1E	04	01	21	30	19	30	17	83	01
	Note 1	84	01	07	89	0F	91	10	32	54	76	98
	10	32	54	76	98	10	32	54	76

Note 1: TeleserviceCode is ’11’ for "Telephony" or is ’10’ for "allSpeechTransmissionServices"

RELEASE COMPLETE (SS RETURN RESULT) 1.2B

Logically (only from operation code):

ForwardingInfo

SS-Code

– Call Forwarding Unconditional

ForwardFeatureList

ForwardingFeature

TeleserviceCode

– See Note 1

SS-Status

– state ind.: operative

– provision ind.: provisioned

– registration ind.: registered

– activation ind.: active

Coding:

Coding	0A	A0	0D	04	01	21	30	08	30	06	83	01
	Note 1	84	01	07

Note 1: TeleserviceCode is ’11’ for "Telephony" or is ’10’ for "allSpeechTransmissionServices"

TERMINAL RESPONSE: SEND SS 1.4.1A

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Additional information: Operation Code and SS Parameters

Coding:

BER-TLV:	81	03	01	11	00	82	02	82	81	03	22
	00	0A	A0	1E	04	01	21	30	19	30	17
	83	01	Note 1	84	01	07	89	0F	91	10	32
	54	76	98	10	32	54	76	98	10	32	54
	76

Note 1: TeleserviceCode is ’11’ for "Telephony" or is ’10’ for "allSpeechTransmissionServices"

TERMINAL RESPONSE: SEND SS 1.4.1B

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Additional information: Operation Code and SS Parameters

Coding:

BER-TLV:	81	03	01	11	00	82	02	82	81	03	11
	00	0A	A0	0D	04	01	21	30	08	30	06
	83	01	Note 1	84	01	07

Note 1: TeleserviceCode is ’11’ for "Telephony" or is ’10’ for "allSpeechTransmissionServices"

Expected Sequence 1.5 (SEND SS, interrogate CLIR status, successful, alpha identifier limits)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 1.5.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 1.5.1
4	ME → USER	Display "Even if the Fixed Dialling Number service is enabled, the supplementary service control string included in the SEND SS proactive command shall not be checked against those of the FDN list. Upon receiving this command, the ME shall deci"
5	ME → USS	REGISTER 1.3
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.3	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 1.5.1

PROACTIVE COMMAND: SEND SS 1.5.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Even if the Fixed Dialling Number service is enabled, the supplementary service control string included in the SEND SS proactive command shall not be checked against those of the FDN list. Upon receiving this command, the ME shall deci"

SS String

TON: Undefined

NPI: Undefined

SS string: "*#31#"

Coding:

BER-TLV:	D0	81	FD	81	03	01	11	00	82	02	81	83
	85	81	EB	45	76	65	6	20	69	66	20	74
	68	65	20	46	69	78	65	64	20	44	69	61
	6C	6C	69	6E	67	20	4E	75	6D	62	65	72
	20	73	65	72	76	69	63	65	20	69	73	20
	65	6E	61	62	6C	65	64	2C	20	74	68	65
	20	73	75	70	70	6C	65	6D	65	6E	74	61
	72	79	20	73	65	72	76	69	63	65	20	63
	6F	6E	74	72	6F	6C	20	73	74	72	69	6E
	67	20	69	6E	63	6C	75	64	65	64	20	69
	6E	20	74	68	65	20	53	45	4E	44	20	53
	53	20	70	72	6F	61	63	74	69	76	65	20
	63	6F	6D	6D	61	6E	64	20	73	68	61	6C
	6C	20	6E	6F	74	20	62	65	20	63	68	65
	63	6B	65	64	20	61	67	61	69	6E	73	74
	20	74	68	6F	73	65	20	6F	66	20	74	68
	65	20	46	44	4E	20	6C	69	73	74	2E	20
	55	70	6F	6E	20	72	65	63	65	69	76	69
	6E	67	20	74	68	69	73	20	63	6F	6D	6D
	61	6E	64	2C	20	74	68	65	20	4D	45	20
	73	68	61	6C	6C	20	64	65	63	69	89	04
	FF	BA	13	FB

Logically (only SS argument):

INTERROGATE SS ARGUMENT

SS-Code

– Calling Line Id Restriction

Coding:

BER-TLV

RELEASE COMPLETE (SS RETURN RESULT) 1.3

Logically (only from operation code):

INTERROGATE SS RESULT

CliRestrictionInfo

SS-Status

– state ind.: operative

– provision ind.: provisioned

– registration ind.: registered

– activation ind.: not active

CliRestrictionOption

– Temporary Def Allowed

Coding:

Coding

TERMINAL RESPONSE: SEND SS 1.5.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Additional information

Operation Code: SS Code

Parameters: SS Return Result

Coding:

BER-TLV:	81	03	01	11	00	82	02	82	81	03	0A
	00	0E	A4	06	04	01	06	0A	01	02

Expected Sequence 1.6A (SEND SS, call forward unconditional, all bearers, successful, null data alpha identifier)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 1.6.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 1.6.1
4	ME	Should not give any information to the user on the fact that the ME is sending an SS request
5	ME → USS	REGISTER 1.1A
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.1A	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 1.1.1A

Expected Sequence 1.6B (SEND SS, call forward unconditional, all bearers, successful, null data alpha identifier)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 1.6.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 1.6.1
4	ME	Should not give any information to the user on the fact that the ME is sending an SS request
5	ME → USS	REGISTER 1.1B
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.1B	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 1.1.1B

PROACTIVE COMMAND: SEND SS 1.6.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: null data object

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Coding:

BER-TLV:	D0	1D	81	03	01	11	00	82	02	81	83	85
	00	89	10	91	AA	12	0A	21	43	65	87	09
	21	43	65	87	A9	01	FB

27.22.4.11.1.5 Test requirement

The ME shall operate in the manner defined in expected sequence 1.1 to 1.6.

27.22.4.11.2 SEND SS (Icon support)

27.22.4.11.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.11.2.2 Conformance requirement

27.22.4.11.2.3 Test purpose

To verify that the ME displays the text contained in the SEND SS proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

In addition to verify that if an icon is provided by the UICC, the icon indicated in the command may be used by the ME to inform the user, in addition to, or instead of the alpha identifier, as indicated with the icon qualifier.

27.22.4.11.2.4 Method of test

27.22.4.11.2.4.1 Initial conditions

The ME is connected to the USIM Simulator and to the USS. Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

The elementary files are coded as Toolkit default.

27.22.4.11.2.4.2 Procedure

Expected Sequence 2.1A (SEND SS, call forward unconditional, all bearers, successful, basic icon self explanatory, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 2.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 2.1.1	[BASIC-ICON, self-explanatory]
4	ME → USER	Display the basic icon without the alpha identifier
5	ME → USS	REGISTER 1.1A Or REGISTER 1.1B	Option A applies if A.1/63 is supported, Option B applies if A.1/63 is not supported
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.1A or RELEASE COMPLETE (SS RETURN RESULT) 1.1B	[Successful] Option A applies if A.1/63 is supported, Option B applies if A.1/63 is not supported
7	ME → UICC	TERMINAL RESPONSE: SEND SS 2.1.1AA or TERMINAL RESPONSE: SEND SS 2.1.1AB	[Command performed successfully] Option AA applies if A.1/63 is supported, Option AB applies if A.1/63 is not supported

PROACTIVE COMMAND: SEND SS 2.1.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Basic Icon"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Icon Identifier:

Icon qualifier: icon is self-explanatory

Icon Identifier: record 1 in EF_(IMG)

Coding:

BER-TLV:	D0	2B	81	03	01	11	00	82	02	81	83	85
	0A	42	61	73	69	63	20	49	63	6F	6E	89
	10	91	AA	12	0A	21	43	65	87	09	21	43
	65	87	A9	01	FB	9E	02	00	01

TERMINAL RESPONSE: SEND SS 2.1.1AA

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Additional information: Operation Code and SS Parameters

Coding:

BER-TLV:	81	03	01	11	00	82	02	82	81	03	1E
	00	0A	A0	1A	04	01	21	30	15	30	13
	83	01	00	84	01	07	89	0B	91	10	32
	54	76	98	10	32	54	76	98

TERMINAL RESPONSE: SEND SS 2.1.1AB

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Additional information: Operation Code and SS Parameters

Coding:

BER-TLV:	81	03	01	11	00	82	02	82	81	03	11
	00	0A	A0	0D	04	01	21	30	08	30	06
	83	01	00	84	01	07

Expected Sequence 2.1B (SEND SS, call forward unconditional, all bearers, successful, basic icon self explanatory, requested icon could not be displayed)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 2.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 2.1.1	[BASIC-ICON, self-explanatory]
4	ME → USER	Display "Basic Icon" without the icon
5	ME → USS	REGISTER 1.1A Or REGISTER 1.1B	Option A applies if A.1/63 is supported, Option B applies if A.1/63 is not supported
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.1A or RELEASE COMPLETE (SS RETURN RESULT) 1.1B	[Successful] Option A applies if A.1/63 is supported, Option B applies if A.1/63 is not supported
7	ME → UICC	TERMINAL RESPONSE: SEND SS 2.1.1BA or TERMINAL RESPONSE: SEND SS 2.1.1BB	[Command performed successfully, but requested icon could not be displayed] Option BA applies if A.1/63 is supported, Option BB applies if A.1/63 is not supported

TERMINAL RESPONSE: SEND SS 2.1.1BA

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully, but requested icon could not be displayed

Additional information: Operation Code and SS Parameters

Coding:

BER-TLV:	81	03	01	11	00	82	02	82	81	03	1E
	04	0A	A0	1A	04	01	21	30	15	30	13
	83	01	00	84	01	07	89	0B	91	10	32
	54	76	98	10	32	54	76	98

TERMINAL RESPONSE: SEND SS 2.1.1BB

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully, but requested icon could not be displayed

Additional information: Operation Code and SS Parameters

Coding:

BER-TLV:	81	03	01	11	00	82	02	82	81	03	11
	04	0A	A0	0D	04	01	21	30	08	30	06
	83	01	00	84	01	07

Expected Sequence 2.2A (SEND SS, call forward unconditional, all bearers, successful, colour icon self explanatory, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 2.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 2.2.1	[COLOUR-ICON, self-explanatory]
4	ME → USER	Display the colour icon without thealpha identifier
5	ME → USS	REGISTER 1.1A Or REGISTER 1.1B	Option A applies if A.1/63 is supported, Option B applies if A.1/63 is not supported
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.1A or RELEASE COMPLETE (SS RETURN RESULT) 1.1B	[Successful] Option A applies if A.1/63 is supported, Option B applies if A.1/63 is not supported
7	ME → UICC	TERMINAL RESPONSE: SEND SS 2.1.1AA or TERMINAL RESPONSE: SEND SS 2.1.1AB	[Command performed successfully] Option AA applies if A.1/63 is supported, Option AB applies if A.1/63 is not supported

PROACTIVE COMMAND: SEND SS 2.2.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Colour Icon"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Icon Identifier:

Icon qualifier: icon is self-explanatory

Icon Identifier: record 2 in EF_(IMG)

Coding:

BER-TLV:	D0	2C	81	03	01	11	00	82	02	81	83	85
	0B	43	6F	6C	6F	75	72	20	49	63	6F	6E
	89	10	91	AA	12	0A	21	43	65	87	09	21
	43	65	87	A9	01	FB	9E	02	00	02

Expected Sequence 2.2B (SEND SS, call forward unconditional, all bearers, successful, colour icon self explanatory, requested icon could not be displayed)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 2.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 2.2.1	[COLOUR-ICON, self-explanatory]
4	ME → USER	Display "Colour Icon" without the icon
5	ME → USS	REGISTER 1.1A Or REGISTER 1.1B	Option A applies if A.1/63 is supported, Option B applies if A.1/63 is not supported
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.1A or RELEASE COMPLETE (SS RETURN RESULT) 1.1B	[Successful] Option A applies if A.1/63 is supported, Option B applies if A.1/63 is not supported
7	ME → UICC	TERMINAL RESPONSE: SEND SS 2.1.1BA or TERMINAL RESPONSE: SEND SS 2.1.1BB	[Command performed but requested icon could not be displayed] Option BA applies if A.1/63 is supported, Option BB applies if A.1/63 is not supported

Expected Sequence 2.3A (SEND SS, call forward unconditional, all bearers, successful, basic icon non self-explanatory, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 2.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 2.3.1	[BASIC-ICON, non self-explanatory]
4	ME → USER	Display "Basic Icon" and the basic icon
5	ME → USS	REGISTER 1.1A Or REGISTER 1.1B	Option A applies if A.1/63 is supported, Option B applies if A.1/63 is not supported
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.1A or RELEASE COMPLETE (SS RETURN RESULT) 1.1B	[Successful] Option A applies if A.1/63 is supported, Option B applies if A.1/63 is not supported
7	ME → UICC	TERMINAL RESPONSE: SEND SS 2.1.1AA or TERMINAL RESPONSE: SEND SS 2.1.1AB	[Command performed successfully] Option AA applies if A.1/63 is supported, Option AB applies if A.1/63 is not supported

PROACTIVE COMMAND: SEND SS 2.3.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha Identifier

Text: "Basic Icon"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Icon Identifier

Icon qualifier: icon is non self-explanatory

Icon Identifier: record 1 in EF_(IMG)

Coding:

BER-TLV:	D0	2B	81	03	01	11	00	82	02	81	83	85
	0A	42	61	73	69	63	20	49	63	6F	6E	89
	10	91	AA	12	0A	21	43	65	87	09	21	43
	65	87	A9	01	FB	9E	02	01	01

Expected Sequence 2.3B (SEND SS, call forward unconditional, all bearers, successful, basic icon non self-explanatory)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 2.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 2.3.1	[BASIC-ICON, non self-explanatory]
4	ME → USER	Display "Basic Icon" without the icon
5	ME → USS	REGISTER 1.1A Or REGISTER 1.1B	Option A applies if A.1/63 is supported, Option B applies if A.1/63 is not supported
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.1A or RELEASE COMPLETE (SS RETURN RESULT) 1.1B	[Successful] Option A applies if A.1/63 is supported, Option B applies if A.1/63 is not supported
7	ME → UICC	TERMINAL RESPONSE: SEND SS 2.1.1BA or TERMINAL RESPONSE: SEND SS 2.1.1BB	[Command performed but requested icon could not be displayed] Option BA applies if A.1/63 is supported, Option BB applies if A.1/63 is not supported

Expected Sequence 2.4 (SEND SS, call forward unconditional, all bearers, successful, basic icon non self-explanatory, no alpha identifier presented)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 2.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 2.4.1	[BASIC-ICON, non self-explanatory]
4	ME → UICC	TERMINAL RESPONSE: SEND SS 2.4.1	[Command data not understood by ME]

PROACTIVE COMMAND: SEND SS 2.4.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789#"

Icon Identifier

Icon qualifier: icon is non self-explanatory

Icon Identifier: record 1 in EF_(IMG)

Coding:

BER-TLV:	D0	1D	81	03	01	11	00	82	02	81	83	89
	0E	91	AA	12	0A	21	43	65	87	09	21	43
	65	87	B9	9E	02	01	01

TERMINAL RESPONSE: SEND SS 2.4.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command data not understood by ME

Coding:

BER-TLV:

27.22.4.11.2.5 Test requirement

The ME shall operate in the manner defined in expected sequences 2.1A to 2.4.

27.22.4.11.3 SEND SS (UCS2 display in Cyrillic)

27.22.4.11.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.11.3.2 Conformance requirement

The ME shall support the Proactive UICC: SEND SHORT MESSAGE facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.11, clause 6.6.10, clause 8.12.1 , clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.14, clause 8.31 and clause 6.5

Additionnally, the ME shall support the UCS2 facility for the coding of the Cyrillic alphabet, as defined in: ISO/IEC 10646 [17].

27.22.4.11.3.3 Test purpose

To verify that the ME displays the UCS2 text contained in the SEND SS proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.11.3.4 Method of test

27.22.4.11.3.4.1 Initial conditions

27.22.4.11.3.4.2 Procedure

Expected Sequence 3.1 (SEND SS, call forward unconditional, all bearers, successful, UCS2 text in Cyrillic)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 3.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 3.1.1
4	ME → USER	Display "ЗДРАВСТВУЙТЕ"	["Hello" in Russian]
5	ME → USS	REGISTER 1.1A Or REGISTER 1.1B	Option A applies if A.1/63 is supported, Option B applies if A.1/63 is not supported
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.1A or RELEASE COMPLETE (SS RETURN RESULT) 1.1B	[Successful] Option A applies if A.1/63 is supported, Option B applies if A.1/63 is not supported
7	ME → UICC	TERMINAL RESPONSE: SEND SS 1.1.1A or TERMINAL RESPONSE: SEND SS 1.1.1B	[Command performed successfully] Option A applies if A.1/63 is supported, Option B applies if A.1/63 is not supported

PROACTIVE COMMAND: SEND SS 3.1.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha Identifier

Data coding scheme: UCS2 (16bit)

Text: "ЗДРАВСТВУЙТЕ"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Coding:

BER-TLV:	D0	36	81	03	01	11	00	82	02	81	83	85
	19	80	04	17	04	14	04	20	04	10	04	12
	04	21	04	22	04	12	04	23	04	19	04	22
	04	15	89	10	91	AA	12	0A	21	43	65	87
	09	21	43	65	87	A9	01	FB

27.22.4.11.3.5 Test requirement

The ME shall operate in the manner defined in expected sequence 3.1.

27.22.4.11.4 SEND SS (support of Text Attribute)

27.22.4.11.4.1 SEND SS (support of Text Attribute – Left Alignment)

27.22.4.11.4.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.11.4.1.2 Conformance requirement

The ME shall support the Proactive UICC: Send SS facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.11, clause 6.6.10, clause 8.12.1 , clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.14, clause 8.31 and clause 6.5.

27.22.4.11.4.1.3 Test purpose

To verify that the ME displays the alpha identifier according to the left alignment text attribute configuration in the SEND SS proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.11.4.1.4 Method of test

27.22.4.11.4.1.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.11.4.1.4.2 Procedure

Expected Sequence 4.1A (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Left Alignment)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.1.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with left alignment]
5	ME → USS	REGISTER 4.1A
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.1.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.1.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with left alignment. Remark: If left alignment is the ME’s default alignment as declared in table A.2/12, no alignment change will take place]
12	ME → USS	REGISTER 4.1A
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A

Expected Sequence 4.1B (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Left Alignment)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.1.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with left alignment]
5	ME → USS	REGISTER 4.1B
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.1.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.1.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with left alignment. Remark: If left alignment is the ME’s default alignment as declared in table A.2/12, no alignment change will take place]
12	ME → USS	REGISTER 4.1B
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B

PROACTIVE COMMAND: SEND SS 4.1.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	33	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB	D0
	04	00	10	00	B4

PROACTIVE COMMAND: SEND SS 4.1.2

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Coding:

BER-TLV:	D0	2D	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB

Same as cl 27.22.4.11.1.4.2 REGISTER 1.1A

Same as cl 27.22.4.11.1.4.2 REGISTER 1.1B

RELEASE COMPLETE (SS RETURN RESULT) 4.1A

Same as cl 27.22.4.11.1.4.2 RELEASE COMPLETE (SS RETURN RESULT) 1.1A

RELEASE COMPLETE (SS RETURN RESULT) 4.1B

Same as cl 27.22.4.11.1.4.2 RELEASE COMPLETE (SS RETURN RESULT) 1.1B

TERMINAL RESPONSE: SEND SS 4.1.1A

Same as cl 27.22.4.11.1.4.2 TERMINAL RESPONSE: SEND SS 1.1.1A

TERMINAL RESPONSE: SEND SS 4.1.1B

Same as cl 27.22.4.11.1.4.2 TERMINAL RESPONSE: SEND SS 1.1.1B

27.22.4.11.4.1.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.1.

27.22.4.11.4.2 SEND SS (support of Text Attribute – Center Alignment)

27.22.4.11.4.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.11.4.2.2 Conformance requirement

The ME shall support the Proactive UICC: Send SS facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.11, clause 6.6.10, clause 8.12.1 , clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.14, clause 8.31 and clause 6.5.

27.22.4.11.4.2.3 Test purpose

To verify that the ME displays the alpha identifier according to the center alignment text attribute configuration in the SEND SS proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.11.4.2.4 Method of test

27.22.4.11.4.2.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.11.4.2.4.2 Procedure

Expected Sequence 4.2A (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Center Alignment)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.2.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with center alignment]
5	ME → USS	REGISTER 4.1A
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.2.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.2.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with center alignment. Remark: If center alignment is the ME’s default alignment as declared in table A.2/12, no alignment change will take place]
12	ME → USS	REGISTER 4.1A
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A

Expected Sequence 4.2B (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Center Alignment)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.2.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with center alignment]
5	ME → USS	REGISTER 4.1B
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.2.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.2.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with center alignment. Remark: If center alignment is the ME’s default alignment as declared in table A.2/12, no alignment change will take place]
12	ME → USS	REGISTER 4.1B
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B

PROACTIVE COMMAND: SEND SS 4.2.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Center Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	33	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB	D0
	04	00	10	01	B4

PROACTIVE COMMAND: SEND SS 4.2.2

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Coding:

BER-TLV:	D0	2D	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB

27.22.4.11.4.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.2.

27.22.4.11.4.3 SEND SS (support of Text Attribute – Right Alignment)

27.22.4.11.4.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.11.4.3.2 Conformance requirement

The ME shall support the Proactive UICC: Send SS facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.11, clause 6.6.10, clause 8.12.1 , clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.14, clause 8.31 and clause 6.5.

27.22.4.11.4.3.3 Test purpose

To verify that the ME displays the alpha identifier according to the right alignment text attribute configuration in the SEND SS proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.11.4.3.4 Method of test

27.22.4.11.4.3.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.11.4.3.4.2 Procedure

Expected Sequence 4.3A (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Right Alignment)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.3.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with right alignment]
5	ME → USS	REGISTER 4.1A
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.3.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.3.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with right alignment. Remark: If right alignment is the ME’s default alignment as declared in table A.2/12, no alignment change will take place]
12	ME → USS	REGISTER 4.1A
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A

Expected Sequence 4.3B (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Right Alignment)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.3.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with right alignment]
5	ME → USS	REGISTER 4.1B
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.3.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.3.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with right alignment. Remark: If right alignment is the ME’s default alignment as declared in table A.2/12, no alignment change will take place]
12	ME → USS	REGISTER 4.1B
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B

PROACTIVE COMMAND: SEND SS 4.3.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Right Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	33	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB	D0
	04	00	10	02	B4

PROACTIVE COMMAND: SEND SS 4.3.2

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Coding:

BER-TLV:	D0	2D	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB

27.22.4.11.4.3.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.3.

27.22.4.11.4.4 SEND SS (support of Text Attribute – Large Font Size)

27.22.4.11.4.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.11.4.4.2 Conformance requirement

The ME shall support the Proactive UICC: Send SS facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.11, clause 6.6.10, clause 8.12.1 , clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.14, clause 8.31 and clause 6.5.

27.22.4.11.4.4.3 Test purpose

To verify that the ME displays the alpha identifier according to the large font size text attribute configuration in the SEND SS proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.11.4.4.4 Method of test

27.22.4.11.4.4.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.11.4.4.4.2 Procedure

Expected Sequence 4.4A (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Large Font Size)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.4.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with large font size]
5	ME → USS	REGISTER 4.1A
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.4.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.4.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with normal font size]
12	ME → USS	REGISTER 4.1A
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.4.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND SS 4.4.1
18	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with large font size]
19	ME → USS	REGISTER 4.1A
20	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
21	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.4.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND SS 4.4.3
25	ME → USER	Display "Text Attribute 3"	[Message shall be formatted with normal font size]
26	ME → USS	REGISTER 4.1A
27	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
28	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A

Expected Sequence 4.4B (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Large Font Size)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.4.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with large font size]
5	ME → USS	REGISTER 4.1B
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.4.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.4.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with normal font size]
12	ME → USS	REGISTER 4.1B
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.4.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND SS 4.4.1
18	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with large font size]
19	ME → USS	REGISTER 4.1B
20	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
21	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.4.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND SS 4.4.3
25	ME → USER	Display "Text Attribute 3"	[Message shall be formatted with normal font size]
26	ME → USS	REGISTER 4.1B
27	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
28	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B

PROACTIVE COMMAND: SEND SS 4.4.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Large Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	33	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB	D0
	04	00	10	04	B4

PROACTIVE COMMAND: SEND SS 4.4.2

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	33	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB	D0
	04	00	10	00	B4

PROACTIVE COMMAND: SEND SS 4.4.3

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 3"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Coding:

BER-TLV:	D0	2D	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	33	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB

27.22.4.11.4.4.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.4.

27.22.4.11.4.5 SEND SS (support of Text Attribute – Small Font Size)

27.22.4.11.4.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.11.4.5.2 Conformance requirement

The ME shall support the Proactive UICC: Send SS facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.11, clause 6.6.10, clause 8.12.1 , clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.14, clause 8.31 and clause 6.5.

27.22.4.11.4.5.3 Test purpose

To verify that the ME displays the alpha identifier according to the small font size text attribute configuration in the SEND SS proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.11.4.5.4 Method of test

27.22.4.11.4.5.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.11.4.5.4.2 Procedure

Expected Sequence 4.5A (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Small Font Size)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.5.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.5.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with small font size]
5	ME → USS	REGISTER 4.1A
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.5.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.5.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with normal font size]
12	ME → USS	REGISTER 4.1A
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.5.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND SS 4.5.1
18	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with small font size]
19	ME → USS	REGISTER 4.1A
20	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
21	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.5.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND SS 4.5.3
25	ME → USER	Display "Text Attribute 3"	[Message shall be formatted with normal font size]
26	ME → USS	REGISTER 4.1A
27	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
28	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A

Expected Sequence 4.5B (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Small Font Size)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.5.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.5.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with small font size]
5	ME → USS	REGISTER 4.1B
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.5.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.5.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with normal font size]
12	ME → USS	REGISTER 4.1B
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.5.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND SS 4.5.1
18	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with small font size]
19	ME → USS	REGISTER 4.1B
20	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
21	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.5.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND SS 4.5.3
25	ME → USER	Display "Text Attribute 3"	[Message shall be formatted with normal font size]
26	ME → USS	REGISTER 4.1B
27	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
28	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B

PROACTIVE COMMAND: SEND SS 4.5.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Small Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	33	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB	D0
	04	00	10	08	B4

PROACTIVE COMMAND: SEND SS 4.5.2

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	33	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB	D0
	04	00	10	00	B4

PROACTIVE COMMAND: SEND SS 4.5.3

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 3"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Coding:

BER-TLV:	D0	2D	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	33	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB

27.22.4.11.4.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.5.

27.22.4.11.4.6 SEND SS (support of Text Attribute – Bold On)

27.22.4.11.4.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.11.4.6.2 Conformance requirement

The ME shall support the Proactive UICC: Send SS facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.11, clause 6.6.10, clause 8.12.1 , clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.14, clause 8.31 and clause 6.5.

27.22.4.11.4.6.3 Test purpose

To verify that the ME displays the alpha identifier according to the bold text attribute configuration in the SEND SS proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.11.4.6.4 Method of test

27.22.4.11.4.6.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.11.4.6.4.2 Procedure

Expected Sequence 4.6A (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Bold On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.6.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.6.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with bold on]
5	ME → USS	REGISTER 4.1A
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.6.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.6.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with bold off]
12	ME → USS	REGISTER 4.1A
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.6.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND SS 4.6.1
18	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with bold on]
19	ME → USS	REGISTER 4.1A
20	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
21	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.6.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND SS 4.6.3
25	ME → USER	Display "Text Attribute 3"	[Message shall be formatted with bold off]
26	ME → USS	REGISTER 4.1A
27	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
28	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A

Expected Sequence 4.6B (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Bold On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.6.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.6.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with bold on]
5	ME → USS	REGISTER 4.1B
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.6.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.6.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with bold off]
12	ME → USS	REGISTER 4.1B
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.6.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND SS 4.6.1
18	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with bold on]
19	ME → USS	REGISTER 4.1B
20	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
21	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.6.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND SS 4.6.3
25	ME → USER	Display "Text Attribute 3"	[Message shall be formatted with bold off]
26	ME → USS	REGISTER 4.1B
27	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
28	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B

PROACTIVE COMMAND: SEND SS 4.6.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold On, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	33	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB	D0
	04	00	10	10	B4

PROACTIVE COMMAND: SEND SS 4.6.2

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	33	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB	D0
	04	00	10	00	B4

PROACTIVE COMMAND: SEND SS 4.6.3

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 3"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Coding:

BER-TLV:	D0	2D	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	33	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB

27.22.4.11.4.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.6.

27.22.4.11.4.7 SEND SS (support of Text Attribute – Italic On)

27.22.4.11.4.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.11.4.7.2 Conformance requirement

The ME shall support the Proactive UICC: Send SS facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.11, clause 6.6.10, clause 8.12.1 , clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.14, clause 8.31 and clause 6.5.

27.22.4.11.4.7.3 Test purpose

To verify that the ME displays the alpha identifier according to the italic text attribute configuration in the SEND SS proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.11.4.7.4 Method of test

27.22.4.11.4.7.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.11.4.7.4.2 Procedure

Expected Sequence 4.7A (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Italic On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.7.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.7.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with italic on]
5	ME → USS	REGISTER 4.1A
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.7.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.7.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with italic off]
12	ME → USS	REGISTER 4.1A
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.7.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND SS 4.7.1
18	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with italic on]
19	ME → USS	REGISTER 4.1A
20	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
21	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.7.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND SS 4.7.3
25	ME → USER	Display "Text Attribute 3"	[Message shall be formatted with italic off]
26	ME → USS	REGISTER 4.1A
27	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
28	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A

Expected Sequence 4.7B (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Italic On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.7.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.7.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with italic on]
5	ME → USS	REGISTER 4.1B
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.7.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.7.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with italic off]
12	ME → USS	REGISTER 4.1B
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.7.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND SS 4.7.1
18	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with italic on]
19	ME → USS	REGISTER 4.1B
20	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
21	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.7.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND SS 4.7.3
25	ME → USER	Display "Text Attribute 3"	[Message shall be formatted with italic off]
26	ME → USS	REGISTER 4.1B
27	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
28	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B

PROACTIVE COMMAND: SEND SS 4.7.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic On, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	33	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB	D0
	04	00	10	20	B4

PROACTIVE COMMAND: SEND SS 4.7.2

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	33	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB	D0
	04	00	10	00	B4

PROACTIVE COMMAND: SEND SS 4.7.3

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 3"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Coding:

BER-TLV:	D0	2D	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	33	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB

27.22.4.11.4.7.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.7.

27.22.4.11.4.8 SEND SS (support of Text Attribute – Underline On)

27.22.4.11.4.8.1 Definition and applicability

See clause 3.2.2.

27.22.4.11.4.8.2 Conformance requirement

The ME shall support the Proactive UICC: Send SS facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.11, clause 6.6.10, clause 8.12.1 , clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.14, clause 8.31 and clause 6.5.

27.22.4.11.4.8.3 Test purpose

To verify that the ME displays the alpha identifier according to the underline text attribute configuration in the SEND SS proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.11.4.8.4 Method of test

27.22.4.11.4.8.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.11.4.8.4.2 Procedure

Expected Sequence 4.8A (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Underline On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.8.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.8.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with underline on]
5	ME → USS	REGISTER 4.1A
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.8.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.8.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with underline off]
12	ME → USS	REGISTER 4.1A
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.8.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND SS 4.8.1
18	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with underline on]
19	ME → USS	REGISTER 4.1A
20	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
21	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.8.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND SS 4.8.3
25	ME → USER	Display "Text Attribute 3"	[Message shall be formatted with underline off]
26	ME → USS	REGISTER 4.1A
27	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
28	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A

Expected Sequence 4.8B (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Underline On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.8.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.8.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with underline on]
5	ME → USS	REGISTER 4.1B
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.8.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.8.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with underline off]
12	ME → USS	REGISTER 4.1B
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.8.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND SS 4.8.1
18	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with underline on]
19	ME → USS	REGISTER 4.1B
20	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
21	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.8.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND SS 4.8.3
25	ME → USER	Display "Text Attribute 3"	[Message shall be formatted with underline off]
26	ME → USS	REGISTER 4.1B
27	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
28	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B

PROACTIVE COMMAND: SEND SS 4.8.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline On, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	33	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB	D0
	04	00	10	40	B4

PROACTIVE COMMAND: SEND SS 4.8.2

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	33	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB	D0
	04	00	10	00	B4

PROACTIVE COMMAND: SEND SS 4.8.3

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 3"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Coding:

BER-TLV:	D0	2D	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	33	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB

27.22.4.11.4.8.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.8.

27.22.4.11.4.9 SEND SS (support of Text Attribute – Strikethrough On)

27.22.4.11.4.9.1 Definition and applicability

See clause 3.2.2.

27.22.4.11.4.9.2 Conformance requirement

The ME shall support the Proactive UICC: Send SS facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.11, clause 6.6.10, clause 8.12.1 , clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.14, clause 8.31 and clause 6.5.

27.22.4.11.4.9.3 Test purpose

To verify that the ME displays the alpha identifier according to the strikethrough text attribute configuration in the SEND SS proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.11.4.9.4 Method of test

27.22.4.11.4.9.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.11.4.9.4.2 Procedure

Expected Sequence 4.9A (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Strikethrough On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.9.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.9.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with strikethrough on]
5	ME → USS	REGISTER 4.1A
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.9.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.9.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with strikethrough off]
12	ME → USS	REGISTER 4.1A
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.9.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND SS 4.9.1
18	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with strikethrough on]
19	ME → USS	REGISTER 4.1A
20	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
21	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.9.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND SS 4.9.3
25	ME → USER	Display "Text Attribute 3"	[Message shall be formatted with strikethrough off]
26	ME → USS	REGISTER 4.1A
27	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
28	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A

Expected Sequence 4.9B (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Strikethrough On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.9.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.9.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with strikethrough on]
5	ME → USS	REGISTER 4.1B
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.9.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.9.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with strikethrough off]
12	ME → USS	REGISTER 4.1B
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.9.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND SS 4.9.1
18	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with strikethrough on]
19	ME → USS	REGISTER 4.1B
20	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
21	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.9.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND SS 4.9.3
25	ME → USER	Display "Text Attribute 3"	[Message shall be formatted with strikethrough off]
26	ME → USS	REGISTER 4.1B
27	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
28	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B

PROACTIVE COMMAND: SEND SS 4.9.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough On

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	33	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB	D0
	04	00	10	80	B4

PROACTIVE COMMAND: SEND SS 4.9.2

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	33	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB	D0
	04	00	10	00	B4

PROACTIVE COMMAND: SEND SS 4.9.3

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 3"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Coding:

BER-TLV:	D0	2D	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	33	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB

27.22.4.11.4.9.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.9.

27.22.4.11.4.10 SEND SS (support of Text Attribute – Foreground and Background Colour)

27.22.4.11.4.10.1 Definition and applicability

See clause 3.2.2.

27.22.4.11.4.10.2 Conformance requirement

The ME shall support the Proactive UICC: Send SS facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.11, clause 6.6.10, clause 8.12.1 , clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.14, clause 8.31 and clause 6.5.

27.22.4.11.4.10.3 Test purpose

To verify that the ME displays the alpha identifier according to the foreground and background colour text attribute configuration in the SEND SS proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.11.4.10.4 Method of test

27.22.4.11.4.10.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.11.4.10.4.2 Procedure

Expected Sequence 4.10A (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Foreground and Background Colour)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.10.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.10.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with foreground and background colour according to text attribute configuration]
5	ME → USS	REGISTER 4.1A
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.10.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.10.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with ME’s default foreground and background colour]
12	ME → USS	REGISTER 4.1A
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1A	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1A

Expected Sequence 4.10B (SEND SS, call forward unconditional, all bearers, successful, alpha identifier with Text attribute – Foreground and Background Colour)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.10.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 4.10.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with foreground and background colour according to text attribute configuration]
5	ME → USS	REGISTER 4.1B
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 4.10.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND SS 4.10.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with ME’s default foreground and background colour]
12	ME → USS	REGISTER 4.1B
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1B	[Successful]
14	ME → UICC	TERMINAL RESPONSE: SEND SS 4.1.1B

PROACTIVE COMMAND: SEND SS 4.10.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	33	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB	D0
	04	00	10	00	B4

PROACTIVE COMMAND: SEND SS 4.10.2

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Coding:

BER-TLV:	D0	2D	81	03	01	11	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	89	10	91	AA	12	0A	21
	43	65	87	09	21	43	65	87	A9	01	FB

27.22.4.11.4.10.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.10.

27.22.4.11.5 SEND SS (UCS2 display in Chinese)

27.22.4.11.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.11.5.2 Conformance requirement

The ME shall support the Proactive UICC: SEND SHORT MESSAGE facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.11, clause 6.6.10, clause 8.12.1 , clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.14, clause 8.31 and clause 6.5

Additionnally, the ME shall support the UCS2 facility for the coding of the Chinese characters, as defined in: ISO/IEC 10646 [17].

27.22.4.11.5.3 Test purpose

To verify that the ME displays the UCS2 text contained in the SEND SS proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.11.5.4 Method of test

27.22.4.11.5.4.1 Initial conditions

27.22.4.11.5.4.2 Procedure

Expected Sequence 5.1A (SEND SS, call forward unconditional, all bearers, successful, UCS2 text in Chinese)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 5.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 5.1.1
4	ME → USER	Display "你好"	["Hello" in Chinese]
5	ME → USS	REGISTER 5.1A
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 5.1A	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 5.1.1A	[Command performed successfully]

Expected Sequence 5.1B (SEND SS, call forward unconditional, all bearers, successful, UCS2 text in Chinese)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 5.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 5.1.1
4	ME → USER	Display "你好"	["Hello" in Chinese]
5	ME → USS	REGISTER 5.1B
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 5.1B	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 5.1.1B	[Command performed successfully]

PROACTIVE COMMAND: SEND SS 5.1.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha Identifier

Data coding scheme: UCS2 (16bit)

Text: "你好"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Coding:

BER-TLV:	D0	22	81	03	01	11	00	82	02	81	83	85
	05	80	4F	60	59	7D	89	10	91	AA	12	0A
	21	43	65	87	09	21	43	65	87	A9	01	FB

Same as cl 27.22.4.11.1.4.2 REGISTER 1.1A

Same as cl 27.22.4.11.1.4.2 REGISTER 1.1B

RELEASE COMPLETE (SS RETURN RESULT) 5.1A

Same as cl 27.22.4.11.1.4.2 RELEASE COMPLETE (SS RETURN RESULT) 1.1A

RELEASE COMPLETE (SS RETURN RESULT) 5.1B

Same as cl 27.22.4.11.1.4.2 RELEASE COMPLETE (SS RETURN RESULT) 1.1B

TERMINAL RESPONSE: SEND SS 5.1.1A

Same as cl 27.22.4.11.1.4.2 TERMINAL RESPONSE: SEND SS 1.1.1A

TERMINAL RESPONSE: SEND SS 5.1.1B

Same as cl 27.22.4.11.1.4.2 TERMINAL RESPONSE: SEND SS 1.1.1B

27.22.4.11.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 5.1.

27.22.4.11.6 SEND SS (UCS2 display in Katakana)

27.22.4.11.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.11.6.2 Conformance requirement

The ME shall support the Proactive UICC: SEND SHORT MESSAGE facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.11, clause 6.6.10, clause 8.12.1 , clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.14, clause 8.31 and clause 6.5

Additionnally, the ME shall support the UCS2 facility for the coding of the Katakana characters, as defined in: ISO/IEC 10646 [17].

27.22.4.11.6.3 Test purpose

To verify that the ME displays the UCS2 text contained in the SEND SS proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.11.6.4 Method of test

27.22.4.11.6.4.1 Initial conditions

27.22.4.11.6.4.2 Procedure

Expected Sequence 6.1A (SEND SS, call forward unconditional, all bearers, successful, UCS2 text in Katakana)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 6.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 6.1.1
4	ME → USER	Display "ル"	[Character in Katakana]
5	ME → USS	REGISTER 6.1A
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 6.1A	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 6.1.1A	[Command performed successfully]

Expected Sequence 6.1B (SEND SS, call forward unconditional, all bearers, successful, UCS2 text in Katakana)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND SS 6.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND SS 6.1.1
4	ME → USER	Display "ル"	[Character in Katakana]
5	ME → USS	REGISTER 6.1B
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 6.1B	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND SS 6.1.1B	[Command performed successfully]

PROACTIVE COMMAND: SEND SS 6.1.1

Logically:

Command details

Command number: 1

Command type: SEND SS

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha Identifier

Data coding scheme: UCS2 (16bit)

Text: "ル"

SS String

TON: International

NPI: "ISDN / telephone numbering plan"

SS string: "**21*01234567890123456789*10#"

Coding:

BER-TLV:	D0	20	81	03	01	11	00	82	02	81	83	85
	03	80	30	EB	89	10	91	AA	12	0A	21	43
	65	87	09	21	43	65	87	A9	01	FB

Same as cl 27.22.4.11.1.4.2 REGISTER 1.1A

Same as cl 27.22.4.11.1.4.2 REGISTER 1.1B

RELEASE COMPLETE (SS RETURN RESULT) 6.1A

Same as cl 27.22.4.11.1.4.2 RELEASE COMPLETE (SS RETURN RESULT) 1.1A

RELEASE COMPLETE (SS RETURN RESULT) 6.1B

Same as cl 27.22.4.11.1.4.2 RELEASE COMPLETE (SS RETURN RESULT) 1.1B

TERMINAL RESPONSE: SEND SS 6.1.1A

Same as cl 27.22.4.11.1.4.2 TERMINAL RESPONSE: SEND SS 1.1.1A

TERMINAL RESPONSE: SEND SS 6.1.1B

Same as cl 27.22.4.11.1.4.2 TERMINAL RESPONSE: SEND SS 1.1.1B

27.22.4.11.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.1.

27.22.4.12 SEND USSD

27.22.4.12.1 SEND USSD (normal)

27.22.4.12.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.12.1.2 Conformance requirement

The ME shall support the Proactive UICC: Send USSD facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.12, clause 6.6.11, clause 8.12.7, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.17, clause 8.31 and clause 6.5.

– TS 23.038 [7] clause 5

Additionally the ME shall support the UCS2 facility for the coding of the Cyrillic alphabet, as defined in: ISO/IEC 10646 [17].

27.22.4.12.1.3 Test purpose

To verify that the ME correctly translates and sends the unstructured supplementary service request indicated in the SEND USSD proactive UICC command to the USS.

To verify that the ME returns a TERMINAL RESPONSE command to the UICC indicating the status of the transmission of the USSD request and including a USSD result as a text string in the TERMINAL RESPONSE.

27.22.4.12.1.4 Method of test

27.22.4.12.1.4.1 Initial conditions

27.22.4.12.1.4.2 Procedure

Expected Sequence 1.1 (SEND USSD, 7-bit data, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 1.1.1
4	ME → USER	Display "7-bit USSD"
5	ME → USS	REGISTER 1.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.1	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 1.1.1

PROACTIVE COMMAND: SEND USSD 1.1.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "7-bit USSD"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV:	D0	50	81	03	01	12	00	82	02	81	83	85
	0A	37	2D	62	69	74	20	55	53	53	44	8A
	39	F0	41	E1	90	5⁸	34	1E	91	49	E5	92
	D9	74	3E	A1	51	E9	94	5A	B5	5E	B1	59
	6D	2B	2C	1E	93	CB	E6	33	3A	AD	5E	B3
	DB	EE	37	3C	2E	9F	D3	EB	F6	3B	3E	AF
	6F	C5	64	33	5A	CD	76	C3	E5	60

Logically (only USSD argument)

ProcessUnstructuredSS-Request ARGUMENT

USSD-DataCodingScheme:

– 7-bit default, no message class

USSD string:

– "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV

³4

RELEASE COMPLETE (SS RETURN RESULT) 1.1

Logically (only from USSD result):

ProcessUnstructuredSS-Request RETURN RESULT

USSD-DataCodingScheme:

– 7-bit default, no message class

USSD string:

– "USSD string received from SS"

Coding:

BER-TL^V	30	1E	04	01	F0	04	19	D5	E9	94	08	9A
	D3	E5	69	F7	19	24	2F	8F	CB	69	7B	99
	0C	32	CB	DF	6D	D0	74	0A

TERMINAL RESPONSE: SEND USSD 1.1.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Text String

Data coding scheme: 7-bit default, no message class

String: "USSD string received from SS"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	01
	00	8D	1A	00	D5	E9	94	08	9A	D3	E5
	69	F7	19	24	2F	8F	CB	69	7B	99	0C
	32	CB	DF	6D	D0	74	0A

Expected Sequence 1.2 (SEND USSD, 8-bit data, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 1.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 1.2.1
4	ME → USER	Display "8-bit USSD"
5	ME → USS	REGISTER 1.2
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.2	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 1.2.1

PROACTIVE COMMAND: SEND USSD 1.2.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "8-bit USSD"

USSD String

Data coding scheme: Uncompressed, no message class meaning, 8-bit data

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV:	D0	58	81	03	01	12	00	82	02	81	83	85
	0A	38	2D	62	69	74	20	55	53	53	44	8A
	41	44	41	42	43	44	45	46	47	48	49	4A
	4B	4C	4D	4E	4F	50	51	52	53	54	55	56
	57	58	59	5A	2D	61	62	63	64	65	66	67
	68	69	6A	6B	6C	6D	6E	6F	70	71	72	73
	74	75	76	77	78	79	7A	2D	31	32	33	34
	35	36	37	38	39	30

Logically (only USSD argument):

ProcessUnstructuredSS-Request ARGUMENT

USSD-DataCodingScheme:

– Uncompressed, no message class meaning, 8-bit data

USSD string:

– "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV	30	45	04	01	44	04	40	41	42	43	44	45
	46	47	48	49	4A	4B	4C	4D	4E	4F	50	51
	52	53	54	55	56	57	58	59	5A	2D	61	62
	63	64	65	66	67	68	69	6A	6B	6C	6D	6E
	6F	70	71	72	73	74	75	76	77	78	79	7A
	2D	31	32	33	34	35	36	37	38	39	30

RELEASE COMPLETE (SS RETURN RESULT) 1.2

Logically (only from USSD result):

ProcessUnstructuredSS-Request RETURN RESULT

USSD-DataCodingScheme:

– Uncompressed, no message class meaning, 8-bit data

USSD string:

– "USSD string received from SS"

Coding:

BER-TLV	30	21	04	01	44	04	1C	55	53	53	44	20
	73	74	72	69	6E	67	20	72	65	63	65	69
	76	65	64	20	66	72	6F	6D	20	53	53

TERMINAL RESPONSE: SEND USSD 1.2.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Text String

Data coding scheme: Uncompressed, no message class meaning, 8-bit data

String: "USSD string received from SS"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	01
	00	8D	1D	04	55	53	53	44	20	73	74
	72	69	6E	67	20	72	65	63	65	69	76
	65	64	20	66	72	6F	6D	20	53	53

Expected Sequence 1.3 (SEND USSD, UCS2 data, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 1.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 1.3.1
4	ME → USER	Display "UCS2 USSD"
5	ME → USS	REGISTER 1.3
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.3	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 1.3.1

PROACTIVE COMMAND: SEND USSD 1.3.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "UCS2 USSD"

USSD String

Data coding scheme: Uncompressed, no message class meaning, UCS2 (16 bit)

USSD string: "ЗДРАВСТВУЙТЕ" ("Hello" in Russian)

Coding:

BER-TLV:	D0	2F	81	03	01	12	00	82	02	81	83	85
	09	55	43	53	32	20	55	53	53	44	8A	19
	48	04	17	04	14	04	20	04	10	04	12	04
	21	04	22	04	12	04	23	04	19	04	22	04
	15

Logically (only USSD argument):

ProcessUnstructuredSS-Request ARGUMENT

USSD-DataCodingScheme:

– Uncompressed, no message class meaning, UCS2 (16 bit)

USSD string:

– "ЗДРАВСТВУЙТЕ" ("Hello" in Russian)

Coding:

BER-TLV	30	1D	04	01	48	04	18	04	17	04	14	04
	20	04	10	04	12	04	21	04	22	04	12	04
	23	04	19	04	22	04	15

RELEASE COMPLETE (SS RETURN RESULT) 1.3

Logically (only from USSD result):

ProcessUnstructuredSS-Request RETURN RESULT

USSD-DataCodingScheme:

– Uncompressed, no message class meaning, UCS2 (16 bit)

USSD string:

– "USSD string received from SS"

Coding:

BER-TLV	30	3D	04	01	48	04	38	00	55	00	53	00
	53	00	44	00	20	00	73	00	74	00	72	00
	69	00	6E	00	67	00	20	00	72	00	65	00
	63	00	65	00	69	00	76	00	65	00	64	00
	20	00	66	00	72	00	6F	00	6D	00	20	00
	53	00	53

TERMINAL RESPONSE: SEND USSD 1.3.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Text String

Data coding scheme: Uncompressed, no message class meaning, UCS2 (16 bit)

String: "USSD string received from SS"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	01
	00	8D	39	08	00	55	00	53	00	53	00
	44	00	20	00	73	00	74	00	72	00	69
	00	6E	00	67	00	20	00	72	00	65	00
	63	00	65	00	69	00	76	00	65	00	64
	00	20	00	66	00	72	00	6F	00	6D	00
	20	00	53	00	53

Expected Sequence 1.4 (SEND USSD, 7-bit data, unsuccessful (Return Error))

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 1.1.1
4	ME → USER	Display "7-bit USSD"
5	ME → USS	REGISTER 1.1
6	USS → ME	RELEASE COMPLETE (SS RETURN ERROR) 1.1	Return Error
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 1.4.1

RELEASE COMPLETE (SS RETURN ERROR) 1.1

Logically (only from Return Error code):

ProcessUnstructuredSS-Request RETURN ERROR

Return Error code:

– Unknown alphabet

Coding:

Coding

TERMINAL RESPONSE: SEND USSD 1.4.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: USSD Return Error

Additional information: "Unknown alphabet"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	02
	37	47

Expected Sequence 1.5 (SEND USSD, 7-bit data, unsuccessful (Reject))

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 1.1.1
4	ME → USER	Display "7-bit USSD"
5	ME → USS	REGISTER 1.1
6	USS → ME	RELEASE COMPLETE (SS REJECT) 1.1	Reject
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 1.5.1

RELEASE COMPLETE (SS REJECT) 1.1

Logically (only from Problem code):

ProcessUnstructuredSS-Request REJECT

Invoke Problem code:

– Mistyped parameter

Coding:

Coding

TERMINAL RESPONSE: SEND USSD 1.5.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: USSD Return Error

Additional information: "No specific cause can be given"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	02
	37	00

Expected Sequence 1.6 (SEND USSD, 256 octets, 7-bit data, successful, long alpha identifier)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 1.6.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 1.6.1
4	ME → USER	Display "once a RELEASE COMPLETE message containing the USSD Return Result message not containing an error has been received from the network, the ME shall inform the SIM that the command has"
5	ME → USS	REGISTER 1.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.1	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 1.1.1

PROACTIVE COMMAND: SEND USSD 1.6.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "once a RELEASE COMPLETE message containing the USSD Return Result message not containing an error has been received from the network, the ME shall inform the SIM that the command has"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV:	D0	81	FD	81	03	01	12	00	82	02	81	83
	85	81	B6	6F	6E	63	65	20	61	20	52	45
	4C	45	41	53	45	20	43	4F	4D	50	4C	45
	54	45	20	6D	65	73	73	61	67	65	20	63
	6F	6E	74	6¹	69	6^E	69	6E	67	20	74	68
	65	20	55	53	53	44	20	52	65	74	75	⁷2
	6E	20	52	65	73	75	6C	74	20	6D	65	73
	73	61	67	65	20	6E	6F	74	20	63	6F	6E
	74	61	69	6E	69	6E	67	20	61	6E	20	65
	72	72	6F	72	20	68	61	73	20	62	65	65
	6E	20	72	65	63	65	69	76	65	64	20	66
	72	6F	6D	20	74	68	65	20	6E	65	74	77
	6F	72	6B	2C	20	74	68	65	20	4D	45	20
	73	68	61	6C	6C	20	69	6E	66	6F	72	6D
	20	74	68	65	20	53	49	4D	20	74	68	61
	74	20	74	68	65	20	63	6F	6D	6D	61	6E
	64	20	68	61	73	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60

Expected Sequence 1.7 (SEND USSD, 7-bit data, successful, no alpha identifier)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 1.7.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 1.7.1
4	ME → USER	Optionally display an informative message
5	ME → USS	REGISTER 1.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.1	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 1.1.1

PROACTIVE COMMAND: SEND USSD 1.7.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV:

5⁸

Expected Sequence 1.8 (SEND USSD, 7-bit data, successful, null length alpha identifier)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 1.8.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 1.8.1
4	ME → USER	the ME should not give any information to the user on the fact that the ME is sending a USSD request
5	ME → USS	REGISTER 1.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 1.1	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 1.1.1

PROACTIVE COMMAND: SEND USSD 1.8.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: ""

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV:	D0	46	81	03	01	12	00	82	02	81	83	85
	00	8A	39	F0	41	E1	90	5⁸	34	1E	91	49
	E5	92	D9	74	3E	A1	51	E9	94	5A	B5	5E
	B1	59	6D	2B	2C	1E	93	CB	E6	33	3A	AD
	5E	B3	DB	EE	37	3C	2E	9F	D3	EB	F6	3B
	3E	AF	6F	C5	64	33	5A	CD	76	C3	E5	60

27.22.4.12.1.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1 – 1.8.

27.22.4.12.2 SEND USSD (Icon support)

27.22.4.12.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.12.2.2 Conformance requirement

27.22.4.12.2.3 Test purpose

To verify that the ME displays the text contained in the SEND USSD proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.12.2.4 Method of test

27.22.4.12.2.4.1 Initial conditions

The ME is connected to the USIM Simulator and to the USS. Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS

The elementary files are coded as Toolkit default.

27.22.4.12.2.4.2 Procedure

Expected Sequence 2.1A (SEND USSD, 7-bit data, successful, basic icon self explanatory, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 2.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 2.1.1	[BASIC-ICON, self-explanatory]
4	ME → USER	Display BASIC ICON
5	ME → USS	REGISTER 2.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 2.1	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 2.1.1A	[Command performed successfully]

PROACTIVE COMMAND: SEND USSD 2.1.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Basic Icon"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Icon Identifier:

Icon qualifier: icon is self-explanatory

Icon Identifier: record 1 in EF_(IMG)

Coding:

BER-TLV:	D0	54	81	03	01	12	00	82	02	81	83	85
	0A	42	61	73	69	63	20	49	63	6F	6E	8A
	39	F0	41	E1	90	5⁸	34	1E	91	49	E5	92
	D9	74	3E	A1	51	E9	94	5A	B5	5E	B1	59
	6D	2B	2C	1E	93	CB	E6	33	3A	AD	5E	B3
	DB	EE	37	3C	2E	9F	D3	EB	F6	3B	3E	AF
	6F	C5	64	33	5A	CD	76	C3	E⁵	60	9E	02
	00	01

Logically (only USSD argument)

ProcessUnstructuredSS-Request ARGUMENT

USSD-DataCodingScheme:

– 7-bit default, no message class

USSD string:

– "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV

³4

RELEASE COMPLETE (SS RETURN RESULT) 2.1

Logically (only from USSD result):

ProcessUnstructuredSS-Request RETURN RESULT

USSD-DataCodingScheme:

– 7-bit default, no message class

USSD string:

– "USSD string received from SS"

Coding:

BER-TLV	30	1E	04	01	F0	04	19	D5	E9	94	08	9A
	D3	E5	69	F7	19	24	2F	8F	CB	69	7B	99
	0C	32	CB	DF	6D	D0	74	0A

TERMINAL RESPONSE: SEND USSD 2.1.1A

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Text String

Data coding scheme: 7-bit default, no message class

String: "USSD string received from SS"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	01
	00	8D	1A	00	D5	E9	94	08	9A	D3	E5
	69	F7	19	24	2F	8F	CB	69	7B	99	0C
	32	CB	DF	6D	D0	74	0A

Expected Sequence 2.1B (SEND USSD, 7-bit data, successful, basic icon self explanatory, requested icon could not be displayed)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 2.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 2.1.1	[BASIC-ICON, self-explanatory]
4	ME → USER	Display "Basic Icon" without the icon
5	ME → USS	REGISTER 2.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 2.1	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 2.1.1B	[Command performed but requested icon could not be displayed]

TERMINAL RESPONSE: SEND USSD 2.1.1B

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully, but requested icon could not be displayed

Text String

Data coding scheme: 7-bit default, no message class

String: "USSD string received from SS"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	01
	04	8D	1A	00	D5	E9	94	08	9A	D3	E5
	69	F7	19	24	2F	8F	CB	69	7B	99	0C
	32	CB	DF	6D	D0	74	0A

Expected Sequence 2.2 (SEND USSD, 7-bit data, successful, colour icon self explanatory)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 2.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 2.2.1	[COLOUR-ICON, self-explanatory]
4	ME → USER	Display COLOUR-ICON or May give information to user concerning what is happening
5	ME → USS	REGISTER 2.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 2.1	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 2.1.1A or TERMINAL RESPONSE: SEND USSD 2.1.1B	[Command performed successfully] or [Command performed but requested icon could not be displayed]

PROACTIVE COMMAND: SEND USSD 2.2.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Color Icon"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Icon Identifier:

Icon qualifier: icon is self-explanatory

Icon Identifier: record 2 in EF_(IMG)

Coding:

BER-TLV:	D0	54	81	03	01	12	00	82	02	81	83	85
	0A	43	6F	6C	6F	72	20	49	63	6F	6E	8A
	39	F0	41	E1	90	5⁸	34	1E	91	49	E5	92
	D9	74	3E	A1	51	E9	94	5A	B5	5E	B1	59
	6D	2B	2C	1E	93	CB	E6	33	3A	AD	5E	B3
	DB	EE	37	3C	2E	9F	D3	EB	F6	3B	3E	AF
	6F	C5	64	33	5A	CD	76	C3	E⁵	60	9E	02
	00	02

Expected Sequence 2.3A (SEND USSD, 7-bit data, successful, basic icon non self-explanatory, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 2.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 2.3.1	[BASIC-ICON, non self-explanatory]
4	ME → USER	Display "Basic Icon" and BASIC-ICON
5	ME → USS	REGISTER 2.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 2.1	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 2.1.1A	[Command performed successfully]

PROACTIVE COMMAND: SEND USSD 2.3.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Basic Icon"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Icon Identifier

Icon qualifier: icon is non self-explanatory

Icon Identifier: record 1 in EF_(IMG)

Coding:

BER-TLV:	D0	54	81	03	01	12	00	82	02	81	83	85
	0A	42	61	73	69	63	20	49	63	6F	6E	8A
	39	F0	41	E1	90	58	34	1E	91	49	E5	92
	D9	74	3E	A1	51	E9	94	5A	B5	5E	B1	59
	6D	2B	2C	1E	93	CB	E6	33	3A	AD	5E	B3
	DB	EE	37	3C	2E	9F	D3	EB	F6	3B	3E	AF
	6F	C5	64	33	5A	CD	76	C3	E⁵	60	9E	02
	01	01

Expected Sequence 2.3B (SEND USSD, 7-bit data, successful, basic icon non self-explanatory, requested icon could not be displayed)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 2.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 2.3.1	[BASIC-ICON, non self-explanatory]
4	ME → USER	Display "Basic Icon" without the icon
5	ME → USS	REGISTER 2.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 2.1	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 2.1.1B	[Command performed but requested icon could not be displayed]

Expected Sequence 2.4 (SEND USSD, 7-bit data, basic icon non self-explanatory, no alpha identifier presented)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 2.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 2.4.1	[BASIC-ICON, non self-explanatory]
4	ME → UICC	TERMINAL RESPONSE: SEND USSD 2.4.1	[Command data not understood by ME]

PROACTIVE COMMAND: SEND USSD 2.4.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-

Icon Identifier

Icon qualifier: icon is non self-explanatory

Icon Identifier: record 1 in EF_(IMG)

Coding:

BER-TLV:	D0	48	81	03	01	12	00	82	02	81	83	8A
	39	F0	41	E1	90	58	34	1E	91	49	E5	92
	D9	74	3E	A1	51	E9	94	5A	B5	5E	B1	59
	6D	2B	2C	1E	93	CB	E6	33	3A	AD	5E	B3
	DB	EE	37	3C	2E	9F	D3	EB	F6	3B	3E	AF
	6F	C5	64	33	5A	CD	76	C3	E⁵	60	9E	02
	01	01

TERMINAL RESPONSE: SEND USSD 2.4.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command data not understood by ME

Coding:

BER-TLV:

27.22.4.12.2.5 Test requirement

The ME shall operate in the manner defined in expected sequences 2.1 – 2.4.

27.22.4.12.3 SEND USSD (UCS2 display in Cyrillic)

27.22.4.12.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.12.3.2 Conformance requirement

The ME shall support the Proactive UICC: Send USSD facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.12, clause 6.6.11, clause 8.12.7, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.17, clause 8.31 and clause 6.5.

– TS 23.038 [7] clause 5

Additionally the ME shall support the UCS2 facility for the coding of the Cyrillic alphabet, as defined in: ISO/IEC 10646 [17].

27.22.4.12.3.3 Test purpose

To verify that the ME displays the UCS2 text contained in the SEND USSD proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.12.3.4 Method of test

27.22.4.12.3.4.1 Initial conditions

27.22.4.12.3.4.2 Procedure

Expected Sequence 3.1 (SEND USSD, 7-bit data, successful, UCS2 text in Cyrillic)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 3.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 3.1.1
4	ME → USER	Display "ЗДРАВСТВУЙТЕ"	["Hello" in Russian]
5	ME → USS	REGISTER 3.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 3.1	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 3.1.1	[Command performed successfully]

PROACTIVE COMMAND: SEND USSD 3.1.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha Identifier

Data coding scheme: UCS2 (16bit)

Text: "ЗДРАВСТВУЙТЕ"

USSD String

Data coding scheme: 7-bit default, no message class

USSD String: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-

Coding:

BER-TLV:	D0	5F	81	03	01	12	00	82	02	81	83	85
	19	80	04	17	04	14	04	20	04	10	04	12
	04	21	04	22	04	12	04	23	04	19	04	22
	04	15	8A	39	F0	41	E1	90	58	34	1E	91
	49	E5	92	D9	74	3E	A1	51	E9	94	5A	B5
	5E	B1	59	6D	2B	2C	1E	93	CB	E6	33	3A
	AD	5E	B3	DB	EE	37	3C	2E	9F	D3	EB	F6
	3B	3E	AF	6F	C5	64	33	5A	CD	76	C3	E5
	60

Logically (only USSD argument)

ProcessUnstructuredSS-Request ARGUMENT

USSD-DataCodingScheme:

– 7-bit default, no message class

USSD String:

– "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV

³4

RELEASE COMPLETE (SS RETURN RESULT) 3.1

Logically (only from USSD result):

ProcessUnstructuredSS-Request RETURN RESULT

USSD-DataCodingScheme:

– 7-bit default, no message class

USSD String:

– "USSD string received from SS"

Coding:

BER-TL^V	30	1E	04	01	F0	04	19	D5	E9	94	08	9A
	D3	E5	69	F7	19	24	2F	8F	CB	69	7B	99
	0C	32	CB	DF	6D	D0	74	0A

TERMINAL RESPONSE: SEND USSD 3.1.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Text String

Data coding scheme: 7-bit default, no message class

String: "USSD string received from SS"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	01
	00	8D	1A	00	D5	E9	94	08	9A	D3	E5
	69	F7	19	24	2F	8F	CB	69	7B	99	0C
	32	CB	DF	6D	D0	74	0A

27.22.4.12.3.5 Test requirement

The ME shall operate in the manner defined in expected sequence 3.1.

27.22.4.12.4 SEND USSD (support of Text Attribute)

27.22.4.12.4.1 SEND USSD (support of Text Attribute – Left Alignment)

27.22.4.12.4.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.12.4.1.2 Conformance requirement

The terminal shall support the Proactive UICC: Send USSD facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.12, clause 6.6.11, clause 8.12.7, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.17, clause 8.31 and clause 6.5.

27.22.4.12.4.1.3 Test purpose

To verify that the ME displays the alpha identifier according to the left alignment text attribute configuration in the SEND USSD proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.12.4.1.4 Method of test

27.22.4.12.4.1.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the terminal shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.12.4.1.4.2 Procedure

Expected Sequence 4.1 (SEND USSD, 7-bit data, successful, with Text Attribute – Left Alignment)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.1.1
4	ME → USER	Display "Text Attribute 1"	[Alpha identifier is displayed with left alignment]
5	ME → USS	REGISTER 4.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.1.1
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.1.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.1.2
11	ME → USER	Display "Text Attribute 2"	[Alpha identifier is displayed without left alignment. Remark: If left alignment is the ME’s default alignment as declared in table A.2/13, no alignment change will take place]
12	ME → USS	REGISTER 4.1
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
14	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.1.1

PROACTIVE COMMAND: SEND USSD 4.1.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	5C	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60	D0	04	00	10	00	B4

PROACTIVE COMMAND: SEND USSD 4.1.2

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV:	D0	56	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60

Logically (only USSD argument)

ProcessUnstructuredSS-Request ARGUMENT

USSD-DataCodingScheme:

– 7-bit default, no message class

USSD string:

– "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

Coding

³4

RELEASE COMPLETE (SS RETURN RESULT) 4.1

Logically (only from USSD result):

ProcessUnstructuredSS-Request RETURN RESULT

USSD-DataCodingScheme:

– 7-bit default, no message class

USSD string:

– "USSD string received from SS"

Coding:

BER-TLV	30	1E	04	01	F0	04	19	D5	E9	94	08	9A
	D3	E5	69	F7	19	24	2F	8F	CB	69	7B	99
	0C	32	CB	DF	6D	D0	74	0A

TERMINAL RESPONSE: SEND USSD 4.1.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Text String

Data coding scheme: 7-bit default, no message class

String: "USSD string received from SS"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	01
	00	8D	1A	00	D5	E9	94	08	9A	D3	E5
	69	F7	19	24	2F	8F	CB	69	7B	99	0C
	32	CB	DF	6D	D0	74	0A

27.22.4.12.4.1.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.1.

27.22.4.12.4.2 SEND USSD (support of Text Attribute – Center Alignment)

27.22.4.12.4.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.12.4.2.2 Conformance requirement

The terminal shall support the Proactive UICC: Send USSD facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.12, clause 6.6.11, clause 8.12.7, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.17, clause 8.31 and clause 6.5.

27.22.4.12.4.2.3 Test purpose

To verify that the ME displays the alpha identifier according to the center alignment text attribute configuration in the SEND USSD proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.12.4.2.4 Method of test

27.22.4.12.4.2.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the terminal shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.12.4.2.4.2 Procedure

Expected Sequence 4.2 (SEND USSD, 7-bit data, successful, with Text Attribute – Center Alignment)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.2.1
4	ME → USER	Display "Text Attribute 1"	[Alpha identifier is displayed with center alignment]
5	ME → USS	REGISTER 4.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.2.1
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.2.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.2.2
11	ME → USER	Display "Text Attribute 2"	[Alpha identifier is displayed without center alignment. Remark: If center alignment is the ME’s default alignment as declared in table A.2/13, no alignment change will take place]
12	ME → USS	REGISTER 4.1
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
14	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.2.1

PROACTIVE COMMAND: SEND USSD 4.2.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Center Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	5C	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60	D0	04	00	10	01	B4

PROACTIVE COMMAND: SEND USSD 4.2.2

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV:	D0	56	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60

TERMINAL RESPONSE: SEND USSD 4.2.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Text String

Data coding scheme: 7-bit default, no message class

String: "USSD string received from SS"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	01
	00	8D	1A	00	D5	E9	94	08	9A	D3	E5
	69	F7	19	24	2F	8F	CB	69	7B	99	0C
	32	CB	DF	6D	D0	74	0A

27.22.4.12.4.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.2.

27.22.4.12.4.3 SEND USSD (support of Text Attribute – Right Alignment)

27.22.4.12.4.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.12.4.3.2 Conformance requirement

The terminal shall support the Proactive UICC: Send USSD facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.12, clause 6.6.11, clause 8.12.7, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.17, clause 8.31 and clause 6.5.

27.22.4.12.4.3.3 Test purpose

To verify that the ME displays the alpha identifier according to the right alignment text attribute configuration in the SEND USSD proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.12.4.3.4 Method of test

27.22.4.12.4.3.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the terminal shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.12.4.3.4.2 Procedure

Expected Sequence 4.3 (SEND USSD, 7-bit data, successful, with Text Attribute – Right Alignment)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.3.1
4	ME → USER	Display "Text Attribute 1"	[Alpha identifier is displayed with right alignment]
5	ME → USS	REGISTER 4.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.3.1
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.3.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.3.2
11	ME → USER	Display "Text Attribute 2"	[Alpha identifier is displayed without right alignment. Remark: If right alignment is the ME’s default alignment as declared in table A.2/13, no alignment change will take place]
12	ME → USS	REGISTER 4.1
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
14	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.3.1

PROACTIVE COMMAND: SEND USSD 4.3.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Right Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	5C	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60	D0	04	00	10	02	B4

PROACTIVE COMMAND: SEND USSD 4.3.2

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV:	D0	56	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60

TERMINAL RESPONSE: SEND USSD 4.3.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Text String

Data coding scheme: 7-bit default, no message class

String: "USSD string received from SS"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	01
	00	8D	1A	00	D5	E9	94	08	9A	D3	E5
	69	F7	19	24	2F	8F	CB	69	7B	99	0C
	32	CB	DF	6D	D0	74	0A

27.22.4.12.4.3.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.3.

27.22.4.12.4.4 SEND USSD (support of Text Attribute – Large Font Size)

27.22.4.12.4.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.12.4.4.2 Conformance requirement

The terminal shall support the Proactive UICC: Send USSD facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.12, clause 6.6.11, clause 8.12.7, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.17, clause 8.31 and clause 6.5.

27.22.4.12.4.4.3 Test purpose

To verify that the ME displays the alpha identifier according to the large font size text attribute configuration in the SEND USSD proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.12.4.4.4 Method of test

27.22.4.12.4.4.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the terminal shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.12.4.4.4.2 Procedure

Expected Sequence 4.4 (SEND USSD, 7-bit data, successful, with Text Attribute – Large Font Size)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.4.1
4	ME → USER	Display "Text Attribute 1"	[Alpha identifier is displayed with large font size]
5	ME → USS	REGISTER 4.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.4.1
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.4.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.4.2
11	ME → USER	Display "Text Attribute 2"	[Alpha identifier is displayed with normal font size]
12	ME → USS	REGISTER 4.1
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
14	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.4.1
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.4.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.4.1
18	ME → USER	Display "Text Attribute 1"	[Alpha identifier is displayed with large font size]
19	ME → USS	REGISTER 4.1
20	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
21	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.4.1
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.4.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.4.3
25	ME → USER	Display "Text Attribute 3"	[Alpha identifier is displayed with normal font size]
26	ME → USS	REGISTER 4.1
27	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
28	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.4.1

PROACTIVE COMMAND: SEND USSD 4.4.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Large Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	5C	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60	D0	04	00	10	04	B4

PROACTIVE COMMAND: SEND USSD 4.4.2

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	5C	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60	D0	04	00	10	00	B4

PROACTIVE COMMAND: SEND USSD 4.4.3

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 3"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV:	D0	56	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	33	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60

TERMINAL RESPONSE: SEND USSD 4.4.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Text String

Data coding scheme: 7-bit default, no message class

String: "USSD string received from SS"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	01
	00	8D	1A	00	D5	E9	94	08	9A	D3	E5
	69	F7	19	24	2F	8F	CB	69	7B	99	0C
	32	CB	DF	6D	D0	74	0A

27.22.4.12.4.4.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.4.

27.22.4.12.4.5 SEND USSD (support of Text Attribute – Small Font Size)

27.22.4.12.4.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.12.4.5.2 Conformance requirement

The terminal shall support the Proactive UICC: Send USSD facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.12, clause 6.6.11, clause 8.12.7, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.17, clause 8.31 and clause 6.5.

27.22.4.12.4.5.3 Test purpose

To verify that the ME displays the alpha identifier according to the small font size text attribute configuration in the SEND USSD proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.12.4.5.4 Method of test

27.22.4.12.4.5.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the terminal shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.12.4.5.4.2 Procedure

Expected Sequence 4.5 (SEND USSD, 7-bit data, successful, with Text Attribute – Small Font Size)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.5.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.5.1
4	ME → USER	Display "Text Attribute 1"	[Alpha identifier is displayed with small font size]
5	ME → USS	REGISTER 4.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.5.1
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.5.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.5.2
11	ME → USER	Display "Text Attribute 2"	[Alpha identifier is displayed with normal font size]
12	ME → USS	REGISTER 4.1
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
14	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.5.1
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.5.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.5.1
18	ME → USER	Display "Text Attribute 1"	[Alpha identifier is displayed with small font size]
19	ME → USS	REGISTER 4.1
20	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
21	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.5.1
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.5.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.5.3
25	ME → USER	Display "Text Attribute 3"	[Alpha identifier is displayed with normal font size]
26	ME → USS	REGISTER 4.1
27	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
28	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.5.1

PROACTIVE COMMAND: SEND USSD 4.5.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Small Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	5C	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60	D0	04	00	10	08	B4

PROACTIVE COMMAND: SEND USSD 4.5.2

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	5C	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60	D0	04	00	10	00	B4

PROACTIVE COMMAND: SEND USSD 4.5.3

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 3"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV:	D0	56	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	33	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60

TERMINAL RESPONSE: SEND USSD 4.5.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Text String

Data coding scheme: 7-bit default, no message class

String: "USSD string received from SS"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	01
	00	8D	1A	00	D5	E9	94	08	9A	D3	E5
	69	F7	19	24	2F	8F	CB	69	7B	99	0C
	32	CB	DF	6D	D0	74	0A

27.22.4.12.4.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.5.

27.22.4.12.4.6 SEND USSD (support of Text Attribute – Bold On)

27.22.4.12.4.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.12.4.6.2 Conformance requirement

The terminal shall support the Proactive UICC: Send USSD facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.12, clause 6.6.11, clause 8.12.7, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.17, clause 8.31 and clause 6.5.

27.22.4.12.4.6.3 Test purpose

To verify that the ME displays the alpha identifier according to the bold text attribute configuration in the SEND USSD proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.12.4.6.4 Method of test

27.22.4.12.4.6.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the terminal shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.12.4.6.4.2 Procedure

Expected Sequence 4.6 (SEND USSD, 7-bit data, successful, with Text Attribute – Bold On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.6.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.6.1
4	ME → USER	Display "Text Attribute 1"	[Alpha identifier is displayed with bold on]
5	ME → USS	REGISTER 4.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.6.1
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.6.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.6.2
11	ME → USER	Display "Text Attribute 2"	[Alpha identifier is displayed with bold off]
12	ME → USS	REGISTER 4.1
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
14	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.6.1
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.6.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.6.1
18	ME → USER	Display "Text Attribute 1"	[Alpha identifier is displayed with bold on]
19	ME → USS	REGISTER 4.1
20	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
21	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.6.1
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.6.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.6.3
25	ME → USER	Display "Text Attribute 3"	[Alpha identifier is displayed with bold off]
26	ME → USS	REGISTER 4.1
27	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
28	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.6.1

PROACTIVE COMMAND: SEND USSD 4.6.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold On, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	5C	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60	D0	04	00	10	10	B4

PROACTIVE COMMAND: SEND USSD 4.6.2

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	5C	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60	D0	04	00	10	00	B4

PROACTIVE COMMAND: SEND USSD 4.6.3

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 3"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV:	D0	56	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	33	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60

TERMINAL RESPONSE: SEND USSD 4.6.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Text String

Data coding scheme: 7-bit default, no message class

String: "USSD string received from SS"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	01
	00	8D	1A	00	D5	E9	94	08	9A	D3	E5
	69	F7	19	24	2F	8F	CB	69	7B	99	0C
	32	CB	DF	6D	D0	74	0A

27.22.4.12.4.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.6.

27.22.4.12.4.7 SEND USSD (support of Text Attribute – Italic On)

27.22.4.12.4.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.12.4.7.2 Conformance requirement

The terminal shall support the Proactive UICC: Send USSD facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.12, clause 6.6.11, clause 8.12.7, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.17, clause 8.31 and clause 6.5.

27.22.4.12.4.7.3 Test purpose

To verify that the ME displays the alpha identifier according to the italic text attribute configuration in the SEND USSD proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.12.4.7.4 Method of test

27.22.4.12.4.7.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the terminal shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.12.4.7.4.2 Procedure

Expected Sequence 4.7 (SEND USSD, 7-bit data, successful, with Text Attribute – Italic On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.7.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.7.1
4	ME → USER	Display "Text Attribute 1"	[Alpha identifier is displayed with italic on]
5	ME → USS	REGISTER 4.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.7.1
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.7.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.7.2
11	ME → USER	Display "Text Attribute 2"	[Alpha identifier is displayed with italic off]
12	ME → USS	REGISTER 4.1
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
14	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.7.1
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.7.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.7.1
18	ME → USER	Display "Text Attribute 1"	[Alpha identifier is displayed with italic on]
19	ME → USS	REGISTER 4.1
20	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
21	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.7.1
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.7.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.7.3
25	ME → USER	Display "Text Attribute 3"	[Alpha identifier is displayed with italic off]
26	ME → USS	REGISTER 4.1
27	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
28	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.7.1

PROACTIVE COMMAND: SEND USSD 4.7.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic On, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	5C	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60	D0	04	00	10	20	B4

PROACTIVE COMMAND: SEND USSD 4.7.2

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	5C	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60	D0	04	00	10	00	B4

PROACTIVE COMMAND: SEND USSD 4.7.3

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 3"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV:	D0	56	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	33	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60

TERMINAL RESPONSE: SEND USSD 4.7.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Text String

Data coding scheme: 7-bit default, no message class

String: "USSD string received from SS"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	01
	00	8D	1A	00	D5	E9	94	08	9A	D3	E5
	69	F7	19	24	2F	8F	CB	69	7B	99	0C
	32	CB	DF	6D	D0	74	0A

27.22.4.12.4.7.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.7.

27.22.4.12.4.8 SEND USSD (support of Text Attribute – Underline On)

27.22.4.12.4.8.1 Definition and applicability

See clause 3.2.2.

27.22.4.12.4.8.2 Conformance requirement

The terminal shall support the Proactive UICC: Send USSD facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.12, clause 6.6.11, clause 8.12.7, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.17, clause 8.31 and clause 6.5.

27.22.4.12.4.8.3 Test purpose

To verify that the ME displays the alpha identifier according to the underline text attribute configuration in the SEND USSD proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.12.4.8.4 Method of test

27.22.4.12.4.8.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the terminal shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.12.4.8.4.2 Procedure

Expected Sequence 4.8 (SEND USSD, 7-bit data, successful, with Text Attribute – Underline On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.8.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.8.1
4	ME → USER	Display "Text Attribute 1"	[Alpha identifier is displayed with underline on]
5	ME → USS	REGISTER 4.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.8.1
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.8.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.8.2
11	ME → USER	Display "Text Attribute 2"	[Alpha identifier is displayed with underline off]
12	ME → USS	REGISTER 4.1
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
14	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.8.1
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.8.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.8.1
18	ME → USER	Display "Text Attribute 1"	[Alpha identifier is displayed with underline on]
19	ME → USS	REGISTER 4.1
20	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
21	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.8.1
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.8.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.8.3
25	ME → USER	Display "Text Attribute 3"	[Alpha identifier is displayed with underline off]
26	ME → USS	REGISTER 4.1
27	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
28	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.8.1

PROACTIVE COMMAND: SEND USSD 4.8.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline On, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	5C	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60	D0	04	00	10	40	B4

PROACTIVE COMMAND: SEND USSD 4.8.2

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	5C	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60	D0	04	00	10	00	B4

PROACTIVE COMMAND: SEND USSD 4.8.3

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 3"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV:	D0	56	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	33	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60

TERMINAL RESPONSE: SEND USSD 4.8.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Text String

Data coding scheme: 7-bit default, no message class

String: "USSD string received from SS"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	01
	00	8D	1A	00	D5	E9	94	08	9A	D3	E5
	69	F7	19	24	2F	8F	CB	69	7B	99	0C
	32	CB	DF	6D	D0	74	0A

27.22.4.12.4.8.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.8.

27.22.4.12.4.9 SEND USSD (support of Text Attribute – Strikethrough On)

27.22.4.12.4.9.1 Definition and applicability

See clause 3.2.2.

27.22.4.12.4.9.2 Conformance requirement

The terminal shall support the Proactive UICC: Send USSD facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.12, clause 6.6.11, clause 8.12.7, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.17, clause 8.31 and clause 6.5.

27.22.4.12.4.9.3 Test purpose

To verify that the ME displays the alpha identifier according to the strikethrough text attribute configuration in the SEND USSD proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.12.4.9.4 Method of test

27.22.4.12.4.9.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the terminal shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.12.4.9.4.2 Procedure

Expected Sequence 4.9 (SEND USSD, 7-bit data, successful, with Text Attribute – Strikethrough On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.9.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.9.1
4	ME → USER	Display "Text Attribute 1"	[Alpha identifier is displayed with strikethrough on]
5	ME → USS	REGISTER 4.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.9.1
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.9.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.9.2
11	ME → USER	Display "Text Attribute 2"	[Alpha identifier is displayed with strikethrough off]
12	ME → USS	REGISTER 4.1
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
14	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.9.1
15	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.9.1
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.9.1
18	ME → USER	Display "Text Attribute 1"	[Alpha identifier is displayed with strikethrough on]
19	ME → USS	REGISTER 4.1
20	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
21	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.9.1
22	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.9.3
23	ME → UICC	FETCH
24	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.9.3
25	ME → USER	Display "Text Attribute 3"	[Alpha identifier is displayed with strikethrough off]
26	ME → USS	REGISTER 4.1
27	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
28	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.9.1

PROACTIVE COMMAND: SEND USSD 4.9.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough On

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	5C	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60	D0	04	00	10	80	B4

PROACTIVE COMMAND: SEND USSD 4.9.2

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	5C	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60	D0	04	00	10	00	B4

PROACTIVE COMMAND: SEND USSD 4.9.3

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 3"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV:	D0	56	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	33	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60

TERMINAL RESPONSE: SEND USSD 4.9.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Text String

Data coding scheme: 7-bit default, no message class

String: "USSD string received from SS"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	01
	00	8D	1A	00	D5	E9	94	08	9A	D3	E5
	69	F7	19	24	2F	8F	CB	69	7B	99	0C
	32	CB	DF	6D	D0	74	0A

27.22.4.12.4.9.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.9.

27.22.4.12.4.10 SEND USSD (support of Text Attribute – Foreground and Background Colour)

27.22.4.12.4.10.1 Definition and applicability

See clause 3.2.2.

27.22.4.12.4.10.2 Conformance requirement

The terminal shall support the Proactive UICC: Send USSD facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.12, clause 6.6.11, clause 8.12.7, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.17, clause 8.31 and clause 6.5.

27.22.4.12.4.10.3 Test purpose

To verify that the ME displays the alpha identifier according to the foreground and background colour text attribute configuration in the SEND USSD proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.12.4.10.4 Method of test

27.22.4.12.4.10.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.

The elementary files are coded as UICC default. Prior to this test the terminal shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.12.4.10.4.2 Procedure

Expected Sequence 4.10 (SEND USSD, 7-bit data, successful, with Text Attribute – Foreground and Background Colour)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.10.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.10.1
4	ME → USER	Display "Text Attribute 1"	[Message shall be formatted with foreground and background colour according to text attribute configuration]
5	ME → USS	REGISTER 4.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.10.1
8	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 4.10.2
9	ME → UICC	FETCH
10	UICC → ME	PROACTIVE COMMAND: SEND USSD 4.10.2
11	ME → USER	Display "Text Attribute 2"	[Message shall be formatted with ME’s default foreground and background colour]
12	ME → USS	REGISTER 4.1
13	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 4.1	["USSD string received from SS"]
14	ME → UICC	TERMINAL RESPONSE: SEND USSD 4.10.1

PROACTIVE COMMAND: SEND USSD 4.10.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 1"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	5C	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	31	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60	D0	04	00	10	00	B4

PROACTIVE COMMAND: SEND USSD 4.10.2

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Text Attribute 2"

USSD String

Data coding scheme: 7-bit default, no message class

USSD string: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV:	D0	56	81	03	01	12	00	82	02	81	83	85
	10	54	65	78	74	20	41	74	74	72	69	62
	75	74	65	20	32	8A	39	F0	41	E1	90	58
	34	1E	91	49	E5	92	D9	74	3E	A1	51	E9
	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB
	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F
	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD
	76	C3	E5	60

TERMINAL RESPONSE: SEND USSD 4.10.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Text String

Data coding scheme: 7-bit default, no message class

String: "USSD string received from SS"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	01
	00	8D	1A	00	D5	E9	94	08	9A	D3	E5
	69	F7	19	24	2F	8F	CB	69	7B	99	0C
	32	CB	DF	6D	D0	74	0A

27.22.4.12.4.10.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.10.

27.22.4.12.5 SEND USSD (UCS2 display in Chinese)

27.22.4.12.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.12.5.2 Conformance requirement

The ME shall support the Proactive UICC: Send USSD facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.12, clause 6.6.11, clause 8.12.7, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.17, clause 8.31 and clause 6.5.

– TS 23.038 [7] clause 5

Additionally the ME shall support the UCS2 facility for the coding of the Chinese characters, as defined in: ISO/IEC 10646 [17].

27.22.4.12.5.3 Test purpose

To verify that the ME displays the UCS2 text contained in the SEND USSD proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.12.5.4 Method of test

27.22.4.12.5.4.1 Initial conditions

27.22.4.12.5.4.2 Procedure

Expected Sequence 5.1 (SEND USSD, 7-bit data, successful, UCS2 text in Chinese)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 5.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 5.1.1
4	ME → USER	Display "你好"	["Hello" in Chinese]
5	ME → USS	REGISTER 5.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 5.1	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 5.1.1	[Command performed successfully]

PROACTIVE COMMAND: SEND USSD 5.1.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha Identifier

Data coding scheme: UCS2 (16bit)

Text: "你好"

USSD String

Data coding scheme: 7-bit default, no message class

USSD String: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV:	D0	4B	81	03	01	12	00	82	02	81	83	85
	05	80	4F	60	59	7D	8A	39	F0	41	E1	90
	58	34	1E	91	49	E5	92	D9	74	3E	A1	51
	E9	94	5A	B5	5E	B1	59	6D	2B	2C	1E	93
	CB	E6	33	3A	AD	5E	B3	DB	EE	37	3C	2E
	9F	D3	EB	F6	3B	3E	AF	6F	C5	64	33	5A
	CD	76	C3	E5	60

Logically (only USSD argument)

ProcessUnstructuredSS-Request ARGUMENT

USSD-DataCodingScheme:

– 7-bit default, no message class

USSD String:

– "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

Coding

RELEASE COMPLETE (SS RETURN RESULT) 5.1

Logically (only from USSD result):

ProcessUnstructuredSS-Request RETURN RESULT

USSD-DataCodingScheme:

– 7-bit default, no message class

USSD String:

– "USSD string received from SS"

Coding:

Coding	30	1E	04	01	00	04	19	D5	E9	94	08	9A
	D3	E5	69	F7	19	24	2F	8F	CB	69	7B	99
	0C	32	CB	DF	6D	D0	74	0A

TERMINAL RESPONSE: SEND USSD 5.1.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Text String

Data coding scheme: 7-bit default, no message class

String: "USSD string received from SS"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	01
	00	8D	1A	00	D5	E9	94	08	9A	D3	E5
	69	F7	19	24	2F	8F	CB	69	7B	99	0C
	32	CB	DF	6D	D0	74	0A

27.22.4.12.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 5.1.

27.22.4.12.6 SEND USSD (UCS2 display in Katakana)

27.22.4.12.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.12.6.2 Conformance requirement

The ME shall support the Proactive UICC: Send USSD facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.12, clause 6.6.11, clause 8.12.7, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.17, clause 8.31 and clause 6.5.

– TS 23.038 [7] clause 5

Additionally the ME shall support the UCS2 facility for the coding of the Katakana characters, as defined in: ISO/IEC 10646 [17].

27.22.4.12.6.3 Test purpose

To verify that the ME displays the UCS2 text contained in the SEND USSD proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.12.6.4 Method of test

27.22.4.12.6.4.1 Initial conditions

27.22.4.12.6.4.2 Procedure

Expected Sequence 6.1 (SEND USSD, 7-bit data, successful, UCS2 text in Katakana)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND USSD 6.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND USSD 6.1.1
4	ME → USER	Display "ル"	[Character " in Katakana]
5	ME → USS	REGISTER 6.1
6	USS → ME	RELEASE COMPLETE (SS RETURN RESULT) 6.1	[Successful]
7	ME → UICC	TERMINAL RESPONSE: SEND USSD 6.1.1	[Command performed successfully]

PROACTIVE COMMAND: SEND USSD 6.1.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha Identifier

Data coding scheme: UCS2 (16bit)

Text: "ル"

USSD String

Data coding scheme: 7-bit default, no message class

USSD String: "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV:	D0	49	81	03	01	12	00	82	02	81	83	85
	03	80	30	EB	8A	39	F0	41	E1	90	58	34
	1E	91	49	E5	92	D9	74	3E	A1	51	E9	94
	5A	B5	5E	B1	59	6D	2B	2C	1E	93	CB	E6
	33	3A	AD	5E	B3	DB	EE	37	3C	2E	9F	D3
	EB	F6	3B	3E	AF	6F	C5	64	33	5A	CD	76
	C3	E5	60

Logically (only USSD argument)

ProcessUnstructuredSS-Request ARGUMENT

USSD-DataCodingScheme:

– 7-bit default, no message class

USSD String:

– "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

Coding

RELEASE COMPLETE (SS RETURN RESULT) 6.1

Logically (only from USSD result):

ProcessUnstructuredSS-Request RETURN RESULT

USSD-DataCodingScheme:

– 7-bit default, no message class

USSD String:

– "USSD string received from SS"

Coding:

Coding	30	1E	04	01	00	04	19	D5	E9	94	08	9A
	D3	E5	69	F7	19	24	2F	8F	CB	69	7B	99
	0C	32	CB	DF	6D	D0	74	0A

TERMINAL RESPONSE: SEND USSD 6.1.1

Logically:

Command details

Command number: 1

Command type: SEND USSD

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Text String

Data coding scheme: 7-bit default, no message class

String: "USSD string received from SS"

Coding:

BER-TLV:	81	03	01	12	00	82	02	82	81	83	01
	00	8D	1A	00	D5	E9	94	08	9A	D3	E5
	69	F7	19	24	2F	8F	CB	69	7B	99	0C
	32	CB	DF	6D	D0	74	0A

27.22.4.12.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.1.

27.22.4.13 SET UP CALL

27.22.4.13.1 SET UP CALL (normal)

27.22.4.13.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.13.1.2 Conformance requirement

The ME shall support the Proactive UICC: Set Up Call facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.13, clause 6.6.12, clause 8.6, clause 8.7, clause 8.12, clause 8.12.3 and clause 5.2.

27.22.4.13.1.3 Test purpose

To verify that the ME accepts the Proactive Command – Set Up Call, displays the alpha identifier to the user, attempts to set up a call to the address and returns the result in the TERMINAL RESPONSE.

27.22.4.13.1.4 Method of test

27.22.4.13.1.4.1 Initial conditions

The ME is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default, with the following exceptions for sequence 1.1 only:

– The Outgoing Call Information (OCI and OCT) service is available in the USIM Service Table.

– EF_OCI (Outgoing Call Information) is present with the following content:

Logically: Invalid

Byte:	B01	…	B41	B42	B43	B44	B45	B46	B47
Coding:	FF	…	FF	00	00	00	01	FF	FF

– EF_OCT (Outgoing Call Timer) is present with the following content:

Logically: Accumulated call timer value: 0

Byte:	B01	B02	B03
Coding:	00	00	00

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.13.1.4.2 Procedure

Expected Sequence 1.1 (SET UP CALL, call confirmed by the user and connected)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 1.1.1
4	ME → USER	ME displays "Not busy" during user confirmation phase.
5	USER → ME	The user confirms the call set up	[user confirmation]
6	ME  USS	The ME attempts to set up a call to "+012340123456"
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 1.1.1	[Command performed successfully]
9	USER → ME	The user ends the call after 10 s. The ME returns to idle mode.
10	ME 🡪 UICC	The ME shall not have updated EF OCI or EF OCT with the call set-up details.

PROACTIVE COMMAND: SET UP CALL 1.1.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Not busy"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Coding:

BER-TLV^:	D0	1E	81	03	01	10	00	82	02	81	83	85
	08	4E	6F	74	20	62	75	73	79	86	09	91
	10	32	04	21	43	65	1C	2C

TERMINAL RESPONSE: SET UP CALL 1.1.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 1.2 (SET UP CALL, call rejected by the user)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 1.1.1
4	ME → USER	ME displays "Not busy" during the user confirmation phase
5	USER → ME	The user rejects the set up call	[user rejects the call]
6	ME → UICC	TERMINAL RESPONSE 1.2.1	[User did not accept call set-up request]
7	ME  USER	The ME returns in idle mode.

TERMINAL RESPONSE: SET UP CALL 1.2.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: User did not accept the proactive command

Coding:

BER-TLV:

Expected Sequence 1.3 void

Expected Sequence 1.4 (SET UP CALL, putting all other calls on hold, ME busy)

ME is busy on a call

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 1.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 1.4.1	[putting all other calls on hold]
4	ME → USER	ME displays "On hold" during the user confirmation phase
5	USER → ME	The user confirms the set up call	[user confirms the call]
6	ME  USS	The active call is put on hold
7	MEUSS	The ME attempts to set up a call to "+012340123456"
8	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
9	ME → UICC	TERMINAL RESPONSE 1.4.1	[Command performed successfully]
10	USER → ME	The user ends the call after 10 s. The ME retrieves the previous call automatically or on request of the user.

PROACTIVE COMMAND: SET UP CALL 1.4.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: putting all other calls on hold

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "On hold"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Coding:

BER-TLV:	D0	1D	81	03	01	10	02	82	02	81	83	85
	07	4F	6E	20	68	6F	6C	64	86	09	91	10
	32	04	21	43	65	1C	2C

TERMINAL RESPONSE: SET UP CALL 1.4.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: putting all other calls on hold

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 1.5 (SET UP CALL, disconnecting all other calls, ME busy)

ME is busy on a call

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 1.5.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 1.5.1	[disconnecting all other calls]
4	ME → USER	ME displays "Disconnect" during the user confirmation phase
5	USER → ME	The user confirms the set up call	[user confirms the call]
6	ME  USS	The ME disconnects the active call
7	MEUSS	The ME attempts to set up a call to "+012340123456"
8	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
9	ME → UICC	TERMINAL RESPONSE 1.5.1	[Command performed successfully]
10	USER → ME	The user ends the call after 10 s.

PROACTIVE COMMAND: SET UP CALL 1.5.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: disconnecting all other calls

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Disconnect"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Coding:

BER-TLV:	D0	20	81	03	01	10	04	82	02	81	83	85
	0A	44	69	73	6³	6^F	6E	6E	65	63	74	86
	09	91	10	32	04	21	43	65	1C	2C

TERMINAL RESPONSE: SET UP CALL 1.5.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: putting all other calls on hold

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 1.6 (SET UP CALL, only if not currently busy on another call, ME busy)

ME is busy on a call

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 1.1.1	[only if not currently busy on another call]
4	ME → UICC	TERMINAL RESPONSE 1.6.1	[ME currently unable to process command]

TERMINAL RESPONSE: SET UP CALL 1.6.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: ME currently unable to process command

Additional Information: ME currently busy on call

Coding:

BER-TLV:	81	03	01	10	00	82	02	82	81	83	02	20
	02

Expected Sequence 1.7 (SET UP CALL, putting all other calls on hold, call hold is not allowed)

ME is busy on a call. The USS shall be configured to not allow Call Hold.

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 1.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 1.4.1	[putting all other calls on hold]
4	ME → USER	ME displays "On hold" during the user confirmation phase
5	USER → ME	The user confirms the set up call	[user confirms the call]
6	ME → USS	The ME attempts to put the active call on hold.
7	USS->ME	The ME receives the HOLD REJECT message from the USS.	[USS sends "Facility Rejected" as cause value]
8	ME → UICC	TERMINAL RESPONSE 1.7.1A OR TERMINAL RESPONSE 1.7.1B	[Network currently unable to process command] [Option A shall apply only from R99 to Rel-6, whereas option B is applicable in all releases]

TERMINAL RESPONSE: SET UP CALL 1.7.1A

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: putting all other calls on hold

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Network currently unable to process command

Additional Information: No specific cause can be given

Coding:

BER-TLV:	81	03	01	10	02	82	02	82	81	83	02	21
	00

TERMINAL RESPONSE: SET UP CALL 1.7.1B

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: putting all other calls on hold

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Network currently unable to process command

Additional Information: Facility Rejected

Coding:

BER-TLV:	81	03	01	10	02	82	02	82	81	83	02	21
	9D

Expected Sequence 1.8 (SET UP CALL, Capability configuration)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 1.8.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 1.8.1	[Capability configuration parameters: full rate support]
4	ME → USER	ME displays "Capability config" during the user confirmation phase
5	USER → ME	The user confirms the set up call	[user confirmation]
6	ME USS	The ME attempts to set up a call to "+012340123456" using the capability configuration parameters supplied by UICC
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 1.8.1	[Command performed successfully]
9	USER → ME	The user ends the call after 10 s The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 1.8.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: if not busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Capability config"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Capability configuration parameters

Information transfer cap: full rate support only MS

Coding:

BER-TLV:	D0	2B	81	03	01	10	00	82	02	81	83	85
	11	43	61	70	61	62	69	6C	69	74	79	20
	63	6F	6E	66	69	67	86	09	91	10	32	04
	21	43	65	1C	2C	87	02	01	A0

TERMINAL RESPONSE: SET UP CALL 1.8.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: if not busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 1.9 (SET UP CALL, max dialling number string, no alpha identifier)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 1.9.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND SET UP CALL 1.9.1	[dialling number string, no alpha identifier]
4	USER → ME	The user confirms the set up call	[user confirmation]
5	MEUSS	The ME attempts to set up a call to "+01234567890123456789012345678901"
6	USS → ME	The ME receives the CONNECT message from the USS.
7	ME → UICC	TERMINAL RESPONSE 1.9.1	[Command performed successfully]
8	USER → ME	The user ends the call The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 1.9.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call with redial

Device identities

Source device: UICC

Destination device: Network

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string: "01234567890123456789012345678901"

Coding:

BER-TLV:	D0	1C	81	03	01	10	01	82	02	81	83	86
	11	91	10	32	54	76	98	10	32	54	76	98
	10	32	54	76	98	10

TERMINAL RESPONSE: SET UP CALL 1.9.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call with redial

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 1.10 (SET UP CALL,256 octets length, long first alpha identifier)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 1.10.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 1.10.1	[ alpha identifier]
4	ME → USER	ME displays "Three types are defined: – set up a call, but only if not currently busy on another call; – set up a call, putting all other calls (if any) on hold; – set up a call, disconnecting all other calls (if any) first. For each of these types, " during the user confirmation phase.
5	USER → ME	The user confirms the set up call	[user confirmation]
6	MEUSS	The ME attempts to set up a call to "+01"
7	USS → ME	The ME receives the CONNECT message from the USS.
8	ME → UICC	TERMINAL RESPONSE 1.10.1	[Command performed successfully]
9	USER → ME	The user ends the call The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 1.10.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call with redial

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Three types are defined: – set up a call, but only if not currently busy on another call; – set up a call, putting all other calls (if any) on hold; – set up a call, disconnecting all other calls (if any) first. For each of these types, "

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string: "01"

Coding:

BER-TLV:	D0	81	FD	81	03	01	10	01	82	02	81	83
	85	81	ED	54	68	72	65	65	20	74	79	70
	65	73	20	61	72	65	20	64	65	66	69	6E
	65	64	3A	20	2D	20	73	65	74	20	75	70
	20	61	20	63	61	6C	6C	2C	20	62	75	74
	20	6F	6E	6C	79	20	69	66	20	6E	6F	74
	20	63	75	72	72	65	6E	74	6C	79	20	62
	75	73	79	20	6F	6E	20	61	6E	6F	74	68
	65	72	20	63	61	6C	6C	3B	20	2D	20	73
	65	74	20	75	70	20	61	20	63	61	6C	6C
	2C	20	70	75	74	74	69	6E	67	20	61	6C
	6C	20	6F	74	68	65	72	20	63	61	6C	6C
	73	20	28	69	66	20	61	6E	79	29	20	6F
	6E	20	68	6F	6C	64	3B	20	2D	20	73	65
	74	20	75	70	20	61	20	63	61	6C	6C	2C
	20	64	69	73	6³	6^F	6E	6E	65	63	74	⁶9
	6E	67	20	61	6C	6C	20	6F	74	68	65	72
	20	63	61	6C	6C	73	20	28	69	66	20	⁶1
	6E	79	29	20	66	69	72	7³	74	2E	20	46
	6F	72	20	65	61	63	68	20	6F	66	20	74
	68	65	73	65	20	74	79	70	65	73	2C	20
	86	02	91	10

TERMINAL RESPONSE: SET UP CALL 1.10.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call with redial

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 1.11A (SET UP CALL, Called party subaddress, command performed successfully)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 1.11.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 1.11.1	[set up a call with called party subaddress]
4	ME → USER	ME displays "Called party" during the user confirmation phase
5	USER → ME	The user confirms the set up call	[user confirmation]
6	MEUSS	The ME attempts to set up a call to "+012340123456" with the called party subaddress information
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 1.11.1A	[Command performed successfully]
9	USER → ME	The user ends the call after 10 s The ME returns in idle mode.

Expected Sequence 1.11B (SET UP CALL, Called party subaddress, ME not supporting the called party subaddress)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 1.11.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 1.11.1	[set up a call with called party subaddress]
4	ME → UICC	TERMINAL RESPONSE 1.11.1B	[beyond ME’s capabilities]

PROACTIVE COMMAND: SET UP CALL 1.11.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: if not busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Called party"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string: "012340123456p1p2"

Called party subaddress

Type of subaddress: NSAP (X.213 / ISO 8348 AD2)

Odd / even indicator: even number of address signals

Subaddress information: AFI, 95, 95, 95, 95, 95

Coding:

BER-TLV:	D0	2B	81	03	01	10	00	82	02	81	83	85
	0C	43	61	6C	6C	65	64	20	70	61	72	74
	79	86	09	91	10	32	04	21	43	65	1C	2C
	88	07	80	50	95	95	95	95	95

TERMINAL RESPONSE: SET UP CALL 1.11.1A

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: if not busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

TERMINAL RESPONSE: SET UP CALL 1.11.1B

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: if not busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Beyond ME’s capabilities

Coding:

BER-TLV:

Expected Sequence 1.12 (SET UP CALL, maximum duration for the redial mechanism)

The USS shall be configured such that call set up requests will be rejected with cause "User Busy".

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 1.12.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 1.12.1	[only if not currently busy on another call with redial]
4	ME → USER	ME displays "Duration" during the user confirmation phase
5	USER → ME	The user confirms the set up call	[user confirms the call]
6	ME  USS	ME attempts to set up a call to "+012340123456" . It stops its attempts after 10 seconds.	[redial mechanism with maximum duration of 10 seconds]]
7	ME → UICC	TERMINAL RESPONSE 1.12.1	[network currently unable to process command]
8	ME  USER	The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 1.12.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call with redial

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Duration"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string: "012340123456p1p2"

Duration

Unit: Seconds

Interval: 10

Coding:

BER-TLV:	D0	22	81	03	01	10	01	82	02	81	83	85
	08	44	75	72	61	74	69	6F	6E	86	09	91
	10	32	04	21	43	65	1C	2C	84	02	01	0A

TERMINAL RESPONSE: SET UP CALL 1.12.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call with redial

Device identities

Source device: ME

Destination device: UICC

Result

General Result: network currently unable to process command

Additional Information: User Busy

Coding:

BER-TLV:	81	03	01	10	01	82	02	82	81	83	02	21
	91

27.22.4.13.1.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1 to 1.12.

27.22.4.13.2 SET UP CALL (second alpha identifier)

27.22.4.13.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.13.2.2 Conformance requirement

Same as clause 27.22.4.13.2.1.

27.22.4.13.2.3 Test purpose

To verify that the ME accepts a Proactive Command – Set Up Call, displays the alpha identifiers to the user, attempts to set up a call to the address and returns the result in the TERMINAL RESPONSE.

27.22.4.13.2.4 Method of test

27.22.4.13.2.4.1 Initial conditions

The ME is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and is in updated idle mode on the USS.

27.22.4.13.2.4.2 Procedure

Expected Sequence 2.1 (SET UP CALL, two alpha identifiers)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 2.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 2.1.1
4	ME → USER	ME displays "CONFIRMATION" during the user confirmation phase
5	USER → ME	The user confirms the set up call	[user confirmation]
6	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL"	[second alpha identifier]
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 2.1.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
9	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 2.1.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL"

Coding:

BER-TLV:	D0	28	81	03	01	10	00	82	02	81	83	85
	0C	43	4F	4E	46	49	52	4D	41	54	49	4F
	4E	86	09	91	10	32	04	21	43	65	1C	2C
	85	04	43	41	4C	4C

TERMINAL RESPONSE: SET UP CALL 2.1.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.13.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 2.1.

27.22.4.13.3 SET UP CALL (display of icons)

27.22.4.13.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.13.3.2 Conformance requirement

27.22.4.13.3.3 Test purpose

To verify that the ME accepts a Proactive Set Up Call , displays the message or icon to the user ,attempts to set up a call to the address, returns the result in the TERMINAL response.

27.22.4.13.3.4 Method of test

27.22.4.13.3.4.1 Initial conditions

The ME is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and is in updated idle mode on the USS.

27.22.4.13.3.4.2 Procedure

Expected Sequence 3.1A (SET UP CALL, display of basic icon during confirmation phase, not self-explanatory, successful )

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 3.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 3.1.1	Including icon identifier, icon shall be displayed in addition of the first alpha identifier
4	ME → USER	ME displays "Set up call Icon 3.1.1" and the basic icon during a user confirmation phase.
5	USER → ME	The user confirms the set up call	[user confirmation]
6	MEUSS	The ME attempts to set up a call to "+012340123456"
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 3.1.1A	[Command performed successfully]
9	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 3.1.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Set up call Icon 3.1.1"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Icon identifier

Icon qualifier: icon is not self-explanatory

Icon identifier: <record 1 in EF IMG>

Coding:

BER-TLV:	D0	30	81	03	01	10	00	82	02	81	83	85
	16	53	65	74	20	75	70	20	63	61	6C	6C
	20	49	63	6F	6E	20	33	2E	31	2E	31	86
	09	91	10	32	04	21	43	65	1C	2C	9E	02
	01	01

TERMINAL RESPONSE: SET UP CALL 3.1.1A

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 3.1B (SET UP CALL, display of basic icon during confirmation phase, not self-explanatory, requested icon could not be displayed)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 3.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 3.1.1	Including icon identifier, icon shall be displayed in addition of the first alpha identifier
4	ME → USER	ME displays "Set up call Icon 3.1.1" without the basic icon during a user confirmation phase.
5	USER → ME	The user confirms the set up call	[user confirmation]
6	MEUSS	The ME attempts to set up a call to "+012340123456"
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 3.1.1B	[Command performed successfully, but requested icon could not be displayed].
9	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.

TERMINAL RESPONSE: SET UP CALL 3.1.1B

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully, but requested icon could not be displayed

Coding:

BER-TLV:

Expected Sequence 3.2A (SET UP CALL, display of basic icon during confirmation phase, self-explanatory, successful )

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 3.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 3.2.1	Including icon identifier, icon shall be displayed instead of the first alpha identifier
4	ME → USER	ME displays the basic icon during a user confirmation phase.
5	USER → ME	The user confirms the set up call	[user confirmation]
6	ME USS	The ME attempts to set up a call to "+012340123456"
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 3.2.1A	[Command performed successfully]
9	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 3.2.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Set up call Icon 3.2.1"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Icon identifier

Icon qualifier: icon is self-explanatory

Icon identifier: <record 1 in EF IMG>

Coding:

BER-TLV:	D0	30	81	03	01	10	00	82	02	81	83	85
	16	53	65	74	20	75	70	20	63	61	6C	6C
	20	49	6³	6F	6E	2⁰	33	2^E	32	2E	31	86
	09	91	10	32	04	21	43	65	1C	2C	9E	02
	00	01

TERMINAL RESPONSE: SET UP CALL 3.2.1A

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 3.2B (SET UP CALL, display of basic icon during confirmation phase, self-explanatory, requested icon could not be displayed)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 3.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 3.2.1	Including icon identifier, icon shall be displayed instead of the first alpha identifier
4	ME → USER	ME display "Set up call Icon 3.2.1" without the icon
5	USER → ME	The user confirms the set up call	[user confirmation]
6	MEUSS	The ME attempts to set up a call to "+012340123456"
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 3.2.1B	[Command performed successfully, but requested icon could not be displayed].
9	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.

TERMINAL RESPONSE: SET UP CALL 3.2.1B

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully, but requested icon could not be displayed

Coding:

BER-TLV:

Expected Sequence 3.3A (SET UP CALL, display of colour icon during confirmation phase, not self‑explanatory, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 3.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 3.3.1	Including icon identifier, icon shall be displayed in addition of the first alpha identifier
4	ME → USER	ME displays "Set up call Icon 3.3.1" and the colour icon during a user confirmation phase.
5	USER → ME	The user confirms the set up call	[user confirmation]
6	MEUSS	The ME attempts to set up a call to "+012340123456"
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 3.3.1A	[Command performed successfully]
9	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 3.3.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Set up call Icon 3.3.1"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Icon identifier

Icon qualifier: icon is not self-explanatory

Icon identifier: <record 2 in EF IMG>

Coding:

BER-TLV:	D0	30	81	03	01	10	00	82	02	81	83	85
	16	53	65	74	20	75	70	20	63	61	6C	6C
	20	49	63	6F	6E	20	33	2E	33	2E	31	86
	09	91	10	32	04	21	43	65	1C	2C	9E	02
	01	02

TERMINAL RESPONSE: SET UP CALL 3.3.1A

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 3.3B (SET UP CALL, display of colour icon during confirmation phase, not self‑explanatory, requested icon could not be displayed)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 3.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 3.3.1	Including icon identifier, icon shall be displayed in addition of the first alpha identifier
4	ME → USER	ME only display alpha string: " Set up call Icon 3.3.1"
5	USER → ME	The user confirms the set up call	[user confirmation]
6	ME USS	The ME attempts to set up a call to "+012340123456"
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 3.3.1B	[Command performed successfully, but requested icon could not be displayed].
9	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.

TERMINAL RESPONSE: SET UP CALL 3.3.1B

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully, but requested icon could not be displayed

Coding:

BER-TLV:

Expected Sequence 3.4A (SET UP CALL, display of self explanatory basic icon during set up call, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 3.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 3.4.1	Including a second alpha identifier and two icons
4	ME → USER	ME displays the basic icon during a user confirmation phase.
5	USER → ME	The user confirms the set up call	[user confirmation]
6	MEUSS	The ME attempts to set up a call to "+012340123456". The ME displays the basic icon without the text during the set up call.
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 3.4.1A	[Command performed successfully]
9	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 3.4.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Set up call Icon 3.4.1"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Icon identifier

Icon qualifier: icon is self-explanatory

Icon identifier: <record 1 in EF IMG>

Alpha identifier: "Set up call Icon 3.4.2"

Icon identifier

Icon qualifier: icon is self-explanatory

Icon identifier: <record 1 in EF IMG>

Coding:

BER-TLV:	D0	4C	81	03	01	10	00	82	02	81	83	85
	16	53	65	74	20	75	70	20	63	61	6C	6C
	20	49	63	6F	6E	20	33	2E	34	2E	31	86
	09	91	10	32	04	21	43	65	1C	2C	9E	02
	00	01	85	16	53	65	74	20	75	70	20	63
	61	6C	6C	20	49	63	6F	6E	20	33	2E	34
	2E	32	9E	02	00	01

TERMINAL RESPONSE: SET UP CALL 3.4.1A

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 3.4B (SET UP CALL, display of self explanatory basic icon during set up call, requested icon could not be displayed)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 3.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 3.4.1	Including a second alpha identifier and two icons
4	ME → USER	ME displays "Set up call Icon 3.4.1" without the icon
5	USER → ME	The user confirms the set up call	[user confirmation]
6	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "Set up call Icon 3.4.2" without the icon during the set up call.
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 3.4.1B	[Command performed successfully, but requested icon could not be displayed].
9	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.

TERMINAL RESPONSE: SET UP CALL 3.4.1B

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully, but requested icon could not be displayed

Coding:

BER-TLV:

27.22.4.13.3.5 Test requirement

The ME shall operate in the manner defined in expected sequences 3.1A to 3.4B.

27.22.4.13.4 SET UP CALL (support of Text Attribute)

27.22.4.13.4.1 SET UP CALL (support of Text Attribute – Left Alignment)

27.22.4.13.4.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.13.4.1.2 Conformance requirement

The ME shall support the Proactive UICC: Set Up Call facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.13, clause 6.6.12, clause 8.6, clause 8.7, clause 8.12, clause 8.12.3, clause 8.70 and clause 5.2.

27.22.4.13.4.1.3 Test purpose

To verify that the ME accepts the Proactive Command – Set Up Call, displays the alpha identifier according to the left alignment text attribute configuration to the user, attempts to set up a call to the address and returns the result in the TERMINAL RESPONSE.

27.22.4.13.4.1.4 Method of test

27.22.4.13.4.1.4.1 Initial conditions

The ME is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and in the updated idle mode on the USS.

27.22.4.13.4.1.4.2 Procedure

Expected Sequence 4.1 (SET UP CALL, Text Attribute – Left Alignment)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.1.1
4	ME → USER	ME displays "CONFIRMATION 1" during the user confirmation phase
5	USER → ME	The user confirms the set up call	[user confirmation is displayed with left alignment]
6	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 1"	[second alpha identifier is displayed with left alignment]
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 4.1.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
9	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
10	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.1.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.1.2
13	ME → USER	ME displays "CONFIRMATION 2" during the user confirmation phase
14	USER → ME	The user confirms the set up call	[User confirmation shall be formatted without left alignment. Remark: If left alignment is the ME’s default alignment as declared in table A.2/14, no alignment change will take place]
15	ME → USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 2"	[Second alpha identifier shall be formatted without left alignment. Remark: If left alignment is the ME’s default alignment as declared in table A.2/14, no alignment change will take place]
16	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
17	ME → UICC	TERMINAL RESPONSE 4.1.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
18	USER → ME	The user ends the call after 18 s. The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 4.1.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 1"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 1"

Text Attribute (user confirmation phase)

Formatting position: 0

Formatting length: 14

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Text Attribute (call set up phase)

Formatting position: 0

Formatting length: 6

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	38	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	⁴F
	4E	20	31	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	31	D0	04
	00	0E	00	B4	D0	04	00	06	00	B4

PROACTIVE COMMAND: SET UP CALL 4.1.2

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 2"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 2"

Coding:

BER-TLV:	D0	2C	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	4F
	4E	20	32	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	32

TERMINAL RESPONSE: SET UP CALL 4.1.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.13.4.1.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.1.

27.22.4.13.4.2 SET UP CALL (support of Text Attribute – Center Alignment)

27.22.4.13.4.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.13.4.2.2 Conformance requirement

The ME shall support the Proactive UICC: Set Up Call facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.13, clause 6.6.12, clause 8.6, clause 8.7, clause 8.12, clause 8.12.3, clause 8.70 and clause 5.2.

27.22.4.13.4.2.3 Test purpose

To verify that the ME accepts the Proactive Command – Set Up Call, displays the alpha identifier according to the center alignment text attribute configuration to the user, attempts to set up a call to the address and returns the result in the TERMINAL RESPONSE.

27.22.4.13.4.2.4 Method of test

27.22.4.13.4.2.4.1 Initial conditions

The ME is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and in the updated idle mode on the USS.

27.22.4.13.4.2.4.2 Procedure

Expected Sequence 4.2 (SET UP CALL, Text Attribute – Center Alignment)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.2.1
4	ME → USER	ME displays "CONFIRMATION 1" during the user confirmation phase
5	USER → ME	The user confirms the set up call	[user confirmation is displayed with center alignment]
6	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 1"	[second alpha identifier is displayed with center alignment]
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 4.2.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
9	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
10	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.2.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.2.2
13	ME → USER	ME displays "CONFIRMATION 2" during the user confirmation phase
14	USER → ME	The user confirms the set up call	[User confirmation shall be formatted without center alignment. Remark: If center alignment is the ME’s default alignment as declared in table A.2/14, no alignment change will take place]
15	ME → USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 2"	[Second alpha identifier shall be formatted without centert alignment. Remark: If center alignment is the ME’s default alignment as declared in table A.2/14, no alignment change will take place]
16	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
17	ME → UICC	TERMINAL RESPONSE 4.2.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
18	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 4.2.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 1"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 1"

Text Attribute (user confirmation phase)

Formatting position: 0

Formatting length: 14

Formatting mode: Center Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Text Attribute (call set up phase)

Formatting position: 0

Formatting length: 6

Formatting mode: Center Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	38	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	⁴F
	4E	20	31	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	31	D0	04
	00	0E	01	B4	D0	04	00	06	01	B4

PROACTIVE COMMAND: SET UP CALL 4.2.2

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 2"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 2"

Coding:

BER-TLV:	D0	2C	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	4F
	4E	20	32	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	32

TERMINAL RESPONSE: SET UP CALL 4.2.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.13.4.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.2.

27.22.4.13.4.3 SET UP CALL (support of Text Attribute – Right Alignment)

27.22.4.13.4.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.13.4.3.2 Conformance requirement

The ME shall support the Proactive UICC: Set Up Call facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.13, clause 6.6.12, clause 8.6, clause 8.7, clause 8.12, clause 8.12.3, clause 8.70 and clause 5.2.

27.22.4.13.4.3.3 Test purpose

To verify that the ME accepts the Proactive Command – Set Up Call, displays the alpha identifier according to the right alignment text attribute configuration to the user, attempts to set up a call to the address and returns the result in the TERMINAL RESPONSE.

27.22.4.13.4.3.4 Method of test

27.22.4.13.4.3.4.1 Initial conditions

The ME is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and in the updated idle mode on the USS.

27.22.4.13.4.3.4.2 Procedure

Expected Sequence 4.3 (SET UP CALL, Text Attribute – Right Alignment)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.3.1
4	ME → USER	ME displays "CONFIRMATION 1" during the user confirmation phase
5	USER → ME	The user confirms the set up call	[user confirmation is displayed with right alignment]
6	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 1"	[second alpha identifier is displayed with right alignment]
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 4.3.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
9	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
10	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.3.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.3.2
13	ME → USER	ME displays "CONFIRMATION 2" during the user confirmation phase
14	USER → ME	The user confirms the set up call	[User confirmation shall be formatted without right alignment. Remark: If right alignment is the ME’s default alignment as declared in table A.2/14, no alignment change will take place]
15	ME → USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 2"	[Second alpha identifier shall be formatted without right alignment. Remark: If right alignment is the ME’s default alignment as declared in table A.2/14, no alignment change will take place]
16	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
17	ME → UICC	TERMINAL RESPONSE 4.3.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
18	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 4.3.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 1"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 1"

Text Attribute (user confirmation phase)

Formatting position: 0

Formatting length: 14

Formatting mode: Right Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Text Attribute (call set up phase)

Formatting position: 0

Formatting length: 6

Formatting mode: Right Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	38	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	⁴F
	4E	20	31	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	31	D0	04
	00	0E	02	B4	D0	04	00	06	02	B4

PROACTIVE COMMAND: SET UP CALL 4.3.2

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 2"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 2"

Coding:

BER-TLV:	D0	2C	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	4F
	4E	20	32	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	32

TERMINAL RESPONSE: SET UP CALL 4.3.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.13.4.3.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.3.

27.22.4.13.4.4 SET UP CALL (support of Text Attribute – Large Font Size)

27.22.4.13.4.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.13.4.4.2 Conformance requirement

The ME shall support the Proactive UICC: Set Up Call facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.13, clause 6.6.12, clause 8.6, clause 8.7, clause 8.12, clause 8.12.3, clause 8.70 and clause 5.2.

27.22.4.13.4.4.3 Test purpose

To verify that the ME accepts the Proactive Command – Set Up Call, displays the alpha identifier according to the large font size text attribute configuration to the user, attempts to set up a call to the address and returns the result in the TERMINAL RESPONSE.

27.22.4.13.4.4.4 Method of test

27.22.4.13.4.4.4.1 Initial conditions

The ME is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and in the updated idle mode on the USS.

27.22.4.13.4.4.4.2 Procedure

Expected Sequence 4.4 (SET UP CALL, Text Attribute – Large Font Size)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.4.1
4	ME → USER	ME displays "CONFIRMATION 1" during the user confirmation phase
5	USER → ME	The user confirms the set up call	[user confirmation is displayed with large font size]
6	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 1"	[second alpha identifier is displayed with large font size]
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 4.4.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
9	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
10	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.4.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.4.2
13	ME → USER	ME displays "CONFIRMATION 2" during the user confirmation phase
14	USER → ME	The user confirms the set up call	[user confirmation is displayed with normal font size]
15	ME → USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 2"	[second alpha identifier is displayed with normal font size]
16	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
17	ME → UICC	TERMINAL RESPONSE 4.4.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
18	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
19	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.4.1
20	ME → UICC	FETCH
21	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.4.1
22	ME → USER	ME displays "CONFIRMATION 1" during the user confirmation phase
23	USER → ME	The user confirms the set up call	[user confirmation is displayed with large font size]
24	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 1"	[second alpha identifier is displayed with large font size]
25	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
26	ME → UICC	TERMINAL RESPONSE 4.4.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
27	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
28	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.4.3
29	ME → UICC	FETCH
30	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.4.3
31	ME → USER	ME displays "CONFIRMATION 3" during the user confirmation phase
32	USER → ME	The user confirms the set up call	[user confirmation is displayed with normal font size]
33	ME → USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 3"	[second alpha identifier is displayed with normal font size]
34	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
35	ME → UICC	TERMINAL RESPONSE 4.4.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
36	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 4.4.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 1"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 1"

Text Attribute (user confirmation phase)

Formatting position: 0

Formatting length: 14

Formatting mode: Left Alignment, Large Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Text Attribute (call set up phase)

Formatting position: 0

Formatting length: 6

Formatting mode: Left Alignment, Large Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	38	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	⁴F
	4E	20	31	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	31	D0	04
	00	0E	04	B4	D0	04	00	06	04	B4

PROACTIVE COMMAND: SET UP CALL 4.4.2

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 2"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 2"

Text Attribute (user confirmation phase)

Formatting position: 0

Formatting length: 14

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Text Attribute (call set up phase)

Formatting position: 0

Formatting length: 6

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	38	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	⁴F
	4E	20	32	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	32	D0	04
	00	0E	00	B4	D0	04	00	06	00	B4

PROACTIVE COMMAND: SET UP CALL 4.4.3

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 3"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 3"

Coding:

BER-TLV:	D0	2C	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	4F
	4E	20	33	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	33

TERMINAL RESPONSE: SET UP CALL 4.4.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.13.4.4.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.4.

27.22.4.13.4.5 SET UP CALL (support of Text Attribute – Small Font Size)

27.22.4.13.4.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.13.4.5.2 Conformance requirement

The ME shall support the Proactive UICC: Set Up Call facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.13, clause 6.6.12, clause 8.6, clause 8.7, clause 8.12, clause 8.12.3, clause 8.70 and clause 5.2.

27.22.4.13.4.5.3 Test purpose

To verify that the ME accepts the Proactive Command – Set Up Call, displays the alpha identifier according to the small font size text attribute configuration to the user, attempts to set up a call to the address and returns the result in the TERMINAL RESPONSE.

27.22.4.13.4.4.5 Method of test

27.22.4.13.4.4.5.1 Initial conditions

The ME is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and in the updated idle mode on the USS.

27.22.4.13.4.4.5.2 Procedure

Expected Sequence 4.5 (SET UP CALL, Text Attribute – Small Font Size)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.5.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.5.1
4	ME → USER	ME displays "CONFIRMATION 1" during the user confirmation phase
5	USER → ME	The user confirms the set up call	[user confirmation is displayed with small font size]
6	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 1"	[second alpha identifier is displayed with small font size]
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 4.5.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
9	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
10	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.5.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.5.2
13	ME → USER	ME displays "CONFIRMATION 2" during the user confirmation phase
14	USER → ME	The user confirms the set up call	[user confirmation is displayed with normal font size]
15	ME → USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 2"	[second alpha identifier is displayed with normal font size]
16	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
17	ME → UICC	TERMINAL RESPONSE 4.5.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
18	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
19	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.5.1
20	ME → UICC	FETCH
21	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.5.1
22	ME → USER	ME displays "CONFIRMATION 1" during the user confirmation phase
23	USER → ME	The user confirms the set up call	[user confirmation is displayed with small font size]
24	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 1"	[second alpha identifier is displayed with small font size]
25	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
26	ME → UICC	TERMINAL RESPONSE 4.5.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
27	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
28	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.5.3
29	ME → UICC	FETCH
30	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.5.3
31	ME → USER	ME displays "CONFIRMATION 3" during the user confirmation phase
32	USER → ME	The user confirms the set up call	[user confirmation is displayed with normal font size]
33	ME → USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 3"	[second alpha identifier is displayed with normal font size]
34	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
35	ME → UICC	TERMINAL RESPONSE 4.5.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
36	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 4.5.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 1"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 1"

Text Attribute (user confirmation phase)

Formatting position: 0

Formatting length: 14

Formatting mode: Left Alignment, Small Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Text Attribute (call set up phase)

Formatting position: 0

Formatting length: 6

Formatting mode: Left Alignment, Small Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	38	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	⁴F
	4E	20	31	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	31	D0	04
	00	0E	08	B4	D0	04	00	06	08	B4

PROACTIVE COMMAND: SET UP CALL 4.5.2

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 2"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 2"

Text Attribute (user confirmation phase)

Formatting position: 0

Formatting length: 14

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Text Attribute (call set up phase)

Formatting position: 0

Formatting length: 6

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	38	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	⁴F
	4E	20	32	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	32	D0	04
	00	0E	00	B4	D0	04	00	06	00	B4

PROACTIVE COMMAND: SET UP CALL 4.5.3

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 3"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 3"

Coding:

BER-TLV:	D0	2C	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	4F
	4E	20	33	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	33

TERMINAL RESPONSE: SET UP CALL 4.5.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.13.4.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.5.

27.22.4.13.4.6 SET UP CALL (support of Text Attribute – Bold On)

27.22.4.13.4.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.13.4.6.2 Conformance requirement

The ME shall support the Proactive UICC: Set Up Call facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.13, clause 6.6.12, clause 8.6, clause 8.7, clause 8.12, clause 8.12.3, clause 8.70 and clause 5.2.

27.22.4.13.4.6.3 Test purpose

To verify that the ME accepts the Proactive Command – Set Up Call, displays the alpha identifier according to the bold text attribute configuration to the user, attempts to set up a call to the address and returns the result in the TERMINAL RESPONSE.

27.22.4.13.4.6.4 Method of test

27.22.4.13.4.6.4.1 Initial conditions

The ME is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and in the updated idle mode on the USS.

27.22.4.13.4.6.4.2 Procedure

Expected Sequence 4.6 (SET UP CALL, Text Attribute – Bold On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.6.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.6.1
4	ME → USER	ME displays "CONFIRMATION 1" during the user confirmation phase
5	USER → ME	The user confirms the set up call	[user confirmation is displayed with bold on]
6	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 1"	[second alpha identifier is displayed with bold on]
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 4.6.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
9	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
10	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.6.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.6.2
13	ME → USER	ME displays "CONFIRMATION 2" during the user confirmation phase
14	USER → ME	The user confirms the set up call	[user confirmation is displayed with bold off]
15	ME → USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 2"	[second alpha identifier is displayed with bold off]
16	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
17	ME → UICC	TERMINAL RESPONSE 4.6.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
18	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
19	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.6.1
20	ME → UICC	FETCH
21	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.6.1
22	ME → USER	ME displays "CONFIRMATION 1" during the user confirmation phase
23	USER → ME	The user confirms the set up call	[user confirmation is displayed with bold on]
24	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 1"	[second alpha identifier is displayed with bold on]
25	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
26	ME → UICC	TERMINAL RESPONSE 4.6.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
27	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
28	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.6.3
29	ME → UICC	FETCH
30	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.6.3
31	ME → USER	ME displays "CONFIRMATION 3" during the user confirmation phase
32	USER → ME	The user confirms the set up call	[user confirmation is displayed with bold off]
33	ME → USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 3"	[second alpha identifier is displayed with bold off]
34	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
35	ME → UICC	TERMINAL RESPONSE 4.6.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
36	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 4.6.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 1"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 1"

Text Attribute (user confirmation phase)

Formatting position: 0

Formatting length: 14

Formatting mode: Left Alignment, Normal Font, Bold On, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Text Attribute (call set up phase)

Formatting position: 0

Formatting length: 6

Formatting mode: Left Alignment, Normal Font, Bold On, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	38	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	⁴F
	4E	20	31	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	31	D0	04
	00	0E	10	B4	D0	04	00	06	10	B4

PROACTIVE COMMAND: SET UP CALL 4.6.2

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 2"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 2"

Text Attribute (user confirmation phase)

Formatting position: 0

Formatting length: 14

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Text Attribute (call set up phase)

Formatting position: 0

Formatting length: 6

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	38	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	⁴F
	4E	20	32	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	32	D0	04
	00	0E	00	B4	D0	04	00	06	00	B4

PROACTIVE COMMAND: SET UP CALL 4.6.3

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 3"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 3"

Coding:

BER-TLV:	D0	2C	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	4F
	4E	20	33	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	33

TERMINAL RESPONSE: SET UP CALL 4.6.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.13.4.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.6.

27.22.4.13.4.7 SET UP CALL (support of Text Attribute – Italic On)

27.22.4.13.4.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.13.4.7.2 Conformance requirement

The ME shall support the Proactive UICC: Set Up Call facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.13, clause 6.6.12, clause 8.6, clause 8.7, clause 8.12, clause 8.12.3, clause 8.70 and clause 5.2.

27.22.4.13.4.7.3 Test purpose

To verify that the ME accepts the Proactive Command – Set Up Call, displays the alpha identifier according to the italic text attribute configuration to the user, attempts to set up a call to the address and returns the result in the TERMINAL RESPONSE.

27.22.4.13.4.7.4 Method of test

27.22.4.13.4.7.4.1 Initial conditions

The ME is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and in the updated idle mode on the USS.

27.22.4.13.4.7.4.2 Procedure

Expected Sequence 4.7 (SET UP CALL, Text Attribute – Italic On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.7.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.7.1
4	ME → USER	ME displays "CONFIRMATION 1" during the user confirmation phase
5	USER → ME	The user confirms the set up call	[user confirmation is displayed with italic on]
6	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 1"	[second alpha identifier is displayed with italic on]
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 4.7.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
9	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
10	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.7.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.7.2
13	ME → USER	ME displays "CONFIRMATION 2" during the user confirmation phase
14	USER → ME	The user confirms the set up call	[user confirmation is displayed with italic off]
15	ME → USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 2"	[second alpha identifier is displayed with italic off]
16	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
17	ME → UICC	TERMINAL RESPONSE 4.7.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
18	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
19	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.7.1
20	ME → UICC	FETCH
21	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.7.1
22	ME → USER	ME displays "CONFIRMATION 1" during the user confirmation phase
23	USER → ME	The user confirms the set up call	[user confirmation is displayed with italic on]
24	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 1"	[second alpha identifier is displayed with italic on]
25	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
26	ME → UICC	TERMINAL RESPONSE 4.7.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
27	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
28	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.7.3
29	ME → UICC	FETCH
30	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.7.3
31	ME → USER	ME displays "CONFIRMATION 3" during the user confirmation phase
32	USER → ME	The user confirms the set up call	[user confirmation is displayed with italic off]
33	ME → USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 3"	[second alpha identifier is displayed with italic off]
34	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
35	ME → UICC	TERMINAL RESPONSE 4.7.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
36	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 4.7.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 1"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 1"

Text Attribute (user confirmation phase)

Formatting position: 0

Formatting length: 14

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic On, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Text Attribute (call set up phase)

Formatting position: 0

Formatting length: 6

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic On, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	38	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	⁴F
	4E	20	31	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	31	D0	04
	00	0E	20	B4	D0	04	00	06	20	B4

PROACTIVE COMMAND: SET UP CALL 4.7.2

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 2"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 2"

Text Attribute (user confirmation phase)

Formatting position: 0

Formatting length: 14

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Text Attribute (call set up phase)

Formatting position: 0

Formatting length: 6

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	38	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	⁴F
	4E	20	32	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	32	D0	04
	00	0E	00	B4	D0	04	00	06	00	B4

PROACTIVE COMMAND: SET UP CALL 4.7.3

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 3"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 3"

Coding:

BER-TLV:	D0	2C	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	4F
	4E	20	33	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	33

TERMINAL RESPONSE: SET UP CALL 4.7.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.13.4.7.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.7.

27.22.4.13.4.8 SET UP CALL (support of Text Attribute – Underline On)

27.22.4.13.4.8.1 Definition and applicability

See clause 3.2.2.

27.22.4.13.4.8.2 Conformance requirement

The ME shall support the Proactive UICC: Set Up Call facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.13, clause 6.6.12, clause 8.6, clause 8.7, clause 8.12, clause 8.12.3, clause 8.70 and clause 5.2.

27.22.4.13.4.8.3 Test purpose

To verify that the ME accepts the Proactive Command – Set Up Call, displays the alpha identifier according to the underline text attribute configuration to the user, attempts to set up a call to the address and returns the result in the TERMINAL RESPONSE.

27.22.4.13.4.8.4 Method of test

27.22.4.13.4.8.4.1 Initial conditions

The ME is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and in the updated idle mode on the USS.

27.22.4.13.4.8.4.2 Procedure

Expected Sequence 4.8 (SET UP CALL, Text Attribute – Underline On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.8.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.8.1
4	ME → USER	ME displays "CONFIRMATION 1" during the user confirmation phase
5	USER → ME	The user confirms the set up call	[user confirmation is displayed with underline on]
6	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 1"	[second alpha identifier is displayed with underline on]
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 4.8.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
9	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
10	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.8.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.8.2
13	ME → USER	ME displays "CONFIRMATION 2" during the user confirmation phase
14	USER → ME	The user confirms the set up call	[user confirmation is displayed with underline off]
15	ME → USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 2"	[second alpha identifier is displayed with underline off]
16	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
17	ME → UICC	TERMINAL RESPONSE 4.8.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
18	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
19	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.8.1
20	ME → UICC	FETCH
21	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.8.1
22	ME → USER	ME displays "CONFIRMATION 1" during the user confirmation phase
23	USER → ME	The user confirms the set up call	[user confirmation is displayed with underline on]
24	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 1"	[second alpha identifier is displayed with underline on]
25	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
26	ME → UICC	TERMINAL RESPONSE 4.8.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
27	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
28	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.8.3
29	ME → UICC	FETCH
30	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.8.3
31	ME → USER	ME displays "CONFIRMATION 3" during the user confirmation phase
32	USER → ME	The user confirms the set up call	[user confirmation is displayed with underline off]
33	ME → USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 3"	[second alpha identifier is displayed with Undeline off]
34	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
35	ME → UICC	TERMINAL RESPONSE 4.8.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
36	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 4.8.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 1"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 1"

Text Attribute (user confirmation phase)

Formatting position: 0

Formatting length: 14

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline On, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Text Attribute (call set up phase)

Formatting position: 0

Formatting length: 6

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline On, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	38	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	⁴F
	4E	20	31	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	31	D0	04
	00	0E	40	B4	D0	04	00	06	40	B4

PROACTIVE COMMAND: SET UP CALL 4.8.2

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 2"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 2"

Text Attribute (user confirmation phase)

Formatting position: 0

Formatting length: 14

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Text Attribute (call set up phase)

Formatting position: 0

Formatting length: 6

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	38	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	⁴F
	4E	20	32	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	32	D0	04
	00	0E	00	B4	D0	04	00	06	00	B4

PROACTIVE COMMAND: SET UP CALL 4.8.3

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 3"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 3"

Coding:

BER-TLV:	D0	2C	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	4F
	4E	20	33	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	33

TERMINAL RESPONSE: SET UP CALL 4.8.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.13.4.8.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.8.

27.22.4.13.4.9 SET UP CALL (support of Text Attribute – Strikethrough On)

27.22.4.13.4.9.1 Definition and applicability

See clause 3.2.2.

27.22.4.13.4.9.2 Conformance requirement

The ME shall support the Proactive UICC: Set Up Call facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.13, clause 6.6.12, clause 8.6, clause 8.7, clause 8.12, clause 8.12.3, clause 8.70 and clause 5.2.

27.22.4.13.4.9.3 Test purpose

To verify that the ME accepts the Proactive Command – Set Up Call, displays the alpha identifier according to the strikethrough text attribute configuration to the user, attempts to set up a call to the address and returns the result in the TERMINAL RESPONSE.

27.22.4.13.4.9.4 Method of test

27.22.4.13.4.9.4.1 Initial conditions

The ME is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and in the updated idle mode on the USS.

27.22.4.13.4.9.4.2 Procedure

Expected Sequence 4.9 (SET UP CALL, Text Attribute – Strikethrough On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.9.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.9.1
4	ME → USER	ME displays "CONFIRMATION 1" during the user confirmation phase
5	USER → ME	The user confirms the set up call	[user confirmation is displayed with strikethrough on]
6	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 1"	[second alpha identifier is displayed with strikethrough on]
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 4.9.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
9	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
10	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.9.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.9.2
13	ME → USER	ME displays "CONFIRMATION 2" during the user confirmation phase
14	USER → ME	The user confirms the set up call	[user confirmation is displayed with strikethrough off]
15	ME → USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 2"	[second alpha identifier is displayed with strikethrough off]
16	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
17	ME → UICC	TERMINAL RESPONSE 4.9.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
18	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
19	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.9.1
20	ME → UICC	FETCH
21	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.9.1
22	ME → USER	ME displays "CONFIRMATION 1" during the user confirmation phase
23	USER → ME	The user confirms the set up call	[user confirmation is displayed with strikethrough on]
24	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 1"	[second alpha identifier is displayed with strikethrough on]
25	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
26	ME → UICC	TERMINAL RESPONSE 4.9.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
27	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
28	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.9.3
29	ME → UICC	FETCH
30	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.9.3
31	ME → USER	ME displays "CONFIRMATION 3" during the user confirmation phase
32	USER → ME	The user confirms the set up call	[user confirmation is displayed with strikethrough off]
33	ME → USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 3"	[second alpha identifier is displayed with strikethrough off]
34	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
35	ME → UICC	TERMINAL RESPONSE 4.9.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
36	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 4.9.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 1"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 1"

Text Attribute (user confirmation phase)

Formatting position: 0

Formatting length: 14

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough On

Colour: Dark Green Foreground, Bright Yellow Background

Text Attribute (call set up phase)

Formatting position: 0

Formatting length: 6

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough On

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	38	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	⁴F
	4E	20	31	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	31	D0	04
	00	0E	80	B4	D0	04	00	06	80	B4

PROACTIVE COMMAND: SET UP CALL 4.9.2

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 2"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 2"

Text Attribute (user confirmation phase)

Formatting position: 0

Formatting length: 14

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Text Attribute (call set up phase)

Formatting position: 0

Formatting length: 6

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	38	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	⁴F
	4E	20	32	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	32	D0	04
	00	0E	00	B4	D0	04	00	06	00	B4

PROACTIVE COMMAND: SET UP CALL 4.9.3

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 3"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 3"

Coding:

BER-TLV:	D0	2C	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	4F
	4E	20	33	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	33

TERMINAL RESPONSE: SET UP CALL 4.9.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.13.4.9.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.9.

27.22.4.13.4.10 SET UP CALL (support of Text Attribute – Foreground and Background Colour)

27.22.4.13.4.10.1 Definition and applicability

See clause 3.2.2.

27.22.4.13.4.10.2 Conformance requirement

The ME shall support the Proactive UICC: Set Up Call facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.13, clause 6.6.12, clause 8.6, clause 8.7, clause 8.12, clause 8.12.3, clause 8.70 and clause 5.2.

27.22.4.13.4.10.3 Test purpose

To verify that the ME accepts the Proactive Command – Set Up Call, displays the alpha identifier according to the foreground and background colour text attribute configuration to the user, attempts to set up a call to the address and returns the result in the TERMINAL RESPONSE.

27.22.4.13.4.10.4 Method of test

27.22.4.13.4.10.4.1 Initial conditions

The ME is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and in the updated idle mode on the USS.

27.22.4.13.4.10.4.2 Procedure

Expected Sequence 4.10 (SET UP CALL, Text Attribute – Foreground and Background Colour)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.10.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.10.1
4	ME → USER	ME displays "CONFIRMATION 1" during the user confirmation phase
5	USER → ME	The user confirms the set up call	[user confirmation is displayed with foreground and background colour according to Text Attribute configuration]
6	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 1"	[second alpha identifier is displayed with foreground and background colour according to Text Attribute configuration]
7	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
8	ME → UICC	TERMINAL RESPONSE 4.10.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
9	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.
10	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 4.10.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: SET UP CALL 4.10.2
13	ME → USER	ME displays "CONFIRMATION 2" during the user confirmation phase
14	USER → ME	The user confirms the set up call	[user confirmation is displayed with ME’s default foreground and background colour]
15	ME → USS	The ME attempts to set up a call to "+012340123456". The ME displays "CALL 2"	[second alpha identifier is displayed with ME’s default foreground and background colour]
16	USS → ME	The ME receives the CONNECT message from the USS.	[The USS also has to handle the START DTMF and STOP DTMF messages sent by the ME in an appropriate way]
17	ME → UICC	TERMINAL RESPONSE 4.10.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
18	USER → ME	The user ends the call after 10 s. The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 4.10.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 1"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 1"

Text Attribute (user confirmation phase)

Formatting position: 0

Formatting length: 14

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Text Attribute (call set up phase)

Formatting position: 0

Formatting length: 6

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Bright Yellow Foreground, Dark Green Background

Coding:

BER-TLV:	D0	38	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	⁴F
	4E	20	31	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	31	D0	04
	00	0E	00	B4	D0	04	00	06	00	4B

PROACTIVE COMMAND: SET UP CALL 4.10.2

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "CONFIRMATION 2"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456p1p2"

Alpha Identifier (call set up phase): "CALL 2"

Coding:

BER-TLV:	D0	2C	81	03	01	10	00	82	02	81	83	85
	0E	43	4F	4E	46	49	52	4D	41	54	49	4F
	4E	20	32	86	09	91	10	32	04	21	43	65
	1C	2C	85	06	43	41	4C	4C	20	32

TERMINAL RESPONSE: SET UP CALL 4.10.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.13.4.10.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.10.

27.22.4.13.5 SET UP CALL (UCS2 Display in Cyrillic)

27.22.4.13.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.13.5.2 Conformance requirement

The ME shall support the Proactive UICC: Set Up Call facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.13, clause 6.6.12, clause 8.6, clause 8.7, clause 8.12, clause 8.12.3 and clause 5.2.

The ME shall support the UCS2 facility for the coding of the Cyrillic alphabet, as defined in:

– ISO/IEC 10646 [17].

27.22.4.13.5.3 Test purpose

To verify that the ME accepts the Proactive Command – Set Up Call, displays the alpha identifier with UCS2 coding to the user, attempts to set up a call to the address and returns the result in the TERMINAL RESPONSE.

27.22.4.13.5.4 Method of test

27.22.4.13.5.4.1 Initial conditions

The ME is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.13.5.4.2 Procedure

Expected Sequence 5.1 (SET UP CALL with UCS2 – Cyrillic Characters, call confirmed by the user and connected)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 5.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 5.1.1
4	ME → USER	ME displays "ЗДРАВСТВУЙТЕ" during user confirmation phase.	["ЗДРАВСТВУЙТЕ": "Hello" in Russian]
5	USER → ME	The user confirms the call set up	[user confirmation]
6	ME  USS	The ME attempts to set up a call to "+012340123456"
7	USS → ME	The ME receives the CONNECT message from the USS.
8	ME → UICC	TERMINAL RESPONSE 5.1.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
9	USER → ME	The user ends the call after 5 s. The ME returns to idle mode.

PROACTIVE COMMAND: SET UP CALL 5.1.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "ЗДРАВСТВУЙТЕ"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456"

Coding:

BER-TLV:	D0	2D	81	03	01	10	00	82	02	81	83	85
	19	80	04	17	04	14	04	20	04	10	04	12
	04	21	04	22	04	12	04	23	04	19	04	22
	04	15	86	07	91	10	32	04	21	43	65

TERMINAL RESPONSE: SET UP CALL 5.1.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 5.2 (SET UP CALL, two alpha identifiers coded in UCS2 – Cyrillic Characters)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 5.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 5.2.1
4	ME → USER	ME displays "ЗДРАВСТВУЙТЕ1" during the user confirmation phase	["ЗДРАВСТВУЙТЕ1": "Hello1" in Russian]
5	USER → ME	The user confirms the set up call	[user confirmation]
6	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "ЗДРАВСТВУЙТЕ2"	[second alpha identifier] ["ЗДРАВСТВУЙТЕ2": "Hello2" in Russian]
7	USS → ME	The ME receives the CONNECT message from the USS.
8	ME → UICC	TERMINAL RESPONSE 5.2.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
9	USER → ME	The user ends the call after 5 s. The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 5.2.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: " ЗДРАВСТВУЙТЕ1"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456"

Alpha Identifier (call set up phase): " ЗДРАВСТВУЙТЕ2"

Coding:

BER-TLV:	D0	4C	81	03	01	10	00	82	02	81	83	85
	1B	80	04	17	04	14	04	20	04	10	04	12
	04	21	04	22	04	12	04	23	04	19	04	22
	04	15	00	31	86	07	91	10	32	04	21	43
	65	85	1B	80	04	17	04	14	04	20	04	10
	04	12	04	21	04	22	04	12	04	23	04	19
	04	22	04	15	00	32

TERMINAL RESPONSE: SET UP CALL 5.2.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.13.5.5 Test requirement

The ME shall operate in the manner defined in expected sequences 5.1 to 5.2.

27.22.4.13.6 SET UP CALL (UCS2 Display in Chinese)

27.22.4.13.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.13.6.2 Conformance requirement

The ME shall support the Proactive UICC: Set Up Call facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.13, clause 6.6.12, clause 8.6, clause 8.7, clause 8.12, clause 8.12.3 and clause 5.2.

The ME shall support the UCS2 facility for the coding of the Chinese characters, as defined in:

– ISO/IEC 10646 [17].

27.22.4.13.6.3 Test purpose

27.22.4.13.6.4 Method of test

27.22.4.13.6.4.1 Initial conditions

The ME is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.13.6.4.2 Procedure

Expected Sequence 6.1 (SET UP CALL with UCS2 – Chinese characters, call confirmed by the user and connected)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 6.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 6.1.1
4	ME → USER	ME displays "不忙" during user confirmation phase.	["不忙": "Not Busy" in Chinese]
5	USER → ME	The user confirms the call set up	[user confirmation]
6	ME  USS	The ME attempts to set up a call to "+012340123456"
7	USS → ME	The ME receives the CONNECT message from the USS.
8	ME → UICC	TERMINAL RESPONSE 6.1.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
9	USER → ME	The user ends the call after 5 s. The ME returns to idle mode.

PROACTIVE COMMAND: SET UP CALL 6.1.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "不忙"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456"

Coding:

BER-TLV:	D0	19	81	03	01	10	00	82	02	81	83	85
	05	80	4E	0D	5F	D9	86	07	91	10	32	04
	21	43	65

TERMINAL RESPONSE: SET UP CALL 6.1.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 6.2 (SET UP CALL, two alpha identifiers coded in UCS2 – Chinese characters)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 6.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 6.2.1
4	ME → USER	ME displays "确定" during the user confirmation phase	["确定": "Confirmation" in Chinese]
5	USER → ME	The user confirms the set up call	[user confirmation]
6	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "打电话"	[second alpha identifier] ["打电话": "CALL" in Chinese]
7	USS → ME	The ME receives the CONNECT message from the USS.
8	ME → UICC	TERMINAL RESPONSE 6.2.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
9	USER → ME	The user ends the call after 5 s. The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 6.2.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "确定"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456"

Alpha Identifier (call set up phase): "打电话"

Coding:

BER-TLV:	D0	22	81	03	01	10	00	82	02	81	83	85
	05	80	78	6E	5B	9A	86	07	91	10	32	04
	21	43	65	85	07	80	62	53	75	35	8B	DD

TERMINAL RESPONSE: SET UP CALL 6.2.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.13.6.5 Test requirement

The ME shall operate in the manner defined in expected sequences 6.1 to 6.2.

27.22.4.13.7 SET UP CALL (UCS2 Display in Katakana)

27.22.4.13.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.13.7.2 Conformance requirement

The ME shall support the Proactive UICC: Set Up Call facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.13, clause 6.6.12, clause 8.6, clause 8.7, clause 8.12, clause 8.12.3 and clause 5.2.

The ME shall support the UCS2 facility for the coding of the Katakana characters, as defined in:

– ISO/IEC 10646 [17].

27.22.4.13.7.3 Test purpose

27.22.4.13.7.4 Method of test

27.22.4.13.7.4.1 Initial conditions

The ME is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.13.7.4.2 Procedure

Expected Sequence 7.1 (SET UP CALL with UCS2 – Katakana characters, call confirmed by the user and connected)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 7.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 7.1.1
4	ME → USER	ME displays "ル" during user confirmation phase.	[Character in Katakana]
5	USER → ME	The user confirms the call set up	[user confirmation]
6	ME  USS	The ME attempts to set up a call to "+012340123456"
7	USS → ME	The ME receives the CONNECT message from the USS.
8	ME → UICC	TERMINAL RESPONSE 7.1.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
9	USER → ME	The user ends the call after 5 s. The ME returns to idle mode.

PROACTIVE COMMAND: SET UP CALL 7.1.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "ル"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456"

Coding:

BER-TLV:	D0	17	81	03	01	10	00	82	02	81	83	85
	03	80	30	EB	86	07	91	10	32	04	21	43
	65

TERMINAL RESPONSE: SET UP CALL 7.1.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 7.2 (SET UP CALL, two alpha identifiers coded in UCS2 – Katakana characters)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP CALL 7.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP CALL 7.2.1
4	ME → USER	ME displays "ル1" during the user confirmation phase	[Character in Katakana]
5	USER → ME	The user confirms the set up call	[user confirmation]
6	ME USS	The ME attempts to set up a call to "+012340123456". The ME displays "ル2".	[second alpha identifier] [Character in Katakana]
7	USS → ME	The ME receives the CONNECT message from the USS.
8	ME → UICC	TERMINAL RESPONSE 7.2.1 The ME shall not update EF LND with the called party address.	[Command performed successfully]
9	USER → ME	The user ends the call after 5 s. The ME returns in idle mode.

PROACTIVE COMMAND: SET UP CALL 7.2.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "ル1"

Address

TON: International

NPI: ISDN / telephone numbering plan

Dialling number string "012340123456"

Alpha Identifier (call set up phase): "ル2"

Coding:

BER-TLV:	D0	20	81	03	01	10	00	82	02	81	83	85
	05	80	30	EB	00	31	86	07	91	10	32	04
	21	43	65	85	05	80	30	EB	00	32

TERMINAL RESPONSE: SET UP CALL 7.2.1

Logically:

Command details

Command number: 1

Command type: SET UP CALL

Command qualifier: only if not currently busy on another call

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.13.7.5 Test requirement

The ME shall operate in the manner defined in expected sequences 7.1 to 7.2.

27.22.4.14 POLLING OFF

27.22.4.14.1 Definition and applicability

See clause 3.2.2.

27.22.4.14.2 Conformance requirement

The ME shall support the POLLING OFF as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.14, clause 6.8, clause 6.11, clause 8.6 and clause 8.7.

27.22.4.14.3 Test purpose

To verify that the ME cancels the effect of any previous POLL INTERVAL commands and does not effect UICC presence detection.

27.22.4.14.4 Method of test

27.22.4.14.4.1 Initial conditions

For sequence 1.1:

– The elementary files are coded as Toolkit default.

– The ME is connected to the USIM Simulator and to the USS.

For sequence 1.2:

– The default E-UTRAN/EPC UICC, the default E-UTRAN parameters are used.

– The ME is connected to the USIM Simulator and to the E-USS/NB-SS.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.14.4.2 Procedure

Expected Sequence 1.1 (POLLING OFF)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: POLL INTERVAL 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: POLL INTERVAL 1.1.1	Interval = 1 min
4	ME → UICC	TERMINAL RESPONSE: POLL INTERVAL 1.1.1 A or TERMINAL RESPONSE: POLL INTERVAL 1.1.1B	[command performed successfully, duration depends on the ME’s capabilities]
5	UICC → ME	PROACTIVE COMMAND PENDING: POLLING OFF 1.1.2
6	ME → UICC	FETCH
7	UICC → ME	PROACTIVE COMMAND: POLLING OFF 1.1.2
8	ME → UICC	TERMINAL RESPONSE: POLLING OFF 1.1.2	[command performed successfully]
9	USER  ME	Call to be set up	A call shall be set up using the generic call setup for circuit switched call or to activate a PDP context.
10	ME  UICC	Periods of inactivity on the UICC-ME interfaceshall not exceed 30 seconds	In case of PDP context for a terminal that supports Rel-12 or later, exchange of data with the network may be required to guarantee the correct result of the test.
11	USER  ME	Call to be terminated 3 minutes after call setup

PROACTIVE COMMAND: POLL INTERVAL 1.1.1

Logically:

Command details

Command number: 1

Command type: POLL INTERVAL

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Duration

Time unit: Minutes

Time interval: 1

Coding:

BER-TLV:	D0	0D	81	03	01	03	00	82	02	81	82	84
	02	00	01

TERMINAL RESPONSE: POLL INTERVAL 1.1.1A

Logically:

Command details

Command number: 1

Command type: POLL INTERVAL

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Duration

Time unit: Minutes

Time interval: 1

Coding:

BER-TLV:	81	03	01	03	00	82	02	82	81	83	01	00
	84	02	00	01

TERMINAL RESPONSE: POLL INTERVAL 1.1.1B

Logically:

Command details

Command number: 1

Command type: POLL INTERVAL

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Duration

Time unit: Seconds

Time interval: 60

Coding:

BER-TLV:	81	03	01	03	00	82	02	82	81	83	01	00
	84	02	01	3C

Note: If the requested poll interval is not supported by the ME, the ME is allowed to use a different one as stated in TS 31.111 [15], clause 6.4.6.

PROACTIVE COMMAND: POLLING OFF 1.1.2

Logically:

Command details

Command number: 1

Command type: POLLING OFF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

TERMINAL RESPONSE: POLLING OFF 1.1.2

Logically:

Command details

Command number: 1

Command type: POLLING OFF

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 1.2 (POLLING OFF, E-UTRAN)

Step	Direction	MESSAGE / Action	Comments
1	ME → E-USS/NB-SS	The ME successfully performs EPS bearer context activation
2	UICC → ME	PROACTIVE COMMAND PENDING: POLL INTERVAL 1.1.1
3	ME → UICC	FETCH
4	UICC → ME	PROACTIVE COMMAND: POLL INTERVAL 1.1.1	Interval = 1 min
5	ME → UICC	TERMINAL RESPONSE: POLL INTERVAL 1.1.1 A or TERMINAL RESPONSE: POLL INTERVAL 1.1.1B	[command performed successfully, duration depends on the ME’s capabilities]
6	UICC → ME	PROACTIVE COMMAND PENDING: POLLING OFF 1.1.2
7	ME → UICC	FETCH
8	UICC → ME	PROACTIVE COMMAND: POLLING OFF 1.1.2
9	ME → UICC	TERMINAL RESPONSE: POLLING OFF 1.1.2	[command performed successfully]
10	ME  UICC	Periods of inactivity on the UICC-ME interface shall not exceed 30 seconds	For a terminal that supports Rel-12 or later, exchange of data with the network is required to guarantee the correct result of the test.

27.22.4.14.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1 – 1.2.

27.22.4.15 PROVIDE LOCAL INFORMATION

27.22.4.15.1 Definition and applicability

See clause 3.2.2.

27.22.4.15.2 Conformance requirement

The ME shall support the PROVIDE LOCAL INFORMATION facility as defined in:

– TS 31.111 [15] clause 6.4.15.

27.22.4.15.3 Test purpose

To verify that the ME returns the following requested local information within a TERMINAL RESPONSE:

– location information:

– Mobile Country Code (MCC);

– Mobile Network Code (MNC);

– Location Area Code (LAC); and

– cell ID of the current serving cell;

– the IMEI of the ME;

– the Network Measurement Results and the BCCH channel list;

– the current date, time and time zone;

– the current ME language setting;

– the Timing Advance;

– the Access Technology;

– the IMEISV;

– the Search Mode change;

– the Battery charge State;

– the UTRAN intra- and inter-frequency measurements;

– the E-UTRAN intra- and inter-frequency measurements

– the CSG ID list and corresponding HNB names of surrounding CSG cells (if class "q" is supported);

– the list of slice(s) information.

If the local information is stored in the ME; otherwise, sends the correct error code to the UICC in the TERMINAL RESPONSE.

To verify that the ME returns required error information in the TERMINAL RESPONSE in case requested information cannot be provided due to missing network coverage.

To verify that the E-UTRAN cell identifier is correctly transmitted when requesting the location information while accessing an E-UTRAN.

To verify that the NG-RAN cell identifier is correctly transmitted when requesting the location information while accessing an NG-RAN SA mode Cell.

To verify that the NG-RAN cell identifier is correctly transmitted when requesting the location information while accessing an NG-RAN Cell.

To verify that the Served S-NSSAIs are correctly transmitted in the TERMINAL RESPONSE when requesting the list of slice(s) information.

27.22.4.15.4 Method of tests

27.22.4.15.4.1 Initial conditions

The ME is connected to the USIM Simulator.

Except for sequences 1.2, 1.4, 1.5, 1.9, 1.10 and 1.11 the ME is connected to the USS and except for sequence 1.10 has performed the location update procedure or routing area update or combined update procedure.

For sequence 1.22, 1.23 and 1.24 the ME is connected to NG-SS and it has performed the Registration procedure.

The NG-RAN parameters of the system simulator are:

– Mobile Country Code (MCC) = 001;

– Mobile Network Code (MNC) = 01;

– Tracking Area Code (TAC) = 000001;

– NG-RAN Cell Identity value = 0001 (36 bits);

– Served S-NSSAIs = 01010103 (SST: MBB, SD: 010103);

The E-UTRAN/NB-IoT parameters of the system simulator are:

– Mobile Country Code (MCC) = 001;

– Mobile Network Code (MNC) = 01;

– Tracking Area Code (TAC) = 0001;

– E-UTRAN Cell Identity value = 0001 (28 bits);

The UTRAN parameters of the system simulator are:

– Mobile Country Code (MCC) = 001;

– Mobile Network Code (MNC) = 01;

– Location Area Code (LAC) = 0001;

– Cell Identity value = 0001;

The GERAN parameters of the system simulator are:

– Mobile Country Code (MCC) = 001;

– Mobile Network Code (MNC) = 01;

– Location Area Code (LAC) = 0001;

– Cell Identity value = 0001;

– Timing advance = 0;

– Neighbour allocations = 561, 565, 568, 569, 573, 575, 577, 581, 582 and 585.

The PCS 1900 parameters of the system simulator are:

– Mobile Country Code (MCC) = 001;

– Mobile Network Code (MNC) = 011;

– Location Area Code (LAC) = 0001;

– Cell Identity value = 0001;

– Timing advance = 0;

– Neighbour allocations = 561, 565, 568, 569, 573, 575, 577, 581, 582 and 585.

The elementary files are coded as the USIM Application Toolkit default with the exception that for sequences 1.14 to 1.18, the default E-UTRAN/EPC UICC is used and for sequence 1.22, 1.23 and 1.24 the default NG-RAN UICC is used.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

Expected sequence 1.3 and 1.6 shall be used on a USS setting up only a GERAN or PCS 1900 cell and expected sequences 1.7 and 1.12 shall be used on a USS setting up only a UTRAN cell.

Expected sequence 1.12 requires 2 UTRA cells on the same frequency and 1.13 requires 2 UTRA cells on different frequencies.

Expected sequences 1.14 and 1.17 shall be used on a E-USS/NB-SS setting up only a E-UTRAN/NB-IoT cell.

Expected sequence 1.22, 1.23 and 1.24 shall be used on a NG-SS setting up only a NG-RAN cell.

Expected sequence 1.15 requires 2 E-UTRA cells on the same frequency and 1.16 requires 2 E-UTRA cells on different frequencies, with second cell having EARFCN less than maxEARFCN. For both sequences if the USIM request is triggered in the RRC_CONNECTED state, the system simulator shall configure the corresponding frequency measurement for a sufficient period before sending the USIM request.

Expected sequence 1.18 requires 2 E-UTRAN cells configured in CSG mode.

For sequence 1.18 the default E-UTRAN/EPC UICC is used and the E-USS transmits on 2 cells with the following parameters:

Network parameters for cell 1:

– TAI (MCC/MNC/TAC): 001/01/0001.

– Access control: unrestricted.

– csg-Indication: TRUE

– csg-Identity: 01 (27 bits)

– Home (e)NB Name Home ONE

Network parameters for cell 2:

– TAI (MCC/MNC/TAC): 001/01/0002.

– Access control: unrestricted.

– csg-Indication: TRUE

– csg-Identity: 02 (27 bits)

– Home (e)NB Name Home TWO

27.22.4.15.4.2 Procedure

Expected Sequence 1.1 (PROVIDE LOCAL INFORMATION, Local Info (MCC, MNC, LAC & Cell ID))

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING PROVIDE LOCAL INFORMATION 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.1.1
4	ME → UICC	TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.1.1A or TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.1.1B	[Command performed successfully, MCC MNC LAC and Cell Identity as USS, option A shall apply for 3GPP parameters] [Command performed successfully, MCC MNC LAC and Cell Identity as USS, option B shall apply for PCS1900 parameters]

PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.1.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "00" Location information (MCC MNC LAC and Cell Identity)

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.1.1A

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "00" Location information (MCC MNC LAC and Cell Identity)

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Location Information

MCC & MNC: MCC = 001, MNC = 01

Location Area Code: 0001

Cell Identity Value: 0001

Extended Cell Identity Value: RNC-id value (for Rel-4 onwards), see also Note 2

Coding:

BER-TLV:	81	03	01	26	00	82	02	82	81	83	01	00
	93	Note 1	00	F1	10	00	01	00	01	Note 2

Note 1: Depending on the presence of the Extended Cell Identity Value the length is ’07’ or ’09’

Note 2: The Extended Cell Identity Value is present in Rel-4 and onwards implementations, the values of the two bytes shall not be verified

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.1.1B

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "00" Location information (MCC MNC LAC and Cell Identity)

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Location Information

MCC & MNC: MCC = 001, MNC = 011

Location Area Code: 0001

Cell Identity Value: 0001

Coding:

BER-TLV:	81	03	01	26	00	82	02	82	81	83	01	00
	93	07	00	11	10	00	01	00	01

Expected Sequence 1.2 (PROVIDE LOCAL INFORMATION, IMEI of the ME)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING PROVIDE LOCAL INFORMATION 1.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.2.1
4	ME → UICC	TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.2.1	[Command performed successfully, IMEI as declared in A.2/23, coded according to TS 24.008 [10], clause 10.5.1, but spare digit shall be zero when transmitted by the ME]

PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.2.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "01" IMEI of the ME

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.2.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "01" IMEI of the ME

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

IMEI

IMEI of the ME: The IMEI of the ME

The result coding depends on the Mobile IMEI value as declared in table A.2/23.

Coding:

BER-TLV:	81	03	01	26	01	82	02	82	81	83	01	00
	94	08	XX	XX	XX	XX	XX	XX	XX	XX

As an example, if the IMEI of the mobile is "123456789012345" then XX XX XX XX XX XX XX XX = 1A 32 54 76 98 10 32 04. For further details see also TS 24.008 [10], clause 10.5.1.

Expected Sequence 1.3 (PROVIDE LOCAL INFORMATION, Network Measurement Results (NMR))

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING PROVIDE LOCAL INFORMATION 1.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.3.1
4	ME → UICC	TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.3.1	[Command performed successfully, NMR as USS ]

PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.3.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "02" Network Measurement Results

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.3.1

The actual values of the measurements are not tested.

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "02" Network Measurement Results

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Network Measurement Results RXLEV-FULL-SERVING-CELL=52, BA not used, DTX not used, as an example in the BER-TLV)

BCCH channel list 561, 565, 568, 569, 573, 575, 577, 581, 582 and 585

Coding:

BER-TLV:	81	03	01	26	02	82	02	82	81	83	01	00
	96	10	34	34	00	00	00	00	00	00	00	00
	00	00	00	00	00	00	9D	0D	8C	63	58	E2
	39	8F	63	F9	06	45	91	A4	90

Expected Sequence 1.4 (PROVIDE LOCAL INFORMATION, Date, Time, Time Zone)

See ETSI TS 102 384 [26] in clause 27.22.4.15.4.2, Expected Sequence 1.4.

Expected Sequence 1.5 (PROVIDE LOCAL INFORMATION, Language setting)

See ETSI TS 102 384 [26] in clause 27.22.4.15.4.2, Expected Sequence 1.5.

Expected Sequence 1.6 (PROVIDE LOCAL INFORMATION, Timing advance)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING PROVIDE LOCAL INFORMATION 1.6.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.6.1
4	ME → UICC	TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.6.1	[Command performed successfully]

PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.6.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "05" Timing Advance

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.6.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "05" Timing Advance

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Timing Advance 2 bytes

ME status: "00" ME is in idle state

Timing Advance: 0

Coding:

BER-TLV:	81	03	01	26	05	82	02	82	81	83	01	00
	AE	02	00	00

Expected Sequence 1.7 (PROVIDE LOCAL INFORMATION, Access Technology

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING PROVIDE LOCAL INFORMATION 1.7.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.7.1
4	ME → UICC	TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.7.1	[Command performed successfully]

PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.7.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "06" Access Technology

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.7.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "06" Access Technology

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Access Technology

Technology: UTRAN

Coding:

BER-TLV:	81	03	01	26	06	82	02	82	81	83	01	00
	3F	01	03

Expected Sequence 1.8 (Void)

Expected Sequence 1.9 (PROVIDE LOCAL INFORMATION, IMEISV of the terminal)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING PROVIDE LOCAL INFORMATION 1.9.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.9.1
4	ME → UICC	TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.9.1	[Command performed successfully, IMEISV as declared in A.2/24, coded as defined in TS 24.008 [10]]

PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.9.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "08" IMEISV of the ME

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.9.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "08" IMEISV of the ME

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

IMEISV

IMEISV of the ME: The IMEISV of the ME

The result coding depends on the ME IMEISV value as declared in table A.2/24.

Coding:

BER-TLV:	81	03	01	26	08	82	02	82	81	83	01	00
	E2	09	XX	XX	XX	XX	XX	XX	XX	XX	XX

As an example, if the IMEISV of the ME is "1234567890123456" then XX XX XX XX XX XX XX XX XX= 13 32 54 76 98 10 32 54 F6. For further details see also TS 24.008 [10].

Expected Sequence 1.10 (PROVIDE LOCAL INFORMATION, Network Search Mode)

Step	Direction	MESSAGE / Action	Comments
1	User	The user sets the ME to manual network selection mode
2	UICC → ME	PROACTIVE COMMAND PENDING PROVIDE LOCAL INFORMATION 1.10.1
3	ME → UICC	FETCH
4	UICC → ME	PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.10.1
5	ME → UICC	TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.10.1	[Command performed successfully]
6	User	The user selects automatic network selection mode
7	UICC → ME	PROACTIVE COMMAND PENDING PROVIDE LOCAL INFORMATION 1.10.2
8	ME → UICC	FETCH
9	UICC → ME	PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.10.2
10	ME → UICC	TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.10.2	[Command performed successfully]

PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.10.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "09" Search Mode

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.10.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "09" Search Mode

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Network Search Mode Manual mode

Coding:

BER-TLV:	81	03	01	26	09	82	02	82	81	83	01	00
	65	01	00

PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.10.2

same as PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.10.1

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.10.2

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "09" Search Mode

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Network Search Mode Automatic mode

Coding:

BER-TLV:	81	03	01	26	09	82	02	82	81	83	01	00
	65	01	01

Expected Sequence 1.11 (PROVIDE LOCAL INFORMATION, charge state of the battery)

See ETSI TS 102 384 [26] in clause 27.22.4.15.4.2, Expected Sequence 1.11.

Expected Sequence 1.12 (PROVIDE LOCAL INFORMATION, Intra-Frequency UTRAN Measurements)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING PROVIDE LOCAL INFORMATION 1.12.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.12.1
4	ME → UICC	TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.12.1	[Command performed successfully]

PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.12.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "02" Network Measurement Results

Device identities

Source device: UICC

Destination device: ME

UTRAN/E-UTRAN Measurement Qualifier

UTRAN/E-UTRAN Measurement Qualifier: "01" Intra-frequency measurements

Coding:

BER-TLV:	D0	0C	81	03	01	26	02	82	02	81	82	69
	01	01

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.12.1

The actual values of the measurements are not tested.

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "02" Network Measurement Results

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Network Measurement Results MEASUREMENT REPORT message

intraFreqMeasuredResultsList

Coding:

BER-TLV:	81	03	01	26	02	82	02	82	81	83	01	00
	96	Note 1	80	Note 2	Note 3	Note 4

Note 1: This is the length indicator for the following bytes which represent the Measurement report coded in ASN.1 and therefore the length cannot be foreseen.

Note2: This byte shall be checked bitwise against pattern: 0000 xxxx (x – don’t care).

Note 3: This byte shall be checked bitwise against pattern: x000 0111 (x – don’t care).

Note 4: The remaining bytes shall not be verified.

The network measurement result indicated by the sequence of bytes above is:

MeasurementReport

measurementIdentity

measuredResults: intraFreqMeasuredResultsList ( 0 )

intraFreqMeasuredResultsList

CellMeasuredResults

modeSpecificInfo: fdd ( 0 )

fdd

primaryCPICH-Info

cpich-Ec-N0

cpich-RSCP

pathloss

Expected Sequence 1.13 (PROVIDE LOCAL INFORMATION, Inter-frequency UTRAN Measurements)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING PROVIDE LOCAL INFORMATION 1.13.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.13.1
4	ME → UICC	TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.13.1	[Command performed successfully]

PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.13.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "02" Network Measurement Results

Device identities

Source device: UICC

Destination device: ME

UTRAN/E-UTRAN Measurement Qualifier

UTRAN/E-UTRAN Measurement Qualifier: "02" Inter-frequency measurements

Coding:

BER-TLV:	D0	0C	81	03	01	26	02	82	02	81	82	69
	01	02

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.13.1

The actual values of the measurements are not tested.

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "02" Network Measurement Results

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Network Measurement Results MEASUREMENT REPORT message

interFreqMeasuredResultsList

Coding:

BER-TLV:	81	03	01	26	02	82	02	82	81	83	01	00
	96	Note 1	80	Note 2	Note 3	Note 4	Note 4	Note 5	Note 6	Note 7

Note 1: This is the length indicator for the following bytes which represent the Measurement report coded in ASN.1 and therefore the length cannot be foreseen.

Note2: This byte shall be checked bitwise against pattern: 0001 xxx1 (x – don’t care).

Note 3: This byte shall be checked bitwise against pattern: 1100 xxxx (x – don’t care).

Note 4: This byte shall not be verified.

Note 5: This byte shall be checked bitwise against pattern: xxxx xx00 (x – don’t care).

Note 6: This byte shall be checked bitwise against pattern: 0011 1xxx (x – don’t care).

Note 7: The remaining bytes shall not be verified.

The network measurement result indicated by the sequence of bytes above is:

MeasurementReport

measurementIdentity

MeasuredResults: interFreqMeasuredResultsList InterFreqMeasuredResultsList ( 1 )

interFreqMeasuredResultsList

InterFreqMeasuredResults

frequencyInfo

utra-CarrierRSSI

interFreqCellMeasuredResultsList

CellMeasuredResults

modeSpecificInfo: fdd ( 0 )

fdd

primaryCPICH-Info

cpich-Ec-N0

cpich-RSCP

pathloss

Expected Sequence 1.14 (PROVIDE LOCAL INFORMATION, Access Technology, E-UTRAN)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING PROVIDE LOCAL INFORMATION 1.14.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.14.1
4	ME → UICC	TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.14.1	[Command performed successfully]

PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.14.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "06" Access Technology

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.14.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "06" Access Technology

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Access Technology

Technology: E-UTRAN

Coding:

BER-TLV:	81	03	01	26	06	82	02	82	81	83	01	00
	3F	01	08

Expected Sequence 1.15 (PROVIDE LOCAL INFORMATION, E-UTRAN Intra-Frequency Measurements)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING PROVIDE LOCAL INFORMATION 1.15.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.15.1
4	ME → UICC	TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.15.1	[Command performed successfully]

PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.15.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "02" Network Measurement Results

Device identities

Source device: UICC

Destination device: ME

UTRAN/E-UTRAN Measurement Qualifier

UTRAN/E-UTRAN Measurement Qualifier: "05" E-UTRAN Intra-frequency measurements

Coding:

BER-TLV:	D0	0C	81	03	01	26	02	82	02	81	82	69
	01	05

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.15.1

The actual values of the measurements are not tested.

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "02" Network Measurement Results

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Network Measurement Results MEASUREMENT REPORT message

measResultNeighCells

Coding:

BER-TLV:	81	03	01	26	02	82	02	82	81	83	01	00
	96	Note 1	02	Note 2	Note 3	Note 4	Note 5

Note 1: This is the length indicator for the following bytes which represent the Measurement report coded in ASN.1 and therefore the length cannot be foreseen.

Note 2: This byte shall be checked bitwise against pattern: 0000 xxxx (x – don’t care).

Note 3: This byte shall not be verified.

Note 4: This byte shall be checked bitwise against pattern: x000 xxxx (x – don’t care).

Note 5: The remaining bytes shall not be verified.

The network measurement result indicated by the sequence of bytes above is:

Network Measurement results:
measurementReport
criticalExtensions: c1 (0)
c1: measurementReport-r8 (0)
measurementReport-r8
measResults
… {Not Verified}
measResultNeighCells:
… {Not Verified}

Expected Sequence 1.16 (PROVIDE LOCAL INFORMATION, E-UTRAN Inter-Frequency Measurements)

Step	Direction	MESSAGE / Action	Comments
1	ME	Terminal is in RRC idle state
2	UICC → ME	PROACTIVE COMMAND PENDING PROVIDE LOCAL INFORMATION 1.16.1
3	ME → UICC	FETCH
4	UICC → ME	PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.16.1
5	ME → UICC	TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.16.1	[Command performed successfully, limited service]

PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.16.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "02" Network Measurement Results

Device identities

Source device: UICC

Destination device: ME

UTRAN/E-UTRAN Measurement Qualifier

UTRAN/E-UTRAN Measurement Qualifier: "06" E-UTRAN Inter-frequency measurements

Coding:

BER-TLV:	D0	0C	81	03	01	26	02	82	02	81	82	69
	01	06

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.16.1

The actual values of the measurements are not tested.

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "02" Network Measurement Results

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Network Measurement Results Frequency value of inter-frequency E-UTRAN cell and MEASUREMENT REPORT message

measResultNeighCells

Coding:

BER-TLV:	81	03	01	26	02	82	02	82	81	83	01	00
	96	Note 1	Note 2	Note 2	02	Note 3	Note 4	Note 5	Note 6

Note 1: This is the length indicator for the following bytes which contain 2 bytes with the frequency value coded as the ARFCN-ValueEUTRA followed by the Measurement report coded in ASN.1 and therefore the length cannot be foreseen.

Note 2: This is the frequency of the second E-UTRA cell, coded as ARFCN-ValueEUTRA. This byte shall not be verified.

Note 3: This byte shall be checked bitwise against pattern: 0000 xxxx (x – don’t care).

Note 4: This byte shall not be verified.

Note 5: This byte shall be checked bitwise against pattern: x000 xxxx (x – don’t care).

Note 6: The remaining bytes shall not be verified.

Expected Sequence 1.17 (PROVIDE LOCAL INFORMATION, E-UTRAN Local Info (MCC, MNC, TAC & E-UTRAN Cell ID))

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING PROVIDE LOCAL INFORMATION 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.1.1
4	ME → UICC	TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.17.1

PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.1.1

Sames as PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.1.1 in expected sequence 1.1

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.17.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "00" Location information (MCC MNC TAC and E-UTRAN Cell Identity)

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Location Information

MCC & MNC: MCC = 001, MNC = 01

Tracking Area Code: 0001

E-UTRAN Cell Identifier: 0001 (28 bits)

Coding:

BER-TLV:	81	03	01	26	00	82	02	82	81	83	01	00
	93	09	00	F1	10	00	01	00	00	00	1F

Expected Sequence 1.18 (PROVIDE LOCAL INFORMATION, Discovery of surrounding CSG cells)

Step	Direction	MESSAGE / Action	Comments
1	E-USS	Cell 1 is enabled, with csg-indication set to TRUE Cell 2 disabled
2	ME	A manual CSG cell selection is performed.
3	UICC → ME	PROACTIVE COMMAND PENDING PROVIDE LOCAL INFORMATION 1.18.1
4	ME → UICC	FETCH
5	UICC → ME	PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.18.1	1 cell in the list
6	ME → UICC	TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.18.1	[Command performed successfully]
7	E-USS	Cell 2 is enabled, with csg-indication set to TRUE
8	ME	A manual CSG cell selection is performed.
9	UICC → ME	PROACTIVE COMMAND PENDING PROVIDE LOCAL INFORMATION 1.18.1
10	ME → UICC	FETCH
11	UICC → ME	PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.18.1	2 cells in the list
12	ME → UICC	TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.18.2	[Command performed successfully]

PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.18.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "11" CSG ID list and corresponding HNB name

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.18.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "11" CSG ID list and corresponding HNB name

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

CSG ID list Identifier

PLMN MCC = 001, MNC = 01

CSG ID and Name

CSG ID 01 (27 bits)

HNB name Home ONE

Coding:

BER-TLV:	81	03	01	26	11	82	02	82	81	83	01	00
	7E	1C	80	03	00	F1	10	81	15	00	00	00
	3F	80	00	48	00	6F	00	6D	00	65	00	20
	00	4F	00	4E	00	45

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.18.2

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "11" CSG ID list and corresponding HNB name

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

CSG ID list Identifier

PLMN MCC = 001, MNC = 01

CSG ID and Name

CSG ID 01 (27 bits)

HNB name Home ONE

CSG ID and Name

CSG ID 02 (27 bits)

HNB name Home TWO

BER-TLV:	81	03	01	26	11	82	02	82	81	83	01	00
	7E	33	80	03	00	F1	10	81	15	00	00	00
	3F	80	00	48	00	6F	00	6D	00	65	00	20
	00	4F	00	4E	00	45	81	15	00	00	00	5F
	80	00	48	00	6F	00	6D	00	65	00	20	00
	54	00	57	00	4F

Expected Sequence 1.19 (PROVIDE LOCAL INFORMATION, Location Information for Multiple Access Technologies)

TBD

Expected Sequence 1.20 (PROVIDE LOCAL INFORMATION, NMR for Multiple Access Technologies)

TBD

Expected Sequence 1.21 (PROVIDE LOCAL INFORMATION, current access technologies, Multiple Access Technologies)

TBD

NOTE: The above test sequences (1.19, 1.20, 1.21) on Multiple Access Technologies imply the support of one or more non-3GPP access technologies and therefore can not be tested within 3GPP.

Expected Sequence 1.22 (PROVIDE LOCAL INFORMATION, NG-RAN Local Info (MCC, MNC, TAC & NG-RAN Cell ID))

Step	Direction	Message / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING PROVIDE LOCAL INFORMATION 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.1.1
4	ME → UICC	TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.22.1

PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.1.1

Same as PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.1.1 in expected sequence 1.1

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.22.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "00" Location information (MCC MNC TAC and NG-RAN Cell Identity)

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Location Information

MCC & MNC: MCC = 001, MNC = 01

Tracking Area Code: 000001

NG-RAN Cell Identifier: 0001 (36 bits)

Coding:

BER-TLV:	81	03	01	26	00	82	02	82	81	83	01	00
	93	0B	00	F1	10	00	00	01	00	00	00	00
	1F

Expected Sequence 1.23 (PROVIDE LOCAL INFORMATION, Access Technology, NG-RAN)

Step	Direction	Message / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING PROVIDE LOCAL INFORMATION 1.14.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.14.1
4	ME → UICC	TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.23.1	[Command performed successfully]

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.23.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "06" Access Technology

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Access Technology

Technology: 3GPP NR

Coding:

BER-TLV:	81	03	01	26	06	82	02	82	81	83	01	00
	3F	01	0A

Expected Sequence 1.24 (PROVIDE LOCAL INFORMATION, slice(s) information)

Step	Direction	MESSAGE / Action	Comments
1	ME → NG-SS	ME successfully REGISTER with NG-RAN cell.
2	ME → NG-SS	An Internet PDU Session is established successfully.	Served S-NSSAIs = 01010103
3	UICC → ME	PROACTIVE COMMAND PENDING PROVIDE LOCAL INFORMATION 1.24.1
4	ME → UICC	FETCH
5	UICC → ME	PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.24.1
6	ME → UICC	TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.24.1	[Command performed successfully]

PROACTIVE COMMAND: PROVIDE LOCAL INFORMATION 1.24.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "15" slices information

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

TERMINAL RESPONSE: PROVIDE LOCAL INFORMATION 1.24.1

Logically:

Command details

Command number: 1

Command type: PROVIDE LOCAL INFORMATION

Qualifier: "15" slices information

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Slice Information

Number of Served S-NSSAIs: 1

Served S-NSSAI: ’01 01 01 03′ (SST: MBB, SD: 010103)

Coding:

BER-TLV:	81	03	01	26	15	82	02	82	81	83	01	00
	D6	05	01	01	01	01	03

27.22.4.15.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1 to 1.23.

27.22.4.16 SET UP EVENT LIST

27.22.4.16.1 SET UP EVENT LIST (normal)

27.22.4.16.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.16.1.2 Conformance requirement

The ME shall support the Proactive UICC: Set Up Event List facility as defined in:

– TS 31.111 [15] clause 6.4.16 and clause 6.6.16.

Additionally the ME shall support the Event Download: Call Connect and the Event Download: Call Disconnected mechanism as defined in:

– TS 31.111 [15] clause 11.2, clause 11.2.1, clause 11.2.2, clause 11.3, clause 11.3.1 and clause 11.3.2.

27.22.4.16.1.3 Test purpose

To verify that the ME accepts a list of events that it shall monitor the current list of events supplied by the UICC, is able to have this current list of events replaced and is able to have the list of events removed.

To verify that when the ME has successfully accepted or removed the list of events, it shall send TERMINAL RESPONSE (OK) to the UICC and when the ME is not able to successfully accept or remove the list of events, it shall send TERMINAL RESPONSE (Command beyond ME’s capabilities).

27.22.4.16.1.4 Method of test

27.22.4.16.1.4.1 Initial conditions

The ME is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default with the following exceptions.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.16.1.4.2 Procedure

Expected Sequence 1.1 (SET UP EVENT LIST, Set Up Call Connect Event)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP EVENT LIST 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1
4	ME → UICC	TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1
5	UICC → ME	PROACTIVE UICC SESSION ENDED
6	USS → ME	SETUP 1.1.1	[Incoming call alert]
7	USER → ME	User shall accept the incoming call
8	ME → USS	CONNECT 1.1.1
9	ME → UICC	ENVELOPE: EVENT DOWNLOAD CALL CONNECTED 1.1.1	[Call Connected Event]
10	UICC → ME	PROACTIVE UICC SESSION ENDED

PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1

Logically:

Command details

Command number: 1

Command type: SET UP EVENT LIST

Command qualifier: ’00’

Device identities

Source device: UICC

Destination device: ME

Event list

Event 1: Call Connected

Coding:

BER-TLV:	D0	0C	81	03	01	05	00	82	02	81	82	99
	01	01

TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1

Logically:

Command details

Command number: 1

Command type: SET UP EVENT LIST

Command qualifier: ’00’

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

SET UP 1.1.1

Logically:

Transaction identifier

TI value: 0 (bit 5-7)

Address

TON: "Unknown"

NPI: "ISDN/ telephone numbering plan"

Dialling number string: "9876"

CONNECT 1.1.1

Logically:

Transaction identifier

TI value: 0 (bit 5-7)

TI flag: 1 (bit 8)

ENVELOPE: EVENT DOWNLOAD CALL CONNECTED 1.1.1

Logically

Event list

Event 1: Call Connected

Device identities

Source device: ME

Destination device: UICC

Transaction identifier

TI value: 0 (bit 5-7) – If A.1/150 is supported, this shall not be verified

TI flag: 1 (bit 8)

Coding:

BER-TLV:

Expected Sequence 1.2 (SET UP EVENT LIST, Replace Event)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP EVENT LIST 1.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP EVENT LIST 1.2.1	[Call Connected and Call Disconnected Events]
4	ME → UICC	TERMINAL RESPONSE: SET UP EVENT LIST 1.2.1
5	UICC → ME	PROACTIVE COMMAND PENDING: SET UP EVENT LIST 1.2.2
6	ME → UICC	FETCH
7	UICC → ME	PROACTIVE COMMAND: SET UP EVENT LIST 1.2.2	[Call Disconnected Event]
8	ME → UICC	TERMINAL RESPONSE: SET UP EVENT LIST 1.2.2
9	UICC → ME	PROACTIVE UICC SESSION ENDED
10	USS → ME	SETUP 1.2.2	[Incoming call alert]
11	USER → ME	User shall accept the incoming call
12	ME → USS	CONNECT 1.2.2
13	USS → ME	DISCONNECT 1.2.2
14	ME → UICC	ENVELOPE: EVENT DOWNLOAD CALL DISCONNECT 1.2.2A or ENVELOPE: EVENT DOWNLOAD CALL DISCONNECT 1.2.2B	[Call Disconnect Event]
15	UICC → ME	PROACTIVE UICC SESSION ENDED

PROACTIVE COMMAND: SET UP EVENT LIST 1.2.1

Logically:

Command details

Command number: 1

Command type: SET UP EVENT LIST

Command qualifier: ’00’

Device identities

Source device: UICC

Destination device: ME

Event list

Event 1: Call Connected

Event 2: Call Disconnected

Coding:

BER-TLV:	D0	0D	81	03	01	05	00	82	02	81	82	99
	02	01	02

TERMINAL RESPONSE: SET UP EVENT LIST 1.2.1

Logically:

Command details

Command number: 1

Command type: SET UP EVENT LIST

Command qualifier: ’00’

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

PROACTIVE COMMAND: SET UP EVENT LIST 1.2.2

Logically:

Command details

Command number: 1

Command type: SET UP EVENT LIST

Command qualifier: ’00’

Device identities

Source device: UICC

Destination device: ME

Event list

Event 1: Call Disconnected

Coding:

BER-TLV:	D0	0C	81	03	01	05	00	82	02	81	82	99
	01	02

TERMINAL RESPONSE: SET UP EVENT LIST 1.2.2

Logically:

Command details

Command number: 1

Command type: SET UP EVENT LIST

Command qualifier: ’00’

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

SET UP 1.2.2

Logically:

Transaction identifier

TI value: 0 (bit 5-7)

TI flag: 0 (bit 8)

Address

TON: "Unknown"

NPI: "ISDN/ telephone numbering plan"

Dialling number string: "9876"

CONNECT 1.2.2

Logically:

Transaction identifier

TI value: 0 (bit 5-7)

TI flag: 1 (bit 8)

DISCONNECT 1.2.2

Logically:

Transaction identifier

TI value: 0 (bit 5-7)

TI flag: 0 (bit 8)

Cause

Value: Normal call clearing

ENVELOPE: EVENT DOWNLOAD CALL DISCONNECTED 1.2.2A

Logically:

Event list

Event 1: Call Disconnected

Device identities

Source device: Network

Destination device: UICC

Transaction identifier

TI value: 0 (bit 5-7) – If A.1/150 is supported, this shall not be verified

TI flag: 0 (bit 8)

Cause

Value: Normal call clearing

Coding:

BER-TLV:	D6	0E	99	01	02	82	02	83	81	9C	01	00
	9A	02	60	90

ENVELOPE: EVENT DOWNLOAD CALL DISCONNECTED 1.2.2B

Logically:

Event list

Event 1: Call Disconnected

Device identities

Source device: Network

Destination device: UICC

Transaction identifier

TI value: 0 (bit 5-7) – If A.1/150 is supported, this shall not be verified

TI flag: 0 (bit 8)

Cause

Value: Normal call clearing

Coding:

BER-TLV:	D6	0E	99	01	02	82	02	83	81	9C	01	00
	9A	02	E0	90

Expected Sequence 1.3 (SET UP EVENT LIST, Remove Event)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP EVENT LIST 1.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP EVENT LIST 1.3.1	[Call Connected Event]
	ME → UICC	TERMINAL RESPONSE: SET UP EVENT LIST 1.3.1
4	UICC → ME	PROACTIVE COMMAND PENDING: SET UP EVENT LIST 1.3.2
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SET UP EVENT LIST 1.3.2	[Remove Event]
7	ME → UICC	TERMINAL RESPONSE: SET UP EVENT LIST 1.3.2
8	UICC → ME	PROACTIVE UICC SESSION ENDED
10	USS → ME	SETUP 1.3.2	[Incoming call alert]
11	USER → ME	User shall accept the incoming call
12	ME → USS	CONNECT 1.3.2
13	ME → UICC	No ENVELOPE: EVENT DOWNLOAD (call connected) sent
14	USS → ME	DISCONNECT 1.3.2

PROACTIVE COMMAND: SET UP EVENT LIST 1.3.1

Logically:

Command details

Command number: 1

Command type: SET UP EVENT LIST

Command qualifier: ’00’

Device identities

Source device: UICC

Destination device: ME

Event list

Event 1: Call Connected

Coding:

BER-TLV:	D0	0C	81	03	01	05	00	82	02	81	82	99
	01	01

TERMINAL RESPONSE: SET UP EVENT LIST 1.3.1

Logically:

Command details

Command number: 1

Command type: SET UP EVENT LIST

Command qualifier: ’00’

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

PROACTIVE COMMAND: SET UP EVENT LIST 1.3.2

Logically:

Command details

Command number: 1

Command type: SET UP EVENT LIST

Command qualifier: ’00’

Device identities

Source device: UICC

Destination device: ME

Event list: Empty

Coding:

BER-TLV:	D0	0B	81	03	01	05	00	82	02	81	82	99
	00

TERMINAL RESPONSE: SET UP EVENT LIST 1.3.2

Logically:

Command details

Command number: 1

Command type: SET UP EVENT LIST

Command qualifier: ’00’

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

SET UP 1.3.2

Logically:

Transaction identifier

Ti value: 0 (bit 5-7)

Ti flag: 0 (bit 8)

Address

TON: "Unknown"

NPI: "ISDN/ telephone numbering plan"

Dialling number string: "9876"

CONNECT 1.3.2

Logically:

Transaction identifier

Ti value: 0 (bit 5-7)

Ti flag: 1 (bit 8)

DISCONNECT 1.3.2

Logically:

Transaction identifier

Ti value: 0 (bit 5-7)

Ti flag: 0 (bit 8)

Cause

Value: Normal call clearing

Expected Sequence 1.4 (SET UP EVENT LIST, Remove Event on ME Power Cycle)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP EVENT LIST 1.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP EVENT LIST 1.4.1	[Call Connected Event]
	ME → UICC	TERMINAL RESPONSE: SET UP EVENT LIST 1.4.1
4	UICC → ME	PROACTIVE UICC SESSION ENDED
5	User → ME	Power off ME
6	User → ME	Power on ME
7	USS → ME	SETUP 1.4.1	[Incoming call alert]
8	USER → ME	User shall accept the incoming call
9	ME → USS	CONNECT 1.4.1
10	ME → UICC	No ENVELOPE: EVENT DOWNLOAD (call connected) sent
11	USS → ME	DISCONNECT 1.4.1

PROACTIVE COMMAND: SET UP EVENT LIST 1.4.1

Logically:

Command details

Command number: 1

Command type: SET UP EVENT LIST

Command qualifier: ’00’

Device identities

Source device: UICC

Destination device: ME

Event list

Event 1: Call Connected

Coding:

BER-TLV:	D0	0C	81	03	01	05	00	82	02	81	82	99
	01	01

TERMINAL RESPONSE: SET UP EVENT LIST 1.4.1

Logically:

Command details

Command number: 1

Command type: SET UP EVENT LIST

Command qualifier: ’00’

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

SET UP 1.4.1

Logically:

Transaction identifier

Ti value: 0 (bit 5-7)

Ti flag: 0 (bit 8)

Address

TON: "Unknown"

NPI: "ISDN/ telephone numbering plan"

Dialling number string: "9876"

CONNECT 1.4.1

Logically:

Transaction identifier

Ti value: 0 (bit 5-7)

Ti flag: 1 (bit 8)

DISCONNECT 1.4.1

Logically:

Transaction identifier

Ti value: 0 (bit 5-7)

Ti flag: 0 (bit 8)

Cause

Value: Normal call clearing

27.22.4.16.1.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1 to 1.4.

27.22.4.17 PERFORM CARD APDU

27.22.4.17.1 PERFORM CARD APDU (normal)

27.22.4.17.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.17.1.2 Conformance requirement

The ME shall support the Proactive UICC: Perform Card APDU facility as defined in:

– TS 31.111 [15] clause 6.1, clause 5.2, clause 6.4.17, clause 6.6.17, clause 6.8, clause 8.6, clause 8.7, clause 8.35, clause 8.36 and clause 8.12.9.

Additionally the ME shall support multiple card operation as defined in:

– TS 31.111 [15] clause 6.4.19, clause 6.6.19, clause 6.4.18 and clause 6.6.18.

27.22.4.17.1.3 Test purpose

To verify that the ME sends an APDU command to the additional card identified in the PERFORM CARD APDU proactive UICC command, and successfully returns the result of the execution of the command in the TERMINAL RESPONSE command send to the UICC.

The ME-Manufacturer can assign the card reader identifier from 0 to 7.

This test applies for MEs with only one additional card reader.

In this particular case the card reader identifier 1 is chosen.

In this particular case a special Test-SIM (TestSIM) with T=0 protocol is chosen as additional card for the additional ME card reader (for coding of the TestSIM see annex A).

27.22.4.17.1.4 Method of test

27.22.4.17.1.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The TestSIM is inserted in the additional ME card reader.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

If the ME supports a detachable card reader, the card reader shall be attached to the ME.

The elementary files of the TestSIM are coded as defined in annex A. Another card with different parameters may be used as TestSIM to execute these tests. In this case the USIM Simulator shall take into account the corresponding response data.

27.22.4.17.1.4.2 Procedure

Expected Sequence 1.1 (PERFORM CARD APDU, card reader 1, additional card inserted, Select MF and Get Response)

See ETSI TS 102 384 [26] in clause 27.22.4.17.1.4.2, Expected Sequence 1.1.

Expected Sequence 1.2 (PERFORM CARD APDU, card reader 1, additional card inserted, Select DF GSM, Select EF PLMN , Update Binary, Read Binary on EF PLMN)

See ETSI TS 102 384 [26] in clause 27.22.4.17.1.4.2, Expected Sequence 1.2.

Expected Sequence 1.3 (PERFORM CARD APDU, card reader 1, card inserted, card powered off)

See ETSI TS 102 384 [26] in clause 27.22.4.17.1.4.2, Expected Sequence 1.3.

Expected Sequence 1.4 (PERFORM CARD APDU, card reader 1, no card inserted)

See ETSI TS 102 384 [26] in clause 27.22.4.17.1.4.2, Expected Sequence 1.4.

Expected Sequence 1.5 (PERFORM CARD APDU, card reader 7 (which is not the valid card reader identifier of the additional ME card reader))

See ETSI TS 102 384 [26] in clause 27.22.4.17.1.4.2, Expected Sequence 1.5.

27.22.4.17.1.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1 to 1.5.

27.22.4.17.2 PERFORM CARD APDU (detachable card reader)

27.22.4.17.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.17.2.2 Conformance requirement

27.22.4.17.2.3 Test purpose

27.22.4.17.2.4 Method of test

27.22.4.17.2.4.1 Initial conditions

The ME is connected to the USIM Simulator.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The card reader shall be detached from the ME.

27.22.4.17.2.4.2 Procedure

Expected Sequence 2.1 (PERFORM CARD APDU, card reader 1, card reader detached)

See ETSI TS 102 384 [26] in clause 27.22.4.17.2.4.2, Expected Sequence 2.1.

27.22.4.17.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 2.1.

27.22.4.18 POWER OFF CARD

27.22.4.18.1 POWER OFF CARD (normal)

27.22.4.18.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.18.1.2 Conformance requirement

The ME shall support the Proactive UICC: Power Off Card facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.18, clause 6.6.18, clause 8.6, clause 8.7, clause 8.12, clause 8.12.9, clause 5.2 and annex H.

27.22.4.18.1.3 Test purpose

To verify that the ME closes a session with the additional card identified in the POWER OFF CARD proactive UICC command, and successfully returns result in the TERMINAL RESPONSE command send to the UICC.

The ME-Manufacturer can assign the card reader identifier from 0 to 7.

This test applies for MEs with only one additional card reader.

In this particular case the card reader identifier 1 is chosen.

27.22.4.18.1.4 Method of test

27.22.4.18.1.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The ME card reader is connected to aSIM Simulator (SIM2). Instead of a SIM Simulator a card with different parameters may be used as SIM2 to execute these tests. In this case the USIM Simulator shall take into account the corresponding response data.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

If the ME supports a detachable card reader, the card reader shall be attached to the ME.

Prior to this test the ME shall have powered on the SIM Simulator (SIM2).

27.22.4.18.1.4.2 Procedure

Expected Sequence 1.1 (POWER OFF CARD, card reader 1)

See ETSI TS 102 384 [26] in clause 27.22.4.18.1.4.2, Expected Sequence 1.1.

Expected Sequence 1.2 (POWER OFF CARD, card reader 1, no card inserted)

See ETSI TS 102 384 [26] in clause 27.22.4.18.1.4.2, Expected Sequence 1.2.

27.22.4.18.1.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1 to 1.2.

27.22.4.18.2 POWER OFF CARD (detachable card reader)

27.22.4.18.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.18.2.2 Conformance requirement

Void.

27.22.4.18.2.3 Test purpose

27.22.4.18.2.4 Method of test

27.22.4.18.2.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The ME card reader is connected to a SIM Simulator (SIM2).

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

Prior to this test the ME shall have powered on the SIM Simulator (SIM2).

The card reader shall be detached from the ME.

27.22.4.18.2.4.2 Procedure

Expected Sequence 2.1 (POWER OFF CARD, card reader 1, no card reader attached)

See ETSI TS 102 384 [26] in clause 27.22.4.18.2.4.2, Expected Sequence 2.1.

27.22.4.18.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 2.1.

27.22.4.19 POWER ON CARD

27.22.4.19.1 POWER ON CARD (normal)

27.22.4.19.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.19.1.2 Conformance requirement

The ME shall support the Proactive UICC: Power On Card facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.19, clause 6.6.19, clause 8.6, clause 8.7, clause 8.12, clause 8.12.9, clause 8.34, clause 5.2 and annex H.

27.22.4.19.1.3 Test purpose

To verify that the ME starts a session with the additional card identified in the POWER ON CARD proactive UICC command, and successfully returns the Answer To Reset within the TERMINAL RESPONSE command send to the UICC.

The ME-Manufacturer can assign the card reader identifier from 0 to 7.

This test applies for MEs with only one additional card reader.

In this particular case the card reader identifier 1 is chosen.

27.22.4.19.1.4 Method of test

27.22.4.19.1.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The ME card reader is connected to a SIM Simulator (SIM2). Instead of the SIM Simulator a card with different parameters may be used as SIM2 to execute these tests. In this case the USIM Simulator shall take into account the corresponding response data.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

If the ME supports a detachable card reader, the card reader shall be attached to the ME.

27.22.4.19.1.4.2 Procedure

Expected Sequence 1.1 (POWER ON CARD, card reader 1)

See ETSI TS 102 384 [26] in clause 27.22.4.19.1.4.2, Expected Sequence 1.1.

Expected Sequence 1.2 (POWER ON CARD, card reader 1, no ATR)

See ETSI TS 102 384 [26] in clause 27.22.4.19.1.4.2, Expected Sequence 1.2.

Expected Sequence 1.3 (POWER ON CARD, card reader 1, no card inserted)

See ETSI TS 102 384 [26] in clause 27.22.4.19.1.4.2, Expected Sequence 1.3.

27.22.4.19.1.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1 to 1.3.

27.22.4.19.2 POWER ON CARD (detachable card reader)

27.22.4.19.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.19.2.2 Conformance requirement

27.22.4.19.2.3 Test purpose

27.22.4.19.2.4 Method of test

27.22.4.19.2.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default with the following exceptions.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The card reader shall be detached from the ME.

27.22.4.19.2.4.2 Procedure

Expected Sequence 2.1 (POWER ON CARD, card reader 1, no card reader attached)

See ETSI TS 102 384 [26] in clause 27.22.4.19.2.4.2, Expected Sequence 2.1.

27.22.4.19.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 2.1.

27.22.4.20 GET READER STATUS

27.22.4.20.1 GET READER STATUS (normal)

27.22.4.20.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.20.1.2 Conformance requirement

The ME shall support the Proactive UICC: Get Card Reader Status facility as defined in:

– TS 31.111 [15] clause 6.1, clause 5.2, clause 6.4.20, clause 6.6.20, clause 6.8, clause 8.6, clause 8.7, clause 8.33, clause 8.57 and annex H.

Additionally the ME shall support multiple card operation as defined in:

– TS 31.111 [15] clause 6.4.19, clause 6.6.19, clause 6.4.18 and clause 6.6.18.

27.22.4.20.1.3 Test purpose

To verify that the ME sends starts a session with the additional card identified in the GET CARD READER STATUS proactive UICC command, and successfully returns information about all interfaces to additional card reader(s) in the TERMINAL RESPONSE command send to the UICC.

The ME-Manufacturer can assign the card reader identifier from 0 to 7.

This test applies for MEs with only one additional card reader.

In this particular case the card reader identifier 1 is chosen.

In this test case the SIM-Simulator (SIM2) shall response with the ATR "3B 00".

27.22.4.20.1.4 Method of test

27.22.4.20.1.4.1 Initial conditions

The ME shall support the Proactive UICC: Get Card Reader Status (Card Reader Status) facility. The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

If the ME supports a detachable card reader, the card reader shall be attached to the ME.

Prior to this test the ME shall have powered on the SIM Simulator (SIM2).

27.22.4.20.1.4.2 Procedure

Expected Sequence 1.1 (GET CARD READER STATUS, card reader 1, card inserted, card powered)

See ETSI TS 102 384 [26] in clause 27.22.4.20.1.4.2, Expected Sequence 1.1.

Expected Sequence 1.2 (GET CARD READER STATUS, card reader 1, card inserted, card not powered)

See ETSI TS 102 384 [26] in clause 27.22.4.20.1.4.2, Expected Sequence 1.2.

Expected Sequence 1.3 (GET CARD READER STATUS, card reader 1, card not present)

See ETSI TS 102 384 [26] in clause 27.22.4.20.1.4.2, Expected Sequence 1.3.

27.22.4.20.1.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1 to 1.3.

27.22.4.20.2 GET CARD READER STATUS (detachable card reader)

27.22.4.20.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.20.2.2 Conformance requirement

Void.

27.22.4.20.2.3 Test purpose

To verify that the ME closes a session with the additional card identified in the GET CARD READER STATUS proactive UICC command, and successfully returns result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.20.2.4 Method of test

27.22.4.20.2.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

Prior to this test the ME shall have powered on the SIM Simulator (SIM2).

The card reader shall be detached from the ME.

27.22.4.20.2.4.2 Procedure

Expected Sequence 2.1 (GET CARD READER STATUS, no card reader attached)

See ETSI TS 102 384 [26] in clause 27.22.4.20.2.4.2, Expected Sequence 2.1.

27.22.4.20.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 2.1.

27.22.4.21 TIMER MANAGEMENT and ENVELOPE TIMER EXPIRATION

27.22.4.21.1 TIMER MANAGEMENT (normal)

27.22.4.21.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.21.1.2 Conformance Requirement

The ME shall support the TIMER MANAGEMENT as defined in:

– TS 31.111 [15] clause 5.2, clause 6.4.21, clause 6.8, clause 8.6, clause 8.7, clause 8.37 and clause 8.38.

27.22.4.21.1.3 Test purpose

To verify that the ME manages correctly its internal timers, start a timer, deactivate a timer or return the current value of a timer according to the Timer Identifier defined in the TIMER MANAGEMENT proactive UICC command.

27.22.4.21.1.4 Method of Test

27.22.4.21.1.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default with the following exceptions.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The ME screen shall be in its normal stand-by display.

27.22.4.21.1.4.2 Procedure

Expected Sequence 1.1 (TIMER MANAGEMENT, start timer 1 several times, get the current value of the timer and deactivate the timer successfully)

See ETSI TS 102 384 [26] in clause 27.22.4.21.1.4.2, Expected Sequence 1.1.

Expected Sequence 1.2 (TIMER MANAGEMENT, start timer 2 several times, get the current value of the timer and deactivate the timer successfully)

See ETSI TS 102 384 [26] in clause 27.22.4.21.1.4.2, Expected Sequence 1.2.

Expected Sequence 1.3 (TIMER MANAGEMENT, start timer 8 several times, get the current value of the timer and deactivate the timer successfully)

See ETSI TS 102 384 [26] in clause 27.22.4.21.1.4.2, Expected Sequence 1.3.

Expected Sequence1.4 (TIMER MANAGEMENT, try to get the current value of a timer which is not started: action in contradiction with the current timer state)

See ETSI TS 102 384 [26] in clause 27.22.4.21.1.4.2, Expected Sequence 1.4.

Expected Sequence1.5 (TIMER MANAGEMENT, try to deactivate a timer which is not started: action in contradiction with the current timer state)

See ETSI TS 102 384 [26] in clause 27.22.4.21.1.4.2, Expected Sequence 1.5.

Expected Sequence 1.6 (TIMER MANAGEMENT, start 8 timers successfully)

See ETSI TS 102 384 [26] in clause 27.22.4.21.1.4.2, Expected Sequence 1.6.

27.22.4.21.1.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1 to 1.6.

27.22.4.21.2 ENVELOPE TIMER EXPIRATION (normal)

27.22.4.21.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.21.2.2 Conformance requirement

The ME shall support the ENVELOPE (TIMER EXPIRATION) command as defined in the following technical specifications:

– TS 31.111 [15] clause 4.10, clause 7.4.1 and clause 7.4.2.

The ME shall support the TIMER MANAGEMENT as defined in the following technical specifications:

– TS 31.111 [15] clause 5.2, clause 6.4.21, clause 6.8, clause 8.6, clause 8.7, clause 8.37 and clause 8.38.

27.22.4.21.2.3 Test purpose

To verify that the ME shall pass the identifier of the timer that has expired and its value using the ENVELOPE (TIMER EXPIRATION) command, when a timer previously started in a TIMER MANAGEMENT proactive command expires.

27.22.4.21.2.4 Method of test

27.22.4.21.2.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default with the following exceptions.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The timer 1 is not started.

When the UICC is busy when the envelope TIMER EXPIRATION is sent, either the ME retries periodically to send the envelope or it waits for a status not indicating busy.

27.22.4.21.2.4.2 Procedure

Expected Sequence 2.1 (TIMER EXPIRATION, pending proactive UICC command)

See ETSI TS 102 384 [26] in clause 27.22.4.21.2.4.2, Expected Sequence 2.1.

Expected Sequence 2.2 (TIMER EXPIRATION, UICC application toolkit busy)

See ETSI TS 102 384 [26] in clause 27.22.4.21.2.4.2, Expected Sequence 2.2.

27.22.4.21.2.5 Test requirement

The ME shall operate in the manner defined in expected sequences 2.1 to 2.2.

27.22.4.22 SET UP IDLE MODE TEXT

27.22.4.22.1 SET UP IDLE MODE TEXT (normal)

27.22.4.22.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.22.1.2 Conformance requirement

– TS 31.111 [15] clause 4.7, clause 5.2, clause 6.4.22, clause 6.6.22, clause 6.4.16, clause 6.6.16, clause 7.5.6, clause 6.8, clause 7.5, clause 7.5.1, clause 8.25, clause 6.4.7 and clause 6.6.13.

Additionally the ME shall support the REFRESH proactive UICC facility as defined in:

– TS 31.111 [15] clause 5.2, clause 6.1, clause 6.4.7, clause 6.6.13, clause 6.11, clause 8.6, clause 8.7, clause 8.12, clause 9.4 and clause 10.

27.22.4.22.1.3 Test purpose

To verify that the text passed to the ME is displayed as idle mode text.

27.22.4.22.1.4 Method of test

27.22.4.22.1.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.22.1.4.2 Procedure

Expected Sequence 1.1 (SET UP IDLE MODE TEXT, display idle mode text)

See ETSI TS 102 384 [26] in clause 27.22.4.22.1.4.2, Expected Sequence 1.1.

Expected Sequence 1.2 (SET UP IDLE MODE TEXT, replace idle mode text)

See ETSI TS 102 384 [26] in clause 27.22.4.22.1.4.2, Expected Sequence 1.2.

Expected Sequence 1.3 (SET UP IDLE MODE TEXT, remove idle mode text)

See ETSI TS 102 384 [26] in clause 27.22.4.22.1.4.2, Expected Sequence 1.3.

Expected Sequence 1.4 (SET UP IDLE MODE TEXT, competing information on ME display)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP IDLE MODE TEXT 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP IDLE MODE TEXT 1.1.1	["Idle Mode Text"]
4	ME → UICC	TERMINAL RESPONSE: SET UP IDLE MODE TEXT 1.1.1	[Command performed successfully]
5	USER → ME	Select idle screen	Only if idle screen not already available
6	ME → USER	Display "Idle Mode Text"
7	USS → ME	SMS PP 1.4.1	[Display immediate SMS]
8	ME → USER	Display "Test Message"
9	USER → ME	Clear display and select idle screen
10	ME → USER	Display "Idle Mode Text"
11	UICC → ME	PROACTIVE COMMAND PENDING: DISPLAY TEXT 1.4.1
12	ME → UICC	FETCH
13	UICC → ME	PROACTIVE COMMAND: DISPLAY TEXT 1.4.1	[Normal priority, wait for user to clear message, unpacked, 8 bit data]
14	ME → USER	Display "Toolkit Test 1"
15	USER → ME	Clear Message
16	ME → UICC	TERMINAL RESPONSE: DISPLAY TEXT 1.4.1	[Command performed successfully]
17	ME → USER	Display "Idle Mode Text"
18	UICC → ME	PROACTIVE COMMAND PENDING: PLAY TONE 1.4.1
19	ME → UICC	FETCH
20	UICC → ME	PROACTIVE COMMAND: PLAY TONE 1.4.1
21	ME → USER	Display "Dial Tone" Play a standard supervisory dial tone through the external ringer for a duration of 5 s
22	ME → UICC	TERMINAL RESPONSE: PLAY TONE 1.4.1	[Command performed successfully]
23	UICC → ME	PROACTIVE UICC SESSION ENDED
24	ME → USER	Display "Idle Mode Text"

SMS-PP 1.4.1

Logically:

SMS TPDU

TP-MTI SMS-DELIVER

TP-MMS No more messages waiting for the MS in this SC

TP-RP TP-Reply-Path is not set in this SMS-DELIVER

TP-UDHI TP-UD field contains only the short message

TP-SRI A status report will not be returned to the ME

TP-OA

TON International number

NPI "ISDN / telephone numbering plan"

Address value "1234"

TP-PID "00"

TP-DCS

Coding Group General Data Coding

Compression Text is uncompressed

Message Class Class 0

Alphabet GSM 7 bit default alphabet

TP-SCTS: 01/01/98 00:00:00 +0

TP-UDL 12

TP-UD "Test Message"

Coding:

Coding	04	04	91	21	43	00	10	89	10	10	00	00
	00	00	0C	D4	F2	9C	0E	6A	96	E7	F3	F0
	B9	0C

PROACTIVE COMMAND: DISPLAY TEXT 1.4.1

Logically:

Command details

Command number: 1

Command type: DISPLAY TEXT

Command qualifier: normal priority, wait for user to clear message

Device identities

Source device: UICC

Destination device: Display

Text String

Data coding scheme: unpacked, 8 bit data

Text: "Toolkit Test 1"

Coding:

BER-TLV:	D0	1A	81	03	01	21	80	82	02	81	02	8D
	0F	04	54	6F	6F	6C	6B	69	74	20	54	65
	73	74	20	31

TERMINAL RESPONSE: DISPLAY TEXT 1.4.1

Logically:

Command details

Command number: 1

Command type: DISPLAY TEXT

Command qualifier: normal priority, wait for user to clear message

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

PROACTIVE COMMAND: PLAY TONE 1.4.1

Logically:

Command details

Command number: 1

Command type: PLAY TONE

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Earpiece

Alpha identifier: "Dial Tone"

TONe: Standard supervisory tones: dial tone

Duration

Time unit: Seconds

Time interval: 5

Coding:

BER-TLV:	D0	1B	81	03	01	20	00	82	02	81	03	85
	09	44	69	61	6C	20	54	6F	6E	65	8E	01
	01	84	02	01	05

TERMINAL RESPONSE: PLAY TONE 1.4.1

Logically:

Command details

Command number: 1

Command type: PLAY TONE

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 1.5 (SET UP IDLE MODE TEXT, ME power cycled)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP IDLE MODE TEXT 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP IDLE MODE TEXT 1.1.1	["Idle Mode Text"]
4	ME → UICC	TERMINAL RESPONSE: SET UP IDLE MODE TEXT 1.1.1	[command performed successfully]
5	USER → ME	Select idle screen	Only if idle screen not already available
6	ME → USER	Display "Idle Mode Text"
7	USER → ME	Power off ME
8	ME ⇔ UICC	3G Session TERMINATION PROCEDURE
9	USER → ME	Power on ME
10	ME ⇔ UICC	3G Session ACTIVATION PROCEDURE
11	ME ⇔ UICC	USIM INITIALIZATION
12	USER → ME	Select idle screen	Only if idle screen not already available
13	ME → USER	Display idle screen / "Idle Mode Text" not to be displayed

Expected Sequence 1.6 (SET UP IDLE MODE TEXT, REFRESH with USIM Initialization)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SET UP IDLE MODE TEXT 1.1.1	[Idle Mode Text]
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SET UP IDLE MODE TEXT 1.1.1
4	ME → UICC	TERMINAL RESPONSE: SET UP IDLE MODE TEXT 1.1.1
5	USER → ME	Select idle screen	Only if idle screen not already available
6	ME → USER	Display "Idle Mode Text"
7	UICC → ME	PROACTIVE COMMAND PENDING: REFRESH 1.6.1
8	ME → UICC	FETCH
9	UICC → ME	PROACTIVE COMMAND: REFRESH 1.6.1	[USIM Initialization]
10	ME ⇔ UICC	USIM INITIALIZATION
11	USER → ME	Select idle screen	Only if idle screen not already available
12	ME → USER	Display idle screen / "Idle Mode Text" not to be displayed
13	ME → UICC	TERMINAL RESPONSE: REFRESH 1.6.1A or TERMINAL RESPONSE: REFRESH 1.6.1B	[Command performed successfully] [Command performed successfully with additional files read]
14	UICC → ME	PROACTIVE UICC SESSION ENDED

PROACTIVE COMMAND: REFRESH 1.6.1

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: USIM Initialization

Device identities

Source device: UICC

Destination device: ME

Coding:

BER-TLV:

TERMINAL RESPONSE: REFRESH 1.6.1A

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: USIM Initialization

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

TERMINAL RESPONSE: REFRESH 1.6.1B

Logically:

Command details

Command number: 1

Command type: REFRESH

Command qualifier: USIM Initialization

Device identities

Source device: ME

Destination device: UICC

Result

General Result: REFRESH performed with additional EFs read

Coding:

BER-TLV:

Expected Sequence 1.7 (SET UP IDLE MODE TEXT, large text string)

See ETSI TS 102 384 [26] in clause 27.22.4.22.1.4.2, Expected Sequence 1.7.

27.22.4.22.1.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1 to 1.7.

27.22.4.22.2 SET UP IDLE MODE TEXT (Icon support)

27.22.4.22.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.22.2.2 Conformance requirement

27.22.4.22.2.3 Test purpose

To verify that the ME text and / or icon passed to the ME is displayed by the ME as an idle mode text.

To verify that the icon identifier provided with the text string can replace the text string or accompany it.

To verify that if both an alpha identifier or text string, and an icon are provided with a proactive command, and both are requested to be displayed, but the ME is not able to display both together on the screen, then the alpha identifier or text string takes precedence over the icon.

To verify that if the UICC provides an icon identifier with a proactive command, then the ME shall inform the UICC if the icon could not be displayed by sending the general result "Command performed successfully, but requested icon could not be displayed".

To verify that if the ME receives an icon identifier with a proactive command, and either an empty, or no alpha identifier / text string is given by the UICC, than the ME shall reject the command with general result "Command data not understood by ME".

27.22.4.22.2.4 Method of test

27.22.4.22.2.4.1 Initial conditions

The ME is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in update idle mode on the System Simulator.

27.22.4.22.2.4.2 Procedure

Expected Sequence 2.1A (SET UP IDLE MODE TEXT, Icon is self-explanatory, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.22.2.4.2, Expected Sequence 2.1A.

Expected Sequence 2.1B (SET UP IDLE MODE TEXT, Icon is self-explanatory, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.22.2.4.2, Expected Sequence 2.1B.

Expected Sequence 2.2A (SET UP IDLE MODE TEXT, Icon is not self-explanatory, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.22.2.4.2, Expected Sequence 2.2A.

Expected Sequence 2.2B (SET UP IDLE MODE TEXT, Icon is not self-explanatory, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.22.2.4.2, Expected Sequence 2.2B.

Expected Sequence 2.3A (SET UP IDLE MODE TEXT, Icon is self-explanatory, colour icon, successful)

See ETSI TS 102 384 [26] in clause 27.22.4.22.2.4.2, Expected Sequence 2.3A.

Expected Sequence 2.3B (SET UP IDLE MODE TEXT, Icon is self-explanatory, colour icon, requested icon could not be displayed)

See ETSI TS 102 384 [26] in clause 27.22.4.22.2.4.2, Expected Sequence 2.3B.

Expected Sequence 2.4 (SET UP IDLE MODE TEXT, Icon is not self-explanatory, empty text string)

See ETSI TS 102 384 [26] in clause 27.22.4.22.2.4.2, Expected Sequence 2.4.

27.22.4.22.2.5 Test requirement

The ME shall operate in the manner defined in expected sequences 2.1A to 2.4.

27.22.4.22.3 SET UP IDLE MODE TEXT (UCS2 support)

27.22.4.22.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.22.3.2 Conformance requirement

The ME shall support the UCS2 facility for the coding of the Cyrillic alphabet, as defined in:

– ISO/IEC 10646 [17].

27.22.4.22.3.3 Test purpose

To verify that the UCS2 coded text string is displayed by the ME as an idle mode text.

27.22.4.22.3.4 Method of test

27.22.4.22.3.4.1 Initial conditions

The ME is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in update idle mode on the System Simulator..

27.22.4.22.3.4.2 Procedure

Expected Sequence 3.1 (SET UP IDLE MODE TEXT, UCS2 alphabet text)

See ETSI TS 102 384 [26] in clause 27.22.4.22.3.4.2, Expected Sequence 3.1.

27.22.4.22.3.5 Test requirement

The ME shall operate in the manner defined in expected sequence 3.1.

27.22.4.22.4 SET UP IDLE MODE TEXT (support of Text Attribute)

27.22.4.22.4.1 SET UP IDLE MODE TEXT (support of Text Attribute – Left Alignment)

27.22.4.22.4.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.22.4.1.2 Conformance requirement

– TS 31.111 [15] clause 4.7, clause 5.2, clause 6.4.22, clause 6.6.22, clause 6.4.16, clause 6.6.16, clause 7.5.6, clause 6.8, clause 7.5, clause 7.5.1, clause 8.25, clause 8.70, clause 6.4.7 and clause 6.6.13.

27.22.4.22.4.1.3 Test purpose

To verify that the text passed to the ME is displayed as idle mode text according to the left alignment text attribute configuration.

27.22.4.22.4.1.4 Method of test

27.22.4.22.4.1.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.22.4.1.4.2 Procedure

Expected Sequence 4.1 (SET UP IDLE MODE TEXT, display idle mode text, Text Attribute – Left Alignment)

See ETSI TS 102 384 [26] in clause 27.22.4.22.4.1.4.2, Expected Sequence 4.1.

27.22.4.22.4.1.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.1.

27.22.4.22.4.2 SET UP IDLE MODE TEXT (support of Text Attribute – Center Alignment)

27.22.4.22.4.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.22.4.2.2 Conformance requirement

27.22.4.22.4.2.3 Test purpose

To verify that the text passed to the ME is displayed as idle mode text according to the center alignment text attribute configuration.

27.22.4.22.4.2.4 Method of test

27.22.4.22.4.2.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.22.4.2.4.2 Procedure

Expected Sequence 4.2 (SET UP IDLE MODE TEXT, display idle mode text, Text Attribute – Center Alignment)

See ETSI TS 102 384 [26] in clause 27.22.4.22.4.2.4.2, Expected Sequence 4.2.

27.22.4.22.4.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.2.

27.22.4.22.4.3 SET UP IDLE MODE TEXT (support of Text Attribute – Right Alignment)

27.22.4.22.4.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.22.4.3.2 Conformance requirement

27.22.4.22.4.3.3 Test purpose

To verify that the text passed to the ME is displayed as idle mode text according to the right alignment text attribute configuration.

27.22.4.22.4.3.4 Method of test

27.22.4.22.4.3.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.22.4.3.4.2 Procedure

Expected Sequence 4.3 (SET UP IDLE MODE TEXT, display idle mode text, Text Attribute – Right Alignment)

See ETSI TS 102 384 [26] in clause 27.22.4.22.4.3.4.2, Expected Sequence 4.3.

27.22.4.22.4.3.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.3.

27.22.4.22.4.4 SET UP IDLE MODE TEXT (support of Text Attribute – Large Font Size)

27.22.4.22.4.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.22.4.4.2 Conformance requirement

27.22.4.22.4.4.3 Test purpose

To verify that the text passed to the ME is displayed as idle mode text according to the large font size text attribute configuration.

27.22.4.22.4.4.4 Method of test

27.22.4.22.4.4.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.22.4.4.4.2 Procedure

Expected Sequence 4.4 (SET UP IDLE MODE TEXT, display idle mode text, Text Attribute – Large Font Size)

See ETSI TS 102 384 [26] in clause 27.22.4.22.4.4.4.2, Expected Sequence 4.4.

27.22.4.22.4.4.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.4.

27.22.4.22.4.5 SET UP IDLE MODE TEXT (support of Text Attribute – Small Font Size)

27.22.4.22.4.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.22.4.5.2 Conformance requirement

27.22.4.22.4.5.3 Test purpose

To verify that the text passed to the ME is displayed as idle mode text according to the small font size text attribute configuration.

27.22.4.22.4.5.4 Method of test

27.22.4.22.4.5.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.22.4.5.4.2 Procedure

Expected Sequence 4.5 (SET UP IDLE MODE TEXT, display idle mode text, Text Attribute – Small Font Size)

See ETSI TS 102 384 [26] in clause 27.22.4.22.4.5.4.2, Expected Sequence 4.5.

27.22.4.22.4.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.5.

27.22.4.22.4.6 SET UP IDLE MODE TEXT (support of Text Attribute – Bold On)

27.22.4.22.4.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.22.4.6.2 Conformance requirement

27.22.4.22.4.6.3 Test purpose

To verify that the text passed to the ME is displayed as idle mode text according to the bold text attribute configuration.

27.22.4.22.4.6.4 Method of test

27.22.4.22.4.6.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.22.4.6.4.2 Procedure

Expected Sequence 4.6 (SET UP IDLE MODE TEXT, display idle mode text, Text Attribute – Bold On)

See ETSI TS 102 384 [26] in clause 27.22.4.22.4.6.4.2, Expected Sequence 4.6.

27.22.4.22.4.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.6.

27.22.4.22.4.7 SET UP IDLE MODE TEXT (support of Text Attribute – Italic On)

27.22.4.22.4.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.22.4.7.2 Conformance requirement

27.22.4.22.4.7.3 Test purpose

To verify that the text passed to the ME is displayed as idle mode text according to the italic text attribute configuration.

27.22.4.22.4.7.4 Method of test

27.22.4.22.4.7.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.22.4.7.4.2 Procedure

Expected Sequence 4.7 (SET UP IDLE MODE TEXT, display idle mode text, Text Attribute – Italic On)

See ETSI TS 102 384 [26] in clause 27.22.4.22.4.7.4.2, Expected Sequence 4.7.

27.22.4.22.4.7.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.7.

27.22.4.22.4.8 SET UP IDLE MODE TEXT (support of Text Attribute – Underline On)

27.22.4.22.4.8.1 Definition and applicability

See clause 3.2.2.

27.22.4.22.4.8.2 Conformance requirement

27.22.4.22.4.8.3 Test purpose

To verify that the text passed to the ME is displayed as idle mode text according to the underline text attribute configuration.

27.22.4.22.4.8.4 Method of test

27.22.4.22.4.8.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.22.4.8.4.2 Procedure

Expected Sequence 4.8 (SET UP IDLE MODE TEXT, display idle mode text, Text Attribute – Underline On)

See ETSI TS 102 384 [26] in clause 27.22.4.22.4.8.4.2, Expected Sequence 4.8.

27.22.4.22.4.8.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.8.

27.22.4.22.4.9 SET UP IDLE MODE TEXT (support of Text Attribute – Strikethrough On)

27.22.4.22.4.9.1 Definition and applicability

See clause 3.2.2.

27.22.4.22.4.9.2 Conformance requirement

27.22.4.22.4.9.3 Test purpose

To verify that the text passed to the ME is displayed as idle mode text according to the strikethrough text attribute configuration.

27.22.4.22.4.9.4 Method of test

27.22.4.22.4.9.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.22.4.9.4.2 Procedure

Expected Sequence 4.9 (SET UP IDLE MODE TEXT, display idle mode text, Text Attribute – Strikethrough On)

See ETSI TS 102 384 [26] in clause 27.22.4.22.4.9.4.2, Expected Sequence 4.9.

27.22.4.22.4.9.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.9.

27.22.4.22.4.10 SET UP IDLE MODE TEXT (support of Text Attribute – Foreground and Background Colour)

27.22.4.22.4.10.1 Definition and applicability

See clause 3.2.2.

27.22.4.22.4.10.2 Conformance requirement

27.22.4.22.4.10.3 Test purpose

To verify that the text passed to the ME is displayed as idle mode text according to the foreground and background colour text attribute configuration.

27.22.4.22.4.10.4 Method of test

27.22.4.22.4.10.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.22.4.10.4.2 Procedure

Expected Sequence 4.10 (SET UP IDLE MODE TEXT, display idle mode text, Text Attribute – Foreground and Background Colour)

See ETSI TS 102 384 [26] in clause 27.22.4.22.4.10.4.2, Expected Sequence 4.10.

27.22.4.22.4.10.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.10.

27.22.4.22.5 SET UP IDLE MODE TEXT (UCS2 display in Chinese)

27.22.4.22.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.22.5.2 Conformance requirement

The Terminal shall additionally support the UCS2 facility for the coding of the Chinese character, as defined in:

ISO/IEC 10646 [17a/17b].

27.22.4.22.5.3 Test purpose

To verify that the UCS2 coded text string is displayed by the ME as an idle mode text.

27.22.4.22.5.4 Method of test

27.22.4.22.5.4.1 Initial conditions

The Terminal is connected to both the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the Terminal shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.22.5.4.2 Procedure

Expected Sequence 5.1 (SET UP IDLE MODE TEXT, UCS2 alphabet text in Chinese)

See ETSI TS 102 384 [26] in clause 27.22.4.22.5.4.2, Expected Sequence 5.1.

27.22.4.22.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 5.1.

27.22.4.22.6 SET UP IDLE MODE TEXT (UCS2 display in Katakana)

27.22.4.22.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.22.6.2 Conformance requirement

The ME shall additionally support the UCS2 facility for the coding of the Katakana character, as defined in:

ISO/IEC 10646 [17a/17b].

27.22.4.22.6.3 Test purpose

To verify that the UCS2 coded text string is displayed by the ME as an idle mode text.

27.22.4.22.6.4 Method of test

27.22.4.22.6.4.1 Initial conditions

The ME is connected to both the UICC Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.22.6.4.2 Procedure

Expected Sequence 6.1 (SET UP IDLE MODE TEXT, UCS2 alphabet text in Katakana)

See ETSI TS 102 384 [26] in clause 27.22.4.22.6.4.2, Expected Sequence 6.1.

27.22.4.22.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.1.

27.22.4.23 RUN AT COMMAND

27.22.4.23.1 RUN AT COMMAND (normal)

27.22.4.23.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.23.1.2 Conformance requirement

The ME shall support the Proactive UICC: RUN AT COMMAND facility as defined in:

– TS 31.111 [15] clause 6.4.23, clause 6.6.23, clause 5.2, clause 6.8, clause 8.6, clause 8.7, clause 8.2, clause 8.40, clause 8.31 and clause 8.41.

– TS 27.007 [18].

27.22.4.23.1.3 Test purpose

To verify that the ME responds to an AT Command contained within a RUN AT COMMAND as though it were initiated by an attached TE, and returns an AT Response within a TERMINAL RESPONSE to the UICC.

27.22.4.23.1.4 Method of test

27.22.4.23.1.4.1 Initial conditions

The ME is connected to the USIM Simulator. The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

Prior to the test the ME shall be connected to the TE.

The TA-TE interface is set to 8-bit operation.

27.22.4.23.1.4.2 Procedure

Expected Sequence 1.1(RUN AT COMMAND, no alpha identifier presented, request IMSI)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 1.1.1	[no alpha identifier, request IMSI]
4	ME (→ User)	The ME may give information to the user concerning what is happening
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 1.1.1	[Command performed successfully, AT Response containing IMSI]

PROACTIVE COMMAND: RUN AT COMMAND 1.1.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

AT Command

AT Command string: "AT+CIMI<CR>"

Coding:

BER-TLV:	D0	13	81	03	01	34	00	82	02	81	82	A8
	08	41	54	2B	43	49	4D	49	0D

TERMINAL RESPONSE: RUN AT COMMAND 1.1.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

AT Response

AT Response string: <CR><LF>IMSI<CR><LF><CR><LF>OK<CR><LF>

Coding:

BER-TLV:	81	03	01	34	00	82	02	82	81	83	01	00
	A9	19	0D	0A	30	30	31	30	31	30	31	32
	33	34	35	36	37	38	39	0D	0A	0D	0A	4F
	4B	0D	0A

Expected Sequence 1.2 (RUN AT COMMAND, null data alpha identifier presented, request IMSI)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 1.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 1.2.1	[null data alpha identifier, request IMSI]
4	ME	The ME should not give any information to user on the fact that the ME is performing an AT command
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 1.1.1	[Command performed successfully, AT Response containing IMSI]

PROACTIVE COMMAND: RUN AT COMMAND 1.2.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier null data object

AT Command

AT Command string: "AT+CIMI<CR>"

Coding:

BER-TLV:	D0	15	81	03	01	34	00	82	02	81	82	85
	00	A8	08	41	54	2B	43	49	4D	49	0D

Expected Sequence 1.3 (RUN AT COMMAND, alpha identifier presented, request IMSI)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 1.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 1.3.1	[alpha identifier, request IMSI]
4	ME → USER	Display "Run AT Command"
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 1.1.1	[Command performed successfully, AT Response containing IMSI]

PROACTIVE COMMAND: RUN AT COMMAND 1.3.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command"

AT Command

AT Command string: "AT+CIMI<CR>"

Coding:

BER-TLV:	D0	23	81	03	01	34	00	82	02	81	82	⁸5
	0E	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	A8	08	41	54	2B	43	49	4D	49
	0D

27.22.4.23.1.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1 to 1.3.

27.22.4.23.2 RUN AT COMMAND (Icon support)

27.22.4.23.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.23.2.2 Conformance requirement

The ME shall support the Proactive UICC: RUN AT COMMAND facility as defined in:

– TS 31.111 [15] clause 6.4.23, clause 6.6.23, clause 5.2, clause 6.8, clause 8.6, clause 8.7, clause 8.2, clause 8.40, clause 8.31 and clause 8.41.

– TS 27.007 [18].

27.22.4.23.2.3 Test purpose

To verify that the ME responds to an AT Command contained within a RUN AT COMMAND as though it were initiated by an attached TE, and returns an AT Response within a TERMINAL RESPONSE to the UICC.

27.22.4.23.2.4 Method of test

27.22.4.23.2.4.1 Initial conditions

The ME is connected to the USIM Simulator. The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

Prior to the test the ME shall be connected to the TE.

The TA-TE interface is set to 8-bit operation.

The ME screen shall be in its normal stand-by display.

27.22.4.23.2.4.2 Procedure

Expected Sequence 2.1A (RUN AT COMMAND, basic icon self explanatory, request IMSI, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 2.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 2.1.1	[BASIC-ICON, self-explanatory, request IMSI]
4	ME → USER	Display BASIC ICON without the alpha identifier
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 2.1.1A	[Command performed successfully, AT response containing IMSI]

PROACTIVE COMMAND: RUN AT COMMAND 2.1.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha identifier: "Basic Icon"

AT Command

AT Command string: "AT+CIMI<CR>"

Icon identifier:

Icon qualifier: icon is self-explanatory

Icon identifier: record 1 in EF_(IMG)

Coding:

BER-TLV:	D0	23	81	03	01	34	00	82	02	81	82	85
	0A	42	61	73	69	63	20	49	63	6F	6E	A8
	08	41	54	2B	43	49	4D	49	0D	9E	02	00
	01

TERMINAL RESPONSE: RUN AT COMMAND 2.1.1A

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

AT Response

AT Response string: <CR><LF>IMSI<CR><LF><CR><LF>OK<CR><LF>

Coding:

BER-TLV:	81	03	01	34	00	82	02	82	81	83	01	00
	A9	19	0D	0A	30	30	31	30	31	30	31	32
	33	34	35	36	37	38	39	0D	0A	0D	0A	4F
	4B	0D	0A

Expected Sequence 2.1B (RUN AT COMMAND, basic icon self explanatory, request IMSI, requested icon could not be displayed)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 2.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 2.1.1	[BASIC-ICON, self-explanatory, request IMSI]
4	ME → USER	Display "Basic Icon" without the BASIC-ICON
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 2.1.1B	[Command performed but requested icon could not be displayed, AT response containing IMSI]

TERMINAL RESPONSE: RUN AT COMMAND 2.1.1B

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully, but requested icon could not be displayed

AT Response

AT Response string: <CR><LF>IMSI<CR><LF><CR><LF>OK<CR><LF>

Coding:

BER-TLV:	81	03	01	34	00	82	02	82	81	83	01	04
	A9	19	0D	0A	30	30	31	30	31	30	31	32
	33	34	35	36	37	38	39	0D	0A	0D	0A	4F
	4B	0D	0A

Expected Sequence 2.2A (RUN AT COMMAND, colour icon self explanatory, request IMSI, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 2.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 2.2.1	[COLOUR-ICON, self-explanatory, request IMSI]
4	ME → USER	Display COLOUR-ICON without the alpha identifier
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 2.1.1A	[Command performed successfully, AT response containing IMSI]

PROACTIVE COMMAND: RUN AT COMMAND 2.2.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha identifier: "Colour Icon"

AT Command

AT Command string: "AT+CIMI<CR>"

Icon identifier:

Icon qualifier: icon is self-explanatory

Icon identifier: record 2 in EF_(IMG)

Coding:

BER-TLV:	D0	24	81	03	01	34	00	82	02	81	82	A8
	0B	43	6F	6C	6F	75	72	20	49	63	6F	6E
	A8	08	41	54	2B	43	49	4D	49	0D	9E	02
	00	02

Expected Sequence 2.2B (RUN AT COMMAND, colour icon self explanatory, request IMSI, requested icon could not be displayed)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 2.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 2.2.1	[COLOUR-ICON, self-explanatory, request IMSI]
4	ME → USER	Display "Colour Icon" without the COLOUR-ICON
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 2.1.1B	[Command performed but requested icon could not be displayed, AT response containing IMSI]

Expected Sequence 2.3A (RUN AT COMMAND, basic icon non self-explanatory, request IMSI, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 2.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 2.3.1	[BASIC-ICON, non self-explanatory, request IMSI]
4	ME → USER	Display "Basic Icon" and BASIC-ICON
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 2.1.1A	[Command performed successfully, AT response containing IMSI]

PROACTIVE COMMAND: RUN AT COMMAND 2.3.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha identifier: "Basic Icon"

AT Command

AT Command string: "AT+CIMI<CR>"

Icon identifier

Icon qualifier: icon is non self-explanatory

Icon identifier: record 1 in EF_(IMG)

Coding:

BER-TLV:	D0	23	81	03	01	34	00	82	02	81	82	85
	0A	42	61	73	69	63	20	49	63	6F	6E	A8
	08	41	54	2B	43	49	4D	49	0D	9E	02	01
	01

Expected Sequence 2.3B (RUN AT COMMAND, basic icon non self-explanatory, request IMSI, requested icon could not be displayed)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 2.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 2.3.1	[BASIC-ICON, non self-explanatory, request IMSI]
4	ME → USER	Display "Basic Icon" without BASIC-ICON
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 2.1.1B	[Command performed but requested icon could not be displayed, AT response containing IMSI]

Expected Sequence 2.4A (RUN AT COMMAND, colour icon non self-explanatory, request IMSI, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 2.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 2.4.1	[COLOUR-ICON, non self-explanatory, request IMSI]
4	ME → USER	Display "Colour Icon" and COLOUR-ICON
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 2.1.1A	[Command performed successfully, AT response containing IMSI]

PROACTIVE COMMAND: RUN AT COMMAND 2.4.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha identifier: "Colour Icon"

AT Command

AT Command string: "AT+CIMI<CR>"

Icon identifier:

Icon qualifier: icon is self-explanatory

Icon identifier: record 2 in EF_(IMG)

Coding:

BER-TLV:	D0	24	81	03	01	34	00	82	02	81	82	85
	0B	43	6F	6C	6F	75	72	20	49	63	6F	6E
	A8	08	41	54	2B	43	49	4D	49	0D	9E	02
	01	02

Expected Sequence 2.4B (RUN AT COMMAND, colour icon non self-explanatory, request IMSI, requested icon could not be displayed)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 2.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 2.4.1	[COLOUR-ICON, non self-explanatory, request IMSI]
4	ME → USER	Display "Colour Icon" without COLOUR-ICON
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 2.1.1B	[Command performed but requested icon could not be displayed, AT response containing IMSI]

Expected Sequence 2.5 (RUN AT COMMAND, basic icon non self-explanatory, no alpha identifier presented)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 2.5.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 2.5.1	[BASIC-ICON, non self-explanatory]
4	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 2.5.1	[Command data not understood by ME]

PROACTIVE COMMAND: RUN AT COMMAND 2.5.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

AT Command

AT Command string: "AT+CIMI<CR>"

Icon identifier

Icon qualifier: icon is non self-explanatory

Icon identifier: record 1 in EF_(IMG)

Coding:

BER-TLV:	D0	17	81	03	01	34	00	82	02	81	82	A8
	08	41	54	2B	43	49	4D	49	0D	9E	02	01
	01

TERMINAL RESPONSE: RUN AT COMMAND 2.5.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Result

General Result: Command data not understood by ME

Coding:

BER-TLV:

27.22.4.23.2.5 Test requirement

The ME shall operate in the manner defined in expected sequences 2.1 to 2.5.

27.22.4.23.3 RUN AT COMMAND (support of Text Attribute)

27.22.4.23.3.1 RUN AT COMMAND (support of Text Attribute – Left Alignment)

27.22.4.23.3.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.23.3.1.2 Conformance requirement

The ME shall support the Proactive UICC: RUN AT COMMAND facility as defined in:

– TS 31.111 [15] clause 6.4.23, clause 6.6.23, clause 5.2, clause 6.8, clause 8.6, clause 8.7, clause 8.2, clause 8.40, clause 8.31, clause 8.41 and clause 8.70.

– TS 27.007 [18].

The terminal shall support the text attribute.

27.22.4.23.3.1.3 Test purpose

To verify that the ME responds to an AT Command contained within a RUN AT COMMAND with left alignment text attribute as though it were initiated by an attached TE, and returns an AT Response within a TERMINAL RESPONSE to the UICC.

27.22.4.23.3.1.4 Method of test

27.22.4.23.3.1.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

Prior to the test the ME shall be connected to the TE.

The TA-TE interface is set to 8-bit operation.

27.22.4.23.3.1.4.2 Procedure

Expected Sequence 3.1(RUN AT COMMAND, with alpha identifier presented, request IMSI, Text Attribute – Left Alignment)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.1.1
4	ME (→ USER)	Display "Run AT Command 1"	[alpha identifier is displayed with left alignment, request IMSI]
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.1.1	[Command performed successfully, AT Response containing IMSI]
6	UICC → ME	PROACTIVE UICC SESSION ENDED
7	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.1.2
8	ME → UICC	FETCH
9	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.1.2
10	ME (→ USER)	Display "Run AT Command 2"	[Message shall be formatted without left alignment, request IMSI. Remark: If left alignment is the ME’s default alignment as declared in table A.2/16, no alignment change will take place]
11	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.1.1	[Command performed successfully, AT Response containing IMSI]
12	UICC → ME	PROACTIVE UICC SESSION ENDED

PROACTIVE COMMAND: RUN AT COMMAND 3.1.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 1"

AT Command

AT Command string: "AT+CIMI<CR>"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Right Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2B	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	31	A8	07	41	54	2B	43	49
	4D	49	0D	D0	04	00	10	00	B4

PROACTIVE COMMAND: RUN AT COMMAND 3.1.2

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 2"

AT Command

AT Command string: "AT+CIMI<CR>"

Coding:

BER-TLV:	D0	25	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	32	A8	08	41	54	2B	43	49
	4D	49	0D

TERMINAL RESPONSE: RUN AT COMMAND 3.1.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

AT Response

AT Response string: <CR><LF>IMSI<CR><LF><CR><LF>OK<CR><LF>

Coding:

BER-TLV:	81	03	01	34	00	82	02	82	81	83	01	00
	A9	19	0D	0A	30	30	31	30	31	30	31	32
	33	34	35	36	37	38	39	0D	0A	0D	0A	4F
	4B	0D	0A

27.22.4.23.3.1.5 Test requirement

The ME shall operate in the manner defined in expected sequence 3.1.

27.22.4.23.3.2 RUN AT COMMAND (support of Text Attribute – Center Alignment)

27.22.4.23.3.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.23.3.2.2 Conformance requirement

The ME shall support the Proactive UICC: RUN AT COMMAND facility as defined in:

– TS 31.111 [15] clause 6.4.23, clause 6.6.23, clause 5.2, clause 6.8, clause 8.6, clause 8.7, clause 8.2, clause 8.40, clause 8.31, clause 8.41 and clause 8.70.

– TS 27.007 [18].

The terminal shall support the text attribute.

27.22.4.23.3.2.3 Test purpose

To verify that the ME responds to an AT Command contained within a RUN AT COMMAND with center alignment text attribute as though it were initiated by an attached TE, and returns an AT Response within a TERMINAL RESPONSE to the UICC.

27.22.4.23.3.2.4 Method of test

27.22.4.23.3.2.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

Prior to the test the ME shall be connected to the TE.

The TA-TE interface is set to 8-bit operation.

27.22.4.23.3.2.4.2 Procedure

Expected Sequence 3.2(RUN AT COMMAND, with alpha identifier presented, request IMSI, Text Attribute – Center Alignment)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.2.1
4	ME (→ USER)	Display "Run AT Command 1"	[alpha identifier is displayed with center alignment, request IMSI]
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.2.1	[Command performed successfully, AT Response containing IMSI]
6	UICC → ME	PROACTIVE UICC SESSION ENDED
7	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.2.2
8	ME → UICC	FETCH
9	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.2.2
10	ME (→ USER)	Display "Run AT Command 2"	[Message shall be formatted without center alignment, request IMSI. Remark: If center alignment is the ME’s default alignment as declared in table A.2/16, no alignment change will take place]
11	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.2.1	[Command performed successfully, AT Response containing IMSI]
12	UICC → ME	PROACTIVE UICC SESSION ENDED

PROACTIVE COMMAND: RUN AT COMMAND 3.2.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 1"

AT Command

AT Command string: "AT+CIMI<CR>"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Center Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2A	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	31	A8	07	41	54	2B	43	49
	4D	49	0D	D04	04	00	10	01	B4

PROACTIVE COMMAND: RUN AT COMMAND 3.2.2

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 2"

AT Command

AT Command string: "AT+CIMI<CR>"

Coding:

BER-TLV:	D0	25	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	32	A8	08	41	54	2B	43	49
	4D	49	0D

TERMINAL RESPONSE: RUN AT COMMAND 3.2.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

AT Response

AT Response string: <CR><LF>IMSI<CR><LF><CR><LF>OK<CR><LF>

Coding:

BER-TLV:	81	03	01	34	00	82	02	82	81	83	01	00
	A9	19	0D	0A	30	30	31	30	31	30	31	32
	33	34	35	36	37	38	39	0D	0A	0D	0A	4F
	4B	0D	0A

27.22.4.23.3.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 3.2.

27.22.4.23.3.3 RUN AT COMMAND (support of Text Attribute – Right Alignment)

27.22.4.23.3.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.23.3.3.2 Conformance requirement

The ME shall support the Proactive UICC: RUN AT COMMAND facility as defined in:

– TS 31.111 [15] clause 6.4.23, clause 6.6.23, clause 5.2, clause 6.8, clause 8.6, clause 8.7, clause 8.2, clause 8.40, clause 8.31, clause 8.41 and clause 8.70.

– TS 27.007 [18].

The terminal shall support the text attribute.

27.22.4.23.3.3.3 Test purpose

To verify that the ME responds to an AT Command contained within a RUN AT COMMAND with right alignment text attribute as though it were initiated by an attached TE, and returns an AT Response within a TERMINAL RESPONSE to the UICC.

27.22.4.23.3.3.4 Method of test

27.22.4.23.3.3.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

Prior to the test the ME shall be connected to the TE.

The TA-TE interface is set to 8-bit operation.

27.22.4.23.3.3.4.2 Procedure

Expected Sequence 3.3(RUN AT COMMAND, with alpha identifier presented, request IMSI, Text Attribute – Right Alignment)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.3.1
4	ME (→ USER)	Display "Run AT Command 1"	[alpha identifier is displayed with right alignment, request IMSI]
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.3.1	[Command performed successfully, AT Response containing IMSI]
6	UICC → ME	PROACTIVE UICC SESSION ENDED
7	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.3.2
8	ME → UICC	FETCH
9	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.3.2
10	ME (→ USER)	Display "Run AT Command 2"	[Message shall be formatted without right alignment, request IMSI. Remark: If right alignment is the ME’s default alignment as declared in table A.2/16, no alignment change will take place]
11	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.3.1	[Command performed successfully, AT Response containing IMSI]
12	UICC → ME	PROACTIVE UICC SESSION ENDED

PROACTIVE COMMAND: RUN AT COMMAND 3.3.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 1"

AT Command

AT Command string: "AT+CIMI<CR>"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Right Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2B	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	31	A8	07	41	54	2B	43	49
	4D	49	0D	D0	04	00	10	02	B4

PROACTIVE COMMAND: RUN AT COMMAND 3.3.2

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 2"

AT Command

AT Command string: "AT+CIMI<CR>"

Coding:

BER-TLV:	D0	25	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	32	A8	08	41	54	2B	43	49
	4D	49	0D

TERMINAL RESPONSE: RUN AT COMMAND 3.3.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

AT Response

AT Response string: <CR><LF>IMSI<CR><LF><CR><LF>OK<CR><LF>

Coding:

BER-TLV:	81	03	01	34	00	82	02	82	81	83	01	00
	A9	19	0D	0A	30	30	31	30	31	30	31	32
	33	34	35	36	37	38	39	0D	0A	0D	0A	4F
	4B	0D	0A

27.22.4.23.3.3.5 Test requirement

The ME shall operate in the manner defined in expected sequence 3.3.

27.22.4.23.3.4 RUN AT COMMAND (support of Text Attribute – Large Font Size)

27.22.4.23.3.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.23.3.4.2 Conformance requirement

The ME shall support the Proactive UICC: RUN AT COMMAND facility as defined in:

– TS 31.111 [15] clause 6.4.23, clause 6.6.23, clause 5.2, clause 6.8, clause 8.6, clause 8.7, clause 8.2, clause 8.40, clause 8.31, clause 8.41 and clause 8.70.

– TS 27.007 [18].

The terminal shall support the text attribute.

27.22.4.23.3.4.3 Test purpose

To verify that the ME responds to an AT Command contained within a RUN AT COMMAND with large font size as though it were initiated by an attached TE, and returns an AT Response within a TERMINAL RESPONSE to the UICC.

27.22.4.23.3.4.4 Method of test

27.22.4.23.3.4.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

Prior to the test the ME shall be connected to the TE.

The TA-TE interface is set to 8-bit operation.

27.22.4.23.3.4.4.2 Procedure

Expected Sequence 3.4(RUN AT COMMAND, with alpha identifier presented, request IMSI, Text Attribute – Large Font Size)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.4.1
4	ME (→ USER)	Display "Run AT Command 1"	[alpha identifier is displayed with large font size, request IMSI]
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.4.1	[Command performed successfully, AT Response containing IMSI]
6	UICC → ME	PROACTIVE UICC SESSION ENDED
7	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.4.2
8	ME → UICC	FETCH
9	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.4.2
10	ME (→ USER)	Display "Run AT Command 2"	[alpha identifier is displayed with normal font size, request IMSI]
11	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.4.1	[Command performed successfully, AT Response containing IMSI]
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.4.1
14	ME → UICC	FETCH
15	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.4.1
16	ME (→ USER)	Display "Run AT Command 1"	[alpha identifier is displayed with large font size, request IMSI]
17	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.4.1	[Command performed successfully, AT Response containing IMSI]
18	UICC → ME	PROACTIVE UICC SESSION ENDED
19	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.4.3
20	ME → UICC	FETCH
21	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.4.3
22	ME (→ USER)	Display "Run AT Command 3"	[alpha identifier is displayed with normal font size, request IMSI]
23	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.4.1	[Command performed successfully, AT Response containing IMSI]
24	UICC → ME	PROACTIVE UICC SESSION ENDED

PROACTIVE COMMAND: RUN AT COMMAND 3.4.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 1"

AT Command

AT Command string: "AT+CIMI<CR>"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Large Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2B	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	31	A8	08	41	54	2B	43	49
	4D	49	0D	D0	04	00	10	04	B4

PROACTIVE COMMAND: RUN AT COMMAND 3.4.2

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 2"

AT Command

AT Command string: "AT+CIMI<CR>"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2B	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	32	A8	08	41	54	2B	43	49
	4D	49	0D	D0	04	00	10	00	B4

PROACTIVE COMMAND: RUN AT COMMAND 3.4.3

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 3"

AT Command

AT Command string: "AT+CIMI<CR>"

Coding:

BER-TLV:	D0	25	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	33	A8	08	41	54	2B	43	49
	4D	49	0D

TERMINAL RESPONSE: RUN AT COMMAND 3.4.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

AT Response

AT Response string: <CR><LF>IMSI<CR><LF><CR><LF>OK<CR><LF>

Coding:

BER-TLV:	81	03	01	34	00	82	02	82	81	83	01	00
	A9	19	0D	0A	30	30	31	30	31	30	31	32
	33	34	35	36	37	38	39	0D	0A	0D	0A	4F
	4B	0D	0A

27.22.4.23.3.4.5 Test requirement

The ME shall operate in the manner defined in expected sequence 3.4.

27.22.4.23.3.5 RUN AT COMMAND (support of Text Attribute – Small Font Size)

27.22.4.23.3.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.23.3.5.2 Conformance requirement

The ME shall support the Proactive UICC: RUN AT COMMAND facility as defined in:

– TS 31.111 [15] clause 6.4.23, clause 6.6.23, clause 5.2, clause 6.8, clause 8.6, clause 8.7, clause 8.2, clause 8.40, clause 8.31, clause 8.41 and clause 8.70.

– TS 27.007 [18].

The terminal shall support the text attribute.

27.22.4.23.3.5.3 Test purpose

To verify that the ME responds to an AT Command contained within a RUN AT COMMAND with small font size as though it were initiated by an attached TE, and returns an AT Response within a TERMINAL RESPONSE to the UICC.

27.22.4.23.3.5.4 Method of test

27.22.4.23.3.5.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

Prior to the test the ME shall be connected to the TE.

The TA-TE interface is set to 8-bit operation.

27.22.4.23.3.5.4.2 Procedure

Expected Sequence 3.5(RUN AT COMMAND, with alpha identifier presented, request IMSI, Text Attribute – Small Font Size)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.5.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.5.1
4	ME (→ USER)	Display "Run AT Command 1"	[alpha identifier is displayed with small font size, request IMSI]
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.5.1	[Command performed successfully, AT Response containing IMSI]
6	UICC → ME	PROACTIVE UICC SESSION ENDED
7	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.5.2
8	ME → UICC	FETCH
9	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.5.2
10	ME (→ USER)	Display "Run AT Command 2"	[alpha identifier is displayed with normal font size, request IMSI]
11	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.5.1	[Command performed successfully, AT Response containing IMSI]
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.5.1
14	ME → UICC	FETCH
15	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.5.1
16	ME (→ USER)	Display "Run AT Command 1"	[alpha identifier is displayed with small font size, request IMSI]
17	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.5.1	[Command performed successfully, AT Response containing IMSI]
18	UICC → ME	PROACTIVE UICC SESSION ENDED
19	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.5.3
20	ME → UICC	FETCH
21	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.5.3
22	ME (→ USER)	Display "Run AT Command 3"	[alpha identifier is displayed with normal font size, request IMSI]
23	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.5.1	[Command performed successfully, AT Response containing IMSI]
24	UICC → ME	PROACTIVE UICC SESSION ENDED

PROACTIVE COMMAND: RUN AT COMMAND 3.5.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 1"

AT Command

AT Command string: "AT+CIMI<CR>"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Small Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2B	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	31	A8	08	41	54	2B	43	49
	4D	49	0D	D0	04	00	10	08	B4

PROACTIVE COMMAND: RUN AT COMMAND 3.5.2

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 2"

AT Command

AT Command string: "AT+CIMI<CR>"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2B	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	32	A8	08	41	54	2B	43	49
	4D	49	0D	D0	04	00	10	00	B4

PROACTIVE COMMAND: RUN AT COMMAND 3.5.3

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 3"

AT Command

AT Command string: "AT+CIMI<CR>"

Coding:

BER-TLV:	D0	25	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	33	A8	08	41	54	2B	43	49
	4D	49	0D

TERMINAL RESPONSE: RUN AT COMMAND 3.5.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

AT Response

AT Response string: <CR><LF>IMSI<CR><LF><CR><LF>OK<CR><LF>

Coding:

BER-TLV:	81	03	01	34	00	82	02	82	81	83	01	00
	A9	19	0D	0A	30	30	31	30	31	30	31	32
	33	34	35	36	37	38	39	0D	0A	0D	0A	4F
	4B	0D	0A

27.22.4.23.3.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 3.5.

27.22.4.23.3.6 RUN AT COMMAND (support of Text Attribute – Bold On)

27.22.4.23.3.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.23.3.6.2 Conformance requirement

The ME shall support the Proactive UICC: RUN AT COMMAND facility as defined in:

– TS 31.111 [15] clause 6.4.23, clause 6.6.23, clause 5.2, clause 6.8, clause 8.6, clause 8.7, clause 8.2, clause 8.40, clause 8.31, clause 8.41 and clause 8.70.

– TS 27.007 [18].

The terminal shall support the text attribute.

27.22.4.23.3.6.3 Test purpose

To verify that the ME responds to an AT Command contained within a RUN AT COMMAND with bold text attribute as though it were initiated by an attached TE, and returns an AT Response within a TERMINAL RESPONSE to the UICC.

27.22.4.23.3.6.4 Method of test

27.22.4.23.3.6.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

Prior to the test the ME shall be connected to the TE.

The TA-TE interface is set to 8-bit operation.

27.22.4.23.3.6.4.2 Procedure

Expected Sequence 3.6(RUN AT COMMAND, with alpha identifier presented, request IMSI, Text Attribute – Bold On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.6.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.6.1
4	ME (→ USER)	Display "Run AT Command 1"	[alpha identifier is displayed with bold on, request IMSI]
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.6.1	[Command performed successfully, AT Response containing IMSI]
6	UICC → ME	PROACTIVE UICC SESSION ENDED
7	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.6.2
8	ME → UICC	FETCH
9	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.6.2
10	ME (→ USER)	Display "Run AT Command 2"	[alpha identifier is displayed with bold off, request IMSI]
11	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.6.1	[Command performed successfully, AT Response containing IMSI]
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.6.1
14	ME → UICC	FETCH
15	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.6.1
16	ME (→ USER)	Display "Run AT Command 1"	[alpha identifier is displayed with bold on, request IMSI]
17	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.6.1	[Command performed successfully, AT Response containing IMSI]
18	UICC → ME	PROACTIVE UICC SESSION ENDED
19	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.6.3
20	ME → UICC	FETCH
21	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.6.3
22	ME (→ USER)	Display "Run AT Command 3"	[alpha identifier is displayed with bold off, request IMSI]
23	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.6.1	[Command performed successfully, AT Response containing IMSI]
24	UICC → ME	PROACTIVE UICC SESSION ENDED

PROACTIVE COMMAND: RUN AT COMMAND 3.6.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 1"

AT Command

AT Command string: "AT+CIMI<CR>"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold On, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2B	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	31	A8	08	41	54	2B	43	49
	4D	49	0D	D0	04	00	10	10	B4

PROACTIVE COMMAND: RUN AT COMMAND 3.6.2

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 2"

AT Command

AT Command string: "AT+CIMI<CR>"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2B	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	32	A8	08	41	54	2B	43	49
	4D	49	0D	D0	04	00	10	00	B4

PROACTIVE COMMAND: RUN AT COMMAND 3.6.3

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 3"

AT Command

AT Command string: "AT+CIMI<CR>"

Coding:

BER-TLV:	D0	25	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	33	A8	08	41	54	2B	43	49
	4D	49	0D

TERMINAL RESPONSE: RUN AT COMMAND 3.6.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

AT Response

AT Response string: <CR><LF>IMSI<CR><LF><CR><LF>OK<CR><LF>

Coding:

BER-TLV:	81	03	01	34	00	82	02	82	81	83	01	00
	A9	19	0D	0A	30	30	31	30	31	30	31	32
	33	34	35	36	37	38	39	0D	0A	0D	0A	4F
	4B	0D	0A

27.22.4.23.3.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 3.6.

27.22.4.23.3.7 RUN AT COMMAND (support of Text Attribute – Italic On)

27.22.4.23.3.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.23.3.7.2 Conformance requirement

The ME shall support the Proactive UICC: RUN AT COMMAND facility as defined in:

– TS 31.111 [15] clause 6.4.23, clause 6.6.23, clause 5.2, clause 6.8, clause 8.6, clause 8.7, clause 8.2, clause 8.40, clause 8.31, clause 8.41 and clause 8.70.

– TS 27.007 [18].

The terminal shall support the text attribute.

27.22.4.23.3.7.3 Test purpose

To verify that the ME responds to an AT Command contained within a RUN AT COMMAND with italic text attribute as though it were initiated by an attached TE, and returns an AT Response within a TERMINAL RESPONSE to the UICC.

27.22.4.23.3.7.4 Method of test

27.22.4.23.3.7.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

Prior to the test the ME shall be connected to the TE.

The TA-TE interface is set to 8-bit operation.

27.22.4.23.3.7.4.2 Procedure

Expected Sequence 3.7(RUN AT COMMAND, with alpha identifier presented, request IMSI, Text Attribute – Italic On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.7.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.7.1
4	ME (→ USER)	Display "Run AT Command 1"	[alpha identifier is displayed with italic on, request IMSI]
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.7.1	[Command performed successfully, AT Response containing IMSI]
6	UICC → ME	PROACTIVE UICC SESSION ENDED
7	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.7.2
8	ME → UICC	FETCH
9	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.7.2
10	ME (→ USER)	Display "Run AT Command 2"	[alpha identifier is displayed with italic off, request IMSI]
11	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.7.1	[Command performed successfully, AT Response containing IMSI]
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.7.1
14	ME → UICC	FETCH
15	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.7.1
16	ME (→ USER)	Display "Run AT Command 1"	[alpha identifier is displayed with italic on, request IMSI]
17	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.7.1	[Command performed successfully, AT Response containing IMSI]
18	UICC → ME	PROACTIVE UICC SESSION ENDED
19	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.7.3
20	ME → UICC	FETCH
21	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.7.3
22	ME (→ USER)	Display "Run AT Command 3"	[alpha identifier is displayed with italic off, request IMSI]
23	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.7.1	[Command performed successfully, AT Response containing IMSI]
24	UICC → ME	PROACTIVE UICC SESSION ENDED

PROACTIVE COMMAND: RUN AT COMMAND 3.7.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 1"

AT Command

AT Command string: "AT+CIMI<CR>"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic On, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2B	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	31	A8	08	41	54	2B	43	49
	4D	49	0D	D0	04	00	10	20	B4

PROACTIVE COMMAND: RUN AT COMMAND 3.7.2

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 2"

AT Command

AT Command string: "AT+CIMI<CR>"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2B	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	32	A8	08	41	54	2B	43	49
	4D	49	0D	D0	04	00	10	00	B4

PROACTIVE COMMAND: RUN AT COMMAND 3.7.3

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 3"

AT Command

AT Command string: "AT+CIMI<CR>"

Coding:

BER-TLV:	BER-TLV:	D0	25	81	03	01	34	00	82	02	81	82
		10	52	75	6E	20	41	54	20	43	6F	6D
		61	6E	64	20	33	A8	08	41	54	2B	43
		4D	49	0D

TERMINAL RESPONSE: RUN AT COMMAND 3.7.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

AT Response

AT Response string: <CR><LF>IMSI<CR><LF><CR><LF>OK<CR><LF>

Coding:

BER-TLV:	81	03	01	34	00	82	02	82	81	83	01	00
	A9	19	0D	0A	30	30	31	30	31	30	31	32
	33	34	35	36	37	38	39	0D	0A	0D	0A	4F
	4B	0D	0A

27.22.4.23.3.7.5 Test requirement

The ME shall operate in the manner defined in expected sequence 3.7.

27.22.4.23.3.8 RUN AT COMMAND (support of Text Attribute – Underline On)

27.22.4.23.3.8.1 Definition and applicability

See clause 3.2.2.

27.22.4.23.3.8.2 Conformance requirement

The ME shall support the Proactive UICC: RUN AT COMMAND facility as defined in:

– TS 31.111 [15] clause 6.4.23, clause 6.6.23, clause 5.2, clause 6.8, clause 8.6, clause 8.7, clause 8.2, clause 8.40, clause 8.31, clause 8.41 and clause 8.70.

– TS 27.007 [18].

The terminal shall support the text attribute.

27.22.4.23.3.8.3 Test purpose

To verify that the ME responds to an AT Command contained within a RUN AT COMMAND with underline text attribute as though it were initiated by an attached TE, and returns an AT Response within a TERMINAL RESPONSE to the UICC.

27.22.4.23.3.8.4 Method of test

27.22.4.23.3.8.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

Prior to the test the ME shall be connected to the TE.

The TA-TE interface is set to 8-bit operation.

27.22.4.23.3.8.4.2 Procedure

Expected Sequence 3.8(RUN AT COMMAND, with alpha identifier presented, request IMSI, Text Attribute – Underline On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.8.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.8.1
4	ME (→ USER)	Display "Run AT Command 1"	[alpha identifier is displayed with underline on, request IMSI]
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.8.1	[Command performed successfully, AT Response containing IMSI]
6	UICC → ME	PROACTIVE UICC SESSION ENDED
7	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.8.2
8	ME → UICC	FETCH
9	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.8.2
10	ME (→ USER)	Display "Run AT Command 2"	[alpha identifier is displayed with underline off, request IMSI]
11	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.8.1	[Command performed successfully, AT Response containing IMSI]
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.8.1
14	ME → UICC	FETCH
15	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.8.1
16	ME (→ USER)	Display "Run AT Command 1"	[alpha identifier is displayed with underline on, request IMSI]
17	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.8.1	[Command performed successfully, AT Response containing IMSI]
18	UICC → ME	PROACTIVE UICC SESSION ENDED
19	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.8.3
20	ME → UICC	FETCH
21	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.8.3
22	ME (→ USER)	Display "Run AT Command 3"	[alpha identifier is displayed with underline off, request IMSI]
23	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.8.1	[Command performed successfully, AT Response containing IMSI]
24	UICC → ME	PROACTIVE UICC SESSION ENDED

PROACTIVE COMMAND: RUN AT COMMAND 3.8.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 1"

AT Command

AT Command string: "AT+CIMI<CR>"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline On, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2B	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	31	A8	08	41	54	2B	43	49
	4D	49	0D	D0	04	00	10	40	B4

PROACTIVE COMMAND: RUN AT COMMAND 3.8.2

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 2"

AT Command

AT Command string: "AT+CIMI<CR>"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2B	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	32	A8	08	41	54	2B	43	49
	4D	49	0D	D0	04	00	10	00	B4

PROACTIVE COMMAND: RUN AT COMMAND 3.8.3

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 3"

AT Command

AT Command string: "AT+CIMI<CR>"

Coding:

BER-TLV:	D0	25	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	33	A8	08	41	54	2B	43	49
	4D	49	0D

TERMINAL RESPONSE: RUN AT COMMAND 3.8.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

AT Response

AT Response string: <CR><LF>IMSI<CR><LF><CR><LF>OK<CR><LF>

Coding:

BER-TLV:	81	03	01	34	00	82	02	82	81	83	01	00
	A9	19	0D	0A	30	30	31	30	31	30	31	32
	33	34	35	36	37	38	39	0D	0A	0D	0A	4F
	4B	0D	0A

27.22.4.23.3.8.5 Test requirement

The ME shall operate in the manner defined in expected sequence 3.8.

27.22.4.23.3.9 RUN AT COMMAND (support of Text Attribute – Strikethrough On)

27.22.4.23.3.9.1 Definition and applicability

See clause 3.2.2.

27.22.4.23.3.9.2 Conformance requirement

The ME shall support the Proactive UICC: RUN AT COMMAND facility as defined in:

– TS 31.111 [15] clause 6.4.23, clause 6.6.23, clause 5.2, clause 6.8, clause 8.6, clause 8.7, clause 8.2, clause 8.40, clause 8.31, clause 8.41 and clause 8.70.

– TS 27.007 [18].

The terminal shall support the text attribute.

27.22.4.23.3.9.3 Test purpose

To verify that the ME responds to an AT Command contained within a RUN AT COMMAND with strikethrough text attribute as though it were initiated by an attached TE, and returns an AT Response within a TERMINAL RESPONSE to the UICC.

27.22.4.23.3.9.4 Method of test

27.22.4.23.3.9.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

Prior to the test the ME shall be connected to the TE.

The TA-TE interface is set to 8-bit operation.

27.22.4.23.3.9.4.2 Procedure

Expected Sequence 3.9(RUN AT COMMAND, with alpha identifier presented, request IMSI, Text Attribute – Strikethrough On)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.9.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.9.1
4	ME (→ USER)	Display "Run AT Command 1"	[alpha identifier is displayed with strikethrough on, request IMSI]
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.9.1	[Command performed successfully, AT Response containing IMSI]
6	UICC → ME	PROACTIVE UICC SESSION ENDED
7	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.9.2
8	ME → UICC	FETCH
9	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.9.2
10	ME (→ USER)	Display "Run AT Command 2"	[alpha identifier is displayed with strikethrough off, request IMSI]
11	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.9.1	[Command performed successfully, AT Response containing IMSI]
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.9.1
14	ME → UICC	FETCH
15	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.9.1
16	ME (→ USER)	Display " Run AT Command 1"	[alpha identifier is displayed with strikethrough on, request IMSI]
17	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.9.1	[Command performed successfully, AT Response containing IMSI]
18	UICC → ME	PROACTIVE UICC SESSION ENDED
19	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.9.3
20	ME → UICC	FETCH
21	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.9.3
22	ME (→ USER)	Display "Run AT Command 3"	[alpha identifier is displayed with strikethrough off, request IMSI]
23	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.9.1	[Command performed successfully, AT Response containing IMSI]
24	UICC → ME	PROACTIVE UICC SESSION ENDED

PROACTIVE COMMAND: RUN AT COMMAND 3.9.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 1"

AT Command

AT Command string: "AT+CIMI<CR>"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough On

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2B	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	31	A8	08	41	54	2B	43	49
	4D	49	0D	D0	04	00	10	80	B4

PROACTIVE COMMAND: RUN AT COMMAND 3.9.2

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 2"

AT Command

AT Command string: "AT+CIMI<CR>"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2B	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	32	A8	08	41	54	2B	43	49
	4D	49	0D	D0	04	00	10	00	B4

PROACTIVE COMMAND: RUN AT COMMAND 3.9.3

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 3"

AT Command

AT Command string: "AT+CIMI<CR>"

Coding:

BER-TLV:	D0	25	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	33	A8	08	41	54	2B	43	49
	4D	49	0D

TERMINAL RESPONSE: RUN AT COMMAND 3.9.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

AT Response

AT Response string: <CR><LF>IMSI<CR><LF><CR><LF>OK<CR><LF>

Coding:

BER-TLV:	81	03	01	34	00	82	02	82	81	83	01	00
	A9	19	0D	0A	30	30	31	30	31	30	31	32
	33	34	35	36	37	38	39	0D	0A	0D	0A	4F
	4B	0D	0A

27.22.4.23.3.9.5 Test requirement

The ME shall operate in the manner defined in expected sequence 3.9.

27.22.4.23.3.10 RUN AT COMMAND (support of Text Attribute – Foreground and Background Colour)

27.22.4.23.3.10.1 Definition and applicability

See clause 3.2.2.

27.22.4.23.3.10.2 Conformance requirement

The ME shall support the Proactive UICC: RUN AT COMMAND facility as defined in:

– TS 31.111 [15] clause 6.4.23, clause 6.6.23, clause 5.2, clause 6.8, clause 8.6, clause 8.7, clause 8.2, clause 8.40, clause 8.31, clause 8.41 and clause 8.70.

– TS 27.007 [18].

The terminal shall support the text attribute.

27.22.4.23.3.10.3 Test purpose

To verify that the ME responds to an AT Command contained within a RUN AT COMMAND with foreground and background colour text attribute as though it were initiated by an attached TE, and returns an AT Response within a TERMINAL RESPONSE to the UICC.

27.22.4.23.3.10.4 Method of test

27.22.4.23.3.10.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

Prior to the test the ME shall be connected to the TE.

The TA-TE interface is set to 8-bit operation.

27.22.4.23.3.10.4.2 Procedure

Expected Sequence 3.10(RUN AT COMMAND, with alpha identifier presented, request IMSI, Text Attribute – Foreground and Background Colour)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.10.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.10.1
4	ME (→ USER)	Display "Run AT Command 1"	[alpha identifier is displayed with foreground and background colour according to the text attribute configuration, request IMSI]
5	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.10.1	[Command performed successfully, AT Response containing IMSI]
6	UICC → ME	PROACTIVE UICC SESSION ENDED
7	UICC → ME	PROACTIVE COMMAND PENDING: RUN AT COMMAND 3.10.2
8	ME → UICC	FETCH
9	UICC → ME	PROACTIVE COMMAND: RUN AT COMMAND 3.10.2
10	ME (→ USER)	Display "Run AT Command 2"	[alpha identifier is displayed with ME’s default foreground and background colour, request IMSI]
11	ME → UICC	TERMINAL RESPONSE: RUN AT COMMAND 3.10.1	[Command performed successfully, AT Response containing IMSI]
12	UICC → ME	PROACTIVE UICC SESSION ENDED

PROACTIVE COMMAND: RUN AT COMMAND 3.10.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 1"

AT Command

AT Command string: "AT+CIMI<CR>"

Text Attribute

Formatting position: 0

Formatting length: 16

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	2B	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	31	A8	08	41	54	2B	43	49
	4D	49	0D	D0	04	00	10	00	B4

PROACTIVE COMMAND: RUN AT COMMAND 3.10.2

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier

Alpha Identifier "Run AT Command 2"

AT Command

AT Command string: "AT+CIMI<CR>"

Coding:

BER-TLV:	D0	25	81	03	01	34	00	82	02	81	82	85
	10	52	75	6E	20	41	54	20	43	6F	6D	6D
	61	6E	64	20	32	A8	08	41	54	2B	43	49
	4D	49	0D

TERMINAL RESPONSE: RUN AT COMMAND 3.10.1

Logically:

Command details

Command number: 1

Command type: RUN AT COMMAND

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

AT Response

AT Response string: <CR><LF>IMSI<CR><LF><CR><LF>OK<CR><LF>

Coding:

BER-TLV:	81	03	01	34	00	82	02	82	81	83	01	00
	A9	19	0D	0A	30	30	31	30	31	30	31	32
	33	34	35	36	37	38	39	0D	0A	0D	0A	4F
	4B	0D	0A

27.22.4.23.3.10.5 Test requirement

The ME shall operate in the manner defined in expected sequence 3.10.

27.22.4.23.4 RUN AT COMMAND (UCS2 display in Cyrillic)

27.22.4.23.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.23.4.2 Conformance requirement

The ME shall support the Proactive UICC: RUN AT COMMAND facility as defined in:

– TS 31.111 [15] clause 6.4.23, clause 6.6.23, clause 5.2, clause 6.8, clause 8.6, clause 8.7, clause 8.2, clause 8.40, clause 8.31, clause 8.41 and clause 8.70.

– TS 27.007 [18].

The terminal shall support the text attribute.

27.22.4.23.4.3 Test purpose

To verify that the ME responds to an AT Command contained within a RUN AT COMMAND with UCS2 alpha identifier as though it were initiated by an attached TE, and returns an AT Response within a TERMINAL RESPONSE to the UICC.

27.22.4.23.4.4 Method of test

27.22.4.23.4.4.1 Initial conditions

The ME is connected to the UICC Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

Prior to the test the ME shall be connected to the TE.

The TA-TE interface is set to 8-bit operation.

27.22.4.23.4.4.2 Procedure

Expected Sequence 4.1(RUN AT COMMAND, alpha identifier presented coded with UCS2 in Cyrillic, request ME Manufacturer ID)

See ETSI TS 102 384 [26] in clause 27.22.4.23.4.4.2, Expected Sequence 4.1.

27.22.4.23.4.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.1.

27.22.4.23.5 RUN AT COMMAND (UCS2 display in Chinese)

27.22.4.23.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.23.5.2 Conformance requirement

The ME shall support the Proactive UICC: RUN AT COMMAND facility as defined in:

– TS 31.111 [15] clause 6.4.23, clause 6.6.23, clause 5.2, clause 6.8, clause 8.6, clause 8.7, clause 8.2, clause 8.40, clause 8.31, clause 8.41 and clause 8.70.

– TS 27.007 [18].

The terminal shall support the text attribute.

27.22.4.23.5.3 Test purpose

27.22.4.23.5.4 Method of test

27.22.4.23.5.4.1 Initial conditions

The ME is connected to the UICC Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

Prior to the test the ME shall be connected to the TE.

The TA-TE interface is set to 8-bit operation.

27.22.4.23.5.4.2 Procedure

Expected Sequence 5.1(RUN AT COMMAND, alpha identifier presented coded with UCS2 in Chinese, request ME Manufacturer ID)

See ETSI TS 102 384 [26] in clause 27.22.4.23.5.4.2, Expected Sequence 5.1.

27.22.4.23.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 5.1.

27.22.4.23.6 RUN AT COMMAND (UCS2 display in Katakana)

27.22.4.23.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.23.6.2 Conformance requirement

The ME shall support the Proactive UICC: RUN AT COMMAND facility as defined in:

– TS 31.111 [15] clause 6.4.23, clause 6.6.23, clause 5.2, clause 6.8, clause 8.6, clause 8.7, clause 8.2, clause 8.40, clause 8.31, clause 8.41 and clause 8.70.

– TS 27.007 [18].

The terminal shall support the text attribute.

27.22.4.23.6.3 Test purpose

27.22.4.23.6.4 Method of test

27.22.4.23.6.4.1 Initial conditions

The ME is connected to the UICC Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

Prior to the test the ME shall be connected to the TE.

The TA-TE interface is set to 8-bit operation.

27.22.4.23.6.4.2 Procedure

Expected Sequence 6.1(RUN AT COMMAND, alpha identifier presented coded with UCS2 in Katakana, request ME Manufacturer ID)

See ETSI TS 102 384 [26] in clause 27.22.4.23.6.4.2, Expected Sequence 6.1.

27.22.4.23.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.1.

27.22.4.24 SEND DTMF

27.22.4.24.1 SEND DTMF (Normal)

27.22.4.24.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.24.1.2 Conformance requirement

The ME shall support the Proactive UICC: Send DTMF facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.24, clause 6.6.24, clause 8.12.2, clause 5.2, clause 8.6, clause 8.7, clause 8.2 and clause 8.44.

27.22.4.24.1.3 Test purpose

To verify that after a call has been successfully established the ME sends the DTMF string contained in the SEND DTMF proactive UICC command to the network, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

To verify that the ME does not locally generate audible DTMF tones and play them to the user.

To verify that if the ME is in idle mode it informs the UICC using TERMINAL RESPONSE ’20’ with the additional information "Not in speech call".

To verify that the ME displays the text contained in the SEND DTMF proactive UICC command.

To verify that if an alpha identifier is provided by the UICC and is a null data object the ME does not give any information to the user on the fact that the ME is performing a SEND DTMF command.

27.22.4.24.1.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.24.1.4. 2 Procedure

Expected Sequence 1.1 (SEND DTMF, normal)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 1.1.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 1.1.1
7	ME → USER	May give information to the user concerning what is happening. Do not locally generate audible DTMF tones and play them to the user.
8	ME → USS	Start DTMF 1.1	["1"]
9	ME		No DTMF sending for 3 seconds ±20%
10	ME → USS	Start DTMF 1.2	["2"]
11	ME → UICC	TERMINAL RESPONSE: SEND DTMF 1.1.1	[Command performed successfully]
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13	User → ME	End the call

PROACTIVE COMMAND: SEND DTMF 1.1.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

DTMF String: "1" pause "2"

Coding:

BER-TLV:	D0	0D	81	03	01	14	00	82	02	81	83	AC
	02	C1	F2

Start DTMF 1.1

Logically:

DTMF String: "1"

Start DTMF 1.2

Logically:

DTMF String: "2"

TERMINAL RESPONSE: SEND DTMF 1.1.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 1.2 (SEND DTMF, containing alpha identifier)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 1.2.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 1.2.1
7	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	Alpha identifier
8	ME → USS	Start DTMF 1.1	["1"]
9	ME → USS	Start DTMF 1.2	["2"]
10	ME → USS	Start DTMF 1.3	["3"]
11	ME → USS	Start DTMF 1.4	["4"]
12	ME → USS	Start DTMF 1.5	["5"]
13	ME → USS	Start DTMF 1.6	["6"]
14	ME → USS	Start DTMF 1.7	["7"]
15	ME → USS	Start DTMF 1.8	["8"]
16	ME → USS	Start DTMF 1.9	["9"]
17	ME → USS	Start DTMF 1.10	["0"]
18	ME → UICC	TERMINAL RESPONSE: SEND DTMF 1.1.1	[Command performed successfully]
19	UICC → ME	PROACTIVE UICC SESSION ENDED
20	User → ME	End the call

PROACTIVE COMMAND: SEND DTMF 1.2.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF"

DTMF String: "1234567890"

Coding:

BER-TLV:	D0	1B	81	03	01	14	00	82	02	81	83	85
	09	53	65	6E	64	20	44	54	4D	46	AC	05
	21	43	65	87	09

Start DTMF 1.3

Logically:

DTMF String: "3"

Start DTMF 1.4

Logically:

DTMF String: "4"

Start DTMF 1.5

Logically:

DTMF String: "5"

Start DTMF 1.6

Logically:

DTMF String: "6"

Start DTMF 1.7

Logically:

DTMF String: "7"

Start DTMF 1.8

Logically:

DTMF String: "8"

Start DTMF 1.9

Logically:

DTMF String: "9"

Start DTMF 1.10

Logically:

DTMF String: "0"

Expected Sequence 1.3 (SEND DTMF, containing alpha identifier with null data object)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 1.3.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 1.3.1	Alpha identifier with null data object
7	ME → USER	Do not give any information to the user on the fact that the ME is performing a SEND DTMF command. Do not locally generate audible DTMF tones and play them to the user.
8	ME → USS	Start DTMF 1.1	["1"]
9	ME		No DTMF sending for 30 seconds ±20%
10	ME → USS	Start DTMF 1.2	["2"]
11	ME → UICC	TERMINAL RESPONSE: SEND DTMF 1.1.1	[Command performed successfully]
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13	User → ME	End the call

PROACTIVE COMMAND: SEND DTMF 1.3.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "" (null data object)

DTMF String: "1" pause pause pause pause pause pause pause pause pause pause "2"

Coding:

BER-TLV:	D0	13	81	03	01	14	00	82	02	81	83	85
	00	AC	06	C1	CC	CC	CC	CC	2C

Expected Sequence 1.4 (SEND DTMF, mobile is not in a speech call)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 1.1.1	[Mobile is not in a speech call]
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: SEND DTMF 1.1.1
4	ME → UICC	TERMINAL RESPONSE: SEND DTMF 1.4.1	[ME currently unable to process command, not in speech call]
5	UICC → ME	PROACTIVE UICC SESSION ENDED

TERMINAL RESPONSE: SEND DTMF 1.4.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: ME currently unable to process command

Additional information: Not in speech call

Coding:

BER-TLV:	81	03	01	14	00	82	02	82	81	83	02	20
	07

27.22.4.24.1.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1 to 1.4.

27.22.4.24.2 SEND DTMF (Display of icons)

27.22.4.24.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.24.2.2 Conformance requirement

The ME shall support the Proactive UICC: Send DTMF facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.24, clause 6.6.24, clause 8.12.2, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.44, clause 8.31 and clause 6.5.4.

27.22.4.24.2.3 Test purpose

To verify that after a call has been successfully established the ME send the DTMF string contained in the SEND DTMF proactive UICC command to the network, and returns a successful response in the TERMINAL RESPONSE command sent to the UICC.

To verify that the ME do not locally generate audible DTMF tones and play them to the user.

To verify that the ME displays the text contained in the SEND DTMF proactive UICC command.

To verify that the ME displays the icons which are referred to in the contents of the SEND DTMF proactive UICC command.

27.22.4.24.2.4 Method of test

27.22.4.24.2.4.1 Initial conditions

The ME is connected to the SIM Simulator and only connected to the System Simulator if the System Simulator is mentioned in the sequence table.Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

The elementary files are coded as Toolkit default.

27.22.4.24.2.4.2 Procedure

Expected Sequence 2.1A (SEND DTMF, BASIC ICON self explanatory, successful)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 2.1.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 2.1.1	[BASIC-ICON, self-explanatory]
7	ME → USER	Display the BASIC-ICON Do not locally generate audible DTMF tones and play them to the user.
8	ME → USS	Start DTMF 1.1	["1"]
9	ME		No DTMF sending for 3 seconds ±20%
10	ME → USS	Start DTMF 1.2	["2"]
11	ME → UICC	TERMINAL RESPONSE: SEND DTMF 2.1.1A	[Command performed successfully]
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13	User → ME	End the call

PROACTIVE COMMAND: SEND DTMF 2.1.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Basic Icon"

DTMF String: "1" pause "2"

Icon identifier

Icon qualifier: icon is self-explanatory

Icon identifier: record 1 in EF_(IMG)

Coding:

BER-TLV:	D0	1D	81	03	01	14	00	82	02	81	83	85
	0A	42	61	73	69	63	20	49	63	6F	6E	AC
	02	C1	F2	9E	02	00	01

DTMF Request 2.1.1

Logically:

DTMF String: $DTMF_2.1$ = "C1 F2" (given as example)

TERMINAL RESPONSE: SEND DTMF 2.1.1A

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 2.1B (SEND DTMF, BASIC ICON self explanatory, requested icon could not be displayed)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 2.1.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 2.1.1	[BASIC-ICON, self-explanatory]
7	ME → USER	Display "Basic Icon" without the icon Do not locally generate audible DTMF tones and play them to the user.
8	ME → USS	Start DTMF 1.1	["1"]
9	ME		No DTMF sending for 3 seconds ±20 %
10	ME → USS	Start DTMF 1.2	["2"]
11	ME → UICC	TERMINAL RESPONSE: SEND DTMF 2.1.1B	[Command performed successfully, but requested icon could not be displayed]
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13	User → ME	End the call

TERMINAL RESPONSE: SEND DTMF 2.1.1B

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully, but requested icon could not be displayed

Coding:

BER-TLV:

Expected Sequence 2.2A (SEND DTMF, COLOUR-ICON self explanatory, successful)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 2.2.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 2.2.1	[COLOUR-ICON]
7	ME → USER	Display the COLOUR-ICON Do not locally generate audible DTMF tones and play them to the user.
8	ME → USS	Start DTMF 1.1	["1"]
9	ME		No DTMF sending for 3 seconds ±20%
10	ME → USS	Start DTMF 1.2	["2"]
11	ME → UICC	TERMINAL RESPONSE: SEND DTMF 2.1.1A	[Command performed successfully]
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13	User → ME	End the call

PROACTIVE COMMAND: SEND DTMF 2.2.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Colour Icon"

DTMF String: "1" pause "2"

Icon identifier:

Icon qualifier: icon is self-explanatory

Icon identifier: record 2 in EF_(IMG)

Coding:

BER-TLV:	D0	1E	81	03	01	14	00	82	02	81	83	85
	0B	43	6F	6C	6F	75	72	20	49	63	6F	6E
	AC	02	C1	F2	9E	02	00	02

Expected Sequence 2.2B (SEND DTMF, COLOUR-ICON self explanatory, requested icon could not be displayed)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 2.2.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 2.2.1	[COLOUR-ICON]
7	ME → USER	Display "Colour Icon" without the icon Do not locally generate audible DTMF tones and play them to the user.
8	ME → USS	Start DTMF 1.1	["1"]
9	ME		No DTMF sending for 3 seconds ±20%
10	ME → USS	Start DTMF 1.2	["2"]
11	ME → UICC	TERMINAL RESPONSE: SEND DTMF 2.1.1B	[Command performed successfully, but requested icon could not be displayed]
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13	User → ME	End the call

Expected Sequence 2.3A (SEND DTMF, Alpha identifier & BASIC-ICON, not self-explanatory, successful)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 2.3.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 2.3.1	[Alpha identifier & BASIC-ICON, not self-explanatory]
7	ME → USER	Display "Send DTMF" and the BASIC-ICON Do not locally generate audible DTMF tones and play them to the user.
8	ME → USS	Start DTMF 1.1	["1"]
9	ME		No DTMF sending for 3 seconds ±20 %
10	ME → USS	Start DTMF 1.2	["2"]
11	ME → UICC	TERMINAL RESPONSE: SEND DTMF 2.1.1A	[Command performed successfully]
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13	User → ME	End the call

PROACTIVE COMMAND: SEND DTMF 2.3.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF"

DTMF String: "1" pause "2"

Icon identifier:

Icon qualifier: icon is not self-explanatory

Icon identifier: record 1 in EF_(IMG)

Coding:

BER-TLV:	D0	1C	81	03	01	14	00	82	02	81	83	85
	09	53	65	6E	64	20	44	54	4D	46	AC	02
	C1	F2	9E	02	01	01

Expected Sequence 2.3B (SEND DTMF, Alpha identifier & BASIC-ICON, not self-explanatory, requested icon could not be displayed)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 2.3.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 2.3.1	[Alpha identifier & BASIC-ICON, not self-explanatory]
7	ME → USER	Display "Send DTMF" without the icon Do not locally generate audible DTMF tones and play them to the user.
8	ME → USS	Start DTMF 1.1	["1"]
9	ME		No DTMF sending for 3 seconds ±20%
10	ME → USS	Start DTMF 1.2	["2"]
11	ME → UICC	TERMINAL RESPONSE: SEND DTMF 2.1.1B	[Command performed successfully, but requested icon could not be displayed]
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13	User → ME	End the call

27.22.4.24.2.5 Test requirement

The ME shall operate in the manner defined in expected sequences 2.1 to 2.3.

27.22.4.24.3 SEND DTMF (UCS2 display in Cyrillic)

27.22.4.24.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.24.3.2 Conformance requirement

The ME shall support the Proactive UICC: Send DTMF facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.24, clause 6.6.24, clause 8.12.2, clause 5.2, clause 8.6, clause 8.7, clause 8.2 and clause 8.44.

Additionally the ME shall support the UCS2 facility for the coding of the Cyrillic alphabet, as defined in:

– ISO/IEC 10646. [17].

27.22.4.24.3.3 Test purpose

To verify that the ME displays the UCS2 text contained in the SEND DTMF proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.24.3.4 Method of test

27.22.4.24.3.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table.The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.24.3.4.2 Procedure

Expected Sequence 3.1 (SEND DTMF, successful, UCS2 text in Cyrillic)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 3.1.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 3.1.1
7	ME → USER	Display "ЗДРАВСТВУЙТЕ"	["Hello" in Russian]
8	ME → USS	Start DTMF 1.1	["1"]
9	ME		No DTMF sending for 3 seconds ±20%
10	ME → USS	Start DTMF 1.2	["2"]
11	ME → UICC	TERMINAL RESPONSE: SEND DTMF 3.1.1	[Command performed successfully]
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13	User → ME	End the call

PROACTIVE COMMAND: SEND DTMF 3.1.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha Identifier

Text: "ЗДРАВСТВУЙТЕ"

DTMF String: "1" pause "2"

Coding:

BER-TLV:	D0	28	81	03	01	14	00	82	02	81	83	85
	19	80	04	17	04	14	04	20	04	10	04	12
	04	21	04	22	04	12	04	23	04	19	04	22
	04	15	AC	02	C1	F2

TERMINAL RESPONSE: SEND DTMF 3.1.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successful

Coding:

BER-TLV:

27.22.4.12.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 3.1.

27.22.4.24.4 SEND DTMF (support of Text Attribute)

27.22.4.24.4.1 SEND DTMF (support of Text Attribute – Left Alignment)

27.22.4.24.4.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.24.4.1.2 Conformance requirement

The ME shall support the Proactive UICC: Send DTMF facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.24, clause 6.6.24, clause 8.12.2, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.44 and clause 8.70.

27.22.4.24.4.1.3 Test purpose

To verify that the ME does not locally generate audible DTMF tones and play them to the user.

To verify that if the ME is in idle mode it informs the UICC using TERMINAL RESPONSE ’20’ with the additional information "Not in speech call".

To verify that the ME displays the text contained in the SEND DTMF proactive UICC command.

To verify that the ME displays the alpha identifier according to the left alignment text attribute configuration which are referred to in the contents of the SEND DTMF proactive UICC command.

27.22.4.24.4.1.4 Method of test

27.22.4.24.4.1.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.24.4.1.4.2 Procedure

Expected Sequence 4.1 (SEND DTMF, with text attribute – Left Alignment)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.1.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.1.1
7	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with left alignment]
8	ME → USS	Start DTMF 1.1	["1"]
9	ME → USS	Start DTMF 1.2	["2"]
10	ME → USS	Start DTMF 1.3	["3"]
11	ME → USS	Start DTMF 1.4	["4"]
12	ME → USS	Start DTMF 1.5	["5"]
13	ME → USS	Start DTMF 1.6	["6"]
14	ME → USS	Start DTMF 1.7	["7"]
15	ME → USS	Start DTMF 1.8	["8"]
16	ME → USS	Start DTMF 1.9	["9"]
17	ME → USS	Start DTMF 1.10	["0"]
18	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.1.1	[Command performed successfully]
19	UICC → ME	PROACTIVE UICC SESSION ENDED
20	User → ME	End the call
21	User → ME	Set up a call to "+0123456789"
22	ME → USS	The ME attempts to set up a call to "+0123456789"
23	USS → ME	The ME receives the CONNECT message from the USS.
24	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.1.2
25	ME → UICC	FETCH
26	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.1.2
27	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Message shall be formatted without left alignment. Remark: If left alignment is the ME’s default alignment as declared in table A.2/17, no alignment change will take place]
28	ME → USS	Start DTMF 1.1	["1"]
29	ME → USS	Start DTMF 1.2	["2"]
30	ME → USS	Start DTMF 1.3	["3"]
31	ME → USS	Start DTMF 1.4	["4"]
32	ME → USS	Start DTMF 1.5	["5"]
33	ME → USS	Start DTMF 1.6	["6"]
34	ME → USS	Start DTMF 1.7	["7"]
35	ME → USS	Start DTMF 1.8	["8"]
36	ME → USS	Start DTMF 1.9	["9"]
37	ME → USS	Start DTMF 1.10	["0"]
38	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.1.1	[Command performed successfully]
39	UICC → ME	PROACTIVE UICC SESSION ENDED
40	User → ME	End the call

PROACTIVE COMMAND: SEND DTMF 4.1.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 1"

DTMF String: "1234567890"

Text Attribute

Formatting position: 0

Formatting length: 11

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	23	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	31
	AC	05	21	43	65	87	09	D0	04	00	0B	00
	B4

PROACTIVE COMMAND: SEND DTMF 4.1.2

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 2"

DTMF String: "1234567890"

Coding:

BER-TLV:	D0	1D	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	32
	AC	05	21	43	65	87	09

TERMINAL RESPONSE: SEND DTMF 4.1.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.24.4.1.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.1.

27.22.4.24.4.2 SEND DTMF (support of Text Attribute – Center Alignment)

27.22.4.24.4.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.24.4.2.2 Conformance requirement

The ME shall support the Proactive UICC: Send DTMF facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.24, clause 6.6.24, clause 8.12.2, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.44 and clause 8.70.

27.22.4.24.4.2.3 Test purpose

To verify that the ME does not locally generate audible DTMF tones and play them to the user.

To verify that if the ME is in idle mode it informs the UICC using TERMINAL RESPONSE ’20’ with the additional information "Not in speech call".

To verify that the ME displays the text contained in the SEND DTMF proactive UICC command.

To verify that the ME displays the alpha identifier according to the center alignment text attribute configuration which are referred to in the contents of the SEND DTMF proactive UICC command.

27.22.4.24.4.2.4 Method of test

27.22.4.24.4.2.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.24.4.2.4.2 Procedure

Expected Sequence 4.2 (SEND DTMF, with text attribute – Center Alignment)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.2.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.2.1
7	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with center alignment]
8	ME → USS	Start DTMF 1.1	["1"]
9	ME → USS	Start DTMF 1.2	["2"]
10	ME → USS	Start DTMF 1.3	["3"]
11	ME → USS	Start DTMF 1.4	["4"]
12	ME → USS	Start DTMF 1.5	["5"]
13	ME → USS	Start DTMF 1.6	["6"]
14	ME → USS	Start DTMF 1.7	["7"]
15	ME → USS	Start DTMF 1.8	["8"]
16	ME → USS	Start DTMF 1.9	["9"]
17	ME → USS	Start DTMF 1.10	["0"]
18	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.2.1	[Command performed successfully]
19	UICC → ME	PROACTIVE UICC SESSION ENDED
20	User → ME	End the call
21	User → ME	Set up a call to "+0123456789"
22	ME → USS	The ME attempts to set up a call to "+0123456789"
23	USS → ME	The ME receives the CONNECT message from the USS.
24	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.2.2
25	ME → UICC	FETCH
26	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.2.2
27	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Message shall be formatted without center alignment. Remark: If center alignment is the ME’s default alignment as declared in table A.2/17, no alignment change will take place]
28	ME → USS	Start DTMF 1.1	["1"]
29	ME → USS	Start DTMF 1.2	["2"]
30	ME → USS	Start DTMF 1.3	["3"]
31	ME → USS	Start DTMF 1.4	["4"]
32	ME → USS	Start DTMF 1.5	["5"]
33	ME → USS	Start DTMF 1.6	["6"]
34	ME → USS	Start DTMF 1.7	["7"]
35	ME → USS	Start DTMF 1.8	["8"]
36	ME → USS	Start DTMF 1.9	["9"]
37	ME → USS	Start DTMF 1.10	["0"]
38	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.2.1	[Command performed successfully]
39	UICC → ME	PROACTIVE UICC SESSION ENDED
40	User → ME	End the call

PROACTIVE COMMAND: SEND DTMF 4.2.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 1"

DTMF String: "1234567890"

Text Attribute

Formatting position: 0

Formatting length: 11

Formatting mode: Center Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	23	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	31
	AC	05	21	43	65	87	09	D0	04	00	0B	01
	B4

PROACTIVE COMMAND: SEND DTMF 4.2.2

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 2"

DTMF String: "1234567890"

Coding:

BER-TLV:	D0	1D	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	32
	AC	05	21	43	65	87	09

TERMINAL RESPONSE: SEND DTMF 4.2.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.24.4.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.2.

27.22.4.24.4.3 SEND DTMF (support of Text Attribute – Right Alignment)

27.22.4.24.4.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.24.4.3.2 Conformance requirement

The ME shall support the Proactive UICC: Send DTMF facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.24, clause 6.6.24, clause 8.12.2, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.44 and clause 8.70.

27.22.4.24.4.3.3 Test purpose

To verify that the ME does not locally generate audible DTMF tones and play them to the user.

To verify that if the ME is in idle mode it informs the UICC using TERMINAL RESPONSE ’20’ with the additional information "Not in speech call".

To verify that the ME displays the text contained in the SEND DTMF proactive UICC command.

To verify that the ME displays the alpha identifier according to the right alignment text attribute configuration which are referred to in the contents of the SEND DTMF proactive UICC command.

27.22.4.24.4.3.4 Method of test

27.22.4.24.4.3.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.24.4.3.4.2 Procedure

Expected Sequence 4.3 (SEND DTMF, with text attribute – Right Alignment)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.3.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.3.1
7	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with right alignment]
8	ME → USS	Start DTMF 1.1	["1"]
9	ME → USS	Start DTMF 1.2	["2"]
10	ME → USS	Start DTMF 1.3	["3"]
11	ME → USS	Start DTMF 1.4	["4"]
12	ME → USS	Start DTMF 1.5	["5"]
13	ME → USS	Start DTMF 1.6	["6"]
14	ME → USS	Start DTMF 1.7	["7"]
15	ME → USS	Start DTMF 1.8	["8"]
16	ME → USS	Start DTMF 1.9	["9"]
17	ME → USS	Start DTMF 1.10	["0"]
18	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.3.1	[Command performed successfully]
19	UICC → ME	PROACTIVE UICC SESSION ENDED
20	User → ME	End the call
21	User → ME	Set up a call to "+0123456789"
22	ME → USS	The ME attempts to set up a call to "+0123456789"
23	USS → ME	The ME receives the CONNECT message from the USS.
24	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.3.2
25	ME → UICC	FETCH
26	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.3.2
27	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Message shall be formatted without right alignment. Remark: If right alignment is the ME’s default alignment as declared in table A.2/17, no alignment change will take place]
28	ME → USS	Start DTMF 1.1	["1"]
29	ME → USS	Start DTMF 1.2	["2"]
30	ME → USS	Start DTMF 1.3	["3"]
31	ME → USS	Start DTMF 1.4	["4"]
32	ME → USS	Start DTMF 1.5	["5"]
33	ME → USS	Start DTMF 1.6	["6"]
34	ME → USS	Start DTMF 1.7	["7"]
35	ME → USS	Start DTMF 1.8	["8"]
36	ME → USS	Start DTMF 1.9	["9"]
37	ME → USS	Start DTMF 1.10	["0"]
38	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.3.1	[Command performed successfully]
39	UICC → ME	PROACTIVE UICC SESSION ENDED
40	User → ME	End the call

PROACTIVE COMMAND: SEND DTMF 4.3.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 1"

DTMF String: "1234567890"

Text Attribute

Formatting position: 0

Formatting length: 11

Formatting mode: Right Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	23	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	31
	AC	05	21	43	65	87	09	D0	04	00	B0	02
	B4

PROACTIVE COMMAND: SEND DTMF 4.3.2

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 2"

DTMF String: "1234567890"

Coding:

BER-TLV:	D0	1D	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	32
	AC	05	21	43	65	87	09

TERMINAL RESPONSE: SEND DTMF 4.3.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.24.4.3.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.3.

27.22.4.24.4.4 SEND DTMF (support of Text Attribute – Large Font Size)

27.22.4.24.4.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.24.4.4.2 Conformance requirement

The ME shall support the Proactive UICC: Send DTMF facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.24, clause 6.6.24, clause 8.12.2, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.44 and clause 8.70.

27.22.4.24.4.4.3 Test purpose

To verify that the ME does not locally generate audible DTMF tones and play them to the user.

To verify that if the ME is in idle mode it informs the UICC using TERMINAL RESPONSE ’20’ with the additional information "Not in speech call".

To verify that the ME displays the text contained in the SEND DTMF proactive UICC command.

To verify that the ME displays the alpha identifier according to the large font size text attribute configuration which are referred to in the contents of the SEND DTMF proactive UICC command.

27.22.4.24.4.4.4 Method of test

27.22.4.24.4.4.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.24.4.4.4.2 Procedure

Expected Sequence 4.4 (SEND DTMF, with text attribute – Large Font Size)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.4.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.4.1
7	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with large font size]
8	ME → USS	Start DTMF 1.1	["1"]
9	ME → USS	Start DTMF 1.2	["2"]
10	ME → USS	Start DTMF 1.3	["3"]
11	ME → USS	Start DTMF 1.4	["4"]
12	ME → USS	Start DTMF 1.5	["5"]
13	ME → USS	Start DTMF 1.6	["6"]
14	ME → USS	Start DTMF 1.7	["7"]
15	ME → USS	Start DTMF 1.8	["8"]
16	ME → USS	Start DTMF 1.9	["9"]
17	ME → USS	Start DTMF 1.10	["0"]
18	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.4.1	[Command performed successfully]
19	UICC → ME	PROACTIVE UICC SESSION ENDED
20	User → ME	End the call
21	User → ME	Set up a call to "+0123456789"
22	ME → USS	The ME attempts to set up a call to "+0123456789"
23	USS → ME	The ME receives the CONNECT message from the USS.
24	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.4.2
25	ME → UICC	FETCH
26	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.4.2
27	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with normal font size]
28	ME → USS	Start DTMF 1.1	["1"]
29	ME → USS	Start DTMF 1.2	["2"]
30	ME → USS	Start DTMF 1.3	["3"]
31	ME → USS	Start DTMF 1.4	["4"]
32	ME → USS	Start DTMF 1.5	["5"]
33	ME → USS	Start DTMF 1.6	["6"]
34	ME → USS	Start DTMF 1.7	["7"]
35	ME → USS	Start DTMF 1.8	["8"]
36	ME → USS	Start DTMF 1.9	["9"]
37	ME → USS	Start DTMF 1.10	["0"]
38	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.4.1	[Command performed successfully]
39	UICC → ME	PROACTIVE UICC SESSION ENDED
40	User → ME	End the call
41	User → ME	Set up a call to "+0123456789"
42	ME → USS	The ME attempts to set up a call to "+0123456789"
43	USS → ME	The ME receives the CONNECT message from the USS.
44	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.4.1
45	ME → UICC	FETCH
46	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.4.1
47	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with large font size]
48	ME → USS	Start DTMF 1.1	["1"]
49	ME → USS	Start DTMF 1.2	["2"]
50	ME → USS	Start DTMF 1.3	["3"]
51	ME → USS	Start DTMF 1.4	["4"]
52	ME → USS	Start DTMF 1.5	["5"]
53	ME → USS	Start DTMF 1.6	["6"]
54	ME → USS	Start DTMF 1.7	["7"]
55	ME → USS	Start DTMF 1.8	["8"]
56	ME → USS	Start DTMF 1.9	["9"]
57	ME → USS	Start DTMF 1.10	["0"]
58	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.4.1	[Command performed successfully]
59	UICC → ME	PROACTIVE UICC SESSION ENDED
60	User → ME	End the call
61	User → ME	Set up a call to "+0123456789"
62	ME → USS	The ME attempts to set up a call to "+0123456789"
63	USS → ME	The ME receives the CONNECT message from the USS.
64	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.4.3
65	ME → UICC	FETCH
66	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.4.3
67	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with normal font size]
68	ME → USS	Start DTMF 1.1	["1"]
69	ME → USS	Start DTMF 1.2	["2"]
70	ME → USS	Start DTMF 1.3	["3"]
71	ME → USS	Start DTMF 1.4	["4"]
72	ME → USS	Start DTMF 1.5	["5"]
73	ME → USS	Start DTMF 1.6	["6"]
74	ME → USS	Start DTMF 1.7	["7"]
75	ME → USS	Start DTMF 1.8	["8"]
76	ME → USS	Start DTMF 1.9	["9"]
77	ME → USS	Start DTMF 1.10	["0"]
78	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.4.1	[Command performed successfully]
79	UICC → ME	PROACTIVE UICC SESSION ENDED
80	User → ME	End the call

PROACTIVE COMMAND: SEND DTMF 4.4.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 1"

DTMF String: "1234567890"

Text Attribute

Formatting position: 0

Formatting length: 11

Formatting mode: Left Alignment, Large Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	23	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	31
	AC	05	21	43	65	87	09	D0	04	00	0B	04
	B4

PROACTIVE COMMAND: SEND DTMF 4.4.2

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 2"

DTMF String: "1234567890"

Text Attribute

Formatting position: 0

Formatting length: 11

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	23	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	32
	AC	05	21	43	65	87	09	D0	04	00	0B	00
	B4

PROACTIVE COMMAND: SEND DTMF 4.4.3

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 3"

DTMF String: "1234567890"

Coding:

BER-TLV:	D0	1D	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	33
	AC	05	21	43	65	87	09

TERMINAL RESPONSE: SEND DTMF 4.4.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.24.4.4.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.4.

27.22.4.24.4.5 SEND DTMF (support of Text Attribute – Small Font Size)

27.22.4.24.4.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.24.4.5.2 Conformance requirement

The ME shall support the Proactive UICC: Send DTMF facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.24, clause 6.6.24, clause 8.12.2, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.44 and clause 8.70.

27.22.4.24.4.5.3 Test purpose

To verify that the ME does not locally generate audible DTMF tones and play them to the user.

To verify that if the ME is in idle mode it informs the UICC using TERMINAL RESPONSE ’20’ with the additional information "Not in speech call".

To verify that the ME displays the text contained in the SEND DTMF proactive UICC command.

To verify that the ME displays the alpha identifier according to the small font size text attribute configuration which are referred to in the contents of the SEND DTMF proactive UICC command.

27.22.4.24.4.5.4 Method of test

27.22.4.24.4.5.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.24.4.5.4.2 Procedure

Expected Sequence 4.5 (SEND DTMF, with text attribute – Small Font Size)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.5.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.5.1
7	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with small font size]
8	ME → USS	Start DTMF 1.1	["1"]
9	ME → USS	Start DTMF 1.2	["2"]
10	ME → USS	Start DTMF 1.3	["3"]
11	ME → USS	Start DTMF 1.4	["4"]
12	ME → USS	Start DTMF 1.5	["5"]
13	ME → USS	Start DTMF 1.6	["6"]
14	ME → USS	Start DTMF 1.7	["7"]
15	ME → USS	Start DTMF 1.8	["8"]
16	ME → USS	Start DTMF 1.9	["9"]
17	ME → USS	Start DTMF 1.10	["0"]
18	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.5.1	[Command performed successfully]
19	UICC → ME	PROACTIVE UICC SESSION ENDED
20	User → ME	End the call
21	User → ME	Set up a call to "+0123456789"
22	ME → USS	The ME attempts to set up a call to "+0123456789"
23	USS → ME	The ME receives the CONNECT message from the USS.
24	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.5.2
25	ME → UICC	FETCH
26	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.5.2
27	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with normal font size]
28	ME → USS	Start DTMF 1.1	["1"]
29	ME → USS	Start DTMF 1.2	["2"]
30	ME → USS	Start DTMF 1.3	["3"]
31	ME → USS	Start DTMF 1.4	["4"]
32	ME → USS	Start DTMF 1.5	["5"]
33	ME → USS	Start DTMF 1.6	["6"]
34	ME → USS	Start DTMF 1.7	["7"]
35	ME → USS	Start DTMF 1.8	["8"]
36	ME → USS	Start DTMF 1.9	["9"]
37	ME → USS	Start DTMF 1.10	["0"]
38	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.5.1	[Command performed successfully]
39	UICC → ME	PROACTIVE UICC SESSION ENDED
40	User → ME	End the call
41	User → ME	Set up a call to "+0123456789"
42	ME → USS	The ME attempts to set up a call to "+0123456789"
43	USS → ME	The ME receives the CONNECT message from the USS.
44	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.5.1
45	ME → UICC	FETCH
46	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.5.1
47	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with small font size]
48	ME → USS	Start DTMF 1.1	["1"]
49	ME → USS	Start DTMF 1.2	["2"]
50	ME → USS	Start DTMF 1.3	["3"]
51	ME → USS	Start DTMF 1.4	["4"]
52	ME → USS	Start DTMF 1.5	["5"]
53	ME → USS	Start DTMF 1.6	["6"]
54	ME → USS	Start DTMF 1.7	["7"]
55	ME → USS	Start DTMF 1.8	["8"]
56	ME → USS	Start DTMF 1.9	["9"]
57	ME → USS	Start DTMF 1.10	["0"]
58	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.5.1	[Command performed successfully]
59	UICC → ME	PROACTIVE UICC SESSION ENDED
60	User → ME	End the call
61	User → ME	Set up a call to "+0123456789"
62	ME → USS	The ME attempts to set up a call to "+0123456789"
63	USS → ME	The ME receives the CONNECT message from the USS.
64	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.5.3
65	ME → UICC	FETCH
66	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.5.3
67	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with normal font size]
68	ME → USS	Start DTMF 1.1	["1"]
69	ME → USS	Start DTMF 1.2	["2"]
70	ME → USS	Start DTMF 1.3	["3"]
71	ME → USS	Start DTMF 1.4	["4"]
72	ME → USS	Start DTMF 1.5	["5"]
73	ME → USS	Start DTMF 1.6	["6"]
74	ME → USS	Start DTMF 1.7	["7"]
75	ME → USS	Start DTMF 1.8	["8"]
76	ME → USS	Start DTMF 1.9	["9"]
77	ME → USS	Start DTMF 1.10	["0"]
78	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.5.1	[Command performed successfully]
79	UICC → ME	PROACTIVE UICC SESSION ENDED
80	User → ME	End the call

PROACTIVE COMMAND: SEND DTMF 4.5.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 1"

DTMF String: "1234567890"

Text Attribute

Formatting position: 0

Formatting length: 11

Formatting mode: Left Alignment, Small Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	23	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	31
	AC	05	21	43	65	87	09	D0	04	00	0B	08
	B4

PROACTIVE COMMAND: SEND DTMF 4.5.2

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 2"

DTMF String: "1234567890"

Text Attribute

Formatting position: 0

Formatting length: 11

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	23	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	32
	AC	05	21	43	65	87	09	D0	04	00	0B	00
	B4

PROACTIVE COMMAND: SEND DTMF 4.5.3

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 3"

DTMF String: "1234567890"

Coding:

BER-TLV:	D0	1D	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	33
	AC	05	21	43	65	87	09

TERMINAL RESPONSE: SEND DTMF 4.5.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.24.4.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.5.

27.22.4.24.4.6 SEND DTMF (support of Text Attribute – Bold On)

27.22.4.24.4.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.24.4.6.2 Conformance requirement

The ME shall support the Proactive UICC: Send DTMF facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.24, clause 6.6.24, clause 8.12.2, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.44 and clause 8.70.

27.22.4.24.4.6.3 Test purpose

To verify that the ME does not locally generate audible DTMF tones and play them to the user.

To verify that if the ME is in idle mode it informs the UICC using TERMINAL RESPONSE ’20’ with the additional information "Not in speech call".

To verify that the ME displays the text contained in the SEND DTMF proactive UICC command.

To verify that the ME displays the alpha identifier according to the bold text attribute configuration which are referred to in the contents of the SEND DTMF proactive UICC command.

27.22.4.24.4.6.4 Method of test

27.22.4.24.4.6.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.24.4.6.4.2 Procedure

Expected Sequence 4.6 (SEND DTMF, with text attribute – Bold On)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.6.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.6.1
7	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with bold on]
8	ME → USS	Start DTMF 1.1	["1"]
9	ME → USS	Start DTMF 1.2	["2"]
10	ME → USS	Start DTMF 1.3	["3"]
11	ME → USS	Start DTMF 1.4	["4"]
12	ME → USS	Start DTMF 1.5	["5"]
13	ME → USS	Start DTMF 1.6	["6"]
14	ME → USS	Start DTMF 1.7	["7"]
15	ME → USS	Start DTMF 1.8	["8"]
16	ME → USS	Start DTMF 1.9	["9"]
17	ME → USS	Start DTMF 1.10	["0"]
18	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.6.1	[Command performed successfully]
19	UICC → ME	PROACTIVE UICC SESSION ENDED
20	User → ME	End the call
21	User → ME	Set up a call to "+0123456789"
22	ME → USS	The ME attempts to set up a call to "+0123456789"
23	USS → ME	The ME receives the CONNECT message from the USS.
24	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.6.2
25	ME → UICC	FETCH
26	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.6.2
27	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with bold off]
28	ME → USS	Start DTMF 1.1	["1"]
29	ME → USS	Start DTMF 1.2	["2"]
30	ME → USS	Start DTMF 1.3	["3"]
31	ME → USS	Start DTMF 1.4	["4"]
32	ME → USS	Start DTMF 1.5	["5"]
33	ME → USS	Start DTMF 1.6	["6"]
34	ME → USS	Start DTMF 1.7	["7"]
35	ME → USS	Start DTMF 1.8	["8"]
36	ME → USS	Start DTMF 1.9	["9"]
37	ME → USS	Start DTMF 1.10	["0"]
38	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.6.1	[Command performed successfully]
39	UICC → ME	PROACTIVE UICC SESSION ENDED
40	User → ME	End the call
41	User → ME	Set up a call to "+0123456789"
42	ME → USS	The ME attempts to set up a call to "+0123456789"
43	USS → ME	The ME receives the CONNECT message from the USS.
44	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.6.1
45	ME → UICC	FETCH
46	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.6.1
47	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with bold on]
48	ME → USS	Start DTMF 1.1	["1"]
49	ME → USS	Start DTMF 1.2	["2"]
50	ME → USS	Start DTMF 1.3	["3"]
51	ME → USS	Start DTMF 1.4	["4"]
52	ME → USS	Start DTMF 1.5	["5"]
53	ME → USS	Start DTMF 1.6	["6"]
54	ME → USS	Start DTMF 1.7	["7"]
55	ME → USS	Start DTMF 1.8	["8"]
56	ME → USS	Start DTMF 1.9	["9"]
57	ME → USS	Start DTMF 1.10	["0"]
58	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.6.1	[Command performed successfully]
59	UICC → ME	PROACTIVE UICC SESSION ENDED
60	User → ME	End the call
61	User → ME	Set up a call to "+0123456789"
62	ME → USS	The ME attempts to set up a call to "+0123456789"
63	USS → ME	The ME receives the CONNECT message from the USS.
64	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.6.3
65	ME → UICC	FETCH
66	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.6.3
67	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with bold off]
68	ME → USS	Start DTMF 1.1	["1"]
69	ME → USS	Start DTMF 1.2	["2"]
70	ME → USS	Start DTMF 1.3	["3"]
71	ME → USS	Start DTMF 1.4	["4"]
72	ME → USS	Start DTMF 1.5	["5"]
73	ME → USS	Start DTMF 1.6	["6"]
74	ME → USS	Start DTMF 1.7	["7"]
75	ME → USS	Start DTMF 1.8	["8"]
76	ME → USS	Start DTMF 1.9	["9"]
77	ME → USS	Start DTMF 1.10	["0"]
78	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.6.1	[Command performed successfully]
79	UICC → ME	PROACTIVE UICC SESSION ENDED
80	User → ME	End the call

PROACTIVE COMMAND: SEND DTMF 4.6.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 1"

DTMF String: "1234567890"

Text Attribute

Formatting position: 0

Formatting length: 11

Formatting mode: Left Alignment, Normal Font, Bold On, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	23	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	31
	AC	05	21	43	65	87	09	D0	04	00	0B	10
	B4	00

PROACTIVE COMMAND: SEND DTMF 4.6.2

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 2"

DTMF String: "1234567890"

Text Attribute

Formatting position: 0

Formatting length: 11

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	23	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	32
	AC	05	21	43	65	87	09	D0	04	00	0B	00
	B4

PROACTIVE COMMAND: SEND DTMF 4.6.3

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 3"

DTMF String: "1234567890"

Coding:

BER-TLV:	D0	1D	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	33
	AC	05	21	43	65	87	09

TERMINAL RESPONSE: SEND DTMF 4.6.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.24.4.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.6.

27.22.4.24.4.7 SEND DTMF (support of Text Attribute – Italic On)

27.22.4.24.4.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.24.4.7.2 Conformance requirement

The ME shall support the Proactive UICC: Send DTMF facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.24, clause 6.6.24, clause 8.12.2, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.44 and clause 8.70.

27.22.4.24.4.7.3 Test purpose

To verify that the ME does not locally generate audible DTMF tones and play them to the user.

To verify that if the ME is in idle mode it informs the UICC using TERMINAL RESPONSE ’20’ with the additional information "Not in speech call".

To verify that the ME displays the text contained in the SEND DTMF proactive UICC command.

To verify that the ME displays the alpha identifier according to the italic text attribute configuration which are referred to in the contents of the SEND DTMF proactive UICC command.

27.22.4.24.4.7.4 Method of test

27.22.4.24.4.7.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.24.4.7.4.2 Procedure

Expected Sequence 4.7 (SEND DTMF, with text attribute – Italic On)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.7.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.7.1
7	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with italic on]
8	ME → USS	Start DTMF 1.1	["1"]
9	ME → USS	Start DTMF 1.2	["2"]
10	ME → USS	Start DTMF 1.3	["3"]
11	ME → USS	Start DTMF 1.4	["4"]
12	ME → USS	Start DTMF 1.5	["5"]
13	ME → USS	Start DTMF 1.6	["6"]
14	ME → USS	Start DTMF 1.7	["7"]
15	ME → USS	Start DTMF 1.8	["8"]
16	ME → USS	Start DTMF 1.9	["9"]
17	ME → USS	Start DTMF 1.10	["0"]
18	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.7.1	[Command performed successfully]
19	UICC → ME	PROACTIVE UICC SESSION ENDED
20	User → ME	End the call
21	User → ME	Set up a call to "+0123456789"
22	ME → USS	The ME attempts to set up a call to "+0123456789"
23	USS → ME	The ME receives the CONNECT message from the USS.
24	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.7.2
25	ME → UICC	FETCH
26	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.7.2
27	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with italic off]
28	ME → USS	Start DTMF 1.1	["1"]
29	ME → USS	Start DTMF 1.2	["2"]
30	ME → USS	Start DTMF 1.3	["3"]
31	ME → USS	Start DTMF 1.4	["4"]
32	ME → USS	Start DTMF 1.5	["5"]
33	ME → USS	Start DTMF 1.6	["6"]
34	ME → USS	Start DTMF 1.7	["7"]
35	ME → USS	Start DTMF 1.8	["8"]
36	ME → USS	Start DTMF 1.9	["9"]
37	ME → USS	Start DTMF 1.10	["0"]
38	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.7.1	[Command performed successfully]
39	UICC → ME	PROACTIVE UICC SESSION ENDED
40	User → ME	End the call
41	User → ME	Set up a call to "+0123456789"
42	ME → USS	The ME attempts to set up a call to "+0123456789"
43	USS → ME	The ME receives the CONNECT message from the USS.
44	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.7.1
45	ME → UICC	FETCH
46	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.7.1
47	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with italic on]
48	ME → USS	Start DTMF 1.1	["1"]
49	ME → USS	Start DTMF 1.2	["2"]
50	ME → USS	Start DTMF 1.3	["3"]
51	ME → USS	Start DTMF 1.4	["4"]
52	ME → USS	Start DTMF 1.5	["5"]
53	ME → USS	Start DTMF 1.6	["6"]
54	ME → USS	Start DTMF 1.7	["7"]
55	ME → USS	Start DTMF 1.8	["8"]
56	ME → USS	Start DTMF 1.9	["9"]
57	ME → USS	Start DTMF 1.10	["0"]
58	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.7.1	[Command performed successfully]
59	UICC → ME	PROACTIVE UICC SESSION ENDED
60	User → ME	End the call
61	User → ME	Set up a call to "+0123456789"
62	ME → USS	The ME attempts to set up a call to "+0123456789"
63	USS → ME	The ME receives the CONNECT message from the USS.
64	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.7.3
65	ME → UICC	FETCH
66	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.7.3
67	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with italic off]
68	ME → USS	Start DTMF 1.1	["1"]
69	ME → USS	Start DTMF 1.2	["2"]
70	ME → USS	Start DTMF 1.3	["3"]
71	ME → USS	Start DTMF 1.4	["4"]
72	ME → USS	Start DTMF 1.5	["5"]
73	ME → USS	Start DTMF 1.6	["6"]
74	ME → USS	Start DTMF 1.7	["7"]
75	ME → USS	Start DTMF 1.8	["8"]
76	ME → USS	Start DTMF 1.9	["9"]
77	ME → USS	Start DTMF 1.10	["0"]
78	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.7.1	[Command performed successfully]
79	UICC → ME	PROACTIVE UICC SESSION ENDED
80	User → ME	End the call

PROACTIVE COMMAND: SEND DTMF 4.7.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 1"

DTMF String: "1234567890"

Text Attribute

Formatting position: 0

Formatting length: 11

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic On, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	23	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	31
	AC	05	21	43	65	87	09	D0	04	00	0B	20
	B4

PROACTIVE COMMAND: SEND DTMF 4.7.2

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 2"

DTMF String: "1234567890"

Text Attribute

Formatting position: 0

Formatting length: 11

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	23	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	32
	AC	05	21	43	65	87	09	D0	04	00	0B	00
	B4

PROACTIVE COMMAND: SEND DTMF 4.7.3

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 3"

DTMF String: "1234567890"

Coding:

BER-TLV:	D0	1D	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	33
	AC	05	21	43	65	87	09

TERMINAL RESPONSE: SEND DTMF 4.7.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.24.4.7.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.7.

27.22.4.24.4.8 SEND DTMF (support of Text Attribute – Underline On)

27.22.4.24.4.8.1 Definition and applicability

See clause 3.2.2.

27.22.4.24.4.8.2 Conformance requirement

The ME shall support the Proactive UICC: Send DTMF facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.24, clause 6.6.24, clause 8.12.2, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.44 and clause 8.70.

27.22.4.24.4.8.3 Test purpose

To verify that the ME does not locally generate audible DTMF tones and play them to the user.

To verify that if the ME is in idle mode it informs the UICC using TERMINAL RESPONSE ’20’ with the additional information "Not in speech call".

To verify that the ME displays the text contained in the SEND DTMF proactive UICC command.

To verify that the ME displays the alpha identifier according to the underline text attribute configuration which are referred to in the contents of the SEND DTMF proactive UICC command.

27.22.4.24.4.8.4 Method of test

27.22.4.24.4.8.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.24.4.8.4.2 Procedure

Expected Sequence 4.8 (SEND DTMF, with text attribute – Underline On)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.8.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.8.1
7	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with underline on]
8	ME → USS	Start DTMF 1.1	["1"]
9	ME → USS	Start DTMF 1.2	["2"]
10	ME → USS	Start DTMF 1.3	["3"]
11	ME → USS	Start DTMF 1.4	["4"]
12	ME → USS	Start DTMF 1.5	["5"]
13	ME → USS	Start DTMF 1.6	["6"]
14	ME → USS	Start DTMF 1.7	["7"]
15	ME → USS	Start DTMF 1.8	["8"]
16	ME → USS	Start DTMF 1.9	["9"]
17	ME → USS	Start DTMF 1.10	["0"]
18	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.8.1	[Command performed successfully]
19	UICC → ME	PROACTIVE UICC SESSION ENDED
20	User → ME	End the call
21	User → ME	Set up a call to "+0123456789"
22	ME → USS	The ME attempts to set up a call to "+0123456789"
23	USS → ME	The ME receives the CONNECT message from the USS.
24	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.8.2
25	ME → UICC	FETCH
26	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.8.2
27	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with underline off]
28	ME → USS	Start DTMF 1.1	["1"]
29	ME → USS	Start DTMF 1.2	["2"]
30	ME → USS	Start DTMF 1.3	["3"]
31	ME → USS	Start DTMF 1.4	["4"]
32	ME → USS	Start DTMF 1.5	["5"]
33	ME → USS	Start DTMF 1.6	["6"]
34	ME → USS	Start DTMF 1.7	["7"]
35	ME → USS	Start DTMF 1.8	["8"]
36	ME → USS	Start DTMF 1.9	["9"]
37	ME → USS	Start DTMF 1.10	["0"]
38	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.8.1	[Command performed successfully]
39	UICC → ME	PROACTIVE UICC SESSION ENDED
40	User → ME	End the call
41	User → ME	Set up a call to "+0123456789"
42	ME → USS	The ME attempts to set up a call to "+0123456789"
43	USS → ME	The ME receives the CONNECT message from the USS.
44	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.8.1
45	ME → UICC	FETCH
46	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.8.1
47	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with underline on]
48	ME → USS	Start DTMF 1.1	["1"]
49	ME → USS	Start DTMF 1.2	["2"]
50	ME → USS	Start DTMF 1.3	["3"]
51	ME → USS	Start DTMF 1.4	["4"]
52	ME → USS	Start DTMF 1.5	["5"]
53	ME → USS	Start DTMF 1.6	["6"]
54	ME → USS	Start DTMF 1.7	["7"]
55	ME → USS	Start DTMF 1.8	["8"]
56	ME → USS	Start DTMF 1.9	["9"]
57	ME → USS	Start DTMF 1.10	["0"]
58	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.8.1	[Command performed successfully]
59	UICC → ME	PROACTIVE UICC SESSION ENDED
60	User → ME	End the call
61	User → ME	Set up a call to "+0123456789"
62	ME → USS	The ME attempts to set up a call to "+0123456789"
63	USS → ME	The ME receives the CONNECT message from the USS.
64	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.8.3
65	ME → UICC	FETCH
66	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.8.3
67	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with underline off]
68	ME → USS	Start DTMF 1.1	["1"]
69	ME → USS	Start DTMF 1.2	["2"]
70	ME → USS	Start DTMF 1.3	["3"]
71	ME → USS	Start DTMF 1.4	["4"]
72	ME → USS	Start DTMF 1.5	["5"]
73	ME → USS	Start DTMF 1.6	["6"]
74	ME → USS	Start DTMF 1.7	["7"]
75	ME → USS	Start DTMF 1.8	["8"]
76	ME → USS	Start DTMF 1.9	["9"]
77	ME → USS	Start DTMF 1.10	["0"]
78	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.8.1	[Command performed successfully]
79	UICC → ME	PROACTIVE UICC SESSION ENDED
80	User → ME	End the call

PROACTIVE COMMAND: SEND DTMF 4.8.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 1"

DTMF String: "1234567890"

Text Attribute

Formatting position: 0

Formatting length: 11

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline On, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	23	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	31
	AC	05	21	43	65	87	09	D0	04	00	0B	40
	B4

PROACTIVE COMMAND: SEND DTMF 4.8.2

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 2"

DTMF String: "1234567890"

Text Attribute

Formatting position: 0

Formatting length: 11

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	23	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	32
	AC	05	21	43	65	87	09	D0	04	00	0B	00
	B4

PROACTIVE COMMAND: SEND DTMF 4.8.3

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 3"

DTMF String: "1234567890"

Coding:

BER-TLV:	D0	1D	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	33
	AC	05	21	43	65	87	09

TERMINAL RESPONSE: SEND DTMF 4.8.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.24.4.8.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.8.

27.22.4.24.4.9 SEND DTMF (support of Text Attribute – Strikethrough On)

27.22.4.24.4.9.1 Definition and applicability

See clause 3.2.2.

27.22.4.24.4.9.2 Conformance requirement

The ME shall support the Proactive UICC: Send DTMF facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.24, clause 6.6.24, clause 8.12.2, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.44 and clause 8.70.

27.22.4.24.4.9.3 Test purpose

To verify that the ME does not locally generate audible DTMF tones and play them to the user.

To verify that if the ME is in idle mode it informs the UICC using TERMINAL RESPONSE ’20’ with the additional information "Not in speech call".

To verify that the ME displays the text contained in the SEND DTMF proactive UICC command.

To verify that the ME displays the alpha identifier according to the strikethrough text attribute configuration which are referred to in the contents of the SEND DTMF proactive UICC command.

27.22.4.24.4.9.4 Method of test

27.22.4.24.4.9.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.24.4.9.4.2 Procedure

Expected Sequence 4.9 (SEND DTMF, with text attribute – Strikethrough On)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.9.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.9.1
7	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with strikethrough on]
8	ME → USS	Start DTMF 1.1	["1"]
9	ME → USS	Start DTMF 1.2	["2"]
10	ME → USS	Start DTMF 1.3	["3"]
11	ME → USS	Start DTMF 1.4	["4"]
12	ME → USS	Start DTMF 1.5	["5"]
13	ME → USS	Start DTMF 1.6	["6"]
14	ME → USS	Start DTMF 1.7	["7"]
15	ME → USS	Start DTMF 1.8	["8"]
16	ME → USS	Start DTMF 1.9	["9"]
17	ME → USS	Start DTMF 1.10	["0"]
18	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.9.1	[Command performed successfully]
19	UICC → ME	PROACTIVE UICC SESSION ENDED
20	User → ME	End the call
21	User → ME	Set up a call to "+0123456789"
22	ME → USS	The ME attempts to set up a call to "+0123456789"
23	USS → ME	The ME receives the CONNECT message from the USS.
24	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.9.2
25	ME → UICC	FETCH
26	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.9.2
27	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with strikethrough off]
28	ME → USS	Start DTMF 1.1	["1"]
29	ME → USS	Start DTMF 1.2	["2"]
30	ME → USS	Start DTMF 1.3	["3"]
31	ME → USS	Start DTMF 1.4	["4"]
32	ME → USS	Start DTMF 1.5	["5"]
33	ME → USS	Start DTMF 1.6	["6"]
34	ME → USS	Start DTMF 1.7	["7"]
35	ME → USS	Start DTMF 1.8	["8"]
36	ME → USS	Start DTMF 1.9	["9"]
37	ME → USS	Start DTMF 1.10	["0"]
38	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.9.1	[Command performed successfully]
39	UICC → ME	PROACTIVE UICC SESSION ENDED
40	User → ME	End the call
41	User → ME	Set up a call to "+0123456789"
42	ME → USS	The ME attempts to set up a call to "+0123456789"
43	USS → ME	The ME receives the CONNECT message from the USS.
44	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.9.1
45	ME → UICC	FETCH
46	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.9.1
47	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with strikethrough on]
48	ME → USS	Start DTMF 1.1	["1"]
49	ME → USS	Start DTMF 1.2	["2"]
50	ME → USS	Start DTMF 1.3	["3"]
51	ME → USS	Start DTMF 1.4	["4"]
52	ME → USS	Start DTMF 1.5	["5"]
53	ME → USS	Start DTMF 1.6	["6"]
54	ME → USS	Start DTMF 1.7	["7"]
55	ME → USS	Start DTMF 1.8	["8"]
56	ME → USS	Start DTMF 1.9	["9"]
57	ME → USS	Start DTMF 1.10	["0"]
58	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.9.1	[Command performed successfully]
59	UICC → ME	PROACTIVE UICC SESSION ENDED
60	User → ME	End the call
61	User → ME	Set up a call to "+0123456789"
62	ME → USS	The ME attempts to set up a call to "+0123456789"
63	USS → ME	The ME receives the CONNECT message from the USS.
64	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.9.3
65	ME → UICC	FETCH
66	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.9.3
67	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with strikethrough off]
68	ME → USS	Start DTMF 1.1	["1"]
69	ME → USS	Start DTMF 1.2	["2"]
70	ME → USS	Start DTMF 1.3	["3"]
71	ME → USS	Start DTMF 1.4	["4"]
72	ME → USS	Start DTMF 1.5	["5"]
73	ME → USS	Start DTMF 1.6	["6"]
74	ME → USS	Start DTMF 1.7	["7"]
75	ME → USS	Start DTMF 1.8	["8"]
76	ME → USS	Start DTMF 1.9	["9"]
77	ME → USS	Start DTMF 1.10	["0"]
78	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.9.1	[Command performed successfully]
79	UICC → ME	PROACTIVE UICC SESSION ENDED
80	User → ME	End the call

PROACTIVE COMMAND: SEND DTMF 4.9.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 1"

DTMF String: "1234567890"

Text Attribute

Formatting position: 0

Formatting length: 11

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough On

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	23	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	31
	AC	05	21	43	65	87	09	D0	04	00	0B	80B
	B4

PROACTIVE COMMAND: SEND DTMF 4.9.2

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 2"

DTMF String: "1234567890"

Text Attribute

Formatting position: 0

Formatting length: 11

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	23	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	32
	AC	05	21	43	65	87	09	D0	04	00	0B	00
	B4

PROACTIVE COMMAND: SEND DTMF 4.9.3

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 3"

DTMF String: "1234567890"

Coding:

BER-TLV:	D0	1D	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	33
	AC	05	21	43	65	87	09

TERMINAL RESPONSE: SEND DTMF 4.9.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.24.4.9.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.9.

27.22.4.24.4.10 SEND DTMF (support of Text Attribute – Foreground and Background Colour)

27.22.4.24.4.10.1 Definition and applicability

See clause 3.2.2.

27.22.4.24.4.10.2 Conformance requirement

The ME shall support the Proactive UICC: Send DTMF facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.24, clause 6.6.24, clause 8.12.2, clause 5.2, clause 8.6, clause 8.7, clause 8.2, clause 8.44 and clause 8.70.

27.22.4.24.4.10.3 Test purpose

To verify that the ME does not locally generate audible DTMF tones and play them to the user.

To verify that if the ME is in idle mode it informs the UICC using TERMINAL RESPONSE ’20’ with the additional information "Not in speech call".

To verify that the ME displays the text contained in the SEND DTMF proactive UICC command.

To verify that the ME displays the alpha identifier according to the foreground and background colour text attribute configuration which are referred to in the contents of the SEND DTMF proactive UICC command.

27.22.4.24.4.10.4 Method of test

27.22.4.24.4.10.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on, performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the USS.

27.22.4.24.4.10.4.2 Procedure

Expected Sequence 4.10 (SEND DTMF, with text attribute – Foreground and Background Colour)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.10.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.10.1
7	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with foreground and background colour according to the text attribute configuration]
8	ME → USS	Start DTMF 1.1	["1"]
9	ME → USS	Start DTMF 1.2	["2"]
10	ME → USS	Start DTMF 1.3	["3"]
11	ME → USS	Start DTMF 1.4	["4"]
12	ME → USS	Start DTMF 1.5	["5"]
13	ME → USS	Start DTMF 1.6	["6"]
14	ME → USS	Start DTMF 1.7	["7"]
15	ME → USS	Start DTMF 1.8	["8"]
16	ME → USS	Start DTMF 1.9	["9"]
17	ME → USS	Start DTMF 1.10	["0"]
18	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.10.1	[Command performed successfully]
19	UICC → ME	PROACTIVE UICC SESSION ENDED
20	User → ME	End the call
21	User → ME	Set up a call to "+0123456789"
22	ME → USS	The ME attempts to set up a call to "+0123456789"
23	USS → ME	The ME receives the CONNECT message from the USS.
24	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 4.10.2
25	ME → UICC	FETCH
26	UICC → ME	PROACTIVE COMMAND: SEND DTMF 4.10.2
27	ME → USER	Display "Send DTMF" Do not locally generate audible DTMF tones and play them to the user.	[Alpha identifier is displayed with ME’s default foreground and background colour]
28	ME → USS	Start DTMF 1.1	["1"]
29	ME → USS	Start DTMF 1.2	["2"]
30	ME → USS	Start DTMF 1.3	["3"]
31	ME → USS	Start DTMF 1.4	["4"]
32	ME → USS	Start DTMF 1.5	["5"]
33	ME → USS	Start DTMF 1.6	["6"]
34	ME → USS	Start DTMF 1.7	["7"]
35	ME → USS	Start DTMF 1.8	["8"]
36	ME → USS	Start DTMF 1.9	["9"]
37	ME → USS	Start DTMF 1.10	["0"]
38	ME → UICC	TERMINAL RESPONSE: SEND DTMF 4.10.1	[Command performed successfully]
39	UICC → ME	PROACTIVE UICC SESSION ENDED
40	User → ME	End the call

PROACTIVE COMMAND: SEND DTMF 4.10.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 1"

DTMF String: "1234567890"

Text Attribute

Formatting position: 0

Formatting length: 11

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	23	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	31
	AC	05	21	43	65	87	09	D0	04	00	0B	00
	B4

PROACTIVE COMMAND: SEND DTMF 4.10.2

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha identifier: "Send DTMF 2"

DTMF String: "1234567890"

Coding:

BER-TLV:	D0	1D	81	03	01	14	00	82	02	81	83	85
	0B	53	65	6E	64	20	44	54	4D	46	20	32
	AC	05	21	43	65	87	09

TERMINAL RESPONSE: SEND DTMF 4.10.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.24.4.10.5 Test requirement

The ME shall operate in the manner defined in expected sequence 4.10.

27.22.4.24.5 SEND DTMF (UCS2 Display in Chinese)

27.22.4.24.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.24.5.2 Conformance requirement

The ME shall support the Proactive UICC: Send DTMF facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.24, clause 6.6.24, clause 8.12.2, clause 5.2, clause 8.6, clause 8.7, clause 8.2 and clause 8.44.

Additionally the ME shall support the UCS2 facility for the coding of the Chinese characters , as defined in:

– ISO/IEC 10646. [17].

27.22.4.24.5.3 Test purpose

To verify that the ME displays the UCS2 text contained in the SEND DTMF proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.24.5.4 Method of test

27.22.4.24.5.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table. The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.24.5.4.2 Procedure

Expected Sequence 5.1 (SEND DTMF, successful, UCS2 text in Chinese)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 5.1.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 5.1.1
7	ME → USER	Display "你好"	["Hello" in Chinese]
8	ME → USS	Start DTMF 1.1	["1"]
9	ME		No DTMF sending for 3 seconds ±20%
10	ME → USS	Start DTMF 1.2	["2"]
11	ME → UICC	TERMINAL RESPONSE: SEND DTMF 5.1.1	[Command performed successfully]
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13	User → ME	End the call

PROACTIVE COMMAND: SEND DTMF 5.1.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha Identifier

Text: "你好"

DTMF String: "1" pause "2"

Coding:

BER-TLV:	D0	14	81	03	01	14	00	82	02	81	83	85
	05	80	4F	60	59	7D	AC	02	C1	F2

TERMINAL RESPONSE: SEND DTMF 5.1.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successful

Coding:

BER-TLV:

27.22.4.24.5.5 Test requirement

The ME shall operate in the manner defined in expected sequence 5.1.

27.22.4.24.6 SEND DTMF (UCS2 Display in Katakana)

27.22.4.24.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.24.6.2 Conformance requirement

The ME shall support the Proactive UICC: Send DTMF facility as defined in:

– TS 31.111 [15] clause 6.1, clause 6.4.24, clause 6.6.24, clause 8.12.2, clause 5.2, clause 8.6, clause 8.7, clause 8.2 and clause 8.44.

Additionally the ME shall support the UCS2 facility for the coding of the Katakana characters , as defined in:

– ISO/IEC 10646. [17].

27.22.4.24.6.3 Test purpose

To verify that the ME displays the UCS2 text contained in the SEND DTMF proactive UICC command, and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.24.6.4 Method of test

27.22.4.24.6.4.1 Initial conditions

The ME is connected to the USIM Simulator and only connected to the USS if the USS is mentioned in the sequence table. The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.24.6.4.2 Procedure

Expected Sequence 6.1 (SEND DTMF, successful, UCS2 text)

Some details of the DTMF protocol have been left out for clarity.

Step	Direction	MESSAGE / Action	Comments
1	User → ME	Set up a call to "+0123456789"
2	ME → USS	The ME attempts to set up a call to "+0123456789"
3	USS → ME	The ME receives the CONNECT message from the USS.
4	UICC → ME	PROACTIVE COMMAND PENDING: SEND DTMF 6.1.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: SEND DTMF 6.1.1
7	ME → USER	Display "ル"	[Character in Katakana]
8	ME → USS	Start DTMF 1.1	["1"]
9	ME		No DTMF sending for 3 seconds ±20%
10	ME → USS	Start DTMF 1.2	["2"]
11	ME → UICC	TERMINAL RESPONSE: SEND DTMF 6.1.1	[Command performed successfully]
12	UICC → ME	PROACTIVE UICC SESSION ENDED
13	User → ME	End the call

PROACTIVE COMMAND: SEND DTMF 6.1.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: UICC

Destination device: Network

Alpha Identifier

Text: "ル"

DTMF String: "1" pause "2"

Coding:

BER-TLV:	D0	12	81	03	01	14	00	82	02	81	83	85
	03	80	30	EB	AC	02	C1	F2

TERMINAL RESPONSE: SEND DTMF 6.1.1

Logically:

Command details

Command number: 1

Command type: SEND DTMF

Command qualifier: "00"

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successful

Coding:

BER-TLV:

27.22.4.24.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.1.

27.22.4.25 LANGUAGE NOTIFICATION

27.22.4.25.1 Definition and applicability

See clause 3.2.2.

27.22.4.25.2 Conformance Requirement

The ME shall conclude the command by sending TERMINAL RESPONSE (OK) to the UICC, as soon as possible after receiving the LANGUAGE NOTIFICATION proactive UICC command.

– TS 31.111 [15] clause 6.4.25 and clause 6.6.25.

27.22.4.25.3 Test purpose

To verify that the ME shall send a TERMINAL RESPONSE (OK) to the UICC after the ME receives the LANGUAGE NOTIFICATION proactive UICC command.

27.22.4.25.4 Method of Test

27.22.4.25.4.1 Initial conditions

The ME is connected to the USIM Simulator.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

27.22.4.25.4.2 Procedure

Expected Sequence 1.1 (LANGUAGE NOTIFICATION)

See ETSI TS 102 384 [26] in clause 27.22.4.25.4.2, Expected Sequence 1.1.

Expected Sequence 1.2 (LANGUAGE NOTIFICATION)

See ETSI TS 102 384 [26] in clause 27.22.4.25.4.2, Expected Sequence 1.2.

27.22.4.25.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1 and 1.2.

27.22.4.26 LAUNCH BROWSER

27.22.4.26.1 LAUNCH BROWSER (No session already launched)

27.22.4.26.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.26.1.2 Conformance requirements

The ME shall support the LAUNCH BROWSER Proactive UICC Command as defined in:

– TS 31.111 [15] clause 5.2, clauses 6.4.26 and 6.6.26, clause 8.6, clause 8.7, clause 8.48, clause 9.2, clause 8.2, clause 8.47, clause 8.49, clause 8.50, clause 8.15 and clause 8.31.

27.22.4.26.1.3 Test purpose

To verify that when the ME is in idle state, it launches properly the browser session required in LAUNCH BROWSER, and returns a successful result in the TERMINAL RESPONSE command.

27.22.4.26.1.4 Method of test

27.22.4.26.1.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

A valid access to 2 different Wap gateways is required:

– the default browser parameters (IP address, gateway/proxy identity, called number, URL …) of the tested mobile shall be properly filled to access one of the gateways ("default gateway")

With that default gateway we shall be able to access to an URL different from the default one.

– another gateway with an IP address different from the one defined in default browser parameters.

The mobile is in idle mode. To ensure that there are no active PDP contexts established until the proactive command is fetched, the USS shall be configured to ignore any PDP context activation request before the LAUNCH BROWSER command is fetched.

For URL requests resulting from the LAUNCH BROWSER command execution the USS shall be configured to respond with an HTTP status error code (4xx "Client Error" or 5xx "Server Error") to URL requests which do not match the Default URL or the URL provided in the proactive command. At the same time the USS shall ignore these URL requests regarding the test case verdict generation.

Bearer Parameters

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

GPRS Parameters

Network access name: TestGp.rs

User login: UserLog

User password: UserPwd

UICC/ME interface transport level

Transport format: UDP

Port number: 44444

Data destination address 01.01.01.01 (as an example)

Note: If a data destination address different to 01.01.01.01 is used then the network simulator setup and related UE settings might require a corresponding adaptation.

27.22.4.26.1.4.2 Procedure

Expected Sequence 1.1 (LAUNCH BROWSER, connect to the default URL)

Step	Direction	MESSAGE / Action	Comments
0	ME		[The ME is in idle mode and the browser’s cache shall have been cleared. The ME supports Launch Browser with Default URL]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 1.1.1	[connect to the default URL, "launch browser, if not already launched", no null alpha id.]
4	ME → USER	ME displays the alpha identifier
5	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 1.1.1	[Command performed successfully]
7	MEUSS	If command was performed successfully, the ME attempts to launch the session with the default browser parameters and the default URL.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the browser session to defined URL is properly established.

PROACTIVE COMMAND: LAUNCH BROWSER 1.1.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL empty

Alpha Identifier "Default URL"

Coding:

BER-TLV:	D0	18	81	03	01	15	00	82	02	81	82	31
	00	05	0B	44	65	66	61	75	6C	74	20	55
	52	4C

TERMINAL RESPONSE: LAUNCH BROWSER 1.1.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 1.2 (LAUNCH BROWSER, connect to the specified URL, alpha identifier length=0)

Step	Direction	MESSAGE / Action	Comments
0	ME		[The ME is in idle mode and the browser’s cache shall have been cleared.]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 1.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 1.2.1	[connect to defined URL, "launch browser, if not already launched, alpha identifier length=0]
4	ME → USER	No information should be displayed.
5	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 1.2.1	[Command performed successfully]
7	MEUSS	The ME attempts to connect the URL specified in the LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the URL is properly connected.

PROACTIVE COMMAND: LAUNCH BROWSER 1.2.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier empty

Coding:

BER-TLV:	D0	1F	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	00

TERMINAL RESPONSE: LAUNCH BROWSER 1.2.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 1.3 (LAUNCH BROWSER, Browser identity, no alpha identifier)

Step	Direction	MESSAGE / Action	Comments
0	ME		[The ME is in idle mode and the browser’s cache shall have been cleared.]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 1.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 1.3.1	[connect to the defined URL, "launch browser, if not already launched, browser identity]
4	ME → USER	ME may display a default message of its own.
5	USER → ME	The user may confirm the launch browser.	[option: user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 1.3.1	[Command performed successfully]
7	MEUSS	The ME attempts to connect the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the default browser session is properly established.

PROACTIVE COMMAND: LAUNCH BROWSER 1.3.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

Browser Identity default

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Coding::

BER-TLV:	D0	20	81	03	01	15	00	82	02	81	82	30
	01	00	31	12	68	74	74	70	3A	2F	2F	78
	78	78	2E	79	79	79	2E	7A	7A	7A

TERMINAL RESPONSE: LAUNCH BROWSER 1.3.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 1.4 (LAUNCH BROWSER, only GPRS bearer specified and gateway/proxy identity, GPRS supported by USS)

Step	Direction	MESSAGE / Action	Comments
0	ME		[The ME is in idle mode, GPRS supported by USS, GPRS supported by the ME and activated, the terminal might need to be configured with an entry linking the Gateway/Proxy Identity in the proactive command with the corresponding connectivity parameters in the mobile. The browser’s cache shall have been cleared.]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 1.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 1.4.1	[connect to the defined URL, "launch browser, if not already launched, 1 bearer specified, gateway/proxy id specified]
4	ME → USER	ME may display a default message
5	USER → ME	The user may confirm the launch browser.	[option: user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 1.4.1	[Command performed successfully]
7	MEUSS	The ME attempts to connect the URL specified in LAUNCH BROWSER command using the requested bearer and proxy identity	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the browser session is properly established with the required bearer.

PROACTIVE COMMAND: LAUNCH BROWSER 1.4.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Bearer GPRS

Gateway/Proxy id

DCSunpacked, 8 bits data

Text string abc.def.ghi.jkl (different from the default IP address)

Coding::

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	32	01	03	0D	10
	04	61	62	63	2E	64	65	66	2E	67	68	69
	2E	6A	6B	6C

TERMINAL RESPONSE: LAUNCH BROWSER 1.4.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 1.5 Void

Expected Sequence 1.6 (LAUNCH BROWSER, ME does not support Launch Browser with Default URL)

Step	Direction	MESSAGE / Action	Comments
0	ME		[The ME is in idle mode and the browser’s cache shall have been cleared. The ME does not support Launch Browser with Default URL]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 1.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 1.1.1	[connect to the default URL, "launch browser, if not already launched", no null alpha id.]
4	ME → USER	The ME may display the alpha identifier
5	USER → ME	If the ME displays the alpha identifier then the user confirms the launch browser.	[option: user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 1.6.1 )	[ME unable to process command – Default URL unavailable]
7	UICC → ME	PROACTIVE UICC SESSION ENDED

TERMINAL RESPONSE: LAUNCH BROWSER 1.6.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Launch browser generic error code

Additional data Default URL unavailable

Coding:

BER-TLV:	81	03	01	15	00	82	02	82	81	83	02	26
	04

27.22.4.26.1.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 1.1 to 1.6..

27.22.4.26.2 LAUNCH BROWSER (Interaction with current session)

27.22.4.26.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.26.2.2 Conformance requirements

The ME shall support the LAUNCH BROWSER Proactive UICC Command as defined in:

– TS 31.111 [15] clause 5.2, clauses 6.4.26 and 6.6.26, clause 8.6, clause 8.7, clause 8.48, clause 9.2, clause 82.2, clause 8.47, optional clause 8.49, optional clause 8.50, clause 8.15 and clause 8.31.

27.22.4.26.2.3 Test purpose

To verify that when the ME is already busy in a browser session, it launches properly the browser session required in LAUNCH BROWSER, and returns a successful result in the TERMINAL RESPONSE.

27.22.4.26.2.4 Method of test

27.22.4.26.2.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

A valid access to a Wap gateway is required. The default browser parameters (IP address, gateway/proxy identity, called number…) of the tested mobile shall be properly filled to access that gateway.

The mobile is busy in a browser session, the user navigates in pages different from the URL defined in the test sequence.

The Bearer Parameters defined in 27.22.4.26.1.4.1 shall be used.

27.22.4.26.2.4.2 Procedure

Expected Sequence 2.1 (LAUNCH BROWSER, use the existing browser, connect to the specified URL)

Step	Direction	MESSAGE / Action	Comments
0	ME	The user is navigating in a browser session (not theURL defined in the test sequence).	[Browser is in use, the current session is not secured]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 2.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 2.1.1	[connect to the defined URL, "use the existing browser", no null alpha id.]
4	ME → USER	ME displays the alpha identifier
5	USER → ME	The user confirms the launch browser.	[user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 2.1.1	[Command performed successfully]
7	MEUSS	The ME does not close the existing session and attempts to connect the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause] Usage of a new active tab in the browser is a valid behaviour (see note)
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the URL specified in LAUNCH BROWSER command is connected; and the previous URL can be retrieved.
NOTE: Active tab indicates that web page is visible to the user.

PROACTIVE COMMAND: LAUNCH BROWSER 2.1.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: use the existing browser

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL"

Coding:

BER-TLV:	D0	2A	81	03	01	15	02	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0B	44	65	66
	69	6E	65	64	20	55	52	4C

TERMINAL RESPONSE: LAUNCH BROWSER 2.1.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: use the existing browser

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 2.2 (LAUNCH BROWSER, close the existing browser session and launch new browser session, connect to the specified URL)

Step	Direction	MESSAGE / Action	Comments
0	ME	The user is navigating in a browser session (not the URL defined in the test sequence).	[Browser is in use, the current session is not secured]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 2.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 2.2.1	[connect to the defined URL, "close the existing browser session and launch new browser session", no null alpha id.]
4	ME → USER	ME displays the alpha identifier
5	USER → ME	The user confirms the launch browser.	[user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 2.2.1	[Command performed successfully]
7	MEUSS	The ME closes the existing session and attempts to launch the session with the default browser parameters and the URL specified in LAUNCH BROWSER command. IF A.1/155_THEN it is a valid behaviour to keep other sessions/tabs open and start the session in a new active tab (see note).	[The UE has the option of maintaining the currently active PDP Context. The USS shall handle the request of additional URLs as defined in the initial conditions clause.]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the URL specified in LAUNCH BROWSER command is connected.
NOTE: Active tab indicates that web page is visible to the user.

PROACTIVE COMMAND: LAUNCH BROWSER 2.2.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: close the existing browser session and launch new browser session

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL"

Coding:

BER-TLV:	D0	2A	81	03	01	15	03	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0B	44	65	66
	69	6E	65	64	20	55	52	4C

TERMINAL RESPONSE: LAUNCH BROWSER 2.2.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: close the existing browser session and launch new browser session

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 2.3 (LAUNCH BROWSER, if not already launched)

Step	Direction	MESSAGE / Action	Comments
0	ME	The user is navigating in a browser session (not the URL defined in the test sequence).	[Browser is in use, the current session is not secured]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 2.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 2.3.1	[connect to the defined URL, "launch browser, if not already launched]
4	ME → UICC	IF (NOT A.1/155)_THEN TERMINAL RESPONSE: LAUNCH BROWSER 2.3.1 ELSE IF (A.1/155) THEN TERMINAL RESPONSE:LAUNCH BROWSER 2.3.2	[ME unable to process command – browser unavailable] If browser supports multiple sessions/tabs, it is valid behaviour to open the session in a new active tab that does not interfere with other sessions (see note).
5	UICC → ME	PROACTIVE UICC SESSION ENDED
6	USER → ME	IF (NOT A.1/155)_THEN the user verifies that the URL specified in LAUNCH BROWSER command has not been connected.
NOTE: Active tab indicates that web page is visible to the user.

PROACTIVE COMMAND: LAUNCH BROWSER 2.3.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Coding:

BER-TLV:	D0	1D	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A

TERMINAL RESPONSE: LAUNCH BROWSER 2.3.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Launch browser generic error code

Additional data Browser unavailable

Coding:

BER-TLV:	81	03	01	15	00	82	02	82	81	83	02	26
	02

TERMINAL RESPONSE: LAUNCH BROWSER 2.3.2

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.26.2.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 2.1 to 2.3.

27.22.4.26.3 LAUNCH BROWSER (UCS2 display in Cyrillic)

27.22.4.26.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.26.3.2 Conformance requirements

The ME shall support the LAUNCH BROWSER Proactive UICC Command as defined in:

– TS 31.111 [15] clause 5.2, clauses 6.4.26 and 6.6.26, clause 8.6, clause 8.7, clause 8.48, clause 9.2, clause 8.2, clause 8.47, optional clause 8.49, optional clause 8.50, clause 8.15 and clause 8.31.

Additionally the ME shall support the UCS2 facility for the coding of the Cyrillic alphabet, as defined in:

– ISO/IEC 10646 [17].

27.22.4.26.3.3 Test purpose

To verify that the ME performs a proper user confirmation with an USC2 alpha identifier, launches the Wap session required in LAUNCH BROWSER and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.26.3.4 Method of test

27.22.4.26.3.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

A valid access to 2 different Wap gateways is required:

– the default browser parameters (IP address, gateway/proxy identity, called number, URL …) of the tested mobile shall be properly filled to access one of the gateways ("default gateway").

With that default gateway we shall be able to access to an URL different from the default one.

– another gateway with an IP address different from the one defined in default browser parameters.

The mobile is busy in a browser session, the user navigates in pages different from the URL defined by default in Wap parameters.

The browser’s cache shall have been cleared before execution of each sequence.

The Bearer Parameters defined in 27.22.4.26.1.4.1 shall be used.

27.22.4.26.3.4.2 Procedure

Expected Sequence 3.1 (LAUNCH BROWSER, use the existing browser, connect to the specified URL, UCS2 in Cyrillic)

Step	Direction	MESSAGE / Action	Comments
0	ME	The user is navigating in a browser session (not the URL defined in the test sequence).	[Browser is in use, the current session is not secured]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 3.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 3.1.1	[connect to the defined URL, "use the existing browser", alpha id. In UCS2]
4	ME → USER	ME displays the alpha identifier "ЗДРАВСТВУЙТЕ"	["Hello" in Russian]
5	USER → ME	The user confirms the launch browser.	[user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 3.1.1	[Command performed successfully]
7	MEUSS	The ME does not close the existing session and attempts to connect the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the URL is connected; and the previous URL can be retrieved.

PROACTIVE COMMAND: LAUNCH BROWSER 3.1.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: use the existing browser

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier

Data coding scheme: UCS2 (16 bits)

Text: "ЗДРАВСТВУЙТЕ"

Coding:

BER-TLV:	D0	38	81	03	01	15	02	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	19	80	04	17
	04	14	04	20	04	10	04	12	04	21	04	22
	04	12	04	23	04	19	04	22	04	15

TERMINAL RESPONSE: LAUNCH BROWSER 3.1.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: use the existing browser

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.26.3.5 Test Requirement

The ME shall operate in the manner defined in expected sequence 3.1.

27.22.4.26.4 LAUNCH BROWSER (icons support)

27.22.4.26.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.26.4.2 Conformance requirements

The ME shall support the LAUNCH BROWSER Proactive UICC Command as defined in:

27.22.4.26.4.3 Test purpose

To verify that the ME performs a proper user confirmation with an icon identifier, launches the browser session required in LAUNCH BROWSER and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.26.4.4 Method of test

27.22.4.26.4.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

A valid access to 2 different Wap gateways is required:

– the default browser parameters (IP address, gateway/proxy identity, called number, URL …) of the tested mobile shall be properly filled to access one of the gateways ("default gateway").

With that default gateway we shall be able to access to an URL different from the default one.

– another gateway with an IP address different from the one defined in default browser parameters.

The mobile is busy in a browser session, the user navigates in pages different from the URL defined by default in browser parameters.

The Bearer Parameters defined in 27.22.4.26.1.4.1 shall be used.

27.22.4.26.4.4.2 Procedure

Expected Sequence 4.1A (LAUNCH BROWSER, use the existing browser, icon not self explanatory, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 4.1.1	[Browser is in use, the current session is not secured]
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 4.1.1	[connect to the defined URL, "use the existing browser", no null alpha id.]
4	ME → USER	ME displays the alpha identifier and the icon	["Not self explan."]
5	USER → ME	The user confirms the launch browser.	[user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 4.1.1 A	[Command performed successfully]
7	MEUSS	The ME does not close the existing session and attempts to connect the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the URL specified in LAUNCH BROWSER command is connected; and the previous URL can be retrieved.

PROACTIVE COMMAND: LAUNCH BROWSER 4.1.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: use the existing browser

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Not self explan."

Icon identifier:

Icon qualifier: not self-explanatory

Icon identifier: record 1 in EF_(IMG)

Coding:

BER-TLV:	D0	33	81	03	01	15	02	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	10	4E	6F	74
	20	73	65	6C	66	20	65	78	70	6C	61	6E
	2E	1E	02	01	01

TERMINAL RESPONSE: LAUNCH BROWSER 4.1.1 A

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: use the existing browser

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 4.1B (LAUNCH BROWSER, use the existing browser, icon not self explanatory, requested icon could not be displayed)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 4.1.1	[Browser is in use, the current session is not secured]
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 4.1.1	[connect to the defined URL, "use the existing browser", no null alpha id.]
4	ME → USER	ME displays the alpha identifier Without the icon	["Not self explan."]
5	USER → ME	The user confirms the launch browser.	[user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 4.1.1 B	[Command performed successfully but requested icon could not be displayed]
7	MEUSS	The ME does not close the existing session and attempts to connect the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the URL specified in LAUNCH BROWSER command is connected; and the previous URL can be retrieved.

TERMINAL RESPONSE: LAUNCH BROWSER 4.1.1 B

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: use the existing browser

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully but requested icon could not be displayed

Coding:

BER-TLV:

Expected Sequence 4.2A (LAUNCH BROWSER, use the existing browser, icon self explanatory, successful)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 4.2.1	[Browser is in use, the current session is not secured]
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 4.2.1	[connect to the defined URL, "use the existing browser", alpha id. In UCS2]
4	ME → USER	ME displays only the icon	["Self explan."]
5	USER → ME	The user confirms the launch browser.	[user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 4.2.1 A	[Command performed successfully]
7	MEUSS	The ME does not close the existing session and attempts to connect the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the URL specified in LAUNCH BROWSER command is connected; and the previous URL can be retrieved.

PROACTIVE COMMAND: LAUNCH BROWSER 4.2.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: use the existing browser

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Self explan."

Icon identifier:

Icon qualifier: self-explanatory

Icon identifier: record 1 in EF_(IMG)

Coding:

BER-TLV:	D0	2F	81	03	01	15	02	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0C	53	65	6C
	66	20	65	78	70	6C	61	6E	2E	1E	02	00
	01

TERMINAL RESPONSE: LAUNCH BROWSER 4.2.1 A

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: use the existing browser

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 4.2B (LAUNCH BROWSER, use the existing browser, icon self explanatory, requested icon could not be displayed)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 4.2.1	[Browser is in use, the current session is not secured]
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 4.2.1	[connect to the defined URL, "use the existing browser", alpha id. In UCS2]
4	ME → USER	ME displays only the alpha identifier	["Self explan."]
5	USER → ME	The user confirms the launch browser.	[user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 4.2.1 B	[Command performed successfully] [Command performed successfully but requested icon could not be displayed]
7	MEUSS	The ME does not close the existing session and attempts to connect the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the URL specified in LAUNCH BROWSER command is connected; and the previous URL can be retrieved.

TERMINAL RESPONSE: LAUNCH BROWSER 4.2.1 B

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: use the existing browser

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully but requested icon could not be displayed

Coding:

BER-TLV:

27.22.4.26.3.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 4.1A to 4.2B.

27.22.4.26.5 LAUNCH BROWSER (support of Text Attribute)

27.22.4.26.5.1 LAUNCH BROWSER (support of Text Attribute – Left Alignment)

27.22.4.26.5.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.26.5.1.2 Conformance requirements

The ME shall support the LAUNCH BROWSER Proactive UICC Command as defined in:

– TS 31.111[15] clause 5.2, clauses 6.4.26 and 6.6.26, clause 8.6, clause 8.7, clause 8.48, clause 9.2, clause 8.2, clause 8.47, clause 8.49, clause 8.50, clause 8.15, clause 8.31 and clause 8.70.

27.22.4.26.5.1.3 Test purpose

To verify that the ME performs a proper user confirmation with an alpha identifier according to the left alignment text attribute configuration, launches the Wap session required in LAUNCH BROWSER and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.26.5.1.4 Method of test

27.22.4.26.5.1.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

A valid access to 2 different Wap gateways is required:

– the default Wap parameters (IP address, gateway/proxy identity, called number, URL …) of the tested mobile shall be properly filled to access one of the gateways ("default gateway")

With that default gateway we shall be able to access to an URL different from the default one.

– another gateway with an IP address different from the one defined in default Wap parameters.

The Bearer Parameters defined in 27.22.4.26.1.4.1 shall be used.

The ME is in idle mode. To ensure that there are no active PDP contexts established until the proactive command is fetched, the USS shall be configured to ignore any PDP context activation request before the LAUNCH BROWSER command is fetched.

27.22.4.26.5.1.4.2 Procedure

Expected Sequence 5.1 (LAUNCH BROWSER, connect to the specified URL with Text Attribute – Left Alignment)

Step	Direction	MESSAGE / Action	Comments
0	ME		[The ME is in idle mode and the browser’s cache shall have been cleared.]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.1.1	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
4	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with left alignment]
5	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.1.1	[Command performed successfully]
7	MEUSS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
10	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.1.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.1.2	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
13	ME → USER	ME displays the alpha identifier	[Message shall be formatted without left alignment. Remark: If left alignment is the ME’s default alignment as declared in table A.2/18, no alignment change will take place]
14	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
15	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.1.1	[Command performed successfully]
16	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
17	UICC → ME	PROACTIVE UICC SESSION ENDED
18	USER → ME	The user verifies that the default Wap session is properly established.

PROACTIVE COMMAND: LAUNCH BROWSER 5.1.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 1"

Text Attribute

Formatting position: 0

Formatting length: 13

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	31	D0	04
	00	0D	00	B4

PROACTIVE COMMAND: LAUNCH BROWSER 5.1.2

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 2"

Coding:

BER-TLV:	D0	2C	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	32

TERMINAL RESPONSE: LAUNCH BROWSER 5.1.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.26.5.1.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 5.1.

27.22.4.26.5.2 LAUNCH BROWSER (support of Text Attribute – Center Alignment)

27.22.4.26.5.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.26.5.2.2 Conformance requirements

The ME shall support the LAUNCH BROWSER Proactive UICC Command as defined in:

– TS 31.111 [15] clause 5.2, clauses 6.4.26 and 6.6.26, clause 8.6, clause 8.7, clause 8.48, clause 9.2, clause 8.2, clause 8.47, clause 8.49, clause 8.50, clause 8.15, clause 8.31 and clause 8.70.

27.22.4.26.5.2.3 Test purpose

To verify that the ME performs a proper user confirmation with an alpha identifier according to the center alignment text attribute configuration, launches the Wap session required in LAUNCH BROWSER and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.26.5.2.4 Method of test

27.22.4.26.5.2.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

A valid access to 2 different Wap gateways is required:

– the default Wap parameters (IP address, gateway/proxy identity, called number, URL …) of the tested mobile shall be properly filled to access one of the gateways ("default gateway")

With that default gateway we shall be able to access to an URL different from the default one.

– another gateway with an IP address different from the one defined in default Wap parameters.

The Bearer Parameters defined in 27.22.4.26.1.4.1 shall be used.

27.22.4.26.5.2.4.2 Procedure

Expected Sequence 5.2 (LAUNCH BROWSER, connect to the default URL with Text Attribute – Center Alignment)

Step	Direction	MESSAGE / Action	Comments
0	ME		[The ME is in idle mode and the browser’s cache shall have been cleared.]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.2.1	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
4	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with center alignment]
5	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.2.1	[Command performed successfully]
7	MEUSS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
10	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.2.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.2.2	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
13	ME → USER	ME displays the alpha identifier	[Message shall be formatted without center alignment. Remark: If center alignment is the ME’s default alignment as declared in table A.2/18, no alignment change will take place]
14	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
15	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.2.1	[Command performed successfully]
16	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
17	UICC → ME	PROACTIVE UICC SESSION ENDED
18	USER → ME	The user verifies that the default Wap session is properly established.

PROACTIVE COMMAND: LAUNCH BROWSER 5.2.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 1"

Text Attribute

Formatting position: 0

Formatting length: 13

Formatting mode: Center Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	31	D0	04
	00	0D	01	B4

PROACTIVE COMMAND: LAUNCH BROWSER 5.2.2

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 2"

Coding:

BER-TLV:	D0	2C	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	32

TERMINAL RESPONSE: LAUNCH BROWSER 5.2.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.26.5.2.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 5.2.

27.22.4.26.5.3 LAUNCH BROWSER (support of Text Attribute – Right Alignment)

27.22.4.26.5.3.1 Definition and applicability

See clause 3.2.2.

27.22.4.26.5.3.2 Conformance requirements

The ME shall support the LAUNCH BROWSER Proactive UICC Command as defined in:

– TS 31.111 [15] clause 5.2, clauses 6.4.26 and 6.6.26, clause 8.6, clause 8.7, clause 8.48, clause 9.2, clause 8.2, clause 8.47, clause 8.49, clause 8.50, clause 8.15, clause 8.31 and clause 8.70.

27.22.4.26.5.3.3 Test purpose

To verify that the ME performs a proper user confirmation with an alpha identifier according to the right alignment text attribute configuration, launches the Wap session required in LAUNCH BROWSER and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.26.5.3.4 Method of test

27.22.4.26.5.3.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

A valid access to 2 different Wap gateways is required:

– the default Wap parameters (IP address, gateway/proxy identity, called number, URL …) of the tested mobile shall be properly filled to access one of the gateways ("default gateway")

With that default gateway we shall be able to access to an URL different from the default one.

– another gateway with an IP address different from the one defined in default Wap parameters.

The Bearer Parameters defined in 27.22.4.26.1.4.1 shall be used.

Before execution of each sequence the browser’s cache shall be cleared.

27.22.4.26.5.3.4.2 Procedure

Expected Sequence 5.3 (LAUNCH BROWSER, connect to the specified URL with Text Attribute – Right Alignment)

Step	Direction	MESSAGE / Action	Comments
0	ME		[The ME is in idle mode and the browser’s cache shall have been cleared.]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.3.1	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
4	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with right alignment]
5	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.3.1	[Command performed successfully]
7	MEUSS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
10	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.3.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.3.2	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
13	ME → USER	ME displays the alpha identifier	[Message shall be formatted without right alignment. Remark: If right alignment is the ME’s default alignment as declared in table A.2/18, no alignment change will take place]
14	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
15	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.3.1	[Command performed successfully]
16	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
17	UICC → ME	PROACTIVE UICC SESSION ENDED
18	USER → ME	The user verifies that the default Wap session is properly established.

PROACTIVE COMMAND: LAUNCH BROWSER 5.3.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 1"

Text Attribute

Formatting position: 0

Formatting length: 13

Formatting mode: Right Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	31	D0	04
	00	0D	02	B4

PROACTIVE COMMAND: LAUNCH BROWSER 5.3.2

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 2"

Coding:

BER-TLV:	D0	2C	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	32

TERMINAL RESPONSE: LAUNCH BROWSER 5.3.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.26.5.3.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 5.3.

27.22.4.26.5.4 LAUNCH BROWSER (support of Text Attribute – Large Font Size)

27.22.4.26.5.4.1 Definition and applicability

See clause 3.2.2.

27.22.4.26.5.4.2 Conformance requirements

The ME shall support the LAUNCH BROWSER Proactive UICC Command as defined in:

– TS 31.111 [15] clause 5.2, clauses 6.4.26 and 6.6.26, clause 8.6, clause 8.7, clause 8.48, clause 9.2, clause 8.2, clause 8.47, clause 8.49, clause 8.50, clause 8.15, clause 8.31 and clause 8.70.

27.22.4.26.5.4.3 Test purpose

To verify that the ME performs a proper user confirmation with an alpha identifier according to the large font size text attribute configuration, launches the Wap session required in LAUNCH BROWSER and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.26.5.4.4 Method of test

27.22.4.26.5.4.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

A valid access to 2 different Wap gateways is required:

– the default Wap parameters (IP address, gateway/proxy identity, called number, URL …) of the tested mobile shall be properly filled to access one of the gateways ("default gateway")

With that default gateway we shall be able to access to an URL different from the default one.

– another gateway with an IP address different from the one defined in default Wap parameters.

The Bearer Parameters defined in 27.22.4.26.1.4.1 shall be used.

Before execution of each sequence the browser’s cache shall be cleared.

27.22.4.26.5.4.4.2 Procedure

Expected Sequence 5.4 (LAUNCH BROWSER, connect to the specified URL with Text Attribute – Large Font Size)

Step	Direction	MESSAGE / Action	Comments
0	ME		[The ME is in idle mode and the browser’s cache shall have been cleared.]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.4.1	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
4	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with large font size]
5	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.4.1	[Command performed successfully]
7	MEUSS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
10	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.4.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.4.2	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
13	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with normal font size]
14	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
15	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.4.1	[Command performed successfully]
16	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
17	UICC → ME	PROACTIVE UICC SESSION ENDED
18	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
19	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.4.1
20	ME → UICC	FETCH
21	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.4.1	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
22	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with large font size]
23	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
24	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.4.1	[Command performed successfully]
25	MEUSS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
26	UICC → ME	PROACTIVE UICC SESSION ENDED
27	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
28	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.4.3
29	ME → UICC	FETCH
30	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.4.3	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
31	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with normal font size]
32	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
33	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.4.1	[Command performed successfully]
34	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
35	UICC → ME	PROACTIVE UICC SESSION ENDED
36	USER → ME	The user verifies that the default Wap session is properly established.

PROACTIVE COMMAND: LAUNCH BROWSER 5.4.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 1"

Text Attribute

Formatting position: 0

Formatting length: 13

Formatting mode: Left Alignment, Large Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	31	D0	04
	00	0D	04	B4

PROACTIVE COMMAND: LAUNCH BROWSER 5.4.2

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 2"

Text Attribute

Formatting position: 0

Formatting length: 13

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	32	D0	04
	00	0D	00	B4

PROACTIVE COMMAND: LAUNCH BROWSER 5.4.3

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 3"

Coding:

BER-TLV:	D0	2C	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	33

TERMINAL RESPONSE: LAUNCH BROWSER 5.4.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.26.5.4.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 5.4.

27.22.4.26.5.5 LAUNCH BROWSER (support of Text Attribute – Small Font Size)

27.22.4.26.5.5.1 Definition and applicability

See clause 3.2.2.

27.22.4.26.5.5.2 Conformance requirements

The ME shall support the LAUNCH BROWSER Proactive UICC Command as defined in:

– TS 31.111 [15] clause 5.2, clauses 6.4.26 and 6.6.26, clause 8.6, clause 8.7, clause 8.48, clause 9.2, clause 8.2, clause 8.47, clause 8.49, clause 8.50, clause 8.15, clause 8.31 and clause 8.70.

27.22.4.26.5.5.3 Test purpose

To verify that the ME performs a proper user confirmation with an alpha identifier according to the small font size text attribute configuration, launches the Wap session required in LAUNCH BROWSER and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.26.5.5.4 Method of test

27.22.4.26.5.5.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

A valid access to 2 different Wap gateways is required:

– the default Wap parameters (IP address, gateway/proxy identity, called number, URL …) of the tested mobile shall be properly filled to access one of the gateways ("default gateway")

With that default gateway we shall be able to access to an URL different from the default one.

– another gateway with an IP address different from the one defined in default Wap parameters.

The Bearer Parameters defined in 27.22.4.26.1.4.1 shall be used.

27.22.4.26.5.5.4.2 Procedure

Expected Sequence 5.5 (LAUNCH BROWSER, connect to the specified URL with Text Attribute – Small Font Size)

Step	Direction	MESSAGE / Action	Comments
0	ME		[The ME is in idle mode and the browser’s cache shall have been cleared.]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.5.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.5.1	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
4	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with small font size]
5	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.5.1	[Command performed successfully]
7	MEUSS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
10	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.5.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.5.2	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
13	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with normal font size]
14	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
15	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.5.1	[Command performed successfully]
16	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
17	UICC → ME	PROACTIVE UICC SESSION ENDED
18	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
19	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.5.1
20	ME → UICC	FETCH
21	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.5.1	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
22	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with small font size]
23	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
24	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.5.1	[Command performed successfully]
25	MEUSS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
26	UICC → ME	PROACTIVE UICC SESSION ENDED
27	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
28	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.5.3
29	ME → UICC	FETCH
30	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.5.3	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
31	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with normal font size]
32	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
33	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.5.1	[Command performed successfully]
34	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
35	UICC → ME	PROACTIVE UICC SESSION ENDED
36	USER → ME	The user verifies that the default Wap session is properly established.

PROACTIVE COMMAND: LAUNCH BROWSER 5.5.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 1"

Text Attribute

Formatting position: 0

Formatting length: 13

Formatting mode: Left Alignment, Small Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	31	D0	04
	00	0D	08	B4

PROACTIVE COMMAND: LAUNCH BROWSER 5.5.2

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 2"

Text Attribute

Formatting position: 0

Formatting length: 13

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	32	D0	04
	00	0D	00	B4

PROACTIVE COMMAND: LAUNCH BROWSER 5.5.3

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 3"

Coding:

BER-TLV:	D0	2C	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	33

TERMINAL RESPONSE: LAUNCH BROWSER 5.5.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.26.5.5.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 5.5.

27.22.4.26.5.6 LAUNCH BROWSER (support of Text Attribute – Bold on)

27.22.4.26.5.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.26.5.6.2 Conformance requirements

The ME shall support the LAUNCH BROWSER Proactive UICC Command as defined in:

– TS 31.111 [15] clause 5.2, clauses 6.4.26 and 6.6.26, clause 8.6, clause 8.7, clause 8.48, clause 9.2, clause 8.2, clause 8.47, clause 8.49, clause 8.50, clause 8.15, clause 8.31 and clause 8.70.

27.22.4.26.5.6.3 Test purpose

To verify that the ME performs a proper user confirmation with an alpha identifier according to the bold text attribute configuration, launches the Wap session required in LAUNCH BROWSER and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.26.5.6.4 Method of test

27.22.4.26.5.6.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

A valid access to 2 different Wap gateways is required:

– the default Wap parameters (IP address, gateway/proxy identity, called number, URL …) of the tested mobile shall be properly filled to access one of the gateways ("default gateway")

With that default gateway we shall be able to access to an URL different from the default one.

– another gateway with an IP address different from the one defined in default Wap parameters.

The Bearer Parameters defined in 27.22.4.26.1.4.1 shall be used.

27.22.4.26.5.6.4.2 Procedure

Expected Sequence 5.6 (LAUNCH BROWSER, connect to the specified URL with Text Attribute – Bold On)

Step	Direction	MESSAGE / Action	Comments
0	ME		[The ME is in idle mode and the browser’s cache shall have been cleared.]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.6.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.6.1	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
4	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with bold on]
5	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.6.1	[Command performed successfully]
7	MEUSS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
10	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.6.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.6.2	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
13	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with bold off]
14	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
15	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.6.1	[Command performed successfully]
16	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
17	UICC → ME	PROACTIVE UICC SESSION ENDED
18	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
19	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.6.1
20	ME → UICC	FETCH
21	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.6.1	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
22	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with bold on]
23	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
24	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.6.1	[Command performed successfully]
25	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
26	UICC → ME	PROACTIVE UICC SESSION ENDED
27	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
28	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.6.3
29	ME → UICC	FETCH
30	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.6.3	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
31	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with bold off]
32	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
33	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.6.1	[Command performed successfully]
34	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
35	UICC → ME	PROACTIVE UICC SESSION ENDED
36	USER → ME	The user verifies that the default Wap session is properly established.

PROACTIVE COMMAND: LAUNCH BROWSER 5.6.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 1"

Text Attribute

Formatting position: 0

Formatting length: 13

Formatting mode: Left Alignment, Normal Font, Bold On, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	31	D0	04
	00	0D	10	B4

PROACTIVE COMMAND: LAUNCH BROWSER 5.6.2

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 2"

Text Attribute

Formatting position: 0

Formatting length: 13

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	32	D0	04
	00	0D	00	B4

PROACTIVE COMMAND: LAUNCH BROWSER 5.6.3

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 3"

Coding:

BER-TLV:	D0	2C	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	33

TERMINAL RESPONSE: LAUNCH BROWSER 5.6.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.26.5.6.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 5.6.

27.22.4.26.5.7 LAUNCH BROWSER (support of Text Attribute – Italic On)

27.22.4.26.5.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.26.5.7.2 Conformance requirements

The ME shall support the LAUNCH BROWSER Proactive UICC Command as defined in:

– TS 31.111 [15] clause 5.2, clauses 6.4.26 and 6.6.26, clause 8.6, clause 8.7, clause 8.48, clause 9.2, clause 8.2, clause 8.47, clause 8.49, clause 8.50, clause 8.15, clause 8.31 and clause 8.70.

27.22.4.26.5.7.3 Test purpose

To verify that the ME performs a proper user confirmation with an alpha identifier according to the italic text attribute configuration, launches the Wap session required in LAUNCH BROWSER and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.26.5.7.4 Method of test

27.22.4.26.5.7.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

A valid access to 2 different Wap gateways is required:

– the default Wap parameters (IP address, gateway/proxy identity, called number, URL …) of the tested mobile shall be properly filled to access one of the gateways ("default gateway")

With that default gateway we shall be able to access to an URL different from the default one.

– another gateway with an IP address different from the one defined in default Wap parameters.

The Bearer Parameters defined in 27.22.4.26.1.4.1 shall be used.

27.22.4.26.5.7.4.2 Procedure

Expected Sequence 5.7 (LAUNCH BROWSER, connect to the specified URL with Text Attribute – Italic On)

Step	Direction	MESSAGE / Action	Comments
0	ME		[The ME is in idle mode and the browser’s cache shall have been cleared.]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.7.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.7.1	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
4	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with italic on]
5	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.7.1	[Command performed successfully]
7	MEUSS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
10	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.7.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.7.2	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
13	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with italic off]
14	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
15	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.7.1	[Command performed successfully]
16	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
17	UICC → ME	PROACTIVE UICC SESSION ENDED
18	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
19	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.7.1
20	ME → UICC	FETCH
21	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.7.1	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
22	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with italic on]
23	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
24	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.7.1	[Command performed successfully]
25	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
26	UICC → ME	PROACTIVE UICC SESSION ENDED
27	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
28	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.7.3
29	ME → UICC	FETCH
30	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.7.3	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
31	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with italic off]
32	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
33	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.7.1	[Command performed successfully]
34	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
35	UICC → ME	PROACTIVE UICC SESSION ENDED
36	USER → ME	The user verifies that the default Wap session is properly established.

PROACTIVE COMMAND: LAUNCH BROWSER 5.7.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 1"

Text Attribute

Formatting position: 0

Formatting length: 13

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic On, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	31	D0	04
	00	0D	20	B4

PROACTIVE COMMAND: LAUNCH BROWSER 5.7.2

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 2"

Text Attribute

Formatting position: 0

Formatting length: 13

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	32	D0	04
	00	0D	00	B4

PROACTIVE COMMAND: LAUNCH BROWSER 5.7.3

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 3"

Coding:

BER-TLV:	D0	2C	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	33

TERMINAL RESPONSE: LAUNCH BROWSER 5.7.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.26.5.7.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 5.7.

27.22.4.26.5.8 LAUNCH BROWSER (support of Text Attribute – Underline On)

27.22.4.26.5.8.1 Definition and applicability

See clause 3.2.2.

27.22.4.26.5.8.2 Conformance requirements

The ME shall support the LAUNCH BROWSER Proactive UICC Command as defined in:

– TS 31.111 [15] clause 5.2, clauses 6.4.26 and 6.6.26, clause 8.6, clause 8.7, clause 8.48, clause 9.2, clause 8.2, clause 8.47, clause 8.49, clause 8.50, clause 8.15, clause 8.31 and clause 8.70.

27.22.4.26.5.8.3 Test purpose

To verify that the ME performs a proper user confirmation with an alpha identifier according to the underline text attribute configuration, launches the Wap session required in LAUNCH BROWSER and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.26.5.8.4 Method of test

27.22.4.26.5.8.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

A valid access to 2 different Wap gateways is required:

– the default Wap parameters (IP address, gateway/proxy identity, called number, URL …) of the tested mobile shall be properly filled to access one of the gateways ("default gateway")

With that default gateway we shall be able to access to an URL different from the default one.

– another gateway with an IP address different from the one defined in default Wap parameters.

The Bearer Parameters defined in 27.22.4.26.1.4.1 shall be used.

27.22.4.26.5.8.4.2 Procedure

Expected Sequence 5.8 (LAUNCH BROWSER, connect to the specified URL with Text Attribute – Underline On)

Step	Direction	MESSAGE / Action	Comments
0	ME		[The ME is in idle mode and the browser’s cache shall have been cleared.]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.8.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.8.1	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
4	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with underline on]
5	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.8.1	[Command performed successfully]
7	MEUSS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
10	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.8.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.8.2	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
13	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with underline off]
14	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
15	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.8.1	[Command performed successfully]
16	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
17	UICC → ME	PROACTIVE UICC SESSION ENDED
18	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
19	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.8.1
20	ME → UICC	FETCH
21	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.8.1	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
22	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with underline on]
23	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
24	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.8.1	[Command performed successfully]
25	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
26	UICC → ME	PROACTIVE UICC SESSION ENDED
27	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
28	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.8.3
29	ME → UICC	FETCH
30	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.8.3	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
31	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with underline off]
32	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
33	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.8.1	[Command performed successfully]
34	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
35	UICC → ME	PROACTIVE UICC SESSION ENDED
36	USER → ME	The user verifies that the default Wap session is properly established.

PROACTIVE COMMAND: LAUNCH BROWSER 5.8.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 1"

Text Attribute

Formatting position: 0

Formatting length: 13

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline On, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	31	D0	04
	00	0D	40	B4

PROACTIVE COMMAND: LAUNCH BROWSER 5.8.2

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 2"

Text Attribute

Formatting position: 0

Formatting length: 13

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	32	D0	04
	00	0D	00	B4

PROACTIVE COMMAND: LAUNCH BROWSER 5.8.3

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 3"

Coding:

BER-TLV:	D0	2C	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	33

TERMINAL RESPONSE: LAUNCH BROWSER 5.8.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.26.5.8.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 5.8.

27.22.4.26.5.9 LAUNCH BROWSER (support of Text Attribute – Strikethrough On)

27.22.4.26.5.9.1 Definition and applicability

See clause 3.2.2.

27.22.4.26.5.9.2 Conformance requirements

The ME shall support the LAUNCH BROWSER Proactive UICC Command as defined in:

– TS 31.111 [15] clause 5.2, clauses 6.4.26 and 6.6.26, clause 8.6, clause 8.7, clause 8.48, clause 9.2, clause 8.2, clause 8.47, clause 8.49, clause 8.50, clause 8.15, clause 8.31 and clause 8.70.

27.22.4.26.5.9.3 Test purpose

To verify that the ME performs a proper user confirmation with an alpha identifier according to the strikethrough text attribute configuration, launches the Wap session required in LAUNCH BROWSER and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.26.5.9.4 Method of test

27.22.4.26.5.9.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

A valid access to 2 different Wap gateways is required:

– the default Wap parameters (IP address, gateway/proxy identity, called number, URL …) of the tested mobile shall be properly filled to access one of the gateways ("default gateway")

With that default gateway we shall be able to access to an URL different from the default one.

– another gateway with an IP address different from the one defined in default Wap parameters.

The Bearer Parameters defined in 27.22.4.26.1.4.1 shall be used.

27.22.4.26.5.9.4.2 Procedure

Expected Sequence 5.9 (LAUNCH BROWSER, connect to the specified URL with Text Attribute – Strikethrough On)

Step	Direction	MESSAGE / Action	Comments
0	ME		[The ME is in idle mode and the browser’s cache shall have been cleared.]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.9.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.9.1	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
4	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with strikethrough on]
5	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.9.1	[Command performed successfully]
7	MEUSS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
10	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.9.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.9.2	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
13	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with strikethrough off]
14	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
15	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.9.1	[Command performed successfully]
16	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
17	UICC → ME	PROACTIVE UICC SESSION ENDED
18	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
19	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.9.1
20	ME → UICC	FETCH
21	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.9.1	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
22	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with strikethrough on]
23	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
24	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.9.1	[Command performed successfully]
25	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
26	UICC → ME	PROACTIVE UICC SESSION ENDED
27	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
28	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.9.3
29	ME → UICC	FETCH
30	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.9.3	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
31	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with strikethrough off]
32	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
33	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.9.1	[Command performed successfully]
34	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
35	UICC → ME	PROACTIVE UICC SESSION ENDED
36	USER → ME	The user verifies that the default Wap session is properly established.

PROACTIVE COMMAND: LAUNCH BROWSER 5.9.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 1"

Text Attribute

Formatting position: 0

Formatting length: 13

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough On

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	31	D0	04
	00	0D	80	B4

PROACTIVE COMMAND: LAUNCH BROWSER 5.9.2

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 2"

Text Attribute

Formatting position: 0

Formatting length: 13

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	32	D0	04
	00	0D	00	B4

PROACTIVE COMMAND: LAUNCH BROWSER 5.9.3

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 3"

Coding:

BER-TLV:	D0	2C	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	33

TERMINAL RESPONSE: LAUNCH BROWSER 5.9.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.26.5.9.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 5.9.

27.22.4.26.5.10 LAUNCH BROWSER (support of Text Attribute – Foreground and Background Colour)

27.22.4.26.5.10.1 Definition and applicability

See clause 3.2.2.

27.22.4.26.5.10.2 Conformance requirements

The ME shall support the LAUNCH BROWSER Proactive UICC Command as defined in:

– TS 31.111 [15] clause 5.2, clauses 6.4.26 and 6.6.26, clause 8.6, clause 8.7, clause 8.48, clause 9.2, clause 8.2, clause 8.47, clause 8.49, clause 8.50, clause 8.15, clause 8.31 and clause 8.70.

27.22.4.26.5.10.3 Test purpose

To verify that the ME performs a proper user confirmation with an alpha identifier according to the foreground and background colour text attribute configuration, launches the Wap session required in LAUNCH BROWSER and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.26.5.10.4 Method of test

27.22.4.26.5.10.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

A valid access to 2 different Wap gateways is required:

– the default Wap parameters (IP address, gateway/proxy identity, called number, URL …) of the tested mobile shall be properly filled to access one of the gateways ("default gateway")

With that default gateway we shall be able to access to an URL different from the default one.

– another gateway with an IP address different from the one defined in default Wap parameters.

The Bearer Parameters defined in 27.22.4.26.1.4.1 shall be used.

27.22.4.26.5.10.4.2 Procedure

Expected Sequence 5.10 (LAUNCH BROWSER, connect to the specified URL with Text Attribute – Foreground and Background Colour)

Step	Direction	MESSAGE / Action	Comments
0	ME		[The ME is in idle mode and the browser’s cache shall have been cleared.]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.10.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.10.1	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
4	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with foreground and background colour according to the text attribute configuration]
5	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.10.1	[Command performed successfully]
7	MEUSS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the default Wap session is properly established. The user shall attempt to close the browser or shall at least set the ME to the idle screen.
10	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 5.10.2
11	ME → UICC	FETCH
12	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 5.10.2	[connect to the defined URL, "launch browser, if not already launched", no null alpha id]
13	ME → USER	ME displays the alpha identifier	[alpha identifier is displayed with ME’s default foreground and background colour]
14	USER → ME	The user may have to confirm the launch browser.	[option: user confirmation]
15	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 5.10.1	[Command performed successfully]
16	ME → USS	The ME attempts to launch the session with the default Wap parameters and the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
17	UICC → ME	PROACTIVE UICC SESSION ENDED
18	USER → ME	The user verifies that the default Wap session is properly established.

PROACTIVE COMMAND: LAUNCH BROWSER 5.10.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 1"

Text Attribute

Formatting position: 0

Formatting length: 13

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	31	D0	04
	00	0D	00	B4

PROACTIVE COMMAND: LAUNCH BROWSER 5.10.2

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier "Defined URL 2"

Coding:

BER-TLV:	D0	2C	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	0D	44	65	66
	69	6E	65	64	20	55	52	4C	20	32

TERMINAL RESPONSE: LAUNCH BROWSER 5.10.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.26.5.10.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 5.10.

27.22.4.26.6 LAUNCH BROWSER (UCS2 Display in Chinese)

27.22.4.26.6.1 Definition and applicability

See clause 3.2.2.

27.22.4.26.6.2 Conformance requirements

The ME shall support the LAUNCH BROWSER Proactive UICC Command as defined in:

Additionally the ME shall support the UCS2 facility for the coding of the Chinese characters, as defined in:

– ISO/IEC 10646 [17].

27.22.4.26.6.3 Test purpose

27.22.4.26.6.4 Method of test

27.22.4.26.6.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

A valid access to 2 different Wap gateways is required:

– the default Wap parameters (IP address, gateway/proxy identity, called number, URL …) of the tested mobile shall be properly filled to access one of the gateways ("default gateway").

With that default gateway we shall be able to access to an URL different from the default one.

– another gateway with an IP address different from the one defined in default Wap parameters.

The mobile is busy in a Wap session, the user navigates in pages different from the URL defined by default in Wap parameters.

The browser’s cache shall have been cleared before execution of the test sequence.

The Bearer Parameters defined in 27.22.4.26.1.4.1 shall be used.

27.22.4.26.6.4.2 Procedure

Expected Sequence 6.1 (LAUNCH BROWSER, use the existing browser, connect to the specified URL, UCS2 in Chinese)

Step	Direction	MESSAGE / Action	Comments
0	ME	The user is navigating in a Wap session (not the URL specified in the test sequence).	[Browser is in use, the current session is not secured]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 6.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 6.1.1	[connect to the defined URL, "use the existing browser", alpha id. In UCS2]
4	ME → USER	ME displays the alpha identifier "你好"	["Hello" in Chinese]
5	USER → ME	The user confirms the launch browser.	[user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 6.1.1	[Command performed successfully]
7	MEUSS	The ME does not close the existing session and attempts to connect the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the URL is connected; and the previous URL can be retrieved.

PROACTIVE COMMAND: LAUNCH BROWSER 6.1.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: use the existing browser

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier

Data coding scheme: UCS2 (16 bits)

Text: "你好"

Coding:

BER-TLV:	D0	24	81	03	01	15	02	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	05	80	4F	60
	59	7D

TERMINAL RESPONSE: LAUNCH BROWSER 6.1.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: use the existing browser

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.26.6.5 Test requirement

The ME shall operate in the manner defined in expected sequence 6.1.

27.22.4.26.7 LAUNCH BROWSER (UCS2 Display in Katakana)

27.22.4.26.7.1 Definition and applicability

See clause 3.2.2.

27.22.4.26.7.2 Conformance requirements

The ME shall support the LAUNCH BROWSER Proactive UICC Command as defined in:

Additionally the ME shall support the UCS2 facility for the coding of the Katakana characters, as defined in:

– ISO/IEC 10646 [17].

27.22.4.26.7.3 Test purpose

27.22.4.26.7.4 Method of test

27.22.4.26.7.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as USIM Application Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

A valid access to 2 different Wap gateways is required:

– the default Wap parameters (IP address, gateway/proxy identity, called number, URL …) of the tested mobile shall be properly filled to access one of the gateways ("default gateway").

With that default gateway we shall be able to access to an URL different from the default one.

– another gateway with an IP address different from the one defined in default Wap parameters.

The mobile is busy in a Wap session, the user navigates in pages different from the URL defined by default in Wap parameters.

The browser’s cache shall have been cleared before execution of the test sequence.

The Bearer Parameters defined in 27.22.4.26.1.4.1 shall be used.

27.22.4.26.7.4.2 Procedure

Expected Sequence 7.1 (LAUNCH BROWSER, use the existing browser, connect to the specified URL, UCS2 in Katakana)

Step	Direction	MESSAGE / Action	Comments
0	ME	The user is navigating in a Wap session (not the URL defined in the test sequence).	[Browser is in use, the current session is not secured]]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 7.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 7.1.1	[connect to the defined URL, "use the existing browser", alpha id. In UCS2]
4	ME → USER	ME displays the alpha identifier "ル"	[Character in Katakana]
5	USER → ME	The user confirms the launch browser.	[user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 7.1.1	[Command performed successfully]
7	MEUSS	The ME does not close the existing session and attempts to connect the URL specified in LAUNCH BROWSER command.	[The USS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the URL is connected; and the previous URL can be retrieved.

PROACTIVE COMMAND: LAUNCH BROWSER 7.1.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: use the existing browser

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Alpha Identifier

Data coding scheme: UCS2 (16 bits)

Text: "ル"

Coding:

BER-TLV:	D0	22	81	03	01	15	02	82	02	81	82	31
	00	05	03	80	30	EB
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	05	03	80	30	EB

TERMINAL RESPONSE: LAUNCH BROWSER 7.1.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: use the existing browser

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.26.7.5 Test requirement

The ME shall operate in the manner defined in expected sequence 7.1.

27.22.4.26.8 LAUNCH BROWSER (NG-RAN bearer)

27.22.4.26.8.1 Definition and applicability

See clause 3.2.2.

27.22.4.26.8.2 Conformance requirements

The ME shall support the LAUNCH BROWSER Proactive UICC Command as defined in:

– TS 31.111 [15] clause 5.2, clauses 6.4.26 and 6.6.26, clause 8.6, clause 8.7, clause 8.48, clause 9.2, clause 8.2, clause 8.47, clause 8.49, clause 8.50, clause 8.15 and clause 8.31.

27.22.4.26.8.3 Test purpose

To verify that when the ME is in connected state, it launches properly the browser session required in LAUNCH BROWSER, and returns a successful result in the TERMINAL RESPONSE command.

27.22.4.26.8.4 Method of test

27.22.4.26.8.4.1 Initial conditions

The ME is connected to the USIM Simulator and the NG-SS. NG-SS is configured with the IMSI within the USIM application, the home domain name, public and private user identities together with the shared secret key of IMS AKA algorithm, related to the IMS private user identity (IMPI) that is configured on the UICC card equipped into the ME. NG-SS is able to perform IMS AKA authentication for the IMPI, according to 3GPP TS 33.203 [45] clause 6.1.

The NG-RAN parameters of the NG-SS are:

– Mobile Country Code (MCC) = 001;

– Mobile Network Code (MNC) = 01;

– Tracking Area Code (TAC) = 000001.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The default NG-RAN UICC, the default NG-RAN parameters and the following URSP rules stored in the ME are used:

URSP:

Rule Precedence =1

Traffic Descriptor:

DNN=TestGp.rs

Route Selection Descriptor:

Precedence=1
Network Slice Selection, S-NSSAI: 01 01 01 02 (ST: MBB, SD: 010102)
SSC Mode Selection: SSC Mode 1
Access Type preference: 3GPP access

Rule Precedence = <lowest priority>

Traffic Descriptor: *

Route Selection Descriptor:

Precedence =1
Network Slice Selection, S-NSSAI: 01 01 01 01 (ST: MBB, SD: 010101)
SSC Mode Selection: SSC Mode 1
DNN Selection: internet

The Allowed S-NSSAI list is configured in NG-SS as ’01 01 01 01′, ’01 01 01 02′ and ’01 01 01 03′.

The browser’s cache shall have been cleared before execution of the test sequence.

For Expected Sequence 8.2, Service n°30 “Call Control by USIM” shall be available in EF_UST.

27.22.4.26.8.4.2 Procedure

Expected Sequence 8.1 (LAUNCH BROWSER, only NG-RAN bearer specified and gateway proxy identity)

Step	Direction	MESSAGE / Action	Comments
0	ME		[The ME is in connected mode, NG-RAN supported by the ME and activated, the terminal might need to be configured with an entry linking the Gateway/Proxy Identity in the proactive command with the corresponding connectivity parameters in the mobile. The browser’s cache shall have been cleared.]
1	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 8.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 8.1.1	[connect to the defined URL, "launch browser, if not already launched, 1 bearer specified, gateway/proxy id specified]
4	ME → USER	ME may display a default message
5	USER → ME	The user may confirm the launch browser.	[option: user confirmation]
6	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 8.1.1	[Command performed successfully]
7	ME NG-SS	The ME attempts to connect the URL specified in LAUNCH BROWSER command using the requested bearer and proxy identity	[The NG-SS shall handle the request of additional URLs as defined in the initial conditions clause]
8	UICC → ME	PROACTIVE UICC SESSION ENDED
9	USER → ME	The user verifies that the browser session is properly established with the required bearer.

PROACTIVE COMMAND: LAUNCH BROWSER 8.1.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Bearer NG-RAN

Gateway/Proxy id DCSunpacked, 8 bits data

Text string abc.def.ghi.jkl (different from the default IP address)

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	32	01	03	0D	10
	04	61	62	63	2E	64	65	66	2E	67	68	69
	2E	6A	6B	6C

TERMINAL RESPONSE: LAUNCH BROWSER 8.1.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 8.2 (LAUNCH BROWSER, Trigger LAUNCH BROWSER by CALL CONTROL)

Step	Direction	MESSAGE / Action	Comments
0	ME	The ME is configured to register for IMS after switch on.	[The terminal might need to be configured with an entry linking the Gateway/Proxy Identity in the proactive command with the corresponding connectivity parameters in the mobile. The browser’s cache shall have been cleared.]
1	User  ME	The ME is made to attempt an IMS voice call to "+01234567890123456789"
2	ME  UICC	ENVELOPE CALL CONTROL 8.2.1
3	UICC → ME	CALL CONTROL RESULT 8.2.1	not Allowed
4	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 8.2.1
5	ME → UICC	FETCH
6	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 8.2.1	[connect to the defined URL, "launch browser, if not already launched, 1 bearer specified, gateway/proxy id specified]
7	ME → USER	ME may display a default message
8	USER → ME	The user may confirm the launch browser.	[option: user confirmation]
9	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 8.2.1	[Command performed successfully]
10	ME NG-SS	The ME attempts to connect the URL specified in LAUNCH BROWSER command using the requested bearer and proxy identity	[The NG-SS shall handle the request of additional URLs as defined in the initial conditions clause]
11	UICC → ME	PROACTIVE UICC SESSION ENDED
12	USER → ME	The user verifies that the browser session is properly established with the required bearer.

ENVELOPE CALL CONTROL 8.2.1

Logically:

Device identities

Source device: ME

Destination device: UICC

Address

TON: International

NPI: "ISDN / telephone numbering plan" or "unknown"

Dialling number string "+01234567890123456789"

Capability configuration parameters 1

This parameter is optional. If present, the contents shall not be checked.

Subaddress

This parameter is optional. If present, the contents shall not be checked.

Location Information

MCC & MNC the mobile country and network code (00F110)

Tracking Area Code (TAC) = 000001;

Cell Identity value = 0001 (36 bits);

Capability configuration parameters 2

This parameter is optional. If present, the contents shall not be checked.

Coding:

BER-TLV:	D4	Note 1	82	02	82	81	86	0B	91	10	32	54
	76	98	10	32	54	76	98	Note 2	Note 3	13	Note 5	00
	F1	10	00	00	01	00	01	Note 4

Note 1: Length of BER-TLV is ‘1A’ plus the actual length of all the present optional SIMPLE-TLV data objects.

Note 2: Capability configuration parameters 1 may be present at this place. If present, it may take up several octets.

Note 3: Subaddress may be present at this place. If present, it may take up several octets.

Note 4: Capability configuration parameters 2 may be present at this place. If present, it may take up several octets.

Note 5: Depending on the presence of the Extended Cell Identity Value the length is ’07’ or ’09’

CALL CONTROL RESULT 8.2.1

Logically:

Call control result: ’01’ = not Allowed

Coding:

BER-TLV:

PROACTIVE COMMAND: LAUNCH BROWSER 8.2.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Bearer NG-RAN

Gateway/Proxy id DCSunpacked, 8 bits data

Text string abc.def.ghi.jkl (different from the default IP address)

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	32	01	03	0D	10
	04	61	62	63	2E	64	65	66	2E	67	68	69
	2E	6A	6B	6C

TERMINAL RESPONSE: LAUNCH BROWSER 8.2.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 8.3 (LAUNCH BROWSER, LAUNCH BROWSER, Trigger LAUNCH BROWSER by MT Call event)

Step	Direction	MESSAGE / Action	Comments
0	ME	The ME is configured to register for IMS after switch on.	[The terminal might need to be configured with an entry linking the Gateway/Proxy Identity in the proactive command with the corresponding connectivity parameters in the mobile. The browser’s cache shall have been cleared.]
1	UICC  ME	PROACTIVE COMMAND PENDING: SET UP EVENT LIST 8.3.1
2	ME  UICC	FETCH
3	UICC  ME	PROACTIVE COMMAND: SET UP EVENT LIST 8.3.1
4	ME  UICC	TERMINAL RESPONSE: SET UP EVENT LIST 8.3.1
5	NG-SSME	CALL SET UP
6	ME  UICC	ENVELOPE: EVENT DOWNLOAD – MT Call 8.3.1
7	UICC → ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 8.3.1
8	ME → UICC	FETCH
9	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 8.3.1	[connect to the defined URL, "launch browser, if not already launched, 1 bearer specified, gateway/proxy id specified]
10	ME → USER	ME may display a default message
11	USER → ME	The user may confirm the launch browser.	[option: user confirmation]
12	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 8.3.1	[Command performed successfully]
13	ME NG-SS	The ME attempts to connect the URL specified in LAUNCH BROWSER command using the requested bearer and proxy identity	[The NG-SS shall handle the request of additional URLs as defined in the initial conditions clause]
14	UICC → ME	PROACTIVE UICC SESSION ENDED
15	USER → ME	The user verifies that the browser session is properly established with the required bearer.

PROACTIVE COMMAND: SET UP EVENT LIST 8.3.1

Logically:

Command details

Command number: 1

Command type: SET UP EVENT LIST

Command qualifier: ’00’

Device identities

Source device: UICC

Destination device: ME

Event list

Event 1: MT call

Coding:

BER-TLV:	D0	0C	81	03	01	05	00	82	02	81	82	99
	01	00

TERMINAL RESPONSE: SET UP EVENT LIST 8.3.1

Logically:

Command details

Command number: 1

Command type: SET UP EVENT LIST

Command qualifier: ’00’

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

EVENT DOWNLOAD – MT CALL 8.3.1

Logically:

Event list: MT call event

Device identities

Source device: Network

Destination device: UICC

Transaction identifier:

TI value: 0 (bit 5-7) – If A.1/150 is supported, this shall not be verified

TI flag: 0 (bit 8)

Address:

TON Unknown

NPI "ISDN / telephone numbering plan"

Dialling number string "9876"

Coding:

BER-TLV:	D6	0F	19	01	00	82	02	83	81	1C	01	00
	86	03	81	89	67

PROACTIVE COMMAND: LAUNCH BROWSER 8.3.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Bearer NG-RAN

Gateway/Proxy id DCSunpacked, 8 bits data

Text string abc.def.ghi.jkl (different from the default IP address)

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	32	01	03	0D	10
	04	61	62	63	2E	64	65	66	2E	67	68	69
	2E	6A	6B	6C

TERMINAL RESPONSE: LAUNCH BROWSER 8.3.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 8.4(LAUNCH BROWSER, Trigger LAUNCH BROWSER during mobile originated call )

Step	Direction	MESSAGE / Action	Comments
0	ME	The ME is configured to register for IMS after switch on.	[The terminal might need to be configured with an entry linking the Gateway/Proxy Identity in the proactive command with the corresponding connectivity parameters in the mobile. The browser’s cache shall have been cleared.]
1	User  ME	The ME is made to attempt an IMS voice call to "+01234567890123456789"	Call need to be connected and held
2	ME →UICC	ENVELOPE: SMS-PP DOWNLOAD 8.4.1
3	UICC →ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 8.4.1
4	ME → UICC	FETCH
5	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 8.4.1	[connect to the defined URL, "launch browser, if not already launched, 1 bearer specified, gateway/proxy id specified]
6	ME → USER	ME may display a default message
7	USER → ME	The user may confirm the launch browser.	[option: user confirmation]
8	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 8.4.1	[Command performed successfully]
9	ME NG-SS	The ME attempts to connect the URL specified in LAUNCH BROWSER command using the requested bearer and proxy identity	[The NG-SS shall handle the request of additional URLs as defined in the initial conditions clause]
10	UICC → ME	PROACTIVE UICC SESSION ENDED
11	USER → ME	The user verifies that the browser session is properly established with the required bearer.

ENVELOPE: SMS-PP DOWNLOAD 8.4.1

Logically:

Device identities

Source device: Network

Destination device: UICC

Address

TON: International number

NPI: "ISDN / telephone numbering plan"

Dialling number string: "+01234567890123456789"

SMS TPDU

TP-MTI: SMS-DELIVER

TP-MMS: No more messages waiting for the MS in this SC

TP‑RP: TP-Reply-Path is not set in this SMS-DELIVER

TP-UDHI: TP-UD field contains only the short message

TP-SRI: A status report will not be returned to the SME

TP-OA

TON: International number

NPI: "ISDN / telephone numbering plan"

Address value "1234"

TP-PID : (U)SIM Data download

TP-DCS:

Coding Group: Data coding/message class

Message Code: 8-bit data

Message Class: Class 2 (U)SIM Specific Message

TP-SCTS: 01/01/98 00:00:00 +0

TP-UDL:08

TP-UD: 3132333435363738

BER-TLV:	D1	23	82	02	83	81	06	04	02	91	00	11
	22	0B	17	04	04	91	21	43	7F	F6	89	10
	10	00	00	00	00	08	31	32	33	34	35	36
	37	38

PROACTIVE COMMAND: LAUNCH BROWSER 8.4.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Bearer NG-RAN

Gateway/Proxy id DCSunpacked, 8 bits data

Text string abc.def.ghi.jkl (different from the default IP address)

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	32	01	03	0D	10
	04	61	62	63	2E	64	65	66	2E	67	68	69
	2E	6A	6B	6C

TERMINAL RESPONSE: LAUNCH BROWSER 8.4.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

Expected Sequence 8.5 (LAUNCH BROWSER, Trigger LAUNCH BROWSER during mobile terminated call)

Step	Direction	MESSAGE / Action	Comments
0	ME	The ME is configured to register for IMS after switch on.	[The terminal might need to be configured with an entry linking the Gateway/Proxy Identity in the proactive command with the corresponding connectivity parameters in the mobile. The browser’s cache shall have been cleared.]
1	NG-SSME	CALL SET UP	Call need to be connected and held
2	ME → UICC	ENVELOPE: SMS-PP DOWNLOAD 8.5.1
3	UICC →ME	PROACTIVE COMMAND PENDING: LAUNCH BROWSER 8.5.1
4	ME → UICC	FETCH
5	UICC → ME	PROACTIVE COMMAND: LAUNCH BROWSER 8.5.1	[connect to the defined URL, "launch browser, if not already launched, 1 bearer specified, gateway/proxy id specified]
6	ME → USER	ME may display a default message
7	USER → ME	The user may confirm the launch browser.	[option: user confirmation]
8	ME → UICC	TERMINAL RESPONSE: LAUNCH BROWSER 8.5.1	[Command performed successfully]
9	ME NG-SS	The ME attempts to connect the URL specified in LAUNCH BROWSER command using the requested bearer and proxy identity	[The NG-SS shall handle the request of additional URLs as defined in the initial conditions clause]
10	UICC → ME	PROACTIVE UICC SESSION ENDED
11	USER → ME	The user verifies that the browser session is properly established with the required bearer.

ENVELOPE: SMS-PP DOWNLOAD 8.5.1

Logically:

Device identities

Source device: Network

Destination device: UICC

Address

TON: International number

NPI: "ISDN / telephone numbering plan"

Dialling number string: "+01234567890123456789"

SMS TPDU

TP-MTI: SMS-DELIVER

TP-MMS: No more messages waiting for the MS in this SC

TP‑RP: TP-Reply-Path is not set in this SMS-DELIVER

TP-UDHI: TP-UD field contains only the short message

TP-SRI: A status report will not be returned to the SME

TP-OA

TON: International number

NPI: "ISDN / telephone numbering plan"

Address value "1234"

TP-PID : (U)SIM Data download

TP-DCS:

Coding Group: Data coding/message class

Message Code: 8-bit data

Message Class: Class 2 (U)SIM Specific Message

TP-SCTS: 01/01/98 00:00:00 +0

TP-UDL:08

TP-UD: 3132333435363738

BER-TLV:	D1	23	82	02	83	81	06	04	02	91	00	11
	22	0B	17	04	04	91	21	43	7F	F6	89	10
	10	00	00	00	00	08	31	32	33	34	35	36
	37	38

PROACTIVE COMMAND: LAUNCH BROWSER 8.5.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: UICC

Destination device: ME

URL http://xxx.yyy.zzz (Note: this URL shall be different from the default URL, but it can be reached from the gateway defined by default in the browser parameters of the mobile)

Bearer NG-RAN

Gateway/Proxy id DCSunpacked, 8 bits data

Text string abc.def.ghi.jkl (different from the default IP address)

Coding:

BER-TLV:	D0	32	81	03	01	15	00	82	02	81	82	31
	12	68	74	74	70	3A	2F	2F	78	78	78	2E
	79	79	79	2E	7A	7A	7A	32	01	03	0D	10
	04	61	62	63	2E	64	65	66	2E	67	68	69
	2E	6A	6B	6C

TERMINAL RESPONSE: LAUNCH BROWSER 8.5.1

Logically:

Command details

Command number: 1

Command type: LAUNCH BROWSER

Command qualifier: launch browser, if not already launched

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.26.8.5 Test requirement

The ME shall operate in the manner defined in expected sequence 8.1 to 8.5.

27.22.4.27 OPEN CHANNEL

27.22.4.27.1 Void

27.22.4.27.2 Open Channel (related to GPRS)

27.22.4.27.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.27.2.2 Conformance requirements

The ME shall support the class "e" commands as defined in:

– TS 31.111[15] clause 5.2, clauses 6.4.27 and 6.6.27, clause 8.6, clause 8.7, clause 9.2, clause 8.2, clause 8.15, clause 8.31 and clause 8.70.

27.22.4.27.2.3 Test purpose

To verify that the ME shall send a:

– TERMINAL RESPONSE (OK); or

– TERMINAL RESPONSE (Command performed with modification); or

– TERMINAL RESPONSE (User did not accept the proactive command);

– TERMINAL RESPONSE (ME currently unable to process command);

to the UICC after the ME receives the OPEN CHANNEL proactive command. The TERMINAL RESPONSE sent back to the UICC is the result of the ME and the network capabilities against requested parameters by the UICC.

27.22.4.27.2.4 Method of test

27.22.4.27.2.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS. The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The following Bearer Parameters used are those defined in the default Test PDP context for test cases using packet services:

The Channel identifier value used for these tests is set to 1 as an example.

This channel identifier is dependent on the ME’s default channel identifier as declared in table A.2/27.

The following Bearer Parameters used are those defined in the default Test PDP ContextDch, as specified in TS 34.123-3 [27], clause 8.10 for test cases using packet services:

Bearer Parameters

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

GPRS Parameters

Network access name: TestGp.rs

User login: UserLog

User password: UserPwd

UICC/ME interface transport level

Transport format: UDP or TCP mode

Port number: 44444

Data destination address 01.01.01.01 (as an example)

Note: If a data destination address different to 01.01.01.01 is used then the same value is used in the content of the affected Open Channel commands and the network simulator setup and related UE settings might require a corresponding adaptation.

Prior to test case execution the apparatus supplier shall have provided the "Preferred buffer size supported by the terminal for Open Channel command" as requested in table A.2/29.

Pre-condition for successful execution of expected sequence 2.1:

If the terminal does not support the execution of an Open Channel (GPRS) command when no Network Access Name TLV is present in the proactive command and when no default Access Point Name is set in the terminal configuration (s.a. table A.1/48), then "TestGp.rs" shall be set and activated as default Access Point Name in the terminal configuration prior to execution of the proactive command in expected sequence 2.1.

27.22.4.27.2.4.2 Procedure

Expected Sequence 2.1 void

NOTE: The above sequence has been made void, however the messages defined below are still required for further test sequences.

PROACTIVE COMMAND: OPEN CHANNEL 2.1.1

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: UICC

Destination device: ME

Bearer

Bearer type: GPRS

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: 1400

Text String: UserLog (User login)

Text String: UserPwd (User password)

UICC/ME interface transport level

Transport format: UDP

Port number: 44444

Data destination address 01.01.01.01

Coding:

BER-TLV:	D0	36	81	03	01	40	01	82	02	81	82	35
	07	02	03	04	03	04	1F	02	39	02	05	78
	0D	08	F4	55	73	65	72	4C	6F	67	0D	08
	F4	55	73	65	72	50	77	64	3C	03	01	AD
	9C	3E	05	21	01	01	01	01

TERMINAL RESPONSE: OPEN CHANNEL 2.1.1A

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Channel status Channel identifier 1 and link established or PDP context activated

Bearer description

Bearer type: GPRS

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: 1400

Coding:

BER-TLV:	81	03	01	40	01	82	02	82	81	83	01	00
	38	02	81	00	35	07	02	03	04	03	04	1F
	02	39	02	05	78

TERMINAL RESPONSE: OPEN CHANNEL 2.1.1B

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Channel status Channel identifier 1 and link established or PDP context activated

Bearer description

Bearer type: GPRS

Bearer parameter:

Precedence Class: 00

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: 1400

Coding:

BER-TLV:	81	03	01	40	01	82	02	82	81	83	01	00
	38	02	81	00	35	07	02	00	04	03	04	1F
	02	39	02	05	78

Expected Sequence 2.2 (OPEN CHANNEL, immediate link establishment GPRS, no alpha identifier, with network access name)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: OPEN CHANNEL 2.2.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: OPEN CHANNEL 2.2.1
4	ME → user	The ME may display channel opening information
5	ME → USS	PDP context activation request	[The UE may request IPv4 or IPv4v6 address as PDP type.]
6	USS → ME	PDP context activation accept
7	ME → UICC	TERMINAL RESPONSE: OPEN CHANNEL 2.2.1A or TERMINAL RESPONSE: OPEN CHANNEL 2.2.1B	[Command performed successfully]

PROACTIVE COMMAND: OPEN CHANNEL 2.2.1

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: UICC

Destination device: ME

Bearer

Bearer type: GPRS

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: 1400

Network access name: TestGp.rs

Text String: UserLog (User login)

Text String: UserPwd (User password)

UICC/ME interface transport level

Transport format: UDP

Port number: 44444

Data destination address 01.01.01.01

Coding:

BER-TLV:	D0	42	81	03	01	40	01	82	02	81	82	35
	07	02	03	04	03	04	1F	02	39	02	05	78
	47	0A	06	54	65	73	74	47	70	02	72	73
	0D	08	F4	55	73	65	72	4C	6F	67	0D	08
	F4	55	73	65	72	50	77	64	3C	03	01	AD
	9C	3E	05	21	01	01	01	01

TERMINAL RESPONSE: OPEN CHANNEL 2.2.1A

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Channel status Channel identifier 1 and link established or PDP context activated

Bearer Description:

Bearer Type: GPRS

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size 1400

Coding:

BER-TLV:	81	03	01	40	01	82	02	82	81	83	01	00
	38	02	81	00	35	07	02	03	04	03	04	1F
	02	39	02	05	78

TERMINAL RESPONSE: OPEN CHANNEL 2.2.1B

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Channel status Channel identifier 1 and link established or PDP context activated

Bearer Description:

Bearer Type: GPRS

Bearer parameter:

Precedence Class: 00

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size 1400

Coding:

BER-TLV:	81	03	01	40	01	82	02	82	81	83	01	00
	38	02	81	00	35	07	02	00	04	03	04	1F
	02	39	02	05	78

Expected Sequence 2.3 (OPEN CHANNEL, immediate link establishment, GPRS, with alpha identifier)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: OPEN CHANNEL 2.3.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: OPEN CHANNEL 2.3.1
4	ME → user	Confirmation phase with alpha ID	"Open ID"
5	user → ME	The user confirms
6	ME → USS	PDP context activation request	[The UE may request IPv4 or IPv4v6 address as PDP type.]
7	USS → ME	PDP context activation accept
8	ME → UICC	TERMINAL RESPONSE: OPEN CHANNEL 2.1.1A or TERMINAL RESPONSE: OPEN CHANNEL 2.1.1B	[Command performed successfully]

PROACTIVE COMMAND: OPEN CHANNEL 2.3.1

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier Open ID

Bearer

Bearer type: GPRS

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: 1400

Network access name: TestGp.rs

Text String: UserLog (User login)

Text String: UserPwd (User password)

UICC/ME interface transport level

Transport format: UDP

Port number: 44444

Data destination address 01.01.01.01

Coding:

BER-TLV:	D0	4B	81	03	01	40	01	82	02	81	82	05
	07	4F	70	65	6E	20	49	44	35	07	02	03
	04	03	04	1F	02	39	02	05	78	47	0A	06
	54	65	73	74	47	70	02	72	73	0D	08	F4
	55	73	65	72	4C	6F	67	0D	08	F4	55	73
	65	72	50	77	64	3C	03	01	AD	9C	3E	05
	21	01	01	01	01

Expected Sequence 2.4 (OPEN CHANNEL, immediate link establishment, GPRS, with null alpha identifier)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: OPEN CHANNEL 2.4.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: OPEN CHANNEL 2.4.1
4	ME → user	Confirmation phase	[The ME should not give any information]
5	user → ME	The user confirms	[Only if the ME asks for user confirmation]
6	ME → USS	PDP context activation request	[The UE may request IPv4 or IPv4v6 address as PDP type.]
7	USS → ME	PDP context activation accept
8	ME → UICC	TERMINAL RESPONSE: OPEN CHANNEL 2.1.1A or TERMINAL RESPONSE: OPEN CHANNEL 2.1.1B	[Command performed successfully]

PROACTIVE COMMAND: OPEN CHANNEL 2.4.1

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: ME

Destination device: UICC

Alpha Identifier Null

Bearer

Bearer type: GPRS

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: 1400

Network access name: TestGp.rs

Text String: UserLog (User login)

Text String: UserPwd (User password)

UICC/ME interface transport level

Transport format: UDP

Port number: 44444

Data destination address 01.01.01.01

Coding:

BER-TLV:	D0	44	81	03	01	40	01	82	02	81	82	05
	00	35	07	02	03	04	03	04	1F	02	39	02
	05	78	47	0A	06	54	65	73	74	47	70	02
	72	73	0D	08	F4	55	73	65	72	4C	6F	67
	0D	08	F4	55	73	65	72	50	77	64	3C	03
	01	AD	9C	3E	05	21	01	01	01	01

Expected Sequence 2.5 (OPEN CHANNEL, immediate link establishment, GPRS, command performed with modifications (buffer size) )

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: OPEN CHANNEL 2.5.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: OPEN CHANNEL 2.5.1
4	ME → user	The ME may display channel opening information
5	ME → USS	PDP context activation request	[The UE may request IPv4 or IPv4v6 address as PDP type.]
6	USS → ME	PDP context activation accept
7	ME → UICC	TERMINAL RESPONSE: OPEN CHANNEL 2.5.1A or TERMINAL RESPONSE: OPEN CHANNEL 2.5.1B	[Command performed with modification]

PROACTIVE COMMAND: OPEN CHANNEL 2.5.1

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: ME

Destination device: UICC

Bearer

Bearer type: GPRS

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: 65535

Network access name: TestGp.rs

Text String: UserLog (User login)

Text String: UserPwd (User password)

UICC/ME interface transport level

Transport format: UDP

Port number: 44444

Data destination address 01.01.01.01

Coding:

BER-TLV:	D0	42	81	03	01	40	01	82	02	81	82	35
	07	02	03	04	03	04	1F	02	39	02	FF	FF
	47	0A	06	54	65	73	74	47	70	02	72	73
	0D	08	F4	55	73	65	72	4C	6F	67	0D	08
	F4	55	73	65	72	50	77	64	3C	03	01	AD
	9C	3E	05	21	01	01	01	01

TERMINAL RESPONSE: OPEN CHANNEL 2.5.1A

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed with modifications (07)

Channel status Channel identifier 1 and link established or PDP context activated

Bearer description

Bearer type: GPRS

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: The buffer size TLV shall be attached and contain the value stated in table A.2/29 "Preferred buffer size supported by the terminal for Open Channel command".

Coding:

BER-TLV:	81	03	01	40	01	82	02	82	81	83	01	07
	38	02	81	00	35	07	02	03	04	03	04	1F
	02	Note 1

Note1: The buffer size TLV shall be attached and contain the value stated in table A.2/29 "Preferred buffer size supported by the terminal for Open Channel command".

TERMINAL RESPONSE: OPEN CHANNEL 2.5.1B

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed with modifications (07)

Channel status Channel identifier 1 and link established or PDP context activated

Bearer description

Bearer type: GPRS

Bearer parameter:

Precedence Class: 00

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: The buffer size TLV shall be attached and contain the value stated in table A.2/29 "Preferred buffer size supported by the terminal for Open Channel command".

Coding:

BER-TLV:	81	03	01	40	01	82	02	82	81	83	01	07
	38	02	81	00	35	07	02	00	04	03	04	1F
	02	Note 1

Note1: The buffer size TLV shall be attached and contain the value stated in table A.2/29 "Preferred buffer size supported by the terminal for Open Channel command".

Expected Sequence 2.6 Void

Expected Sequence 2.7A (OPEN CHANNEL, immediate link establishment, GPRS, open command with alpha identifier, User did not accept the proactive command)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: OPEN CHANNEL 2.7.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: OPEN CHANNEL 2.7.1
4	ME → user	Confirmation phase with alpha ID	[The ME shall display "Open ID"]
5	user → ME	The user rejects
6	ME → USS	No PDP context activation request is sent to the USS
7	ME → UICC	TERMINAL RESPONSE: OPEN CHANNEL 2.7.1A or TERMINAL RESPONSE: OPEN CHANNEL 2.7.1B	[User did not accept the proactive command]

Expected Sequence 2.7B (OPEN CHANNEL, immediate link establishment, GPRS, open command with alpha identifier, User did not accept the proactive command)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: OPEN CHANNEL 2.7.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: OPEN CHANNEL 2.7.1
4	ME → USS	PDP context activation request	[The UE may request IPv4 or IPv4v6 address as PDP type.]
5	USS → ME	PDP context activation accept
6	ME → user	Confirmation phase with alpha ID	[The ME shall display "Open ID"]
7	user → ME	The user rejects
8	ME → UICC	TERMINAL RESPONSE: OPEN CHANNEL 2.7.1A or TERMINAL RESPONSE: OPEN CHANNEL 2.7.1B	[User did not accept the proactive command]

PROACTIVE COMMAND: OPEN CHANNEL 2.7.1

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier "Open ID"

Bearer

Bearer type: GPRS

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: 1400

Network access name: TestGp.rs

Text String: UserLog (User login)

Text String: UserPwd (User password)

UICC/ME interface transport level

Transport format: UDP

Port number: 44444

Data destination address 01.01.01.01

Coding:

BER-TLV:	D0	4B	81	03	01	40	01	82	02	81	82	05
	07	4F	70	65	6E	20	49	44	35	07	02	03
	04	03	04	1F	02	39	02	05	78	47	0A	06
	54	65	73	74	47	70	02	72	73	0D	08	F4
	55	73	65	72	4C	6F	67	0D	08	F4	55	73
	65	72	50	77	64	3C	03	01	AD	9C	3E	05
	21	01	01	01	01

TERMINAL RESPONSE: OPEN CHANNEL 2.7.1A

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: ME

Destination device: UICC

Result

General Result: User did not accept the proactive command

Channel status The presence and content of this TLV shall not be verified

Bearer description

Bearer type: GPRS

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: Because the value depends in this case on the terminal’s implementation, it shall be ignored.

Coding:

BER-TLV:

Note 1

Note 2

Note1: The presence and content of the Channel Status TLV shall not be verified.

Note2: The buffer size TLV shall be present and because the value depends in this case on the terminal’s implementation, the value shall be ignored.

TERMINAL RESPONSE: OPEN CHANNEL 2.7.1B

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: ME

Destination device: UICC

Result

General Result: User did not accept the proactive command

Channel status The presence and content of this TLV shall not be verifiedBearer description

Bearer type: GPRS

Bearer parameter:

Precedence Class: 00

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: Because the value depends in this case on the terminal’s implementation, it shall be ignored.

Coding:

BER-TLV:

Note 1

Note 2

Note1: The presence and content of the Channel Status TLV shall not be verified.

Note2: The buffer size TLV shall be present and because the value depends in this case on the terminal’s implementation, the value shall be ignored.

Expected Sequence 2.8 Void

Expected Sequence 2.9 (OPEN CHANNEL, immediate link establishment, no alpha identifier, with network access name)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: OPEN CHANNEL 2.9.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: OPEN CHANNEL 2.9.1
4	ME → user	The ME may display channel opening information
5	ME → USS	PDP context activation request	[The UE may request IPv4 or IPv4v6 address as PDP type.]
6	USS → ME	PDP context activation accept
7	ME → UICC	TERMINAL RESPONSE: OPEN CHANNEL 2.9.1A or TERMINAL RESPONSE: OPEN CHANNEL 2.9.1B	[Command performed successfully]

PROACTIVE COMMAND: OPEN CHANNEL 2.9.1

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: UICC

Destination device: ME

Bearer

Bearer type: GPRS / UTRAN packet service / E-UTRAN

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: 1400

Network access name: TestGp.rs

Text String: UserLog (User login)

Text String: UserPwd (User password)

UICC/ME interface transport level

Transport format: TCP

Port number: 44444

Data destination address 01.01.01.01

Coding:

BER-TLV:	D0	42	81	03	01	40	01	82	02	81	82	35
	07	02	03	04	03	04	1F	02	39	02	05	78
	47	0A	06	54	65	73	74	47	70	02	72	73
	0D	08	F4	55	73	65	72	4C	6F	67	0D	08
	F4	55	73	65	72	50	77	64	3C	03	02	AD
	9C	3E	05	21	01	01	01	01

TERMINAL RESPONSE: OPEN CHANNEL 2.9.1A

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Channel status Channel identifier 1 and link established or PDP context activated

Bearer Description:

Bearer Type: GPRS

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size 1400

Coding:

BER-TLV:	81	03	01	40	01	82	02	82	81	83	01	00
	38	02	81	00	35	07	02	03	04	03	04	1F
	02	39	02	05	78

TERMINAL RESPONSE: OPEN CHANNEL 2.9.1B

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Channel status Channel identifier 1 and link established or PDP context activated

Bearer Description:

Bearer Type: GPRS

Bearer parameter:

Precedence Class: 00

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size 1400

Coding:

BER-TLV:	81	03	01	40	01	82	02	82	81	83	01	00
	38	02	81	00	35	07	02	00	04	03	04	1F
	02	39	02	05	78

Expected Sequence 2.10 (OPEN CHANNEL, multi Open Channel, one in TCP Server mode and one in TCP Client mode)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: OPEN CHANNEL 2.10.1	TCP server mode
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: OPEN CHANNEL 2.10.1
4	ME → UICC	TERMINAL RESPONSE: OPEN CHANNEL 2.10.1	[Command performed successfully] TCP in LISTEN state
5	UICC → ME	PROACTIVE COMMAND PENDING: OPEN CHANNEL 2.10.2	TCP Client mode
6	ME → UICC	FETCH
7	UICC → ME	PROACTIVE COMMAND: OPEN CHANNEL 2.10.2
8	ME → user	The ME may display channel opening information
9	ME → USS	PDP context activation request	[The UE may request IPv4 or IPv4v6 address as PDP type.]
10	USS → ME	PDP context activation accept
11	ME → UICC	TERMINAL RESPONSE: OPEN CHANNEL 2.10.2A or TERMINAL RESPONSE: OPEN CHANNEL 2.10.2B	[Command performed successfully]

PROACTIVE COMMAND: OPEN CHANNEL 2.10.1

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: RFU

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier Null

Buffer

Buffer size: 1400

UICC/terminal interface transport level

Transport format: TCP, UICC in server mode

Port number: 3516

Coding:

BER-TLV:	D0	14	81	03	01	40	00	82	02	81	82	05
	00	39	02	05	78	3C	03	03	0D	BC

TERMINAL RESPONSE: OPEN CHANNEL 2.10.1

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: RFU

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Channel status Channel identifier 1 and TCP in LISTEN state

Buffer

Buffer size: 1400

Coding:

BER-TLV:	81	03	01	40	00	82	02	82	81	83	01	00
	38	02	41	00	39	02	05	78

PROACTIVE COMMAND: OPEN CHANNEL 2.10.2

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: UICC

Destination device: ME

Bearer

Bearer type: GPRS / UTRAN packet service / E-UTRAN

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: 1400

Network access name: TestGp.rs

Text String: UserLog (User login)

Text String: UserPwd (User password)

UICC/ME interface transport level

Transport format: TCP

Port number: 44444

Data destination address 01.01.01.01

Coding:

BER-TLV:	D0	42	81	03	01	40	01	82	02	81	82	35
	07	02	03	04	03	04	1F	02	39	02	05	78
	47	0A	06	54	65	73	74	47	70	02	72	73
	0D	08	F4	55	73	65	72	4C	6F	67	0D	08
	F4	55	73	65	72	50	77	64	3C	03	02	AD
	9C	3E	05	21	01	01	01	01

TERMINAL RESPONSE: OPEN CHANNEL 2.10.2A

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Channel status Channel identifier 2 and link established or PDP context activated

Bearer Description:

Bearer Type: GPRS

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size 1400

Coding:

BER-TLV:	81	03	01	40	01	82	02	82	81	83	01	00
	38	02	82	00	35	07	02	03	04	03	04	1F
	02	39	02	05	78

TERMINAL RESPONSE: OPEN CHANNEL 2.10.2B

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Channel status Channel identifier 2 and link established or PDP context activated

Bearer Description:

Bearer Type: GPRS

Bearer parameter:

Precedence Class: 00

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size 1400

Coding:

BER-TLV:	81	03	01	40	01	82	02	82	81	83	01	00
	38	02	82	00	35	07	02	00	04	03	04	1F
	02	39	02	05	78

27.22.4.27.2.5 Test requirement

The ME shall operate in the manner defined in expected sequences 2.2 to 2.10.

27.22.4.27.3 Open Channel (default bearer)

27.22.4.27.3.1 Open Channel (default bearer, E-UTRAN)

Open Channel for Default (network) Bearer for E-UTRAN is tested in clause 27.22.4.27.6, expected sequences 6.4 and 6.5.

27.22.4.27.3.2 Open Channel (Default bearer, GERAN/UTRAN)

27.22.4.27.3.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.27.3.2.2 Conformance requirements

The ME shall support the class "e" commands as defined in:

– TS 31.111[15] clause 5.2, clauses 6.4.27 and 6.6.27, clause 8.2, clause 8.6, clause 8.7, clause 8.52, clause 8.55, 8.59 and clause 9.2,

27.22.4.27.3.2.3 Test purpose

To verify that the ME allocates the buffer, activates the PDP context and reports the Channel status using TERMINAL RESPONSE (Command performed successfully) to the UICC after the ME receives the OPEN CHANNEL proactive command.

27.22.4.27.3.2.4 Method of test

27.22.4.27.3.2.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS. The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The following Bearer Parameters used are those defined in the default Test PDP context for test cases using packet services:

The Channel identifier value used for these tests is set to 1 as an example.

This channel identifier is dependent on the ME’s default channel identifier as declared in table A.2/27.

The following Bearer Parameters used are those defined in the default Test PDP ContextDch, as specified in TS 34.123-3 [27], clause 8.10 for test cases using packet services:

Bearer Parameters

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

GPRS Parameters

Network access name: TestGp.rs

User login: UserLog

User password: UserPwd

UICC/ME interface transport level

Transport format: TCP mode

Port number: 44444

Data destination address 01.01.01.01 (as an example)

Pre-condition for successful execution of expected sequence x.1:

27.22.4.27.3.2.4.2 Procedure

Expected Sequence 3.1 (OPEN CHANNEL, Default Bearer, GPRS, with null alpha identifier)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: OPEN CHANNEL 3.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: OPEN CHANNEL 3.1.1
4	ME → User	[The ME should not give any information]	[If the ME ask for user confirmation, then the user shall confirm the Open Channel request]
5	ME → USS	PDP context activation request	[The ME may have activated a PDP context at earlier stage. In this case a PDP context activation at this point might not be required if the existing PDP context is reused.] [The UE may request IPv4 or IPv4v6 address as PDP type.]
6	USS → ME	PDP context activation accept
7	ME → UICC	TERMINAL RESPONSE: OPEN CHANNEL 3.1.1A or TERMINAL RESPONSE: OPEN CHANNEL 3.1.1B	[Command performed successfully]

PROACTIVE COMMAND: OPEN CHANNEL 3.1.1

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment, automatic reconnection

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier Null

Bearer

Bearer type: Default bearer for requested transport layer

Buffer

Buffer size: 1400

UICC/ME interface transport level

Transport format: TCP, UICC in client mode, remote connection

Port number: 44444

Data destination address 01.01.01.01

Coding:

BER-TLV:	D0	1E	81	03	01	40	03	82	02	81	82	85
	00	35	01	03	39	02	05	78	3C	03	02	AD
	9C	3E	05	21	01	01	01	01

TERMINAL RESPONSE: OPEN CHANNEL 3.1.1A

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment, automatic reconnection

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Channel status Channel identifier 1 and link established or PDP context activated

Bearer

Bearer type: Default bearer for requested transport layer

Buffer

Buffer size: 1400

Coding:

BER-TLV:	81	03	01	40	03	82	02	82	81	83	01	00
	38	02	81	00	35	01	03	39	02	05	78

TERMINAL RESPONSE: OPEN CHANNEL 3.1.1B

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment, automatic reconnection

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Channel status Channel identifier 1 and link established or PDP context activated

Bearer description

Bearer type: GPRS

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: 1400

Coding:

BER-TLV:	81	03	01	40	03	82	02	82	81	83	01	00
	38	02	81	00	35	07	02	03	04	03	04	1F
	02	39	02	05	78

27.22.4.27.3.2.5 Test requirement

The ME shall operate in the manner defined in expected sequence 3.1.

27.22.4.27.4 Open Channel (Local Bearer)

TBD

27.22.4.27.5 Open Channel (GPRS, support of Text Attribute)

27.22.4.27.5.1 Open Channel (GPRS, support of Text Attribute – Left Alignment)

27.22.4.27.5.1.1 Definition and applicability

See clause 3.2.2.

27.22.4.27.5.1.2 Conformance requirements

The ME shall support the class "e" commands as defined in:

– TS 31.111 [15].

27.22.4.27.5.1.3 Test purpose

To verify that the ME displays an alpha identifier according to the left alignment text attribute configuration in OPEN CHANNEL and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.27.5.1.4 Method of test

27.22.4.27.5.1.4.1 Initial conditions

The ME is connected to the USIM Simulator and the USS.

The elementary files are coded as Toolkit default.

Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The channel identifier value used for these tests is set to 1 as an example.

This channel identifier is dependent on the ME’s default channel identifier as declared in table A.2/27.

The following Bearer Parameters used are those defined in the default Test PDP context3, as specified in TS 34.108 [12], for test cases using packet services:

Bearer Parameters: Same Bearer Parameters as defined in 27.22.4.27.2.4.1

GPRS Parameters: Same GPRS Parameters as defined in 27.22.4.27.2.4.1

UICC/ME interface transport level: Same UICC/ME transport interface level as defined in 27.22.4.27.2.4.1

Data destination address : Same Data Destination Address as defined in 27.22.4.27.2.4.1.

27.22.4.27.5.1.4.2 Procedure

Expected Sequence 5.1 (OPEN CHANNEL, immediate link establishment, GPRS, Text Attribute – Left Alignment)

Step	Direction	MESSAGE / Action	Comments
1	UICC → ME	PROACTIVE COMMAND PENDING: OPEN CHANNEL 5.1.1
2	ME → UICC	FETCH
3	UICC → ME	PROACTIVE COMMAND: OPEN CHANNEL 5.1.1
4	ME → USER	Confirmation phase with alpha ID	[alpha identifier is displayed with left alignment]
5	USER → ME	The user confirms
6	ME → USS	PDP context activation request	[The UE may request IPv4 or IPv4v6 address as PDP type.]
7	USS → ME	PDP context activation accept
8	ME → UICC	TERMINAL RESPONSE: OPEN CHANNEL 5.1.1A or TERMINAL RESPONSE: OPEN CHANNEL 5.1.1B	[Command performed successfully]
9	UICC → ME	PROACTIVE COMMAND PENDING: CLOSE CHANNEL 5.1.1
10	ME → UICC	FETCH
11	UICC → ME	PROACTIVE COMMAND: CLOSE CHANNEL 5.1.1
12	ME → USS	PDP context deactivation request
13	USS → ME	PDP context deactivation accept
14	ME → UICC	TERMINAL RESPONSE: CLOSE CHANNEL 5.1.1	[Command performed successfully]
15	UICC → ME	PROACTIVE COMMAND PENDING: OPEN CHANNEL 5.1.2
16	ME → UICC	FETCH
17	UICC → ME	PROACTIVE COMMAND: OPEN CHANNEL 5.1.2
18	ME → USER	Confirmation phase with alpha ID	[Message shall be formatted without left alignment. Remark: If left alignment is the ME’s default alignment as declared in table A.2/19, no alignment change will take place]
19	USER → ME	The user confirms
20	ME → USS	PDP context activation request	[The UE may request IPv4 or IPv4v6 address as PDP type.]
21	USS → ME	PDP context activation accept
22	ME → UICC	TERMINAL RESPONSE: OPEN CHANNEL 5.1.1A or TERMINAL RESPONSE: OPEN CHANNEL 5.1.1B	[Command performed successfully]
23	UICC → ME	PROACTIVE COMMAND PENDING: CLOSE CHANNEL 5.1.1
24	ME → UICC	FETCH
25	UICC → ME	PROACTIVE COMMAND: CLOSE CHANNEL 5.1.1
26	ME → USS	PDP context deactivation request
27	USS → ME	PDP context deactivation accept
28	ME → UICC	TERMINAL RESPONSE: CLOSE CHANNEL 5.1.1	[Command performed successfully]

PROACTIVE COMMAND: OPEN CHANNEL 5.1.1

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier "Open ID 1"

Bearer

Bearer type: GPRS

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: 1400

Network access name: TestGp.rs

Text String: UserLog (User login)

Text String: UserPwd (User password)

UICC/ME interface transport level

Transport format: UDP

Port number: 44444

Data destination address 01.01.01.01

Text Attribute

Formatting position: 0

Formatting length: 9

Formatting mode: Left Alignment, Normal Font, Bold Off, Italic Off, Underline Off, Strikethrough Off

Colour: Dark Green Foreground, Bright Yellow Background

Coding:

BER-TLV:	D0	53	81	03	01	40	01	82	02	81	82	05
	09	4F	70	65	6E	20	49	44	20	31	35	07
	02	03	04	03	04	1F	02	39	02	05	78	47
	0A	06	54	65	73	74	47	70	02	72	73	0D
	08	F4	55	73	65	72	4C	6F	67	0D	08	F4
	55	73	65	72	50	77	64	3C	03	01	AD	9C
	3E	05	21	01	01	01	01	D0	04	00	09	00
	B4

PROACTIVE COMMAND: OPEN CHANNEL 5.1.2

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: UICC

Destination device: ME

Alpha Identifier "Open ID 2"

Bearer

Bearer type: GPRS

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: 1400

Network access name: TestGp.rs

Text String: UserLog (User login)

Text String: UserPwd (User password)

UICC/ME interface transport level

Transport format: UDP

Port number: 44444

Data destination address 01.01.01.01

Coding:

BER-TLV:	D0	4D	81	03	01	40	01	82	02	81	82	05
	09	4F	70	65	6E	20	49	44	20	32	35	07
	02	03	04	03	04	1F	02	39	02	05	78	47
	0A	06	54	65	73	74	47	70	02	72	73	0D
	08	F4	55	73	65	72	4C	6F	67	0D	08	F4
	55	73	65	72	50	77	64	3C	03	01	AD	9C
	3E	05	21	01	01	01	01

PROACTIVE COMMAND: CLOSE CHANNEL 5.1.1

Logically:

Command details

Command number: 1

Command type: CLOSE CHANNEL

Command qualifier: RFU

Device identities

Source device: UICC

Destination device: Channel

Alpha Identifier "Close ID"

Coding:

BER-TLV:	D0	14	81	03	01	41	00	82	02	81	21
	85	08	43	6C	6F	73	65	20	49	44

TERMINAL RESPONSE: OPEN CHANNEL 5.1.1A

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Channel status Channel identifier 1 and link established or PDP context activated

Bearer description

Bearer type: GPRS

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: 1400

Coding:

BER-TLV:	81	03	01	40	01	82	02	82	81	83	01	00
	38	02	81	00	35	07	02	03	04	03	04	1F
	02	39	02	05	78

TERMINAL RESPONSE: OPEN CHANNEL 5.1.1B

Logically:

Command details

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Channel status Channel identifier 1 and link established or PDP context activated

Bearer description

Bearer type: GPRS

Bearer parameter:

Precedence Class: 00

Delay Class: 04

Reliability Class: 03

Peak throughput class: 04

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: 1400

Coding:

BER-TLV:	81	03	01	40	01	82	02	82	81	83	01	00
	38	02	81	00	35	07	02	00	04	03	04	1F
	02	39	02	05	78

TERMINAL RESPONSE: CLOSE CHANNEL 5.1.1

Logically:

Command details

Command number: 1

Command type: CLOSE CHANNEL

Command qualifier: RFU

Device identities

Source device: ME

Destination device: UICC

Result

General Result: Command performed successfully

Coding:

BER-TLV:

27.22.4.27.5.1.5 Test Requirement

The ME shall operate in the manner defined in expected sequences 5.1.

27.22.4.27.5.2 Open Channel (GPRS, support of Text Attribute – Center Alignment)

27.22.4.27.5.2.1 Definition and applicability

See clause 3.2.2.

27.22.4.27.5.2.2 Conformance requirements

The ME shall support the class "e" commands as defined in:

– TS 31.111 [15].

27.22.4.27.5.2.3 Test purpose

To verify that the ME displays an alpha identifier according to the center alignment text attribute configuration in OPEN CHANNEL and returns a successful result in the TERMINAL RESPONSE command send to the UICC.

27.22.4.27.5.2.4 Method of test

27.22.4.27.5.2.4.1 Initial conditions