SIST ETS 300 403-4:1998

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.VNXãDQMDIntegrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 4: Test Suite Structure and Test Purposes (TSS&TP) specification for the user35.100.30Omrežni slojNetwork layer33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:ETS 300 403-4 Edition 1SIST ETS 300 403-4:1998en01-junij-1998SIST ETS 300 403-4:1998SLOVENSKI
STANDARD
EUROPEANETS 300 403-4TELECOMMUNICATIONJanuary 1997STANDARDSource: ETSI TC-SPSReference: DE/SPS-05091ICS:33.020Key words:ISDN, DSS1, layer 3, testing, TSS&TP, userIntegrated Services Digital Network (ISDN);Digital Subscriber Signalling System No. one (DSS1) protocol;Signalling network layer for circuit-mode basic call control;Part 4: Test Suite Structure and Test Purposes (TSS&TP)specification for the userETSIEuropean 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 4 92 94 42 00 - Fax: +33 4 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 1997. All rights reserved.SIST ETS 300 403-4:1998

Page 2ETS 300 403-4: January 1997Whilst 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 403-4:1998

Page 3ETS 300 403-4: January 1997ContentsForeword.71Scope.92Normative references.93Definitions.103.1Definitions related to conformance testing.103.2Definitions related to ETS 300 403-1.104Abbreviations.115Test Suite Structure (TSS).126Test purposes (TP).146.1Introduction.146.1.1TP naming convention.146.1.2Source of TP definition.146.1.3TP structure.156.1.4Test strategy.156.1.5Test of call states.156.1.6Test of inopportune and syntactically invalid behaviour.166.2TPs for the basic call control, layer 3, user.166.2.1Null call state U00.166.2.1.1Valid.166.2.1.2Inopportune.196.2.1.3Syntactically invalid.206.2.1.4Active.216.2.2Call Initiated call state U01.226.2.2.1Valid.226.2.2.2Inopportune.226.2.2.3Syntactically invalid.236.2.2.4Active.246.2.3Overlap Sending call state U02.246.2.3.1Valid.246.2.3.2Inopportune.256.2.3.3Syntactically invalid.266.2.3.4Active.276.2.4Outgoing Call Proceeding call state U03.276.2.4.1Valid.276.2.4.2Inopportune.286.2.4.3Syntactically invalid.296.2.4.4Active.306.2.5Call Delivered call state U04.316.2.5.1Valid.316.2.5.2Inopportune.316.2.5.3Syntactically invalid.326.2.5.4Active.336.2.6Call Received call state U07.346.2.6.1Valid.346.2.6.2Inopportune.346.2.6.3Syntactically invalid.356.2.6.4Active.366.2.7Connect Request call state U08.376.2.7.1Valid.376.2.7.2Inopportune.37SIST ETS 300 403-4:1998

Page 4ETS 300 403-4: January 19976.2.7.3Syntactically invalid.386.2.7.4Active.396.2.8Incoming Call Proceeding call state U09.406.2.8.1Valid.406.2.8.2Inopportune.406.2.8.3Syntactically invalid.416.2.8.4Active.426.2.9Active call state U10 (Incoming call).436.2.9.1Valid.436.2.9.2Inopportune.446.2.9.3Syntactically invalid.456.2.9.4Active.466.2.10Active call state U10 (Outgoing call).476.2.10.1Valid.476.2.10.2Inopportune.486.2.10.3Syntactically invalid.496.2.10.4Active.506.2.11Disconnect Request call state U11 (Incoming call).516.2.11.1Valid.516.2.11.2Inopportune.516.2.11.3Syntactically invalid.526.2.11.4Active.536.2.12Disconnect Request call state U11 (Outgoing call).536.2.12.1Valid.536.2.12.2Inopportune.546.2.12.3Syntactically invalid.556.2.12.4Active.566.2.13Disconnect Indication call state U12 (Incoming call).566.2.13.1Valid.566.2.13.2Inopportune.566.2.13.3Syntactically invalid.576.2.13.4Active.586.2.14Disconnect Indication call state U12 (Outgoing call).586.2.14.1Valid.586.2.14.2Inopportune.596.2.14.3Syntactically invalid.606.2.14.4Active.606.2.15Suspend Request call state U15 (Incoming call).616.2.15.1Valid.616.2.15.2Inopportune.616.2.15.3Syntactically invalid.636.2.15.4Active.646.2.16Suspend Request call state U15 (Outgoing call).646.2.16.1Valid.646.2.16.2Inopportune.656.2.16.3Syntactically invalid.666.2.16.4Active.676.2.17Resume Request call state U17.676.2.17.1Valid.676.2.17.2Inopportune.676.2.17.3Syntactically invalid.686.2.17.4Active.696.2.18Release Request call state U19 (Incoming call).696.2.18.1Valid.696.2.18.2Inopportune.706.2.18.3Syntactically invalid.716.2.18.4Active.726.2.19Release Request call state U19 (Outgoing call).726.2.19.1Valid.726.2.19.2Inopportune.726.2.19.3Syntactically invalid.736.2.19.4Active.74SIST ETS 300 403-4:1998

