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

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 network

DE/SPS-05048-6

Digitalno omrežje z integriranimi storitvami (ISDN) - Daljinski storitvi: telefonija 7 kHz in videotelefonija - 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 specifikacije za omrežje

General Information

• Status: Published
• Publication Date: 16-Apr-1998
• Technical Committee: SPS 5 3 - Conformance Testing
• Current Stage: 12 - Completion
• Due Date: 08-Apr-1998
• Completion Date: 17-Apr-1998
• Mandate: T-294
• Ref Project: SIST ETS 300 267-6:1998 - 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 network

Standards Content (Sample)

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
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: [e-mail].: [phone] - Fax: [phone]Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 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 : SAPComments : CEId: = (SAPI,CES) mapped onto DLCI: = (SAPI,TEI)
This ASP is used to confirm the termination of an established multiple frame
operation or to report an unsuccessful establishment attempt (L2--->L3)Parameter Name
|
Parameter Type
|
CommentsDetailed Comments :Table 2 shows an example of a parameterized ASP. All ASPs containing PDUs contain only that PDU andno other parameters.Table 2: TTCN ASP type definition DL_DATA_RQTTCN ASP Type DefinitionASP NAME : DL_DAT_RQ
(DL_DATA_REQUEST)PCO Type : DSAPComments :Parameter Name
|
Parameter Type
|
Commentsmun (MessageUnit)
|PDU
|Detailed Comments :To make TTCN more readable, aliases have been defined for ASPs.7.1.1.3.2ASN.1 ASP type definitionsThere are no ASN.1 ASP type definitions in the ATS.7.1.1.4PDU type definitions7.1.1.4.1TTCN PDU type definitionsThe TTCN PDU type reflects the actual data being transferred or received. All PDUs are embedded inASPs.A meta-type ASP has been defined for all messages which do not require the fields inside to bereferenced. This meta-type ASP carries the parameter type PDU. There is one meta-type ASP for sendevents and one for receive events, named DL_DAT_RQ and DL_DAT_IN, respectively. If certain fields ofa PDU have to be referenced, then a particular ASP type has been defined for that message. Forexample, the call reference of an outgoing SETUP message needs to be read by the tester and thereforethe ASP type DL_DAT_IN_SETUP has been defined for this event.7.1.1.4.2ASN.1 PDU type definitionsThere are no ASN.1 PDU type definitions in the ATS.7.1.2Test suite constantsEach test suite constant is defined in terms of a predefined type. The values given in the value column willremain unchanged throughout the ATS.7.1.3Test suite parametersEach test suite parameter is defined in terms of a predefined type or a referenced type. A referenced typeis used when it is necessary to attach restrictions to these type definitions (it is not allowed to includerestrictions directly in the test suite parameter table). The referenced type can have a length or valuerestriction attached to it in its declaration table.SIST ETS 300 267-6:1998

Page 17Draft prETS 300 267-6: April 19977.1.4Variables
...

SLOVENSKI STANDARD
01-december-1998
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'1'DOMLQVNLVWRULWYLWHOHIRQLMD
N+]LQYLGHRWHOHIRQLMD3URWRNROGLJLWDOQHQDURþQLãNHVLJQDOL]DFLMHãW'66
GHO$EVWUDNWQLSUHVNXãDOQLQL]$76LQGHOQDGRGDWQDLQIRUPDFLMD]DSUHVNXãDQMH
L]YHGEHSURWRNROD3,;,73URIRUPDVSHFLILNDFLMH]DRPUHåMH
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 network
Ta slovenski standard je istoveten z: ETS 300 267-6 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 267-6
TELECOMMUNICATION April 1998
STANDARD
Source: SPS Reference: DE/SPS-05048-6
ICS: 33.020
Key words: ISDN, DSS1, teleservice, 7 kHz, video, telephony, testing, ATS, PIXIT, network
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 network
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Internet: [e-mail] - http://www.etsi.fr - http://www.etsi.org
Tel.: [phone] - Fax: [phone]
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1998. All rights reserved.

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

