Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 24.538  Word version:  17.2.0

Top   Top   None   None   Next
1…   6… 
1 Scope  2 References  3 Definitions of terms, symbols and abbreviations  3.1 Terms  3.2 Symbols  3.3 Abbreviations  4 General description  5 Functional entities  5.1 MSGin5G Client  5.2 MSGin5G Server 
...

 

1  Scope  p. 8

The present document specifies the protocol aspects for supporting MSGin5G services as specified in TS 23.554 for:
  1. communication between the MSGin5G UE and the MSGin5G Server over the MSGin5G-1 interface;
  2. communication between the Constrained UE (without MSGin5G Client) and MSGin5G Gateway UE which is an Unconstrained UE over the MSGin5G-5 interfaces; and
  3. communication between the Constrained UE (with MSGin5G Client) and the MSGin5G Relay UE which is an Unconstrained UE over the MSGin5G-6 interfaces.
The present specification defines the usage and interactions of the MSGin5G Service with SEAL services.
The present specification also defines the message format, message contents, error handling and system parameters applied by the protocols for the MSGin5G Service.
Up

2  References  p. 8

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 23.554: "Application architecture for MSGin5G Service; Stage 2;".
[3]
TS 23.434: "Service Enabler Architecture Layer for Verticals".
[4]
RFC 7641:  "Observing Resources in the Constrained Application Protocol (CoAP)".
[5]
RFC 7252:  "The Constrained Application Protocol (CoAP)".
[6]
TS 24.546: "Configuration management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".
[7]
TS 29.538: "Enabling MSGin5G Service; Application Programming Interfaces (API) specification; Stage 3".
[8]
JSON Schema: "JSON Schema Draft-07", http://json-schema.org/specification.html
[9]
TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)".
[10]
TS 24.544: "Group Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".
[11]
TS 24.545: "Location Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".
[12]
TS 24.546: "Configuration Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".
[13]
TS 24.547: "Identity Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".
[14]
TS 24.548: "Network Resource Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".
[15]
TS 24.007: "Mobile radio interface signalling layer 3; General Aspects".
[16]
TS 33.501: "Security architecture and procedures for 5G system".
[17]
TS 23.502: " Procedures for the 5G System; Stage 2"
[18]
TS 23.003: "Numbering, addressing and identification".
[19]
RFC 4122:  "A Universally Unique IDentifier (UUID) URN Namespace".
Up

3  Definitions of terms, symbols and abbreviations  p. 9

3.1  Terms  p. 9

For the purposes of the present document, the terms 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.
For the purposes of the present document, the following terms and definitions given in TS 23.554 apply:
Broadcast Area
Messaging Topic
MSGin5G Client
MSGin5G Gateway UE
MSGin5G Group
MSGin5G Relay UE
MSGin5G Service
MSGin5G Server
MSGin5G UE
Non-3GPP UE
Non-MSGin5G UE
Constrained UE
Up

3.2  Symbols  p. 9

Void

3.3  Abbreviations  p. 10

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.
AF
Application Function
AS
Application Server
CAPIF
Common API Framework for northbound APIs
CoAP
Constrained Application Protocol
NIDD
Non IP Data Delivery
SCEF
Service Capability Exposure Function
SCS
Service Capability Server
SEAL
Service Enabler Architecture Layer for Verticals
Up

4  General description  p. 10

The MSGin5G Service (message service for MIoT over 5G System) is basically designed and optimized for massive IoT device communication including thing-to-thing communication and person-to-thing communication. The MSGin5G Service provides messaging communication capability in 5GS including the following message communication models:
  1. Point-to-Point message;
  2. Application-to-Point message/ Point-to-Application message;
  3. Group message;
  4. Broadcast message.
The MSGin5G Service support the message exchanging between the following UE types:
  1. MSGin5G UE:
    1. light weight Constrained UEs (e.g. sensors, actuators) and
    2. Unconstrained UEs with advanced capabilities (e.g. washing machine, micro-ovens).
  2. Legacy 3GPP UE.
  3. Non-3GPP UE.
