SIST ETS 300 369-3:1998

Integrated Services Digital Network (ISDN); Explicit Call Transfer (ECT) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user

,

Digitalno omrežje z integriranimi storitvami (ISDN) - Dopolnilna storitev: nedvoumna predaja klica (ECT) - Protokol digitalne naročniške signalizacije št. 1 (DSS1) - 3. del: Zgradba preskušalnega niza in namen preskušanja (TSS&TP) - Specifikacija za uporabnika

General Information

• Status: Published
• Publication Date: 31-May-1998
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• Technical Committee: SPS - Signalling protocols and switching
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jun-1998
• Due Date: 01-Jun-1998
• Completion Date: 01-Jun-1998
• Ref Project: ETSI ETS 300 369-3 ed.1 (1996-10) - Integrated Services Digital Network (ISDN); Explicit Call Transfer (ECT) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.VWRULWHYIntegrated Services Digital Network (ISDN); Explicit Call Transfer (ECT) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:ETS 300 369-3 E13SIST ETS 300 369-3:1998en01-MDQXDU-19983SIST ETS 300 369-3:1998SLOVENSKI
STANDARD



SIST ETS 300 369-3:1998



EUROPEANETS 300 369-3TELECOMMUNICATIONOctober 1996STANDARDSource: ETSI TC-SPSReference: DE/SPS-05061-Q1-3ICS:33.080Key words:ISDN, DSS1, supplementary service, ECT, testing, TSS&TP, userIntegrated Services Digital Network (ISDN);Explicit Call Transfer (ECT) supplementary service;Digital Subscriber Signalling System No. one (DSS1) protocol;Part 3: 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: [e-mail].: [phone] - Fax: [phone]Copyright 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 369-3:1998



Page 2ETS 300 369-3: October 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 369-3:1998



Page 3ETS 300 369-3: October 1996ContentsForeword.51Scope.72Normative references.73Definitions.83.1Definitions related to conformance testing.83.2Definitions related to ETS 300 369-1.84Abbreviations.95Test Suite Structure (TSS).96Test Purposes (TP).106.1Introduction.106.1.1TP naming convention.106.1.2Source of TP definition.106.1.3TP structure.106.1.4Test strategy.116.2User TPs for ECT.126.2.1User (S/T).126.2.1.1Served user.126.2.1.1.1Implicit linkage procedures.126.2.1.1.1.1Valid.126.2.1.1.1.2Invalid.136.2.1.1.2Explicit linkage procedures.136.2.1.1.2.1Valid.136.2.1.1.2.2Invalid.156.2.1.1.3Confirmation of call transfer.166.2.1.1.3.1Valid.176.2.1.1.3.2Invalid.186.2.1.2Remote user.196.2.2User (T).196.2.2.1Served user connected.196.2.2.2Remote user connected.217Compliance.218Requirements for a comprehensive testing service.22History.23SIST ETS 300 369-3:1998



Page 4ETS 300 369-3: October 1996Blank pageSIST ETS 300 369-3:1998



Page 5ETS 300 369-3: October 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 Digital Subscriber Signalling System No. one(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) Explicit Call Transfer(ECT) supplementary service, 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 the user";Part 4:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information forTesting (PIXIT) proforma specification for the user";Part 5:"TSS&TP specification for the network";Part 6:"ATS and partial PIXIT proforma specification for the network".Transposition datesDate of adoption of this ETS:4 October 1996Date of latest announcement of this ETS (doa):31 January 1997Date of latest publication of new National Standardor endorsement of this ETS (dop/e):31 July 1997Date of withdrawal of any conflicting National Standard (dow):31 July 1997SIST ETS 300 369-3:1998



Page 6ETS 300 369-3: October 1996Blank pageSIST ETS 300 369-3:1998



Page 7ETS 300 369-3: October 19961ScopeThis third part of ETS 300 369 specifies the Test Suite Structure and Test Purposes (TSS&TP) for theUser side of the T reference point or coincident S and T reference point (as defined in ITU-TRecommendation I.411 [7]) of implementations conforming to the stage three standard for the Explicit CallTransfer (ECT) supplementary service for the pan-European Integrated Services Digital Network (ISDN)by means of the Digital Subscriber Signalling System No. one (DSS1) protocol, ETS 300 369-1 [1].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 369-1 [1].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 369-1 (1995): "Integrated Services Digital Network (ISDN); Explicit CallTransfer (ECT) supplementary service; Digital Subscriber Signalling System No.one (DSS1) protocol; Part 1: Protocol specification".[2]ETS 300 369-2 (1996): "Integrated Services Digital Network (ISDN); Explicit CallTransfer (ECT) supplementary service; Digital Subscriber Signalling System No.one (DSS1) protocol; Part 2: Protocol Implementation Conformance Statement(PICS) proforma specification".[3]ISO/IEC 9646-1: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 1: General Concepts".[4]ISO/IEC 9646-2: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 2: Abstract Test Suite specification".[5]ISO/IEC 9646-3: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 3: The Tree and Tabular CombinedNotation".[6]ETS 300 196-1 (1993): "Integrated Services Digital Network (ISDN); Genericfunctional protocol for the support of supplementary services; Digital SubscriberSignalling System No. one (DSS1) protocol; Part 1: Protocol specification".[7]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces -Reference configurations".[8]ETS 300 102-1: "Integrated Services Digital Network (ISDN);User-network interface layer 3; Specifications for basic call control".[9]ITU-T Recommendation I.112 (1993): "Vocabulary and terms for ISDNs".[10]CCITT Recommendation E.164 (1991): "Numbering plan for the ISDN era".[11]ITU-T Recommendation I.210 (1993): "Principles of the telecommunicationservices supported by an ISDN and the means to describe them".SIST ETS 300 369-3:1998



