4 Call Deflection (CD)
24.0723GPPCall Deflection (CD) supplementary serviceRelease 17Stage 3TS
4.1 Normal operation
4.1.1 Served mobile subscriber side
The served mobile subscriber may invoke the call deflection supplementary service if an incoming call is offered. According to 3GPP TS 22.072 this may happen as an automatic response from the mobile station if the call is offered or as the result of a subscriber action.
The mobile station shall invoke the call deflection supplementary service by initiating call clearing with a DISCONNECT message including the call deflection request (refer to figure 4.1). The call deflection request shall contain the DeflectedToNumber which may be accompanied by a DeflectedToSubAddress.
The MS may invoke the call deflection supplementary service at every time after call confirmation until the call is accepted (refer to 3GPP TS 24.008). If the network accepts the call deflection request, it shall continue call clearing. The result indication shall be returned to the mobile station in the RELEASE message.
If the network cannot accept the call deflection request, it shall continue call clearing. The corresponding error indication shall be returned to the mobile station in the RELEASE message. Error values are specified in 3GPP TS 24.080.
During the call deflection request the MS shall run a timer TCD (T305). This timer is started when the call deflection request is sent and stopped when a response is received from the network. If this timer expires the MS shall assume that the call deflection request has failed, locally release the invokeID, inform the user of the failure and continue call clearing as defined in 3GPP TS 24.008.
MS Network
SETUP
<————————————————————————————————————————
CALL CONFIRMED
————————————————————————————————————————>
·
·
·
DISCONNECT
————————————————————————————————————————>
Facility (Invoke = CallDeflection (DeflectedToNumber, DeflectedToSubAddress))
RELEASE
<————————————————————————————————————————
Facility (Return result)
RELEASE
<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
Facility (Return error (Error))
RELEASE
<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
Facility (Reject = (Invoke Problem))
RELEASE COMPLETE
————————————————————————————————————————>
Figure 4.1: Call deflection invocation for an incoming call
4.1.2 Deflected-to mobile subscriber side
As for the call forwarding supplementary services the deflected-to mobile subscriber will receive a NotifySS operation containing the SS Notification indicating that the incoming call is a forwarded call. When available, the SS Code of the Call Deflection supplementary service is included, see figure 4.2.
When multiple diversions occurs the value of the SS Code shall relate to the last invoked diversion service.
In addition the deflected-to subscriber will receive the redirecting party BCD number and optionally, a redirecting party subaddress.
The redirecting party BCD number information element is made up of a number of information units as defined in 3GPP TS 24.008.
In addition to or instead of the redirecting party’s digits, the subscriber may be given the following information:
– screening indicator;
– presentation indicator.
Indicator values are given in 3GPP TS 24.008.
The redirecting party subaddress information element is made up of a number of information units as defined in 3GPP TS 24.008.
MS Network
SETUP
<————————————————————————————————————————
Facility (Invoke = NotifySS (CD, SS-Notification)),
Redirecting party BCD number (screening indicator, presentation indicator, redirecting party digits),
Redirecting party subaddress
Figure 4.2: Notification to the forwarded to mobile subscriber that the incoming call is a forwarded call
4.1.3 Calling mobile subscriber side
As a subscription option, the served mobile subscriber can request that the calling mobile subscriber receives a NotifySS operation containing the SS Notification indicating that the call has been deflected. When available, the SS Code of the call deflection supplementary service is included, see figure 4.3.
MS Network
SETUP
————————————————————————————————————————>
FACILITY
<————————————————————————————————————————
Facility (Invoke = NotifySS (CD, SS-Notification))
Figure 4.3: Notification to the calling mobile subscriber that the call is forwarded
Annex A (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
Apr 1999 |
Transferred to 3GPP CN1 |
||||||
|
CN#03 |
Approved at CN#03 |
3.0.0 |
|||||
|
CN#11 |
Release 4 after CN#11 |
4.0.0 |
|||||
|
CN#15 |
References updated |
4.0.1 |
|||||
|
CN#16 |
Release 5 after CN#16 |
5.0.0 |
|||||
|
CN#26 |
Release 6 after CN#26 |
6.0.0 |
|||||
|
CT#36 |
Upgraded unchanged from Rel-6 |
7.0.0 |
|||||
|
CT#42 |
Upgraded unchanged from Rel-7 |
8.0.0 |
|||||
|
2009-12 |
Update to Rel-9 version (MCC) |
9.0.0 |
|||||
|
2011-03 |
Update to Rel-10 version (MCC) |
10.0.0 |
|||||
|
2012-09 |
Update to Rel-11 version (MCC) |
11.0.0 |
|||||
|
2014-09 |
Update to Rel-12 version (MCC) |
12.0.0 |
|||||
|
2015-12 |
Update to Rel-13 version (MCC) |
13.0.0 |
|||||
|
2017-03 |
Update to Rel-14 version (MCC) |
14.0.0 |
|||||
|
2018-06 |
Update to Rel-15 version (MCC) |
15.0.0 |
|||||
|
2020-07 |
Update to Rel-16 version (MCC) |
16.0.0 |
|||||
|
2022-03 |
CT#95e |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |