SIST EN 300 805-2 V1.2.1:2005

• Abstract:

  Update of ETS 300 805-2 in order to align with the IS version.

• Status: Published
• Publication Date: 28-Feb-2005
• ICS: 33.040.35 - Telephone networks
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Mar-2005
• Due Date: 01-Mar-2005
• Completion Date: 01-Mar-2005
• Mandate: IT-74
• Mandate: T-245
• Ref Project: ETSI EN 300 805-2 V1.2.1 (2000-05) - Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Circuit mode basic services; Network Layer (NL); Part 2: Abstract Test Suite (ATS) specification

SIST EN 300 805-2 V1.2.1:2005 is the SIST adoption of an ETSI European Standard for testing the Network Layer of PISN inter-exchange signalling for circuit mode basic services. It specifies an Abstract Test Suite (ATS) for conformance testing of implementations such as PINX roles over Basic Rate or Primary Rate access on leased lines, using the ISO/IEC 9646 test methodology.

What does SIST EN 300 805-2 V1.2.1:2005 specify?

SIST EN 300 805-2 V1.2.1:2005 specifies the ATS for the Network Layer of circuit mode basic services in PISN. Its purpose is to support conformance tests that give a high probability of interoperability for the Network Layer.

The document applies to implementations with Basic Rate access, Primary Rate access, or both, and to Originating, Terminating, Transit, Incoming Gateway and Outgoing Gateway PINX roles. It focuses on the procedures in EN 300 172 and the parts of EN 301 048 related to the transit counter in Basic Call procedures.

Annex	What it covers
Annex A	Partial PIXIT proforma
Annex B	PCTR proforma for PSS1_BC Layer
Annex C	ATS in TTCN form
Annex D	Compatibility guidance
Annex E	Summary of changes from the previous edition

What are the key requirements of SIST EN 300 805-2 V1.2.1:2005?

The ATS is organized around the way the protocol is tested, the roles being tested, and the way test cases are selected and reported. In practice, this tells a test lab how to configure the IUT, which test method to use, and which test purposes can be executed.

Abstract test method and test configuration

Clause 4 uses two Abstract Test Methods: the Remote single layer test method and the Multi-Party test method. Single-PCO testing is used for Segmentation, Protocol Discriminator Filter, Protocol Control, and Call Control for non-Transit PINX; multiple-PCO testing is used for Transit PINX Call Control. This matters because the tester must either control one interface or two interfaces at the same time.

Clause 4 also defines two configurations: mono and transit. Mono uses one MTC and one PCO, while transit uses one MTC and two PTCs with two coordination points. This is the practical setup a test engineer must build.

Test purposes and coverage limits

Clause 5 lists test purposes that are untestable in this ATS and therefore not derived into test cases. This helps implementers and labs understand where the suite has deliberate coverage limits and avoid expecting those cases in execution plans.

Conformance of reports, PIXIT and ATS execution

Clause 6 requires PCTR conformance to ISO/IEC 9646-5 and to the PCTR proforma in Annex B. It also requires a conformant PIXIT proforma to be based on Annex A, and a conformant ATS realization to follow ISO/IEC 9646-4. For a lab, this means the test report and test setup information have fixed structures.

Clause 6 also states that test cases for information channel selection are repeated with the IUT configured as A-side and B-side, and, if supported, with Channel map. The test suite parameter IUT_A identifies which side is used in each run.

Naming, parameters and TTCN conventions

Clause 7 defines the naming rules for PDUs, ASPs, IEs, test components, PCOs, coordination points, parameters, timers, constraints and test steps. This matters because the ATS uses these identifiers consistently in the TTCN suite and in the proformas, so implementers can map test artifacts unambiguously.

Clause 7.9 also fixes bit and octet order conventions for TTCN use of QSIG PDUs. That is important when comparing encoded values during test realization.

Mapping between test cases and purposes

Clause 8 states that there is a one-to-one mapping between the test cases and the final derived test purposes in EN 300 805-1, with the same identifiers. This makes it easier to cross-reference the ATS with the structure and intent of the companion part.

What terms does SIST EN 300 805-2 V1.2.1:2005 define?

• Abstract Test Suite (ATS) - the set of abstract test cases and related information used to assess conformance.
• Implementation Under Test (IUT) - the implementation being tested.
• Point of Control and Observation (PCO) - the boundary where the tester controls and observes protocol behavior.
• Protocol Implementation Conformance Statement (PICS) - the statement that records which protocol features an implementation supports.
• Protocol Implementation eXtra Information for Testing (PIXIT) - extra implementation-specific information needed to prepare testing.
• Protocol Conformance Test Report (PCTR) - the structured report used to record conformance test results.
• Signalling Carriage Mechanism (SCM) - the mechanism used for carrying signalling, named in the protocol definitions.
• Private Integrated ServiceseXchange (PINX) - a private exchange in a Private Integrated Services Network.

Who uses SIST EN 300 805-2 V1.2.1:2005?

SIST EN 300 805-2 V1.2.1:2005 is used by test laboratories, test realizers, equipment vendors and conformance engineers working on PISN inter-exchange signalling. It is also relevant to quality managers and buyers who need evidence that a network product can be tested against the Network Layer requirements for specific PINX roles and access types.

In practice, it supports preparing PIXIT data, selecting applicable test cases, building executable test suites, and producing PCTR documents for certification or acceptance testing.

What changed in SIST EN 300 805-2 V1.2.1:2005 from the previous edition?