Page 8ETS 300 369-3: October 19963DefinitionsFor the purposes of this ETS, the following definitions apply:3.1Definitions related to conformance testingabstract test case: Refer to ISO/IEC 9646-1 [3].Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [3].Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [3].implicit send event: Refer to ISO/IEC 9646-3 [5].lower tester: Refer to ISO/IEC 9646-1 [3].point of control and observation: Refer to ISO/IEC 9646-1 [3].Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [3].PICS proforma: Refer to ISO/IEC 9646-1 [3].Protocol Implementation eXtra Information for Testing (PIXIT): Refer to ISO/IEC 9646-1 [3].PIXIT proforma: Refer to ISO/IEC 9646-1 [3].system under test: Refer to ISO/IEC 9646-1 [3].Test Purpose (TP): Refer to ISO/IEC 9646-1 [3].3.2Definitions related to ETS 300 369-1Call Held auxiliary state: See ETS 300 196-1 [6], subclause 7.1.2.Call Reference (CR): See ETS 300 102-1 [8], subclause 4.3.component: See ETS 300 196-1 [6], subclause 11.2.2.1.Idle auxiliary state: See ETS 300 196-1 [6], subclause 7.1.2.Integrated Services Digital Network (ISDN): See ITU-T Recommendation I.112 [9], definition 308.ISDN number: A number conforming to the numbering and structure specified inCCITT Recommendation E.164 [10].invoke component: See ETS 300 196-1 [6], subclause 11.2.2.1.return error component: See ETS 300 196-1 [6], subclause 11.2.2.1.return result component: See ETS 300 196-1 [6], subclause 11.2.2.1.served user: The served user is the user who invokes the ECT supplementary service.service; telecommunication service: See ITU-T Recommendation I.112 [9], definition 201.supplementary service: See ITU-T Recommendation I.210 [11], subclause 2.4.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.SIST ETS 300 369-3:1998



Page 9ETS 300 369-3: October 1996user (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).4AbbreviationsFor the purposes of this ETS, the following abbreviations apply:(Held)Call Held auxiliary state(Idle)Idle auxiliary stateATMAbstract Test MethodATSAbstract Test SuiteCRCall ReferenceCR1CR one (held or idle)CR2CR two (held or idle)CR3CR three (held, with CR1 and CR2 idle)DSS1Digital Subscriber Signalling System No. oneECTExplicit Call TransferISDNIntegrated Services Digital NetworkIUTImplementation Under TestPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingTPTest PurposeTSSTest Suite StructureU04Call Delivered call stateU10Active call stateU19Release Request call state5Test Suite Structure (TSS)ECT - UserUser (S/T)User (T)Served userRemote user(07)Served user connected(08)Remote user connected(09)Implicit linkageproceduresExplicit linkageproceduresConfirmation ofcall transferValid(01)Invalid(02)Valid(03)Invalid(04)Valid(05)Invalid(06)NOTE:Numbers in brackets represent group numbers and are used in TP identifiers.Figure 1: Test suite structureSIST ETS 300 369-3:1998



Page 10ETS 300 369-3: October 19966Test 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:__=supplementary service:e.g. "ECT"=type of IUT:UUserNNetwork=group2 digit field representing group reference according to TSS=sequential number(001-999)6.1.2Source of TP definitionThe TPs are based on ETS 300 369-1 [1].6.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 and this is illustrated intable 2. This table should be read in conjunction with any TP, i.e. use a TP as an example to fullyunderstand the table.SIST ETS 300 369-3:1998



Page 11ETS 300 369-3: October 1996Table 2: Structure of a single TPTP partTextExampleHeader tabsee table 1 tabsubclause 0.0.0 tabvalid, invalid, inopportune CR.mandatory, optional, conditionalStimulusEnsure that the IUT in theECT Implicit Request stateand with CR1 in ()U10 (Idle), U10 (Held), etc.and with CR2 in ()"and with CR3 in ()" see below for message structurereceiving a XXXX messageor to request a .Reactionsends, saves, does, etc.using en-bloc sending, .if the action is sending
see below for message structure, etc.and enters and/or and remains in the same call state(s)or and enters call state with CRMessagestructuremessage containing aSETUP, FACILITY, CONNECT, .a) information element withb) a encoded as or including and back to a or b,Bearer capability, Facility, .Note: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.6.1.4Test strategyAs the base standard ETS 300 369-1 [1] contained no explicit requirements for testing, the TPs weregenerated as a result of an analysis of the base standard and the PICS specification, ETS 300 369-2 [2].The criteria applied included 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.SIST ETS 300 369-3:1998



Page 12ETS 300 369-3: October 19966.2User TPs for ECT6.2.1User (S/T)Selection:IUT supports coincident S and T reference point procedures. PICS: R 3.1.6.2.1.1Served userSelection:IUT can handle two calls.Selection:IUT supports Call hold supplementary service.6.2.1.1.1Implicit linkage procedures6.2.1.1.1.1ValidECT_U01_001subclause 9.2.1.1validmandatoryEnsure that the IUT in the ECT Idle state, with CR1 in call state U10 (Held) and CR2 in call stateU10 (Idle) to request ECT using implicit linkage procedure,sends a FACILITY message with CR1 containing a Facility information element with an EctExecuteinvoke component and enters the ECT Implicit Request state and remains in the same call states.ECT_U01_002subclause 9.2.1.1validoptionalEnsure that the IUT in the ECT Idle state, with CR1 in call state U10 (Held) and CR2 in call stateU04 (Idle) to request ECT using implicit linkage procedure,sends a FACILITY message with CR1 containing a Facility information element with an EctExecuteinvoke component and enters the ECT Implicit Request state and remains in the same call states.Selection:IUT supports transfer with one answered and one alerting call. PICS: MC 3.ECT_U01_003subclause 9.2.1.1validoptionalEnsure that the IUT in the ECT Idle state, with CR2 in call state U10 (Idle) and CR1 in call stateU04 (Held) to request ECT using implicit linkage procedure,sends a FACILITY message with CR1 containing a Facility information element with an EctExecuteinvoke component and enters the ECT Implicit Request state and remains in the same call states.Selection:IUT supports transfer with one answered and one alerting call. PICS: MC 3.ECT_U01_004subclause 9.2.1.2validmandatoryEnsure that the IUT in the ECT Implicit Request state, with CR1 in call state U10 (Held) and CR2 in callstate U10 (Idle) receiving a valid FACILITY message with CR1 containing a Facility information elementwith an EctExecute return error component,enters the ECT Idle state and remains in the same call states.ECT_U01_005subclause 9.2.1.2validoptionalEnsure that the IUT in the ECT Implicit Request state, with CR1 in call state U10 (Held) and CR2 in callstate U04 (Idle) receiving a valid FACILITY message with CR1 containing a Facility information elementwith an EctExecute return error component,enters the ECT Idle state and remains in the same call states.Selection:IUT supports transfer with one answered and one alerting call. PICS: MC 3.ECT_U01_006subclause 9.2.1.2validoptionalEnsure that the IUT in the ECT Implicit Request state, with CR2 in call state U10 (Idle) and CR1 in callstate U04 (Held) receiving a valid FACILITY message with CR1 containing a Facility information elementwith an EctExecute return error component,enters the ECT Idle state and remains in the same call states.Selection:IUT supports transfer with one answered and one alerting call. PICS: MC 3.ECT_U01_007subclause 9.2.1.2validmandatoryEnsure that the IUT in the ECT Implicit Request state, with CR1 in call state U10 (Held) and CR2 in callstate U10 (Idle) receiving a valid FACILITY message with CR1 containing a Facility information elementwith a reject component,enters the ECT Idle state and remains in the same call states.SIST ETS 300 369-3:1998



