SIST ETS 300 267-5:1998
(Main)Integrated Services Digital Network (ISDN); Telephony 7 kHz and videotelephony teleservices; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network
- Abstract
..
- Status
- Published
- Publication Date
- 30-Nov-1998
- Technical Committee
- SPS - Signalling protocols and switching
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Dec-1998
- Due Date
- 01-Dec-1998
- Completion Date
- 01-Dec-1998
- Mandate
- T-294
Buy Documents
SIST ETS 300 267-5:1998 is the Slovenian version of ETS 300 267-5 Edition 1 from ETSI. It defines the network-side Test Suite Structure and Test Purposes (TSS&TP) for Integrated Services Digital Network (ISDN) telephony 7 kHz and videotelephony teleservices using the Digital Subscriber Signalling System No. one (DSS1) protocol. Engineers use it to select and build conformance tests for implementations at the T reference point or the coincident S and T reference point.
What does SIST ETS 300 267-5:1998 specify?
SIST ETS 300 267-5:1998 specifies the stage three test suite structure and test purposes for the network side of the ISDN telephony 7 kHz and videotelephony teleservices. It covers the protocol requirements defined in ETS 300 267-1, the additional generic requirements in clause 5 of that part, and the telephony 7 kHz and videotelephony teleservice requirements in clauses 6 and 7 of ETS 300 267-1.
The standard is written for two implementation types:
- network requirements at the coincident S and T reference point
- network requirements for interworking with private ISDNs at the T reference point
Clause 4 defines the test suite structure, clause 5 lists the test purposes, clause 6 states compliance, and Annex A gives informative cross references between generic, telephony 7 kHz, and videotelephony test purposes.
| Annex | What it covers |
|---|---|
| Annex A | Informative cross references between generic test purposes and the telephony 7 kHz and videotelephony test purposes, plus the mapping between telephony 7 kHz and videotelephony test purposes |
What are the key requirements of SIST ETS 300 267-5:1998?
SIST ETS 300 267-5:1998 is mainly a conformance test-purpose document, so its key requirements are about how to structure, identify, and select test cases rather than how to design the protocol itself.
Clause 4 defines a six-level TSS tree. The top level is NT7V, then ORIG or DEST, then BV, BI, or BO, then GEN, TL7, or VTL, then FBA, FBN, or CMN, and finally ST, PT, or ST_T. In practice, this lets a test lab filter cases by where the behaviour occurs, what kind of behaviour it is, which teleservice is under test, and which implementation type is being assessed.
Clause 5.1 defines the TP identifier format. GTP, TTP, and VTP identify generic, telephony 7 kHz, and videotelephony test purposes; the digits identify originating or destination interface, valid/invalid/inopportune behaviour, and fallback allowed, fallback not allowed, or connection management. This makes the case names readable and traceable when selecting tests from the PICS proforma.
Clause 5 uses structured tables for each test purpose. Each TP entry carries the ETS 300 267-1 reference, any other relevant reference, the full TSS reference, selection criteria, the test purpose description, cross references, and comments. In practice, this is the information a test developer needs to decide whether a case applies to a given implementation and how to interpret the expected behaviour.
Fallback allowed cases verify selection and substitution behaviour. In the originating and destination interface clauses, the network is tested with SETUP messages carrying combinations such as BC1, BC2, HLC1, and HLC2. The cases check whether the IUT can accept the higher-priority or lower-priority bearer/high-layer option, whether it can fall back to telephony 7 kHz or videotelephony, and whether it uses the right CONNECT, CALL PROCEEDING, PROGRESS, or ALERTING behaviour.
Subscription checks are part of the fallback allowed flow. Some test purposes require the IUT to perform a subscription check for the defined prime service, then accept the call if the check succeeds or release it with cause #57 "bearer capability not authorized" if the check fails. In practice, this is how the standard ties service authorization to call setup behaviour.
Fallback not allowed cases test rejection and clearing. When the calling user does not allow fallback, the test purposes expect either call clearing with cause #65 "bearer capability not implemented" or, where applicable, normal call progression with the selected bearer capability. This matters because the network must respect the user's service choice and not silently substitute another teleservice.
Connection management cases cover call clearing and videotelephony second-connection setup. The document checks DISCONNECT handling, the use of PI=#8, and the presentation of tone or announcement in 3,1 kHz mode. For videotelephony, clause 5.3.3 also includes establishment of CR2 for calls that require two connections.
Invalid and inopportune behaviour are tested separately. The invalid behaviour cases cover syntactically invalid or incompatible messages, such as CONNECT or CALL PROCEEDING with unexpected bearer or high-layer compatibility content. The inopportune behaviour cases cover progress indicators such as PI=#1, PI=#2, and PI=#5 appearing in sequence and the way the network should continue handling the call.
Clause 6 defines what a compliant abstract test suite must do. A compliant suite must use a set or subset of the test purposes in clause 5, use an appropriate subset of the TSS in clause 4, keep the same naming conventions, preserve the link to ETS 300 267-2 PICS-based selection, and comply with ISO/IEC 9646-2 and ISO/IEC 9646-3. For users, that means an ATS built from this document must stay aligned with the standard's selection logic.
What terms does SIST ETS 300 267-5:1998 define?
- BC1 and BC2 are the first and second Bearer Capability information elements in a SETUP message when bearer capability selection is being tested, with BC1 lower priority and BC2 higher priority.
- HLC1 and HLC2 are the first and second High layer compatibility information elements in a SETUP message when high-layer compatibility selection is being tested, with HLC1 lower priority and HLC2 higher priority.
- IUT means Implementation Under Test, the user terminal or private ISDN that provides the protocol at the S/T or T reference point.
- LLC means Low Layer Compatibility information element, which the test purposes use to distinguish messages that carry or omit low-layer compatibility information.
- PI=#5 is the Progress indicator information element with progress description #5, "interworking has occurred and has resulted in a telecommunications service change."
- PI=#8 is the Progress indicator information element with progress description #8, "In-band information or appropriate pattern now available."
- CR1 and CR2 are the call references for the first and second call, used where videotelephony establishes or manages two connections.
Who uses SIST ETS 300 267-5:1998?
SIST ETS 300 267-5:1998 is used by test engineers, protocol conformance labs, network equipment suppliers, and ISDN operators who need to verify network-side DSS1 behaviour for telephony 7 kHz and videotelephony teleservices. Quality managers and buyers can use it to check whether a vendor's implementation has test purposes that match the required fallback, connection management, and call-clearing behaviour.
The document is especially useful when a team needs to:
- derive abstract test cases from a PICS proforma
- decide whether fallback allowed or fallback not allowed cases apply
- verify originator-side and destination-side call handling
- check interoperability with private ISDNs and interworking cases
- confirm that call clearing, progress indications, and second-connection handling follow the defined network behaviour
What changed in SIST ETS 300 267-5:1998 from the previous edition?
SIST ETS 300 267-5:1998 is identical to ETS 300 267-5 Edition 1.
Which standards are used with SIST ETS 300 267-5:1998?
SIST ETS 300 267-5:1998 cites these standards and recommendations as its technical basis:
- ETS 300 102-1 - basic call control for the ISDN user-network interface layer 3; used for call states, timers, and basic call clearing behaviour
- ETS 300 144 - audiovisual channel frame structure and in-band signalling syntax; used for bit-rate allocation signal handling
- ETS 300 267-1 - the protocol specification for the telephony 7 kHz and videotelephony teleservices; this is the main requirement source for the test purposes
- ETS 300 267-2 - the PICS proforma specification; used for test selection criteria
- I-ETS 300 316 - PICS proforma for the signalling network layer protocol for circuit-mode basic call control; used in selection criteria
- CCITT Recommendation G.711 - PCM of voice frequencies; used for A-law encoding of tones and announcements
- CCITT Recommendation I.130 - characterization of telecommunication services supported by an ISDN; provides the stage three service description context
- ITU-T Recommendation I.411 - ISDN user-network interface reference configurations; defines the T reference point and coincident S and T reference point context
- ISO/IEC 9646-2 - abstract test suite specification methodology; required for compliant ATS construction
- ISO/IEC 9646-3 - Tree and Tabular Combined Notation; used for the test suite and test purpose notation
The foreword also identifies the companion parts of the ETS 300 267 series:
- 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
What does the SIST ETS 300 267-5:1998 document contain?
SIST ETS 300 267-5:1998 contains a six-clause structure, a figure showing the TSS tree, tables for TP identifiers and TP layout, and a long clause 5 catalogue of test purposes. The test purposes are written to cover originating and destination network behaviour, valid, invalid, and inopportune cases, and the three main functional groupings of generic requirements, telephony 7 kHz, and videotelephony.
Clause 5 uses table-style entries with references, selection criteria, descriptions, cross references, and comments so that a tester can map each case to the relevant PICS items. Annex A contains two cross-reference tables: one maps generic test purposes to the telephony 7 kHz and videotelephony cases, and the other maps telephony 7 kHz test purposes to equivalent videotelephony test purposes.
Buy Documents
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST ETS 300 267-5:1998 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Integrated Services Digital Network (ISDN); Telephony 7 kHz and videotelephony teleservices; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network". This standard covers: ..
..
SIST ETS 300 267-5:1998 is classified under the following ICS (International Classification for Standards) categories: 33.080 - Integrated Services Digital Network (ISDN). The ICS classification helps identify the subject area and facilitates finding related standards.
SIST ETS 300 267-5:1998 is associated with the following European legislation: Standardization Mandates: T-294. When a standard is cited in the Official Journal of the European Union, products manufactured in conformity with it benefit from a presumption of conformity with the essential requirements of the corresponding EU directive or regulation.
SIST ETS 300 267-5:1998 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.SHFLILNDFLMDIntegrated Services Digital Network (ISDN); Telephony 7 kHz and videotelephony teleservices; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network33.020Telekomunikacije na splošnoTelecommunications in generalICS:Ta slovenski standard je istoveten z:ETS 300 267-5 E13SIST ETS 300 267-5:1998en01-DSULO-19983SIST ETS 300 267-5:1998SLOVENSKI
STANDARD
DRAFTEUROPEANprETS 300 267-5TELECOMMUNICATIONMarch 1997STANDARDSource: ETSI TC-SPSReference: DE/SPS-05048-5ICS:33.020Key words:ISDN, DSS1, teleservice, 7 kHz, video, telephony, testing, TSS&TP, networkIntegrated Services Digital Network (ISDN);Telephony 7 kHz and videotelephony teleservices;Digital Subscriber Signalling System No. one (DSS1) protocol;Part 5: Test Suite Structure and Test Purposes (TSS&TP)specification for the networkETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1997. All rights reserved.SIST ETS 300 267-5:1998
Page 2Draft prETS 300 267-5: March 1997Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.SIST ETS 300 267-5:1998
Page 3Draft prETS 300 267-5: March 1997ContentsForeword.5Introduction.51Scope.72Normative references.73Definitions and abbreviations.83.1Definitions.83.2Abbreviations.94Test Suite Structure (TSS).104.1First test group level.104.2Second test group level.104.3Third test group level.104.4Fourth test group level.104.5Fifth test group level.104.6Sixth test group level.115Test Purposes (TP).125.1Test purpose format.125.2Calling network interface.135.2.1Valid behaviour.135.2.1.1Generic requirements.135.2.1.1.1Fallback allowed.135.2.1.1.2Fallback not allowed.195.2.1.1.3Connection management.215.2.1.2Telephony 7 kHz teleservice.215.2.1.2.1Fallback allowed.215.2.1.2.2Fallback not allowed.265.2.1.2.3Connection management.285.2.1.3Videotelephony teleservice.285.2.1.3.1Fallback allowed.285.2.1.3.2Fallback not allowed.335.2.1.3.3Connection management.355.2.2Invalid behaviour.365.2.2.1Generic requirements.365.2.2.1.1Fallback allowed.365.3Destination interface.365.3.1Valid behaviour.365.3.1.1Generic requirements.365.3.1.1.1Fallback allowed.365.3.1.1.1.1Requirements at the coincident S andT reference point or for interworkingwith private ISDNs.365.3.1.1.1.2Requirements at the coincident S andT reference point.395.3.1.1.1.3Requirements for interworking withprivate ISDNs.445.3.1.1.2Fallback not allowed.445.3.1.1.3Connection management.465.3.1.2Telephony 7 kHz teleservice.475.3.1.2.1Fallback allowed.475.3.1.2.1.1Requirements at the coincident S andT reference point or for interworkingwith private ISDNs.47SIST ETS 300 267-5:1998
Page 4Draft prETS 300 267-5: March 19975.3.1.2.1.2Requirements for interworking withprivate ISDNs.505.3.1.2.2Fallback not allowed.515.3.1.2.3Connection management.525.3.1.3Videotelephony teleservice.525.3.1.3.1Fallback allowed.525.3.1.3.1.1Requirements at the coincident S andT reference point or for interworkingwith private ISDNs.525.3.1.3.1.1Requirements at the coincident S andT reference point.575.3.1.3.1.1Requirements for interworking withprivate ISDNs.595.3.1.3.2Fallback not allowed.605.3.1.3.3Connection management.615.3.2Invalid behaviour.625.3.2.1Generic requirements.625.3.2.1.1Fallback allowed.625.3.2.1.1.1Requirements at the coincident S andT reference point or for interworkingwith private ISDNs.625.3.2.1.1.2Requirements at the coincident S andT reference point.635.3.2.1.1.3Requirements for interworking withprivate ISDNs.645.3.2.2Telephony 7 kHz teleservice.695.3.2.2.1Fallback allowed.695.3.2.3Videotelephony teleservice.705.3.2.3.1Fallback allowed.705.3.3Inopportune behaviour.765.3.3.1Generic requirements.765.3.3.1.1Fallback allowed.766Compliance.78Annex A (informative):Cross references: Generic, telephony 7 kHz and videotelephony teleservicestest purposes.79A.1Generic test purposes to telephony 7 kHz and videotelephony teleservices test purposes.79A.2Telephony 7 kHz to videotelephony teleservices test purposes.82History.84SIST ETS 300 267-5:1998
Page 5Draft prETS 300 267-5: March 1997ForewordThis draft European Telecommunication Standard (ETS) has been produced by the Signalling Protocolsand Switching (SPS) Technical Committee of the European Telecommunications Standards Institute(ETSI), and is now submitted for the Public Enquiry phase of the ETSI standards approval procedure.This ETS is part 5 of a multi-part standard covering the Digital Subscriber Signalling System No. one(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) telephony 7 kHz andvideotelephony teleservices, 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".Proposed transposition datesDate of latest announcement of this ETS (doa):3 months after ETSI publicationDate of latest publication of new National Standardor endorsement of this ETS (dop/e):6 months after doaDate of withdrawal of any conflicting National Standard (dow):6 months after doaIntroductionThis ETS is divided into six clauses. Clauses 1 to 3 form the scope, references and abbreviations.Clause 4 contains the test suite structure. Clause 5 contains the complete list of test purposes. Clause 6contains the requirements for a generic or abstract test suite to comply with this ETS.It is been assumed that the Implementation Under Test (IUT) already complies with the conformancerequirements associated with the ISDN basic call as defined in ETS 300 102-1. This is specified as arequirement in ETS 300 267-2, clause 5. ETS 300 267-1, subclause 5.1, states that the additional genericrequirements of clause 5 are defined to be compatible with the existing requirements of ETS 300 102-1.In cases where ETS 300 267-1 specifies that requirements in ETS 300 102-1 shall apply, it is assumedthat, because the IUT already complies with ETS 300 102-1, it also complies with these requirements.However, when specifying the abstract test cases, including test case selection, the requirements ofETS 300 102-1 need to be taken into account.SIST ETS 300 267-5:1998
Page 6Draft prETS 300 267-5: March 1997Blank pageSIST ETS 300 267-5:1998
Page 7Draft prETS 300 267-5: March 19971ScopeThis fifth part of ETS 300 267 is applicable to the stage three of the telephony 7 kHz and videotelephonyteleservices for the pan-European Integrated Services Digital Network (ISDN) as provided by Europeanpublic telecommunications operators at the T reference point or coincident S and T reference point (asspecified in ITU-T Recommendation I.411 [8] by means of the Digital Subscriber Signalling SystemNo. one (DSS1) protocol. ETS 300 267-1 [3] provides the protocol specification and ETS 300 267-2 [4] theProtocol Implementation Conformance Statement (PICS) proforma specification. Stage three identifies theprotocol procedures and switching functions needed to support a telecommunications service (see CCITTRecommendation I.130 [7]).This ETS specifies the Test Suite Structure and Test Purposes (TSS&TP) for the network side. It coversthe protocol requirements as defined in ETS 300 267-1 [3] and provides test purposes for the additionalgeneric requirements for basic telecommunication services not defined in ETS 300 102-1 [1](ETS 300 267-1 [3], clause 5), for the telephony 7 kHz teleservice (ETS 300 267-1 [3], clause 6) and forthe videotelephony teleservice (ETS 300 267-1 [3], clause 7).Two types of implementation are covered:-an implementation which supports network requirements at the coincident S and T reference point;-an implementation which supports network requirements for interworking with private ISDNs at theT reference point.2Normative referencesThis ETS incorporates by dated or undated references, 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 102-1: "Integrated Services Digital Network (ISDN); User-networkinterface layer 3; Specifications for basic call control".[2]ETS 300 144: "Integrated Services Digital Network (ISDN); Audiovisual services;Frame structure for a 64 kbit/s to 1 920 kbit/s channel and associated syntax forinband signalling" (equivalent to ITU-T Recommendation H.221).[3]ETS 300 267-1 (1994) including A1 (1996): "Integrated Services Digital Network(ISDN); Telephony 7 kHz and videotelephony teleservices; Digital SubscriberSignalling System No. one (DSS1) protocol; Part 1: Protocol specification".[4]ETS 300 267-2 (1996): "Integrated Services Digital Network (ISDN); Telephony7 kHz and videotelephony teleservices; Digital Subscriber Signalling System No.one (DSS1) protocol; Part 2: Protocol Implementation Conformance Statement(PICS) proforma specification".[5]I-ETS 300 316: "Integrated Services Digital Network (ISDN); Digital SubscriberSignalling System No. one (DSS1); Protocol Implementation ConformanceStatement (PICS) proforma specification for signalling network layer protocol forcircuit-mode basic call control (basic access, network)".[6]CCITT Recommendation G.711 (1988): "Pulse code modulation (PCM) of voicefrequencies".[7]CCITT Recommendation I.130 (1988): "Method for the characterization oftelecommunication services supported by an ISDN and network capabilities ofan ISDN".[8]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces -Reference configurations".SIST ETS 300 267-5:1998
Page 8Draft prETS 300 267-5: March 1997[9]ISO/IEC 9646-2: "Information technology - Open systems interconnection -Conformance testing methodology and framework - Part 2: Abstract test suitespecification".[10]ISO/IEC 9646-3: "Information technology - Open systems interconnection -Conformance testing methodology and framework - Part 3: The Tree andTabular Combined Notation".3Definitions and abbreviations3.1DefinitionsFor the purposes of this ETS, the definitions in ETS 300 267-1 [3] apply in addition to the followingdefinitions:BC1: The first (lower priority) Bearer capability information element included in a SETUP messageallowing bearer capability selection.BC2: The second (higher priority) Bearer capability information element included in a SETUP messageallowing bearer capability selection.BC=speech: A Bearer capability information element with its information transfer capability field set to"speech" and its user information layer one protocol field set to "G.711 A-law".BC=UDI/TA: A Bearer capability information element with its information transfer capability field set to"UDI/TA" and its user information layer one protocol field set to "Recommendations H.221 and H.242".BC=UDI: A Bearer capability information element with its information transfer capability field set to "UDI"and its user information layer one protocol field set to "Recommendations H.221 and H.242".bit-rate allocation signal: Bit position within the frame structure to transmit commands, control andindication signals, capabilities.HLC1: The first (lower priority) High layer compatibility information element in a SETUP message allowinghigh layer compatibility selection.HLC2: The second (higher priority) High layer compatibility information element in a SETUP messageallowing high layer compatibility selection.HLC=telephony: A High layer compatibility information element with its high layer characteristicsidentification field set to "telephony".HLC=videotelephony_ic: A High layer compatibility information element with its high layer characteristicsidentification field set to "110 0000 - videotelephony (Recommendation F.721)" and its extendedaudiovisual characteristics identification field set to "000 0001 - capability set of initial channel ofRecommendation H.221".HLC=videotelephony_nex: A High layer compatibility information element with its high layercharacteristics identification field set to "110 0000 - videotelephony (Recommendation F.721)" but notcontaining an extended audiovisual characteristics identification field.HLC=videotelephony_sc: A High layer compatibility information element with its high layercharacteristics identification field set to "110 0000 - videotelephony (Recommendation F.721)" and itsextended audiovisual characteristics identification field set to "000 0010 - capability set of subsequentchannel of Recommendation H.221".Implementation Under Test (IUT): The component of the system under test (user terminal or privateISDN) providing the protocol specified in ETS 300 267-1 [3] at the S/T or T reference point.in-band signalling: Signalling via the bit-rate allocation signal of the frame structure, as defined inETS 300 144 [2].SIST ETS 300 267-5:1998
Page 9Draft prETS 300 267-5: March 1997mode 0F: Transmission mode in which the initial channel contains framing, and 7-bit G.711 audio signalis being transmitted.mode 0U: Transmission mode in which the initial channel does not contain framing, and 8-bit G.711 audiosignal is being transmitted.PI=#1: A Progress indicator information element, with its progress description field set to #1 "Call is notend-to-end ISDN".PI=#2: A Progress indicator information element, with its progress description field set to #2 "Destinationaddress is non-ISDN".PI=#3: A Progress indicator information element, with its progress description field set to #3 "Originationaddress is non-ISDN".PI=#4: A Progress indicator information element, with its progress description field set to #4 "Call hasreturned to the ISDN".PI=#5: A Progress indicator information element, with its progress description field set to #5 "interworkinghas occurred and has resulted in a telecommunications service change".PI=#8: A Progress indicator information element, with its progress description field set to #8 "In-bandinformation or appropriate pattern now available".telephony 7 kHz fallback allowed SETUP message: A SETUP message containing two BCs, with thefirst BC=speech and the second BC=UDI/TA, a HLC=telephony, and not containing a LLC.telephony 7 kHz fallback not allowed SETUP message: A SETUP message containing a singleBC=UDI/TA and a single HLC=telephony, and not containing a LLC.videotelephony fallback allowed SETUP message: A SETUP message containing two BCs, with thefirst BC=speech and the second BC=UDI/TA, and two HLCs, with the first HLC=telephony and the secondHLC=videotelephony_ic, and not containing a LLC.videotelephony fallback not allowed SETUP message: A SETUP message containing a singleBC=UDI/TA and a single HLC=videotelephony_ic, and not containing a LLC.videotelephony SETUP message for CR2 : A SETUP message containing a single BC=UDI and asingle HLC=videotelephony_sc. The SETUP message is used to establish the second connection in avideotelephony call requiring two connections.3.2AbbreviationsFor the purposes of this ETS, the abbreviations in ETS 00 267-1 [3] and ETS 300 267-2 [4] apply. Inaddition, the following abbreviations apply.ATSAbstract Test SuiteBCBearer Capability information elementCR1Call Reference for the first callCR2Call Reference for the second callHLCHigh Layer Compatibility information elementIUTImplementation under testLLCLow Layer Compatibility information elementPIProgress Indicator information elementTPTest PurposeTSSTest Suite StructureUDIUnrestricted Digital InformationUDI/TAUnrestricted Digital Information with Tones/AnnouncementsSIST ETS 300 267-5:1998
Page 10Draft prETS 300 267-5: March 19974Test Suite Structure (TSS)The test suite is structured as a tree. Six test group levels are defined. The TSS is depicted in figure 1.4.1First test group levelThe first test group level contains the name of the test suite:NT7VNetwork side telephony 7 kHz, videotelephony teleservices and generic protocol.4.2Second test group levelThe second test group level indicates whether the test purpose covers the originating interface or thedestination interface:ORIGOriginating Interface;DESTDestination Interface.4.3Third test group levelThe third test group level indicates whether the test purpose covers a requirement applicable to validbehaviour, to invalid behaviour or to inopportune behaviour:BVValid Behaviour test purpose;BIInvalid Behaviour test purpose;BOinOpportune Behaviour test purpose.4.4Fourth test group levelThe fourth test group level indicates whether the test purpose covers a requirement applicable to thegeneric protocol, the telephony 7 kHz protocol, or the videotelephony teleservice protocol:GENGeneric requirements. The test purpose covers a requirement applicable for thegeneric part of ETS 300 267-1 [3] (clause 5);TL7Telephony 7 kHz teleservice. The test purpose covers a requirement applicable for thetelephony 7 kHz part of ETS 300 267-1 [3] (clause 6);VTLVideotelephony teleservice. The test purpose covers a requirement applicable for thevideotelephony part of ETS 300 267-1 [3] (clause 7).The group for generic requirements does not appear in the TSS. None of the generic test purposes canbe considered as testable.4.5Fifth test group levelThe fifth test group level indicates which kind of functionality is tested and, more precisely, whether thetest purposes covers requirements applicable to fallback allowed, fallback not allowed or connectionmanagement. Three groups are defined:FBAFallBack Allowed: this group covers all tests where a fallback allowed SETUPmessage is sent to the IUT;FBNFallBack Not allowed: this group covers all tests where a fallback not allowed SETUPmessage is sent to the IUT;CMNConnection MaNagement: this group includes all other cases which do not test theresponse to or the sending of a fallback allowed or a fallback not allowed SETUPmessage. As a consequence, the clearing of a call and the establishment of a secondconnection for videotelephony is tested here.SIST ETS 300 267-5:1998
Page 11Draft prETS 300 267-5: March 19974.6Sixth test group levelThe sixth test group level indicates the type of implementation to which the test purpose applies:STAn implementation which supports network requirements at the coincident S andT reference point;PTAn implementation which supports network requirements for interworking with privateISDNs at the T reference point;ST_TAn implementation which supports network requirements at the coincident S andT reference point or network requirements for interworking with private ISDNs at theT reference point.This level group does not appear when only one of them is included as subgroup. ORIG
(1)NT7VBV (1)ORIG
(1)TL7CMN (3)GENFBN (2)FBA (1)FBA (1)FBN (2)VTLFBA (1)FBN (2)CMN (3)BI (2)FBA (1)GENCMN (3)DEST
(2)DEST
(2)TL7BV
(1)GENTL7BI (2)FBA (1)VTLBO (3)FBA (1)FBA (1)FBA (1)GENFBN (2)GENFBA (1)ST_TSTPTVTLCMN (3)FBN (2)FBA (1)ST_TSTPTFBA (1)FBN (2)CMN (3)PTST_TCMN (3)ST_TSTPTFigure 1: Test suite structureSIST ETS 300 267-5:1998
Page 12Draft prETS 300 267-5: March 19975Test Purposes (TP)5.1Test purpose formatThe structure of a test purpose identifier is defined in table 1.Table 1: TP identifier naming convention scheme_GTPgeneric protocol requirementTTPtelephony 7 kHz requirementVTPvideotelephony requirement1st digit1 Originating Interface; 2 Destination Interface2nd digit1 Valid; 2 Invalid; 3 Inopportune3rd digit1 Fallback Allowed; 2 Fallback Not Allowed; 3 Connection Management2 digitssequential test case numberThe test purposes are formatted as tables to increase readability. The table format is shown in table 2.Text in bold shows the text which is always present, normal text provides an explanation for each field.Table 2: Structure of a single TPTest purpose identifierReference to ETS 300 267-1 [3]:Other relevant reference:TSS referenceThe full test suite structure reference.Selection criteriaThe criteria necessary in order to select the test. Unless otherwise specified,references are to ETS 300 267-2 [4].Test purposeDescription of the test purpose.Cross referenceGTP/TTP/VTP cross reference data.CommentsAny relevant comments.The "Other relevant reference" field, where applicable, contains a reference to a specification documentcontaining the whole, or part, of the requirement to be tested by the test purpose.The "Selection criteria" field consists of a Boolean expression incorporating items from ETS 300 267-2 [4](in which case items are not prefixed by a reference number) and from I-ETS 300 316 [5].Some of the telephony 7 kHz or videotelephony test purposes are directly related, but not identical, togeneric ones. Where such a relationship exists, the reference to the related generic test purpose isspecified in the "Cross reference" field of the telephony 7 kHz or videotelephony test purpose.Untestable test purposes are listed using italic font. Test purposes for generic protocol requirementswhich correspond to no particular IUT have been considered as untestable.SIST ETS 300 267-5:1998
Page 13Draft prETS 300 267-5: March 19975.2Calling network interface5.2.1Valid behaviour5.2.1.1Generic requirements5.2.1.1.1Fallback allowedGTP111_01Reference to ETS 300 267-1 [3]:5.5.1.1, 5.6.1Other relevant reference:TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaMC 3.1 OR MC 4.1Test purposeVerify that the IUT, in Outgoing Call Proceeding call state N3, having received aSETUP message, containing two BCs, BC1 and BC2, and no LLC,is capable of sending a CONNECT message containing BC2.Cross referenceCommentsSending of CONNECT following receipt of a SETUP, fallback from BC2 to BC1allowed; the two BCs are included in the SETUP message in ascending order ofpriority, i.e. BC2 appears subsequent to BC1: fallback did not occur either withinthe IUT or at the destination user.GTP111_02Reference to ETS 300 267-1 [3]:5.5.1.1, 5.6.1Other relevant reference:TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaMC 3.1 OR MC 4.1Test purposeVerify that the IUT, in Call Delivered call state N4, having received a SETUPmessage, containing two BCs, BC1 and BC2, and no LLC,is capable of sending a CONNECT message containing BC2.Cross referenceCommentsSending of CONNECT following receipt of a SETUP, fallback from BC2 to BC1allowed; the two BCs are included in the SETUP message in ascending order ofpriority, i.e. BC2 appears subsequent to BC1: fallback did not occur either withinthe IUT or at the destination user.GTP111_03Reference to ETS 300 267-1 [3]:5.5.1.1, 5.6.1Other relevant reference:TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaMC 3.1 OR MC 4.1Test purposeVerify that the IUT, in Outgoing Call Proceeding call state N3, having received aSETUP message, containing two BCs, BC1 and BC2, and no LLC,is capable of sending a CONNECT message containing BC1.Cross referenceCommentsSending of CONNECT: fallback occurred, to BC1, at the destination user.GTP111_04Reference to ETS 300 267-1 [3]:5.5.1.1, 5.6.1Other relevant reference:TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaMC 3.1 OR MC 4.1Test purposeVerify that the IUT, in Call Delivered call state N4, having received a SETUPmessage, containing two BCs, BC1 and BC2, and no LLC,is capable of sending a CONNECT message containing BC1.Cross referenceCommentsSending of CONNECT: fallback occurred, to BC1, at the destination user.SIST ETS 300 267-5:1998
Page 14Draft prETS 300 267-5: March 1997GTP111_05Reference to ETS 300 267-1 [3]:5.5.1.1, 5.6.1Other relevant reference:TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaMC 3.1 OR MC 4.1Test purposeVerify that the IUT, in Idle call state N0, on receipt of a SETUP messagecontaining two BCs, BC1 and BC2, and no LLC,is capable of sending a CALL PROCEEDING, PROGRESS or ALERTINGmessage containing a PI=#5 and BC1.Cross referenceCommentsSending of CALL PROCEEDING, PROGRESS or ALERTING: fallback occurred,to BC1, within the IUT.GTP111_06Reference to ETS 300 267-1 [3]:5.5.1.1, 5.6.1Other relevant reference:TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaMC 3.1 OR MC 4.1Test purposeVerify that the IUT, in Outgoing Call Proceeding call state N3, having received aSETUP message, containing two BCs, BC1 and BC2, and no LLC, on sending aPROGRESS message containing a PI=#5,does not stop timers as described in ETS 300 102-1 [1].Cross referenceCommentsSending of PROGRESS: fallback occurred, to BC1, within the IUT.GTP111_07Reference to ETS 300 267-1 [3]:5.5.3.1, 5.6.3Other relevant reference:TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaMC 3.3 OR MC 4.3Test purposeVerify that the IUT, in Outgoing Call Proceeding call state N3, having received aSETUP message, containing two HLCs, HLC1 and HLC2,is capable of sending a CONNECT message containing HLC2.Cross referenceCommentsSending of CONNECT following receipt of a SETUP, fallback from HLC2 toHLC1 allowed; the two HLCs are included in the SETUP message in ascendingorder of priority, i.e. HLC2 appears subsequent to HLC1: fallback did not occureither within the IUT or at the destination user.GTP111_08Reference to ETS 300 267-1 [3]:5.5.3.1, 5.6.3Other relevant reference:TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaMC 3.3 OR MC 4.3Test purposeVerify that the IUT, in Call Delivered call state N4, having received a SETUPmessage, containing two HLCs, HLC1 and HLC2,is capable of sending a CONNECT message containing HLC2.Cross referenceCommentsSending of CONNECT following receipt of a SETUP, fallback from HLC2 toHLC1 allowed; the two HLCs are included in the SETUP message in ascendingorder of priority, i.e. HLC2 appears subsequent to HLC1: fallback did not occureither within the IUT or at the destination user.SIST ETS 300 267-5:1998
Page 15Draft prETS 300 267-5: March 1997GTP111_09Reference to ETS 300 267-1 [3]:5.5.3.1, 5.6.3Other relevant reference:TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaMC 3.3 OR MC 4.3Test purposeVerify that the IUT, in Outgoing Call Proceeding call state N3, having received aSETUP message, containing two HLCs, HLC1 and HLC2,is capable of sending a CONNECT message containing HLC1.Cross referenceCommentsSending of CONNECT: fallback occurred, to HLC1, at the destination user.GTP111_10Reference to ETS 300 267-1 [3]:5.5.3.1, 5.6.3Other relevant reference:TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaMC 3.3 OR MC 4.3Test purposeVerify that the IUT, in Call Delivered call state N4, having received a SETUPmessage, containing two HLCs, HLC1 and HLC2,is capable of sending a CONNECT message containing HLC1.Cross referenceCommentsSending of CONNECT: fallback occurred, to HLC1, at the destination user.GTP111_11Reference to ETS 300 267-1 [3]:5.5.3.1, 5.6.3Other relevant reference:TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaMC 3.3 OR MC 4.3Test purposeVerify that the IUT, in Idle call state N0, on receipt of a SETUP messagecontaining two HLCs, HLC1 and HLC2,is capable of sending a CALL PROCEEDING, PROGRESS or ALERTINGmessage containing a PI=#5.Cross referenceCommentsSending of CALL PROCEEDING, PROGRESS or ALERTING: fallback occurred,to HLC1, within the IUT.GTP111_12Reference to ETS 300 267-1 [3]:5.5.3.1, 5.6.3Other relevant reference:TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaMC 3.3 OR MC 4.3Test purposeVerify that the IUT, in Idle call state N0, on receipt of a SETUP messagecontaining two HLCs, HLC1 and HLC2,is capable of sending a CALL PROCEEDING, PROGRESS or ALERTINGmessage containing a PI=#5 and HLC1.Cross referenceCommentsSending of CALL PROCEEDING, PROGRESS or ALERTING: fallback occurred,to HLC1, within the IUT.GTP111_13Reference to ETS 300 267-1 [3]:5.5.3.1, 5.6.3Other relevant reference:TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaMC 3.3 OR MC 4.3Test purposeVerify that the IUT, having received a SETUP message, containing two HLCs,HLC1 and HLC2, on sending a PROGRESS message containing a PI=#5,does not stop timers as described in ETS 300 102-1 [1].Cross referenceCommentsSending of PROGRESS: fallback occurred, to BC1, within the IUT.SIST ETS 300 267-5:1998
Page 16Draft prETS 300 267-5: March 1997GTP111_14Reference to ETS 300 267-1 [3]:5.5.5.1, 5.6.5.1Other relevant reference:TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteria(MC 3.1 OR MC 4.1)Test purposeVerify that the IUT, in Idle call state N0, on receipt of a SETUP message,containing two BCs, BC1 and BC2, and no LLC,performs a subscription check for the defined prime service by use of BC2and, if the subscription check is successful, accepts the call.Cross referenceCommentsAcceptance of call following successful optional subscription check based onBC2.GTP111_15Reference to ETS 300 267-1 [3]:5.5.5.1, 5.6.5.1Other relevant reference:TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteria(MC 3.1 OR MC 4.1)Test purposeVerify that the IUT, in Idle call state N0, on receipt of a SETUP message,containing two BCs, BC1 and BC2, and no LLC,performs a subscription check for the defined prime service by use of BC2and, if the subscription check is unsuccessful, releases the call with cause#57 "bearer capability not authorized".Cross referenceCommentsRelease of call following unsuccessful optional subscription check based onBC2.GTP111_16Reference to ETS 300 267-1 [3]:5.5.5.1, 5.6.5.1Other relevant reference:TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteria(MC 3.1 AND MC 3.3) OR (MC 4.1 AND MC 4.3)Test purposeVerify that the IUT, in Idle call state N0, on receipt of a SETUP message,containing two BCs, BC1 and BC2, and no LLC, and two HLCs, HLC1 andHLC2,performs a subscription check for the defined prime service by use of BC2and HLC2 and, if the subscription check is successful, accepts the call.Cross referenceCommentsAcceptance of call following successful optional subscription check based onBC2 and HLC2.GTP111_17Reference to ETS 300 267-1 [3]:5.5.5.1, 5.6.5.1Other relevant reference:TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteria(MC 3.1 AND MC 3.3) OR (MC 4.1 AND MC 4.3)Test purposeVerify that the IUT, in Idle call state N0, on receipt of a SETUP message,containing two BCs, BC1 and BC2, and no LLC, and two HLCs, HLC1 andHLC2,performs a subscription check for the defined prime service by use of BC2and HLC2 and, if the subscription check is unsuccessful, releases the callwith cause #57 "bearer capability not authorized".Cross referenceCommentsRelease of call following unsuccessful optional subscription check based on BC2and HLC2.SIST ETS 300 267-5:1998
Page 17Draft prETS 300 267-5: March 1997GTP111_18Reference to ETS 300 267-1 [3]:5.5.5.1, 5.6.5.1Other relevant reference:TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteria(MC 3.1 AND MC 3.3) OR (MC 4.1 AND MC 4.3)Test purposeVerify that the IUT,checks the applicability of supplementary services, for the prime serviceonly, at the originating interface.Cross referenceCommentsGTP111_19Reference to ETS 300 267-1 [3]:5.5.7, 5.6.7Other relevant reference:ETS 300 102-1 [1] 5.3.4.1TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaSC 5.1Test purposeVerify that the IUT, in Overlap Sending call state N2, having received a SETUPmessage, containing two BCs, BC1 and BC2, with one of them set to UDI/TA,and no LLC,is capable of sending a DISCONNECT message containing a PI=#8 andof simultaneously providing in-band tones and announcement in a 3,1 kHzmode, encoded according to CCITT Recommendation G.711 [6] A-law.Cross referenceCommentsGTP111_20Reference to ETS 300 267-1 [3]:5.5.7, 5.6.7Other relevant reference:ETS 300 102-1 [1] 5.3.4.1TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaSC 5.1Test purposeVerify that the IUT, in Outgoing Call Proceeding call state N3, having received aSETUP message, containing two BCs, BC1 and BC2, with one of them set toUDI/TA, and no LLC,is capable of sending a DISCONNECT message containing a PI=#8 andof simultaneously providing in-band tones and announcement in a 3,1 kHzmode, encoded according to CCITT Recommendation G.711 [6] A-law.Cross referenceCommentsGTP111_21Reference to ETS 300 267-1 [3]:5.5.7, 5.6.7Other relevant reference:ETS 300 102-1 [1] 5.1.3TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaSC 5.1Test purposeVerify that the IUT, in Idle call state N0, on receipt of a SETUP messagecontaining two BCs, BC1 and BC2, with one of them set to UDI/TA, and no LLC,but not containing any called number information,sends a SETUP ACKNOWLEDGE message, containing a PI=#8 and ofsimultaneously providing in-band tones and announcement in a 3,1 kHzmode, encoded according to CCITT Recommendation G.711 [6] A-law.Cross referenceCommentsSIST ETS 300 267-5:1998
Page 18Draft prETS 300 267-5: March 1997GTP111_22Reference to ETS 300 267-1 [3]:5.5.7, 5.6.7Other relevant reference:ETS 300 102-1 [1] 5.4TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaSC 5.1Test purposeVerify that the IUT, in Idle call state N0, having received a SETUP message,containing two BCs, BC1 and BC2, with one of them set to UDI/TA, no LLC witha sending complete indication,is capable of sending a PROGRESS or an ALERTING or a CALLPROCEEDING message, containing a PI=#8, and of simultaneouslyproviding in-band tones announcement in a 3,1 kHz mode, encodedaccording to CCITT Recommendation G.711 [6] A-law.Cross referenceCommentsGTP111_23Reference to ETS 300 267-1 [3]:5.5.7, 5.6.7Other relevant reference:ETS 300 102-1 [1] 5.3.4.1TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaSC 5.1Test purposeVerify that the IUT, in Overlap Sending call state N2, having received a SETUPmessage, containing two BCs, BC1 and BC2, with one of them set to UDI/TA ,no LLC, and two HLCs, HLC1 and HLC2,is capable of sending a DISCONNECT message containing a PI=#8 andof simultaneously providing in-band tones and announcement in a 3,1 kHzmode, encoded according to CCITT Recommendation G.711 [6] A-law.Cross referenceCommentsGTP111_24Reference to ETS 300 267-1 [3]:5.5.7, 5.6.7Other relevant reference:ETS 300 102-1 [1] 5.3.4.1TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaSC 5.1Test purposeVerify that the IUT, in Outgoing Call Proceeding call state N3, having received aSETUP message, containing two BCs, BC1 and BC2, with one of them set toUDI/TA , no LLC, and two HLCs, HLC1 and HLC2,is capable of sending a DISCONNECT message containing a PI=#8 andof simultaneously providing in-band tones and announcement in a 3,1 kHzmode, encoded according to CCITT Recommendation G.711 [6] A-law.Cross referenceCommentsGTP111_25Reference to ETS 300 267-1 [3]:5.5.7, 5.6.7Other relevant reference:ETS 300 102-1 [1] 5.1.3TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaSC 5.1Test purposeVerify that the IUT, in Idle call state N0, on receipt of a SETUP messagecontaining two BCs, BC1 and BC2, with one of them set to UDI/TA, no LLC, twoHLCs, HLC1 and HLC2, but not containing any called number information,sends a SETUP ACKNOWLEDGE message, containing a PI=#8 and ofsimultaneously providing in-band tones and announcement in a 3,1 kHzmode, encoded according to CCITT Recommendation G.711 [6] A-law.Cross referenceCommentsSIST ETS 300 267-5:1998
Page 19Draft prETS 300 267-5: March 1997GTP111_26Reference to ETS 300 267-1 [3]:5.5.7, 5.6.7Other relevant reference:ETS 300 102-1 [1] 5.4TSS referenceNT7V/ORIG/BV/GEN/FBASelection criteriaSC 5.1Test purposeVerify that the IUT, in Idle call state N0, having received a SETUP message,containing two BCs, BC1 and BC2, with one of them set to UDI/TA, no LLC, twoHLCs, HLC1 and HLC2, with a sending complete indication,is capable of sending a PROGRESS or an ALERTING or a CALLPROCEEDING message, containing a PI=#8, and of simultaneouslyproviding in-band tones announcement in a 3,1 kHz mode, encodedaccording to CCITT Recommendation G.711 [6] A-law.Cross referenceComments5.2.1.1.2Fallback not allowedGTP112_01Reference to ETS 300 267-1 [3]:5.5.7, 5.6.7Other relevant reference:ETS 300 102-1 [1] 5.3.4.1TSS referenceNT7V/ORIG/BV/GEN/FBNSelection criteriaSC 5.1Test purposeVerify that the IUT, in Overlap Sending call state N2, having received a SETUPmessage, containing a single BC=UDI/TA,is capable of sending a DISCONNECT message containing a PI=#8 andof simultaneously providing in-band tones and announcement in a 3,1 kHzmode, encoded according to CCITT Recommendation G.711 [6] A-law.Cross referenceCommentsGTP112_02Reference to ETS 300 267-1 [3]:5.5.7, 5.6.7Other relevant reference:ETS 300 102-1 [1] 5.3.4.1TSS referenceNT7V/ORIG/BV/GEN/FBNSelection criteriaSC 5.1Test purposeVerify that the IUT, in Outgoing Call Proceeding call state N3, having received aSETUP message, containing a single BC=UDI/TA,is capable of sending a DISCONNECT message containing a PI=#8 andof simultaneously providing in-band tones and announcement in a 3,1 kHzmode, encoded according to CCITT Recommendation G.711 [6] A-law.Cross referenceCommentsGTP112_03Reference to ETS 300 267-1 [3]:5.5.7, 5.6.7Other relevant reference:ETS 300 102-1 [1] 5.1.3TSS referenceNT7V/ORIG/BV/GEN/FBNSelection criteriaSC 5.1Test purposeVerify that the IUT, in Idle call state N0, on receipt of a SETUP messagecontaining a BC=UDI/TA, but not containing any called number information,sends a SETUP ACKNOWLEDGE message, containing a PI=#8 and ofsimultaneously providing in-band tones and announcement in a 3,1 kHzmode, encoded according to CCITT Recommendation G.711 [6] A-law.Cross referenceCommentsSIST ETS 300 267-5:1998
Page 20Draft prETS 300 267-5: March 1997GTP112_04Reference to ETS 300 267-1 [3]:5.5.7, 5.6.7Other relevant reference:ETS 300 102-1 [1] 5.4TSS referenceNT7V/ORIG/BV/GEN/FBNSelection criteriaSC 5.1Test purposeVerify that the IUT, in Idle call state N0, having received a SETUP message,containing a BC=UDI/TA with a sending complete indication,is capable of sending a PROGRESS or an ALERTING or a CALLPROCEEDING message, containing a PI=#8, and of simultaneouslyproviding in-band tones announcement in a 3,1 kHz mode, encodedaccording to CCITT Recommendation G.711 [6] A-law.Cross referenceCommentsGTP112_05Reference to ETS 300 267-1 [3]:5.5.7, 5.6.7Other relevant reference:ETS 300 102-1 [1] 5.3.4.1TSS referenceNT7V/ORIG/BV/GEN/FBNSelection criteriaSC 5.1Test purposeVerify that the IUT, in Overlap Sending call state N2, having received a SETUPmessage, a single BC=UDI/TA and a single HLC,is capable of sending a DISCONNECT message containing a PI=#8 andof simultaneously providing in-band tones and announcement in a 3,1 kHzmode, encoded according to CCITT Recommendation G.711 [6] A-law.Cross referenceCommentsGTP112_06Reference to ETS 300 267-1 [3]:5.5.7, 5.6.7Other relevant reference:ETS 300 102-1 [1] 5.3.4.1TSS referenceNT7V/ORIG/BV/GEN/FBNSelection criteriaSC 5.1Test purposeVerify that the IUT, in Outgoing Call Proceeding call state N3, having received aSETUP message, containing a single BC=UDI/TA and a single HLC,is capable of sending a DISCONNECT message containing a PI=#8 andof simultaneously providing in-band tones and announcement in a 3,1 kHzmode, encoded according to CCITT Recommendation G.711 [6] A-law.Cross referenceCommentsGTP112_07Reference to ETS 300 267-1 [3]:5.5.7, 5.6.7Other relevant reference:ETS 300 102-1 [1] 5.1.3TSS referenceNT7V/ORIG/BV/GEN/FBNSelection criteriaSC 5.1Test purposeVerify that the IUT, in Idle call state N0, on receipt of a SETUP messagecontaining a BC=UDI/TA and a single HLC, but not containing any called numberinformation,sends a SETUP ACKNOWLEDGE message, containing a PI=#8 and ofsimultaneously providing
...
SLOVENSKI STANDARD
01-december-1998
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL ,6'1 'DOMLQVNLVWRULWYL WHOHIRQLMD
N+]LQYLGHRWHOHIRQLMD3URWRNROGLJLWDOQHQDURþQLãNHVLJQDOL]DFLMHãW '66
GHO =JUDGEDSUHVNXãDOQHJDQL]DLQQDPHQSUHVNXãDQMD 766 73 6SHFLILNDFLMD
]DRPUHåMH
Integrated Services Digital Network (ISDN); Telephony 7 kHz and videotelephony
teleservices; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 5: Test
Suite Structure and Test Purposes (TSS&TP) specification for the network
Ta slovenski standard je istoveten z: ETS 300 267-5 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN ETS 300 267-5
TELECOMMUNICATION April 1998
STANDARD
Source: SPS Reference: DE/SPS-05048-5
ICS: 33.020
Key words: ISDN, DSS1, teleservice, 7 kHz, video, telephony, testing, TSS&TP, network
Integrated Services Digital Network (ISDN);
Telephony 7 kHz and videotelephony teleservices;
Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 5: Test Suite Structure and Test Purposes (TSS&TP)
specification for the network
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
Internet: secretariat@etsi.fr - http://www.etsi.fr - http://www.etsi.org
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
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 1998. All rights reserved.
Page 2
ETS 300 267-5: April 1998
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 3
ETS 300 267-5: April 1998
Contents
Foreword .5
Introduction.5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .8
3.1 Definitions .8
3.2 Abbreviations .9
4 Test Suite Structure (TSS) .10
4.1 First test group level.10
4.2 Second test group level .10
4.3 Third test group level .10
4.4 Fourth test group level .10
4.5 Fifth test group level.10
4.6 Sixth test group level.11
5 Test Purposes (TP).12
5.1 Test purpose format.12
5.2 Calling network interface.13
5.2.1 Valid behaviour.13
5.2.1.1 Generic requirements.13
5.2.1.1.1 Fallback allowed .13
5.2.1.1.2 Fallback not allowed .19
5.2.1.1.3 Connection management.21
5.2.1.2 Telephony 7 kHz teleservice.21
5.2.1.2.1 Fallback allowed .21
5.2.1.2.2 Fallback not allowed .26
5.2.1.2.3 Connection management.28
5.2.1.3 Videotelephony teleservice.28
5.2.1.3.1 Fallback allowed .28
5.2.1.3.2 Fallback not allowed .33
5.2.1.3.3 Connection management.35
5.2.2 Invalid behaviour .36
5.2.2.1 Generic requirements.36
5.2.2.1.1 Fallback allowed .36
5.3 Destination interface .36
5.3.1 Valid behaviour.36
5.3.1.1 Generic requirements.36
5.3.1.1.1 Fallback allowed .36
5.3.1.1.1.1 Requirements at the coincident S and
T reference point or for interworking
with private ISDNs .36
5.3.1.1.1.2 Requirements at the coincident S and
T reference point.39
5.3.1.1.1.3 Requirements for interworking with
private ISDNs.44
5.3.1.1.2 Fallback not allowed .44
5.3.1.1.3 Connection management.46
5.3.1.2 Telephony 7 kHz teleservice.47
5.3.1.2.1 Fallback allowed .47
5.3.1.2.1.1 Requirements at the coincident S and
T reference point or for interworking
with private ISDNs .47
Page 4
ETS 300 267-5: April 1998
5.3.1.2.1.2 Requirements for interworking with
private ISDNs . 50
5.3.1.2.2 Fallback not allowed. 51
5.3.1.2.3 Connection management. 52
5.3.1.3 Videotelephony teleservice . 52
5.3.1.3.1 Fallback allowed. 52
5.3.1.3.1.1 Requirements at the coincident S and
T reference point or for interworking
with private ISDNs. 52
5.3.1.3.1.2 Requirements at the coincident S and
T reference point. 57
5.3.1.3.1.3 Requirements for interworking with
private ISDNs . 59
5.3.1.3.2 Fallback not allowed. 60
5.3.1.3.3 Connection management. 61
5.3.2 Invalid behaviour. 62
5.3.2.1 Generic requirements . 62
5.3.2.1.1 Fallback allowed. 62
5.3.2.1.1.1 Requirements at the coincident S and
T reference point or for interworking
with private ISDNs. 62
5.3.2.1.1.2 Requirements at the coincident S and
T reference point. 63
5.3.2.1.1.3 Requirements for interworking with
private ISDNs . 64
5.3.2.2 Telephony 7 kHz teleservice. 69
5.3.2.2.1 Fallback allowed. 69
5.3.2.3 Videotelephony teleservice . 70
5.3.2.3.1 Fallback allowed. 70
5.3.3 Inopportune behaviour. 76
5.3.3.1 Generic requirements . 76
5.3.3.1.1 Fallback allowed. 76
6 Compliance. 78
Annex A (informative): Cross references: Generic, telephony 7 kHz and videotelephony teleservices
test purposes . 79
A.1 Generic test purposes to telephony 7 kHz and videotelephony teleservices test purposes. 79
A.2 Telephony 7 kHz to videotelephony teleservices test purposes . 82
History. 84
Page 5
ETS 300 267-5: April 1998
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 5 of a multi-part standard covering the Digital Subscriber Signalling System No. one
(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) telephony 7 kHz and
videotelephony teleservices, 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: 20 March 1998
Date of latest announcement of this ETS (doa): 31 July 1998
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 January 1999
Date of withdrawal of any conflicting National Standard (dow): 31 January 1999
Introduction
This ETS is divided into six clauses. Clauses 1 to 3 form the scope, references and abbreviations.
Clause 4 contains the test suite structure. Clause 5 contains the complete list of test purposes. Clause 6
contains the requirements for a generic or abstract test suite to comply with this ETS.
It is been assumed that the Implementation Under Test (IUT) already complies with the conformance
requirements associated with the ISDN basic call as defined in ETS 300 102-1. This is specified as a
requirement in ETS 300 267-2, clause 5. ETS 300 267-1, subclause 5.1, states that the additional generic
requirements of clause 5 are defined to be compatible with the existing requirements of ETS 300 102-1.
In cases where ETS 300 267-1 specifies that requirements in ETS 300 102-1 shall apply, it is assumed
that, because the IUT already complies with ETS 300 102-1, it also complies with these requirements.
However, when specifying the abstract test cases, including test case selection, the requirements of
ETS 300 102-1 need to be taken into account.
Page 6
ETS 300 267-5: April 1998
Blank page
Page 7
ETS 300 267-5: April 1998
1 Scope
This fifth part of ETS 300 267 is applicable to the stage three of the telephony 7 kHz and videotelephony
teleservices for the pan-European Integrated Services Digital Network (ISDN) as provided by European
public telecommunications operators at the T reference point or coincident S and T reference point (as
specified in ITU-T Recommendation I.411 [8] by means of the Digital Subscriber Signalling System
No. one (DSS1) protocol. ETS 300 267-1 [3] provides the protocol specification and ETS 300 267-2 [4] the
Protocol Implementation Conformance Statement (PICS) proforma specification. Stage three identifies the
protocol procedures and switching functions needed to support a telecommunications service (see CCITT
Recommendation I.130 [7]).
This ETS specifies the Test Suite Structure and Test Purposes (TSS&TP) for the network side. It covers
the protocol requirements as defined in ETS 300 267-1 [3] and provides test purposes for the additional
generic requirements for basic telecommunication services not defined in ETS 300 102-1 [1]
(ETS 300 267-1 [3], clause 5), for the telephony 7 kHz teleservice (ETS 300 267-1 [3], clause 6) and for
the videotelephony teleservice (ETS 300 267-1 [3], clause 7).
Two types of implementation are covered:
- an implementation which supports network requirements at the coincident S and T reference point;
- an implementation which supports network requirements for interworking with private ISDNs at the
T reference point.
2 Normative references
This ETS incorporates by dated or undated references, 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 102-1: "Integrated Services Digital Network (ISDN); User-network
interface layer 3; Specifications for basic call control".
[2] ETS 300 144: "Integrated Services Digital Network (ISDN); Audiovisual services;
Frame structure for a 64 kbit/s to 1 920 kbit/s channel and associated syntax for
inband signalling" (equivalent to ITU-T Recommendation H.221).
[3] ETS 300 267-1 (1994) including A1 (1996): "Integrated Services Digital Network
(ISDN); Telephony 7 kHz and videotelephony teleservices; Digital Subscriber
Signalling System No. one (DSS1) protocol; Part 1: Protocol specification".
[4] ETS 300 267-2 (1996): "Integrated Services Digital Network (ISDN); Telephony
7 kHz and videotelephony teleservices; Digital Subscriber Signalling System No.
one (DSS1) protocol; Part 2: Protocol Implementation Conformance Statement
(PICS) proforma specification".
[5] I-ETS 300 316: "Integrated Services Digital Network (ISDN); Digital Subscriber
Signalling System No. one (DSS1); Protocol Implementation Conformance
Statement (PICS) proforma specification for signalling network layer protocol for
circuit-mode basic call control (basic access, network)".
[6] CCITT Recommendation G.711 (1988): "Pulse code modulation (PCM) of voice
frequencies".
[7] CCITT Recommendation I.130 (1988): "Method for the characterization of
telecommunication services supported by an ISDN and network capabilities of
an ISDN".
[8] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces -
Reference configurations".
Page 8
ETS 300 267-5: April 1998
[9] ISO/IEC 9646-2: "Information technology - Open systems interconnection -
Conformance testing methodology and framework - Part 2: Abstract test suite
specification".
[10] ISO/IEC 9646-3: "Information technology - Open systems interconnection -
Conformance testing methodology and framework - Part 3: The Tree and
Tabular Combined Notation".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the definitions in ETS 300 267-1 [3] apply in addition to the following
definitions:
BC1: The first (lower priority) Bearer capability information element included in a SETUP message
allowing bearer capability selection.
BC2: The second (higher priority) Bearer capability information element included in a SETUP message
allowing bearer capability selection.
BC=speech: A Bearer capability information element with its information transfer capability field set to
"speech" and its user information layer one protocol field set to "G.711 A-law".
BC=UDI/TA: A Bearer capability information element with its information transfer capability field set to
"UDI/TA" and its user information layer one protocol field set to "Recommendations H.221 and H.242".
BC=UDI: A Bearer capability information element with its information transfer capability field set to "UDI"
and its user information layer one protocol field set to "Recommendations H.221 and H.242".
bit-rate allocation signal:
Bit position within the frame structure to transmit commands, control and
indication signals, capabilities.
HLC1: The first (lower priority) High layer compatibility information element in a SETUP message allowing
high layer compatibility selection.
HLC2: The second (higher priority) High layer compatibility information element in a SETUP message
allowing high layer compatibility selection.
HLC=telephony: A High layer compatibility information element with its high layer characteristics
identification field set to "telephony".
HLC=videotelephony_ic: A High layer compatibility information element with its high layer characteristics
identification field set to "110 0000 - videotelephony (Recommendation F.721)" and its extended
audiovisual characteristics identification field set to "000 0001 - capability set of initial channel of
Recommendation H.221".
HLC=videotelephony_nex: A High layer compatibility information element with its high layer
characteristics identification field set to "110 0000 - videotelephony (Recommendation F.721)" but not
containing an extended audiovisual characteristics identification field.
HLC=videotelephony_sc: A High layer compatibility information element with its high layer
characteristics identification field set to "110 0000 - videotelephony (Recommendation F.721)" and its
extended audiovisual characteristics identification field set to "000 0010 - capability set of subsequent
channel of Recommendation H.221".
Implementation Under Test (IUT): The component of the system under test (user terminal or private
ISDN) providing the protocol specified in ETS 300 267-1 [3] at the S/T or T reference point.
in-band signalling: Signalling via the bit-rate allocation signal of the frame structure, as defined in
ETS 300 144 [2].
Page 9
ETS 300 267-5: April 1998
mode 0F: Transmission mode in which the initial channel contains framing, and 7-bit G.711 audio signal
is being transmitted.
mode 0U: Transmission mode in which the initial channel does not contain framing, and 8-bit G.711 audio
signal is being transmitted.
PI=#1: A Progress indicator information element, with its progress description field set to #1 "Call is not
end-to-end ISDN".
PI=#2: A Progress indicator information element, with its progress description field set to #2 "Destination
address is non-ISDN".
PI=#3: A Progress indicator information element, with its progress description field set to #3 "Origination
address is non-ISDN".
PI=#4: A Progress indicator information element, with its progress description field set to #4 "Call has
returned to the ISDN".
PI=#5: A Progress indicator information element, with its progress description field set to #5 "interworking
has occurred and has resulted in a telecommunications service change".
PI=#8: A Progress indicator information element, with its progress description field set to #8 "In-band
information or appropriate pattern now available".
telephony 7 kHz fallback allowed SETUP message: A SETUP message containing two BCs, with the
first BC=speech and the second BC=UDI/TA, a HLC=telephony, and not containing a LLC.
telephony 7 kHz fallback not allowed SETUP message: A SETUP message containing a single
BC=UDI/TA and a single HLC=telephony, and not containing a LLC.
videotelephony fallback allowed SETUP message: A SETUP message containing two BCs, with the
first BC=speech and the second BC=UDI/TA, and two HLCs, with the first HLC=telephony and the second
HLC=videotelephony_ic, and not containing a LLC.
videotelephony fallback not allowed SETUP message: A SETUP message containing a single
BC=UDI/TA and a single HLC=videotelephony_ic, and not containing a LLC.
videotelephony SETUP message for CR2 : A SETUP message containing a single BC=UDI and a
single HLC=videotelephony_sc. The SETUP message is used to establish the second connection in a
videotelephony call requiring two connections.
3.2 Abbreviations
For the purposes of this ETS, the abbreviations in ETS 300 267-1 [3] and ETS 300 267-2 [4] apply. In
addition, the following abbreviations apply:
ATS Abstract Test Suite
BC Bearer Capability information element
CR1 Call Reference for the first call
CR2 Call Reference for the second call
HLC High Layer Compatibility information element
IUT Implementation Under Test
LLC Low Layer Compatibility information element
PI Progress Indicator information element
TP Test Purpose
TSS Test Suite Structure
UDI Unrestricted Digital Information
UDI/TA Unrestricted Digital Information with Tones/Announcements
Page 10
ETS 300 267-5: April 1998
4 Test Suite Structure (TSS)
The test suite is structured as a tree. Six test group levels are defined. The TSS is depicted in figure 1.
4.1 First test group level
The first test group level contains the name of the test suite:
NT7V Network side telephony 7 kHz, videotelephony teleservices and generic protocol.
4.2 Second test group level
The second test group level indicates whether the test purpose covers the originating interface or the
destination interface:
ORIG Originating Interface;
DEST Destination Interface.
4.3 Third test group level
The third test group level indicates whether the test purpose covers a requirement applicable to valid
behaviour, to invalid behaviour or to inopportune behaviour:
BV Valid Behaviour test purpose;
BI Invalid Behaviour test purpose;
BO inOpportune Behaviour test purpose.
4.4 Fourth test group level
The fourth test group level indicates whether the test purpose covers a requirement applicable to the
generic protocol, the telephony 7 kHz protocol, or the videotelephony teleservice protocol:
GEN Generic requirements. The test purpose covers a requirement applicable for the
generic part of ETS 300 267-1 [3] (clause 5);
TL7 Telephony 7 kHz teleservice. The test purpose covers a requirement applicable for the
telephony 7 kHz part of ETS 300 267-1 [3] (clause 6);
VTL Videotelephony teleservice. The test purpose covers a requirement applicable for the
videotelephony part of ETS 300 267-1 [3] (clause 7).
The group for generic requirements does not appear in the TSS. None of the generic test purposes can
be considered as testable.
4.5 Fifth test group level
The fifth test group level indicates which kind of functionality is tested and, more precisely, whether the
test purposes covers requirements applicable to fallback allowed, fallback not allowed or connection
management. Three groups are defined:
FBA FallBack Allowed: this group covers all tests where a fallback allowed SETUP
message is sent to the IUT;
FBN FallBack Not allowed: this group covers all tests where a fallback not allowed SETUP
message is sent to the IUT;
CMN Connection MaNagement: this group includes all other cases which do not test the
response to or the sending of a fallback allowed or a fallback not allowed SETUP
message. As a consequence, the clearing of a call and the establishment of a second
connection for videotelephony is tested here.
Page 11
ETS 300 267-5: April 1998
4.6 Sixth test group level
The sixth test group level indicates the type of implementation to which the test purpose applies:
ST An implementation which supports network requirements at the coincident S and
T reference point;
PT An implementation which supports network requirements for interworking with private
ISDNs at the T reference point;
ST_T An implementation which supports network requirements at the coincident S and
T reference point or network requirements for interworking with private ISDNs at the
T reference point.
This level group does not appear when only one of them is included as subgroup.
NT7V
ORIG (1) DEST (2)
ORIG (1)
BV (1)
BI (2)
GEN VTL GEN
TL7
FBA (1) FBN (2) CMN (3) FBA (1) FBN (2) CMN (3) FBA (1) FBN (2) CMN (3) FBA (1)
DEST (2)
BV (1) BO (3)
BI (2)
GEN TL7 VTL
GEN
GEN TL7 VTL
FBA (1)
FBN (2)CMN (3)
FBA (1)FBN (2)CMN (3) FBA (1) FBN (2)CMN (3) FBA (1) FBA (1) FBA (1) FBA (1)
ST_T ST PT
ST_T PT ST PT ST PT
ST_T ST_T
Figure 1: Test suite structure
Page 12
ETS 300 267-5: April 1998
5 Test Purposes (TP)
5.1 Test purpose format
The structure of a test purpose identifier is defined in table 1.
Table 1: TP identifier naming convention scheme
_
GTP generic protocol requirement
TTP telephony 7 kHz requirement
VTP videotelephony requirement
1st digit 1 Originating Interface; 2 Destination Interface
2nd digit 1 Valid; 2 Invalid; 3 Inopportune
3rd digit 1 Fallback Allowed; 2 Fallback Not Allowed; 3 Connection Management
2 digits sequential test case number
The test purposes are formatted as tables to increase readability. The table format is shown in table 2.
Text in bold shows the text which is always present, normal text provides an explanation for each field.
Table 2: Structure of a single TP
Test purpose identifier Reference to ETS 300 267-1 [3]: Other relevant reference:
TSS reference The full test suite structure reference.
Selection criteria The criteria necessary in order to select the test. Unless otherwise specified,
references are to ETS 300 267-2 [4].
Test purpose Description of the test purpose.
Cross reference GTP/TTP/VTP cross reference data.
Any relevant comments.
Comments
The "Other relevant reference" field, where applicable, contains a reference to a specification document
containing the whole, or part, of the requirement to be tested by the test purpose.
The "Selection criteria" field consists of a Boolean expression incorporating items from ETS 300 267-2 [4]
(in which case items are not prefixed by a reference number) and from I-ETS 300 316 [5].
Some of the telephony 7 kHz or videotelephony test purposes are directly related, but not identical, to
generic ones. Where such a relationship exists, the reference to the related generic test purpose is
specified in the "Cross reference" field of the telephony 7 kHz or videotelephony test purpose.
Untestable test purposes are listed using italic font. Test purposes for generic protocol requirements
which correspond to no particular IUT have been considered as untestable.
Page 13
ETS 300 267-5: April 1998
5.2 Calling network interface
5.2.1 Valid behaviour
5.2.1.1 Generic requirements
5.2.1.1.1 Fallback allowed
GTP111_01 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.1.1, 5.6.1
TSS reference NT7V/ORIG/BV/GEN/FBA
Selection criteria MC 3.1 OR MC 4.1
Verify that the IUT, in Outgoing Call Proceeding call state N3, having received a
Test purpose
SETUP message, containing two BCs, BC1 and BC2, and no LLC,
is capable of sending a CONNECT message containing BC2.
Cross reference
Comments Sending of CONNECT following receipt of a SETUP, fallback from BC2 to BC1
allowed; the two BCs are included in the SETUP message in ascending order of
priority, i.e. BC2 appears subsequent to BC1: fallback did not occur either within
the IUT or at the destination user.
GTP111_02 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.1.1, 5.6.1
TSS reference NT7V/ORIG/BV/GEN/FBA
Selection criteria MC 3.1 OR MC 4.1
Test purpose Verify that the IUT, in Call Delivered call state N4, having received a SETUP
message, containing two BCs, BC1 and BC2, and no LLC,
is capable of sending a CONNECT message containing BC2.
Cross reference
Comments Sending of CONNECT following receipt of a SETUP, fallback from BC2 to BC1
allowed; the two BCs are included in the SETUP message in ascending order of
priority, i.e. BC2 appears subsequent to BC1: fallback did not occur either within
the IUT or at the destination user.
GTP111_03 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.1.1, 5.6.1
TSS reference NT7V/ORIG/BV/GEN/FBA
MC 3.1 OR MC 4.1
Selection criteria
Test purpose Verify that the IUT, in Outgoing Call Proceeding call state N3, having received a
SETUP message, containing two BCs, BC1 and BC2, and no LLC,
is capable of sending a CONNECT message containing BC1.
Cross reference
Sending of CONNECT: fallback occurred, to BC1, at the destination user.
Comments
GTP111_04 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.1.1, 5.6.1
TSS reference NT7V/ORIG/BV/GEN/FBA
Selection criteria MC 3.1 OR MC 4.1
Verify that the IUT, in Call Delivered call state N4, having received a SETUP
Test purpose
message, containing two BCs, BC1 and BC2, and no LLC,
is capable of sending a CONNECT message containing BC1.
Cross reference
Comments Sending of CONNECT: fallback occurred, to BC1, at the destination user.
Page 14
ETS 300 267-5: April 1998
GTP111_05 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.1.1, 5.6.1
TSS reference NT7V/ORIG/BV/GEN/FBA
MC 3.1 OR MC 4.1
Selection criteria
Test purpose Verify that the IUT, in Idle call state N0, on receipt of a SETUP message
containing two BCs, BC1 and BC2, and no LLC,
is capable of sending a CALL PROCEEDING, PROGRESS or ALERTING
message containing a PI=#5 and BC1.
Cross reference
Comments Sending of CALL PROCEEDING, PROGRESS or ALERTING: fallback occurred,
to BC1, within the IUT.
GTP111_06 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.1.1, 5.6.1
TSS reference NT7V/ORIG/BV/GEN/FBA
Selection criteria MC 3.1 OR MC 4.1
Verify that the IUT, in Outgoing Call Proceeding call state N3, having received a
Test purpose
SETUP message, containing two BCs, BC1 and BC2, and no LLC, on sending a
PROGRESS message containing a PI=#5,
does not stop timers as described in ETS 300 102-1 [1].
Cross reference
Comments Sending of PROGRESS: fallback occurred, to BC1, within the IUT.
GTP111_07 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.3.1, 5.6.3
TSS reference NT7V/ORIG/BV/GEN/FBA
MC 3.3 OR MC 4.3
Selection criteria
Test purpose Verify that the IUT, in Outgoing Call Proceeding call state N3, having received a
SETUP message, containing two HLCs, HLC1 and HLC2,
is capable of sending a CONNECT message containing HLC2.
Cross reference
Sending of CONNECT following receipt of a SETUP, fallback from HLC2 to
Comments
HLC1 allowed; the two HLCs are included in the SETUP message in ascending
order of priority, i.e. HLC2 appears subsequent to HLC1: fallback did not occur
either within the IUT or at the destination user.
GTP111_08 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.3.1, 5.6.3
TSS reference NT7V/ORIG/BV/GEN/FBA
Selection criteria MC 3.3 OR MC 4.3
Test purpose Verify that the IUT, in Call Delivered call state N4, having received a SETUP
message, containing two HLCs, HLC1 and HLC2,
is capable of sending a CONNECT message containing HLC2.
Cross reference
Comments Sending of CONNECT following receipt of a SETUP, fallback from HLC2 to
HLC1 allowed; the two HLCs are included in the SETUP message in ascending
order of priority, i.e. HLC2 appears subsequent to HLC1: fallback did not occur
either within the IUT or at the destination user.
Page 15
ETS 300 267-5: April 1998
GTP111_09 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.3.1, 5.6.3
TSS reference NT7V/ORIG/BV/GEN/FBA
MC 3.3 OR MC 4.3
Selection criteria
Test purpose Verify that the IUT, in Outgoing Call Proceeding call state N3, having received a
SETUP message, containing two HLCs, HLC1 and HLC2,
is capable of sending a CONNECT message containing HLC1.
Cross reference
Sending of CONNECT: fallback occurred, to HLC1, at the destination user.
Comments
GTP111_10 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.3.1, 5.6.3
TSS reference NT7V/ORIG/BV/GEN/FBA
Selection criteria MC 3.3 OR MC 4.3
Test purpose Verify that the IUT, in Call Delivered call state N4, having received a SETUP
message, containing two HLCs, HLC1 and HLC2,
is capable of sending a CONNECT message containing HLC1.
Cross reference
Comments Sending of CONNECT: fallback occurred, to HLC1, at the destination user.
GTP111_11 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.3.1, 5.6.3
TSS reference NT7V/ORIG/BV/GEN/FBA
Selection criteria MC 3.3 OR MC 4.3
Verify that the IUT, in Idle call state N0, on receipt of a SETUP message
Test purpose
containing two HLCs, HLC1 and HLC2,
is capable of sending a CALL PROCEEDING, PROGRESS or ALERTING
message containing a PI=#5.
Cross reference
Sending of CALL PROCEEDING, PROGRESS or ALERTING: fallback occurred,
Comments
to HLC1, within the IUT.
GTP111_12 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.3.1, 5.6.3
TSS reference NT7V/ORIG/BV/GEN/FBA
Selection criteria MC 3.3 OR MC 4.3
Test purpose Verify that the IUT, in Idle call state N0, on receipt of a SETUP message
containing two HLCs, HLC1 and HLC2,
is capable of sending a CALL PROCEEDING, PROGRESS or ALERTING
message containing a PI=#5 and HLC1.
Cross reference
Comments Sending of CALL PROCEEDING, PROGRESS or ALERTING: fallback occurred,
to HLC1, within the IUT.
GTP111_13 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.3.1, 5.6.3
TSS reference NT7V/ORIG/BV/GEN/FBA
Selection criteria MC 3.3 OR MC 4.3
Test purpose Verify that the IUT, having received a SETUP message, containing two HLCs,
HLC1 and HLC2, on sending a PROGRESS message containing a PI=#5,
does not stop timers as described in ETS 300 102-1 [1].
Cross reference
Comments Sending of PROGRESS: fallback occurred, to BC1, within the IUT.
Page 16
ETS 300 267-5: April 1998
GTP111_14 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.5.1, 5.6.5.1
TSS reference NT7V/ORIG/BV/GEN/FBA
(MC 3.1 OR MC 4.1)
Selection criteria
Test purpose Verify that the IUT, in Idle call state N0, on receipt of a SETUP message,
containing two BCs, BC1 and BC2, and no LLC,
performs a subscription check for the defined prime service by use of BC2
and, if the subscription check is successful, accepts the call.
Cross reference
Comments Acceptance of call following successful optional subscription check based on
BC2.
GTP111_15 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.5.1, 5.6.5.1
TSS reference NT7V/ORIG/BV/GEN/FBA
Selection criteria (MC 3.1 OR MC 4.1)
Verify that the IUT, in Idle call state N0, on receipt of a SETUP message,
Test purpose
containing two BCs, BC1 and BC2, and no LLC,
performs a subscription check for the defined prime service by use of BC2
and, if the subscription check is unsuccessful, releases the call with cause
#57 "bearer capability not authorized".
Cross reference
Comments Release of call following unsuccessful optional subscription check based on
BC2.
GTP111_16 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.5.1, 5.6.5.1
TSS reference NT7V/ORIG/BV/GEN/FBA
(MC 3.1 AND MC 3.3) OR (MC 4.1 AND MC 4.3)
Selection criteria
Test purpose Verify that the IUT, in Idle call state N0, on receipt of a SETUP message,
containing two BCs, BC1 and BC2, and no LLC, and two HLCs, HLC1 and
HLC2,
performs a subscription check for the defined prime service by use of BC2
and HLC2 and, if the subscription check is successful, accepts the call.
Cross reference
Acceptance of call following successful optional subscription check based on
Comments
BC2 and HLC2.
GTP111_17 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.5.1, 5.6.5.1
TSS reference NT7V/ORIG/BV/GEN/FBA
(MC 3.1 AND MC 3.3) OR (MC 4.1 AND MC 4.3)
Selection criteria
Test purpose Verify that the IUT, in Idle call state N0, on receipt of a SETUP message,
containing two BCs, BC1 and BC2, and no LLC, and two HLCs, HLC1 and
HLC2,
performs a subscription check for the defined prime service by use of BC2
and HLC2 and, if the subscription check is unsuccessful, releases the call
with cause #57 "bearer capability not authorized".
Cross reference
Comments Release of call following unsuccessful optional subscription check based on BC2
and HLC2.
Page 17
ETS 300 267-5: April 1998
GTP111_18 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.5.1, 5.6.5.1
TSS reference NT7V/ORIG/BV/GEN/FBA
(MC 3.1 AND MC 3.3) OR (MC 4.1 AND MC 4.3)
Selection criteria
Test purpose Verify that the IUT,
checks the applicability of supplementary services, for the prime service
only, at the originating interface.
Cross reference
Comments
GTP111_19 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.7, 5.6.7 ETS 300 102-1 [1] 5.3.4.1
TSS reference NT7V/ORIG/BV/GEN/FBA
Selection criteria SC 5.1
Test purpose Verify that the IUT, in Overlap Sending call state N2, having received a SETUP
message, containing two BCs, BC1 and BC2, with one of them set to UDI/TA,
and no LLC,
is capable of sending a DISCONNECT message containing a PI=#8 and
of simultaneously providing in-band tones and announcement in a 3,1 kHz
mode, encoded according to CCITT Recommendation G.711 [6] A-law.
Cross reference
Comments
GTP111_20 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.7, 5.6.7 ETS 300 102-1 [1] 5.3.4.1
TSS reference NT7V/ORIG/BV/GEN/FBA
SC 5.1
Selection criteria
Test purpose Verify that the IUT, in Outgoing Call Proceeding call state N3, having received a
SETUP message, containing two BCs, BC1 and BC2, with one of them set to
UDI/TA, and no LLC,
is capable of sending a DISCONNECT message containing a PI=#8 and
of simultaneously providing in-band tones and announcement in a 3,1 kHz
mode, encoded according to CCITT Recommendation G.711 [6] A-law.
Cross reference
Comments
GTP111_21 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.7, 5.6.7 ETS 300 102-1 [1] 5.1.3
NT7V/ORIG/BV/GEN/FBA
TSS reference
Selection criteria SC 5.1
Test purpose Verify that the IUT, in Idle call state N0, on receipt of a SETUP message
containing two BCs, BC1 and BC2, with one of them set to UDI/TA, and no LLC,
but not containing any called number information,
sends a SETUP ACKNOWLEDGE message, containing a PI=#8 and of
simultaneously providing in-band tones and announcement in a 3,1 kHz
mode, encoded according to CCITT Recommendation G.711 [6] A-law.
Cross reference
Comments
Page 18
ETS 300 267-5: April 1998
GTP111_22 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.7, 5.6.7 ETS 300 102-1 [1] 5.4
TSS reference NT7V/ORIG/BV/GEN/FBA
SC 5.1
Selection criteria
Test purpose Verify that the IUT, in Idle call state N0, having received a SETUP message,
containing two BCs, BC1 and BC2, with one of them set to UDI/TA, no LLC with
a sending complete indication,
is capable of sending a PROGRESS or an ALERTING or a CALL
PROCEEDING message, containing a PI=#8, and of simultaneously
providing in-band tones announcement in a 3,1 kHz mode, encoded
according to CCITT Recommendation G.711 [6] A-law.
Cross reference
Comments
GTP111_23 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.7, 5.6.7 ETS 300 102-1 [1] 5.3.4.1
TSS reference NT7V/ORIG/BV/GEN/FBA
SC 5.1
Selection criteria
Test purpose Verify that the IUT, in Overlap Sending call state N2, having received a SETUP
message, containing two BCs, BC1 and BC2, with one of them set to UDI/TA ,
no LLC, and two HLCs, HLC1 and HLC2,
is capable of sending a DISCONNECT message containing a PI=#8 and
of simultaneously providing in-band tones and announcement in a 3,1 kHz
mode, encoded according to CCITT Recommendation G.711 [6] A-law.
Cross reference
Comments
GTP111_24 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.7, 5.6.7 ETS 300 102-1 [1] 5.3.4.1
TSS reference NT7V/ORIG/BV/GEN/FBA
Selection criteria SC 5.1
Test purpose Verify that the IUT, in Outgoing Call Proceeding call state N3, having received a
SETUP message, containing two BCs, BC1 and BC2, with one of them set to
UDI/TA , no LLC, and two HLCs, HLC1 and HLC2,
is capable of sending a DISCONNECT message containing a PI=#8 and
of simultaneously providing in-band tones and announcement in a 3,1 kHz
mode, encoded according to CCITT Recommendation G.711 [6] A-law.
Cross reference
Comments
GTP111_25 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.7, 5.6.7 ETS 300 102-1 [1] 5.1.3
NT7V/ORIG/BV/GEN/FBA
TSS reference
Selection criteria SC 5.1
Test purpose Verify that the IUT, in Idle call state N0, on receipt of a SETUP message
containing two BCs, BC1 and BC2, with one of them set to UDI/TA, no LLC, two
HLCs, HLC1 and HLC2, but not containing any called number information,
sends a SETUP ACKNOWLEDGE message, containing a PI=#8 and of
simultaneously providing in-band tones and announcement in a 3,1 kHz
mode, encoded according to CCITT Recommendation G.711 [6] A-law.
Cross reference
Comments
Page 19
ETS 300 267-5: April 1998
GTP111_26 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.7, 5.6.7 ETS 300 102-1 [1] 5.4
TSS reference NT7V/ORIG/BV/GEN/FBA
SC 5.1
Selection criteria
Test purpose Verify that the IUT, in Idle call state N0, having received a SETUP message,
containing two BCs, BC1 and BC2, with one of them set to UDI/TA, no LLC, two
HLCs, HLC1 and HLC2, with a sending complete indication,
is capable of sending a PROGRESS or an ALERTING or a CALL
PROCEEDING message, containing a PI=#8, and of simultaneously
providing in-band tones announcement in a 3,1 kHz mode, encoded
according to CCITT Recommendation G.711 [6] A-law.
Cross reference
Comments
5.2.1.1.2 Fallback not allowed
GTP112_01 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.7, 5.6.7 ETS 300 102-1 [1] 5.3.4.1
TSS reference NT7V/ORIG/BV/GEN/FBN
Selection criteria SC 5.1
Test purpose Verify that the IUT, in Overlap Sending call state N2, having received a SETUP
message, containing a single BC=UDI/TA,
is capable of sending a DISCONNECT message containing a PI=#8 and
of simultaneously providing in-band tones and announcement in a 3,1 kHz
mode, encoded according to CCITT Recommendation G.711 [6] A-law.
Cross reference
Comments
GTP112_02 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.7, 5.6.7 ETS 300 102-1 [1] 5.3.4.1
TSS reference NT7V/ORIG/BV/GEN/FBN
Selection criteria SC 5.1
Verify that the IUT, in Outgoing Call Proceeding call state N3, having received a
Test purpose
SETUP message, containing a single BC=UDI/TA,
is capable of sending a DISCONNECT message containing a PI=#8 and
of simultaneously providing in-band tones and announcement in a 3,1 kHz
mode, encoded according to CCITT Recommendation G.711 [6] A-law.
Cross reference
Comments
GTP112_03 Reference to ETS 300 267-1 [3]: Other relevant reference:
5.5.7, 5.6.7 ETS 300 102-1 [1] 5.1.3
NT7V/ORIG/BV/GEN/FBN
TSS reference
Selection criteria SC 5.1
Test purpose Verify that the IUT, in Idle call state N0, on
...