TIA TSB-474-2011 Study for Machine-to-Machine (M2M) Communication for cdma2000 Networks《cdma2000网络的机器对机器(M2M)通信研究》.pdf

《TIA TSB-474-2011 Study for Machine-to-Machine (M2M) Communication for cdma2000 Networks《cdma2000网络的机器对机器(M2M)通信研究》.pdf》由会员分享，可在线阅读，更多相关《TIA TSB-474-2011 Study for Machine-to-Machine (M2M) Communication for cdma2000 Networks《cdma2000网络的机器对机器(M2M)通信研究》.pdf（38页珍藏版）》请在麦多课文档分享上搜索。

1、 TSB-474 February 2011Study for Machine-to-Machine (M2M) Communication for cdma2000 Networks NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and imp

2、rovement 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

3、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 National Standards Inst

4、itute (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 regul

5、atory 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. 3-0391, formulated under the cognizance of the TIA TR-45 Mobile (b) there is n

6、o 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 of

7、 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 t

8、he 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 Docume

10、nt 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 such

11、 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) T

12、IAs 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 TI

13、A 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 PRO

15、PERTY 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 CONSEQ

17、UENTIAL 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 DA

18、MAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. S.R0141-0 v1.0 ii Editor Eileen McGrath, NEC Corporation, Clifton Barber, KDDI, Revision History Revision Description of Changes Date Rev0 v1.0 Initial Publi

19、cation 9 December 2010 S.R0141-0 v1.0 iii This page intentionally left blank. S.R0141-0 v1.0 iv Table of Contents Foreword . viii 1 Introduction . 1 1.1 Scope . 1 1.2 Document Conventions 1 1.3 References . 2 2 Acronyms, Abbreviations, and Terminology 2 3 M2M Communication and Services Overview 3 3.

20、1 Introduction . 3 3.2 Potential Impact of M2M Communication Services on Network Operational Complexities . 4 4 M2M Communication Services and Scenarios 4 4.1 Introduction . 4 4.2 M2M Communication Characteristics . 5 4.3 M2M Device Communications with One or More M2M Server(s) . 7 4.3.1 M2M server

21、is located inside the cdma2000 network. 7 4.3.2 M2M Server is located outside the cdma2000 network . 8 4.4 M2M Device Communications with M2M Device(s) . 8 4.5 M2M Access Hierarchical Architecture 9 5 M2M Addressing and Identifiers . 9 6 Potential M2M Communication Service Requirements 10 6.1 Improv

22、ed Management of M2M Communication Groups . 10 6.2 Reduced Complexity . 11 6.3 Device Management . 11 7 M2M Communication Use Cases 11 8 System Enhancements for M2M Communications Services Support . 13 8.1 3GPP2 System Architecture Enhancements Overview 14 8.1.1 Communication Model 14 8.1.2 M2M Comm

23、unication Adaptation Protocol 15 8.1.3 New M2M Terminal Class 15 8.2 cdma2000 Radio Enhancements 16 8.2.1 Transmission Efficiency of Communication Networks . 16 S.R0141-0 v1.0 v 8.2.1.1 Reverse Link Transmission Efficiency 16 8.2.1.1.1 Access Mechanism Enhancement . 16 8.2.1.1.2 Lower Minimum Transm

24、ission Rate . 17 8.2.1.1.3 Reduce Transmission Overhead 18 8.2.2 Improve Radio Link Reliability and Extend Coverage . 18 8.2.2.1 Reduce the Minimum Transmission Rate . 18 8.2.2.2 Improved Access Channel Performance 18 8.2.2.3 Improve FL and RL Balance . 19 8.2.3 M2M Terminal Management 19 8.2.3.1 M2

25、M Terminal ID Management . 19 8.2.3.2 M2M Terminal Security . 20 8.2.4 Battery Life Improvement for Battery Operated M2M Devices . 20 8.3 cdma2000 Core Network Enhancements . 21 8.3.1 Resource Management Mechanism Enhancement 21 8.3.2 Paging Enhancement . 21 8.3.3 Circuit Switch Core Networks Enhanc

26、ements 21 8.3.4 Packet Data Core Network Enhancements . 21 Annex A M2M Parking Lot 23 S.R0141-0 v1.0 vi List of Figures FIGURE 1: M2M DEVICES COMMUNICATING WITH M2M SERVER(S) 8 FIGURE 2: INTER-M2M DEVICES COMMUNICATION 8 FIGURE 3: M2M GATEWAY ARCHITECTURE 9 FIGURE 4: M2M CLIENT SERVER COMMUNICATION

27、MODEL . 14 S.R0141-0 v1.0 vii List of Tables TABLE 1: LIST OF M2M CHARACTERISTICS 6 TABLE 2: LIST OF M2M USE CASES . 12 TABLE A-1: LIST OF NOT TO LOSE M2M ENHANCEMENTS 23 S.R0141-0 v1.0 viii FOREWORD This foreword is not part of this study. 3GPP2 Study for M2M Communication references material initi

28、ally presented in the following publication: SC.R5003-0 v1.0: “3GPP2 Vision for 2009 and Beyond”1 S.R0141-0 v1.0 1 1 INTRODUCTION 1 1.1 Scope 2 The intent of this document is to evaluate the aspects of Machine-to-Machine 3 (M2M) communications that are required to ensure that cdma20001 network 4 inf

29、rastructure is a viable communication network option for the M2M 5 applications, including: 6 Identify M2M service functionalities that capture the 7 fundamentals of M2M communications and possible M2M 8 applications. 9 Identify applicable M2M communications use cases and 10 characteristics to ensur

