SIST ETS 300 359-3:1998

Integrated Services Digital Network (ISDN); Completion of Calls to Busy Subscriber (CCBS) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user

:

Digitalno omrežje z integriranimi storitvami (ISDN) - Dopolnilna storitev: dokončanje klica do zasedenega naročnika (CCBS) - Protokol digitalne naročniške signalizacije št. 1 (DSS1) - 3. del: Zgradba preskušalnega niza in namen preskušanja (TSS&TP) - Specifikacija za uporabnika

General Information

• Status: Published
• Publication Date: 31-May-1998
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• Technical Committee: SPS - Signalling protocols and switching
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jun-1998
• Due Date: 01-Jun-1998
• Completion Date: 01-Jun-1998
• Ref Project: ETSI ETS 300 359-3 ed.1 (1996-10) - Integrated Services Digital Network (ISDN); Completion of Calls to Busy Subscriber (CCBS) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.VWRULWHYIntegrated Services Digital Network (ISDN); Completion of Calls to Busy Subscriber (CCBS) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:ETS 300 359-3 E13SIST ETS 300 359-3:1998en01-jDQXDU-19983SIST ETS 300 359-3:1998SLOVENSKI
STANDARD



SIST ETS 300 359-3:1998



EUROPEANETS 300 359-3TELECOMMUNICATIONOctober 1996STANDARDSource: ETSI TC-SPSReference: DE/SPS-05061-G-3ICS:33.080Key words:ISDN, DSS1, supplementary service, CCBS, testing, TSS&TP, userIntegrated Services Digital Network (ISDN);Completion of Calls to Busy Subscriber (CCBS)supplementary service;Digital Subscriber Signalling System No. one (DSS1) protocol;Part 3: Test Suite Structure and Test Purposes (TSS&TP)specification for the userETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail].: [phone] - Fax: [phone]Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1996. All rights reserved.SIST ETS 300 359-3:1998



Page 2ETS 300 359-3: October 1996Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.SIST ETS 300 359-3:1998



Page 3ETS 300 359-3: October 1996ContentsForeword.51Scope.72Normative references.73Definitions.83.1Definitions related to conformance testing.83.2Definitions related to ETS 300 359-1.84Abbreviations.95Test Suite Structure (TSS).96Test Purposes (TP).106.1Introduction.106.1.1TP naming convention.106.1.2Source of TP definition.106.1.3TP structure.106.1.4Test strategy.116.2User TPs for CCBS.126.2.1User (S/T).126.2.1.1User A.126.2.1.1.1Activation.126.2.1.1.2Deactivation.136.2.1.1.3Interrogation.146.2.1.1.4Invocation and operation.156.2.1.1.5Retention.176.2.1.2User B.186.2.1.3GFP.186.2.2User (T).186.2.2.1Originating side.196.2.2.1.1General.196.2.2.1.2GFP.216.2.2.2Destination side.216.2.2.2.1General.216.2.2.2.2GFP.247Compliance.258Requirements for a comprehensive testing service.25History.26SIST ETS 300 359-3:1998



Page 4ETS 300 359-3: October 1996Blank pageSIST ETS 300 359-3:1998



Page 5ETS 300 359-3: October 1996ForewordThis European Telecommunication Standard (ETS) has been produced by the Signalling Protocols andSwitching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).This ETS is part 3 of a multi-part standard covering the Digital Subscriber Signalling System No. one(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) Completion of Calls toBusy Subscriber (CCBS) supplementary service, as described below:Part 1:"Protocol specification";Part 2:"Protocol Implementation Conformance Statement (PICS) proforma specification";Part 3:"Test Suite Structure and Test Purposes (TSS&TP) specification for the user";Part 4:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information forTesting (PIXIT) proforma specification for the user";Part 5:"TSS&TP specification for the network";Part 6:"ATS and partial PIXIT proforma specification for the network".Transposition datesDate of adoption of this ETS:4 October 1996Date of latest announcement of this ETS (doa):31 January 1997Date of latest publication of new National Standardor endorsement of this ETS (dop/e):31 July 1997Date of withdrawal of any conflicting National Standard (dow):31 July 1997SIST ETS 300 359-3:1998



Page 6ETS 300 359-3: October 1996Blank pageSIST ETS 300 359-3:1998



Page 7ETS 300 359-3: October 19961ScopeThis third part of ETS 300 359 specifies the Test Suite Structure and Test Purposes (TSS&TP) for theUser side of the T reference point or coincident S and T reference point (as defined in ITU-TRecommendation I.411 [7]) of implementations conforming to the stage three standard of the Completionof Calls to Busy Subscriber (CCBS) supplementary service for the pan-European Integrated ServicesDigital Network (ISDN) by means of the Digital Subscriber Signalling System No. one (DSS1) protocol,ETS 300 359 [1].A further part of this ETS specifies the Abstract Test Suite (ATS) and partial Protocol ImplementationeXtra Information for Testing (PIXIT) proforma based on this ETS. Other parts specify the TSS&TP andthe ATS and partial PIXIT proforma for the Network side of the T reference point or coincident S and Treference point of implementations conforming to ETS 300 359-1 [1].2Normative referencesThis ETS incorporates by dated and undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this ETS only when incorporated in it by amendment or revision. For undated references the latestedition of the publication referred to applies.[1]ETS 300 359-1 (1995): "Integrated Services Digital Network (ISDN); Completionof Calls to Busy Subscriber (CCBS) supplementary service; Digital SubscriberSignalling System No. one (DSS1) protocol; Part 1: Protocol specification".[2]ETS 300 359-2 (1995): "Integrated Services Digital Network (ISDN); Completionof Calls to Busy Subscriber (CCBS) supplementary service; Digital SubscriberSignalling System No. one (DSS1) protocol; Part 2: Protocol ImplementationConformance Statement (PICS) proforma specification".[3]ISO/IEC 9646-1: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 1: General Concepts".[4]ISO/IEC 9646-2: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 2: Abstract Test Suite specification".[5]ISO/IEC 9646-3: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 3: The Tree and Tabular CombinedNotation".[6]ETS 300 196-1 (1993): "Integrated Services Digital Network (ISDN); Genericfunctional protocol for the support of supplementary services; Digital SubscriberSignalling System No. one (DSS1) protocol; Part 1: Protocol specification".[7]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces -Reference configurations".[8]ETS 300 102-1: "Integrated Services Digital Network (ISDN);User-network interface layer 3; Specifications for basic call control".[9]ITU-T Recommendation I.112 (1993): "Vocabulary and terms for ISDNs".[10]CCITT Recommendation E.164 (1991): "Numbering plan for the ISDN era".[11]ITU-T Recommendation I.210 (1993): "Principles of the telecommunicationservices supported by an ISDN and the means to describe them".[12]ETS 300 196-2 (1996): "Integrated Services Digital Network (ISDN); Genericfunctional protocol for the support of supplementary services; Digital SubscriberSignalling System No. one (DSS1); Part 2: Protocol ImplementationConformance Statement (PICS) proforma specification".SIST ETS 300 359-3:1998



