SIST ETS 300 141-3:1997

Integrated Services Digital Network (ISDN); Call Hold (HOLD) 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: zadržanje klica (HOLD) - 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: 30-Nov-1997
• 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-Dec-1997
• Due Date: 01-Dec-1997
• Completion Date: 01-Dec-1997
• Ref Project: ETSI ETS 300 141-3 ed.1 (1996-10) - Integrated Services Digital Network (ISDN); Call Hold (HOLD) 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.XSRUDEQLNDIntegrated Services Digital Network (ISDN); Call Hold (HOLD) 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 141-3 Edition 13SIST ETS 300 141-3:1997en01-RNWREHU-19973SIST ETS 300 141-3:1997SLOVENSKI
STANDARD



SIST ETS 300 141-3:1997



EUROPEANETS 300 141-3TELECOMMUNICATIONOctober 1996STANDARDSource: ETSI TC-SPSReference: DE/SPS-05061-S-3ICS:33.080Key words:ISDN, DSS1, supplementary service, HOLD, testing, TSS&TP, userIntegrated Services Digital Network (ISDN);Call Hold (HOLD) 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 141-3:1997



Page 2ETS 300 141-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 141-3:1997



Page 3ETS 300 141-3: October 1996ContentsForeword.51Scope.72Normative references.73Definitions.83.1Definitions related to conformance testing.83.2Definitions related to ETS 300 141-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 HOLD.126.2.1Served user (S/T).126.2.1.1Normal procedures.126.2.1.1.1Hold.126.2.1.1.2Retrieve.136.2.1.2Channel reservation function.146.2.1.2.1Request.146.2.1.2.2Manage.156.2.1.2.3Cancel.156.2.1.2.4Receipt of return result.176.2.1.3Timers.186.2.2Remote user - receipt of notifications.186.2.3User (T).197Compliance.208Requirements for a comprehensive testing service.20History.21SIST ETS 300 141-3:1997



Page 4ETS 300 141-3: October 1996Blank pageSIST ETS 300 141-3:1997



Page 5ETS 300 141-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) Call Hold (HOLD)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 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 141-3:1997



Page 6ETS 300 141-3: October 1996Blank pageSIST ETS 300 141-3:1997



Page 7ETS 300 141-3: October 19961ScopeThis third part of ETS 300 141 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 Call Hold(HOLD) supplementary service for the pan-European Integrated Services Digital Network (ISDN) bymeans of the Digital Subscriber Signalling System No. one (DSS1) protocol, ETS 300 141-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 141-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 141-1 (1993): "Integrated Services Digital Network (ISDN);Call Hold (HOLD) supplementary service ; Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Part 1: Protocol specification".[2]ETS 300 141-2: "Integrated Services Digital Network (ISDN); Call Hold (HOLD)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-networkinterface 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".[12]ETS 300 196-2 (1996): "Integrated Services Digital Network (ISDN); Genericfunctional protocol for the support of supplementary services; Digital SubscriberSignalling System No. one (DSS1) protocol; Part 2: Protocol ImplementationConformance Statement (PICS) proforma specification".SIST ETS 300 141-3:1997



Page 8ETS 300 141-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 141-1Call Held auxiliary state: See ETS 300 196-1 [6], subclause 7.1.2.component: See ETS 300 196-1 [6], subclause 11.2.2.1.Hold Requested auxiliary state: See ETS 300 196-1 [6], subclause 7.1.2.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 CCITTRecommendation E.164 [10].invoke component: See ETS 300 196-1 [6], subclause 11.2.2.1.Retrieve Requested auxiliary state: See ETS 300 196-1 [6], subclause 7.1.2.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 HOLD 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.SIST ETS 300 141-3:1997



