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.3.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.17…   10.17.3…   10.17.5…   11…   11.3…   11.5…   11.5.2…   11.5.3…   11.5.3.3.2A…   A…   B…   C…   E… 
10.8 Affiliation and de-affiliation to/from MC service group(s)  10.8.1 General  10.8.2 Information flows  10.8.2.1 MC service group affiliation request  10.8.2.2 MC service group affiliation request (MC service server - MC service server)  10.8.2.3 MC service group affiliation response  10.8.2.4 MC service group affiliation response (MC service server - MC service server)  10.8.2.6 MC service group de-affiliation request  10.8.2.7 MC service group de-affiliation request (MC service server - MC service server)  10.8.2.8 MC service group de-affiliation response  10.8.2.9 MC service group de-affiliation response (MC service server - MC service server)  10.8.2.11 MC service group affiliation change request  10.8.2.12 MC service group affiliation change response  10.8.2.13 MC service group de-affiliation notification  10.8.2.14 Notify group dynamic data request  10.8.3 Affiliation  10.8.3.1 MC service group affiliation procedure  10.8.3.2 Affiliation to MC service group(s) defined in partner MC system without topology hiding  10.8.3.2a Affiliation to MC service group(s) defined in partner MC system using topology hiding 
...

 

10.8  Affiliation and de-affiliation to/from MC service group(s)  p. 161

10.8.1  General  p. 161

The following subclauses specify the procedures for affiliation and de-affiliation to a single MC service, and which are utilised by the following MC services:
MC service specific pre-requisites and resultant behaviour by functional entities in performing these procedures are specified in the respective MC service TSs as listed above.
Up

10.8.2  Information flows  p. 161

10.8.2.1  MC service group affiliation request  p. 161

Table 10.8.2.1-1 describes the information flow MC service group affiliation request from the MC service client to the MC service server.
Information element Status Description
MC service IDMThe MC service ID of the originator who triggers the MC service group affiliation request.
MC service group ID listMA list of one or more MC service group IDs to which the originator intends to affiliate.
Up

10.8.2.2  MC service group affiliation request (MC service server - MC service server)  p. 161

Table 10.8.2.2-1 describes the information flow MC service group affiliation request between the MC service servers.
Information element Status Description
MC service IDMThe MC service ID of the originator who triggers the MC service group affiliation request.
MC service group ID listMA list of one or more MC service group IDs to which the originator intends to affiliate and is defined in the destination MC system.
Up

10.8.2.3  MC service group affiliation response  p. 161

Table 10.8.2.3-1 describes the information flow MC service group affiliation response from the MC service server to the MC service client. This information flow is sent individually addressed on unicast or multicast.
Information element Status Description
MC service IDMThe MC service ID of the originator who triggers the MC service group affiliation request.
MC service group ID listMA list of one or more MC service group IDs to which the originator intends to affiliate.
Affiliation status per MC service group IDMIndicates the affiliation result for every MC service group ID in the list.
Up

10.8.2.4  MC service group affiliation response (MC service server - MC service server)  p. 162

Table 10.8.2.4-1 describes the information flow MC service group affiliation response between the MC service servers.
Information element Status Description
MC service IDMThe MC service ID of the originator who triggers the MC service group affiliation request.
MC service group ID listMA list of one or more MC service group IDs to which the originator intends to affiliate and is defined in the destination MC system.
Affiliation status per MC service group IDMIndicates the affiliation result for every MC service group ID in the list.
Up

10.8.2.5  Void

10.8.2.6  MC service group de-affiliation request  p. 162

Table 10.8.2.6-1 describes the information flow MC service group de-affiliation request from the MC service client to the MC service server.
Information element Status Description
MC service IDMThe MC service ID of the originator who triggers the MC service group de-affiliation request.
MC service group ID listMA list of one or more MC service group IDs to which the originator intends to de-affiliate.
Scope of De-affiliation requestMIndicating, whether de-affiliation is requested for this specific MC service client only, or for all MC service clients where this MC service ID has logged on.
Up

10.8.2.7  MC service group de-affiliation request (MC service server - MC service server)  p. 162

