SIST EN 300 196-2 V1.3.2:2004

• Abstract:

  PICS for REN/SPS-05135-1

• 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 300 196-2 V1.3.2 (2001-06) - Integrated Services Digital Network (ISDN); Generic functional protocol for the support of supplementary services; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification

SIST EN 300 196-2 V1.3.2:2004 is the Slovenian adoption of ETSI EN 300 196-2 Version 1.3.2. It specifies the Protocol Implementation Conformance Statement (PICS) proforma for the Integrated Services Digital Network (ISDN) generic functional protocol that supports supplementary services over the Digital Subscriber Signalling System No. one (DSS1). Suppliers use it to declare which functions, messages, parameters, timers and call states are implemented in a user or network product.

What does SIST EN 300 196-2 V1.3.2:2004 specify?

SIST EN 300 196-2 V1.3.2:2004 specifies the PICS proforma for the ISDN DSS1 generic functional protocol for supplementary services. In practice, it is the questionnaire a supplier completes to state what an implementation supports, so that conformity can be reviewed in a structured way.

The document applies to the pan-European ISDN at the T reference point or coincident S and T reference point. It is tied to EN 300 196-1, and its completion rules follow ISO/IEC 9646-7 guidance for implementation conformance statements.

The document is organized into:

• Clause 1 - Scope
• Clause 2 - References
• Clause 3 - Definitions, symbols and abbreviations
• Clause 4 - Conformance
• Annex A - normative PICS proforma
• Annex B - informative bibliography

What are the key requirements of SIST EN 300 196-2 V1.3.2:2004?

SIST EN 300 196-2 V1.3.2:2004 is a proforma standard, so its main requirements are about how the PICS is completed and what information it must contain.

• A conforming PICS must be technically equivalent to Annex A and must keep the same numbering and order of items. This matters because test tools and reviewers rely on a stable structure.
• The completed PICS must describe an implementation that claims conformance to EN 300 196-1, and it must identify both the supplier and the implementation. This lets a buyer or test lab tie the statement to a specific product build.
• The global statement of conformance asks whether all mandatory capabilities are implemented. If the answer is No, the completed PICS must identify the unsupported mandatory capabilities and explain why. That is the key screen for static conformance review.
• Annex A separates the answer set into roles and implementation types. The User section is for user implementations, including private network implementations; the Network section is for network implementations; the Roles section applies to all implementations.
• The capability tables ask about major capabilities such as separate-message and common-information-element control of supplementary services, bearer-related and bearer-independent procedures, notification procedures, channel reservation, supplementary services management, and generic status request. These answers tell the reader which service models the implementation supports.
• The message and parameter tables check support for protocol data units such as FACILITY, HOLD, RETRIEVE, SETUP, CONNECT, RELEASE and related messages, together with fields such as protocol discriminator, call reference, message type, facility, notification indicator, channel identification, cause, connected number and display. In practice, this is what a test house uses to select protocol cases and verify signaling behavior.
• The timer and call-state tables cover user and network auxiliary states and protocol timers such as T-HOLD, T-RETRIEVE, T303, T308, T309, T310, T313, T322 and T-STATUS. These items matter because they define state-dependent behavior during supplementary-service procedures.

What terms does SIST EN 300 196-2 V1.3.2:2004 define?

• Protocol Implementation Conformance Statement (PICS) - a supplier statement that lists which capabilities of an OSI implementation are implemented for a given protocol.
• PICS proforma - the questionnaire form that becomes a PICS after it is completed for a specific implementation.
• Implementation Under Test (IUT) - the implementation being assessed.
• System Under Test (SUT) - the system that contains the IUT.
• System Conformance Statement (SCS) - a statement that summarizes which OSI standards are implemented and claimed.
• Static conformance review - a review that compares the PICS with the standard’s static conformance requirements.
• DSS1 - Digital Subscriber Signalling System No. one, the signaling protocol used here for ISDN supplementary services.

Who uses SIST EN 300 196-2 V1.3.2:2004?

SIST EN 300 196-2 V1.3.2:2004 is used by suppliers of ISDN DSS1 implementations, telecom equipment vendors, test laboratories, and network operators. It is also useful for quality managers and buyers who need a structured statement of supported functions before procurement, integration or acceptance testing.

What changed in SIST EN 300 196-2 V1.3.2:2004 from the previous edition?

SIST EN 300 196-2 V1.3.2:2004 is the Version 1.3.2 edition. The document history shows an earlier Version 1.3.1 and the later Version 1.3.2 publication sequence.

Which standards are used with SIST EN 300 196-2 V1.3.2:2004?

Standard	What it contributes
ETSI EN 300 403-1	Basic call control protocol reference used in the message and parameter tables
ETSI EN 300 196-1	The protocol specification that this PICS proforma supports
ISO/IEC 9646-1	General concepts for OSI conformance testing
ISO/IEC 9646-7	Rules for implementation conformance statements
ITU-T Recommendation I.411	ISDN user-network reference configurations

What does the SIST EN 300 196-2 V1.3.2:2004 document contain?

Annex A is the practical core of the document. It contains editable tables for identification data, the global conformance statement, role selection, major and subsidiary capabilities, received and transmitted messages, PDU parameters, timers, and auxiliary call states.

The tables are split between user and network implementations, with conditional items marked by support status and references to the related protocol clauses. That layout helps a test lab or procurement team read the implementation profile quickly and use it for static review, test selection and conformance comparison.

