Tech-invite  3GPPspace  IETF RFCs  SIP
index  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:  18.4.0

Top   Top   Up   Prev   Next
1…   7…   7.4…   10…   10.5…   10.6…   10.6.2.2.18…   10.6.2.2.34…   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.9…   10.6.2.9.3…   10.6.2.9.4…   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.3…   A…   A.4…   B… 
10.7.4 MCPTT private call call-back request  10.7.4.1 Information flows for MCPTT private call call-back request  10.7.4.1.1 MCPTT private call call-back request  10.7.4.1.2 MCPTT private call call-back response  10.7.4.1.3 MCPTT private call call-back cancel request  10.7.4.1.4 MCPTT private call call-back cancel response  10.7.4.2 MCPTT private call call-back request within one MCPTT system  10.7.4.3 MCPTT private call call-back cancel request within one MCPTT system  10.7.4.4 MCPTT private call call-back request fulfillment within one MCPTT system 
...

 

10.7.4  MCPTT private call call-back request  p. 147

10.7.4.1  Information flows for MCPTT private call call-back request  p. 147

10.7.4.1.1  MCPTT private call call-back request  p. 147
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.
Information Element Status Description
MCPTT IDMThe MCPTT ID of the calling party
MCPTT IDMThe MCPTT ID of the called party
Urgency indicationMThis element indicates the urgency (i.e., low, normal, high) of the call-back request.
Up
10.7.4.1.2  MCPTT private call call-back response  p. 147
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.
Information Element Status Description
MCPTT IDMThe MCPTT ID of the calling party
MCPTT IDMThe MCPTT ID of the called party
ResultMResult of the MCPTT call-back request - success or fail.
Up
10.7.4.1.3  MCPTT private call call-back cancel request  p. 147
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.
Information Element Status Description
MCPTT IDMThe MCPTT ID of the calling party
MCPTT IDMThe MCPTT ID of the called party
Up
10.7.4.1.4  MCPTT private call call-back cancel response  p. 147
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.
Information Element Status Description
MCPTT IDMThe MCPTT ID of the calling party
MCPTT IDMThe MCPTT ID of the called party
ResultMResult of the MCPTT private call call-back cancel request - success or fail
Up

10.7.4.2  MCPTT private call call-back request within one MCPTT system  p. 148

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.
Reproduction of 3GPP TS 23.379, Fig. 10.7.4.2-1: MCPTT private call call-back request - MCPTT users in the same MCPTT system
Figure 10.7.4.2-1: MCPTT private call call-back request - MCPTT users in the same MCPTT system
Up
Step 1.
MCPTT user on MCPTT client 1 initiates an MCPTT private call call-back request to the MCPTT user of MCPTT client 2.
Step 2.
MCPTT client 1 sends an MCPTT private call call-back request towards the MCPTT server.
Step 3.
MCPTT server checks whether the MCPTT user 1 at MCPTT client 1 is authorized to initiate the MCPTT private call call-back request.
Step 4.
If authorized, MCPTT server sends the corresponding MCPTT private call call-back request towards the MCPTT client 2.
Step 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.
Step 6.
The MCPTT client 2 notifies the MCPTT user 2 that there is an MCPTT private call call-back request awaiting his attention.
Step 7.
The receiving MCPTT client 2 sends an MCPTT private call call-back response to the MCPTT server.
Step 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.
Up

10.7.4.3  MCPTT private call call-back cancel request within one MCPTT system  p. 149

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.
Reproduction of 3GPP TS 23.379, Fig. 10.7.4.3-1: MCPTT private call call-back cancel request - MCPTT users in the same MCPTT system
Figure 10.7.4.3-1: MCPTT private call call-back cancel request - MCPTT users in the same MCPTT system
Up
Step 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.
Step 2.
MCPTT client 1 sends an MCPTT private call call-back cancel request towards the MCPTT server.
Step 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.
Step 4.
If authorized, MCPTT server sends the corresponding MCPTT private call call-back cancel request towards the MCPTT client 2.
Step 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.
Step 6.
The receiving MCPTT client 2 sends an MCPTT private call call-back cancel response to the MCPTT server.
Step 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.
Up

10.7.4.4  MCPTT private call call-back request fulfillment within one MCPTT system  p. 150

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.
Reproduction of 3GPP TS 23.379, Fig. 10.7.4.4-1: MCPTT private call-back request fulfillment - MCPTT users in the same MCPTT system
Figure 10.7.4.4-1: MCPTT private call-back request fulfillment - MCPTT users in the same MCPTT system
Up
Step 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.
Step 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.

Up   Top   ToC