1、 TIA-4984 January 2014Interoperability Specification (IOS) for cdma2000Machine to Machine (M2M) Communications NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating intercha
2、ngeability 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 and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or sel
3、ling 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 domestically or internationally. Standards and Publications are adopted by TIA in accordance with the American Natio
4、nal 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 or Publication. This Standard does not purport to address all safety problems associated with its use or al
5、l 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 regulatory limitations before its use. (From Project No. TIA-PN-4984, formulated under the cognizance of the TIA TR-4
6、5 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 changed in the standards development or any editing process. The use or practice of contents of this Document
7、 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 IPR consisting of patents and published pending patent applications are claimed and called to TIAs attent
8、ion, 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 scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing term
9、s 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 warrant or represent that procedures or practices suggested or provided in the Manual have been complied with
10、 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, development or publication of standards (whether designated as a standard, specification, recommendation or o
11、therwise), 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 search or investigate the records of any other SSO for IPR or letters of assurance relating to any such Norm
12、ative 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 (iii) Information as to claims of IPR in the records or publications of the other SSO shall not constitu
13、te 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 certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance wi
14、th 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 APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD
15、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 COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR
16、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 TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIA
17、L, 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 NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE F
18、OREGOING 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-4984 Revision History Date Revision Description December 2013 A.S0025-0 v1.0. Initial revision. For features supported, refer to sec
19、tion 1.1. TIA-4984 (This page intentionally left blank) TIA-4984 Table of Contents 1 Foreword iv 2 1 Introduction . 1-1 3 1.1 Overview . 1-1 4 1.1.1 Purpose 1-1 5 1.1.2 Scope . 1-1 6 1.1.3 Document Convention 1-1 7 1.2 References . 1-1 8 1.2.1 Normative References . 1-1 9 1.2.2 Informative Reference
20、s . 1-2 10 1.3 Terminology 1-2 11 1.3.1 Acronyms 1-2 12 1.3.2 Definitions 1-3 13 1.4 Architecture 1-3 14 1.5 M2M IOS Assumptions 1-3 15 1.6 Feature Descriptions . 1-3 16 1.6.1 1x Device Capability. 1-3 17 2 M2M IOS Interfaces . 2-1 18 2.1 cdma2000 1x Message Requirements for M2M . 2-1 19 2.1.1 Devic
21、e Capability . 2-1 20 2.2 HRPD Message Requirements for M2M 2-1 21 3 M2M IOS Message Flows 3-1 22 3.1 cdma2000 1x Message Flows for M2M . 3-1 23 3.1.1 Identification of M2M Device Capability . 3-1 24 3.1.1.1 MS Initiated Location Registration . 3-1 25 3.1.1.2 Network Initiated Location Registration
22、. 3-2 26 3.1.1.3 MS Initiated PDSI Setup - Packet Data Session is Dormant or Inactive 3-3 27 3.1.1.4 Network Initiated PDSI Reactivation when the Packet Data Session is Dormant 3-5 28 3.1.1.5 Network Initiated PDSI Reactivation via DCA (Dormant Packet Data, SCCP 29 Maintained) . 3-7 30 3.1.2 M2M Pow
23、er Down Indication 3-9 31 3.1.2.1 Active MS Release to Dormant State with Power Down Indication 3-9 32 3.1.2.2 Dormant MS Power Down 3-10 33 3.2 HRPD Message Flows for M2M 3-10 34 4 Signaling Enhancements for M2M . 4-1 35 4.1 cdma2000 1x Signaling Enhancements for M2M . 4-1 36 i TIA-4984 4.1.1 Devic
24、e Capability . 4-1 1 4.2 HRPD Signaling Enhancements for M2M 4-1 2 3 4 ii TIA-4984 Table of Figures 1 2 Figure 3.1.1.1-1 MS Location Registration . 3-1 3 Figure 3.1.1.2-1 Network Location Registration . 3-2 4 Figure 3.1.1.3-1 MS Initiated PDSI Setup - Packet Data Session is Dormant or Inactive 3-3 5
25、 Figure 3.1.1.4-1 Network Initiated PDSI Reactivation - Packet Data Session is Dormant . 3-5 6 Figure 3.1.1.5-1 Network Initiated PDSI Reactivation via DCA 3-7 7 Figure 3.1.2.1-1 Active MS Release to Dormant State with Power Down Indication 3-9 8 Figure 3.1.2.2-1 Dormant MS Power Down 3-10 9 10 11 1
26、2 iii TIA-4984 Foreword 1 This foreword is not part of this document. 2 This document describes the cdma20001Radio Access Network (RAN) protocols and procedures opti-3 mized for Machine to Machine (M2M) communications. 4 This document was produced by TSG-AC of the Third Generation Partnership Projec
27、t 2. This document 5 was developed in accordance with the procedural guidelines of 3GPP2 and its Organizational Partners, 6 and represents the consensus position of these groups. 7 8 1cdma2000is the trademark for the technical nomenclature for certain specifications and standards of the Organization
28、al 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. iv TIA-4984 1 Introduction 1 2 1.1 Overview 3 This document includes a description of the interface protoco
29、ls and procedures to support the following 4 features and functions. 5 Features and functions explicitly supported in this standard: 6 Machine To Machine (M2M) communications 7 1.1.1 Purpose 8 The purpose of this document is to provide a guide for optimized standards and message flows for Radio 9 Ac
30、cess Network (RAN) interfaces for M2M communications. 10 1.1.2 Scope 11 M2M communication is a form of data communication that involves one or more entities that do not 12 necessarily require human interaction or intervention in the process of communication. 13 M2M communication can be carried over
31、cdma2000 1x or HRPD networks. In M2M communication, the 14 cdma2000 role is largely confined to serving as transport, as well as performing other networking services 15 (access security, accounting, QoS, etc). 16 This document provides RAN considerations for M2M to guide the work of the enhancements
32、 required to 17 the cdma2000 technology for the support of this feature. 18 1.1.3 Document Convention 19 “Shall” and “shall not” identify requirements to be followed strictly to conform to this document and from 20 which no deviation is permitted. “Should” and “should not” indicate that one of sever
33、al possibilities is 21 recommended as particularly suitable, without mentioning or excluding others; that a certain course of 22 action is preferred but not necessarily required; or (in the negative form) that a certain possibility or 23 course of action is discouraged but not prohibited. “May” and
34、“need not” indicate a course of action 24 permissible within the limits of the standard. “Can” and “cannot” are used for statements of possibility 25 and capability, whether material, physical, or causal. 26 1.2 References 27 References are either normative or informative. A normative reference is u
35、sed to include another doc-28 ument as a mandatory part of a 3GPP2 specification. Documents that provide additional non-essential in-29 formation are included in the informative references section. 30 1.2.1 Normative References 31 The following standards contain provisions which, through reference i
36、n this text, constitute provisions of 32 this standard. At the time of publication, the editions indicated were valid. All standards are subject to 33 revision, and parties to agreements based on this standard are encouraged to investigate the possibility of 34 applying the most recent editions of t
37、he standards indicated below. ANSI and TIA maintain registers of 35 currently valid national standards published by them. 36 None 37 38 1-1 TIA-4984 1.2.2 Informative References 1 A.S0008 3GPP2: A.S0008-D v1.0, Interoperability Specification (IOS) for High Rate Packet Data 2 (HRPD) Radio Access Netw
38、ork Interfaces with Session Control in the Access Network, 3 March 2013. 4 A.S0009 3GPP2: A.S0009-D v1.0, Interoperability Specification (IOS) for High Rate Packet Data 5 (HRPD) Radio Access Network Interfaces with Session Control in the Packet Control 6 Function, March 2013. 7 A.S0011 3GPP2: A.S001
39、1-D v4.0, Interoperability Specification (IOS) for cdma2000 Access Net-8 work Interfaces Part 1 Overview, August 2012. 9 A.S0012 3GPP2: A.S0012-D v4.0, Interoperability Specification (IOS) for cdma2000 Access Net-10 work Interfaces Part 2 Transport, August 2012. 11 A.S0013 3GPP2: A.S0013-D v4.0, Int
40、eroperability Specification (IOS) for cdma2000 Access Net-12 work Interfaces Part 3 Features, August 2012. 13 A.S0014 3GPP2: A.S0014-D v4.0, Interoperability Specification (IOS) for cdma2000 Access Net-14 work Interfaces Part 4 (A1, A1p, A2, and A5 Interfaces), August 2012. 15 A.S0015 3GPP2: A.S0015
41、-D v4.0, Interoperability Specification (IOS) for cdma2000 Access Net-16 work Interfaces Part 5 (A3 and A7 Interfaces), August 2012. 17 A.S0016 3GPP2: A.S0016-D v4.0, Interoperability Specification (IOS) for cdma2000 Access Net-18 work Interfaces Part 6 (A8 and A9 Interfaces), August 2012. 19 A.S001
42、7 3GPP2: A.S0017-D v4.0, Interoperability Specification (IOS) for cdma2000 Access Net-20 work Interfaces Part 7 (A10 and A11 Interfaces), August 2012. 21 C.R1001 3GPP2: C.R1001-I v1.0 Administration of Parameter Value Assignments for cdma2000 22 Spread Spectrum Standards, September 2013. 23 C.S0001
43、3GPP2: C.S0001-F v1.0, Introduction to cdma2000 Standards for Spread Spectrum 24 Systems, December 2012. 25 C.S0002 3GPP2: C.S0002-F v1.0, Physical Layer Standard for cdma2000 Spread Spectrum 26 Systems, December 2012. 27 C.S0003 3GPP2: C.S0003-F v1.0, Medium Access Control (MAC) Standard for cdma20
44、00 Spread 28 Spectrum Systems, December 2012. 29 C.S0004 3GPP2: C.S0004-F v1.0, Signaling Link Access Control (LAC) Standard for cdma2000 30 Spread Spectrum Systems, December 2012. 31 C.S0005 3GPP2: C.S0005-F v1.0, Upper Layer (Layer 3) Signaling Standard for cdma2000 32 Spread Spectrum Systems, Dec
45、ember 2012. 33 S.P0146 3GPP2: S.R0146-0 v1.0, Machine-to-Machine Communication System Requirements, 34 August 2012. 35 36 1.3 Terminology 37 1.3.1 Acronyms 38 39 3GPP2 3rdGeneration Partnership Project 2 BS Base Station 1-2 TIA-4984 ANID Access Network Identifiers CANID Current Access Network Identi
46、fiers CDMA Code Division Multiple Access HRPD High Rate Packet Data IE Information Element IOS Interoperability Specification M2M Machine to Machine MS Mobile Station MSC Mobile Switching Center PCF Packet Control Function PDSI Packet Data Service Instance PDSN Packet Data Serving Network PPP Point-
47、to-Point Protocol RAN Radio Access Network SC/MM Session Control/Mobility Management 1.3.2 Definitions 1 1x Refer to “cdma2000 1x”. 2 cdma2000 1x The version of cdma2000 defined by C.S0001 C.S0005 and also 3 supported by A.S0011 A.S0017. 4 HRPD The version of High Rate Packet Data supported by A.S00
48、08 and 5 A.S0009. 6 M2M Device A device that hosts M2M application(s) and is able to directly or in-7 directly communicate with an M2M application server. 8 1.4 Architecture 9 There are no cdma2000 1x or HRPD architectural differences identified for the support of M2M IOS en-10 hancements. Refer to
49、A.S0011 Section 2.2 for the 1x RAN reference model, to A.S0008 Section 1.4 11 for the HRPD (SC/MM in the AN) reference model or to A.S0009 Section 1.4 for the HRPD (SC/MM 12 in the PCF) reference model. 13 1.5 M2M IOS Assumptions 14 None. 15 1.6 Feature Descriptions 16 This document provides a guide for the following RAN features. 17 1.6.1 1x Device Capability 18 This feature supports the ability of the MS and the 1x MSC to notify the BS of the M2M capabilities 19 supported by the MS (e.g., direct channel assignmen
