SIST EN 300 797 V1.2.1:2006
(Main)Digital Audio Broadcasting (DAB); Distribution interfaces; Service Transport Interface (STI)
- Abstract
The present document establishes a standard method for transporting Service components (audio and data) produced by Service providers at their own studios to the DAB multiplexing equipment located at the Ensemble provider's centre. EN 300 401 [1] established a broadcasting standard for a DAB system. Broadcasters who implement DAB networks require methods for transporting DAB signals, or the component parts of a DAB signal, between studios, where the programme or data service originates, and the transmitter sites from which the signal will be radiated. The network of circuits connecting the studios to the Ensemble provider's ensemble multiplexer is generally known as the Collection Network. The network of circuits connecting the ensemble multiplexer to the transmitters is generally known as the Distribution Network.
The present document is applicable to Collection Networks used in a DAB System. It describes the characteristics of a signal suitable for transporting Service Components, Service Information and control data between a Service provider and an Ensemble provider. The interface is suitable for use on a number of different physical media and telecommunication networks. Provision is made for the inclusion of appropriate error detection and correction and for the management of network transit delay.
- Status
- Published
- Publication Date
- 28-Feb-2006
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Mar-2006
- Due Date
- 01-Mar-2006
- Completion Date
- 01-Mar-2006
- Mandate
- T-244
SIST EN 300 797 V1.2.1:2006 is the Slovenian edition of ETSI EN 300 797 V1.2.1 for Digital Audio Broadcasting (DAB) distribution interfaces. It specifies the Service Transport Interface (STI) used to carry audio and data service components, Service Information and control data from a Service provider to an Ensemble provider in a DAB collection network. In practice, it tells broadcasters and network engineers how to format the data part, the control part and the physical transport options.
What does SIST EN 300 797 V1.2.1:2006 specify?
SIST EN 300 797 V1.2.1:2006 covers the collection-network side of a DAB system, where service content moves from studios to the Ensemble provider's multiplexing equipment. It is aimed at the link between the Service provider and the Ensemble provider, not at the radiated transmitter path.
The document also explains how the STI can run over different physical media and telecommunication networks. It includes provisions for error detection and correction, and for managing transit delay, which matters when a service must arrive in step with a planned multiplex or with a shared time reference.
| Annex | What it covers |
|---|---|
| Annex A | CRC word calculation for the STI |
| Annex B | Timestamp coding and mapping into STI layers |
| Annex C | Definition of the WG1/2 interface |
| Annex D | Coding of NASC data |
| Annex E | DAB multiplex configuration management and STI reconfiguration procedure |
| Annex F | Delay between Service provider and users, timestamp setting and multicasting |
| Annex G | Examples of the STI-C(TA) protocol |
| Annex H | Use of STI(PI, G.704/1) on T1 networks |
| Annex I | Bibliography |
What are the key requirements of SIST EN 300 797 V1.2.1:2006?
The logical model and frame handling
SIST EN 300 797 V1.2.1:2006 defines STI as a point-to-point interface between an upstream entity (UE) and a downstream entity (DE). The STI-D(LI) part carries broadcast data downstream, while the STI-C(LI) part carries control information in both directions. This split matters because the service payload and the management traffic are handled differently.
Clause 3 fixes the basic notation needed to read the rest of the standard. Bytes are transmitted in sequence with the lowest numbered byte first, and reserved bits are marked as Rfa or Rfu, so implementers know which bits must be left untouched and which may change in future revisions.
STI-D(LI): the data part
Clause 5 defines STI-D(LI) as 24 ms logical frames. Each frame includes status, header, stream description, payload, end-of-frame and timestamp fields, so the receiving side can identify each frame, parse its contents and place them into the DAB multiplex correctly.
The frame characterization field carries the Service provider identifier (SPID), the Data length field (DL), the Data frame count field (DFCT) and the Number of streams field (NST). In practice, that tells the receiver who sent the frame, how large it is, how to track sequence progression and how many individual streams are inside it.
The stream characterization field describes each stream with a Type identifier (TID), Stream length field (STL), Type identifier extension field (TIDext), Stream cyclic redundancy checksum flag field (CRCSTF) and Stream identifier field (STID). TIDext distinguishes cases such as MSC audio stream, MSC data stream, MSC packet mode stream and MSC packet mode contribution, so the receiver can decode the payload in the right way and know whether a stream checksum is present.
Clause 5.9 maps the actual content types carried in the main stream data field (MST). It covers MSC audio streams, MSC data streams, MSC packet mode streams, MSC packet mode data contributions, FIC FIG streams, FIC FIB streams and in-house data. For an implementer, this is the practical checklist for matching each service component to the correct transport format.
The standard also supports both synchronous and asynchronous insertion of FIBs. When asynchronous insertion is used, the Ensemble provider may delay insertion until capacity is available in the Fast Information Channel (FIC), which gives flexibility when the multiplex is busy.
STI-C(LI): the control and management part
Clause 6 defines STI-C(LI) as asynchronous, bidirectional communication between UE and DE. Its message classes cover action, configuration, FIG file, FIB grid, resource, information and supervision traffic. That matters because each task in a live DAB network has its own message family.
Reconfiguration is handled by the RCONFIG messages. The two sides exchange a named configuration and a reconfiguration instant, then confirm, cancel or report an error. In practice, this gives the operator a controlled way to move from one multiplex configuration to another at an agreed time.
Configuration messages are defined in a hierarchy: sub-channel definition first, then stream definition, component definition, service definition and FIG file use definition. This order helps catch errors early because later items can only refer to items already defined.
Resource messages are used to monitor limited ensemble resources such as Main Service Channel capacity, sub-channel identifiers and packet settings. The Ensemble provider allocates those resources, and the upstream side uses the messages to see what is available and what is already in use.
Information and supervision messages report capabilities, status, protocol errors and alarm conditions. They are the operational side of STI-C(LI): they let a network operator see configuration counts, file names, counters and current alarm state without touching the data path.
STI-C(TA), STI(PI, X) and the physical links
Clause 7 defines STI-C(TA), the transport adaptation used to move STI-C(LI) safely and reliably. It adds framing, addressing, packet numbering, acknowledgement and repetition, and it is designed so the control messages arrive error-free and in the order sent. The transport layer can repeat a packet up to ten times, which gives a concrete mechanism for coping with an impaired link.
Clause 8 defines the generic transport frame STI(PI, X). It is a 24 ms frame with SYNC, TFH, DF, CF and FRPD fields, and it can carry STI-D(LI), STI-C(TA), or both. In practical terms, this is the common wrapper that lets the standard adapt to different physical media.
Clauses 9 and 10 map STI(PI, X) to actual physical interfaces, including G.703, V.11, WG1/WG2, IEC 60958, G.704 with and without error protection, H.221 and V.24. These clauses are what equipment designers use when they choose the port type, framing method and electrical interface for a collection network.
What terms does SIST EN 300 797 V1.2.1:2006 define?
- Service Transport Interface (STI) - the DAB interface that links a Service provider and an Ensemble provider for service transport and control exchange.
- STI-D(LI) - the logical data part of STI, carrying broadcast frames downstream.
- STI-C(LI) - the logical control part of STI, carrying configuration, reconfiguration, monitoring and supervision messages in both directions.
- STI-C(TA) - the transport adaptation for STI-C(LI), adding packet handling, addressing and retransmission.
- Upstream entity (UE) - the source side of the logical interface, typically the Service provider.
- Downstream entity (DE) - the receiving side of the logical interface, typically the Ensemble provider.
- Fast Information Block (FIB) - a unit of Fast Information Channel content that can be inserted synchronously or asynchronously.
- Fast Information Group (FIG) - a Fast Information Channel information group that can be exchanged and managed through FIG-related messages.
Who uses SIST EN 300 797 V1.2.1:2006?
Service providers use this standard to format studio-originated audio, data and information services for delivery into a DAB multiplex. They also use it when they need to define reconfiguration timing or end-to-end delay.
Ensemble providers use it to receive service components, allocate shared resources and manage multiplex reconfiguration. It is also used by broadcasters, network engineers and equipment vendors who design or operate DAB collection networks and the interfaces between studios, transport links and multiplexers.
Quality managers and buyers use it to check whether a proposed DAB interface supports the needed link type, message handling and timing control for their network architecture.
Which standards are used with SIST EN 300 797 V1.2.1:2006?
- EN 300 401 [1] - the base DAB system standard, used here for the DAB signal model, definitions and multiplex configuration information.
- EN 300 798 [2] and ETS 300 799 [3] - companion DAB interface documents referenced in the introduction as part of the wider interface set.
- ITU-T Recommendation V.28 [10] - the electrical characteristics for unbalanced double-current interchange circuits.
- ITU-T Recommendation H.221 [11] - the frame structure used for the H.221 physical interface adaptation.
- ITU-T Recommendation H.242 [12] - the signalling protocol used to manage the H.221 interface.
- ITU-T Recommendations G.703, G.704, V.11, V.24 and X.24, and IEC 60958 - the physical and framing bases used in the synchronous and asynchronous interface clauses.
What does the SIST EN 300 797 V1.2.1:2006 document contain?
The document contains the STI-D(LI) frame structure, field definitions and stream mapping rules for the DAB data part. It also contains the STI-C(LI) message sets for configuration, reconfiguration, resource control, information exchange and supervision.
It includes the STI-C(TA) packet handling rules, the generic 24 ms transport frame STI(PI, X), and interface adaptations for the named synchronous and asynchronous links. Annexes add the CRC method, timestamp coding, WG1/2 details, NASC coding, reconfiguration procedures, delay handling, example protocol exchanges and the T1 variant of G.704/1.
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 V1.2.1:2006 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: The present document establishes a standard method for transporting Service components (audio and data) produced by Service providers at their own studios to the DAB multiplexing equipment located at the Ensemble provider's centre. EN 300 401 [1] established a broadcasting standard for a DAB system. Broadcasters who implement DAB networks require methods for transporting DAB signals, or the component parts of a DAB signal, between studios, where the programme or data service originates, and the transmitter sites from which the signal will be radiated. The network of circuits connecting the studios to the Ensemble provider's ensemble multiplexer is generally known as the Collection Network. The network of circuits connecting the ensemble multiplexer to the transmitters is generally known as the Distribution Network. The present document is applicable to Collection Networks used in a DAB System. It describes the characteristics of a signal suitable for transporting Service Components, Service Information and control data between a Service provider and an Ensemble provider. The interface is suitable for use on a number of different physical media and telecommunication networks. Provision is made for the inclusion of appropriate error detection and correction and for the management of network transit delay.
The present document establishes a standard method for transporting Service components (audio and data) produced by Service providers at their own studios to the DAB multiplexing equipment located at the Ensemble provider's centre. EN 300 401 [1] established a broadcasting standard for a DAB system. Broadcasters who implement DAB networks require methods for transporting DAB signals, or the component parts of a DAB signal, between studios, where the programme or data service originates, and the transmitter sites from which the signal will be radiated. The network of circuits connecting the studios to the Ensemble provider's ensemble multiplexer is generally known as the Collection Network. The network of circuits connecting the ensemble multiplexer to the transmitters is generally known as the Distribution Network. The present document is applicable to Collection Networks used in a DAB System. It describes the characteristics of a signal suitable for transporting Service Components, Service Information and control data between a Service provider and an Ensemble provider. The interface is suitable for use on a number of different physical media and telecommunication networks. Provision is made for the inclusion of appropriate error detection and correction and for the management of network transit delay.
SIST EN 300 797 V1.2.1:2006 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 V1.2.1:2006 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 V1.2.1:2006 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-marec-2006
Digitalna zvokovna radiodifuzija (DAB) – Vmesniki za razpošiljanje – Vmesnik za
prenos storitev (STI)
Digital Audio Broadcasting (DAB); Distribution interfaces; Service Transport Interface
(STI)
Ta slovenski standard je istoveten z: EN 300 797 Version 1.2.1
ICS:
33.170 Televizijska in radijska Television and radio
difuzija broadcasting
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
European Standard (Telecommunications series)
Digital Audio Broadcasting (DAB);
Distribution interfaces;
Service Transport Interface (STI)
European Broadcasting Union Union Européenne de Radio-Télévision
EBU·UER
2 ETSI EN 300 797 V1.2.1 (2005-05)
Reference
REN/JTC-DAB-37
Keywords
audio, broadcasting, DAB, data, digital, interface,
transport
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
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 2005.
© European Broadcasting Union 2005.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI EN 300 797 V1.2.1 (2005-05)
Contents
Intellectual Property Rights.10
Foreword.10
Introduction .11
1 Scope.13
2 References.13
3 Definitions, abbreviations, symbols and terminology.14
3.1 Definitions.14
3.2 Abbreviations.17
3.3 Symbols.18
3.3.1 Numerical ranges.18
3.3.2 Bit and byte numbering.19
3.3.3 Arithmetic operators.19
3.3.4 Logical operators.19
3.3.5 STI-C(LI) Field Types .19
3.4 Ordering of bytes and bits for transmission.19
3.5 Reserved bits.20
3.6 STI-C character set.20
3.6.1 STI-C(LI) message character set .20
3.6.2 STI-C(TA) character set .20
4 Overview of the Service Transport Interface definition.20
4.1 Conceptual model of the Service Transport Interface .20
4.2 The logical model of the STI.23
4.3 The layered model of the STI.24
4.4 The implementation model of the STI.25
4.4.1 Examples of network topologies.25
4.4.2 Hierarchical collection networks.27
4.4.3 Multicasting.27
5 Logical definition of the STI Data Part, STI-D(LI) .28
5.1 General structure.28
5.2 Error field (ERR).30
5.3 Frame characterization field (FC) .30
5.3.1 Service provider identifier field (SPID).30
5.3.2 Reserved bits.30
5.3.3 Data length field (DL).31
5.3.4 Reserved bits.31
5.3.5 Data frame count field (DFCT).31
5.3.6 Number of streams field (NST) .31
5.4 Stream characterization field (STC).31
5.4.1 Individual stream characterization field (ISTC ).31
Strm
5.4.1.1 Type identifier field (TID) .32
5.4.1.2 Stream length field (STL) .32
5.4.1.3 Type identifier extension field (TIDext) .32
5.4.1.4 Stream cyclic redundancy checksum flag field (CRCSTF).33
5.4.1.5 Stream identifier field (STID).33
5.5 End-of-header field (EOH).33
5.5.1 Reserved bytes.33
5.5.2 Header cyclic redundancy checksum field (CRCH) .33
5.6 Main stream data field (MST) .34
5.6.1 Individual stream data field (ISTD ) .34
Strm
5.6.2 Stream cyclic redundancy checksum field (CRCST ).34
Strm
5.7 End-of-frame field (EOF).34
5.8 STI-D(LI) time stamp field (TIST) .34
5.9 Details of the individual streams carried in the MST .34
ETSI
4 ETSI EN 300 797 V1.2.1 (2005-05)
5.9.1 MSC sub-channel streams .34
5.9.1.1 MSC audio stream.34
5.9.1.2 MSC data stream.35
5.9.1.3 MSC packet mode stream .35
5.9.2 MSC sub-channel contributions.35
5.9.2.1 MSC packet mode data contributions .35
5.9.3 FIC FIG stream.35
5.9.4 FIC FIB stream .35
5.9.5 In-house data.36
6 Logical definition of the STI Control Part STI-C(LI) .36
6.1 General Structure.36
6.2 Message handling.37
6.2.1 Data Exchange Sessions .38
6.3 STI-C(LI) message set.38
6.4 Action messages.40
6.4.1 General rules to use action messages.41
6.4.2 RCONFIG messages.41
6.4.2.1 RCONFIG REQ.42
6.4.2.2 RCONFIG DEF.42
6.4.2.3 RCONFIG INF.43
6.4.2.4 RCONFIG CAN.43
6.4.2.5 RCONFIG ACK.44
6.4.2.6 RCONFIG ERR.44
6.5 Configuration messages.45
6.5.1 General rules to use configuration messages .46
6.5.2 CONFDEF messages.47
6.5.2.1 CONFDEF INF.47
6.5.2.2 CONFDEF DEF.48
6.5.2.3 CONFDEF END.48
6.5.2.4 CONFDEF DEL.49
6.5.2.5 CONFDEF ERR.49
6.5.3 SUBCHAN messages.50
6.5.3.1 SUBCHAN DEF.50
6.5.4 USESTRM messages.51
6.5.4.1 USESTRM DEF.51
6.5.5 CMPNENT messages.52
6.5.5.1 CMPNENT DEF.53
6.5.6 SERVICE messages.54
6.5.6.1 SERVICE DEF.54
6.5.7 USEFIGF messages.55
6.5.7.1 USEFIGF DEF.55
6.6 FIG file messages.55
6.6.1 General rules to use FIG file messages.56
6.6.2 FIGFILE messages.56
6.6.2.1 FIGFILE INF.57
6.6.2.2 FIGFILE DEF.57
6.6.2.3 FIGFILE REC.58
6.6.2.4 FIGFILE END.58
6.6.2.5 FIGFILE DEL.58
6.6.2.6 FIGFILE SEL.59
6.6.2.7 FIGFILE DES.59
6.6.2.8 FIGFILE ERR.60
6.7 FIB grid messages .60
6.7.1 General rules to use FIBGRID messages.61
6.7.2 FIBGRID messages.61
6.7.2.1 FIBGRID INF.62
6.7.2.2 FIBGRID DEF.62
6.7.2.3 FIBGRID REC.62
6.7.2.4 FIBGRID END.63
6.7.2.5 FIBGRID ACT.63
6.7.2.6 FIBGRID ERR.64
ETSI
5 ETSI EN 300 797 V1.2.1 (2005-05)
6.8 Resource messages.65
6.8.1 General rules to use resource messages .65
6.8.2 RESOURC messages.66
6.8.2.1 RESOURC INF.66
6.8.2.2 RESOURC DEF.66
6.8.2.3 RESOURC END.67
6.8.2.4 RESOURC ERR.67
6.8.3 CHANCAP messages.67
6.8.3.1 CHANCAP DEF.68
6.8.4 STLIMIT messages.68
6.8.4.1 STLIMIT DEF.68
6.8.5 IDALLOC messages.69
6.8.5.1 IDALLOC DEF.69
6.8.6 IDLIMIT messages.71
6.8.6.1 IDLIMIT DEF.72
6.8.7 PACKCON messages.73
6.8.7.1 PACKCON DEF.73
6.8.8 FIGBLCK messages.74
6.8.8.1 FIGBLCK DEF.74
6.8.9 ANNSEND messages.75
6.8.9.1 ANNSEND DEF.75
6.9 Information messages.76
6.9.1 General rules to use information messages.77
6.9.2 CONINFO messages.77
6.9.2.1 CONINFO INF.77
6.9.2.2 CONINFO DEF.77
6.9.3 CONNAME messages.78
6.9.3.1 CONNAME INF.78
6.9.3.2 CONNAME DEF.78
6.9.3.3 CONNAME REC.79
6.9.3.4 CONNAME END.79
6.9.3.5 CONNAME ERR.79
6.9.4 FIGINFO messages.80
6.9.4.1 FIGINFO INF.80
6.9.4.2 FIGINFO DEF.80
6.9.5 FIGNAME messages.81
6.9.5.1 FIGNAME INF.81
6.9.5.2 FIGNAME DEF.81
6.9.5.3 FIGNAME REC.82
6.9.5.4 FIGNAME END.82
6.9.5.5 FIGNAME ERR.82
6.9.6 COUNTER messages.83
6.9.6.1 COUNTER INF.83
6.9.6.2 COUNTER DEF.83
6.10 Supervision Messages.84
6.10.1 General rules for the use of supervision messages.85
6.10.2 PRERROR messages.85
6.10.2.1 PRERROR GBG.85
6.10.2.2 PRERROR UKN.85
6.10.2.3 PRERROR SYN.86
6.10.2.4 PRERROR SEM.86
6.10.2.5 PRERROR PRT.87
6.10.3 ALARMST messages.88
6.10.3.1 ALARMST INF.88
6.10.3.2 ALARMST DEF.88
6.10.4 STERROR messages.89
6.10.4.1 STERROR INF.89
6.10.4.2 STERROR DEF.90
7 Transport Adaptation for the STI control part STI-C(TA).91
7.1 General structure.91
7.1.1 STI-C(TA) on synchronous physical links .91
ETSI
6 ETSI EN 300 797 V1.2.1 (2005-05)
7.1.2 STI-C(TA) on asynchronous physical links.92
7.2 The data link layer.93
7.2.1 Start field (START) .93
7.2.2 Network packet.93
7.2.3 Cyclic redundancy checksum field (CRC).93
7.2.4 End field (END).93
7.2.5 Data link packet handling .93
7.2.5.1 Packet transmission.93
7.2.5.2 Packet reception.93
7.3 Padding character.93
7.4 The network layer.93
7.4.1 Source address field (SAD) .94
7.4.2 Destination address field (DAD) .94
7.4.3 Transport packet.94
7.4.4 Separator fields (SEP).94
7.4.5 Network packet handling .94
7.4.5.1 Packet transmission.94
7.4.5.2 Packet reception.94
7.5 The transport layer.94
7.5.1 Packet number (PKTNUM).94
7.5.2 Acknowledge Number (ACKNUM).95
7.5.3 Repetition Index (REP).95
7.5.4 Acknowledge field (ACK).95
7.5.5 Flag field (FLAG).95
7.5.6 Logical packet.95
7.5.7 Separator fields (SEP).95
7.5.8 Transport packet handling .95
7.5.8.1 Opening a connection.96
7.5.8.2 Closing a connection.96
7.5.8.3 Transmission on an open connection .97
7.5.8.4 Reception on an open connection.97
7.6 The logical layer.97
7.6.1 STI-C(LI).97
7.6.2 Logical packet handling.98
7.6.2.1 Packet transmission.98
7.6.2.2 Packet reception.98
8 Generic transport frame STI(PI, X).98
8.1 General.98
8.2 Adaptation of the logical layer .98
8.2.1 Synchronization field (SYNC).100
8.2.1.1 Error field (ERR) .100
8.2.1.2 Frame synchronization field (FSYNC) .100
8.2.2 Transport frame header field (TFH).101
8.2.2.1 Data frame size field (DFS) .101
8.2.2.2 Control frame size field (CFS).101
8.2.3 Data frame field (DF) .101
8.2.3.1 STI-D(LI) data field (D-LIDATA) .101
8.2.3.2 Data frame padding field (DFPD).101
8.2.4 Control frame field (CF) .101
8.2.5 Frame padding field (FRPD) .101
9 Physical Interfaces for synchronous links .102
9.1 G.703 interfaces, STI(PI, G.703).102
9.1.1 General description.102
9.1.2 Adaptation of the STI(PI, X) to the STI(PI, G.703).102
9.1.3 Physical interface.102
9.2 V.11 interface, STI(PI, V.11) .102
9.2.1 General description.102
9.2.2 Adaptation of the STI(PI, X) to the STI(PI, V.11).102
9.2.3 Physical interface.103
9.3 WG1/WG2 interface, STI(PI, WG1/2).103
ETSI
7 ETSI EN 300 797 V1.2.1 (2005-05)
9.3.1 General description.103
9.3.2 Adaptation of the STI(PI, X) to the STI(PI, WG1/2).103
9.3.3 Adaptation to the WG1/2 frame structure.104
9.3.4 Physical interface.104
9.4 IEC 60958 interface, STI(PI, IEC 60958) .104
9.4.1 General description.104
9.4.2 Adaptation of the STI(PI, X) to the STI(PI, IEC 60958).104
9.4.3 Adaptation to the IEC 60958 frame structure .105
9.4.4 Physical interface.105
9.5 G.704 interface with error protection, STI(PI, G.704/1) .106
9.5.1 General description.106
9.5.2 Transparency of STI(PI, G.704/1) layer to STI-D(LI).106
9.5.2.1 Transparency of STI(PI, G.704/1) layer to STI(PI, X) .106
5 592
9.5.2.2 Transparency of STI(PI, G.704/1) layer to STI(PI, X).106
5 376
9.5.3 STI(PI, G.704/1) structure .107
9.5.3.1 G.704 reserved bytes.107
9.5.3.2 STI(PI, G.704/1) reserved bytes.107
9.5.3.2.1 Multiframe management byte, M .108
bl,s
9.5.3.2.2 Multiframe supervision byte, S .110
bl,s
9.5.4 STI(PI, G.704/1) multiframe generation.110
9.5.4.1 General description.110
9.5.4.2 Error coding and interleaving for STI(PI, G.704/1) .111
5 592
9.5.4.2.1 Coding array formation.111
9.5.4.2.2 Interleaving.111
9.5.4.2.3 Output array formation.112
9.5.4.3 Error coding and interleaving for STI(PI, G.704/1) .112
5 376
9.5.4.3.1 Coding array formation.112
9.5.4.3.2 Interleaving.113
9.5.4.3.3 Output array formation.113
9.5.5 Order of data transmission.113
9.5.6 Error protection code.
...