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.6  MC service UE migration |R15|p. 92

10.1.6.1  MC service UE obtains migration connectivity information of partner MC systemp. 92

Connectivity information for the partner MC system, including MC system identification and access information, is contained in the on-network user profiles for MCPTT in TS 23.379, for MCVideo in TS 23.281 and for MCData in TS 23.282.

10.1.6.2  Signalling plane registration for the MC service UE between the primary and the partner MC systemsp. 93

The MC service UE performs the following procedure when connecting to a partner MC system for one or more MC services.
Pre-conditions:
  1. The MC service UE has successfully obtained migration connectivity information for the partner MC system (see subclause 10.1.6.1).
  2. The MC service UE has successfully set-up bearers to the partner MC system's PDN(s).
  3. The configuration management client has secure access to the configuration management server in the primary MC system.
  4. The migration management server in the partner MC system has been configured with the mapping between the SIP identities of the partner MC system and the SIP identities of the primary MC system.
Reproduction of 3GPP TS 23.280, Fig. 10.1.6.2-1: MC service UE signalling plane registration in a partner MC system
Up
Step 1.
The signalling user agent sends a SIP registration request to the SIP core of the partner MC system, which includes the partner MC system SIP identities.
Step 2.
The SIP core in the partner MC system sends get SIP authentication information request to the migration management server also in the partner MC system, which includes the partner MC system SIP identities received in step 2.
Step 3.
The migration management server in the partner MC system, due to the binding created in the migration management server (see pre-condition 4), recognises the partner MC system SIP identities and determines the identifier of the MC service user's migration management server in the primary MC system and the primary MC system SIP identities.
Step 4.
The migration management server in the partner MC system sends get SIP authentication information request to the migration management server in the primary MC system, which includes the primary MC system SIP identities as determined in step 3.
Step 5.
The migration management server in the primary MC system sends get SIP authentication information request to the SIP database, via the SIP core / IMS, in the primary MC system, which includes the primary MC system SIP identities received in step 4.
Step 6.
The SIP database in the primary MC system recognises the primary MC system SIP identities and sends get SIP authentication information response to the migration management server, via the SIP core / IMS, in the primary MC system, which includes the primary MC system SIP identities and authentication information (e.g. authentication vectors).
Step 7.
The migration management server in the primary MC system sends get SIP authentication information request to the migration management server in the partner MC system, which includes the primary MC system SIP identities and authentication information received in step 6.
Step 8.
The migration management server in the partner MC system, due to the binding created in the migration management server (see pre-condition 4), recognises the primary MC system SIP identities, and determines the partner MC system SIP identities.
Step 9.
The migration management server in the partner MC system sends get SIP authentication information response to the SIP core also in the partner MC system, which includes the partner MC system SIP identities and the authentication information as received in step 7.
Step 10.
The SIP core and MC service UE perform the SIP authentication procedure.
Step 11.
The SIP core in the partner MC system sends SIP registration response to the signalling user agent in the MC service UE, which includes an indication that the authentication is successful.
Up

10.1.7  Functional alias configuration management |R15|p. 94

10.1.7.1  Retrieve functional alias configurations from the functional alias management serverp. 94

The procedure for retrieve functional alias configurations from the functional alias management server is described in Figure 10.1.7.1-1. This procedure can be used following service authorisation when the configuration management client has received the list of functional aliases and the functional alias management client needs to obtain the functional alias configurations, or following a notification from the functional alias management server that new functional alias configuration information or functional alias configuration update is available. This procedure can be also used by the MC service server under authorization to obtain the functional alias configurations (e.g. upon functional alias activation or call processing).
Pre-conditions:
  • The functional alias management server has received configuration data for functional aliases, and has stored this configuration data;
  • The MC service UE has registered for service and the functional alias management client needs to download functional alias configuration data applicable to the current user.
Reproduction of 3GPP TS 23.280, Fig. 10.1.7.1-1: Retrieve functional alias configurations from the functional alias management server
Up
Step 1.
The functional alias management client or the MC service server requests the functional alias configuration data.
Step 2.
The functional alias management server provides the functional alias configuration data to the client or MC service server.
Step 3.
The functional alias management client or MC service server stores the functional alias configuration information.

10.1.7.2  Subscription and notification for functional alias configuration datap. 95

The procedure for subscription for functional alias configuration data as described in Figure 10.1.7.2-1 is used by the functional alias management client to indicate to the functional alias management server that it wishes to receive updates of functional alias configuration data for functional aliases for which it is authorized. This procedure can be also used by the MC service server under authorization to obtain the functional alias configurations and the updates (e.g. upon functional alias activation or call processing).
Pre-conditions:
  • The functional alias management server has some functional alias configurations stored.
Reproduction of 3GPP TS 23.280, Fig. 10.1.7.2-1: Subscription for functional alias configurations
Up
Step 1.
The functional alias management client or MC service server subscribes to the functional alias configuration information stored at the functional alias management server using the subscribe functional alias configuration request.
Step 2.
The functional alias management server provides a subscribe functional alias configuration response to the functional alias management client or MC service server indicating success or failure of the request.
The procedure for notification of functional alias configuration data as described in Figure 10.1.7.2-1 is used by the functional alias management server to inform the functional alias management client or MC service server that new functional alias configuration data is available.
Pre-conditions:
  • The functional alias management client has subscribed to the functional alias configuration information
  • The functional alias management server has received and stored new functional alias configuration information.
Reproduction of 3GPP TS 23.280, Fig. 10.1.7.2-2: Notification of functional alias configurations
Up
Step 1.
The functional alias management server provides the notification to the functional alias management client or MC service server, who previously subscribed for the functional alias configuration information.
Step 2.
The functional alias management client or MC service server provides a notify functional alias configuration response to the functional alias management server.
If the functional alias management server has notified the functional alias management client about new functional alias configuration information through this procedure, the functional alias management client may then follow the procedure described in subclause 10.1.7.1 in order to retrieve that functional alias configuration information.
Up

10.1.7.3  Dynamic data associated with a functional alias |R17|p. 96

10.1.7.3.1  Dynamic data associated with a functional alias in MC service serverp. 96
There may be dynamic data associated with a functional alias. The following dynamic data is known to the MC service server and provided when requested:
Parameter description
Activation status of each functional alias and the corresponding MC service ID of the user who activated that functional alias (subscription and notification procedures for functional alias are defined in clause 10.13.10)
Up

Up   Top   ToC