SIST EN 300 369-5 V1.3.1:2005

• Abstract:

  Upgrade of Test Specification.

• Status: Published
• Publication Date: 31-Dec-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-Jan-2005
• Due Date: 01-Jan-2005
• Completion Date: 01-Jan-2005
• Ref Project: ETSI EN 300 369-5 V1.3.1 (2002-05) - Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Explicit Call Transfer (ECT) supplementary service; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network

SIST EN 300 369-5 V1.3.1:2005 is the SIST adoption of ETSI EN 300 369-5 V1.3.1 for the Integrated Services Digital Network (ISDN) Digital Subscriber Signalling System No. one (DSS1) Explicit Call Transfer (ECT) supplementary service. It specifies the Test Suite Structure and Test Purposes (TSS&TP) for the network side at the T reference point, so test teams can check whether a network implementation follows the ECT protocol defined in EN 300 369-1.

What does SIST EN 300 369-5 V1.3.1:2005 specify?

SIST EN 300 369-5 V1.3.1:2005 specifies network-side conformance test purposes for ECT over DSS1 in ISDN. It covers implementations at the T reference point, or the coincident S and T reference point, and it is part 5 of a multi-part ECT deliverable.

The document is organized into:

• scope and references
• definitions and abbreviations
• Test Suite Structure (TSS)
• Test Purposes (TP)
• compliance
• requirements for a comprehensive testing service
• informative Annex A on changes

The foreword places this part in a six-part series:

• Part 1 - protocol specification
• Part 2 - PICS proforma specification
• Part 3 - TSS&TP specification for the user
• Part 4 - ATS and PIXIT proforma specification for the user
• Part 5 - TSS&TP specification for the network
• Part 6 - ATS and PIXIT proforma specification for the network

What are the key requirements of SIST EN 300 369-5 V1.3.1:2005?

This standard does not define product behavior directly; it defines the test purposes used to verify network behavior. The practical value is that each TP states the call states, messages, and expected responses a network should show under specific ECT conditions.

1. The test purposes are structured and named consistently

Clause 5.1 defines TP numbering and the identifier pattern. In practice, this lets labs trace every test back to a specific ECT group, network type, and sequential case.

2. The TP set is built from the base ECT protocol and the PICS

Clause 5.1.2 states that the TPs are based on EN 300 369-1, and clause 5.1.4 says they were generated from analysis of the base standard and EN 300 369-2. For a reader, that means the TP set is tied to declared implementation capabilities rather than being an open-ended test list.

3. The network-side TP groups cover several ECT procedures

Clause 5.2 divides the tests into Network(S/T) and Network(T), with served user procedures and remote user procedures. The served user tests cover implicit linkage and explicit linkage; the remote user tests cover call-transfer notifications and redirection information. This matters because different network arrangements need different checks.

4. The tests verify correct FACILITY handling and call-state reactions

Many TPs check whether the network accepts valid FACILITY messages, sends the expected DISCONNECT or NOTIFY responses, and stays in the correct ECT and call states. This is the core of the document: it checks signaling behavior during transfer, not voice quality or numbering plans in isolation.

5. The suite checks defined error conditions

The TP set includes responses such as notSubscribed, notAvailable, invalidCallState, supplementaryServiceInteractionNotAllowed, resourceUnavailable, and LinkIdNotAssignedByNetwork. In practice, this is what proves the implementation fails safely when transfer is not allowed or cannot be completed.

6. LinkId handling is tested in both request and execute flows

Clause 9.2.2 cases cover EctLinkIdRequest and ExplicitEctExecute, including cases where a LinkId is allocated, reused, missing, or cannot be allocated. That means a tester can verify both the setup of explicit linkage and the execution of a transfer based on that linkage.

7. Loop avoidance is part of the network checks

Clause 10.3 covers the mechanism to avoid looping of uncontrolled circuits. This matters because transfer must not create a network loop that would keep calls circulating instead of completing.

What terms does SIST EN 300 369-5 V1.3.1:2005 define?

• Abstract Test Suite (ATS) - the formal set of test cases used to assess conformance.
• Implementation Under Test (IUT) - the network entity being tested.
• Protocol Implementation Conformance Statement (PICS) - the declaration of supported features that drives which TPs apply.
• Protocol Implementation eXtra Information for Testing (PIXIT) - extra implementation details needed to build or run tests.
• Test Purpose (TP) - a statement of one test objective and its expected outcome.
• Digital Subscriber Signalling System No. one (DSS1) - the signaling protocol used at the ISDN user-network interface.
• Explicit Call Transfer (ECT) - the supplementary service being tested.
• Call Reference (CR) - the identifier used to distinguish calls in a test case.

