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

Integrated Services Digital Network (ISDN); Telephony 7 kHz and videotelephony teleservices; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the user

DE/SPS-05048-4

Digitalno omrežje z integriranimi storitvami (ISDN) - Daljinski storitvi: telefonija 7 kHz in videotelefonija - Protokol digitalne naročniške signalizacije št. 1 (DSS1) - 4. del: Abstraktni preskušalni niz (ATS) in delna dodatna informacija za preskušanje izvedbe protokola (PIXIT) - Proforma specifikacije za uporabnika

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-4:1998 - Integrated Services Digital Network (ISDN); Telephony 7 kHz and videotelephony teleservices; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the user

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 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the user33.020Telekomunikacije na splošnoTelecommunications in generalICS:Ta slovenski standard je istoveten z:ETS 300 267-4 E13SIST ETS 300 267-4:1998en01-DSULO-19983SIST ETS 300 267-4:1998SLOVENSKI
STANDARD
DRAFTEUROPEANprETS 300 267-4TELECOMMUNICATIONApril 1997STANDARDSource: ETSI TC-SPSReference: DE/SPS-05048-4ICS:33.020Key words:ISDN, DSS1, teleservice, 7 kHz, video, telephony, testing, ATS, PIXIT, userIntegrated Services Digital Network (ISDN);Telephony 7 kHz and videotelephony teleservices;Digital Subscriber Signalling System No. one (DSS1) protocol;Part 4: Abstract Test Suite (ATS) and partial ProtocolImplementation eXtra Information for Testing (PIXIT) proformaspecification for the userETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail].: [phone] - Fax: [phone]Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1997. All rights reserved.SIST ETS 300 267-4:1998

Page 2Draft prETS 300 267-4: 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-4:1998

Page 3Draft prETS 300 267-4: April 1997ContentsForeword.71Scope.92Normative references.93Definitions and abbreviations.103.1Definitions.103.2Abbreviations.104Introduction.115Abstract Test Method (ATM).115.1Description of ATM used.115.2Conventions for test components and PCOs.115.3Description of PCOs.125.3.1D-channel PCO.125.3.2B-channels PCOs.135.4Naming conventions.135.4.1Test cases.135.4.2Variables and parameters.145.4.3Trees and subtrees.146Untestable test purposes.147ATS conventions.147.1Declarations part.147.1.1Type definitions.147.1.1.1Simple type definitions.147.1.1.2Structured type definitions.147.1.1.2.1TTCN structured type definitions.147.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.157.1.1.4PDU type definitions.157.1.1.4.1TTCN PDU type definitions.157.1.1.4.2ASN.1 PDU type definitions.167.1.2Test suite constants.167.1.3Test suite parameters.167.1.4Variables.167.1.4.1Test suite variables.167.1.4.2Test case variables.167.1.5Test suite operation definitions.167.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.177.2.4PDU type constraint declaration.177.2.4.1ASN.1 PDU type constraint declaration.177.2.4.2TTCN PDU type constraint declaration.177.2.5Derived constraints.177.2.6Parameterized constraints.18SIST ETS 300 267-4:1998

Page 4Draft prETS 300 267-4: April 19977.2.7Value assignment.187.2.7.1Specific values.187.2.7.2Matching values.187.3Dynamic part.187.3.1Test cases.187.3.2Test steps.187.3.3Defaults.187.3.4Synchronization.188ATS 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.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.2Configuration to be tested.27B.6.3Actions required to stimulate IUT.28B.6.4Test management timers.28B.6.5Parameter values.29SIST ETS 300 267-4:1998

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

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

Page 7Draft prETS 300 267-4: 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 4 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 forTesting (PIXIT) proforma specification for the user";Part 5:"TSS&TP specification for the network";Part 6:"ATS and partial PIXIT proforma specification for the network".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-4:1998

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