Page 13ETS 300 369-3: October 1996ECT_U01_008subclause 9.2.1.2validoptionalEnsure that the IUT in the ECT Implicit Request state, with CR1 in call state U10 (Held) and CR2 in callstate U04 (Idle) receiving a valid FACILITY message with CR1 containing a Facility information elementwith a reject component,enters the ECT Idle state and remains in the same call states.Selection:IUT supports transfer with one answered and one alerting call. PICS: MC 3.ECT_U01_009subclause 9.2.1.2validoptionalEnsure that the IUT in the ECT Implicit Request state, with CR2 in call state U10 (Idle) and CR1 in callstate U04 (Held) receiving a valid FACILITY message with CR1 containing a Facility information elementwith a reject component,enters the ECT Idle state and remains in the same call states.Selection:IUT supports transfer with one answered and one alerting call. PICS: MC 3.6.2.1.1.1.2InvalidECT_U02_001subclause 7.2invalidmandatoryEnsure that the IUT in the ECT Implicit Request state, with CR1 in call state U10 (Held) and CR2 in callstate U10 (Idle) receiving a valid FACILITY message with CR1 containing a Facility information elementwith an invalid EctExecute return error component,sends a FACILITY message containing a Facility information element with a reject component andremains in the same auxiliary and call states.ECT_U02_002subclause 7.2invalidoptionalEnsure that the IUT in the ECT Implicit Request state, with CR1 in call state U10 (Held) and CR2 in callstate U04 (Idle) receiving a valid FACILITY message with CR1 containing a Facility information elementwith an invalid EctExecute return error component,sends a FACILITY message containing a Facility information element with a reject component andremains in the same auxiliary and call states.Selection:IUT supports transfer with one answered and one alerting call. PICS: MC 3.ECT_U02_003subclause 7.2invalidoptionalEnsure that the IUT in the ECT Implicit Request state, with CR2 in call state U10 (Idle) and CR1 in callstate U04 (Held) receiving a valid FACILITY message with CR1 containing a Facility information elementwith an invalid EctExecute return error component,sends a FACILITY message containing a Facility information element with a reject component andremains in the same auxiliary and call states.Selection:IUT supports transfer with one answered and one alerting call. PICS: MC 3.6.2.1.1.2Explicit linkage proceduresSelection:IUT supports explicit linkage procedures. PICS: MC 2.6.2.1.1.2.1ValidECT_U03_001subclause 9.2.2.1.1validmandatoryEnsure that the IUT in the ECT Idle state and with CR3 in call state U10 (Idle) and CR2 in call stateU10 (Idle) and CR1 in call state U10 (Held) in order to initiate the explicit linkage procedure,sends a FACILITY message with CR2 containing a Facility information element with anEctLinkIdRequest invoke component and enters ECT LinkId Request state and remains in thesame call states.ECT_U03_002subclause 9.2.2.1.1validoptionalEnsure that the IUT in the ECT Idle state and with CR3 in call state U10 (Idle) and CR2 in call stateU04 (Idle) and CR1 in call state U10 (Held) in order to initiate the explicit linkage procedure,sends a FACILITY message with CR2 containing a Facility information element with anEctLinkIdRequest invoke component and enters ECT LinkId Request state and remains in thesame call states.Selection:IUT supports transfer with one answered and one alerting call. PICS: MC 3.SIST ETS 300 369-3:1998



