SIST EN 300 195-4 V1.2.1:2004
(Main)Integrated Services Digital Network (ISDN); Supplementary service interactions; 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
Test specification for RE/SPS-05138-1
- Status
- Published
- Publication Date
- 31-Mar-2004
- Technical Committee
- SPN - Services and Protocols for Networks
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Apr-2004
- Due Date
- 01-Apr-2004
- Completion Date
- 01-Apr-2004
SIST EN 300 195-4 V1.2.1:2004 is the Slovenian adoption of ETSI EN 300 195-4 V1.2.1 for Integrated Services Digital Network (ISDN) supplementary service interactions. It gives the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the user side, so implementers and test labs can check conformance at the T reference point or the coincident S and T reference point.
What does SIST EN 300 195-4 V1.2.1:2004 specify?
SIST EN 300 195-4 V1.2.1:2004 specifies the user-side test material for implementations of the stage three supplementary service interactions standard that use the Digital Subscriber Signalling System No. one (DSS1) protocol. It is organized as a conformance-testing document built around an ATS plus the information needed to prepare test settings for a specific implementation.
The document is structured around the main clauses for scope, references, definitions, the abstract test method, ATS conventions, mapping, and conformance, followed by four annexes.
| Annex | What it covers |
|---|---|
| Annex A | Protocol Conformance Test Report (PCTR) proforma |
| Annex B | Partial PIXIT proforma |
| Annex C | ATS in TTCN.GR and TTCN.MP forms |
| Annex D | General structure of an ATS |
What are the key requirements of SIST EN 300 195-4 V1.2.1:2004?
SIST EN 300 195-4 V1.2.1:2004 is built for remote conformance testing. Clause 4 places the Point of Control and Observation (PCO) at the service access point between layers 2 and 3, and verdicts are based on what is observed there. In practice, this means the test result comes from lower-layer behavior at the interface under test, not from internal implementation details.
Clause 4 also uses an additional informal PCO called O for test co-ordination. This point is for control only, not for verdict assignment, which helps the tester describe setup actions clearly without confusing them with observations.
Clause 5 states that there are no untestable test purposes associated with the ATS. For a user, that means the suite is intended to cover the test purposes defined for it.
Clause 6 defines the ATS conventions. It uses TTCN and ASN.1 together, with structured type definitions, ASP and PDU definitions, test suite parameters, testcase variables, and test suite operation definitions. The practical effect is that the suite can describe both data content and test behavior in a way that can be turned into an executable test suite.
Clause 6.2 sets out the constraint rules. The ATS uses:
- static chaining for fixed bindings
- semi-dynamic chaining when a value is passed as a parameter
- parameterized constraints
- matching values such as AnyOrOmit, AnyValue, SuperSet, Omit, AnyOne and AnyOrNone
This matters because the test suite can adapt messages to the case being exercised while still keeping the expected structure controlled.
Clause 6.2.2 gives the encoding approach for ASN.1. ISDN encoding is the default for ASN.1 constraints, while BER is used only where it is explicitly stated. For BER, the ATS requires a variety of length forms to be used in test campaigns. In practice, the laboratory must be ready to send and receive the relevant encodings the implementation is expected to handle.
Clause 7 maps test purposes to test cases one-to-one by reusing the TP identifiers as test case names. That makes it easier to trace a test verdict back to the corresponding purpose.
Clauses 8 to 10 set the conformance expectations for the PCTR, PIXIT, ATS, and the test realizations. A laboratory or tool supplier claiming conformance must use the specified proformas and produce technically equivalent executable material.
What terms does SIST EN 300 195-4 V1.2.1:2004 define?
- Abstract Test Suite (ATS) - A formal set of abstract test cases used to assess protocol behavior.
- Implementation Under Test (IUT) - The implementation being checked for conformance.
- Point of Control and Observation (PCO) - The interface point where the tester controls and observes behavior.
- Protocol Implementation Conformance Statement (PICS) - The statement of what an implementation supports before testing.
- Protocol Implementation eXtra Information for Testing (PIXIT) - Extra implementation details needed to prepare and run tests.
- System Under Test (SUT) - The whole system that contains the IUT and the surrounding test context.
- Tree and Tabular Combined Notation (TTCN) - The notation used to write the ATS.
- Protocol Conformance Test Report (PCTR) - The report format used to record conformance test results.
Who uses SIST EN 300 195-4 V1.2.1:2004?
SIST EN 300 195-4 V1.2.1:2004 is used by test laboratories, test tool developers, and conformance assessment teams working on ISDN DSS1 supplementary service interactions. It is also used by equipment vendors and integrators who need to prepare a PICS, complete the PIXIT items, or verify that an implementation at the user side of the T reference point can pass the defined ATS.
Which standards are used with SIST EN 300 195-4 V1.2.1:2004?
| Standard | What it contributes |
|---|---|
| EN 300 195-1 | The protocol specification for supplementary service interactions |
| EN 300 195-2 | The PICS proforma specification |
| EN 300 195-3 | The TSS & TP specification for the user, which supplies the test purposes used here |
| EN 300 196-1 | Generic functional protocol support and BER-related guidance |
| ISO/IEC 9646-1 | General conformance testing concepts |
| ISO/IEC 9646-2 | Abstract Test Suite specification and abstract test method concepts |
| ISO/IEC 9646-3 | TTCN and ASN.1-based ATS notation and matching semantics |
| ISO/IEC 9646-4 | Test realization and executable test suite requirements |
| ISO/IEC 9646-5 | Test laboratory and client requirements, including PCTR expectations |
| ITU-T Recommendation I.411 | ISDN user-network interface reference configurations |
| CCITT Recommendation X.209 | Basic Encoding Rules (BER) for ASN.1 |
| EN 300 102-1 | Basic call control structures used in the ATS |
| EN 300 195-5 and EN 300 195-6 | The network-side companion parts mentioned in the series structure |
What does the SIST EN 300 195-4 V1.2.1:2004 document contain?
SIST EN 300 195-4 V1.2.1:2004 contains the ATS conventions, constraint descriptions, dynamic test behavior, and the reporting and proforma annexes needed to run and document conformance tests. Annex C provides the ATS itself in TTCN.GR and TTCN.MP forms, and the document notes that both forms are equivalent. Annex B gives the questionnaire-style PIXIT items for access type, service activation, options, timers, and basic call coding details, which helps a lab set up the Means Of Testing (MOT). Annex A provides the PCTR template used to report static and dynamic conformity 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 195-4 V1.2.1:2004 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Integrated Services Digital Network (ISDN); Supplementary service interactions; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the user". This standard covers: Test specification for RE/SPS-05138-1
Test specification for RE/SPS-05138-1
SIST EN 300 195-4 V1.2.1:2004 is classified under the following ICS (International Classification for Standards) categories: 33.080 - Integrated Services Digital Network (ISDN). The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 300 195-4 V1.2.1:2004 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.YSOLYDQMHIntegrated Services Digital Network (ISDN); Supplementary service interactions; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 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 195-4 Version 1.2.1SIST EN 300 195-4 V1.2.1:2004en01-april-2004SIST EN 300 195-4 V1.2.1:2004SLOVENSKI
STANDARD
ETSIEN300195-4V1.2.1(2000-11)EuropeanStandard(Telecommunicationsseries)IntegratedServicesDigitalNetwork(ISDN);Supplementaryserviceinteractions;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part4:AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationfortheuserSIST EN 300 195-4 V1.2.1:2004
ETSIETSIEN300195-4V1.2.1(2000-11)2ReferenceREN/SPAN-05138-4KeywordsISDN,DSS1,supplementaryservice,interaction,ATS,PIXIT,user,testingETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:+33492944200Fax:+33493654716SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88ImportantnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http://www.etsi.orgThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSIdocumentsisavailableathttp://www.etsi.org/tb/status/Ifyoufinderrorsinthepresentdocument,sendyourcommentto:editor@etsi.frCopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 300 195-4 V1.2.1:2004
ETSIETSIEN300195-4V1.2.1(2000-11)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.116.1.1.4PDUtypedefinitions.116.1.1.4.1TTCNPDUtypedefinitions.116.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.126.2Constraintspart.126.2.1Structuredtypeconstraintdeclaration.126.2.2ASN.1typeconstraintdeclaration.126.2.2.1Specificationofencodingrules.136.2.3ASPtypeconstraintdeclaration.146.2.3.1ASN.1ASPtypeconstraintdeclaration.146.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.156.2.7Parameterizedconstraints.156.2.8Valueassignment.156.2.8.1Specificvalues.156.2.8.2Matchingvalues.156.3Dynamicpart.156.3.1Testcases.156.3.2Teststeps.156.3.3Defaults.16SIST EN 300 195-4 V1.2.1:2004
ETSIETSIEN300195-4V1.2.1(2000-11)47ATStoTPmap.168PCTRconformance.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.21AnnexB(normative):PartialPIXITproforma.22B.1Identificationsummary.22B.2Abstracttestsuitesummary.22B.3Testlaboratory.22B.4Client(ofthetestlaboratory).23B.5SystemUnderTest(SUT).23B.6Protocolinformation.24B.6.1Protocolidentification.24B.6.2Parametervalues.24B.6.3Actionsrequiredtoinvokesupplementaryservices.24B.6.4Actionsrequiredtoactivatesupplementaryservices.25B.6.5ActionsrequiredtoprovoketheIUT.25B.6.6OptionssupportedbytheIUT.26B.6.7Timervalues.26B.7BasiccallPIXITitems.27B.7.1Parametervalues-informationelementcodings.27AnnexC(normative):AbstractTestSuite(ATS).28C.1TheTTCNGraphicalform(TTCN.GR).28C.2TheTTCNMachineProcessableform(TTCN.MP).28AnnexD(informative):GeneralstructureofATS.29History.30SIST EN 300 195-4 V1.2.1:2004
ETSIETSIEN300195-4V1.2.1(2000-11)5IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinETSISR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinETSISR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSITechnicalCommitteeServicesandProtocolsforAdvancedNetworks(SPAN).Thepresentdocumentispart4ofamulti-partdeliverablecoveringtheDigitalSubscriberSignallingSystemNo.one(DSS1)protocolspecificationfortheIntegratedServicesDigitalNetwork(ISDN)supplementaryserviceinteractions,asdescribedbelow:Part1:"Protocolspecification";Part2:"ProtocolImplementationConformanceStatement(PICS)proformaspecification";Part3:"TestSuiteStructureandTestPurposes(TSS&TP)specificationfortheuser";Part4:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationfortheuser";Part5:"TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetwork";Part6:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforthenetwork".NationaltranspositiondatesDateofadoptionofthisEN:3November2000DateoflatestannouncementofthisEN(doa):28February2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31August2001DateofwithdrawalofanyconflictingNationalStandard(dow):31August2001SIST EN 300 195-4 V1.2.1:2004
ETSIETSIEN300195-4V1.2.1(2000-11)61ScopeThepresentdocumentspecifiestheAbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformafortheUsersideoftheTreferencepointorcoincidentSandTreferencepoint(asdefinedinITU-TRecommendationI.411[10])ofimplementationsconformingtothestagethreestandardforthesupplementaryserviceinteractionsforthepan-EuropeanIntegratedServicesDigitalNetwork(ISDN)bymeansoftheDigitalSubscriberSignallingSystemNo.one(DSS1)protocol,EN300195-1[1].EN300195-3[3]specifiestheTestSuiteStructureandTestPurposes(TSS&TP)relatedtothisATSandpartialPIXITproforma.OtherpartsspecifytheTSS&TPandtheATSandpartialPIXITproformafortheNetworksideoftheTreferencepointorcoincidentSandTreferencepointofimplementationsconformingtoEN300195-1[1].2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIEN300195-1:"IntegratedServicesDigitalNetwork(ISDN);Supplementaryserviceinteractions;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part1:Protocolspecification".[2]ETSIEN300195-2:"IntegratedServicesDigitalNetwork(ISDN);Supplementaryserviceinteractions;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecification".[3]ETSIEN300195-3:"IntegratedServicesDigitalNetwork(ISDN);Supplementaryserviceinteractions;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part3:TestSuiteStructureandTestPurposes(TSS&TP)specificationfortheuser".[4]ETSIEN300196-1:"IntegratedServicesDigitalNetwork(ISDN);Genericfunctionalprotocolforthesupportofsupplementaryservices;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part1:Protocolspecification".[5]ISO/IEC9646-1:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[6]ISO/IEC9646-2:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part2:AbstractTestSuitespecification".[7]ISO/IEC9646-3:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part3:TheTreeandTabularCombinedNotation(TTCN)".[8]ISO/IEC9646-4:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part4:Testrealization".[9]ISO/IEC9646-5:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part5:Requirementsontestlaboratoriesandclientsfortheconformanceassessmentprocess".[10]ITU-TRecommendationI.411(1993):"ISDNuser-networkinterfaces-Referenceconfigurations".SIST EN 300 195-4 V1.2.1:2004
ETSIETSIEN300195-4V1.2.1(2000-11)7[11]CCITTRecommendationX.209(1988):"SpecificationofbasicencodingrulesforAbstractSyntaxNotationOne(ASN.1)".[12]ETSIEN300102-1:"IntegratedServicesDigitalNetwork(ISDN);User-networkinterfacelayer3;Specificationsforbasiccallcontrol".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:AbstractTestSuite(ATS):seeISO/IEC9646-1[5]ImplementationUnderTest(IUT):seeISO/IEC9646-1[5]LowerTester(LT):seeISO/IEC9646-1[5]PointofControlandObservation(PCO):seeISO/IEC9646-1[5]ProtocolImplementationConformanceStatement(PICS):seeISO/IEC9646-1[5]PICSproforma:seeISO/IEC9646-1[5]ProtocolImplementationeXtraInformationforTesting(PIXIT):seeISO/IEC9646-1[5]PIXITproforma:seeISO/IEC9646-1[5]SystemUnderTest(SUT):seeISO/IEC9646-1[5]UpperTester(UT):seeISO/IEC9646-1[5]3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ASPAbstractServicePrimitiveATMAbstractTestMethodATSAbstractTestSuiteBERBasicEncodingRulesExTSExecutableTestSuiteFIEFacilityInformationElementIUTImplementationUnderTestLTLowerTesterMOTMeansOfTestingPCOPointofControlandObservationPCTRProtocolConformanceTestReportPDUProtocolDataUnitPICSProtocolImplementationConformanceStatementPIXITProtocolImplementationeXtraInformationforTestingSUTSystemUnderTestTCPTestCo-ordinationProceduresTPTestPurposeTTCNTreeandTabularCombinedNotationUTUpperTesterSIST EN 300 195-4 V1.2.1:2004
ETSIETSIEN300195-4V1.2.1(2000-11)84AbstractTestMethod(ATM)TheremotetestmethodisappliedforthesupplementaryserviceinteractionsuserATS.ThePointofControlandObservation(PCO)residesattheserviceaccesspointbetweenlayers2and3.ThisPCOisnamed"L"(forLower).TheLPCOisusedtocontrolandobservethebehaviouroftheImplementationUnderTest(IUT)andtestcaseverdictsareassigneddependingonthebehaviourobservedatthisPCO.TesterSUTLTIUTPCOLayer2Layer2Layer1Layer1ServiceproviderFigure1:RemotetestmethodISO/IEC9646-2[6]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 195-4 V1.2.1:2004
ETSIETSIEN300195-4V1.2.1(2000-11)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.Intable1,theASN.1typeBIT7OR15isdefinedasbeingoftypeBITSTRINGwithasizeconstraintattachedtoit.ThesizeisdeterminedbythevalueofCR_LENGTH,atestsuiteparameter.Itcanhavethevalueofeither7or15.ThetypeBIT7OR15isusedinthestructuredtypeCR,fieldcr_rallowingthistypetorepresentaBasicAccessoraPrimaryRateAccesscallreference.Byusingthistypedefinitionthefieldcr_risalwaystypecompatiblewithvaluesoftypeBITSTRING(SIZE(7))andBITSTRING(SIZE(15)).AnotherapproachtosolvethistypeproblemwouldbetodefinethetypeBIT7OR15asBITSTRING(SIZE(7|15)).Thistypehasasmalldisadvantagecomparedwiththepreviousone.Itisimpossible,inrun-time,todeterminetheactuallengthofanyinstanceofthistype.Table1:ASN.1typedefinitionBIT7OR15ASN.1TypeDefinitionTypeName:BIT7OR15Comments:TypeDefinitionBITSTRING(SIZE(CR_LENGTH))Table2showsatypicaluseofASN.1.TheCHIelementwillhavetwodifferenttypedefinitionsdependingonwhetheritrepresentsbasicorprimaryrateaccess.InTTCN,thisneedstobedefinedastwodifferenttypes.InASN.1thiscanbedoneinone,thetypebeingachoiceofeitherBASIC_CHIorPRIMARY_CHI.Thesetwotypesarethen(locally)definedinthesametableandaccordingtothestandard.SIST EN 300 195-4 V1.2.1:2004
ETSIETSIEN300195-4V1.2.1(2000-11)10Table2:ASN.1typedefinitionCHIASN.1TypeDefinitionTypeName:CHIComments:InfoElementChannelIdentificationEN300102-1[12]clause4.5.13TypeDefinitionCHOICE{basicBASIC_CHI,primaryPRIMARY_CHI}--Localtypedefinitions--BASIC_CHI::=SEQUENCE{chi_iCHI_I,--Identifierchi_lBITSTRING(SIZE(8)),--Lengthchi_e3_csBITSTRING(SIZE(8))--Channelselection}PRIMARY_CHI::=SEQUENCE{chi_iCHI_I,--Identifierchi_lBITSTRING(SIZE(8)),--Lengthchi_e3_p1BITSTRING(SIZE(4)),--FirstnibbleofChannelselectionchi_e3_peBITSTRING(SIZE(1)),--Preferred/ExclusiveBitchi_e3_p3BITSTRING(SIZE(3)),--LastthreebitsofChannelselectionchi_e4BITSTRING(SIZE(8)),--Channeltypechi_e5_chlBITSTRING(SIZE(1)),chi_e5_ch2BITSTRING(SIZE(7))--Channelnumber}Table3showsanexampleofhowASN.1canbeusedtomodelunorderedsequences.Table3:ASN.1typedefinitionFIESASN.1TypeDefinitionTypeName:FIESComments:TypeDefinitionSETOFFIEThepossibilitytouseTTCNandASN.1incombinationisused,i.e.referringtoanASN.1typefromaTTCNtype.6.1.1.3ASPtypedefinitions6.1.1.3.1TTCNASPtypedefinitionsTTCNASPtypedefinitionsonlycontainonePDUornoPDUatall.TherelationshipbetweenanASPtypeandaPDUtypeisone-to-one.Thatis,thereexistsoneASPtypedefinitionforeachPDUtypedefinition(ifthatASPtypecontainsaPDU).AllTTCNASPtypedefinitionsareprovidedwithafullidentifier.SomeASPsarenotparameterizedasshownintheexampleintable4.SuchASPsareonlyusedforrequestingorreceivingservicefromthelowerlayer.Table4:TTCNASPtypedefinitionDL_REL_INTTCNASPTypeDefinitionASPNAME:DL_REL_IN(DL_RELEASE_INDICATION)PCOType:SAPComments:ParameterName|ParameterType|CommentsDetailedComments:SIST EN 300 195-4 V1.2.1:2004
ETSIETSIEN300195-4V1.2.1(2000-11)11Table5showsanexampleofaparameterizedASP.AllASPscontainingPDUscontainonlythatPDUandnootherparameters.Table5:TTCNASPtypedefinitionDL_DATA_RQ_ALERTTTCNASPTypeDefinitionASPNAME:DL_DATA_RQ_ALERT(DL_DATA_REQUEST)PCOType:SAPComments:ParameterName|ParameterType|Commentsmun(MessageUnit)|ALERT_PDU|DetailedComments:6.1.1.3.2ASN.1ASPtypedefinitionsTherearenoASN.1ASPtypedefinitionsintheATS.6.1.1.4PDUtypedefinitions6.1.1.4.1TTCNPDUtypedefinitionsTheTTCNPDUtypereflectstheactualdatabeingtransferredorreceived.AllPDUsareembeddedinASPs.IfaspecificPDUtypedefinitioncontainselementsdefinedintermsofapre-definedtype,thatelementhasarestrictionattachedtoit.6.1.1.4.2ASN.1PDUtypedefinitionsTherearenoASN.1PDUtypedefinitionsintheATS.6.1.2TestsuiteconstantsNotestsuiteconstantsareusedordefinedinthisATS.6.1.3TestsuiteparametersEachtestsuiteparameterisdefinedintermsofapredefinedtypeorareferencedtype.Areferencedtypeisusedwhenitisnecessarytoattachrestrictionstothesetypedefinitions(itisnotallowedtoincluderestrictionsdirectlyinthetestsuiteparametertable).Thereferencedtypecanhavealengthorvaluerestrictionattachedtoitinitsdeclarationtable.6.1.4Variables6.1.4.1TestsuitevariablesNotestsuitevariablesareusedordefinedinthisATS.6.1.4.2TestcasevariablesEachtestcasevariableisdefinedintermsofapredefinedtypeorareferencedtype.Areferencedtypeisusedwhenitisnecessarytoattachrestrictionstothesetypedefinitions(itisnotallowedtoincluderestrictionsdirectlyinthetestcasevariabletable).Thereferencedtypecanhavealengthorvaluerestrictionattachedtoitinitsdeclarationtable.Wheretestcasevariablesareusedinconstraints,theyarepassedasformalparameters.SIST EN 300 195-4 V1.2.1:2004
ETSIETSIEN300195-4V1.2.1(2000-11)126.1.5TestsuiteoperationdefinitionsThedescriptionpartofatestsuiteoperationdefinitionuseseithernaturallanguageormetaC.Table6:TestsuiteoperationdefinitionASSIGN_CHITestSuiteOperationDefinitionOperationName:ASSIGN_CHI(basic,primary:CHI;basic_flag:BOOLEAN)ResultType:CHIComments:ThisoperationisusedtoassignacorrectChannelidentificationinformationelementtoPDUsdependentonthetypeofaccessthatistested.Description{if(basic_flag)returnbasic;elsereturnprimary}Detailedcomments:Thetestsuiteoperationdefinitionshownintable6isusedintheconstraintspartwhenassigninganelementoftypeCHIavalue.Aspreviouslydescribed,theCHItypecanbedefinedintwowaysdependingonwhethertheATSistestingbasicorprimaryrateaccess.ToavoidduplicatetypesandtherebyduplicatetestcasestheCHItypeisdefinedinASN.1.ThisoperationisusedtoassignavaluetoanelementofCHItype.Ittakesthreeparameters:primary:aconstraintoftypeCHIvalidforprimaryrateaccess;basic:aconstraintoftypeCHIvalidforbasicaccess;basic_flag:aBooleanvalue:TRUEifbasicaccessisapplicable,FALSEotherwise.ThisoperationreturnsthecorrectconstraintaccordingtotheBooleanflagbasic_flag.ThatconstraintwillthenbeassignedtothespecificelementoftypeCHI.6.2Constraintspart6.2.1StructuredtypeconstraintdeclarationForeverystructuredtypedefinitionthereexistsoneormorestructuredtypeconstraint.6.2.2ASN.1typeconstraintdeclarationConstraintsofthistypeareusedtoassignthecorrespondingtypeaspecificvalue.TheseconstraintsareusedforthepurposeofmodellingunordereddataorspecifictypesthatcannotbeexpressedinTTCN.AvalueassignedtoanelementoftypeSETOFdiffersdependingonwhetheritisasendorreceiveconstraint.Table7:ASN.1typeconstraintdeclarationfIEs(sendconstraint)ASN.1TypeConstraintDeclarationConstraintName:fIEs(comp:Component)ASN.1Type:FIEDerivationPath:Comments:SendFIEwhichwillcontainonecomponent"comp".Description{informationElementIdentifier'00011100'B,lengthCALC_FIE_LENGTH(comp),extBit'1'B,spareBits'00'B,protocolProfile'10001'B,components{comp}}Detailedcomments:NOTE:Thelastelementintheconstraint,components,isoftypeSETOFComponentwhereComponentisstructureddataofsometype.SIST EN 300 195-4 V1.2.1:2004
ETSIETSIEN300195-4V1.2.1(2000-11)13Iftheconstraintisasendconstraint(seetable7)thevalueforthecomponentelementisstatedas"{comp}"wherecompisanargumentreceivedasaparameter.The"{"and"}"turnsthevalueintoaSETOFvaluewhichiscorrectaccordingtothatelement'
...



