Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.280  Word version:  19.1.0

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.17…   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.3 MC service user obtains the MC service user profile(s) from the network  10.1.4.3.1 MC service user receiving MC service in primary MC system  10.1.4.3.2 MC service user receiving MC service from a partner MC system  10.1.4.4 MC service user receives updated MC service user profile data from the network 
...

 

10.1.4.3  MC service user obtains the MC service user profile(s) from the network  p. 80

10.1.4.3.1  MC service user receiving MC service in primary MC system |R15|  p. 80
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.
Reproduction of 3GPP TS 23.280, Fig. 10.1.4.3.1-1: MC service user obtains the MC service user profile(s) from the network
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|  p. 81
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.
Reproduction of 3GPP TS 23.280, Fig. 10.1.4.3.2-1: Retrieval of user profile in partner MC system
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 network  p. 83

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.
Reproduction of 3GPP TS 23.280, Fig. 10.1.4.4-1: MC service user receives updated MC service user profile data from the network
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

Up   Top   ToC