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…

 

4  Architectural requirementsp. 10

4.1  Generalp. 10

4.1.1  Descriptionp. 10

This subclause specifies the general architecture requirements for MSGin5G Service.

4.1.2  Requirementsp. 11

[AR-4.1.2-a]
The MSGin5G Client shall support one or more applications which need to use the MSGin5G message exchanging capabilities.
[AR-4.1.2-b]
The MSGin5G Server shall support one or more Applications Servers which support the MSGin5G message exchanging capabilities.
[AR-4.1.2-c]
The MSGin5G messaging related capabilities (e.g. registration, Point-to-Point messaging, Group messaging, message delivery status, etc.) should be exposed as APIs to the Applications Server(s).
[AR-4.1.2-d]
The application architecture shall enable the communication between the UEs in different PLMNs. The UEs support MSGin5G Service.
[AR-4.1.2-e]
The MSGin5G service should support different application priority levels for the MSGin5G messages Including High, Normal and Low.
Up

4.2  UE typesp. 11

4.2.1  Descriptionp. 11

This subclause specifies the requirements for UE types supported by MSGin5G Service.

4.2.2  Requirementsp. 11

[AR-4.2.2-a]
The application architecture shall support the message exchanging between the following UE types:
  1. MSGin5G UE:
    1. light weight constrained devices (e.g. sensors, actuators) and
    2. unconstrained devices with advanced capabilities (e.g. washing machine, micro-ovens)
  2. Legacy 3GPP UE
  3. Non-3GPP UE
[AR-4.2.2-b]
The application architecture shall enable the unconstrained devices to act as a UE Message Gateway to constrained devices to communicate with MSGin5G Server.

4.3  Communication modelsp. 11

4.3.1  Descriptionp. 11

This subclause specifies the requirements for MSGin5G communication models.

4.3.2  Requirementsp. 11

[AR-4.3.2-a]
The application architecture shall support 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.
[AR-4.3.2-b]
The application architecture shall support the interconnecting between MSGin5G and other different messaging delivery mechanisms, e.g. SMS specified in TS 23.040, or RCS message as specified in GSMA PRD RCC.07 [3]).

4.4  Charging |R18|p. 12

4.4.1  Introductionp. 12

This subclause specifies the charging related requirements for the MSGin5G Service.

4.4.2  Requirementsp. 12

[AR-4.4.2]
The MSGin5G Server shall support collecting charging information from MSGin5G message according to the operator's charging policy including charge per message, charge by amount of data, and flat rate (e.g., per month or per year).

Up   Top   ToC