Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

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

 

10.13.10  Subscription and notification for functional alias |R16|p. 270

10.13.10.1  Generalp. 270

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

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.
Reproduction of 3GPP TS 23.280, Fig. 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 procedurep. 272

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.
Reproduction of 3GPP TS 23.280, Fig. 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 procedurep. 272

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.
Reproduction of 3GPP TS 23.280, Fig. 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|p. 272

10.13.11.1  Generalp. 272

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 bindingp. 272

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.
Reproduction of 3GPP TS 23.280, Fig. 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 unbindingp. 272

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.
Reproduction of 3GPP TS 23.280, Fig. 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