SIST EN 300 805-1 V1.2.1:2005
(Main)Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Circuit mode basic services; Network Layer (NL); Part 1: Test Suite Structure and Test Purposes (TSS&TP) specification
- Abstract
Enhancement of the ETS 300 805-1 in order to align with the IS version.
- Status
- Published
- Publication Date
- 28-Feb-2005
- Technical Committee
- SPN - Services and Protocols for Networks
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Mar-2005
- Due Date
- 01-Mar-2005
- Completion Date
- 01-Mar-2005
- Mandate
- T-245
SIST EN 300 805-1 V1.2.1:2005 is the Slovenian adoption of the ETSI standard for the Private Integrated Services Network (PISN) inter-exchange signalling protocol, circuit mode basic services, Network Layer (NL), Part 1. It specifies the Test Suite Structure (TSS) and Test Purposes (TPs) used to check conformance of the Network Layer at the Q-reference point between Private Integrated Services Network Exchanges (PINXs).
What does SIST EN 300 805-1 V1.2.1:2005 specify?
SIST EN 300 805-1 V1.2.1:2005 specifies how to structure conformance tests and which behaviours to test for PISN Network Layer circuit mode basic services. It is aimed at interoperability testing of basic call control and related procedures.
The document covers the procedures in EN 300 172 and also those parts of EN 301048 that relate to the transit counter in Basic Call procedures. It uses the conformance testing methodology of ISO/IEC 9646-1 and ISO/IEC 9646-2, and it applies to Basic Call support at the Q-reference point between interconnected PINXs.
The document is organized into these main parts:
- Clause 4 - Test Suite Structure
- Clause 5 - Test Purposes
- Clause 6 - Compliance
- Clause 7 - Requirements for a comprehensive testing service
- Annex A - Backward compatibility
What are the key requirements of SIST EN 300 805-1 V1.2.1:2005?
SIST EN 300 805-1 V1.2.1:2005 is built around test objectives for call control, call clearing, message segmentation, STATUS handling, and error cases. In practice, it tells a test designer what behaviours the Implementation Under Test (IUT) should show, and it gives the state-based conditions needed to verify them.
Test Suite Structure and test selection
Clause 4 organizes the Test Suite Structure as a tree:
- protocol control common to all behaviours
- role-based call control for Originating, Terminating, Transit, Incoming Gateway, and Outgoing Gateway PINXs
- call phases such as Call Establishing, Call Clearing, Message Segmentation, STATUS Procedures, and Layer Management
- test nature such as valid, invalid, and inopportune behaviour
This matters because it lets a tester pick the right branch for the IUT role and feature set instead of running unrelated cases.
Test Purposes and identifiers
Clause 5 explains how Super Test Purposes (STPs) are reviewed and then turned into final TPs that map to individual test cases in the Abstract Test Suite (ATS). It also defines the TP naming scheme and the way optional behaviour is selected with Protocol Implementation Conformance Statement (PICS) and Protocol Implementation eXtra Information for Testing (PIXIT).
In practice, this makes the test set traceable: each final TP ties back to a specific requirement, state, and supported option.
Call establishment, progress, and collisions
Clause 5.3 covers the main call setup behaviour for outgoing, incoming, terminating, transit, and gateway PINXs. It includes bearer selection, channel identification, overlap sending and receiving, CALL PROCEEDING, ALERTING, CONNECT, CONNECT ACKNOWLEDGE, PROGRESS, and collision handling.
For readers, this is the core of interoperability testing. It checks whether the IUT chooses channels correctly, reacts to incomplete addressing, handles simultaneous calls, and uses the right signalling sequence.
Call clearing and exception conditions
Clause 5.3.2 covers call clearing, clear collisions, and exception conditions. It checks that the IUT sends and reacts to DISCONNECT, RELEASE, and RELEASE COMPLETE in the correct states and timer conditions.
This is important because failed calls must be released cleanly, with the channel and call reference brought back to a usable state.
Message segmentation and reassembly
Clause 5.3.3 covers segmentation and reassembly when a message exceeds the implemented Signalling Carriage Mechanism (SCM) information field length. It also tests invalid and inopportune segmented messages and the timer used during reassembly.
This matters for implementations that carry longer signalling messages, because they must split, reassemble, and reject malformed segments consistently.
STATUS procedures and Layer Management
Clause 5.3.4 tests STATUS and STATUS ENQUIRY handling, including response content, retry timing, and release on repeated unanswered enquiries. Clause 5.3.5 covers Layer Management, including RESTART, restart collision, and related state handling.
These tests verify that the IUT can report and recover its signalling state correctly, which is important for fault recovery and network management.
Protocol error handling
Clause 5.3.6 covers protocol discriminator errors, messages that are too short, call reference errors, message type and sequence errors, and information element errors. It also includes Signalling Carriage Mechanism reset and failure behaviour.
For implementers, this is the defensive side of conformance: the IUT must reject malformed signalling in a controlled way.
What terms does SIST EN 300 805-1 V1.2.1:2005 define?
- Abstract Test Suite (ATS) - the set of abstract test cases derived from the TPs.
- Implementation Under Test (IUT) - the equipment or system being checked.
- Protocol Implementation Conformance Statement (PICS) - the declaration used to select applicable tests.
- Protocol Implementation eXtra Information for Testing (PIXIT) - extra implementation data needed to choose or parameterize tests.
- Private Integrated Services Network (PISN) - the private network environment covered by the standard.
- Private Integrated Network Exchange (PINX) - a network exchange inside the PISN.
- Signalling Carriage Mechanism (SCM) - the transport mechanism whose information field can force segmentation.
- Test Suite Structure (TSS) - the tree that organizes the test purposes.
Who uses SIST EN 300 805-1 V1.2.1:2005?
SIST EN 300 805-1 V1.2.1:2005 is used by equipment vendors, conformance test labs, and quality teams working on PISN and QSIG basic call control implementations. It is also useful for buyers or certification teams who need a defined test basis for interoperability checks at the Q-reference point.
What changed in SIST EN 300 805-1 V1.2.1:2005 from the previous edition?
SIST EN 300 805-1 V1.2.1:2005 is an enhancement of ETS 300 805-1 to align it with the IS version.
Which standards are used with SIST EN 300 805-1 V1.2.1:2005?
- EN 300 172 - the base specification for circuit-mode basic services that most TPs reference.
- EN 301048 - adds the transit counter network feature covered by some TPs.
- ISO/IEC 9646-1 and ISO/IEC 9646-2 - provide the conformance testing methodology and ATS framework.
- ETS 300475-1 - defines the Q-reference point used for applicability.
- ITU-T Recommendation I.112 - supplies general ISDN vocabulary used for definitions.
- ITU-T Recommendation Q.931 - related signalling layer 3 context for basic call control.
- Part 2 of this multi-part EN - the companion Abstract Test Suite specification.
What does the SIST EN 300 805-1 V1.2.1:2005 document contain?
The document contains a tree-structured TSS, detailed TP writing rules, and a large set of state-based TP descriptions for call setup, clearing, segmentation, STATUS, layer management, and protocol error handling. Clause 5 also explains TP identifiers, selection rules, and how PICS and PIXIT information affects applicability.
It includes Figure 1 for the overall PSS1 Layer 3 test suite structure, Table 1 and Table 2 for TP writing rules, and Annex A for backward compatibility. The document also provides many specific test objectives that describe message type, call state, and expected response so they can be turned into executable conformance tests.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST EN 300 805-1 V1.2.1:2005 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Circuit mode basic services; Network Layer (NL); Part 1: Test Suite Structure and Test Purposes (TSS&TP) specification". This standard covers: Enhancement of the ETS 300 805-1 in order to align with the IS version.
Enhancement of the ETS 300 805-1 in order to align with the IS version.
SIST EN 300 805-1 V1.2.1:2005 is classified under the following ICS (International Classification for Standards) categories: 33.040.35 - Telephone networks. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 300 805-1 V1.2.1:2005 is associated with the following European legislation: Standardization Mandates: T-245. When a standard is cited in the Official Journal of the European Union, products manufactured in conformity with it benefit from a presumption of conformity with the essential requirements of the corresponding EU directive or regulation.
SIST EN 300 805-1 V1.2.1:2005 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Zasebno omrežje z integriranimi storitvami (PISN) - Medcentralni signalizacijski protokol - Vodovna osnovna storitev - Omrežna plast (NL) - 1. del: Zgradba preskušalnega niza in nameni preskušanja (TSS&TP) - SpecifikacijaPrivate Integrated Services Network (PISN); Inter-exchange signalling protocol; Circuit mode basic services; Network Layer (NL); Part 1: Test Suite Structure and Test Purposes (TSS&TP) specification33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 300 805-1 Version 1.2.1SIST EN 300 805-1 V1.2.1:2005en01-marec-2005SIST EN 300 805-1 V1.2.1:2005SLOVENSKI
STANDARD
ETSIEN300805-1V1.2.1(2000-05)EuropeanStandard(Telecommunicationsseries)PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Circuitmodebasicservices;NetworkLayer(NL);Part1:TestSuiteStructureandTestPurposes(TSS&TP)specificationSIST EN 300 805-1 V1.2.1:2005
ETSIEN300805-1V1.2.1(2000-05)ETSI2ReferenceREN/ECMA-00159-1Keywordscircuitmode,layer3,PINX,PISN,QSIG,testing,TSS&TPETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:+33492944200Fax:+33493654716SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88ImportantnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http://www.etsi.orgThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSIdocumentsisavailableathttp://www.etsi.org/tb/status/Ifyoufinderrorsinthepresentdocument,sendyourcommentto:editor@etsi.frCopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 300 805-1 V1.2.1:2005
ETSIEN300805-1V1.2.1(2000-05)ETSI3ContentsIntellectualPropertyRights.5Foreword.51Scope.62References.63Definitions,symbolsandabbreviations.73.1Definitions.73.2Symbols.83.3Abbreviations.84TestSuiteStructure(TSS).95TestPurposes(TP).105.1IntroductiontoTestPurposes.105.1.1Testpurposesproductionmethod.105.1.2STPidentifier.115.1.3"Final"derivedTPidentifier.115.1.4Standardoptions.125.1.5Messagesegmentation.125.2Testpurposewritingrules.125.2.1Terminating,Originating,Incoming/OutgoingGatewayPINX.135.2.2TransitPINX.145.3TestPurposes.145.3.1ProtocolControlrequirementsforCallEstablishment.155.3.1.1CallRequest.155.3.1.1.1Outgoingside.155.3.1.1.2Incomingside.175.3.1.2Informationchannelselection.175.3.1.2.1Outgoingside.175.3.1.2.2Incomingside-singleinformationchannel.185.3.1.2.3Incomingside-multirate.195.3.1.3OverlapSendingandReceiving.205.3.1.3.1Incomingside.205.3.1.3.2Outgoingside.215.3.1.4CallProceeding.215.3.1.5CallConfirmationindication.225.3.1.6CallConnected.235.3.1.7UseofthePROGRESSmessage.265.3.1.8Callcollisions.275.3.1.9Additionalprogressdescriptions.335.3.2ProtocolControlrequirementsforCallClearing.345.3.2.1Clearing.345.3.2.2ClearCollision.365.3.2.3Exceptionconditions.365.3.3ProtocolControlrequirementsforMessageSegmentation.375.3.3.1Proceduresforsegmentation.375.3.3.2Proceduresforreassembly.385.3.4ProtocolControlrequirementsforSTATUSprocedures.435.3.4.1ReceivingaSTATUSmessage.435.3.4.2Statusenquiryprocedure.455.3.5ProtocolControlrequirementsforLayerManagement.495.3.5.1SendingaRESTART.495.3.5.2ReceiptofRESTART.505.3.5.3RestartCollision.515.3.6ProtocolControlrequirementsforhandlingofprotocolerrorconditions.525.3.6.1Protocoldiscriminatorerror.52SIST EN 300 805-1 V1.2.1:2005
ETSIEN300805-1V1.2.1(2000-05)ETSI45.3.6.2Messagetooshort.535.3.6.3Callreferenceerror.535.3.6.3.1Invalidcallreferenceformat.535.3.6.3.2CallReferenceproceduralerrors.545.3.6.4MessagetypeorMessagesequenceerrors.555.3.6.5GeneralIEerrors.575.3.6.5.1DuplicatedIEs.575.3.6.5.2IEsexceedingmaximumlength.575.3.6.6MandatoryIEerrors.585.3.6.6.1MandatoryIEsmissing.585.3.6.6.2MandatoryIEcontenterror.605.3.6.7Non-mandatoryIEerrors.615.3.6.7.1Non-mandatoryIEnotrecognized.615.3.6.7.2Non-mandatoryIEcontenterror.635.3.6.8SignallingCarriageMechanismreset.645.3.6.9SignallingCarriageMechanismfailure.645.3.7OriginatingPINXCallControlrequirements.655.3.8TerminatingPINXCallControlrequirements.675.3.8.1CallEstablishment.675.3.8.2CallClearinginitiatedbytheTerminatingPINX.695.3.9IncomingGatewayPINXCallControlrequirements.695.3.9.1CallEstablishment.705.3.10OutgoingGatewayPINXCallControlrequirements.715.3.10.1CallEstablishment.725.3.11CallControlrequirementsforaTransitPINX.735.3.11.1CallEstablishment.735.3.11.2CallClearing.825.3.11.2.1CallclearingnotinitiatedbythetransitPINX.825.3.11.2.2CallClearinginitiatedbytheTransitPINX.865.3.11.3HandlingofBasicCallIEsataTransitPINX.885.3.12ProtocolControlrequirementsfortheuseoftheSignallingCarriageMechanism.935.3.13Verificationofstate.945.3.13.1ProtocolControlState.945.3.13.2LayerManagementState.945.4DistributionofTPsoverTestSuiteStructure.946Compliance.957Requirementsforacomprehensivetestingservice.95AnnexA(informative):Backwardcompatibility.96A.1Introduction.96A.2ETS300172.96A.2.1ETS300172editions1and2.96A.2.2ETS300172edition3.96A.3ISO/IEC11572.96A.3.1ISO/IEC11572edition1.96A.3.2ISO/IEC11572edition2andamendments1and2.96A.4ECMA-143.97A.4.1ECMA-143editions1and2.97A.4.2ECMA-143edition3.97A.5ISO/IEC15056edition1andECMA-225edition2.97Bibliography.98Index.99History.105SIST EN 300 805-1 V1.2.1:2005
ETSIEN300805-1V1.2.1(2000-05)ETSI5IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinSR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinSR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyEuropeanComputerManufacturersAssociation(ECMA)onbehalfofitsmembersandthoseoftheEuropeanTelecommunicationsStandardsInstitute(ETSI).Thepresentdocumentispart1ofamulti-partENcoveringthePrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Circuitmodebasicservices;NetworkLayer(NL),asidentifiedbelow:Part1:"TestSuiteStructureandTestPurposes(TSS&TP)specification";Part2:"AbstractTestSuite(ATS)specification".NationaltranspositiondatesDateofadoptionofthisEN:28April2000DateoflatestannouncementofthisEN(doa):31July2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31January2001DateofwithdrawalofanyconflictingNationalStandard(dow):31January2001SIST EN 300 805-1 V1.2.1:2005
ETSIEN300805-1V1.2.1(2000-05)ETSI61ScopeThepresentdocumentspecifiestheTestSuiteStructure(TSS)andTestPurposes(TPs)fortheNetworkLayer,CircuitModeBasicServicesoftheInter-exchangesignallingprotocolforPrivateIntegratedServicesNetworks(PISN).TheobjectiveofthisTSSandTPsspecificationistoprovideconformancetestswhichgiveahighprobabilityofinter-operabilityoftheNetworkLayer.TheTSSandTPsspecificationcoverstheproceduresdescribedinEN300172[2].InadditionthisTSS&TPspecificationcoversthosepartsofEN301048[1]whichrelatetotheuseofthetransitcounterinconnectionwithBasicCallprocedures.NOTE1:ThepartsofEN301048[1]includedarethosewhichareequivalenttoETS300172[3]annexZB.NOTE2:SomeoralloftheTPsinthepresentdocumentcanbeusedfortestingequipmentimplementedaccordingtootherPSS1specifications.TheISOstandardforthemethodologyofconformancetesting(ISO/IEC9646-1[7]andISO/IEC9646-2[8])isusedasbasisforthetestmethodology.ThepresentdocumentisapplicabletothesupportofBasicCall,attheQ-referencepointbetweenPrivateIntegratedServicesNetworkExchanges(PINXs)connectedtogetherwithinaPISN.TheQreferencepointisdefinedinETS300475-1[6].2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIEN301048(V1.1):"PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Transitcounteradditionalnetworkfeature[ISO/IEC15056(1997)modified]".[2]ETSIEN300172(V1.4):"PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Circuit-modebasicservices[ISO/IEC11572(1996)modified]".[3]ETSIETS300172:"PrivateTelecommunicationNetwork(PTN);Inter-exchangesignallingprotocol;Circuitmodebasicservices".[4]ETSIETS300239(1995):"PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Genericfunctionalprotocolforthesupportofsupplementaryservices[ISO/IEC11582(1995),modified]".[5]ETSIEN300403-1:"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Signallingnetworklayerforcircuit-modebasiccallcontrol;Part1:Protocolspecification[ITU-TRecommendationQ.931(1993),modified]".[6]ETSIETS300475-1(1995):"PrivateTelecommunicationNetwork(PTN);Referenceconfiguration;Part1:ReferenceconfigurationforPTNeXchanges(PTNX)[ISO/IEC11579-1(1994),modified]".[7]ISO/IEC9646-1(1994):"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".SIST EN 300 805-1 V1.2.1:2005
ETSIEN300805-1V1.2.1(2000-05)ETSI7[8]ISO/IEC9646-2(1994):"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part2:AbstractTestSuitespecification".[9]ISO/IEC11572:"InformationTechnology-Telecommunicationsandinformationexchangebetweensystems-PrivateIntegratedServicesNetwork-Circuitmodebearerservices-Inter-exchangesignallingproceduresandprotocol".[10]ISO/IEC15056(1997):"Informationtechnology-Telecommunicationsandinformationexchangebetweensystems-PrivateIntegratedServicesNetwork-Inter-exchangesignallingprotocol-Transitcounteradditionalnetworkfeature".[11]ITU-TRecommendationI.112(1993):"VocabularyoftermsforISDNs".[12]ITU-TRecommendationQ.931(1998):"SDNuser-networkinterfacelayer3specificationforbasiccallcontrol".[13]ECMA-143:"PrivateIntegratedServicesNetwork(PISN)-CircuitModeBearerServices-Inter-exchangeSignallingProceduresandProtocol".[14]ECMA-225:"PrivateIntegratedServicesNetwork(PISN)-Inter-exchangeSignallingProtocolTransitCounterAdditionalNetworkFeature".3Definitions,symbolsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thetermsanddefinitionsgiveninITU-TRecommendationI.112[11]andthefollowingapply:AbstractTestSuite(ATS):seeISO/IEC9646-1[7].finaltestpurpose:testpurposewhichisintendedtobemappedtoasingletestcase(exceptifitisuntestable).NOTE:Inthepresentdocumentallfinaltestpurposesareindividualtestpurposesasthereisnocombinationoftestpurposes.ImplementationUnderTest(IUT):seeISO/IEC9646-1[7].incomingcall:seeEN300172[2].incominggatewayPINX:seeEN300172[2].Individualtestpurpose:testpurposefocusingonasingleconformancerequirement,producedbeforeanycombiningoftestpurposes.ThistermisnotdefinedinISO/IEC9646-1[7]butcorrespondstothe"individualtestpurpose"referredtoinISO/IEC9646-2[8]subclause10.3.3.informationelementswithinvalidcontents:seeEN300172[2].originatingPINX:seeEN300172[2].outgoingcall:seeEN300172[2].outgoinggatewayPINX:seeEN300172[2].precedingPINX:seeEN300172[2].PrivateIntegratedNetworkExchange(PINX):seeEN300172[2].PrivateIntegratedServicesNetwork(PISN):seeEN300172[2].ProtocolImplementationConformanceStatement(PICS):seeISO/IEC9646-1[7].SIST EN 300 805-1 V1.2.1:2005
ETSIEN300805-1V1.2.1(2000-05)ETSI8ProtocolImplementationExtraInformationForTesting(PIXIT):seeISO/IEC9646-1[7].reassembly:processwherebyanimplementationonreceiptofthepartsofasinglemessagewhichhasbeensegmentedfortransmission,reassemblesthesepartstomakeuptheoriginalmessage.segmentation:processbywhichamessageisdividedintopartswhenthemessagesizeexceedsthemaximumsizeoftheSCMinformationfield.SignallingCarriageMechanism(SCM):seeEN300172[2].subsequentPINX:seeEN300172[2].supertestpurpose:generaltestpurposefromwhichoneormoretestpurposesmaybederived.ThesederivedtestpurposesmaybemoredetailedthantheSuperTestPurpose.ThistermisnotdefinedinISO/IEC9646-1[7]butcorrespondstothe"morespecifictestobjectives"referredtoinISO/IEC9646-2[8]subclause10.3.1.terminatingPINX:seeEN300172[2].transitPINX:seeEN300172[2].unexpectedmessage:seeEN300172[2].unrecognizedinformationelement:seeEN300172[2].3.2SymbolsForthepurposesofthepresentdocument,thefollowingsymbolsapply:BOInopportuneBehaviour(TSSgroup)BVValidBehaviour(TSSgroup)CCCallClearing(TSSgroup)CECallEstablishing(TSSgroup)CRCallReference(value)IGIncomingGateway(TSSgroup)IVInValidbehaviourtests(TSSgroup)IOInOpportunebehaviourtest(TSSgroup)MSMessageSegmentation(TSSgroup)OGOutgoingGateway(TSSgroup)PCProtocolControl(TSSgroup)PVParameterVariations(TSSgroup)SEStateEventtransitions(TSSgroup)TRTRansit(TSSgroup)TETErminating(TSSgroup)3.3AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ATSAbstractTestSuiteIEInformationElementIUTImplementationUnderTestPICSProtocolImplementationConformanceStatementPINXPrivateIntegratedServicesNetworkeXchangePISNPrivateIntegratedServicesNetworkPIXITProtocolImplementationeXtraInformationforTestingPSS1PrivateIntegratedSignallingSystemNumber1SCMSignallingCarriageMechanismSTPSuperTestPurposeTPTestpurposeTSSTestSuiteStructureSIST EN 300 805-1 V1.2.1:2005
ETSIEN300805-1V1.2.1(2000-05)ETSI94TestSuiteStructure(TSS)Thetestsuiteisstructuredasatreewiththefollowinglevels:1stlevel:thenamerepresentingthebasespecification(EN300172[2]):-PSS1_BC.2ndlevel:CallControlforthemajorrolesofthebasespecification(Originating,Terminating,Transit,IncomingGateway,OutgoingGateway)andProtocolControlwhichiscommontoallthebehaviours:-ProtocolControl(PC);-callcontrolforOrIginating(OI);-callcontrolforTErminating(TE);-callcontrolforTRansit(TR);-callcontrolforIncomingGateway(IG);-callcontrolforOutgoingGateway(OG).3rdlevel:thephasesofthebasespecification:-CallEstablishing(CE);-CallClearing(CC);-MessageSegmentation(MS)(thisgroupisemptyforcallcontrolrequirements);-STATUSProcedures(ST)(thisgroupisemptyforcallcontrolrequirements);-LayerManagement(LM)(thisgroupisemptyforcallcontrolrequirements).4thlevel:thenatureofthetest:-Validbehaviourtests(BV);-InValidbehaviourtests(IV);-InOpportunebehaviourtests(IO).Figure1showsthePSS1Layer3TestSuiteStructureoverview.Notallthebrancheshavebeenexpandedtothefinaldetails.OnlygroupswhichareexpectedtocontainTPsareshown.SIST EN 300 805-1 V1.2.1:2005
ETSIEN300805-1V1.2.1(2000-05)ETSI10Inopportune(IO)Invalid(IV)Valid(BV)ProtocolControl(PC)CallEstablishing(CE)Inopportune(IO)Invalid(IV)Valid(BV)CallClearing(CC)Inopportune(IO)Invalid(IV)Valid(BV)MessageSegmentation(MS)Inopportune(IO)Valid(BV)StatusProcedures(ST)Inopportune(IO)Invalid(IV)Valid(BV)LayerManagement(LM)Valid(BV)Originating(OI)CallEstablishing(CE)Valid(BV)Terminating(TE)CallEstablishing(CE)CallClearing(CC)Valid(BV)Valid(BV)Transit(TR)CallEstablishing(CE)CallClearing(CC)Valid(BV)Valid(BV)IncomingGateway(IG)CallEstablishing(CE)Valid(BV)OutgoingGateway(OG)CallEstablishing(CE)QSIGBasicCall(PSS1_BC)Figure1:PSS1Layer3TestSuiteStructureoverview5TestPurposes(TP)5.1IntroductiontoTestPurposes5.1.1TestpurposesproductionmethodTheTPsproductionmethodconsistsofreviewingthestandardandspecifyingeverythingthatshouldbetested,i.e.allthecharacteristicsthatcouldbedeterminedfromthestandard,whichanimplementationisrequiredtoconformto.Thisfirstphaseledtotheproductionof"Super"TestPurposes(STPs),whicharegeneralTPs,reflectingmorethefunctionalaspectsandthestructureofthestandardratherthantheTSSitself(seeclause4).SIST EN 300 805-1 V1.2.1:2005
ETSIEN300805-1V1.2.1(2000-05)ETSI11ThesecondphaseconsistedofderivingfromeachSTPseveral"Final"TPs.These"Final"TPsaretheindividualTPsasidentifiedintheAbstractTestSuite(ATS)(eachofwhichwillgiverisetoaTestCase).Thecriteriaforderivingthese"Final"TPswastotakeintoaccounttheTSS,inordertoensuregoodcoveragefortesting.Theobjectivewastoderive"Final"TPsanddistributethemoverthecompleteTSS,takingintoaccountallthetestingaspects(validbehaviour,inopportunebehaviour,timer,parametervariations,stateeventtransition,etc.),whileretainingalltherequirementsofthestandard.Inthisway,oneormore"Final"TPsmaybederivedfromanSTP.AlthoughanSTPmaygenerateanumberof"final"TPs,notallofthemmayberetained,astheymaydealwitharequirementwhichhasalreadybeencoveredbyaprevious"final"TP.Thisensuresamoreefficienttestingwithgoodcoverage,avoidingrepeatedlytestingthesameaspectofthestandard,probablyleadingtothesameverdicteachtime.SomeSTPsarenotdecomposedinto"final"derivedTPsbecausetherequirementofthisSTPhasalreadybeencoveredbyanother"final"TP.5.1.2STPidentifierTheSTPidentifierisdescribedusinga5digitalphanumericcode,thiscodeisusedinthefollowingmanner:-characters5-4:"SP";-digit3-2-1:STPnumber;-PATTERN:SPwith=000->999.5.1.3"Final"derivedTPidentifierTheTPidentifierisdescribedusingan7digitalphanumericcode,thiscodeisusedinthefollowingmanner:-characters7-6:"TC";-digit5:2ndlevelofTSS;-digit4:3rdlevelofTSS;-digit3:4thlevelofTSS;-characters2-1:lettersidentifyingthefinalTP.PATTERN:TCwith:-=0:protocolcontrol;1:callcontroloriginating;2:callcontrolterminating;3:callcontroltransit;4:callcontroloutgoinggateway;5:callcontrolincominggateway.-=0:callestablishing;1:callclearing;2:messagesegmentation;3:statusprocedures;4:layermanagement.SIST EN 300 805-1 V1.2.1:2005
ETSIEN300805-1V1.2.1(2000-05)ETSI12-=2:validbehaviourtests;3:invalidbehaviourtest;4:inopportunebehaviourtests.-=AA->ZZEXAMPLE1:TC212KWisthenumberofthetestpurposeKW,foraterminatingPINX,totestthevalidbehaviouroftheIUTduringcallclearing.EXAMPLE2:TC212KUisthenumberofthetestpurposeKU,foraterminatingPINX,totestthevalidbehaviouroftheIUTduringcallclearing.5.1.4StandardoptionsInreviewingthestandardtoproduceTPs,twosituationshavebeenidentifiedregardingoptionalrequirements.ThefirstcaseiswhereeithertheImplementationUnderTest(IUT)performsanactionwhichcanbetested,ordoesnothingthatcanbetested.InthissituationthereisaTPforthecasewheretheIUTdoessomethingtestableandaProtocolImplementationeXtraInformationforTesting(PIXIT)questionshouldbeusedtoselecttheassociatedtestcase.ThesecondcaseiswheretheIUTalwaysperformsafirstactionwhichhastobetestedandoptionallyperformsasecondactionwhichhasalsotobetestedifitoccurs.InthissituationnoPIXITquestionisaskedforthisselection.5.1.5MessagesegmentationWhereaTPreferstoamessagesentbytheIUT,thismessagemaybesegmented(unlessotherwisestated)withoutaffectingtheTP.5.2TestpurposewritingrulesWritingruleshavebeendefinedinordertohaveconsistencybetweenalltheTPs.However,insomecases,itisnotpossibletousethemwithoutlosingtherealobjectiveofthetest.Consequently,asmallnumberofTPsmaydeviatefromtheserulesinaminorway.SIST EN 300 805-1 V1.2.1:2005
ETSIEN300805-1V1.2.1(2000-05)ETSI135.2.1Terminating,Originating,Incoming/OutgoingGatewayPINXTable1givesthetestpurposeswritingrulesfornon-transitPINXrequirements.Table1:TestPurposewritingrulesfornon-transitPINXrequirementsTPpartTextExampleHeadertabsee5.1.2and5.1.3(note2)tabsubclausex.x.xCRvalid,invalid,inopportuneetc.PreconditionEnsurethattheIUTin[call]state0,1,2,3,etc.[andin]Reassemblynullstate[seebelowformessagestructureifmessage]afterhavingsentaXXXmessage.StimulusseebelowformessagestructureonreceivingaXXXXmessageortorequesta.[]CRasaresultofcalleduseractionReactionsends,does,discards,etc.[]fortheoutgoingcalliftheactionissendingseebelowformessagestructure[and/or],etc.andenters[call]state0,1,2,3,etc.and/orentersReassemblynullstateand/orandremainsinthesame[call]state(s)MessagestructuremessagecontainingaSETUP,CONNECTetc.a)IEwithorcontainingb)aencodedasorincludingandbacktoaorb,Bearercapability,causeetc.Causevalueetc.NOTE1:TextinitalicsdoesnotappearinTPs,textbetween<>isfilledinforeachTPanddiffersfromoneTPtothenexttextbetween[]onlyappearincertainTPs.NOTE2:WherethetextofanSTPandaTPderivedfromitareidenticaltherearetwoheaders.SIST EN 300 805-1 V1.2.1:2005
ETSIEN300805-1V1.2.1(2000-05)ETSI145.2.2TransitPINXTable2givesthetestpurposeswritingrulesfortransitPINXrequirements.Table2:TestPurposewritingrulesfortransitPINXrequirementsTPpartTextExampleHeadertabsee5.1.2and5.1.3(note2)tabsubclausex.x.xCRvalid,invalid,inopportuneetc.PreconditionEnsurethattheIUTintransitstateTCC_AwaitDigitsinstateforthecalloninterfaceX7,8,9etc.andinstateforthecalloninterfaceY1,2,3,etc.[seebelowformessagestructureifmessage]afterhavingreceivedaXXXmessageoninterfaceX.StimulusseebelowformessagestructureonreceivingaXXXXmessageoninterfaceXorinordertoinitiatecallclearing[]CRwithsufficientaddressinformationtoroutethecallReactionsends,does,discards,etc.[]fortheoutgoingcall[on/forinterface]X,Yiftheactionissendingseebelowformessagestructure[and/or],etc.andentersstateforthecalloninterfaceX7,8,9etc.andentersstateforthecalloninterfaceY1,2,3etcand/orandremainsinthesame[call]state(s)MessagestructuremessagecontainingaSETUP,CONNECTetc.a)IEwithorcontainingb)aencodedasorincludingandbacktoaorb,Bearercapability,causeetc.Causevalueetc.NOTE1:TextinitalicsdoesnotappearinTPs,textbetween<>isfilledinforeachTPanddiffersfromoneTPtothenexttextbetween[]onlyappearincertainTPs.NOTE2:WherethetextofanSTPandaTPderivedfromitareidenticaltherearetwoheaders.5.3TestPurposesAllPICSitemsreferredtointhissubclauseareasspecifiedinEN300172[2]unlessindicatedotherwise.WherethereisareferencetotheANF-TCPICSthisreferstoEN301048[1].Unlessspecified:-themessagesindicatedarevalidandcontainatleastthemandatoryinformationelementsandpossiblyoptionalinformationelements;-theinformationelementsindicatedarevalidandcontainatleastthemandatoryparametersandpossiblyoptionalparameters.NOTE1:Onlythederived"Final"TPsareusedtoproducetestcases.NOTE2:WhereatestpurposespecifiesthattheIUTentersorremainsinaspecifiedProtocolControlorLayerManagementstate,thisisverifiedasspecifiedinsubclause5.3.13.NOTE3:WhereTPsarenotapplicabletoallimplementationsthisisindicatedbyaselectionstatement.WheresuchastatementappearsatthestartofasubclauseitappliestoallTPsinthatsubclause,whereitappearsafteraSTPitappliestothatSTPandallitsderivedTPs,whereitappearsafteraderivedTPitappliestothatTPonly.ATPisapplicableiftheselectionstatements(ifany)fortheTP,STPandsubclauseareallsatisfied.SIST EN 300 805-1 V1.2.1:2005
ETSIEN300805-1V1.2.1(2000-05)ETSI155.3.1ProtocolControlrequirementsforCallEstablishmentTheTPsinthissubclauserefertoEN300172[2],subclause10.1.5.3.1.1CallRequest5.3.1.1.1OutgoingsideTheTPsinthissubclauserefertoEN300172[2],subclause10.1.1.Selection:IUTsupportsproceduresforcallrequest.PICSB6.SP001subclauses10.1.1and14.5.5ValidTC002XDsubclauses10.1.1and14.5.5.ValidEnsurethattheIUTinstate0,inordertoinitiateacallsupporting64kbits/sUnrestricted,sendsaSETUPmessagecontainingaBearerCapabilityIEwithanInformationTransferCapabilityfieldencodedasUnrestricted.Selection:IUTsupports64kbit/sUnrestrictedbearer.PICS:Z1.SP002subclauses10.1.1and14.5.5ValidTC002XEsubclauses10.1.1and14.5.5ValidEnsurethattheIUTinstate0,inordertoinitiateacallsupporting64kbits/sSpeech,sendsaSETUPmessagecontainingaBearerCapabilityIEwithanInformationTransferCapabilityfieldencodedasSpeech.Selection:IUTsupports64kbit/sSpeechbearer.PICS:Z2.SP003subclauses10.1.1and14.5.5ValidTC002XFsubclauses10.1.1and14.5.5ValidEnsurethattheIUTinstate0,inordertoinitiateacallsupporting64kbits/s3,1kHzAudio,sendsaSETUPmessagecontainingaBearerCapabilityIEwithanInformationTransferCapabilityfieldencodedas3,1kHzAudio.Selection:IUTsupports64kbit/s3,1kHzAudiobearer.PICS:Z3.SP310subclauses10.1.1and14.5.5ValidTC002YJsubclauses10.1.1and14.5.5ValidEnsurethattheIUTinstate0,inordertoinitiateacallsupportingamultiratebearer,sendsaSETUPmessagecontainingaBearerCapabilityIEwithanInformationTransferRatefieldencodedasMultirate,384kbit/s,1536kbit/sor1920kbit/s.Selection:IUTsupportsmultiratebearer.PICS:Z4.SP311subclauses10.1.1and14.5.5ValidTC002YKsubclauses10.1.1and14.5.5ValidEnsurethattheIUTinstate0,inordertoinitiateacallsupportingA-lawuserinformationlayer1protocol,sendsaSETUPmessagecontainingaBearerCapabilityIEwiththeUserInformationLayer1ProtocolfieldencodedasA-law.Selection:IUTsupportsA-law.PICS:Z5.SIST EN 300 805-1 V1.2.1:2005
ETSIEN300805-1V1.2.1(2000-05)ETSI16SP312subclauses10.1.1and14.5.5ValidTC002YLsubclauses10.1.1and14.5.5ValidEnsurethattheIUTinstate0,inordertoinitiateacallsupportingµ-lawuserinformationlayer1protocol,sendsaSETUPmessagecontainingaBearerCapabilityIEwiththeUserInformationLayer1Protocolfieldencodedasµ-law.Selection:IUTsupportsµ-law.PICS:Z6.SP306subclauses10.1.1and14.5.5ValidTC002YGsubclauses10.1.1and14.5.5ValidEnsurethattheIUTinstate0,inordertoinitiateacallsupporting64kbits/sunrestricteddigitalinformationwithtonesandannouncements,sendsaSETUPmessagecontainingaBearerCapabilityIEwithanInformationTransferCapabilityfieldencodedasunrestricteddigitalinformationwithtonesandannouncements.Selection:IUTsupports64kbit/sunrestricteddigitalinformationwithtonesandannouncementsbearer.PICS:Z7.NOTE:ThePICSreferenceZ7istakenfromECMA-143.TheidentifierinEN300172[2](inthedelta)isZ5whichconflictswithaniteminISO/IEC11572[9].SP007subclauses10.1.1and13.2.10ValidTC002AAsubclause10.1.1ValidEnsurethattheIUTinstate0,inordertoinitiateacall,sendsaSETUPmessagewithallthemandatoryIE,andentersstate1.SP008subclause10.1.1ValidTC002AEsubclause10.1.1ValidEnsurethattheIUTinstate1,atfirstexpiryoftimerT303,sendsthesameSETUPmessageastheonesentpreviously,andremainsinthesamestate.Selection:IUTsupportsre-transmissionofSETUP.SP009subclause10.1.1ValidTC002AGsubclause10.1.1ValidEnsurethattheIUTinstate1,atthesecondexpiryoftimerT303,sendsaRELEASECOMPLETEmessagecontainingaCauseIEwithaCauseValueencodedas102,andentersstate0(referenceEN300172[2],subclause10.1.1).Selection:IUTsupportsre-transmissionofSETUP.SP010subclause10.1.1ValidTC002AIsubclause10.1.1ValidEnsurethattheIUTinstate0,inordertoinitiateacall,sendsaSETUPmessagecontainingaChannelIdentificationIEwithaChannelNumberindicatingafreechannel,andentersstate1.SP011subclauses10.1.1and14.3ValidTC002AJsubclauses10.1.1and14.3ValidEnsurethattheIUTinstate0,inordertoinitiateacall,sendsaSETUPmessagecontainingaCallReferenceIEwithaCallReferenceFlagencodedas0andaCallReferenceValuecodedin2octets,andentersstate1.SIST EN 300 805-1 V1.2.1:2005
ETSIEN300805-1V1.2.1(2000-05)ETSI17SP012subclause10.1.1ValidTC002ALsubclause10.1.1ValidEnsurethattheIUTinstate0,inordertoinitiateacall,usingen-blocsending,sendsaSETUPmessagecontainingaCalledPartyNumberIEencodedasacompleteNumberasstatedinthePIXIT.SP013subclause10.1.1ValidTC002AMsubclause10.1.1ValidEnsurethattheIUTinstate0,inordertoinitiateacall,usingen-blocsending,sendsaSETUPmessagecontainingaSendingCompleteIE,andentersstate1.Selection:IUTsupportsinclusionofSendingCompleteintheSETUPmessage.PICS:B7ORJ12.5.3.1.1.2IncomingsideTheTPsinthissubclauserefertoEN300172[2],subclause10.1.1.Selection:IUTsupportsproceduresforincomingcalls:PICSB3ORB4ORB5.SP014subclause10.1.1ValidTC002UZsubclause10.1.1ValidEnsurethattheIUTinstate0,onreceivingaSETUPmessage,entersstate6(referenceEN300172[2],subclause10.1.1).NOTE:ThisSTPisreferencedin'UntestableTPs'sectionintheassociatedATSspecificationdocument.5.3.1.2InformationchannelselectionTheTPsinthissubclauserefertoEN300172[2],subclause10.1.2.5.3.1.2.1OutgoingsideSelection:IUTsupportsproceduresforcallrequest.PICSB6.SP016subclause10.1.2ValidEnsurethattheIUTinstate1,onreceivinganALERTINGorCONNECTmessageasthefirstresponsetotheSETUPmessage,doesnotindicateaprotocolerror.TC002AZsubclause10.1.2ValidEnsurethattheIUTinstate1,onreceivinganALERTINGmessageasthefirstresponsetotheSETUPmessage,doesnotindicateaprotocolerror.TC002BAsubclause10.1.2ValidEnsurethattheIUTinstate1,onreceivingaCONNECTmessageasthefirstresponsetotheSETUPmessage,sendsaCONNECTACKmessage.Selection:IUTsupportssendingofCONNECTACKNOWLEDGE.SP017subclauses10.1.2and10.2.2ValidTC002BBsubclauses10.1.2and10.2.2ValidEnsurethattheIUTinstate1,onreceivingaRELEASECOMPLETEmessagecontainingaCauseIEwithaCauseValueencodedas44,asthefirstresponsetotheSETUPmessagecontainingaChannelIdentificationIEwiththepreferred/exclusivefieldencodedasexclusive,entersstate0.Selection:IUTsupportssendingSETUPincludingexclusiveChannelID.SIST EN 300 805-1 V1.2.1:2005
ETSIEN300805-1V1.2.1(2000-05)ETSI18SP018subclauses10.1.2and10.2.2ValidTC002BCsubclauses10.1.2and10.2.2ValidEnsurethattheIUTinstate1,onreceivingaRELEASECOMPLETEmessagecontainingaCauseIEwithaCauseValueencodedas34,asthefirstresponsetotheSETUPmessagecontainingaChannelIdentificationIEwiththepreferred/exclusivefieldencodedaspreferred,entersstate0.Selection:IUTsupportssendingSETUPincludingpreferredChannelID.SP019subclauses10.1.2and10.2.2ValidEnsurethattheIUTinstate1,onreceivingaCALLPROCEEDINGorSETUPACKNOWLEDGEmessagecontainingaChannelIdentificationIEwithaChannelNumberencodedwithanunacceptablechannelnumber,asthefirstresponsetotheSETUPmessage,sendsaRELEASEmessagecontainingaCauseIEwithaCauseValueencodedas6,andentersstate19.TC002BDsubclauses10.1.2and10.2.2ValidEnsurethattheIUTinstate1,onreceivingaCALLPROCEEDINGmessagecontainingaChannelIdentificationIEwithaChannelNumberencodedwithanon-existentchannelnumber,asthefirstresponsetotheSETUPmessage,sendsaRELEASEmessagecontainingaCauseIEwithaCauseValueencodedas6,andentersstate19.TC002BEsubclauses10.1.2and10.2.2ValidEnsurethattheIUTinstate1,onreceivingaSETUPACKNOWLEDGEmessagecontainingaChannelIdentificationIEwithaChannelNumberencodedwithachannelnumberknowntobebusy,asthefirstresponsetotheSETUPmessage,sendsaRELEASEmessagecontainingaCauseIEwithaCauseValueencodedas6.5.3.1.2.2Incomingside-singleinformationchannelSelection:IUTsupportsproceduresforincomingcalls:PICSB3ORB4ORB5.SP020subclause10.1.2ValidEnsurethattheIUTinstate0,onreceivingaSETUPmessage,containingaChannelIdentificationIEwithaChannelNumberencodedasn,knowntobeavailable,sendsaCALLPROCEEDINGorSETUPACKmessagecontainingaChannelIdentificationIEwithaChannelNumberencodedasnandentersstate9or25.TC002JDsubclause10.1.2ValidEnsurethattheIUTinstate0,onreceivingaSETUPmessage,containingaChannelIdentificationIEwithaChannelNumberencodedasn,knowntobeavailable,andaSendingCompleteIE,sendsaCALLPROCEEDINGmessagecontainingaChannelIdentificationIEwithaChannelNumberencodedasn.SP021subclause10.1.2ValidEnsurethattheIUTinstate0,onreceivingaSETUPmessagecontainingaChannelIdentificationIEwithaChannelNumberencodedasn,knowntobebusy,andapreferred/exclusivefieldencodedaspreferred,havinganalternativeavailableInformationchannelwhosenumberism,sendsaCALLPROCEEDINGorSETUPACKmessagecontainingaChannelIdentificationIEwithaChannelNumberencodedasm,andentersstate9or25respectively.TC002JEsubclause10.1.2ValidEnsurethattheIUTinstate0,onreceivingaSETUPmessagecontainingaChannelIdentificationIEwithaChannelNumberencodedasn,knowntobebusy,andapreferred/exclusivefieldencodedaspreferred,andaSendingCompleteIE,havinganalternativeavailableInformationchannelwhosenumberism,sendsaCALLPROCEEDINGmessagecontainingaChannelIdentificationIEwithaChannelNumberencodedasm.SIST EN 300 805-1 V1.2.1:2005
ETSIEN300805-1V1.2.1(2000-05)ETSI19SP022subclause10.1.2ValidTC002JFsubclause10.1.2ValidEnsurethattheIUTinstate0,onreceivingaSETUPmessagecontainingaChannelIdentificationIEwithaChannelNumberknowntobebusyandapreferred/exclusivefieldencodedasexclusive,sendsaRELEASECOMPLETEmessagecontainingaCauseIEwithaCauseValueencodedas44,andentersstate0.SP023subclause10.1.2ValidTC002JGsubclause10.1.2ValidEnsurethattheIUTinstate0,onreceivingaSETUPmessagecontainingaChannelIdentificationIEwithaChannelNumberknowntobebusyandapreferred/exclusivefieldencodedaspreferred,andhavingnoalternativeInformationchannelavailable,sendsaRELEASECOMPLETEmessagecontainingaCauseIEwithaCauseValueencodedas34,andentersstate0.5.3.1.2.3Incomingside-multirateSelection:IUTsupportsproceduresforincomingcalls:PICSB3ORB4ORB5.Selection:IUTsupportsmultiratebearers:PICSZ4.SP31
...