SIST EN 301 003-5 V1.2.1:2004

• Abstract:

  Correct errors in edition 1 of the standard and make other possible modifications based on contributions.

• Status: Published
• Publication Date: 31-Mar-2004
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Apr-2004
• Due Date: 01-Apr-2004
• Completion Date: 01-Apr-2004
• Ref Project: ETSI EN 301 003-5 V1.2.1 (2000-10) - Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Peak cell rate modification by the connection owner; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network

SIST EN 301 003-5 V1.2.1:2004 is the Slovenian adoption of ETSI EN 301 003-5 Version 1.2.1, published by SIST. It specifies the Test Suite Structure and Test Purposes (TSS&TP) for network-side conformance testing of peak cell rate modification by the connection owner in B-ISDN DSS2. It is intended for people defining, selecting, or executing conformance tests for network implementations that claim conformance to EN 301 003-1.

What does SIST EN 301 003-5 V1.2.1:2004 specify?

SIST EN 301 003-5 V1.2.1:2004 specifies the network TSS&TP for implementations at the TB reference point or the coincident SB and TB reference point. In practice, that means it gives the test structure and the test purposes for checking network behaviour around peak cell rate modification, rather than the protocol specification itself.

The document is organized into these main clauses:

• Clause 1 - Scope
• Clause 2 - References
• Clause 3 - Definitions and abbreviations
• Clause 4 - Test Suite Structure (TSS)
• Clause 5 - Test Purposes (TP)
• Clause 6 - Compliance
• Clause 7 - Requirements for a comprehensive testing service

Clause 5 is the core of the document because it lists the test purposes for the network and the expected protocol reactions in normal and error cases.

What are the key requirements of SIST EN 301 003-5 V1.2.1:2004?

The test suite is split by function and by role

Clause 4 structures the tests around signalling procedures at the coincident SB/TB and TB reference points, then divides them into modification procedures at the requesting entity and at the responding entity. This matters because a network test plan must cover both sides of the modification exchange, not just one message flow.

Each test purpose is identified and traceable

Clause 5 explains the TP naming convention and uses identifiers of the form <suite_id>_<group>_<nnn>. The TPs are numbered within each group and linked to the TSS, so test selection can be matched to PICS items in a consistent way.

The TP set is based on observable network behaviour

Clause 5 states that the TPs are generated from analysis of EN 301 003-1 and the PICS specification EN 301 003-2. The test strategy focuses on externally observable behaviour and on situations a real implementation is likely to face, which keeps the test set practical for conformance work.

Requesting-entity behaviour is checked in normal and error paths

Clause 5 covers the requesting entity with valid behaviour, handling of error conditions, and timer expiry. The tests cover actions such as sending MODIFYREQUEST, reacting to MODIFYACKNOWLEDGE, MODIFYREJECT, RELEASE, STATUS, and CONNECTIONAVAILABLE, and handling timer T360 expiry. In practice, this checks that the network reacts correctly when a modification is accepted, rejected, incomplete, or delayed.

Responding-entity behaviour is checked against traffic parameter validity

Clause 5 also covers the responding entity. The tests check whether a MODIFYREQUEST with compatible ATM traffic descriptor parameters is accepted, and whether an incompatible combination causes a MODIFYREJECT with the appropriate cause. That matters because traffic parameter checking is part of whether the network accepts the requested peak cell rate change.

Error handling includes message and information element faults

Clause 5 gives many error-oriented TPs for wrong protocol discriminator values, unused Call Reference values, missing mandatory information elements, malformed or unrecognized information elements, and different information element action indicator outcomes. This is important in practice because conformance is not only about the ideal exchange, but also about how the network handles invalid or unexpected messages.

Compliance is tied to the TP set and ISO/IEC 9646-2

Clause 6 says a compliant ATS must use an appropriate subset of the TSS, keep the naming conventions, preserve the TP-to-PICS relationship, and comply with ISO/IEC 9646-2. It also states that all testable TPs from clause 5 must be included. This gives testers a clear rule for building a conformant abstract test suite.

What terms does SIST EN 301 003-5 V1.2.1:2004 define?