Page 9ETS 300 141-3: October 1996user: 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 (commonly referred to as a Private ISDN).4AbbreviationsFor the purposes of this ETS, the following abbreviations apply:ATMAbstract Test MethodATSAbstract Test SuiteDSS1Digital Subscriber Signalling System No. oneHOLDCall HoldISDNIntegrated Services Digital NetworkIUTImplementation under testPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingTPTest PurposeTSSTest Suite StructureU04Call Delivered call stateU07Call Received call stateU10Active call state5Test Suite Structure (TSS)HOLD - UserServed user (S/T)Remote user -Served user (T)receipt of notifications(09)(08)Normal proceduresChannel reservationfunctionTimers(07)Hold(01)Retrieve(02)Request(03)Manage(04)Cancel(05)Receipt of returnresult(06)NOTE:Numbers in brackets represent group numbers and are used in TP identifiers.Figure 1: Test suite structureSIST ETS 300 141-3:1997



Page 10ETS 300 141-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. "HOLD"=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 141-1 [1], clauses 9, 10 and 14.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 141-3:1997



Page 11ETS 300 141-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 theU00, U10, etc.and Hold Requested, . 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 remains in the same stateor and enters state Messagestructuremessage 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 141-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 141-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 141-3:1997



Page 12ETS 300 141-3: October 19966.2User TPs for HOLDAll PICS items referred to in this subclause are as specified in ETS 300 141-2 [2] unless indicatedotherwise by another numbered reference.6.2.1Served user (S/T)Selection:IUT supports coincident S and T reference point procedures. PICS: R 3.1.6.2.1.1Normal procedures6.2.1.1.1HoldHOLD_U01_001subclause 9.1.1validmandatoryEnsure that the IUT in the Active call state U10 and Idle auxiliary state to initiate the HOLD service,sends a HOLD message and enters the Hold Requested auxiliary state.HOLD_U01_002subclause 9.1.1validoptionalEnsure that the IUT in the Call Delivered call state U04 and Idle auxiliary state to initiate the HOLDservice,sends a HOLD message and enters the Hold Requested auxiliary state.Selection:IUT supports holding a call in call state U04. PICS: MC 1.2.HOLD_U01_003subclause 9.1.1validmandatoryEnsure that the IUT in the Active call state U10 and Hold Requested auxiliary state receiving a HOLDACKNOWLEDGE message,releases the B-channel, remains in the Active call state U10 and enters the Call Held auxiliary state.HOLD_U01_004subclause 9.1.1invalidmandatoryEnsure that the IUT in the Active call state U10 and Hold Requested auxiliary state, receiving an HOLDACKNOWLEDGE message with an optional information element with content error,sends no message or sends a STATUS message cause #100 "invalid information elementcontents" and enters the Call Held auxiliary state.HOLD_U01_005subclause 9.1.1validoptionalEnsure that the IUT in the Call Delivered call state U04 and Hold Requested auxiliary state, receiving aHOLD ACKNOWLEDGE message,enters the Call Held auxiliary state.Selection:IUT supports holding a call in call state U04. PICS: MC 1.2.HOLD_U01_006subclause 9.1.1invalidoptionalEnsure that the IUT in the Call Delivered call state U04 and Hold Requested auxiliary state, receiving aHOLD ACKNOWLEDGE message with an optional information element with content error,sends no message or sends a STATUS message cause #100 "invalid information elementcontents" and enters the Call Held auxiliary state.Selection:IUT supports holding a call in call state U04. PICS: MC 1.2.HOLD_U01_007subclause 9.1.2validmandatoryEnsure that the IUT in the Active call state U10 and Hold Requested auxiliary state, receiving a HOLDREJECT message,does not release the B-channel, remains in the Active call state U10 and enters the Idle auxiliarystate.HOLD_U01_008subclause 9.1.2invalidmandatoryEnsure that the IUT in the Active call state U10 and Hold Requested auxiliary state, receiving a HOLDREJECT message with an optional information element with content error,sends no message or sends a STATUS message cause #100 "invalid information elementcontents" and enters the Idle auxiliary state.SIST ETS 300 141-3:1997