The MSGin5G Client contained in the MSGin5G UE communicates with the MSGin5G Server over the MSGin5G-1 interface (see TS 23.554). CoAP specified in IETF RFC 7252 [5] is used as the basic transport protocol of MSGin5G service in this reference point and shall be supported by the MSGin5G Client and MSGin5G Server. For supporting sending/receiving MSGin5G message for the MSGin5G Client contained in Constrained UE, the transport protocols of MSGin5G-6 interface is also CoAP specified in IETF RFC 7252 [5].
An MSGin5G UE-1 may be Constrained UEs which do not have enough capability to communicate with MSGin5G Server. If allowed by configuration, an Unconstrained UE MSGin5G UE-2 may act as an MSGin5G Gateway UE or an MSGin5G Relay UE to MSGin5G UE-1. In this scenario, the MSGin5G UE-1 communicates with the MSGin5G UE-2 over the MSGin5G-5 and/or MSGin5G-6 interfaces (see TS 23.554).
Additionally, the MSGin5G Client(s) may interact with SEAL Clients over the SEAL-C reference point specified for each SEAL service as specified in TS 23.434. The MSGin5G Server(s) may interact with SEAL Servers over the SEAL-S reference point specified for each SEAL service as specified in TS 23.434. The interaction between a SEAL Client and the corresponding SEAL Server is supported by SEAL-UU reference point specified for each SEAL service as specified in TS 23.434.
By means of using the MSGin5G-1 interface, the following aspects can be provided:
  1. MSGin5G UE registration and de-registration towards the MSGin5G Server;
  2. MSGin5G message delivery and MSGin5G message delivery status report; and
  3. Messaging Topic Subscription.
By means of using the MSGin5G-5 interfaces, the following aspects can be provided:
  1. Constrained UE registration and de-registration towards the MSGin5G Gateway UE; and
  2. The exchanging of message and message delivery status report between Constrained UE and MSGin5G Server by using MSGin5G Gateway UE.
By means of using MSGin5G-6 interfaces, the following aspects can be provided:
  1. Constrained UE registration and de-registration towards the MSGin5G Server by using MSGin5G Relay UE; and
  2. The exchanging of MSGin5G message and MSGin5G message delivery status report between Constrained UE and MSGin5G Server by using MSGin5G Relay UE.
The necessary 5GC Network Capabilities, e.g. device triggering, may be used in MSGin5G Service as specified in TS 23.554. The device trigger is delivered to the MSGin5G Client via SCEF/NEF and the Core Network as specified in TS 23.502 and is out of scope of this document.
Up

5  Functional entities  p. 11

5.1  MSGin5G Client  p. 11

An MSGin5G Client acts as client-side functionality for MSGin5G UE configuration, registration and message delivery.
The functionalities of MSGin5G Client include:
  1. supporting registration to an MSGin5G Server;
  2. supporting configuration required to use MSGin5G Service;
  3. constructing MSGin5G message when:
    1. requested by an Application Client resides on the same MSGin5G UE or;
    2. requested by the Application Client resides on a Constrained UE without MSGin5G Client by acting as a gateway;
  4. delivering MSGin5G message payload to the targeted Application Client;
    1. directly when the Application Client resides on the same MSGin5G UE or;
    2. resides on a Constrained UE without MSGin5G Client by acting as a gateway;
  5. exchanging MSGin5G messages with an MSGin5G Server;
  6. supporting MSGin5G message segmentation according to service provider's policy;
  7. acting as a relay for MSGin5G Client resides in other UE, which does not have enough capability to communicate with MSGin5G Server (i.e. a Constrained UE), to use MSGin5G Service; and
  8. acting as a gateway to handle the registration and deregistration procedures initiated by the application client in a Constrained UE.
Up

5.2  MSGin5G Server  p. 12

An MSGin5G Server functional entity provides server-side functionality for configuration, registration and message delivery.
The following functionalities of MSGin5G Server need to be considered in current document:
  1. exchanging MSGin5G messages with MSGin5G Client;
  2. routing MSGin5G messages based on UE Service ID;
  3. supporting transport level protocol selection and conversion for exchanging MSGin5G messages with MSGin5G UE;
  4. to resolve the MSGin5G Group Service ID to determine the members of the Group specified in TS 23.434;
  5. supporting MSGin5G message segmentation according to service provider's policy;
  6. supporting MSGin5G UE configuration procedures as specified in TS 23.434 and TS 24.546 or communicating with the SEAL Configuration Management Server to provide MSGin5G configuration data on a UE to be ready for the MSGin5G Service; and
  7. managing MSGin5G UE information related to the MSGin5G Service, such as MSGin5G Client availability.
Up

Up   Top   ToC