7.1.1 SMS-PP DATA DOWNLOAD
Definition and Applicability
The ME shall support the SMS-PP-DATA DOWNLOAD command as defined in section 7.1 of [1].
All sequences of this test case are applicable for all MEs supporting CDMA Card Application
Toolkit enabled UICCs.
SEQ 3 and SEQ 5 are applicable for MEs supporting the R-UIM.
SEQ 4 and SEQ 6 are applicable for MEs supporting the CSIM.
In case an ME not supporting the option “ME supports display capability” [Table A.1/59] is
tested the display or the non-display of any alpha identifier, text string or icon shall be treated
as successfully verified.
Conformance Requirement
CR 1
Verify that when the ME receives a Short Message with Teleservice Identifier = Card
Application Toolkit Protocol Teleservice (CATPT), the ME transparently passes the
CDMA SMS TPDU parameters from the network using the ENVELOPE(SMS-PP
DATA DOWNLOAD) command to the UICC.
CR 2
Verify that the ME shall not display the contents of the message or alert the user
that there is a short message waiting when receiving any short message CATPT.
CR 3
Verify that the ME acknowledges the receipt of the short message CATPT using
SMS User Acknowledgment message to the network after receiving status words ‘90
00’ from the UICC in response to the SMS-PP DATA DOWNLOAD command.
CR 4
Verify that the ME sends back an SMS User Acknowledgment message to the
network with the User Response Code value “Destination busy”, after receiving
status words ’93 00’ from the UICC as response to SMS-PP DATA DOWNLOAD
command.
CR 5
Verify that the ME includes the UICC Acknowledgment data in the User
Data field of the SMS User Acknowledgment message that will be sent back
to the network, after receiving status words ‘9F XX’ from the R-UIM as
response to SMS-PP DATA DOWNLOAD command.
CR 6
Verify that the ME includes the UICC Acknowledgment data in the User
Data field of the SMS User Acknowledgment message that will be sent back
to the network, after receiving status words ’61 XX’ from the UICC as
response to SMS-PP DATA DOWNLOAD command.
CR 7
Verify that the ME includes the UICC Acknowledgment data in the User
Data field of the SMS User Acknowledgment message, after receiving status
words ‘9E XX’ from the R-UIM as a response to SMS-PP DATA DOWNLOAD
command and with the User Response Code set to “Other terminal
problem”.
CR 8
Verify that the ME includes the UICC Acknowledgment data in the User
Data field of the SMS User Acknowledgment message, after receiving status
words ‘63 XX’ or “62 XX” from the CSIM as a response to SMS-PP DATA
DOWNLOAD command and with the User Response Code set to “Other
terminal problem”.
Test Purpose
The purpose of the test is to verify that the ME complies with the above requirements.
Method of Test
7.1.1.4.1
Initial Conditions
The common initial conditions as defined in section 2.1 do apply.
7.1.1.4.2
Procedure
SEQ 1: SMS-PP DATA DOWNLOAD, Successful
Step Direction
MESSAGE / Action
Comments
1.
NS → ME
Data Burst Message (SMS-PP
DATA DOWNLOAD
The short message contains CATPT
teleservice and CDMA SMS TPDU.
2.
ME → CS
ENVELOPE: SMS-PP DATA
DOWNLOAD
[CR1/CR2]
3.
CS → ME
SW1=’90’ SW2 = ‘00’
Normal ending of the command
4.
ME → NS
Data Burst Message (SMS User The UICC Acknowledgment is empty. [CR3]
Acknowledgment Message)
SMS-PP DATA DOWNLOAD (Step 1):
Logically:
CDMA SMS TPDU
‘48’ CDMA-SMS TPDU Tag
Length
‘28’
SMS_MSG_TYPE
‘00’ SMS Point-to-Point
PARAMETER_ID
‘00’ Teleservice Identifier
PARAMETER_LEN
‘02’
IDENTIFIER
’10 07’ Card Application Toolkit Protocol Teleservice
Address Parameters:
PARAMETER_ID
‘02’ Originating Address
PARAMETER_LEN
‘06’
DIGIT_MODE
‘0’ Using the binary representation of the DTMF digits
NUMBER_MODE
‘0’ Specifies an address using the definitions in ANSI T1.607
NUM_FIELDS
‘08’
CHARi
’98 86 88 24’ Address digits
RESERVED
‘000000’
Bearer Reply Option:
PARAMETER_ID
‘06’ Bearer Reply Option
PARAMETER_LEN
‘01’ SMS message parameter length
REPLY_SEQ
‘000000’
RESERVED
‘00’
Bearer Data:
PARAMETER_ID
‘08’ Bearer Data
PARAMETER_LEN
‘16’
SUBPARAMETER_ID
‘00’ Message Identifier
SUBPARAMETER_LEN
‘03’
MESSAGE_TYPE
‘0001’ Deliver (mobile-terminated only)
MESSAGE_ID
’00 21’ Message identifier
HEADER_IND
‘0’ User Data subparameter field doesn’t include the User
Data header
RESERVED
‘000’
SUBPARAMETER_ID
‘01’ User Data
SUBPARAMETER_LEN
‘09’
MSG_ENCODING
‘00000’ Octet, unspecified
NUM_FIELDS
‘07’
CHARi
“Inc SMS” Characters
RESERVED
‘000’
SUBPARAMETER_ID
‘08’ Priority Indicator
SUBPARAMETER_LEN
‘01’
PRIORITY
‘00’ Normal
RESERVED
‘000000’
Coding in Hex:
48
01
02
28
00
9A
00
08
6A
00
16
98
02
00
08
10
03
01
07
10
00
02
02
08
06
10
01
ENVELOPE: SMS-PP DATA DOWNLOAD (Step 2)
02
01
00
26
09
21
00
A2
3C
09
4B
00
73
06
19
Logically:
Device identities:
Source device:
Network
Destination device:
UICC
CDMA SMS TPDU
‘48’ CDMA-SMS TPDU Tag
Length
‘28’
SMS_MSG_TYPE
‘00’ SMS Point-to-Point
PARAMETER_ID
‘00’ Teleservice Identifier
PARAMETER_LEN
‘02’
IDENTIFIER
’10 07’ Card Application Toolkit Protocol Teleservice
Address Parameters:
PARAMETER_ID
‘02’ Originating Address
PARAMETER_LEN
‘06’
DIGIT_MODE
‘0’ Using the binary representation of the DTMF digits
NUMBER_MODE
‘0’ Specifies an address using the definitions in ANSI T1.607
NUM_FIELDS
‘08’
CHARi
’98 86 88 24’ Address digits
RESERVED
‘000000’
BEARER Reply Option:
PARAMETER_ID
‘06’ Bearer Reply Option
PARAMETER_LEN
‘01’
REPLY_SEQ
‘000000’ Reply sequence number
RESERVED
‘00’
PARAMETER_ID
‘08’ Bearer Data
PARAMETER_LEN
‘16’
SUBPARAMETER_ID
‘00’ Message Identifier
SUBPARAMETER_LEN
‘03’
MESSAGE_TYPE
‘0001’ Deliver (mobile-terminated only)
MESSAGE_ID
’00 21’
HEADER_IND
‘0’ User Data subparameter field doesn’t include the User Data
header
RESERVED
‘000’
User Data:
SUBPARAMETER_ID
‘01’ User Data
SUBPARAMETER_LEN
‘09’
MSG_ENCODING
‘00000’ Octet, unspecified
NUM_FIELDS
‘07’
CHARi
“Inc SMS” Characters
RESERVED
‘000’
SUBPARAMETER_ID
‘08’ Priority Indicator
SUBPARAMETER_LEN
‘01’
PRIORITY
‘00’ Normal
RESERVED
‘000000’
Coding in Hex:
D1
26
09
2E
21
00
82
A2
3C
02
09
4B
83
00
73
81
06
19
48
01
02
28
00
9A
00
08
6A
00
16
98
02
00
08
10
03
01
07
10
00
02
02
08
06
10
01
SMS User Acknowledgment (Step 4):
Logically:
Message Identifier:
SUBPARAMETER_ID
‘00’
SUBPARAMETER_LEN
‘03’
MESSAGE_TYPE
‘0101’ User Acknowledgment
MESSAGE_ID
’00 00’
HEADER_IND
‘0’
RESERVED
‘000’
Coding in Hex:
00
03
50
00
00
SEQ 2: SMS-PP DATA DOWNLOAD, Card continuously busy
Step Direction
MESSAGE / Action
Comments
1.
NS → ME
Data Burst Message (SMS-PP
DATA DOWNLOAD
The short message contains CATPT
teleservice and CDMA SMS TPDU.
2.
ME → CS
ENVELOPE: SMS-PP DATA
DOWNLOAD
[CR1/CR2]
3.
CS → ME
SW1=’93’ SW2 = ‘00’
Card Application Toolkit is busy.
02
01
00
Step Direction
MESSAGE / Action
4.
If the ME is configured to retry,
after the completion of step 3
it may return to step 2.
5.
ME → NS
Comments
Data Burst Message (SMS User The UICC Acknowledgment and destination
Acknowledgment Message)
busy information are included in the
message. [CR4]
SMS-PP DATA DOWNLOAD (Step 1):
Same data as SEQ 1, Step 1.
ENVELOPE: SMS-PP DATA DOWNLOAD (Step 2):
Same data as SEQ 1, Step 2.
SMS User Acknowledgment (Step 5):
Logically:
Message Identifier:
SUBPARAMETER_ID
‘00’
SUBPARAMETER_LEN
‘03’
MESSAGE_TYPE
‘0101’ User Acknowledgment
MESSAGE_ID
’00 00’
HEADER_IND
‘0’
RESERVED
‘000’
User response code:
SUBPARAMETER_ID
‘02’
SUBPARAMETER_LEN
‘01’
RESPONSE_CODE
33 Destination busy
Coding in Hex:
00
03
50
00
02
01
21
SEQ 3: SMS-PP DATA DOWNLOAD ‘9F XX’, Successful, with UICC Acknowledgment included
Step Direction
MESSAGE / Action
Comments
1.
NS → ME
Data Burst Message (SMS-PP
DATA DOWNLOAD
The short message contains CATPT
teleservice and CDMA SMS TPDU.
2.
ME → CS
ENVELOPE: SMS-PP DATA
DOWNLOAD
[CR1/CR2]
3.
CS → ME
SW1=’9F’ SW2 = ‘09’
The ME shall send a GET RESPONSE
command header to the CS.
Step Direction
MESSAGE / Action
Comments
4.
ME → CS
GET RESPONSE
5.
CS → ME
‘53 50 4F 4E 47 45 42 4F 42’
6.
ME → NS
Data Burst Message (SMS User The UICC Acknowledgment is included in
Acknowledgment Message)
the message. [CR5]
“SPONGEBOB“
SMS-PP DATA DOWNLOAD (Step 1):
Same data as SEQ 1, Step 1.
ENVELOPE: SMS-PP DATA DOWNLOAD (Step 2):
Same data as SEQ 1, Step 2.
SMS User Acknowledgment (Step 6):
Logically:
Message Identifier:
SUBPARAMETER_ID
‘00’
SUBPARAMETER_LEN
‘03’
MESSAGE_TYPE
‘0101’ User Acknowledgment
MESSAGE_ID
’00 00’
HEADER_IND
‘0’
RESERVED
‘000’
User Data:
SUBPARAMETER_ID
‘01’ User Data
SUBPARAMETER_LEN
‘0B’
MSG_ENCODING
‘00000’ Octet, unspecified
NUM_FIELDS
‘09’
CHARi
“SPONGEBOB”
RESERVED
‘000’
Coding in Hex:
00
7A
03
10
50
00
00
01
0B
00
4A
9A
82
7A
72
3A
2A
12
SEQ 4: SMS-PP DATA DOWNLOAD ‘61 XX’, Successful, with UICC Acknowledgment included
Step Direction
MESSAGE / Action
Comments
1.
Data Burst Message (SMS-PP
DATA DOWNLOAD
The short message contains CATPT
teleservice and CDMA SMS TPDU.
NS → ME
Step Direction
MESSAGE / Action
Comments
2.
ME → CS
ENVELOPE: SMS-PP DATA
DOWNLOAD
[CR1/CR2]
3.
CS → ME
SW1=’61’ SW2 = ‘09’
The ME shall send a GET RESPONSE
command header to the CS.
4.
ME → CS
GET RESPONSE
5.
CS → ME
‘53 50 4F 4E 47 45 42 4F 42’
6.
ME → NS
Data Burst Message (SMS User The UICC Acknowledgment is included in
Acknowledgment Message)
the message. [CR6]
“SPONGEBOB“
SMS-PP DATA DOWNLOAD (Step 1):
Same data as SEQ 1, Step 1.
ENVELOPE: SMS-PP DATA DOWNLOAD (Step 2):
Same data as SEQ 1, Step 2.
SMS User Acknowledgment (Step 6):
Same data as SEQ 3, Step 6.
SEQ 5: SMS-PP DATA DOWNLOAD ‘9E XX’, Unsuccessful, with UICC Acknowledgment and
other terminal problem included
Step Direction
MESSAGE / Action
Comments
1.
NS → ME
Data Burst Message (SMS-PP
DATA DOWNLOAD
The short message contains CATPT
teleservice and CDMA SMS TPDU.
2.
ME → CS
ENVELOPE: SMS-PP DATA
DOWNLOAD
[CR1/CR2]
3.
CS → ME
SW1=’9E’ SW2 = ‘08’
Data download error that requires the ME
to send a GET RESPONSE command header
to the CS.
4.
ME → CS
GET RESPONSE
5.
CS → ME
‘54 68 65 20 42 4C 4F 42’
6.
ME → NS
Data Burst Message (SMS User The UICC Acknowledgment and other
Acknowledgment Message + terminal problem are included in the
other terminal problem)
message. [CR7]
SMS-PP DATA DOWNLOAD (Step 1):
Same data as SEQ 1, Step 1.
ENVELOPE: SMS-PP DATA DOWNLOAD (Step 2):
Same data as SEQ 1, Step 2.
“The BLOB“
SMS User Acknowledgment (Step 6):
Logically:
Message Identifier:
SUBPARAMETER_ID
‘00’
SUBPARAMETER_LEN
‘03’
MESSAGE_TYPE
‘0101’ User Acknowledgment
MESSAGE_ID
’00 00’
HEADER_IND
‘0’
RESERVED
‘000’
User Data:
SUBPARAMETER_ID
‘01’ User Data
SUBPARAMETER_LEN
‘0B’
MSG_ENCODING
‘00000’ Octet, unspecified
NUM_FIELDS
‘08’
CHARi
“The BLOB”
RESERVED
‘000’
User response code:
SUBPARAMETER_ID
‘02’
SUBPARAMETER_LEN
‘01’
RESPONSE_CODE
39 Other terminal problem
Coding in Hex:
00
10
03
02
50
01
00
27
00
01
0B
00
42
83
43
29
02
12
62
7A
SEQ 6: SMS-PP DATA DOWNLOAD ‘62 XX’ or ‘63 XX’, Unsuccessful, with UICC
Acknowledgment and other terminal problem included
Step Direction
MESSAGE / Action
Comments
1.
NS → ME
Data Burst Message (SMS-PP
DATA DOWNLOAD
The short message contains CATPT
teleservice and CDMA SMS TPDU.
2.
ME → CS
ENVELOPE: SMS-PP DATA
DOWNLOAD
[CR1/CR2]
3.
CS → ME
SW1/SW2 = ’62 08’ or ’63 08’
Data download error that requires the ME
to send a GET RESPONSE command header
to the CS.
4.
ME → CS
GET RESPONSE
Step Direction
MESSAGE / Action
Comments
5.
CS → ME
‘54 68 65 20 42 4C 4F 42’
“The BLOB“
6.
ME → NS
Data Burst Message (SMS User The UICC Acknowledgment and other
Acknowledgment Message + terminal problem are included in the
other terminal problem)
message. [CR8]
SMS-PP DATA DOWNLOAD (Step 1):
Same data as SEQ 1, Step 1,
ENVELOPE: SMS-PP DATA DOWNLOAD (Step 2):
Same data as SEQ 1, Step 2.
SMS User Acknowledgment (Step 6):
Same data as SEQ 5, Step 6.