Page 8ETS 300 359-3: October 19963DefinitionsFor the purposes of this ETS, the following definitions apply:3.1Definitions related to conformance testingabstract test case: Refer to ISO/IEC 9646-1 [3].Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [3].Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [3].implicit send event: Refer to ISO/IEC 9646-3 [5].lower tester: Refer to ISO/IEC 9646-1 [3].point of control and observation: Refer to ISO/IEC 9646-1 [3].Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [3].PICS proforma: Refer to ISO/IEC 9646-1 [3].Protocol Implementation eXtra Information for Testing (PIXIT): Refer to ISO/IEC 9646-1 [3].PIXIT proforma: Refer to ISO/IEC 9646-1 [3].system under test: Refer to ISO/IEC 9646-1 [3].Test Purpose (TP): Refer to ISO/IEC 9646-1 [3].3.2Definitions related to ETS 300 359-1Call Held auxiliary state: See ETS 300 196-1 [6], subclause 7.1.2.call reference: See ETS 300 102-1 [8], subclause 4.3.component: See ETS 300 196-1 [6], subclause 11.2.2.1.Idle auxiliary state: See ETS 300 196-1 [6], subclause 7.1.2.Integrated Services Digital Network (ISDN): See ITU-T Recommendation I.112 [9], definition 308.ISDN number: A number conforming to the numbering and structure specified in CCITTRecommendation E.164 [10].invoke component: See ETS 300 196-1 [6], subclause 11.2.2.1.return error component: See ETS 300 196-1 [6], subclause 11.2.2.1.return result component: See ETS 300 196-1 [6], subclause 11.2.2.1.served user: The served user is the user who invokes the CCBS supplementary service.service; telecommunication service: See ITU-T Recommendation I.112 [9], definition 201.supplementary service: See ITU-T Recommendation I.210 [11], subclause 2.4.user: The DSS1 protocol entity at the User side of the user-network interface where a T reference point orcoincident S and T reference point applies.SIST ETS 300 359-3:1998



Page 9ETS 300 359-3: October 1996user (S/T): The DSS1 protocol entity at the User side of the user-network interface where a coincidentS and T reference point applies.user (T): The DSS1 protocol entity at the User side of the user-network interface where a T referencepoint applies (User is the Private ISDN).4AbbreviationsFor the purposes of this ETS, the following abbreviations apply:ATMAbstract Test MethodATSAbstract Test SuiteCCBSCompletion of Calls to Busy SubscriberCRCall ReferenceCR1normal (bearer related) CRCR2CR used for bearer independent transport mechanismDSS1Digital Subscriber Signalling System No. oneGFPGeneric Functional ProtocolISDNIntegrated Services Digital NetworkIUTImplementation Under TestPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingTPTest PurposeTSSTest Suite StructureU00Null call stateU01Call Initiated call stateU03Outgoing Call Proceeding call stateU04Call Delivered call stateU06Call Present call stateU07Call Received call stateU08Connect Request call stateU09Incoming Call Proceeding call stateU10Active call stateU12Disconnect Indication call stateU25Overlap Receiving call stateU31Bearer Independent Transport call stateUIUnnumbered Information5Test Suite Structure (TSS)CCBS - UserUser (S/T)User (T)User AUser B(06)GFP(07)OriginatingsideDestinationsideGeneral(08)GFP(09)General(10)GFP(11)Activation(01)Deactivation(02)Interrogation(03)Invocation andoperation(04)Retention(05)NOTE:Numbers in brackets represent group numbers and are used in TP identifiers.Figure 1: Test suite structureSIST ETS 300 359-3:1998



Page 10ETS 300 359-3: October 19966Test Purposes (TP)6.1IntroductionFor each test requirement a TP is defined.6.1.1TP naming conventionTPs are numbered, starting at 001, within each group. Groups are organized according to the TSS.Additional references are added to identify the actual test suite and whether it applies to the network or theuser (see table 1).Table 1: TP identifier naming convention schemeIdentifier:__=supplementary service:e.g. "CCBS"=type of IUT:UUserNNetwork=group2 digit field representing group reference according to TSS=sequential number(001-999)6.1.2Source of TP definitionThe TPs are based on ETS 300 359-1 [1].6.1.3TP structureEach TP has been written in a manner which is consistent with all other TPs. The intention of this is tomake the TPs more readable and checkable. A particular structure has been used and this is illustrated intable 2. This table should be read in conjunction with any TP, i.e. use a TP as an example to fullyunderstand the table.SIST ETS 300 359-3:1998



