SIST EN 301 060-6 V1.1.4:2005

• Abstract:

  Test specification for DE/SPS-05109-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
• Mandate: BC-T-338
• Ref Project: ETSI EN 301 060-6 V1.1.4 (1999-11) - Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Basic call control; Enhancement at the b service entry point for Virtual Private Network (VPN) applications; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network

SIST EN 301 060-6 V1.1.4:2005 is the Slovenian standard identical to ETSI EN 301 060-6 V1.1.4. Published by ETSI, it specifies the test material for Integrated Services Digital Network (ISDN) Digital Subscriber Signalling System No. one (DSS1) basic call control enhancements at the "b" service entry point for Virtual Private Network (VPN) applications. It is aimed at testing the network side of an implementation that conforms to EN 301 060-1.

What does SIST EN 301 060-6 V1.1.4:2005 specify?

SIST EN 301 060-6 V1.1.4:2005 specifies an Abstract Test Suite (ATS) and a partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the network side at the T reference point, or a coincident S and T reference point. The document is used with the DSS1 protocol and the implementation defined in EN 301 060-1.

The standard is organized as follows:

• Clause 1 states the scope.
• Clause 2 lists references.
• Clause 3 gives definitions and abbreviations.
• Clauses 4 to 10 cover the test method, ATS conventions, mapping, and conformance.
• Annex A gives the Protocol Conformance Test Report (PCTR) proforma.
• Annex B gives the partial PIXIT proforma.
• Annex C contains the ATS in TTCN.GR and TTCN.MP forms.

Annex	What it covers
A	PCTR proforma for reporting conformance test results
B	Partial PIXIT proforma for test preparation and configuration
C	ATS in graphical and machine-processable TTCN forms
D	Void
E	General structure of an ATS
F	TTCN.MP and TTCN.GR version history

What are the key requirements of SIST EN 301 060-6 V1.1.4:2005?

SIST EN 301 060-6 V1.1.4:2005 is built for conformance testing of the network DSS1 entity at one user-network interface, not for the whole network. Clause 4 explains that the standard uses a combination of remote and multi-party test methods, with one Main Test Component (MTC) and one or more Parallel Test Components (PTC).

Clause 4 matters because verdicts are taken only from the interface under test, observed at the lower tester point of control and observation (PCO) L0. Events at other interfaces can support the test, but a failure there does not automatically become a FAIL verdict at L0; it may lead to INCONCLUSIVE instead.

Clause 5 states that there are no untestable test purposes in this ATS. That means the test suite is intended to be executable as written, rather than containing test goals that must be skipped.

Clauses 6.1 to 6.3 describe how the ATS is written in TTCN terms:

• type definitions, constraints, constants, parameters, and variables are organized in the declarations part
• no Test Suite Variables are used
• the operation ASSIGN_CHI selects the correct Channel identification information element for basic or primary rate access
• the SETUP transit counter uses special coding with a locking shift to codeset 4
• derived constraints are used only for SETUP and ERROR PDUs
• matching values use the familiar TTCN symbols such as *, ?, and -

In practice, these conventions tell a test realizer how to build a conforming executable suite and how to prepare message data correctly.

Clause 6.3 says each testcase carries the corresponding test purpose text from EN 301 060-3, and test steps are reused to avoid repetition. Clause 7 gives a one-to-one mapping from test purpose identifiers to testcase names. Clauses 8, 9, and 10 require conformance of the PCTR, PIXIT, and ATS implementations against the ISO/IEC 9646 framework.

What terms does SIST EN 301 060-6 V1.1.4:2005 define?

• Abstract Test Suite (ATS) - The set of abstract test cases, constraints, and conventions used to test conformance.
• Implementation Under Test (IUT) - The network entity being assessed against the protocol specification.
• Main Test Component (MTC) - The test component that controls the test and assigns verdicts from the interface under test.
• Parallel Test Components (PTC) - Supporting test components that stimulate or observe other interfaces during multi-party testing.
• Protocol Conformance Test Report (PCTR) - The report form used to record conformance assessment results.
• Protocol Implementation eXtra Information for Testing (PIXIT) - The extra implementation information needed to prepare and run the tests.
• T reference point - The user-network reference point where the network DSS1 entity is tested.
• Virtual Private Network (VPN) - The application context for the basic call control enhancement covered by this standard.

Who uses SIST EN 301 060-6 V1.1.4:2005?

SIST EN 301 060-6 V1.1.4:2005 is used by test laboratories, test realizers, and clients who need conformance evidence for a network implementation. It is also relevant to equipment vendors, network operators, and quality teams working on DSS1 behavior at the user-network interface.

