committee.tta.or.kr INS ID abc de f_:M S_0 01M S_0 1 I N S I D a b c d e f _: M S _ 0 0 1 M S _ 0 0...
Transcript of committee.tta.or.kr INS ID abc de f_:M S_0 01M S_0 1 I N S I D a b c d e f _: M S _ 0 0 1 M S _ 0 0...
T T
A S
t a n
d a
r d
정보통신단체표준(기술규격) 제정일: 2018 년 월
TTAT.3G-23.093(R14-14.0.0)
3GPP-(Technical Speciation
Group Technical realization of
Completion of Calls to Busy
Subscriber (CCBS); Stage 2 )
본 문서에 대한 저작권은 TTA에 있으며, TTA와 사전 협의 없이 이 문서의
전체 또는 일부를 상업적 목적으로 복제 또는 배포해서는 안 됩니다.
Copyright 2018, Telecommunications Technology Association.
All rights reserved.
5
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP TS 23.093 V14.0.0 (2017-03)
Technical Specification
3rd Generation Partnership Project;Technical Specification Group Core Network and Terminals;
Technical realization ofCompletion of Calls to Busy Subscriber (CCBS);
Stage 2(Release 14)
The present document has been developed within the 3rd 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.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)2Release 14
KeywordsLTE, UMTS, GSM, network, CCBS,
supplementary service, stage 2
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
Copyright Notification
No part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.
© 2017, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).All rights reserved.
UMTS™ is a Trade Mark of ETSI registered for the benefit of its members3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational PartnersLTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational PartnersGSM® and the GSM logo are registered and owned by the GSM Association
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)3Release 14
Contents
Foreword ......................................................................................................................................................5
1 Scope..................................................................................................................................................6
2 Normative references ..........................................................................................................................6
3 Definitions and abbreviations ..............................................................................................................63.1 Definitions...................................................................................................................................................63.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.........................................................................................................................................95.3 Activation ..................................................................................................................................................145.4 Deactivation...............................................................................................................................................155.5 Interrogation ..............................................................................................................................................165.6 Messages and their contents .......................................................................................................................165.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 ...........................................................245.6.5 Messages between MSC and HLR (C-interface) ....................................................................................255.6.6 Messages between MSC - MSC (E-interface) ........................................................................................255.6.7 Existing parameters containing CCBS specific information ...................................................................25
6 Monitoring and CCBS Call Reporting...............................................................................................266.1 Monitoring.................................................................................................................................................266.1.1 Overview..............................................................................................................................................266.1.2 Monitoring Subscriber B-state information............................................................................................266.1.3 Monitoring Subscriber A state information:...........................................................................................266.2 MSC/VLR Monitoring Model ....................................................................................................................276.2.1 Subscriber status...................................................................................................................................276.2.1.1 Idle .................................................................................................................................................286.2.1.2 Not Idle...........................................................................................................................................286.2.1.3 Not Reachable.................................................................................................................................286.2.2 Reporting of subscriber state transitions ................................................................................................296.2.2.1 Start Reporting of Monitoring Events ..............................................................................................296.2.2.2 Stop Reporting of Monitoring Events...............................................................................................296.3 CCBS Call Reporting.................................................................................................................................306.3.1 Overview..............................................................................................................................................306.3.2 Originating Network (A-side) ...............................................................................................................306.3.3 Destination Network (B-side)................................................................................................................306.3.3.1 Interaction of Event Reporting and CCBS Call Report .....................................................................306.4 Location Update.........................................................................................................................................30
7 Mobility............................................................................................................................................317.1 Mobility during Activation .........................................................................................................................317.2 Number used within CCBS Call .................................................................................................................31
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)4Release 14
7.3 MS does Location Update ..........................................................................................................................317.4 Mobility during CCBS Call in the destination network................................................................................31
8 Interaction with other supplementary services ...................................................................................328.1 Call forwarding unconditional (CFU) .........................................................................................................328.2 Call forward on busy (CFB) .......................................................................................................................328.3 Call forwarding on no reply (CFNRy) ........................................................................................................328.4 Call forwarding on MS not reachable (CFNRc) ..........................................................................................328.5 Call Waiting (CW).....................................................................................................................................338.6 Multiparty service (MPTY) ........................................................................................................................338.7 Closed user group (CUG) ...........................................................................................................................338.8 Advice Of Charge (AoC)............................................................................................................................338.9 Barring of all outgoing calls (BAOC) .........................................................................................................338.10 Barring of outgoing international calls (BOIC) ...........................................................................................338.11 Barring of outgoing international calls except those directed to the home PLMN country (BOIC-exHC)......338.12 Barring of all incoming calls (BAIC)..........................................................................................................338.13 Barring of incoming calls when roaming outside the home PLMN country (BIC-Roam)..............................348.14 Completion of calls to busy subscriber (CCBS) ..........................................................................................34
9 Interaction with other network features .............................................................................................359.1 Customised Applications for Mobile network Enhanced Logic (CAMEL)...................................................359.2 Support of Optimal Routeing (SOR)...........................................................................................................35
10 Interworking with other networks......................................................................................................3610.1 Interworking with network entities not supporting CCBS............................................................................3610.1.1 CCBS not supported by MSC A............................................................................................................3610.1.2 CCBS not supported by HLR B.............................................................................................................3610.1.3 CCBS not supported by MSC B ............................................................................................................37
11 Network entity functions ...................................................................................................................3811.1 Originating Network Processes...................................................................................................................3811.1.1 Processes and procedures in MSC/VLR ................................................................................................3811.1.2 Processes and procedures in HLR..........................................................................................................6011.2 Destination Network Processes...................................................................................................................9111.2.1 Procedures in GMSC ............................................................................................................................9111.2.2 Processes and procedures in HLR..........................................................................................................9711.2.3 Procedures in MSC/VLR ....................................................................................................................12711.3 Processes and procedures common in originating and destination network entities ....................................139
12 Information stored in the HLRs.......................................................................................................15512.1 Originating Network Data ........................................................................................................................15512.2 Destination Network Data ........................................................................................................................15612.3 Transfer of information from HLR to VLR...............................................................................................156
13 State transition model......................................................................................................................15713.1 State transition model for the CCBS service in the originating network .....................................................15713.2 State transition model for the CCBS service in the destination network .....................................................15713.3 State transition model for a CCBS Request ...............................................................................................15813.4 Information stored in the VLRs ................................................................................................................159
Annex A (informative): Message flow diagrams showing a successful CCBS request..................160
Annex B (informative): Change history .........................................................................................164
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)5Release 14
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) supplementary service within the 3GPP system.
The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change 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;
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)6Release 14
1 ScopeThis Technical Specification gives the stage 2 description of the Completion of Calls to Busy Subscriber (CCBS) supplementary service.
2 Normative referencesThe following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "3G Vocabulary".
[2] 3GPP TS 22.030: "Man Machine Interface (MMI) of the Mobile Station (MS)".
[3] 3GPP TS 22.093: "Completion of calls to busy subscriber (CCBS) supplementary services - Stage 1".
[4] 3GPP TS 23.011: "Technical realization of supplementary services - General Aspects".
[5] 3GPP TS 23.018: "Basic Call Handling - Technical Realization".
[6] 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) -Stage 2".
[7] 3GPP TS 23.079: "Support for Optimal Routeing (SOR) - Technical Realization".
[8] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core Network Protocols Stage3".
[9] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[10] ETSI ETS 300 358: "ISDN Completion of Calls to Busy Subscriber (CCBS) supplementary service; Functional capabilities and information flows".
3 Definitions and abbreviations
3.1 Definitions
Destination 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 of those CCBS Requests.
SSAP: Supplementary Service Application Part. SSAP is the protocol used for CCBS procedures on the interface between the originating and destination network. Communication across this interface is performed using SCCP Connectionless Signalling (Refer to ETS 300 358).
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)7Release 14
Subscriber A: The user of MS A, requesting CCBS. Similarly, MSC A, VLR A and HLR A are the network elements pertaining 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 C and 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 CCBS Requests.
Timers: For each of the service timers, the location, start and stop conditions and action on expiry are given - Refer to subclause 5.1.
3.2 Abbreviations
Abbreviations used in this specification are listed in 3GPP TR 21.905.
4 General
4.1 Overview
The CCBS service allows a calling subscriber A, encountering a NDUB destination B, to be notified when destination B becomes 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 Architecture
Figure 4.2.1 is an architectural overview of the CCBS service when interworking between the originating and the destination networks involved. The originating network may be a mobile network or a fixed network and the destination network 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 following interfaces:
HLR A - HLR B;
HLR A - DLE;
OLE - HLR B.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)8Release 14
ISUP
ISUP ISUP
ISUP
SSAP
SSAP
SSAP
SSAP
OLE
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 HPLMNs during the CCBS service. When all the involved networks support CCBS service the normal handling described in this specification applies. When some network entities do not support CCBS service refer to clause 10 where the exceptions are described in more detail.
The signalling between different networks described in the subclause 4.2 applies also during roaming. HLR A and HLR B belongs always to the HPLMN of the subscriber whereas VLR A and MSC A and GMSC, VLR B and MSC B respectively may belong to a HPLMN or VPLMN. Refer to TS 23.018 where call handling in the mobile network is described in more detail.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)9Release 14
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 the operation of the service, and are described in this section.
5.1 CCBS Timers
The timers used to control the operation of CCBS can be considered to consist of two groups i.e. the timers which operate on a per subscriber basis (see table 1) and the service duration timers (T3 and T7) which operate on a per CCBS Request 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 received from MS A
Discard retained information
T4 Recall 20-30s MSC A CCBS Recall sent to MS A and MS A is idle
Subscriber A initiates CCBS setup or rejects CCBS Recall
Cancel request
T8 Destination idle guard
0-15s HLR B Event Report received from VLR B indicating destination B is idle
Event Report received from VLR B indicating destination B is no longer idle
Inform originating network that Destination B is free
T9 Recall B 40-55s HLR B Remote User Free sent to the A-side
Request cancelled, completed or suspended
Cancel request
T10 CCBS notification
20-30s MSC A CCBS Recall sent to MS A and MS A is not idle
Subscriber A initiates CCBS setup, rejects CCBS Recall or requests suspension
Suspend request
T11 CCBS resume 20-25s HLR A HLR A receives a resume request and there are more than one suspended request in subscriber A’s queue
Remote User Free received from destination network
Resume next suspended request in queue
T12 CCBS Call Guard
20-30s HLRA HLRA receives a CCBS RUF Ack and starts to wait CCBS Call Report
CCBS Call Report received
Cancel request
Table 2: Service Duration Timers
Timer Name Value Run At Started Stopped Expiry
T3 Originating service duration
15-45m HLR A Acknowledgement to CCBS Request received from destination network
Request cancelled or completed
Cancel request
T7 Terminating service duration
>45m HLR B HLR B acknowledges successful activation of a CCBS Request
Request cancelled or completed
Cancel request
5.2 Information flows
Figures 5.2.1 and 5.2.2 show the flow of information between network elements for a mobile to mobile call for the following:
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)10Release 14
Figure 5.2.1: Successful CCBS request, destination B busy when request made, subscriber A free when destination B becomes 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 same situations 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 as follows:
(1) Pre-conditions (Initial Call encountering NDUB and CCBS possible in the destination network). The detailed description of the basic call handling can be found in TS 23.018;
(2) Activation;
(3) Invocation;
(4) Operation (CCBS Call Set-up).
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)11Release 14
Start ReportingAck
MS (A) MSC/VLR (A) HLR (A) GMSC HLR (B) MSC (B)
Set-up
IAMInfo Req
PRN
MSRN
Info 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 Ack
Info Req Ack
IAM (CCBS Call)
ACM/ANM/CPG
ACM/ANM/CPGAlert/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 free when destination B becomes free (mobile-to-mobile)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)12Release 14
Start ReportingAck
Start ReportingAck
MS (A) MSC/VLR (A) HLR (A) GMSC HLR (B) MSC (B)
Set-up
IAMInfo Req
PRN
MSRN
Info 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
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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)13Release 14
CCBS RUFAck
CCBS RUF
MS (A) MSC/VLR (A) HLR (A) DLE (B)
Set-up
IAM
RELEASE (Busy, CCBS Possible)
CCBS Poss
CCBS Request
CCBS Request
CCBS Request
CCBS Request Ack
CCBS Request
Ack
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 free when destination B becomes free (mobile-to-fixed)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)14Release 14
Start ReportingAck
Start Reporting
MS (A) MSC/VLR (A) HLR (A) DLE (B)
Set-up
IAM
RELEASE (Busy, CCBS Possible)
CCBS Poss
CCBS Request
CCBS Request
CCBS 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 Activation
Activation of a CCBS Request is carried out by subscriber A. VLR A is considered to be transparent during the activation operation.
The information flows shown in figures 5.2.1 to 5.2.4 inclusive show the information flow for the activation process.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)15Release 14
5.4 Deactivation
Subscriber 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 TS 22.030.
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 request from the subscriber A’s originating CCBS queue and instruct the destination B network to cancel the corresponding CCBS request in the destination CCBS queue of subscriber B. HLR A shall return a result indicating whether the deactivation attempt was successful or not.
MS A MSC A VLR A HLR A Destination B Network
Deactivate CCBS
------------------->
Deactivate CCBS
--------------------->
Deactivate CCBS
------------------->
CCBS Cancel
------------------->
(note)
Acknowledge
<-------------------
Acknowledge
<--------------------
Acknowledge
<---------------------
Figure 5.4.1: Successful deactivation of all CCBS Requests/a specific CCBS request
NOTE: CCBS Cancel shall be sent for each CCBS Request that is cancelled in HLR A.
NOTE: In the case where a subscriber attempts to perform a deactivation operation but the subscriber is not provisioned with the CCBS service then, the subscriber shall receive an indication that the CCBS service is not provisioned for him.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)16Release 14
5.5 Interrogation
Interrogation of CCBS shall be carried by request to HLR A. HLR A then returns the required information or error to MS 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 each CCBS Request in the queue. The entries shall be ordered in the chronological order, the oldest entry shall be presented first.
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 not provisioned with the CCBS service then, the subscriber shall receive an indication that the CCBS service is not provisioned for him.
5.6 Messages and their contents
This 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 information element shall always be present. A conditional information shall be present if certain conditions are fulfilled; if those conditions are not fulfilled it shall be absent. An optional information element may be present or absent, at the discretion of the application at the sending entity. This categorisation is a functional classification, i.e., stage 2 information and not a stage 3 classifications to be used for the protocol.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)17Release 14
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 element contains unmodified copy of the SETUP message received from the MS A. If CCBS Request is activated, the Call Information is stored in the HLR A. During CCBS Recall Call Information is relayed back to the MS. Refer to SETUP Container information element defined in TS 24.008.
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 the destination B dialled by the A-user.
Table 5.6.1.2: Structure of AddressOfB information element
Parent Information Element
Child Information element name
Information element
Required
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 Information Element
Child Information element name
Information element
Required
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.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)18Release 14
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 Message sender
Information element name
Information element
Required
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 the network.The structure of the AddressOfB is defined in table 5.6.1.2
BasicServiceGroup related to the original call.
CCBS REQUEST ERROR
MSC Error M The information element can take the following values:- Short term denial- Long term denial
DEACTIVATE CCBS MS CCBS Index C If CCBS Index is present the corresponding request shall be deleted, otherwise all requests shall be deleted.
DEACTIVATE CCBS ACK
MSC DeactivateResult M The information element can take the following values:- Success- Not Provisioned
INTERROGATE CCBS
MS - - This message contains no information elements.
INTERROGATE CCBS ACK
MSC List(1-5) of CCBS Description;No Entries;
Not Provisioned
C
CC
The list shall contain one entry for each CCBS Request for which the HLR stores data or;the queue is empty or;CCBS is not provisioned for the subscriberExactly one of these information elements shall be present. The structure of the CCBS Description is defined in table 5.6.1.3.
CCBS CALL INFO MSC Call Information M The content of the Call Information is defined in the subclause 5.6.1.1.
CCBS CALL INFO ACK
MS GSM BC M GSM BC indicates the BC the MS prefers to use. The network may allocate a traffic channel accordingly.
CCBS CALL INFO ERROR
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 in table 5.6.1.3.Alerting Pattern shall be present if it was received in the CCBS RUF message
CCBS SETUP MS - - The content of the message is the same as the MO Set-up message has. Refer to TS 24.008.
CCBS RECALL REJECT
MS Cause M The MS shall indicate the reason of CCBS Recall rejection.The information element can take the following values:- Recall Rejected by the user- UDUB- ACMmax exceeded
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)19Release 14
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 are marked accordingly.
Table 5.6.3.1: Messages between MSC and VLR in the originating network
Message Message sender
Information element name
Information element
Required
Information element description
CALL END MSC - - This message contains no information elements.
The message is used also in the terminating network.CCBS CALL DELIVERY
MSC Outcome M The information element indicates whether CCBS Call was 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 the network.The structure of the AddressOfB is defined in table 5.6.1.2
BasicServiceGroup related to the original call.
CCBS REQUEST ERROR
VLR Error M The information element can take the following values:- Short term denial;- Long term denial.
COMPLETE RECALL
VLR Call Information M The content of the Call Information is defined in the subclause 5.6.1.1.
COMPLETE RECALL ACK
MSC - - This message contains no information elements
COMPLETE RECALL NEGATIVE
RESPONSE
MSC Negative Response M The negative information element can take the following values:- Absent Subscriber;- Incompatible Terminal;- Radio Congestion.
DEACTIVATE CCBS MSC CCBS Index C If CCBS Index is present the corresponding request shall be deleted, otherwise all requests shall be deleted.
DEACTIVATE CCBS ACK
VLR DeactivateResult M The information element can take the following values:- Success;- Not Provisioned.
INTERROGATE CCBS
MSC - - This message contains no information elements
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)20Release 14
Table 5.6.3.1: Messages between MSC and VLR in the originating network, cont.
Message Message sender
Information element name
Information element
Required
Information element description
INTERROGATE CCBS ACK
VLR List(1-5) of CCBS Description;No Entries;
Not Provisioned
C
C
C
The list shall contain one entry for each CCBS Request for which the HLR stores data; orthe queue is empty; or
CCBS is not provisioned for the subscriber.
Exactly one of these information elements shall be present. The structure of the CCBS Description is defined in table 5.6.1.3.
NOT IDLE MSC - - This message contains no information elements. The message is used also in the terminating network.
PAGE MS FOR RECALL
VLR Location area ID,
TMSI
M
O
Location area in which the MS is to be paged
TMSI to be broadcast to identify the MS
PAGE MS FOR RECALL NEGATIVE
RESPONSE
MSC Negative Response M The negative information element can take the following values:- Unknown LAI;- Absent Subscriber;- Busy Subscriber.
PROCESS ACCESS REQUEST
MSC - - Refer to TS 23.018
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 in table 5.6.1.3.Alerting Pattern shall be present if it was received in the CCBS 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 MS MSC FOR RECALL
VLR - - This message contains no information elements
SEARCH FOR MS MSC FOR RECALL
ACK
MSC - - This message contains no information elements
SEARCH FOR MS MSC FOR RECALL
NEGATIVE RESPONSE
MSC Negative Response M The negative information element can take the following values:- Absent Subscriber;- Busy Subscriber;
SEND INFO FOR OUTGOING CALL
MSC - - Refer to TS 23.018
START STATUS ENQUIRY
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 ENQUIRY
VLR - - This message contains no information elements.
The message is used also in the terminating network.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)21Release 14
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 are marked accordingly.
Table 5.6.3.2: Messages between MSC and VLR in the destination network
Message Message sender
Information element name
Information element
Required
Information element description
CALL END MSC - - Refer to table 5.6.3.1
CCBS CALL DELIVERY
MSC - - Refer to table 5.6.3.1
START STATUS ENQUIRY
VLR - - Refer to table 5.6.3.1
STATUS ENQUIRY RESULT
MSC - - Refer to table 5.6.3.1
STOP STATUS ENQUIRY
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 TS 23.018In addition:The information element shall be present if the call is CCBS Call; otherwise it shall be absent.
PROCESS CALL WAITING
VLR -
Indicator
-
C
Refer to TS 23.018In addition:The information element shall be present if the call is CCBS Call; otherwise it shall be absent.
SEND INFO FORINCOMING CALL
ACK
VLR -
CCBS Target
-
C
Refer to TS 23.018In addition:The information element shall be present if the B subscriber can be target of CCBS request; otherwise it shall be absent.
SEND INFO FORINCOMING CALL
NEGATIVE RESPONSE
VLR -
CCBS Target
-
C
Refer to TS 23.018In addition:The information element shall be present if the B subscriber can be target of CCBS request; otherwise it shall be absent.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)22Release 14
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 destination network. They are marked accordingly.
Table 5.6.4.1: Messages between VLR and HLR in the originating network
Message Message sender
Information element name
Information element
Required
Information element description
CCBS REQUEST VLR Call Information
ISDN BC
ISDN HLC
ISDN LLC
Presentation Indicator
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 the subclause 5.6.1.1.ISDN BC derived for the initial call.
Shall be present if ISDN HLC was present in the initial call; otherwise shall be absent.Shall be present if ISDN LLC was present in the initial call; 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 in international E.164 format.Shall be present if MO CAMEL was invoked in the initial call; otherwise shall be absent.GSM Elementary Basic Service Group which corresponds to the basic service used for initial call set-upThe structure of the AddressOfB is defined in table 5.6.1.2
CCBS REQUEST ACK
HLR CCBS Index
AddressOfB
Basic Service Group
M
O
O
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.
CCBS REQUEST ERROR
HLR 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 the subclause 5.6.1.1.The content of the CCBS Description is defined in table 5.6.1.3.The number used for routing purposes in international E.164 format.The information element shall be present if the HLR instructs the MSC to replace the destination B number with the translated B number; otherwise it shall be absent.
Alerting Pattern shall be present if the HLR has determined an alerting category or an alerting level for the CCBS recall
CCBS RUF ACK VLR Result M The information element indicates whether CCBS Recall was 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 CCBS Recall could not be successfully delivered. It can take the following values:- IMSI Detached;- Restricted Area;- No Page Response;- Incompatible Terminal;- Absent Subscriber;- Radio Failure;- Ccomp Busy;- System Failure.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)23Release 14
Table 5.6.4.1: Messages between VLR and HLR in the originating network, cont.
Message Message sender
Information element name
Information element
Required
Information element description
EVENT REPORT VLR 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.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 REPORTING HLR - - This message contains no information elements.
The message is used also in the terminating network.
START REPORTING ACK
VLR 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 REPORTING
ERRORVLR Error M The information element contains no application specific error
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. It can take the following values :- A;- B.The information element indicates the outcome of the CCBS 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 is set 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 ACK
HLR - - This message contains no information elements.
The message is used also in the terminating network.
CCBS CALL REPORT ERROR
HLR Error M The information element contains no application specific error values.
The message is used also in the terminating network.DEACTIVATE CCBS VLR CCBS Index C If CCBS Index is present the corresponding request shall be
deleted, otherwise all requests shall be deleted.
DEACTIVATE CCBS ACK
HLR DeactivateResult M The information element can take the following values:- Success;- Not Provisioned.
DEACTIVATE CCBS ERROR
HLR Error M The information element contains no application specific error values.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)24Release 14
Table 5.6.4.1: Messages between VLR and HLR in the originating network, cont.
Message Message sender
Information element name
Information element
Required
Information element description
INTERROGATE CCBS
VLR - - This message contains no information elements.
INTERROGATE CCBS ACK
HLR List(1-5) of CCBS Description;No Entries;
Not Provisioned
C
C
C
The list shall contain one entry for each CCBS Request for 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 be present. The structure of the CCBS Description is defined in table 5.6.1.3.
INTERROGATE CCBS ERROR
HLR Error M The information element contains no application specific error 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 originating network. They are marked accordingly.
Table 5.6.4.2: Messages between VLR and HLR in the destination network
Message Message sender
Information element name
Information element
Required
Information element description
EVENT REPORT VLR - - Refer to table 5.6.4.1
EVENT REPORT ACK
HLR - - Refer to table 5.6.4.1
EVENT REPORT ERROR
HLR - - Refer to table 5.6.4.1
START REPORTING HLR - - Refer to table 5.6.4.1
START REPORTING ACK
VLR - - Refer to table 5.6.4.1
START REPORTING ERROR
VLR - - Refer to table 5.6.4.1
CONTINUE MONITORING
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 CALL REPORT ACK
HLR - - Refer to table 5.6.4.1
CCBS CALL REPORT ERROR
HLR - - Refer to table 5.6.4.1
PROVIDE ROAMING NUMBER
HLR -
CCBS Call Reporting Request
-
C
Refer to TS 23.018In addition:The information element shall be present for CCBS Call roaming number enquiry; otherwise it shall be absent.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)25Release 14
5.6.5 Messages between MSC and HLR (C-interface)
Table 5.6.5: Messages between MSC and HLR
Message Message sender
Information element name
Information element
Required
Information element description
SEND ROUTING INFO
MSC -
CCBS Supported
CCBS Call Indicator
-
C
C
Refer to TS 23.018In addition:The information element shall be present if GMSC supports CCBS; otherwise it shall be absent.The information element shall be present, if SRI is for CCBS Call; otherwise it shall be absent.
SEND ROUTING INFO_ACK
HLR -
CCBS Target
Keep CCBS Call Indicator
Forwarding Reason
-
C
C
C
Refer to TS 23.018In addition:The information element shall be present if the call is forwarded on busy and the subscriber B can be target of CCBS requests; otherwise it shall be absent.The information element shall be present if the VMSC supports CCBS and SRI enquiry was for CCBS Call; otherwise it shall be absent.The reason CFBusy shall be present if the HLR has determined that the call is to be forwarded for that CCBS case.
SEND ROUTING INFO NEGATIVE
RESPONSE
HLR -
Negative Response
-
-
Refer to TS 23.018New 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 Message sender
Information element name
Information element
Required
Information element description
RESUME CALL HANDLING
MSC -
CCBS Target
-
C
Refer to TS 23.079In addition:The information element shall be present if the call is forwarded on busy and the subscriber B can be target of CCBS requests; otherwise it shall be absent.
5.6.7 Existing parameters containing CCBS specific information
Mobile Station Classmark 2 (refer to TS 24.008 contains information whether “Network initiated MO CM connection request” is supported or not. This information is vital for the recall mechanism.
CC capabilities (refer to TS 24.008) 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 TS 29.002) contains information whether CCBS service is provisioned to the subscriber. Both originating and destination CCBS service have their own SS-Code.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)26Release 14
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 current subscriber 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 from the appropriate HLR. The actions on the A-side and B-side for monitoring are completely independent and the following description is generic to cover either case. The HLR sends an explicit Start Reporting signal to the VLR to initiate monitoring. The VLR acknowledges the request confirming that monitoring has started and indicates the current status of the subscriber state in the VMSC/VLR. The VLR will continue to send an Event Report to the HLR whenever the appropriate subscriber state transition event occurs. The HLR sends an explicit Stop Reporting signal to the VLR when reporting 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 monitoring enables the HLR B to be aware of any transition of subscriber state in VMSC/VLR B while there is an active CCBS Request 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 appropriate time. If subsequently to that event the destination B subscriber state becomes not Idle or not reachable,then the HLR B is informed by the VMSC/VLR B in order that it can take an appropriate action towards HLR A, e.g. defer sending of the Remote 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 B network cannot be acted upon because e.g. MS A is not idle or not reachable and leads to the CCBS request being suspended. The service action in this event is that, when the subscriber state subsequently becomes Idle, the HLR A is informed and a Resume indication is sent towards the destination B network at the appropriate time.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)27Release 14
6.2 MSC/VLR Monitoring Model
The Monitoring model represents the information related to the status of the subscriber connection in the MSC/VLR. A generic monitoring model is used in the MSC/VLR covering the needs of both subscriber A and subscriber B state information for CCBS. The MSC/VLR monitoring model for CCBS is shown in figure 6.2.1. Note that state transitions reported 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 TS 23.078 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 "NOT REACHABLE"
"Assumed Idle"
NOT IDLE The MS is engaged on a transaction for a MO or MT circuit switched call
"CAMEL busy"
NOT REACHABLE The MSC/VLR can determine from its internal data that the MS is not reachable e.g. IMSI detached, Restricted Area, No Page Response.
"Network Determined Not Reachable"
For each subscriber state a description can be found on the entry events, functions and exit events.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)28Release 14
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.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)29Release 14
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 for the CCBS service. An appropriate Event Report signal is sent from the VLR to the HLR when a relevant state transition occurs. 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 report Subscriber 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 that monitoring has started and indicate the current status of the subscriber state in the MSC/VLR. The VLR shall subsequently continue to send the Event Reports indicated in table 6.2.2 whenever the appropriate subscriber state transition event occurs.
Note where a single user has a CCBS request activated against him and has an outstanding CCBS request suspended against someone else, (i.e. is effectively both destination B and CCBS subscriber A) reporting on both A-side and B-side is required. In this case, the VLR shall only send a single Event Report as indicated in table 6.2.2 whenever the appropriate subscriber state transition event occurs. The HLR shall not send another Start Reporting signal to the VLR if monitoring 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.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)30Release 14
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 basic reporting 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 resulting from the acceptance of the CCBS Recall by Subscriber A. The VLR A sends a CCBS Call Report to the HLR A indicating the outcome of the CCBS call processing in MSC/VLR A when e.g. an address complete message (ACM) is received from the destination B network. CCBS Call Reporting on the A-side is completely independent of any monitoring of subscriber state information. The sending of CCBS Call Report is required even when there is no monitoring ongoing in the MSC/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 in the MSC/VLR B. The HLR B initiates the CCBS call outcome reporting in the VLR when the VLR is normally queried to provide routing information for mobile terminated calls (by including an CCBS indicator in the PRN message). The VLR B sends a CCBS Call Report to the HLR B indicating the outcome of the CCBS call processing and the new status of the subscriber 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 being sent to the MS. When the response to the CCBS Recall is received, the VLR shall subsequently send a CCBS Call Report when the relevant processing for the outgoing CCBS call to the destination network is completed as shown in the SDLs for 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 Number message, the VLR shall subsequently send a CCBS Call Report when the relevant processing of the incoming CCBS call is 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 is required.
When a subscriber state transition from IDLE to NOT IDLE occurs due to an incoming CCBS call, an Event Report shall not be sent. Instead, a CCBS Call Report (containing CCBS call outcome information and the status) shall be sent to the HLR B. After the CCBS Call Report has been sent, normal Event Reporting will continue i.e. the VLR shall subsequently send only the Event Reports indicated in table 6.2.2 when the next appropriate subscriber state transition event occurs.
6.4 Location Update
The MS may roam to a new MSC/VLR area while monitoring is ongoing in the previous MSC/VLR. When the VLR receives a Cancel Location signal from the HLR due to normal mobility management procedures, any ongoing CCBS related activities associated with the subscriber shall cease.
If the A-side monitoring is ongoing when the HLR receives a Location Update request from the VLR, the Location Update signal is considered to indicate that the subscriber state is idle and the appropriate CCBS process in the HLR is informed. The normal mobility management procedures will lead to a Cancel Location signal being sent to the old VLR causing the Event Reporting to stop.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)31Release 14
If the B-side monitoring is ongoing when the HLR receives a Location Update request from the VLR, the normal mobility management procedures are followed. On successful completion of Location Update procedure, the HLR shall send a Start Reporting signal to the new VLR. If during the handling of the normal Location Updating procedure, it is detected that the new MSC/VLR does not support CCBS, the HLR shall not send a Start Reporting signal to the new VLR.
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 Activation
In order to allow the activation of CCBS when the call is released, the CC connection towards the MS shall be kept, to avoid 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 the MSC sends a CCBS REQUEST ACK or CCBS REQUEST ERROR to the MS. After MSC has sent CCBS REQUEST ACK or CCBS REQUEST ERROR, the MSC A shall release the CC connection with MS.
7.2 Number used within CCBS Call
The activating MSC A shall store the originally dialled number in the Call Information container. The TranslatedBNo parameter 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 the destination B network the HLR A may request the recall MSC A to change the number used for CCBS Call to the TranslatedBNo 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 CCBS Call.
7.3 MS does Location Update
CCBS does place extra requirements for the Location Update procedure in the HLR when MS is monitored. Refer to subclause 6.4.
7.4 Mobility during CCBS Call in the destination network
If MS registers to non-supporting network special handling has to be applied. Refer to subclause 10.1.3.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)32Release 14
8 Interaction with other supplementary servicesTS 22.093 specifies a number of interactions between CCBS and other supplementary services. Additional details of how 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 that CCBS is not possible when it releases the call. Refer to Process MT_GMSC (see TS 23.018) for further details.
If destination B activates CFU after subscriber A has activated a CCBS Request against destination B, HLR B shall not process CCBS Requests in the queue which are related to the relevant Basic Service Group, except that T7 shall continue for 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 B queue subsequently become "Active and Quiescent", then HLR B shall send “Stop Reporting” to MSC B. If destination B 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 or VMSC) shall inform MSC A that CCBS is possible when it releases the call. Refer to Process MT_GMSC or Process ICH_MSC (see TS 23.018) for further details.
If destination B activates CFB after subscriber A has activated a CCBS Request against destination B, HLR B shall continue to process CCBS Requests in the queue. If a CCBS Call subsequently arrives at MSC B and MS B is NDUB, a network 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) shall inform MSC A that CCBS is not possible when it releases the call. Refer to Process MT_GMSC or Process ICH_MSC (see TS 23.018) for further details
If destination B activates CFNRy after subscriber A has activated a CCBS Request against destination B, HLR B shall continue 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 or VMSC) shall inform MSC A that CCBS is not possible when it releases the call. Refer to Process MT_GMSC or Process_ICH_MSC (see TS 23.018) for further details.
If destination B activates CFNRc after subscriber A has activated a CCBS Request against destination B, HLR B shall continue to process CCBS Requests in the queue.
The CCBS call shall be forwarded without the CCBS call Indicator.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)33Release 14
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 associated request 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 A shall 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 detects that 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 directed to 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 home PLMN country and MSC A detects that BOIC-exHC is active and operative, then MSC A shall cancel the associated request 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 Service 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 BAIC is activated by destination B then all the CCBS Requests in the destination B queue subsequently become "Active and Quiescent" and HLR B shall send "Stop Reporting" to MSC B. If destination B deactivates 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, such that a CCBS call from subscriber A is not permitted, HLR B shall cancel the associated request related to the Basic Service Group and select the next non-suspended request in the queue for processing for other Basic Service Groups.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)34Release 14
8.13 Barring of incoming calls when roaming outside the home PLMN 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 Basic Service 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 the destination B queue subsequently become "Active and Quiescent" and HLR B shall send "Stop Reporting" to MSC B. If destination B deactivates BIC-Roam 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 incoming calls when roaming outside the home PLMN country becomes active and operative for aparticular Basic Service Group for destination B, such that a CCBS call from subscriber A is not permitted, HLR B shall cancel the associated request related to the Basic Service Group and select the next non-suspended request in the queue for processing 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 also have one or more CCBS requests successfully activated against him by different subscribers. In this case, HLR A shall co-ordinate the different requests.
Checking for an identical CCBS request already existing shall include checks in both directions, i.e. if subscriber A activates a CCBS Request against destination B, HLR A shall check subscriber A’s originating queue for any previous requests activated by subscriber A against destination B for the same basic service group. HLR A shall also check subscriber A’s target queue for any requests activated by destination B against subscriber A for the same basic service group.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)35Release 14
9 Interaction with other network featuresTS 22.093 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 which subsequently encounters NDUB, the GMSC shall inform originating network that CCBS is not possible when it releases the call.
If an originating CAMEL based service determines for a CCBS Call a different destination B Address than for the original call, 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, CCBS Possible 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 SRI for a CCBS call set-up) and the SRI does not include a CCBS call indicator nor CCBS supported in the GMSC indicator and the request is from a GMSC not in the same PLMN as HLR B, then HLR B shall return an SRI negative response indicating OR not allowed. This will force the GMSC to route the call to a GMSC in the same PLMN as HLR B (see TS 23.079).
The GMSC in HPLMN B should be able to include the CCBS Call indicator in the non-OR SRI, and the CCBS call set-up will 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, it can treat the request as if the B-subscriber were busy, regardless of where the GMSC is.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)36Release 14
10 Interworking with other networksThe point of interworking shall be the interface between HLR A and HLR B. The flow of information across this interface shall 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 may fail.
10.1 Interworking with network entities not supporting CCBS
CCBS 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 that the 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 an entity which receives an indication for the CCBS service but does not support it can indicate its lack of support to the sending 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 A where MS A is currently registered does not support CCBS, then HLR A shall suspend the corresponding CCBS Request 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 A had 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 be generated in the CCBS diagnostic.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)37Release 14
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 B queue and subsequently no monitoring of destination B will be possible until destination B registers in a supporting MSC.
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 shall request a Roaming No without including the CCBS Call indicator in the request. Within Send Routeing Info Ack the HLR shall 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 may register in an MSC which does not support the service. MSC B shall accept the CCBS call, but MSC B will not be able to inform HLR B of the successful completion of the CCBS call, so the request will remain active in HLR B until the recall B timer (T9) expires and the request is cancelled.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)38Release 14
11 Network entity functionsThe following SDL diagrams describe the various processes and procedures within individual network entities for handling 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. If CCBS 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 CCBS activation 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 HLR respectively.
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 informs HLR 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 call delivery failure.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)39Release 14
Process MSC_CCBS_Recall_Manager 1(4)
Signals to/from the leftare to/f rom the BSS.signals to/from the rightare to/f rom 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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)40Release 14
Process MSC_CCBS_Recall_Manager 2(4)
Signals to/from the leftare to/f rom the BSS.signals to/from the rightare to/f rom 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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)41Release 14
Process MSC_CCBS_Recall_Manager 3(4)
Signals to/from the leftare to/f rom the BSS.signals to/from the rightare to/f rom 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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)42Release 14
Process MSC_CCBS_Recall_Manager 4(4)
Signal s to/from th e left
are to/from the BS S.signals to/fr om the rightare to/from the VL Runless speci fied otherwise
Wa it_For_Recall_
Response
C CBS_Se tup
BasicServiceGroupof the cal l =BasicServiceGroup received
from HLR
Rep laceBNo
Use Translate dBNoinstead of the origin ally
dia led B numb er
Stop T4Stop T10
C ause :=Incompatibe
terminal
Cau se:=Accept
Reca ll_Ack(Cause)
Recall _Ack(Cause)
IdleCCBS_Report_
Not_Idle
Refer to GSM 0 3.18 OG_Call_Setup_MSC
CCBS_Check_Last_Call
Releasecall
resources
Idle
Yes
No
Tru e
False
Figure 11.1.1.1: Process MSC_CCBS_Recall_Manager (sheet 4 of 4)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)43Release 14
Process VLR_CCBS_Recall_Manager 1(4)
Signals to and from the leftare to/from the MSC. Signalsto and from the right are to/fromthe HLR unless specified otherwise
Idle
CCBS_RUF
Check_Parameters
See GSM 03.18
Result
Error:=Negative Response
IMSIDetached
Error := IMSI_Detached
Roaming in LA Allowed
Error:= Restricted_Area
Locationarea IDknown
Search_For_MS_VLR_Recall
Page_MS_For_Recall
CCBS_RUF_Error (Error)
Result=PassTo CCBS_Monitoring_VLR Not Reachable
1Wait_For_
Recall_RequestIdle
Fail
Pass
Yes
No
No
Yes
No
Yes
No
Yes
Figure 11.1.1.2: Process VLR_CCBS_Recall_Manager (sheet 1 of 4)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)44Release 14
Process VLR_CCBS_Recall_Manager 2(4)
Signals to and from the leftare to/from the MSC. Signalsto and from the right are to/fromthe HLR unless specified otherwiseWait_For_
Recall_Request
Page MS For Recall negativeresponse
1Process Access Request
AbsentSubscriber
Refer to GSM 03.18Process_Access_
Request_VLR
Not_ReachableTo CCBS_Monitoring_VLRThis check does not
determine whether a CCconnection is establishedbut rather that another call is in the establishment phase
BusySubscriber
Result = Pass
Error :=CComp_Busy
Error := No Page Response
Error :=System_Failure
Error :=Absent_Subscriber
CCBS_RUF_Error (Error)
CompleteRecall
IdleWait_For_Complete
_Call_Result
Yes
No
Yes
No
No
Yes
Figure 11.1.1.2: Process VLR_CCBS_Recall_Manager (sheet 2 of 4)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)45Release 14
Process VLR_CCBS_Recall_Manager 3(4)
Signals to and from the leftare to/from the MSC. Signalsto and from the right are to/fromthe HLR unless specified otherwiseWait_for_Complete_
Recall_Result
CompleteRecall ack
Complete Recallnegative response
NegativeResponse
Recall Error := Incompatible Terminal
Error :=Radio_Faliure
Error :=System_Failure
CCBS_RUFError (Error)
Wait_For_Recall_Response
Idle
Incompatible_Terminal
Absent_SubscriberRadio_Congestion
ELSE
Figure 11.1.1.2: Process VLR_CCBS_Recall_Manager (sheet 3 of 4)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)46Release 14
Process VLR_CCBS_Recall_Manager 4(4)
Signals to and from the leftare to/from the MSC. Signalsto and from the right are to/fromthe HLR unless specified otherwise
Wait_For_Recall_Response
Recall_Ack (Cause)
Cause
Error := Radio_Failure
Error :=Incompatible_Terminal
Result := Cause
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
Radio FailureIncompatible Terminal ELSE
RUF Accepted
ELSE
Figure 11.1.1.2: Process VLR_CCBS_Recall_Manager (sheet 4 of 4)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)47Release 14
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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)48Release 14
Procedure CCBS_Check_OG_Call 1(1)
CCBS ProvisionedandME supports CCBS
Reconnect
CCBS Call
Transl atedBNo :=Routing addressi n international
E.164 forma t
Tra nslated B N o received
from HLR = C CBS Cal ltranslate d target
TranslatedBN o :=Ro uting addre ssin internationa l
E.164 format
Set CCBS_ Cal l_Indica tor to IAM
message
Store CallInformation
Result :=Fail
Result :=Pass
Yes
No
False
True
Yes
No
Yes
No
Figure 11.1.1.4: Procedure CCBS_Check_OG_Call
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)49Release 14
Pro cedure CCBS _Check_If_C CBS_P ossible 1(1)
Call Completion
Trea tment Indica tor
pres ent in S II2?Ca ll Completion Tr eatment
Indicator set t o re jec t call
completion serv ic e
req uest?
CCBS
Provis ioned
Reconnect
Initial
result
Cause = Busy
or
Cause = No circuit
channel available
Result :=
CCBS_
Possible
Result :=
CCBS_Not_
Possible
Cau se = Busy
or
Cau se = No circuit
channel available
CCBS
Call
Outcome :=
Failure
CCBS_Call_
Delivery
(Outcome)
To V LR_CCB S_
Rec all_
Manager
Clear stored
call inf ormation
Initial re sult :=
CCBS_Not
Possible
Resu lt : =
CCBS_Not_
Possible
CCBS
Call
Outcome :=
Busy
CCBS_Call_
Delivery
(Outcome)
To VLR_CCBS_
Rec all_
Manager
CCBS
Possible
Che ck diagnos tic
assoc ia ted w it h the
busy cause value
ME
supports
CCBS
Initial result :=
CCBS_
Possible
Result :=
CCBS_
Possible
Y es
No
Y es
True
CCBS_
Possible
Yes
No
CCBS_
Not_
Possible
FalseNo
Yes
NoY es
Y es
Y esNo
Y es
No
No
No
Yes
No
Figure 11.1.1.5: Procedure CCBS_Check_If_CCBS_Possible
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)50Release 14
Procedure CCBS_Activation_MSC 1(2)
Signals to/from the leftare to/f rom the BSS;signals to/from the rightare to/f rom HLRunless marked otherwise
CCBS_Possible
Start T1
RR connect ionmay 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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)51Release 14
Procedure CCBS_Activation_MSC 2(2)
Signals to/from the leftare to/f rom the BSS;
signals to/from the rightare to/f rom 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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)52Release 14
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/f rom the BSS; signals to/from the rightare to/f rom the VLRunless marked otherwise
Locat ionarea IDknown
MSconnection
existsDoes an RR connection exist
Regat iveresponse:=
Unknown LAI
Set accessconnection
status
Start Pageresponse
timer
Page MS ForRecallnegativeresponse
Result:=Pass
In specified location area
PageResult:=
Fail
Wait_For_Page_
Response
Yes
No
Yes
No
Figure 11.1.1.7: Procedure Page_MS_MSC_For_Recall (sheet 1 of 2)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)53Release 14
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/f rom the BSS; signals to/from the rightare to/f rom 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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)54Release 14
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
PageResult:=
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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)55Release 14
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/f rom 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 negat ivecause to the
parent process
Result:=Pass
Result:=Fail
Figure 11.1.1.9: Procedure Search_For_MS_VLR_Recall
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)56Release 14
Procedure Complete_Recall_MSC 1(2)
Signals to/from the leftare to/from the BS S;signals to/fr om the right
are to/from the VLRunless marked o therwise
CM_S erv_ Prompt
Wait_For_CM_ Serv_Prompt_
Response
Rele asetran saction
Co nnection_type_
not_supported
Start_CC
Negativeresponse:=
Absent
subscriber
CCBS_Ca ll_Info
Wait_For_Ack
Incompatib leTermi nal
Release(UDUB)
Releasetransaction
CCBS_Ca ll_Info_Confi rmed
N egative
re sponse:=Incompatib le
Terminal
Negativerespon se:=
CComp Busy
Negative
response:=Absent
subscriber
BasicServiceGroup
of the CCBS_ Cal l_Info= BasigServiceGroupreceived from HLR
Negative
response:=Incompatible
Terminal
Complete_Reca ll_negative_
Resp onse
Result:=Fail
1
No
Yes
Figure 11.1.1.10: Procedure Complete_Recall_MSC (sheet 1 of 2)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)57Release 14
Procedure Complete_Recall_MSC 2(2)
1
Early traficchannelal location?
Establ ish_Originat ing_
TC H_If_
Re quire d
Refer GSM 03.18
Re sult =Pass
Negativeresp onse :=
Radio_congestion
Complete_Recal l_Ack
Complete_Recal l_
Ack
C omplete_Recall_negative_
R esponse
Result :=Pass
Re sult:=TCH_all ocated
Result:=Fail
YesNo
N o
Yes
Figure 11.1.1.10: Procedure Complete_Recall_MSC (sheet 2 of 2)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)58Release 14
Procedure CCBS_OCH_Report_Success 1(1)
CCBSCal l
R econnect
Outcome :=Success
To VLR_CC BS_R ecal l_Manager
CCBS CallDelivery(Outcome)
C lear storedca ll info rmation
Yes
No
False
True
Figure 11.1.1.11: Procedure CCBS_OCH_Report_Success
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)59Release 14
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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)60Release 14
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 is present in the queue or not.
The process has three states, "Idle", "Operative" and "Operative Resuming". In the "Idle" state the queue is empty and the 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) in the queue and none of them are suspended.
When HLRA_Request reports of suspension the process changes it’s state to "Operative Resuming" and the HLRA_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 until them 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 starts again when idle condition is met again or there is a new recall with successful outcome i.e. the recall ends without Not Reach indication.
The resuming process will be stopped, if there are no suspended requests in the queue any more. The process changes it’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 different states, "Wait_For_Answer", "Active", "Recall", "Suspended" and "Frozen". During its creation the process sends CCBS_Request via SSAP interface to destination network B containing all call related data as well originating networks retention capabilities.
In the "Wait_For_Answer" state process receives response from destination network which is further relayed to the HLRA_Request_Manager. In case of positive acknowledgement destination network returns info whether the retention is supported in both networks.
In "Active" state process waits recall from destination network, however process can vanish if operation timer T3 expires or 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 the request 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 process transits to the suspended state.
If the request is deleted during "Recall" due SSAP_Cancel, T3 expiry or explicit deletion the queue is updated immediately 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 be deleted 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 network and the request can’t be fulfilled due service interaction or lack of support in MSCVLR. The request shall indicate suspended back to the destination network and stay in the queue. If the service becomes later possible, the request will revert back “Active” state and indicate resumed to the destination network.
Whenever the state of the process is changed, the new state is stored and the procedure CCBS_Notify_SS_Invocation is called.
Figure 11.1.2.4: Process HLRA_Recall_Manager
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)61Release 14
This process has two different states, "Idle" and "CCBS_Busy".
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 it changes it’s state to "CCBS_Busy". In this state other requests are suspended immediately and marked as NET suspended with cause code = Busy.
In "CCBS_Busy" state the process waits recall reporting from the MSC. Possible inputs from the MSC are CCBS_RUF_Ack, CCBS_RUF_Error and CCBS_Call_Report. CCBS_Call_Report can be received if the subscriber has accepted the recall, otherwise the process changes it’s state back to "Idle". If the process receives Query_State request from 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 is started 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 and Recall_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 a permission to start resuming. When the permission is received the process asks for the first NET request to resumed. If A_Idle signal is received from the monitoring process the resuming process asks the queue manager to set all suspended requests 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 the process to "Monitoring" state. In this state the process reports "Idle" condition to the resuming process and starts the monitoring 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.
Figure 11.1.2.8: Procedure CCBS_Notify_SS_Invocation
This procedure is called by the process HLRA_Request whenever there is a change of state. The procedure informs the gsmSCF of the state change if the SS-CSI applicable to CCBS is stored in the HLR.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)62Release 14
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
Resume
Delete
CCBS_Request_Ack
CCBS_Request_ErrorSuspendDeleted
CCBS_RequestCCBS_SuspendCCBS_Resume
CCBS_Cancel
CCBS_Request_AckCCBS_Reject_RequestRemote_User_Free
CCBS_CancelCCBS_END
Destinationnetwork B
Recall
CompletedSuspendFailure
Busy
Set_All_ActiveSelect_Active_ReqSelect_Fi rst_Req
Set_Trigger_Recall_EndSet_Trigger_A_Id leReset_Trigger _A_Idle
Select_RespNot_S electedStop_Resume
Query_Status
RecallRecall_End
A_QueryStop_Monitoring
A_Idle
CCBS_Coordinator_HLR
CCBS_Call_Report
Start_ReportingStop_Reporting
Start_Reporti ng_Ack
Event_Report
VLRA
CCBS_RUF_A ckCCBS_RUF_E rror
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 not constrained to follow the implementation given in figure 11.1.2.1. However, the external behaviour of HLR A shall appear to be the same.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)63Release 14
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 queue manager.
CCBS_Request_Error signal is sent if the destination networks queue is full or the destination networks queue size is set to 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 individual request the request to die.
Deleted is used within HLRA_Request_Manager and HLRA_Request. The individual request informs the queue of its expiry.
Resume is used within HLRA_Request_Manager and HLRA_Request. The individual request is resumed and it shall inform 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 ongoing this 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 this signal 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 resuming process 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 to start T11.
Not_Selected is used within the HLRA_request_manager and HLRA_resume. This signal informs the resuming process that 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 process to 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 all suspended 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 to select 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 to select first suspended request to be resumed. If successful the request process will return "Select_Resp", otherwise "Not_Selected".
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)64Release 14
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 the CCBS_Call.
Completed is used within the HLRA_Recall_Manager and HLRA_Request. It informs the request of successful CCBS_Call and causes the request to vanish.
Failure is used within the HLRA_Recall_Manager and HLRA_Request. It informs the request of unsuccessful CCBS_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_Call and 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 the suspension 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 actions and 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 now CCBS_Idle and not CCBS_Busy.
Stop_Monitoring is used with HLRA_Resume and HLRA_Monitoring. It instructs the monitoring process to stop it’s actions and stop the monitoring from VLR also.
Location_Update/Restore_Data events are tracked and external reporting is started again.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)65Release 14
Process HLRA_RequestManager(1,1) 1(10)
IDLEThere is not any re quest in the
IDLE state
CCBS_Request From MSCVL R
Check_Parameters
Se e GSM 03 .18
IDLE Resul t
HLRA_Request
Error :=Negative
respo nse
Upda te thequeu e
CCBS_Request_Error(Erro r)
To MSC VLR
IDLE OPER ATIVE IDLE
From MSC _VLRDeactivate_CCBS
See GSM 03.18 Check_Parameters
Result
CCBSprovisioned
Deactivate_Resu lt :=
Not Provisi oned
Deactivate_Result :=Succe ss
Error :=N egativere sponse
To MSC_VLR
Deactivate_
CCBS_Ack(Deactivate_Resu lt)
Deactivate_CCBS
Error(Error)
To MSCVLR
IDLE ID LE
Pass
Fai l
Pass
Fail
No
Yes
Figure 11.1.2.2: Process HLRA_Request_Manager (sheet 1 of 10)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)66Release 14
Process HLRA_RequestManager(1,1) 2(10)
*
Interro gate_CCBS
From MSC_VLR
C heck_Parameters
See GSM 03.1 8
R esul t
Error :=Nega tive
response
CCBSprovisioned
To MSC_ VLRInterrogate_CCBS_Ack
(Erro r)
Queuee mpty
- Resu lt :=No Entries
Query the queue :=
List
Result :=Not_ Provisione d
R esul t := List
To MSC_ VLRInterrogate_CCBS_Ack
(Resul t)
To MSC_ VLRInterroga te_CC BS_Ack
(Result)
Interro gate_CCBS_Ack(Resul t)
To MSC_ VLR
-
Fa il
Pass
Yes
N o
Yes
No
Figure 11.1.2.2: Process HLRA_Request_Manager (sheet 2 of 10)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)67Release 14
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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)68Release 14
Process HLRA_RequestManager(1,1) 4(10)
*(IDLE)
From MSCVLRCCBS_Requ est
See GSM 03.18C heck_
Parameters
R esul t
Queueful l
Error :=Negativerespo nse
Id entica lrequest
Error :=Short_Term_
D enial
To HL RA_
R equest. The e xisting entryshould be d elete d
Delete
U pdate thequeue To MSCVLR
CCBS_Request_Error(Erro r)
HLRA_Request
Update the queue
-
Pass
Fai l
No
Yes
Yes
No
Figure 11.1.2.2: Process HLRA_Request_Manager (sheet 4 of 10)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)69Release 14
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 condit ion
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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)70Release 14
Process HLRA_RequestManager(1,1) 6(10)
OPERATIVE
Deactiva te_CCBS
From MSC_ VLR
Check_Parameters
Resul t
Delete allrequests
Error :=Nega tiveresponse
Req uestexists
To MSCVLRDeactiva te_CCBS
Erro r(Error)
To individualHLRA_Request
Delete DeleteTo HL RA_R eque st
NOTE: To al l individual reque sts
OPERATIVE
Resul t :=Success
Deactiva te_CCBS_Ack(Resul t)
To MSC_VLR
Update thequeue
Que ueempty
OPERATIVE IDLE
Pass
Fa il
No
Yes
Yes
No
No
Yes
Figure 11.1.2.2: Process HLRA_Request_Manager (sheet 6 of 10)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)71Release 14
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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)72Release 14
Process HLRA_RequestManager(1,1) 8(10)OPERATIVERESUMING
Deactivate_CCBS From MSC_VLR
C heck_Parameters
See GSM 03.1 8
R esul t
D elete allre quests
Error :=Negativerespo nse
Requestexists
To MSCVLRDeactivate_CCBS
Error(Erro r)
To individualH LRA_Req uest Delete Dele te
To HLRA_Req uest
NOTE : To all individual requests
OPERATIVERES UMING
R esul t :=Success
Deactivate_CCBS_Ack(R esul t)
To MSC_ VLR
U pdate theq ueue
Anysuspen ded
requests
Stop_Resu me
To HLRA_Resume
Queuee mpty
OPERATIVERESUMING OPERATIVE IDLE
Pass
Fai l
No
Yes
Yes
No
No
Yes
No Yes
Figure 11.1.2.2: Process HLRA_Request_Manager (sheet 8 of 10)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)73Release 14
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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)74Release 14
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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)75Release 14
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 dest ination 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
State :=Request
CCBS_Notify_SS_Invocation
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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)76Release 14
Process HLRA_Request 2(5)
ACTIVE
Remote_User_Free
From destinationnetwork B
HLRA_CCBS_CHECK_
INTERACTIONS
Result
RecallTo HLRA_Recall_Manager
State :=Recall
CCBS_Notify_SS_Invocation
RECALL
CCBS_Suspend
To destinationnetwork B
State :=Frozen
CCBS_Notify_SS_Invocation
FROZEN
T3 Expiry
Cause :=T3-Timeout
CCBS_Cancel(Cause)
To destinationnetwork B
DeletedTo HLRA_Request_Manager
State :=Deleted
CCBS_Notify_SS_Invocation
CCBS_Cancel
From destinationnetwork B
DeleteFrom HLRA_Request_Manager
CCBS_Cancel
To destinationnetwork B
1
2
Pass
Fail
Figure 11.1.2.3: Process HLRA_Request (sheet 2 of 5)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)77Release 14
Process HLRA_Request 3(5)
RECALL
CompletedFrom HLRA_Recall_Manager
DeletedTo HLRA_Request_Manager
BusyFrom HLRA_Recall_Manager
Retain_supported
State :=Active
CCBS_Notify_SS_Invocation
ACTIVE
Failure(Cause)
From HLRA_Recall_Manager
Cause
Cause :=T4-Timeout
CCBS_Cancel(Cause)
To destinationnetwork B
DeletedTo HLRA_Request_Manager
1
CCBS_Cancel
To destinationnetwork B
3
RECALL
DeleteFrom HLRA_Request_Manager
CCBS_Cancel
To destinationnetwork B
1
CCBS_Cancel
From destinationnetwork B
DeletedTo HLRA_Request_Manager
CCBS_END
From destinationnetwork B
T3 Expiry
State :=Completed
CCBS_Notify_SS_Invocation
False
True T4 exp
else
Figure 11.1.2.3: Process HLRA_Request (sheet 3 of 5)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)78Release 14
Process HLRA_Request 4(5)RECALL
From HLRA_Recall_Manager
Suspend(Type,Sus_Cause)
To destinationnetwork B
CCBS_Suspend
To HLRA_Request_Manager
Suspend(Type,Sus_Cause)
State :=Suspend
CCBS_Notify_SS_Invocation
SUSPENDED
SUSPENDED
From HLRA_Request_Manager
Resume T3 ExpiryFrom destinationnetwork B
CCBS_Cancel
From HLRA_Request_Manager
Delete
To destinationnetwork B
CCBS_Resume
Cause :=T3-Timeout
To destinationnetwork B
CCBS_Cancel
CCBS_Cancel(Cause)
To destinationnetwork B
To HLRA_Request_Manager
Deleted
1
3
4
1
Figure 11.1.2.3: Process HLRA_Request (sheet 4 of 5)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)79Release 14
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
Locat ion_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.
FROZEN
DeleteFrom HLRA_Request_Manager
CCBS_Cancel
To destinationnetwork B
1
2
1
4
Pass
Fail
Figure 11.1.2.3: Process HLRA_Request (sheet 5 of 5)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)80Release 14
Process HLRA_RecallManager 1(4)
IDLE
RecallFrom individualHLRA_Request
RecallTo HLRA_Resumeto stop T11
CCBS_RUF
To 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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)81Release 14
Process HLRA_RecallManager 2(4)
CCBS_BUSY
CCBS_RUF_Ack(Result)
From MSC_VLR
Result
Start T12
CCBS_BUSY
Caus e :=Resu lt
Failure(Cause)
To individualHLRA_Request
Recall_EndTo HLRA_Resume
IDLE
Type := USERSus_Cause
:= Busy
Suspend(Type,Sus_Cause )
To ind ividualHLRA_Request
RUF Ac cepted
T4 expi ry
UDUB_IdleRUF Re jected
T10 expiry
UDUB _Busy
Figure 11.1.2.4: Process HLRA_Recall_Manager (sheet 2 of 4)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)82Release 14
Process HLRA_RecallManager 3(4)
CCBS_BUSY
T12 exp iryCCBS_RUF_Erro r(Error)
From MSC_VLR
Close thecommunication
between HLR and VLRError
Cause :=Failure
Type := NET
Sus_Cause:= Not Reach
To individua lHLRA_Request
Fai lu re(Caus e)
To individual
HLRA_Reques tNOTE: Becaus eMS is not reachableresuming is not
started
Suspend(Type,
Sus_Cause)
To HLRA_Resume
Recall_End
IDLE
ELSE
IMSI Detached
Restricted AreaNo Page ResponseAbsen t_Subs cribe rRadio Failure
CCom p Busy
Figure 11.1.2.4: Process HLRA_Recall_Manager (sheet 3 of 4)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)83Release 14
Process HLRA_RecallManager 4(4)
CCBS_BUSY
From CCBS_Coordina tor_HLR
CCBS_Call_Report(Outcome)
Stop T12
Outcome
Cause :=Failure
To individualHLRA_Request
Co mpletedTo individualHLRA_Request
Failure(Caus e)
To individu alHLRA_ Request
Busy
To HLRA_Resume
Recall_End
IDLE
Fai lure
Success Busy
Figure 11.1.2.4: Process HLRA_Recall_Manager (sheet 4 of 4)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)84Release 14
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 is
received.
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 cont inues.
A_Query(Sus_Cause)
To HLRA_Monitoring
-
Figure 11.1.2.5: Process HLRA_Resume (sheet 1 of 3)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)85Release 14
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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)86Release 14
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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)87Release 14
Process HLRA_Monitoring(1,1) 1(2)
Signals to / from lef t are to / fromCCBS_Coordinator_HLR unlessshown otherwise.Signals to / from right are to / from
HLRA_Resume uless shownotherwise
IDLE
IDLE
A_Query(Sus_Cause)
Start_Reporting
WAIT_FOR_ANSWER
*(IDLE)
Stop_Monitoring
Stop_Report ing
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. The
manufacturer is allowed to use othertechnics to achieve eff icient solution.
A_Idle
MONITORING
Yes
ELSE
Yes
No
Figure 11.1.2.6: Process HLRA_Monitoring (sheet 1 of 2)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)88Release 14
Process HLRA_Monitoring(1,1) 2(2)
Signals to / from lef t are to / fromCCBS_Coordinator_HLR unlessshown otherwise.Signals to / from right are to / from
HLRA_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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)89Release 14
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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)90Release 14
Procedure in the MSC to notifythe gsmSCF of the CCBS invocation
Procedure CCBS_Notify_SS_Invocation 1(1)
Signals to/from the leftare to/from the gsmSCF.
SS-CSI storedin HLR?
SS InvocationNotify (State)
SS-CSI appliesto CCBS?
Yes
Yes
No
No
Figure 11.1.2.8: Procedure CCBS_Notify_SS_Invocation
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)91Release 14
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 is set to the Send Routeing Info message. This functionality shall be applied only to the initial call leg. The procedure initialises also the CCBS Possible variable as True, the variable is accessible to all CCBS specific procedures in the GMSC.
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 be applied 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. It also 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 this call 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 message content. The procedure alters CCBS specific global variable CCBS Target which controls setting of the diagnostic field in the Release message towards the originating network.
Global variables Reconnect and Resume Call are specific to CAMEL and OR interaction respectively. They are initialised and updated in the process MT_GMSC or MT_CF_MSC, refer to TS 23.018.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)92Release 14
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 functionality
of 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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)93Release 14
Procedure CCBS_MT_GMSC_Check_CCBS_Indi cators 1(1)
Reco nnect = Trueor
Resu me Call = True
CCBS Call
Te st the para meter recei vedin SRI. I f absent, False exi tshal be taken.
Keep CCBS Call
indicator
Indicator to theoutgoing IAM message
CCBS Cal lIndicator :=
True
CCBS Cal lIndicator :=
False
CCBS Cal lIndi cator :=
False
No
Yes
Ye s
No
True
False
Figure 11.2.1.2: Procedure CCBS_MT_GMSC_Check_CCBS_Indicators
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)94Release 14
Procedure CCBS_MT_GMSC_Remove_Indicators_Store_FWT 1(1)
Reconnect = TrueorResume Call = True
Test the parameter receivedin SRI Ack. If absent False
exit 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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)95Release 14
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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)96Release 14
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
Call Completion TreatmentIndicator set to Reject CallCompletion Service Request?
Call CompletionTreatment Indicatorpresent in SII2?
True
No
Yes
Yes
No
No
Resume _Call_Handling
No
Yes
Release
No
Yes
Yes
False
Yes
No
Yes
No
Figure 11.2.1.5: Procedure CCBS_MT_GMSC_Check_CCBS_Possible
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)97Release 14
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 the queue or not.
The process has two states "idle" and "active". In the "idle" state there are no "operative" requests in the queue i.e. thereare only suspended requests or no requests at all. In the "active" state there is at least one "operative" request in the 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 external interface (SSAP signalling) are handled by this process.
Retention is handled by this process. The individual request is informed by the Recall manager process about the outcome 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 has kept 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 this process. The response indicates that user B is idle guarded i.e. a CCBS Recall can be initiated. Hence, the process asks the 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 external interface 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 in the 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 a CCBS Recall.
The process is controlled by the "HLRB_Recall_Manager" process which was formerly in charge of detecting the recall condition.
When the process is started, it invokes the monitoring function in the MSC/VLR and awaits the first event report. The process 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, the process 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 this information by sending a "B_Query" signal to the monitoring process. The process "HLRB_Monitoring" gives this information only if the "B_Query" signal has been received. This is done by sending the signal "B_Guarded" to the Recall Manager and it is only done once per request. The monitoring process keeps track on whether a query was received or not by appropriate state changes.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)98Release 14
As the monitoring process is in charge for the idle guard function, it also controls the blocking of incoming calls during the idle guard time (T8). Hence, when the recall manager process has sent a "B_Query" (i.e. a CCBS request needs to be processed) then the monitoring process starts the corresponding blocking along with T8. The blocking is only stopped if T8 does not expire. If T8 expires, then blocking is still needed for the following CCBS Recall. The responsibility for controlling 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 the reporting functionality of the outcome of the CCBS Call is not blindly triggered whenever there is a terminating CCBS Call.
The process has three different states: "idle", "Blocking" and "Recall Blocking". The "Idle" state reflects the case when blocking is disabled. In the "Blocking" state all incoming calls are blocked (e.g. while T8 is running). The "Recall Blocking" state allows one CCBS Call to pass, which will trigger the CCBS Call delivery reporting in the MSC/VLR via the TS 23.018 process "SRI_HLR". When this happens, the process will automatically change back to state "Blocking" as no 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 will change state to "Blocking". As soon as the process "HLRB_Recall_Manager" has initiated a CCBS Recall, it will cause a state 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 request in the TS 23.018 process "SRI_HLR".
For Figure 11.2.2.6, sheet 2: The procedure Handle_CFB is specified in TS 23.018, clause 7.3.2.6.
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 Calls can proceed, others will fail with busy or forward indication. For CCBS Call CCBS Call Indicator is set to the Provide Roaming 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 call report.
The handling of multiple requests in HLR B can be further clarified by the diagram shown in figure 11.2.2.1.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)99Release 14
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_Re ject_Request
CCBS_Request
Start_Recall_ManagerStop_Recall_ManagerSelect_Request_Response
Select_Request
Selection_Req
Re-Acti vated
De letedInactive
Remote_User_FreeCCBS_Cance lCCBS End
CCBS_ResumeCCBS_CancelCCBS_Suspend
Send_RUFRecall_Report
End
Start_BlockingRecall_Block
Start_Moni toring
Stop_MonitoringB_Query
Cal l_DeliveryB_Guarded
SRI_Received_Ack
SRI_ReceivedStart_ReportingStop_Reporting
Event_Report
CCBS_Call_Report
CCBS_Coordinator_HLR
Start_Blocking
Stop_Blocking
Location_Update
Figure 11.2.2.1: HLRB_Processes
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)100Release 14
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 HLRB Request Manager.
CCBS_Request_Ack: When the HLRB_Request_Manager acknowledges the activation, it sends CCBS_Request Ack to originating network.
CCBS_Reject: If the HLRB_Request_Manager does not accept the activation attempt, it sends CCBS_Reject to the originating 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_Resume message to HLRB Request.
CCBS Cancel: When a request is cancelled in the originating network, it sends a CCBS Cancel message to HLRB Request.
Remote_User_Free: HLRB_Request sends Remote_User_Free to the originating network to inform the originating network that destination B is now idle.
CCBS_Cancel: If a CCBS Request is cancelled in the destination network, HLRB_Request sends CCBS_Cancel to the originating network.
TC_END: If a CCBS Call is successfully delivered to destination B, then HLRB_Request ends the dialogue with the originating 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 the request 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 queue status 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 manager receives 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 "Recall Block" to HLRB_Blocking so that one CCBS Call can be delivered to destination B, but other normal incoming calls are blocked.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)101Release 14
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 Request manager. 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 the monitoring 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 the recall 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 originating network 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 Recall Manager process.
Relation HLRB_Recall_Manager and HLRB_Monitoring
Start_Monitoring: When the Recall manager process is started by the Request manager process, the Recall manager sends "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 manager sends "Stop_Monitoring" to the HLRB_Monitoring process.
B_Query: HLRB_Recall_Manager requests the HLRB_monitoring process to get informed when destination B has become 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.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)102Release 14
Process HLRB_RequestManager 1(3)
Signal s to and from the left
are to and from the originatingnetwo rk unle ss sp ecifie d otherw ise
IdleIn this state th ere are either no CCBS Req uestsin the queue or the queue contains only inactive(su spended or quiesent) requests
IdleCCBS_Request(Retain_supported )
Note: R etention informationma y be recei ved in theCCBS Request.
Refer to ETS 300 3 58
From HLRB_R equest Re-Activated Deleted
From HLRB_Request
CCBS service
provisione d indestinationnetwork
Update requestqueue
Up date requestqu eue
Reason :=long te rm
denial
queuefull
HLRB_Request
Reason :=short term
denial
To HLRB_R ecal l_
Manage r
Start_Recall _
Manager
Update requestqueue CCBS_Reje ct_
Requ est
(Reason)
Retention su pportedin the D estina tion B
ne twork
- Active -
Retain _supported
:= Fal se
CCBS_Request_Ack(Retain_supported )
NOTE : Retention informationmay be sent in the C CBS Request AckRe fer to ETS 3 00 358
Store Retainsupported
To HLRB_Recal l_Manager
Start_Re call_Manager
In this state, there isat least one active reque st
Active
No
Yes
No
Yes
No Yes
Figure 11.2.2.2: Process HLRB_REQUEST_MANAGER (sheet 1 of 3)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)103Release 14
Process HLRB_RequestManager 2(3)
Active
DeletedFrom HLRB_Request
Upd ate requestqueue
Que ueempty
Only inactiverequests inqueue
Stop_Rec all_Man ger
To HLRB_Recall_Mana ger
Idle
Continue_Monitoring
To CCBS_Coordinator_HLR
-
Inacti veFrom HLRB_Request
Update requestqueue
CCBS_Request(Retain_
supported)
Note: Retention information
m ay b e rece ived in theCCBS Reque st. Refer to ETS 300 358
queuefull
HLRB_Reques t
Update requestqueue
Re tention supportedin the Des tinatio n Bnetwork
Retain_su pported:= False
CCBS_Request_Ack (Retain_supported)
NOTE: Rete ntion informationmay be sent in the CCBSReques t Ack
Refer to ETS 3 00 358
Store Retainsu pported
Acti ve
Rea son :=short term
denial
CCBS_Reject_Request
(Reas on)
No
Yes
No
Yes
No
No Yes
Yes
Figure 11.2.2.2: Process HLRB_REQUEST_MANAGER (sheet 2 of 3)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)104Release 14
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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)105Release 14
Process HLRB_Request 1(6)
Signals to and from the lef tare to and from the originatingnetwork unless specif ied 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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)106Release 14
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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)107Release 14
Process HLRB_Request 3(6)
Selected
Send_RUFFrom HLRB_Recall_Manager
CCBS_Suspend
CCBS_Cancel
T7_Expiry SS_EventFrom 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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)108Release 14
Process HLRB_Request 4(6)
Selected
R ecal l_Report(Outcome)
From HLRB_Reca ll_Manager
Outcome
Re ason:=Outcome
Re tainsupported
CCBS_Cancel
CCBSEnd
CCBS_Cancel
(Reason)
Dele ted To HLRB_Re quest_Manager
Operative
T9_Expiry
N DUB
Fai lure Success
Fa lse
True
Figure 11.2.2.3: Process HLRB_REQUEST (sheet 4 of 6)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)109Release 14
Process HLRB_Request 5(6)
Suspended
CCBS_Resume SS_Event
From Supplementaryservice handling indicatingthat service status has beenchanged
To HLRB_Request_Manager
Re-ActivatedHLRB_CCBS_
Check_Interactions
Result
OperativeQuiescentSuspended
Suspended
Fail
Pass
Figure 11.2.2.3: Process HLRB_REQUEST (sheet 5 of 6)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)110Release 14
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
OperativeQuiescentSuspended
SuspendedQuiescentOperative
Pass
Fail Fail
Pass
Figure 11.2.2.3: Process HLRB_REQUEST (sheet 6 of 6)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)111Release 14
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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)112Release 14
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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)113Release 14
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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)114Release 14
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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)115Release 14
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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)116Release 14
Process HLRB_Monitoring 3(7)
B_Not_IdleNo_B_Query
Event_Report(Status)
Status
Start T8
Start_Blocking
To 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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)117Release 14
Process HLRB_Monitoring 4(7)
B_Not_IdleB_Query
Event_Report(Status)
From CCBS_Coordinator_HLR
Stop_Monitoring
From HLRB_Recall_Manager
StatusStop_Report ing
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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)118Release 14
Process HLRB_Monitoring 5(7)
B_IdleNo_B_Query
Event_Report(Status)
From CCBS_Coordinator_HLR
T8 Expiry B_QueryFrom HLRB_Recall_Manager
Stop_Monitoring
From HLRB_Recall_Manager
Status Stop T8
Stop_Blocking
To HLRB_Blocking
Stop_Report ing
To CCBS_Coordinator_HLR
B_Not_IdleNo_B_Query
-B_Idle_Guarded
No_B_QueryB_Idle
B_QueryIdle
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
Status
To HLRB_Blocking
Stop_Blocking
Start_Report ing
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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)119Release 14
Process HLRB_Monitoring 6(7)
B_IdleB_Query
Event_Report(Status)
From CCBS_Coordinator_HLR
T8 ExpiryStop_Monitoring
From HLRB_Recall_Manager
Status Stop T8
Stop T8
Stop_Blocking
To HLRB_Blocking
To HLRB_Blocking
Stop_Blocking
B_GuardedTo 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
Status
To 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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)120Release 14
Process HLRB_Monitoring 7(7)
B_Idle_GuardedNo_B_Query
Event_Report(Status)
From CCBS_Coordinator_HLR
B_QueryFrom HLRB_Recall_Manager
Stop_Monitoring
From HLRB_Recall_Manager
Status
Start_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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)121Release 14
Process HLRB_BLOCKING 1(3)
*
Stop_Blocking
From HL RB_R ecal l_Manager o rHLRB_Moni toring
Idle Idle
Idle
SRI_ Rece ived Fro m GSM 03.18SRI_HLR(CC BS_Handl ing_HLR)
Start_Blocking
From HL RB_
Mo nitoring
Result := OK
SRI_ Rece ived_Ack(Resul t)
To GSM 03.18SRI_HLR(CC BS_Handl ing_HLR)
- Blocking
Figure 11.2.2.6: Process HLRB_BLOCKING (sheet 1 of 3)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)122Release 14
Process HLRB_BLOCKING 2(3)
Blocking
From GSM 03.18SRI_HLR (CCBS_Handling_HLR)
SRI_Received
From HLRB_Recall_Manager
Recall_Block
StopBlocking
From HLRB_Monitoring
See TS 23.018 Handle_CFBRecall
BlockingIdle
Result =Forward?
max queue size > 0and CCBS supportedin the VMSC?
Result =Busy?
CCBS Target:= True
CCBS Target:= False
Result:= Fail
Result :=Forward
max queue size > 0and CCBS supportedin the VMSC?
Result := Busy,CCBS Possible
Result := Busy,CCBS Not Possible
To GSM 03.18SRI_HLR (CCBS_Handling_HLR)
SRI_Received_Ack(Result,CCBS Target)
-
Yes
No
Yes
No
No
Yes
Yes
No
Figure 11.2.2.6: Process HLRB_BLOCKING (sheet 2 of 3)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)123Release 14
Process HLRB_BLOCKING 3(3)
Handle_CFB
Result =Forward?
max queue size > 0and CCBS supportedin the VMSC?
Result =Busy?
CCBS Target:= True
CCBS Target:= False
Result:= Fail
Result :=Forward
To GSM 03.18SRI_HLR (CCBS_Handling_HLR)
SRI_Received_Ack(Result)
RecallBlocking
max queue size > 0and CCBS supportedin the VMSC?
Result := Busy,CCBS Possible
Result := Busy,CCBS Not Possible
RecallBlocking
SRI_Received
From GSM 03.18SRI_HLR (CCBS_Handling_HLR)
CCBSCall?
CCBSsupported in
VMSC?
Keep CCBS CallIndicator :=
True
Keep CCBS CallIndicator :=
False
Result := OK
SRI_Received_Ack(Result)
Blocking
See TS 23.018
To GSM 03.18SRI_HLR (CCBS_Handling_HLR)
Yes
No
Yes
No
No
Yes
No
Yes
NoNo
Yes
Yes
Figure 11.2.2.6: Process HLRB_BLOCKING (sheet 3 of 3)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)124Release 14
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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)125Release 14
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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)126Release 14
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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)127Release 14
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 diagnostic value 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 call Not_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 forward the 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 in the 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 in the 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 the user has elected to be target of CCBS requests, CCBS Target is set to True.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)128Release 14
Procedure CCBS_MT_MSC_Check_Forwarding 1(1)
CCBStarget
Pa rameter is set
when SIFIC_Ackis received fro mVL R
Cause = BusyorCause = No circuit
channel availa ble
CCBS Target:= True
Al te r the i nternal variablewhich con trols setting of
the diagn ostic field
CCBS Target:= False
True
Yes
No
False
Figure 11.2.3.1: Procedure CCBS_MT_MSC_Check_Forwarding
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)129Release 14
Procedure CCBS_Handle_PRN 1(1)
Store CCBS Callindicator alongwith the MSRN
Figure 11.2.3.2: Procedure CCBS_Handle_PRN
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)130Release 14
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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)131Release 14
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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)132Release 14
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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)133Release 14
Procedure CCBS_ICH_Report_Not_Reachable 1(1)
CCBS Call
Outcome :=Absent Subscriber
CCBS_Call_Delivery(Outcome)
To CCBS_Monitoring_VLRNot_ReachableTo CCBS_Monitoring_VLR
Yes
No
Figure 11.2.3.6: Procedure CCBS_ICH_Report_Not_Reachable
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)134Release 14
Procedure CCBS_ICH_Handle_NDUB 1(1)
Busy conditio n :=ND UB
CC BS C all
Netw ork option:Release o r forw ard
Outcome :=Failure
Outcome :=ND UB
To CCBS_Monitoring_VLR
CCBS_Call _Delivery
(Outcome)
CCBS_Call _Delivery
(Outcome)
To C CBS_Monitoring_VLR
Re sult :=Fo rward
Re sult :=Re lease
Yes
No
Forwa rd Release
Figure 11.2.3.7: Procedure CCBS_ICH_Handle_NDUB
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)135Release 14
Procedure CCBS_ICH_Handle_UDUB 1(1)
Busy condition :=UDUB
Figure 11.2.3.8: Procedure CCBS_ICH_Handle_UDUB
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)136Release 14
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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)137Release 14
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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)138Release 14
Pro cedure CCBS _ICH_ Set_ CCBS_Target 1(1)
Busy condition
CCBSAllow ed
Has des tination B electedto be a target o f reques ts
CCBS Target:= True
CCBS Target:= F al s e
NDUB
Yes
No
UDUB
Figure 11.2.3.11: Procedure CCBS_ICH_Set_CCBS_Target
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)139Release 14
11.3 Processes and procedures common in originating and destination 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 only once towards MSC, CCBS_Call_Report messages are directed to correct queue and Status information is distributed to both 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 internal CCBS 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 monitoring process 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 monitoring process 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 VLR monitoring process.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)140Release 14
Process CCBS_MONITORING_VLR 1(4)
Signal s to / from left are to / from HLR unless shown otherwise
Idle
Start_Report ing
Ch eck_Parame ters
See GSM 03.18
Re sult
Event_R eporting:= True
Error :=Negativerespo nse
IMSIDe tached
Start_Reporting _
Error(Erro r)
Idle
Ro amin g inLA al low ed
Status :=CC BS_Not_
Re achab le
Start_Status_Enqui ry
To C CBS_Monitoring_ MSC
Start_Report ing_Ack(Status)
Wait_For_Re spon se
MonitoringDe tached
Status_EnquiryResul t
From CCBS_Mo nitori ng_MSC
CC BS_No t_Idle
Status :=CC BS_N ot_Id le
Status :=CCBS_Idle
Start_Report ing_
Ack(Status)
Start_Re porting_
Ack(Status)
MonitoringNo t Idle
Mon itorin gIdle
Pass
Fai l
No
Yes
N o
Yes
Yes
N o
Figure 11.3.1: Process CCBS_Monitoring_VLR (sheet 1 of 4)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)141Release 14
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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)142Release 14
Process CCBS_MONITORING_VLR 3(4)
Signals to / f rom lef t are to / from HLR unless shown otherwise
MonitoringIdle
Not_Idle
From 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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)143Release 14
Process CCBS_MONITORING_VLR 4(4)
Signals to / f rom lef t are to / from HLR unless shown otherwise
Note: Only MT CCBS Callreporting is interacting withthe monitoring process. MOcall reporting is shown on
VLR_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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)144Release 14
Process CCBS_MONITORING_MSC 1(1)
Signals to/f rom the leftare to/from the VLR;signals to/from the rightare to/from the BSS
unless 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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)145Release 14
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_Reques t_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)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)146Release 14
Process CCBS_Coordinator_HLR 2(6)
Sig nals to / from le ft
are to / from the VLRunless shownotherwise
Mon itoringA
C CBS_Call _
R eport(Mode,Outcome,Status)
Note: CCBS_C all_Re portcan exist on A side w ithoutongoing monitoring in the MSC
Stop_Re porting
From HLRA_
Monitoring
See GSM 03.18C heck_
Pa rametersStop_Reporting
R esul t Idle
Mode
CCBS_Ca ll_Report(Outcome)
To HLRA_
Recal l_Manager
Error :=Negative
response
Moni toringACCBS_Ca ll_
Report_Error(Error)
C CBS_Call _R eport_Ack
Start_Reporting_Error(Erro r)
Eve nt_Report(Status)
-
See GSM 03.1 8 Check_Parameters
Resul t
Error :=Negativeresponse
Event_Re port_
Error(Error)
Eve nt_Report_
Ack
Status :=Not_Reachable Store Status
Event_Re port
(Status)
-
Pass
Fai l
A
B
Fail
Pass
Figure 11.3.3: Process CCBS_Coordinator_HLR (sheet 2 of 6)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)147Release 14
Process CCBS_Coordinator_HLR 3(6)
Signals to / f rom lef tare 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 subsc riberdatahandling inHLR
Start_Reporting
-
MonitoringB
Start_Reporting
From HLRA_Monitoring
Statusavailable
EventReport(Status)
To HLRA_Monitoring
MonitoringA + B
Restore_Data
From subsc riberdatahandling inHLR
Start_Reporting
-
Yes
No
Yes
No
Figure 11.3.3: Process CCBS_Coordinator_HLR (sheet 3 of 6)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)148Release 14
Process CCBS_Coordinator_HLR 4(6)
Sig nals to / from le ft
are to / from the VLRunless shownotherwise
Moni toringB
Start_Report ing_
Ack(Status)
Start_Report ing_
Error
From HLRB_
Moni toring
Stop_Reporting
Store StatusStatus :=
No t_Reachable
To HLRB_
Moni toring
Event_R eport
(Status)
Stop_Reporting
- Idle
MonitoringB
Event_Re port(Status)
CCBS_Call_Report(Mode,Outco me,
Status)
Check_Parameters
See GSM 03.18 Ch eck_Parame ters
See GSM 03.18
Resu lt Re sult
Error :=Nega tiveresponse
Store StatusErro r :=Negative
response
CCBS_C allReport_Error
(Error)
CCBS_Call_Report_AckEvent_
Re port_Ack
Event_Report_Error(Error)
Outco me := Fai lureStatu s :=
Not_reachableStatus :=Not_Reachable
Mode
To HLRB_Moni toring
Event_Report(Status)
To HLRA_R ecal l_Manage r
CCBS_Call_Report(Outcome)
CCBS_Call_Repo rt(Outcome,
Status)
To H LRB_Moni toring
Store Status
-
Pa ss
Fail Fa il
Pass
A
B
Figure 11.3.3: Process CCBS_Coordinator_HLR (sheet 4 of 6)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)149Release 14
Process CCBS_Coordinator_HLR 5(6)
Sig nals to / from le ftare to / from the VLRunless shown
otherwiseMonitoring
A + B
Event_R eport(Status)
Start_Reporting_Ack(Status)
Start_R eporti ng_Error
C CBS_Call_R eport(Mode,Outcome,
Status)
C heck_Pa rameters
Status :=Not_Reachable
Check_Pa rameters
R esul t Resul t
Error :=Negativerespo nse
Error :=N egativere sponse
Event_Report_Ack C CBS_Call_
R eport_ Ack
CCBS_Ca ll_Report_
Error(Erro r)
Event_R eport_
Error(Error) Outco me:=Fai lureStatus :=
Not_R each able
Status :=N ot_Re achab le
Mo de
Event_Report
(Status)
To HLRB_Monitoring
Event_Report(Status)
To HLRA_Monitoring
To HLRB_Monitoring
CC BS_Call_Re port(Outcome,
Status)
Moni toringA + B
Event_Report
(Status)
To HL RB_Monitoring
Event_Report(Status)
To HL RA_Monitoring
Store StatusTo HLRA_R ecal l_
Manage r
CCBS_Call_Report
(Outcome)
-
Fail
Pass Fai l
Pass
B
A
Figure 11.3.3: Process CCBS_Coordinator_HLR (sheet 5 of 6)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)150Release 14
Process CCBS_Coordinator_HLR 6(6)
Signals to / f rom lef tare to / from the VLRunless shownotherwise
MonitoringA + B
Stop_Reporting
From HLRA_Monitoring
MonitoringB
Stop_Reporting
From HLRB_Monitoring
MonitoringA
Restore_Data
From subsc riberdatahandling inHLR
Start_Reporting
-
Figure 11.3.3: Process CCBS_Coordinator_HLR (sheet 6 of 6)
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)151Release 14
Pro cedure CCBS _Set_Diagnostic_For_ Release 1(1)
CCBSTarget
Ca ll Co m pletio nTreatme nt Indicatorpres ent in SII2?
Call Com pletion Treatm entIndicator set to Reject CallCom pletion Service Reques t?
Diagnos tic :=CCBS Pos s ib le
D iag no stic :=C CBS Not Pos si ble
Are the c onditi on s s uc hthat th e subsc riber ca nb e a targ et o f C CBSReques ts True
Yes
No
Yes
No
False
Figure 11.3.4: Procedure CCBS_Set_Diagnostic_For_Release
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)152Release 14
Procedure CCBS_Report_Not_Idle 1(1)
Not_Idle To CCBS_Monitoring_VLR
Figure 11.3.5: Procedure CCBS_Report_Not_Idle
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)153Release 14
Procedure CCBS_Report_MS_Activity 1(1)
Reason:=CM SERV TYPE
MS Act ivity To CCBS_Monitoring_VLR
Figure 11.3.6: Procedure CCBS_Report_MS_Activity
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)154Release 14
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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)155Release 14
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 be required to store both the data for HLR A and the data for HLR B against a given subscriber.
12.1 Originating Network Data
The following logical states are applicable for the CCBS service in the originating network (refer to TS 23.011 for an explanation 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 per subscriber basis. The HLR shall store the following information for each CCBS Request that is successfully activated by subscriber 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.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)156Release 14
12.2 Destination Network Data
The following logical states are applicable for the CCBS service in the destination network (refer to TS 23.011 for an explanation 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 per subscriber 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 VLR
If 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 HLR shall 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 each other to the VLR.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)157Release 14
13 State transition model
13.1 State transition model for the CCBS service in the originating network
Figure 13.1.1 shows the successful cases of transition between the applicable logical states of the CCBS service in the originating 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 the destination network
Figure 13.2.1 shows the successful cases of transition between the applicable logical states of the CCBS service in the destination 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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)158Release 14
13.3 State transition model for a CCBS Request
Figure 13.3.1 shows the successful cases of transition between the applicable logical states of a CCBS Request. The state 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 requests allowed 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
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)159Release 14
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 VLRs
Originating 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.
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)160Release 14
Annex A (informative):Message flow diagrams showing a successful CCBS requestThe 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).
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)161Release 14
OC
H_
MS
C
HL
RA
HL
RB
MT
_G
MS
CIC
H_M
SC
ICH
_V
LR
MS
VL
RM
SC
MS
C /
VL
RG
MS
CM
S
Se
t-up
Initia
l Add
ress
Me
ssa
ge
Re
lease
Initi
al A
ddre
ss
Me
ssa
ge
Re
lease
(C
CB
S P
oss
ible
)
SIF
IC
SIF
IC N
eg
(ND
UB
)
OP
ER
AT
IVE
CC
BS
Poss.
CC
BS
Re
qu
est
CC
BS
Req
uest
Sta
rts
HLR
A_
Re
quest
Sta
rts
HLR
B_
Req
ue
stC
CB
S R
equ
est
CC
BS
Req
uest A
ck
Sta
rt_
Reca
ll_M
ana
ge
r
IDL
EID
LE
AC
TIV
E
WA
IT_F
OR
B_
GU
AR
DE
D
IDL
E
CC
BS
_M
on
ito
rin
g_
MS
C
CC
BS
_M
on
ito
rin
g_
VL
R
WA
IT
Sta
rt_
Mo
nito
rin
g
B_Q
uery
Sta
rt_R
ep
ort
ing
Sta
rt_
Sta
tus
En
quir
y
Sta
tus
En
quir
yR
esu
lt(N
ot
Idle
)
MO
NIT
OR
ING
MO
NIT
OR
ING
,N
OT
ID
LE
Even
t_R
epo
rt (
CC
BS
Not
Idle
)
B_
NO
T_ID
LE
NO
_B
_Q
UE
RY
B_
QU
ER
Y
B_N
OT
_ID
LE
B_
QU
ER
Y
CC
BS
_R
eq
Ack
OP
ER
AT
IVE
OP
ER
AT
IVE
AC
TIV
E
WA
IT_
FO
RA
NS
WE
R
IDL
E
CC
BS
_R
eq
ue
st_
Ack
Re
lease
(CC
BS
Ack
)
HL
RB
_M
on
ito
rin
g
HL
RB
_R
eca
ll_
Man
ag
er
HL
RB
_R
eq
uest_
Man
ag
er
HL
RB
_R
eq
uest
HL
RA
_R
eq
uest_
Man
ag
er
HL
RA
_R
eq
uest
ICH
_M
SC
MO
NIT
OR
ING
,ID
LE
IDL
E
Ca
ll E
nd
Even
t_R
ep
ort
(C
CB
S_
Idle
)
CC
BS
_C
he
ck_
La
st_C
all
Sta
rt_
Blo
ckin
g
T8
Exp
iry
B_
IDLE
B_
QU
ER
Y
B_G
uard
ed
B_
IDLE
_G
UA
RD
ED
NO
_B
_Q
UE
RY
WA
IT_
FO
R_
SE
LE
CT
ION
_R
ES
PO
NS
ES
ELE
CT
ED
AC
TIV
E
Se
lect
_R
eq
uest
Se
lect
ion
_R
eq
Se
lect
_R
eq
ue
st_R
esp
on
se
Se
nd
_R
UF
Re
call
Blo
ckR
em
ote
User
Fre
e
SE
LE
CT
ED
BLO
CK
ING
RE
CA
LL_
BL
OC
KIN
GW
AIT
_F
OR
_C
CB
S_
CA
LL
HL
RB
_B
loc
kin
g
Y
Sta
rt T
8
CC
BS
_C
oo
rdin
ato
r_H
LR
Mo
nito
rin
g B
Mo
nito
rin
g B
Mo
nito
rin
g B
Event_
Rep
ort
(CC
BS
_Id
le)
Even
t_R
ep
ort
Ack
Sta
rt_
Re
po
rtin
g_
Ack
Sta
rt_
Re
po
rtin
g
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)162Release 14
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)163Release 14
Reca
ll_R
ep
ort
(su
cce
ss)
MS
Co
nn
ect
ion
est
ablis
he
d
If Q
em
pty
:
If h
ave
su
spen
ded r
eq
ue
sts:
Els
e::
IDL
E
MT
_G
MS
C
MS
C_
CC
BS
_R
ec
all
_M
an
ag
er
VL
R_
CC
BS
_R
ec
all_
Ma
nag
er
Reca
ll
RE
CA
LL
CC
BS
_B
US
Y
CC
BS
_R
UF
Pa
ge_
MS
_F
or_
Reca
llP
age
Pro
cessA
cce
ss
Re
que
st
CM
_S
erv
ice_
Pro
mp
t
Sta
rt C
C
CC
BS
_C
all_
Info
CC
BS
_C
all_
Info
_A
ck
Co
mp
lete
_R
eca
ll_A
ck
Com
ple
teR
eca
ll
Reca
llR
eca
ll
CC
BS
_S
etu
pR
eca
ll_A
ckC
CB
S_
RU
F_A
ck (
acc
ep
t)
CC
BS
_B
US
YW
AIT
_F
OR
_C
AL
L_D
EL
IVE
RY
OG
_C
all_
Se
tup
_M
SC
:O
CH
_C
CB
S_V
LR
SIF
OC
Com
ple
teC
all
Call
Pro
ceedin
g
Initia
l Add
ress
Me
ssag
e
Addre
ss C
om
ple
te , A
nsw
er
/ C
on
nect
Co
nne
ct A
ck
CC
BS
Ca
llD
eliv
ery
(su
cce
ss)
WA
IT_F
OR
_C
LE
AR
VL
R_
CC
BS
_R
eca
ll_
Ma
nag
er
IDL
E
ICH
_M
SC
ICH
_V
LR
SIF
IC
IDL
E
Initia
l Add
ress
Su
cces
sfu
lC
all
WA
IT_F
OR
_C
LE
AR
IDL
E
Re
lea
se
Ad
dre
ss C
om
ple
te , A
nsw
er
/ C
onne
ct
WA
IT_
FO
R_
CL
EA
R
HL
RB
_M
on
ito
rin
gH
LR
B_
Re
ca
ll_
Man
ag
er
HL
RB
_R
eq
ue
st_
Ma
nag
er
HL
RB
_R
eq
ue
st
CC
BS
_C
all
De
livery
(su
cce
ss)
Ca
ll D
eliv
ery
(su
cce
ss)
If Q
is
em
pty
:S
top
_R
ecall_
Man
ager
CC
BS
_E
ND
De
lete
d
IDL
EID
LE
IDLE
AC
TIV
ES
ELE
CT
ED
RE
CA
LL_
BLO
CK
ING
WA
IT_
FO
R_
CC
BS
_C
ALL
IDLE
HL
RB
_B
loc
kin
g
Sto
p B
lock
ing
Sto
p B
locki
ng
Sto
pM
on
itori
ng
Sto
p_
Repo
rtin
g
CC
BS
_M
on
ito
rin
g_
MS
C
CC
BS
_M
on
ito
rin
g_
VL
R
MO
NIT
OR
ING
MO
NIT
OR
ING
,ID
LE Sto
p S
tatu
sE
nquir
y
IDL
EID
LE
IDL
E
Sto
p B
locki
ng
ICH
_M
SC
IDLE
Re
lea
se
IDL
E
OP
ER
AT
IVE
IDLE
CC
BS
_C
all_
Repo
rt (
Mo
deA
, su
ccess
)
De
lete
d
Co
mp
lete
d
IDLE
OP
ER
AT
IVE
Re
lease
Re
lea
se
OP
ER
AT
IVE
RE
SU
MIN
G
WA
IT_
FO
R_
CA
LL_D
ELIV
ER
Y
B_ID
LE
_G
UA
RD
ED
NO
_B
_Q
UE
RY
B_
IDLE
_G
UA
RD
ED
NO
_B
_Q
UE
RY
B_Q
uery
WA
IT_
FO
RB
_G
UA
RD
ED
Sta
rt B
locki
ng
B_G
uard
ed
Sele
ct_R
equ
est
(Go t
o Y
)
B_ID
LE
_G
UA
RD
ED
NO
_B
_Q
UE
RY
WA
IT_
FO
R_
SE
LE
CT
ION
_R
ES
PO
NS
E
IDLE
BLO
CK
ING
HL
RA
_R
ec
all
_M
an
ag
er
HL
RA
_R
eq
ue
st_
Man
ag
er
HL
RA
_R
eq
ue
st
CC
BS
_C
all_
Re
port
CC
BS
_C
all_
Re
port
Ack
CC
BS
_C
oo
rdin
ato
r_H
LR
Mo
nito
rin
g B
CC
BS
_C
oo
rdin
ato
r_H
LR
IDLE
CC
BS
_C
all_
Rep
ort
(su
cce
ss)
CC
BS
_C
all
Rep
ort
(su
cce
ss)
IDLE
Sto
p_
Re
port
ing
Mo
nito
rin
g B
INSIDabcdef_:MS_0001MS_0001IN
SID
abcd
ef_
:MS
_000
1M
S_0
001
3GPP
3GPP TS 23.093 V14.0.0 (2017-03)164Release 14
Annex B (informative):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#03CN#06 23.093 3.0.0 001r3 R99 3.1.0 Approved at CN#06CN#06 23.093 3.0.0 002r3 R99 3.1.0 Approved at CN#06CN#09 23.093 3.1.0 003r1 R99 3.2.0 Handling of the Call Completion Treatment
IndicatorCN#09 23.093 3.1.0 004 R99 3.2.0 Handling of the Call Diversion Treatment
IndicatorCN#11 23.093 3.2.0 Rel-4 4.0.0 Release 4 after CN#11CN#16 23.093 4.0.0 Rel-5 5.0.0 Release 5 after CN#16CN#26 23.093 5.0.0 Rel-6 6.0.0 Release 6 after CN#26CT#36 23.093 6.0.0 Rel-7 7.0.0 Upgraded unchanged from Rel-6CT#37 23.093 7.0.0 0005 Rel-7 7.1.0 HLR procedure on Location Update from the
current VLRCT#37 23.093 7.0.0 0006 Rel-7 7.1.0 Incompatible terminal handling in VLRCT#38 23.093 7.1.0 0007 Rel-7 7.2.0 Call forwarding on busy handling in HLRCT#40 23.093 7.2.0 0008r1 Rel-7 7.3.0 Missing signal in process
VLR_CCBS_Recall_ManagerCT#42 23.093 7.3.0 Rel-8 8.0.0 Upgraded unchanged from Rel-7CT#46 23.093 8.0.0 - Rel-9 9.0.0 Update to Rel-9 version (MCC)2011-03 23.093 9.0.0 - Rel-10 10.0.0 Update to Rel-10 version (MCC)2011-11 23.093 10.0.0 Rel-10 10.0.1 Editorial correction to previous line in history
table2012-09 23.093 10.0.1 - Rel-11 11.0.0 Update to Rel-11 version (MCC)
2014-09 23.093 11.0.0 - Rel-12 12.0.0 Update to Rel-12 version (MCC)
2015-12 23.093 12.0.0 - Rel-13 13.0.0 Update to Rel-13 version (MCC)
2017-03 23.093 13.0.0 - Rel-14 14.0.0 Update to Rel-14 version (MCC)