Page 11ETS 300 359-3: October 1996Table 2: Structure of a single TPTP partTextExampleHeader tabsee table 1 tabsubclause 0.0.0 tabvalid, invalid, inopportune CR.mandatory, optional, conditionalStimulusEnsure that the IUT in theU10, U12, etc.and CCBS Idle state see below for message structurereceiving a XXXX messageor to request a .Reactionsends, saves, does, etc.using en-bloc sending, .if the action is sending
see below for message structure, etc.and enters and/or and remains in the same call state(s)or and enters call state Messagestructuremessage containing aSETUP, FACILITY, CONNECT, .a) information element withb) a encoded as or including and back to a or b,Bearer capability, Facility, .NOTE:Text in italics will not appear in TPs and text between <> is filled in for each TP and maydiffer from one TP to the next.6.1.4Test strategyAs the base standard ETS 300 359-1 [1] contains no explicit requirements for testing, the TPs weregenerated as a result of an analysis of the base standard and the PICS specification ETS 300 359-2 [2].The criteria applied included the following:-only the requirements from the point of view of the T or coincident S and T reference point areconsidered;-whether or not a test case can be built from the TP is not considered.SIST ETS 300 359-3:1998



Page 12ETS 300 359-3: October 19966.2User TPs for CCBS6.2.1User (S/T)Selection:IUT supports coincident S and T reference point procedures. PICS: R 3.2.NOTE:Unless stated otherwise, all FACILITY messages in TPs in this subclause use thedummy call reference as specified in subclause 8.3.2.2 of ETS 300 196-1 [6] (bearerindependent connectionless transport mechanism). Where an UnnumberedInformation (UI) frame is specified for a FACILITY message, the message is sent orreceived using broadcast procedures; otherwise point-to-point procedures are used.6.2.1.1User A6.2.1.1.1ActivationCCBS_U01_001subclause 9.1.1validmandatoryEnsure that the IUT in call state U12 and CCBS Idle state, having been informed that the network isperforming the Call Information Retention procedure, to activate the CCBS supplementary service,sends a FACILITY message containing a Facility information element with a CCBSRequest invokecomponent including the callLinkageID parameter and enters the CCBS Requested state beforeexpiry of timer T-RETENTION.CCBS_U01_002subclause 9.1.1validmandatoryEnsure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY messagecontaining a Facility information element with a CCBSRequest return result component including arecallMode parameter indicating "specificRecall",sends no message but retains the CCBSReference and enters CCBS Activated state.CCBS_U01_003subclause 9.1.1validoptionalEnsure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY messagecontaining a Facility information element with a CCBSRequest return result component including arecallMode parameter indicating "globalRecall",sends no message, retains the cCBSReference parameter and enters CCBS Activated state,orsends no message, releases the cCBSReference parameter and remains in the CCBS Requestedstate.CCBS_U01_004subclause 9.1.2validmandatoryEnsure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY messagecontaining a Facility information element with a CCBSRequest return error component indicating"invalidCallLinkageID",sends no message, releases the callLinkageID parameter and enters CCBS Idle state.CCBS_U01_005subclause 9.1.2validmandatoryEnsure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY messagecontaining a Facility information element with a CCBSRequest return error component indicating"notSubscribed",sends no message and enters the CCBS Idle state.CCBS_U01_006subclause 9.1.2validmandatoryEnsure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY messagecontaining a Facility information element with a CCBSRequest return error component indicating"callFailureReasonNotBusy",sends no message and enters the CCBS Idle state.CCBS_U01_007subclause 9.1.2validmandatoryEnsure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY messagecontaining a Facility information element with a CCBSRequest return error component indicating"outgoingCCBSQueueFull",sends no message and enters the CCBS Idle state.SIST ETS 300 359-3:1998



Page 13ETS 300 359-3: October 1996CCBS_U01_008subclause 9.1.2validmandatoryEnsure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY messagecontaining a Facility information element with a CCBSRequest return error component indicating"cCBSIsAlreadyActivated",sends no message and enters the CCBS Idle state.CCBS_U01_009subclause 9.1.2validmandatoryEnsure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY messagecontaining a Facility information element with a CCBSRequest return error component indicating"supplementaryServiceInteractionNotAllowed",sends no message and enters the CCBS Idle state.CCBS_U01_010subclause 9.1.2validmandatoryEnsure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY messagecontaining a Facility information element with a CCBSRequest return error component indicating"longTermDenial",sends no message and enters the CCBS Idle state.CCBS_U01_011subclause 9.1.2validmandatoryEnsure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY messagecontaining a Facility information element with a CCBSRequest return error component indicating"shortTermDenial",sends no message and enters the CCBS Idle state.CCBS_U01_012subclause 9.1.2validmandatoryEnsure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY messagecontaining a Facility information element with a CCBSRequest reject component,sends no message and enters the CCBS Idle state.CCBS_U01_013subclause 9.1.2validmandatoryEnsure that the IUT in call state U00 and CCBS Requested state, on expiry of timer T-ACTIVATE,enters the CCBS Idle state.6.2.1.1.2DeactivationCCBS_U02_001subclause 9.2.1validmandatoryEnsure that the IUT in call state U00 and CCBS Activated state, to deactivate a CCBS request,sends a FACILITY message containing a Facility information element with a CCBSDeactivateinvoke component including the cCBSReference parameter and enters the CCBS DeactivationRequested state.CCBS_U02_002subclause 9.2.1validmandatoryEnsure that the IUT in call state U00 and CCBS Activated state, to deactivate a number of CCBSrequests,sends one or more FACILITY messages containing one or more Facility information elements withone or more CCBSDeactivate invoke components including the relevant cCBSReferenceparameters and enters the CCBS Deactivation Requested state.CCBS_U02_003subclause 9.2.1validmandatoryEnsure that the IUT in call state U00 and CCBS Deactivation Requested state, on receipt of a FACILITYmessage containing a Facility information element with a CCBSDeactivate return result component,sends no message, releases the cCBSReference parameter and enters the CCBS Idle state.CCBS_U02_004subclause 9.2.2validmandatoryEnsure that the IUT in call state U00 and CCBS Deactivation Requested state, on receipt of a FACILITYmessage containing a Facility information element with a CCBSDeactivate return error componentindicating "invalidCCBSReference",sends no message, releases its knowledge of the CCBS request identified by the cCBSReferenceparameter and enters CCBS Idle state.SIST ETS 300 359-3:1998



