10.14 IWF functional alias management
23.2833GPPMission Critical Communication Interworking with Land Mobile Radio SystemsRelease 18TS
10.14.1 General
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.
Editor’s Note: The corresponding service profiles in the MC system for LMR user homed to IWF are FFS.
Editor’s Note: How the MC service system authorizes the actions of users homed in the IWF is FFS.
The functional alias feature is not a requirement in 3GPP TS 22.179 [3] and is therefore an optional feature for systems that support 3GPP TS 22.179 [3].
10.14.2 IWF information flows for functional alias management
10.14.2.1 IWF functional alias information query request
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.
Table 10.14.2.1-1: IWF functional alias information query request
|
Information element |
Status |
Description |
|
MC service ID |
M |
The identity of the requesting MC service user. |
|
MC service ID |
O |
The identity of the MC service user to be queried. |
|
Functional alias |
O |
The functional alias to be queried. |
10.14.2.2 IWF functional alias information query response
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.
Table 10.14.2.2-1: IWF functional alias information query response.
|
Information element |
Status |
Description |
|
MC service ID |
M |
The identity of the MC service user that performed the query. |
|
MC service ID |
O |
The identity of the MC service user that was queried. |
|
Functional alias |
O |
The functional alias that was queried. |
|
Query result |
M |
The 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. |
10.14.2.3 IWF functional alias activation request
Table 10.14.2.3-1 describes the information flow of the functional alias activation request from the IWF to the MC service server.
Table 10.14.2.3-1: IWF functional alias activation request
|
Information element |
Status |
Description |
|
MC service ID |
M |
The identity of the requesting MC service user. |
|
Functional alias list |
M |
A list of one or more functional aliases which the originator intends to activate. |
10.14.2.4 IWF functional alias activation response
Table 10.14.2.4-1 describes the information flow of the functional alias activation response from the MC service server to the IWF.
Table 10.14.2.4-1: IWF functional alias activation response
|
Information element |
Status |
Description |
|
MC service ID |
M |
The identity of the MC service user that originated the functional alias activation request. |
|
Functional alias list |
M |
A list of one or more functional aliases which the originating party intended to activate. |
|
Activation status per functional alias |
M |
Indicates the activation result for each functional alias in the list (activated, rejected, can be taken over). |
10.14.2.5 IWF functional alias de-activation request
Table 10.14.2.5-1 describes the information flow functional alias de-activation request from the IWF to the MC service server.
Table 10.14.2.5-1: IWF functional alias de-activation request
|
Information element |
Status |
Description |
|
MC service ID |
M |
The identity of the requesting MC service user. |
|
Functional alias list |
M |
A list of one or more functional aliases which the requesting MC service user intends to de-activate. |
10.14.2.6 IWF functional alias de-activation response
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.
Table 10.14.2.6-1: IWF functional alias de-activation response
|
Information element |
Status |
Description |
|
MC service ID |
M |
The identity of the MC service user that originated the functional alias de-activation request. |
|
Functional alias list |
M |
A list of one or more functional aliases which the originating party intends to de-activate. |
|
De-activation status per functional alias |
M |
Indicates the de-activation result for every functional alias in the list. |
10.14.2.7 IWF functional alias status notification
Table 10.14.2.7-1 describes the information flow of the functional alias notification from the MC service server to the IWF.
Table 10.14.2.7-1: IWF functional alias status notification
|
Information element |
Status |
Description |
|
MC service ID |
M |
The identity of the MC service user that originated the functional alias activation, de-activation or take over request. |
|
Functional alias list |
M |
A list of one or more functional aliases. |
|
Operational status |
M |
Activation, de-activation or take over status per functional alias. |
10.14.2.8 IWF Functional alias take over request
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.
Table 10.14.2.8-1: IWF functional alias take over request
|
Information element |
Status |
Description |
|
MC service ID |
M |
The identity of the requesting MC service user. |
|
Functional alias |
M |
A functional alias which the requester intends to take over. |
10.14.2.9 IWF Functional alias take over response
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.
Table 10.14.2.9-1: IWF functional alias take over response
|
Information element |
Status |
Description |
|
MC service ID |
M |
The identity of the requesting MC service user. |
|
Functional alias |
M |
A functional alias which the requester intends to take over. |
|
Activation status per functional alias |
M |
Indicates the take over request result (accepted, rejected). |
10.14.2.10 IWF Functional alias revoke notification
Table 10.14.2.10-1 describes the information flow of the functional revoke notification from the MC service server to the IWF.
Table 10.14.2.10-1: IWF functional alias revoke notification
|
Information element |
Status |
Description |
|
MC service ID |
M |
The identity of the requesting MC service user. |
|
Functional alias |
M |
The functional alias which is being revoked. |
10.14.3 IWF Functional alias management procedures
10.14.3.1 General
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
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.
Figure 10.14.3.2-1: IWF active functional alias list query
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.
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.
Editor’s note: How the MC service server checks the authorization of the IWF to perform functional alias related actions is FFS.
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.
10.14.3.3 User homed in the IWF activates functional alias(es) within an MC system
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.
Figure 10.14.3.3-1: IWF functional alias activation procedure within an MC system
1. The user homed in the IWF requests the MC service server to activate a functional alias or a set of functional aliases.
2. The MC service server checks if there are any conflicts with active functional alias(es).
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).
Editor’s note: How the MC service server checks the authorization of the IWF to perform functional alias related actions is FFS.
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).
Editor’s note: How the MC service server checks whether a user homed in the IWF is an "authorized" user is FFS.
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).
4. MC service server sends an IWF functional alias(es) activation response to the user homed in the IWF.
5. The MC service server informs all other MC service user(s) and/or IWF sharing the same functional alias(es).
10.14.3.4 User homed in the IWF de-activates functional alias(es) within an MC system
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.
Figure 10.14.3.4-1: IWF functional alias de-activation procedure within an MC system
1. The user homed in the IWF requests the MC service server to de-activate a functional alias or a set of functional aliases.
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).
Editor’s note: How the MC service server checks the authorization of the IWF to perform functional alias related actions is FFS.
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.
4. MC service server provides to the user homed in the IWF the functional alias de-activation response.
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).
10.14.3.5 User homed in the IWF takes over functional alias(es) within an MC system
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.
Figure 10.14.3.5-1: IWF functional alias taking over procedure within an MC system
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.
2. The MC service server checks if there are any conflicts taking over the functional alias.
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.
Editor’s note: How the MC service server checks the authorization of the IWF to perform functional alias related actions is FFS.
4. The MC service server stores the functional alias status of the requested functional alias.
5. MC service server sends an IWF functional alias take over response to the user homed in the IWF.
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.
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.