• Abstract Test Method (ATM) - The testing approach used to realize abstract test cases.
• Abstract Test Suite (ATS) - The set of abstract test cases used for conformance testing.
• Implementation Under Test (IUT) - The network implementation being checked against the standard.
• Protocol Implementation Conformance Statement (PICS) - The statement used to select relevant test cases.
• Protocol Implementation eXtra Information for Testing (PIXIT) - Extra implementation-specific information needed for testing.
• Test Purpose (TP) - A statement of what a specific test is intended to verify.
• Peak Cell Rate (PCR) - The traffic characteristic whose modification is the subject of this part.

Who uses SIST EN 301 003-5 V1.2.1:2004?

SIST EN 301 003-5 V1.2.1:2004 is used by conformance test designers, test laboratories, and network vendors working on B-ISDN DSS2 implementations. It also matters to quality teams and procurement teams that need evidence that a network-side implementation can be tested against EN 301 003-1. Clause 7 additionally addresses organizations claiming to provide a comprehensive testing service for network equipment.

What changed in SIST EN 301 003-5 V1.2.1:2004 from the previous edition?

The scope states that this edition corrects errors in edition 1 and makes other possible modifications based on contributions. The version history also shows the earlier publication V1.1.3 and the later V1.2.1 publication.

Which standards are used with SIST EN 301 003-5 V1.2.1:2004?

• ETS 300 406 - Gives the standardization methodology for protocol and profile conformance test specifications.
• EN 300 443-1 - Provides the basic call and bearer control layer 3 specification used for call-state procedures.
• EN 301 003-1 - Gives the protocol specification for peak cell rate modification by the connection owner.
• EN 301 003-2 - Provides the PICS proforma used to select the applicable test cases.
• ITU-T Recommendation I.413 - Defines the B-ISDN user-network interface referenced for the TB and SB/TB reference points.
• ISO/IEC 9646-1 - Supplies the general conformance testing concepts and definitions.
• ISO/IEC 9646-2 - Supplies the abstract test suite specification framework used for compliance.
• ITU-T Recommendation Q.2963.1 - Is the underlying DSS2 connection modification specification that EN 301 003-1 modifies.

The foreword also identifies the related series parts: part 1 protocol specification, part 2 PICS proforma, part 3 TSS&TP for the user, part 4 ATS and PIXIT proforma for the user, and part 6 ATS and PIXIT proforma for the network.

What does the SIST EN 301 003-5 V1.2.1:2004 document contain?

The document contains a TSS figure, a TP naming convention table, and a large TP catalogue for the network side. Clause 5 lays out valid-behaviour cases and error-handling cases for the requesting entity and the responding entity, including message exchanges, call-state handling, and timer expiry. Clause 6 states the compliance conditions for an ATS, and clause 7 gives the minimum remote test method for organizations offering a comprehensive testing service.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Peak cell rate modification by the connection owner; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 301 003-5 Version 1.2.1SIST EN 301 003-5 V1.2.1:2004en01-april-2004SIST EN 301 003-5 V1.2.1:2004SLOVENSKI
STANDARD
ETSIEN301003-5V1.2.1(2000-10)EuropeanStandard(Telecommunicationsseries)BroadbandIntegratedServicesDigitalNetwork(B-ISDN);DigitalSubscriberSignallingSystemNo.two(DSS2)protocol;Connectioncharacteristics;Peakcellratemodificationbytheconnectionowner;Part5:TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetworkSIST EN 301 003-5 V1.2.1:2004

ETSIETSIEN301003-5V1.2.1(2000-10)2ReferenceREN/SPAN-05242-5KeywordsATM,B-ISDN,DSS2,TSS&TPETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:[phone]Fax:[phone]SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88ImportantnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http://www.etsi.orgThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSIdocumentsisavailableathttp://www.etsi.org/tb/status/Ifyoufinderrorsinthepresentdocument,sendyourcommentto:[e-mail]opartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 301 003-5 V1.2.1:2004

