hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.3.7 Late Entry
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.3.7.1 General
|
Late Entry for an ongoing interworking group call is triggered by a successful group affiliation procedure from the participating system.
NOTE: These procedures apply to all types of group calls, including, for example, emergency call, imminent peril call and broadcast call.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.3.7.2 Group call late entry on an interworking group defined in the MCPTT system
|
In this procedure, the group affiliation from IWF triggers a late entry procedure in the MCPTT system. The signalling procedure is described in figure 10.3.3.7.2-1.
For the first affiliating LMR user, this procedure is applicable for both IWF affiliation options (see subclauses 10.1.2.1 and 10.3.1). For the following LMR users affiliating to the same group, this procedure is triggered only if the IWF passes through individual affiliations for each group member.
This subclause is based upon subclauses in 3GPP TS 23.379 [7] for:
- Late entry for pre-arranged group call, subclause 10.6.2.3.1.1.4, and
- Group call for an MCPTT group defined in partner MCPTT system, subclause 10.6.2.4.3.1.
Pre-conditions:
1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the MCPTT system.
2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
3. There is an on-going group call in the interworking group involving MCPTT clients 1 and 2.
4. First LMR user affiliates to the interworking group.
NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.3.3.7.2-1: Group call late entry on an interworking group defined in the MCPTT system
1. The IWF triggers a group affiliation towards the MCPTT server (see subclause 10.1.2.2).
2. The MCPTT server initiates a group call late entry for an interworking group.
3. The MCPTT server sends an IWF group call request to the IWF.
NOTE 2: How the IWF delivers the group call request to the LMR system is out of the scope of the present document.
4. The IWF confirms the group call request by sending IWF group call response to the MCPTT server.
5. The IWF (and the LMR user) is successfully added to the ongoing group call and MCPTT users at MCPTT client 1 and MCPTT client 2 may be notified about the LMR user joining the group call.
6. If the floor has been granted to another user, the MCPTT server sends a IWF floor taken (6a) to the IWF. If the floor is not granted to any party, an IWF floor idle (6b) is sent to the IWF.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.3.7.3 Group call late entry on an interworking group defined in the LMR system
|
In this procedure, the group affiliation from MCPTT system triggers a late entry procedure in the LMR system. The signalling procedure is described in figure 10.3.3.7.3-1.
This procedure describes the affiliation and late entry of the first MCPTT user into the interworking group, but it is applicable also for all subsequent MCPTT users' affiliations to the same group.
This subclause is based upon subclauses in 3GPP TS 23.379 [7] for:
- Late entry pre-arranged group call, subclause 10.6.2.3.1.1.4, and
- Group call setup involving groups from multiple MCPTT systems, subclause 10.6.2.4.1.1.
Pre-conditions:
1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system.
2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
3. There is an on-going group call in the interworking group, involving only LMR users.
NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.3.3.7.3-1: Group call late entry on an interworking group defined in the LMR system
1. MCPTT user (client 1) affiliates to the group (see subclause 10.1.2.4).
NOTE 2: How the IWF delivers the affiliation to LMR system and how the LMR system handles the late entry is out of scope of the present document.
2. The IWF sends an IWF group call request to the MCPTT server.
3. The MCPTT server triggers a group call setup procedure for the newly affiliated user in MCPTT client 1, as described in 3GPP TS 23.379 [7].
4. The MCPTT server confirms the successful establishment of the group call by sending IWF group call response to the IWF. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF.
5. MCPTT client 1 is successfully added to the ongoing group call.
6. If the floor has been granted to another user, the IWF sends an IWF floor taken (6a) to the MCPTT server. If the floor is not granted to any party, an IWF floor idle (6b) is sent.
7. The MCPTT server sends Floor taken (7a) or Floor idle (7b) to the newly affiliated user in MCPTT client 1, as described in 3GPP TS 23.379 [7].
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.3.8 Interworking group call release
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.3.8.1 General
|
The procedures in this subclause define the cases where the group host server releases an ongoing interworking group call for all the participants of that group.
If the group host server is an MCPTT server, the release conditions are described in 3GPP TS 23.379 [7], subclause 10.6.2.4.1.2.
If the group host server is an LMR system, represented by an IWF, the release conditions are outside the scope of the present document.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.3.8.2 Group call release on an interworking group defined in the MCPTT system
|
In this procedure, the MCPTT system is releasing a group call on an interworking group defined in the MCPTT system. The signalling procedure is described in figure 10.3.3.8.2-1.
This subclause is based upon subclause 10.6.2.4.1.2 Group call release in 3GPP TS 23.379 [7].
Pre-conditions:
1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the MCPTT system.
2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
3. There is an on-going group call involving the IWF and MCPTT clients 1 and 2.
NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.3.3.8.2-1: Group call release initiated by MCPTT system on an interworking group
1. The MCPTT server initiates a group call release on an interworking group.
NOTE 2: The MCPTT server may decide to release the group call for different reasons, see subclause 10.6.2.4.1.2 in 3GPP TS 23.379 [7].
2. The MCPTT server identifies the participants of the ongoing group call, at least one of them being an LMR user, represented by an IWF.
3. The MCPTT server sends IWF group call release request(s) to the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group call release request message is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group call release request is sent (to the IWF) for each affiliated LMR user.
NOTE 3: How the group call release request(s) is(are) forwarded to the LMR system is out of scope of the present document.
4. The MCPTT server sends the (MCPTT) group call release request(s) to the group's MCPTT users, as described in 3GPP TS 23.379 [7].
NOTE 4: Steps 3 and 4 can occur in any order.
5. The IWF confirms the IWF group call release request(s) received in step 3 by IWF group call release response(s) to the MCPTT server.
6. The MCPTT client 1, client 2 and the IWF have successfully released the floor control and media plane resources associated with the group call that is released.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.3.8.3 Group call release on an interworking group defined in the LMR system
|
In this procedure, the LMR system is releasing a group call on an interworking group defined in the LMR system. The signalling procedure is described in figure 10.3.3.8.3-1.
This subclause is based upon subclause 10.6.2.4.1.2 Group call release in 3GPP TS 23.379 [7].
Pre-conditions:
1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system.
2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
3. There is an on-going group call involving the IWF and MCPTT clients 1 and 2.
4. The LMR system initiates release of the group call.
NOTE 1: The reasons for the LMR system's decision to release the group call are out of scope of the present document.
NOTE 2: 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.3.3.8.3-1: Group call release initiated by LMR system on an interworking group defined in the LMR system
1. The IWF sends IWF group call release requests to the MCPTT server. An individual IWF group call release request is sent for each MCPTT user in the call.
2. The MCPTT server forwards the release requests to the group's MCPTT users (in this example to users in MCPTT clients 1 and 2), as described in 3GPP TS 23.379 [7].
3. The MCPTT clients respond with group call release response(s).
4. The MCPTT server confirms the IWF group call release requests received in step 1 by IWF group call release responses to the IWF.
5. The MCPTT client 1, client 2 and the IWF have successfully released the floor control and media plane resources associated with the group call that is released.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.4 Group broadcast
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.4.1 General
|
A broadcast group call is a special group call where the initiating user expects no response from the receiving users so that when the transmission is complete, so is the call. The initiating user can be an MCPTT user or can be an LMR user.
The group-broadcast group is defined as a set of groups, not a set of users. The user that originates the group-broadcast group call is the only one transmitting media during this call.
The group-broadcast group is defined with a hierarchy. For example, groups A and B may be subordinate to a group-broadcast group. All subordinate groups belonging to a group-broadcast group are defined either in the MCPTT system or the LMR system.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.4.2 Group-broadcast group call procedure with an interworking group where the group-broadcast group is defined in the MCPTT system
|
3GPP TS 23.379 [7], subclause 10.6.2.5.2.1 describes the procedure for a group-broadcast group call within a single MCPTT system. The present procedure describes a group-broadcast group call that includes the IWF.
In this procedure, the MCPTT server is initiating the broadcast and is the owner of the group-broadcast group.
The procedure shows the case where the call is initiated by a MCPTT user. However, if the override feature is enabled, then the call originator may be overridden.
Figure 10.3.4.2-1 illustrates the procedure for group-broadcast group call establishment (the group-broadcast group is defined in the MCPTT system).
Pre-conditions:
1. The group (e.g. A) to which MCPTT client 2 and the IWF are members is a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group A as a subordinate group).
2. The group (e.g. A) currently has an on-going MCPTT group call that is not an MCPTT emergency group call.
3. The call initiator of the group-broadcast group is a member of another group (e.g., X, not group A) which is also a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group X as a subordinate group).
4. The group-broadcast group and its subordinate groups are defined in the same group management server and served by the same MCPTT server.
Figure 10.3.4.2-1: Group-broadcast group call involving IWF (group-broadcast group is defined in the MCPTT system)
1. MCPTT user at MCPTT client 1 initiates the group-broadcast group call setup procedure.
2. The MCPTT client 1 sends a group-broadcast group call request to the MCPTT server.
3. The MCPTT server needs to resolve the group-broadcast group ID into its subordinate groups in order to contact the affiliated MCPTT users of those subordinate groups.
4. The MCPTT server then needs to consider any on-going group calls on those subordinate groups because this may affect the behaviour for what happens next. In this case a group call exists on a subordinate group. Thus, the MCPTT users involved in the group call on this subordinate group.
5. The MCPTT server performs group call release procedures of groups defined in the MCPTT system as described in subclause 10.3.3.8.2.
6. A group-broadcast group call request is sent to MCPTT client 2 and an IWF group-broadcast group call request to the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group-broadcast group call request is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group-broadcast group call request is sent (to the IWF) for each affiliated LMR user.
NOTE 1: How the group-broadcast group call request(s) is(are) forwarded to the LMR system is out of scope of the present document.
7. MCPTT client 2 is notified of the incoming group-broadcast group call.
NOTE 2: How LMR user(s) is(are) notified of the incoming group-broadcast group call is outside the scope of the present document.
8. MCPTT client 2 and the IWF respond to the IWF group-broadcast group call request by sending an IWF group-broadcast group call response. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group-broadcast group call response is sent to the MCPTT server. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group-broadcast group call response is sent (to the MCPTT server) for each affiliated LMR user.
9. The MCPTT server responds to MCPTT client 1 (the call initiator) that the group-broadcast group call has been established by sending a group-broadcast group call response.
10. The MCPTT client 1 notifies its user that the user can begin transmitting using the group-broadcast group call resources.
Once the user of MCPTT cleint 1 completes transmitting, the group-broadcast group call is released.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.4.3 Group-broadcast group call procedure with an interworking group where the group-broadcast group is defined in the LMR system
|
3GPP TS 23.379 [7], subclause 10.6.2.5.2.1 describes the procedure for a group-broadcast group call within a single MCPTT system. The present procedure describes a group-broadcast group call that includes the IWF.
In this procedure, the IWF is the owner of the group-broadcast group and is initiating the group-broadcast group call.
The procedure only shows the case where the call is initiated by a MCPTT user. However, if the override feature is enabled, then the call originator may be overridden.
Figure 10.3.4.3-1 illustrates the procedure for group-broadcast group call establishment (the group-broadcast group is defined in the LMR system).
Pre-conditions:
1. The group (e.g. A) to which MCPTT client 2 is a member is a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group A as a subordinate group).
2. The group (e.g. A) currently has an on-going MCPTT group call that is not an MCPTT emergency group call.
3. The call initiator, MCPTT client 1, of the group-broadcast group is a member of another group (e.g., X, not group A) which is also a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group X as a subordinate group).
4. The group-broadcast group and its subordinate groups are defined in the IWF.
Figure 10.3.4.3-1: Group-broadcast group call involving IWF (group-broadcast group defined in the LMR system)
1. MCPTT user at MCPTT client 1 initiates the group-broadcast group call setup procedure.
2. The MCPTT client 1 sends a group-broadcast group call request to the MCPTT server.
3. As the group-broadcast group is defined in the LMR system the MCPTT server sends an IWF group-broadcast group call setup request to the IWF.
4. The IWF performs group call release procedures of groups defined in the LMR system as described in subclause 10.3.3.8.3.
5. The IWF issues a group-broadcast group call setup request to establish the group-broadcast call.
6. The MCPTT user of MCPTT client 2 is notified.
NOTE: How LMR user(s) is(are) notified of the incoming group-broadcast group call is outside the scope of the present document.
7. Optionally, MCPTT client 2 respond with a group-broadcast group call response to the MCPTT server and then to the IWF.
8. The MCPTT server responds to MCPTT client 1 (the call initiator) that the group-broadcast group call has been established by sending a group-broadcast group call response.
9. The MCPTT client 1 notifies its user that the user can begin transmitting using the group-broadcast group call resources.
Once the user of MCPTT client 1 completes transmitting, the group-broadcast group call is released.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.4.4 Group-broadcast group call release with an interworking group procedure where the group-broadcast group is defined in the MCPTT system
|
When the call originator has completed transmitting, the group-broadcast group call is ended and the resources are released.
Figure 10.3.4.4-1 illustrates the procedure for group-broadcast group call release (the group-broadcast group is defined in the MCPTT system).
Pre-conditions:
1. An on-going group-broadcast group call involving MCPTT client 1, the MCPTT client 2 and the IWF exists.
Figure 10.3.4.4-1: Group-broadcast group call transmission ended (group-broadcast group is defined in the MCPTT system)
1. MCPTT user on MCPTT client 1 finished transmitting.
2. A group-broadcast group call release request is sent to the MCPTT server of the group-broadcast group.
3. The MCPTT users of MCPTT client 2 and the IWF of the group-broadcast group's subordinate groups are sent a group-broadcast group call release request. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group-broadcast group call release request is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group-broadcast group call request is sent (to the IWF) for each affiliated LMR user.
4. MCPTT client 2 and the IWF notify their users that the group-broadcast group call has ended.
NOTE: How LMR user(s) is(are) notified that the group-broadcast group call has ended is outside the scope of the present document.
5. MCPTT client 2 and the IWF respond to confirm the release of the group-broadcast group call by sending a group-broadcast group call release response. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group-broadcast group call release response is sent to the MCPTT server. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group-broadcast group call response is sent (to the MCPTT server) for each affiliated LMR user.
6. The MCPTT server sends a group-broadcast group call release response indicating to the initiator that the call is now ended.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.4.5 Group-broadcast group call release with an interworking group procedure where the group-broadcast group is defined in the LMR system
|
When the call originator has completed transmitting, the group-broadcast group call is ended and the resources are released.
Figure 10.3.4.5-1 illustrates the procedure for group-broadcast group call release (the group-broadcast group defined in the LMR system).
Pre-conditions:
1. An on-going group-broadcast group call involving MCPTT client 1, the MCPTT client 2 and the IWF exists.
Figure 10.3.4.5-1: Group-broadcast group call transmission ended (group-broadcast group defined in the LMR system)
1. The MCPTT user on MCPTT client 1 finished transmitting.
2. A group-broadcast group call release request is sent to the MCPTT server.
3. As the group-broadcast group is defined in the LMR system the MCPTT server sends an IWF group-broadcast group call release request to the IWF.
4. The IWF sends an IWF group-broadcast group call release request to the MCPTT server hosting client 2. The MCPTT server sends the group-broadcast group call release request to MCPTT client 2.
5. MCPTT client 2 is notified that the group-broadcast group call has ended.
NOTE: How LMR user(s) is(are) notified that the group-broadcast group call has ended is outside the scope of the present document.
6. MCPTT client 2 responds to confirm the release of the group-broadcast group call by sending a group-broadcast group call release response.
7. The MCPTT server sends an IWF group-broadcast group call release response to the IWF. The IWF becomes aware that MCPTT client 2 has confirmed the group-broadcast group call release and replies with another IWF group-broadcast group call release response back to the MCPTT server to trigger step 8.
8. The MCPTT server sends a group-broadcast group call release response indicating to the initiator that the group-broadcast group call is now ended.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.4.6 Broadcast group regroup call using pre-configured group
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.4.6.1 General
|
The temporary group created using a pre-configured group can be a broadcast group or a non-broadcast group.
A broadcast group regroup call using pre-configured groups can be achieved by first regrouping users into a pre-configured group regroup, making the broadcast group call on the pre-configured group, and then cancelling the pre-configured group regroup.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.4.6.2 Broadcast group regroup call using pre-configured group the MCPTT system
|
The broadcast group regroup call procedure using pre-configured group allows an authorized MCPTT user to initiate a broadcast call to a set of MCPTT groups, which are regrouped only for the duration of the broadcast call. The regroup is cancelled at the end of the broadcast call to prevent users from talking back on the pre-configured group regroup. This procedure requires that the authorized MCPTT user is a group member of at least one of the MCPTT groups included in the regroup operation.
Figure 10.3.4.6.2‑1 illustrates the procedure to initiate a broadcast group regroup call using a pre-configured MCPTT regroup group owned by the MCPTT system. For simplicity, no receiving clients are shown.
Pre-conditions:
- The MCPTT client is registered with the MCPTT service.
- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in the MCPTT client and the IWF. The MCPTT client and the IWF have received the relevant security related information to allow them to communicate in the pre-configured group regroup.
- The MCPTT client is authorized to initiate a pre-configured group regroup using the pre-configured group regroup procedure.
- The MCPTT client is aware of a suitable pre-configured group whose configuration has been pre-configured in the IWF and the MC service UEs of the MCPTT users who will be regrouped.
- The MCPTT client is affiliated to group 1.
- The IWF is affiliated to one or more of MCPTT group 1, 2 or 3.
- The pre-configured group regroup is homed in the MCPTT server.
- The IWF is home to at least one group that's a constituent group of the pre-configured group regroup.
Figure 10.3.4.6.2-1: Broadcast group regroup call using pre-configured group in the MCPTT system
1. The authorized user of the MCPTT client initiates the pre-configured group regroup formation procedure using pre-configured groups as specified in subclause 10.3.7.1. MCPTT groups 1, 2, and 3 are regrouped into group 4.
2. The MCPTT user at the MCPTT client performs the broadcast group call procedure as specified in subclause 10.3.4.
3. The MCPTT client initiates the pre-configured group regroup cancellation procedure using pre-configured groups as specified in subclause 10.3.7.1.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.4.6.3 Broadcast group regroup call using pre-configured group in the IWF
|
The broadcast group regroup call procedure using a pre-configured group allows an IWF user to initiate a broadcast call to a set of MCPTT groups, which are regrouped only for the duration of the broadcast call.
Figure 10.3.4.6.3-1 illustrates the procedure to initiate a broadcast group regroup call using a pre-configured group owned by the IWF.
Pre-conditions:
- MCPTT clients 1 and 2 are registered with the MCPTT service.
- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in MCPTT clients 1 and 2, and MCPTT clients 1 and 2 have received the relevant security related information to allow them to communicate in the pre-configured group regroup.
- MCPTT client 1 is affiliated to group 1, MCPTT client 2 is affiliated to group 2. Group 3 is used as the pre-configured group regroup.
- The pre-configured group regroup is homed in the IWF.
- The MCPTT server is home to at least one group that's a constituent group of the pre-configured group regroup.
Figure 10.3.4.6.3-1: Broadcast group regroup call using pre-configured group in the IWF
1. The IWF initiates the group regroup formation procedure using pre-configured groups as specified in subclause 10.3.7.1. MCPTT groups 1 and 2 are regrouped into group 3.
2. The IWF performs the broadcast group call procedure as specified in subclause 10.3.4.
3. The IWF initiates the pre-configured group regroup cancellation procedure using pre-configured groups as specified in subclause 10.3.7.1.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.5 Chat group call
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.5.1 General
|
This subclause is based upon subclause for chat group call in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.2. For LMR systems that do not support the concept of chat groups, the IWF might still adapt its calls to the MCPTT chat model.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.5.2 MCPTT user initiated chat group call in an interworking group defined in LMR system
|
In this procedure, an MCPTT user initiates a chat group call in an interworking group defined in the LMR system. The signalling procedure is described in figure 10.3.5.2-1.
Pre-conditions:
1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system.
2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
NOTE: 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.3.5.2-1: MCPTT user initiated chat group call in an interworking group defined in the LMR system
1. MCPTT user of the MCPTT client indicates to join the group communication for the group. The MCPTT client joins the group by sending a group join request to the MCPTT server. If there is a request to transmit, then the group join request contains an indication of an implicit floor request and the location of the joining party if required.
2. The MCPTT server inspects the Group join request for presence of location information of the calling party. If location information is included in the join request, 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 requesting MCPTT user to decide if the user's location information may be provided to other MCPTT users on the call and the IWF.
3. The MCPTT server notices that the interworking group is defined in the LMR system and forwards the group join request with or without location depending on the outcome of the privacy check as an IWF group join request to the IWF.
4. The IWF replies with an IWF group join response indicating the acceptance of the group join request and also returns the IWF selected media parameters for the chat group call in the IWF group join response.
5. The MCPTT server forwards the IWF group join response to the MCPTT client as a group join response.
6. If the MCPTT client requests to transmit, the MCPTT server establishes the media plane (if not already established) for the call.
7. Floor control will continue to be used by the floor participants associated with the MCPTT client and the IWF for the duration of the call. Media plane signalling using floor control will be used for subsequent calls for the group as long as one or more users are affiliated.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.5.3 LMR user initiated chat group call in an interworking group defined in MCPTT system
|
In this procedure, an LMR user initiates a chat group call in an interworking group defined in the MCPTT system. The signalling procedure is described in figure 10.3.5.3-1.
Pre-conditions:
1. The interworking group information is known at the IWF by configuration. The interworking group has been defined in the MCPTT system.
2. MCPTT user 1 and MCPTT user 2 have previously joined (affiliated) to the group.
3. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
4. LMR user initiates a join to the group.
NOTE: 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.3.5.3-1: LMR user initiated chat group call in an interworking group defined in the MCPTT system
1. The IWF sends an IWF group join request to the MCPTT server. The request to join may contain location information of the transmitting party. If there is a request to transmit, then the IWF group join request contains an indication of an implicit floor request and the location of the joining party if required.
2. The MCPTT server checks whether the MCPTT ID is authorized to affiliate to the group. MCPTT server generates an implicit affiliation if the MCPTT ID is not already affiliated to the group.
3. The MCPTT server replies with a group join response indicating the acceptance of the group join request and also returns the MCPTT server selected media parameters for the chat group call in the IWF group join response.
4. If the IWF requests to transmit, the MCPTT server establishes the media plane (if not already established) for the call.
5. Floor control will continue to be used by the floor participants associated with MCPTT client 1, MCPTT client 2 and the IWF for the duration of the call. Media plane signalling using floor control will be used for subsequent calls for the group as long as one or more users are affiliated.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.5.4 Release chat group call on an interworking group defined in the LMR system
|
This procedure describes the case where the LMR system releases an ongoing MCPTT chat group call on an interworking group defined in the LMR system, for all the participants of that group call. The signalling procedure is described in figure 10.3.5.4-1.
Pre-conditions:
1. A chat group call is ongoing involving an MCPTT client and the IWF.
2. The LMR system initiates release of the chat group call.
Figure 10.3.5.4-1: Release chat group call on an interworking group defined in the LMR system
1. The IWF sends an IWF group call release request to the MCPTT server. An individual IWF group call release request is sent for each MCPTT user in the call.
2. MCPTT server forwards the release request(s) to the group's MCPTT users, as described in 3GPP TS 23.379 [7].
3. MCPTT users are notified about the release of the group call.
4. Optionally, the MCPTT client confirms the group call release request received in step 2 with a group call release response to the MCPTT server.
5. The MCPTT server forwards the group call release response to the IWF as an IWF group call release response.
6. The MCPTT client and the IWF release the floor control and media plane resources associated with the chat group call that is released. Successful release of the chat group call does not affect the status of affiliation of any of the clients.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.5.5 Release chat group call on an interworking group defined in the MCPTT system
|
This procedure describes the case where the MCPTT server releases an ongoing MCPTT chat group call, on an interworking group defined in the MCPTT system, for all the participants of that group call, since at least one of the conditions for release are met e.g. due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or the number of affiliated MCPTT group members is below the minimum number permitted.
The signalling procedure is described in figure 10.3.5.5-1.
Pre-conditions:
1. A chat group call is ongoing involving MCPTT clients 1, 2 and the IWF.
Figure 10.3.5.5-1: Release chat group call on an interworking group defined in the MCPTT system
1. The MCPTT server decides to release the MCPTT chat group call which is ongoing e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCPTT group members are not present.
2. The MCPTT server sends an IWF group call release request to the IWF to release the ongoing session. If the IWF has joined itself to this group on behalf of all the group's LMR users, only one IWF group call release request message is sent to the IWF. If the MCPTT server has received individual joins from the group's LMR users, an individual IWF group call release request is sent to the IWF for each joined LMR user.
3. The MCPTT server sends a group call release request towards each MCPTT participant of the ongoing group call.
4. The MCPTT users are notified about the release of the group call.
5. The IWF confirms the IWF group call release request(s) received in step 2 by IWF group call release response(s) to the MCPTT server.
6. Optionally, the MCPTT client(s) receiving a group call release request may send a group call release response to the MCPTT server.
7. MCPTT client 1, client 2 and the IWF release the floor control and media plane resources associated with the chat group call that is released. Successful release of the chat group call does not affect the status of affiliation of any of the clients.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.5.6 Void
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.5.7 Void
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.5.8 Newly joined MCPTT group member of a group defined in the LMR system
|
Procedures in figure 10.3.5.8-1 are those for a group member entering an ongoing MCPTT group call, i.e. performing a late entry.
Pre-conditions:
1. The MCPTT client is registered and the MCPTT user has been authenticated and authorized to use the MCPTT service.
2. There is an ongoing group call on the group homed on the LMR system.
3. The MCPTT client has not yet joined the group call.
4. The MCPTT user indicates to join the group call.
Figure 10.3.5.8-1: Late entry of a newly joined MCPTT group member
1. The MCPTT client sends a group join request with the MCPTT group ID of the desired group to the MCPTT server. If there is a request to transmit, then the group joint request contains an indication of an implicit floor request.
2. The MCPTT server forwards the request to the IWF.
3. The IWF replies with a group join response indicating the acceptance of the group join request.
4. The MCPTT server forwards the response to the MCPTT client.
5. The IWF establishes the media plane with the MCPTT client.
6. The IWF may notify its users that an MCPTT user has joined the group.
7 a. The IWF sends an IWF floor taken (for the current talker) to the MCPTT server if the floor has been taken.
7b. The MCPTT responds to any incoming IWF floor taken message by forwarding a floor taken message to the MCPTT client.
8. Floor control will continue to be used by the floor participants.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.5.9 Newly joined LMR group member of a group defined in the MCPTT system
|
Procedures in figure 10.3.5.9-1 are those for the IWF entering an ongoing MCPTT group call, i.e. performing a late entry.
Pre-conditions:
1. MCPTT user 1 and MCPTT user 2 have previously joined to the group.
2. MCPTT users using MCPTT client 1 and MCPTT client 2 are in an ongoing group call.
3. The IWF has not yet joined the group call.
Figure 10.3.5.9-1: Late entry of a newly joined LMR group member
1. The IWF sends a group join request with the MCPTT group ID of the desired group and either using the MCPTT ID corresponding to the LMR group member or using the pre-configured MCPTT ID for use when the IWF is affiliating itself on behalf of the group's LMR users. If there is a request to transmit, then the group join request contains an indication of an implicit floor request. If the group join request includes an implicit floor request it may also include location information.
2. The MCPTT server receives the group join request. MCPTT server generates an implicit affiliation using the MCPTT ID used by the IWF (if the IWF or the LMR user is not already affiliated to the group) and verifies that IWF is authorized to affiliate to the group.
3. The MCPTT server replies with a group join response indicating the acceptance of the group join request.
4. The MCPTT server establishes the media plane between the IWF and the MCPTT server.
5. MCPTT users at MCPTT client 1 and MCPTT client 2 may be notified about the IWF joining the group call.
6. The MCPTT server sends a floor taken (for the current talker) to the IWF.
7. Floor control will continue to be used by the floor participants associated with MCPTT client 1, MCPTT client 2 and the IWF.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.5.10 MCPTT client returning to coverage on a group homed in the LMR system
|
Procedures in figure 10.3.5.10-1 are those for an MCPTT client returning to coverage during an ongoing MCPTT chat group call.
Pre-conditions:
1. The MCPTT user using an MCPTT client is in an ongoing chat group call when the MCPTT client goes out of radio coverage.
Figure 10.3.5.10-1: Late entry of a MCPTT client returning from out of coverage
1. The MCPTT client or MCPTT server detects that MCPTT client has returned to coverage.
NOTE: How the MCPTT client or MCPTT server detects that the client has returned to coverage is out of scope of the present document.
2. The media plane between the MCPTT client and the IWF are re-established using media plane control signalling
3a. The IWF sends an IWF floor taken to the MCPTT server if anyone currently has the floor.
3b. The MCPTT server forwards a floor taken message to the MC Client if anyone currently has the floor.
4. Floor control will continue to be used by the floor participants.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.6 Exiting group call due to de-affiliation
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.6.1 General
|
The following procedures are applicable both for the pre-arranged and chat group calls.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.6.2 Exiting group call defined in the LMR system due to de-affiliation
|
Procedures in figure 10.3.6.2-1 are the signalling control plane procedures for the IWF requesting a newly de-affiliated MCPTT user to leave an ongoing MCPTT group call.
Pre-conditions:
1. The MCPTT group is previously defined on the IWF with MCPTT users affiliated to that group. At least one user is an LMR user represented by an MCPTT ID.
2. An MCPTT user on the MCPTT client and an LMR user via the IWF, are on an ongoing call.
Figure 10.3.6.2-1: Exiting MCPTT group call due to de-affiliation
1. The MCPTT client is de-affiliated.
2. The IWF sends an IWF group call leave request to the MCPTT client via the MCPTT server.
3. The MCPTT server forwards the IWF group call leave request as a group call leave request to the MCPTT client.
4. The MCPTT user at the MCPTT client is notified about leaving the group call.
5. The MCPTT client sends the group call leave response to the MCPTT server and leaves the group call.
6. The MCPTT server forwards the group call leave response to the IWF as an IWF group call leave response.
7. The MCPTT client is now removed from the ongoing group call.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.6.3 Exiting group call defined in the MCPTT system due to de-affiliation
|
Procedures in figure 10.3.6.3-1 are the signalling control plane procedures for the MCPTT server requesting a newly de-affiliated LMR user to leave an ongoing MCPTT group call.
Pre-conditions:
1. The MCPTT group is previously defined on the group management server with MCPTT users affiliated to that group. At least one user is an LMR user represented by an MCPTT ID.
2. An MCPTT user on the MCPTT client and an LMR user via the IWF, are on an ongoing call.
Figure 10.3.6.3-1: Exiting MCPTT group call due to de-affiliation
1. The LMR user represented by the IWF has been de-affiliated.
2. The MCPTT server sends an IWF group call leave request to the LMR user via the IWF.
3. The IWF sends an IWF group call leave response to the MCPTT server and leaves the group call.
4. The LMR user represented by the IWF is now removed from the ongoing group call.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.7 Group regroup with pre-configured group
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.7.1 General
|
A group regroup may be achieved by regrouping MCPTT groups into a new regroup group which uses the configuration of a separate pre-configured MCPTT group. The MCPTT group configuration needs to be provided to the relevant MCPTT group members of the MCPTT groups that will be regrouped in advance of the regrouping operation.
NOTE 1: A pre-configured group which is intended only to provide configuration for the pre-configured group regroup process is identified by a parameter in group configuration described in 3GPP TS 23.280 [5].
NOTE 2: The configuration may alternatively be taken from any MCPTT group that has been configured in the IWF and the user profile of all the relevant MCPTT users who will be regrouped.
NOTE 3: Pre-configured group regroups may be defined according to the organizational structure of a mission critical organization, or by some other means which allows the MCPTT client of an authorized user and the IWF to be aware of an appropriate pre-configured group regroup for sets of MCPTT groups that will be regrouped together.
The pre-configured MCPTT group that provides the configuration is not used as the pre-configured group regroup itself, it only provides configuration for one or more pre-configured group or user regroup. The MCPTT group ID of the pre-configured group regroup is provided by the authorized user or the IWF (for the case where the IWF owns the pre-configured group regroup) when the pre-configured group regrouping is carried out.
The pre-configured group regroup can be specified to be a broadcast or non-broadcast type according to the configuration of the MCPTT group whose configuration is specified by the pre-configured group regroup request. The broadcast type of pre-configured group regroup is used for one-way communication where only an authorized user or the IWF (for the case where the IWF owns the pre-configured group regroup) is allowed to transmit and all other regroup members are only allowed to receive the communication (e.g. a call from a dispatcher to all regroup members). The non-broadcast type is used for two-way communication where all regroup members can transmit and receive (i.e, the pre-configured group regroup call behaves like a normal non-broadcast group call).
These procedures provide a regrouping service for MCPTT only and are independent of group regrouping procedures specified in subclause 10.2.2. If one of the MCPTT groups that has been requested for regrouping by means of this procedure has already been regrouped by the group regrouping procedure specified in 3GPP TS 23.280 [5] or subclause 10.2.2, the request for regrouping shall be rejected. The rules for regrouping set forth in subclause 10.2.2.5 apply.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.7.2 Regroup formation using pre-configured group
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.7.2.1 Regroup formation using pre-configured group initiated in the MCPTT system
|
Figure 10.3.7.2.1-1 illustrates the procedure to initiate a regroup procedure using a pre-configured MCPTT regroup group, where at least one of the groups to be regrouped is configured in the IWF. The group management server in the MCPTT system of the regroup group shares the necessary security related parameters together with the group configuration of the pre-configured group regroup with the group management server in the IWF; the MCPTT system does not need to be aware of the group members of the pre-configured group regroup that are receiving service in the IWF.
The procedure takes place prior to the establishment of a group call to the pre-configured group regroup.
In this procedure, any gateway MC servers between the IWF and the MCPTT system are not shown.
Pre-conditions:
- The MCPTT client is authorized to initiated a pre-configured group regroup procedure, and is receiving MCPTT service in the MCPTT system.
- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in the IWF, and the IWF has received the relevant security related information to allow communication in the pre-configured group regroup.
- In order to be aware whether the group is regrouped, the MCPTT server is subscribed to the group configuration in GMS.
- The GMS has subscribed group dynamic data as specified in subclause 10.1.5.5.1 from the MCPTT server within the same MCPTT system using the procedures defined in subclause 10.1.5.6 in 3GPP TS 23.280 [5].
- The IWF is affiliated to one or more of the MCPTT groups that will be regrouped; and/or, the IWF may own one or more of MCPTT groups to be regrouped.
- The pre-configured group regroup is homed in the MCPTT server.
- The IWF is home to at least one group that's a constituent group of the pre-configured group regroup.
NOTE 1: The IWF has the configuratiton information contained in the pre-configured group regroup, which is normally because at least one member of the pre-configured group regroup is homed on the IWF.
Figure 10.3.7.2.1-1: Regroup procedure using pre-configured group initiated in the MCPTT system
1. The authorized user of the MCPTT client initiates the pre-configured group regroup procedure, specifying the list of MCPTT groups to be regrouped including MCPTT group 1, the MCPTT group ID of the pre-configured group regroup and the MCPTT group ID of the group from which configuration information for the pre-configured group regroup is to be taken.
2. The MCPTT client sends the pre-configured regroup request to the MCPTT server.
3. The MCPTT server checks that the MCPTT client is authorized to initiate a pre-configured group regroup procedure, and resolves the group identities of the MCPTT groups requested in step 1. The MCPTT server also checks which group members are affiliated to the requested MCPTT groups that are homed in the MCPTT system. The MCPTT server identifies any partner systems or IWFs which are the group home systems for MCPTT groups identified in the list of groups to be regrouped. The MCPTT server may retrieve the configuration for the regroup group from the GMS if that configuration information is not already known to the MCPTT server.
NOTE 2: This procedure does not require that that the authorized user of the MCPTT client is a group member of the MCPTT groups listed in the pre-configured group regroup request, or that the authorized user of the MCPTT client is an affiliated group member of any of the listed MCPTT groups.
4. The MCPTT server sends an IWF pre-configured regroup requests to the IWF.
NOTE 3: Only group members that are affiliated to the MCPTT groups that are to be regrouped are sent a pre-configured regroup request.
5. The IWF sends an IWF pre-configured regroup response to the MCPTT server. The IWF may reject the IWF group regroup response. (e.g. if one of its constituent groups is in the emergency state or is already in a regroup, if the IWF does not support temporary groups or the IWF does not support group regrouping)
6. The MCPTT server sends the pre-configured regroup response to the MCPTT client.
After the pre-configured group regrouping procedure, the regrouping remains in effect until explicitly cancelled by the procedure in subclause 10.3.7.3.
Participation by the IWF in the ongoing pre-configured group regroup persists until the IWF is no longer affiliated to any of the regrouped groups.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.7.2.2 Regroup formation using pre-configured group initiated in the IWF
|
Figure 10.3.7.2.2-1 illustrates the procedure to initiate a pre-configured group regroup procedure using a pre-configured MCPTT group, where at least one of the groups to be regrouped is configured in an MCPTT system. The group management server in the IWF shares the necessary security related parameters together with the group configuration of the MCPTT regroup group with the group management server in the MCPTT system and the group management server in the MCPTT system distributes this configuration including those security parameters to its served MCPTT users according to the procedures in 3GPP TS 23.280 [5] subclause 10.2.7; the IWF does not need to be aware of the list of group members of the pre-configured group regroup that are receiving service in the MCPTT system. The group can have multiple MCPTT clients, but only one MCPTT client involved in the session is shown for simplicity.
The procedure takes place prior to the establishment of a group call to the pre-configured group regroup.
In this procedure, any gateway MC servers between the IWF and the MCPTT system are not shown.
Pre-conditions:
- The MCPTT client is an affiliated member of MCPTT group 1 where MCPTT group 1 is defined in the MCPTT system.
- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in the MCPTT client, and the MCPTT client has received the relevant security related information to allow communication in the pre-configured group regroup.
- The pre-configured group regroup is homed in the IWF.
- The MCPTT system is home to at least one group that's a constituent group of the pre-configured group regroup.
NOTE 1: The MCPTT system has the configuratiton information contained in the pre-configured group, which is normally because at least one member of the preconfigured group is homed on the MCPTT system.
Figure 10.3.7.2.2-1: Regroup procedure using pre-configured group initiated in the IWF
1. The IWF initiates the pre-configured group regroup procedure, specifying the list of MCPTT groups to be regrouped including MCPTT group 1, the MCPTT group ID of the pre-configured group regroup and the MCPTT group ID of the group from which configuration information for the pre-configured group regroup is to be taken. The IWF sends the IWF pre-configured regroup request to the MCPTT server in the partner MCPTT system.
2. The MCPTT server checks the status of any MCPTT groups hosted by itself, and identifies affiliated group members of any of the identified MCPTT groups (both MCPTT groups that are hosted in the MCPTT system and MCPTT groups that are hosted in the IWF) that are receiving MCPTT service in the MCPTT system, which includes the MCPTT client.
3. The MCPTT server sends a pre-configured regroup request to the MCPTT client.
NOTE 2: Only group members that are affiliated to the MCPTT groups that are to be regrouped are sent a pre-configured regroup request.
4. The MCPTT client notifies the user of the regrouping.
5. The MCPTT client 2 may send the pre-configured regroup response to the MCPTT server to acknowledge the regrouping action. This acknowledgement is not sent in response to a multicast transmission of the pre-configured regroup request.
6. The MCPTT server affiliates the regrouped MCPTT client to the pre-configured group regroup.
7. The MCPTT server sends an IWF pre-configured regroup response to the IWF.
After the pre-configured group regrouping procedure, the regrouping remains in effect until explicitly cancelled by the procedure in subclause 10.3.7.3.
MCPTT client participation in the ongoing pre-configured group regroup persists until the MCPTT client is no longer affiliated to any of the regrouped groups.
MCPTT client affiliation to the pre-configured group regroup may cease when the clients MCPTT service ceases, e.g. when the UE is powered down, or by the client performing a log-off operation.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.7.3 Regroup cancellation using pre-configured group regroup
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.7.3.1 Regroup cancellation using pre-configured group initiated in the MCPTT system
|
Figure 10.3.7.3.1-1 illustrates the procedure to cancel a regrouping that uses a pre-configured MCPTT regroup group where there the regroup had been initiated in the MCPTT system.
Pre-conditions:
- The IWF has been regrouped into the pre-configured group regroup.
- The MCPTT client is authorized to cancel a pre-configured group regroup.
- The GMS has subscribed to the group dynamic data specified in 3GPP TS 23.280 [5] subclause 10.1.5.5.1 from the MCPTT server as specified in 3GPP TS 23.280 [5] subclause 10.1.5.6.
Figure 10.3.7.3.1-1: Regroup cancellation using pre-configured group initiated in the MCPTT system
1. The authorized user of the MCPTT client initiates the cancellation of the pre-configured group regroup.
2. The MCPTT client sends the pre-configured regroup cancel request to the MCPTT server, specifying the MCPTT group ID of the regroup group.
3. The MCPTT server checks that the MCPTT client is authorized to cancel a pre-configured group regroup.
4. The MCPTT server sends the IWF pre-configured regroup cancel request to the IWF.
5. The IWF sends the IWF pre-configured regroup cancel response to the MCPTT server. The IWF may reject the IWF group regroup response. (e.g. if one of its constituent groups is in the emergency state or is already in a regroup, if the IWF does not support temporary groups or the IWF does not support group regrouping)
6. The MCPTT server sends a pre-configured regroup cancel response to the MCPTT client.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.7.3.2 Regroup cancellation using pre-configured group initiated in the IWF
|
Figure 10.3.7.3.2-1 illustrates the procedure to cancel a regrouping that uses a pre-configured MCPTT group where the regroup is initiated in the IWF. Only one MCPTT group member is shown for simplicity.
Pre-conditions:
- The MCPTT client has been regrouped into a pre-configured group regroup, and is receiving MCPTT service in the MCPTT system.
Figure 10.3.7.3.2-1: Cancel pre-configured group regroup procedure using pre-configured group in the MCPTT system
1. The IWF initiates the cancellation of the regrouping that uses a pre-configured MCPTT group. The IWF sends the IWF pre-configured regroup cancel request to the MCPTT server, specifying the MCPTT group ID of the regroup group.
2. The MCPTT server sends the pre-configured regroup cancel request to the MCPTT client.
3. The MCPTT client notifies the user of the cancellation of the pre-configured group regrouping.
4. The MCPTT client may send the pre-configured regroup remove response to the MCPTT server to acknowledge the cancellation of the pre-configured group regrouping. This acknowledgement is not sent in response to a multi-cast transmission of the pre-configured regroup cancel request.
5. The MCPTT server de-affiliates the MCPTT client from the pre-configured group regroup.
6. The MCPTT server sends the IWF pre-configured regroup cancel response to the IWF.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.7.4 Regroup rejection using pre-configured group
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.7.4.1 Regroup rejection using pre-configured group for regroup initiated in the MCPTT system
|
Figure 10.3.7.4.1‑1 illustrates the case where the procedure to initiate a pre-configured group regroup procedure with an MCPTT system and an IWF using a pre-configured MCPTT group described in subclause 10.3.7.3.1 commences, but where the request for the regroup is rejected by the IWF, for example because one of the groups hosted by the IWF is already regrouped by other group regrouping procedures.
In this procedure, any gateway MC servers between the IWF and the MCPTT system are not shown.
Pre-conditions:
- The MCPTT client is authorized to initiate a pre-configured group regroup procedure.
- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in the IWF, and the IWF has received the relevant security related information to allow communication in the pre-configured group regroup.
- In order to be aware whether the group is regrouped, the MCPTT server is subscribed to the group configuration in GMS.
- The GMS has subscribed group dynamic data as specified in subclause 10.1.5.5.1 from the MCPTT server within the same MCPTT system using the procedures defined in subclause 10.1.5.6 in 3GPP TS 23.280 [5].
- The IWF is affiliated to one or more of the MCPTT groups that will be regrouped; and/or, the IWF may own one or more of MCPTT groups to be regrouped.
Figure 10.3.7.4.1-1: Regroup rejection using pre-configured group for group initiated in the MCPTT system
1. The authorized user of the MCPTT client initiates the pre-configured group regroup procedure, specifying the list of MCPTT groups to be regrouped including MCPTT group 1, the MCPTT group ID of the pre-configured group regroup and the MCPTT group ID of the group from which configuration information for the pre-configured group regroup is to be taken.
2. The MCPTT client sends the pre-configured regroup request to the MCPTT server.
3. The MCPTT server checks that the MCPTT client is authorized to initiate a pre-configured group regroup procedure, and resolves the group identities of the MCPTT groups requested in step 1. The MCPTT server also checks which group members are affiliated to the requested MCPTT groups that are homed in the MCPTT system. The MCPTT server identifies any partner systems or IWFs which are the group home systems for MCPTT groups identified in the list of groups to be regrouped. The MCPTT server may retrieve the configuration for the pre-configured group regroup from the GMS if that configuration information is not already known to the MCPTT server.
NOTE: This procedure does not require that that the authorized user of the MCPTT client is a group member of the MCPTT groups listed in the regroup request, or that the authorized user of the MCPTT client is an affiliated group member of any of the listed MCPTT groups.
4. The MCPTT server sends the IWF pre-configured regroup requests to the IWF.
5. The IWF sends a pre-configured regroup reject to the MCPTT server, indicating the reason for rejection, for example because one or more of the MCPTT groups has already been regrouped by another group regrouping procedure, either internal to the IWF or in an MCPTT system.
6. The MCPTT server sends a pre-configured regroup reject to the MCPTT client, indicating the reason for the rejection.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.7.4.2 Regroup rejection using pre-configured group for regroup initiated in the IWF
|
Figure 10.3.7.4.2 1 illustrates the case where the procedure to initiate a regroup procedure with an MCPTT system and an IWF using a pre-configured MCPTT group described in subclause 10.3.7.3.2 commences, but where the request for the pre-configured group regroup is rejected by the MCPTT system, for example because one of the groups hosted by the MCPTT system is already regrouped by other group regrouping procedures.
In this procedure, any gateway MC servers between the IWF and the MCPTT system are not shown.
Pre-conditions:
- The MCPTT client is an affiliated member of MCPTT group 1 where MCPTT group 1 is defined in the MCPTT system.
- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in the MCPTT client, and the MCPTT client has received the relevant security related information to allow communication in the pre-configured group regroup.
Figure 10.3.7.4.2-1: Regroup rejection using pre-configured group for group initiated in the IWF
1. The IWF initiates the pre-configured group regroup procedure, specifying the list of MCPTT groups to be regrouped including MCPTT group 1, the MCPTT group ID of the pre-configured group regroup and the MCPTT group ID of the group from which configuration information for the pre-configured group regroup is to be taken. The IWF sends the IWF pre-configured regroup request to the MCPTT server.
2. The MCPTT server checks the status of any MCPTT groups hosted by that MCPTT server, and determines that one or more requested MCPTT groups has already been regrouped by another group regrouping procedure.
3. The partner MCPTT server sends an IWF pre-configured regroup reject to the IWF, indicating the reason for rejection.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.7.5 Pre-configured regroup update procedures
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.7.5.1 MCPTT client PTTs on MCPTT group during an in-progress pre-configured group regroup
|
Figure 10.3.7.5.1‑1 illustrates the procedure when a user attempts to set up a MCPTT group call on a group involved in an in-progress pre-configured group regroup, homed in the IWF.
Pre-conditions:
- The MCPTT client is an affiliated member of MCPTT group A that is part of an in-progress pre-configured group regroup with MCPTT groups B and C. MCPTT groups A, B and C can be homed in either the IWF or the MCPTT system.
- MCPTT group D is being used as the pre-configured group regroup. MCPTT group D is homed in the IWF.
- The MCPTT client has missed the pre-configured regroup request message (e.g. poor signalling conditions, race condition).
Figure 10.3.7.5.1-1: Procedure for MCPTT client PTTs on MCPTT group during an in-progress pre-configured group regroup
1. The MCPTT client attempts to start a call on MCPTT group A. The MCPTT client sends a group call request message to the MCPTT server containing MCPTT group A as the target group.
2. The MCPTT server forwards the request to the IWF as an IWF group call request.
3. The IWF sends an IWF group call response to the MCPTT server indicating that the call set up is denied because the group is part of an in-progress pre-configured group regroup.
4. The MCPTT server forwards the response to the MCPTT client as a group call response.
5. The IWF sends an IWF pre-configured regroup request to the MCPTT server containing MCPTT group D, the group ID of the pre-configured group regroup.
6. The MCPTT server forwards the request to the MCPTT client as a pre-configured regroup request.
7. The MCPTT client notifies the user of the group call set up failure and of the regrouping procedure.
NOTE 1: Step 5 can occur prior to step 4 and step 7 can occur after step 4.
8. The MCPTT client sends the pre-configured regroup response to the MCPTT server to acknowledge the regrouping action.
9. The MCPTT server forwards the response to the IWF as an IWF pre-configured regroup response. The IWF affiliates the regrouped MCPTT client to the pre-configured group regroup.
NOTE 2: If there is a call currently in progress on the pre-configured group regroup then this MCPTT client can be added to the call using the late entry procedure. If there is no call currently in progress, then the MCPTT user can retry the group call set up.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.7.6 Call request on pre-configured regroup group after group regroup has been cancelled
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.7.6.1 MCPTT client PTTs on pre-configured regroup group after group regroup has been cancelled
|
Figure 10.3.7.6.1‑1 illustrates the procedure when an MCPTT user attempts to set up a MCPTT group call on a pre-configured regroup group after the pre-configured MCPTT group regroup has been cancelled.
Pre-conditions:
- The MCPTT client is a member of MCPTT group A that was part of an in-progress pre-configured group regroup with MCPTT groups B and C that has been cancelled. MCPTT group D was used as the pre-configured regroup group. MCPTT group D is homed in the IWF.
- The MCPTT client has missed the pre-configured regroup cancel request message (e.g. poor signalling conditions, race condition).
Figure 10.3.7.6.1-1: Procedure for MCPTT client PTTs on pre-configured regroup group after the group regroup is cancelled
1. The MCPTT client attempts to start a call on MCPTT group D, the pre-configured regroup group. The MCPTT client sends a group call request message to the MCPTT server containing MCPTT group D as the target group.
2. The MCPTT server forwards the request to the IWF as an IWF group call request.
NOTE 1: The pre-configured regroup group D can be a group in the MCPTT client's profile, and the MCPTT client can be a member of group D.
3. The IWF sends an IWF group call response to the MCPTT server indicating that the call set up is denied because the group regroup is no longer active.
4. The MCPTT server forwards the response to the MCPTT client as a group call response
NOTE 2: In the following, steps 5, 6, 8 and 9 are optional.
5. The IWF sends an IWF pre-configured regroup cancel request to the MCPTT server.
6. The MCPTT server forwards the request as a pre-configured regroup cancel request to the MCPTT client.
NOTE 3: This message should be sent over unicast.
7. The MCPTT client notifies the user of the group call set up failure and of the regrouping cancellation.
8. The MCPTT client sends a pre-configured regroup cancel response to the MCPTT server to acknowledge the regrouping cancellation.
9. The MCPTT server forwards the response to the IWF as an IWF pre-configured regroup cancel response.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.7.7 Adding newly affiliated user to a pre-configured group regroup
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.7.7.1 Adding newly affiliated MCPTT user to a pre-configured group regroup
|
Figure 10.3.7.7.1‑1 illustrates the procedure to add a newly affiliated MCPTT user to an in-progress pre-configured group regroup operation.
Pre-conditions:
- The MCPTT client is a member of, but not yet affiliated with, a MCPTT group that is part of an in-progress pre-configured group regroup operation.
- The MCPTT group identity and group configuration for the regroup MCPTT group has been pre-configured in the MCPTT client, and the MCPTT client has received the relevant security related information to allow it to communicate in the pre-configured group regroup.
Figure 10.3.7.7.1-1: Procedure to add a newly affiliated user to a pre-configured group regroup
1. The MCPTT client affiliates to an MCPTT group that is currently part of an in-progress pre-configured group regroup. The affiliation follows the procedure in subclause 10.1.2.4.
2. The IWF sends an IWF pre-configured regroup request to the MCPTT server.
3. The MCPTT server sends a pre-configured regroup request to the MCPTT client.
4. The MCPTT client notifies the user of the regrouping.
5. The MCPTT client may send the pre-configured regroup response to the MCPTT server to acknowledge the regrouping action. These acknowledgements are not sent in response to a multicast transmission of the pre-configured regroup request.
6. The MCPTT server sends an IWF pre-configured regroup response to the IWF. The IWF affiliates the MCPTT client to the group regroup.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.7.7.2 Adding newly affiliated user homed in the IWF to a pre-configured group regroup
|
Figure 10.3.7.7.2‑1 illustrates the procedure to add a newly affiliated user homed in the IWF to an in-progress pre-configured group regroup operation.
Pre-conditions:
- The LMR user is a member of, but not yet affiliated to, an MCPTT group that is part of an in-progress pre-configured group regroup operation.
- The MCPTT group identity and group configuration for the pre-configured group regroup has been pre-configured in the IWF, and the IWF has received the relevant security related information to allow it to communicate in the pre-configured group regroup.
Figure 10.3.7.7.2-1: Procedure to add a newly affiliated user to a pre-configured regroup
1. The IWF affiliates to an MCPTT group that is currently part of an in-progress pre-configured group regroup. The affiliation follows the procedure in subclause 10.1.2.2.
2. The MCPTT server retrieves the MCPTT group ID of the pre-configured group regroup and the MCPTT group ID of the group from which configuration information for the pre-configured group regroup is to be taken.
3. The MCPTT server sends an IWF pre-configured regroup request to the IWF.
4. The IWF sends an IWF pre-configured regroup response to the MCPTT server to acknowledge the regrouping action.
5. The MCPTT server affiliates the IWF to the group regroup.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.8 User regroup with pre-configured group
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.8.1 General
|
A user regroup may be achieved by regrouping MCPTT users into a new regroup group which uses the configuration of a separate pre-configured MCPTT group. The MCPTT regroup group configuration needs to be provided to the relevant MCPTT users who will be regrouped in advance of the regrouping operation. A pre-configured user regroup may contain users homed in the IWF and the IWF may host pre-configured user regroups which may contain members homed in an MCPTT system.
NOTE 1: A pre-configured group which is intended only to provide configuration for the pre-configured user regroup process is identified by a parameter in group configuration described in 3GPP TS 23.280 [5].
NOTE 2: The configuration may alternatively be taken from any MCPTT group that has been configured in the user profile of all of the relevant MCPTT users who will be regrouped and that has also been configured to the IWF for the case where the pre-configured user regroup contains members homed in the IWF.
The pre-configured user regroup that provides the configuration is not used as the pre-configured user regroup itself, it only provides configuration for one or more pre-configured user regroups. The MCPTT group ID of the pre-configured user regroup is provided by the originating authorized user or the originating IWF when the pre-configured user regrouping is carried out.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.8.2 Pre-configured user regroup formation
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.8.2.1 Pre-configured user regroup formation by the MCPTT system
|
Figure 10.3.8.2.1‑1 illustrates the procedure to initiate a pre-configured user regroup procedure using a pre-configured user regroup. The procedure takes place prior to the establishment of a group call to the pre-configured user regroup.
Pre-conditions:
- MCPTT clients 2 and 3 are registered with the MCPTT service.
- An MCPTT group that will be used for configuration of the pre-configured user regroup has been pre-configured in MCPTT clients 2 and 3 and the IWF, and MCPTT clients 2 and 3 and the IWF have received the relevant security related information to allow them to communicate in the pre-configured user regroup.
- MCPTT client 1 is authorized to initiated a pre-configured user regroup using the pre-configured user regroup procedure.
- MCPTT client 1 is aware of a suitable pre-configured group whose configuration has been pre-configured in the MC service clients of the MCPTT users who will be regrouped.
- The pre-configured user regroup is homed in the MCPTT server.
Figure 10.3.8.2.1-1: User regroup procedure using pre-configured group by the MCPTT system
1. The authorized user of MCPTT client 1 initiates the pre-configured user regroup procedure, specifying the list of MCPTT users to be regrouped (MCPTT clients 2, 3 and one or more IWF users), the MCPTT group ID of the pre-configured user regroup, and the MCPTT group ID of the group from which configuration information for the pre-configured user regroup is to be taken.
2. MCPTT client 1 sends the pre-configured regroup request to the MCPTT server. The request indicates the list of users to be included in the regroup operation.
3. The MCPTT server checks that MCPTT client 1 is authorized to initiate a pre-configured user regroup procedure.
NOTE 1: MCPTT clients and users homed in the IWF can be involved in multiple user and group regroups simultaneously.
4. The MCPTT server sends the pre-configured regroup requests to MCPTT clients 2 and 3 in steps 4a and 4b respectively.
5. MCPTT clients 2 and 3 notify their users of the regrouping in steps 4a and 4b respectively.
6. MCPTT clients 2 and 3 may send the pre-configured regroup response to the MCPTT server to acknowledge the regrouping action. These acknowledgements are not sent in response to a multicast transmission of the pre-configured regroup request.
7. The MCPTT server sends the IWF an IWF pre-configured regroup request.
8. The IWF sends the MCPTT server and IWF pre-configured regroup response.
9. The MCPTT server affiliates the regrouped MCPTT clients and the IWF to the pre-configured user regroup.
10. The MCPTT server sends a pre-configured user regroup response to MCPTT client 1.
NOTE 2: After the pre-configured user regrouping procedure, the regrouping remains in effect until explicitly cancelled by the procedure in subclause 10.3.8.3.1.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.8.2.2 Pre-configured user grop regroup formation by the IWF
|
Figure 10.3.8.2.2-1 illustrates the procedure for the IWF to initiate a pre-configured user regroup procedure using a pre-configured MCPTT group. The procedure takes place prior to the establishment of a pre-configured user regroup call to the pre-configured user regroup. For simplicity, only one receiving MCPTT client is shown.
Pre-conditions:
- The MCPTT client is registered with the MCPTT service.
- An MCPTT group that will be used for configuration of the pre-configured user regroup has been pre-configured in the MCPTT client and the IWF, and the MCPTT client has received the relevant security related information to allow it to communicate in the pre-configured user regroup.
- The pre-configured user regroup is homed in the IWF.
Figure 10.3.8.2.2-1: User regroup procedure using pre-configured group by the IWF
1. The IWF initiates the pre-configured user regroup, the IWF sends an IWF pre-configured regroup request to the MCPTT server. The request indicates the list of users to be included in the regroup operation, that are homed in the MCPTT system.
NOTE 1: MCPTT clients and users homed in the IWF can be involved in multiple user and group regroups simultaneously.
2. The MCPTT server sends the pre-configured regroup request to the MCPTT client.
3. The MCPTT client notifies the MCPTT users of the regrouping.
4. The MCPTT client may send the pre-configured regroup response to the MCPTT server to acknowledge the regrouping action. This acknowledgement is not sent in response to a multicast transmission of the pre-configured regroup request.
5. The MCPTT server sends an IWF pre-configured regroup response to the IWF.
NOTE 2: After the pre-configured user regroup procedure, the regrouping remains in effect until explicitly cancelled by the procedure in subclause 10.3.8.3.2.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.8.3 Pre-configured user regroup cancellation
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.8.3.1 Pre-configured user regroup cancellation by the MCPTT system
|
Figure 10.3.8.3.1-1 illustrates the procedure to cancel a pre-configured user regroup that uses a pre-configured MCPTT group. For simplicity, only one receiving MCPTT client is shown.
Pre-conditions:
- MCPTT client 2 and at least one user homed in the IWF have been regrouped into the pre-configured user regroup.
- MCPTT client 1 is authorized to cancel a pre-configured user regroup that uses a pre-configured MCPTT group.
Figure 10.3.8.3.1-1: Cancel pre-configured user regroup procedure by the MCPTT system
1. The authorized user of MCPTT client 1 initiates the cancellation of the pre-configured user regroup that uses a pre-configured MCPTT group.
2. MCPTT client 1 sends the pre-configured regroup cancel request to the MCPTT server, specifying the MCPTT group ID of the pre-configured user regroup.
3. The MCPTT server checks that MCPTT client 1 is authorized to cancel a pre-configured user regroup.
4. The MCPTT server sends the pre-configured regroup cancel requests to MCPTT client 2.
5. MCPTT clients 2 notifies the MCPTT user of the cancellation of the pre-configured user regroup.
6. MCPTT client 2 may send the MCPTT server a pre-configured regroup cancel response. This acknowledgement is not sent in response to a multicast transmission of the pre-configured regroup cancel request.
7. The MCPTT server sends the IWF an IWF pre-configured regroup cancel request.
8. The IWF sends the MCPTT server an IWF pre-configured regroup cancel response.
9. The MCPTT server de-affiliates MCPTT clients 2 and 3 from the pre-configured user regroup.
10. The MCPTT server sends a pre-configured regroup cancel response to MCPTT client 1.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.8.3.2 Pre-configured user regroup cancellation by the IWF
|
Figure 10.3.8.3.2-1 illustrates the procedure to cancel a pre-configured user regroup that uses a pre-configured MCPTT group. For simplicity, only one receiving MCPTT client is shown.
Pre-conditions:
- An MCPTT client and at least one user homed in the IWF have been regrouped into the pre-configured user regroup.
Figure 10.3.8.3.2-1: Cancel pre-configured pre-configured user regroup procedure by the IWF
1. The IWF initiates the cancellation of the pre-configured user regroup. The IWF sends the pre-configured regroup cancel request to the MCPTT server, specifying the MCPTT group ID of the pre-configured user regroup.
2. The MCPTT server sends the pre-configured regroup cancel requests to the MCPTT client.
3. The MCPTT client notifies the MCPTT user of the cancellation of the pre-configured user regroup.
4. The MCPTT client may send the MCPTT server a pre-configured regroup cancel response. This acknowledgement is not sent in response to a multicast transmission of the pre-configured regroup cancel request.
5. The MCPTT server sends an IWF pre-configured regroup cancel response to the IWF.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.4 Private call
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.4.1 Information flows for private calls
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.4.1.1 General
|
The following subclauses define information flows for private calls on the IWF-1 interface. Private call related information flows on reference points other than IWF-1 are defined in 3GPP TS 23.379 [7].
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.4.1.2 IWF private call request
|
Table 10.4.1.2-1 describes the information flow IWF private call request from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Table 10.4.1.2-1: IWF private call request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias associated with the MCPTT ID of the calling party.
MCPTT ID (see NOTE 1)
O
The MCPTT ID of the called party
Functional alias
(see NOTE 1)
O
The functional alias of the called party
Use floor control indication
M
This element indicates whether floor control will be used for the private call.
SDP offer
M
Media parameters of MCPTT client.
Encryption Algorithm
O
Encryption algorithm to use for the call. The field can also indicate whether the encryption algorithm choice is determined from information in the media stream.
Encryption mode
M
Whether E2EE will be used.
Requested commencement mode
O
An indication of the commencement mode to be used.
Implicit floor request
(see NOTE 2)
O
An indication that the user is also requesting the floor.
Location
O
Location of the calling party
Requested priority
O
Application priority level requested for this call.
Transfer indicator
O
Indicates that the MCPTT private call request is a result of a call transfer (true/false).
Forwarding indicator
O
Indicates that the MCPTT private call request is a result of a call forwarding (true/false)
Remotely initiated call request indicator
O
Indicates that the MCPTT private call request is a result of receiving of a remotely initiated call request and may be included only for remotely initiated call.
Additional application specific data (see NOTE 3)
O
Some LMR systems use additional information at the application layer.
NOTE 1: At least one identity shall be present. If both elements are present, the MCPTT ID is used to route the call.
NOTE 2: This element shall be included only when the originating client requests the floor.
NOTE 3: This element can be present if the LMR system uses it (like GSM-R). GSM-R uses for example UUI as defined in ETSI TS 103 389 [10] and ETSI TS 102 610 [11]
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.4.1.3 IWF private call response
|
Table 10.4.1.3-1 describes the information flow IWF private call response from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Table 10.4.1.3-1: IWF private call response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
MCPTT ID
O
The MCPTT ID of the called party
Acceptance confirmation
O
An indication whether the user has positively accepted the call.
SDP answer
M
Media parameters selected
Result
M
Result of the IWF private call request: success or failure
Encryption Algorithm(s) response
O
A list of one or more alternative encryption algorithm(s) to use for the call.
Use floor control indication response
O
This element indicates whether the floor control indication in the request is acceptable.
Implicit floor request response
O
This element indicates whether the indication that the user is also requesting the floor in the request is acceptable.
Additional application specific data (see NOTE)
O
Some LMR systems use additional information at the application layer.
NOTE: This element can be present if the LMR system uses it (like GSM-R). GSM-R uses for example UUI as defined in ETSI TS 103 389 [10] and ETSI TS 102 610 [11].
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.4.1.4 IWF ringing
|
Table 10.4.1.4-1 describes the information flow IWF ringing from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Table 10.4.1.4-1: IWF ringing information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
MCPTT ID
M
The MCPTT ID of the called party
Ringing indication
O
Indication to the caller.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.4.1.5 IWF call end request
|
Table 10.4.1.5-1 describes the information flow IWF call end request from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Table 10.4.1.5-1: IWF call end request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
MCPTT ID
M
The MCPTT ID of the called party
Additional application specific data (see NOTE)
O
Some LMR systems use additional information at the application layer.
NOTE: This element can be present if the LMR system uses it (like GSM-R). GSM-R uses for example UUI as defined in ETSI TS 103 389 [10] and ETSI TS 102 610 [11].
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.4.1.6 IWF call end response
|
Table 10.4.1.6-1 describes the information flow IWF call end response from the IWF to the MCPTT server.
Table 10.4.1.6-1: IWF call end response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the responding party
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.4.2 Private call setup in automatic commencement mode
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.4.2.1 MCPTT user initiating an MCPTT private call
|
In this procedure, an MCPTT user is initiating an MCPTT private call (automatic commencement mode) for communicating with a user in an LMR system, with or without floor control enabled.
This subclause is based on the procedure for private call setup in automatic commencement mode – MCPTT users in multiple MCPTT systems described in 3GPP TS 23.379 [7], subclause 10.7.2.3.1.
In figure 10.4.2.1-1, an MCPTT client initiates establishment of an MCPTT private call with an LMR user.
Pre-conditions:
1. The calling MCPTT user has selected automatic commencement mode for the call;
2. The MCPTT client is registered to the MCPTT service, as per procedure in subclause 10.2 in 3GPP TS 23.379 [7].
3. Optionally, MCPTT client may use an activated functional alias for the call.
4. The MCPTT server has subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Figure 10.4.2.1-1: Private call setup in automatic commencement mode, initiated by an MCPTT user
1. The MCPTT user at the MCPTT client initiates an MCPTT private call. The MCPTT client sends an MCPTT private call request towards the MCPTT server. The MCPTT private call request contains the MCPTT IDs corresponding to the calling MCPTT party and called LMR party and an SDP offer containing one or more media types. If available, the MCPTT user at the MCPTT client may also include a functional alias. The following parameters are also included that describe the MCPTT client's choices:
- the encryption algorithm;
- the encryption mode (encrypted or not);
- an indication of whether the MCPTT client is requesting the floor, and if the MCPTT client is requesting the floor, location information of the calling MCPTT client may be provided;
- requested commencement mode (automatic in this case); and
- an indication of whether the call is to be full or half duplex (whether to establish floor control).
2. The MCPTT server checks whether the MCPTT user at the MCPTT client is authorized to initiate the private call and whether the provided functional alias, if present, can be used and has been activated for the user. Because the IWF private call request is requesting automatic commencement mode, the MCPTT server also checks whether the MCPTT user at the MCPTT client is authorized to initiate a call in automatic commencement mode. If the MCPTT private call request contains a functional alias instead of an MCPTT ID as called party, the MCPTT server shall resolve the functional alias to the corresponding MCPTT ID(s) for which the functional alias is active. The MCPTT server shall also check whether MCPTT client 1 is allowed to use the functional alias of MCPTT client 2 to setup a private call and whether MCPTT client 2 is allowed to receive a private call from MCPTT client 1 using the functional alias. If authorized the MCPTT server proceeds with step 3. If location information was included in the MCPTT private call request, 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.
NOTE 1: For private calls to a functional alias homed in the LMR system (i.e. GSM-R). the final resolution of the functional alias is performed in the GSM-R system.
3a. The MCPTT server responds with a functional alias resolution response message that contains the resolved MCPTT ID back to MCPTT client.
3b. If the MCPTT server replies with a MCPTT functional alias resolution response message, the MCPTT client 1 abandons the first MCPTT private call request in step 1 and sends a new MCPTT private call request towards the resolved MCPTT ID.
4. If authorized, the MCPTT server sends the IWF private call request that may or may not include location of the requestor, depending on the outcome of the privacy check towards the IWF, including the original parameters and offering the same media types or a subset of the media types contained in the initial received request as per 3GPP TS 23.379 [7].
NOTE 2: How the IWF private call request is forwarded to the LMR system is out of scope of the present document.
5. The IWF sends an IWF private call response to the MCPTT server, indicating that the IWF does support one of the requested media types. The response indicates success or failure. If the indication is failure, the response may include one or more alternatives to the parameter values contained in step 3.
6. The MCPTT server forwards the MCPTT private call response to the MCPTT client. If the result parameter indicates success, then the MCPTT client proceeds to step 6. Otherwise, if the parameters returned in the MCPTT private call response are acceptable to the MCPTT client, then the MCPTT client can send a new MCPTT private call request with the new parameters and behaves according to those parameters. The calling MCPTT user may be notified of the change in parameters, for example, that the call is to be without floor control. The MCPTT user can choose to end the call rather than continue with the new parameters. If the parameters returned are not acceptable to the MCPTT client, then the call fails.
7. The MCPTT client has successfully established media plane for communication to the IWF and either end can transmit media. The MCPTT system initiating the call is responsible of granting the floor, solving competing floor requests and issuing floor revoked indications.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.4.2.2 LMR user initiating a private call with MCPTT user
|
In this procedure, an LMR user is initiating a private call (in automatic commencement mode) for communicating with a user in MCPTT system, with or without floor control enabled.
This subclause is based on the procedure for private call setup in automatic commencement mode – MCPTT users in multiple MCPTT systems described in 3GPP TS 23.379 [7], subclause 10.7.2.3.1.
In figure 10.4.2.2-1, an LMR user initiates establishment of a private call with an MCPTT user.
Pre-conditions:
1. The calling LMR user has selected automatic commencement mode for the call;
2. The MCPTT client is registered to the MCPTT service, as per procedure in subclause 10.2 in 3GPP TS 23.379 [7].
3. The LMR user at the LMR system has initiated a private call towards an MCPTT user.
4. Optionally, LMR user may use an activated functional alias (homed in the MCPTT system) for the call.
5. The MCPTT server has subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates.
NOTE 1: Private call operation between the LMR user and the IWF are out of scope of the present document.
NOTE 2: The mapping between alternative addressing schemes of the LMR user and the corresponding functional alias is out of scope of the present document.
Figure 10.4.2.2-1: Private call setup in automatic commencement mode, initiated by an LMR user
1. The IWF sends an IWF private call request towards the MCPTT server. The IWF private call request contains the MCPTT IDs corresponding to the calling LMR party and the called MCPTT party and an SDP offer containing one or more media types. If available, the LMR party homed in the IWF may also include a functional alias. The following parameters are also included that describe the MCPTT client's choices:
- the encryption algorithm;
- the encryption mode (encrypted or not);
- an indication of whether the LMR user is requesting the floor, and if the MCPTT client is requesting the floor, location information of the calling MCPTT client may be provided;
- requested commencement mode (automatic in this case); and
- an indication of whether the call is to be full or half duplex (whether to establish floor control).
2. The MCPTT server checks whether the MCPTT user at the MCPTT client is authorized and able to receive the private call. Because the IWF private call request is requesting automatic commencement mode, the MCPTT server also checks whether the MCPTT user at the MCPTT client is authorized to receive a call in automatic commencement mode. If the MCPTT private call request contains a functional alias instead of an MCPTT ID as called party, the MCPTT server shall resolve the functional alias to the corresponding MCPTT ID for which the functional alias is active. The MCPTT server shall also check whether MCPTT client 1 is allowed to use the target functional alias to setup a private call and whether the MCPTT client is allowed to receive a private call from the IWF using the functional alias. If authorized the MCPTT server proceeds with step 3.
3a. The MCPTT server responds with a functional alias resolution response message that contains the resolved MCPTT ID back to the IWF.
3b. If the MCPTT server replies with a MCPTT functional alias resolution response message, the IWF abandons the first MCPTT private call request in step 1 and sends a new MCPTT private call request towards the resolved MCPTT ID.
4. If authorized, the MCPTT server sends the MCPTT private call request towards the MCPTT client, including the original parameters with or without the location of the calling party and offering the same media types or a subset of the media types contained in the initial received request as per 3GPP TS 23.379 [7].
5. The MCPTT client sends an MCPTT private call response to the MCPTT server indicating that the MCPTT client does support one of the requested media types. The response indicates success or failure. If the indication is failure, the response may also include one or more alternatives to the parameter values contained in step 3.
6. The MCPTT server sends the IWF private call response to the IWF offering the same media type as that sent in step 4. If the parameters returned are not acceptable to the IWF, then the call fails. If the parameters returned in the IWF private call response are different but acceptable to the IWF, then the IWF can send a new IWF private call request with the new parameters starting with step 1, which is to essentially restart the call. If there is no change of parameter, then the call proceeds to step 6.
NOTE 3: The calling LMR user may be notified of the change in parameters, for example, that the call is to be without floor control.
7. The MCPTT client has successfully established media plane for communication to the IWF and either end can transmit media. The LMR system initiating the call is responsible of granting the floor, solving competing floor requests and issuing floor revoked indications.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.4.3 Private call setup in manual commencement mode
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.4.3.1 MCPTT user is initiating an MCPTT private call
|
In this procedure, an MCPTT user is initiating an MCPTT private call (manual commencement mode) for communicating with an LMR user via an IWF, with or without floor control enabled.
This subclause is based on the procedure for private call setup in manual commencement mode – MCPTT users in multiple MCPTT systems described in 3GPP TS 23.379 [7], subclause 10.7.2.3.2.
In figure 10.4.3.1-1, an MCPTT client initiates establishment of an MCPTT private call with an LMR user.
Pre-conditions:
1. The calling MCPTT user has selected manual commencement mode for the call.
2. The MCPTT client is registered to the MCPTT service, as per procedure in subclause 10.2 in 3GPP TS 23.379 [7].
3. Optionally, MCPTT client may use an activated functional alias (homed in the MCPTT system) for the call.
4. The MCPTT server has subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Figure 10.4.3.1-1: Private call setup in manual commencement mode – initiated by an MCPTT user
1. The MCPTT user at the MCPTT client would like to initiate an MCPTT private call. The MCPTT client sends an MCPTT private call request towards the MCPTT server. The MCPTT private call request contains the MCPTT IDs corresponding to the calling MCPTT party and called LMR party and an SDP offer containing one or more media types. If available, the MCPTT user at the MCPTT client may also include a functional alias. The following parameters are also included that describe the MCPTT client's choices:
- the encryption algorithm;
- the encryption mode (encrypted or not)
- an indication of whether the MCPTT client is requesting the floor;
- requested commencement mode (manual in this case), and if the MCPTT client is requesting the floor, location information of the calling MCPTT client may be provided; and
- an indication of whether the call is to be full or half duplex (whether to establish floor control).
2. The MCPTT server checks whether the MCPTT user at the MCPTT client is authorized to initiate the private call and whether the provided functional alias, if present, can be used and has been activated for the user. Because the IWF private call request is requesting manual commencement mode, the MCPTT server also checks whether the MCPTT user at the MCPTT client is authorized to initiate a call in manual commencement mode. If the MCPTT private call request contains a functional alias instead of an MCPTT ID as called party, the MCPTT server shall resolve the functional alias to the corresponding MCPTT ID for which the functional alias is active. The MCPTT server shall also check whether MCPTT client 1 is allowed to use the functional alias of MCPTT client 2 to setup a private call and whether MCPTT client 2 is allowed to receive a private call from MCPTT client 1 using the functional alias. If authorized the MCPTT server proceeds with step 3. If location information was included in the MCPTT private call request, 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.
NOTE 1: For private calls to a functional alias homed in the LMR system (i.e. GSM-R). the final resolution of the functional alias is performed in the GSM-R system.
3a. The MCPTT server responds with a functional alias resolution response message that contains the resolved MCPTT ID back to MCPTT client 1.
3b. If the MCPTT server replies with a MCPTT functional alias resolution response message, the MCPTT client 1 abandons the first MCPTT private call request in step 1 and sends a new MCPTT private call request towards the resolved MCPTT ID.
4. If authorized, the MCPTT server sends the IWF private call request towards the IWF, including the original parameters that may or may not include location of the requestor, depending on the outcome of the privacy check, and offering the same media types or a subset of the media types contained in the initial received request as per 3GPP TS 23.379 [7].
NOTE 2: How the IWF private call request is forwarded to the LMR system is out of scope of the present document.
5. The IWF may report failure with an IWF private call response to the MCPTT server. The response may include one or more alternatives to the parameter values contained in step 3. If the IWF does not report failure, the process proceeds with step 6.
6. The MCPTT server forwards the MCPTT private call response to the MCPTT client. If the result parameter indicates failure, the MCPTT client may abandon the call. If the parameters in the MCPTT private call response are acceptable to the MCPTT client, then the MCPTT client can send a new MCPTT private call request with the new parameters to the MCPTT server and behaves according to those parameters. The calling user may be notified of the change in parameters, for example, that the call is to be without floor control. The calling user may choose to end the call rather than continue with the new parameters.
7. The receiving IWF sends an IWF ringing to the MCPTT server while waiting for the call to be accepted.
8. The MCPTT server forwards the MCPTT ringing to the MCPTT client. The MCPTT client may indicate to the MCPTT user that the LMR user has been notified, e.g. by producing ringback audio.
9. Once the call has been accepted by the called user, the IWF sends an IWF private call response to the MCPTT server. The IWF private call response indicates that the IWF does support one of the requested media types.
10. The MCPTT server forwards the MCPTT private call response to the MCPTT client. The MCPTT client may indicate to the MCPTT user that the call is connected, e.g. by stopping the ringback audio.
11. The MCPTT client has successfully established media plane for communication to the IWF. The MCPTT system initiating the call is responsible of granting the floor and solving the competing floor requests, and floor revoked indications.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.4.3.2 LMR user initiating a private call with MCPTT user
|
In this procedure, an LMR user is initiating a private call (in manual commencement mode) for communicating with an MCPTT user via an IWF, with or without floor control enabled.
This subclause is based on the procedure for private call setup in manual commencement mode – MCPTT users in multiple MCPTT systems described in 3GPP TS 23.379 [7], subclause 10.7.2.3.2.
In figure 10.4.3.2-1, an LMR user initiates establishment of a private call with an MCPTT user.
Pre-conditions:
1. The calling LMR user has selected manual commencement mode for the call.
2. The MCPTT client is registered to the MCPTT service, as per procedure in subclause 10.2 in 3GPP TS 23.379 [7].
3. The LMR user at the LMR system has initiated a private call towards an MCPTT user.
4. Optionally, LMR user may use an activated functional alias (homed in the MCPTT system) for the call.
5. The MCPTT server has subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates.
NOTE 1: Private call operation between the LMR user and the IWF are out of scope of the present document.
NOTE 2: The mapping between alternative addressing schemes of the LMR user and the corresponding functional alias is out of scope of the present document
Figure 10.4.3.2-1: Private call setup in manual commencement mode, initiated by an LMR user
1. The IWF sends an IWF private call request towards the MCPTT server. The IWF private call request contains the MCPTT IDs corresponding to the calling LMR party and called MCPTT party and an SDP offer containing one or more media types. If available, the LMR party homed in the IWF may also include a functional alias. The following parameters are also included that describe the IWF's choices:
- the encryption algorithm;
- the encryption mode (encrypted or not)
- an indication of whether the LMR user is requesting the floor, and if the MCPTT client is requesting the floor, location information of the calling MCPTT client may be provided;
- requested commencement mode (manual in this case); and
- an indication of whether the call is to be full or half duplex (whether to establish floor control).
2. The MCPTT server checks whether the MCPTT user at the MCPTT client is authorized and able to receive the private call. Because the IWF private call request is requesting manual commencement mode, the MCPTT server also checks whether the MCPTT user at the MCPTT client is authorized to receive a call in manual commencement mode. If the MCPTT private call request contains a functional alias instead of an MCPTT ID as called party, the MCPTT server shall resolve the functional alias to the corresponding MCPTT ID(s) for which the functional alias is active. The MCPTT server shall also check whether MCPTT client 1 is allowed to use the functional alias of MCPTT client 2 to setup a private call and whether MCPTT client 2 is allowed to receive a private call from MCPTT client 1 using the functional alias. If authorized, the MCPTT server proceeds with step 3.
3a. The MCPTT server responds with a functional alias resolution response message that contains the resolved MCPTT ID back to the IWF.
3b. If the MCPTT server replies with a MCPTT functional alias resolution response message, the IWF abandons the first MCPTT private call request in step 1 and sends a new MCPTT private call request towards the resolved MCPTT ID.
4. If authorized, the MCPTT server sends the MCPTT private call request towards the MCPTT client, including the original parameters with or without the location of the calling party and offering the same media types or a subset of the media types contained in the initial received request as per 3GPP TS 23.379 [7].
NOTE 3: How the IWF private call request is forwarded to the LMR system is out of scope of the present document.
5. The MCPTT client may report failure with an MCPTT private call response to the MCPTT server. The response may include one or more alternatives to the parameter values contained in step 3. If the MCPTT client does not report failure, the process proceeds with step 6.
6. The MCPTT server forwards the MCPTT private call response to the IWF. If the result parameter indicates failure, the IWF may abandon the call. If the parameters in the IWF private call response are acceptable to the IWF, then the IWF can send a new IWF private call request with the new parameters to the MCPTT server and behaves according to those parameters. The IWF may choose to end the call rather than continue with the new parameters.
7. The MCPTT client sends an MCPTT ringing to the MCPTT server while waiting for the call to be accepted by the MCPTT user.
8. The MCPTT server sends an IWF ringing to IWF the while waiting for the call to be accepted.
9. Once the call has been accepted by the called user, the MCPTT client sends an MCPTT private call response to the MCPTT server. The IWF private call response indicates that the IWF does support one of the requested media types.
10. The MCPTT sends the IWF private call response to the IWF.
11. The MCPTT client has successfully established media plane for communication to the IWF. The LMR system initiating the call is responsible of granting the floor, solving competing floor requests and issuing floor revoked indications.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.4.4 Private call release
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.4.4.1 MCPTT client initiated
|
The procedure describes the case where an MCPTT client requests release of an ongoing MCPTT private call (with or without floor control) that was established in either of the two commencement modes (manual or automatic). This subclause is based upon the subclauses for MCPTT private call release in 3GPP TS 23.379 [7], subclauses 10.7.2.2.3.1 and 10.7.2.3.3.
Procedures in figure 10.4.4.1-1 are the basic signalling control plane procedures for the MCPTT client initiating the release of an ongoing interworked private call.
Pre-conditions:
1. The MCPTT user on the MCPTT client is already registered for receiving MCPTT service and is involved in a private call with an LMR user via the IWF with or without floor control and established either in manual or automatic commencement mode, as described in subclause 10.4.2 and subclause 10.4.3.
Figure 10.4.4.1-1: Private call release – client initiated
1. The user at the MCPTT client would like to release an ongoing interworked private call with the LMR user.
2. The MCPTT client sends an MCPTT private call end request towards the MCPTT server (via SIP core) for tearing down the private call with the other client. Depending on the reason of the release, the MCPTT client may include additional application specific data in the MCPTT private call end request.
3. The MCPTT server sends the corresponding IWF call end request towards the IWF, addressed to the MCPTT client ID specified in the original MCPTT private call end request.
NOTE: The LMR user is also notified about the release of the private call. How the LMR user is notified is outside the scope of the present document.
4. The IWF acknowledges the IWF call end request with an IWF call end response sent towards the MCPTT server.
5. After receiving the MCPTT private call end request acknowledgement from the IWF, the MCPTT server generates an acknowledgement for the MCPTT client's MCPTT private call end request.
6. The MCPTT client and the IWF release all the media plane resources used for the private call. Further, if the private call was established with floor control, floor control resources are released and the MCPTT client cannot make further requests for floor control or send media.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.4.4.2 MCPTT server initiated
|
The procedure describes the case where an MCPTT server terminates an ongoing interworked private call (with or without floor control) that was established in either of the two commencement modes (manual or automatic). The conditions causing the MCPTT server to terminate the call could include expiry of the MCPTT administrator configured maximum duration for MCPTT private calls or expiry of the maximum time permitted for an MCPTT private call without transmission/reception. This subclause is based upon the subclauses for MCPTT private call release in 3GPP TS 23.379 [7], subclauses 10.7.2.2.3.2 and 10.7.2.3.3.
Procedures in figure 10.4.4.2-1 are the basic signalling control plane procedures for the MCPTT server initiating termination of an ongoing interworked private call.
Pre-conditions:
1. The MCPTT user on the MCPTT client is already registered for receiving MCPTT service and is involved in a private call with an LMR user via the IWF with or without floor control and established either in manual or automatic commencement mode, as described in subclause 10.4.2 and subclause 10.4.3.
Figure 10.4.4.2-1: End private call – server initiated
1. Upon conditions to terminate call e.g., MCPTT administrator configured maximum duration for MCPTT private calls expiry or time out due to MCPTT private call without transmission/reception, the MCPTT server decides to initiate termination of an ongoing interworking private call between the MCPTT client and the LMR user.
2a. The MCPTT server sends an MCPTT private call end request towards the MCPTT client (via SIP core) for tearing down the private call.
2b. The MCPTT server sends a corresponding IWF call end request towards the MCPTT client identity associated with the LMR user
3. The MCPTT user at the MCPTT client is notified about the termination of the private call.
NOTE: The LMR user is also notified about the termination of the private call. How the LMR user is notified is outside the scope of the present document.
4. The MCPTT client and the IWF acknowledge the request.
5. The MCPTT client and the IWF release all the media plane resources used for the private call. Further, if the private call was established with floor control, floor control resources are released and the MCPTT client cannot make further requests for floor control or send media.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.4.4.3 LMR user initiated
|
The procedure describes the case where either an LMR user or the LMR system is requesting to release an ongoing interworked private call (with or without floor control) and the call established in either of the two commencement modes (manual or automatic). This subclause is based upon the subclauses for MCPTT private call release in 3GPP TS 23.379 [7], subclauses 10.7.2.2.3.1 and 10.7.2.3.3.
Procedures in figure 10.4.4.3-1 are the basic signalling control plane procedures for the LMR user, via the IWF, initiating the release of an ongoing interworked private call.
Pre-conditions:
1. The MCPTT user on the MCPTT client is already registered for receiving MCPTT service and is involved in a private call with an LMR user via the IWF with or without floor control and established either in manual or automatic commencement mode, as described in subclause 10.4.2 and subclause 10.4.3.
Figure 10.4.4.3-1: Private call release – IWF initiated
1. The LMR system would like to release an ongoing interworked private call with the MCPTT user.
2. The IWF sends an IWF call end request towards the MCPTT server for tearing down the private call with the MCPTT client. Depending on the reason of the release, the IWF may include additional application specific data in the IWF private call end request.
3. The MCPTT server sends the corresponding MCPTT private call end request towards the MCPTT client specified in the original IWF call end request.
4. The MCPTT user is notified about the release of the private call. If additional application specific data is present in the MCPTT private call end request the MCPTT client may react depending on the content of the additional application specific data.
NOTE: The reaction of the MCPTT client on receiving additional application specific data is out of scope of the present document. It could be for example just displaying the content of the additional application specific data or notifying the user at the terminating client of a certain event.
5. The MCPTT client acknowledges the MCPTT private call end request.
6. After receiving the MCPTT private call end request acknowledgement from the MCPTT client, the MCPTT server generates an acknowledgement for the IWF's IWF call end request.
7. The MCPTT client and the IWF release all the media plane resources used for the private call. Further, if the private call was established with floor control, floor control resources are released and the MCPTT client cannot make further requests for floor control or send media.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.4.5 Encryption of private calls
|
Private calls can use MC media encryption (see 3GPP TS 33.180 [8]) between the IWF and the MCPTT client. A private call that uses an LMR vocoder may use LMR E2EE if the calling and called parties have previously been provisioned with the appropriate LMR E2EE keys.
NOTE: MC media encryption is independent of LMR E2EE techniques. MC media encryption can be applied in addition to LMR E2EE.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5 Floor control
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.1 General
|
Floor control for interworking applies to both private call and group call.
Floor control involving a single MCPTT server is described in 3GPP TS 23.379 [7]. Floor control involving multiple MCPTT servers is also described in 3GPP TS 23.379 [7] in that a primary MCPTT server is interconnected to a partner MCPTT server. Subclause 10.5.2 describes information flows for floor control between an MCPTT server and an IWF, and are based on those defined interconnection in 3GPP TS 23.379 [7]. Subclause 10.5.3 describes aspects of floor control that apply to interworking groups and interworking private calls. Subclauses 10.5.4/10.5.6 and 10.5.5/10.5.7 describe general cases of floor control on an interworking group defined in the LMR system and in the MCPTT system respectively, where the partner system has been configured to apply/not apply local filtering of floor control requests before communicating with the primary system. Subclauses 10.5.9 and 10.5.10 describe general cases of floor control in a private call, where the controlling role is taken by the LMR system and the MCPTT system respectively.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.2 Information flows for floor control
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.2.1 General
|
The following sections describe information flows for interworking floor control.
In the following information flows the MCPTT ID and its associated functional alias represents the LMR user, the IWF, or the MCPTT user depending on the interworking methods being used and the message source/destination.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.2.2 IWF floor request
|
Table 10.5.2.2-1 describes the information flow IWF floor request, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to request the floor for media transfer.
Table 10.5.2.2-1: IWF floor request
Information element
Status
Description
MCPTT ID
M
Requester identity
Functional alias
O
Functional alias of the requester
Floor priority
M
Priority of the request
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Location
O
Location information of requester
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.2.3 IWF floor granted
|
Table 10.5.2.3-1 describes the information flow IWF floor granted, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate that a request for floor is granted and media transfer is possible.
Table 10.5.2.3-1: IWF floor granted
Information element
Status
Description
MCPTT ID
M
Granted party identity
Functional alias
O
Functional alias of the granted party identity
Duration
M
The time for which the granted party is allowed to transmit
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Acknowledgement required
O
Indicates if acknowledgement from the floor participant is required
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.2.4 IWF floor rejected
|
Table 10.5.2.4-1 describes the information flow IWF floor rejected, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate that a request for the floor is rejected.
Table 10.5.2.4-1: IWF floor rejected
Information element
Status
Description
MCPTT ID
M
Rejected party identity
Functional alias
O
Functional alias of the rejected party
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Rejection cause
O
Indicates the cause for floor rejection
Acknowledgement required
O
Indicates if acknowledgement from the floor participant is required
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.2.5 IWF floor request cancel
|
Table 10.5.2.5-1 describes the information flow IWF floor request cancel, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to request cancelling the floor request from the floor request queue.
Table 10.5.2.5-1: IWF floor request cancel
Information element
Status
Description
MCPTT ID
M
Identity for the requester
Functional alias
O
Functional alias of the requester
List of MCPTT IDs
M
Target identity (Identities) whose floor request is to be cancelled
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.2.6 IWF floor request cancel response
|
Table 10.5.2.6-1 describes the information flow IWF floor request cancel response, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate the response for the floor request cancellation.
Table 10.5.2.6-1: IWF floor request cancel response
Information element
Status
Description
MCPTT ID
M
Identity of party that initiated the cancellation request
Functional alias
O
Functional alias of the requester
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Acknowledgement required
O
Indicates if acknowledgement from the floor participant is required
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.2.7 IWF floor request cancel notify
|
Table 10.5.2.7-1 describes the information flow IWF floor request cancel notify, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate the floor request is cancelled by the administrator/floor control server.
Table 10.5.2.7-1: IWF floor request cancel notify
Information element
Status
Description
MCPTT ID
M
Identity of the administrator
Functional alias
O
Functional alias of the administrator
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Acknowledgement required
O
Indicates if acknowledgement from the floor participant is required
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.2.8 IWF floor idle
|
Table 10.5.2.8-1 describes the information flow IWF floor idle, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate that a session is in idle status, i.e. the floor is not granted to any party.
Table 10.5.2.8-1: IWF floor idle
Information element
Status
Description
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Acknowledgement required
O
Indicates if acknowledgement from the floor participant is required
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.2.9 IWF floor release
|
Table 10.5.2.9-1 describes the information flow IWF floor release, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate the media transfer is completed and the floor is released.
Table 10.5.2.9-1: IWF floor release
Information element
Status
Description
MCPTT ID
M
Identity of party that released the floor
Functional alias
O
Functional alias of the party that released the floor
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.2.10 IWF floor taken
|
Table 10.5.2.10-1 describes the information flow IWF floor taken, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate the floor is granted to another MCPTT user.
Table 10.5.2.10-1: IWF floor taken
Information element
Status
Description
MCPTT ID
M
Identity for the granted party
Functional alias
O
Functional alias for the granted party
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Permission to request the floor
O
Indicates whether receiving parties are allowed to request the floor or not (e.g. broadcast call).
Acknowledgement required
O
Indicates if acknowledgement from the floor participant is required
Location
O
Location information of the granted party
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.2.11 IWF floor revoked
|
Table 10.5.2.11-1 describes the information flow IWF floor revoked, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate the floor is revoked from its current holder (the floor participant who was granted the floor).
Table 10.5.2.11-1: IWF floor revoked
Information element
Status
Description
MCPTT ID
M
Revoked party identity
Functional alias
O
Functional alias of the revoked party
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Acknowledgement required
O
Indicates if acknowledgement from the floor participant is required
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.2.12 IWF floor acknowledgement
|
Table 10.5.2.12-1 describes the information flow IWF floor acknowledgement, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to provide an acknowledgement if the acknowledgement is required in the received floor control message.
NOTE: The floor acknowledgement flow can be sent by the floor control server after each floor control information flow that includes an indication that an acknowledgement is required.
Table 10.5.2.12-1: IWF floor acknowledgement
Information element
Status
Description
MCPTT ID
M
Identity of the sender.
Functional alias
O
Functional alias of the sender
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.2.13 IWF queue position request
|
Table 10.5.2.13-1 describes the information flow IWF queue position request, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to request the position in the floor request queue. The MCPTT server and the MCPTT client that support queuing of the floor control requests shall support this information flow.
Table 10.5.2.13-1: IWF queue position request
Information element
Status
Description
MCPTT ID
M
Identity of party whose floor position is requested
Functional alias
O
Functional alias of the party whose floor position is requested
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.2.14 IWF queue position info
|
Table 10.5.2.14-1 describes the information flow IWF queue position info, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate the floor request is queued and the queue position to the floor requesting UE.
Table 10.5.2.14-1: IWF queue position info
Information element
Status
Description
MCPTT ID
M
Identity of party whose floor position is provided
Functional alias
O
Functional alias of the party whose floor position is provided
Queue position info
M
Position of the queued floor request in the queue
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Acknowledgement required
O
Indicates if acknowledgement from the floor participant is required
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.2.15 IWF unicast media stop request
|
Table 10.5.2.15-1 describes the information flow IWF unicast media stop request, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate that the unicast media flow of the designated communication does not need to be sent to the client indicated by the MCPTT ID.
Table 10.5.2.15-1: IWF unicast media stop request
Information element
Status
Description
MCPTT ID
M
Identity of the requester
Functional alias
O
Functional alias of the requester
Source identifier
O
Identifies the communication whose media flow is to be stopped, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.2.16 IWF unicast media resume request
|
Table 10.5.2.16-1 describes the information flow IWF unicast media resume request, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used by the floor control server to request that the unicast media flow of the designated communication is to be sent to the client indicated by the MCPTT ID.
Table 10.5.2.16-1: IWF unicast media resume request
Information element
Status
Description
MCPTT ID
M
Identity of the requester
Functional alias
O
Functional alias of the requester
Source identifier
O
Identifies the communication whose media flow is to be resumed, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.2.17 IWF floor talker ID update
|
Table 10.5.2.17-1 describes the information flow IWF floor talker ID update, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate that the talker ID has changed for the current MCPTT user granted the floor.
Table 10.5.2.17-1: IWF floor talker ID update
Information element
Status
Description
MCPTT ID
M
Identity for the party using the floor
Functional alias
O
Functional alias associated with the MCPTT ID using the floor
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.3 Interworking floor control
|
3GPP TS 23.379 [7], subclause 10.9.1.4.1 describes floor control involving groups in multiple MCPTT systems where floor control arbitration resides with the primary MCPTT server and all floor control messages are routed to that primary MCPTT server. The group is homed on the primary MCPTT server.
An interworking group can be homed on the MCPTT server or on the LMR system. When the group is homed on the MCPTT server the floor control server is on this MCPTT server. When the group is homed on the LMR system the floor control server is represented by the IWF.
The primary MCPTT system of an MCPTT group is defined by configuration and identified by the MC service group ID.
3GPP TS 23.379 [7], subclause 10.9.1.4.2 describes floor control involving groups in multiple MCPTT systems where the partner MCPTT system filters its MCPTT users' floor requests before communicating with the floor control server of the primary MCPTT system. When an MCPTT system is interworking with an IWF, depending on where the group is homed the MCPTT server, or the IWF can filter floor control requests in the same way as an interconnected MCPTT system.
In a private call, one of the IWF or MCPTT server acts as the controlling floor control server within the call, and manages arbitration of floor control requests received from both users in the call. The entity (MCPTT server or IWF) that does not fulfil the controlling role shall send all floor control requests from its served call participant to the controlling floor control server without filtering.
NOTE: Allocation of controlling floor control server functionality to the MCPTT server or IWF may be according to the system within which the call originated, or by some other means.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.5.4 Floor override without using floor revoked on an interworking group
|
This procedure describes the case where a transmitting radio cannot be signalled that the floor has been taken or revoked. Within the context of interworking between MCPTT and LMR systems, this condition can occur due to both MCPTT and LMR users obtaining the floor simultaneously, or the floor granted to an LMR user is taken by an MCPTT user.
Figure 10.5.4‑1 shows the high-level procedure where an MCPTT session is already established between the floor participants (with floor granted to an LMR user represented by the IWF) and the floor control server (with an override based on priority and configured to permit the transmission of overridden floor participant from the IWF). The group is defined in the MCPTT system and the MCPTT Server is the floor control server. Only two UEs involved in the session are shown for simplicity.
Pre-conditions:
1. The MCPTT floor control server has been configured to support override.
2. The override supported in this case permits both the overridden floor participant and the overriding floor participant to be transmitting.
3. An MCPTT session is established between an MCPTT client, the interworked system, and MCPTT server.
4. Session is ongoing.
Figure 10.5.4‑1: Floor override (overridden continues to transmit) during an interworking session
1. It is assumed that the floor participant B (represented by the IWF in figure 10.5.4‑1) has been given the floor and is transmitting voice media.
2. Floor participant A, having a floor priority which is relatively higher than that of floor participant B, wants to send voice media over the session.
3. Floor participant A sends a floor request message to the floor control server.
4. The floor control server determines to accept the floor request from floor participant A based on arbitration result e.g., according to the floor priority information that is received in the floor request message.
5a. Floor control server responds with a floor granted message to floor participant A.
5b. Floor control server sends a floor taken message to the other floor participants (via the IWF). Floor participant B continues transmitting the (overridden) voice media transmission.
NOTE 1: All other floor participants (not shown) that are part of this group call receive a floor taken message, so that the other floor participants learn who the newly granted talker (overriding) is.
6a. The floor granted causes the user of floor participant A to be notified.
6b. Floor participant B cannot be notified of the status because it is unable to receive the message and continues transmitting.
7. Floor participant A (overriding) starts sending voice media over the session established beforehand.
NOTE 2: Floor participant B is still sending voice (overridden). The list of floor participants that receive the overriding, overridden, or both transmissions is based on configuration.
NOTE 3: When floor participant A stops transmitting, if floor participant B is still sending voice, then the floor is granted back to floor participant B and audio is routed to all current floor participants.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.