1、 TIA-4993 September 2014Network Enhancements for Machine to Machine (M2M) NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of product
2、s, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling products not conforming to such
3、Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards and Publications are adopted by TIA in accordance with the American National Standards Institute (ANSI) patent
4、 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 or Publication. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements.
5、 It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. Any use of trademarks in this document are for information purposes and do not constitute an endorsement by TIA or
6、this committee of the products or services of the company. (From Project No. TIA-PN-4993, 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
7、may be amended, modified or changed 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
8、 or investigation for IPR. When IPR 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
9、investigate or inquire into, the scope 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-d
10、iscriminatory. TIA does not warrant 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”)
11、engaged in the formulation, development 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 Procedures for American National Standards) then (i)
12、 TIA disclaims any duty or obligation to search 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 TIA Procedures for American National Standards Annex C.1.2.3) of Essent
13、ial Patent(s) and published pending patent applications shall apply; and (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 o
14、r monitor compliance with the contents of the Document. TIA does not certify, 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
15、ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS 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
16、AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE 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 LI
17、ABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING 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),
18、WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING 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 PU
19、BLISHED BY TIA WITHOUT SUCH LIMITATIONS. 3GPP2 X.S0068-0 v1.0 REVISION HISTORY Revision Date Comments Rev 0 v1.0 July 2014 Initial release of the specification. 3GPP2 X.S0068-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 4
20、3 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 i Network Enhancements for Machine to Machine (M2M) CONTENTS 1 Introduction 1 1.1 Scope 1 1.2 Requirements Terminology . 1 1.3 Normative References 1 2 Definitions and Abbreviations . 2 2.1 Definitions . 2 2.1.1 Symbols and Abbreviations . 3 3 M2M Ar
21、chitecture 5 3.1 General Concept 5 3.2 Architectural Model for CDMA2000 6 3.3 Network Entities 6 3.4 Reference Points 7 3.5 Protocol Descriptions . 7 3.5.1 User Plane (using IP) . 7 3.5.2 Control Plane . 8 3.5.2.1 Control Plane for Device Trigger Using SMS . 8 3.5.2.2 Control Plane for Device Trigge
22、r Using IP 9 3.5.2.3 Control Plane between AAA and M2M-IWF 9 4 Feature descriptions and information flows . 10 4.1 M2M authentication . 11 4.1.1 EAP-Re-authentication Protocol (ERP) using regular PPP . 11 4.2 M2M triggering 13 4.2.1 Tsp interface call flow . 13 4.2.2 Point to point device triggering
23、 . 15 4.2.2.1 SMS on the common channel 15 4.2.2.2 SMS on the traffic channel 16 4.2.2.3 Device Trigger using IP Interface 17 4.2.3 Broadcast device triggering . 19 5 Procedures and protocols . 21 5.1 Security 21 5.1.1 Fast Re-authentication using ERP . 21 5.1.1.1 Key Hierarchy for Access Authentica
24、tion 22 5.1.1.2 MS Requirements 22 5.1.1.3 PDSN Requirements 23 3GPP2 X.S0068-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 ii 5.1.2 VAAA Requirements . 23 5.1.2.1 RADIUS
25、23 5.1.2.2 Diameter 26 5.1.2.3 HAAA Requirements 27 5.2 Device Trigger . 27 5.2.1 M2M-IWF Requirements 27 5.2.1.1 Support of Tsp interface 28 5.2.1.2 Support of M1 interface 28 5.2.1.3 Support of M2 Interface 35 5.2.1.4 Support of Device Trigger Delivery 37 5.2.2 AAA Requirements . 37 5.2.3 MS Requi
26、rements 37 5.2.4 MC Requirements 37 Annex A Tsp Parameters Supported for cdma2000 Network (Informative) . 38 3GPP2 X.S0068-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 ii
27、i LIST OF FIGURES Figure 1 Enhanced Network Architecture to Support M2M . 6 Figure 2 User plane protocol 7 Figure 3 Control plane protocol (SMS-MC) . 8 Figure 4 Control plane protocol (TCP) . 9 Figure 5 Control plane protocol (AAA-M2M-IWF) . 9 Figure 6 EAP-Re-authentication Protocol (ERP) using regu
28、lar PPP 11 Figure 7 Tsp Interface Call Flow 13 Figure 8 Point-to-Point M2M Device Triggering via Common Channel . 15 Figure 9 Point-to-Point M2M Device Triggering via Traffic Channel . 16 Figure 10 Device trigger using IP interface 18 Figure 11 Broadcast M2M Device Triggering 19 Figure 12 Key hierar
29、chy for access authentication . 22 Figure 13 Key-Request VSA 24 Figure 14 Key-Response VSA 25 3GPP2 X.S0068-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 iv LIST OF TABLES
30、 Table 1 Additional RADIUS Attributes between VAAA and HAAA for Access Authentication and Authorization used for ERP 24 Table 2 Additional RADIUS Attributes between PDSN and VAAA for Access Authentication and Authorization used for ERP 24 Table 3 Additional Diameter AVPs between VAAA and PDSN during
31、 Access Authentication and Authorization using ERP 26 Table 4 Command-Code values for M1 28 Table 5 M1 specific Diameter AVPs . 30 Table 6 AAA-Cause 33 Table 7 MAP Parameters for M2M; P2P 35 Table 8 MAP Parameters for M2M; Broadcast . 36 Table 9 Support of Tsp Specific Diameter AVPs for cdma2000 . 3
32、8 Table 10 Support of Tsp Re-Used Diameter AVPs for cdma2000 39 3GPP2 X.S0068-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 v FOREWORD This foreword is not part of this do
33、cument. This document was prepared by the Third Generation Partnership Project 2 (3GPP2) TSG-SX Working Group. This document is a new specification. This document is subject to change following formal approval procedures. Should this document be modified in the future, it will be re-released with a
34、change-of-release date and an identifying change in version number as follows: X.S0068-X-n where: X: a numerical or uppercase alphabetic character A, B, C, that indicates the revision level; n: a numeric string 1, 2, 3, that indicates the point release level. 3GPP2 X.S0068-0 v1.0 1 2 3 4 5 6 7 8 9 1
35、0 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 vi This page is intentionally left blank.3GPP2 X.S0068-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
36、 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 1 1 Introduction This document specifies the network enhancements to support M2M in cdma20001. 1.1 Scope This document defines the Stage 2 service descriptions, call flows and normative Stage 3 procedures for the network
37、enhancements to support M2M in HRPD, and cdma2000 1x circuit-switched. 1.2 Requirements Terminology “Shall” and “shall not” identify requirements to be followed strictly to conform to this document and from which no deviation is permitted. “Should” and “should not” indicate that one of several possi
38、bilities is recommended as particularly suitable, without mentioning or excluding others, that a certain course of action is preferred but not necessarily required, or that (in the negative form) a certain possibility or course of action is discouraged but not prohibited. “May” and “need not” indica
39、te a course of action permissible within the limits of the document. “Can” and “cannot” are used for statements of possibility and capability, whether material, physical or causal. 1.3 Normative References This section provides references to other specifications and standards that are necessary to i
40、mplement this document. References are either specific (identified by date of publication, revision identifier, and version number) or non-specific. For a specific reference, subsequent revisions may not apply. For a non-specific reference, the latest revision applies. X.S0011 3GPP2: X.S0011-E v1.0,
41、 “cdma2000 Wireless IP Network Standard”, November 2009. TS 23.682 3GPP: TS 23.682, Architecture enhancements to facilitate communications with packet data networks and applications (Release 11). TS 23.040 3GPP: TS 23.040, Technical realization of the short message service (SMS) (Release 11). TS 29.
42、368 3GPP: TS 29.368, Tsp interface protocol between the MTC Interworking Function (MTC-IWF) and Service Capability Server (SCS) (Release 11). TR 23.888 3GPP: TS 23.888, System improvements for Machine-Type Communication (MTC) (Release 11). 1cdma2000is the trademark for the technical nomenclature for
43、 certain specifications and standards of the Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of publication), cdma2000is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States. 3GPP2 X.S0068-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13
44、 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 2 C.S0015 3GPP2: C.S0015-C, Short Message Service (SMS) for Wideband Spread Spectrum Systems, November 2012. C.R1001 3GPP2: C.R1001-I, Administration of Paramete
45、rs Value Assignments for cdma2000 Spread Spectrum Standards, September 2013. X.S0004-550 3GPP2: X.S0004-550-E, Mobile Application Part (MAP) Parameters Signaling Protocols, July 2009. X.S0004-641 3GPP2: X.S0004-641-E, Mobile Application Part (MAP) SMS, July 2007. A.S0013 3GPP2: A.S0013-D v4.0, “Inte
46、roperability Specification (IOS) for cdma2000Access Network Interface Part 3 Features”, August 2012. TS 23.003 3GPP: TS 23.003, “Numbering, addressing and identification”, (Release 11). Rec E.164 ITU-T: Rec E.164, “The international public telecommunication numbering plan”, November 2010. TS 29.002
47、3GPP: TS 29.002, “Mobile Application Part (MAP) specification”, (Release 11). TS 29.329 3GPP: TS 29.329, “Sh interface based on Diameter protocol; Protocol details” (Release 11)”. TS 29.336 3GPP: TS 29.336, “Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks
48、and applications”. RFC 3588 IETF: RFC 3588, “Diameter Based Protocol”. RFC 3748 IETF: RFC 3748, “Extensible Authentication Protocol (EAP)”. RFC 4006 IETF: RFC 4006, “Diameter Credit Control Application”. RFC 4072 IETF: RFC 4072, “Diameter Extensible Authentication Protocol (EAP) Application”. RFC 52
49、95 IETF: RFC 5295, “Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK)”. RFC 6696 IETF: RFC 6695, “EAP Extensions for the EAP Re-authentication Protocol (ERP)”. RFC 6942 IETF: RFC 6942, “Diameter Support for the EAP Re-authentication Protocol (ERP)”. 2 Definitions and Abbreviations 2.1 Definitions Machine to Machine (M2M) A form of data communication that involves one or more entities that do not necessarily require human interaction. MTC is synonymous with “M2M Communication”. 3GP
