Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.554  Word version:  18.0.0

Top   Top   Up   Prev   Next
1…   4…   5…   5.5…   6…   7…   8…   8.2…   8.2.3…   8.2.5…   8.3…   8.3.4…   8.4…   8.5…   8.6…   8.7…   8.7.2…   8.7.3…   8.7.4…   8.7.5…   8.8…   8.9…   8.9.3…   8.10…   8.11…   9…   10…

 

8.10  Usage of SEALp. 100

8.10.1  Generalp. 100

The MSGin5G Service functional entities MSGin5G Client and MSGin5G Server utilize the SEAL services. All SEAL services specified in TS 23.434 are available to MSGin5G Service. In this clause, only the details of the information flows, procedures and APIs whose utilization by MSGin5G Service are well-known are described.

8.10.2  Configuration management servicep. 101

8.10.2.1  Generalp. 101

The MSGin5G Service functional entities MSGin5G Client and MSGin5G Server utilize configuration management service procedures of SEAL to support MSGin5G Service.

8.10.2.2  Information flowsp. 101

The following information flows of Configuration Management service are applicable for the MSGin5G Service:
Information element Status Description
MSGin5G UE informationOOther information needed by the configuration procedure.(NOTE)
NOTE:
The information can be the device type, device Vendor, etc. It is specified by application provider or MSGin5G Service provider and is out of scope of this document. The MSGin5G Service provider can configure the MSGin5G UE with different configuration data based on this IE. E.g. all sensors can be configured to a same MSGin5G Server.
Information element Status Description
UE service IDMMSGin5G Service ID assigned to the requesting MSGin5G UE.
MSGin5G Server addressMThe MSGin5G Server which serves this MSGin5G UE.
MSGin5G Service specified informationOThe specific information of the MSGin5G Service specified by the MSGin5G Service provider. (NOTE)
NOTE:
E.g. the segment size of MSGin5G message in this service provider, the detailed definition is out of scope of this document.
The usage of the above information flows are clarified as below:
  • The VAL UE ID is the MSGin5G UE ID;
  • VAL service ID is the service identifier of the MSGin5G Service; and
  • VAL UE configuration data is the MSGin5G UE configuration data.
Up

8.10.2.3  Proceduresp. 101

The following procedures of configuration management service are applicable for the MSGin5G Service:

8.10.3  Group management servicep. 102

8.10.3.1  Generalp. 102

The MSGin5G Service functional entities MSGin5G Client and MSGin5G Server utilize SEAL Client and SEAL Server for the group management service (e.g. creation, join, leave) on the group configuration information (e.g. group join policy, group leader) provided by the MSGin5G Server. The decisions and corresponding triggers (e.g. group creation, join, leave and deletion) for group management are responsibility of the application leveraging MSGin5G Service. The group management service of SEAL provides support for creating group for MSGin5G Service for applications leveraging MSGin5G Service.
Up

8.10.3.2  Information flowsp. 102

8.10.3.3  Proceduresp. 102

The following procedures of group management service of SEAL as specified in TS 23.434 are applicable for the MSGin5G Service:
  • Group creation specified in clause 10.3.3;
    • Subsequent to Step 3, when the identity list with the list of VAL user IDs or VAL UE IDs that are part of the created group contain the list of VAL user IDs or VAL UE IDs which does not have group management client (e.g. Legacy 3GPP UEs, Non-3GPP UEs or Application Server), it is responsibility of the VAL server (MSGin5G Server) to initiate the group creation notification towards those UEs.
  • Group configuration management specified in clause 10.3.6;
  • Group deletion specified in clause 10.3.13.
  • Group membership update specified in clause 10.3.5.2.
Up

8.10.3.4  APIsp. 102

The following APIs of group management service of SEAL as specified in TS 23.434 are applicable for the MSGin5G Service:

Up   Top   ToC