7 Interactions between optimal routeing and supplementary services

23.0793GPPRelease 17Support of Optimal Routeing (SOR)Technical realizationTS

7.1 Call forwarding

If an optimally routed call encounters early call forwarding, GMSCA attempts to route the call to the forwarded-to destination. The forwarded-to destination is the C subscriber if the C subscriber is not a mobile subscriber, or the HPLMN of the C subscriber if the C subscriber is a mobile subscriber. If GMSCA cannot route the call to the forwarded-to destination without contravening the charging requirements for Support of Optimal Routeing given in clause 9.1, the call is routed to a GMSC in the HPLMN of the B subscriber.

If an optimally routed call encounters late call forwarding, GMSCA attempts to route the call to the forwarded-to destination. The forwarded-to destination is the C subscriber if the C subscriber is not a mobile subscriber, or the HPLMN of the C subscriber if the C subscriber is a mobile subscriber. If GMSCA cannot route the call to the forwarded-to destination without contravening the charging requirements for Support of Optimal Routeing given in clause 9.1, the call is routed from VMSCB to the forwarded-to destination.

The handling of call forwarding at HLRB for optimally routed calls is encapsulated in the procedures First_Forwarding_HLR, PRN_Error_HLR, Handle_CFB, Handle_CFNRc and Handle_CFNRY, which are specified in 3GPP TS 23.018 [6].

7.2 Closed User Group (CUG)

The handling of CUG checking for outgoing calls at VLRA is encapsulated in the process OCH_VLR, which is specified in 3GPP TS 23.018 [6].

The handling of CUG checking at HLRB is encapsulated in the procedures Subscription_Check_HLR and Forward_CUG_Check, which are specified in 3GPP TS 23.018 [6].

7.3 Advice of Charge

Advice of Charge (Information) and Advice of Charge (Charging) do not take account of whether a call has been optimally routed.

7.4 Call barring

It has been accepted in principle that all supplementary service call barring programmes except for BAIC are applied for cost control reasons, and that therefore barring should be applied on the basis of the cost of the actual route taken by the call. For phase 1 of Support of Optimal Routeing, this principle does not apply. Barring of outgoing calls is applied on the basis of the B subscriber number. Barring of all incoming calls will prevent a call to the served mobile subscriber, whether or not the call is optimally routed. If Barring of Incoming Calls when roaming outside the home PLMN country is active and operative it will prevent a call to the B subscriber even if the A subscriber pays to route the call to the VMSC of the B subscriber.

The handling of barring of outgoing calls at VLRA is encapsulated in the process OCH_VLR, which is specified in 3GPP TS 23.018 [6].

The handling of barring of incoming calls at HLRB is encapsulated in the procedure Subscription_Check_HLR, which is specified in 3GPP TS 23.018 [6].

The interactions between barring of outgoing calls and call forwarding for phase 1 of Support of Optimal Routeing are defined in 3GPP TS 22.082 [4].

The interactions between BIC-Roam and call forwarding for phase 1 of Support of Optimal Routeing are defined in 3GPP TS 22.082 [4].

7.5 Other supplementary services

The effects of the following supplementary services on optimally routed calls are identical to their effects on non-optimally routed calls, so they are omitted from the present document:

– CLIP, CLIR, COLP, COLR (3GPP TS 23.081);

– CW, HOLD (3GPP TS 23.083);

– MPTY (3GPP TS 23.084);

– ECT (3GPP TS 23.091).