Integrated Services Digital Network (ISDN); Conference call, add-on (CONF) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network

Update to references to cite latest basic call standards et al. Incorporation of minor technical modifications where necessary.

Digitalno omrežje z integriranimi storitvami (ISDN) – Dopolnilna storitev: konferenčni klic, postopno vzpostavljanje (CONF) – Protokol digitalne naročniške signalizacije št. 1 (DSS1) – 6. del: Abstraktni preskušalni niz (ATS) in delna dodatna informacija za preskušanje izvedbe protokola (PIXIT) – Proforma specifikacija za omrežje

General Information

Status
Published
Publication Date
30-Nov-2003
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Dec-2003
Due Date
01-Dec-2003
Completion Date
01-Dec-2003

Buy Standard

Standard
SIST EN 300 185-6 V1.2.4:2003
English language
32 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day

Standards Content (sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.VWRULWHYRIRUPDIntegrated Services Digital Network (ISDN); Conference call, add-on (CONF) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 300 185-6 Version 1.2.4SIST EN 300 185-6 V1.2.4:2003en01-december-2003SIST EN 300 185-6 V1.2.4:2003SLOVENSKI

STANDARD
SIST EN 300 185-6 V1.2.4:2003

EN 300 185-6 V1.2.4 (1998-06)European Standard (Telecommunications series)Integrated Services Digital Network (ISDN);Conference call, add-on (CONF) supplementary service;Digital Subscriber Signalling System No. one (DSS1) protocol;Part 6: Abstract Test Suite (ATS) and partial ProtocolImplementation eXtra Information for Testing (PIXIT)proforma specification for the networkSIST EN 300 185-6 V1.2.4:2003

ETSIEN 300 185-6 V1.2.4 (1998-06)2ReferenceREN/SPS-05145-J1-6 (1ppi0iqo.PDF)KeywordsISDN, DSS1, supplementary service, CONF,testing, ATS, PIXIT, networkETSIPostal 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.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 300 185-6 V1.2.4:2003

ETSIEN 300 185-6 V1.2.4 (1998-06)3ContentsIntellectual Property Rights................................................................................................................................5Foreword............................................................................................................................................................51Scope........................................................................................................................................................62Normative references...............................................................................................................................63Definitions and abbreviations..................................................................................................................73.1Definitions.........................................................................................................................................................73.2Abbreviations.....................................................................................................................................................74Abstract Test Method (ATM)..................................................................................................................84.1Description of ATM used..................................................................................................................................84.1.1Conventions for test components and PCOs................................................................................................84.1.2Conventions for variables and parameters....................................................................................................94.1.3Special conventions for the CONF supplementary service........................................................................104.1.4Conventions for the remote user group......................................................................................................104.2Alternative ATM..............................................................................................................................................115Untestable test purposes.........................................................................................................................126ATS conventions....................................................................................................................................126.1Declarations part..............................................................................................................................................126.1.1Type definitions.........................................................................................................................................126.1.1.1Simple type definitions.........................................................................................................................126.1.1.2Structured type definitions....................................................................................................................126.1.1.2.1TTCN structured type definitions...................................................................................................126.1.1.2.2ASN.1 structured type definitions...................................................................................................126.1.1.3ASP type definitions.............................................................................................................................146.1.1.3.1TTCN ASP type definitions............................................................................................................146.1.1.3.2ASN.1 ASP type definitions............................................................................................................146.1.1.4PDU type definitions............................................................................................................................146.1.1.4.1TTCN PDU type definitions...........................................................................................................146.1.1.4.2ASN.1 PDU type definitions...........................................................................................................146.1.2Test suite constants.....................................................................................................................................146.1.3Test suite parameters..................................................................................................................................146.1.4Variables....................................................................................................................................................156.1.4.1Test suite variables...............................................................................................................................156.1.4.2Test case variables................................................................................................................................156.1.5Test suite operation definitions..................................................................................................................156.2Constraints part................................................................................................................................................156.2.1Structured type constraint declaration........................................................................................................156.2.2ASN.1 type constraint declaration..............................................................................................................156.2.2.1Specification of encoding rules.............................................................................................................166.2.3ASP type constraint declaration.................................................................................................................176.2.3.1ASN.1 ASP type constraint declaration................................................................................................176.2.3.2TTCN ASP type constraint declaration................................................................................................176.2.4PDU type constraint declaration.................................................................................................................186.2.4.1ASN.1 PDU type constraint declaration...............................................................................................186.2.4.2TTCN PDU type constraint declaration................................................................................................186.2.5Chaining of constraints...............................................................................................................................186.2.5.1Static chaining......................................................................................................................................186.2.5.2Dynamic chaining.................................................................................................................................186.2.6Derived constraints.....................................................................................................................................186.2.7Parameterized constraints...........................................................................................................................186.2.8Value assignment.......................................................................................................................................186.2.8.1Specific values......................................................................................................................................186.2.8.2Matching values....................................................................................................................................19SIST EN 300 185-6 V1.2.4:2003

ETSIEN 300 185-6 V1.2.4 (1998-06)46.3Dynamic part....................................................................................................................................................196.3.1Test cases...................................................................................................................................................196.3.2Test steps....................................................................................................................................................196.3.2.1PTC1_IN..............................................................................................................................................196.3.2.2PTC1_OUT..........................................................................................................................................196.3.3Defaults......................................................................................................................................................197ATS to TP map......................................................................................................................................198PCTR conformance................................................................................................................................209PIXIT conformance................................................................................................................................2010ATS conformance..................................................................................................................................20Annex A (normative):Protocol Conformance Test Report (PCTR) proforma.............................21A.1Identification summary..........................................................................................................................21A.1.1Protocol conformance test report.....................................................................................................................21A.1.2IUT identification............................................................................................................................................21A.1.3Testing environment........................................................................................................................................21A.1.4Limits and reservations....................................................................................................................................22A.1.5Comments........................................................................................................................................................22A.2IUT conformance status.........................................................................................................................22A.3Static conformance summary.................................................................................................................22A.4Dynamic conformance summary............................................................................................................22A.5Static conformance review report..........................................................................................................23A.6Test campaign report..............................................................................................................................23A.7Observations...........................................................................................................................................24Annex B (normative):Partial PIXIT proforma................................................................................25B.1Identification summary..........................................................................................................................25B.2Abstract test suite summary...................................................................................................................25B.3Test laboratory.......................................................................................................................................25B.4Client (of the test laboratory).................................................................................................................26B.5System Under Test (SUT)......................................................................................................................26B.6Protocol information..............................................................................................................................27B.6.1Protocol identification......................................................................................................................................27B.6.2Parameter values..............................................................................................................................................27B.6.3Codings of information elements.....................................................................................................................27B.6.4Configuration of IUT.......................................................................................................................................27B.7Basic call PIXIT items...........................................................................................................................28B.7.1Parameter values - information element codings.............................................................................................28Annex C (normative):Abstract Test Suite (ATS).............................................................................29C.1The TTCN Graphical form (TTCN.GR)................................................................................................29C.2The TTCN Machine Processable form (TTCN.MP).............................................................................29Annex D (informative):General structure of ATS.............................................................................30Annex E (informative):Changes with respect to the previous ETS 300 185-6................................31History..............................................................................................................................................................32SIST EN 300 185-6 V1.2.4:2003

ETSIEN 300 185-6 V1.2.4 (1998-06)5Intellectual 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 6 of a multi-part standard covering the Digital Subscriber Signalling System No. one(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) Conference call, add-on (CONF)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".The present version updates the references to the basic call specifications.National transposition datesDate of adoption of this EN:19 June 1998Date of latest announcement of this EN (doa):30 September 1998Date of latest publication of new National Standardor endorsement of this EN (dop/e):31 March 1999Date of withdrawal of any conflicting National Standard (dow):31 March 1999SIST EN 300 185-6 V1.2.4:2003

ETSIEN 300 185-6 V1.2.4 (1998-06)61ScopeThis sixth part of EN 300 185 specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtraInformation for Testing (PIXIT) proforma for the Network side of the T reference point or coincident S and T referencepoint (as defined in ITU-T Recommendation I.411 [11]) of implementations conforming to the stage three standard forthe Conference call, add-on (CONF) supplementary service for the pan-European Integrated Services Digital Network(ISDN) by means of the Digital Subscriber Signalling System No. one (DSS1) protocol, EN 300 185-1 [2].EN 300 185-5 [4] specifies the Test Suite Structure and Test Purposes (TSS&TP) related to this ATS and partial PIXITproforma specification. Other parts specify the TSS&TP and the ATS and partial PIXIT proforma for the User side ofthe T reference point or coincident S and T reference point of implementations conforming to EN 300 185-1 [2].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 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]".[2]EN 300 185-1 (V1.2): "Integrated Services Digital Network (ISDN); Conference call, add-on(CONF) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;Part 1: Protocol specification".[3]EN 300 185-2 (V1.2): "Integrated Services Digital Network (ISDN); Conference call, add-on(CONF) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification".[4]EN 300 185-5 (V1.2): "Integrated Services Digital Network (ISDN); Conference call, add-on(CONF) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network".[5]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".[6]ISO/IEC 9646-1: "Information Technology - OSI Conformance Testing Methodology andFramework; Part 1: General Concepts".[7]ISO/IEC 9646-2: "Information Technology - OSI Conformance Testing Methodology andFramework; Part 2: Abstract Test Suite Specification".[8]ISO/IEC 9646-3: "Information Technology - OSI Conformance Testing Methodology andFramework; Part 3: The Tree and Tabular Combined Notation".[9]ISO/IEC 9646-4: "Information Technology - OSI Conformance Testing Methodology andFramework; Part 4: Test realization".SIST EN 300 185-6 V1.2.4:2003