In practice, these users apply it to prepare the Means Of Testing (MOT), complete the PIXIT, run the ATS, and document the outcome in a PCTR.

What changed in SIST EN 301 060-6 V1.1.4:2005 from the previous edition?

The document history lists earlier publications V1.1.2 and V1.1.3 before this V1.1.4 version. Annex F says the first version of the TTCN files is the first edition.

Which standards are used with SIST EN 301 060-6 V1.1.4:2005?

SIST EN 301 060-6 V1.1.4:2005 builds on a set of protocol and conformance-testing references:

• EN 301 060-1 - the protocol specification being tested.
• EN 301 060-2 - the PICS proforma for the series.
• EN 301 060-3 - the user-side TSS & TP specification, whose test purpose text is reused.
• EN 301 060-4 - the user-side ATS and PIXIT proforma.
• EN 301 060-5 - the network-side TSS & TP specification referenced for untestable test purposes.
• ISO/IEC 9646-1/2/3/4/5 - the conformance testing framework, ATS method, TTCN, test realization, and laboratory requirements.
• EN 300 403-1 - the basic call control signalling network layer base specification.
• CCITT I.130, ITU-T I.411, I.112, I.210, and E.164 - the service, reference configuration, ISDN vocabulary, service principles, and numbering definitions used by the document.

What does the SIST EN 301 060-6 V1.1.4:2005 document contain?

SIST EN 301 060-6 V1.1.4:2005 contains a TTCN-based ATS, a PCTR proforma, and a partial PIXIT proforma. It also includes the structure notes for ATS development and the version history for the TTCN.GR and TTCN.MP files.

