22.0823GPPCall Forwarding (CF) Supplementary ServicesStage 1TS
This service permits a called mobile subscriber to have the network send all incoming calls, or just those associated with a specific Basic service group, addressed to the called mobile subscriber’s directory number and which meet no reply to another directory number. The ability of the served mobile subscriber to originate calls is unaffected. If this service is activated, a call is forwarded only if the call meets no reply.
The served mobile subscriber can request a different forwarded-to number for each Basic service group containing a basic service to which she has subscribed.
3.2.2 Applicability to telecommunication services
The applicability of this supplementary service is defined in 3GPP TS 22.004.
A served mobile subscriber is a mobile subscriber of a particular PLMN access who is requesting that calls to her number be forwarded. This subscriber may also be referred to as the forwarding subscriber or the called subscriber.
A forwarded-to subscriber is a subscriber to whom the call shall be forwarded.
3.3 Normal procedures with successful outcome
The supplementary service will be provisioned for all Basic Services subscribed to and to which it is applicable.
The service can be offered with several subscription options. Options apply to all Basic services subscribed to. For each subscription option, only one value can be selected.
Subscription options are summarized below:
Subscription options Value
Forwarding subscriber receives – No
notification that the call has been forwarded – Yes
Calling subscriber receives – No
notification that the call has been forwarded – Yes
MSISDN of the served subscriber can be – No
presented to the forwarded-to subscriber – Yes
The service will be withdrawn at the subscriber’s request or for administrative reasons.
The following information has to be registered in the network:
1) the forwarded-to number, which may be accompanied by a forwarded-to sub-address;
2) information as to whether all calls or all calls of one (or several) specific Basic service group(s) should be forwarded;
If no Basic Service Code is inserted by the user this is interpreted as All Basic Services.
3) the duration of the no reply condition timer.
Registration can take place either by the service provider or with an appropriate control procedure by the subscriber. If the duration of the no reply condition timer is not registered by the mobile subscriber then the previous value set by the mobile subscriber applies. If no previous value exists, a default value set by the service provider applies. The value is in between 5 and 30 seconds, in steps of 5 seconds.
Verification, where possible, of the forwarded-to number should be accomplished before accepting the call forwarding request. This verification is done by a simple check of the forwarded-to number to see if the number is within the allowed number range.
When the mobile subscriber so registers call forwarding on no reply, the network will return notification of acceptance or rejection of the request. This notification will include the forwarded-to number to which call forwarding on no reply is registered and the duration of the no reply condition timer.
A previous registration can be erased in either of three ways:
Firstly, the subscriber can specifically erase a previous registration with an appropriate control procedure.
Secondly, the subscriber can register information for call forwarding on no reply for the specific Basic service group to another directory number, thus causing the previous registration of call forwarding on no reply to be overridden.
Thirdly, all information is erased as a result of withdrawal of the service.
The user shall be allowed to activate Call Forwarding on No Reply (CFNRy) by e.g. using the MMI command described in 3GPP TS 22.030. This activation request may include information of which Basic Service Group(s) it shall apply to. If no such information is included, the Activation request applies to all Basic Service Groups.
When receiving an activation request the network shall activate CFNRy for the Basic Service Groups comprised in the BS group information given by the user against which a CFNRy forwarded-to-number is registered. The Activation(s) shall be in accordance with the rules set out in 3GPP TS 22.004.
The user shall receive a notification that CFNRy has been activated.
The supplementary service is also activated for a Basic service group as a result of Registration for that Basic service group.
An active CFNRy can be deactivated in either of two ways:
– The user may deactivate CFNRy by means of an appropriate control procedure (e.g. as described in 3GPP TS 22.030). A deactivation request may contain information of which Basic Service Group(s) it shall apply to. If no such information is included the Deactivation request applies to all Basic Service Groups.
When receiving a deactivation request the network shall deactivate CFNRy for the Basic Service Groups comprised in the BS group information given by the user against which a CFNRy forwarded-to-number is registered. However, the registered information shall not be erased. The Deactivation(s) shall be in accordance with the rules set out in 3GPP TS 22.004.
Even if there is no data stored against a particular Basic Service group comprised in a deactivation request, the request shall be accepted by the network for the other Basic Service groups included in the information given by the user.
– The service is deactivated as a result of Erasure.
In the former case, and also in the latter if Erasure is user controlled, the user shall receive a notification of whether her request was accepted or rejected in accordance with the rules set out in 3GPP TS 22.004.
If the supplementary service is activated for a Basic service incoming calls for the specified Basic service that are not answered within the period defined by the no reply condition timer, will be forwarded by network invocation.
3.3.8 Normal operation with successful outcome
When call forwarding on no reply is active and operative, incoming calls for the specified Basic Service(s) that are not answered within the period defined by the no reply condition timer, will be forwarded without being offered to the served mobile subscriber.
When an incoming call is forwarded on no reply the served mobile subscriber can, as a subscription option, receive notification (but will not be able to answer the incoming call).
The forwarded-to subscriber will receive an indication that the call has been forwarded with the cause. The cause, when available, will be the appropriate forwarding condition. Depending on the value of the served subscribers subscription option, the forwarded-to subscriber may also receive the MSISDN of the served subscriber.
When multiple forwarding occurs the reason for forwarding and the MSISDN given to the forwarded-to subscriber should relate to the last forwarding subscriber in the chain.
When call forwarding on no reply is active and operative, the ability of the served mobile subscriber to originate calls is not affected. However, an indication that the call forwarding service is currently active and operative on a number will be given to the forwarding party each time an outgoing call is made.
As a subscription option, the served mobile subscriber can request that the calling subscriber receives a notification that the call has been forwarded.
NOTE: In case the notification is implemented using intermediate tones or announcements, the tones and/or announcements to the calling party should not be provided if the information transfer capability is set to UDI.
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 the served mobile subscriber should be given a list of all Basic service groups to which call forwarding on no reply is registered, including information whether it is active and if so, whether it is operative or quiescent, the associated forwarded-to numbers and the duration of the no reply timer;
– in response to a specific request concerning one particular Basic service group, the served mobile subscriber should be informed whether or not call forwarding on no reply is registered, including information whether it is active and if so, whether it is operative or quiescent for that Basic service group. If CFNRy is registered, the associated forwarded-to number and the duration of the no reply timer shall be given.
3.3.12 Charging requirements
The forwarding subscriber may be charged for the forwarded part of the call.
3.4 Exceptional procedures or unsuccessful outcome
If the system cannot accept a registration request, the served mobile subscriber should receive a notification that call forwarding on no reply registration was not successful. Possible causes are:
– service not subscribed to;
– forwarded-to number is invalid directory number;
– use of an operator access prefix;
– insufficient information;
– forwarded-to number is a special service code (e.g. police);
– forwarded-to number is the directory number of the mobile subscriber herself;
– conflicting situation with other supplementary services (e.g. incoming call barring has been activated);
– no basic service provisioned within the basic service group(s).
The network is not required to validate information related to the forwarded-to number.
If the network cannot accept a mobile subscriber’s request for erasure, cause will be returned to the subscriber, such as:
– insufficient information;
– inconsistent with registration.
If the subscriber does not completely specify which call forwarding on no reply request is to be erased, the network will reject the erasure request with appropriate cause.
If no Basic Service Code is inserted by the user, CF will be erased from all Basic Services.
If there is no CFNRy forwarded-to-number registered against a Basic Service group, the activation request for that Basic Service group shall be denied. [However, if there is CFNRy forwarded-to-numbers stored against other Basic Service groups contained in the same activation request, these will be activated.]
Examples of causes for a not accepted activation request:
– service not provisioned;
– conflicting situation with other supplementary services;
– service not registered.
If the network cannot accept a deactivation request, an appropriate cause will be returned to the user, e.g. Service not Active.
Within a PLMN or different PLMNs the number of tandem forwarding connections should be limited. The maximum number of tandem forwarding connections should be limited to a value between 1 and 5. This is to prevent infinite looping.
If the limit of successive forwardings of a call is reached and an attempt is made to forward the call an additional time, then the forwarded call shall be treated as in the following paragraph.
If the forwarded call cannot be completed to the forwarded-to destination, then the network will clear the call towards the calling user with an indication that the call cannot be completed. This indication shall not include information that the call has been forwarded.
NOTE 1: The alerting of the forwarding user shall have ceased on invocation of the CFNRy Service.
NOTE 2: The alerting of the calling subscriber should, if possible, not cease on invocation of CFNRy.
NOTE 3: Call forwarding on no reply applies only to the Basic services subscribed to. Calls to a directory number requesting a Basic service which is not subscribed to will never be forwarded.
3.5 Alternate procedures
3.6 Interactions with other supplementary services
220.127.116.11 Calling line identification presentation
See 3GPP TS 22.081.
18.104.22.168 Calling line identification restriction
See 3GPP TS 22.081.
22.214.171.124 Connected line identification presentation
See 3GPP TS 22.081.
126.96.36.199 Connected line identification restriction
See 3GPP TS 22.081.
188.8.131.52 Call forwarding unconditional
See section 184.108.40.206.
220.127.116.11 Call waiting
See 3GPP TS 22.083.
18.104.22.168 Multi party
See 3GPP TS 22.084.
22.214.171.124 Closed user group
See 3GPP TS 22.085.
126.96.36.199 Advice of charge
See 3GPP TS 22.086.
188.8.131.52 Barring of all outgoing calls
Same as the interaction between call forwarding unconditional and barring of all outgoing calls.
184.108.40.206 Barring of outgoing international calls
Same as the interaction between call forwarding on mobile subscriber busy and barring of outgoing international calls.
220.127.116.11 Barring of outgoing international calls except those directed to the home PLMN country
Same as the interaction between call forwarding on mobile subscriber busy and barring of outgoing international calls except those directed to the home PLMN country.
18.104.22.168 Barring of all incoming calls
Same as the interaction between call forwarding unconditional and barring of all incoming calls.
22.214.171.124 Barring of incoming calls when roaming outside the home PLMN country
Same as the interaction between call forwarding on mobile subscriber busy and barring of incoming calls when roaming outside the home PLMN country.
126.96.36.199 Anonymous Call Rejection
See 3GPP TS 22.088 .
3.7 Interworking considerations
If the forwarded-to number is not a PLMN- or ISDN-number, then an interworking situation is said to exist.
If a forwarded call meets an interworking situation, then an interworking indication should be sent to the calling party. When interworking with non-PLMN or non-ISDN networks, tones and announcements will be required.
NOTE1: The number of times a call has been forwarded once it has exited the PLMN or ISDN may not be limited.
NOTE2: Tones and/or announcements should not be provided to the calling party if the information transfer capability is set to UDI.