27.22.5 Data Download to UICC
31.1243GPPMobile Equipment (ME) conformance test specificationRelease 16TSUniversal Subscriber Identity Module Application Toolkit (USAT) conformance test specification
27.22.5.1 SMS-PP Data Download
27.22.5.1.1 Definition and applicability
See clause 3.2.2.
27.22.5.1.2 Conformance requirement
The ME shall support the Proactive UICC: SMS-PP Data Download facility as defined in the following technical specifications:
– TS 31.111 [15] clause 5, clause 7.1, clause 8.1, clause 8.7, clause 8.13 and clause 11.
– TS 31.115 [28] clause 4.
– TS 23.038 [7] clause 4..
27.22.5.1.3 Test purpose
To verify that the ME transparently passes the "data download via SMS Point-to-point" messages to the UICC.
To verify that the ME returns the RP-ACK message back to the USS, if the UICC responds with ’90 00′, ’91 XX’, ’62 XX’ or ’63 XX’.
To verify that the ME with an SMS-PP download feature implementation prior to Rel-11 returns the RP-ERROR message back to the system Simulator, if the UICC responds with ’62 XX’ or ’63 XX’ (while the ME with the Rel-11 or later implemention of this feature returns an RP-ACK in this case).
To verify that the ME returns the response data from the UICC back to the USS in the TP-User-Data element of the RP-ACK message, if the UICC returns response data’.
27.22.5.1.4 Method of Test
27.22.5.1.4.1 Initial conditions
The ME is connected to the USIM Simulator and connected to the USS.
The "data download via SMS-PP" service is available in the USIM Service Table.
27.22.5.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 (SMS-PP Data Download over CS/PS, UTRAN/GERAN)
In case A.1/156 is supported perform the "CS related procedure 1" and continue with "Generic Test Procedure 1 (SMS-PP Data Download)" as defined in this clause 27.22.5.3.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 Profle Download and USIM initialisation |
|
2 |
ME → NWS |
ME performs CS/PS or CS registration. |
|
|
3 |
CONTINUE WITH STEP 4 Generic Test Procedure 1 (SMS-PP Data Download) in clause 27.22.5.3.4.2 |
In case A.1/156 is not supported but A.1/158 is supported perform the "PS related procedure" and continue with "Generic Test Procedure 1 (SMS-PP Data Download)" as defined in this clause 27.22.5.3.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 Profle Download and USIM initialisation |
|
2 |
ME → NWS |
ME performs CS/PS or PS registration. |
|
|
3 |
CONTINUE WITH STEP 4 Generic Test Procedure 1 (SMS-PP Data Download) in clause 27.22.5.3.4.2 |
27.22.5.1.5 Test requirement
The ME shall operate in the manner defined in expected sequence 1.9.
27.22.5.2 Cell Broadcast Data Download
27.22.5.2.1 Definition and applicability
See clause 3.2.2.
27.22.5.2.2 Conformance requirement
The ME shall support the Proactive UICC: Cell Broadcast Data Download facility as defined in:
– TS 31.111 [15] clause 5, clause 7.1.2, clause 8.5, clause 8.7 and clause 11.
– TS 31.115 [28] clause 5.
– TS 23.038 [7] clause 5.
27.22.5.2.3 Test purpose
To verify that the ME transparently passes the "data download via Cell Broadcast" messages to the UICC, which contain a message identifier found in EFCBMID.
27.22.5.2.4 Method of Test
27.22.5.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 Toolkit default with the following exeception:
EF PL shall contain an entry indicating "English".
A USS setting up only a GERAN or PCS 1900 cell shall be used for Expected sequence 1.1, 1.7 and 1.3.
A USS setting up only a UTRAN cell shall be used on and expected sequence 1.4, 1.5 and 1.6.
Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.
27.22.5.2.4.2 Procedure
Expected Sequence 1.1 (Cell Broadcast Data Download (GSM), ENVELOPE(CELL BROADCAST DOWNLOAD), ME does not display message)
|
Step |
Direction |
MESSAGE / Action |
Comments |
|
1 |
USS → ME |
CELL BROADCAST 1.1 |
Message identifier ’10 01′ |
|
2 |
ME → UICC |
ENVELOPE (CELL BROADCAST DOWNLOAD) 1.1 |
|
|
3 |
UICC → ME |
SW1, SW2 ’90 00′ |
Cell Broadcast Message 1.1
Logically:
Message Content
Serial Number
Geographical scope: Cell wide, normal display mode
Message code: 1
Update number: 1
Message Identifier: "1001"
Data coding Scheme
Message Coding: English, language using the GSM 7 bit default alphabet
Page Parameter
Total number of pages: 1
Page number: 1
Content of message: "Cell Broadcast"
Coding:
|
Coding |
C0 |
11 |
10 |
01 |
01 |
11 |
C3 |
32 |
9B |
0D |
12 |
CA |
|
DF |
61 |
F2 |
38 |
3C |
A7 |
83 |
40 |
20 |
10 |
08 |
04 |
|
|
02 |
81 |
40 |
20 |
10 |
08 |
04 |
02 |
81 |
40 |
20 |
10 |
|
|
08 |
04 |
02 |
81 |
40 |
20 |
10 |
08 |
04 |
02 |
81 |
40 |
|
|
20 |
10 |
08 |
04 |
02 |
81 |
40 |
20 |
10 |
08 |
04 |
02 |
|
|
81 |
40 |
20 |
10 |
08 |
04 |
02 |
81 |
40 |
20 |
10 |
08 |
|
|
04 |
02 |
81 |
40 |
20 |
10 |
08 |
04 |
02 |
81 |
40 |
20 |
|
|
10 |
08 |
04 |
02 |
ENVELOPE: CELL BROADCAST DOWNLOAD 1.1
Logically:
Cell Broadcast Download
Device identities
Source device: Network
Destination device: UICC
Cell Broadcast page
Serial Number
Geographical scope: Cell wide, normal display mode
Message code: 1
Update number: 1
Message Identifier: "1001"
Data coding Scheme
Message Coding: English, language using the GSM 7 bit default alphabet
Page Parameter
Number of pages: 1
Page number: 1
Content of message: "Cell Broadcast"
Coding:
|
BER-TLV: |
D2 |
5E |
82 |
02 |
83 |
81 |
8C |
58 |
C0 |
11 |
10 |
01 |
|
01 |
11 |
C3 |
32 |
9B |
0D |
12 |
CA |
DF |
61 |
F2 |
38 |
|
|
3C |
A7 |
83 |
40 |
20 |
10 |
08 |
04 |
02 |
81 |
40 |
20 |
|
|
10 |
08 |
04 |
02 |
81 |
40 |
20 |
10 |
08 |
04 |
02 |
81 |
|
|
40 |
20 |
10 |
08 |
04 |
02 |
81 |
40 |
20 |
10 |
08 |
04 |
|
|
02 |
81 |
40 |
20 |
10 |
08 |
04 |
02 |
81 |
40 |
20 |
10 |
|
|
08 |
04 |
02 |
81 |
40 |
20 |
10 |
08 |
04 |
02 |
81 |
40 |
|
|
20 |
10 |
08 |
04 |
02 |
81 |
40 |
20 |
10 |
08 |
04 |
02 |
Expected Sequence 1.2 (void)
Expected Sequence 1.3 (Cell Broadcast (GSM), ME may display the message)
|
Step |
Direction |
MESSAGE / Action |
Comments |
|
1 |
USS → ME |
CELL BROADCAST 1.2 |
Message identifier ’03 E7′ |
|
2a |
ME 🡪 USER |
ME may display the message |
|
|
2b |
ME 🡪 UICC |
ME shall not download the CB message to the UICC using ENVELOPE (CELL BROADCAST DOWNLOAD) |
|
|
3 |
USER 🡪 ME |
The user shall use a MMI dependent procedure to initiate the display of the received CB message |
[only if message has not been displayed in step 2a] |
|
4 |
ME 🡪 USER |
ME displays the message |
[only if message has not been displayed in step 2a] |
Cell Broadcast Message 1.2
Logically:
Message Content
Serial Number
Geographical scope: Cell wide, normal display mode
Message code: 1
Update number: 1
Message Identifier: "03E7"
Data coding Scheme
Message Coding: English, language using the GSM 7 bit default alphabet
Page Parameter
Total number of pages: 1
Page number: 1
Content of message: "Cell Broadcast".
Coding:
|
Coding |
C0 |
11 |
03 |
E7 |
01 |
11 |
C3 |
32 |
9B |
0D |
12 |
CA |
|
DF |
61 |
F2 |
38 |
3C |
A7 |
83 |
40 |
20 |
10 |
08 |
04 |
|
|
02 |
81 |
40 |
20 |
10 |
08 |
04 |
02 |
81 |
40 |
20 |
10 |
|
|
08 |
04 |
02 |
81 |
40 |
20 |
10 |
08 |
04 |
02 |
81 |
40 |
|
|
20 |
10 |
08 |
04 |
02 |
81 |
40 |
20 |
10 |
08 |
04 |
02 |
|
|
81 |
40 |
20 |
10 |
08 |
04 |
02 |
81 |
40 |
20 |
10 |
08 |
|
|
04 |
02 |
81 |
40 |
20 |
10 |
08 |
04 |
02 |
81 |
40 |
20 |
|
|
10 |
08 |
04 |
02 |
Expected Sequence 1.4 (Cell Broadcast (UMTS), ENVELOPE (CELL BROADCAST DOWNLOAD), ME does not display message)
TBD
Expected Sequence 1.5 (Cell Broadcast (UMTS), ENVELOPE (CELL BROADCAST DOWNLOAD), FETCH, MORE TIME, ME does not display message)
TBD
Expected Sequence 1.6 (Cell Broadcast (UMTS), ME displays message)
TBD
Expected Sequence 1.7 (Cell Broadcast (GSM),, ENVELOPE (CELL BROADCAST DATA DOWNLOAD), FETCH, MORE TIME, ME does not display message, User Data Header Payload)
|
Step |
Direction |
MESSAGE / Action |
Comments |
|
1 |
USS → ME |
CELL BROADCAST Message 1.7 |
Message identifier ’10 01′ |
|
2 |
ME → UICC |
ENVELOPE (CELL BROADCAST DOWNLOAD) 1.7 |
|
|
3 |
UICC → ME |
PROACTIVE COMMAND PENDING: MORE TIME 1.2 |
SW1/SW2 ’91 0B’ |
|
4 |
ME → UICC |
FETCH 1.2 |
|
|
5 |
UICC → ME |
PROACTIVE COMMAND:MORE TIME 1.2 |
|
|
6 |
ME → UICC |
TERMINAL RESPONSE: MORE TIME 1.2 |
|
|
7 |
UICC → ME |
SW1/SW2 ’90 00′ |
UICC session ended |
CELL BROADCAST Message 1.7
Logically:
Message Content
Serial Number
Geographical scope: Cell wide, normal display mode
Message code: 1
Update number: 1
Message Identifier: "1001"
Data coding Scheme
Message Coding: 8 bit data
Message class: Class 2 (U)SIM specific message
Page Parameter
Total number of pages: 1
Page number: 1
Secured User Header (Content of message)
TP-UDHL 2
IEI (U)SIM Toolkit Security Headers
IEIL 0
Command Packet Length: 77
Command Header Identifier: 0
Command Header Length: 13
Security Parameter Indicator: No RC, CC or DS and No PoR reply to the Sending Entity
Ciphering Key Identifier: Algorithm known implicitly by both entities
Key Identifier: Algorithm known implicitly by both entities
Toolkit Application Reference: Proprietary Toolkit Application
Counter: 1
Padding Counter: 0 (no padding is necessary)
Secure Data: 62 octets set to ‘DC’ (dummy data)
Coding:
|
Coding |
C0 |
11 |
10 |
01 |
96 |
11 |
02 |
70 |
00 |
00 |
4D |
00 |
|
0D |
00 |
00 |
00 |
00 |
BF |
FF |
00 |
00 |
00 |
00 |
00 |
|
|
01 |
00 |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
|
|
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
|
|
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
|
|
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
|
|
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
|
|
DC |
DC |
DC |
DC |
ENVELOPE: CELL BROADCAST DOWNLOAD 1.7
Logically:
Cell Broadcast Download
Device identities
Source device: Network
Destination device: UICC
Cell Broadcast page
Serial Number
Geographical scope: Cell wide, normal display mode
Message code: 1
Update number: 1
Message Identifier: "1001"
Data coding Scheme
Message Coding: 8 bit data (Message with User Data Header (UDH) structure)
Message class: Class 2 (U)SIM specific message
Page Parameter
Number of pages: 1
Page number: 1
Secured User Header (Content of message)
TP-UDHL 2
IEI (U)SIM Toolkit Security Headers
IEIL 0
Command Packet Length: 77
Command Header Identifier: 0
Command Header Length: 13
Security Parameter Indicator: No RC, CC or DS and No PoR reply to the Sending Entity
Ciphering Key Identifier: Algorithm known implicitly by both entities
Key Identifier: Algorithm known implicitly by both entities
Toolkit Application Reference: Proprietary Toolkit Application
Counter: 1
Padding Counter: 0 (no padding is necessary)
Secure Data: 62 octets set to ‘DC’ (dummy data)
Coding:
|
BER-TLV: |
D2 |
5E |
82 |
02 |
83 |
81 |
8C |
58 |
C0 |
11 |
10 |
01 |
|
96 |
11 |
02 |
70 |
00 |
00 |
4D |
00 |
0D |
00 |
00 |
00 |
|
|
00 |
BF |
FF |
00 |
00 |
00 |
00 |
00 |
01 |
00 |
DC |
DC |
|
|
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
|
|
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
|
|
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
|
|
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
|
|
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
PROACTIVE COMMAND: MORE TIME 1.2
Logically:
Command details
Command number: 1
Command type: MORE TIME
Command qualifier: "00"
Device identities
Source device: UICC
Destination device: ME
Coding:
|
BER-TLV: |
D0 |
09 |
81 |
03 |
01 |
02 |
00 |
82 |
02 |
81 |
82 |
TERMINAL RESPONSE: MORE TIME 1.2
Logically:
Command details
Command number: 1
Command type: MORE TIME
Command qualifier: "00"
Device identities
Source device: ME
Destination device: UICC
Result
General Result: Command performed successfully
Coding:
|
BER-TLV: |
81 |
03 |
01 |
02 |
00 |
82 |
02 |
82 |
81 |
83 |
01 |
00 |
27.22.5.2.5 Test requirement
The ME shall operate in the manner defined in expected sequences 1.1 to 1.7.
27.22.5.3 SMS-PP Data Download over IMS
27.22.5.3.1 Definition and applicability
See clause 3.2.2.
For IMS: That the UE correctly implemented the role of an SMS-over-IP receiver is tested in clause 18.2 of TS 34.229-1 [36].
27.22.5.3.2 Conformance requirement
The ME shall support the Proactive UICC: SMS-PP Data Download facility for SMS over IP as defined in the following technical specifications:
– TS 31.111 [15] clause 5, clause 7.1, clause 8.1, clause 8.7, clause 8.13 and clause 11.
– TS 31.115 [28] clause 4.
– TS 23.038 [7] clause 4.
– TS 34.229 [36], Annexes C.2, C.17 and C.18.
– TS 24.341 [37], clause 5.2.3.4.
27.22.5.3.3 Test purpose
To verify that the ME transparently passes the "data download via SMS Point-to-point" messages which have been received over IMS to the UICC.
To verify that the ME returns the RP-ACK message back to the E-USS/USS, if the UICC responds with ’90 00′, ’91 XX’, ’62 XX’ or ’63 XX’. In case of IMS the RP-ACK message is contained in the SIP MESSAGE for the SM delivery report.
To verify that the ME with an SMS-PP download feature implementation prior to Rel-11 returns the RP-ERROR message in the SIP MESSAGE for the SM delivery report to the E-USS/USS, if the UICC responds with ’62 XX’ or ’63 XX’ (while the ME with the Rel-11 or later implemention of this feature return an RP-ACK in this case). In case of IMS the RP-ERROR message is contained in the SIP MESSAGE for the SM delivery report.
To verify that the ME returns available response data from the UICC in the TP-User-Data element of the RP-ACK message back to the E-USS/USS. In case of IMS the RP-ACK message is contained in the SIP MESSAGE for the SM delivery report.
27.22.5.3.4 Method of Test
27.22.5.3.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 3.1 the ME is additionally connected to the E-USS.
For sequence 3.2 the ME is additionally connected to the USS.
27.22.5.3.4.2 Procedure
Expected Sequence 3.1 (SMS-PP Data Download over IMS, E-UTRAN)
Perform the "IMS related procedure 1" and continue with "Generic Test Procedure 1 (SMS-PP Data Download)" as defined in this clause as "Expected Sequence 3.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 3.2 (SMS-PP Data Download over IMS, UTRAN)
Perform the "IMS related procedure 1" and continue with "Generic Test Procedure 1 (SMS-PP Data Download)" as defined in this clause as "Expected Sequence 3.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
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 (SMS-PP Data Download) |
Generic Test Procedure 1 (SMS-PP Data Download)
|
Step |
Direction |
MESSAGE / Action |
Comments |
|
4 |
NWS → ME |
SMS-PP Data Download Message 3.1.1 |
See Note 1. |
|
5 |
ME → USER |
The ME shall not display the message or alert the user of a short message waiting. |
|
|
6 |
ME → UICC |
ENVELOPE: SMS-PP DOWNLOAD 3.1.1 |
|
|
7 |
UICC → ME |
SMS-PP Data Download UICC Acknowledgement 3.1.1 |
[SW1 / SW2 of ’90 00′] |
|
8 |
ME → NWS |
SMS-PP Data Download UICC Acknowledgement 3.1.1 in the TP-User-Data element of the RP-ACK message. The values of protocol identifier and data coding scheme in RP-ACK shall be as in the original message. |
See Note 2. |
|
9 |
NWS → ME |
SMS-PP Data Download Message 3.1.2 |
See Note 1. |
|
10 |
ME → USER |
The ME shall not display the message or alert the user of a short message waiting |
|
|
11 |
ME → UICC |
ENVELOPE: SMS-PP DOWNLOAD 3.1.2 |
|
|
12 |
UICC → ME |
PROACTIVE COMMAND PENDING: MORE TIME 3.1.1 |
[SW1 / SW2 of ’91 0B’] |
|
13 |
ME → NWS |
RP-ACK |
See Note 2. |
|
14 |
ME → UICC |
FETCH |
|
|
15 |
UICC → ME |
PROACTIVE COMMAND: MORE TIME 3.1.1 |
|
|
16 |
ME → UICC |
TERMINAL RESPONSE: MORE TIME 3.1.1 |
|
|
17 |
UICC → ME |
PROACTIVE UICC SESSION ENDED |
|
|
18 |
NWS → ME |
SMS-PP Data Download Message 3.1.3 |
See Note 1. |
|
19 |
ME |
The ME shall not display the message or alert the user of a short message waiting |
|
|
20 |
ME → UICC |
ENVELOPE: SMS-PP DOWNLOAD 3.1.3 |
|
|
21 |
UICC → ME |
SW1 / SW2 of ’90 00′ |
|
|
22 |
ME → NWS |
RP-ACK |
See Note 2. |
|
23 |
NWS → ME |
SMS-PP Data Download Message 3.1.1 |
See Note 1. |
|
24 |
ME → USER |
The ME shall not display the message or alert the user of a short message waiting. |
|
|
25 |
ME → UICC |
ENVELOPE: SMS-PP DOWNLOAD 3.1.1 |
|
|
26 |
UICC → ME |
SMS-PP Data Download UICC Acknowledgement 3.1.4 |
[SW1 / SW2 of ’62 xx’ or ’63 xx’] |
|
27 |
ME → NWS |
IF A.1/154_THEN SMS-PP Data Download UICC Acknowledgement 3.1.4 in the TP-User-Data element of the RP-ACK message. The values of protocol identifier and data coding scheme in RP-ACK shall be as in the original message. ELSE IF (NOT A.1/154) THENSMS-PP Data Download UICC Acknowledgement 3.1.4 in the TP-User-Data element of the RP-ERROR message. The values of protocol identifier and data coding scheme in RP-ERROR shall be as in the original message. |
See Note 2. See Note 3. |
|
28 |
NWS → ME |
SMS-PP Data Download Message 3.1.5 |
See Note 1. |
|
29 |
ME |
The ME shall not display the message or alert the user of a short message waiting |
|
|
30 |
ME → UICC |
ENVELOPE: SMS-PP DOWNLOAD 3.1.5 |
|
|
31 |
UICC → ME |
SW1 / SW2 of ’90 00′ |
|
|
32 |
ME → NWS |
RP-ACK |
See Note 2. |
|
33 |
USER → ME |
The ME is switched off |
|
|
Note 1: In case of IMS the SMS-PP Data Download Message is contained in the message body of the SIP MESSAGE. Note 2: In case of IMS the RP-ACK message is contained in the message body of the SIP MESSAGE. Note 3: In case of IMS the RP-ERROR message is contained in the message body of the SIP MESSAGE. |
|||
SMS-PP (Data Download) Message 3.1.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 "TestMessage 1"
Coding:
|
Coding |
04 |
04 |
91 |
21 |
43 |
7F |
16 |
89 |
10 |
10 |
00 |
00 |
|
00 |
00 |
0D |
54 |
65 |
73 |
74 |
4D |
65 |
73 |
73 |
61 |
|
|
67 |
65 |
20 |
31 |
ENVELOPE: SMS-PP DOWNLOAD 3.1.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 "TestMessage 1"
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 |
54 |
65 |
|
|
73 |
74 |
4D |
65 |
73 |
73 |
61 |
67 |
65 |
20 |
31 |
SMS-PP Data Download UICC Acknowledgement 3.1.1
|
Coding |
44 |
61 |
74 |
61 |
20 |
41 |
63 |
6B |
SMS-PP (Data Download) Message 3.1.2
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 "2143"
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 "TestMessage 2"
Coding:
|
Coding |
04 |
04 |
91 |
12 |
34 |
7F |
16 |
89 |
10 |
10 |
00 |
00 |
|
00 |
00 |
0D |
54 |
65 |
73 |
74 |
4D |
65 |
73 |
73 |
61 |
|
|
67 |
65 |
20 |
32 |
ENVELOPE: SMS-PP DOWNLOAD 3.1.2
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 "2143"
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 "TestMessage 2"
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 |
12 |
34 |
|
|
7F |
16 |
89 |
10 |
10 |
00 |
00 |
00 |
00 |
0D |
54 |
65 |
|
|
73 |
74 |
4D |
65 |
73 |
73 |
61 |
67 |
65 |
20 |
32 |
PROACTIVE COMMAND: MORE TIME 1.1.1
Logically:
Command details
Command number: 1
Command type: MORE TIME
Command qualifier: "00"
Device identities
Source device: UICC
Destination device: ME
Coding:
|
BER-TLV: |
D0 |
09 |
81 |
03 |
01 |
02 |
00 |
82 |
02 |
81 |
82 |
TERMINAL RESPONSE: MORE TIME 1.1.1
Logically:
Command details
Command number: 1
Command type: MORE TIME
Command qualifier: "00"
Device identities
Source device: ME
Destination device: UICC
Result
General Result: Command performed successfully
Coding:
|
BER-TLV: |
81 |
03 |
01 |
02 |
00 |
82 |
02 |
82 |
81 |
83 |
01 |
00 |
SMS-PP (Data Download) Message 3.1.3
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 "2233"
TP-PID (U)SIM Data download
TP-DCS
Coding Group Data Coding / Message Class
Message Coding 8 bit data
Message Class Class 2 (U)SIM Specific Message
TP-SCTS: 01/01/98 00:00:00 +0
TP-UDL 13
TP-UD "TestMessage 3"
Coding:
|
Coding |
04 |
04 |
91 |
22 |
33 |
7F |
F6 |
89 |
10 |
10 |
00 |
00 |
|
00 |
00 |
0D |
54 |
65 |
73 |
74 |
4D |
65 |
73 |
73 |
61 |
|
|
67 |
65 |
20 |
33 |
ENVELOPE: SMS-PP DOWNLOAD 3.1.3
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 "2233"
TP-PID (U)SIM Data download
TP-DCS
Coding Group Data Coding / Message Class
Message Coding 8 bit data
Message Class Class 2 (U)SIM Specific Message
TP-SCTS: 01/01/98 00:00:00 +0
TP-UDL 13
TP-UD "TestMessage 3"
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 |
22 |
33 |
|
|
7F |
F6 |
89 |
10 |
10 |
00 |
00 |
00 |
00 |
0D |
54 |
65 |
|
|
73 |
74 |
4D |
65 |
73 |
73 |
61 |
67 |
65 |
20 |
32 |
SMS-PP Data Download UICC Acknowledgement 3.1.4
|
Coding |
44 |
61 |
74 |
61 |
20 |
45 |
72 |
72 |
65 |
72 |
SMS-PP (Data Download) Message 3.1.5
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 user data header and a short message
TP-SRI A status report will not be returned to the SME
TP-OA
TON International number
NPI "ISDN / telephone numbering plan"
Address value "1234"
TP-PID (U)SIM Data download
TP-DCS
Coding Group Data Coding / Message Class
Message Coding 8 bit data
Message Class Class 2 (U)SIM Specific Message
TP-SCTS: 01/01/98 00:00:00 +0
TP-UDL 30
TP-UD
TP-UDHL 2
IEI (U)SIM Toolkit Security Headers
IEIL 0
SM (8 bit data)
Command Packet Length: 25
Command Header Identifier: 0
Command Header Length: 13
Security Parameter Indicator: No RC, CC or DS and No PoR reply to the Sending Entity
Ciphering Key Identifier: Algorithm known implicitly by both entities
Key Identifier: Algorithm known implicitly by both entities
Toolkit Application Reference: Proprietary Toolkit Application
Counter: 1
Padding Counter: 0 (no padding is necessary)
Secure Data: 10 octets set to ‘DC’ (dummy data)
Coding:
|
Coding |
44 |
04 |
91 |
21 |
43 |
7F |
F6 |
89 |
10 |
10 |
00 |
00 |
|
00 |
00 |
1E |
02 |
70 |
00 |
00 |
19 |
00 |
0D |
00 |
00 |
|
|
00 |
00 |
BF |
FF |
00 |
00 |
00 |
00 |
00 |
01 |
00 |
DC |
|
|
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
DC |
ENVELOPE: SMS-PP DOWNLOAD 3.1.5
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 user data header and a short message
TP-SRI A status report will not be returned to the SME
TP-OA
TON International number
NPI "ISDN / telephone numbering plan"
Address value "1234"
TP-PID (U)SIM Data download
TP-DCS
Coding Group Data Coding / Message Class
Message Coding 8 bit data
Message Class Class 2 (U)SIM Specific Message
TP-SCTS: 01/01/98 00:00:00 +0
TP-UDL 30
TP-UD
TP-UDHL 2
IEI (U)SIM Toolkit Security Headers
IEIL 0
SM (8 bit data)
Command Packet Length: 25
Command Header Identifier: 0
Command Header Length: 13
Security Parameter Indicator: No RC, CC or DS and No PoR reply to the Sending Entity
Ciphering Key Identifier: Algorithm known implicitly by both entities
Key Identifier: Algorithm known implicitly by both entities
Toolkit Application Reference: Proprietary Toolkit Application
Counter: 1
Padding Counter: 0 (no padding is necessary)
Secure Data: 10 octets set to ‘DC’ (dummy data)
Coding:
|
BER-TLV: |
D1 |
3E |
82 |
02 |
83 |
81 |
06 |
09 |
91 |
11 |
22 |
33 |
|
44 |
55 |
66 |
77 |
F8 |
8B |
2D |
44 |
04 |
91 |
21 |
43 |
|
|
7F |
F6 |
89 |
10 |
10 |
00 |
00 |
00 |
00 |
1E |
02 |
70 |
|
|
00 |
00 |
19 |
00 |
0D |
00 |
00 |
00 |
00 |
BF |
FF |
00 |
|
|
00 |
00 |
00 |
00 |
01 |
00 |
DC |
DC |
DC |
DC |
DC |
DC |
|
|
DC |
DC |
DC |
DC |
27.22.5.3.5 Test requirement
The ME supporting eFDD or eTDD shall operate in the manner defined in expected sequence 3.1.
The ME supporting UTRAN shall operate in the manner defined in expected sequence 3.2.
27.22.5.4 SMS-PP Data Download over SGs in E-UTRAN
27.22.5.4.1 Definition and applicability
See clause 3.2.2.
27.22.5.4.2 Conformance requirement
The ME shall support the Proactive UICC: SMS-PP Data Download facility for SMS over SGs as defined in the following technical specifications:
– TS 31.111 [15] clause 5, clause 7.1, clause 8.1, clause 8.7, clause 8.13 and clause 11.
– TS 31.115 [28] clause 4.
– TS 23.038 [7] clause 4.
– TS 24.301 [32] clause 5.6.3.1, 5.6.3.3 and 9.9.3.22
27.22.5.4.3 Test purpose
To verify that the ME transparently passes the "data download via SMS Point-to-point" messages to the UICC.
To verify that the ME returns the RP-ACK message back to the USS, if the UICC responds with ’90 00′, ’91 XX’, ’62 XX’ or ’63 XX’.
To verify that the ME with an SMS-PP download feature implementation prior to Rel-11 returns the RP-ERROR message back to the system Simulator, if the UICC responds with ’62 XX’ or ’63 XX’ (while the ME with the Rel-11 or later implemention of this feature return an RP-ACK in this case).
To verify that the ME returns the response data from the UICC back to the USS in the TP-User-Data element of the RP-ACK message, if the UICC returns response data’.
27.22.5.4.4 Method of Test
27.22.5.4.4.1 Initial conditions
The ME is connected to the USIM Simulator and connected to the E-USS/NB-SS.
The "data download via SMS-PP" service is available in the USIM Service Table.
27.22.5.4.4.2 Procedure
Expected Sequence 4.1 (SMS-PP Data Download over SGs, E-UTRAN)
Perform the "SMS over SGs related procedure" and continue with "Generic Test Procedure 1 (SMS-PP Data Download)" as defined in this clause 27.22.5.3.4.2 as "Expected Sequence 4.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 Profle 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 (SMS-PP Data Download) in clause 27.22.5.3.4.2 |
27.22.5.4.5 Test requirement
The ME shall operate in the manner defined in expected sequence 4.1.