Page 5ETS 300 403-4: January 19976.2.20Overlap Receiving call state U25.746.2.20.1Valid.746.2.20.2Inopportune.756.2.20.3Syntactically invalid.766.2.20.4Active.776.2.21Restart null call state R00 (Incoming call).776.2.21.1Valid.776.2.21.2Inopportune.786.2.21.3Syntactically invalid.786.2.21.4Active.806.2.22Restart null call state R00 (Outgoing call).806.2.22.1Valid.806.2.22.2Inopportune.816.2.22.3Syntactically invalid.816.2.22.4Active.836.2.23Restart Request call state R01.836.2.23.1Valid.836.2.23.2Inopportune.836.2.23.3Syntactically invalid.846.2.23.4Active.856.2.24Message segmentation procedure.856.2.24.1Valid.856.2.24.2Inopportune.866.2.24.3Syntactically invalid.866.2.24.4Active.867Compliance.878Requirements for a comprehensive testing service.87History.88SIST ETS 300 403-4:1998

Page 6ETS 300 403-4: January 1997Blank pageSIST ETS 300 403-4:1998

Page 7ETS 300 403-4: January 1997ForewordThis 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 4 of a multi-part standard covering the Digital Subscriber Signalling System No. one(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) signalling network layerfor circuit-mode basic call control, as described below:Part 1:"Protocol specification [ITU-T Recommendation Q.931 (1993), modified]";Part 2:"Specification and Description Language (SDL) diagrams";Part 3:"Protocol Implementation Conformance Statement (PICS) proforma specification";Part 4:"Test Suite Structure and Test Purposes (TSS&TP) specification for the user";Part 5:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing(PIXIT) proforma specification for the user";Part 6:"TSS&TP specification for the network";Part 7:"ATS and partial PIXIT proforma specification for the network".Transposition datesDate of adoption:20 December 1996Date of latest announcement of this ETS (doa):30 April 1997Date of latest publication of new National Standardor endorsement of this ETS (dop/e):31 October 1997Date of withdrawal of any conflicting National Standard (dow):31 October 1997SIST ETS 300 403-4:1998

Page 8ETS 300 403-4: January 1997Blank pageSIST ETS 300 403-4:1998

