ETSI ETS 300 374-3 ed.1 (1996-02)
Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for Service Switching Function (SSF) and Specialized Resource Function (SRF)
Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for Service Switching Function (SSF) and Specialized Resource Function (SRF)
DE/SPS-03016-1
Inteligentno omrežje (IN) - Prvi nabor zmožnosti (CS1) inteligentnega omrežja - Jedrni uporabovni (aplikacijski) del inteligentnega omrežja (INAP) - 3. del: Specifikacija zgradbe preskušalnega niza in namena preskušanja (TSS&TP) za funkcijo komutacije storitev (SSF) in funkcijo posebnih virov (SRF)
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Inteligentno omrežje (IN) - Prvi nabor zmožnosti (CS1) inteligentnega omrežja - Jedrni uporabovni (aplikacijski) del inteligentnega omrežja (INAP) - 3. del: Specifikacija zgradbe preskušalnega niza in namena preskušanja (TSS&TP) za funkcijo komutacije storitev (SSF) in funkcijo posebnih virov (SRF)Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for Service Switching Function (SSF) and Specialized Resource Function (SRF)33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:ETS 300 374-3 Edition 1SIST ETS 300 374-3:1997en01-november-1997SIST ETS 300 374-3:1997SLOVENSKI
STANDARD
SIST ETS 300 374-3:1997
EUROPEANETS 300 374-3TELECOMMUNICATIONFebruary 1996STANDARDSource: ETSI TC-SPSReference: DE/SPS-03016-1ICS:33.020, 33.080Key words:IN, CS1, INAP, TSS&TP, testingIntelligent Network (IN);Intelligent Network Capability Set 1 (CS1);Core Intelligent Network Application Protocol (INAP);Part 3: Test Suite Structure and Test Purposes (TSS&TP)specification for Service Switching Function (SSF) andSpecialized Resource Function (SRF)ETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1996. All rights reserved.SIST ETS 300 374-3:1997
Page 2ETS 300 374-3: February 1996Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.SIST ETS 300 374-3:1997
Page 3ETS 300 374-3: February 1996ContentsForeword.71Scope.92Normative references.93Definitions and abbreviations.93.1Definitions.93.2Abbreviations.104Test Suite Structure (TSS).114.1Overview.114.2Physical scenarios.134.3Test groups.164.3.1Interface groups.164.3.1.1Basic SSF - bS.164.3.1.2SSF relay - rS.164.3.1.3Initiating SSF - iS.164.3.1.4Assisting SSF - aS.174.3.1.5IP with direct path to SCP - cI.174.3.2Main test groups.174.3.2.1Capability tests (CA).174.3.2.2Valid Behaviour tests (BV).174.3.2.3Invalid Behaviour tests (BI).174.3.2.4Inopportune Behaviour tests (BO).174.4Test step structure.174.4.1Preambles.174.4.2Postambles.174.5Timers of the Abstract Test Suite (ATS).185Test Purposes (TP).205.1Introduction.205.1.1Test purpose naming convention.205.1.2Source of test purpose definition.215.1.3Initial state.215.1.4Untested procedures.215.2Service Switching Point (SSP).215.2.1Basic SSF - bS.215.2.1.1Capability tests (CA).215.2.1.1.1SSF-FSM state "Idle".215.2.1.1.2SSF-FSM state "Waiting ForInstructions".225.2.1.1.3SSF-FSM state "Monitoring".225.2.1.1.4SSME-FSM state "Idle".225.2.1.2Valid Behaviour tests (BV).235.2.1.2.1SSF-FSM state "Idle".235.2.1.2.2SSF-FSM state "Waiting ForInstructions".275.2.1.2.3SSF-FSM state "Monitoring".375.2.1.2.4SSME-FSM state "Idle".485.2.1.2.5SSME-FSM state "Non CallAssociated Treatment".495.2.1.3Invalid Behaviour tests (BI).505.2.1.3.1SSF-FSM state "Idle".505.2.1.3.2SSF-FSM state "Waiting ForInstructions".515.2.1.3.3SSF-FSM state "Monitoring".52SIST ETS 300 374-3:1997
Page 4ETS 300 374-3: February 19965.2.1.3.4SSME-FSM state "Idle".535.2.1.4Inopportune Behaviour tests (BO).535.2.1.4.1SSF-FSM state "Idle".535.2.1.4.2SSF-FSM state "Waiting ForInstructions".545.2.1.4.3SSF-FSM state "Monitoring".545.2.2SSF relay - rS.555.2.2.1Valid Behaviour tests (BV).555.2.2.1.1SSF-FSM state "Waiting ForInstructions".555.2.2.1.2SSF-FSM state "Waiting For End OfUser Interaction".565.2.2.2Invalid Behaviour tests (BI).625.2.2.2.1SSF-FSM state "Waiting ForInstructions".625.2.2.2.2SSF-FSM state "Waiting For End OfUser Interaction".625.2.2.3Inopportune Behaviour tests (BO).635.2.2.3.1SSF-FSM state "Idle".635.2.2.3.2SSF-FSM state "Waiting ForInstructions".635.2.2.3.3SSF-FSM state "Waiting for End ofUser Interaction".645.2.2.3.4SSF-FSM state "Monitoring".645.2.3Initiating SSF - iS.655.2.3.1Valid Behaviour tests (BV).655.2.3.1.1SSF-FSM state "Waiting ForInstructions".655.2.3.1.2SSF-FSM state "Waiting For End OfTemporary Connection".665.2.3.2Invalid Behaviour tests (BI).675.2.3.2.1SSF-FSM state "Waiting ForInstructions".675.2.3.2.2SSF-FSM state "Waiting For End OfTemporary Connection".685.2.3.3Inopportune Behaviour tests (BO).685.2.3.3.1SSF-FSM state "Idle".685.2.3.3.2SSF-FSM state "Waiting ForInstructions".695.2.3.3.3SSF-FSM state "Waiting for End ofTemporary Connection".695.2.3.3.4SSF-FSM state "Monitoring".705.2.4Assisting SSF - aS.705.2.4.1Valid Behaviour tests (BV).705.2.4.1.1SSF-FSM state "Idle".705.2.4.1.2SSF-FSM state "Waiting ForInstructions".715.2.4.1.3SSF-FSM state "Waiting For End OfUser Interaction".735.2.4.2Invalid Behaviour tests (BI).755.2.4.2.1SSF-FSM state "Waiting ForInstructions".755.2.4.2.2SSF-FSM state "Waiting for End ofUser Interaction".755.2.4.3Inopportune Behaviour tests (BO).765.2.4.3.1SSF-FSM state "Waiting ForInstructions".765.3Intelligent Peripheral (IP).775.3.1Valid Behaviour tests (BV).775.3.1.1SRSM-FSM state "Idle".775.3.1.2SRSM-FSM state "Connected".775.3.1.2.1Network events.775.3.1.2.2Operations.78SIST ETS 300 374-3:1997
Page 5ETS 300 374-3: February 19965.3.1.2.3Operation errors.825.3.1.3SRSM-FSM state "User Interaction".835.3.1.3.1Network events.835.3.1.3.2Operations.835.3.2Invalid Behaviour tests (BI).845.3.2.1SRSM-FSM state "Connected".845.3.2.2SRSM-FSM state "User Interaction".845.3.3Inopportune Behaviour tests (BO).855.3.3.1SRSM-FSM state "Idle".855.3.3.2SRSM-FSM state "Connected".856Compliance.85Annex A (informative):TP coverage.86History.87SIST ETS 300 374-3:1997
Page 6ETS 300 374-3: February 1996Blank pageSIST ETS 300 374-3:1997
Page 7ETS 300 374-3: February 1996ForewordThis European Telecommunication Standard (ETS) has been produced by the Signalling Protocols andSwitching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).This ETS is part 3 of a multi-part standard covering the Capability Set 1 (CS1) core Intelligent NetworkProtocol (INAP) as described below:Part 1:"Protocol specification";Part 2:"Protocol Implementation Conformance Statement (PICS) proforma specification";Part 3:"Test Suite Structure and Test Purposes (TSS&TP) specification for Service SwitchingFunction (SSF) and Specialized Resource Function (SRF)";Part 4:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing(PIXIT) proforma specification for SSF and SRF";Part 5:"Protocol specification for the Service Control Function (SCF) - Service Data Function (SDF)interface";Part 6:"PICS proforma specification for the SCF-SDF interface".NOTE:Further parts of this standard may be identified later.Transposition datesDate of adoption of this ETS:1 March 1996Date of latest announcement of this ETS (doa):31 May 1996Date of latest publication of new National Standardor endorsement of this ETS (dop/e):30 November 1996Date of withdrawal of any conflicting National Standard (dow):30 November 1996SIST ETS 300 374-3:1997
Page 8ETS 300 374-3: February 1996Blank pageSIST ETS 300 374-3:1997
Page 9ETS 300 374-3: February 19961ScopeThis third part of ETS 300 374 provides the Test Suite Structure and Test Purposes (TSS&TP) forconformance testing of the Service Switching Function (SSF) and the Specialized Resource Function(SRF) of the core Intelligent Network Application Protocol (INAP) of Intelligent Network (IN) CapabilitySet 1 (CS1) according to ETS 300 374-1 [1].ISO/IEC 9646-1 [3] and ISO/IEC 9646-2 [4] are used as the basis for the test methodology.2Normative referencesThis ETS incorporates by dated and undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this ETS only when incorporated in it by amendment or revision. For undated references the latestedition of the publication referred to applies.[1]ETS 300 374-1 (1994): "Intelligent Network (IN); Intelligent Network CapabilitySet 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 1:Protocol specification".[2]ETS 300 374-2: "Intelligent Network (IN); Intelligent Network Capability Set 1(CS1); Core Intelligent Network Application Protocol (INAP); Part 2: ProtocolImplementation Conformance Statement (PICS) proforma specification forService Switching Function (SSF), Specialized Resource Function (SRF) andService Control Function (SCF)".[3]ISO/IEC 9646-1: "Information technology - Open systems interconnection -Conformance testing methodology and framework - Part 1: General concepts".[4]ISO/IEC 9646-2: "Information technology - Open systems interconnection -Conformance testing methodology and framework - Part 2: Abstract test suitespecification".3Definitions and abbreviations3.1DefinitionsFor the purposes of this ETS, the following definitions apply:-terms defined in ETS 300 374-1 [1];-terms defined in ISO/IEC 9646-1 [3] and in ISO/IEC 9646-2 [4].In particular, the following terms defined in ISO/IEC 9646-1 [3] apply:-Abstract Test Suite (ATS);-Implementation Under Test (IUT);-System Under Test (SUT);-Protocol Implementation Conformance Statement (PICS).SIST ETS 300 374-3:1997
Page 10ETS 300 374-3: February 19963.2AbbreviationsFor the purposes of this ETS, the following abbreviations apply:aSassisting SSFaSSPassisting SSPATSAbstract Test SuiteBIInvalid Behaviour testsBOInopportune Behaviour testsbStests for SSP basic functionsBVValid Behaviour testsCACapability testscIIP with direct path to SCPEDP-NEvent Detection Point - NotificationEDP-REvent Detection Point - RequestFEFunctional EntityFSMFinite State MachineINIntelligent NetworkINAPIntelligent Network Application ProtocolIPIntelligent PeripheraliSinitiating SSFiSSPinitiating SSPIUTImplementation Under TestPICSProtocol Implementation Conformance StatementPDUProtocol Data UnitrSSSF relaySCFService Control FunctionSCPService Control PointSDFService Data FunctionSDPService Data PointSRFSpecialized Resource FunctionSRSMSRF call State ModelSSFService Switching FunctionSSMESSF Management EntitySSPService Switching PointSUTSystem Under TestTCAPTransaction Capabilities Application PartTDPTrigger Detection PointTPTest PurposeTSSTest Suite StructureSIST ETS 300 374-3:1997
Page 11ETS 300 374-3: February 19964Test Suite Structure (TSS)4.1OverviewTables 1 and 2 show the structure of the test suites for SSF and SRF.Table 1: Test suite structure of the SSF testsSUTInterfaceCategoryStateGroupSSPSCF-SSFCAState 1Network eventbS: SSP basic functionsOperationState 3OperationState 6Network eventState 7OperationBVState 1Network eventOperationState 3Network eventOperationOperation errorState 6Network eventOperationOperation errorState 7OperationState 8Network eventBIState 1OperationState 3OperationOperation errorState 6OperationState 7OperationBOState 1OperationState 3OperationState 6OperationSCF-SSF-SRFBVState 3OperationrS: add. for SSP withState 4Network eventrelay functionsOperationOperation errorBIState 3OperationState 4OperationBOState 1OperationState 3OperationState 4OperationState 6Operation (continued)SIST ETS 300 374-3:1997
Page 12ETS 300 374-3: February 1996Table 1 (concluded): Test suite structure of the SSF testsSUTInterfaceCategoryStateGroupSSPSCF-SSFBVState 3OperationiS: add. for SSP actingState 5Network eventas initiating SSPOperationOperation errorBIState 3OperationState 5OperationBOState 1OperationState 3OperationState 5OperationState 6OperationSCF-SSFBVState 1Network eventaS: add. for SSP actingState 3Network eventas assisting SSPOperationOperation errorState 4Network eventOperationOperation errorBIState 3OperationState 4OperationBOState 3OperationState 4OperationTable 2: Test suite structure of the SRF testsSUTInterfaceCategoryStateGroupIPSCF-SRFBVState 1Network eventcI (IP direct path to SCP)State 2Network eventOperationOperation errorState 3Network eventOperationBIState 2OperationState 3OperationBOState 1OperationState 2OperationSIST ETS 300 374-3:1997
Page 13ETS 300 374-3: February 19964.2Physical scenariosThe test suites given in subclause 4.1 are based on the mapping of Functional Entities (FE) to PhysicalEntities (PE) as shown in table 3.Table 3: Mapping of functional entities to physical entitiesFEPESRFSSFSCFSDFSSPomn/an/aSCPn/an/amoSDPn/an/an/amIPmn/an/an/aThe application of the test suites according to subclause 4.1 is given in figures 1 to 5 for a number ofdifferent example physical scenarios.The following figures illustrate mainly the SRF configurations. The SDP is included for betterunderstanding of the whole IN configuration. Nevertheless, it possible to support an SCP with anintegrated SDF.SCPSSPIPNon-integrated SRFIntegrated SRFSCFSSFCCFSRFSDFapplied test suite groups for SSP testing:bS + rSFigure 1: Example for SCP with single SSP Non-integrated or Integrated SRFSIST ETS 300 374-3:1997
Page 14ETS 300 374-3: February 1996SCPSSPIPSCFSSFCCFSRFSDFapplied test suite groups for iSSP testing:bS + iSapplied test suite groups for IP testing:cIFigure 2: Example for direct path SCP - IPSCPinitiating SSPIPNon-integrated SRFIntegrated SRFSCFSSFCCFSRFSSFCCFassisting SSPSDFapplied test suite groups for iSSP testing:bS + iSapplied test suite groups for aSSP testing:aS + rSFigure 3: Example for SSP Assist/Hand-off (assisting SSP with relay)SIST ETS 300 374-3:1997
Page 15ETS 300 374-3: February 1996SCPIPSCFSSFCCFSRFSDFSRFNon-integrated SRFIntegrated SRFinitiating SSPIPapplied test suite groups for iSSP testing:bS + iS + rSapplied test suite groups for IP testing:cIFigure 4: Example for SSP Assist/Hand-off (initiating SSP with relay)SCPIPNon-integrated SRFIntegrated SRFSCFSSFCCFSRFSSFCCFassisting SSPSDFSRFNon-integrated SRFIntegrated SRFIPinitiating SSPapplied test suite groups for iSSP testing:bS + iS + rSapplied test suite groups for aSSP testing:aS + rSFigure 5: Example for SSP Assist/Hand-off (initiating and assisting SSP with relay)SIST ETS 300 374-3:1997
Page 16ETS 300 374-3: February 19964.3Test groups4.3.1Interface groups4.3.1.1Basic SSF - bSThe defined test purposes cover the INAP procedures at the SSP for the basic functions as described inETS 300 374-1 [1], clauses 7 to 10. The basic functions are the INAP procedures at the SSP for thefollowing operations:ActivateServiceFilteringActivityTestApplyChargingApplyChargingReportCallInformationRequestCallInformationReportCancel (CCF events)CollectInformationConnectContinueEventNotificationChargingEventReportBCSMFurnishChargingInformationInitialDPInitiateCallAttemptReleaseCallRequestNotificationChargingEventRequestReportBCSMEventResetTimerSendChargingInformationServiceFilteringResponse4.3.1.2SSF relay - rSThe defined test purposes cover the INAP procedures at the SSP needed in addition to the basicfunctions for the user interaction with relay as described in ETS 300 374-1 [1], clauses 7 to 10. These arethe procedures for the following operations:Cancel (PA, PC)ConnectToResourceDisconnectForwardConnectionPlayAnnouncementPromptAndCollectUserInformationSpecializedResourceReport4.3.1.3Initiating SSF - iSThe defined test purposes cover the INAP procedures at the initiating SSP needed in addition to the basicfunctions as described in ETS 300 374-1 [1], clauses 7 to 10. These are the procedures for the followingoperations:Connect (hand-off)DisconnectForwardConnectionEstablishTemporaryConnectionSIST ETS 300 374-3:1997
Page 17ETS 300 374-3: February 19964.3.1.4Assisting SSF - aSThe defined test purposes cover the INAP procedures at the assisting SSP needed in addition to the basicand relay functions as described in ETS 300 374-1 [1], clauses 7 to 10. These are the procedures for thefollowing operations:AssistRequestInstructions4.3.1.5IP with direct path to SCP - cIThe defined test purposes cover the INAP procedures at the IP related to the SRF-SCF interface in caseof a direct path between SCP and IP as described in ETS 300 374-1 [1], clauses 7 to 10. These are theprocedures for the following operations:AssistRequestInstructionsCancelPlayAnnouncementPromptAndCollectUserInformationSpecializedResourceReport4.3.2Main test groups4.3.2.1Capability tests (CA)Capability testing provides a limited testing to ascertain the capabilities stated in the PICS can beobserved.4.3.2.2Valid Behaviour tests (BV)Predefined state transitions are considered as valid. The test purposes in the valid behaviour test subgroup cover as far as reasonable the verification of the normal and exceptional procedures of the variousFinite State Machines (FSMs), i.e. a valid behaviour test is a test where the message sequence and themessage contents is considered as valid.4.3.2.3Invalid Behaviour tests (BI)This test sub group is intended to verify that the IUT is able to react properly having received an invalidProtocol Data Unit (PDU). An invalid PDU is defined as a syntactically incorrect message.4.3.2.4Inopportune Behaviour tests (BO)This test group is intended to verify that the IUT is able to react properly in the case an inopportuneprotocol event occurring. Such an event is syntactically correct but occurs when it is not expected, e.g. acorrectly coded operation is received in a wrong state (the IUT may respond by sending errorUnexpectedComponentSequence).4.4Test step structure4.4.1PreamblesThe preamble test group contains the preamble test steps needed for initialisation of the IUT beforetesting the particular test purpose. Each preamble shall start from the IUT initial state as defined insubclause 5.1.4.4.4.2PostamblesAfter each test case the IUT shall be brought back to the initial state as defined in subclause 5.1.4.SIST ETS 300 374-3:1997
Page 18ETS 300 374-3: February 19964.5Timers of the Abstract Test Suite (ATS)This subclause describes the timers and counters used in the ATS. The "min" and "max" indicationsdefine if the timer value represents the minimum or maximum limit of a timer. The timer values containsome additional tolerances for delays caused by test simulators. Therefore, a bigger timer tolerance isgiven than defined in ETS 300 374-1 [1]:Minimum value of ATS timer = minimum ETS timer;Maximum value of ATS timer = maximum ETS timer ´ 1,2.Table 4 shows the identified timers used in the ATS and the references to ETS 300 374-1 [1].Table 4: ATS timer valuesATS timer nameATS timer value[s]ETS timer nameReference toETS 300 374-1 [1]TSSFmin(note)TSSFnot definedTSSFmax(note)TSRFmin(note)TSRFnot definedTSRFmax(note)TSCF-SSFmin(note)TSCF-SSFnot definedTSCF-SSFmax(note)TActTestmin(note)TActTestnot definedTActTestmax(note)TASSIST/HAND-OFFmin(note)TASSIST/HAND-OFFnot definedTASSIST/HAND-OFFmax(note)Tasfmin1Tasf6.1Tasfmax12Tatmin1Tat6.1Tatmax12Tacmin1Tac6.1Tacmax12Tacrmin1Tacr6.1Tacrmax12Tarimin1Tari6.1Tarimax12Tcgmin1Tcg6.1Tcgmax12Tcirpmin1Tcirp6.1Tcirpmax12Tcirqmin1Tcirq6.1Tcirqmax12Tcanmin1Tcan6.1Tcanmax12Tcimin1Tci6.1Tcimax72(continued)SIST ETS 300 374-3:1997
Page 19ETS 300 374-3: February 1996Table 4 (concluded): ATS timer valuesATS timer nameATS timer value[s]ETS timer nameReference toETS 300 374-1 [1]Tconmin1Tcon6.1Tconmax12Tctrmin1Tctr6.1Tctrmax12Tcuemin1Tcue6.1Tcuemax12Tdfcmin1Tdfc6.1Tdfcmax12Tetcmin1Tetc6.1Tetcmax72Tencmin1Tenc6.1Tencmax12Terbmin1Terb6.1Terbmax12Tfcimin1Tfci6.1Tfcimax12Tidpmin1Tidp6.1Tidpmax12Ticamin1Tica6.1Ticamax12Trcmin1Trc6.1Trcmax12Trncmin1Trnc6.1Trncmax12Trrbmin1Trrb6.1Trrbmax12Trtmin1Trt6.1Trtmax12Tscimin1Tsci6.1Tscimax12Tsfrmin1Tsfr6.1Tsfrmax12Tpamin1Tpa6.1Tpamax1 800Tpcmin1Tpc6.1Tpcmax1 800Tsrrmin1Tsrr6.1Tsrrmax12NOTE:The value of this timer is given in ETS 300 374-2 [2].SIST ETS 300 374-3:1997
Page 20ETS 300 374-3: February 19965Test Purposes (TP)5.1IntroductionFor each test requirement a TP is defined.At the start of each test sub group the preambles and the postambles are listed.5.1.1Test purpose naming conventionThe identifier of the TP is built according to the scheme in table 5.Table 5: TP identifier naming convention schemeIdentifier:IN=interface:(1)SCP: Basic SCF (bC)(not used)(2)SCP: SCF-SSF relay handling (rC)(not used)(3)SCP: SCF Assist with relay handling (aC)(not used)(4)SCP: SCF direct path IP handling (pC)(not used)(5)SCP: SCF-SDF handling (dC)(not used)6SSP: Basic SSF (bS)7SSP: SSF relay (rS)8SSP: Initiating SSF (iS)9SSP: Assisting SSF (aS)AIP: SCF-SRF direct path to SCP (cI)(B)SDP: SCF-SDF direct path to SCP (cD)(not used)=category:1BIT, Basic Interconnection tests(not used)2CA, Capability tests3BV, Valid Behaviour tests4BI, Invalid Behaviour tests5BO, Inopportune Behaviour tests=state:0not relevant1State 1 / State a in case of SSF2State 2 / State b in case of SSF3State 3 / State c in case of SSF4State 4 / State d in case of SSF5State 5 / State e in case of SSF6State 6 / State f in case of SSF7State 7 / State ma in case of SSF8State 8 / State mb in case of SSF=group:0Network event1Operation2Return result3Operation error=sequential number:(01-99)SIST ETS 300 374-3:1997
Page 21ETS 300 374-3: February 19965.1.2Source of test purpose definitionThe test purposes are based on ETS 300 374-1 [1]. In each test purpose, a reference to the relevantsubclauses of ETS 300 374-1 [1] is made below the test purpose name.5.1.3Initial stateThe initial state for all SUTs (SSP, IP) shall be "Idle" for all test purposes.5.1.4Untested proceduresApplication Context Name negotiation is not tested. Tests on Application Context Name negotiation shallbe part of test purposes and associated ATS for Transaction Capabilities Application Part (TCAP) testing.5.2Service Switching Point (SSP)5.2.1Basic SSF - bSThe test group objective is to test the INAP procedures at the SSP for basic functions.5.2.1.1Capability tests (CA)The test group objective is to test the SSP general capability of interconnecting with the partner entity.5.2.1.1.1SSF-FSM state "Idle"The test group objective is to check the capability of the IUT of establishing a relation between the SCPand SSP initiated by the SSP or by the SCP.5.2.1.1.1.1Network eventsPreamble:-Postamble:ReleaseCall invoke and terminate the dialogue.IN6210017.1.5.1,9.19To ensure that the IUT being in the "Idle" state, at detection of a TDP,initiates a dialogue and sends an InitialDP invoke containing all mandatoryparameters and all parameters related to the called party, with at least theparameters:-serviceKey,-calledPartyNumber.5.2.1.1.1.2OperationsPreamble:-Postamble:ReleaseCall invoke and terminate the dialogue.IN6211017.1.5.1,9.20To ensure that the IUT being in the "Idle" state, receiving an InitiateCallAttemptinvoke containing mandatory parameters only, with:-destinationRoutingAddress,followed by a RequestReportBCSMEvent invoke with:-bcsmEvents including at least:-eventTypeBCSM (routeSelectFailure),-eventTypeBCSM (oCalledPartyBusy),-eventTypeBCSM (oNoAnswer),-eventTypeBCSM (oAnswer),-monitorMode being interrupted,and a Continue invoke,does not return any error, reject the invoke or abort the dialogue within theoperation time out.SIST ETS 300 374-3:1997
Page 22ETS 300 374-3: February 19965.2.1.1.2SSF-FSM state "Waiting For Instructions"The
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.