Page 13ETS 300 141-3: October 1996HOLD_U01_009subclause 9.1.2invalidmandatoryEnsure that the IUT in the Active call state U10 and Hold Requested auxiliary state, receiving a HOLDREJECT message with a mandatory information element with content error,sends a STATUS message cause #100 "invalid information element contents" and remains in thesame state.HOLD_U01_010subclause 9.1.2invalidoptionalEnsure that the IUT in the Call Delivered call state U04 and Hold Requested auxiliary state, receiving aHOLD REJECT message,enters the Idle auxiliary state.Selection:IUT supports holding a call in call state U04. PICS: MC 1.2.HOLD_U01_011subclause 9.1.2invalidoptionalEnsure that the IUT in the Call Delivered call state U04 and Hold Requested auxiliary state, receiving aHOLD REJECT message with an optional information element with content error,sends no message or sends a STATUS message cause #100 "invalid information elementcontents" and enters the Idle auxiliary state.Selection:IUT supports holding a call in call state U04. PICS: MC 1.2.HOLD_U01_012subclause 9.1.2invalidoptionalEnsure that the IUT in the Call Delivered call state U04 and Hold Requested auxiliary state, receiving aHOLD REJECT message with a mandatory information element with content error,sends a STATUS message cause #100 "invalid information element contents" and remains in thesame state.Selection:IUT supports holding a call in call state U04. PICS: MC 1.2.6.2.1.1.2RetrieveHOLD_U02_001subclause 9.3.1validmandatoryEnsure that the IUT in the Active call state U10 and Call Held auxiliary state to initiate the Retrievefunction,sends a RETRIEVE message and enters the Retrieve Requested auxiliary state.HOLD_U02_002subclause 9.3.1validoptionalEnsure that the IUT in the Call Delivered call state U04 and Call Held auxiliary state to initiate the Retrievefunction,sends a RETRIEVE message and enters the Retrieve Requested auxiliary state.Selection:IUT supports holding a call in call state U04. PICS: MC 1.2.HOLD_U02_003subclause 9.3.1validmandatoryEnsure that the IUT in the Active call state U10 and Retrieve Requested auxiliary state receiving aRETRIEVE ACKNOWLEDGE message,connects to the B channel and enters the Idle auxiliary state.HOLD_U02_004subclause 9.3.1invalidmandatoryEnsure that the IUT in the Active call state U10 and Retrieve Requested auxiliary state receiving aRETRIEVE ACKNOWLEDGE message with an optional information element with content error,sends no message or sends a STATUS message cause #100 "invalid information elementcontents" and enters the Idle auxiliary state.HOLD_U02_005subclause 9.3.1validoptionalEnsure that the IUT in the Call Delivered call state U04 and Retrieve Requested auxiliary state, receiving aRETRIEVE ACKNOWLEDGE
...

SLOVENSKI STANDARD
SIST ETS 300 141-3:1997
01-december-1997
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'1'RSROQLOQDVWRULWHY]DGUåDQMH
NOLFD+2/'3URWRNROGLJLWDOQHQDURþQLãNHVLJQDOL]DFLMHãW'66GHO
=JUDGEDSUHVNXãDOQHJDQL]DLQQDPHQSUHVNXãDQMD766 736SHFLILNDFLMD]D
XSRUDEQLND
Integrated Services Digital Network (ISDN); Call Hold (HOLD) 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 141-3 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
SIST ETS 300 141-3:1997 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

SIST ETS 300 141-3:1997

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

SIST ETS 300 141-3:1997
EUROPEAN ETS 300 141-3
TELECOMMUNICATION October 1996
STANDARD
Source: ETSI TC-SPS Reference: DE/SPS-05061-S-3
ICS: 33.080
Key words: ISDN, DSS1, supplementary service, HOLD, testing, TSS&TP, user
Integrated Services Digital Network (ISDN);
Call Hold (HOLD) 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 141-3:1997
Page 2
ETS 300 141-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 141-3:1997
Page 3
ETS 300 141-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 141-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 HOLD.12
6.2.1 Served user (S/T).12
6.2.1.1 Normal procedures.12
6.2.1.1.1 Hold.12
6.2.1.1.2 Retrieve.13
6.2.1.2 Channel reservation function.14
6.2.1.2.1 Request.14
6.2.1.2.2 Manage.15
6.2.1.2.3 Cancel.15
6.2.1.2.4 Receipt of return result .17
6.2.1.3 Timers.18
6.2.2 Remote user - receipt of notifications.18
6.2.3 User (T) .19
7 Compliance .20
8 Requirements for a comprehensive testing service .20
History.21

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

