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.5  MC service group configuration managementWord‑p. 83

10.1.5.1  Store group configurations at the group management serverWord‑p. 83

The procedure for store group configurations at the group management server is described in Figure 10.1.5.1-1.
Pre-conditions:
  • The group management server may have some pre-configuration data which can be used for online group configuration validation;
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.1.5.1-1: Store group configurations at group management server
Up
Step 1.
The group configurations are received by the group management client of an authorized user.
Step 2.
The received group configurations are sent to the group management server for storage using a store group configuration request.
Step 3.
The group management server may validate the group configurations before storage.
Step 4.
The group management server stores the group configurations.
Step 5.
The group management server provides a store group configuration response indicating success or failure. If any validation or storage fails, the group management server provides a failure indication in the store group configuration response.
Up

10.1.5.2  Retrieve group configurations at the group management clientWord‑p. 83

The procedure for retrieve group configurations at the group management client is described in Figure 10.1.5.2-1. This procedure can be used following service authorisation when the configuration management client has received the list of groups and the group management client needs to obtain the group configurations, or following a notification from the group management server that new group configuration information is available.
Pre-conditions:
  • The group management server has received configuration data for groups, and has stored this configuration data;
  • The MC service UE has registered for service and the group management client needs to download group configuration data applicable to the current user.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.1.5.2-1: Retrieve group configurations at group management client
Up
Step 1.
The group management client requests the group configuration data.
Step 2.
The group management server provides the group configuration data to the client.
Step 3.
The group management client stores the group configuration information.

10.1.5.3  Subscription and notification for group configuration data at group management clientWord‑p. 84

The procedure for subscription for group configuration data as described in Figure 10.1.5.3-1 is used by the group management client to indicate to the group management server that it wishes to receive updates of group configuration data for groups for which it is authorized.
Pre-conditions:
  • The group management server has some group configurations stored.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.1.5.3-1: Subscription for group configurations at group management client
Up
Step 1.
The group management client subscribes to the group configuration information stored at the group management server using the subscribe group configuration request.
Step 2.
The group management server provides a subscribe group configuration response to the group management client indicating success or failure of the request.
The procedure for notification of group configuration data as described in Figure 10.1.5.3-2 is used by the group management server to inform the group management client that new group configuration data is available. It can also be used by the group management server to provide new group related key material to the group management client.
Pre-conditions:
  • The group management client has subscribed to the group configuration information
  • The group management server has received and stored new group configuration information, or the group management server has generated and stored new key material, or both of these have occurred.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.1.5.3-2: Notification of group configurations to group management client
Up
Step 1.
The group management server provides the notification to the group management client, who previously subscribed for the group configuration information. Optionally, the notify group configuration request may contain group related key material for the group management client.
Step 2.
The group management client provides a notify group configuration response to the group management server.
Step 3.
If the group management server had provided group related key material to the group management client, the group management client stores the key material.
If the group management server has notified the group management client about new group configuration information through this procedure, the group management client may then follow the procedure described in subclause 10.1.5.2 in order to retrieve that group configuration information.
Up

10.1.5.3a  Subscription and notification for group policy at MC service server |R17|Word‑p. 85

The procedure for subscription for group configuration data as described in Figure 10.1.5.3a-1 is used by the MC service server to indicate to the group management server that it wishes to receive updates of group configuration data for groups for which it is authorized.
Pre-conditions:
  • The group management server has some group configurations stored.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.1.5.3a-1: Subscription for group policy at MC service server
Up
Step 1.
The MC service server subscribes to the group policy from the group configuration stored at the group management server using the subscribe group policy request.
Step 2.
The group management server provides a subscribe group policy response to the MC service server indicating success or failure of the request.
The procedure for notification of group policy as described in Figure 10.1.5.3a-2 is used by the group management server to inform the MC service server that new group policy is available.
Pre-conditions:
  • The MC service server has subscribed to the group policy information from group management server.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.1.5.3a-2: Notification of group policy to MC service server
Up
Step 1.
The group management server provides the notification to the MC service server, who previously subscribed for the group policy from the group configuration.
Step 2.
The MC service server provides a notify group policy response to the group management server.

10.1.5.4  Structure of group configuration dataWord‑p. 86

