ETSI ETS 300 267-6 ed.1 (1998-04)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Integrated Services Digital Network (ISDN); Telephony 7 kHz and videotelephony teleservices; 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.020Telekomunikacije na splošnoTelecommunications in generalICS:Ta slovenski standard je istoveten z:ETS 300 267-6 E13SIST ETS 300 267-6:1998en01-DSULO-19983SIST ETS 300 267-6:1998SLOVENSKI
STANDARD



SIST ETS 300 267-6:1998



DRAFTEUROPEANprETS 300 267-6TELECOMMUNICATIONApril 1997STANDARDSource: ETSI TC-SPSReference: DE/SPS-05048-6ICS:33.020Key words:ISDN, DSS1, teleservice, 7 kHz, video, telephony, testing, ATS, PIXIT, networkIntegrated Services Digital Network (ISDN);Telephony 7 kHz and videotelephony teleservices;Digital Subscriber Signalling System No. one (DSS1) protocol;Part 6: Abstract Test Suite (ATS) and partial ProtocolImplementation eXtra Information for Testing (PIXIT) proformaspecification for the networkETSIEuropean 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: secretariat@etsi.frTel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16Copyright 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 1997. All rights reserved.SIST ETS 300 267-6:1998



Page 2Draft prETS 300 267-6: April 1997Whilst 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 267-6:1998



Page 3Draft prETS 300 267-6: April 1997ContentsForeword.71Scope.92Normative references.93Definitions and abbreviations.103.1Definitions.103.2Abbreviations.104Introduction.105Abstract Test Method (ATM).115.1Description of ATM used.115.2Conventions for test components and PCOs.115.3Description of PCOs.125.3.1D-channel PCOs.125.3.2PSTN PCO.135.4Naming conventions.135.4.1Test cases.135.4.2Variables and parameters.145.4.3Trees and subtrees.146Untestable test purposes.147ATS conventions.157.1Declarations part.157.1.1Type definitions.157.1.1.1Simple type definitions.157.1.1.2Structured type definitions.157.1.1.2.1TTCN structured type definitions.157.1.1.2.2ASN.1 structured type definitions.157.1.1.3ASP type definitions.157.1.1.3.1TTCN ASP type definitions.157.1.1.3.2ASN.1 ASP type definitions.167.1.1.4PDU type definitions.167.1.1.4.1TTCN PDU type definitions.167.1.1.4.2ASN.1 PDU type definitions.167.1.2Test suite constants.167.1.3Test suite parameters.167.1.4Variables.177.1.4.1Test suite variables.177.1.4.2Test case variables.177.1.5Test suite operation definitions.177.2Constraints part.177.2.1Structured type constraint declaration.177.2.2ASN.1 type constraint declaration.177.2.3ASP type constraint declaration.177.2.3.1ASN.1 ASP type constraint declaration.177.2.3.2TTCN ASP type constraint declaration.187.2.4PDU type constraint declaration.187.2.4.1ASN.1 PDU type constraint declaration.187.2.4.2TTCN PDU type constraint declaration.187.2.5Derived constraint.187.2.6Parameterized constraints.18SIST ETS 300 267-6:1998



Page 4Draft prETS 300 267-6: April 19977.2.7Value assignment.187.2.7.1Specific values.187.2.7.2Matching values.187.3Dynamic part.197.3.1Test cases.197.3.2Test steps.197.3.2.1PTC1_IN, PTC1_2B_IN.197.3.2.2PTC1_OUT, PTC1_BCAP_OUT,PTC1_BCAP_HLC_OUT, PTC1_2B_OUT.197.3.3Defaults.198ATS to TP map.209PCTR conformance.2010PIXIT conformance.2011ATS 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.26Annex B (normative):Partial PIXIT proforma.27B.1Identification summary.27B.2Abstract test suite summary.27B.3Test laboratory.27B.4Client (of the test laboratory).28B.5System Under Test (SUT).28B.6Protocol information.29B.6.1Protocol identification.29B.6.2Configuration to be tested.29B.6.3Actions required to stimulate IUT.30B.6.4Test management timers.30B.6.5Parameter values.31SIST ETS 300 267-6:1998