Page 9Draft prETS 300 267-4: April 19971ScopeThis fourth part of ETS 300 267 specifies the Abstract Test Suite (ATS) and partial ProtocolImplementation eXtra Information for Testing (PIXIT) proforma for the User side of the T reference pointor coincident S and T reference point (as defined in ITU-T Recommendation I.411 [17]) ofimplementations conforming to the stage three standard of the telephony 7 kHz and videotelephonyteleservices for the pan-European Integrated Services Digital Network (ISDN) by means of the DigitalSubscriber Signalling System No. one (DSS1) protocol, ETS 300 267-1 [6].ETS 300 267-3 [8] 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 Network side of the T reference point or coincident S and T reference point ofimplementations conforming to ETS 300 267-1 [6].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 143: "Integrated Services Digital Network (ISDN); Audiovisual services;Inband signalling procedures for audiovisual terminals using digital channels upto 2 048 kbit/s".[3]ETS 300 144: "Integrated Services Digital Network (ISDN); Audiovisual services;Frame structure for a 64 kbit/s to 1 920 kbit/s channel and associated syntax forinband signalling" (equivalent to ITU-T Recommendation H.221).[4]ETS 300 145: "Integrated Services Digital Network (ISDN); Audiovisual services;Videotelephone systems and terminal equipment operating on one or two64 kbit/s channels".[5]ETS 300 196-1: "Integrated Services Digital Network (ISDN); Generic functionalprotocol for the support of supplementary services; Digital Subscriber SignallingSystem No. one (DSS1) protocol; Part 1: Protocol specification".[6]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".[7]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".[8]ETS 300 267-3: "Integrated Services Digital Network (ISDN); Telephony 7 kHzand videotelephony teleservices; Digital Subscriber Signalling System No. one(DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP)specification for the user".[9]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]".SIST ETS 300 267-4:1998

Page 10Draft prETS 300 267-4: April 1997[10]ETS 300 403-5: "Integrated Services Digital Network (ISDN); Digital SubscriberSignalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 5: Abstract Test Suite (ATS) and partial ProtocolImplementation eXtra Information for Testing (PIXIT) proforma specification forthe user".[11]I-ETS 300 763-2: "Integrated Services Digital Network (ISDN); Audiovisualservices in-band signalling testing; Part 2: Abstract Test Suite (ATS) and partialProtocol Implementation eXtra Information for Testing (PIXIT) proforma".[12]ISO/IEC 9646-1: "Information technology - OSI Conformance TestingMethodology and Framework; Part 1: General Concepts".[13]ISO/IEC 9646-2: "Information technology - OSI Conformance TestingMethodology and Framework; Part 2: Abstract Test Suite Specification".[14]ISO/IEC 9646-3: "Information technology - OSI Conformance TestingMethodology and Framework; Part 3: The Tree and Tabular CombinedNotation".[15]ISO/IEC 9646-4: "Information technology - OSI Conformance TestingMethodology and Framework; Part 4: Test realization".[16]ISO/IEC 9646-5: "Information technology - OSI Conformance TestingMethodology and Framework; Part 5: Requirements on test laboratories andclients for the conformance assessment process".[17]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 [6] and ISO/IEC 9646, parts 1 [12]to 5 [16] and the following definitions apply:additional B-channel: The second or subsequent B-channel established in a videotelephony call.initial B-channel: The first channel established in a videotelephony call.3.2AbbreviationsFor the purposes of this ETS, the following abbreviations apply:ASPAbstract Service PrimitiveATMAbstract Test MethodATSAbstract Test SuiteBASBit rate Allocation SignalCESConnection Endpoint SuffixCMCo-ordination MessageCPCo-ordination PointCRCCyclic Redundancy CheckExTSExecutable Test SuiteFAWFrame Alignment WordIUTImplementation Under TestLTLower TesterSIST ETS 300 267-4:1998

Page 11Draft prETS 300 267-4: April 1997MOTMeans 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 [9],and the ATS related to ETS 300 143 [2], ETS 300 144 [3] and ETS 300 145 [4] which is contained inI-ETS 300 763-2 [11]].Any messages or fields within messages which are introduced by ETS 300 403-1 [9] 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 [9] basic call standards. This ATS also takes into accountmessages defined for the supplementary services, in particular ETS 300 196-1 [5]. When such messagesare received, they are ignored by the ATS as this is not within the scope of this ETS.5Abstract 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 user.Testing activity will take place on the D-channel and on one or two B-channels depending on whichteleservice is supported and where the service is provided. The videotelephony teleservice can imply up totwo B-channels and telephony 7 kHz teleservice up to one B-channel. Only S and T reference point hasan associated in-band protocol entity and has to follow requirements on B-channels.As a consequence of testing multiple channels simultaneously, the concurrent testing method is used. Atest configuration includes at least a master test component, a Parallel Test Component (PTC) for theD-channel and eventually one or two PTCs for each involved B-channel. No actual testing is performed bythe Main Test Component (MTC), as all Points of Control and Observation (PCOs) are on the PTCs. Theremote test method as defined in ISO/IEC 9646-2 [13] is applied in each PTC.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. The testmethod used is very close to the test method used in I-ETS 300 763-2 [11].SIST ETS 300 267-4:1998

