Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.379  Word version:  19.0.0

Top   Top   Up   Prev   Next

 

10.7.5.2.3a  MCPTT private call forwarding based on manual user input in a single MCPTT systemp. 162
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.
Reproduction of 3GPP TS 23.379, Fig. 10.7.5.2.3a-1: MCPTT call forwarding based on manual user input
Up
Step 1.
MCPTT client 1 sends an MCPTT private call request towards the MCPTT server.
Step 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.
Step 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.
Step 4.
The user at MCPTT client 2 is alerted. MCPTT client 2 sends an MCPTT ringing to the MCPTT server.
Step 5.
In manual commencement mode the MCPTT server sends an MCPTT ringing to the MCPTT client 1.
Step 6.
During ringing the user at MCPTT client 2 requests the call to be forwarded based on manual input.
Step 7.
MCPTT client 2 sends an MCPTT private call forwarding request to the MCPTT server.
Step 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.
Step 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.
Step 8b.
MCPTT client 1 sends an MCPTT call private cancel response back to the MCPTT server.
Step 8c.
The MCPTT server sends an MCPTT private call forwarding response with Result equals "fail" to MCPTT client 2, and the procedure ends.
Step 9.
The MCPTT server stops the timer for the no answer timeout.
Step 10.
The MCPTT server verifies that no other forwarding with the condition no answer or based on manual user input has occurred so far.
Step 11.
The MCPTT server sends an MCPTT private call forwarding response to MCPTT client 2.
Step 12.
The MCPTT server sends an MCPTT private call forwarding request towards the MCPTT client 1.
Step 13.
The user at MCPTT client 1 is notified that a call forwarding is in process.
Step 14.
MCPTT client 1 sends an MCPTT private call forwarding response back to the MCPTT server.
Step 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.
Step 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.
Step 17.
The MCPTT server sends an MCPTT private call request towards MCPTT client 3.
Step 18.
Optionally the MCPTT server sends an MCPTT progress indication to MCPTT client 1.
Step 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.
Step 20.
The MCPTT server sends an MCPTT ringing to MCPTT client 1. This step is not required in case of automatic commencement mode.
Step 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.
Step 22.
The MCPTT server sends an MCPTT private call response to MCPTT client 1 indicating that MCPTT client 3 has accepted the call.
Step 23.
The media plane for communication between MCPTT client 1 and MCPTT client 3 is established.
Up
10.7.5.2.4  Handling of multiple MCPTT private call forwardingsp. 165
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.
Up
10.7.5.2.5  MCPTT private call forwarding with target of the MCPTT private call forwarding in partner MCPTT system |R18|p. 165
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.
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.
Reproduction of 3GPP TS 23.379, Fig. 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
Up
Step 1.
MCPTT client 1 sends an MCPTT private call request towards MCPTT server 1.
Step 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.
Step 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.
Step 3.
MCPTT server 1 sends an MCPTT private call forwarding request towards MCPTT client 1.
Step 4.
The user at MCPTT client 1 is notified that a call forwarding is in process.
Step 5.
MCPTT client 1 sends an MCPTT call private forwarding response back to MCPTT server 1.
Step 6.
MCPTT client 1 sends an MCPTT private call request towards MCPTT server 1 that includes a call forwarding indication set to true.
Step 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.
Step 8.
MCPTT server 1 sends an MCPTT private call request towards MCPTT server 2.
Step 9.
MCPTT server 2 sends an MCPTT private call request towards MCPTT client 3.
Step 10.
Optionally MCPTT server 1 sends an MCPTT progress indication to MCPTT client 1.
Step 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.
Step 12.
MCPTT server 2 sends an MCPTT ringing to MCPTT server 1. This step is not required in case of automatic commencement mode.
Step 13.
MCPTT server 1 sends an MCPTT ringing to MCPTT client 1. This step is not required in case of automatic commencement mode.
Step 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.
Step 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.
Step 16.
MCPTT server 1 sends an MCPTT private call response to MCPTT client 1 indicating that MCPTT client 3 has accepted the call.
Step 17.
The media plane for communication between MCPTT client 1 and MCPTT client 3 is established.
Up
10.7.5.2.6  MCPTT private call forwarding with MCPTT private call forwarding occurring in the partner MCPTT system |R18|p. 167
The procedure for MCPTT private call forwarding describes the case of an MCPTT private call forwarding occurring in the partner MCPTT system.
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.
Reproduction of 3GPP TS 23.379, Fig. 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
Up
Step 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.
Step 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.
Step 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.
Step 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.
Step 3.
MCPTT server 2 detects that MCPTT client 3 has immediate call forwarding enabled to MCPTT client 2 registered at MCPTT system 1.
Step 4.
MCPTT server 2 sends an MCPTT private call forwarding request towards MCPTT server 1.
Step 5.
MCPTT server 1 sends an MCPTT private call forwarding request towards MCPTT client 1.
Step 6.
The user at MCPTT client 1 is notified that a call forwarding is in process.
Step 7.
MCPTT client 1 sends an MCPTT call private forwarding response back to MCPTT server 1.
Step 8.
MCPTT server 1 sends an MCPTT call private forwarding response back to MCPTT server 2.
Step 9.
MCPTT client 1 sends an MCPTT private call request towards MCPTT server 1 that includes a call forwarding indication set to true.
Step 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.
Step 11.
MCPTT server 1 sends an MCPTT private call request towards MCPTT client 2.
Step 12.
Optionally MCPTT server 1 sends an MCPTT progress indication to MCPTT client 1.
Step 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.
Step 14.
MCPTT server 1 sends an MCPTT ringing to MCPTT client 1. This step is not required in case of automatic commencement mode.
Step 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.
Step 16.
MCPTT server 1 sends an MCPTT private call response to MCPTT client 1 indicating that MCPTT client 2 has accepted the call.
Step 17.
The media plane for communication between MCPTT client 1 and MCPTT client 2 is established.
Up

Up   Top   ToC