Page 5Draft prETS 300 267-6: April 1997Annex C (normative):Abstract Test Suite (ATS).32C.1The TTCN Graphical form (TTCN.GR).32C.2The TTCN Machine Processable form (TTCN.MP).32Annex D (informative):General structure of ATS.33History.34SIST ETS 300 267-6:1998



Page 6Draft prETS 300 267-6: April 1997Blank pageSIST ETS 300 267-6:1998



Page 7Draft prETS 300 267-6: April 1997ForewordThis draft European Telecommunication Standard (ETS) has been produced by the Signalling Protocolsand Switching (SPS) Technical Committee of the European Telecommunications Standards Institute(ETSI), and is now submitted for the Public Enquiry phase of the ETSI standards approval procedure.This ETS 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) telephony 7 kHz andvideotelephony teleservices, 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".Proposed transposition datesDate of latest announcement of this ETS (doa):3 months after ETSI publicationDate of latest publication of new National Standardor endorsement of this ETS (dop/e):6 months after doaDate of withdrawal of any conflicting National Standard (dow):6 months after doaSIST ETS 300 267-6:1998



Page 8Draft prETS 300 267-6: April 1997Blank pageSIST ETS 300 267-6:1998



Page 9Draft prETS 300 267-6: April 19971ScopeThis sixth part of ETS 300 267 specifies the Abstract Test Suite (ATS) and partial Protocol ImplementationeXtra Information for Testing (PIXIT) proforma for the Network side of the T reference point or coincidentS and T reference point (as defined in ITU-T Recommendation I.411 [13]) of implementations conformingto the stage three standard of the telephony 7 kHz and videotelephony teleservices for the pan-EuropeanIntegrated Services Digital Network (ISDN) by means of the Digital Subscriber Signalling System No. one(DSS1) protocol, ETS 300 267-1 [3].ETS 300 267-5 [5] specifies the Test Suite Structure and Test Purposes (TSS&TP) related to this ATSand partial PIXIT proforma specification. Other parts specify the TSS&TP and the ATS and partial PIXITproforma for the User side of the T reference point or coincident S and T reference point ofimplementations conforming to ETS 300 267-1 [3].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 102-1: "Integrated Services Digital Network (ISDN); User-networkinterface layer 3; Specifications for basic call control".[2]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".[3]ETS 300 267-1 (1994) including A1 (1996): "Integrated Services Digital Network(ISDN); Telephony 7 kHz and videotelephony teleservices; Digital SubscriberSignalling System No. one (DSS1) protocol; Part 1: Protocol specification".[4]ETS 300 267-2 (1996): "Integrated Services Digital Network (ISDN); Telephony7 kHz and videotelephony teleservices; Digital Subscriber Signalling System No.one (DSS1) protocol; Part 2: Protocol Implementation Conformance Statement(PICS) proforma specification".[5]ETS 300 267-5: "Integrated Services Digital Network (ISDN); Telephony 7 kHzand videotelephony teleservices; Digital Subscriber Signalling System No. one(DSS1) protocol; Part 5: Test Suite Structure and Test Purposes (TSS&TP)specification for the network".[6]ETS 300 403-1 (1995): "Integrated Services Digital Network (ISDN); DigitalSubscriber Signalling System No. one (DSS1) protocol; Signalling network layerfor circuit-mode basic call control; Part 1: Protocol specification [ITU-TRecommendation Q.931 (1993), modified]".[7]ETS 300 403-7: "Integrated Services Digital Network (ISDN); Digital SubscriberSignalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 7: Abstract Test Suite (ATS) and partial ProtocolImplementation eXtra Information for Testing (PIXIT) proforma specification forthe network".[8]ISO/IEC 9646-1: "Information technology - OSI Conformance TestingMethodology and Framework; Part 1: General Concepts".[9]ISO/IEC 9646-2: "Information technology - OSI Conformance TestingMethodology and Framework; Part 2: Abstract Test Suite Specification".SIST ETS 300 267-6:1998



