hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.6.2.2.4 Emergency group call setup initiated by a user in the MCPTT system to an interworking group defined in the LMR system
| Figure 10.6.2.2.4‑1 shows the procedure for an emergency group call initiated by a user in the MCPTT system. The figure is based upon the figure for MCPTT emergency group call in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.1. This scenario assumes that the MCPTT group is an interworking group defined in the LMR system.
N... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.6.2.3 In-progress emergency group state cancel of an interworking group
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.6.2.3.1 LMR user initiated in-progress emergency group state cancel of an interworking group defined in the MCPTT system
| Figure 10.6.2.3.1‑1 shows the procedure for an in-progress emergency group state cancel initiated by an LMR user. The figure is based upon the figure for MCPTT in-progress emergency group state cancel in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3.
NOTE 1: For simplicity, a single MCPTT server is shown in place of a us... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.6.2.3.2 MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in the MCPTT system
| Figure 10.6.2.3.2‑1 shows the procedure for an in-progress emergency group state cancel initiated by an MCPTT user. The figure is based upon the figure for MCPTT in-progress emergency group state cancel in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3.
NOTE 1: For simplicity, a single MCPTT server is shown in place of a ... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.6.2.3.3 LMR user initiated in-progress emergency group state cancel of an interworking group defined in an LMR system
| Figure 10.6.2.3.3‑1 shows the procedure for an in-progress emergency group state cancel initiated by an LMR user.
NOTE 1: The information flows between MCPTT client and MCPTT server are defined 3GPP TS 23.379 [7].
NOTE 2: The end of an MCPTT emergency group call does not cancel the MCPTT group's in-progress emergency... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.6.2.3.4 MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in an LMR system
| Figure 10.6.2.3.4‑1 shows the procedure for an in-progress emergency group state cancel initiated by an MCPTT user. The figure is based upon the figure for MCPTT in-progress emergency group state cancel in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3.
NOTE 1: The information flows between an MCPTT client and an MCPTT se... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.6.2.4 Losing audio
| For LMR systems where a user cannot be pre-empted, the IWF identifies the audio as losing audio to the system. Subclause 10.5 is applicable to losing audio during emergency calls as well as non-emergency calls.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.6.2.5 Default emergency group
| In MCPTT, the user's profile determines whether an emergency is raised on the user's currently selected group or on a configured default emergency group. It's up to the IWF and the LMR system to which it is connected to determine what group the emergency is raised on and whether an alert is also sent when the emergency... |
b222c2facf93ba50ceb04ea3111d14d8 | 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.
|
b222c2facf93ba50ceb04ea3111d14d8 | 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 MCP... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.6.3 Imminent peril calls
| |
b222c2facf93ba50ceb04ea3111d14d8 | 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 docu... |
b222c2facf93ba50ceb04ea3111d14d8 | 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 an... |
b222c2facf93ba50ceb04ea3111d14d8 | 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... |
b222c2facf93ba50ceb04ea3111d14d8 | 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 ... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.6.4 Emergency alerts
| |
b222c2facf93ba50ceb04ea3111d14d8 | 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 se... |
b222c2facf93ba50ceb04ea3111d14d8 | 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... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.6.5 Emergency alert cancellation
| |
b222c2facf93ba50ceb04ea3111d14d8 | 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... |
b222c2facf93ba50ceb04ea3111d14d8 | 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 servi... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.7 Codec
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.7.1 Information flows for codec
| |
b222c2facf93ba50ceb04ea3111d14d8 | 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 reque... |
b222c2facf93ba50ceb04ea3111d14d8 | 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 s... |
b222c2facf93ba50ceb04ea3111d14d8 | 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 ... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.7.3 Codec negotiation by the LMR system
| |
b222c2facf93ba50ceb04ea3111d14d8 | 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... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.8 MCData short data service
| |
b222c2facf93ba50ceb04ea3111d14d8 | 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, ... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.8.2 Information flows for the short data service
| |
b222c2facf93ba50ceb04ea3111d14d8 | 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 approp... |
b222c2facf93ba50ceb04ea3111d14d8 | 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
M... |
b222c2facf93ba50ceb04ea3111d14d8 | 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 ... |
b222c2facf93ba50ceb04ea3111d14d8 | 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)
Infor... |
b222c2facf93ba50ceb04ea3111d14d8 | 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)
Informati... |
b222c2facf93ba50ceb04ea3111d14d8 | 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
MCD... |
b222c2facf93ba50ceb04ea3111d14d8 | 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
... |
b222c2facf93ba50ceb04ea3111d14d8 | 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
St... |
b222c2facf93ba50ceb04ea3111d14d8 | 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
I... |
b222c2facf93ba50ceb04ea3111d14d8 | 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].
|
b222c2facf93ba50ceb04ea3111d14d8 | 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.
|
b222c2facf93ba50ceb04ea3111d14d8 | 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.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.8.6 MCData user one-to-one SDS request to an LMR user
| |
b222c2facf93ba50ceb04ea3111d14d8 | 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 ... |
b222c2facf93ba50ceb04ea3111d14d8 | 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... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.8.7 LMR user one-to-one SDS request to an MCData user
| |
b222c2facf93ba50ceb04ea3111d14d8 | 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 be... |
b222c2facf93ba50ceb04ea3111d14d8 | 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 a... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.8.8 MCData user group SDS request to an MCData group including LMR users
| |
b222c2facf93ba50ceb04ea3111d14d8 | 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... |
b222c2facf93ba50ceb04ea3111d14d8 | 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 on... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.8.9 LMR user group SDS request to an MCData group
| |
b222c2facf93ba50ceb04ea3111d14d8 | 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 IW... |
b222c2facf93ba50ceb04ea3111d14d8 | 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 M... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.9 IWF as a security gateway
| |
b222c2facf93ba50ceb04ea3111d14d8 | 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... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.10 Simultaneous interworked calls (on-network)
| |
b222c2facf93ba50ceb04ea3111d14d8 | 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.... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.11 Location
| |
b222c2facf93ba50ceb04ea3111d14d8 | 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.
|
b222c2facf93ba50ceb04ea3111d14d8 | 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 curre... |
b222c2facf93ba50ceb04ea3111d14d8 | 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 t... |
b222c2facf93ba50ceb04ea3111d14d8 | 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.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.11.4.1 Location information services between the IWF and the LMS
| |
b222c2facf93ba50ceb04ea3111d14d8 | 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.
|
b222c2facf93ba50ceb04ea3111d14d8 | 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.
|
b222c2facf93ba50ceb04ea3111d14d8 | 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.
|
b222c2facf93ba50ceb04ea3111d14d8 | 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.
|
b222c2facf93ba50ceb04ea3111d14d8 | 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.
|
b222c2facf93ba50ceb04ea3111d14d8 | 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.
|
b222c2facf93ba50ceb04ea3111d14d8 | 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.
|
b222c2facf93ba50ceb04ea3111d14d8 | 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.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.11.4.2.1 On-demand request of location information procedure
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 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 interw... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 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... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.11.4.2.2 Location information notification procedure
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 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... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 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:... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.11.4.2.3 Location information subscription procedure
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 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 hi... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 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 hi... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.11.4.2.4 Location information cancel subscription procedure
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 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.
F... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 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.... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.12 LMR security transport
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.12.1 Information flows for LMR security transport
| |
b222c2facf93ba50ceb04ea3111d14d8 | 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... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.12.1.2 Void
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.12.2 LMR key management messages
| |
b222c2facf93ba50ceb04ea3111d14d8 | 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 but only implemented for 3GPP transport using the MC... |
b222c2facf93ba50ceb04ea3111d14d8 | 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... |
b222c2facf93ba50ceb04ea3111d14d8 | 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 c... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.13 Analogue FM/TIA-603-D and other legacy LMR interworking
| |
b222c2facf93ba50ceb04ea3111d14d8 | 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 withou... |
b222c2facf93ba50ceb04ea3111d14d8 | 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 leg... |
b222c2facf93ba50ceb04ea3111d14d8 | 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 th... |
b222c2facf93ba50ceb04ea3111d14d8 | 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 subc... |
b222c2facf93ba50ceb04ea3111d14d8 | 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 subcla... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.14 IWF functional alias management
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.