Page 9ETS 300 403-4: January 19971ScopeThis fourth part of ETS 300 403 specifies the user Test Suite Structure and Test Purposes (TSS&TP) forthe T reference point or coincident S and T reference point (as defined in ITU-T RecommendationI.411 [9]) of implementations conforming to the standards for the signalling network layer for circuit-modebasic call control of the Digital Subscriber Signalling System No. one (DSS1) protocol for the pan-European Integrated Services Digital Network (ISDN), ETS 300 403-1 [1] and ETS 300 403-2 [2].A further part of this ETS specifies the Abstract Test Suite (ATS) and partial Protocol ImplementationeXtra Information for Testing (PIXIT) proforma based on this ETS. Other parts specify the TSS&TP andthe ATS and partial PIXIT proforma for the Network side of the T reference point or coincident S andT reference point of implementations conforming to ETS 300 403-1 [1] and ETS 300 403-2 [2].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 403-1 (1995): "Integrated Services Digital Network (ISDN); DigitalSubscriber Signalling System No. one (DSS1) protocol; Signalling network layerfor circuit-mode basic call control; Part 1: Protocol specification [ITU-TRecommendation Q.931 (1993), modified]".[2]ETS 300 403-2 (1995): "Integrated Services Digital Network (ISDN); DigitalSubscriber Signalling System No. one (DSS1) protocol; Signalling network layerfor circuit-mode basic call control; Part 2: Specification and DescriptionLanguage (SDL) diagrams".[3]ETS 300 403-3 (1993): "Integrated Services Digital Network (ISDN); DigitalSubscriber Signalling System No. one (DSS1) protocol; Signalling network layerfor circuit-mode basic call control; Part 3: Protocol Implementation ConformanceStatement (PICS) proforma specification".[4]ISO/IEC 9646-1: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 1: General Concepts".[5]ISO/IEC 9646-2: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 2: Abstract Test Suite Specification".[6]ISO/IEC 9646-3: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 3: The Tree and Tabular CombinedNotation".[7]CCITT Recommendation E.164 (1991): "Numbering plan for the ISDN era".[8]ITU-T Recommendation I.112 (1993): "Vocabulary and terms for ISDNs".[9]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces -Reference configurations".SIST ETS 300 403-4:1998

Page 10ETS 300 403-4: January 19973DefinitionsFor the purposes of this ETS, the following definitions apply, in addition to those given inETS 300 403-1 [1]:3.1Definitions related to conformance testingabstract test case: Refer to ISO/IEC 9646-1 [4].Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [4].Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [4].active test: A test case where the IUT is required to send a particular message, but not in reaction to areceived message. This would usually involve the use of PIXIT information to see how this message canbe generated and quite often is specified in an ATS using an implicit send event.Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [4].implicit send event: Refer to ISO/IEC 9646-3 [6].lower tester: Refer to ISO/IEC 9646-1 [4].passive test: A test case where the IUT is required to respond to a protocol event (e.g. receivedmessage) with another protocol event (sends message) and which normally does not require any specialoperator intervention such as is associated with the implicit send event.point of control and observation: Refer to ISO/IEC 9646-1 [4].Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [4].PICS proforma: Refer to ISO/IEC 9646-1 [4].Protocol Implementation eXtra Information for Testing (PIXIT): Refer to ISO/IEC 9646-1 [4].PIXIT proforma: Refer to ISO/IEC 9646-1 [4].system under test: Refer to ISO/IEC 9646-1 [4].Test Purpose (TP): Refer to ISO/IEC 9646-1 [4].3.2Definitions related to ETS 300 403-1Integrated Services Digital Network (ISDN): See ITU-T Recommendation I.112 [8], definition 308.ISDN number: A number conforming to the numbering and structure specified in CCITTRecommendation E.164 [7].user: The DSS1 protocol entity at the User side of the user-network interface where a T reference point orcoincident S and T reference point applies.user (S/T): The DSS1 protocol entity at the User side of the user-network interface where a coincidentS and T reference point applies.user (T): The DSS1 protocol entity at the User side of the user-network interface where a T referencepoint applies (User is the private ISDN).SIST ETS 300 403-4:1998

Page 11ETS 300 403-4: January 19974AbbreviationsFor the purposes of this ETS, the following abbreviations apply:AActive test caseATMAbstract Test MethodATSAbstract Test SuiteCRCall ReferenceDSS1Digital Subscriber Signalling System No. oneIInopportune stimulusISDNIntegrated Services Digital NetworkIUTImplementation Under TestPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingR00Restart Null call stateR01Restart Request call stateR02Restart call stateSSyntactically invalid stimulusSEGmessage Segmentation procedureTPTest PurposeTSSTest Suite StructureU00Null call stateU01Call Initiated call stateU02Overlap Sending call stateU03Outgoing Call Proceeding call stateU04Call Delivered call stateU06Call Present call stateU07Call Received call stateU08Connect Request call stateU09Incoming Call Proceeding call stateU10Active call stateU11Disconnect Request call stateU12Disconnect Indication call stateU15Suspend Request call stateU17Resume Request call stateU19Release Request call stateU25Overlap Receiving call stateVValid stimulusSIST ETS 300 403-4:1998

