SIST EN 302 550-1-1 V1.1.1:2010
(Main)Satellite Earth Stations and Systems (SES) - Satellite Digital Radio (SDR) Systems - Part 1: Physical Layer of the Radio Interface - Sub-part 1: Outer Physical Layer
Satellite Earth Stations and Systems (SES) - Satellite Digital Radio (SDR) Systems - Part 1: Physical Layer of the Radio Interface - Sub-part 1: Outer Physical Layer
The present document concerns the radio interface of SDR broadcast receivers. It specifies the functionality of the outer physical layer. It allows implementing this part of the system in an interoperable way.
Satelitske zemeljske postaje in sistemi (SES) - Satelitski digitalni radijski sistemi - 1. del: Fizična plast radijskega vmesnika - 1. poddel: Zunanja fizična plast
Pričujoči dokument zadeva radijski vmesnik SDR radiodifuzijskih sprejemnikov. Določa funkcionalnost zunanje fizične plasti. Dopušča izvajanje tega dela sistema v interoperabilnem načinu.
General Information
Standards Content (Sample)
Draft ETSI EN 302 550-1-1 V1.1.0 (2009-07)
European Standard (Telecommunications series)
Satellite Earth Stations and Systems (SES);
Satellite Digital Radio (SDR) Systems;
Part 1: Physical Layer of the Radio Interface;
Sub-part 1: Outer Physical Layer
2 Draft ETSI EN 302 550-1-1 V1.1.0 (2009-07)
Reference
DEN/SES-00312-1-1
Keywords
digital, layer 1, radio, satellite
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 2009.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
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.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 Draft ETSI EN 302 550-1-1 V1.1.0 (2009-07)
Contents
Intellectual Property Rights . 5
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Symbols and abbreviations . 7
3.1 Symbols . 7
3.2 Abbreviations . 7
4 Outer physical layer. 7
4.1 Overview . 7
4.2 Interfacing to Service Layer (SL) . 11
4.3 S-TS to OPL adaptation layer: S-TS encapsulation . 12
4.3.1 PF infoword format for S-TS stream type 0 (dummy packet) . 13
4.3.2 PF infoword format for S-TS stream type 1 (transparent) . 13
4.3.3 PF infoword format for S-TS stream type 2 (MPEG-TS) . 13
4.3.4 PF infoword format for S-TS stream type 3 (IP stream) . 15
4.4 PL FEC: turbo code . 16
4.4.1 Interface to OPL encapsulation . 16
4.4.2 Turbo encoder . 17
4.4.3 Turbo code termination . 20
4.4.4 Turbo Interleavers . 22
4.4.5 Output of turbo encoder . 23
4.4.6 FEC Parameter signalling . 23
4.4.7 Diversity combining . 24
4.4.8 FEC Parameters for the signalling pipe . 24
4.5 Mixer . 24
4.6 Segmenter and Slot demultiplexer . 25
4.7 Disperser. 26
4.8 Collector . 27
4.9 C-TS multiplexer . 28
4.10 Configuration of the OPL . 29
4.10.1 Signalling pipe . 29
4.10.1.1 Encoding and interleaving of signalling pipe . 29
4.10.1.2 SOF Preamble . 30
4.10.1.3 Format of the signalling pipe infoword . 30
4.10.2 Partitioning of the C-TS multiplex . 35
4.10.3 S-TS schedule and slot allocation . 36
4.10.4 S-TS re-scheduling and slot re-allocation . 37
4.10.5 Birth/death of S-TS . 37
4.10.6 S-TS ID . 37
4.10.7 Calculation of the disperser profile . 38
4.10.8 Configuration of the tail pipe . 39
4.10.9 Unused pipes . 39
4.10.10 Announcing reconfigurations and reschedulings . 39
4.10.11 Pipe reconfiguration . 40
4.11 Network aspects . 44
Annex A (normative): Number format definitions . 46
A.1 Number format and transmission order . 46
A.2 SI-Prefix Notation . 46
ETSI
4 Draft ETSI EN 302 550-1-1 V1.1.0 (2009-07)
A.3 Default Settings . 46
Annex B (normative): Calculation of the CRC word . 47
Annex C (informative): Bibliography . 48
History . 49
ETSI
5 Draft ETSI EN 302 550-1-1 V1.1.0 (2009-07)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Satellite Earth
Stations and Systems (SES), and is now submitted for the Public Enquiry phase of the ETSI standards Two-step
Approval Procedure.
The present document is part 1, sub-part 1 of a multi-part deliverable covering Satellite Digital Radio (SDR), as
identified below:
Part 1: "Physical Layer of the Radio Interface";
Sub-part 1: "Outer Physical Layer";
Sub-part 2: "Inner Physical Layer Single Carrier Modulation";
Sub-part 3: "Inner Physical Layer Multi Carrier Modulation".
Proposed national transposition dates
Date of latest announcement of this EN (doa): 3 months after ETSI publication
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 6 months after doa
Date of withdrawal of any conflicting National Standard (dow): 6 months after doa
Introduction
TC SES is producing standards and other deliverables for Satellite Digital Radio (SDR) systems. An SDR system
enables broadcast to fixed and mobile receivers through satellites and complementary terrestrial transmitters.
Functionalities, architecture and technologies of such systems are described in TR 102 525 [i.1].
Several existing and planned ETSI standards specify parts of the SDR system, with the aim of interoperable
implementations. The physical layer of the radio interface (air interface) is divided up into the outer physical layer, the
inner physical layer with a single carrier modulation, and the inner physical layer with multi carrier modulation. These
parts can be used all together in SDR compliant equipment, or in conjunction with other existing and future
specifications.
The present document specifies the outer physical layer. The inner physical layer with single carrier modulation is
specified in EN 302 550-1-2 [i.2], and with multi carrier modulation in EN 302 550-1-3 [i.3]. Guidelines for using the
physical layer standard can be found in TR 102 604 [i.4].
The physical layer specifications have previously been published as "Technical Specification (TS)" type ETSI
deliverables. The present document supersedes TS 102 550 [i.5] and is recommended for new implementations.
ETSI
6 Draft ETSI EN 302 550-1-1 V1.1.0 (2009-07)
1 Scope
The present document concerns the radio interface of SDR broadcast receivers. It specifies the functionality of the outer
physical layer. It allows implementing this part of the system in an interoperable way.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ISO/IEC 13818-1: "Information technology - Generic coding of moving pictures and associated
audio information: Systems".
[2] ISO/IEC 11172-1: "Information technology - Coding of moving pictures and associated audio for
digital storage media at up to about 1,5 Mbit/s - Part 1: Systems".
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
[i.1] ETSI TR 102 525: "Satellite Earth Stations and Systems (SES); Satellite Digital Radio (SDR)
service; Functionalities, architecture and technologies".
[i.2] ETSI EN 302 550-1-2: "Satellite Earth Stations and Systems (SES); Satellite Digital Radio (SDR)
Systems; Part 1: Physical Layer of the Radio Interface; Sub-part 2: Inner Physical Layer Single
Carrier Modulation".
[i.3] ETSI EN 302 550-1-3: "Satellite Earth Stations and Systems (SES); Satellite Digital Radio (SDR)
Systems; Part 1: Physical Layer of the Radio Interface; Sub-part 3: Inner Physical Layer Multi
Carrier Modulation".
[i.4] ETSI TR 102 604: "Satellite Earth Stations and Systems (SES); Satellite Digital Radio (SDR)
Systems; Guidelines for the Use of the Physical Layer Standards".
[i.5] ETSI TS 102 550 (V1.3.1): "Satellite Earth Stations and Systems (SES); Satellite Digital Radio
(SDR) Systems; Outer Physical Layer of the Radio Interface".
ETSI
7 Draft ETSI EN 302 550-1-1 V1.1.0 (2009-07)
3 Symbols and abbreviations
3.1 Symbols
For the purposes of the present document, the following symbols apply:
Code rate
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AWGN Additive White Gaussian Noise
BCH Bose, Ray-Chaudhuri, Hocquenghem code
CRC Cyclic Redundancy Checksum
C-TS Channel-Transport Stream
CU Capacity Unit
FEC Forward Error Correction
ID IDentifier
IP Internet Protocol
IPL Inner Physical Layer
IU Interleaving Unit
LSB Least Significant Bit
MPEG-TS MPEG Transport Stream
MSB Most Significant Bit
MTU Maximum Transfer Unit
OPL Outer Physical Layer
PF Physical layer FEC
PFIW Physical layer FEC Info Word
PL Physical Layer
QoS Quality of Service
RFU Reserved for Future Use
SL Service Layer
SOF Start Of Frame
S-TS Service-Transport Stream
VBR Variable Bit Rate
WER Word Error Rate
4 Outer physical layer
Refer to annex A for number format definitions.
4.1 Overview
Figure 1 displays the position and the interfaces of the Outer Physical Layer (in the following denoted by OPL) inside a
complete broadcast transmission chain. The OPL connects to the Service Layer, where the interface is Service
Transport Streams (S-TS) on the one side, and on the other side to the Inner Physical Layer (IPL - described in
EN 302 550-1-2 [i.2] and EN 302 550-1-3 [i.3]), where the interfaces are Channel Transport Streams (C-TS).
ETSI
8 Draft ETSI EN 302 550-1-1 V1.1.0 (2009-07)
Figure 1: Position and interfaces of the OPL inside the transmission chain
The following table gives an overview about the terminology used for the data streaming through the system.
Description Comments
SC Service component E.g. source encoded audio or video or other data
SC-TS Service component transport stream
ES Elementary Stream ES: Elementary Stream, a generic term for one of the
coded video, coded audio or other coded data
bitstreams, cf. MPEG-1 standard
ISO/IEC 11172-1 [2].
Program A program is a collection of program In line with the definition used for MPEG standard
elements. Program elements may be ISO/IEC 13818-1 [1].
elementary streams (ES, SC-TS).
Service Set of programs and related auxiliary
information
S-TS Service transport stream Generalized term for transport stream. MPEG-TS is
one example for a service transport stream.
MPEG-TS Transport stream compliant to MPEG
standard ISO/IEC 13818-1 [1]
C-TS Channel transport stream Data stream (bit stream) representing the input to the
modulator = data stream including all redundancy
added by the FEC encoder - possibly with
time-interleaving - and carrying configuration
signalling information for the receiver.
The content of the C-TS is referred to as a C-TS
multiplex (a multiplex of encoded and interleaved
S-TS plus signalling information).
A bouquet of programs is carried by one or more
C-TS multiplexes.
ETSI
9 Draft ETSI EN 302 550-1-1 V1.1.0 (2009-07)
Description Comments
Channel RF resource The meaning "RF resource" is aligned with the
terminology used for DVB.
The functionality of the Outer Physical Layer is to provide Forward Error Correction and time interleaving for
resistance against a variety of transmission channel conditions. Different transport channels are used in the OPL to offer
the requested performance for different types of services. These transport channels are called pipes in the scope of the
present document. The OPL is configurable in terms of error protection, outage mitigation in case of signal losses,
end-to-end delay, zapping time, payload throughput and receiver complexity.
Multiple pipes can be used as described above. Each of them contains FEC, Mixer and Disperser. One special pipe
exists whose functionality is to transmit all relevant parameters to decode the other pipes. The so-called signalling pipe
is always transmitted at the lowest coderate which is 1/5. The modulation of the signalling pipe is equal to the
modulation of the data pipes.
The general block diagram of the OPL functionality is given in figure 2.
ETSI
10 Draft ETSI EN 302 550-1-1 V1.1.0 (2009-07)
Figure 2: General overview of the OPL functionality
ETSI
11 Draft ETSI EN 302 550-1-1 V1.1.0 (2009-07)
The processing, multiplexing and demultiplexing of the data in the OPL is displayed in figure 3. An S-TS scheduler
multiplexes together all S-TS contained in the pipe. The scheduler is controlled by an S-TS schedule, which determines
the number of words taken from one S-TS before the multiplexer selects the next S-TS of the pipe. After an
encapsulation, FEC encoding and mixing, the codewords (segmented into interleaver units) are demultiplexed
codeword-wise to the slots of the considered pipe, each of the slots possessing its individual disperser. After
demultiplexing a codeword to a slot, i.e. to the input of its disperser, the slot demultiplexer selects the next
slot/disperser. At the outputs of the dispersers, the dispersed codewords are multiplexed together again by the collector
to form one pipe. The slot demultiplexer and the collector always select synchronously the same slot/disperser.
IUs of one slot Dispersed IUs of
Packets of an one slot
S-TS
Slots of IUs
OPL Slots or IUs of
Disperser
S-TS i one pipe of one
Encapsulation
Mixed
PF infowords PF codewords C-TS frame
codewords
OPL
S-TS i + 1
Encapsulation
C-TS
PL FEC Mixer Segmenter Disperser
mux
... Collector
Slot
Demux
OPL S-TS
S-TS j
Encapsulation scheduler
...
Number of S-TS
Disperser
in this pipe:
Num_STS
Number of
Dispersers in this
pipe:
Pipe_Width_Slots
Figure 3: Definition of the different blocks involved in the OPL processing
4.2 Interfacing to Service Layer (SL)
The interface to the service layer is the so-called Service-Transport Stream (S-TS). For the OPL, each S-TS source is
the smallest granularity which can be processed independently.
The interface may work synchronously or asynchronously. In the case of asynchronous interface, the PL must be able to
accept at least the average data rate that is provided by the SL. Any data buffering shall be done inside the SL, such that
no data from the S-TS is lost at this interface. When the PL requests new data for transmission, the SL can either
provide the requested data to the PL or it can signal that no data is currently available. If no data is available for
transmission, the PL instead transmits dummy data that is discarded in the receiver.
Inside an S-TS, multiplexing and de-multiplexing of information shall be carried out by the service layer.
Each pipe provides a different set of transmission parameters (e.g. FEC code rate and disperser profile), and achieves a
different QoS in terms of protection against transmission errors and end-to-end delay. One pipe of the OPL may carry
several S-TS, all with the same QoS parameters.
If PL time slicing is used, each time slice is associated with one S-TS. The scheduling of the S-TS, i.e. their start
instants and lengths, inside a pipe can be adapted frequently (once per schedule/time slicing period). This opens the
possibility of handling Variable Bit Rate (VBR) transmission.
The maximum allowed payload throughput per S-TS is 3,2 Mbit/s (this corresponds to approximately 8 to 10 video
services inside one S-TS). This is the throughput that the processing chain inside the receiver (e.g. the turbo decoder)
must be able to handle at least.
ETSI
12 Draft ETSI EN 302 550-1-1 V1.1.0 (2009-07)
4.3 S-TS to OPL adaptation layer: S-TS encapsulation
The OPL is prepared to transport different types of S-TS, and a mixture of different S-TS types may be transported
simultaneously over one C-TS multiplex.
The following parameters have to be determined for each S-TS (for parameters, refer to signalling pipe in
clause 4.10.1):
• S-TS ID: identifier for the transported S-TS, that is unique for each network operator (i.e. for each
Operator_ID); observe that one S-TS may be transported over multiple instances of the PL and still have a
single unique S-TS ID; this helps, for example, for diversity combining of one S-TS transmitted over satellite
and simultaneously over terrestrial repeaters. Several rules apply for the S-TS:
- S-TS ID 0 plays a special role: this is the Service Layer configuration S-TS (the SL can signal its own
configuration via this S-TS).
- An S-TS may be fed to several C-TS multiplexes. The S-TS IDs in all of these C-TS multiplexes are
identical.
- An S-TS may not be fed to several pipes inside the same C-TS multiplex, and an S-TS may not be fed
several times to the same pipe inside one C-TS multiplex either.
- S-TS IDs must be unique over the complete network of one operator except for S-TS ID 0 which is
allowed on every C-TS multiplex.
- S-TS with an identical Operator_ID and S-TS ID can always be diversity combined (except for
S-TS ID 0).
- The length of an S-TS can be configured in a granularity of one PL infoword per C-TS frame.
• Pipe number that this S-TS is transported over.
Moreover, for the ensemble of S-TS contained inside a complete C-TS multiplex, the following parameters have to be
fixed (for parameters, refer also to signalling pipe in clause 4.10.1):
• Operator_ ID: unique identifier for the network operator.
• Partitioning of the C-TS multiplex into pipes and scheduling of the S-TS inside the pipes, i.e. what is the data
rate of one S-TS and when are the bursts of one S-TS transported.
Each S-TS is partitioned into packets to match the length of the PL FEC information word (PF infoword). The packet
size is individual for each type of S-TS. The OPL encapsulation inside the S-TS to OPL adaptation layer adapts the
length of the S-TS packets to the PF infoword length by appending a suffix to the S-TS packet. Table 1 defines the S-TS
packet length and the suffix length for different S-TS types.
Table 1: Defined S-TS type IDs
S-TS Type S-TS Type ID S-TS payload packet Suffix length Comment
Size in bytes in bits
Dummy packet 0 0 26 used for asynchronous sl/pl interface.
is discarded in receiver.
Transparent
1 1 532 26 sl has to decide what to do with this
data.
MPEG-TS 2 1 504 250 payload packet is 8 mpeg packets of
188 bytes each; additionally, a bch
code of 196 bits is applied.
IP stream 3 1 504 250 mtu of ip = 4 095 bytes with 2 bytes
additional header per packet.
RFU
4 to 7 reserved for future s-ts types.
The detailed format for the different types of S-TS is given in the following clauses. The Cyclic Redundancy Check
8 5 3 2
(CRC) polynomial, which appears in the following clauses, is x + x + x + x + x + 1 for all S-TS stream types. The
calculation of the CRC is described in annex B.
ETSI
13 Draft ETSI EN 302 550-1-1 V1.1.0 (2009-07)
4.3.1 PF infoword format for S-TS stream type 0 (dummy packet)
The format of the dummy packet is given in table 2. The insertion of a dummy packet is performed if no data was
available at the instant of processing the actual packet in the OPL.
Table 2: PF infoword format for S-TS stream type 0 (dummy packet)
Start bit Wordsize
Parameter Description Format Comment
index (bits)
1 532×U8
0 Dummy data To be filled with zeros 12 256
(1 532 bytes)
helps to bit-align the payload to
12 256 RFU 4 bits reserved for future use 4 U4
byte boundaries.
12 260 STS_ID S-TS ID 8 U8 can be chosen arbitrarily.
12 268 STS_Stream_Type_ID S-TS stream type identifier 3 U3 fixed to 0 for dummy packets.
Version number of the OPL
12 271 Encap_Ver 3 U3 fixed to 0.
encapsulation format
CRC over the 18 relevant the light grey marked bits are
12 274 HeaderCRC 8 U8
bits of the header included in the header.
Total length of PFIW 12 282
4.3.2 PF infoword format for S-TS stream type 1 (transparent)
The format of the transparent mode is given in table 3. It provides a transparent transmission of whatever payload. The
throughput capability of the transparent stream type is 1 532 bytes per PF infoword. No additional error correction or
detection except the turbo code is used; therefore, data integrity and flow control needs to be performed by the link
layer. The definition of such protocol is not included in the present document.
Table 3: PF infoword format for S-TS stream type 1 (transparent)
Start bit Wordsize
Parameter Description Format Comment
index (bits)
1 532×U8 May include counters, error
0 Payload_Packet Transparent payload packet 12 256
(1 532 bytes) correction and error detection.
Helps to bit-align the payload
12 256 RFU 4 bits reserved for future use 4 U4
to byte boundaries.
12 260 STS_ID S-TS ID 8 U8
Fixed to 1 for transparent
12 268 STS_Stream_Type_ID S-TS stream type identifier 3 U3
packets.
Version number of the OPL
12 271 Encap_Ver 3 U3 Fixed to 0.
encapsulation format
CRC over the 18 relevant The light grey marked bits are
12 274 HeaderCRC 8 U8
bits of the header included in the CRC check.
Total length of PFIW 12 282
4.3.3 PF infoword format for S-TS stream type 2 (MPEG-TS)
The format of the MPEG-TS stream mode is given in table 4. It provides a transparent transmission of up to
8 MPEG-TS packets according to ISO/IEC 13818-1 [1], each having a size of 188 bytes. If less than 8 packets are
available for transport, the missing packets are filled by MPEG-TS null packets. Additional error correction and
detection is performed by using one shortened BCH (3 057, 3 008) code each 2 MPEG-TS packets. Therefore, each PF
infoword contains 4 sections of BCH parity of 49 bits each.
As this BCH-code is a systematic code, the parity may be discarded in the receiver if this additional parity check is not
desired; however, performance is supposed to degrade in this case. On the contrary, it is a mandatory requirement on
the transmitter side to include this parity.
ETSI
14 Draft ETSI EN 302 550-1-1 V1.1.0 (2009-07)
The error correction code (overall minimum distance d = 10) is actually an outer BCH(3056, 3008, 9) code (with
min
minimum distance d = 9) concatenated by an inner single-parity check code (3057,3056,1). The BCH code is gained
min
by shortening a narrow-sense binary BCH(4095,4047,9)-Code. Concatenated encoding of (payload) message bits
m = (m ,mm,., ,m ) onto an (overall) codeword
3007 3006 1 0
c = (m ,mm,., ,m ,d ,d ,.,d ,d ,p ) is achieved as follows:
3007 3006 1 0 47 46 1 0 0
• The message bit m is gained from the temporally first bit (MSB of the temporally first byte) of the
temporally earlier MPEG-TS packet. The next message bit m corresponds to the temporally second bit (Bit
6 of the temporally first byte) of the temporally earlier MPEG-TS packet, and so on until bit m , which is
the temporally last bit (LSB of the temporally last byte) of the temporally earlier MPEG-TS packet. The
following 1 504 bits m to m are taken in the same manner from the temporally later MPEG-TS packet.
1503 0
3007 3006 48
• Multiply the message polynomial m(x) = m xm++x .+mx+m by x (the coefficients
3007 3006 1 0
of m(x) for exponents > 3 007 are all set to zero in order to shorten this BCH code; note that this corresponds
to temporally preceding the message by 1 039 zeros).
• Divide x m(x) by the BCH generator polynomial
48 44 41 37 36 34 32 29 27 26 21 17 16 13 7 5 3
g(x)=x+xx+ +x+++x x x+xx+ +xx+ +x+x+x+x+x+x+x+1
Let d(xd)=+x .+dx+ d be the remainder.
471 0
• Set the outer (i.e. BCH) codeword polynomial c (xx)(=+mx) d(x) .
o
• Calculate the single-parity check bit pc==(1x ) and set the overall codeword polynomial to
0 o
c(xc)=⋅()x x+p=xm()x+x⋅d()x+ p .
o00
Observe that the temporal transmission order of the bits of the codeword c is (m ,mm,., ,m ) for the
3007 3006 1 0
message part and (d ,dd,., ,d ,p ) for the parity part, i.e. the order is temporally descending for this BCH
4746 1 0 0
codeword-specific indexing. Note that by contrast the indexing of the bits inside the PF infoword is in temporally
ascending order, i.e. bit 0 to bit 12 281. Inside the Payload_Packet field of the PF infoword, there are four such message
parts (each representing 2 MPEG-TS packets or 376 bytes); the four associated parity parts are transmitted in the field
Parity_Parts in the same order.
Table 4: PF infoword format for S-TS stream type 2 (MPEG-TS)
Start bit Wordsize
Parameter Description Format Comments
index (bits)
1 504×U8
0 Payload_Packet 12 032
Payload packet (1 504 bytes)
Four times the 49 parity bits
of a shortened
12 032 Parity_Parts Parity bits for Error 196 4×U49 BCH(3 057,3 008)-code,
Detection or Outer Error which each protects 2
Correction Code MPEG-TS packets.
32 bits reserved for future Helps to bit-align the payload
12 228 RFU 32 U32
use to byte boundaries.
12 260 STS_ID S-TS ID 8 U8
12 268 STS_Stream_Type_ID S-TS stream type identifier 3 U3 Fixed to 2 for MPEG-TS.
Version number of the OPL
12 271 Encap_Ver 3 U3
encapsulation format Fixed to 0.
CRC over the 46 relevant The light grey marked bits are
12 274 CRC_Bits 8 U8
bits of the header included in the CRC check.
Total length of PFIW 12 282
ETSI
15 Draft ETSI EN 302 550-1-1 V1.1.0 (2009-07)
4.3.4 PF infoword format for S-TS stream type 3 (IP stream)
The format of the IP stream mode is given in table 5. It provides a transparent transmission of IP packets, each having a
maximum size (MTU) of 4 095 bytes. Each IP packet to be transmitted is preceded by a header of 2 bytes that is defined
in table 6 and contains information about the IP packet format and length.
The payload size of one PF infoword is 1 504 bytes, but the amount of header information needs to be taken into
account. Each header consumes 2 bytes of the total payload available.
The address of the first available header within one PF infoword is contained in the parameter
First_Header_Address. Only this first header is announced; if more than one IP packets are present in one PF
infoword, the address of the headers can be incrementally derived from the preceding ones.
If no header was available in this PF infoword, the value 0xFFF is set to indicate the absence of any header.
See figure 4 for clarification.
If not enough payload is available for transport, the missing bytes are filled with 0xFF bytes. Any
First_Header_Address larger than 1 502 is not allowed as splitting of headers is not permitted. In this case, the
last byte(s) of the payload packet is (are) padded with 0xFF bytes.
Additional error correction and detection is performed by using one shortened BCH (3 057, 3 008) code each 376 bytes.
Therefore, each PF infoword contains 4 sections of BCH parity of 49 bits each.
As this BCH-code is a systematic code, the parity may be discarded in the receiver if this additional parity check is not
desired; however, performance is supposed to degrade in this case. On the contrary, it is a mandatory requirement on
the transmitter side to include this code.
The generation of the BCH codeword and the bit format is described in clause 4.3.3.
Table 5: PF infoword format for S-TS stream type 3 (IP stream)
Start bit Wordsize
Parameter Description Format Comment
index (bits)
1 504×U8
0 Payload_Packet Payload packet 12 032 See table 6 for further details.
(1 504 bytes)
Four times the 49 parity bits of
Parity bits for Error Detection a shortened
12 032 Parity_Parts or Outer Error Correction 196 4×U49 BCH(3 057,3 008)-code, which
Code each protects 376 payload
bytes.
20 bits reserved for future Helps to bit-align the payload to
12 228 RFU 20 U20
use byte boundaries.
This value gives the start
address of the first header to
be found. If no header is
Byte address where the first
present, the address is set to
header of the first IP packet
12 248 First_Header_Address 12 U12 0xFFF. Any
can be found; counting is
First_Header_Address
zero-based
larger than 1 502 needs to be
discarded while 1 502 is still
allowed.
12 260 STS_ID S-TS ID 8 U8
12 268 STS_Stream_Type_ID S-TS stream type identifier 3 U3 Fixed to 3 for IP stream.
Version number of the OPL
12 271 Encap_Ver 3 U3 Fixed to 0.
encapsulation format
CRC over the 46 relevant bits The light grey marked bits are
12 274 CRC_Bits 8 U8
of the header included in the CRC check.
Total length of PFIW
12 282
ETSI
16 Draft ETSI EN 302 550-1-1 V1.1.0 (2009-07)
Table 6: IP Header definition for each IP packet processed by the OPL encapsulation
Start bit Wordsize
Parameter Description Format Comment
index (bits)
The following definitions apply:
0: reserved
Defines the type of the
0 IP_Packet_Type 2 U2 1: IPv4;
encapsulated packet
2: IPv6;
3: Padding/Stuffing.
Is set if the IP packet is
2 IP_Packet_Error 1 U1 0 if no error occurred.
erroneous
Defines the length of the IP This enables a maximum transfer
3 IP_Packet_Length 12 U12
Packet (in bytes) unit (MTU) size of 4 095 bytes.
14 RFU 1 bit reserved for future use 1 U1
Total length of one header 16
Figure 4: Description of IP packet encapsulation
4.4 PL FEC: turbo code
As PL FEC scheme, the Turbo Code as standardized by the 3GPP2 organization has been chosen.
4.4.1 Interface to OPL encapsulation
The turbo encoder encodes blocks of 12 282 bits, which are referred to as PL FEC information words (PF infoword), for
the payload transmission.
For each S-TS, these PF infowords are sequentially input to the turbo encoder after OPL encapsulation.
ETSI
17 Draft ETSI EN 302 550-1-1 V1.1.0 (2009-07)
4.4.2 Turbo encoder
Besides the PF infowords for the S-TS payload of length 12 282 bits, the turbo encoder is also able to encode blocks of
762 bits for the signalling pipe. During encoding, an encoder output tail sequence is added. N is the total number of
turbo
data excluding the tail bits. The turbo encoder generates N /R encoded data output symbols followed by 6/R tail
turbo
output symbols, where R is the code rate.
The turbo encoder employs two systematic, recursive, convolutional encoders connected in parallel, with an interleaver,
the turbo interleaver, preceding the second recursive convolutional encoder. The two recursive convolutional codes are
called the constituent codes of the turbo code. The outputs of the constituent encoders are punctured to achieve the
(N + 6)/R output symbols.
turbo
A common constituent code is used for all turbo code rates. The transfer function for the constituent code is:
⎤
⎡
n(D) n(D)
G(D) = 1
⎥
⎢
d(D) d(D)
⎥
⎣
⎦
2 3 3 2 3
where d(D) = 1 + D + D , n (D) = 1 + D + D , and n (D) = 1 + D + D + D .
0 1
The turbo encoder generates an output symbol sequence that is identical to the one generated by the encoder shown in
figure 5. Initially, the states of the constituent encoder registers in this figure are set to zero. Then, the constituent
encoders are clocked with the switches in the positions noted.
Using the turbo encoder, the constituent encoder output symbols are generated by clocking the constituent encoders
N times with the switches in the up positions and puncturing as specified in table 7. Within a puncturing pattern, a
turbo
"0" means that the symbol shall be deleted and a "1" means that a symbol shall be passed. The puncturing patterns shall
be read from left to right and continuously from one text line to the next one. The patterns are displayed with a
partitioning into groups of 5 symbols. The 5 symbols of a group represent the outputs X Y Y Y' Y' of the encoder
0 1 0 1
shown in figure 5, respectively. Each puncturing pattern consists of one such group or of a sequence of several groups.
The displayed pattern is repeated cyclically, until 12 282 groups have been processed (one group per infoword bit).
Hence, the last period of the pattern remains incomplete for some puncturing patterns.
According to table 7, some examples for puncturing are given.
The turbo encoder shall generate symbols for rate 1/2 turbo codes as follows:
• The symbols output by the encoder for even-indexed data bit periods shall be XY .
• The symbols output by the encoder for odd-indexed data bit periods shall be XY' .
The turbo encoder shall generate symbols for rate 1/3 turbo codes as follows:
• The symbols output by the encoder for all data bit periods shall be XY Y' .
0 0
The turbo encoder shall generate symbols for rate 1/4 turbo codes as follows:
• The symbols output by the encoder for even-indexed data bit periods shall be XY Y Y' .
0 1 1
• The symbols output by the encoder for odd-indexed data bit periods shall be XY Y' Y' .
0 0 1
The turbo encoder shall generate symbols for rate 1/5 turbo codes as follows:
• The symbols output by the encoder for all data bit periods shall be XY Y Y' Y' .
0 1 0 1
Symbol repetition is not used in generating the encoded data output symbols.
ETSI
18 Draft ETSI EN 302 550-1-1 V1.1.0 (2009-07)
Constituent Encoder 1
X
Y
n
Y
n
N
turbo
Bits
(Input)
d
Control
(N + 6)/R
turbo
Symbol
Code
Clocked once for each of the N bit periods with the switch up; then,
turbo
Puncture Symbols
clocked once for each of the three Constituent Encoder 1 tail bit periods with
(Output)
the switch down; then, not clocked for the three Constituent Encoder 2 tail bit
periods.
Turbo
Interleaver
Constituent Encoder 2
X'
Y'
n
Y'
n
d
Control
Clocked once for each of the N bit periods with the switch up; then, not
turbo
clocked for the three Constituent Encoder 1
tail bit periods; then, clocked once for each of the three
Constituent Encoder 2 tail bit periods with the switch down.
Figure 5: Turbo encoder
ETSI
19 Draft ETSI EN 302 550-1-1 V1.1.0 (2009-07)
Table 7: Puncturing patterns for the turbo encoder during the data bit periods
Code
Puncturing Pattern (X; Y ; Y ; Y' ; Y' ; X; Y ; etc.)
Punct_Pat_ID Pattern Name
0 1 0 1 0
Rate
0 1/5 Standard 1;1;1;1;1
1 2/9 Standard 1;0;1;1;1; 1;1;1;1;1; 1;1;1;0;1; 1;1;1;1;1
2 1/4 Standard 1;1;1;0;1; 1;1;0;1;1
3 2/7 Standard 1;0;1;0;1; 1;0;1;1;1; 1;0;1;0;1; 1;1;1;0;1
1;1;0;1;0; 1;1;0;1;0; 1;1;0;1;0;
4 3/10 Standard
1;1;0;1;0; 1;1;0;1;0; 1;1;1;1;1
5 1/3 Standard 1;1;0;1;0
6 1/3 Complementary1 1;0;1;0;1
7 3/8 Standard 0;1;0;1;0; 1;1;0;1;0; 1;1;0;1;0
8 3/8 Complementary1 1;0;1;0;1; 0;0;1;0;1; 1;0;1;0;1
1;0;0;0;0; 1;0;1;0;1; 0;0;1;0;1;
1;0;1;0;1; 1;0;1;0;1; 0;0;1;0;1;
9 2/5 Standard
1;0;1;0;1; 1;0;1;0;1; 0;0;1;0;1;
1;0;1;0;1; 1;0;1;0;1; 0;0;1;0;1
1;1;0;1;0; 0;1;0;1;0; 1;1;0;1;0;
1;1;0;1;0; 0;1;0;1;0; 1;0;0;0;0;
10 2/5 Complementary1
1;1;0;1;0; 0;1;0;1;0; 1;1;0;1;0;
1;1;0;1;0; 0;1;0;1;0; 1;1;0;1;0
1;0;0;0;0; 1;1;0;1;0; 0;1;0;1;0;
11 3/7 Standard
1;1;0;1;0; 0;1;0;1;0; 1;1;0;1;0
1;0;1;0;1; 0;0;1;0;1; 1;0;1;0;1;
12 3/7 Complementary1
1;0;0;0;0; 1;0;1;0;1; 0;0;1;0;1
13 1/2 Standard 1;1;0;0;0; 1;0;0;1;0
14 1/2 Complementary1 1;0;0;1;0;
...
Final draft ETSI EN 302 550-1-1 V1.1.0 (2009-12)
European Standard (Telecommunications series)
Satellite Earth Stations and Systems (SES);
Satellite Digital Radio (SDR) Systems;
Part 1: Physical Layer of the Radio Interface;
Sub-part 1: Outer Physical Layer
2 Final draft ETSI EN 302 550-1-1 V1.1.0 (2009-12)
Reference
DEN/SES-00312-1-1
Keywords
digital, layer 1, radio, satellite
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 2009.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
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.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 Final draft ETSI EN 302 550-1-1 V1.1.0 (2009-12)
Contents
Intellectual Property Rights . 5
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Symbols and abbreviations . 7
3.1 Symbols . 7
3.2 Abbreviations . 7
4 Outer physical layer. 7
4.1 Overview . 7
4.2 Interfacing to Service Layer (SL) . 11
4.3 S-TS to OPL adaptation layer: S-TS encapsulation . 12
4.3.1 PF infoword format for S-TS stream type 0 (dummy packet) . 13
4.3.2 PF infoword format for S-TS stream type 1 (transparent) . 13
4.3.3 PF infoword format for S-TS stream type 2 (MPEG-TS) . 13
4.3.4 PF infoword format for S-TS stream type 3 (IP stream) . 15
4.4 PL FEC: turbo code . 16
4.4.1 Interface to OPL encapsulation . 16
4.4.2 Turbo encoder . 17
4.4.3 Turbo code termination . 20
4.4.4 Turbo Interleavers . 22
4.4.5 Output of turbo encoder . 23
4.4.6 FEC Parameter signalling . 23
4.4.7 Diversity combining . 24
4.4.8 FEC Parameters for the signalling pipe . 24
4.5 Mixer . 24
4.6 Segmenter and Slot demultiplexer . 25
4.7 Disperser. 26
4.8 Collector . 27
4.9 C-TS multiplexer . 28
4.10 Configuration of the OPL . 29
4.10.1 Signalling pipe . 29
4.10.1.1 Encoding and interleaving of signalling pipe . 29
4.10.1.2 SOF Preamble . 30
4.10.1.3 Format of the signalling pipe infoword . 30
4.10.2 Partitioning of the C-TS multiplex . 35
4.10.3 S-TS schedule and slot allocation . 36
4.10.4 S-TS re-scheduling and slot re-allocation . 37
4.10.5 Birth/death of S-TS . 37
4.10.6 S-TS ID . 37
4.10.7 Calculation of the disperser profile . 38
4.10.8 Configuration of the tail pipe . 39
4.10.9 Unused pipes . 39
4.10.10 Announcing reconfigurations and reschedulings . 39
4.10.11 Pipe reconfiguration . 40
4.11 Network aspects . 44
Annex A (normative): Number format definitions . 46
A.1 Number format and transmission order . 46
A.2 SI-Prefix Notation . 46
ETSI
4 Final draft ETSI EN 302 550-1-1 V1.1.0 (2009-12)
A.3 Default Settings . 46
Annex B (normative): Calculation of the CRC word . 47
Annex C (informative): Bibliography . 48
History . 49
ETSI
5 Final draft ETSI EN 302 550-1-1 V1.1.0 (2009-12)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Satellite Earth
Stations and Systems (SES), and is now submitted for the Vote phase of the ETSI standards Two-step Approval
Procedure.
The present document is part 1, sub-part 1 of a multi-part deliverable covering Satellite Digital Radio (SDR), as
identified below:
Part 1: "Physical Layer of the Radio Interface";
Sub-part 1: "Outer Physical Layer";
Sub-part 2: "Inner Physical Layer Single Carrier Modulation";
Sub-part 3: "Inner Physical Layer Multi Carrier Modulation".
Proposed national transposition dates
Date of latest announcement of this EN (doa): 3 months after ETSI publication
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 6 months after doa
Date of withdrawal of any conflicting National Standard (dow): 6 months after doa
Introduction
TC SES is producing standards and other deliverables for Satellite Digital Radio (SDR) systems. An SDR system
enables broadcast to fixed and mobile receivers through satellites and complementary terrestrial transmitters.
Functionalities, architecture and technologies of such systems are described in TR 102 525 [i.1].
Several existing and planned ETSI standards specify parts of the SDR system, with the aim of interoperable
implementations. The physical layer of the radio interface (air interface) is divided up into the outer physical layer, the
inner physical layer with a single carrier modulation, and the inner physical layer with multi carrier modulation. These
parts can be used all together in SDR compliant equipment, or in conjunction with other existing and future
specifications.
The present document specifies the outer physical layer. The inner physical layer with single carrier modulation is
specified in EN 302 550-1-2 [i.2], and with multi carrier modulation in EN 302 550-1-3 [i.3]. Guidelines for using the
physical layer standard can be found in TR 102 604 [i.4].
The physical layer specifications have previously been published as "Technical Specification (TS)" type ETSI
deliverables. The present document supersedes TS 102 550 [i.5] and is recommended for new implementations.
ETSI
6 Final draft ETSI EN 302 550-1-1 V1.1.0 (2009-12)
1 Scope
The present document concerns the radio interface of SDR broadcast receivers. It specifies the functionality of the outer
physical layer. It allows implementing this part of the system in an interoperable way.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ISO/IEC 13818-1: "Information technology - Generic coding of moving pictures and associated
audio information: Systems".
[2] ISO/IEC 11172-1: "Information technology - Coding of moving pictures and associated audio for
digital storage media at up to about 1,5 Mbit/s - Part 1: Systems".
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
[i.1] ETSI TR 102 525: "Satellite Earth Stations and Systems (SES); Satellite Digital Radio (SDR)
service; Functionalities, architecture and technologies".
[i.2] ETSI EN 302 550-1-2: "Satellite Earth Stations and Systems (SES); Satellite Digital Radio (SDR)
Systems; Part 1: Physical Layer of the Radio Interface; Sub-part 2: Inner Physical Layer Single
Carrier Modulation".
[i.3] ETSI EN 302 550-1-3: "Satellite Earth Stations and Systems (SES); Satellite Digital Radio (SDR)
Systems; Part 1: Physical Layer of the Radio Interface; Sub-part 3: Inner Physical Layer Multi
Carrier Modulation".
[i.4] ETSI TR 102 604: "Satellite Earth Stations and Systems (SES); Satellite Digital Radio (SDR)
Systems; Guidelines for the Use of the Physical Layer Standards".
[i.5] ETSI TS 102 550 (V1.3.1): "Satellite Earth Stations and Systems (SES); Satellite Digital Radio
(SDR) Systems; Outer Physical Layer of the Radio Interface".
ETSI
7 Final draft ETSI EN 302 550-1-1 V1.1.0 (2009-12)
3 Symbols and abbreviations
3.1 Symbols
For the purposes of the present document, the following symbols apply:
Code rate
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AWGN Additive White Gaussian Noise
BCH Bose, Ray-Chaudhuri, Hocquenghem code
CRC Cyclic Redundancy Checksum
C-TS Channel-Transport Stream
CU Capacity Unit
FEC Forward Error Correction
ID IDentifier
IP Internet Protocol
IPL Inner Physical Layer
IU Interleaving Unit
LSB Least Significant Bit
MPEG-TS MPEG Transport Stream
MSB Most Significant Bit
MTU Maximum Transfer Unit
OPL Outer Physical Layer
PF Physical layer FEC
PFIW Physical layer FEC Info Word
PL Physical Layer
QoS Quality of Service
RFU Reserved for Future Use
SL Service Layer
SOF Start Of Frame
S-TS Service-Transport Stream
VBR Variable Bit Rate
WER Word Error Rate
4 Outer physical layer
Refer to annex A for number format definitions.
4.1 Overview
Figure 1 displays the position and the interfaces of the Outer Physical Layer (in the following denoted by OPL) inside a
complete broadcast transmission chain. The OPL connects to the Service Layer, where the interface is Service
Transport Streams (S-TS) on the one side, and on the other side to the Inner Physical Layer (IPL - described in
EN 302 550-1-2 [i.2] and EN 302 550-1-3 [i.3]), where the interfaces are Channel Transport Streams (C-TS).
ETSI
8 Final draft ETSI EN 302 550-1-1 V1.1.0 (2009-12)
Figure 1: Position and interfaces of the OPL inside the transmission chain
The following table gives an overview about the terminology used for the data streaming through the system.
Description Comments
SC Service component E.g. source encoded audio or video or other data
SC-TS Service component transport stream
ES Elementary Stream ES: Elementary Stream, a generic term for one of the
coded video, coded audio or other coded data
bitstreams, cf. MPEG-1 standard
ISO/IEC 11172-1 [2].
Program A program is a collection of program In line with the definition used for MPEG standard
elements. Program elements may be ISO/IEC 13818-1 [1].
elementary streams (ES, SC-TS).
Service Set of programs and related auxiliary
information
S-TS Service transport stream Generalized term for transport stream. MPEG-TS is
one example for a service transport stream.
MPEG-TS Transport stream compliant to MPEG
standard ISO/IEC 13818-1 [1]
C-TS Channel transport stream Data stream (bit stream) representing the input to the
modulator = data stream including all redundancy
added by the FEC encoder - possibly with
time-interleaving - and carrying configuration
signalling information for the receiver.
The content of the C-TS is referred to as a C-TS
multiplex (a multiplex of encoded and interleaved
S-TS plus signalling information).
A bouquet of programs is carried by one or more
C-TS multiplexes.
ETSI
9 Final draft ETSI EN 302 550-1-1 V1.1.0 (2009-12)
Description Comments
Channel RF resource The meaning "RF resource" is aligned with the
terminology used for DVB.
The functionality of the Outer Physical Layer is to provide Forward Error Correction and time interleaving for
resistance against a variety of transmission channel conditions. Different transport channels are used in the OPL to offer
the requested performance for different types of services. These transport channels are called pipes in the scope of the
present document. The OPL is configurable in terms of error protection, outage mitigation in case of signal losses,
end-to-end delay, zapping time, payload throughput and receiver complexity.
Multiple pipes can be used as described above. Each of them contains FEC, Mixer and Disperser. One special pipe
exists whose functionality is to transmit all relevant parameters to decode the other pipes. The so-called signalling pipe
is always transmitted at the lowest coderate which is 1/5. The modulation of the signalling pipe is equal to the
modulation of the data pipes.
The general block diagram of the OPL functionality is given in figure 2.
ETSI
10 Final draft ETSI EN 302 550-1-1 V1.1.0 (2009-12)
Figure 2: General overview of the OPL functionality
ETSI
11 Final draft ETSI EN 302 550-1-1 V1.1.0 (2009-12)
The processing, multiplexing and demultiplexing of the data in the OPL is displayed in figure 3. An S-TS scheduler
multiplexes together all S-TS contained in the pipe. The scheduler is controlled by an S-TS schedule, which determines
the number of words taken from one S-TS before the multiplexer selects the next S-TS of the pipe. After an
encapsulation, FEC encoding and mixing, the codewords (segmented into interleaver units) are demultiplexed
codeword-wise to the slots of the considered pipe, each of the slots possessing its individual disperser. After
demultiplexing a codeword to a slot, i.e. to the input of its disperser, the slot demultiplexer selects the next
slot/disperser. At the outputs of the dispersers, the dispersed codewords are multiplexed together again by the collector
to form one pipe. The slot demultiplexer and the collector always select synchronously the same slot/disperser.
IUs of one slot Dispersed IUs of
Packets of an one slot
S-TS
Slots of IUs
OPL Slots or IUs of
Disperser
S-TS i one pipe of one
Encapsulation
Mixed
PF infowords PF codewords C-TS frame
codewords
OPL
S-TS i + 1
Encapsulation
C-TS
PL FEC Mixer Segmenter Disperser
mux
... Collector
Slot
Demux
OPL S-TS
S-TS j
Encapsulation scheduler
...
Number of S-TS
Disperser
in this pipe:
Num_STS
Number of
Dispersers in this
pipe:
Pipe_Width_Slots
Figure 3: Definition of the different blocks involved in the OPL processing
4.2 Interfacing to Service Layer (SL)
The interface to the service layer is the so-called Service-Transport Stream (S-TS). For the OPL, each S-TS source is
the smallest granularity which can be processed independently.
The interface may work synchronously or asynchronously. In the case of asynchronous interface, the PL must be able to
accept at least the average data rate that is provided by the SL. Any data buffering shall be done inside the SL, such that
no data from the S-TS is lost at this interface. When the PL requests new data for transmission, the SL can either
provide the requested data to the PL or it can signal that no data is currently available. If no data is available for
transmission, the PL instead transmits dummy data that is discarded in the receiver.
Inside an S-TS, multiplexing and de-multiplexing of information shall be carried out by the service layer.
Each pipe provides a different set of transmission parameters (e.g. FEC code rate and disperser profile), and achieves a
different QoS in terms of protection against transmission errors and end-to-end delay. One pipe of the OPL may carry
several S-TS, all with the same QoS parameters.
If PL time slicing is used, each time slice is associated with one S-TS. The scheduling of the S-TS, i.e. their start
instants and lengths, inside a pipe can be adapted frequently (once per schedule/time slicing period). This opens the
possibility of handling Variable Bit Rate (VBR) transmission.
The maximum allowed payload throughput per S-TS is 3,2 Mbit/s (this corresponds to approximately 8 to 10 video
services inside one S-TS). This is the throughput that the processing chain inside the receiver (e.g. the turbo decoder)
must be able to handle at least.
ETSI
12 Final draft ETSI EN 302 550-1-1 V1.1.0 (2009-12)
4.3 S-TS to OPL adaptation layer: S-TS encapsulation
The OPL is prepared to transport different types of S-TS, and a mixture of different S-TS types may be transported
simultaneously over one C-TS multiplex.
The following parameters have to be determined for each S-TS (for parameters, refer to signalling pipe in
clause 4.10.1):
• S-TS ID: identifier for the transported S-TS, that is unique for each network operator (i.e. for each
Operator_ID); observe that one S-TS may be transported over multiple instances of the PL and still have a
single unique S-TS ID; this helps, for example, for diversity combining of one S-TS transmitted over satellite
and simultaneously over terrestrial repeaters. Several rules apply for the S-TS:
- S-TS ID 0 plays a special role: this is the Service Layer configuration S-TS (the SL can signal its own
configuration via this S-TS).
- An S-TS may be fed to several C-TS multiplexes. The S-TS IDs in all of these C-TS multiplexes are
identical.
- An S-TS may not be fed to several pipes inside the same C-TS multiplex, and an S-TS may not be fed
several times to the same pipe inside one C-TS multiplex either.
- S-TS IDs must be unique over the complete network of one operator except for S-TS ID 0 which is
allowed on every C-TS multiplex.
- S-TS with an identical Operator_ID and S-TS ID can always be diversity combined (except for
S-TS ID 0).
- The length of an S-TS can be configured in a granularity of one PL infoword per C-TS frame.
• Pipe number that this S-TS is transported over.
Moreover, for the ensemble of S-TS contained inside a complete C-TS multiplex, the following parameters have to be
fixed (for parameters, refer also to signalling pipe in clause 4.10.1):
• Operator_ ID: unique identifier for the network operator.
• Partitioning of the C-TS multiplex into pipes and scheduling of the S-TS inside the pipes, i.e. what is the data
rate of one S-TS and when are the bursts of one S-TS transported.
Each S-TS is partitioned into packets to match the length of the PL FEC information word (PF infoword). The packet
size is individual for each type of S-TS. The OPL encapsulation inside the S-TS to OPL adaptation layer adapts the
length of the S-TS packets to the PF infoword length by appending a suffix to the S-TS packet. Table 1 defines the S-TS
packet length and the suffix length for different S-TS types.
Table 1: Defined S-TS type IDs
S-TS Type S-TS Type ID S-TS payload packet Suffix length Comment
Size in bytes in bits
Dummy packet 0 0 26 used for asynchronous sl/pl interface.
is discarded in receiver.
Transparent
1 1 532 26 sl has to decide what to do with this
data.
MPEG-TS 2 1 504 250 payload packet is 8 mpeg packets of
188 bytes each; additionally, a bch
code of 196 bits is applied.
IP stream 3 1 504 250 mtu of ip = 4 095 bytes with 2 bytes
additional header per packet.
RFU
4 to 7 reserved for future s-ts types.
The detailed format for the different types of S-TS is given in the following clauses. The Cyclic Redundancy Check
8 5 3 2
(CRC) polynomial, which appears in the following clauses, is x + x + x + x + x + 1 for all S-TS stream types. The
calculation of the CRC is described in annex B.
ETSI
13 Final draft ETSI EN 302 550-1-1 V1.1.0 (2009-12)
4.3.1 PF infoword format for S-TS stream type 0 (dummy packet)
The format of the dummy packet is given in table 2. The insertion of a dummy packet is performed if no data was
available at the instant of processing the actual packet in the OPL.
Table 2: PF infoword format for S-TS stream type 0 (dummy packet)
Start bit Wordsize
Parameter Description Format Comment
index (bits)
1 532×U8
0 Dummy data To be filled with zeros 12 256
(1 532 bytes)
helps to bit-align the payload to
12 256 RFU 4 bits reserved for future use 4 U4
byte boundaries.
12 260 STS_ID S-TS ID 8 U8 can be chosen arbitrarily.
12 268 STS_Stream_Type_ID S-TS stream type identifier 3 U3 fixed to 0 for dummy packets.
Version number of the OPL
12 271 Encap_Ver 3 U3 fixed to 0.
encapsulation format
CRC over the 18 relevant the light grey marked bits are
12 274 HeaderCRC 8 U8
bits of the header included in the header.
Total length of PFIW 12 282
4.3.2 PF infoword format for S-TS stream type 1 (transparent)
The format of the transparent mode is given in table 3. It provides a transparent transmission of whatever payload. The
throughput capability of the transparent stream type is 1 532 bytes per PF infoword. No additional error correction or
detection except the turbo code is used; therefore, data integrity and flow control needs to be performed by the link
layer. The definition of such protocol is not included in the present document.
Table 3: PF infoword format for S-TS stream type 1 (transparent)
Start bit Wordsize
Parameter Description Format Comment
index (bits)
1 532×U8 May include counters, error
0 Payload_Packet Transparent payload packet 12 256
(1 532 bytes) correction and error detection.
Helps to bit-align the payload
12 256 RFU 4 bits reserved for future use 4 U4
to byte boundaries.
12 260 STS_ID S-TS ID 8 U8
Fixed to 1 for transparent
12 268 STS_Stream_Type_ID S-TS stream type identifier 3 U3
packets.
Version number of the OPL
12 271 Encap_Ver 3 U3 Fixed to 0.
encapsulation format
CRC over the 18 relevant The light grey marked bits are
12 274 HeaderCRC 8 U8
bits of the header included in the CRC check.
Total length of PFIW 12 282
4.3.3 PF infoword format for S-TS stream type 2 (MPEG-TS)
The format of the MPEG-TS stream mode is given in table 4. It provides a transparent transmission of up to
8 MPEG-TS packets according to ISO/IEC 13818-1 [1], each having a size of 188 bytes. If less than 8 packets are
available for transport, the missing packets are filled by MPEG-TS null packets. Additional error correction and
detection is performed by using one shortened BCH (3 057, 3 008) code each 2 MPEG-TS packets. Therefore, each PF
infoword contains 4 sections of BCH parity of 49 bits each.
As this BCH-code is a systematic code, the parity may be discarded in the receiver if this additional parity check is not
desired; however, performance is supposed to degrade in this case. On the contrary, it is a mandatory requirement on
the transmitter side to include this parity.
ETSI
14 Final draft ETSI EN 302 550-1-1 V1.1.0 (2009-12)
The error correction code (overall minimum distance d = 10) is actually an outer BCH(3056, 3008, 9) code (with
min
minimum distance d = 9) concatenated by an inner single-parity check code (3057,3056,1). The BCH code is gained
min
by shortening a narrow-sense binary BCH(4095,4047,9)-Code. Concatenated encoding of (payload) message bits
m = (m ,mm,., ,m ) onto an (overall) codeword
3007 3006 1 0
c = (m ,mm,., ,m ,d ,d ,.,d ,d ,p ) is achieved as follows:
3007 3006 1 0 47 46 1 0 0
• The message bit m is gained from the temporally first bit (MSB of the temporally first byte) of the
temporally earlier MPEG-TS packet. The next message bit m corresponds to the temporally second bit (Bit
6 of the temporally first byte) of the temporally earlier MPEG-TS packet, and so on until bit m , which is
the temporally last bit (LSB of the temporally last byte) of the temporally earlier MPEG-TS packet. The
following 1 504 bits m to m are taken in the same manner from the temporally later MPEG-TS packet.
1503 0
3007 3006 48
• Multiply the message polynomial m(x) = m xm++x .+mx+m by x (the coefficients
3007 3006 1 0
of m(x) for exponents > 3 007 are all set to zero in order to shorten this BCH code; note that this corresponds
to temporally preceding the message by 1 039 zeros).
• Divide x m(x) by the BCH generator polynomial
48 44 41 37 36 34 32 29 27 26 21 17 16 13 7 5 3
g(x)=x+xx+ +x+++x x x+xx+ +xx+ +x+x+x+x+x+x+x+1
Let d(xd)=+x .+dx+ d be the remainder.
471 0
• Set the outer (i.e. BCH) codeword polynomial c (xx)(=+mx) d(x) .
o
• Calculate the single-parity check bit pc==(1x ) and set the overall codeword polynomial to
0 o
c(xc)=⋅()x x+p=xm()x+x⋅d()x+ p .
o00
Observe that the temporal transmission order of the bits of the codeword c is (m ,mm,., ,m ) for the
3007 3006 1 0
message part and (d ,dd,., ,d ,p ) for the parity part, i.e. the order is temporally descending for this BCH
4746 1 0 0
codeword-specific indexing. Note that by contrast the indexing of the bits inside the PF infoword is in temporally
ascending order, i.e. bit 0 to bit 12 281. Inside the Payload_Packet field of the PF infoword, there are four such message
parts (each representing 2 MPEG-TS packets or 376 bytes); the four associated parity parts are transmitted in the field
Parity_Parts in the same order.
Table 4: PF infoword format for S-TS stream type 2 (MPEG-TS)
Start bit Wordsize
Parameter Description Format Comments
index (bits)
1 504×U8
0 Payload_Packet 12 032
Payload packet (1 504 bytes)
Four times the 49 parity bits
of a shortened
12 032 Parity_Parts Parity bits for Error 196 4×U49 BCH(3 057,3 008)-code,
Detection or Outer Error which each protects 2
Correction Code MPEG-TS packets.
32 bits reserved for future Helps to bit-align the payload
12 228 RFU 32 U32
use to byte boundaries.
12 260 STS_ID S-TS ID 8 U8
12 268 STS_Stream_Type_ID S-TS stream type identifier 3 U3 Fixed to 2 for MPEG-TS.
Version number of the OPL
12 271 Encap_Ver 3 U3
encapsulation format Fixed to 0.
CRC over the 46 relevant The light grey marked bits are
12 274 CRC_Bits 8 U8
bits of the header included in the CRC check.
Total length of PFIW 12 282
ETSI
15 Final draft ETSI EN 302 550-1-1 V1.1.0 (2009-12)
4.3.4 PF infoword format for S-TS stream type 3 (IP stream)
The format of the IP stream mode is given in table 5. It provides a transparent transmission of IP packets, each having a
maximum size (MTU) of 4 095 bytes. Each IP packet to be transmitted is preceded by a header of 2 bytes that is defined
in table 6 and contains information about the IP packet format and length.
The payload size of one PF infoword is 1 504 bytes, but the amount of header information needs to be taken into
account. Each header consumes 2 bytes of the total payload available.
The address of the first available header within one PF infoword is contained in the parameter
First_Header_Address. Only this first header is announced; if more than one IP packets are present in one PF
infoword, the address of the headers can be incrementally derived from the preceding ones.
If no header was available in this PF infoword, the value 0xFFF is set to indicate the absence of any header.
See figure 4 for clarification.
If not enough payload is available for transport, the missing bytes are filled with 0xFF bytes. Any
First_Header_Address larger than 1 502 is not allowed as splitting of headers is not permitted. In this case, the
last byte(s) of the payload packet is (are) padded with 0xFF bytes.
Additional error correction and detection is performed by using one shortened BCH (3 057, 3 008) code each 376 bytes.
Therefore, each PF infoword contains 4 sections of BCH parity of 49 bits each.
As this BCH-code is a systematic code, the parity may be discarded in the receiver if this additional parity check is not
desired; however, performance is supposed to degrade in this case. On the contrary, it is a mandatory requirement on
the transmitter side to include this code.
The generation of the BCH codeword and the bit format is described in clause 4.3.3.
Table 5: PF infoword format for S-TS stream type 3 (IP stream)
Start bit Wordsize
Parameter Description Format Comment
index (bits)
1 504×U8
0 Payload_Packet Payload packet 12 032 See table 6 for further details.
(1 504 bytes)
Four times the 49 parity bits of
Parity bits for Error Detection a shortened
12 032 Parity_Parts or Outer Error Correction 196 4×U49 BCH(3 057,3 008)-code, which
Code each protects 376 payload
bytes.
20 bits reserved for future Helps to bit-align the payload to
12 228 RFU 20 U20
use byte boundaries.
This value gives the start
address of the first header to
be found. If no header is
Byte address where the first
present, the address is set to
header of the first IP packet
12 248 First_Header_Address 12 U12 0xFFF. Any
can be found; counting is
First_Header_Address
zero-based
larger than 1 502 needs to be
discarded while 1 502 is still
allowed.
12 260 STS_ID S-TS ID 8 U8
12 268 STS_Stream_Type_ID S-TS stream type identifier 3 U3 Fixed to 3 for IP stream.
Version number of the OPL
12 271 Encap_Ver 3 U3 Fixed to 0.
encapsulation format
CRC over the 46 relevant bits The light grey marked bits are
12 274 CRC_Bits 8 U8
of the header included in the CRC check.
Total length of PFIW
12 282
ETSI
16 Final draft ETSI EN 302 550-1-1 V1.1.0 (2009-12)
Table 6: IP Header definition for each IP packet processed by the OPL encapsulation
Start bit Wordsize
Parameter Description Format Comment
index (bits)
The following definitions apply:
0: reserved
Defines the type of the
0 IP_Packet_Type 2 U2 1: IPv4;
encapsulated packet
2: IPv6;
3: Padding/Stuffing.
Is set if the IP packet is
2 IP_Packet_Error 1 U1 0 if no error occurred.
erroneous
Defines the length of the IP This enables a maximum transfer
3 IP_Packet_Length 12 U12
Packet (in bytes) unit (MTU) size of 4 095 bytes.
14 RFU 1 bit reserved for future use 1 U1
Total length of one header 16
Figure 4: Description of IP packet encapsulation
4.4 PL FEC: turbo code
As PL FEC scheme, the Turbo Code as standardized by the 3GPP2 organization has been chosen.
4.4.1 Interface to OPL encapsulation
The turbo encoder encodes blocks of 12 282 bits, which are referred to as PL FEC information words (PF infoword), for
the payload transmission.
For each S-TS, these PF infowords are sequentially input to the turbo encoder after OPL encapsulation.
ETSI
17 Final draft ETSI EN 302 550-1-1 V1.1.0 (2009-12)
4.4.2 Turbo encoder
Besides the PF infowords for the S-TS payload of length 12 282 bits, the turbo encoder is also able to encode blocks of
762 bits for the signalling pipe. During encoding, an encoder output tail sequence is added. N is the total number of
turbo
data excluding the tail bits. The turbo encoder generates N /R encoded data output symbols followed by 6/R tail
turbo
output symbols, where R is the code rate.
The turbo encoder employs two systematic, recursive, convolutional encoders connected in parallel, with an interleaver,
the turbo interleaver, preceding the second recursive convolutional encoder. The two recursive convolutional codes are
called the constituent codes of the turbo code. The outputs of the constituent encoders are punctured to achieve the
(N + 6)/R output symbols.
turbo
A common constituent code is used for all turbo code rates. The transfer function for the constituent code is:
⎤
⎡
n(D) n(D)
G(D) = 1
⎥
⎢
d(D) d(D)
⎥
⎣
⎦
2 3 3 2 3
where d(D) = 1 + D + D , n (D) = 1 + D + D , and n (D) = 1 + D + D + D .
0 1
The turbo encoder generates an output symbol sequence that is identical to the one generated by the encoder shown in
figure 5. Initially, the states of the constituent encoder registers in this figure are set to zero. Then, the constituent
encoders are clocked with the switches in the positions noted.
Using the turbo encoder, the constituent encoder output symbols are generated by clocking the constituent encoders
N times with the switches in the up positions and puncturing as specified in table 7. Within a puncturing pattern, a
turbo
"0" means that the symbol shall be deleted and a "1" means that a symbol shall be passed. The puncturing patterns shall
be read from left to right and continuously from one text line to the next one. The patterns are displayed with a
partitioning into groups of 5 symbols. The 5 symbols of a group represent the outputs X Y Y Y' Y' of the encoder
0 1 0 1
shown in figure 5, respectively. Each puncturing pattern consists of one such group or of a sequence of several groups.
The displayed pattern is repeated cyclically, until 12 282 groups have been processed (one group per infoword bit).
Hence, the last period of the pattern remains incomplete for some puncturing patterns.
According to table 7, some examples for puncturing are given.
The turbo encoder shall generate symbols for rate 1/2 turbo codes as follows:
• The symbols output by the encoder for even-indexed data bit periods shall be XY .
• The symbols output by the encoder for odd-indexed data bit periods shall be XY' .
The turbo encoder shall generate symbols for rate 1/3 turbo codes as follows:
• The symbols output by the encoder for all data bit periods shall be XY Y' .
0 0
The turbo encoder shall generate symbols for rate 1/4 turbo codes as follows:
• The symbols output by the encoder for even-indexed data bit periods shall be XY Y Y' .
0 1 1
• The symbols output by the encoder for odd-indexed data bit periods shall be XY Y' Y' .
0 0 1
The turbo encoder shall generate symbols for rate 1/5 turbo codes as follows:
• The symbols output by the encoder for all data bit periods shall be XY Y Y' Y' .
0 1 0 1
Symbol repetition is not used in generating the encoded data output symbols.
ETSI
18 Final draft ETSI EN 302 550-1-1 V1.1.0 (2009-12)
Constituent Encoder 1
X
Y
n
Y
n
N
turbo
Bits
(Input)
d
Control
(N + 6)/R
turbo
Symbol
Code
Clocked once for each of the N bit periods with the switch up; then,
turbo
Puncture
Symbols
clocked once for each of the three Constituent Encoder 1 tail bit periods with
(Output)
the switch down; then, not clocked for the three Constituent Encoder 2 tail bit
periods.
Turbo
Interleaver
Constituent Encoder 2
X'
Y'
n
Y'
n
d
Control
Clocked once for each of the N bit periods with the switch up; then, not
turbo
clocked for the three Constituent Encoder 1
tail bit periods; then, clocked once for each of the three
Constituent Encoder 2 tail bit periods with the switch down.
Figure 5: Turbo encoder
ETSI
19 Final draft ETSI EN 302 550-1-1 V1.1.0 (2009-12)
Table 7: Puncturing patterns for the turbo encoder during the data bit periods
Code
Puncturing Pattern (X; Y ; Y ; Y' ; Y' ; X; Y ; etc.)
Punct_Pat_ID Pattern Name
0 1 0 1 0
Rate
0 1/5 Standard 1;1;1;1;1
1 2/9 Standard 1;0;1;1;1; 1;1;1;1;1; 1;1;1;0;1; 1;1;1;1;1
2 1/4 Standard 1;1;1;0;1; 1;1;0;1;1
3 2/7 Standard 1;0;1;0;1; 1;0;1;1;1; 1;0;1;0;1; 1;1;1;0;1
1;1;0;1;0; 1;1;0;1;0; 1;1;0;1;0;
4 3/10 Standard
1;1;0;1;0; 1;1;0;1;0; 1;1;1;1;1
5 1/3 Standard 1;1;0;1;0
6 1/3 Complementary1 1;0;1;0;1
7 3/8 Standard 0;1;0;1;0; 1;1;0;1;0; 1;1;0;1;0
8 3/8 Complementary1 1;0;1;0;1; 0;0;1;0;1; 1;0;1;0;1
1;0;0;0;0; 1;0;1;0;1; 0;0;1;0;1;
1;0;1;0;1; 1;0;1;0;1; 0;0;1;0;1;
9 2/5 Standard
1;0;1;0;1; 1;0;1;0;1; 0;0;1;0;1;
1;0;1;0;1; 1;0;1;0;1; 0;0;1;0;1
1;1;0;1;0; 0;1;0;1;0; 1;1;0;1;0;
1;1;0;1;0; 0;1;0;1;0; 1;0;0;0;0;
10 2/5 Complementary1
1;1;0;1;0; 0;1;0;1;0; 1;1;0;1;0;
1;1;0;1;0; 0;1;0;1;0; 1;1;0;1;0
1;0;0;0;0; 1;1;0;1;0; 0;1;0;1;0;
11 3/7 Standard
1;1;0;1;0; 0;1;0;1;0; 1;1;0;1;0
1;0;1;0;1; 0;0;1;0;1; 1;0;1;0;1;
12 3/
...
European Standard (Telecommunications series)
Satellite Earth Stations and Systems (SES);
Satellite Digital Radio (SDR) Systems;
Part 1: Physical Layer of the Radio Interface;
Sub-part 1: Outer Physical Layer
2 ETSI EN 302 550-1-1 V1.1.1 (2010-02)
Reference
DEN/SES-00312-1-1
Keywords
digital, layer 1, radio, satellite
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 2010.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
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.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI EN 302 550-1-1 V1.1.1 (2010-02)
Contents
Intellectual Property Rights . 5
Foreword . 5
Introduction . 5
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 7
3 Symbols and abbreviations . 8
3.1 Symbols . 8
3.2 Abbreviations . 8
4 Outer physical layer. 8
4.1 Overview . 8
4.2 Interfacing to Service Layer (SL) . 12
4.3 S-TS to OPL adaptation layer: S-TS encapsulation . 13
4.3.1 PF infoword format for S-TS stream type 0 (dummy packet) . 14
4.3.2 PF infoword format for S-TS stream type 1 (transparent) . 14
4.3.3 PF infoword format for S-TS stream type 2 (MPEG-TS) . 14
4.3.4 PF infoword format for S-TS stream type 3 (IP stream) . 16
4.4 PL FEC: turbo code . 17
4.4.1 Interface to OPL encapsulation . 17
4.4.2 Turbo encoder . 18
4.4.3 Turbo code termination . 21
4.4.4 Turbo Interleavers . 23
4.4.5 Output of turbo encoder . 24
4.4.6 FEC Parameter signalling . 24
4.4.7 Diversity combining . 25
4.4.8 FEC Parameters for the signalling pipe . 25
4.5 Mixer . 25
4.6 Segmenter and Slot demultiplexer . 26
4.7 Disperser. 27
4.8 Collector . 28
4.9 C-TS multiplexer . 29
4.10 Configuration of the OPL . 30
4.10.1 Signalling pipe . 30
4.10.1.1 Encoding and interleaving of signalling pipe . 30
4.10.1.2 SOF Preamble . 31
4.10.1.3 Format of the signalling pipe infoword . 31
4.10.2 Partitioning of the C-TS multiplex . 36
4.10.3 S-TS schedule and slot allocation . 37
4.10.4 S-TS re-scheduling and slot re-allocation . 38
4.10.5 Birth/death of S-TS . 38
4.10.6 S-TS ID . 38
4.10.7 Calculation of the disperser profile . 39
4.10.8 Configuration of the tail pipe . 40
4.10.9 Unused pipes . 40
4.10.10 Announcing reconfigurations and reschedulings . 40
4.10.11 Pipe reconfiguration . 41
4.11 Network aspects . 45
Annex A (normative): Number format definitions . 47
A.1 Number format and transmission order . 47
A.2 SI-Prefix Notation . 47
ETSI
4 ETSI EN 302 550-1-1 V1.1.1 (2010-02)
A.3 Default Settings . 47
Annex B (normative): Calculation of the CRC word . 48
Annex C (informative): Bibliography . 49
History . 50
ETSI
5 ETSI EN 302 550-1-1 V1.1.1 (2010-02)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Satellite Earth
Stations and Systems (SES).
The present document is part 1, sub-part 1 of a multi-part deliverable covering Satellite Digital Radio (SDR), as
identified below:
Part 1: "Physical Layer of the Radio Interface";
Sub-part 1: "Outer Physical Layer";
Sub-part 2: "Inner Physical Layer Single Carrier Modulation";
Sub-part 3: "Inner Physical Layer Multi Carrier Modulation".
National transposition dates
Date of adoption of this EN: 15 February 2010
Date of latest announcement of this EN (doa): 31 May 2010
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 November 2010
Date of withdrawal of any conflicting National Standard (dow): 30 November 2010
Introduction
TC SES is producing standards and other deliverables for Satellite Digital Radio (SDR) systems. An SDR system
enables broadcast to fixed and mobile receivers through satellites and complementary terrestrial transmitters.
Functionalities, architecture and technologies of such systems are described in TR 102 525 [i.1].
Several existing and planned ETSI standards specify parts of the SDR system, with the aim of interoperable
implementations. The physical layer of the radio interface (air interface) is divided up into the outer physical layer, the
inner physical layer with a single carrier modulation, and the inner physical layer with multi carrier modulation. These
parts can be used all together in SDR compliant equipment, or in conjunction with other existing and future
specifications.
ETSI
6 ETSI EN 302 550-1-1 V1.1.1 (2010-02)
The present document specifies the outer physical layer. The inner physical layer with single carrier modulation is
specified in EN 302 550-1-2 [i.2], and with multi carrier modulation in EN 302 550-1-3 [i.3]. Guidelines for using the
physical layer standard can be found in TR 102 604 [i.4].
The physical layer specifications have previously been published as "Technical Specification (TS)" type ETSI
deliverables. The present document supersedes TS 102 550 [i.5] and is recommended for new implementations.
ETSI
7 ETSI EN 302 550-1-1 V1.1.1 (2010-02)
1 Scope
The present document concerns the radio interface of SDR broadcast receivers. It specifies the functionality of the outer
physical layer. It allows implementing this part of the system in an interoperable way.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ISO/IEC 13818-1: "Information technology - Generic coding of moving pictures and associated
audio information: Systems".
[2] ISO/IEC 11172-1: "Information technology - Coding of moving pictures and associated audio for
digital storage media at up to about 1,5 Mbit/s - Part 1: Systems".
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
[i.1] ETSI TR 102 525: "Satellite Earth Stations and Systems (SES); Satellite Digital Radio (SDR)
service; Functionalities, architecture and technologies".
[i.2] ETSI EN 302 550-1-2: "Satellite Earth Stations and Systems (SES); Satellite Digital Radio (SDR)
Systems; Part 1: Physical Layer of the Radio Interface; Sub-part 2: Inner Physical Layer Single
Carrier Modulation".
[i.3] ETSI EN 302 550-1-3: "Satellite Earth Stations and Systems (SES); Satellite Digital Radio (SDR)
Systems; Part 1: Physical Layer of the Radio Interface; Sub-part 3: Inner Physical Layer Multi
Carrier Modulation".
[i.4] ETSI TR 102 604: "Satellite Earth Stations and Systems (SES); Satellite Digital Radio (SDR)
Systems; Guidelines for the Use of the Physical Layer Standards".
ETSI
8 ETSI EN 302 550-1-1 V1.1.1 (2010-02)
[i.5] ETSI TS 102 550 (V1.3.1): "Satellite Earth Stations and Systems (SES); Satellite Digital Radio
(SDR) Systems; Outer Physical Layer of the Radio Interface".
3 Symbols and abbreviations
3.1 Symbols
For the purposes of the present document, the following symbols apply:
Code rate
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AWGN Additive White Gaussian Noise
BCH Bose, Ray-Chaudhuri, Hocquenghem code
CRC Cyclic Redundancy Checksum
C-TS Channel-Transport Stream
CU Capacity Unit
FEC Forward Error Correction
ID IDentifier
IP Internet Protocol
IPL Inner Physical Layer
IU Interleaving Unit
LSB Least Significant Bit
MPEG-TS MPEG Transport Stream
MSB Most Significant Bit
MTU Maximum Transfer Unit
OPL Outer Physical Layer
PF Physical layer FEC
PFIW Physical layer FEC Info Word
PL Physical Layer
QoS Quality of Service
RFU Reserved for Future Use
SDR Satellite Digital Radio
SL Service Layer
SOF Start Of Frame
S-TS Service-Transport Stream
VBR Variable Bit Rate
WER Word Error Rate
XOR eXclusive OR
4 Outer physical layer
Refer to annex A for number format definitions.
4.1 Overview
Figure 1 displays the position and the interfaces of the Outer Physical Layer (in the following denoted by OPL) inside a
complete broadcast transmission chain. The OPL connects to the Service Layer, where the interface is Service
Transport Streams (S-TS) on the one side, and on the other side to the Inner Physical Layer (IPL - described in
EN 302 550-1-2 [i.2] and EN 302 550-1-3 [i.3]), where the interfaces are Channel Transport Streams (C-TS).
ETSI
9 ETSI EN 302 550-1-1 V1.1.1 (2010-02)
Figure 1: Position and interfaces of the OPL inside the transmission chain
The following table gives an overview about the terminology used for the data streaming through the system.
Description Comments
SC Service component E.g. source encoded audio or video or other data
SC-TS Service component transport stream
ES Elementary Stream ES: Elementary Stream, a generic term for one of the
coded video, coded audio or other coded data
bitstreams, cf. MPEG-1 standard
ISO/IEC 11172-1 [2].
Program A program is a collection of program In line with the definition used for MPEG standard
elements. Program elements may be ISO/IEC 13818-1 [1].
elementary streams (ES, SC-TS).
Service Set of programs and related auxiliary
information
S-TS Service transport stream Generalized term for transport stream. MPEG-TS is
one example for a service transport stream.
MPEG-TS Transport stream compliant to MPEG
standard ISO/IEC 13818-1 [1]
C-TS Channel transport stream Data stream (bit stream) representing the input to the
modulator = data stream including all redundancy
added by the FEC encoder - possibly with
time-interleaving - and carrying configuration
signalling information for the receiver.
The content of the C-TS is referred to as a C-TS
multiplex (a multiplex of encoded and interleaved
S-TS plus signalling information).
A bouquet of programs is carried by one or more
C-TS multiplexes.
ETSI
10 ETSI EN 302 550-1-1 V1.1.1 (2010-02)
Description Comments
Channel RF resource The meaning "RF resource" is aligned with the
terminology used for DVB.
The functionality of the Outer Physical Layer is to provide Forward Error Correction and time interleaving for
resistance against a variety of transmission channel conditions. Different transport channels are used in the OPL to offer
the requested performance for different types of services. These transport channels are called pipes in the scope of the
present document. The OPL is configurable in terms of error protection, outage mitigation in case of signal losses,
end-to-end delay, zapping time, payload throughput and receiver complexity.
Multiple pipes can be used as described above. Each of them contains FEC, Mixer and Disperser. One special pipe
exists whose functionality is to transmit all relevant parameters to decode the other pipes. The so-called signalling pipe
is always transmitted at the lowest coderate which is 1/5. The modulation of the signalling pipe is equal to the
modulation of the data pipes.
The general block diagram of the OPL functionality is given in figure 2.
ETSI
11 ETSI EN 302 550-1-1 V1.1.1 (2010-02)
Figure 2: General overview of the OPL functionality
ETSI
12 ETSI EN 302 550-1-1 V1.1.1 (2010-02)
The processing, multiplexing and demultiplexing of the data in the OPL is displayed in figure 3. An S-TS scheduler
multiplexes together all S-TS contained in the pipe. The scheduler is controlled by an S-TS schedule, which determines
the number of words taken from one S-TS before the multiplexer selects the next S-TS of the pipe. After an
encapsulation, FEC encoding and mixing, the codewords (segmented into interleaver units) are demultiplexed
codeword-wise to the slots of the considered pipe, each of the slots possessing its individual disperser. After
demultiplexing a codeword to a slot, i.e. to the input of its disperser, the slot demultiplexer selects the next
slot/disperser. At the outputs of the dispersers, the dispersed codewords are multiplexed together again by the collector
to form one pipe. The slot demultiplexer and the collector always select synchronously the same slot/disperser.
IUs of one slot Dispersed IUs of
Packets of an one slot
S-TS
Slots of IUs
OPL Slots or IUs of
Disperser
S-TS i one pipe of one
Encapsulation
Mixed
PF infowords PF codewords C-TS frame
codewords
OPL
S-TS i + 1
Encapsulation
C-TS
PL FEC Mixer Segmenter Disperser
mux
... Collector
Slot
Demux
OPL S-TS
S-TS j
Encapsulation scheduler
...
Number of S-TS
Disperser
in this pipe:
Num_STS
Number of
Dispersers in this
pipe:
Pipe_Width_Slots
Figure 3: Definition of the different blocks involved in the OPL processing
4.2 Interfacing to Service Layer (SL)
The interface to the service layer is the so-called Service-Transport Stream (S-TS). For the OPL, each S-TS source is
the smallest granularity which can be processed independently.
The interface may work synchronously or asynchronously. In the case of asynchronous interface, the PL must be able to
accept at least the average data rate that is provided by the SL. Any data buffering shall be done inside the SL, such that
no data from the S-TS is lost at this interface. When the PL requests new data for transmission, the SL can either
provide the requested data to the PL or it can signal that no data is currently available. If no data is available for
transmission, the PL instead transmits dummy data that is discarded in the receiver.
Inside an S-TS, multiplexing and de-multiplexing of information shall be carried out by the service layer.
Each pipe provides a different set of transmission parameters (e.g. FEC code rate and disperser profile), and achieves a
different QoS in terms of protection against transmission errors and end-to-end delay. One pipe of the OPL may carry
several S-TS, all with the same QoS parameters.
If PL time slicing is used, each time slice is associated with one S-TS. The scheduling of the S-TS, i.e. their start
instants and lengths, inside a pipe can be adapted frequently (once per schedule/time slicing period). This opens the
possibility of handling Variable Bit Rate (VBR) transmission.
The maximum allowed payload throughput per S-TS is 3,2 Mbit/s (this corresponds to approximately 8 to 10 video
services inside one S-TS). This is the throughput that the processing chain inside the receiver (e.g. the turbo decoder)
must be able to handle at least.
ETSI
13 ETSI EN 302 550-1-1 V1.1.1 (2010-02)
4.3 S-TS to OPL adaptation layer: S-TS encapsulation
The OPL is prepared to transport different types of S-TS, and a mixture of different S-TS types may be transported
simultaneously over one C-TS multiplex.
The following parameters have to be determined for each S-TS (for parameters, refer to signalling pipe in
clause 4.10.1):
• S-TS ID: identifier for the transported S-TS, that is unique for each network operator (i.e. for each
Operator_ID); observe that one S-TS may be transported over multiple instances of the PL and still have a
single unique S-TS ID; this helps, for example, for diversity combining of one S-TS transmitted over satellite
and simultaneously over terrestrial repeaters. Several rules apply for the S-TS:
- S-TS ID 0 plays a special role: this is the Service Layer configuration S-TS (the SL can signal its own
configuration via this S-TS).
- An S-TS may be fed to several C-TS multiplexes. The S-TS IDs in all of these C-TS multiplexes are
identical.
- An S-TS may not be fed to several pipes inside the same C-TS multiplex, and an S-TS may not be fed
several times to the same pipe inside one C-TS multiplex either.
- S-TS IDs must be unique over the complete network of one operator except for S-TS ID 0 which is
allowed on every C-TS multiplex.
- S-TS with an identical Operator_ID and S-TS ID can always be diversity combined (except for
S-TS ID 0).
- The length of an S-TS can be configured in a granularity of one PL infoword per C-TS frame.
• Pipe number that this S-TS is transported over.
Moreover, for the ensemble of S-TS contained inside a complete C-TS multiplex, the following parameters have to be
fixed (for parameters, refer also to signalling pipe in clause 4.10.1):
• Operator_ ID: unique identifier for the network operator.
• Partitioning of the C-TS multiplex into pipes and scheduling of the S-TS inside the pipes, i.e. what is the data
rate of one S-TS and when are the bursts of one S-TS transported.
Each S-TS is partitioned into packets to match the length of the PL FEC information word (PF infoword). The packet
size is individual for each type of S-TS. The OPL encapsulation inside the S-TS to OPL adaptation layer adapts the
length of the S-TS packets to the PF infoword length by appending a suffix to the S-TS packet. Table 1 defines the S-TS
packet length and the suffix length for different S-TS types.
Table 1: Defined S-TS type IDs
S-TS Type S-TS Type ID S-TS payload packet Suffix length Comment
Size in bytes in bits
Dummy packet 0 0 26 used for asynchronous sl/pl interface.
is discarded in receiver.
Transparent
1 1 532 26 sl has to decide what to do with this
data.
MPEG-TS 2 1 504 250 payload packet is 8 mpeg packets of
188 bytes each; additionally, a bch
code of 196 bits is applied.
IP stream 3 1 504 250 mtu of ip = 4 095 bytes with 2 bytes
additional header per packet.
RFU
4 to 7 reserved for future s-ts types.
The detailed format for the different types of S-TS is given in the following clauses. The Cyclic Redundancy Check
8 5 3 2
(CRC) polynomial, which appears in the following clauses, is x + x + x + x + x + 1 for all S-TS stream types. The
calculation of the CRC is described in annex B.
ETSI
14 ETSI EN 302 550-1-1 V1.1.1 (2010-02)
4.3.1 PF infoword format for S-TS stream type 0 (dummy packet)
The format of the dummy packet is given in table 2. The insertion of a dummy packet is performed if no data was
available at the instant of processing the actual packet in the OPL.
Table 2: PF infoword format for S-TS stream type 0 (dummy packet)
Start bit Wordsize
Parameter Description Format Comment
index (bits)
1 532×U8
0 Dummy data To be filled with zeros 12 256
(1 532 bytes)
helps to bit-align the payload to
12 256 RFU 4 bits reserved for future use 4 U4
byte boundaries.
12 260 STS_ID S-TS ID 8 U8 can be chosen arbitrarily.
12 268 STS_Stream_Type_ID S-TS stream type identifier 3 U3 fixed to 0 for dummy packets.
Version number of the OPL
12 271 Encap_Ver 3 U3 fixed to 0.
encapsulation format
CRC over the 18 relevant the light grey marked bits are
12 274 HeaderCRC 8 U8
bits of the header included in the header.
Total length of PFIW 12 282
4.3.2 PF infoword format for S-TS stream type 1 (transparent)
The format of the transparent mode is given in table 3. It provides a transparent transmission of whatever payload. The
throughput capability of the transparent stream type is 1 532 bytes per PF infoword. No additional error correction or
detection except the turbo code is used; therefore, data integrity and flow control needs to be performed by the link
layer. The definition of such protocol is not included in the present document.
Table 3: PF infoword format for S-TS stream type 1 (transparent)
Start bit Wordsize
Parameter Description Format Comment
index (bits)
1 532×U8 May include counters, error
0 Payload_Packet Transparent payload packet 12 256
(1 532 bytes) correction and error detection.
Helps to bit-align the payload
12 256 RFU 4 bits reserved for future use 4 U4
to byte boundaries.
12 260 STS_ID S-TS ID 8 U8
Fixed to 1 for transparent
12 268 STS_Stream_Type_ID S-TS stream type identifier 3 U3
packets.
Version number of the OPL
12 271 Encap_Ver 3 U3 Fixed to 0.
encapsulation format
CRC over the 18 relevant The light grey marked bits are
12 274 HeaderCRC 8 U8
bits of the header included in the CRC check.
Total length of PFIW 12 282
4.3.3 PF infoword format for S-TS stream type 2 (MPEG-TS)
The format of the MPEG-TS stream mode is given in table 4. It provides a transparent transmission of up to
8 MPEG-TS packets according to ISO/IEC 13818-1 [1], each having a size of 188 bytes. If less than 8 packets are
available for transport, the missing packets are filled by MPEG-TS null packets. Additional error correction and
detection is performed by using one shortened BCH (3 057, 3 008) code each 2 MPEG-TS packets. Therefore, each PF
infoword contains 4 sections of BCH parity of 49 bits each.
As this BCH-code is a systematic code, the parity may be discarded in the receiver if this additional parity check is not
desired; however, performance is supposed to degrade in this case. On the contrary, it is a mandatory requirement on
the transmitter side to include this parity.
ETSI
15 ETSI EN 302 550-1-1 V1.1.1 (2010-02)
The error correction code (overall minimum distance d = 10) is actually an outer BCH(3056, 3008, 9) code (with
min
minimum distance d = 9) concatenated by an inner single-parity check code (3057,3056,1). The BCH code is gained
min
by shortening a narrow-sense binary BCH(4095,4047,9)-Code. Concatenated encoding of (payload) message bits
m = (m ,mm,., ,m ) onto an (overall) codeword
3007 3006 1 0
c = (m ,mm,., ,m ,d ,d ,.,d ,d ,p ) is achieved as follows:
3007 3006 1 0 47 46 1 0 0
• The message bit m is gained from the temporally first bit (MSB of the temporally first byte) of the
temporally earlier MPEG-TS packet. The next message bit m corresponds to the temporally second bit (Bit
6 of the temporally first byte) of the temporally earlier MPEG-TS packet, and so on until bit m , which is
the temporally last bit (LSB of the temporally last byte) of the temporally earlier MPEG-TS packet. The
following 1 504 bits m to m are taken in the same manner from the temporally later MPEG-TS packet.
1503 0
3007 3006 48
• Multiply the message polynomial m(x) = m xm++x .+mx+m by x (the coefficients
3007 3006 1 0
of m(x) for exponents > 3 007 are all set to zero in order to shorten this BCH code; note that this corresponds
to temporally preceding the message by 1 039 zeros).
• Divide x m(x) by the BCH generator polynomial
48 44 41 37 36 34 32 29 27 26 21 17 16 13 7 5 3
g(x)=x+xx+ +x+++x x x+xx+ +xx+ +x+x+x+x+x+x+x+1
Let d(xd)=+x .+dx+ d be the remainder.
471 0
• Set the outer (i.e. BCH) codeword polynomial c (xx)(=+mx) d(x) .
o
• Calculate the single-parity check bit pc==(1x ) and set the overall codeword polynomial to
0 o
c(xc)=⋅()x x+p=xm()x+x⋅d()x+ p .
o00
Observe that the temporal transmission order of the bits of the codeword c is (m ,mm,., ,m ) for the
3007 3006 1 0
message part and (d ,dd,., ,d ,p ) for the parity part, i.e. the order is temporally descending for this BCH
4746 1 0 0
codeword-specific indexing. Note that by contrast the indexing of the bits inside the PF infoword is in temporally
ascending order, i.e. bit 0 to bit 12 281. Inside the Payload_Packet field of the PF infoword, there are four such message
parts (each representing 2 MPEG-TS packets or 376 bytes); the four associated parity parts are transmitted in the field
Parity_Parts in the same order.
Table 4: PF infoword format for S-TS stream type 2 (MPEG-TS)
Start bit Wordsize
Parameter Description Format Comments
index (bits)
1 504×U8
0 Payload_Packet 12 032
Payload packet (1 504 bytes)
Four times the 49 parity bits
of a shortened
12 032 Parity_Parts Parity bits for Error 196 4×U49 BCH(3 057,3 008)-code,
Detection or Outer Error which each protects 2
Correction Code MPEG-TS packets.
32 bits reserved for future Helps to bit-align the payload
12 228 RFU 32 U32
use to byte boundaries.
12 260 STS_ID S-TS ID 8 U8
12 268 STS_Stream_Type_ID S-TS stream type identifier 3 U3 Fixed to 2 for MPEG-TS.
Version number of the OPL
12 271 Encap_Ver 3 U3
encapsulation format Fixed to 0.
CRC over the 46 relevant The light grey marked bits are
12 274 CRC_Bits 8 U8
bits of the header included in the CRC check.
Total length of PFIW 12 282
ETSI
16 ETSI EN 302 550-1-1 V1.1.1 (2010-02)
4.3.4 PF infoword format for S-TS stream type 3 (IP stream)
The format of the IP stream mode is given in table 5. It provides a transparent transmission of IP packets, each having a
maximum size (MTU) of 4 095 bytes. Each IP packet to be transmitted is preceded by a header of 2 bytes that is defined
in table 6 and contains information about the IP packet format and length.
The payload size of one PF infoword is 1 504 bytes, but the amount of header information needs to be taken into
account. Each header consumes 2 bytes of the total payload available.
The address of the first available header within one PF infoword is contained in the parameter
First_Header_Address. Only this first header is announced; if more than one IP packets are present in one PF
infoword, the address of the headers can be incrementally derived from the preceding ones.
If no header was available in this PF infoword, the value 0xFFF is set to indicate the absence of any header.
See figure 4 for clarification.
If not enough payload is available for transport, the missing bytes are filled with 0xFF bytes. Any
First_Header_Address larger than 1 502 is not allowed as splitting of headers is not permitted. In this case, the
last byte(s) of the payload packet is (are) padded with 0xFF bytes.
Additional error correction and detection is performed by using one shortened BCH (3 057, 3 008) code each 376 bytes.
Therefore, each PF infoword contains 4 sections of BCH parity of 49 bits each.
As this BCH-code is a systematic code, the parity may be discarded in the receiver if this additional parity check is not
desired; however, performance is supposed to degrade in this case. On the contrary, it is a mandatory requirement on
the transmitter side to include this code.
The generation of the BCH codeword and the bit format is described in clause 4.3.3.
Table 5: PF infoword format for S-TS stream type 3 (IP stream)
Start bit Wordsize
Parameter Description Format Comment
index (bits)
1 504×U8
0 Payload_Packet Payload packet 12 032 See table 6 for further details.
(1 504 bytes)
Four times the 49 parity bits of
Parity bits for Error Detection a shortened
12 032 Parity_Parts or Outer Error Correction 196 4×U49 BCH(3 057,3 008)-code, which
Code each protects 376 payload
bytes.
20 bits reserved for future Helps to bit-align the payload to
12 228 RFU 20 U20
use byte boundaries.
This value gives the start
address of the first header to
be found. If no header is
Byte address where the first
present, the address is set to
header of the first IP packet
12 248 First_Header_Address 12 U12 0xFFF. Any
can be found; counting is
First_Header_Address
zero-based
larger than 1 502 needs to be
discarded while 1 502 is still
allowed.
12 260 STS_ID S-TS ID 8 U8
12 268 STS_Stream_Type_ID S-TS stream type identifier 3 U3 Fixed to 3 for IP stream.
Version number of the OPL
12 271 Encap_Ver 3 U3 Fixed to 0.
encapsulation format
CRC over the 46 relevant bits The light grey marked bits are
12 274 CRC_Bits 8 U8
of the header included in the CRC check.
Total length of PFIW
12 282
ETSI
17 ETSI EN 302 550-1-1 V1.1.1 (2010-02)
Table 6: IP Header definition for each IP packet processed by the OPL encapsulation
Start bit Wordsize
Parameter Description Format Comment
index (bits)
The following definitions apply:
0: reserved
Defines the type of the
0 IP_Packet_Type 2 U2 1: IPv4;
encapsulated packet
2: IPv6;
3: Padding/Stuffing.
Is set if the IP packet is
2 IP_Packet_Error 1 U1 0 if no error occurred.
erroneous
Defines the length of the IP This enables a maximum transfer
3 IP_Packet_Length 12 U12
Packet (in bytes) unit (MTU) size of 4 095 bytes.
14 RFU 1 bit reserved for future use 1 U1
Total length of one header 16
Figure 4: Description of IP packet encapsulation
4.4 PL FEC: turbo code
As PL FEC scheme, the Turbo Code as standardized by the 3GPP2 organization has been chosen.
4.4.1 Interface to OPL encapsulation
The turbo encoder encodes blocks of 12 282 bits, which are referred to as PL FEC information words (PF infoword), for
the payload transmission.
For each S-TS, these PF infowords are sequentially input to the turbo encoder after OPL encapsulation.
ETSI
18 ETSI EN 302 550-1-1 V1.1.1 (2010-02)
4.4.2 Turbo encoder
Besides the PF infowords for the S-TS payload of length 12 282 bits, the turbo encoder is also able to encode blocks of
762 bits for the signalling pipe. During encoding, an encoder output tail sequence is added. N is the total number of
turbo
data excluding the tail bits. The turbo encoder generates N /R encoded data output symbols followed by 6/R tail
turbo
output symbols, where R is the code rate.
The turbo encoder employs two systematic, recursive, convolutional encoders connected in parallel, with an interleaver,
the turbo interleaver, preceding the second recursive convolutional encoder. The two recursive convolutional codes are
called the constituent codes of the turbo code. The outputs of the constituent encoders are punctured to achieve the
(N + 6)/R output symbols.
turbo
A common constituent code is used for all turbo code rates. The transfer function for the constituent code is:
⎤
⎡
n(D) n(D)
G(D) = 1
⎥
⎢
d(D) d(D)
⎥
⎣
⎦
2 3 3 2 3
where d(D) = 1 + D + D , n (D) = 1 + D + D , and n (D) = 1 + D + D + D .
0 1
The turbo encoder generates an output symbol sequence that is identical to the one generated by the encoder shown in
figure 5. Initially, the states of the constituent encoder registers in this figure are set to zero. Then, the constituent
encoders are clocked with the switches in the positions noted.
Using the turbo encoder, the constituent encoder output symbols are generated by clocking the constituent encoders
N times with the switches in the up positions and puncturing as specified in table 7. Within a puncturing pattern, a
turbo
"0" means that the symbol shall be deleted and a "1" means that a symbol shall be passed. The puncturing patterns shall
be read from left to right and continuously from one text line to the next one. The patterns are displayed with a
partitioning into groups of 5 symbols. The 5 symbols of a group represent the outputs X Y Y Y' Y' of the encoder
0 1 0 1
shown in figure 5, respectively. Each puncturing pattern consists of one such group or of a sequence of several groups.
The displayed pattern is repeated cyclically, until 12 282 groups have been processed (one group per infoword bit).
Hence, the last period of the pattern remains incomplete for some puncturing patterns.
According to table 7, some examples for puncturing are given.
The turbo encoder shall generate symbols for rate 1/2 turbo codes as follows:
• The symbols output by the encoder for even-indexed data bit periods shall be XY .
• The symbols output by the encoder for odd-indexed data bit periods shall be XY' .
The turbo encoder shall generate symbols for rate 1/3 turbo codes as follows:
• The symbols output by the encoder for all data bit periods shall be XY Y' .
0 0
The turbo encoder shall generate symbols for rate 1/4 turbo codes as follows:
• The symbols output by the encoder for even-indexed data bit periods shall be XY Y Y' .
0 1 1
• The symbols output by the encoder for odd-indexed data bit periods shall be XY Y' Y' .
0 0 1
The turbo encoder shall generate symbols for rate 1/5 turbo codes as follows:
• The symbols output by the encoder for all data bit periods shall be XY Y Y' Y' .
0 1 0 1
Symbol repetition is not used in generating the encoded data output symbols.
ETSI
19 ETSI EN 302 550-1-1 V1.1.1 (2010-02)
Constituent Encoder 1
X
Y
n
Y
n
N
turbo
Bits
(Input)
d
Control
(N + 6)/R
turbo
Symbol
Code
Clocked once for each of the N bit periods with the switch up; then,
turbo
Puncture Symbols
clocked once for each of the three Constituent Encoder 1 tail bit periods with
(Output)
the switch down; then, not clocked for the three Constituent Encoder 2 tail bit
periods.
Turbo
Interleaver
Constituent Encoder 2
X'
Y'
n
Y'
n
d
Control
Clocked once for each of the N bit periods with the switch up; then, not
turbo
clocked for the three Constituent Encoder 1
tail bit periods; then, clocked once for each of the three
Constituent Encoder 2 tail bit periods with the switch down.
Figure 5: Turbo encoder
ETSI
20 ETSI EN 302 550-1-1 V1.1.1 (2010-02)
Table 7: Puncturing patterns for the turbo encoder during the data bit periods
Code
Puncturing Pattern (X; Y ; Y ; Y' ; Y' ; X; Y ; etc.)
Punct_Pat_ID Pattern Name
0 1 0 1 0
Rate
0 1/5 Standard 1;1;1;1;1
1 2/9 Standard 1;0;1;1;1; 1;1;1;1;1; 1;1;1;0;1; 1;1;1;1;1
2 1/4 Standard 1;1;1;0;1; 1;1;0;1;1
3 2/7 Standard 1;0;1;0;1; 1;0;1;1;1; 1;0;1;0;1; 1;1;1;0;1
1;1;0;1;0; 1;1;0;1;0; 1;1;0;1;0;
4 3/10 Standard
1;1;0;1;0; 1;1;0;1;0; 1;1;1;1;1
5 1/3 Standard 1;1;0;1;0
6 1/3 Complementary1 1;0;1;0;1
7 3/8 Standard 0;1;0;1;0; 1;1;0;1;0; 1;1;0;1;0
8 3/8 Complementary1 1;0;1;0;1; 0;0;1;0;1; 1;0;1;0;1
1;0;0;0;0; 1;0;1;0;1; 0;0;1;0;1;
1;0;1;0;1; 1;0;1;0;1; 0;0;1;0;1;
9 2/5 Standard
1;0;1;0;1; 1;0;1;0;1; 0;0;1;0;1;
1;0;1;0;1; 1;0;1;0;1; 0;0;1;0;1
1;1;0;1;0; 0;1;0;1;0; 1;1;0;1;0;
1;1;0;1;0; 0;1;0;1;0; 1;0;0;0;0;
10 2/5 Complementary1
1;1;0;1;0; 0;1;0;1;0; 1;1;0;1;0;
1;1;0;1;0; 0;1;0;1;0; 1;1;0;1;0
1;0;0;0;0; 1;1;0;1;0; 0;1;0;1;0;
11 3/7 Standard
1;1;0;1;0; 0;1;0;1;0; 1;1;0;1;0
1;0;1;0;1; 0;0;1;0;1; 1;0;1;0;1;
12 3/7 Complementary1
1;0;0;0;0; 1;0;1;0;1; 0;0;1;0;1
13 1/2 Standard 1;1;0;0;0; 1;0;0;1;0
14 1/2 Complementary1 1;0;0;1;0; 1;1;0;0;0
15 1/2 Complementary2 1;0;1;0;0; 1;0;0;0
...
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Satellite Earth Stations and Systems (SES) - Satellite Digital Radio (SDR) Systems - Part 1: Physical Layer of the Radio Interface - Sub-part 1: Outer Physical Layer35.100.10Physical layer33.060.30Radiorelejni in fiksni satelitski komunikacijski sistemiRadio relay and fixed satellite communications systemsICS:Ta slovenski standard je istoveten z:EN 302 550-1-1 Version 1.1.1SIST EN 302 550-1-1 V1.1.1:2010en01-april-2010SIST EN 302 550-1-1 V1.1.1:2010SLOVENSKI
STANDARD
ETSI ETSI EN 302 550-1-1 V1.1.1 (2010-02)2
Reference DEN/SES-00312-1-1 Keywords digital, layer 1, radio, satellite 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 2010. All rights reserved.
DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association. SIST EN 302 550-1-1 V1.1.1:2010
ETSI ETSI EN 302 550-1-1 V1.1.1 (2010-02)3 Contents Intellectual Property Rights . 5 Foreword . 5 Introduction . 5 1 Scope . 7 2 References . 7 2.1 Normative references . 7 2.2 Informative references . 7 3 Symbols and abbreviations . 8 3.1 Symbols . 8 3.2 Abbreviations . 8 4 Outer physical layer. 8 4.1 Overview . 8 4.2 Interfacing to Service Layer (SL) . 12 4.3 S-TS to OPL adaptation layer: S-TS encapsulation . 13 4.3.1 PF infoword format for S-TS stream type 0 (dummy packet) . 14 4.3.2 PF infoword format for S-TS stream type 1 (transparent) . 14 4.3.3 PF infoword format for S-TS stream type 2 (MPEG-TS) . 14 4.3.4 PF infoword format for S-TS stream type 3 (IP stream) . 16 4.4 PL FEC: turbo code . 17 4.4.1 Interface to OPL encapsulation . 17 4.4.2 Turbo encoder . 18 4.4.3 Turbo code termination . 21 4.4.4 Turbo Interleavers . 23 4.4.5 Output of turbo encoder . 24 4.4.6 FEC Parameter signalling . 24 4.4.7 Diversity combining . 25 4.4.8 FEC Parameters for the signalling pipe . 25 4.5 Mixer . 25 4.6 Segmenter and Slot demultiplexer . 26 4.7 Disperser. 27 4.8 Collector . 28 4.9 C-TS multiplexer . 29 4.10 Configuration of the OPL . 30 4.10.1 Signalling pipe . 30 4.10.1.1 Encoding and interleaving of signalling pipe . 30 4.10.1.2 SOF Preamble . 31 4.10.1.3 Format of the signalling pipe infoword . 31 4.10.2 Partitioning of the C-TS multiplex . 36 4.10.3 S-TS schedule and slot allocation . 37 4.10.4 S-TS re-scheduling and slot re-allocation . 38 4.10.5 Birth/death of S-TS . 38 4.10.6 S-TS ID . 38 4.10.7 Calculation of the disperser profile . 39 4.10.8 Configuration of the tail pipe . 40 4.10.9 Unused pipes . 40 4.10.10 Announcing reconfigurations and reschedulings . 40 4.10.11 Pipe reconfiguration . 41 4.11 Network aspects . 45 Annex A (normative): Number format definitions . 47 A.1 Number format and transmission order . 47 A.2 SI-Prefix Notation . 47 SIST EN 302 550-1-1 V1.1.1:2010
ETSI ETSI EN 302 550-1-1 V1.1.1 (2010-02)4 A.3 Default Settings . 47 Annex B (normative): Calculation of the CRC word . 48 Annex C (informative): Bibliography . 49 History . 50
ETSI ETSI EN 302 550-1-1 V1.1.1 (2010-02)5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http://webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Satellite Earth Stations and Systems (SES). The present document is part 1, sub-part 1 of a multi-part deliverable covering Satellite Digital Radio (SDR), as identified below: Part 1: "Physical Layer of the Radio Interface"; Sub-part 1: "Outer Physical Layer"; Sub-part 2: "Inner Physical Layer Single Carrier Modulation"; Sub-part 3: "Inner Physical Layer Multi Carrier Modulation".
National transposition dates Date of adoption of this EN: 15 February 2010 Date of latest announcement of this EN (doa): 31 May 2010 Date of latest publication of new National Standard or endorsement of this EN (dop/e):
30 November 2010 Date of withdrawal of any conflicting National Standard (dow): 30 November 2010
Introduction TC SES is producing standards and other deliverables for Satellite Digital Radio (SDR) systems. An SDR system enables broadcast to fixed and mobile receivers through satellites and complementary terrestrial transmitters. Functionalities, architecture and technologies of such systems are described in TR 102 525 [i.1]. Several existing and planned ETSI standards specify parts of the SDR system, with the aim of interoperable implementations. The physical layer of the radio interface (air interface) is divided up into the outer physical layer, the inner physical layer with a single carrier modulation, and the inner physical layer with multi carrier modulation. These parts can be used all together in SDR compliant equipment, or in conjunction with other existing and future specifications. SIST EN 302 550-1-1 V1.1.1:2010
ETSI ETSI EN 302 550-1-1 V1.1.1 (2010-02)6 The present document specifies the outer physical layer. The inner physical layer with single carrier modulation is specified in EN 302 550-1-2 [i.2], and with multi carrier modulation in EN 302 550-1-3 [i.3]. Guidelines for using the physical layer standard can be found in TR 102 604 [i.4]. The physical layer specifications have previously been published as "Technical Specification (TS)" type ETSI deliverables. The present document supersedes TS 102 550 [i.5] and is recommended for new implementations. SIST EN 302 550-1-1 V1.1.1:2010
ETSI ETSI EN 302 550-1-1 V1.1.1 (2010-02)7 1 Scope The present document concerns the radio interface of SDR broadcast receivers. It specifies the functionality of the outer physical layer. It allows implementing this part of the system in an interoperable way. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ISO/IEC 13818-1: "Information technology - Generic coding of moving pictures and associated audio information: Systems". [2] ISO/IEC 11172-1: "Information technology - Coding of moving pictures and associated audio for digital storage media at up to about 1,5 Mbit/s - Part 1: Systems". 2.2 Informative references The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI TR 102 525: "Satellite Earth Stations and Systems (SES); Satellite Digital Radio (SDR) service; Functionalities, architecture and technologies". [i.2] ETSI EN 302 550-1-2: "Satellite Earth Stations and Systems (SES); Satellite Digital Radio (SDR) Systems; Part 1: Physical Layer of the Radio Interface; Sub-part 2: Inner Physical Layer Single Carrier Modulation". [i.3] ETSI EN 302 550-1-3: "Satellite Earth Stations and Systems (SES); Satellite Digital Radio (SDR) Systems; Part 1: Physical Layer of the Radio Interface; Sub-part 3: Inner Physical Layer Multi Carrier Modulation". [i.4] ETSI TR 102 604: "Satellite Earth Stations and Systems (SES); Satellite Digital Radio (SDR) Systems; Guidelines for the Use of the Physical Layer Standards". SIST EN 302 550-1-1 V1.1.1:2010
ETSI ETSI EN 302 550-1-1 V1.1.1 (2010-02)8 [i.5] ETSI TS 102 550 (V1.3.1): "Satellite Earth Stations and Systems (SES); Satellite Digital Radio (SDR) Systems; Outer Physical Layer of the Radio Interface". 3 Symbols and abbreviations 3.1 Symbols For the purposes of the present document, the following symbols apply: Code rate 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AWGN Additive White Gaussian Noise BCH Bose, Ray-Chaudhuri, Hocquenghem code CRC Cyclic Redundancy Checksum C-TS Channel-Transport Stream CU Capacity Unit FEC Forward Error Correction ID IDentifier IP Internet Protocol IPL Inner Physical Layer IU Interleaving Unit LSB Least Significant Bit MPEG-TS MPEG Transport Stream MSB Most Significant Bit MTU Maximum Transfer Unit OPL Outer Physical Layer PF Physical layer FEC PFIW Physical layer FEC Info Word PL Physical Layer QoS Quality of Service RFU Reserved for Future Use SDR Satellite Digital Radio SL Service Layer SOF Start Of Frame S-TS Service-Transport Stream VBR Variable Bit Rate WER Word Error Rate XOR eXclusive OR 4 Outer physical layer Refer to annex A for number format definitions. 4.1 Overview Figure 1 displays the position and the interfaces of the Outer Physical Layer (in the following denoted by OPL) inside a complete broadcast transmission chain. The OPL connects to the Service Layer, where the interface is Service Transport Streams (S-TS) on the one side, and on the other side to the Inner Physical Layer (IPL - described in EN 302 550-1-2 [i.2] and EN 302 550-1-3 [i.3]), where the interfaces are Channel Transport Streams (C-TS). SIST EN 302 550-1-1 V1.1.1:2010
ETSI ETSI EN 302 550-1-1 V1.1.1 (2010-02)9
Figure 1: Position and interfaces of the OPL inside the transmission chain The following table gives an overview about the terminology used for the data streaming through the system.
Description
Comments SC Service component E.g. source encoded audio or video or other data SC-TS Service component transport stream
ES Elementary Stream ES: Elementary Stream, a generic term for one of the coded video, coded audio or other coded data bitstreams, cf. MPEG-1 standard ISO/IEC 11172-1 [2]. Program A program is a collection of program elements. Program elements may be elementary streams (ES, SC-TS). In line with the definition used for MPEG standard ISO/IEC 13818-1 [1]. Service
Set of programs and related auxiliary information
S-TS Service transport stream
Generalized term for transport stream. MPEG-TS is one example for a service transport stream.
MPEG-TS Transport stream compliant to MPEG standard ISO/IEC 13818-1 [1]
C-TS Channel transport stream Data stream (bit stream) representing the input to the modulator = data stream including all redundancy added by the FEC encoder - possibly with time-interleaving - and carrying configuration signalling information for the receiver. The content of the C-TS is referred to as a C-TS multiplex (a multiplex of encoded and interleaved S-TS plus signalling information). A bouquet of programs is carried by one or more C-TS multiplexes. SIST EN 302 550-1-1 V1.1.1:2010
ETSI ETSI EN 302 550-1-1 V1.1.1 (2010-02)10
Description
Comments Channel
RF resource
The meaning "RF resource" is aligned with the terminology used for DVB.
The functionality of the Outer Physical Layer is to provide Forward Error Correction and time interleaving for resistance against a variety of transmission channel conditions. Different transport channels are used in the OPL to offer the requested performance for different types of services. These transport channels are called pipes in the scope of the present document. The OPL is configurable in terms of error protection, outage mitigation in case of signal losses, end-to-end delay, zapping time, payload throughput and receiver complexity.
Multiple pipes can be used as described above. Each of them contains FEC, Mixer and Disperser. One special pipe exists whose functionality is to transmit all relevant parameters to decode the other pipes. The so-called signalling pipe is always transmitted at the lowest coderate which is 1/5. The modulation of the signalling pipe is equal to the modulation of the data pipes.
The general block diagram of the OPL functionality is given in figure 2. SIST EN 302 550-1-1 V1.1.1:2010
ETSI ETSI EN 302 550-1-1 V1.1.1 (2010-02)11
Figure 2: General overview of the OPL functionality SIST EN 302 550-1-1 V1.1.1:2010
ETSI ETSI EN 302 550-1-1 V1.1.1 (2010-02)12 The processing, multiplexing and demultiplexing of the data in the OPL is displayed in figure 3. An S-TS scheduler multiplexes together all S-TS contained in the pipe. The scheduler is controlled by an S-TS schedule, which determines the number of words taken from one S-TS before the multiplexer selects the next S-TS of the pipe. After an encapsulation, FEC encoding and mixing, the codewords (segmented into interleaver units) are demultiplexed codeword-wise to the slots of the considered pipe, each of the slots possessing its individual disperser. After demultiplexing a codeword to a slot, i.e. to the input of its disperser, the slot demultiplexer selects the next slot/disperser. At the outputs of the dispersers, the dispersed codewords are multiplexed together again by the collector to form one pipe. The slot demultiplexer and the collector always select synchronously the same slot/disperser.
OPL EncapsulationPL FECMixerSegmenterDisperserDisperserDisperserSlotDemuxCollectorC-TSmuxS-TS iS-TS i + 1.Packets of anS-TSPF infowordsPF codewordsMixed codewordsSlots of IUsIUs of one slotDispersed IUs of one slotSlots or IUs of one pipe of one C-TS frameS-TS jS-TSschedulerNumber of S-TS in this pipe:Num_STSNumber of Dispersers in this pipe:Pipe_Width_SlotsOPL EncapsulationOPL Encapsulation Figure 3: Definition of the different blocks involved in the OPL processing 4.2 Interfacing to Service Layer (SL) The interface to the service layer is the so-called Service-Transport Stream (S-TS). For the OPL, each S-TS source is the smallest granularity which can be processed independently.
The interface may work synchronously or asynchronously. In the case of asynchronous interface, the PL must be able to accept at least the average data rate that is provided by the SL. Any data buffering shall be done inside the SL, such that no data from the S-TS is lost at this interface. When the PL requests new data for transmission, the SL can either provide the requested data to the PL or it can signal that no data is currently available. If no data is available for transmission, the PL instead transmits dummy data that is discarded in the receiver. Inside an S-TS, multiplexing and de-multiplexing of information shall be carried out by the service layer.
Each pipe provides a different set of transmission parameters (e.g. FEC code rate and disperser profile), and achieves a different QoS in terms of protection against transmission errors and end-to-end delay. One pipe of the OPL may carry several S-TS, all with the same QoS parameters.
If PL time slicing is used, each time slice is associated with one S-TS. The scheduling of the S-TS, i.e. their start instants and lengths, inside a pipe can be adapted frequently (once per schedule/time slicing period). This opens the possibility of handling Variable Bit Rate (VBR) transmission. The maximum allowed payload throughput per S-TS is 3,2 Mbit/s (this corresponds to approximately 8 to 10 video services inside one S-TS). This is the throughput that the processing chain inside the receiver (e.g. the turbo decoder) must be able to handle at least. SIST EN 302 550-1-1 V1.1.1:2010
ETSI ETSI EN 302 550-1-1 V1.1.1 (2010-02)13 4.3 S-TS to OPL adaptation layer: S-TS encapsulation The OPL is prepared to transport different types of S-TS, and a mixture of different S-TS types may be transported simultaneously over one C-TS multiplex. The following parameters have to be determined for each S-TS (for parameters, refer to signalling pipe in clause 4.10.1): • S-TS ID: identifier for the transported S-TS, that is unique for each network operator (i.e. for each Operator_ID); observe that one S-TS may be transported over multiple instances of the PL and still have a single unique S-TS ID; this helps, for example, for diversity combining of one S-TS transmitted over satellite and simultaneously over terrestrial repeaters. Several rules apply for the S-TS: - S-TS ID 0 plays a special role: this is the Service Layer configuration S-TS (the SL can signal its own configuration via this S-TS). - An S-TS may be fed to several C-TS multiplexes. The S-TS IDs in all of these C-TS multiplexes are identical. - An S-TS may not be fed to several pipes inside the same C-TS multiplex, and an S-TS may not be fed several times to the same pipe inside one C-TS multiplex either. - S-TS IDs must be unique over the complete network of one operator except for S-TS ID 0 which is allowed on every C-TS multiplex. - S-TS with an identical Operator_ID and S-TS ID can always be diversity combined (except for S-TS ID 0). - The length of an S-TS can be configured in a granularity of one PL infoword per C-TS frame. • Pipe number that this S-TS is transported over. Moreover, for the ensemble of S-TS contained inside a complete C-TS multiplex, the following parameters have to be fixed (for parameters, refer also to signalling pipe in clause 4.10.1): • Operator_ ID: unique identifier for the network operator. • Partitioning of the C-TS multiplex into pipes and scheduling of the S-TS inside the pipes, i.e. what is the data rate of one S-TS and when are the bursts of one S-TS transported. Each S-TS is partitioned into packets to match the length of the PL FEC information word (PF infoword). The packet size is individual for each type of S-TS. The OPL encapsulation inside the S-TS to OPL adaptation layer adapts the length of the S-TS packets to the PF infoword length by appending a suffix to the S-TS packet. Table 1 defines the S-TS packet length and the suffix length for different S-TS types. Table 1: Defined S-TS type IDs S-TS Type S-TS Type ID S-TS payload packet Size in bytes Suffix length in bits Comment Dummy packet 0 0 26 used for asynchronous sl/pl interface. is discarded in receiver. Transparent 1 1 532 26 sl has to decide what to do with this data. MPEG-TS 2 1 504 250 payload packet is 8 mpeg packets of 188 bytes each; additionally, a bch code of 196 bits is applied. IP stream 3 1 504 250 mtu of ip = 4 095 bytes with 2 bytes additional header per packet. RFU 4 to 7
reserved for future s-ts types.
The detailed format for the different types of S-TS is given in the following clauses. The Cyclic Redundancy Check (CRC) polynomial, which appears in the following clauses, is x8 + x5 + x3 + x2 + x + 1 for all S-TS stream types. The calculation of the CRC is described in annex B. SIST EN 302 550-1-1 V1.1.1:2010
ETSI ETSI EN 302 550-1-1 V1.1.1 (2010-02)14 4.3.1 PF infoword format for S-TS stream type 0 (dummy packet) The format of the dummy packet is given in table 2. The insertion of a dummy packet is performed if no data was available at the instant of processing the actual packet in the OPL. Table 2: PF infoword format for S-TS stream type 0 (dummy packet) Start bit index Parameter Description Wordsize (bits) Format Comment 0 Dummy data To be filled with zeros 12 256 1 532×U8
(1 532 bytes)
12 256 RFU 4 bits reserved for future use 4 U4 helps to bit-align the payload to byte boundaries. 12 260 STS_ID S-TS ID 8 U8 can be chosen arbitrarily. 12 268 STS_Stream_Type_ID S-TS stream type identifier 3 U3 fixed to 0 for dummy packets. 12 271 Encap_Ver Version number of the OPL encapsulation format 3 U3 fixed to 0. 12 274 HeaderCRC CRC over the 18 relevant bits of the header 8 U8 the light grey marked bits are included in the header.
Total length of PFIW 12 282
4.3.2 PF infoword format for S-TS stream type 1 (transparent) The format of the transparent mode is given in table 3. It provides a transparent transmission of whatever payload. The throughput capability of the transparent stream type is 1 532 bytes per PF infoword. No additional error correction or detection except the turbo code is used; therefore, data integrity and flow control needs to be performed by the link layer. The definition of such protocol is not included in the present document.
Table 3: PF infoword format for S-TS stream type 1 (transparent) Start bit index Parameter Description Wordsize (bits) Format Comment 0 Payload_Packet Transparent payload packet 12 256 1 532×U8 (1 532 bytes) May include counters, error correction and error detection. 12 256 RFU 4 bits reserved for future use 4 U4 Helps to bit-align the payload to byte boundaries. 12 260 STS_ID S-TS ID 8 U8
12 268 STS_Stream_Type_ID S-TS stream type identifier 3 U3 Fixed to 1 for transparent packets. 12 271 Encap_Ver Version number of the OPL encapsulation format 3 U3 Fixed to 0. 12 274 HeaderCRC CRC over the 18 relevant bits of the header 8 U8 The light grey marked bits are included in the CRC check.
Total length of PFIW 12 282
4.3.3 PF infoword format for S-TS stream type 2 (MPEG-TS) The format of the MPEG-TS stream mode is given in table 4. It provides a transparent transmission of up to 8 MPEG-TS packets according to ISO/IEC 13818-1 [1], each having a size of 188 bytes. If less than 8 packets are available for transport, the missing packets are filled by MPEG-TS null packets. Additional error correction and detection is performed by using one shortened BCH (3 057, 3 008) code each 2 MPEG-TS packets. Therefore, each PF infoword contains 4 sections of BCH parity of 49 bits each.
As this BCH-code is a systematic code, the parity may be discarded in the receiver if this additional parity check is not desired; however, performance is supposed to degrade in this case. On the contrary, it is a mandatory requirement on the transmitter side to include this parity.
ETSI ETSI EN 302 550-1-1 V1.1.1 (2010-02)15 The error correction code (overall minimum distance dmin = 10) is actually an outer BCH(3056, 3008, 9) code (with minimum distance dmin = 9) concatenated by an inner single-parity check code (3057,3056,1). The BCH code is gained by shortening a narrow-sense binary BCH(4095,4047,9)-Code. Concatenated encoding of (payload) message bits m3007300610(,,.,,)mmmm=onto an (overall) codeword
c = 30073006104746100(,,.,,,,,.,,,)mmmmddddpis achieved as follows: • The message bit m3007 is gained from the temporally first bit (MSB of the temporally first byte) of the temporally earlier MPEG-TS packet. The next message bit m3006 corresponds to the temporally second bit (Bit 6 of the temporally first byte) of the temporally earlier MPEG-TS packet, and so on until bit m1504, which is the temporally last bit (LSB of the temporally last byte) of the temporally earlier MPEG-TS packet. The following 1 504 bits m1503 to m0 are taken in the same manner from the temporally later MPEG-TS packet. • Multiply the message polynomial m(x) = 300730063007300610.mxmxmxm++++ by 48x (the coefficients of m(x) for exponents > 3 007 are all set to zero in order to shorten this BCH code; note that this corresponds to temporally preceding the message by 1 039 zeros). • Divide 48xm(x) by the BCH generator polynomial
Let 474710().dxdxdxd=+++be the remainder. • Set the outer (i.e. BCH) codeword polynomial 48()()()ocxxmxdx=+. • Calculate the single-parity check bit 0(1)opcx== and set the overall codeword polynomial to 4900()()()()ocxcxxpxmxxdxp=⋅+=+⋅+. Observe that the temporal transmission order of the bits of the codeword c is 3007300610(,,.,,)mmmm for the message part and 4746100(,,.,,,)ddddp for the parity part, i.e. the order is temporally descending for this BCH codeword-specific indexing. Note that by contrast the indexing of the bits inside the PF infoword is in temporally ascending order, i.e. bit 0 to bit 12 281. Inside the Payload_Packet field of the PF infoword, there are four such message parts (each representing 2 MPEG-TS packets or 376 bytes); the four associated parity parts are transmitted in the field Parity_Parts in the same order. Table 4: PF infoword format for S-TS stream type 2 (MPEG-TS) Start bit index Parameter Description Wordsize (bits) Format Comments 0 Payload_Packet Payload packet 12 032 1 504×U8
(1 504 bytes)
12 032 Parity_Parts Parity bits for Error Detection or Outer Error Correction Code 196 4×U49 Four times the 49 parity bits of a shortened BCH(3 057,3 008)-code, which each protects 2 MPEG-TS packets. 12 228 RFU 32 bits reserved for future use 32 U32 Helps to bit-align the payload to byte boundaries. 12 260 STS_ID S-TS ID 8 U8
12 268 STS_Stream_Type_ID S-TS stream type identifier 3 U3 Fixed to 2 for MPEG-TS. 12 271 Encap_Ver Version number of the OPL encapsulation format 3 U3 Fixed to 0. 12 274 CRC_Bits CRC over the 46 relevant bits of the header 8 U8 The light grey marked bits are included in the CRC check.
Total length of PFIW 12 282
4844413736343229272621171613753()1gxxxxxxxxxxxxxxxxxxx=++++++++++++++++++SIST EN 302 550-1-1 V1.1.1:2010
ETSI ETSI EN 302 550-1-1 V1.1.1 (2010-02)16 4.3.4 PF infoword format for S-TS stream type 3 (IP stream) The format of the IP stream mode is given in table 5. It provides a transparent transmission of IP packets, each having a maximum size (MTU) of 4 095 bytes. Each IP packet to be transmitted is preceded by a header of 2 bytes that is defined in table 6 and contains information about the IP packet format and length.
The payload size of one PF infoword is 1 504 bytes, but the amount of header information needs to be taken into account. Each header consumes 2 bytes of the total payload available.
The address of the first available header within one PF infoword is contained in the parameter First_Header_Address. Only this first header is announced; if more than one IP packets are present in one PF infoword, the address of the headers can be incrementally derived from the preceding ones.
If no header was available in this PF infoword, the value 0xFFF is set to indicate the absence of any header.
See figure 4 for clarification.
If not enough payload is available for transport, the missing bytes are filled with 0xFF bytes. Any First_Header_Address larger than 1 502 is not allowed as splitting of headers is not permitted. In this case, the last byte(s) of the payload packet is (are) padded with 0xFF bytes.
Additional error correction and detection is performed by using one shortened BCH (3 057, 3 008) code each 376 bytes. Therefore, each PF infoword contains 4 sections of BCH parity of 49 bits each. As this BCH-code is a systematic code, the parity may be discarded in the receiver if this additional parity check is not desired; however, performance is supposed to degrade in this case. On the contrary, it is a mandatory requirement on the transmitter side to include this code.
The generation of the BCH codeword and the bit format is described in clause 4.3.3. Table 5: PF infoword format for S-TS stream type 3 (IP stream) Start bit index Parameter Description Wordsize (bits) Format Comment 0 Payload_Packet Payload packet 12 032 1 504×U8 (1 504 bytes) See table 6 for further details. 12 032 Parity_Parts Parity bits for Error Detection or Outer Error Correction Code 196 4×U49 Four times the 49 parity bits of a shortened BCH(3 057,3 008)-code, which each protects 376 payload bytes. 12 228 RFU 20 bits reserved for future use 20 U20 Helps to bit-align the payload to byte boundaries. 12 248 First_Header_Address Byte address where the first header of the first IP packet can be found; counting is zero-based 12 U12 This value gives the start address of the first header to be found. If no header is present, the address is set to 0xFFF. Any First_Header_Address larger than 1 502 needs to be discarded while 1 502 is still allowed. 12 260 STS_ID S-TS ID 8 U8
12 268 STS_Stream_Type_ID S-TS stream type identifier 3 U3 Fixed to 3 for IP stream. 12 271 Encap_Ver Version number of the OPL encapsulation format 3 U3 Fixed to 0. 12 274 CRC_Bits CRC over the 46 relevant bits of the header 8 U8 The light grey marked bits are included in the CRC check.
Total length of PFIW 12 282
ETSI ETSI EN 302 550-1-1 V1.1.1 (2010-02)17 Table 6: IP Header definition for each IP packet processed by the OPL encapsulation Start bit index Parameter Description Wordsize (bits) Format Comment 0 IP_Packet_Type Defines the type of the encapsulated packet 2 U2 The following definitions apply:
0: reserved
1: IPv4;
2: IPv6;
3: Padding/Stuffing.
2 IP_Packet_Error Is set if the IP packet is erroneous 1 U1 0 if no error occurred. 3 IP_Packet_Length Defines the length of the IP Packet (in bytes) 12 U12 This enables a maximum transfer unit (MTU) size of 4 095 bytes. 14 RFU 1 bit reserved for future use 1 U1
Total length of one header 16
Figure 4: Description of IP packet encapsulation 4.4 PL FEC: turbo code As PL FEC scheme, the Turbo Code as standardized by the 3GPP2 organization has been chosen. 4.4.1 Interface to OPL encapsulation The turbo encoder encodes blocks of 12 282 bits, which are referred to as PL FEC information words (PF infoword), for the payload transmission.
For each S-TS, these PF infowords are sequentially input to the turbo encoder after OPL encapsulation. SIST EN 302 550-1-1 V1.1.1:2010
ETSI ETSI EN 302 550-1-1 V1.1.1 (2010-02)18 4.4.2 Turbo encoder Besides the PF infowords for the S-TS payload of length 12 282 bits, the turbo encoder is also able to encode blocks of 762 bits for the signalling pipe. During encoding, an encoder output tail sequence is added. Nturbo is the total number of data excluding the tail bits. The turbo encoder generates Nturbo/R encoded data output symbols followed by 6/R tail output symbols, where R is the code rate. The turbo encoder employs two systematic, recursive, convolutional encoders connected in parallel, with an interleaver, the turbo interleaver, preceding the second recursive convolutional encoder. The two recursive convolutional codes are called the constituent codes of the turbo code. The outputs of the constituent encoders are punctured to achieve the (Nturbo + 6)/R output symbols. A common constituent code is used for all turbo code rates. The transfer function for the constituent code is: 01n(D)n(D)G(D)
1d(D)d(D)⎤⎡=⎥⎢⎥⎣⎦ where d(D) = 1 + D2 + D3, n0(D) = 1 + D + D3, and n1(D) = 1 + D + D2 + D3. The turbo encoder generates an output symbol sequence that is identical to the one generated by the encoder shown in figure 5. Initially, the states of the constituent encoder registers in this figure are set to zero. Then, the constituent encoders are clocked with the switches in the positions noted. Using the turbo encoder, the constituent encoder output symbols are generated by clocking the constituent encoders Nturbo times with the switches in the up positions and puncturing as specified in table 7. Within a puncturing pattern, a "0" means that the symbol shall be deleted and a "1" means that a symbol shall be passed. The puncturing patterns shall be read from left to right and continuously from one text line to the next one. The patterns are displayed with a partitioning into groups of 5 symbols. The 5 symbols of a group represent the outputs X Y0 Y1 Y'0 Y'1 of the encoder shown in figure 5, respectively. Each puncturing pattern consists of one such group or of a sequence of several groups. The displayed pattern is repeated cyclically, until 12 282 groups have been processed (one group per infoword bit). Hence, the last period of the pattern remains incomplete for some puncturing patterns. According to table 7, some examples for puncturing are given. The turbo encoder shall generate symbols for rate 1/2 turbo codes as follows: • The symbols output by the encoder for even-indexed data bit periods shall be XY0. • The symbols output by the encoder for odd-indexed data bit periods shall be XY'0. The turbo encoder shall generate symbols for rate 1/3 turbo codes as follows: • The symbols output by the encoder for all data bit periods shall be XY0Y'0. The turbo encoder shall generate symbols for rate 1/4 turbo codes as follows: • The symbols output by the encoder for even-indexed data bit periods shall be XY0Y1Y'1. • The symbols output by the encoder for odd-indexed data bit periods shall be XY0Y'0Y'1. The turbo encoder shall generate symbols for rate 1/5 turbo codes as follows: • The symbols output by the encoder for all data bit periods shall be XY0Y1Y'0Y'1. Symbol repetition is not used in generating the encoded data output symbols. SIST EN 302 550-1-1 V1.1.1:2010
ETSI ETSI EN 302 550-1-1 V1.1.1 (2010-02)19 TurboInterleaverX'Y'0Y'1Constituent Encoder 2 n1n0dClocked once for each of the Nturbo bit periods with the switch up; then, not clocked for the three Constituent Encoder 1tail bit periods; then, clocked once for each of the threeConstituent Encoder 2 tail
bit periods with the switch down.ControlXY0Y1Constituent Encoder 1 n1n0dClocked once for each of the Nturbo bit periods with the switch up; then, clocked once for each of the three Constituent Encoder 1 tail
bit periods with the switch down; then, not clocked for the three Constituent Encoder 2 tail bit periods.ControlSymbolPunctureNturboBits(Input)(Nturbo + 6)/RCodeSymbols(Output) Figure 5: Turbo encoder SIST EN 302 550-1-1 V1.1.1:2010
ETSI ETSI EN 302 550-1-1 V1.1.1 (2010-02)20 Table 7: Puncturing patterns for the turbo encoder during the data bit periods Punct_Pat_ID Code Rate Pattern Name Puncturing Pattern (X; Y0; Y1; Y'0; Y'1; X; Y0; etc.) 0 1/5 Standard 1;1;1;1;1 1 2/9 Standard 1;0;1;1;1; 1;1;1;1;1; 1;1;1;0;1; 1;1;1;1;1 2 1/4 Standard 1;1;1;0;1; 1;1;0;1;1 3 2/7 Standard 1;0;1;0;1; 1;0;1;1;1; 1;0;1;0;1; 1;1;1;0;1 4 3/10 Standard 1;1;0;1;0; 1;1;0;1;0; 1;1;0;1;0; 1;1;0;1;0; 1;1;0;1;0; 1;1;1;1;1 5 1/3 Standard 1;1;0;1;0 6 1/3 Complementary1 1;0;1;0;1 7 3/8 Standard 0;1;0;1;0; 1;1;0;1;0; 1;1;0;1;0 8 3/8 Complementary1 1;0;1;0;1; 0;0;1;0;1; 1;0;1;0;1 9 2/5 Standard 1;0;0;0;0; 1;0;1;0;1; 0;0;1;0;1; 1;0;1;0;1; 1;0;1;0;1; 0;0;1;0;1; 1;0;1;0;1; 1;0;1;0;1; 0;0;1;0;1; 1;0;1;0;1; 1;0;1;0;1; 0;0;1;0;1 10 2/5 Complementary1 1;1;0;1;0; 0;1;0;1;0; 1;1;0;1;0; 1;1;0;1;0; 0;1;0;1;0; 1;0;0;0;0; 1;1;0;1;0; 0;1;0;1;0; 1;1;0;1;0; 1;1;0;1;0; 0;1;0;1;0; 1;1;0;1;0 11 3/7 Standard 1;0;0;0;0; 1;1;0;1;0; 0;1;0;1;0; 1;1;0;1;0; 0;1;0;1;0; 1;1;0;1;0 12 3/7 Complementary1 1;0;1;0;1; 0;0;1;0;1; 1;0;1;0;1; 1;0;0;0;0; 1;0;1;0;1; 0;0;1;0;1 13 1/2 Standard 1;1;0;0;0; 1;0;0;1;0 14 1/2 Complementary1 1;0;0;1;0; 1;1;0;0;0 15 1/2 Complementary2 1;0;1;0;0; 1;0;0;0;1 16 3/5 Standard 1;0;0;0;0; 1;0;0;1;0; 1;1;0;0;0 17 3/5 Complementary1 1;0;0;1;0; 1;1;0;0;0; 1;0;0;0;0 18 3/5 Complementary2 1;1;0;0;0; 1;0;0;0;0; 1;0;0;1;0 19 2/3 Standard 1;0;0;0;0; 1;0;0;0;0; 1;0;0;0;0; 1;0;1;0;1 20 2/3 Complementary1 1;0;0;0;0; 1;0;1;0;1; 1;0;0;0;0; 1;0;0;0;0 21 2/3 Complementary2 1;0;0;0;0; 1;0;0;0;0; 1;0;1;0;1; 1;0;0;0;0 22 3/4 Standard 1;0;0;0;0; 1;0;0;0;0; 1;1;0;0;0; 1;0;0;0;0; 1;0;0;0;0; 1;0;0;1;0 23 3/4 Complementary1 1;0;0;0;0; 1;0;0;1;0; 1;0;0;0;0; 1;0;0;0;0; 1;1;0;0;0; 1;0;0;0;0 24 3/4 Complementary2 1;1;0;0;0; 1;0;0;0;0; 1;0;0;0;0; 1;0;0;1;0; 1;0;0;0;0; 1;0;0;0;0 25 6/7 Standard 1;0;0;0;0; 1;0;0;0;0; 1;0;0;0;0; 1;0;0;0;0; 1;0;0;0;0; 1;0;0;0;0; 1;0;0;0;0; 1;0;0;0;0; 1;0;0;0;0; 1;0;0;0;0; 1;0;1;0;0; 1;0;0;0;1 26 6/7 Complementary1 1;0;0;0;0; 1;0;0;0;0; 1;0;0;0;0; 1;0;0;0;0; 1;0;0;0;0; 1;0;0;0;0;
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...