Tech-invite3GPPspaceIETF RFCsSIP

Content for  TR 22.824  Word version:  16.0.0

Top   Top   None   None   Next
1…   5…


1  Scopep. 6

The present document develops use cases of message communication for MIoT, identifies 5G Message (5GMSG) service potential requirements, and identifies potential requirements on 5G system. The use cases include the following scenarios:
  • Efficient message communication
  • Low delay message communication
  • Group message communication
  • Multicast and broadcast message communication
  • High density of UEs message communication
    It also provides a gap analysis between the new requirements of message communication for MIoT and the existing operator's message services/3GPP network capabilities, and recommends the future work for the standardization of 5GMSG service for MIoT.
  • Up

    2  Referencesp. 6

    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.
    TR 21.905: "Vocabulary for 3GPP Specifications".
    TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications"
    TS 23.040: "Technical realization of the Short Message Service (SMS)"
    TS 23.041: "Technical realization of Cell Broadcast Service (CBS)"
    OMA OMA-ERELD-LightweightM2M-V1_1-20180612-C: "Enabler Release Definition for LightweightM2M"
    GSMA RCC.71: "RCS Universal Profile Service Definition Document"

    3  Definitions, symbols and abbreviationsp. 7

    3.1  Definitionsp. 7

    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.
    5GMSG Service:
    a MNO message service with the 5G System that enables point to point, application to point, broadcast, multicast and group message communications for IoT devices, including thing-to-thing communication and person-to-thing communication.
    5GMSG proxy/gateway:
    a device performing the interworking between 5G MSG and M2M system, or access of 5G IoT devices.
    Controller terminal:
    usually an intelligent terminal that can access the 5G network and sends the control message instructions to machine equipment. A controller terminal can control multiple controlled terminals.
    Controlled terminal:
    an IoT physical equipment which can access the network through a variety of technologies and network slicing. A controlled terminal can be controlled by a number of controller terminals.

    3.2  Symbolsp. 7

    For the purposes of the present document, the following symbols apply:

    3.3  Abbreviationsp. 7

    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.
    5G Message
    Application Programming Interface
    Cellular Internet of Things
    Constrained Application Protocol
    Data Resource Bearer
    Discontinuous Reception
    Hypertext Transfer Protocol
    IP Multimedia Subsystem
    Internet of Things
    JavaScript Object Notation
    Lightweight Machine to Machine
    Machine to Machine
    Multimedia Broadcast Multicast Service
    Massive Internet of Things
    Mobile Network Operator
    Non-IP Data Delivery
    Open Mobile Alliance
    Protocol Buffer
    Quality of Service
    Session Initiation Protocol
    Short Message Service
    Short Message Service-Cell Broadcast
    Signal Resource Bearer
    Extensible Markup Language

    4  Overviewp. 8

    Massive Internet of Things (MIoT) is one of key market segments of 5G. The typical IoT device communication is sending and receiving small data which can be delivered just in a message. Although an IoT application may implement its own message enabler or data communication enabler, it will introduce problems such as interoperability, signalling overhead etc. For the benefit of the IoT ecosystem, it is expected that MNOs provide advanced message service for MIoT.
    Today SMS is used as message enabler for some IoT applications. However SMS has limitation in term of service capabilities (e.g. 140 bytes payload) and performance (e.g. long latency), in addition, the overhead of control plane resource is high. There have been enhancements and optimizations on the 3GPP network capabilities to facilitate IoT applications including device triggering, small data transfer, Non IP Data Delivery (NIDD), and group messaging etc. Nevertheless, MIoT will bring various new demands on message communication, e.g. light weight message communication for provision and monitoring, ultra low delay and high reliability message communication for remote control, and extremely high resource efficiency for large scale connections.
    5GMSG Service is to be developed for this new and huge market segment. It enables an UE sending/receiving message of text, voice, video or data to/from another UE or application server. While SMS is originally designed for person-to-person communication, 5GMSG Service is basically designed for IoT device communication, including thing-to-thing communication and person-to-thing communication. The emerging IoT device communication will introduce new requirements of messaging service in terms of service capabilities, performance, charging, and security etc.
    The 5GMSG Service enables various messaging communications models including:
    • MOMT: UE A sends a message to UE B
    • MOAT: UE A sends a message to Application Server
    • AOMT: Application Server sends a message to UE A
    • MOMT-G: UE A sends a message to a group of UEs
    • AOMT-G: Application Server sends a message to a group of UEs
    • AOMT-B: Application Server broadcast a message to all UEs ( in a specific service area)
    The UEs can be handset and IoT devices. The message communication between two UEs can be with or without a 5GMSG Proxy/Gateway.

    Up   Top   ToC