This document updates ETS 300 805-2 to align with the IS version. Annex E says the changes include a simplified test suite structure and revised test case identifiers, broader support for multirate behavior, conversion of many test suite operations to procedural notation, some reductions in duplicate test purposes, and changes to test suite parameters and test case selection.

Which standards are used with SIST EN 300 805-2 V1.2.1:2005?

Reference	What it contributes
EN 300 805-1	Test Suite Structure and Test Purposes for the same Network Layer
EN 300 172	Base specification for circuit mode basic services procedures
EN 301 048	Transit counter additional network feature
ISO/IEC 9646-1 to -5	Conformance testing concepts, ATS specification, TTCN, test realization, and laboratory/client requirements
ISO/IEC 11572	Earlier base standard for circuit mode bearer services procedures
ISO/IEC 15056	Earlier transit counter additional network feature standard
ETSI TR 101 101	TTCN version used by the ATS

What does the SIST EN 300 805-2 V1.2.1:2005 document contain?

Annex A and Annex B are proformas filled in during testing: one for PIXIT information and one for the PCTR report. Annex C contains the ATS itself in TTCN.GR and TTCN.MP forms, so it is the executable testing core of the document.

The body of the standard includes the abstract test method, the conformance rules, the naming conventions, and the mapping between test cases and test purposes. Annex D adds compatibility notes for other protocol specifications and connection scenarios, while Annex E summarizes edition changes for implementers.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Zasebno omrežje z integriranimi storitvami (PISN) - Medcentralni signalizacijski protokol - Vodovna osnovna storitev - Omrežna plast (NL) - 2. del: Abstraktni preskušalni niz (ATS) - SpecifikacijaPrivate Integrated Services Network (PISN); Inter-exchange signalling protocol; Circuit mode basic services; Network Layer (NL); Part 2: Abstract Test Suite (ATS) specification33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 300 805-2 Version 1.2.1SIST EN 300 805-2 V1.2.1:2005en01-marec-2005SIST EN 300 805-2 V1.2.1:2005SLOVENSKI
STANDARD
ETSIEN300805-2V1.2.1(2000-05)EuropeanStandard(Telecommunicationsseries)PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Circuitmodebasicservices;NetworkLayer(NL);Part2:AbstractTestSuite(ATS)specificationSIST EN 300 805-2 V1.2.1:2005

ETSIETSIEN300805-2V1.2.1(2000-05)2ReferenceREN/ECMA-00159-2KeywordsATS,circuitmode,layer3,PINX,PISN,QSIG,testingETSI650RoutedesLuciolesF-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 300 805-2 V1.2.1:2005

ETSIETSIEN300805-2V1.2.1(2000-05)3ContentsIntellectualPropertyRights.6Foreword.61Scope.72References.73Definitionsandabbreviations.83.1Definitions.83.2Abbreviations.94AbstractTestMethod(ATM).104.1ChoiceoftheATM.104.1.1Functionalsubsets.104.1.2Single-andMulti-partytesting.104.2SinglePCOtesting.114.2.1CallControltestingfornon-TransitPINXandProtocolControltesting.114.2.2SegmentationandProtocolDiscriminatorFiltertesting.124.3MultiplePCOtesting.124.3.1CallControltestingforaTransitPINX.124.4TestConfigurationsanduseofConcurrentTTCN.135UntestableTestPurposes.146Conformance.156.1PCTRconformance.156.2PIXITconformance.156.3ATSconformance.157ATSConventions.167.1Shortnamesandabbreviations.167.2Testsuitetype,ASPtype,PDUtypeandAliasidentifiers.177.2.1ASPtypeidentifiers.177.2.2PDUtypeidentifiers.177.2.3TestSuiteTypeidentifiers(InformationElements).177.2.4Aliases.187.3Identifiersconcerningtestconfiguration.187.3.1Testcomponents.187.3.2Testcomponentconfigurations.187.3.3PointsofControlandObservations(PCOs).187.3.4Co-ordinationPoints(CPs).187.3.5CMtypes.187.4TestSuiteParameterandSelectionExpressionidentifiers.197.4.1Testsuiteparameters.197.4.2PICSParameters.197.4.3PIXITparameters.197.4.4TestCaseSelectionExpressions.197.4.5AbbreviationsusedinPIXITparametersandTestCaseSelectionExpressions.207.5Miscellaneousidentifiers.217.5.1Testsuiteoperations.217.5.2Testsuiteconstants.217.5.3Testsuitevariables.217.5.4Testcasevariables.217.5.5Timers.217.6Constraints.227.6.1TTCNTestsuitetypeconstraints.227.6.2ASPconstraints.227.6.3PDUconstraints.227.6.4CMconstraints.22SIST EN 300 805-2 V1.2.1:2005

ETSIETSIEN300805-2V1.2.1(2000-05)47.7Dynamicpart.227.7.1TestCaseidentifiers.227.7.2TestStepidentifier.237.7.3Defaultidentifier.237.8Notation.237.9Bitandoctetorder.248Testcaseandtestpurposemapping.24AnnexA(normative):PartialPIXITproforma.25A.1Identificationsummary.25A.2ATSsummary.25A.3Testlaboratory.25A.4Clientidentification.25A.5SUT.26A.6Protocollayerinformation.26A.6.1Protocolidentification.26A.6.2IUTinformation.26A.6.2.1Generalinformation.26A.6.2.1.1GeneralConfiguration.26A.6.2.1.2Addressing.27A.6.2.2ClearingProcedures.28A.6.2.3GeneralSendingofMessages.28A.6.2.4OriginatingPINX.30A.6.2.5TerminatingPINX.30A.6.2.6IncomingGatewayPINX.31A.6.2.7OutgoingGatewayPINX.32A.6.2.8TransitPINX.32A.6.2.9StatusProcedure.33A.6.2.10LayerManagement.33A.6.2.11ErrorHandling.33A.6.2.12Segmentation.34A.6.2.13Timers.34A.6.3CalledPartyNumbersinthePIXIT.34AnnexB(normative):ProtocolConformanceTestReport(PCTR)ProformaforPSS1_BCLayer.36B.1Identificationsummary.36B.1.1Protocolconformancetestreport.36B.1.2IUTidentification.36B.1.3Testingenvironment.37B.1.4Limitsandreservation.37B.1.5Comments.37SIST EN 300 805-2 V1.2.1:2005

