TIA-1106-2007 Secured Packet Structure for CCAT Applications《CCAT应用的安全分组结构》.pdf

《TIA-1106-2007 Secured Packet Structure for CCAT Applications《CCAT应用的安全分组结构》.pdf》由会员分享，可在线阅读，更多相关《TIA-1106-2007 Secured Packet Structure for CCAT Applications《CCAT应用的安全分组结构》.pdf（22页珍藏版）》请在麦多课文档分享上搜索。

1、 TIA STANDARD Secured Packet Structure for CCAT Applications TIA-1106 May 2007 TELECOMMUNICATIONS INDUSTRY ASSOCIATION Representing the telecommunications industry in association with the Electronic Industries Alliance NOTICE TIA Engineering Standards and Publications are designed to serve the publi

2、c interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards

3、and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestic

4、ally or internationally. Standards and Publications are adopted by TIA in accordance with the American National Standards Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard

5、 or Publication. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulator

6、y limitations before its use. (From Project No. 3-0248, formulated under the cognizance of the TIA TR-45 Mobile (b) there is no assurance that the Document will be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or change

7、d in the standards development or any editing process. The use or practice of contents of this Document may involve the use of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IP

8、R consisting of patents and published pending patent applications are claimed and called to TIAs attention, a statement from the holder thereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the s

9、cope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing terms or conditions, which are instead left to the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warran

10、t or represent that procedures or practices suggested or provided in the Manual have been complied with as respects the Document or its contents. If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, develo

11、pment or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) then (i) TIA disclaims any duty or obligation to searc

12、h or investigate the records of any other SSO for IPR or letters of assurance relating to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent applications shall apply; and (

13、iii) Information as to claims of IPR in the records or publications of the other SSO shall not constitute identification to TIA of a claim of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certi

14、fy, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APP

15、ROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIAN

16、CE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING

17、 TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING

18、 NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-1106 2 1 Contents 2 1 INTRODU

19、CTION.4 3 2 SCOPE4 4 3 REFERENCES.5 5 4 DEFINITIONS, SYMBOLS, ABBREVIATIONS AND CODING CONVENTIONS 7 6 4.1 DEFINITIONS. 7 7 4.2 ABBREVIATIONS7 8 5 IMPLEMENTATION OF SMS-PP 8 9 5.1 STRUCTURE OF THE UDH IN A SECURED SHORT MESSAGE POINT-TO-POINT 8 10 5.2 STRUCTURE OF THE COMMAND PACKET CONTAINED IN A S

20、INGLE SHORT MESSAGE 11 POINT-TO-POINT. 8 12 5.3 A COMMAND PACKET CONTAINED IN CONCATENATED SHORT MESSAGES POINT-TO-13 POINT 10 14 5.4 STRUCTURE OF THE RESPONSE PACKET 11 15 5.5 A RESPONSE PACKET CONTAINED IN CONCATENATED SHORT MESSAGES POINT-TO-16 POINT 13 17 6 IMPLEMENTATION OF SMS BROADCAST .14 18

21、 19 TIA-1106 3 No text.1 TIA-1106 4 1 1 INTRODUCTION 2 The present document specifies the bearer specific part of secured packets structure. The 3 generic part is specified in ETSI TS 102 225 13. 4 5 2 SCOPE 6 The present document specifies the structure of the Secured Packets based on ETSI TS 102 7

22、 225 13. 8 The structure of the Secured Packets shall comply with the one defined in ETSI TS 102 225 9 13. The present document only contains additional requirements or explicit limitations for 10 CCAT applications. 11 It is applicable to the exchange of secured packets between an entity in a CDMA n

23、etwork 12 and an entity in the R-UIM/CSIM. 13 Secured Packets contain application messages to which certain mechanisms according to 14 11 have been applied. Application messages are commands or data exchanged between an 15 application resident in or behind the CDMA network and on the R-UIM/CSIM. The