ETSIEN 300 185-6 V1.2.4 (1998-06)7[10]ISO/IEC 9646-5: "Information Technology - OSI Conformance Testing Methodology andFramework; Part 5: Requirements on test laboratories and clients for the conformance assessmentprocess".[11]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces - Reference configurations".[12]CCITT Recommendation X.209 (1988): "Specification of Basic Encoding Rules for AbstractSyntax Notation One (ASN.1)".3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the following definitions apply:Abstract Test Suite (ATS): See ISO/IEC 9646-1 [6].Implementation Under Test (IUT): See ISO/IEC 9646-1 [6].Lower Tester (LT): See ISO/IEC 9646-1 [6].Point of Control and Observation (PCO): See ISO/IEC 9646-1 [6].Protocol Implementation Conformance Statement (PICS): See ISO/IEC 9646-1 [6].PICS proforma: See ISO/IEC 9646-1 [6].Protocol Implementation Extra Information for Testing (PIXIT): See ISO/IEC 9646-1 [6].PIXIT proforma: See ISO/IEC 9646-1 [6].System Under Test (SUT): See ISO/IEC 9646-1 [6].Upper Tester (UT): See ISO/IEC 9646-1 [6].3.2AbbreviationsFor the purposes of the present document, the following abbreviations apply:ASPAbstract Service PrimitiveATMAbstract Test MethodATSAbstract Test SuiteBERBasic Encoding RulesCMCo-ordination MessageCONFConference call, add-onCPCo-ordination PointExTSExecutable Test SuiteIUTImplementation Under TestLTLower TesterMOTMeans Of TestingMTCMain Test ComponentPCOPoint of Control and ObservationPDUProtocol Data UnitPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingPTCParallel Test ComponentSUTSystem Under TestTCPTest Co-ordination ProceduresTPTest PurposeTTCNTree and Tabular Combined NotationSIST EN 300 185-6 V1.2.4:2003

