SIST I-ETS 300 697-4 E1:2003
(Main)Integrated Services Digital Network (ISDN); Conformance testing for the Euro-ISDN Programming Communication Interface (PCI); Part 4: Abstract Test Suite (ATS) specification for the Network Access Facility (NAF)
Integrated Services Digital Network (ISDN); Conformance testing for the Euro-ISDN Programming Communication Interface (PCI); Part 4: Abstract Test Suite (ATS) specification for the Network Access Facility (NAF)
To specify the conformance testing requirements of a PCI for use on the Euro-ISDN. Provision of the ATS for the NAF.
Digitalno omrežje z integriranimi storitvami (ISDN) – Preskušanje skladnosti programirljivega komunikacijskega vmesnika (PCI) sistema Euro-ISDN – 4. del: Specifikacija abstraktnega preskušalnega niza (ATS) za omrežni dostopovni pripomoček (NAF)
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.VWRSRYQLIntegrated Services Digital Network (ISDN); Conformance testing for the Euro-ISDN Programming Communication Interface (PCI); Part 4: Abstract Test Suite (ATS) specification for the Network Access Facility (NAF)33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:I-ETS 300 697-4 Edition 1SIST I-ETS 300 697-4 E1:2003en01-december-2003SIST I-ETS 300 697-4 E1:2003SLOVENSKI
STANDARD
SIST I-ETS 300 697-4 E1:2003
INTERIMEUROPEANI-ETS 300 697-4TELECOMMUNICATIONMarch 1998STANDARDSource: TEReference: DI/TE-02028-5ICS:33.020Key words:IDSN, access, ATS, network, PCI, testingIntegrated Services Digital Network (ISDN);Conformance testing for the Euro-ISDN ProgrammingCommunication Interface (PCI);Part 4: Abstract Test Suite (ATS) specificationfor the Network Access Facility (NAF)ETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEInternet: secretariat@etsi.fr - http://www.etsi.fr - http://www.etsi.orgTel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1998. All rights reserved.SIST I-ETS 300 697-4 E1:2003
Page 2I-ETS 300 697-4: March 1998Whilst 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 I-ETS 300 697-4 E1:2003
Page 3I-ETS 300 697-4: March 1998ContentsForeword.5Introduction.51Scope.72References.73Definitions and abbreviations.83.1Definitions.83.2Abbreviations.84Status.85General constraints for testing and applicable test method.95.1Testing Model.95.2Test method for PCI messages and Exchange Mechanism.95.3Testing configuration.105.4Mapping of PCI concepts into TTCN terms.115.4.1Exchange Mechanism functions.115.4.2ISDN PCI messages.116ATS naming conventions.117Notes on the ATS.127.1Encoding of ISDN message Information Elements (IEs).127.2Naming ISDN messages constraints.137.3Test Purposes grouping into a combined TP.137.4Order of parameters.138Test Purpose to Test Case mapping.13Annex A (normative):Abstract Test Suite (ATS) for the ETS 300 325 NAF.14A.1The TTCN Graphical form (TTCN.GR).14A.2The TTCN Machine Processable form (TTCN.MP).14Annex B (normative):PCTR for the ETS 300 325 NAF.15B.1Identification summary.15B.1.1Protocol Conformance Test Report.15B.1.2IUT.15B.1.3Testing environment.16B.1.4Limits and reservations.16B.1.5Comments.16B.2IUT conformance status.16B.3Static conformance summary.16B.4Dynamic conformance summary.16B.5Static conformance review report.17B.6Test campaign report.17SIST I-ETS 300 697-4 E1:2003
Page 4I-ETS 300 697-4: March 1998B.7Observations.24Annex C (normative):Partial IXIT proforma for the ETS 300 325 NAF.25C.1Identification summary.25C.2Abstract Test Suite summary.25C.3Test laboratory.25C.4Client.25C.5SUT.25C.6Protocol information for the ETS 300 325 NAF.26C.6.1Protocol identification.26C.6.2IUT information.26Annex D (informative):ETS 300 325 NAF PCI ICS Proforma.29D.1Instructions for completing the NAF PCI ICS proforma.29D.1.1Purposes and structure.29D.1.2Conventions.30D.1.2.1Standardized symbols for the status column.30D.1.2.2Standardized symbols for the support column.30D.1.3Instructions for completing the PCI ICS.30D.2Identification of the implementation.31D.2.1Date of statement.31D.2.2Implementation Under Test (IUT) identification.31D.2.3System Under Test (SUT) identification.31D.2.4Product supplier.31D.2.5Client.32D.2.6ICS contact person.32D.3PCI ICS/System Conformance Statement (SCS).33D.4Identification of the PCI.33D.5Global statement of conformance.33D.6Static requirements.33D.6.1Major capabilities.33D.6.1.1Underlying Operating System.33D.6.1.2Exchange Mechanism.34D.6.1.3Administration Plane classes.34D.6.1.4Control Plane classes.34D.6.1.5User Plane class.35D.6.1.6User Plane protocols.35D.6.2Messages.36D.6.2.1Administration Plane messages.36D.6.2.2Control Plane messages.37D.6.2.3User Plane messages.39D.6.3Miscellaneous features.40Annex E (informative):Bibliography.40History.42SIST I-ETS 300 697-4 E1:2003
Page 5I-ETS 300 697-4: March 1998ForewordThe fourth part of this Interim European Telecommunication Standard (I-ETS) has been produced by theTerminal Equipment (TE) Technical Committee of the European Telecommunications Standards Institute(ETSI).An ETSI standard may be given I-ETS status either because it is regarded as a provisional solution aheadof a more advanced standard, or because it is immature and requires a "trial period". The life of an I-ETSis limited to three years after which it can be converted into an ETS, have its life extended for a further twoyears, be replaced by a new version, or be withdrawn.This is the fourth part of a I-ETS which comprises four parts:"Integrated Services Digital Network (ISDN); Conformance testing for the Euro-ISDN ProgrammingCommunication Interface (PCI):Part 1: "Test Suite Structure and Test Purposes (TSS&TP) for the PCI User Facility (PUF);Part 2: "Abstract Test Suite (ATS) for the PCI User Facility (PUF);Part 3: "Test Suite Structure and Test Purposes (TSS&TP) for the Network Access Facility (NAF);Part 4: "Abstract Test Suite (ATS) for the Network Access Facility (NAF)".Announcement dateDate of adoption of this I-ETS:6 March 1998Date of latest announcement of this I-ETS (doa):30 June 1998IntroductionI-ETS 300 697, parts 1 to 4 comprises the Test Suite Structure and Test Purposes (TSS&TP) and theAbstract Test Suites (ATS) to ETS 300 325 [1]. The Euro-ISDN PCI is a PCI which provides access to theEuro-ISDN. The basic model of the ISDN PCI consists of two entities, a service user called the PCI UserFacility (PUF) and a service provider called the Network Access Facility (NAF). For the purposes ofconformance testing, the PUF and the NAF are treated separately. This is because the PUF manufacturerand the NAF manufacturer may be completely different and their testing needs should be treatedseparately. Each part is tested to ensure that they each meet the conformance requirements of the I-ETSand to increase their probability of inter-operating. This is the reason why a separate TSS&TP and aseparate ATS has been produced for both the PCI User Facility (PUF) and the Network Access Facility(NAF).All parts have been produced according to ISO/IEC 9646 [2] to [6] and ETS 300 406 [10].As stated above, this I-ETS is structured in four parts:-part 1 contains the TSS&TP for the PUF;-part 2 contains the ATS for the PUF;-part 3 contains the TSS&TP for the NAF;-part 4 contains the ATS for the NAF.SIST I-ETS 300 697-4 E1:2003
Page 6I-ETS 300 697-4: March 1998Part 1 (TSS&TP for the PUF) contains all Test Purposes (TPs) for the PUF (PCI messages). It describeswhat is covered by the TPs for the PUF and what areas of the I-ETS are not covered. The Test SuiteStructure (TSS) is described and the convention followed in naming the TPs is described. A list of basicinterconnection tests is given.Part 2 (ATS for the PUF) contains the ATS for the PUF (PCI messages). The test method used isdescribed in detail and diagrams explaining the test method are presented. The reasons for choosing thetest method are also given. The ATS is written in Tree and Tabular Combined Notation (TTCN) and theTTCN is contained in annex A. Annex B contains the Protocol Conformance Test Report (PCTR), annexC contains the Implementation eXtra Information for Testing (IXIT) and annex D contains anImplementation Conformance Statement (ICS).Part 3 (TSS&TP for the NAF) contains all TPs for the NAF (PCI messages and Exchange Mechanism). Itdescribes what is covered by the TPs for the NAF and what areas of the I-ETS are not covered. The TSSis described and the TPs are given. A list of basic interconnection tests is given.Part 4 (ATS for the NAF) contains the ATS for the NAF (PCI messages and Exchange Mechanism). Thetest method used is described in detail and a diagram explaining the test method is given. The reasons forchoosing that test method is also given. The ATS is written in concurrent TTCN and the TTCN iscontained in annex A. Annex B contains the PCTR, annex C contains the IXIT and annex D contains anICS.NOTE: The ICS in annexes D of part 2 and part 4 are informative as ETS 300 325 [1] alreadycontains an ICS. However, the ICS in ETS 300 325 [1] is not adequate for these ATSsand should, eventually, be replaced by annexes D of part 2 and part 4 of this I-ETS.SIST I-ETS 300 697-4 E1:2003
Page 7I-ETS 300 697-4: March 19981ScopePart 4 of this I-ETS contains the Abstract Test Suite (ATS) for the Network Access Facility (NAF). The testmethod used is described in detail and diagrams explaining the test method are presented. The reasonsfor choosing this test method are also given. The ATS is written in Tree and Tabular Combined Notation(TTCN) and the TTCN is contained in annex A. Annex B contains the Protocol Conformance Test Report(PCTR), annex C contains the Implementation eXtra Information for Testing (IXIT) and annex D containsan Implementation Conformance Statement (ICS).2Normative referencesPart 4 of this I-ETS incorporates by dated or 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 part of this I-ETS only when incorporated in it by amendment or revision. For undatedreferences the latest edition of the publication referred to applies.[1]ETS 300 325 (1994): "Integrated Services Digital Network (ISDN); ProgrammingCommunication Interface (PCI) for Euro-ISDN".[2]ISO/IEC 9646-1 (1991): "Information Technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 1:General concepts".[3]ISO/IEC 9646-2 (1991): "Information Technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 2:Abstract Test Suite specification".[4]ISO/IEC 9646-3 (1992): "Information Technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 3:The Tree and Tabular Combined Notation (TTCN)".[5]ISO/IEC 9646-5 (1994): "Information Technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 5:Requirements on test laboratories and clients for the conformance assessmentprocess".[6]ISO/IEC DIS 9646-7 (1991): "Information Technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 7:Implementation Conformance Statement".[7]ETS 300 697-3: "Integrated Services Digital Network (ISDN); Conformancetesting for the Euro-ISDN Programming Communication (PCI); Part 3: TestSuite Structure and Test Purposes (TSS&TP) for the Network Access Facility(NAF)".[8]ISO/IEC 8208 (1990): "Information technology; Data communications - X.25Packet Layer Protocol for Data Terminal Equipment".[9]ETS 300 080: "Integrated Services Digital Network (ISDN); ISDN lower layerprotocols for telematic terminals".[10]ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocoland profile conformance testing specifications Standardization Methodology".[11]CCITT Recommendation T.70 (1998): "Network-independent basic transportservice for the telematic services".SIST I-ETS 300 697-4 E1:2003
Page 8I-ETS 300 697-4: March 19983Definitions and abbreviations3.1DefinitionsFor the purposes of this I-ETS all definitions in ISO/IEC 9646, parts 1, 2, 3, 5 and 7 ([2] to [6]) and itsamendments and draft amendments, and in ETS 300 325 [1] apply.PCI Implementation Conformance Statement (PCI ICS) proforma: A document, in the form of aquestionnaire, which when completed for a PCI implementation becomes the PCI ICS (seeISO/IEC DIS 9646-7 [6]).PCI ICS: A statement made by the supplier of a PCI, stating which capabilities have been implemented fora given PCI (see ISO/IEC DIS 9646-7 [6]).3.2AbbreviationsFor the purposes of this part of this I-ETS, the following abbreviations apply:ASPAbstract Service PrimitiveATSAbstract Test SuiteCPCo-ordination PointICSImplementation Conformance StatementIEInformation ElementISDNIntegrated Services Digital NetworkIUTImplementation Under TestIXITImplementation eXtra Information for TestingMTCMaster Test ComponentMTSMethods for Testing and SpecificationNAFNetwork Access FacilityN/ANot ApplicableOSIOpen Systems InterconnectionPCIProgramming Communication InterfacePCOPoint of Control and ObservationPCTRProtocol Conformance Test ReportPDUProtocol Data UnitPTCParallel Test ComponentPUFProgramming communication interface User FacilitySCSSystem Conformance StatementSUTSystem Under TestTCTest CaseTCVTest Case VariableTPTest PurposeTSSTest Suite StructureTSS&TPTest Suite Structure & Test PurposesTSVTest Suite VariableTTCNTree and Tabular Combined Notation4StatusThis ATS uses concurrent TTCN and has been edited using the ITEX tool, version 2.2. Since this toolcontains bugs in the concurrent parts, parts of the test suite have not been parsed.SIST I-ETS 300 697-4 E1:2003
Page 9I-ETS 300 697-4: March 19985General constraints for testing and applicable test method5.1Testing ModelETS 300 325 [1] is an interface standard and not a protocol standard. ISO/IEC 9646-1 [2] explicitly statesthat it applies only to protocols of the OSI stack. This means that ISO/IEC 9646, [2] to [6] could not beused directly for testing the NAF. Due to historical reasons, the solution for the NAF is not the same as forthe PUF. In particular, the PCI messages and the Exchange Mechanism testing are not treatedseparately. The messages of the standard mapped onto Protocol Data Unit (PDUs) and the ExchangeMechanism functions are mapped onto Abstract Service Primitives (ASPs) for PCI messages testing ANDfor Exchange Mechanism testing.5.2Test method for PCI messages and Exchange MechanismBoth the upper and the lower interfaces of the NAF with a tester placed at each interface can be controlledand observed:-the lower interface of the NAF is the ISDN network interface (D-channel and B-channel). Althoughthis interface is not really a part of the I-ETS (it is not the Euro-ISDN PCI), it was chosen to observeit to check that the NAF provides really the service. Moreover, the mapping between PCI messagesand network PDUs are well defined in the ETS 300 325 [1].There are 2 PCOs at this lower interface. PCO_D at which test events are Euro-ISDN protocolLayer 3 PDUs, and PCO_B at which test events are user protocol PDUs.-the upper service boundary is its PCI interface with the PUF. There is one PCO (PCO_U) at thisinterface, at which the test events are ASPs (Exchange Mechanism functions).A test co-ordination procedure shall be necessary to co-ordinate between the Upper and the LowerTesters. The nature of the interfaces and the use of a co-ordination procedure means that a distributedtest method (see ISO/IEC 9646-2 [3] is the most suitable test method for testing the NAF. Using thismethod, all of the test suite execution can be automated. Concurrent TTCN was required in order todevelop the ATS because there are three Points of Control and Observation (PCOs) which need to becontrolled simultaneously, i.e. the one at the upper boundary and two at the lower boundary for theD-channel and the B-channel.SIST I-ETS 300 697-4 E1:2003
Page 10I-ETS 300 697-4: March 19985.3Testing configurationFigure 1 describes the testing configuration used throughout this ATS:Figure 1: NAF test configuration using distributed test method-Main Test Component (MTC);-Parallel Test Component (PTC) (Upper, D-channel, B-channel);-Implementation Under Test) (IUT) is the NAF under test;-Co-ordination Point (CP) (between the PTCs and the PTCs and the MTC);-Service Provider is the ISDN network access; it carries ISDN Layer 3 PDUs exchanged betweenthe IUT and the D-channel part of the Lower Tester and ISDN B-channel PDUs exchanged betweenthe IUT and the B-channel part of the Lower Tester;-PCO-U is the PCO between the IUT, the Upper Tester (test events are ASPs: ExchangeMechanism functions and PDUs are PCI messages);-PCO-D is the PCO between the IUT the D-channel emulator (test events are Euro-ISDN Layer 3PDUs);-PCO-B is the PCO between the IUT the B-channel emulator (test events are user connection Layer3 PDUs).The tester consists of a Main Test Component (MTC) which is responsible for:-creating and terminating all Parallel Test Components (PTCs) within the test system;-co-ordination between the PTCs involved in a test case;-receipt of preliminary results from PTCs;-computing the Test verdict.and three PTCs:-PTC-U, which corresponds to an Upper Tester playing the role of PCI User Facility (PUF)responsible for creating and destroying Network Connection Objects (NCOs);-PTC_D, which corresponds to a Lower Tester playing the role of ISDN D-channel;-PTC_B, which corresponds to a second Lower Tester playing the role of ISDN B-channel.SIST I-ETS 300 697-4 E1:2003
Page 11I-ETS 300 697-4: March 19985.4Mapping of PCI concepts into TTCN termsSome terms within PCI have been mapped onto terms used within TTCN.5.4.1Exchange Mechanism functionsThe functions used within the Exchange Mechanism correspond to the Abstract Service Primitives (ASPs)as defined in ISO/IEC 9646-3 [4].Each function of the Exchange Mechanism used within ISDN PCI has been translated into an exchange ofAbstract Service Primitives of the kind ASP_Req / ASP_Cnf. The reason why two ASPs are used for eachExchange Mechanism function is because in ETS 300 325 [1] the Exchange Mechanism functions aredescribed as functions which are called with parameters and which return values. The returned values arepassed in ASP_Cnf. e.g. the use of the Exchange Mechanism function PciRegister is done in this ATS thefollowing way:-PTC_U sending an ASP of the type PciRegister_Req;-PTC_U receiving an ASP of the type PciRegister_Cnf.The fact that these functions depend on the operating system, brought some problems to the definition ofthese ASPs. The following solution is used:-each ASP_Req/ASP_Cnf type declaration contains all of the parameter fields corresponding to allthe input/output parameters that are needed in UNIX, DOS and Windows operating systems;-there is a different ASP constraint for each underlying operating system. Therefore:-three ASPs constraints of the type PciRegister_Req are defined, PR_DOSReq,PR_UNIXReq and PR_WinReq, one to be used with DOS, and one with UNIX and one withWindows;-three ASPs constraints of the type PciRegister_Cnf are defined, PR_DOSCnf, PR_UNIXCnfand PR_WinCnf, one to be used with DOS, and one with UNIX and one with Windows.All of these ASP constraints shall be parameterized according to the input/output values that vary for eachof the operating systems in ETS 300 325 [1].5.4.2ISDN PCI messagesThe PCI messages are translated into PDUs. The PDU parameters correspond to the PCI messageparameters.The way these PCI messages are sent and received from the NAF is never by a simple send or receiveevent at the associated PCO, in this case PCO_U. The PDUs shall always be carried inside the ASPscorresponding to the relevant exchange function, PciPutMessage or PciGetMessage. When a PDU is tobe sent to the NAF, it shall be stored in one of the parameters of the PciPutMessage ASP. In order toreduce the complexity of the test case behaviour description by making the use of the exchange functionsmore transparent, test steps corresponding to the exchange functions shall be defined.6ATS naming conventionsThe naming conventions described here have been chosen to ensure easy understanding of the ATS. Asfar as possible, the names reflect their role in the ATS. When a name is used to represent an item fromETS 300 325 [1], then the name shall be taken directly from ETS 300 325 [1] and usually prefixed with therelevant prefix. Where an identifier is made up of one or more words, the words shall each start with acapital letter.-Test suite variables start with TSV_.EXAMPLE 1:TSV_MaxNCOCount.SIST I-ETS 300 697-4 E1:2003
Page 12I-ETS 300 697-4: March 1998-Test suite parameters start with TSP_.EXAMPLE 2:TSP_LocalNumber.-Structured type definitions are named to reflect the nature of the type.EXAMPLE 3:GroupID is a structured type definition for the PCI parameter GroupID.-Constraints on structured type definitions are used to represent the parameters of PCI messages.EXAMPLE 4:NCOID is a structured type definition for the PCI parameter NCOID and par_NCOID is a constraint of type NCOID.-Simple type definitions are named to reflect the nature of the type.EXAMPLE 5:OCTETSTRING4 is a type definition for octetstrings of length 4.-Test case variables start with TCV_.EXAMPLE 6: TCV_SyncFlag.-Timers start with a T.EXAMPLE 7: T0, T1.-PCI messages use the same names as in ETS 300 325 [1].EXAMPLE 8: ACreateNCOReq.-PCI message parameters use the same names as in ETS 300 325 [1] and are prefixed by par_.The fields of the parameters use the same names as the fields of the parameters inETS 300 325 [1].EXAMPLE 9:par_GroupID.-There shall be a one-to-one mapping between the test purpose identifiers in ETS 300 697-3 [7]and the test case names used in this test suite. The TPxxxxxx maps to TCxxxxxx.EXAMPLE 10:TP2213 maps to TC2213.-Test step names reflect the purpose of the test step. Those which are concerned with preamblesare prefixed with pre_ and those concerned with postambles are prefixed with post_.EXAMPLE 11:pre_C2.7Notes on the ATS7.1Encoding of ISDN message Information Elements (IEs)Only the Information Elements (IEs) which correspond to a PCI parameter, as for table B.2 ofETS 300 325 [1] shall have been coded mandatory in any of the ISDN messages that are used in the TestSuite.The coding of these IEs was
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.