ETSIETSIEN300805-2V1.2.1(2000-05)5B.2IUTConformancestatus.38B.3Staticconformancesummary.38B.4Dynamicconformancesummary.38B.5Staticconformancereviewreport.38B.6Testcampaignreport.39B.7Observations.46AnnexC(normative):AbstractTestSuite(ATS)forPSS1_BC.47C.1TheTTCNGraphicalform(TTCN.GR).47C.2TheTTCNMachineProcessableform(TTCN.MP).47AnnexD(informative):Compatibility.48D.1OtherPSS1protocolspecifications.48D.2Otherconnectionscenarios.50D.2.1Numberofchannels.50D.2.2Codingofinformationelements.50AnnexE(informative):Summaryofchangesfrompreviousedition.51E.1Introduction.51E.2TestSuiteStructureandTestCaseidentifierchanges.51E.3Supportformultirate.51E.4TestSuiteOperationandtypechanges.51E.5ReviewofderivationofTPs.52E.6Testsuiteparametersandtestcaseselection.52Bibliography.53History.54SIST EN 300 805-2 V1.2.1:2005

ETSIETSIEN300805-2V1.2.1(2000-05)6IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.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)hasbeenproducedbyEuropeanComputerManufacturersAssociation(ECMA)onbehalfofitsmembersandthoseoftheEuropeanTelecommunicationsStandardsInstitute(ETSI).Thepresentdocumentispart2ofamulti-partENcoveringthePrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Circuitmodebasicservices;NetworkLayer(NL),asidentifiedbelow:Part1:"TestSuiteStructureandTestPurposes(TSS&TP)specification";Part2:"AbstractTestSuite(ATS)specification".NationaltranspositiondatesDateofadoptionofthisEN:28April2000DateoflatestannouncementofthisEN(doa):31July2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31January2001DateofwithdrawalofanyconflictingNationalStandard(dow):31January2001SIST EN 300 805-2 V1.2.1:2005

ETSIETSIEN300805-2V1.2.1(2000-05)71ScopeThepresentdocumentspecifiestheAbstractTestSuite(ATS)fortheNetworkLayer,CircuitModeBasicServicesoftheInter-exchangesignallingprotocol,forPrivateIntegratedServicesNetworks(PISN).Theobjectiveofthepresentdocumentistoprovideconformancetestswhichgiveahighprobabilityofinter-operabilityoftheNetworkLayer.ThepresentdocumentcoverstheproceduresdescribedinEN300172[3]andthosepartsofEN301048[6]whichrelatetotheuseofthetransitcounterinconnectionwithBasicCallprocedures.NOTE1:ThepartsofEN301048[6]includedarethosewhichareequivalenttoETS300172[4]annexZB.NOTE2:TheATSinthepresentdocumentcanalsobeusedfortestingequipmentimplementedaccordingtocertainotherPSS1specifications.TheISOstandardforthemethodologyofconformancetesting(ISO/IEC9646-1[7],ISO/IEC9646-2[8]andISO/IEC9646-3[9])isusedasbasisforthetestmethodology.ThepresentdocumentisapplicabletoimplementationswhichsupporteitheraBasicRateoraPrimaryRateaccessinterface,orboth,operatingoveraleasedline.ItisapplicabletovariousPINXroles,i.e.Originating,Terminating,Transit,Incoming/OutgoingGateway.NOTE3:Thepresentdocumentcanalsobeapplicabletootherscenariosifthescenarioconcerneddoesnotrelyonextensionstotheprotocolforbasiccalldefinedinthemappingspecification(e.g.theuseofNationalStandardcodepointsintheBearerCapabilityIE)orsupportmorethan30informationchannels.Forscenarioswhichdonotsatisfytheseconditionssometestcasescanbeunsuitableand/orrequiremodifications.AnnexAprovidesthePartialProtocolImplementationeXtraInformationforTesting(PIXIT)Proformaofthisspecification.AnnexBprovidestheProtocolConformanceTestReport(PCTR)Proformaofthisspecification.AnnexCprovidestheTreeandTabularCombinedNotation(TTCN)partofthisspecification.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,subsequentrevisionsdoapply.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ECMA-143(1997):"PrivateIntegratedServicesNetwork(PISN)-CircuitModeBearerServices-Inter-ExchangeSignallingProceduresandProtocol(QSIG-BC)".[2]ECMA-225(1997):"PrivateIntegratedServicesNetwork(PISN)-Inter-ExchangeSignallingProtocol-TransitCounterAdditionalNetworkFeature(QSIG-TC)".[3]ETSIEN300172(V1.4):"PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Circuit-modebasicservices[ISO/IEC11572(1996)modified]".[4]ETSIETS300172:"PrivateTelecommunicationNetwork(PTN);Inter-exchangesignallingprotocol;Circuitmodebasicservices".SIST EN 300 805-2 V1.2.1:2005