Page 12ETS 300 403-4: January 19975Test Suite Structure (TSS)·
Null call state U00·
Valid·
Inopportune·
Syntactically invalid·
Active·
Call Initiated call state U01·
Valid·
Inopportune·
Syntactically invalid·
Active·
Overlap Sending call state U02·
Valid·
Inopportune·
Syntactically invalid·
Active·
Outgoing Call Proceeding call state U03·
Valid·
Inopportune·
Syntactically invalid·
Active·
Call Delivered call state U04·
Valid·
Inopportune·
Syntactically invalid·
Active·
Call Received call state U07·
Valid·
Inopportune·
Syntactically invalid·
Active·
Connect Request call state U08·
Valid·
Inopportune·
Syntactically invalid·
Active·
Incoming Call Proceeding call state U09·
Valid·
Inopportune·
Syntactically invalid·
Active·
Active call state U10 (Incoming call)·
Valid·
Inopportune·
Syntactically invalid·
Active·
Active call state U10 (Outgoing call)·
Valid·
Inopportune·
Syntactically invalid·
Active·
Disconnect Request call state U11 (Incoming call)·
Valid·
Inopportune·
Syntactically invalid·
ActiveFigure 1 (sheet 1 of 2): Test suite structureSIST ETS 300 403-4:1998

Page 13ETS 300 403-4: January 1997·
Disconnect Request call state U11 (Outgoing call)·
Valid·
Inopportune·
Syntactically invalid·
Active·
Disconnect Indication call state U12 (Incoming call)·
Valid·
Inopportune·
Syntactically invalid·
Active·
Disconnect Indication call state U12 (Outgoing call)·
Valid·
Inopportune·
Syntactically invalid·
Active·
Suspend Request call state U15 (Incoming call)·
Valid·
Inopportune·
Syntactically invalid·
Active·
Suspend Request call state U15 (Outgoing call)·
Valid·
Inopportune·
Syntactically invalid·
Resume Request call state U17·
Valid·
Inopportune·
Syntactically invalid·
Release Request call state U19 (Incoming call)·
Valid·
Inopportune·
Syntactically invalid·
Release Request call state U19 (Outgoing call)·
Valid·
Inopportune·
Syntactically invalid·
Overlap Receiving call state U25·
Valid·
Inopportune·
Syntactically invalid·
Active·
Restart null call state R00 (Incoming call)·
Valid·
Inopportune·
Syntactically invalid·
Active·
Restart null call state R00 (Outgoing call)·
Valid·
Inopportune·
Syntactically invalid·
Active·
Restart Request call state R01·
Valid·
Inopportune·
Syntactically invalid·
Message segmentation procedure·
Valid·
Inopportune·
Syntactically invalid·
ActiveFigure 1 (sheet 2 of 2): Test suite structureSIST ETS 300 403-4:1998

Page 14ETS 300 403-4: January 19976Test Purposes (TP)6.1IntroductionFor each test requirement, a TP is defined.6.1.1TP naming conventionTPs are numbered, starting at 001, within each group. Groups are organized according to the TSS.Additional references are added to identify the actual test suite and whether it applies to the network or theuser (see table 1).Table 1: TP Identifier naming convention schemeIdentifier:___=layer + type of IUT:e.g. "L3U" for layer 3, IUT = user=call state:e.g. U10 for Active call state=group:one character field representing the groupreference according to TSSV:Valid stimulusI: Inopportune stimulusS:Syntactically invalid stimulusA:Active test case=sequential number:(001-999)6.1.2Source of TP definitionThe TPs are based on ETS 300 403-1 [1] and ETS 300 403-2 [2].SIST ETS 300 403-4:1998