Page 3
ETS 300 267-6: April 1998
Contents
Foreword .7
1 Scope .9
2 Normative references.9
3 Definitions and abbreviations .10
3.1 Definitions .10
3.2 Abbreviations .10
4 Introduction.10
5 Abstract Test Method (ATM).11
5.1 Description of ATM used .11
5.2 Conventions for test components and PCOs.11
5.3 Description of PCOs .12
5.3.1 D-channel PCOs .12
5.3.2 PSTN PCO.13
5.4 Naming conventions .13
5.4.1 Test cases.13
5.4.2 Variables and parameters .14
5.4.3 Trees and subtrees .14
6 Untestable test purposes.14
7 ATS conventions .15
7.1 Declarations part.15
7.1.1 Type definitions .15
7.1.1.1 Simple type definitions.15
7.1.1.2 Structured type definitions .15
7.1.1.2.1 TTCN structured type definitions .15
7.1.1.2.2 ASN.1 structured type definitions.15
7.1.1.3 ASP type definitions.15
7.1.1.3.1 TTCN ASP type definitions .15
7.1.1.3.2 ASN.1 ASP type definitions .16
7.1.1.4 PDU type definitions .16
7.1.1.4.1 TTCN PDU type definitions.16
7.1.1.4.2 ASN.1 PDU type definitions .16
7.1.2 Test suite constants .16
7.1.3 Test suite parameters .16
7.1.4 Variables .17
7.1.4.1 Test suite variables.17
7.1.4.2 Test case variables.17
7.1.5 Test suite operation definitions.17
7.2 Constraints part.17
7.2.1 Structured type constraint declaration.17
7.2.2 ASN.1 type constraint declaration .17
7.2.3 ASP type constraint declaration .17
7.2.3.1 ASN.1 ASP type constraint declaration .17
7.2.3.2 TTCN ASP type constraint declaration.18
7.2.4 PDU type constraint declaration.18
7.2.4.1 ASN.1 PDU type constraint declaration.18
7.2.4.2 TTCN PDU type constraint declaration .18
7.2.5 Derived constraint .18
7.2.6 Parameterized constraints.18
7.2.7 Value assignment.18
7.2.7.1 Specific values.18

Page 4
ETS 300 267-6: April 1998
7.2.7.2 Matching values . 18
7.3 Dynamic part . 19
7.3.1 Test cases . 19
7.3.2 Test steps . 19
7.3.2.1 PTC1_IN, PTC1_2B_IN . 19
7.3.2.2 PTC1_OUT, PTC1_BCAP_OUT,
PTC1_BCAP_HLC_OUT, PTC1_2B_OUT. 19
7.3.3 Defaults. 19
8 ATS to TP map . 20
9 PCTR conformance. 20
10 PIXIT conformance. 20
11 ATS conformance. 20
Annex A (normative): Protocol Conformance Test Report (PCTR) proforma . 21
A.1 Identification summary. 21
A.1.1 Protocol conformance test report. 21
A.1.2 IUT identification. 21
A.1.3 Testing environment. 21
A.1.4 Limits and reservations . 22
A.1.5 Comments. 22
A.2 IUT conformance status . 22
A.3 Static conformance summary. 22
A.4 Dynamic conformance summary. 22
A.5 Static conformance review report . 23
A.6 Test campaign report. 23
A.7 Observations. 26
Annex B (normative): Partial PIXIT proforma . 27
B.1 Identification summary. 27
B.2 Abstract test suite summary . 27
B.3 Test laboratory. 27
B.4 Client (of the test laboratory) . 28
B.5 System Under Test (SUT) . 28
B.6 Protocol information. 29
B.6.1 Protocol identification . 29
B.6.2 Configuration to be tested .29
B.6.3 Actions required to stimulate IUT. 30
B.6.4 Test management timers . 30
B.6.5 Parameter values . 31
Annex C (normative): Abstract Test Suite (ATS). 32
C.1 The TTCN Graphical form (TTCN.GR) .32
C.2 The TTCN Machine Processable form (TTCN.MP) . 32