Table 10.8.2.7-1 describes the information flow MC service group de-affiliation request between the MC service servers.
Information element Status Description
MC service IDMThe MC service ID of the originator who triggers the MC service group de-affiliation request.
MC service group ID listMA list of one or more MC service group IDs to which the originator intends to de-affiliate and is defined in the destination MC system.
Scope of De-affiliation requestMIndicating, whether de-affiliation is requested for this specific MC service client only, or for all MC service clients where this MC service ID has logged on.
Up

10.8.2.8  MC service group de-affiliation response  p. 162

Table 10.8.2.8-1 describes the information flow MC service group de-affiliation response from the MC service server to the MC service client. This information flow is sent individually addressed on unicast or multicast.
Information element Status Description
MC service IDMThe MC service ID of the originator who triggers the MC service group de-affiliation request.
MC service group ID listMA list of one or more MC service group IDs to which the originator intends to de-affiliate.
De-affiliation status per MC service group IDMIndicates the de-affiliation result for every MC service group ID in the list.
Up

10.8.2.9  MC service group de-affiliation response (MC service server - MC service server)  p. 163

Table 10.8.2.9-1 describes the information flow MC service group de-affiliation response between MC service servers.
Information element Status Description
MC service IDMThe MC service ID of the originator who triggers the MC service group de-affiliation request.
MC service group ID listMA list of one or more MC service group IDs to which the originator intends to de-affiliate and is defined in the destination MC system.
De-affiliation status per MC service group IDMIndicates the de-affiliation result for every MC service group ID in the list.
Up

10.8.2.10  Void

10.8.2.11  MC service group affiliation change request  p. 163

Table 10.8.2.11-1 describes the information flow MC service group affiliation change request from the MC service client to the MC service server.
Information element Status Description
MC service IDMThe MC service ID of the originator who triggers the MC service group affiliation change request.
MC service ID listMA list of one or more MC service IDs to which the originator intends to the change their MC service group affiliation relationship.
MC service group ID list (per listed MC service ID)MA list of one or more MC service group IDs to which the originator intends to change their affiliation relationship with the target user.
Requested affiliation status (per group ID)MIndicates if the request is to affiliate or deaffiliate
Change request typeMIndicates the affiliation request type, i.e. mandatory or negotiated
Up

10.8.2.12  MC service group affiliation change response  p. 163

Table 10.8.2.12-1 describes the information flow MC service group affiliation change response from the MC service server to the MC service client. This information flow is sent individually addressed on unicast or multicast.
Information element Status Description
MC service IDMThe MC service ID of the originator who triggers the MC service group affiliation request.
MC service ID listMA list of one or more MC service IDs to which the originator intends to the change their MC service group affiliation relationship.
MC service group ID listMA list of one or more MC service group IDs to which the originator intends to change their affiliation relationship with the target user.
Affiliation status per MC service group IDMIndicates the affiliation relationship change result for every MC service group ID in the list.
Up

10.8.2.13  MC service group de-affiliation notification |R15|  p. 164

Table 10.8.2.13-1 describes the information flow MC service group de-affiliation notification from the MC service server to the MC service client. This information flow is sent individually addressed on unicast or multicast.
Information element Status Description
MC service IDMThe MC service ID of the MC service user that will be de-affiliated.
MC service group ID listMA list of one or more MC service group IDs to which the originator intends to de-affiliate.
De-affiliation status per MC service group IDMIndicates the de-affiliation result for every MC service group ID in the list.
Up

10.8.2.14  Notify group dynamic data request |R16|  p. 164

Table 10.8.2.14-1 describes the information flow notify group dynamic data request from the MC service server to the group management server.
Information element Status Description
MC service group IDMThe MC service group ID to which the GMS has subscribed and for which the group dynamic data needs to be updated.
MC service IDMThe MC service ID for which the group dynamic data (e.g. affiliation status, de-affiliation status) needs to be updated.
Affiliation or de-affiliation statusMIndicates the affiliation status or de-affiliation status for the MC service group ID.
Up

10.8.3  Affiliation  p. 164

10.8.3.1  MC service group affiliation procedure  p. 164

