SIST EN 300 797:2000
(Main)Digital Audio Broadcasting (DAB); Distribution interfaces; Service Transport Interface (STI)
- Abstract
Specifies an interface which allows broadcasters, who are producing a DAB programme or data service component, to transmit this DAB component to the multiplex operator responsible for building the full signal.
- Status
- Published
- Publication Date
- 31-Dec-1999
- Technical Committee
- RES - Radio equipment and systems
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Jan-2000
- Due Date
- 01-Jan-2000
- Completion Date
- 01-Jan-2000
- Mandate
- T-244
SIST EN 300 797:2000 is the Slovenian adoption of EN 300 797 V1.1.1. It specifies the Digital Audio Broadcasting (DAB) Service Transport Interface (STI), which lets a broadcaster or service provider transfer a DAB programme or data service component to the multiplex operator that builds the full signal. It is written for DAB distribution links between upstream and downstream entities.
What does SIST EN 300 797:2000 specify?
SIST EN 300 797:2000 specifies the STI for DAB distribution interfaces. In practice, it defines how service components, configurations, FIG files, FIB grids, and resource information are carried and managed between the entities that exchange them.
The document is organized into:
- scope and references
- definitions, symbols, abbreviations and terminology
- the STI overview
- logical definition of the data part, STI-D(LI)
- logical definition of the control part, STI-C(LI)
- transport adaptation for STI-C(TA)
- a generic transport frame, STI(PI, X)
- physical interfaces for synchronous and asynchronous links
What are the key requirements of SIST EN 300 797:2000?
The standard splits STI into data, control, and transport layers
SIST EN 300 797:2000 defines STI-D(LI) for carrying DAB service data and STI-C(LI) for control and management messages. The data part has a defined frame structure with fields for error indication, frame characterization, stream characterization, end-of-header, main stream data, end-of-frame, and a time stamp.
That matters because implementers must handle both payload and control information consistently, not just move bits from one side to the other.
STI-C(LI) uses explicit message formats and sessions
SIST EN 300 797:2000 requires STI-C(LI) messages to use command words, command extensions, data fields, separators, and a delimiter. It also uses data exchange sessions for grouped transfers such as configuration, FIG file, FIB grid, resource, configuration name, and FIG file name exchanges.
This means systems have to open, complete, or abort a session in a controlled way instead of sending unrelated control messages ad hoc.
Reconfiguration is controlled by named configurations and timing fields
SIST EN 300 797:2000 defines action messages for reconfiguration, including RCONFIG REQ, DEF, INF, CAN, ACK, and ERR. A reconfiguration is a change from one configuration to another at a defined time, identified by a configuration name and a time reference using UTC and DFCT.
In practice, this lets both sides agree on when the multiplex change happens and reduces the risk of switching too early or too late.
Configurations are built hierarchically
SIST EN 300 797:2000 uses configuration messages to describe sub-channels, streams, components, services, and FIG files. The definition has to follow a hierarchy: sub-channel first, then stream, then component, then service, then FIG file use.
This matters because a configuration must be complete and internally consistent before it can be accepted or broadcast.
FIG files and FIB grids are managed as separate exchange types
SIST EN 300 797:2000 defines FIG file messages for Service Information FIGs only, including definition, record transfer, selection, deselection, deletion, and error handling. It also defines FIB grid messages for synchronous insertion of Fast Information Blocks, with a 500-record grid and activation at a specified UTC time.
That gives operators separate tools for cyclic FIG broadcasting and frame-accurate FIB insertion.
Resources, capacities, and identifier usage are allocated explicitly
SIST EN 300 797:2000 provides resource messages for channel capacities, stream limits, identifier allocations, and identifier usage limits. It covers scarce resources such as Main Service Channel capacity and Fast Information Channel capacity.
This is important for capacity planning, because the upstream entity needs to know what it is allowed to use and how much.
The transport part is mapped to several physical interfaces
SIST EN 300 797:2000 includes transport adaptation for synchronous and asynchronous links, a generic transport frame, and physical interfaces for G.703, V.11, WG1/WG2, IEC 958, G.704 with and without error protection, H.221, and V.24.
That makes the STI usable across different transmission environments without changing the logical message model.
What terms does SIST EN 300 797:2000 define?
- Service Transport Interface (STI) - The interface defined by this standard for moving DAB service components and related control information between entities.
- STI-D(LI) - The logical data part of STI, used for the DAB payload and stream-related framing.
- STI-C(LI) - The logical control part of STI, used for messages that manage configurations, files, grids, resources, and supervision.
- FIG - A Fast Information Group used for Service Information in DAB.
- FIB - A Fast Information Block, handled here with synchronous insertion and grid control.
- MSC - The Main Service Channel, one of the DAB channels whose capacity and usage are managed by the interface.
- DAB - Digital Audio Broadcasting, the broadcast system addressed by the standard.
Who uses SIST EN 300 797:2000?
SIST EN 300 797:2000 is used by DAB broadcasters, service providers, ensemble providers, and multiplex operators. It is also relevant for system integrators and equipment vendors that implement DAB distribution links, configuration exchange, FIG file handling, and resource allocation.
Quality and operations teams use it to check that a distribution chain can define services, coordinate reconfigurations, manage broadcast metadata, and allocate channel resources in a controlled way.
Which standards are used with SIST EN 300 797:2000?
SIST EN 300 797:2000 refers to ETS 300 401 [1]. That companion standard supplies the DAB terms and parameters used for items such as sub-channel definitions, service component types, service identifiers, and multiplex configuration information.
What does the SIST EN 300 797:2000 document contain?
The document contains detailed message formats, field definitions, and rules for using STI-C(LI) sessions. It also includes logical frame structures for STI-D(LI), transport adaptation rules for synchronous and asynchronous links, and a generic transport frame format.
Many clauses are supported by figures and tables that define how messages are built and interpreted, including reconfiguration, configuration, FIG file, FIB grid, resource, information, and supervision messages. Later clauses describe mapping to physical interfaces such as G.703, V.11, IEC 958, G.704, H.221, and V.24.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST EN 300 797:2000 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Digital Audio Broadcasting (DAB); Distribution interfaces; Service Transport Interface (STI)". This standard covers: Specifies an interface which allows broadcasters, who are producing a DAB programme or data service component, to transmit this DAB component to the multiplex operator responsible for building the full signal.
Specifies an interface which allows broadcasters, who are producing a DAB programme or data service component, to transmit this DAB component to the multiplex operator responsible for building the full signal.
SIST EN 300 797:2000 is classified under the following ICS (International Classification for Standards) categories: 33.170 - Television and radio broadcasting. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 300 797:2000 is associated with the following European legislation: Standardization Mandates: T-244. 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 EN 300 797:2000 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.Digitalna zvokovna radiodifuzija (DAB) - Vmesniki za razpošiljanje - Vmesnik za prenos storitev (STI)Digital Audio Broadcasting (DAB); Distribution interfaces; Service Transport Interface (STI)33.170Televizijska in radijska difuzijaTelevision and radio broadcastingICS:Ta slovenski standard je istoveten z:EN 300 797 V1.1.13SIST EN 300 797:en01-jXQLM-3SIST EN 300 797:SLOVENSKI
STANDARD
EN 300 797 V1.1.1 (1999-02)European Standard (Telecommunications series)Digital Audio Broadcasting (DAB);Distribution interfaces;Service Transport Interface (STI)EBUUEREuropean Broadcasting UnionUnion Européenne de Radio-TélévisionSIST EN 300 797:2000
ETSIEN 300 797 V1.1.1 (1999-02)2ReferenceDEN/JTC-DAB-5 (7do00ico.PDF)KeywordsDAB, digital, audio, broadcasting, data, transport,interfaceETSIPostal 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/88Internetsecretariat@etsi.frIndividual copies of this ETSI deliverablecan be downloaded fromhttp://www.etsi.orgIf you find errors in the present document, send yourcomment to: editor@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 1999.© European Broadcasting Union 1999.All rights reserved.SIST EN 300 797:2000
ETSIEN 300 797 V1.1.1 (1999-02)3ContentsIntellectual Property Rights.10Foreword.10Introduction.111Scope.132References.133Definitions, symbols, abbreviations and terminology.143.1Definitions.143.2Abbreviations.183.3Symbols.193.3.1Numerical ranges.193.3.2Bit and byte numbering.193.3.3Arithmetic operators.193.3.4Logical operators.193.3.5STI-C(LI) Field Types.193.4Ordering of bytes and bits for transmission.203.5Reserved bits.203.6STI-C character set.203.6.1STI-C(LI) message character set.203.6.2STI-C(TA) character set.204Overview of the Service Transport Interface definition.214.1Conceptual model of the Service Transport Interface.214.2The logical model of the STI.234.3The layered model of the STI.244.4The implementation model of the STI.254.4.1Examples of network topologies.254.4.2Hierarchical collection networks.274.4.3Multicasting.275Logical definition of the STI Data Part, STI-D(LI).285.1General structure.285.2Error field (ERR).305.3Frame characterization field (FC).305.3.1Service provider identifier field (SPID).305.3.2Reserved bits.305.3.3Data length field (DL).305.3.4Reserved bits.315.3.5Data frame count field (DFCT).315.3.6Number of streams field (NST).315.4Stream characterization field (STC).315.4.1Individual stream characterization field (ISTCStrm).315.4.1.1Type identifier field (TID).315.4.1.2Stream length field (STL).325.4.1.3Type identifier extension field (TIDext).325.4.1.4Stream cyclic redundancy checksum flag field (CRCSTF).335.4.1.5Stream identifier field (STID).335.5End-of-header field (EOH).335.5.1Reserved bytes.335.5.2Header cyclic redundancy checksum field (CRCH).335.6Main stream data field (MST).335.6.1Individual stream data field (ISTDStrm).345.6.2Stream cyclic redundancy checksum field (CRCSTStrm).345.7End-of-frame field (EOF).345.8STI-D(LI) time stamp field (TIST).34SIST EN 300 797:2000
ETSIEN 300 797 V1.1.1 (1999-02)45.9Details of the individual streams carried in the MST.345.9.1MSC sub-channel streams.345.9.1.1MSC audio stream.345.9.1.2MSC data stream.345.9.1.3MSC packet mode stream.345.9.2MSC sub-channel contributions.355.9.2.1MSC packet mode data contributions.355.9.3FIC FIG stream.355.9.4FIC FIB stream.355.9.5In-house data.356Logical definition of the STI Control Part STI-C(LI).366.1General Structure.366.2Message handling.376.2.1Data Exchange Sessions.376.3STI-C(LI) message set.386.4Action messages.416.4.1General rules to use action messages.426.4.2RCONFIG messages.426.4.2.1RCONFIG REQ.436.4.2.2RCONFIG DEF.436.4.2.3RCONFIG INF.446.4.2.4RCONFIG CAN.446.4.2.5RCONFIG ACK.456.4.2.6RCONFIG ERR.456.5Configuration messages.466.5.1General rules to use configuration messages.476.5.2CONFDEF messages.486.5.2.1CONFDEF INF.486.5.2.2CONFDEF DEF.496.5.2.3CONFDEF END.496.5.2.4CONFDEF DEL.506.5.2.5CONFDEF ERR.506.5.3SUBCHAN messages.516.5.3.1SUBCHAN DEF.516.5.4USESTRM messages.526.5.4.1USESTRM DEF.526.5.5CMPNENT messages.536.5.5.1CMPNENT DEF.546.5.6SERVICE messages.556.5.6.1SERVICE DEF.556.5.7USEFIGF messages.566.5.7.1USEFIGF DEF.566.6FIG file messages.566.6.1General rules to use FIG file messages.576.6.2FIGFILE messages.576.6.2.1FIGFILE INF.586.6.2.2FIGFILE DEF.586.6.2.3FIGFILE REC.596.6.2.4FIGFILE END.596.6.2.5FIGFILE DEL.596.6.2.6FIGFILE SEL.606.6.2.7FIGFILE DES.606.6.2.8FIGFILE ERR.616.7FIB grid messages.616.7.1General rules to use FIBGRID messages.626.7.2FIBGRID messages.626.7.2.1FIBGRID INF.636.7.2.2FIBGRID DEF.636.7.2.3FIBGRID REC.636.7.2.4FIBGRID END.64SIST EN 300 797:2000
ETSIEN 300 797 V1.1.1 (1999-02)56.7.2.5FIBGRID ACT.646.7.2.6FIBGRID ERR.656.8Resource messages.666.8.1General rules to use resource messages.666.8.2RESOURC messages.676.8.2.1RESOURC INF.676.8.2.2RESOURC DEF.676.8.2.3RESOURC END.686.8.2.4RESOURC ERR.686.8.3CHANCAP messages.696.8.3.1CHANCAP DEF.696.8.4STLIMIT messages.706.8.4.1STLIMIT DEF.706.8.5IDALLOC messages.716.8.5.1IDALLOC DEF.716.8.6IDLIMIT messages.726.8.6.1IDLIMIT DEF.736.8.7PACKCON messages.746.8.7.1PACKCON DEF.746.8.8 FIGBLCK messages.756.8.8.1FIGBLCK DEF.756.8.9ANNSEND messages.766.8.9.1ANNSEND DEF.766.9Information messages.776.9.1General rules to use information messages.786.9.2CONINFO messages.786.9.2.1CONINFO INF.786.9.2.2CONINFO DEF.786.9.3CONNAME messages.796.9.3.1CONNAME INF.796.9.3.2CONNAME DEF.796.9.3.3CONNAME REC.806.9.3.4CONNAME END.806.9.3.5CONNAME ERR.806.9.4FIGINFO messages.816.9.4.1FIGINFO INF.816.9.4.2FIGINFO DEF.816.9.5FIGNAME messages.826.9.5.1FIGNAME INF.826.9.5.2FIGNAME DEF.826.9.5.3FIGNAME REC.836.9.5.4FIGNAME END.836.9.5.5FIGNAME ERR.836.9.6COUNTER messages.846.9.6.1COUNTER INF.846.9.6.2COUNTER DEF.846.10Supervision Messages.856.10.1General rules for the use of supervision messages.866.10.2PRERROR messages.866.10.2.1PRERROR GBG.866.10.2.2PRERROR UKN.866.10.2.3PRERROR SYN.876.10.2.4PRERROR SEM.876.10.2.5PRERROR PRT.886.10.3ALARMST messages.896.10.3.1ALARMST INF.896.10.3.2ALARMST DEF.896.10.4STERROR messages.906.10.4.1STERROR INF.906.10.4.2STERROR DEF.91SIST EN 300 797:2000
ETSIEN 300 797 V1.1.1 (1999-02)67Transport Adaptation for the STI control part STI-C(TA).927.1General structure.927.1.1STI-C(TA) on synchronous physical links.927.1.2STI-C(TA) on asynchronous physical links.937.2The data link layer.947.2.1Start field (START).947.2.2Network packet.947.2.3Cyclic redundancy checksum field (CRC).947.2.4End field (END).947.2.5Data link packet handling.947.2.5.1Packet transmission.947.2.5.2Packet reception.947.3Padding character.947.4The network layer.947.4.1Source address field (SAD).957.4.2Destination address field (DAD).957.4.3Transport packet.957.4.4Separator fields (SEP).957.4.5Network packet handling.957.4.5.1Packet transmission.957.4.5.2Packet reception.957.5The transport layer.957.5.1Packet number (PKTNUM).957.5.2Acknowledge Number (ACKNUM).967.5.3Repetition Index (REP).967.5.4Acknowledge field (ACK).967.5.5Flag field (FLAG).967.5.6Logical packet.967.5.7Separator fields (SEP).967.5.8Transport packet handling.967.5.8.1Opening a connection.977.5.8.2Closing a connection.977.5.8.3Transmission on an open connection.987.5.8.4Reception on an open connection.987.6The logical layer.987.6.1STI-C(LI).987.6.2Logical packet handling.997.6.2.1Packet transmission.997.6.2.2Packet reception.998Generic transport frame STI(PI, X).998.1General.998.2Adaptation of the logical layer.998.2.1Synchronization field (SYNC).1018.2.1.1Error field (ERR).1018.2.1.2Frame synchronization field (FSYNC).1018.2.2Transport frame header field (TFH).1028.2.2.1Data frame size field (DFS).1028.2.2.2Control frame size field (CFS).1028.2.3Data frame field (DF).1028.2.3.1STI-D(LI) data field (D-LIDATA).1028.2.3.2Data frame padding field (DFPD).1028.2.4Control frame field (CF).1028.2.5Frame padding field (FRPD).1029Physical Interfaces for synchronous links.1039.1G.703 interfaces, STI(PI, G.703).1039.1.1General description.1039.1.2Adaptation of the STI(PI, X) to the STI(PI, G.703).1039.1.3Physical interface.1039.2V.11 interface, STI(PI, V.11).103SIST EN 300 797:2000
ETSIEN 300 797 V1.1.1 (1999-02)79.2.1General description.1039.2.2Adaptation of the STI(PI, X) to the STI(PI, V.11).1039.2.3Physical interface.1049.3WG1/WG2 interface, STI(PI, WG1/2).1049.3.1General description.1049.3.2Adaptation of the STI(PI, X) to the STI(PI, WG1/2).1049.3.3Adaptation to the WG1/2 frame structure.1059.3.4Physical interface.1059.4IEC 958 interface, STI(PI, IEC958).1059.4.1General description.1059.4.2Adaptation of the STI(PI, X) to the STI(PI, IEC958).1059.4.3Adaptation to the IEC 958 frame structure.1069.4.4Physical interface.1069.5G.704 interface with error protection, STI(PI, G.704/1).1079.5.1General description.1079.5.2Transparency of STI(PI, G.704/1) layer to STI-D(LI).1079.5.2.1Transparency of STI(PI, G.704/1) 5592 layer to STI(PI, X).1079.5.2.2Transparency of STI(PI, G.704/1)5376 layer to STI(PI, X).1079.5.3STI(PI, G.704/1) structure.1089.5.3.1G.704 reserved bytes.1089.5.3.2STI(PI, G.704/1) reserved bytes.1089.5.3.2.1Multiframe management byte, Mbl,s.1099.5.3.2.2Multiframe supervision byte, Sbl,s.1119.5.4STI(PI, G.704/1) multiframe generation.1119.5.4.1General description.1119.5.4.2Error coding and interleaving for STI(PI, G.704/1)5592.1129.5.4.2.1Coding array formation.1129.5.4.2.2Interleaving.1129.5.4.2.3Output array formation.1139.5.4.3Error coding and interleaving for STI(PI, G.704/1)5376.1139.5.4.3.1Coding array formation.1139.5.4.3.2Interleaving.1149.5.4.3.3Output array formation.1149.5.5Order of data transmission.1149.5.6Error protection code.1149.5.7Synchronization.1149.5.7.1Synchronization of G.704 frames.1149.5.7.2Synchronization of STI(PI, G.704/1) multiframes.1159.5.8Physical interface.1159.5.9Modifying the STI-D(LI) ERR field.1159.6G.704 interface without error protection, STI(PI, G.704/2).1189.6.1General description.1189.6.2Adaptation of the STI(PI, X) to the STI(PI, G.704/2).1189.6.3Adaptation to the G.704 frame structure.1189.6.3.1G.704 reserved bytes.1189.6.3.2STI(PI, G.704/2) generation.1189.6.3.2.1Output array formation.1189.6.3.2.2Order of data transmission.1199.6.3.2.3Synchronization of G.704 frames.1199.6.4Physical interface.1199.7H.221 interfaces, STI(PI, H.221).1209.7.1General description.1209.7.2Adaptation of the STI(PI, X) to the STI(PI, H.221).
...