Page 15ETS 300 403-4: January 19976.1.3TP structureEach TP has been written in a manner which is consistent with all other TPs. The intention of this is tomake the TPs more readable and checkable. A particular structure has been used which is illustrated intable 2. This table should be read in conjunction with any TP, i.e. please use a TP as an example tofacilitate the full comprehension of table 2.Table 2: Structure of a single TPTP partTextExampleHeader tabsee table 1 tabsubclause 2.3.4 or new TCTC10822 (see note 2)StimulusEnsure that the IUT in theU00, U10, etc. see below for message structureon receipt of a XXXX message(see note 3)or to request a .Reactionsends, saves, does, etc.using en bloc sending, etc.if the action is sending
see below for message structure, etc.and remains in the same stateor and enters state MessagestructuremessageSETUP, FACILITY, CONNECT,etc. (see note 3)a) with a information elementb) indicating in the and back to a) or b)Bearer capability, Facility, etc.NOTE 1:Text in italics will not appear in TPs and text between <> is filled in for each TP and maydiffer from one TP to the next.NOTE 2:These references to I-ETS 300 322 helped in developing this ETS and are of a purelyinformative nature.NOTE 3:All messages shall be considered as "valid and compatible" unless otherwise specified in thetest purpose.6.1.4Test strategyAs the base standard ETS 300 403-1 [1] contains no explicit requirements for testing, the TPs weregenerated as a result of an analysis of the base standard and the PICS specification ETS 300 403-3 [3].The criteria applied include the following:-only the requirements from the point of view of the T or coincident S and T reference point areconsidered;-whether or not a test case can be built from the TP is not considered.6.1.5Test of call statesMany TPs include a reference to the IUT's final call state after the realization of the TP. In these cases theTP includes the requirement to ensure that the IUT has entered this particular final call state. Ensuringthat the IUT is in a particular call state shall be realized by following the procedures described insubclause 5.8.10 of ETS 300 403-1 [1]. According to these procedures, the IUT on receipt of a STATUSENQUIRY message, shall respond with a STATUS message indicating, in the third octet of the Call stateinformation element, the current call state of the IUT. This exchange of messages is not mentionedexplicitly in each TP but is considered to be implicit in the reference to the final call state. This way ofphrasing the TPs has been used to avoid over-complicating the text and structure of the TPs and toimprove the readability.SIST ETS 300 403-4:1998

Page 16ETS 300 403-4: January 19976.1.6Test of inopportune and syntactically invalid behaviourIn the test groups for inopportune and syntactically invalid behaviour the procedures as described insubclause 5.8 of ETS 300 403-1 [1] are tested. This is done in each call state with one message for eachof the described error cases. Messages have been chosen that are, if they are received without theinopportune or erroneous coding, expected messages in the call states under test.Test purposes for inopportune behaviour that is described outside the subclause 5.8 of ETS 300 403-1 [1]are found in the valid test groups. This was done, as these procedures are seen more as a part of thebasic call procedures than as a part of the error handling procedures.6.2TPs for the basic call control, layer 3, userAll PICS items referred to in this subclause are as specified in ETS 300 403-3 [3] unless indicatedotherwise by another numbered reference.6.2.1Null call state U006.2.1.1ValidSelection:IUT supports incoming calls. PICS: MCu 2.L3U_U00_V_001subclauses 5.2.1, 5.2.4, 5.2.5.1TC10005Ensure that the IUT in the Null call state U00, on receipt of a valid SETUP message without the Sendingcomplete information element,sends any of a SETUP ACKNOWLEDGE, CALL PROCEEDING, ALERTING or CONNECTmessage and enters the relevant call state Overlap Receiving U25, Incoming Call Proceeding U09,Call Received U07 or Connect Request U08.Selection:IUT supports overlap receiving. PICS: MCu 2.2.L3U_U00_V_002subclauses 5.2.1, 5.2.5.1TC10006Ensure that the IUT in the Null call state U00, on receipt of a valid SETUP message with the Sendingcomplete information element,sends any of a CALL PROCEEDING, ALERTING or CONNECT message and enters the relevantcall state Incoming Call Proceeding U09, Call Received U07 or Connect Request U08.L3U_U00_V_003subclause 5.2.3.1new TCEnsure that the IUT in the Null call state U00, on receipt of a valid SETUP message (delivered via thepoint-to-point data link) with the Channel identification information element indicating a B-channel that isnot available and indicating in the preferred/exclusive bit "indicated channel is preferred",sends any of a SETUP ACKNOWLEDGE, CALL PROCEEDING, ALERTING or CONNECTmessage with the Channel identification information element indicating a B-channel that is availableand indicating in the preferred/exclusive bit "exclusive: only the indicated channel is acceptable" andenters the relevant call state Overlap Receiving U25, Incoming Call Proceeding U09, Call ReceivedU07 or Connect Request U08.Selection:IUT supports point-to-point configuration. PICS: R 7.1.L3U_U00_V_004subclause 5.2.3.1new TCEnsure that the IUT in the Null call state U00, on receipt of a valid SETUP message (delivered via thepoint-to-point data link) with the Channel identification information element indicating a B-channel that isnot available and indicating in the preferred/exclusive bit "exclusive: only the indicated channel isacceptable",sends a RELEASE COMPLETE message with a Cause information element indicating the causevalue 44 "requested circuit/channel/channel not available" and remains in the Null call state.Selection:IUT supports point-to-point configuration. PICS: R 7.1.SIST ETS 300 403-4:1998