Page 12Draft prETS 300 267-4: April 1997TC_MasterTC_DTC_B1TC_B2B2LB1LS/T busB-channelsD-channelCP_B1_D CP_Master_DCP_Master_B1CP_Master_B2MTCPTCsPCOsDLIUTTESTERFigure 1: Multi-party test methodIn a master/slave arrangement, the MTC is considered to be the master while the PTCs are the slaves.There are communication paths or CPs between the MTC and each PTC, and also between D-channelPTC and the initial B-channel PTC. The MTC handles all scheduling of test components and exchangesmessages with PTCs to start or to stop the running of their associated tree. Messages between TC_D andTC_B1 concern more functional synchronization like advising the initial B-channel that it can expand themode on two B-channels when the additional B-channel is set up by the TC_D.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 PCOFor the D-channel, the PCO resides at the service access point between layers 2 and 3. This PCO isnamed "DL" (L for Lower). The same Abstract Service Primitives (ASPs) as defined in ETS 300 403-5 [10]are used.LTSUTLayer 3IUTPCO DLLayer 2Layer 2Layer 1Layer 1Service providerFigure 2: Remote test methodSIST ETS 300 267-4:1998

Page 13Draft prETS 300 267-4: April 19975.3.2B-channels PCOsFor the in-band signalling protocol there is no explicit layered structure. However, there is an implicitlydefined structure: a lower layer dealing with frame and multiframe structure, bit encoding of BAS codesand their corresponding CRC codes, FAW etc., and a higher layer dealing with the various sequences andprocedures which make use of BAS codes to control the communication.Lower layer PCOs and the corresponding declarations have been reused from the ATS specified inI-ETS 300 763-2 [11]. When a test case needs description behaviour at a higher layer which cannot beeasily expressed at a lower layer, e.g. a complete initialization procedure, and because it is not thepurpose of this ATS to check in-band signalling, references to the test step included in the ATS specifiedin I-ETS 300 763-2 [11] are made instead of importing all of the ASN.1 descriptions.The audio and video signal contents in the frames and multiframes are ignored. Audio encoding/decodingis out of scope of this ETS and requires specific test tools. As it is not possible to analyse the unframedmode, this is not described in this ETS.In the B-channel, frames or multiframes are required to be sent and received continuously to maintainframe alignment and this is achieved by looping until the expected frame or multiframe is received or thetimer expires.A procedure for the detection of incorrect CRC4 is described in this ATS. This depends on the detection ofan ASP which is generated when the tester implements CRC4 and detects incorrect bit values in bitsC1-C4.5.4Naming conventions5.4.1Test casesTest cases have exactly the same reference as the corresponding combined test purpose, seeETS 300 267-3 [8].The structure of a test case identifier is as follows:CT_test case covering a telephony 7 kHz requirement;CV_test case covering a videotelephony requirement.The digits correspond to the digits of the first Test Purpose (TP) included in the combined TP. The TPsare 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 Calling user interface (ORIG);2for Called user 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-4:1998

Page 14Draft prETS 300 267-4: April 19975.4.2Variables and parametersVariables used in PTCs associated to B-channels are prefixed by the letter B.TC_Dcall referenceCREFchannel nrB_CHN1call referenceCREF2channel nrB_CHN25.4.3Trees and subtreesTest case trees and subtrees are prefixed by "d_" when they describe the behaviour at PTC TC_D, by"b1_" for PTC TC_B1 and "b2_" for PTC TC_B2.Test step names use upper case letters and local subtrees use lower case letters.Preamble subtrees are prefixed by "PR_" and postamble subtrees by "PO_".6Untestable test purposesCombined TPs correspond only to testable TPs and are all covered by the ATS.TPs for generic protocol requirements do not correspond to specific protocol behaviour and only describeparts of ETS 300 267-1 [6] which support the telephony 7 kHz and videotelephony teleservices. TheseTPs have been considered as untestable. Furthermore, TPs which test an unframed mode in theB-channel or an internal behaviour of the IUT have also been considered as untestable.7ATS 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.SIST ETS 300 267-4:1998