Who uses SIST EN 300 369-5 V1.3.1:2005?

Telecom protocol engineers use this standard to design or review network-side ECT behavior. Test labs and certification teams use it to derive ATS and execute conformance checks.

Quality managers and buyers use it to confirm that a supplier’s ISDN/DSS1 implementation supports the network-side test scope they need. It is also relevant to vendors working on basic call control, supplementary service handling, and interoperability with other ISDN signaling functions such as HOLD and COLR.

What changed in SIST EN 300 369-5 V1.3.1:2005 from the previous edition?

Annex A is informative and summarizes changes with respect to EN 300 369-4 V1.2.4. It also gives the relationship between edition 1 and V1.2.4.

Which standards are used with SIST EN 300 369-5 V1.3.1:2005?

• EN 300 369-1 - the ECT protocol specification that the TPs are based on.
• EN 300 369-2 - the PICS proforma used to select applicable tests.
• EN 300 369-6 - the companion network ATS and PIXIT proforma specification.
• ISO/IEC 9646-1 - the conformance testing framework that defines ATS, IUT, PICS, PIXIT, and TP concepts.
• ISO/IEC 9646-2 - the abstract test suite specification method used for this kind of test document.
• EN 300 141-2 - the HOLD PICS reference used when HOLD capability affects selection.
• EN 300 403-1 and EN 300 403-3 - the basic call control protocol and PICS references used for call-state behavior.
• EN 300 196-1 - the generic supplementary-service protocol reference used for shared definitions.
• ITU-T I.411, I.112, E.164, and I.210 - reference configurations, vocabulary, numbering, and service principles used by the test definitions.

What does the SIST EN 300 369-5 V1.3.1:2005 document contain?

The document contains a TSS figure, a TP naming convention table, and a TP structure table that show how each test case is written. It then lists detailed network-side test purposes grouped by procedure and call condition, with clause references, expected messages, and expected state outcomes.

The content is primarily for test design, conformance verification, and implementation review. It shows what to stimulate, what network response to expect, and which PICS selections make each TP applicable.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.SHFLILNDFLMDIntegrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Explicit Call Transfer (ECT) supplementary service; 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 300 369-5 Version 1.3.1SIST EN 300 369-5 V1.3.1:2005en01-januar-2005SIST EN 300 369-5 V1.3.1:2005SLOVENSKI
STANDARD
ETSIEN300369-5V1.3.1(2002-05)EuropeanStandard(Telecommunicationsseries)IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;ExplicitCallTransfer(ECT)supplementaryservice;Part5:TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetworkSIST EN 300 369-5 V1.3.1:2005

ETSIETSIEN300369-5V1.3.1(2002-05)2ReferenceREN/SPAN-130228-5KeywordsDSS1,ECT,ISDN,network,supplementaryservice,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://portal.etsi.org/tb/status/status.aspIfyoufinderrorsinthepresentdocument,sendyourcommentto:[e-mail]opartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2002.Allrightsreserved.DECTTM,PLUGTESTSTMandUMTSTMareTradeMarksofETSIregisteredforthebenefitofitsMembers.TIPHONTMandtheTIPHONlogoareTradeMarkscurrentlybeingregisteredbyETSIforthebenefitofitsMembers.3GPPTMisaTradeMarkofETSIregisteredforthebenefitofitsMembersandofthe3GPPOrganizationalPartners.SIST EN 300 369-5 V1.3.1:2005

ETSIETSIEN300369-5V1.3.1(2002-05)3ContentsIntellectualPropertyRights.4Foreword.41Scope.52References.53Definitionsandabbreviations.63.1Definitions.63.1.1Definitionsrelatedtoconformancetesting.63.1.2DefinitionsrelatedtoEN300369-1.63.2Abbreviations.74TestSuiteStructure(TSS).85TestPurposes(TP).85.1Introduction.85.1.1TPnamingconvention.85.1.2SourceofTPdefinition.85.1.3TPstructure.95.1.4Teststrategy.95.2NetworkTPsforECT.95.2.1Network(S/T).105.2.1.1Serveduserprocedures.105.2.1.1.1Implicitlinkageprocedures.105.2.1.1.2Explicitlinkageprocedures.165.2.1.2Remoteuserprocedures.315.2.2Network(T).365.2.2.1Serveduserconnected.365.2.2.1.1Mechanismtoavoidloopingofuncontrolledcircuits.365.2.2.1.2CalltransferperformedbythepublicISDN,serveduserisconnectedtotheprivateISDN.375.2.2.2Remoteuserconnected.446Compliance.457Requirementsforacomprehensivetestingservice.46AnnexA(informative):ChangeswithrespecttothepreviousEN301065-5.47A.1ChangeswithrespecttothepreviousEN300369-4V1.2.4.47A.2Relationshipbetweenedition1andV1.2.4.47History.48SIST EN 300 369-5 V1.3.1:2005

