1、 TIA-4962 March 2012cdma2000 M2M Numbering Recommendations 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 improvem
2、ent 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 confo
3、rming 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 Institute
4、 (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 regulatory
5、 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-4962, 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. 3GPP2 SC.R4005-0 v1.0 Revision History Revision Description of Changes Date Rev 0 v1.0 Initial publication release 14 October 2011 i Table of Contents 1 1 INTR
19、ODUCTION 1 2 1.1 OVERVIEW . 1 3 1.2 SCOPE 1 4 1.3 DOCUMENT CONVENTIONS 2 5 1.4 REFERENCES 2 6 1.5 ASSUMPTIONS 4 7 2 ACRONYMS, ABBREVIATIONS, AND TERMINOLOGY 4 8 3 OBJECTIVES OF THE M2M NUMBERING SCHEME 6 9 4 IDENTIFIER MATRIX 6 10 5 PROBLEMS DEFINITION AND SOLUTION OPTIONS - 1X SUBSCRIPTION IDENTIFI
20、ERS 9 11 5.1 MIN EXHAUSTION . 9 12 5.2 IDENTIFIER GLOBAL UNIQUENESS . 10 13 5.3 MULTIPLE SUBSCRIPTIONS . 10 14 5.4 MULTIPLE SIMULTANEOUS CDMA2000 ACCESSES . 10 15 5.5 MULTIPLE ACCESS SUBSCRIPTION IDENTIFIERS FOR DIFFERENT ACCESS TECHNOLOGIES . 11 16 5.6 IMSI VS. MIN 11 17 5.7 ALLOCATION EFFICIENCY 1
21、2 18 5.8 PROTOCOL LIMITATIONS 12 19 6 PROBLEM DEFINITIONS AND PROPOSED SOLUTIONS - PACKET DATA ACCESS 20 SUBSCRIPTION IDENTIFIERS 13 21 6.1 SIZE OF M2M PACKET DATA ACCESS SUBSCRIPTION IDENTIFIER . 13 22 6.2 SIZE OF NAI WITH DECORATION 14 23 6.3 UNIQUENESS OF M2M ACCESS SUBSCRIPTION IDENTIFIER 14 24
22、6.4 M2M ACCESS SUBSCRIPTION IDENTIFIER PRIVACY . 15 25 7 PROBLEM DEFINITIONS AND PROPOSED SOLUTIONS - HARDWARE IDENTIFIERS . 15 26 7.1 ESN EXHAUSTION . 16 27 7.2 IDENTIFIER GLOBAL UNIQUENESS . 16 28 7.3 MULTI-RADIO ACCESS TECHNOLOGY (RAT) HARDWARE IDENTIFICATION 16 29 7.4 ALLOCATION EFFICIENCY 17 30
23、 8 PROBLEM DEFINITIONS AND PROPOSED SOLUTIONS - IP IDENTIFIERS . 17 31 8.1 IPV4 EXHAUSTION . 18 32 9 PROBLEM DEFINITIONS AND PROPOSED SOLUTIONS - MOBILE DIRECTORY NUMBERS . 19 33 9.1 USE OF PHONE NUMBERS FOR PSTN CALLS 19 34 9.2 USE OF PHONE NUMBERS FOR CDMA2000 SMS . 19 35 9.3 MDNS FOR CROSS-TECHNO
24、LOGY SMS . 20 36 9.4 MDNS FOR OTHER SERVICES 20 37 9.5 VOIP AND MDN 20 38 9.6 NO PREMATURE EXHAUSTION OF MDNS FROM M2M . 21 39 10 PROBLEM DEFINITIONS AND PROPOSED SOLUTIONS - CARD IDENTIFIERS . 21 40 10.1 UIMID EXHAUSTION FOR M2M . 22 41 10.2 EUIMID FOR M2M . 22 42 10.3 CARD ID UNIQUENESS 23 43 3GPP
25、2 SC.R4005-0 v1.0 ii 11 PROBLEM DEFINITIONS AND PROPOSED SOLUTIONS - RADIO ACCESS NETWORK (RAN) 1 IDENTIFIERS . 24 2 11.1 SID (SYSTEM IDENTIFIER) . 24 3 11.2 SID CODES 24 4 11.3 SID CODE UNIQUENESS 25 5 11.4 NID (NETWORK IDENTIFICATION NUMBER) 25 6 11.5 NID CODES . 25 7 11.6 NID UNIQUENESS 25 8 11.7
26、 MCC+MNC 26 9 11.8 MCC CODES . 26 10 11.9 MCC UNIQUENESS 26 11 11.10 MNC CODES . 26 12 11.11 MNC UNIQUENESS 26 13 11.12 HRPD SERVING AREA IDENTIFIER1 . 27 14 11.13 SUBNET ID UNIQUENESS . 27 15 11.14 SUBNET IDS 27 16 11.15 HRPD SECTOR ID . 28 17 12 RECOMMENDATIONS . 28 18 13 ADDITIONAL NOTES . 30 19
27、20 iii Foreword 1 This foreword is not part of this specification. 2 The document has been prepared by the 3GPP2 SC (Steering Committee) M2M 3 Numbering AdHoc under charter from the 3GPP2 SC. 4 5 6 3GPP2 SC.R4005-0 v1.0 iv 1 This page intentionally left blank. 2 3 1 1 1 INTRODUCTION 2 1.1 Overview 3
28、 This report is a System Requirements Document that analyzes issues 4 associated with M2M Numbering and provides recommendations from 5 the 3GPP2 SC M2M Numbering AdHoc. This report contains normative 6 requirements and suggested normative requirements. 7 M2M refers to “machine-to-machine” communica
29、tions communications 8 for devices that normally exchange data without human intervention and 9 which, in the context of this report, have at least one cdma2000110 operational mode. 11 1.2 Scope 12 This document is focused on the numbering, identification, and 13 addressing aspects of M2M technologi
30、es and services using 3GPP2 14 specifications. The following activities were executed in the development 15 of this document: 16 Consideration of issues related to M2M numbering and addressing 17 schemes; 18 Investigation of global M2M numbering issues and liaison with 19 industry M2M committees, re
31、levant stakeholders and fora; 20 Determination of M2M numbering impacts regarding addressing 21 (e.g., E.164 MSISDNs, IMSI) and device identification (e.g., IMEI, 22 MEID) in a fashion that is complementary to the work of other 23 groups; 24 Consideration of other terminology for M2M (e.g., (MTC) Ma
32、chine 25 Type Communications and (SDC) Smart Device Communications); 26 Evaluation of proposals for M2M numbering resources while 27 identifying numbering methods that consider potential negative 28 impacts on legacy numbering and back office systems. 29 1cdma2000is a trademark for the technical nom
33、enclature 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. 3GPP2 SC.R4005-0 v1.0 2 Terminology
34、used in this report, unless otherwise specified, is limited to 1 the context of cdma2000 protocols. 2 1.3 Document Conventions 3 “Shall” and “shall not” identify requirements to be followed strictly to 4 conform to this document and from which no deviation is permitted. 5 “Should” and “should not” i
35、ndicate that one of several possibilities is 6 recommended as particularly suitable, without mentioning or excluding 7 others, that a certain course of action is preferred but not necessarily 8 required, or that (in the negative form) a certain possibility or course of 9 action is discouraged but no
36、t prohibited. “May” and “need not” indicate a 10 course of action permissible within the limits of the document. “Can” and 11 “cannot” are used for statements of possibility and capability, whether 12 material, physical or causal. 13 1.4 References 14 The following informative references were used i
37、n the preparation of this 15 report: 16 1 3GPP2 C.S0024-B v3.0 cdma2000 High Rate Packet Data Air 17 Interface Specification. September 2009. 18 2 Ericsson North America - Geoff Hollingsworth. Presentation to the 19 CDG webinar on Smart Wireless Devices entitled “Perspectives on 20 M2M”. 17 January
38、2011. 21 http:/www.cdg.org/news/events/webcast/110310_smart_devices22 _service/2_Ericsson-Hollingworth_M2M_Perspectives_PA7av2.pdf 23 3 IETF RFC 4282 The Network Access Identifier. December 2005. 24 4 IEEE Guidelines for 64-bit Global Identifier (EUI-64) Registration 25 Authority. 26 http:/standards
39、.ieee.org/develop/regauth/tut/eui64.pdf 27 5 3GPP2 SC.R4001-0 v3.0 Global Wireless Equipment Numbering 28 Administration Procedures. 3GPP2. April, 2011. 29 6 3GPP2 SC.R4002-0 v7.0 GHA Assignment Procedures for MEID 30 and SF_EUIMID. 3GPP2. April, 2011. 31 7 3GPP2 SC.R4003-0 v1.0 Expanded R-UIM Numbe
40、ring 32 Administration Procedures. 3GPP2. June 2007. 33 8 3GPP2 SC.R4004-0 v2.0 User Identification Mobile ID 34 Manufacturers Code Assignment Guidelines and Procedures. 35 3GPP2. May 2010. 36 9 GSMA TS.06 IMEI Allocation and Approval Guidelines Version 6.0. 37 July 2011. 38 3 10 MBI Oversight Counc
41、il - MIN Block Identifier (MBI) Assignment 1 Guidelines and Procedures Version 6.00. April 2008. 2 https:/ 3 11 IFAST International Roaming Mobile Identification Number (MIN) 4 (IRM) Assignment Guidelines and Procedures Version 5.4. April 5 2007. http:/www.ifast.org/files/GuidelinesMay2007/IRM 6 Gui
42、delines v5.4.pdf 7 12 IFAST System Identification Number (SID) Assignment Guidelines 8 and Procedures Version 2.2. April 2007. 9 http:/ifast.org/files/GuidelinesMay2007/IFAST SID Guidelines 10 r2.2.pdf 11 13 ITU-T E.164 The international public telecommunication 12 numbering plan. November 2010. 13
43、14 ITU-T E.118 The international telecommunication charge card. 14 May 2006. 15 15 ITU-T E.212 The international identification plan for public 16 networks and subscriptions. May 2008. 17 16 TIA TR-45 Electronic Serial Number Manufacturers Code 18 Assignment Guidelines and Procedures. December 2009.
44、 19 17 IETF RFC 2460 Internet Protocol, Version 6 (IPv6). December 1998. 20 18 IETF eRFC 791 Internet Protocol. September 1981. 21 19 IETF RFC 2784 Generic Routing Encapsulation (GRE). March 22 2000. 23 20 IETF RFC 2865 Remote Authentication Dial In User Service 24 (RADIUS). June 2000. 25 21 ARN IPv
45、4 Depletion, IPv6 Adoption. February 2011. 26 https:/ 27 22 3GPP2 C.S0005-E v3.0 Upper Layer (Layer 3) Signaling Standard 28 for cdma2000 Spread Spectrum Systems. June 2011. 29 23 3GPP2 C.S0087-A v1.0 E-UTRAN cdma2000 HRPD Connectivity 30 and Interworking: Air Interface Specification. April 2011. 31
46、 24 3GPP2 C.S0098-0 v1.0 cdma2000 Extended Cell High Rate Packet 32 Data Air Interface Specification. January 2011. 33 3GPP2 SC.R4005-0 v1.0 4 1.5 Assumptions 1 The following assumptions are considered reasonable as of the date of 2 this report but cannot be fully validated as they depend on the fut
47、ure 3 evolution of M2M: 4 1. Backwards compatibility with existing cdma2000 specifications is 5 expected to be maintained, 6 2. Existing Numbering Administration and related 7 guidelines/procedures (e.g., ESN, MEID, UIMID, IMEI are not 8 intended to be affected or require modifications as a result o
48、f 9 recommendations in this document). 10 3. Industry projections estimate that 50 billion M2M devices will be 11 deployed globally using some or all of the available access 12 technologies by the year 2020.2 In the most extreme case, 13 identifiers used in cdma2000 systems that simultaneously suppo
49、rt 14 legacy and M2M devices, should accommodate at least 60 billion 15 devices. 16 4. The majority of M2M devices in cdma2000 networks will never 17 need to make circuit or packet voice, TDD, or analog modem calls 18 and therefore will not need an MDN for this purpose. 19 5. It is reasonable for operators to use MIN or IMSI to address SMS if 20 they have insufficient MDNs for all M2M devices. 21 6. It is reasonable to utilize a mediation
