Depicted in Figure 10.1.1.1-1 is a MC service configuration time sequence of the data related to specific MC service, representing the general lifecycle of MC service UE using an MC service.

The MC service UE is provided with initial UE configuration via a bootstrap procedure that provides the MC service UE's clients (e.g. MC service client, group management client, configuration management client, identity management client, key management client, functional alias management client) with critical information needed to connect to the MC system. This includes PDN connection information corresponding to the configured MC services on the MC service UE (see "EPS bearer considerations" in the TS 23.379) and on-network server identity information for all application plane servers with which the MC service UE needs to interact. See Annex A.6 for more information. The MC service UE is provided with UE configuration, MC service user profile configuration and group configuration via online configuration. While the MC service UE is using the MC service it may receive online configuration updates. If the MC service user profile configuration contains multiple MC service user profiles for an authenticated MC service user, then the MC service client and MC service server set the active MC service user profile to the configured pre-selected MC service user profile after MC service authorization (which can be updated by the MC service user using the procedure specified in subclause 10.1.4.6). The active MC service user profile can be changed by the MC service user to a different MC service user profile during MC service service (see MC service TSs). The MC service is configured with the service configuration (not shown in the Figure 10.1.1.1-1) which the MC service enforces during the entire phase of MC service UE using the MC service.

Figure 10.1.1.2-1 depicts a general MC service configuration time sequence of the data related to MC service, representing the general lifecycle of MC service UE which obtains MC service when migrated to a partner MC system. The MC service user can only receive MC service from one MC system at a time.

The MC service user and MC service UE first follow the MC service UE configuration and MC service user authorization steps described in subclause 10.1.1.1 to obtain one or more MC service user profiles from the primary MC system. Each user profile received from the primary MC system contains a list of partner MC systems to which migration is permitted using that user profile, together with the access information needed to communicate with the application plane servers of the partner MC system. See Annex A.3 for more information. The MC service user also obtains the necessary security parameters needed to authenticate and become service authorized on the partner MC system; the process for this is specified in TS 33.180. At this point, the MC UE is configured sufficiently for the partner system so that the MC service user is capable of utilizing "limited services" as described in TS 33.180. To initiate migration, the desired partner system from those listed in the chosen user profile is selected, and the access information provided in the user profile is used to initiate communication with the partner MC system. The MC service user performs user authentication to the partner MC system as specified in TS 33.180. The user profile or profiles for that MC service user which are to be used for service when migrated to the partner MC system are then downloaded to the configuration management client in the MC service UE by the partner MC system, and these downloaded profile or profiles are used by the MC service user during the ensuing period of MC service on the partner MC system. Group configuration for the MC service groups listed in the user profile are then obtained by the group management client in the MC service UE. After these configuration steps, the MC service user obtains service authorization on the partner MC system. Once service authorized, further configuration changes may be provided by the partner MC system during the period of operational MC service, in accordance with subclause 10.1.1.1. The partner MC system enforces the use of the user profiles and group configuration that have been provided by the configuration process described in this subclause.

Table 10.1.2.1-1 describes the information flow store group configuration request from the group management client to the group management server.

Table 10.1.2.2-1 describes the information flow store group configuration response from the group management server to the group management client.

Table 10.1.2.3-1 describes the information flow get group configuration request from the group management client to the group management server.

Table 10.1.2.4-1 describes the information flow get configuration response from the group management server to the group management client.

Table 10.1.2.5-1 describes the information flow subscribe group configuration request from the group management client to the group management server.

Table 10.1.2.5a-1 describes the information flow subscribe group policy request from the MC service server to the group management server.

Table 10.1.2.6-1 describes the information flow subscribe group configuration response from the group management server to the group management client.

Table 10.1.2.6a-1 describes the information flow subscribe group configuration response from the group management server to the MC service server.

Table 10.1.2.7-1 describes the information flow notify group configuration request from the group management server to the group management client.

Table 10.1.2.7a-1 describes the information flow notify group policy request from the group management server to the MC service server.

Table 10.1.2.8-1 describes the information flow notify group configuration response from the group management client to the group management server.

Table 10.1.2.8a-1 describes the information flow notify group configuration response from the MC service server to the group management server.

Table 10.1.2.9-1 describes the information flow get functional alias configuration request from the functional alias management client or the MC service server to the functional alias management server.

Table 10.1.2.10-1 describes the information flow get configuration response from the functional alias management server to the functional alias management client or the MC service server.

Table 10.1.2.11-1 describes the information flow subscribe functional alias configuration request from the functional alias management client or the MC service server to the functional alias management server.

Table 10.1.2.12-1 describes the information flow subscribe functional alias configuration response from the functional alias management server to the functional management client or the MC service server.

Table 10.1.2.13-1 describes the information flow notify functional alias configuration request from the functional alias management server to the functional alias management client or the MC service server.

Table 10.1.2.14-1 describes the information flow notify functional alias configuration response from the functional alias management client or the MC service server to the functional alias management server.

The MC service UE configuration data has to be known by the MC service UE before it can use the MC service.

The procedure for MC service UE obtaining the MC service UE related configuration data is illustrated in Figure 10.1.3.2-1. Pre-conditions:

• The MC service UE has the secure access to the configuration management server.

For a MC service, the MC service UE configuration data is listed in the corresponding MC service TS.

An MC service user is identified by an MC service ID. An MC service ID is associated with at least one MC service user profile and can be associated with multiple MC service user profiles (identified by an index and optionally a profile name). This is depicted in Figure 10.1.4.1-1.

