General Information

Abstract

Test specification for RE/SPS-05138-1

Status
Published
Publication Date
31-Dec-2004
ICS
33.080 - Integrated Services Digital Network (ISDN)
Technical Committee
SPN - Services and Protocols for Networks
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Jan-2005
Due Date
01-Jan-2005
Completion Date
01-Jan-2005
Ref Project
ETSI EN 300 195-6 V1.2.1 (2000-11) - Integrated Services Digital Network (ISDN); Supplementary service interactions; 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

Buy Documents

SIST EN 300 195-6 V1.2.1:2005 - Page 1 previewSIST EN 300 195-6 V1.2.1:2005 - Page 2 previewSIST EN 300 195-6 V1.2.1:2005 - Page 3 previewSIST EN 300 195-6 V1.2.1:2005 - Page 4 preview
PreviousNext
Standard

SIST EN 300 195-6 V1.2.1:2005

English language (37 pages)
Preview
Preview
e-Library read for
×1 day

Overview

SIST EN 300 195-6 V1.2.1:2005 is a European telecommunications standard developed by the Slovenski inštitut za standardizacijo (SIST) in alignment with ETSI’s EN 300 195-6. This document focuses on Integrated Services Digital Network (ISDN) supplementary service interactions using the Digital Subscriber Signalling System No. one (DSS1) protocol. Specifically, Part 6 details the Abstract Test Suite (ATS) and the partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network side.

The standard provides a formalized test specification, supporting the assessment of DSS1 protocol implementations for conformance at the network interface as defined in ITU-T Recommendation I.411. The target is to ensure proper behavior of ISDN features and interoperability through standardized test methods and documentation.

Key Topics

  • Abstract Test Suite (ATS):

    • Defines structured test cases and methods for verifying DSS1 protocol functions and supplementary service interactions at the network reference point.
    • Uses both Tree and Tabular Combined Notation (TTCN) and ASN.1 for test case definition and constraints.

  • Partial PIXIT Proforma:

    • Presents a set of questions and required information from protocol implementors, such as configuration details and feature support, essential for customizing and executing conformance tests.

  • Test Methodologies:

    • Incorporates both remote and multi-party testing methods, assigning roles to master and parallel test components with a focus on observable results at the targeted interface.
    • Details conventions for test component interaction and verdict assignment.

  • Protocol Conformance Assessment:

    • Provides reporting proformas (such as the Protocol Conformance Test Report - PCTR) for documenting results and the status of the Implementation Under Test (IUT).
    • Defines processes for test suite applicability, constraints, and encoding rules, primarily using ISDN-specific and BER (Basic Encoding Rules) variations as specified in referenced standards.

Applications

SIST EN 300 195-6 V1.2.1:2005 is a crucial resource for:

  • Network Operators

    • Ensuring their ISDN network side implementations of DSS1 meet European conformance requirements regarding supplementary service interactions.
    • Facilitating interoperability with user equipment and third-party systems.

  • Equipment Manufacturers

    • Providing conformity evidence for DSS1 protocol implementations by following a standardized ATS and robust PIXIT proforma.
    • Streamlining integration by clarifying requirements for supplementary service behaviors at network interfaces.

  • Test Laboratories

    • Utilizing a harmonized and repeatable test suite to assess protocol conformance for ISDN devices and network elements.
    • Preparing validated reports (PCTR) based on standardized templates to support certification and market entry.

  • Regulatory Authorities

    • Referencing an internationally aligned blueprint for verifying telecommunications protocol conformance that supports regulatory compliance in ISDN deployments.

Related Standards

Adopting this standard in a conformance or development process benefits from familiarity with the following closely related specifications:

  • EN 300 195-1: Protocol specification for ISDN supplementary service interactions using DSS1.
  • EN 300 195-2: Protocol Implementation Conformance Statement (PICS) proforma.
  • EN 300 195-4: ATS and partial PIXIT proforma for the user side.
  • EN 300 195-5: Test suite structure and test purposes specification for the network.
  • EN 300 196-1: ISDN generic functional protocol for supplementary services.
  • ISO/IEC 9646 series: OSI conformance testing methodology and framework.
  • ITU-T Recommendation I.411: ISDN user-network interfaces - reference configurations.
  • ITU-T Recommendation X.209: Basic encoding rules for ASN.1.

Practical Value

By applying SIST EN 300 195-6 V1.2.1:2005, organizations ensure repeatable, standardized testing of ISDN DSS1 supplementary services at the network side. This enables robust product development, vendor interoperability, and future-proofing against evolving telecommunications requirements. The standard is an essential part of a comprehensive ISDN protocol validation strategy, reflecting best practices in protocol conformance verification as accepted throughout Europe.

Buy Documents

SIST EN 300 195-6 V1.2.1:2005 - Page 1 previewSIST EN 300 195-6 V1.2.1:2005 - Page 2 previewSIST EN 300 195-6 V1.2.1:2005 - Page 3 previewSIST EN 300 195-6 V1.2.1:2005 - Page 4 preview
PreviousNext
Standard

SIST EN 300 195-6 V1.2.1:2005

English language (37 pages)
Preview
Preview
e-Library read for
×1 day

Get Certified

Connect with accredited certification bodies for this standard

ANCE

Mexican certification and testing association.

EMA Mexico Verified
Visit Website

Intertek Slovenia

Intertek testing, inspection, and certification services in Slovenia.

UKAS Slovenia Verified
Visit Website

