8 Implementation for HTTP
31.1153GPPRelease 17Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applicationsTS
The security for data exchange over TCP is provided by TLS. The HTTP protocol is used on top of TLS to provide encapsulation of the data and information about the receiving entity.
See ETSI TS 102 225 [9]
Annex A (normative):
USSD String format
For the purpose of UICC-based application, the USSD String shall be coded as follows:
Figure 6: USSD String format
The header of an USSD Message may contain two fields:
– A mandatory PFI field, which is coded on 1 byte. The PFI contains information on the format of the USSD String.
– An optional CCF field, which is coded on 3 bytes. The CCF field presence is indicated by the PFI.
The PFI is coded as follows.
|
B8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
|||||||||
|
X |
0 |
0 |
Proprietary Application Data format |
|||||||||||||
|
X |
0 |
1 |
Application Data formatted according to the present document. |
|||||||||||||
|
0 |
0 |
1 |
If b2 b1 = ’01’ (Application Data formatted according to the present document), then b3 shall be coded as follows: No CCF field |
|||||||||||||
|
1 |
0 |
1 |
CCF field present |
|||||||||||||
|
Reserved for future use |
||||||||||||||||
The usage of CCF field allows USSD Messages to be concatenated to form a longer message. The CCF field contains information set by the application so that the receiving entity is able to re‑assemble the received Ums in the correct order. Additionally, the CCF contains a reference number, which allows the receiving entity to discriminate between messages. The CCF octets shall be coded as follows.
Octet 1: Concatenated USSD Message reference number.
This octet shall contain a modulo-256 counter indicating the reference number for a particular USSD Message, Concatenated or not. This reference number shall remain constant for every USSD Message that makes up a particular Concatenated USSD Message.
Octet 2: Total number of USSD Messages in the Concatenated USSD Message.
This octet shall contain a value in the range 1 to 255 indicating the total number of USSD Messages constituting the Concatenated USSD Message. The value shall start at 1 and remain constant for every USSD Message that makes up the Concatenated USSD message. If the value is zero then the receiving entity shall ignore the whole USSD Message.
Octet 3: Sequence number of the current USSD Message.
This octet shall contain a value in the range 1 to 255 indicating the sequence number of a particular USSD Message within the Concatenated USSD Message. The value shall start at 1 and increment by one for every USSD Message sent within the Concatenated USSD Message. If the value is zero or the value is greater than the value in octet 2 then the receiving entity shall ignore the whole USSD Message.
The UM field contains the actual application data (e.g. secure Command/Response Packets coded according to the present document).
In each USSD String in a concatenated series, the PFI and CCF fields shall be present.
Annex B (informative):
Change History
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2005-06 |
CP-28 |
CP-050141 |
0005 |
– |
B |
Introduction of secured data download for USSD |
7.0.0 |
|
2007-06 |
CP-36 |
CP-070301 |
0007 |
1 |
F |
Correction of the reference to ETSI TS 102 225 |
7.1.0 |
|
2008-12 |
CP-42 |
CP-080907 |
0008 |
1 |
B |
Introduction of AES and deprecation of DES |
8.0.0 |
|
2009-03 |
– |
– |
– |
– |
– |
Figure 2 fixed |
8.0.1 |
|
2009-12 |
CT-46 |
CP-091011 |
0010 |
1 |
F |
References update |
8.1.0 |
|
2009-12 |
CT-46 |
CP-090995 |
0011 |
1 |
B |
Secured message structure for HTTP |
9.0.0 |
|
2011-03 |
SP-51 |
Automatic upgrade to Rel-10 |
10.0.0 |
||||
|
2012-03 |
CT-55 |
CP-120148 |
0014 |
1 |
A |
Correction to ETSI TS 102 225 reference |
10.1.0 |
|
2012-09 |
CT-57 |
CP-120623 |
0016 |
3 |
C |
Enhancements to the security of the SMS OTA download mechanisms |
11.0.0 |
|
2013-03 |
CT-59 |
CP-120148 |
0023 |
2 |
B |
Update of references to ETSI TS 102 225 and 3GPP TS 24.090 specifications |
12.0.0 |
|
2014-12 |
CT-66 |
CP-140961 |
0025 |
– |
F |
Correction of handling of Proof of Receipt |
12.1.0 |
|
2015-06 |
CT-68 |
CP-150388 |
0026 |
– |
F |
Correction of handling of Proof of Receipt |
12.2.0 |
|
2015-12 |
SP-70 |
– |
Automatic upgrade to Rel-13 |
13.0.0 |
|||
|
2017-03 |
SA-75 |
– |
– |
– |
– |
Automatic upgrade to Rel-14 |
14.0.0 |
|
2019-01 |
CT-81 |
– |
Automatic upgrade to Rel-15 |
15.0.0 |
|||
|
2020-03 |
CT#87e |
CP-200088 |
0034 |
– |
Secured packet usability in networks beyond GSM and 3G |
16.0.0 |
|
|
2022-04 |
CT#95e |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |