SIST EN 302 092-3 V1.1.1:2005

• Abstract:

  Develop part 3 (TSS&TP for the user)

• Status: Published
• Publication Date: 31-Dec-2004
• ICS: 33.040.35 - Telephone networks
• 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-Jan-2005
• Due Date: 01-Jan-2005
• Completion Date: 01-Jan-2005
• Mandate: BC-T-338
• Ref Project: ETSI EN 302 092-3 V1.1.1 (2000-08) - Broadband Integrated Services Digital Network (B-ISDN) and Broadband Private Integrated Services Network (B-PISN); Digital Subscriber Signalling System No. two (DSS2), Broadband Inter-Exchange Signalling (B-QSIG), and Signalling System No. 7 (SS7); Call control in a separated call and bearer control environment; Part 3 : Test Suite Structure and Test Purposes (TSS&TP) specification

SIST EN 302 092-3 V1.1.1:2005 is the Slovenian adoption of ETSI EN 302 092-3 Version 1.1.1. It specifies the Test Suite Structure and Test Purposes (TSS&TP) for call control in a separated call and bearer control environment for Broadband Integrated Services Digital Network (B-ISDN), Broadband Private Integrated Services Network (B-PISN), Digital Subscriber Signalling System No. two (DSS2), Broadband Inter-Exchange Signalling (B-QSIG) and Signalling System No. 7 (SS7). The document is for people who need to define or check conformance test cases for implementations of EN 302 092-1.

What does SIST EN 302 092-3 V1.1.1:2005 specify?

SIST EN 302 092-3 V1.1.1:2005 specifies the TSS&TP for the Call Control protocol at the QB, SB, TB and co-incident SB/TB reference points within and between Broadband Private Integrated Services Networks and at the access to public Broadband Integrated Services Digital Networks.

The document is organized as a testing-specification companion to the protocol standard. It covers scope, references, definitions and abbreviations, the TSS, the TP set, compliance, and requirements for a comprehensive testing service.

What are the key requirements of SIST EN 302 092-3 V1.1.1:2005?

Test suite structure

Clause 4 defines the TSS as a tree with three test-group levels. The first level is DSS2_CC, the second level splits the protocol into Call Establishment (CE), Call Status Change (SC), and Call Clearing (CL), and the third level distinguishes Initiator (I) and Responder (R), with a fourth-level split for Valid (V), Invalid (IV), and Inopportune (IO) cases.

In practice, this structure tells a test developer how to organize a conformance suite so that similar tests are grouped together and can be selected consistently from the PICS.

Test purposes and naming

Clause 5 says that a TP is defined for each test requirement, and that TPs are numbered from 01 within each group. The naming convention identifies the suite, group and sequence number, so a TP name carries the call-control phase, whether the IUT acts as initiator or responder, and whether the case is valid, invalid or inopportune.

That matters because a lab can trace each test back to a protocol function and select only the tests that apply to the implementation under test (IUT). Clause 5 also states that the TPs are based on EN 302 092-1 and on the PICS in EN 302 092-2.

What the TPs check

Clause 5 focuses on externally observable behaviour at the specified reference points. It covers call establishment, call status change and call clearing for the call control (CC) entity, including the messages the IUT sends, the APDU contents it uses, and how it reacts to received APDUs in defined states such as CC0 to CC9.

The practical effect is that the standard checks both normal signalling and exceptional handling. For example, it includes cases for unrecognized parameters, duplicate or unknown Call Segment Id values, rejected or unexpected APDUs, and timer expiry such as T710.

Selection by PICS

Many TPs include a selection note tied to a PICS item from EN 302 092-2. That means a test case is only relevant when the implementation declares support for the corresponding procedure, option or parameter handling.

For a buyer or verifier, this is important because it links the test set directly to declared product capabilities. It prevents testing features the product has not claimed.

Compliance and testing service

Clause 6 says that a compliant ATS shall use a suitable subset of the TSS, keep the same 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 shall be included in a compliant ATS.

Clause 7 requires the Remote test method from ISO/IEC 9646-2 as the minimum method for any organization claiming to provide a comprehensive testing service for equipment conforming to EN 302 092-1.

What terms does SIST EN 302 092-3 V1.1.1:2005 define?

• Abstract Test Suite (ATS) - the defined set of abstract test cases used for conformance testing.
• Abstract Test Method (ATM) - the abstract way the test suite is applied.
• Implementation Under Test (IUT) - the implementation being checked for conformance.
• Protocol Implementation Conformance Statement (PICS) - the declaration of which protocol features the implementation supports.
• Protocol Implementation eXtra Information for Testing (PIXIT) - extra test information needed to run the suite.
• Test Purpose (TP) - a statement of what one test is intended to check.
• Test Suite Structure (TSS) - the tree that organizes the test groups and test cases.
• Application Protocol Data Unit (APDU) - the protocol data unit used in the signalling exchanges described by the TPs.

Who uses SIST EN 302 092-3 V1.1.1:2005?

SIST EN 302 092-3 V1.1.1:2005 is used by test laboratories, protocol implementers, and manufacturers of broadband network equipment that claim conformance to EN 302 092-1. It is also relevant to organizations that build a comprehensive testing service, because clause 7 sets the minimum testing method.

In practice, these users apply it to build ATS documents, map tests to PICS items, verify call establishment and clearing behaviour, and check how an IUT handles normal, invalid and exceptional signalling cases.

Which standards are used with SIST EN 302 092-3 V1.1.1:2005?

• ETSI EN 302 092-1 - provides the protocol specification that the TPs are based on.
• ETSI EN 302 092-2 - provides the PICS proforma used to select relevant test purposes.
• ISO/IEC 9646-1 - supplies the conformance testing concepts and definitions used in the document.
• ISO/IEC 9646-2 - provides the ATS specification framework and the Remote test method.
• ETSI ETS 300 406 - gives the testing methodology used when forming the TPs from externally observable behaviour.

What does the SIST EN 302 092-3 V1.1.1:2005 document contain?

Clause 4 presents the overall TSS and Figure 1 shows its tree structure. Clause 5 contains the TP set, including the TP naming convention, the structure of a single TP, the test strategy, and detailed TP groups for call establishment, call status change and call clearing.

The detailed TP sections describe message direction, call state, APDU contents, and expected reactions for the IUT. They also cover invalid and inopportune cases such as unknown identifiers, duplicated identifiers, rejected messages, and unrecognized parameters.

Clause 6 states what a compliant ATS must do, and clause 7 states the minimum testing method for a comprehensive service. The bibliography points to supporting conformance-testing and broadband-signalling documents.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.HVNXãDQMDBroadband Integrated Services Digital Network (B-ISDN) and Broadband Private Integrated Services Network (B-PISN); Digital Subscriber Signalling System No. two (DSS2), Broadband Inter-Exchange Signalling (B-QSIG), and Signalling System No. 7 (SS7); Call control in a separated call and bearer control environment; Part 3 : Test Suite Structure and Test Purposes (TSS&TP) specification33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 302 092-3 Version 1.1.1SIST EN 302 092-3 V1.1.1:2005en01-januar-2005SIST EN 302 092-3 V1.1.1:2005SLOVENSKI
STANDARD
ETSIEN302092-3V1.1.1(2000-08)EuropeanStandard(Telecommunicationsseries)BroadbandIntegratedServicesDigitalNetwork(B-ISDN)andBroadbandPrivateIntegratedServicesNetwork(B-PISN);DigitalSubscriberSignallingSystemNo.two(DSS2),BroadbandInter-ExchangeSignalling(B-QSIG),andSignallingSystemNo.7(SS7);Callcontrolinaseparatedcallandbearercontrolenvironment;Part3:TestSuiteStructureandTestPurposes(TSS&TP)specificationSIST EN 302 092-3 V1.1.1:2005

ETSIETSIEN302092-3V1.1.1(2000-08)2ReferenceDEN/SPS-05154-3Keywordsbearer,B-ISDN,B-ISUP,B-QSIG,broadband,DSS2,ISDN,ISUP,QSIG,SS7,TSS&TP,userETSI650RoutedesLuciolesF-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 302 092-3 V1.1.1:2005

ETSIETSIEN302092-3V1.1.1(2000-08)3ContentsIntellectualPropertyRights.4Foreword.41Scope.52References.53Definitionsandabbreviations.63.1Definitions.63.2Abbreviations.64TestSuiteStructure(TSS).75TestPurposes(TP).85.1Introduction.85.1.1TPnamingconvention.85.1.2SourceofTPdefinition.85.1.3TPStructure.85.1.4Teststrategy.95.1.5Testofcallstates.95.2TPsforthecallcontrol(CC)entity.95.2.1CallEstablishment.95.2.1.1PrecedingCCentity.95.2.1.1.1Valid.95.2.1.1.2Invalid.105.2.1.1.3Inopportune.125.2.1.2SucceedingCCentity.125.2.1.2.1Valid.125.2.1.2.2Invalid.165.2.2CallStatusChange.195.2.2.1InitiatingCCentity.195.2.2.1.1Valid.195.2.2.2ReceivingCCentity.205.2.2.2.1Invalid.205.2.3CallClearing.215.2.3.1CCentitythatinitiatescallclearing.215.2.3.1.1Valid.215.2.3.1.2Invalid.225.2.3.2CCentitythatrespondstocallclearing.235.2.3.2.1Valid.235.2.3.2.2Invalid.236Compliance.247Requirementsforacomprehensivetestingservice.24Bibliography.25History.26SIST EN 302 092-3 V1.1.1:2005

ETSIETSIEN302092-3V1.1.1(2000-08)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).Thepresentdocumentispart3ofamulti-partENcoveringtheBroadbandIntegratedServicesDigitalNetwork(B-ISDN)andBroadbandPrivateIntegratedServicesNetwork(B-PISN);DigitalSubscriberSignallingSystemNo.2(DSS2),BroadbandInter-ExchangeSignalling(B-QSIG),andSignallingSystemNo.7(SS7);Callcontrolspecificationinaseparatedcallandbearercontrolenvironment,asdescribedbelow:Part1:"Protocolspecification";Part2:"ProtocolImplementationConformanceStatement(PICS)proformaspecification";Part3:"TestSuiteStructureandTestPurposes(TSS&TP)specification";Part4:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecification".NationaltranspositiondatesDateofadoptionofthisEN:26May2000DateoflatestannouncementofthisEN(doa):31August2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):28February2001DateofwithdrawalofanyconflictingNationalStandard(dow):28February2001SIST EN 302 092-3 V1.1.1:2005

ETSIETSIEN302092-3V1.1.1(2000-08)51ScopeThepresentdocumentisapplicabletotheCallControlprotocolattheQB,SB,TBandco-incidentSB/TBreferencepointswithin,betweenandattheaccesstoBroadbandPrivateIntegratedServicesNetworksandwithin,betweenandattheaccesstopublicBroadbandIntegratedServicesDigitalNetworks.ThepresentdocumentprovidestheTestSuiteStructureandTestPurposes(TSS&TP)fortheCallControlprotocolasspecifiedinEN302092-1[1].AfurtherpartofthepresentdocumentspecifiestheAbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformabasedonthepresentdocument.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIEN302092-1(V1.1):"BroadbandIntegratedServicesDigitalNetwork(B-ISDN)andBroadbandPrivateIntegratedServicesNetwork(B-PISN);DigitalSubscriberSignallingSystemNo.two(DSS2),BroadbandInter-ExchangeSignalling(B-QSIG),andSignallingSystemNo.7(SS7);Callcontrolinaseparatedcallandbearercontrolenvironment;Part1:Protocolspecification".[2]ETSIEN302092-2(V1.1):"BroadbandIntegratedServicesDigitalNetwork(B-ISDN)andBroadbandPrivateIntegratedServicesNetwork(B-PISN);DigitalSubscriberSignallingSystemNo.two(DSS2),BroadbandInter-ExchangeSignalling(B-QSIG),andSignallingSystemNo.7(SS7);Callcontrolinaseparatedcallandbearercontrolenvironment;Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecification".[3]ISO/IEC9646-1(1994):"Informationtechnology;OpenSystemsInterconnection;Conformancetestingmethodologyandframework;Part1:Generalconcepts".[4]ISO/IEC9646-2(1994):"Informationtechnology;OpenSystemsInterconnection;Conformancetestingmethodologyandframework;Part2:AbstractTestSuitespecification".[5]ETSIETS300406:"MethodsforTestingandSpecification(MTS);Protocolandprofileconformancetestingspecifications;Standardizationmethodology".SIST EN 302 092-3 V1.1.1:2005

ETSIETSIEN302092-3V1.1.1(2000-08)63Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapplyinadditiontothedefinitionsinEN302092-1[1]:Abstracttestcase:refertoISO/IEC9646-1[3]AbstractTestMethod(ATM):refertoISO/IEC9646-1[3]AbstractTestSuite(ATS):refertoISO/IEC9646-1[3]ImplementationUnderTest(IUT):refertoISO/IEC9646-1[3]Lowertester:refertoISO/IEC9646-1[3]ProtocolImplementationConformanceStatement(PICS):refertoISO/IEC9646-1[3]PICSproforma:refertoISO/IEC9646-1[3]ProtocolImplementationeXtraInformationforTesting(PIXIT):refertoISO/IEC9646-1[3]PIXITproforma:refertoISO/IEC9646-1[3]TestPurpose(TP):refertoISO/IEC9646-1[3]3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:APDUApplicationProtocolDataUnitATMAbstractTestMethodATSAbstractTestSuiteDSS2DigitalSubscriberSignallingSystemNo.twoB-ISDNBroadbandIntegratedServicesDigitalNetworkB-PISNBroadbandPrivateIntegratedServicesNetworkB-QSIGBroadbandInter-ExchangeSignallingSystemCCCallControlCC0CallIdlestateCC1CallInitiatedstateCC2OutgoingCallProceedingstateCC3CallReadystateCC4CallPresentstateCC5IncomingCallProceedingstateCC6AwaitCallCompletionstateCC7CallActivestateCC8CallReleaseRequeststateCC9CallReleaseIndicationstateIUTImplementationUnderTestPICSProtocolImplementationConformanceStatementPIXITProtocolImplementationeXtraInformationforTestingTPTestPurposeTSSTestSuiteStructureSIST EN 302 092-3 V1.1.1:2005

ETSIETSIEN302092-3V1.1.1(2000-08)74TestSuiteStructure(TSS)Thetestsuitestructureisatree.Threetestgrouplevelsaredefined.TheTSSisdepictedinfigure1.Thelevelsarethefollowing:1stlevel:thenamerepresentingthebasespecification(EN302092-1[1]):DSS2_CC.2ndlevel:thephasesofthebasespecification:• CallEstablishment(CE);• CallStatusChange(SC);• CallClearing(CL).3rdlevel:initiatororresponder:• Initiator(I);• Responder(R).4thlevel:thenatureofthetest:• Valid(V);• Invalid(IV);• Inopportune(IO).DSS2_CCCE(1)SC(2)CL(3)I(1)R(2)V(1)IV(2)IO(3)V(1)IV(2)IO(3)I(1)R(2)V(1)IV(2)V(1)IV(2)I(1)R(2)V(1)IV(2)IO(3)V(1)IV(2)Figure1:TestsuitestructureSIST EN 302 092-3 V1.1.1:2005

ETSIETSIEN302092-3V1.1.1(2000-08)85TestPurposes(TP)5.1IntroductionForeachtestrequirementaTPisdefined.5.1.1TPnamingconventionTPsarenumbered,startingat01,withineachgroup.GroupsareorganizedaccordingtotheTSS.Additionalreferencesareaddedtoidentifytheactualtestsuite(seetable1).Table1:TPidentifiernamingconventionschemeIdentifier:__=layer+typeofIUT:"L3CC"forLayer3CallControlProtocol=groupnumber(3digits):1stdigit1Callestablishment;2CallStatusChange;3Callclearing2nddigit1Initiator;2Responder3rddigit1Valid;2Invalid;3Inopportune=sequentialnumber:(01-99)5.1.2SourceofTPdefinitionTheTPsarebasedonEN302092-1[1].5.1.3TPStructureEachTPhasbeenwritteninamannerwhichisconsistentwithallotherTPs.TheintentionofthisistomaketheTPsmorereadableandcheckable.Aparticularstructurehasbeenusedandthisisillustratedintable2.ThistableshouldbereadinconjunctionwithanyTP,i.e.useaTPasanexampletofullyunderstandthetable.Table2:StructureofasingleTPTPpartTextExampleHeadertabseetable1tabsubclause0.0.0StimulusEnsurethattheIUTintheCC1,CC2,etc.seebelowformessagestructurereceivingaXXXXmessageortorequesta.Reactionsends,saves,does,etc.using???,.iftheactionissendingseebelowformessagestructure,etc.APDUstructureAPDUcontainingacallEstablishinvoke,callReleasereturnResult….encodedasorincluding,callSegmentId,callDescription…NOTE:TextinitalicswillnotappearinTPsandtextbetween<>isfilledinforeachTPandmaydifferfromoneTPtothenext.SIST EN 302 092-3 V1.1.1:2005

