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.283  Word version:  18.1.0

Top   Top   Up   Prev   Next
1…   10…   10.2…   10.2.2…   10.2.3…   10.3…   10.3.3…   10.3.3.7…   10.3.4…   10.3.4.4…   10.3.5…   10.3.5.8…   10.3.6…   10.3.7…   10.3.7.5…   10.3.8…   10.4…   10.4.4…   10.5…   10.5.7…   10.6…   10.6.2…   10.6.2.3…   10.6.3…   10.6.4…   10.7…   10.8…   10.11…   10.11.4…   10.12…   10.14…   10.15… 
10.14 IWF functional alias management  10.14.1 General  10.14.2 IWF information flows for functional alias management  10.14.2.1 IWF functional alias information query request  10.14.2.2 IWF functional alias information query response  10.14.2.3 IWF functional alias activation request  10.14.2.4 IWF functional alias activation response  10.14.2.5 IWF functional alias de-activation request  10.14.2.6 IWF functional alias de-activation response  10.14.2.7 IWF functional alias status notification  10.14.2.8 IWF Functional alias take over request  10.14.2.9 IWF Functional alias take over response  10.14.2.10 IWF Functional alias revoke notification  10.14.3 IWF Functional alias management procedures  10.14.3.1 General  10.14.3.2 User homed in the IWF retrieves active functional alias(es) for a certain MC service user  10.14.3.3 User homed in the IWF activates functional alias(es) within an MC system  10.14.3.4 User homed in the IWF de-activates functional alias(es) within an MC system  10.14.3.5 User homed in the IWF takes over functional alias(es) within an MC system 

 

10.14  IWF functional alias management |R16|  p. 170

10.14.1  General |R17|  p. 170

LMR users homed in the IWF shall have the ability to enable, apply, or disable a functional alias in the MC system for the use in communication with MC service users.
The functional alias feature is not a requirement in TS 22.179 and is therefore an optional feature for systems that support TS 22.179.
Up

10.14.2  IWF information flows for functional alias management |R17|  p. 170

10.14.2.1  IWF functional alias information query request  p. 170

Table 10.14.2.1-1 describes the information flow of the functional alias information query request from the IWF to the MC service server.
Information element Status Description
MC service IDMThe identity of the requesting MC service user.
MC service IDOThe identity of the MC service user to be queried.
Functional aliasOThe functional alias to be queried.
Up

10.14.2.2  IWF functional alias information query response  p. 170

Table 10.14.2.2-1 describes the information flow of the functional alias information query response from the MC service server to the user homed in the IWF.
Information element Status Description
MC service IDMThe identity of the MC service user that performed the query.
MC service IDOThe identity of the MC service user that was queried.
Functional aliasOThe functional alias that was queried.
Query resultMThe functional alias or MC service ID information retrieved from the functional alias management server, i.e. the list of activated functional alias identities of the MC service user or the associated MC service IDs and status which correspond to the queried functional alias.
Up

10.14.2.3  IWF functional alias activation request  p. 171

Table 10.14.2.3-1 describes the information flow of the functional alias activation request from the IWF to the MC service server.
Information element Status Description
MC service IDMThe identity of the requesting MC service user.
Functional alias listMA list of one or more functional aliases which the originator intends to activate.
Up

10.14.2.4  IWF functional alias activation response  p. 171

Table 10.14.2.4-1 describes the information flow of the functional alias activation response from the MC service server to the IWF.
Information element Status Description
MC service IDMThe identity of the MC service user that originated the functional alias activation request.
Functional alias listMA list of one or more functional aliases which the originating party intended to activate.
Activation status per functional aliasMIndicates the activation result for each functional alias in the list (activated, rejected, can be taken over).
Up

10.14.2.5  IWF functional alias de-activation request  p. 171

Table 10.14.2.5-1 describes the information flow functional alias de-activation request from the IWF to the MC service server.
Information element Status Description
MC service IDMThe identity of the requesting MC service user.
Functional alias listMA list of one or more functional aliases which the requesting MC service user intends to de-activate.
Up

10.14.2.6  IWF functional alias de-activation response  p. 171

Table 10.14.2.6-1 describes the information flow of the functional alias de-activation response from the MC service server to the user homed in the IWF.
Information element Status Description
MC service IDMThe identity of the MC service user that originated the functional alias de-activation request.
Functional alias listMA list of one or more functional aliases which the originating party intends to de-activate.
De-activation status per functional aliasMIndicates the de-activation result for every functional alias in the list.
Up

10.14.2.7  IWF functional alias status notification  p. 172

Table 10.14.2.7-1 describes the information flow of the functional alias notification from the MC service server to the IWF.
Information element Status Description
MC service IDMThe identity of the MC service user that originated the functional alias activation, de-activation or take over request.
Functional alias listMA list of one or more functional aliases.
Operational statusMActivation, de-activation or take over status per functional alias.
Up

10.14.2.8  IWF Functional alias take over request  p. 172

Table 10.14.2.8-1 describes the information flow of the functional alias take over request from the IWF to the MC service server.
Information element Status Description
MC service IDMThe identity of the requesting MC service user.
Functional aliasMA functional alias which the requester intends to take over.
Up

10.14.2.9  IWF Functional alias take over response  p. 172

Table 10.14.2.9-1 describes the information flow of the functional alias take over response from the MC service server to the IWF.
Information element Status Description
MC service IDMThe identity of the requesting MC service user.
Functional aliasMA functional alias which the requester intends to take over.
Activation status per functional aliasMIndicates the take over request result (accepted, rejected).
Up

10.14.2.10  IWF Functional alias revoke notification  p. 172