ETSIETSIEN300369-5V1.3.1(2002-05)4IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinETSISR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://webapp.etsi.org/IPR/home.asp).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinETSISR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSITechnicalCommitteeServicesandProtocolsforAdvancedNetworks(SPAN).Thepresentdocumentispart5ofamulti-partdeliverablecoveringtheDigitalSubscriberSignallingSystemNo.one(DSS1)protocolspecificationfortheIntegratedServicesDigitalNetwork(ISDN)ExplicitCallTransfer(ECT)supplementaryservice,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:17May2002DateoflatestannouncementofthisEN(doa):31August2002DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):28February2003DateofwithdrawalofanyconflictingNationalStandard(dow):28February2003SIST EN 300 369-5 V1.3.1:2005

ETSIETSIEN300369-5V1.3.1(2002-05)51ScopeThepresentdocumentspecifiestheTestSuiteStructureandTestPurposes(TSS&TP)fortheNetworksideoftheTreferencepointorcoincidentSandTreferencepoint(asdefinedinITU-TRecommendationI.411[7])ofimplementationsconformingtothestagethreestandardfortheExplicitCallTransfer(ECT)supplementaryserviceforthepan-EuropeanIntegratedServicesDigitalNetwork(ISDN)bymeansoftheDigitalSubscriberSignallingSystemNo.one(DSS1)protocol,EN300369-1[1].AfurtherpartofthepresentdocumentspecifiestheAbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformabasedonthepresentdocument.OtherpartsspecifytheTSS&TPandtheATSandpartialPIXITproformafortheUsersideoftheTreferencepointorcoincidentSandTreferencepointofimplementationsconformingtoEN300369-1[1].2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublicationand/oreditionnumberorversionnumber)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.[1]ETSIEN300369-1(V1.2.4):"IntegratedServicesDigitalNetwork(ISDN);ExplicitCallTransfer(ECT)supplementaryservice;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part1:Protocolspecification".[2]ETSIEN300369-2(V1.2.4):"IntegratedServicesDigitalNetwork(ISDN);ExplicitCallTransfer(ECT)supplementaryservice;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecification".[3]ISO/IEC9646-1:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[4]ISO/IEC9646-2:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part2:AbstractTestSuiteSpecification".[5]ETSIEN300141-2(V1.2.4):"IntegratedServicesDigitalNetwork(ISDN);CallHold(HOLD)supplementaryservice;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecification".[6]ETSIEN300196-1(V1.2.2):"IntegratedServicesDigitalNetwork(ISDN);Genericfunctionalprotocolforthesupportofsupplementaryservices;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part1:Protocolspecification".[7]ITU-TRecommendationI.411(1993):"ISDNuser-networkinterfaces-Referenceconfigurations".[8]ETSIEN300403-1:"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Signallingnetworklayerforcircuit-modebasiccallcontrol;Part1:Protocolspecification[ITU-TRecommendationQ.931(1993),modified]".[9]ITU-TRecommendationI.112(1993):"VocabularyandtermsforISDNs".[10]ITU-TRecommendationE.164(1997):"Theinternationalpublictelecommunicationnumberingplan".[11]ITU-TRecommendationI.210(1993):"PrinciplesoftelecommunicationservicessupportedbyanISDNandthemeanstodescribethem".SIST EN 300 369-5 V1.3.1:2005

