SIST EN 301 144-4 V1.1.4:2005

• Abstract:

  Test specification for DE/SPS-05121-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 144-4 V1.1.4 (2000-05) - Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) and Signalling System No.7 protocols; Signalling application for the mobility management service on the alpha interface; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the user

SIST EN 301 144-4 V1.1.4:2005 is the SIST adoption of the ETSI European Standard for the Integrated Services Digital Network (ISDN) signalling application for the mobility management service on the alpha interface. It specifies the Abstract Test Suite (ATS) and the partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the user side, so test laboratories and implementers can prepare and run conformance tests for the protocol in EN 301 144-1. The document is a test specification for DE/SPS-05121-1 and uses the remote test method.

What does SIST EN 301 144-4 V1.1.4:2005 specify?

SIST EN 301 144-4 V1.1.4:2005 specifies the ATS and partial PIXIT proforma for the user of the signalling application for the mobility management service on the alpha interface. It applies to all types of exchanges defined in the reference specification.

The document is organized around the test method, ATS conventions, ATS-to-TP mapping, and conformance rules, followed by normative annexes for the report and proforma material.

Annex	What it covers
Annex A	Partial Protocol Conformance Test Report (PCTR) proforma
Annex B	Partial PIXIT proforma
Annex C	Abstract Test Suite (ATS) in TTCN.GR and TTCN.MP form
Annex D	General structure of an ATS

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

Clause 4 defines a remote test method. The Point of Control and Observation (PCO) named L sits at the service access point between layers 2 and 3, and test verdicts are assigned from behaviour observed at that PCO. A second PCO, O, is used to coordinate operator actions above the IUT, but it does not drive verdicts. In practice, this means the test system must both observe protocol behaviour and coordinate external actions during the test.

Clause 5 states that there are no untestable test purposes associated with the ATS. For users, that means the ATS is intended to cover the listed test purposes without leaving special cases outside the design.

Clause 6 fixes the ATS conventions. It uses the TTCN version defined in TR 101 101, sets naming rules for test suite objects, timers, PCOs, constraints and test steps, and explains when ASN.1 is used. This matters because toolchains and executable test suites must follow the same naming and encoding logic to stay aligned with the specification.

Clause 6.3 also explains the encoding rules for ASN.1. The default is the direct encoding used by this ATS, while BER is used only where explicitly indicated, and Component constraints are encoded with BER. That tells the test realizer how to encode test data consistently.

Clause 7 maps the test purposes from EN 301 144-3 directly to test case names. This gives a one-to-one link between the TSS&TP document and the ATS, so users can trace each abstract test case back to the corresponding purpose.

Clauses 8 to 10 define conformance for the PCTR, PIXIT and ATS. A test laboratory producing a PCTR or PIXIT must follow the ISO/IEC 9646 requirements and the annexed proformas, and an executable test suite must be technically equivalent to the ATS in Annex C.

Annex A and Annex B also matter in practice because they collect the information needed to run and report tests: the IUT identification, test environment, limits and reservations, protocol information, configuration actions, timer values, and parameter values for basic call and CTM-related items.

What terms does SIST EN 301 144-4 V1.1.4:2005 define?

• Abstract Test Suite (ATS) - The abstract set of test cases and related structure used to assess conformance.
• Protocol Implementation eXtra Information for Testing (PIXIT) - Implementation-specific information needed to prepare the Means of Testing for a particular IUT.
• Protocol Conformance Test Report (PCTR) - The report format used to record the outcome of conformance assessment.
• Implementation Under Test (IUT) - The implementation being assessed against the protocol specification.
• Point of Control and Observation (PCO) - The interface where the tester controls and observes protocol behaviour.
• Tree and Tabular Combined Notation (TTCN) - The notation used to express the ATS in Annex C.
• Basic Encoding Rules (BER) - The ASN.1 encoding method used where the ATS explicitly calls for it.

Who uses SIST EN 301 144-4 V1.1.4:2005?

SIST EN 301 144-4 V1.1.4:2005 is used by test laboratories, test realizers, and clients requesting conformance assessment for implementations of EN 301 144-1. It is also used by teams preparing the PICS and PIXIT information needed to configure the SUT and by engineers building the Means of Testing for the ATS.

