7 Interaction with other supplementary services

22.0933GPPCompletion of Calls to Busy Subscriber (CCBS)Release 17Service description, Stage 1TS

7.1 Calling line identification presentation

No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.

7.2 Calling line identification restriction

CLIR information from the original call, stored in the network, shall also be automatically included in the CCBS call.

7.3 Connected line identification presentation

No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.

7.4 Connected line identification restriction

No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.

7.5 Call Forwarding Unconditional (CFU)

CCBS recalls shall never be forwarded.

If subscriber A places a call to destination B and the call is forwarded to user C by the CFU supplementary service and user C is busy, then subscriber A shall not receive any CCBS possible indication.

If destination B activates the CFU supplementary service after subscriber A has activated a CCBS request, then all the CCBS requests related to the relevant Basic Service Group shall be excluded from the destination B network’s queue processing until the CFU supplementary service becomes deactive or quiescent or until the CCBS duration timers (T3 or T7) expire.

If destination B activates the CFU supplementary service for the relevant Basic Service Group between the expiry of the destination B idle guard timer and the arrival of the CCBS call, the CCBS call shall be forwarded as a normal call.

If the destination network B receives a CCBS request from the originating A network while the CFU supplementary is active and operative for the relevant Basic Service Group, then the CCBS request shall be rejected with an indication of short term denial.

7.6 Call Forwarding on mobile subscriber Busy (CFB)

CCBS recalls shall never be forwarded.

If subscriber A places a call to destination B and the call is forwarded to user C by the CFB supplementary service and user C is busy, then any subsequent attempt to activate a CCBS request by subscriber A against destination B will be accepted.

If destination B activates the CFB supplementary service after subscriber A has activated a CCBS request, then the processing of destination B’s CCBS queue shall be continued.

If destination B which has activated the CFB supplementary service is busy upon arrival of a CCBS call two network provider options exist with regard to the treatment of that CCBS call, i.e.:

– the CCBS call shall be treated according to the exceptional procedures (destination B again busy); or

– the CCBS call shall be forwarded as a normal call.

7.7 Call Forwarding on No Reply (CFNRy)

CCBS recalls shall never be forwarded.

If subscriber A places a call to destination B and the call is forwarded to user C by the CFNRy supplementary service and user C is busy, then subscriber A shall not receive any CCBS possible indication.

If destination B activates the CFNRy supplementary service after subscriber A has activated a CCBS request, then the processing of destination B’s CCBS queue shall be continued.

If destination B activates the call forwarding no reply supplementary service after subscriber A has activated a CCBS requestagainst destination B, then the CCBS call shall be given to destination B at the user’s original location. After the no reply timer has expired at destination B the CCBS call shall be forwarded as a normal call.

7.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc)

CCBS recalls shall never be forwarded.

If subscriber A places a call to destination B and the call is forwarded to user C by the CFNRc supplementary service and user C is busy, then subscriber A shall not receive any CCBS possible indication.

If destination B activates the CFNRc supplementary service after subscriber A has activated a CCBS request, then the processing of destination B’s queue shall be continued.

If destination B activates the CFNRc supplementary service after subscriber A has activated a CCBS request against destination B and destination B is not reachable upon the arrival of CCBS call then the CCBS call shall be forwarded as a normal call.

7.9 Call waiting

If subscriber A has subscribed to the CCBS supplementary service and places a normal call to a destination B that has subscribed to the call waiting supplementary service, and the call waiting indication is given to destination B (i.e. the call is waiting), a subsequent CCBS request activation by subscriber A shall not be allowed.

If the call waiting indication cannot be given at the destination B, subscriber A will receive busy indication and can activate a CCBS request against destination B.

CCBS requests in the destination B CCBS queue shall only be processed if destination B is idle.

A CCBS call shall be treated as a normal call with respect to call waiting, at subscriber B.

7.10 Call hold

No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.

7.11 Multiparty services

No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.

7.12 Closed user group

Closed user group information from the original call, stored in the network, shall also be automatically included in the CCBS call.

If subscriber A or destination B roam to a network not supporting CUG the call restriction procedures as described in TS 22.085 [4] shall apply after a CCBS request has been activated.

7.13 Advice of charge services

No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.

If subscriber A has subscribed to Advice of Charge Charging (AoCC) and if ACMmax is reached, or exceeded, and subscriber A is awaiting a CCBS recall notification, then the ME shall be informed of the CCBS recall. Subscriber A shall not be informed of the CCBS recall. The ME shall reject the CCBS recall which shall stop T4 or T10 and the corresponding CCBS request shall be deactivated. Any outstanding CCBS request shall remain in subscriber A’s CCBS queue until the CCBS service duration timer (T3 or T7) expires.