Page 17ETS 300 403-4: January 1997L3U_U00_V_005subclause 5.2.3.1new TCEnsure that the IUT in the Null call state U00, on receipt of a valid SETUP message (delivered via thepoint-to-point data link) with the Channel identification information element indicating a B-channel andindicating in the preferred/exclusive bit "indicated channel is preferred", when no B-channel is available,sends a RELEASE COMPLETE message with a Cause information element indicating the causevalue 34 "no circuit/channel available" and remains in the Null call state.Selection:IUT supports point-to-point configuration. PICS: R 7.1.L3U_U00_V_006subclause 5.2.3.1new TCEnsure that the IUT in the Null call state U00, on receipt of a valid SETUP message (delivered via thepoint-to-point data link) with the Channel identification information element indicating in the channelselection "any channel", when no B-channel is available,sends a RELEASE COMPLETE message with a Cause information element indicating the causevalue 34 "no circuit/channel available" and remains in the Null call state.Selection:IUT supports point-to-point configuration. PICS: R 7.1.L3U_U00_V_007subclause 5.2.3.2new TCEnsure that the IUT in the Null call state U00, on receipt of a valid SETUP message (delivered via thebroadcast data link) with the Channel identification information element indicating a B-channel that is notavailable and indicating in the preferred/exclusive bit "exclusive: only the indicated channel is acceptable",sends a RELEASE COMPLETE message with a Cause information element indicating the causevalue 44 "requested circuit/channel not available" and remains in the Null call state.Selection:IUT supports point-to-multipoint configuration. PICS: R 7.2.L3U_U00_V_008annex Bnew TCEnsure that the IUT in the Null call state U00, on receipt of a SETUP message without the Sendingcomplete information element and with the Called party number information element containingmismatching number digits,sends no message and remains in the Null call state U00.L3U_U00_V_009annex Bnew TCEnsure that the IUT in the Null call state U00, on receipt of a SETUP message without the Sendingcomplete information element and with the Called subaddress information element containingmismatching subaddress digits,sends no message and remains in the Null call state U00.L3U_U00_V_010subclause 5.2.5.1new TCEnsure that the busy IUT in the Null call state U00, on receipt of a SETUP message with the Sendingcomplete information element,sends a RELEASE COMPLETE message with a Cause information element indicating the causevalue 17 "user busy" and remains in the Null call state U00.L3U_U00_V_011subclause 5.2.5.1new TCEnsure that the IUT in the Null call state U00, on receipt of a SETUP message with the Sending Completeinformation element, to refuse the call,sends a RELEASE COMPLETE message with a Cause information element indicating the causevalue 21 "call rejected" and remains in the Null call state U00.L3U_U00_V_012subclause 5.2.6, annex BTC10007Ensure that the IUT in the Null call state U00, on receipt of a valid SETUP message without High and Lowlayer compatibility information elements but with a Progress indicator information element indicating theprogress description 1 "call is not end-to-end ISDN",modifies its compatibility checking and accepts the call on the basis of a compatible Bearercapability information element.Selection:IUT supports compatibility checking of the higher layers. PICS: SCu 8 ANDIUT supports compatibility checking of the lower layers. PICS: SCu 6.L3U_U00_V_013subclauses 5.2.2, 5.2.5.1, annex BTC10008Ensure that the IUT in the Null call state U00, on receipt of a SETUP message (delivered via thebroadcast data link) containing an incompatible Bearer capability information element,sends no message or sends a RELEASE COMPLETE message with the Cause informationelement indicating cause value 88 "incompatible destination" and remains in the Null call state U00.Selection:IUT supports point-to-multipoint configuration. PICS: R 7.2.SIST ETS 300 403-4:1998