Page 14ETS 300 369-3: October 1996ECT_U03_003subclause 9.2.2.1.1validmandatoryEnsure that the IUT in the ECT LinkId Request state (invoked via CR2) and with CR3 in call stateU10 (Idle) and CR2 in call state U10 (Idle) and CR1 in call state U10 (Held) receiving a valid FACILITYmessage with CR2 containing a Facility information element with a LinkId value in an EctLinkIdRequestreturn result component,enters the ECT LinkId Assigned state and remains in the same call states.ECT_U03_004subclause 9.2.2.1.1validoptionalEnsure that the IUT in the ECT LinkId Request state (invoked via CR2) and with CR3 in call stateU10 (Idle) and CR2 in call state U04 (Idle) and CR1 in call state U10 (Held) receiving a valid FACILITYmessage with CR2 containing a Facility information element with a LinkId value in an EctLinkIdRequestreturn result component,enters the ECT Link Id Assigned state and remains in the same call states.Selection:IUT supports transfer with one answered and one alerting call. PICS: MC 3.ECT_U03_005subclause 9.2.2.1.2validmandatoryEnsure that the IUT in the ECT LinkId Request state (invoked via CR2) and with CR3 in call stateU10 (Idle) and CR2 in call state U10 (Idle) and CR1 in call state U10 (Held) receiving a valid FACILITYmessage with CR2 containing a Facility information element with an EctLinkIdRequest return errorcomponent,enters the ECT Idle state and remains in the same call states.ECT_U03_006subclause 9.2.2.1.2validoptionalEnsure that the IUT in the ECT LinkId Request state (invoked via CR2) and with CR3 in call stateU10 (Idle) and CR2 in call state U04 (Idle) and CR1 in call state U10 (Held) receiving a valid FACILITYmessage with CR2 containing a Facility information element with an EctLinkIdRequest return errorcomponent,enters the ECT Idle state and remains in the same call states.Selection:IUT supports transfer with one answered and one alerting call. PICS: MC 3.ECT_U03_007subclause 9.2.2.1.2validmandatoryEnsure that the IUT in the ECT LinkId Request state (invoked via CR2) and with CR3 in call stateU10 (Idle) and CR2 in call state U10 (Idle) and CR1 in call state U10 (Held) receiving a valid FACILITYmessage with CR2 containing a Facility information element with a reject component,enters the ECT Idle state and remains in the same call states.ECT_U03_008subclause 9.2.2.1.2validoptionalEnsure that the IUT in the ECT LinkId Request state (invoked via CR2) and with CR3 in call stateU10 (Idle) and CR2 in call state U04 (Idle) and CR1 in call state U10 (Held) receiving a valid FACILITYmessage with CR2 containing a Facility information element with a reject component,enters the ECT Idle state and remains in the same call states.Selection:IUT supports transfer with one answered and one alerting call. PICS: MC 3.ECT_U03_009subclause 9.2.2.2.1validmandatoryEnsure that the IUT in the ECT LinkId Assigned state (invoked via CR2) and with CR3 in call stateU10 (Idle) and CR2 in call state U10 (Idle) and CR1 in call state U10 (Held) to request ECT using explicitlinkage procedure,sends a FACILITY message with CR1 containing a Facility information element with anExplicitEctExecute invoke component including the previously received LinkId value and enters theECT Explicit Request state and remains in the same call states.ECT_U03_010subclause 9.2.2.2.1validoptionalEnsure that the IUT in the ECT LinkId Assigned state (invoked via CR2) and with CR3 in call stateU10 (Idle) and CR2 in call state U10 (Idle) and CR1 in call state U04 (Held) to request ECT using explicitlinkage procedure,sends a FACILITY message with CR1 containing a Facility information element with anExplicitEctExecute invoke component including the previously received LinkId value and enters theECT Explicit Request state and remains in the same call states.Selection:IUT supports transfer with one answered and one alerting call. PICS: MC 3.SIST ETS 300 369-3:1998



Page 15ETS 300 369-3: October 1996ECT_U03_011subclause 9.2.2.2.1validoptionalEnsure that the IUT in the ECT LinkId Assigned state (invoked via CR2) and with CR3 in call stateU10 (Idle) and CR2 in call state U04 (Idle) and CR1 in call state U10 (Held) to request ECT using explicitlinkage procedure,sends a FACILITY message with CR1 containing a Facility information element with anExplicitEctExecute invoke component including the previously received LinkId value and enters theECT Explicit Request state and remains in the same call states.Selection:IUT supports transfer with one answered and one alerting call. PICS: MC 3.ECT_U03_012subclause 9.2.2.2.2validmandatoryEnsure that the IUT in the ECT Explicit Request state (invoked via CR1 and LinkId assigned via CR2) andwith CR3 in call state U10 (Idle) and CR2 in call state U10 (Idle) and CR1 in call state U10 (Held) receivinga FACILITY message with CR1 containing a Facility information element with an ExplicitEctExecute returnerror component,enters the ECT Idle state and remains in the same call states.ECT_U03_013subclause 9.2.2.2.2validoptionalEnsure that the IUT in the ECT Explicit Request state (invoked via CR1 and LinkId assigned via CR2) andwith CR3 in call state U10 (Idle) and CR2 in call state U10 (Idle) and CR1 in call state U04 (Held) receivinga FACILITY message with CR1 containing a Facility information element with an ExplicitEctExecute returnerror component,enters the ECT Idle state and remains in the same call states.Selection:IUT supports transfer with one answered and one alerting call. PICS: MC 3.ECT_U03_014subclause 9.2.2.2.2validoptionalEnsure that the IUT in the ECT Explicit Request state (invoked via CR1 and LinkId assigned via CR2) andwith CR3 in call state U10 (Idle) and CR2 in call state U04 (Idle) and CR1 in call state U10 (Held) receivinga FACILITY message with CR1 containing a Facility information element with an ExplicitEctExecute returnerror component,enters the ECT Idle state and remains in the same call states.Selection:IUT supports transfer with one answered and one alerting call. PICS: MC 3.ECT_U03_015subclause 9.2.2.2.2validmandatoryEnsure that the IUT in the ECT Explicit Request state (invoked via CR1 and LinkId assigned via CR2) andwith CR3 in call state U10 (Idle) and CR2 in call state U10 (Idle) and CR1 in call state U10 (Held) receivinga FACILITY message with CR1 containing a Facility information element with a reject component,enters the ECT Idle state and remains in the same call states.ECT_U03_016subclause 9.2.2.2.2validoptionalEnsure that the IUT in the ECT Explicit Request state (invoked via CR1 and LinkId assigned via CR2) andwith CR3 in call state U10 (Idle) and CR2 in call state U10 (Idle) and CR1 in call state U04 (Held) receivinga FACILITY message with CR1 containing a Facility information element with a reject component,enters the ECT Idle state and remains in the same call states.Selection:IUT supports transfer with one answered and one alerting call. PICS: MC 3.ECT_U03_017subclause 9.2.2.2.2validoptionalEnsure that the IUT in the ECT Explicit Request state (invoked via CR1 and LinkId assigned via CR2) andwith CR3 in call state U10 (Idle) and CR2 in call state U04 (Idle) an
...

SLOVENSKI STANDARD
SIST ETS 300 369-3:1998
01-junij-1998
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'1'RSROQLOQDVWRULWHY
QHGYRXPQDSUHGDMDNOLFD(&73URWRNROGLJLWDOQHQDURþQLãNHVLJQDOL]DFLMHãW
'66GHO=JUDGEDSUHVNXãDOQHJDQL]DLQQDPHQSUHVNXãDQMD766 73
6SHFLILNDFLMD]DXSRUDEQLND
Integrated Services Digital Network (ISDN); Explicit Call Transfer (ECT) supplementary
service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: Test Suite
Structure and Test Purposes (TSS&TP) specification for the user
Ta slovenski standard je istoveten z: ETS 300 369-3 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
SIST ETS 300 369-3:1998 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ETS 300 369-3:1998

