Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.379  Word version:  19.3.0

Top   Top   Up   Prev   Next
1…   7…   7.4…   10…   10.5…   10.6…   10.6.2.2.13…   10.6.2.2.24…   10.6.2.3…   10.6.2.3.1.2…   10.6.2.3.2…   10.6.2.4…   10.6.2.4.3…   10.6.2.5…   10.6.2.5.2.3…   10.6.2.6…   10.6.2.6.2…   10.6.2.7…   10.6.2.10…   10.6.3…   10.7…   10.7.2.2…   10.7.2.3…   10.7.3…   10.7.4…   10.7.5…   10.7.5.2.3a…   10.7.6…   10.7.6.2.3…   10.9…   10.9.1.3…   10.9.1.3.2…   10.9.1.3.3…   10.9.1.4…   10.9.1.5…   10.9.2…   10.9.2.6…   10.10…   10.12…   10.14…   10.15…   10.19…   10.19.2.11…   10.19.3…   10.19.3.1.4…   10.19.3.2…   10.19.3.2.4…   10.19.3.2.6…   A…   A.4…   B… 
10.14 Ambient listening call  10.14.1 General  10.14.2 Information flows for ambient listening call  10.14.2.1 Ambient listening call request  10.14.2.2 Ambient listening call response  10.14.2.3 Ambient listening call release request  10.14.2.4 Ambient listening call release response  10.14.2.5 Ambient listening call release notification  10.14.3 Ambient listening call procedures  10.14.3.1 Remotely initiated ambient listening call setup  10.14.3.2 Locally initiated ambient listening call setup  10.14.3.3 Ambient listening call release - server initiated  10.14.3.4 Remotely initiated ambient listening call release - "listening" user initiated  10.14.3.5 Ambient listening call release - "listened to" user initiated 
...

 

10.14  Ambient listening call  p. 207

10.14.1  General  p. 207

The ambient listening call is a type of a private MCPTT call that only allows a "listened to" user to transmit media to a "listening" user such that there is no indication on the MCPTT UE of the "listened to" user about the call and the media transmission.
There are two types of ambient listening call as below:
  • Remotely initiated ambient listening is initiated by the authorized user (e.g., dispatcher) who wants to listen to another user. In this case, the "listened to" user is the called party, and shall automatically accept the call without causing any indication about the call and transmit the media to the "listening" user.
  • Locally initiated ambient listening is initiated by an authorized user who wants another user to listen to the MCPTT UE communication. In this case, the "listened to" user is the calling party and shall automatically transmit the media to the "listening" user without causing any indication about the call processing and media transmission.
Up

10.14.2  Information flows for ambient listening call  p. 207

10.14.2.1  Ambient listening call request  p. 207

Table 10.14.2.1-1 describes the information flow ambient listening call request from the MCPTT client to the MCPTT server and MCPTT server to the MCPTT client.
Information Element Status Description
MCPTT IDM The MCPTT ID of the "listening" user
MCPTT IDM The MCPTT ID of the "listened to" user
SDP offerMMedia parameters of MCPTT client
Ambient listening typeMThe ambient listening type indicates remotely initiated ambient listening call or locally initiated ambient listening call
Up

10.14.2.2  Ambient listening call response  p. 208

Table 10.14.2.2-1 describes the information flow ambient listening call response from the MCPTT client to the MCPTT server and MCPTT server to the MCPTT client.
Information Element Status Description
MCPTT IDM The MCPTT ID of the "listening" user
MCPTT IDM The MCPTT ID of the "listened to" user
SDP answerMMedia parameters selected
Up

10.14.2.3  Ambient listening call release request  p. 208

Table 10.14.2.3-1 describes the information flow ambient listening call release request from the MCPTT client to the MCPTT server and MCPTT server to the MCPTT client.
Information Element Status Description
MCPTT IDM The MCPTT ID of the "listening" user
MCPTT IDM The MCPTT ID of the "listened to" user
Ambient listening typeMThe ambient listening type indicates a remotely initiated ambient listening call or a locally initiated ambient listening call
Up

10.14.2.4  Ambient listening call release response  p. 208

Table 10.14.2.4-1 describes the information flow ambient listening call release response from the MCPTT client to the MCPTT server and MCPTT server to the MCPTT client.
Information Element Status Description
MCPTT IDM The MCPTT ID of the "listening" user
MCPTT IDM The MCPTT ID of the "listened to" user
Ambient listening typeMThe ambient listening type indicates a remotely initiated ambient listening call or a locally initiated ambient listening call
Up

