1、 ETSI TR 1Universal Mobile TelStudy on Machine-Typ(3GPP TR 22.9TECHNICAL REPORT 122 988 V13.0.0 (2016elecommunications System (LTE; n alternatives to E.164 for y e Communications (MTC) .988 version 13.0.0 Release 1316-01) (UMTS); 13) ETSI ETSI TR 122 988 V13.0.0 (2016-01)13GPP TR 22.988 version 13.0
2、.0 Release 13Reference RTR/TSGS-0122988vd00 Keywords LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Im
3、portant notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior writt
4、en authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document
5、 should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the followin
6、g services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF vers
7、ion shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI regist
8、ered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 122 988 V13.0.0 (2016-01)23GPP TR 22.988 versi
9、on 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “I
10、ntellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, i
11、ncluding IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has b
12、een produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross refe
13、rence between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in
14、clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TR 122 988 V13.0.0 (2016-01)33GPP TR 22.988 version 13.0.0 Release 13Contents Intellectual Property Rights
15、2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 6g33.1 Definitions 6g33.2 Symbols 6g33.3 Abbreviations . 6g34 Use cases 6g34.1 Use case 1 (Wireless Vending Machines) 6g34.1.1 Short Description 6g34.1.2 Ac
16、tors 7g34.1.3 Pre-Conditions 7g34.1.4 Post-Conditions. 7g34.1.5 Normal Flow . 7g34.1.6 Alternative Flows 8g34.1.7 Exceptions. 8g34.2 Use case 2 (Smart Bridges and Tunnels) 8g34.2.1 Short Description 8g34.2.2 Actors 9g34.2.3 Pre-Conditions 9g34.2.4 Post-Conditions. 9g34.2.5 Normal Flow . 9g34.2.6 Alt
17、ernative Flows 10g34.2.7 Exceptions. 10g34.3 Use case 3 Implantable Defibrillators 10g34.3.1 Short Description 10g34.3.2 Actors 11g34.3.3 Pre-Conditions 11g34.3.4 Post-Conditions. 11g34.3.5 Normal Flow . 11g34.3.6 Alternative Flows 12g34.3.7 Exceptions. 12g34.4 Use case 4 (Wireless Utility Meters) 1
18、2g34.4.1 Short Description 12g34.4.2 Actors 13g34.4.3 Pre-Conditions 13g34.4.4 Post-Conditions. 13g34.4.5 Normal Flow . 13g34.4.6 Alternative Flows 14g34.4.7 Exceptions. 14g34.5 Use case 5 (Wireless Weather Monitors) . 14g34.5.1 Short Description 14g34.5.2 Actors 14g34.5.3 Pre-Conditions 14g34.5.4 P
19、ost-Conditions. 15g34.5.5 Normal Flow . 15g34.5.6 Alternative Flows 15g34.5.7 Exceptions. 15g3ETSI ETSI TR 122 988 V13.0.0 (2016-01)43GPP TR 22.988 version 13.0.0 Release 135 High level Service Aspects . 16g35.1 What are the high level requirements for alternatives to E.164 for machine-type communic
20、ations? 16g35.1.1 Large capacity . 17g35.1.2 Compatibility with existing schemes 17g35.1.3 Impact on existing systems and hardware. 17g35.1.4 Provisioning 17g35.1.5 Device Identity Portability 17g35.1.6 Charging . 18g35.1.7 Services . 18g35.2 What are the security, reliability, and priority handling
21、 requirements for alternatives to E.164 for machine-type communications? . 18g35.3 Are there any implications due to roaming? . 18g35.4 Are there any implications on inter-domain routing? . 18g35.5 Are there any implications to hand-over between access networks? 18g36 MMI Aspects 18g37 Charging Aspe
22、cts . 19g38 Security Aspects . 19g39 Analysis 19g39.1 MSISDN (E.164) with existing number length 21g39.2 MSISDN (E.164) with max length of 15 digits 21g39.3 E.212 Numbers (IMSI) . 21g39.4 Other Numbering Plan Indicator in MAP . 21g39.5 Generic Uniform Resource Identifier (URI). 22g39.5.1 SIP Uniform
23、 Resource Identifier (URI) 22g39.5.2 TEL Uniform Resource Identifier (URI) 22g39.6 Fully Qualified Domain Name (FQDN) . 23g39.7 IPv4 Address 23g39.8 IPv6 Address 23g39.9 Network Access Identifier (NAI) . 24g310 Conclusion 24g311 Potential requirements for alternatives to E.164 for machine-type commu
24、nications . 25g3Annex A: Additional Definitions (Informative) . 26g3Annex B: Change history 27g3History 28g3ETSI ETSI TR 122 988 V13.0.0 (2016-01)53GPP TR 22.988 version 13.0.0 Release 13Foreword This Technical Report has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of
25、 the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Ver
26、sion x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the t
27、hird digit is incremented when editorial only changes have been incorporated in the document. Introduction There are currently unprecedented demands within the telecommunications industry for E.164 MSISDNs resources and these demands are expected to accelerate in the years to come. Accordingly, some
28、 countries and their national regulatory authorities have expressed concerns over the numbering requirements of new services involving Machine Type Communications (MTC) services and their expected rapid growth. MTC demand is forecast to grow from 50M connections to over 200M by 2013. A large number
29、of these services are currently deployed over circuit-switched GSM architectures and therefore use E.164 MSISDNs although such services do not require dialable numbers, and generally do not communicate with each other by human interaction. Without technical alternative to using public international
30、numbering resources as addresses, and considering the current forecasts and pending applications for numbers made to numbering plan administration agencies, there is a significant risk that some national numbering/dialling plans will run out of numbers in the near future, which would impact not only
31、 these MTC services but also the GSM/UMTS service providers in general. ETSI ETSI TR 122 988 V13.0.0 (2016-01)63GPP TR 22.988 version 13.0.0 Release 131 Scope This document seeks to study and highlight the challenge of using the existing public numbering resources to support Machine Type Communicati
32、on (MTC) services and proposes that 3GPP develop an alternative to using public numbering resources for MTC communications. 2 References 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 41.101: “Technical Specifications and Technical Reports for a GERAN-based 3GPP system“. 3 IETF RF
33、C 3986 “Uniform Resource Identifier (URI): Generic Syntax. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 and the following apply. A term defined in the present document takes precedence over the defin
34、ition of the same term, if any, in TR 21.905 1. (void) 3.2 Symbols For the purposes of the present document, the following symbols apply: (void) 3.3 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1 and the following apply. An abbreviation defined in the
35、present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. NIMTC Network Improvements for Machine Type Communications MNO Mobile Network Operator MTC Machine-Type Communications 4 Use cases 4.1 Use case 1 (Wireless Vending Machines) 4.1.1 Short Descriptio
36、n The Snack Company owns 100,000 snack vending machines in the Tri-City area. Each machine is connected to Snack“s central network via a wireless connection and sends a report of sales every hour. These scheduled reports are staggered so they don“t collide within Snack“s systems. These reports are s
37、hort bursts of no more than a few hundred bytes of data, and typically take less than 3 seconds to transmit. On occasion, Snack“s network will contact a machine by sending it an SMS, to which the machine sends a response. ETSI ETSI TR 122 988 V13.0.0 (2016-01)73GPP TR 22.988 version 13.0.0 Release 1
38、3Snack would like to add another 250,000 machines across the state, but their wireless service providers cannot provide enough MSISDNs. One provider, however, has implemented SIP capability, and makes available radio modules that use all-IP connections over the radio network. The main benefits to th
39、is new service is that each machine is assigned a SIP URI rather than a MSISDN (an alphanumerical SIP URI that doesn“t encapsulate a phone number), and that the service provider expects network loads and costs to decrease by going with all-IP traffic. The service provider“s network can easily handle
40、 the traffic load from 350,000 vending machines. The service provider has assigned Snack its own domain, vending. , so Snack can assign its own names to the machines. Snack has chosen to use its internal asset numbers for machine names to simplify the mapping from their asset management system to th
41、e messaging interface provided by the service provider. Messages are generated by Snack“s system and sent via the Internet to a web service provided by the service provider. The service provider then delivers the messages to the machines using SMS over IP. The machine modules are pre-configured to s
42、end scheduled reports to a web service provided by the service provider that transmits them to Snack“s network. All messages are encrypted in transit. Because the service provider was able to recover 100,000 previously issued MSISDNs, it was able to expand its coverage to wireless service consumers,
43、 generating much greater margins in the process. 4.1.2 Actors - Snack Company - Its wireless service provider 4.1.3 Pre-Conditions - The service provider has available to it IP-ready radio modules - The service provider“s network can support SIP or IMS, and is able to map a SIP URI to an IMSI or IMP
44、I in its HLR or HSS node. The service provider can support SIP URIs with a domain name of . - The service provider has a messaging gateway, maybe not much more than a web service - The radio modules are capable of establishing an IP connection in response to a page over the paging channel 4.1.4 Post
45、-Conditions - Vending machines transmit sales and trouble reports according to the schedule - Snack“s network receives and processes the reports - The service provider“s network supports the traffic load - Machines are reachable via their SIP URI and the service provider“s message gateway - The serv
46、ice provider“s experience allows it to lower the price charged to Snack by 25% 4.1.5 Normal Flow In the course of normal operations, there are three main events for a given vending machine: 1) When it first powers up and registers with the network 2) When it generates and sends a report to the netwo
47、rk 3) When the Snack network sends a message to the machine Each of these events is comprised of a sequence of smaller steps. Registration: 1) The machine powers up ETSI ETSI TR 122 988 V13.0.0 (2016-01)83GPP TR 22.988 version 13.0.0 Release 132) The radio module registers through the GPRSnetwork in
48、 the normal way 3) The radio module registers with the SIP server on the service provider“s network. This sets up the mapping between the SIP URI in the HSS and the newly assigned IP address Note: this would normally require a MSISDN+IMSI (IMSI for authentication and MSISDN generally required in all
49、 back-office IT/IS). Remote-originated messages: 1) The machine wakes up on schedule and establishes a SIP session with the SIP server 2) The machine generates a report as a short message then transmits that to the SIP server as a message payload. If the message is more than 1500 bytes, then concatenated messages are sent. 3) The SIP server acknowledges receipt of the message 4) The machine terminates the SIP session 5) The machine goes back to sleep Remote-terminated messages: 1) The Snack network generates a message addressed
