Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.280  Word version:  17.8.0

Top   Top   Up   Prev   Next
1…   5…   7…   7.4…   7.5…   8…   9…   10…   10.1.2…   10.1.3…   10.1.5…   10.2…   10.2.3…   10.2.5…   10.3…   10.7…   10.7.3…   10.7.3.7…   10.7.3.10…   10.8…   10.8.4…   10.9…   10.9.3…   10.9.3.8…   10.10…   10.11…   10.12…   10.13…   10.13.3…   10.14…   10.15…   10.15.3…   A…   B…

 

10.1.3  MC service UE configuration dataWord‑p. 72

10.1.3.1  GeneralWord‑p. 72

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

10.1.3.2  ProceduresWord‑p. 72

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.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.1.3.2-1: MC service UE obtains the configuration data
Up
  1. The configuration management client sends a get MC service UE configuration request to the configuration management server for obtaining MC service UE configuration data.
  2. The configuration management server sends get MC service UE configuration response to the configuration management client. This message carries the MC service UE configuration data.

10.1.3.3  Structure of UE configuration dataWord‑p. 72

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

10.1.4  MC service user profileWord‑p. 72

10.1.4.1  GeneralWord‑p. 72

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.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.1.4.1-1: The relationship of MC service user, MC service IDs, MC service user profile and MC services
Up
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.
Up

10.1.4.2  Information flows for MC service user profileWord‑p. 74

10.1.4.2.1  Get MC service user profile requestWord‑p. 74
Table 10.1.4.2.1-1 describes the information flow get MC service user profile request from the configuration management client to the configuration management server.
Information element Status Description
MC service IDMThe MC service ID of the MC service user.
Up
10.1.4.2.2  Get MC service user profile responseWord‑p. 74
Table 10.1.4.2.2-1 describes the information flow get MC service user profile response from the configuration management server to the configuration management client.
Information element Status Description
MC service user profile dataMOne or more MC service user profiles (identified as specified in subclause 10.1.4.1) associated with the MC service ID provided in the associated get MC service user profile request.
Up
10.1.4.2.3  Notification for MC service user profile data updateWord‑p. 74
Table 10.1.4.2.3-1 describes the information flow notification for MC service user profile data update from the configuration management server to the configuration management client.
Information element Status Description
Pointer to modified MC service user profile dataMPointer to the modified MC service user profile data.
Up
10.1.4.2.4  Get updated MC service user profile data requestWord‑p. 74
Table 10.1.4.2.4-1 describes the information flow get updated MC service user profile data request from the configuration management client to the configuration management server.
Information element Status Description
MC service IDMThe MC service ID of the originating MC service user.
Pointer to modified MC service user profile dataMPointer to the modified MC service user profile data.
Up
10.1.4.2.5  Get updated MC service user profile data responseWord‑p. 75
Table 10.1.4.2.5-1 describes the information flow get updated MC service user profile data response from the configuration management server to the configuration management client.
Information element Status Description
Updated MC service user profile dataMMC service user profile data that has been modified.
Up
10.1.4.2.6  Update MC service user profile data requestWord‑p. 75
Table 10.1.4.2.6-1 describes the information flow update MC service user profile data request from the configuration management client to the configuration management server.
Information element Status Description
MC service IDMThe MC service ID of the originating MC service user.
Updated MC service user profile dataMThe contents of the user profile data to be updated.
Up
10.1.4.2.7  Update MC service user profile data responseWord‑p. 75
Table 10.1.4.2.7-1 describes the information flow update MC service user profile data response from the configuration management server to the configuration management client.
Information element Status Description
ResultMIndicates the success or failure
Up
10.1.4.2.8  Update pre-selected MC service user profile requestWord‑p. 75
Table 10.1.4.2.8-1 describes the information flow update pre-selected MC service user profile request from the configuration management client to the configuration management server.
Information element Status Description
MC service IDMThe MC service ID of the originator.
MC service user profile indexMThe MC service user profile index of the MC service user profile that is to be pre-selected by the MC service server at MC service user authentication.
Up
10.1.4.2.9  Update pre-selected MC service user profile responseWord‑p. 76
Table 10.1.4.2.9-1 describes the information flow update pre-selected MC service user profile response from the configuration management server to the configuration management client. This information flow is sent individually addressed on unicast or multicast.
Information element Status Description
ResultMIndicates the success or failure.
Up
10.1.4.2.10  Update selected MC service user profile requestWord‑p. 76
Table 10.1.4.2.10-1 describes the information flow update selected MC service user profile request from the MC service client to the MC service server and is used by the following MC services:
Information element Status Description
MC service IDMThe MC service ID of the originator.
MC service user profile indexMThe MC service user profile index of the selected MC service user profile.
Up
10.1.4.2.11  Update selected MC service user profile responseWord‑p. 76
Table 10.1.4.2.11-1 describes the information flow update selected MC service user profile response from the MC service server to the MC service client and is used by the following MC services:
Information element Status Description
ResultMIndicates the success or failure.
Up

10.1.4.3  MC service user obtains the MC service user profile(s) from the networkWord‑p. 76

10.1.4.3.1  MC service user receiving MC service in primary MC system |R15|Word‑p. 76
The procedure for the MC service user obtaining MC service user profiles in the primary MC system of that MC service user is illustrated in Figure 10.1.4.3.1-1.
Pre-conditions:
  • The MC service user has performed user authentication in the identity management server.
  • The MC service UE has secure access to the configuration management server.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.1.4.3.1-1: MC service user obtains the MC service user profile(s) from the network
