ETSI EN 300 195-6 V1.2.1 (2000-11)
Integrated Services Digital Network (ISDN); Supplementary service interactions; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network
Integrated Services Digital Network (ISDN); Supplementary service interactions; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network
REN/SPAN-05138-6
Digitalno omrežje z integriranimi storitvami (ISDN) – Medsebojno vplivanje dopolnilne storitve – Protokol digitalne naročniške signalizacije št. 1 (DSS1) – 6. del: Abstraktni preskušalni niz (ATS) in delna dodatna informacija za preskušanje izvedbe protokola (PIXIT) – Proforma specifikacija za omrežje
General Information
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 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 300 195-6 Version 1.2.1SIST EN 300 195-6 V1.2.1:2005en01-januar-2005SIST EN 300 195-6 V1.2.1:2005SLOVENSKI
STANDARD
SIST EN 300 195-6 V1.2.1:2005
ETSIEN300195-6V1.2.1(2000-11)EuropeanStandard(Telecommunicationsseries)IntegratedServicesDigitalNetwork(ISDN);Supplementaryserviceinteractions;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part6:AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforthenetworkSIST EN 300 195-6 V1.2.1:2005
ETSIETSIEN300195-6V1.2.1(2000-11)2ReferenceREN/SPAN-05138-6KeywordsISDN,DSS1,supplementaryservice,interaction,testing,ATS,PIXIT,networkETSI650RoutedesLuciolesF-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-6 V1.2.1:2005
ETSIETSIEN300195-6V1.2.1(2000-11)3ContentsIntellectualPropertyRights.5Foreword.51Scope.62References.63Definitionsandabbreviations.73.1Definitions.73.2Abbreviations.74AbstractTestMethod(ATM).84.1DescriptionofATMused.84.2ConventionsfortestcomponentsandPCOs.85Untestabletestpurposes.96ATSconventions.106.1Declarationspart.106.1.1Typedefinitions.106.1.1.1Simpletypedefinitions.106.1.1.2Structuredtypedefinitions.106.1.1.2.1TTCNstructuredtypedefinitions.106.1.1.2.2ASN.1structuredtypedefinitions.106.1.1.3ASPtypedefinitions.116.1.1.3.1TTCNASPtypedefinitions.116.1.1.3.2ASN.1ASPtypedefinitions.126.1.1.4PDUtypedefinitions.126.1.1.4.1TTCNPDUtypedefinitions.126.1.1.4.2ASN.1PDUtypedefinitions.126.1.2Testsuiteconstants.126.1.3Testsuiteparameters.126.1.4Variables.136.1.4.1Testsuitevariables.136.1.4.2Testcasevariables.136.1.5Testsuiteoperationdefinitions.136.2Constraintspart.136.2.1Structuredtypeconstraintdeclaration.136.2.2ASN.1typeconstraintdeclaration.136.2.2.1Specificationofencodingrules.146.2.3ASPtypeconstraintdeclaration.156.2.3.1ASN.1ASPtypeconstraintdeclaration.156.2.3.2TTCNASPtypeconstraintdeclaration.156.2.4PDUtypeconstraintdeclaration.166.2.4.1ASN.1PDUtypeconstraintdeclaration.166.2.4.2TTCNPDUtypeconstraintdeclaration.166.2.5Chainingofconstraints.166.2.5.1Staticchaining.166.2.5.2Dynamicchaining.166.2.6Derivedconstraints.166.2.7Parameterizedconstraints.166.2.8Valueassignment.166.2.8.1Specificvalues.166.2.8.2Matchingvalues.176.3Dynamicpart.176.3.1Testcases.176.3.2Teststeps.176.3.3Defaults.17SIST EN 300 195-6 V1.2.1:2005
ETSIETSIEN300195-6V1.2.1(2000-11)47ATStoTPmap.178PCTRconformance.179PIXITconformance.1810ATSconformance.18AnnexA(normative):ProtocolConformanceTestReport(PCTR)proforma.19A.1Identificationsummary.19A.1.1Protocolconformancetestreport.19A.1.2IUTidentification.19A.1.3Testingenvironment.20A.1.4Limitsandreservations.20A.1.5Comments.20A.2IUTconformancestatus.20A.3Staticconformancesummary.20A.4Dynamicconformancesummary.21A.5Staticconformancereviewreport.21A.6Testcampaignreport.21A.7Observations.26AnnexB(normative):PartialPIXITproforma.27B.1Identificationsummary.27B.2Abstracttestsuitesummary.27B.3Testlaboratory.27B.4Client(ofthetestlaboratory).28B.5SystemUnderTest(SUT).28B.6Protocolinformation.29B.6.1Protocolidentification.29B.6.2Parametervalues.29B.6.3Codingsofinformationelements.30B.6.4CalledpartynumberandCallingpartynumbervalues.31B.6.5ActionsrequiredtoconfiguretheIUT.32B.6.6OptionssupportedbytheIUT.32B.6.7Timervalues.33B.7BasiccallPIXITitems.33B.7.1Parametervalues-informationelementcodings.33AnnexC(normative):AbstractTestSuite(ATS).35C.1TheTTCNGraphicalform(TTCN.GR).35C.2TheTTCNMachineProcessableform(TTCN.MP).35AnnexD(informative):GeneralstructureofATS.36History.37SIST EN 300 195-6 V1.2.1:2005
ETSIETSIEN300195-6V1.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).Thepresentdocumentispart6ofamulti-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-6 V1.2.1:2005
ETSIETSIEN300195-6V1.2.1(2000-11)61ScopeThepresentdocumentspecifiestheAbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformafortheNetworksideoftheTreferencepointorcoincidentSandTreferencepoint(asdefinedinITU-TRecommendationI.411[10])ofimplementationsconformingtothestagethreestandardforthesupplementaryserviceinteractionsforthepan-EuropeanIntegratedServicesDigitalNetwork(ISDN)bymeansoftheDigitalSubscriberSignallingSystemNo.one(DSS1)protocol,EN300195-1[1].EN300195-5[3]specifiestheTestSuiteStructureandTestPurposes(TSS&TP)relatedtothisATSandpartialPIXITproformaspecification.OtherpartsspecifytheTSS&TPandtheATSandpartialPIXITproformafortheUsersideoftheTreferencepointorcoincidentSandTreferencepointofimplementationsconformingtoEN300195-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-5:"IntegratedServicesDigitalNetwork(ISDN);Supplementaryserviceinteractions;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part5:TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetwork".[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-referencesconfigurations".SIST EN 300 195-6 V1.2.1:2005
ETSIETSIEN300195-6V1.2.1(2000-11)7[11]ITU-TRecommendationX.209(1988):"SpecificationofbasicencodingrulesforAbstractSyntaxNotationOne(ASN.1)".[12]ETSIEN300195-4:"IntegratedServicesDigitalNetwork(ISDN);Supplementaryserviceinteractions;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part4:AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationfortheuser".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:ASPAbstractServicePrimitiveATMAbstractTestMethodATSAbstractTestSuiteBERBasicEncodingRulesExTSExecutableTestSuiteFIEFacilityInformationElementIUTImplementationUnderTestLTLowerTesterMOTMeansOfTestingPCOPointofControlandObservationPCTRProtocolConformanceTestReportPDUProtocolDataUnitPICSProtocolImplementationConformanceStatementPIXITProtocolImplementationeXtraInformationforTestingSUTSystemUnderTestTPTestPurposeTTCNTreeandTabularCombinedNotationUTUpperTesterSIST EN 300 195-6 V1.2.1:2005
ETSIETSIEN300195-6V1.2.1(2000-11)84AbstractTestMethod(ATM)4.1DescriptionofATMusedTherequirementfortestingthenetworkIUTistofocusonthebehaviourofthenetworkIUTattheuser-networkinterfacewhereaTreferencepointorcoincidentSandTreferencepointapplies.ThustheIUTisthenetworkDSS1protocolentityataparticularuser-networkinterfaceandisnotthewholenetwork.ItispossibletospecifyanATSbasedonaSingleparty(remote)testmethodforsuchanIUT.However,itisconsideredthatanATSbasedonsuchanapproachisoflimiteduseastheonlywaytospecifyIUTgeneratedPDUsistousethe"implicitsend"statement.ManyusersofsuchanATSwouldreplacethe"implicitsend"statementswithdescriptionsofthebehaviouratotherinterfaces.AnATSbasedonamulti-partytestmethodisconsideredtobemoreusefulinthatitisclosertohowarealtestsuitewouldbeconstructed.Suchatestmethodspecifiesbehaviouratmultiplenetworkinterfaces.Oneveryimportantlimitationhereisthattestsarefocussedononeparticularinterface.ThusthetestsystemismadeuponeMainTestComponent(MTC)andoneormoreParallelTestComponents(PTC),seefigure1.4.2ConventionsfortestcomponentsandPCOsMasterpartSlavepartMTCAPTC2CPA2PTC1CPA1L0PCOL1PCOL2PCOIUTNETWORKFigure1:Multi-partytestmethodInamaster/slavearrangement,theMTCisconsideredtobethemasterwhilethePTCsaretheslaves.The"slave"testersareonlyanexplicitdescriptionofhowtodealwiththe"other"interfacesduringthetestingprocess,i.e."howtomaketheIUTsendtherequiredmessage".SIST EN 300 195-6 V1.2.1:2005
ETSIETSIEN300195-6V1.2.1(2000-11)9Thismeans,inparticular,thattheverdictwillonlybeassignedfromtheprotocolaspectsobservedontheinterfaceundertest(i.e.bythe"master"tester),asitwouldbeobservedbyaterminalconnectedtothisinterface.Afailureinthecorrelationbetweentheprotocolatthedifferentinterfacestowhichthedifferenttestersareconnected,i.e.inthemechanismofthefunctionalserviceitself,willnotcauseaFAILverdict.Forinstance,iftheIUTfailstosendamessageonthetestedinterfaceafteranotherinterfacehasreceivedtheproperstimulus,theverdictwillbeINCONCLUSIVE.TheMTCMTCAhastwofunctionsinthisconfiguration.Firstly,ithastheMTCfunctionofcontrollingtheoneormorePTCs.ThusitisresponsibleforstartingthePTCsandafterwardscoordinatesactivitiesbyexchangingCoordinationMessages(CM)withthePTCs.SecondlyitisresponsibleforthebehaviouroftheLowerTester(LT)atPCOL0.Acombinationoftheremoteandmulti-partytestmethodsisapplied.Ascanbeseenfromfigure1,severalPCOsareused.AllPCOsresideattheserviceaccesspointsbetweenlayers2and3.MTCSUTPTC1,2Layer3Layer2Layer1L0IUTL1,2Layer3Layer2Layer1ServiceproviderFigure2:Combinationoftheremoteandmulti-partytestmethodsTheMTCPCOisnamed"L0"("L"forLower).TheL0PCOisusedtocontrolandobservethebehaviouroftheIUTandtestcaseverdictsareassigneddependingonthebehaviourobservedatthisPCO.ThePTCsPTC1,PTC2etc.usePCOsL1,L2etc.ThesePCOsareusedtocontroland,inalimitedway,observethebehaviourofthenetworkequipmentatinterfacesotherthantheoneundertest.NoverdictsareassignedatthesePCOs.Asstatedinapreviousparagraph,thenon-receiptofnetworkgeneratedmessagesatL0,whicharestimulatedbyeventsattheL1,L2etc.,willresultinINCONCLUSIVEratherthanFAILverdictsbeingassigned.PTC2isonlyactivatedinasmallsetoftestcasesthattestthehandlingoftwocallsatonetime.IntestcaseswhichverifythattheIUTrejectsinvalidorunacceptableSETUPmessages,noPTCisactivatedatall,astheserejectionproceduresareconsideredlocaltotheaccessbetweenIUTandMTC.ThecapabilityoftheIUTtosendINFORMATIONandPROGRESSmessagesistestedindifferentcallstates.Implicitsendeventshavetobeusedinthissmallsetoftestcases,asthesendingofthosemessagescannotbetriggeredviaaPTC.SeparatePIXITquestionsareaskedforeachcallstate,ifandhowitispossibleforthetestoperatortocausethesendingofthemessages.5UntestabletestpurposesThefollowingtestpurposeshavebeenfoundtobeuntestable:SSI_N50_01_001,SSI_N50_01_003,andSSI_N50_01_005DuetothefactthattheserviceOCB-FcannotbeactivatedaftertheCCBSservicehasbeenactivated.SIST EN 300 195-6 V1.2.1:2005
ETSIETSIEN300195-6V1.2.1(2000-11)106ATSconventionsThisclauseisstructuredsimilarlytothestructureofaTTCNATS.However,thenamesofthesubclausesarearrangedinawaymoresuitabletothepresentdocument.6.1Declarationspart6.1.1Typedefinitions6.1.1.1SimpletypedefinitionsWhereappropriate,simpletypeshavealength,avaluelistorarangerestrictionattached.Simpletypesdefinedasbeingofsomestringtype(e.g.BITSTRING,OCTETSTRING),havealengthrestrictionoravaluelistattached.Simpletypes,definedasbeingofINTEGERtype,haveavaluelistorarangerestrictionattached.6.1.1.2Structuredtypedefinitions6.1.1.2.1TTCNstructuredtypedefinitionsAllstructuredtypedefinitionsareprovidedwithafullname.Allelementsineverystructuredtypedefinition,definedasbeingofsomestringtype(e.g.BITSTRING,OCTETSTRING),havealengthrestrictionattached.Ifanelementinastructuredtypedefinitionisdefinedasbeingofareferencedtype,the(possible)restrictionisdefinedinthatreferencedtype.Forinformationelementstheidentifier,whichisuniqueforeachelement,hasitstypedefinedasasimpletypewherethevaluelistisrestrictedtothesinglevaluewhichistheidentifieritself.ThishastheadvantagethatitallowsatestsystemderivedfromthisATStoeasilyidentifyinformationelementsembeddedinmessages.AnATSwhereinformationelementidentifiersarerepresentedasunrestrictedtypescanpresentdifficultiesforaderivedtestsysteminthecasewhereitneedstofindoneinformationelementembeddedinanumberofothersandtheconstraintsfortheotherelementshavetheany-or-omitvalue.Insuchacasethetestsystemcannoteasilyfindthebeginningofeachinformationelement.6.1.1.2.2ASN.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)).AnotherapproachtosolvethisproblemwouldbetodefinethetypeBIT7OR15asBITSTRING(SIZE(7|15)).Thistypehasasmalldisadvantagecomparedwiththepreviousone.Itisimpossible,inrun-time,todeterminetheactuallengthofanyinstanceofthistype.SIST EN 300 195-6 V1.2.1:2005
ETSIETSIEN300195-6V1.2.1(2000-11)11Table1:ASN.1typedefinitionBIT7OR15ASN.1TypeDefinitionTypeName:BIT7OR15Comments:TypeDefinitionBITSTRING(SIZE(CR_LENGTH))Table2showsatypicaluseofASN.1.TheCHIelementwillhavetwodifferenttypedefinitionsdependingonwhetheritrepresentsbasicorprimaryrateaccess.InTTCN,thisneedstobedefinedastwodifferenttypes.InASN.1thiscanbedoneinone,thetypebeingachoiceofeitherBASIC_CHIorPRIMARY_CHI.Thesetwotypesarethen(locally)definedinthesametable.Table2:ASN.1typedefinitionCHIASN.1TypeDefinitionTypeName:CHIComments:InfoElementChannelIdentificationETS300102-1clause4.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,thereexistsoneASPty
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.