1、 TIA-4954 August 2012Machine-to-Machine (M2M) Communication System Requirements Document NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improve
2、ment 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 selling products not conf
3、orming 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 National Standards Institut
4、e (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 all applicable regulator
5、y 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-4954, formulated under the cognizance of the TIA TR-45 Mobile (b) there is
6、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 may involve the use o
7、f 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 attention, a statement from
8、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 terms or conditions, which
9、 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 as respects the Docum
10、ent 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 otherwise), whether suc
11、h 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 Normative Reference; (ii)
12、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 constitute identification to T
13、IA 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 with the contents of the
14、 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 PARTYS INTELLECTUAL PR
15、OPERTY 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 ANY PRODUCT OR SERVICE
16、 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, SPECIAL, INCIDENTAL OR CONSE
17、QUENTIAL 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 FOREGOING NEGATION OF D
18、AMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. 3GPP2 S.R0146-0 v1.0 ii 1 REVISION HISTORY 2 3 Revision Description of Changes Date Rev 0 v1.0 Initial publication 9 August 2012 4 5 3GPP2 S.R0146-0 v1.0 iii
19、1 TABLE OF CONTENTS 2 3 4 FOREWORD. iv 5 INTRODUCTION 1 6 1.1 Scope1 7 1.2 Document Conventions .1 8 1.3 Terminology 2 9 1.3.1 Definitions 2 10 1.3.2 Abbreviations 2 11 1.4 References 3 12 2 GENERAL FEATURE DESCRIPTION .4 13 2.1 Backwards Compatibility 4 14 3 DETAILED REQUIREMENTS 5 15 3.1 General R
20、equirements 5 16 3.2 Architecture Requirements .5 17 3.3 Core Network Requirements 6 18 3.4 Access Network Requirements 7 19 3.5 Device Requirements 7 20 3.5.1 Device Type and Identification 7 21 3.5.2 Device Software Upgrade .8 22 3.5.3 Device Battery Life Optimization .8 23 3.5.4 Device Access Req
21、uirements .8 24 3.6 Security Requirements 8 25 3.7 Service Requirements .9 26 3.8 Special Requirements .9 27 3.8.1 Transmission Efficiency Requirements 9 28 3.8.2 Monitoring and Diagnostic Management .9 29 30 31 32 3GPP2 S.R0146-0 v1.0 iv FOREWORD 1 This foreword is not part of this document. 2 3 Th
22、is document was prepared as a joint TSG effort led by Technical 4 Specification Group S (TSG-S) of the Third Generation Partnership Project 2 5 (3GPP2). 6 7 8 9 10 3GPP2 S.R0146-0 v1.0 v 1 2 3 4 5 6 This page intentionally left blank. 7 3GPP2 S.R0146-0 v1.0 1 INTRODUCTION 2 1.1 Scope 3 Machine-to-Ma
23、chine (M2M) communication is a form of data 4 communication that involves one or more entities that do not necessarily 5 require human interaction or intervention in the process of 6 communication. 7 M2M communication could be carried over cdma200011x or HRPD 8 networks. In M2M communication, the cd
24、ma2000 role is largely 9 confined to serving as transport, as well as performing other networking 10 services (access security, accounting, QoS, etc). 11 M2M services have their own specific characteristics which might be 12 different from services in which humans directly influence 13 communication
25、 flow. This may require some special handling or 14 optimization of the cdma2000 network for better support of M2M 15 communications. 16 This document provides the system requirements for M2M to guide the 17 work of the enhancements required to the cdma2000 technology for the 18 support of this feat
26、ure. 19 20 1.2 Document Conventions 21 “Shall” and “shall not” identify requirements to be followed strictly to 22 conform to this document and from which no deviation is permitted. 23 “Should” and “should not” indicate that one of several possibilities is 24 recommended as particularly suitable, wi
27、thout mentioning or excluding 25 others, that a certain course of action is preferred but not necessarily 26 required, or that (in the negative form) a certain possibility or course of 27 action is discouraged but not prohibited. “May” and “need not” indicate a 28 course of action permissible within
28、 the limits of the document. “Can” and 29 “cannot” are used for statements of possibility and capability, whether 30 material, physical or causal. 31 In addition: 32 1cdma2000is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs)
29、 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. 3GPP2 S.R0146-0 v1.0 2 “cdma2000 networks shall support” means that this is a 1 mandatory feature in cdma2000 networks that
30、 are compliant with 2 this document. 3 “cdma2000 networks shall be capable of supporting” means that 4 this feature must be supported by the specification, and the 5 deployment is at the discretion of the network operator. 6 “cdma2000 devices shall support” means that this is a 7 mandatory feature i
31、n all cdma2000 devices that are compliant with 8 this document. 9 “cdma2000 devices shall be capable of supporting” means that 10 this feature must be supported by the specification for 11 incorporation into cdma2000 devices, and the product support is 12 at the discretion of the device vendor. 13 1
32、4 1.3 Terminology 15 Terms and abbreviations used within this specification are defined in this 16 Section. 17 18 1.3.1 Definitions 19 cdma2000 M2M Device 20 A cdma2000 M2M Device hosts M2M application(s), and is able to 21 directly or indirectly communicate with an M2M application server over 22 on
33、e or more cdma2000 access technologies (e.g., 1, 2). 23 24 cdma2000 M2M Hardware Identifier 25 The cdma2000 M2M Hardware Identifier is the globally unique hardware 26 identifier assigned to a cdma2000 M2M Device (e.g., MEID). 27 28 29 30 1.3.2 Abbreviations 31 32 CDMA Code Division Multiple Access E
34、TSI European Telecommunication Standards Institute 3GPP2 S.R0146-0 v1.0 3 HRPD High Rate Packet Data IP Internet Protocol IPv4, IPv6 Internet Protocol Version 4, 6 M2M Machine to Machine MEID Mobile Equipment Identifier MTC Machine Type Communication NAT Network Address Translation P sensitivity to
35、battery life; access delay tolerance; support 26 of single or multiple application priorities; mobile vs. stationary, 27 etc. 28 DEV-02: A cdma2000 M2M Device shall be assigned an MEID cdma2000 29 hardware identifier (see SC.R4002-0). 30 DEV-03: A cdma2000 M2M Device that also supports a 3GPP access
36、 31 technology shall be assigned a globally unique multimode MEID 32 hardware identifier (see SC.R4001-0 and SC.R4002-0). 33 DEV-04: A cdma2000 M2M Device shall be capable of supporting multiple 34 group addresses. 35 3GPP2 S.R0146-0 v1.0 8 1 3.5.2 Device Software Upgrade 2 DVSFT-01: cdma2000 networ
37、ks and cdma2000 M2M Devices shall be capable 3 of supporting remote software upgrade for cdma2000 M2M Devices. 4 5 3.5.3 Device Battery Life Optimization 6 DVBAT-01: cdma2000 networks and cdma2000 M2M Devices shall be capable 7 of supporting mechanisms for enhancing cdma2000 M2M Device 8 battery lif
38、e. 9 10 3.5.4 Device Access Requirements 11 DA-01: cdma2000 M2M Devices shall support access control mechanisms 12 to mitigate access-attempt overload at the network. This support 13 should include cdma2000 M2M Device provisioning over the 14 cdma2000 Network to manage device access attempts. 15 DA-
39、02: cdma2000 networks shall be capable of managing cdma2000 M2M 16 Device access transmissions including the ability to disable all 17 transmissions from a cdma2000 M2M Device. The functionality 18 should be supported for multiple cdma2000 M2M Devices using 19 the group addressing capability (see AC
40、C-05 and DEV-07). 20 DA-03: When a cdma2000 device that supports one or more applications 21 with varying priorities, (e.g. a low priority M2M and a higher 22 priority non-M2M application) accesses the network, the device-23 applied access control for the network access shall be consistent 24 with t
41、he following criteria: (a) application initation delay tolerance, 25 (b) application priority. 26 27 3.6 Security Requirements 28 SEC-01: cdma2000 networks shall support authorization of a cdma2000 29 M2M Device based on cdma2000 access subscription 30 authentication. 31 SEC-02: cdma2000 networks sh
42、all support secure communication between 32 the cdma2000 M2M Device and the M2M service provider domain. 33 SEC-03: cdma2000 networks shall support mutual authentication between 34 the cdma2000 access network and the cdma2000 M2M Device. 35 3GPP2 S.R0146-0 v1.0 9 SEC-04: cdma2000 networks shall supp
43、ort a mechanism to restrict the use 1 of a cdma2000 M2M access subscription to a specific cdma2000 2 M2M Device or a M2M group of devices. 3 4 3.7 Service Requirements 5 SERV-01: The cdma2000 network shall be capable of restricting a cdma2000 6 M2M Device to only attaching to a specific set of base
44、stations. 7 SERV-02: The cdma2000 network shall be capable of controlling the 8 frequency of registration of an individual or a group of cdma2000 9 M2M Devices. 10 11 3.8 Special Requirements 12 3.8.1 Transmission Efficiency Requirements 13 EFF-01: cdma2000 networks shall be capable of supporting en
45、hanced 14 transport efficiency when delivering M2M data from or to a 15 cdma2000 M2M Device, especially considering small data 16 payloads. 17 18 3.8.2 Monitoring and Diagnostic Management 19 MON-01: cdma2000 networks shall be capable of supporting over-the-air 20 (OTA) monitoring and diagnosing a cdma2000 M2M Device 21 connected to the cdma2000 network. 22 Note: This capability may include the use of existing OTA 23 capabilities to cause remote diagnostics to be run on the device. 24 25 26 27 28 29 30 31 3GPP2 S.R0146-0 v1.0 10 1 2 3 4 This page intentionally left blank. 5 6