ETSIETSIEN300369-5V1.3.1(2002-05)6[12]ETSIEN300403-3(V1.2.2):"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Signallingnetworklayerforcircuit-modebasiccallcontrol;Part3:ProtocolImplementationConformanceStatement(PICS)proformaspecification".[13]ETSIETS300369-5:"IntegratedServicesDigitalNetwork(ISDN);ExplicitCallTransfer(ECT)supplementaryservice;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part5:TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetwork".[14]ETSIETS300369-6:"IntegratedServicesDigitalNetwork(ISDN);ExplicitCallTransfer(ECT)supplementaryservice;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part6:AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforthenetwork".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:3.1.1DefinitionsrelatedtoconformancetestingAbstractTestSuite(ATS):RefertoISO/IEC9646-1[3].ImplementationUnderTest(IUT):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:RefertoISO/IEC9646-1[3].3.1.2DefinitionsrelatedtoEN300369-1CallHeldauxiliarystate:SeeEN300196-1[6],clause7.1.2.CallReference(CR):SeeEN300403-1[8],clause4.3.component:SeeEN300196-1[6],clause3.1.Idleauxiliarystate:SeeEN300196-1[6],clause7.1.2.IntegratedServicesDigitalNetwork(ISDN):SeeITU-TRecommendationI.112[9],definition308.ISDNnumber:numberconformingtothenumberingandstructurespecifiedinITU-TRecommendationE.164invokecomponent:wherereferenceismadetoan"xxxx"invokecomponent,aninvokecomponentismeantwithitsoperationvaluesettothevalueoftheoperation"xxxx"NOTE:SeeEN300196-1[6],clause8.2.2.1.network:DSS1protocolentityatthenetworksideoftheuser-networkinterfacewhereaTreferencepointorcoincidentSandTreferencepointappliesnetwork(S/T):DSS1protocolentityatthenetworksideoftheuser-networkinterfacewhereacoincidentSandTreferencepointappliesnetwork(T):DSS1protocolentityatthenetworksideoftheuser-networkinterfacewhereaTreferencepointapplies(NetworkconnectedtoPrivateISDN)SIST EN 300 369-5 V1.3.1:2005

ETSIETSIEN300369-5V1.3.1(2002-05)7returnerrorcomponent:wherereferenceismadetoan"xxxx"returnerrorcomponent,anreturnerrorcomponentismeantwithitsoperationvaluesettothevalueoftheoperation"xxxx"NOTE:SeeEN300196-1[6],clause8.2.2.3.returnresultcomponent:wherereferenceismadetoan"xxxx"returnresultcomponent,anreturnresultcomponentismeantwithitsoperationvaluesettothevalueoftheoperation"xxxx"NOTE:SeeEN300196-1[6],clause8.2.2.2.serveduser:userwhoinvokestheECTsupplementaryserviceservice;telecommunicationservice:SeeITU-TRecommendationI.112[9],definition201.supplementaryservice:SeeITU-TRecommendationI.210[11],clause2.4.3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ATMAbstractTestMethodATSAbstractTestSuiteCOLRCOnnectedLineRestrictionCRCallReferenceCR1CRforthefirstcallinaTPCR2CRforthesecondcallinaTPCR3CRforthethirdcallinaTPDSS1DigitalSubscriberSignallingSystemNo.oneECTExplicitCallTransfer(Held)CallHeldauxiliarystate(Idle)IdleauxiliarystateISDNIntegratedServicesDigitalNetworkIUTImplementationundertestN02OverlapSendingcallstateN03OutgoingCallProceedingcallstateN04CallDeliveredcallstateN06CallPresentcallstateN07CallReceivedcallstateN08ConnectRequestcallstateN09IncomingCallProceedingcallstateN10ActivecallstateN12DisconnectIndicationcallstateN19ReleaseRequestcallstateN25OverlapReceivingcallstatePICSProtocolImplementationConformanceStatementPIXITProtocolImplementationeXtraInformationforTestingTPTestPurposeTSSTestSuiteStructureU07CallReceivedcallstate(user)U08ConnectRequestcallstate(user)U10Activecallstate(user)SIST EN 300 369-5 V1.3.1:2005

ETSIETSIEN300369-5V1.3.1(2002-05)84TestSuiteStructure(TSS)ECT-NetworkNetwork(S/T)Network(T)ServeduserproceduresRemoteuserprocedures(03)ServeduserconnectedRemoteuserconnected(06)Implicitlinkageprocedures(01)Explicitlinkageprocedures(02)Mechanismtoavoidloopingofuncontrolledcircuits(04)Transferperformedinpublicnetwork(05)NOTE:NumbersinbracketsrepresentgroupnumbersandareusedinTPidentifiers.Figure1:Testsuitestructure5TestPurposes(TP)5.1IntroductionForeachtestrequirementaTPisdefined.5.1.1TPnamingconventionTPsarenumbered,startingat001,withineachgroup.GroupsareorganizedaccordingtotheTSS.Additionalreferencesareaddedtoidentifytheactualsupplementaryserviceandwhetheritappliestothenetworkortheuser(seetable1).Table1:TPidentifiernamingconventionschemeIdentifier:__=supplementaryservice:e.g."ECT"=typeofIUT:UUserNNetwork=group2digitfieldrepresentinggroupreferenceaccordingtoTSS=sequentialnumber(001-999)5.1.2SourceofTPdefinitionTheTPsarebasedonEN300369-1[1].SIST EN 300 369-5 V1.3.1:2005