The group configuration data contains group configuration data common to all MC services and group configuration data specific to each MC service. All group configuration data is specified in Annex A.4 of the present document.

10.1.5.5  Dynamic data associated with a groupWord‑p. 86

10.1.5.5.1  Dynamic data associated with a group in MC service server |R16|Word‑p. 86
There may be dynamic data associated with a group. The following dynamic data is known to the MC service server and provided when requested:
Parameter description
Status i.e. indication of potential emergency or in-peril status of the group, together with the identification of the user who has performed the last modification of this status.
Affiliation status of each MC service ID of the group corresponding to the MC service and the Contact URI(s) from which the user affiliated.
Contact URIs used for designation of the group e.g. aliases of group broadcast, group regroup group URIs.
Media description for group media, including transport and multiplexing information.
Group call ongoing.
Regroup status of group where regrouping using a preconfigured group is used, e.g. whether group is regrouped, MC service group identity of regroup group.
Functional alias binding information for each user within the group.
Up
10.1.5.5.2  Dynamic data associated with a group in group management server |R16|Word‑p. 86
The group management server may require (e.g., for regrouping) subscribe to a subset of dynamic data including affiliation status, regroup status and emergency status in the MC service server listed in Table 10.1.5.5.1-1.
The affiliation status in the form of a list of MC service IDs of affiliated group members corresponding to the MC service for that group is available in group management server. The group management server can subscribe to this information from the MC service server in Table 10.1.5.5.1-1. Table 10.1.5.5.2-1 describes the affiliation status contained in the group management server.
Parameter description
MC service group ID
List of affiliated group members
> MCPTT
>> MCPTT ID
> MCVideo
>> MCVideo ID
> MCData
>> MCData ID
The regroup status of a group in the form of a list of MC service group IDs of the group being regrouped is available in group management server. The group management server can subscribe to this information from the MC service server in Table 10.1.5.5.1-1. Table 10.1.5.5.2-2 describes the regroup status contained in the group management server.
Parameter description
List of MC service groups being regrouped into a new group
> MC service group ID (Constituent MC service group)
> Corresponding regrouped group information
>> MC service group ID
The emergency status of a group in the form of a list of MC service group IDs of the group in emergency state is available in group management server. The group management server can subscribe to this information from the MC service server in Table 10.1.5.5.1-1. Table 10.1.5.5.2-3 describes the emergency status contained in the group management server.
Parameter description
List of MC service groups in emergency state
> MC service group ID
Up

10.1.5.6  Subscription and notification for dynamic data associated with a group |R15|Word‑p. 87

10.1.5.6.0  General |R17|Word‑p. 87
An authorized user can request the current dynamic data for an MC service group on request. The dynamic data is described in subclause 10.1.5.5.1.
The group management server can subscribe for affiliation status, regroup status and emergency status associated with a group at the MC service server. The affiliation status, regroup status and emergency status in the group management server is described in subclause 10.1.5.5.2.
Up
10.1.5.6.1  Information flows for subscription and notification for dynamic data associated with a groupWord‑p. 88
10.1.5.6.1.1  Subscribe group dynamic data requestWord‑p. 88
Table 10.1.5.6.1.1-1 describes the information flow subscribe group dynamic data request from the MC service client to the MC service server and from the group management server to the MC service server.
Information element Status Description
MC service group IDMThe MC service group ID for which dynamic data is requested.
List of group dynamic data type (See NOTE)OThe type of group dynamic data requested, e.g., affiliated status, regroup status, emergency status
NOTE:
If the Group dynamic data type IE is not present, all types of group dynamic data is requested. This IE shall be present from when the request is sent from the group management sever.
Up
10.1.5.6.1.2  Subscribe group dynamic data responseWord‑p. 88
Table 10.1.5.6.1.2-1 describes the information flow subscribe group dynamic data response from the MC service server to the MC service client and from the MC service server to the group management server. This information flow from the MC service server to the MC service client is sent individually addressed on unicast or multicast.
Information element Status Description
MC service group IDMThe MC service group ID for which dynamic data is requested.
StatusMSuccess or failure of the request
Up
10.1.5.6.1.3  Notify group dynamic data requestWord‑p. 88
Table 10.1.5.6.1.3-1 describes the information flow notify group dynamic data response from the MC service server to the MC service client and from the MC service server to the group management server. This information flow from the MC service server to the MC service client may be sent individually addressed or group addressed on unicast or multicast (see subclause 10.7.3.4.1).
Information element Status Description
MC service group IDMThe MC service group ID for which dynamic data is requested.
Group dynamic dataMDynamic data associated with the group as per the requested group dynamic data type(s)
Up
10.1.5.6.1.4  Notify group dynamic data responseWord‑p. 88
Table 10.1.5.6.1.4-1 describes the information flow notify group dynamic data response from the MC service client to the MC service server and from the group management server to the MC service server.
Information element Status Description
MC service group IDMThe MC service group ID for which dynamic data was received
Up
10.1.5.6.2  Procedure for subscription and notification for dynamic data associated with a group by the MC service clientWord‑p. 89
The procedure for subscription for dynamic data associated with an MC service group is described in Figure 10.1.5.6.2-1 and is used by the MC service client of the authorized user to obtain the dynamic data from the MC service server.
Pre-conditions:
  • The MC service server holds dynamic data associated with the MC service group.
  • The MC service client is authorized to request the dynamic data associated with the MC service group.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.1.5.6.2-1: Subscription for group dynamic data