Procedure for affiliation to MC service group(s) for a single MC service is described in Figure 10.8.3.1-1.
Pre-conditions:
  1. MC service client has already been provisioned (statically or dynamically) with the group information, or a pointer to the group information, that the MC service client is allowed to be affiliated;
  2. MC service server may have retrieved the user profile and group policy from the group configuration e.g. which user(s) are authorized to affiliate to what MC service group(s), priority, and other configuration data;
  3. MC service client may have indicated to the group management server that it wishes to receive updates of group configuration data for MC service groups(s) for which it is authorized (as described in subclause 10.1.5.3);
  4. The MC service client triggers the affiliation procedure. This is an explicit affiliation caused either by the MC service user or determined by a trigger event such as the MC service UE coming within a permitted geographic operational area of an MC service group; and
  5. The group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates.
Reproduction of 3GPP TS 23.280, Fig. 10.8.3.1-1: MC service group affiliation procedure
Figure 10.8.3.1-1: MC service group affiliation procedure
Up
Step 1.
MC service client of the MC service user requests the MC service server to affiliate to an MC service group or a set of MC service groups.
Step 2a.
MC service server checks if the group policy is locally cached. If the group policy is not locally cached on the MC service server then MC service server requests the group policy from the group configuration from the group management server.
Step 2b.
MC service server receives the group policy from the group configuration from the group management server.
Step 3.
Based on the group policy from the group configuration and user profile, the MC service server checks if the MC service group(s) is enabled and if the MC service client is authorised to affiliate to the requested MC service group(s). The MC service server also performs the check for the maximum limit of the total number (N2) of MC service groups that the user can be affiliated to simultaneously.
Step 4.
If the user of the MC service client is authorised to affiliate to the requested MC service group(s) then the MC service server stores the affiliation status of the user for the requested MC service group(s).
Step 5.
MC service server confirms to the MC service client the affiliation (5a) and updates the group management server with the affiliation status of the user for the requested MC service group(s) (5b).
Up

10.8.3.2  Affiliation to MC service group(s) defined in partner MC system without topology hiding  p. 165

10.8.3.2.1  Functional description  p. 165
When an MC service client wants to affiliate to MC service group(s) which is defined in a partner MC system for a single MC service and where topology hiding is not required, it shall be subject to authorization from the partner MC system where the MC service group(s) is defined, and whether it subjects to authorization from the primary MC system is conditional.
10.8.3.2.2  Procedure  p. 166
The procedure for affiliation to MC service group(s) which is defined in a partner MC system where topology hiding is not required for a single MC service is described in Figure 10.8.3.2.2-1.
Pre-conditions:
  1. The MC service client has already been provisioned (statically or dynamically) with the group information, or a pointer to the group information, that the MC service client is allowed to be affiliated;
  2. The MC service server of the primary MC system may have locally cached the MC service group affiliation status of the MC service user;
  3. The MC service server of the partner MC system may have retrieved the group related information from the group management server;
  4. The MC service client may have indicated to the group management server of the partner MC system that it wishes to receive updates of group configuration data for MC service group(s) for which it is authorized (as described in subclause 10.1.5.3);
  5. The MC service user triggers the affiliation procedure. This is an explicit affiliation caused by the MC service user; and
  6. The group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates.
Reproduction of 3GPP TS 23.280, Fig. 10.8.3.2.2-1: Affiliation for an MC service group defined in partner MC system where topology hiding is not required
Figure 10.8.3.2.2-1: Affiliation for an MC service group defined in partner MC system where topology hiding is not required
Up
Step 1.
The MC service client requests the MC service server of the primary MC system to affiliate to an MC service group or a set of MC service groups.
Step 2.
The MC service server of the primary MC system checks if the MC service client is authorized to affiliate to the requested MC service group(s) based on the user profile. The MC service server also performs the check for the maximum limit of the total number (N2) of MC service groups that the user can be affiliated to simultaneously.
Step 3.
Based on the group information included in the request, the MC service server of the primary MC system, it determines to send group affiliation request to the corresponding MC service server of the partner MC system. The request may be routed through intermediate signalling nodes.
Step 4a.
The MC service server of the partner MC system checks if the group policy is locally cached. If the group policy is not locally cached on the MC service server then MC service server subscribes to the group policy from the group configuration from the group management server.
Step 4b.
The MC service server of the partner MC system receives the group policy from the group configuration from the group management server via notification and locally caches the group policy from the group configuration.
Step 5.
Based on the group policy, the MC service server of the partner MC system checks if the MC service group(s) is not disabled and if the user of the MC service client is authorised to affiliate to the requested MC service group(s).
Step 6.
If the user of the MC service client is authorised to affiliate to the requested MC service group(s) then the MC service server of the partner MC system stores the affiliation status of the user for the requested MC service group(s).
Step 7.
The MC service server of the partner MC system sends the affiliation status result of requested MC service group(s) to the MC service server of the primary MC system (7a) and updates the group management server with the affiliation status of the user for the requested MC service group(s) (7b).
Step 8.
The MC service server of the primary MC system stores the affiliation status of the user for the requested MC service group(s).
Step 9.
The MC service server of the primary MC system sends the group affiliation status result for the requested MC service group(s) to the MC service client.
Up

