Embed Size (px)
Citation preview
3G TS 23.078 V3.2.0 (1999-11)Technical Specification
3rd Generation Partnership Project;Technical Specification Group Core Network;
(CAMEL) Phase 3 - Stage 2(3G TS 23.078 version 3.2.0)
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposesof 3GPP.The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of thisSpecification.Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners' PublicationsOffices.
3GPP
3G TS 23.078 V3.2.0 (1999-11)23G TS 23.078 version 3.2.0
ReferenceDTS/TSGN-0223078U
Keywords<keyword[, keyword]>
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.
© 1999, 3GPP Organizational Partners (ARIB, CWTS, ETSI, T1, TTA,TTC).All rights reserved.
3GPP
3G TS 23.078 V3.2.0 (1999-11)33G TS 23.078 version 3.2.0
Contents
Foreword ..............................................................................................................................................10
1 Scope ..........................................................................................................................................11
2 Normative references...................................................................................................................12
3 Definitions and abbreviations .........................................................................................................133.1 Definitions........................................................................................................................................................................... 133.2 Abbreviations..................................................................................................................................................................... 14
4 Architecture.................................................................................................................................154.1 Functional Entities used for CAMEL.............................................................................................................................. 154.2 Interfaces defined for CAMEL......................................................................................................................................... 164.2.1 HLR - VLR interface..................................................................................................................................................... 164.2.2 GMSC - HLR interface................................................................................................................................................. 164.2.3 GMSC - gsmSSF interface .......................................................................................................................................... 164.2.4 gsmSSF - gsmSCF interface ....................................................................................................................................... 164.2.5 MSC - gsmSSF interface............................................................................................................................................. 164.2.6 gsmSCF - HLR interface.............................................................................................................................................. 164.2.7 gsmSCF - gsmSRF interface....................................................................................................................................... 164.2.8 MSC - gsmSCF interface............................................................................................................................................. 16
5 Detection Points (DPs).................................................................................................................175.1 Definition and description................................................................................................................................................ 175.1.1 Arming/disarming mechanism................................................................................................................................... 175.1.2 Criteria ........................................................................................................................................................................... 185.1.2.1 Criteria for a terminating call................................................................................................................................ 185.1.2.2 Criteria for an originating call or a forwarded call............................................................................................. 185.1.3 Relationship.................................................................................................................................................................. 195.2 DP processing rules........................................................................................................................................................... 19
6 Description of CAMEL Subscriber Data........................................................................................216.1 Originating/Terminating CAMEL Subscription Information (O/T-CSI) .................................................................... 216.1.1 gsmSCF address .......................................................................................................................................................... 216.1.2 Service Key................................................................................................................................................................... 216.1.3 Default Call Handling.................................................................................................................................................. 216.1.4 TDP List........................................................................................................................................................................ 216.1.5 DP criteria...................................................................................................................................................................... 216.1.6 CAMEL Capability Handling..................................................................................................................................... 216.2 Other CAMEL data............................................................................................................................................................ 216.2.1 USSD CAMEL Subscription Information (U-CSI).................................................................................................. 216.2.1.1 Service Code .......................................................................................................................................................... 226.2.1.2 gsmSCF address.................................................................................................................................................... 226.2.2 Supplementary Service Invocation Notification CAMEL Subscription Information (SS-CSI)........................ 226.2.2.1 Content of the SS-CSI........................................................................................................................................... 226.2.2.1.1 Notification criteria.......................................................................................................................................... 226.2.2.1.2 gsmSCF address.............................................................................................................................................. 226.2.3 Location information/Subscriber state Interrogation............................................................................................. 226.2.4 Translation Information Flag (TIF-CSI).................................................................................................................... 22
7 Description of CAMEL BCSMs....................................................................................................237.1 General Handling................................................................................................................................................................ 237.2 Originating Basic Call State Model (O-BCSM).............................................................................................................. 237.2.1 Description of O-BCSM.............................................................................................................................................. 237.2.1.1 Description of the call model (PICs)................................................................................................................... 257.2.1.1.1 O_Null & Authorise_Origination_Attempt_Collect_Info ........................................................................ 257.2.1.1.2 Analyse, Routing & Alerting ........................................................................................................................ 25
3GPP
3G TS 23.078 V3.2.0 (1999-11)43G TS 23.078 version 3.2.0
7.2.1.1.3 O_Active .......................................................................................................................................................... 267.2.1.1.4 O_Exception..................................................................................................................................................... 267.3 Terminating Basic Call State Model (T-BCSM)............................................................................................................. 267.3.1 Description of T-BCSM .............................................................................................................................................. 267.3.1.1 Description of the call model (PICs)................................................................................................................... 287.3.1.1.1 T_Null ............................................................................................................................................................... 287.3.1.1.2 Terminating Call Handling ............................................................................................................................. 287.3.1.1.3 T_Active........................................................................................................................................................... 307.3.1.1.4 T_Exception ..................................................................................................................................................... 307.4 Rules for Implicit Disarming of Detection Points'................................................................................................... 317.5 BCSM Modelling of Call Scenarios................................................................................................................................. 317.5.1 Mobile Originated Call................................................................................................................................................ 327.5.2 Mobile Terminated Call............................................................................................................................................... 327.5.3 Call Forwarding at the GMSC .................................................................................................................................... 327.5.4 Call Forwarding at the MSC....................................................................................................................................... 33
8 Procedures for CAMEL ...............................................................................................................358.1 Overall SDL architecture ................................................................................................................................................... 358.2 Handling of mobile originated calls ................................................................................................................................. 388.2.1 Handling of mobile originated calls in the originating MSC................................................................................. 388.2.1.1 Actions of the MSC on receipt of Int_Error...................................................................................................... 388.2.1.2 Actions of the MSC on receipt of Int_Continue.............................................................................................. 388.2.1.3 Actions of the MSC on receipt of Int_Connect ............................................................................................... 388.2.1.4 Actions of the MSC on receipt of Int_Release_Call........................................................................................ 398.2.1.5 Action of the MSC in procedure CAMEL_OCH_ETC.................................................................................... 398.2.2 Handling of mobile originating calls in the originating VLR................................................................................. 648.3 Retrieval of routeing information..................................................................................................................................... 678.3.1 Retrieval of routeing information in the GMSC....................................................................................................... 678.3.1.1 Action of the GMSC on receipt of Int_Release_Call....................................................................................... 678.3.1.2 Action of the GMSC on receipt of Int_Error..................................................................................................... 678.3.1.3 Action of the GMSC on receipt of Int_Continue ............................................................................................. 678.3.1.4 Action of the GMSC on receipt of Int_Connect............................................................................................... 688.3.1.5 Action of the GMSC on receipt of Send_Routeing_Info Negative Response (at state
Wait_For_Routeing_Info_2)............................................................................................................................... 688.3.1.6 Action of the GMSC on receipt of Send_Routeing_Info ack with MSRN (at state
Wait_For_Routeing_Info_2)............................................................................................................................... 688.3.1.7 Action of the GMSC on receipt of Send_Routeing_Info ack with FTN (at state
Wait_For_Routeing_Info_2)............................................................................................................................... 688.3.1.8 Action of the GMSC on receipt of Send_Routeing_Info ack with O-CSI and FTN (at state
Wait_For_Routeing_Info_2)............................................................................................................................... 688.3.1.9 Action of the GMSC in procedure CAMEL_MT_ETC................................................................................... 698.3.1.10 Action of the GMSC in procedure CAMEL_MT_GMSC_Notify_CF .......................................................... 698.3.2 Retrieval of routeing information in the HLR .......................................................................................................... 988.3.3 Handling of provide roaming number request in the VLR................................................................................... 1038.4 Handling of mobile terminating calls ............................................................................................................................. 1058.4.1 Handling of mobile terminating calls in the terminating VMSC.......................................................................... 1058.4.2 Handling of mobile terminating calls in the VLR................................................................................................... 1058.5 Handling of forwarded calls ........................................................................................................................................... 1058.5.1 Procedure CAMEL_CF_MSC_INIT : handling of Int_Connect ........................................................................ 1058.5.2 Action of the GMSC in procedure CAMEL_CF_ETC......................................................................................... 1068.6 Handling of mobile calls in the gsmSSF ....................................................................................................................... 1208.6.1 Information flow for call duration control.............................................................................................................. 1208.6.2 Behaviour of the gsmSSF in the process gsmSSF................................................................................................ 1208.6.2.1 Actions of the gsmSSF on receipt of CAP_Request_Report_BCSM_Event (at the state
Waiting_For_Instructions)................................................................................................................................ 1218.6.2.2 Actions of the gsmSSF on receipt of CAP_Continue (at the state Waiting_For_Instructions)............ 1218.6.2.3 Actions of the gsmSSF on receipt of CAP_Release_Call (at the state Monitoring)................................ 121
3GPP
3G TS 23.078 V3.2.0 (1999-11)53G TS 23.078 version 3.2.0
8.6.2.4 Actions of the gsmSSF on receipt of Int_DP_T_Busy or Int_DP_T_No_Answer including theparameter CF (at the state Monitoring)............................................................................................................ 121
8.6.3 Procedure Handle_SCI.............................................................................................................................................. 1218.7 Assisting case.................................................................................................................................................................. 1558.8 Procedure CAMEL_Provide_Subscriber_Info............................................................................................................ 1658.8.1 MS reachable.............................................................................................................................................................. 1658.8.2 MS not reachable....................................................................................................................................................... 1658.8.2.1 Location Information requested........................................................................................................................ 1658.8.2.2 Subscriber State requested................................................................................................................................ 1658.8.3 Actions at state Wait_For_Information................................................................................................................. 1658.8.3.1 Provide_Subscriber_Info ack............................................................................................................................ 1658.8.3.2 Provide_Subscriber_Info Negative Response............................................................................................... 1658.9 Any Time Interrogation .................................................................................................................................................. 1678.10 Handling of USSD to/from gsmSCF.............................................................................................................................. 1698.10.1 MS Initiated USSD .................................................................................................................................................... 1698.10.2 gsmSCF Initiated USSD............................................................................................................................................ 1698.10.3 Content of the USSD General CAMEL Service Information (UG-CSI).............................................................. 1708.10.3.1 Service Code ........................................................................................................................................................ 1708.10.3.2 gsmSCF address.................................................................................................................................................. 1708.11 Handling of Supplementary Service Invocation Notification ................................................................................... 1708.12 CAMEL specific handling of location updating and data restoration..................................................................... 1708.13 Processing of Non-Call Related Events........................................................................................................................ 1708.14 Cross phase compatibility .............................................................................................................................................. 1718.15 Handling of North American Carrier Information........................................................................................................ 171
9 Description of information flows.................................................................................................. 1729.1 gsmSSF to gsmSCF information flows.......................................................................................................................... 1729.1.1 Activity Test ack....................................................................................................................................................... 1729.1.1.1 Description........................................................................................................................................................... 1729.1.1.2 Information Elements .......................................................................................................................................... 1729.1.2 Apply Charging Report ............................................................................................................................................ 1729.1.2.1 Description........................................................................................................................................................... 1729.1.2.2 Information Elements .......................................................................................................................................... 1729.1.3 Call Information Report............................................................................................................................................. 1739.1.3.1 Description........................................................................................................................................................... 1739.1.3.2 Information Elements .......................................................................................................................................... 1739.1.4 Event Report BCSM .................................................................................................................................................. 1739.1.4.1 Description........................................................................................................................................................... 1739.1.4.2 Information Elements .......................................................................................................................................... 1749.1.5 Initial DP...................................................................................................................................................................... 1749.1.5.1 Description........................................................................................................................................................... 1749.1.5.2 Information Elements .......................................................................................................................................... 1749.2 gsmSCF to gsmSSF information flows.......................................................................................................................... 1779.2.1 Activity Test .............................................................................................................................................................. 1779.2.1.1 Description........................................................................................................................................................... 1779.2.1.2 Information Elements .......................................................................................................................................... 1779.2.2 Apply Charging ......................................................................................................................................................... 1779.2.2.1 Description........................................................................................................................................................... 1779.2.2.2 Information Elements .......................................................................................................................................... 1789.2.3 Call Information Request.......................................................................................................................................... 1799.2.3.1 Description........................................................................................................................................................... 1799.2.3.2 Information Elements .......................................................................................................................................... 1799.2.4 Cancel.......................................................................................................................................................................... 1799.2.4.1 Description........................................................................................................................................................... 1799.2.4.2 Information Elements .......................................................................................................................................... 1809.2.5 Connect ....................................................................................................................................................................... 1809.2.5.1 Description........................................................................................................................................................... 1809.2.5.2 Information Elements .......................................................................................................................................... 180
3GPP
3G TS 23.078 V3.2.0 (1999-11)63G TS 23.078 version 3.2.0
9.2.6 Connect To Resource ............................................................................................................................................... 1819.2.6.1 Description........................................................................................................................................................... 1819.2.6.2 Information Elements .......................................................................................................................................... 1819.2.7 Continue...................................................................................................................................................................... 1819.2.7.1 Description........................................................................................................................................................... 1819.2.7.2 Information Elements .......................................................................................................................................... 1819.2.8 Disconnect Forward Connection ............................................................................................................................ 1829.2.8.1 Description........................................................................................................................................................... 1829.2.8.2 Information Elements .......................................................................................................................................... 1829.2.9 Establish Temporary Connection............................................................................................................................ 1829.2.9.1 Description........................................................................................................................................................... 1829.2.9.2 Information Elements .......................................................................................................................................... 1829.2.10 Furnish Charging Information ................................................................................................................................. 1839.2.10.1 Information Elements .......................................................................................................................................... 1839.2.11 Release Call................................................................................................................................................................. 1839.2.11.1 Description........................................................................................................................................................... 1839.2.11.2 Information Elements .......................................................................................................................................... 1839.2.12 Request Report BCSM Event .................................................................................................................................. 1849.2.12.1 Description........................................................................................................................................................... 1849.2.12.2 Information Elements .......................................................................................................................................... 1849.2.13 Reset Timer................................................................................................................................................................. 1849.2.13.1 Description........................................................................................................................................................... 1849.2.13.2 Information Elements .......................................................................................................................................... 1849.2.14 Send Charging Information...................................................................................................................................... 1859.2.14.1 Description........................................................................................................................................................... 1859.2.14.2 Information Elements .......................................................................................................................................... 1859.3 Optional (Service logic dependent) gsmSCF to gsmSRF information flows........................................................... 1869.3.1 Cancel.......................................................................................................................................................................... 1869.3.1.1 Description........................................................................................................................................................... 1869.3.1.2 Information Elements .......................................................................................................................................... 1869.3.2 Play Announcement.................................................................................................................................................. 1869.3.2.1 Description........................................................................................................................................................... 1869.3.2.2 Information Elements .......................................................................................................................................... 1869.3.3 Prompt And Collect User Information (received information)............................................................................ 1889.3.3.1 Description........................................................................................................................................................... 1889.3.3.2 Information Elements .......................................................................................................................................... 1889.3.4 Activity Test .............................................................................................................................................................. 1899.3.4.1 Description........................................................................................................................................................... 1899.3.4.2 Information Elements .......................................................................................................................................... 1899.4 gsmSRF to gsmSCF information flows ......................................................................................................................... 1909.4.1 Assist Request Instructions .................................................................................................................................... 1909.4.1.1 Description........................................................................................................................................................... 1909.4.1.2 Information Elements .......................................................................................................................................... 1909.4.2 Prompt And Collect User Information ack (received information)..................................................................... 1909.4.2.1 Description........................................................................................................................................................... 1909.4.2.2 Information Elements .......................................................................................................................................... 1909.4.3 Specialized Resource Report.................................................................................................................................... 1909.4.3.1 Description ........................................................................................................................................................... 1909.4.3.2 Information Elements .......................................................................................................................................... 1909.4.4 Activity Test ack....................................................................................................................................................... 1909.4.4.1 Description........................................................................................................................................................... 1909.4.4.2 Information Elements .......................................................................................................................................... 1919.5 gsmSCF to Assisting SSF information flows............................................................................................................... 1919.5.1 Cancel.......................................................................................................................................................................... 1919.5.1.1 Description........................................................................................................................................................... 1919.5.2 Connect To Resource ............................................................................................................................................... 1919.5.2.1 Description........................................................................................................................................................... 1919.5.3 Play Announcement.................................................................................................................................................. 191
3GPP
3G TS 23.078 V3.2.0 (1999-11)73G TS 23.078 version 3.2.0
9.5.3.1 Description........................................................................................................................................................... 1919.5.4 Prompt And Collect User Information.................................................................................................................... 1919.5.4.1 Description........................................................................................................................................................... 1919.5.5 Reset Timer................................................................................................................................................................. 1919.5.5.1 Description........................................................................................................................................................... 1919.5.6 Activity Test .............................................................................................................................................................. 1919.5.6.1 Description........................................................................................................................................................... 1919.5.6.2 Information Elements .......................................................................................................................................... 1919.6 Assisting SSF to gsmSCF information flows............................................................................................................... 1929.6.1 Assist Request Instructions .................................................................................................................................... 1929.6.1.1 Description........................................................................................................................................................... 1929.6.2 Prompt And Collect User Information ack (received information)..................................................................... 1929.6.2.1 Description........................................................................................................................................................... 1929.6.3 Specialized Resource Report.................................................................................................................................... 1929.6.3.1 Description........................................................................................................................................................... 1929.6.4 Activity Test ack....................................................................................................................................................... 1929.6.4.1 Description........................................................................................................................................................... 1929.6.4.2 Information Elements .......................................................................................................................................... 1929.7 gsmSCF to HLR information flows ................................................................................................................................ 1929.7.1 Any Time Interrogation Request ............................................................................................................................ 1929.7.1.1 Description........................................................................................................................................................... 1929.7.1.2 Information Elements .......................................................................................................................................... 1929.7.2 Unstructured SS Request......................................................................................................................................... 1939.7.2.1 Description........................................................................................................................................................... 1939.7.2.2 Information Elements .......................................................................................................................................... 1939.7.3 Unstructured SS Notify ............................................................................................................................................ 1939.7.3.1 Description........................................................................................................................................................... 1939.7.3.2 Information Elements .......................................................................................................................................... 1939.7.4 Process Unstructured SS Data ack......................................................................................................................... 1949.7.4.1 Description........................................................................................................................................................... 1949.7.4.2 Information Elements .......................................................................................................................................... 1949.7.5 Process Unstructured SS Request ack................................................................................................................... 1949.7.5.1 Description........................................................................................................................................................... 1949.7.5.2 Information Elements .......................................................................................................................................... 1949.8 HLR to gsmSCF information flows ................................................................................................................................ 1959.8.1 Any Time Interrogation ack..................................................................................................................................... 1959.8.1.1 Description........................................................................................................................................................... 1959.8.1.2 Information Elements .......................................................................................................................................... 1959.8.2 Unstructured SS Request ack.................................................................................................................................. 1959.8.2.1 Description........................................................................................................................................................... 1959.8.2.2 Information Elements .......................................................................................................................................... 1959.8.3 Unstructured SS Notify ack..................................................................................................................................... 1969.8.3.1 Description........................................................................................................................................................... 1969.8.4 Process Unstructured SS Data ................................................................................................................................ 1969.8.4.1 Description........................................................................................................................................................... 1969.8.4.2 Information Elements .......................................................................................................................................... 1969.8.5 Process Unstructured SS Request.......................................................................................................................... 1969.8.5.1 Description........................................................................................................................................................... 1969.8.5.2 Information Elements .......................................................................................................................................... 1969.8.6 Begin Subscriber Activity........................................................................................................................................ 1979.8.6.1 Description........................................................................................................................................................... 1979.8.6.2 Information Elements .......................................................................................................................................... 1979.9 HLR to VLR information flows ....................................................................................................................................... 1979.9.1 Delete Subscriber Data ............................................................................................................................................. 1979.9.1.1 Description........................................................................................................................................................... 1979.9.1.2 Information Elements .......................................................................................................................................... 1979.9.2 Insert Subscriber Data .............................................................................................................................................. 1979.9.2.1 Description........................................................................................................................................................... 197
3GPP
3G TS 23.078 V3.2.0 (1999-11)83G TS 23.078 version 3.2.0
9.9.2.2 Information Elements .......................................................................................................................................... 1979.9.3 Provide Subscriber Info ............................................................................................................................................ 1989.9.3.1 Description........................................................................................................................................................... 1989.9.3.2 Information Elements .......................................................................................................................................... 1989.9.4 Provide Roaming Number......................................................................................................................................... 1999.9.4.1 Description........................................................................................................................................................... 1999.9.4.2 Information Elements .......................................................................................................................................... 1999.10 VLR to HLR information flows ....................................................................................................................................... 1999.10.1 Insert Subscriber Data ack....................................................................................................................................... 1999.10.1.1 Description........................................................................................................................................................... 1999.10.1.2 Information Elements .......................................................................................................................................... 1999.10.2 Provide Subscriber Info ack..................................................................................................................................... 1999.10.2.1 Description........................................................................................................................................................... 1999.10.2.2 Information Elements .......................................................................................................................................... 2009.10.3 Update Location ........................................................................................................................................................ 2009.10.3.1 Description........................................................................................................................................................... 2009.10.3.2 Information Elements .......................................................................................................................................... 2009.10.4 Restore Data............................................................................................................................................................... 2009.10.4.1 Description........................................................................................................................................................... 2009.10.4.2 Information Elements .......................................................................................................................................... 2009.11 HLR to GMSC information flows ................................................................................................................................... 2019.11.1 Send Routeing Info ack............................................................................................................................................ 2019.11.1.1 Description........................................................................................................................................................... 2019.11.1.2 Information Elements .......................................................................................................................................... 2019.12 GMSC to HLR information flows ................................................................................................................................... 2029.12.1 Send Routeing Info ................................................................................................................................................... 2029.12.1.1 Description........................................................................................................................................................... 2029.12.1.2 Information Elements .......................................................................................................................................... 2029.13 MSC to gsmSCF information flows ............................................................................................................................... 2039.13.1 SS Invocation Notification....................................................................................................................................... 2039.13.1.1 Description........................................................................................................................................................... 2039.13.1.2 Information Elements .......................................................................................................................................... 2049.14 VMSC to GMSC information flows ............................................................................................................................... 2049.14.1 Resume Call Handling............................................................................................................................................... 2049.14.1.1 Description........................................................................................................................................................... 2049.14.1.2 Information Elements .......................................................................................................................................... 2049.15 MSC to VLR information flows ...................................................................................................................................... 2059.15.1 Send Info For Outgoing Call.................................................................................................................................... 2059.15.1.1 Description........................................................................................................................................................... 2059.15.1.2 Information Elements .......................................................................................................................................... 2059.15.2 Send Info For Reconnected Call.............................................................................................................................. 2059.15.2.1 Description........................................................................................................................................................... 2059.15.2.2 Information Elements .......................................................................................................................................... 2059.16 VLR to MSC information flows ...................................................................................................................................... 2069.16.1 Complete Call.............................................................................................................................................................. 2069.16.1.1 Description........................................................................................................................................................... 2069.16.1.2 Information Elements .......................................................................................................................................... 2069.16.2 Process Call Waiting ................................................................................................................................................. 2069.16.2.1 Description........................................................................................................................................................... 2069.16.2.2 Information Elements .......................................................................................................................................... 2069.16.3 Send Info For Incoming Call ack............................................................................................................................. 2069.16.3.1 Description........................................................................................................................................................... 2069.16.3.2 Information Elements .......................................................................................................................................... 2079.16.4 Send Info For Incoming Call negative response................................................................................................... 2079.16.4.1 Description........................................................................................................................................................... 2079.16.4.2 Information Elements .......................................................................................................................................... 207
3GPP
3G TS 23.078 V3.2.0 (1999-11)93G TS 23.078 version 3.2.0
10 Interaction with supplementary services....................................................................................... 20810.1 Line identification ............................................................................................................................................................ 20810.2 Call forwarding services.................................................................................................................................................. 20810.2.1 Registration of Call Forwarding............................................................................................................................... 20810.2.2 Invocation of Call Forwarding................................................................................................................................. 20810.3 Call Barring services ........................................................................................................................................................ 208
Annex A (informative): Document change history ｴﾗｰ! ﾌﾞｯｸﾏｰｸが定義されていません。
History.................................................................................ｴﾗｰ ! ﾌﾞｯｸﾏｰｸが定義されていません。
3GPP
3G TS 23.078 V3.2.0 (1999-11)103G TS 23.078 version 3.2.0
ForewordThis Technical Specification has been produced by the 3GPP.
The contents of the present document are subject to continuing work within the TSG and may change following formalTSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifyingchange of release date and an increase in version number as follows:
Version 3.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 Indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates,etc.
z the third digit is incremented when editorial only changes have been incorporated in the specification;
3GPP
3G TS 23.078 V3.2.0 (1999-11)113G TS 23.078 version 3.2.0
1 ScopeThis Technical Specification (TS) specifies the stage 2 description for the second phase (see GSM 02.78 [2]) of theCustomized Applications for Mobile network Enhanced Logic (CAMEL) feature which provides the mechanisms tosupport services of operators which are not covered by standardized GSM services even when roaming outside theHPLMN.
The CAMEL feature is a network feature and not a supplementary service. It is a tool to help the network operator toprovide the subscribers with the operator specific services even when roaming outside the HPLMN.
In this specification, the GSM Service Control Function (gsmSCF) is treated as being part of the HPLMN. The regulatoryenvironment in some countries may require the possibility that the gsmSCF and the HPLMN are controlled by differentoperators, and the gsmSCF and the HPLMN are therefore distinct entities.
In the second phase the CAMEL feature supports:- mobile originated and forwarded calls;
- mobile terminating calls;
- any time interrogation;
- suppression of announcements;
- announcements, in band user interaction;
- charging features;
- supplementary service invocation notifications;
- USSD interaction with the gsmSCF.
- North American carrier selection.
Note that CAMEL is not applicable to Emergency Setup (TS 12), i.e., in case an Emergency call has been requested thegsmSSF shall not be invoked.
The mechanism described in this standard addresses especially the need for information exchange between the VPLMNor IPLMN and the HPLMN for support of operator specific services. Any user procedures for the control of operatorspecific services are outside the scope of this standard. Subscribers who have subscribed to operator specific servicesand therefore need the functional support of the CAMEL feature shall be marked in the HPLMN and VPLMN. In case asubscriber is marked to need CAMEL support, the appropriate procedures which provide the necessary information tothe VPLMN or the HPLMN are invoked. It is possible for the HPLMN to instruct the VPLMN or IPLMN to interact with agsmSCF which is controlled by the HPLMN.
The specification of operator specific services is outside the scope of this standard.
3GPP
3G TS 23.078 V3.2.0 (1999-11)123G TS 23.078 version 3.2.0
2 Normative referencesThe following documents contain provisions which, through reference in this text, constitute provisions of the presentdocument.
- References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies.
- A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.
[1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
[2] GSM 02.78: "Digital cellular telecommunications system (Phase 2+); Customized Applications forMobile network Enhanced Logic (CAMEL) - Phase 2. Service description. Stage 1
[3] GSM 03.18: "Digital cellular telecommunications system (Phase 2+); Basic call handling ; Technicalrealisation".
[4] GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP)specification".
[5] GSM 09.78: "Digital cellular telecommunications system (Phase 2+); CAMEL Application Part(CAP) specification - Phase 2".
[6] ITU-T Q.1214, May 1995: "Distributed Functional Plane for Intelligent Network CS-1"
[7] EN 301 070-1 v1.1.1. "Integrated Services Digital Network (ISDN) ; Signalling System No.7 ; ISDNUser Part (ISUP) version 3 interactions with the Intelligent Network Application Part (INAP) ; Part1 : Protocol specification [ITU-T Recommendation Q.1600 (1997), modified]".
[8] GSM 03.90 : "Digital cellular telecommunication system (Phase 2+); Unstructured SupplementaryService Data (USSD) - Stage 2".
[9] GSM 03.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG)supplementary services - Stage 2".
[10] ANSI T1.113-1995 Signalling System No. 7(SS7) – Integrated Services Digital Network (ISDN) UserPart.
[11] GSM 03.84: “Digital cellular telecommunications system; Multi Party (MPTY) supplementaryservices - Stage 2”.
[12] GSM 03.91: “Digital cellular telecommu nications system; Explicit Call Transfer (ECT) supplementaryservice – Stage 2”
3GPP
3G TS 23.078 V3.2.0 (1999-11)133G TS 23.078 version 3.2.0
3 Definitions and abbreviations
3.1 DefinitionsFor the purposes of this TS, the following definitions apply:
Basic Call State Model (BCSM): The BCSM provides a high-level model of GMSC- or MSC/VLR-activities required toestablish and maintain communication paths for users. As such, it identifies a set of basic call activities in a GMSC orMSC/VLR and shows how these activities are joined together to process a basic call.
Call Control Function (CCF): The CCF is the Call Control Function in the network that that provides call/serviceprocessing and control (see ITU-T Q.1214 [6]).
Detection Points (DP): The points in processing at which notifications (to the service logic) can occur and transfer ofcontrol (to the gsmSCF) is possible are called Detection Points (DPs).
GSM Service Control Function (gsmSCF): A functional entity that contains the CAMEL service logic to implement OSS.It interfaces with the gsmSSF, the gsmSRF and the HLR.
GSM Service Switching Function (gsmSSF): A functional entity that interfaces the MSC/GMSC to the gsmSCF. Theconcept of the gsmSSF is derived from the IN SSF, but uses different triggering mechanisms because of the nature of themobile network.
GSM Specialised Resource Function (gsmSRF): A functional entity which provides various specialized resources. Itinterfaces with the gsmSCF and with the MSC. This entity is defined in ITU-T Q.1214 ([6]) with variations defined in thespecification.
NA (North American): A prefix attached to certain information items used by North American PLMNs in connectionwith routing a call to a preferred or dialled long distance carrier.
Location Information: Indicates the location of the served subscriber. The provision of location information isindependent of the MS status. As part of the location information, an indication of the age of this information may bedelivered.
Originating Basic Call State Model (O-BCSM): The originating half of the BCSM. The O-BCSM corresponds to thatportion of the BCSM associated with the originating party.
Originating CAMEL Subscription Information (O-CSI): The O-CSI identifies the subscriber as having originatingCAMEL services.
Point In Call (PIC): PICs identify MSC/VLR (GMSC) activities associated with one or more basic call/connection statesof interest to OSS service logic instances.
Service Key: The Service Key can identify to the gsmSCF the service logic that it should apply. The Service Key isadministered by the HPLMN, and is passed transparently by the VPLMN/IPLMN to the gsmSCF. The Service Key is apart of the T/O-CSI.
Subscriber State: See GSM 02.78 [2].
Supplementary Service Notification CAMEL Subscription Information (SS-CSI): The SS-CSI identifies the subscriberas having supplementary service invocation notification CAMEL services.
Terminating Basic Call State Model (T-BCSM): The terminating half of the BCSM. The T-BCSM corresponds to thatportion of the BCSM associated with the terminating party.
Terminating CAMEL Subscription Information (T-CSI): The T-CSI identifies the subscriber as having terminatingCAMEL services.
3GPP
3G TS 23.078 V3.2.0 (1999-11)143G TS 23.078 version 3.2.0
Translation Information Flag (TIF-CSI) : The TIF-CSI is a flag in the CAMEL subscriber data which indicates that whenthe subscriber registers a forwarded-to number, that the HLR shall not attempt to perform any translation, number formatchecks, prohibited FTN checks, call barring checks.
USSD CAMEL Subscription Information (U-CSI) : The U-CSI identifies a set of subscriber specific mappings from aUSSD service code to a gsmSCF address.
USSD General CAMEL Service Information (UG-CSI) : The UG-CSI globally identifies a set of mappings from a USSDservice code to a gsmSCF address. The global mapping applies to all HPLMN subscribers. If, for a particular service code,both U-CSI and UG-CSI are applicable then the U-CSI shall take precedence.
3.2 AbbreviationsAbbreviations used in this specification are listed in GSM 01.04 [1].
For the purposes of this TS, the following abbreviations apply:
BCSM Basic Call State ModelCAMEL Customized Applications for Mobile network Enhanced LogicDP Detection PointEDP Event Detection PointGMSC Gateway MSCgsmSCF GSM Service Control FunctiongsmSRF GSM Specialised Resource FunctiongsmSSF GSM Service Switching FunctionHLR Home Location RegisterHPLMN Home PLMNIE Information ElementIF Information FlowIP Intelligent PeripheralIPLMN Interrogating PLMNMSC Mobile service Switching CentreNA North AmericanO-BCSM Originating Basic Call State ModelO-CSI Originating CAMEL Subscription InformationODB Operator Determined BarringOSS Operator Specific ServicePIC Point In CallPLMN Public Land Mobile NetworkSLPI Service Logic Program InstanceSMF Service Management FunctionSS-CSI Supplementary Service Notification CAMEL Subscription InformationT-BCSM Terminating Basic Call State ModelT-CSI Terminating CAMEL Subscription InformationTDP Trigger Detection PointTIF-CSI Translation Information FlagU-CSI USSD CAMEL Subscription InformationUG-CSI USSD General CAMEL Service InformationVLR Visitor Location RegisterVPLMN Visited PLMN
3GPP
3G TS 23.078 V3.2.0 (1999-11)153G TS 23.078 version 3.2.0
4 Architecture
4.1 Functional Entities used for CAMELThis subclause describes the functional architecture needed to support CAMEL. Also the additions needed to the basicGSM functionality are described. Figure 1 shows the functional entities involved in calls requiring CAMEL support. Thearchitecture is applicable to the second phase of CAMEL.
HLR
GMSC
gsmSCF
MSC
Forwarded leg
MSIncoming line
Visiting NetworkInterrogating Network
Home Network
gsmSSFVLR
Roaming leg
CAPCAP
MAP
MAP MAP
gsmSSF
gsmSRFHome/Interrogating/Visiting Network
CAP
MO call - Outgoing leg(or Forwarding leg)
MAP
Figure 1: Functional architecture for support of CAMEL
HLR: The HLR stores for subscribers requiring CAMEL support the information relevant to the current subscriptionregarding O-CSI, T-CSI, TIF-CSI, U-CSI and SS-CSI. The UG-CSI is stored as global data applicable to all CAMELsubscribers. The O-CSI is sent to the VLR in case of Location Update or if the O-CSI is updated. The SS-CSI is sent tothe VLR in case of Location Update or if the SS-CSI is updated. The O/T-CSI is sent to the GMSC when the HLRresponds to a request for routeing information. The TIF-CSI, U-CSI and the UG-CSI are stored in the HLR only. The HLRmay provide an interface towards the gsmSCF for the Any Time Interrogation procedure.
GMSC: When processing the calls for subscribers requiring CAMEL support, the GMSC receives a O/T-CSI from theHLR, indicating the GMSC to request instructions from the gsmSSF. The GMSC monitors on request the call states(events) and informs the gsmSSF of these states during processing, enabling the gsmSSF to control the execution of thecall in the GMSC.
MSC: When processing the calls for subscribers requiring CAMEL support, the MSC receives a O-CSI from the VLRindicating the MSC to request instructions from the gsmSSF. The MSC monitors on request the call states (events) andinforms the gsmSSF of these states during processing, enabling the gsmSSF to control the execution of the call in theMSC. When processing an invocation of any of the supplementary services ECT, CD and MPTY, the MSC receives aSS-CSI from the VLR, indicating that a notification of the invocation of the supplementary service shall be sent to thegsmSCF.
VLR: The VLR stores the O-CSI and SS-CSI as a part of the subscriber data for subscribers roaming in the VLR area.
gsmSSF: see subclause 3.1.
3GPP
3G TS 23.078 V3.2.0 (1999-11)163G TS 23.078 version 3.2.0
gsmSCF: see subclause 3.1.
gsmSRF: see subclause 3.1.
4.2 Interfaces defined for CAMELThis subclause describes the different interfaces applicable to CAMEL. It specifies on a high level the functions specificto CAMEL.
4.2.1 HLR - VLR interface
This interface is used to send the CAMEL related subscriber data to the visited PLMN and for provision of MSRN. Theinterface is also used to retrieve subscriber status and location information of the mobile subscriber or to indicatesuppression of announcement for a CAMEL service.
4.2.2 GMSC - HLR interface
This interface is used at terminating calls to exchange routeing information, subscriber status, location information,subscription information and suppression of announcements. The O/T-CSI that is passed to the IPLMN is sent over thisinterface.
4.2.3 GMSC - gsmSSF interface
This is an internal interface. The interface is described in the specification to make it easier to understand the handling ofDPs (arming/disarming of DPs, DP processing etc.).
4.2.4 gsmSSF - gsmSCF interface
This interface is used by the gsmSCF to control a call in a certain gsmSSF and to request the gsmSSF to establish aconnection with a gsmSRF. Relationships on this interface are opened as a result of the gsmSSF sending a request forinstructions to the gsmSCF.
4.2.5 MSC - gsmSSF interface
This is an internal interface. The interface is described in the specification to make it easier to understand the handling ofDPs (arming/disarming of DPs, DP processing etc.).
4.2.6 gsmSCF - HLR interface
This interface is used by the gsmSCF to request information from the HLR. As a network operator option the HLR mayrefuse to provide the information requested by the gsmSCF.
This interface is also used for USSD operations, both for gsmSCF-initiated dialogues and MS-initiated dialogues (relayedvia HLR). It is a network operator option whether to support or not USSD operations on this interface.
4.2.7 gsmSCF - gsmSRF interface
This interface is used by the gsmSCF to instruct the gsmSRF to play tones/announcements to the users.
4.2.8 MSC - gsmSCF interface
This interface is used by the MSC to send supplementary service invocation notifications to the gsmSCF.
3GPP
3G TS 23.078 V3.2.0 (1999-11)173G TS 23.078 version 3.2.0
5 Detection Points (DPs)
5.1 Definition and descriptionCertain basic call events may be visible to the GSM Service Control Function (gsmSCF). The DPs are the points in call atwhich these events are detected. The DPs for Mobile Originated Calls and Mobile Terminated Calls are described insubclauses 7.2 and 7.3.
A DP can be armed in order to notify the gsmSCF that the DP was encountered, and potentially to allow the gsmSCF toinfluence subsequent handling of the call. If the DP is not armed, the processing entity continues the processing withoutgsmSCF involvement.
Three different types of DPs are identified:
- Trigger Detection Point - Request (TDP-R)
This detection point is statically armed and initiates a CAMEL control relationship when encountered. Processingis suspended when the DP is encountered.
- Event Detection Point - Request (EDP-R)
This detection point is dynamically armed within the context of a CAMEL control relationship. Processing issuspended when encountering the DP and the gsmSSF waits for instructions from the gsmSCF.
- Event Detection Point - Notification (EDP-N)
This detection point is dynamically armed within the context of a CAMEL control relationship. Processing is notsuspended when encountering the DP.
The DPs are characterized in the following subclauses.
5.1.1 Arming/disarming mechanism
The mechanism by which the DP is armed. A DP may be statically armed or dynamically armed.
The following arming rules apply:
- DP for mobile terminating call handling is statically armed in GMSC as result of T-CSI delivery from HLR. DP forforwarding leg handling is statically armed in GMSC as result of O-CSI delivery from HLR. DP for mobileoriginating call or forwarded leg handling is statically armed in VMSC as result of O-CSI delivery from VLR.
- A DP is dynamically armed by the gsmSCF within the context of a CAMEL control relationship (between thegsmSSF and the gsmSCF).
The following disarming rules apply:
- A statically armed DP is disarmed when a O/T-CSI is withdrawn in the HLR. Only TDP-Rs can be disarmed usingthis mechanism.
- If an armed EDP is met, then it is disarmed.
- If an EDP is met that causes the release of the related leg, then all EDPs related to that leg are disarmed.
- If a call is released, then all EDPs related to that call are disarmed.
- If an EDP is met, then other EDPS are disarmed, in accordance with the implicit disarming rule table (see section7.4).
- If an EDP is armed, it can be explicitly disarmed by the gsmSCF by means of the RequestReportBCSMEventinformation flow.
3GPP
3G TS 23.078 V3.2.0 (1999-11)183G TS 23.078 version 3.2.0
5.1.2 Criteria
Criteria are the conditions that must be met in order for the gsmSSF to request instructions from the gsmSCF.
5.1.2.1 Criteria for a terminating call
The criteria for a terminating call are checked in the HLR. The HLR may store a list of up to 5 basic service codes, each ofwhich may represent an individual basic service or a basic service group. This list is a triggering list. The basic servicecriterion is met if the basic service for the call matches a stored individual basic service code or is a member of the groupdefined by a stored basic service group code. For the purpose of this paragraph a general bearer service is a member ofthe corresponding bearer service group.
The HLR shall include the CAMEL subscription information in the subscriber data sent to the GMSC only if thetriggering criteria are met.
5.1.2.2 Criteria for an originating call or a forwarded call
The criteria for an originating or forwarded call are checked in the originating or forwarding MSC.
NOTE: In the case of a forwarded call, the HLR may decide not to include the CAMEL subscription information inthe subscriber data sent to the GMSC if the triggering criteria are not met.
The following criteria are applicable for DP2 :
- Destination number triggering criterion: The HLR may store a list of up to 10 destination numbers and/or up to 3number lengths. The nature of address shall be one of the following:
- unknown, or
- international.
There is no restriction on numbering plan indicator. This criterion may be defined to be either "enabling" or"inhibiting".
- Basic service triggering criterion: The HLR may store a list of up to 5 basic service codes, each of which mayrepresent an individual basic service or a basic service group. This list is a triggering list.
- Forwarding triggering criterion: The HLR may store an indicator that triggering shall occur only for a call whichhas been subject to GSM or CAMEL call forwarding. This criterion may be defined to be either "enabling" or"inhibiting".
For MO calls, triggering at DP2 shall be strictly based on the number received over the access network.No service selection information, such as ∗ and # digits, or carrier selection information, dialled by the subscriber, shallbe removed from the number before conditional triggering check takes place.
For MF calls at the VMSC, triggering at DP2 shall be strictly based on the number received over the access network (theDeflected-to-Number in case of Call Deflection) or the Forwarded-to-Number retained in the VLR.No service selection information or carrier selection information shall be removed from the number before conditionaltriggering check takes place.
For MF calls at the GMSC, triggering at DP2 shall be strictly based on the Forwarded-to-Number received from HLR oron the Destination Routing Address received in the Connect operation from SCF during a Terminating CAMEL Service.
No service selection information or carrier selection information shall be removed from the number before conditionaltriggering check takes place.
One or more DP criteria may be applicable. All applicable triggering criteria must be satisfied before the dialogue isestablished with the gsmSCF.
If the destination number triggering criterion is enabling, then the gsmSSF may establish a dialogue with the gsmSCF if:
3GPP
3G TS 23.078 V3.2.0 (1999-11)193G TS 23.078 version 3.2.0
- the destination number matches one of the destination number strings defined in the list, or
- the length of the destination number matches one of the destination number lengths defined in the list.
In this test the destination number matches one of the destination number strings in the list if:
- the nature of address of destination number is the same as the nature of address of the destination numberstring
- the destination number is at least as long as the destination number string in the list, and
- all the digits in the destination number string in the list match the leading digits of the destination number.
If the destination number triggering criterion is inhibiting, then the gsmSSF may establish a dialogue with the gsmSCF if:
- the destination number does not match any of the destination number strings defined in the list, and
- the length of the destination number does not match any of the destination number lengths defined in the list.
In this test the destination number matches one of the destination number strings in the list if:
- the nature of address of destination number is the same as the nature of address of the destination numberstring
- the destination number is at least as long as the destination number string in the list, and
- all the digits in the destination number string in the list match the leading digits of the destination number.
The basic service triggering criterion is met if the basic service for the call matches a stored individual basic service codeor is a member of the group defined by a stored basic service group code. For the purpose of this paragraph a generalbearer service is a member of the corresponding bearer service group.
If the forwarding triggering criterion is enabling, then the gsmSSF may establish a dialogue with the gsmSCF only if thecall has been subject to CAMEL or GSM call forwarding. If the forwarding triggering criterion is inhibiting, then thegsmSSF may establish a dialogue with the gsmSCF only if the call has not been subject to CAMEL or GSM callforwarding.
5.1.3 Relationship
Given that an armed DP was encountered, the gsmSSF provides an information flow via a relationship.
A relationship between the gsmSSF and the gsmSCF for the purpose of operator specific service processing isconsidered to be a CAMEL relationship. There are two types of CAMEL relationships:
- A CAMEL control relationship if the gsmSCF is able to influence the call processing via the relationship.
- A CAMEL monitor relationship if the gsmSCF is not able to influence the call processing via the relationship.
5.2 DP processing rulesThe gsmSSF shall apply the following set of rules during DP processing to ensure a single point of control:
- EDPs are disarmed by the gsmSSF as they are encountered and reported to the gsmSCF, when the occurrence ofanother EDP causes the implicit disarming of the EDP or when the leg clears.
- A control relationship persists as long as there is 1 or more EDP-R armed for this portion of the call or if thegsmSSF is in any state except Monitoring or Idle.
- A control relationship changes to a monitor relationship if the control relationship does not persist and :
- 1 or more EDP-N armed, or
- 1 or more Call information Report outstanding, or
3GPP
3G TS 23.078 V3.2.0 (1999-11)203G TS 23.078 version 3.2.0
- an Apply Charging Report outstanding.
- A control relationship terminates if it does not persist and does not change to a monitor relationship. A monitorrelationship terminates if there are neither EDP-Ns armed nor reports outstanding or if the call clears.
3GPP
3G TS 23.078 V3.2.0 (1999-11)213G TS 23.078 version 3.2.0
6 Description of CAMEL Subscriber Data
6.1 Originating/Terminating CAMEL Subscription Information(O/T-CSI)
This subclause defines the contents of the Originating/Terminating CAMEL Subscription Information.
6.1.1 gsmSCF address
Address to be used to access the gsmSCF for a particular subscriber. The address shall be an E.164 number to be usedfor routeing.
6.1.2 Service Key
The Service Key identifies to the gsmSCF the service logic that should apply
6.1.3 Default Call Handling
The Default Call Handling indicates whether the call shall be released or continued as requested in case of error in thegsmSSF to gsmSCF dialogue.
6.1.4 TDP List
The TDP List indicates on which detection point triggering shall take place. For O-CSI only DP2 is used. For T-CSI onlyDP12 is used.
6.1.5 DP criteria
The DP criteria indicate whether the gsmSSF shall request the gsmSCF for instructions.
6.1.6 CAMEL Capability Handling
CAMEL Capability Handling indicates the phase of CAMEL which is asked by the gsmSCF for the service. The HLRshall not include in a CSI which it sends to a VLR or GMSC any data for a CAMEL phase later than that which theCAMEL capability handling indicates. E.g. if the CAMEL Capability Handling indicates CAMEL phase 1 then the HLRshall not send triggering criteria to the VLR. Different CSIs may contain different values of CAMEL Capability Handling.
NOTE: If CAMEL is not supported or if a lower phase of CAMEL is supported in the VLR, the HLR can decide ona subscriber basis to apply ODB, perform normal call handling or perform operator specific handling(eventually support of a lower version of CSI).
6.2 Other CAMEL data
6.2.1 USSD CAMEL Subscription Information (U-CSI)
The subscription information specified in this subclause is for information only.
This subclause defines the contents of the USSD CAMEL Subscription Information (U-CSI). The U-CSI consists of a listof pairs of the following two parameters.
3GPP
3G TS 23.078 V3.2.0 (1999-11)223G TS 23.078 version 3.2.0
6.2.1.1 Service Code
Service code for a specific application in a gsmSCF which interacts with the user by USSD.
6.2.1.2 gsmSCF address
Address to be used to access the gsmSCF for a particular subscriber and a particular service code. The address shall bean E.164 number to be used for routeing.
6.2.2 Supplementary Service Invocation Notification CAMEL SubscriptionInformation (SS-CSI)
6.2.2.1 Content of the SS-CSI
This subclause defines the contents of the Supplementary Service Invocation Notification CAMEL SubscriptionInformation (SS-CSI).
6.2.2.1.1 Notification criteria
This data indicates for which supplementary services notifications shall be sent. The supplementary services which maybe indicated are ECT, CD and MPTY.
6.2.2.1.2 gsmSCF address
Address to be used to access the gsmSCF for a particular subscriber. The address shall be an E.164 number to be usedfor routeing.
6.2.3 Location information/Subscriber state Interrogation
This data indicates whether additional subscriber information shall be sent to the GMSC as part of the terminating callhandling.
- an indication that the HLR shall send the location information of the called subscriber.
- an indication that the HLR shall send the subscriber state of the called subscriber.
6.2.4 Translation Information Flag (TIF-CSI)
A flag (TIF-CSI) in the CAMEL Subscriber data in the HLR indicates, when the subscriber registers a forwarded-tonumber, that the HLR shall not attempt to perform any translation, number format checks, prohibited FTN checks, callbarring checks (cf. 10.2).
If the flag is absent, this indicates that a translation is needed in the HLR and the usual procedure applies as defined inthe current version of TS GSM 03.82. In particular, the interaction with barring services shall be performed by the HLR atthe registration of the FTN.
3GPP
3G TS 23.078 V3.2.0 (1999-11)233G TS 23.078 version 3.2.0
7 Description of CAMEL BCSMs
7.1 General HandlingThe BCSM is used to describe the actions in an MSC/GMSC during originating, forwarded or terminating calls.
The BCSM identifies the points in basic call processing when Operator Specific Service (OSS) logic instances (accessedthrough the gsmSCF) are permitted to interact with basic call control capabilities.
Figure 2 shows the components that have been identified to describe a BCSM.
Point In Call (PIC)
DP
Transition
Figure 2: BCSM Components
7.2 Originating Basic Call State Model (O-BCSM)
7.2.1 Description of O-BCSM
The O-BCSM is used to describe the actions in an MSC during originating (MSC) or forwarded (MSC or GMSC) calls.
When encountering a DP the O-BCSM processing is suspended at the DP and the MSC/GMSC indicates this to thegsmSSF which determines what action, if any, shall be taken in case the DP is armed.
3GPP
3G TS 23.078 V3.2.0 (1999-11)243G TS 23.078 version 3.2.0
O_Null & Authorise_Origination_Attempt_Collect_Info
DP2
O_Exception
DP9
DP7
Collected_Info
O_Answer
Basic Call transition
Transition beyond Basic Call
DP4
DP5
DP6
O_Disconnect
O_Active
Route_Select_Failure
O_Busy
O_No_Answer
DP10
O_Abandon
& Alerting
Analyse, Routing
A
A
Figure 3: Originating BCSM for CAMEL
The following table defines the different DPs which apply to mobile originating and forwarded calls.
Table 1: Description of O-BCSM DPs in the MSC
CAMEL Detection Point: DP Type Description:
DP2 Collected_Info TDP-R Indication that the O-CSI is analysed.
DP 4 Route_Select_Failure EDP-N, EDP-R Indication that the call establishment failed
DP 5 O_Busy EDP-N, EDP-R Indication that:
- a busy indication is received from the terminatingparty,
- a not reachable event is determined upon a cause IEin the ISUP release message.
DP6 O_No_Answer EDP-N, EDP-R Indication that an application timer associated with theO_No_Answer DP expires
DP7 O_Answer EDP-N, EDP-R Indication that the call is accepted and answered by theterminating party.
DP9 O_Disconnect EDP-N, EDP-R A disconnect indication is received from the originatingparty or from the terminating party.
DP 10 O_Abandon EDP-N Indication that a disconnect indication is received fromthe originating party during the call establishmentprocedure
NOTE: the DPs 2, 4, 5, 6, 7, 9, 10 are defined in ITU-T Q.1214 ([6]).
3GPP
3G TS 23.078 V3.2.0 (1999-11)253G TS 23.078 version 3.2.0
7.2.1.1 Description of the call model (PICs)
This subclause describes the call model for originating and forwarded calls. For each PIC a description can be found ofthe entry events, functions and exit events.
It should be noted that although the names used for PICs match those used in ITU-T Q.1214 [6] the specific descriptionsdiffer.
7.2.1.1.1 O_Null & Authorise_Origination_Attempt_Collect_Info
Entry events:- Disconnection and clearing of a previous call (DP9 - O_Disconnect) or default handling of exceptions by
gsmSSF/(G)MSC completed.
- Abandon event is reported from Analyse, Routing and Alerting PIC.
- Exception event is reported.
Functions:- Interface is idled.
- Originating call: SETUP message containing the dialled number is received from MS.
- Originating call: The supplementary service "barring of all outgoing calls" is checked and invoked if necessary.
- Originating call: The ODB category "barring of all outgoing calls" is checked and ODB is invoked if necessary.
NOTE: the ODB category "barring of all outgoing calls when roaming" causes the HLR to send the category"barring of all outgoing call" if the VLR is not in the HPLMN.
- Originating call: CUG checks done in the originating MSC/VLR are performed.
- Information being analysed e.g., O-CSI is analysed.
Exit events:- Originating CSI is analysed.
- An exception condition is encountered. For this PIC, if the call encounters one of these exceptions during the PICprocessing, the exception event is not visible because there is no corresponding DP. Example exceptioncondition : Calling party abandons call.
7.2.1.1.2 Analyse, Routing & Alerting
Entry events:- Originating CSI is analysed. (DP2 - Collected Info).
- Busy event, Route Select Failure event event or No Answer event is reported from Analyse Routing and AlertingPIC.
- Disconnect event is reported from O_Active PIC.
Functions:- Information being analysed and/or translated according to dialling plan to determine routeing address.
- Routeing address being interpreted.
- Originating call: Outgoing barring services and ODB categories not already applied are checked and invoked ifnecessary.
- Call is being processed by the terminating half BCSM. Continued processing of call setup (e.g., ringing) is takingplace. Waiting for indication from terminating half BCSM that the call has been answered by terminating party.
3GPP
3G TS 23.078 V3.2.0 (1999-11)263G TS 23.078 version 3.2.0
Exit events:- Indication from the terminating half BCSM that the call is accepted and answered by terminating party. (DP7 -
O_Answer)
- An exception condition is encountered - this leads to the O_Exception PIC.
- Calling party abandons the call- this leads to the O_Abandon DP.
- A busy indication is received from the terminating party - this leads to the O_Busy DP.
- A not reachable indication is received from the terminating party - this leads to the O_Busy DP.
- Attempt to select the route for the call fails - this leads to the Route_Select_Failure DP.
- If the no reply timer expires and DP O_No_Answer is armed - this leads to the O_No_Answer DP.
7.2.1.1.3 O_Active
Entry events:- Indication from the terminating half BCSM that the call is accepted and answered by the terminating party. (DP7 -
O_Answer)
Functions:- Connection established between originating party and terminating party. Call supervision is provided.
- Call release is awaited.
Exit events:- A disconnection indication is received from the originating party, or received from the terminating party via the
terminating half BCSM. (DP9 - O_Disconnect)
- An exception condition is encountered.
7.2.1.1.4 O_Exception
Entry events:- An exception condition is encountered. In addition to specific examples listed above, exception events include
any type of failure, which means that the normal exit events for a PIC can not be met.
Functions:- Default handling of the exception condition is being provided. This includes general actions necessary to ensure
that no resources remain inappropriately allocated such as:
- If any relationship exists between the gsmSSF and the gsmSCF send an error information flow closing therelationships and indicating that any outstanding call handling instructions will not run to completion
- The (G)MSC/gsmSSF should make use of vendor-specific procedures to ensure release of resources withinthe (G)MSC/gsmSSF, so that line, trunk and other resources are made available for new calls.
Exit events:- Default handling of the exception condition by gsmSSF/(G)MSC completed.
7.3 Terminating Basic Call State Model (T-BCSM)
7.3.1 Description of T-BCSM
The T-BCSM is used to describe the actions in a GMSC during terminating calls.
When encountering a DP the T-BCSM processing is suspended at the DP and the GMSC indicates this to the gsmSSFwhich determines what action, if any, shall be taken in case the DP is armed.
3GPP
3G TS 23.078 V3.2.0 (1999-11)273G TS 23.078 version 3.2.0
T_Null
Terminating Call Handling
DP12
T_Exception
DP17 T_Active
DP15
Terminating_Attempt_Authorised
T_Answer
Basic Call transition
Transition beyond Basic Call
DP13
DP14
T_Busy
T_No_Answer
DP18
T_Abandon
T_Disconnect
A
A
Figure 4: T-BCSM in the GMSC
In the following table the different DPs (in the T-BCSM) are described.
Table 2: Description of T-BCSM DPs in the GMSC
CAMEL Detection Point: DP Type Description:
DP12Terminating_Attempt_Authorised
TDP-R Indication that the T-CSI is analysed.
DP 13 T_Busy EDP-N, EDP-R Indication that:
- a busy indication is received from thedestination exchange,
- Not reachable or call establishment failureevent is determined from the HLR response orupon a cause IE in the ISUP release message.
DP 14 T_No_Answer EDP-N, EDP-R Indication that an application timer associatedwith the T_No_Answer DP expires
DP15 T_Answer EDP-N, EDP-R Call is accepted and answered by terminatingparty
DP17 T_Disconnect EDP-N, EDP-R A disconnect indication is received from theterminating party or from the originating party.
DP 18 T_Abandon EDP-N A disconnect indication is received from theoriginating party during the call establishmentprocedure
3GPP
3G TS 23.078 V3.2.0 (1999-11)283G TS 23.078 version 3.2.0
NOTE: The DPs 12, 13, 14, 15, 17, 18 are defined in ITU-T Q.1214 ([6]).
7.3.1.1 Description of the call model (PICs)
This subclause describes the call model for terminating calls in the GMSC. For each PIC a description can be found of theentry events, functions, information available and exit events.
It should be noted that although the names used for PICs match those used in ITU-T Q.1214 [6] the specific descriptionsdiffer.
7.3.1.1.1 T_Null
Entry events:- Disconnection and clearing of a previous call (DP 17) or default handling of exceptions by gsmSSF/GMSC
completed.
- Abandon event is reported from Terminating Call Handling PIC ;
- Exception event is reported.
Functions:- Interface is idled.
- ISUP_IAM is received, the appropriate information is analysed.
- Send_Routeing_Info information flow is sent to HLR.
- The supplementary services "barring of all incoming calls" and "barring of incoming calls when roaming" arechecked and invoked if necessary.
- The ODB categories "barring of all incoming calls" and "barring of incoming calls when roaming" are checked andODB is invoked if necessary.
- The supplementary service "CUG" is checked and invoked if necessary.
- T-CSI is received and analysed.
Exit events:- Response is received from HLR and terminating CSI (if available) is analysed.
- An exception condition is encountered. For this PIC, if the call encounters one of these exceptions during the PICprocessing, the exception event is not visible because there is no corresponding DP.
Example exception condition is:
- Calling party abandons call.
7.3.1.1.2 Terminating Call Handling
Entry events:- Response is received from HLR and terminating CSI (if available) is analysed. (DP 12
Terminating_Attempt_Authorised),
- Busy event or No Answer event is reported from Terminating Call Handling PIC,
- Disconnect event is reported from T_Active PIC.
- The terminating party is not reachable.
3GPP
3G TS 23.078 V3.2.0 (1999-11)293G TS 23.078 version 3.2.0
NOTE: The HLR may use MAP signalling to indicate to the GMSC before the call is extended to the destinationVMSC that the terminating party is not reachable, or the destination VMSC may use telephony signallingto indicate to the GMSC after the call has been extended to the destination VMSC that the terminatingparty is not reachable.
3GPP
3G TS 23.078 V3.2.0 (1999-11)303G TS 23.078 version 3.2.0
Functions:- The response from HLR is analysed.
- Routeing address and call type being interpreted. The next route is being selected.
- The terminating party is being alerted. Waiting for the call to be answered by terminating party.
- The GSM supplementary service call forwarding is invoked if necessary.
Exit events:- Call is accepted and answered by terminating party.
- An exception condition is encountered - this leads to the T_Exception PIC. Example exception conditions: the callsetup to the MSC/GMSC was not successful.
- Calling party abandons the call - this leads to the T_Abandon DP.
- A busy indication is received from the destination exchange - this leads to the T_Busy DP.
- Not reachable event detected or failure of attempt to select the route for the terminating leg - this leads to theT_Busy DP.
- If no reply timer expires and DP T_No_Answer is armed - this leads to the T_No_Answer DP.
7.3.1.1.3 T_Active
Entry events:- Indication that the call is accepted and answered by the terminating party. (DP15 - T_Answer)
Functions:- Connection established between originating party and terminating party. Call supervision is being provided.
- Call release is awaited.
Exit events:- A disconnection indication is received from the terminating party, or received from the originating party via the
originating half BCSM. (DP17 - T_Disconnect)
- An exception condition is encountered. In addition to specific examples listed above, exception events includeany type of failure that means that the normal exit events for a PIC can not be met.
7.3.1.1.4 T_Exception
Entry events:- An exception condition is encountered. In addition to specific examples listed above, exception events include
any type of failure, which means that the normal exit events for PIC cannot be met.
Functions:- Default handling of the exception condition is being provided. This includes general actions necessary to ensure
that no resources remain inappropriately allocated such as:
- If any relationship exists between the gsmSSF and the gsmSCF send an error information flow closing therelationships and indicating that any outstanding call handling instructions will not run to completion
- The GMSC/gsmSSF should make use of vendor-specific procedures to ensure release of resources within theGMSC/gsmSSF, so that line, trunk and other resources are made available for new calls.
3GPP
3G TS 23.078 V3.2.0 (1999-11)313G TS 23.078 version 3.2.0
Exit events:- Default handling of the exception condition by gsmSSF/GMSC completed.
7.4 Rules for Implicit Disarming of Detection Points'The following tables give the rules for implicit disarming of event detection points.
The table entry 'X' means that if one DP occurs (independently of arming and reporting to the gsmSCF) the marked one isimplicitly disarmed.
It shall be possible to rearm explicitly an implicitly disarmed DP, e.g. for follow on call.
Table 3: Implicit disarmed DPs in the O-BCSM
Encountered DP Implicit disarmed DPs
DP4 DP 5 DP 6 DP 7 DP 9leg 1
DP 9leg 2
DP 10
DP4 Route_Select_Failure X X X X XDP5 O_Busy X X X X XDP6 O_No_Answer X X X X XDP7 O_Answer X X X X XDP9 O_Disconnect leg 1 X XDP9 O_Disconnect leg 2 X X X X XDP10 O_Abandon X X
Table 4: Implicit disarmed DPs in the T-BCSM
Encountered DP Implicit disarmed DPs
DP 13 DP 14 DP 15 DP 17leg 1
DP 17leg 2
DP 18
DP13 T_Busy X X X XDP14 T_No_Answer X X X XDP 15 T_Answer X X X XDP 17 T_Disconnect leg 1 X XDP 17 T_Disconnect leg 2 X X X XDP18 T_Abandon X X
7.5 BCSM Modelling of Call ScenariosThis subclause describes how the BCSMs defined above are used to model GSM call scenarios. For each scenario theused and unused BCSMs involved in the call are shown.
In some cases these models may have an allocation to physical nodes different from that shown. However, the physicalseparation of the logic functions shown shall not impact the modelling. This subclause describes the call scenarioswithout optimal routeing. If optimal routeing is invoked the physical configurations may be different from those shown,but the modelling is not changed.
CAMEL may be applied simultaneously and independently for each GSM subscriber involved in a call. This is notshown in these scenarios.
Subscribers other than those being served by CAMEL may be either PSTN subscribers, other GSM subscribers or anyother addressable subscriber.
3GPP
3G TS 23.078 V3.2.0 (1999-11)323G TS 23.078 version 3.2.0
7.5.1 Mobile Originated Call
The O-BCSM for the call from A to B (labelled "O(A-B)") is invoked if the A-party has an active O-CSI. A controlrelationship with gsmSCF (1) will be created.
MSCgsmSSF/CCF
T(A-B)
B-PartyA-Party
O(A-B)
gsmSCF (1)
CAMEL relationship
Figure 5: BCSM Scenario for Mobile Originated Call
7.5.2 Mobile Terminated Call
The T-BCSM for the call from A to B (labelled "T(A-B)") is invoked if the B-party has an active T-CSI. A controlrelationship with gsmSCF (1) will be created.
GMSCgsmSSF/CCF
T(A-B)
B-PartyA-Party
O(A-B)
gsmSCF (1)
CAMEL relationship
MSCgsmSSF/CCF
Figure 6: BCSM Scenario for Mobile Terminated Calls
7.5.3 Call Forwarding at the GMSC
The T-BCSM for the call from A to B (labelled "T(A-B)") is invoked if the B-party has an active T-CSI. A controlrelationship with gsmSCF (1) will be created.
3GPP
3G TS 23.078 V3.2.0 (1999-11)333G TS 23.078 version 3.2.0
A new call leg to a "C" party is created if:
- a GSM call forwarding supplementary service forwards the call to C. In this case O-BCSM O(B-C) is alwaysinvoked for the forwarding party if an O-CSI has been received by the GMSC from the HLR; or
- a CAMEL service in a control relationship with T(A-B) performs a CAMEL-based call forwarding by using aConnect information flow containing the forwarding information. In this case O-BCSM O(B-C) is only invoked forthe forwarding party if an O-CSI has been received by the GMSC from the HLR and " O-CSI Applicable" flag iscontained in the Connect information flow.
A control relationship with gsmSCF (2) will be created.
The relationships with gsmSCF (1) and gsmSCF(2) may exist simultaneously. The two relationships are treatedindependently at the GMSC. The BCSM T(A-B) and BCSM O(B-C) are linked by an internal interface which is assumedto behave in a similar way to an ISUP interface.
The nodes gsmSCF (1) and gsmSCF (2) may be the same or different physical entities.
GMSCgsmSSF/CCF
T(A-B)
B-Party"surrogate"
A-Party
O(A-B)
gsmSCF (1)
CAMEL relationship (1)
O(B-C)T(B-C)
C-Party
gsmSCF (2)
CAMEL relationship (2)
Internal "ISUP-like" interface
Figure 7: BCSM Scenario for Call Forwarding at the GMSC
7.5.4 Call Forwarding at the MSC
The T-BCSM for the call from A to B (labelled "T(A-B)") is invoked if the B-party has an active T-CSI. A controlrelationship with gsmSCF (1) will be created. Following processing at the GMSC the call will be extended to the MSCserving the B-party. This MSC may be physically integrated with the GMSC, but it is shown as being separate in thediagram below.
If a GSM call forwarding supplementary service acting at the MSC forwards the call to C, a new call leg to C isestablished. If the B-party has an active O-CSI, the BCSM O(B-C) is invoked. A control relationship with gsmSCF (2) willbe created.
The relationships with gsmSCF (1) and gsmSCF(2) may exist simultaneously.
The nodes gsmSCF (1) and gsmSCF (2) may be the same or different physical entities.
3GPP
3G TS 23.078 V3.2.0 (1999-11)343G TS 23.078 version 3.2.0
GMSCgsmSSF/CCF
T(A-B)
B-Party"Surrogate"
A-Party
O(A-B)
gsmSCF (1)
CAMEL relationship (1)
MSCgsmSSF/CCF
C-Party
T(B-C) O(B-C)
gsmSCF (2)
CAMEL relationship (2)
Figure 8: BCSM Scenario for Call Forwarding at the MSC
3GPP
3G TS 23.078 V3.2.0 (1999-11)353G TS 23.078 version 3.2.0
8 Procedures for CAMELThe SDLs in this specification illustrate how CAMEL modifies the normal call handling. They do not attempt to show allthe details of call handling in nodes that support CAMEL. Relevant parts of GSM 03.18 [3] apply in addition to theseSDLs. For example, some inputs leading to unsuccessful call attempts are not shown on these diagrams - correspondingclauses in GSM 03.18 [3] apply.
Note that in some SDL processes and procedures the Release message may be sent on both an access interface and aninter-switch interface. If the message is sent on a UNI, its effect is the same as a Release transaction message.
The text in this clause is a supplement to the definition in the SDL diagrams ; it does not duplicate the information in theSDL diagrams.
In the following SDLs, the term SRF is used for gsmSRF.
8.1 Overall SDL architectureThe following diagram shows the overall architecture for the SDL diagrams.
A interface ISUP interface
Internal interfaceInternal interface
CAP interface
gsmSRFCAP relayinterface
OCH_MSC
gsmSSF
MobileStation
Destinationexchange
gsmSCF
Figure 9a: Outgoing case (gsmSSF relay)
3GPP
3G TS 23.078 V3.2.0 (1999-11)363G TS 23.078 version 3.2.0
A interface ISUP interface
Internal interfaceInternal interface
CAP interface
gsmSRF orAssisting SSP
OCH_MSC
gsmSSF
MobileStation
Destinationexchange
gsmSCF
CAP interface
Figure 9b: Outgoing case (direct path gsmSCF to gsmSRF or assist with relay)
ISUPinterface
ISUPinterface
Internal ISUPinterface
Internal interface Internal interfaceInternal interface Internal interface
CAP interface CAP interface
gsmSRF gsmSRF
MT_GMSC MT_CF_MSC
gsmSSF gsmSSF
Originatingexchange
Destinationexchange
CAP relayinterface
CAP relayinterface
gsmSCF gsmSCF
Figure 9c: Terminating case (gsmSSF relay)
3GPP
3G TS 23.078 V3.2.0 (1999-11)373G TS 23.078 version 3.2.0
ISUPinterface
ISUPinterface
Internal ISUPinterface
Internal interface Internal interfaceInternal interface Internal interface
CAP interface CAP interface
gsmSRF orassisting
SSP
gsmSRF orassisting
SSP
MT_GMSC MT_CF_MSC
gsmSSF gsmSSF
Originatingexchange
Destinationexchange
gsmSCF gsmSCF
CAP interfaceCAP interface
Figure 9d: Terminating case (direct path gsmSCF to gsmSRF or assist with relay)
ISUP interface
Internal interfaceInternal interface
CAP interface
gsmSRFCAP relayinterface
Assisting_MSC
Assisting_gsmSSF
InitiatingMSC
gsmSCF
Figure 9e: Assisting case
3GPP
3G TS 23.078 V3.2.0 (1999-11)383G TS 23.078 version 3.2.0
8.2 Handling of mobile originated calls
8.2.1 Handling of mobile originated calls in the originating MSC
The functional behaviour of the originating VMSC is specified in GSM 03.18 [3]. The procedures specific to CAMEL arespecified in this subclause :
- Procedure CAMEL_OCH_MSC_INIT,
- Procedure CAMEL_OCH_MSC_ANSWER,
- Procedure CAMEL_OCH_MSC1,
- Procedure CAMEL_OCH_MSC2,
- Procedure CAMEL_OCH_MSC_DISC1,
- Procedure CAMEL_OCH_MSC_DISC2,
- Procedure CAMEL_OCH_MSC_DISC4,
- Procedure CAMEL_OCH_ETC,
- Procedure CAMEL_OCH_CTR,
- Procedure CAMEL_Start_TNRy,
- Procedure CAMEL_Stop_TNRy.
The procedure Send_Access_Connect_If_Required is specified in GSM 03.18 [3].
The following paragraphs gives details on the behaviour of the MSC in the procedure CAMEL_OCH_MSC_INIT.
8.2.1.1 Actions of the MSC on receipt of Int_Error
The MSC checks the default Call Handling parameter in O-CSI.
If the default call handling is release call, a Release is sent to the MS and an Abort to the VLR. The MSC then releases allcall resources and the procedure CAMEL_OCH_MSC_INIT ends.
If the default call handling is continue call, the MSC continues processing without CAMEL support. It sendsSend_Info_For_Ougoing_Call to the VLR and waits in state Wait_For_MO_Call_Result.
8.2.1.2 Actions of the MSC on receipt of Int_Continue
The MSC continues processing without any modification of call parameters. It sends Send_Info_For_Ougoing_Call tothe VLR and waits in state Wait_For_MO_Call_Result.
8.2.1.3 Actions of the MSC on receipt of Int_Connect
The MSC continues processing with modified call parameters. The MSC shall transparently modify the call parameterswith the received information. The MSC then sends a PROGRESS message to the MS. Call parameters which are notincluded in the Int_Connect message are unchanged.
Signalling limitations or regulatory requirements may require the Calling Partys Category, Generic Number, OriginalCalled Party Number and Redirecting Party ID to be ignored or modified.
The network signalling system shall indicate that this is an internal network number.
The MSC sets the O-CSI suppression parameter, sends a Send Info For Outgoing Call to the VLR and waits in stateWait_For_MO_Call_Result.
3GPP
3G TS 23.078 V3.2.0 (1999-11)393G TS 23.078 version 3.2.0
8.2.1.4 Actions of the MSC on receipt of Int_Release_Call
A Release is sent to the MS, an abort to the VLR and a Release is sent to the destination exchange. The release causereceived in the Int_Release_Call is used. The MSC then releases all call resources and the procedureCAMEL_OCH_MSC_INIT ends.
8.2.1.5 Action of the MSC in procedure CAMEL_OCH_ETC
In procedure CAMEL_OCH_ETC (sheet 2) the MSC will remain in the Wait_For_Assisting_Answer state until itreceives an ISUP Answer Message (ANM) or timeout occurs. This is to ensure that a call record is always generated forevery successful establishment of a temporary connection to a gsmSRF, especially in the case where the connection isbetween PLMNs.
NOTE: This means that it may not be possible to access an SRF which does not generate an ISUP AnswerMessage (ANM).
If a Progress message is sent towards the MS the progress indicator shall indicate "In Band Information".
3GPP
3G TS 23.078 V3.2.0 (1999-11)403G TS 23.078 version 3.2.0
Procedure in the MSC to per formCAMEL handling for an outgoingc a l l r e q u e s t
Procedure CAMEL_OCH_MSC_INIT 1(4)
Signals to/from the right are to/from the gsmSSF.
O-CSI invocation?
Result:=pass
Allocatecall reference
number
Store originalcall parameters
Int_Invoke_gsmSSF(O-CSI )
Wait_for_gsmSSF_
Invoked
Int_error
Result :=fail
In t_gsmSSF_Invoked
Answer_Received :=False
Int_DP_Collected_Info
DP_Collected_
Info
Release
Int_O_Exception
Result:=fail
N o
Yes
Figure 10a: Procedure CAMEL_OCH_MSC_INIT (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)413G TS 23.078 version 3.2.0
Procedure in the MSC to performCAMEL handling for an outgoingcall request
Procedure CAMEL_OCH_MSC_INIT 2(4)
Signals to/from the left areto/from the BSS; signals to/from the right are to/from the gsmSSF ifnot otherwise stated.
DP_Collected_
_Info
Int_Release_Call
Abort To VLR
Release
Result:=fail
Int_Error
Default callhandling = continue
call ?
Set O-CSIsuppression
Send Info ForOutgoing Call
To VLR
Wait_ForMO_Call_
Result
Send InfoFor OutgoingCall NegativeResponse
From VLR
Int_O_Exception
CompleteCall
From VLR
Result:=pass
Int_Continue Int_Connect
Modify callparameters with
received information
Progress
YesN o
Figure 10b: Procedure CAMEL_OCH_MSC_INIT (sheet 2)
3GPP
3G TS 23.078 V3.2.0 (1999-11)423G TS 23.078 version 3.2.0
Procedure in the MSC to performCAMEL handling for an outgoingcall request
Procedure CAMEL_OCH_MSC_INIT 3(4)
Signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
DP_Collected_Info
Int_Establish_Temporary_Connection
CAMEL_OCH_ETC
Result=fail?
Result:=fail
DP_Collected_Info
Int_Connect_To_Resource
CAMEL_OCH_CTR
YesN o
Figure 10c: Procedure CAMEL_OCH_MSC_INIT (sheet 3)
3GPP
3G TS 23.078 V3.2.0 (1999-11)433G TS 23.078 version 3.2.0
Procedure in the MSC to performCAMEL handling for an outgoingcall request
Procedure CAMEL_OCH_MSC_INIT 4(4)
Signals to/from the left areto/from the BSS; signals to/from the right are to/from the gsmSSF.
DP_Collected_infoWait_For_MO_Call_Result
Release
Int_DP_O_Abandon
Result:=fail
Figure 10d: Procedure CAMEL_OCH_MSC_INIT (sheet 4)
3GPP
3G TS 23.078 V3.2.0 (1999-11)443G TS 23.078 version 3.2.0
Procedure in the MSC to handle an outgoing call
Procedure CAMEL_OCH_MSC_ANSWER 1(1)
Signals to/from the left areto/from the BSS; signals to/from
the right are to/from the gsmSSF ifnot otherwise stated.
gsmSSFinvoked?
Result:=pass
Int_DP_O_Answer
Answer_Received :=True
DP_O_Answer
Int_Continue
Result:=
pass
Int_Release
Release
Release
Result:=
fail
Release
CAMEL_OCH_
MSC_DISC1
Result:CAMEL_Handling
Release
Release From destinationexchange
CAMEL_OCH_
MSC_DISC2
Result=reconnect?
Result:CAMEL_Handling
Release
Answer_Received :=
False
Result:=reconnect
No
Yes
No
Yes
No
No
Yes
Yes
Figure 11a: Procedure CAMEL_OCH_MSC_ANSWER (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)453G TS 23.078 version 3.2.0
Procedure in the MSC in thecase of CAMEL handling toconnect a call at DP Busy,Not reachable, Route select failure.
Procedure CAMEL_OCH_MSC1 1(3)
Signals to/from the right are to/from the gsmSSF ifnot otherwise stated.
gsmSSFinvoked?
Release cause
Int_DP_O_Busy
DP_O_Busy
Int_Connect
Modify call parameterswith received information
Destination numbermodified?
Send Info ForReconnected call
To process CAMEL_Reconnected_Call_VLR
Wait_Forreconnected call
Result_1
Send Info ForReconnected callNegative Response
From process CAMEL_Reconnected_Call_VLR
Int_O_Exception
Result:=continue
Send Info ForReconnected callAck
From process CAMEL_Reconnected_Call_VLR
Result:=reconnect Resul t :=
cont inue
Int_Cont inue Int_Error
Int_DP_Route__Select__Failure
DP_Route__Select__Failure
Int_Release_Call
Result:=continue
Yes
BusySubscriber Absent
Yes
No
Other cause
No
Figure 12a: Procedure CAMEL_OCH_MSC1 (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)463G TS 23.078 version 3.2.0
Procedure in the MSC in thecase of CAMEL handling toconnect a call at DP Busy,Route select failure.
Procedure CAMEL_OCH_MSC1 2(3)
Signals to/from the left areto/from the BSS; signals to/from the right are to/from the gsmSSF ifnot otherwise stated.
DP_O_BusyDP_Route_Select_Failure
Release
Int_DP_O_Abandon
Result:=continue
Figure 12b: Procedure CAMEL_OCH_MSC1 (sheet 2)
3GPP
3G TS 23.078 V3.2.0 (1999-11)473G TS 23.078 version 3.2.0
Procedure in the MSC in thecase of CAMEL handling toconnect a call at DP Busy,Route select failure.
Procedure CAMEL_OCH_MSC1 3(3)
Signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
DP_Route_Select__FailureDP_O_Busy
Int_Establish_Temporary_Connect ion
CAMEL__OCH_ETC
Result=fail?
Result:=cont inue
-
Int_Connect_To_Resource
CAMEL_OCH_CTR
YesN o
Figure 12c: Procedure CAMEL_OCH_MSC1 (sheet 3)
3GPP
3G TS 23.078 V3.2.0 (1999-11)483G TS 23.078 version 3.2.0
Procedure in the MSC toconnect a call at DPNo_Answer
Procedure CAMEL_OCH_MSC2 1(3)
Signals to/from the right are to/from the gsmSSF ifnot otherwise stated.
gsmSSFinvoked?
Result:=continue
Int_DP_O_No_Answer
DP_O_No_Answer
Int_Connect
Modify call parameters with
received information
Destinationmodified?
Send Info ForReconnected Call
To processCAMEL_Reconnected_Call_VLR
Wait_ForReconnected_
Call_2
Send Info ForReconnected CallNegative Response
From processCAMEL_Reconnected_Call_VLR
Int_O_Execption
Result:=release
Send Info ForReconnected CallA c k
From processCAMEL_Reconnected_Call_VLR
Result:=reconnect
Int_O_Exception
Result:=release
Int_Continue Int_Error
Resul t :=release
Int_Release_Call
No
Yes
Yes
No
Figure 13a: Procedure CAMEL_OCH_MSC2 (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)493G TS 23.078 version 3.2.0
Prodecure in the MSC toconnect a call at DPNo_Answer
Procedure CAMEL_OCH_MSC2 2(3)
Signals to/from the left areto/from the BSS; signals to/from the right are to/from the gsmSSF ifnot otherwise stated.
DP_O_No_Answer
Release
Int_DP_O_Abandon
Result:=fail
Figure 13b: Procedure CAMEL_OCH_MSC2 (sheet 2)
3GPP
3G TS 23.078 V3.2.0 (1999-11)503G TS 23.078 version 3.2.0
Prodecure in the MSC toconnect a call at DPNo_Answer
Procedure CAMEL_OCH_MSC2 3(3)
Signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
DP_O_No_Answer
Int_Establish_Temporary_Connection
CAMEL_OCH_ETC
Result=fail?
Result:=release
DP_O_No_Answer
Int_Connect_To_Resource
CAMEL_OCH_CTR
YesNo
Figure 13c: Procedure CAMEL_OCH_MSC2 (sheet 3)
3GPP
3G TS 23.078 V3.2.0 (1999-11)513G TS 23.078 version 3.2.0
Procedure in the MSC performhandling for a call release
Procedure CAMEL_OCH_MSC_DISC1 1(1)
Signals to/from the right are to/from the gsmSSF ifnot otherwise stated.
gsmSSFinvoked?
Int_DP_O_Disconnect/* legId = 1 */
DP_O_Disconnect_1
Int_Error
Release To destination exchange
result:=CAMEL_handling
Int_Continue Int_Release_Call ReleaseFrom destinationexchange
Int_DP_O_Disconnect/* legId = 2 */
DP_O_Disconnect
Int_Error Int_Continue Int_ReleaseCall
result:=normal_handling
Yes
N o
Figure 14a: Procedure CAMEL_OCH_MSC_DISC1 (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)523G TS 23.078 version 3.2.0
Procedure in the MSC performhandling for a call release
Procedure CAMEL_OCH_MSC_DISC2 1(2)Signals to/from the left areto/from the BSS or the processMT_GMSC; signals to/from the right are to/from the gsmSSF ifnot otherwise stated.
gsmSSFinvoked?
Int_DP__O_Disconnect/* legId = 2 */
DP_O_Disconnect_2
Release
Int_DP_O_Disconnect/* legId = 1 */
DP_O_Disconnect
Int_Error
result:=CAMEL_handling
Int_Continue Int_Release_Call
Int_Continue
Release
result:=CAMEL_handling
Int_Release_Call Int_error Int_Connect
Modify call parameters with
received information
Destinationmodified?
Send Info ForReconnected Call
To processCAMEL_Reconnected_Call_VLR
Wait_ForReconnected_
Call_2
Send Info ForReconnected CallNegative Response
From processCAMEL_Reconnected_Call_VLR
Int_O_Exception
Release
result:=CAMEL handling
Send Info ForReconnected CallAck
From processCAMEL_Reconnected_Call_VLR
Answer Received :=False
Result:=reconnect
result:=normal_handling
Yes
No
Yes
N o
Figure 15a: Procedure CAMEL_OCH_MSC_DISC2 (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)533G TS 23.078 version 3.2.0
Procedure in the MSC performhandl ing for a cal l release
Procedure CAMEL_OCH_MSC_DISC2 2(2)
Signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
DP_O_Disconnect_2
Int_Establish_Temporary_Connection
CAMEL_OCH_ETC
Result=fail?
Result:=re lease
DP_O_Disconnect_2
Int_Connect_To_Resource
CAMEL_OCH_CTR
YesN o
Figure 15b: Procedure CAMEL_OCH_MSC_DISC2 (sheet 2)
3GPP
3G TS 23.078 V3.2.0 (1999-11)543G TS 23.078 version 3.2.0
Procedure in the MSC performCAMEL handling for a call release
Procedure CAMEL_OCH_MSC_DISC4 1(1)
Signals to the right are to the gsmSSF
gsmSSFinvoked?
Int_DP_O_Abandon
Yes
No
Figure 16a: Procedure CAMEL_OCH_MSC_DISC4 (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)553G TS 23.078 version 3.2.0
Procedure in the MSC to handle a temporaryconnection
Procedure CAMEL_OCH_ETC 1(3)Signals to/from the left are to/fromthe BSS;signals to/from the right areto/from the gsmSSF;if not otherwise stated.
InitialAddress
To process CAMEL_Assisting_MSCor SRF
Send_Alerting_If_Required
Procedure definedin GSM 03.18
Wait_For_Assisting_ACM
Release
Answer Received
Int_DP_O_Disconnect/*legID*/
Wait_For_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
ReleaseTo processCAMEL_Assisting_MSC or SRF
Result:=pass
Int_DP_O_Abandon
ReleaseTo processCAMEL_Assisting_MSC or SRF
Result:=fail
ReleaseFrom destinationexchange
Int_ETC_Failed
Result:=pass
True False
Figure 17a: Procedure CAMEL_OCH_ETC (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)563G TS 23.078 version 3.2.0
Procedure in the MSC to handle a temporaryconnection
Procedure CAMEL_OCH_ETC 2(3)
Signals to/from the left are to/fromthe BSS;signals to/from the right areto/from the CAMEL_Assisting_MSC or SRF.
Wait_For_Assisting_ACM
AddressComplete
Wait_For_Assisting_
Answer
Answer
Bothwaythrough connection
required?
Send_Access_Connect_
If_Required
Procedure definedin GSM 03.18
Int_TemporaryConnectionEstablished
Temporary_Connection_Established
Connect
Bothwaythrough connection
required?
ProgressSend_Access_
Connect_If_Required
Procedure definedin GSM 03.18
Progress
Yes
No
Yes
N o
Figure 17b: Procedure CAMEL_OCH_ETC (sheet 2)
3GPP
3G TS 23.078 V3.2.0 (1999-11)573G TS 23.078 version 3.2.0
Procedure in the MSC to handle a temporaryconnection
Procedure CAMEL_OCH_ETC 3(3 )
Signals to/from the left are to/fromthe BSS;signals to/from the right areto/from the gsmSSF;if not otherwise stated.
Temporary_Connection_EstablishedWait_For_Assisting_Answer
Release
AnswerReceived
Int_DP_O_Disconnect/*legID*/
Wait_For_Disconnect_Forward_Connection
Int_DP_O_Abandon
ReleaseTo processCAMEL_Assisting_MSC o r SRF
Result:=fail
ReleaseFrom destinationexchange
Int_TC_Released
Result:=pass
Int_Disconnect_Forward_Connection
Int_TC_Released
Release To destinationexchange
Result:=pass
True
false
Figure 17c: Procedure CAMEL_OCH_ETC (sheet 3)
3GPP
3G TS 23.078 V3.2.0 (1999-11)583G TS 23.078 version 3.2.0
Procedure in the originating MSC to handle a Connect To Resourceoperation
Procedure CAMEL_OCH_CTR 1(4)
Signals to/from the left areto/from the BSS;signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
Int_Invoke_SRF To SRF
Await_SRF__Initialisation
Int_SRF_Connection_Failure
from SRF
Int_CTR_Failed
Result:=pass
Int_SRF_Connected from SRF
Connect SRF to the call
Send_Alerting_If_Required
Procedure definedin GSM 03.18
Through-connectionrequired?
Send_Access_Connect_If_
required
Procedure definedin GSM 03.18
Int_SRF_Connected
relay
Y e s
N o
Figure 18a: Procedure CAMEL_OCH_CTR (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)593G TS 23.078 version 3.2.0
Procedure in the originating MSC to handle a Connect To Resourceoperation
Procedure CAMEL_OCH_CTR 2(4)Signals to/from the left areto/from the BSS;signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
Relay
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF
To SRF
Await_SRF_Disconnection_
Continue
Release
AnswerReceived
Int_DP_O_Disconnect/* legID */
Result:=pass
Int_DP_O_Abandon/* legID */
Result:=fail
Int_SRF_Released
From SRF
Int_SRF_Released
Result:=pass
Release
AnswerReceived
Int_DP_O_Disconnect/* legID */
Wait_For_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF
To SRF
Await_SRF_Disconnection_
Active
Int_SRF_Released
Result :=Pass
Int_DP_O_Abandon/* legID */
Wait_For_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF
To SRF
Await_SRF_Disconnection_
Fail
True
False
True
False
Figure 18b: Procedure CAMEL_OCH_CTR (sheet 2)
3GPP
3G TS 23.078 V3.2.0 (1999-11)603G TS 23.078 version 3.2.0
Procedure in the originating MSC to handle a Connect To Resourceoperation
Procedure CAMEL_OCH_CTR 3(4)
Signals to/from the right are to/fromthe gsmSSF.Signals to/from the left are to/fromthe external SRF.
Re lay
CAP_Play_Announcement
CAP_Play_Announcement
Re lay
CAP_Prompt_And_Col lect_User_Information
CAP_Prompt_And_Collect_User_Information
CAP_Specialized_Ressource_Report
CAP_Special ized_Ressource_Report
CAP_Prompt_And_Collect_User_Informationack
CAP_Prompt_And_Collect_User_Informationack
Figure 18c: Procedure CAMEL_OCH_CTR (sheet 3)
3GPP
3G TS 23.078 V3.2.0 (1999-11)613G TS 23.078 version 3.2.0
Procedure in the originating MSC to handle a Connect To Resourceoperation
Procedure CAMEL_OCH_CTR 4(4)
Signals to/from the left areto/from the BSS;signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
Await_SRF_Initialisation
Release
Answer Received
Int_DP_O_Disconnect/*legID*/
Int_Disconnect_SRF To SRF
Await_SRF_Disconnection_
Active
Int_SRF_Released
From SRF
Result:=pass
Int_DP_O_Abandon
Int_Disconnect_SRF To SRF
Await_SRF_Disconnection_
Fail
Int_SRF_Released
From SRF
Result:=fail
True False
Figure 18d: Procedure CAMEL_OCH_CTR (sheet 4)
3GPP
3G TS 23.078 V3.2.0 (1999-11)623G TS 23.078 version 3.2.0
Prodedure in MSC to startt h e t i m e r T N R y
Procedure CAMEL_Start_TNRy 1(1)
TNRy default value available?
gsmSSFinvoked?
DP6 orDP14 armed?
TNRy received?
Start TNRywith received
time value
Start TNRy with default value
Yes
Yes
Yes
No
No
Yes
N o
No
Figure 19a: Procedure CAMEL_Start_TNRy (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)633G TS 23.078 version 3.2.0
Procedure in the MSCto stop the t imer TNRy
Procedure CAMEL_Stop_TNRy 1(1)
gsmSSFinvoked?
TNRyrunning?
Stop TNRy
Yes
Yes
No
No
Figure 20a: Procedure CAMEL_Stop_TNRy (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)643G TS 23.078 version 3.2.0
8.2.2 Handling of mobile originating calls in the originating VLR
The functional behaviour of the originating VLR is specified in GSM 03.18 [3]. The procedure specific to CAMEL arespecified in this subclause :
- Procedure CAMEL_OCH_VLR
- Process CAMEL_Reconnected_Call_VLR
3GPP
3G TS 23.078 V3.2.0 (1999-11)653G TS 23.078 version 3.2.0
Procedure in the VLRto handle an outgoing call stup
Procedure CAMEL_OCH_VLR 1(1)
Signals to/from the left areto/from the MSC
Complete Call
Wait_for_SIFOC_2
Abort
Result:=fail
Send InfoFor OutgoingCall
Result:=pass
Figure 21a: Procedure CAMEL_OCH_VLR (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)663G TS 23.078 version 3.2.0
Process in the VLRto handle Send_Info_For_Reconnected_Call
Process CAMEL_Reconnected_Call_VLR 1(1)
Signals to/from the left areto/from the MSC.
Idle
Send Info ForReconnectedCall
Check_OG_Barring
Check ODB and SS barring.Specified in GSM 03.18
Result=Call barred?
Send Info ForReconnectedCall Ack
Idle
Set error:=Call barred
Send Info ForReconnected CallNegative Response
Idle
N o Yes
Figure 22a: Process CAMEL_Reconnected_Call_VLR (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)673G TS 23.078 version 3.2.0
8.3 Retrieval of routeing information
8.3.1 Retrieval of routeing information in the GMSC
The functional behaviour of the GMSC is specified in GSM 03.18 [3]. The procedures specific to CAMEL are specified inthis subclause :
- Procedure CAMEL_Set_ORA_Parameters
- Procedure CAMEL_MT_GMSC_INIT
- Procedure CAMEL_MT_GMSC_ANSWER
- Procedure CAMEL_MT_GMSC_DISC1
- Procedure CAMEL_MT_GMSC_DISC2
- Procedure CAMEL_MT_GMSC_DISC4,
- Procedure CAMEL_MT_GMSC_DISC5,
- Procedure CAMEL_MT_GMSC_DISC6
- Procedure CAMEL_MT_CTR,
- Procedure CAMEL_MT_ETC
- Procedure CAMEL_Start_TNRy,
- Procedure CAMEL_Stop_TNRy.
- Procedure CAMEL_MT_GMSC_Notify_CF.
The procedure Send_ACM_If_Required is specified in GSM 03.18 [3].
The following paragraphs gives details on the behaviour of the GMSC in the procedure CAMEL_MT_GMSC_INIT.
8.3.1.1 Action of the GMSC on receipt of Int_Release_Call
An ISUP_Release is sent to the originating exchange and resources are released.
8.3.1.2 Action of the GMSC on receipt of Int_Error
The GMSC checks in T-CSI the default Call Handling parameter.
If the default call handling is release call, an ISUP_Release is sent to the originating exchange. The MSC then releases allcall resources and the procedure CAMEL_MT_GMSC_INIT returns result=fail.
If the default call handling is continue call, the MSC continue call handling without CAMEL support.
8.3.1.3 Action of the GMSC on receipt of Int_Continue
If a FTN has been stored the information received from HLR is used to overwrite corresponding call parameters. Notethat the MSISDN is replaced by the FTN as the Called party number. The redirection counter is incremented.
If no FTN has been stored, a Send Routeing Info message including a T-CSI suppression parameter is sent to the HLR.The Send Routing Info includes an indication which phase of CAMEL is supported by the GMSC/gsmSSF.
3GPP
3G TS 23.078 V3.2.0 (1999-11)683G TS 23.078 version 3.2.0
8.3.1.4 Action of the GMSC on receipt of Int_Connect
If the Destination Number received from the gsmSCF (via the gsmSSF) is the same as the ISUP Called party number, i.e.the MSISDN, the following parameters, if received, are used to overwrite the corresponding ISUP parameters (formapping see GSM 09.78 [5]): Calling Partys Category and Generic Number. If received, the Announcement SuppressionIndicator is stored. The further processing is described in subclause 8.3.1.3 with the addition that the AnnouncementSuppression indicator, if stored, is sent to the HLR in the Send_Routeing_Info message.
If:
- the Destination Number received from the gsmSCF (via the gsmSSF) is not the same as the stored ISUP Calledparty number, i.e. the MSISDN; and
- a CUG active indication was received from the HLR ; and
- CUG information was received in the ISUP_IAM for the incoming call,
then an exception event is reported to the process gsmSSF, an ISUP_Release is sent to the originating exchange and allresources are released.
Otherwise the following parameters, if received, are used to overwrite the corresponding ISUP parameters (for mappingsee GSM 09.78 [5]): Destination Number, Calling Partys Category, Generic Number, Original Called Party ID, RedirectingParty ID, Announcement Suppression Indicator, and Redirection Information. Call parameters that are not included in theInt_Connect message are unchanged.
As a network operator option loop prevention mechanisms may cause the redirection information to be ignored ormodified (e.g., if the Redirection counter has been decreased).
Signalling limitations or regulatory requirements may require the Calling Partys Category, Generic Number, OriginalCalled Party Number and Redirecting Party ID to be ignored or modified.
The network signalling system shall indicate that this is an internal network number.
8.3.1.5 Action of the GMSC on receipt of Send_Routeing_Info Negative Response (atstate Wait_For_Routeing_Info_2)
An exception event is reported to the process gsmSSF. If the Announcement Suppression indicator has been receivedfrom the gsmSCF (via the gsmSSF) any announcements or tones shall be suppressed.
8.3.1.6 Action of the GMSC on receipt of Send_Routeing_Info ack with MSRN (at stateWait_For_Routeing_Info_2)
An ISUP_IAM with the MSRN as Called party number is constructed.
8.3.1.7 Action of the GMSC on receipt of Send_Routeing_Info ack with FTN (at stateWait_For_Routeing_Info_2)
The information received from HLR is used to overwrite corresponding call parameters (for details see GSM 03.18 [3]).The redirection counter is incremented.
8.3.1.8 Action of the GMSC on receipt of Send_Routeing_Info ack with O-CSI and FTN(at state Wait_For_Routeing_Info_2)
The information received from the HLR is used to overwrite corresponding call parameters. The redirection counter isincremented. The Called Party Number is set to FTN.
3GPP
3G TS 23.078 V3.2.0 (1999-11)693G TS 23.078 version 3.2.0
8.3.1.9 Action of the GMSC in procedure CAMEL_MT_ETC
In procedure CAMEL_MT_ETC (sheet 2) the GMSC will remain in the Wait_For_Assiting_Answer state until it receivesan ISUP Answer Message (ANM) or timeout occurs. This is to ensure that a call record is always generated for everysuccessful establishment of a temporary connection to a gsmSRF, especially in the case where the connection isbetween PLMNs.
NOTE: This means that it may not be possible to access an SRF which does not generate an ISUP AnswerMessage (ANM).
If a Progress message is sent towards the MS the progress indicator shall indicate "In Band Information".
8.3.1.10 Action of the GMSC in procedure CAMEL_MT_GMSC_Notify_CF
The Forwarding reason is taken from the Send Routeing Info ack (for early call forwarding) or the Resume Call Handling(for Optimal Routeing of Late Call Forwarding).
The Int_DP_T_No_Answer and Int_DP_T_Busy messages include a parameter to indicate that the call has encounteredconditional call forwarding. The gsmSSF will transfer this parameter to the CAP_Event_Report_BCSM message which itsends to the gsmSCF.
3GPP
3G TS 23.078 V3.2.0 (1999-11)703G TS 23.078 version 3.2.0
Procedure in the GMSCto set CAMEL parameters forthe procedure Obtain_Routeing_Address
Procedure CAMEL_Set_ORA_Parameters 1(1)
Call referenceNumber
allocated ?
Allocate Callreference number
No
Yes
Figure 23a: Procedure CAMEL_Set_ORA_Parameters (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)713G TS 23.078 version 3.2.0
Process in the GMSC to perform CAMEL handlingfor a terminating call request
Procedure CAMEL_MT_GMSC_INIT 1(8)
Signals to/from the right are to/fromthe gsmSSF
Reconnect=true?
2
CAMEL informationReceived in SRIack?
MSRNreceived?
FTNReceived?
Result:=FTN
Result:= Fai l
Result:=MSRN
Content ofSRI ack
setCSI=T-CSI
Int_Invoke gsmSSF(T-CSI)
wait_for_gsmSSF_Invoked
Set CSI=T-CSI
Store O-CSI
Set CSI=T-CSI
Store FTN
Set CSI=T-CSI
StoreO-CSI & FTN
Set CSI=O-CSI
set redirectioninformation
Result:=FTN
Yes
No
no
N o
yes
N o
yes
Y e s
T-CSI T-CSIO-CSI
T-CSIFTN
T-CSIO-CSIF T N
FTNO-CSI
Figure 24a: Procedure CAMEL_MT_GMSC_INIT (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)723G TS 23.078 version 3.2.0
Process in the GMSC to perform CAMEL handlingfor a terminating call request
Procedure CAMEL_MT_GMSC_INIT 2(8)
Signals to/from the left are to/fromthe orginating exchange;signals to/from the right are to/fromthe gsmSSF
wait_for_gsmSSF_Invoked
Int_gsmSSF_Invoked
Answer Received:=False
Int_DP_Termination_attempt_Autorized
DP_Termination_attempt_
Autorized
Release
Int_T_Exception
Result:=aborted
Figure 24b: Procedure CAMEL_MT_GMSC_INIT (sheet 2)
3GPP
3G TS 23.078 V3.2.0 (1999-11)733G TS 23.078 version 3.2.0
Process in the GMSC to perform CAMEL handlingfor a terminating call request
Procedure CAMEL_MT_GMSC_INIT 3(8)
Signals to/from the left are to/fromthe orginating exchange;
signals to/from the right are to/fromthe gsmSSF;if not otherwise stated.
DP_Termination__Attempt_
_Authorised
Int_Continue
FTNstored ?
Set T-CSI
suppression
CLI_MT_GMSC
Send
RouteingInfo
To HLR
Wair_For__Routeing_
_Info_2
Set redirection
information
Result:=
FTN
Int_Connect
Send_ACM_If_Required
Procedure definedin GSM 03.18
Destination
Number=called MSISDN
Modify callparameters
with receivedinformation.
OriginalCalled Party Subscribed
To CUG?
CUG info
received inincoming call?
Modify callparameters
with receivedinformation
Apply_O-CSIindicatorpresent?
O-CSIstored ?
FTN:=Destination Routing
Address
CMN:=Destination Routing
Address
Result:=
CMN
Int_Exception
Result:=
fail
1 2
No
Yes
Yes
No
Yes
No
Yes
Yes
No
No
Yes
No
Figure 24c: Procedure CAMEL_MT_GMSC_INIT (sheet 3)
3GPP
3G TS 23.078 V3.2.0 (1999-11)743G TS 23.078 version 3.2.0
Process in the GMSC to perform CAMEL handlingfor a terminating call request
Procedure CAMEL_MT_GMSC_INIT 4(8)
Signals to/from the left are to/fromthe orginating exchange;signals to/from the right are to/fromthe gsmSSF;if not otherwise stated.
DP_Termination_Attempt_
Authorised
Release
Int_DP__T_Abandon
Result:=aborted
Int_ReleaseCall
Result:=fail
Int_Error
Default CallHandling = ContinueCall?
1
Yes
No
Figure 24d: Procedure CAMEL_MT_GMSC_INIT (sheet 4)
3GPP
3G TS 23.078 V3.2.0 (1999-11)753G TS 23.078 version 3.2.0
Process in the GMSC to perform CAMEL handlingfor a terminating call request
Procedure CAMEL_MT_GMSC_INIT 5(8)
Signals to/from the right are to/fromthe gsmSSF.
DP_Termination_Attempt_AuthorisedDP_T_Busy
Int_Establish_Temporary_Connection
CAMEL_MT_ETC
Result=fail?
Result:=fail
-
Int_Connect_To_Resource
CAMEL_MT_CTR
YesN o
Figure 24e: Procedure CAMEL_MT_GMSC_INIT (sheet 5)
3GPP
3G TS 23.078 V3.2.0 (1999-11)763G TS 23.078 version 3.2.0
Process in the GMSC to perform CAMEL handlingfor a terminating call request
Procedure CAMEL_MT_GMSC_INIT 6(8)
Signals to/from the right are to/fromthe gsmSSF;if not otherwise stated.
Wait_For_Routeing_
Info_2
Send RouteingInfoNegative Response
From HLR
Cause=Absent
Subscriber?
Int_DP_T_Busy
DP_T_Busy
Int_DP_T_Abandon
Result:=fail
Int_Release_Call
Result:=Fail
Yes
No
Figure 24f: Procedure CAMEL_MT_GMSC_INIT (sheet 6)
3GPP
3G TS 23.078 V3.2.0 (1999-11)773G TS 23.078 version 3.2.0
Process in the GMSC to perform CAMEL handlingfor a terminating call request
Procedure CAMEL_MT_GMSC_INIT 7(8)
Signals to/from the left are to/fromthe orginating exchange;signals to/from the right are to/fromthe gsmSSF;if not otherwise stated.
Wait_For__Routeing_
_Info_2
Send RouteingInfo Ack/* FTN */
From HLR
Set redirectioninformation
Result:=FTN
Send RouteingInfo Ack/* FTN, O-CSI */
From HLR
Store O-CSI
Send RouteingInfo Ack/* MSRN */
From HLR
Result:=MSRN
Figure 24g: Procedure CAMEL_MT_GMSC_INIT (sheet 7)
3GPP
3G TS 23.078 V3.2.0 (1999-11)783G TS 23.078 version 3.2.0
Process in the GMSC to perform CAMEL handlingfor a terminating call request
Procedure CAMEL_MT_GMSC_INIT 8(8)Signals to/from the left are to/fromthe orginating exchange;signals to/from the right are to/fromthe gsmSSF;if not otherwise stated.
DP_T_busy
Release
Int_DP_T_Abandon
Result:=aborted
Int_Release
Result:=fail
Int_Error
Int_T_Exception
Result:=fail
Int_Continue Int_Connect
Destinationaddress modified?
2 Int_T_Exception
Result:=fail
Yes
No
Figure 24h: Procedure CAMEL_MT_GMSC_INIT (sheet 8)
3GPP
3G TS 23.078 V3.2.0 (1999-11)793G TS 23.078 version 3.2.0
Process in the GMSC to handle aterminating call request
Procedure CAMEL_MT_GMSC_ANSWER 1(1)
Signals to/from the left are to/fromthe originating exchange;signals to/from the right are to/fromthe terminating exchange if nototherwise stated.
gsmSSFinvoked?
Result:=pass
Int_DP_T_Answer to gsmSSF
Answer Received :=True
DP_T_Answer
Int_Release from gsmSSF
Release
Release
Result:=fail
Release
CAMEL_MT_GMSC_DISC1
Result=CAMEL_handling?
Release
Result:=fail
Release
CAMEL_MT_GMSC_DISC2
Result=reconnect?
Result=CAMEL_handling?
Release
Answer Received :=False
Result:=reconnect
Int_continuefrom gsmSSF
Result:=pass
noyes
No
Yes
N o
N o
Yes
Figure 25a: Procedure CAMEL_MT_GMSC_ANSWER (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)803G TS 23.078 version 3.2.0
Process in the GMSC to handle aterminat ing cal l request
Procedure CAMEL_MT_GMSC_DISC1 1(1)
Signals to/from the r ight are to/ f rom the gsmSSF i fnot otherwise stated.
gsmSSF
invoked?
Int_DP_T_Disconnect/* legId = 1 */
DP_T_Disconnect_1
In t_Error
ReleaseTo destinationexchangeo r MT_CF_MSC
Result:=CAMEL_Handl ing
Int_Continue Int_Release_Cal l Release
In t_DP_T_Disconnect/ * leg Id = 2 * /
D P _T_Disconnect
Int_Error Int_Continue Int_ReleaseCall
Result:=normal_handling
From destination
exchange or processMT_CF_MSC
Yes
No
Figure 26a: Procedure CAMEL_MT_GMSC_DISC1 (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)813G TS 23.078 version 3.2.0
Process in the GMSC to handle aterminating call request
Procedure CAMEL_MT_GMSC_DISC2 1(2)
Signals to/from the left are to/from theoriginating exchange;signals to/from the right are to/from the gsmSSF ifnot otherwise stated.
gsmSSFinvoked?
Int_DP_T_Disconnect/* legId = 2 */
DP_T_Disconnect_2
Int_Connect
Destinationaddress modified?
Answer Received :=False
Modify callparameters with
received information
Result:=reconnect
Int_T_Exception
Release
Result:=CAMEL handling
Int_Error
Release
Result:=CAMEL_handling
Int_Continue Int_Release_Call Release
Int_DP_T_Disconnect/* legId = 1 */
DP_T_Disconnect
Int_Error Int_Continue Int_ReleaseCall
Result:=normal_handling
Yes
Yes
No
No
Figure 27a: Procedure CAMEL_MT_GMSC_DISC2 (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)823G TS 23.078 version 3.2.0
Process in the GMSC to handle aterminating call request
Procedure CAMEL_MT_GMSC_DISC2 2(2)
Signals to/from the right are to/from thegsmSSF.
Result:=fail
DP_T_Disconnect_2
CAMEL_MT_CTR
Result=fail?
CAMEL_MT_ETC
Int_Connect_To_Ressource
Int_Establish_Temporary_Connection
DP_T_Disconnect_2
YesNo
Figure 27b: Procedure CAMEL_MT_GMSC_DISC2 (sheet 2)
3GPP
3G TS 23.078 V3.2.0 (1999-11)833G TS 23.078 version 3.2.0
Procedure in the GMSC to handle aterminating call request
Procedure CAMEL_MT_GMSC_DISC4 1(3)
Signals to/from the left are to/fromthe orginating exchange;signals to/from the right are to/fromthe gsmSSF.
gsmSSFinvoked?
Result:=fail
Int_DP_T_Busy
DP_T_Busy
Int_Connect
Modify callparameters with
received information
Destination Number
Modified?
Result:=reconnect
Result:=fail
Int_Continue Int_Error Int_Release_Call
N o
Yes
No
Yes
Figure 28a: Procedure CAMEL_MT_GMSC_DISC4 (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)843G TS 23.078 version 3.2.0
Procedure in the GMSC to handle aterminating call request
Procedure CAMEL_MT_GMSC_DISC4 2(3)
Signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
DP_T_Busy
Int_Establish_Temporary_Connection
CAMEL_MT_ETC
Result=fail?
Result:=fail
-
Int_Connect_To_Resource
CAMEL_MT_CTR
Y e sN o
Figure 28b: Procedure CAMEL_MT_GMSC_DISC4 (sheet 2)
3GPP
3G TS 23.078 V3.2.0 (1999-11)853G TS 23.078 version 3.2.0
Procedure in the GMSC to handle aterminating call request
Procedure CAMEL_MT_GMSC_DISC4 3(3)
Signals to/from the left are to/fromthe orginating exchange;signals to/from the right are to/fromthe gsmSSF.
DP_T_Busy
Release
Int_DP_T_Abandon
Result:=fail
Figure 28c: Procedure CAMEL_MT_GMSC_DISC4 (sheet 3)
3GPP
3G TS 23.078 V3.2.0 (1999-11)863G TS 23.078 version 3.2.0
Process in the GMSC to handle aterminating call request
Procedure CAMEL_MT_GMSC_DISC5 1(3)
Signals to/from the right are to/fromthe gsmSSF;if not otherwise stated.
Destinationaddress modified?
gsmSSFinvoked?
Result:=continue
ReleaseTo processMT_CF_MSC
Int_DP_T__No_Answer
ORA result=Forward
ReleaseTo processMT_CF_MSC
DP_T_No_Answer
Int_Connect
Modify callparameters with
received information
Result:=reconnect
Int_Continue
Int_T_Exception
Result:=release
Int_Error
Result:=release
Int_Release_Call
Result:=release
Int_T_Exception
Yes
No
Yes
Yes
No
No
Figure 29a: Procedure CAMEL_MT_GMSC_DISC5 (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)873G TS 23.078 version 3.2.0
Process in the GMSC to handle aterminating call request
Procedure CAMEL_MT_GMSC_DISC5 2(3)
Signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
DP_T_No_Answer
Int_Establish_Temporary_Connection
CAMEL_MT_ETC
Result=fail?
Result:=release
DP_T_No_Answer
Int_Connect_To_Resource
CAMEL_MT_CTR
YesNo
Figure 29b: Procedure CAMEL_MT_GMSC_DISC5 (sheet 2)
3GPP
3G TS 23.078 V3.2.0 (1999-11)883G TS 23.078 version 3.2.0
Process in the GMSC to handle aterminating call request
Procedure CAMEL_MT_GMSC_DISC5 3(3)
Signals to/from the left are to/fromthe orginating exchange;signals to/from the right are to/fromthe gsmSSF;if not otherwise stated.
DP_T_No_Answer
Release
Int_DP_T_Abandon
Result:=fail
Figure 29c: Procedure CAMEL_MT_GMSC_DISC5 (sheet 3)
3GPP
3G TS 23.078 V3.2.0 (1999-11)893G TS 23.078 version 3.2.0
Process in the GMSC to handle aterminating call request
Procedure CAMEL_MT_GMSC_DISC6 1(1)
Signals to/from the right are to/fromthe gsmSSF;if not otherwise stated.
gsmSSFinvoked?
Result:=continue
Int_DP_T_Abandon
Result:=fail
No
Yes
Figure 30a: Procedure CAMEL_MT_GMSC_DISC6 (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)903G TS 23.078 version 3.2.0
Procedure in the GMSC to handle a temporaryconnection
Procedure CAMEL_MT_ETC 1 ( 3 )
Signals to/from the left are to/fromthe originating exchange;signals to/from the right are
to/from the gsmSSF;if not otherwise stated.
InitialAddress
To process CAMEL_Assis t ing_MSC or SRF.
Send_ACM_If_Required
Procedure definedin GSM 03.18
Wait_For_Assist ing_ACM
Release
Answer
Received
Int_DP_T_Disconnect/*legID*/
Wait_For_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
ReleaseTo processCAMEL_Assist ing_MSC or SRF
Result:=pass
Int_DP_T_Abandon
ReleaseTo processCAMEL_Assisting_M S C o r S R F
Result:=fail
Release From destinationexchange
Int_ETC_Failed
Result:=pass
True False
Figure 31a: Procedure CAMEL_MT_ETC (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)913G TS 23.078 version 3.2.0
Procedure in the GMSC to handle a temporary
connection
Procedure CAMEL_MT_ETC 2(3)
Signals to/from the left are to/fromthe originationg exchange;
signals to/from the right areto/from the CAMEL_Assisting_MSC or SRF.
Wait_For_
Assist ing_ACM
Address
Complete
Wait_For_
Assisting_Answer
Answer
Bothwaythrough connection
required?
Send_Answer_
If_Required
Procedure defined
in GSM 03.18
Int_TemporaryConnection
Established
Temporary_Connection_Established
Send_ACM_
If_Required
Procedure defined
in GSM 03.18
Connect
Bothwaythrough connection
required?
ProgressSend_Network_
Connec t_ I f_Required
Procedure defined
in GSM 03.18
Yes
N o N o
Yes
Figure 31b: Procedure CAMEL_MT_ETC (sheet 2)
3GPP
3G TS 23.078 V3.2.0 (1999-11)923G TS 23.078 version 3.2.0
Procedure in the GMSC to handle a temporaryconnection
Procedure CAMEL_MT_ETC 3(3)
Signals to/from the left are to/fromthe orinating exchange;signals to/from the right areto/from the gsmSSF;if not otherwise stated.
Temporary_Connection_EstablishedWait_For_Assisting_Answer
Release
AnswerReceived
Int_DP_T_Disconnect/*legID*/
Wait_For_Disconnect_Forward_Connection
Int_DP_T_Abandon
ReleaseTo processCAMEL_Assisting_MSC or SRF
Result:=fail
Release From destinationexchange
Int_TC_Released
Result:=pass
Int_Disconnect_Forward_Connection
Int_TC_Released
Release To destinationexchange
Result:=pass
True
false
Figure 31c: Procedure CAMEL_MT_ETC (sheet 3)
3GPP
3G TS 23.078 V3.2.0 (1999-11)933G TS 23.078 version 3.2.0
Procedure in the GMSC to handle
a Connect To Resource operation
Procedure CAMEL_MT_CTR 1(4)
Signals to/from the left areto/from the originating exchange;
signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
Int_Invoke_
SRFTo SRF
Await_SRF_
_Initialisation
Int_SRF_Connection_Failure
from SRF
Int_CTR_Failed
Result:=
continue
Int_SRF_
ConnectedFrom SRF
Connect SRF to
the call
Send_ACM_
If_Required
Procedure defined
in GSM 03.18
Through-connect ion
required?
Send_Network_Connect_If_
Required
Procedure definedin GSM 03.18
Int_SRF_Connected
relay
Yes
N o
Figure 32a: Procedure CAMEL_MT_CTR (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)943G TS 23.078 version 3.2.0
Procedure in the GMSC to handlea Connect To Resource operation
Procedure CAMEL_MT_CTR 2(4)Signals to/from the left areto/from the originating exchange;signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
Relay
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF
To SRF
Await_SRF_Disconnection_
Continue
Release
Answer Received
Int_DP_T_Disconnect/* legID */
Result:=pass
Int_DP_T_Abandon/* legID */
Result:=fail
Int_SRF_Released
From SRF
Int_SRF_Released
Result:=pass
Release
Answer Received
Int_DP_T_Disconnect/* legID */
Wait_For_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
Int_Disconnect_S R F
To SRF
Await_SRF_Disconnection_
Active
Int_SRF_Released
Result :=Pass
Int_DP_T_Abandon/* legID */
Wait_For_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF
To SRF
Await_SRF_Disconnection_
Fail
True
False
True
False
Figure 32b: Procedure CAMEL_MT_CTR (sheet 2)
3GPP
3G TS 23.078 V3.2.0 (1999-11)953G TS 23.078 version 3.2.0
Procedure in the GMSC to handle
a Connect To Resource operat ion
Procedure CAMEL_MT_CTR 3(4)
Signals to/from the right are to/fromthe gsmSSF.Signals to/ f rom the lef t are to/ f romthe external SRF.
Relay
CAP_Play_Announcement
CAP_Play_Announcement
Relay
CAP_Prompt_And_Col lect_User_Informat ion
CAP_Prompt_And_Collect_User_Information
CAP_Specialized_Ressource_Report
CAP_Specialized_Ressource_Report
CAP_Prompt_And_Collect_User_Informationack
CAP_Prompt_And_Collect_User_Informationack
Figure 32c: Procedure CAMEL_MT_CTR (sheet 3)
3GPP
3G TS 23.078 V3.2.0 (1999-11)963G TS 23.078 version 3.2.0
Procedure in the GMSC to handlea Connect To Resource operation
Procedure CAMEL_MT_CTR 4(4)
Signals to/from the left areto/from the originating exchange;signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
Await_SRF_Initialisation
Release
Answer Received
Int_DP_T_Disconnect/*legID*/
Wait_For_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF To SRF
Await_SRF_Disconnection_
Active
Int_SRF_Released
From SRF
Result:=pass
Int_DP_T_Abandon
Wait_For_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF To SRF
Await_SRF_Disconnection_
Fail
Int_SRF_Released
From SRF
Result:=fail
True False
Figure 32d: Procedure CAMEL_MT_CTR (sheet 4)
3GPP
3G TS 23.078 V3.2.0 (1999-11)973G TS 23.078 version 3.2.0
Procedure in the GMSC to not i fy the gsmSSF thata cal l has encountered condit ional cal l forwarding
Procedure CAMEL_MT_GMSC_Noti fy_CF 1(1)
Signals to/from the left areto/from the or iginat ing MSC;signals to/from the right areto/from the gsmSSFunless marked otherwise
Forward ing reason=No subscriber reply
Forward ing reason=Mob i le subscr iber not reachable
Forward ing reason=Busy
Int_DP_T_Busy(CF)
D P _ T _ C C F
Release
In t_DP_T_Abandon
C Fcancelled
To procesM T _ C F _ M S C
Release ca l lresources
Result :=Fa i l
Int_Continue
Result:=Continue
Int_Connect
Result:=Reconnect
Int_Release_C a l l
Release
C Fcancelled
To procesM T _ C F _ M S C
Release cal lresources
Result :=Fa i l
Result:=Continue
Int_DP_T_No_Answer(CF)
False
False
T r u e
False
T r u e
T r u e
Figure 33a: Procedure CAMEL_MT_GMSC_Notify_CF (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)983G TS 23.078 version 3.2.0
8.3.2 Retrieval of routeing information in the HLR
The functional behaviour of the HLR is specified in GSM 03.18 [3]. The procedures specific to CAMEL are specified inthis subclause :
- CAMEL_HLR_INIT,
- CAMEL_CSI_Check_HLR,
- CAMEL_O_CSI_CHECK_HLR,
- CAMEL_T_CSI_CHECK_HLR,
The procedure CAMEL_Provide_Subscriber_Info is specified in subclause 8.8.
3GPP
3G TS 23.078 V3.2.0 (1999-11)993G TS 23.078 version 3.2.0
This procedure is called inSRI_HLR (in GSM 03.18)
Procedure CAMEL_HLR_INIT 1(1)
CAMELsubscriber
Triggering criteriastored?
Triggering criteriafulfilled?
GMSC supports CAMEL
phase 2
GMSC supports CAMEL
phase 1
CAMEL phase 1sufficient?
Result:=pass
Defaulthandl ing?
Result:=fail
Normal call handling according
to GSM 03.18
Result:=pass
Network specifichandling
The network specific handlingshall include the result of the procedureCAMEL_HLR_INIT (fail, pass)
Set negativeresponse: Call Barred
Yes
Yes
Yes
No
Yes
Yes
No
O D BContinue
Networkspecific
No
Yes
No
No
No
Figure 34a: Procedure CAMEL_HLR_INIT (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1003G TS 23.078 version 3.2.0
This procedure in the HLRto perform the handling for aforwarded CAMEL call
Procedure CAMEL_CSI_Check_HLR 1(1)
CAMEL_T_CSI_CHECK_HLR
Result=T-CSI
active?
CAMEL_O_CSI_CHECK_HLR
Result:=CSI active
Result:=CSI not active
Yes
No
Figure 35a: Procedure CAMEL_CSI_Check_HLR (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1013G TS 23.078 version 3.2.0
Procedure in the HLR to checkthe O-CSI and set the O-CSIparameter for SRI ack accordingly.
Procedure CAMEL_O_CSI_CHECK_HLR 1(1)
O-CSIprovisioned?
Set O-CSIparameter
Y e s
N o
Figure 36a: Procedure CAMEL_O_CSI_CHECK_HLR (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1023G TS 23.078 version 3.2.0
Procedure in the HLR tocheck the T-CSI and set the SRI ack parameter accordingly
Procedure CAMEL_T_CSI_CHECK_HLR 1(1)
T-CSIprovisioned?
SuppressT-CSI?
Subscriberinfo
required?
CAMEL_Provide_Subscriber_
Info_HLR
Set T-CSIparameter
Result:=S R I
Result:=continue
No
Yes
No
Y e s
No
Yes
Figure 37a: Procedure CAMEL_T_CSI_CHECK_HLR (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1033G TS 23.078 version 3.2.0
8.3.3 Handling of provide roaming number request in the VLR
The functional behaviour of the VLR is specified in GSM 03.18 [3]. The procedure specific to CAMEL is specified in thissubclause :
- CAMEL_SET_SOA.
3GPP
3G TS 23.078 V3.2.0 (1999-11)1043G TS 23.078 version 3.2.0
Procedure in the VLR to set thesuppression of announcement indicator as required for this call
Procedure CAMEL_SET_SOA 1(1)
Suppression ofannouncement
required?
Suppression ofannouncementrequired:=false
Suppression ofannouncementrequired:=true
N o
Yes
Figure 38a: Procedure CAMEL_SET_SOA (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1053G TS 23.078 version 3.2.0
8.4 Handling of mobile terminating calls
8.4.1 Handling of mobile terminating calls in the terminating VMSC
The functional behaviour of the terminating VMSC is specified in GSM 03.18 [3]. The only behaviour specific to CAMELis:
- the inclusion of the O-CSI parameter in the Perform Call Forwarding message sent to the process MT_CF_MSC ifit was received in the Send Info For Incoming Call ack;
- the requirement to suppress the connection of announcements or tones if the VLR includes the suppression ofannouncements parameter in the Send Info For Incoming Call negative response.
8.4.2 Handling of mobile terminating calls in the VLR
The functional behaviour of the terminating VLR is specified in GSM 03.18 [3]. The only behaviour specific to CAMEL is:
- the inclusion of the O-CSI parameter in the Send Info For Incoming Call ack if the call is to be forwarded and O-CSI is included in the subscriber data for that subscriber in the VLR;
- the inclusion of the suppression of announcements parameter in the Send Info For Incoming Call negativeresponse if it was received in the Provide Roaming Number.
8.5 Handling of forwarded callsThe handling of forwarded calls in the GMSC or the terminating VMSC is specified in GSM 03.18 [3]. The proceduresspecific to CAMEL are specified in this subclause.
- Procedure CAMEL_CF_MSC_INIT,
- Procedure CAMEL_CF_MSC_ANSWER
- Procedure CAMEL_CF_ETC,
- Procedure CAMEL_CF_CTR,
- Procedure CAMEL_Check_ORLCF_VMSC.
A mobile terminated call can be forwarded either in the GMSC (indicated by provision of Forwarded-To-Number fromHLR or gsmSCF) or in the MSC (indicated by provisioning of Forwarded-To-Number from VLR).
8.5.1 Procedure CAMEL_CF_MSC_INIT : handling of Int_Connect
The received parameters are used to overwrite the corresponding ISUP parameters (for mapping see GSM 09.78 [5]. Callparameters which are not included in the Int_Connect message are unchanged.
An a network operator option, loop prevention mechanisms may cause the redirection information to be ignored ormodified (e.g., if the Redirection counter has been decreased).
Signalling limitations or regulatory requirements may require the Calling Partys Category, Generic Number, OriginalCalled Party Number and Redirecting Party ID to be ignored or modified.
The network signalling system shall indicate that this is an internal network number.
3GPP
3G TS 23.078 V3.2.0 (1999-11)1063G TS 23.078 version 3.2.0
8.5.2 Action of the GMSC in procedure CAMEL_CF_ETC
In procedure CAMEL_CF_ETC (sheet 2) the GMSC or terminating VMSC will remain in the Wait_For_Assiting_Answerstate until it receives an ISUP Answer Message (ANM) or timeout occurs. This is to ensure that a call record is alwaysgenerated for every successful establishment of a temporary connection to a gsmSRF, especially in the case where theconnection is between PLMNs.
NOTE: This means that it may not be possible to access an SRF which does not generate an ISUP AnswerMessage (ANM).
3GPP
3G TS 23.078 V3.2.0 (1999-11)1073G TS 23.078 version 3.2.0
Procedure in the MSC to handle a forwarded call
Procedure CAMEL_CF_MSC_INIT 1(4)
Signals to/from the left are to/fromthe process MT_GMSC;signals to/from the right are to/fromthe process gsmSSF if nototherwise stated.
O-CSIstored,
Result:=pass
Int_Invoke gsmSSF(O-CSI)
Wait_For__gsmSSF__Invoked
Int_Error
Release
Result:=fail
Int_gsmSSF Invoked
Answer Received :=False
Int_DP__Collected__Info
DP__Collected_
_Info
CF Cancelled
Int_O_Exception
Result:=cancelled
No
Yes
Figure 39a: Procedure CAMEL_CF_MSC_INIT (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1083G TS 23.078 version 3.2.0
Procedure in the MSC to handle a forwarded call
Procedure CAMEL_CF_MSC_INIT 2(4)
Signals to/from the left are to/fromthe process MT_GMSC;signals to/from the right are to/fromthe process gsmSSF if nototherwise stated.
D P _Collected_
_Info
Int_Release_Call
Release
Result:=fail
Int_Error
Default CallHandling = ContinueCall?
Result:=pass
Int_Continue Int_Connect
Modify call parameterswith received information
No
Figure 39b: Procedure CAMEL_CF_MSC_INIT (sheet 2)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1093G TS 23.078 version 3.2.0
Procedure in the MSC to
handle a forwarded call
Procedure CAMEL_CF_MSC_INIT 3(4)
Signals to/from the right are to/from
the gsmSSF if not otherwise stated.
DP_Collected_
I n f o
Int_Establish_
Temporary_Connection
CAMEL_CF_ETC
Result=
fail?
Resu l t :=
f a i l
DP_Collected_In fo
Int_Connect_To_
Resource
CAMEL_CF_CTR
YesN o
Figure 39c: Procedure CAMEL_CF_MSC_INIT (sheet 3)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1103G TS 23.078 version 3.2.0
Procedure in the MSC to handle a forwarded call
Procedure CAMEL_CF_MSC_INIT 4(4)
Signals to/from the left are to/fromthe process MT_GMSC;signals to/from the right are to/fromthe gsmSSF;if not otherwise stated.
DP_Collected_Info
Release
Int_DP_O_Abandon
Result:=fail
Figure 39d: Procedure CAMEL_CF_MSC_INIT (sheet 4)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1113G TS 23.078 version 3.2.0
Procedure in the MSC to handlea fowarded call
Procedure CAMEL_CF_MSC_ANSWER 1(1)
Signals to/from the leftare to/from the processMT_GMSC; signals to/from the rightare to/from the terminatingexchange.
gsmSSFexists?
result=pass Int_O_Answer to the gsmSSF
Answer Received :=True
DP_O_Answer
Int_Releasefrom thegsmSSF
Release
Release
Result=:fail
Int_continuefrom thegsmSSF
Result:=pass
Release
CAMEL_OCH_MSCDISC_1
Result=CAMEL_handling?
Release
Result:=fail
Release
CAMEL_OCH_MSCDISC_2
Result=reconnect?
Result=CAMEL_handling?
Release
Answer Received :=False
Result:=reconnect
no
yes
No
Yes
N o
N o
Yes
Figure 40a: Procedure CAMEL_CF_MSC_ANSWER (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1123G TS 23.078 version 3.2.0
Procedure in the MSC to handle a temporaryconnection
Procedure CAMEL_CF_ETC 1(3)
Signals to/from the left are to/fromthe process MT_GMSC;signals to/from the right areto/from the gsmSSF;if not otherwise stated.
InitialAddress
To process CAMEL_Assisting_MSC or SRF
Send_ACM_If_Required
Procedure definedin GSM 03.18
Wait_For_Assisting_ACM
Release
Answer Received
Int_DP_O_Disconnect/*legID*/
Wait_For_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
ReleaseTo processCAMEL_Assisting_MSC or SRF
Result:=pass
Int_DP_O_Abandon
ReleaseTo processCAMEL_Assisting_MSC or SRF
Result:=fail
ReleaseFrom destinationexchange
Int_ETC_Failed
Result:=pass
True False
Figure 41a: Process CAMEL_CF_ETC (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1133G TS 23.078 version 3.2.0
Procedure in the MSC to handle a temporary
connection
Procedure CAMEL_CF_ETC 2(3)
Signals to/from the left are to/from
the process MT_GMSC;signals to/from the right areto/from the CAMEL_Assisting_MSC or SRF.
Wait_For_
Assist ing_ACM
Address
Complete
Wait_For_Assisting_
Answer
Answer
Bothwaythrough connection
required?
Send_Answer_
If_Required
Procedure defined
in GSM 03.18
Int_TemporaryConnection
Established
Temporary_Connection_
Established
Send_ACM_
If_Required
Procedure defined
in GSM 03.18
Connect
Bothwaythrough connection
required?
ProgressSend_Network_
Connec t_ I f_Required
Procedure defined
in GSM 03.18
Yes
N o N o
Yes
Figure 41b: Procedure CAMEL_CF_ETC (sheet 2)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1143G TS 23.078 version 3.2.0
Procedure in the MSC to handle a temporaryconnection
Procedure CAMEL_CF_ETC 3(3)
Signals to/from the left are to/fromthe process MT_GMSC;signals to/from the right areto/from the gsmSSF;if not otherwise stated.
Temporary_Connection_EstablishedWait_For_Assisting_Answer
Release
Answer Received
Int_DP_O_Disconnect/*legID*/
Wait_For_Disconnect_
Forward_Connection
Int_DP_O_Abandon
ReleaseTo processCAMEL_Assisting_MSC or SRF
Result:=fail
Release From destinationexchange
Int_TC_Released
Result:=pass
Int_Disconnect_Forward_Connection
Int_TC_Released
ReleaseTo destinationexchange
Result:=pass
True
false
Figure 41c: Procedure CAMEL_CF_ETC (sheet 3)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1153G TS 23.078 version 3.2.0
Procedure in the MSC to handle a Connect To Resource
operation
Procedure CAMEL_CF_CTR 1(4)
Signals to/from the left areto/from the process MT_GMSC;signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
Int_Invoke_
SRFTo SRF
Await_SRF_
_Initialisation
In t_SRF_Connection_Failure
f rom SRF
Int_CTR_Failed
Result :=pass
Int_SRF_
Connectedfrom SRF
Connect SRF to
the call
Send_ACM_
If_Required
Procedure defined
in GSM 03.18
Through-
connection
required?
Send_Network_Connect_I f_
required
Procedure definedin GSM 03.18
Int_SRF_Connected
relay
Yes
N o
Figure 42a: Process CAMEL_CF_CTR (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1163G TS 23.078 version 3.2.0
Procedure in the MSC to handle a Connect To Resourceoperation
Procedure CAMEL_CF_CTR 2(4)Signals to/from the left areto/from the process MT_GMSC;signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
Relay
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF
To SRF
Await_SRF_Disconnection_
Continue
Release
Answer Received
Int_DP_O_Disconnect/* legID */
Result:=pass
Int_DP_O_Abandon/* legID */
Result:=fail
Int_SRF_Released
From SRF
Int_SRF_Released
Result:=pass
Release
Answer Received
Int_DP_O_Disconnect/* legID */
Wait_For_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF
To SRF
Await_SRF_Disconnection_
Active
Int_SRF_Released
Result :=Pass
Int_DP_O_Abandon/* legID */
Wait_For_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF
To SRF
Await_SRF_Disconnection_
Fail
True
False
True
False
Figure 42b: Procedure CAMEL_CF_CTR (sheet 2)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1173G TS 23.078 version 3.2.0
Procedure in the MSC to handle a Connect To Resourceoperation
Procedure CAMEL_CF_CTR 3(4)
Signals to/from the right are to/fromthe gsmSSF.Signals to/ from the lef t are to/ fromthe external SRF.
Relay
CAP_Play_Announcement
CAP_Play_Announcement
Relay
CAP_Prompt_And_Collect_User_Informat ion
CAP_Prompt_And_Col lect_User_Informat ion
CAP_Specialized_Ressource_Report
CAP_Specialized_Ressource_Report
CAP_Prompt_And_Collect_User_Informat ionack
CAP_Prompt_And_Collect_User_Informat ionack
Figure 42c: Procedure CAMEL_CF_CTR (sheet 3)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1183G TS 23.078 version 3.2.0
Procedure in the MSC to handle a Connect To Resourceoperation
Procedure CAMEL_CF_CTR 4(4)
Signals to/from the left areto/from the process MT_GMSC;
signals to/from the right are to/fromthe gsmSSF if not otherwise stated.Await_SRF_Initialisation
Release
Answer Received
Int_DP_O_Disconnect/*legID*/
Int_Disconnect_SRF To SRF
Await_SRF_Disconnection_
Active
Int_SRF_Released
From SRF
Result:=pass
Int_DP_O_Abandon
Int_Disconnect_SRF To SRF
Await_SRF_Disconnection_
Fail
Int_SRF_Released
From SRF
Result:=fail
True False
Figure 42d: Procedure CAMEL_CF_CTR (sheet 4)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1193G TS 23.078 version 3.2.0
Procedure CAMEL_Check_ORLCF_VMSC 1(1)
Note:If CAMEL Capability Handling is not
presented in O-CSI, it is assumed to be “phase 1”. If GMSC supported CAMEL phases are not present in PRN, it is assumed
to be “phase 1”.
Result:=
VMSCCF
O-CSI CAMEL capabilityhandling included in
GMSC supported phase?
GMSC supportedCAMEL phase
is present?
CAMEL capability
handling presentin O-CSI?
O-CSIpresent?
Triggeringcriteria in
O-CSI?
Triggering criteria
satisfied?
Result:=
CAMEL ORLCF
Result:=
ORLCF
CAMEL CapabilityHandling :=
phase 1
GMSC supportedCAMEL phase :=
phase 1
No
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
Figure 43a: Procedure CAMEL_Check_ORLCF_VMSC (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1203G TS 23.078 version 3.2.0
8.6 Handling of mobile calls in the gsmSSFHandling of mobile calls in the gsmSSF may involve the following process and procedures :
- gsmSSF,
- Check_Criteria.
- Handle_AC,
- Handle_ACR,
- Handle_CIR,
- Handle_CIR_leg,
- Complete_FCI_record,
- Complete_all_FCI_records,- Handle_SCI.
The detailed error handling for the process gsmSSF and the associated procedures is specified in GSM 09.78 ([5]).
8.6.1 Information flow for call duration control
The following diagram shows the handling of the different timers that are used in the process gsmSSF and in theprocedures Handle_AC, Handle_ACR, Handle_CIR. Timers Tssf, Tcp, Tsw, Tw and DELTA are defined in the processgsmSSF.
AC(Tcp1)
ANSWER
ACR
AC(Tcp2)
RELEASEACR
RRBCSM
CONNECT
SET UP
ALERT
ANSWER
AC(Tcp3)
RELEASEACR
Tsw
Tcp1
Delta
Tcp2-Delta
Tsw
Tcp3
CSE gsmSSF/MSC MSC / TE
ETC/CTR
ERBCSM
Figure 44: Information flow for call control duration
8.6.2 Behaviour of the gsmSSF in the process gsmSSF
The following paragraphs give details on the behaviour of the gsmSSF in the process gsmSSF.
3GPP
3G TS 23.078 V3.2.0 (1999-11)1213G TS 23.078 version 3.2.0
8.6.2.1 Actions of the gsmSSF on receipt of CAP_Request_Report_BCSM_Event (atthe state Waiting_For_Instructions)
The gsmSSF arms the requested EDP, if the arming rules are fulfilled and returns to state Waiting_For_Instructions.
The gsmSCF may request the monitoring for any one or more Answer, Busy, No Answer, Abandon, Route Select Failureand Disconnect Event of a party in the call.
8.6.2.2 Actions of the gsmSSF on receipt of CAP_Continue (at the stateWaiting_For_Instructions)
An Int_Continue is sent to request the GMSC/MSC to continue call set-up as originally requested.
8.6.2.3 Actions of the gsmSSF on receipt of CAP_Release_Call (at the stateMonitoring)
When a control relationship exists between the gsmSCF and gsmSSF (at least one EDP-R is armed), the gsmSCF mayspontaneously instruct the gsmSSF to release the call at any time using the Release Call IF. The Release Call IF shall notbe sent from the gsmSCF if only monitor relationship exists between the gsmSSF and the gsmSCF.
8.6.2.4 Actions of the gsmSSF on receipt of Int_DP_T_Busy or Int_DP_T_No_Answerincluding the parameter CF (at the state Monitoring)
If the handling of Int_DP_T_Busy or Int_DP_T_No_Answer including the parameter CF leads to the gsmSSF sending aCAP_Event_Report_BCSM to the gsmSCF, the gsmSSF shall include the parameter Call Forwarded as the Event SpecificInformation BCSM.
8.6.3 Procedure Handle_SCI
1) Precondition: before an answer event is detected and no Tsw running:
if 1 set of e-parameters received --> send to the MSC
if 2 sets e-parameters received --> error
if 1 set of e-parameters and Tariff Switch received --> error
if 2 sets of e-parameters and Tariff Switch received --> send 1st/start Tsw/store 2nd
2) Precondition: before an answer event is detected and Tsw running and no e-parameters
if 1 set of e-parameters received --> error, no e-parameters stored
if 2 sets e-parameters received --> send 1st/store 2nd
if 1 set of e-parameters and Tariff Switch received --> error
if 2 sets of e-parameters and Tariff Switch received --> error
3) Precondition: before an answer event is detected and Tsw running and e-parameters stored:
if 1 set of e-parameters received --> error
if 2 sets e-parameters received --> error
if 1 set of e-parameters and Tariff Switch received --> error
if 2 sets of e-parameters and Tariff Switch received --> error
4) Precondition: after an answer event is detected and no Tsw running:
3GPP
3G TS 23.078 V3.2.0 (1999-11)1223G TS 23.078 version 3.2.0
if 1 set of e-parameters received --> send to the MSC
if 2 sets e-parameters received --> error
if 1 set of e-parameters and Tariff Switch received --> start Tsw/store set
if 2 sets of e-parameters and Tariff Switch received --> error
5) Precondition: after an answer event is detected and Tsw running and no e-parameters
if 1 set of e-parameters received --> store e-parameters
if 2 sets e-parameters received --> error
if 1 set of e-parameters and Tariff Switch received --> error
if 2 sets of e-parameters and Tariff Switch received --> error
6) Precondition: after an answer event is detected and Tsw running and e-parameters stored:
if 1 set of e-parameters received --> error
if 2 sets e-parameters received --> error
if 1 set of e-parameters and Tariff Switch received --> error
if 2 sets of e-parameters and Tariff Switch received --> error
NOTE: The MSC shall store the received e-parameters to be sent subsequently to the MS. The MSC shall sendthese e parameters to the MS in a Connect message or in a Facility message.
3GPP
3G TS 23.078 V3.2.0 (1999-11)1233G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 1(25)
Signals to/from the left are to/from the MSC;signals to/from the right areto/from the gsmSCF.
Timers used in the gsmSSF process:
Tssf: Application timer in the ssf.Tcp: Timer for call period. This timer measures the duration of a call period.Tsw: Timer for tariff switch. At the expiration of this timer, a new tariff switch shall be started.Tw: Warning timer. At the expiration of this timer, a warning tone shall be played to the calling party.DELTA: time, measured in the gsmSSF, elapsed between the time an ApplyChargingReport operation is send to the gsmSCF and an ApplyCharging operation is received from the gsmSCF.
Idle
Int_InvokegsmSSF(O-CSI)
Arm DP
The received CSI stateswhether DP Collected_Infoor DP Terminating_Attempt_Authorised shall be armedas TDP.
Int_gsmSSF Invoked
Wait_For__Request
Int_InvokegsmSSF(T-CSI)
Int_O_Exception,Int_T_Exception
Idle
Int_DP_O_Answer,Int_DP_T_Answer,Int_DP_O_Abandon,Int_DP_T_Abandon,Int_DP_Route_Select_Failure,Int_DP_O_No_Answer,Int_DP_T_No_Answer,Int_DP_O_Busy,Int_DP_T_Busy,Int_DP_O_Disconnect,Int_DP_T_Disconnect
Int_Continue
Figure 45a: Process gsmSSF (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1243G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 2(25)
Signals to/from the left are to/from the MSC;signals to/from the right areto/from the gsmSCF.
Wait_For__Request
Int_DP__Terminating__Attempt__Authorized
Set Tssf to defaultnon user interactionTssf timer interval
and restart Tssf
Open ControlRelationship
CAP_InitialDP
ACR sent:=falseAC pending:=falseOutstanding requests = 1Oustanding Call Information Report = 0
Waiting_for__Instructions
Int_DP__Collected__Info
Check_Criteria
Result=pass?
Int_Continue
Idle
Int_T_Exception,Int_O_Exception,Int_DP_T_Abandon,Int_DP_O_Abandon
Yes
No
Figure 45b: Process gsmSSF (sheet 2)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1253G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 3(25)Signals to/from the left are to/from the MSC;signals to/from the right areto/from the gsmSCF.
Waiting_for__Instructions
CAP_Continue
Stop Tssf
Int_Continue
Message was received due to DP of
legID?
Complete_FCI_record(leg2)
DP was dueto call
forwarding?
Handle_CIR_leg (leg1)
Current DP isO_Disconnect orT_Disconnect?
Set Outstanding__Requests =Outstanding__Requests - 1
Outstanding__Requests > 0 ?
Any remainingarmed EDP-Rs?
Any remainingarmed EDP orreport pending?
TerminateControl
Relationship
Complete_all_FCI_records
Idle
Change type ofrelationship
Terminate ControlRelationship and openMonitor Relationship
Monitoring
Set Tssf to last used time interval
and restart Tssf
Waiting_For_
_Instructions
Set Outstanding__Requests =0
Complete_FCI_record(leg1)
Handle_CIR_leg (leg2)
CAP_Connect
Stop Tssf
Int_Connect
Message was received due to DP of
legID?
Complete_FCI_record(leg2)
DP was dueto call
forwarding?
Destination numbermodified?
Handle_CIR_leg (leg1)
DP_O_No_Answer of leg 2DP_T_No_Answer of leg 2DP_O_Busy of leg 2DP_T_Busy of leg 2
DP_Route_Select_Failure of leg 2DP_O_Disconnect of leg 2DP_T_Disconnect of leg 2
No
Yes
No
No
No
Yes
Yes
Yes
No
Yes
DP_O_Disconnect of leg1DP_T_Disconnect of leg1
Else
DP_O_No_Answer of leg 2DP_T_No_Answer of leg 2DP_O_Busy of leg 2DP_T_Busy of leg 2DP_Route_Select_Failure of leg 2
DP_O_Disconnect of leg 2DP_T_Disconnect of leg 2
No
No
Yes
Yes
Else
Figure 45c: Process gsmSSF (sheet 3)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1263G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 4(25)
Signals to/from the left are to/from the MSC;signals to/from the right areto/from the gsmSCF.
Waiting_for__Instructions
CAP_Apply_Charging
Handle_AC
Waiting_For__Instructions
CAP_Reset_Timer
Set Tssf toCAP_Reset_Timer
time interval andrestart Tssf
Timer expiryTssf
Internal
Abort
Int_Error
Complete_all_FCI_records
Idle
Figure 45c: Process gsmSSF (sheet 4)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1273G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 5(25)
Signals to/from the left are to/from the MSC;signals to/from the right areto/from the gsmSCF.
Waiting_for__Instructions
CAP_Request__ReportBCSM__Event
Set Tssf to lastused time intervaland restart Tssf
Arming rulesfulfilled?
Error
UnexpectedData Value
Waiting_For__Instructions
Arm EDP
and/ordisarm EDP
Depending on the Monitoringparameter received for theindicated detection point.For DP O/T Disconnect a DPis only disarmed for the legfor which the event wasreceived.
CAP__Release_Call
AC pending?
CAP_Apply_Charging_Report
Call active=False
Handle_CIR
Complete_all_FCI_records
Stop Tssf
TerminateControl
Relationship
Int_Release Call
Idle
Int_T_Exception,Int_O_Exception
AC pending?
CAP_Apply_Charging_Report
Call active=False
Handle_CIR
Complete_all_FCI_records
TerminateControl
Relationship
Abort
No
Yes
True
False
True
False
Figure 45d: Process gsmSSF (sheet 5)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1283G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 6(25)
Signals to/from the left are to/from the MSC;signals to/from the right areto/from the gsmSCF.
Waiting_For__Instructions
CAP_EstablishTemporaryConnection
Stop Tssf
Int_EstablishTemporaryConnection
Await_Temporary_Connection_
Establishment
Int_Temporary_Connection_Established
AC pending?
Start Tcp
Tw>0
Start Tw
Stored Eparameters?
Send E parameters
Set Tssf to userinteraction timervalue and restart
Tssf
Waiting_For__End_Of_
Temporary_Connection
Int_ETC_Failed
Error ETC failed
Set Tssf to lastused time intervaland restart Tssf
Waiting_For_Instructions
CAP_Cancel_(All)
Disarm allEDPs
Cancel allreports
Yes
Yes
Yes
No
No
No
Figure 45e: Process gsmSSF (sheet 6)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1293G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 7(25)
Signals to/from the left are to/from the MSC;signals to/from the right areto/from the gsmSCF.
Waiting_for__Instructions
CAP_ConnectTo_Resource
Stop Tssf
Int_Connect_To_Resource
Await_Resource_Connection
Figure 45f: Process gsmSSF (sheet 7)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1303G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 8(25)
Signals to/from the left are to/from the MSC;signals to/from the right areto/from the gsmSCF.
Await_Resource_Connection
Int_SRFConnected
AC pending?
Start Tcp
Tw>0
Start Tw
Stored Eparameters?
Send E parameters
Set Tssf to userinteraction timervalue and restart
Tssf
Waiting_For_End_Of_
User_Interaction
Int_CTR_Failed
Set Tssf to lastused time intervaland restart Tssf
Return appropriateerror to thegsmSCF
Waiting_For_Instructions
Yes
Yes
Yes
No
No
Figure 45g: Process gsmSSF (sheet 8)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1313G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 9(25)
Signals to/from the left are to/from the MSC;signals to/from the right areto/from the gsmSCF.
Waiting_for_Instructions,Waiting_for_End_Of_Temporary_Connection,Waiting_for_End_Of_User_Interaction,Await_Temporary_Connection_Establishment
Int_DP_T_
_Disconnect/* legID */
DP armed forleg ID?
DP armedas EDP-R?
Perform implicitdisarming of DPs
CAP_Event__Report_BCSM(Notify & Continue)
Reload andrestart Tssf
Handle_ACRCall active=False
Handle_CIR
Waiting_for_Instructions
Perform implicitdisarming of DPs
Handle_ACRCall active=False
Handle_CIR_leg (legID)
CAP_Event__Report_BCSM(Interrupted)
Set Tssf to defaultnon user interaction
timer value andrestart Tssf
Set Outstanding__Requests =Outstanding_
_Requests + 1
Perform implicitdisarming of DPs
Handle_ACRCall active=False
Handle_CIR
Int_DP_O_
_Disconnect/* legID */
Yes
No
Yes
No
Figure 45h: Process gsmSSF (sheet 9)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1323G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 10(25)
Signals to/from the right areto/from the gsmSCF.
Monitoring
CAP_Request_Report_BCSM_Event
Arming rulesfllfilled?
In state 'Monitoring', only requests to disarm DPs or to send notifications are allowed
Error: UnexpectedData Value
Arm DPand / or
disarm DP
Monitoring
No
Yes
Figure 45i: Process gsmSSF (sheet 10)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1333G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 11(25)
Signals to/from the left are to/from the MSC;signals to/from the right are
to/from the gsmSCF.
Monitoring
Int_DP_O__Disconnect/* legID */
DP armed forleg ID?
DP armedas EDP-R?
Perform implicitdisarming of DPs
CAP_Event__Report_BCSM(Notify & Continue)
Handle_ACRCall active=False
Handle_CIR
Complete_all_FCI_records
Terminaterelationship
Int_Continue
Idle
Perform implicitdisarming of DPs
Handle_ACRCall active=False
Handle_CIR_leg (ledID)
CAP_Event__Report_BCSM(Interrupted)
Set Tssf to defaultnon user interaction
timer value andrestart Tssf
Set Outstanding__Requests =Outstanding_
_Requests + 1
Waiting_for_Instructions
Perform implicitdisarming of DPs
Int_DP_T__Disconnect/* legID */
Int_DP_O_Abandon
Int_DP_T_Abandon
Yes
No
Yes
No
Figure 45j: Process gsmSSF (sheet 11)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1343G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 12(25)
Signals to/from the left are to/from the MSC;signals to/from the right areto/from the gsmSCF.
Int_Continue
Terminate
Relationship
Stop Tssf
Waiting_for_Instructions,Waiting_for_End_Of_Temporary_Connection,Waiting_for_End_Of_User_Interaction,Await_Temporary_Connection_Establishment
Int_DP_O__Abandon
Perform implicitdisarming of DPs
DP armed asEDP?
CAP_Event_
_Report_BCSM(Notify & Continue)
Handle_ACRCall active=False
Handle_CIR
Waiting_For_Instructions
Int_DP_T__Abandon
Yes
No
Figure 45k: Process gsmSSF (sheet 12)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1353G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 13(25)
Signals to/from the left are to/from the MSC;signals to/from the right areto/from the gsmSCF.
Waiting_for_End__Of_Temporary_
Connection
CAP_Disconnect_Forward__Connection/* legID */
Handle_ACRCall active=False
Int_Disconnect_
Forward_Connection
Set Tssf to lastused time intervaland restart Tssf
Waiting_For__Instructions
Int_TC_Released
Handle_ACRCall active=False
CAP_Apply_Charging
Handle_AC
Waiting_for_End__Of_Temporary_
_Connection
CAP_Reset_Timer
Set Tssf tolast used timeinterval and
restart Tssf
Tssf expired Internal
Abort
Int_Disconnect_Forward_Connection
TC_Release_Pending
Int_TC_Released
Int_Error
Complete_all_
FCI_records
Idle
Figure 45l: Process gsmSSF (sheet 13)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1363G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 14(25)
Signals to/from the left are to/from the MSC;signals to/from the right are
to/from the gsmSCF.
Waiting_for_End_Of_Temporary_ConnectionWaiting_for_End_Of_User_Interaction
Tw expired Internal
Int_Apply_Warning_Tone
This provoques the MSCto play a tone to the partyfor whom the BCSM is operating
-
Tsw expired Internal
Storede parameters?
Send_e_Parameters
This provoques the MSCto send e parameters tothe calling party
Store curentvalue of Tcp
Tcp expired Internal
Release?
Handle_ACRCall active=True
Set Tssf to lastused time interval and restart Tssf
CAP_Apply_Charging_Report
Call active=False
Int_Disconnect_Forward_Connection
Handle_CIR
Complete_all_FCI_records
Int_Release
Idle
Yes
No
No
Yes
Figure 45m: Process gsmSSF (sheet 14)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1373G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 15(25)
Signals to/from the left are to/from the MSC;signals to/from the right areto/from the gsmSCF.
Monitoring
Tw expired Internal
Int_Apply_Warning_Tone
This provoques the MSCto play a tone to the partyfor whom the BCSM is operating
Monitoring
Tsw expired Internal
Storede parameters?
Send_e_Parameters
This provoques the MSCto send e parameters tothe calling party
Store curentvalue of Tcp
Tcp expired Internal
Release?
CAP_Apply_Charging_Report
Call active=False
Handle_CIR
Complete_all_FCI_records
Int_Release
Idle
Any EDP or report
outstanding?
Handle_ACR Call active=True
Complete_all_FCI_records
Yes
No
Yes
No
Yes
No
Figure 45n: Process gsmSSF (sheet 15)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1383G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 16(25)
Signals to/from the left are to/from the MSC;signals to/from the right areto/from the gsmSCF.
Waiting_for_End__Of_User__Interaction
CAP_Play__Announcement
Relay the operationto the SRF
To SRF
Set Tssf to last
used time intervaland restart Tssf
Waiting_for_End__Of_User__Interaction
CAP_Prompt_&
_Collect_User__Information
CAP_Cancel__(Invoke_ID)
CAP_Reset_Timer
Set Tssf toCAP_Reset_Timertime interval and
restart Tssf
Figure 45o: Process gsmSSF (sheet 16)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1393G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 17(25)
Signals to/from the left are to/from the MSC;signals to/from the right areto/from the gsmSCF.
Waiting_for_End__Of_User__Interaction
CAP_Apply_Charging
Handle_AC
IWaiting_For_End_Of_User_Interaction
CAP_Disconnect_Forward_
_Connection/* legID */
Handle_ACRCall active=False
Int_Disconnect_Forward_Connection
Set Tssf to default
non user interactiontime interval and
restart Tssf
Int_SRF_Released
Handle_ACRCall active=False
Set Tssf to default
non user interactiontime interval and
restart Tssf
Waiting_For__Instructions
Figure 45o: Process gsmSSF (sheet 17)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1403G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 18(25)
Signals to/from the left are to/fromthe process Generic_SRF;
signals to/from the right areto/from the gsmSCF unless otherwise stated.Waiting_for_End_
_Of_User__Interaction
CAP_Cancelled__error
Relay the operation/result/error to the gsmSCF
Waiting_for_End__Of_User__Interaction
CAP_Cancel__Failed_error
CAP_Prompt_&_Collect_User__Information__Result
From SRF
CAP_Specialised_Resource_Report
From SRF
Timer expiryTss f
Abort
Int_Disconnect_Forward_Connection
SRF_Release_Pending
Int_SRF_Released
Int_Error
Complete_all_FCI_records
Idle
Internal
Figure 45p: Process gsmSSF (sheet 18)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1413G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 19(25)Signals to/from the left are to/from the MSC;signals to/from the right are
to/from the gsmSCF.
Complete_all_
FCI_records
Monitoring
Int_DP_O_Answer,Int_DP_T_Answer
AC pending
Start Tcp
Tw>0
Start Tw
Stored e parameters?
Send
e parameters
This provoques the MSCto send e parameters tothe calling party
DP armed?
Perform implicitdisarming of DPs
TerminateRelationship
Control orMonitor
Relationship
Int_Continue
Idle
Any remaining armedEDPs oroutstanding report?
Int_Continue
Monitoring
DP armedas EDP-R?CAP_Event_
_Report_BCSM(Notify & Continue)
Perform implicitdisarming of DPs
For DP O/T Disconnect the DPis only disarmed for the leg
for which the event wasreceived.
CAP_Event__Report_BCSM(Interrupted)
Perform implicitdisarming of DPs
For DP O/T Disconnect the DP
is only disarmed for the legfor which the event wasreceived.
Set Outstanding_
_Requests = 1
Set Tssf to defaultnon user interactionTssf timer value and
restart Tssf
Waiting_For__Instructions
CAP_Cancel_(All)
Disarm allEDPs
Cancel allreports
True
Yes
Yes
No
No
Yes
Yes
No
Yes
No
No
False
Figure 45q: Process gsmSSF (sheet 19)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1423G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 20(25)Signals to/from the left are to/from the MSC;signals to/from the right are
to/from the gsmSCF.
Monitoring
Int_DP_O_No_Answer,Int_DP_T_No_Answer,Int_DP_O_Busy,Int_DP_T_Busy,Int_DP_Route_Select_Failure
EDP type?
Handle_ACRCall active=False
Stop Delta
Handle_CIR_leg (leg2)
CAP_Event_
_Report_BCSM(Interrupted)
Perform implicitdisarming of DPs
For DP O/T Disconnect the DPis only disarmed for the leg
for which the event wasreceived.
Set Outstanding__Requests = 1
Set Tssf to default
non user interactionTssf timer value and
restart Tssf
Waiting_For__Instructions
Handle_ACR Call active=False
Stop Delta
Call forwardingpending?
Handle_CIR_leg (leg2)
Complete_FCI_
record (leg2)
Perform implicit
disarming of DPs
Any remaining armedEDPs oroutstanding report?
Int_Continue
Monitoring
TerminateRelationship
Control orMonitorRelationship
Int_Continue
Complete_FCI_
record (leg1)
Idle
Handle_CIR
CAP_Event_
_Report_BCSM(Notify & Continue)
Handle_ACRCall active=False
Stop Delta
Call forwardingpending?
Handle_CIR_
leg (leg2)
Complete_FCI_record (leg2)
Perform implicitdisarming of DPs
For DP O/T Disconnect the DPis only disarmed for the leg
for which the event wasreceived.
Handle_CIR
EDP-RNot armed
Yes
Yes
No
No
EDP-N
Yes
No
Figure 45r: Process gsmSSF (sheet 20)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1433G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 21(25)
Signals to/from the left are to/from the MSC;signals to/from the right areto/from the gsmSCF.
Monitoring
CAP__ReleaseCall
Handling of CAP_Release_Callis only specified in a controlrelationship.The gsmSCF shall not send a CAP_Release_Call in a monitor relationship
AC pending
CAP_Apply_Charging_Report
Call active=False
Handle_CIR
Complete_all_FCI_records
TerminateControl
Relationship
Int_Release_Call
Idle
Int_O_Exception,Int_T_Exception
AC pending
CAP_Apply_Charging_Report
Call active=False
Handle_CIR
Complete_all_FCI_records
TerminateRelationship
Control orMonitorRelationship
Abort
Idle
CAP_Apply_Charging
Handle_AC
Monitoring
True
False
True
False
Figure 45s: Process gsmSSF (sheet 21)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1443G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 22(25)
Signals to/from the right areto/from the gsmSCF.
Waiting_For_Instructions,Waiting_For_End_Of_Temporary_Connection,Waiting_For_End_Of_User_Interaction
CAP_Furnish_Charging_Information
Set Tssf to lastused time intervaland restart Tssf
Non completedCAMEL logical call recordexists for this legID?
Overwrite CAMELlogical call record
with FCI data
-
Create CAMEL logicalcall record
Write FCI datain CAMEL logical
call record
Yes
No
Figure 45t: Process gsmSSF (sheet 22)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1453G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 23(25)
Signals to/from the right areto/from the gsmSCF.
Monitoring
CAP_Furnish_Charging_Information
Non completedCAMEL logical call recordexists for this legID?
Overwrite CAMELlogical call record
with FCI data
Monitoring
Create CAMEL logicalcall record
Write FCI datain CAMEL logical
call record
Yes
No
Figure 45t: Process gsmSSF (sheet 23)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1463G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 24(25)
Signals to/from the right areto/from the gsmSCF.
Monitoring,Wait_For_Instructions,Waiting_For_End_Of_User_Intercation,Waiting_Fot_End_Of_Temporary_Connection
CAP_Send_Charging_Information
Handle_SCI See section 8.6.3
-
Figure 45t: Process gsmSSF (sheet 24)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1473G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process gsmSSF 25(25)
Signals to/from the right areto/from the gsmSCF.
Waiting_For_Instructions
CAP_Call_Information_Request
Set Tssf to lastused time intervaland restart Tssf
store request
Oustanding Call Information Report:=Oustanding Call Information Report +1
Waiting_For_Instructions
Figure 45t: Process gsmSSF (sheet 25)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1483G TS 23.078 version 3.2.0
Procedure to checkthe criteria in the gsmSSF
Procedure Check_Criteria 1(1)
Destination numbertriggering criterion
exists?
enabling criterion met?
inhibiting criterionmet?
Basic servicecriterion exists?
basic servicecriterion met?
Forwarding triggeringcriterion exists?
enabling criterion met?
inhibiting criterionmet?
Result:=pass
Result:=fail
Yes
No
No
Yes
Yes
Yes
No
No Yes
Yes
No
No
No
Yes
Yes
No
Figure 46a: Procedure Check_Criteria (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1493G TS 23.078 version 3.2.0
This procedure shows the handl ing inthe gsmSSF for the opera t ion CAPApply Charg ing
Procedure Handle_AC 1(1)
Set Tss f to las tused t ime intervaland restar t Tssf
AC pending?
Tar i f f swi tchprovided?
Start Tsw
Answer received?
Stop del tam e a s u r e m e n t
Tcp:=Tcp-delta
Release indicatorpresent?
Tone to beplayed?
Tw:=0
1
Tw:=
Tcp-Warn ing t ime
1
A n s w e rreceived?
Start Tcp
Tw>0
S t a r t T w
AC pending:=true
True
False
Yes
Yes
No
Yes
No
No
No
Yes
Yes
No
No
Yes
Figure 47a: Procedure Handle_AC (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1503G TS 23.078 version 3.2.0
This procedure is only called at theend of connection to an outgoing leg,a temporary connection or a connectionto a SRF when the call can be continued
Procedure Handle_ACR 1(1)
Tsw running?
Stop Tsw
e-valuesstored?
discard e-values
AC pending=true?
Stop TcpIf running
Stop TwIf running
Start Delta
CAP_Apply_Charging_Report
AC pending:=false
Value of Call Active inACR is defined in the callingprocess gsmSSF.
Yes
Yes
Yes
No
No
No
Figure 48a: Procedure Handle_ACR (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1513G TS 23.078 version 3.2.0
Procedure in the gsmSSF to
handle Call Information Report.
Procedure Handle_CIR 1(1)
Signals to/from the right are
to / f rom the gsmSCF.
Hand le_CIR_
leg (leg1)
Hand le_CIR_
leg (leg2)
Figure 49a: Procedure Handle_CIR (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1523G TS 23.078 version 3.2.0
Procedure in the gsmSSF tohandle Call Information Reportfo r the spec i f ied leg .LegID is received in procedure call
Procedure Handle_CIR_leg 1(1)
Signals to/from the right are
to / f rom the gsmSCF.
Outsanding CallInformat ion Report>0?
Call Information Report pending for
t h i s l eg ID?
Outsanding Call Information Report:=
Outsanding Call Information Report -1
CAP_Call_Information_Report
Yes
Yes
No
N o
Figure 50a: Procedure Handle_CIR_leg (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1533G TS 23.078 version 3.2.0
Procedure in the gsmSSF towrite Furnish Charging Informationdata for the speci f ied leg.LegID is received in procedure call.
Procedure Complete_FCI_record 1(1)
Complete CAMELlogical call record
Non completed LogicalCAMEL call record existsfor th is legID
Yes
No
Figure 51a: Procedure Complete_FCI_record (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1543G TS 23.078 version 3.2.0
Procedure in the gsmSSF towrite Furnish Charging Informationdata to CDR for both LegIDs.
Procedure Complete_all_FCI_records 1(1)
Complete_FCI_
record (leg2)
Comple te_FCI_
record (leg1)
Figure 52a: Procedure Complete_all_FCI_records (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1553G TS 23.078 version 3.2.0
8.7 Assisting caseAssisting case involves the following processes :
- CAMEL_Assisting_MSC,
- Assisting_gsmSSF.
The detailed error handling for these 2 processes is specified in GSM 09.78 ([5]).
3GPP
3G TS 23.078 V3.2.0 (1999-11)1563G TS 23.078 version 3.2.0
Process in the MSC to handle an assist request
Process CAMEL_Assisting_MSC 1(3)
Signals to/from the left are to/from the process CAMEL_OCH_ETC, CAMEL_TC_ETC or CAMEL_CF_ECT;signals to/from the right are to/fromthe assisting_gsmSSF;
Int_Release_Assisting_gsmSSF
Idle
Initial Address
Int_Assist__Required
Wait_for_assisting__gsm_SSF_invoked
Int_assisting__gsmSSF_invoked
Wait_For__Assisting_
_Event
Release
Idle
Figure 53a: Process CAMEL_Assisting_MSC (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1573G TS 23.078 version 3.2.0
Process in the MSC to handle an assist request
Process CAMEL_Assisting_MSC 2(3)
Signals to/from the left are to/from the process CAMEL_OCH_ETC, CAMEL_TC_ETC or CAMEL_CF_ECT;signals to/from the right are to/fromthe assisting_gsmSSF;if not otherwise stated.
Wait_For_Assisting_
Event
Int_Connect_To_Resource
Int_Invoke__SRF to SRF
Await_SRF__Initialisation
Int_assisting__gsmSSF__released
Release
Idle
Release
Int_release__assisting_gsmSSF
Releasing_assisting__gsmSSF
Int_assisting_gsmSSF_released
Figure 53b: Process CAMEL_Assisting_MSC (sheet 2)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1583G TS 23.078 version 3.2.0
Process in the MSC to handle an assist request
Process CAMEL_Assisting_MSC 3(3)
Signals to/from the left are to/from the process CAMEL_OCH_ETC, CAMEL_TC_ETC or CAMEL_CF_ECT;signals to/from the right are to/fromthe assisting_gsmSSF;if not otherwise stated.
Await_SRF__Initialisation
Int_SRF__Connected from SRF
Connect SRF to theCall
Send_ACM_If_Required
Procedure specifiedin GSM 03.18
Send_Answer_If_Required
Procedure specifiedin GSM 03.18
Int_SRF_Connected
Wait_For_Assisting_
Event
Int_SRF__Connection__Failure
from SRF
Int_CTR_Failed
Release
Int_Disconnect_SRFTo SRF
Await_gsmSRF__disconnection
Int_SRF_ReleasedFrom SRF
Int_release__assisting_gsmSSF
Releasing_assisting__gsmSSF
Int_assisting_gsmSSF_released
Idle
Int_assisting__gsmSSF__released
Release
Figure 53c: Process CAMEL_Assisting_MSC (sheet 3)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1593G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process assisting_gsmSSF 1(6)
Signals to/from the left are to/fromthe process CAMEL_Assisting_MSC;signals to/from the right areto/from the gsmSCF,unless otherwise indicated.
Idle
Int_Assist__Required
Int_assisting__gsmSSF__Invoked
Set Tssf to defaultnon user interaction
Tssf timer intervaand restart Tssfl
Open ControlRelationship
CAP_Assist__Request__Instructions
Waiting_for__Instructions
Figure 54a: Process Assisting_gsmSSF (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1603G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process assisting_gsmSSF 2(6)
Signals to/from the left are to/fromthe process CAMEL_Assisting_MSC;signals to/from the right areto/from the gsmSCF,unless otherwise indicated. Waiting_for_
_Instructions
Tssf expires
Abort
Int_assisting__gsmSSF__released
Idle
CAP_Reset_Timer
Set Tssf toCAP_Reset_Timer
time interval andresart Tssf
Waiting_For_Instructions
CAP_ConnectToResource
Int_Connect_To_Resource
Await_Resource_Connection
Int_CTR_FailedFrom processCAMEL_Assisting_MSC
Return appropriateerror to SCF
Set Tssf to normalnon user interaction
timer value andresart Tssf
Int_SRFConnected
From processCAMEL_Assisting_MSC
Set Tssf to userinteraction timer
value and restart Tssf
Waiting_For_End_Of_
User_Interaction
Internal
Figure 54b: Process Assisting_gsmSSF (sheet 2)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1613G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process assisting_gsmSSF 3(6)
Signals to/from the left are to/fromthe process CAMEL_Assisting_MSC;signals to/from the right areto/from the gsmSCF,unless otherwise indicated.
Waiting_for_End__Of_User_
_Interaction
CAP_Disconnect_Forward__Connection/* legID */
Set Tssf to defaultuser interaction
Tssf timer intervaand resrt Tssfl
Int_Disconnect__SRF
to SRF
Waiting_For__Instructions
Int_SRF_ReleasedFrom SRF CAP_Reset_Timer
Set Tssf toCAP_Reset_Timer
time interval andrestart Tssf
Waiting_for_End__Of_User_
_Interaction
CAP_Play__Announcement
Relay the operationto the SRF
To SRF
Set Tssf to lastused time intervaland restart Tssf
Waiting_for_End__Of_User__Interaction
CAP_Prompt_&_Collect_User__Information
CAP_Cancel__(Invoke_ID)
Figure 54c: Process Assisting_gsmSSF (sheet 3)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1623G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process assisting_gsmSSF 4(6)
Signals to/from the left are to/fromthe SRF;signals to/from the right areto/from the gsmSCF. Waiting_for_End_
_Of_User__Interaction
CAP_Cancelled__error
Relay the operation/result/error to the gsmSCF
Waiting_for_End__Of_User__Interaction
CAP_Cancel__Failed_error
CAP_Prompt_&_Collect_User__Information_Result
CAP_Specialised__Resource_Report
Figure 54d: Process Assisting_gsmSSF (sheet 4)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1633G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process assisting_gsmSSF 5(6)
Signals to/from the left are to/fromthe process CAMEL_Assisting_MSC;signals to/from the right areto/from the SRF,unless otherwise indicated. Waiting_for_End_
_Of_User__Interaction
Tssf expires
Abort To gsmSCF
Int_disconnect__SRF
Wait_For_gsm_SRF_Release
Int_SRF_Released
Int_assisting__gsmSSF__released
Idle
Internal
Figure 54e: Process Assisting_gsmSSF (sheet 5)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1643G TS 23.078 version 3.2.0
Invocation of gsmSSF in MO,MT or CF call case.
Process assisting_gsmSSF 6(6)
Signals to/from the right areto/from the process CAMEL_Assisting_MSC.
Waiting_For_InstructionsWaiting_For_End_Of_User_Interaction
Int_release__assisting__gsmSSF
TerminateControl
Relationship
Int_assisting__gsmSSF__released
Idle
Figure 54f: Process Assisting_gsmSSF (sheet 6)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1653G TS 23.078 version 3.2.0
8.8 Procedure CAMEL_Provide_Subscriber_Info
8.8.1 MS reachable
A Provide_Subscriber_Info Request is sent to VLR and the HLR waits in state Wait_For_Information.
If the VLR returns a Provide_Subscriber_Info ack, the HLR uses the returned information to set the Subscriber Info to bereturned to the gsmSCF. As a network option, the HLR may use the returned Cell Id or Location Area to derive thelocation number and/or Geographical Info. The mapping from cell ID and location area to location number is network-specific and outside the scope of the GSM standard.
NOTE: The handling in the VLR of Provide_Subscriber_Info Request is defined in GSM 03.18 [3].
8.8.2 MS not reachable
8.8.2.1 Location Information requested
If VLR number is available in the HLR, then the Location Information is set to this parameter only.
If location information is not available in the HLR, no location information is set.
8.8.2.2 Subscriber State requested
The Subscriber State is set to "Network determined not reachable".
8.8.3 Actions at state Wait_For_Information
The following actions are possible in state Wait_For_Information depending on the result of theProvide_Subscriber_Info Request sent to VLR.
8.8.3.1 Provide_Subscriber_Info ack
The Location Information or/and the Subscriber State are set to the received information.
8.8.3.2 Provide_Subscriber_Info Negative Response
If location information was requested the VLR number is provided as location information. If the subscriber state wasrequested the subscriber state is set to “not provided from VLR”.
3GPP
3G TS 23.078 V3.2.0 (1999-11)1663G TS 23.078 version 3.2.0
P r o c e d u r e i n t h e H L Rf o r R e t r i e v a l o f L o c a t i o n i n f o r m a t i o na n d S u b s c r i b e r S t a t u s
P r o c e d u r e C A M E L _ P r o v i d e _ S u b s c r i b e r _ I n f o 1 ( 1 )
S i g n a l s t o / f r o m t h e l e f t a r e t o / f r o mt h e V L R .
M S r e a c h a b l e ?
Prov ide_Subsc r i be r__Info
W a i t _ f o r _
_ I n f o r m a t i o n
Prov ide_Subsc r i be r_
_ In fo ack
P r o v i d e _ S u b s c r i b e r _
I n f o r m a t i o nn e g a t i v e r e s p o n s e
L o c . i n f o .r e q u e s t e d ?
L o c . I n f o .a v a i l a b l e ?
L o c _ I n f o = l a t e s t
stored loc. in fo.S t a t u s = " u n r e l i a b l e "
S u b s c r . s t a t u sr e q u e s t e d ?
S u b s c r i b e rs ta tus=
" N e t w o r k d e t e r m i n e dn o t r e a c h a b l e "
L o c _ I n f o ="unava i l ab le "
Yes
Y e s
Y e s
Y e s
N o
N o
N o
N o
Figure 55a: Procedure CAMEL_Provide_Subscriber_Info (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1673G TS 23.078 version 3.2.0
8.9 Any Time InterrogationHandling of Any Time Interrogation involves the following process :
- CAMEL_ATI_HLR.
If an OSS needs the Subscriber State and/or the Location Information, the gsmSCF initiates a transaction to the HLR bysending a Any_Time_Interrogation Request. Support for this procedure is a network operator option.
3GPP
3G TS 23.078 V3.2.0 (1999-11)1683G TS 23.078 version 3.2.0
Process in the HLRreceiving an Any TimeInterrogation request fromgsmSCF.
Process CAMEL_ATI_HLR 1(1)
Signals to/from the left are to/fromthe gsmSCF.
Idle
Any_Time_Interrogation
ATIaccepted?
M Sknown?
Provide_Subscriber_Info
/*input data=requested info*/
Any_Time_Interrogationresult
Idle
Set UE=Unknown Subscriber
Any TimeInterrogationError
Idle
S e t U E ="ATI Not Allowed"
Yes
Yes
No
No
Figure 56a: Process CAMEL_ATI_HLR (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1693G TS 23.078 version 3.2.0
8.10 Handling of USSD to/from gsmSCFThe functional model of USSD in an HLR that supports CAMEL is shown in figure 57. The phase 2 USSD handler isdefined in GSM 03.90 ([8)]. Phase 1 USSD messages may be relayed from the HLR to the gsmSCF. CAMEL introduces a"CAMEL USSD application" which is invoked by the USSD handler. The CAMEL USSD application behaviour isspecified in this section.
HLR
gsmSCF
MSC MS
Visiting Network
Home Network
VLR
MAP
MAP
CAMEL USSDapplication
USSD Handler
Figure 57: Handling of USSD to and from a CAMEL subscriber
8.10.1 MS Initiated USSD
For the behaviour of the USSD handler in HLR when receiving a MS initiated USSD see GSM 03.90.
When the USSD handler has determined that the service code present in the received USSD does not indicate that anUSSD application in the HLR shall be invoked it shall route the USSD to the USSD application specific for CAMEL, i.e.the CAMEL USSD application.
The procedure at the CAMEL USSD application at the HLR is implementation dependent. The following text describes arecommended procedure.
The CAMEL USSD application shall check the U-CSI data assigned to the specific subscriber. If the service code ispresent in the U-CSI the USSD is routed to the gsmSCF given by the gsmSCF address stored against the service code inthe U-CSI.
If the service code is not present in the U-CSI (or the subscriber does not have U-CSI defined) then the CAMEL USSDapplication shall check the UG-CSI data assigned to the HLR. If the service code is present in the UG-CSI then the USSDis routed to the gsmSCF given by the gsmSCF address stored against the service code in the UG-CSI.
If the service code is not present in U-CSI or UG-CSI an error (unknown application) is returned to the USSD handler.
8.10.2 gsmSCF Initiated USSD
The HLR may at any time receive a USSD operation from the gsmSCF. If the subscriber can be contacted, the HLR shallset up a transaction to the VLR and forward the operation unchanged. Any further information exchange between thegsmSCF and MSC shall be transparent to the VLR and the HLR. When one transaction is released, the HLR shall releasethe other. If an error is received from the MSC, the VLR shall release the transaction to the HLR and the HLR shall releasethe transaction to the gsmSCF.
3GPP
3G TS 23.078 V3.2.0 (1999-11)1703G TS 23.078 version 3.2.0
8.10.3 Content of the USSD General CAMEL Service Information (UG-CSI)
The service information specified in this subclause is for information only.
This subclause defines the contents of the USSD General CAMEL Service Information (UG-CSI). The allocation of theUG-CSI is independent from a particular subscriber.
The UG-CSI consists of a list of pairs of the following two parameters.
8.10.3.1 Service Code
Service code for a specific application in a gsmSCF which interacts with the user by USSD.
8.10.3.2 gsmSCF address
Address to be used to access the gsmSCF for a particular a particular service code. The address shall be an E.164 numberto be used for routeing.
8.11 Handling of Supplementary Service Invocation NotificationAt the invocation of any of the services ECT, CD and MPTY the VLR checks whether the criteria for sending anotification are fulfilled, i.e. whether the subscriber is provisioned with the SS-CSI and the particular invokedsupplementary service is marked in the SS-CSI. If this is the case a notification is sent to the gsmSCF given by thegsmSCF address contained in the SS-CSI. The processing of the particular SS invocation is not suspended. If thenotification criteria are not fulfilled the processing of the particular supplementary service continues unchanged and nonotification is sent.
The sending of the notification is independent of call related CAMEL processing, i.e. processing indicated by O/T-CSI.
On invocation of ECT, the VLR shall include the SS-CSI in the Invoke ECT response message (see Process MAF027 inGSM 03.91) to the MSC if applicable for ECT.
On invocation of MPTY, the VLR shall include the SS-CSI in the Process MPTY message (see Process MPTY_MAF026in GSM 03.84) to the MSC if applicable for MPTY.
On invocation of CD, the VLR shall include the SS-CSI in the Send Info For Incoming Call ack message to the MSC ifapplicable to CD.
8.12 CAMEL specific handling of location updating and datarestoration
When requesting location updating or data restoration the VLR shall indicate to the HLR which CAMEL phases itsupports.
The CAMEL phase 2 HLR shall then send to the VLR CAMEL subscription data for one of the CAMEL phasessupported by the VLR or, if some different handling is required, data for substitute handling.
8.13 Processing of Non-Call Related EventsCAMEL does not modify any of the standardized procedures for non-call related events including:
- call independent supplementary service procedures;
- transfer of SMS messages;
3GPP
3G TS 23.078 V3.2.0 (1999-11)1713G TS 23.078 version 3.2.0
- mobility management procedures.
8.14 Cross phase compatibilityTo avoid a case by case fallback between the gsmSSF and the gsmSCF, the gsmSSF shall use the CAP phasecorresponding to the CAMEL phase negotiated on the HLR-VLR interface when it opens a dialogue with the gsmSCF.The HLR-VLR negotiation of CAMEL phase is per subscriber.
8.15 Handling of North American Carrier Information The following procedures apply normally only when the HPLMN of the CAMEL subscriber and either the VPLMN (for amobile originated or forwarded call) or the IPLMN (for a mobile terminated or forwarded call) are both North American.As an option, the procedures may also be applied for a mobile originated or forwarded call at a North American VPLMNwhen the HPLMN of the CAMEL subscriber is not North American. A gsmSCF may then provide the gsmSSF with anyof the following North American (NA) carrier related information items.
- NA Carrier Information,
- NA Originating Line Information,
- NA Charge NumberA gsmSSF shall use the received information items both to select any long distance carrierneeded for the call and to provide certain information needed by this carrier. Any required information items notreceived shall be defaulted to those that would normally apply to the call in the absence of an interaction with agsmSCF.
If any NA information item received from the gsmSCF is found to be invalid, the gsmSSF may either, as an operatoroption, release the call or behave as if the invalid information item had not been sent.
If the carrier specified in the NA Carrier Information parameter is not supported in the VPLMN or IPLMN, the gsmSSFmay either, as an operator option, release the call or substitute for the unsupported carrier a preferred carrier of theVPLMN or IPLMN.
Support of the NA Originating Line Information and NA Charge Number parameters is an operator option in a VPLMNbased on roaming agreements with the operators of other PLMNs, A gsmSSF may ignore these items when received fromcertain or all gsmSCFs located in other PLMNs and replace them with the corresponding default items for an MO, MF orMT call.
3GPP
3G TS 23.078 V3.2.0 (1999-11)1723G TS 23.078 version 3.2.0
9 Description of information flowsThis clause contains the detailed description of the information flows used by CAMEL.
Each Information Element, IE is marked as Mandatory, Conditional, Optional or Not applicable for each different trafficcase, Mobile Originating call (MO), Mobile Forwarded call (MF) and Mobile Terminating call (MT). This categorisation isa functional classification, i.e., stage 2 information and not a stage 3 classification to be used for the ASN.1 syntax of theprotocol.
The following principles apply for the handling of the IEs by the receiving entity :
- The gsmSSF shall functionally support all IEs which can be sent to it.
- The gsmSCF may silently discard any IE which it does not functionally support
- The gsmSRF shall return an error if it does not functionally support a IE which it receives.
- The HLR may silently discard any IE which it does not functionally support.
Details of errors and exceptions to these rules are specified in are specified in GSM 09.78.
9.1 gsmSSF to gsmSCF information flows
9.1.1 Activity Test ack
9.1.1.1 Description
This IF is the response to the Activity Test.
9.1.1.2 Information Elements
This IF contains no information elements.
9.1.2 Apply Charging Report
9.1.2.1 Description
This IF is used by the gsmSSF to report to the gsmSCF the information requested in the Apply Charging IF.
9.1.2.2 Information Elements
Information element name MO MF MT Description
Call Result M M M This IE contains the charging information to be provided by thegsmSSF.
M Mandatory (The IE shall always be sent)
Call Result contains the following information:
Information element name MO MF MT Description
Time Duration Charging Result M M M This IE is a list defined in the next table.
3GPP
3G TS 23.078 V3.2.0 (1999-11)1733G TS 23.078 version 3.2.0
M Mandatory (The IE shall always be sent)
Time Duration Charging Result contains the following information:
Information element name MO MF MT Description
Time Information M M M This IE is a choice between Time if No Tariff Switch and Time ifTariff Switch.
Party To Charge M M M This IE is received in the related ApplyCharging operation tocorrelate the result to the request. This IE shall be a copy of thecorresponding IE received in the Apply Charging operation.
Call Active M M M This IE indicates whether the call is active or not.
M Mandatory (The IE shall always be sent)
C Conditional (The IE shall be sent, if available)
Time Information contains one of the following information:
Information element name MO MF MT Description
Time If No Tariff Switch C C C This IE will be present if no tariff switch has occurred since thedetection of Answer for the connection to the Called Party, theTemporary Connection, or the SRF connection, otherwise it willbe absent.
Time If Tariff Switch C C C This IE will be present if a tariff switch has occurred since thedetection of Answer for the connection to the Called Party, theTemporary Connection, or the SRF connection, otherwise it willbe absent.
C Conditional (The IE shall be sent, if available)
9.1.3 Call Information Report
9.1.3.1 Description
This IF is used to send specific call information for a single call to the gsmSCF as requested from the gsmSCF in aprevious Call Information Request.
9.1.3.2 Information Elements
Information element name MO MF MT Description
Requested Information List M M M This IE specifies a list of Requested information Values which arerequested.
Leg ID M M M This IE indicates the party in the call for which information shallbe collected. When absent, it indicates the ‘outgoing’ leg createdwith Connect or Continue.
M Mandatory (The IE shall always be sent)
9.1.4 Event Report BCSM
9.1.4.1 Description
This IF is used to notify the gsmSCF of a call-related event (i.e., BCSM events as answer and disconnect) previouslyrequested by the gsmSCF in a Request Report BCSM Event IF.
3GPP
3G TS 23.078 V3.2.0 (1999-11)1743G TS 23.078 version 3.2.0
9.1.4.2 Information Elements
The following information elements are required:
Information element name MO MF MT Description
Event type BCSM M M M This IE specifies the type of event that is reported.
Event Specific Information BCSM C C C This IE indicates the call related information specific to theevent.
Leg ID M M M This IE indicates the party in the call for which the event isreported.
Misc Call Info M M M This IE indicates the DP type.
M Mandatory (The IE shall always be sent)
C Conditional (The IE shall be sent, if available)
9.1.5 Initial DP
9.1.5.1 Description
This IF is generated by the gsmSSF when a trigger is detected at a DP in the BCSM, to request instructions from thegsmSCF.
9.1.5.2 Information Elements
The following information elements are required:
Information element name MO MF MT Description
Additional Calling PartyNumber
- C C The calling party number provided by the access signalling systemof the calling user.
Bearer Capability M C C This IE indicates the type of the bearer capability connection to theuser.
Called Party Number - M M This IE contains the number used to identify the called party in theforward direction.
Called Party BCD Number M - - This IE contains the number used to identify the called party in theforward direction. The number contained in this IE shall be identicalto the number received over the access network. It may e.g. includeservice selection information, such as ∗ and # digits, or carrierselection information dialled by the subscriber.
Calling Party Number M C C This IE carries the calling party number to identify the calling partyor the origin of the call.
Calling Partys Category M C C Indicates the type of calling party (e.g., operator, pay phone,ordinary subscriber).
(continued)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1753G TS 23.078 version 3.2.0
(concluded)
Information element name MO MF MT Description
Call Reference Number M M M This IE may be used by the gsmSCF for inclusion in a networkoptional gsmSCF call record. It has to be coupled with the identityof the MSC which allocated it in order to define unambiguously theidentity of the call.
For MO calls, the call reference number is set by the serving VMSCand included in the MO call record.
For MT calls, the call reference number is set by the GMSC andincluded in the RCF call record in the GMSC and in the MT callrecord in the terminating MSC.
For CF calls, the call reference number is set by the GMSC andincluded in the CF record in the forwarding MSC.
Event Type BCSM M M M This IE indicates the armed BCSM DP event (i.e., Collected_Infoand Terminating_Attempt_Authorised), resulting in the Initial DPIF.
Ext-Basic Service Code C C C This IE indicates the type of basic service i.e., teleservice or bearerservice.
High Layer Compatibility C C C This IE indicates the type of the high layer compatibility, which willbe used to determine the ISDN-teleservice of a connected ISDNterminal.
IMSI M M M This IE identifies the mobile subscriber.
IP SSP Capabilities C C C This IE indicates which SRF resources are supported within thegsmSSF and are available. If this IE is absent, this indicates that nogsmSRF is attached and available.
Location Information M - C This IE is described in the next table.
Location Number M C C For mobile originated calls this IE represents the location of thecalling party. For all other call scenarios this IE contains thelocation number received in incoming ISUP signalling.
MSC Address M M M For MO calls, the MSC Address carries the international E.164address of the serving VMSC.
For MT calls, the MSC Address Address carries the internationalE.164 address of the GMSC.
For CF calls, the MSC Address carries the international E.164address of the forwarding MSC.
GMSC Address - M - For CF calls, the GMSC Address carries the international E.164address of the GMSC.
(continued)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1763G TS 23.078 version 3.2.0
(concluded)
Information element name MO MF MT Description
NA Carrier Information C C C The content of this IE is described in the next table.
The IE may normally be sent when the VPLMN and the HPLMN ofthe subscriber are both North American.
For MO calls, this IE shall contain any carrier that was dialed by thecalling subscriber. If no carrier was dialed, the IE shall contain thecalling subscriber’s subscribed carrier.
For MT calls, the IE shall contain the carrier subscribed to by thecalled subscriber.For MF calls, the IE shall contain the carriersubscribed to by the forwarding subscriber.
Original Called Party ID - C C This IE carries the dialled digits if the call has met call forwardingon the route to the gsmSSF.
Redirecting Party ID - M C This IE indicates the directory number the call was redirected from.
Redirection Information - M C It contains forwarding related information, such as redirectioncounter.
Service Key M M M This IE identifies for the gsmSCF the requested set of one or moreCAMEL services. It is used to address the correct application/SLPwithin the gsmSCF.
Subscriber State - - C This IE indicates the status of the MS. The states are:
- CAMELBusy: The MS is engaged on a transaction for a mobileoriginating or terminated circuit-switched call.
- NetworkDeterminedNotReachable: The network can determinefrom its internal data that the MS is not reachable.
- AssumedIdle: The state of the MS is neither "CAMELBusy"nor "NetworkDeterminedNotReachable".
- Not provided from VLR.
Time And Timezone M M M This IE contains the time that the gsmSSF was triggered, and thetime zone the gsmSSF resides in.
GSM Forwarding Pending - - C This parameter indicates that a forwarded-to-number was receivedand the call will be forwarded due to GSM supplementary servicecall forwarding in the GMSC.
M Mandatory (The IE shall always be sent)
C Conditional (The IE shall be sent, if available)
- Not applicable
Location Information contains the following information:
3GPP
3G TS 23.078 V3.2.0 (1999-11)1773G TS 23.078 version 3.2.0
Information element name MO MF MT Description
Location Number - - C See GSM 03.18 [3].
CellIdOrLAI M - C See GSM 03.18 [3].
Geographical Information C - C See GSM 03.18 [3].
Age Of Location Information M - C See GSM 03.18 [3].
VLR number M - C See GSM 03.18 [3].
M Mandatory (The IE shall always be sent)
C Conditional (The IE shall be sent, if available)
- Not applicable
NA Carrier Information contains the following information:
Information element name MO MF MT Description
NA Carrier Identification Code M M M This IE uniquely identifies a North American long distance carrier.
NA Carrier SelectionInformation
M M M This IE indicates the way the carrier was selected e.g.:– dialled– subscribed
M Mandatory (The IE shall always be sent)
9.2 gsmSCF to gsmSSF information flows
9.2.1 Activity Test
9.2.1.1 Description
This IF is used to check for the continued existence of a relationship between the gsmSCF and gsmSSF. If therelationship is still in existence, then the gsmSSF will respond. If no reply is received, then the gsmSCF will assume thatthe gsmSSF has failed in some way and will take the appropriate action.
9.2.1.2 Information Elements
This IF contains no information elements.
9.2.2 Apply Charging
9.2.2.1 Description
This IF is used for interacting from the gsmSCF with the gsmSSF charging mechanisms to control the call duration.
3GPP
3G TS 23.078 V3.2.0 (1999-11)1783G TS 23.078 version 3.2.0
9.2.2.2 Information Elements
Information element name MO MF MT Description
ACh Billing ChargingCharacteristics
M M M This IE specifies the charging related information to be providedby the gsmSSF and the conditions on which this information hasto be provided back to the gsmSCF.
Party To Charge M M M This IE shall be reflected in the corresponding IE of the ApplyCharging Report operation. This IE has no effect on the chargingprocedures in the MSC.
M Mandatory (The IE shall always be sent)
ACh Billing Charging Characteristics contains the following information:
Information element name MO MF MT Description
Time Duration Charging M M M This IE is described in the next table.
M Mandatory (The IE shall always be sent)
Time Duration Charging contains the following information:
Information element name MO MF MT Description
Max Call Period Duration M M M This IE indicates the maximum call period duration timer.
Tariff Switch Interval O O O This IE indicates the tariff switch time until the next tariffswitch applies.
Release If Duration Exceeded O O O This IE indicates that the call shall be released when theMax call Period Duration expires, with a warning tone ifthe Play Tone IE is present. The cause used in therelease message shall be "normal unspecified".
Default is to continue the call.
M Mandatory (The IE shall always be sent)
O Optional (Service logic dependent)
Release If Duration Exceeded contains the following IE :
Information element name MO MF MT Description
Play Tone O - O This IE is set if a tone has to be played to theparty for whom the BCSM is operating. Ifpresent, this IE indicates that 30 secondsbefore the Max Call Period Duration timerexpires,
a triple tone of 900 Hz (200 milliseconds tone,200 milliseconds pause) shall be played.
This IE shall be absent if the call is not to bereleased.
O Optional (Service logic dependant)
- Not applicable
3GPP
3G TS 23.078 V3.2.0 (1999-11)1793G TS 23.078 version 3.2.0
9.2.3 Call Information Request
9.2.3.1 Description
This IF is used to request the gsmSSF to record specific information about a single call and report it to the gsmSCF (witha CallInformationReport)
9.2.3.2 Information Elements
Information element name MO MF MT Description
Requested Information TypeList
M M M This IE specifies a list of specific items of information which arerequested.
Leg ID M M M This IE indicates the party in the call for which information shallbe collected. When absent, it indicates the ‘outgoing’ leg createdwith Connect or Continue.
M Mandatory (The IE shall always be sent)
Requested Information Type List contains the following information:
Information element name MO MF MT Description
Call Attempt Elapsed Time O O O This IE indicates that the Call Attempt Elapsed Time is requestedin the Call Information Report.
Call Attempt Elapsed Time is the duration between the end of theCAMEL processing initiating call setup (Connect or Continue IF)and the received answer indication from the called party side. Forthe Calling Party, the value of Call Attempt Elapsed Time in theCall Information Report shall be set to 0.
Call Stop Time O O O This parameter indicates that the Call Stop Time is requested inthe Call Information Report.
Call Connected Elapsed Time is the time stamp when theconnection is released.
Call Connected Elapsed Time O O O This parameter indicates that the Call Connected Elapsed Time isrequested in the Call Information Report.Call Connected Elapsed Time is the duration between the receivedanswer indication from the called party side and the release of theconnection.
For a Calling Party, it indicates the duration between the sendingof InitialDP and the release of that party.
Release Cause O O O This parameter indicates the Release Cause is requested in theCall Information Report.Release Cause is the release cause for the call.
O Optional (Service logic dependent)
9.2.4 Cancel
9.2.4.1 Description
This IF is used by the gsmSCF to request the gsmSSF to cancel all EDPs and reports.
3GPP
3G TS 23.078 V3.2.0 (1999-11)1803G TS 23.078 version 3.2.0
9.2.4.2 Information Elements
The following information elements are used:
Information element name MO MF MT Description
All Requests M M M This IE indicates that all active requests for EventReportBCSM,ApplyChargingReport and CallInformationReport shall becancelled.
M Mandatory (The IE shall always be sent)
9.2.5 Connect
9.2.5.1 Description
This IF is used to request the gsmSSF to perform the call processing actions to route a call to a specific destination. Todo so, the gsmSSF may use destination information from the calling party and existing call set-up information dependingon the information provided by the gsmSCF.
9.2.5.2 Information Elements
The following information elements are required:
Information element name MO MF MT Description
Alerting Pattern - - O This parameter indicates the kind of Alerting Pattern to beapplied.
Calling Partys Category O O O This IE indicates the type of calling party (e.g., operator, payphone, ordinary subscriber).
Destination Routing Address M M M This IE contains the called party number towards which thecall is to be routed.
Generic Number O O O This IE contains the generic number. Its used to convey theadditional calling party number, which e.g. could be used tomodify the calling line ID presented to the called user.
NA Carrier Information O O O This IE is described in the next table.
NA Originating Line Information O O O This IE identifies the type of number in the NA ChargeNumber (e.g. subscriber versus PLMN operator number).
NA Charge Number O O O This IE identifies the chargeable number for the usage of aNorth American carrier.
O-CSI Applicable - - O This IE indicates that the O-CSI, if present shall be applied onthe outgoing leg.
Original Called Party ID O O O This IE carries the dialled digits if the call has met callforwarding on route to the gsmSSF or is forwarded by thegsmSCF.
Redirecting Party ID O O O This IE indicates the directory number the call was redirectedfrom.
Redirection Information O O O This IE contains forwarding related information, such asredirecting counter.
Suppression Of Announcements - - O This IE indicates that announcements or tones generated as aresult of unsuccessful call setup shall be suppressed.
O Optional (Service logic dependent)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1813G TS 23.078 version 3.2.0
- Not applicable
NA Carrier Information contains the following information:
Information element name MO MF MT Description
NA Carrier Identification Code M M M This IE uniquely identifies a North American long distance carrier.
NA Carrier SelectionInformation
M M M This IE indicates the way the carrier was selected e.g.:– dialled– subscribed
M Mandatory (The IE shall always be sent)
9.2.6 Connect To Resource
9.2.6.1 Description
This IF is used to connect a call from the gsmSSF to a gsmSRF.
9.2.6.2 Information Elements
The following information elements are required:
Information element name MO MF MT Description
Service Interaction IndicatorsTwo
O O O This parameter indicates whether or not a bothway throughconnection is required between the Calling party and the gsmSRF.The handling when this IE is not present is defined in EN 301 070-1 ([7]).
Resource Address O O O This IE indicates the physical location of the gsmSRF.
O Optional (Service logic dependent)
Resource Address contains the following information:
Information element name MO MF MT Description
IP Routing Address O O O This IE indicates the routeing address to set up a connectiontowards the gsmSRF.
None O O O This parameter indicates that the call party is to be connected to apredefined gsmSRF.
O Optional (Service logic dependent)
9.2.7 Continue
9.2.7.1 Description
This information flow requests the gsmSSF to proceed with call processing at the DP at which it previously suspendedcall processing to await gsmSCF instructions. The gsmSSF completes DP processing, and continues basic callprocessing (i.e., proceeds to the next point in call in the BCSM) without substituting new data from the gsmSCF.
9.2.7.2 Information Elements
This IF contains no information elements.
3GPP
3G TS 23.078 V3.2.0 (1999-11)1823G TS 23.078 version 3.2.0
9.2.8 Disconnect Forward Connection
9.2.8.1 Description
This IF is used :
− to disconnect a connection with a gsmSRF previously established with a Connect To Resource IF,
− to disconnect an initiating gsmSSF from an assisting gsmSSF and its associated gsmSRF. The IF is send to theinitiating gsmSSF
9.2.8.2 Information Elements
This IF contains no information elements.
9.2.9 Establish Temporary Connection
9.2.9.1 Description
This IF is used to create a connection between an initiating gsmSSF and an assisting gsmSSF as a part of the assistprocedure. It can also be used to create a connection between a gsmSSF and a gsmSRF.
9.2.9.2 Information Elements
The following information elements are required:
Information element name MO MF MT Description
Assisting SSP IP RoutingAddress
M M M This parameter indicates the destination address of the gsmSRF orassisting gsmSSF for the assist procedure. As a network operatoroption, the Assisting SSP IP Routing Address may containembedded within it, a "Correlation ID" and " Scf ID", but only if"Correlation ID" and "Scf ID" are not specified separately.
Correlation ID O O O This parameter is used for :
- the correlation of dialogues from the initiating gsmSSF->gsmSCF with dialogues from gsmSRF -> gsmSCF
- the correlation of dialogues from the initiating gsmSSF->gsmSCF with dialogues from assisting gsmSSF -> gsmSCF.
NA Carrier Information O O O This IE is described in the next table.
NA Originating LineInformation
O O O This IE identifies the type of number in the NA Charge Number(e.g. subscriber versus PLMN operator number).
NA Charge Number O O O This IE identifies the chargeable number for the usage of a NorthAmerican carrier.
Scf ID O O O This parameter indicates the gsmSCF identifier
Service Interaction IndicatorsTwo
O O O This parameter indicates whether or not a bothway throughconnection is required between the Calling party and thegsmSRF. The handling when this IE is not present is defined inEN 301 070-1 ([7]).
M Mandatory (The IE shall always be sent)
O Optional (Service logic dependent)
NA Carrier Information contains the following information:
3GPP
3G TS 23.078 V3.2.0 (1999-11)1833G TS 23.078 version 3.2.0
Information element name MO MF MT Description
NA Carrier Identification Code M M M This IE uniquely identifies a North American long distance carrier.
NA Carrier SelectionInformation
M M M This IE indicates the way the carrier was selected e.g.:– dialled– subscribed
M Mandatory (The IE shall always be sent)
9.2.10 Furnish Charging Information
This IF is used to request the gsmSSF to include call related information in the CAMEL specific logical call record.
9.2.10.1 Information Elements
The following information elements are required:
Information element name MO MF MT Description
FCI Billing ChargingCharacteristics
M M M This IE is described in the next table.
M Mandatory (The IE shall always be sent)
FCI Billing Charging Characteristics contains the following information:
Information element name MO MF MT Description
FCIBCCCAMEL Sequence 1 M M M This IE is described in the next table.
M Mandatory (The IE shall always be sent)
FCIBCCCAMEL Sequence 1 contains the following information:
Information element name MO MF MT Description
Free Format Data M M M This IE is a free format data to be inserted in the CAMEL logicalcall record.
Party To Charge M M M This IE indicates the party for whom a CAMEL logical call recordwill be created.
M Mandatory (The IE shall always be sent)
9.2.11 Release Call
9.2.11.1 Description
This IF is used to tear down by the gsmSCF an existing call at any phase of the call for all parties involved in the call.
9.2.11.2 Information Elements
The following information elements are required:
Information element name MO MF MT Description
Cause M M M A number giving an indication to the gsmSSF about the reason ofreleasing this specific call. This may be used by MSC/GMSC forgenerating specific tones to the different parties in the call or to fillin the "cause" in the release message.
M Mandatory (The IE shall always be sent)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1843G TS 23.078 version 3.2.0
9.2.12 Request Report BCSM Event
9.2.12.1 Description
This IF is used to request the gsmSSF to monitor for a call-related event, then send a notification back to the gsmSCFwhen the event is detected (see Event Report BCSM).
9.2.12.2 Information Elements
The following information elements are used:
Information element name MO MF MT Description
BCSM Event M M M This IE specifies the event or events of which a report isrequested.
M Mandatory (The IE shall always be sent)
BCSM Event contains the following information:
Information element name MO MF MT Description
Event type M M M This IE specifies the type of event of which a report is requested.
Leg ID C C C This IE indicates the party in the call for which the event shall bereported.
Monitor Mode M M M This IE indicates how the event shall be reported.
DP Specific Criteria O O O This IE is described in the next table.
M Mandatory (The IE shall always be sent)
C Conditional
O Optional (Service logic dependent)
DP Specific Criteria is defined as:
Information element name MO MF MT Description
Application Timer O O O This IE carries additional timer duration information (timer valuesfor No Answer event) required for arming No_Answer EDPs in thegsmSSF. The TNRy timer (value defined between 10s and 40s)shall be shorter than the network no answer timer.
O Optional (Service logic dependent)
9.2.13 Reset Timer
9.2.13.1 Description
This IF is used to refresh a timer.
9.2.13.2 Information Elements
The following information elements are required:
3GPP
3G TS 23.078 V3.2.0 (1999-11)1853G TS 23.078 version 3.2.0
Information element name MO MF MT Description
Timer Value M M M This IE specifies the value to which the timer Tssf shall be set.
Timer ID O O O This IE has a default value indicating the Tssf value.
M Mandatory (The IE shall always be sent)
O Optional (Service logic dependent)
9.2.14 Send Charging Information
9.2.14.1 Description
This IF is used to send e-parameters from the gsmSCF to the gsmSSF. If charge advice information is received from thegsmSCF, it shall replace the charge advice information which would be generated by the MSC and inhibit any furthergeneration of CAI by the MSC. Further processing of the charge advice information by the MSC shall be in accordancewith the GSM Advice of Charge Supplementary Service.
NOTE: If charge advice information is received from the gsmSCF after charge information has been generated bythe MSC and sent to the MS, the behaviour of the service may be unpredictable or incorrect ; the servicedesigner should therefore ensure that the first set of charge advice information is sent to the gsmSSFbefore charge information is sent to the to the MS.
9.2.14.2 Information Elements
The following information elements are only used for the MO case :
Information element name MO Description
SCI Billing ChargingCharacteristics
M This IE defines the Advice Of Charge related information to beprovided to the Mobile Station
Leg ID M This IE indicates where the charging information shall be sent.
M Mandatory (The IE shall always be sent)
SCI Billing Charging Characteristics is defined as:
Information element name MO Description
AOC After Answer C This IE is sent after an Answer from event has been detected fromthe called party, the current connected SRF or the temporaryconnection.
AOC Before Answer C This IE is sent before an Answer event has been detected from thecalled party, the current connected SRF or the temporaryconnection.
C Conditional (only one of these IEs may be sent)
AOC Before Answer is defined as:
Information element name MO Description
AOC Initial M This IE contains CAI elements as defined in GSM 02.24.
AOC Subsequent O See definition in the next table.
M Mandatory (The IE shall always be sent)
O Optional (Service logic dependent)
AOCSubsequent is defined as:
3GPP
3G TS 23.078 V3.2.0 (1999-11)1863G TS 23.078 version 3.2.0
Information element name MO Description
CAI Elements M This IE contains CAI elements as defined in GSM 02.24
Tariff Switch Interval O This IE indicates the tariff switch time until the next tariff switchapplies.
M Mandatory (The IE shall always be sent)
O Optional (Service logic dependent)
AOCAfterAnswer is defined as:
Information element name MO Description
CAI Elements M This IE contains CAI elements as defined in GSM 02.24
Tariff Switch Interval O This IE indicates the tariff switch time until the next tariff switchapplies.
M Mandatory (The IE shall always be sent)
9.3 Optional (Service logic dependent) gsmSCF to gsmSRFinformation flows
9.3.1 Cancel
9.3.1.1 Description
This IF is used by the gsmSCF to request the gsmSRF to cancel a correlated previous operation.
9.3.1.2 Information Elements
The following information elements are used:
Information element name MO MF MT Description
Invoke ID M M M This IE specifies the operation to be cancelled.
M Mandatory (The IE shall always be sent)
9.3.2 Play Announcement
9.3.2.1 Description
This IF is used for inband interaction.
9.3.2.2 Information Elements
The following information elements are required:
3GPP
3G TS 23.078 V3.2.0 (1999-11)1873G TS 23.078 version 3.2.0
Information element name MO MF MT Description
Information To Send M M M This IE indicates an announcement or a tone to be sent to theend user by the gsmSRF.
Disconnect From IP Forbidden M M M This IE indicates whether or not the gsmSRF may bedisconnected from the user when all information has beensent.
Request AnnouncementComplete
M M M This IE indicates whether or not a SpecializedResourceReportshall be sent to the gsmSCF when all information has beensent.
M Mandatory (The IE shall always be sent)
O Optional (Service logic dependent)
Information To Send contains the following information:
Information element name MO MF MT Description
Inband Info O O O This IE indicates the inband information to be sent.
Tone O O O This IE indicates the tone to be sent. The mapping from the codepoints of this IE to tones is a matter for agreement between thegsmSCF operator and the gsmSRF operator.
O Optional (Service logic dependent)
Inband Info contains the following information:
Information element name MO MF MT Description
Message ID M M M This IE is described in the next table.
Number Of Repetitions M M M This IE indicates the maximum number of times the message shallbe sent to the end-user.
Duration O O O This IE indicates the maximum duration time in seconds that themessage shall be played/repeated. Zero indicates endlessrepetition.
Interval O O O This IE indicates the time interval in seconds between tworepetitions.
M Mandatory (The IE shall always be sent)
O Optional (Service logic dependent)
Message ID contains the following information:
Information element name MO MF MT Description
Elementary Message ID O O O This IE indicates a single announcement
Text O O O This IE indicates a text to be sent. The text shall be transformed toinband information (speech) by the gsmSRF.
Elementary Message IDs O O O This IE indicates a sequence of announcements
Variable Message O O O This IE indicates an announcement with one or more variableparts.
O Optional (Service logic dependent)
Tone contains the following information:
3GPP
3G TS 23.078 V3.2.0 (1999-11)1883G TS 23.078 version 3.2.0
Information element name MO MF MT Description
Tone ID M M M This IE indicates the tone to be sent.
Duration O O O This IE indicates the maximum duration time in seconds that themessage shall be played/repeated. Zero indicates endlessrepetition.
M Mandatory (The IE shall always be sent)
O Optional (Service logic dependent)
9.3.3 Prompt And Collect User Information (received information)
9.3.3.1 Description
This IF is used to interact with a call party in order to collect information.
9.3.3.2 Information Elements
The following information elements are required:
Information element name MO MF MT Description
Collected Info M M M This IE is described in the next table.
Information To Send O O O This IE indicates an announcement or a tone to be sent to theend user by the gsmSRF.
Disconnect From IP Forbidden O O O This IE indicates whether the gsmSRF should bedisconnected from the user when all information has beensent.
O Optional (Service logic dependent)
Collected Info contains the following information:
Information element name MO MF MT Description
Collected Digits M M M This IE is described in the next table.
O Optional (Service logic dependent)
Collected Digits contains the following information:
3GPP
3G TS 23.078 V3.2.0 (1999-11)1893G TS 23.078 version 3.2.0
Information element name MO MF MT Description
Minimum Number Of Digits M M M This IE indicates the minimum number of valid digits to becollected.
Maximum Number Of Digits O O O This IE specifies the maximum number of valid digits to becollected
End Of Reply Digit O O O This IE indicates the digit(s) used to signal the end of input.
Cancel Digit O O O If this IE is present, the cancel digit can be entered by the user torequest a possible retry
Start Digit O O O If this IE is present, the start digit(s) indicates the start of thevalid digits to be collected.
First Digit Time Out O O O If this IE is present, the first digit shall be received before theexpiration of the first digit timer expiration
Inter Digit Time Out O O O If this IE is present, any subsequent valid or invalid digit shall bereceived by the gsmSRF before the inter digit timer expires.
Error Treatment O O O This IE indicates what specific action shall be taken by thegsmSRF in the event of error conditions occurring.
Interruptable Ann Ind O O O If this IE is set to TRUE (default value) the announcement isinterrupted after the first valid or invalid digit received by thegsmSRF. If this IE is present and explicitly set to FALSE, theannouncement will not be interrupted after the first digit isreceived by the gsmSRF
Voice Information O O O This IE is optional, where the default value is specified beingFALSE. If the VoiceInformation IE is set to FALSE, all valid orinvalid digits are entered by DTMF If this IE is present andexplicitly set to TRUE, calling user is required to provide all validor invalid information by speech
Voice Back O O O This IE is optional, where the default value is specified beingFALSE. If the VoiceBack IE is set to FALSE, no voice backinformation is given by the gsmSRF If this IE is present andexplicitly set to TRUE, the valid input digits received by thegsmSRF will be announced back to the calling user immediatelyafter the end of input is received
O Optional (Service logic dependent)
InformationToSend is defined in subclause 9.3.3.
9.3.4 Activity Test
9.3.4.1 Description
This IF is used to check for the continued existence of a relationship between the gsmSCF and gsmSRF. If therelationship is still in existence, then the gsmSRF will respond. If no reply is received, then the gsmSCF will assume thatthe gsmSRF has failed in some way and will take the appropriate action.
9.3.4.2 Information Elements
This IF contains no information elements.
3GPP
3G TS 23.078 V3.2.0 (1999-11)1903G TS 23.078 version 3.2.0
9.4 gsmSRF to gsmSCF information flows
9.4.1 Assist Request Instructions
9.4.1.1 Description
This IF is sent to the gsmSCF by a gsmSSF which is acting as the assisting gsmSSF or by a gsmSRF
9.4.1.2 Information Elements
The following information elements are required:
Information element name MO MF MT Description
CorrelationID M M M This IE is used to associate the AssistRequestInstructions IFfrom an assisting gsmSSF or by a gsmSRF with the InitialDPfrom the initiating gsmSSF.
IP SSP Capabilities M M M This IE indicates which SRF resources are attached, availableand supported within the MSC where the gsmSSF resides orthe IP in which the gsmSRF resides.
M Mandatory (The IE shall always be sent)
9.4.2 Prompt And Collect User Information ack (received information)
9.4.2.1 Description
This IF is used by the gsmSRF to indicate the result a Prompt And Collect User Information IF.
9.4.2.2 Information Elements
The following information elements are required:
Information element name MO MF MT Description
Digits Response C C C This IE indicates the digit sequence received from the end user
C Conditional (The IE shall be sent, if available)
9.4.3 Specialized Resource Report
9.4.3.1 Description
This IF is used to response to a PlayAnnouncement IF when the announcement complete indication is set.
9.4.3.2 Information Elements
This IF contains no information elements.
9.4.4 Activity Test ack
9.4.4.1 Description
This IF is the response to the Activity Test.
3GPP
3G TS 23.078 V3.2.0 (1999-11)1913G TS 23.078 version 3.2.0
9.4.4.2 Information Elements
This IF contains no information elements.
9.5 gsmSCF to Assisting SSF information flows
9.5.1 Cancel
9.5.1.1 Description
This IF is described in section 9.3.
9.5.2 Connect To Resource
9.5.2.1 Description
This IF is described in section 9.2.
9.5.3 Play Announcement
9.5.3.1 Description
This IF is described in section 9.3..
9.5.4 Prompt And Collect User Information
9.5.4.1 Description
This IF is described in section 9.3.
9.5.5 Reset Timer
9.5.5.1 Description
This IF is described in section 9.2.
9.5.6 Activity Test
9.5.6.1 Description
This IF is used to check for the continued existence of a relationship between the gsmSCF and assistSSF. If therelationship is still in existence, then the assistSSF will respond. If no reply is received, then the gsmSCF will assume thatthe assistSSF has failed in some way and will take the appropriate action.
9.5.6.2 Information Elements
This IF contains no information elements.
3GPP
3G TS 23.078 V3.2.0 (1999-11)1923G TS 23.078 version 3.2.0
9.6 Assisting SSF to gsmSCF information flows
9.6.1 Assist Request Instructions
9.6.1.1 Description
This IF is defined in subclause 9.4.
9.6.2 Prompt And Collect User Information ack (received information)
9.6.2.1 Description
This IF is described in section 9.4.
9.6.3 Specialized Resource Report
9.6.3.1 Description
This IF is described in section 9.4.
9.6.4 Activity Test ack
9.6.4.1 Description
This IF is the response to the Activity Test.
9.6.4.2 Information Elements
This IF contains no information elements.
9.7 gsmSCF to HLR information flows
9.7.1 Any Time Interrogation Request
9.7.1.1 Description
This IF is used to request information (subscriber state and location) from the HLR at any time.
9.7.1.2 Information Elements
The following information elements are required:
3GPP
3G TS 23.078 V3.2.0 (1999-11)1933G TS 23.078 version 3.2.0
Information element name Required Description
gsmSCF Address M This IE indicates the address of the interrogating gsmSCF.
Requested Info M This IE indicates the type of subscriber information being requested:
- subscriber location
- subscriber state
Subscriber Identity M This IE identifies the subscriber for which the information is requested.The identity can be one of:
- IMSI
- MSISDN
M Mandatory (The IE shall always be sent)
9.7.2 Unstructured SS Request
9.7.2.1 Description
This interface is used for the gsmSCF to request data from the MS via the HLR.
9.7.2.2 Information Elements
The following information elements are required:
Information element name Required Description
USSD String M This IE contains the string that will be sent to the MS.
Data Coding Scheme M This IE indicates the characteristics of the USSD string
IMSI C This IE identifies the subscriber for which the information is requested
Alerting Pattern O This IE indicates an alerting pattern to be sent to the MS.
M Mandatory (The IE shall always be sent)
C Conditional (This IE shall be sent if this IF is the first IF in a USSD dialogue)
O Optional (Service Logic dependent)
9.7.3 Unstructured SS Notify
9.7.3.1 Description
This interface is used for the gsmSCF to send data to the MS via the HLR.
9.7.3.2 Information Elements
The following information elements are required:
3GPP
3G TS 23.078 V3.2.0 (1999-11)1943G TS 23.078 version 3.2.0
Information element name Required Description
USSD String M This IE contains the string that will be sent to the MS.
Data Coding Scheme M This IE indicates the characteristics of the USSD string
IMSI C This IE identifies the subscriber for which the information is requested.
Alerting Pattern O This IE indicates an alerting pattern to be sent to the MS.
M Mandatory (The IE shall always be sent)
C Conditional (This IE shall be sent if this IF is the first IF in a USSD dialogue)
O Optional (Service Logic dependent)
9.7.4 Process Unstructured SS Data ack
9.7.4.1 Description
This interface is used for the gsmSCF to send the response to the MS via the HLR for the MS initiated operation.
9.7.4.2 Information Elements
The following information element is required:
Information element name Required Description
SS User Data C This IE contains the string that will be sent to the MS.
C Conditional (The IE shall be sent, if requested and available)
9.7.5 Process Unstructured SS Request ack
9.7.5.1 Description
This interface is used for the gsmSCF to send the response to the MS via the HLR for the MS initiated operation.
9.7.5.2 Information Elements
The following information elements are required:
Information element name Required Description
USSD String C This IE contains the string that will be sent to the MS.
Data Coding Scheme C This IE indicates the characteristics of the USSD string
C Conditional (the presence of the IE depends on the application. Both IEs shall be sent.)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1953G TS 23.078 version 3.2.0
9.8 HLR to gsmSCF information flows
9.8.1 Any Time Interrogation ack
9.8.1.1 Description
This IF is used by the HLR to provide the requested information to the gsmSCF.
9.8.1.2 Information Elements
The following information elements are required:
Information element name Required Description
Location Information C This IE indicates the location of the served subscriber.
Subscriber State C This IE indicates the status of the MS. The possible values of the IEare:
- CAMELBusy: The VLR has indicated that the MS is engagedon a transaction for a mobile originating or terminated circuit-switched call.
- NetworkDeterminedNotReachable: The VLR has indicated thatthe network can determine from its internal data that the MS is notreachable.
- AssumedIdle: The VLR has indicated that the state of the MS isneither "CAMELBusy" nor "NetworkDeterminedNotReachable".
- NotProvidedFromVLR: The VLR did not provide anyinformation on subscriber state even though it was requested.
C Conditional (The IE shall be sent, if requested and available)
Location Information contains the following information:
Information element name Required Description
Location Number C See GSM 03.18 [3].
CellIdOrLAI C See GSM 03.18 [3].
Geographical Information C See GSM 03.18 [3].
Age Of Location Information C See GSM 03.18 [3].
VLR number C See GSM 03.18 [3].
C Conditional (The IE shall be sent, if available)
9.8.2 Unstructured SS Request ack
9.8.2.1 Description
This interface is used for the MS to via the HLR send the response to the gsmSCF for the gsmSCF initiated operation.
9.8.2.2 Information Elements
The following information elements are required:
3GPP
3G TS 23.078 V3.2.0 (1999-11)1963G TS 23.078 version 3.2.0
Information element name Required Description
USSD String C This IE contains the string that will be sent to the gsmSCF.
Data Coding Scheme C This IE indicates the characteristics of the USSD string
C Conditional (The presence of the IE depends on the application. Both IEs shall be sent.)
9.8.3 Unstructured SS Notify ack
This IE contains no information element.
9.8.3.1 Description
This interface is used for the MS to via the HLR acknowledge to the gsmSCF that the notification was received.
9.8.4 Process Unstructured SS Data
9.8.4.1 Description
This interface is used for the gsmSCF to request data from the MS via the HLR.
9.8.4.2 Information Elements
The following information elements are required:
Information element name Required Description
SS User Data M This IE contains the string that will be sent to the MS.
M Mandatory (The IE shall always be sent)
9.8.5 Process Unstructured SS Request
9.8.5.1 Description
This interface is used for the MS to request data from the gsmSCF via the HLR.
9.8.5.2 Information Elements
The following information elements are required:
Information element name Required Description
USSD String M This IE contains the string that will be sent to the gsmSCF, includingthe Service Code.
Data Coding Scheme M This IE indicates the characteristics of the USSD string
IMSI M This IE identifies the subscriber.
MSISDN O This IE contains the basic MSISDN of the subscriber who hasrequested the USSD operation. This IE is used as an operator option.
Originating Entity Number M This IE identifies the functional entity initiating the information flow.In this case, this shall be the address of the HLR.
M Mandatory (The IE shall always be sent)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1973G TS 23.078 version 3.2.0
O Optional (Operator option)
9.8.6 Begin Subscriber Activity
9.8.6.1 Description
This Information Flow is used by the HLR to start subscriber activity towards the gsmSCF for USSD purposes.
9.8.6.2 Information Elements
The following information elements are required:
Information element name Required Description
IMSI M This IE identifies the subscriber.
Originating Entity Number M This IE identifies the functional entity initiating the subscriber activity.In this case, this shall be the address of the HLR.
M Mandatory (The IE shall always be sent)
9.9 HLR to VLR information flows
9.9.1 Delete Subscriber Data
9.9.1.1 Description
This IF is specified in GSM 09.02 [4] and is used by the HLR to delete subscriber data in the VLR.
9.9.1.2 Information Elements
The Delete Subscriber Data contains the following CAMEL specific IE:
Information element name Required Description
CAMEL Subscription InfoWithdraw
C This IE identifies that all CSIs shall be deleted from the subscriber datain VLR.
C Conditional (The IE shall be sent when deletion is requested)
9.9.2 Insert Subscriber Data
9.9.2.1 Description
This IF is specified in GSM 09.02 [4] and used by the HLR to insert subscriber data in the VLR.
9.9.2.2 Information Elements
Insert Subscriber Data contains the following CAMEL specific IE:
3GPP
3G TS 23.078 V3.2.0 (1999-11)1983G TS 23.078 version 3.2.0
Information element name Required Description
O-CSI C This IE identifies the subscriber as having originating CAMELservices.
SS-CSI C This IE identifies the subscriber as having supplementary serviceinvocation notification services. It contains the Notification Criteriaand gsmSCFAddress.
C Conditional (The IE shall be sent, if required)
O-CSI contains the following information:
Information element name Required Description
gsmSCF Address M This IE is described in section 6.1
Service Key M This IE is described in section 6.1.
Default Call Handling M This IE is described in section 6.1.
TDP List M This IE is described in section 6.1.
DP Criteria O This IE is described in section 6.1.
CAMEL Capability Handling C This IE is described in section 6.1. If this IE is absent, this indicatesthat CAMEL phase 1 is asked.
M Mandatory
C Conditional
O Optional (service logic dependant)
9.9.3 Provide Subscriber Info
9.9.3.1 Description
This IF is used by the HLR to request information (subscriber state and location) from the VLR at any time.
9.9.3.2 Information Elements
Provide Subscriber Info contains the following CAMEL specific IE:
Information element name Required Description
Requested Info M This IE indicates the type of subscriber information to the gsmSCF.
- subscriber location
- subscriber state
Subscriber Identity M This IE identifies the subscriber for which the information isrequested. The identity can be:
- IMSI: The IMSI shall be accompanied by a LMSI if one wasprovided by the VLR.
M Mandatory (The IE shall always be sent)
3GPP
3G TS 23.078 V3.2.0 (1999-11)1993G TS 23.078 version 3.2.0
9.9.4 Provide Roaming Number
9.9.4.1 Description
This IF is specified in GSM 03.18 [3] and used by the HLR to request a roaming number from the VLR.
9.9.4.2 Information Elements
Provide Roaming Number contains the following CAMEL specific IE:
Information element name Required Description
Suppression Of Announcements C This IE indicates that announcements or tones generated asa result of unsuccessful call setup shall be suppressed.
Call Reference Number M This IE carries the Call Reference Number provided by theGMSC in the Send Routeing Info IF.
GMSC Address M This IE is the E.164 address of the GMSC
Alerting Pattern C This IE indicates the kind of Alerting Pattern to be applied.
GMSC CAMEL Phases C This IE indicates the CAMEL Phases supported in theGMSC.
M Mandatory (The IE shall always be sent)
C Conditional (The IE shall be sent, if received from the GMSC in the Send Routeing Info)
9.10 VLR to HLR information flows
9.10.1 Insert Subscriber Data ack
9.10.1.1 Description
This IF is specified in GSM 09.02 [4] and used by the VLR to indicate to the HLR the result of the Insert Subscriber DataIF.
9.10.1.2 Information Elements
Insert Subscriber Data ack contains the following CAMEL specific IE:
Information element name Required Description
Supported CAMEL Phases C This IE identifies which CAMEL phases are supported by theMSC/VLR.
C Conditional (The IE shall always be sent when a CSI has been included in the ISD)
9.10.2 Provide Subscriber Info ack
9.10.2.1 Description
This IF is used by the VLR to provide the requested information to the HLR.
3GPP
3G TS 23.078 V3.2.0 (1999-11)2003G TS 23.078 version 3.2.0
9.10.2.2 Information Elements
Provide Subscriber Info ack contains the following CAMEL specific IE:
Information element name Required Description
Location Information C This IE indicates the location of the served subscriber. The elementscontained in this IE are specified in GSM 03.18 ([3]).
Subscriber State C This IE indicates the status of the MS. The states are:
- CAMELBusy: The MS is engaged on a transaction for a mobileoriginating or terminated circuit-switched call.
- NetworkDeterminedNotReachable: The network can determinefrom its internal data that the MS is not reachable.
- AssumedIdle: The state of the MS is neither "CAMELBusy" nor"NetworkDeterminedNotReachable".
C Conditional (The IE shall be sent, if requested and available)
9.10.3 Update Location
9.10.3.1 Description
This IF is used by the VLR to provide the information about supported CAMEL phases to the HLR.
9.10.3.2 Information Elements
Update Location contains the following CAMEL specific IE:
Information element name Required Description
Supported CAMEL phases C This IE indicates which phases of CAMEL are supported. It shall bepresent if a CAMEL phase different from phase 1 is supported.Otherwise may be absent.
9.10.4 Restore Data
9.10.4.1 Description
This IF is used by the VLR to provide the information about supported CAMEL phases to the HLR.
9.10.4.2 Information Elements
Restore Data contains the following CAMEL specific IE:
3GPP
3G TS 23.078 V3.2.0 (1999-11)2013G TS 23.078 version 3.2.0
Information element name Required Description
Supported CAMEL phases C This IE indicates which phases of CAMEL are supported. It shall bepresent if a CAMEL phase different from phase 1 is supported.Otherwise may be absent.
9.11 HLR to GMSC information flows
9.11.1 Send Routeing Info ack
9.11.1.1 Description
This IF is specified in GSM 03.18 [3] and is used by the HLR to transfer the requested routeing information to the GMSC.
9.11.1.2 Information Elements
Send Routeing Info ack contains the following CAMEL specific IE:
Information element name Required Description
Location Information C This IE indicates the location of the served subscriber.
O-CSI C This IE identifies the subscriber as having originating CAMELservices.
Shall be sent if O-CSI is active, and CFU or CFNRc has been invoked,or if both O-CSI and T-CSI are active.
Subscriber State C This IE indicates the status of the MS. The possible values of the IEare:
- CAMELBusy: The VLR has indicated that the MS is engagedon a transaction for a mobile originating or terminated circuit-switched call.
- NetworkDeterminedNotReachable: The VLR has indicated thatthe network can determine from its internal data that the MS is notreachable.
- AssumedIdle: The VLR has indicated that the state of the MS isneither "CAMELBusy" nor "NetworkDeterminedNotReachable".
- NotProvidedFromVLR: The VLR did not provide anyinformation on subscriber state even though it was requested.
T-CSI C This IE identifies the subscriber as having terminating CAMELservices.
Shall be sent if T-CSI is active and no Suppress T-CSI indicator ispresent in the SRI.
Basic Service Code C This IE indicates the type of basic service i.e., teleservice or bearerservice.
CUG Subscription Flag C This IE indicates if the called party has a CUG subscription. It shallonly be sent if the T-CSI is active and included in the Send RoutingInformation ack.
C Conditional (The IE shall be sent, if available)
C’ Conditional (The IE shall be sent, if available and indicated by Subscriber Information in Send RouteingInformation ack indicator.)
3GPP
3G TS 23.078 V3.2.0 (1999-11)2023G TS 23.078 version 3.2.0
Location Information contains the following information:
Information element name Required Description
Location Number C’ See GSM 03.18 [3].
CellIdOrLAI C’ See GSM 03.18 [3].
Geographical Information C’ See GSM 03.18 [3].
Age Of Location Information C’ See GSM 03.18 [3].
VLR number C See GSM 03.18 [3].
C Conditional (The IE shall be sent, if available)
C’ Conditional (The IE shall be sent, if available and indicated by Subscriber Information in Send RouteingInformation ack indicator.)
O-CSI is defined in section 0.
T-CSI contains the following information:
Information element name Required Description
gsmSCF Address M This IE is described in section 6.1.
Service Key M This IE is described in section 6.1.
Default Call Handling M This IE is described in section 6.1.
TDP List M This IE is described in section 6.1.
CAMEL Capability Handling C This IE is described in section 6.1. If this IE is absent, this indicatesthat CAMEL phase 1 is asked.
M Mandatory
C Conditional
9.12 GMSC to HLR information flows
9.12.1 Send Routeing Info
9.12.1.1 Description
This IF is described in GSM 03.18 [3] and is used to request information from the HLR to route an MT call.
9.12.1.2 Information Elements
Send Routeing Info contains the following CAMEL specific IE:
3GPP
3G TS 23.078 V3.2.0 (1999-11)2033G TS 23.078 version 3.2.0
Information element name Required Description
Alerting Pattern C This IE indicates the kind of Alerting Pattern to be applied.
Suppression Of Announcement C This IE indicates that announcements or tones generated as aresult of unsuccessful call setup shall be suppressed.Shall be sent in the second interrogation if available, i.e., when ithas been received from the gsmSCF.
Suppress T-CSI C This IE indicates that T-CSI shall be suppressed.Shall always be sent in the second interrogation
Supported CAMEL Phases M This IE lists the supported CAMEL phases.
Call Reference Number M This IE carries the Call Reference Number allocated for the call bythe GMSC.
Shall be allocated once per call and sent in both first and secondinterrogations.
GMSC Address M This IE is the E.164 address of the GMSC
C Conditional (The IE shall be sent, if received from the gsmSCF or set by the gsmSSF)
M Mandatory (The IE shall always be sent when the GMSC supports CAMEL)
9.13 MSC to gsmSCF information flows
9.13.1 SS Invocation Notification
9.13.1.1 Description
This IF is generated by the MSC when it shall notify the gsmSCF of a supplementary service invocation.
3GPP
3G TS 23.078 V3.2.0 (1999-11)2043G TS 23.078 version 3.2.0
9.13.1.2 Information Elements
The following information elements are required:
Information element name Required Description
Notification Event M This IE indicates the supplementary service invocation,resulting in the SS Invocation Notification IF.
Only the following Supplementary Services are allowed :Explicit Call Transfer, Call Deflection, Multi Party.
Notification Event SpecificInformation
C In the case of ECT, the sending entity shall include thecalled party for each call originated by the subscriber andrelevant to the ECT invocation. Note : the subscriber mayhave originated zero, one or two calls relevant to the ECTservice.
In the case of CD, the deflected to number shall beincluded in this information element.
In the case of MPTY, this IE shall be omitted.
IMSI M This IE identifies the mobile subscriber who has invokedthe supplementary service to be notified.
MSISDN M This IE identifies the mobile subscriber who has invokedthe supplementary service to be notified.
M Mandatory (The IE shall always be sent)
C Conditional (The IE shall be sent if applicable)
9.14 VMSC to GMSC information flows
9.14.1 Resume Call Handling
9.14.1.1 Description
This IF is described in GSM 03.79 [4] and is used to request the GMSC to take over handling the call so that it can beforwarded from the GMSC.
9.14.1.2 Information Elements
Resume Call Handling contains the following CAMEL specific IE:
Information element name Required Description
O-CSI C This IE contains O-CSI without triggering criteria. It indicates thatCAMEL handling applies for a forwarded call.Shall be present if CAMEL handling applies; otherwise shall beabsent.
C Conditional (The IE shall be sent if applicable)
3GPP
3G TS 23.078 V3.2.0 (1999-11)2053G TS 23.078 version 3.2.0
9.15 MSC to VLR information flows
9.15.1 Send Info For Outgoing Call
9.15.1.1 Description
This IF is described in GSM 03.18 [3] and is used to request the VLR to provide information to handle an outgoing call.
9.15.1.2 Information Elements
Send Info For Outgoing Call contains the following CAMEL specific IE
Information element name Required Description
Suppress O-CSI C This IE indicates that O-CSI shall be suppressed.Shall always be sent in the second interrogation.
C Conditional (The IE shall be sent if applicable)
9.15.2 Send Info For Reconnected Call
9.15.2.1 Description
This IF is used to request the VLR to provide information to handle a reconnected call.
9.15.2.2 Information Elements
Send Info For Reconnected Call contains the following IE
Information element name Required Description
Called number M E.164 number of the call destination.Bearer service C Bearer service required for the MO call, derived from the GSM
bearer capability information received in the setup request from theMS. One of bearer service or teleservice shall be present.
Teleservice C Teleservice required for the MO call, derived from the GSM bearercapability information received in the setup request from the MS orfrom the emergency setup request from the MS. One of bearerservice or teleservice shall be present.
CUG index C For the definition of this IE, see ETS 300 546 [9]. Shall be present ifit was received in the setup request from the MS.
Suppress preferential CUG C For the definition of this IE, see ETS 300 546 [9]. Shall be present ifit was received in the setup request from the MS.
Suppress CUG outgoing access C For the definition of this IE, see ETS 300 546 [9]. Shall be present ifit was received in the setup request from the MS.
Suppress O-CSI C This IE indicates that O-CSI shall be suppressed.Shall always be sent in the second interrogation.
M Mandatory (The IE shall always be sent)
C Conditional (The IE shall be sent if applicable)
3GPP
3G TS 23.078 V3.2.0 (1999-11)2063G TS 23.078 version 3.2.0
9.16 VLR to MSC information flows
9.16.1 Complete Call
9.16.1.1 Description
This IF is described in GSM 03.18 [3] and is used to instruct the MSC to continue the connection of a call.
9.16.1.2 Information Elements
Complete Call contains the following CAMEL specific IE:
Information element name Required Description
O-CSI C This IE indicates that CAMEL handling applies for an MO call.Shall be present in the response to the first interrogation for anMO call if CAMEL handling applies; otherwise shall be absent.Shall be absent in the response to the second interrogation for anMO call and in the response to the interrogation for an MT call.
Call Reference Number M This IE carries the Call Reference Number provided by the HLR inthe Provide Roaming Number IF.
GMSC Address M This IE is the E.164 address of the GMSC.
M Mandatory (The IE shall always be sent)
C Conditional (The IE shall be sent if applicable)
9.16.2 Process Call Waiting
9.16.2.1 Description
This IF is described in GSM 03.18 [3] and is used to instruct the MSC to continue the connection of a waiting call.
9.16.2.2 Information Elements
Process Call Waiting contains the following CAMEL specific IE:
Information element name Required Description
Call Reference Number M This IE carries the Call Reference Number provided by the HLR inthe Provide Roaming Number IF.
GMSC Address M This IE is the E.164 address of the GMSC.
M Mandatory (The IE shall always be sent)
9.16.3 Send Info For Incoming Call ack
9.16.3.1 Description
This IF is described in GSM 03.18 [3] and is used to indicate that the incoming call for which the MSC requestedsubscription information shall be forwarded.
3GPP
3G TS 23.078 V3.2.0 (1999-11)2073G TS 23.078 version 3.2.0
9.16.3.2 Information Elements
Send Info For Incoming Call ack contains the following CAMEL specific IE:
Information element name Required Description
O-CSI C This IE indicates that CAMEL handling applies for a forwardedcall.Shall be present if CAMEL handling applies; otherwise shall beabsent.
Suppression Of Announcement C This IE indicates that announcements or tones generated whenthe call is forwarded shall be suppressed.Shall be sent if it was received in the Provide Roaming Number forthis call.
Call Reference Number M This IE carries the Call Reference Number provided by the HLR inthe Provide Roaming Number IF.
GMSC Address M This IE is the E.164 address of the GMSC.
SS-CSI C This IE indicates that SS invocation notification applies for thecall.
Shall be present if SS invocation notification is required if CallDeflection is invoked; otherwise shall be absent.
M Mandatory (The IE shall always be sent)
C Conditional (The IE shall be sent if applicable)
9.16.4 Send Info For Incoming Call negative response
9.16.4.1 Description
This IF is described in GSM 03.18 [3] and is used to indicate that the incoming call for which the MSC requestedsubscription information shall not be connected.
9.16.4.2 Information Elements
Send Info For Incoming Call negative response contains the following CAMEL specific IE which may be attached as a IEto any of the negative response values defined in GSM 03.18 [3]:
Information element name Required Description
Suppression Of Announcement C This IE indicates that announcements or tones generated as aresult of unsuccessful call setup shall be suppressed.Shall be sent if it was received in the Provide Roaming Number forthis call.
C Conditional (The IE shall be sent if applicable)
3GPP
3G TS 23.078 V3.2.0 (1999-11)2083G TS 23.078 version 3.2.0
10 Interaction with supplementary services
10.1 Line identificationFor further study.
10.2 Call forwarding services
10.2.1 Registration of Call Forwarding
The functional behaviour for the registration of the Call Forwarding supplementary service is defined in GSM 03.82. Theprocedure specific to CAMEL is defined in this subclause:
- CAMEL_Check_CF_Interaction
10.2.2 Invocation of Call Forwarding
The functional behaviour for the invocation of the Call Forwarding supplementary service is defined in GSM 03.18. Thefollowing additional requirements apply.
When call forwarding is invoked for a CAMEL subscriber with O-CSI, the gsmSSF shall send the FTN to the gsmSCF inthe format in which it was received from the HLR.
An HLR shall not send an FTN which is not in international E.164 format to a VLR or GMSC which does not supportCAMEL phase 2, i.e.:if the HLR is handling a request from a GMSC for routeing information and the forwarded-to numberis registered a format other than international E.164, the service logic in the HLR shall behave as if the call forwarding isprovisioned but not registered.
10.3 Call Barring servicesWhen a CAMEL subscriber with O-CSI and TIF-CSI attempts to activate a conditional call barring service (BOIC,BOIC-exHC), the HLR shall not check the interactions with call forwarding.
3GPP
3G TS 23.078 V3.2.0 (1999-11)2093G TS 23.078 version 3.2.0
Procedure in the HLR to check the
provision of TIF-CSI.
Procedure CAMEL_Check_CF_Interaction 1(1)
Result:=
fail
Result:=
pass
TIF-CSI
provided?No
Yes
Figure 58a: Procedure CAMEL_Check_CF_Interaction (sheet 1)
3GPP
3G TS 23.078 V3.2.0 (1999-11)2103G TS 23.078 version 3.2.0
3GPP
3G TS 23.078 V3.2.0 (1999-11)2113G TS 23.078 version 3.2.0
Annex A:Change history
Change historyTSG CN# Spec Version CR <Phase> New Version Subject/CommentApr 1999 GSM 03.78 7.0.0 Transferred to 3GPP CN1CN#03 23.078 3.0.0 3.0.0 Approved at CN#03CN#4 23.078 3.1.0 003 R99 3.1.0 Inclusion of Subscriber Activity Information Flow
CN#4 23.078 3.1.0 004 R99 3.1.0 Inclusion of Alerting Pattern in Provide RoamingNumber
CN#4 23.078 3.1.0 005 R99 3.1.0 Dialled Number String FormatCN#4 23.078 3.1.0 006 R99 3.1.0 Handling of AC/ACR in DP Busy, DP No Answer
and DPCN#4 23.078 3.1.0 007 R99 3.1.0 Inclusion of Activity Test IF between gsmSCF &
gsmSRF and gsmSCF and assistSSF
CN#4 23.078 3.1.0 008 R99 3.1.0 Correction of USSD Information flows
CN#4 23.078 3.1.0 009 R99 3.1.0 Various corrections
CN#4 23.078 3.1.0 010 R99 3.1.0 Correction of CAMEL Phase interworking withCall Forwarding
CN#4 23.078 3.1.0 011 R99 3.1.0 Renaming of Call Active Variable
CN#4 23.078 3.1.0 012 R99 3.1.0 Reporting of O/T_Abandon DP when callerclears during O/T_Busy, O/T_No_Answer orRoute_Select_Failure EDP-R.
CN#4 23.078 3.1.0 013 R99 3.1.0 Clarification on the scope of CAMEL CapabilityHandling parameter
CN#4 23.078 3.1.0 014 R99 3.1.0 Refining trigger criteria at DP2, due to theintroduction of North American Equal Access
CN#4 23.078 3.1.0 015 R99 3.1.0 Introduction of MSISDN in USSD operation
CN#4 23.078 3.1.0 016 R99 3.1.0 MSC address in Initial DP
CN#4 23.078 3.1.0 017 R99 3.1.0 Correction of gsmSDL; return to idle after ACR
CN#4 23.078 3.1.0 018 R99 3.1.0 Notification of call forwarding to the gsmSCF
CN#5 23.078 3.1.0 019 R99 3.2.0 Inclusion of the SS invocation notificationprocedure
CN#5 23.078 3.1.0 021 R99 3.2.0 Removal of TDP criteria from resume callhandling
CN#5 23.078 3.1.0 022r1 R99 3.2.0 GMSC CAMEL phases in Provide RoamingNumber
CN#5 23.078 3.1.0 023r1 R99 3.2.0 Call Reference Number
CN#5 23.078 3.1.0 025 R99 3.2.0 Clarification on Call Reference Number andGMSC address
CN#5 23.078 3.1.0 027 R99 3.2.0 Value of the Active Call parameter in ACRoperation
CN#5 23.078 3.1.0 028 R99 3.2.0 Correction of process gsmSSF SDL
CN#5 23.078 3.1.0 029 R99 3.2.0 Alignment of CAMEL2 FCI & handling of CIR
CN#5 23.078 3.1.0 030 R99 3.2.0 Correction of Inhibiting Triggering Criteria
3GPP
3G TS 23.078 V3.2.0 (1999-11)2123G TS 23.078 version 3.2.0
3GPP
3G TS 23.078 V3.2.0 (1999-11)2133G TS 23.078 version 3.2.0
History
Document history
V3.0.0 May 1999 Approved at TSGN #3. Under TSG TSG CN Change Control.
V3.1.0 August 1999 Approved at TSGN #4
V3.2.0 November 1999 Approved at TSGN #5
