SIST EN 301 065-3:2001
(Main)Integrated Services Digital Network (ISDN); Completion of Calls on No Reply (CCNR) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user
Integrated Services Digital Network (ISDN); Completion of Calls on No Reply (CCNR) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user
Test specification for DE/SPS-05115-1
Digitalno omrežje z integriranimi storitvami (ISDN) - Dopolnilna storitev: dokončanje klicanja, ko ni odziva (CCNR) - 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
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.VWRULWHYRþQLãNHIntegrated Services Digital Network (ISDN); Completion of Calls on No Reply (CCNR) 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:EN 301 065-3 V1.1.33SIST EN 301 065-3:en01-GHFHPEHU3SIST EN 301 065-3:SLOVENSKI
STANDARD
SIST EN 301 065-3:2001
EN 301 065-3 V1.1.3 (1998-10)European Standard (Telecommunications series)Integrated Services Digital Network (ISDN);Completion of Calls on No Reply (CCNR)supplementary service;Digital Subscriber Signalling System No. one (DSS1) protocol;Part 3: Test Suite Structure and Test Purposes (TSS&TP)specification for the userSIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)2ReferenceDEN/SPS-05115-3 (9v0r0ie0.PDF)KeywordsISDN, DSS1, supplementary service, CCNR,testing, TSS&TP, userETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frhttp://www.etsi.orgCopyright NotificationNo 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 1998.All rights reserved.SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)3ContentsIntellectual Property Rights.4Foreword.41Scope.52Normative references.53Definitions and abbreviations.63.1Definitions.63.1.1Definitions related to conformance testing.63.1.2Definitions related to EN 301 065-1.63.2Abbreviations.74Test Suite Structure (TSS).85Test Purposes (TP).85.1Introduction.85.1.1TP naming convention.85.1.2Source of TP definition.85.1.3TP structure.95.1.4Test strategy.95.2User TPs for CCNR.95.2.1Signalling procedures at the coincident S and T reference point.105.2.1.1Activation.105.2.1.2Deactivation.115.2.1.3Interrogation.115.2.1.3.1General interrogation.115.2.1.3.2Specific interrogation.125.2.1.4Invocation and operation.135.2.1.4.1Recall indication.135.2.1.4.2CCNR call request.135.2.1.4.3Network initiated deactivation procedure.145.2.1.4.4B free but A busy procedure.145.2.1.4.5User A monitoring procedure.145.2.1.5Call information retention.155.2.2Procedures for interworking with private ISDNs.155.2.2.1Procedures for the originating T reference point.155.2.2.2Procedures for the destination T reference point.176Compliance.197Requirements for a comprehensive testing service.19History.20SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)4Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on theETSI Web server (http://www.etsi.fr/ipr or http://www.etsi.org/ipr).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical Committee SignallingProtocols and Switching (SPS).The present document 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 on No Reply(CCNR) 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:"Test Suite Structure and Test Purposes (TSS&TP) specification for the network";Part 6:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)proforma specification for the network".National transposition datesDate of adoption of this EN:9 October 1998Date of latest announcement of this EN (doa):31 January 1999Date of latest publication of new National Standardor endorsement of this EN (dop/e):31 July 1999Date of withdrawal of any conflicting National Standard (dow):31 July 1999SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)51ScopeThis third part of EN 301 065 specifies the Test Suite Structure and Test Purposes (TSS&TP) for the User side of theT reference point or coincident S and T reference point (as defined in ITU-T Recommendation I.411 [7]) ofimplementations conforming to the stage three standard for the Completion of Calls on No Reply (CCNR)supplementary service for the pan-European Integrated Services Digital Network (ISDN) by means of the DigitalSubscriber Signalling System No. one (DSS1) protocol, EN 301 065-1 [1].A further part of the present document specifies the Abstract Test Suite (ATS) and partial PIXIT proforma based on thepresent document. Other parts specify the TSS&TP and the ATS and partial PIXIT proforma for the Network side of theT reference point or coincident S and T reference point of implementations conforming to EN 301 065-1 [1].2Normative referencesReferences may be made to:a)specific versions of publications (identified by date of publication, edition number, version number, etc.), inwhich case, subsequent revisions to the referenced document do not apply; orb)all versions up to and including the identified version (identified by "up to and including" before the versionidentity); orc)all versions subsequent to and including the identified version (identified by "onwards" following the versionidentity); ord)publications without mention of a specific version, in which case the latest version applies.A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.[1]EN 301 065-1 (V1.1): "Integrated Services Digital Network (ISDN); Completion of Calls on NoReply (CCNR) supplementary service; Digital Subscriber Signalling System No. one (DSS1)protocol; Part 1: Protocol specification".[2]EN 301 065-2 (V1.1): "Integrated Services Digital Network (ISDN); Completion of Calls on NoReply (CCNR) supplementary service; Digital Subscriber Signalling System No. one (DSS1)protocol; Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification".[3]ISO/IEC 9646-1 (1994): "Information technology; Open Systems Interconnection; Conformancetesting methodology and framework; Part 1: General concepts".[4]ISO/IEC 9646-2 (1994): "Information technology; Open Systems Interconnection; Conformancetesting methodology and framework; Part 2: Abstract test suite specification".[5]ISO/IEC 9646-3 (1992): "Information technology; Open Systems Interconnection; Conformancetesting methodology and framework; Part 3: The Tree and Tabular Combined Notation (TTCN)".[6]EN 300 196-1: "Integrated Services Digital Network (ISDN); Generic functional protocol for thesupport 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]EN 300 403-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 1:Protocol specification [ITU-T Recommendation Q.931 (1993), modified]".[9]ITU-T Recommendation I.112 (1993): "Vocabulary of terms for ISDNs".[10]CCITT Recommendation E.164 (1997): "The international public telecommunication numberingplan".SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)6[11]ITU-T Recommendation I.210 (1993): "Principles of the telecommunication services supported byan ISDN and the means to describe them".[12]EN 300 403-3: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 3:Protocol Implementation Conformance Statement (PICS) proforma specification".3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the following definitions apply:3.1.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].active test: a test case where the IUT is required to send a particular message, but not in reaction to a received message.This would usually involve the use of PIXIT information to see how this message can be generated and quite often isspecified in an ATS using an implicit send event.Implementation Under Test (IUT): refer to ISO/IEC 9646-1 [3].implicit send event: refer to ISO/IEC 9646-3 [5].Lower Tester (LT): refer to ISO/IEC 9646-1 [3].passive test: a test case where the IUT is required to respond to a protocol event (e.g. received message) with anotherprotocol event (e.g. send message) which normally does not require any special operator intervention as associated withthe implicit send event.Point of Control and Observation (PCO): 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 (SUT): refer to ISO/IEC 9646-1 [3].Test Purpose (TP): refer to ISO/IEC 9646-1 [3].3.1.2Definitions related to EN 301 065-1component: see EN 300 196-1 [6], subclause 11.2.2.1.dummy call reference: see EN 300 403-1 [8], subclause 4.3.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 EN 300 196-1 [6], subclause 11.2.2.1.return error component: see EN 300 196-1 [6], subclause 11.2.2.1.SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)7return result component: see EN 300 196-1 [6], subclause 11.2.2.1.service; telecommunication service: see ITU-T Recommendation I.112 [9], definition 201.supplementary service: see ITU-T Recommendation I.210 [11], subclause 2.4.S/T: the DSS1 protocol entity at the User side of the user-network interface where a coincident S and T reference pointapplies.T: the DSS1 protocol entity at the User side of the user-network interface where a T reference point applies (User is aPrivate ISDN).3.2AbbreviationsFor the purposes of the present document, the following abbreviations apply:ATSAbstract Test SuiteCCNRCompletion of Calls on No ReplyISDNIntegrated Services Digital NetworkIUTImplementation Under TestPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingTPTest PurposeTSSTest Suite StructureU0Null call stateU3Outgoing Call Proceeding call stateU4Call Delivered call stateU7Call Received call stateU10Active call stateU11Disconnect Request call stateU19Release Request call stateU31Bearer Independent Transport call stateSIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)84Test Suite Structure (TSS)Signalling procedures at the coincident S and T reference pointGroupActivationU01DeactivationU02General interrogationU03Specific interrogationU04Recall indicationU05CCNR call requestU06Network initiated deactivation procedureU07B free but A busy procedureU08User A monitoring procedureU09Call information retentionU10Procedures for interworking with private ISDNsProcedures for the originating T reference pointU11Procedures for the destination T reference pointU12Figure 1: Test suite structure5Test Purposes (TP)5.1IntroductionFor each test requirement a TP is defined.5.1.1TP naming conventionTPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional referencesare 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 schemeIdentifier:__=supplementary service: "CCNR"=type of IUT:UUserNNetwork=group2 digit field representing group reference according to TSS=sequential number(001-999)5.1.2Source of TP definitionThe TPs are based on EN 301 065-1 [1].SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)95.1.3TP structureEach TP has been written in a manner which is consistent with all other TPs. The intention of this is to make the TPsmore readable and checkable. A particular structure has been used and this is illustrated in table 2. This table should beread in conjunction with any TP, i.e. use a TP as an example to fully understand the table.Table 2: Structure of a single TP for CCNRTP partTextExampleHeader tabsee table 1 tabsubclause 0.0.0 CR.mandatory, optional (see note 1)StimulusEnsure that the IUT in the or U10 etc. 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 remains in the same stateor and enters 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 1:Mandatory test purpose are always applicable. Optional test purposes are applicable according to theconfiguration options of the IUT. If the configuration option is covered by a PICS item, a selection criteriais indicated, else the selection of the corresponding test cases will depend on test suite parameters(PIXIT) in the ATS.NOTE 2:Text in italics will not appear in TPs and text between <> is filled in for each TP and may differ from oneTP to the next.5.1.4Test strategyAs the base standard EN 301 065-1 [1] contains no explicit requirements for testing, the TPs were generated as a resultof an analysis of the base standard and the PICS specification EN 301 065-2 [2]. The criteria applied include thefollowing:-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.5.2User TPs for CCNRAll PICS items referred to in this subclause are as specified in EN 301 065-2 [2] unless indicated otherwise by anothernumbered reference.Unless specified:-The messages indicated are valid and contain at least the mandatory information elements and possibly optionalinformation elements.-The information elements indicated are valid and contain at least the mandatory parameters and possibly optionalparameters.SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)105.2.1Signalling procedures at the coincident S and T reference pointSelection:IUT supports coincident S/T reference point procedures. PICS: R 3.1.NOTE:The signalling procedures at the coincident S and T reference point use mainly the bearer-independentconnectionless transport mechanism using the dummy call reference. To augment the readability of thetest purposes, basic call states are only mentioned where significant.5.2.1.1ActivationNOTE:The IUT may be in call state U4, U11 or U0 when requesting the activation of CCNR.CCNR_U01_001subclause 9.1.1mandatoryEnsure that the IUT in the CCNR Idle state, having received an ALERTING message with a Facility informationelement including a CallInfoRetain invoke component with callLinkageID parameter, to activate the CCNRsupplementary service,sends a FACILITY message with the dummy call reference containing a Facility information element with aCCNRRequest invoke component including the callLinkageID parameter and enters the CCNR Requested state.CCNR_U01_002subclause 9.1.1mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a CCNRRequest return result component including the cCBSReferenceparameter and the recallMode parameter indicating "specificRecall",sends no message, retains the CCBS Reference and enters the CCNR Activated state.CCNR_U01_003subclause 9.1.1mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a CCNRRequest return result component including the cCBSReferenceparameter and the recallMode parameter indicating "globalRecall",sends no message, retains the CCBS Reference and enters the CCNR Activated stateorsends no message, releases the CCBS Reference and enters the CCNR Idle state.CCNR_U01_004subclause 9.1.2mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a CCNRRequest return error component indicating "notSubscribed",sends no message and enters the CCNR Idle state.CCNR_U01_005subclause 9.1.2mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a CCNRRequest return error component indicating"invalidCallLinkageID",sends no message and releases the callLinkageID parameter.CCNR_U01_006subclause 9.1.2mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a CCNRRequest return error component indicating"outgoingCCBSQueueFull",sends no message and enters the CCNR Idle state.CCNR_U01_007subclause 9.1.2mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a CCNRRequest return error component indicating"cCBSIsAlreadyActivated",sends no message and enters the CCNR Idle state.CCNR_U01_008subclause 9.1.2mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a CCNRRequest return error component indicating"supplementaryServiceInteractionNotAllowed",sends no message and enters the CCNR Idle state.SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)11CCNR_U01_009subclause 9.1.2mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a CCNRRequest return error component indicating "longTermDenial",sends no message and enters the CCNR Idle state.CCNR_U01_010subclause 9.1.2mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a CCNRRequest return error component indicating "shortTermDenial",sends no message and enters the CCNR Idle state.CCNR_U01_011subclause 9.1.2mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a reject component including the invoke identifier,sends no message and enters the CCNR Idle state.CCNR_U01_012subclause 9.1.2mandatoryEnsure that the IUT in the CCNR Requested state, on the expiry of timer T-ACTIVATE,sends no message and enters the CCNR Idle state.5.2.1.2DeactivationCCNR_U02_001subclause 9.2.1mandatoryEnsure that the IUT in the CCNR Activated state, to deactivate the CCNR supplementary service,sends a FACILITY message with the dummy call reference containing a Facility information element with aCCBSDeactivate invoke component including the cCBSReference parameter and enters the CCNR DeactivationRequested state.CCNR_U02_002subclause 9.2.1mandatoryEnsure that the IUT in the CCNR Deactivation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a CCBSDeactivate return result component,sends no message, releases the CCBS Reference and enters the CCNR Idle state.CCNR_U02_003subclause 9.2.2mandatoryEnsure that the IUT in the CCNR Deactivation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a CCBSDeactivate return error component indicating"invalidCCBSReference",sends no message, releases the CCBS Reference and enters the CCNR Idle state.CCNR_U02_004subclause 9.2.2mandatoryEnsure that the IUT in the CCNR Deactivation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a reject component including the invoke identifier,sends no message, retains the CCBS Reference and enters the CCNR Idle state.5.2.1.3Interrogation5.2.1.3.1General interrogationCCNR_U03_001subclause 9.3.1.1mandatoryEnsure that the IUT, to perform an interrogation of all CCNR requests,sends a FACILITY message with the dummy call reference containing a Facility information element with aCCNRInterrogate invoke component without a cCBSReference parameter and enters the CCNR InterrogationRequested state.CCNR_U03_002subclause 9.3.1.1mandatoryEnsure that the IUT in the CCNR Interrogation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a CCNRInterrogate return result component,sends no message and exits the CCNR Interrogation Requested state.SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)12CCNR_U03_003subclause 9.3.1.2mandatoryEnsure that the IUT in the CCNR Interrogation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a CCNRInterrogate return error component indicating"notSubscribed",sends no message, removes knowledge of all CCNR requests and exits the CCNR Interrogation Requested state.CCNR_U03_004subclause 9.3.1.2mandatoryEnsure that the IUT in the CCNR Interrogation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a reject component including the invoke identifier,sends no message and exits the CCNR Interrogation Requested state.CCNR_U03_005subclause 9.3.1.2mandatoryEnsure that the IUT in the CCNR Interrogation Requested state, on the expiry of timer T-ACTIVATE,sends no message and exits the CCNR Interrogation Requested state.5.2.1.3.2Specific interrogationCCNR_U04_001subclause 9.3.2.1mandatoryEnsure that the IUT, to perform an interrogation of a specific CCNR requests,sends a FACILITY message with the dummy call reference containing a Facility information element with aCCNRInterrogate invoke component with the cCBSReference parameter and enters the CCNR InterrogationRequested state.CCNR_U04_002subclause 9.3.2.1mandatoryEnsure that the IUT in the CCNR Interrogation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a CCNRInterrogate return result component,sends no message and exits the CCNR Interrogation Requested state.CCNR_U04_003subclause 9.3.2.2mandatoryEnsure that the IUT in the CCNR Interrogation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a CCNRInterrogate return error component indicating"notSubscribed",sends no message, removes knowledge of all CCNR requests and exits the CCNR Interrogation Requested state.CCNR_U04_004subclause 9.3.2.2mandatoryEnsure that the IUT in the CCNR Interrogation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a CCNRInterrogate return error component indicating"invalidCCBS Reference",sends no message, removes knowledge of the specific CCNR request and exits the CCNR InterrogationRequested state.CCNR_U04_005subclause 9.3.2.2mandatoryEnsure that the IUT in the CCNR Interrogation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a reject component including the invoke identifier,sends no message, retains knowledge of the specific CCNR request and exits the CCNR Interrogation Requestedstate.CCNR_U04_006subclause 9.3.2.2mandatoryEnsure that the IUT in the CCNR Interrogation Requested state, on the expiry of timer T-ACTIVATE,sends no message and exits the CCNR Interrogation Requested state.SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)135.2.1.4Invocation and operation5.2.1.4.1Recall indicationCCNR_U05_001subclause 9.4.1.1, 9.7mandatoryEnsure that the IUT in the CCNR Activated state, where
...
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.VWRULWHYRþQLãNHIntegrated Services Digital Network (ISDN); Completion of Calls on No Reply (CCNR) 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:EN 301 065-3 Version 1.1.3SIST EN 301 065-3:2001en01-februar-2001SIST EN 301 065-3:2001SLOVENSKI
STANDARD
SIST EN 301 065-3:2001
EN 301 065-3 V1.1.3 (1998-10)European Standard (Telecommunications series)Integrated Services Digital Network (ISDN);Completion of Calls on No Reply (CCNR)supplementary service;Digital Subscriber Signalling System No. one (DSS1) protocol;Part 3: Test Suite Structure and Test Purposes (TSS&TP)specification for the userSIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)2ReferenceDEN/SPS-05115-3 (9v0r0ie0.PDF)KeywordsISDN, DSS1, supplementary service, CCNR,testing, TSS&TP, userETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frhttp://www.etsi.orgCopyright NotificationNo 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 1998.All rights reserved.SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)3ContentsIntellectual Property Rights.4Foreword.41Scope.52Normative references.53Definitions and abbreviations.63.1Definitions.63.1.1Definitions related to conformance testing.63.1.2Definitions related to EN 301 065-1.63.2Abbreviations.74Test Suite Structure (TSS).85Test Purposes (TP).85.1Introduction.85.1.1TP naming convention.85.1.2Source of TP definition.85.1.3TP structure.95.1.4Test strategy.95.2User TPs for CCNR.95.2.1Signalling procedures at the coincident S and T reference point.105.2.1.1Activation.105.2.1.2Deactivation.115.2.1.3Interrogation.115.2.1.3.1General interrogation.115.2.1.3.2Specific interrogation.125.2.1.4Invocation and operation.135.2.1.4.1Recall indication.135.2.1.4.2CCNR call request.135.2.1.4.3Network initiated deactivation procedure.145.2.1.4.4B free but A busy procedure.145.2.1.4.5User A monitoring procedure.145.2.1.5Call information retention.155.2.2Procedures for interworking with private ISDNs.155.2.2.1Procedures for the originating T reference point.155.2.2.2Procedures for the destination T reference point.176Compliance.197Requirements for a comprehensive testing service.19History.20SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)4Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on theETSI Web server (http://www.etsi.fr/ipr or http://www.etsi.org/ipr).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical Committee SignallingProtocols and Switching (SPS).The present document 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 on No Reply(CCNR) 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:"Test Suite Structure and Test Purposes (TSS&TP) specification for the network";Part 6:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)proforma specification for the network".National transposition datesDate of adoption of this EN:9 October 1998Date of latest announcement of this EN (doa):31 January 1999Date of latest publication of new National Standardor endorsement of this EN (dop/e):31 July 1999Date of withdrawal of any conflicting National Standard (dow):31 July 1999SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)51ScopeThis third part of EN 301 065 specifies the Test Suite Structure and Test Purposes (TSS&TP) for the User side of theT reference point or coincident S and T reference point (as defined in ITU-T Recommendation I.411 [7]) ofimplementations conforming to the stage three standard for the Completion of Calls on No Reply (CCNR)supplementary service for the pan-European Integrated Services Digital Network (ISDN) by means of the DigitalSubscriber Signalling System No. one (DSS1) protocol, EN 301 065-1 [1].A further part of the present document specifies the Abstract Test Suite (ATS) and partial PIXIT proforma based on thepresent document. Other parts specify the TSS&TP and the ATS and partial PIXIT proforma for the Network side of theT reference point or coincident S and T reference point of implementations conforming to EN 301 065-1 [1].2Normative referencesReferences may be made to:a)specific versions of publications (identified by date of publication, edition number, version number, etc.), inwhich case, subsequent revisions to the referenced document do not apply; orb)all versions up to and including the identified version (identified by "up to and including" before the versionidentity); orc)all versions subsequent to and including the identified version (identified by "onwards" following the versionidentity); ord)publications without mention of a specific version, in which case the latest version applies.A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.[1]EN 301 065-1 (V1.1): "Integrated Services Digital Network (ISDN); Completion of Calls on NoReply (CCNR) supplementary service; Digital Subscriber Signalling System No. one (DSS1)protocol; Part 1: Protocol specification".[2]EN 301 065-2 (V1.1): "Integrated Services Digital Network (ISDN); Completion of Calls on NoReply (CCNR) supplementary service; Digital Subscriber Signalling System No. one (DSS1)protocol; Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification".[3]ISO/IEC 9646-1 (1994): "Information technology; Open Systems Interconnection; Conformancetesting methodology and framework; Part 1: General concepts".[4]ISO/IEC 9646-2 (1994): "Information technology; Open Systems Interconnection; Conformancetesting methodology and framework; Part 2: Abstract test suite specification".[5]ISO/IEC 9646-3 (1992): "Information technology; Open Systems Interconnection; Conformancetesting methodology and framework; Part 3: The Tree and Tabular Combined Notation (TTCN)".[6]EN 300 196-1: "Integrated Services Digital Network (ISDN); Generic functional protocol for thesupport 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]EN 300 403-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 1:Protocol specification [ITU-T Recommendation Q.931 (1993), modified]".[9]ITU-T Recommendation I.112 (1993): "Vocabulary of terms for ISDNs".[10]CCITT Recommendation E.164 (1997): "The international public telecommunication numberingplan".SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)6[11]ITU-T Recommendation I.210 (1993): "Principles of the telecommunication services supported byan ISDN and the means to describe them".[12]EN 300 403-3: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 3:Protocol Implementation Conformance Statement (PICS) proforma specification".3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the following definitions apply:3.1.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].active test: a test case where the IUT is required to send a particular message, but not in reaction to a received message.This would usually involve the use of PIXIT information to see how this message can be generated and quite often isspecified in an ATS using an implicit send event.Implementation Under Test (IUT): refer to ISO/IEC 9646-1 [3].implicit send event: refer to ISO/IEC 9646-3 [5].Lower Tester (LT): refer to ISO/IEC 9646-1 [3].passive test: a test case where the IUT is required to respond to a protocol event (e.g. received message) with anotherprotocol event (e.g. send message) which normally does not require any special operator intervention as associated withthe implicit send event.Point of Control and Observation (PCO): 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 (SUT): refer to ISO/IEC 9646-1 [3].Test Purpose (TP): refer to ISO/IEC 9646-1 [3].3.1.2Definitions related to EN 301 065-1component: see EN 300 196-1 [6], subclause 11.2.2.1.dummy call reference: see EN 300 403-1 [8], subclause 4.3.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 EN 300 196-1 [6], subclause 11.2.2.1.return error component: see EN 300 196-1 [6], subclause 11.2.2.1.SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)7return result component: see EN 300 196-1 [6], subclause 11.2.2.1.service; telecommunication service: see ITU-T Recommendation I.112 [9], definition 201.supplementary service: see ITU-T Recommendation I.210 [11], subclause 2.4.S/T: the DSS1 protocol entity at the User side of the user-network interface where a coincident S and T reference pointapplies.T: the DSS1 protocol entity at the User side of the user-network interface where a T reference point applies (User is aPrivate ISDN).3.2AbbreviationsFor the purposes of the present document, the following abbreviations apply:ATSAbstract Test SuiteCCNRCompletion of Calls on No ReplyISDNIntegrated Services Digital NetworkIUTImplementation Under TestPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingTPTest PurposeTSSTest Suite StructureU0Null call stateU3Outgoing Call Proceeding call stateU4Call Delivered call stateU7Call Received call stateU10Active call stateU11Disconnect Request call stateU19Release Request call stateU31Bearer Independent Transport call stateSIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)84Test Suite Structure (TSS)Signalling procedures at the coincident S and T reference pointGroupActivationU01DeactivationU02General interrogationU03Specific interrogationU04Recall indicationU05CCNR call requestU06Network initiated deactivation procedureU07B free but A busy procedureU08User A monitoring procedureU09Call information retentionU10Procedures for interworking with private ISDNsProcedures for the originating T reference pointU11Procedures for the destination T reference pointU12Figure 1: Test suite structure5Test Purposes (TP)5.1IntroductionFor each test requirement a TP is defined.5.1.1TP naming conventionTPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional referencesare 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 schemeIdentifier:__=supplementary service: "CCNR"=type of IUT:UUserNNetwork=group2 digit field representing group reference according to TSS=sequential number(001-999)5.1.2Source of TP definitionThe TPs are based on EN 301 065-1 [1].SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)95.1.3TP structureEach TP has been written in a manner which is consistent with all other TPs. The intention of this is to make the TPsmore readable and checkable. A particular structure has been used and this is illustrated in table 2. This table should beread in conjunction with any TP, i.e. use a TP as an example to fully understand the table.Table 2: Structure of a single TP for CCNRTP partTextExampleHeader tabsee table 1 tabsubclause 0.0.0 CR.mandatory, optional (see note 1)StimulusEnsure that the IUT in the or U10 etc. 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 remains in the same stateor and enters 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 1:Mandatory test purpose are always applicable. Optional test purposes are applicable according to theconfiguration options of the IUT. If the configuration option is covered by a PICS item, a selection criteriais indicated, else the selection of the corresponding test cases will depend on test suite parameters(PIXIT) in the ATS.NOTE 2:Text in italics will not appear in TPs and text between <> is filled in for each TP and may differ from oneTP to the next.5.1.4Test strategyAs the base standard EN 301 065-1 [1] contains no explicit requirements for testing, the TPs were generated as a resultof an analysis of the base standard and the PICS specification EN 301 065-2 [2]. The criteria applied include thefollowing:-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.5.2User TPs for CCNRAll PICS items referred to in this subclause are as specified in EN 301 065-2 [2] unless indicated otherwise by anothernumbered reference.Unless specified:-The messages indicated are valid and contain at least the mandatory information elements and possibly optionalinformation elements.-The information elements indicated are valid and contain at least the mandatory parameters and possibly optionalparameters.SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)105.2.1Signalling procedures at the coincident S and T reference pointSelection:IUT supports coincident S/T reference point procedures. PICS: R 3.1.NOTE:The signalling procedures at the coincident S and T reference point use mainly the bearer-independentconnectionless transport mechanism using the dummy call reference. To augment the readability of thetest purposes, basic call states are only mentioned where significant.5.2.1.1ActivationNOTE:The IUT may be in call state U4, U11 or U0 when requesting the activation of CCNR.CCNR_U01_001subclause 9.1.1mandatoryEnsure that the IUT in the CCNR Idle state, having received an ALERTING message with a Facility informationelement including a CallInfoRetain invoke component with callLinkageID parameter, to activate the CCNRsupplementary service,sends a FACILITY message with the dummy call reference containing a Facility information element with aCCNRRequest invoke component including the callLinkageID parameter and enters the CCNR Requested state.CCNR_U01_002subclause 9.1.1mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a CCNRRequest return result component including the cCBSReferenceparameter and the recallMode parameter indicating "specificRecall",sends no message, retains the CCBS Reference and enters the CCNR Activated state.CCNR_U01_003subclause 9.1.1mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a CCNRRequest return result component including the cCBSReferenceparameter and the recallMode parameter indicating "globalRecall",sends no message, retains the CCBS Reference and enters the CCNR Activated stateorsends no message, releases the CCBS Reference and enters the CCNR Idle state.CCNR_U01_004subclause 9.1.2mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a CCNRRequest return error component indicating "notSubscribed",sends no message and enters the CCNR Idle state.CCNR_U01_005subclause 9.1.2mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a CCNRRequest return error component indicating"invalidCallLinkageID",sends no message and releases the callLinkageID parameter.CCNR_U01_006subclause 9.1.2mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a CCNRRequest return error component indicating"outgoingCCBSQueueFull",sends no message and enters the CCNR Idle state.CCNR_U01_007subclause 9.1.2mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a CCNRRequest return error component indicating"cCBSIsAlreadyActivated",sends no message and enters the CCNR Idle state.CCNR_U01_008subclause 9.1.2mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a CCNRRequest return error component indicating"supplementaryServiceInteractionNotAllowed",sends no message and enters the CCNR Idle state.SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)11CCNR_U01_009subclause 9.1.2mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a CCNRRequest return error component indicating "longTermDenial",sends no message and enters the CCNR Idle state.CCNR_U01_010subclause 9.1.2mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a CCNRRequest return error component indicating "shortTermDenial",sends no message and enters the CCNR Idle state.CCNR_U01_011subclause 9.1.2mandatoryEnsure that the IUT in the CCNR Requested state, receiving a FACILITY message with the dummy call referencecontaining a Facility information element with a reject component including the invoke identifier,sends no message and enters the CCNR Idle state.CCNR_U01_012subclause 9.1.2mandatoryEnsure that the IUT in the CCNR Requested state, on the expiry of timer T-ACTIVATE,sends no message and enters the CCNR Idle state.5.2.1.2DeactivationCCNR_U02_001subclause 9.2.1mandatoryEnsure that the IUT in the CCNR Activated state, to deactivate the CCNR supplementary service,sends a FACILITY message with the dummy call reference containing a Facility information element with aCCBSDeactivate invoke component including the cCBSReference parameter and enters the CCNR DeactivationRequested state.CCNR_U02_002subclause 9.2.1mandatoryEnsure that the IUT in the CCNR Deactivation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a CCBSDeactivate return result component,sends no message, releases the CCBS Reference and enters the CCNR Idle state.CCNR_U02_003subclause 9.2.2mandatoryEnsure that the IUT in the CCNR Deactivation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a CCBSDeactivate return error component indicating"invalidCCBSReference",sends no message, releases the CCBS Reference and enters the CCNR Idle state.CCNR_U02_004subclause 9.2.2mandatoryEnsure that the IUT in the CCNR Deactivation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a reject component including the invoke identifier,sends no message, retains the CCBS Reference and enters the CCNR Idle state.5.2.1.3Interrogation5.2.1.3.1General interrogationCCNR_U03_001subclause 9.3.1.1mandatoryEnsure that the IUT, to perform an interrogation of all CCNR requests,sends a FACILITY message with the dummy call reference containing a Facility information element with aCCNRInterrogate invoke component without a cCBSReference parameter and enters the CCNR InterrogationRequested state.CCNR_U03_002subclause 9.3.1.1mandatoryEnsure that the IUT in the CCNR Interrogation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a CCNRInterrogate return result component,sends no message and exits the CCNR Interrogation Requested state.SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)12CCNR_U03_003subclause 9.3.1.2mandatoryEnsure that the IUT in the CCNR Interrogation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a CCNRInterrogate return error component indicating"notSubscribed",sends no message, removes knowledge of all CCNR requests and exits the CCNR Interrogation Requested state.CCNR_U03_004subclause 9.3.1.2mandatoryEnsure that the IUT in the CCNR Interrogation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a reject component including the invoke identifier,sends no message and exits the CCNR Interrogation Requested state.CCNR_U03_005subclause 9.3.1.2mandatoryEnsure that the IUT in the CCNR Interrogation Requested state, on the expiry of timer T-ACTIVATE,sends no message and exits the CCNR Interrogation Requested state.5.2.1.3.2Specific interrogationCCNR_U04_001subclause 9.3.2.1mandatoryEnsure that the IUT, to perform an interrogation of a specific CCNR requests,sends a FACILITY message with the dummy call reference containing a Facility information element with aCCNRInterrogate invoke component with the cCBSReference parameter and enters the CCNR InterrogationRequested state.CCNR_U04_002subclause 9.3.2.1mandatoryEnsure that the IUT in the CCNR Interrogation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a CCNRInterrogate return result component,sends no message and exits the CCNR Interrogation Requested state.CCNR_U04_003subclause 9.3.2.2mandatoryEnsure that the IUT in the CCNR Interrogation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a CCNRInterrogate return error component indicating"notSubscribed",sends no message, removes knowledge of all CCNR requests and exits the CCNR Interrogation Requested state.CCNR_U04_004subclause 9.3.2.2mandatoryEnsure that the IUT in the CCNR Interrogation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a CCNRInterrogate return error component indicating"invalidCCBS Reference",sends no message, removes knowledge of the specific CCNR request and exits the CCNR InterrogationRequested state.CCNR_U04_005subclause 9.3.2.2mandatoryEnsure that the IUT in the CCNR Interrogation Requested state, receiving a FACILITY message with the dummy callreference containing a Facility information element with a reject component including the invoke identifier,sends no message, retains knowledge of the specific CCNR request and exits the CCNR Interrogation Requestedstate.CCNR_U04_006subclause 9.3.2.2mandatoryEnsure that the IUT in the CCNR Interrogation Requested state, on the expiry of timer T-ACTIVATE,sends no message and exits the CCNR Interrogation Requested state.SIST EN 301 065-3:2001
ETSIEN 301 065-3 V1.1.3 (1998-10)135.2.1.4Invocation and operation5.2.1.4.1Recall indicationCCNR_U05_001subclause 9.4.1.1, 9.7mandatoryEnsure that the IUT in the CCNR Activ
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.