Page 15Draft prETS 300 267-4: April 1997For 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.Some ASPs are not parameterized as shown in the example in table 1. Such ASPs are only used forrequesting or receiving service from the B-channel lower layer.Table 1: TTCN ASP type definition SEND_UNFRAMEDTTCN ASP Type DefinitionASP NAME : SEND_UNFRAMEDPCO Type : BSAPComments :Tester will send in unframed mode continuously until another send event occursParameter 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 for the D-channel areembedded in ASPs. For the B-channel, because no ASP has been defined for the in-band signallingprotocol, frames or multiframes are sent and received on their own.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. ForSIST ETS 300 267-4:1998

Page 16Draft prETS 300 267-4: April 1997example, 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
...

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]DXSRUDEQLND
Integrated Services Digital Network (ISDN); Telephony 7 kHz and videotelephony
teleservices; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 4:
Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for
Testing (PIXIT) proforma specification for the user
Ta slovenski standard je istoveten z: ETS 300 267-4 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-4
TELECOMMUNICATION April 1998
STANDARD
Source: SPS Reference: DE/SPS-05048-4
ICS: 33.020
Key words: ISDN, DSS1, teleservice, 7 kHz, video, telephony, testing, ATS, PIXIT, user
Integrated Services Digital Network (ISDN);
Telephony 7 kHz and videotelephony teleservices;
Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 4: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT) proforma
specification for the user
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
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-4: 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-4: 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.11
5 Abstract Test Method (ATM).11
5.1 Description of ATM used .11
5.2 Conventions for test components and PCOs.12
5.3 Description of PCOs .12
5.3.1 D-channel PCO .12
5.3.2 B-channels PCOs.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 .14
7.1 Declarations part.14
7.1.1 Type definitions .14
7.1.1.1 Simple type definitions.14
7.1.1.2 Structured type definitions .14
7.1.1.2.1 TTCN structured type definitions .14
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 .15
7.1.1.4 PDU type definitions .15
7.1.1.4.1 TTCN PDU type definitions.15
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 .16
7.1.4.1 Test suite variables.16
7.1.4.2 Test case variables.16
7.1.5 Test suite operation definitions.16
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.17
7.2.4 PDU type constraint declaration.17
7.2.4.1 ASN.1 PDU type constraint declaration.17
7.2.4.2 TTCN PDU type constraint declaration .17
7.2.5 Derived constraints.17
7.2.6 Parameterized constraints.18

Page 4
ETS 300 267-4: April 1998
7.2.7 Value assignment . 18
7.2.7.1 Specific values . 18
7.2.7.2 Matching values . 18
7.3 Dynamic part . 18
7.3.1 Test cases . 18
7.3.2 Test steps . 18
7.3.3 Defaults. 18
7.3.4 Synchronization . 18
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. 24
Annex B (normative): Partial PIXIT proforma . 25
B.1 Identification summary. 25
B.2 Abstract test suite summary . 25
B.3 Test laboratory. 25
B.4 Client (of the test laboratory) . 26
B.5 System Under Test (SUT) . 26
B.6 Protocol information. 27
B.6.1 Protocol identification . 27
B.6.2 Configuration to be tested .27
B.6.3 Actions required to stimulate IUT. 28
B.6.4 Test management timers . 28
B.6.5 Parameter values . 29

Page 5
ETS 300 267-4: April 1998
Annex C (normative): Abstract Test Suite (ATS).30
C.1 The TTCN Graphical form (TTCN.GR) .30
C.2 The TTCN Machine Processable form (TTCN.MP) .30
Annex D (informative): General structure of ATS.31
History.32