Annex A also includes instructions for completing the PICS, so the completed document can be used as a formal supplier declaration rather than a free-text description.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.URIRUPDVSHFLILNDFLMHIntegrated Services Digital Network (ISDN); Generic functional protocol for the support of supplementary services; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 300 196-2 Version 1.3.2SIST EN 300 196-2 V1.3.2:2004en01-april-2004SIST EN 300 196-2 V1.3.2:2004SLOVENSKI
STANDARD
ETSIEN300196-2V1.3.2(2001-06)EuropeanStandard(Telecommunicationsseries)IntegratedServicesDigitalNetwork(ISDN);Genericfunctionalprotocolforthesupportofsupplementaryservices;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecificationSIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)2ReferenceREN/SPAN-05135-2KeywordsDSS1,functional,generic,ISDN,PICS,supplementaryserviceETSI650RoutedesLuciolesF-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.©EuropeanTelecommunicationsStandardsInstitute2001.Allrightsreserved.SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)3ContentsIntellectualPropertyRights.4Foreword.41Scope.52References.53Definitions,symbolsandabbreviations.63.1Definitions.63.2Symbols.63.3Abbreviations.64Conformance.7AnnexA(normative):PICSproformaforEN300196-1.8A.1InstructionsforcompletingthePICSproforma.8A.1.1Identificationoftheimplementation.8A.1.2Globalstatementofconformance.8A.1.3ExplanationofPICSproformaclauses.8A.1.4Symbols,abbreviationsandterms.9A.2Identificationoftheimplementation.9A.2.1ImplementationUnderTest(IUT)identification.9A.2.2SystemUnderTest(SUT)identification.9A.2.3Productsupplier.10A.2.4Client.10A.2.5PICScontactperson.11A.3PICS/SCSrelationship.11A.4Identificationoftheprotocol.11A.5Globalstatementofconformance.12A.6Roles.12A.7User.12A.7.1Majorcapabilities.12A.7.2Subsidiarycapabilities.14A.7.3Protocoldataunits.15A.7.4Protocoldataunitparameters.17A.7.4.1Protocoldataunitparametersreceived.17A.7.4.2Protocoldataunitparameterstransmitted.28A.7.5Timers.38A.7.6Callstates.39A.8Network.39A.8.1Majorcapabilities.39A.8.2Subsidiarycapabilities.41A.8.3Protocoldataunits.42A.8.4Protocoldataunitparameters.44A.8.4.1Protocoldataunitparametersreceived.44A.8.4.2Protocoldataunitparameterstransmitted.54A.8.5Timers.65A.8.6Callstates.66AnnexB(informative):Bibliography.67History.68SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)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).Thepresentdocumentispart2ofamulti-partdeliverablecoveringtheIntegratedServicesDigitalNetwork(ISDN);Genericfunctionalprotocolforthesupportofsupplementaryservices;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol,asidentifiedbelow: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:8June2001DateoflatestannouncementofthisEN(doa):30September2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31March2002DateofwithdrawalofanyconflictingNationalStandard(dow):31March2002SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)51ScopeThepresentdocumentisapplicabletothegenericfunctionalprotocolforthesupportofsupplementaryservicesforthepan-EuropeanIntegratedServicesDigitalNetwork(ISDN)asprovidedbyEuropeanpublictelecommunicationsoperatorsattheTreferencepointorcoincidentSandTreferencepoint(asdefinedinITU-TRecommendationI.411[6])bymeansoftheDigitalSubscriberSignallingSystemNo.one(DSS1)protocol.ThepresentdocumentprovidestheProtocolImplementationConformanceStatement(PICS)proformafortheISDNDSS1genericfunctionalprotocolforthesupportofsupplementaryservicesasspecifiedinEN300196-1[2]incompliancewiththerelevantrequirementsandinaccordancewiththerelevantguidancegiveninISO/IEC9646-7[5].ThesupplierofaprotocolimplementationwhichisclaimedtoconformtoEN300196-1[2]isrequiredtocompleteacopyofthePICSproformaprovidedinannexAofthepresentdocumentandisrequiredtoprovidetheinformationnecessarytoidentifyboththesupplierandtheimplementation.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.[1]ETSIEN300403-1:"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Signallingnetworklayerforcircuit-modebasiccallcontrol;Part1:Protocolspecification[ITU-TRecommendationQ.931(1993),modified]".[2]ETSIEN300196-1(V1.3.2):"IntegratedServicesDigitalNetwork(ISDN);Genericfunctionalprotocolforthesupportofsupplementaryservices;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part1:Protocolspecification".[3]Void[4]ISO/IEC9646-1:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[5]ISO/IEC9646-7:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part7:ImplementationConformanceStatements".[6]ITU-TRecommendationI.411:"ISDNuser-networkinterfaces-Referenceconfigurations".SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)63Definitions,symbolsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsgiveninEN300196-1[2]andthefollowingapply:ProtocolImplementationConformanceStatement(PICS):statementmadebythesupplierofanOpenSystemsInterconnection(OSI)implementationorsystem,statingwhichcapabilitieshavebeenimplementedforagivenOSIprotocol(seeISO/IEC9646-1)PICSproforma:document,intheformofaquestionnaire,designedbytheprotocolspecifierorconformancetestsuitespecifier,which,whencompletedforanOSIimplementationorsystembecomesthePICS(seeISO/IEC9646-1)staticconformancereview:reviewoftheextenttowhichthestaticconformancerequirementsaremetbytheIUT,accomplishedbycomparingthePICSwiththestaticconformancerequirementsexpressedintherelevantstandard(s)(seeISO/IEC9646-1)3.2SymbolsForthepurposesofthepresentdocument,thefollowingsymbolsapply:andBoolean"and"CConditionalrequirement(tobeobservediftherelevantconditionsapply)MMandatoryrequirement(tobeobservedinallcases)N/Anotapplicable,notsupportedortheconditionsforstatusarenotmeetNonotsupportednotBoolean"not"OOption(maybeselectedtosuittheimplementation,providedthatanyrequirementsapplicabletotheoptionareobserved)orBoolean"or"Yessupported3.3AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:DSS1DigitalSubscriberSignallingSystemNo.oneIERInformationElementsReceivedIETInformationElementsTransmittedISDNIntegratedServicesDigitalNetworkIUTImplementationUnderTestMCMajorCapabilitiesMRMessagesReceivedMTMessagesTransmittedOSIOpenSystemsInterconnectionPParametersPICSProtocolImplementationConformanceStatementRRoleSCSubsidiaryCapabilitiesSCSSystemConformanceStatementSUTSystemUnderTestTMprefixforindexesnumbersforthetimersgroupSIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)74ConformanceAPICSproformawhichconformstothisPICSproformaspecificationshallbetechnicallyequivalenttoannexA,andshallpreservethenumberingandorderingoftheitemsinannexA.APICSwhichconformstothisPICSproformaspecificationshall:a)describeanimplementationwhichclaimstoconformtoEN300196-1[2];b)beaconformingICSproformawhichhasbeencompletedinaccordancewiththeinstructionsforcompletiongiveninclauseA.1;c)includetheinformationnecessarytouniquelyidentifyboththesupplierandtheimplementation.SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)8AnnexA(normative):PICSproformaforEN300196-1Notwithstandingtheprovisionsofthecopyrightclauserelatedtothetextofthepresentdocument,ETSIgrantsthatusersofthepresentdocumentmayfreelyreproducethePICSproformainthisannexsothatitcanbeusedforitsintendedpurposesandmayfurtherpublishthecompletedPICS.A.1InstructionsforcompletingthePICSproformaA.1.1IdentificationoftheimplementationIdentificationoftheImplementationUnderTest(IUT)andthesysteminwhichitresides(theSystemUnderTest(SUT))shouldbefilledinsoastoprovideasmuchdetailaspossibleregardingversionnumbersandconfigurationoptions.Theproductsupplierinformationandclientinformationshouldbothbefillediniftheyaredifferent.ApersonwhocananswerqueriesregardinginformationsuppliedinthePICSshouldbenamedasthecontactperson.TheSystemConformanceStatement(SCS)asdefinedinISO/IEC9646-1isadocumentsuppliedbytheclientorproductsupplierthatsummarizeswhichOSIstandardsareimplementedandtowhichconformanceisclaimed.ThePICS/SCSclauseshoulddescribetherelationshipofthePICStotheSCS.A.1.2GlobalstatementofconformanceIftheanswertothestatementinthisclauseis"Yes",allsubsequentclausesshouldbecompletedtofacilitateselectionoftestcasesforoptionalfunctions.Iftheanswertothestatementinthisclauseis"No",allsubsequentclausesshouldbecompleted,andallnon-supportedmandatorycapabilitiesshouldbeidentifiedandexplained.Explanationsmaybeenteredinthecommentsfieldatthebottomofeachtableoronattachedpages.A.1.3ExplanationofPICSproformaclausesThePICSproformacontainsaRolesclauseandthereafterispresentedintwoparts(foruserandnetwork)withthefollowingclauses,asrequired:-majorcapabilities;-subsidiarycapabilities;-protocoldataunitsupport;-protocoldataunitparameters;-timers;-callstates.TheUserclauseshallonlybecompletedforuserimplementations(includingprivatenetworkimplementations)whiletheNetworkclauseshallonlybecompletedfornetworkimplementations.TheRolesclauseshallbecompletedforallimplementations.TherelationshipbetweenthisPICSproformaandotherrelatedPICSproforma(e.g.thebasiccallPICSproforma)isexpressedintherequirementslistcontainedinannexB.Thisprovidestheadditionalrestrictionsplacedontherelatedproforma(differentconditions,differentstatus,etc.).SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)9A.1.4Symbols,abbreviationsandtermsThePICSproformacontainedinthisannexiscomprisedofinformationintabularforminaccordancewiththeguidelinespresentedinISO/IEC9646-7.Thereferencecolumncontainedinthetablesgivesreferencetotheappropriatepart(s)ofEN300196-1(unlessanothernumberedreferenceisexplicitlyindicated)describingtheparticularitem.Note,however,thatareferencemerelyindicatestheplacewherethecoreofadescriptionofanitemcanbefound.AnyadditionalinformationcontainedinEN300196-1(oranyotherpossiblyusedreference)hastobetakenintoaccountwhenmakingastatementabouttheconformanceofthatparticularitem.Thefollowingcommonnotations,definedinISO/IEC9646-7,areusedforthestatuscolumn:MmandatoryOoptionalN/AnotapplicableO.mutuallyexclusiveorselectableoptionsfromasetThefollowingcommonnotations,definedinISO/IEC9646-7,areusedforthesupportcolumn:Ysupported/implementedNnotsupported/notimplementedA.2IdentificationoftheimplementationA.2.1ImplementationUnderTest(IUT)identificationIUTname:.IUTversion:.A.2.2SystemUnderTest(SUT)identificationSUTname:.Hardwareconfiguration:.Operatingsystem:.SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)10A.2.3ProductsupplierName:.Address:.Telephonenumber:.Facsimilenumber:.Additionalinformation:.A.2.4ClientName:.Address:.Telephonenumber:.Facsimilenumber:.Additionalinformation:.SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)11A.2.5PICScontactpersonName:.Address:.Telephonenumber:.Facsimilenumber:.Additionalinformation:.A.3PICS/SCSrelationshipProvidetherelationshipofthePICSwiththeSCSforthesystem:.A.4IdentificationoftheprotocolThisPICSproformaappliestothefollowingstandard:ETSIEN300196-1:"IntegratedServicesDigitalNetwork(ISDN);Genericfunctionalprotocolforthesupportofsupplementaryservices;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part1:Protocolspecification".SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)12A.5GlobalstatementofconformanceAreallmandatorycapabilitiesimplemented?(Yes/No).NOTE:Answering"No"tothisquestionindicatesnon-conformancetotheprotocolspecification.Non-supportedmandatorycapabilitiesaretobeidentifiedinthePICS,withanexplanationofwhytheimplementationisnon-conforming.Explanationmaybeenteredinthecommentsfieldatthebottomofeachtableoronattachedpages.Inthetabulationswhichfollow,allreferencesaretoEN300196-1:unlessanothernumberedreferenceisexplicitlyindicated.A.6RolesTableA.1:TypeofimplementationItemMajorrole:Doestheimplementation.ConditionsforstatusStatusReferenceSupportTypeofimplementationR1notusedR2.1supportuserrequirements?O.17,8,9,10[]Yes[]NoR2.2supportnetworkrequirements?O.17,8,9,10[]Yes[]NoR3notusedR4notusedR5.1supportthefunctionsofaninitiatingentity?O.27,8,9,10[]Yes[]NoR5.2supportthefunctionsofarespondingentity?O.27,8,9,10[]Yes[]NoO.1Supportofoneandonlyoneoftheseoptionsisrequired.O.2Supportofatleastoneoftheseoptionsisrequired.Comments:A.7UserThetablesprovidedinthisclauseneedonlytobecompletedforuserimplementations,whereitemR2.1intableA.1issupported.A.7.1MajorcapabilitiesTableA.2:Majorcapabilities-userItemMajorcapability:Doestheimplementation.ConditionsforstatusStatusReferenceSupportMCu1supportthefunctionalprotocol(separatemessagecategory)forthecontrolofsupplementaryservices?O.36.3,7[]Yes[]NoMCu2supportthefunctionalprotocol(commoninformationelementcategory)forthecontrolofsupplementaryservices?O.36.3,8[]Yes[]NoMCu2.1supportbearerrelatedsupplementaryservicesprocedure?MCu2NOTMCu2O.4N/A8.3.1[]Yes[]No[]N/AMCu2.2supportbearerindependentsupplementaryservicesprocedure?MCu2NOTMCu2O.4N/A8.3.2[]Yes[]No[]N/ASIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)13ItemMajorcapability:Doestheimplementation.ConditionsforstatusStatusReferenceSupportMCu2.3supportpoint-to-point(bearerrelated)transportmechanism?MCu2.1NOTMCu2.1MN/A8.3.1,8.3.1.1[]Yes[]No[]N/AMCu2.4supportbroadcast(bearerrelated)transportmechanism?MCu2.1NOTMCu2.1ON/A8.3.1,8.3.1.2[]Yes[]No[]N/AMCu2.5supportpoint-to-point(bearerindependent)connection-orientedtransportmechanismforlocalsignalling?MCu2.2NOTMCu2.2O.5N/A8.3.2,8.3.2.1[]Yes[]No[]N/AMCu2.6supportpoint-to-point(bearerindependent)connectionlesstransportmechanism?MCu2.2NOTMCu2.2O.5N/A8.3.2,8.3.2.2[]Yes[]No[]N/AMCu2.7supportbroadcast(bearerindependent)connectionlesstransportmechanism?MCu2.2NOTMCu2.2O.5N/A8.3.2,8.3.2.4[]Yes[]No[]N/AMCu2.8supportpoint-to-point(bearerindependent)connection-orientedtransportmechanismforgeneralsignalling?MCu2.2NOTMCu2.2O.5N/A8.3.2,8.3.2.5[]Yes[]No[]N/AMCu3supportnotificationcategoryprocedures?O.39[]Yes[]NoMCu3.1supporttransportofbearer-relatednotifications?MCu3NOTMCu3O.6N/A9.3[]Yes[]No[]N/AMCu3.2supporttransportofbearer-independentnotifications?MCu3NOTMCu3O.6N/A9.4[]Yes[]No[]N/AMCu4supportthenetwork-sidechannelreservation?O.310.1[]Yes[]No[]N/AMCu4.1supportimplicitreservation?MCu4NOTMCu4O.7N/A10.1.1[]Yes[]No[]N/AMCu4.2supportexplicitreservation?MCu4NOTMCu4O.7N/A10.1.2[]Yes[]No[]N/AMCu5supportgenericproceduresforthesupplementaryservicesmanagement?O.310.2[]Yes[]NoMCu5.1supportactivation?MCu5ANDMCu2.6NOT(MCu5ANDMCu2.6)O.8N/A10.2.2[]Yes[]No[]N/AMCu5.2supportdeactivation?MCu5ANDMCu2.6NOT(MCu5ANDMCu2.6)O.8N/A10.2.3[]Yes[]No[]N/AMCu5.3supportinterrogation?MCu5ANDMCu2.6NOT(MCu5ANDMCu2.6)O.8N/A10.2.4[]Yes[]No[]N/AMCu5.4supportstatusnotification?(note)MCu5ANDMCu2.7NOT(MCu5ANDMCu2.7)O.8N/A10.2.5[]Yes[]No[]N/AMCu6supportgenericstatusrequestprocedure?MCu2.6ORMCu2.7NOT(MCu2.6ORMCu2.7)O.3N/A10.3[]Yes[]No[]N/AO.3Supportofatleastoneoftheseoptionsisrequired.O.4Supportofatleastoneoftheseoptionsisrequired.O.5Supportofatleastoneoftheseoptionsisrequired.O.6Supportofatleastoneoftheseoptionsisrequired.O.7Supportofatleastoneoftheseoptionsisrequired.O.8Supportofatleastoneoftheseoptionsisrequired.NOTE:ThismajorcapabilitycanbesupportedevenifneitherMCu5.1norMCu5.2aresupported.Comments:SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)14A.7.2SubsidiarycapabilitiesTableA.3:Subsidiarycapabilities-userItemCapability:Doestheimplementation.ConditionsforstatusStatusReferenceSupportSCu1SeparatemessagecategorySCu1.1supporttheHoldprocedures?MCu1NOTMCu1MN/A7.1,7.2[]Yes[]No[]N/ASCu1.2supporttheRetrieveprocedures?MCu1NOTMCu1MN/A7.1,7.4[]Yes[]No[]N/ASCu3NotificationproceduresSCu3.1supportthetransportofnotificationinformationinsimplenotification"indicators"?MCu3NOTMCu3O.10N/A9.2[]Yes[]No[]N/ASCu3.2supportthetransportofnotificationinformationinnotification"parameters"?MCu3NOTMCu3O.10N/A9.2[]Yes[]No[]N/ASCu3.3supportthetransportofnotificationinformationinnotification"indicators"and"parameters"usinganextensioncodepointinoctet3oftheNotificationindicatorinformationelement?MCu3NOTMCu3O.10N/A9.2[]Yes[]No[]N/ASCu4ReservationSCu4.1supportinteractionbetweenexplicitandimplicitchannelreservation?MCu4.1ANDMCu4.2NOT(MCu4.1ANDMCu4.2)MN/A10.1.2.5[]Yes[]No[]N/AO.10Supportofatleastoneoftheseoptionsisrequired.Comments:SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)15A.7.3ProtocoldataunitsTableA.4:Messagesreceived-userItemMessage:Doestheimplementationsupporttheinterpretationof.ConditionsforstatusStatusReferenceSupportMRu1FACILITY?(note1)MCu2NOTMCu2MN/A8.3,11.1.1.1,11.1.2.1,11.1.3.1[]Yes[]No[]N/AMRu2HOLD?SCu1.1ANDR5.2NOT(SCu1.1ANDR5.2)MN/A7.2,11.1.1.2[]Yes[]No[]N/AMRu3HOLDACKNOWLEDGE?SCu1.1ANDR5.1NOT(SCu1.1ANDR5.1)MN/A7.2,11.1.1.3[]Yes[]No[]N/AMRu4HOLDREJECT?SCu1.1ANDR5.1NOT(SCu1.1ANDR5.1)MN/A7.2,11.1.1.4[]Yes[]No[]N/AMRu5REGISTER?MCu2.5ANDR5.2NOT(MCu2.5ANDR5.2)MN/A8.3.2.1.1,11.1.2.2[]Yes[]No[]N/AMRu6RETRIEVE?SCu1.2ANDR5.2NOT(SCu1.2ANDR5.2)MN/A7.4,11.1.1.5[]Yes[]No[]N/AMRu7RETRIEVEACKNOWLEDGE?SCu1.2ANDR5.1NOT(SCu1.2ANDR5.1)MN/A7.4,11.1.1.6[]Yes[]No[]N/AMRu8RETRIEVEREJECT?SCu1.2ANDR5.1NOT(SCu1.2ANDR5.1)MN/A7.4,11.1.1.7[]Yes[]No[]N/AMRu9CALLPROCEEDING(note2)MCu2.8NOTMCu2.8MN/A8.3.2.5,11.1.4,11.1.4.1[]Yes[]No[]N/AMRu10CONNECTMCu2.8NOTMCu2.8MN/A8.3.2.5,11.1.4,11.1.4.2[]Yes[]No[]N/AMRu11CONNECTACKNOWLEDGEMCu2.8NOTMCu2.8MN/A8.3.2.5,11.1.4,11.1.4.3[]Yes[]No[]N/AMRu12FACILITYMCu2.8NOTMCu2.8MN/A8.3.2.5,11.1.4,11.1.4.4[]Yes[]No[]N/AMRu13RELEASEMCu2.8NOTMCu2.8MN/A8.3.2.5,11.1.4,11.1.4.5[]Yes[]No[]N/AMRu14RELEASECOMPLETEMCu2.8NOTMCu2.8MN/A8.3.2.5,11.1.4,11.1.4.6[]Yes[]No[]N/AMRu15SETUPMCu2.8NOTMCu2.8MN/A8.3.2.5,11.1.4,11.1.4.7[]Yes[]No[]N/AMRu16STATUSMCu2.8NOTMCu2.8MN/A8.3.2.5,11.1.4,11.1.4.8[]Yes[]No[]N/AMRu17STATUSENQUIRYMCu2.8NOTMCu2.8MN/A8.3.2.5,11.1.4,11.1.4.9[]Yes[]No[]N/ANOTE1:ThisitemexcludesuseoftheFACILITYmessageforthepoint-to-point(bearerindependent)connection-orientedtransportmechanismforgeneralsignalling.NOTE2:Theseitemsonlyconcerntheuseofthemessagesforthepoint-to-point(bearerindependent)connection-orientedtransportmechanismforgeneralsignalling.Comments:SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)16TableA.5:Messagestransmitted-userItemMessage:Doestheimplementationsupporttheinclusionof.ConditionsforstatusStatusReferenceSupportMTu1FACILITY?(note1)MCu2.6(NOTMCu2.6)ANDMCu2NOTMCu2MON/A8.3,11.1.1.1,11.1.2.1,11.1.3.1[]Yes[]No[]N/AMTu2HOLD?SCu1.1ANDR5.1NOT(SCu1.1ANDR5.1)MN/A7.2,11.1.1.2[]Yes[]No[]N/AMTu3HOLDACKNOWLEDGE?SCu1.1ANDR5.2NOT(SCu1.1ANDR5.2)MN/A7.2,11.1.1.3[]Yes[]No[]N/AMTu4HOLDREJECT?SCu1.1ANDR5.2NOT(SCu1.1ANDR5.2)MN/A7.2,11.1.1.4[]Yes[]No[]N/AMTu5REGISTER?MCu2.5ANDR5.1NOT(MCu2.5ANDR5.1)MN/A8.3.2.1.1,11.1.2.2[]Yes[]No[]N/AMTu6RETRIEVE?SCu1.2ANDR5.1NOT(SCu1.2ANDR5.1)MN/A7.4,11.1.1.5[]Yes[]No[]N/AMTu7RETRIEVEACKNOWLEDGE?SCu1.2ANDR5.2NOT(SCu1.2ANDR5.2)MN/A7.4,11.1.1.6[]Yes[]No[]N/AMTu8RETRIEVEREJECT?SCu1.2ANDR5.2NOT(SCu1.2ANDR5.2)MN/A7.4,11.1.1.7[]Yes[]No[]N/AMTu9CALLPROCEEDING(note2)MCu2.8NOTMCu2.8MN/A8.3.2.5,11.1.4,11.1.4.1[]Yes[]No[]N/AMTu10CONNECTMCu2.8NOTMCu2.8MN/A8.3.2.5,11.1.4,11.1.4.2[]Yes[]No[]N/AMTu11CONNECTACKNOWLEDGEMCu2.8NOTMCu2.8MN/A8.3.2.5,11.1.4,11.1.4.3[]Yes[]No[]N/AMTu12FACILITYMCu2.8NOTMCu2.8MN/A8.3.2.5,11.1.4,11.1.4.4[]Yes[]No[]N/AMTu13RELEASEMCu2.8NOTMCu2.8MN/A8.3.2.5,11.1.4,11.1.4.5[]Yes[]No[]N/AMTu14RELEASECOMPLETEMCu2.8NOTMCu2.8MN/A8.3.2.5,11.1.4,11.1.4.6[]Yes[]No[]N/AMTu15SETUPMCu2.8NOTMCu2.8MN/A8.3.2.5,11.1.4,11.1.4.7[]Yes[]No[]N/AMTu16STATUSMCu2.8NOTMCu2.8MN/A8.3.2.5,11.1.4,11.1.4.8[]Yes[]No[]N/AMTu17STATUSENQUIRYMCu2.8NOTMCu2.8MN/A8.3.2.5,11.1.4,11.1.4.9[]Yes[]No[]N/ANOTE1:ThisitemexcludesuseoftheFACILITYmessageforthepoint-to-point(bearerindependent)connection-orientedtransportmechanismforgeneralsignalling.NOTE2:Theseitemsonlyconcerntheuseofthemessagesforthepoint-to-point(bearerindependent)connection-orientedtransportmechanismforgeneralsignalling.Comments:SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)17A.7.4ProtocoldataunitparametersA.7.4.1ProtocoldataunitparametersreceivedTableA.6:FACILITYPDUparametersreceived-userItemFACILITYPDUparameters:Doestheimplementationsupportthe.ConditionsforstatusStatusReferenceSupportIERu1.1Protocoldiscriminator?MRu1NOTMRu1MN/A4.2[]Yes[]No[]N/AIERu1.2Callreference?MRu1NOTMRu1MN/A4.3[]Yes[]No[]N/AIERu1.3Messagetype?MRu1NOTMRu1MN/A11.2.1[]Yes[]No[]N/AIERu1.4Facility?MRu1NOTMRu1MN/A11.2.2.1[]Yes[]No[]N/AIERu1.5Calledpartynumber?(note1)MRu1AND(MCu2.6ORMCu2.7)NOT(MRu1OR(MCu2.6ORMCu2.7))ON/A4.5[]Yes[]No[]N/AIERu1.6Calledpartysubaddress?(note2)MRu1AND(MCu2.6ORMCu2.7)NOT(MRu1OR(MCu2.6ORMCu2.7))ON/A4.5[]Yes[]No[]N/AIERu1.7Notificationindicator?MRu1ANDMCu3.1NOT(MRu1ANDMCu3.1)MN/A11.2.2.2[]Yes[]No[]N/AIERu1.8Display?MRu1AND(NOTMCu2.8)NOTMRu1MN/A4.5[]Yes[]No[]N/ANOTE1:OnlyapplicableinconjunctionwiththeMultiplesubscribernumbersupplementaryservice.NOTE2:OnlyapplicableinconjunctionwiththeSubaddressingsupplementaryservice.Comments:TableA.7:HOLDPDUparametersreceived-userItemHOLDPDUparameters:Doestheimplementationsupportthe.ConditionsforstatusStatusReferenceSupportIERu2.1Protocoldiscriminator?MRu2NOTMRu2MN/A4.2[]Yes[]No[]N/AIERu2.2Callreference?MRu2NOTMRu2MN/A4.3[]Yes[]No[]N/AIERu2.3Messagetype?MRu2NOTMRu2MN/A11.2.1[]Yes[]No[]N/AIERu2.4Facility?MRu2ANDMCu2.1NOT(MRu2ANDMCu2.1)MN/A11.2.2.1[]Yes[]No[]N/AIERu2.5Notificationindicator?MRu2ANDMCu3.1NOT(MRu2ANDMCu3.1)MN/A11.2.2.2[]Yes[]No[]N/AIERu2.6Display?MRu2NOTMRu2MN/A4.5[]Yes[]No[]N/AComments:SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)18TableA.8:HOLDACKNOWLEDGEPDUparametersreceived-userItemHOLDACKNOWLEDGEPDUparameters:Doestheimplementationsupportthe.ConditionsforstatusStatusReferenceSupportIERu3.1Protocoldiscriminator?MRu3NOTMRu3MN/A4.2[]Yes[]No[]N/AIERu3.2Callreference?MRu3NOTMRu3MN/A4.3[]Yes[]No[]N/AIERu3.3Messagetype?MRu3NOTMRu3MN/A11.2.1[]Yes[]No[]N/AIERu3.4Facility?MRu3ANDMCu2.1NOT(MRu3ANDMCu2.1)MN/A11.2.2.1[]Yes[]No[]N/AIERu3.5Notificationindicator?MRu3ANDMCu3.1NOT(MRu3ANDMCu3.1)MN/A11.2.2.2[]Yes[]No[]N/AIERu3.6Display?MRu3NOTMRu3MN/A4.5[]Yes[]No[]N/AComments:TableA.9:HOLDREJECTPDUparametersreceived-userItemHOLDREJECTPDUparameters:Doestheimplementationsupportthe.ConditionsforstatusStatusReferenceSupportIERu4.1Protocoldiscriminator?MRu4NOTMRu4MN/A4.2[]Yes[]No[]N/AIERu4.2Callreference?MRu4NOTMRu4MN/A4.3[]Yes[]No[]N/AIERu4.3Messagetype?MRu4NOTMRu4MN/A11.2.1[]Yes[]No[]N/AIERu4.4Cause?MRu4NOTMRu4MN/A4.5[]Yes[]No[]N/AIERu4.5Facility?MRu4ANDMCu2.1NOT(MRu4ANDMCu2.1)MN/A11.2.2.1[]Yes[]No[]N/AIERu4.5Notificationindicator?MRu4ANDMCu3.1NOT(MRu4ANDMCu3.1)MN/A11.2.2.2[]Yes[]No[]N/AIERu4.6Display?MRu4NOTMRu4MN/A4.5[]Yes[]No[]N/AComments:SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)19TableA.10:REGISTERPDUparametersreceived-userItemREGISTERPDUparameters:Doestheimplementationsupportthe.ConditionsforstatusStatusReferenceSupportIERu5.1Protocoldiscriminator?MRu5NOTMRu5MN/A4.2[]Yes[]No[]N/AIERu5.2Callreference?MRu5NOTMRu5MN/A4.3[]Yes[]No[]N/AIERu5.3Messagetype?MRu5NOTMRu5MN/A11.2.1[]Yes[]No[]N/AIERu5.4Facility?MRu5NOTMRu5MN/A11.2.2.1[]Yes[]No[]N/AIERu5.5Display?MRu5NOTMRu5MN/A4.5[]Yes[]No[]N/AComments:TableA.11:RETRIEVEPDUparametersreceived-userItemRETRIEVEPDUparameters:Doestheimplementationsupportthe.ConditionsforstatusStatusReferenceSupportIERu6.1Protocoldiscriminator?MRu6NOTMRu6MN/A4.2[]Yes[]No[]N/AIERu6.2Callreference?MRu6NOTMRu6MN/A4.3[]Yes[]No[]N/AIERu6.3Messagetype?MRu6NOTMRu6MN/A11.2.1[]Yes[]No[]N/AIERu6.4Channelidentification?MRu6NOTMRu6MN/A4.5[]Yes[]No[]N/AIERu6.5Facility?MRu6ANDMCu2.1NOT(MRu6ANDMCu2.1)MN/A11.2.2.1[]Yes[]No[]N/AIERu6.6Notificationindicator?MRu6ANDMCu3.1NOT(MRu6ANDMCu3.1)MN/A11.2.2.2[]Yes[]No[]N/AIERu6.7Display?MRu6NOTMRu6MN/A4.5[]Yes[]No[]N/AComments:SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)20TableA.12:RETRIEVEACKNOWLEDGEPDUparametersreceived-userItemRETRIEVEACKNOWLEDGEPDUparameters:Doestheimplementationsupportthe.ConditionsforstatusStatusReferenceSupportIERu7.1Protocoldiscriminator?MRu7NOTMRu7MN/A4.2[]Yes[]No[]N/AIERu7.2Callreference?MRu7NOTMRu7MN/A4.3[]Yes[]No[]N/AIERu7.3Messagetype?MRu7NOTMRu7MN/A11.2.1[]Yes[]No[]N/AIERu7.4Channelidentification?MRu7NOTMRu7MN/A4.5[]Yes[]No[]N/AIERu7.5Facility?MRu7ANDMCu2.1NOT(MRu7ANDMCu2.1)MN/A11.2.2.1[]Yes[]No[]N/AIERu7.6Notificationindicator?MRu7ANDMCu3.1NOT(MRu7ANDMCu3.1)MN/A11.2.2.2[]Yes[]No[]N/AIERu7.7Display?MRu7NOTMRu7MN/A4.5[]Yes[]No[]N/AComments:TableA.13:RETRIEVEREJECTPDUparametersreceived-userItemRETRIEVEREJECTPDUparameters:Doestheimplementationsupportthe.ConditionsforstatusStatusReferenceSupportIERu8.1Protocoldiscriminator?MRu8NOTMRu8MN/A4.2[]Yes[]No[]N/AIERu8.2Callreference?MRu8NOTMRu8MN/A4.3[]Yes[]No[]N/AIERu8.3Messagetype?MRu8NOTMRu8MN/A11.2.1[]Yes[]No[]N/AIERu8.4Cause?MRu8NOTMRu8MN/A4.5[]Yes[]No[]N/AIERu8.5Facility?MRu8ANDMCu2.1NOT(MRu8ANDMCu2.1)MN/A11.2.2.1[]Yes[]No[]N/AIERu8.6Notificationindicator?MRu8ANDMCu3.1NOT(MRu8ANDMCu3.1)MN/A11.2.2.2[]Yes[]No[]N/AIERu8.7Display?MRu8NOTMRu8MN/A4.5[]Yes[]No[]N/AComments:SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)21TableA.14:ALERTINGPDUparametersreceived-userItemALERTINGPDUparameters:Doestheimplementationsupportthe.ConditionsforstatusStatusReferenceSupportIERu9.1Facility?MCu2.1NOTMCu2.1MN/A11.2.2.1[]Yes[]No[]N/AIERu9.2Notificationindicator?MCu3.1NOTMCu3.1MN/A11.2.2.2[]Yes[]No[]N/ANOTE:Theseparametersareadditionaltothoserequiredforsupportofbasiccall(EN300403-1).Comments:TableA.15:CALLPROCEEDINGPDUparametersreceived-userItemCALLPROCEEDINGPDUparameters:Doestheimplementationsupportthe.ConditionsforstatusStatusReferenceSupportIERu10.1Facility?MCu2.1NOTMCu2.1MN/A11.2.2.1[]Yes[]No[]N/AIERu10.2Notificationindicator?MCu3.1NOTMCu3.1MN/A11.2.2.2[]Yes[]No[]N/ANOTE:Theseparametersareadditionaltothoserequiredforsupportofbasiccall(EN300403-1).Comments:TableA.15a:CALLPROCEEDINGPDUparametersreceived-userundertheconditionofMCu2.8ItemCALLPROCEEDINGPDUparameters:Doestheimplementationsupportthe.ConditionsforstatusStatusReferenceSupportIERu10.1Protocoldiscriminator?MRu9NOTMRu9MN/A4.2[]Yes[]No[]N/AIERu10.2Callreference?MRu9NOTMRu9MN/A4.3[]Yes[]No[]N/AIERu10.3Messagetype?MRu9NOTMRu9MN/A4.4[]Yes[]No[]N/AComments:SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)22TableA.16:CONNECTPDUparametersreceived-userItemCONNECTPDUparameters:Doestheimplementationsupportthe.ConditionsforstatusStatusReferenceSupportIERu11.1Facility?MCu2.1NOTMCu2.1MN/A11.2.2.1[]Yes[]No[]N/AIERu11.2Notificationindicator?MCu3.1NOTMCu3.1MN/A11.2.2.2[]Yes[]No[]N/ANOTE:Theseparametersareadditionaltothoserequiredforsupportofbasiccall(EN300403-1).Comments:TableA.16a:CONNECTPDUparametersreceived-userundertheconditionofMCu2.8ItemCONNECTPDUparameters:Doestheimplementationsupportthe.ConditionsforstatusStatusReferenceSupportIERu11.1Protocoldiscriminator?MRu10NOTMRu10MN/A4.2[]Yes[]No[]N/AIERu11.2Callreference?MRu10NOTMRu10MN/A4.3[]Yes[]No[]N/AIERu11.3Messagetype?MRu10NOTMRu10MN/A4.4[]Yes[]No[]N/AIERu11.4Facility?MCu28NOTMCu28)MN/A11.2.2.1[]Yes[]No[]N/AIERu11.5Connectednumber?MCu2.8NOTMCu2.8ON/A7.1[]Yes[]No[]N/AComments:TableA.17:CONNECTACKNOWLEDGEPDUparametersreceived-userItemCONNECTACKNOWLEDGEPDUparameters:Doestheimplementationsupportthe.ConditionsforstatusStatusReferenceSupportIERu12.1Facility?MCu2.1NOTMCu2.1MN/A11.2.2.1[]Yes[]No[]N/AIERu12.2Notificationindicator?MCu3.1NOTMCu3.1MN/A11.2.2.2[]Yes[]No[]N/ANOTE:Theseparametersareadditionaltothoserequiredforsupportofbasiccall(EN300403-1).Comments:SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)23TableA.18:DISCONNECTPDUparametersreceived-userItemDISCONNECTPDUparameters:Doestheimplementationsupportthe.ConditionsforstatusStatusReferenceSupportIERu13.1Facility?MCu2.1NOTMCu2.1MN/A11.2.2.1[]Yes[]No[]N/AIERu13.2Notificationindicator?MCu3.1NOTMCu3.1MN/A11.2.2.2[]Yes[]No[]N/ANOTE:Theseparametersareadditionaltothoserequiredforsupportofbasiccall(EN300403-1).Comments:TableA.19:INFORMATIONPDUparametersreceived-userItemINFORMATIONPDUparameters:Doestheimplementationsupportthe.ConditionsforstatusStatusReferenceSupportIERu14.1Facility?MCu2.1NOTMCu2.1MN/A11.2.2.1[]Yes[]No[]N/AIERu14.2Notificationindicator?MCu3.1NOTMCu3.1MN/A11.2.2.2[]Yes[]No[]N/ANOTE:Theseparametersareadditionaltothoserequiredforsupportofbasiccall(EN300403-1).Comments:TableA.20:PROGRESSPDUparametersreceived-userItemPROGRESSPDUparameters:Doestheimplementationsupportthe.ConditionsforstatusStatusReferenceSupportIERu15.1Facility?MCu2.1NOTMCu2.1MN/A11.2.2.1[]Yes[]No[]N/AIERu15.2Notificationindicator?MCu3.1NOTMCu3.1MN/A11.2.2.2[]Yes[]No[]N/ANOTE:Theseparametersareadditionaltothoserequiredforsupportofbasiccall(EN300403-1).Comments:SIST EN 300 196-2 V1.3.2:2004

ETSIETSIEN300196-2V1.3.2(2001-06)24TableA.21:RELEASEPDUparametersreceived-userItemRELEASEPDUparameters:Doestheimplementationsupportthe.ConditionsforstatusStatusReferenceSupportIERu16.1Facility?MCu2.1ORMCu28NOT(MCu2.1ORMCu28)MN/A11.2.2.1[]Yes[]No[]N/AIERu16.2Notificationindicator?MCu3.1NOTMCu3.1MN/A11.2.2.2[]Yes[]No[]N/ANOTE:Theseparametersareadditionaltothoserequiredforsupportofbasiccall(EN300403-1).Comments:TableA.22:RELEASECOMPLETEPDUparametersreceived-userItemRELEASECOMPLETEPDUparameters:Doestheimplementationsupportthe.ConditionsforstatusStatusReferenceSupportIERu17.1Facility?MCu2.1ORMCu28NOT(MCu2.1ORMCu28)MN/A11.2.2.1[]Yes[]No[]N/AIERu17.2Notificationindicator?MCu3.1NOTMCu3.1MN/A11.2.2.2[]Yes[]No[]N/ANOTE:Theseparametersareadditionaltothoserequiredforsupportofbasiccall(EN300403-1).Comments:TableA.23:RES
...