Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 22.082  Word version:  18.0.1

Top   Top   Up   Prev   Next
0…   1…   2…   3…   4… 
2 Call Forwarding on Mobile Subscriber Busy  2.1 Definition  2.2 Description  2.3 Normal procedures with successful outcome  2.4 Exceptional procedures or unsuccessful outcome  2.5 Alternate Procedures  2.6 Interactions with other supplementary services  2.7 Interworking considerations 
...

 

2  Call Forwarding on Mobile Subscriber Busy  p. 14

2.1  Definition  p. 14

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 mobile subscriber busy 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 mobile subscriber busy.

2.2  Description  p. 15

2.2.1  Description  p. 15

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.

2.2.2  Applicability to telecommunication services  p. 15

The applicability of this supplementary service is defined in TS 22.004.

2.2.3  Terminology  p. 15

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.

2.3  Normal procedures with successful outcome  p. 15

2.3.1  Provision  p. 15

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 notification that the call has been forwarded No
Yes
Calling subscriber receives notification that the call has been forwarded No
Yes
MSISDN of the served subscriber can be presented to the forwarded-to subscriber No
Yes
In case of User Determined User Busy (UDUB) a notification towards the forwarding subscriber will not be given.
Up

2.3.2  Withdrawal  p. 15

The service will be withdrawn at the subscriber's request or for administrative reasons.

2.3.3  Registration  p. 15

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.
Registration can take place either by the service provider or with an appropriate control procedure by the subscriber. 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 mobile subscriber busy, 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 mobile subscriber busy is registered.
Up

2.3.4  Erasure  p. 16

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 mobile subscriber busy for the specific Basic service group to another directory number, thus causing the previous registration of call forwarding on mobile subscriber busy to be overridden.
Thirdly, all information is erased as a result of withdrawal of the service.
Up

2.3.5  Activation  p. 16

The user shall be allowed to activate Call Forwarding on Busy (CFB) by e.g. using the MMI command described in 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 CFB for the Basic Service Groups comprised in the BS group information given by the user against which a CFB forwarded-to-number is registered. The Activation(s) shall be in accordance with the rules set out in TS 22.004.
The user shall receive a notification that CFB has been activated.
The supplementary service is also activated for a Basic service group as a result of registration for that Basic service group.
Up

2.3.6  Deactivation  p. 16

