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.13.3  Authorised MC service user retrieves active functional alias(es) for certain MC service user(s)Word‑p. 226

An authorised MC service user can request the active functional alias(es) for one or more MC service users.
Figure 10.13.3-1 below illustrates the active functional alias list query for the MC service user(s).
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.13.3-1: Active functional alias list query for the user
Up
Step 1.
The MC service client of the MC service user requests the list(s) of active functional aliases for each MC service user(s) from the MC service server by sending an active functional alias information user query request. The MC service ID(s) to be queried is included.
Step 2.
The MC service server checks whether the MC service user is authorized to perform the query. If authorized, then the MC service server retrieves the requested active functional alias information based on the MC service ID(s).
Step 3.
The MC service server sends an active functional alias information user query response including the functional alias information to the MC service client.
Up

10.13.4  MC service user activates functional alias(es) within an MC systemWord‑p. 227

The procedure for MC service user activates functional alias(es) within an MC system is illustrated in Figure 10.13.4-1.
Pre-conditions:
  1. MC service client has already been provisioned (statically or dynamically) with the functional alias(es) information that the MC service client is allowed to activate.
  2. MC service server may have retrieved the user profile and functional alias policy from the functional alias configuration e.g. which user(s) are authorized to activate to what functional alias, priority, and other configuration data.
  3. MC service client may have indicated to the functional alias management server that it wishes to receive updates of functional alias data for the functional aliases for which it is authorized.
  4. The MC service client triggers the functional alias activation procedure. This is an explicit activation 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 a functional alias.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.13.4-1: Functional alias activation procedure within an MC system
Up
Step 1.
MC service client of the MC service user requests the MC service server to activate a functional alias or a set of functional aliases.
Step 2.
The MC service server checks if there are any conflicts with active functional alias(es).
Step 3.
If the user of the MC service client is authorised to activate the requested functional alias(es) then the MC service server stores the functional alias(es) status of the requested functional alias(es).
If a certain functional alias(es) can be simultaneously active for multiple MC service users and the upper limit of number of simultaneous MC service users is not reached, the MC service shall activate the functional alias(es) for the MC service user and inform all other MC service user(s) with sharing the same functional alias(es) (step 5). If the limit of number of simultaneous MC service users is reached or the functional alias is not allowed to be shared, the request is rejected and the MC service user is notified (step 4).
If the functional alias(es) is (are) already used by another MC service user(s), an authorized MC service user gets an offer to take over the functional alias from the MC service user currently using the functional alias(es).
Step 4.
MC service server sends a functional alias(es) activation response to the MC service client.
Step 5.
The MC service server informs all other MC service user(s) sharing the same functional alias(es).
Up

10.13.5  MC service user de-activates functional alias(es) within an MC systemWord‑p. 228

The procedure for MC service user de-activates functional alias(es) within an MC system is illustrated in Figure 10.13.5-1.
When an MC service user does not want to use a functional alias(es) anymore, then the MC service user can de-activate functional alias(es).
Pre-conditions:
  1. MC service server has already subscribed to the functional alias(es) information from the functional alias management server and has stored the data of the functional alias(es) a MC service user has activated.
  2. The MC service client triggers the functional alias(es) de-activation procedure. This is an explicit de-activation request 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 a functional alias.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.13.5-1: Functional alias de-activation procedure within an MC system
Up
Step 1.
MC service client requests the MC service server to de-activate a functional alias or a set of functional aliases.
Step 2.
Based on the MC service user profile and stored functional alias policy from the functional alias configuration, the MC service server checks if the MC service user of the MC service client is authorized to de-activate from the requested functional alias(es) and if the MC service user of the MC service client has activated to the requested functional alias(es).
Step 3.
If the MC service user is authorized to de-activate from the requested functional alias(es) then the MC service server updates the functional alias activation status of the MC service user.
Step 4.
MC service server provides to the MC service client the functional alias de-activation response.
Step 5.
The MC service server informs all other MC service user(s) sharing the same functional alias(es).
Up

10.13.6  Authorised MC service user takes over functional alias(es) within an MC systemWord‑p. 229

