4 Call Forwarding on mobile subscriber Not Reachable (CFNRc)
24.0823GPPCall Forwarding (CF) Supplementary ServicesRelease 17Stage 3TS
4.1 Normal operation
4.1.1 Served mobile subscriber side
When call forwarding on mobile subscriber not reachable, all incoming calls for the specified basic service(s) when the mobile subscriber is not reachable, will be forwarded without being offered to the served mobile subscriber.
When CFNRc is active, the ability of the served mobile subscriber to originate calls is not affected. However, a NotifySS operation containing the SS‑Status indicating that a conditional call forwarding service is currently active and operative will be sent to the served mobile subscriber each time an outgoing call is made, see figure 4.1.
MS Network
SETUP
————————————————————————————————————————>
e.g. ALERTING
<————————————————————————————————————————
Facility (Invoke = NotifySS (SS-Code, SS-Status))
NOTE: The SS‑Code will be the common SS‑Code for all conditional call forwarding services.
Figure 4.1: Notification to the served mobile subscriber that a conditional call forwarding service is active
4.1.2 Forwarded‑to mobile subscriber side
The forwarded‑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 invoked forwarding service is also included, see figure 4.2.
When multiple forwarding occurs the value of the SS‑Code shall relate to the last invoked forwarding service.
In addition the forwarded-to mobile 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 indicated 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 indicated in 3GPP TS 24.008.
MS Network
SETUP
<————————————————————————————————————————
Facility (Invoke = NotifySS (CFNRc, SS-Notification))
Redirecting party BCD number (screening indicator, presentation indicator, redirecting party digits),
Redirecting party subaddress
NOTE: If the specific call forwarding service is not known the common SS‑Code for call forwarding SS will be used.
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 forwarded. When available, the SS‑Code of the invoked forwarding service is also included, see figure 4.3.
MS Network
SETUP
————————————————————————————————————————>
FACILITY
<————————————————————————————————————————
Facility (Invoke = NotifySS (CFNRc, SS-Notification))
NOTE: If the specific call forwarding service is not known the common SS‑Code for all forwarding SS will be used.
Figure 4.3: Notification to the calling mobile subscriber that the call is forwarded
4.2 Registration
The following information has to be registered in the network:
‑ the ForwardedToNumber which may be accompanied by a ForwardedToSubAddress;
‑ information as to whether all calls or all calls of a specific basic service should be forwarded.
4.2.1 Registration by the served mobile subscriber
A CFNRc registration request from a mobile user shall include the SS‑Code of the forwarding service to be registered and possibly the BasicServiceCode the request applies to. If the BasicServiceCode is not included, the request applies to all basic services.
If the registration is successful, the CFNRc will be registered and activated. The network will then send a return result indicating of acceptance of the request, including the ForwardedToNumber and possibly the applicable BasicService (group) code to which CFNRc is registered. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases the result shall not contain a ForwardedToSubAddress. The result may also contain an SS‑Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS‑Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS‑Status in the result is optional. If the SS‑Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS‑Status parameter if one is received. See figure 4.4.
Note that the use of SS‑Status is to provide backwards compatibility with phase 1.
If the registration is successful, the CFNRc will be registered and activated. The network will then send a return result indicating of acceptance of the request, including the ForwardedToNumber to which CFNRc is registered. If no BasicServiceCode was included in the registration request it is not included in the return result either, see figure 4.4.
If the system cannot accept a registration request, a corresponding error indication is returned to the served mobile subscriber that CFNRc registration was not successful. Error values are specified in 3GPP TS 24.080.
MS Network
REGISTER
————————————————————————————————————————>
Facility (Invoke = RegisterSS (CFNRc, BasicServiceCode, ForwardedToNumber, ForwardedToSubAddress, LongFTNsupported))
RELEASE COMPLETE
<————————————————————————————————————————
Facility (Return result = RegisterSS (BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress))
RELEASE COMPLETE
<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
Facility (Return error (Error))
RELEASE COMPLETE
<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
Facility (Reject (Invoke_problem))
NOTE: If BasicServiceCode is not included it applies to all basic services. The ForwardedToNumber may be accompanied by a ForwardedToSubAddress. The SS‑Code may also indicate the code for "all conditional forwarding SS", as specified in subclause 2.2.1, or the code for "all forwarding SS", as specified in subclause 1.2.1. The SS‑Status may not be included in all cases, see text.
Figure 4.4: Registration of call forwarding on mobile subscriber not reachable
The condition for the presence of longFTNsupport is specified in 3GPP TS 23.082 [15].
4.3 Erasure
A previous registration can be erased in one of three ways:
‑ the subscriber can specifically erase a previous registration with an appropriate control procedure;
‑ the subscriber can register information for CFNRc for the specific basic service to another directory number, thus causing the previous registration of CFNRc to be overridden;
‑ all information is erased as a result of withdrawal of the supplementary service (administrative handling).
4.3.1 Erasure by the served mobile subscriber
A CFNRc erasure request from a mobile subscriber may include the BasicServiceCode. If this is not the case, the erasure applies to all basic services.
If the erasure is successful, the CFNRc service will be erased (and automatically deactivated). The network will then send a return result indicating acceptance of the request. The result is formatted according to the options shown below:
‑ The result includes the BasicService (group) Code for which CFNRc was erased. The result may also contain an SS‑Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS‑Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS‑Status in the result is optional. If the SS‑Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS‑Status parameter if one is received. See figure 4.5.
Note that the use of SS‑Status is to provide backwards compatibility with phase 1.
‑ If the request did not include a BasicServiceCode, and the erasure was successful for all basic services, the network may send an empty return result to the MS. This option applies whether or not an SS Version Indicator is received from the MS.
If the network cannot accept the erasure request, the status of CFNRc in the network remains unchanged. An error indication will then be returned to the served mobile subscriber that erasure of CFNRc was unsuccessful. Error values are specified in 3GPP TS 24.080.
MS Network
REGISTER
————————————————————————————————————————>
Facility (Invoke = EraseSS (CFNRc, BasicServiceCode))
RELEASE COMPLETE
<————————————————————————————————————————
Facility (Return result = EraseSS (BasicServiceCode, SS-Status))
RELEASE COMPLETE
<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
Facility (Return error (Error))
RELEASE COMPLETE
<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
Facility (Reject (Invoke_problem))
NOTE: If BasicServiceCode is not included it applies to all basic services. The SS-Code may also indicate the code for "all conditional forwarding SS" or the code for "all forwarding SS". The SS‑Status may not be included in all cases, see text.
Figure 4.5: Erasure of call forwarding on mobile subscriber not reachable
4.4 Activation
An explicit CFNRc activation request shall contain the SS‑Code of the supplementary service to be activated and possibly the BasicServiceCode the request applies to. If a BasicServiceCode is not included in the activation request the request applies to all basic services against which a CFNRc forwarded‑to number is registered. The user shall receive appropriate notification of acceptance, rejection or partial acceptance of the CFNRc activation request, see figure 4.6.
Error values (which are used in the two latter situations) are specified in 3GPP TS 24.080.
MS Network
REGISTER
————————————————————————————————————————>
Facility (Invoke = ActivateSS (CFNRc, LongFTNsupported, BasicServiceCode))
RELEASE COMPLETE
<————————————————————————————————————————
Facility (Return result = ActivateSS (SS-Status))
RELEASE COMPLETE
<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
Facility (Return error (Error))
RELEASE COMPLETE
<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
Facility (Reject (Invoke_problem))
NOTE: The SS‑Code may also indicate the code "all conditional forwarding SS" group, as specified in subclause 2.2.1, or the "all forwarding SS" group, as specified in subclause 1.2.1.
Figure 4.6: Activation of call forwarding on mobile subscriber not reachable
The condition for the presence of longFTNsupport is specified in 3GPP TS 23.082 [15].
4.5 Deactivation
An explicit CFNRc deactivation request shall contain the SS‑Code of the supplementary service to be deactivated and possibly the BasicServiceCode the request applies to. If a BasicServiceCode is not included in the deactivation request the request applies to all basic services against which CFNRc is activated. The user shall receive appropriate notification of acceptance or rejection of the CFNRc deactivation request, see figure 4.7.
Error values to be used in the latter situation are specified in 3GPP TS 24.080.
Deactivation shall not lead to erasure of the information registered in the network.
MS Network
REGISTER
————————————————————————————————————————>
Facility (Invoke = DeactivateSS (CFNRc, BasicServiceCode))
RELEASE COMPLETE
<————————————————————————————————————————
Facility (Return result = DeactivateSS (SS-Status))
RELEASE COMPLETE
<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
Facility (Return error (Error))
RELEASE COMPLETE
<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
Facility (Reject (Invoke_problem))
NOTE: The SS‑Code may also indicate the "all conditional forwarding SS" group or the "all forwarding SS" group.
Figure 4.7: Deactivation of call forwarding on mobile subscriber not reachable
4.6 Interrogation
Data request
The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. After having requested this procedure the network shall return the following information:
‑ in response to a general data request (i.e. not including a BasicServiceCode) the served mobile subscriber should be given the following data for each basic service group to which CFNRc is registered:
‑ the SS‑Status indicating whether the supplementary service is "not active", "active and operative" or "active and quiescent";
‑ the associated ForwardedToNumber which shall not be accompanied by a ForwardedToSubAddress,
see figure 4.8.
If CFNRc is not registered for any basic service groups, only the SS‑Status parameter indicating "not registered" is returned.
MS Network
REGISTER
————————————————————————————————————————>
Facility (Invoke = InterrogateSS (CFNRc, LongFTNsupported))
RELEASE COMPLETE
<————————————————————————————————————————
Facility (Return result = InterrogateSS (BasicServiceCode, SS-Status, ForwardedToNumber))
RELEASE COMPLETE
<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
Facility (Return error (Error))
RELEASE COMPLETE
<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
Facility (Reject (Invoke_problem))
NOTE: The ForwardedToNumber shall not be accompanied by a ForwardedToSubAddress. The return result may consist of a list of parameters, each relating to a specific basic service group.
Figure 4.8: Interrogation of call forwarding on mobile subscriber not reachable active for all basic services
‑ in response to a specific request (i.e. containing one particular BasicService (group) code), the served mobile subscriber should receive the SS‑Status parameter, indicating whether or not CFNRc is registered, including information as to whether or not it is active and operative or active and quiescent for that basic service group. If CFNRc is registered, the associated ForwardedToNumber shall be given, see figure 4.9. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases the result shall not contain a ForwardedToSubAddress. The condition for the presence of longFTNsupport is specified in 3GPP TS 23.082 [15].
If CFNRc is not registered for the interrogated BasicService (group) code, only the SS‑Status parameter indicating "not registered" is returned.
MS Network
REGISTER
————————————————————————————————————————>
Facility (Invoke = InterrogateSS (CFNRc, BasicServiceCode, LongFTNsupported))
RELEASE COMPLETE
<————————————————————————————————————————
Facility (Return result = InterrogateSS
(BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress))
RELEASE COMPLETE
<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
Facility (Return error (Error))
RELEASE COMPLETE
<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
Facility (Reject (Invoke_problem))
NOTE: The ForwardedToNumber may be accompanied by a ForwardedToSubAddress.
Figure 4.9: Interrogation of active call forwarding on mobile subscriber not reachable for one particular basic service
The values "all forwarding SS" and "all conditional forwarding SS" shall not be sent over the air interface by the MS in an interrogation. If an interrogation is received containing one of these codes the network shall send a return error component. The condition for the presence of longFTNsupport is specified in 3GPP TS 23.082 [15].
4.7 Cross phase compatibility
4.7.1 Network only supports protocol version 1 control of SS by the subscriber
A CFNRc registration request which contains a ForwardedToSubaddress shall be rejected by the network if any network element involved is of protocol version 1.
Note that a CFNRc activation or deactivation request will be rejected by the network is any network element involved is of protocol version 1.
4.7.2 MS only supports protocol version 1 control of SS by the subscriber
In response to a CFNRc interrogation request, where the SS Version Indicator is not received from the MS, the network shall only return data for basic service groups to which CFNRc is activated and operative. Data shall not be returned for basic service groups to which CFNRc is deactivated. This means that the subscriber is not always aware of the true state of the service.
In response to a CFNRc registration or erasure request, where the SS Version Indicator is not received from the MS, the network shall always include the SS‑Status parameter.
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#16 |
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#37 |
0001 |
Long FTN supported is not listed in registration, activation and interrogation message |
7.1.0 |
||||
|
CT#42 |
Upgraded unchanged from Rel-7 |
8.0.0 |
|||||
|
CT#44 |
0003 |
Error in implementing CP-070543 "Long FTN supported is not listed in registration, activation and interrogation message" |
8.1.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 |