24、 16 Sending/Receiving Entity in the CDMA network and the R-UIM/CSIM are responsible for 17 applying the security mechanisms to the application messages and thus turning them into 18 Secured Packets. 19 TIA-1106 5 1 3 REFERENCES 2 The following standards contain provisions that, through reference in

25、this text, constitute 3 provisions of this Standard. At the time of publication, the editions indicated were valid. 4 All standards are subject to revision, and parties to agreements based upon this 5 Standard are encouraged to investigate the possibility of applying the most recent 6 editions of th

26、e standards indicated below. ANSI and TIA maintain registers of currently 7 valid national standards published by them. 8 9 1 ETSI TS 102 221 “Smart Cards; UICC-Terminal interface; Physical and 10 logical characteristics (Release 7)“. 11 2 3GPP TS 31.101 “UICC-Terminal interface; Physical and logica

27、l 12 characteristics “. 13 3 3GPP TS 31.900 “SIM/USIM internal and external Interworking aspects” 14 4 TIA-1058-0, UICC-Terminal interface Physical and Logical characteristics 15 for cdma2000 Spread Spectrum Systems. 16 5 TIA-820-C, Removable User Identity Module for Spread Spectrum Systems, 17 6 TI

28、A-915-A, CDMA Card Application Toolkit (CCAT). 18 7 TIA-637-B, Short Message Service (SMS) for Wideband Spread Spectrum 19 Systems. 20 8 ETSI TS 101 220: “Smart cards; ETSI numbering system for 21 telecommunication application providers“. 22 9 3GPP TS 11.11, Release 99: “Specification of the Subscri

29、ber Identity 23 Module - Mobile Equipment Interface“ 24 10 3GPP TS 51.011, Release 4: “Specification of the Subscriber Identity 25 Module - Mobile Equipment Interface“ 26 11 ETSI TS 102 224: “Smart Cards; Security mechanisms for UICC based 27 Applications - Functional requirements“. 28 12 3GPP TS 23

30、.040: “Technical realization of the Short Message Service 29 (SMS)“. 30 13 ETSI TS 102 225: “Smart Cards; Secured packet structure for UICC based 31 applications“. 32 TIA-1106 6 14 ETSI TS 102 127: “Smart cards; Transport protocol for CAT applications; 1 Stage 2“. 2 15 TIA-1080-0, cdma2000 Applicati

31、on on UICC for Spread Spectrum Systems. 3 TIA-1106 7 1 4 DEFINITIONS, SYMBOLS, ABBREVIATIONS AND CODING CONVENTIONS 2 For the purposes of the present document, the definitions, symbols, and abbreviations 3 specified in ETSI TS 102 225 13, 7, 5,15 and the following apply. 4 4.1 DEFINITIONS 5 R-UIM: R

32、emovable User Identity Module residing on a non-UICC based platform as defined 6 in 5. 7 CSIM: cdma2000 Subscriber Identify Module specified in 15. A cdma20001Application 8 residing on the UICC, an IC card specified in 4. 9 Short Message: Information that may be conveyed by means of the SMS Service

33、as defined 10 in 7. 11 12 4.2 ABBREVIATIONS 13 14 IEI Information Element Identifier 15 IEIDL Information Element Identifier Data Length 16 IED Information Element Data 17 SM Short Message 18 SMS Short Message Service 19 SMS-PP Short Message Service Point-to-Point 20 21 1cdma2000is the trademark for

34、 the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of publication), cdma2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States. TIA-1106 8 1 5 IMP

35、LEMENTATION OF SMS-PP 2 5.1 Structure of the UDH in a Secured Short Message Point-to-Point 3 The coding of the SMS Deliver , SMS Submit Message and SMS User Acknowledgement User 4 Data subparameter shall indicate that the data is binary (8 bit data), and not 7 bit or 16 bit. 5 In order to invoke the

36、 UDH functionality of relevant SMS element, the HEADER_IND bit 6 shall be set as defined in 7. 7 However, in the case of a Response Packet originating from the R-UIM/UICC, due to the 8 inability of the R-UIM/UICC to indicate to an ME that the HEADER_IND bit should be set, 9 the Response Packet SMS w