ETSIETSIEN300369-5V1.3.1(2002-05)95.1.3TPstructureEachTPhasbeenwritteninamannerwhichisconsistentwithallotherTPs.TheintentionofthisistomaketheTPsmorereadableandcheckable.Aparticularstructurehasbeenusedandthisisillustratedintable2.ThistableshouldbereadinconjunctionwithanyTP,i.e.useaTPasanexampletofullyunderstandthetable.Table2:StructureofasingleTPTPPartTextExampleHeadertabseetable1tabclause0.0.0tabvalid,invalid,inopportuneCR.mandatory,optional,conditionalStimulusEnsurethattheIUTintheECTRequeststateandwithCR1in()N10(Idle),N10(Held),etc.andwithCR2in()"andwithCR3in()"seebelowformessagestructurereceivingaXXXXmessageortorequesta.Reactionsends,saves,does,etc.usingen-blocsending,.iftheactionissendingseebelowformessagestructure,etc.andentersand/orandremainsinthesamestate(s)orandentersstatewithCRMessagestructuremessagecontainingaSETUP,FACILITY,CONNECT,.a)informationelementwithb)aencodedasorincludingandbacktoaorb,Bearercapability,Facility,.NOTE:TextinitalicswillnotappearinTPsandtextbetween<>isfilledinforeachTPandmaydifferfromoneTPtothenext.5.1.4TeststrategyAsthebasestandardEN300369-1[1]containsnoexplicitrequirementsfortesting,theTPsweregeneratedasaresultofananalysisofthebasestandardandthePICSspecificationEN300369-2[2].Thecriteriaappliedincludethefollowing:-onlytherequirementsfromthepointofviewoftheTorcoincidentSandTreferencepointareconsidered;-whetherornotatestcasecanbebuiltfromtheTPisnotconsidered.5.2NetworkTPsforECTAllPICSitemsreferredtointhisclauseareasspecifiedinEN300369-2[2]unlessindicatedotherwise.WherethereisareferencetotheHOLDPICSthisreferstoEN300141-2[5]andwherethereisareferencetotheBasicCallPICSthisreferstoEN300403-3[12].Unlessspecified:-Themessagesindicatedarevalidandcontainatleastthemandatoryinformationelementsandpossiblyoptionalinformationelements.-Theinformationelementsindicatedarevalidandcontainatleastthemandatoryparametersandpossiblyoptionalparameters.SIST EN 300 369-5 V1.3.1:2005

ETSIETSIEN300369-5V1.3.1(2002-05)105.2.1Network(S/T)Selection:IUTsupportsrequirementsatthecoincidentSandTreferencepoint.PICS:R.3.1.5.2.1.1Serveduserprocedures5.2.1.1.1ImplicitlinkageproceduresECT_N01_001clauses9.2.1.1,9.2.3mandatoryEnsurethattheIUTintheECTIdlestateandwithCR1instateN10(Held)andCR2instateN10(Idle)receivingavalidFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,sendsaDISCONNECTmessagewithCR1containingaFacilityinformationelementwithaEctExecutereturnresultcomponentandentersstateN12(CR1);sendsaDISCONNECTmessagewithCR2andentersstateN12(CR2);andremainsinthesameECTstate.ECT_N01_002clauses(seenote.1.1,9.2.3)optionalEnsurethattheIUTintheECTIdlestateandwithCR1instateN04(Held)andCR2instateN10(Idle)receivingavalidFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,sendsaDISCONNECTmessagewithCR1containingaFacilityinformationelementwithaEctExecutereturnresultcomponentandentersstateN12(CR1);sendsaDISCONNECTmessagewithCR2andentersstateN12(CR2);andremainsinthesameECTstate.Selection:IUTsupportsECTfromstateN04.PICS:MC11.Selection:IUTsupportsHOLDinstateN04.HOLDPICS:MC3.2.ECT_N01_003clauses9.2.1.1,9.2.3optionalEnsurethattheIUTintheECTIdlestateandwithCR1instateN10(Held)andCR2instateN04(Idle)receivingavalidFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,sendsaDISCONNECTmessagewithCR1containingaFacilityinformationelementwithaEctExecutereturnresultcomponentandentersstateN12(CR1);sendsaDISCONNECTmessagewithCR2andentersstateN12(CR2);andremainsinthesameECTstate.Selection:IUTsupportsECTfromstateN04.PICS:MC11.ECT_N01_004clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR1incallstateN10(Held)andCR2incallstateN10(Idle)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponentandtheECTsupplementaryserviceisnotsubscribedto,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"notSubscribed"andremainsinthesameECTandcallstates.ECT_N01_005clause9.2.1.2optionalEnsurethattheIUTintheECTIdlestatewithCR1incallstateN10(Held)andCR2incallstateN04(Idle)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponentandtheECTsupplementaryserviceisnotsubscribedto,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"notSubscribed"andremainsinthesameECTandcallstates.Selection:IUTsupportsECTfromstateN04.PICS:MC11.SIST EN 300 369-5 V1.3.1:2005