Page 6
ETS 300 267-4: April 1998
Blank page
Page 7
ETS 300 267-4: 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 4 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-4: April 1998
Blank page
Page 9
ETS 300 267-4: April 1998
1 Scope
This fourth part of ETS 300 267 specifies the Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT) proforma for the User side of the T reference point
or coincident S and T reference point (as defined in ITU-T Recommendation I.411 [17]) 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 [6].
ETS 300 267-3 [8] 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 Network side of the T reference point or coincident S and T reference point of
implementations conforming to ETS 300 267-1 [6].
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 143: "Integrated Services Digital Network (ISDN); Audiovisual services;
Inband signalling procedures for audiovisual terminals using digital channels up
to 2 048 kbit/s".
[3] ETS 300 144: "Integrated Services Digital Network (ISDN); Audiovisual services;
Frame structure for a 64 kbit/s to 1 920 kbit/s channel and associated syntax for
inband signalling" (equivalent to ITU-T Recommendation H.221).
[4] ETS 300 145: "Integrated Services Digital Network (ISDN); Audiovisual services;
Videotelephone systems and terminal equipment operating on one or two
64 kbit/s channels".
[5] ETS 300 196-1: "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".
[6] 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".
[7] 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".
[8] ETS 300 267-3: "Integrated Services Digital Network (ISDN); Telephony 7 kHz
and videotelephony teleservices; Digital Subscriber Signalling System No. one
(DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP)
specification for the user".
[9] 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]".

Page 10
ETS 300 267-4: April 1998
[10] ETS 300 403-5: "Integrated Services Digital Network (ISDN); Digital Subscriber
Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-
mode basic call control; Part 5: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT) proforma specification for
the user".
[11] I-ETS 300 763-2: "Integrated Services Digital Network (ISDN); Audiovisual
services in-band signalling testing; Part 2: Abstract Test Suite (ATS) and partial
Protocol Implementation eXtra Information for Testing (PIXIT) proforma".
[12] ISO/IEC 9646-1: "Information technology - OSI Conformance Testing
Methodology and Framework; Part 1: General Concepts".
[13] ISO/IEC 9646-2: "Information technology - OSI Conformance Testing
Methodology and Framework; Part 2: Abstract Test Suite Specification".
[14] ISO/IEC 9646-3: "Information technology - OSI Conformance Testing
Methodology and Framework; Part 3: The Tree and Tabular Combined
Notation".
[15] ISO/IEC 9646-4: "Information technology - OSI Conformance Testing
Methodology and Framework; Part 4: Test realization".
[16] 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".
[17] 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 [6] and ISO/IEC 9646, parts 1 [12]
to 5 [16] and the following definitions apply:
additional B-channel: The second or subsequent B-channel established in a videotelephony call.
initial B-channel: The first channel established in a videotelephony call.
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
CES Connection Endpoint Suffix
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
Page 11
ETS 300 267-4: April 1998
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 [9],
and the ATS related to ETS 300 143 [2], ETS 300 144 [3] and ETS 300 145 [4] which is contained in
I-ETS 300 763-2 [11].
Any messages or fields within messages which are introduced by ETS 300 403-1 [9] 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 [9] basic call standards. This ATS also takes into account
messages defined for the supplementary services, in particular ETS 300 196-1 [5]. When such messages
are received, they are ignored by the ATS as this is not within the scope of this ETS.
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 user.
Testing activity will take place on the D-channel and on one or two B-channels depending on which
teleservice is supported and where the service is provided. The videotelephony teleservice can imply up to
two B-channels and telephony 7 kHz teleservice up to one B-channel. Only S and T reference point has
an associated in-band protocol entity and has to follow requirements on B-channels.
As a consequence of testing multiple channels simultaneously, the concurrent testing method is used. A
test configuration includes at least a master test component, a Parallel Test Component (PTC) for the
D-channel and eventually one or two PTCs for each involved B-channel. No actual testing is performed by
the Main Test Component (MTC), as all Points of Control and Observation (PCOs) are on the PTCs. The
remote test method as defined in ISO/IEC 9646-2 [13] is applied in each PTC.