Page 18ETS 300 403-4: January 1997L3U_U00_V_014subclauses 5.2.2, 5.2.5.1, annex BTC10008Ensure that the IUT in the Null call state U00, on receipt of a SETUP message (delivered via the point-to-point data link) containing an incompatible Bearer capability information element,sends a RELEASE COMPLETE message with the Cause information element indicating causevalue 88 "incompatible destination" and remains in the Null call state U00.Selection:IUT supports point-to-point configuration. PICS: R 7.1.L3U_U00_V_015subclauses 5.2.2, 5.2.5.1, annex BTC10009Ensure that the IUT in the Null call state U00, on receipt of a SETUP message (delivered via thebroadcast data link) containing an incompatible High layer compatibility information element,sends no message or sends a RELEASE COMPLETE message with the Cause informationelement indicating cause value 88 "incompatible destination" and remains in the Null call state U00.Selection:IUT supports point-to-multipoint configuration. PICS: R 7.2 ANDIUT supports compatibility checking of the higher layers. PICS: SCu 8.L3U_U00_V_016subclauses 5.2.2, 5.2.5.1, annex BTC10009Ensure that the IUT in the Null call state U00, on receipt of a SETUP message (delivered via the point-to-point data link) containing an incompatible High layer compatibility information element,sends a RELEASE COMPLETE message with the Cause information element indicating causevalue 88 "incompatible destination" and remains in the Null call state U00.Selection:IUT supports point-to-point configuration. PICS: R 7.1 ANDIUT supports compatibility checking of the higher layers. PICS: SCu 8.L3U_U00_V_017subclauses 5.2.2, 5.2.5.1, annex Bnew TCEnsure that the IUT in the Null call state U00, on receipt of a SETUP message (delivered via thebroadcast data link) containing a Low layer compatibility information element that is incompatible in thepart that provides additional information to the information given in the Bearer capability informationelement,sends no message or sends a RELEASE COMPLETE message with the Cause informationelement indicating cause value 88 "incompatible destination" and remains in the Null call state U00.Selection:IUT supports point-to-multipoint configuration. PICS: R 7.2 ANDIUT supports compatibility checking of the lower layers. PICS: SCu 6.L3U_U00_V_018subclauses 5.2.2, 5.2.5.1, annex Bnew TCEnsure that the IUT in the Null call state U00, on receipt of a SETUP message (delivered via the point-to-point data link) containing a Low layer compatibility information element that is incompatible in the part thatprovides additional information to the information given in the Bearer capability information element,sends a RELEASE COMPLETE message with the Cause information element indicating causevalue 88 "incompatible destination" and remains in the Null call state U00.Selection:IUT supports point-to-point configuration. PICS: R 7.1 ANDIUT supports compatibility checking of the lower layers. PICS: SCu 6.L3U_U00_V_019subclauses 5.2.2, 5.2.5.1, annex Bnew TCEnsure that the IUT in the Null call state U00, on receipt of a SETUP containing a Low layer compatibilityinformation element that is incompatible and that provides no additional information to the informationgiven in the Bearer capability information element,sends any of a CALL PROCEEDING, ALERTING or CONNECT message and enters the relevantcall state Incoming Call Proceeding U09, Call Received U07 or Connect Request U08.Selection:IUT supports compatibility checking of the lower layers. PICS: SCu 6.L3U_U00_V_020subclause 5.11.1new TCEnsure that the IUT in the Null call state U00, on receipt of a SETUP message with two Bearer capabilityinformation elements,sends any of a CALL PROCEEDING, ALERTING or CONNECT message and enters the relevantcall state Incoming Call Proceeding U09, Call Received U07 or Connect Request U08.Selection:IUT supports processing of incoming Bearer capability selection request.PICS MCu 21.2SIST ETS 300 403-4:1998