Page 5
ETS 300 267-6: April 1998
Annex D (informative): General structure of ATS.33
History.34

Page 6
ETS 300 267-6: April 1998
Blank page
Page 7
ETS 300 267-6: April 1998
Foreword
This European Telecommunication Standard (ETS) has been produced by the Signalling Protocols and
Switching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).
This ETS is part 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 and
videotelephony 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".
Transposition dates
Date of adoption of this ETS: 20 March 1998
Date of latest announcement of this ETS (doa): 31 July 1998
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 January 1999
Date of withdrawal of any conflicting National Standard (dow): 31 January 1999

Page 8
ETS 300 267-6: April 1998
Blank page
Page 9
ETS 300 267-6: April 1998
1 Scope
This sixth part of ETS 300 267 specifies the Abstract Test Suite (ATS) and partial Protocol Implementation
eXtra Information for Testing (PIXIT) proforma for the Network side of the T reference point or coincident
S and T reference point (as defined in ITU-T Recommendation I.411 [13]) of implementations conforming
to the stage three standard of the telephony 7 kHz and videotelephony teleservices for the pan-European
Integrated 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 ATS
and partial PIXIT proforma specification. Other parts specify the TSS&TP and the ATS and partial PIXIT
proforma for the User side of the T reference point or coincident S and T reference point of
implementations conforming to ETS 300 267-1 [3].
2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] ETS 300 102-1: "Integrated Services Digital Network (ISDN); User-network
interface layer 3; Specifications for basic call control".
[2] ETS 300 196-1 (1993): "Integrated Services Digital Network (ISDN); Generic
functional protocol for the support of supplementary services; Digital Subscriber
Signalling System No. one (DSS1) protocol; Part 1: Protocol specification".
[3] ETS 300 267-1 (1994) including A1 (1996): "Integrated Services Digital Network
(ISDN); Telephony 7 kHz and videotelephony teleservices; Digital Subscriber
Signalling System No. one (DSS1) protocol; Part 1: Protocol specification".
[4] ETS 300 267-2 (1996): "Integrated Services Digital Network (ISDN); Telephony
7 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 kHz
and 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); Digital
Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer
for circuit-mode basic call control; Part 1: Protocol specification [ITU-T
Recommendation Q.931 (1993), modified]".
[7] ETS 300 403-7: "Integrated Services Digital Network (ISDN); Digital Subscriber
Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-
mode basic call control; Part 7: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT) proforma specification for
the network".
[8] ISO/IEC 9646-1: "Information technology - OSI Conformance Testing
Methodology and Framework; Part 1: General Concepts".
[9] ISO/IEC 9646-2: "Information technology - OSI Conformance Testing
Methodology and Framework; Part 2: Abstract Test Suite Specification".

Page 10
ETS 300 267-6: April 1998
[10] ISO/IEC 9646-3: "Information technology - OSI Conformance Testing
Methodology and Framework; Part 3: The Tree and Tabular Combined
Notation".
[11] ISO/IEC 9646-4: "Information technology - OSI Conformance Testing
Methodology and Framework; Part 4: Test realization".
[12] ISO/IEC 9646-5: "Information technology - OSI Conformance Testing
Methodology and Framework; Part 5: Requirements on test laboratories and
clients for the conformance assessment process".
[13] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces -
Reference configurations".
3 Definitions and abbreviations
3.1 Definitions
For 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.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
BAS Bit rate Allocation Signal
CM Co-ordination Message
CP Co-ordination Point
CRC Cyclic Redundancy Check
ExTS Executable Test Suite
FAW Frame Alignment Word
IUT Implementation Under Test
LT Lower Tester
MOT Means Of Testing
MTC Main Test Component
PCO Point of Control and Observation
PCTR Protocol Conformance Test Report
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
PTC Parallel Test Component
SUT System Under Test
TP Test Purpose
TSS Test Suite Structure
TTCN Tree and Tabular Combined Notation
UT Upper Tester
4 Introduction
Implementations Under Test (IUTs) which are to be tested using this ATS are required to have previously
been 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 this
ATS. Behaviours in test cases have been described in such a way to be able to take into account both
ETS 300 102-1 [1] and ETS 300 403-1 [6] basic call standards. This ATS also takes into account
messages defined for the supplementary services, in particular ETS 300 196-1 [2]. When such messages
are received, they are ignored by the ATS as this is not within the scope of this ETS.