ETSIETSIEN300805-2V1.2.1(2000-05)8[5]ETSIEN300805-1(V1.2):"PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Circuitmodebasicservices;NetworkLayer(NL);Part1:TestSuiteStructureandTestPurposes(TSS&TP)specification".[6]ETSIEN301048(V1.1):"PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Transitcounteradditionalnetworkfeature[ISO/IEC15056(1997)modified]".[7]ISO/IEC9646-1(1994):"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[8]ISO/IEC9646-2(1994):"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part2:AbstractTestSuitespecification".[9]ISO/IEC9646-3(1998):"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part3:TheTreeandTabularCombinedNotation(TTCN)".[10]ISO/IEC9646-4(1994):"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part4:Testrealization".[11]ISO/IEC9646-5(1994):"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part5:Requirementsontestlaboratoriesandclientsfortheconformanceassessmentprocess".[12]ISO/IEC11572(1997):"Informationtechnology-Telecommunicationsandinformationexchangebetweensystems-PrivateIntegratedServicesNetwork-Circuitmodebearerservices-Inter-exchangesignallingproceduresandprotocol".[13]ISO/IEC15056(1997):"Informationtechnology-Telecommunicationsandinformationexchangebetweensystems-PrivateIntegratedServicesNetwork-Inter-exchangesignallingprotocol-Transitcounteradditionalnetworkfeature".[14]ETSITR101101(V1.1):"MethodsforTestingandSpecification(MTS);TTCNinterimversionincludingASN.11994support[ISO/IEC9646-3](SecondEditionMock-upforJTC1/SC21Review)".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:AbstractTestSuite(ATS):seeISO/IEC9646-1[7].finaltestpurpose:seeEN300805-1[5].ImplementationUnderTest(IUT):seeISO/IEC9646-1[7].incomingcall:seeEN300172[3].incominggatewayPINX:seeEN300172[3].LowerTester(LT):seeISO/IEC9646-1[7].networklayer:forthepurposesofthisATStheproceduresdescribedinEN300172[3].originatingPINX:seeEN300172[3].outgoingcall:seeEN300172[3].outgoinggatewayPINX:seeEN300172[3].PICSproforma:seeISO/IEC9646-1[7].SIST EN 300 805-2 V1.2.1:2005

ETSIETSIEN300805-2V1.2.1(2000-05)9PIXITproforma:seeISO/IEC9646-1[7].PointOfControlAndObservation(PCO):seeISO/IEC9646-1[7].precedingPINX:seeEN300172[3].ProtocolImplementationConformanceStatement(PICS):seeISO/IEC9646-1[7].ProtocolImplementationExtraInformationForTesting(PIXIT):seeISO/IEC9646-1[7].segmentation:seeEN300805-1[5].SignallingCarriageMechanism(SCM):seeEN300172[3].subsequentPINX:seeEN300172[3].supertestpurpose:seeEN300805-1[5].SystemUnderTest(SUT):seeISO/IEC9646-1[7].terminatingPINX:seeEN300172[3].transitPINX:seeEN300172[3].UpperTester(UT):seeISO/IEC9646-1[7].3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ANF-TCTransitCounterAdditionalNetworkFeatureASPAbstractServicePrimitiveATMAbstractTestMethodATSAbstractTestSuiteCMCo-ordinationMessageCPCo-ordinationPointIEInformationElementISOInternationalOrganizationforStandardizationIUTImplementationUnderTestLTLowerTesterMOTMeanOfTestingMSBMostSignificantBitMTCMasterTestComponentPCOPointofControlandObservationPCTRProtocolConformanceTestReportPDUProtocolDataUnitPICSProtocolImplementationConformanceStatementPINXPrivateIntegratedServiceseXchangePISNPrivateIntegratedServicesNetworkPIXITProtocolImplementationeXtraInformationforTestingPSS1orQSIGPrivateIntegratedSignallingSystemNumber1PTCParallelTestComponentSCMSignallingCarriageMechanismSUTSystemUnderTestTCTestCaseTPTestPurposeTSOTestSuiteOperationTTCNTreeandTabularCombinedNotationUTUpperTesterSIST EN 300 805-2 V1.2.1:2005

ETSIETSIEN300805-2V1.2.1(2000-05)104AbstractTestMethod(ATM)ThisclausedescribesthedifferentAbstractTestMethods(ATM)usedfortestingtheNetworkLayerprotocol.Twomethodsareapplied:theRemotesinglelayertestmethod,andtheMulti-Partytestmethod.4.1ChoiceoftheATM4.1.1FunctionalsubsetsThechoiceoffunctionalsubsetsisbasedprimarilyonthefactthatPSS1issubdividedintotwofunctionalentities:-CallControl;-ProtocolControl.EachofthesetwofunctionalentitiesistestedusingdifferentsetsofTestPurposesandhencedifferentTestCases.TheProtocolControlentityisfurtherdividedintothreesublayers:-theProtocolDiscriminatorFiltersublayer;-theMessageSegmentationsublayer;-theOtherProtocolControlFunctionssublayer.FromtheviewpointofthisATS,PSS1isconsideredtobedividedintotwofunctionalsubsets,asshowninfigure1.ThefirstofthesefunctionalgroupsconsistsoftheProtocolDiscriminatorFiltersublayerandtheMessageSegmentationsublayer.ThesecondfunctionalgroupconsistsoftheOtherProtocolControlFunctionssublayerandtheCallControlentity.AdifferentPCOisusedforeachofthesefunctionalgroupswhenbeingtested.SegmentationCallControlOtherProtocolP.D.FilterLayer2Layer12ndgroup1stgroupControlFunctionsCallControlProtocolControlPSS1SCMNOTE:Intheremainderofclause4,theterm"ProtocolControl"refersonlytothe"OtherProtocolControlFunctions"sublayer.Figure1:PSS1functionalsubsets4.1.2Single-andMulti-partytestingForCallControl,theprotocoldefinesdifferentrolesthataPINXcanplay:itcanbeanendorgatewayPINX(Originating,Terminating,IncomingGateway,OutgoingGateway),oraTransitPINX.Inthefirstcase,onlyoneinterfaceneedstobetested,andinthesecondcase,twointerfacesneedtobetestedsimultaneously.SIST EN 300 805-2 V1.2.1:2005