37、ill not have the HEADER_IND bit set, and the Sending Entity 10 shall treat the Response Packet as if the HEADER_IND bit was set. 11 The generalized structure of the UDH in the Short Message element is contained in the User 12 Data part of the Short Message element and is described in TS 23.040 12. T

38、he Command 13 Packet and the Response Packet are partially mapped into this UDH structure. 14 Information Element Identifiers (IEIs) values range 70 - 7F are reserved in TS 23.040 12 15 for use in the present document and allocated as follows: 16 - 70 and 71 are specified in the present document 17

39、- values 72 - 7D are reserved for future use 18 - 7E and 7F are for proprietary implementations. 19 If a Response Packet (Response Header + Data) is too large to be contained in a single Short 20 Message (including the Response Header), it shall be concatenated according to 12. 21 If it is indicated

40、 in the SPI2 of a Command Packet to send back a PoR using SMS User 22 Acknowledgement and if the Response Packet is too large to be contained in a single SMS 23 User Acknowledgement - message, then: 24 One single Response Packet shall be sent back to the Sending Entity using SMS User 25 Acknowledgem

41、ent . This Response Packet: 26 Shall not contain any Additional response data, 27 Shall contain the Response Status Code set to “Actual response data to be sent using 28 SMS Submit“ (see Table 3), and 29 The security applied to this Response Packet shall be the one indicated in the SPI2 of 30 the Co

42、mmand Packet. 31 This shall be followed by a complete Response Packet, contained in one SMS Submit 32 element or in a concatenated Short Message composed of several SMS Submit elements. 33 5.2 Structure of the Command Packet Contained in a Single Short Message Point-to-34 Point 35 CPI identifies the

43、 Command Packet and indicates that the first portion of the SM (8 bit data) 36 contains the Command Packet Length (CPL), the Command Header Length (CHL) followed by 37 TIA-1106 9 the remainder of the Command Header: the Secured Data follows on immediately as the 1 remainder of the SM element. 2 The

44、relationship between the Command Packet and its inclusion in the UDH structure of a 3 single Short Message defined in TS 23.040 12 is as following: 4 5 CPI is mapped to IEIa defined in TS 23.040 12 and shall be set to 70. 6 IEDa defined in TS 23.040 12 shall be a null field and its length IEIDLa sha

45、ll be set 7 to 00. 8 The following Table 1 indicates the Command Packet contained in a single SMS-PP. It is a 9 particular implementation for single SMS-PP of the generic Command Packet structure 10 described in TS 102 225 13. 11 12 Table 1: Structure of the Command Packet Contained in the SM (8 bit

46、 data) 13 Command Packet Elements Length Description Command Packet Length 2 octets (see NOTE) Length of the Command Packet (CPL), coded over 2 octets, and shall not be coded as the length of BER-TLV data objects described in TS 101 220 8. Command Header Identifier Null field (CHI) Null field. Comma

47、nd Header Length 1 octet Length of the Command Header (CHL), coded over one octet, and shall not be coded as the length of BER-TLV data objects described in TS 101 220 8. SPI to RC/CC/DS in the Command Header Variable The remainder of the Command Header as described in TS 102 225 13. Secured Data Va

48、riable Applicative Message, including possible padding octets as described in TS 102 225 13. 14 NOTE: Whilst not absolutely necessary in this particular instance, this field is necessary 15 for the case where concatenated Short Message is employed (see section 5.3). 16 It is recognised that most che

49、cksum algorithms require input data in modulo 8 length. In 17 order to achieve a modulo 8 length of the data before the RC/CC/DS field in the Command 18 Header, the Command Packet Length and Command Header Length shall be included in the 19 calculation of RC/CC/DS if used. These fields shall not be ciphered. 20 The SPI shall be coded as specified in TS 102 225 13. The bit 6 of the second octet is used 21 for SMS only and shall be coded as followed: 22 23 TIA-1106 10 Secon