Page 14ETS 300 359-3: October 1996CCBS_U02_005subclause 9.2.2validmandatoryEnsure that the IUT in call state U00 and CCBS Deactivation Requested state, on receipt of a FACILITYmessage containing a Facility information element with a CCBSDeactivate reject component,sends no message, retains knowledge of the CCBS request identified by the cCBSReferenceparameter and enters the CCBS Idle state.CCBS_U02_006subclause 9.2.2validmandatoryEnsure that the IUT in call state U00 and CCBS Deactivation Requested state, on expiry of timerT-DEACTIVATE,sends no message, releases its knowledge of the CCBS request identified by the cCBSReferenceparameter and enters CCBS Idle state.6.2.1.1.3InterrogationCCBS_U03_001subclause 9.3.1.1validoptionalEnsure that the IUT in call state U00 and CCBS Activated state, to perform an interrogation of all CCBSrequests,sends a FACILITY message containing a Facility information element with a CCBSInterrogateinvoke component without a cCBSReference parameter and including a partyNumberOfAparameter and enters the CCBS Interrogation Requested state,orsends a FACILITY message containing a Facility information element with a CCBSInterrogateinvoke component without a cCBSReference parameter and without a partyNumberOfA parameterand enters the CCBS Interrogation Requested state.CCBS_U03_002subclause 9.3.1.1validmandatoryEnsure that the IUT in call state U00 and CCBS Interrogation Requested state, on receipt of a FACILITYmessage containing a Facility information element with a CCBSInterrogate return result componentincluding the recallMode parameter and a list in chronological order of the CCBS requests if any,sends no message, discards details of those requests that are not compatible with its servicecompatibility information and exits the CCBS Interrogation Requested state.CCBS_U03_003subclause 9.3.1.2validmandatoryEnsure that the IUT in call state U00 and CCBS Interrogation Requested state, on receipt of a FACILITYmessage containing a Facility information element with a CCBSInterrogate return error componentindicating "notSubscribed",sends no message and removes knowledge of all CCBS requests and exits the CCBS InterrogationRequested state.CCBS_U03_004subclause 9.3.1.2validmandatoryEnsure that the IUT in call state U00 and CCBS Interrogation Requested state, on receipt of a FACILITYmessage containing a Facility information element with a CCBSInterrogate reject component,sends no message and exits the CCBS Interrogation Requested state.CCBS_U03_005subclause 9.3.2.1validmandatoryEnsure that the IUT in call state U00 and CCBS Activated state, to perform an interrogation of a specificactive CCBS request,sends a FACILITY message containing a Facility information element with a CCBSInterrogateinvoke component including a cCBSReference parameter and enters the CCBS InterrogationRequested state.CCBS_U03_006subclause 9.3.2.1validmandatoryEnsure that the IUT in call state U00 and CCBS Interrogation Requested state, on receipt of a FACILITYmessage containing a Facility information element with a CCBSInterrogate return result componentincluding the recallMode parameter and details of the specific active CCBS request,sends no message and exits the CCBS Interrogation Requested state.CCBS_U03_007subclause 9.3.2.2validmandatoryEnsure that the IUT in call state U00 and CCBS Interrogation Requested state, on receipt of a FACILITYmessage containing a Facility information element with a CCBSInterrogate return error componentindicating "notSubscribed",sends no message and removes knowledge of all CCBS requests identified by the cCBSReferenceparameter and exits the CCBS Interrogation Requested state.SIST ETS 300 359-3:1998



Page 15ETS 300 359-3: October 1996CCBS_U03_008subclause 9.3.2.2validmandatoryEnsure that the IUT in call state U00 and CCBS Interrogation Requested state, on receipt of a FACILITYmessage containing a Facility information element with a CCBSInterrogate return error componentindicating "invalidCCBSReference",sends no message and removes knowledge of the CCBS request identified by the cCBSReferenceparameter and exits the CCBS Interrogation Requested state.CCBS_U03_009subclause 9.3.2.2validmandatoryEnsure that the IUT in call state U00 and CCBS Interrogation Requested state, on receipt of a FACILITYmessage containing a Facility information element with a CCBSInterrogate reject component,sends no message and retains knowledge of the CCBS request identified by the cCBSReferenceparameter and exits the CCBS Interrogation Requested state.CCBS_U03_010subclause 9.3.1.1 and [6] 10.2.4.2validmandatoryEnsure that the IUT in call state U00 and CCBS Interrogation Requested state, on expiry of timerT-INTERROGATE,sends no message and exits the CCBS Interrogation Requested state.6.2.1.1.4Invocation and operationCCBS_U04_001subclauses 9.4.1.1 and 9.7.1validmandatoryEnsure that the IUT in call state U00 and CCBS Activated state, where the IUT has subscribed to theRecall mode option with a value set to "Specific recall", on receipt of a FACILITY message containing aFacility information element with a CCBSRemoteUserFree invoke component including a recallModeparameter indicating "specificRecall", a valid cCBSReference parameter retained by the IUT, theaddressOfB parameter and q931InfoElement parameter,sends no message, retains the cCBSReference parameter and enters the CCBS Free state or mayproceed to establish a call.CCBS_U04_002subclauses 9.4.1.2 and 9.7.1validmandatoryEnsure that the IUT in call state U00 and CCBS Activated state, where the IUT has subscribed to theRecall mode option with a value set to "Specific recall", on receipt of a FACILITY message containing aFacility information element with a CCBSRemoteUserFree invoke component including a recallModeparameter indicating "specificRecall", a cCBSReference parameter not retained by the IUT, theaddressOfB parameter and q931InfoElement parameter,ignores the component and remains in the same state or initiates the deactivation procedure.CCBS_U04_003subclauses 9.4.1.1 and 9.7.1validmandatoryEnsure that the IUT in call state U00 and CCBS Activated state, where the IUT has subscribed to theRecall mode option with a value set to "Global recall", on receipt of a FACILITY message containing aFacility information element with a CCBSRemoteUserFree invoke component including a recallModeparameter indicating "globalRecall", a cCBSReference parameter, an addressOfB parameter and aq931InfoElement parameter containing one or more Bearer capability information elements and one ormore High layer compatibility information elements which are compatible with the IUT according toannex B, subclauses B.3.2 and B.3.3 in ETS 300 102-1[8],sends no message, retains the cCBSReference parameter and enters the CCBS Free state or mayproceed to establish a call.CCBS_U04_004subclauses 9.4.1.2 and 9.7.1validmandatoryEnsure that the IUT in call state U00 and CCBS Activated state, where the IUT has subscribed to theRecall
...

