Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 23.379  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   4…   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.2…   10.6.2.4…   10.6.2.5…   10.6.2.6…   10.6.2.7…   10.6.2.9…   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.6…   10.9…   10.9.1.3…   10.9.2…   10.10…   10.14…   A…   A.4…   B…

 

10.7.5  MCPTT call forwarding for private calls |R16|

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).
Up
10.7.5.1.1Void
10.7.5.1.2  MCPTT private call forwarding request (MCPTT client to MCPTT server)Word‑p. 153
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.
Information Element Status Description
MCPTT IDMThe MCPTT ID requesting the call forwarding
MCPTT IDMThe MCPTT ID originating the MCPTT private call
MCPTT ID (see NOTE)OThe target MCPTT ID of the call forwarding
Functional alias (see NOTE)OThe target functional alias of the call forwarding
Up
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.
Information Element Status Description
MCPTT IDMThe MCPTT ID requesting the call call forwarding
ResultMResult of the call forwarding request - success or fail
Up
10.7.5.1.4  MCPTT private call forwarding request (MCPTT server to MCPTT client) |R17|
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.
Information Element Status Description
MCPTT IDMThe MCPTT ID of the party to be forwarded
MCPTT IDMThe target MCPTT ID of the call forwarding
Up
10.7.5.1.5  MCPTT private call forwarding response (MCPTT client to MCPTT server) |R17|
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.
Information Element Status Description
MCPTT IDMThe MCPTT ID of the party to be forwarded
MCPTT IDMThe MCPTT ID of the target of the forwarding
ResultMResult of the call forwarding request - success or fail
Up

10.7.5.2  ProceduresWord‑p. 154
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 TS 23.280, subclause 10.1.4.5.
10.7.5.2.2  MCPTT immediate private call forwarding
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.
(not reproduced yet)
Figure 10.7.5.2.2-1: Call forwarding immediate for private calls
Up
Step 1.
MCPTT client 1 sends an MCPTT private call request towards the MCPTT server.
Step 2.
The MCPTT server detects that MCPTT client 2 has immediate call forwarding enabled.
Step 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.
Step 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.
Step 3b.
MCPTT client 1 sends an MCPTT call private cancel response back to the MCPTT server, and the procedure ends.
Step 4.
The MCPTT server sends an MCPTT private call forwarding request towards MCPTT client 1.
Step 5.
The user at MCPTT client 1 is notified that a call forwarding is in process.
Step 6.
MCPTT client 1 sends an MCPTT call private forwarding response back to the MCPTT server.
Step 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.
Step 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.
Step 9.
The MCPTT server sends an MCPTT private call request towards MCPTT client 3.
Step 10.
Optionally the MCPTT server 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 the MCPTT server. This step is not required in case of automatic commencement mode.
Step 12.
The MCPTT server sends an MCPTT ringing to MCPTT client 1. This step is not required in case of automatic commencement mode.
Step 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.
Step 14.
The MCPTT server sends an MCPTT private call response to MCPTT client 1 indicating that MCPTT client 3 has accepted the call.
Step 15.
The media plane for communication between MCPTT client 1 and MCPTT client 3 is established.
Up
10.7.5.2.3  MCPTT private call forwarding no answerWord‑p. 156
Figure 10.7.5.2.3-1 below illustrates the procedure of call forwarding no answer of MCPTT private calls.
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.
(not reproduced yet)
Figure 10.7.5.2.3-1: MCPTT call forwarding no answer
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 7. 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 7.
Step 4.
The user at MCPTT client 2 is alerted. MCPTT client 2 sends an MCPTT ringing to the MCPTT server.
Step 5.
The MCPTT server sends an MCPTT ringing to the MCPTT client 1. This step is not required in case of automatic commencement mode.
Step 6.
The MCPPT server detects that MCPTT client 2 does not answer within the specified time interval.
Step 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.
Step 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.
Step 7b.
MCPTT client 1 sends an MCPTT call private cancel response back to the MCPTT server, and the procedure ends.
Step 8.
The MCPTT server sends an MCPTT private call forwarding request towards the MCPTT client 1.
Step 9.
The user at MCPTT client 1 is notified that a call forwarding is in process.
Step 10.
MCPTT client 1 sends an MCPTT private call forwarding response back to the MCPTT server.
Step 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.
Step 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.
Step 13.
The MCPTT server sends an MCPTT private call request towards MCPTT client 3.
Step 14.
Optionally the MCPTT server sends an MCPTT progress indication to MCPTT client 1.
Step 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.
Step 16.
The MCPTT server sends an MCPTT ringing to MCPTT client 1. This step is not required in case of automatic commencement mode.
Step 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.
Step 18.
The MCPTT server sends an MCPTT private call response to MCPTT client 1 indicating that MCPTT client 3 has accepted the call.
Step 19.
The media plane for communication between MCPTT client 1 and MCPTT client 3 is established.
Up
10.7.5.2.3a  MCPTT private call forwarding based on manual user input |R17|Word‑p. 160
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.
(not reproduced yet)
Figure 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 forwardingsWord‑p. 163
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


Up   Top   ToC