SIST I-ETS 300 236 E1:2003
(Main)Terminal Equipment (TE); Syntax-based videotex protocol; Protocol Terminal conformance testing
- Abstract
Conformance testing (reference to PICS & abstract test suites) for the application layer protocol between terminal and access function.
- Status
- Published
- Publication Date
- 30-Nov-2003
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Dec-2003
- Due Date
- 01-Dec-2003
- Completion Date
- 01-Dec-2003
- Mandate
- T-149
SIST I-ETS 300 236 E1:2003 is the Slovenian adoption of ETSI I-ETS 300 236, an Interim European Telecommunication Standard for conformance testing of Terminal Equipment (TE) that uses the Syntax-based Videotex (SBV) protocol. It specifies an Abstract Test Suite (ATS), PICS and PIXIT guidance, and detailed test purposes for checking SBV protocol behavior between a terminal and the access function.
What does SIST I-ETS 300 236 E1:2003 specify?
SIST I-ETS 300 236 E1:2003 specifies conformance testing for Videotex terminals that use SBV as defined by ETS 300 223 or ETS 300 079. The standard is focused on protocol testing at layer 7, with special handling for ETS 300 079-based terminals and role-dependent test coverage.
Clause 1 sets the scope, Clause 2 lists the normative references, Clauses 3 and 4 define terms and abbreviations, Clauses 5 to 9 define the test suite, and Annexes A to L provide proformas, test purposes, state models, and related information.
| Annex | What it covers |
|---|---|
| A | SBV PICS Proforma |
| B | SBV PICS conditional expressions |
| C | SBV PICS optional types |
| D | SBV PIXIT proforma |
| E | SBV Test Purposes |
| F | SBV State Diagrams |
| G | SBV state tables |
| H | BIS for SBV over ISDN circuit switched DTE/DTE (ETS 300 079) |
| J | Scope of conformance testing of SBV Protocol |
| K | CTS-2 Triple-X conformance testing |
| L | Bibliography |
For ETS 300 079-based terminals, the standard says that tests for layers other than layer 7 are outside scope, and that some cases linked to services only defined in ETS 300 223 are to be de-selected when the standard is applied to ETS 300 079 terminals.
What are the key requirements of SIST I-ETS 300 236 E1:2003?
SIST I-ETS 300 236 E1:2003 is an ATS that follows ISO 9646-1, ISO 9646-2, ISO 9646-3 and ISO 9646-5. In practice, that means the test material is written as a formal conformance suite, and where there is any difference between the base standard and the test suite, the base standard takes precedence.
Test method and role coverage
The standard uses a remote method for conformance testing, so the test setup does not add requirements beyond the protocol standards themselves. That matters because implementers can check conformance without having to redesign the product for a special test mode.
Test cases are fully specified for the Terminal Function (TF) role, while only test purposes are given for the Access Function (AF) role. This is important for planning: a lab gets executable detail for TF behavior, but must derive the AF test cases from the stated purposes.
Conformance artifacts and declarations
Clause 6 defines the supporting TTCN declarations: test suite parameters, test case de-selection, variables, constants, Point of Control and Observation (PCO) declarations, Protocol Data Units (PDU), Abstract Service Primitives (ASPs), aliases, timers, user type definitions and user operator definitions. In practice, these are the building blocks a test environment needs to run the suite consistently.
Annex A is the Protocol Implementation Conformance Statement (PICS) proforma and Annex D is the Protocol Implementation eXtra Information for Testing (PIXIT) proforma. Together they capture what the implementation supports, what values it accepts or emits, and how the lab should configure and observe the System under Test (SUT).
Test structure and behavior classes
Clause 9 organizes the test case library by behavior class: Basic Interconnect Tests (BIT), Capability Tests (CA), Valid Behaviour (BV), Inopportune Behaviour (BI), and Invalid Behaviour (BO). The BV, BI and BO groups are further split into State Event Transitions (SE), Parameter Variations (PV), Encoding Variations (EV) and Parameter Combinations (PC).
That structure matters because it shows what the suite is checking in practice: normal state changes, supported options, parameter handling, encoding rules, unusual but allowed events, and clearly wrong inputs. A supplier can use that organization to see whether implementation defects are likely to appear in state handling, parameter processing or error handling.
SBV services and protocol elements
The suite covers the SBV service set through tests for elements such as SBV_Establish, SBV_Release, SBV_Reset, SBV_VTX_Data, SBV_Set_Param, SBV_Read_Param, SBV_Set_Read_Param, SBV_Param_Indication, SBV_TFI, SBV_TC_Error, SBV_Channel_Open, SBV_Channel_Close, SBV_Channel_Error, SBV_Begin_Application, SBV_End_Application, SBV_End_Immediate, SBV_TPD_Begin, SBV_TPD_End, SBV_DFK, SBV_Remote_Echo and SBV_Escape.
This matters because the suite does not just check one message type - it checks channel setup and release, parameter exchange, application selection, transparent processable data, function key handling, echo behavior and escape handling.
PICS, PIXIT and role-dependent options
Annex A classifies implementation capabilities and options, including initiator/responder capability, network capabilities, SBV services, SBV to BIS association options, PDUs and parameters. Annex D then asks the client to provide actual addressing, parameter values, timer values and procedural information for test execution.
That is important in practice because the abstract test suite is not run with generic values. The lab and client agree the values that the implementation can accept or is expected to produce, and the PIXIT records those choices.
What terms does SIST I-ETS 300 236 E1:2003 define?
- Abstract Test Suite (ATS) - a formal set of abstract test cases derived from test purposes and used to assess conformance.
- Protocol Implementation Conformance Statement (PICS) - the proforma where an implementation states which capabilities and options it supports.
- Protocol Implementation eXtra Information for Testing (PIXIT) - the proforma that supplies test-specific implementation data such as addresses, parameter values and timers.
- Implementation Under Test (IUT) - the implementation being examined by the test suite.
- Terminal Function (TF) - the SBV role used when the terminal originates communication or behaves as the terminal side of the exchange.
- Access Function (AF) - the SBV role used when the terminal accepts an incoming Establish request and acts as the access side.
- Bearer Independent Service (BIS) - the service abstraction used in the SBV protocol context and referenced in the testing of SBV over lower layers.
- Protocol Data Unit (PDU) - a protocol message unit exchanged during testing and defined through the test suite declarations.
Who uses SIST I-ETS 300 236 E1:2003?
SIST I-ETS 300 236 E1:2003 is used by terminal manufacturers, protocol implementers, conformance test laboratories, quality teams and buyers who need evidence of SBV support. It is relevant to Videotex terminal equipment, access functions and implementations that use SBV over the protocol arrangements referenced by ETS 300 223 or ETS 300 079.
In practice, a test lab uses it to build and run the ATS, a supplier uses it to prepare a PICS and PIXIT, and a quality manager uses it to check whether the product supports the required services, PDUs and parameter behavior. A buyer can use the listed capabilities and options to confirm that a device fits the intended Videotex deployment.
Which standards are used with SIST I-ETS 300 236 E1:2003?
- ETS 300 222 - gives the framework of Videotex terminal protocols.
- ETS 300 223 - provides the common end-to-end SBV protocols and is the main base standard for the SBV behavior tested here.
- ETS 300 079 - provides SBV end-to-end protocols for ISDN circuit mode DTE-DTE and is used for the ISDN-related scope in Annex H.
- ISO 9646-1, ISO 9646-2, ISO 9646-3, ISO 9646-5 - provide the conformance testing methodology, ATS specification rules, TTCN and laboratory/client requirements.
- CCITT Recommendation X.3 and CCITT Recommendation X.29 - support the packet assembly/disassembly and control information exchange used in the parameter and message handling.
- ETS 300 072, ETS 300 073, ETS 300 074, ETS 300 075 and ETS 300 076 - contribute the Videotex presentation layer syntax, transparent data, processable data and Terminal Facility Identifier (TFI) context.
- ETS 300 102-1 - supplies ISDN basic call control references.
- ISO 7498, ISO/TR 8509 and ISO/IEC 8208 - provide the OSI model, service conventions and X.25 packet level protocol background used by the definitions and procedures.
What does the SIST I-ETS 300 236 E1:2003 document contain?
SIST I-ETS 300 236 E1:2003 contains TTCN-style material for conformance testing, including declarations, constraints, shared test steps and a structured test case library. Clause 6 covers the objects used by the suite, Clause 7 defines constraints for ASPs, PDUs and structured types, and Clause 8 provides common preambles, postambles and other test steps.
The document also contains PICS and PIXIT proformas, which are the practical forms used to capture implementation capabilities and test setup data. Annex E gives test purposes, while Annex F and Annex G provide state diagrams and state tables for the SBV behavior that the tests exercise.
Annex H describes BIS usage for SBV over ISDN circuit switched DTE/DTE, and Annex K links the material to CTS-2 Triple-X conformance testing. Together, these parts show how to prepare the test, choose the right cases, and interpret the expected SBV behavior without reproducing the normative tables themselves.
Get Certified
Connect with accredited certification bodies for this standard
BSI Group
BSI (British Standards Institution) is the business standards company that helps organizations make excellence a habit.
NYCE
Mexican standards and certification body.
ANCE
Mexican certification and testing association.
Sponsored listings
Frequently Asked Questions
SIST I-ETS 300 236 E1:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Terminal Equipment (TE); Syntax-based videotex protocol; Protocol Terminal conformance testing". This standard covers: Conformance testing (reference to PICS & abstract test suites) for the application layer protocol between terminal and access function.
Conformance testing (reference to PICS & abstract test suites) for the application layer protocol between terminal and access function.
SIST I-ETS 300 236 E1:2003 is classified under the following ICS (International Classification for Standards) categories: 33.160.99 - Other audio, video and audiovisual equipment; 35.180 - IT Terminal and other peripheral equipment. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST I-ETS 300 236 E1:2003 is associated with the following European legislation: Standardization Mandates: T-149. 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 I-ETS 300 236 E1:2003 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)
SLOVENSKI STANDARD
01-december-2003
Terminalska oprema (TE) – Skladenjski protokol za Videotex – Preskušanje
skladnosti terminalov
Terminal Equipment (TE); Syntax-based videotex protocol; Protocol Terminal
conformance testing
Ta slovenski standard je istoveten z: I-ETS 300 236 Edition 1
ICS:
33.160.99 Druga avdio, video in Other audio, video and
avdiovizuelna oprema audiovisual equipment
35.180 Terminalska in druga IT Terminal and other
periferna oprema IT peripheral equipment
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
INTERIM
EUROPEAN I-ETS 300 236
TELECOMMUNICATION May 1993
STANDARD
Source: ETSI TC-TE Reference: DI/TE-01011
ICS: 33.020
Videotex
Key words:
Terminal Equipment (TE);
Syntax-based Videotex protocol
Terminal conformance testing
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - secretariat@etsi.fr
X.400: Internet:
Tel.: +33 92 94 42 00 - Fax: +33 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 1993. All rights reserved.
New presentation - see History box
Page 2
I-ETS 300 236: May 1993
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
I-ETS 300 236: May 1993
Contents
Foreword .11
1 Scope .13
2 Normative references.14
3 Definitions.15
4 Abbreviations.16
5 Test suite overview.17
5.1 Test suite structure .17
5.2 Test purposes .19
5.3 Method of conformance testing .19
5.3.1 SBV Protocol Data Unit (PDU) .19
5.3.2 Use of Bearer Independent Service (BIS).20
6 Declarations .21
6.1 Test Suite Parameters Declaration.21
6.2 Test Case De-Selection.25
6.3 Test Case Variables Declaration .25
6.4 Test Suite Constants Declaration .25
6.5 Test Suite Variables Declaration.25
6.6 Point Control and Observations (PCOs) declaration .26
6.7 PDUs declaration.26
6.7.1 PDU Type declaration .27
6.7.2 Structured Type Declaration.43
6.8 ASPs Declaration.46
6.9 Alias Declaration.51
6.10 Timers Declaration.53
6.11 User Type Definitions.54
6.12 User Operator Definitions .54
7 Constraint Declarations.55
7.1 Constraints declaration .55
7.1.1 ASP Constraints declaration .55
7.1.2 PDU Constraints Declaration .60
7.1.3 Structured Type Constraints declaration.185
8 Common Test Step Library .203
8.1 Preambles.203
8.2 Postambles .204
8.3 Other Test Steps.206
9 Test Case Library.208
9.1 Terminal Functions (TF) .208
9.1.1 TF/Basic Interconnect Tests (BIT) .208
9.1.2 TF/Capability Tests (CA).208
9.1.3 TF/Valid Behaviour Tests (BV).208
9.1.3.1 TF/BV - State Event Transitions (SE).208
9.1.3.1.1 SBV/TF/BV/SE - Kernel (KE).209
9.1.3.1.2 SBV/TF/BV/SE Comm. Channel
Management (CCM) .217
9.1.3.1.3 SBV/TF/BV/SE Application Services
(AS).223
Page 4
I-ETS 300 236: May 1993
9.1.3.1.4 SBV/TF/BV/SE Transparent
Processable Data (TPD) . 225
9.1.3.1.5 SBV/TF/BV/SE Define Function Keys
(DFK). 229
9.1.3.1.6 SBV/TF/BV/SE Remote Echo (RE). 229
9.1.3.1.7 SBV/TF/BV/SE Escape (ESC) . 230
9.1.3.2 TF/BV - Parameter Variations (PV). 231
9.1.3.2.1 TF/BV/PV Kernel (KE). 231
9.1.3.2.2 TF/BV/PV Communication Channel
Management (CCM). 245
9.1.3.2.3 TF/BV/PV Application Selections (AS)260
9.1.3.2.4 TF/BV/PV Transparent Processable
Data (TPD) . 263
9.1.3.2.5 TF/BV/PV Define Function Keys
(DFK). 266
9.1.3.2.6 TF/BV/PV Remote Echo (RE). 267
9.1.3.2.7 TF/BV/PV Escape (ESC) . 268
9.1.3.3 TF/BV - Encoding Variations (EV) . 270
9.1.3.4 TF/BV - Parameter Combinations (PC) . 270
9.1.3.4.1 TF/BV/PC Kernel (KE) . 270
9.1.3.4.2 TF/BV/PC Communication Channel
Management (CCM). 277
9.1.3.4.3 TF/BV/PC Application Selections (AS)284
9.1.3.4.4 TF/BV/PC Transparent Processable
Data (TPD) . 285
9.1.3.4.5 TF/BV/PC Define Function Keys
(DFK). 287
9.1.3.4.6 TF/BV/PC Escape (ESC) . 288
9.1.4 TF - Inopportune Behaviour (BI). 289
9.1.4.1 TF/BI - Test Event variation (TE) . 289
9.1.4.1.1 TF/BI/TE - Unsupported services. 289
9.1.4.1.2 TF/BI/TE - Other inopportune events. 292
9.1.4.2 TF/BI - Timing/Timer variation . 293
9.1.4.3 TF/BI - Parameter Value Variation (PV). 295
9.1.4.3.1 TF/BI/PV - Establishment service . 295
9.1.4.3.2 TF/BI/PV - X3 related services. 296
9.1.4.3.3 TF/BI/PV - Telematic Commands . 297
9.1.4.4 TF/BI - Parameter Combination (PC) . 301
9.1.4.4.1 TF/BI/PC - X.3 related services. 301
9.1.4.4.2 TF/BI/PC - Telematic Commands. 301
9.1.5 TF - Invalid Behaviour (BO). 302
9.1.5.1 TF/BO - Parameter Value Variation (PV). 302
9.1.5.1.1 TF/BO/PV - X.3 related services. 302
9.1.5.1.2 TF/BO/PV - Telematic Commands . 302
9.1.5.2 TF/BO - Encoding Variations (EV) . 308
9.1.5.2.1 TF/BO/EV - X.3 related services. 308
9.1.5.2.2 TF/BO/EV - Telematic Commands . 308
Annex A (normative): SBV PICS Proforma . 310
A.1 Classification. 310
A.2 PICS Proforma, identification of the implementation. 311
A.2.1 Guidance for completion . 311
A.2.2 Date. 311
A.2.3 Supplier details. 311
A.2.4 Implementation details . 311
A.2.5 Claimed compliance to standards. 311
A.3 PICS Proforma, capabilities and options . 312
A.3.1 Initiator/Responder capability . 312
A.3.2 Network Capabilities. 313
A.3.3 SBV Services . 313
Page 5
I-ETS 300 236: May 1993
A.3.4 SBV to BIS association options .313
A.3.5 PDUs.314
A.3.5.1 AF PDUs .314
A.3.5.1.1 AF PDUs/SBV_Establish.314
A.3.5.1.2 AF PDUs/SBV_Release .314
A.3.5.1.3 AF PDUs/SBV_Reset .314
A.3.5.1.4 AF PDUs/SBV_VTX_Data.314
A.3.5.1.5 AF PDUs/SBV_Set_Param .315
A.3.5.1.6 AF PDUs/SBV_Read_Param .315
A.3.5.1.7 AF PDUs/SBV_Set_Read_Param.315
A.3.5.1.8 AF PDUs/SBV_Param_Indication .315
A.3.5.1.9 AF PDUs/SBV_TFI .315
A.3.5.1.10 AF PDUs/SBV_TC_Error.315
A.3.5.1.11 AF PDUs/SBV_Channel_Open .316
A.3.5.1.12 AF PDUs/SBV_Channel_Close.316
A.3.5.1.13 AF PDUs/SBV_Channel_Error .316
A.3.5.1.14 AF PDUs/SBV_Begin_Application.316
A.3.5.1.15 AF PDUs/SBV_End_Application.316
A.3.5.1.16 AF PDUs/SBV_End_Immediate .316
A.3.5.1.17 AF PDUs/SBV_TPD_Begin .317
A.3.5.1.18 AF PDUs/SBV_TPD_End.317
A.3.5.1.19 AF PDUs/SBV_DFK .317
A.3.5.1.20 AF PDUs/SBV_Remote_Echo.317
A.3.5.1.21 AF PDUs/SBV_Escape.317
A.3.5.2 TF PDUs.318
A.3.5.2.1 TF PDUs/SBV_Establish .318
A.3.5.2.2 TF PDUs/SBV_Release .318
A.3.5.2.3 TF PDUs/SBV_Reset .318
A.3.5.2.4 TF PDUs/SBV_VTX_Data.318
A.3.5.2.5 TF PDUs/SBV_Set_Param.318
A.3.5.2.6 TF PDUs/SBV_Read_Param .319
A.3.5.2.7 TF PDUs/SBV_Set_Read_Param.319
A.3.5.2.8 TF PDUs/SBV_Param_Indication.319
A.3.5.2.9 TF PDUs/SBV_TFI .319
A.3.5.2.10 TF PDUs/SBV_TC_Error.319
A.3.5.2.11 TF PDUs/SBV_Channel_Open .319
A.3.5.2.12 TF PDUs/SBV_Channel_Close .320
A.3.5.2.13 TF PDUs/SBV_Channel_Error .320
A.3.5.2.14 TF PDUs/SBV_Begin_Application.320
A.3.5.2.15 TF PDUs/SBV_End_Application.320
A.3.5.2.16 TF PDUs/SBV_End_Immediate .320
A.3.5.2.17 TF PDUs/SBV_TPD_Begin .320
A.3.5.2.18 TF PDUs/SBV_TPD_End .321
A.3.5.2.19 TF PDUs/SBV_DFK .321
A.3.5.2.20 TF PDUs/SBV_Remote_Echo.321
A.3.5.2.21 TF PDUs/SBV_Escape.321
A.3.6 Parameters .321
A.3.6.1 AF Parameters .322
A.3.6.1.1 AF Parameters/SBV_Establish Request .322
A.3.6.1.2 AF Parameters/SBV_Establish Response .322
A.3.6.1.3 AF Parameters/SBV_Release Request.323
A.3.6.1.4 AF Parameters/SBV_Reset Request .323
A.3.6.1.5 AF Parameters/SBV_Reset Response.323
A.3.6.1.6 AF Parameters/SBV_VTX_Data Request .323
A.3.6.1.7 AF Parameters/SBV_Set_Param Request.324
A.3.6.1.8 AF Parameters/SBV_Read_Param Request.324
A.3.6.1.9 AF Parameters/SBV_Set_Read_Param Request .324
A.3.6.1.10 AF Parameters/SBV_Param_Ind Request .324
A.3.6.1.11 AF Parameters/SBV_TFI Request .324
A.3.6.1.12 AF Parameters/SBV_TFI Response.324
A.3.6.1.13 AF Parameters/SBV_TC_Error Request.325
A.3.6.1.14 AF Parameters/SBV_Channel_Open Request.325
A.3.6.1.15 AF Parameters/SBV_Channel_Open Response.325
Page 6
I-ETS 300 236: May 1993
A.3.6.1.16 AF Parameters/SBV_Channel_Close Request. 326
A.3.6.1.17 AF Parameters/SBV_Channel_Close Response. 326
A.3.6.1.18 AF Parameters/SBV_Channel_Error Request. 326
A.3.6.1.19 AF Parameters/SBV_Begin_Application Request . 326
A.3.6.1.20 AF Parameters/SBV_Begin_Application Response. 326
A.3.6.1.21 AF Parameters/SBV_End_Application Request . 327
A.3.6.1.22 AF Parameters/SBV_End_Immediate Request. 327
A.3.6.1.23 AF Parameters/SBV_TPD_Begin Request. 327
A.3.6.1.24 AF Parameters/SBV_TPD_Begin Response. 327
A.3.6.1.25 AF Parameters/SBV_TPD_End Request. 327
A.3.6.1.26 AF Parameters/SBV_DFK Request. 327
A.3.6.1.27 AF Parameters/SBV_Remote_Echo Request . 327
A.3.6.1.28 AF Parameters/SBV_Escape Request . 328
A.3.6.2 TF Parameters. 328
A.3.6.2.1 TF Parameters/SBV_Establish Request. 328
A.3.6.2.2 TF Parameters/SBV_Establish Response. 329
A.3.6.2.3 TF Parameters/SBV_Release Request . 329
A.3.6.2.4 TF Parameters/SBV_Reset Request. 329
A.3.6.2.5 TF Parameters/SBV_Reset Response . 329
A.3.6.2.6 TF Parameters/SBV_VTX_Data Request. 330
A.3.6.2.7 TF Parameters/SBV_Set_Param Request . 330
A.3.6.2.8 TF Parameters/SBV_Read_Param Request . 330
A.3.6.2.9 TF Parameters/SBV_Set_Read_Param Request. 330
A.3.6.2.10 TF Parameters/SBV_Param_Ind Request. 330
A.3.6.2.11 TF Parameters/SBV_TFI Request. 331
A.3.6.2.12 TF Parameters/SBV_TFI Response . 331
A.3.6.2.13 TF Parameters/SBV_TC_Error Request . 331
A.3.6.2.14 TF Parameters/SBV_Channel_Open Request . 332
A.3.6.2.15 TF Parameters/SBV_Channel_Open Response . 332
A.3.6.2.16 TF Parameters/SBV_Channel_Close Request. 332
A.3.6.2.17 TF Parameters/SBV_Channel_Close Response. 332
A.3.6.2.18 TF Parameters/SBV_Channel_Error Request. 333
A.3.6.2.19 TF Parameters/SBV_Begin_Application Request. 333
A.3.6.2.20 TF Parameters/SBV_Begin_Application Response. 333
A.3.6.2.21 TF Parameters/SBV_End_Application Request . 333
A.3.6.2.22 TF Parameters/SBV_End_Immediate Request. 333
A.3.6.2.23 TF Parameters/SBV_TPD_Begin Request. 333
A.3.6.2.24 TF Parameters/SBV_TPD_Begin Response . 333
A.3.6.2.25 TF Parameters/SBV_TPD_End Request. 334
A.3.6.2.26 TF Parameters/SBV_DFK Request . 334
A.3.6.2.27 AF Parameters/SBV_Remote_Echo Request . 334
A.3.6.2.28 TF Parameters/SBV_Escape Request . 334
A.3.6.3 X.3 Parameters. 334
A.3.6.3.1 X.3 Parameters/send . 335
A.3.6.3.2 X.3 Parameters/receive . 335
Annex B (normative): SBV PICS conditional expressions. 336
Annex C (normative): SBV PICS optional types . 337
Annex D (normative): SBV PIXIT proforma . 338
D.1 Identification Summary . 338
D.2 Abstract Test Suite Summary. 338
D.3 Test Laboratory. 338
D.4 Client. 338
D.5 SUT. 339
D.6 Ancillary protocols. 339
Page 7
I-ETS 300 236: May 1993
D.7 Protocol Layer Information for SBV Protocol.339
D.7.1 Protocol Identification.339
D.7.1.1 IUT Information .340
D.7.1.2 Addresses .340
D.7.1.2.1 PDU Parameter Values .341
D.7.1.2.2 Parameter values accepted by the IUT .341
D.7.1.2.2.1 Specific parameters for an IUT acting
as an Access Function.341
D.7.1.2.2.3 Parameter values expected from the
IUT .344
D.7.1.2.4 Timer values .347
D.7.1.2.5 Procedural Information .347
D.7.1.2.5.1 Triggering IUT actions .348
D.7.1.2.5.2 Observing IUT Events.349
Annex E (informative): SBV Test Purposes .351
E.1 Terminal Functions (TF).351
E.1.1 TF/Basic Interconnect Tests (BIC) .351
E.1.2 TF/Capability Tests (CA).351
E.1.3 TF/Valid Behaviour Tests (BV) .352
E.1.3.1 TF/BV - State Event Transitions (SE).352
E.1.3.1.1 TF/BV/SE - Kernel (KE).352
E.1.3.1.2 TF/BV/SE Comm. Channel Management (CCM).353
E.1.3.1.2.1 TF/BV/SE/CCM Channel
Management Procedure (CMP).353
E.1.3.1.2.2 TF/BV/SE/CCM Multiple Channel
Coordination (MCC).353
E.1.3.1.3 TF/BV/SE Application Selection (AS) .354
E.1.3.1.4 TF/BV/SE Transparent Processable Data (TPD) .354
E.1.3.1.5 TF/BV/SE Define Function Keys (DFK).354
E.1.3.1.6 TF/BV/SE Remote Echo (RE) .354
E.1.3.1.7 TF/BV/SE Escape (ESC).355
E.1.3.2 TF/BV - Parameter Variations (PV).355
E.1.3.2.1 TF/BV/PV Kernel (KE) .355
E.1.3.2.1.1 TF/BV/PV/KE SBV_Establish .355
E.1.3.2.1.2 TF/BV/PV/KE SBV_Release.356
E.1.3.2.1.3 TF/BV/PV/KE SBV_Reset.356
E.1.3.2.1.4 TF/BV/PV/KE SBV_VTX_Data .356
E.1.3.2.1.5 TF/BV/PV/KE SBV_Set_parameter .356
E.1.3.2.1.6 TF/BV/PV/KE SBV_Read_parameter.356
E.1.3.2.1.7 TF/BV/PV/KE
SBV_Set/Read_parameter .357
E.1.3.2.1.8 TF/BV/PV/KE
SBV_Parameter_indication.357
E.1.3.2.1.9 TF/BV/PV/KE SBV_TFI .357
E.1.3.2.1.10 TF/BV/PV/KE SBV_TC_Error .357
E.1.3.2.2 TF/BV/PV Communication Channel Management (CCM) 357
E.1.3.2.2.1 TF/BV/PV/CCM Channel
Management Procedure (CMP).357
E.1.3.2.2.2 TF/BV/PV/CCM Multiple channel co-
ordination .359
E.1.3.2.3 TF/BV/PV Application Selection (AS) .359
E.1.3.2.3.1 TF/BV/PV/AS SBV_Begin_application359
E.1.3.2.4 TF/BV/PV Transparent Processable Data (TPD) .359
E.1.3.2.4.1 TF/BV/PV/TPD SBV_TPD_Begin .359
E.1.3.2.5 TF/BV/PV Define Function Keys (DFK).360
E.1.3.2.5.1 TF/BV/PV/DFK SBV_DFK .360
E.1.3.2.6 TF/BV/PV Remote Echo (RE) .360
E.1.3.2.6.1 TF/BV/PV/RE SBV_Remote_Echo.360
E.1.3.2.7 TF/BV/PV Escape (ESC).360
E.1.3.2.7.1 TF/BV/PV/ESC SBV_Escape .360
E.1.3.3 TF/BV - Encoding Variations (EV).360
Page 8
I-ETS 300 236: May 1993
E.1.3.4 TF/BV - Parameter Combinations (PC). 360
E.1.3.4.1 TF/BV/PC Kernel (KE) . 361
E.1.3.4.1.1 TF/BV/PC/KE SBV_Establish. 361
E.1.3.4.1.2 TF/BV/PC/KE SBV_Release. 362
E.1.3.4.1.3 TF/BV/PC/KE SBV_VTX_Data . 362
E.1.3.4.1.4 TF/BV/PC/KE SBV_Set_parameter . 362
E.1.3.4.1.5 TF/BV/PC/KE SBV_Read_parameter 362
E.1.3.4.1.6 TF/BV/PC/KE
SBV_Set/Read_parameter. 362
E.1.3.4.1.7 TF/BV/PC/KE
SBV_Parameter_indication . 362
E.1.3.4.1.8 TF/BV/PC/KE SBV_TFI. 363
E.1.3.4.1.9 TF/BV/PC/KE SBV_TC_Error . 363
E.1.3.4.2 TF/BV/PC Communication Channel Management (CCM) 363
E.1.3.4.2.1 TF/BV/PC/CCM Channel
Management Procedure (CMP) . 363
E.1.3.4.2.2 TF/BV/PC/CCM Multiple Channel
Coordination. 363
E.1.3.4.3 TF/BV/PC Application Selections (AS). 364
E.1.3.4.3.1 TF/BV/PC/AS SBV_Begin_application364
E.1.3.4.4 TF/BV/PC Transparent Processable Data (TPD) . 364
E.1.3.4.4.1 TF/BV/PC/TPD SBV_TPD_Begin . 364
E.1.3.4.5 TF/BV/PC Define Function Keys (DFK) . 364
E.1.3.4.5.1 TF/BV/PC/DFK SBV_DFK . 364
E.1.3.4.6 TF/BV/PC Escape (ESC) . 364
E.1.3.4.6.1 TF/BV/PC/TPD SBV_Escape. 364
E.1.4 TF - Inopportune Behaviour (BI) . 364
E.1.4.1 TF/BI - Test Event variation (TE). 365
E.1.4.1.1 TF/BI/TE - Unsupported services. 365
E.1.4.1.2 TF/BI/TE - Other inopportune events. 365
E.1.4.2 TF/BI - Timing/Timer variation (TI) . 365
E.1.4.3 TF/BI - Parameter Value Variation (PV) . 366
E.1.4.3.1 TF/BI/PV - Establishment service . 366
E.1.4.3.2 TF/BI/PV - X.3 related services. 366
E.1.4.3.3 TF/BI/PV - Telematic Commands. 366
E.1.4.4 TF/BI - Parameter Combination (PC) . 367
E.1.4.4.1 TF/BI/PC - X.3 related services . 367
E.1.4.4.2 TF/BI/PC - Telematic Commands. 367
E.1.5 TF - Invalid Behaviour (BO). 367
E.1.5.1 TF/BO - Parameter Value Variation (PV) . 367
E.1.5.1.1 TF/BO/PV - X.3 related services. 367
E.1.5.1.2 TF/BO/PV - Telematic Commands . 367
E.1.5.2 TF/BO - Encoding Variations (EV). 368
E.1.5.2.1 TF/BO/EV - X.3 related services. 368
E.1.5.2.2 TF/BO/EV - Telematic Commands . 368
E.2 Access Functions (AF) . 368
E.2.1 AF/Basic Interconnect Tests (BIC). 368
E.2.2 AF/Capability Tests (CA). 369
E.2.3 AF/Valid Behaviour Tests (BV). 369
E.2.3.1 AF/BV - State Event Transitions (SE). 369
E.2.3.1.1 AF/BV/SE - Kernel (KE) . 369
E.2.3.1.2 AF/BV/SE Comm. Channel Management (CCM) . 370
E.2.3.1.2.1 AF/BV/SE/CCM Channel
Management Procedure (CMP) . 370
E.2.3.1.2.2 AF/BV/SE/CCM Multiple Channel Co-
ordination (MCC). 370
E.2.3.1.3 AF/BV/SE Application Selection (AS) . 371
E.2.3.1.4 AF/BV/SE Transparent Processable Data (TPD) . 371
E.2.3.1.5 AF/BV/SE Define Function Keys (DFK) . 371
E.2.3.1.6 AF/BV/SE Remote Echo (RE). 371
E.2.3.1.7 AF/BV/SE Escape (ESC) . 371
E.2.4 AF - Inopportune Behaviour (BI) . 372
Page 9
I-ETS 300 236: May 1993
E.2.4.1 AF/BI - Test Event variation (TE) .372
E.2.4.1.1 AF/BI/TE - Unsupported services.372
E.2.4.1.2 AF/BI/TE - Other inopportune events .373
E.2.4.2 AF/BI - Timing/Timer variation (TI).373
E.2.4.3 AF/BI - Parameter Value Variation (PV).373
E.2.4.3.1 AF/BI/PV - Establishment service.373
E.2.4.3.2 AF/BI/PV - X.3 related services .373
E.2.4.3.3 AF/BI/PV - Telematic Commands .374
E.2.4.4 AF/BI - Parameter Combination (PC).374
E.2.4.4.1 AF/BI/PC - X.3 related services.374
E.2.4.4.2 AF/BI/PC - Telematic Commands .374
E.2.5 AF - Invalid Behaviour (BO).374
E.2.5.1 AF/BO - Parameter Value Variation (PV).374
E.2.5.1.1 AF/BO/PV - X.3 related services .374
E.2.5.1.2 AF/BO/PV - Telematic Commands.375
E.2.5.2 AF/BO - Encoding Variations (EV) .375
E.2.5.2.1 AF/BO/EV - X.3 related services .375
E.2.5.2.2 AF/BO/EV - Telematic Commands.375
Annex F (normative): SBV State Diagrams.376
F.1 CCITT Recommendation X.29 state machine .376
F.2 SBV State Diagram .377
Annex G (normative): SBV state tables.386
G.1 Terminal Function state tables .387
G.1.1.1 Terminal Function Service events.387
G.1.1.2 Terminal Function Protocol events.389
G.2. Access Function State Tables.391
G.2.1.1 Access Function Service events .391
G.2.1.2 Access Function Protocol events .393
Annex H (normative): BIS for SBV over ISDN circuit switched DTE/DTE (ETS 300 079) .395
H.1 Normative references.395
H.2 Access network scenario .396
H.3 Protocol pillar.396
H.4 Bearer Independent Service (BIS) definition.396
H.5 Use of BIS .397
H.6 Lower Layers.397
H.6.1 Co-ordination between D-channel and B-channel .397
H.6.2 Layer 3 D-channel protocol .397
H.6.2.1 The access protocol .397
H.6.2.2 Terminal selection and compatibility checking .397
H.6.2.3 Service specific use of supplementary services .397
H.6.2.4 Call Progress Signals .397
H.6.3 Layer 3 B-channel protocol .397
H.6.4 Layer 2 D-channel protocol .397
H.6.5 Layer 2 B-channel protocol .397
H.6.6 Layer 1 protocol .397
Annex J (informative): Scope of conformance testing of SBV Protocol .398
Annex K (informative): CTS-2 Triple-X conformance testing.400
Page 10
I-ETS 300 236: May 1993
K.1 Terminal Function related Test Cases. 400
K.1.1 DTM31A . 401
K.1.2 DTM31B . 403
K.1.3 DTM32. 404
K.1.4 DTM33A . 405
K.1.5 DTM33B . 406
K.1.6 DTM34. 406
K.2 Access Function related Test Cases. 406
K.2.1 DTM4. 406
K.2.2 DTM5. 407
Annex L (informative): Bibliography . 408
History. 409
Page 11
I-ETS 300 236: May 1993
Foreword
This Interim European Telecommunication Standard (I-ETS) has been produced by the Terminal
Equipment (TE) Technical Committee of the European Telecommunications Standards Institute (ETSI).
An ETSI standard may be given I-ETS status as it is regarded either as a provisional solution ahead of a
more advanced standard, or because it is immature and requires a trial period. The life of an I-ETS is
limited, at first, to three years after which it can be converted into a European Telecommunication
Standard (ETS), have it's life extended for a further two years, be replaced by a new version of the I-ETS
or, finally, be withdrawn.
Page 12
I-ETS 300 236: May 1993
Blank page
Page 13
I-ETS 300 236: May 1993
1 Scope
The Abstract Test Suite (ATS) defined by this I-ETS complies with the international standards on
conformance testing (ISO 9646-1 [4], ISO 9646-2 [5], ISO 9646-3 [6] and ISO 9646-5 [7]). Results of the
joint EWOS/ETSI Project Team No.5 on Open Systems Interconnection (OSI) conformance testing in
Europe are also taken into account.
NOTE 1: As defined by ISO 9646, in case of any discrepancy between a base standard and a
test suite, the base standard takes precedence above the test suite.
The ATS defined by this I-ETS is applicable to Videotex terminals which make use of the Syntax-based
Videotex (SBV) protocol as defined by ETS 300 223 [2] or ETS 300 079 [3].
NOTE 2: This conformance testing I-ETS does not apply in totality to ETS 300 079 [3] based
terminals. As a matter of fact, some services are tested in this I-ETS, which are only
defined in ETS 300 223 [2], and not in ETS 300 079 [3]. These services are :
SBV_Reset_TC, SBV_End_Immediate, SBV_Remote_Echo. When applying this I-
ETS to ETS 300 079 [3] based terminals, the test cases in question should be de-
selected.
NOTE 3: At the time of producing this I-ETS, ETS 300 079 [3] contains both the SBV protocol
definition and the use of that protocol over an Integrated Services Digital Network
(ISDN) DTE/DTE connection. In case of an ETS 300 079 [3] based terminal, tests for
layers other than layer 7 are out side the scope of this ETS.
The chosen test method for this ATS ensures that all SBV terminals can be tested without any additional
requirement other than those resulting from the protocol standard itself.
NOTE 4: The scope of testing is currently restricted to protocol testing where protocol is
understood in the way described in ISO 7498 [16]. Extension of the scope might
require other test methods. (See also subclause 5.1 and Annex K (informative)).
Test cases are fully specified for those situations in which an SBV terminal acts as a Terminal Function
(TF) (cf. subclause 6.2 of ETS 300 223 [2] or ETS 300 079 [3]).
NOTE 5: This situation, in which the SBV terminal acts as a Terminal Function, covers the
following cases : when the communication is established by the terminal itself (without
having the reverse_role_assignment parameter present in the Establish PDU), or
when the terminal is called by an SBV service or another SBV terminal with this
parameter present.
For those situations in which an SBV terminal behaves like an Access Function (AF) (cf. subclause 6.2 of
ETS 300 223 [2] or ETS 300 079 [3]), only the test purposes are given by this I-ETS.
NOTE 6: This situation occurs when a called SBV terminal accepts an incoming Establish
request, on which the reverse_role_assignment parameter is not present. This is
generally used in case of terminal-to-terminal communication.
NOTE 7: This I-ETS provides only for an empty place-holder for a test case selection table.
Completion of this table is left open for the possible transition of this I-ETS to an ETS.
As a consequence, and for an interim period, de-selection of those test cases related
to optional elements of the base standard needs to be done by other means. It should
not be understood that all the test cases are applicable in all cases ; a de-selection
process is implied.
Page 14
I-ETS 300 236: May 1993
2 Normative references
This I-ETS incorporates by dated or undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the test and the publications are listed
hereafter. For dated references subsequent amendments to or revisions of any of these publications apply
to this I-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 222: "Terminal Equipment (TE); Framework of Videotex terminal
protocols".
[2] ETS 300 223: "Terminal Equipment (TE); Syntax-based Videotex, Common
end-to-end protocols".
[3] ETS 300 079: "Integrated Services Digital Network (ISDN); Syntax-based
Videotex, End-to-end protocols, circuit mode DTE - DTE".
[4] ISO 9646-1: "OSI Conformance Testing Methodology and Framework, Part 1:
General Concepts".
[5] ISO 9646-2: "OSI Conformance Testing Methodology and Framework, Part 2:
Abstract Test Suite Specification".
[6] ISO 9646-3: "OSI Conformance Testing Methodology and Framework, Part 3:
Tree and Tabular Combined Notation (TTCN)."
[7] ISO 9646-5: "OSI Conformance Testing Methodology and Framework, Part 5:
Requirements on Test Laboratorie
...