SLOVENSKI STANDARD
SIST ETS 300 359-3:1998
01-junij-1998
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'1'RSROQLOQDVWRULWHY
GRNRQþDQMHNOLFDGR]DVHGHQHJDQDURþQLND&&%63URWRNROGLJLWDOQHQDURþQLãNH
VLJQDOL]DFLMHãW'66GHO=JUDGEDSUHVNXãDOQHJDQL]DLQQDPHQ
SUHVNXãDQMD766 736SHFLILNDFLMD]DXSRUDEQLND
Integrated Services Digital Network (ISDN); Completion of Calls to Busy Subscriber
(CCBS) supplementary service; Digital Subscriber Signalling System No. one (DSS1)
protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the
user
Ta slovenski standard je istoveten z: ETS 300 359-3 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
SIST ETS 300 359-3:1998 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ETS 300 359-3:1998

---------------------- Page: 2 ----------------------

SIST ETS 300 359-3:1998
EUROPEAN ETS 300 359-3
TELECOMMUNICATION October 1996
STANDARD
Source: ETSI TC-SPS Reference: DE/SPS-05061-G-3
ICS: 33.080
Key words: ISDN, DSS1, supplementary service, CCBS, testing, TSS&TP, user
Integrated Services Digital Network (ISDN);
Completion of Calls to Busy Subscriber (CCBS)
supplementary service;
Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 3: Test Suite Structure and Test Purposes (TSS&TP)
specification for the user
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail]
Tel.: [phone] - Fax: [phone]
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.
© European Telecommunications Standards Institute 1996. All rights reserved.

---------------------- Page: 3 ----------------------

SIST ETS 300 359-3:1998
Page 2
ETS 300 359-3: October 1996
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

---------------------- Page: 4 ----------------------

SIST ETS 300 359-3:1998
Page 3
ETS 300 359-3: October 1996
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions.8
3.1 Definitions related to conformance testing.8
3.2 Definitions related to ETS 300 359-1.8
4 Abbreviations.9
5 Test Suite Structure (TSS) .9
6 Test Purposes (TP).10
6.1 Introduction .10
6.1.1 TP naming convention.10
6.1.2 Source of TP definition.10
6.1.3 TP structure.10
6.1.4 Test strategy.11
6.2 User TPs for CCBS.12
6.2.1 User (S/T).12
6.2.1.1 User A.12
6.2.1.1.1 Activation .12
6.2.1.1.2 Deactivation .13
6.2.1.1.3 Interrogation.14
6.2.1.1.4 Invocation and operation.15
6.2.1.1.5 Retention.17
6.2.1.2 User B.18
6.2.1.3 GFP .18
6.2.2 User (T) .18
6.2.2.1 Originating side.19
6.2.2.1.1 General .19
6.2.2.1.2 GFP.21
6.2.2.2 Destination side .21
6.2.2.2.1 General .21
6.2.2.2.2 GFP.24
7 Compliance .25
8 Requirements for a comprehensive testing service .25
History.26

---------------------- Page: 5 ----------------------

SIST ETS 300 359-3:1998
Page 4
ETS 300 359-3: October 1996
Blank page

---------------------- Page: 6 ----------------------

SIST ETS 300 359-3:1998
Page 5
ETS 300 359-3: October 1996
Foreword
This European Telecommunication Standard (ETS) has been produced by the Signalling Protocols and
Switching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).
This ETS is part 3 of a multi-part standard covering the Digital Subscriber Signalling System No. one
(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) Completion of Calls to
Busy Subscriber (CCBS) supplementary service, as described below:
Part 1: "Protocol specification";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) specification for the user";
Part 4: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for
Testing (PIXIT) proforma specification for the user";
Part 5: "TSS&TP specification for the network";
Part 6: "ATS and partial PIXIT proforma specification for the network".
Transposition dates
Date of adoption of this ETS: 4 October 1996
Date of latest announcement of this ETS (doa): 31 January 1997
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 July 1997
Date of withdrawal of any conflicting National Standard (dow): 31 July 1997

---------------------- Page: 7 ----------------------

SIST ETS 300 359-3:1998
Page 6
ETS 300 359-3: October 1996
Blank page

---------------------- Page: 8 ----------------------