ETSIETSIEN300805-2V1.2.1(2000-05)114.2SinglePCOtestingSinglePCOtestingappliestotheSegmentationandProtocolDiscriminatorFilter,totheProtocolControl,andtotheCallControlforanOriginating,Terminating,IncomingGatewayorOutgoingGatewayPINX.4.2.1CallControltestingfornon-TransitPINXandProtocolControltestingAsshowninfigure2,theIUTistheProtocolControlandCallControlpart,anditisanend-system.ItisnotpossibletoobserveandcontroltheupperserviceboundaryoftheIUT.Consequently,thetestmethodchosenistheRemoteTestMethod,wheretheco-ordinationproceduresareexpressedinaninformalway.ThetestsystemwillonlycontainoneLTandnoUT.ThePCO,calledLX,islocatedbetweentheProtocolControlandCallControlpart,andtheSegmentationpart.OnlyunsegmentedProtocolDataUnits(PDUs)areexchanged.TESTSYSTEMSUTPCO:LXSCMPSS1LTCallControlandProtocolControlSegmentationP.D.FilterPDUsSegmentationP.D.FilterUnsegmentedCallControlandProtocolControlIUTFigure2:RemotesinglelayertestmethodforProtocolControlandCallControlfornon-TransitPINXSIST EN 300 805-2 V1.2.1:2005

ETSIETSIEN300805-2V1.2.1(2000-05)124.2.2SegmentationandProtocolDiscriminatorFiltertestingAsshowninfigure3,theIUTistheSegmentationandProtocolDiscriminatorFilterpart,anditisanend-system.ItisnotpossibletoobserveandcontroltheupperserviceboundaryoftheIUT.Consequently,thetestmethodchosenistheRemoteTestMethod,wheretheco-ordinationproceduresareexpressedinaninformalway.ThetestsystemwillonlycontainoneLTandnoUT.ThePCO,calledLSEG,islocatedbetweentheSegmentationandProtocolDiscriminatorFilterpart,andtheSCM.ThePDUsexchangedareSEGMENTPDUsandunsegmentedPDUs.TESTSYSTEMSUTPCO:LSEGSCMLTCallControlandProtocolControlPSS1CallControlandProtocolControlSegmentationP.D.FilterSEGMENTPDUsSegmentationP.D.FilterIUTunsegmentedPDUsandFigure3:RemotesinglelayertestmethodforSegmentationandProtocolDiscriminatorFilter4.3MultiplePCOtestingMultiplePCOtestingappliestotheProtocolControlandtheCallControlforTransitPINX.4.3.1CallControltestingforaTransitPINXAsshowninfigure4,theIUTistheProtocolControlandCallControlpartoftheTransitPINX,anditisanopen-relaysystem.Consequently,thetestmethodchosenisaMulti-PartyTestMethodwithnoUT.ThetestsystemwillcontaintwoLTsattachedtotheIUTviatwoPCOs,calledLXandLYbetweentheProtocolControlandCallControlpart,andtheSegmentationpart.ThePDUsexchangedareonlyunsegmentedPDUs.SIST EN 300 805-2 V1.2.1:2005

ETSIETSIEN300805-2V1.2.1(2000-05)13SUT(RELAY-SYSTEM)CallControlProtocolControlandIUTSegmentationP.D.FilterSCMPSS1PCO:LXSegmentationP.D.FilterCallControlProtocolControlandLT1SegmentationP.D.FilterTESTSYSTEMLT2PCO:LYCallControlProtocolControlandSegmentationP.D.FilterLOWERTESTERCONTROLFUNCTIONTCPTCPPDUsUnsegmentedPDUsUnsegmentedSCMFigure4:Multi-partytestmethodforProtocolControlandCallControlforTransitPINX4.4TestConfigurationsanduseofConcurrentTTCNAsthisATScoversbothsingle-partytestingusingnon-concurrentTTCN,andmulti-partytestingusingconcurrentTTCN,thenotationchosenforthecompleteATSistheconcurrentTTCNsyntax.Therefore,testcomponentsaredefinedtodescribethetwoconfigurations:the"mono"configurationandthe"transit"configuration,asshowninfigures5and6.Themonoconfigurationisusedincaseofsingle-partytesting,i.e.fortheProtocolControltesting,theCallControltestingfornon-transitPINX,andtheSegmentationandProtocolDiscriminatorFiltertesting.Onlyonetestcomponent,whichisthemastertestcomponentMTC_MONO,connectedtotheIUTviathePCOsLXorLSEG,isneededinthiscase.IUTMTC_MONOLXorLSEGFigure5:MonoconfigurationSIST EN 300 805-2 V1.2.1:2005