ETSIETSIEN302092-3V1.1.1(2000-08)95.1.4TeststrategyAsthebasestandardEN302092-1[1]containsnoexplicitrequirementsfortesting,theTPsweregeneratedasaresultofananalysisofthebasestandardandthePICSspecificationEN302092-2[2].Thecriteriaappliedincludethefollowing:-onlytherequirementsfromthepointofviewoftheQB,SB,TBandco-incidentSB/TBreferencepointsareconsidered;-whetherornotatestcasecanbebuiltfromtheTPisnotconsidered.TheTPsareonlybasedonconformancerequirementsrelatedtotheexternallyobservablebehaviouroftheIUT,andarelimitedtoconceivablesituationstowhicharealimplementationislikelytobefaced(ETS300406[5]).5.1.5TestofcallstatesItisnotpossibletotestthefinalcallstatesbecausenoproceduresaredefinedforthis.5.2TPsforthecallcontrol(CC)entityAllPICSitemsreferredtointhissubclauseareasspecifiedinEN302092-2[2]unlessindicatedotherwisebyanothernumberedreference.Unlessspecified:• theAPDUsindicatedarevalidandcontainatleastthemandatoryfieldsandpossiblyoptionalones;• thefieldsindicatedarevalidandcontainatleastthemandatorycontentsandpossiblyoptionalones.5.2.1CallEstablishment5.2.1.1PrecedingCCentity5.2.1.1.1ValidCC_111_01subclause9.1.1EnsurethattheIUTinstateCC0,isabletosendacallEstablishinvokeAPDUtowardsthesucceedingCCentitycontainingtheparametercallSegmentIdwiththesucceedingSideCallSegIdsettotheNullvalueandthebearerEstablishmentAddresscontainingthenumberoftheterminalornetworknodeconnectedtotheprecedingCCentity.Selection:SupportsignallingproceduresforcallestablishmentrequestwhenactingasaprecedingCCentity,PICS:MC1.CC_111_02subclause9.4.1EnsurethattheIUTinstateCC3,isabletosendacallCompleteinvokeAPDU.Selection:SupportsignallingproceduresforcallacceptancewhenactingasaprecedingCCentity.PICS:MC9.SIST EN 302 092-3 V1.1.1:2005

ETSIETSIEN302092-3V1.1.1(2000-08)105.2.1.1.2InvalidCC_112_01subclause9.8.5.3EnsurethattheIUTinstateCC7,onreceiptofarejectAPDUthatiscorrelatedtoacallCompleteinvokeAPDU,sendsacallReleaseinvokeAPDUwiththereleaseCausecontainingtheparametercauseValuewiththevaluetemporaryFailure.Selection:SupportexceptionalproceduresonreceiptofrejectAPDUs.PICS:SC9.CC_112_02subclause9.8.6EnsurethattheIUTinstateCC2,onreceiptofacallEstablishreturnresultAPDUwithanunrecognizedparameterandparameterActionIndicatorsettoclearCallAndItsInformationModel,sendsacallReleaseinvokeAPDU.Selection:SupportproceduresforthehandlingofunrecognizedparameterswithinCC-Operations.PICS:SC10.CC_112_03subclause9.8.6EnsurethattheIUTinstateCC2,onreceiptofacallEstablishreturnresultAPDUwithanunrecognizedparameterandparameterActionIndicatorsettodiscardApduAndReject,sendsarejectAPDU.Selection:SupportproceduresforthehandlingofunrecognizedparameterswithinCC-Operations.PICS:SC10.CC_112_04subclause9.8.6EnsurethattheIUTinstateCC2,onreceiptofacallEstablishreturnresultAPDUwithanunrecognizedparameterandparameterActionIndicatorsettodiscardApduNoReject,doesnotsendarejectAPDU.Selection:SupportproceduresforthehandlingofunrecognizedparameterswithinCC-Operations.PICS:SC10.CC_112_05subclause9.8.6EnsurethattheIUTinstateCC2,onreceiptofacallEstablishreturnresultAPDUwithanunrecognizedparameterandparameterActionIndicatorsettodiscardParameterAndPassApduToApplication,doesnotrespond.Selection:SupportproceduresforthehandlingofunrecognizedparameterswithinCC-Operations.PICS:SC10.CC_112_06subclause9.8.6EnsurethattheIUTinstateCC2,onreceiptofacallEstablishreturnresultAPDUwithanunrecognizedparameterandparameterActionIndicatorsettoignoreParameterAndPassApduToApplication,doesnotrespond.Selection:SupportproceduresforthehandlingofunrecognizedparameterswithinCC-Operations.PICS:SC10.CC_112_07subclause9.8.6EnsurethattheIUTinstateCC1,onreceiptofacallProceedinginvokeAPDUwithanunrecognizedparameterandparameterActionIndicatorsettoclearCallAndItsInformationModel,sendsacallReleaseinvokeAPDU.Selection:SupportproceduresforthehandlingofunrecognizedparameterswithinCC-Operations.PICS:SC10.CC_112_08subclause9.8.6EnsurethattheIUTinstateCC1,onreceiptofacallProceedinginvokeAPDUwithanunrecognizedparameterandparameterActionIndicatorsettodiscardApduAndReject,sendsarejectAPDU.Selection:SupportproceduresforthehandlingofunrecognizedparameterswithinCC-Operations.PICS:SC10.SIST EN 302 092-3 V1.1.1:2005

ETSIETSIEN302092-3V1.1.1(2000-08)11CC_112_09subclause9.8.6EnsurethattheIUTinstateCC1,onreceiptofacallProceedinginvokeAPDUwithanunrecognizedparameterandparameterActionIndicatorsettodiscardApduNoReject,doesnotsendarejectAPDU.Selection:SupportproceduresforthehandlingofunrecognizedparameterswithinCC-Operations.PICS:SC10.CC_112_10subclause9.8.6EnsurethattheIUTinstateCC1,onreceiptofacallProceedinginvokeAPDUwithanunrecognizedparameterandparameterActionIndicatorsettodiscardParameterAndPassApduToApplication,doesnotrespond.Selection:SupportproceduresforthehandlingofunrecognizedparameterswithinCC-Operations.PICS:SC10.CC_112_11subclause9.8.6EnsurethattheIUTinstateCC1,onreceiptofacallProceedinginvokeAPDUwithanunrecognizedparameterandparameterActionIndicatorsettoignoreParameterAndPassApduToApplication,doesnotrespond.Selection:SupportproceduresforthehandlingofunrecognizedparameterswithinCC-Operations.PICS:SC10.CC_112_12subclause9.8.6EnsurethattheIUTinstateCC7,onreceiptofacallStatusinvokeAPDUwithanunrecognizedparameterandparameterActionIndicatorsettoclearCallAndItsInformationModel,sendsacallReleaseinvokeAPDU.Selection:SupportproceduresforthehandlingofunrecognizedparameterswithinCC-Operations.PICS:SC10.CC_112_13subclause9.8.6EnsurethattheIUTinstateCC7,onreceiptofacallStatusinvokeAPDUwithanunrecognizedparameterandparameterActionIndicatorsettodiscardApduAndReject,sendsarejectAPDU.Selection:SupportproceduresforthehandlingofunrecognizedparameterswithinCC-Operations.PICS:SC10.CC_112_14subclause9.8.6EnsurethattheIUTinstateCC7,onreceiptofacallStatusinvokeAPDUwithanunrecognizedparameterandparameterActionIndicatorsettodiscardApduNoReject,doesnotsendarejectAPDU.Selection:SupportproceduresforthehandlingofunrecognizedparameterswithinCC-Operations.PICS:SC10.CC_112_15subclause9.8.6EnsurethattheIUTinstateCC7,onreceiptofacallStatusinvokeAPDUwithanunrecognizedparameterandparameterActionIndicatorsettodiscardParameterAndPassApduToApplication,doesnotrespond.Selection:SupportproceduresforthehandlingofunrecognizedparameterswithinCC-Operations.PICS:SC10.CC_112_16subclause9.8.6EnsurethattheIUTinstateCC7,onreceiptofacallStatusinvokeAPDUwithanunrecognizedparameterandparameterActionIndicatorsettoignoreParameterAndPassApduToApplication,doesnotrespond.Selection:SupportproceduresforthehandlingofunrecognizedparameterswithinCC-Operations.PICS:SC10.SIST EN 302 092-3 V1.1.1:2005