LNE (Laboratoire National de Métrologie et d'Essais)

French national laboratory for metrology and testing.

COFRAC France Verified
Visit Website

Sponsored listings

Frequently Asked Questions

SIST EN 300 195-6 V1.2.1:2005 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Integrated Services Digital Network (ISDN); Supplementary service interactions; 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". This standard covers: Test specification for RE/SPS-05138-1

Test specification for RE/SPS-05138-1

SIST EN 300 195-6 V1.2.1:2005 is classified under the following ICS (International Classification for Standards) categories: 33.080 - Integrated Services Digital Network (ISDN). The ICS classification helps identify the subject area and facilitates finding related standards.

SIST EN 300 195-6 V1.2.1:2005 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.

Standards Content (Sample)


2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.YSOLYDQMHIntegrated Services Digital Network (ISDN); Supplementary service interactions; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 300 195-6 Version 1.2.1SIST EN 300 195-6 V1.2.1:2005en01-januar-2005SIST EN 300 195-6 V1.2.1:2005SLOVENSKI
STANDARD
ETSIEN300195-6V1.2.1(2000-11)EuropeanStandard(Telecommunicationsseries)IntegratedServicesDigitalNetwork(ISDN);Supplementaryserviceinteractions;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part6:AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforthenetworkSIST EN 300 195-6 V1.2.1:2005

ETSIETSIEN300195-6V1.2.1(2000-11)2ReferenceREN/SPAN-05138-6KeywordsISDN,DSS1,supplementaryservice,interaction,testing,ATS,PIXIT,networkETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:+33492944200Fax:+33493654716SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88ImportantnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http://www.etsi.orgThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSIdocumentsisavailableathttp://www.etsi.org/tb/status/Ifyoufinderrorsinthepresentdocument,sendyourcommentto:editor@etsi.frCopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 300 195-6 V1.2.1:2005

ETSIETSIEN300195-6V1.2.1(2000-11)3ContentsIntellectualPropertyRights.5Foreword.51Scope.62References.63Definitionsandabbreviations.73.1Definitions.73.2Abbreviations.74AbstractTestMethod(ATM).84.1DescriptionofATMused.84.2ConventionsfortestcomponentsandPCOs.85Untestabletestpurposes.96ATSconventions.106.1Declarationspart.106.1.1Typedefinitions.106.1.1.1Simpletypedefinitions.106.1.1.2Structuredtypedefinitions.106.1.1.2.1TTCNstructuredtypedefinitions.106.1.1.2.2ASN.1structuredtypedefinitions.106.1.1.3ASPtypedefinitions.116.1.1.3.1TTCNASPtypedefinitions.116.1.1.3.2ASN.1ASPtypedefinitions.126.1.1.4PDUtypedefinitions.126.1.1.4.1TTCNPDUtypedefinitions.126.1.1.4.2ASN.1PDUtypedefinitions.126.1.2Testsuiteconstants.126.1.3Testsuiteparameters.126.1.4Variables.136.1.4.1Testsuitevariables.136.1.4.2Testcasevariables.136.1.5Testsuiteoperationdefinitions.136.2Constraintspart.136.2.1Structuredtypeconstraintdeclaration.136.2.2ASN.1typeconstraintdeclaration.136.2.2.1Specificationofencodingrules.146.2.3ASPtypeconstraintdeclaration.156.2.3.1ASN.1ASPtypeconstraintdeclaration.156.2.3.2TTCNASPtypeconstraintdeclaration.156.2.4PDUtypeconstraintdeclaration.166.2.4.1ASN.1PDUtypeconstraintdeclaration.166.2.4.2TTCNPDUtypeconstraintdeclaration.166.2.5Chainingofconstraints.166.2.5.1Staticchaining.166.2.5.2Dynamicchaining.166.2.6Derivedconstraints.166.2.7Parameterizedconstraints.166.2.8Valueassignment.166.2.8.1Specificvalues.166.2.8.2Matchingvalues.176.3Dynamicpart.176.3.1Testcases.176.3.2Teststeps.176.3.3Defaults.17SIST EN 300 195-6 V1.2.1:2005

ETSIETSIEN300195-6V1.2.1(2000-11)47ATStoTPmap.178PCTRconformance.179PIXITconformance.1810ATSconformance.18AnnexA(normative):ProtocolConformanceTestReport(PCTR)proforma.19A.1Identificationsummary.19A.1.1Protocolconformancetestreport.19A.1.2IUTidentification.19A.1.3Testingenvironment.20A.1.4Limitsandreservations.20A.1.5Comments.20A.2IUTconformancestatus.20A.3Staticconformancesummary.20A.4Dynamicconformancesummary.21A.5Staticconformancereviewreport.21A.6Testcampaignreport.21A.7Observations.26AnnexB(normative):PartialPIXITproforma.27B.1Identificationsummary.27B.2Abstracttestsuitesummary.27B.3Testlaboratory.27B.4Client(ofthetestlaboratory).28B.5SystemUnderTest(SUT).28B.6Protocolinformation.29B.6.1Protocolidentification.29B.6.2Parametervalues.29B.6.3Codingsofinformationelements.30B.6.4CalledpartynumberandCallingpartynumbervalues.31B.6.5ActionsrequiredtoconfiguretheIUT.32B.6.6OptionssupportedbytheIUT.32B.6.7Timervalues.33B.7BasiccallPIXITitems.33B.7.1Parametervalues-informationelementcodings.33AnnexC(normative):AbstractTestSuite(ATS).35C.1TheTTCNGraphicalform(TTCN.GR).35C.2TheTTCNMachineProcessableform(TTCN.MP).35AnnexD(informative):GeneralstructureofATS.36History.37SIST EN 300 195-6 V1.2.1:2005

ETSIETSIEN300195-6V1.2.1(2000-11)5IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinETSISR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinETSISR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSITechnicalCommitteeServicesandProtocolsforAdvancedNetworks(SPAN).Thepresentdocumentispart6ofamulti-partdeliverablecoveringtheDigitalSubscriberSignallingSystemNo.one(DSS1)protocolspecificationfortheIntegratedServicesDigitalNetwork(ISDN)supplementaryserviceinteractions,asdescribedbelow:Part1:"Protocolspecification";Part2:"ProtocolImplementationConformanceStatement(PICS)proformaspecification";Part3:"TestSuiteStructureandTestPurposes(TSS&TP)specificationfortheuser";Part4:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationfortheuser";Part5:"TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetwork";Part6:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforthenetwork".NationaltranspositiondatesDateofadoptionofthisEN:3November2000DateoflatestannouncementofthisEN(doa):28February2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31August2001DateofwithdrawalofanyconflictingNationalStandard(dow):31August2001SIST EN 300 195-6 V1.2.1:2005

ETSIETSIEN300195-6V1.2.1(2000-11)61ScopeThepresentdocumentspecifiestheAbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformafortheNetworksideoftheTreferencepointorcoincidentSandTreferencepoint(asdefinedinITU-TRecommendationI.411[10])ofimplementationsconformingtothestagethreestandardforthesupplementaryserviceinteractionsforthepan-EuropeanIntegratedServicesDigitalNetwork(ISDN)bymeansoftheDigitalSubscriberSignallingSystemNo.one(DSS1)protocol,EN300195-1[1].EN300195-5[3]specifiestheTestSuiteStructureandTestPurposes(TSS&TP)relatedtothisATSandpartialPIXITproformaspecification.OtherpartsspecifytheTSS&TPandtheATSandpartialPIXITproformafortheUsersideoftheTreferencepointorcoincidentSandTreferencepointofimplementationsconformingtoEN300195-1[1].2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIEN300195-1:"IntegratedServicesDigitalNetwork(ISDN);Supplementaryserviceinteractions;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part1:Protocolspecification".[2]ETSIEN300195-2:"IntegratedServicesDigitalNetwork(ISDN);Supplementaryserviceinteractions;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecification".[3]ETSIEN300195-5:"IntegratedServicesDigitalNetwork(ISDN);Supplementaryserviceinteractions;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part5:TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetwork".[4]ETSIEN300196-1:"IntegratedServicesDigitalNetwork(ISDN);Genericfunctionalprotocolforthesupportofsupplementaryservices;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part1:Protocolspecification".[5]ISO/IEC9646-1:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[6]ISO/IEC9646-2:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part2:AbstractTestSuitespecification".[7]ISO/IEC9646-3:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part3:TheTreeandTabularCombinedNotation(TTCN)".[8]ISO/IEC9646-4:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part4:Testrealization".[9]ISO/IEC9646-5:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part5:Requirementsontestlaboratoriesandclientsfortheconformanceassessmentprocess".[10]ITU-TRecommendationI.411(1993):"ISDNuser-networkinterfaces-referencesconfigurations".SIST EN 300 195-6 V1.2.1:2005

ETSIETSIEN300195-6V1.2.1(2000-11)7[11]ITU-TRecommendationX.209(1988):"SpecificationofbasicencodingrulesforAbstractSyntaxNotationOne(ASN.1)".[12]ETSIEN300195-4:"IntegratedServicesDigitalNetwork(ISDN);Supplementaryserviceinteractions;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part4:AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationfortheuser".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:AbstractTestSuite(ATS):seeISO/IEC9646-1[5]ImplementationUnderTest(IUT):seeISO/IEC9646-1[5]LowerTester(LT):seeISO/IEC9646-1[5]PointofControlandObservation(PCO):seeISO/IEC9646-1[5]ProtocolImplementationConformanceStatement(PICS):seeISO/IEC9646-1[5]PICSproforma:seeISO/IEC9646-1[5]ProtocolImplementationeXtraInformationforTesting(PIXIT):seeISO/IEC9646-1[5]PIXITproforma:seeISO/IEC9646-1[5]SystemUnderTest(SUT):seeISO/IEC9646-1[5]UpperTester(UT):seeISO/IEC9646-1[5]3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ASPAbstractServicePrimitiveATMAbstractTestMethodATSAbstractTestSuiteBERBasicEncodingRulesExTSExecutableTestSuiteFIEFacilityInformationElementIUTImplementationUnderTestLTLowerTesterMOTMeansOfTestingPCOPointofControlandObservationPCTRProtocolConformanceTestReportPDUProtocolDataUnitPICSProtocolImplementationConformanceStatementPIXITProtocolImplementationeXtraInformationforTestingSUTSystemUnderTestTPTestPurposeTTCNTreeandTabularCombinedNotationUTUpperTesterSIST EN 300 195-6 V1.2.1:2005

ETSIETSIEN300195-6V1.2.1(2000-11)84AbstractTestMethod(ATM)4.1DescriptionofATMusedTherequirementfortestingthenetworkIUTistofocusonthebehaviourofthenetworkIUTattheuser-networkinterfacewhereaTreferencepointorcoincidentSandTreferencepointapplies.ThustheIUTisthenetworkDSS1protocolentityataparticularuser-networkinterfaceandisnotthewholenetwork.ItispossibletospecifyanATSbasedonaSingleparty(remote)testmethodforsuchanIUT.However,itisconsideredthatanATSbasedonsuchanapproachisoflimiteduseastheonlywaytospecifyIUTgeneratedPDUsistousethe"implicitsend"statement.ManyusersofsuchanATSwouldreplacethe"implicitsend"statementswithdescriptionsofthebehaviouratotherinterfaces.AnATSbasedonamulti-partytestmethodisconsideredtobemoreusefulinthatitisclosertohowarealtestsuitewouldbeconstructed.Suchatestmethodspecifiesbehaviouratmultiplenetworkinterfaces.Oneveryimportantlimitationhereisthattestsarefocussedononeparticularinterface.ThusthetestsystemismadeuponeMainTestComponent(MTC)andoneormoreParallelTestComponents(PTC),seefigure1.4.2ConventionsfortestcomponentsandPCOsMasterpartSlavepartMTCAPTC2CPA2PTC1CPA1L0PCOL1PCOL2PCOIUTNETWORKFigure1:Multi-partytestmethodInamaster/slavearrangement,theMTCisconsideredtobethemasterwhilethePTCsaretheslaves.The"slave"testersareonlyanexplicitdescriptionofhowtodealwiththe"other"interfacesduringthetestingprocess,i.e."howtomaketheIUTsendtherequiredmessage".SIST EN 300 195-6 V1.2.1:2005

ETSIETSIEN300195-6V1.2.1(2000-11)9Thismeans,inparticular,thattheverdictwillonlybeassignedfromtheprotocolaspectsobservedontheinterfaceundertest(i.e.bythe"master"tester),asitwouldbeobservedbyaterminalconnectedtothisinterface.Afailureinthecorrelationbetweentheprotocolatthedifferentinterfacestowhichthedifferenttestersareconnected,i.e.inthemechanismofthefunctionalserviceitself,willnotcauseaFAILverdict.Forinstance,iftheIUTfailstosendamessageonthetestedinterfaceafteranotherinterfacehasreceivedtheproperstimulus,theverdictwillbeINCONCLUSIVE.TheMTCMTCAhastwofunctionsinthisconfiguration.Firstly,ithastheMTCfunctionofcontrollingtheoneormorePTCs.ThusitisresponsibleforstartingthePTCsandafterwardscoordinatesactivitiesbyexchangingCoordinationMessages(CM)withthePTCs.SecondlyitisresponsibleforthebehaviouroftheLowerTester(LT)atPCOL0.Acombinationoftheremoteandmulti-partytestmethodsisapplied.Ascanbeseenfromfigure1,severalPCOsareused.AllPCOsresideattheserviceaccesspointsbetweenlayers2and3.MTCSUTPTC1,2Layer3Layer2Layer1L0IUTL1,2Layer3Layer2Layer1ServiceproviderFigure2:Combinationoftheremoteandmulti-partytestmethodsTheMTCPCOisnamed"L0"("L"forLower).TheL0PCOisusedtocontrolandobservethebehaviouroftheIUTandtestcaseverdictsareassigneddependingonthebehaviourobservedatthisPCO.ThePTCsPTC1,PTC2etc.usePCOsL1,L2etc.ThesePCOsareusedtocontroland,inalimitedway,observethebehaviourofthenetworkequipmentatinterfacesotherthantheoneundertest.NoverdictsareassignedatthesePCOs.Asstatedinapreviousparagraph,thenon-receiptofnetworkgeneratedmessagesatL0,whicharestimulatedbyeventsattheL1,L2etc.,willresultinINCONCLUSIVEratherthanFAILverdictsbeingassigned.PTC2isonlyactivatedinasmallsetoftestcasesthattestthehandlingoftwocallsatonetime.IntestcaseswhichverifythattheIUTrejectsinvalidorunacceptableSETUPmessages,noPTCisactivatedatall,astheserejectionproceduresareconsideredlocaltotheaccessbetweenIUTandMTC.ThecapabilityoftheIUTtosendINFORMATIONandPROGRESSmessagesistestedindifferentcallstates.Implicitsendeventshavetobeusedinthissmallsetoftestcases,asthesendingofthosemessagescannotbetriggeredviaaPTC.SeparatePIXITquestionsareaskedforeachcallstate,ifandhowitispossibleforthetestoperatortocausethesendingofthemessages.5UntestabletestpurposesThefollowingtestpurposeshavebeenfoundtobeuntestable:SSI_N50_01_001,SSI_N50_01_003,andSSI_N50_01_005DuetothefactthattheserviceOCB-FcannotbeactivatedaftertheCCBSservicehasbeenactivated.SIST EN 300 195-6 V1.2.1:2005

ETSIETSIEN300195-6V1.2.1(2000-11)106ATSconventionsThisclauseisstructuredsimilarlytothestructureofaTTCNATS.However,thenamesofthesubclausesarearrangedinawaymoresuitabletothepresentdocument.6.1Declarationspart6.1.1Typedefinitions6.1.1.1SimpletypedefinitionsWhereappropriate,simpletypeshavealength,avaluelistorarangerestrictionattached.Simpletypesdefinedasbeingofsomestringtype(e.g.BITSTRING,OCTETSTRING),havealengthrestrictionoravaluelistattached.Simpletypes,definedasbeingofINTEGERtype,haveavaluelistorarangerestrictionattached.6.1.1.2Structuredtypedefinitions6.1.1.2.1TTCNstructuredtypedefinitionsAllstructuredtypedefinitionsareprovidedwithafullname.Allelementsineverystructuredtypedefinition,definedasbeingofsomestringtype(e.g.BITSTRING,OCTETSTRING),havealengthrestrictionattached.Ifanelementinastructuredtypedefinitionisdefinedasbeingofareferencedtype,the(possible)restrictionisdefinedinthatreferencedtype.Forinformationelementstheidentifier,whichisuniqueforeachelement,hasitstypedefinedasasimpletypewherethevaluelistisrestrictedtothesinglevaluewhichistheidentifieritself.ThishastheadvantagethatitallowsatestsystemderivedfromthisATStoeasilyidentifyinformationelementsembeddedinmessages.AnATSwhereinformationelementidentifiersarerepresentedasunrestrictedtypescanpresentdifficultiesforaderivedtestsysteminthecasewhereitneedstofindoneinformationelementembeddedinanumberofothersandtheconstraintsfortheotherelementshavetheany-or-omitvalue.Insuchacasethetestsystemcannoteasilyfindthebeginningofeachinformationelement.6.1.1.2.2ASN.1structuredtypedefinitionsASN.1hasbeenusedforthreemajorreasons.First,typesdefinedinASN.1canmodelproblemsthat"pure"TTCNcannot.Forinstance,datastructuresmodellingorderedorunorderedsequencesofdataarepreferablydefinedinASN.1.Second,ASN.1providesabetterrestrictionmechanismfortypedefinitionsbyusingsub-typedefinitions.Third,itisnecessarytouseASN.1toreproducethetypedefinitionsforremoteoperationcomponentsasspecifiedinthebasestandards.ThefactthatASN.1providesabetterrestrictionmechanismfortypedefinitionsisusedforthepurposeofachievingtype-compatibility.Intable1,theASN.1typeBIT7OR15isdefinedasbeingoftypeBITSTRINGwithasizeconstraintattachedtoit.ThesizeisdeterminedbythevalueofCR_LENGTH,atestsuiteparameter.Itcanhavethevalueofeither7or15.ThetypeBIT7OR15isusedinthestructuredtypeCR,fieldcr_rallowingthistypetorepresentaBasicAccessoraPrimaryRateAccesscallreference.Byusingthistypedefinitionthefieldcr_risalwaystypecompatiblewithvaluesoftypeBITSTRING(SIZE(7))andBITSTRING(SIZE(15)).AnotherapproachtosolvethisproblemwouldbetodefinethetypeBIT7OR15asBITSTRING(SIZE(7|15)).Thistypehasasmalldisadvantagecomparedwiththepreviousone.Itisimpossible,inrun-time,todeterminetheactuallengthofanyinstanceofthistype.SIST EN 300 195-6 V1.2.1:2005

ETSIETSIEN300195-6V1.2.1(2000-11)11Table1:ASN.1typedefinitionBIT7OR15ASN.1TypeDefinitionTypeName:BIT7OR15Comments:TypeDefinitionBITSTRING(SIZE(CR_LENGTH))Table2showsatypicaluseofASN.1.TheCHIelementwillhavetwodifferenttypedefinitionsdependingonwhetheritrepresentsbasicorprimaryrateaccess.InTTCN,thisneedstobedefinedastwodifferenttypes.InASN.1thiscanbedoneinone,thetypebeingachoiceofeitherBASIC_CHIorPRIMARY_CHI.Thesetwotypesarethen(locally)definedinthesametable.Table2:ASN.1typedefinitionCHIASN.1TypeDefinitionTypeName:CHIComments:InfoElementChannelIdentificationETS300102-1clause4.5.13TypeDefinitionCHOICE{basicBASIC_CHI,primaryPRIMARY_CHI}--Localtypedefinitions--BASIC_CHI::=SEQUENCE{chi_iCHI_I,--Identifierchi_lBITSTRING(SIZE(8)),--Lengthchi_e3_csBITSTRING(SIZE(8))--Channelselection}PRIMARY_CHI::=SEQUENCE{chi_iCHI_I,--Identifierchi_lBITSTRING(SIZE(8)),--Lengthchi_e3_p1BITSTRING(SIZE(4)),--FirstnibbleofChannelselectionchi_e3_peBITSTRING(SIZE(1)),--Preferred/ExclusiveBitchi_e3_p3BITSTRING(SIZE(3)),--LastthreebitsofChannelselectionchi_e4BITSTRING(SIZE(8)),--Channeltypechi_e5_chlBITSTRING(SIZE(1)),chi_e5_ch2BITSTRING(SIZE(7))--Channelnumber}Table3showsanexampleofhowASN.1canbeusedtomodelunorderedsequences.Table3:ASN.1typedefinitionFIESASN.1TypeDefinitionTypeName:FIESComments:TypeDefinitionSETOFFIEThepossibilitytouseTTCNandASN.1incombinationisused,i.e.referringtoanASN.1typefromaTTCNtype.6.1.1.3ASPtypedefinitions6.1.1.3.1TTCNASPtypedefinitionsTTCNASPtypedefinitionsonlycontainonePDUornoPDUatall.TherelationshipbetweenanASPtypeandaPDUtypeisone-to-one.Thatis,thereexistsoneASPtypedefinitionforeachPDUtypedefinition(ifthatASPtypecontainsaPDU).AllTTCNASPtypedefinitionsareprovidedwithafullidentifier.SIST EN 300 195-6 V1.2.1:2005

ETSIETSIEN300195-6V1.2.1(2000-11)12SomeASPsarenotparameterizedasshownintheexampleintable4.SuchASPsareonlyusedforrequestingorreceivingservicefromthelowerlayer.Table4:TTCNASPtypedefinitionDL_REL_INTTCNASPTypeDefinitionASPNAME:DL_REL_IN(DL_RELEASE_INDICATION)PCOType:SAPComments:ParameterName|ParameterType|CommentsDetailedComments:Table5showsanexampleofaparameterizedASP.AllASPscontainingPDUscontainonlythatPDUandnootherparameters.Table5:TTCNASPtypedefinitionDL_DATA_RQ_ALERTTTCNASPTypeDefinitionASPNAME:DL_DATA_RQ_ALERT(DL_DATA_REQUEST)PCOType:SAPComments:ParameterName|ParameterType|Commentsmun(MessageUnit)|ALERT_PDU|DetailedComments:6.1.1.3.2ASN.1ASPtypedefinitionsTherearenoASN.1ASPtypedefinitionsintheATS.6.1.1.4PDUtypedefinitions6.1.1.4.1TTCNPDUtypedefinitionsTheTTCNPDUtypereflectstheactualdatabeingtransferredorreceived.AllPDUsareembeddedinASPs.IfaspecificPDUtypedefinitioncontainselementsdefinedintermsofapre-definedtype,thatelementhasarestrictionattachedtoit.6.1.1.4.2ASN.1PDUtypedefinitionsTherearenoASN.1PDUtypedefinitionsintheATS.6.1.2TestsuiteconstantsNotestsuiteconstantsareusedordefinedinthisATS.6.1.3TestsuiteparametersEachtestsuiteparameterisdefinedintermsofapredefinedtypeorareferencedtype.Areferencedtypeisusedwhenitisnecessarytoattachrestrictionstothesetypedefinitions(itisnotallowedtoincluderestrictionsdirectlyinthetestsuiteparametertable).Thereferencedtypecanhavealengthorvaluerestrictionattachedtoitinitsdeclarationtable.SIST EN 300 195-6 V1.2.1:2005

ETSIETSIEN300195-6V1.2.1(2000-11)136.1.4Variables6.1.4.1TestsuitevariablesNotestsuitevariablesareusedordefinedinthisATS.6.1.4.2TestcasevariablesEachtestcasevariableisdefinedintermsofapredefinedtypeorareferencedtype.Areferencedtypeisusedwhenitisnecessarytoattachrestrictionstothesetypedefinitions(itisnotallowedtoincluderestrictionsdirectlyinthetestcasevariabletable).Thereferencedtypecanhavealengthorvaluerestrictionattachedtoitinitsdeclarationtable.Wheretestcasevariablesareusedinconstraints,theyarepassedasformalparameters.6.1.5TestsuiteoperationdefinitionsThedescriptionpartofatestsuiteoperationdefinitionuseseithernaturallanguageormetaC.Table6:TestsuiteoperationdefinitionASSIGN_CHITestSuiteOperationDefinitionOperationName:ASSIGN_CHI(basic,primary:CHI;basic_flag:BOOLEAN)ResultType:CHIComments:ThisoperationisusedtoassignacorrectChannelidentificationinformationelementtoPDUsdependentonthetypeofaccessthatistested.Description{if(basic_flag)returnbasic;elsereturnprimary}Detailedcomments:Thetestsuiteoperationdefinitionshownintable6isusedintheconstraintspartwhenassigninganelementoftypeCHIavalue.Aspreviouslydescribed,theCHItypecanbedefinedintwowaysdependingonwhethertheATSistestingbasicorprimaryrateaccess.ToavoidduplicatetypesandtherebyduplicatetestcasestheCHItypeisdefinedinASN.1.ThisoperationisusedtoassignavaluetoanelementofCHItype.Ittakesthreeparameters:primary:aconstraintoftypeCHIvalidforprimaryrateaccess;basic:aconstraintoftypeCHIvalidforbasicaccess;basic_flag:aBooleanvalue:TRUEifbasicaccessisapplicable,FALSEotherwise.ThisoperationreturnsthecorrectconstraintaccordingtotheBooleanflagbasic_flag.ThatconstraintwillthenbeassignedtothespecificelementoftypeCHI.6.2Constraintspart6.2.1StructuredtypeconstraintdeclarationForeverystructuredtypedefinitionthereexistsoneormorestructuredtypeconstraint.6.2.2ASN.1typeconstraintdeclarationConstraintsofthistypeareusedtoassignthecorrespondingtypeaspecificvalue.TheseconstraintsareusedforthepurposeofmodellingunordereddataorspecifictypesthatcannotbeexpressedinTTCN.AvalueassignedtoanelementoftypeSETOFdiffersdependingonwhetheritisasendorreceiveconstraint.SIST EN 300 195-6 V1.2.1:2005

ETSIETSIEN300195-6V1.2.1(2000-11)14Table7:ASN.1typeconstraintdeclarationfIEs(sendconstraint)ASN.1TypeConstraintDeclarationConstraintName:fIEs(comp:Component)ASN.1Type:FIEDerivationPath:Comments:SendFIEwhichwillcontainonecomponent"comp".Description{informationElementIdentifier'00011100'B,lengthCALC_FIE_LENGTH(comp),extBit'1'B,spareBits'00'B,protocolProfile'10001'B,components{comp}}Detailedcomments:NOTE:Thelastelementintheconstraint,namedcomponents,isoftypeSETOFComponentwhereComponentisstructureddataofsometype.Iftheconstraintisasendconstraint(asintable7)thevalueforthecomponentelementisstatedas"{comp}"wherecompisanargumentreceivedasaparameter.The"{"and"}"turnsthevalueintoaSETOFvaluewhichiscorrectaccordingtothatelement'stypedefinition.Table8:ASN.1typeconstraintdeclarationfIEr(receiveconstraint)ASN.1TypeConstraintDeclarationConstraintName:fIEr(comp:Component)ASN.1Type:FIEDerivationPath:Comments:AreceivedFIEwhichcancontainseveralcomponents,butwhichcontainsatleast"comp".Description{informationElementIdentifier'00011100'B,length'????????'B,extBit'1'B,spareBits'00'B,protocolProfile'10001'B,componentsSUPERSET({comp})}Detailedcomments:NOTE:Thelastelementintheconstraint,namedcomponents,isoftypeSETOFComponentwhereComponentisstructureddataofsometype.Iftheconstraintisareceiveconstraint(asintable8)thecorrespondingmatchingvalueisassignedbyusingSUPERSET.Thekey-wordSUPERSEThasanargumentthatistypecompatiblewiththetypedefinitionofthatfield.Intable8,theelementnamedcomponentsisdefinedas"SETOFComponent"andthisimpliesthattheargumenttoSUPERSETshouldbeoftypeSETOFComponent.Thisisachievedthesamewayasforsendconstraints,enclosingthevalueincurlybrackets.ThesemanticofSUPERSETisstatedinISO/IEC9646-3[7],subclause11.6.4.7.Inshortitdefinesthesemanticasfollows:"AvaluethatusesSUPERSETmatchestheincomingvalueif,andonlyif,theincomingvaluecontainsatleastalloftheelementsdefinedwithintheSUPERSET,andmaycontainmoreelements".ThisisexactlythesemanticdefinitionusedinthisATS.6.2.2.1SpecificationofencodingrulesAtthetimeofspecifyingthisATSthemechanismsrelatedtoencodingofASN.1types,specifiedinDAM-2ofISO/IEC9646-3[7],werenotyetstable.NeverthelessasthereisavariationintheencodingrulesasappliedtoASN.1typesandconstraintsspecifiedinthisATS,amechanismisusedtodifferentiatethedifferentencodingrules.Giventhenon-finalizedstatusofDAM-2,asolutionwhichisbroadlyinthespiritofDAM-2hasbeencreated.Commentfieldshavebeenusedasameansofincludingtheencodingrules.SIST EN 300 195-6 V1.2.1:2005

ETSIETSIEN300195-6V1.2.1(2000-11)15ForASN.1usedinthisATS,twovariationsofencodingrulesareused.OneisthecommonlyknownBasicEncodingRules(BER)asspecifiedinITU-TRecommendationX.209[11].InthesecondcasetheencodingisaccordingtoISDN,i.e.theASN.1datatypesarearepresentationofstructurescontainedwithintheISDNspecification(basiccall,Genericfunctionalprotocolorindividualsupplementaryservice).Forexample,ifoctetsofaninformationelementarespecifiedinASN.1asaSEQUENCEthenthisshouldbeencodedinanExecutableTestSuite(ExTS)asanyotherISDNinformationelementspecifiedusingtabularTTCN.ThisISDNencodingvariationisthedefaultencodingruleforthisATS.ThismeansthatallASN.1constrainttablesareencodedusingISDN(non-BER)encodingunlessstatedotherwise.BERencodingshouldneverbeappliedtoanASN.1constraintwhereBERencodinghasnotbeenspecified.ForBERencoding,anindicationisgiveninthecommentsfieldofthetableheader.ForthisATSsuchindicationsappearintheASN.1typeconstraintdeclarationtablesonly.Inthefirstlineofthetableheadercommentfield,thenotation"ASN1_Encoding:BER"isused.NotethatwithinBER,thereareanumberofvariationsfortheencodingoflengthsoffields.AccordingtoEN300196-1[4],anIUTshouldbeabletointerpretalllengthformswithinBERforreceivedPDUs.WhensendingPDUscontainingBERencoding,EN300196-1[4]givesguidelinesbutmakesnorestrictionsonthelengthformswithinBERwhichanIUTmayapply.InrelationtocomponentssentbythetestertotheIUT,implementorsofthisATSshalluseavarietyoflengthformssuchthatatleastoneofeachofthelengthformsissenttotheIUTduringatestcampaign.Thevariationsoflengthformstobeusedareindefinite,shortdefiniteandlongdefinite.InthisparticularATSallASN.1typeconstraintswhichareoftype"Component"aretobeencodedusingBER.Table9:ASN.1typeconstraintdeclarationshowinguseofencodingvariationASN.1TypeConstraintDeclarationConstraintName:Beg3PTYinvASN.1Type:ComponentDerivationPath:Comments:ASN1_Encoding:BERReceivecomponent:Begin3PTYinvokecomponentDescriptionbegin3PTY_Componentsbegin3PTY_InvokeComp{invokeID?,operation_valuelocalValue4}Detailedcomments:6.2.3ASPtypeconstraintdeclaration6.2.3.1ASN.1ASPtypeconstraintdeclarationNoASN.1ASPtypeconstraintdeclarationexistsinthisATS.6.2.3.2TTCNASPtypeconstraintdeclarationForTTCNASPconstraintdeclarationsthereisaone-to-onerelationshipbetweenitstypeandtheconstraint.Thatis,thereisonlyoneconstraintforeachTTCNASPTypeDeclaration.ThereasonforthisisthattheASPsareusedonlyforcarryingaspecificPDUvalue.ThemanyASPconstraints(andtypes)couldhavebeenavoidedbyusingthemetatypePDU,butthatwasnotsuitableasvaluesinsideaspecificPDUhavetobereferenced.ToreferenceelementsinsideavalueofmetatypePDUisnotallowedaccordingtoISO/IEC9646-3[7],soeachASPhastobedefinedashavingaparameterofaspecificPDUtype.InallASPconstraintstheembeddedPDUconstraintiseitherchainedstaticor"semi-dynamic".Thatis,thePDUconstraintisalwaysfixedtoaspecificASPconstraintbutit(thePDU)maybeparameterized.AllASPconstraintshaveaspecificvalueforitsparameter.NomatchingsymbolsareusedinASPs.SIST EN 300 195-6 V1.2.1:2005

ETSIETSIEN300195-6V1.2.1(2000-11)166.2.4PDUtypeconstraintdeclaration6.2.4.1ASN.1PDUtypeconstraintdeclarationNoASN.1PDUtypeconstraintdeclarationexistsinthisATS.6.2.4.2TTCNPDUtypeconstraintdeclarationPDUconstraintsareusedforassigningvaluesorpatternstothedatabeingsentorreceived.6.2.5Chainingofconstraints6.2.5.1StaticchainingStaticchaining,thatisafixedreferencetoaspecificconstraint,isusedinthisATS.Thestaticchainingisusedforstaticbindingofbothvariablesandsub-structures.6.2.5.2DynamicchainingDynamicchainingisachievedwhenhavingareferencetoavaluewhichisunknown.Theonlythingknown(beforerun-time)isthetypeofthatreference.Thereferenceispassedasaparameter.StrictdynamicchainingisnotusedinthisATS.Whatisusedissomethingthatiscalled"semi-dynamicchaining".Thedefinitionofsemi-dynamicchainingisthatthefixedreferenceisparameterizedwithanunknownvalue.Thatvalueisreceivedasaparameter.Table10:TTCNASPconstraintdeclarationA_RST1TTCNASPConstraintDeclarationConstraintName:A_RST1(FLAG:INTEGER)ASN.1Type:DL_DAT_IN_RESTARTrDerivationPath:Comments:ParameterNameParameterValueCommentsmunRST1(FLAG)RST1(FLAG)Detailedcomments:Table10isanexampleofsemi-dynamicchaining.TheTTCNASPconstraintisparameterizedwithanINTEGERvaluenamedFLAG.ThatvalueispassedfurtherdowninthestructureasaparametertoastaticnamedPDUconstraintreference.6.2.6DerivedconstraintsNoderivationofanyconstraintisused.Allconstraintsareconsideredtobebaseconstraints.6.2.7ParameterizedconstraintsParameterizedconstraintsareusedinthisATS.6.2.8Valueassignment6.2.8.1SpecificvaluesForspecificvalueassignmentbothexplicitvaluesandreferencestoexplicitvaluesareused.SIST EN 300 195-6 V1.2.1:2005

ETSIETSIEN300195-6V1.2.1(2000-11)176.2.8.2MatchingvaluesAsmatchingvaluesthefollowingmechanismsareused:• InsteadofValue:-AnyOrOmit"*"-AnyValue"?"-SuperSetSUPERSET-Omit"-"• Insidevalue:-AnyOne"?"-AnyOrNone"*"6.3Dynamicpart6.3.1TestcasesEachtestcasecontainsthetestpurposetextfromEN300195-5[3].Tobeabletoreadandunderstandthetestcasedynamicbehaviouritisrecommendedthattheteststepsareunderstoodfirst.6.3.2TeststepsMuchusehasbeenmadeofteststepstoavoidneedlessrepetitionofdynamicbehaviour.ManyteststepsarebasedonthoseusedfortheISDNbasiccallATS.6.3.3DefaultsNotetheuseoftheRETURNstatementwhichisdefinedinDAM1ofISO/IEC9646-3[7].Thisallowsvalidbackgroundbehaviourtobehandledinthedefaulttreewithapossibilitytoreturntotheoriginalsetofalternativesinthetestcase.7ATStoTPmapTheidentifiersusedfortheTPsarereusedastestcasenames.Thusthereisastraightforwardone-to-onemapping.8PCTRconformanceAtestlaboratory,whenrequestedbyaclienttoproduceaPCTR,isrequired,asspecifiedinISO/IEC9646-5[9],toproduceaPCTRconformantwiththePCTRtemplategiveninannexBofISO/IEC9646-5[9].Furthermore,atestlaboratory,offeringtestingfortheATSspecificationcontainedinannexC,whenrequestedbyaclienttoproduceaPCTR,isrequiredtoproduceaPCTRconformantwiththePCTRproformacontainedinannexAofthepresentdocument.APCTRwhichconformstothisPCTRproformaspecificationshallpreservethecontentandorderingoftheclausescontainedinannexA.ClauseA.6ofthePCTRmaycontainadditionalcolumns.Ifincluded,theseshallbeplacedtotherightoftheexistingcolumns.Textinitalicsmayberetainedbythetestlaboratory.SIST EN 300 195-6 V1.2.1:2005

ETSIETSIEN300195-6V1.2.1(2000-11)189PIXITconformanceAtestrealizer,producinganexecutabletestsuitefortheATSspecificationcontainedinannexC,isrequired,asspecifiedinISO/IEC9646-4[8],toproduceanaugmentedpartialPIXITproformaconformantwiththispartialPIXITproformaspecification.AnaugmentedpartialPIXITproformawhichconformstothispartialPIXITproformaspecificationshall,asaminimum,havecontentswhicharetechnicallyequivalenttoannexB.TheaugmentedpartialPIXITproformamaycontainadditionalquestionsthatneedtobeansweredinordertopreparetheMeansOfTesting(MOT)foraparticularIUT.Atestlaboratory,offeringtestingfortheATSspecificationcontainedinannexC,isrequired,asspecifiedinISO/IEC9646-5[9],tofurtheraugmenttheaugmentedpartialPIXITproformatoproduceaPIXITproformaconformantwiththispartialPIXITproformaspecification.APIXITproformawhichconformstothispartialPIXITproformaspecificationshall,asaminimum,havecontentswhicharetechnicallyequivalenttoannexB.ThePIXITproformamaycontainadditionalquestionsthatneedtobeansweredinordertopreparethetestlaboratoryforaparticularIUT.10ATSconformanceThetestrealizer,producingMOTandExTSforthisATSspecification,shallcomplywiththerequirementsofISO/IEC9646-4[8].Inparticular,theseconcerntherealizationofanExTSbasedoneachATS.ThetestrealizershallprovideastatementofconformanceoftheMOTtothisATSspecification.AnExTSwhichconformstothisATSspecificationshallcontaintestgroupsandtestcaseswhicharetechnicallyequivalenttothosecontainedintheATSinannexC.Allsequencesoftesteventscomprisinganabstracttestcaseshallbecapableofbeingrealizedintheexecutabletestcase.AnyfurthercheckingwhichthetestsystemmightbecapableofperformingisoutsidethescopeofthisATSspecificationandshallnotcontributetotheverdictassignmentforeachtestcase.TestlaboratoriesrunningconformancetestservicesusingthisATSshallcomplywithISO/IEC9646-5[9].AtestlaboratorywhichclaimstoconformtothisATSspecificationshalluseanMOTwhichconformstothisATS.SIST EN 300 195-6 V1.2.1:2005

ETSIETSIEN300195-6V1.2.1(2000-11)19AnnexA(normative):ProtocolConformanceTestReport(PCTR)proformaNotwithstandingtheprovisionsofthecopyrightclauserelatedtothetextofthepresentdocument,ETSIgrantsthatusersofthepresentdocumentmayfreelyreproducethePCTRproformainthisannexsothatitcanbeusedforitsintendedpurposesandmayfurtherpublishthecompletedPCTR.A.1IdentificationsummaryA.1.1ProtocolconformancetestreportPCTRnumber:PCTRdate:CorrespondingSCTRnumber:CorrespondingSCTRdate:Testlaboratoryidentification:Testlaboratorymanager:Signature:A.1.2IUTidentificationName:Version:Protocolspecification:EN300195-1PICS:PreviousPCTRs(ifany):SIST EN 300 195-6 V1.2.1:2005

ETSIETSIEN300195-6V1.2.1(2000-11)20A.1.3TestingenvironmentPIXITrefere
...