ETSIETSIEN300369-5V1.3.1(2002-05)11ECT_N01_006clause9.2.1.2optionalEnsurethattheIUTintheECTIdlestatewithCR1incallstateN04(Held)andCR2incallstateN10(Idle)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponentandtheECTsupplementaryserviceisnotsubscribedto,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"notSubscribed"andremainsinthesameECTandcallstates.Selection:IUTsupportsECTfromstateN04.PICS:MC11.Selection:IUTsupportsHOLDinstateN04.HOLDPICS:MC3.2.ECT_N01_007clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR1incallstateN10(Held)andCR2incallstateN10(Idle)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponentandthenetworkrecognizesaloopingcondition,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"notAvailable"andremainsinthesameECTandcallstates.ECT_N01_008clause9.2.1.2optionalEnsurethattheIUTintheECTIdlestatewithCR1incallstateN10(Held)andCR2incallstateN04(Idle)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponentandthenetworkrecognizesaloopingcondition,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"notAvailable"andremainsinthesameECTandcallstates.Selection:IUTsupportsECTfromstateN04.PICS:MC11.ECT_N01_009clause9.2.1.2optionalEnsurethattheIUTintheECTIdlestatewithCR1incallstateN04(Held)andCR2incallstateN10(Idle)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponentandthenetworkrecognizesaloopingcondition,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"notAvailable"andremainsinthesameECTandcallstates.Selection:IUTsupportsECTfromstateN04.PICS:MC11.Selection:IUTsupportsHOLDinstateN04.HOLDPICS:MC3.2.ECT_N01_010clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR1incallstateN10(Held)andCR2incallstateN10(Idle)receivingaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_011clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR1incallstateN10(Held)andCR2incallstateN04(Idle)receivingaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_012clause9.2.1.2optionalEnsurethattheIUTintheECTIdlestatewithCR1incallstateN04(Held)andCR2incallstateN10(Idle)receivingaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.Selection:IUTsupportsHOLDinstateN04.HOLDPICS:MC3.2.ECT_N01_013clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN02andCR1incallstateN10(Idle)receivingaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.SIST EN 300 369-5 V1.3.1:2005

ETSIETSIEN300369-5V1.3.1(2002-05)12ECT_N01_014clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN03andCR1incallstateN10(Idle)receivingaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_015clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN06andCR1incallstateN10(Idle)receivingaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_016clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN07andCR1incallstateN10(Idle)receivingaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_017clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN09andCR1incallstateN10(Idle)receivingaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_018clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN12andCR1incallstateN10(Idle)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_019clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN19andCR1incallstateN10(Idle)receivingaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_020clause9.2.1.2optionalEnsurethattheIUTintheECTIdlestatewithCR2incallstateN25andCR1incallstateN10(Idle)receivingaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.Selection:IUTsupportsoverlapreceiving.BasicCallPICS:MCn2.2.ECT_N01_021clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN02andCR1incallstateN04(Idle)receivingaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_022clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN03andCR1incallstateN04(Idle)receivingaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_023clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN06andCR1incallstateN04(Idle)receivingaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.SIST EN 300 369-5 V1.3.1:2005

ETSIETSIEN300369-5V1.3.1(2002-05)13ECT_N01_024clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN07andCR1incallstateN04(Idle)receivingaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_025clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN09andCR1incallstateN04(Idle)receivingaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_026clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN12andCR1incallstateN04(Idle)receivingaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_027clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN19andCR1incallstateN04(Idle)receivingaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_028clause9.2.1.2optionalEnsurethattheIUTintheECTIdlestatewithCR2incallstateN25andCR1incallstateN04(Idle)receivingaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.Selection:IUTsupportsoverlapreceiving.BasicCallPICS:MCn2.2.ECT_N01_029clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN02andCR1incallstateN10(Held)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_030clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN03andCR1incallstateN10(Held)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_031clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN06andCR1incallstateN10(Held)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_032clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN07andCR1incallstateN10(Held)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_033clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN09andCR1incallstateN10(Held)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.SIST EN 300 369-5 V1.3.1:2005