In practice, the document supports test campaign planning, test execution, verdict recording, and report preparation for implementations of the mobility management service on the alpha interface.

Which standards are used with SIST EN 301 144-4 V1.1.4:2005?

• EN 301 144-1 - The protocol specification being tested.
• EN 301 144-2 - The PICS proforma referenced in the PIXIT note.
• EN 301 144-3 - The user-side TSS&TP document that supplies the test purposes mapped to the ATS.
• ISO/IEC 9646-2, 9646-3, 9646-4, 9646-5 - The conformance testing framework used for abstract test suites, test realization, and laboratory requirements.
• TR 101 101 - The TTCN interim version used by this ATS.
• ISO/IEC 8825-1 - The ASN.1 encoding rules referenced for BER.
• ETS 300 175-5 - The DECT Common Interface reference used for several CTM-related parameter encodings.
• EN 300 196-1 - The DSS1 protocol reference cited for BER length handling.

What does the SIST EN 301 144-4 V1.1.4:2005 document contain?

Annex A provides a structured PCTR proforma with identification, conformity summary, campaign report and observations. Annex B provides a partial PIXIT proforma with protocol identification, IUT information, configuration actions, timer values, and parameter values for information element codings and CTM-related items.

Annex C contains the ATS itself in two forms: TTCN.GR and TTCN.MP. The document notes that the ATS was produced using TTCN and that the graphical and machine-processable representations accompany the standard as separate files.

Annex D gives the general structure of an ATS, which helps readers find common parts quickly.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.LJLWDOQHIntegrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) and Signalling System No.7 protocols; Signalling application for the mobility management service on the alpha interface; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the user33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 301 144-4 Version 1.1.4SIST EN 301 144-4 V1.1.4:2005en01-januar-2005SIST EN 301 144-4 V1.1.4:2005SLOVENSKI
STANDARD
ETSIEN301144-4V1.1.4(2000-05)EuropeanStandard(Telecommunicationsseries)IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)andSignallingSystemNo.7protocols;Signallingapplicationforthemobilitymanagementserviceonthealphainterface;Part4:AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationfortheuserSIST EN 301 144-4 V1.1.4:2005

ETSIETSIEN301144-4V1.1.4(2000-05)2ReferenceDEN/SPS-05121-4KeywordsATS,CTM,DSS1,ISDN,PIXIT,SS7,userETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:[phone]Fax:[phone]SiretN°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:[e-mail]opartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 301 144-4 V1.1.4:2005

ETSIETSIEN301144-4V1.1.4(2000-05)3ContentsIntellectualPropertyRights.5Foreword.51Scope.62References.63Definitionsandabbreviations.73.1Definitions.73.2Abbreviations.74AbstractTestMethod(ATM).75Untestabletestpurposes.86ATSconventions.86.1VersionofTTCNused.86.2Namingconventions.86.2.1Declarationspart.86.2.1.1Testsuitetypeandstructuredtypedefinitions.86.2.1.2Testsuiteoperationsdefinitions.86.2.1.3Testsuiteparameterdeclarations.86.2.1.4Testcaseselectionexpressiondefinitions.96.2.1.5Testsuiteconstantdeclarations.96.2.1.6Testsuitevariabledeclarations.96.2.1.7Testcasevariabledeclarations.96.2.1.8PCOdeclarations.96.2.1.9Timerdeclarations.96.2.1.10ASPtypedefinitions.96.2.1.11PDUtypedefinitions.96.2.2Constraintspart.96.2.2.1Structuredtypeconstraint.96.2.2.2PDUconstraint.96.2.3Dynamicpart.106.2.3.1Teststepidentifier.106.3UseofASN.1.106.3.1SituationswhereASN.1isused.106.3.2Specificationofencodingrules.107ATStoTPmapping.118PCTRconformance.119PIXITconformance.1110ATSconformance.11AnnexA(normative):PartialPCTRproforma.12A.1Identificationsummary.12A.1.1Protocolconformancetestreport.12A.1.2IUTidentification.12A.1.3Testingenvironment.12A.1.4Limitsandreservations.13A.1.5Comments.13SIST EN 301 144-4 V1.1.4:2005