10.14.2.5  Ambient listening call release notification  p. 209

Table 10.14.2.5-1 describes the information flow ambient listening call release notification from the MCPTT server to the MCPTT client.
Information Element Status Description
MCPTT IDM The MCPTT ID of the "listening" user
MCPTT IDM The MCPTT ID of the "listened to" user
Call release reasonMThe reason for call release by the MCPTT server
Ambient listening typeMThe ambient listening type indicates a remotely initiated ambient listening call or a locally initiated ambient listening call
Up

10.14.3  Ambient listening call procedures  p. 209

10.14.3.1  Remotely initiated ambient listening call setup  p. 209

The MCPTT service provides the capability for an authorised user to initiate a remotely initiated ambient listening call at an MCPTT client.
Figure 10.14.3.1-1 illustrates the information flow for remotely initiated ambient listening call setup.
Pre-conditions:
  • MCPTT client 1 is the client of the authorized user who is authorized to invoke a remotely initiated ambient listening call to be set up at the requested MCPTT client 2.
  • MCPTT user 1 is the "listening" user at MCPTT client 1, and MCPTT user 2 is the "listened to" user at MCPTT client 2.
Reproduction of 3GPP TS 23.379, Fig. 10.14.3.1-1: Remotely initiated ambient listening call
Figure 10.14.3.1-1: Remotely initiated ambient listening call
Up
Step 1.
MCPTT client 1 initiates a remotely initiated ambient listening call by sending the ambient listening call request to the MCPTT server. The remotely initiated ambient listening call type is included.
Step 2.
The MCPTT server performs an authorization check for the authorized user 1 for the remotely initiated ambient listening call. If authorization fails, the MCPTT server provides a failure response to MCPTT client 1.
Step 3.
The MCPTT server sends the ambient listening call request to MCPTT client 2.
Step 4.
MCPTT client 2 returns the ambient listening call response to the MCPTT server.
Step 5.
MCPTT server provides an ambient listening call response to MCPTT client 1, indicating whether the call is set up successfully or not.
Step 6.
The floor control server of the MCPTT server then sends a floor granted to MCPTT client 2 according to the ambient listening type received in step 1.
Step 7.
Accordingly, the floor control server of the MCPTT server sends a floor taken to MCPTT client 1.
Step 8.
After receiving the floor granted message at the MCPTT client 2, the media is transmitted from MCPTT client 2 to MCPTT client 1.
Up

10.14.3.2  Locally initiated ambient listening call setup  p. 210

The MCPTT service provides the capability for an authorised user to initiate a locally initiated ambient listening call at an MCPTT client.
Figure 10.14.3.2-1 illustrates the information flow for locally initiated ambient listening call setup.
Pre-conditions:
  • MCPTT client 2 is the client of the authorized user who is authorized to invoke a locally initiated ambient listening call to be set up at the requested MCPTT client 1.
  • MCPTT user 1 is the "listening" user at MCPTT client 1, and MCPTT user 2 is the "listened to" user at MCPTT client 2.
Reproduction of 3GPP TS 23.379, Fig. 10.14.3.2-1: Locally initiated ambient listening call
Figure 10.14.3.2-1: Locally initiated ambient listening call
Up
Step 1.
MCPTT client 2 initiates a locally initiated ambient listening call by sending the ambient listening call request to the MCPTT server. The locally initiated ambient listening call type is included.
Step 2.
The MCPTT server performs an authorization check for the authorized user 2 for the locally initiated ambient listening call. If authorization fails, the MCPTT server provides a failure response to MCPTT client 2.
Step 3.
The MCPTT server sends the ambient listening call request to MCPTT client 1.
Step 4.
MCPTT client 1 returns the ambient listening call response to the MCPTT server.
Step 5.
MCPTT server provides an ambient listening call response to MCPTT client 2, indicating whether the call is set up successfully or not.
Step 6.
The floor control server of the MCPTT server then sends a floor granted to MCPTT client 2 according to the ambient listening type received in step 1.
Step 7.
Accordingly, the floor control server of the MCPTT server sends a floor taken to MCPTT client 1.
Step 8.
After receiving the floor granted message at the MCPTT client 2, the media is transmitted from MCPTT client 2 to MCPTT client 1.
Up