ETSIEN 300 185-6 V1.2.4 (1998-06)8UTUpper Tester4Abstract Test Method (ATM)4.1Description of ATM usedThe requirement for testing the network IUT is to focus on the behaviour of the network IUT at the user-networkinterface where a T reference point or coincident S and T reference point applies. Thus the IUT is the network DSS1protocol entity at a particular user-network interface and is not the whole network.It is possible to specify an ATS based on a Single party (remote) test method for such an IUT. However, it is consideredthat an ATS based on such an approach is of limited use as the only way to specify IUT generated PDUs is to use the"implicit send" statement. Many users of such an ATS would replace the "implicit send" statements with descriptions ofthe behaviour at other interfaces.An ATS based on a multi-party test method is considered to be more useful in that it is closer to how a real test suitewould be constructed. Such a test method specifies behaviour at multiple network interfaces. One very importantlimitation here is that tests are focused on one particular interface. Thus the test system is made up one Main TestComponent (MTC) and one or more Parallel Test Components (PTC), see figure 1.4.1.1Conventions for test components and PCOsMaster partSlave partMTCAPTC2CPA2PTC1CPA1L0 PCOL1 PCOL2 PCOIUTNETWORKFigure 1: Multi-party test methodIn a master/slave arrangement, the MTC is considered to be the master while the PTCs are the slaves. The "slave" testersare only an explicit description of how to deal with the "other" interfaces during the testing process, i.e. "how to makethe IUT send the required message".SIST EN 300 185-6 V1.2.4:2003