ETSIETSIEN302092-3V1.1.1(2000-08)125.2.1.1.3InopportuneCC_113_01subclause9.8.4EnsurethattheIUTinCC1onreceiptofacallProceedinginvokeAPDUafteracallEstablishreturnresultAPDUcontainingthesameCallSegmentId,ignoresthiscallProceedinginvokeAPDU.Selection:SupportexceptionalproceduresonreceiptofAPDUsoutofsequencewhenactingasaprecedingCCentity.PICS:SC8.CC_113_02subclause9.8.1.1EnsurethattheIUTinstateCC2,onexpiryoftimerT710,sendsacallReleaseinvokeAPDUwiththereleaseCausecontainingtheparametercauseValuewiththevaluerecoveryOnTimerExpiry.Selection:SupportexceptionalproceduresontimerexpirywhenactingasaprecedingCCentity.PICS:SC3.5.2.1.2SucceedingCCentity5.2.1.2.1ValidCC_121_01subclause9.2.2EnsurethattheIUTinCC4,isabletosendcallProceedinginvokeAPDUcontainingaprecedingSideCallSegIdincludingthevaluereceivedinthecallEstablishinvokeAPDU.Selection:SupportsignallingproceduresforcallproceedingwhenactingasasucceedingCCentity,PICS:MC6.CC_121_02subclause9.3.2EnsurethattheIUTinCC4,andthestoredvalueof"Awaitcompleteindicator"isTRUEisabletosendcallEstablishreturnresultAPDU.Selection:SupportsignallingproceduresforcompletionofcallestablishmentwhenactingasasucceedingCCentity,PICS:MC10.CC_121_03subclause9.3.2EnsurethattheIUTinCC5,andthestoredvalueof"Awaitcompleteindicator"isTRUEisabletosendcallEstablishreturnresultAPDU.Selection:SupportsignallingproceduresforcompletionofcallestablishmentwhenactingasasucceedingCCentity,PICS:MC10.CC_121_04subclause9.3.2EnsurethattheIUTinCC4,andthestoredvalueof"Awaitcompleteindicator"isFALSEisabletosendcallEstablishreturnresultAPDU.Selection:SupportsignallingproceduresforcallacceptancewhenactingasasucceedingCCentity,PICS:MC8.CC_121_05subclause9.3.2EnsurethattheIUTinCC5,andthestoredvalueof"Awaitcompleteindicator"isFALSEisabletosendcallEstablishreturnresultAPDU.Selection:SupportsignallingproceduresforcallacceptancewhenactingasasucceedingCCentity,PICS:MC8.SIST EN 302 092-3 V1.1.1:2005

ETSIETSIEN302092-3V1.1.1(2000-08)13CC_121_06subclause9.6.2EnsurethattheIUTinCC4inordertoreportanegativeresultfortheestablishmentofthecallbecausethereceivedcalldescriptionwasnotacceptedbytheCCsignallingserviceuser,isabletosendcallEstablishreturnerrorAPDUcontainingcallDescriptionNotAcceptederrorvalue,optionallycontaininganalternativecalldescription.Selection1:SupportsignallingproceduresforcallestablishmentfailurewhenactingasasucceedingCCentity,PICS:SC2.Selection2:SupportinclusionofanalternativecallDescriptionincallEstablishreturnerror,PICS:P2.CC_121_07subclause9.6.2EnsurethattheIUTinCC5inordertoreportanegativeresultfortheestablishmentofthecallbecausethereceivedcalldescriptionwasnotacceptedbytheCCsignallingserviceuser,isabletosendcallEstablishreturnerrorAPDUcontainingcallDescriptionNotAcceptederrorvalue,optionallycontaininganalternativecalldescription.Selection1:SupportsignallingproceduresforcallestablishmentfailurewhenactingasasucceedingCCentity,PICS:SC2.Selection2:SupportinclusionofanalternativecallDescriptionincallEstablishreturnerror,PICS:P2.CC_121_08subclause9.6.2EnsurethattheIUTinCC4inordertoreportanegativeresultfortheestablishmentofthecallbecausethecalleduserisbusy,isabletosendcallEstablishreturnerrorAPDUcontaininguserBusyerrorvalue,optionallycontaininganalternativecalldescription.Selection1:SupportsignallingproceduresforcallestablishmentfailurewhenactingasasucceedingCCentity,PICS:SC2.Selection2:SupportinclusionofanalternativecallDescriptionincallEstablishreturnerror,PICS:P2.CC_121_9subclause9.6.2EnsurethattheIUTinCC5inordertoreportanegativeresultfortheestablishmentofthecallbecausethecalleduserisbusy,isabletosendcallEstablishreturnerrorAPDUcontaininguserBusyerrorvalue,optionallycontaininganalternativecalldescription.Selection1:Supportsignallingproceduresforcallestablishmentfailurewhenactinga
...