27.22.4 Proactive UICC commands

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

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:

81

03

01

21

80

82

02

82

81

83

01

00

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:

– 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, clause 8.31 and clause 8.70.

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:

– 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, clause 8.31 and clause 8.70.

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:

– 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, clause 8.31 and clause 8.70.

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:

– 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, clause 8.31 and clause 8.70.

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:

– 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, clause 8.31 and clause 8.70.

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:

– 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, clause 8.31 and clause 8.70.

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:

– 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, clause 8.31 and clause 8.70.

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:

– 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, clause 8.31 and clause 8.70.

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:

– 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, clause 8.31 and clause 8.70.

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:

– 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, clause 8.31 and clause 8.70.

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 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.

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:

D0

09

81

03

01

01

03

82

02

81

82

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:

81

03

01

01

03

82

02

82

81

83

01

00

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:

81

03

01

01

03

82

02

82

81

83

01

03

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:

81

03

01

01

01

82

02

82

81

83

01

00

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:

81

03

01

01

01

82

02

82

81

83

01

03

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:

81

03

01

01

02

82

02

82

81

83

01

00

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:

81

03

01

01

02

82

02

82

81

83

01

03

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:

D0

09

81

03

01

01

00

82

02

81

82

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:

81

03

01

01

00

82

02

82

81

83

01

00

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:

81

03

01

01

00

82

02

82

81

83

01

03

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:

D0

09

81

03

01

01

04

82

02

81

82

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:

D0

09

81

03

01

01

05

82

02

81

82

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:

81

03

01

01

05

82

02

82

81

83

01

00

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:

D0

09

81

03

01

01

04

82

02

81

82

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

MEUSS

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:

D0

09

81

03

01

01

05

82

02

81

82

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:

81

03

01

01

05

82

02

82

81

83

01

00

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

MEUSS

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:

81

03

01

01

06

82

02

82

81

83

01

00

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:

81

03

01

01

06

82

02

82

81

83

01

03

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:

D0

09

81

03

01

01

04

82

02

81

82

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

MEUSS

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

MEUSS

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:

D0

09

81

03

01

01

04

82

02

81

82

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

MEUSS

Deactivate PDP context

Mobile will deactivate the PDP context

Note: this step can be performed in parallel or after step 8.

7

MEUSS

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:

81

03

01

01

06

82

02

82

81

83

01

00

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:

81

03

01

01

06

82

02

82

81

83

01

03

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:

EFFPLMN

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

EFOPLMNwACT

Logically: 1st PLMN: 254 001 (MCC MNC)

1st ACT: UTRAN

2nd PLMN: 254 001

2nd ACT: GSM

3rd PLMN: 274 002

3rd ACT: UTRAN

4th PLMN: 274 003

4th ACT: UTRAN

5th PLMN: 274 004

5th ACT: UTRAN

6th PLMN: 274 005

6th ACT: UTRAN

7th PLMN: 274 006

7th ACT: UTRAN

8th PLMN: 274 007

8th 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:

EFFPLMN

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

EFOPLMNwACT

Logically: 1st PLMN: 254 001 (MCC MNC)

1st ACT: E-UTRAN, UTRAN

2nd PLMN: 254 001

2nd ACT: GSM

3rd PLMN: 274 002

3rd ACT: E-UTRAN

4th PLMN: 274 003

4th ACT: E-UTRAN

5th PLMN: 274 004

5th ACT: E-UTRAN

6th PLMN: 274 005

6th ACT: E-UTRAN

7th PLMN: 274 006

7th ACT: E-UTRAN

8th PLMN: 274 007

8th 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:

81

03

01

01

07

82

02

82

81

83

01

00

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:

81

03

01

01

07

82

02

82

81

83

01

00

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:

81

03

01

01

07

82

02

82

81

83

01

00

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:

81

03

01

01

07

82

02

82

81

83

01

00

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:

  1. 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
  2. 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:

81

03

01

01

03

82

02

82

81

83

01

00

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:

81

03

01

01

03

82

02

82

81

83

01

03

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, 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

MEE-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 GPRS 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" in PS.

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:

D0

09

81

03

01

01

04

82

02

81

82

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

MEE-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

MEE-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:

81

03

01

01

06

82

02

82

81

83

01

00

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:

81

03

01

01

06

82

02

82

81

83

01

03

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.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.

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.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.

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.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.

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.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.

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.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.

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.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 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.

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.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 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.

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.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.

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.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 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.

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.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 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.

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.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

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.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:

