ccbs training

8/4/2019 CCBS Training

http://slidepdf.com/reader/full/ccbs-training 1/17

1 © NOKIA CCBS service/ 02-02-2005 Company Confidential

CCBS Call Completition to Busy Subscriber




What is CCBS/CCNR?

• CCBS

Subscriber A would like to talk with subscriber B, who is busy at themoment. Subscriber A can register a CCBS request towards subscriber B. The network will establish this call, after subscriber B end the call.

MS -> MS, MS -> PBX, PBX -> MS, PBX -> PBX

• CCNR

Subscriber A would like to talk with subscriber B (fixed ISDN, PBX

extension), who is not reachable at the moment. Subscriber A canregister a CCNR request towards subscriber B. The network will establishthis call, after subscriber B initiates a new call.

PBX -> PBX, PBX->PSTN




CCBS termsWhen subscriber A encounters a Network Determined User Busy(NDUB) destination B, subscriber A can request the CCBS

supplementary service. The network will then monitor the wanteddestination B for becoming idle.

When the wanted destination B becomes idle, then the networkwill wait a short time in order to allow destination B to make anoutgoing call. If destination B does not make a call within this

time, then the network shall automatically recall subscriber A (i.e.inform subscriber A that now the call to destination B is possible).

When subscriber A accepts the recall, the network willautomatically generate a call (i.e. CCBS call) to destination B.

CCBS has to be supported by both the originating and theterminating networks.




CCBS/CCNR interfaces

HLRHLR HLRHLR

MSC/VLRMSC/VLR MSC/VLRMSC/VLR

SSAP

SSAP

MAP

ISUP v2 (CCBS)

ISUP v3 (CCNR)

PBX PBXDSS1 DSS1

A-if A-if

SSAPMAP

SSAP


http://slidepdf.com/reader/full/ccbs-training 5/175 © NOKIA CCBS service/ 02-02-2005 Company Confidential

CCBS Request

HLRHLR HLRHLR

MSC/VLRMSC/VLR MSC/VLRMSC/VLR2. IAM

5. REL (busy, CCBS possible)

3. PAGING

4. PAGING_NACK (busy)

10.Set

Repo

rtingStaste(start)

11.SetRe

po

rtingStasteAck

1. SETUP

7.a RELEASE (Invoke)

