Content for  TS 23.280  Word version:  19.1.0

The configuration management client functional entity acts as the application user agent for configuration related transactions. The configuration management client interacts with the configuration management server and provides and receives configuration data. The configuration management client functional entity is supported by the signalling user agent and HTTP client functional entities of the signalling control plane. The configuration management client provides the functional alias management client functionality as described in subclause 7.4.2.2.12.

The configuration management server is a functional entity used to configure one or more MC service applications with non-group management MC service related information and configure data on the configuration management client. The configuration management server manages MC service configuration supported within the MC service provider. The configuration management server functional entity is supported by the SIP AS and HTTP server functional entities of the signalling control plane. The configuration management server provides the functional alias management server functionality as described in subclause 7.4.2.2.13.

The group management client functional entity acts as the application user agent for management of groups. A MC system maintains groups corresponding to one or more mission critical organizations. The group management client interacts with the group management server. The group management client functional entity is supported by the signalling user agent and HTTP client functional entities of the signalling control plane.

The group management server functional entity provides for management of groups supported within the MC service provider. The group management server functional entity is supported by the SIP AS and HTTP server functional entities of the signalling control plane. All the group management clients supporting users belonging to a single group are required to use the same group management server for that group. A group management client supporting a user involved in multiple groups can have relationships with multiple group management servers. The group management server manages media policy information for use by the UE for media processing. The group management server manages group call policy information for use by the UE for both on-network and off-network group call control.

This functional entity acts as the application user agent for MC ID transactions. It interacts with the identity management server.

The identity management server is a functional entity that is capable of authenticating the MC ID. It contains the knowledge and means to do authentication by verifying the credentials supplied by the user. The identity management server functional entity may reside in the same domain as the user's MC system.

This functional entity acts as the application user agent for key management functions. It interacts with the key management server. The functionality of the key management client is specified in TS 33.180.

The key management server is a functional entity that stores and provides security related information (e.g. encryption keys) to the key management client, group management server and MC service server(s) to achieve the security goals of confidentiality and integrity of media and signalling. The functionality of the key management server is specified in TS 33.180.

This functional entity acts as the application user agent for location management functions. It interacts with the location management server.

The location management server is a functional entity that receives and stores user location information, and provides user location information to the MC service server. The location management server may also acquire location information provided by PLMN operator (e.g. LCS network).

The migration management server is used in migration from the SIP core of the primary MC system to the SIP core of the partner MC system. In the SIP core of the primary MC system, the migration management server provides configured SIP identities to be used by a particular MC service UE in order to migrate to one or more SIP cores belonging to partner MC systems. In the SIP core of a partner MC system, the migration management server provides a point of authority for binding SIP identities of the SIP core of partner MC system and SIP identities of the SIP core for primary MC system. The migration management server is used during configuration of an MC service UE for MC service user migration (see subclause 10.1.6.1), and during SIP registration of an MC service UE's SIP user agent when migrating to the SIP core of a partner MC system (see subclause 10.6.2). A single set or multiple sets of SIP identities of the SIP core of the primary MC system for an MC service UE that is enabled for migration shall be configured in the primary MC system's migration management server. EXAMPLE: A unique set of partner MC system SIP identities for all possible inbound migrated MC service UEs shall be configured in the partner MC system's migration management server. The migration management server functional entity is supported by the Diameter proxy functional entity of the signalling control plane.

The functional alias management client functional entity acts as the application user agent for management of functional aliases. The functional alias management client interacts with the functional alias management server. The functional management client functional entity is supported by the signalling user agent and by the HTTP client functional entities of the signalling control plane.

The functional alias management server functional entity provides the configuration management of functional alias(es). The functional alias management server functional entity is supported by the SIP AS and by the HTTP server functional entities of the signalling control plane.

The ACM client is a functional entity that acts as the application user agent for an authorized user that is responsible for requesting, approving, and applying configurations between a primary MC system and partner MC system. These configurations include MC service user profile, group management, and associated system parameters. The administrative configuration management client interacts with the administrative configuration management server. The ACM client functional entity is supported by the signalling user agent and by the HTTP client functional entities of the signalling control plane.

The ACM server is a functional entity that provides the necessary capabilities to control and perform required transactions to exchange administrative configurations and/or information between partner MC system(s). ACM server has the following functions:

• Provides the temporary storage of configuration changes when requests are received from a partner MC system. The configuration changes include MC service user profile, group management configuration, and associated system parameters.
• Supports requests from the ACM client that result in exchanges with the partner MC system to share administrative configurations and information.
• Controls, processes, validates, accepts, forwards or rejects administrative configuration exchange based on a set of pre-defined rules and policies.

The administrative configuration management server functional entity is supported by the SIP AS and by the HTTP server functional entities of the signalling control plane.

The MC service client functional entity acts as the user agent for all MC service transactions. For a specific MC service, the detailed description of functions of the MC service client is contained in the corresponding MC service TS.

The MC service server functional entity provides centralised support for MC services. The MC service server functional entity represents a specific instantiation of the GCS AS described in TS 23.468 to control multicast and unicast operations for group communications. For a specific MC service, the detailed description of the GCS AS role assumed by the MC service server is contained in the corresponding MC service TS. The MC service server performs the functional alias controlling role for functional alias management including functional alias activation, deactivation, take over and interrogation. For a single functional alias, only one MC service server is specified as the functional alias controlling role. The detailed description of the functional alias controlling role assumed by the different MC service servers are contained in TS 23.379, TS 23.281 and TS 23.282. The MC service server functional entity is supported by the SIP AS, HTTP client and HTTP server functional entities of the signalling control plane.

This functional entity contains information of the MC service user profile associated with an MC service ID that is held by the MC service provider at the application plane. The MC service user profile is determined by the mission critical organization, the MC service provider, and potentially the MC service user. Each MC service shall have a corresponding MC service user database i.e. MCPTT user database as defined in TS 23.379, MCVideo user database as defined in TS 23.281 and MCData user database as defined in TS 23.282. These MC service user databases can be co-located.

The MC gateway server provides support for interconnection between a primary MC system and a partner MC system in a different trust domain whilst providing topology hiding. It acts as a proxy for one or more MC service servers in the partner MC system without needing to expose the MC service servers in the primary MC system outside the trusted domain of the primary MC system. It may be a role of an MC service server described in subclause 7.4.2.3.2 of the present document. The MC gateway server is responsible for relaying signalling control messages and media between MC service servers in the interconnected MC systems.