ETSIETSIEN300805-2V1.2.1(2000-05)14Thetransitconfigurationisusedincaseofmulti-partytesting,i.e.fortheProtocolControlandCallControltestingfortransitPINX.Inthiscase,threetestcomponentsareneeded,thesearetheMasterTestComponentMTC_TRANSIT,andthetwoParallelTestComponentsPTC_XandPTC_Y,whichareconnectedtotheMasterTestComponentviathetwoCo-ordinationPointsCPXandCPY.PTC_XandPTC_YarefurtherconnectedtotheIUTviathetwoPCOsLXandLY.LXPTC_YLYIUTCPXCPYMTC_TRANSITPTC_XFigure6:Transitconfiguration5UntestableTestPurposesDuetotheATMschoseninthisATSorotherrestrictions,thefollowingtestpurposeshavebeenidentifiedasbeinguntestable,andthereforehavenotbeenderivedintotestcases:-TC002UQ;-TC002UR;-TC002UZ;-TC002UU;-TC002UV;-TC002UW;-TC032UX;-TC004US;-TC004UT.SIST EN 300 805-2 V1.2.1:2005

ETSIETSIEN300805-2V1.2.1(2000-05)156Conformance6.1PCTRconformanceAtestlaboratory,whenrequestedbyaclienttoproduceaPCTR,isrequired,asspecifiedinISO/IEC9646-5[11],toproduceaPCTRconformantwiththePCTRtemplategiveninannexBofISO/IEC9646-5[11].Furthermore,atestlaboratory,offeringtestingfortheATSspecificationcontainedinannexC,whenrequestedbyaclienttoproduceaPCTR,isrequiredtoproduceaPCTRconformantwiththePCTRproformacontainedinannexB.APCTRwhichconformstothisPCTRproformaspecificationshallpreservethecontentandorderingoftheclausescontainedinannexB.ClauseB.6ofthePCTRmaycontainadditionalcolumns.Ifincluded,theseshallbeplacedtotherightoftheexistingcolumns.Textinitalicsmayberetainedbythetestlaboratory.6.2PIXITconformanceAtestrealizer,producinganexecutabletestsuitefortheATSspecificationcontainedinannexC,isrequired,asspecifiedinISO/IEC9646-4[10],toproduceanaugmentedpartialPIXITproformaconformantwiththispartialPIXITproformaspecification.AnaugmentedpartialPIXITproformawhichconformstothispartialPIXITproformaspecificationshall,asaminimum,havecontentswhicharetechnicallyequivalenttoannexA.TheaugmentedpartialPIXITproformamaycontainadditionalquestionsthatneedtobeansweredinordertopreparetheMeansOfTesting(MOT)foraparticularIUT.Atestlaboratory,offeringtestingfortheATSspecificationcontainedinannexC,isrequired,asspecifiedinISO/IEC9646-5[11],tofurtheraugmenttheaugmentedpartialPIXITproformatoproduceaPIXITproformaconformantwiththispartialPIXITproformaspecification.APIXITproformawhichconformstothispartialPIXITproformaspecificationshall,asaminimum,havecontentswhicharetechnicallyequivalenttoannexA.ThePIXITproformamaycontainadditionalquestionsthatneedtobeansweredinordertopreparethetestlaboratoryforaparticularIUT.6.3ATSconformanceThetestrealizer,producingMOTandETSforthisATSspecification,shallcomplywiththerequirementsofISO/IEC9646-4[10].Inparticular,theseconcerntherealizationofanETSbasedoneachATS.ThetestrealizershallprovideastatementofconformanceoftheMOTtothisATSspecification.ThisspecificationisapplicabletoimplementationswhichsupporteitheraBasicRateoraPrimaryRateaccessinterface,orboth,operatingoveraleasedline.Ameansoftestmayofferoneorbothaccesstypes.AnETSwhichconformstothisATSspecificationshallcontaintestgroupsandtestcaseswhicharetechnicallyequivalenttothosecontainedintheATSinannexC.Allsequencesoftesteventscomprisinganabstracttestcaseshallbecapableofbeingrealizedintheexecutabletestcase.AnyfurthercheckingwhichthetestsystemmightbecapableofperformingisoutsidethescopeofthisATSspecificationandshallnotcontributetotheverdictassignmentforeachtestcase.AMeansofTestconformingtothisATSshallimplementatleastasubsetoftestcaseswhichisthecompletesubsetoftestcasesselectedaccordingtotheselectionexpressionsforaparticularconsistentsetoftestsuiteparameters.SuchasubsetmayincludeonlytestcasesapplicabletoTransitPINXorEndPINXtesting.TestlaboratoriesrunningconformancetestservicesusingthisATSshallcomplywithISO/IEC9646-5[11].Thetestcasesconcerninginformationchannelselection(TC002BD-BE,TC002BV-CETC002JD-JG,TC002YM-YQ,TC002YU-ZB)shallberepeatedwiththeIUTconfiguredasA-sideandB-sideand,iftheChannelmapissupported,withChannellistandChannelmap.ThetestsuiteparameterIUT_AshallbesetoneachruntoindicatewhichsidetheIUTisconfiguredas.AtestlaboratorywhichclaimstoconformtothisATSspecificationshalluseanMOTwhichconformstothisATS.SIST EN 300 805-2 V1.2.1:2005