ETSIETSIEN301144-4V1.1.4(2000-05)4A.2IUTconformancestatus.13A.3Staticconformancesummary.13A.4Dynamicconformancesummary.13A.5Staticconformancereviewreport.14A.6Testcampaignreport.14A.7Observations.19AnnexB(normative):PartialPIXITproforma.20B.1Identificationsummary.20B.2Abstracttestsuitesummary.20B.3Testlaboratory.20B.4Client(ofthetestlaboratory).21B.5SystemUnderTest(SUT).21B.6Protocolinformation.22B.6.1Protocolidentification.22B.6.2IUTinformation.22B.6.2.1Parametervalues.22B.6.2.2ConfigurationofIUT.23B.6.2.3Timervalues.23B.7BasiccallPIXITitems.24B.7.1Parametervalues-informationelementcodings.24AnnexC(normative):AbstractTestSuite(ATS).26C.1TheTTCNGraphicalform(TTCN.GR).26C.2TheTTCNMachineProcessableform(TTCN.MP).26AnnexD(informative):GeneralstructureofATS.27History.28SIST EN 301 144-4 V1.1.4:2005

ETSIETSIEN301144-4V1.1.4(2000-05)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)hasbeenproducedbyETSITechnicalCommitteeServicesandProtocolsforAdvancedNetworks(SPAN).Thepresentdocumentispart4ofamulti-partENcoveringtheIntegratedServicesDigitalNetwork(ISDN)DigitalSubscriberSignallingSystemNo.one(DSS1)andSignallingSystemNo.7(SS7)protocols;Signallingapplicationforthemobilitymanagementserviceonthealphainterfaceasidentifiedbelow: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:5May2000DateoflatestannouncementofthisEN(doa):31August2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):28February2001DateofwithdrawalofanyconflictingNationalStandard(dow):28February2001SIST EN 301 144-4 V1.1.4:2005

ETSIETSIEN301144-4V1.1.4(2000-05)61ScopeThepresentdocumentspecifiestheAbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformafortheuseroftheSignallingapplicationforthemobilitymanagementserviceonthealphainterface.Itisapplicabletoalltypesofexchangesasdefinedinthereferencespecification.EN301144-3[7]specifiestheTestSuiteStructureandTestPurposes(TSS&TP)relatedtothisprotocol.OtherpartsspecifytheTSS&TPandtheATSandpartialPIXITproformafortheNetworksideforimplementationsconformingtoEN301144-1[1].2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIEN301144-1(V1.1):"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)andSignallingSystemNo.7(SS7);Signallingapplicationforthemobilitymanagementserviceonthealphainterface;Part1:Protocolspecification".[2]ETSIEN300196-1(V1.2):"IntegratedServicesDigitalNetwork(ISDN);Genericfunctionalprotocolforthesupportofsupplementaryservices;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part1:Protocolspecification".[3]ISO/IEC9646:"Informationtechnology-OpenSystemsInterconnection-ConformanceTestingMethodologyandFramework"(allparts).[4]ETSITR101101(V1.1):"MethodsforTestingandSpecification(MTS);TTCNinterimversionincludingASN.11994support[ISO/IEC9646-3](SecondEditionMock-upforJTC1/SC21Review)".[5]ISO/IEC9646-2:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part2:Abstracttestsuitespecification".[6]ETSIETS300175-5:"DigitalEnhancedCordlessTelecommunications(DECT);CommonInterface(CI);Part5:Network(NWK)layer".[7]ETSIEN301144-3:"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)andSignallingSystemNo.7protocols;Signallingapplicationforthemobilitymanagementserviceonthealphainterface;Part3:TestSuiteStructureandTestPurposes(TSS&TP)specificationfortheuser".[8]ISO/IEC9646-3/AM2:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part3:TheTreeandTabularCombinedNotation(TTCN)".[9]ISO/IEC8825-1:"Informationtechnology-EncodingRulesforAbstractSyntaxNotationOne(ASN.1)-Part1:SpecificationofBasicEncodingRules(BER),CanonicalEncodingRules(CER)andDistinguishedEncodingRules(DER)"(SeealsoITU-TRecommendationX.690:1994.)".[10]ISO/IEC9646-5:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part5:Requirementsontestlaboratoriesandclientsfortheconformanceassessmentprocess".SIST EN 301 144-4 V1.1.4:2005

