Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.280  Word version:  19.2.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…   10.17.3…   10.17.5…   11…   11.3…   11.5…   11.5.2…   11.5.3…   11.5.3.3.2A…   11.5.4…   A…   B…   C…

 

10.8.4  De-affiliation from MC service group(s)p. 169

10.8.4.1  Generalp. 169

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 procedurep. 169

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.
Reproduction of 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), either for the requesting specific MC service client only, or for all MC service clients, where this user has logged on to.
Step 4.
MC service server provides to the MC service client the group de-affiliation response (4a). When the MC service user has logged into multiple MC service clients concurrently, the MC service server updates the group management server with the de-affiliation status of the user for the requested MC service group(s) only when the MC service ID de-affiliates for the provided MC service group(s) from the last MC service client. If the MC service user has logged into only one client then the MC service server and update 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 systemp. 170

The procedure for de-affiliation from affiliated MC service group(s) which is defined in partner MC 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.
Reproduction of 3GPP TS 23.280, Fig. 10.8.4.3-1: De-affiliation from an MC service group defined in partner MC 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), either for the requesting specific MC service client only, or for all MC service clients, where this user has logged on to.
Step 6.
The partner MC service server sends the MC service group de-affiliation response to primary MC service server (6a) . When the MC service user has logged into multiple MC service clients concurrently, the MC service server updates the group management server with the de-affiliation status of the user for the requested MC service group(s) only when the MC service ID de-affiliates for the provided MC service group(s) from the last MC service client. If the MC service user has logged into only one client then the MC service server 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 system, considering that the user may have logged on to multiple MC service clients and that de-affiliation may have been performed only for the specific MC service client from which the de-affiliation request has been sent, or for all MC service clients, where this user has been affiliated to this MC service group.
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|p. 172

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.
Reproduction of 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 system |R15|p. 172

The procedure for the MC service server to trigger a de-affiliation from an MC service group which is defined in partner MC 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.
Reproduction of 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

Up   Top   ToC