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…

 

5.5  Capability exposure for enabling MSGin5G Servicep. 19

5.5.1  MSGin5G application enabler layer adaptation to CAPIFp. 19

The MSGin5G Server and Application Server may support CAPIF. When CAPIF is supported:
  • The MSGin5G Server shall support the CAPIF API provider domain functions (i.e. CAPIF-2/2e, CAPIF-3/3e, CAPIF-4/4e and CAPIF-5/5e as specified in TS 23.222) as shown in Figure 5.5.1-1;
  • The Application Server shall act as API invoker and support the API invoker functions (i.e. CAPIF-1/1e and CAPIF-2/2e as specified in TS 23.222) as shown in Figure 5.5.1-1.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 5.5.1-1: MSGin5G adaptation to the CAPIF architecture
Up

5.6  Service based interface representation for MSGin5G Servicep. 19

5.6.1  Generalp. 19

The Service based architecture for MSGin5G Service is represented using functional entities and reference points between the functional entities as specified in subclause 5.

5.6.2  Service based architecturep. 19

Figure 5.6.2-1 is the Service based Architecture for MSGin5G Service.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 5.6.2-1: Service based MSGin5G Architecture
Figure 5.6.2-1: Service based MSGin5G Architecture
(⇒ copy of original 3GPP image)
Up
The M5S function is a service based function exhibited by MSGin5G Server.
The M5C function is the MSGin5G Client.
The AC is the application client.
The L3G function is a service based function exhibited by Legacy 3GPP Message Gateway.
The N3G function is a service based function exhibited by Non-3GPP Message Gateway.
The M5S manages the distribution of the messages it has received from MSGin5G UE, from Application Server, or from N3G (on behalf of Non-3GPP UE) or from L3G (on behalf of Legacy 3GPP UE).
The M5S invokes services provided by L3G/N3G to send MSGin5G Messages towards Legacy 3GPP UE or Non-3GPP UE.
The AS/L3G/N3G invokes services provided by M5S to send MSGin5G Messages to M5S on behalf of Legacy 3GPP UE or Non-3GPP UE.
The M5S invokes services provided by SEAL Group management function to do MSGin5G Group management.
The M5S/L3G/N3G invokes services provided by SEAL Configuration management function to do service configuration (including UE service ID provisioning).
Up

5.6.3  Service based interfacesp. 20

Table 5.6.3-1 specifies the service based interfaces supported by MSGin5G Service.
Service based interface Application function entity Mapping server entity APIs offered
Mm5sMSGin5G Server functionMSGin5G ServerSpecified in clause 9.1
Ml3gLegacy 3GPP Message Gateway functionLegacy 3GPP Message GatewaySpecified in clause 9.2.1
Mn3gNon-3GPP Message Gateway functionNon-3GPP Message GatewaySpecified in clause 9.2.2
Up

Up   Top   ToC