SIST ETS 300 359-3:1998
Page 7
ETS 300 359-3: October 1996
1 Scope
This third part of ETS 300 359 specifies the Test Suite Structure and Test Purposes (TSS&TP) for the
User side of the T reference point or coincident S and T reference point (as defined in ITU-T
Recommendation I.411 [7]) of implementations conforming to the stage three standard of the Completion
of Calls to Busy Subscriber (CCBS) supplementary service for the pan-European Integrated Services
Digital Network (ISDN) by means of the Digital Subscriber Signalling System No. one (DSS1) protocol,
ETS 300 359 [1].
A further part of this ETS specifies the Abstract Test Suite (ATS) and partial Protocol Implementation
eXtra Information for Testing (PIXIT) proforma based on this ETS. Other parts specify the TSS&TP and
the ATS and partial PIXIT proforma for the Network side of the T reference point or coincident S and T
reference point of implementations conforming to ETS 300 359-1 [1].
2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] ETS 300 359-1 (1995): "Integrated Services Digital Network (ISDN); Completion
of Calls to Busy Subscriber (CCBS) supplementary service; Digital Subscriber
Signalling System No. one (DSS1) protocol; Part 1: Protocol specification".
[2] ETS 300 359-2 (1995): "Integrated Services Digital Network (ISDN); Completion
of Calls to Busy Subscriber (CCBS) supplementary service; Digital Subscriber
Signalling System No. one (DSS1) protocol; Part 2: Protocol Implementation
Conformance Statement (PICS) proforma specification".
[3] ISO/IEC 9646-1: "Information Technology - OSI Conformance Testing
Methodology and Framework; Part 1: General Concepts".
[4] ISO/IEC 9646-2: "Information Technology - OSI Conformance Testing
Methodology and Framework; Part 2: Abstract Test Suite specification".
[5] ISO/IEC 9646-3: "Information Technology - OSI Conformance Testing
Methodology and Framework; Part 3: The Tree and Tabular Combined
Notation".
[6] ETS 300 196-1 (1993): "Integrated Services Digital Network (ISDN); Generic
functional protocol for the support of supplementary services; Digital Subscriber
Signalling System No. one (DSS1) protocol; Part 1: Protocol specification".
[7] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces -
Reference configurations".
[8] ETS 300 102-1: "Integrated Services Digital Network (ISDN);
User-network interface layer 3; Specifications for basic call control".
[9] ITU-T Recommendation I.112 (1993): "Vocabulary and terms for ISDNs".
[10] CCITT Recommendation E.164 (1991): "Numbering plan for the ISDN era".
[11] ITU-T Recommendation I.210 (1993): "Principles of the telecommunication
services supported by an ISDN and the means to describe them".
[12] ETS 300 196-2 (1996): "Integrated Services Digital Network (ISDN); Generic
functional protocol for the support of supplementary services; Digital Subscriber
Signalling System No. one (DSS1); Part 2: Protocol Implementation
Conformance Statement (PICS) proforma specification".

---------------------- Page: 9 ----------------------

SIST ETS 300 359-3:1998
Page 8
ETS 300 359-3: October 1996
3 Definitions
For the purposes of this ETS, the following definitions apply:
3.1 Definitions related to conformance testing
abstract test case: Refer to ISO/IEC 9646-1 [3].
Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [3].
Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [3].
implicit send event: Refer to ISO/IEC 9646-3 [5].
lower tester: Refer to ISO/IEC 9646-1 [3].
point of control and observation: Refer to ISO/IEC 9646-1 [3].
Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [3].
PICS proforma: Refer to ISO/IEC 9646-1 [3].
Protocol Implementation eXtra Information for Testing (PIXIT): Refer to ISO/IEC 9646-1 [3].
PIXIT proforma: Refer to ISO/IEC 9646-1 [3].
system under test: Refer to ISO/IEC 9646-1 [3].
Test Purpose (TP): Refer to ISO/IEC 9646-1 [3].
3.2 Definitions related to ETS 300 359-1
Call Held auxiliary state: See ETS 300 196-1 [6], subclause 7.1.2.
call reference: See ETS 300 102-1 [8], subclause 4.3.
component: See ETS 300 196-1 [6], subclause 11.2.2.1.
Idle auxiliary state: See ETS 300 196-1 [6], subclause 7.1.2.
Integrated Services Digital Network (ISDN): See ITU-T Recommendation I.112 [9], definition 308.
ISDN number: A number conforming to the numbering and structure specified in CCITT
Recommendation E.164 [10].
invoke component: See ETS 300 196-1 [6], subclause 11.2.2.1.
return error component: See ETS 300 196-1 [6], subclause 11.2.2.1.
return result component: See ETS 300 196-1 [6], subclause 11.2.2.1.
served user: The served user is the user who invokes the CCBS supplementary service.
service; telecommunication service: See ITU-T Recommendation I.112 [9], definition 201.
supplementary service: See ITU-T Recommendation I.210 [11], subclause 2.4.
user: The DSS1 protocol entity at the User side of the user-network interface where a T reference point or
coincident S and T reference point applies.

---------------------- Page: 10 ----------------------

SIST ETS 300 359-3:1998
Page 9
ETS 300 359-3: October 1996
user (S/T): The DSS1 protocol entity at the User side of the user-network interface where a coincident
S and T reference point applies.
user (T): The DSS1 protocol entity at the User side of the user-network interface where a T reference
point applies (User is the Private ISDN).
4 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
ATM Abstract Test Method
ATS Abstract Test Suite
CCBS Completion of Calls to Busy Subscriber
CR Call Reference
CR1 normal (bearer related) CR
CR2 CR used for bearer independent transport mechanism
DSS1 Digital Subscriber Signalling System No. one
GFP Generic Functional Protocol
ISDN Integrated Services Digital Network
IUT Implementation Under Test
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
TP Test Purpose
TSS Test Suite Structure
U00 Null call state
U01 Call Initiated call state
U03 Outgoing Call Proceeding call state
U04 Call Delivered call state
U06 Call Present call state
U07 Call Received call state
U08 Connect Request call state
U09 Incoming Call Proceeding call state
U10 Active call state
U12 Disconnect Indication call state
U25 Overlap Receiving call state
U31 Bearer Independent Transport call state
UI Unnumbered Information
5 Test Suite Structure (TSS)
CCBS - User
User (S/T) User (T)
User A User B GFP Originating Destination
(06) (07) side side
General GFP General GFP
(08) (09) (10) (11)
Activation Deactivation Interrogation Invocation and Retention
(01) (02) (03) operation (05)
(04)
NOTE: Numbers in brackets represent group numbers and are used in TP identifiers.
Figure 1: Test suite structure

---------------------- Page: 11 ----------------------

SIST ETS 300 359-3:1998
Page 10
ETS 300 359-3: October 1996
6 Test Purposes (TP)
6.1 Introduction
For each test requirement a TP is defined.
6.1.1 TP naming convention
TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS.
Additional references are added to identify the actual test suite and whether it applies to the network or the
user (see table 1).
Table 1: TP identifier naming convention scheme
Identifier: __
= supplementary service: e.g. "CCBS"
= type of IUT: U User
N Network
= group 2 digit field representing group reference according to TSS
= sequential number (001-999)
6.1.2 Source of TP definition
The TPs are based on ETS 300 359-1 [1].
6.1.3 TP structure
Each TP has been written in a manner which is consistent with all other TPs. The intention of this is to
make the TPs more readable and checkable. A particular structure has been used and this is illustrated in
table 2. This table should be read in conjunction with any TP, i.e. use a TP as an example to fully
understand the table.

