ETSI ETS 300 267-3 ed.1 (1997-05)
Integrated Services Digital Network (ISDN); Telephony 7 kHz and videotelephony teleservices; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user
Integrated Services Digital Network (ISDN); Telephony 7 kHz and videotelephony teleservices; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user
DE/SPS-05048-3
Digitalno omrežje z integriranimi storitvami (ISDN) - Daljinski storitvi: telefonija 7 kHz in videotelefonija - 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
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 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 267-3 E13SIST ETS 300 267-3:1998en01-DSULO-19983SIST ETS 300 267-3:1998SLOVENSKI
STANDARD
EUROPEANETS 300 267-3TELECOMMUNICATIONMay 1997STANDARDSource: ETSI TC-SPSReference: DE/SPS-05048-3ICS:33.020Key words:ISDN, DSS1, teleservice, 7 kHz, video, telephony, testing, TSS&TP, userIntegrated Services Digital Network (ISDN);Telephony 7 kHz and videotelephony teleservices;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: 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-3:1998
Page 2ETS 300 267-3: May 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-3:1998
Page 3ETS 300 267-3: May 1997ContentsForeword.7Introduction.71Scope.92Normative references.93Definitions and abbreviations.103.1Definitions.103.2Abbreviations.124Test Suite Structure (TSS).124.1First test group level.124.2Second test group level.124.3Third test group level.124.4Fourth test group level.124.5Fifth test group level.134.6Sixth test group level.145Test purposes for generic requirements, telephony 7 kHz and videotelephony teleservices.145.1Test purpose format.145.2Calling user interface.155.2.1Valid behaviour.155.2.1.1Generic requirements.155.2.1.1.1Fallback allowed.155.2.1.1.1.1User requirements at the coincident Sand T reference point or forinterworking with private ISDNs.155.2.1.1.1.2User requirements at the coincident Sand T reference point.165.2.1.1.2Fallback not allowed.185.2.1.1.2.1User requirements at the coincident Sand T reference point.185.2.1.1.2.2User requirements for interworkingwith private ISDNs.205.2.1.1.3Connection management.205.2.1.1.3.1User requirements at the coincident Sand T reference point or forinterworking with private ISDNs.205.2.1.1.3.2User requirements at the coincident Sand T reference point.215.2.1.2Telephony 7 kHz teleservice.215.2.1.2.1Fallback allowed.215.2.1.2.1.1User requirements at the coincident Sand T reference point or forinterworking with private ISDNs.215.2.1.2.1.2User requirements at the coincident Sand T reference point.235.2.1.2.2Fallback not allowed.265.2.1.2.2.1User requirements at the coincident Sand T reference point or forinterworking with private ISDNs.265.2.1.2.2.2User requirements at the coincident Sand T reference point.26SIST ETS 300 267-3:1998
Page 4ETS 300 267-3: May 19975.2.1.2.3Connection management.275.2.1.2.3.1User requirements at the coincident Sand T reference point.275.2.1.3Videotelephony teleservice.285.2.1.3.1Fallback allowed.285.2.1.3.1.1User requirements at the coincident Sand T reference point or forinterworking with private ISDNs.285.2.1.3.1.2User requirements at the coincident Sand T reference point.305.2.1.3.2Fallback not allowed.345.2.1.3.2.1User requirements at the coincident Sand T reference point or forinterworking with private ISDNs.345.2.1.3.2.2User requirements at the coincident Sand T reference point.345.2.1.3.3Connection management.355.2.1.3.3.1User requirements at the coincident Sand T reference point.355.2.1.3.3.2User requirements for interworkingwith private ISDNs.375.2.2Invalid behaviour.375.2.2.1Generic requirements.375.2.2.1.1Fallback allowed.375.2.2.1.1.1User requirements at the coincident Sand T reference point or forinterworking with private ISDNs.375.2.2.1.1.2User requirements at the coincident Sand T reference point.385.2.2.2Telephony 7 kHz teleservice.405.2.2.2.1Fallback allowed.405.2.2.2.1.1User requirements at the coincident Sand T reference point or forinterworking with private ISDNs.405.2.2.2.1.2User requirements at the coincident Sand T reference point.405.2.2.3Videotelephony teleservice.425.2.2.3.1Fallback allowed.425.2.2.3.1.1User requirements at the coincident Sand T reference point or forinterworking with private ISDNs.425.2.2.3.1.2User requirements at the coincident Sand T reference point.435.3Called user interface.455.3.1Valid behaviour.455.3.1.1Generic requirements.455.3.1.1.1Fallback allowed.455.3.1.1.1.1User requirements at the coincident Sand T reference point or forinterworking with private ISDNs.455.3.1.1.1.2User requirements at the coincident Sand T reference point.475.3.1.1.1.3User requirements for interworkingwith private ISDNs.475.3.1.1.2Fallback not allowed.485.3.1.1.2.1User requirements at the coincident Sand T reference point.485.3.1.1.2.2User requirements for interworkingwith private ISDNs.48SIST ETS 300 267-3:1998
Page 5ETS 300 267-3: May 19975.3.1.2Telephony 7 kHz teleservice.485.3.1.2.1Fallback allowed.485.3.1.2.1.1User requirements at the coincident Sand T reference point or forinterworking with private ISDNs.485.3.1.2.1.2User requirements at the coincident Sand T reference point.495.3.1.2.1.3User requirements for interworkingwith private ISDNs.505.3.1.2.2Fallback not allowed.505.3.1.2.2.1User requirements at the coincident Sand T reference point or forinterworking with private ISDNs.505.3.1.2.2.2User requirements at the coincident Sand T reference point.505.3.1.2.3Connection management.515.3.1.2.3.1User requirements at the coincident Sand T reference point.515.3.1.3Videotelephony teleservice.515.3.1.3.1Fallback allowed.515.3.1.3.1.1User requirements at the coincident Sand T reference point or forinterworking with private ISDNs.515.3.1.3.1.2User requirements at the coincident Sand T reference point.525.3.1.3.1.3User requirements for interworkingwith private ISDNs.535.3.1.3.2Fallback not allowed.545.3.1.3.2.1User requirements at the coincident Sand T reference point or forinterworking with private ISDNs.545.3.1.3.2.2User requirements at the coincident Sand T reference point.545.3.1.3.3Connection management.555.3.1.3.3.1User requirements at the coincident Sand T reference point.555.3.2Invalid behaviour.565.3.2.1Generic requirements.565.3.2.1.1Fallback allowed.565.3.2.1.1.1User requirements at the coincident Sand T reference point.565.3.3Inopportune behaviour.575.3.3.1Generic requirements.575.3.3.1.1Connection management.575.3.3.1.1.1User requirements at the coincident Sand T reference point or forinterworking with private ISDNs.576Combined test purposes for telephony 7 kHz and videotelephony teleservices.586.1Combined test purpose format.586.2Calling user interface.596.2.1Valid behaviour.596.2.1.1Telephony 7 kHz teleservice.596.2.1.1.1Fallback allowed.596.2.1.1.2Fallback not allowed.626.2.1.1.3Connection management.636.2.1.2Videotelephony teleservice.636.2.1.2.1Fallback allowed.636.2.1.2.2Fallback not allowed.676.2.1.2.3Connection management.686.2.2Invalid behaviour.716.2.2.1Telephony 7 kHz teleservice.716.2.2.1.1Fallback allowed.71SIST ETS 300 267-3:1998
Page 6ETS 300 267-3: May 19976.2.2.2Videotelephony teleservice.726.2.2.2.1Fallback allowed.726.3Called user interface.746.3.1Valid behaviour.746.3.1.1Telephony 7 kHz teleservice.746.3.1.1.1Fallback allowed.746.3.1.1.2Fallback not allowed.756.3.1.2Videotelephony teleservice.766.3.1.2.1Fallback allowed.766.3.1.2.2Fallback not allowed.796.3.1.2.3Connection management.797Compliance.79Annex A (informative):Cross reference: Generic, telephony 7 kHz and videotelephony teleservicestest purposes.81A.1Generic test purposes to telephony 7 kHz and videotelephony teleservices test purposes.81A.2Telephony 7 kHz to videotelephony teleservices test purposes.83History.85SIST ETS 300 267-3:1998
Page 7ETS 300 267-3: May 1997ForewordThis European Telecommunication Standard (ETS) has been produced by the Signalling Protocols andSwitching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).This ETS is part 3 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".Transposition datesDate of adoption:23 May 1997Date of latest announcement of this ETS (doa):31 August 1997Date of latest publication of new National Standardor endorsement of this ETS (dop/e):28 February 1998Date of withdrawal of any conflicting National Standard (dow):28 February 1998IntroductionThis ETS is divided into seven 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 list of combined test purposes, i.e. test purposes which can be tested together in one testcase. Clause 7 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 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.The following approach is adopted with regard to specifying test purposes:-resultant states of the IUT are not checked following receipt of messages which comply withETS 300 102-1. Resultant states of the IUT are checked following receipt of messages which donot comply with ETS 300 102-1, e.g. a CONNECT message which contains a Bearer capabilityinformation element;-for ETS 300 267-1, clause 5, the use of the word "assumes", in the case of an IUT at the originatinginterface, is interpreted as meaning that the IUT checks in-band: such test purposes are applicable,therefore, only to IUTs which contain in-band entities.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 inETS 300 102-1 need to be taken into account.SIST ETS 300 267-3:1998
Page 8ETS 300 267-3: May 1997Blank pageSIST ETS 300 267-3:1998
Page 9ETS 300 267-3: May 19971ScopeThis third 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 [11] by means of the Digital Subscriber Signalling SystemNo. one (DSS1) protocol. ETS 300 267-1 [5] provides the protocol specification and ETS 300 267-2 [6] 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 [10]).This ETS provides the Test Suite Structure and Test Purposes (TSS&TP) for the user side. It covers theprotocol requirements as defined in ETS 300 267-1 [5] and provides test purposes for the additionalgeneric requirements for basic telecommunication services not defined in ETS 300 102-1 [2](ETS 300 267-1 [5], clause 5), for the telephony 7 kHz teleservice (ETS 300 267-1 [5], clause 6) and forthe videotelephony teleservice (ETS 300 267-1 [5], clause 7).Two types of implementations are covered:-an implementation which supports user requirements at the coincident S and T reference point;-an implementation which supports user 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 082 (1992): "Integrated Services Digital Network (ISDN); 3,1 kHztelephony teleservice; End-to-end compatibility requirements for telephonyterminals".[2]ETS 300 102-1: "Integrated Services Digital Network (ISDN); User-networkinterface layer 3; Specifications for basic call control".[3]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).[4]ETS 300 145: "Integrated Services Digital Network (ISDN); Audiovisual services;Videotelephone systems and terminal equipment operating on one or two64 kbit/s channels".[5]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".[6]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".[7]I-ETS 300 281: "Integrated Services Digital Network (ISDN); Telephony 7 kHzteleservice; Terminal requirements necessary for end-to-end compatibility".SIST ETS 300 267-3:1998
Page 10ETS 300 267-3: May 1997[8]I-ETS 300 314: "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, user)".[9]CCITT Recommendation G.711 (1988): "Pulse code modulation (PCM) of voicefrequencies".[10]CCITT Recommendation I.130 (1988): "Method for the characterization oftelecommunication services supported by an ISDN and network capabilities ofan ISDN".[11]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces -Reference configurations".[12]ISO/IEC 9646-2: "Information technology - Open systems interconnection -Conformance testing methodology and framework - Part 2: Abstract test suitespecification".[13]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 [5] 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".SIST ETS 300 267-3:1998
Page 11ETS 300 267-3: May 1997HLC=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 [5] 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 [3].mode 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.SIST ETS 300 267-3:1998
Page 12ETS 300 267-3: May 19973.2AbbreviationsFor the purposes of this ETS, the following abbreviations apply:ATSAbstract Test SuiteBCBearer Capability information elementCR1Call Reference for the first callCR2Call Reference for the second callCR3Call Reference for the third callHLCHigh Layer Compatibility information elementIUTImplementation Under TestLLCLow Layer Compatibility information elementPIProgress Indicator information elementTPTest PurposeTSSTest Suite StructureUDIUnrestricted Digital InformationUDI/TAUnrestricted Digital Information with Tones/AnnouncementsFor TSS specific abbreviations, see clause 4.4Test 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:UT7VUser side telephony 7 kHz, videotelephony teleservices and generic protocol.4.2Second test group levelThe second test group level indicates whether the IUT is the calling or the called terminal:ORIGCalling User Interface;DESTCalled User 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 [5] (clause 5);TL7Telephony 7 kHz teleservice. The test purpose covers a requirement applicable for thetelephony 7 kHz part of ETS 300 267-1 [5] (clause 6);VTLVideotelephony teleservice. The test purpose covers a requirement applicable for thevideotelephony part of ETS 300 267-1 [5] (clause 7).The group for generic requirements does not appear in the TSS of the combined test purposes. None ofthe generic test purposes can be considered as testable.SIST ETS 300 267-3:1998
Page 13ETS 300 267-3: May 19974.5Fifth test group levelThe fifth test group level indicates which kind of functionality is tested and, more precisely, whether thetest purposes cover 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. UT7V(1)(2)GENTL7BVCMN (3) BOST_TBISTVTLFBA (1)FBN (2)CMN (3)STST_TSTST_TSTPTFBN (2)ST_TSTFBA (1)CMN (3)STFBN (2)FBA (1)ST_TSTPTSTPTDEST(2)BVORIG(1)GENTL7VTLST_TSTFBA (1)ST_TSTFBA (1)BI
FBA (1)VTLFBA (1)FBN (2)ST_TSTST_TSTCMN (3)STPTFBN (2)ST_TSTFBA (1)CMN (3)STTL7ST_TSTGENFBN (2)CMN (3)STPTSTST_TFBA (1)ST_TSTPTORIGDESTGENGENFBA (1)STST_TST_TSTFigure 1: Test suite structureSIST ETS 300 267-3:1998
Page 14ETS 300 267-3: May 19974.6Sixth test group levelThe sixth test group level indicates the type of implementation to which the test purpose applies:STAn implementation which supports user requirements at the coincident S andT reference point;PTAn implementation which supports user requirements for interworking with privateISDNs at the T reference point;ST_TAn implementation which supports user requirements at the coincident S andT reference point or user requirements for interworking with private ISDNs at theT reference point.The TSS for combined test purposes, described in clause 6, neither contains groups that include onlyuntestable test purposes nor the sixth test group level due to the fact that combined test purposes containcombinations of both ST, ST_T and PT test purposes.5Test purposes for generic requirements, telephony 7 kHz and video-telephony teleservices5.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 [5]: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 [6].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 [6](in which case items are not prefixed by a reference number) and from I-ETS 300 314 [8].SIST ETS 300 267-3:1998
Page 15ETS 300 267-3: May 1997Some 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. Test purposes which test anunframed mode in the B-channel or an internal behaviour of the IUT have also been considered asuntestable.5.2Calling user interface5.2.1Valid behaviour5.2.1.1Generic requirements5.2.1.1.1Fallback allowed5.2.1.1.1.1User requirements at the coincident S and T reference point or for interworkingwith private ISDNsGTP111_01Reference to ETS 300 267-1 [5]:5.6.1, 5.5.1.1, 5.3 a)Other relevant reference:TSS referenceUT7V/ORIG/BV/GEN /FBA/ST_TSelection criteriaMC 1.1 OR MC 2.1Test purposeVerify that the IUT, in the Null call state U0, when initiating a call, sends aSETUP message containing two BCs, BC1 and BC2 in ascending order ofpriority, and not containing LLC.Cross referenceCommentsSending of SETUP, fallback from BC2 to BC1 allowed: the two BCs are includedin the SETUP message in ascending order of priority, i.e. BC2 appearssubsequent to BC1. The reference to 5.3 a), is included because of the omissionfrom 5.5.1.1 of the requirement that, where the BC is repeated in the SETUPmessage, the inclusion of the LLC shall not occur.GTP111_02Reference to ETS 300 267-1 [5]:5.6.1, 5.5.1.1Other relevant reference:ETS 300 102-1 [2] 5.1.6TSS referenceUT7V/ORIG/BV/GEN/FBA /ST_TSelection criteria(MC 1.1 OR MC 2.1) AND NOT MC 1.1 [6] AND TM 4 [6] Test purposeVerify that the IUT, in the Overlap Sending call state U2, having sent a SETUPmessage containing two BCs, BC1 and BC2, and no LLC, on receipt of aPROGRESS message, containing PI=#5, does not stop optional timer T304.Cross referenceCommentsReceipt of PROGRESS: fallback allowed and occurred in the network.The IUT has to wait T304 (30 s) for DISCONNECT as defined inETS 300 102-1 [2]GTP111_03Reference to ETS 300 267-1 [5]:5.6.1, 5.5.1.1Other relevant reference:ETS 300 102-1 [2] 5.1.6TSS referenceUT7V/ORIG/BV/GEN/FBA /ST_TSelection criteria(MC 1.1 OR MC 2.1) AND TM 10 [6] Test purposeVerify that the IUT, in the Outgoing Call Proceeding call state U3, having sent aSETUP message containing two BCs, BC1 and BC2, and no LLC, on receipt of aPROGRESS message, containing PI=#5, does not stop optional timer T310.Cross referenceCommentsReceipt of PROGRESS: fallback allowed and occurred in the network.The IUT has to wait T310 (more than 40 sec) for DISCONNECT as defined inETS 300 102-1 [2]SIST ETS 300 267-3:1998
Page 16ETS 300 267-3: May 1997GTP111_04Reference to ETS 300 267-1 [5]:5.6.3, 5.5.3.1Other relevant reference:TSS referenceUT7V/ORIG/BV/GEN/FBA/ST_TSelection criteriaMC 1.3 OR MC 2.3Test purposeVerify that the IUT, in the Null call state U0, when initiating a call, sends aSETUP message containing two HLCs, HLC1 and HLC2 in ascending order ofpriority.Cross referenceCommentsSending of SETUP, fallback from HLC2 to HLC1 allowed: the two HLCs areincluded in the SETUP message in ascending order of priority, i.e. HLC2 appearssubsequent to HLC1.GTP111_05Reference to ETS 300 267-1 [5]:5.6.3, 5.5.3.1Other relevant reference:ETS 300 102-1 [2] 5.1.6TSS referenceUT7V/ORIG/BV/GEN/FBA/ST_TSelection criteria(MC 1.3 OR MC 2.3) AND NOT MC 1.1 [6] AND TM 4 [6]Test purposeVerify that the IUT, in the Overlap Sending call state U2, having sent a SETUPmessage containing two HLCs, HLC1 and HLC2, on receipt of a PROGRESSmessage, containing PI=#5, does not stop optional timer T304.Cross referenceCommentsReceipt of PROGRESS: fallback allowed and occurred in the network.The IUT has to wait T304 before DISCONNECT as defined in ETS 300 102-1 [2]GTP111_06Reference to ETS 300 267-1 [5]:5.6.3, 5.5.3.1Other relevant reference:ETS 300 102-1 [2] 5.1.6TSS referenceUT7V/ORIG/BV/GEN/FBA/ST_TSelection criteria(MC 1.3 OR MC 2.3) AND TM 10 [6]Test purposeVerify that the IUT, in the Outgoing Call Proceeding call state U3, having sent aSETUP message containing two HLCs, HLC1 and HLC2, on receipt of aPROGRESS message, containing PI=#5, does not stop optional timer T310.Cross referenceCommentsReceipt of PROGRESS: fallback allowed and occurred in the network.The IUT has to wait T310 before DISCONNECT as defined in ETS 300 102-1 [2]5.2.1.1.1.2User requirements at the coincident S and T reference pointGTP111_07Reference to ETS 300 267-1 [5]:5.5.1.2 b)Other relevant reference:ETS 300 102-1 [2] 5.1.6TSS referenceUT7V/ORIG/BV/GEN/FBA/STSelection criteriaR 3.1 AND MC 1.1Test purposeVerify that the IUT, in the Call Initiated call state U1, having sent a SETUPmessage containing two BCs, BC1 and BC2, and no LLC, on receipt of PI=#1 inPROGRESS message, subsequent to receiving PI=#5 in a CALL PROCEEDINGmessage, assumes fallback to a bearer service category of circuit mode 64 kbit/s8 kHz structured usable for 3,1 kHz audio information transfer in the B-channel.Cross referenceCommentsFallback allowed and occurred, to the bearer service category, circuit-mode64 kbit/s 8 kHz structured usable for 3,1 kHz audio information transfer, in thenetwork.SIST ETS 300 267-3:1998
Page 17ETS 300 267-3: May 1997GTP111_08Reference to ETS 300 267-1 [5]:5.5.1.2 b)Other relevant reference:ETS 300 102-1 [2] 5.1.6TSS referenceUT7V/ORIG/BV/GEN/ FBA/STSelection criteriaR 3.1 AND MC 1.1Test purposeVerify that the IUT, in the Call Initiated call state U1, having sent a SETUPmessage containing two BCs, BC1 and BC2, and no LLC, on receipt of PI=#2 inPROGRESS message, subsequent to receiving PI=#5 in a CALL PROCEEDINGmessage, assumes fallback to a bearer service category of circuit mode 64 kbit/s8 kHz structured usable for 3,1 kHz audio information transfer in the B-channel.Cross referenceCommentsFallback allowed and occurred, to the bearer service category, circuit-mode64 kbit/s 8 kHz structured usable for 3,1 kHz audio information transfer, in thenetwork.GTP111_09Reference to ETS 300 267-1 [5]:5.6.3, 5.5.3.2 b)Other relevant reference:TSS referenceUT7V/ORIG/BV/GEN/FBA/STSelection criteriaR 3.1 AND MC 1.3Test purposeVerify that the IUT, in the Call Initiated call state U1, having sent a SETUPmessage containing two HLCs, HLC1 and HLC2, on receipt of PI=#1 in aPROGRESS message, subsequent to receiving PI=#5 in a CALL PROCEEDINGmessage, assumes fallback to a bearer service category of circuit mode 64 kbit/s8 kHz structured usable for 3,1 kHz audio information transfer in the B-channel.Cross referenceCommentsFallback allowed and occurred, to the bearer service category, circuit-mode64 kbit/s 8 kHz structured usable for 3,1 kHz audio information transfer, in thenetwork.GTP111_10Reference to ETS 300 267-1 [5]:5.6.3, 5.5.3.2 b)Other relevant reference:TSS referenceUT7V/ORIG/BV/GEN/FBA/STSelection criteriaR 3.1 AND MC 1.3Test purposeVerify that the IUT, in the Call Initiated call state U1, having sent a SETUPmessage containing two HLCs, HLC1 and HLC2, on receipt of PI=#2 in aPROGRESS message, subsequent to receiving PI=#5 in a CALL PROCEEDINGmessage, assumes fallback to a bearer service category of circuit mode 64 kbit/s8 kHz structured usable for 3,1 kHz audio information transfer in the B-channel.Cross referenceCommentsFallback allowed and occurred, to the bearer service category, circuit-mode64 kbit/s 8 kHz structured usable for 3,1 kHz audio information transfer, in thenetwork.GTP111_11Reference to ETS 300 267-1 [5]:5.5.7Other relevant reference:TSS referenceUT7V/ORIG/BV/GEN/FBA/STSelection criteriaR 3.1 AND MC 1.1Test purposeVerify that the IUT, in the Outgoing Call Proceeding call state U3, having sent aSETUP message, containing two BCs, with the second (higher priority)BC=UDI/TA, on receipt of tones and announcements from the network, presentsthe tones and announcements to the user.Cross referenceCommentsTones and announcements received from the network are as specified in CCITTRecommendation G.711 [9].Tones and announcements sent to the user are as specified in ETS 300 082 [1],clause 6.SIST ETS 300 267-3:1998
Page 18ETS 300 267-3: May 19975.2.1.1.2Fallback not allowed5.2.1.1.2.1User requirements at the coincident S and T reference pointGTP112_01Reference to ETS 300 267-1 [5]:5.5.7Other relevant reference:ETS 300 102-1 [2] 5.1.3TSS referenceUT7V/ORIG/BV/GEN/FBN/STSelection criteriaR 3.1 AND MC 1.2 [6]Test purposeVerify that the IUT, in the Call Initiated call state U1, having sent a SETUPmessage containing BC=UDI/TA and an incomplete sending indication, onreceipt of a SETUP ACKNOWLEDGE message, which includes PI=#8, attachesto the B-channel.Cross referenceCommentsGTP112_02Reference to ETS 300 267-1 [5]:5.5.7Other relevant reference:ETS 300 102-1 [2] 5.1.7TSS referenceUT7V/ORIG/BV/GEN/FBN/STSelection criteriaR 3.1 AND MT 5 AND (NOT MC 1.7 [6])Test purposeVerify that an IUT, in the Call Initiated call state U1, having sent a SETUPmessage containing BC=UDI/TA, and not having attached to the B-channel, onreceipt of an ALERTING message, attaches to the B-channel and initiates aninternally generated alerting indication.Cross referenceCommentsGTP112_03Reference to ETS 300 267-1 [5]:5.5.7Other relevant reference:ETS 300 102-1 [2] 5.1.7TSS referenceUT7V/ORIG/BV/GEN/FBN/STSelection criteriaR 3.1 AND MT 5 AND (NOT MC 1.7 [6])Test purposeVerify that an IUT, in the Outgoing Call Proceeding call state U3, having sent aSETUP message containing BC=UDI/TA, and not having attached to theB-channel, on receipt of an ALERTING message, attaches to the B-channel andinitiates an internally generated alerting indication.Cross referenceCommentsGTP112_04Reference to ETS 300 267-1 [5]:5.5.7Other relevant reference:ETS 300 102-1 [2] 5.1.6TSS referenceUT7V/ORIG/BV/GEN/FBN/STSelection criteriaR 3.1 AND MC 1.2 [6]Test purposeVerify that the IUT, in the Call Initiated call state U1, having sent a SETUPmessage containing BC=UDI/TA and an incomplete sending indication, and nothaving attached to the B-channel, on receipt of a SETUP ACKNOWLEDGEmessage containing PI=#1, attaches to, and monitors, the B-channel for furtherin-band information.Cross referenceCommentsSIST ETS 300 267-3:1998
Page 19ETS 300 267-3: May 1997GTP112_05Reference to ETS 300 267-1 [5]:5.5.7Other relevant reference:ETS 300 102-1 [2] 5.1.6TSS referenceUT7V/ORIG/BV/GEN/FBN/STSelection criteriaR 3.1 AND MT 5Test purposeVerify that the IUT, in the Call Initiated call state U1, having sent a SETUPmessage containing BC=UDI/TA, and not having attached to the B-channel, onreceipt of a CALL PROCEEDING message containing PI=#1, attaches to, andmonitors, the B-channel for further in-band information.Cross referenceCommentsGTP112_06Reference to ETS 300 267-1 [5]:5.5.7Other relevant reference:ETS 300 102-1 [2] 5.1.6TSS referenceUT7V/ORIG/BV/GEN/FBN/STSelection criteriaR 3.1 AND MT 5Test purposeVerify that the IUT, in the Outgoing Call Proceeding call state U3, having sent aSETUP message containing BC=UDI/TA, and not having attached to theB-channel, on receipt of an ALERTING message containing PI=#1, attaches to,and monitors, the B-channel for further in-band information.Cross referenceCommentsGTP112_07Reference to ETS 300 267-1 [5]:5.5.7Other relevant reference:ETS 300 102-1 [2] 5.1.6TSS referenceUT7V/ORIG/BV/GEN/FBN/STSelection criteriaR 3.1 AND MT 5Test purposeVerify that the IUT, in the Call Delivered call state U4, having sent a SETUPmessage containing BC=UDI/TA, and not having attached to the B-channel, onreceipt of an PROGRESS message containing PI=#1, attaches to, and monitors,the B-channel for further in-band information.Cross referenceCommentsGTP112_08Reference to ETS 300 267-1 [5]:5.5.7Other relevant reference:TSS referenceUT7V/ORIG/BV/GEN/FBN/STSelection criteriaR 3.1 AND MT 5Test purposeVerify that the IUT, in the Outgoing Call Proceeding call state U3, having sent aSETUP message, containing a single BC=UDI/TA, on receipt
...
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
]DXSRUDEQLND
Integrated Services Digital Network (ISDN); Telephony 7 kHz and videotelephony
teleservices; 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 267-3 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-3
TELECOMMUNICATION May 1997
STANDARD
Source: ETSI TC-SPS Reference: DE/SPS-05048-3
ICS: 33.020
Key words: ISDN, DSS1, teleservice, 7 kHz, video, telephony, testing, TSS&TP, user
Integrated Services Digital Network (ISDN);
Telephony 7 kHz and videotelephony teleservices;
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: secretariat@etsi.fr
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 1997. All rights reserved.
Page 2
ETS 300 267-3: May 1997
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-3: May 1997
Contents
Foreword .7
Introduction.7
1 Scope .9
2 Normative references.9
3 Definitions and abbreviations .10
3.1 Definitions .10
3.2 Abbreviations .12
4 Test Suite Structure (TSS) .12
4.1 First test group level.12
4.2 Second test group level .12
4.3 Third test group level .12
4.4 Fourth test group level .12
4.5 Fifth test group level.13
4.6 Sixth test group level.14
5 Test purposes for generic requirements, telephony 7 kHz and videotelephony teleservices .14
5.1 Test purpose format.14
5.2 Calling user interface .15
5.2.1 Valid behaviour.15
5.2.1.1 Generic requirements.15
5.2.1.1.1 Fallback allowed .15
5.2.1.1.1.1 User requirements at the coincident S
and T reference point or for
interworking with private ISDNs.15
5.2.1.1.1.2 User requirements at the coincident S
and T reference point.16
5.2.1.1.2 Fallback not allowed .18
5.2.1.1.2.1 User requirements at the coincident S
and T reference point.18
5.2.1.1.2.2 User requirements for interworking
with private ISDNs .20
5.2.1.1.3 Connection management.20
5.2.1.1.3.1 User requirements at the coincident S
and T reference point or for
interworking with private ISDNs.20
5.2.1.1.3.2 User requirements at the coincident S
and T reference point.21
5.2.1.2 Telephony 7 kHz teleservice.21
5.2.1.2.1 Fallback allowed .21
5.2.1.2.1.1 User requirements at the coincident S
and T reference point or for
interworking with private ISDNs.21
5.2.1.2.1.2 User requirements at the coincident S
and T reference point.23
5.2.1.2.2 Fallback not allowed .26
5.2.1.2.2.1 User requirements at the coincident S
and T reference point or for
interworking with private ISDNs.26
5.2.1.2.2.2 User requirements at the coincident S
and T reference point.26
Page 4
ETS 300 267-3: May 1997
5.2.1.2.3 Connection management. 27
5.2.1.2.3.1 User requirements at the coincident S
and T reference point. 27
5.2.1.3 Videotelephony teleservice . 28
5.2.1.3.1 Fallback allowed. 28
5.2.1.3.1.1 User requirements at the coincident S
and T reference point or for
interworking with private ISDNs . 28
5.2.1.3.1.2 User requirements at the coincident S
and T reference point. 30
5.2.1.3.2 Fallback not allowed. 34
5.2.1.3.2.1 User requirements at the coincident S
and T reference point or for
interworking with private ISDNs . 34
5.2.1.3.2.2 User requirements at the coincident S
and T reference point. 34
5.2.1.3.3 Connection management. 35
5.2.1.3.3.1 User requirements at the coincident S
and T reference point. 35
5.2.1.3.3.2 User requirements for interworking
with private ISDNs. 37
5.2.2 Invalid behaviour. 37
5.2.2.1 Generic requirements . 37
5.2.2.1.1 Fallback allowed. 37
5.2.2.1.1.1 User requirements at the coincident S
and T reference point or for
interworking with private ISDNs . 37
5.2.2.1.1.2 User requirements at the coincident S
and T reference point. 38
5.2.2.2 Telephony 7 kHz teleservice. 40
5.2.2.2.1 Fallback allowed. 40
5.2.2.2.1.1 User requirements at the coincident S
and T reference point or for
interworking with private ISDNs . 40
5.2.2.2.1.2 User requirements at the coincident S
and T reference point. 40
5.2.2.3 Videotelephony teleservice . 42
5.2.2.3.1 Fallback allowed. 42
5.2.2.3.1.1 User requirements at the coincident S
and T reference point or for
interworking with private ISDNs . 42
5.2.2.3.1.2 User requirements at the coincident S
and T reference point. 43
5.3 Called user interface . 45
5.3.1 Valid behaviour . 45
5.3.1.1 Generic requirements . 45
5.3.1.1.1 Fallback allowed. 45
5.3.1.1.1.1 User requirements at the coincident S
and T reference point or for
interworking with private ISDNs . 45
5.3.1.1.1.2 User requirements at the coincident S
and T reference point. 47
5.3.1.1.1.3 User requirements for interworking
with private ISDNs. 47
5.3.1.1.2 Fallback not allowed. 48
5.3.1.1.2.1 User requirements at the coincident S
and T reference point. 48
5.3.1.1.2.2 User requirements for interworking
with private ISDNs. 48
Page 5
ETS 300 267-3: May 1997
5.3.1.2 Telephony 7 kHz teleservice.48
5.3.1.2.1 Fallback allowed .48
5.3.1.2.1.1 User requirements at the coincident S
and T reference point or for
interworking with private ISDNs.48
5.3.1.2.1.2 User requirements at the coincident S
and T reference point.49
5.3.1.2.1.3 User requirements for interworking
with private ISDNs .50
5.3.1.2.2 Fallback not allowed .50
5.3.1.2.2.1 User requirements at the coincident S
and T reference point or for
interworking with private ISDNs.50
5.3.1.2.2.2 User requirements at the coincident S
and T reference point.50
5.3.1.2.3 Connection management.51
5.3.1.2.3.1 User requirements at the coincident S
and T reference point.51
5.3.1.3 Videotelephony teleservice.51
5.3.1.3.1 Fallback allowed .51
5.3.1.3.1.1 User requirements at the coincident S
and T reference point or for
interworking with private ISDNs.51
5.3.1.3.1.2 User requirements at the coincident S
and T reference point.52
5.3.1.3.1.3 User requirements for interworking
with private ISDNs .53
5.3.1.3.2 Fallback not allowed .54
5.3.1.3.2.1 User requirements at the coincident S
and T reference point or for
interworking with private ISDNs.54
5.3.1.3.2.2 User requirements at the coincident S
and T reference point.54
5.3.1.3.3 Connection management.55
5.3.1.3.3.1 User requirements at the coincident S
and T reference point.55
5.3.2 Invalid behaviour .56
5.3.2.1 Generic requirements.56
5.3.2.1.1 Fallback allowed .56
5.3.2.1.1.1 User requirements at the coincident S
and T reference point.56
5.3.3 Inopportune behaviour .57
5.3.3.1 Generic requirements.57
5.3.3.1.1 Connection management.57
5.3.3.1.1.1 User requirements at the coincident S
and T reference point or for
interworking with private ISDNs.57
6 Combined test purposes for telephony 7 kHz and videotelephony teleservices .58
6.1 Combined test purpose format .58
6.2 Calling user interface .59
6.2.1 Valid behaviour.59
6.2.1.1 Telephony 7 kHz teleservice.59
6.2.1.1.1 Fallback allowed .59
6.2.1.1.2 Fallback not allowed .62
6.2.1.1.3 Connection management.63
6.2.1.2 Videotelephony teleservice.63
6.2.1.2.1 Fallback allowed .63
6.2.1.2.2 Fallback not allowed .67
6.2.1.2.3 Connection management.68
6.2.2 Invalid behaviour .71
6.2.2.1 Telephony 7 kHz teleservice.71
6.2.2.1.1 Fallback allowed .71
Page 6
ETS 300 267-3: May 1997
6.2.2.2 Videotelephony teleservice . 72
6.2.2.2.1 Fallback allowed. 72
6.3 Called user interface . 74
6.3.1 Valid behaviour . 74
6.3.1.1 Telephony 7 kHz teleservice. 74
6.3.1.1.1 Fallback allowed. 74
6.3.1.1.2 Fallback not allowed. 75
6.3.1.2 Videotelephony teleservice . 76
6.3.1.2.1 Fallback allowed. 76
6.3.1.2.2 Fallback not allowed. 79
6.3.1.2.3 Connection management. 79
7 Compliance. 79
Annex A (informative): Cross reference: Generic, telephony 7 kHz and videotelephony teleservices
test purposes . 81
A.1 Generic test purposes to telephony 7 kHz and videotelephony teleservices test purposes. 81
A.2 Telephony 7 kHz to videotelephony teleservices test purposes . 83
History. 85
Page 7
ETS 300 267-3: May 1997
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) 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: 23 May 1997
Date of latest announcement of this ETS (doa): 31 August 1997
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 28 February 1998
Date of withdrawal of any conflicting National Standard (dow): 28 February 1998
Introduction
This ETS is divided into seven 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 list of combined test purposes, i.e. test purposes which can be tested together in one test
case. Clause 7 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.
The following approach is adopted with regard to specifying test purposes:
- resultant states of the IUT are not checked following receipt of messages which comply with
ETS 300 102-1. Resultant states of the IUT are checked following receipt of messages which do
not comply with ETS 300 102-1, e.g. a CONNECT message which contains a Bearer capability
information element;
- for ETS 300 267-1, clause 5, the use of the word "assumes", in the case of an IUT at the originating
interface, is interpreted as meaning that the IUT checks in-band: such test purposes are applicable,
therefore, only to IUTs which contain in-band entities.
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 in
ETS 300 102-1 need to be taken into account.
Page 8
ETS 300 267-3: May 1997
Blank page
Page 9
ETS 300 267-3: May 1997
1 Scope
This third 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 [11] by means of the Digital Subscriber Signalling System
No. one (DSS1) protocol. ETS 300 267-1 [5] provides the protocol specification and ETS 300 267-2 [6] 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 [10]).
This ETS provides the Test Suite Structure and Test Purposes (TSS&TP) for the user side. It covers the
protocol requirements as defined in ETS 300 267-1 [5] and provides test purposes for the additional
generic requirements for basic telecommunication services not defined in ETS 300 102-1 [2]
(ETS 300 267-1 [5], clause 5), for the telephony 7 kHz teleservice (ETS 300 267-1 [5], clause 6) and for
the videotelephony teleservice (ETS 300 267-1 [5], clause 7).
Two types of implementations are covered:
- an implementation which supports user requirements at the coincident S and T reference point;
- an implementation which supports user 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 082 (1992): "Integrated Services Digital Network (ISDN); 3,1 kHz
telephony teleservice; End-to-end compatibility requirements for telephony
terminals".
[2] ETS 300 102-1: "Integrated Services Digital Network (ISDN); User-network
interface layer 3; Specifications for basic call control".
[3] 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).
[4] ETS 300 145: "Integrated Services Digital Network (ISDN); Audiovisual services;
Videotelephone systems and terminal equipment operating on one or two
64 kbit/s channels".
[5] 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".
[6] 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".
[7] I-ETS 300 281: "Integrated Services Digital Network (ISDN); Telephony 7 kHz
teleservice; Terminal requirements necessary for end-to-end compatibility".
Page 10
ETS 300 267-3: May 1997
[8] I-ETS 300 314: "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, user)".
[9] CCITT Recommendation G.711 (1988): "Pulse code modulation (PCM) of voice
frequencies".
[10] CCITT Recommendation I.130 (1988): "Method for the characterization of
telecommunication services supported by an ISDN and network capabilities of
an ISDN".
[11] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces -
Reference configurations".
[12] ISO/IEC 9646-2: "Information technology - Open systems interconnection -
Conformance testing methodology and framework - Part 2: Abstract test suite
specification".
[13] 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 [5] 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".
Page 11
ETS 300 267-3: May 1997
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 [5] 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 [3].
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.
Page 12
ETS 300 267-3: May 1997
3.2 Abbreviations
For the purposes of this ETS, 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
CR3 Call Reference for the third 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
For TSS specific abbreviations, see clause 4.
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:
UT7V User side telephony 7 kHz, videotelephony teleservices and generic protocol.
4.2 Second test group level
The second test group level indicates whether the IUT is the calling or the called terminal:
ORIG Calling User Interface;
DEST Called User 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 [5] (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 [5] (clause 6);
VTL Videotelephony teleservice. The test purpose covers a requirement applicable for the
videotelephony part of ETS 300 267-1 [5] (clause 7).
The group for generic requirements does not appear in the TSS of the combined test purposes. None of
the generic test purposes can be considered as testable.
Page 13
ETS 300 267-3: May 1997
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 cover 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.
UT7V
ORIG
DEST
(2)
(1)
ORIG (1)
BI
BV
GEN TL7 VTL GEN TL7 VTL
CMN (3) FBA (1) FBN (2) CMN (3) FBA (1) FBN (2) CMN (3) FBA (1) FBA (1) FBA (1)
FBA (1) FBN (2)
ST_T ST ST PT ST_T ST ST_T ST ST_T ST ST ST_T ST ST_T ST ST PT ST_T ST ST_T ST ST
ST_T
(2)
DEST
BI BO
BV
GEN
GEN
GEN TL7 VTL
FBN (2)
FBA (1) FBA (1) FBN (2) CMN (3) FBA (1) FBN (2) CMN (3) FBA (1) CMN (3)
ST_T ST PT ST PT ST_T ST PT ST_T ST ST ST_T ST PT ST_T ST ST ST ST_T
Figure 1: Test suite structure
Page 14
ETS 300 267-3: May 1997
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 user requirements at the coincident S and
T reference point;
PT An implementation which supports user requirements for interworking with private
ISDNs at the T reference point;
ST_T An implementation which supports user requirements at the coincident S and
T reference point or user requirements for interworking with private ISDNs at the
T reference point.
The TSS for combined test purposes, described in clause 6, neither contains groups that include only
untestable test purposes nor the sixth test group level due to the fact that combined test purposes contain
combinations of both ST, ST_T and PT test purposes.
5 Test purposes for generic requirements, telephony 7 kHz and video-
telephony teleservices
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 [5]: Other relevant reference:
The full test suite structure reference.
TSS reference
Selection criteria The criteria necessary in order to select the test. Unless otherwise specified,
references are to ETS 300 267-2 [6].
Test purpose Description of the test purpose.
Cross reference GTP/TTP/VTP cross reference data.
Comments Any relevant 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 [6]
(in which case items are not prefixed by a reference number) and from I-ETS 300 314 [8].
Page 15
ETS 300 267-3: May 1997
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. Test purposes which test an
unframed mode in the B-channel or an internal behaviour of the IUT have also been considered as
untestable.
5.2 Calling user interface
5.2.1 Valid behaviour
5.2.1.1 Generic requirements
5.2.1.1.1 Fallback allowed
5.2.1.1.1.1 User requirements at the coincident S and T reference point or for interworking
with private ISDNs
GTP111_01 Reference to ETS 300 267-1 [5]: Other relevant reference:
5.6.1, 5.5.1.1, 5.3 a)
UT7V/ORIG/BV/GEN /FBA/ST_T
TSS reference
Selection criteria MC 1.1 OR MC 2.1
Test purpose Verify that the IUT, in the Null call state U0, when initiating a call, sends a
SETUP message containing two BCs, BC1 and BC2 in ascending order of
priority, and not containing LLC.
Cross reference
Comments Sending of 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. The reference to 5.3 a), is included because of the omission
from 5.5.1.1 of the requirement that, where the BC is repeated in the SETUP
message, the inclusion of the LLC shall not occur.
GTP111_02 Reference to ETS 300 267-1 [5]: Other relevant reference:
5.6.1, 5.5.1.1 ETS 300 102-1 [2] 5.1.6
TSS reference UT7V/ORIG/BV/GEN/FBA /ST_T
(MC 1.1 OR MC 2.1) AND NOT MC 1.1 [6] AND TM 4 [6]
Selection criteria
Test purpose Verify that the IUT, in the Overlap Sending call state U2, having sent a SETUP
message containing two BCs, BC1 and BC2, and no LLC, on receipt of a
PROGRESS message, containing PI=#5, does not stop optional timer T304.
Cross reference
Receipt of PROGRESS: fallback allowed and occurred in the network.
Comments
The IUT has to wait T304 (30 s) for DISCONNECT as defined in
ETS 300 102-1 [2]
GTP111_03 Reference to ETS 300 267-1 [5]: Other relevant reference:
5.6.1, 5.5.1.1 ETS 300 102-1 [2] 5.1.6
TSS reference UT7V/ORIG/BV/GEN/FBA /ST_T
Selection criteria (MC 1.1 OR MC 2.1) AND TM 10 [6]
Verify that the IUT, in the Outgoing Call Proceeding call state U3, having sent a
Test purpose
SETUP message containing two BCs, BC1 and BC2, and no LLC, on receipt of a
PROGRESS message, containing PI=#5, does not stop optional timer T310.
Cross reference
Comments Receipt of PROGRESS: fallback allowed and occurred in the network.
The IUT has to wait T310 (more than 40 sec) for DISCONNECT as defined in
ETS 300 102-1 [2]
Page 16
ETS 300 267-3: May 1997
GTP111_04 Reference to ETS 300 267-1 [5]: Other relevant reference:
5.6.3, 5.5.3.1
TSS reference UT7V/ORIG/BV/GEN/FBA/ST_T
MC 1.3 OR MC 2.3
Selection criteria
Test purpose Verify that the IUT, in the Null call state U0, when initiating a call, sends a
SETUP message containing two HLCs, HLC1 and HLC2 in ascending order of
priority.
Cross reference
Sending of SETUP, fallback from HLC2 to HLC1 allowed: the two HLCs are
Comments
included in the SETUP message in ascending order of priority, i.e. HLC2 appears
subsequent to HLC1.
GTP111_05 Reference to ETS 300 267-1 [5]: Other relevant reference:
5.6.3, 5.5.3.1 ETS 300 102-1 [2] 5.1.6
TSS reference UT7V/ORIG/BV/GEN/FBA/ST_T
Selection criteria (MC 1.3 OR MC 2.3) AND NOT MC 1.1 [6] AND TM 4 [6]
Verify that the IUT, in the Overlap Sending call state U2, having sent a SETUP
Test purpose
message containing two HLCs, HLC1 and HLC2, on receipt of a PROGRESS
message, containing PI=#5, does not stop optional timer T304.
Cross reference
Comments Receipt of PROGRESS: fallback allowed and occurred in the network.
The IUT has to wait T304 before DISCONNECT as defined in ETS 300 102-1 [2]
GTP111_06 Reference to ETS 300 267-1 [5]: Other relevant reference:
5.6.3, 5.5.3.1 ETS 300 102-1 [2] 5.1.6
TSS reference UT7V/ORIG/BV/GEN/FBA/ST_T
Selection criteria (MC 1.3 OR MC 2.3) AND TM 10 [6]
Test purpose Verify that the IUT, in the Outgoing Call Proceeding call state U3, having sent a
SETUP message containing two HLCs, HLC1 and HLC2, on receipt of a
PROGRESS message, containing PI=#5, does not stop optional timer T310.
Cross reference
Comments Receipt of PROGRESS: fallback allowed and occurred in the network.
The IUT has to wait T310 before DISCONNECT as defined in ETS 300 102-1 [2]
5.2.1.1.1.2 User requirements at the coincident S and T reference point
GTP111_07 Reference to ETS 300 267-1 [5]: Other relevant reference:
5.5.1.2 b) ETS 300 102-1 [2] 5.1.6
UT7V/ORIG/BV/GEN/FBA/ST
TSS reference
Selection criteria R 3.1 AND MC 1.1
Test purpose Verify that the IUT, in the Call Initiated call state U1, having sent a SETUP
message containing two BCs, BC1 and BC2, and no LLC, on receipt of PI=#1 in
PROGRESS message, subsequent to receiving PI=#5 in a CALL PROCEEDING
message, assumes fallback to a bearer service category of circuit mode 64 kbit/s
8 kHz structured usable for 3,1 kHz audio information transfer in the B-channel.
Cross reference
Comments Fallback allowed and occurred, to the bearer service category, circuit-mode
64 kbit/s 8 kHz structured usable for 3,1 kHz audio information transfer, in the
network.
Page 17
ETS 300 267-3: May 1997
GTP111_08 Reference to ETS 300 267-1 [5]: Other relevant reference:
5.5.1.2 b) ETS 300 102-1 [2] 5.1.6
TSS reference UT7V/ORIG/BV/GEN/ FBA/ST
R 3.1 AND MC 1.1
Selection criteria
Test purpose Verify that the IUT, in the Call Initiated call state U1, having sent a SETUP
message containing two BCs, BC1 and BC2, and no LLC, on receipt of PI=#2 in
PROGRESS message, subsequent to receiving PI=#5 in a CALL PROCEEDING
message, assumes fallback to a bearer service category of circuit mode 64 kbit/s
8 kHz structured usable for 3,1 kHz audio information transfer in the B-channel.
Cross reference
Comments Fallback allowed and occurred, to the bearer service category, circuit-mode
64 kbit/s 8 kHz structured usable for 3,1 kHz audio information transfer, in the
network.
GTP111_09 Reference to ETS 300 267-1 [5]: Other relevant reference:
5.6.3, 5.5.3.2 b)
TSS reference UT7V/ORIG/BV/GEN/FBA/ST
Selection criteria R 3.1 AND MC 1.3
Test purpose Verify that the IUT, in the Call Initiated call state U1, having sent a SETUP
message containing two HLCs, HLC1 and HLC2, on receipt of PI=#1 in a
PROGRESS message, subsequent to receiving PI=#5 in a CALL PROCEEDING
message, assumes fallback to a bearer service category of circuit mode 64 kbit/s
8 kHz structured usable for 3,1 kHz audio information transfer in the B-channel.
Cross reference
Comments Fallback allowed and occurred, to the bearer service category, circuit-mode
64 kbit/s 8 kHz structured usable for 3,1 kHz audio information transfer, in the
network.
GTP111_10 Reference to ETS 300 267-1 [5]: Other relevant reference:
5.6.3, 5.5.3.2 b)
UT7V/ORIG/BV/GEN/FBA/ST
TSS reference
Selection criteria R 3.1 AND MC 1.3
Test purpose Verify that the IUT, in the Call Initiated call state U1, having sent a SETUP
message containing two HLCs, HLC1 and HLC2, on receipt of PI=#2 in a
PROGRESS message, subsequent to receiving PI=#5 in a CALL PROCEEDING
message, assumes fallback to a bearer service category of circuit mode 64 kbit/s
8 kHz structured usable for 3,1 kHz audio information transfer in the B-channel.
Cross reference
Comments Fallback allowed and occurred, to the bearer service category, circuit-mode
64 kbit/s 8 kHz structured usable for 3,1 kHz audio information transfer, in the
network.
GTP111_11 Reference to ETS 300 267-1 [5]: Other relevant reference:
5.5.7
TSS reference UT7V/ORIG/BV/GEN/FBA/ST
Selection criteria R 3.1 AND MC 1.1
Test purpose Verify that the IUT, in the Outgoing Call Proceeding call state U3, having sent a
SETUP message, containing two BCs, with the second (higher priority)
BC=UDI/TA, on receipt of tones and announcements from the network, presents
the tones and announcements to the user.
Cross reference
Comments Tones and announcements received from the network are as specified in CCITT
Recommendation G.711 [9].
Tones and announcements sent to the user are as specified in ETS 300 082 [1],
clause 6.
Page 18
ETS 300 267-3: May 1997
5.2.1.1.2 Fallback not allowed
5.2.1.1.2.1 User requirements at the coincident S and T reference point
GTP112_01 Reference to ETS 300 267-1 [5]: Other relevant reference:
5.5.7 ETS 300 102-1 [2] 5.1.3
TSS reference UT7V/ORIG/BV/GEN/FBN/ST
Selection criteria R 3.1 AND MC 1.2 [6]
Test purpose Verify that the IUT, in the Call Initiated call state U1, having sent a SETUP
message containing BC=UDI/TA and an incomplete sending indication, on
receipt of a SETUP ACKNOWLEDGE message, which includes PI=#8, attaches
to the B-channel.
Cross reference
Comments
GTP112_02 Reference to ETS 300 267-1 [5]: Other relevant reference:
5.5.7 ETS 300 102-1 [2] 5.1.7
TSS reference UT7V/ORIG/BV/GEN/FBN/ST
R 3.1 AND MT 5 AND (NOT MC 1.7 [6])
Selection criteria
Test purpose Verify that an IUT, in the Call Initiated call state U1, having sent a SETUP
message containing BC=UDI/TA, and not having attached to the B-channel, on
receipt of an ALERTING message, attaches to the B-channel and initiates an
internally generated alerting indication.
Cross reference
Comments
GTP112_03 Reference to ETS 300 267-1 [5]: Other relevant reference:
5.5.7 ETS 300 102-1 [2] 5.1.7
UT7V/ORIG/BV/GEN/FBN/ST
TSS reference
Selection criteria R 3.1 AND MT 5 AND (NOT MC 1.7 [6])
Test p
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...