Page 10Draft prETS 300 267-6: April 1997[10]ISO/IEC 9646-3: "Information technology - OSI Conformance TestingMethodology and Framework; Part 3: The Tree and Tabular CombinedNotation".[11]ISO/IEC 9646-4: "Information technology - OSI Conformance TestingMethodology and Framework; Part 4: Test realization".[12]ISO/IEC 9646-5: "Information technology - OSI Conformance TestingMethodology and Framework; Part 5: Requirements on test laboratories andclients for the conformance assessment process".[13]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces -Reference configurations".3Definitions and abbreviations3.1DefinitionsFor the purposes of this ETS, the definitions given in ETS 300 267-1 [3] and ISO/IEC 9646, parts 1 [8]to 5 [12] apply.3.2AbbreviationsFor the purposes of this ETS, the following abbreviations apply:ASPAbstract Service PrimitiveATMAbstract Test MethodATSAbstract Test SuiteBASBit rate Allocation SignalCMCo-ordination MessageCPCo-ordination PointCRCCyclic Redundancy CheckExTSExecutable Test SuiteFAWFrame Alignment WordIUTImplementation Under TestLTLower TesterMOTMeans Of TestingMTCMain Test ComponentPCOPoint of Control and ObservationPCTRProtocol Conformance Test ReportPDUProtocol Data UnitPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingPTCParallel Test ComponentSUTSystem Under TestTPTest PurposeTSSTest Suite StructureTTCNTree and Tabular Combined NotationUTUpper Tester4IntroductionImplementations Under Test (IUTs) which are to be tested using this ATS are required to have previouslybeen tested for conformity against and passed the test suites for ETS 300 102-1 [1] or ETS 300 403-1 [6].Any messages or fields within messages which are introduced by ETS 300 403-1 [6] are included in thisATS. Behaviours in test cases have been described in such a way to be able to take into account bothETS 300 102-1 [1] and ETS 300 403-1 [6] basic call standards. This ATS also takes into accountmessages defined for the supplementary services, in particular ETS 300 196-1 [2]. When such messagesare received, they are ignored by the ATS as this is not within the scope of this ETS.SIST ETS 300 267-6:1998



Page 11Draft prETS 300 267-6: April 19975Abstract Test Method (ATM)5.1Description of ATM usedThis ATS describes the testing specification of the protocol procedures and switching functions needed tosupport the videotelephony and telephony 7 kHz teleservices at T or coincident S and T reference pointsfor the network.The requirement for testing the network IUT is to focus on the behaviour of the network IUT at the user-network interface where a T reference point or coincident S and T reference point applies. Thus the IUT isthe network DSS1 protocol entity at a particular user-network interface and not the whole network.It is possible to specify an ATS based on a single party (remote) test method for such an IUT. However, itis considered that an ATS based on such an approach is of limited use as the only way to specify IUTgenerated PDUs is to use the "implicit send" statement. Many users of such an ATS would replace the"implicit send" statements with descriptions of the 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 areal test suite would be constructed. Such a test method specifies behaviour at multiple networkinterfaces. One very important limitation here is that tests are focused on one particular interface. Thusthe test system is made up of one Main Test Component (MTC) and one or more Parallel TestComponents (PTC), see figure 1. No actual testing is performed by the MTC, as all Points of Control andObservation (PCOs) are on the PTCs.5.2Conventions for test components and PCOsFigure 1 shows a logical view of the complete configuration of the MTC, PTCs, and PCOs. TheCo-ordination Point (CP) relationships between the various components are also indicated. In amaster/slave arrangement, PTC0 is considered to be the master while PTC1 and PTCT are the slaves.The "slave" testers are only an explicit description of how to deal with the "other" interfaces during thetesting process, i.e. "how to make the IUT send the required message".PTCMPTC1L1PTCTTCPM1MTCPTCsPCOsPTC0CP01 CPM0L0IUTTESTERNetworkCPMTCP0T MasterPartSlavePartFigure 1: Multi-party test methodSIST ETS 300 267-6:1998