SIST ETS 300 141-3:1997
Page 4
ETS 300 141-3: October 1996
Blank page

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

SIST ETS 300 141-3:1997
Page 5
ETS 300 141-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) Call Hold (HOLD)
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 141-3:1997
Page 6
ETS 300 141-3: October 1996
Blank page

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

SIST ETS 300 141-3:1997
Page 7
ETS 300 141-3: October 1996
1 Scope
This third part of ETS 300 141 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 Call Hold
(HOLD) 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 141-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 141-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 141-1 (1993): "Integrated Services Digital Network (ISDN);
Call Hold (HOLD) supplementary service ; Digital Subscriber Signalling System
No. one (DSS1) protocol; Part 1: Protocol specification".
[2] ETS 300 141-2: "Integrated Services Digital Network (ISDN); Call Hold (HOLD)
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".
[12] ETS 300 196-2 (1996): "Integrated Services Digital Network (ISDN); Generic
functional protocol for the support of supplementary services; Digital Subscriber
Signalling System No. one (DSS1) protocol; Part 2: Protocol Implementation
Conformance Statement (PICS) proforma specification".

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

SIST ETS 300 141-3:1997
Page 8
ETS 300 141-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 141-1
Call Held auxiliary state: See ETS 300 196-1 [6], subclause 7.1.2.
component: See ETS 300 196-1 [6], subclause 11.2.2.1.
Hold Requested auxiliary state: See ETS 300 196-1 [6], subclause 7.1.2.
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.
Retrieve Requested auxiliary state: See ETS 300 196-1 [6], subclause 7.1.2.
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 HOLD 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.

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

SIST ETS 300 141-3:1997
Page 9
ETS 300 141-3: October 1996
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.
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 (commonly referred to as a Private ISDN).
4 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
ATM Abstract Test Method
ATS Abstract Test Suite
DSS1 Digital Subscriber Signalling System No. one
HOLD Call Hold
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
U07 Call Received call state
U10 Active call state
5 Test Suite Structure (TSS)
HOLD - User
Served user (S/T) Remote user - Served user (T)
receipt of notifications (09)
(08)
Normal procedures Channel reservation Timers
function (07)
Hold Retrieve Request Manage Cancel Receipt of return
(01) (02) (03) (04) (05) result
(06)
NOTE: Numbers in brackets represent group numbers and are used in TP identifiers.
Figure 1: Test suite structure

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