10.8.3.2a  Affiliation to MC service group(s) defined in partner MC system using topology hiding |R15|  p. 167

10.8.3.2a.1  Functional description  p. 167
When an MC service client wants to affiliate to MC service group(s) which is defined in a partner MC system for a single MC service using topology hiding, it shall be subject to authorization from the partner MC system where the MC service group(s) is defined, and may also be subject to authorization from the serving MC system of the MC service client.
10.8.3.2a.2  Procedure  p. 167
Figure 10.8.3.2a.2-1 illustrates the group affiliation procedure to an MC service group defined in the partner MC system of the serving MC system of the MC service user, where topology hiding procedures are required.
Pre-conditions:
  1. MC service client 1 is service authorized within its serving MC system.
  2. The group host MC service server of the MC service group to which the MC service user of MC service client 1 wishes to affiliate is located in the partner MC system of the serving MC system of MC service client 1
  3. Topology hiding is required by both MC systems
  4. The serving MC system of MC service client 1 and the group home MC system are configured to allow topology hiding to take place.
Reproduction of 3GPP TS 23.280, Fig. 10.8.3.2a.2-1: Group affiliation to an MCservice group defined in partner MC system using topology hiding
Figure 10.8.3.2a.2-1: Group affiliation to an MCservice group defined in partner MC system using topology hiding
Up
Step 1.
MC service client 1 initiates an MC service group affiliation request to the serving MC service server of MC service client 1 on behalf of its MC service user.
Step 2.
The MC service server of the serving MC system checks that the MC service client 1 is authorized to affiliate to the requested MC service group based on the user profile, and that the maximum number of MC service groups that the user can be affiliated to (N2) has not been exceeded.
Step 3.
The MC service server determines the group host MC service server of the MC service group. The MC service group is identified to have a different group home MC system, and if topology hiding is required by the serving MC system of MC service client 1, the serving MC system gateway server is determined to act as proxy group host MC service server for the MC service group.
Step 4.
The MC service server of the serving MC system forwards the MC service group affiliation request to the gateway server of the serving MC system.
Step 5.
The gateway server determines which MC system is the group home system for the MC service group.
Step 6.
The gateway server in the serving system of MC service client 1 forwards the MC service group affiliation request to the gateway server of the group home MC system of the MC service group.
Step 7.
The gateway server of the group home MC system of the MC service group determines which MC service server is the group host MC service server for that MC service group.
Step 8.
The gateway server of the group home system of the MC service group forwards the MC service group affiliation request to the group host MC service server of the MC service group.
Step 9.
The group host MC service server in the partner MC system checks whether the user of MC service client 1 is authorized to affiliate to the MC service group based on the MC service group configuration. The group host MC service server may optionally subscribe to the GMS containing the group configuration information, and receive notification of group policy from the group configuration. The group host MC service server shall update the GMS with the affiliation status of the user for the requested MC service group by sending the notify group dynamic data request (not shown in the figure).
Step 10.
The group host MC service server sends an MC service group affiliation response to the gateway server in the group home MC system of the MC service group.
Step 11.
The gateway server in the group home MC system forwards the MC service group affiliation response to the gateway server in the serving MC system of MC service client 1.
Step 12.
The gateway server in the serving MC system of MC service client 1 forwards the MC service group affiliation response to the serving MC service server of MC service client 1.
Step 13.
The serving MC service server of MC service client 1 forwards the MC service group affiliation response to MC service client 1.
Up

Up   Top   ToC