ETSIETSIEN301144-4V1.1.4(2000-05)7[11]ISO/IEC9646-4:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part4:Testrealization".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thetermsanddefinitionsgiveninISO/IEC9646[3]apply.3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ASPAbstractServicePrimitiveATMAbstractTestMethodATSAbstractTestSuiteBERBasicEncodingRulesIUTImplementationUnderTestLTLowerTesterMOTMeansOfTestingPCOPointofControlandObservationPDUProtocolDataUnitPICSProtocolImplementationConformanceStatementPIXITProtocolImplementationeXtraInformationforTestingSUTSystemUnderTestTPTestPurposeTTCNTreeandTabularCombinedNotationUTUpperTester4AbstractTestMethod(ATM)TheremotetestmethodisappliedforthisuserAbstractTestSuite(ATS).APointofControlandObservation(PCO)residesattheserviceaccesspointbetweenlayers2and3inthetestsystem.ThisPCOisnamed"L"(forLower).TheLPCOisusedtocontrolandobservethebehaviouroftheImplementationUnderTest(IUT)andtestcaseverdictsareassigneddependingonthebehaviourobservedatthisPCO.SIST EN 301 144-4 V1.1.4:2005

ETSIETSIEN301144-4V1.1.4(2000-05)8Asecond"informal"PCO,called"O"(forOperator)isusedtospecifycontrolbutnotobservationabovetheIUT;eventsatthisPCOareneverusedtogeneratetestcaseverdicts.MessagessentbythetesteratthisPCOexplicitlyindicatetotheoperatoractionswhicharetobeperformedontheSystemUnderTest(SUT).Thisisregardedasapreferredalternativetotheuseoftheimplicitsendevent.TesterInformaltestco-ordinationbyoperatorSUTUpperlayer(s)PCOOLTIUTPCOLLayer2Layer2Layer1Layer1ServiceproviderFigure1:RemotetestmethodwithPCOOfortestco-ordination5UntestabletestpurposesTherearenountestabletestpurposesassociatedwiththisATS.6ATSconventions6.1VersionofTTCNusedTheversionofTTCNusedisthatdefinedinTR101101[4].6.2Namingconventions6.2.1DeclarationspartSubclause6.2.1describesthenamingconventionschosenfortheelementsoftheATSdeclarationspart.6.2.1.1TestsuitetypeandstructuredtypedefinitionsThetestsuitetypeandtestsuitestructuredtypeidentifiersarewritteninlowercasestartingbyanuppercaseletterorcompletelyinuppercaseletters.6.2.1.2TestsuiteoperationsdefinitionsThetestsuiteoperationidentifiersarecomposedofstringsinuppercaseandlowercaselettersstartingbythestring"TSO_".EXAMPLE:TSO_CalcFieLength6.2.1.3TestsuiteparameterdeclarationsThetestsuiteparameteridentifiersarecomposedofstringsinuppercaseandlowercaselettersstartingbytheuppercasestring"PC_"foraPICSor"PX_"foraPIXIT.SIST EN 301 144-4 V1.1.4:2005