30、e that they are the basis for the evaluated 11 network enhancements through out this study. 12 Identify the list of potential requirements needed to enable 13 machine type communications on cdma2000 networks based on 14 the identified M2M service functionalities. 15 Evaluate the impact of the antici

31、pated large number of M2M 16 devices and how to minimize this impact on the cdma2000 17 networks (e.g., a clear definition of M2M Group Based 18 communications and its usage). 19 Identify possible enhancements that would help in providing 20 cdma2000 network operators with lower operational complexi

32、ties 21 when offering machine-type communication services. 22 Optimize network operations to minimize the impact on device 23 battery power usage. 24 This study of M2M Communication is targeting the enablement of machine-25 type data communication services and M2M applications on cdma2000 26 network

33、s. 27 1.2 Document Conventions 28 “Shall” and “shall not” identify requirements to be followed strictly to conform 29 to this document and from which no deviation is permitted. “Should” and 30 “should not” indicate that one of several possibilities is recommended as 31 particularly suitable, without

34、 mentioning or excluding others, that a certain 32 course of action is preferred but not necessarily required, or that (in the 33 1cdma2000 is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2. When applied to goods an

35、d services, the cdma2000 mark certifies their compliance with cdma2000 standards. Geographically (and as of the date of publication), cdma2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States. S.R0141-0 v1.0 2 negative form) a certain possibilit

36、y or course of action is discouraged but not 1 prohibited. “May” and “need not” indicate a course of action permissible within 2 the limits of the document. “Can” and “cannot” are used for statements of 3 possibility and capability, whether physical or causal. 4 1.3 References 5 All references are i

37、nformative. 6 1 ETSI TS 102 671 Release 9, “Smartcards; Machine To Machine UICC; 7 Physical and logical characteristic”, April 2010. 8 2 3GPP2 C.S0024 cdma2000 High Rate Packet Data Air Interface 9 Specification 10 11 2 ACRONYMS, ABBREVIATIONS, AND TERMINOLOGY 12 ACRONYM 25 Through another subsystem

38、s internal addressing mechanism (e.g., 26 through a “Home Gateway”, or a “Data Aggregator”); 27 Through a logical mapping of pre-registered information (e.g., use 28 ATI to access an M2M device in a cell in an HRPD network). 29 S.R0141-0 v1.0 10 Although it is straightforward to have each M2M device

39、 equipped with an IP 1 address, it may not be practical due to the complexity limitation of some M2M 2 devices, such as a simple motion sensor of a security monitoring system. 3 Addressing through another subsystem is a typical solution to accommodate 4 the M2M devices with limited complexities or t

40、o shield certain M2M devices 5 from being directly accessed from the external addressing mode (e.g., through 6 direct IP access). 7 Each M2M device should be uniquely identified. Typically, an M2M device must 8 have an identifier associated with the physical identity (e.g., a serial number) 9 so tha

41、t it can be uniquely tracked for device management purposes. 10 Those M2M devices that connect directly to the cdma2000 network need a 11 subscription for a service, and hence, a subscription identity is required. The 12 subscription identity, preferably, should be uniquely associated with the M2M 1

42、3 device; however, there may be occasions the subscription identity indicates a 14 “group service”, which is applicable to a group of M2M devices. 15 In order for an M2M device to transmit data or for the network to page an M2M 16 device within a cell more efficiently, a physical identity (or a subs

43、cription identity) 17 can be mapped to a logical identity with an access ID in a shorter format. For 18 example, in cdma2000 network, the physical identity of an M2M device can be 19 mapped into a logical identity such as an Access Terminal Identifier (ATI) after 20 the M2M device has been registere

44、d with a valid subscription identity. The logical 21 identity can then be used to identify the M2M device in the same way as the 22 physical identity but in a more compact format for the transmission efficiency 23 over the air link. 24 In order to support the class of M2M devices that require end-to

45、-end IP 25 communication capability, each M2M device directly connected to the cdma2000 26 network may need to have a unique IP address. M2M devices connected to the 27 network via some type of M2M Gateway may or may not use IP addressing. 28 It is recommended that the device identity be separated f

46、rom the subscription 29 identity. Comprehensive recommendations on device numbering and 30 addressing related to the M2M subscription identity and the device identity for 31 the cdma2000 systems can be found in the SC report on this subject. 32 33 6 POTENTIAL M2M COMMUNICATION SERVICE REQUIREMENTS 3

47、4 6.1 Improved Management of M2M Communication Groups 35 M2M Service subscribers will be able to assign multiple devices that can be 36 managed on an individual or group basis. For an operator supporting M2M 37 devices on its network, it would be helpful if there is a broadcast message that 38 can b

48、e sent from the network for the purpose of controlling or alerting a group 39 of M2M devices. From the viewpoint of radio congestion, it is preferable to 40 utilize aggregate control via broadcast messaging rather than individual 41 S.R0141-0 v1.0 11 simultaneous messaging addressed to each one of t

49、he multiple M2M 1 subscribed devices. 2 M2M Services will be able to send a broadcast message to a large group of M2M 3 devices affiliated with a single subscriber (e.g., to page the M2M devices). 4 6.2 Reduced Complexity 5 There is a need for a class of M2M devices with reduced design complexity (e.g., 6 reduced radio interface design complexity due to low data transmission rate) 7 for certain M2M applications such as vending machine, Supervisory Control 8 And Data Acquisition (SCADA), electric meters, home s