Page 11
ETS 300 267-6: April 1998
5 Abstract Test Method (ATM)
5.1 Description of ATM used
This ATS describes the testing specification of the protocol procedures and switching functions needed to
support the videotelephony and telephony 7 kHz teleservices at T or coincident S and T reference points
for 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 is
the 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, it
is considered that 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 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 a
real test suite would be constructed. Such a test method specifies behaviour at multiple network
interfaces. One very important limitation here is that tests are focused on one particular interface. Thus
the test system is made up of one Main Test Component (MTC) and one or more Parallel Test
Components (PTC), see figure 1. No actual testing is performed by the MTC, as all Points of Control and
Observation (PCOs) are on the PTCs.
5.2 Conventions for test components and PCOs
Figure 1 shows a logical view of the complete configuration of the MTC, PTCs, and PCOs. The
Co-ordination Point (CP) relationships between the various components are also indicated. In a
master/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 the
testing process, i.e. "how to make the IUT send the required message".
PTCM
MTC
CPM1 CPMT
CPM0
CP0T
CP01
PTCs
PTC0 PTC1 PTCT
Master Slave
Part Part
L0 L1
T
PCOs
TESTER
IUT
Network
Figure 1: Multi-party test method

Page 12
ETS 300 267-6: April 1998
This means, in particular, that the verdict FAIL will only be assigned from the protocol aspects observed
on the interface under test (i.e. by PTC0), as it would be observed by a terminal connected to this
interface. A failure in the correlation between the protocol at the different interfaces to which the different
testers 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 has
received the proper stimulus, the verdict will be INCONCLUSIVE.
The MTC, PTCM, handles all scheduling of test components and exchanges messages with PTCs to start
or to stop the running of their associated tree. There are communication paths or CPs between the MTC
and 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 behaviour
of the IUT and test case verdicts are assigned depending on the behaviour observed at this PCO. The
PTCs 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 or
INCONCLUSIVE 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 events at L1 or T will result in INCONCLUSIVE rather than FAIL verdicts being assigned.
5.3 Description of PCOs
The PCOs are used to control and observe the behaviour of the IUT. Preliminary test case verdicts are
assigned depending on the behaviour observed at those points. The final verdict is set by the MTC at the
end of the test.
5.3.1 D-channel PCOs
For the D-channel, the PCOs reside at the service access point between layers 2 and 3. These PCOs are
named "L0" and "L1". The same Abstract Service Primitives (ASPs) as defined in ETS 300 403-7 [7] are
used.
PTC0 SUT PTC1
Layer 3 IUT Layer 3
 L0      L1 
Layer 2 Layer 2
          
Layer 1 Layer 1
Service provider
Figure 2: Combination of the remote and multi-party test methods without interworking with PSTN

Page 13
ETS 300 267-6: April 1998
5.3.2 PSTN PCO
For tests involving the PSTN, the PCOs used are L0 and T. L0 is at the same location as in figure 2 and T
is located at the upper tester at the access point between the test operator and the IUT.
PTC0 SUT PTCT
T
Layer 3 IUT
 L0       
Layer 2
         
Layer 1
Service provider PSTN
Figure 3: Combination of the remote and multi-party test methods with interworking with PSTN
5.4 Naming conventions
5.4.1 Test cases
The 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:
1 for Originating interface (ORIG);
2 for Destination interface (DEST);
- the second digit refers to the third test group level:
1 Valid behaviour (BV);
2 Invalid behaviour (BI);
3 Inopportune behaviour (BO);
- the third digit refers to the fifth test group level:
1 Fallback allowed (FBA);
2 Fallback not allowed (FBN);
3 Connection 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.