---------------------- Page: 12 ----------------------

SIST ETS 300 359-3:1998
Page 11
ETS 300 359-3: October 1996
Table 2: Structure of a single TP
TP part Text Example
Header tab see table 1
tab subclause 0.0.0
tab valid, invalid, inopportune
CR. mandatory, optional, conditional
Stimulus Ensure that the IUT in the
U10, U12, etc.
and CCBS Idle state
see below for message structure receiving a XXXX message
or to request a .
Reaction sends, saves, does, etc.
using en-bloc sending, .
if the action is sending
  see below for message structure
, etc.
and enters
and/or and remains in the same call state(s)
or and enters call state
Message SETUP, FACILITY, CONNECT, .
message containing a
structure
a) Bearer capability, Facility, .
information element with
b) a
encoded as or including
and back to a or b,
NOTE: Text in italics will not appear in TPs and text between <> is filled in for each TP and may
differ from one TP to the next.
6.1.4 Test strategy
As the base standard ETS 300 359-1 [1] contains no explicit requirements for testing, the TPs were
generated as a result of an analysis of the base standard and the PICS specification ETS 300 359-2 [2].
The criteria applied included the following:
- only the requirements from the point of view of the T or coincident S and T reference point are
considered;
- whether or not a test case can be built from the TP is not considered.

---------------------- Page: 13 ----------------------

SIST ETS 300 359-3:1998
Page 12
ETS 300 359-3: October 1996
6.2 User TPs for CCBS
6.2.1 User (S/T)
Selection: IUT supports coincident S and T reference point procedures. PICS: R 3.2.
NOTE: Unless stated otherwise, all FACILITY messages in TPs in this subclause use the
dummy call reference as specified in subclause 8.3.2.2 of ETS 300 196-1 [6] (bearer
independent connectionless transport mechanism). Where an Unnumbered
Information (UI) frame is specified for a FACILITY message, the message is sent or
received using broadcast procedures; otherwise point-to-point procedures are used.
6.2.1.1 User A
6.2.1.1.1 Activation
CCBS_U01_001 subclause 9.1.1 valid mandatory
Ensure that the IUT in call state U12 and CCBS Idle state, having been informed that the network is
performing the Call Information Retention procedure, to activate the CCBS supplementary service,
sends a FACILITY message containing a Facility information element with a CCBSRequest invoke
component including the callLinkageID parameter and enters the CCBS Requested state before
expiry of timer T-RETENTION.
CCBS_U01_002 subclause 9.1.1 valid mandatory
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message
containing a Facility information element with a CCBSRequest return result component including a
recallMode parameter indicating "specificRecall",
sends no message but retains the CCBSReference and enters CCBS Activated state.
CCBS_U01_003 subclause 9.1.1 valid optional
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message
containing a Facility information element with a CCBSRequest return result component including a
recallMode parameter indicating "globalRecall",
sends no message, retains the cCBSReference parameter and enters CCBS Activated state,
or
sends no message, releases the cCBSReference parameter and remains in the CCBS Requested
state.
CCBS_U01_004 subclause 9.1.2 valid mandatory
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message
containing a Facility information element with a CCBSRequest return error component indicating
"invalidCallLinkageID",
sends no message, releases the callLinkageID parameter and enters CCBS Idle state.
CCBS_U01_005 subclause 9.1.2 valid mandatory
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message
containing a Facility information element with a CCBSRequest return error component indicating
"notSubscribed",
sends no message and enters the CCBS Idle state.
CCBS_U01_006 subclause 9.1.2 valid mandatory
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message
containing a Facility information element with a CCBSRequest return error component indicating
"callFailureReasonNotBusy",
sends no message and enters the CCBS Idle state.
CCBS_U01_007 subclause 9.1.2 valid mandatory
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message
containing a Facility information element with a CCBSRequest return error component indicating
"outgoingCCBSQueueFull",
sends no message and enters the CCBS Idle state.

---------------------- Page: 14 ----------------------

SIST ETS 300 359-3:1998
Page 13
ETS 300 359-3: October 1996
CCBS_U01_008 subclause 9.1.2 valid mandatory
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message
containing a Facility information element with a CCBSRequest return error component indicating
"cCBSIsAlreadyActivated",
sends no message and enters the CCBS Idle state.
CCBS_U01_009 subclause 9.1.2 valid mandatory
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message
containing a Facility information element with a CCBSRequest return error component indicating
"supplementaryServiceInteractionNotAllowed",
sends no message and enters the CCBS Idle state.
CCBS_U01_010 subclause 9.1.2 valid mandatory
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message
containing a Facility information element with a CCBSRequest return error component indicating
"longTermDenial",
sends no message and enters the CCBS Idle state.
CCBS_U01_011 subclause 9.1.2 valid mandatory
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message
containing a Facility information element with a CCBSRequest return error component indicating
"shortTermDenial",
sends no message and enters the CCBS Idle state.
CCBS_U01_012 subclause 9.1.2 valid mandatory
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message
containing a Facility information element with a CCBSRequest reject component,
sends no message and enters the CCBS Idle state.
CCBS_U01_013 subclause 9.1.2 valid mandatory
Ensure that the IUT in call state U00 and CCBS Requested state, on expiry of timer T-ACTIVATE,
enters the CCBS Idle state.
6.2.1.1.2 Deactivation
CCBS_U02_001 subclause 9.2.1 valid mandatory
Ensure that the IUT in call state U00 and CCBS Activated state, to deactivate a CCBS request,
sends a FACILITY message containing a Facility information element with a CCBSDeactivate
invoke component including the cCBSReference parameter and enters the CCBS Deactivation
Requested state.
CCBS_U02_002 subclause 9.2.1 valid mandatory
Ensure that the IUT in call state U00 and CCBS Activated state, to deactivate a number of CCBS
requests,
sends one or more FACILITY messages containing one or more Facility information elements with
one or more CCBSDeactivate invoke components including the relevant cCBSReference
parameters and enters the CCBS Deactivation Requested state.
CCBS_U02_003 subclause 9.2.1 valid mandatory
Ensure that the IUT in call state U00 and CCBS Deactivation Requested state, on receipt of a FACILITY
message containing a Facility information element with a CCBSDeactivate return result component,
sends no message, releases the cCBSReference parameter and enters the CCBS Idle state.
CCBS_U02_004 subclause 9.2.2 valid mandatory
Ensure that the IUT in call state U00 and CCBS Deactivation Requested state, on receipt of a FACILITY
message containing a Facility information element with a CCBSDeactivate return error component
indicating "invalidCCBSReference",
sends no message, releases its knowledge of the CCBS request identified by the cCBSReference
parameter and enters CCBS Idle state.

