4 General
24.4843GPPMission Critical Services (MCS) configuration managementProtocol specificationRelease 18TS
4.1 MCS service administrator configuration
4.1.1 Common configuration
An MCS service administrator can, using an MCS UE configure the:
– MCS UE initial configuration document;
The format of the MCS UE initial configuration document for configuration by an MCS service administrator is defined in clause 7.2.
To create a new configuration document on the configuration management server, the MCS UE uses the procedures in clause 6.3.2.2.
NOTE: If the MCS administrator includes a <Default-user-profile> element in the MCS UE initial configuration document as defined in clause 7.2.2.1, at least one instance of an MCS user profile configuration document needs to first be created on the configuration management server, containing the "XUI-URI" attribute and "user-profile-index" attribute (as defined in clause 8.3.2.1) that are included in the <Default-user-profile> element.
To update an existing configuration document on the configuration management server, the MCS UE uses the procedures in clause 6.3.4.2.
To delete an existing configuration document on the configuration management server, the MCS UE uses the procedures in clause 6.3.5.2.
To create a new MC group document on the configuration management server, the MCS UE uses the procedures in 3GPP TS 24.481 [5].
To update an existing MCPTT group document on the configuration management server, the MCS UE uses the procedures in 3GPP TS 24.481 [5].
To delete an existing MC group document on the configuration management server, the MCS UE uses the procedures in 3GPP TS 24.481 [5].
4.1.2 MCPTT configuration
An MCPTT service administrator can, using an MCPTT UE configure the:
– MCPTT UE configuration document;
– MCPTT user profile configuration document;
– MCPTT service configuration document; and
– MCPTT group document.
The format of the MCPTT UE configuration document is defined in clause 8.2.
The format of the MCPTT user profile configuration document is defined in clause 8.3.
The format of the MCPTT service configuration document is defined in clause 8.4.
The format of the MCPTT group document is defined in 3GPP TS 24.481 [5].
4.1.3 MCVideo configuration
An MCVideo service administrator can, using an MCVideo UE configure the:
– MCVideo UE configuration document;
– MCVideo user profile configuration document;
– MCVideo service configuration document; and
– MCVideo related group configuration data in the MCS group document.
The format of the MCVideo UE configuration document is defined in clause 9.2.
The format of the MCVideo user profile configuration document is defined in clause 9.3.
The format of the MCVideo service configuration document is defined in clause 9.4.
The format of the MCVideo related group configuration data in the MCS group document is defined in 3GPP TS 24.481 [5].
4.1.4 MCData configuration
An MCData service administrator can, using an MCData UE configure the:
– MCData UE configuration document;
– MCData user profile configuration document;
– MCData service configuration document; and
– MCData related group configuration data in the MCS group document.
The format of the MCData UE configuration document is defined in clause 10.2.
The format of the MCData user profile configuration document is defined in clause 10.3.
The format of the MCData service configuration document is defined in clause 10.4.
The format of the MCData related group configuration data in the MCS group document is defined in 3GPP TS 24.481 [5].
4.2 MCS UE configuration
4.2.1 General
Upon start up the MCS UE bootstraps the required information (e.g. FQDN or IP address) to locate the configuration management server for configuration of the MCS UE initial configuration management object (MO) and the default MCPTT user profile configuration management object (MO).
In order to obtain access to MC services the MCS UE needs to obtain configuration data either online via the network or offline using some external device (e.g. a laptop). As part of the bootstrap process the MCS UE needs to discover either:
1. the online configuration management server in the network that configures the MCS UE initial configuration MO and the default MCS user profile configuration MO(s), then the MCS UE:
a) using the URI of the configuration management server obtained from the MCS UE initial configuration MO, obtains for each MCS that is enabled:
– the appropriate MCS UE configuration document;
– the appropriate MCS user profile configuration document; and
– the appropriate MCS service configuration document; and
b) using the URI of the group management server obtained from the MCS UE initial configuration MO obtain the MCS group document; or
2. the:
a) offline configuration management server on the external device that configures the MCS UE with the:
– MCS UE initial configuration MO;
– appropriate MCS UE configuration MO(s);
– appropriate MCS user profile MO(s); and
– appropriate MCS service configuration MO(s); and
b) offline group management server on the external device that configures the MCS UE with the MCS group MO.
The mechanism to discover the online or offline configuration management server is dependent on the protocol used to manage and configure the MO and is out of scope of the present document.
4.2.2 Online configuration
4.2.2.1 General
The format of the MCS UE initial configuration MO downloaded to the MCS UE during online configuration is defined in 3GPP TS 24.483 [4].
The format of the MCS group document downloaded to the MCS UE during online configuration is defined in 3GPP TS 24.481 [5].
Figure 4.2.2.1-1 shows the MCPTT UE online configuration time sequence.
Figure 4.2.2.1-1 MCS UE online configuration time sequence
If the MCS UE initial configuration MO has changed from the version stored in the MCS UE, the updated MCS UE initial configuration MO is downloaded to the MCPTT UE.
If the MCS UE initial configuration MO contains a <default-user-profile> element and the identified default MCS user profile configuration MO(s) have changed from the version stored in the MCS UE, the updated default MCS user profile configuration MO(s) are downloaded to the MCS UE.
NOTE 1: The default MCS user profile configuration MO(s) define the default identity(s) for the enabled mission critical service(s) and the profile of services available to the user (e.g. emergency MCPTT services) prior to user authentication.
The MCS UE contacts the identity management server using the HTTPS URI stored in the MCS UE initial configuration MO and performs MCS User authentication as specified in 3GPP TS 24.482 [6].
The MCS UE, using the identities obtained during MCS user authentication, subscribes to the MCS UE configuration document, the MCS user profile configuration document and the MCS service configuration document for each enabled MCS using the procedure for subscribing to multiple documents simultaneously using the subscription proxy function specified in clause 6.3.13.2.2 (i.e., the CMS acts as a Subscription Proxy) and subscribes to the MCS group document using the procedure specified in 3GPP TS 24.481 [5]. If these documents have been updated since the current version stored in the MCS UE, then the MCS UE will receive a SIP NOTIFY request with an XCAP Diff document (see IETF RFC 5875 [11]), in which case the CMC updates its local document copies . Retrieval by the MCS UE using the notified HTTPS URI of the MCS group document is performed as specified in 3GPP TS 24.481 [5].
NOTE 2: The MCS UE can be notified of changes to a configuration document at any time while using the MCS.
4.2.2.2 MCPTT
The format of the MPCTT UE configuration document downloaded to the MCPTT UE during online configuration is defined in clause 8.2.
The format of the MPCTT user profile configuration document downloaded to the MCPTT UE during online configuration is defined in clause 8.3.
The format of the MPCTT service configuration document downloaded to the MCPTT UE during online configuration is defined in clause 8.4.
4.2.2.3 MCVideo configuration
The format of the MCVideo UE configuration document downloaded to the MCVideo UE during online configuration is defined in clause 9.2.
The format of the MCVideo user profile configuration document downloaded to the MCVideo UE during online configuration is defined in clause 9.3.
The format of the MCVideo service configuration document downloaded to the MCVideo UE during online configuration is defined in clause 9.4.
4.2.2.4 MCData configuration
The format of the MCData UE configuration document downloaded to the MCData UE during online configuration is defined in clause 10.2.
The format of the MCData user profile configuration document downloaded to the MCData UE during online configuration is defined in clause 10.3.
The format of the MCData service configuration document downloaded to the MCData UE during online configuration is defined in clause 10.4.
4.2.3 Offline configuration
4.2.3.1 General
When configuring an MCS UE offline the offline configuration management server will need to support the MCS administrator providing the identity(s) of the MCS user for whom the MCS UE is being configured so that the correct configuration data for that MCPTT user can be configured in the MOs.
The format of the MCS UE initial configuration MO downloaded to the MCPTT UE during offline configuration is defined in 3GPP TS 24.483 [4].
The format of the MCS group document MO to the MCPTT UE during offline configuration is defined in 3GPP TS 24.483 [4].
NOTE: If the MCPTT service administrator includes a "DefaultUserProfile" element in the MCS UE initial configuration MO as defined in 3GPP TS 24.483 [4], at least one instance of an MCS user profile configuration MO needs to first be created on the offline configuration management server, containing the "MCPTTUserID" element and "UserProfileIndex" element (as defined in 3GPP TS 24.483 [4]) that are included in the "DefaultUserProfile" element.
Editor’s Note: [C1-170137, MCImp-eMCPTT-CT] Addressing the identities element is FFS.
4.2.3.2 MCPTT
The format of the MPCTT UE configuration MO downloaded to the MCPTT UE during offline configuration is defined in 3GPP TS 24.483 [4].
The format of the MPCTT user profile configuration MO downloaded to the MCPTT UE during offline configuration is defined in 3GPP TS 24.483 [4].
The format of the MPCTT service configuration MO downloaded to the MCPTT UE during offline configuration is defined in 3GPP TS 24.483 [4].
4.2.3.3 MCVideo configuration
The format of the MCVideo UE configuration MO downloaded to the MCPTT UE during offline configuration is defined in 3GPP TS 24.483 [4].
The format of the MCVideo user profile configuration MO downloaded to the MCPTT UE during offline configuration is defined in 3GPP TS 24.483 [4].
The format of the MCVideo service configuration MO downloaded to the MCPTT UE during offline configuration is defined in 3GPP TS 24.483 [4].
4.2.3.4 MCData configuration
The format of the MCData UE configuration MO downloaded to the MCPTT UE during offline configuration is defined in 3GPP TS 24.483 [4].
The format of the MCData user profile configuration MO downloaded to the MCPTT UE during offline configuration is defined in 3GPP TS 24.483 [4].
The format of the MCData service configuration MO downloaded to the MCPTT UE during offline configuration is defined in 3GPP TS 24.483 [4].
4.3 MCS server
4.3.1 General
The MCS server obtains the appropriate MCS service configuration document that contains the mission critical organisation configured parameters that defined the behaviour of the MCS from the configuration management server.
The MCS server obtains the MCS service configuration document that contains the mission critical organisation configured parameters that defined the behaviour of the MCS from the configuration management server.
The MCS server subscribes to the MCS service configuration document for each mission critical organisation that is provisioned that is supported by the MCS server using the procedure specified in clause 6.3.13.2.3. How the MCS server is provisioned with the identities of the mission critical organisations is out of scope of the present document.
If the MCS service configuration document has been updated since the current version stored at the MCS server, then the MCS server will receive a SIP NOTIFY request containing an HTTPS URI of the MCS service configuration document. Retrieval by the MCS server, using the notified HTTPS URI, of the MCS service configuration document is performed as specified in clause 6.3.3.2.3.
NOTE: The MCS server can be notified of changes to the MCS service management configuration document at any time while operating the MCS.
4.3.2 MCPTT Server
The format of the MCPTT service configuration document downloaded to the MCPTT server is defined in clause 8.4.
4.3.3 MCVideo Server
The format of the MCData service configuration document downloaded to the MCData server is defined in clause 9.4.
4.3.4 MCData Server
The format of the MCData service configuration document downloaded to the MCData server is defined in clause 10.4.
4.4 Configuration management server
The following applies to the configuration management server used for online configuration.
The configuration management server needs to convert the MCS UE initial configuration document received from an MCS administrator into an appropriate format for configuration of the MCS UE initial configuration MO.
If the MCS UE initial configuration MO contains a <default-user-profile> element that identifies an MCS user profile configuration document, the configuration management server needs to convert the identified MCS user profile configuration document received from an MCS administrator into an appropriate format for configuration of the MCS user profile configuration MO.
Once an MCS User Profile configuration document has been created or updated by the MCS UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to store MCS user profile configuration document as the user profile in the MC service user database.
In order to download the MCS user profile configuration document to an MCS UE or to support an MCS UE updating the MCS user profile configuration document, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to obtain the MCS user profile from the MC service user database.
In order to be notified of changes to an MCS user profile configuration document(s) that have been subscribed to by an MCS UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to be notified of changes to the MCS user profile stored in the MC service user database.
In order to delete the MCS user profile when requested by an MCS UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to delete the MCS user profile from the MC service user database.
NOTE: The configuration management server and group management server functionality for offline configuration is out of scope of the present document.