---------------------- Page: 2 ----------------------

SIST ETS 300 369-3:1998
EUROPEAN ETS 300 369-3
TELECOMMUNICATION October 1996
STANDARD
Source: ETSI TC-SPS Reference: DE/SPS-05061-Q1-3
ICS: 33.080
Key words: ISDN, DSS1, supplementary service, ECT, testing, TSS&TP, user
Integrated Services Digital Network (ISDN);
Explicit Call Transfer (ECT) supplementary service;
Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 3: Test Suite Structure and Test Purposes (TSS&TP)
specification for the user
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail]
Tel.: [phone] - Fax: [phone]
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1996. All rights reserved.

---------------------- Page: 3 ----------------------

SIST ETS 300 369-3:1998
Page 2
ETS 300 369-3: October 1996
Whilst 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.

---------------------- Page: 4 ----------------------

SIST ETS 300 369-3:1998
Page 3
ETS 300 369-3: October 1996
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions.8
3.1 Definitions related to conformance testing.8
3.2 Definitions related to ETS 300 369-1.8
4 Abbreviations.9
5 Test Suite Structure (TSS) .9
6 Test Purposes (TP).10
6.1 Introduction .10
6.1.1 TP naming convention.10
6.1.2 Source of TP definition.10
6.1.3 TP structure.10
6.1.4 Test strategy.11
6.2 User TPs for ECT .12
6.2.1 User (S/T).12
6.2.1.1 Served user .12
6.2.1.1.1 Implicit linkage procedures .12
6.2.1.1.1.1 Valid.12
6.2.1.1.1.2 Invalid.13
6.2.1.1.2 Explicit linkage procedures .13
6.2.1.1.2.1 Valid.13
6.2.1.1.2.2 Invalid.15
6.2.1.1.3 Confirmation of call transfer.16
6.2.1.1.3.1 Valid.17
6.2.1.1.3.2 Invalid.18
6.2.1.2 Remote user .19
6.2.2 User (T) .19
6.2.2.1 Served user connected.19
6.2.2.2 Remote user connected .21
7 Compliance .21
8 Requirements for a comprehensive testing service .22
History.23

---------------------- Page: 5 ----------------------

SIST ETS 300 369-3:1998
Page 4
ETS 300 369-3: October 1996
Blank page

---------------------- Page: 6 ----------------------

SIST ETS 300 369-3:1998
Page 5
ETS 300 369-3: October 1996
Foreword
This European Telecommunication Standard (ETS) has been produced by the Signalling Protocols and
Switching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).
This ETS is part 3 of a multi-part standard covering the Digital Subscriber Signalling System No. one
(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) Explicit Call Transfer
(ECT) supplementary service, 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 the user";
Part 4: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for
Testing (PIXIT) proforma specification for the user";
Part 5: "TSS&TP specification for the network";
Part 6: "ATS and partial PIXIT proforma specification for the network".
Transposition dates
Date of adoption of this ETS: 4 October 1996
Date of latest announcement of this ETS (doa): 31 January 1997
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 July 1997
Date of withdrawal of any conflicting National Standard (dow): 31 July 1997

---------------------- Page: 7 ----------------------

SIST ETS 300 369-3:1998
Page 6
ETS 300 369-3: October 1996
Blank page

---------------------- Page: 8 ----------------------

SIST ETS 300 369-3:1998
Page 7
ETS 300 369-3: October 1996
1 Scope
This third part of ETS 300 369 specifies the Test Suite Structure and Test Purposes (TSS&TP) for the
User side of the T reference point or coincident S and T reference point (as defined in ITU-T
Recommendation I.411 [7]) of implementations conforming to the stage three standard for the Explicit Call
Transfer (ECT) supplementary service for the pan-European Integrated Services Digital Network (ISDN)
by means of the Digital Subscriber Signalling System No. one (DSS1) protocol, ETS 300 369-1 [1].
A further part of this ETS specifies the Abstract Test Suite (ATS) and partial Protocol Implementation
eXtra Information for Testing (PIXIT) proforma based on this ETS. Other parts specify the TSS&TP and
the ATS and partial PIXIT proforma for the Network side of the T reference point or coincident S and
T reference point of implementations conforming to ETS 300 369-1 [1].
2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] ETS 300 369-1 (1995): "Integrated Services Digital Network (ISDN); Explicit Call
Transfer (ECT) supplementary service; Digital Subscriber Signalling System No.
one (DSS1) protocol; Part 1: Protocol specification".
[2] ETS 300 369-2 (1996): "Integrated Services Digital Network (ISDN); Explicit Call
Transfer (ECT) supplementary service; Digital Subscriber Signalling System No.
one (DSS1) protocol; Part 2: Protocol Implementation Conformance Statement
(PICS) proforma specification".
[3] ISO/IEC 9646-1: "Information Technology - OSI Conformance Testing
Methodology and Framework; Part 1: General Concepts".
[4] ISO/IEC 9646-2: "Information Technology - OSI Conformance Testing
Methodology and Framework; Part 2: Abstract Test Suite specification".
[5] ISO/IEC 9646-3: "Information Technology - OSI Conformance Testing
Methodology and Framework; Part 3: The Tree and Tabular Combined
Notation".
[6] ETS 300 196-1 (1993): "Integrated Services Digital Network (ISDN); Generic
functional protocol for the support of supplementary services; Digital Subscriber
Signalling System No. one (DSS1) protocol; Part 1: Protocol specification".
[7] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces -
Reference configurations".
[8] ETS 300 102-1: "Integrated Services Digital Network (ISDN);
User-network interface layer 3; Specifications for basic call control".
[9] ITU-T Recommendation I.112 (1993): "Vocabulary and terms for ISDNs".
[10] CCITT Recommendation E.164 (1991): "Numbering plan for the ISDN era".
[11] ITU-T Recommendation I.210 (1993): "Principles of the telecommunication
services supported by an ISDN and the means to describe them".