6.a DISCONNEC T (#34)

7.b D TMF

6.b CONNECT

14. RELEASE COMPLETE

9. CCBSRequest

12. CCBSRequestAck

8.Reg

isterC

CEntry

13.RegisterCCEntryAck



CCBS Recall

HLRHLR HLRHLR

MSC/VLRMSC/VLR MSC/VLRMSC/VLR

5. PAGING

7.a FACILITY (Recall)

6. PAGING_ACK

7.b SETUP

8.a SETUP

2..StatusReportAck

1.StatusReport(Idle)

8.b DTMF

3. RemoteUserFree

4.Rem

oteU

SerFree

9..Remo

teUserFreeAck



CCBS Call

HLRHLR HLRHLR

MSC/VLRMSC/VLR MSC/VLRMSC/VLR2. IAM

10. ACM/ALERT

1.a SETUP

3. PAGING

4. PAGING _ACK

1.b. DTMF

5..Statu

sRe

port(Succ.)

6..Sta

tusReportAck

13. CONNECT

7. CCBSCancel (CallSucc)

11.StatusRe

port(Reca

llCompl.)

12.Sta

tusR

eportAck

8.SetReportingStaste(S

top)

9.SetRe

portingStasteA

ck



CCBS timersOriginating network T1 [MSC] CCBS retention 15-30 sec

Time that MSC A will wait for subscriber A to activate CCBS when he is informed that B was busy butCCBS is possible.

T3 [HLR] Originating service duration 15-45 min

The maximum time the CCBS request will be kept in the network

T4 [MSC] Recall 20-30 sec

Time that MSC A will wait for subscriber A to accept the recall when he is idle and is informed about Bbecoming idle.

T10 [MSC] Notification 20-30 sec

Time that MSC A will wait for subscriber A to accept the recall when subscriber A is buys when he

received the recall.

T11 [HLR] CCBS resume 20-25 sec

If subscriber A has several suspended requests and they can now be resumed, they are resumed oneat a time, the next one after T11.

Terminating network T7 [HLR] Terminating service duration 45-60 min

The maximum timer the CCBS request will be kept in the network.

T8 [HLR] Destination idle guard 0-15 sec

When HLR B is informed of subscriber B becoming idle, HLR B will wait this time for subscriber B tomake another call or become not reachable before sending recall to HLR A.

T9 [HLR] Recall timer 40-90 sec

After HLR B has sent recall to HLR A, in this time either a suspend message or the CCBS call shouldarrive from the originating network, otherwise the request is cancelled.




SA2PRB

TCAP

TCAP

CCBS service in MSC and HLR

MSC-A

MS-A

FN234

HLR-A

(SSAP)

CTIFIL

W/R

R

CQUEUEMS

C

MAP

FN896

CTIFIL

CQUEUEHLR

W/R

HOSTEL/HORROR

HLR-B

SSAP

MSC/VLR-B

KYTTIS

MAP

BUQMAN

BUDATA

MMX

CZA

CZG

INIF

BCSM

CCBSPR

SCP CON

SIG

CQDHAN

MS-B

(busy subs.)

CQDHAN

CQCONT

CQREQU

SA2PRB

SA2PRB

ICJ-OCJ




Interworking features

• Call Waiting

If waiting call is indicated to the target subscriber, then no CCBS indication isgiven. When UDUB is given to the waiting call, then CCBS is indicated to theoriginating side.

• Call Forwarding

1. Before request – only in case of CFB can CCBS indicated to the originatingside. In this case the CCBS request is registered towards the original B-party.

The forwarding NE should take care of changing CCBS possible to CCBS notpossible.

2. After request – if CFU is activated processing of target queue is stopped. If deactivated then processing continues.

3. After CCBSRecall has been sent – CCBS call is forwarded as a normal call.

• Call Barring

If subscriber B has (ODB-) BAIC, BIRO or BIRZ active and operative for somebasic service groups, new CCBS requests with these basic services cannot be

activated against the subscriber.When CCBS call setup is attempted subscriber A’s outgoing and subscriberB’s incoming barrings prevent the CCBS call and cause the CCBS request inquestion to be deleted.




Interworking features

• Alternate line service

ALS also supported in CCBS. Network and MS should also support ALS.• CLIR/CLIP

CLIR can’t be changed temporarily in CCBS call. Request to each othercan be performed if CLIR is ON.

• Closed user group

The initial call setup information is stored in CCBS request. Thisinformation can be used in the CCBS call setup.

• CAMEL services

If originating CAMEL service performs number translation the original andthe translated number is saved in the CCBS request.

During CCBS call setup the CAMEL service is invoked again and the

original number is translated again. This is compared to the previouslytranslated number. If they do not match, the CCBS call is cleared.




Interfaces

• Operator interface• HLR – MD command group

• MDD - Delete existing requests• MDL – Output subscribers• MDO – Output CCBS request• MDP – Output CCBS parameter values• MDR – Adjust CCBS parameter values

• MSC – MD command group

• MDI – Interrogate CCBS parameter values• MDM – Modify CCBS parameter values• MDS – Set CCBS announcements

• Subscriber interface• CCBS phone• Non-CCBS phone

USSD codes:• *#37# - interrogation of CCBS requests• #37# - deactivation of all CCBS requests




Documentation

• Standards• 3GPP TS 22.093

Completion of Calls to Busy Subscriber (CCBS) - Stage 1

Describes the service from subscriber’s and user’s point of view. Successful operations, exceptional cases, interaction withother SS.

• 3GPP TS 23.093


Detailed description of the service, responsibilities of differentnetwork elements. Specifies protocol and messages.

• 3GPP TS 24.093


Specifies the procedures used at the radio interface (normaloperation, activation, deactivation, etc.)




Questions and answers• How can CCBS be charged?

• CCBS announcements can be chargeable and• CCBS activation and invocation can be chargeable.

CDRs are generated for CCBS request:

SUPS, MOC (with facility_usage field) or UCA

CDRs are generated for CCBS recall:

MTC (with facility_usage field)

CDRs are generated for CCBS call:

SUPS, MOC (with facility_usage field), and so on…

• Can CCBS activation be automatic (i.e. no DTMF confirmation is required bysubscriber)?

It is possible to do. However it wasn’t required so far from our customers,so PDC has to be raised.

• Does CCBS work for roaming subscribers?

Subscribers can have CCBS functionality even when roaming. Both homeand visited network has to support CCBS.




Questions and answers• Are there special CCBS timers?

• 3 timers in MSC/VLR-A• 2 timers in HLR-A• 3 timers in HLR-B

• Maximal CCBS entries/subscriber?

A subscriber can have 1..5 requests as an originating subscriber and

he can be target of 1..5 CCBS request.

• Is CCBS started for Not Reachable, No Reply, NDUB or UDUB?CCBS is started for B-busy cases. UDUB/NDUB can be set on VLR basis.

• Activation and deactivation for subscribers

CCBS request can be activated by DTMF confirmation (pressing 5).

CCBS recall acceptance is can be automatic (after a notificationannouncement) or by DTMF confirmation (pressing 5).

USSD interrogation of all originating CCBS requests: *#37#

USSD deactivation of all originating CCBS requests: #37#




Questions and answers

• Subscriber based settings:• Both originating and terminating CCBS Supplementary Services

can be provisioned to single and multiple subscribers

• System based settings:• CCBS can be turned ON/OFF in MSC/VLR and in HLR• CCBS can be included in the list of not supported

Supplementary Services• Announcements• Timers• Handling of CCBS mobiles• Size of originating and terminating CCBS queue• Circuit group and outgoing route support for CCBS




Questions and answers

• How long time setup takes, what does the subscriber hear?

After accepted recall everything works as it should for “normalcalls”, call setup takes as much time as usual.

The following announcements are for CCBS functionality:• CCBS request notification• CCBS request confirmation• CCBS request rejection

• CCBS recall notification

• Capacity considerations

CCBS database is able to store CCBS requests for the 2% of themaximum number of subscribers in the HLR.

• Subrack – 1 request / 6000 subscribers• Cartridge – 1 request / 24.000 subscribers

ccbs training

Documents