ETSIETSIEN301144-4V1.1.4(2000-05)96.2.1.4TestcaseselectionexpressiondefinitionsThenamingconventionsforthetestcaseselectionexpressiondefinitionsusefreetextstartingwiththestring:"TCSE_".Thenameoftheexpressionshallexplainclearlytheselectionrule.Thetestcaseselectionexpressionsaregenerallylogicalcombinationsofthetestsuiteparameterdefinitions.6.2.1.5TestsuiteconstantdeclarationsThetestsuiteconstantidentifiersarecomposedofstringsinuppercaseandlowerlettersstartingbytheuppercasestring"TSC_".6.2.1.6TestsuitevariabledeclarationsThetestsuitevariableidentifiersarecomposedofstringinlowercaselettersstartingbythelowercasestring"tsv_".6.2.1.7TestcasevariabledeclarationsThetestcasevariableidentifiersarecomposedofstringsinlowercaselettersstartingbythelowercasestring"tcv_".6.2.1.8PCOdeclarationsThepointofcontrolandobservationidentifiersarecomposedofthreetosixcapitalletters,beginningwithan"L",asthereareonlyLTs.6.2.1.9TimerdeclarationsThetimernamesbeginwiththeprefix"T_",followedbyastringinlowercaseoruppercaseletterswitheachwordinthefollowingstringstartingwithanuppercaseletter.6.2.1.10ASPtypedefinitionsTheASPtypesweredefinedinuppercaseletters.6.2.1.11PDUtypedefinitionsThetypeofaProtocolDataUnit(PDU)isgiveninuppercaseletters.6.2.2ConstraintspartSubclause6.2.2describesthenamingconventionschosenfortheelementsoftheATSconstraintspart.6.2.2.1StructuredtypeconstraintStructuredTypeconstraintidentifierbeginwithanuppercaseletterfollowedbyuppercaseandlowercaseletters.Themeaningoftheidentifierrepresentthecontentsofthestructuredtypeconstraint.6.2.2.2PDUconstraintConstraintidentifierbeginwiththetypeofthePDUwritteninuppercase.Theremainingpartofthenameisseparatedfromthebeginningwithanunderscoreandiswritteninlowercasewitheachwordstartingwithanuppercaseletter.Theprefix_Sor_Rshallbeaddedattheendoftheidentifiertoindicateiftheconstraintissentorreceivedbythetester.SIST EN 301 144-4 V1.1.4:2005

ETSIETSIEN301144-4V1.1.4(2000-05)106.2.3DynamicpartSubclause6.2.3describesthenamingconventionschosenfortheelementsoftheATSdynamicpart.6.2.3.1TeststepidentifierTheteststepidentifierisbuiltwithastringoflowercaselettersleadedbyastringofcapitalletterandjoinedbyanunderscorecharacter.Thefirststringindicatesthemainfunctionoftheteststep;e.g.PREforpreamble,PSTforpostambleandSTPforanormalstep.Thesecondstringindicatesthemeaningofthestep.EXAMPLES:PRE_Name;PST_Name;STP_Name.6.3UseofASN.16.3.1SituationswhereASN.1isusedASN.1hasbeenusedforthreemajorreasons.First,typesdefinedinASN.1canmodelproblemsthat"pure"TTCNcannot.Forinstance,datastructuresmodellingorderedorunorderedsequencesofdataarepreferablydefinedinASN.1.Second,ASN.1providesabetterrestrictionmechanismfortypedefinitionsbyusingsub-typedefinitions.Third,itisnecessarytouseASN.1toreproducethetypedefinitionsforremoteoperationcomponentsspecifiedinthebasestandardsinASN.1.ThepossibilitytouseTTCNandASN.1incombinationisused,i.e.referringtoanASN.1typefromaTTCNtype.6.3.2SpecificationofencodingrulesThereisavariationintheencodingrulesappliedtoASN.1typesandconstraintsspecifiedinthisATSandthereforeamechanismisneededtodifferentiatetheencodingrules.HoweverthemechanismspecifiedinISO/IEC9646-3[8]/AM2andinTR101101[4]doesnotfacilitatedefinitionoftheencodingrulesasneededforthisATS.AsolutionisthereforeusedwhichisbroadlyinthespiritofISO/IEC9646-3[8]/AM2inwhichcommentfieldshavebeenusedasameansofencodingrules.ForASN.1usedinthisATS,twovariationsofencodingrulesareused.OneisthecommonlyknownBasicEncodingRules(BER)asspecifiedinISO/IEC8825-1[9],thesecondoneistheencodingthatcorrespondtothespecification,i.e.theASN.1datatypesarearepresentationofstructurescontainedwithinthespecification.Forexample,ifoctetsofaninformationelementarespecifiedinASN.1asaSEQUENCEthenthisshouldbeencodedinanExecutableTestSuite(ETS)asanyotherinformationelementspecifiedusingtabularTTCN.ThisencodingvariationisthedefaultencodingruleforthisATS.ThismeansthatallASN.1constrainttablesareencodedusingthissecond(non-BER)encodingunlessstatedotherwise.BERencodingshallnotbeappliedtoanASN.1constraintwhereBERencodinghasnotbeenspecified.Thisencodingruleissometimesnamed"DirectEncoding".ForBERencoding,anindicationisgiveninthecommentsfieldofthetableheaderandintheencodingvariationfield.NotethatwithinBER,thereareanumberofvariationsfortheencodingoflengthsoffields.AccordingtoEN300196-1[2],anIUTshouldbeabletointerpretalllengthformswithinBERforreceivedPDUs.WhensendingPDUscontainingBERencoding,EN300196-1[2]givesguidelinesbutmakesnorestrictionsonthelengthformswithinBERwhichanIUTmayapply.InthisparticularATSallASN.1typeconstraintswhichareoftype"Component"aretobeencodedusingBER.SIST EN 301 144-4 V1.1.4:2005