SIST ETS 300 141-3:1997
Page 10
ETS 300 141-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. "HOLD"
= 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 141-1 [1], clauses 9, 10 and 14.
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 141-3:1997
Page 11
ETS 300 141-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
U00, U10, etc.
and Hold Requested, .
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 remains in the same state
or and enters state
Message SETUP, FACILITY, CONNECT, .
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 141-1 [1] contains 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 141-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 141-3:1997
Page 12
ETS 300 141-3: October 1996
6.2 User TPs for HOLD
All PICS items referred to in this subclause are as specified in ETS 300 141-2 [2] unless indicated
otherwise by another numbered reference.
6.2.1 Served user (S/T)
Selection: IUT supports coincident S and T reference point procedures. PICS: R 3.1.
6.2.1.1 Normal procedures
6.2.1.1.1 Hold
HOLD_U01_001 subclause 9.1.1 valid mandatory
Ensure that the IUT in the Active call state U10 and Idle auxiliary state to initiate the HOLD service,
sends a HOLD message and enters the Hold Requested auxiliary state.
HOLD_U01_002 subclause 9.1.1 valid optional
Ensure that the IUT in the Call Delivered call state U04 and Idle auxiliary state to initiate the HOLD
service,
sends a HOLD message and enters the Hold Requested auxiliary state.
Selection: IUT supports holding a call in call state U04. PICS: MC 1.2.
HOLD_U01_003 subclause 9.1.1 valid mandatory
Ensure that the IUT in the Active call state U10 and Hold Requested auxiliary state receiving a HOLD
ACKNOWLEDGE message,
releases the B-channel, remains in the Active call state U10 and enters the Call Held auxiliary state.
HOLD_U01_004 subclause 9.1.1 invalid mandatory
Ensure that the IUT in the Active call state U10 and Hold Requested auxiliary state, receiving an HOLD
ACKNOWLEDGE message with an optional information element with content error,
sends no message or sends a STATUS message cause #100 "invalid information element
contents" and enters the Call Held auxiliary state.
HOLD_U01_005 subclause 9.1.1 valid optional
Ensure that the IUT in the Call Delivered call state U04 and Hold Requested auxiliary state, receiving a
HOLD ACKNOWLEDGE message,
enters the Call Held auxiliary state.
Selection: IUT supports holding a call in call state U04. PICS: MC 1.2.
HOLD_U01_006 subclause 9.1.1 invalid optional
Ensure that the IUT in the Call Delivered call state U04 and Hold Requested auxiliary state, receiving a
HOLD ACKNOWLEDGE message with an optional information element with content error,
sends no message or sends a STATUS message cause #100 "invalid information element
contents" and enters the Call Held auxiliary state.
Selection: IUT supports holding a call in call state U04. PICS: MC 1.2.
HOLD_U01_007 subclause 9.1.2 valid mandatory
Ensure that the IUT in the Active call state U10 and Hold Requested auxiliary state, receiving a HOLD
REJECT message,
does not release the B-channel, remains in the Active call state U10 and enters the Idle auxiliary
state.
HOLD_U01_008 subclause 9.1.2 invalid mandatory
Ensure that the IUT in the Active call state U10 and Hold Requested auxiliary state, receiving a HOLD
REJECT message with an optional information element with content error,
sends no message or sends a STATUS message cause #100 "invalid information element
contents" and enters the Idle auxiliary state.

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