ETSIETSIEN300369-5V1.3.1(2002-05)14ECT_N01_034clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN12andCR1incallstateN10(Held)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_035clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR2incallstateN19andCR1incallstateN10(Held)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.ECT_N01_036clause9.2.1.2optionalEnsurethattheIUTintheECTIdlestatewithCR2incallstateN25andCR1incallstateN10(Held)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.Selection:IUTsupportsoverlapreceiving.BasicCallPICS:MCn2.2.ECT_N01_037clause9.2.1.2optionalEnsurethattheIUTintheECTIdlestatewithCR2incallstateN02andCR1incallstateN04(Held)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.Selection:IUTsupportsHOLDinstateN04.HOLDPICS:MC3.2.ECT_N01_038clause9.2.1.2optionalEnsurethattheIUTintheECTIdlestatewithCR2incallstateN03andCR1incallstateN04(Held)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.Selection:IUTsupportsHOLDinstateN04.HOLDPICS:MC3.2.ECT_N01_039clause9.2.1.2optionalEnsurethattheIUTintheECTIdlestatewithCR2incallstateN06andCR1incallstateN04(Held)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.Selection:IUTsupportsHOLDinstateN04.HOLDPICS:MC3.2.ECT_N01_040clause9.2.1.2optionalEnsurethattheIUTintheECTIdlestatewithCR2incallstateN07andCR1incallstateN04(Held)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.Selection:IUTsupportsHOLDinstateN04.HOLDPICS:MC3.2.ECT_N01_041clause9.2.1.2optionalEnsurethattheIUTintheECTIdlestatewithCR2incallstateN09andCR1incallstateN04(Held)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.Selection:IUTsupportsHOLDinstateN04.HOLDPICS:MC3.2.SIST EN 300 369-5 V1.3.1:2005

ETSIETSIEN300369-5V1.3.1(2002-05)15ECT_N01_42clause9.2.1.2optionalEnsurethattheIUTintheECTIdlestatewithCR2incallstateN12andCR1incallstateN04(Held)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.Selection:IUTsupportsHOLDinstateN04.HOLDPICS:MC3.2.ECT_N01_43clause9.2.1.2optionalEnsurethattheIUTintheECTIdlestatewithCR2incallstateN19andCR1incallstateN04(Held)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.Selection:IUTsupportsHOLDinstateN04.HOLDPICS:MC3.2.ECT_N01_44clause9.2.1.2optionalEnsurethattheIUTintheECTIdlestatewithCR2incallstateN25andCR1incallstateN04(Held)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1andCR2states.Selection:IUTsupportsHOLDinstateN04.HOLDPICS:MC3.2.Selection:IUTsupportsoverlapreceiving.BasicCallPICS:MCn2.2.ECT_N01_045clause9.2.1.2optionalEnsurethattheIUT,intheECTIdlestatewithCR1incallstateN10(Held),CR2incallstateN04(Idle)andCR3incallstateN10(Idle),receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1,CR2andCR3states.Selection:IUTsupportsHOLDinstateN04.HOLDPICS:MC3.2.Selection:IUTsupports3ormorecallsoneofwhichmaybeheld.ECT_N01_046clause9.2.1.2optionalEnsurethattheIUT,intheECTIdlestatewithCR1incallstateN10(Held),CR2incallstateN10(Idle)andCR3incallstateN10(Idle),receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1,CR2andCR3states.Selection:IUTsupports3ormorecallsoneofwhichmaybeheld.ECT_N01_047clause9.2.1.2optionalEnsurethattheIUT,intheECTIdlestatewithCR1incallstateN04(Held),CR2incallstateN10(Idle)andCR3incallstateN10(Idle),receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1,CR2andCR3states.Selection:IUTsupportsHOLDinstateN04.HOLDPICS:MC3.2.Selection:IUTsupports3ormorecallsoneofwhichmaybeheld.ECT_N01_048clause9.2.1.2optionalEnsurethattheIUT,intheECTIdlestatewithCR1incallstateN04(Held),CR2incallstateN04(Idle)andCR3incallstateN10(Idle),receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponent,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"invalidCallState"andremainsinthesameECT,CR1,CR2andCR3states.Selection:IUTsupportsHOLDinstateN04.HOLDPICS:MC3.2.Selection:IUTsupports3ormorecallsoneofwhichmaybeheld.SIST EN 300 369-5 V1.3.1:2005