The procedure for MC service user takes over functional alias(es) within an MC system is illustrated in Figure 10.13.6-1.
During functional alias(es) activation, if the functional alias(es) is (are) already used by another MC service user(s), an authorized MC service user may get an offer to take over the functional alias(es) from the MC service user currently using the functional alias(es).
Pre-conditions:
  1. MC service client 1 has performed the functional alias(es) activation procedure as described in subclause 10.13.4.
  2. As result of the functional alias(es) activation procedure, the MC service user of MC service client 1 is aware which functional alias(es) are already used but can be taken over.
  3. The MC service user of MC service client 1 decides to take over a functional alias.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.13.6-1: Functional alias taking over procedure within an MC system
Up
Step 1.
MC service client 1 of the MC service user 1 requests the MC service server to take over a functional alias by sending a functional alias take over request.
Step 2.
The MC service server checks if there are any conflicts taking over the functional alias.
Step 3.
If the user of the MC service client 1 is authorised to take over the requested functional alias then the MC service server sends a functional alias revoke notification to inform MC service client 2 that the functional alias has been revoked and is not any longer active for the user of MC service client 2.
Step 4.
The MC service server stores the functional alias status of the requested functional alias.
Step 5.
MC service server sends a functional alias take over response to the MC service client.
Step 6.
The MC service server informs all other MC service user(s) sharing the same functional alias.
Up

10.13.7  Authorised MC service user retrieves MC service user(s) for certain active functional alias(es) |R16|Word‑p. 230

An authorised MC service user can request the MC service user(s) who have activated the functional alias being queried, for one or more functional aliases.
Figure 10.13.7-1 below illustrates the query of usage of the active functional alias(es) procedure.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.13.7-1: Query of usage of the active functional alias(es)
Up
Step 1.
The MC service client of the MC service user requests the list(s) of MC service user(s) who have actived the functional alias being queried, by sending an active functional alias information usage query request. The functional alias(es) to be queried are included.
Step 2.
The MC service server checks whether the MC service user is authorized to perform the query. If authorized, then the MC service server retrieves the requested MC service user(s) information for those MC service users who have actived the functional alias being queried.
Step 3.
The MC service server sends an active functional alias information usage query response including the MC service user information to the MC service client.
Up

10.13.8  Automatic activation of functional alias(es) within an MC system |R16|Word‑p. 230

The MC Service Server can automatically activate functional aliases that can be specified by internal or external triggers such as location dependency, schedule, or timer.
The procedure for automatic activation of functional alias(es) within an MC system is illustrated in Figure 10.13.8-1. The MC service client(s) get(s) notified by the MC service server at the time when a functional alias has been activated by the MC service server.
Pre-conditions:
  1. MC service server may have retrieved the MC service user profile and functional alias policy from the functional alias configuration, for example, which MC service user(s) are authorized to activate which functional alias(es), to use corresponding priorities and other configuration data associated with the functional alias.
  2. MC service server has already been provisioned with the functional alias(es) information that the MC service client is allowed to activate.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.13.8-1: Automatic functional alias activation within an MC system
Up
Step 1.
The condition e.g. timer or current location of the MC service user for automatic functional alias(es) activation is met.
Step 2.
The MC service server checks if there are any conflicts with current active functional alias(es).
  1. If a certain functional alias(es) can be simultaneously active for multiple MC service users and the upper limit of simultaneous MC service users is not reached, the MC service server shall activate the functional alias(es) for the corresponding MC service user and inform all other MC service user(s) that are sharing the same functional alias(es) (step 5).
  2. If the limit of simultaneous MC service users is reached or the functional alias is not allowed to be shared then the MC service server does not proceed with the functional alias(es) activation procedure or the MC service server can reassign the functional alias, i.e. takeover, from the MC service user currently using the functional alias(es) to the new MC service client.
Step 3.
MC service server notifies the MC service client about the activation of the functional alias(es).
Step 4.
The MC service server stores the functional alias(es) status for the functional alias(es), including date and time of activation.
Step 5.
The MC service server informs all other MC service user(s) sharing the same functional alias(es).
Up

10.13.9  Automatic deactivation of functional alias(es) within an MC system |R16|Word‑p. 231

The MC Service Server can automatically activate functional aliases that can be specified by internal or external triggers such as location dependency, schedule, or timer.
The procedure for automatic deactivation of functional alias(es) within an MC system is illustrated in Figure 10.13.9-1. The MC service client(s) get(s) notified by the MC service server at the time when a functional alias has been deactivated by the MC service server.
Pre-conditions:
  1. MC service server has already retrieved the relevant functional alias(es) information from the configuration (functional alias) management server and has stored the data of the concerning functional alias(es) a MC service user has activated.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.13.9-1: Automatic functional alias deactivation within an MC system
