3G TS 23.093 V3.0 - 株式会社QT ·  · 1999-09-085.6.4 Messages between VLR and HLR (D-in...

165
3G TS 23.093 V3.0.0 (1999-05) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network; Technical realization of Completion of Calls to Busy Subscriber (CCBS) - Stage 2 (3G TS 23.093 version 3.0.0) The present document has been developed within the 3 rd Generation Partnership Project (3GPP TM ) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners' Publications Offices.

Transcript of 3G TS 23.093 V3.0 - 株式会社QT ·  · 1999-09-085.6.4 Messages between VLR and HLR (D-in...

3G TS 23.093 V3.0.0 (1999-05)Technical Specification

3rd Generation Partnership Project;Technical Specification Group Core Network;

Technical realization ofCompletion of Calls to Busy Subscriber (CCBS) - Stage 2

(3G TS 23.093 version 3.0.0)

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposesof 3GPP.The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of thisSpecification.Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners' PublicationsOffices.

3GPP

3G TS 23.093 V3.0.0 (1999-05)23G TS 23.093 version 3.0.0

ReferenceDTS/TSGN-0023093U

Keywords3GPP, CN

3GPP

Postal address

3GPP support office address650 Route des Lucioles - Sophia Antipolis

Valbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Internethttp://www.3gpp.org

3GPP

3G TS 23.093 V3.0.0 (1999-05)33G TS 23.093 version 3.0.0

Contents

Foreword ................................................................................................................................................5

1 Scope ............................................................................................................................................6

2 Normative references.....................................................................................................................6

3 Definitions and abbreviations ...........................................................................................................73.1 Definitions............................................................................................................................................................................. 73.2 Abbreviations....................................................................................................................................................................... 7

4 General..........................................................................................................................................74.1 Overview............................................................................................................................................................................... 74.2 Architecture .......................................................................................................................................................................... 74.2.1 Architectural overview during roaming ..................................................................................................................... 8

5 Handling of completion of calls to busy subscriber ............................................................................95.1 CCBS Timers ......................................................................................................................................................................... 95.2 Information flows ............................................................................................................................................................... 105.3 Activation ........................................................................................................................................................................... 145.4 Deactivation........................................................................................................................................................................ 155.5 Interrogation....................................................................................................................................................................... 165.6 Messages and their contents ........................................................................................................................................... 175.6.1 Information elements used in the messages............................................................................................................ 175.6.1.1 Call Information information element ................................................................................................................. 175.6.1.2 AddressOfB information element ....................................................................................................................... 175.6.1.3 CCBS Description information element.............................................................................................................. 175.6.2 Messages between MS and MSC............................................................................................................................. 185.6.3 Messages between MSC and VLR (B-interface).................................................................................................... 195.6.3.1 Messages between MSC and VLR in the originating network ...................................................................... 195.6.3.2 Messages between MSC and VLR in the destination network...................................................................... 215.6.4 Messages between VLR and HLR (D-interface)..................................................................................................... 225.6.4.1 Messages between VLR and HLR in the originating network ....................................................................... 225.6.4.2 Messages between VLR and HLR in the destination network....................................................................... 265.6.5 Messages between MSC and HLR (C-interface).................................................................................................... 275.6.6 Messages between MSC - MSC (E-interface)......................................................................................................... 275.6.7 Existing parameters containing CCBS specific information .................................................................................. 27

6 Monitoring and CCBS Call Reporting.............................................................................................286.1 Monitoring.......................................................................................................................................................................... 286.1.1 Overview....................................................................................................................................................................... 286.1.2 Monitoring Subscriber B-state information............................................................................................................. 286.1.3 Monitoring Subscriber A state information:........................................................................................................... 286.2 MSC/VLR Monitoring Model.......................................................................................................................................... 296.2.1 Subscriber status ......................................................................................................................................................... 296.2.1.1 Idle ........................................................................................................................................................................... 306.2.1.2 Not Idle ................................................................................................................................................................... 306.2.1.3 Not Reachable........................................................................................................................................................ 306.2.2 Reporting of subscriber state transit ions ................................................................................................................ 316.2.2.1 Start Reporting of Monitoring Events ............................................................................................................... 316.2.2.2 Stop Reporting of Monitoring Events ............................................................................................................... 316.3 CCBS Call Reporting.......................................................................................................................................................... 326.3.1 Overview....................................................................................................................................................................... 326.3.2 Originating Network (A-side).................................................................................................................................... 326.3.3 Destination Network (B-side).................................................................................................................................... 326.3.3.1 Interaction of Event Reporting and CCBS Call Report .................................................................................... 326.4 Location Update................................................................................................................................................................. 32

3GPP

3G TS 23.093 V3.0.0 (1999-05)43G TS 23.093 version 3.0.0

7 Mobility .......................................................................................................................................337.1 Mobility during Activation .............................................................................................................................................. 337.2 Number used within CCBS Call........................................................................................................................................ 337.3 MS does Location Update................................................................................................................................................ 337.4 Mobility during CCBS Call in the destination network................................................................................................ 33

8 Interaction with other supplementary services ................................................................................348.1 Call forwarding unconditional (CFU).............................................................................................................................. 348.2 Call forward on busy (CFB).............................................................................................................................................. 348.3 Call forwarding on no reply (CFNRy)............................................................................................................................. 348.4 Call forwarding on MS not reachable (CFNRc)............................................................................................................. 348.5 Call Waiting (CW).............................................................................................................................................................. 358.6 Multiparty service (MPTY) .............................................................................................................................................. 358.7 Closed user group (CUG).................................................................................................................................................. 358.8 Advice Of Charge (AoC) .................................................................................................................................................. 358.9 Barring of all outgoing calls (BAOC).............................................................................................................................. 358.10 Barring of outgoing international calls (BOIC).............................................................................................................. 358.11 Barring of outgoing international calls except those directed to the home PLMN country (BOIC-exHC)........... 358.12 Barring of all incoming calls (BAIC)................................................................................................................................ 358.13 Barring of incoming calls when roaming outside the home PLMN country (BIC-Roam) ....................................... 368.14 Completion of calls to busy subscriber (CCBS)............................................................................................................ 36

9 Interaction with other network features..........................................................................................379.1 Customised Applications for Mobile network Enhanced Logic (CAMEL) .............................................................. 379.2 Support of Optimal Routeing (SOR)................................................................................................................................ 37

10 Interworking with other networks ..................................................................................................3810.1 Interworking with network entities not supporting CCBS........................................................................................... 3810.1.1 CCBS not supported by MSC A ............................................................................................................................... 3810.1.2 CCBS not supported by HLR B................................................................................................................................. 3810.1.3 CCBS not supported by MSC B................................................................................................................................ 39

11 Network entity functions ...............................................................................................................4011.1 Originating Network Processes ....................................................................................................................................... 4011.1.1 Processes and procedures in MSC/VLR.................................................................................................................. 4011.1.2 Processes and procedures in HLR............................................................................................................................ 6211.2 Destination Network Processes....................................................................................................................................... 9211.2.1 Procedures in GMSC................................................................................................................................................... 9211.2.2 Processes and procedures in HLR............................................................................................................................ 9811.2.3 Procedures in MSC/VLR........................................................................................................................................... 12811.3 Processes and procedures common in originating and destination network entities ........................................... 140

12 Information stored in the HLRs ................................................................................................... 15612.1 Originating Network Data............................................................................................................................................... 15612.2 Destination Network Data .............................................................................................................................................. 15712.3 Transfer of information from HLR to VLR.................................................................................................................... 157

13 State transition model.................................................................................................................. 15813.1 State transition model for the CCBS service in the originating network ................................................................. 15813.2 State transition model for the CCBS service in the destination network................................................................. 15813.3 State transition model for a CCBS Request.................................................................................................................. 15913.4 Information stored in the VLRs ...................................................................................................................................... 160

Annex A (Informative): Message flow diagrams showing a successful CCBS request........... 161

Annex A: Change history ......................................................................................................... 164

History................................................................................................................................................ 165

3GPP

3G TS 23.093 V3.0.0 (1999-05)53G TS 23.093 version 3.0.0

ForewordThis Technical Specification has been produced by the 3GPP.

This specification gives the stage 2 description of the Completion of Calls to Busy Subscriber (CCBS) supplementaryservice within the 3GPP system.

The contents of the present document are subject to continuing work within the TSG and may change following formalTSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifyingchange of release date and an increase in version number as follows:

Version 3.y.z

where:

x the first digit:

1 presented to TSG for information;

2 presented to TSG for approval;

3 Indicates TSG approved document under change control.

y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,updates, etc.

z the third digit is incremented when editorial only changes have been incorporated in the specification;

3GPP

3G TS 23.093 V3.0.0 (1999-05)63G TS 23.093 version 3.0.0

1 ScopeThis Technical Specification gives the stage 2 description of the Completion of Calls to Busy Subscriber (CCBS)supplementary service.

2 Normative referencesReferences may be made to:

a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in whichcase, subsequent revisions to the referenced document do not apply; or

b) all versions up to and including the identified version (identified by "up to and including" before the versionidentity); or

c) all versions subsequent to and including the identified version (identified by "onwards" following the versionidentity); or

d) publications without mention of a specific version, in which case the latest version applies.

A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.

[1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".

[2] GSM 02.30: "Digital cellular telecommunications system (Phase 2+); Man Machine Interface (MMI)of the Mobile Station (MS)".

[3] GSM 02.93: " Digital cellular telecommunications system (Phase 2+); Completion of calls to busysubscriber (CCBS) supplementary services - Stage 1".

[4] GSM 03.11: "Digital cellular telecommunications system (Phase 2+); Technical realization ofsupplementary services".

[5] GSM 03.18: "Digital cellular telecommunications system (Phase 2+); Basic Call Handling - TechnicalRealization".

[6] GSM 03.78: "Digital cellular telecommunications system (Phase 2+); Customised Applications forMobile network Enhanced Logic (CAMEL) - Stage 2".

[7] GSM 03.79: "Digital cellular telecommunications system (Phase 2+); Support for Optimal Routeing(SOR) - Technical Realization".

[8] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3specification".

[9] GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP)specification".

[10] ETS 300 358: "ISDN Completion of Calls to Busy Subscriber (CCBS) supplementary service;Functional capabilities and information flows".

3GPP

3G TS 23.093 V3.0.0 (1999-05)73G TS 23.093 version 3.0.0

3 Definitions and abbreviations

3.1 DefinitionsDestination B: The entity addressed in the original call set up, which is busy when first called by subscriber A. Similarly,MSC B, VLR B and HLR B are the network elements pertaining to Destination B when Destination B is a GSM mobile.

Originating queue: The queue that manages CCBS requests for a subscriber, when that subscriber is the originator ofthose CCBS Requests.

SSAP: Supplementary Service Application Part. SSAP is the protocol used for CCBS procedures on the interfacebetween the originating and destination network. Communication across this interface is performed using SCCPConnectionless Signalling (Refer to ETS 300 358).

Subscriber A: The user of MS A, requesting CCBS. Similarly, MSC A, VLR A and HLR A are the network elementspertaining to Subscriber A.

Subscriber B: The user of destination B, who may not necessarily subscribe to CCBS.

Subscriber C: The user of MS C, who is the forwarded-to-party when call forwarding applies. Similarly, MSC C, VLR Cand HLR C are the network elements pertaining to Subscriber C.

Target queue: The queue that manages CCBS requests for a subscriber, when that subscriber is the target of CCBSRequests.

Timers: For each of the service timers, the location, start and stop conditions and action on expiry are given - Refer tosubclause 5.1.

3.2 AbbreviationsAbbreviations used in this specification are listed in GSM 01.04.

4 General

4.1 OverviewThe CCBS service allows a calling subscriber A, encountering a NDUB destination B, to be notified when destination Bbecomes idle and to have the network automatically generate a CCBS call to destination B, if subscriber A desires.Subscriber A may make distinct CCBS requests for calls to the same destination B for different basic services.

4.2 ArchitectureFigure 4.2.1 is an architectural overview of the CCBS service when interworking between the originating and thedestination networks involved. The originating network may be a mobile network or a fixed network and the destinationnetwork may also be a mobile network or a fixed network.

The call related signalling for CCBS is performed on ISUP links on the following interfaces:

VMSC A - GMSC B;

VMSC A - DLE;

OLE - GMSC B;

whereas the specific CCBS procedures are performed via the SSAP protocol, which is signalled on the followinginterfaces:

3GPP

3G TS 23.093 V3.0.0 (1999-05)83G TS 23.093 version 3.0.0

HLR A - HLR B;

HLR A - DLE;

OLE - HLR B.

ISUP

ISUP ISUP

ISUP

SSAP

SSAP

SSAP

SSAPOLE

VMSC A

VLR A

HLR A

GMSC B

DLE

VMSC B

VLR B

HLR B

ISUP

TRANSITNETWORK(S)

Originating Network Destination Network

FixedNetwork

FixedNetwork

MobileNetwork

MobileNetwork

MAP

Figure 4.2.1: Architectural overview showing common point of interworking

4.2.1 Architectural overview during roaming

Either the originating subscriber A or the destination subscriber B or both may be located outside of their HPLMNsduring the CCBS service. When all the involved networks support CCBS service the normal handling described in thisspecification applies. When some network entities do not support CCBS service refer to clause 10 where the exceptionsare described in more detail.

The signalling between different networks described in the subclause 4.2 applies also during roaming. HLR A and HLR Bbelongs always to the HPLMN of the subscriber whereas VLR A and MSC A and GMSC, VLR B and MSC B respectivelymay belong to a HPLMN or VPLMN. Refer to GSM 03.18 where call handling in the mobile network is described in moredetail.

3GPP

3G TS 23.093 V3.0.0 (1999-05)93G TS 23.093 version 3.0.0

5 Handling of completion of calls to busy subscriberRegistration and erasure of CCBS are not applicable. Activation and Invocation of CCBS are intrinsic parts of theoperation of the service, and are described in this section.

5.1 CCBS TimersThe timers used to control the operation of CCBS can be considered to consist of two groups i.e. the timers whichoperate on a per subscriber basis (see table 1) and the service duration timers (T3 and T7) which operate on a per CCBSRequest basis (see table 2).

Table 1: CCBS Service Timers

Timer Name Value Run At Started Stopped Expiry

T1 Retention >15s MSC A Busy (CCBS Possible)sent to MS A

CCBS Request receivedfrom MS A

Discard retainedinformation

T4 Recall 20-30s MSC A CCBS Recall sent toMS A and MS A is idle

Subscriber A initiatesCCBS setup or rejectsCCBS Recall

Cancel request

T8 Destinationidle guard

0-15s HLR B Event Report receivedfrom VLR B indicatingdestination B is idle

Event Report receivedfrom VLR B indicatingdestination B is nolonger idle

Inform originatingnetwork thatDestination B isfree

T9 Recall B 40-55s HLR B Remote User Free sentto the A-side

Request cancelled,completed or suspended

Cancel request

T10 CCBSnotification

20-30s MSC A CCBS Recall sent toMS A and MS A is not idle

Subscriber A initiatesCCBS setup, rejectsCCBS Recall or requestssuspension

Suspend request

T11 CCBS resume 20-25s HLR A HLR A receives aresume request andthere are more than onesuspended request insubscriber A’s queue

Remote User Freereceived from destinationnetwork

Resume nextsuspendedrequest in queue

T12 CCBS CallGuard

20-30s HLRA HLRA receives a CCBSRUF Ack and starts towait CCBS Call Report

CCBS Call Reportreceived

Cancel request

Table 2: Service Duration Timers

Timer Name Value Run At Started Stopped Expiry

T3 Originatingserviceduration

15-45m HLR A Acknowledgement toCCBS Requestreceived fromdestination network

Request cancelled orcompleted

Cancel request

T7 Terminatingserviceduration

>45m HLR B HLR B acknowledgessuccessful activation ofa CCBS Request

Request cancelled orcompleted

Cancel request

3GPP

3G TS 23.093 V3.0.0 (1999-05)103G TS 23.093 version 3.0.0

5.2 Information flowsFigures 5.2.1 and 5.2.2 show the flow of information between network elements for a mobile to mobile call for thefollowing:

Figure 5.2.1: Successful CCBS request, destination B busy when request made, subscriber A free when destination Bbecomes free.

Figure 5.2.2: Subscriber A is not idle when destination B becomes free.

Figures 5.2.3 and 5.2.4 show the flow of information between network elements for a mobile to fixed call for the samesituations described in figures 5.2.1 and 5.2.2 respectively.

Each information flow diagram has been divided where appropriate into four distinct phases of operation. These are asfollows:

(1) Pre-conditions (Initial Call encountering NDUB and CCBS possible in the destination network). The detaileddescription of the basic call handling can be found in GSM 03.18;

(2) Activation;

(3) Invocation;

(4) Operation (CCBS Call Set-up).

3GPP

3G TS 23.093 V3.0.0 (1999-05)113G TS 23.093 version 3.0.0

Start ReportingAck

MS (A) MSC/VLR (A) HLR (A) GMSC HLR (B) MSC (B)

Set-upIAM

Info ReqPRN

MSRNInfo Req Ack

IAM

RELEASE (Busy, CCBS Possible)RELEASE (Busy, CCBS Possible)

CCBS Poss

CCBS RequestCCBS Request

CCBS Request

CCBS Request Ack

CCBS Request

AckCCBS Request Ack

Start Reporting

Event Report

(Idle & Reachable)Remote User Free

CCBS RUF

CCBS Recall

CCBS Set-up

IAM (CCBS Call)Info Req

(CCBS Call)

PRN(CCBS Call)

PRN AckInfo Req Ack

IAM (CCBS Call)

ACM/ANM/CPGACM/ANM/CPG

Alert/Connect

TC-END

CCBSCall ReportCCBS Call

Report(Success)

T1:

:T1

T3 T7:

:

T9

:

:

:

:

:

:

:

T7

:

:

:

:

:

:

:

:

:

T3

:

T4:

:

:T4

Release

T8

T8:

:

T9

Set-up

Stop Reporting

:

:

1

2

3

4

CCBS RUF Ack:

:

CCBS Call Info

CCBS Call Info Ack

Figure 5.2.1: Successful CCBS request. Destination B busy when request activated, subscriber A freewhen destination B becomes free (mobile-to-mobile)

3GPP

3G TS 23.093 V3.0.0 (1999-05)123G TS 23.093 version 3.0.0

Start ReportingAck

Start ReportingAck

MS (A) MSC/VLR (A) HLR (A) GMSC HLR (B) MSC (B)

Set-upIAM

Info ReqPRN

MSRNInfo Req Ack

IAM

RELEASE (Busy, CCBS Possible)RELEASE (Busy, CCBS Possible)

CCBS Poss

CCBS RequestCCBS Request

CCBS Request

CCBS Request Ack

CCBS Request

AckCCBS Request

Ack

Start Reporting

Event Report

(Idle & Reachable)Remote User FreeCCBS RUF

CCBS Recall

T1:

:T1

T3 T7:

:

T9

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

Release

T8

:

:

T8

T10

CCBS RUF AckT10 Expires

CCBS SuspendT9

Note: T3 & T7 are not stopped

MS (A) becomes

idleEvent Report(Idle & Reach) CCBS Resume

:

::

Note 1 : Stop Reporting is sent if there are only suspended requests in the queue

1

2

3

Stop Reporting

Start Reporting

(Note 1)

(Note 2)

Note 2 : Start Reporting is sent if MSC B is not monitoring destination B

Start Reporting Ack

Start Reporting

CCBS Call Info

CCBS Call Info Ack

Figure 5.2.2: Subscriber A not idle when destination B becomes free (mobile-to-mobile);Processing of a single request

3GPP

3G TS 23.093 V3.0.0 (1999-05)133G TS 23.093 version 3.0.0

CCBS RUFAck

CCBS RUF

MS (A) MSC/VLR (A) HLR (A) DLE (B)

Set-upIAM

RELEASE (Busy, CCBS Possible)

CCBS Poss

CCBS Request

CCBS RequestCCBS Request

CCBS Request Ack

CCBS RequestAck

CCBS Request Ack Remote User Free

CCBS Recall

T1:

:T1

T3

:

:

Release

T4

:

::

:::

::

::

CCBS Set-up

IAM (CCBS Call)

ACM/ANM/CPG

TC-ENDCCBS CallReport (success)

T3

T4

2

1

3

4

:::

Alert/Connect

CCBS Call Info

CCBS Call Info Ack

Figure 5.2.3: Successful CCBS request. Destination B busy when request activated, subscriber A freewhen destination B becomes free (mobile-to-fixed)

3GPP

3G TS 23.093 V3.0.0 (1999-05)143G TS 23.093 version 3.0.0

Start ReportingAck

Start Reporting

MS (A) MSC/VLR (A) HLR (A) DLE (B)

Set-upIAM

RELEASE (Busy, CCBS Possible)

CCBS Poss

CCBS Request

CCBS RequestCCBS Request

CCBS Request Ack

CCBS Request

Ack

CCBS Request Ack Remote User Free

CCBS RUF

CCBS Recall

T1:

:T1

T3

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

Release

T10

T10 ExpiresCCBS Suspend

Note: T3 & T7 are not stopped

MS (A) becomes

idle Event Report(Idle&Reach)

CCBS Resume

::

1

2

3

CCBS RUF Ack

CCBS Call Info

CCBS Call Info Ack

Figure 5.2.4: Subscriber A not idle when destination B becomes free (mobile-to-fixed)

5.3 ActivationActivation of a CCBS Request is carried out by subscriber A. VLR A is considered to be transparent during theactivation operation.

The information flows shown in figures 5.2.1 to 5.2.4 inclusive show the information flow for the activation process.

3GPP

3G TS 23.093 V3.0.0 (1999-05)153G TS 23.093 version 3.0.0

5.4 DeactivationSubscriber A may deactivate CCBS in any of the following ways:

- Deactivate all outstanding CCBS requests; or

- Deactivate a specific CCBS Request.

The different deactivation operations are identified by different MMI commands as specified in GSM 02.30.

Deactivation of CCBS requests by subscriber A shall be performed at HLR A.

To deactivate all outstanding CCBS requests, the Deactivate CCBS operation request shall contain the SS-Code only.

To deactivate a specific CCBS request, the Deactivate CCBS operation request shall contain the following parameters:

- SS-Code;

- CCBS Index.

On receipt of the deactivation request, HLR A shall cancel the CCBS request, i.e. remove all record of a CCBS requestfrom the subscriber A’s originating CCBS queue and instruct the destination B network to cancel the correspondingCCBS request in the destination CCBS queue of subscriber B. HLR A shall return a result indicating whether thedeactivation attempt was successful or not.

MS A MSC A VLR A HLR A Destination BNetwork

Deactivate CCBS

------------------->

Deactivate CCBS

--------------------->

Deactivate CCBS

------------------->

CCBS Cancel

------------------->

(note)

Acknowledge

<-------------------

Acknowledge

<--------------------

Acknowledge

<---------------------

3GPP

3G TS 23.093 V3.0.0 (1999-05)163G TS 23.093 version 3.0.0

NOTE: CCBS Cancel shall be sent for each CCBS Request that is cancelled in HLR A.

Figure 5.4.1: Successful deactivation of all CCBS Requests/a specific CCBS request

NOTE: In the case where a subscriber attempts to perform a deactivation operation but the subscriber is notprovisioned with the CCBS service then, the subscriber shall receive an indication that the CCBS service isnot provisioned for him.

5.5 InterrogationInterrogation of CCBS shall be carried by request to HLR A. HLR A then returns the required information or error toMS A, see figure 5.5.1. MSC A and VLR A are considered to be transparent during the interrogation operation.

MS A MSC A VLR A HLR A