ETSIETSIEN301144-4V1.1.4(2000-05)117ATStoTPmappingTheidentifiersusedfortheTPs(seeEN301144-3[7])arereusedastestcasenames.Thusthereisastraightforwardone-to-onemapping.8PCTRconformanceAtestlaboratory,whenrequestedbyaclienttoproduceaPCTR,isrequired,asspecifiedinISO/IEC9646-5[10],toproduceaPCTRconformancewiththePCTRtemplategiveninannexBofISO/IEC9646-5[10].Furthermore,atestlaboratory,offeringtestingforeitherATSspecificationcontainedinannexC,whenrequestedbyaclienttoproduceaPCTR,isrequiredtoproduceaPCTRconformancewiththePCTRproformacontainedinannexA.APCTRwhichconformstothisPCTRproformaspecificationshallpreservethecontentandorderingoftheclausescontainedinannexA.ClauseA.6ofthePCTRmaycontainadditionalcolumns.Ifincluded,theseshallbeplacedtotherightoftheexistingcolumns.Textinitalicsmayberetainedbythetestlaboratory.9PIXITconformanceAtestrealizer,producinganexecutabletestsuiteforATSspecificationcontainedinannexC,isrequired,asspecifiedinISO/IEC9646-4[11],toproduceanaugmentedpartialPIXITproformaconformantwiththispartialPIXITproformaspecification.AnaugmentedpartialPIXITproformawhichconformstothispartialPIXITproformaspecificationshall,asaminimum,havecontentswhicharetechnicallyequivalenttoannexB.TheaugmentedpartialPIXITproformamaycontainadditionalquestionsthatneedtobeansweredinordertopreparetheMeansOfTesting(MOT)foraparticularIUT.Atestlaboratory,offeringtestingforeitherATSspecificationcontainedinannexC,isrequired,asspecifiedinISO/IEC9646-5[10],tofurtheraugmenttheaugmentedpartialPIXITproformatoproduceaPIXITproformaconformantwiththispartialPIXITproformaspecification.APIXITproformawhichconformstothispartialPIXITproformaspecificationshall,asaminimum,havecontentswhicharetechnicallyequivalenttoannexB.ThePIXITproformamaycontainadditionalquestionsthatneedtobeansweredinordertopreparethetestlaboratoryforaparticularIUT.10ATSconformanceThetestrealizer,producingMOTandexecutabletestsuiteforthisATSspecification,shallcomplywiththerequirementsofISO/IEC9646-4[11].Inparticular,theseconcerntherealizationofanexecutabletestsuitebasedtothisATSspecification.ThetestrealizershallprovideastatementofconformanceoftheMOTtothisATSspecification.AnexecutabletestsuitewhichconformstothisATSspecificationshallcontaintestgroupsandtestcaseswhicharetechnicallyequivalenttothosecontainedinattheATSinannexC.Allsequencesoftesteventscomprisinganabstracttestcaseshallbecapableofbeingrealizedintheexecutabletestcase.AnyfurthercheckingwhichthetestsystemmightbecapableofperformingisoutsidethescopeofthisATSspecificationandshallnotcontributetotheverdictassignmentforeachtestcase.Tes
...