7.14 Barring of All Outgoing Calls (BAOC)

If the BAOC supplementary service becomes active and operative for subscriber A after subscriber A has activated a CCBS request, and subscriber A accepts the CCBS Recall, the CCBS call will be barred and the CCBS Request shall be automatically deactivated.

7.15 Barring of Outgoing International Calls (BOIC)

If the BOIC supplementary service becomes active and operative for subscriber A after subscriber A has activated a CCBS request, and subscriber A accepts the CCBS Recall, the CCBS call will be barred if it is an international call and the CCBS Request shall be automatically deactivated.

7.16 Barring of Outgoing International Calls except those directed to the Home PLMN Country (BOIC-exHC)

If the BOIC-exHC supplementary service becomes active and operative for subscriber A after subscriber A has activated a CCBS request, and subscriber A accepts the CCBS Recall, the CCBS call will be barred if it is an international call except to the HPLMN country and the CCBS Request shall be automatically deactivated.

7.17 Barring of All Incoming Calls (BAIC)

If destination B activates the BAIC supplementary service after subscriber A has activated a CCBS request, then all the CCBS requests related to the relevant Basic Service Group shall be excluded from the destination B network’s queue processing until the BAIC supplementary service becomes deactive or until the CCBS duration timers (T3 or T7) expire.

If the BAIC supplementary service is active and operative for the relevant Basic Service Group when the HPLMN B receives an interrogation to route the CCBS call, then the specific CCBS request relating to that CCBS call shall be automatically deactivated.

If the destination network B receives a CCBS request from the originating A network while the BAIC supplementary service is active and operative for the relevant Basic Service Group, then the CCBS request shall be rejected with an indication of short term denial.

7.18 Barring of Incoming Calls when roaming outside the home PLMN country (BIC-Roam)

If destination B activates the BIC-Roam supplementary service after subscriber A has activated a CCBS request, then all the CCBS requests related to the relevant Basic Service Group shall be excluded from the destination B network’s queue processing until the BAIC supplementary service becomes deactive or quiescent or until the CCBS duration timers (T3 or T7) expire.

If the BIC-Roam supplementary service becomes active and operative for the relevant Basic Service Group when the HPLMN B receives an interrogation to route the CCBS call, then the specific CCBS request relating to that CCBS call shall be automatically deactivated.

If the destination network B receives a CCBS request from the originating A network while the BIC-Roam supplementary service is active and operative for the relevant Basic Service Group, then the CCBS request shall be rejected with an indication of short term denial.

7.19 Explicit call transfer

No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.

7.20 Completion of calls to busy subscriber

No impact.

A subscriber can be both a "subscriber A" and a "destination B" simultaneously, i.e. the same subscriber can be both the originator and the target of one or more CCBS requests.

If the subscriber receives a CCBS call while that subscriber is being alerted or is awaiting completion of the CCBS call for which the subscribers is the originator, then the received CCBS call shall be treated as if the subscriber was busy again.

7.21 Customised Applications for Mobile network Enhanced Logic (CAMEL)

The CCBS call shall be treated as normal originating call for the purpose of CAMEL based originating services.

If a mobile originating CAMEL based service determines for a CCBS call different called party address than for the initial call, the CCBS call shall be released by the network and the corresponding CCBS request shall be automatically deactivated.

There will be no interaction in case of the called party address is not changed by any CAMEL based terminating service.

In case of a terminating CAMEL based service changing the called party address, then a CCBS request activation shall not be allowed.

At Interrogation the network shall return the same B subscriber address as subscriber A has entered at the time of CCBS request activation.

If the CSE (CAMEL Service Environment) requests a call set-up to an alternative destination after the original call set-up to destination B has encountered a busy condition and this call meets a busy destination, then any subsequent attempt to activate a CCBS request by subscriber A against destination B (the original called party) will be accepted.

If the CSE (CAMEL Service Environment) requests a call set-up to an alternative destination after the original call set-up has failed for other reasons than the busy condition of destination B or was disconnected and this call meets a busy destination, then subscriber A shall not receive any CCBS possible indication..

7.22 Support of Private Numbering Plan (SPNP)

A CCBS call shall always be directed to the party originally addressed, regardless of any changes in the B party number after activation of a CCBS request.

At Interrogation, the network shall return the same B subscriber address as subscriber A has entered at the time of the original call.