tech-invite   World Map     

3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search

Top        in Index        Prev        None

TR 22.988 (SA1)
Study on alternatives to E.164 for Machine-Type Communications (MTC)

|   ToC   |   3GPP‑Page   |   ETSI‑search   |   Help   |

(P) V14.0.0    2017/03    29 p.
(P) V13.0.0    2016/01    29 p.
(P) V12.2.0    2012/09    29 p.

Rapporteur:  Mr. Jones, Gary
See also:  MTC-related TS/TR    

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 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 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 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 these MTC services but also the GSM/UMTS service providers in general.

This document seeks to study and highlight the challenge of using the existing public numbering resources to support Machine Type Communication (MTC) services and proposes that 3GPP develop an alternative to using public numbering resources for MTC communications.


Here        Top


1 Scope    2 References    3 Definitions, symbols and abbreviations    3.1 Definitions    3.2 Symbols    3.3 Abbreviations    4 Use cases    4.1 Use case 1 (Wireless Vending Machines)    4.2 Use case 2 (Smart Bridges and Tunnels)    4.3 Use case 3 Implantable Defibrillators    4.4 Use case 4 (Wireless Utility Meters)    4.5 Use case 5 (Wireless Weather Monitors)    5 High level Service Aspects    5.1 What are the high level requirements for alternatives to E.164 for machine-type communications?    5.2 What are the security, reliability, and priority handling requirements for alternatives to E.164 for machine-type communications?    5.3 Are there any implications due to roaming?    5.4 Are there any implications on inter-domain routing?    5.5 Are there any implications to hand-over between access networks?    6 MMI Aspects    7 Charging Aspects    8 Security Aspects    9 Analysis    9.1 MSISDN (E.164) with existing number length    9.2 MSISDN (E.164) with max length of 15 digits    9.3 E.212 Numbers (IMSI)    9.4 Other Numbering Plan Indicator in MAP    9.5 Generic Uniform Resource Identifier (URI)    9.6 Fully Qualified Domain Name (FQDN)    9.7 IPv4 Address    9.8 IPv6 Address    9.9 Network Access Identifier (NAI)    10 Conclusion    11 Potential requirements for alternatives to E.164 for machine-type communications    A Additional Definitions    B Change history   


1   Scope   PDF-p. 6
2   References
3   Definitions, symbols and abbreviations
4   Use cases
5   High level Service Aspects   PDF-p. 16
6   MMI Aspects      Up
7   Charging Aspects   PDF-p. 19
8   Security Aspects
9   Analysis
10   Conclusion
11   Potential requirements for alternatives to E.164 for machine-type communications   PDF-p. 25
A   Additional Definitions   PDF-p. 26
B   Change history   PDF-p. 27

Up        Top