Page 12
ETS 300 267-4: April 1998
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. The test
method used is very close to the test method used in I-ETS 300 763-2 [11].
TC_Master
MTC
CP_Master_D CP_Master_B1 CP_Master_B2
TC_D TC_B1 TC_B2 PTCs
CP_B1_D
IUT
DL B1L B2L
PCOs
D-channel B-channels
S/T bus
TESTER
Figure 1: Multi-party test method
In a master/slave arrangement, the MTC is considered to be the master while the PTCs are the slaves.
There are communication paths or CPs between the MTC and each PTC, and also between D-channel
PTC and the initial B-channel PTC. The MTC handles all scheduling of test components and exchanges
messages with PTCs to start or to stop the running of their associated tree. Messages between TC_D and
TC_B1 concern more functional synchronization like advising the initial B-channel that it can expand the
mode on two B-channels when the additional B-channel is set up by the TC_D.
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 PCO
For the D-channel, the PCO resides at the service access point between layers 2 and 3. This PCO is
named "DL" (L for Lower). The same Abstract Service Primitives (ASPs) as defined in ETS 300 403-5 [10]
are used.
LT SUT
Layer 3 IUT
PCO DL
Layer 2 Layer 2
Layer 1 Layer 1
Service provider
Figure 2: Remote test method
Page 13
ETS 300 267-4: April 1998
5.3.2 B-channels PCOs
For the in-band signalling protocol there is no explicit layered structure. However, there is an implicitly
defined structure: a lower layer dealing with frame and multiframe structure, bit encoding of BAS codes
and their corresponding CRC codes, FAW etc., and a higher layer dealing with the various sequences and
procedures which make use of BAS codes to control the communication.
Lower layer PCOs and the corresponding declarations have been reused from the ATS specified in
I-ETS 300 763-2 [11]. When a test case needs description behaviour at a higher layer which cannot be
easily expressed at a lower layer, e.g. a complete initialization procedure, and because it is not the
purpose of this ATS to check in-band signalling, references to the test step included in the ATS specified
in I-ETS 300 763-2 [11] are made instead of importing all of the ASN.1 descriptions.
The audio and video signal contents in the frames and multiframes are ignored. Audio encoding/decoding
is out of scope of this ETS and requires specific test tools. As it is not possible to analyse the unframed
mode, this is not described in this ETS.
In the B-channel, frames or multiframes are required to be sent and received continuously to maintain
frame alignment and this is achieved by looping until the expected frame or multiframe is received or the
timer expires.
A procedure for the detection of incorrect CRC4 is described in this ATS. This depends on the detection of
an ASP which is generated when the tester implements CRC4 and detects incorrect bit values in bits
C1-C4.
5.4 Naming conventions
5.4.1 Test cases
Test cases have exactly the same reference as the corresponding combined test purpose, see
ETS 300 267-3 [8].
The structure of a test case identifier is as follows:
CT_ test case covering a telephony 7 kHz requirement;
CV_ test case covering a videotelephony requirement.
The digits correspond to the digits of the first Test Purpose (TP) included in the combined TP. 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 Calling user interface (ORIG);
2 for Called user 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-4: April 1998
5.4.2 Variables and parameters
Variables used in PTCs associated to B-channels are prefixed by the letter B.
TC_D
call reference CREF
channel nr B_CHN1
call reference CREF2
channel nr B_CHN2
5.4.3 Trees and subtrees
Test case trees and subtrees are prefixed by "d_" when they describe the behaviour at PTC TC_D, by
"b1_" for PTC TC_B1 and "b2_" for PTC TC_B2.
Test step names use upper case letters and local subtrees use lower case letters.
Preamble subtrees are prefixed by "PR_" and postamble subtrees by "PO_".
6 Untestable test purposes
Combined TPs correspond only to testable TPs and are all covered by the ATS.
TPs for generic protocol requirements do not correspond to specific protocol behaviour and only describe
parts of ETS 300 267-1 [6] which support the telephony 7 kHz and videotelephony teleservices. These
TPs have been considered as untestable. Furthermore, TPs which test an unframed mode in the
B-channel or an internal behaviour of the IUT have also been considered as untestable.
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.

Page 15
ETS 300 267-4: April 1998
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.
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 B-channel lower layer.
Table 1: TTCN ASP type definition SEND_UNFRAMED
TTCN ASP Type Definition
ASP NAME : SEND_UNFRAMED
PCO Type : BSAP
Comments :Tester will send in unframed mode continuously until another send event occurs
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 for the D-channel are
embedded in ASPs. For the B-channel, because no ASP has been defined for the in-band signalling
protocol, frames or multiframes are sent and received on their own.
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