Page 12Draft prETS 300 267-6: April 1997This means, in particular, that the verdict FAIL will only be assigned from the protocol aspects observedon the interface under test (i.e. by PTC0), as it would be observed by a terminal connected to thisinterface. A failure in the correlation between the protocol at the different interfaces to which the differenttesters are connected, i.e. in the mechanism of the functional service itself, will not cause a FAIL verdict.For instance, if the IUT fails to send a message on the tested interface after another interface hasreceived the proper stimulus, the verdict will be INCONCLUSIVE.The MTC, PTCM, handles all scheduling of test components and exchanges messages with PTCs to startor to stop the running of their associated tree. There are communication paths or CPs between the MTCand each PTC, and also between PTC0 and the "slave" PTCs PTC1 and PTCT.The PTC0 PCO is named "L0" ("L" for Lower). The L0 PCO is used to control and observe the behaviourof the IUT and test case verdicts are assigned depending on the behaviour observed at this PCO. ThePTCs PTC1 and PTCT use PCOs L1 and T. These PCOs are used to control and, in a limited way,observe the behaviour of the network equipment at interfaces other than the one under test. Only PASS orINCONCLUSIVE verdicts are assigned at these PCOs.As stated in a previous paragraph, the non-receipt of network generated messages at L0, which arestimulated by events at L1 or T will result in INCONCLUSIVE rather than FAIL verdicts being assigned.5.3Description of PCOsThe PCOs are used to control and observe the behaviour of the IUT. Preliminary test case verdicts areassigned depending on the behaviour observed at those points. The final verdict is set by the MTC at theend of the test.5.3.1D-channel PCOsFor the D-channel, the PCOs reside at the service access point between layers 2 and 3. These PCOs arenamed "L0" and "L1". The same Abstract Service Primitives (ASPs) as defined in ETS 300 403-7 [7] areused.PTC0SUTPTC1Layer 3¾¾¾¾Layer 2¾¾¾¾Layer 1¾L0¾¾¾¾¾¾¾¾¾IUT¾¾¾¾¾¾¾¾¾
¾¾
¾¾¾¾¾¾¾¾¾¾¾¾¾¾L1¾¾¾¾¾Layer 3¾¾¾¾Layer 2¾¾¾¾Layer 1Service providerFigure 2: Combination of the remote and multi-party test methods without interworking with PSTNSIST ETS 300 267-6:1998



Page 13Draft prETS 300 267-6: April 19975.3.2PSTN PCOFor tests involving the PSTN, the PCOs used are L0 and T. L0 is at the same location as in figure 2 and Tis located at the upper tester at the access point between the test operator and the IUT.PTC0SUTPTCTTLayer 3¾¾¾¾Layer 2¾¾¾¾Layer 1¾L0¾¾¾¾¾¾¾¾¾IUT¾¾¾¾¾¾¾¾¾
¾¾
¾¾
¾ ¾¾
¾ ¾Service providerPSTNFigure 3: Combination of the remote and multi-party test methods with interworking with PSTN5.4Naming conventions5.4.1Test casesThe structure of test case identifier is as follows:TTC_test case covering a telephony 7 kHz requirement;VTC_test case covering a videotelephony requirement.The digits corresponds to the digits of the Test Purpose (see ETS 300 267-5 [5]) involved in the test case.The TPs are ordered:a)by type of requirement (i.e. generic, telephony 7 kHz or videotelephony);b)by a three digit number which specifies the relevant position in the Test Suite Structure (TSS):-the first digit refers to the second test group level:1for Originating interface (ORIG);2for Destination interface (DEST);-the second digit refers to the third test group level:1Valid behaviour (BV);2Invalid behaviour (BI);3Inopportune behaviour (BO);-the third digit refers to the fifth test group level:1Fallback allowed (FBA);2Fallback not allowed (FBN);3Connection management (CMN);c)by a two digit sequence number:the sequence number follows the order in which the TPs appear in the third level of the TSS.SIST ETS 300 267-6:1998