---------------------- Page: 9 ----------------------

SIST ETS 300 369-3:1998
Page 8
ETS 300 369-3: October 1996
3 Definitions
For the purposes of this ETS, the following definitions apply:
3.1 Definitions related to conformance testing
abstract test case: Refer to ISO/IEC 9646-1 [3].
Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [3].
Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [3].
implicit send event: Refer to ISO/IEC 9646-3 [5].
lower tester: Refer to ISO/IEC 9646-1 [3].
point of control and observation: Refer to ISO/IEC 9646-1 [3].
Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [3].
PICS proforma: Refer to ISO/IEC 9646-1 [3].
Protocol Implementation eXtra Information for Testing (PIXIT): Refer to ISO/IEC 9646-1 [3].
PIXIT proforma: Refer to ISO/IEC 9646-1 [3].
system under test: Refer to ISO/IEC 9646-1 [3].
Test Purpose (TP): Refer to ISO/IEC 9646-1 [3].
3.2 Definitions related to ETS 300 369-1
Call Held auxiliary state: See ETS 300 196-1 [6], subclause 7.1.2.
Call Reference (CR): See ETS 300 102-1 [8], subclause 4.3.
component: See ETS 300 196-1 [6], subclause 11.2.2.1.
Idle auxiliary state: See ETS 300 196-1 [6], subclause 7.1.2.
Integrated Services Digital Network (ISDN): See ITU-T Recommendation I.112 [9], definition 308.
ISDN number: A number conforming to the numbering and structure specified in
CCITT Recommendation E.164 [10].
invoke component: See ETS 300 196-1 [6], subclause 11.2.2.1.
return error component: See ETS 300 196-1 [6], subclause 11.2.2.1.
return result component: See ETS 300 196-1 [6], subclause 11.2.2.1.
served user: The served user is the user who invokes the ECT supplementary service.
service; telecommunication service: See ITU-T Recommendation I.112 [9], definition 201.
supplementary service: See ITU-T Recommendation I.210 [11], subclause 2.4.
user: The DSS1 protocol entity at the User side of the user-network interface where a T reference point or
coincident S and T reference point applies.

---------------------- Page: 10 ----------------------

SIST ETS 300 369-3:1998
Page 9
ETS 300 369-3: October 1996
user (S/T): The DSS1 protocol entity at the User side of the user-network interface where a coincident
S and T reference point applies.
user (T): The DSS1 protocol entity at the User side of the user-network interface where a T reference
point applies (User is the Private ISDN).
4 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
(Held) Call Held auxiliary state
(Idle) Idle auxiliary state
ATM Abstract Test Method
ATS Abstract Test Suite
CR Call Reference
CR1 CR one (held or idle)
CR2 CR two (held or idle)
CR3 CR three (held, with CR1 and CR2 idle)
DSS1 Digital Subscriber Signalling System No. one
ECT Explicit Call Transfer
ISDN Integrated Services Digital Network
IUT Implementation Under Test
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
TP Test Purpose
TSS Test Suite Structure
U04 Call Delivered call state
U10 Active call state
U19 Release Request call state
5 Test Suite Structure (TSS)
ECT - User
User (S/T) User (T)
Served user Remote user Served user connected Remote user connected
(07) (08) (09)
Implicit linkage Explicit linkage Confirmation of
procedures procedures call transfer
Valid Invalid Valid Invalid Valid Invalid
(01) (02) (03) (04) (05) (06)
NOTE: Numbers in brackets represent group numbers and are used in TP identifiers.
Figure 1: Test suite structure

---------------------- Page: 11 ----------------------

SIST ETS 300 369-3:1998
Page 10
ETS 300 369-3: October 1996
6 Test Purposes (TP)
6.1 Introduction
For each test requirement a TP is defined.
6.1.1 TP naming convention
TPs 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 the
user (see table 1).
Table 1: TP identifier naming convention scheme
Identifier: __
= supplementary service: e.g. "ECT"
= type of IUT: U User
N Network
= group 2 digit field representing group reference according to TSS
= sequential number (001-999)
6.1.2 Source of TP definition
The TPs are based on ETS 300 369-1 [1].
6.1.3 TP structure
Each TP has been written in a manner which is consistent with all other TPs. The intention of this is to
make the TPs more readable and checkable. A particular structure has been used and this is illustrated in
table 2. This table should be read in conjunction with any TP, i.e. use a TP as an example to fully
understand the table.

---------------------- Page: 12 ----------------------

SIST ETS 300 369-3:1998
Page 11
ETS 300 369-3: October 1996
Table 2: Structure of a single TP
TP part Text Example
Header tab see table 1
tab subclause 0.0.0
tab valid, invalid, inopportune
CR. mandatory, optional, conditional
Stimulus Ensure that the IUT in the
ECT Implicit Request state
and with CR1 in () U10 (Idle), U10 (Held), etc.
and with CR2 in () "
and with CR3 in () "
see below for message structure receiving a XXXX message
or to request a .
Reaction sends, saves, does, etc.
using en-bloc sending, .
if the action is sending
  see below for message structure
, etc.
and enters
and/or and remains in the same call state(s)
or and enters call state with CR
SETUP, FACILITY, CONNECT, .
Message
message containing a
structure
a) Bearer capability, Facility, .
information element with
b) a
encoded as or including
and back to a or b,
Note: Text in italics will not appear in TPs and text between <> is filled in for each TP and may
differ from one TP to the next.
6.1.4 Test strategy
As the base standard ETS 300 369-1 [1] contained no explicit requirements for testing, the TPs were
generated as a result of an analysis of the base standard and the PICS specification, ETS 300 369-2 [2].
The criteria applied included the following:
- only the requirements from the point of view of the T or coincident S and T reference point are
considered;
- whether or not a test case can be built from the TP is not considered.

---------------------- Page: 13 ----------------------