Page 14
ETS 300 267-6: April 1998
5.4.2 Variables and parameters
The following shows the naming convention for variables used for each B-channel depending on whether
one or two B-channels are established during the call between PTC0 and PTC1.
PTC0
Initial B-channel
call reference CREF
B-channel (basic) B_CHN
channel nr (primary) PX_CH_NUM
Additional B-channel
call reference CREF2
B-channel (basic) B_CHN2
channel nr (primary) PX_CH_NUM2
PTC1
Initial B-channel
call reference P1CREF
B-channel (basic) P1_B_CHN
channel nr (primary) PX_CH_NUM
Additional B-channel
call reference P1CREF2
B-channel (basic) P1_B_CHN2
channel nr (primary) PX_CH_NUM2
The following shows the naming conventions for parameters used to address the PTCs.
PTC Parameters
PTC0 PX_PSTN_LCPN,
PX_PSTN_CDPN_OCTET3,
PX_PSTN_CPN
PTC1 PX_PTC1_LCPN,
PX_PTC1_CDPN_OCTET3,
PX_PTC1_CPN
PTCT PX_PSTN_LCPN,
PX_PSTN_CDPN_OCTET3,
PX_PSTN_CPN
5.4.3 Trees and subtrees
Test 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 be
0 or 1 depending on the PTC for which this subtree is defined.
6 Untestable test purposes
TPs for generic protocol requirements do not correspond to specific protocol behaviour and only describe
parts of ETS 300 267-1 [3] which support the telephony 7 kHz and videotelephony teleservices. These
TPs have been considered as untestable.

Page 15
ETS 300 267-6: April 1998
7 ATS conventions
This clause is structured similarly to the structure of a TTCN ATS. However, the names of the subclauses
are arranged in a way more suitable to this ETS.
7.1 Declarations part
7.1.1 Type definitions
7.1.1.1 Simple type definitions
Where 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 length
restriction 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.2 Structured type definitions
7.1.1.2.1 TTCN structured type definitions
All 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 simple
type where the value list is restricted to the single value which is the identifier itself. This has the
advantage that it allows a test system derived from this ATS to easily identify information elements
embedded in messages. An ATS where information element identifiers are represented as unrestricted
types can present difficulties for a derived test system in the case where it needs to find one information
element embedded in a number of others and the constraints for the other elements have the any-or-omit
value. In such a case the test system cannot easily find the beginning of each information element.
7.1.1.2.2 ASN.1 structured type definitions
There are no ASN.1 structured type definitions in the ATS.
7.1.1.3 ASP type definitions
7.1.1.3.1 TTCN ASP type definitions
TTCN ASP type definitions only contain one PDU or no PDU at all.
All TTCN ASP type definitions are provided with a full identifier.