81

03

01

13

00

82

02

82

81

83

01

00

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

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.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:

81

03

01

13

00

82

02

82

81

83

01

00

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:

81

03

01

13

00

82

02

82

81

83

01

04

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:

81

03

01

13

00

82

02

82

81

83

01

00

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:

81

03

01

13

00

82

02

82

81

83

01

04

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

01

01

02

91

10

40

F0

01

20

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

01

02

02

91

10

40

F0

01

20

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

01

03

02

91

10

40

F0

01

20

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

01

04

02

91

10

40

F0

01

20

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:

81

03

01

13

00

82

02

82

81

83

01

00

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:

81

03

01

13

00

82

02

82

81

83

01

00

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:

81

03

01

13

00

82

02

82

81

83

01

00

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:

81

03

01

13

00

82

02

82

81

83

01

00

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:

81

03

01

13

00

82

02

82

81

83

01

00

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:

81

03

01

13

00

82

02

82

81

83

01

00

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:

81

03

01

13

00

82

02

82

81

83

01

00

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:

81

03

01

13

00

82

02

82

81

83

01

00

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:

81

03

01

13

00

82

02

82

81

83

01

00

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:

81

03

01

13

00

82

02

82

81

83

01

00

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

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.5.4 Method of test

27.22.4.10.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.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:

81

03

01

13

00

82

02

82

81

83

01

00

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

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.6.4 Method of test

27.22.4.10.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.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:

81

03

01

13

00

82

02

82

81

83

01

00

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:

81

03

01

13

00

82

02

82

81

83

01

00

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:

81

03

01

13

01

82

02

82

81

83

01

00

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

REGISTER 1.1A

Logically (only SS argument):

REGISTER 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

REGISTER 1.1B

Logically (only SS argument):

REGISTER 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):

REGISTER SS RETURN RESULT

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):

REGISTER SS RETURN RESULT

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

02

01

15

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

80

01

00

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

REGISTER 1.2A

Logically (only SS argument):

REGISTER 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"

REGISTER 1.2B

Logically (only SS argument):

REGISTER 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):

REGISTER SS RETURN RESULT

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):

REGISTER SS RETURN RESULT

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

REGISTER 1.3

Logically (only SS argument):

INTERROGATE SS ARGUMENT

SS-Code

– Calling Line Id Restriction

Coding:

BER-TLV

30

03

04

01

12

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

0E

A4

06

04

01

06

0A

01

02

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:

81

03

01

11

00

82

02

82

81

83

01

32

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

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.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

REGISTER 4.1A

Same as cl 27.22.4.11.1.4.2 REGISTER 1.1A

REGISTER 4.1B

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

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.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

REGISTER 5.1A

Same as cl 27.22.4.11.1.4.2 REGISTER 1.1A

REGISTER 5.1B

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

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.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

REGISTER 6.1A

Same as cl 27.22.4.11.1.4.2 REGISTER 1.1A

REGISTER 6.1B

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

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.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

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

REGISTER 1.1

Logically (only USSD argument)

ProcessUnstructuredSS-Request ARGUMENT

USSD-DataCodingScheme:

– 7-bit default, no message class

USSD string:

– "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV

30

3D

04

01

F0

04

38

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

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-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 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

REGISTER 1.2

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

REGISTER 1.3

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

02

01

47

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

81

01

02

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

61

69

6E

69

6E

67

20

74

68

65

20

55

53

53

44

20

52

65

74

75

72

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:

D0

44

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

E5

60

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

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

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.

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.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

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

9E

02

00

01

REGISTER 2.1

Logically (only USSD argument)

ProcessUnstructuredSS-Request ARGUMENT

USSD-DataCodingScheme:

– 7-bit default, no message class

USSD string:

– "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV

30

3D

04

01

F0

04

38

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

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

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

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

E5

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

E5

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:

81

03

01

12

00

82

02

82

81

83

01

32

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

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.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

REGISTER 3.1

Logically (only USSD argument)

ProcessUnstructuredSS-Request ARGUMENT

USSD-DataCodingScheme:

– 7-bit default, no message class

USSD String:

– "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

BER-TLV

30

3D

04

01

F0

04

38

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

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-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 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

REGISTER 4.1

Logically (only USSD argument)

ProcessUnstructuredSS-Request ARGUMENT

USSD-DataCodingScheme:

– 7-bit default, no message class

USSD string:

– "ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-1234567890"

Coding:

Coding

30

3D

04

01

F0

04

40

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

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