Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.280  Word version:  19.0.1

Top   Top   Up   Prev   Next
1…   5…   5.2.8…   6   7…   7.3.2   7.4…   7.4.3…   7.5…   8…   9…   9.2.2…   9.2.2.2…   9.3…   10…   10.1.2…   10.1.3…   10.1.4.3…   10.1.4.5…   10.1.5…   10.1.6…   10.2…   10.2.3…   10.2.4.2…   10.2.4.3…   10.2.5…   10.2.7…   10.3…   10.6…   10.7…   10.7.3…   10.7.3.4…   10.7.3.7…   10.7.3.7.3   10.7.3.8…   10.7.3.10…   10.8…   10.8.4…   10.8.5…   10.9…   10.9.3…   10.9.3.5…   10.9.3.8…   10.9.3.9…   10.9.3.9.3…   10.9.3.9.4…   10.9.3.10…   10.9.3.10.4…   10.9.3.10.6…   10.10…   10.10.1.2.3…   10.10.2…   10.10.3…   10.10.3.3…   10.10.3.4…   10.11…   10.11.5…   10.12…   10.13…   10.13.3…   10.13.7…   10.13.10…   10.14…   10.15…   10.15.3…   10.15.3.3…   10.15.3.4…   10.16…   10.16.3…   11…   11.3…   11.5…   11.5.2…   11.5.3…   11.5.3.3.2A…   11.5.4…   A…   B…   C…

 

9.2.2.2  MC service user database, SIP database and HSSp. 61

Figure 9.2.2.2-1 to Figure 9.2.2.2-4 show the possible deployment scenarios of the MC service user database and SIP database, including collocation with the HSS.
The MC service user database may be combined with an HSS in some deployment scenarios (e.g. when the MC service provider and the PLMN operator are part of the same trust domain).
The MC service user database may be a user data repository (UDR) in deployment scenarios when the UDC architecture is applied (see TS 23.335), in that case the MC service server and the configuration management server are assumed to be application front-ends and the Ud interface is used to access data from the repository.
Reproduction of 3GPP TS 23.280, Fig. 9.2.2.2-1: Collocation of MC service user database and SIP database with HSS
Up
The HSS depicted in Figure 9.2.2.2-1 can be deployed either in the PLMN operator's network or the MC service provider's network.
Reproduction of 3GPP TS 23.280, Fig. 9.2.2.2-2: Shared PLMN operator and MC service provider based deployment of MC service - SIP database collocated with HSS with separate MC service user database
Up
The MC service user database depicted in Figure 9.2.2.2-2 can be deployed in the PLMN operator's network or the MC service provider's network, and the HSS depicted in Figure 9.2.2.2-2 can be deployed in the same or different network to the MC service user database i.e. PLMN operator's network or the MC service provider's network.
Reproduction of 3GPP TS 23.280, Fig. 9.2.2.2-3: Shared PLMN operator and MC service provider based deployment of MC service - MC service user database and SIP database deployed together, with separate HSS
Up
The MC service user database and SIP database depicted in Figure 9.2.2.2-3 can be deployed in the PLMN operator's network or the MC service provider's network, and the HSS depicted in Figure 9.2.2.2-3 can be deployed in the same or different network to the MC service user database i.e. PLMN operator's network or the MC service provider's network.
Reproduction of 3GPP TS 23.280, Fig. 9.2.2.2-4: Shared PLMN operator and MC service provider based deployment of MC service - separate HSS, MC service user database and SIP database
Up
Each of the MC service user database, SIP database and HSS depicted in Figure 9.2.2.2-4 can be deployed in the same or different networks i.e. PLMN operator's network or the MC service provider's network.

9.2.2.3  Control of bearers by SIP core and MC service serverp. 64

9.2.2.3.1  Generalp. 64
This subclause describes two different scenarios in which bearers are controlled by access to Rx by either the SIP core or the MC service server.
These may provide suitable models for each of the scenarios listed in subclause 9.2.2.1. However, there is no direct correlation of any of the scenarios described in this subclause to each of the scenarios described in subclause 9.2.2.1.
Up
9.2.2.3.2  Control of bearers by SIP corep. 64
In this scenario, bearer control is performed by the SIP core alone, as shown in Figure 9.2.2.3.2-1 below.
Reproduction of 3GPP TS 23.280, Fig. 9.2.2.3.2-1: Bearer control by SIP core
Up
9.2.2.3.3  Control of bearers by MC service serverp. 64
In this scenario, bearer control is performed by the MC service server alone, as shown in Figure 9.2.2.3.3-1 below.
Reproduction of 3GPP TS 23.280, Fig. 9.2.2.3.3-1: Bearer control by MC service server
Up

Up   Top   ToC