Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.280  Word version:  18.1.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…   11…   11.5…   11.5.2…   11.5.3…   A…   B…

 

10.8.4  De-affiliation from MC service group(s)Word‑p. 166

10.8.4.1  GeneralWord‑p. 166

When an MC service user does not want to communicate with an MC service group anymore for a single MC service, then the MC service user can revoke its affiliation to the MC service group.

10.8.4.2  MC service group de-affiliation procedureWord‑p. 166

The procedure for revoking the affiliation with an MC service group for a single MC service is described in Figure 10.8.4.2-1.
Pre-conditions:
  1. MC service server has already subscribed to the MC service group information from group management server and has stored the data of MC service group(s) to which the MC service user is affiliated to;
  2. The MC service client triggers the de-affiliation procedure. This is an explicit de-affiliation requested either by the MC service user or determined by a trigger event such as the MC service UE moving outside a permitted geographic operational area of an MC service group; and
  3. The group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates.
  4. The MC service server has subscribed to the MC service functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. 10.8.4.2-1: MC service group de-affiliation procedure
Up
Step 1.
MC service client requests the MC service server to de-affiliate from an MC service group or a set of MC service groups.
Step 2.
Based on the user profile and stored group policy from the group configuration, the MC service server checks if the user of the MC service client is authorized to de-affiliate from the requested MC service group(s) and if the user of the MC service client has affiliated to the requested MC service group(s). The authorisation check includes whether the MC service user has activated a certain functional alias which prevents de-affiliating or whether the MC service user is the last user who has bound a certain functional alias to the group which also prevents de-affiliating.
Step 3.
If the user of the MC service client has affiliated to the requested MC service group(s), is authorized to de-affiliate from the requested MC service group(s) then the MC service server removes the affiliation status of the user for the requested MC service group(s).
Step 4.
MC service server provides to the MC service client the group de-affiliation response (4a) and updates the group management server with the de-affiliation status of the user for the requested MC service group(s) (4b).
Up

10.8.4.3  De-affiliation from MC service group(s) defined in partner MC service systemWord‑p. 167

The procedure for de-affiliation from affiliated MC service group(s) which is defined in partner MC service system for a single MC service is described in Figure 10.8.4.3-1.
Pre-conditions:
  1. The primary/partner MC service servers have already subscribed to the group information from group management server and stored the data of MC service group(s) to which the MC service user intends to de-affiliate; and
  2. The group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. 10.8.4.3-1: De-affiliation from an MC service group defined in partner MC service system
Up
Step 1.
The MC service client requests the primary MC service server to de-affiliate from an MC service group or a set of MC service groups.
Step 2.
The primary MC service server checks if the MC service client is authorized to de-affiliate from the requested MC service group(s) based on the user profile. The primary MC service server performs the check if the user has affiliated to the MC service groups.
Step 3.
Based on the MC service group information included in the request, the primary MC service server determines to send MC service group de-affiliation request to the corresponding partner MC service server. The request may be routed through some intermediate signalling nodes.
Step 4.
Based on the stored group policy from the group configuration, the partner MC service server checks if the MC service group is not disabled and if the user of the MC service client has affiliated to the requested MC service group(s) and is authorized to de-affiliate from the requested MC service group(s).
Step 5.
If the user of the MC service client has affiliated to the requested MC service group(s) and is authorized to de-affiliate to the requested MC service group(s), then the partner MC service server removes the affiliation status of the user for the requested MC service group(s).
Step 6.
The partner MC service server sends the MC service group de-affiliation response to primary MC service server (6a) and updates the group management server with the de-affiliation status of the user for the requested MC service group(s) (6b).
Step 7.
The primary MC service server will remove any information stored about the user's affiliation with requested MC service group(s) of partner MC service system.
Step 8.
The primary MC service server sends the MC service group de-affiliation response to the MC service client.
Up

10.8.4.4  MC server initiated group de-affiliation procedure |R15|Word‑p. 168