ETSIETSIEN301003-5V1.2.1(2000-10)3ContentsIntellectualPropertyRights.4Foreword.41Scope.52References.53Definitionsandabbreviations.63.1Definitions.63.1.1Definitionsrelatedtoconformancetesting.63.1.2DefinitionsrelatedtoEN301003-1.63.2Abbreviations.64TestSuiteStructure(TSS).75TestPurposes(TP).75.1Introduction.75.1.1TPnamingconvention.75.1.2SourceofTPdefinition.85.1.3Teststrategy.85.1.4Testofcallstates.85.2TPsforthePeakcellratemodification,network.85.2.1SignallingproceduresatthecoincidentSB/TBandattheTBreferencepoints.85.2.1.1Modificationproceduresattherequestingentity.85.2.1.1.1Validbehaviour(01).85.2.1.1.2Handlingoferrorsconditions(02).95.2.1.1.3Timers(03).125.2.1.2Modificationproceduresattherespondingentity.125.2.1.2.1Validbehaviour(04).125.2.1.2.2Handlingoferrorconditions(05).136Compliance.177Requirementsforacomprehensivetestingservice.17Bibliography.18History.19SIST EN 301 003-5 V1.2.1:2004

ETSIETSIEN301003-5V1.2.1(2000-10)4IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.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).Thepresentdocumentispart5ofamulti-partstandardcoveringtheDigitalSubscriberSignallingSystemNo.2(DSS2)protocolspecificationfortheB-ISDNPeakcellratemodificationbytheconnectionowner,asidentified:Part1:"Protocolspecification[ITU-TRecommendationQ.2963.1[8](1996),modified]";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:29September2000DateoflatestannouncementofthisEN(doa):31December2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):30June2001DateofwithdrawalofanyconflictingNationalStandard(dow):30June2001SIST EN 301 003-5 V1.2.1:2004