Page 14Draft prETS 300 267-6: April 19975.4.2Variables and parametersThe following shows the naming convention for variables used for each B-channel depending on whetherone or two B-channels are established during the call between PTC0 and PTC1.PTC0Initial B-channelcall referenceCREFB-channel (basic)B_CHNchannel nr (primary)PX_CH_NUMAdditional B-channelcall referenceCREF2B-channel (basic)B_CHN2channel nr (primary)PX_CH_NUM2PTC1Initial B-channelcall referenceP1CREFB-channel (basic)P1_B_CHNchannel nr (primary)PX_CH_NUMAdditional B-channelcall referenceP1CREF2B-channel (basic)P1_B_CHN2channel nr (primary)PX_CH_NUM2The following shows the naming conventions for parameters used to address the PTCs.PTCParametersPTC0PX_PSTN_LCPN,PX_PSTN_CDPN_OCTET3,PX_PSTN_CPNPTC1PX_PTC1_LCPN,PX_PTC1_CDPN_OCTET3,PX_PTC1_CPNPTCTPX_PSTN_LCPN,PX_PSTN_CDPN_OCTET3,PX_PSTN_CPN5.4.3Trees and subtreesTest step names use upper case letters and local subtrees use lower case letters.Preamble subtrees are prefixed by "PTCx_PR_" and postamble subtrees by "PTCx_PO_", where x can be0 or 1 depending on the PTC for which this subtree is defined.6Untestable test purposesTPs for generic protocol requirements do not correspond to specific protocol behaviour and only describeparts of ETS 300 267-1 [3] which support the telephony 7 kHz and videotelephony teleservices. TheseTPs have been considered as untestable.SIST ETS 300 267-6:1998



Page 15Draft prETS 300 267-6: April 19977ATS conventionsThis clause is structured similarly to the structure of a TTCN ATS. However, the names of the subclausesare arranged in a way more suitable to this ETS.7.1Declarations part7.1.1Type definitions7.1.1.1Simple type definitionsWhere appropriate, simple types have a length, a value list or a range restriction attached.Simple types defined as being of some string type (e.g. BITSTRING, OCTETSTRING), have a lengthrestriction or a value list attached.Simple types, defined as being of INTEGER type, have a value list or a range restriction attached.7.1.1.2Structured type definitions7.1.1.2.1TTCN structured type definitionsAll structured type definitions are provided with a full name.All elements in every structured type definition, defined as being of some string type (e.g. BITSTRING,OCTETSTRING), have a length restriction attached.If an element in a structured type definition is defined as being of a referenced type, the (possible)restriction is defined in that referenced type.For information elements the identifier, which is unique for each element, has its type defined as a simpletype where the value list is restricted to the single value which is the identifier itself. This has theadvantage that it allows a test system derived from this ATS to easily identify information elementsembedded in messages. An ATS where information element identifiers are represented as unrestrictedtypes can present difficulties for a derived test system in the case where it needs to find one informationelement embedded in a number of others and the constraints for the other elements have the any-or-omitvalue. In such a case the test system cannot easily find the beginning of each information element.7.1.1.2.2ASN.1 structured type definitionsThere are no ASN.1 structured type definitions in the ATS.7.1.1.3ASP type definitions7.1.1.3.1TTCN ASP type definitionsTTCN ASP type definitions only contain one PDU or no PDU at all.All TTCN ASP type definitions are provided with a full identifier.SIST ETS 300 267-6:1998



Page 16Draft prETS 300 267-6: April 1997Some ASPs are not parameterized as shown in the example in table 1. Such ASPs are only used forrequesting or receiving service from the lower layer.Table 1: TTCN ASP type definition DL_REL_INTTCN ASP Type DefinitionASP NAME : DL_REL_IN
(DL-RELEASE-INDICATION)PCO Type : SAPCo
...