The procedure for the MC service server to trigger a de-affiliation with an MC service group is described in Figure 10.8.4.4-1.
Pre-conditions:
  1. The MC service user has previously affiliated to the group, and the MC service server has stored the status of MC service group affiliation;
  2. Following a relevant trigger condition, e.g. the user moving outside the permitted geographical operational area of the MC service group, or the permitted geographical operational area is modified, causing user outside of the permitted geographical operational area, the MC service server de-affiliates the user from the MC service group; and
  3. The group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates.
  4. The MC service server has subscribed to the MC service functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. 10.8.4.4-1: MC service server initiated group de-affiliation procedure
Up
Step 1.
The MC service server determines the MC service client could be de-affiliated to the group again due to the trigger event, e.g. the permitted geographical operational area is modified, causing the user outside of the permitted geographical operational area of the MC service group, the MC service server needs to de-affiliate the MC Service user from the group.
Step 2.
The MC service server changes the affiliation status of the user.
Step 3.
The MC service server updates the group management server with the de-affiliation status of the user for the requested MC service group(s).
Step 4.
The MC service server provides a de-affiliation notification with the group information to the MC service client.
Up

10.8.4.5  MC server initiated group de-affiliation from group defined in partner MC service system |R15|Word‑p. 169

The procedure for the MC service server to trigger a de-affiliation from an MC service group which is defined in partner MC service system is described in Figure 10.8.4.5-1.
Pre-conditions:
  1. The MC service user has previously affiliated to the group, and the MC service server has stored the status of MC service group affiliation;
  2. Following a relevant trigger condition (e.g. the user moving outside the permitted geographical operational area of the MC service group, or the permitted geographical operational area is modified), the de-affiliation for the MC service user is initiated by the MC service server from the MC service group;
  3. The primary/partner MC service servers have already subscribed to the group information from group management server and stored the data of MC service group(s) to which the MC service user intends to de-affiliate; and
  4. The group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. 10.8.4.5-1: MC service server initiated group de-affiliation from group in partner system procedure
Up
Step 1.
The MC service server determines the MC service client could be de-affiliated to the group due to the trigger event, e.g. the permitted geographical operational area is modified, causing the user outside of the permitted geographical operational area of the MC service group, the MC service server needs to de-affiliate the MC Service user from the group.
Step 2.
Based on the stored MC service group information, the primary MC service server determines to send MC service group de-affiliation request to the corresponding partner MC service server. The request may be routed through some intermediate signalling nodes.
Step 3.
Based on the stored group policy from the group configuration, the partner MC service server checks if the MC service group is not disabled and if the user of the MC service client has affiliated to the requested MC service group(s) and is authorized to de-affiliate from the requested MC service group(s).
Step 4.
If the user of the MC service client has affiliated to the requested MC service group(s) and is authorized to de-affiliate to the requested MC service group(s), then the partner MC service server removes the affiliation status of the user for the requested MC service group(s).
Step 5.
The partner MC service server sends the MC service group de-affiliation response to primary MC service server (5a) and updates the group management server with the de-affiliation status of the user for the requested MC service group(s) (5b).
Step 6.
The primary MC service server changes the affiliation status of the user.
Step 7.
The MC service server provides a de-affiliation notification with the group information to the MC service client.
Up

10.8.5  Remote change of affiliationWord‑p. 171

10.8.5.1  Remote change of affiliation for groups defined in primary MC systemWord‑p. 171

10.8.5.1.1  Authorized user remotely changes another MC service user's affiliated MC service group(s) - mandatory modeWord‑p. 171
The procedure for an authorized user to remotely change another MC service user's affiliated MC service group(s) for a single MC service without requiring the target user's approval is described in Figure 10.8.5.1.1-1.
Pre-conditions:
  1. The MC service client 1 (authorized user 1) has already been provisioned (statically or dynamically) with the target MC service user's information and its group information, that target MC service user 2 is allowed to be affiliated or de-affiliated;
  2. The primary MC service server may have retrieved the user profile or group policy from the group configuration e.g. information regarding user(s) authorization to affiliate or to de-affiliate to MC service group(s), priority, and other related configuration data; and
  3. The group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. 10.8.5.1.1-1: Remotely change MC service group affiliation - mandatory mode