ETSIEN 300 185-6 V1.2.4 (1998-06)9This means, in particular, that the verdict will only be assigned from the protocol aspects observed on the interfaceunder test (i.e. by the "master" tester), as it would be observed by a terminal connected to this interface. A failure in thecorrelation between the protocol at the different interfaces to which the different testers are connected, i.e. in themechanism of the functional service itself, will not cause a FAIL verdict. For instance, if the IUT fails to send a messageon the tested interface after another interface has received the proper stimulus, the verdict will be INCONCLUSIVE.The MTC MTCA has two functions in this configuration. Firstly, it has the MTC function of controlling the one or morePTCs. Thus it is responsible for starting the PTCs and afterwards co-ordinates activities by exchanging Co-ordinationMessages (CM) with the PTCs. Secondly it is responsible for the behaviour of the Lower Tester (LT) at PCO L0.A combination of the remote and multi-party test methods is applied. As can be seen from figure 1, several PCOs areused. All PCOs reside at the service access points between layers 2 and 3.MTCSUTPTC1,2Layer 3¾¾¾¾Layer 2¾¾¾¾Layer 1¾L0¾¾¾¾¾¾¾¾¾IUT¾¾¾¾¾¾¾¾¾

¾¾¾¾¾¾¾¾¾¾¾¾¾¾L1,2¾¾¾¾¾Layer 3¾¾¾¾Layer 2¾¾¾¾Layer 1Service providerFigure 2: Combination of the remote and multi-party test methodsThe MTC PCO is named "L0" ("L" for Lower). The L0 PCO is used to control and observe the behaviour of the IUTand test case verdicts are assigned depending on the behaviour observed at this PCO. The PTCs PTC1, PTC2 etc. usePCOs L1, L2 etc. These PCOs are used to control and, in a limited way, observe the behaviour of the networkequipment at interfaces other than the one under test. No verdicts are assigned at these PCOs.As stated in a previous paragraph, the non-receipt of network generated messages at L0, which are stimulated by eventsat the L1, L2 etc., will result in INCONCLUSIVE rather than FAIL verdicts being assigned.4.1.2Conventions for variables and parametersMTCAcall referenceCREF1B channel (basic)bch_num1(to PTC1)channel nr (primary)CH_NUM1call referenceCREF2B channel (basic)bch_num2(to PTC2)channel nr (primary)CH_NUM2PCO L0IPN0, LIPN0PTC1call referenceP1CREFB channel (basic)P1_bch_numchannel nr (primary)P1_CH_NUMPCO L1IPN1, LIPN1SIST EN 300 185-6 V1.2.4:2003

ETSIEN 300 185-6 V1.2.4 (1998-06)10PTC2call referenceP2CREFB channel (basic)P2_bch_numchannel nr (primary)P2_CH_NUMPCO L2IPN2, LIPN24.1.3Special conventions for the CONF supplementary serviceTo begin a conference from the Null Call State, a remote user is not required. The CREF1 will be used without thePTC1. To add a party to the conference, a remote user with CREF2 using PTC2 is called.Some remote user test cases use 2 parties. To do that the first party is added by using the CREF2 with PTC1. After theparty has been added to the conference, CREF2 will be released. Then it is possible to add the second party by usingCREF2 with PTC2.4.1.4Conventions for the remote user groupFor this group, the side of the network which is being tested is where the conference remote user is connected. The mostconvenient approach here is to connect PTC1 to the IUT. The MTC is, as for the served user group test cases, connectedat the served user side of the network. This approach allows the reuse of test steps developed for the served user grouptests. This approach, representing a slight modification in the test method, is illustrated in figure 3. This shows that thepart of the network considered to be the IUT is connected to PTC1 rather than MTC1.Master partSlave partMTCAPTC2CPA2PTC1CPA1L0 PCOL1 PCOL2 PCOIUTNETWORKFigure 3: Multi-party test method - modified for remote user testsSIST EN 300 185-6 V1.2.4:2003

ETSIEN 300 185-6 V1.2.4 (1998-06)11The PTC1 is used to observe the notifications sent by the network. The test step PTC1_remoteUser_CR1 is used tocheck the receipt of the notification and depending on the result sends a CM back to the MTC. The MTC then issues averdict depending on the CM received from the PTC1. This is done in order to maintain the convention that the MTC isonly allowed to issue verdicts. However, one consequence of this is that any behaviour at the served user side which isnon-conforming will result in a Fail verdict being issued even though the focus of the tests is at the remote user side.This constraint is viewed as acceptable given the fact that in any case the network shall provide a conforming serveduser interface as well as one or more conforming remote us

...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.