SIST EN 300 188-4 V1.3.3:2003
(Main)Integrated Services Digital Network (ISDN); Three-Party (3PTY) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the user
- Abstract
To handle comments and incorporate appropriate corrections into the ATS of DSS1 L2
- Status
- Published
- Publication Date
- 30-Nov-2003
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Dec-2003
- Due Date
- 01-Dec-2003
- Completion Date
- 01-Dec-2003
SIST EN 300 188-4 V1.3.3:2003 is the Slovenian adoption of ETSI EN 300 188-4 V1.3.3 for the Integrated Services Digital Network (ISDN) Three-Party (3PTY) supplementary service using the Digital Subscriber Signalling System No. one (DSS1) protocol. It specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the user side of the T reference point, so implementers and test laboratories can assess conformance to EN 300 188-1.
What does SIST EN 300 188-4 V1.3.3:2003 specify?
SIST EN 300 188-4 V1.3.3:2003 specifies the user-side ATS and partial PIXIT proforma for implementations of the 3PTY supplementary service. It sits in a six-part series: Part 1 gives the protocol specification, Part 2 the PICS proforma, Part 3 the TSS & TP for the user, Part 4 this ATS and partial PIXIT, and Parts 5 and 6 cover the network side.
| Annex | What it covers |
|---|---|
| Annex A | Protocol Conformance Test Report (PCTR) proforma |
| Annex B | Partial PIXIT proforma |
| Annex C | ATS |
| Annex D | General structure of ATS |
| Annex E | Change record |
The scope focuses on handling comments and incorporating corrections into the ATS of DSS1 L2, and on the user side of the T reference point or coincident S and T reference point.
What are the key requirements of SIST EN 300 188-4 V1.3.3:2003?
Test method and observation
Clause 4 uses the remote test method. The Point of Control and Observation (PCO) is at the service access point between layers 2 and 3 and is named L. In practice, verdicts come from what the tester sees at L, so this is the point that must be connected and monitored during test execution.
Clause 4 also introduces an informal PCO named O for test coordination procedures (TCP). O is for control only, not for verdicts. That matters because it lets the ATS describe operator actions clearly without turning those actions into test results.
ATS structure and encoding
Clause 6 organizes the ATS like a TTCN test suite, with declarations, constraints, and a dynamic part. Simple and structured types carry length or value restrictions, and information element identifiers are modeled as single-value types so a derived test system can identify embedded information elements more easily.
The ATS uses both TTCN and ASN.1. ASN.1 is used where ordered or unordered structures are easier to model, and for remote operation components. ASPs and PDUs have a one-to-one relationship when a PDU is carried, which keeps test events aligned with protocol data.
Clause 6.2.2.1 distinguishes Basic Encoding Rules (BER) from ISDN encoding. ISDN encoding is the default, while BER is used only where stated. For BER-encoded components, the ATS expects variety in length forms during a test campaign, so the implementation is exercised with multiple encodings, not just one convenient form.
Test cases, mapping and conformance
Clause 6.3 says each test case contains the test purpose text from EN 300 188-3, and test steps are reused to avoid repetition. Clause 7 gives a one-to-one mapping between test purposes and test case names. In practice, that makes the ATS easier to trace from the TSS & TP document to executable tests.
Clauses 8 to 10 tie the ATS to reporting and conformance. Annex A gives the PCTR proforma, Annex B the partial PIXIT proforma, and Annex C the ATS itself. Test laboratories, test realizers and ATS users must follow these structures when claiming conformance.
What terms does SIST EN 300 188-4 V1.3.3:2003 define?
- Abstract Test Suite (ATS) - The collection of abstract test cases used to assess protocol behavior.
- Implementation Under Test (IUT) - The implementation being checked for protocol conformance.
- Lower Tester (LT) - The test system component that interacts with the IUT at the lower interface.
- Point of Control and Observation (PCO) - The point where test events are controlled and observed.
- Protocol Implementation Conformance Statement (PICS) - The statement that describes what an implementation supports.
- Protocol Implementation eXtra Information for Testing (PIXIT) - Implementation-specific testing information needed to prepare tests.
- System Under Test (SUT) - The complete system that includes the IUT during testing.
- Upper Tester (UT) - The tester role above the IUT used for coordination.
Who uses SIST EN 300 188-4 V1.3.3:2003?
Telecommunications test laboratories use this standard to prepare, run and report conformance tests. Test realizers use it to build an executable test suite and the associated Means of Testing (MOT). Equipment developers and quality teams use it when they need to check whether an ISDN user implementation supports 3PTY in line with EN 300 188-1.
What changed in SIST EN 300 188-4 V1.3.3:2003 from the previous edition?
Annex E says the update from EN 300 188-4 V1.2 to V1.3 includes a revised ATS. It also records the conversion to EN layout, replacement of references to ETS 300 102 with EN 300 403-1, and substitution of non-specific references with the latest versions of the cited basic standards.
Which standards are used with SIST EN 300 188-4 V1.3.3:2003?
- EN 300 188-1 - The protocol specification for the 3PTY supplementary service.
- EN 300 188-2 - The PICS proforma specification.
- EN 300 188-3 - The TSS & TP specification for the user.
- EN 300 196-1 - Provides generic supplementary-service protocol material used in the ASN.1 examples.
- EN 300 403-1 - Gives the DSS1 signalling network layer for circuit-mode basic call control.
- ISO/IEC 9646-1 to 9646-5 - Provide the conformance testing framework, ATS specification, TTCN, test realization and laboratory requirements.
- ITU-T I.411 - Defines ISDN reference configurations used for the T reference point.
- CCITT X.209 - Defines BER for ASN.1.
- ETS 300 102 - Basic call control layer 3 reference mentioned in the document history.
What does the SIST EN 300 188-4 V1.3.3:2003 document contain?
The document contains the TTCN-based ATS, the partial PIXIT proforma, and the PCTR proforma for user-side 3PTY testing. It also includes clause text on test method, ATS conventions, conformance rules, and ATS-to-test-purpose mapping.
Annex C provides the ATS in two representations: TTCN.GR and TTCN.MP. Annex B gives the questions and fields needed to prepare test execution, including protocol identification, parameter values, stimulus actions and timer values. Annex A gives the reporting form used to record conformance assessment results.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST EN 300 188-4 V1.3.3:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Integrated Services Digital Network (ISDN); Three-Party (3PTY) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the user". This standard covers: To handle comments and incorporate appropriate corrections into the ATS of DSS1 L2
To handle comments and incorporate appropriate corrections into the ATS of DSS1 L2
SIST EN 300 188-4 V1.3.3:2003 is classified under the following ICS (International Classification for Standards) categories: 33.080 - Integrated Services Digital Network (ISDN). The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 300 188-4 V1.3.3:2003 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.VWRULWHYIntegrated Services Digital Network (ISDN); Three-Party (3PTY) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; 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 300 188-4 Version 1.3.3SIST EN 300 188-4 V1.3.3:2003en01-december-2003SIST EN 300 188-4 V1.3.3:2003SLOVENSKI
STANDARD
ETSIEN300188-4V1.3.3(2000-05)EuropeanStandard(Telecommunicationsseries)IntegratedServicesDigitalNetwork(ISDN);Three-Party(3PTY)supplementaryservice;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part4:AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationfortheuserSIST EN 300 188-4 V1.3.3:2003
ETSIETSIEN300188-4V1.3.3(2000-05)2ReferenceREN/SPS-05167-4KeywordsISDN,DSS1,supplementaryservice,3PTY,ATS,PIXIT,userETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:+33492944200Fax:+33493654716SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88ImportantnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http://www.etsi.orgThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSIdocumentsisavailableathttp://www.etsi.org/tb/status/Ifyoufinderrorsinthepresentdocument,sendyourcommentto:editor@etsi.frCopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 300 188-4 V1.3.3:2003
ETSIETSIEN300188-4V1.3.3(2000-05)3ContentsIntellectualPropertyRights.5Foreword.51Scope.62References.63Definitionsandabbreviations.73.1Definitions.73.2Abbreviations.74AbstractTestMethod(ATM).85Untestabletestpurposes.86ATSconventions.86.1Declarationspart.86.1.1Typedefinitions.86.1.1.1Simpletypedefinitions.86.1.1.2Structuredtypedefinitions.96.1.1.2.1TTCNstructuredtypedefinitions.96.1.1.2.2ASN.1structuredtypedefinitions.96.1.1.3ASPtypedefinitions.106.1.1.3.1TTCNASPtypedefinitions.106.1.1.3.2ASN.1ASPtypedefinitions.106.1.1.4PDUtypedefinitions.106.1.1.4.1TTCNPDUtypedefinitions.106.1.1.4.2ASN.1PDUtypedefinitions.116.1.2Testsuiteconstants.116.1.3Testsuiteparameters.116.1.4Variables.116.1.4.1Testsuitevariables.116.1.4.2Testcasevariables.116.1.5Testsuiteoperationdefinitions.116.2Constraintspart.126.2.1Structuredtypeconstraintdeclaration.126.2.2ASN.1typeconstraintdeclaration.126.2.2.1Specificationofencodingrules.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.5Chainingofconstraints.146.2.5.1Staticchaining.146.2.5.2Dynamicchaining.146.2.6Derivedconstraints.146.2.7Parameterizedconstraints.156.2.8Valueassignment.156.2.8.1Specificvalues.156.2.8.2Matchingvalues.156.3Dynamicpart.156.3.1Testcases.156.3.2Teststeps.156.3.3Defaults.15SIST EN 300 188-4 V1.3.3:2003
ETSIETSIEN300188-4V1.3.3(2000-05)47ATStoTPmap.158PCTRconformance.169PIXITconformance.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.18A.5Staticconformancereviewreport.19A.6Testcampaignreport.19A.7Observations.19AnnexB(normative):PartialPIXITproforma.20B.1Identificationsummary.20B.2Abstracttestsuitesummary.20B.3Testlaboratory.20B.4Client(ofthetestlaboratory).21B.5SystemUnderTest(SUT).21B.6Protocolinformation.22B.6.1Protocolidentification.22B.6.2Parametervalues.22B.6.3SendingofmessagesbyIUT.22B.6.4Timervalues.22AnnexC(normative):AbstractTestSuite(ATS).23C.1TheTTCNGraphicalform(TTCN.GR).23C.2TheTTCNMachineProcessableform(TTCN.MP).23AnnexD(informative):GeneralstructureofATS.24AnnexE(informative):Changerecord.25E.1ChangesbetweenEN300188-4V1.2and1.3.25E.2ChangesbetweenETS300188-4andEN300188-4V1.2.25History.26SIST EN 300 188-4 V1.3.3:2003
ETSIETSIEN300188-4V1.3.3(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-partstandardcoveringtheDigitalSubscriberSignallingSystemNo.one(DSS1)protocolspecificationfortheIntegratedServicesDigitalNetwork(ISDN)ThreeParty(3PTY)supplementaryservice,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".ThepresentversionupdatestheATS.NationaltranspositiondatesDateofadoptionofthisEN:28April2000DateoflatestannouncementofthisEN(doa):31July2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31January2001DateofwithdrawalofanyconflictingNationalStandard(dow):31January2001SIST EN 300 188-4 V1.3.3:2003
ETSIETSIEN300188-4V1.3.3(2000-05)61ScopeThisfourthpartofEN300188specifiestheAbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformafortheUsersideoftheTreferencepointorcoincidentSandTreferencepoint(asdefinedinITU-TRecommendationI.411[11])ofimplementationsconformingtothestagethreestandardfortheThreeParty(3PTY)supplementaryserviceforthepan-EuropeanIntegratedServicesDigitalNetwork(ISDN)bymeansoftheDigitalSubscriberSignallingSystemNo.one(DSS1)protocol,EN300188-1[2].EN300188-3[4]specifiestheTestSuiteStructureandTestPurposes(TSS&TP)relatedtothisATSandpartialPIXITproformaspecification.OtherpartsspecifytheTSS&TPandtheATSandpartialPIXITproformafortheNetworksideoftheTreferencepointorcoincidentSandTreferencepointofimplementationsconformingtoEN300188-1[2].2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIEN300403-1:"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Signallingnetworklayerforcircuit-modebasiccallcontrol;Part1:Protocolspecification[ITU-TRecommendationQ.931(1993),modified]".[2]ETSIEN300188-1(V1.2):"IntegratedServicesDigitalNetwork(ISDN);Three-Party(3PTY)supplementaryservice;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part1:Protocolspecification".[3]ETSIEN300188-2(V1.2):"IntegratedServicesDigitalNetwork(ISDN);Three-Party(3PTY)supplementaryservice;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecification".[4]ETSIEN300188-3(V1.2):"IntegratedServicesDigitalNetwork(ISDN);Three-Party(3PTY)supplementaryservice;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part3:TestSuiteStructureandTestPurposes(TSS&TP)specificationfortheuser".[5]ETSIEN300196-1:"IntegratedServicesDigitalNetwork(ISDN);Genericfunctionalprotocolforthesupportofsupplementaryservices;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part1:Protocolspecification".[6]ISO/IEC9646-1:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[7]ISO/IEC9646-2:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part2:Abstracttestsuitespecification".[8]ISO/IEC9646-3:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part3:TheTreeandTabularCombinedNotation(TTCN)".[9]ISO/IEC9646-4:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part4:Testrealization".SIST EN 300 188-4 V1.3.3:2003
ETSIETSIEN300188-4V1.3.3(2000-05)7[10]ISO/IEC9646-5:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part5:Requirementsontestlaboratoriesandclientsfortheconformanceassessmentprocess".[11]ITU-TRecommendationI.411(1993):"ISDNuser-networkinterfaces-Referenceconfigurations".[12]CCITTRecommendationX.209(1988):"SpecificationofbasicencodingrulesforAbstractSyntaxNotationOne(ASN.1)".[13]ETSIETS300102:"IntegratedServicesDigitalNetwork(ISDN);User-networkinterfacelayer3;Specificationsforbasiccallcontrol".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:AbstractTestSuite(ATS):seeISO/IEC9646-1[6]ImplementationUnderTest(IUT):seeISO/IEC9646-1[6]LowerTester(LT):seeISO/IEC9646-1[6]PointofControlandObservation(PCO):seeISO/IEC9646-1[6]ProtocolImplementationConformanceStatement(PICS):seeISO/IEC9646-1[6]PICSproforma:seeISO/IEC9646-1[6]ProtocolImplementationeXtraInformationforTesting(PIXIT):seeISO/IEC9646-1[6]PIXITproforma:seeISO/IEC9646-1[6]SystemUnderTest(SUT):seeISO/IEC9646-1[6]UpperTester(UT):seeISO/IEC9646-1[6]3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:3PTYThreePartyASPAbstractServicePrimitiveATMAbstractTestMethodATSAbstractTestSuiteBERBasicEncodingRulesExTSExecutableTestSuiteIUTImplementationUnderTestLTLowerTesterMOTMeansOfTestingPCOPointofControlandObservationPDUProtocolDataUnitPICSProtocolImplementationConformanceStatementPIXITProtocolImplementationeXtraInformationforTestingSUTSystemUnderTestTCPTestCo-ordinationProceduresTPTestPurposeTTCNTreeandTabularCombinedNotationUTUpperTesterSIST EN 300 188-4 V1.3.3:2003
ETSIETSIEN300188-4V1.3.3(2000-05)84AbstractTestMethod(ATM)Theremotetestmethodisappliedforthe3PTYuserATS.ThePointofControlandObservation(PCO)residesattheserviceaccesspointbetweenlayers2and3.ThisPCOisnamed"L"(forLower).TheLPCOisusedtocontrolandobservethebehaviouroftheImplementationUnderTest(IUT)andtestcaseverdictsareassigneddependingonthebehaviourobservedatthisPCO.TesterSUTLTIUTPCOLayer2Layer2Layer1Layer1ServiceproviderFigure1:RemotetestmethodISO/IEC9646-2[7]allowstheinformalexpressionofTestCo-ordinationProcedures(TCP)betweentheSystemUnderTest(SUT)upperlayer(s)andtheLowerTester(LT).IntheATScontainedinannexC,TCPisachievedbyuseofasecond"informal"PCO,called"O"(forOperator).ThisPCOisusedtospecifycontrolbutnotobservationabovetheIUTandconsequently,eventsatthisPCOareneverusedtogeneratetestcaseverdicts.TheuseofthisOPCOisregardedasapreferredalternativetotheuseoftheimplicitsendevent,inthatitallowstheATStospecifyinaclearandmeaningfulwaywhatactionsarerequiredtobeperformedontheIUT.5UntestabletestpurposesTherearenountestabletestpurposesassociatedwiththisATS.6ATSconventionsThisclauseisstructuredsimilarlytothestructureofaTTCNATS.However,thenamesofthesubclausesarearrangedinawaymoresuitabletothepresentdocument.6.1Declarationspart6.1.1Typedefinitions6.1.1.1SimpletypedefinitionsWhereappropriate,simpletypeshavealength,avaluelistorarangerestrictionattached.Simpletypesdefinedasbeingofsomestringtype(e.g.BITSTRING,OCTETSTRING),havealengthrestrictionoravaluelistattached.Simpletypes,definedasbeingofINTEGERtype,haveavaluelistorarangerestrictionattached.SIST EN 300 188-4 V1.3.3:2003
ETSIETSIEN300188-4V1.3.3(2000-05)96.1.1.2Structuredtypedefinitions6.1.1.2.1TTCNstructuredtypedefinitionsAllstructuredtypedefinitionsareprovidedwithafullname.Allelementsineverystructuredtypedefinition,definedasbeingofsomestringtype(e.g.BITSTRING,OCTETSTRING),havealengthrestrictionattached.Ifanelementinastructuredtypedefinitionisdefinedasbeingofareferencedtype,the(possible)restrictionisdefinedinthatreferencedtype.Forinformationelementstheidentifier,whichisuniqueforeachelement,hasitstypedefinedasasimpletypewherethevaluelistisrestrictedtothesinglevaluewhichistheidentifieritself.ThishastheadvantagethatitallowsatestsystemderivedfromthisATStoeasilyidentifyinformationelementsembeddedinmessages.AnATSwhereinformationelementidentifiersarerepresentedasunrestrictedtypescanpresentdifficultiesforaderivedtestsysteminthecasewhereitneedstofindoneinformationelementembeddedinanumberofothersandtheconstraintsfortheotherelementshavetheany-or-omitvalue.Insuchacasethetestsystemcannoteasilyfindthebeginningofeachinformationelement.6.1.1.2.2ASN.1structuredtypedefinitionsASN.1hasbeenusedforthreemajorreasons.First,typesdefinedinASN.1canmodelproblemsthat"pure"TTCNcannot.Forinstance,datastructuresmodellingorderedorunorderedsequencesofdataarepreferablydefinedinASN.1.Second,ASN.1providesabetterrestrictionmechanismfortypedefinitionsbyusingsub-typedefinitions.Third,itisnecessarytouseASN.1toreproducethetypedefinitionsforremoteoperationcomponentsasspecifiedinthebasestandards.ThefactthatASN.1providesabetterrestrictionmechanismfortypedefinitionsisusedforthepurposeofachievingtype-compatibility.Tables1and2showthetypicaluseofASN.1.TheFIEtypeintable1iswritteninASN.1topermittheuseoftheSETOFconstructioninthecomponentsfield.ConstraintsoftheFIEtypecanthereforebewrittenusingtheSUPERSETfunctionwhichallowstomatchasinglecomponentwhichmaybedeliveredtogetherwithasetofothercomponents.Table2showstherejectcomponenttypewhichisdefinedfollowingtheASN.1declarationinEN300196-1[5].Table1:ASN.1typedefinitionFIEASN.1TypeDefinitionTypeName:FIEComments:FacilityinformationelementtakenfromEN300196;11.2.2.1.Specifiedhereforbothsend&receiveevent.TypeDefinitionSEQUENCE{informationElementIdentifierFIE_I,lengthFIE_LengthType,extBitBITSTRING(SIZE(1)),spareBitsBITSTRING(SIZE(2)),protocolProfileBITSTRING(SIZE(5)),componentsSETOFComponent}Table2:ASN.1typedefinitionRejectComponentASN.1TypeDefinitionTypeName:RejectComponentComments:RejectComponentisnotspecifictoanyparticularoperation.TheinvokeIDmaybeusedtoidentifyaspecificoperation.TypeDefinitionSEQUENCE{invokedIDCHOICE{invokeIDInvokeIDType,nullNULL},problemCHOICE{generalProblem[0]IMPLICITGeneralProblem,invokeProblem[1]IMPLICITInvokeProblem,returnResultProblem[2]IMPLICITReturnResultProblem,returnErrorProblem[3]IMPLICITReturnErrorProblem}}SIST EN 300 188-4 V1.3.3:2003
ETSIETSIEN300188-4V1.3.3(2000-05)10Table3showsanexampleofhowASN.1canbeusedtomodelunorderedsequences.Table3:ASN.1typedefinitionFIESASN.1TypeDefinitionTypeName:FIESComments:TypeDefinitionSETOFFIEThepossibilitytouseTTCNandASN.1incombinationisused,i.e.referringtoanASN.1typefromaTTCNtype.6.1.1.3ASPtypedefinitions6.1.1.3.1TTCNASPtypedefinitionsTTCNASPtypedefinitionsonlycontainonePDUornoPDUatall.TherelationshipbetweenanASPtypeandaPDUtypeisone-to-one.Thatis,thereexistsoneASPtypedefinitionforeachPDUtypedefinition(ifthatASPtypecontainsaPDU).AllTTCNASPtypedefinitionsareprovidedwithafullidentifier.SomeASPsarenotparameterizedasshownintheexampleintable4.SuchASPsareonlyusedforrequestingorreceivingservicefromthelowerlayer.Table4:TTCNASPtypedefinitionDL_REL_INTTCNASPTypeDefinitionASPNAME:DL_REL_IN(DL_RELEASE_INDICATION)PCOType:SAPComments:ParameterName|ParameterType|CommentsDetailedComments:Table5showsanexampleofaparameterizedASP.AllASPscontainingPDUscontainonlythatPDUandnootherparameters.Table5:TTCNASPtypedefinitionDL_DATA_RQ_ALERTTTCNASPTypeDefinitionASPNAME:DL_DATA_RQ_ALERT(DL_DATA_REQUEST)PCOType:SAPComments:ParameterName|ParameterType|Commentsmun(MessageUnit)|ALERT_PDU|DetailedComments:6.1.1.3.2ASN.1ASPtypedefinitionsTherearenoASN.1ASPtypedefinitionsintheATS.6.1.1.4PDUtypedefinitions6.1.1.4.1TTCNPDUtypedefinitionsTheTTCNPDUtypereflectstheactualdatabeingtransferredorreceived.AllPDUsareembeddedinASPs.IfaspecificPDUtypedefinitioncontainselementsdefinedintermsofapre-definedtype,thatelementhasarestrictionattachedtoit.SIST EN 300 188-4 V1.3.3:2003
ETSIETSIEN300188-4V1.3.3(2000-05)116.1.1.4.2ASN.1PDUtypedefinitionsTherearenoASN.1PDUtypedefinitionsintheATS.6.1.2TestsuiteconstantsNotestsuiteconstantsareusedordefinedinthisATS.6.1.3TestsuiteparametersEachtestsuiteparameterisdefinedintermsofapredefinedtypeorareferencedtype.Areferencedtypeisusedwhenitisnecessarytoattachrestrictionstothesetypedefinitions(itisnotallowedtoincluderestrictionsdirectlyinthetestsuiteparametertable).Thereferencedtypecanhavealengthorvaluerestrictionattachedtoitinitsdeclarationtable.6.1.4Variables6.1.4.1TestsuitevariablesNotestsuitevariablesareusedordefinedinthisATS.6.1.4.2TestcasevariablesEachtestcasevariableisdefinedintermsofapredefinedtypeorareferencedtype.Areferencedtypeisusedwhenitisnecessarytoattachrestrictionstothesetypedefinitions(itisnotallowedtoincluderestrictionsdirectlyinthetestcasevariabletable).Thereferencedtypecanhavealengthorvaluerestrictionattachedtoitinitsdeclarationtable.Wheretestcasevariablesareusedinconstraints,theyarepassedasformalparameters.6.1.5Testsuiteoperationdefin
...