Up
Step 1.
When an authorized user requires one or more MC service users to change the affiliation to an MC service group or set of MC service groups, the MC service client 1 of the authorized user 1 sends MC service group affiliation change request with the indication of mandatory mode to the primary MC service server. The information used to indicate the change of the affiliation relationship between the target MC service user 2 and the MC service group(s) shall be included.
Step 2.
The primary MC service server shall check if the MC service user 1 is authorized to initiate the change of the affiliation relationship between the target user 2 and the MC service group(s). The primary MC service server shall check if the target MC service user(s) are authorized for the requested affiliation relationship based on the user profile. The primary MC service server also performs the check for the maximum limit on the total number (N2) of MC service groups that the user can be affiliated to simultaneously.
Step 3a.
The primary 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, the MC service server subscribes to the group policy from the group configuration from the group management server.
Step 3b.
The primary MC service server 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 4.
Based on the group policy, the primary MC service server checks if the target MC service user 2 is authorized to affiliate or de-affiliate to the MC service group(s).
Step 5.
If the target MC service user 2 is authorized to affiliate or de-affiliate to the MC service group(s) then the primary MC service server stores the new requested affiliation status of the target MC service user 2 for the MC service group(s).
Step 6.
If the requested affiliation status is a change from the current affiliation status, then the primary MC service server updates the group management server with the affiliation status of the MC service user 2 for the MC service group(s).
Step 7a.
If the requested affiliation status is a change the primary MC service server sends the MC service group affiliation change request with the indication of mandatory mode to MC service client 2 of the target MC service user 2. The target MC service user 2 receives the latest information about the affiliated MC service groups. The MC service client 2 may subscribe to the affiliated MC service groups information with the group management server.
Step 7b.
The MC service user 2 provides a response to the primary MC service server by sending an MC service group affiliation change response.
Step 8.
The primary MC service server sends the MC service group affiliation change response to MC service client 1. If the requested affiliation status was not changed (see 7a), then the MC service server creates an appropriate (accept) MC service group affiliation change response to send to MC service client 1.
Up
10.8.5.1.2  Authorized user remotely changes another MC service user's affiliated MC service group(s) - negotiated modeWord‑p. 172
The procedure for the authorized user to remotely change another MC service user's affiliated MC service group(s) for a single MC service with the target MC service user's approval is described in Figure 10.8.5.1.2-1.
Pre-conditions:
  • The MC service client 1 (authorized user 1) has already been provisioned (statically or dynamically) with target MC service user's information and its group information, that target MC service user 2 is allowed to be affiliated or de-affiliated;
  • The primary MC service server may have retrieved the user profile or group policy from the group configuration e.g. information regarding user(s) authorization to affiliate or to de-affiliate to MC service group(s), priority, and other related configuration data.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. 10.8.5.1.2-1: Remotely change MC service group affiliation - negotiated mode
Up
Step 1.
When an authorized user requires one or more MC service users to change the affiliation to an MC service group or set of MC service groups, the MC service client 1 of the authorized user 1 sends MC service group affiliation change request to the primary MC service server. The information (i.e. target MC service user(s) ID, MC service group(s) ID, requested affiliation status) used to indicate the change of the affiliation relationship between the target MC service user 2 and the MC service group(s) shall be included.
Step 2.
The primary MC service server checks if the MC service user 1 is authorized to initiate the change of the affiliation relationship between the target user 2 and the MC service group(s). The primary MC service server checks if the target MC service user(s) are authorized for the requested affiliation relationship based on the user profile and the group policy from the group configuration (i.e. if not available, the primary MC service server obtains the group policy from the group configuration from the group management server). The primary MC service server also performs the check for the maximum limit on the total number (N2) of MC service groups that the user can be affiliated to simultaneously.
Step 3.
If the target MC service user 2 is authorized to accept the changes to its affiliated MC service group(s), then the primary MC service server sends the MC service group affiliation change request to the MC service client 2 of the target MC service user 2.
Step 4.
If the requested affiliation status is different from the current affiliation status, then the MC service client 2 notifies the MC service group affiliation change request to the target MC service user 2 to receive the approval from the user on the proposed changes to the affiliated MC service group(s).
Step 5.
If the target MC service user 2 provides a response (accept or reject) to the notification, then the MC service client 2 sends an MC service group affiliation change response to the primary MC service server. A response indicating target user 2's acceptance to the requested affiliation change by authorized user 1, triggers the affiliation or de-affiliation procedures at the primary MC service server (see subclause 10.8.3.1 or subclause 10.8.4.2) as per the MC service user 1's requested changes to the target user 2's affiliated group(s).
Step 6.
The primary MC service server sends the MC service group affiliation change response to the MC service client 1. If the requested affiliation status was not changed (see 4), then the MC service server creates an appropriate (accept) MC service group affiliation change response to send to MC service client 1.
Up