Up
Step 1.
The configuration management client sends a get MC service user profile request message to the configuration management server, which includes the MC service ID.
Step 2.
The configuration management server obtains the MC service user profile information.
Step 3.
The configuration management server sends get MC service user profile response message to the configuration management client. When a download is necessary, this message includes all MC service user profiles that are associated with the MC service ID.
10.1.4.3.2  MC service user receiving MC service from a partner MC system |R15|Word‑p. 77
Figure 10.1.4.3.2-1 below illustrates mechanism for the configuration management client to retrieve the MC service user profile for the migrating MC service user from the partner MC system.
Preconditions
  • The MC service user is permitted to migrate to the partner MC system, and the relevant authorizations are configured in both the primary and partner MC systems of that MC service user
  • The MC service user has performed MC service user authentication in the partner MC system, and has received the necessary credentials to retrieve configuration information and to request service authorization.
  • The MC service UE has been provided with addressing information to allow the configuration management client in the MC service UE to access the configuration management server in the partner MC system.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.1.4.3.2-1:	Retrieval of user profile in partner MC system
Up
Step 1.
The configuration management client in the MC service UE of the migrating MC service user requests the MC service user profile for migration from the configuration management server in the partner MC system.
Step 2.
The configuration management server in the partner MC system requests the MC service user profile from the configuration management server in the primary MC system of the MC service user.
Step 3.
The configuration management server in the primary MC system of the MC service user retrieves the MC service user profile from the MC service user database in that primary MC system. The identification of the partner MC system to which the MC service user is attempting to migrate is used to determine which MC service user profile is retrieved for that MC service user for migration to that partner MC system.
Step 4.
The configuration management server in the primary MC system provides the MC service user profile to the configuration management server in the partner MC system of the MC service user, optionally requesting validation of the modified MC service user profile.
Step 5.
The partner MC system of the MC service user modifies the MC service user profile according to local configuration information and stores the modified MC service user profile in the MC service user database in the partner MC system.
Step 6.
If the primary MC system requested validation of the MC service user profile in step 4, the configuration management server in the partner MC system of the migrating MC service user may send the modified MC service user profile to the configuration management server of the primary MC system of the MC service user to allow the primary MC system of the MC service user to validate the modified MC service user profile.
Step 7.
The primary MC system of the migrated MC service user validates the modified MC service profile of the migrated MC service user.
Step 8.
The primary MC system of the migrated MC service user responds to the partner MC system with the results of the validation process.
Step 9.
The configuration management server in the partner MC system provides the MC service user profile to the configuration management client of the migrating MC service user,
Up

10.1.4.4  MC service user receives updated MC service user profile data from the networkWord‑p. 79

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.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.1.4.4-1: MC service user receives updated MC service user profile data from the network
Up
Step 1.
The configuration management server obtains updated MC service user profile data.
Step 2.
The configuration management server sends a notification for MC service user profile data update to the configuration management client.
Step 3.
The configuration management client sends get updated MC service user profile data request to the configuration management server, which includes the MC service ID.
Step 4.
The configuration management server sends get updated MC service user profile data response to the configuration management client which includes the updated MC service user profile data requested in step 3.
Up

10.1.4.5  MC service user updates MC service user profile data to the networkWord‑p. 79

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.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.1.4.5-1: MC service user updates MC service user profile data to the network
Up
Step 1.
The configuration management client is triggered (e.g. by user interaction operation) to update the MC service user profile data on the configuration management server.
Step 2.
The configuration management client sends update MC service user profile data request to the configuration management server, which includes the MC service user profile data to be updated.
Step 3.
The configuration management server stores the received MC service user profile data.
Step 4.
The configuration management server sends update MC service user profile data response to the configuration management client to confirm the MC service user profile data update is complete.
Up

10.1.4.6  Updating the pre-selected MC service user profileWord‑p. 80

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.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.1.4.6-1: MC service user updates the pre-selected MC service user profile
Up
Step 1.
The configuration management client sends update pre-selected MC service user profile request to the configuration management server, which includes the MC service user's MC service ID and an MC service user profile index that indicates which MC service user profile is to be pre-selected by the MC service server at next MC service authorization.
Step 2.
The configuration management server checks the authorization of the update pre-selected MC service user profile request.
Step 3.
The configuration management server stores the received pre-selected MC service user profile selection.
Step 4.
The configuration management server sends update pre-selected MC service user profile response to the configuration management client to confirm the pre-selected MC service user profile has been set.
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.
Up

10.1.4.7  Updating the selected MC service user profile for an MC serviceWord‑p. 81

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:
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.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.1.4.7-1: MC service user updates the selected MC service user profile
Up
Step 1.
MC service client sends update selected MC service user profile request to the MC service server, which includes the MC service user's MC service ID and an MC service user profile index that indicates which MC service user profile is selected to be currently active for MC service client.
Step 2.
If the MPCTT server does not have stored the MC service user profile data for the MC service user, then the MC service server obtains the MC service user profile data.
Step 3.
The MC service server stores the selected MC service user profile index for the MC service client.
Step 4.
If the MC service server does not have stored the group configuration data for the selected MC service user profile then the MC service server obtains group configuration data according to the selected MC service user profile (see subclause 10.1.5.2) and subscribes to updates of the group configuration data (see subclause 10.1.5.3).
Step 5.
The MC service server sends update selected MC service user profile response to the MC service client to confirm the active MC service user profile has been set.
Step 6.
If the MC service client does not have stored the group configuration data for the selected MC service user profile then the MC service client obtains group configuration data according to the successfully selected MC service user profile (see subclauase 10.1.5.2) and subscribes to updates of the group configuration data (see subclause 10.1.5.3).
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.
Up

Up   Top   ToC