hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.1 General
|
When an MCPTT user using a ProSe-enabled UE wants to communicate with a specific MCPTT group using ProSe capabilities, the MCPTT client enables the use of the ProSe layer procedures for public safety, as specified in 3GPP TS 23.303 [7].
The MCPTT client obtains configuration data such as the user info ID of the calling MCPTT user and the ProSe Group IP multicast address and ProSe Layer-2 Group ID associated to the target MCPTT group (as described in clause 8.1.3.2 in 3GPP TS 23.280 [16]), and provides it to the ProSe layer. The ProSe Layer-2 Group ID of the target MCPTT group may be used by the ProSe layer as the target group info and the discovery group ID (defined in 3GPP TS 23.303 [7]).
Prior to the establishment of an off-network group call, a group member discovery procedure may be initiated to identify whether other members of the target MCPTT group are in the proximity of the calling MCPTT user, as described in the ProSe direct discovery for public safety use procedure in 3GPP TS 23.303 [7]. The establishment of an off-network group call using the ProSe capability is based on the one-to-many ProSe direct communication procedure for public safety use described in 3GPP TS 23.303 [7].
Off-network group calls can use pre-defined configuration information provided to MCPTT clients prior to the off-network group call or configuration information that is transmitted to MCPTT clients during group call setup or late entry procedures.
If off-network group configuration information is pre-defined (e.g. codec to be used) and provided to the MCPTT clients prior to the off-network group call (e.g. as part of group metadata), the MCPTT client will be able to participate in the off-network group call without needing to follow the group call setup or late joining procedures as they will be able to receive the media and signalling without the need for the announcement or invitation.
If off-network group configuration information is not pre-defined or provided, call parameters need to be transmitted to MCPTT clients via group call announcement or invitation.
NOTE: When the MCPTT client receives a message that is not addressed to either its MCPTT ID or to any MCPTT group of which the MCPTT client is an affiliated group member, the MCPTT client ignores the message.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.2 Information flows for group call in off-network
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.2.1 Group call announcement
|
Table 10.6.3.2.1-1 describes the information flow for the group call announcement from the MCPTT client to other MCPTT clients.
Table 10.6.3.2.1-1: Group call announcement
Information Element
Status
Description
MCPTT ID
M
The identity of the calling party
MCPTT group ID
M
The MCPTT group ID on which the call is to be conducted
Media type
M
Type of the media to be used for the call
Media codec
M
The media codec to be used for the call
Multi-cast port
M
Multicast port number for media
Floor control port number
M
Port number for floor control protocol
Announcement period
M
Period of the group call announcement
Encryption parameters
O
Encryption parameters to be used for the call, if the call is to be encrypted
Confirm mode indicator
O
Indicates whether the MCPTT group call is to be confirmed
Emergency indicator
O
Indicates that the MCPTT group call is an MCPTT emergency call
Imminent peril indicator
O
Indicates that the MCPTT group call is an MCPTT imminent peril call
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.2.2 MCPTT upgrade to emergency call
|
Table 10.6.3.2.2-1 describes the information flow for the MCPTT upgrade to emergency call from the MCPTT client to other MCPTT clients.
Table 10.6.3.2.2-1: MCPTT upgrade to emergency call
Information Element
Status
Description
MCPTT ID
M
The identity of the upgrading party
MCPTT group ID
M
The MCPTT group ID on which the call is to be conducted
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.2.3 MCPTT emergency group state cancel
|
Table 10.6.3.2.3-1 describes the information flow for the MCPTT emergency group state cancel from the MCPTT client to other MCPTT clients.
NOTE: In Rel-14 and Rel-13 versions of this specification the name of this information flow is "MCPTT emergency group cancel".
Table 10.6.3.2.3-1: MCPTT emergency group state cancel
Information Element
Status
Description
MCPTT ID
M
The identity of the cancelling party
MCPTT group ID
M
The MCPTT group ID which emergency state is to be cancelled
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.2.4 Response
|
Table 10.6.3.2.4-1 describes the information flow for the response.
Table 10.6.3.2.4-1: Response
Information Element
Status
Description
MCPTT ID
M
The identity of the called party
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.2.5 Void
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.2.6 Void
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.2.7 MCPTT upgrade to imminent peril call
|
Table 10.6.3.2.7-1 describes the information flow for the MCPTT upgrade to imminent peril call from the MCPTT client to other MCPTT clients.
Table 10.6.3.2.7-1: MCPTT upgrade to imminent peril call
Information Element
Status
Description
MCPTT ID
M
The identity of the upgrading party
MCPTT group ID
M
The MCPTT group ID of the group to be upgraded
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.2.8 MCPTT imminent peril group call cancel
|
Table 10.6.3.2.8-1 describes the information flow MCPTT imminent peril group call cancel from the MCPTT client to other MCPTT clients.
Table 10.6.3.2.8-1: MCPTT imminent peril group call cancel
Information Element
Status
Description
MCPTT ID
M
The identity of the cancelling party
MCPTT group ID
M
The MCPTT group ID on which the imminent peril is to be cancelled
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.3 Group call setup
|
The flow in figure 10 6.3.3-1 illustrates the control plane procedures for MCPTT group call establishment for off-network. The procedure describes how an MCPTT client initiates an MCPTT group call with other MCPTT client within the off-network radio coverage and how the group call is established.
Pre-conditions:
- It is assumed that information for ProSe direct communications corresponding to the mappings of MCPTT group ID and ProSe Layer-2 Group ID (see subclause 8.1.3.2 in 3GPP TS 23.280 [16]) are pre-configured;
- It is assumed that a multicast IP address and port for the call setup signalling are pre-configured;
- All messages exchanged between the MCPTT clients for the MCPTT group follows ProSe direct communications as defined in 3GPP TS 23.303 [7]; and
- The MCPTT users of MCPTT client 1, 2 and 3 belong to the same MCPTT group.
Figure 10.6.3.3-1: Off-network group call setup
1. MCPTT client 1 as the group call originator sends group call announcement message to the group. This message contains the following parameters such as MCPTT group ID, group call originator identity, media type, media codec, multicast port number for media, port number for floor control protocol, period of group call announcement, and any encryption key for the media encryption if needed, and optionally confirm mode indication.
NOTE 1: The group call announcement includes at least one common set of parameters and values for media transfer. Additional values per parameter will not be prohibited for the better user experience.
NOTE 2: By using the ProSe Layer-2 Group ID mapping with the MCPTT group ID, ProSe layer ensures that the messages sent for the corresponding MCPTT group are only received by its group's members.
2. MCPTT client 2, 3 join the group call. The MCPTT clients configure the parameters for media delivery by making use of the received parameters in group call announcement.
3. MCPTT client 2, 3 may send the response message to the group when the group call announcement from originator includes confirm mode indication. This message contains MCPTT ID.
4. MCPTT client 2, 3 recognize the group call originator through the group call announcement and MCPTT client 1 checks the participants of the group call through the received response message.
NOTE 3: Due to the movement of the participants (in and out of the radio coverage) during the off-network group call, the group call announcement message including parameters for media delivery is periodically sent.
NOTE 4: The participating MCPTT clients do not need to respond to the periodic group call announcement.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.4 Passive join to group call
|
Figure 10 6.3.4-1 illustrates the control plane procedures for the passive MCPTT client to join the on-going MCPTT group call. The passive MCPTT client does not initiate to establish an MCPTT group call, but receives the group call announcement to be transferred periodically. When receiving the announcement message with parameters for media transfer, the passive MCPTT client configures the parameter to receive the voice and joins the announced MCPTT group call.
This procedure happens after the MCPTT group call is established. The group call announcement including the parameters for the media transfer has been performed periodically, in order for the MCPTT client later to join the MCPTT group call.
The MCPTT client 4 enters the coverage of the MCPTT group call lately.
Figure 10.6.3.4-1: Passive join to group call
1. MCPTT client 2 sends the group call announcement message. This message contains parameters such as MCPTT group ID, group call originator identity, media type, media codec, multicast port number for media, port number for floor control protocol, any encryption key for the media encryption if needed, and optionally confirm mode indication.
NOTE 1: The group call announcement includes at least one common set of parameters and values for media transfer. Additional values per parameter will not be prohibited for the better user experience.
2. MCPTT client 4 configures the parameters for media transfer by making use of the received parameters in group call announcement.
3. MCPTT client 4 may send the response message to the group when the periodic group call announcement includes confirm mode indication. This message contains the MCPTT ID.
4. MCPTT client 1, 2, 3 check through the received response message that the MCPTT client 4 joins the group call. The MCPTT client 2, as the floor control arbitrator, may send a floor taken message.
NOTE 2: Due to the movement of the participants (in and out of the radio coverage) during the off-network group call, the group call announcement message including parameters for media delivery is periodically sent.
NOTE 3: The participating MCPTT clients do not need to respond to the periodic group call announcement.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.5 Join to ongoing group call when new entry member initiates the call with on-going group call id
|
Figure 10 6.3.5-1 illustrates the control plane procedures for an MCPTT client to join an on-going MCPTT group call. When entering the coverage of on-going group call, new MCPTT client may send group call setup announcement message with on-going group call id. Upon receiving the group call setup announcement, the MCPTT client as a participant of on-going MCPTT group call sends parameters for media transfer to the newly entered MCPTT client (entrant) to join the on-going MCPTT group call. When receiving the parameters for media transfer of on-going MCPTT group call, the MCPTT client configures the parameters to receive the voice and becomes the participant of the on-going MCPTT group call.
Figure 10.6.3.5-1: Late entry join when receiving MCPTT group call announcement with on-going MCPTT group ID
1. MCPTT client 4 enters the coverage of the on-going MCPTT group call.
2. The new entry of MCPTT client 4 sends group call setup announcement with MCPTT group call id.
3. MCPTT client 1 as a participant of on-going MCPTT group call acknowledges that on-going MCPTT group call exists with MCPTT group call id sent by MCPTT client 4 and sends parameters for media transfer to MCPTT client 4.
4. MCPTT client 4 may send a response message.
5. MCPTT client 4 sets the parameters for media delivery in the on-going MCPTT group call.
MCPTT client 4 joins and becomes participants of the on-going MCPTT group call.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.6 Immediate group call announcement to join an ongoing group call
|
Figure 10.6.3.6-1 illustrates the control plane procedures for an MCPTT client to immediately join an on-going MCPTT group call. Upon the detection of a new entrant, the MCPTT client that is the current talker (floor arbitrator) immediately sends the group call announcement. When receiving the group call announcement message with parameters for media transfer, that MCPTT client configures the parameters to receive the voice and joins the on-going MCPTT group call.
Pre-conditions:
1. There is on-going group call. MCPTT client 1 is the current talker and therefore the floor arbitrator.
Figure 10.6.3.6-1: Immediate group call announcement to join an ongoing group call
1. MCPTT client 4 enters the coverage of the on-going MCPTT group call.
2. The entry of MCPTT client 4 is detected by the current participants.
3. Since MCPTT client 1 is the current talker (floor arbitrator), MCPTT client 1 immediately sends the group call announcement with the call parameters to the group.
4. MCPTT client 4 may send a response message.
5. MCPTT client 4 sets the parameters for the group call.
6. All participants are now considered part of the on-going group call.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.7 Group call release due to inactivity
|
If the on-going MCPTT group call is inactive for a specific duration, the participating MCPTT clients release the MCPTT group call by themselves.
NOTE: Inactivity time can be set according to the policy of MCPTT service provider.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.8 Broadcast group call
|
Group call on group-broadcast group and user-broadcast group are handled without distinction in off-network.
Figure 10 6.3.8.1-1 illustrates the control plane procedures for broadcast group call in off-network.
Figure 10.6.3.8.1-1: Broadcast group call in off-network
1. An authorized MCPTT client 1 initiates broadcast group call setup as described in subclause 10.6.3.3. The group call announcement message includes the indication of broadcast group call.
2. The MCPTT client 1 initiating broadcast group call starts to transmit media.
NOTE: Other clients of group member are not allowed to transmit media in broadcast group call.
3. The broadcast group call is released as described in subclause 10.6.3.7.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.9 Emergency and imminent peril procedures
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.9.1 Emergency group call
|
The off-network emergency group call is a special case of off-network (non-emergency) group call as defined in subclauses 10.6.3.2, 10.6.3.3, 10.6.3.4, 10.6.3.5, 10.6.3.6 and 10.6.3.7. The following are modifications to the aforementioned subclauses to support MCPTT emergency group calls:
- As a pre-condition, the client initiating the emergency call has previously been provisioned with an MCPTT group designated as the MCPTT emergency group. The MCPTT client initiates MCPTT emergency group calls on this group. Alternatively, the MCPTT client could have been provisioned for emergency behaviour on the selected MCPTT group.
- The group call announcement contains an indication that the MCPTT group call is to be an MCPTT emergency call regardless of whether or not the MCPTT client is in call. Group call participants learn of the MCPTT group's in-progress emergency state from the indication.
- Every call initiated by the MCPTT client will be an emergency call while the MCPTT client is in MCPTT emergency state.
- The MCPTT client enters the MCPTT emergency state when initiating an MCPTT emergency call or MCPTT emergency alert. Only the MCPTT user of the MCPTT client can clear the client's local MCPTT emergency state.
- The MCPTT group in-progress emergency state is cancelled when the call ends.
- The MCPTT user who initiated an emergency call, or upgraded a group call to an emergency call, or an authorized user, may cancel the in-progress emergency state with an MCPTT emergency group state cancel message. The message is sent to the call participants.
- When the MCPTT group is no longer in the in-progress emergency state, every client returns its default value of ProSe Per Packet Priority.
- An MCPTT group call in-progress is upgraded to an emergency group call when the periodic group call announcement contains the emergency indicator.
- The value of ProSe Per Packet Priority is upgraded according to emergency state of MCPTT group call.
- An MCPTT group call becoming an emergency group call does not affect the state of other MCPTT call(s) in the client.
- The MCPTT group remains in the in-progress emergency state until the emergency group call ends or the in-progress emergency state is cancelled.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.9.2 MCPTT imminent peril
|
The off-network imminent peril group call is a special case of off-network (non-imminent peril) group call as defined in subclauses 10.6.3.2, 10.6.3.3, 10.6.3.4, 10.6.3.5, 10.6.3.6 and 10.6.3.7. The following are modifications to the aforementioned subclauses to support MCPTT imminent peril calls:
- As a pre-condition, the user initiating the imminent peril call has previously an MCPTT group to be used as the MCPTT imminent peril group. The MCPTT client initiates MCPTT imminent peril group calls on this group.
- The group call announcement contains an indication that the MCPTT group call is to be an MCPTT imminent peril call. Group call participants learn of the MCPTT group in-progress imminent peril condition from the indication.
- The MCPTT group in-progress imminent peril state is considered cancelled when the call ends.
- The originating MCPTT user of the in-progress imminent peril or an authorized user may cancel the in-progress imminent peril state with an MCPTT imminent peril group cancel. The message is sent to the call participants.
- When the MCPTT in-progress imminent peril is no longer in the in-progress imminent peril state, every MCPTT client returns its bearer to the priority it had prior to the in-progress imminent peril state.
- An MCPTT upgrade to imminent peril call is used to upgrade an MCPTT group call already in progress. The message is sent to all call participants so that they are aware of the in-progress imminent peril.
- The bearer is upgraded by all participants for the MCPTT group call already in progress when the MCPTT group call is upgraded to in-progress imminent peril state.
- An MCPTT imminent peril call puts the MCPTT group into the in-progress imminent peril state.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.6.3.9.3 MCPTT emergency alert (off-network)
|
The MCPTT service shall support the procedures and related information flows as specified in subclauses 10.10.2 of 3GPP TS 23.280 [5] with the following clarifications:
- The MC service client is the MCPTT client;
- The MC service server is the MCPTT server;
- The MC service group ID is the MCPTT Group ID; and
- The MC service user profile index is the MCPTT user profile index.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7 Private call
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.1 General
|
Private calls are enabled in both on-network and off-network.
Private calls can be setup in two different commencement modes, automatic commencement mode and manual commencement mode.
Private calls in on-network can be with or without floor control. Private calls in off-network are with floor control.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2 Private call in on-network
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.1 Information flows for private call in on-network
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.1.1 MCPTT private call request (MCPTT client to MCPTT server)
|
Table 10.7.2.1.1-1 describes the information flow MCPTT private call request from the MCPTT client to the MCPTT server.
Table 10.7.2.1.1-1: MCPTT private call request (MCPTT client to MCPTT server) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ID (see NOTE)
O
The MCPTT ID of the called party
Functional alias (see NOTE)
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
O
Media parameters of MCPTT client.
Requested commencement mode
O
An indication that is included if the user is requesting a particular commencement mode
Implicit floor request
O
An indication that the user is also requesting the floor.
Location information
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
NOTE: At least one identity shall be present. If both are present the MCPTT ID shall be used to route the call request and the functional alias is just for information.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.1.2 MCPTT private call request (MCPTT server to MCPTT server)
|
Table 10.7.2.1.2-1 describes the information flow MCPTT private call request from the MCPTT server to the MCPTT server.
Table 10.7.2.1.2-1: MCPTT private call request (MCPTT server to MCPTT server) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ID
M
The MCPTT ID of the called party
Functional alias
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.
Requested commencement mode
O
An indication of the commencement mode to be used.
Implicit floor request
O
An indication that the user is also requesting the floor.
Requested priority
O
Priority level requested for the call.
Forwarding indicator
O
Indicates whether the MCPTT private call request is a result of a call forwarding. (true/false)
Transfer indicator
O
Indicates that the MCPTT private call request is a result of a call transfer (true/false)
Location information
O
Location of the calling party
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
10.7.2.1.2a MCPTT private call request (MCPTT server to MCPTT client)
Table 10.7.2.1.2a describes the information flow MCPTT private call request from the MCPTT server to the MCPTT client.
Table 10.7.2.1.2a: MCPTT private call request (MCPTT server to MCPTT client) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ID
M
The MCPTT ID of the called party
Functional alias
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.
Requested commencement mode
O
An indication of the commencement mode to be used.
Implicit floor request
O
An indication that the user is also requesting the floor.
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
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.1.3 MCPTT private call response (MCPTT client to MCPTT server)
|
Table 10.7.2.1.3-1 describes the information flow MCPTT private call response from the MCPTT client to the MCPTT server.
Table 10.7.2.1.3-1: MCPTT private call response (MCPTT client to MCPTT server) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ID
O
The MCPTT ID of the called party
Functional alias
O
The functional alias of the called party
SDP answer
M
Media parameters selected
Requested commencement mode
O
An indication of the commencement mode to be used.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.1.4 MCPTT private call response
|
Table 10.7.2.1.4-1 describes the information flow MCPTT private call response from the MCPTT server to the MCPTT server and the MCPTT server to the MCPTT client.
Table 10.7.2.1.4-1: MCPTT private call response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ID
O
The MCPTT ID of the called party
Functional alias
O
The functional alias of the called party
Acceptance confirmation
O
An indication whether the user has positively accepted the call.
SDP answer
M
Media parameters selected
10.7.2.1.4a MCPTT private call end request
Table 10.7.2.1.4a-1 describes the information flow MCPTT private call end request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client.
Table 10.7.2.1.4a-1: MCPTT private 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
Private call end reason
O
Indicate that the reason to end the call, e.g., due to migration, or due to user request.
10.7.2.1.4b MCPTT private call end response
Table 10.7.2.1.4b-1 describes the information flow MCPTT private call end response from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client.
Table 10.7.2.1.4b-1: MCPTT private call end response information elements
Information Element
Status
Description
MCPTT ID
M
In the direction MCPTT client to MCPTT server this shall be the MCPTT ID of the responding MCPTT client.
In the direction MCPTT server to MCPTT client this shall be the MCPTT ID of the destination MCPTT client
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.1.5 MCPTT emergency private call request (MCPTT client to MCPTT server)
|
Table 10.7.2.1.5-1 describes the information flow MCPTT emergency private call request from the MCPTT client to the MCPTT server.
Table 10.7.2.1.5-1: MCPTT emergency private call request (MCPTT client to MCPTT server) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ID (see NOTE)
O
The MCPTT ID of the called party
Functional alias (see NOTE)
O
The functional alias of the called party
Emergency indicator
M
Indicates that the private call request is an MCPTT emergency call
Alert indicator
M
Indicates whether an emergency alert is to be sent
Requested commencement mode
O
An indication of the commencement mode to be used.
Implicit floor request
O
An indication that the user is also requesting the floor.
SDP offer
M
Media parameters of MCPTT client.
Requested priority
O
Priority level requested for the call.
Location information
O
Location of the calling party
NOTE: Only one identity shall be present.
10.7.2.1.5a MCPTT emergency private call request (MCPTT server to MCPTT client)
Table 10.7.2.1.5a-1 describes the information flow MCPTT emergency private call request from the MCPTT server to the MCPTT client.
Table 10.7.2.1.5a-1: MCPTT emergency private call request (MCPTT server to MCPTT client) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ID
M
The MCPTT ID of the called party
Emergency indicator
M
Indicates that the private call request is an MCPTT emergency call
Alert indicator
M
Indicates whether an emergency alert is to be sent
Requested commencement mode
O
An indication of the commencement mode to be used.
Implicit floor request
O
An indication that the user is also requesting the floor.
SDP offer
M
Media parameters of MCPTT client.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.1.6 MCPTT progress indication
|
Table 10.7.2.1.6-1 describes the information flow MCPTT progress indication from the MCPTT server to the MCPTT client.
Table 10.7.2.1.6-1: MCPTT progress indication 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
Progress indication
O
Indication to the caller.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.1.7 MCPTT ringing
|
Table 10.7.2.1.7-1 describes the information flow MCPTT ringing from the MCPTT client to the MCPTT server, from the MCPTT server to the MCPTT server, and from the MCPTT server to the MCPTT client.
Table 10.7.2.1.7-1: MCPTT 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.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.1.8 MCPTT functional alias resolution response
|
Table 10.7.2.1.8-1 describes the information flow MCPTT functional alias resolution response from the MCPTT server to the MCPTT client.
Table 10.7.2.1.8-1: MCPTT functional alias resolution response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
MCPTT ID
M
The corresponding MCPTT ID of the called functional alias
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.1.9 MCPTT private call cancel request (MCPTT server to MCPTT client)
|
Table 10.7.2.1.9-1 describes the information flow MCPTT private call cancel request from the MCPTT server to the MCPTT client.
Table 10.7.2.1.9-1: MCPTT private call cancel request (MCPTT server to MCPTT client)
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
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.1.10 MCPTT private call cancel response (MCPTT client to MCPTT server)
|
Table 10.7.2.1.10-1 describes the information flow MCPTT private call cancel response from the MCPTT client to the MCPTT server.
Table 10.7.2.1.10-1: MCPTT private call cancel response (MCPTT client to MCPTT server)
information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the called party
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.1.11 MCPTT emergency private call floor remote trigger (MCPTT client to MCPTT server)
|
Table 10.7.2.1.11-1 describes the information flow MCPTT emergency private call floor remote trigger, from the MCPTT client to the MCPTT server, to trigger the target MCPTT client, who has initiated the emergency communication, to send a floor request.
Table 10.7.2.1.11-1: MCPTT emergency private call floor remote trigger information elements
(MCPTT client to MCPTT server)
Information element
Status
Description
MCPTT ID
M
The identity of the requester, e.g. dispatcher
Functional alias
O
Functional alias of the requester
MCPTT ID
M
The identity of the target, who is triggered to send a floor request and automatically open the microphone
Functional alias
O
Functional alias of the target
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.1.12 MCPTT emergency private call floor remote trigger (MCPTT server to MCPTT client)
|
Table 10.7.2.1.12-1 describes the information flow MCPTT emergency private call floor remote trigger, from the MCPTT server to the target MCPTT client, who has initiated the emergency communication, to send a floor request.
Table 10.7.2.1.12-1: MCPTT emergency private call floor remote trigger information elements
(MCPTT server to MCPTT client)
Information element
Status
Description
MCPTT ID
M
The identity of the requester, e.g. dispatcher
Functional alias
O
Functional alias of the requester
MCPTT ID
M
The identity of the target, who is triggered to send a floor request and automatically open the microphone
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.2 Private call within one MCPTT system
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.2.1 Private call setup in automatic commencement mode
|
The procedure focuses on the case where an MCPTT user is initiating an MCPTT private call for communicating with another MCPTT user, with or without floor control enabled, in an automatic commencement mode.
Procedures in figure 10.7.2.2.1-1 are the basic signalling control plane procedures for the MCPTT client initiating establishment of MCPTT private call with the chosen MCPTT user.
Pre-conditions:
1. The calling MCPTT user has selected automatic commencement mode for the call; or
2. The called MCPTT client is set to automatic commencement mode.
3. Optionally, MCPTT client 1 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.7.2.2.1-1: Private call setup in automatic commencement mode– MCPTT users in the same MCPTT system
1. MCPTT users on MCPTT client 1 and MCPTT client 2 are already registered for receiving MCPTT service, as per procedure in subclause 10.2.
2. User at MCPTT client 1 would like to initiate an MCPTT private call for the chosen MCPTT user. The MCPTT user at MCPTT client 1 may include a functional alias used within the MCPTT private call. For a private call with floor control, floor control is to be established.
3. MCPTT client 1 sends an MCPTT private call request towards the MCPTT server (via SIP core) using a service identifier as defined in 3GPP TS 23.228 [5] for MCPTT, for establishing a private call with the chosen MCPTT user. The MCPTT private call request contains the MCPTT ID or the functional alias of the invited user, an SDP offer containing one or more media types. For a private call with floor control, the MCPTT private call request also contains an element that indicates that MCPTT client 1 is requesting the floor. The MCPTT client 1 may include a Requested commencement mode that indicates that the call is to be established in automatic commencement mode if automatic commencement mode is requested by the initiating user.
NOTE 1: As part of this step, MCPTT client 1 and MCPTT client 2 set up a security association (when no functional alias is present), if end-to-end encryption is used for this call.
4. 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, proceed with step 5. Otherwise, the MCPTT server checks whether the MCPTT user at MCPTT client 1 is authorized to initiate the private call, and that MCPTT user at MCPTT client 2 is authorized to receive the private call. If the MCPTT private call request requested automatic commencement mode then the MCPTT server also checks whether the MCPTT user at MCPTT client 1 is authorized to initiate a private call in automatic commencement mode and proceed with step 6.
NOTE 2: Depending on implementation the MCPTT server can apply additional call restrictions and decide whether the call is allowed to proceed with the resolved MCPTT ID(s) (e.g. whether the MCPTT ID is within the allowed area of the functional alias). If the MCPTT server detects that the functional alias used as the target of the private call request is simultaneously active for multiple MCPTT users, then the MCPTT server can proceed by selecting an appropriate MCPTT ID based on some selection criteria (e.g. current location of the initiating user to determine the dispatcher who is responsible for the related geographic area). The selection of an appropriate MCPTT ID is left to implementation. This selection criteria can include rejection of the call, if no suitable MCPTT ID is selected.
5a. The MCPTT server responds with a functional alias resolution response message that contains the resolved MCPTT ID back to MCPTT client 1.
5b. 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 3 and sends a new MCPTT private call request towards the resolved MCPTT ID.
NOTE 3: MCPTT client 1 and MCPTT client 2 set up a security association for the media, if end-to-end encryption is used for this call.
6. MCPTT server may provide a progress indication to MCPTT client 1 to indicate progress in the call setup process.
NOTE 4: Step 6 can occur at any time following step 5b, and prior to step 10.
7. If authorized, MCPTT server includes information that it communicates using MCPTT service, offers the same media types or a subset of the media types contained in the initial received request, includes the requested automatic commencement mode indication based on a requested automatic commencement mode by the calling user or based upon the setting of the called MCPTT client and sends the corresponding MCPTT private call request towards the MCPTT client 2, including the MCPTT ID and, if available, the functional alias of the calling MCPTT user 1. If the called MCPTT user has registered to the MCPTT service with multiple MCPTT UEs and has designated the MCPTT UE for receiving the private calls, then the incoming MCPTT private call request is delivered only to the designated MCPTT UE.
8. The receiving MCPTT client 2 notifies the user about the incoming private call and displays the functional alias of calling MCPTT user 1.
9. The receiving MCPTT client 2 accepts the private call automatically, and an MCPTT private call response is sent to the MCPTT server (via SIP core).
10. Upon receiving the MCPTT private call response from MCPTT client 2 accepting the private call request, the MCPTT server informs the MCPTT client 1 about successful call establishment.
11. MCPTT client 1 and MCPTT client 2 have successfully established media plane for communication and either user can transmit media. For successful call establishment for private call with floor control request from MCPTT client 1, floor participant at MCPTT client 1 is granted floor by the floor control server, giving it permission to transmit. At the same time floor participant at MCPTT client 2 is informed by the floor control server that floor is taken.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.2.2 Private call setup in manual commencement mode
|
10.7.2.2.2.1 Description
Figure 10.7.2.2.2.2-1 describes the basic procedure for the MCPTT client initiating an MCPTT private call that uses manual commencement mode. The flow may use a floor request in the MCPTT private call request indicating that the originator will be given the floor when the call starts and eliminates the need for a separate initial floor request message during media plane establishment. Alternatively the call initiation may be sent without the floor request, which allows the called party to request the floor first.
10.7.2.2.2.2 Procedure
Both clients are served by the primary MCPTT service provider in figure 10.7.2.2.2.2-1.
Pre-conditions:
1. The calling MCPTT user has selected manual commencement mode or has not specified a commencement mode for the call; and
2. The called MCPTT client is set to manual commencement mode.
3. Optionally, MCPTT client 1 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.7.2.2.2.2-1: MCPTT private call in manual commencement mode– MCPTT users in the same MCPTT system
1. MCPTT client 1 and MCPTT client 2 are both registered and their respective users, MCPTT user 1 and MCPTT user 2, are authenticated and authorized to use the MCPTT service, as per procedure in subclause 10.2.
2. MCPTT user at MCPTT client 1 would like to initiate an MCPTT private call for the selected MCPTT user. The MCPTT user at MCPTT client 1 may include a functional alias used within the MCPTT private call. For a private call with floor control, floor control is to be established. For private call without floor control, both users will have the ability to transmit without floor arbitration.
3. MCPTT client 1 sends an MCPTT private call request addressed to the MCPTT ID of MCPTT user 2 using an MCPTT service identifier as defined in 3GPP TS 23.228 [5] (possible for the SIP core to route the request to the MCPTT server). The MCPTT private call request contains the MCPTT ID or the functional alias of invited user and an SDP offer containing one or more media types. The MCPTT private call request may also contain a data element that indicates that MCPTT client 1 is requesting the floor, for a private call with floor control. The MCPTT client 1 may include a requested commencement mode that indicates that the call is to be established in manual commencement mode if manual commencement mode is requested by the initiating user.
NOTE 1: As part of this step, MCPTT client 1 and MCPTT client 2 set up a security association (when no functional alias is present), if end-to-end encryption is used for this call.
4. The MCPTT server confirms that both MCPTT users are authorized for the private call. MCPTT server verifies whether the provided functional alias, if present, can be used and has been activated for the user. 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. The MCPTT server checks the commencement mode setting of the called MCPTT client and also checks whether the MCPTT user at MCPTT client 1 is authorized to initiate a call in manual commencement mode.
NOTE 2: Depending on implementation the MCPTT server can apply additional call restrictions and decide whether the call is allowed to proceed with the resolved MCPTT ID(s) (e.g. whether the MCPTT ID is within the allowed area of the functional alias). If the MCPTT server detects that the functional alias used as the target of the private call request is simultaneously active for multiple MCPTT users, then the MCPTT server can proceed by selecting an appropriate MCPTT ID based on some selection criteria (e.g. current location of the initiating user to determine the dispatcher who is responsible for the related geographic area). The selection of an appropriate MCPTT ID is left to implementation. This selection criteria can include rejection of the call, if no suitable MCPTT ID is selected.
5a. If the MCPTT private call request contains a functional alias instead of an MCPTT ID as called party, the MCPTT server responds with a functional alias resolution response message that contains the resolved MCPTT ID back to MCPTT client 1.
5b. 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 3 and sends a new MCPTT private call request towards the resolved MCPTT ID.
NOTE 3: MCPTT client 1 and MCPTT client 2 set up a security association for the media, if end-to-end encryption is used for this call.
6. The MCPTT server includes information that it communicates using MCPTT service, offers the same media types or a subset of the media types contained in the initial received request and sends an MCPTT private call request for the call to MCPTT client 2, including the MCPTT ID and, if available, the functional alias of the calling MCPTT user 1. If the called MCPTT user has registered to the MCPTT service with multiple MCPTT UEs and has designated the MCPTT UE for receiving the private calls, then the incoming MCPTT private call request is delivered only to the designated MCPTT UE.
7. MCPTT server may provide a progress indication to MCPTT client 1 to indicate progress in the call setup process.
NOTE 4: Step 7 can occur at any time following step 5b, and prior to step 8b.
8a. The MCPTT user is alerted and may display the functional alias of calling MCPTT user 1. MCPTT client 2 sends an MCPTT ringing to the MCPTT server.
8b. The MCPTT server sends an MCPTT ringing to MCPTT client 1, indicating that MCPTT client 2 is being alerted.
9. MCPTT user 2 has accepted the call using manual commencement mode (i.e., has taken some action to accept via the user interface) which causes MCPTT client 2 to send an MCPTT private call response to the MCPTT server. If MCPTT user 2 has not accepted the incoming call, the MCPTT client 2 sends a call failure response to the MCPTT server without adding reason for call failure.
10. The MCPTT server sends an MCPTT private call response to MCPTT client 1 indicating that MCPTT user 2 has accepted the call, including the accepted media parameters.
11. The media plane for communication is established. Either user can transmit media individually when using floor control. For successful call establishment for private call with floor request from MCPTT client 1, the floor participant associated with MCPTT client 1 is granted the floor initially. At the same time the floor participant associated with MCPTT client 2 is informed that the floor is taken. The meaning of the floor request (give floor initially to originator [client 1], or give floor initially to target [client 2]) may be configurable. For a private call without floor control both users are allowed to transmit simultaneously.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.2.3 Private call release
|
10.7.2.2.3.1 Client initiated
The procedure focuses on the case where an MCPTT client is requesting to release an ongoing MCPTT private call (with or without floor control) and the call established in either of the two commencement modes (manual or automatic).
Procedures in figure 10.7.2.2.3.1-1 are the basic signalling control plane procedures for the MCPTT client initiating the release of an ongoing MCPTT private call.
Figure 10.7.2.2.3.1-1: Private call release – client initiated
1. It is assumed that MCPTT users on MCPTT client 1 and MCPTT client 2 are already registered for receiving MCPTT service and are involved in private call with or without floor control established either in manual or automatic commencement mode, as described in subclause 10.7.2.2.1 and subclause 10.7.2.2.2.
2. User at MCPTT client 1 would like to release an ongoing MCPTT private call with MCPTT client 2.
3. MCPTT client 1 sends an MCPTT private call end request towards the MCPTT server (via SIP core), for tearing down the private call with the other client.
4. MCPTT server sends the corresponding MCPTT private call end request towards the MCPTT client specified in the original MCPTT private call end request.
5. MCPTT user is notified about the release of the private call.
6. The receiving MCPTT client 2 acknowledges the MCPTT private call end request with an MCPTT private call end response.
7. After receiving the MCPTT private call end response from MCPTT client 2, the MCPTT server generates an acknowledgement for the MCPTT client 1's MCPTT private call end request.
8. MCPTT clients 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 MCPTT clients cannot make further requests for floor control or send media.
10.7.2.2.3.2 Server initiated
The procedure focuses on the case where an MCPTT server is terminating an ongoing MCPTT private call (with or without floor control) and the call established in either of the two commencement modes (manual or automatic), upon conditions to terminate call e.g., MCPTT administrator configured maximum duration for MCPTT private calls has expired or timed out due to MCPTT private call without transmission/reception.
Procedures in figure 10.7.2.2.3.2-1 are the basic signalling control plane procedures for the MCPTT server initiating termination of an ongoing MCPTT private call.
Figure 10.7.2.2.3.2-1: End private call – server initiated
1. It is assumed that MCPTT users on MCPTT client 1 and MCPTT client 2 are already registered for receiving MCPTT service and are involved in private call with or without floor control established either in manual or automatic commencement mode.
2. Upon conditions to terminate call e.g., MCPTT administrator configured maximum duration for MCPTT private calls has expired or timed out due to MCPTT private call without transmission/reception, the MCPTT server decides to initiate termination of an ongoing MCPTT private call between MCPTT client 1 and MCPTT client 2.
3. MCPTT server sends an MCPTT private call end request towards the MCPTT clients 1 and 2 (via SIP core), for tearing down the private call between them.
4. MCPTT users at client 1 and client 2 are notified about the termination of the private call.
5. The MCPTT private call end request receiving MCPTT clients 1 and 2 acknowledge the request with an MCPTT private call end response.
6. MCPTT clients 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 MCPTT clients cannot make further requests for floor control or send media.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.3 Private call within several MCPTT systems
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.3.1 Private call setup in automatic commencement mode – MCPTT users in multiple MCPTT systems
|
The procedure focuses on the case where an MCPTT user is initiating an MCPTT private call (automatic commencement mode) for communicating with MCPTT user in another MCPTT system with or without floor control enabled.
Procedures in figure 10.7.2.3.1-1 are the procedures for the MCPTT client initiating establishment of MCPTT private call with the chosen MCPTT user.
Pre-conditions:
1. The calling MCPTT user has selected automatic commencement mode for the call; or
2. The called MCPTT client is set to automatic commencement mode.
Figure 10.7.2.3.1-1: Private call setup in automatic commencement mode – users in multiple MCPTT systems
1. It is assumed that MCPTT users on MCPTT client 1 and MCPTT client 2 are already registered for receiving MCPTT service to their respective MCPTT service provider, as per procedure in subclause 10.2.
2. MCPTT user at MCPTT client 1 would like to initiate an MCPTT private call for the chosen MCPTT user. For a private call with floor control, floor control is to be established.
3. MCPTT client 1 sends an MCPTT private call request towards the home MCPTT server 1 (via SIP core) using a service identifier as defined in 3GPP TS 23.228 [5] for MCPTT, for establishing private call with the MCPTT client 2 registered at MCPTT service provider 2. The MCPTT private call request contains the MCPTT id of invited user and an SDP offer containing one or more media types. For a private call with floor control, the MCPTT private call request also contains an element that indicates that MCPTT client 1 is requesting the floor. If the private call request request the floor it may include location information. The MCPTT client 1 may include a requested commencement mode that indicates that the call is to be established in automatic commencement mode if automatic commencement mode is requested by the initiating user.
4. MCPTT server 1 checks whether the MCPTT user at MCPTT client 1 is authorized to initiate the private call. If the MCPTT private call request requested automatic commencement mode then the MCPTT server 1 also checks whether the MCPTT user at MCPTT client 1 is authorized to initiate a call in automatic commencement mode.
5. MCPTT server 1 may provide a progress indication to MCPTT client 1 to indicate progress in the call setup process.
NOTE: Step 5 can occur at any time following step 4, and prior to step 11.
6. If authorized, MCPTT server 1 includes information that it communicates using MCPTT service, offers the same media types or a subset of the media types contained in the initial received request, includes an automatic commencement mode indication if automatic commencement mode was requested by and authorised for the calling user and sends the corresponding MCPTT private call request towards the MCPTT system (via SIP core) of the MCPTT client specified in the original MCPTT private call request (MCPTT client 2) i.e., MCPTT server 2. If location information was included in the private call request, the MCPTT server checks the privacy policy of the MCPTT user to decide if the location information of MCPTT client 1 can be provided to the other user on the call (refer to Annex A.3 "Authorisation to provide location information to other MCPTT users on a call when talking").
7. MCPTT server 2 checks whether the MCPTT user at MCPTT client 2 is authorized to receive a private call.
8. MCPTT server 2 includes information that it communicates using MCPTT service, offers the same media types or a subset of the media types contained in the initial received request, includes a requested automatic commencement mode indication based on a requested automatic commencement mode by the calling user or based upon the setting of the called MCPTT client and sends the received MCPTT private call request towards the MCPTT client specified in the received MCPTT private call request (i.e., MCPTT client 2). If the called MCPTT user has registered to the MCPTT service with multiple MCPTT UEs and has designated the MCPTT UE for receiving the private calls, then the incoming MCPTT private call request is delivered only to the designated MCPTT UE.
9. The receiving MCPTT client 2 notifies the user about the incoming private call.
10. The receiving MCPTT client 2 accepts the private call automatically, and an acknowledgement is sent to the MCPTT server 1 (via SIP core and MCPTT server 2).
11. Upon receiving the MCPTT private call response from MCPTT client 2 accepting the private call request, MCPTT client 1 is informed about successful call establishment.
12. MCPTT client 1 and MCPTT client 2 have successfully established media plane for communication and either user can transmit media. For successful call establishment of a private call with implicit floor control request from MCPTT client 1, floor participant at MCPTT client 1 is granted floor by the floor control server at MCPTT service provider 1, giving it permission to transmit. At the same time floor participant at MCPTT client 2 is informed by the floor control server at MCPTT service provider 1 that the floor is taken.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.3.2 Private call setup in manual commencement mode – MCPTT users in multiple MCPTT systems
|
The procedure focuses on the case where an MCPTT user is initiating an MCPTT private call (manual commencement mode) for communicating with MCPTT user in another MCPTT system with or without floor control enabled.
Procedures in figure 10.7.2.3.2-1 are the procedures for the MCPTT client initiating establishment of MCPTT private call with the selected MCPTT user.
Pre-conditions:
1. The calling MCPTT user has selected manual commencement mode or has not specified a commencement mode for the call; and
2. The called MCPTT client is set to manual commencement mode.
Figure 10.7.2.3.2-1: Private call setup in manual commencement mode – users in multiple MCPTT systems
1. It is assumed that MCPTT users on MCPTT client 1 and MCPTT client 2 are already registered for receiving MCPTT service to their respective MCPTT service provider, as per procedure in subclause 10.2.
2. MCPTT user at MCPTT client 1 would like to initiate an MCPTT private call for the selected MCPTT user. For a private call with floor control, floor control is to be established.
3. MCPTT client 1 sends an MCPTT private call request towards the home MCPTT server 1 (via SIP core), for establishing private call with the MCPTT client 2 registered at MCPTT service provider 2. For a private call with floor control, the MCPTT private call request contains an element that indicates that MCPTT client 1 is requesting the floor. If the call request requests the floor the call request may include location information. The MCPTT client 1 may include a requested commencement mode that indicates that the call is to be established in manual commencement mode if manual commencement mode is requested by the initiating user.
4. MCPTT server 1 checks whether the MCPTT user at MCPTT client 1 is authorized to initiate the private call. The MCPTT server 1 also checks whether the MCPTT user at MCPTT client 1 is authorized to initiate a call in manual commencement mode.
5. If authorized, MCPTT server 1 sends the corresponding MCPTT private call request towards the MCPTT system (via SIP core) of the MCPTT client specified in the original MCPTT private call request (MCPTT client 2) i.e., MCPTT server 2. If location information was included in the private call request, the MCPTT server checks the privacy policy of the MCPTT user to decide if the location information of MCPTT client 1 can be provided to the other user on the call (refer to Annex A.3 "Authorisation to provide location information to other MCPTT users on a call when talking").
6. MCPTT server may provide a progress indication to MCPTT client 1 to indicate progress in the call setup process.
NOTE: Step 6 can occur at any time following step 4, and prior to step 10.
7. The MCPTT server 2 checks whether the MCPTT user at MCPTT client 2 is authorized to receive a private call and also checks the commencement mode setting of MCPTT client 2.
8. The MCPTT server 2 offers the same media types or a subset of the media types contained in the initial received request and sends an MCPTT private call request towards the MCPTT client specified in the received MCPTT private call request (i.e., MCPTT client 2). If the called MCPTT user has registered to the MCPTT service with multiple MCPTT UEs and has designated the MCPTT UE for receiving the private calls, then the incoming MCPTT private call request is delivered only to the designated MCPTT UE.
9. The MCPTT user is alerted. MCPTT client 2 sends an MCPTT ringing to the MCPTT server 1 (via server 2).
10. The MCPTT server 1 sends an MCPTT ringing to MCPTT client 1, indicating that MCPTT client 2 is being alerted.
11. MCPTT user 2 has accepted the call using manual commencement mode (i.e. has taken some action to accept via the user interface) which causes MCPTT client 2 to send an MCPTT private call response to the MCPTT server 1 (via SIP core and MCPTT server 2)
12. Upon receiving the MCPTT private call response from MCPTT client 2 accepting the private call request, MCPTT client 1 is informed about successful call establishment.
13. MCPTT client 1 and client 2 have successfully established media plane for communication and either user can transmit media. For successful call establishment of a private call with implicit floor control request from MCPTT client 1, floor participant at MCPTT client 1 is granted the floor by the floor control server at MCPTT service provider 1, giving it permission to transmit. At the same time floor participant at MCPTT client 2 is informed by the floor control server at MCPTT service provider 1 that the floor is taken.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.3.3 Private call release – MCPTT users in multiple MCPTT systems
|
The procedure in this subclause is for the case where an MCPTT client is requesting to release an ongoing MCPTT private call (with or without floor control) established in either of the two commencement modes (manual or automatic), and the MCPTT users are in multiple MCPTT systems.
Procedures are similar to those described for private call release when MCPTT users are in single MCPTT system as in subclause 10.7.2.2.3.1, with the addition that the MCPTT call end request and the corresponding acknowledgement are routed through the MCPTT server in partner MCPTT system.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.4 MCPTT emergency private call
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.4.1 MCPTT emergency private call commencement
|
This procedure focuses on the case where an authorized MCPTT user is initiating an MCPTT emergency private call with unicast signalling for communicating with another MCPTT user. An MCPTT client in the MCPTT emergency state gains elevated access privilege for all of the MCPTT user's mission critical applications.
Procedures in figure 10.7.2.4.1-1 are the procedures for the MCPTT client initiating establishment of an MCPTT emergency private call.
Pre-conditions:
1. Both members of the MCPTT private call belong to the same MCPTT system.
2. The initiating MCPTT client 1 has been configured to send an MCPTT emergency alert prior to initiating an MCPTT emergency private call.
3. Optionally, MCPTT client 1 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.7.2.4.1-1 MCPTT emergency private call
1. The user at the MCPTT client 1 initiates an MCPTT emergency private call. MCPTT client 1 sets its MCPTT emergency state. MCPTT client 1 retains the MCPTT emergency state until explicitly cancelled by the user of MCPTT client 1.
NOTE 1: While MCPTT client 1 is in the emergency state, all MCPTT group and private calls initiated by MCPTT client 1 are initiated as MCPTT emergency calls.
2. MCPTT client 1 sends an MCPTT emergency private call request towards the MCPTT server. The request contains an indication of the MCPTT emergency. MCPTT user at MCPTT client 1 may select a functional alias as calling party address and the MCPTT server verifies whether the provided functional alias can be used. Instead of an MCPTT ID the MCPTT user at MCPTT client 1 may also select a functional alias as called party address, which the MCPTT server replaces by an appropriate MCPTT ID. The MCPTT server records the identity of the MCPTT user that initiated the MCPTT emergency private call until the MCPTT emergency is cancelled. If the MCPTT client is configured to send an MCPTT emergency alert when initiating an MCPTT emergency private call, the request also contains an indication that an MCPTT emergency alert is to be initiated.
NOTE 2: If the MCPTT server detects that the functional alias used as the target of the private call request is simultaneously active for multiple MCPTT users, then the MCPTT server can proceed by selecting an appropriate MCPTT ID based on some selection criteria. This selection of an appropriate MCPTT ID is left to implementation.
3. MCPTT server sends the MCPTT emergency private call request towards the target MCPTT client. The request contains an indication of the in-progress emergency. The request contains an indication of an MCPTT emergency alert if the request from the originator indicated MCPTT emergency alert.
4. The MCPTT user on MCPTT client 2 is notified of the incoming MCPTT emergency private call and may display the functional alias of MCPTT client 1.
NOTE 3: MCPTT client 2 does not set its emergency state as a result of receiving the MCPTT emergency private call.
5. The receiving MCPTT client acknowledges the MCPTT emergency private call request to the MCPTT server.
6. The MCPTT server adjusts the priority of the underlying bearer.
7. The MCPTT server informs MCPTT client 1 about the successful MCPTT emergency private call establishment.
8. MCPTT client 1 and MCPTT client 2 establish the media plane for communication. The MCPTT client 1 can override MCPTT client 2 unless MCPTT client 2 is also in the MCPTT emergency state.
NOTE 4: The priority for the MCPTT emergency private call is retained until cancelled according to system policy (e.g. timeout or call end) or cancelled by an authorized MCPTT user.
NOTE 5: The initiating MCPTT user's MCPTT emergency state is retained by the system until cancelled as in subclause 10.6.2.6.1.3, or by the emergency alert cancellation procedure specified in 3GPP TS 23.280 subclause 10.10.1.2.2.2. The initiating MCPTT user's MCPTT emergency state is also retained locally by the MCPTT client until explicitly cancelled by the MCPTT user.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.4.2 MCPTT private call emergency upgrade
|
This procedure describes the case where an authorized MCPTT user is upgrading a private call to an MCPTT emergency private call while the private call is already in progress.
Procedures in figure 10.7.2.4.2-1 are the signalling procedures for the MCPTT client upgrading a private call to an MCPTT emergency private call.
Pre-conditions:
1. Both members of the private call belong to the same MCPTT system.
2. A private call is already in progress.
Figure 10.7.2.4.2-1: MCPTT private call upgrade
1. The MCPTT user at MCPTT client 1 initiates an emergency. MCPTT client 1 sets its MCPTT emergency state. MCPTT client 1 retains the MCPTT emergency state until explicitly cancelled by the user of MCPTT client 1.
NOTE 1: While MCPTT client 1 is in the emergency state, all MCPTT group and private calls initiated by MCPTT client 1 are initiated as MCPTT emergency calls.
2. MCPTT client 1 requests the MCPTT server to upgrade the private call to in-progress emergency by sending an MCPTT emergency request. If configured to send an MCPTT alert when initiating an MCPTT emergency upgrade, the request also contains an indication that an MCPTT alert is to be initiated. The request may contain an indication of an implicit floor request. If the emergency private call request includes an implicit floor reques it may also include location information.
3. The MCPTT server sends the MCPTT emergency request towards MCPTT client 2, the MCPTT client of the other participant. If location information was included in the emergency private call request, the MCPTT server checks the privacy policy of the MCPTT user to decide if the location information of MCPTT client 1 can be provided to the other user on the call (refer to Annex A.3 "Authorisation to provide location information to other MCPTT users on a call when talking").
4. The MCPTT user of MCPTT client 2 is notified of the in-progress emergency of the MCPTT emergency private call.
NOTE 2: MCPTT client 2 does not set its emergency state as a result of receiving the MCPTT emergency private call upgrade.
5. The receiving MCPTT client acknowledges the MCPTT emergency request to the MCPTT server.
6. The MCPTT server adjusts the priority of the underlying bearer for both participants in the private call. The priority is retained until the call ends.
7. The MCPTT server confirms the upgrade request to MCPTT client 1.
8. MCPTT client 1 and MCPTT client 2 continue with the private call, which has been transformed into an MCPTT emergency private call. MCPTT client 1 can override MCPTT client 2 unless MCPTT client 2 is also in the MCPTT emergency state.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.2.4.3 MCPTT emergency private call floor remote trigger procedure
|
The procedure describes the case where an MCPTT client triggers another MCPTT client to send a floor request. This may be applicable, where an MCPTT user, who has initiated the MCPTT emergency communication and still is in an emergency state, cannot operate his UE anymore. This enables an authorized MCPTT user, e.g. dispatcher, to listen to the activities at the location of the MCPTT user, who may be in a life-threatening situation.
NOTE: This procedure is only applicable, when the MCPTT emergency private call has been setup with floor control.
Figure 10.7.2.4.3-1 shows the MCPTT emergency private call floor remote trigger procedure with floor control.
Pre-conditions:
1. MCPTT client 2 has initiated an emergency private call with floor control and has entered emergency state, as described in clause 10.7.2.4.1.
2. The MCPTT user of MCPTT client 2 does not have the floor.
Figure 10.7.2.4.3-1: MCPTT emergency private call floor remote trigger
1. The MCPTT emergency communication is in progress.
2. The authorized MCPTT user at MCPTT client 1 sends a MCPTT emergency private call floor remote trigger to the MCPTT server, which is intended for MCPTT client 2.
3. The MCPTT server checks if MCPTT client 1 is authorized, for initiating MCPTT emergency private call floor remote trigger.
4. If authorized, the MCPTT server sends the MCPTT emergency private call floor remote trigger towards MCPTT client 2.
5. MCPTT client 2, based on the MCPTT emergency private call floor remote trigger, initiates a floor request procedure, as described in clause 10.9.1.3.1 and automatically opens the microphone, when the floor is granted.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.3 Private call in off-network
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.3.1 Information flows for private call in off-network
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.3.1.1 Call setup request
|
Table 10.7.3.1.1-1 describes the information flow call setup request from one MCPTT client to another MCPTT client.
Table 10.7.3.1.1-1: call setup request
Information element
Status
Description
MCPTT ID of the caller
M
The identity of the calling party
MCPTT ID of the callee
M
The identity of the called party
SDP offer for private call
M
SDP with media information offered by (to) client
Location information
O
Location of the calling party
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.3.1.2 Call setup response
|
Table 10.7.3.1.2-1 describes the information flow call setup response from one MCPTT client to another MCPTT client.
Table 10.7.3.1.2-1: call setup response
Information element
Status
Description
MCPTT ID of the caller
M
The identity of the calling party
MCPTT ID of the callee
M
The identity of the called party
SDP answer for private call
M
SDP with media information offered by (to) client
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.3.1.3 Call release request
|
Table 10.7.3.1.3-1 describes the information flow call release request from one MCPTT client to another MCPTT client.
Table 10.7.3.1.3-1: call release request
Information element
Status
Description
MCPTT ID of the caller
M
The identity of the calling party
MCPTT ID of the callee
M
The identity of the called party
MCPTT private call release reason
O
This element indicates that reason for the private call release. e.g., Originating client requested, target client requested.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.3.1.4 Call release response
|
Table 10.7.3.1.4-1 describes the information flow call release response from one MCPTT client to another MCPTT client.
Table 10.7.3.1.4-1: Call release response
Information element
Status
Description
MCPTT ID of the caller
M
The identity of the calling party
MCPTT ID of the callee
M
The identity of the called party
MCPTT private call release reason
O
This element indicates that reason for the private call release. e.g., Originating client requested, target client requested, server requested.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.3.2 Use of ProSe capability for private call
|
When an MCPTT user using a ProSe-enabled UE wants to communicate with a specific MCPTT user using a ProSe-enabled UE by a ProSe mechanism, the MCPTT client enables the use of the ProSe layer procedures for public safety, as specified in 3GPP TS 23.303 [7].
The MCPTT client obtains configuration data such as the ProSe discovery group ID and user info ID of the target MCPTT user from the "List of user(s) who can be called in private call" in the MCPTT user profile and requests the IP address of the MCPTT UE associated with the target MCPTT user from the ProSe layer.
The MCPTT client enables the ProSe layer to determine the IP address for the communication with the target MCPTT UE by providing the ProSe discovery group ID and user info ID (as defined in specification 3GPP TS 23.303 [7]) of the target MCPTT user. This may trigger the ProSe direct discovery for public safety use procedure, described in 3GPP TS 23.303 [7], to identify whether the target MCPTT user is in the proximity of the calling MCPTT user. The user info ID of the target MCPTT user is used by the ProSe layer as the target info (as defined in specification 3GPP TS 23.303 [7]).
The ProSe layer can then provide the IP address related to the target MCPTT user's MCPTT ID to the MCPTT client. The establishment of the off-network private call using the ProSe capability is based on the one-to-one ProSe direct communication procedure described in 3GPP TS 23.303 [7].
NOTE: The ProSe procedures for one-to-one direct communications specified in 3GPP TS 23.303 [7] retrieves a layer-2 ID associated with the user info ID of the target MCPTT user by the discovery procedure to establish direct communications between ProSe users.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.3.3 Private call setup in automatic commencement mode
|
The procedure focuses on the case where an MCPTT user is initiating an MCPTT private call for communicating with another MCPTT user when off-network using an automatic commencement mode.
Procedures in figure 10.7.3.3-1 are the basic signalling procedures for the MCPTT client initiating establishment of an off-network MCPTT private call with the chosen MCPTT user.
Pre-conditions:
1. MCPTT user profile used for off-network operation mode is pre-provisioned in the MCPTT UEs.
Figure 10.7.3.3-1: Private call setup in automatic commencement mode
1. The MCPTT user at MCPTT client 1 would like to initiate a private call to the MCPTT user at MCPTT client 2.
2. The MCPTT client 1 sends a call setup request towards the MCPTT client 2. The call setup request contains an SDP offer, an automatic commencement mode indication, and an element that indicates that MCPTT client 1 is requesting the floor. If the private call request requests the floor it may include location information.
3. The MCPTT client 2 notifies the MCPTT user about the incoming private call.
4. The receiving MCPTT client 2 accepts the private call automatically, and a call setup response indicating the successful call establishment is sent to MCPTT client 1. If MCPTT client 2 rejected the incoming call, the MCPTT client 2 sends a call setup response indicating the failure reason to the MCPTT client 1.
NOTE: Step 4 can also occur prior to step 3.
5. The MCPTT client 1 and the MCPTT client 2 have successfully established the media plane for communication with floor control and the MCPTT client 1 is automatically granted the floor.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.3.4 Private call setup in manual commencement mode
|
The procedure focuses on the case where an MCPTT user is initiating an MCPTT private call for communicating with another MCPTT user when off-network using a manual commencement mode.
Procedures in figure 10.7.3.4-1 are the basic signalling procedures for the MCPTT client initiating establishment of an off-network MCPTT private call with the chosen MCPTT user.
Pre-conditions:
1. MCPTT user profile used for off-network operation mode is pre-provisioned in the MCPTT UEs.
Figure 10.7.3.4-1: Private call setup in manual commencement mode
1. The MCPTT user at MCPTT client 1 would like to initiate an MCPTT private call to the MCPTT user at MCPTT client 2.
2. The MCPTT client 1 sends a call setup request towards the MCPTT client 2. The MCPTT private call setup request contains an SDP offer, a manual commencement mode indication, and an element that indicates that MCPTT client 1 is requesting the floor. If the private call request requests the floor it may include location information.
3. The receiving MCPTT client 2 notifies the MCPTT user about the incoming private call.
4. The MCPTT client 2 sends MCPTT ringing message to the MCPTT client 1.
NOTE: Step 4 can also occur prior to step 3.
5. The MCPTT user at the MCPTT client 2 has accepted the call using manual commencement mode (i.e., has taken some action to accept via the user interface). The MCPTT user may also reject or fail to answer the incoming call.
6. The MCPTT client 2 sends a call setup response indicating the successful call establishment to MCPTT client 1. If the MCPTT client 2 rejected the call or the MCPTT user 2 rejected or failed to answer the incoming call, the MCPTT client 2 sends a call setup response indicating the failure reason to the MCPTT client 1.
7. The MCPTT client 1 and the MCPTT client 2 have successfully established the media plane for communication with floor control and the MCPTT client 1 is automatically granted the floor.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.3.5 Private call release
|
The procedure focuses on the case where an MCPTT client is requesting to release an ongoing MCPTT private call whether the call was established using either of the two commencement modes (manual or automatic), as described in subclause 10.7.3.3 and subclause 10.7.3.4. Either MCPTT client can initiate the call release procedure.
Procedures in figure 10.7.3.5-1 are the basic signalling control plane procedures for an MCPTT client initiating the release of an ongoing off-network MCPTT private call.
Pre-conditions:
1. Two MCPTT users are currently engaged in an off-network MCPTT private call.
Figure 10.7.3.5-1: Private call release
1. The MCPTT user at MCPTT client 1 would like to initiate an MCPTT private call release to the MCPTT user at MCPTT client 2.
2. The MCPTT client 1 sends a call release request towards the MCPTT client 2.
3. The MCPTT client 2 notifies the MCPTT user about the private call release.
4. The MCPTT client 2 sends a call release response indicating the successful call release to MCPTT client 1.
NOTE: Step 4 can also occur prior to step 3.
5. The MCPTT client 1 and the MCPTT client 2 release all associated media plane resources.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.3.6 MCPTT emergency private call
|
The off-network emergency private call is a special case of off-network private call as defined in subclause 10.7.3. The following are modifications to the aforementioned subclause to support MCPTT private calls:
- The call setup contains an indication that the MCPTT private call is to be an MCPTT emergency private call,
- the bearers of both MCPTT private call participants are given MCPTT emergency priority prior to media transfer,
- either participant in an MCPTT private call may upgrade the call to the MCPTT emergency state during the call by sending an MCPTT upgrade private emergency request,
- placing an MCPTT emergency private call places the MCPTT client in the MCPTT emergency state,
- the bearer priority of each participant is restored to the priority as it was prior to the MCPTT emergency private call initiation, when the call ends or when the MCPTT emergency priority is cancelled
- an authorized user or the originator of the call may cancel the MCPTT emergency priority of the call by sending an MCPTT cancel private emergency request and
- the MCPTT emergency priority of the MCPTT private call may be cancelled when criteria established by the MCPTT Administrator are met (e.g., timeout).
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.4 MCPTT private call call‑back request
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.4.1 Information flows for MCPTT private call call‑back request
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.4.1.1 MCPTT private call call‑back request
|
Table 10.7.4.1.1-1 describes the information flow MCPTT private call call‑back request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client.
Table 10.7.4.1.1-1: MCPTT private call call‑back 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
Urgency indication
M
This element indicates the urgency (i.e., low, normal, high) of the call‑back request.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.4.1.2 MCPTT private call call‑back response
|
Table 10.7.4.1.2-1 describes the information flow MCPTT private call call‑back response from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client.
Table 10.7.4.1.2-1: MCPTT private call call‑back response 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
Result
M
Result of the MCPTT call‑back request – success or fail.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.4.1.3 MCPTT private call call‑back cancel request
|
Table 10.7.4.1.3-1 describes the information flow MCPTT private call call‑back cancel request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client.
Table 10.7.4.1.3-1: MCPTT private call call‑back cancel 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
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.4.1.4 MCPTT private call call‑back cancel response
|
Table 10.7.4.1.4-1 describes the information flow MCPTT private call call‑back cancel response from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client.
Table 10.7.4.1.4-1: MCPTT private call call‑back cancel response 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
Result
M
Result of the MCPTT private call call‑back cancel request – success or fail.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.4.2 MCPTT private call call‑back request within one MCPTT system
|
The MCPTT private call call‑back request procedure includes the initial MCPTT private call call‑back request from the MCPTT user and the indication to the receiving MCPTT user of the who called, the time when the call request was made, and the urgency indication.
Procedures in figure 10.7.4.2-1 show the signalling control plane procedures for the MCPTT client initiating an MCPTT private call call‑back request with the chosen MCPTT user.
Pre-conditions:
- MCPTT user 1 is the current user at MCPTT client 1 and MCPTT user 2 is the current user at MCPTT client 2;
- MCPTT client 1 and MCPTT client 2 are registered for MCPTT service.
Figure 10.7.4.2-1: MCPTT private call call‑back request – MCPTT users in the same MCPTT system
1. MCPTT user on MCPTT client 1 initiates an MCPTT private call call‑back request to the MCPTT user of MCPTT client 2.
2. MCPTT client 1 sends an MCPTT private call call‑back request towards the MCPTT server.
3. MCPTT server checks whether the MCPTT user 1 at MCPTT client 1 is authorized to initiate the MCPTT private call call‑back request.
4. If authorized, MCPTT server sends the corresponding MCPTT private call call‑back request towards the MCPTT client 2.
5. The receiving MCPTT client 2 stores the MCPTT user who initiated the MCPTT private call call‑back request, the time the MCPTT private call call‑back request was received, and the urgency indication for the MCPTT private call call-back request.
6. The MCPTT client 2 notifies the MCPTT user 2 that there is an MCPTT private call call-back request awaiting his attention.
7. The receiving MCPTT client 2 sends an MCPTT private call call‑back response to the MCPTT server.
8. Upon receiving the MCPTT private call call-back response from MCPTT client 2, the MCPTT server informs the MCPTT client 1 about successful call-back request.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.4.3 MCPTT private call call‑back cancel request within one MCPTT system
|
Once an MCPTT private call call‑back request has been successfully made and before the receiving MCPTT user has made an MCPTT private call to the calling MCPTT user, the calling MCPTT user may cancel the outstanding MCPTT private call request.
Procedures in figure 10.7.4.3-1 show the signalling control plane procedures for the MCPTT client initiating an MCPTT private call call-back cancel request with the chosen MCPTT user.
Pre-conditions:
1. A previously successfully made MCPTT private call call‑back request from MCPTT client 1 to MCPTT client 2.
Figure 10.7.4.3-1: MCPTT private call call‑back cancel request – MCPTT users in the same MCPTT system
1. MCPTT user on MCPTT client 1 wants to cancel a previously created MCPTT private call call‑back request to the MCPTT user 2 of MCPTT client 2.
2. MCPTT client 1 sends an MCPTT private call call‑back cancel request towards the MCPTT server.
3. MCPTT server checks whether the MCPTT user 1 at MCPTT client 1 is authorized to cancel the previous MCPTT private call call‑back request, if one exists.
4. If authorized, MCPTT server sends the corresponding MCPTT private call call‑back cancel request towards the MCPTT client 2.
5. The receiving MCPTT client 2 removes all stored information about the previous MCPTT private call call‑back request from the MCPTT user 1 on MCPTT client 1.
6. The receiving MCPTT client 2 sends an MCPTT private call call‑back cancel response to the MCPTT server.
7. Upon receiving the MCPTT private call call‑back cancel response from MCPTT client 2, the MCPTT server informs the MCPTT client 1 about successful call‑back request cancelation.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.4.4 MCPTT private call call‑back request fulfillment within one MCPTT system
|
Once an MCPTT private call call‑back request has been successfully made, it is expected that the receiving MCPTT user will make an MCPTT private call to the MCPTT user who sent the MCPTT private call call‑back request. The procedures for establishing the MCPTT private call between the two users is the same as an MCPTT private call (10.7.2.2.2).
Procedures in figure 10.7.4.4-1 show the signalling control plane procedures for the MCPTT client returning an MCPTT private call to the MCPTT user who initiated the MCPTT private call call‑back request.
Pre-conditions:
1. A previously successfully made MCPTT private call call‑back request from MCPTT client 1 to MCPTT client 2.
Figure 10.7.4.4-1: MCPTT private call‑back request fulfillment – MCPTT users in the same MCPTT system
1. MCPTT user 2 on MCPTT client 2 decides to initiate an MCPTT private call based on the stored MCPTT private call call‑back request to the MCPTT user 1 on MCPTT client 1 using the MCPTT private call procedures of 10.7.2.2.2.
2. Once a successful MCPTT private call has been made between the MCPTT user 1 on MCPTT client 1 and MCPTT user 2, then the MCPTT client 2 removes the stored call‑back request information.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.5 MCPTT call forwarding for private calls
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.5.1 General
|
Call forwarding of MCPTT private calls allows users to configure forwarding of incoming private calls (with or without Floor control) to another MCPTT user depending on the following conditions:
- Immediate
- No answer: If the incoming private call is a call with manual commencement mode and the MCPTT User does not answer within a configured period
The forwarding of an individual call can also be based on manual input of the called MCPTT user on a per call basis. In this case the MCPTT user responds to an incoming MCPTT private call by requesting redirection of that MCPTT private call to another MCPTT user. It can only be invoked before the communication is established by the served user, which is the period that the served user is being informed of the communication (during ringing).
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.5.1.1 Void
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.5.1.2 MCPTT private call forwarding request (MCPTT client to MCPTT server and MCPTT server to MCPTT server)
|
Table 10.7.5.1.2-1 describes the information flow of the MCPTT private call forwarding request from the MCPTT client to the MCPTT server and MCPTT server to MCPTT server.
Table 10.7.5.1.2-1: MCPTT private call forwarding request (MCPTT client to MCPTT server and MCPTT server to MCPTT server) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID requesting the call forwarding
MCPTT ID
M
The MCPTT ID originating the MCPTT private call
MCPTT ID (see NOTE)
O
The target MCPTT ID of the call forwarding
Functional alias (see NOTE)
O
The target functional alias of the call forwarding
NOTE: One identity shall be present
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.5.1.3 MCPTT private call forwarding response (MCPTT server to MCPTT client)
|
Table 10.7.5.1.3-1 describes the information flow of the MCPTT private call forwarding response from the MCPTT server to the MCPTT client.
Table 10.7.5.1.3-1: MCPTT private call forwarding response (MCPTT server to MCPTT client) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID requesting the call call forwarding
Result
M
Result of the call forwarding request – success or fail
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.5.1.4 MCPTT private call forwarding request (MCPTT server to MCPTT client)
|
Table 10.7.5.1.4-1 describes the information flow of the MCPTT private call forwarding request from the MCPTT server to the MCPTT client.
Table 10.7.5.1.4-1: MCPTT private call forwarding request (MCPTT server to MCPTT client) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the party to be forwarded
MCPTT ID
M
The target MCPTT ID of the call forwarding
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.5.1.5 MCPTT private call forwarding response (MCPTT client to MCPTT server and MCPTT server to MCPTT server)
|
Table 10.7.5.1.5-1 describes the information flow of the MCPTT private call forwarding response from the MCPTT client to the MCPTT server and MCPTT server to MCPTT server.
Table 10.7.5.1.5-1: MCPTT private call forwarding response (MCPTT client to MCPTT server and MCPTT server to MCPTT server) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the party to be forwarded
MCPTT ID
M
The MCPTT ID of the target of the forwarding
Result
M
Result of the call forwarding request – success or fail
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.5.2 Procedures
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.5.2.1 Update configuration for MCPTT private call forwarding
|
An authorized user can update the call forwarding related parameters stored in the user profile using the procedures as defined in 3GPP TS 23.280 [8] subclause 10.1.4.5.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.5.2.2 MCPTT immediate private call forwarding in a single MCPTT system
|
Figure 10.7.5.2.2-1 below illustrates the procedure of immediate call forwarding of MCPTT private calls.
Pre-conditions:
1. MCPTT client 2 is authorized to use call forwarding and has immediate call forwarding enabled with the destination MCPTT client 3.
2. MCPTT client 1 is authorized to make private calls to client 2.
3. The redirection counter is below the limit.
4. MCPTT client 1 has the necessary security information to initiate a private call with MCPTT client 2 and MCPTT client 3 if end2end encryption is required for the private call.
Figure 10.7.5.2.2-1: Call forwarding immediate for private calls
1. MCPTT client 1 sends an MCPTT private call request towards the MCPTT server.
2. The MCPTT server detects that MCPTT client 2 has immediate call forwarding enabled.
3. The MCPTT server checks that the limit of immediate forwardings is not reached. The MCPTT server increments the redirection counter for immediate forwardings. If the target of the MCPTT private call forwarding is a functional alias instead of an MCPTT ID the MCPTT server resolves the functional alias to the corresponding MCPTT ID for which the functional alias is active.
NOTE 1: Depending on implementation the MCPTT server can apply additional call restrictions and decide whether the call is allowed to proceed with the resolved MCPTT ID(s) (e.g. whether the MCPTT ID is within the allowed area of the functional alias). If the MCPTT server detects that the functional alias used as the target of the MCPTT private call forwarding is simultaneously active for multiple MCPTT users, then the MCPTT server can proceed by selecting an appropriate MCPTT ID based on some selection criteria (e.g. current location of the initiating user to determine the dispatcher who is responsible for the related geographic area). The selection of an appropriate MCPTT ID is left to implementation. The selection criteria can include rejection of the call, if no suitable MCPTT ID is selected.
3a. If the target of the call forwarding is a functional alias that is not active, or if the target functional is simultaneously active by multiple users and the outcome of the selection is a rejection, the MCPTT private call forwarding is cancelled, and the MCPTT server sends an MCPTT private call cancel request towards MCPTT client 1. Otherwise, the procedure continues with step 4.
3b. MCPTT client 1 sends an MCPTT call private cancel response back to the MCPTT server, and the procedure ends.
4. The MCPTT server sends an MCPTT private call forwarding request towards MCPTT client 1.
NOTE 2: The target MCPTT ID is based on the entry in the user profile for call forwarding immediate.
5. The user at MCPTT client 1 is notified that a call forwarding is in process.
6. MCPTT client 1 sends an MCPTT call private forwarding response back to the MCPTT server.
7. MCPTT client 1 sends an MCPTT private call request towards the MCPTT server that includes a call forwarding indication set to true. MCPTT client 1 and MCPTT client 3 set up a security association if end-to-end encryption is used for this call.
8. The MCPTT server verifies that client 1 is authorized to perform the MCPTT private call as a result of the MCPTT private call forwarding request. The MCPTT server verifies that the MCPTT private call request contains MCPTT client 3 that is the authorized target from step 4, and the forwarding indication is set to true.
9. The MCPTT server sends an MCPTT private call request towards MCPTT client 3.
10. Optionally the MCPTT server sends an MCPTT progress indication to MCPTT client 1.
11. The user at MCPTT client 3 is alerted. MCPTT client 3 sends an MCPTT ringing to the MCPTT server. This step is not required in case of automatic commencement mode.
12. The MCPTT server sends an MCPTT ringing to MCPTT client 1. This step is not required in case of automatic commencement mode.
13. MCPTT client 3 sends an MCPTT private call response to the MCPTT server. In manual commencement mode this occurs after the user at MCPTT client 3 has accepted the call.
14. The MCPTT server sends an MCPTT private call response to MCPTT client 1 indicating that MCPTT client 3 has accepted the call.
15. The media plane for communication between MCPTT client 1 and MCPTT client 3 is established.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.5.2.3 MCPTT private call forwarding no answer in a single MCPTT system
|
Figure 10.7.5.2.3-1 below illustrates the procedure of call forwarding no answer of MCPTT private calls.
NOTE 1: The condition no answer covers both the cases in which the user does not answer because he is not reachable, as well as the case in which he is reachable but does not answer.
Pre-conditions:
1. MCPTT client 2 is authorized to use call forwarding and has call forwarding no answer enabled with the destination MCPTT client 3.
2. MCPTT client 1 is authorized to make private calls to MCPTT client 2.
3. No forwarding with no answer or based on manual user input has so far occurred in this call.
4. MCPTT client 1 has the necessary security information to initiate a private call with MCPTT client 2 and MCPTT client 3 if end2end encryption is required for the private call.
Figure 10.7.5.2.3-1: MCPTT call forwarding no answer
1. MCPTT client 1 sends an MCPTT private call request towards the MCPTT server.
2. The MCPTT server checks if MCPTT client 2 has call forwarding no answer enabled. If the MCPTT server detects that MCPTT client 2 is not registered, the procedure continues with step 7. Otherwise, the MCPTT server starts a timer with the configured no answer timeout.
3. The MCPTT server sends an MCPTT private call request in manual commencement mode towards MCPTT client 2. If the MCPTT server detects that MCPTT client 2 is not reachable, the procedure continues with step 7.
4. The user at MCPTT client 2 is alerted. MCPTT client 2 sends an MCPTT ringing to the MCPTT server.
5. The MCPTT server sends an MCPTT ringing to the MCPTT client 1. This step is not required in case of automatic commencement mode.
6. The MCPTT server detects that MCPTT client 2 does not answer within the specified time interval.
7. The MCPTT server verifies that no other forwarding with the condition no answer or based on manual user input has occurred so far. If the target of the MCPTT private call forwarding is a functional alias instead of an MCPTT ID the MCPTT server resolves the functional alias to the corresponding MCPTT ID for which the functional alias is active.
NOTE 2: Depending on implementation the MCPTT server can apply additional call restrictions and decide whether the call is allowed to proceed with the resolved MCPTT ID(s) (e.g. whether the MCPTT ID is within the allowed area of the functional alias). If the MCPTT server detects that the functional alias used as the target of the MCPTT private call forwarding is simultaneously active for multiple MCPTT users, then the MCPTT server can proceed by selecting an appropriate MCPTT ID based on some selection criteria (e.g. current location of the initiating user to determine the dispatcher who is responsible for the related geographic area). The selection of an appropriate MCPTT ID is left to implementation. The selection criteria can include rejection of the call, if no suitable MCPTT ID is selected.
7a. If the target of the call forwarding is a functional alias that is not active, or if the target functional is simultaneously active by multiple users and the outcome of the selection is a rejection, the MCPTT private call forwarding is cancelled, and the MCPTT server sends an MCPTT private call cancel request towards MCPTT client 1. Otherwise, the procedure continues with step 8.
7b. MCPTT client 1 sends an MCPTT call private cancel response back to the MCPTT server, and the procedure ends.
8. The MCPTT server sends an MCPTT private call forwarding request towards the MCPTT client 1.
NOTE 3: The target MCPTT ID is based on the entry in the user profile for call forwarding no answer.
9. The user at MCPTT client 1 is notified that a call forwarding is in process.
10. MCPTT client 1 sends an MCPTT private call forwarding response back to the MCPTT server.
11. MCPTT client 1 sends an MCPTT private call request towards the MCPTT server that includes a call forwarding indication set to true. MCPTT client 1 and MCPTT client 3 set up a security association if end-to-end encryption is used for this call.
12. The MCPTT server verifies that client 1 is authorized to perform the MCPTT private call as a result of the MCPTT private call forwarding request. The MCPTT server verifies that the MCPTT private call request contains MCPTT client 3 that is the authorized target from step 8, and the forwarding indication is set to true.
NOTE 4: For call forwarding the MCPTT server does not check if the initial originating MCPTT user at MCPTT client 1 is authorized to make an MCPTT private call to the final target MCPTT user at MCPTT client 3.
13. The MCPTT server sends an MCPTT private call request towards MCPTT client 3.
14. Optionally the MCPTT server sends an MCPTT progress indication to MCPTT client 1.
15. The user at MCPTT client 3 is alerted. MCPTT client 3 sends an MCPTT ringing to the MCPTT server. This step is not required in case of automatic commencement mode.
16. The MCPTT server sends an MCPTT ringing to MCPTT client 1. This step is not required in case of automatic commencement mode.
17. MCPTT client 3 sends an MCPTT private call response to the MCPTT server. In manual commencement mode this occurs after the user at MCPTT client 3 has accepted the call.
18. The MCPTT server sends an MCPTT private call response to MCPTT client 1 indicating that MCPTT client 3 has accepted the call.
19. The media plane for communication between MCPTT client 1 and MCPTT client 3 is established.
10.7.5.2.3a MCPTT private call forwarding based on manual user input in a single MCPTT system
Figure 10.7.5.2.3a-1 below illustrates the procedure of call forwarding based on manual user input of MCPTT private calls.
Pre-conditions:
1. MCPTT client 2 is authorized to perform call forwarding based on manual input.
2. MCPTT client 1 is authorized to make private calls to MCPTT client 2.
3. No forwarding with no answer or based on manual user input has so far occurred in this call.
4. MCPTT client 1 has the necessary security information to initiate a private call with MCPTT client 2 and MCPTT client 3 if end2end encryption is required for the private call.
Figure 10.7.5.2.3a-1: MCPTT call forwarding based on manual user input
1. MCPTT client 1 sends an MCPTT private call request towards the MCPTT server.
2. The MCPTT server checks if MCPTT client 2 has call forwarding no answer enabled. If the MCPTT server detects that MCPTT client 2 is not registered, the procedure continues with step 10. Otherwise, the MCPTT server starts a timer with the configured no answer timeout.
3. The MCPTT server sends an MCPTT private call request in manual commencement mode towards MCPTT client 2. If the MCPTT server detects that MCPTT client 2 is not reachable, the procedure continues with step 10.
4. The user at MCPTT client 2 is alerted. MCPTT client 2 sends an MCPTT ringing to the MCPTT server.
5. In manual commencement mode the MCPTT server sends an MCPTT ringing to the MCPTT client 1.
6. During ringing the user at MCPTT client 2 requests the call to be forwarded based on manual input.
7. MCPTT client 2 sends an MCPTT private call forwarding request to the MCPTT server.
8. The MCPTT server verifies if the user at client 2 is allowed to perform forwarding based on manual input. If the target of the MCPTT private call forwarding is a functional alias instead of an MCPTT ID the MCPTT server resolves the functional alias to the corresponding MCPTT ID for which the functional alias is active.
NOTE 1: Depending on implementation the MCPTT server can apply additional call restrictions and decide whether the call is allowed to proceed with the resolved MCPTT ID(s) (e.g. whether the MCPTT ID is within the allowed area of the functional alias). If the MCPTT server detects that the functional alias used as the target of the MCPTT private call forwarding is simultaneously active for multiple MCPTT users, then the MCPTT server can proceed by selecting an appropriate MCPTT ID based on some selection criteria (e.g. current location of the initiating user to determine the dispatcher who is responsible for the related geographic area). The selection of an appropriate MCPTT ID is left to implementation. The selection criteria can include rejection of the call, if no suitable MCPTT ID is selected.
8a. If the target of the call forwarding is a functional alias that is not active, or if the target functional is simultaneously active by multiple users and the outcome of the selection is a rejection, the MCPTT private call forwarding is cancelled, and the MCPTT server sends an MCPTT private call cancel request towards MCPTT client 1. Otherwise, the procedure continues with step 9.
8b. MCPTT client 1 sends an MCPTT call private cancel response back to the MCPTT server.
8c. The MCPTT server sends an MCPTT private call forwarding response with Result equals "fail" to MCPTT client 2, and the procedure ends.
9. The MCPTT server stops the timer for the no answer timeout.
10. The MCPTT server verifies that no other forwarding with the condition no answer or based on manual user input has occurred so far.
11.The MCPTT server sends an MCPTT private call forwarding response to MCPTT client 2.
12. The MCPTT server sends an MCPTT private call forwarding request towards the MCPTT client 1.
NOTE 2: The target MCPTT ID is based on the identity manually entered by the user at MCPTT client 2 in step 6.
13. The user at MCPTT client 1 is notified that a call forwarding is in process.
14. MCPTT client 1 sends an MCPTT private call forwarding response back to the MCPTT server.
15. MCPTT client 1 sends an MCPTT private call request towards the MCPTT server that includes a call forwarding indication set to true. MCPTT client 1 and MCPTT client 3 set up a security association if end-to-end encryption is used for this call.
16. The MCPTT server verifies that client 1 is authorized to perform the MCPTT private call as a result of the MCPTT private call forwarding request. The MCPTT server verifies that the MCPTT private call request contains MCPTT client 3 that is the authorized target from step 12, and the forwarding indication is set to true.
NOTE 3: For call forwarding the MCPTT server does not check if the initial originating MCPTT user at MCPTT client 1 is authorized to make an MCPTT private call to the final target MCPTT user at MCPTT client 3.
17. The MCPTT server sends an MCPTT private call request towards MCPTT client 3.
18. Optionally the MCPTT server sends an MCPTT progress indication to MCPTT client 1.
19. The user at MCPTT client 3 is alerted. MCPTT client 3 sends an MCPTT ringing to the MCPTT server. This step is not required in case of automatic commencement mode.
20. The MCPTT server sends an MCPTT ringing to MCPTT client 1. This step is not required in case of automatic commencement mode.
21. MCPTT client 3 sends an MCPTT private call response to the MCPTT server. In manual commencement mode this occurs after the user at MCPTT client 3 has accepted the call.
22. The MCPTT server sends an MCPTT private call response to MCPTT client 1 indicating that MCPTT client 3 has accepted the call.
23. The media plane for communication between MCPTT client 1 and MCPTT client 3 is established.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.5.2.4 Handling of multiple MCPTT private call forwardings
|
If the target of the MCPTT private call forwarding has also any kind of MCPTT call forwarding activated generally the additional forwardings are performed sequentially. However, to avoid excessive numbers of forwardings and in particular to avoid indefinite loops in the forwarding a limit for immediate forwardings is defined in the service configuration. The MCPTT server keeps track of the number of forwardings, if the limit is exceeded, the call will be released. For forwarding no answer or for forwarding based on manual user input, only one forwarding is allowed, and in case of no answer on the first forwarding the MCPTT server will release the call.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.5.2.5 MCPTT private call forwarding with target of the MCPTT private call forwarding in partner MCPTT system
|
The procedure describes the case for MCPTT for private call forwarding that an MCPTT user in a partner MCPTT system is the target of the MCPTT private call forwarding.
NOTE 1: The procedure shows manual commencement mode, but the changes are also applicable when using automatic commencement mode.
NOTE 2: The procedure focusses on the interaction between the MCPTT servers, which is independent of the condition of the call forwarding. Therefore, the procedure is generically applicable for all types of MCPTT private call forwarding.
Pre-conditions:
1. MCPTT client 2 is authorized to use call forwarding and has immediate call forwarding enabled with the destination MCPTT client 3.
2. MCPTT client 1 is authorized to make private calls to MCPTT client 2.
3. The redirection counter is below the limit.
4. MCPTT client 1 has the necessary security information to initiate a private call with MCPTT client 2 and MCPTT client 3 if end-to-end encryption is required for the private call.
Figure 10.7.5.2.5-1: Simplified private call setup with MCPTT private calls forwarding in manual commencement mode with forwarding target in the partner MCPTT system
1. MCPTT client 1 sends an MCPTT private call request towards MCPTT server 1.
1a If the MCPTT private call request contains a functional alias instead of an MCPTT ID as called party, MCPTT server 1 checks 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.
NOTE 1: If the target of the MCPTT private call request is a functional alias, the procedure resolves the functional alias to the corresponding MCPTT ID for which the functional alias is active. For simplicity details are not described in this procedure.
2. MCPTT server 1 detects that MCPTT client 2 has immediate call forwarding enabled to MCPTT client 3 which is registered in MCPTT system 2.
3. MCPTT server 1 sends an MCPTT private call forwarding request towards MCPTT client 1.
NOTE 2: If the target of the MCPTT private call forwarding is a functional alias, the procedure resolves the functional alias to the corresponding MCPTT ID for which the functional alias is active. For simplicity details of the resolution are not described.
4. The user at MCPTT client 1 is notified that a call forwarding is in process.
5. MCPTT client 1 sends an MCPTT call private forwarding response back to MCPTT server 1.
6. MCPTT client 1 sends an MCPTT private call request towards MCPTT server 1 that includes a call forwarding indication set to true.
7. MCPTT server 1 verifies that MCPTT client 1 is authorized to perform an MCPTT private call as a result of the MCPTT private call forwarding request. MCPTT server 1 verifies that the MCPTT private call request contains MCPTT client 3 that is the authorized target from step 3, and the forwarding indication is set to true.
NOTE 3: For call forwarding the MCPTT server does not check if the initial originating MCPTT user at MCPTT client 1 is authorized to make an MCPTT private call to the final target MCPTT user at MCPTT client 3.
8. MCPTT server 1 sends an MCPTT private call request towards MCPTT server 2.
9. MCPTT server 2 sends an MCPTT private call request towards MCPTT client 3.
NOTE 3: MCPTT server 2 detects that the private call request contains a forwarding indication is set to true and therefore skips the authorization checking.
10. Optionally MCPTT server 1 sends an MCPTT progress indication to MCPTT client 1.
11. The user at MCPTT client 3 is alerted. MCPTT client 3 sends an MCPTT ringing to MCPTT server 2. This step is not required in case of automatic commencement mode.
12. MCPTT server 2 sends an MCPTT ringing to MCPTT server 1. This step is not required in case of automatic commencement mode.
13. MCPTT server 1 sends an MCPTT ringing to MCPTT client 1. This step is not required in case of automatic commencement mode.
14. MCPTT client 3 sends an MCPTT private call response to MCPTT server 2. In manual commencement mode this occurs after the user at MCPTT client 3 has accepted the call.
15. MCPTT server 2 sends an MCPTT private call response to MCPTT server 1. In manual commencement mode this occurs after the user at MCPTT client 3 has accepted the call.
16. MCPTT server 1 sends an MCPTT private call response to MCPTT client 1 indicating that MCPTT client 3 has accepted the call.
17. The media plane for communication between MCPTT client 1 and MCPTT client 3 is established.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.5.2.6 MCPTT private call forwarding with MCPTT private call forwarding occurring in the partner MCPTT system
|
The procedure for MCPTT private call forwarding describes the case of an MCPTT private call forwarding occurring in the partner MCPTT system.
NOTE 1: The procedure shows manual commencement mode, but the changes are also applicable when using automatic commencement mode.
NOTE 2: The procedure focusses on the interaction between the MCPTT servers, which is independent of the condition for the call forwarding. Therefore, the procedure is generically applicable for all types of call forwarding.
Pre-conditions:
1. MCPTT client 3 is authorized to use call forwarding and has immediate call forwarding enabled with the destination MCPTT client 2.
2. MCPTT client 1 is authorized to make private calls to MCPTT client 3.
3. The redirection counter is below the limit.
4. MCPTT client 1 has the necessary security information to initiate a private call with MCPTT client 2 and MCPTT client 3 if end-to-end encryption is required for the private call.
Figure 10.7.5.2.6-1: Simplified private call setup with MCPTT private calls forwarding in manual commencement mode with forwarding in the partner MCPTT systems
1. MCPTT client 1 sends an MCPTT private call request towards MCPTT server 1 for establishing an MCPTT private call with MCPTT client 3 registered at MCPTT system 2.
1a If the MCPTT private call request contains a functional alias instead of an MCPTT ID as called party, MCPTT server 1 checks whether MCPTT client 1 is allowed to use the functional alias of MCPTT client 3 to setup a private call.
NOTE 1: If the target of the MCPTT private call request is a functional alias, the procedure resolves the functional alias to the corresponding MCPTT ID for which the functional alias is active. For simplicity details are not described.
2. MCPTT server 1 sends an MCPTT private call request towards MCPTT server 2 for establishing an MCPTT private call with MCPTT client 3 registered at MCPTT system 2.
2a If the MCPTT private call request contains a functional alias instead of an MCPTT ID as called party, MCPTT server 2 checks whether MCPTT client 3 is allowed to receive a private call from MCPTT client 1 using the functional alias.
3. MCPTT server 2 detects that MCPTT client 3 has immediate call forwarding enabled to MCPTT client 2 registered at MCPTT system 1.
NOTE 2: If the target of the MCPTT private call forwarding is a functional alias, the procedure resolves the functional alias to the corresponding MCPTT ID for which the functional alias is active. For simplicity details of the resolution are not described.
4. MCPTT server 2 sends an MCPTT private call forwarding request towards MCPTT server 1.
5. MCPTT server 1 sends an MCPTT private call forwarding request towards MCPTT client 1.
6. The user at MCPTT client 1 is notified that a call forwarding is in process.
7. MCPTT client 1 sends an MCPTT call private forwarding response back to MCPTT server 1.
8. MCPTT server 1 sends an MCPTT call private forwarding response back to MCPTT server 2.
9. MCPTT client 1 sends an MCPTT private call request towards MCPTT server 1 that includes a call forwarding indication set to true.
10. MCPTT server 1 verifies that MCPTT client 1 is authorized to perform the MCPTT private call as a result of the MCPTT private call forwarding request. MCPTT server 1 verifies that the MCPTT private call request contains MCPTT client 2 that is the authorized target from step 5, and the forwarding indication is set to true.
NOTE 3: For call forwarding the MCPTT server does not check if the initial originating MCPTT user at MCPTT client 1 is authorized to make an MCPTT private call to the final target MCPTT user at MCPTT client 2.
11. MCPTT server 1 sends an MCPTT private call request towards MCPTT client 2.
12. Optionally MCPTT server 1 sends an MCPTT progress indication to MCPTT client 1.
13. The user at MCPTT client 2 is alerted. MCPTT client 2 sends an MCPTT ringing to MCPTT server 1. This step is not required in case of automatic commencement mode.
14. MCPTT server 1 sends an MCPTT ringing to MCPTT client 1. This step is not required in case of automatic commencement mode.
15. MCPTT client 2 sends an MCPTT private call response to MCPTT server 1. In manual commencement mode this occurs after the user at MCPTT client 2 has accepted the call.
16. MCPTT server 1 sends an MCPTT private call response to MCPTT client 1 indicating that MCPTT client 2 has accepted the call.
17. The media plane for communication between MCPTT client 1 and MCPTT client 2 is established.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.6 Call transfer for MCPTT private calls
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.6.1 General
|
Call transfer of MCPTT private calls allows users to relocate an existing MCPTT private call to another MCPTT user.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.6.1.1 MCPTT private call transfer request (MCPTT client to MCPTT server)
|
Table 10.7.6.1.1-1 describes the information flow MCPTT private call transfer request from the MCPTT client to the MCPTT server.
Table 10.7.6.1.1-1: MCPTT private call transfer request (MCPTT client to MCPTT server) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the party requesting the transfer
MCPTT ID (see NOTE)
O
The MCPTT ID of the target of the transfer
Functional alias (see NOTE)
O
The functional alias of the target of the transfer
NOTE: One identity shall be present
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.6.1.2 MCPTT private call transfer request (MCPTT server to MCPTT client and MCPTT server to MCPTT server)
|
Table 10.7.6.1.2-1 describes the information flow MCPTT private call transfer request from the MCPTT server to the MCPTT client and from the MCPTT server to the MCPTT server.
Table 10.7.6.1.2-1: MCPTT private call transfer request (MCPTT server to MCPTT client and from the MCPTT server to the MCPTT server) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the party to be transferred
MCPTT ID
M
The MCPTT ID of the target of the transfer
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.6.1.3 MCPTT private call transfer response (MCPTT server to MCPTT client and MCPTT server to MCPTT server)
|
Table 10.7.6.1.3-1 describes the information flow MCPTT private call transfer response from the MCPTT server to the MCPTT client and from the MCPTT server to the MCPTT server.
Table 10.7.6.1.3-1: MCPTT private call transfer response (MCPTT server to MCPTT client and MCPTT server to MCPTT server) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the party requesting the transfer
MCPTT ID
M
The MCPTT ID of the target of the transfer
Result
M
Result of the transfer request – success or fail.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.6.1.4 MCPTT private call transfer response (MCPTT client to MCPTT server)
|
Table 10.7.6.1.4-1 describes the information flow MCPTT private call transfer response from the MCPTT client to the MCPTT server.
Table 10.7.6.1.4-1: MCPTT private call transfer response (MCPTT client to MCPTT server) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the party to be transferred (original calling party)
MCPTT ID
M
The MCPTT ID of the target of the transfer
Result
M
Result of the server initiated transfer request – success or fail.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.6.2 Procedures
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.6.2.1 MCPTT private call unannounced transfer in a single MCPTT system
|
The procedure for MCPTT private call unannounced transfer covers the case where an MCPTT client requests an ongoing MCPTT private call (with or without floor control) to be transferred to another MCPTT user without prior announcement.
Figure 10.7.6.2.1-1 below illustrates the procedure for MCPTT private call unannounced transfer.
Pre-conditions:
1. MCPTT client 2 is authorized to use call transfer.
2. MCPTT client 1 is authorized to make private calls to MCPTT client 2.
3. MCPTT client 2 is authorized to transfer private calls to MCPTT client 3.
4. MCPTT client 1 has the necessary security information to initiate a private call with MCPTT client 2 and MCPTT client 3 if end2end encryption is required for the private call.
Figure 10.7.6.2.1-1: MCPTT private call unannounced transfer
1. MCPTT client 1 initiates an MCPTT private call to MCPTT client 2 using the normal MCPTT call establishment as described in subclause 10.7.2.2. The MCPTT private call is established, and the user at MCPTT client 1 can talk with the user at MCPTT client 2.
2. Now the MCPTT user at MCPTT client 2 decides to perform a call transfer.
3. The MCPTT client 2 sends an MCPTT call transfer request to the MCPTT server.
4. The MCPTT server verifies that MCPTT client 2 is authorized to transfer the MCPTT private call to MCPTT client 3. This check is based on entries in the user profile of the user at MCPTT client 2. First, the MCPTT server checks the value of the "Allow private call transfer" entry. If it is false, the authorization check has failed, and the procedure continues with step 5. Otherwise the MCPTT server checks if the "Authorised to transfer private calls to any MCPTT user" entry is true. If this is the case the check has passed, and for target type of MCPTT ID the procedure continues with step 5 and for target ID type of functional alias the procedure continues with step 4a. The subsequent checking depends on the type of target ID. If the target ID is a MCPTT ID, the MCPTT server checks for a matching entry of the target MCPTT ID in the "List of MCPTT users that the MCPTT user is authorised to use as targets for call transfer" list. If a matching entry is found, the check has passed, if no matching entry is found the check has failed, for any outcome the procedure continues with step 5. If the target ID is a functional alias, the MCPTT server checks for a matching entry of the target functional alias in the "List of functional aliases that the MCPTT user is authorised to use as targets for call transfer" list. If a matching entry is found, the check has passed, and the procedure continues with step 4a. If no matching entry is found, the authorization check has failed and the procedure continues with step 5.
4a. If the target of the MCPTT private call transfer is a functional alias instead of an MCPTT ID the MCPTT server resolves the functional alias to the corresponding MCPTT ID for which the functional alias is active.
NOTE 1: Depending on implementation the MCPTT server can apply additional call restrictions and decide whether the call is allowed to proceed with the resolved MCPTT ID(s) (e.g. whether the MCPTT ID is within the allowed area of the functional alias). If the MCPTT server detects that the functional alias used as the target of the MCPTT private call transfer is simultaneously active for multiple MCPTT users, then the MCPTT server can proceed by selecting an appropriate MCPTT ID based on some selection criteria (e.g. current location of the initiating user to determine the dispatcher who is responsible for the related geographic area). The selection of an appropriate MCPTT ID is left to implementation. The selection criteria can include rejection of the call, if no suitable MCPTT ID is selected.
5. If the authorization check has failed, or the target of the transfer is a functional alias that is not active, or the target of the transfer is a functional alias that is simultaneously active by multiple users and the outcome of the selection is a rejection, the MCPTT private call transfer is cancelled, and the MCPTT server sends an MCPTT private call transfer response with result "fail" back to MCPTT client 2. The MCPTT private call between MCPTT client 1 and MCPTT client 2 remains up, and the procedure stops. Otherwise, the procedure continues.
6. MCPTT client 2 initiates release of the private call between MCPTT client 1 and MCPTT client 2 as described in subclause 10.7.2.2.3.1. This step can occur at any time after step 5, since a new private call between MCPTT client 1 and MCPTT client 3 is independent of the private call between MCPTT client 1 and MCPTT client 2.
7. The MCPTT server sends an MCPTT call transfer request towards the MCPTT client 1.
8. Optionally the user at MCPTT client 1 is notified that a call transfer is in progress.
9. MCPTT client 1 sends an MCPTT call transfer response back to the MCPTT server.
10. MCPTT client 1 sends an MCPTT private call request towards the MCPTT server that includes a call transfer indication set to true.
11. The MCPTT server verifies that MCPTT client 1 is authorized to perform the MCPTT private call as a result of the MCPTT private call transfer request based on the fact that the transfer indication is present and set to true in the MCPTT private call request.
NOTE 2: For call transfer the MCPTT server does not check if the initial originating MCPTT user at MCPTT client 1 is authorized to make an MCPTT private call to the final target MCPTT user at MCPTT client 3.
12. The MCPTT server sends an MCPTT call request to MCPTT client 3.
13. The user at MCPTT client 3 is notified about the incoming call.
14. MCPTT client 3 sends an MCPTT private call response back to the MCPTT server.
15. The MCPTT server forwards the MCPTT private call response towards MCPTT client 1.
16. The media plane for communication between MCPTT client 1 and MCPTT client 3 is established.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.6.2.2 MCPTT private call announced transfer in a single MCPTT system
|
The procedure for MCPTT private call announced transfer covers the case where an MCPTT client requests an ongoing MCPTT private call (with or without floor control) to be transferred to another MCPTT user with prior announcement.
Figure 10.7.6.2.2-1 below illustrates the procedure for MCPTT private call announced transfer.
Pre-conditions:
1. MCPTT client 2 is authorized to use call transfer.
2. MCPTT client 1 is authorized to make private calls to MCPTT client 2.
3. MCPTT client 2 is authorized to make private calls to MCPTT client 3.
4. MCPTT client 2 is authorized to transfer private calls to MCPTT client 3.
5. MCPTT client 2 supports simultaneous sessions for MCPTT private calls (10.8).
6. MCPTT client 1 has the necessary security information to initiate a private call with MCPTT client 2 and MCPTT client 3, and MCPTT client 2 has the necessary security information to initiate a private call with MCPTT client 3 if end2end encryption is required for the private call.
Figure 10.7.6.2.2-1: MCPTT private call announced transfer
1. MCPTT client 1 initiates an MCPTT private call to MCPTT client 2 using the normal MCPTT call establishment as described in subclause 10.7.2.2. The MCPTT private call is established, and the user at MCPTT client 1 can talk with the user at MCPTT client 2. The user at MCPTT client 2 decides to transfer the call.
2. The MCPTT user at MCPTT client 2 puts the call on hold.
3. MCPTT client 2 initiates an MCPTT private call to MCPTT client 3 using the normal MCPTT call establishment procedures as described in subclause 10.7.2.2. The MCPTT private call is established, and the user at MCPTT client 2 can talk with the user at MCPTT client 3.
4. The user at MCPTT client 2 can talk with the user at MCPTT client 3 and announce the call transfer.
5. The MCPTT client 2 releases the MCPTT private call with MCPTT client 3 using the normal MCPTT call release procedure as described in subclause 10.7.2.2.3.1. This step can occur at any time after step 4.
6. Optionally the MCPTT user at MCPTT client 2 puts the call with MCPTT client 1 off hold and confirms that the call will be transferred.
7. The MCPTT client 2 sends an MCPTT call transfer request to the MCPTT server.
8. The MCPTT server verifies that MCPTT client 2 is authorized to transfer the MCPTT private call to MCPTT client 3. This check is based on entries in the user profile of the user at MCPTT client 2. First, the MCPTT server checks the value of the "Allow private call transfer" entry. If it is false, the authorization check has failed, and the procedure continues with step 10. Otherwise the MCPTT server checks if the "Authorised to transfer private calls to any MCPTT user" entry is true. If this is the case the check has passed, and for target type of MCPTT ID the procedure continues with step 10 and for target ID type of functional alias the procedure continues with step 9. The subsequent checking depends on the type of target ID. If the target ID is a MCPTT ID, the MCPTT server checks for a matching entry of the target MCPTT ID in the "List of MCPTT users that the MCPTT user is authorised to use as targets for call transfer" list. If a matching entry is found, the check has passed, if no matching entry is found the check has failed, for any outcome the procedure continues with step 10. If the target ID is a functional alias, the MCPTT server checks for a matching entry of the target functional alias in the "List of functional aliases that the MCPTT user is authorised to use as targets for call transfer" list. If a matching entry is found, the check has passed, and the procedure continues with step 9. If no matching entry is found, the authorization check has failed and the procedure continues with step 10.
9. If the target of the MCPTT private call transfer is a functional alias instead of an MCPTT ID the MCPTT server resolves the functional alias to the corresponding MCPTT ID for which the functional alias is active.
NOTE 1: Depending on implementation the MCPTT server can apply additional call restrictions and decide whether the call is allowed to proceed with the resolved MCPTT ID(s) (e.g. whether the MCPTT ID is within the allowed area of the functional alias). If the MCPTT server detects that the functional alias used as the target of the MCPTT private call transfer is simultaneously active for multiple MCPTT users, then the MCPTT server can proceed by selecting an appropriate MCPTT ID based on some selection criteria (e.g. current location of the initiating user to determine the dispatcher who is responsible for the related geographic area). The selection of an appropriate MCPTT ID is left to implementation. The selection criteria can include rejection of the call, if no suitable MCPTT ID is selected.
10. If the authorization check has failed, or the target of the transfer is a functional alias that is not active, or the target of the transfer is a functional alias that is simultaneously active by multiple users and the outcome of the selection is a rejection, the MCPTT private call transfer is cancelled, and the MCPTT server sends an MCPTT private call transfer response with result "fail" back to MCPTT client 2. The MCPTT private call between MCPTT client 1 and MCPTT client 2 remains up, and the procedure stops. Otherwise, the procedure continues.
11. MCPTT client 2 initiates release of the private call between MCPTT client 1 and MCPTT client 2 as described in subclause 10.7.2.2.3.1. This step can occur at any time after step 10, since a new private call between MCPTT client 1 and MCPTT client 3 is independent of the private call between MCPTT client 1 and MCPTT client 2.
12. The MCPTT server sends an MCPTT call transfer request towards the MCPTT client 1.
13. Optionally the user at MCPTT client 1 is notified that a call transfer is in progress.
14. MCPTT client 1 sends an MCPTT call transfer response back to the MCPTT server.
15. MCPTT client 1 sends an MCPTT private call request towards the MCPTT server that includes a call transfer indication set to true.
16. The MCPTT server verifies that MCPTT client 1 is authorized to perform the MCPTT private call as a result of the MCPTT private call transfer request based on the fact that the transfer indication is present and set to true in the MCPTT private call request.
NOTE 2: For call transfer the MCPTT server does not check if the initial originating MCPTT user at MCPTT client 1 is authorized to make an MCPTT private call to the final target MCPTT user at MCPTT client 3.
17. The MCPTT server sends an MCPTT call request to MCPTT client 3.
18. The user at MCPTT client 3 is notified about the incoming call.
19. MCPTT client 3 sends an MCPTT private call response back to the MCPTT server.
20. The MCPTT server forwards the MCPTT private call response towards MCPTT client 1.
21. The media plane for communication between MCPTT client 1 and MCPTT client 3 is established.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.6.2.3 MCPTT private call announced transfer with target in partner MCPTT system
|
The procedure for MCPTT private call announced transfer covers the case where an MCPTT client requests an ongoing MCPTT private call (with or without floor control) to be transferred to another MCPTT user with prior announcement.
Figure 10.7.6.2.3-1 below illustrates the procedure for MCPTT private call announced transfer with target in partner MCPTT system.
NOTE 1: The procedure for MCPTT private call unannounced transfer is very similar, the only difference is that steps 2-6 are skipped.
Pre-conditions:
1. MCPTT client 2 is authorized to use call transfer.
2. MCPTT client 1 is authorized to make private calls to MCPTT client 2.
3. MCPTT client 2 is authorized to make private calls to MCPTT client 3.
4. MCPTT client 2 is authorized to transfer private calls to MCPTT client 3.
5. MCPTT client 2 supports simultaneous sessions for MCPTT private calls (10.8).
6. MCPTT client 1 has the necessary security information to initiate a private call with MCPTT client 2 and MCPTT client 3, and MCPTT client 2 has the necessary security information to initiate a private call with MCPTT client 3 if end2end encryption is required for the private call.
Figure 10.7.6.2.3-1: MCPTT private call announced transfer with target in partner MCPTT system
1. MCPTT client 1 initiates an MCPTT private call to MCPTT client 2 using the normal MCPTT call establishment as described in subclause 10.7.2.2. The MCPTT private call is established, and the user at MCPTT client 1 can talk with the user at MCPTT client 2. The user at MCPTT client 2 decides to transfer the call.
2. The MCPTT user at MCPTT client 2 puts the call with MCPTT user at MCPTT client 1 on hold.
3. MCPTT client 2 initiates an MCPTT private call to MCPTT client 3 using the normal MCPTT call establishment procedures as described in subclause 10.7.2.3. The MCPTT private call is established, and the user at MCPTT client 2 can talk with the user at MCPTT client 3.
NOTE 2: The procedure for private call using functional alias towards a partner MC system is defined in clause 10.16.3 in 3GPP TS 23.280[16].
4. The user at MCPTT client 2 can talk with the user at MCPTT client 3 and announces the call transfer.
5. The MCPTT client 2 releases the MCPTT private call with MCPTT client 3 using the normal MCPTT call release procedure as described in subclause 10.7.2.3. This step can occur at any time after step 4.
6. The MCPTT user at MCPTT client 2 puts the call with MCPTT client 1 off hold and confirms that the call will be transferred.
7. The MCPTT client 2 sends an MCPTT call transfer request to the MCPTT server 1.
8. The MCPTT server 1 verifies that MCPTT client 2 is authorized to transfer the MCPTT private call to MCPTT client 3. This check is based on entries in the user profile of the user at MCPTT client 2. First, the MCPTT server 1 checks the value of the "Allow private call transfer" entry. If it is false, the authorization check has failed, and the procedure continues with step 10. Otherwise, the MCPTT server 1 checks if the "Authorised to transfer private calls to any MCPTT user" entry is true. If this is the case the check has passed, and for target type of MCPTT ID the procedure continues with step 10 and for target ID type of functional alias the procedure continues with step 9. The subsequent checking depends on the type of target ID. If the target ID is a MCPTT ID, the MCPTT server 1 checks for a matching entry of the target MCPTT ID in the "List of MCPTT users that the MCPTT user is authorised to use as targets for call transfer" list. If a matching entry is found, the check has passed, if no matching entry is found the check has failed, for any outcome the procedure continues with step 10. If the target ID is a functional alias, the MCPTT server 1 checks for a matching entry of the target functional alias in the "List of functional aliases that the MCPTT user is authorised to use as targets for call transfer" list. If a matching entry is found, the check has passed, and the procedure continues with step 9. If no matching entry is found, the authorization check has failed and the procedure continues with step 10.
9. If the target of the MCPTT private call transfer is a functional alias instead of an MCPTT ID the MCPTT server 1 resolves the functional alias to the corresponding MCPTT ID for which the functional alias is active.
NOTE 3: Depending on implementation the MCPTT server can apply additional call restrictions and decide whether the call is allowed to proceed with the resolved MCPTT ID(s) (e.g. whether the MCPTT ID is within the allowed area of the functional alias). If the MCPTT server detects that the functional alias used as the target of the MCPTT private call transfer is simultaneously active for multiple MCPTT users, then the MCPTT server can proceed by selecting an appropriate MCPTT ID based on some selection criteria (e.g. current location of the initiating user to determine the dispatcher who is responsible for the related geographic area). The selection of an appropriate MCPTT ID is left to implementation. The selection criteria can include rejection of the call, if no suitable MCPTT ID is selected.
10. If the authorization check has failed, or the target of the transfer is a functional alias that is not active, or the target of the transfer is a functional alias that is simultaneously active by multiple users and the outcome of the selection is a rejection, the MCPTT private call transfer is cancelled, and the MCPTT server 1 sends an MCPTT private call transfer response with result "fail" back to MCPTT client 2. The MCPTT private call between MCPTT client 1 and MCPTT client 2 remains up, and the procedure stops. Otherwise the procedure continues.
11. The MCPTT server 1 sends an MCPTT call transfer request towards the MCPTT client 1.
12. Optionally the user at MCPTT client 1 is notified that a call transfer is in progress.
13. MCPTT client 1 sends an MCPTT private call request towards the MCPTT server 1 that includes a call transfer indication set to true.
14. The MCPTT server 1 verifies that MCPTT client 1 is authorized to perform the MCPTT private call as a result of the MCPTT private call transfer request based on the fact that the transfer indication is present and set to true in the MCPTT private call request.
NOTE 4: For call transfer the MCPTT server does not check if the initial originating MCPTT user at MCPTT client 1 is authorized to make an MCPTT private call to the final target MCPTT user at MCPTT client 3.
15. The MCPTT server 1 sends an MCPTT call request to MCPTT server 2.
16. The MCPTT server 2 sends an MCPTT call request to MCPTT client 3.
NOTE 5: MCPTT server 2 detects that the private call request contains a transfer indication set to true and therefore skips the authorization checking.
17. The user at MCPTT client 3 is notified about the incoming call.
18. MCPTT client 3 sends an MCPTT private call response back to the MCPTT server 2.
19. MCPTT server 2 sends an MCPTT private call response back to the MCPTT server 1.
20. The MCPTT server 1 forwards the MCPTT private call response towards MCPTT client 1.
21. MCPTT client 1 sends an MCPTT call transfer response back to MCPTT server 1.
22. The MCPTT server 1 forwards the MCPTT private transfer response towards MCPTT client 2.
23. MCPTT client 2 initiates release of the private call between MCPTT client 1 and MCPTT client 2 as described in subclause 10.7.2.3.
24. The media plane for communication between MCPTT client 1 and MCPTT client 3 is established.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.7.6.2.4 MCPTT private call announced transfer with transferring MCPTT user in partner MCPTT system
|
The procedure for MCPTT private call announced transfer covers the case where an MCPTT client requests an ongoing MCPTT private call (with or without floor control) to be transferred to another MCPTT user with prior announcement.
Figure 10.7.6.2.4-1 below illustrates the procedure for MCPTT private call announced transfer with transferring MCPTT user in partner MCPTT system.
NOTE 1: The procedure for MCPTT private call unannounced transfer is very similar, the only difference is that steps 2-6 are skipped.
Pre-conditions:
1. MCPTT client 3 is authorized to use call transfer.
2. MCPTT client 1 is authorized to make private calls to MCPTT client 3.
3. MCPTT client 3 is authorized to make private calls to MCPTT client 2.
4. MCPTT client 3 is authorized to transfer private calls to MCPTT client 2.
5. MCPTT client 3 supports simultaneous sessions for MCPTT private calls (10.8).
6. MCPTT client 1 has the necessary security information to initiate a private call with MCPTT client 2 and MCPTT client 3, and MCPTT client 3 has the necessary security information to initiate a private call with MCPTT client 2 if end2end encryption is required for the private call.
Figure 10.7.6.2.4-1: MCPTT private call announced transfer transferring MCPTT user in partner MCPTT system
1. MCPTT client 1 initiates an MCPTT private call to MCPTT client 3 using the normal MCPTT call establishment as described in subclause 10.7.2.3. The MCPTT private call is established, and the user at MCPTT client 1 can talk with the user at MCPTT client 3. The user at MCPTT client 3 decides to transfer the call.
NOTE 2: The procedure for private call using functional alias towards a partner MC system is defined in clause 10.16.3 in 3GPP TS 23.280[16].
2. The MCPTT user at MCPTT client 3 puts the call with MCPTT user at MCPTT client 1 on hold.
3. MCPTT client 3 initiates an MCPTT private call to MCPTT client 2 using the normal MCPTT call establishment procedures as described in subclause 10.7.2.3. The MCPTT private call is established, and the user at MCPTT client 3 can talk with the user at MCPTT client 2.
NOTE 3: The procedure for private call using functional alias towards a partner MC system is defined in clause 10.16.3 in 3GPP TS 23.280[16].
4. The user at MCPTT client 3 can talk with the user at MCPTT client 2 and announce the call transfer.
5. The MCPTT client 3 releases the MCPTT private call with MCPTT client 2 using the normal MCPTT call release procedure as described in subclause 10.7.2.3. This step can occur at any time after step 4.
6. The MCPTT user at MCPTT client 3 puts the call with MCPTT client 1 off hold and confirms that the call will be transferred.
7. The MCPTT client 3 sends an MCPTT call transfer request to the MCPTT server 2.
8. The MCPTT server 2 verifies that MCPTT client 3 is authorized to transfer the MCPTT private call to MCPTT client 2. This check is based on entries in the user profile of the user at MCPTT client 3. First, the MCPTT server 2 checks the value of the "Allow private call transfer" entry. If it is false, the authorization check has failed, and the procedure continues with step 10. Otherwise, the MCPTT server 2 checks if the "Authorised to transfer private calls to any MCPTT user" entry is true. If this is the case the check has passed, and for target type of MCPTT ID the procedure continues with step 10 and for target ID type of functional alias the procedure continues with step 9. The subsequent checking depends on the type of target ID. If the target ID is an MCPTT ID, the MCPTT server 2 checks for a matching entry of the target MCPTT ID in the "List of MCPTT users that the MCPTT user is authorised to use as targets for call transfer" list. If a matching entry is found, the check has passed, if no matching entry is found the check has failed, for any outcome the procedure continues with step 10. If the target ID is a functional alias, the MCPTT server 2 checks for a matching entry of the target functional alias in the "List of functional aliases that the MCPTT user is authorised to use as targets for call transfer" list. If a matching entry is found, the check has passed, and the procedure continues with step 9. If no matching entry is found, the authorization check has failed and the procedure continues with step 10.
9. If the target of the MCPTT private call transfer is a functional alias instead of an MCPTT ID the MCPTT server 2 resolves the functional alias to the corresponding MCPTT ID for which the functional alias is active.
NOTE 4: Depending on implementation the MCPTT server can apply additional call restrictions and decide whether the call is allowed to proceed with the resolved MCPTT ID(s) (e.g. whether the MCPTT ID is within the allowed area of the functional alias). If the MCPTT server detects that the functional alias used as the target of the MCPTT private call transfer is simultaneously active for multiple MCPTT users, then the MCPTT server can proceed by selecting an appropriate MCPTT ID based on some selection criteria (e.g. current location of the initiating user to determine the dispatcher who is responsible for the related geographic area). The selection of an appropriate MCPTT ID is left to implementation. The selection criteria can include rejection of the call, if no suitable MCPTT ID is selected.
10. If the authorization check has failed, or the target of the transfer is a functional alias that is not active, or the target of the transfer is a functional alias that is simultaneously active by multiple users and the outcome of the selection is a rejection, the MCPTT private call transfer is cancelled, and the MCPTT server 2 sends an MCPTT private call transfer response with result "fail" back to MCPTT client 3. The MCPTT private call between MCPTT client 3 and MCPTT client 2 remains up, and the procedure stops. Otherwise the procedure continues.
11. The MCPTT server 2 sends an MCPTT call transfer request towards the MCPTT server 1.
12. The MCPTT server 1 sends an MCPTT call transfer request towards the MCPTT client 1.
13. Optionally the user at MCPTT client 1 is notified that a call transfer is in progress.
14. MCPTT client 1 sends an MCPTT private call request towards the MCPTT server 1 that includes a call transfer indication set to true.
15. The MCPTT server 1 verifies that MCPTT client 1 is authorized to perform the MCPTT private call as a result of the MCPTT private call transfer request based on the fact that the transfer indication is present and set to true in the MCPTT private call request.
NOTE 5: For call transfer the MCPTT server does not check if the initial originating MCPTT user at MCPTT client 1 is authorized to make an MCPTT private call to the final target MCPTT user at MCPTT client 2.
16. The MCPTT server 1 sends an MCPTT private call request to MCPTT client 2.
17. The user at MCPTT client 2 is notified about the incoming call.
18. MCPTT client 2 sends an MCPTT private call response back to the MCPTT server 1.
19. The MCPTT server 1 forwards the MCPTT private call response towards MCPTT client 1.
20. MCPTT client 1 sends an MCPTT call transfer response back to the MCPTT server 1.
21. The MCPTT server 1 sends an MCPTT call transfer response back to the MCPTT server 2.
22. The MCPTT server 2 sends an MCPTT call transfer response back to the MCPTT client 3.
23. MCPTT client 3 initiates release of the private call between MCPTT client 3 and MCPTT client 1 as described in subclause 10.7.2.3.
24. The media plane for communication between MCPTT client 1 and MCPTT client 2 is established.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.8 Simultaneous session for MCPTT calls (on-network)
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.8.1 General
|
An MCPTT client and MCPTT server may use a simultaneous session as defined in 3GPP TS 23.280 [16] for MCPTT calls. The MCPTT client becomes involved in a simultaneous session for MCPTT calls by inviting, joining or accepting more than one MCPTT call, or affiliating to a group.
NOTE: An MCPTT client affiliating to multiple MCPTT groups with active calls will result in the MCPTT client being invited simultaneously to multiple MCPTT calls.
The MCPTT client can also still handle multiple MCPTT calls in parallel at the same time i.e. using multiple dialogs.
The simultaneous session is established during either an originating on-demand call establishment or during pre-established session establishment or a modification of an already established pre-established session or on-demand call.
It is possible to change the prioritisation while the MCPTT client is engaged in multiple MCPTT calls. The setting of the priority can be made at MCPTT call setup or by performing a modification after the MCPTT call is established. This may result in more than one media bearer.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9 Floor control
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1 Floor control for on-network MCPTT service
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.1 General
|
The procedure is for providing a floor control to MCPTT UE in an on-network case and applies for both private call and group call. Floor control is performed by using floor control information flows between the floor participant and the floor control server. The procedures with a single floor control server are applicable to both, all participants are in a single MC system and when participants are in multiple MC systems. The floor control procedures with multiple floor control servers are only applicable when participants are in multiple MC systems.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.2 Information flows for floor control for on-network
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.2.1 General
|
When the floor control server receives a floor request from the floor participant, it decides whether to give a grant or not based on, e.g., the session status (i.e., whether the grant is given to another user or not), user profile, priority. The result is informed to the requesting floor participant. When the floor participant receives a floor granted message, it can send voice media over the uplink bearer established beforehand. The floor revoked message can be used as part of override. The floor queue status request can be used to know current position in the queue for floor.
Some floor control information flows can also piggyback call control information flows to provide efficient call setup and clearing:
- Call setup request is optionally carried in floor request (uplink) or floor taken (downlink, can be broadcast); and
- Call release request is optionally carried in floor release (uplink) or floor idle (downlink, can be broadcast).
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.