---------------------- Page: 15 ----------------------

SIST ETS 300 359-3:1998
Page 14
ETS 300 359-3: October 1996
CCBS_U02_005 subclause 9.2.2 valid mandatory
Ensure that the IUT in call state U00 and CCBS Deactivation Requested state, on receipt of a FACILITY
message containing a Facility information element with a CCBSDeactivate reject component,
sends no message, retains knowledge of the CCBS request identified by the cCBSReference
parameter and enters the CCBS Idle state.
CCBS_U02_006 subclause 9.2.2 valid mandatory
Ensure that the IUT in call state U00 and CCBS Deactivation Requested state, on expiry of timer
T-DEACTIVATE,
sends no message, releases its knowledge of the CCBS request identified by the cCBSReference
parameter and enters CCBS Idle state.
6.2.1.1.3 Interrogation
CCBS_U03_001 subclause 9.3.1.1 valid optional
Ensure that the IUT in call state U00 and CCBS Activated state, to perform an interrogation of all CCBS
requests,
sends a FACILITY message containing a Facility information element with a CCBSInterrogate
invoke component without a cCBSReference parameter and including a partyNumberOfA
parameter and enters the CCBS Interrogation Requested state,
or
sends a FACILITY message containing a Facility information element with a CCBSInterrogate
invoke component without a cCBSReference parameter and without a partyNumberOfA parameter
and enters the CCBS Interrogation Requested state.
CCBS_U03_002 subclause 9.3.1.1 valid mandatory
Ensure that the IUT in call state U00 and CCBS Interrogation Requested state, on receipt of a FACILITY
message containing a Facility information element with a CCBSInterrogate return result component
including the recallMode parameter and a list in chronological order of the CCBS requests if any,
sends no message, discards details of those requests that are not compatible with its service
compatibility information and exits the CCBS Interrogation Requested state.
CCBS_U03_003 subclause 9.3.1.2 valid mandatory
Ensure that the IUT in call state U00 and CCBS Interrogation Requested state, on receipt of a FACILITY
message containing a Facility information element with a CCBSInterrogate return error component
indicating "notSubscribed",
sends no message and removes knowledge of all CCBS requests and exits the CCBS Interrogation
Requested state.
CCBS_U03_004 subclause 9.3.1.2 valid mandatory
Ensure that the IUT in call state U00 and CCBS Interrogation Requested state, on receipt of a FACILITY
message containing a Facility information element with a CCBSInterrogate reject component,
sends no message and exits the CCBS Interrogation Requested state.
CCBS_U03_005 subclause 9.3.2.1 valid mandatory
Ensure that the IUT in call state U00 and CCBS Activated state, to perform an interrogation of a specific
active CCBS request,
sends a FACILITY message containing a Facility information element with a CCBSInterrogate
invoke component including a cCBSReference parameter and enters the CCBS Interrogation
Requested state.
CCBS_U03_006 subclause 9.3.2.1 valid mandatory
Ensure that the IUT in call state U00 and CCBS Interrogation Requested state, on receipt of a FACILITY
message containing a Facility information element with a CCBSInterrogate return result component
including the recallMode parameter and details of the specific active CCBS request,
sends no message and exits the CCBS Interrogation Requested state.
CCBS_U03_007 subclause 9.3.2.2 valid mandatory
Ensure that the IUT in call state U00 and CCBS Interrogation Requested state, on receipt of a FACILITY
message containing a Facility information element with a CCBSInterrogate return error component
indicating "notSubscribed",
sends no message and removes knowledge of all CCBS requests identified by the cCBSReference
parameter and exits the CCBS Interrogation Requested state.

---------------------- Page: 16 ----------------------

SIST ETS 300 359-3:1998
Page 15
ETS 300 359-3: October 1996
CCBS_U03_008 subclause 9.3.2.2 valid mandatory
Ensure that the IUT in call state U00 and CCBS Interrogation Requested state, on receipt of a FACILITY
message containing a Facility information element with a CCBSInterrogate return error component
indicating "invalidCCBSReference",
sends no message and removes knowledge of the CCBS request identified by the cCBSReference
parameter and exits the CCBS Interrogation Requested state.
CCBS_U03_009 subclause 9.3.2.2 valid mandatory
Ensure that the IUT in call state U00 and CCBS Interrogation Requested state, on receipt of a FACILITY
message containing a Facility information element with a CCBSInterrogate reject component,
sends no message and retains knowledge of the CCBS request identified by the cCBSReference
parameter and exits the CCBS Interrogation Requested state.
CCBS_U03_010 subclause 9.3.1.1 and [6] 10.2.4.2 valid mandatory
Ensure that the IUT in call state U00 and CCBS Interrogation Requested state, on expiry of timer
T-INTERROGATE,
sends no message and exits the CCBS Interrogation Requested state.
6.2.1.1.4 Invocation and operation
CCBS_U04_001 subclauses 9.4.1.1 and 9.7.1 valid mandatory
Ensure that the IUT in call state U00 and CCBS Activated state, where the IUT has subscribed to the
Recall mode option with a value set to "Specific reca
...