An active CFB can be deactivated in either of two ways:
  • The user may deactivate CFB by means of an appropriate control procedure (e.g. as described in 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 CFB for the Basic Service Groups comprised in the BS group information given by the user against which a CFB 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 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 group(s) 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 TS 22.004.
Up

2.3.7  Invocation  p. 17

If the supplementary service is activated for a Basic service incoming calls for the specified Basic service that meet mobile subscriber busy will be forwarded by network invocation.

2.3.8  Normal operation with successful outcome  p. 17

When call forwarding on mobile subscriber busy is active and operative, incoming calls for the specified Basic Service(s) that meet mobile subscriber busy with the condition UDUB (User Determined User Busy) will be forwarded. Incoming calls for the specified basic service(s) that meet mobile subscriber busy with the condition NDUB (Network Determined User Busy) will be forwarded without being offered to the served mobile subscriber.
When an incoming call is forwarded on mobile subscriber busy with the condition NDUB the served mobile subscriber can, as a subscription option, receive notification.
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 mobile subscriber busy 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.
Up

2.3.11  Interrogation  p. 17

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 the served mobile subscriber should be given a list of all Basic service groups to which call forwarding on mobile subscriber busy is registered, including information whether it is active and if so, whether it is operative or quiescent, and the associated forwarded-to numbers;
  • 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 mobile subscriber busy is registered, including information whether it is active and if so, whether it is operative or quiescent for that Basic service group. If CFB is registered, the associated forwarded-to number shall be given.
Up

2.3.12  Charging requirements  p. 17

The forwarding subscriber may be charged for the forwarded part of the call.

2.4  Exceptional procedures or unsuccessful outcome  p. 17

2.4.2  Registration  p. 17

If the system cannot accept a registration request, the served mobile subscriber should receive a notification that call forwarding on mobile subscriber busy 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 groups.
The network is not required to validate information related to the forwarded-to number.
Up

2.4.3  Erasure  p. 18

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 mobile subscriber busy 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.

2.4.4  Activation  p. 18

If there is no CFB forwarded-to-number registered against a Basic Service group, the activation request for that Basic Service group shall be denied.
Examples of causes for a not accepted activation request:
  • service not provisioned;
  • conflicting situation with other supplementary services;
  • service not registered.

2.4.5  Deactivation  p. 18

If the network cannot accept a deactivation request, an appropriate cause will be returned to the user, e.g. Service not Active.

2.4.6  Invocation  p. 18

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 has already been reached, an unsuccessful call set up indication is sent backwards.
If the forwarded call cannot be completed to the forwarded-to destination, then the network will clear the forwarded part of the call and an unsuccessful call set up indication is sent backwards.
Up

2.5  Alternate Procedures  p. 19

None identified.

2.6  Interactions with other supplementary services  p. 19

2.6.8x  -  p. 19

2.6.81.1  Calling line identification presentation  p. 19

See TS 22.081.

2.6.81.2  Calling line identification restriction  p. 19

See TS 22.081.

2.6.81.3  Connected line identification presentation  p. 19

See TS 22.081.

2.6.81.4  Connected line identification restriction  p. 19

See TS 22.081.

2.6.82.1  Call forwarding unconditional  p. 19

See clause 1.6.82.2.

2.6.83.1  Call waiting  p. 19

See TS 22.083.

2.6.84.1  Multi party  p. 19

See TS 22.084.

2.6.85.1  Closed user group  p. 19

See TS 22.085.

2.6.86.1  Advice of charge  p. 19

See TS 22.086.

2.6.88.1  Barring of all outgoing calls  p. 19

Same as the interaction between call forwarding unconditional and barring of all outgoing calls.

2.6.88.2  Barring of outgoing international calls  p. 19

Served mobile subscriber:
  • If barring of outgoing international calls is active, the registration of an international forwarded-to number (from the visited PLMN country) for call forwarding on mobile subscriber busy, as well as the activation of call forwarding on mobile subscriber busy to such a forwarded-to number, is denied. The mobile subscriber shall be informed of this supplementary service incompatibility.
  • If Call forwarding on mobile subscriber busy is active to an international forwarded-to number (from the local PLMN country), activation of Barring of outgoing international calls is denied. The mobile subscriber shall be informed of this supplementary service incompatibility.
  • If Barring of outgoing international calls and Call forwarding on mobile subscriber busy are simultaneously active (i.e. the forwarded-to number is a local number seen from the local PLMN country), Call forwarding on mobile subscriber busy will be made quiescent by the network as soon as the mobile subscriber updates in another PLMN country.
  • If barring of outgoing international calls is subsequently deactivated, or if the mobile subscriber updates in a PLMN where the forwarded-to number is not considered as an international number, call forwarding on mobile subscriber busy is automatically made operative (unless the interaction with another supplementary service requests that it remains quiescent).
Up

2.6.88.4  Barring of outgoing international calls except those directed to the home PLMN country  p. 20

Served mobile subscriber:
  • If Barring of outgoing international calls except those directed to the home PLMN country is active, the registration of an international forwarded-to number (from the local PLMN country) except to the HPLMN country, as well as the activation of call forwarding on mobile subscriber busy to such a forwarded-to number, is denied. The mobile subscriber shall be informed of this supplementary service incompatibility.
  • If Call forwarding on mobile subscriber busy is active to an international forwarded-to number (from the local PLMN country) except to the HPLMN country, activation of Barring of outgoing international calls except those directed to the home PLMN country is denied. The mobile subscriber shall be informed of this supplementary service incompatibility.
  • If Barring of outgoing international calls except those directed to the home PLMN country and Call forwarding on mobile subscriber busy are simultaneously active (i.e. the forwarded-to number is a local number seen from the local PLMN country or a number in the HPLMN country), Call forwarding on mobile subscriber busy will be made quiescent as soon as the mobile subscriber is updated in another PLMN country if the forwarded-to number is not a number in the HPLMN country.
  • If Barring of outgoing international calls except those directed to the home PLMN country is subsequently deactivated, or if the mobile subscriber updates in a PLMN where the forwarded-to number is not barred, Call forwarding on mobile subscriber busy is automatically made operative (unless the interaction with another supplementary service requests that it remains quiescent).
Up

2.6.88.6  Barring of all incoming calls  p. 20

Same as the interaction between call forwarding unconditional and barring of all incoming calls.

2.6.88.7  Barring of incoming calls when roaming outside the home PLMN country  p. 20

Served mobile subscriber:
  • If Barring of incoming calls when roaming outside the home PLMN country is active and operative (i.e. the mobile subscriber is roaming outside the home PLMN country) then the registration and/or activation of Call forwarding on mobile subscriber busy is denied. The mobile subscriber shall be informed of this supplementary service incompatibility.
  • If Barring of incoming calls when roaming outside the home PLMN country is active and quiescent (i.e. the mobile subscriber is in the home PLMN country), then the registration and/or activation of Call forwarding on mobile subscriber busy is not denied.
  • If Barring of incoming calls when roaming outside the home PLMN country becomes operative after Call forwarding on mobile subscriber busy has been registered and/or activated, Call forwarding on mobile subscriber busy is made quiescent.
  • If Barring of incoming calls when roaming outside the home PLMN country subsequently becomes quiescent, Call forwarding on mobile subscriber busy is automatically made operative (unless the interaction with another supplementary service requests that it remains quiescent).
  • If Call forwarding on mobile subscriber busy is active and operative and the mobile subscriber is roaming outside the home PLMN country, activation of Barring of incoming calls when roaming outside the HPLMN country is denied. The mobile subscriber shall be informed of this supplementary service incompatibility.
  • If call forwarding on mobile subscriber busy is active and quiescent and the mobile subscriber is roaming in the home PLMN country, activation of Barring of incoming calls when roaming outside the HPLMN country is not denied.
Forwarded to subscriber: Calls forwarded to a subscriber having Barring of incoming calls when roaming outside the HPLMN country active and operative, will be denied as any other incoming call to that subscriber.
Up

2.6.88.8  Anonymous Call Rejection  p. 21

See TS 22.088.

2.7  Interworking considerations  p. 21

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.
Up

Up   Top   ToC