SIST EN 300 236 V1.2.2:2003
(Main)Terminal Equipment (TE); Syntax-based videotex protocol; Terminal conformance testing
- Abstract
Conversion of existing I-ETS 300 236 to full standard.
- 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
SIST EN 300 236 V1.2.2:2003 is a SIST standard identical to ETSI EN 300 236 Version 1.2.2. It specifies the abstract test suite for terminal conformance testing of Syntax-based Videotex (SBV) Terminal Equipment (TE), so laboratories and implementers can check whether a terminal behaves as the protocol expects.
What does SIST EN 300 236 V1.2.2:2003 specify?
SIST EN 300 236 V1.2.2:2003 specifies an Abstract Test Suite (ATS) for Videotex terminals that use the SBV protocol. It is written for conformance testing, not for defining the user-facing service itself, and it follows the ISO 9646 testing framework.
The standard applies to terminals using SBV as defined by ETS 300 223 or ETS 300 079. For ETS 300 079-based terminals, the document also identifies some services that should be de-selected when the test suite is applied.
| 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 |
What are the key requirements of SIST EN 300 236 V1.2.2:2003?
SIST EN 300 236 V1.2.2:2003 defines how SBV conformance testing is structured, what information the tester must declare, and how SBV protocol events are mapped into testable service primitives. In practice, this tells a test lab what to configure, what to observe, and which cases belong to which test group.
Test method and test structure
The SBV protocol test group uses the single layer Remote Test method. The ATS is split into Terminal Function (TF) and Access Function (AF) branches, each with Basic Interconnection Tests (BIT), Capability (CA), Valid Behaviour (BV), Invalid Behaviour (BO), and Inopportune Behaviour (BI). That structure matters because it tells the reader which behaviour is checked for normal operation, error handling, and unexpected events.
How SBV protocol events are treated
The document treats an SBV PDU as an abstract view of a protocol event or action carried through the Bearer Independent Service (BIS). Some PDU parameters belong to lower-layer transport, while others carry SBV semantics only. This distinction matters when building test cases, because the same service may be encoded through different lower-layer fields depending on the network.
Use of BIS and ETS 300 079 mapping
The main TTCN definitions use BIS as defined in ETS 300 223, and Annex H gives the correspondence for ETS 300 079-based equipment. The standard also notes that SBV_Reset_TC, SBV_End_Immediate, and SBV_Remote_Echo are to be de-selected for ETS 300 079-based terminals. That matters because the same ATS can be applied to different terminal types, but not every test case applies everywhere.
Declared test data and implementation details
Clauses 6.1 and 6.10 define the Test Suite Parameters and timers, including PICS and PIXIT-driven values such as addresses, application data, function key details, and timer durations. The reader has to supply implementation-specific values before the suite can run on a real terminal.
PCOs, PDUs, and state handling
Clause 6 declares two lower tester PCOs, L1 and L2, with L1 as default. The PDU declarations and structured types then define the SBV messages, X.3 parameter lists, error codes, and function key structures used in the test cases. Clauses 8 and 9 provide the common test steps and the test case library that drive the actual conformance checks.
What terms does SIST EN 300 236 V1.2.2:2003 define?
- Abstract Test Suite (ATS) - the structured set of abstract test cases used to assess conformance.
- Implementation under test (IUT) - the equipment whose SBV behaviour is being checked.
- System under test (SUT) - the overall test target in the ISO 9646 sense.
- Protocol Implementation Conformance Statement (PICS) - the declaration of which protocol capabilities and options an implementation claims.
- Protocol Implementation eXtra Information for Testing (PIXIT) - the implementation-specific testing data needed to run the suite.
- Bearer Independent Service (BIS) - the service abstraction used to carry SBV-related events and data.
- Terminal Function (TF) - the SBV role tested when the terminal initiates or acts as the terminal side of the exchange.
- Access Function (AF) - the SBV role tested when the terminal accepts an incoming establishment and behaves as the access side.
Who uses SIST EN 300 236 V1.2.2:2003?
SIST EN 300 236 V1.2.2:2003 is used by test laboratories, conformance assessors, and manufacturers of Videotex terminal equipment. It is also relevant to quality managers and buyers who need to verify that an SBV terminal can be tested in a defined, repeatable way.
It supports implementation, test-case selection, and conformance assessment for teams working with TE, SBV, BIS, and related ISDN or packet-oriented environments. The PICS and PIXIT annexes make it especially useful when preparing a device for formal testing.
What changed in SIST EN 300 236 V1.2.2:2003 from the previous edition?
SIST EN 300 236 V1.2.2:2003 converts the existing I-ETS 300 236 into a full standard. The foreword also says the text was prepared from the published I-ETS with only minor editorial corrections.
Which standards are used with SIST EN 300 236 V1.2.2:2003?
The standard relies on ETS 300 222 for the framework of Videotex terminal protocols, ETS 300 223 for SBV common end-to-end protocols, and ETS 300 079 for SBV over ISDN circuit mode DTE-DTE. It also uses ISO 9646-1, -2, -3, and -5 for the conformance testing framework, ISO 7498 for OSI reference concepts, ISO/IEC 8208 for X.25 packet-level coding, ISO/TR 8509 for service conventions, and CCITT Recommendations X.3 and X.29 for X.3 parameter handling and PAD procedures.
What does the SIST EN 300 236 V1.2.2:2003 document contain?
The document contains a TTCN-based ATS, including declarations for test suite parameters, PCOs, PDUs, structured types, ASPs, aliases, and timers. It also contains the test step library, the test case library, and normative annexes that define PICS and PIXIT proformas, conditional expressions, optional types, and state diagrams.
It gives detailed PDU definitions for SBV services such as establish, release, reset, data transfer, parameter handling, terminal facility identifier, channel open/close, application start/end, transparent processable data, definable function keys, remote echo, and escape. It also includes state tables and mappings that support protocol-level testing and the BIS correspondence for ETS 300 079-based equipment.
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 EN 300 236 V1.2.2:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Terminal Equipment (TE); Syntax-based videotex protocol; Terminal conformance testing". This standard covers: Conversion of existing I-ETS 300 236 to full standard.
Conversion of existing I-ETS 300 236 to full standard.
SIST EN 300 236 V1.2.2: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 EN 300 236 V1.2.2: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)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Terminal Equipment (TE); Syntax-based videotex protocol; Terminal conformance testing35.180Terminalska in druga periferna oprema ITIT Terminal and other peripheral equipment33.160.99Druga avdio, video in avdiovizuelna opremaOther audio, video and audiovisual equipmentICS:Ta slovenski standard je istoveten z:EN 300 236 Version 1.2.2SIST EN 300 236 V1.2.2:2003en01-december-2003SIST EN 300 236 V1.2.2:2003SLOVENSKI
STANDARD
European Telecommunications Standards InstituteEN 300 236 V1.2.2 (1997-12)European Standard (Telecommunications series)Terminal Equipment (TE);Syntax-based videotex protocol;Terminal conformance testingSIST EN 300 236 V1.2.2:2003
EN 300 236 V1.2.2 (1997-12)2ReferenceREN/MTA-001011BIS (26o00ipc.PDF)KeywordsAccess, terminal, testing, videotexETSI SecretariatPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88X.400c= fr; a=atlas; p=etsi; s=secretariatInternetsecretariat@etsi.frhttp://www.etsi.frCopyright NotificationNo 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.SIST EN 300 236 V1.2.2:2003
EN 300 236 V1.2.2 (1997-12)3ContentsIntellectual Property Rights.10Foreword.101Scope.112Normative references.113Definitions.134Abbreviations.145Test suite overview.155.1Test suite structure.155.2Test purposes.175.3Method of conformance testing.175.3.1SBV protocol Data Unit (PDU).175.3.2Use of Bearer Independent Service (BIS).176Declarations.196.1Test Suite Parameters Declaration.196.2Test case De-Selection.236.3Test case Variables Declaration.236.4Test Suite Constants Declaration.236.5Test Suite Variables Declaration.236.6Point Control and Observations (PCOs) declaration.246.7PDUs declaration.246.7.1PDU Type declaration.256.7.2Structured Type Declaration.416.8ASPs Declaration.446.9Alias Declaration.486.10Timers Declaration.516.11User Type Definitions.516.12User Operator Definitions.517Constraint Declarations.527.1Constraints declaration.527.1.1ASP Constraints declaration.527.1.2PDU Constraints Declaration.567.1.3Structured Type Constraints declaration.1818Common Test Step Library.1988.1Preambles.1988.2Postambles.2008.3Other Test Steps.2029Test case Library.2039.1Terminal Functions (TF).2039.1.1TF/Basic Interconnect Tests (BIT).2039.1.2TF/Capability Tests (CA).2039.1.3TF/Valid Behaviour Tests (BV).2039.1.3.1TF/BV - State Event Transitions (SE).2039.1.3.1.1SBV/TF/BV/SE - Kernel (KE).2049.1.3.1.2SBV/TF/BV/SE Comm. Channel Management (CCM).2129.1.3.1.3SBV/TF/BV/SE Application Services (AS).2189.1.3.1.4SBV/TF/BV/SE Transparent Processable Data (TPD).2209.1.3.1.5SBV/TF/BV/SE Define Function Keys (DFK).2249.1.3.1.6SBV/TF/BV/SE Remote Echo (RE).2249.1.3.1.7SBV/TF/BV/SE Escape (ESC).2259.1.3.2TF/BV - Parameter Variations (PV).2259.1.3.2.1TF/BV/PV Kernel (KE).226SIST EN 300 236 V1.2.2:2003
EN 300 236 V1.2.2 (1997-12)49.1.3.2.2TF/BV/PV Communication Channel Management (CCM).2399.1.3.2.3TF/BV/PV Application Selections (AS).2539.1.3.2.4TF/BV/PV Transparent Processable Data (TPD).2569.1.3.2.5TF/BV/PV Define Function Keys (DFK).2599.1.3.2.6TF/BV/PV Remote Echo (RE).2609.1.3.2.7TF/BV/PV Escape (ESC).2619.1.3.3TF/BV - Encoding Variations (EV).2639.1.3.4TF/BV - Parameter Combinations (PC).2639.1.3.4.1TF/BV/PC Kernel (KE).2639.1.3.4.2TF/BV/PC Communication Channel Management (CCM).2699.1.3.4.3TF/BV/PC Application Selections (AS).2759.1.3.4.4TF/BV/PC Transparent Processable Data (TPD).2769.1.3.4.5TF/BV/PC Define Function Keys (DFK).2789.1.3.4.6TF/BV/PC Escape (ESC).2799.1.4TF - Inopportune Behaviour (BI).2809.1.4.1TF/BI - Test Event variation (TE).2809.1.4.1.1TF/BI/TE - Unsupported services.2809.1.4.1.2TF/BI/TE - Other inopportune events.2839.1.4.2TF/BI - Timing/Timer variation.2849.1.4.3TF/BI - parameter value Variation (PV).2859.1.4.3.1TF/BI/PV - Establishment service.2859.1.4.3.2TF/BI/PV - X3 related services.2869.1.4.3.3TF/BI/PV - Telematic Commands.2879.1.4.4TF/BI - Parameter Combination (PC).2919.1.4.4.1TF/BI/PC - X.3 related services.2919.1.4.4.2TF/BI/PC - Telematic Commands.2929.1.5TF - Invalid Behaviour (BO).2929.1.5.1TF/BO - parameter value Variation (PV).2929.1.5.1.1TF/BO/PV - X.3 related services.2939.1.5.1.2TF/BO/PV - Telematic Commands.2939.1.5.2TF/BO - Encoding Variations (EV).2989.1.5.2.1TF/BO/EV - X.3 related services.2989.1.5.2.2TF/BO/EV - Telematic Commands.299Annex A (normative):SBV PICS proforma.301A.1Classification.301A.2PICS proforma, identification of the implementation.302A.2.1Guidance for completion.302A.2.2Date.302A.2.3Supplier details.302A.2.4Implementation details.302A.2.5Claimed compliance to standards.302A.3PICS proforma, capabilities and options.303A.3.1Initiator/Responder capability.303A.3.2Network Capabilities.304A.3.3SBV Services.304A.3.4SBV to BIS association options.304A.3.5PDUs.305A.3.5.1AF PDUs.305A.3.5.1.1AF PDUs/SBV_Establish.305A.3.5.1.2AF PDUs/SBV_Release.305A.3.5.1.3AF PDUs/SBV_Reset.305A.3.5.1.4AF PDUs/SBV_VTX_Data.306A.3.5.1.5AF PDUs/SBV_Set_Param.306A.3.5.1.6AF PDUs/SBV_Read_Param.306A.3.5.1.7AF PDUs/SBV_Set_Read_Param.306A.3.5.1.8AF PDUs/SBV_Param_Indication.306A.3.5.1.9AF PDUs/SBV_TFI.306A.3.5.1.10AF PDUs/SBV_TC_Error.307SIST EN 300 236 V1.2.2:2003
EN 300 236 V1.2.2 (1997-12)5A.3.5.1.11AF PDUs/SBV_Channel_Open.307A.3.5.1.12AF PDUs/SBV_Channel_Close.307A.3.5.1.13AF PDUs/SBV_Channel_Error.307A.3.5.1.14AF PDUs/SBV_Begin_Application.307A.3.5.1.15AF PDUs/SBV_End_Application.307A.3.5.1.16AF PDUs/SBV_End_Immediate.308A.3.5.1.17AF PDUs/SBV_TPD_Begin.308A.3.5.1.18AF PDUs/SBV_TPD_End.308A.3.5.1.19AF PDUs/SBV_DFK.308A.3.5.1.20AF PDUs/SBV_Remote_Echo.308A.3.5.1.21AF PDUs/SBV_Escape.308A.3.5.2TF PDUs.308A.3.5.2.1TF PDUs/SBV_Establish.309A.3.5.2.2TF PDUs/SBV_Release.309A.3.5.2.3TF PDUs/SBV_Reset.309A.3.5.2.4TF PDUs/SBV_VTX_Data.309A.3.5.2.5TF PDUs/SBV_Set_Param.309A.3.5.2.6TF PDUs/SBV_Read_Param.310A.3.5.2.7TF PDUs/SBV_Set_Read_Param.310A.3.5.2.8TF PDUs/SBV_Param_Indication.310A.3.5.2.9TF PDUs/SBV_TFI.310A.3.5.2.10TF PDUs/SBV_TC_Error.310A.3.5.2.11TF PDUs/SBV_Channel_Open.310A.3.5.2.12TF PDUs/SBV_Channel_Close.311A.3.5.2.13TF PDUs/SBV_Channel_Error.311A.3.5.2.14TF PDUs/SBV_Begin_Application.311A.3.5.2.15TF PDUs/SBV_End_Application.311A.3.5.2.16TF PDUs/SBV_End_Immediate.311A.3.5.2.17TF PDUs/SBV_TPD_Begin.311A.3.5.2.18TF PDUs/SBV_TPD_End.312A.3.5.2.19TF PDUs/SBV_DFK.312A.3.5.2.20TF PDUs/SBV_Remote_Echo.312A.3.5.2.21TF PDUs/SBV_Escape.312A.3.6Parameters.312A.3.6.1AF parameters.313A.3.6.1.1AF parameters/SBV_Establish Request.313A.3.6.1.2AF parameters/SBV_Establish Response.313A.3.6.1.3AF parameters/SBV_Release Request.313A.3.6.1.4AF parameters/SBV_Reset Request.314A.3.6.1.5AF parameters/SBV_Reset Response.314A.3.6.1.6AF parameters/SBV_VTX_Data Request.314A.3.6.1.7AF parameters/SBV_Set_Param Request.314A.3.6.1.8AF parameters/SBV_Read_Param Request.315A.3.6.1.9AF parameters/SBV_Set_Read_Param Request.315A.3.6.1.10AF parameters/SBV_Param_Ind Request.315A.3.6.1.11AF parameters/SBV_TFI Request.315A.3.6.1.12AF parameters/SBV_TFI Response.315A.3.6.1.13AF parameters/SBV_TC_Error Request.316A.3.6.1.14AF parameters/SBV_Channel_Open Request.316A.3.6.1.15AF parameters/SBV_Channel_Open Response.316A.3.6.1.16AF parameters/SBV_Channel_Close Request.317A.3.6.1.17AF parameters/SBV_Channel_Close Response.317A.3.6.1.18AF parameters/SBV_Channel_Error Request.317A.3.6.1.19AF parameters/SBV_Begin_Application Request.317A.3.6.1.20AF parameters/SBV_Begin_Application Response.317A.3.6.1.21AF parameters/SBV_End_Application Request.318A.3.6.1.22AF parameters/SBV_End_Immediate Request.318A.3.6.1.23AF parameters/SBV_TPD_Begin Request.318A.3.6.1.24AF parameters/SBV_TPD_Begin Response.318A.3.6.1.25AF parameters/SBV_TPD_End Request.318SIST EN 300 236 V1.2.2:2003
EN 300 236 V1.2.2 (1997-12)6A.3.6.1.26AF parameters/SBV_DFK Request.318A.3.6.1.27AF parameters/SBV_Remote_Echo Request.318A.3.6.1.28AF parameters/SBV_Escape Request.319A.3.6.2TF Parameters.319A.3.6.2.1TF Parameters/SBV_Establish Request.319A.3.6.2.2TF Parameters/SBV_Establish Response.320A.3.6.2.3TF Parameters/SBV_Release Request.320A.3.6.2.4TF Parameters/SBV_Reset Request.320A.3.6.2.5TF Parameters/SBV_Reset Response.320A.3.6.2.6TF Parameters/SBV_VTX_Data Request.321A.3.6.2.7TF Parameters/SBV_Set_Param Request.321A.3.6.2.8TF Parameters/SBV_Read_Param Request.321A.3.6.2.9TF Parameters/SBV_Set_Read_Param Request.321A.3.6.2.10TF Parameters/SBV_Param_Ind Request.321A.3.6.2.11TF Parameters/SBV_TFI Request.322A.3.6.2.12TF Parameters/SBV_TFI Response.322A.3.6.2.13TF Parameters/SBV_TC_Error Request.322A.3.6.2.14TF Parameters/SBV_Channel_Open Request.323A.3.6.2.15TF Parameters/SBV_Channel_Open Response.323A.3.6.2.16TF Parameters/SBV_Channel_Close Request.323A.3.6.2.17TF Parameters/SBV_Channel_Close Response.323A.3.6.2.18TF Parameters/SBV_Channel_Error Request.324A.3.6.2.19TF Parameters/SBV_Begin_Application Request.324A.3.6.2.20TF Parameters/SBV_Begin_Application Response.324A.3.6.2.21TF Parameters/SBV_End_Application Request.324A.3.6.2.22TF Parameters/SBV_End_Immediate Request.324A.3.6.2.23TF Parameters/SBV_TPD_Begin Request.324A.3.6.2.24TF Parameters/SBV_TPD_Begin Response.325A.3.6.2.25TF Parameters/SBV_TPD_End Request.325A.3.6.2.26TF Parameters/SBV_DFK Request.325A.3.6.2.27AF parameters/SBV_Remote_Echo Request.325A.3.6.2.28TF Parameters/SBV_Escape Request.325A.3.6.3X.3 Parameters.326A.3.6.3.1X.3 Parameters/send.326A.3.6.3.2X.3 Parameters/receive.326Annex B (normative):SBV PICS conditional expressions.327Annex C (normative):SBV PICS optional types.328Annex D (normative):SBV PIXIT proforma.329D.1Identification summary.329D.2Abstract Test Suite summary.329D.3Test laboratory.329D.4Client.329D.5SUT.330D.6Ancillary protocols.330D.7Protocol layer information for SBV protocol.330D.7.1Protocol identification.330D.7.1.1ITU information.330D.7.1.2Addresses.330D.7.1.2.1PDU parameter values.331D.7.1.2.2Parameter values accepted by the IUT.332D.7.1.2.2.1Specific parameters for an IUT acting as an Access Function.332D.7.1.2.2.2Parameter values expected from the IUT.335D.7.1.2.3Timer values.336SIST EN 300 236 V1.2.2:2003
EN 300 236 V1.2.2 (1997-12)7D.7.1.2.4Procedural Information.337D.7.1.2.4.1Triggering IUT actions.337D.7.1.2.4.2Observing IUT Events.338Annex E (informative):SBV Test Purposes.340E.1Terminal Functions (TF).340E.1.1TF/Basic Interconnect Tests (BIC).340E.1.2TF/Capability Tests (CA).340E.1.3TF/Valid Behaviour Tests (BV).340E.1.3.1TF/BV - State Event Transitions (SE).341E.1.3.1.1TF/BV/SE - Kernel (KE).341E.1.3.1.2TF/BV/SE Comm. Channel Management (CCM).342E.1.3.1.2.1TF/BV/SE/CCM Channel Management Procedure (CMP).342E.1.3.1.2.2TF/BV/SE/CCM Multiple Channel Coordination (MCC).342E.1.3.1.3TF/BV/SE Application Selection (AS).342E.1.3.1.4TF/BV/SE Transparent Processable Data (TPD).342E.1.3.1.5TF/BV/SE Define Function Keys (DFK).343E.1.3.1.6TF/BV/SE Remote Echo (RE).343E.1.3.1.7TF/BV/SE Escape (ESC).343E.1.3.2TF/BV - Parameter Variations (PV).343E.1.3.2.1TF/BV/PV Kernel (KE).343E.1.3.2.1.1TF/BV/PV/KE SBV_Establish.343E.1.3.2.1.2TF/BV/PV/KE SBV_Release.344E.1.3.2.1.3TF/BV/PV/KE SBV_Reset.344E.1.3.2.1.4TF/BV/PV/KE SBV_VTX_Data.344E.1.3.2.1.5TF/BV/PV/KE SBV_Set_parameter.344E.1.3.2.1.6TF/BV/PV/KE SBV_Read_parameter.345E.1.3.2.1.7TF/BV/PV/KE SBV_Set/Read_parameter.345E.1.3.2.1.8TF/BV/PV/KE SBV_Parameter_indication.345E.1.3.2.1.9TF/BV/PV/KE SBV_TFI.345E.1.3.2.1.10TF/BV/PV/KE SBV_TC_Error.345E.1.3.2.2TF/BV/PV Communication Channel Management (CCM).345E.1.3.2.2.1TF/BV/PV/CCM Channel Management Procedure (CMP).345E.1.3.2.2.2TF/BV/PV/CCM Multiple channel co-ordination.347E.1.3.2.3TF/BV/PV Application Selection (AS).347E.1.3.2.3.1TF/BV/PV/AS SBV_Begin_application.347E.1.3.2.4TF/BV/PV Transparent Processable Data (TPD).347E.1.3.2.4.1TF/BV/PV/TPD SBV_TPD_Begin.347E.1.3.2.5TF/BV/PV Define Function Keys (DFK).348E.1.3.2.5.1TF/BV/PV/DFK SBV_DFK.348E.1.3.2.6TF/BV/PV Remote Echo (RE).348E.1.3.2.6.1TF/BV/PV/RE SBV_Remote_Echo.348E.1.3.2.7TF/BV/PV Escape (ESC).348E.1.3.2.7.1TF/BV/PV/ESC SBV_Escape.348E.1.3.3TF/BV - Encoding Variations (EV).348E.1.3.4TF/BV - Parameter Combinations (PC).348E.1.3.4.1TF/BV/PC Kernel (KE).348E.1.3.4.1.1TF/BV/PC/KE SBV_Establish.348E.1.3.4.1.2TF/BV/PC/KE SBV_Release.349E.1.3.4.1.3TF/BV/PC/KE SBV_VTX_Data.349E.1.3.4.1.4TF/BV/PC/KE SBV_Set_parameter.349E.1.3.4.1.5TF/BV/PC/KE SBV_Read_parameter.349E.1.3.4.1.6TF/BV/PC/KE SBV_Set/Read_parameter.350E.1.3.4.1.7TF/BV/PC/KE SBV_Parameter_indication.350E.1.3.4.1.8TF/BV/PC/KE SBV_TFI.350E.1.3.4.1.9TF/BV/PC/KE SBV_TC_Error.350E.1.3.4.2TF/BV/PC Communication Channel Management (CCM).350E.1.3.4.2.1TF/BV/PC/CCM Channel Management Procedure (CMP).350E.1.3.4.2.2TF/BV/PC/CCM Multiple Channel Coordination.351E.1.3.4.3TF/BV/PC Application Selections (AS).351SIST EN 300 236 V1.2.2:2003
EN 300 236 V1.2.2 (1997-12)8E.1.3.4.3.1TF/BV/PC/AS SBV_Begin_application.351E.1.3.4.4TF/BV/PC Transparent Processable Data (TPD).351E.1.3.4.4.1TF/BV/PC/TPD SBV_TPD_Begin.351E.1.3.4.5TF/BV/PC Define Function Keys (DFK).351E.1.3.4.5.1TF/BV/PC/DFK SBV_DFK.351E.1.3.4.6TF/BV/PC Escape (ESC).351E.1.3.4.6.1TF/BV/PC/TPD SBV_Escape.351E.1.4TF - Inopportune Behaviour (BI).352E.1.4.1TF/BI - Test Event variation (TE).352E.1.4.1.1TF/BI/TE - Unsupported services.352E.1.4.1.2TF/BI/TE - Other inopportune events.352E.1.4.2TF/BI - Timing/Timer variation (TI).352E.1.4.3TF/BI - parameter value Variation (PV).353E.1.4.3.1TF/BI/PV - Establishment service.353E.1.4.3.2TF/BI/PV - X.3 related services.353E.1.4.3.3TF/BI/PV - Telematic Commands.353E.1.4.4TF/BI - Parameter Combination (PC).354E.1.4.4.1TF/BI/PC - X.3 related services.354E.1.4.4.2TF/BI/PC - Telematic Commands.354E.1.5TF - Invalid
...