hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
206be7a57129464f73be1aa9d853095b | 23.283 | 10.6.2.6 Emergency private call | An emergency private call to an LMR user will have emergency priority for the portion of the call transported in the MCPTT system and the LTE EPS but will not receive priority on the LMR system in LMR systems that do not support emergency treatment for private calls. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.6.2.7 LMR systems that do not track group emergencies | The MCPTT system tracks the emergency state of every group. In interworked LMR systems that do not track the emergency state of groups, only a UE in emergency state will be given emergency priority on the LMR system when talking. For any user talking on an emergency group, the portion of the call transported by the MCPTT system will receive emergency priority. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.6.3 Imminent peril calls | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.6.3.1 General | This subclause addresses various aspects of imminent peril call interworking.
LMR systems do not support imminent peril. Imminent peril calls can be propagated into the LMR system by the IWF as normal group calls or emergency group calls. The decision of the LMR group call type is outside the scope of the present document.
Where the group is defined in the MCPTT system and where the IWF has affiliated to an MCPTT group with a single affiliation on behalf of all LMR group members, only a single IWF imminent peril group call request / IWF imminent peril cancel request message is sent to the IWF at the commencement / cancel of an imminent peril group call. Where the group is defined in the MCPTT system and where the IWF has passed through individual affiliations for each group member in the LMR system, the MCPTT system shall send individual IWF imminent peril group call request / IWF imminent peril cancel request messages to the IWF for all affiliated group members in the LMR system in accordance with primary and partner MCPTT system behaviour. In both cases, the distribution of the messages to group members in the LMR system is out of scope of the present document.
Where the group is defined in the LMR system, the IWF shall send individual IWF imminent peril group call request / IWF imminent peril cancel request messages to the MCPTT server for all affiliated MCPTT group members in accordance with primary and partner MCPTT system behaviour. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.6.3.2 Imminent peril group call initiated by an MCPTT user on an interworking group | Figure 10.6.3.2‑1 shows the procedure for an imminent peril group call initiated by a user in the MCPTT system. The figure is based upon the figure for imminent peril group call in 3GPP TS 23.379 [7], subclause 10.6.2.6.2.1.
NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server.
NOTE 2: The imminent peril interworking group call procedures reuse the information flows defined in 3GPP TS 23.379 [7].
Pre-conditions:
1. The initiating MCPTT client 1 has been provisioned with an MCPTT group that has been designated in the provisioning to be used for imminent peril communications
2. The MCPTT group is an interworking group defined in the MCPTT system.
3. MCPTT client 2 is affiliated to the MCPTT group.
4. The IWF is connected to, and is authorized to, interwork with the MCPTT system.
5. At least one LMR user has affiliated to the MCPTT group.
6. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
NOTE 3: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.6.3.2-1: Imminent peril group call initiated by a MCPTT user to an interworking group defined in the MCPTT system
1. An MCPTT user initiates an imminent peril group call.
2. The MCPTT client sends an MCPTT imminent peril group call request to the MCPTT server. The request contains an indication of the in-progress imminent peril. The request may also contain an indication of an implicit floor request and may also contain the location of the calling party.
3. The MCPTT server implicitly affiliates MCPTT client 1 to the imminent peril group if the client is not already affiliated.
4. The MCPTT server checks whether the MCPTT user of MCPTT client 1 is authorized for initiation of imminent peril group calls on the indicated interworking group defined in the MCPTT system. If authorized, it resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status. The MCPTT server also checks the privacy policy (authorisation to provide location information to other MCPTT users on a call when talking, as defined in 3GPP TS 23.379 [7] Annex A.3) of the requesting MCPTT user to decide if the user's location information may be provided to other MCPTT users on the call and the IWF.
5. The MCPTT server configures the priority of the underlying bearers for all participants in the MCPTT group.
NOTE 4: Successive calls during the in-progress imminent peril state will all receive the adjusted bearer priority.
6. The MCPTT server records the imminent peril state of the group. The MCPTT server also records the identity of the MCPTT user that initiated the imminent peril group call until the in-progress imminent peril state is cancelled. Once an imminent peril group call has been initiated, the MCPTT group is considered to be in an in-progress imminent peril state until that state is cancelled.
7. The MCPTT server sends the IWF imminent peril group call request(s) to the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF imminent peril group call request message is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF imminent peril group call request is sent to the IWF for each affiliated LMR user.
8. The IWF responds with the IWF imminent peril group call response(s) to MCPTT server to inform of the successful MCPTT imminent peril call establishment.
NOTE 5: The IWF can reject the request if it does not support imminent peril group calls. IWF actions for priority are out of scope of the present document.
NOTE 6: How the LMR group members are called within the LMR system is out of scope of the present document.
9. The MCPTT server sends the imminent peril group call request towards the MCPTT clients of each of those affiliated MCPTT group members. The request contains an indication of the in-progress imminent peril. MCPTT users are notified of the incoming imminent peril call. The MCPTT clients acknowledge the imminent peril call request as specified in 3GPP TS 23.379 [7].
10. The MCPTT server sends the MCPTT imminent peril group call response to the MCPTT user 1 to inform the successful imminent peril call establishment.
NOTE 7: Step 10 can occur at any time following step 5, and prior to step 11 depending on the conditions to proceed with the imminent peril call.
11. The LMR users via the IWF and the affiliated MCPTT clients have successfully established the media plane for communication. The MCPTT system, where the interworking group is defined, is the controlling system of the group call. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.6.3.3 Group call initiated by a user in the LMR system on an interworking group in imminent peril state | Figure 10.6.3.3‑1 shows the procedure for a group call initiated by an LMR user (represented by the IWF) on an interworking group where the group is currently in imminent peril state within the MCPTT system.
NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server.
NOTE 2: The imminent peril interworking group call procedures reuse the information flows defined in 3GPP TS 23.379 [7].
Pre-conditions:
1. The MCPTT group is previously defined on the group management server with MCPTT client 1, MCPTT client 2, and LMR users (represented by the IWF) affiliated to that MCPTT group.
2. The IWF is connected to, and is authorized to interwork with, the MCPTT system.
3. The interworking group information is available at the IWF.
4. The interworking group is currently in imminent peril state within the MCPTT system.
5. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
6. LMR user initiates a group call.
NOTE 3: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.6.3.3-1: Group call initiated by a user in the LMR system on an interworking group in imminent peril state
1. The IWF does not track the imminent peril state of the group and sends an IWF group call request including an MCPTT group ID to the MCPTT server for call establishment. If floor control is requested by the calling LMR user, an indication of implicit floor request is included and the location information of the requestor if required.
2. The MCPTT server determines that the MCPTT group is currently in imminent peril state.
3. The MCPTT server converts the request and sends an MCPTT imminent peril group call request to all of the affiliated MCPTT clients.
3a. If the group has other affiliated LMR users than the calling party and the MCPTT server has received individual affiliations from those LMR users, an individual IWF imminent peril group call request is sent to the IWF for each affiliated LMR user.
4. The receiving MCPTT clients send the MCPTT imminent peril group call response to the MCPTT server to acknowledge the MCPTT imminent peril group call request. For a multicast call, these acknowledgements are not sent.
4a. The IWF returns IWF imminent peril group call response(s) to the MCPTT server.
5. The MCPTT server sends the IWF imminent peril group call response message to the IWF.
6. The LMR users (via the IWF) and the affiliated MCPTT clients have successfully established the media plane for communication. The MCPTT system where the interworking group is defined is the controlling system of the group call.
The IWF, MCPTT client 1, and MCPTT client 2 continue with the MCPTT group call, which receives adjusted bearer priority within the MCPTT system due to the MCPTT group being in imminent peril state.
NOTE 4: IWF actions for priority are out of scope of the present document. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.6.3.4 In-progress imminent peril state cancel on an interworking group | This procedure describes the case where an authorized MCPTT user cancels an interworking group's in-progress imminent peril state.
Figure 10.6.3.4‑1 shows the procedures for the MCPTT client cancelling an interworking group's in-progress imminent peril state.
NOTE 1: The end of an imminent peril call does not cancel the MCPTT group's in-progress imminent peril state. It is explicitly cancelled by an authorized user.
NOTE 2: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server.
NOTE 3: The in-progress imminent peril interworking group state cancel procedures reuse the information flows defined 3GPP TS 23.379 [7].
Pre-conditions:
1. The MCPTT group is previously defined on the group management server with MCPTT client 1, MCPTT client 2, and LMR users (represented by the IWF) affiliated to that MCPTT group.
2. The IWF is connected to, and is authorized to interwork with, the MCPTT system.
3. The interworking group information is available at the IWF.
4. The interworking group is currently in in-progress imminent peril state within the MCPTT system and has prioritized bearer support.
5. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
NOTE 4: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
6. MCPTT client 1 previously initiated the imminent peril group call.
Figure 10.6.3.4-1: In-progress imminent peril group state cancel on an interworking group
1. The user at the MCPTT client 1 initiates an in-progress imminent peril state cancel.
2. MCPTT client 1 sends an MCPTT in-progress imminent peril group state cancel request to the MCPTT server.
3. The MCPTT server checks whether the MCPTT user 1 at MCPTT client 1 is authorized to cancel the in-progress imminent peril group state.
4. The MCPTT server cancels/resets the in-progress imminent peril group state.
5. The MCPTT server adjusts the priority of the underlying bearer; priority treatment is no longer required.
6. The MCPTT server sends an IWF in-progress imminent peril group state cancel request(s) to the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF in-progress imminent peril group state cancel request is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF in-progress imminent peril group state cancel request is sent (to the IWF) for each affiliated LMR user.
7. The IWF sends the IWF in-progress imminent peril group state cancel response(s) to the MCPTT server.
NOTE 5: The IWF responds even if it does not support imminent peril group calls. IWF actions for priority are out of scope of the present document.
8. The MCPTT server sends an MCPTT in-progress imminent peril group state cancel request to the MCPTT group members.
NOTE 6: Steps 6 and 8 can occur in any order following step 5.
9. MCPTT group members are notified of the in-progress imminent peril group state cancel.
10. MCPTT client 2 sends the MCPTT in-progress imminent peril group state cancel response to the MCPTT server to acknowledge the in-progress MCPTT in-progress imminent peril group state cancel request. For a multicast scenario, this acknowledgement is not sent.
11. The MCPTT server sends the MCPTT in-progress imminent peril group state cancel response to the MCPTT client 1 to confirm the MCPTT in-progress imminent peril group state cancel request.
NOTE 7: Step 11 can occur at any time following step 5. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.6.4 Emergency alerts | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.6.4.1 Emergency alert initiated by LMR user | In this procedure, an LMR user is initiating an emergency alert via the IWF. Figure 10.6.4.1-1 shows the procedure for an emergency alert initiated by a user in the LMR system. This subclause is based upon subclause for MCPTT emergency alerts in 3GPP TS 23.379 [7], subclause 10.6.2.6.3.1.
Pre-conditions:
1. The MC service group is previously defined on the group management server with MC service client 1 and MC service client 2 affiliated to that MC service group.
2. The IWF is connected to and is authorized to interwork with the MC system.
3. The MC service group information is available at the IWF, including information that the MC service group is an interworking group (defined in the LMR system or MC the system).
4. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF.
5. The IWF may or may not have carried out an explicit affiliation procedure with the MC service group.
6. An emergency alert is requested on the LMR system.
NOTE 1: For all signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs identity conversion and protocol translation.
Figure 10.6.4.1-1 MC service emergency alert initiated by LMR user
1. The LMR user initiates an emergency alert.
NOTE 2: How the IWF determines the emergency condition from the LMR system is out of scope of the present document.
2. The IWF sends an IWF emergency alert request to the designated MC service server. If the location of the LMR user is not available to the IWF, the IWF emergency alert request shall contain an indication that location is not available.
3. MC service server checks whether the MC service user ID that represents the LMR user is authorized for initiation of MC service emergency alerts for the indicated MC service group. The MC service server determines the affiliation status of the group members.
4. The MC service server sends an IWF emergency alert response to the IWF to confirm the IWF emergency alert request.
NOTE 3: Sending the IWF emergency alert request without making a request to also start an emergency call does not put the group into an ongoing emergency condition.
5. The MC service server sends an MC service emergency alert request towards the MC service clients of each of those affiliated MC service group members. The MC service emergency alert request message shall contain the following information: Location, MC service ID and MC service group ID (i.e., MC service user's selected MC service group or dedicated MC service emergency group, as per MC service group configuration) and the MC service user's mission critical organization name.
6. MC service users are notified of the MC service emergency.
7. The receiving MC service clients send an MC service emergency alert response to the MC service server to acknowledge the MC service emergency alert request.
8. If the group is an interworking group defined in the MC system, the MC service server implicitly affiliates the individual MC service ID of the LMR user to the emergency group if not already affiliated. If the IWF is configured to affiliate on behalf of all of its group members in a single affiliation step, the MC service server affiliates the IWF ID instead of an individual MC service ID.
NOTE 4: Step 8 can be performed any time after step 3 but at the latest immediately after step 7.
NOTE 5: MC service group calls made to this MC service group will be established as emergency calls if this MC service group has an ongoing emergency condition.
NOTE 6: Sending the emergency alert does not put the other UEs in the group into an emergency state. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.6.4.2 Emergency alert initiated by MC service user | In this procedure, an MC service user is initiating an emergency alert that is delivered to the LMR system via the IWF. Figure 10.6.4.2-1 shows the procedure for an emergency alert initiated by a user in the MC system. This subclause is based upon subclause for MCPTT emergency alerts in 3GPP TS 23.379 [7], subclause 10.6.2.6.3.1.
Pre-conditions:
1. The MC service group is previously defined on the group management server with MC service client 1 and MC service client 2 affiliated to that MC service group.
2. The IWF is connected to and is authorized to interwork with the MC system.
3. The MC service group information is available at the IWF, including information that the MC service group is an interworking group (defined in the LMR system or the MC system).
4. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF.
NOTE 1: For all signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs identity conversion and protocol translation.
Figure 10.6.4.2-1 MC service emergency alert initiated by MC service user
1. The MC service user 1 initiates an emergency alert.
2. MC service client 1 sends an MC service emergency alert request to the MC service server.
3. The MC service server resolves the group ID, determines the affiliation status of the group members and checks whether the IWF should be informed. In this scenario, the group has affiliated members that are homed on the IWF, thus the IWF shall be involved. MC service server also checks whether the MC service user ID is authorized to initiate MC service emergency alerts for the indicated MC service group.
4. The MC service server sends an MC service emergency alert response to the MC service client 1 to confirm the MC service emergency alert request.
NOTE 2: Sending the emergency alert without making a request to also start an emergency call does not put the group into an ongoing emergency condition.
5. MC service server sends an IWF emergency alert request to the IWF. If the location of the MC service client 1 is not available, the IWF emergency alert request shall contain an indication that location is not available. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF emergency alert request is sent to the IWF. If the IWF has sent individual affiliations for each of its LMR users, the MC service server sends an IWF emergency alert request via the IWF to each affiliated LMR group member.
6. The IWF sends an IWF service emergency alert response to the MC service server to confirm the IWF emergency alert request(s).
7. The MC service server sends an MC service emergency alert request towards the MC service clients of each of those affiliated MC service group members. The MC service emergency alert request message shall contain the following information: Location, MC service ID and MC service group ID (i.e., MC service user's selected MC service group or dedicated MC service emergency group, as per MC service group configuration) and the MC service user's mission critical organization name.
8. MC service users are notified of the MC service emergency.
9. The receiving MC service clients send an MC service emergency alert response to the MC service server to acknowledge the MC service emergency alert.
10. The MC service server implicitly affiliates the MC service client 1 to the emergency group if it is not already affiliated.
NOTE 3: Step 10 can be performed any time after step 3. Steps 5 and 7 can be performed in which ever order.
NOTE 4: MC service group calls made to this MC service group will be established as emergency calls if the MC service group has an ongoing emergency condition.
NOTE 5: Sending an emergency alert does not put the other UEs in the group into an emergency state. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.6.5 Emergency alert cancellation | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.6.5.1 Emergency alert cancellation of an LMR user | In this procedure, an LMR user is cancelling the emergency alert. Figure 10.6.5.1-1 shows the procedure for emergency alert cancellation of a user in the LMR system. This subclause is based upon subclause for MCPTT emergency alert cancel in 3GPP TS 23.379 [7], subclause 10.6.2.6.3.2.
Pre-conditions:
1. The MC service group information is available at the IWF, including information that the MC service group is an interworking group (defined in the LMR system or the MC system).
2. The LMR user had previously successfully initiated an emergency alert via the IWF.
3. The MC service client 1 and MC service client 2 are affiliated to the MC service group.
4. The MC service server may have carried out an explicit or implicit affiliation procedure of the LMR user to the MC service group.
5. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF.
6. The LMR user initiates an emergency alert cancel.
NOTE 1: For all the signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.6.5.1-1 MC service emergency alert cancellation of an LMR user
1. The IWF sends an IWF emergency alert cancel request to the MC service group to which the IWF had previously successfully sent the IWF emergency alert request on behalf of the LMR user.
NOTE 2: The IWF emergency alert cancel request may carry an indication to also request that the in-progress emergency state on the group is to be cancelled.
2. The MC service server sends the IWF emergency alert cancel response to the IWF to confirm the IWF emergency alert cancellation.
3. The MC service server sends an MC service emergency alert cancel request to the MC service clients of the affiliated MC service group members.
4. MC service users are notified of the MC service emergency alert cancellation of the LMR user.
5. The receiving MC service clients send the MC service emergency alert cancel response to the MC service server to acknowledge the MC service emergency alert cancel request. For a multicast call scenario, these acknowledgements are not sent.
NOTE 3: Steps 2 and 3 can be performed in which ever order. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.6.5.2 Emergency alert cancellation of an MC service user | In this procedure, an MC service user is cancelling the emergency alert. Figure 10.6.5.2-1 shows the procedure for emergency alert cancellation from a user in the MC system. This subclause is based upon subclause for MCPTT emergency alerts in 3GPP TS 23.379 [7], subclause 10.6.2.6.3.2.
Pre-conditions:
1. The MC service group information is available at the IWF, including information that the MC service group is an interworking group (defined in the LMR system or the MC system).
2. The MC service client 1 had previously successfully initiated an MC service emergency alert request.
3. The MC service client 1 is still in the emergency state.
4. The MC service client 2 is affiliated to the MC service group.
5. The MC service server may have carried out an explicit or implicit affiliation procedure of the LMR user with the MC service group.
6. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF.
NOTE 1: For all the signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.6.5.2-1 MC service emergency alert cancellation of an MC service user
1. The user at the MC service client 1 initiates an emergency alert cancel.
NOTE 2: The MC service emergency alert cancel request may carry an indication that the in-progress emergency state on the group is to be cancelled.
2. MC service client 1 requests the MC service server to send an MC service emergency alert cancel to the MC service group to which MC service client 1 had previously sent the emergency alert request. The MC service server resolves the group ID, determines the affiliation status of the group members and checks whether the IWF should be informed. In this scenario, the group has affiliated members that are homed on the IWF, thus the IWF shall be involved.
3. The MC service server sends the MC service emergency alert cancel response to the MC service client 1 to confirm the MC service emergency alert cancel request. MC service client 1 resets its emergency state.
4. The MC service server sends an IWF emergency alert cancel request(s) to the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF emergency alert cancel request message is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF emergency alert cancel request message is sent to the IWF for each affiliated LMR user.
5. The IWF sends an IWF emergency alert cancel response(s) to the MC service server to acknowledge the IWF emergency alert cancel request(s).
6. The MC service server sends an MC service emergency alert cancel request towards the MC service clients of the affiliated MC service group members.
7. MC service users are notified of the MC service emergency alert cancellation of MC service client 1.
8. The receiving MC service clients send the MC service emergency alert cancel response to the MC service server to acknowledge the MC service emergency alert cancel request. For a multicast call scenario, these acknowledgements are not sent.
NOTE 3: Steps 3 and 4 can be performed in which ever order. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.7 Codec | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.7.1 Information flows for codec | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.7.1.1 IWF codec reconciliation request | Table 10.7.1.1-1 describes the information flow IWF codec reconciliation request from the IWF to the MCPTT server.
Table 10.7.1.1-1: IWF codec reconciliation request
Information element
Status
Description
MCPTT group ID
M
The MCPTT group ID for which a codec change is requested.
Codec type
M
Type of the requested codec |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.7.1.2 IWF codec reconciliation response | Table 10.7.1.2-1 describes the information flow IWF codec reconciliation response from the MCPTT server to the IWF.
Table 10.7.1.2-1: IWF codec reconciliation response
Information element
Status
Description
MCPTT group ID
M
The MCPTT group ID for which a codec change was requested.
Result
M
Result indicates success or failure of the requested codec change. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.7.2 IWF transcoding | The IWF can be used to transcode voice packets in transit between the LMR and MCPTT systems. In this scenario, the MCPTT system can operate its own vocoder type and the LMR system can operate its own vocoder type. The type of vocoder used on the LMR side is outside the scope of the present document.
When operating in this mode, the IWF converts voice media formats between the two sides. Vocoder negotiation is according to procedures in the present document. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.7.3 Codec negotiation by the LMR system | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.7.3.1 Description | An MCPTT group may be configured to use an LMR speech codec, such that speech can be carried end to end between all group members in both LMR and MCPTT system without transcoding.
An LMR system can support more than one speech codec; for example P25 supports both a full rate and a half rate speech codec. Circumstances within the LMR system might require that the codec in use within a group is changed according to the needs of the LMR system.
Figure 10.7.3.1-1 below illustrates a procedure which allows the LMR system to change the speech codec within an MCPTT group that is connected to the LMR system via the IWF.
Pre-conditions:
1. Group members have affiliated to the MCPTT group in both the LMR system and in the MCPTT system
2. A permitted LMR codec has been negotiated for use by MCPTT group members
3. MCPTT group members support the requested second LMR speech codec
NOTE 1: The exception condition created if the IWF does not support trancoding and the MCPTT client does not support the requested LMR codec is outside the scope of the present document.
4. The LMR system requires a change to an alternative speech codec.
Figure 10.7.3.1-1: Codec reconciliation procedure
1. The IWF sends a codec reconciliation request to the MCPTT server on behalf of the LMR system.
2. The MCPTT server checks that the requested codec is permitted for the MCPTT group.
3. The MCPTT server sends a codec reconciliation request to all of the affilliated MCPTT client(s) to negotiate the use of the speech codec requested by the LMR system.
4. The MCPTT client replies with a codec reconciliation response to the MCPTT server, indicating acceptance of the new speech codec.
5. The MCPTT server sends a codec reconciliation response to the IWF.
6. Further transmissions in the MCPTT group use the new codec in the media plane.
NOTE 2: The time at which the new codec is first used by a transmitting party is outside the scope of the present document. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8 MCData short data service | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.1 General | The present document specifies short data service (SDS) interworking between LMR users and MCData clients using one-to-one standalone SDS messages and group standalone SDS messages. The IWF behaves as a peer MCData server to other MCData servers.
When an LMR user attempts to send an LMR message to the MCData service, the IWF converts the LMR message into a request to send an MCData SDS. The method by which the IWF converts the LMR message into a request to send an MCData SDS is outside the scope of the present document.
When the IWF receives a request to send an MCData SDS to an LMR user or a group of LMR users, the IWF converts the request into one or more LMR messages. The method by which the IWF converts the MCData SDS request into an LMR messages is outside the scope of the present document. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.2 Information flows for the short data service | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.2.1 General | The following subclauses define information flows for MCData SDS on the IWF-2 interface. MCData SDS related information flows on reference points other than IWF-2 are defined in 3GPP TS 23.282 [6], subclause 7.4.2.1. In each case, the LMR users behind the IWF are represented by MCData IDs or a MCData group ID as appropriate and so the MCData server shall be capable of routing messages towards identities located behind the IWF. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.2.2 IWF MCData standalone data request | Table 10.8.2.2-1 describes the information flow for the MCData standalone data request (in 3GPP TS 23.282 [6] subclauses 7.4.2.2.2 and 7.4.2.3.2) sent from the MCData server to the IWF and from the IWF to a MCData server.
Table 10.8.2.2-1: IWF MCData standalone data request
Information element
Status
Description
MCData ID
M
The identity of the MCData user sending data
Functional alias
O
The associated functional alias of the MCData user sending data.
MCData ID
M
The identity of the MCData user towards which the data is sent
Conversation Identifier
(see NOTE 1)
M
Identifies the conversation
Transaction Identifier
(see NOTE 1)
M
Identifies the MCData transaction
Reply Identifier
O
Identifies the original MCData transaction to which the current transaction is a reply to
Disposition Type
O
Indicates the disposition type expected from the receiver (i.e., delivered or read or both)
Payload Destination Type
M
Indicates whether the payload is for application consumption or MCData client consumption
Application identifier
(see NOTE 2)
O
Identifies the application for which the payload is intended (e.g. text string, port address, URI)
Payload
M
SDS content
NOTE 1: A reserved value of the Information Element shall be defined which indicates that the sender does not support this Information Element.
NOTE 2: The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.2.3 IWF MCData data disposition notification | Table 10.8.2.3-1 describes the information flow for the MCData data disposition notification sent from the IWF to the MCData server and from the MCData server to the IWF.
Table 10.8.2.3-1: IWF MCData data disposition notification
Information element
Status
Description
MCData ID
M
The identity of the MCData user towards which the notification is sent
MCData ID
M
The identity of the MCData user sending notification
Conversation Identifier
(see NOTE)
M
Identifies the conversation
Disposition association
M
Identity of the original MCData transaction
Disposition
M
Disposition which is delivered, read, delivered and read, or disposition prevented by system
NOTE: A reserved value of the Information Element shall be defined which indicates that the sender does not support this Information Element. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.2.4 IWF MCData group standalone data request (IWF – MCData server) | Table 10.8.2.4-1 describes the information flow for the MCData group standalone data request (in 3GPP TS 23.282 [6] subclause 7.4.2.5.2) sent from the IWF to the MCData server when the IWF is acting as the initiating MCData client.
Table 10.8.2.4-1: IWF MCData group standalone data request (IWF – MCData server)
Information element
Status
Description
MCData ID
M
The identity of the MCData user sending data
MCData group ID
M
The MCData group ID to which the data is to be sent
Conversation Identifier
(see NOTE 1)
M
Identifies the conversation
Transaction Identifier
(see NOTE 1)
M
Identifies the MCData transaction
Reply Identifier
O
Identifies the original MCData transaction to which the current transaction is a reply to
Disposition Type
O
Indicates the disposition type expected from the receiver (i.e., delivered or read or both)
Payload Destination Type
M
Indicates whether the payload is for application consumption or MCData client consumption
Application identifier
(see NOTE 2)
O
Identifies the application for which the payload is intended (e.g. text string, port address, URI)
Payload
M
SDS content
NOTE 1: A reserved value of the Information Element shall be defined which indicates that the sender does not support this Information Element.
NOTE 2: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.2.5 IWF MCData group standalone data request (MCData server - IWF) | Table 10.8.2.5‑1 describes the information flow for the MCData group standalone data request (in 3GPP TS 23.282 [6] subclause 7.4.2.5.2) sent from the MCData server to the IWF when the IWF is acting as proxy for MCData clients.
Table 10.8.2.5‑1: IWF MCData group standalone data request (MCData server – IWF)
Information element
Status
Description
MCData ID
M
The identity of the MCData user sending data
MCData group ID
M
The MCData group ID to which the data is to be sent
MCData ID
M
The identity of the MCData user towards which the data is sent
Conversation Identifier
M
Identifies the conversation
Transaction Identifier
M
Identifies the MCData transaction
Reply Identifier
O
Identifies the original MCData transaction to which the current transaction is a reply to
Disposition Type
O
Indicates the disposition type expected from the receiver (i.e., delivered or read or both)
Payload Destination Type
M
Indicates whether the payload is for application consumption or MCData client consumption
Application identifier
(see NOTE)
O
Identifies the application for which the payload is intended (e.g. text string, port address, URI)
Payload
M
SDS content
NOTE: The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.2.6 IWF MCData data disposition notification(s) (MCData server to IWF) | Table 10.8.2.6‑1 describes the information flow for the MCData data disposition notification(s) sent from the MCData server to the IWF when the IWF is acting as proxy for MCData client(s).
Table 10.8.2.6-1: IWF MCData data disposition notification(s) (MCData server – IWF)
Information element
Status
Description
MCData ID
M
The identity of the MCData user towards which the notification is sent
MCData ID
M
The identity of the MCData user sending notification
Conversation Identifier
M
Identifies the conversation
Disposition association
M
Identity of the original MCData transaction
Disposition
M
Disposition which is delivered, read, delivered and read, or disposition prevented by system |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.2.7 IWF MCData group standalone data request (IWF – MCData server) | Table 10.8.2.7‑1 describes the information flow for the MCData group standalone data request (in 3GPP TS 23.282 [6] subclause 7.4.2.6.2) sent from the IWF representing the MCData client to the MCData server.
Table 10.8.2.7‑1: IWF MCData group standalone data request (IWF – MCData server)
Information element
Status
Description
MCData ID
M
The identity of the MCData user sending data
MCData group ID
M
The MCData group ID to which the data is to be sent
Conversation Identifier
(see NOTE 1)
M
Identifies the conversation
Transaction Identifier
(see NOTE 1)
M
Identifies the MCData transaction
Reply Identifier
O
Identifies the original MCData transaction to which the current transaction is a reply to
Transaction type
M
Standalone transaction
Disposition Type
O
Indicates the disposition type expected from the receiver (i.e., delivered or read or both)
Payload Destination Type
M
Indicates whether the SDS payload is for application consumption or MCData user consumption
Application identifier (see NOTE 2)
O
Identifies the application for which the payload is intended (e.g. text string, port address, URI)
SDP offer
M
Media parameters offered
NOTE 1: A reserved value of the Information Element shall be defined which indicates that the sender does not support this Information Element.
NOTE 2: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.2.8 IWF MCData group standalone data request (MCData server – IWF) | Table 10.8.2.8-1 describes the information flow for the MCData group standalone data request (in 3GPP TS 23.282 [6] subclause 7.4.2.6.2) sent from the MCData server to the IWF acting as proxy for MCData client(s).
Table 10.8.2.8-1: IWF MCData group standalone data request (MCData server – IWF)
Information element
Status
Description
MCData ID
M
The identity of the MCData user sending data
MCData group ID
M
The MCData group ID to which the data is to be sent
MCData ID
M
The identity of the MCData user towards which the data is sent
Conversation Identifier
M
Identifies the conversation
Transaction Identifier
M
Identifies the MCData transaction
Reply Identifier
O
Identifies the original MCData transaction to which the current transaction is a reply to
Transaction type
M
Standalone transaction
Disposition Type
O
Indicates the disposition type expected from the receiver (i.e., delivered or read or both)
Payload Destination Type
M
Indicates whether the SDS payload is for application consumption or MCData user consumption
Application identifier
(see NOTE)
O
Identifies the application for which the payload is intended (e.g. text string, port address, URI)
SDP offer
M
Media parameters offered
NOTE: The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.2.9 IWF MCData group standalone data response | Table 10.8.2.9-1 describes the information flow for the MCData group standalone data response (in 3GPP TS 23.282 [6] subclause 7.4.2.6.2) sent from the IWF to the MCData server and from the MCData server to the IWF acting as proxy for other MCData clients.
Table 10.8.2.9-1: IWF MCData group standalone data response
Information element
Status
Description
MCData ID
M
The identity of the MCData user receiving data
MCData group ID
M
The MCData group ID to which the data is to be sent
MCData ID
M
The identity of the MCData user sent data
Conversation Identifier (see NOTE)
M
Identifies the conversation
SDP answer
M
Media parameters selected
NOTE: A reserved value of the Information Element shall be defined which indicates that the sender does not support this Information Element. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.3 Behaviour at the MCData Client | The MCData client interfaces with the MCData server as specified in 3GPP TS 23.282 [6]. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.4 Behaviour at the IWF | The IWF interfaces with the MCData server via the reference points defined in subclause 7.4 of the present document. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.5 Behaviour at the MCData server | The MCData server behaves as specified in 3GPP TS 23.282 [6], with the addition that the MCData server shall route SDS messages addressed to MCData IDs and MCData group IDs that lie behind IWFs to the appropriate IWFs. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.6 MCData user one-to-one SDS request to an LMR user | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.6.1 Signalling control plane | The procedure for an MCData user requesting to send a signalling control plane SDS to a single LMR user is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.2 for the one‑to‑one standalone short data service using the signalling control plane, with the exception that MCData client 2 is located behind the IWF. The SDS is addressed to the MCData ID that has been allocated to the LMR user. The IWF behaves as a peer MCData server. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.6.2 Media plane | The procedure for an MCData user requesting to send a media plane SDS to a single LMR user is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.3 for the one‑to‑one standalone short data service using the media plane, with the exception that MCData client 2 is located behind the IWF. The SDS is addressed to the MCData ID that has been allocated to the LMR user. The IWF behaves as a peer MCData server. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.7 LMR user one-to-one SDS request to an MCData user | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.7.1 Signalling control plane | The procedure for an IWF requesting, on behalf of an LMR user, to send a signalling control plane SDS to a single MCData user is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.2 for the one‑to‑one standalone short data service using the signalling control plane, with the exception that MCData client 1 is located behind the IWF. The source address of the SDS is the MCData ID that has been allocated to the LMR user. The IWF behaves as a peer MCData server. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.7.2 Media plane | The procedure for an IWF requesting, on behalf of an LMR user, to send a media plane SDS to a single MCData user is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.3 for the one‑to‑one standalone short data service using the media plane, with the exception that MCData client 1 is located behind the IWF. The source address of the SDS is the MCData ID that has been allocated to the LMR user. The IWF behaves as a peer MCData server. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.8 MCData user group SDS request to an MCData group including LMR users | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.8.1 Signalling control plane | The procedure for an MCData user requesting to send a signalling control plane SDS to an MCData group that includes one or more LMR users is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.5 for the group standalone short data service using the signalling control plane. In the case of implementation involving an IWF the difference is that one or more of the MCData clients 2 to n are located behind IWFs that have affiliated to the MCData group (see subclause 10.1.2 of the present document). The SDS is addressed to the MCData group ID. The IWF behaves as a peer MCData server. The IWF can also respond on behalf on a MCData client located behind the IWF to a disposition request with a disposition of 'disposition prevented by system' for forwarding to the originating MCData client. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.8.2 Media plane | The procedure for an MCData user requesting to send a media plane SDS to an MCData group that includes one or more LMR users is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.6 for the group standalone short data service using the media plane. In the case of implementation involving an IWF the difference is that one or more of the MCData clients 2 to n can be located behind IWFs that have affilated to the MCData group (see subclause 10.1.2 of the present document). The SDS is addressed to the MCData group ID. The IWF behaves as a peer MCData server. The IWF can also respond on behalf on a MCData client located behind the IWF to a disposition request with a disposition of 'disposition prevented by system' for forwarding to the originating MCData client. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.9 LMR user group SDS request to an MCData group | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.9.1 Signalling control plane | The procedure for an IWF requesting, on behalf of an LMR user, to send a signalling control plane SDS to an MCData group is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.5 for the group standalone short data service using the signalling control plane, with the exception that MCData client 1 is located behind an IWF and one or more of the MCData clients 2 to n can be behind IWFs that have affiliated to the MCData group (see subclause 10.1.2 of the present document). The SDS is addressed to the MCData group ID. The IWF behaves as a peer MCData server to other MCData servers. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.8.9.2 Media plane | The procedure for an IWF requesting, on behalf of an LMR user, to send a media plane SDS to an MCData group is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.6 for the group standalone short data service using the media plane, with the exception that MCData client 1 is located behind an IWF and one or more of the MCData clients 2 to n can be behind IWFs that have affiliated to the MCData group (see subclause 10.1.2 of the present document). The SDS is addressed to the MCData group ID. The IWF behaves as a peer MCData server to other MCData servers. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.9 IWF as a security gateway | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.9.1 Support for transcoding with encrypted speech | In some cases when encryption of voice media is required in the MC system, the MCPTT user(s) and the LMR user(s) can use different codecs. In these cases, transcoding is needed and before transcoding can occur, encryption applied to the voice media by the MC system needs to be removed. After transcoding, LMR encryption can be applied (out-of-scope of the present document). An IWF can perform these functions and be deployed as a security gateway between the MCPTT system and the LMR system. When the IWF removes the encryption applied by the MC system, the IWF must perform key management procedures defined in 3GPP TS 33.180 [8] to obtain the key material for the group. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.10 Simultaneous interworked calls (on-network) | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.10.1 General | An IWF representing an LMR user may support simultaneous interworked calls for the same LMR user. The LMR user can become involved in simultaneous interworked calls when the IWF invites, joins or accepts more than one interworked call on behalf of the LMR user, or when the IWF affilates the LMR user to multiple groups. This subclause is based on the subclause for simultaneous session for MCPTT calls in 3GPP TS 23.379 [7], subclause 10.8.
NOTE: An LMR user affiliating to multiple interworked groups with active calls via the IWF can result in the LMR user being invited simultaneously to multiple interworked calls.
How the IWF accomodates simultaneous interworked calls to a single LMR user is outside the scope of the present document. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.11 Location | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.11.1 Location of current talker | 3GPP TS 23.379 [7], subclause 10.6.2.7 describes a high-level procedure to provide the location of the current talker to all the receiving MCPTT users. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.11.2 Location of current talker (MCPTT server to IWF) | Figure 10.11.2-1 shows the high-level procedure to for MCPTT service to provide the location information about the current talking user to all the receiving MCPTT users and the IWF.
Pre-conditions:
1. There is on-going group call involving MCPTT client 1 and MCPTT client 2 and the IWF.
2. MCPTT client 1 is the current talking user.
3. MCPTT server has obtained the location information of MCPTT client 1.
Figure 10.11.2-1: Providing location information of the current talker
1. MCPTT client 1 gets the floor to transmit voice media.
2. The MCPTT server checks the privacy policy (authorisation to provide location information to other MCPTT users on a call when talking, as defined in 3GPP TS 23.379 [7] Annex A.3) of the current talking MCPTT user to decide if the location information of MCPTT client 1 can be provided to other MCPTT users on the call.
3. If the privacy policy permits, the MCPTT server provides the location information of MCPTT client 1 to MCPTT client 2 and the IWF. The procedures for this are described in 3GPP TS 23.280 [5] subclause 10.9.3.6. Optionally, the location information may be provided in the floor taken message sent to MCPTT client 2 and the IWF according to 3GPP TS 23.379 [7] subclause 10.9.1.3.1, if the privacy policy permits. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.11.3 Location of current talker (IWF to MCPTT server) | Figure 10.11.3‑1 shows the high-level procedure to for the IWF to provide the location information about the current LMR talking user to all the receiving MCPTT users.
Pre-conditions:
1. There is on-going group call involving MCPTT client 1 and MCPTT client 2 and the IWF.
2. An LMR user is the current talking user through the IWF.
NOTE: How the MCPTT server acquires the location of the LMR user is outside the scope of the present document.
Figure 10.11.3-1: Providing location information of the current talker
1. The IWF gets the floor to transmit voice media.
2. The MCPTT server checks the privacy policy (authorisation to provide location information to other MCPTT users on a call when talking, as defined in 3GPP TS 23.379 [7] Annex A.3) of the current talking IWF user to decide if the location information of the user on the IWF can be provided to other MCPTT users on the call.
3. The MCPTT server provides the location information of the IWF user to MCPTT client 1 and MCPTT client 2. The procedures for this are described in 3GPP TS 23.280 [5] subclause 10.9.3.6. Optionally, the location information may be provided in the floor taken message sent to MCPTT client 2 and the IWF according to 3GPP TS 23.379 [7] subclause 10.9.1.3.1. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.11.4 Information flows for location information between the IWF and the LMS | Editor's Note: It is FFS whether LMR technology type (e.g. TETRA, P25, analogue FM TIA-603-D [9] Standard) will need to be utilized in location messages between the MC system and the IWF. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.11.4.1 Location information services between the IWF and the LMS | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.11.4.1.1 IWF Location information report | Table 10.9.2.2-4 in 3GPP TS 23.280 [5] describes the information flow to support the handling of a location information report from the LMS to the IWF and from the IWF to the LMS. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.11.4.1.2 IWF Location information request | Table 10.9.2.3-4 in 3GPP TS 23.280 [5] describes the information flow to support the handling of an IWF Location information request from the LMS to the IWF and from the IWF to the LMS. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.11.4.1.3 IWF Location information subscription request | Table 10.9.2.5-3 in 3GPP TS 23.280 [5] describes the information flow from the LMS to the IWF and from the IWF to the LMS for an IWF Location information subscription request. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.11.4.1.4 IWF Location information subscription response | Table 10.9.2.6-1 in 3GPP TS 23.280 [5] describes the information flow from the LMS to the IWF and from the IWF to the LMS for an IWF Location information subscription response. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.11.4.1.5 IWF Location information notification | Table 10.9.2.7-3 in 3GPP TS 23.280 [5] describes the information flow from the LMS to the IWF and from the IWF to the LMS for an IWF Location information notification. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.11.4.1.6 IWF Location information cancel subscription request | Table 10.9.2.8-3 in 3GPP TS 23.280 [5] describes the information flow from the LMS to the IWF and from the IWF to the LMS for an IWF Location information cancel subscription request. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.11.4.1.7 IWF Location information cancel subscription response | Table 10.9.2.9-3 in 3GPP TS 23.280 [5] describes the information flow from the LMS to the IWF and from the IWF to the LMS for an IWF Location information cancel subscription response. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.11.4.2 Location information procedures between the IWF and the LMS | Editor's Note: It is FFS how configuration can be added to restrict the reporting and tracking of users in a partner MC system, or users within an LMR system. Configuration for restricting the reporting and tracking of location information in a partner MC system is not present in current stage 2 specifications. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.11.4.2.1 On-demand request of location information procedure | 10.11.4.2.1.1 On-demand request of location information procedure (LMS to IWF)
The MC service server or location management client in the MC system can request an LMR user's location information, which is in the LMR system, at any time by sending an IWF Location information request to the IWF at the LMR system.
The LMR user appears to the MC system as an MC service user. The IWF provides interworking to obtain location information for the LMR user associated with the MC service identity it receives. The IWF can translate, as needed, between MC service identities and identities used within the LMR system.
Figure 10.11.4.2.1.1-1 illustrates the high level procedure of on-demand request of location information.
Figure 10.11.4.2.1.1-1: On-demand request of location information procedure
1. The MC service server or a LMC in the MC system requests from the LMS on-demand location information of the LMR user that appears as an MC service user.
2. The LMS in the MC system checks if the provided information along with the configuration permit the request to proceed.
NOTE: Whether the authorization check is a specific MC service user based check or is a general policy check is outside the scope of this procedure.
3. The LMS in the MC system determines that the request has a target in the LMR system.
4. The LMS in the MC system sends the IWF Location information request to the IWF in the LMR system according to the described information flow in clause 10.11.4.1.2.
5. The IWF in the LMR system can choose to authorize the request.
6. The IWF at the LMR system determines the location information for the LMR user associated with the MC service user identified in the request.
7. The IWF at the LMR system sends the IWF Location information report, described in clause 10.11.4.1.1, to the LMS in the MC system. The LMS forwards the location information report to the MC service server or the LMC.
10.11.4.2.1.2 On-demand request of location information procedure (IWF to LMS)
The IWF in the LMR system can request an MC service user's location information, which is in the MC system, at any time by sending an IWF Location information request to the LMS at the MC system. The IWF can translate, as needed, between MC service identities and identities used within the LMR system.
Figure 10.11.4.2.1.2-1 illustrates the high level procedure of on-demand request of location information.
Figure 10.11.4.2.1.2-1: On-demand request of location information procedure
1. The IWF in the LMR system determines that location information is needed for an MC service user.
2. The IWF in the LMR system determines that the MC service user is in the MC system.
3. The IWF in the LMR system sends the IWF Location information request to the LMS in the MC system according to the described information flow in clause 10.11.4.1.2.
4. The LMS in the MC system authorizes the request.
5. The LMS in the MC system determines the location information for the MC service user identified in the request.
6. The LMS in the MC system sends the IWF Location information report, described in clause 10.11.4.1.1, to the IWF in the LMR system. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.11.4.2.2 Location information notification procedure | 10.11.4.2.2.1 Location information notification procedure (IWF to LMS)
The IWF in the LMR system provides location information, based on some decision or event, to the LMS. The IWF can translate, as needed, between MC service identities and identities used within the LMR system.
Figure 10.11.4.2.2.1-1 illustrates the high level procedure of notification of location information.
Figure 10.11.4.2.2.1-1: Event-triggered location information notification procedure
1. The IWF in the LMR system determines that it has location information available that is to be notified to the LMS in the MC system.
2. The IWF in the LMR system sends the IWF Location information notification to the LMS in the MC system, according to the described information flow in clause 10.11.4.1.5.
10.11.4.2.2.2 Location information notification procedure (LMS to IWF)
The LMS in the MC system provides location information to the IWF in the LMR system. The IWF can translate, as needed, between MC service identities and identities used within the LMR system.
Figure 10.11.4.2.2.2-1 illustrates the high level procedure of notification of location information.
Figure 10.11.4.2.2.2-1: Event-triggered location information notification procedure
1. The LMS in the MC system determines that it has location information available that is to be notified to the IWF in the LMR system.
2. The LMS in the MC system sends the IWF Location information notification to the IWF in the LMR system, according to the described information flow in clause 10.11.4.1.5. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.11.4.2.3 Location information subscription procedure | 10.11.4.2.3.1 Location information subscription procedure (LMS to IWF)
An IWF Location information subscription request is sent from the MC system to the IWF. The IWF in the LMR system sends an IWF location information subscription response. The IWF can translate, as needed, between MC service identities and identities used within the LMR system.
Figure 10.11.4.2.3.1-1 illustrates the high level procedure of subscription to location information from the LMS in the MC system to the IWF in the LMR system.
Figure 10.11.4.2.3.1-1: Location information subscription procedure
1. The MC service server or the LMC in the MC system sends a request for subscription to event-triggered location information of LMR users that appear as MC service users in the LMR system by sending a location information subscription request to the LMS in the MC system, according to the described information flows in clause 10.9.2.5 in 3GPP TS 23.280 [5].
2. The LMS in the MC system checks if the provided information along with the configuration permit the request to proceed.
NOTE: Whether the authorization check is a specific MC service user based check or is a general policy check is outside the scope of this procedure.
3. The LMS in the MC system determines that the request has a target in an LMR system.
4. The LMS in the MC system sends the IWF Location information subscription request to the IWF in the LMR system, according to the described information flow in clause 10.11.4.1.3.
5. The IWF in the LMR system can check if the provided information along with the configuration permit the request to proceed.
6. The IWF in the LMR system applies the subscription.
7. The IWF in the LMR system sends the IWF Location information subscription response to the LMS in the MC system according to the described information flow in clause 10.11.4.1.4. The LMS in the MC system can respond to the LMC or MC server in the MC system per the procedures of 3GPP TS 23.280 [5].
10.11.4.2.3.2 Location information subscription procedure (IWF to LMS)
An IWF Location information subscription request is sent from the MC system to the IWF. The IWF in the LMR system sends an IWF Location information subscription response. The IWF can translate, as needed, between MC service identities and identities used within the LMR system.
Figure 10.11.4.2.3.2-1 illustrates the high level procedure of subscription to location information from the LMS in the MC system to the IWF in the LMR system.
Figure 10.11.4.2.3.2-1: Location information subscription procedure
1. The IWF in the LMR system determines that it needs to subscribe to location information notifications for an MC service user.
2. The IWF in the LMR system determines that the request has a target in the MC system.
3. The IWF in the LMR system sends the IWF Location information subscription request to the LMS in the MC system, according to the described information flow in clause 10.11.4.1.3.
4. The LMS in the MC system checks if the provided information along with the configuration permit the request to proceed.
5. The LMS in the MC system applies the subscription.
6. The LMS in the MC system sends the IWF Location information subscription response to the LMS in the MC system according to the described information flow in clause 10.11.4.1.4. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.11.4.2.4 Location information cancel subscription procedure | 10.11.4.2.4.1 Location information cancel subscription procedure (LMS to IWF)
The LMC in the MC system receives location information updates according to the subscriptions requested in the LMR system per clause 10.11.4.2.3. Those subscriptions can be cancelled anytime from the MC system. The IWF can translate, as needed, between MC service identities and identities used within the LMR system.
Figure 10.11.4.2.4.1-1 illustrates the high level procedure of the subscription cancellation to location information from the MC system to the LMR system.
Figure 10.11.4.2.4.1-1: Location information cancel subscription procedure
1. The MC service server or the LMC in the MC system requests the cancellation of subscriptions to event-triggered location information of LMR users that appear as MC service users in the LMR system by sending location information cancel subscription requests to the LMS in the MC system, according to the described information flows in clause 10.9.2.8 in 3GPP TS 23.280 [5].
2. The LMS in the MC system checks if the provided information along with the configuration permit the request to proceed.
NOTE: Whether the authorization check is a specific MC service user based check or is a general policy check is outside the scope of this procedure.
3. The LMS in the MC system determines that the request has a target in an LMR system.
4. The LMS in the MC system sends the IWF Location information cancel subscription request to the IWF in the LMR system, according to the described information flow in clause 10.11.4.1.6.
5. The IWF in the LMR system can check if the provided information along with the configuration permit the request to proceed.
6. The IWF in the LMR system cancels the subscription.
7. The IWF in the LMR system sends the IWF Location information cancel subscription response to the LMS in the MC system, according to the described information flow in clause 10.11.4.1.7. The LMS can forward the location information cancel subscription response per the procedures in 3GPP TS 23.280 [5].
10.11.4.2.4.2 Location information cancel subscription procedure (IWF to LMS)
The IWF in the LMR system receives location information updates according to the subscriptions requested in the MC system per clause 10.11.4.2.3.2. Those subscriptions can be cancelled anytime from the LMR system. The IWF can translate, as needed, between MC service identities and identities used within the LMR system.
Figure 10.11.4.2.4.2-1 illustrates the high level procedure of the subscription cancellation to location information from the LMR system to the MC system.
Figure 10.11.4.2.4.2-1: Location information cancel subscription procedure
1. The IWF in the LMR system determines that a location information subscription is to be cancelled.
2. The IWF in the LMR system determines that the request has a target in the MC system.
3. The IWF in the LMR system sends the IWF Location information cancel subscription request to the LMS in the MC system, according to the described information flow in clause 10.11.4.1.6.
4. The LMS in the MC system checks if the provided information along with the configuration permit the request to proceed.
5. The LMS in the MC system cancels the subscription.
6. The LMS in the MC system sends the IWF Location information cancel subscription response to the IWF in the LMR system, according to the described information flow in clause 10.11.4.1.7. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.12 LMR security transport | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.12.1 Information flows for LMR security transport | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.12.1.1 Non-3GPP security message | Table 10.12.1.1-1 describes the information flow non-3GPP security message from the MC service server to the IWF, from the IWF to the MC service server, from the MC service server to the MC service client and from the MC service client to the MC service server.
Table 10.12.1.1-1: Non-3GPP security message
Information Element
Status
Description
MC service ID
M
The MC service identity supporting the sending LMR security entity
MC service ID
M
The MC service identity supporting the LMR security entity towards which the data is sent
LMR type
O
The LMR technology, e.g. TETRA, P25. Required when sent toward the MC service client.
Payload
M
Opaque payload. Contents and format are out of 3GPP scope. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.12.1.2 Void | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.12.2 LMR key management messages | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.12.2.1 General | This subclause defines end to end messaging to convey the non-3GPP, LMR security information opaquely (message contents are out of 3GPP's scope) across the MC system, between the IWF and the LMR aware MC service client. The end to end messages are service independent, any MC service may support them. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.12.2.2 MC service client initiated | Figure 10.12.2.2-1 describes the case where an MC service client sends LMR security information to the IWF.
Pre-conditions:
1. The MC service client is registered and the user is authenticated and authorized to use the MC service server.
Figure 10.12.2.2-1: Non-3GPP security messaging, MC service client to the IWF
1. The MC service client sends a non-3GPP security message to the MC service server. The contents of the message are opaque to the MC service and are out of scope of 3GPP.
2. The MC service server forwards the contents of the non-3GPP security message to the IWF. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.12.2.3 IWF initiated | Figure 10.12.2.3-1 describes the case where the IWF sends LMR security information to an MC service client.
Pre-conditions:
1. The MC service client is registered and the user is authenticated and authorized to use the MC service server.
Figure 10.12.2.3-1: Non-3GPP security messaging, from the IWF to MC service client
1. The IWF sends a non-3GPP security message to the MC service server. The contents of the message are opaque to the MC service and are out of scope of 3GPP.
2. The MC service server forwards the contents of non-3GPP security message to the MC service client. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.13 Analogue FM/TIA-603-D and other legacy LMR interworking | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.13.1 General | An IWF representing an LMR user can support interworking with legacy analogue FM radio systems that are compliant with the TIA-603-D [9] Standard. This type of legacy LMR system is sometimes referred to as conventional FM radio.
Characteristics of legacy conventional FM radio include:
- Voice media is conveyed without the use of a voice codec.
- There is no possibility of end-to-end encryption between an LMR user and a MC user.
- Group communication is possible using various means to identify a group such as a single channel / FM frequency, or sub-audible data as defined in [3]. The means for identifying groups within the legacy conventional FM system is outside the scope of the present document.
- The ID of the talking party is generally not available. Various means to identify a talker are available in legacy conventional FM systems, but this is outside the scope of the present document.
- Indication of call priority (e.g. emergency) is generally not available. Various means to identify priority are available in legacy conventional FM systems, but this is outside the scope of the present document.
Other legacy LMR systems such as digital conventional (e.g. P25 conventional), trunked analogue FM systems, non-standard legacy LMR systems, both conventional and trunked, can also be supported as long as they conform to the present document. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.13.2 Interworking Concepts | Procedures defined in the present document are applicable to interworking with legacy analogue FM radio systems.
Architecture concepts for interworking are summarized below, including general information for other legacy conventional radio systems.
- The IWF is configured with knowledge of groups and users from legacy conventional LMR radio systems. Translations to MCPTT Group and MCPTT User IDs is performed by the IWF as specified in the present document. How the legacy LMR conventional system supports groups, such as mapping a group to a channel/frequency, or using a Group ID (i.e. P25 conventional), or mapping some other protocol element or tone signalling to a group is outside the scope of the present document.
- Interworking to a legacy conventional LMR system can make use of the following procedures as defined in the present document:
- affiliation;
- group management including group regrouping
- group calls including pre-arranged, chat, and broadcast;
- priority calls including emergency and imminent peril; and
- private calls.
NOTE 1: Some analogue FM conventional LMR systems and digital conventional LMR systems support various schemes for private call. These can be supported as long as they conform to the present document.
- Interworking to a legacy conventional LMR system can make use of the following functions of the MCPTT system, as defined in the present document:
- transcoding.
- Interworking to a legacy conventional LMR system can make use of the following functions of the MCPTT system, as defined in the present document, with some limitations:
- caller ID / talker ID;
- priority indication (e.g. emergency);
- end-to-end encryption;
- location; and
- short data service.
NOTE 2: Some digital conventional LMR systems, such as P25 Conventional, natively support group IDs, user IDs, short data, and priority indication. In some cases, the talker ID becomes available sometime after the call starts.
NOTE 3: Some analogue FM conventional LMR systems support various schemes for caller ID, emergency, and other features (e.g. Multi-tone, Type 99). These can be supported as long as they conform to the present document. In some cases, the talker ID becomes available sometime after the call starts.
NOTE 4: Some digital conventional LMR systems, such as P25 Conventional, can support end-to-end encryption between the LMR user and a MC user. There is no possibility of end-to-end encryption between an analogue FM LMR user and a MC user. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.13.3 Procedures | As described above, existing procedures in this document can be used for interworking with legacy conventional LMR radio systems.
The following procedures describe special cases where the MCPTT ID (i.e. talker ID) is updated during a media transmission within a call. This mechanism of updating the MCPTT ID part way through an MCPTT media transmission may be used for any MCPTT media transmission described elsewhere in the present document. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.13.3.1 Group call with talker ID update initiated by an LMR user on an interworking group defined in the MCPTT system | In this procedure, an LMR user in a legacy conventional FM radio system initiates a group call on an interworking group defined in the MCPTT system. The talker ID is not known at the start of the call and is updated after media transmission begins. The signalling procedure is described in figure 10.13.3.1-1.
This subclause is based upon subclause for pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2.
Pre-conditions:
1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the MCPTT system.
2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service.
3. The users in this interworking group have been affiliated to the interworking group.
4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
5. The LMR user in a legacy conventional FM radio system initiates a group call.
NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.13.3.1-1: Group call with talker ID update initiated by an LMR user on an interworking group defined in the MCPTT system
1. The IWF sends an IWF group call request to the MCPTT server for call establishment. In this case floor control is also requested and an indication of implicit floor request is included. The IWF uses its pre-configured MCPTT ID in the group call request.
2. The MCPTT server calls the affiliated users from the MCPTT system as described in 3GPP TS 23.379 [7]. The LMR user is in a legacy conventional FM radio system so E2EE is not specified, and transcoding is needed at the IWF.
3. If the group has other affiliated LMR users than the calling party and the MCPTT server has received individual affiliations from those LMR users, an individual IWF group call request is sent to the IWF for each affiliated LMR user.
NOTE 2: Steps 2 and 3 can occur in any order.
NOTE 3: How the LMR users from the LMR system are being called is outside the scope of the present document.
4. The IWF returns IWF group call response(s) to the MCPTT server.
5. The MCPTT server confirms the successful establishment of the group call by sending an IWF Group call response to the IWF.
NOTE 4: How the group call response is returned to the initiating LMR user is outside the scope of the present document.
6. The interworking group call has successfully established media plane for communication and any user can transmit media. The MCPTT system where the interworking group is defined is the controlling system of the group call and manages the floor control.
NOTE 5: How the floor control is managed in the LMR system is outside the scope of the present document.
7. Because the group call request contained an imlicit floor request, and no other users are requesting the floor, the MCPTT server sends an IWF floor granted message to the IWF confirming that the IWF has the floor. The MCPTT server also sends Floor taken messages to the affiliated users in the MCPTT system. The MCPTT ID in the floor taken messages is the pre-configured IWF MCPTT ID.
8. If the group has other affiliated LMR users than the calling party, and the MCPTT server has received individual affiliations from those LMR users, an individual IWF floor taken message is sent to the IWF for each affiliated LMR user.
9. At some time after media transfer begins, the IWF receives knowledge of the LMR user's talker ID.
NOTE 6: How the IWF learns the LMR user's talker ID is outside the scope of the present document. In some LMR conventional systems, the talker ID becomes available shortly after the start of the call; in other systems, it is not available until the end of the call.
10. The IWF sends an IWF talker ID update to the MCPTT server informing the server that a new talker is using the floor, but the floor should not be released.
11. The MCPTT server sends Floor taken messages to the affiliated users in the MCPTT system. The MCPTT ID in the floor taken messages is the new talker ID contained in the IWF talker ID update.
NOTE 7: All other floor participants (not shown) that are part of this group call receive a floor taken message, so that the other floor participants learn the identity of the newly granted talker.
12. If the group has other affiliated LMR users than the calling party, and the MCPTT server has received individual affiliations from those LMR users, an individual IWF floor taken message is sent to the IWF for each affiliated LMR user. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.13.3.2 Group call with talker ID update initiated by an LMR user on an interworking group defined in the LMR system | In this procedure, an LMR user in a legacy conventional FM radio system initiates a group call on an interworking group defined in the LMR system. The talker ID is not known at the start of the call and is updated after media transmission begins. The signalling procedure is described in figure 10.13.3.2-1.
This subclause is based upon subclause for pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2.
Pre-conditions:
1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system.
2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service.
3. The users in this interworking group have been affiliated to the interworking group.
4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
5. The LMR user in a legacy conventional FM radio system initiates a group call.
NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.13.3.2-1: Group call with talker ID update initiated by an LMR user on an interworking group defined in the LMR system
1. The IWF sends an IWF group call request(s) to the MCPTT server for call establishment. An individual IWF group call request is sent to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the users in MCPTT clients 1 and 2. In this case floor control is also requested and an indication of implicit floor request is included. The IWF uses its pre-configured MCPTT ID in the group call request.
2. The MCPTT server sends a group call request(s) to the target MCPTT user(s) as described in 3GPP TS 23.379 [7]. The LMR user is in a legacy conventional FM radio system so E2EE is not specified, and transcoding is needed at the IWF.
3. MCPTT client(s) receiving the group call request, acknowledge towards the MCPTT server by sending a group call response.
4. The MCPTT server acknowledges the IWF group call request(s) by sending an IWF group call response(s) to the IWF.
NOTE 2: How the IWF group call response(s) is handled in the IWF / LMR system and how the other LMR users are being called is outside the scope of the present document.
5. The interworking group call has successfully established media plane for communication and any user can transmit media. The LMR system where the interworking group is defined is the controlling system of the group call and manages the floor control.
NOTE 3: How the floor control is managed in the LMR system is outside the scope of the present document.
6. Because the group call request contained an implicit floor request, and no other users are requesting the floor, the IWF sends an IWF floor taken message to the MCPTT server confirming that the IWF has the floor. An individual IWF floor taken message is sent to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the users in MCPTT clients 1 and 2.
7. The MCPTT server sends Floor taken to the target MCPTT user(s) in the MCPTT system. The MCPTT ID in the floor taken messages is the pre-configured IWF MCPTT ID.
8. At some time after media transfer begins, the IWF receives knowledge of the LMR user's talker ID.
NOTE 4: How the IWF learns the LMR user's talker ID is outside the scope of the present document. In some LMR conventional systems, the talker ID becomes available shortly after the start of the call; in other systems, it is not available until the end of the call.
9. The IWF sends an IWF floor taken to the MCPTT server informing the server that a new talker is using the floor, but the floor should not be released. An individual IWF floor taken message is sent to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the users in MCPTT clients 1 and 2
10. The MCPTT server sends Floor taken messages to the target MCPTT user(s) in the MCPTT system. The MCPTT ID in the floor taken messages is the new talker ID contained in the IWF talker ID update.
NOTE 5: All other floor participants (not shown) that are part of this group call receive a floor taken message, so that the other floor participants learn the identity of the newly granted talker. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.14 IWF functional alias management | |
206be7a57129464f73be1aa9d853095b | 23.283 | 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.
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]. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.14.2 IWF information flows for functional alias management | |
206be7a57129464f73be1aa9d853095b | 23.283 | 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. |
206be7a57129464f73be1aa9d853095b | 23.283 | 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. |
206be7a57129464f73be1aa9d853095b | 23.283 | 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. |
206be7a57129464f73be1aa9d853095b | 23.283 | 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). |
206be7a57129464f73be1aa9d853095b | 23.283 | 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. |
206be7a57129464f73be1aa9d853095b | 23.283 | 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. |
206be7a57129464f73be1aa9d853095b | 23.283 | 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. |
206be7a57129464f73be1aa9d853095b | 23.283 | 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. |
206be7a57129464f73be1aa9d853095b | 23.283 | 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). |
206be7a57129464f73be1aa9d853095b | 23.283 | 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. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.14.3 IWF Functional alias management procedures | |
206be7a57129464f73be1aa9d853095b | 23.283 | 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. |
206be7a57129464f73be1aa9d853095b | 23.283 | 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.
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. |
206be7a57129464f73be1aa9d853095b | 23.283 | 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).
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).
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). |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.