Page 19ETS 300 403-4: January 1997L3U_U00_V_021subclause 5.12.1new TCEnsure that the IUT in the Null call state U00, on receipt of a SETUP message with two High layercompatibility information elements,sends any of a CALL PROCEEDING, ALERTING or CONNECT message and enters the relevantcall state Incoming Call Proceeding U09, Call Received U07 or Connect Request U08.Selection:IUT supports processing of incoming High layer compatibility selection request.PICS MCu 22.26.2.1.2InopportuneSelection:IUT supports incoming calls. PICS: MCu 2.L3U_U00_I_001subclause 5.8.3.1TC10020Ensure that the IUT in the Null call state U00, on receipt of a SETUP message using the dummy callreference,sends no message and remains in the Null call state U00.L3U_U00_I_002subclause 5.8.3.2 a)TC10010Ensure that the IUT in the Null call state U00, on receipt of an inopportune message (DISCONNECT, callreference not recognized as relating to a call),sends a RELEASE or a RELEASE COMPLETE message with a Cause information elementindicating the cause value 81 "invalid call reference value" and enters the Release Request callstate U19 or remains in the Null call state U00.L3U_U00_I_003subclause 5.8.3.2 b)TC10002Ensure that the IUT in the Null call state U00, on receipt of a RELEASE message,sends a RELEASE COMPLETE message with a Cause information element indicating the causevalue 81 "invalid call reference value" and remains in the Null call state U00.L3U_U00_I_004subclause 5.8.3.2 c)TC10001Ensure that the IUT in the Null call state U00, on receipt of a RELEASE COMPLETE message,sends no message and remains in the Null call state U00.L3U_U00_I_005subclause 5.8.3.2 d)TC10014Ensure that the IUT in the Null call state U00, on receipt of a SETUP message with a call reference flag bitset to 1,sends no message and remains in the Null call state U00.L3U_U00_I_006subclause 5.8.3.2 f)TC10021Ensure that the IUT in the Null call state U00, on receipt of a SETUP message using the global callreference,sends a STATUS message using the global call reference with a Call state information elementindicating the call state associated with the global call reference and a Cause information elementindicating the cause value 81 "invalid call reference value" and remains in the Null call state U00.L3U_U00_I_007subclauses 5.8.3.2 g), 5.8.11TC10004Ensure that the IUT in the Null call state U00, on receipt of a STATUS message with a Call stateinformation element indicating a call state other than the Null call state,sends a RELEASE or a RELEASE COMPLETE message with a Cause information elementindicating the cause value 101 "message not compatible with call state" and enters the ReleaseRequest call state U19 or remains in the Null call state U00.L3U_U00_I_008subclauses 5.8.3.2 g), 5.8.11TC10003Ensure that the IUT in the Null call state U00, on receipt of a STATUS message with a Call stateinformation element indicating the Null call state,sends no message and remains in the Null call state U00.L3U_U00_I_009subclauses 5.8.3.2 g), 5.8.11new TCEnsure that the IUT in the Null call state U00, on receipt of a STATUS message using the global callreference and with a Call state information element indicating a call state other than the Null call state,sends no message and remains in the Null call state U00.SIST ETS 300 403-4:1998

Page 20ETS 300 403-4: January 1
...