ETSIETSIEN300805-2V1.2.1(2000-05)167ATSConventionsThisclausedescribestheconventionsadoptedinthisATSandgivesthenamingconventionsusedforthedifferentATSelements.7.1ShortnamesandabbreviationsThroughouttheATSshortnamesandabbreviationsforPDUsandASPsareused,alsoabbreviationsforInformationElementsareused.Thesearedefinedintables1to3.Table1:ShortnamesandabbreviationsforPDUsPDUnameShortNameAbbreviationALERTINGALERTINGALECALLPROCEEDINGCALL_PROCCPRCONNECTCONNECTCONCONNECTACKNOWLEDGECONN_ACKCOADISCONNECTDISCONDISFACILITYFACILITYFACINFORMATIONINFOINFNOTIFYNOTIFYNOTPROGRESSPROGRESSPRORELEASERELEASERELRELEASECOMPLETEREL_COMRLCRESTARTRESTARTRESRESTARTACKNOWLEDGEREST_ACKRSASETUPSETUP,SETUPSSETSETUPACKNOWLEDGESETUP_ACKSUASEGMENTSEGMENTSEGSTATUSSTATUSSTASTATUSENQUIRYSTAT_ENQSTQErrorPDU(note1)ERRORERRQ931message(note2)Q931MSGQ931Genericmessage(note3)GENERICGENNOTE1ERROR_PDUisusedforincorrectlycodedmessagessentbythetesterwhichdonothavethecorrectstructureforanyvalidmessagetype.NOTE2:Q931MSGisusedtoreceiveanymessagewithoutexaminingitscontents.NOTE3:GENERICisusedformessagesreceivedbythetesterwherethemessagetypemayvarybutitisnecessarytoexaminethecontentsofthemessage.Table2:ShortnamesandabbreviationsforASPsASPnameShortnameAbbreviationDL-DATA-REQUESTDL_DAT_REQDLRQDL-DATA-INDICATION(note)DL_DAT_INDDLINDL-ESTABLISH-REQUESTDL_EST_REQDERQDL-ESTABLISH-INDICATIONDL_EST_INDDEINDL-ESTABLISH-CONFIRMDL_EST_CONDECODL-RELEASE-REQUESTDL_REL_REQDRRQDL-RELEASE-INDICATIONDL_REL_INDDRINDL-RELEASE-CONFIRMDL_REL_CONDRCONOTE:DLIN_SEGisusedasDL-DATA-INDICATIONforsegmentation.SIST EN 300 805-2 V1.2.1:2005

ETSIETSIEN300805-2V1.2.1(2000-05)17Table3:AbbreviationsforInformationElementsInformationElementnameAbbreviationProtocoldiscriminatorPDCallReferenceCRMessagetypeMTSendingcompleteSCLockingshift(note1)LSBearercapabilityBCAPCauseCAUCalledpartynumberCDPNCalledpartysubaddressCDPSCallingpartynumberCGPNCallingpartysubaddressCGPSChannelidentificationCHIConnectednumberCNDNConnectedsubaddressCNDSCallstateCSTHighlayercompatibilityHLCLowlayercompatibilityLLCNotificationindicatorNOTPartycategoryPCProgressindicator(note2)PI,PIsRestartindicatorRISegmentedmessageSMTransitcounterTCUnspecifiedIE(note3)UNSPNOTE1:LS4andLS5areusedastheabbreviationsforlockingshifttocodesets4and5.NOTE2:PIsisusedformultipleprogressindicator.NOTE3:UNSPisusedwhereanIEsenttotheIUTdoesnothavethestructureofanyvalidIE.7.2Testsuitetype,ASPtype,PDUtypeandAliasidentifiers7.2.1ASPtypeidentifiersTheidentifierofanASPistheshortnameoftheASP.EXAMPLE:DL_DAT_REQistheDL-DATA-REQUESTASP.7.2.2PDUtypeidentifiersTheidentifierofaPDUtypeistheshortnameofthePDU.EXAMPLE:DISCONistheDISCONNECTPDU.7.2.3TestSuiteTypeidentifiers(InformationElements)TheidentifierofatestsuitetypedescribingasingleinformationelementistheabbreviationfortheIEwiththesuffix"_TYP".EXAMPLE1:BCAP_TYPistheBearercapabilityIEtype.TheidentifierforatypedescribinganinvalidvariantofanIEistheabbreviationfortheIEwiththesuffix"_TYP_BAD".EXAMPLE2:CR_TYP_BADisatypeforaninvalidCallReferenceIE.SIST EN 300 805-2 V1.2.1:2005