Interrogate CCBS

------------------------------>

Interrogate CCBS

----------------------------->

Interrogate CCBS

------------------------------->

Acknowledge

<-------------------------------

Acknowledge

<-----------------------------

Acknowledge

<--------------------------------

Figure 5.5.1: General interrogation of completion of calls to busy subscriber

The Interrogate CCBS operation request shall contain the SS-Code only.

In response to a general interrogation, MS A shall be given the AddressOfB, BasicServiceCode and CCBS index for eachCCBS Request in the queue. The entries shall be ordered in the chronological order, the oldest entry shall be presentedfirst.

If there are no CCBS Requests in the queue, MS A shall be given an indication that no entries exist in the queue.

NOTE: In the case where a subscriber attempts to perform an interrogation operation but the subscriber is notprovisioned with the CCBS service then, the subscriber shall receive an indication that the CCBS service isnot provisioned for him.

3GPP

3G TS 23.093 V3.0.0 (1999-05)173G TS 23.093 version 3.0.0

5.6 Messages and their contentsThis clause contains the detailed description of the information flows used by CCBS.

Each Information Element, IE is marked as (M) Mandatory, (C) Conditional or (O) Optional. A mandatory informationelement shall always be present. A conditional information shall be present if certain conditions are fulfilled; if thoseconditions are not fulfilled it shall be absent. An optional information element may be present or absent, at the discretionof the application at the sending entity. This categorisation is a functional classification, i.e., stage 2 information and nota stage 3 classifications to be used for the protocol.

The stage 2 and stage 3 message and information element names are not necessarily identical.

5.6.1 Information elements used in the messages

In this clause constructed information elements are described.

5.6.1.1 Call Information information element

Call Information information element is formed in the MSC A during the CCBS activation. This information elementcontains unmodified copy of the SETUP message received from the MS A. If CCBS Request is activated, the CallInformation is stored in the HLR A. During CCBS Recall Call Information is relayed back to the MS. Refer to SETUPContainer information element defined in GSM 04.08.

5.6.1.2 AddressOfB information element

AddressOfB information element is formed in the MSC A during the CCBS activation. It contains the number of thedestination B dialled by the A-user.

Table 5.6.1.2: Structure of AddressOfB information element

ParentInformation

Element

Child Informationelement name

Information elementRequired

Information element description

AddressOfB B subscriber number,B subscriber subaddress

MC

The number of the destination B dialled by the A-user;Shall be present if it was dialled by the A-user;otherwise shall be absent

5.6.1.3 CCBS Description information element

CCBS Description information element is formed in the HLR A during the CCBS activation.

Table 5.6.1.3: Structure of CCBS Description information element

Parent InformationElement

Child Informationelement name

Information elementRequired

Information element description

CCBS Description CCBS Index,AddressOfB,

BasicServiceGroup

MMM

CCBS Index (range 1 - 5) identifies the request in the network.The structure of the AddressOfB is defined in table 5.6.1.2;BasicServiceGroup related to the original call.

3GPP

3G TS 23.093 V3.0.0 (1999-05)183G TS 23.093 version 3.0.0

5.6.2 Messages between MS and MSC

These messages are used in the originating network.

Table 5.6.2: Messages between MS and MSC

Message Messagesender

Informationelement name

Information elementRequired

Information element description

CCBS POSSIBLE MSC - - This message contains no information elements.CCBS REQUEST MS - - This message contains no information elements.CCBS REQUEST

ACKMSC CCBS Index,

AddressOfB,

BasicServiceGroup

M

O

O

CCBS Index (range 1 - 5) identifies the request in thenetwork.The structure of the AddressOfB is defined in table 5.6.1.2

BasicServiceGroup related to the original call.CCBS REQUEST

ERRORMSC Error M The information element can take the following values:

- Short term denial- Long term denial

DEACTIVATECCBS

MS CCBS Index C If CCBS Index is present the corresponding request shallbe deleted, otherwise all requests shall be deleted.

DEACTIVATECCBS ACK

MSC DeactivateResult M The information element can take the following values:- Success- Not Provisioned

INTERROGATECCBS

MS - - This message contains no information elements.

INTERROGATECCBS ACK

MSC List(1-5) of CCBSDescription;No Entries;

Not Provisioned

C

CC

The list shall contain one entry for each CCBS Requestfor which the HLR stores data or;the queue is empty or;CCBS is not provisioned for the subscriberExactly one of these information elements shall bepresent. The structure of the CCBS Description is definedin table 5.6.1.3.

CCBS CALL INFO MSC Call Information M The content of the Call Information is defined in thesubclause 5.6.1.1.

CCBS CALL INFOACK

MS GSM BC M GSM BC indicates the BC the MS prefers to use. Thenetwork may allocate a traffic channel accordingly.

CCBS CALL INFOERROR

MS Error M The information element can take the following values:- Incompatible Terminal

CCBS RECALL MSC CCBS Description,

Alerting Pattern

M,

C

The structure of the CCBS Description is defined intable 5.6.1.3.Alerting Pattern shall be present if it was received in theCCBS RUF message

CCBS SETUP MS - - The content of the message is the same as the MO Set-upmessage has. Refer to GSM 04.08.

CCBS RECALLREJECT

MS Cause M The MS shall indicate the reason of CCBS Recallrejection.The information element can take the following values:- Recall Rejected by the user- UDUB- ACMmax exceeded

3GPP

3G TS 23.093 V3.0.0 (1999-05)193G TS 23.093 version 3.0.0

5.6.3 Messages between MSC and VLR (B-interface)

5.6.3.1 Messages between MSC and VLR in the originating network

These messages are used in the originating network. Some messages are used also in the terminating network. They aremarked accordingly.

Table 5.6.3.1: Messages between MSC and VLR in the originating network

Message Messagesender

Informationelement name

Information elementRequired

Information element description

CALL END MSC - - This message contains no information elements.

The message is used also in the terminating network.CCBS CALLDELIVERY

MSC Outcome M The information element indicates whether CCBS Callwas successful or failure. It can take the following values:- Success;- Failure;- NDUB;- Busy;- Absent Subscriber..

The message is used also in the terminating network.CCBS REQUEST MSC - - This message contains no information elementsCCBS REQUEST

ACKVLR CCBS Index,

AddressOfB,

BasicServiceGroup

M

O

O

CCBS Index (range 1 - 5) identifies the request in thenetwork.The structure of the AddressOfB is defined in table 5.6.1.2

BasicServiceGroup related to the original call.CCBS REQUEST

ERRORVLR Error M The information element can take the following values:

- Short term denial;- Long term denial.

COMPLETERECALL

VLR Call Information M The content of the Call Information is defined in thesubclause 5.6.1.1.

COMPLETERECALL ACK

MSC - - This message contains no information elements

COMPLETERECALL

NEGATIVERESPONSE

MSC Negative Response M The negative information element can take the followingvalues:- Absent Subscriber;- Incompatible Terminal;- Radio Congestion.

DEACTIVATECCBS

MSC CCBS Index C If CCBS Index is present the corresponding request shallbe deleted, otherwise all requests shall be deleted.

DEACTIVATECCBS ACK

VLR DeactivateResult M The information element can take the following values:- Success;- Not Provisioned.

INTERROGATECCBS

MSC - - This message contains no information elements

3GPP

3G TS 23.093 V3.0.0 (1999-05)203G TS 23.093 version 3.0.0

Table 5.6.3.1: Messages between MSC and VLR in the originating network, cont.

Message Messagesender

Informationelement name

Information elementRequired

Information element description

INTERROGATECCBS ACK

VLR List(1-5) of CCBSDescription;No Entries;

Not Provisioned

C

C

C

The list shall contain one entry for each CCBS Requestfor which the HLR stores data; orthe queue is empty; or

CCBS is not provisioned for the subscriber.

Exactly one of these information elements shall bepresent. The structure of the CCBS Description is definedin table 5.6.1.3.

NOT IDLE MSC - - This message contains no information elements. Themessage is used also in the terminating network.

PAGE MS FORRECALL

VLR Location area ID,

TMSI

M

O

Location area in which the MS is to be paged

TMSI to be broadcast to identify the MSPAGE MS FOR

RECALLNEGATIVERESPONSE

MSC Negative Response M The negative information element can take the followingvalues:- Unknown LAI;- Absent Subscriber;- Busy Subscriber.

PROCESS ACCESSREQUEST

MSC - - Refer to GSM 03.18

RADIO FAILURE MSC - - This message contains no information elements.

The message is used also in the terminating network.RECALL VLR CCBS Description

Alerting Pattern

M

C

The structure of the CCBS Description is defined intable 5.6.1.3.Alerting Pattern shall be present if it was received in theCCBS RUF message

RECALL ACK MSC Cause M The information element can take the following values:- Accept;- Rejected;- T4 Expiry;- T10 Expiry;- Radio Failure;- UDUB, busy;- UDUB, idle;- Incompatible terminal.

SEARCH FOR MSMSC FOR RECALL

VLR - - This message contains no information elements

SEARCH FOR MSMSC FOR RECALL

ACK

MSC - - This message contains no information elements

SEARCH FOR MSMSC FOR RECALL

NEGATIVERESPONSE

MSC Negative Response M The negative information element can take the followingvalues:- Absent Subscriber;- Busy Subscriber;

SEND INFO FOROUTGOING CALL

MSC - - Refer to GSM 03.18

START STATUSENQUIRY

VLR - - This message contains no information elements.

The message is used also in the terminating network.STATUS ENQUIRY

RESULTMSC Status M The information element can take the following vales:

- CCBS Idle;- CCBS Not Idle.

The message is used also in the terminating network.STOP STATUS

ENQUIRYVLR - - This message contains no information elements.

The message is used also in the terminating network.

3GPP

3G TS 23.093 V3.0.0 (1999-05)213G TS 23.093 version 3.0.0

5.6.3.2 Messages between MSC and VLR in the destination network

These messages are used in the destination network. Some messages are used also in the originating network. They aremarked accordingly.

Table 5.6.3.2: Messages between MSC and VLR in the destination network

Message Messagesender

Informationelement name

Information elementRequired

Information element description

CALL END MSC - - Refer to table 5.6.3.1CCBS CALLDELIVERY

MSC - - Refer to table 5.6.3.1

START STATUSENQUIRY

VLR - - Refer to table 5.6.3.1

STATUS ENQUIRYRESULT

MSC - - Refer to table 5.6.3.1

STOP STATUSENQUIRY

VLR - - Refer to table 5.6.3.1

RADIO FAILURE MSC - - Refer to table 5.6.3.1NOT IDLE MSC - - Refer to table 5.6.3.1

COMPLETE CALL VLR -

Indicator

-

C

Refer to GSM 03.18In addition:The information element shall be present if the call isCCBS Call; otherwise it shall be absent.

PROCESS CALLWAITING

VLR -

Indicator

-

C

Refer to GSM 03.18In addition:The information element shall be present if the call isCCBS Call; otherwise it shall be absent.

SEND INFO FORINCOMING CALL

ACK

VLR -

CCBS Target

-

C

Refer to GSM 03.18In addition:The information element shall be present if the Bsubscriber can be target of CCBS request; otherwise it shallbe absent.

SEND INFO FORINCOMING CALL

NEGATIVERESPONSE

VLR -

CCBS Target

-

C

Refer to GSM 03.18In addition:The information element shall be present if the Bsubscriber can be target of CCBS request; otherwise it shallbe absent.

3GPP

3G TS 23.093 V3.0.0 (1999-05)223G TS 23.093 version 3.0.0

5.6.4 Messages between VLR and HLR (D-interface)

5.6.4.1 Messages between VLR and HLR in the originating network

These messages are used between VLR - HLR in the originating network. Some messages are used also in the destinationnetwork. They are marked accordingly.

Table 5.6.4.1: Messages between VLR and HLR in the originating network

Message Messagesender

Informationelement name

Information elementRequired

Information element description

CCBS REQUEST VLR Call Information

ISDN BC

ISDN HLC

ISDN LLC

PresentationIndicator

Translated B No

CAMEL Invoked

Basic Service Group

AddressOfB

M

M

C

C

C

M

C

M

M

The content of the Call Information is defined in thesubclause 5.6.1.1.ISDN BC derived for the initial call.

Shall be present if ISDN HLC was present in the initialcall; otherwise shall be absent.Shall be present if ISDN LLC was present in the initialcall; otherwise shall be absent.Shall be present if CLIR was invoked for the initial call;otherwise shall be absent.The number used for routing purposes stored ininternational E.164 format.Shall be present if MO CAMEL was invoked in the initialcall; otherwise shall be absent.GSM Elementary Basic Service Group which correspondsto the basic service used for initial call set-upThe structure of the AddressOfB is defined in table 5.6.1.2

CCBS REQUESTACK

HLR CCBS Index

AddressOfB

Basic Service Group

M

O

O

CCBS Index (range 1 - 5) identifies the request in thenetwork.The structure of the AddressOfB is defined in table 5.6.1.2

BasicServiceGroup related to the original call.CCBS REQUEST

ERRORHLR Error M The information element can take the following values:

- Short term denial;- Long term denial;

CCBS RUF HLR Call Information

CCBS Description

Translated B No

Replace B No

Alerting Pattern

M

M

M

C

C

The content of the Call Information is defined in thesubclause 5.6.1.1.The content of the CCBS Description is defined intable 5.6.1.3.The number used for routing purposes in internationalE.164 format.The information element shall be present if the HLRinstructs the MSC to replace the destination B numberwith the translated B number; otherwise it shall be absent.

Alerting Pattern shall be present if the HLR hasdetermined an alerting category or an alerting level forthe CCBS recall

CCBS RUF ACK VLR Result M The information element indicates whether CCBS Recallwas accepted. It can take the following values:- RUF Accepted;- RUF Rejected;- T4 Expiry;- T10 Expiry;- UDUB, idle;- UDUB, busy.

CCBS RUF ERROR VLR Error M The information element indicates the reason why CCBSRecall could not be successfully delivered. It can take thefollowing values:- IMSI Detached;- Restricted Area;- No Page Response;

3GPP

3G TS 23.093 V3.0.0 (1999-05)233G TS 23.093 version 3.0.0

- Incompatible Terminal;- Absent Subscriber;- Radio Failure;- Ccomp Busy;- System Failure.

3GPP

3G TS 23.093 V3.0.0 (1999-05)243G TS 23.093 version 3.0.0

Table 5.6.4.1: Messages between VLR and HLR in the originating network, cont.

Message Messagesender

Informationelement name

Information elementRequired

Information element description

EVENT REPORT VLR Status M The information element contains subscriber status. It cantake the following values:- CCBS Idle;- CCBS Not Idle;- CCBS Not Reachable.

The message is used also in the terminating network.EVENT REPORT

ACKHLR - - This message contains no information elements

The message is used also in the terminating network.EVENT_REPORT_

ERRORHLR Error M The information element contains no application specific

error values.

The message is used also in the terminating network.START

REPORTINGHLR - - This message contains no information elements.

The message is used also in the terminating network.START

REPORTING ACKVLR Status M The information element contains subscriber status. It can

take the following values:- CCBS Idle;- CCBS Not Idle;- CCBS Not Reachable.

The message is used also in the terminating network.START

REPORTINGERROR

VLR Error M The information element contains no application specificerror values.

The message is used also in the terminating network.CONTINUE

MONITORINGHLR - - This message contains no information elements.

The message is used also in the terminating network.STOP REPORTING HLR - - This message contains no information elements.

The message is used also in the terminating network.CCBS CALL

REPORTVLR Mode

Outcome

Status

M

M

C

The information element indicates the reporting mode. Itcan take the following values :- A;- B.The information element indicates the outcome of theCCBS Call. It can take the following values:- Success;- Busy (only for mode A);- NDUB (only for mode B)- Failure.The information element contains subscriber status. It isset only for mode B. It can take the following values:- CCBS Idle;- CCBS Not Idle;- CCBS Not Reachable.

The message is used also in the terminating network.CCBS CALL

REPORT ACKHLR - - This message contains no information elements.

The message is used also in the terminating network.CCBS CALL

REPORT ERRORHLR Error M The information element contains no application specific

error values.

The message is used also in the terminating network.DEACTIVATE

CCBSVLR CCBS Index C If CCBS Index is present the corresponding request shall

be deleted, otherwise all requests shall be deleted.DEACTIVATE HLR DeactivateResult M The information element can take the following values:

3GPP

3G TS 23.093 V3.0.0 (1999-05)253G TS 23.093 version 3.0.0

CCBS ACK - Success;- Not Provisioned.

DEACTIVATECCBS ERROR

HLR Error M The information element contains no application specificerror values.

3GPP

3G TS 23.093 V3.0.0 (1999-05)263G TS 23.093 version 3.0.0

Table 5.6.4.1: Messages between VLR and HLR in the originating network, cont.

Message Messagesender

Informationelement name

Information elementRequired

Information element description

INTERROGATECCBS

VLR - - This message contains no information elements.

INTERROGATECCBS ACK

HLR List(1-5) of CCBSDescription;No Entries;

Not Provisioned

C

C

C

The list shall contain one entry for each CCBS Requestfor which the HLR stores data or;the queue is empty or;

CCBS is not provisioned for the subscriber.

Exactly one of these information elements shall bepresent. The structure of the CCBS Description is definedin table 5.6.1.3.

INTERROGATECCBS ERROR

HLR Error M The information element contains no application specificerror values.

5.6.4.2 Messages between VLR and HLR in the destination network

These messages are used between VLR - HLR in the destination network. Some messages are used also in the originatingnetwork. They are marked accordingly.

Table 5.6.4.2: Messages between VLR and HLR in the destination network

Message Messagesender

Informationelement name

Information elementRequired

Information element description

EVENT REPORT VLR - - Refer to table 5.6.4.1EVENT REPORT

ACKHLR - - Refer to table 5.6.4.1

EVENT REPORTERROR

HLR - - Refer to table 5.6.4.1

STARTREPORTING

HLR - - Refer to table 5.6.4.1

STARTREPORTING ACK

VLR - - Refer to table 5.6.4.1

STARTREPORTING

ERROR

VLR - - Refer to table 5.6.4.1

CONTINUEMONITORING

HLR - - Refer to table 5.6.4.1

STOP REPORTING HLR - - Refer to table 5.6.4.1CCBS CALL

REPORTVLR - - Refer to table 5.6.4.1

CCBS CALLREPORT ACK

HLR - - Refer to table 5.6.4.1

CCBS CALLREPORT ERROR

HLR - - Refer to table 5.6.4.1

PROVIDEROAMINGNUMBER

HLR -

CCBS Call ReportingRequest

-

C

Refer to GSM 03.18In addition:The information element shall be present for CCBS Callroaming number enquiry; otherwise it shall be absent.

3GPP

3G TS 23.093 V3.0.0 (1999-05)273G TS 23.093 version 3.0.0

5.6.5 Messages between MSC and HLR (C-interface)

Table 5.6.5: Messages between MSC and HLR

Message Messagesender

Informationelement name

Information elementRequired

Information element description

SEND ROUTINGINFO

MSC -

CCBS Supported

CCBS Call Indicator

-

C

C

Refer to GSM 03.18In addition:The information element shall be present if GMSCsupports CCBS; otherwise it shall be absent.The information element shall be present, if SRI is forCCBS Call; otherwise it shall be absent.

SEND ROUTINGINFO_ACK

HLR -

CCBS Target

Keep CCBS CallIndicator

-

C

C

Refer to GSM 03.18In addition:The information element shall be present if the call isforwarded on busy and the subscriber B can be target ofCCBS requests; otherwise it shall be absent.The information element shall be present if the VMSCsupports CCBS and SRI enquiry was for CCBS Call;otherwise it shall be absent.

SEND ROUTINGINFO NEGATIVE

RESPONSE

HLR -

Negative Response

-

-

Refer to GSM 03.18New value(s) for existing parameter(s):- Busy_CCBS_Possible;- Busy_CCBS_Not_Possible.

5.6.6 Messages between MSC - MSC (E-interface)

Table 5.6.6: Messages between MSC and MSC

Message Messagesender

Informationelement name

Information elementRequired

Information element description

RESUME CALLHANDLING

MSC -

CCBS Target

-

C

Refer to GSM 03.79In addition:The information element shall be present if the call isforwarded on busy and the subscriber B can be target ofCCBS requests; otherwise it shall be absent.

5.6.7 Existing parameters containing CCBS specific information