Page 16
ETS 300 267-6: April 1998
Some ASPs are not parameterized as shown in the example in table 1. Such ASPs are only used for
requesting or receiving service from the lower layer.
Table 1: TTCN ASP type definition DL_REL_IN
TTCN ASP Type Definition
ASP NAME : DL_REL_IN
(DL-RELEASE-INDICATION)
PCO Type : SAP
Comments : CEId: = (SAPI,CES) mapped onto DLCI: = (SAPI,TEI)
This ASP is used to confirm the termination of an established multiple frame
operation or to report an unsuccessful establishment attempt (L2--->L3)
Parameter Name           |   Parameter Type    |    Comments
Detailed Comments :
Table 2 shows an example of a parameterized ASP. All ASPs containing PDUs contain only that PDU and
no other parameters.
Table 2: TTCN ASP type definition DL_DATA_RQ
TTCN ASP Type Definition
ASP NAME : DL_DAT_RQ
(DL_DATA_REQUEST)
PCO Type : DSAP
Comments :
Parameter Name           |   Parameter Type    |    Comments
mun (MessageUnit)         |PDU            |
Detailed Comments :
To make TTCN more readable, aliases have been defined for ASPs.
7.1.1.3.2 ASN.1 ASP type definitions
There are no ASN.1 ASP type definitions in the ATS.
7.1.1.4 PDU type definitions
7.1.1.4.1 TTCN PDU type definitions
The TTCN PDU type reflects the actual data being transferred or received. All PDUs are embedded in
ASPs.
A meta-type ASP has been defined for all messages which do not require the fields inside to be
referenced. This meta-type ASP carries the parameter type PDU. There is one meta-type ASP for send
events and one for receive events, named DL_DAT_RQ and DL_DAT_IN, respectively. If certain fields of
a PDU have to be referenced, then a particular ASP type has been defined for that message. For
example, the call reference of an outgoing SETUP message needs to be read by the tester and therefore
the ASP type DL_DAT_IN_SETUP has been defined for this event.
7.1.1.4.2 ASN.1 PDU type definitions
There are no ASN.1 PDU type definitions in the ATS.
7.1.2 Test suite constants
Each test suite constant is defined in terms of a predefined type. The values given in the value column will
remain unchanged throughout the ATS.
7.1.3 Test suite parameters
Each test suite parameter is defined in terms of a predefined type or a referenced type. A referenced type
is used when it is necessary to attach restrictions to these type definitions (it is not allowed to include
restrictions directly in the test suite parameter table). The referenced type can have a length or value
restriction attached to it in its declaration table.