ETSIETSIEN301003-5V1.2.1(2000-10)51ScopeThisfifthpartofEN301003specifiesthenetworkTestSuiteStructureandTestPurposes(TSS&TP)fortheTBreferencepointorcoincidentSBandTBreferencepoint(asdefinedinITU-TRecommendationI.413[[5])ofimplementationsconformingtothestandardsforthesignallinguser-networklayer3specificationforPeakcellratemodificationbytheconnectionowneroftheDigitalSubscriberSignallingSystemNo.2(DSS2)protocolforthepan-EuropeanBroadbandIntegratedServicesDigitalNetwork(B-ISDN),EN301003-1[3].AfurtherpartofthepresentdocumentspecifiestheAbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformabasedonthepresentdocument.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.[1]ETSIETS300406:"MethodsforTestingandSpecification(MTS);Protocolandprofileconformancetestingspecifications;Standardizationmethodology".[2]ETSIEN300443-1(V1.3):"BroadbandIntegratedServicesDigitalNetwork(B-ISDN);DigitalSubscriberSignallingSystemNo.two(DSS2)protocol;B-ISDNuser-networkinterfacelayer3specificationforbasiccall/bearercontrol;Part1:Protocolspecification[ITU-TRecommendationQ.2931(1995),modified]".[3]ETSIEN301003-1(V1.1):"BroadbandIntegratedServicesDigitalNetwork(B-ISDN);DigitalSubscriberSignallingSystemNo.two(DSS2)protocol;Connectioncharacteristics;Peakcellratemodificationbytheconnectionowner;Part1:Protocolspecification[ITU-TRecommendationQ.2963.1(1996),modified]".[4]ETSIEN301003-2(V1.1):"BroadbandIntegratedServicesDigitalNetwork(B-ISDN);DigitalSubscriberSignallingSystemNo.two(DSS2)protocol;Connectioncharacteristics;Peakcellratemodificationbytheconnectionowner;Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecification".[5]ITU-TRecommendationI.413(1993):"B-ISDNuser-networkinterface".[6]ISO/IEC9646-1:"InformationTechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[7]ISO/IEC9646-2:"InformationTechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part2:AbstractTestSuitespecification".[8]ITU-TRecommendationQ.2963.1:"DigitalSubscriberSignallingSystemNo.2-Connectionmodification:Peakcellratemodificationbytheconnectionowner".SIST EN 301 003-5 V1.2.1:2004

ETSIETSIEN301003-5V1.2.1(2000-10)63Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thetermsanddefinitionsgiveninEN301003-1[3]andEN300443-1[2]andthefollowingapply:3.1.1Definitionsrelatedtoconformancetestingabstracttestcase:refertoISO/IEC9646-1[6]AbstractTestMethod(ATM):refertoISO/IEC9646-1[6]AbstractTestSuite(ATS):refertoISO/IEC9646-1[6]ImplementationUnderTest(IUT):refertoISO/IEC9646-1[6]lowertester:refertoISO/IEC9646-1[6]ProtocolImplementationConformanceStatement(PICS):refertoISO/IEC9646-1[6]PICSproforma:refertoISO/IEC9646-1[6]ProtocolImplementationeXtraInformationforTesting(PIXIT):refertoISO/IEC9646-1[6]PIXITproforma:refertoISO/IEC9646-1[6]TestPurpose(TP):refertoISO/IEC9646-1[6]3.1.2DefinitionsrelatedtoEN301003-1network:DSS2protocolentityattheNetworksideoftheuser-networkinterfacewhereaTBreferencepointorcoincidentSBandTBreferencepointappliesnetwork(SB/TB):DSS2protocolentityattheNetworksideoftheuser-networkinterfacewhereacoincidentSBandTBreferencepointappliesnetwork(TB):DSS2protocolentityattheNetworksideoftheuser-networkinterfacewhereaTBreferencepointapplies(useristheprivateISDN)3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ATMAbstractTestMethodATSAbstractTestSuiteB-ISDNBroadbandIntegratedServicesDigitalNetworkCRCallReferenceDSS2DigitalSubscriberSignallingSystemNo.twoIE_AIInformationelementactionindicatorIE_flagInformationelementinstructionindicatorflagIUTImplementationUnderTestN0NulllinkstateN1CallInitiatedlinkstateN10ActivelinkstateN12DisconnectIndicationcallstateN3OutgoingCallProceedinglinkstateN4CallDeliveredlinkstateN6CallPresentlinkstateN7CallReceivedlinkstateSIST EN 301 003-5 V1.2.1:2004

ETSIETSIEN301003-5V1.2.1(2000-10)7N9IncomingCallProceedinglinkstatePCRPeakCellRatePICSProtocolImplementationConformanceStatementPIXITProtocolImplementationeXtraInformationforTestingTPTestPurposeTSSTestSuiteStructure4TestSuiteStructure(TSS)SignallingproceduresatthecoincidentSB/TBandattheTBreferencepointsModificationproceduresattherequestingentity.Validbehaviour.(01)Handlingoferrorconditions.(02)Timers.(03)Modificationproceduresattherespondingentity.Validbehaviour.(04)Handlingoferrorconditions.(05)Figure1:Testsuitestructure5TestPurposes(TP)5.1IntroductionForeachtestrequirementaTPisdefined.5.1.1TPnamingconventionTPsarenumbered,startingat01,withineachgroup.GroupsareorganizedaccordingtotheTSS.Additionalreferencesareaddedtoidentifytheactualtestsuite(seetable1).Table1:TPidentifiernamingconventionschemeIdentifier:__=service+typeofIUT:"MODN"formodification,IUT=Network=groupnumber:twocharacterfieldrepresentingthegroupreferenceaccordingtoTSS=sequentialnumber:(01-99)SIST EN 301 003-5 V1.2.1:2004

ETSIETSIEN301003-5V1.2.1(2000-10)85.1.2SourceofTPdefinitionTheTPsarebasedonEN301003-1[3].5.1.3TeststrategyAsthebasestandardEN301003-1[3]containsnoexplicitrequirementsfortesting,theTPsweregeneratedasaresultofananalysisofthebasestandardandthePICSspecificationEN301003-2[4].TheTPsareonlybasedonconformancerequirementsrelatedtotheexternallyobservablebehaviouroftheIUT,andarelimitedtoconceivablesituationstowhicharealimplementationislikelytobefaced(ETS300406[1]).5.1.4TestofcallstatesManyTPsincludeareferencetotheIUT'sfinalcallstateaftertherealizationoftheTP.InthesecasestheTPincludestherequirementtoensurethattheIUThasenteredthisparticularfinalcallstate.EnsuringthattheIUTisinaparticularcallstateshallberealizedbyfollowingtheproceduresdescribedinclause5.6.11ofEN300443-1[2].Accordingtotheseprocedures,theIUTonreceiptofaSTATUSENQUIRYmessage,shallrespondwithaSTATUSmessageindicating,inthefifthoctetoftheCallstateinformationelement,thecurrentcallstateoftheIUT.ThisexchangeofmessagesisnotmentionedexplicitlyineachTPbutisconsideredtobeimplicitinthereferencetothefinalcallstate.ThiswayofphrasingtheTPshasbeenusedtoavoidover-complicatingthetextandstructureoftheTPsandtoimprovethereadability.5.2TPsforthePeakcellratemodification,networkAllPICSitemsreferredtointhisclauseareasspecifiedinEN301003-2[4]unlessindicatedotherwisebyanothernumberedreference.Unlessspecified:• themessagesindicatedarevalidandcontainatleastthemandatoryinformationelementsandpossiblyoptionalinformationelements;• theinformationelementsindicatedarevalidandcontainatleastthemandatoryparametersandpossiblyoptionalparameters.5.2.1SignallingproceduresatthecoincidentSB/TBandattheTBreferencepointsNOTE:Unlessotherwisespecified,theconnectiondefinedbytherequestedATMtrafficdescriptorisavailableforuse.5.2.1.1ModificationproceduresattherequestingentityTestpurposesforEN301003-1[3]clause9.1.Selection:Theiutsupporttherequirementsforthemodificationrequestingentity.PICS:R2.1.5.2.1.1.1Validbehaviour(01)MODN_01_01EnsurethattheIUTinN10,toindicatethataPCRmodificationhasbeenrequested,-sendsaMODIFYREQUESTmessageandentersN13.MODN_01_02EnsurethattheIUTinN13,onreceiptofaMODIFYACKNOWLEDGEmessageincludingaBroadbandreporttypeinformationelement,withtypeofreportfielddifferentfrom"Modificationconfirmation"-sendsnomessageoroptionallysendaSTATUSmessage(causevalue:100,callstate:10)andentersN10.SIST EN 301 003-5 V1.2.1:2004

ETSIETSIEN301003-5V1.2.1(2000-10)9MODN_01_03EnsurethattheIUTinN13,onreceiptofaMODIFYACKNOWLEDGEmessagewithoutbroadbandreporttypeinformationelement,-sendsnomessageandentersN10.MODN_01_04EnsurethattheIUTinN13,onreceiptofaMODIFYACKNOWLEDGEmessageincludinganemptyBroadbandreporttypeinformationelement,-sendsnomessageandentersN10.MODN_01_05EnsurethattheIUTinN10,havingreceivedaMODIFYACKNOWLEDGEmessage,includingabroadbandreporttypeinformationelementrequestingconfirmation,toindicatethatthemodificationoftheconnectionhasbeenconfirmedbytheremoteuser,-sendsaCONNECTIONAVAILABLEmessageandremainsinN10.MODN_01_06EnsurethattheIUTinN13,onreceiptofaMODIFYREJECTmessage,-sendsnomessageandentersN10.MODN_01_07EnsurethattheIUTinN13,onreceiptofaSTATUSmessage(callstate:10,causevalue:97)withdiagnosticidentifyingoftheMODIFYREQUESTmessage,-sendsnomessageandentersN10.MODN_01_08EnsurethattheIUTinN13,onreceiptofaSTATUSmessage(callstate:10,causevalue:97or101)withoutdiagnosticidentifyingoftheMODIFYREQUESTmessage,-sendsaSTATUSENQUIRYmessageandremainsinN13.MODN_01_09EnsurethattheIUTinN13,(havingsentaSTATUSENQUIRYmessage),onreceiptofaSTATUSmessage(callstate:14),-sendsnomessageandremainsinN13.MODN_01_10EnsurethattheIUTinN13,(havingsentaSTATUSENQUIRYmessage),onreceiptofaSTATUSmessage(callstate:10),-sendsnomessageandentersN10.MODN_01_11EnsurethattheIUTinN13,onreceiptofaRELEASEmessage,-entersN11.MODN_01_12EnsurethattheIUTinN13,onreceiptofaclearingindicationattheremoteinterface,-sendsaRELEASEmessageandentersN12.5.2.1.1.2Handlingoferrorsconditions(02)MODN_02_0
...