Mobile Station Classmark 2 (refer to GSM 04.08 contains information whether “Network initiated MO CM connectionrequest” is supported or not. This information is vital for the recall mechanism.

CC capabilities (refer to GSM 04.08) contains information whether “Prolonged Clearing Procedures” are supported or not.This information is vital for the activation mechanism.

SS-Code and SS-Status (refer to GSM 09.02) contains information whether CCBS service is provisioned to the subscriber.Both originating and destination CCBS service have their own SS-Code.

3GPP

3G TS 23.093 V3.0.0 (1999-05)283G TS 23.093 version 3.0.0

6 Monitoring and CCBS Call Reporting

6.1 Monitoring

6.1.1 Overview

Monitoring is the process where the subscriber state is observed and reported. When monitoring is started, the currentsubscriber state is reported and any subsequent changes of subscriber state are reported until monitoring is stopped.

Monitoring subscriber state information will be necessary against MS B and may also be necessary against MS A.

For both these cases the monitoring functionality is located in the appropriate serving VMSC/VLR and is controlled fromthe appropriate HLR. The actions on the A-side and B-side for monitoring are completely independent and the followingdescription is generic to cover either case. The HLR sends an explicit Start Reporting signal to the VLR to initiatemonitoring. The VLR acknowledges the request confirming that monitoring has started and indicates the current statusof the subscriber state in the VMSC/VLR. The VLR will continue to send an Event Report to the HLR whenever theappropriate subscriber state transition event occurs. The HLR sends an explicit Stop Reporting signal to the VLR whenreporting on the subscriber state transitions is no longer required.

6.1.2 Monitoring Subscriber B-state information

The CCBS service requires monitoring of the subscriber state at the called destination network (B-side). This monitoringenables the HLR B to be aware of any transition of subscriber state in VMSC/VLR B while there is an active CCBSRequest in the HLR B queue. The basic service operation is that, when the destination B subscriber state becomes Idle,the HLR B is informed and a Remote User Free indication is sent towards the originating A network at the appropriatetime. If subsequently to that event the destination B subscriber state becomes not Idle or not reachable, then the HLR Bis informed by the VMSC/VLR B in order that it can take an appropriate action towards HLR A, e.g. defer sending of theRemote User Free indication.

6.1.3 Monitoring Subscriber A state information:

Monitoring Subscriber A state information will be necessary if the Remote User Free indication from Destination Bnetwork cannot be acted upon because e.g. MS A is not idle or not reachable and leads to the CCBS request beingsuspended. The service action in this event is that, when the subscriber state subsequently becomes Idle, the HLR A isinformed and a Resume indication is sent towards the destination B network at the appropriate time.

3GPP

3G TS 23.093 V3.0.0 (1999-05)293G TS 23.093 version 3.0.0

6.2 MSC/VLR Monitoring ModelThe Monitoring model represents the information related to the status of the subscriber connection in the MSC/VLR. Ageneric monitoring model is used in the MSC/VLR covering the needs of both subscriber A and subscriber B stateinformation for CCBS. The MSC/VLR monitoring model for CCBS is shown in figure 6.2.1. Note that state transitionsreported to the HLR are shown as solid lines.

NOT IDLENOT

REACHABLE

IDLE

Figure 6.2.1: MSC/VLR Monitoring Model

6.2.1 Subscriber status

The monitoring model in the MSC/VLR makes use of the three subscriber states described in table 6.2.1.

NOTE: Refer to GSM 03.78 for equivalent subscriber state description.

Table 6.2.1: Subscriber States

Subscriber states Description (for monitoring purposes) Notes

IDLE The state of the MS is neither "NOT IDLE" nor "NOTREACHABLE"

"Assumed Idle"

NOT IDLE The MS is engaged on a transaction for a MO or MTcircuit switched call

"CAMEL busy"

NOT REACHABLE The MSC/VLR can determine from its internal data that theMS is not reachable e.g. IMSI detached, Restricted Area,No Page Response.

"Network DeterminedNot Reachable"

For each subscriber state a description can be found on the entry events, functions and exit events.

3GPP

3G TS 23.093 V3.0.0 (1999-05)303G TS 23.093 version 3.0.0

6.2.1.1 Idle

Entry events:

- Indication of last call released (Mobile Originated or Mobile Terminated);

- Indication of radio link failure;

- Indication of MS activity related to e.g. MO-SMS, MT-SMS and CISS;

- IMSI Attached;

- Location Update.

Functions:

- Events leading to a transition to the Not Idle or Not Reachable subscriber state are awaited.

Exit events:

- A Mobile Originated Set-up message is received from the MS for first (and only) call;

- A Mobile Terminated Set-up message is sent to the MS for first (and only) call.

- IMSI Detached;

- Roaming in LA not allowed;

- No Page Response;

- An exception condition is encountered e.g. Cancel Location indication received.

6.2.1.2 Not Idle

Entry events:

- A Mobile Originated Set-up message is received from the MS for first (and only) call;

- A Mobile Terminated Set-up message is sent to the MS for first (and only) call.

Functions:

- Events leading to a transition to the Idle or Not Reachable subscriber state are awaited.

Exit events:

- Indication of last call released (Mobile Originated or Mobile Terminated);

- Indication of radio link failure;

- An exception condition is encountered e.g. Cancel Location indication received.

6.2.1.3 Not Reachable

Entry events:

- IMSI Detached;

- Roaming in LA not allowed;

- No Page Response.

Functions:

- Events leading to a transition to the Idle or Not Idle subscriber state are awaited.

3GPP

3G TS 23.093 V3.0.0 (1999-05)313G TS 23.093 version 3.0.0

Exit events:

- Indication of MS activity related to e.g. MO-SMS, MT-SMS and CISS;

- IMSI Attached;

- Location Update;

- A Mobile Originated Set-up message is received from the MS for first (and only) call;

- A Mobile Terminated Set-up message is sent to the MS for first (and only) call;

- An exception condition is encountered e.g. Cancel Location indication received.

6.2.2 Reporting of subscriber state transitions

Transitions between subscriber states are reported from the MSC/VLR, while monitoring in the MSC/VLR is on going.The table 6.2.2 indicates which transitions are monitored in the MSC/VLR and whether these are reported to the HLR forthe CCBS service. An appropriate Event Report signal is sent from the VLR to the HLR when a relevant state transitionoccurs. The Event Report signal includes a status parameter which reflects the subscriber state information.

Table 6.2.2: Reporting of Subscriber States Transitions

Subscriber state transition event Event reportingHLR informed

Event reportSubscriber status

IDLE to NOT IDLE Yes CCBS Not Idle

IDLE to NOT REACHABLE Yes CCBS Not Reachable

NOT IDLE to IDLE Yes CCBS Idle

NOT IDLE to NOT REACHABLE No -

NOT REACHABLE to IDLE Yes CCBS Idle

NOT REACHABLE to NOT IDLE No -

6.2.2.1 Start Reporting of Monitoring Events

When a Start Reporting signal is received from the HLR, the VLR shall acknowledge the request confirming thatmonitoring has started and indicate the current status of the subscriber state in the MSC/VLR. The VLR shallsubsequently continue to send the Event Reports indicated in table 6.2.2 whenever the appropriate subscriber statetransition event occurs.

Note where a single user has a CCBS request activated against him and has an outstanding CCBS request suspendedagainst someone else, (i.e. is effectively both destination B and CCBS subscriber A) reporting on both A-side and B-sideis required. In this case, the VLR shall only send a single Event Report as indicated in table 6.2.2 whenever theappropriate subscriber state transition event occurs. The HLR shall not send another Start Reporting signal to the VLR ifmonitoring is already ongoing in the MSC/VLR for either A-side or the B-side.

6.2.2.2 Stop Reporting of Monitoring Events

When a Stop Reporting signal is received from the HLR, the VLR shall stop sending the Event Reports.

3GPP

3G TS 23.093 V3.0.0 (1999-05)323G TS 23.093 version 3.0.0

6.3 CCBS Call Reporting

6.3.1 Overview

As well as monitoring of the subscriber state, it is also necessary to report the result of the CCBS Call. The basicreporting requirements are as follows from both the A-side and the B-side.

CCBS Call Reporting - A-side:

The CCBS service logic in the originating network HLR A requires a report on the outcome of the CCBS Call resultingfrom the acceptance of the CCBS Recall by Subscriber A. The VLR A sends a CCBS Call Report to the HLR A indicatingthe outcome of the CCBS call processing in MSC/VLR A when e.g. an address complete message (ACM) is received fromthe destination B network. CCBS Call Reporting on the A-side is completely independent of any monitoring of subscriberstate information. The sending of CCBS Call Report is required even when there is no monitoring ongoing in theMSC/VLR.

CCBS Call Reporting- B-side:

The CCBS service logic in the destination network HLR B requires a report on the outcome of CCBS Call processing inthe MSC/VLR B. The HLR B initiates the CCBS call outcome reporting in the VLR when the VLR is normally queried toprovide routing information for mobile terminated calls (by including an CCBS indicator in the PRN message). The VLR Bsends a CCBS Call Report to the HLR B indicating the outcome of the CCBS call processing and the new status of thesubscriber state in the MSC/VLR B when e.g. MS B is alerted to the CCBS Call.

6.3.2 Originating Network (A-side)

When a CCBS RUF signal is received by the VLR, CCBS processing in the MSC/VLR leads to a CCBS Recall signal beingsent to the MS. When the response to the CCBS Recall is received, the VLR shall subsequently send a CCBS Call Reportwhen the relevant processing for the outgoing CCBS call to the destination network is completed as shown in the SDLsfor MSC/VLR A.

6.3.3 Destination Network (B-side)

When an initiate CCBS Call Reporting Request signal (B-side) is received by the VLR in the Provide Roaming Numbermessage, the VLR shall subsequently send a CCBS Call Report when the relevant processing of the incoming CCBS callis completed as shown in the SDLs for MSC/VLR B.

6.3.3.1 Interaction of Event Reporting and CCBS Call Report

Reporting on subscriber state transitions will be ongoing in the MSC/VLR B when a report on the CCBS call outcome isrequired.

When a subscriber state transition from IDLE to NOT IDLE occurs due to an incoming CCBS call, an Event Report shallnot be sent. Instead, a CCBS Call Report (containing CCBS call outcome information and the status) shall be sent to theHLR B. After the CCBS Call Report has been sent, normal Event Reporting will continue i.e. the VLR shall subsequentlysend only the Event Reports indicated in table 6.2.2 when the next appropriate subscriber state transition event occurs.

6.4 Location UpdateThe MS may roam to a new MSC/VLR area while monitoring is ongoing in the previous MSC/VLR. When the VLRreceives a Cancel Location signal from the HLR due to normal mobility management procedures, any ongoing CCBSrelated activities associated with the subscriber shall cease.

If the A-side monitoring is ongoing when the HLR receives a Location Update request from the new VLR, the LocationUpdate signal is considered to indicate that the subscriber state is idle and the appropriate CCBS process in the HLR isinformed. The normal mobility management procedures will lead to a Cancel Location signal being sent to the old VLRcausing the Event Reporting to stop.

3GPP

3G TS 23.093 V3.0.0 (1999-05)333G TS 23.093 version 3.0.0

If the B-side monitoring is ongoing when the HLR receives a Location Update request from the new VLR, the normalmobility management procedures are followed. On successful completion of Location Update procedure, the HLR shallsend a Start Reporting signal to the new VLR. If during the handling of the normal Location Updating procedure, it isdetected that the new MSC/VLR does not support CCBS, the HLR shall not send a Start Reporting signal to the newVLR.

NOTE: There is no impact to the MS due to CCBS monitoring, i.e. normal Location Update procedures apply.

7 MobilityThe handling for CCBS specific mobility is described below.

7.1 Mobility during ActivationIn order to allow the activation of CCBS when the call is released, the CC connection towards the MS shall be kept, toavoid any problems of mobility with the MS A.

Therefore the MSC shall maintain the CC connection with the MS A while T1 is running and until either T1 expires or theMSC sends a CCBS REQUEST ACK or CCBS REQUEST ERROR to the MS. After MSC has sent CCBS REQUEST ACKor CCBS REQUEST ERROR, the MSC A shall release the CC connection with MS.

7.2 Number used within CCBS CallThe activating MSC A shall store the originally dialled number in the Call Information container. The TranslatedBNoparameter shall contain destination B address stored in international E.164 format.

If the MS A is registered outside of the HPLMN during the initial call or when Remote_User_Free is received from thedestination B network the HLR A may request the recall MSC A to change the number used for CCBS Call to theTranslatedBNo instead. Refer to the SDLs for originating MSC/VLR.

If CAMEL service was activated in the original call the HLR A shall not request to change the number used for the CCBSCall.

7.3 MS does Location UpdateCCBS does place extra requirements for the Location Update procedure in the HLR when MS is monitored. Refer tosubclause 6.4.

7.4 Mobility during CCBS Call in the destination networkIf MS registers to non-supporting network special handling has to be applied. Refer to subclause 10.1.3.

3GPP

3G TS 23.093 V3.0.0 (1999-05)343G TS 23.093 version 3.0.0

8 Interaction with other supplementary servicesGSM 02.93 specifies a number of interactions between CCBS and other supplementary services. Additional details ofhow these interactions apply are as follows.

8.1 Call forwarding unconditional (CFU)If a call to destination B is forwarded to subscriber C by CFU and MS C is NDUB, the GMSC shall inform MSC A thatCCBS is not possible when it releases the call. Refer to Process MT_GMSC (see GSM 03.18) for further details.

If destination B activates CFU after subscriber A has activated a CCBS Request against destination B, HLR B shall notprocess CCBS Requests in the queue which are related to the relevant Basic Service Group, except that T7 shall continuefor each CCBS Request in the destination B queue. If T7 expires for a particular request, HLR B shall cancel the request,as described in the SDLs shown in figure 11.2.2.1.

If MSC B is monitoring MS B when CFU is activated by destination B and all the CCBS Requests in the destination Bqueue subsequently become "Active and Quiescent", then HLR B shall send “Stop Reporting” to MSC B. If destinationB deactivates CFU resulting in one or more requests becoming "Active and Operative" in the destination B queue then,HLR B shall send “Start Reporting” to MSC B if monitoring is not already ongoing.

A CCBS Call shall be forwarded without the CCBS call Indicator.

8.2 Call forward on busy (CFB)If a call to destination B is forwarded to subscriber C by CFB and MS C is NDUB, the forwarding switch (GMSC orVMSC) shall inform MSC A that CCBS is possible when it releases the call. Refer to Process MT_GMSC or ProcessICH_MSC (see GSM 03.18) for further details.

If destination B activates CFB after subscriber A has activated a CCBS Request against destination B, HLR B shallcontinue to process CCBS Requests in the queue. If a CCBS Call subsequently arrives at MSC B and MS B is NDUB, anetwork provider option exists as to whether:

- the CCBS call shall be treated as when MS B is busy for the CCBS call, without CFB active; or

- the CCBS call shall be forwarded without the CCBS call Indicator.

8.3 Call forwarding on no reply (CFNRy)If a call to destination B is forwarded to subscriber C by CFNRy and MS C is NDUB, the forwarding switch (VMSC) shallinform MSC A that CCBS is not possible when it releases the call. Refer to Process MT_GMSC or Process ICH_MSC(see GSM 03.18) for further details

If destination B activates CFNRy after subscriber A has activated a CCBS Request against destination B, HLR B shallcontinue to process CCBS Requests in the queue.

A CCBS call shall be forwarded without the CCBS call Indicator.

8.4 Call forwarding on MS not reachable (CFNRc)If a call to destination B is forwarded to subscriber C by CFNRc and MS C is NDUB, the forwarding switch (GMSC orVMSC) shall inform MSC A that CCBS is not possible when it releases the call. Refer to Process MT_GMSC orProcess_ICH_MSC (see GSM 03.18) for further details.

If destination B activates CFNRc after subscriber A has activated a CCBS Request against destination B, HLR B shallcontinue to process CCBS Requests in the queue.

The CCBS call shall be forwarded without the CCBS call Indicator.

3GPP

3G TS 23.093 V3.0.0 (1999-05)353G TS 23.093 version 3.0.0

8.5 Call Waiting (CW)No impact.

8.6 Multiparty service (MPTY)No impact.

8.7 Closed user group (CUG)No impact.

8.8 Advice Of Charge (AoC)If subscriber A accepts a "CCBS Recall" indication but ACMmax exceeds, then MSC A shall cancel the associatedrequest and shall not establish the CCBS Call.

8.9 Barring of all outgoing calls (BAOC)If subscriber A accepts a "CCBS Recall" indication but MSC A detects that BAOC is active and operative, then MSC Ashall cancel the associated request and shall not establish the CCBS Call.

8.10 Barring of outgoing international calls (BOIC)If subscriber A accepts a "CCBS Recall" indication but the CCBS Call would be an international call and MSC A detectsthat BOIC is active and operative, then MSC A shall cancel the associated request and shall not establish the CCBS Call.

8.11 Barring of outgoing international calls except those directedto the home PLMN country (BOIC-exHC)

If subscriber A accepts a "CCBS Recall" indication but the CCBS Call would be an international call except to the homePLMN country and MSC A detects that BOIC-exHC is active and operative, then MSC A shall cancel the associatedrequest and shall not establish the CCBS Call.

8.12 Barring of all incoming calls (BAIC)If a CCBS Request arrives at HLR B and HLR B detects that BAIC is active and operative for the relevant Basic ServiceGroup, then HLR B shall not accept the activation attempt and shall indicate short term denial in the response.

If MSC B is monitoring MS B when BAIC is activated by destination B then all the CCBS Requests in the destination Bqueue subsequently become "Active and Quiescent" and HLR B shall send "Stop Reporting" to MSC B. If destination Bdeactivates BAIC resulting in one or more requests becoming "Active and Operative" in the destination B queue then,HLR B shall send “Start Reporting” to MSC B if monitoring is not already ongoing.

If barring of all incoming calls becomes active and operative for a particular Basic Service Group for destination B, suchthat a CCBS call from subscriber A is not permitted, HLR B shall cancel the associated request related to the BasicService Group and select the next non-suspended request in the queue for processing for other Basic Service Groups.

3GPP

3G TS 23.093 V3.0.0 (1999-05)363G TS 23.093 version 3.0.0

8.13 Barring of incoming calls when roaming outside the homePLMN country (BIC-Roam)

If a CCBS Request arrives at HLR B and HLR B detects that BIC-Roam is active and operative for the relevant BasicService Group, then HLR B shall not accept the activation attempt and shall indicate short term denial in the response.

If MSC B is monitoring MS B when BIC-Roam is activated by destination B then all the CCBS Requests in thedestination B queue subsequently become "Active and Quiescent" and HLR B shall send "Stop Reporting" to MSC B. Ifdestination B deactivates BIC-Roam resulting in one or more requests becoming "Active and Operative" in thedestination B queue then, HLR B shall send "Start Reporting" to MSC B if monitoring is not already ongoing.

If barring of incoming calls when roaming outside the home PLMN country becomes active and operative for a particularBasic Service Group for destination B, such that a CCBS call from subscriber A is not permitted, HLR B shall cancel theassociated request related to the Basic Service Group and select the next non-suspended request in the queue forprocessing for other Basic Service Groups.

8.14 Completion of calls to busy subscriber (CCBS)Subscriber A may have successfully activated one or more CCBS requests against different destinations B, and alsohave one or more CCBS requests successfully activated against him by different subscribers. In this case, HLR A shallco-ordinate the different requests.

Checking for an identical CCBS request already existing shall include checks in both directions, i.e. if subscriber Aactivates a CCBS Request against destination B, HLR A shall check subscriber A’s originating queue for any previousrequests activated by subscriber A against destination B for the same basic service group. HLR A shall also checksubscriber A’s target queue for any requests activated by destination B against subscriber A for the same basic servicegroup.

3GPP

3G TS 23.093 V3.0.0 (1999-05)373G TS 23.093 version 3.0.0

9 Interaction with other network featuresGSM 02.93 specifies a number of interactions between CCBS and other network features.

9.1 Customised Applications for Mobile network Enhanced Logic(CAMEL)

For a terminating CAMEL based service which changes the destination B address for the original call whichsubsequently encounters NDUB, the GMSC shall inform originating network that CCBS is not possible when it releasesthe call.

If an originating CAMEL based service determines for a CCBS Call a different destination B Address than for the originalcall, the CCBS Call shall be released and the associated CCBS Request shall be cancelled.

If the CAMEL based service requests a call set-up to an alternative destination after the original call has met Busy, CCBSPossible condition, the CCBS activation shall be allowed if the alternative call set-up also encounters Busy condition.

9.2 Support of Optimal Routeing (SOR)The CCBS supporting GMSC shall include CCBS Supported indicator to the SRI message.

If HLR B receives a request for routeing information when destination B is blocked (i.e. the HLR B is waiting for an SRIfor a CCBS call set-up) and the SRI does not include a CCBS call indicator nor CCBS supported in the GMSC indicatorand the request is from a GMSC not in the same PLMN as HLR B, then HLR B shall return an SRI negative responseindicating OR not allowed. This will force the GMSC to route the call to a GMSC in the same PLMN as HLR B (see GSM03.79).

The GMSC in HPLMN B should be able to include the CCBS Call indicator in the non-OR SRI, and the CCBS call set-upwill proceed, although it won't be optimally routed.

If the HLR receives an SRI indicating a CCBS-capable GMSC but not a CCBS call while awaiting SRI for a CCBS call, itcan treat the request as if the B-subscriber were busy, regardless of where the GMSC is.

3GPP

3G TS 23.093 V3.0.0 (1999-05)383G TS 23.093 version 3.0.0

10 Interworking with other networksThe point of interworking shall be the interface between HLR A and HLR B. The flow of information across this interfaceshall be identical to that between exchanges for the ISDN version of CCBS.

Interworking with ISDNs which support the ISDN version of CCBS is therefore available without further modification.

Interworking with networks other than ISDNs, e.g. private networks, is not specified here, but is not precluded.

CCBS shall be able to interwork through networks which do not support CCBS. In this situation, the CCBS service mayfail.

10.1 Interworking with network entities not supporting CCBSCCBS requires support of the service by the following entities for it to operate as specified above:

- MS A;

- MSC A;

- VLR A;

- HLR A;

- GMSC;

- HLR B;

- MSC B;

- VLR B.

The following shows the actions required to cover the situations where these entities do not support CCBS. Note thatthe situation is further complicated by mobility. For example, MSC A may support CCBS when the initial request is made,but if subscriber A has changed location, the new MSC A may not support CCBS.

It is assumed that the entities support the service at the points in the call where actions are initiated by them, and that anentity which receives an indication for the CCBS service but does not support it can indicate its lack of support to thesending entity.

10.1.1 CCBS not supported by MSC A

HLR A knows whether the MSC A supports CCBS or not through the transfer of subscriber data.

MS B becomes idle

When HLR A receives the "Remote User Free" indication for a particular CCBS Request and detects that the MSC Awhere MS A is currently registered does not support CCBS, then HLR A shall suspend the corresponding CCBSRequest and shall send "CCBS Suspend" to HLR B. When MS A registers in a different MSC which supports CCBS,HLR A shall resume the corresponding CCBS Request and shall send "CCBS Resume" to HLR B, continuing as if MS Ahad become free.

10.1.2 CCBS not supported by HLR B

Initial call encounters busy

If an MSC B that supports CCBS recognises that HLR B does not support CCBS then “CCBS Not Possible” will begenerated in the CCBS diagnostic.

3GPP

3G TS 23.093 V3.0.0 (1999-05)393G TS 23.093 version 3.0.0

10.1.3 CCBS not supported by MSC B

HLR B knows whether the MSC B supports CCBS or not through the transfer of subscriber data.

CCBS Request

If MSC B does not support CCBS, HLR B acknowledge the request and start T7. No processing of the destination Bqueue and subsequently no monitoring of destination B will be possible until destination B registers in a supportingMSC.

CCBS Call set-up

If HLR B knows that MSC B does not support CCBS the HLR B shall delete the corresponding CCBS Request and shallrequest a Roaming No without including the CCBS Call indicator in the request. Within Send Routeing Info Ack the HLRshall inform the GMSC to remove CCBS Call Indicator from the IAM message.

After a “Remote User Free” has been sent from MSC B but before the CCBS call set-up is completed, destination B mayregister in an MSC which does not support the service. MSC B shall accept the CCBS call, but MSC B will not be able toinform HLR B of the successful completion of the CCBS call, so the request will remain active in HLR B until the recall Btimer (T9) expires and the request is cancelled.

3GPP

3G TS 23.093 V3.0.0 (1999-05)403G TS 23.093 version 3.0.0

11 Network entity functionsThe following SDL diagrams describe the various processes and procedures within individual network entities forhandling CCBS. The SDL diagrams are as follows:

11.1 Originating Network Processes

11.1.1 Processes and procedures in MSC/VLR

Figure 11.1.1.1: Process MSC_CCBS_Recall_Manager

This process controls the CCBS Recall handling in the MSC and controls timers T4 and T10

Figure 11.1.1.2: Process VLR_CCBS_Recall_Manager

This process controls the CCBS Recall handling in the VLR and reports the result of the Recall directly to the HLR.

Figure 11.1.1.3: Process OCH_CCBS_VLR

This process controls the CCBS Call Setup in the VLR

Figure 11.1.1.4: Procedure CCBS_Check_OG_Call

This procedure checks whether the outgoing call meets various conditions set by the CCBS supplementary service. IfCCBS is not implemented Pass exit shall be taken.

Figure 11.1.1.5: Procedure CCBS_Check_If_CCBS_Possible

This procedure is called when Release message is received from the destination network. It checks whether CCBSactivation is possible.

Figure 11.1.1.6: Procedure CCBS_Activation_MSC

If CCBS activation is possible this procedure is called. It handles the dialogue between MS and MSC and MSC and HLRrespectively.

Figure 11.1.1.7: Procedure Page_MS_MSC_For_Recall

During CCBS recall this procedure handles paging of the MS if the location area id is known.

Figure 11.1.1.8: Procedure Search_For_MS_MSC_For_Recall

During CCBS recall this procedure handles paging of the MS on MSC side if the location area id is not known.

Figure 11.1.1.9: Procedure Search_For_MS_VLR_Recall

During CCBS recall this procedure handles paging of the MS on VLR side if the location area id is not known.

Figure 11.1.1.10: Procedure Complete_Recall_MSC

During CCBS recall this procedure handles early channel allocation and establish CC connection with the MS.

Figure 11.1.1.11: Procedure CCBS_OCH_Report_Success

This procedure is called when CCBS call is successfully delivered to the destination network. The procedure informsHLR of successful call delivery.

Figure 11.1.1.12: Procedure CCBS_OCH_Report_Failure

This procedure is called when CCBS call delivery failed to the destination network. The procedure informs HLR of calldelivery failure.

3GPP

3G TS 23.093 V3.0.0 (1999-05)413G TS 23.093 version 3.0.0

Process MSC_CCBS_Recall_Manager 1(4)

Signals to/from the leftare to/from the BSS.signals to/from the rightare to/from the VLRunless specified otherwise

Idle

Search_For_MS_MSC_For_Recall

Page_MS_For_Recall

Search_For_MS_MSC_For

Recall

Page_MS_MSCFor_Recall

Result=Pass

Refer to GSM 03.18Process_Access_

Request_MSC

Result=Pass

Releasecall

resources

Wait_For_Recall_Result

Idle

Yes

No

No

Yes

Figure 11.1.1.1: Process MSC_CCBS_Recall_Manager (sheet 1 of 4)

3GPP

3G TS 23.093 V3.0.0 (1999-05)423G TS 23.093 version 3.0.0

Process MSC_CCBS_Recall_Manager 2(4)

Signals to/from the leftare to/from the BSS.signals to/from the rightare to/from the VLRunless specified otherwise

Wait_For_Recall_Result

CompleteRecall

Complete_Recall_MSC

Result

TCH allocated :=False

TCH allocated :=True

Releasecall

resources

Wait_For_Recall Idle

Recall

Recall

Is the MS engaged ona circuit switched call

MS =Busy

Start T4 Start T10

Wait_For_Recall_

Response

Pass

TCH_allocated

Fail

No

Yes

Figure 11.1.1.1: Process MSC_CCBS_Recall_Manager (sheet 2 of 4)

3GPP

3G TS 23.093 V3.0.0 (1999-05)433G TS 23.093 version 3.0.0

Process MSC_CCBS_Recall_Manager 3(4)

Signals to/from the leftare to/from the BSS.signals to/from the rightare to/from the VLRunless specified otherwise

Wait_For_Recall_

Response

CCBS_Recall_Reject(Cause)

T4 Expiry T10 ExpiryReleaseTransaction

Stop T4Stop T10

Cause

Is the MS engaged ona circuit switched call

MS =Busy

Cause:=UDUB, busy

Cause:=UDUB, Idle

Cause:=Rejected

Cause:=T4 Expiry

Cause:=T10 Expiry

Cause:=Radio failure

Recall_Ack(Cause)

Releasecall

resources

Idle

UDUB

RejectedACMMax exceeded

Yes

No

Figure 11.1.1.1: Process MSC_CCBS_Recall_Manager (sheet 3 of 4)

3GPP

3G TS 23.093 V3.0.0 (1999-05)443G TS 23.093 version 3.0.0

Process MSC_CCBS_Recall_Manager 4(4)

Signals to/from the leftare to/from the BSS.signals to/from the rightare to/from the VLRunless specified otherwise

Wait_For_Recall_

Response

CCBS_Setup

BasicServiceGroupof the call =BasicServiceGroup receivedfrom HLR

ReplaceBNo

Use TranslatedBNoinstead of the originally

dialed B number

Stop T4Stop T10

Cause :=Incompatibe

terminal

Cause:=Accept

Recall_Ack(Cause)

Recall_Ack(Cause)

Id leCCBS_Report_

Not_Idle

Refer to GSM 03.18 OG_Call_Setup_MSC

CCBS_Check_Last_Call

Releasecall

resources

Idle

Yes

No

True

False

Figure 11.1.1.1: Process MSC_CCBS_Recall_Manager (sheet 4 of 4)

3GPP

3G TS 23.093 V3.0.0 (1999-05)453G TS 23.093 version 3.0.0

Process VLR_CCBS_Recall_Manager 1(4)

Signals to and from the leftare to/from the MSC. Signals to and from the right are to/from the HLR unless specified otherwise

Idle

CCBS_RUF

Check_Parameters See GSM 03.18

Result

Error:=Negativeresponse

CCBS_RUF_Error (Error)

Not_Reachable

To CCBS_Monitoring_VLR

Idle

IMSIDetached

Error := IMSI_Detached

Roaming inLA Allowed

Locationarea IDknown

Search_For_MS_VLR_

Recall

Result=Pass

1Wait_For_

Recall_Request

Page_MS_For_Recall

Error := Restricted_Area

Fail

Pass

Yes

No

Yes

No

No

Yes

Yes

No

Figure 11.1.1.2: Process VLR_CCBS_Recall_Manager (sheet 1 of 4)

3GPP

3G TS 23.093 V3.0.0 (1999-05)463G TS 23.093 version 3.0.0

Process VLR_CCBS_Recall_Manager 2(4)

Signals to and from the leftare to/from the MSC. Signals to and from the right are to/from the HLR unless specified otherwise

Wait_For_Recall_Request

Page MS ForRecallnegativeresponse

1ProcessAccessRequest

Absentsubscriber

Refer to GSM 03.18Process_Access_

Request_VLR

This check does notdetermine whether aCC connection is establishedbut rather that another call isin the establishment phase

Busysubscriber

Not_Reachable

To CCBS_Monitoring_VLR

Result =Pass

Error :=System_Failure

Error :=CComp_Busy

Error :=No Page Response

Error := Absent_Subscriber

CCBS_RUF_Error (Error)

CompleteRecall

IdleWait_For_

Complete_Call_Result

No

Yes

No

Yes

No

Yes

Figure 11.1.1.2: Process VLR_CCBS_Recall_Manager (sheet 2 of 4)

3GPP

3G TS 23.093 V3.0.0 (1999-05)473G TS 23.093 version 3.0.0

Process VLR_CCBS_Recall_Manager 3(4)

Signals to and from the leftare to/from the MSC. Signals to and from the right are to/from the HLR unless specified otherwise

Wait_for_Complete_Recall

Result

CompleteRecall ack

CompleteRecall negativeresponse

RecallNegativeResponse

Error :=Incompatible_

Terminal

Error := Radio_Failure

Error := System_Failure

CCBS_RUFError (Error)

Wait_For-Recall_

ResponseIdle

Incompatible_Terminal

Absent_SubscriberRadio_Congestion

ELSE

Figure 11.1.1.2: Process VLR_CCBS_Recall_Manager (sheet 3 of 4)

3GPP

3G TS 23.093 V3.0.0 (1999-05)483G TS 23.093 version 3.0.0

Process VLR_CCBS_Recall_Manager 4(4)

Signals to and from the leftare to/from the MSC. Signals to and from the right are to/from the HLR unless specified otherwise

Wait_For-Recall_

Response

Recall_Ack(Cause)

Cause = RadioFailure

Result :=Cause

Error := Radio_Failure

CCBS_RUF_Ack (Result)

CCBS_RUF_Error (Error)

Result

Wait_For_Call_Delivery

CCBS_Call_Delivery(Outcome)

Mode := A

CCBS_Call_Report(Mode,Outcome)

Idle

No

Yes

RUF Accepted

ELSE

Figure 11.1.1.2: Process VLR_CCBS_Recall_Manager (sheet 4 of 4)

3GPP

3G TS 23.093 V3.0.0 (1999-05)493G TS 23.093 version 3.0.0

Process OCH_CCBS_VLR 1(1)

Idle

Send infoFor OutgoingCall

Note: From GSM 03.18Procedure OG_Call_Setup_MSC

OG_Call_Subscription_Check_VLR

See GSM 03.18

Idle

Figure 11.1.1.3: Process OCH_CCBS_VLR

3GPP

3G TS 23.093 V3.0.0 (1999-05)503G TS 23.093 version 3.0.0

Procedure CCBS_Check_OG_Call 1(1)

CCBS ProvisionedandME supports CCBS

Reconnect

CCBS Call

TranslatedBNo :=Routing addressin internationalE.164 format

Translated B No receivedfrom HLR = CCBS Calltranslated target

TranslatedBNo :=Routing addressin internationalE.164 format

Set CCBS_Call_Indicator to IAM

message

Store CallInformation

Result :=Fail

Result :=Pass

Y e s

No

False

True

Y e s

No

Y e s

No

Figure 11.1.1.4: Procedure CCBS_Check_OG_Call

3GPP

3G TS 23.093 V3.0.0 (1999-05)513G TS 23.093 version 3.0.0

Procedure CCBS_Check_If_CCBS_Possible 1(1)

CCBSProvisioned

Reconnect

Cause = BusyorCause = No circuitchannel available

CCBSCall

Outcome :=Failure

CCBS_Call_Delivery(Outcome)

To VLR_CCBS_Recall_Manager

Clear storedcall information

Initial result :=CCBS_Not

Possible

Result :=CCBS_Not_

Possible

CCBSCall

Outcome :=Busy

CCBS_Call_Delivery(Outcome)

To VLR_CCBS_Recall_Manager

CCBSPossible

Check diagnostic associated with the busy cause value

MEsupportsCCBS

Initial result :=CCBS_Possible

Result :=CCBS_Possible

Initialresult

Cause = BusyorCause = No circuitchannel available

Result :=CCBS_Possible

Result :=CCBS_Not_

Possible

Yes

False

No

Yes

No

Yes

Yes

Yes

No

Yes

No

No

True

CCBS_Possible

Yes

No

CCBS_Not_Possible

No

Figure 11.1.1.5: Procedure CCBS_Check_If_CCBS_Possible

3GPP

3G TS 23.093 V3.0.0 (1999-05)523G TS 23.093 version 3.0.0

Procedure CCBS_Activation_MSC 1(2)

Signals to/from the leftare to/from the BSS;signals to/from the rightare to/from HLRunless marked otherwise

CCBS_Possible

Start T1

RR connectionmay be converted

to an SDCCH

Wait_For_CCBS_Request

CCBS_Request T1 Expiry

Internaltimer expiry

Releasetransaction

Stop T1Releasetransaction Stop T1

CCBS_Request

Clear StoredCall Information

Clear StoredCall Information

MSC AWait for CCBSRequest Ack

Figure 11.1.1.6: Procedure CCBS_Activation_MSC (sheet 1 of 2)

3GPP

3G TS 23.093 V3.0.0 (1999-05)533G TS 23.093 version 3.0.0

Procedure CCBS_Activation_MSC 2(2)

Signals to/from the leftare to/from the BSS;signals to/from the rightare to/from HLRunless marked otherwise

MSC AWait for CCBSRequest Ack

CCBSRequest_Ack

CCBSRequest_Error

Releasetransaction

Release(CCBSRequest Ack)

Release(CCBSError)

Releasetransaction

Releasetransaction

Figure 11.1.1.6: Procedure CCBS_Activation_MSC (sheet 2 of 2)

3GPP

3G TS 23.093 V3.0.0 (1999-05)543G TS 23.093 version 3.0.0

Procedure in the MSCto page an MS in aspecified location area

Procedure Page_MS_MSC_For_Recall PAGE_M1(2)

Signals to/from the leftare to/from the BSS; signals to/from the rightare to/from the VLRunless marked otherwise

Locationarea IDknown

MSconnection

existsDoes an RR connection exist

Regativeresponse:=

Unknown LAI

Set accessconnection

status

Start Pageresponse

timer

Page MS ForRecallnegativeresponse

Result:=Pass

In specified location area Page

Result:=Fail

Wait_For_Page_

Response

Yes

No

Yes

No

Figure 11.1.1.7: Procedure Page_MS_MSC_For_Recall (sheet 1 of 2)

3GPP

3G TS 23.093 V3.0.0 (1999-05)553G TS 23.093 version 3.0.0

Procedure in the MSCto page an MS in aspecified location area

Procedure Page_MS_MSC_For_Recall PAGE_M2(2)

Signals to/from the leftare to/from the BSS; signals to/from the rightare to/from the VLRunless marked otherwise

Wait_For_Page_

Response

MSconnectionestablished

Pageresponsetimer expired

CM ServiceRequest

For circuit-switched call

CM ServiceRequest

To process OCH_MSC

Negativeresponse:=

AbsentSubscriber

Negativeresponse:=

Busy Subscriber

Set accessconnection

status

Page MS ForRecallnegativeresponse

Page MS ForRecallnegativeresponse

Result:=Pass

Result:=Fail

Result:=Fail

Figure 11.1.1.7: Procedure Page_MS_MSC_For_Recall (sheet 2 of 2)

3GPP

3G TS 23.093 V3.0.0 (1999-05)563G TS 23.093 version 3.0.0

Procedure in the MSCto search for an MS (page in all location areas)

Procedure Search_For_MS_MSC_For_Recall 1(1)

Signals to/from the leftare to/from the BSS; signals to/from the rightare to/from the VLRunless marked otherwise

Does an RR connection existMS

connectionexists?

Start Pageresponse

timer

Set accessconnection

status

In alllocation areas Page

Result:=Pass

Wait_For_Search_Response

MSconnectionestablished

Pageresponsetimer expired

CM ServiceRequest

For circuit-switched call

Search_For_MSMSC_For_Recall_Ack

CM ServiceRequest

To GSM 03.18 Process OCH_MSC

Set negativeresponse:

AbsentSubscriber

Set negativeresponse:

Busy Subscriber

Set accessconnection

status

Search For MSMSC For Recall negativeresponse

Search For MSMSC For Recall negativeresponse

Result:=Pass

Result:=Fail

Result:=Fail

No

Yes

Figure 11.1.1.8: Procedure Search_For_MS_MSC_For_Recall

3GPP

3G TS 23.093 V3.0.0 (1999-05)573G TS 23.093 version 3.0.0

Procedure in the VLRto search for an MS (i.e. page in all location areas)

Procedure Search_For_MS_VLR_Recall 1(1)

Signals to/from the leftare to/from the MSC

Search_ For_MS_MSC_For_Recall

Wait_For_Search_Result

Search_For_MSMSC_For_Recall_Ack

Search_For_MSMSC_For_Recall negativeresponse

UpdateLocationArea ID

Transfer negativecause to the

parent process

Result:=Pass

Result:=Fail

Figure 11.1.1.9: Procedure Search_For_MS_VLR_Recall

3GPP

3G TS 23.093 V3.0.0 (1999-05)583G TS 23.093 version 3.0.0

Procedure Complete_Recall_MSC 1(2)

Signals to/from the leftare to/from the BSS;signals to/from the rightare to/from the VLRunless marked otherwise

CM_Serv_ Prompt

Wait_For_CM_Serv_Prompt_

Response

Releasetransaction

Connection_type_not_supported

Start_CC

Negativeresponse:=

Absentsubscriber

CCBS_Call_Info

Wait_For_Ack

IncompatibleTerminal

Release(UDUB)

Releasetransaction

CCBS_Call_Info_Confirmed

Negativeresponse:=Incompatible

Terminal

Negativeresponse:=

CComp Busy

Negativeresponse:=

Absentsubscriber

BasicServiceGroupof the CCBS_Call_Info= BasigServiceGroupreceived from HLR

Negativeresponse:=

IncompatibleTerminal

Complete_Recall_negative_Response

Result:=Fail

1

No

Yes

Figure 11.1.1.10: Procedure Complete_Recall_MSC (sheet 1 of 2)

3GPP

3G TS 23.093 V3.0.0 (1999-05)593G TS 23.093 version 3.0.0

Procedure Complete_Recall_MSC 2(2)

1

Early traficchannelallocation?

Establish_Originating_

TCH_If_Required

Refer GSM 03.18

Result =Pass

Negativeresponse:=

Radio_congestion

Complete_Recall_Ack

Complete_Recall_Ack

Complete_Recall_negative_Response

Result :=Pass

Result:=TCH_allocated

Result:=Fail

YesNo

N o

Yes

Figure 11.1.1.10: Procedure Complete_Recall_MSC (sheet 2 of 2)

3GPP

3G TS 23.093 V3.0.0 (1999-05)603G TS 23.093 version 3.0.0

Procedure CCBS_OCH_Report_Success 1(1)

CCBSCall

Reconnect

Outcome :=Success

To VLR_CCBS_Recall_Manager

CCBS CallDelivery(Outcome)

Clear storedcall information

Yes

No

False

True

Figure 11.1.1.11: Procedure CCBS_OCH_Report_Success

3GPP

3G TS 23.093 V3.0.0 (1999-05)613G TS 23.093 version 3.0.0

Procedure CCBS_OCH_Report_Failure 1(1)

CCBSCall

Reconnect

Outcome :=Failure

To VLR_CCBS_Recall_Manager

CCBS CallDelivery(Outcome)

Yes

No

False

True

Figure 11.1.1.12: Procedure CCBS_OCH_Report_Failure

3GPP

3G TS 23.093 V3.0.0 (1999-05)623G TS 23.093 version 3.0.0

11.1.2 Processes and procedures in HLR

Figure 11.1.2.1: Block diagram of HLRA processes

Figure 11.1.2.2: Process HLRA_Request_Manager

This process is in charge of the user interface procedures and queue handling, i.e. whether the request to processed ispresent in the queue or not.

The process has three states, "Idle", "Operative" and "Operative Resuming". In the "Idle" state the queue is empty andthe only actions to queue are creation of new request and interrogation of the queue. In other states activation,interrogation and deactivation procedures similarly, that is why they are grouped under "*" state.

Whenever the first request is created the process changes it’s state to "Operative", in this state there are request(s) inthe queue and none of them are suspended.

When HLRA_Request reports of suspension the process changes it’s state to "Operative Resuming" and theHLRA_Resume is started with correct trigger signal i.e. idle indication from MSC or recall end is waited.

Only NET suspended request can be selected and resumed, USER type suspended requests remain as suspended untilthem are marked as NET suspended. This happens when idle indication is received from the MSC.

The resuming process is paused if there is new suspended request with cause code Not reach i.e. The resuming startsagain when idle condition is met again or there is a new recall with successful outcome i.e. the recall ends without NotReach indication.

The resuming process will be stopped, if there are no suspended requests in the queue any more. The process changesit’s state to normal "Operative" or "Idle" state.

Figure 11.1.2.3: Process HLRA_Request

This process is created during the activation of service and contains all related data. The process has five differentstates, "Wait_For_Answer", "Active", "Recall", "Suspended" and "Frozen". During its creation the process sendsCCBS_Request via SSAP interface to destination network B containing all call related data as well originating networksretention capabilities.

In the "Wait_For_Answer" state process receives response from destination network which is further relayed to theHLRA_Request_Manager. In case of positive acknowledgement destination network returns info whether the retentionis supported in both networks.

In "Active" state process waits recall from destination network, however process can vanish if operation timer T3 expiresor explicit deletion is received from the user or destination network. In case of deletion the process informs the queue.When the recall arrives the process transits to the "Recall" state.

In the "Recall" state process waits the recall outcome, either positive or negative. Depending of the recall outcome therequest can be deleted, retained or suspended. If the request is to be retained the process transits back to the "Active"state. If the request is suspended due to the T10 expiry, CCBS_Busy condition or the MS is not reachable the processtransits to the suspended state.

If the request is deleted during "Recall" due SSAP_Cancel, T3 expiry or explicit deletion the queue is updatedimmediately and the request changes it’s state to "Recall Deleted" where it waits the recall to end.

In the "Suspended" state actions the request can be resumed if the MS is known to be CCBS_Idle or the request can bedeleted due to the explicit deletion or timer T3 expiry.

The request is placed in “Frozen” state whenever it receives Remote User Free indication from the destination networkand the request can’t be fulfilled due service interaction or lack of support in MSCVLR. The request shall indicatesuspended back to the destination network and stay in the queue. If the service becomes later possible, the request willrevert back “Active” state and indicate resumed to the destination network.

Figure 11.1.2.4: Process HLRA_Recall_Manager

This process has two different states, "Idle" and "CCBS_Busy".

3GPP

3G TS 23.093 V3.0.0 (1999-05)633G TS 23.093 version 3.0.0

The process let’s only one individual process to be in recall state in a time and have a dialogue open to the MSC and itchanges it’s state to "CCBS_Busy". In this state other requests are suspended immediately and marked as NETsuspended with cause code = Busy.

In "CCBS_Busy" state the process waits recall reporting from the MSC. Possible inputs from the MSC areCCBS_RUF_Ack, CCBS_RUF_Error and CCBS_Call_Report. CCBS_Call_Report can be received if the subscriber hasaccepted the recall, otherwise the process changes it’s state back to "Idle". If the process receives Query_State requestfrom the HLRA_Resume during the recall the process informs the resume process whether a recall is being processed.

Figure 11.1.2.5: Process HLRA_Resume

The process has four different states, "Idle", "Resume pending", "Wait For Selection" and "Resuming". The process isstarted when a request is suspended. For the first suspended request it is also set the trigger point i.e. when it is correctto send out selection request for resuming. Two triggers are provided, A_Idle from the monitoring process andRecall_End from the recall handling. If the trigger is set to A_Idle the monitoring process is also started.

When the process is started and correct trigger is set the process waits in the "Resume pending" state to receive apermission to start resuming. When the permission is received the process asks for the first NET request to resumed. IfA_Idle signal is received from the monitoring process the resuming process asks the queue manager to set all suspendedrequests as NET type in order to allow the selection.

When there are no active suspended request in the queue any more the resuming process is stopped i.e. when the"Deleted" signal in the HLRA_Request_Manager is handled.

Figure 11.1.2.6: Process HLRA_Monitoring

Monitoring process has two different states, "Idle" and "Monitoring". Receival of "A_Query" signal transits theprocess to "Monitoring" state. In this state the process reports "Idle" condition to the resuming process and starts themonitoring again in the MSC if location update or restore data happens.

Figure 11.1.2.7: Procedure HLRA_CCBS_Check_Interactions

This procedure checks whether the Remote User Free indication can be delivered to the MSCVLR or not.

3GPP

3G TS 23.093 V3.0.0 (1999-05)643G TS 23.093 version 3.0.0

Block HLRA_Processes 1(1)

HLRA_Request_Manager(1,1)

HLRA_Request(0,5)

HLRA_Resume(1,1)

HLRA_Monitoring(1,1)

HLRA_Recall_Manager(1,1)

VLRA

CCBS_Request_AckCCBS_Request_ErrorInterrogate_CCBS_AckDeactivate_CCBS_Ack

CCBS_RequestInterrogate_CCBSDeactivate_CCBS

ResumeDelete

CCBS_Request_AckCCBS_Request_ErrorSuspendDeleted

CCBS_RequestCCBS_SuspendCCBS_ResumeCCBS_Cancel

CCBS_Request_AckCCBS_Reject_RequestRemote_User_FreeCCBS_CancelCCBS_END

Destinationnetwork B

Recall

CompletedSuspendFailureBusy

Set_All_ActiveSelect_Active_ReqSelect_First_Req

Set_Trigger_Recall_EndSet_Trigger_A_IdleReset_Trigger_A_IdleSelect_RespNot_SelectedStop_Resume

Query_Status

RecallRecall_End

A_QueryStop_Monitoring

A_Idle

CCBS_Coordinator_HLR

CCBS_Call_Report

Start_ReportingStop_Reporting

Start_Reporting_AckEvent_Report

VLRA

CCBS_RUF_AckCCBS_RUF_Error

CCBS_RUF

Figure 11.1.2.1: HLRA Processes

NOTE: Figure 11.1.2.1 is one possible method of implementing queue processing in HLR A. Manufacturers are notconstrained to follow the implementation given in figure 11.1.2.1. However, the external behaviour ofHLR A shall appear to be the same.

3GPP

3G TS 23.093 V3.0.0 (1999-05)653G TS 23.093 version 3.0.0

Description of above signals:

Relation HLRA_Request_Manager and HLRA_Request

CCBS_Request_Ack signal is acknowledgement of a successful activation from the individual request to the queuemanager.

CCBS_Request_Error signal is sent if the destination networks queue is full or the destination networks queue size is setto zero. The individual request is deleted from the originating side.

Suspend is used within HLRA_Request and HLRA_Request_Manager. The queue shall update it’s internal information.

Delete is used within HLRA_Request_Manager and HLRA_Request. The queue manager instructs the individualrequest the request to die.

Deleted is used within HLRA_Request_Manager and HLRA_Request. The individual request informs the queue of itsexpiry.

Resume is used within HLRA_Request_Manager and HLRA_Request. The individual request is resumed and it shallinform the destination network of the resumption.

Relation HLRA_Request_Manager and HLRA_Resume

Set_Trigger_Recall_End is used within the HLRA_Request_Manager and HLRA_Resume. If resuming is not ongoingthis signal set the resuming process to the "ResumePending" state and query is sent to the recall process.

Set_Trigger_A_Idle is used within the HLRA_request_manager and HLRA_resume. If resuming is not ongoing thissignal set the resuming process to the "ResumePending" state. In all cases this causes "A_Query" signal to be sent.

Reset_Trigger_A_Idle is used within the HLRA_request_manager and HLRA_resume. This signal sets the resumingprocess to the "ResumePending" state and causes "A_Query" signal to be sent.

Select_Resp is used within the HLRA_request_manager and HLRA_resume. This signal informs the resuming process tostart T11.

Not_Selected is used within the HLRA_request_manager and HLRA_resume. This signal informs the resuming processthat the selection was not done and the process will transit to "ResumePending" state.

Stop_Resume is used within the HLRA_request_manager and HLRA_resume. This signal informs the resuming processto stop it’s actions and stop the monitoring also.

Set_All_Active is used within the HLRA_Resume and HLRA_request_manager. This signal informs the queue to set allsuspended requests as NET suspended and later on they can be resumed.

Select_Active_Req is used within the HLRA_Resume and HLRA_request_manager. This signal informs the queue toselect first NET suspended request to be resumed. If successful the request process will return "Select_Resp", otherwise"Not_Selected".

Select_First_Req is used within the HLRA_Resume and HLRA_request_manager. This signal informs the queue toselect first suspended request to be resumed. If successful the request process will return "Select_Resp", otherwise"Not_Selected".

3GPP

3G TS 23.093 V3.0.0 (1999-05)663G TS 23.093 version 3.0.0

Relation HLRA_Recall_Manager and HLRA_Request

Recall is used within HLRA_Request and HLRA_Recall_Manager. It contains all call related data in order to form theCCBS_Call.

Completed is used within the HLRA_Recall_Manager and HLRA_Request. It informs the request of successfulCCBS_Call and causes the request to vanish.

Failure is used within the HLRA_Recall_Manager and HLRA_Request. It informs the request of unsuccessfulCCBS_Call and causes the request to vanish.

Busy is used within the HLRA_Recall_Manager and HLRA_Request. It informs the request of unsuccessful CCBS_Calland causes the request to vanish if retention is not supported.

Suspend is used within HLRA_ Recall_Manager and HLRA_ Request. The request shall change it’s state and report thesuspension to the queue manager.

Relation HLRA_Monitoring and HLRA_Resume

A_Query is used within HLRA_Resume and HLRA_Monitoring. It instruct the HLRA_Monitoring to start it’s actionsand return the idle condition when possible.

A_Idle is used within HLRA_Monitoring and HLRA_Resume. It informs the resuming process that the subscriber is nowCCBS_Idle and not CCBS_Busy.

Stop_Monitoring is used with HLRA_Resume and HLRA_Monitoring. It instructs the monitoring process to stop it’sactions and stop the monitoring from VLR also.

Location_Update/Restore_Data events are tracked and external reporting is started again.

3GPP

3G TS 23.093 V3.0.0 (1999-05)673G TS 23.093 version 3.0.0

Process HLRA_RequestManager(1,1) 1(10)

IDLEThere is not any request in the IDLE state

CCBS_Request From MSCVLR

Check_Parameters

See GSM 03.18

IDLE Result

HLRA_Request

Error :=Negativeresponse

Update thequeue

CCBS_Request_Error(Error)

To MSCVLR

IDLE OPERATIVE IDLE

From MSC_VLRDeactivate_CCBS

See GSM 03.18 Check_Parameters

Result

CCBSprovisioned

Deactivate_Result :=

Not Provisioned

Deactivate_Result :=Success

Error :=Negativeresponse

To MSC_VLRDeactivate_CCBS_Ack(Deactivate_Result)

Deactivate_CCBSError(Error)

To MSCVLR

IDLE IDLE

Pass

Fail

Pass

Fail

No

Yes

Figure 11.1.2.2: Process HLRA_Request_Manager (sheet 1 of 10)

3GPP

3G TS 23.093 V3.0.0 (1999-05)683G TS 23.093 version 3.0.0

Process HLRA_RequestManager(1,1) 2(10)

*

Interrogate_CCBS

From MSC_VLR

Check_Parameters

See GSM 03.18

Result

Error :=Negativeresponse

CCBSprovisioned

To MSC_VLRInterrogate_CCBS_Ack(Error)

Queueempty

- Result :=No Entries

Query the queue :=

List

Result :=Not_Provisioned

Result := List

To MSC_VLRInterrogate_CCBS_Ack(Result)

To MSC_VLRInterrogate_CCBS_Ack(Result)

Interrogate_CCBS_Ack(Result)

To MSC_VLR

-

Fail

Pass

Yes

No

Yes

No

Figure 11.1.2.2: Process HLRA_Request_Manager (sheet 2 of 10)

3GPP

3G TS 23.093 V3.0.0 (1999-05)693G TS 23.093 version 3.0.0

Process HLRA_RequestManager(1,1) 3(10)

*(IDLE)

CCBS_Request_Ack

From HLRA_Request

CCBS _Request_Ack

To MSC_VLR

-There is at least onerequest in the queue

CCBS_Request_Error(Error)

From HLRA_Request

CCBS_Request_Error(Error)

To MSC_VLR

Update thequeue

Queueempty

IDLE

No

Yes

Figure 11.1.2.2: Process HLRA_Request_Manager (sheet 3 of 10)

3GPP

3G TS 23.093 V3.0.0 (1999-05)703G TS 23.093 version 3.0.0

Process HLRA_RequestManager(1,1) 4(10)

*(IDLE)

From MSCVLRCCBS_Request

See GSM 03.18Check_

Parameters

Result

Queuefull

Error :=Negativeresponse

Identicalrequest

Error :=Short_Term_

Denial

To HLRA_Request. The existing entryshould be deleted

Delete

Update thequeue To MSCVLR

CCBS_Request_Error(Error)

HLRA_Request

Update the queue

-

Pass

Fail

No

Yes

Yes

No

Figure 11.1.2.2: Process HLRA_Request_Manager (sheet 4 of 10)

3GPP

3G TS 23.093 V3.0.0 (1999-05)713G TS 23.093 version 3.0.0

Process HLRA_RequestManager(1,1) 5(10)

*(IDLE)

Suspend(Type,Sus_Cause)

From individualHLRA_Request

Type

Mark requestUSER

suspended

NOTE: USER suspendedrequests can't beselected until MSCVLRreports idle condition

Set_Trigger_A_Idle(Sus_Cause)

To HLRA_ResumeNOTE: Request canresumed when idlecondition is met

OPERATIVERESUMING

In this state thereis at least onesuspendedrequests

Mark requestNET

suspended

NOTE: NET suspendedrequests can beselected when Idle condition is met or Recall_Manager reportsRecall_End

Sus_Cause

Reset_Trigger_A_Idle(Sus_Cause)

To HLRA_ResumeNOTE: Resuming ispaused until idlecondition is met

Set_Trigger_Recall_End

To HLRA_ResumeNOTE: Resuming canbe started when recallis ended

USER

NET

Not_Reach

ELSE

Figure 11.1.2.2: Process HLRA_Request_Manager (sheet 5 of 10)

3GPP

3G TS 23.093 V3.0.0 (1999-05)723G TS 23.093 version 3.0.0

Process HLRA_RequestManager(1,1) 6(10)

OPERATIVE

Deactivate_CCBS From MSC_VLR

Check_Parameters

Result

Delete allrequests

Error :=Negativeresponse

Requestexists

To MSCVLRDeactivate_CCBSError(Error)

To individualHLRA_Request Delete Delete

To HLRA_RequestNOTE: To all individual requests

OPERATIVE

Result :=Success

Deactivate_CCBS_Ack(Result)

To MSC_VLR

Update thequeue

Queueempty

OPERATIVE IDLE

Pass

Fail

No

Yes

Yes

No

No

Yes

Figure 11.1.2.2: Process HLRA_Request_Manager (sheet 6 of 10)

3GPP

3G TS 23.093 V3.0.0 (1999-05)733G TS 23.093 version 3.0.0

Process HLRA_RequestManager(1,1) 7(10)

OPERATIVE

DeletedFrom individual HLRA_Request

Update therequest queue

Queueempty

OPERATIVE IDLE

No

Yes

Figure 11.1.2.2: Process HLRA_Request_Manager (sheet 7 of 10)

3GPP

3G TS 23.093 V3.0.0 (1999-05)743G TS 23.093 version 3.0.0

Process HLRA_RequestManager(1,1) 8(10)OPERATIVERESUMING

Deactivate_CCBS From MSC_VLR

Check_Parameters

See GSM 03.18

Result

Delete allrequests

Error :=Negativeresponse

Requestexists

To MSCVLRDeactivate_CCBSError(Error)

To individualHLRA_Request Delete Delete

To HLRA_RequestNOTE: To all individual requests

OPERATIVERESUMING

Result :=Success

Deactivate_CCBS_Ack(Result)

To MSC_VLR

Update thequeue

Anysuspended

requests

Stop_Resume

To HLRA_Resume

Queueempty

OPERATIVERESUMING OPERATIVE IDLE

Pass

Fail

No

Yes

Yes

No

No

Yes

No Yes

Figure 11.1.2.2: Process HLRA_Request_Manager (sheet 8 of 10)

3GPP

3G TS 23.093 V3.0.0 (1999-05)753G TS 23.093 version 3.0.0

Process HLRA_RequestManager(1,1) 9(10)

OPERATIVERESUMING

DeletedFrom individual HLRA_Request

Update therequest queue

Anysuspendedrequests

Stop_Resume

To HLRA_Resume

Queueempty

OPERATIVE IDLEOPERATIVERESUMING

No

No Yes

Yes

Figure 11.1.2.2: Process HLRA_Request_Manager (sheet 9 of 10)

3GPP

3G TS 23.093 V3.0.0 (1999-05)763G TS 23.093 version 3.0.0

Process HLRA_RequestManager(1,1) 10(10)

OPERATIVERESUMING

Set_All_Active

From HLRA_Resume

Mark all USER suspended requestsas NET suspended

OPERATIVERESUMING

Select_Active_Req

From HLRA_Resume

Any NETsuspendedrequest

Select the first NET suspended

request

Update queue,remove suspend

marking for request

ResumeTo individualHLRA_Request

Any moresuspendedrequests

Stop_Resume

To HLRA_Resume

OPERATIVE

Select_Resp

To HLRA_ResumeNOTE: T11 isstarted

Anysuspendedrequests

Not_Selected

To HLRA_ResumeNOTE: T11 is notstarted, Resumewaits A_Idle

OPERATIVERESUMING

Select_First_Req

From HLRA_Resume

Mark all USER suspended requestsas NET suspended

Yes

No

Yes

No

No

Yes

Figure 11.1.2.2: Process HLRA_Request_Manager (sheet 10 of 10)

3GPP

3G TS 23.093 V3.0.0 (1999-05)773G TS 23.093 version 3.0.0

Process HLRA_Request 1(5)

FPARAll the data in the originalCCBS_Request

Retainsupported

CCBS_Request(Retain_Supported)

To destination network B. NOTE: This signalcontains also info of originating network's retain capabilities.

WAIT_FOR_ANSWER

CCBS_Request

To destination network B. NOTE: This signaldoes not contain any information of theretain support.

WAIT_FOR_ANSWER

CCBS_Request_Ack(Retainsupported)

From destination network B. NOTE: Retain_supportedparameter contains info whether retain is supported for this request all alongthe network path. The parameter is received only if retain supported was sendin the CCBS_Request signal.

Store receivedRetain_supported

value

Start T3

CCBS_Request_Ack

To HLRA_Request_Manager

ACTIVE

CCBS_Reject_Request(Cause)

From destinationnetwork B

Error :=Cause

CCBS_Request_Error(Error)

To HLRA_Request_Manager

Yes No

Figure 11.1.2.3: Process HLRA_Request (sheet 1 of 5)

3GPP

3G TS 23.093 V3.0.0 (1999-05)783G TS 23.093 version 3.0.0

Process HLRA_Request 2(5)

ACTIVE

Remote_User_Free

From destinationnetwork B

HLRA_CCBS_CHECK_

INTERACTIONS

Result

RecallTo HLRA_Recall_Manager

RECALL

CCBS_Suspend

To destinationnetwork B

FROZEN

T3 Expiry

Cause :=T3-Timeout

CCBS_Cancel(Cause)

To destinationnetwork B

DeletedTo HLRA_Request_Manager

CCBS_Cancel

From destinationnetwork B

DeleteFrom HLRA_Request_Manager

CCBS_Cancel

To destinationnetwork B

Pass

Fail

Figure 11.1.2.3: Process HLRA_Request (sheet 2 of 5)

3GPP

3G TS 23.093 V3.0.0 (1999-05)793G TS 23.093 version 3.0.0

Process HLRA_Request 3(5)

RECALL

From HLRA_Recall_Manager

Completed BusyFrom HLRA_Recall_Manager

Failure(Cause)

From HLRA_Recall_Manager

Retain_supported Cause

Cause :=T4-Timeout

To destinationnetwork B

CCBS_Cancel(Cause)

CCBS_Cancel

To destinationnetwork B

To HLRA_Request_Manager

DeletedTo HLRA_Request_Manager

Deleted

ACTIVE

RECALL

From HLRA_Request_Manager

DeleteFrom destinationnetwork B

CCBS_Cancel

From destinationnetwork B

CCBS_END T3 Expiry

To destinationnetwork B

CCBS_Cancel Deleted

To HLRA_Request_Manager

False

True T4 exp

else

Figure 11.1.2.3: Process HLRA_Request (sheet 3 of 5)

3GPP

3G TS 23.093 V3.0.0 (1999-05)803G TS 23.093 version 3.0.0

Process HLRA_Request 4(5)

RECALL

Suspend(Type,Sus_Cause)

From HLRA_Recall_Manager

CCBS_Suspend

To destinationnetwork B

Suspend(Type,Sus_Cause)

To HLRA_Request_Manager

SUSPENDED

SUSPENDED

ResumeFrom HLRA_Request_Manager

CCBS_Resume

To destinationnetwork B

ACTIVE

T3 Expiry

Cause :=T3-Timeout

CCBS_Cancel(Cause)

To destinationnetwork B

DeletedTo HLRA_Request_Manager

CCBS_Cancel

From destinationnetwork B

DeleteFrom HLRA_Request_Manager

CCBS_Cancel

To destinationnetwork B

Figure 11.1.2.3: Process HLRA_Request (sheet 4 of 5)

3GPP

3G TS 23.093 V3.0.0 (1999-05)813G TS 23.093 version 3.0.0

Process HLRA_Request 5(5)

FROZEN

T3 Expiry

Cause :=T3-Timeout

CCBS_Cancel(Cause)

To destinationnetwork B

DeletedTo HLRA_Request_Manager

CCBS_Cancel

From destinationnetwork B

Location_Update

HLRA_CCBS_CHECK_

INTERACTIONS

Result

Type := NETSus_Cause :=

Temporary

Suspend(Type,Sus_Cause)

To HLRA_Request_ManagerNote: Allthough the requestcan be handled due theinteraction has been removedthe HLRA_Resume processis invoked in order to resumethe request in well organizedmanner.

SUSPENDEDFROZEN

FROZEN

DeleteFrom HLRA_Request_Manager

CCBS_Cancel

To destinationnetwork B

Pass

Fail

Figure 11.1.2.3: Process HLRA_Request (sheet 5 of 5)

3GPP

3G TS 23.093 V3.0.0 (1999-05)823G TS 23.093 version 3.0.0

Process HLRA_RecallManager 1(4)

IDLE

RecallFrom individualHLRA_Request

RecallTo HLRA_Resumeto stop T11

CCBS_RUFTo MSC_VLR

CCBS_BUSY

Query_Status

From HLRA_Resume

Recall_End To HLRA_Resume

IDLE

CCBS_BUSY

RecallFrom individualHLRA_Request

Type := NETSus_Cause

:= Busy

Suspend(Type,Sus_Cause)

To individualHLRA_Request

CCBS_BUSY

Figure 11.1.2.4: Process HLRA_Recall_Manager (sheet 1 of 4)

3GPP

3G TS 23.093 V3.0.0 (1999-05)833G TS 23.093 version 3.0.0

Process HLRA_RecallManager 2(4)

CCBS_BUSY

CCBS_RUF_Ack(Result)

From MSC_VLR

Result

Start T12

CCBS_BUSY

Cause :=Result

Failure(Cause)

To individualHLRA_Request

Recall_EndTo HLRA_Resume

IDLE

Type := USERSus_Cause

:= Busy

Suspend(Type,Sus_Cause)

To individualHLRA_Request

RUF Accepted

T4 expiryUDUB_IdleRUF Rejected

T10 expiryUDUB _Busy

Figure 11.1.2.4: Process HLRA_Recall_Manager (sheet 2 of 4)

3GPP

3G TS 23.093 V3.0.0 (1999-05)843G TS 23.093 version 3.0.0

Process HLRA_RecallManager 3(4)

CCBS_BUSY

T12 expiryCCBS_RUF_Error(Error)

From MSC_VLR

Close thecommunication

between HLR and VLRError

Cause :=Failure

Type := NETSus_Cause:= Not Reach

To individualHLRA_Request

Failure(Cause)

To individualHLRA_RequestNOTE: BecauseMS is not reachableresuming is not started

Suspend(Type,Sus_Cause)

To HLRA_Resume

Recall_End

IDLE

ELSE

IMSI DetachedRestricted AreaNo Page ResponseAbsent_SubscriberRadio FailureCComp Busy

Figure 11.1.2.4: Process HLRA_Recall_Manager (sheet 3 of 4)

3GPP

3G TS 23.093 V3.0.0 (1999-05)853G TS 23.093 version 3.0.0

Figure 11.1.2.4: Process HLRA_Recall_Manager (sheet 4 of 4)

Process HLRA_RecallManager 4(4)

CCBS_BUSY

From CCBS_Coordinator_HLR

CCBS_Call_Report(Outcome)

Stop T12

Outcome

Cause :=Failure

To individualHLRA_Request

Completed To individualHLRA_Request

Failure(Cause)

To individualHLRA_Request

Busy

To HLRA_Resume Recall_End

IDLE

Failure

Success Busy

3GPP

3G TS 23.093 V3.0.0 (1999-05)863G TS 23.093 version 3.0.0

Process HLRA_Resume 1(3)

*(IDLE) *

Stop_Resume

From HLRA_Request_Manager

Reset_Trigger_A_Idle(Sus_Cause)

From HLRA_Request_Manager. Note:The subscriber is not reachableand the possibly ongoing resumingis stopped until A_Idle input isreceived.

Stop_Monitoring

To HLRA_Monitoring

A_Query(Sus_Cause)

To HLRA_Monitoring

IDLE IDLERESUME_PENDING

*(IDLE)

Set_Trigger_A_Idle(Sus_Cause)

From HLRA_Request_Manager. Note:Suspended request was markedinactivate and needs A_Idle inputin order to be resumed. Ongoingresuming continues.

A_Query(Sus_Cause)

To HLRA_Monitoring

-

Figure 11.1.2.5: Process HLRA_Resume (sheet 1 of 3)

3GPP

3G TS 23.093 V3.0.0 (1999-05)873G TS 23.093 version 3.0.0

Process HLRA_Resume 2(3)

IDLE

Set_Trigger_A_Idle(Sus_Cause)

From HLRA_Request_Manager

A_QueryTo HLRA_Monitoring

RESUME_PENDING

Set_Trigger_Recall_End

From HLRA_Request_Manager

Query_Status

To HLRA_Recall_Manager

RESUME_PENDING

A_IdleFrom HLRA_Monitoring

Select_First_Req

To HLRA_Request_ManagerNOTE: All requests can be resumed

WAIT_FOR_SELECTION

Recall_End

From HLRA_Recall_Manager

Select_Active_Req

To HLRA_Request_Manager

Set_Trigger_Recall_End

From HLRA_Request_Manager

Query_Status

To HLRA_Recall_Manager

RESUME_PENDING

Figure 11.1.2.5: Process HLRA_Resume (sheet 2 of 3)

3GPP

3G TS 23.093 V3.0.0 (1999-05)883G TS 23.093 version 3.0.0

Process HLRA_Resume 3(3)

WAIT_FOR_SELECTION

Select_Resp

From HLRA_Request_Manager

Start_T11

RESUMING

A_IdleFrom HLRA_Monitoring Recall

From HLRA_Recall_Manager

Not_Selected

From HLRA_Request_Manager

RESUME_PENDING

RESUMING

T11 expiry

Select_Active_Req

To HLRA_Request_Manager

WAIT_FOR_SELECTION

A_IdleFrom HLRA_Monitoring

Set_All_Active

To HLRA_Request_Manager

-

RecallFrom HLRA_Recall_Manager

Stop T11

RESUMEPENDING

Figure 11.1.2.5: Process HLRA_Resume (sheet 3 of 3)

3GPP

3G TS 23.093 V3.0.0 (1999-05)893G TS 23.093 version 3.0.0

Process HLRA_Monitoring(1,1) 1(2)

Signals to / from left are to / fromCCBS_Coordinator_HLR unlessshown otherwise.Signals to / from right are to / fromHLRA_Resume uless shownotherwise

IDLE

IDLE

A_Query(Sus_Cause)

Start_Reporting

WAIT_FOR_ANSWER

*(IDLE)

Stop_Monitoring

Stop_Reporting

IDLE

WAIT_FOR_ANSWER

Event_Report(Status)

Status =CCBS_Idle

Sus_Cause= Nrc

NOTE: Using the previous historydata i.e. Sus_Cause value to preventany unnecessary signaling is onepossible implementation. Themanufacturer is allowed to use othertechnics to achieve efficient solution.

A_Idle

MONITORING

Yes

ELSE

Yes

No

Figure 11.1.2.6: Process HLRA_Monitoring (sheet 1 of 2)

3GPP

3G TS 23.093 V3.0.0 (1999-05)903G TS 23.093 version 3.0.0

Process HLRA_Monitoring(1,1) 2(2)

Signals to / from left are to / fromCCBS_Coordinator_HLR unlessshown otherwise.Signals to / from right are to / fromHLRA_Resume uless shownotherwise

MONITORING

Event_Report(status)

status

A_Idle

MONITORING

MONITORING

Location_Update

CCBSsupported in

VLR

A_Idle

IDLEMONITORING

CCBS_Idle

ELSE

Yes

No

Figure 11.1.2.6: Process HLRA_Monitoring (sheet 2 of 2)

3GPP

3G TS 23.093 V3.0.0 (1999-05)913G TS 23.093 version 3.0.0

Procedure HLRA_CCBS_Check_Interactions 1(1)

VLR areaknown

CCBS supportedin current MSCVLR

CAMEL invokedin the originalcall

CAMEL supportedin MSC

Result :=Pass

Result :=Pass

Result :=Fail

Yes

No

Yes

No

Yes

No

Yes

No

Figure 11.1.2.7: Procedure HLRA_CCBS_Check_Interactions

3GPP

3G TS 23.093 V3.0.0 (1999-05)923G TS 23.093 version 3.0.0

11.2 Destination Network Processes

11.2.1 Procedures in GMSC

Figure 11.2.1.1: Procedure CCBS_MT_GMSC_Check_CCBS_Call

This procedure checks from the IAM message whether the call is CCBS call. If that is the case the CCBS Call parameter isset to the Send Routeing Info message. This functionality shall be applied only to the initial call leg. The procedureinitialises also the CCBS Possible variable as True, the variable is accessible to all CCBS specific procedures in theGMSC.

Figure 11.2.1.2: Procedure CCBS_MT_GMSC_Check_CCBS_Indicators

This procedure sets the CCBS_Call indicator to the outgoing IAM message when needed. This functionality shall beapplied only to the initial call leg.

Figure 11.2.1.3: Procedure CCBS_MT_GMSC_Remove_Indicators_Store_FWT

This procedure removes CCBS_Call indicator from the forwarded IAM message and also stores the forwarding type. Italso checks whether subscriber B can be target of CCBS Requests and stores that information for later use.

Figure 11.2.1.4: Procedure CCBS_MT_GMSC_Remove_Indicators

This procedure removes CCBS_Call indicator from the outgoing IAM message. CCBS activation is not possible for thiscall because T-CSI modified destination address.

Figure 11.2.1.5: Procedure CCBS_MT_GMSC_Check_CCBS_Possible

This procedure contains the core logic to handle various interactions with CAMEL, OR and received Release messagecontent. The procedure alters CCBS specific global variable CCBS Target which controls setting of the diagnostic field inthe Release message towards the originating network.

Global variables Reconnect and Resume Call are specific to CAMEL and OR interaction respectively. They are initialisedand updated in the process MT_GMSC or MT_CF_MSC, refer to GSM 03.18.

3GPP

3G TS 23.093 V3.0.0 (1999-05)933G TS 23.093 version 3.0.0

Procedure CCBS_MT_GMSC_Check_CCBS_Call 1(1)

Reconnect = Trueor Resume Call = True

Test the indicatorin received IAMmessage

CCBS Call Indicator

= True

CCBS Callparameter

:= False

CCBS Callparameter :=

True

CCBS Callparameter :=

False

This global variable is specific to CCBS handling.It is set to True by default but indication form HLRor the first call leg's result may lead CCBS NotPossible case. This variable coverns the functionalityof the other CCBS specific procedures in GMSC

CCBS Possible:= True

No

Yes

No

Yes

Figure 11.2.1.1: Procedure CCBS_MT_GMSC_Check_CCBS_Call

3GPP

3G TS 23.093 V3.0.0 (1999-05)943G TS 23.093 version 3.0.0

Procedure CCBS_MT_GMSC_Check_CCBS_Indicators 1(1)

Reconnect = Trueor Resume Call = True

CCBS Call

Test the parameter receivedin SRI. If absent, False exitshal be taken.

Keep CCBS Call

indicator

Indicator to theoutgoing IAM message

CCBS CallIndicator :=

True

CCBS CallIndicator :=

False

CCBS CallIndicator :=

False

No

Yes

Yes

No

True

False

Figure 11.2.1.2: Procedure CCBS_MT_GMSC_Check_CCBS_Indicators

3GPP

3G TS 23.093 V3.0.0 (1999-05)953G TS 23.093 version 3.0.0

Procedure CCBS_MT_GMSC_Remove_Indicators_Store_FWT 1(1)

Reconnect = TrueorResume Call = True

Test the parameter receivedin SRI Ack. If absent Falseexit shall be taken

CCBS Target

FWD onBusy

CCBS is possible only whencall is forwarded on busy

ALter GMSC internalvariable. Default isTrue

CCBS Possible:= False

CCBS Call

RemoveCCBS Indicator

No

Yes

True

False

False

True

Yes

No

Figure 11.2.1.3: Procedure CCBS_MT_GMSC_Remove_Indicators_Store_FWT

3GPP

3G TS 23.093 V3.0.0 (1999-05)963G TS 23.093 version 3.0.0

Procedure CCBS_MT_GMSC_Remove_Indicators 1(1)

Reconnect = TrueorResume Call = True

CCBS Possible:= False

CCBS Call

RemoveCCBS Indicator

No

Yes

Yes

No

Figure 11.2.1.4: Procedure CCBS_MT_GMSC_Remove_Indicators

3GPP

3G TS 23.093 V3.0.0 (1999-05)973G TS 23.093 version 3.0.0

Procedure CCBS_MT_GMSC_Check_CCBS_Possible 1(1)

CCBSPossible

Test the GMSC internalvariable. Does the previous processingindicate that CCBS isnot possible?

Reconnect = TrueorResume Call = True

Forwardedcall

Cause = BusyorCause = No circuitchannel available

CCBS Target:= True

CCBS Target:= False

Receivedmessage

CCBS Targetparameter set

CCBS Possible:= False

CCBS Target:= False

CCBS Target:= True

CCBS Possiblediagnostic set

CCBS Possible:= False

Alter the GMSC internalvariable. CCBS activationis no longer possible

CCBS Target:= False

Alter the GMSC internalvariable. The variablecontrols setting of thediagnostic value

True

N o

Y e s

Yes

N o

No

Resume _Call_Handling

No

Yes

Release

No

Yes

Yes

False

Figure 11.2.1.5: Procedure CCBS_MT_GMSC_Check_CCBS_Possible

3GPP

3G TS 23.093 V3.0.0 (1999-05)983G TS 23.093 version 3.0.0

11.2.2 Processes and procedures in HLR

Figure 11.2.2.1: Block diagram of HLRB_processes

Figure 11.2.2.2: Process HLRB_Request_Manager

This process has the task of controlling the queue and determining whether requests to be processed are present in thequeue or not.

The process has two states "idle" and "active". In the "idle" state there are no "operative" requests in the queue i.e.there are only suspended requests or no requests at all. In the "active" state there is at least one "operative" request inthe queue which needs processing. A transition from "idle" to "active" will trigger this process to start the process"HLRB_Recall_Manager". Only a transition from "active" to "idle" will result in this process stopping the process"HLRB_Recall_Manager".

Figure 11.2.2.3: Process HLRB_Request

This process represents an individual CCBS request on the destination side. Reception of signals on the externalinterface (SSAP signalling) are handled by this process.

Retention is handled by this process. The individual request is informed by the Recall manager process about theoutcome of the CCBS Call. The individual request is in charge to decide on whether it will stay in the destination queue(retention) or not according to its data stored.

T7 expiry is controlled by the individual request in that way, that it remembers T7 expiry when it is the selected request(i.e. a CCBS Recall has been initiated for this request). The event is detected after the CCBS Recall when retention haskept the request in the queue.

Figure 11.2.2.4: Process HLRB_Recall Manager

This process is in charge of the recall handling. It is started and stopped by the process "HLRB_Request_Manager"depending on whether there are operative requests in the terminating queue or not.

As soon as this process is started, it will start the process "HLRB_Monitoring" and wait for a response from thisprocess. The response indicates that user B is idle guarded i.e. a CCBS Recall can be initiated. Hence, the process asksthe request manager for selection of an individual request from the terminating queue.

When an individual process is selected, the process initiates a CCBS Recall via the individual request (since the externalinterface is tied to the individual request), starts T9 and takes over control of the blocking function while waiting for theCCBS Call. Control of blocking is done by sending the signal "Recall_Block" to process "HLRB_Blocking".

While waiting for the outcome of the CCBS Call, the process will be informed either by the selected individual request inthe case of negative outcome (suspension or cancellation, both hidden to the process), or by process"HLRB_Monitoring" in the case the CCBS Call has reached the terminating PLMN.

Figure 11.2.2.5: Process HLRB_Monitoring

This process takes care of monitoring events received from MSC/VLR and detects potential conditions for initiating aCCBS Recall.

The process is controlled by the "HLRB_Recall_Manager" process which was formerly in charge of detecting the recallcondition.

When the process is started, it invokes the monitoring function in the MSC/VLR and awaits the first event report. Theprocess keeps track of the subscriber state changes by running a state machine which reflects the subscriber states.When there is a transition from subscriber state "not idle" to "idle", then T8 is started. As soon as T8 expires, theprocess changes state again in order to remember that the subscriber is now idle guarded and a recall could be initiated

Whether a CCBS Recall is initiated or not depends on whether the process "HLRB_Recall_Manager" has asked for thisinformation by sending a "B_Query" signal to the monitoring process. The process "HLRB_Monitoring" gives thisinformation only if the "B_Query" signal has been received. This is done by sending the signal "B_Guarded" to theRecall Manager and it is only done once per request. The monitoring process keeps track on whether a query wasreceived or not by appropriate state changes.

3GPP

3G TS 23.093 V3.0.0 (1999-05)993G TS 23.093 version 3.0.0

As the monitoring process is in charge for the idle guard function, it also controls the blocking of incoming calls duringthe idle guard time (T8). Hence, when the recall manager process has sent a "B_Query" (i.e. a CCBS request needs to beprocessed) then the monitoring process starts the corresponding blocking along with T8. The blocking is only stopped ifT8 does not expire. If T8 expires, then blocking is still needed for the following CCBS Recall. The responsibility forcontrolling the blocking (i.e. switching it off) is given to the recall manager process.

Figure 11.2.2.6: Process HLRB_Blocking

This process controls the CCBS Call delivery reporting when the processes are in the proper state. This means that thereporting functionality of the outcome of the CCBS Call is not blindly triggered whenever there is a terminating CCBSCall.

The process has three different states: "idle", "Blocking" and "Recall Blocking". The "Idle" state reflects the case whenblocking is disabled. In the "Blocking" state all incoming calls are blocked (e.g. while T8 is running). The "RecallBlocking" state allows one CCBS Call to pass, which will trigger the CCBS Call delivery reporting in the MSC/VLR via theGSM 03.18 process "SRI_HLR". When this happens, the process will automatically change back to state "Blocking" asno other CCBS Call is expected for now.

When the process has detected that destination B is idle, it will start the blocking. Hence, the blocking process willchange state to "Blocking". As soon as the process "HLRB_Recall_Manager" has initiated a CCBS Recall, it will cause astate change in the blocking process to state "Recall Blocking". When the CCBS Call is received, "result = OK"indication in signal "SRI_Received_Ack" will trigger the reporting mechanism for CCBS Call delivery via a PRN requestin the GSM 03.18 process "SRI_HLR"

Figure 11.2.2.7: Procedure HLRB_CCBS_Check_Interactions

This procedure checks whether the request is frozen due to the supplementary service interactions.

Figure 11.2.2.8: Procedure CCBS_Handling_HLR

This procedure is called during Send Routeing Info message handling in the HLR. If blocking is active only CCBS Callscan proceed, others will fail with busy or forward indication. For CCBS Call CCBS Call Indicator is set to the ProvideRoaming Number message.

Figure 11.2.2.9: Procedure CCBS_Report_PRN_Failure

This procedure is called if Provide Roaming Number returns an error. For CCBS call is then generated an internal callreport.

The handling of multiple requests in HLR B can be further clarified by the diagram shown in figure 11.2.2.1.

3GPP

3G TS 23.093 V3.0.0 (1999-05)1003G TS 23.093 version 3.0.0

Block HLRB_Processes 1(1)

HLRB_Request_Manager(1,1)

HLRB_Request(0,5)

Instances of processRequest can be createdby the process Request_Manager

HLRB_Recall_Manager(1,1)

HLRB_Blocking(1,1)

HLRB_Monitoring(1,1)

Originatingnetwork A

CCBS_Request_AckCCBS_Reject_Request

CCBS_Request

Start_Recall_ManagerStop_Recall_ManagerSelect_Request_Response

Select_Request

Selection_Req

Re-ActivatedDeletedInactive

Remote_User_FreeCCBS_CancelCCBS End

CCBS_ResumeCCBS_CancelCCBS_Suspend

Send_RUFRecall_Report

End

Start_BlockingRecall_Block

Start_MonitoringStop_MonitoringB_Query

Call_DeliveryB_Guarded

SRI_Received_Ack

SRI_ReceivedStart_ReportingStop_Reporting

Event_ReportCCBS_Call_Report

CCBS_Coordinator_HLR

Start_BlockingStop_Blocking

Location_Update

Figure 11.2.2.1: HLRB_Processes

3GPP

3G TS 23.093 V3.0.0 (1999-05)1013G TS 23.093 version 3.0.0

Description of above signals

Relation Originating Network and HLRB_Request_Manager

CCBS_Request: When the originating network attempts to activate CCBS, it sends a CCBS_Request message to HLRBRequest Manager.

CCBS_Request_Ack: When the HLRB_Request_Manager acknowledges the activation, it sends CCBS_Request Ack tooriginating network.

CCBS_Reject: If the HLRB_Request_Manager does not accept the activation attempt, it sends CCBS_Reject to theoriginating network indicating long term or short term denial.

Relation Originating Network and HLRB_Request

CCBS_Suspend: If the originating network suspends a CCBS Request, it sends CCBS_Suspend to HLRB Request.

CCBS_Resume: When a request that was suspended is now resumed, the originating network sends a CCBS_Resumemessage to HLRB Request.

CCBS Cancel: When a request is cancelled in the originating network, it sends a CCBS Cancel message to HLRBRequest.

Remote_User_Free: HLRB_Request sends Remote_User_Free to the originating network to inform the originatingnetwork that destination B is now idle.

CCBS_Cancel: If a CCBS Request is cancelled in the destination network, HLRB_Request sends CCBS_Cancel to theoriginating network.

TC_END: If a CCBS Call is successfully delivered to destination B, then HLRB_Request ends the dialogue with theoriginating network by sending a TC_END message.

Relation HLRB_Request_Manager and HLRB_Request

Selection_Request: Once destination B is idle guarded, then the HLRB_Request_Manager will select the first non-suspended request in the queue for processing by sending "Select_Request" to HLRB_Request.

Inactive: When a CCBS Request is either suspended or unselectable due to the supplementary service interaction,HLRB_Request informs HLRB_Request_Manager so that the queue status can be updated.

Re-Activated: When either a suspended CCBS Request is resumed or the supplementary service interaction with therequest ends, then HLRB_Request informs HLRB_Request_Manager so that the queue status can be updated.

Deleted: When a CCBS Request is cancelled, then HLRB_Request informs HLRB_Request_Manager so that the queuestatus can be updated.

Relation HLRB_Recall_Manager and HLRB_Blocking

Stop_Blocking: When the Recall manager process is stopped by the Request Manager process or the Recall managerreceives and ‘End’ signal from the Request manager, the Recall manager sends "Stop_Blocking" to HLRB_Blocking.

Recall_Block: When a "Send RUF" signal is sent to HLRB_Request, the HLRB_Recall_Manager also sends "RecallBlock" to HLRB_Blocking so that one CCBS Call can be delivered to destination B, but other normal incoming calls areblocked.

3GPP

3G TS 23.093 V3.0.0 (1999-05)1023G TS 23.093 version 3.0.0

Relation HLRB Recall_Manager and HLRB_Request_Manager

Select_Request: On reception of a "B_Guarded" signal, the Recall manager sends "Select_Request" to the Requestmanager. The Request manager then selects the first non-suspended request in the queue for processing.

Start_Recall_Manager: When a CCBS Request is successfully activated, the Request manager sends"Start_Recall_Manager" to HLRB_Recall_Manager which subsequently causes the recall manager process to start themonitoring process.

Stop_Recall_Manager: The Request manager can stop the Recall manager process by sending a"Stop_Recall_Manager" signal

Select_Request_Response: When the Request manager has selected a request for processing it sends a response to therecall manager causing the recall manager to initiate a CCBS Recall.

Relation HLRB_Recall_Manager and HLRB_Request

Send_RUF: The Recall manager requests the individual process to send a Remote User Free indication to the originatingnetwork by sending a "Send_RUF" signal to the individual process.

Recall_Report: The Recall manager informs the individual process of the result of processing a CCBS Recall by sending a"Recall Report" signal.

END: When a CCBS Request is suspended or cancelled the HLRB_Request process sends an "End" signal to the RecallManager process.

Relation HLRB_Recall_Manager and HLRB_Monitoring

Start_Monitoring: When the Recall manager process is started by the Request manager process, the Recall managersends "Start_Monitoring" to the HLRB_Monitoring process to request the status of destination B

Stop_Monitoring: When the Recall manager process is stopped by the Request manager process, the Recall managersends "Stop_Monitoring" to the HLRB_Monitoring process.

B_Query: HLRB_Recall_Manager requests the HLRB_monitoring process to get informed when destination B hasbecome idle guarded.

Relation HLRB_Monitoring and HLRB_Recall_Manager

B_Guarded: HLRB_Monitoring informs the HLRB_Recall_Manager that destination B has become idle guarded.

Call_Delivery: HLRB_Monitoring informs the HLRB_Recall_Manager about the delivery of the CCBS call.

3GPP

3G TS 23.093 V3.0.0 (1999-05)1033G TS 23.093 version 3.0.0

Process HLRB_RequestManager 1(3)

Signals to and from the leftare to and from the originatingnetwork unless specified otherwise

IdleIn this state there are either no CCBS Requestsin the queue or the queue contains only inactive(suspended or quiesent) requests

IdleCCBS_Request(Retain_supported)

Note: Retention informationmay be received in theCCBS Request. Refer to ETS 300 358

From HLRB_Request Re-Activated Deleted

From HLRB_Request

CCBS serviceprovisioned indestinationnetwork

Update requestqueue

Update requestqueue

Reason :=long term

denial

queuefull

HLRB_Request

Reason :=short term

denial

To HLRB_Recall_Manager

Start_Recall_Manager

Update requestqueue CCBS_Reject_

Request(Reason)

Retention supportedin the Destination Bnetwork

- Active -

Retain_supported:= False

CCBS_Request_Ack(Retain_supported)

NOTE: Retention informationmay be sent in the CCBS Request AckRefer to ETS 300 358

Store Retainsupported

To HLRB_Recall_Manager

Start_Recall_Manager

In this state, there isat least one active request

Active

No

Yes

No

Yes

No Yes

Figure 11.2.2.2: Process HLRB_REQUEST_MANAGER (sheet 1 of 3)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1043G TS 23.093 version 3.0.0

Process HLRB_RequestManager 2(3)

Active

Deleted From HLRB_Request

Update requestqueue

Queueempty

Only inactiverequests inqueue

Stop_Recall_Manger

To HLRB_Recall_Manager

Idle

Continue_Monitoring

To CCBS_Coordinator_HLR

-

Inactive From HLRB_Request

Update requestqueue

CCBS_Request(Retain_supported)

Note: Retention informationmay be received in theCCBS Request. Refer to ETS 300 358

queuefull

HLRB_Request

Update requestqueue

Retention supportedin the Destination Bnetwork

Retain_supported:= False

CCBS_Request_Ack(Retain_supported)

NOTE: Retention informationmay be sent in the CCBSRequest AckRefer to ETS 300 358

Store Retainsupported

Active

Reason :=short term

denial

CCBS_Reject_Request(Reason)

No

Yes

N o

Yes

No

No Yes

Yes

Figure 11.2.2.2: Process HLRB_REQUEST_MANAGER (sheet 2 of 3)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1053G TS 23.093 version 3.0.0

Process HLRB_RequestManager 3(3)

Active

Select_Request

From HLRB_Recall_Manager

Select the firstactive request

Selection_Request

To HLRB_Request

Select_Request_Response(Request)

To HLRB_Recall_Manager

-

Re-ActivatedFrom HLRB_request

Update requestqueue

Figure 11.2.2.2: Process HLRB_REQUEST_MANAGER (sheet 3 of 3)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1063G TS 23.093 version 3.0.0

Process HLRB_Request 1(6)

Signals to and from the leftare to and from the originatingnetwork unless specified otherwise

Start T7

Operative

Operative

From HLRB_Request_Manager

Selection_Request SS_Event

From Supplementaryservice handling indicatingthat service status has beenchanged

HLRB_CCBS_Check_

Interactions

Result

InactiveTo HLRB_Request_Manager

SelectedQuiescentOperative Operative

Fail

Pass

Figure 11.2.2.3: Process HLRB_REQUEST (sheet 1 of 6)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1073G TS 23.093 version 3.0.0

Process HLRB_Request 2(6)

*(Selected)

T7_Expiry

Reason :=T7_Expiry

CCBS_Cancel(Reason)

DeletedTo HLRB_Request_Manager

CCBS_Cancel

Figure 11.2.2.3: Process HLRB_REQUEST (sheet 2 of 6)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1083G TS 23.093 version 3.0.0

Process HLRB_Request 3(6)

Selected

Send_RUFFrom HLRB_Recall_Manager

CCBS_Suspend

CCBS_Cancel T7_Expiry SS_Event

From Supplementaryservice handling indicatingthat service status has beenchanged

To HLRB_Request_Manager Inactive Deleted

To HLRB_Request_Manager

Remote_User_Free

To HLRB_Recall_Manager End End

To HLRB_Recall_Manager

Stop T7

- Suspended

Figure 11.2.2.3: Process HLRB_REQUEST (sheet 3 of 6)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1093G TS 23.093 version 3.0.0

Process HLRB_Request 4(6)

Selected

Recall_Report(Outcome)

From HLRB_Recall_Manager

Outcome

Reason:=Outcome

Retainsupported

CCBS_Cancel

CCBSEnd

CCBS_Cancel(Reason)

Deleted To HLRB_Request_Manager

Operative

T9_Expiry

NDUB

Failure Success

False

True

Figure 11.2.2.3: Process HLRB_REQUEST (sheet 4 of 6)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1103G TS 23.093 version 3.0.0

Process HLRB_Request 5(6)

Suspended

CCBS_Resume SS_Event

From Supplementaryservice handling indicatingthat service status has beenchanged

To HLRB_Request_Manager Re-Activated

HLRB_CCBS_Check_

Interactions

Result

OperativeQuiescentSuspended Suspended

Fail

Pass

Figure 11.2.2.3: Process HLRB_REQUEST (sheet 5 of 6)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1113G TS 23.093 version 3.0.0

Process HLRB_Request 6(6)

QuiescentOperative

QuiescentSuspended

SS_Event From Supplementaryservice handling indicatingthat service status has beenchanged

SS_Event From Supplementaryservice handling indicatingthat service status has beenchanged

CCBS_Resume

HLRB_CCBS_Check_

Interactions

HLRB_CCBS_Check_

Interactions

Result Result

Re-ActivatedTo HLRB_Request_Manager

QuiescentOperative Operative

QuiescentSuspended Suspended

QuiescentOperative

Pass

Fail Fail

Pass

Figure 11.2.2.3: Process HLRB_REQUEST (sheet 6 of 6)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1123G TS 23.093 version 3.0.0

Process HLRB_RecallManager 1(3)

Idle

Idle

Start_Recall_Manager

From HLRB_Request_Manager

Start_Monitoring

To HLRB_Monitoring

B_QueryTo HLRB_Monitoring

Wait_For_B_Guarded

Wait_For_B_Guarded

B_GuardedFrom HLRB_Monitoring

Select_Request

To HLRB_Request_Manager

Wait_For_Selection_Request

Stop_Recall_Manager

From HLRB_Request_Manager

Stop_Monitoring

To HLRB_Monitoring

Stop_Blocking

To HLRB_Blocking

Idle

Figure 11.2.2.4: Process HLRB_RECALL_MANAGER (sheet 1 of 3)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1133G TS 23.093 version 3.0.0

Process HLRB_RecallManager 2(3)

Wait_For_Selectio_Response

Select_Request_Response(Request)

From HLRB_Request_Manager

Send_RUFTo HLRB_Request

Recall_Block

To HLRB_Blocking

Start T9

Wait_For_CCBS_Call

Stop_RecallManager

From HLRB_Request_Manager

Stop_Monitoring

To HLRB_Monitoring

Stop_Blocking

To HLRB_Blocking

Idle

Figure 11.2.2.4: Process HLRB_RECALL_MANAGER (sheet 2 of 3)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1143G TS 23.093 version 3.0.0

Process HLRB_RecallManager 3(3)

Wait_For_CCBS_Call

EndFrom HLRB_Request

Stop T9

Stop_Blocking

To HLRB_Blocking

B_QueryTo HLRB_Monitoring

Wait_For_B_Guarded

Call_Delivery(Outcome)

From HLRB_Monitoring orCCBS_Report_PRN_Failure

Stop T9

Recall_Report(Outcome)

To HLRB_Request

T9 Expiry

Outcome :=T9 Expiry

Stop_Recall_Manager

From HLRB_Request_Manager

Stop T9

Stop_Monitoring

To HLRB_Monitoring

Stop_Blocking

To HLRB_Blocking

Idle

Figure 11.2.2.4: Process HLRB_RECALL_MANAGER (sheet 3 of 3)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1153G TS 23.093 version 3.0.0

Process HLRB_Monitoring 1(7)

Idle

Idle

Start_Monitoring

From HLRB_Recall_Manager

CCBSsupported in

VLR

Start_Reporting

Wait

To CCBS_Coordinator_HLR

Yes

No

Figure 11.2.2.5: Process HLRB_MONITORING (sheet 1 of 7)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1163G TS 23.093 version 3.0.0

Process HLRB_Monitoring 2(7)

Wait

Event_Report(Status)

From CCBS_Coordinator_HLR B_Query

From HLRB_Recall_Manager

Stop_Monitoring

From HLRB_Recall_Manager

StatusStop_Reporting

To CCBS_Coordinator_HLR

Start T8

Start_Blocking To HLRB_Blocking

B_Not_IdleNo_B_Query

B_IdleNo_B_Query Idle

Wait

From CCBS_Coordinator_HLR Location Update

CCBS supportedin the MSCVLR

Start_Reporting

To CCBS_Coordinator_HLR

-

CCBS_Idle

CCBS_Not_IdleCCBS_Not_Reachable

Yes

No

Figure 11.2.2.5: Process HLRB_MONITORING (sheet 2 of 7)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1173G TS 23.093 version 3.0.0

Process HLRB_Monitoring 3(7)

B_Not_IdleNo_B_Query

Event_Report(Status)

Status

Start T8

Start_BlockingTo HLRB_Blocking

B_IdleNo_B_Query-

B_QueryFrom HLRB_Recall_Manager

B_Not_IdleB_Query

Stop_Monitoring

From HLRB_Recall_Manager

Stop_Reporting

Idle

B_Not_IdleNo_B_Query

CCBS_Call_Report(Outcome,Status)

Call_Delivery(Outcome)

To HLRB_Recall_Manager

Status

-B_Idle

No_B_Query

Location Update

CCBS supportedin the MSCVLR

Start_Reporting

-

From CCBS_Coordinator_HLR

To CCBS_Coordinator_HLR

From CCBS_Coordinator_HLR

To CCBS_Coordinator_HLR

From CCBS_Coordinator_HLR

CCBS_Idle

CCBS_Not_IdleCCBS_Not_Reachable

CCBS_Not_IdleCCBS_Not_Reachable

CCBS_Idle

Yes

No

Figure 11.2.2.5: Process HLRB_MONITORING (sheet 3 of 7)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1183G TS 23.093 version 3.0.0

Process HLRB_Monitoring 4(7)

B_Not_IdleB_Query

Event_Report(Status)

From CCBS_Coordinator_HLR

Stop_Monitoring

From HLRB_Recall_Manager

StatusStop_Reporting

To CCBS_Coordinator_HLR

Start T8

Start_Blocking

To HLRB_Blocking

-B_Idle

B_Query Idle

B_Not_IdleB_Query

From CCBS_Coordinator_HLR Location Update

CCBS supportedin the MSCVLR

Start_Reporting

To CCBS_Coordinator_HLR

-

CCBS_Idle

CCBS_Not_IdleCCBS_Not_Reachable

Yes

No

Figure 11.2.2.5: Process HLRB_MONITORING (sheet 4 of 7)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1193G TS 23.093 version 3.0.0

Process HLRB_Monitoring 5(7)

B_IdleNo_B_Query

Event_Report(Status)

From CCBS_Coordinator_HLR T8 Expiry B_Query

From HLRB_Recall_Manager

Stop_Monitoring

From HLRB_Recall_Manager

Status Stop T8

Stop_Blocking

To HLRB_Blocking

Stop_Reporting

To CCBS_Coordinator_HLR

B_Not_IdleNo_B_Query -

B_Idle_GuardedNo_B_Query

B_IdleB_Query Idle

B_IdleNo_B_Query

CCBS_Call_Report(Outcome,Status)

From CCBS_Coordinator_HLR

From CCBS_Coordinator_HLR Location Update

CCBS supportedin the MSCVLRCall_

Delivery(Outcome)

To HLRB_Recall_Manager

Stop T8

StatusTo HLRB_Blocking

Stop_Blocking

Start_Reporting

To CCBS_Coordinator_HLR

-B_Not_Idle

No_B_QueryB_Not_Idle

No_B_Query -

CCBS_Not_IdleCCBS_Not_Reachable

CCBS_Idle

No

Yes

CCBS_Idle

CCBS_Not_IdleCCBS_Not_Reachable

Figure 11.2.2.5: Process HLRB_MONITORING (sheet 5 of 7)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1203G TS 23.093 version 3.0.0

Process HLRB_Monitoring 6(7)

B_IdleB_Query

Event_Report(Status)

From CCBS_Coordinator_HLR T8 Expiry

Stop_Monitoring

From HLRB_Recall_Manager

Status Stop T8

Stop T8Stop_Blocking

To HLRB_Blocking

To HLRB_Blocking

Stop_Blocking B_Guarded

To HLRB_Recall_Manager

Stop_Reporting

To CCBS_Coordinator_HLR

-B_Not_IdleB_Query

B_Idle_GuardedNo_B_Query Idle

B_IdleB_Query

CCBS_Call_Report(Outcome,Status)

From CCBS_Coordinator_HLR

From CCBS_Coordinator_HLR Location Update

CCBS supportedin the MSCVLRCall_

Delivery(Outcome)

To HLRB_Recall_Manager

Stop T8

StatusTo HLRB_Blocking

Stop_Blocking

Start_Reporting

To CCBS_Coordinator_HLR

-B_Not_IdleB_Query

B_Not_IdleB_Query

B_IdleB_Query

CCBS_Not_IdleCCBS_Not_Reachable

CCBS_Idle

No

Yes

CCBS_Idle

CCBS_Not_IdleCCBS_Not_Reachable

Figure 11.2.2.5: Process HLRB_MONITORING (sheet 6 of 7)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1213G TS 23.093 version 3.0.0

Process HLRB_Monitoring 7(7)

B_Idle_GuardedNo_B_Query

Event_Report(Status)

From CCBS_Coordinator_HLR B_Query

From HLRB_Recall_Manager

Stop_Monitoring

From HLRB_Recall_Manager

StatusStart_Blocking

To HLRB_Blocking

Start T8 B_GuardedTo HLRB_Recall_Manager

Stop_Reporting

To CCBS_Coordinator_HLR

B_Not_IdleNo_B_Query

B_IdleNo_B_Query - Idle

B_Idle_GuardedNo_B_Query

CCBS_Call_Report(Outcome,Status)

From CCBS_Coordinator_HLR

From CCBS_Coordinator_HLR Location Update

Call_Delivery(Outcome)

To HLRB_Recall_Manager

CCBS supportedin the MSCVLR

Start_Reporting

To CCBS_Coordinator_HLR

Status

-B_Not_Idle

No_B_QueryB_Not_Idle

No_B_Query

CCBS_Idle

CCBS_Not_IdleCCBS_Not_Reachable

Yes

No

CCBS_Idle

CCBS_Not_IdleCCBS_Not_Reachable

Figure 11.2.2.5: Process HLRB_MONITORING (sheet 7 of 7)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1223G TS 23.093 version 3.0.0

Process HLRB_BLOCKING 1(3)

*

Stop_Blocking

From HLRB_Recall_Manager orHLRB_Monitoring

Idle Idle

Idle

SRI_Received From GSM 03.18SRI_HLR(CCBS_Handling_HLR)

Start_Blocking

From HLRB_Monitoring

Result := OK

SRI_Received_Ack(Result)

To GSM 03.18SRI_HLR(CCBS_Handling_HLR)

- Blocking

Figure 11.2.2.6: Process HLRB_BLOCKING (sheet 1 of 3)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1233G TS 23.093 version 3.0.0

Process HLRB_BLOCKING 2(3)

Blocking

SRI_Received

From GSM 03.18SRI_HLR (CCBS_Handling_HLR)

CFBActive forthis BS

Max Noof forwardings

reached

max queue size > 0and CCBS supportedin the VMSC

CCBS Target:= True

Set the valueto the SRIresponse

Result := Forward

SRI_Received_Ack(Result,CCBS Target)

To GSM 03.18SRI_HLR(CCBS_Handling_HLR)

-

CCBS Target:= False

Result := Fail

max queue size > 0and CCBS supportedin the VMSC

Result := Busy,CCBS Possible

Result := Busy,CCBS Not Possible

Recall_Block

From HLRB_Recall_Manager

RecallBlocking

Stop Blocking From HLRB_Monitoring

Idle

Yes

No

Yes

No

Yes

No

Y e s

No

Figure 11.2.2.6: Process HLRB_BLOCKING (sheet 2 of 3)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1243G TS 23.093 version 3.0.0

Process HLRB_BLOCKING 3(3)

RecallBlocking

From GSM 03.18SRI_HLR(CCBS_Handling_HLR)

SRI_Received

CCBSCall

CFBActive & Operative

for this BS

Max Noof forwardings

reached

CCBSsupported in

VMSC

max queue size > 0and CCBS supportedin the VMSC

Keep CCBS CallIndicator :=

False

Keep CCBS CallIndicator :=

True

Set the valueto the SRIresponse

CCBS Target:= True

CCBS Target:= False

max queue size > 0and CCBS supportedin the VMSC

Result := Forward Result := FailResult := Busy,

CCBS Not PossibleResult := Busy,CCBS Possible Result := OK

SRI_Received_Ack(Result)

To GSM 03.18SRI_HLR(CCBS_Handling_HLR)

To GSM 03.18SRI_HLR(CCBS_Handling_HLR)

SRI_Received_Ack(Result)

RecallBlocking Blocking

No

Yes

Yes

No

No

Yes

N o

Yes

Yes

No

No

Yes

Figure 11.2.2.6: Process HLRB_BLOCKING (sheet 3 of 3)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1253G TS 23.093 version 3.0.0

Procedure HLRB_CCBS_Check_Interactions 1(1)

CFU active &operative forthe request

BAIC active &operative forthe request

BIC-Roam active & operative forthe request

Result :=Pass

Result :=Fail

No

Yes

No

Yes

No

Yes

Figure 11.2.2.7: Procedure HLRB_Check_Interactions

3GPP

3G TS 23.093 V3.0.0 (1999-05)1263G TS 23.093 version 3.0.0

Procedure CCBS_Handling_HLR 1(1)

SRI_Received To HLRB_Blocking

Wait ForAnswer

SRI_Received_Ack (Result) From HLRB_Blocking

Result

CCBS CallSet neg.respForwarding

violation

Set neg.respBusy

subscriber

Set ForwardingInfo

Set CCBS CallIndicator in PRN

Set resultFrom resultcode receivedin SRI_Received _Ack

OK

Fail

Busy Forward

Yes

No

Figure 11.2.2.8: Procedure CCBS_Handling_HLR

3GPP

3G TS 23.093 V3.0.0 (1999-05)1273G TS 23.093 version 3.0.0

Procedure CCBS_Report_PRN_Failure 1(1)

CCBS call

Outcome :=Failure

Call_Delivery(Outcome)

To HLRB_Recall_Manager

Yes

No

Figure 11.2.2.9: Procedure CCBS_Report_PRN_Failure

3GPP

3G TS 23.093 V3.0.0 (1999-05)1283G TS 23.093 version 3.0.0

11.2.3 Procedures in MSC/VLR

Figure 11.2.3.1: Procedure CCBS_MT_MSC_Check_Forwarding

This procedure is called to set the CCBS Target variable. That variable is used in later phase to set the correct diagnosticvalue to the Release message.

Figure 11.2.3.2: Procedure CCBS_Handle_PRN

This procedure is called to store CCBS call indicator when roaming number is reserved in the VLR.

Figure 11.2.3.3: Procedure CCBS_ICH_Set_CCBS_Call_Indicator

This procedure is called when VLR receives Send Info For Incoming Call message. If MSRN is related to the CCBS call,CCBS call indicator is set for call handling.

Figure 11.2.3.4: Procedure CCBS_ICH_MSC_Report_Failure

This procedure is called when CCBS call fails in the destination MSC and the reason is detected in the MSC side.

Figure 11.2.3.5: Procedure CCBS_ICH_VLR_Report_Failure

This procedure is called when CCBS call fails in the destination MSC and the reason is detected in the VLR side.

Figure 11.2.3.6: Procedure CCBS_ICH_Report_Not_Reachable

This procedure is called when call fails in the destination MSC with special cause of Not_Reachable. On normal callNot_Reachable message is sent to the monitoring process, on CCBS call subscriber is reported being absent.

Figure 11.2.3.7: Procedure CCBS_ICH_Handle_NDUB

This procedure is called when call encounters NDUB condition in the destination MSC. It is a network option to forwardthe call or release the call.

Figure 11.2.3.8: Procedure CCBS_ICH_Handle_UDUB

This procedure is called when call encounters UDUB condition in the destination MSC.

Figure 11.2.3.9: Procedure CCBS_ICH_MSC_Report_Success

This procedure is called when CCBS call is successfully delivered in the destination MSC and the event is detected inthe MSC side.

Figure 11.2.3.10: Procedure CCBS_ICH_VLR_Report_Success

This procedure is called when CCBS call is successfully delivered in the destination MSC and the event is detected inthe VLR side.

Figure 11.2.3.11: Procedure CCBS_ICH_Set_CCBS_Target

This procedure is called if when a call encounters busy condition in the destination MSC. If busy cause is NDUB and theuser has elected to be target of CCBS requests, CCBS Target is set to True.

3GPP

3G TS 23.093 V3.0.0 (1999-05)1293G TS 23.093 version 3.0.0

Procedure CCBS_MT_MSC_Check_Forwarding 1(1)

CCBStarget

Parameter is set when SIFIC_Ackis received fromVLR

Cause = BusyorCause = No circuitchannel available

CCBS Target:= True

Alter the internal variablewhich controls setting ofthe diagnostic field

CCBS Target:= False

True

Yes

No

False

Figure 11.2.3.1: Procedure CCBS_MT_MSC_Check_Forwarding

3GPP

3G TS 23.093 V3.0.0 (1999-05)1303G TS 23.093 version 3.0.0

Procedure CCBS_Handle_PRN 1(1)

Store CCBS Callindicator alongwith the MSRN

Figure 11.2.3.2: Procedure CCBS_Handle_PRN

3GPP

3G TS 23.093 V3.0.0 (1999-05)1313G TS 23.093 version 3.0.0

Procedure CCBS_ICH_Set_CCBS_Call_Indicator 1(1)

MSRN for CCBS_Call

To CCBS_Monitoring_VLR CCBS_Call

Indicator :=CCBS_Call

Yes

No

Figure 11.2.3.3: Procedure CCBS_ICH_Set_CCBS_Call_Indicator

3GPP

3G TS 23.093 V3.0.0 (1999-05)1323G TS 23.093 version 3.0.0

Procedure CCBS_ICH_MSC_Report_Failure 1(1)

CCBS Call

Outcome :=Failure

CCBS_Call_Delivery(Outcome)

To CCBS_Monitoring_VLR

Yes

No

Figure 11.2.3.4: Procedure CCBS_ICH_MSC_Report_Failure

3GPP

3G TS 23.093 V3.0.0 (1999-05)1333G TS 23.093 version 3.0.0

Procedure CCBS_ICH_VLR_Report_Failure 1(1)

CCBS Call

Outcome :=Failure

CCBS_Call_Delivery(Outcome)

To CCBS_Monitoring_VLR

Yes

No

Figure 11.2.3.5: Procedure CCBS_ICH_VLR_Report_Failure

3GPP

3G TS 23.093 V3.0.0 (1999-05)1343G TS 23.093 version 3.0.0

Procedure CCBS_ICH_Report_Not_Reachable 1(1)

CCBS Call

Outcome :=Absent Subscriber

CCBS_Call_Delivery(Outcome)

To CCBS_Monitoring_VLRNot_Reachable

To CCBS_Monitoring_VLR

Yes

No

Figure 11.2.3.6: Procedure CCBS_ICH_Report_Not_Reachable

3GPP

3G TS 23.093 V3.0.0 (1999-05)1353G TS 23.093 version 3.0.0

Procedure CCBS_ICH_Handle_NDUB 1(1)

Busy condition :=NDUB

CCBS Call

Network option:Release or forward

Outcome :=Failure

Outcome :=NDUB

To CCBS_Monitoring_VLR

CCBS_Call_Delivery(Outcome)

CCBS_Call_Delivery(Outcome)

To CCBS_Monitoring_VLR

Result :=Forward

Result :=Release

Yes

No

Forward Release

Figure 11.2.3.7: Procedure CCBS_ICH_Handle_NDUB

3GPP

3G TS 23.093 V3.0.0 (1999-05)1363G TS 23.093 version 3.0.0

Procedure CCBS_ICH_Handle_UDUB 1(1)

Busy condition :=UDUB

Figure 11.2.3.8: Procedure CCBS_ICH_Handle_UDUB

3GPP

3G TS 23.093 V3.0.0 (1999-05)1373G TS 23.093 version 3.0.0

Procedure CCBS_ICH_MSC_Report_Success 1(1)

CCBS_Call

Outcome :=Success

CCBS_Call_Delivery(Outcome)

To CCBS_Monitoring_VLR

Yes

No

Figure 11.2.3.9: Procedure CCBS_ICH_MSC_Report_Success

3GPP

3G TS 23.093 V3.0.0 (1999-05)1383G TS 23.093 version 3.0.0

Procedure CCBS_ICH_VLR_Report_Success 1(1)

CCBS_Call

Outcome :=Success

CCBS_Call_Delivery(Outcome)

To CCBS_Monitoring_VLR

Yes

No

Figure 11.2.3.10: Procedure CCBS_ICH_VLR_Report_Success

3GPP

3G TS 23.093 V3.0.0 (1999-05)1393G TS 23.093 version 3.0.0

Procedure CCBS_ICH_Set_CCBS_Target 1(1)

Busy condition

Has destination B electedto be a target of requests

CCBSAllowed

CCBS Target := True

CCBS Target:= False

NDUB

UDUB

Yes

No

Figure 11.2.3.11: Procedure CCBS_ICH_Set_CCBS_Target

3GPP

3G TS 23.093 V3.0.0 (1999-05)1403G TS 23.093 version 3.0.0

11.3 Processes and procedures common in originating anddestination network entities

Figure 11.3.1: Process CCBS_Monitoring_VLR

This process is responsible for monitoring the subscriber in VLR and also controls the MSC monitoring process.

Figure 11.3.2: Process CCBS_Monitoring_MSC

This process is responsible for monitoring subscriber in MSC.

Figure 11.3.3: Process CCBS_Coordinator_HLR

This process co-ordinates HLRA and HLRB monitoring interaction. Start and Stop Reporting messages are sent onlyonce towards MSC, CCBS_Call_Report messages are directed to correct queue and Status information is distributed toboth queues when needed.

Figure 11.3.4: Procedure CCBS_Set_Diagnostic_For_Release

This procedure is called to set the diagnostic field to the Release message. The diagnostic is set according to the internalCCBS Target variable.

Figure 11.3.5: Procedure CCBS_Report_Not_Idle

This procedure is called when either MO or MT setup is received or sent to the MS. It informs the VLR monitoringprocess that the MS is engaged with a call.

Figure 11.3.6: Procedure CCBS_Report_MS_Activity

This procedure is called when Process_Access_Request is successfully performed. It informs the VLR monitoringprocess and may cause transition to the Idle state.

Figure 11.3.7: Procedure CCBS_Check_Last_Call

This procedure is called when a call is ending. If the call is the last CC connection to the MS, that is reported to the VLRmonitoring process.

3GPP

3G TS 23.093 V3.0.0 (1999-05)1413G TS 23.093 version 3.0.0

Process CCBS_MONITORING_VLR 1(4)

Signals to / from left are to / from HLR unless shown otherwise

Idle

Start_Reporting

Check_Parameters

See GSM 03.18

Result

Event_Reporting:= True

Error :=Negativeresponse

IMSIDetached

Start_Reporting_Error(Error)

Idle

Roaming inLA allowed

Status :=CCBS_Not_Reachable

Start_Status_Enquiry

To CCBS_Monitoring_MSC

Start_Reporting_Ack(Status)

Wait_For_Response

MonitoringDetached

Status_EnquiryResult

From CCBS_Monitoring_MSC

CCBS_Not_Idle

Status :=CCBS_Not_Idle

Status :=CCBS_Idle

Start_Reporting_Ack(Status)

Start_Reporting_Ack(Status)

MonitoringNot Idle

MonitoringIdle

Pass

Fail

No

Y e s

N o

Yes

Yes

No

Figure 11.3.1: Process CCBS_Monitoring_VLR (sheet 1 of 4)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1423G TS 23.093 version 3.0.0

Process CCBS_MONITORING_VLR 2(4)

Signals to / from left are to / from HLR unless shown otherwise

MonitoringNot Idle

From GSM 03.18 Processes OCH_MSCor ICH_MSC

Call_End DetachRadioFailure

Status :=CCBS_Idle

Event_Reporting

Event_Report(Status)

MonitoringIdle

MonitoringDetached

MonitoringDetached

From GSM 03.18 Processes OCH_MSCor ICH_MSCFrom GSM 03.93 Process MSC_CCBS_Recall_Manager

Not_IdleLocation_Update

MS_ActivityFrom GSM 03.18 Process_Access_Request_VLR

MonitoringNot_Idle

CMServType

Status :=CCBS_Idle

Event_Reporting

Event_Report(Status)

MonitoringIdle -

True

False

SMSSS

CSC

True

False

Figure 11.3.1: Process CCBS_Monitoring_VLR (sheet 2 of 4)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1433G TS 23.093 version 3.0.0

Process CCBS_MONITORING_VLR 3(4)

Signals to / from left are to / from HLR unless shown otherwise

MonitoringIdle

Not_IdleFrom GSM 03.18 Processes OCH_MSCor ICH_MSCFrom GSM 03.93 Process MSC_CCBS_Recall_Manager

Status :=CCBS_Not_

Idle

Event_Reporting

Event_Report(Status)

MonitoringNot Idle

RadioFailure

Status :=CCBS_Not_Reachable

Event_Reporting

Event_Report(Status)

MonitoringDetached

NotReachable

From GSM 03.18 ProcessICH_VLR or VLR_CCBS_Recall_Manager

Detach

*(Idle)

Continue_Monitoring

-

CCBS_CallFrom GSM 03.18 Process ICH_VLR

Event_Reporting:= False

True

False

True

False

Figure 11.3.1: Process CCBS_Monitoring_VLR (sheet 3 of 4)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1443G TS 23.093 version 3.0.0

Process CCBS_MONITORING_VLR 4(4)

Signals to / from left are to / from HLR unless shown otherwise

Note: Only MT CCBS Callreporting is interacting withthe monitoring process. MOcall reporting is shown onVLR_CCBS_Recall_Manager

*(Idle)

Cancel_Location

From subscriberdatahandling in VLR

Stop_Status_Enquiry

To CCBS_Monitoring_MSC

Idle

Event_Report_Error

CCBS_Call_Report_Error

Stop_Reporting

*(Idle,Wait_For_Response)

CCBS_Call_Delivery(Outcome)

From GSM 03.18 ProcessesICH_MSC or ICH_VLR

Event_Reporting:= True

Outcome

Mode := BStatus := CCBS_Not_Reachable

Outcome :=Failure

CCBS_Call_Report(Mode,Outcome,Status)

MonitoringDetached

Mode := B

Derive status fromthe current process

state

CCBS_Call_Report(Mode,Outcome,Status)

-

Mode := BStatus := CCBS_

Not_Idle

CCBS_Call_Report(Mode,Outcome,Status)

MonitoringNot Idle

Absent_Subscriber

Failure

SuccessNDUB

Figure 11.3.1: Process CCBS_Monitoring_VLR (sheet 4 of 4)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1453G TS 23.093 version 3.0.0

Process CCBS_MONITORING_MSC 1(1)

Signals to/from the leftare to/from the VLR;signals to/from the rightare to/from the BSSunless marked otherwise

Idle

Start_Status_Enquiry

From CCBS_Monitoring_VLR

CCBS Not Idle

Status :=CCBS Not idle

Status :=CCBS Idle

Status_Enquiry_Result

To CCBS_Monitoring_VLR

Monitoring

From CCBS_Monitoring_VLRStop_Status_Enquiry

RadioLink Failure

RadioFailure

Idle -

Yes

No

Figure 11.3.2: Process CCBS_Monitoring_MSC

3GPP

3G TS 23.093 V3.0.0 (1999-05)1463G TS 23.093 version 3.0.0

Process CCBS_Coordinator_HLR 1(6)

Signals to / from leftare to / from the VLRunless shownotherwise

Idle

From HLRA_Monitoring

Start_Reporting

From HLRB_Monitoring

Start_Reporting

CCBS_Call_Report(Mode,Outcome,Status)

Note: CCBS_Call_Reportcan exist on A side withoutongoing monitoring in the MSC

Check_Parameters See GSM 03.18

Result

ModeError:=

Negativeresponse

To HLRA_Recall_Manager

CCBS_Call_Report(Outcome)

Start_Reporting

Start_Reporting

CCBS_Call_Report_Ack

CCBS_Call_Report_Error(Error)

MonitoringA

MonitoringB - -

*

From subscriberdatahandling inHLR

Location_Update

Continue_Monitoring

From HLRB_Request_Manager

To HLRA_Monitoring

Location_Update

Continue_Monitoring

To HLRB_Monitoring

Location_Update

Idle -

Pass

Fail

A

B

Figure 11.3.3: Process CCBS_Coordinator_HLR (sheet 1 of 6)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1473G TS 23.093 version 3.0.0

Process CCBS_Coordinator_HLR 2(6)

Signals to / from leftare to / from the VLRunless shownotherwise

MonitoringA

CCBS_Call_Report(Mode,Outcome,Status)

Note: CCBS_Call_Reportcan exist on A side withoutongoing monitoring in the MSC

Stop_Reporting

From HLRA_Monitoring

See GSM 03.18Check_

ParametersStop_Reporting

Result Idle

Mode

CCBS_Call_Report(Outcome)

To HLRA_Recall_Manager

Error :=Negativeresponse

MonitoringACCBS_Call_

Report_Error(Error)

CCBS_Call_Report_Ack

Start_Reporting_Error(Error)

Event_Report(Status)

-

See GSM 03.18 Check_Parameters

Result

Error :=Negativeresponse

Event_Report_Error(Error)

Event_Report_Ack

Status :=Not_Reachable Store Status

Event_Report(Status)

-

Pass

Fail

A

B

Fail

Pass

Figure 11.3.3: Process CCBS_Coordinator_HLR (sheet 2 of 6)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1483G TS 23.093 version 3.0.0

Process CCBS_Coordinator_HLR 3(6)

Signals to / from leftare to / from the VLRunless shownotherwise

MonitoringA

Start_Reporting_Ack(Status)

Store Status

Event_Report(Status)

To HLRA_Monitoring

-

Start_Reporting

From HLRB_Monitoring

Statusavailable

Event_Report(Status)

To HLRB_Monitoring

MonitoringA + B

Restore_Data

From subscriberdatahandling inHLR

Start_Reporting

-

MonitoringB

Start_Reporting

From HLRA_Monitoring

Statusavailable

EventReport(Status)

To HLRA_Monitoring

MonitoringA + B

Restore_Data

From subscriberdatahandling inHLR

Start_Reporting

-

Yes

No

Yes

No

Figure 11.3.3: Process CCBS_Coordinator_HLR (sheet 3 of 6)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1493G TS 23.093 version 3.0.0

Process CCBS_Coordinator_HLR 4(6)

Signals to / from leftare to / from the VLRunless shownotherwise

MonitoringB

Start_Reporting_Ack(Status)

Start_Reporting_Error

From HLRB_Monitoring

Stop_Reporting

Store StatusStatus :=

Not_Reachable

To HLRB_Monitoring

Event_Report(Status)

Stop_Reporting

- Idle

MonitoringB

Event_Report(Status)

CCBS_Call_Report(Mode,Outcome,Status)

Check_Parameters

See GSM 03.18 Check_Parameters

See GSM 03.18

Result Result

Error :=Negativeresponse

Store StatusError :=Negativeresponse

CCBS_CallReport_Error(Error)

CCBS_Call_Report_AckEvent_

Report_Ack

Event_Report_Error(Error)

Outcome := FailureStatus :=

Not_reachableStatus :=Not_Reachable

Mode

To HLRB_Monitoring

Event_Report(Status)

To HLRA_Recall_Manager

CCBS_Call_Report(Outcome)

CCBS_Call_Report(Outcome,Status)

To HLRB_Monitoring

Store Status

-

Pass

Fail Fail

Pass

A

B

Figure 11.3.3: Process CCBS_Coordinator_HLR (sheet 4 of 6)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1503G TS 23.093 version 3.0.0

Process CCBS_Coordinator_HLR 5(6)

Signals to / from leftare to / from the VLRunless shownotherwise

MonitoringA + B

Event_Report(Status)

Start_Reporting_Ack(Status)

Start_Reporting_Error

CCBS_Call_Report(Mode,Outcome,Status)

Check_Parameters

Status :=Not_Reachable

Check_Parameters

Result Result

Error :=Negativeresponse

Error :=Negativeresponse

Event_Report_Ack CCBS_Call_

Report_Ack

CCBS_Call_Report_Error(Error)

Event_Report_Error(Error) Outcome:=Failure

Status :=Not_Reachable

Status :=Not_Reachable

Mode

Event_Report(Status)

To HLRB_Monitoring

Event_Report(Status)

To HLRA_Monitoring

To HLRB_Monitoring

CCBS_Call_Report(Outcome,Status)

MonitoringA + B

Event_Report(Status)

To HLRB_Monitoring

Event_Report(Status)

To HLRA_Monitoring

Store StatusTo HLRA_Recall_Manager

CCBS_Call_Report(Outcome)

-

Fail

Pass Fail

Pass

B

A

Figure 11.3.3: Process CCBS_Coordinator_HLR (sheet 5 of 6)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1513G TS 23.093 version 3.0.0

Process CCBS_Coordinator_HLR 6(6)

Signals to / from leftare to / from the VLRunless shownotherwise

MonitoringA + B

Stop_Reporting

From HLRA_Monitoring

MonitoringB

Stop_Reporting

From HLRB_Monitoring

MonitoringA

Restore_Data

From subscriberdatahandling inHLR

Start_Reporting

-

Figure 11.3.3: Process CCBS_Coordinator_HLR (sheet 6 of 6)

3GPP

3G TS 23.093 V3.0.0 (1999-05)1523G TS 23.093 version 3.0.0

Procedure CCBS_Set_Diagnostic_For_Release 1(1)

Is the conditions suchthat the subscriber canbe target of CCBSRequests

CCBSTarget

Diagnostic :=CCBS Possible

Diagnostic :=CCBS Not Possible

True

False

Figure 11.3.4: Procedure CCBS_Set_Diagnostic_For_Release

3GPP

3G TS 23.093 V3.0.0 (1999-05)1533G TS 23.093 version 3.0.0

Procedure CCBS_Report_Not_Idle 1(1)

Not_Idle To CCBS_Monitoring_VLR

Figure 11.3.5: Procedure CCBS_Report_Not_Idle

3GPP

3G TS 23.093 V3.0.0 (1999-05)1543G TS 23.093 version 3.0.0

Procedure CCBS_Report_MS_Activity 1(1)

Reason:=CM SERV TYPE

MS Activity To CCBS_Monitoring_VLR

Figure 11.3.6: Procedure CCBS_Report_MS_Activity

3GPP

3G TS 23.093 V3.0.0 (1999-05)1553G TS 23.093 version 3.0.0

Procedure CCBS_Check_Last_Call 1(1)

Last CCconnection

Call End To CCBS_Monitoring_VLR

Yes

No

Figure 11.3.7: Procedure CCBS_Check_Last_Call

3GPP

3G TS 23.093 V3.0.0 (1999-05)1563G TS 23.093 version 3.0.0

12 Information stored in the HLRsNote that a given subscriber may be both the originator and the target of CCBS requests; a given HLR may therefore berequired to store both the data for HLR A and the data for HLR B against a given subscriber.

12.1 Originating Network DataThe following logical states are applicable for the CCBS service in the originating network (refer to GSM 03.11 for anexplanation of the notation):

Provisioning State Registration State Activation State HLR Induction State

(Not Provisioned, Not Applicable, Not Active, Not Induced)

(Provisioned, Not Applicable, Active and Operative Not Induced)

The logical state shall be on a per subscriber basis and hence the same for all basic service groups.

The HLR shall store the logical state of the CCBS service (which shall be one of the valid states listed above) on a persubscriber basis. The HLR shall store the following information for each CCBS Request that is successfully activated bysubscriber A:

- AddressOfB;

- Basic Service Group;

- CCBS Call Information;

- Translated Number;

- Retention supported by destination network (if HLR A supports retention);

- CCBS Index;

- CAMEL Invoked.

The HLR shall store for the served subscriber as the originator of CCBS requests:

- The parameter “Max Queue Size”,

- This parameter takes a value in the range 1 to 5.

3GPP

3G TS 23.093 V3.0.0 (1999-05)1573G TS 23.093 version 3.0.0

12.2 Destination Network DataThe following logical states are applicable for the CCBS service in the destination network (refer to GSM 03.11 for anexplanation of the notation):

Provisioning State Registration State Activation State HLR Induction State

(Not Provisioned, Not Applicable, Not Active, Not Induced)

(Provisioned, Not Applicable, Active and Operative, Not Induced)

The logical state shall be on a per subscriber basis and hence the same for all basic service groups.

The HLR shall store the logical state of the CCBS service (which shall be one of the valid states listed above) on a persubscriber basis.

The HLR shall store the following information for each CCBS Request that is successfully activated against User B :

- Basic Service Group;

- Retention supported by originating network (if HLR B supports retention).

The HLR shall store on a per subscriber basis:

The parameter "Number of terminating CCBS Requests"

This parameter takes a value in the range 1 to 5.

12.3 Transfer of information from HLR to VLRIf the provisioning state for CCBS supplementary service is "Provisioned" then, when the subscriber registers on a VLR,the HLR shall send that VLR information about the logical state of CCBS supplementary service.

If the logical state of CCBS supplementary service is changed while a subscriber is registered on a VLR, then the HLRshall inform the VLR of the new logical state of CCBS supplementary service.

Both originating and destination network CCBS supplementary service logical states are updated independently of eachother to the VLR.

3GPP

3G TS 23.093 V3.0.0 (1999-05)1583G TS 23.093 version 3.0.0

13 State transition model

13.1 State transition model for the CCBS service in the originatingnetwork

Figure 13.1.1 shows the successful cases of transition between the applicable logical states of the CCBS service in theoriginating network. The state changes may be caused by actions of the service provider or the network.

Not Provisioned

Not Applicable

Not Active

Not Induced

Provisioned

Not Applicable

Active and Operative

Not Induced

Provision

Withdrawal

Figure 13.1.1: State Transition Model for CCBS Service in the originating network

13.2 State transition model for the CCBS service in thedestination network

Figure 13.2.1 shows the successful cases of transition between the applicable logical states of the CCBS service in thedestination network. The state changes may be caused by actions of the service provider or the network.

Not Provisioned

Not Applicable

Not Active

Not Induced

Provisioned

Not Applicable

Active and Operative

Not Induced

Provision

Withdrawal

Figure 13.2.1: State Transition Model for CCBS Service in the destination network

3GPP

3G TS 23.093 V3.0.0 (1999-05)1593G TS 23.093 version 3.0.0

13.3 State transition model for a CCBS RequestFigure 13.3.1 shows the successful cases of transition between the applicable logical states of a CCBS Request. Thestate changes may be caused by actions of the served subscriber or the network.

Each subscriber can be considered to have a set of n requests, where n is the maximum number of CCBS requestsallowed for a subscriber as an originator.

Start

Active

Recall

Suspend

CCBS Request

CCBS Cancel

CCBS Recall

CCBS Suspend

CCBS Resume

CCBS Cancel

CCBS Cancel

CCBS Complete

Figure 13.3.1: State Transition Model for a CCBS Request in Originating Network

On provision of the CCBS service, all requests transit to the "Start" state

3GPP

3G TS 23.093 V3.0.0 (1999-05)1603G TS 23.093 version 3.0.0

Start

Active & Operative

Recall

Suspend

CCBS Request

CCBS Cancel

CCBS Recall CCBS Suspend

CCBS Resume

CCBS Cancel

CCBS Cancel

CCBS Complete

Active & Quiescent

Suspend & Quiescent

CCBS Cancel

SS Int

SS Int

CCBS ResumeSS Int

SS Int

CCBS Cancel

Figure 13.3.2: State Transition Model for a CCBS Request in Destination Network

13.4 Information stored in the VLRsOriginating Network Data

For the CCBS service in the originating network the VLR shall store the service state information received from HLR.

Destination Network Data

For the CCBS service in the destination network the VLR shall store the service state information received from HLR.

3GPP

3G TS 23.093 V3.0.0 (1999-05)1613G TS 23.093 version 3.0.0

Annex A (Informative):Message flow diagrams showing a successful CCBSrequestThe following message flow diagrams show a successful CCBS request. Destination B busy when request activated,subscriber A free when destination B becomes free (mobile-to-mobile).

3GPP

3G TS 23.093 V3.0.0 (1999-05)1623G TS 23.093 version 3.0.0

OC

H_M

SC

HL

RA

HL

RB

MT

_GM

SC

ICH

_MS

CIC

H_V

LR

MS

VL

RM

SC

MS

C /

VL

RG

MS

CM

S

Set

-up

Initi

al A

ddre

ss M

essa

ge

Rel

ease

Initi

al A

ddre

ss M

essa

ge

Rel

ease

(CC

BS

Pos

sibl

e)

SIF

IC

SIF

IC N

eg

(ND

UB

)

OP

ER

ATI

VE

CC

BS

Pos

s.

CC

BS

Req

uest

CC

BS

Req

uest

Sta

rts H

LRA

_R

eque

stS

tart

s H

LRB

_R

eque

stC

CB

S R

eque

st

CC

BS

Req

uest

Ack

Sta

rt_R

ecal

l_M

anag

er

IDLE

IDLE

AC

TIV

E

WA

IT_F

OR

B_G

UA

RD

ED

IDLE

CC

BS

_M

on

ito

rin

g_

MS

C

CC

BS

_M

on

ito

rin

g_

VLR

WA

IT

Sta

rt_

Mon

itorin

g

B_Q

uery

Sta

rt_R

epor

ting

Sta

rt_S

tatu

sE

nqui

ry

Sta

tus

Enq

uiry

Res

ult

(Not

Idle

)

MO

NIT

OR

ING

MO

NIT

OR

ING

,N

OT

IDLE

Eve

nt_R

epor

t (C

CB

S N

ot Id

le)

B_N

OT

_ID

LEN

O_B

_QU

ER

Y

B_Q

UE

RY

B_N

OT

_ID

LEB

_QU

ER

Y

CC

BS

_Req

Ack

OP

ER

AT

IVE

OP

ER

AT

IVE

AC

TIV

E

WA

IT_F

OR

AN

SW

ER

IDLE

CC

BS

_Req

uest

_Ack

Rel

ease

(CC

BS

Ack

)

HL

RB

_M

on

ito

rin

g

HL

RB

_R

ecal

l_M

anag

er

HL

RB

_R

eque

st_

Man

ager

HL

RB

_R

eque

st

HLR

A_

Req

ues

t_M

anag

er

HL

RA

_R

eque

st

ICH

_MS

C

MO

NIT

OR

ING

,ID

LE

IDL

E

Cal

l End

Eve

nt_R

epor

t (C

CB

S_I

dle)

CC

BS

_C

heck

_La

st_C

all

Sta

rt_B

lock

ing

T8

Exp

iry

B_I

DLE

B_Q

UE

RY

B_G

uard

ed

B_I

DLE

_GU

AR

DE

DN

O_B

_QU

ER

YW

AIT

_FO

R_

SE

LEC

TIO

N_

RE

SP

ON

SE

SE

LEC

TED

AC

TIV

E

Sel

ect_

Req

uest

Sel

ectio

n_R

eq

Sel

ect_

Req

uest

_Res

pons

e

Sen

d_R

UF

Rec

all B

lock

Rem

ote

Use

r Fre

e

SE

LEC

TED

BLO

CK

ING

RE

CA

LL_

BLO

CK

ING

WA

IT_F

OR

_C

CB

S_C

ALL

HL

RB

_B

lock

ing

Ψ

Sta

rt T

8

CC

BS

_C

oo

rdin

ato

r_H

LR

Mon

itorin

g B

Mon

itorin

g B

Mon

itorin

g B

Eve

nt_R

epor

t(C

CB

S_I

dle)

Eve

nt_R

epor

tA

ck

Sta

rt_R

epor

ting_

Ack

Sta

rt_

Rep

ortin

g

3GPP

3G TS 23.093 V3.0.0 (1999-05)1633G TS 23.093 version 3.0.0

Rec

all_

Rep

ort

(suc

cess

)

MS

Con

nect

ion

esta

blis

hed

If Q

em

pty:

If ha

ve s

uspe

nded

requ

ests

:

Els

e::

IDLE

MT_

GM

SC

MS

C_C

CB

S_

Rec

all_

Man

ager

VL

R_C

CB

S_

Rec

all_

Man

ager

Rec

all

RE

CA

LL

CC

BS

_BU

SY

CC

BS

_RU

FP

age_

MS

_F

or_R

ecal

lPa

ge

Pro

cess

Acc

ess

Req

uest

CM

_Ser

vice

_P

rom

ptS

tart

CC

CC

BS

_Cal

l_In

foC

CB

S_C

all_

Info

_Ack

Com

plet

e_R

ecal

l_A

ck

Com

plet

eRec

all

Rec

all

Rec

all

CC

BS

_Set

upR

ecal

l_A

ckC

CB

S_R

UF_

Ack

(acc

ept)

CC

BS

_BU

SY

WA

IT_F

OR

_C

ALL

_DE

LIV

ER

Y

OG

_Cal

l_S

etup

_MS

C:

O

CH

_CC

BS

_VL

RS

IFO

C

Com

plet

eC

all

Cal

l P

roce

edin

g

Initi

al A

ddre

ss M

essa

ge

Add

ress

Com

plet

e , A

nsw

er /

Con

nect

Con

nect

Ack

CC

BS

Cal

lD

eliv

ery

(suc

cess

)

WA

IT_F

OR

_C

LEA

R

VL

R_C

CB

S_

Rec

all_

Man

ager

IDLE

ICH

_MS

CIC

H_V

LR

SIF

IC

IDLE

Initi

al A

ddre

ss

Suc

cess

ful

Cal

l

WA

IT_F

OR

_C

LEA

R

IDLE

Rel

ease

Add

ress

Com

plet

e , A

nsw

er /

Con

nect

WA

IT_F

OR

_C

LEA

R

HL

RB

_M

on

ito

rin

gH

LR

B_

Rec

all_

Man

ager

HL

RB

_R

equ

est_

Man

ager

HL

RB

_R

eque

st

CC

BS

_Cal

lD

eliv

ery

(su

cces

s)

Cal

l Del

iver

y(s

ucce

ss)

If Q

is

empt

y :

Sto

p_R

ecal

l_M

anag

er

CC

BS

_EN

D

Del

eted

IDLE

IDLE

IDLE

AC

TIV

ES

ELE

CTE

DR

EC

ALL

_B

LOC

KIN

GW

AIT

_FO

R_

CC

BS

_CA

LL

IDLE

HL

RB

_B

lock

ing

Sto

p B

lock

ing

Sto

p B

lock

ing

Sto

pM

onito

ring

Sto

p_R

epor

ting

CC

BS

_M

onito

ring

_M

SC

CC

BS

_M

onito

ring

_V

LR

MO

NIT

OR

ING

MO

NIT

OR

ING

,ID

LE Sto

p S

tatu

sE

nqui

ry

IDLE

IDLE

IDLE

Sto

p B

lock

ing

ICH

_MS

C

IDLE

Rel

ease

IDLE

OP

ER

ATI

VE

IDLE

CC

BS

_Cal

l_R

epor

t (M

odeA

, suc

cess

)

Del

eted

Com

plet

ed

IDLE

OP

ER

ATI

VE

Rel

ease

Rel

ease

OP

ER

ATI

VE

RE

SU

MIN

G

WA

IT_F

OR

_C

ALL

_DE

LIV

ER

Y

B_I

DLE

_GU

AR

DE

DN

O_B

_QU

ER

Y

B_I

DLE

_GU

AR

DE

DN

O_B

_QU

ER

Y

B_Q

uery

WA

IT_F

OR

B_G

UA

RD

ED

Sta

rt B

lock

ing

B_G

uard

edS

elec

t_R

eque

st(G

o to

Ψ)

B_I

DLE

_GU

AR

DE

DN

O_B

_QU

ER

YW

AIT

_FO

R_

SE

LEC

TIO

N_

RE

SP

ON

SE

IDLE

BLO

CK

ING

HL

RA

_R

ecal

l_M

anag

er

HL

RA

_R

equ

est_

Man

ager

HL

RA

_R

eque

st

CC

BS

_Cal

l_R

epor

t

CC

BS

_Cal

l_R

epor

t Ack

CC

BS

_C

oo

rdin

ato

r_H

LR

Mon

itorin

g B

CC

BS

_C

oo

rdin

ato

r_H

LR

IDLE

CC

BS

_Cal

l_R

epor

t (su

cces

s)C

CB

S_C

all

Rep

ort

(su

cces

s)

IDLE

Sto

p_R

epor

ting

Mon

itorin

g B

3GPP

3G TS 23.093 V3.0.0 (1999-05)1643G TS 23.093 version 3.0.0

Annex A:Change history

Change historyTSG CN# Spec Version CR <Phase> New Version Subject/CommentApr 1999 GSM 03.93 6.2.0 Transferred to 3GPP CN1CN#03 23.093 3.0.0 Approved at CN#03

3GPP

3G TS 23.093 V3.0.0 (1999-05)1653G TS 23.093 version 3.0.0

History

Document history

V3.0.0 May 1999 Approved at TSGN #3. Under TSG TSG CN Change Control.