Page 17
ETS 300 267-6: April 1998
7.1.4 Variables
7.1.4.1 Test suite variables
No test suite variables are used or defined in the ATS. In concurrent TTCN these kind of variables can be
used only by the MTC.
7.1.4.2 Test case variables
Each test case variable is defined in terms of a predefined type or a referenced type. A referenced type is
used when it is necessary to attach restrictions to these type definitions (it is not allowed to include
restrictions directly in the test case variable table). The referenced type can have a length or value
restriction attached to it in its declaration table.
7.1.5 Test suite operation definitions
The description part of a test suite operation definition uses either natural language or meta C.
Table 3: Test suite operation definition ASSIGN_CHI
Test Suite Operation Definition
Operation Name : ASSIGN_CHI(basic, primary : CHI; basic_flag : BOOLEAN)
Result Type  : CHI
Comments    : This operation is used to assign a correct Channel identification information
element to PDUs dependent on the type of access that is tested.
Description
CHI ASSIGN_CHI(basic,primary,basic_flag)
If the value of the basic_flag is set to TRUE, the result of the operation ASSIGN_CHI will be
the value represented by the parameter basic which is of type CHI. Else the operation results in
the value represented by the parameter primary.
Examples:
ASSIGN_CHI(CHI1b_R1, CHI1p_R1, TRUE) = CHI1b_R1
ASSIGN_CHI(CHI1b_R1, CHI1p_R1, FALSE) = CHI1p_R1
Detailed comments :
The Test Suite Operation Definition shown in table 3 is used in the Constraints Part when assigning an
element of type CHI a value. The CHI type can be defined in two ways depending on whether the ATS is
testing Basic or Primary-rate access. To avoid duplicate types and thereby duplicate test cases this
operation is used to assign a value to an element of CHI type. It takes three parameters:
SULPDU\DFRQVWUDLQWRIW\SH&+,YDOLGIRUSULPDU\UDWHDFFHVV
EDVLFDFRQVWUDLQWRIW\SH&+,YDOLGIRUEDVLFDFFHVV
EDVLFBIODJD%RROHDQYDOXH758(LIEDVLFDFFHVVLVDSSOLFDEOH)$/6(RWKHUZLVH
This operation returns the correct constraint according to the Boolean flag basic_flag. That constraint will
then be assigned to the specific element of type CHI.
7.2 Constraints part
7.2.1 Structured type constraint declaration
For every structured type definition there exists one or more structured type constraint.
7.2.2 ASN.1 type constraint declaration
There are no ASN.1 type constraint declarations in the ATS.
7.2.3 ASP type constraint declaration
7.2.3.1 ASN.1 ASP type constraint declaration
There are no ASN.1 ASP type constraint declarations in the ATS.

Page 18
ETS 300 267-6: April 1998
7.2.3.2 TTCN ASP type constraint declaration
The PDUs to be sent or received are passed to the TTCN ASP constraint declarations Ms and Mr as
parameters of meta type PDU. Only if values inside a specific PDU have to be referenced, the use of the
meta type PDU is not allowed according to ISO/IEC 9646-3 [10]. In such cases different TTCN ASP
constraint declarations are used, which are defined to carry only a specific type of PDU (e.g. SETUP).
Table 4 shows an example of such a TTCN ASP constraint declaration.
Table 4: TTCN ASP constraint declaration Sr
TTCN ASP Constraint Declaration
Constraint Name : Sr(PARAM: SETUP_PDU)
ASP Type    : DL_DAT_IN_SETUP
Derivation Path :
Comments    : ASP to indicate the receipt of SETUP messages.
Parameter Name           |   Parameter Value    |    Comments
mun                |PARAM           |
Detailed Comments :
All ASP constraints have a specific value for its parameter. No matching symbols are used in ASP
constraints.
7.2.4 PDU type constraint declaration
7.2.4.1 ASN.1 PDU type constraint declaration
There are no ASN.1 PDU type constraint declarations in the ATS.
7.2.4.2 TTCN PDU type constraint declaration
PDU constraints are used for assigning values or patterns to the data being sent or received.
7.2.5 Derived constraint
Derived constraints are used in the ATS for PDUs only.
7.2.6 Parameterized constraints
Parameterized constraints are used in the ATS.
7.2.7 Value assignment
7.2.7.1 Specific values
For specific value assignment both explicit values and references to explicit values are used.
7.2.7.2 Matching values
As matching values the following mechanisms are used:
Instead of value:
AnyOrOmit "*"
AnyValue "?"
SuperSet SUPERSET
Omit "-"
Inside value:
AnyOne "?"
AnyOrNone "*"
Page 19
ETS 300 267-6: April 1998
7.3 Dynamic part
7.3.1 Test cases
Each test case contains:
- as purpose, the reference of the test purpose from ETS 300 267-5 [5];
- as description, the relevant references to ETS 300 267-1 [3];
- as behaviour description, at least a main tree for the MTC to handle the execution of other PTC’s
subtrees and a subtree for PTCO to describe the expected behaviour. When there is interworking
with PSTN network, subtrees for PTC1 or PTCT are added.
The check of tone and announcements by an operator is optional.
7.3.2 Test steps
Much use has been made of test steps to avoid needless repetition of dynamic behaviour. The MTC
behaviour is specified in three test steps which correspond to the three potential test configurations, i.e.
CONTROL_PTC0, CONTROL_PTC0_PTC1 and CONTROL_PTC0_PTCT. The PTC behaviour is
described in three test step groups, PTC0, PTC1 and PSTN.
7.3.2.1 PTC1_IN, PTC1_2B_IN
These test steps describe the behaviour of PTC1 for support of an incoming call at PTC0. Thus PTC1 is
the originator of the call. PTC1 receives a Co-ordination Message (CM) from PTC0 in order to send the
SETUP message which begins the call establishment. The test step is terminated by receipt of a
RELEASE message or by an appropriate RELEASE_CALL CM from the PTC0.
PTC1_2B_IN is used for an incoming call requiring two B-channels.
7.3.2.2 PTC1_OUT, PTC1_BCAP_OUT, PTC1_BCAP_HLC_OUT, PTC1_2B_OUT
These test steps describe the behaviour of PTC1 for support of an outgoing call at the MTC (served user
side). Thus PTC1 is at the destination side of the call. The test step is terminated by receipt of a
RELEASE message or by an appropriate RELEASE_CALL CM from PTC0.
The behaviour is regulated from the MTC by means of CMs sent via CP01. Thus if PTC1 is expected to
receive a message it receives a CM beforehand telling it what message to expect. On the other hand if the
PTC0 wishes to receive a message from the IUT it may do this by first sending a CM to PTC1.
With PTC1_2B_OUT, two B-channels can be established for the same call.
With PTC1_BCAP_OUT, PTC1_BCAP_HLC_OUT, Bearer capability and High layer compatibility
information elements sent by PTC1 in the CONNECT message are parametrized. With PTC1_OUT, no
Bearer capability and no High layer compatibility information elements are sent in the CONNECT
message. PTC1_BCAP_OUT, PTC1_BCAP_HLC_OUT and PTC1_OUT are used depending on whether
fallback occurs or not.
7.3.3 Defaults
Note the use of the RETURN statement which is defined in DAM1 of ISO/IEC 9646-3 [10]. This allows
valid background behaviour to be handled in the default tree with a possibility to return to the original set of
alternatives in the test case.

Page 20
ETS 300 267-6: April 1998
8 ATS to TP map
The identifiers TTPnnn_nn and VTPnnn_nn used for TPs become TTCnnn_nn and VTCnnn_nn for
associated test cases. The numbering is unchanged, only the requirement part has been changed. Thus
there is a straightforward one-to-one mapping.
9 PCTR conformance
A test laboratory, when requested by a client to produce a PCTR, is required, as specified in
ISO/IEC 9646-5 [12], to produce a PCTR conformant with the PCTR template given in annex B of
ISO/IEC 9646-5 [12].
Furthermore, a test laboratory, offering testing for the ATS specification contained in annex C, when
requested by a client to produce a PCTR, is required to produce a PCTR conformant with the PCTR
proforma contained in annex A of this ETS.
A PCTR which conforms to this PCTR proforma specification shall preserve the content and ordering of
the clauses contained in annex A. Clause A.6 of the PCTR may contain additional columns. If included,
these shall be placed to the right of the existing columns. Text in italics may be retained by the test
laboratory.
10 PIXIT conformance
A test realizer, producing an executable test suite for the ATS specification contained in annex C, is
required, as specified in ISO/IEC 9646-4 [11], to produce an augmented partial PIXIT proforma
conformant with this partial PIXIT proforma specification.
An augmented partial PIXIT proforma which conforms to this partial PIXIT proforma specification shall, as
a minimum, have contents which are technically equivalent to annex B. The augmented partial PIXIT
proforma may contain additional questions that need to be answered in order to prepare the Means Of
Testing (MOT) for a particular IUT.
A test laboratory, offering testing for the ATS specification contained in annex C, is required, as specified
in ISO/IEC 9646-5 [12], to further augment the augmented partial PIXIT proforma to produce a PIXIT
proforma conformant with this partial PIXIT proforma specification.
A PIXIT proforma which conforms to this partial PIXIT proforma specification shall, as a minimum, have
contents which are technically equivalent to annex B. The PIXIT proforma may contain additional
questions that need to be answered in order to prepare the test laboratory for a particular IUT.
11 ATS conformance
The test realizer, producing MOT and ExTS for this ATS specification, shall comply with the requirements
of ISO/IEC 9646-4 [11]. In particular, these concern the realization of an ExTS based on each ATS. The
test realizer shall provide a statement of conformance of the MOT to this ATS specification.
An ExTS which conforms to this ATS specification shall contain test groups and test cases which are
technically equivalent to those contained in the ATS in annex C. All sequences of test events comprising
an abstract test case shall be capable of being realized in the executable test case. Any further checking
which the test system might be capable of performing is outside the scope of this ATS specification and
shall not contribute to the verdict assignment for each test case.
Test laboratories running conformance test services using this ATS shall comply with
ISO/IEC 9646-5 [12].
A test laboratory which claims to conform to this ATS specification s
...