hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.5 Floor control on an interworking group homed in the LMR system
|
Figure 10.5.5‑1 shows the procedure for floor control on an interworking group homed in the LMR system. Simultaneous floor requests are included to show various aspects of interworking floor control.
Pre-conditions:
1. The interworking group is homed in the LMR system.
2. The MCPTT server is configured to locally filter competing floor control requests before communicating with the IWF.
3. MCPTT client 1, MCPTT client 2, and LMR users (represented by the IWF) are affiliated to that group.
4. An interworking group call is ongoing involving MCPTT users and LMR users (represented by the IWF). The floor is currently idle.
Figure 10.5.5-1: Floor control on a group homed in the LMR system
1. The users of MCPTT Client 1 and MCPTT Client 2 both want to send voice media over the session.
2. MCPTT Clients 1 and 2 send floor request messages to the floor control server.
3. The MCPTT floor control server determines to accept the floor request from MCPTT Client 1 based on local arbitration results (e.g., according to priority information versus the competing request from MCPTT client 2).
4. The user of MCPTT client 2 is notified that their floor request was rejected.
5. Since the group is homed in the LMR system the MCPTT floor control server forwards the floor request to the IWF for final floor control determination. The IWF performs floor arbitration in conjunction with the LMR system (not shown). The IWF determines that the floor can be granted to the MCPTT user.
6. The IWF sends a floor granted message to the MCPTT floor control server.
7. The MCPTT floor control server sends a floor granted message to MCPTT client 1.
8. The MCPTT floor control server sends a floor taken message to MCPTT client 2 to notify the user of who is granted the floor.
9. MCPTT Client 1 notifies the user that he/she has been granted the floor and may begin speaking.
10. MCPTT Client 1 begins sending voice media over the established session. The media is distributed to affiliated group members including the IWF.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.6 Floor control on an interworking group homed in the MCPTT system
|
Figure 10.5.6‑1 shows the procedure for floor control on an interworking group homed in the MCPTT system, and the LMR system is configured for local floor control request filtering. Simultaneous floor requests are included to show various aspects of interworking floor control.
Pre-conditions:
1. The interworking group is homed in the MCPTT system.
2. The interworking group is previously defined on the group management server.
3. MCPTT client 1, MCPTT client 2, and LMR users (represented by the IWF) are affiliated to that group.
4. An interworking group call is ongoing involving MCPTT users and LMR users (represented by the IWF). The floor is currently idle.
Figure 10.5.6-1: Floor control on a group homed in the MCPTT system
1. The user of MCPTT Client 1 wants to send voice media over the session. At the same time a user in the LMR system (represented by the IWF) wants to also send voice media over the session.
2. MCPTT Client 1 sends a floor request message to the MCPTT floor control server.
3. The IWF sends a floor request message to the MCPTT floor control server.
NOTE: If multiple LMR users want to speak, it is assumed that the LMR system has arbitrated these requests based on local policies and only presents one floor request to the MCPTT system.
4. Since the group is homed in the MCPTT system the MCPTT floor control server performs final floor control determination. In this case the MCPTT floor control server determines to accept the floor request from MCPTT Client 1 based on local policy and arbitration results (e.g., according to time of arrival of the request versus the competing request from the IWF).
5. The IWF is notified that its floor request was rejected.
6. The MCPTT floor control server sends a floor granted message to MCPTT client 1.
7. The MCPTT floor control server sends a floor taken message to both MCPTT client 2 and the IWF to inform them of who is granted the floor.
8. MCPTT Client 1 notifies the user that he/she has been granted the floor and may begin speaking.
9. MCPTT Client 1 begins sending voice media over the established session. The media is distributed to affiliated group members including the IWF.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.7 Floor control without local filtering on an interworking group defined in the LMR system
|
Figure 10.5.7‑1 shows the procedure for floor control on an interworking group defined in the LMR system where local filtering is not performed by the MCPTT server. Simultaneous floor requests are included to show various aspects of interworking floor control.
Pre-conditions:
1. The interworking group is defined in the LMR system.
2. The MCPTT system is configured to send competing floor control requests to the LMR system (represented by the IWF) for floor control arbitration.
3. MCPTT client 1, MCPTT client 2, and LMR users are affiliated to that group.
4. An interworking group call is ongoing involving MCPTT users and LMR users. The floor is currently idle.
Figure 10.5.7-1: Floor control without local filtering on a group defined in the LMR system
1. The users of MCPTT client 1 and MCPTT client 2 both want to send voice media over the session.
2. MCPTT clients 1 and 2 send floor request messages to the MCPTT floor control server.
3. Since the group is defined in the LMR system the MCPTT floor control server forwards these floor requests to the IWF for final floor control determination. The IWF performs floor arbitration in conjunction with the LMR system (not shown). The IWF determines that the floor can be granted to MCPTT client 1.
4. The IWF sends an IWF floor granted message for MCPTT client 1, an IWF floor rejected message for MCPTT client 2, and an IWF floor taken message for MCPTT client 2 to the MCPTT floor control server.
NOTE: If other MCPTT clients are affiliated to this group, the IWF sends an IWF floor taken message to the MCPTT floor control server for each one of them.
5. The MCPTT floor control server sends a Floor rejected message to MCPTT client 2 to notify the user that his/her floor request was rejected.
6. The MCPTT floor control server sends a Floor granted message to MCPTT client 1.
7. The MCPTT floor control server sends a Floor taken message to MCPTT client 2 to notify the user of who is granted the floor.
8. MCPTT client 1 notifies the user that he/she has been granted the floor and may begin speaking.
9. MCPTT client 1 begins sending voice media over the established session. The media is distributed to affiliated group members including the IWF.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.8 Floor control without local filtering on an interworking group defined in the MCPTT system
|
Figure 10.5.8‑1 shows the procedure for floor control on an interworking group defined in the MCPTT system where local filtering is not performed by the LMR system. Simultaneous floor requests are included to show various aspects of interworking floor control.
Pre-conditions:
1. The interworking group is defined in the MCPTT system.
2. MCPTT client 1, MCPTT client 2, and LMR users are affiliated to that group.
3. The LMR system (represented by the IWF) is configured to send all competing floor control requests to the MCPTT system for floor control arbitration.
4. The IWF is not affiliating on behalf of LMR users. All LMR group affiliations are passed through the IWF to the MCPTT server.
5. An interworking group call is ongoing involving MCPTT users and LMR users. The floor is currently idle.
Figure 10.5.8-1: Floor control without local filtering on a group defined in the MCPTT system
1. The user of MCPTT client 1 wants to send voice media over the session. At the same time multiple users in the LMR system (represented by the IWF) want to also send voice media over the session.
2. MCPTT client 1 sends a floor request message to the MCPTT floor control server.
3. The IWF sends floor request messages to the MCPTT floor control server for each LMR user requesting the floor. In this case two LMR users are requesting the floor. These floor requests contain the MCPTT ID of the LMR user (converted by the IWF).
4. Since the group is defined in the MCPTT system the MCPTT floor control server performs final floor control determination. In this case the MCPTT floor control server determines to accept the floor request from MCPTT client 1 based on local policy and arbitration results (e.g., according to priority of the request versus the competing requests from the IWF).
5. The IWF is notified that its floor requests were rejected. The MCPTT floor control server sends an IWF floor rejected message to the IWF for each floor request.
6. The MCPTT floor control server sends a floor granted message to MCPTT client 1.
7. The MCPTT floor control server sends floor taken messages to MCPTT client 2 and the IWF to inform them of who is granted the floor. In this case a floor taken message is sent to the IWF corresponding to each affiliated LMR user.
NOTE: If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF floor taken message is sent to the IWF.
8. MCPTT client 1 notifies the user that he/she has been granted the floor and may begin speaking.
9. MCPTT client 1 begins sending voice media over the established session. The media is distributed to affiliated group members including the LMR users.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.9 Floor control in private call controlled by the LMR system
|
Figure 10.5.9‑1 shows a procedure for a private call with floor control where the LMR system controls the floor. A request for transmission by the MCPTT user while the LMR user has the floor is rejected by the IWF, to show various aspects of interworking floor control.
Pre-conditions:
1. A private call has been set up between an LMR user and MCPTT client 1.
2. The LMR system is controlling the floor, via the IWF.
3. MCPTT client 1 has the floor.
Figure 10.5.9-1: Floor control with control by the LMR system
1. The user of MCPTT Client 1 finishes transmission and MCPTT client 1 releases the floor.
2. The MCPTT server informs the IWF of the floor release.
3. The IWF indicates that the floor is now idle.
4. MCPTT client 1 is informed that the floor is idle.
5. The IWF indicates that the floor has been taken by the LMR user.
6. The MCPTT server informs MCPTT client 1 that the floor has been taken by the LMR user.
7. Media flows from the LMR user to the IWF (7a) and on to MCPTT client 1 (7b).
8. The user of MCPTT client 1 decides to interrupt the transmission from the LMR user.
9. MCPTT Client 1 sends a floor request with an appropriate priority to request interruption of the transmission from the LMR user.
10. The MCPTT server forwards the floor request to the IWF.
11. The LMR system rejects the request, and the IWF informs the MCPTT server of the rejection.
NOTE: The reason that the request is rejected is outside the scope of the present document.
12. The MCPTT server informs MCPTT client 1 that the request for interruption has been rejected.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.10 Floor control in private call controlled by the MCPTT system
|
Figure 10.5.10‑1 shows a procedure for a private call with floor control where the MCPTT system controls the floor. A request for transmission by the LMR user while the MCPTT user has the floor is accepted by the MCPTT server, to show various aspects of interworking floor control.
Pre-conditions:
1. A private call has been set up between the LMR user and MCPTT client 1.
2. The MCPTT server is controlling the floor.
3. The floor is idle.
Figure 10.5.10-1: Floor control with control by the MCPTT system
1. MCPTT Client 1 requests the floor.
2. The MCPTT server grants the floor to MCPTT Client 1.
3. The MCPTT server informs the IWF that the floor has been granted to MCPTT client 1.
NOTE 1: Step 3 may occur before or after step 2.
4. MCPTT client 1 sends voice media to the MCPTT server (4a) which forwards the voice media to the IWF (4b).
5. The LMR user decides to interrupt the transmission from MCPTT client 1, and the IWF is informed.
6. The IWF sends a floor request to the MCPTT server with sufficient priority to interrupt MCPTT client 1.
7. The MCPTT server decides to allow the interruption from the LMR user, based on the priority of the request and on configuration.
8. The MCPTT server informs MCPTT Client 1 that the transmission permission has been revoked.
9. The floor is granted to the LMR user via the IWF.
NOTE 2: Step 9 may occur before or after step 8.
10. Voice media is sent from the LMR user via the IWF to the MCPTT server (10a) and on to MCPTT client 1 (10b).
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.6 Emergency and imminent peril
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.6.1 Information flows for emergency and imminent peril
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.6.1.1 IWF emergency group call request
|
Table 10.6.1.1-1 describes the information flow IWF emergency group call request from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.6.1.1-1: IWF emergency group call request information elements
Information Element
Status
Description
MCPTT ID
M
The identity of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT group ID
M
The MCPTT group ID on which the call is to be conducted
Emergency indicator
M
Indicates that the group call request is an MCPTT emergency call
Alert indicator
O
May be used to indicate that an emergency alert is to be sent
Location
O
Location, if available
Implicit floor request
(see NOTE)
O
Indicates that the originating client requests the floor
NOTE: This element shall be included only when the originating client requests the floor.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.6.1.2 IWF emergency group call response
|
Table 10.6.1.2-1 describes the information flow IWF emergency group call response from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Table 10.6.1.2-1: IWF emergency group call response information elements
Information Element
Status
Description
MCPTT ID
M
The identity of the calling party
MCPTT group ID
M
The MCPTT group ID on which the call is to be conducted
Result
M
The IWF emergency group call request may be rejected.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.6.1.3 IWF imminent peril group call request
|
Table 10.6.1.3-1 describes the information flow IWF imminent peril group call request from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.6.1.3-1: IWF imminent peril group call request information elements
Information Element
Status
Description
MCPTT ID
M
The identity of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT group ID
M
The MCPTT group ID on which the call is to be conducted
Imminent peril indicator
M
Indicates that the group call request is an imminent peril call
Location
O
Location, if available
Implicit floor request
(see NOTE)
O
Indicates that the originating client requests the floor
NOTE: This element shall be included only when this information flow is from the client to the server and the originator requests the floor.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.6.1.4 IWF imminent peril group call response
|
Table 10.6.1.4-1 describes the information flow IWF imminent peril group call response from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.6.1.4-1: IWF imminent peril group call response information elements
Information Element
Status
Description
MCPTT ID
M
The identity of the calling party
MCPTT group ID
M
The MCPTT group ID on which the call is to be conducted
Result
M
The IWF imminent peril group call request may be rejected.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.6.1.5 IWF in-progress imminent peril group state cancel request
|
Table 10.6.1.5-1 describes the information flow IWF in-progress imminent peril group state cancel request from the MCPTT server to the IWF.
Table 10.6.1.5-1: IWF in-progress imminent peril group state cancel request information elements
Information Element
Status
Description
MCPTT ID
M
The identity of the cancelling party
MCPTT group ID
M
The MCPTT group ID on which the in-progress imminent peril state is to be cancelled
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.6.1.6 IWF in-progress imminent peril group state cancel response
|
Table 10.6.1.6-1 describes the information flow IWF in-progress imminent peril group state cancel response from the IWF to the MCPTT server.
Table 10.6.1.6-1: IWF in-progress imminent peril group state cancel response information elements
Information Element
Status
Description
MCPTT ID
M
The identity of the cancelling party
MCPTT group ID
M
The MCPTT group ID on which the in-progress imminent peril state is to be cancelled
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.6.1.7 IWF emergency alert request
|
Table 10.6.1.7-1 describes the information flow IWF emergency alert request from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.6.1.7-1: IWF emergency alert request information elements
Information Element
Status
Description
MCPTT ID
M
The identity of the alerting party
Functional alias
O
The functional alias of the calling party
MCPTT group ID
M
The MCPTT group ID with which the alert is associated
Organization name
O
The alerting MCPTT user's mission critical organization name.
Location
O
The alerting MCPTT client's location
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.6.1.8 IWF emergency alert response
|
Table 10.6.1.8-1 describes the information flow IWF emergency alert response from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.6.1.8-1: IWF emergency alert response information elements
Information Element
Status
Description
MCPTT ID
M
The identity of the alerting party
MCPTT group ID
M
The MCPTT group ID with which the alert is associated
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.6.1.9 IWF emergency alert cancel request
|
Table 10.6.1.9-1 describes the information flow IWF emergency alert cancel request from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.6.1.9-1: IWF emergency alert cancel request information elements
Information Element
Status
Description
MCPTT ID
M
MCPTT user identity of the cancelling party
MCPTT ID
(see NOTE)
O
MCPTT user identity whose emergency alert is to be cancelled
MCPTT group ID
M
The MCPTT group ID with which the alert is associated
Group's in-progress emergency alert cancel request
O
Requests cancellation of the in-progress emergency alert of the group
NOTE: This information shall be present if the message is requesting cancellation of another MCPTT user's alert. If not present, then the alert of the MCPTT ID of the cancelling party is being cancelled
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.6.1.10 IWF emergency alert cancel response
|
Table 10.6.1.10-1 describes the information flow IWF emergency alert cancel response from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.6.1.10-1: IWF emergency alert cancel response information elements
Information Element
Status
Description
MCPTT ID
M
The identity of the cancelling party
MCPTT group ID
M
The MCPTT group ID with which the alert is associated
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.6.1.11 IWF in-progress emergency group state cancel request
|
Table 10.6.1.11-1 describes the information flow IWF in-progress emergency group state cancel request from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.6.1.11-1: IWF in-progress emergency group state cancel request information elements
Information Element
Status
Description
MCPTT ID
M
The identity of the cancelling party
MCPTT group ID
M
The MCPTT group ID on which the MCPTT in-progress emergency state is to be cancelled.
Alert indicator
O
Indicates whether the emergency alert of the cancelling party is to be cancelled
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.6.1.12 IWF in-progress emergency group state cancel response
|
Table 10.6.1.12-1 describes the information flow IWF in-progress emergency group state cancel response from the MCPTT server to the IWF and from IWF to MCPTT server.
Table 10.6.1.12-1: IWF in-progress emergency group state cancel response information elements
Information Element
Status
Description
MCPTT ID
M
The identity of the cancelling party
MCPTT group ID
M
The MCPTT group ID on which the MCPTT in-progress emergency in-progress is to be cancelled.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.6.2 Emergency calls
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.6.2.1 General
|
This subclause addresses various aspects of emergency call interworking.
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 emergency group call request / IWF in-progress emergency group state cancel request message is sent to the IWF at the commencement / release of an emergency 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 emergency group call request / IWF in-progress emergency group state 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 emergency group call request / IWF in-progress emergency group state cancel request messages to the IWF for all affiliated MCPTT group members in accordance with primary and partner MCPTT system behaviour.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.6.2.2 Emergency group call
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.6.2.2.1 Emergency group call setup initiated by a user in the LMR system on an interworking group defined in the MCPTT system
|
Figure 10.6.2.2.1‑1 shows the procedure for an emergency group call setup initiated by a user in the LMR system. The figure is based upon the figure for emergency calls in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.1. This scenario assumes that the group is an interworking group defined in 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 emergency interworking call procedures reuse the information flows defined 3GPP TS 23.379 [7].
Pre-conditions:
1. The MCPTT group is an interworking group defined in the MCPTT system
2. MCPTT client 1 and MCPTT client 2 are affiliated to that MCPTT group.
3. The IWF is connected to and is authorized to interwork with the MCPTT system.
4. The mapping relationship of group and user identities between MCPTT system and LMR system has been configured at the IWF.
5. LMR user initiates an emergency group call.
Figure 10.6.2.2.1-1: Emergency group call setup, initiated by LMR user on an interworking group defined in the MCPTT system
1. The IWF sends an IWF emergency group call request including a MCPTT group ID to the MCPTT server. The request contains an indication of the MCPTT emergency. The IWF may indicate in its request that an MCPTT emergency alert is to be sent when initiating an MCPTT emergency group call. The request may contain an indication of an implicit floor request.
2. The MCPTT server implicitly affiliates the MCPTT ID of the LMR user to the MCPTT emergency group if the user is 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 instead of an individual MC service ID.
3. The MCPTT server checks whether the MCPTT ID of the LMR user is authorized for initiation of MCPTT emergency calls on the indicated MCPTT group. If authorized, it resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status.
4. The MCPTT server configures the priority of the underlying bearers for all MCPTT participants in the MCPTT group. All successive calls during the MCPTT group's in-progress emergency state will receive the adjusted bearer priority.
5. The MCPTT server records the emergency state of the group. Once an MCPTT emergency call has been initiated, the MCPTT group is in an in-progress emergency state until that state is cancelled.
NOTE 3: The IWF actions for priority are out of scope of the present document.
6. MCPTT server sends the MCPTT emergency group call request towards the MCPTT clients of each of those affiliated MCPTT group members as defined in 3GPP TS 23.379 [7].
7. 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 emergency group call request is sent (to the IWF) for each affiliated LMR user.
8. The IWF returns IWF emergency group call response(s) to the MCPTT server.
9. The MCPTT server sends the IWF emergency group call response to the IWF (as a response to the request received in step 1) to inform of the successful MCPTT emergency group call establishment.
NOTE 4: How the LMR group members are called within the LMR system is out scope of the present document.
NOTE 5: Step 9 can occur at any time following step 5, but at the latest following step 8 depending on the conditions to proceed with the call.
10. The LMR users via the IWF and the affiliated MCPTTs have successfully established 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.2.2.2 Emergency group call setup initiated by a user in the MCPTT system on an interworking group defined in MCPTT system
|
Figure 10.6.2.2.2‑1 shows the procedure for an emergency group call setup initiated by a user in the MCPTT system. The figure is based upon the figure for 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 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 emergency interworking group call procedures reuse the information flows defined 3GPP TS 23.379 [7].
Pre-conditions:
1. The MCPTT group is an interworking group defined in the MCPTT system.
2. MCPTT client 2 is affiliated to the MCPTT group.
3. The IWF is connected to and is authorized to interwork with the MCPTT system.
4. The mapping relationship of group and user identities between MCPTT system and LMR system has been configured at the IWF.
5. The initiating MCPTT client 1 has been provisioned with the MCPTT group that has been designated via provisioning as the MCPTT emergency group.
NOTE 3: Alternatively, the client could have been provisioned for emergency behaviour on the selected group.
Figure 10.6.2.2.2-1: Emergency group call setup, initiated by MCPTT user on an interworking group defined in the MCPTT system
1. An MCPTT user initiates an emergency group call. MCPTT client 1 sets its MCPTT emergency state. The MCPTT emergency state is retained until explicitly cancelled.
2. The MCPTT client sends an MCPTT emergency group call request to the MCPTT server. The request contains an indication of the MCPTT emergency. The MCPTT client may indicate in its request that an MCPTT emergency alert is to be sent when initiating an MCPTT emergency group call. The request may contain an indication of an implicit floor request.
3. The MCPTT server implicitly affiliates MCPTT client 1 to the emergency group if the client is not already affiliated.
4. The MCPTT server checks whether the MCPTT user of the MCPTT client 1 is authorized for initiation of MCPTT emergency calls on the indicated interworking group. If authorized, it resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status.
5. The MCPTT server configures the priority of the underlying bearers for all participants in the MCPTT group.
NOTE 4: Successive calls during the group's in-progress emergency state will all receive the adjusted bearer priority.
6. The MCPTT server records the in-progress emergency state of the group. The MCPTT server also records the identity of the MCPTT user that initiated the MCPTT emergency group call until the MCPTT emergency is cancelled. Once an MCPTT emergency group call has been initiated, the MCPTT group is considered to be in an in-progress emergency state until that state is cancelled.
7. The MCPTT server sends an IWF emergency group call request to IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF emergency 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 emergency group call request is sent (to the IWF) for each affiliated LMR user.
8. IWF responds with the IWF emergency group call response(s) to MCPTT server to inform of the successful MCPTT emergency call establishment.
NOTE 5: How the LMR group members are called within the LMR system is out of scope of the present document.
NOTE 6: Steps 7 to 8 can occur at any time between steps 5 and 10.
NOTE 7: IWF actions for priority are out of scope of the present document.
9. The MCPTT server sends the MCPTT emergency group call request towards the MCPTT clients of each of those affiliated MCPTT group members as defined in 3GPP TS 23.379 [7].
10. The MCPTT server sends an MCPTT emergency group call response to the MCPTT client to inform of the successful MCPTT emergency call establishment.
NOTE 8: Step 10 can occur at any time following step 8, but at the latest following step 9, depending on the conditions to proceed with the call.
11. The LMR users via the IWF and the affiliated MCPTT clients have successfully established 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.2.2.3 Emergency group call setup initiated by a user in the LMR system on an interworking group defined in the LMR system
|
Figure 10.6.2.2.3‑1 shows the procedure for an emergency group call setup initiated by a user in the LMR system. The figure is based upon the figure for 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.
NOTE 1: The emergency interworking group call procedures reuse the information flows defined 3GPP TS 23.379 [7].
Pre-conditions:
1. The MCPTT group is an interworking group defined in the LMR system.
2. MCPTT client 1 and MCPTT client 2 are affiliated to that group.
3. The IWF is connected to and is authorized to interwork with the MCPTT system.
4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
5. LMR user initiates an emergency group call.
Figure 10.6.2.2.3-1: Emergency group call setup, initiated by LMR user on an interworking group defined in the LMR system
1. The IWF sends an IWF emergency group call request(s) to the MCPTT server. An emergency group call request is sent individually for each affiliated MCPTT user in the group. The request contains an indication of the MCPTT emergency.
NOTE 2: IWF actions for priority are out of scope of the present document.
2. The MCPTT server configures the priority of the underlying bearers and sends the MCPTT emergency group call request(s) as defined in 3GPP TS 23.379 [7].
NOTE 3: Successive calls during the MCPTT group's in-progress emergency state will all receive the adjusted bearer priority.
3. The MCPTT clients respond with MCPTT emergency group call response to the MCPTT server.
4. The MCPTT server sends the IWF emergency group call response(s) to the IWF to inform of the successful MCPTT emergency call establishment.
NOTE 4: How the LMR group members are called within the LMR system is out of scope of the present document.
5. The LMR users via the IWF and the affiliated MCPTT clients have successfully established media plane for communication. The LMR system where the interworking group is defined is the controlling system of the group call.
|
206be7a57129464f73be1aa9d853095b
|
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.
NOTE 1: The emergency interworking group call procedures reuse the information flows defined 3GPP TS 23.379 [7].
Pre-conditions:
1. The MCPTT group is an interworking group defined in the LMR system.
2. MCPTT client 2 is affiliated to the MCPTT group.
3. The IWF is connected to and is authorized to interwork with the MCPTT system.
4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
Figure 10.6.2.2.4-1: Emergency group call setup, initiated by MCPTT user to an interworking group defined in the LMR system
1. An MCPTT user initiates an emergency group call.
2. The MCPTT client sends an MCPTT emergency group call request to the MCPTT server. The request contains an indication of the MCPTT emergency. The MCPTT client may indicate in its request that an MCPTT emergency alert is to be sent when initiating an MCPTT emergency group call. The request may contain an indication of an implicit floor request.
3. The MCPTT server configures the priority of the underlying bearer and sends an IWF emergency group call request to the IWF.
4. The IWF sends an individual IWF emergency group call request to the MCPTT server for each affiliated MCPTT group member, in this example to a user in MCPTT client 2.
NOTE 2: How the LMR group members are called within the LMR system is outside the scope of the present document.
NOTE 3: All successive calls during the MCPTT group's in-progress emergency state will receive the adjusted bearer priority.
NOTE 4: IWF actions for priority are out of scope of the present document.
5. The MCPTT server configures the priority of the underlying bearer and sends an MCPTT emergency group call request towards the MCPTT clients as defined in 3GPP TS 23.379 [7].
6. The MCPTT client responds with MCPTT emergency group call response, as defined in 3GPP TS 23.379 [7].
7. The MCPTT server responds to the IWF emergency group call request(s), received in step 4, with IWF emergency group call response(s).
8. The IWF sends an IWF emergency group call response to the MCPTT server, as a response to the request received in step 3, to inform of the successful MCPTT emergency group call establishment.
9. The MCPTT server sends MCPTT emergency group call response to the initiating user in MCPTT client 1.
NOTE 5: Step 8 can occur at any time following step 3, but at the latest following step 7.
10. The LMR users (via the IWF) and the affiliated MCPTT clients have successfully established media plane for communication. The LMR system where the interworking group is defined is the controlling system of the group call.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.6.2.3 In-progress emergency group state cancel of an interworking group
| |
206be7a57129464f73be1aa9d853095b
|
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 user home MCPTT server and a group hosting MCPTT server.
NOTE 2: The information flows between MCPTT client and MCPTT server are defined 3GPP TS 23.379 [7].
NOTE 3: The end of an MCPTT emergency group call does not cancel the MCPTT group's in-progress emergency group state. It is explicitly cancelled by an authorized user by this procedure.
Pre-conditions:
1. The MCPTT group is in an in-progress emergency group state.
2. The MCPTT group is an interworking group defined in the MCPTT system.
3. The MCPTT client is affiliated to the MCPTT group.
4. The IWF is connected to and is authorized to interwork with 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. An LMR user initiates in-progress emergency group state cancel of an interworking group.
Figure 10.6.2.3.1-1: LMR user initiated in-progress emergency group state cancel of an interworking group defined in the MCPTT system
1. The IWF sends an IWF in-progress emergency group state cancel request to the MCPTT server. The IWF in-progress emergency group state cancel request may carry an indication that the emergency alert of the user is also being cancelled.
2. The MCPTT server checks that the initiator of the request is authorized to cancel the in-progress emergency group state of the group.
3. The MCPTT server cancels the in-progress emergency group state of the MCPTT group. If the emergency alert of the user is also requested to be cancelled, the MCPTT server cancels the emergency alert of the user.
4. The MCPTT server adjusts the priority of the underlying bearer; priority treatment is no longer required.
5. The MCPTT server handles the MCPTT in-progress emergency group state cancel request towards the affiliated MCPTT clients as defined in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3.
6. The MCPTT server sends an IWF in-progress emergency group state cancel response to the IWF to confirm the IWF in-progress emergency group state cancel request.
NOTE 4: Step 6 can occur at any time following step 3.
|
206be7a57129464f73be1aa9d853095b
|
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 user home MCPTT server and a group hosting MCPTT server.
NOTE 2: The information flows between an MCPTT client and an MCPTT server are defined 3GPP TS 23.379 [7].
NOTE 3: The end of the MCPTT emergency group call does not cancel the MCPTT group's in-progress emergency group state. It is explicitly cancelled by an authorized user by this procedure.
Pre-conditions:
1. MCPTT group is in an in-progress emergency group state.
2. The MCPTT group is an interworking group defined in the MCPTT system.
3. MCPTT client 2 is affiliated to that MCPTT group.
4. The IWF is connected to and is authorized to interwork with 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.
Figure 10.6.2.3.2-1: MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in MCPTT system
1. The MC user of MCPTT client 1 initiates in-progress emergency group state cancel of an interworking group.
2. The MCPTT client sends an MCPTT in-progress emergency group state cancel request to the MCPTT server. The request may carry an indication that the emergency alert of the user is also being cancelled.
3. The MCPTT server checks that the initiator of the request is authorised to cancel the in-progress emergency group state of the group.
4. The MCPTT server cancels the in-progress emergency group state of the MCPTT group. If the emergency alert of the user is also requested to be cancelled, the MCPTT server cancels the emergency alert of the user.
5. The MCPTT server adjusts the priority of the underlying bearer; priority treatment is no longer required.
6. The MCPTT server sends the IWF in-progress emergency group state cancel request to the IWF.
NOTE 4: IWF actions for cancelling in-progress emergency group state are out of scope of the present document.
7. The IWF sends the IWF in-progress emergency group state cancel response to the MCPTT server to confirm the IWF in-progress emergency group state cancel request.
8. The MCPTT server handles the MCPTT in-progress emergency group state cancel request towards the affiliated MCPTT clients as defined in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3.
9. The MCPTT server sends the MCPTT in-progress emergency group state cancel response to the MCPTT client 1 to confirm the MCPTT in-progress emergency group state cancel request.
NOTE 5: Step 9 can occur at any time following step 4, depending on the conditions to proceed with the call.
|
206be7a57129464f73be1aa9d853095b
|
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 group state. It is explicitly cancelled by an authorized user by this procedure.
Pre-conditions:
1. MCPTT group is in an in-progress emergency group state.
2. The MCPTT group is an interworking group defined in the LMR system.
3. The MCPTT client is affiliated to the MCPTT group.
4. The IWF is connected to and is authorized to interwork with 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. An LMR user initiates in-progress emergency group state cancel of an interworking group.
Figure 10.6.2.3.3-1: LMR user initiated in-progress emergency group state cancel of an interworking group defined in the LMR system
1. The IWF sends an IWF in-progress emergency group state cancel request to the MCPTT server.
2. The MCPTT server adjusts the priority of the underlying bearer; priority treatment is no longer required.
3. The MCPTT server handles the MCPTT in-progress emergency group state cancel request towards the affiliated MCPTT clients as defined in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3.
4. The MCPTT server sends an IWF in-progress emergency group state cancel response to the IWF to confirm the IWF in-progress emergency group state cancel request.
NOTE 3: Step 4 can occur at any time following step 1, depending on the conditions to proceed with the call.
|
206be7a57129464f73be1aa9d853095b
|
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 server are defined 3GPP TS 23.379 [7].
NOTE 2: The end of the MCPTT emergency group call does not cancel the MCPTT group's in-progress emergency group state. It is explicitly cancelled by an authorized user by this procedure.
Pre-conditions:
1. MCPTT group is in an in-progress emergency group state.
2. The MCPTT group is an interworking group defined in the LMR system.
3. MCPTT client 2 is affiliated to that MCPTT group.
4. The IWF is connected to and is authorized to interwork with 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.
Figure 10.6.2.3.4-1: MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in the LMR system
1. The MC user of MCPTT client 1 initiates in-progress emergency group state cancel of an interworking group.
2. An MCPTT client sends an MCPTT in-progress emergency group state cancel request to the MCPTT server. The request may carry an indication that the emergency alert of the user is also being cancelled.
3. The MCPTT server sends the IWF in-progress emergency group state cancel request to the IWF.
NOTE 3: IWF actions for checking authorization and cancelling in-progress emergency group state are out of scope of the present document.
NOTE 4: The LMR system can also reject the request.
4. The IWF sends the IWF in-progress emergency group state cancel response to the MCPTT server to confirm the IWF in-progress emergency group state cancel request.
5. The MCPTT server adjusts the priority of the underlying bearer; priority treatment is no longer required.
6. The MCPTT server handles the MCPTT in-progress emergency group state cancel request towards the affiliated MCPTT clients as defined in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3.
7. The MCPTT server sends the MCPTT in-progress emergency group state cancel response to the MCPTT client 1 to confirm the MCPTT in-progress emergency group state cancel request.
NOTE 5: Step 7 can occur at any time following step 4, depending on the conditions to proceed with the call.
|
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
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 is raised. From the perspective of the MCPTT system, all emergency behavior by the IWF on behalf of its users mapped to MCPTT shall comply with behaviors defined in 3GPP TS 23.379 [7]. The implementation shall ensure that emergency related parameters of a group or private call are adhered to. For example, an MC service group must be configured in the MC sevice group managment system for emergency alerts in order for an emergency alert to be sent on it. This can be enforced through proper configuration of both LMR and MCPTT systems or can be enforced at run time by the IWF.
|
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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.