Page 16
ETS 300 267-4: April 1998
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.
7.1.4 Variables
7.1.4.1 Test suite variables
In concurrent TTCN these kind of variables can be used only by the MTC. To check that the IUT can
achieve synchronization in a two B-channel communication, a shared counter is needed in order to send
multiframes with the same numbering in both B-channels. PTCs TC_B1 and TC_B2, corresponding to
each B-channel, are located on the same machine. Therefore, the test suite variables B_SEMAPHORE,
B_SMF_COUNTER and B_SMF_ADDC_COUNTER can be accessed by both PTCs. The
B_SEMAPHORE variable is used to prevent that the two PTCs update the B_SMF_ADDC_COUNTER
simultaneously. B_SMF_COUNTER and B_SMF_ADDC_COUNTER correspond to the counters for sub-
multiframes sent in the initial and the additional B-channels, respectively.
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.
Where test case variables are used in constraints, they are passed as formal parameters.
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 :
Page 17
ETS 300 267-4: April 1998
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.
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 [14]. 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 constraints
Derived constraints are used in the ATS for PDUs only.

Page 18
ETS 300 267-4: April 1998
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 "*"
7.3 Dynamic part
7.3.1 Test cases
Each test case contains:
- as purpose, the references to the included test purposes in the corresponding combined test
purpose from ETS 300 267-3 [8];
- as comment, a united text of the test purposes;
- as description, the relevant references to ETS 300 267-1 [6];
- as behaviour description, at least a main tree for the MTC and a subtree to describe the behaviour
in the D-channel. Depending on the reference point which is tested and the purpose of the test, one
or two subtrees specify the behaviour in the B-channels. Subtrees that describe B-channel
behaviours are started only to check requirements at the S/T reference point and are created only
for an IUT that supports requirements at this reference point.
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.
Behaviour description for the B-channel always employs test steps so that if the tester does not implement
B-channel testing, those test steps could easily be ignored.
7.3.3 Defaults
Note the use of the RETURN statement which is defined in DAM1 of ISO/IEC 9646-3 [14]. 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.
7.3.4 Synchronization
If a PTC does not finish after an extra long timer, the MTC stops all active PTCs by sending a Halt
message. These co-ordination messages are captured by the PTCs in their default trees and by TC_D in
its postambles.
Page 19
ETS 300 267-4: April 1998
The MTC waits for co-ordination messages from TC_D to create TC_B1’s tree and from TC_B1 to create
TC_B2’s tree. On the opposite, TC_B1 expects, before starting its postamble in a two B-channel
communication call, a co-ordination message from the MTC to tell it that TC_B2 has ended. TC_D
expects, before starting its postamble to free channel(s), a co-ordination message from the MTC to tell it
that TC_B1 has ended.
The PTCs need to exchange co-ordination messages for functional reasons. TC_B1 cannot expand the
communication on both channel until TC_D has not established the call for the additional channel.
Figure 3 shows which and how co-ordination messages are exchanged in a test case where a two
B-channel communication call is established.
TC_MASTER
create(TC_D : d_tree)
TC_D
+PR_VID_IC_U10
First_B_Ch_Up
create(TC_B1 : b1_tree)
TC_B1
+MODE_INIT_2B
Done_Mode_Init_2B
+PR_VID_SC_U10
Expand_Mode
+WAIT_END_B1
+EXPAND_1B_2B_VIDEO
Second_B_Ch_Up
create(TC_B2 : b2_tree)
TC_B2
+SENDS_SYNC_MULTIFRAMES +GAINS_SYNCHRONISATION
+WAIT_END_B2
Clear_Second_B_Ch
Clear_First_B_Ch +PO_2B
+PO_SC_IC
Figure 3: Example of an exchange of co-ordination messages

Page 20
ETS 300 267-4: April 1998
8 ATS to TP map
The identifiers used for the combined TPs are reused as test case names. 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 [16], to produce a PCTR conformant with the PCTR template given in annex B of
ISO/IEC 9646-5 [16].
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 [15], 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 [16], 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
...