SIST ETS 300 141-3:1997
Page 13
ETS 300 141-3: October 1996
HOLD_U01_009 subclause 9.1.2 invalid mandatory
Ensure that the IUT in the Active call state U10 and Hold Requested auxiliary state, receiving a HOLD
REJECT message with a mandatory information element with content error,
sends a STATUS message cause #100 "invalid information element contents" and remains in the
same state.
HOLD_U01_010 subclause 9.1.2 invalid optional
Ensure that the IUT in the Call Delivered call state U04 and Hold Requested auxiliary state, receiving a
HOLD REJECT message,
enters the Idle auxiliary state.
Selection: IUT supports holding a call in call state U04. PICS: MC 1.2.
HOLD_U01_011 subclause 9.1.2 invalid optional
Ensure that the IUT in the Call Delivered call state U04 and Hold Requested auxiliary state, receiving a
HOLD REJECT message with an optional information element with content error,
sends no message or sends a STATUS message cause #100 "invalid information element
contents" and enters the Idle auxiliary state.
Selection: IUT supports holding a call in call state U04. PICS: MC 1.2.
HOLD_U01_012 subclause 9.1.2 invalid optional
Ensure that the IUT in the Call Delivered call state U04 and Hold Requested auxiliary state, receiving a
HOLD REJECT message with a mandatory information element with content error,
sends a STATUS message cause #100 "invalid information element contents" and remains in the
same state.
Selection: IUT supports holding a call in call state U04. PICS: MC 1.2.
6.2.1.1.2 Retrieve
HOLD_U02_001 subclause 9.3.1 valid mandatory
Ensure that the IUT in the Active call state U10 and Call Held auxiliary state to initiate the Retrieve
function,
sends a RETRIEVE message and enters the Retrieve Requested auxiliary state.
HOLD_U02_002 subclause 9.3.1 valid optional
Ensure that the IUT in the Call Delivered call state U04 and Call Held auxiliary state to initiate the Retrieve
function,
sends a RETRIEVE message and enters the Retrieve Requested auxiliary state.
Selection: IUT supports holding a call in call state U04. PICS: MC 1.2.
HOLD_U02_003 subclause 9.3.1 valid mandatory
Ensure that the IUT in the Active call state U10 and Retrieve Requested auxiliary state receiving a
RETRIEVE ACKNOWLEDGE message,
connects to the B channel and enters the Idle auxiliary state.
HOLD_U02_004 subclause 9.3.1 invalid mandatory
Ensure that the IUT in the Active call state U10 and Retrieve Requested auxiliary state receiving a
RETRIEVE ACKNOWLEDGE message with an optional information element with content error,
sends no message or sends a STATUS message cause #100 "invalid information element
contents" and enters the Idle auxiliary state.
HOLD_U02_005 subclause 9.3.1 valid optional
Ensure that the IUT in the Call Delivered call state U04 and Retrieve Requested auxiliary state, receiving a
RETRIEVE ACKNOWLEDGE message,
connects to the B channel and enters the Idle auxiliary state.
Selection: IUT supports holding a call in call state U04. PICS: MC 1.2.
HOLD_U02_006 subclause 9.3.1 invalid optional
Ensure that the IUT in the Call Delivered call state U04 and Retrieve Requested auxiliary state, receiving a
RETRIEVE ACKNOWLEDGE message with an optional information element with content error,
sends no message or sends a STATUS message cause #100 "invalid information element
contents" and enters the Idle auxiliary state.
Selection: IUT supports holding a call in call state U04. PICS: MC 1.2.

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

SIST ETS 300 141-3:1997
Page 14
ETS 300 141-3: October 1996
HOLD_U02_007 subclause 9.3.2 valid mandatory
Ensure that the IUT in the Active call state U10 and Retrieve Requested auxiliary state, receiving a
RETRIEVE REJECT message,
does not connect to the B-channel, remains in the Active call state U10 and enters the Call Held
auxiliary state.
HOLD_U02_008 subclause 9.3.2 invalid mandatory
Ensure that the IUT in the Active call state U10 and Retrieve Requested auxiliary state, receiving a
RETRIEVE REJECT message with an optional information element with content error,
sends no message or, sends a STATUS message cause #100 "invalid information element
contents" and enters the Idle auxiliary state.
HOLD_U02_009 subclause 9.3.2 invalid mandatory
Ensure that the IUT in the Active call state U10 and Retrieve Requested auxiliary state, receiving a
RETRIEVE REJECT message with a mandatory information element with content error,
sends a STATUS message cause #100 "invalid information element contents" and remains in the
same state.
HOLD_U02_0010 subclause 9.3.2 valid optional
Ensure that the IUT in the Call Delivered call state U04 and Retrieve Requested auxiliary state, receiving a
RETRIEVE REJECT message,
enters the Call Held auxiliary state.
Selection: IUT supports holding a call in call state U04. PICS: MC 1.2.
HOLD_U02_0011 subclause 9.3.2 invalid optional
Ensure that the IUT in the Call Delivered call state U04 and Retrieve Requested auxiliary state, receiving a
RETRIEVE REJECT message with an optional information element with content error,
sends no message or sends a STATUS message cause #100 "invalid information element
contents" and enters the Idle auxiliary state.
Selection: IUT supports holding a call in call state U04. PICS: MC 1.2.
HOLD_U02_0012 subclause 9.3.2 invalid optional
Ensure that the IUT in the Call Delivered call state U04 and Retrieve Requested auxiliary state, receiving a
RETRIEVE REJECT message with a mandatory information element with content error,
sends a STATUS message cause #100 "invalid information element contents" and remains in the
same state.
Selection: IUT supports holding a call in call state U04. PICS: MC 1.2.
6.2.1.2 Channel reservation function
Selection: IUT supports explicit channel reservation function. PICS: [12] MCu 4.2.
6.2.1.2.1 Request
HOLD_U03_001 subclause 9.1.1 valid optional
Ensure that the IUT in the Call Delivered call state U04 and Idle auxiliary state, to request an explicit
reservation,
sends an ExplicitReservationCreationControl invoke component, in a Facility information element in
a HOLD message and enters the Hold Request state or in a FACILITY, or INFORMATION
message and remains in the same state.
Selection: IUT supports holding a call in call state U04. PICS: MC 1.2.
HOLD_U03_002 subclause 9.1.1 valid mandatory
Ensure that the IUT in the Active call state U10 and Idle auxiliary state, to request an explicit reservation,
sends an ExplicitReservationCreationControl invoke component, in a Facility information element in
a HOLD message and enters the Hold Request state or in a FACILITY, or INFORMATION
message and remains in the same state.

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