For an MC service user there can be multiple MC service IDs with the constraint that only one MC service ID exists for a given MC service for that MC service user (e.g. MC service ID X may correspond to MCPTT service and MC service ID Y may correspond to MCVideo service). When the MC service provider requires to support a single MC service ID for all MC services, the value of the multiple MC service IDs is the same (e.g. value of MC service ID X is same as MC service ID Y). In the case where a single MC service ID is configured for a MC service user for authorized access to multiple MC services, the MC service UE and MC service server shall include the indication of the specific MC service during the communication. For the same MC service user there can be different MC service user profiles active on different MC service UEs or different MC service user profiles active on the same MC service UE at different times. The MC service user may have one or more specific MC service user profiles defined for use in migration cases, whereby there may be more than one MC service user profiles defined for migration for that MC service user e.g. so that different MC service user profiles can be applied in different partner MC systems. The appropriate MC service user profile for migration for the relevant partner MC system will be provided to the partner MC system by the procedure. For both the cases of MC service on the primary MC system of the MC service user, and MC service when migrating to a partner MC system, only one MC service user profile per MC service client is active at a time. All MC service user profiles associated with an MC service user are stored in the MC service user database. Different parts of the MC service user profile are provisioned by the Mission Critical Organization, by the MC service provider and by the MC service user, respectively. MC service user profile information is downloaded to the MC service UE. The MC service user profile configuration may include more than one information exchange e.g. the configuration management server may provide the MC service UE with a list of some or all enabled MC service user profiles to allow the MC service user to select one (where the list may contain a subset of the MC service user profile information sufficient for the MC service user to distinguish which MC service user profile to select). When an MC service user is receiving MC service in its primary MC system, the MC service user profile provisioning in the UE is initiated by the configuration management client (e.g. upon MC service user authentication or on reconnect to the MC service), or initiated by the configuration management server (e.g. due to role change or organization change). For a migrating MC service user, the MC service user profile provisioning in the UE is initiated when the MC service user attempts to migrate to a partner MC system, and requests the MC service user profile from a nominated configuration management server in the partner MC system, prior to requesting service authorization from a partner MC service server. The partner MC system may require that the MC service user profiles for migrating MC service users have parameters imposed by that partner MC system according to its operating and security policies. For example, there may be limitations in the locations at which migrating MC users can receive service, specific priority levels for migrating MC service users or certain groups to which the migrating MC service users require access. The partner MC system applies any necessary modifications to the MC service user profile received from the primary MC system of the MC service user in accordance with its local requirements. This local profile will be stored, and will be provided to the configuration management server in the partner MC system in order to distribute it to the configuration management client of the migrating MC service user. This modified profile may be sent to the primary MC system of the migrating MC service user so that the primary MC system can validate the modified profile before it is provided to the migrating MC service UE. The modified MC service user profile will subsequently be provided to the MC service server in the partner MC system when the migrating MC user attempts service authorization.

The procedure for MC service user obtaining updated MC service user profile data (see TS 23.379) that is initiated by the network is illustrated in Figure 10.1.4.4-1. Pre-conditions:

• The MC service user has performed user authentication in identity management server.
• The MC service UE has secure access to the configuration management server.
• The MC service UE has already obtained one or more MC service user profiles.
• The configuration management server has access to the MC service user profile(s) associated with the MC service ID of the MC service user.

The procedure for MC service user updating the MC service user profile data (see TS 23.379) is illustrated in Figure 10.1.4.5-1. Pre-conditions:

• The MC service user has performed user authentication in identity management server.
• The MC service UE has secure access to the configuration management server.
• The MC service UE has already obtained one or more MC service user profiles.

The procedure for updating the pre-selected MC service user profile in the configuration for an MC service UE by the MC service user is illustrated in Figure 10.1.4.6-1. Pre-conditions:

• The MC service user has performed user authentication in identity management server.
• The MC service UE has secure access to the configuration management server.
• The MC service UE has already obtained one or more MC service user profiles.
• The configuration management client is triggered (e.g. by user interaction, by some automated means) to change the pre-selected MC service user profile.

For each update pre-selected MC service user profile request to the MC service user profile, the configuration management server determines whether the requested update is allowed prior to storing the configuration parameters and updating the MC service user database (via the CSC-13 reference point as specified in TS 29.283). After each update to the MC service user profile in the MC service user database, the MC service server receives the changes from the MC service user profile database via the corresponding MC service reference point defined between MC service server and the MC service user database, and all of the MC service UEs associated with the MC service user receive the updated MC service user profile as specified in subclause 10.1.4.4. A change to the pre-selected MC service user profile while the MC service user is receiving MC service does not have any effect on the active MC service user profile, however, the change will be applied at the next MC service authorization.

The procedure for updating the selected MC service user profile within a single MC service for an MC service UE by the MC service user whilst the MC service user is receiving that MC service service is illustrated in Figure 10.1.4.7-1. This procedure is used by the following MC services:

• MCPTT (as specified in TS 23.379);
• MCVideo (as specified in TS 23.281); and
• MCData (as specified in TS 23.282).

Pre-conditions:

• For the MC service (see list above) for which the selected MC service user profile is to be updated:
• The MC service user has performed user authentication in the identity management server.
• The MC service UE has secure access to the MC service server.
• The MC service UE has already obtained multiple MC service user profiles.
• The MC service UE has performed MC service authorization.
• The MC service client is triggered (e.g. by user interaction, by some automated means) to select a particular MC service user profile as active.

After each of the MC service server and the MC service UE have successfully negotiated a selected MC service user profile, then both the MC service server and the MC service UE, based upon the selected MC service user profile, clear any currently active service state from any previously selected or pre-selected MC service user profile data (including deaffiliating from relevant groups, disconnecting any MC service calls) and process the successfully negotiated selected MC service user profile data e.g. perform any needed affiliations.