ETSI TS 124 093 V3.0.0 (2000-01) TechnicalSpecification Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Completion of calls to Busy Subscriber (CCBS) - Stage 3 (3G TS 24.093 version 3.0.0 Release 1999) R GLOBALSYSTEM FOR MOBILECOMMUNICATIONS (3GTS24.093version3.0.0Release1999) 1 ETSITS124093V3.0.0(2000-01) Reference DTS/TSGN-SS24093U Keywords GSM,UMTS ETSI Postaladdress F-06921SophiaAntipolisCedex-FRANCE Officeaddress 650RoutedesLucioles-SophiaAntipolis Valbonne-FRANCE Tel.:+33492944200 Fax:+33493654716 SiretN°34862356200017-NAF742C Associationàbutnonlucratifenregistréeàla Sous-PréfecturedeGrasse(06)N°7803/88 Internet [email protected] IndividualcopiesofthisETSIdeliverable canbedownloadedfrom http://www.etsi.org Ifyoufinderrorsinthepresentdocument,sendyour commentto:[email protected] Importantnotice ThisETSIdeliverablemaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingor perceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF). Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetwork drivewithinETSISecretariat. CopyrightNotification Nopartmaybereproducedexceptasauthorizedbywrittenpermission. Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia. ©EuropeanTelecommunicationsStandardsInstitute2000. Allrightsreserved. ETSI (3GTS24.093version3.0.0Release1999) 2 ETSITS124093V3.0.0(2000-01) Intellectual Property Rights IPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.Theinformation pertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefound inSR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespect ofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver (http://www.etsi.org/ipr). PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.Noguarantee canbegivenastotheexistenceofotherIPRsnotreferencedinSR000314(ortheupdatesontheETSIWebserver) whichare,ormaybe,ormaybecome,essentialtothepresentdocument. Foreword ThisTechnicalSpecification(TS)hasbeenproducedbytheETSI3rdGenerationPartnershipProject(3GPP). Thepresentdocumentmayrefertotechnicalspecificationsorreportsusingtheir3GPPidentitiesorGSMidentities. TheseshouldbeinterpretedasbeingreferencestothecorrespondingETSIdeliverables.Themappingofdocument identitiesisasfollows: For3GPPdocuments: 3GTS|TRnn.nnn"<title>"(withorwithouttheprefix3G) isequivalentto ETSITS|TR1nnnnn"[Digitalcellulartelecommunicationssystem(Phase2+)(GSM);]UniversalMobile TelecommunicationsSystem;<title> ForGSMdocumentidentitiesoftype"GSMxx.yy",e.g.GSM01.04,thecorrespondingETSIdocumentidentitymaybe foundintheCrossReferenceListonwww.etsi.org/key ETSI 3G TS 24.093 version 3.0.0 3 3G TS 24.093 V3.0.0 (1999-05) Contents Foreword............................................................................................................................................................4 1 Scope........................................................................................................................................................5 2 References................................................................................................................................................5 3 Definitions and abbreviations..................................................................................................................6 3.1 Definitions.........................................................................................................................................................6 3.2 Abbreviations.....................................................................................................................................................6 4 General.....................................................................................................................................................7 4.1 Overview............................................................................................................................................................7 4.2 Activation..........................................................................................................................................................7 4.3 CCBS Recall and CCBS Call Set-up.................................................................................................................9 4.3.1 CCBS Call Set-up (MS A idle)....................................................................................................................9 4.3.2 CCBS Call Set-up (MS A not idle)............................................................................................................11 4.3.2.1 Existing call released............................................................................................................................11 4.3.2.2 Existing call placed on hold..................................................................................................................13 4.4 Deactivation.....................................................................................................................................................15 4.5 Interrogation....................................................................................................................................................16 Annex A (Informative): Operation for Non-Supporting MS’s...........................................................18 A.0 Scope......................................................................................................................................................18 A.1 MSs which do not support CCBS..........................................................................................................18 A.1.1 Activation for non supporting MSs..................................................................................................................18 A.2 CCBS Call Set-up for non supporting MSs...........................................................................................20 A.3 Deactivation for non supporting MSs....................................................................................................21 A.4 Interrogation for non supporting MSs....................................................................................................21 Annex B: Change history......................................................................................................................22 History..............................................................................................................................................................23 3GPP 3G TS 24.093 version 3.0.0 4 3G TS 24.093 V3.0.0 (1999-05) Foreword This Technical Specification has been produced by the 3GPP. This TS gives the stage 3 description of the Completion of Calls to Busy Subscriber (CCBS) supplementary service within the 3GPP system. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; 3GPP 3G TS 24.093 version 3.0.0 5 3G TS 24.093 V3.0.0 (1999-05) 1 Scope The present dcoument gives the stage 3 description of the Completion of Calls to Busy Subscriber (CCBS) supplementary service. The present document specifies the procedures used at the radio interface (Reference point Um as defined in GSM 04.02) for normal operation, activation, deactivation, invocation and interrogation of the completion of calls to busy subscriber supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface. In GSM 04.10 the general aspects of the specification of supplementary services at the layer 3 radio interface are given. GSM 04.80 specifies the formats and coding for the supplementary services. Definitions and descriptions of supplementary services are given in GSM 02.04, GSM 02.8x and GSM 02.9x-series. Technical specification GSM 02.93 is related specifically to the Completion of Calls to Busy Subscriber supplementary service. The technical realization of supplementary services is described in technical specifications GSM 03.11, GSM 03.8x and 03.9x-series. GSM 03.93 is related specifically to Completion of Calls to Busy Subscriber supplementary service. The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in GSM 04.07 and GSM 04.08. The following supplementary services belong to the call completion supplementary services and are described in the present document: - Completion of Calls to Busy Subscriber (CCBS) (see clause 4). 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); "Abbreviations and acronyms". [2] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services". [3] GSM 02.07: "Digital cellular telecommunications system (Phase 2+); Mobile Stations (MS) features". [4] GSM 02.30: "Digital cellular telecommunications system (Phase 2+); Man-Machine Interface (MMI) of the Mobile Station (MS)". [5] GSM 02.93: "Digital cellular telecommunications system (Phase 2+); Completion of Calls to Busy Subscriber (CCBS) Service description, Stage 1". [6] GSM 03.11: "Digital cellular telecommunications system (Phase 2+); Technical realization of supplementary services". 3GPP 3G TS 24.093 version 3.0.0 6 3G TS 24.093 V3.0.0 (1999-05) [7] GSM 03.93: "Digital cellular telecommunications system (Phase 2+); Technical realization of Completion of Calls to Busy Subscriber (CCBS)". [8] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". [9] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3 General aspects". [10] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [11] GSM 04.10: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 Supplementary services specification General aspects". [12] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification Formats and coding". [13] GSM 04.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3". 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document the following definitions apply. Subscriber A: The user of MS A, requesting CCBS. Destination B: The entity addressed in the original call set up, which is busy when first called by subscriber A. 3.2 Abbreviations For the purposes of the present document the following abbreviations apply: CCBS Completion of Calls to Busy Subscriber MS A Mobile Station of subscriber A NDUB Network Determined User Busy Further related abbreviations are given in GSM 01.04 3GPP 3G TS 24.093 version 3.0.0 7 3G TS 24.093 V3.0.0 (1999-05) 4 General 4.1 Overview CCBS allows a calling subscriber A, encountering a Network Determined User Busy (NDUB) called destination B, to be notified when destination B is idle and to have the network reinitiate the call to destination B, if subscriber A desires. All of the radio signalling specific to CCBS is at the subscriber A-side. Each procedure is described in turn. There is no radio signalling specific to CCBS at destination B-side. The radio signalling on the destination B-side uses basic call signalling procedures only. A mobile station that supports CCBS shall support the requirements of the following options used in GSM 04.08: 1) Prolonged Clearing Procedure; 2) Network Initiated Mobile Originated Connection Management (MO CM) Connection Request; 3) Network initiated MO call. A network supporting CCBS shall support the requirements of the following options used in GSM 04.08: 1) CCBS Request activation; and 2) Network initiated MO call. 4.2 Activation When CCBS is allowed the network shall give subscriber A the option of activating a CCBS Request. The network shall send a DISCONNECT message to MS A (cause #17 (User Busy) or cause #34 (no circuit / channel available)) with diagnostic field indicating CCBS is Possible and allowed actions indicating CCBS is Possible. The network starts the retention timer T1 when it sends the DISCONNECT message. The MS shall not release the connection with the network if allowed actions is present. If subscriber A attempts to activate a CCBS Request, MS A shall send a RELEASE message, with the Facility information element indicating CCBSRequest and the network shall stop T1. If the subscriber A does not accept CCBS activation, the MS shall send normal RELEASE message and the network shall stop T1 and continue normal call clearing. If the timer T1 expires before the RELEASE message is received from the MS, the network shall continue normal call clearing. If the network accepts the activation attempt, it shall acknowledge it by sending a RELEASE COMPLETE message containing the Facility information element with the CCBS index and optionally the AddressOfB, SubAddressOfB and the BasicServiceCode. If the network rejects the activation attempt, it shall send a RELEASE COMPLETE message containing the Facility information element with a return error indication. If a TCH has been allocated for the initial call and there are no further need for this channel configuration, the network may reconfigure the ongoing connection from TCH(s) mode to SDCCH only mode while waiting for further user input activity. It is a network option to maintain the ongoing connection in TCH mode while waiting for further user input activity. SS Version Indicator value 3 or above has to be used. 3GPP 3G TS 24.093 version 3.0.0 8 3G TS 24.093 V3.0.0 (1999-05) MS A NETWORK SETUP (Note 1) -------------------------------------------------------------------------------------------------------------------------------> (Bearer capability, CC capabilities, Called party BCD number) DISCONNECT (Note 2) <------------------------------------------------------------------------------------------------------------------------------ ((Cause #17 (User Busy) / Cause #34 (no circuit/channel available)), diagnostic = CCBSPossible, allowed actions = CCBS Possible) RELEASE (Note 3) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -> RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - RELEASE (Note 4) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ((Cause #17 (User Busy) / Cause #34 (no circuit/channel available) ) / Cause #102 (recovery on timer expiry)) RELEASE COMPLETE - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -> RELEASE ---------------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = AccessRegisterCCEntry) RELEASE COMPLETE <-------------------------------------------------------------------------------------------------------------------------------- Facility (Return Result (CCBS Index, AddressOfB, Sub_AddressOfB, BasicServiceCode)) (Note 5) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return Error = (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject = (Invoke Problem)) NOTE 1: The original call set-up is shown for completeness. NOTE 2: The CCBS activation is possible only when allowed actions field contains CCBS Possible indication NOTE 3: If Subscriber A rejects the CCBS Possible indication, then the MS shall send RELEASE. NOTE 4: If T1 (Retention timer) expires then the network shall send a RELEASE message to the MS. The Timer expiry cause may be included. NOTE 5: AddressOfB, Sub_AddressOfB and BasicServiceCode are optional parameters. Figure 4.2: Activation of a CCBS Request for supporting MSs 3GPP 3G TS 24.093 version 3.0.0 9 3G TS 24.093 V3.0.0 (1999-05) 4.3 CCBS Recall and CCBS Call Set-up When destination B becomes free the network shall offer subscriber A the option of recalling destination B. The network shall prompt MS A to allocate a Transaction Identifier (TI) and establish the CC connection by sending a CM SERVICE PROMPT message. MS A establishes the CC connection by sending a START CC message to the network. The network shall then send a CC ESTABLISHMENT message to MS A and shall include the Setup container. The Setup container contains information necessary to set-up the CCBS Call. The MS can modify the Bearer Capability (BC), High Level Compatibility (HLC) and Low Level Compatibility (LLC) information within the Setup container provided that the same Basic Service Group is maintained. If MS A is compatible with the basic service group it sends CC ESTABLISHMENT CONFIRMED message to the network. Once the network has received the CC ESTABLISHMENT CONFIRMED message it shall send a RECALL message to MS A, which contains information to be presented to the subscriber. At this stage, if the MS detects that ACM ≥ ACMmax, the MS shall interrupt the recall procedure, shall not alert the user and shall send a RELEASE COMPLETE message with the appropriate cause value to the network. If subscriber A accepts the CCBS recall, MS A shall establish a new call with the SETUP message. MSC A shall maintain the RR connection with MS A throughout the time when acceptance of the CCBS Recall is possible. Once the SETUP message is received, normal call handling continues. 4.3.1 CCBS Call Set-up (MS A idle) Figure 4.3.1 shows the case where MS A is idle when a CCBS Recall is received by the originating network. The different possibilities for allocating a traffic channel are described in GSM 04.08. 3GPP