SIST ETS 300 369-3:1998
Page 12
ETS 300 369-3: October 1996
6.2 User TPs for ECT
6.2.1 User (S/T)
Selection: IUT supports coincident S and T reference point procedures. PICS: R 3.1.
6.2.1.1 Served user
Selection: IUT can handle two calls.
Selection: IUT supports Call hold supplementary service.
6.2.1.1.1 Implicit linkage procedures
6.2.1.1.1.1 Valid
ECT_U01_001 subclause 9.2.1.1 valid mandatory
Ensure that the IUT in the ECT Idle state, with CR1 in call state U10 (Held) and CR2 in call state
U10 (Idle) to request ECT using implicit linkage procedure,
sends a FACILITY message with CR1 containing a Facility information element with an EctExecute
invoke component and enters the ECT Implicit Request state and remains in the same call states.
ECT_U01_002 subclause 9.2.1.1 valid optional
Ensure that the IUT in the ECT Idle state, with CR1 in call state U10 (Held) and CR2 in call state
U04 (Idle) to request ECT using implicit linkage procedure,
sends a FACILITY message with CR1 containing a Facility information element with an EctExecute
invoke component and enters the ECT Implicit Request state and remains in the same call states.
Selection: IUT supports transfer with one answered and one alerting call. PICS: MC 3.
ECT_U01_003 subclause 9.2.1.1 valid optional
Ensure that the IUT in the ECT Idle state, with CR2 in call state U10 (Idle) and CR1 in call state
U04 (Held) to request ECT using implicit linkage procedure,
sends a FACILITY message with CR1 containing a Facility information element with an EctExecute
invoke component and enters the ECT Implicit Request state and remains in the same call states.
Selection: IUT supports transfer with one answered and one alerting call. PICS: MC 3.
ECT_U01_004 subclause 9.2.1.2 valid mandatory
Ensure that the IUT in the ECT Implicit Request state, with CR1 in call state U10 (Held) and CR2 in call
state U10 (Idle) receiving a valid FACILITY message with CR1 containing a Facility information element
with an EctExecute return error component,
enters the ECT Idle state and remains in the same call states.
ECT_U01_005 subclause 9.2.1.2 valid optional
Ensure that the IUT in the ECT Implicit Request state, with CR1 in call state U10 (Held) and CR2 in call
state U04 (Idle) receiving a valid FACILITY message with CR1 containing a Facility information element
with an EctExecute return error component,
enters the ECT Idle state and remains in the same call states.
Selection: IUT supports transfer with one answered and one alerting call. PICS: MC 3.
ECT_U01_006 subclause 9.2.1.2 valid optional
Ensure that the IUT in the ECT Implicit Request state, with CR2 in call state U10 (Idle) and CR1 in call
state U04 (Held) receiving a valid FACILITY message with CR1 containing a Facility information element
with an EctExecute return error component,
enters the ECT Idle state and remains in the same call states.
Selection: IUT supports transfer with one answered and one alerting call. PICS: MC 3.
ECT_U01_007 subclause 9.2.1.2 valid mandatory
Ensure that the IUT in the ECT Implicit Request state, with CR1 in call state U10 (Held) and CR2 in call
state U10 (Idle) receiving a valid FACILITY message with CR1 containing a Facility information element
with a reject component,
enters the ECT Idle state and remains in the same call states.

---------------------- Page: 14 ----------------------

SIST ETS 300 369-3:1998
Page 13
ETS 300 369-3: October 1996
ECT_U01_008 subclause 9.2.1.2 valid optional
Ensure that the IUT in the ECT Implicit Request state, with CR1 in call state U10 (Held) and CR2 in call
state U04 (Idle) receiving a valid FACILITY message with CR1 containing a Facility information element
with a reject component,
enters the ECT Idle state and remains in the same call states.
Selection: IUT supports transfer with one answered and one alerting call. PICS: MC 3.
ECT_U01_009 subclause 9.2.1.2 valid optional
Ensure that the IUT in the ECT Implicit Request state, with CR2 in call state U10 (Idle) and CR1 in call
state U04 (Held) receiving a valid FACILITY message with CR1 containing a Facility information element
with a reject component,
enters the ECT Idle state and remains in the same call states.
Selection: IUT supports transfer with one answered and one alerting call. PICS: MC 3.
6.2.1.1.1.2 Invalid
ECT_U02_001 subclause 7.2 invalid mandatory
Ensure that the IUT in the ECT Implicit Request state, with CR1 in call state U10 (Held) and CR2 in call
state U10 (Idle) receiving a valid FACILITY message with CR1 containing a Facility information element
with an invalid EctExecute return error component,
sends a FACILITY message containing a Facility information element with a reject component and
remains in the same auxiliary and call states.
ECT_U02_002 subclause 7.2 invalid optional
Ensure that the IUT in the ECT Implicit Request state, with CR1 in call state U10 (Held) and CR2 in call
state U04 (Idle) receiving a valid FACILITY message with CR1 containing a Facility information element
with an invalid EctExecute return error component,
sends a FACILITY message containing a Facility information element with a reject component and
remains in the same auxiliary and call states.
Selection: IUT supports transfer with one answered and one alerting call. PICS: MC 3.
ECT_U02_003 subclause 7.2 invalid optional
Ensure that the IUT in the ECT Implicit Request state, with CR2 in call state U10 (Idle) and CR1 in call
state U04 (Held) receiving a valid FACILITY message with CR1 containing a Facility information element
with an invalid EctExecute return error component,
sends a FACILITY message containing a Facility information element with a reject component and
remains in the same auxiliary and call states.
Selection: IUT supports transfer with one answered and one alerting call. PICS: MC 3.
6.2.1.1.2 Explicit linkage procedures
Selection: IUT supports explicit linkage procedures. PICS: MC 2.
6.2.1.1.2.1 Valid
ECT_U03_001 subclause 9.2.2.1.1 valid mandatory
Ensure that the IUT in the ECT Idle state and with CR3 in call state U10 (Idle) and CR2 in call state
U10 (Idle) and CR1 in call state U10 (Held) in order to initiate the explicit linkage procedure,
sends a FACILITY message with CR2 containing a Facility information element with an
EctLinkIdRequest invoke component and enters ECT LinkId Request state and remains in the
same call states.
ECT_U03_002 subclause 9.2.2.1.1 valid optional
Ensure that the IUT in the ECT Idle state and with CR3 in call state U10 (Idle) and CR2 in call state
U04 (Idle) and CR1 in call state U10 (Held) in order to initiate the explicit linkage procedure,
sends a FACILITY message with CR2 containing a Facility information element with an
EctLinkIdRequest invoke component and enters ECT LinkId Request state and remains in the
same call states.
Selection: IUT supports transfer with one answered and one alerting call. PICS: MC 3.