ETSIETSIEN300805-2V1.2.1(2000-05)18Theelement(Field)namesusedwithinstructuredtypeswhichdescribingInformationElements(IEs)consistoftheabbreviationfortheIEfollowedbyanunderscore,followedby,inabbreviatedform,andinlowercase,thenameoftherelevantfield.EXAMPLE3:BCAP_codstdistheCodingStandardFieldtypeoftheBearerCapabilityIE.7.2.4AliasesAliasesareusedintheATStoshowwhichPDUisbeingsentorreceivedwithinanASP.TheidentifiersforaliasesconsistoftheshortnameofthePDU,withthesuffix"rq"usedinaliasesforDL_DAT_REQ(PDUssentbythetester)andthesuffix"in"usedinthecaseofaliasesforDL_DAT_IND(PDUsreceivedbythetester).EXAMPLE:CONN_ACKrqisanaliasforDL_DAT_REQusedforsendingaCONNECTACKNOWLEDGEmessage.7.3Identifiersconcerningtestconfiguration7.3.1TestcomponentsThenameofanMasterTestComponent(MTC)iscomposedoftheprefix"MTC_",followedbyastringinuppercaseidentifyingthefunctionoftheMTC.EXAMPLE1:MTC_MONOistheMasterTestComponentusedinthemonoconfiguration.ThenameofaParallelTestComponent(PTC)iscomposedoftheprefix"PTC_",followedbyanuppercaseletterindicatingwhichinterfacethePTCcontrols.EXAMPLE2:PTCXistheParallelTestComponentrepresentingtheXinterfaceoftheIUT.7.3.2TestcomponentconfigurationsThenameofaconfigurationiscomposedoftheprefix"Config_",followedbyanameindicatingthefunctionoftheconfiguration.Thefirstletterofthisnameisinuppercaseandtheremainderinlowercase.EXAMPLE:Config_Transitisusedfortransitconfiguration.Thetwofiguresinsubclause4.4showalogicalviewoftheconfigurationsused.7.3.3PointsofControlandObservations(PCOs)ThePointofControlandObservationidentifiersarecomposedof"L"(forLowertester)followedbyaanuppercaseletterindicatingtheinterfacethatthePCOisconnectedto.EXAMPLE:LXisthePCOoninterfaceXintheLT.7.3.4Co-ordinationPoints(CPs)TheCo-ordinationPointidentifiersarecomposed"CP"followedbyanuppercaseletterindicatingthePTCtheCPcommunicateswith.(AllCPsusedarebetweentheMTCandonePTC).EXAMPLE:CPXisaCo-ordinationPointbetweentheMTC_TRANSITcomponentandthePTCXcomponent.7.3.5CMtypesTheidentifierofaCo-ordinationMessagetypeisastringinuppercase.EXAMPLE:READYisaCMusedtorequestif,ortoindicatethat,aPTCisreadySIST EN 300 805-2 V1.2.1:2005

ETSIETSIEN300805-2V1.2.1(2000-05)197.4TestSuiteParameterandSelectionExpressionidentifiers7.4.1TestsuiteparametersTwocategoriesoftestsuiteparameterscanbedistinguishedasfollows:-PICScategory:thosederivedfromthePICSproformaquestions;-PIXITcategory:thosederivedfromthePIXITproformaquestions.andthelattercanbefurthersubdividedintothefollowingparts:-PIXITvalues:parametersconcerningtheprotocolitself;-Configurationparameters:parametersconcerningtheIUTconfiguration:-Values:Valuesusedwithintestcases;-Boolean:Parametersindictingifthecorrespondingvalueisavailable.AllthePICSparametersandPIXITparametersofthePIXITvaluesareBoolean.ThetypesoftheConfigurationValuesdependonthetypeofinformationrepresentedbytheparameter.TheidentifierofthetestsuiteparameterdependsonwhetheritisaPICSorPIXITparameter.Ineachcaseitstartswithaprefixidentifyingthecategory.7.4.2PICSParametersTheidentifiersofPICSparametersstartwiththeprefix"PC_"followedbythereferenceoftheitemintherelevantPICS.EXAMPLE:PC_B3relatestoitemB3intheBasicCallPICS"IstheimplementationcapableoffunctioningasaTransitPINX?".7.4.3PIXITparametersTheidentifiersofPIXITparametersinthePIXITvalues,ConfigurationvaluesandBooleanvaluecategoriesstartwiththeprefix"PX_","tsp_"or"CO"respectively.Thisisfollowedbyastringofabbreviations,separatedbyunderscores,describingthemeaningoftheparameterasdescribedinsubclause7.4.5.EXAMPLE1:PX_S0_isSETisaparametermeaning"DoestheIUTsupportimplicitsendingofSETUPinstate0".EXAMPLE2:tsp_InvNum1isaparametermeaning"AnumberwhichtheIUTcandeterminetobeinvalid".EXAMPLE3:CO_Cnumisaparametermeaning"IsanumberwhichtheIUTcandeterminetobecompleteavailable".7.4.4TestCaseSelectionExpressionsTheidentifiersofTestCaseSelectionExpressionsconsistofastringofabbreviations,separatedbyunderscores,describingthemeaningoftheparameterasdescribedinsubclause7.4.5.EXAMPLE:TR_ENT_TCC1isaselectionexpressionmeaningwhentrue"TheIUT,asatransitPINX,canenterstateTCC1.SIST EN 300 805-2 V1.2.1:2005

ETSIETSIEN300805-2V1.2.1(2000-05)207.4.5AbbreviationsusedinPIXITparametersandTestCaseSelectionExpressionsTheabbreviationsusedinthePIXITparametersandTestCaseSelectionExpressionsaredefinedintable4.WhileitispossibletoseefromtheseabbreviationstheapproximatemeaningoftheparameterorexpressionitisnecessarytorefertotheappropriatetableintheTTCNATSorthereferencedPIXITquestiontodeterminetheexactmeaning.Table4AbbreviationMeaningOC,Out_CallOutgoingcallIC,In_CallIncomingcallTRTransitPINXTETerminatingPINXOIOriginatingPINXOGOutgoingGatewayPINXIGIncomingGatewayPINXENTEntersstateUNUnstableS8etc.State8.etc.(IfthisisthelastcomponentitmeansthattheIUTcanenterandisstableinthespecifiedstate.IfitisfollowedbyamessageitmeansthattheIUTcansendthemessageinthespecifiedstate).T304etc.TimerT304etc.implementednoNumberrelRelaysRELetc.IUTcansentRELEASEmessageetc.(Messageabbreviationsareasdefinedintable?).iRELetc.ImplicitsendofRELEASEpossibleetc.iCLEARImplicitclearingpossibleimpFeatureisimplementedretrRetransmitsonUNRECIUTsendsmessageonrec
...