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.
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.
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.
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.
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.