---------------------- Page: 15 ----------------------

SIST ETS 300 369-3:1998
Page 14
ETS 300 369-3: October 1996
ECT_U03_003 subclause 9.2.2.1.1 valid mandatory
Ensure that the IUT in the ECT LinkId Request state (invoked via CR2) and with CR3 in call state
U10 (Idle) and CR2 in call state U10 (Idle) and CR1 in call state U10 (Held) receiving a valid FACILITY
message with CR2 containing a Facility information element with a LinkId value in an EctLinkIdRequest
return result component,
enters the ECT LinkId Assigned state and remains in the same call states.
ECT_U03_004 subclause 9.2.2.1.1 valid optional
Ensure that the IUT in the ECT LinkId Request state (invoked via CR2) and with CR3 in call state
U10 (Idle) and CR2 in call state U04 (Idle) and CR1 in call state U10 (Held) receiving a valid FACILITY
message with CR2 containing a Facility information element with a LinkId value in an EctLinkIdRequest
return result component,
enters the ECT Link Id Assigned state and remains in the same call states.
Selection: IUT supports transfer with one answered and one alerting call. PICS: MC 3.
ECT_U03_005 subclause 9.2.2.1.2 valid mandatory
Ensure that the IUT in the ECT LinkId Request state (invoked via CR2) and with CR3 in call state
U10 (Idle) and CR2 in call state U10 (Idle) and CR1 in call state U10 (Held) receiving a valid FACILITY
message with CR2 containing a Facility information element with an EctLinkIdRequest return error
component,
enters the ECT Idle state and remains in the same call states.
ECT_U03_006 subclause 9.2.2.1.2 valid optional
Ensure that the IUT in the ECT LinkId Request state (invoked via CR2) and with CR3 in call state
U10 (Idle) and CR2 in call state U04 (Idle) and CR1 in call state U10 (Held) receiving a valid FACILITY
message with CR2 containing a Facility information element with an EctLinkIdRequest return error
component,
enters the ECT Idle state and remains in the same call states.
Selection: IUT supports transfer with one answered and one alerting call. PICS: MC 3.
ECT_U03_007 subclause 9.2.2.1.2 valid mandatory
Ensure that the IUT in the ECT LinkId Request state (invoked via CR2) and with CR3 in call state
U10 (Idle) and CR2 in call state U10 (Idle) and CR1 in call state U10 (Held) receiving a valid FACILITY
message with CR2 containing a Facility information element with a reject component,
enters the ECT Idle state and remains in the same call states.
ECT_U03_008 subclause 9.2.2.1.2 valid optional
Ensure that the IUT in the ECT LinkId Request state (invoked via CR2) and with CR3 in call state
U10 (Idle) and CR2 in call state U04 (Idle) and CR1 in call state U10 (Held) receiving a valid FACILITY
message with CR2 containing a Facility information element with a reject component,
enters the ECT Idle state and remains in the same call states.
Selection: IUT supports transfer with one answered and one alerting call. PICS: MC 3.
ECT_U03_009 subclause 9.2.2.2.1 valid mandatory
Ensure that the IUT in the ECT LinkId Assigned state (invoked via CR2) and with CR3 in call state
U10 (Idle) and CR2 in call state U10 (Idle) and CR1 in call state U10 (Held) to request ECT using explicit
linkage procedure,
sends a FACILITY message with CR1 containing a Facility information element with an
ExplicitEctExecute invoke component including the previously received LinkId value and enters the
ECT Explicit Request state and remains in the same call states.
ECT_U03_010 subclause 9.2.2.2.1 valid optional
Ensure that the IUT in the ECT LinkId Assigned state (invoked via CR2) and with CR3 in call state
U10 (Idle) and CR2 in call state U10 (Idle) and CR1 in call state U04 (Held) to request ECT using explicit
linkage procedure,
sends a FACILITY message with CR1 containing a Facility information element with an
ExplicitEctExecute invoke component including the previously received LinkId value and enters the
ECT Explicit Request state and remains in the same call states.
Selection: IUT supports transfer with one answered and one alerting call. PICS: MC 3.

---------------------- Page: 16 ----------------------

SIST ETS 300 369-3:1998
Page 15
ETS 300 369-3: October 1996
ECT_U03_011 subclause 9.2.2.2.1 valid optional
Ensure that the IUT in the ECT LinkId Assigned state (invoked via CR2) and with CR3 in call state
U10 (Idle) and CR2 in call state U04 (Idle) and CR1 in call state U10 (Held) to request ECT using explicit
linkage procedure,
sends a FACILITY message with CR1 containing a Facility information element with an
ExplicitEctExecute invoke component including the previously received LinkId value and enters the
ECT Explicit Request state and remains in the same call states.
Selection: IUT supports transfer with one answered and one alerting call. PICS: MC 3.
ECT_U03_012 subclause 9.2.2.2.2 valid mandatory
Ensure that the IUT in the ECT Explicit Request state (invoked via CR1 and LinkId assigned via CR2) and
with CR3 in call state U10 (Idle) and CR2 in call state U10 (Idle) and CR1 in call state U10 (Held) receiving
a FACILITY message with CR1 containing a Facility information element with an ExplicitEctExecute return
error component,
enters the ECT Idle state and remains in the same call states.
ECT_U03_013 subclause 9.2.2.2.2 valid optional
Ensure that the IUT in the ECT Explicit Request state (invoked via CR1 and LinkId assigned via CR2) and
with CR3 in call state U10 (Idle) and CR2 in call state U10 (Idle) and CR1 in call state U04 (Hel
...