10.8.5.2  Remote change of affiliation for groups defined in partner MC systemWord‑p. 174

10.8.5.2.1  Authorized user remotely changes another MC service user's affiliated MC service group(s) defined in partner MC system - mandatory modeWord‑p. 174
The procedure for the authorized user to remotely change another MC service user's affiliated MC service group(s) defined in partner MC systems for a single MC service without requiring the target user's approval is described in Figure 10.8.5.2.1-1.
Pre-conditions:
  1. The MC service client 1 (authorized user) has already been provisioned (statically or dynamically) with the target MC service user 2's information and group information, that the target MC service user 2 is allowed to be affiliated or de-affiliated;
  2. The MC service client 1 (authorized user 1), MC service client 2 (target MC service user 2), and the primary MC service server belong to the same MC system;
  3. The partner MC service server may have retrieved the group related information from the group management server;
  4. The primary MC service server may have retrieved the user policy e.g. user related information regarding user(s) authorization to affiliate or to de-affiliate to MC service group(s), priority, and other related configuration data; and
  5. The partner group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. 10.8.5.2.1-1: Remote change MC service group affiliation defined in partner MC system - mandatory mode
Up
Step 1.
When an authorized user requires one or more MC service users to change the affiliation to an MC service group or set of MC service groups, the MC service client 1 of the authorized user 1 sends MC service group affiliation change request with the indication of mandatory mode to the primary MC service server. The information (i.e. target MC service user(s) ID, MC service group(s) ID, requested affiliation status) used to indicate the change of the affiliation relationship between the target MC service user 2 and the MC service group(s) shall be included.
Step 2.
The primary MC service server shall check if the MC service user 1 is authorized to initiate the change of the affiliation relationship between the target user 2 and the MC service group(s). The primary MC service server shall check if the target MC service user(s) are authorized for the requested affiliation relationship based on the user profile. The primary MC service server also performs the check for the maximum limit on the total number (N2) of MC service groups that the user can be affiliated to simultaneously.
Step 3.
Based on the MC service group information included in the request, the primary MC service server determines to send MC service group affiliation change request to the corresponding partner MC service server (group host server).
Step 4a.
The partner MC service server checks if the group policy is locally cached. If the group policy is not locally cached on the partner MC service server then the partner MC service server subscribes to the group policy from the group configuration from the group management server.
Step 4b.
The partner MC service server 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 partner MC service server checks if the target MC service user 2 is authorized to affiliate to the MC service group(s). It is possible that the target MC service user 2 affiliates to one or more MC service groups and also de-affiliates from one or more MC service groups.
Step 6.
If the target MC service user 2 is authorized to affiliate or de-affiliate to the MC service group(s) and if the requested affiliation status is different to the current affiliation status, then the partner MC service server stores the new affiliation status of the target MC service user 2 for the MC service group(s).
Step 7.
The partner MC service server sends the MC service group affiliation change response to the primary MC service server.
Step 8.
The partner MC service server updates the group management server with the affiliation status of the target MC service user 2 for the MC service group(s).
Step 9.
If the requested affiliation status is different to the current affiliation status, then the primary MC service server stores the new affiliation status of the target MC service user 2 for the MC service group(s).
Step 10a.
If the requested affiliation status is different to the current affiliation status, then the primary MC service server sends the MC service group affiliation change request with the indication of mandatory mode to MC service client 2 of the target MC service user 2. The target MC service user 2 receives the latest information about the affiliated MC service groups. Further the MC service client 2 may subscribe for the affiliated MC service groups information with the group management server.
Step 10b.
The target MC service client 2 provides an MC service group affiliation change response to the MC service server.
Step 11.
The primary MC service server sends the MC service group affiliation change response to MC service client 1 (authorized user). If the requested affiliation status was not changed (see 10a), then the MC service server creates an appropriate (accept) MC service group affiliation change response to send to MC service client 1.
Up

Up   Top   ToC