10.14.3.3  Ambient listening call release - server initiated  p. 211

Figure 10.14.3.3-1 illustrates the information flow for ambient listening call release - server initiated when trigger by the MCPTT administrator. This procedure is applied for both remotely initiated ambient listening call and the locally initiated ambient listening call.
Pre-conditions:
  • MCPTT client 1 is the MCPTT client of the authorized user, who initiated the ambient listening call at MCPTT client 2.
  • There is an ongoing ambient listening call between MCPTT client 2 and MCPTT client 1.
  • MCPTT user 1 is the current user at MCPTT client 1 who is listening, and MCPTT user 2 is the current user at MCPTT client 2 who is being listened to.
Reproduction of 3GPP TS 23.379, Fig. 10.14.3.3-1: Ambient listening call release - server initiated
Figure 10.14.3.3-1: Ambient listening call release - server initiated
Up
Step 1.
The ambient listening call release is triggered by the MCPTT administrator or by one of the following events:
  • the MCPTT server receives MCPTT call requests towards MCPTT client 2; or
  • the MCPTT client 2 initiates MCPTT call requests;
Step 2.
The MCPTT server sends an ambient listening call release request to MCPTT client 2.
Step 3.
MCPTT client 2 stops transmitting media to MCPTT client 1.
Step 4.
MCPTT client 2 provides an ambient listening call release response to the MCPTT server.
Step 5.
The MCPTT server sends an ambient listening call release notification to MCPTT client 1 together with a reason code identifying that the call was released.
Step 6.
MCPTT client 1 notifies the authorized user 1.
Up

10.14.3.4  Remotely initiated ambient listening call release - "listening" user initiated  p. 212

Figure 10.14.3.4-1 illustrates the information flow for ambient listening call release - "listening" user initiated. This procedure is applied for both remotely initiated ambient listening call and the locally initiated ambient listening call.
Pre-conditions:
  • MCPTT client 1 is the MCPTT client of the authorized user, who is authorized to release the ambient listening call at MCPTT client 2.
  • There is an ongoing ambient listening call between MCPTT client 2 and MCPTT client 1.
  • MCPTT user 1 is the "listening" user at MCPTT client 1, and MCPTT user 2 is the "listened to"user at MCPTT client 2.
Reproduction of 3GPP TS 23.379, Fig. 10.14.3.4-1: Ambient listening call release - "
Figure 10.14.3.4-1: Ambient listening call release - ""listening" user initiated
Up
Step 1.
The authorized user 1 at MCPTT client 1 initiates the ambient listening call release by sending an ambient listening call release request to the MCPTT server.
Step 2.
The MCPTT server provides an ambient listening call release request to MCPTT client 2.
Step 3.
MCPTT client 2 stops transmitting media to MCPTT client 1.
Step 4.
MCPTT client 2 provides an ambient listening call release response to the MCPTT server.
Step 5.
The MCPTT server provides the ambient listening call release response to MCPTT client 1.
Up

10.14.3.5  Ambient listening call release - "listened to" user initiated  p. 213

Figure 10.14.3.5-1 illustrates the information flow for ambient listening call release - "listened to" user initiated. This procedure is only applied for the locally initiated ambient listening call.
Pre-conditions:
  • There is an ongoing ambient listening call between MCPTT client 1 and MCPTT client 2.
  • MCPTT user 1 is the "listening" user at MCPTT client 1, and MCPTT user 2 is the "listened to" user at MCPTT client 2.
  • MCPTT client 2 is the MCPTT client of the authorized user, who is authorized to release the locally initiated ambient listening call at MCPTT client 2.
Reproduction of 3GPP TS 23.379, Fig. 10.14.3.5-1: Ambient listening call release - "listened to" user initiated
Figure 10.14.3.5-1: Ambient listening call release - "listened to" user initiated
Up
Step 1.
The authorized user 2 at MCPTT client 2 initiates the ambient listening call release by sending an ambient listening call release request to the MCPTT server.
Step 2.
The MCPTT server provides an ambient listening call release request to MCPTT client 1.
Step 3.
The user 1 at MCPTT client 1 is notified about the ambient listening call release.
Step 4.
MCPTT client 1 provides an ambient listening call release response to the MCPTT server.
Step 5.
The MCPTT server provides the ambient listening call release response to MCPTT client 2.
Step 6.
MCPTT client 2 stops transmitting media to MCPTT client 1.
Up

Up   Top   ToC