SIST ETS 300 141-3:1997
Page 15
ETS 300 141-3: October 1996
HOLD_U03_003 subclause 9.1.1 valid optional
Ensure that the IUT in the Call Delivered call state U04 and Call Held auxiliary state to request an explicit
reservation,
sends an ExplicitReservationCreationControl invoke component, in a Facility information element in
a RETRIEVE message and enters to the Retrieve Request auxiliary state or in a FACILITY, or
INFORMATION message and remains in the same state.
Selection: IUT supports holding a call in call state U04. PICS: MC 1.2.
HOLD_U03_004 subclause 9.1.1 valid mandatory
Ensure that the IUT in the Active call state U10 and Call Held auxiliary state to request an explicit
reservation,
sends an ExplicitReservationCreationControl invoke component, in a Facility information element in
a RETRIEVE message and enters to the Retrieve Request auxiliary state or in a FACILITY or
INFORMATION message and remains in the same state.
6.2.1.2.2 Manage
HOLD_U04_001 subclause 9.1.1 valid optional
Ensure that the IUT in the Call Delivered call state U04 and Call Held auxiliary state to manage an explicit
reservation with reservation indicator,
sends an ExplicitReservationManagement invoke component with the reservation indicator in a
Facility information element in a RETRIEVE message.
Selection: the IUT is able to handle a reservation with reservation indicator.
Selection: IUT supports holding a call in call state U04. PICS: MC 1.2.
HOLD_U04_002 subclause 9.1.1 valid optional
Ensure that the IUT in the Call Delivered call state U04 and Call Held auxiliary state to manage an explicit
reservation without reservation indicator,
sends an ExplicitReservationManagement invoke component without reservation indicator in a
Facility information element in a RETRIEVE message.
Selection: the IUT is able to handle a reservation without reservation indicator.
Selection: IUT supports holding a call in call state U04. PICS: MC 1.2.
HOLD_U04_003 subclause 9.1.1 valid optional
Ensure that the IUT in the Active call state U10 and Call Held auxiliary state to manage an explicit
reservation with reservation indicator,
sends an ExplicitReservationManagement invoke component with the reservation indicator in a
Facility information element in a RETRIEVE message.
Selection: the IUT is able to handle a reservation with reservation indicator.
HOLD_U04_004 subclause 9.1.1 valid optional
Ensure that the IUT in the Active call state U10 and Call Held auxiliary state to manage an explicit
reservation without reservation indicator,
sends an ExplicitReservationManagement invoke component without reservation indicator in a
Facility information element in a RETRIEVE message.
Selection: the IUT is able to handle a reservation without reservation indicator.
6.2.1.2.3 Cancel
HOLD_U05_001 subclause 9.1.1 valid optional
Ensure that the IUT in the Call Delivered call state U04 and Idle auxiliary state to cancel an explicit
reservation with reservation indicator,
sends an ExplicitReservationCancel invoke component with the reservation indicator
...