Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 22.368  Word version:  16.0.0

Top   Top   None   None   Next
1…   5…   7…   A…

...

1  ScopeWord‑p. 5

The present document specifies the service requirements for Network Improvements for Machine Type Communications. In particular it will:
  • identify and specify general requirements for machine type communications;
  • identify service aspects where network improvements (compared to the current human-to-human oriented services) are needed to cater for the specific nature of machine-type communications;
  • specify machine type communication requirements for these service aspects where network improvements are needed for machine type communication.
Up

2  References

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.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 22.011: "Service accessibility".
[3]
TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[4]
ETSI TS 102 690: "Machine-to-Machine communications (M2M); functional architecture".
[5]
ETSI TS 102 921: "Machine-to-Machine communications (M2M); mla, dla, and mld interfaces".
Up

3  Definitions and abbreviations

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TR 21.905 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.
MTC Device:
A MTC Device is a UE equipped for Machine Type Communication, which communicates through a PLMN with MTC Server(s) and/or other MTC Device(s).
MTC Feature:
MTC Features are network functions to optimize the network for use by M2M applications.
MTC Group:
A MTC Group is a group of MTC Devices that share one or more MTC Features and that belong to the same MTC Subscriber.
MTC Server:
A MTC Server is a server, which communicates to the PLMN itself, and to MTC Devices through the PLMN. The MTC Server can also have an interface which can be accessed by the MTC User. The MTC Server can:
  • Provide services for other servers (e.g. The MTC Server is a Services Capability Server TS 23.682 for an Application Server [3]), and/or
  • Provide services for applications and can host the application (e.g. The MTC Server is an Application Server [3]).
MTC User:
A MTC User uses the service provided by the MTC Server.
MTC Subscriber:
A MTC Subscriber is a legal entity having a contractual relationship with the network operator to provide service to one or more MTC Devices.
Up

3.2  AbbreviationsWord‑p. 6

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.
NIMTC
Network Improvements for Machine Type Communications
MNO
Mobile Network Operator
MTC
Machine-Type Communications

4  Overview of system optimizations for machine-type communicationsWord‑p. 7

Machine-type communication is a form of data communication which involves one or more entities that do not necessarily need human interaction.
A service optimized for machine type communications differs from a service optimized for Human to Human communications. Machine-type communications is different to current mobile network communication services as it involves:
  1. different market scenarios,
  2. data communications,
  3. lower costs and effort,
  4. a potentially very large number of communicating terminals with,
  5. to a large extent, little traffic per terminal.
For the purpose of the present document, the term MTC is used for the purpose to describe use-cases and illustrate the diverse characteristics of machine-type communication services.
The informative annex A gives an overview of MTC use-cases which also illustrate different overload scenarios which will require overload control functions to prevent overload and to differentiate between services offered to different subscribers with different service requirements. In particular, certain MTC services and MTC applications, as exemplified in annex B, are more tolerant and can accept a lower level of performance requirements for its communication services. However, some MTC services will have similar service requirements as current mobile network communication services.
Up

Up   Top   ToC