ETSIETSIEN300369-5V1.3.1(2002-05)16ECT_N01_049clause9.2.1.2mandatoryEnsurethattheIUTintheECTIdlestatewithCR1incallstateN10(Held)andCR2incallstateN10(Idle)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponentandtheECTsupplementaryserviceisinvokedwhenanotherserviceisalreadyactivatedandthisserviceinteractionisnotallowed,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"supplementaryServiceInteractionNotAllowed"andremainsinthesameECTandcallstates.ECT_N01_050clause9.2.1.2optionalEnsurethattheIUTintheECTIdlestatewithCR1incallstateN10(Held)andCR2incallstateN04(Idle)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponentandtheECTsupplementaryserviceisinvokedwhenanotherserviceisalreadyactivatedandthisserviceinteractionisnotallowed,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"supplementaryServiceInteractionNotAllowed"andremainsinthesameECTandcallstates.Selection:IUTsupportsECTfromstateN04.PICS:MC11.ECT_N01_051clause9.2.1.2optionalEnsurethattheIUTintheECTIdlestatewithCR1incallstateN04(Held)andCR2incallstateN10(Idle)receivingaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutecomponentandtheECTsupplementaryserviceisinvokedwhenanotherserviceisalreadyactivatedandthisserviceinteractionisnotallowed,respondswithaFACILITYmessagewithCR1containingaFacilityinformationelementwithanEctExecutereturnerrorcomponentindicating"supplementaryServiceInteractionNotAllowed"andremainsinthesameECTandcallstates.Selection:IUTsupportsHOLDinstateN04.HOLDPICS:MC3.2.Selection:IUTsupportsECTfromstateN04.PICS:MC11.5.2.1.1.2ExplicitlinkageproceduresSelection:IUTsupportsexplicitlinkageoption.PICS:MC10.ECT_N02_001clause9.2.2.1.1optionalEnsurethattheIUTintheECTIdlestatewithCR1incallstateN10(Held)andCR2incallstateN04(Idle)andCR3incallstateN10(Idle)receivingavalidFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctLinkIdRequestinvokecomponentandtherequestisaccepted,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctLinkIdRequestreturnresultcomponentincludingaLinkIdvalueandremainsinthesameECTandcallstates.Selection:IUTsupportsECTfromstateN04.PICS:MC11.Selection:IUTcanhandleatleast2activenon-heldcallsandatleastoneheldcall,allonthesamedatalinkconnection.ECT_N02_002clause9.2.2.1.1optionalEnsurethattheIUTintheECTIdlestatewithCR1incallstateN04(Held)andCR2incallstateN10(Idle)andCR3incallstateN10(Idle)receivingavalidFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctLinkIdRequestinvokecomponentandtherequestisaccepted,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctLinkIdRequestreturnresultcomponentincludingaLinkIdvalueandremainsinthesameECTandcallstates.Selection:IUTsupportsECTfromstateN04.PICS:MC11.Selection:IUTsupportsHOLDinstateN04.HOLDPICS:MC3.2.Selection:IUTcanhandleatleast2activenon-heldcallsandatleastoneheldcall,allonthesamedatalinkconnection.ECT_N02_003clause9.2.2.1.1optionalEnsurethattheIUTintheECTIdlestatewithCR1incallstateN10(Held)andCR2incallstateN10(Idle)andCR3incallstateN10(Idle)receivingavalidFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctLinkIdRequestinvokecomponentandtherequestisaccepted,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctLinkIdRequestreturnresultcomponentincludingaLinkIdvalueandremainsinthesameECTandcallstates.SIST EN 300 369-5 V1.3.1:2005

ETSIETSIEN300369-5V1.3.1(2002-05)17Selection:IUTcanhandleatleast2activenon-heldcallsandatleastoneheldcall,allonthesamedatalinkconnection.ECT_N02_004clause9.2.2.1.1optionalEnsurethattheIUTintheECTIdlestatewithCR1incallstateN10(Idle)andCR2incallstateN04(Idle)receivingavalidFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctLinkIdRequestinvokecomponentandtherequestisaccepted,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctLinkIdRequestreturnresultcomponentincludingaLinkIdvalueandremainsinthesameECTandcallstates.Selection:IUTsupportsECTfromstateN04.PICS:MC11.Selection:IUTsupportsECTwithneithercallintheHeldstatePICS:MC16.ECT_N02_005clause9.2.2.1.1optionalEnsurethattheIUTintheECTIdlestatewithCR1incallstateN04(Idle)andCR2incallstateN10(Idle)receivingavalidFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctLinkIdRequestinvokecomponentandtherequestisaccepted,respondswithaFACILITYmessagewithCR2containingaFacilityinformationelementwithanEctLinkIdReque
...