Up
Step 1.
The MC service client subscribes to the group dynamic data stored in the MC service server using the subscribe group dynamic data request.
Step 2.
The MC service server checks that the MC service client is authorized to receive dynamic data associated with the MC service group.
Step 3.
The MC service server provides a subscribe group dynamic data response to the MC service client indicating success or failure of the request.
The procedure for notification of group dynamic data as shown in Figure 10.1.5.6.2-2 is used by the MC service server to inform the MC service client about new group dynamic data.
Pre-conditions:
  • The MC service client has subscribed to the group dynamic data
  • The MC service server has new group dynamic data available.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.1.5.6.2-2: Notification of group dynamic data
Up
Step 1.
The MC service server provides the notification to the MC service client, who previously subscribed for the group dynamic data.
Step 2.
The MC service client provides a notify group dynamic data response to the MC service server.
10.1.5.6.3  Procedure for subscription and notification for dynamic data associated with a group by the group management server |R16|Word‑p. 89
The procedure for subscription for affiliation status regroup status and emergency status associated with an MC service group by the group management server is described in Figure 10.1.5.6.3-1 and is used by the group management server to obtain the affiliation status (implicit and explicit), regroup status and emergency status from the MC service server.
Pre-conditions:
  • The MC service server is the MC service server within the MC system where the group is defined.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.1.5.6.3-1: Subscription for dynamic data associated with a group
Up
Step 1.
The group management server subscribes to the dynamic data associated with a group stored in the MC service server using the subscribe group dynamic data request.
Step 2.
The MC service server provides a subscribe group dynamic data response to the group management server indicating success or failure of the request by specifying the list of group dynamic data type. The group dynamic data type indicates the group affiliation status, regroup status or emergency status to be subscribed.
The procedure for notification of group affiliation status, regroup status or emergency status as shown in Figure 10.1.5.6.3-2 is used by the MC service server to inform the group management server about the updates to the group affiliation status, regroup status or emergency status.
Pre-conditions:
  • The group management server has subscribed to the affiliation status, regroup status or emergency status in the MC service server.
  • The affiliation status, regroup status or emergency status associated with a group subscribed to by the group management server has been updated at the MC service server.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.1.5.6.3-2: Notification of dynamic data associated with a group
Up
Step 1.
The MC service server provides either or all of the affiliation status, regroup status and emergency status via a notification to the group management server based on the list of group dynamic data type which has subscribed.
Step 2.
The group management server provides a notify group dynamic data response to the MC service server.

10.1.6  MC service UE migration |R15|Word‑p. 90

10.1.6.1  MC service UE obtains migration connectivity information of partner MC systemWord‑p. 90

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 systemsWord‑p. 91

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.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 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|Word‑p. 92

10.1.7.1  Retrieve functional alias configurations from the functional alias management serverWord‑p. 92

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.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 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 dataWord‑p. 93

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.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 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.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 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|Word‑p. 94

10.1.7.3.1  Dynamic data associated with a functional alias in MC service serverWord‑p. 94
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