Annex C points to the graphical and machine-processable TTCN files that accompany the standard. Annex A and Annex B provide the forms a lab uses to capture test setup, configuration, and results.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.SUHVNXãDQMHIntegrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Basic call control; Enhancement at the b service entry point for Virtual Private Network (VPN) applications; 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 301 060-6 Version 1.1.4SIST EN 301 060-6 V1.1.4:2005en01-januar-2005SIST EN 301 060-6 V1.1.4:2005SLOVENSKI
STANDARD
ETSIEN301060-6V1.1.4(1999-11)EuropeanStandard(Telecommunicationsseries)IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Basiccallcontrol;Enhancementatthe"b"serviceentrypointforVirtualPrivateNetwork(VPN)applications;Part6:AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforthenetworkSIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)2ReferenceDEN/SPS-05109-6(9tdi0ieo.PDF)KeywordsATS,ISDN,DSS1,basic,PIXIT,network,VPNETSIPostaladdressF-06921SophiaAntipolisCedex-FRANCEOfficeaddress650RoutedesLucioles-SophiaAntipolisValbonne-FRANCETel.:[phone]Fax:[phone]SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/[e-mail]ETSIdeliverablecanbedownloadedfromhttp://www.etsi.orgIfyoufinderrorsinthepresentdocument,sendyourcommentto:[e-mail]Ideliverablemaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshouldbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.CopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute1999.Allrightsreserved.SIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)3ContentsIntellectualPropertyRights.5Foreword.51Scope.62References.63Definitionsandabbreviations.73.1Definitions.73.1.1Definitionsrelatedtoconformancetesting.73.1.2DefinitionsrelatedtoEN301060-1.83.2Abbreviations.84AbstractTestMethod.94.1DescriptionofATMused.94.2ConventionsfortestcomponentsandPCOs.95Untestabletestpurposes.106ATSconventions.116.1Declarationspart.116.1.1Typedefinitions.116.1.1.1Simpletypedefinitions.116.1.1.2Structuredtypedefinitions.116.1.1.2.1TTCNstructuredtypedefinitions.116.1.1.2.2ASN.1structuredtypedefinitions.116.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.126.1.4.1Testsuitevariables.126.1.4.2Testcasevariables.136.1.5Testsuiteoperationdefinitions.136.2Constraintspart.136.2.1Structuredtypeconstraintdeclaration.136.2.2ASN.1typeconstraintdeclaration.136.2.3ASPtypeconstraintdeclaration.136.2.3.1ASN.1ASPtypeconstraintdeclaration.136.2.3.2TTCNASPtypeconstraintdeclaration.146.2.4PDUtypeconstraintdeclaration.146.2.4.1ASN.1PDUtypeconstraintdeclaration.146.2.4.2TTCNPDUtypeconstraintdeclaration.146.2.4.3Specialcoding.146.2.5Derivedconstraints.146.2.6Parameterizedconstraints.146.2.7Valueassignment.146.2.7.1Specificvalues.146.2.7.2Matchingvalues.156.3Dynamicpart.156.3.1Testcases.156.3.2Teststeps.156.3.3Defaults.15SIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)47ATStoTPmap.158PCTRconformance.159PIXITconformance.1610ATSConformance.16AnnexA(normative):ProtocolConformanceTestReport(PCTR)proforma.17A.1Identificationsummary.17A.1.1Protocolconformancetestreport.17A.1.2IUTidentification.17A.1.3Testingenvironment.17A.1.4Limitsandreservations.18A.1.5Comments.18A.2IUTConformancestatus.18A.3Staticconformancesummary.18A.4Dynamicconformancesummary.19A.5Staticconformancereviewreport.19A.6Testcampaignreport.19A.7Observations.32AnnexB(normative):PartialPIXITproforma.33B.1Identificationsummary.33B.2Abstracttestsuitesummary.33B.3Testlaboratory.34B.4Client(oftheTestlaboratory).34B.5SUT.35B.6Protocolinformation.35B.6.1Protocolidentification.35B.6.2Configurationtobetested.36B.6.3Configurationoptions.36B.6.4Testmanagementtimers.37B.6.5SendingofmessagesbyIUT.37B.6.6Parametervalues.38AnnexC(normative):AbstractTestSuite(ATS).40C.1TheTTCNGraphicalform(TTCN.GR).40C.2TheTTCNMachineProcessableform(TTCN.MP).40AnnexD(normative):Void.41AnnexE(informative):GeneralstructureofATS.42AnnexF(informative):"TTCN.MPandTTCN.GR"versionhistory.43Bibliography.44History.45SIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)5IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinSR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinSR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSITechnicalCommitteeSignallingProtocolandSwitching(SPS).Thepresentdocumentispart6ofamulti-partstandardcoveringtheDigitalSubscriberSignallingSystemNo.one(DSS1)protocolspecificationfortheIntegratedServicesDigitalNetwork(ISDN)Basiccallcontrolextensionsatthe"b"serviceentrypointforVPNapplications,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:12November1999DateoflatestannouncementofthisEN(doa):29February2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31August2000DateofwithdrawalofanyconflictingNationalStandard(dow):31August2000SIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)61ScopeThissixthpartofEN301060isapplicabletotheBasiccallcontrolextensionsatthe"b"serviceentrypointforVPNapplicationsforthepan-EuropeanIntegratedServicesDigitalNetwork(ISDN)asprovidedbyEuropeanpublictelecommunicationsoperatorsattheTreferencepoint(asdefinedinITU-TRecommendationI.411[8])bymeansoftheDigitalSubscriberSignallingSystemNo.one(DSS1)protocol.Stagethreeidentifiestheprotocolproceduresandswitchingfunctionsneededtosupportatelecommunicationsservice(seeCCITTRecommendationI.130[7]).ThepresentdocumentspecifiestheAbstractTestSuite(ATS),andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformafortheusersideoftheTreferencepointorcoincidentSandTreferencepointofimplementationconformingtoEN301060-1[2]incompliancewiththerelevantrequirementsandinaccordancewiththerelevantguidancegiveninISO/IEC9646[3]to[6].2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]EN300403-1(V1.3):"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Signallingnetworklayerforcircuit-modebasiccallcontrol;Part1:Protocolspecification[ITU-TRecommendationQ.931(1993),modified]".[2]EN301060-1:"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Basiccallcontrol;Enhancementatthe"b"serviceentrypointforVirtualPrivateNetwork(VPN)applications;Part1:Protocolspecification".[3]ISO/IEC9646-1:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[4]ISO/IEC9646-3:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part3:TheTreeandTabularCombinedNotation(TTCN)".[5]ISO/IEC9646-4:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part4:Testrealization".[6]ISO/IEC9646-5:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part5:Requirementsontestlaboratoriesandclientsfortheconformanceassessmentprocess".[7]CCITTRecommendationI.130(1988):"MethodforthecharacterizationoftelecommunicationservicessupportedbyanISDNandnetworkcapabilitiesofanISDN".[8]ITU-TRecommendationI.411(1993):"ISDNuser-networkinterfaces-Referenceconfigurations".[9]EN301060-2(V1.1):"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Basiccallcontrol;Enhancementatthe"b"serviceentrypointforVirtualPrivateNetwork(VPN)applications;Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecification".SIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)7[10]EN301060-3(V1.1):"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Basiccallcontrol;Enhancementatthe"b"serviceentrypointforVirtualPrivateNetwork(VPN)applications;Part3:TestSuiteStructureandTestPurposes(TSS&TP)specificationfortheuser".[11]ITU-TRecommendationI.112(1993):"VocabularyoftermsforISDNs".[12]ITU-TRecommendationI.210(1993):"PrinciplesoftelecommunicationservicessupportedbyanISDNandthemeanstodescribethem".[13]ITU-TRecommendationE.164(1997):"Theinternationalpublictelecommunicationnumberingplan".[14]ISO/IEC9646-2:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part2:Abstracttestsuitespecification".[15]EN301060-4(V1.1):"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Basiccallcontrol;Enhancementatthe"b"serviceentrypointforVirtualPrivateNetwork(VPN)applications;Part4:AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationfortheuser".[16]EN301060-5(V1.1):"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Basiccallcontrol;Enhancementatthe"b"serviceentrypointforVirtualPrivateNetwork(VPN)applications;Part5:TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetwork".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply.3.1.1Definitionsrelatedtoconformancetestingabstracttestcase:refertoISO/IEC9646-1[3]AbstractTestSuite(ATS):refertoISO/IEC9646-1[3]activetest:testcasewheretheIUTisrequiredtosendaparticularmessage,butnotinreactiontoareceivedmessage.ThiswouldusuallyinvolvetheuseofPIXITinformationtoseehowthismessagecanbegeneratedandquiteoftenisspecifiedinanATSusinganimplicitsendeventImplementationUnderTest(IUT):refertoISO/IEC9646-1[3]implicitsendevent:refertoISO/IEC9646-3[4]lowertester:refertoISO/IEC9646-1[3]passivetest:testcasewheretheIUTisrequiredtorespondtoaprotocolevent(e.g.receivedmessage)withanotherprotocolevent(e.g.sendmessage)whichnormallydoesnotrequireanyspecialoperatorinterventionasassociatedwiththeimplicitsendeventpointofcontrolandobservation:refertoISO/IEC9646-1[3]ProtocolImplementationConformanceStatement(PICS):refertoISO/IEC9646-1[3]PICSproforma:refertoISO/IEC9646-1[3]ProtocolImplementationeXtraInformationforTesting(PIXIT):refertoISO/IEC9646-1[3]SIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)8PIXITproforma:refertoISO/IEC9646-1[3]systemundertest:refertoISO/IEC9646-1[3]TestPurpose(TP):refertoISO/IEC9646-1[3]3.1.2DefinitionsrelatedtoEN301060-1Dummycallreference:seeEN300403-1[1],subclause4.3IntegratedServicesDigitalNetwork(ISDN):seeITU-TRecommendationI.112[11],definition308ISDNnumber:numberconformingtothenumberingandstructurespecifiedinITU-TRecommendationE.164[13]service;telecommunicationservice:seeITU-TRecommendationI.112[11],definition201supplementaryservice:seeITU-TRecommendationI.210[12],subclause2.4T:DSS1protocolentityattheUsersideoftheuser-networkinterfacewhereaTreferencepointapplies(UserisaPrivateISDN)3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ASPAbstractServicePrimitiveATMAbstractTestMethodATSAbstractTestSuiteBABasicAccessCESConnectionEndpointSuffixCMCo-ordinationMessageDSS1DigitalSubscriberSignallingSystemNo.oneExTSExecutableTestSuiteISDNIntegratedServicesDigitalNetworkIUTImplementationUnderTestLTLowerTesterMOTMeansOfTestingMTCMainTestComponentPCOPointofControlandObservationPCTRProtocolConformanceTestReportPDUProtocolDataUnitPICSProtocolImplementationConformanceStatementPIXITProtocolImplementationeXtraInformationforTestingPRAPrimaryRateAccessPTCParallelTestComponentsSUTSystemUnderTestTPTestPurposeTSSTestSuiteStructureTTCNTreeandTabularCombinedNotationUTUpperTesterVPNVirtualPrivateNetworkSIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)94AbstractTestMethod4.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 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)10Thismeans,inparticular,thattheverdictwillonlybeassignedfromtheprotocolaspectsobservedontheinterfaceundertest(i.e.bythe"master"tester),asitwouldbeobservedbyaterminalconnectedtothisinterface.Afailureinthecorrelationbetweentheprotocolatthedifferentinterfacestowhichthedifferenttestersareconnected,i.e.inthemechanismofthefunctionalserviceitself,willnotcauseaFAILverdict.Forinstance,iftheIUTfailstosendamessageonthetestedinterfaceafteranotherinterfacehasreceivedtheproperstimulus,theverdictwillbeINCONCLUSIVE.TheMTCMTCAhastwofunctionsinthisconfiguration.Firstly,ithastheMTCfunctionofcontrollingtheoneormorePTCs.ThusitisresponsibleforstartingthePTCsandafterwardscoordinatesactivitiesbyexchangingCo-ordinationMessages(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.5UntestabletestpurposesTherearenountestabletestpurposesinthisATS.SeeEN301060-5[16].SIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)116ATSconventionsThisclauseisstructuredsimilarlytothestructureofaTTCNATS.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.1structuredtypedefinitionsTherearenoASN.1structuredtypedefinitionsintheATS.6.1.1.3ASPtypedefinitions6.1.1.3.1TTCNASPtypedefinitionsTTCNASPtypedefinitionsonlycontainonePDUornoPDUatall.AllTTCNASPtypedefinitionsareprovidedwithafullidentifier.SomeASPsarenotparameterizedasshownintheexampleintable1.SuchASPsareonlyusedforrequestingorreceivingservicefromthelowerlayer.SIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)12Table1:TTCNASPtypedefinitionDL_REL_INTTCNASPTypeDefinitionASPNAME:DL_REL_IN(DL_RELEASE_INDICATION)PCOType:SAPComments:ParameterName|ParameterType|CommentsDetailedComments:Table2showsanexampleofaparameterizedASP.AllASPscontainingPDUscontainonlythatPDUandnootherparameters.Table2:TTCNASPtypedefinitionDL_DATA_RQTTCNASPTypeDefinitionASPNAME:DL_DATA_RQ(DL_DATA_REQUEST)PCOType:SAPComments:ParameterName|ParameterType|Commentsmun(MessageUnit)|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.2TestsuiteconstantsEachtestsuiteconstantisdefinedintermsofapredefinedtypeorareferencedtype.Thevaluesgiveninthevaluecolumnwillremainunchangedthroughoutthetestsuite.6.1.3TestsuiteparametersEachtestsuiteparameterisdefinedintermsofapredefinedtypeorareferencedtype.Areferencedtypeisusedwhenitisnecessarytoattachrestrictionstothesetypedefinitions(itisnotallowedtoincluderestrictionsdirectlyinthetestsuiteparametertable).Thereferencedtypecanhavealengthorvaluerestrictionattachedtoitinitsdeclarationtable.6.1.4Variables6.1.4.1TestsuitevariablesNoTestSuiteVariablesareusedordefinedinthisATS.SIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)136.1.4.2TestcasevariablesEachtestcasevariableisdefinedintermsofapredefinedtypeorareferencedtype.Areferencedtypeisusedwhenitisnecessarytoattachrestrictionstothesetypedefinitions(itisnotallowedtoincluderestrictionsdirectlyinthetestcasevariabletable).Thereferencedtypecanhavealengthorvaluerestrictionattachedtoitinitsdeclarationtable.Wheretestcasevariablesareusedinconstraints,theyarepassedasformalparameters.6.1.5TestsuiteoperationdefinitionsThedescriptionpartofatestsuiteoperationdefinitionuseseithernaturallanguageormetaC.Table3:TestsuiteoperationdefinitionASSIGN_CHITestSuiteOperationDefinitionOperationName:ASSIGN_CHI(basic,primary:CHI;basic_flag:BOOLEAN)ResultType:CHIComments:ThisoperationisusedtoassignacorrectChannelidentificationinformationelementtoPDUsdependentonthetypeofaccessthatistested.DescriptionCHIASSIGN_CHI(basic,primary,basic_flag)Ifthevalueofthebasic_flagissettoTRUE,theresultoftheoperationASSIGN_CHIwillbethevaluerepresentedbytheparameterbasicwhichisoftypeCHI.Elsetheoperationresultsinthevaluerepresentedbytheparameterprimary.Examples:ASSIGN_CHI(CHI1b_R1,CHI1p_R1,TRUE)=CHI1b_R1ASSIGN_CHI(CHI1b_R1,CHI1p_R1,FALSE)=CHI1p_R1Detailedcomments:Thetestsuiteoperationdefinitionshownintable3isusedintheconstraintspartwhenassigninganelementoftypeCHIavalue.TheCHItypecanbedefinedintwowaysdependingonwhethertheATSistestingbasicorprimaryrateaccess.ToavoidduplicatetypesandtherebyduplicatetestcasesthisoperationisusedtoassignavaluetoanelementofCHItype.Ittakesthreeparameters:ThisoperationreturnsthecorrectconstraintaccordingtotheBooleanflagbasic_flag.ThatconstraintwillthenbeassignedtothespecificelementoftypeCHI.6.2Constraintspart6.2.1StructuredtypeconstraintdeclarationForeverystructuredtypedefinitionthereexistsoneormorestructuredtypeconstraint.6.2.2ASN.1typeconstraintdeclarationTherearenoASN.1typeconstraintdeclarationsintheATS.6.2.3ASPtypeconstraintdeclaration6.2.3.1ASN.1ASPtypeconstraintdeclarationTherearenoASN.1ASPtypeconstraintdeclarationsintheATS.SIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)146.2.3.2TTCNASPtypeconstraintdeclarationThePDUstobesentorreceivedarepassedtotheTTCNASPconstraintdeclarationsMsandMrasparametersofmetatypePDU.OnlyifvaluesinsideaspecificPDUhavetobereferenced,theuseofthemetatypePDUisnotallowedaccordingtoISO/IEC9646-3[4].InsuchcasesdifferentTTCNASPconstraintdeclarationsareused,thataredefinedtocarryonlyaspecifictypeofPDU(e.g.SETUP).Table4showsanexampleofsuchaTTCNASPconstraintdeclaration.Table4:TTCNASPconstraintdeclarationSrTTCNASPConstraintDeclarationConstraintName:Sr(PARAM:SETUP_PDU)ASPType:DL_DAT_IN_SETUPDerivationPath:Comments:ASPtoindicatethereceiptofSETUPmessages.ParameterName|ParameterValue|Commentsmun|PARAM|DetailedComments:AllASPconstraintshaveaspecificvalueforitsparameter.NomatchingsymbolsareusedinASPs.6.2.4PDUtypeconstraintdeclaration6.2.4.1ASN.1PDUtypeconstraintdeclarationTherearenoASN.1PDUtypeconstraintdeclarationsintheATS.6.2.4.2TTCNPDUtypeconstraintdeclarationPDUconstraintsareusedforassigningvaluesorpatternstothedatabeingsentorreceived.6.2.4.3SpecialcodingTheinformationelementtransitcounter,presentintheSETUPPDU,shallbedefinedincodeset4,forthispurposetheATSiscodingthisIEwithalockingshift(codeset4)attheendofthePDUSETUP.6.2.5DerivedconstraintsDerivedconstraintsareusedinthisATSonlyforSETUPandERRORPDUs.6.2.6ParameterizedconstraintsParameterizedconstraintsareusedinthisATS.6.2.7Valueassignment6.2.7.1SpecificvaluesForspecificvalueassignmentbothexplicitvaluesandreferencestoexplicitvaluesareused.SIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)156.2.7.2MatchingvaluesAsmatchingvaluesthefollowingmechanismsareused:InsteadofValue:AnyOrOmit"*"AnyValue"?"Omit"-"Insidevalue:AnyOne"?"AnyOrNone"*"6.3Dynamicpart6.3.1TestcasesEachtestcasecontainsthetestpurposetextfromEN301060-3[10].Tobeabletoreadandunderstandthetestcasedynamicbehaviouritisrecommendedthattheteststepsareunderstoodfirst.6.3.2TeststepsMuchusehasbeenmadeofteststepstoavoidneedlessrepetitionofdynamicbehaviour.6.3.3DefaultsNotetheuseoftheRETURNstatementwhichisdefinedinDAM1ofISO/IEC9646-3[4].Thisallowsvalidbackgroundbehaviourtobehandledinthedefaulttreewithapossibilitytoreturntotheoriginalsetofalternativesinthetestcase.7ATStoTPmapTheidentifiersusedfortheTPsarereusedastestcasenames.Thusthereisastraightforwardone-to-onemapping.8PCTRconformanceAtestlaboratory,whenrequestedbyaclienttoproduceaPCTR,isrequired,asspecifiedinISO/IEC9646-5[6],toproduceaPCTRconformantwiththePCTRtemplategiveninannexBofISO/IEC9646-5[6].Furthermore,atestlaboratory,offeringtestingfortheATSspecificationcontainedinannexC,whenrequestedbyaclienttoproduceaPCTR,isrequiredtoproduceaPCTRconformantwiththePCTRproformacontainedinannexAofthepresentdocument.APCTRwhichconformstothisPCTRproformaspecificationshallpreservethecontentandorderingoftheclausescontainedinannexA.ClauseA.6ofthePCTRmaycontainadditionalcolumns.Ifincluded,theseshallbeplacedtotherightoftheexistingcolumns.Textinitalicsmayberetainedbythetestlaboratory.SIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)169PIXITconformanceAtestrealizer,producinganexecutabletestsuitefortheAbstractTestSuite(ATS)specificationcontainedinannexC,isrequired,asspecifiedinISO/IEC9646-4[5],toproduceanaugmentedpartialPIXITproformaconformantwiththispartialPIXITproformaspecification.AnaugmentedpartialPIXITproformawhichconformstothispartialPIXITproformaspecificationshall,asaminimum,havecontentswhicharetechnicallyequivalenttoannexB.TheaugmentedpartialPIXITproformamaycontainadditionalquestionsthatneedtobeansweredinordertopreparetheMeansOfTesting(MOT)foraparticularImplementationUnderTest(IUT).Atestlaboratory,offeringtestingfortheATSspecificationcontainedinannexC,isrequired,asspecifiedinISO/IEC9646-5[6],tofurtheraugmenttheaugmentedpartialPIXITproformatoproduceaPIXITproformaconformantwiththispartialPIXITproformaspecification.APIXITproformawhichconformstothispartialPIXITproformaspecificationshall,asaminimum,havecontentswhicharetechnicallyequivalenttoannexB.ThePIXITproformamaycontainadditionalquestionsthatneedtobeansweredinordertopreparethetestlaboratoryforaparticularIUT.10ATSConformanceThetestrealizer,producingaMeansOfTesting(MOT)andExecutableTestSuite(ExTS)forthisAbstractTestSuite(ATS)specification,shallcomplywiththerequirementsofISO/IEC9646-4[5].Inparticular,theseconcerntherealizationofanExecutableTestSuite(ExTS)basedoneachATS.ThetestrealizershallprovideastatementofconformanceoftheMOTtothisATSspecification.AnExTSwhichconformstothisATSspecificationshallcontaintestgroupsandtestcaseswhicharetechnicallyequivalenttothosecontainedintheATSinannexC.Allsequencesoftesteventscomprisinganabstracttestcaseshallbecapableofbeingrealizedintheexecutabletestcase.AnyfurthercheckingwhichthetestsystemmightbecapableofperformingisoutsidethescopeofthisATSspecificationandshallnotcontributetotheverdictassignmentforeachtestcase.TestlaboratoriesrunningconformancetestservicesusingthisATSshallcomplywithISO/IEC9646-5[6].AtestlaboratorywhichclaimstoconformtothisATSspecificationshalluseanMOTwhichconformstothisATS.SIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)17AnnexA(normative):ProtocolConformanceTestReport(PCTR)proformaNotwithstandingtheprovisionsofthecopyrightclauserelatedtothetextofthepresentdocument,ETSIgrantsthatusersofthepresentdocumentmayfreelyreproducethePCTRproformainthisannexsothatitcanbeusedforitsintendedpurposesandmayfurtherpublishthecompletedPCTR.A.1IdentificationsummaryA.1.1ProtocolconformancetestreportPCTRnumber:PCTRDate:CorrespondingSCTRnumber:CorrespondingSCTRdate:TestLaboratoryidentification:TestLaboratoryManager:Signature:A.1.2IUTidentificationName:Version:Protocolspecification:EN301060-1PICS:PreviousPCTRs(ifany)A.1.3TestingenvironmentPIXITReferencenumber:ATSSpecification:EN301060-6AbstractTestMethod:Multy-Partytestmethod(seeISO/IEC9646-2)MeansofTestingidentification:Datesoftesting:ConformanceLogreference(s):RetentionDateforLogreference(s):SIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)18A.1.4LimitsandreservationsAdditionalinformationrelevanttothetechnicalcontentsorfurtheruseofthetestreport,ortotherightsandobligationsofthetestlaboratoryandtheclient,maybegivenhere.Suchinformationmayincluderestrictiononthepublicationofthereport.____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________A.1.5CommentsAdditionalcommentsmaybegivenbyeithertheclientorthetestlaboratoryonanyofthecontentsofthePCTR,forexample,tonotedisagreementbetweenthetwoparties.________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________A.2IUTConformancestatusThisIUThasorhasnotbeenshownbyconformanceassessmenttobenon-conformingtothespecifiedprotocolspecification.Striketheappropriatewordsinthissentence.IfthePICSforthisIUTisconsistentwiththestaticconformancerequirements(asspecifiedinclauseA.3ofthisreport)andthereareno"FAIL"verdictstoberecorded(inclauseA.6)strikethewords"hasor",otherwisestrikethewords"orhasnot".A.3StaticconformancesummaryThePICSforthisIUTisorisnotconsistentwiththestaticconformancerequirementsinthespecifiedprotocol.Striketheappropriatewordsinthissentence.SIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)19A.4DynamicconformancesummaryThetestcampaigndidordidnotrevealerrorsintheIUT.Striketheappropriatewordsinthissentence.Ifthereareno"FAIL"verdictstoberecorded(inclauseA.6ofthisreport)strikethewords"didor",otherwisestrikethewords"ordidnot".Summaryoftheresultsofgroupsoftests:________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________A.5StaticconformancereviewreportIfclauseA.3indicatesnon-conformance,thissubclauseitemizesthemismatchesbetweenthePICSandthestaticconformancerequirementsofthespecifiedprotocolspecification.________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________A.6TestcampaignreportATSReferenceSelected?(Y/N)Run?(Y/N)VerdictObservationsCallstateN00L3N_N00_V_001L3N_N00_V_002L3N_N00_V_003L3N_N00_V_004L3N_N00_V_005L3N_N00_V_006L3N_N00_V_007L3N_N00_V_008L3N_N00_V_009L3N_N00_V_010L3N_N00_V_011L3N_N00_V_012L3N_N00_V_013L3N_N00_V_014L3N_N00_V_015L3N_N00_V_016L3N_N00_V_017L3N_N00_V_018L3N_N00_V_019L3N_N00_V_020L3N_N00_V_021SIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)20ATSReferenceSelected?(Y/N)Run?(Y/N)VerdictObservationsL3N_N00_V_022L3N_N00_V_023L3N_N00_V_024L3N_N00_V_025L3N_N00_V_026L3N_N00_V_027L3N_N00_V_028L3N_N00_V_029L3N_N00_V_030L3N_N00_V_031L3N_N00_V_v01L3N_N00_V_v02L3N_N00_V_v03L3N_N00_V_v04L3N_N00_V_v05L3N_N00_V_v06L3N_N00_V_v07L3N_N00_V_v08L3N_N00_V_032L3N_N00_V_033L3N_N00_V_034L3N_N00_V_035L3N_N00_V_036L3N_N00_V_037L3N_N00_V_038L3N_N00_V_039L3N_N00_V_040L3N_N00_V_v09L3N_N00_V_v10L3N_N00_V_v11L3N_N00_V_v12L3N_N00_V_v13L3N_N00_V_v14L3N_N00_V_v15L3N_N00_I_001L3N_N00_I_002L3N_N00_I_003L3N_N00_I_004L3N_N00_I_005L3N_N00_I_007L3N_N00_I_008L3N_N00_I_009L3N_N00_I_010L3N_N00_I_011L3N_N00_I_012L3N_N00_S_001L3N_N00_S_002L3N_N00_S_003L3N_N00_S_004L3N_N00_S_005L3N_N00_S_006L3N_N00_S_007L3N_N00_S_008L3N_N00_S_009L3N_N00_S_010L3N_N00_S_011L3N_N00_S_012L3N_N00_S_v16L3N_N00_S_v17L3N_N00_S_v18L3N_N00_S_v19SIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)21ATSReferenceSelected?(Y/N)Run?(Y/N)VerdictObservationsCallstateN02L3N_N02_V_001L3N_N02_V_002L3N_N02_V_003L3N_N02_V_004L3N_N02_V_005L3N_N02_V_006L3N_N02_V_007L3N_N02_V_008L3N_N02_V_009L3N_N02_V_010L3N_N02_V_011L3N_N02_V_012L3N_N02_V_013L3N_N02_I_001L3N_N02_I_002L3N_N02_I_003L3N_N02_I_004L3N_N02_I_005L3N_N02_I_006L3N_N02_I_007L3N_N02_I_008L3N_N02_I_009L3N_N02_I_011L3N_N02_S_001L3N_N02_S_002L3N_N02_S_003L3N_N02_S_004L3N_N02_S_005L3N_N02_S_006L3N_N02_S_007L3N_N02_S_008L3N_N02_S_009L3N_N02_S_010SIST EN 301 060-6 V1.1.4:2005

ETSIETSIEN301060-6V1.1.4(1999-11)22ATSReferenceSelected?(Y/N)Run?(Y/N)VerdictObservationsCallstateN03L3N_N03_V_001L3N_N03_V_002L3N_N03_V_003L3N_N03_V_004L3N_N03_V_005L3N_N03_V_006L3N_N03_V_007L3N_N03_V_008L3N_N03_V_009L3N_N0
...