Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.554  Word version:  19.3.0

Top   Top   Up   Prev   None
1…   4…   5…   5.3…   5.5…   6…   7…   8…   8.2…   8.2.7…   8.2.11   8.3…   8.3.5…   8.4…   8.4.3   8.5…   8.6…   8.7…   8.7.2…   8.7.3…   8.7.4…   8.7.5…   8.7.6…   8.8…   8.9…   8.10…   8.11…   9…   9.2…   10…   11…

 

11  Deployment models |R18|p. 140

11.1  Generalp. 140

This clause describes deployments of the functional model specified in clause 5.

11.2  Deployment of MSGin5G server(s)p. 140

The MSGin5G server(s) should be deployed in the PLMN operator domain. The VAL service using MSGin5G service for the message delivery acts as Application Server and interacts with MSGin5G Server via MSGin5G-3 reference point. The MSGin5G server(s) connects with the 3GPP network system in one or more PLMN operator domain. The MSGin5G server(s) may be supporting multiple Application Servers.
Figure 11.2-1 illustrates the deployment of multiple MSGin5G Servers in a single PLMN operator domain. Each MSGin5G Server serves a part of MSGin5G service subscribers (including the subscriber using the MSGin5G UE or Non-MSGin5G UE) in this PLMN operator domain. In this deployment, the MSGin5G Servers shall be connected with each other to provide the MSGin5G service to all MSGin5G service subscribers in the PLMN operator domain. The MSGin5G Servers provide MSGin5G service to the Application Server(s) deployed in the VAL service provider domain. The Application Server may be connected and registered to one MSGin5G Server.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 11.2-1: MSGin5G Server(s) deployed in a single PLMN operator domain with interconnection between MSGin5G Server(s)
Up
Figure 11.2-2 illustrates the deployment of MSGin5G Servers in multiple PLMN operator domains. Each MSGin5G Server serves the MSGin5G service subscribers in this PLMN operator domain. In this deployment, the MSGin5G Servers deployed in PLMN operator domain 1 may be connected with the MSGin5G deployed in PLMN operator domain 2 to provide the MSGin5G service interconnection based on the business agreement between PLMN operator 1 and PLMN operator 2.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 11.2-2: MSGin5G Server(s) deployed in multiple PLMN operator domain with interconnection between MSGin5G Server(s)
Up

11.3  Deployment of Message Gateway(s)p. 142

Figure 11.3-1 illustrates the deployment of Message Gateway in a single PLMN operator domain. If only one Message Gateway, i.e. Message Gateway 1 in Figure 11.3-1, is deployed, all MSGin5G Servers in this PLMN domain may connected to a single Message Gateway to provide the MSGin5G service for the Non-MSGin5G UEs. Multiple Message Gateways may also be deployed in a single PLMN operator domain. In this deployment, i.e. Message Gateway 1 and Message Gateway 2 in Figure 11.3-1 are deployed, each Message Gateway is used to provide MSGin5G service for a part of MSGin5G service subscribers in this PLMN operator domain.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 11.3-1: deployment of Message Gateway in a single PLMN operator domain
Up
Figure 11.3-2 illustrates the deployment of Message Gateway in multipl PLMN operator domains. The MSGin5G Server(s) in one PLMN domain are only connected the Message Gateway(s) in the same PLMN operator domain to provide the MSGin5G service for the Non-MSGin5G UEs served by this PLMN operator.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 11.3-2: deployment of Message Gateway in multipl PLMN operator domains
Up

11.4  Deployment of MSGin5G Server(s) and SEAL server(s)p. 143

If an MSGin5G Server interacts with SEAL Servers over the SEAL-S reference point specified for each SEAL service, i.e. the SEAL Server are not collocated in the MSGin5G Server, the application of functional model to deployments of SEAL servers specified in TS 23.434 applied. In the deployment, MSGin5G acts as the VAL servers specified in TS 23.434, but may be deployed in the PLMN operator domain.
Up

$  Change historyp. 144


Up   Top