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:  18.5.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. 9

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 Application Client and the MSGin5G Client over the MSGin5G-5 interfaces; and
  3. communication between the MSGin5G Client residing on the Constrained UE and the MSGin5G Gateway Client 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. 9

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".
[20]
TS 29.641: "3GPP registry for Service Names and Port Numbers".
[21]
TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".
[22]
TS 23.433: "Service Enabler Architecture Layer for Verticals (SEAL); Data Delivery enabler for vertical applications".
[23]
TS 24.543: "Data Delivery Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".
[24]
TS 33.535: "Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS)".
Up

3  Definitions of terms, symbols and abbreviations  p. 10

3.1  Terms  p. 10

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:
Application Client
Broadcast Area
Messaging Topic
MSGin5G Client
MSGin5G Gateway Client
MSGin5G Gateway UE
MSGin5G Group
MSGin5G Service
MSGin5G Server
MSGin5G UE
Non-3GPP UE
Non-MSGin5G UE
Constrained UE
Up

3.2  Symbols  p. 11

Void

3.3  Abbreviations  p. 11

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
SEALDD
SEAL Data Delivery
SDDM
SEAL Data Delivery Management
SDDM-C
SEAL Data Delivery Management Client
SDDM-S
SEAL Data Delivery Management Server
Up

4  General description  p. 11

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; and
  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; and
  3. Non-3GPP UE.
MSGin5G Service also provides the following capabilities to enhance the message delivery for all message communication models:
  • MSGin5G Store and Forward;
  • Message delivery based on Messaging Topic;
  • Message Aggregation;
  • Message Segmentation and Reassembly; and
  • Usage of Network Capabilities including UE reachability status monitoring and MSGin5G device triggering.
The MSGin5G Client contained in the MSGin5G UE communicates with the MSGin5G Server over the MSGin5G-1 reference point (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.
An MSGin5G Client may reside in a Constrained UE which cannot connect to the 3GPP network directly for message exchange with MSGin5G Server (e.g. the Constrained UE is out of 3GPP RAN coverage, with or without authorization to use UE-to-Network relay). If allowed by configuration, the MSGin5G Client residing in a Constrained UE can use the options listed below to communicate with the MSGin5G Server:
  • the MSGin5G Client residing in a Constrained UE uses another UE as UE-to-Network relay. In this scenario, the MSGin5G Client residing on the Constrained UE communicates with the MSGin5G Server over the MSGin5G-1 reference point (see TS 23.554); or
  • the MSGin5G Client residing in a Constrained UE interacts with an MSGin5G Gateway UE which supports MSGin5G Gateway Client. The MSGin5G Gateway UE provides access to multiple Constrained UEs to connect to the 3GPP network for MSGin5G services. In this scenario, the MSGin5G Client residing in the Constrained UE communicates with the MSGin5G Gateway Client residing on the MSGin5G Gateway UE over the MSGin5G-6 reference point (see TS 23.554) for sending and receiving MSGin5G messages. The transport protocols of MSGin5G-6 reference point is also based on CoAP specified in IETF RFC 7252 [5].
An Application Client may reside on the same UE with the MSGin5G Client or reside on a different UE. The Application Client communicates with the MSGin5G Client over the MSGin5G-5 reference point (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 reference point, 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;
  3. Messaging Topic Subscription and Unsubscription; and
  4. MSGin5G UE bulk registration and bulk de-registration towards the MSGin5G Server.
By means of using the MSGin5G-5 reference point, the following aspects can be provided:
  1. Application Client registration and de-registration towards the MSGin5GClient; and
  2. The exchanging of message and message delivery status report between the Application Client and the MSGin5G Server by using MSGin5G Client.
By means of using MSGin5G-6 reference point, the following aspects can be provided:
  1. Constrained UE registration and de-registration towards the MSGin5G Server by using MSGin5G Gateway UE;
  2. The exchanging of MSGin5G message and MSGin5G message delivery status report between Constrained UE and MSGin5G Server by using MSGin5G Gateway UE; and
  3. The bulk registration and de-registration procedures from multiple Constrained UEs towards the MSGin5G Server by using MSGin5G Gateway UE.
The authentication between the MSGin5G Client and the MSGin5G Server shall be based on DTLS with AKMA as specified in Annex C of TS 33.535.
Up

5  Functional entities  p. 13

5.1  MSGin5G Client  p. 13

5.1.1  General functionalities of MSGin5G Client  p. 13

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 another UE without MSGin5G Client;
  4. delivering MSGin5G message payload to the targeted Application Client;
    1. directly when the Application Client resides on the same MSGin5G UE or;
    2. over MSGin5G-5 reference point when the Application Client resides on another UE without MSGin5G Client by acting as a gateway;
  5. exchanging MSGin5G messages with an MSGin5G Server; and
  6. supporting MSGin5G message aggregation and segmentation according to service provider's policy.
Up

5.1.2  MSGin5G Gateway Client  p. 13

An MSGin5G Gateway Client is an MSGin5G Client which supports MSGin5G Gateway service functionality in additional to the MSGin5G Client functionalities specified in clause 5.1.1. It enables constrained devices to obtain services from the MSGin5G Server when communications via ProSe UE-to-Network Relay are not or cannot be supported.
The MSGin5G Gateway service functionality in the MSGin5G Gateway Client supports the bulk configuration and bulk (de-)registration for the MSGin5G Client residing on the Constrained UE, e.g. checking whether bulk configuration/bulk (de-)registration can be used, holding the (de-)registration request from MSGin5G Client residing on the constrained device, construction of the bulk (de-)registration request and splits of the MSGin5G UE bulk (de-)registration response, etc.
Up

5.2  MSGin5G Server  p. 13

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 aggregation and 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