This Technical Report studies and evaluates architectural aspects of the System Improvements for Machine Type Communications requirements specified in TS 22.368
Specifically, the following system improvements are considered:
Architectural enhancements to support a large number of Machine-Type Communication (MTC) devices in the network;
Architectural enhancements to fulfil MTC service requirements;
Support combinations of architectural enhancements for MTC, though not all combinations may by possible.
The end-to-end aspects of communication between MTC devices and MTC servers (which can be located outside or inside the network operator's domain) are out of the scope of this study. However, the transport services for MTC as provided by the 3GPP system and the related optimizations are considered in this study. In addition, the aspects needed to ensure that MTC devices and/or MTC servers and/or MTC applications do not cause peak loads of short duration (e.g. a "busy minute" rather than a "busy hour") are within the scope of this TR.
Even though some provided solutions may be beneficial for communications from a MTC Device towards another MTC Device, this particular type communication has not been explicitly considered in this Technical Report.
This Technical Report analyzes architectural aspects to achieve these objectives and to gather technical content until it can be included in the relevant technical specifications.
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
: "Vocabulary for 3GPP Specifications".
: "Service Requirements for Machine-Type Communications".
NAT Traversal through Tunnelling (NATTT) available at: http://www.cs.arizona.edu/~bzhang/nat/nattt.htm
: "Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based services and Packet Data Networks (PDN)".
: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
: "Technical Realization of the Short Message Service (SMS)".
ITU T Recommendation E.118: "Operation, numbering, routing and mobile service - International operation - General provisions concerning Administrations".
ETSI TS 102 221: "UICC-Terminal interface; Physical and logical characteristics".
: "Value-added Services for SMS (VAS4SMS)".
: "Network sharing; Architecture and functional description".
: "Numbering, Addressing and Identification".
: "Domain Name System Procedures; Stage 3".
: "IP Multimedia Subsystem (IMS); Stage 2".
: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2".
: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3".
: "Mobile Application Part (MAP) specification".
: "Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol".
: "Architecture Enhancements to facilitate communications with Packet Data Networks and Applications".
: "General Packet Radio Service (GPRS); Service description; Stage 2".
: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2".
For the purposes of the present document, the terms and definitions given in TR 21.905
, TS 22.368
, and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905
Identifier used from outside the 3GPP system (e.g. at the MTCsp interface), to refer to a UE using a subscription (or the subscription itself e.g. when UE is not registered).
Identifier used within the 3GPP system to uniquely identify a UE using a subscription (or the subscription itself e.g. when the UE is not registered). In Rel-11, IMSI is the internal identifier in the 3GPP network for mapping to/from an external identifier.
For the purposes of the present document, the abbreviations given in TR 21.905
and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905
Machine Type Communications