Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.280  Word version:  19.0.1

Top   Top   Up   Prev   Next
1…   5…   5.2.8…   6   7…   7.3.2   7.4…   7.4.3…   7.5…   8…   9…   9.2.2…   9.2.2.2…   9.3…   10…   10.1.2…   10.1.3…   10.1.4.3…   10.1.4.5…   10.1.5…   10.1.6…   10.2…   10.2.3…   10.2.4.2…   10.2.4.3…   10.2.5…   10.2.7…   10.3…   10.6…   10.7…   10.7.3…   10.7.3.4…   10.7.3.7…   10.7.3.7.3   10.7.3.8…   10.7.3.10…   10.8…   10.8.4…   10.8.5…   10.9…   10.9.3…   10.9.3.5…   10.9.3.8…   10.9.3.9…   10.9.3.9.3…   10.9.3.9.4…   10.9.3.10…   10.9.3.10.4…   10.9.3.10.6…   10.10…   10.10.1.2.3…   10.10.2…   10.10.3…   10.10.3.3…   10.10.3.4…   10.11…   10.11.5…   10.12…   10.13…   10.13.3…   10.13.7…   10.13.10…   10.14…   10.15…   10.15.3…   10.15.3.3…   10.15.3.4…   10.16…   10.16.3…   11…   11.3…   11.5…   11.5.2…   11.5.3…   11.5.3.3.2A…   11.5.4…   A…   B…   C…

 

10.1.4.5  MC service user updates MC service user profile data to the networkp. 81

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.
Reproduction of 3GPP TS 23.280, Fig. 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 profilep. 82

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.
Reproduction of 3GPP TS 23.280, Fig. 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 servicep. 83

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.
Reproduction of 3GPP TS 23.280, Fig. 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 subclause 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