5 MC Service General Architecture
29.2833GPPDiameter data management applicationsRelease 17TS
5.1 Introduction
This clause further specifies the architectural assumptions associated with the MCPTT-2, MDVideo-2, MCData-2 and CSC-13 reference points, building on respectively 3GPP TS 23.379 [18], 3GPP TS 23.281 [19], 3GPP TS 23.282 [20] and 3GPP TS 23.280 [21].
5.2 Functional requirements of network entities
5.2.1 Functional Requirements of the MC Service Server
Depending on the MC Service, the MC Server is:
– the MCPTT Server for MCPTT services, as defined in 3GPP TS 23.379 [18],
– the MCVideo Server for MCVideo services, as defined in 3GPP TS 23.281 [19],
– and the MCData Server for MCData services, as defined in 3GPP TS 23.282 [20].
The MC Service Server may communicate with the MC Service User Database over:
– the MCPTT-2 interface between the MCPTT Server and the MCPTT User Database;
– the MCVideo-2 interface between the MCVideo Server and the MCVideo User Database;
– the MCData-2 interface between the MCData Server and the MCPTT User Database.
For more details on the functionality of the MC Service Server, refer to 3GPP TS 23.379 [18], 3GPP TS 23.281 [19] and 3GPP TS 23.282 [20], depending on the MC Service.
5.2.2 Functional Requirements of the Configuration Management Server
The Configuration Management Server may communicate with the MC Service User Database over the CSC-13 interface.
For more details on the functionality of the Configuration Management Server, refer to 3GPP TS 23.280 [21].
5.2.3 Functional requirements of MCPTT User Database
Depending on the MC Service, the MC Service User Database is:
– the MCPTT user database for MCPTT services, as defined in 3GPP TS 23.379 [18],
– the MCVideo user database for MCVideo services, as defined in 3GPP TS 23.281 [19],
– and the MCData user database for MCData services, as defined in 3GPP TS 23.282 [20].
These MC service user databases can be co-located.
The MCPTT User Database may communicate with the MCPTT Server over the MCPTT-2 interface.
The MCVideo User Database may communicate with the MCVideo Server over the MCVideo-2 interface.
The MCData User Database may communicate with the MCData Server over the MCData-2 interface.
Any MC Service User Database may communicate with the Configuration Management Server over the CSC-13 interface.
For more details on the functionality of the MC Service User Database, refer to 3GPP TS 23.280 [21], 3GPP TS 23.379 [18], 3GPP TS 23.281 [19] and 3GPP TS 23.282 [20] depending on the MC Service.
5.3 Functional classification of MC Service Server to MC Service User Database related interface procedures
MC Service Server to MC Service User Database interfaces are:
– The MCPTT-2 interface between the MCPTT User Database and the MCPTT Server;
– The MCVideo-2 interface between the MCVideo User Database and the MCVideo Server;
– The MCData-2 interface between the MCData User Database and the MCData Server.
Operations on the MC Service Server to MC Service User Database interfaces are classified in functional groups:
1. Data handling procedures
– The download of data from the MC Service User Database to an MC Service Server.
– The subscription to notifications from the MC Service User Database when particular information about a specific MC Service User is updated.
– The MC Service User Database can notify an MC Service Server of changes in data for which the MC Service Server previously had subscribed.
5.4 Functional classification of CSC-13 interface procedures
Operations on the CSC-13 interface are classified in functional groups:
1. Data handling procedures
– The download of data from the MC Service User Database to a Configuration Management Server.
– The update of data in the MC Service User Database.
– The subscription to notifications from the MC Service User Database when particular information about a specific MC Service User is updated.
– The MC Service User Database can notify a Configuration Management Server of changes in data for which the Configuration Management Server previously had subscribed.