Up
Step 1.
The condition e.g. timer or current location of the MC service user for automatic functional alias(es) deactivation is met. The trigger for deactivation may be done by the MC system or by an authorized external system attached to the MC system.
Step 2.
MC service server notifies the MC service client about the deactivation of the functional alias(es).
Step 3.
The MC service server stores the status, e.g. deactivated, of the concerned functional alias(es) and the corresponding MC service ID(s).
Step 4.
The MC service server informs all other MC service user(s) sharing the same functional alias(es).
Up

10.13.10  Subscription and notification for functional alias |R16|Word‑p. 233

10.13.10.1  GeneralWord‑p. 233

The subscriber (e.g. MC service server, location management server) obtains the list of MC service users who have activated a functional alias from the functional alias controlling MC service server via subscription and notification mechanisms.

10.13.10.2  Subscription for functional alias procedureWord‑p. 233

The procedure for subscription for functional alias is described in Figure 10.13.10.2-1.
Pre-conditions:
  • The functional alias controlling MC service server holds a list of MC service users who has activated the functional alias.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.13.10.2-1: Subscription for functional alias
Up
Step 1.
The subscriber sends a subscribe functional alias request to the functional alias controlling MC service server in order to receive notifications about the list of MC service users who has activated the function alias.
Step 2.
The functional alias controlling MC service server provides a subscribe functional alias response to the subscriber indicating success or failure of the request.

10.13.10.3  Notification for functional alias procedureWord‑p. 234

The procedure for notification for functional alias as shown in Figure 10.13.10.3-1 is used by the functional alias controlling MC service server to inform the subscriber about MC service users who has activated the functional alias.
Pre-conditions:
  • The subscriber has subscribed to the functional alias
  • The list of MC service users who has activated the functional alias is changed at functional alias controlling MC service server due to activation, deactivation or taken over.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.13.10.3-1: Notification for the functional alias
Up
Step 1.
The functional alias controlling MC service server provides the list of MC service users who has activated the functional alias in the notify functional alias request to the subscriber.
Step 2.
The subscriber provides a notify functional alias response to the functional alias controlling MC service server.

10.13.10.4  Unsubscription for functional alias procedureWord‑p. 234

The procedure for unsubscription for functional alias is described in Figure 10.13.10.4-1.
Pre-conditions:
  • The functional alias controlling MC service server holds a list of MC service users who has activated the functional alias.
Copy of original 3GPP image for 3GPP TS 23.280, Figure 10.13.10.4-1: Unsubscription for functional alias
Up
Step 1.
The subscriber sends a unsubscribe functional alias request to the functional alias controlling MC service server in order to stop receiving notifications about the list of MC service IDs who has activated the function alias.
Step 2.
The functional alias controlling MC service server provides a subscribe functional alias response to the subscriber indicating success or failure of the request.

10.13.11  Functional alias to group binding |R17|Word‑p. 235

10.13.11.1  GeneralWord‑p. 235

The MC service client creates a functional alias to group binding association to be stored within the group controlling MC server. Once a functional alias is bound to a group it is bound till the functional alias is unbound to the group. After an MC service log-off the user's functional alias to group bindings are deleted.

10.13.11.2  Functional alias to group bindingWord‑p. 235

The procedure for binding a functional alias with a group is described in Figure 10.13.11.2-1.
Pre-conditions:
  • 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, Figure 10.13.11.2-1: Functional alias to group binding procedure
Up
Step 1.
The MC service client sends a functional alias to group binding request to the group controlling MC service server to bind functional aliases to groups to be used for communications within those groups.
Step 2.
The group controlling MC service server provides a functional alias to group binding response to the MC service client indicating success or failure of the request.

10.13.11.3  Functional alias to group unbindingWord‑p. 235

The procedure for unbinding a functional alias with a group is described in Figure 10.13.11.3-1.
Pre-conditions:
  • 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, Figure 10.13.11.3-1: Functional alias to group unbinding procedure
Up
Step 1.
The MC service client sends a functional alias to group unbinding request to the group controlling MC service server to unbind functional aliases from groups which are not used for communications within those groups anymore.
Step 2.
The group controlling MC service server provides a functional alias to group unbinding response to the MC service client indicating success or failure of the request. The MC service server also checks whether the MC service client is the last client who has bound a certain functional alias to a group which may prevent unbinding that functional alias from the group.
Up

Up   Top   ToC