Table 10.14.2.10-1 describes the information flow of the functional revoke notification from the MC service server to the IWF.
Information element Status Description
MC service IDMThe identity of the requesting MC service user.
Functional aliasMThe functional alias which is being revoked.
Up

10.14.3  IWF Functional alias management procedures |R17|  p. 173

10.14.3.1  General  p. 173

The following subclauses describe the relevant functional alias management procedures between the MC system and the IWF to enable role based addressing of users homed in the IWF.

10.14.3.2  User homed in the IWF retrieves active functional alias(es) for a certain MC service user  p. 173

An user homed in the IWF can request the active functional alias(es) for a certain MC service user.
Figure 10.14.3.2-1 below illustrates the active functional alias list query for a certain MC service user.
Copy of original 3GPP image for 3GPP TS 23.283, Fig. 10.14.3.2-1: IWF active functional alias list query
Figure 10.14.3.2-1: IWF active functional alias list query
(⇒ copy of original 3GPP image)
Up
Step 1.
The user homed in the IWF requests a list of active functional aliases for a certain MC service ID from the MC service server by sending an IWF functional alias information query request encompassing the MC service ID or the functional alias of the queried user.
Step 2.
The MC service server checks whether the querying user homed in the IWF is authorized to perform the query. If authorized, then the MC service server retrieves the requested functional alias information based on the corresponding MC service ID or the MC service IDs based on the functional alias.
Step 3.
The MC service server sends an IWF functional alias information query response including the active functional alias or MC service ID information to the user homed in the IWF.
Up

10.14.3.3  User homed in the IWF activates functional alias(es) within an MC system  p. 173

The procedure for the user homed in the IWF activates functional alias(es) within an MC system is illustrated in Figure 10.14.3.3-1.
Pre-conditions:
  1. The IWF has already been provisioned (statically or dynamically) with the functional alias(es) information that the user homed in the IWF is allowed to activate.
  2. MC service server has retrieved the user subscription and functional alias policy e.g. which user(s) are authorized to activate to what functional alias, priority, and other configuration data.
Copy of original 3GPP image for 3GPP TS 23.283, Fig. 10.14.3.3-1: IWF functional alias activation procedure within an MC system
Figure 10.14.3.3-1: IWF functional alias activation procedure within an MC system
(⇒ copy of original 3GPP image)
Up
Step 1.
The user homed in the IWF 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 homed in the IWF 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 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 user homed in the IWF and inform all other user(s) with sharing the same functional alias(es) (step 5). If the limit of number of simultaneous users is reached or the functional alias is not allowed to be shared, the request is rejected, and the IWF is notified (step 4).
If the functional alias(es) is (are) already used by another user(s), an authorized user homed in the IWF gets an offer to take over the functional alias from the user currently using the functional alias(es).
Step 4.
MC service server sends an IWF functional alias(es) activation response to the user homed in the IWF.
Step 5.
The MC service server informs all other MC service user(s) and/or IWF sharing the same functional alias(es).
Up

10.14.3.4  User homed in the IWF de-activates functional alias(es) within an MC system  p. 174

The procedure for the user homed in the IWF de-activates functional alias(es) within an MC system is illustrated in Figure 10.14.3.4-1.
When a user homed in the IWF does not want to use a functional alias(es) anymore, then the user homed in the IWF 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 user homed in the IWF has activated.
Copy of original 3GPP image for 3GPP TS 23.283, Fig. 10.14.3.4-1: IWF functional alias de-activation procedure within an MC system
Figure 10.14.3.4-1: IWF functional alias de-activation procedure within an MC system
(⇒ copy of original 3GPP image)
Up
Step 1.
The user homed in the IWF 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 subscription and stored functional alias policy, the MC service server checks if the user homed in the IWF is authorized to de-activate from the requested functional alias(es) and if the user homed in the IWF has activated to the requested functional alias(es).
Step 3.
If the user homed in the IWF is authorized to de-activate from the requested functional alias(es) then the MC service server updates the functional alias activation status of the user homed in the IWF.
Step 4.
MC service server provides to the user homed in the IWF the functional alias de-activation response.
Step 5.
The MC service server informs all other MC service user(s) and/or users homed in the IWF sharing the same functional alias(es).
Up

10.14.3.5  User homed in the IWF takes over functional alias(es) within an MC system  p. 175

The procedure for the user homed to IWF takes over functional alias(es) within an MC system is illustrated in Figure 10.14.3.5-1.
During functional alias(es) activation, if the functional alias(es) is (are) already used by another MC service user(s), an authorized user homed in the IWF can 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.
  2. As result of the functional alias(es) activation procedure, the user homed in the IWF is aware which functional alias(es) are already used but can be taken over.
  3. The user homed in the IWF decides to take over a functional alias.
Copy of original 3GPP image for 3GPP TS 23.283, Fig. 10.14.3.5-1: IWF functional alias taking over procedure within an MC system
Figure 10.14.3.5-1: IWF functional alias taking over procedure within an MC system
(⇒ copy of original 3GPP image)
Up
Step 1.
The user homed in the IWF requests the MC service server to take over a functional alias by sending an IWF 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 homed in the IWF 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 1 that the functional alias has been revoked and is not any longer active for the user of MC service client 1.
Step 4.
The MC service server stores the functional alias status of the requested functional alias.
Step 5.
MC service server sends an IWF functional alias take over response to the user homed in the IWF.
Step 6.
The MC service server informs all other MC service user(s) sharing the same functional alias, of the take over by sending a functional alias status notification.
Step 7.
The MC service server informs all user(s) homed in the IWF sharing the same functional alias of the take over by sending an IWF functional alias status notification.
Up

Up   Top   ToC