hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
ec98b24719461dc9223daa92c56ce747 | 103 179 | 1 Scope | The present document specifies the Return Link Encapsulation (RLE) Protocol, which is used to encapsulate and if necessary fragment network layer packets such as for example IP datagrams to allow their transmission over the return link of an interactive satellite network. RLE has been derived from the Generic Stream En... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 2 References | |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 3 Definition of terms, symbols and abbreviations | |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 3.1 Terms | For the purposes of the present document, the following terms apply: Protocol Data Unit (PDU): unit of data produced by a layer of the network stack and given to the next lower layer for transport to the remote peer layer instance NOTE 1: It contains control information from the current layer and may contain user data ... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 3.2 Symbols | Void. ETSI ETSI TS 103 179 V1.2.1 (2023-06) 9 |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACM Adaptive Coding and Modulation ALPDU Addressed Link PDU ARQ Automatic Repeat reQuest bslbf bit string, left bit first CDMA Code Division Multiple Access CoS Class of Service CRC Cyclic Redundancy Check CRDSA Contention Resolution Diversity... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 4 System Aspects | |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 4.0 General | The main use of the RLE protocol is the transport of data on the return link of transparent or regenerative interactive satellite networks and on the direct links between terminals in fully meshed systems (see Figure 4.1). ETSI ETSI TS 103 179 V1.2.1 (2023-06) 10 Figure 4.1: Interactive Satellite Network The terminal t... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 4.1 Protocol Stack | The RLE protocol resides in the Data Link Layer of the communication system (see Figure 4.2). The RLE transmitter gets network layer packets from the network layer (for example IP datagrams) and produces burst or frame payloads that are delivered to the physical layer for transmission. On the receiver side burst or fra... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 4.2 Protocol Tailoring and Configuration | The RLE protocol can be tailored and configured to fit the transmission system requirements as good as possible. This involves two steps: 1) Selection of the capabilities and options to be implemented in the transmission system. This is done based on the system requirements and on the characteristics of the surrounding... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 4.3 Physical Layer Requirements | RLE can operate over physical layers with fixed burst or frame sizes as well as over physical layers with burst or frame sizes varying from burst to burst or frame to frame as they occur in systems like DVB-RCS2 when using adaptive coding and modulation (ETSI EN 301 545-2 [2]). The RLE transmitter dynamically adapts th... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5 RLE Data Format | |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.0 General | The RLE transmitter transforms the network layer PDU into an Addressed Link PDU (ALPDU), sections the ALPDU into one or more Payload-adapted PDUs (PPDUs) as required, and assembles PPDUs into FPDUs that fit into burst payload. On the receiving side the FPDUs from the physical layer are unpacked, the resulting PPDUs are... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.1 Higher Layer SDU | The SDU is constructed from extension headers and higher layer PDUs, for example IP packets according to the rules in IETF RFC 4326 [4]. Each of the two parts, but not both at the same time, is optional. Associated to the SDU is a 16-bit protocol type value which is either the type value of the outermost extension head... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.2 The Addressed Link PDU (ALPDU) | |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.2.0 General | The RLE transmitter shall build ALPDUs that, in addition to the SDU, may include an explicit protocol type indication and an explicit address tag in a similar structure as for GSE (ETSI TS 102 606 [1]). When both fields are included the label field is appended after the protocol type field and before the SDU. Both fiel... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.2.1 Addressed Link PDU Format and Syntax | |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.2.1.0 General | The ALPDU format and syntax are defined in Table 5.1. Table 5.1: Addressed Link PDU Format and Syntax Syntax No. of bits Mnemonic Reserved Information addressed_link_pdu() { if (implied_protocol_type[alpdu_label_type] <> protocol_type) { if (protocol_type_compressed[alpdu_label_type] = 1){ compressed_protocol_type 8 ui... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.2.1.1 compressed_protocol_type Field (optional) | This 8-bit field may be present in the ALPDU as defined by system specification or instructed by system signalling, if not explicitly suppressed by the Protocol Suppressed flag. ETSI ETSI TS 103 179 V1.2.1 (2023-06) 15 If present, the field shall explicitly indicate the protocol type of the SDU by its compressed equiva... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.2.1.2 protocol_type Field (optional) | This 16 bit field is present in the ALPDU if not explicitly indicated to be suppressed by the Protocol Type Suppressed flag (provided by PPDU) or excluded by use of other compressed protocol types than one indicating inclusion of the full size protocol type. The protocol_Type field may explicitly indicate the protocol ... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.2.1.3 alpdu_label_byte Field (optional) | The alpdu_label_byte field is one byte of the ALPDU label. The length of the ALPDU label is indicated in the PPDU by the ALPDU Label Type value. The correspondence between label types and ALPDU label lengths is defined in the system specification or established via signalling. See the specification of the ALPDU Label T... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.2.1.4 sdu_byte Field | This 8 bit field holds one byte from the complete contiguous sequence of SDU bytes. The maximum number of SDU bytes supported depends on the length of the protection field, the label length and the length of the protocol type field. The maximum size of the entire ALPDU is 4 095 bytes. |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.2.1.5 fragmenting_aldpdu | This control parameter is local to the RLE transmitter and reflects whether the ALPDU is mapped into one payload adapted PDU or fragmented into multiple such PDUs. A trailing field for integrity protection is included when the ALPDU is fragmented for adaptation to the next layer, and excluded when the ALPDU is containe... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.2.1.6 sequence_number Field (optional) | The 8 bit sequence_number field may be included at the end of the ALPDU and it is mutually exclusive with use of the alpdu_crc field. ETSI ETSI TS 103 179 V1.2.1 (2023-06) 16 The presence of the sequence number in the ALPDU is either indicated by the value 0 in the use_alpdu_crc field of the corresponding START PPDU if... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.2.1.7 alpdu_crc Field (optional) | This 32 bit field may be included in the ALPDU and it is mutually exclusive with the sequence_number field. It carries the ALPDU CRC. The presence of the ALPDU CRC is indicated by the value 1 in the use_alpdu_crc field of the corresponding START PPDU if this field is present, or is given by the system specification or ... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.2.2 The ALPDU Label | The format and length of the ALPDU label is specified in the system specification of the transmission system. For each transmission context used in the system up to four different label lengths and formats shall be specified for the four different ALPDU label types to be used at the same time. |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.2.3 Mapping the ALPDU to Available Payload | |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.2.3.0 General | The transmitter shall fragment an ALPDU into Payload-adapted PDUs as necessary to fit these PPDUs into transmission frames, aimed for the receivers targeted by the ALPDU. |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.2.3.1 Forwarding the ALPDU in One Payload-adapted PDU | The ALPDU may be transmitted in full in a single PPDU if the payload can hold the PPDU. ETSI ETSI TS 103 179 V1.2.1 (2023-06) 17 |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.2.3.2 Forwarding the ALPDU Using Several Payload-adapted PDUs | The ALPDU may be fragmented and mapped into a sequence of a start PPDU, optionally a number of intermediate PPDUs and an end PPDU finalizing the transport of the ALPDU. These PPDUs shall all be tagged with the same Fragment ID value. The Fragment ID values shall be managed in the transmission context of the transmitter... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.2.3.3 Integrity Protection of a Fragmented ALPDU | A transmitter shall use either the ALPDU CRC method or the ALPDU Sequence Number method for integrity protection at fragmentation of the ALPDU onto several PPDUs. The transmitter shall use a method explicitly allowed by the system specification or signalling. A transmitter shall associate an independent 8 bit wrapping ... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.2.3.4 Multiplexing Payload-adapted PDUs used for Different ALPDUs | A transmitter may multiplex PPDUs associated to different ALPDUs even if all of the PPDUs carry fragments of different ALPDUs, as long as each of the ALPDUs not yet finalized by an end PPDU is associated with a Fragment ID value that is not associated to any other ALPDU in progress from the transmitter. An ALPDU in pro... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.3 The Payload-adapted PDU (PPDU) | |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.3.0 General | The RLE transmitter shall use a Payload-adapted PDU (PPDU) format complying with this clause as specified in the system specification or by signalling. An ALPDU shall be transported by using one or more PPDUs. This set of 4 PPDU types is defined: 1) FULL PPDU: the PPDU type for an unfragmented ALPDU. 2) START PPDU: the... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.3.1 The Payload-adapted PDU Format and Syntax | |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.3.1.0 General | The format and syntax of the PPDU is specified in Table 5.2. Table 5.2: Payload-adapted PDU Format and Syntax Syntax No. of bits Mnemonic Reserved Information payload_adapted_pdu() { start_indicator 1 bslbf end_indicator 1 bslbf ppdu_length 11 uimsbf if (start_indicator = 1 and end_indicator = 1) { alpdu_label_type 2 u... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.3.1.1 start_indicator and end_indicator Fields | These are both 1 bit fields and appear in all PPDUs. A value of "1" in the Start Indicator position indicates that the PPDU contains the initiation of transport of an ALPDU. A value of "0" indicates that the PPDU either contains an intermediate section or finalizes an ALPDU where earlier sections of the ALPDU are conta... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.3.1.2 ppdu_length Field | This 11 bit field is present in all PPDU types. The ppdu_length field contains the length of the PPDU exclusive of the two byte PPDU header and exclusive of the PPDU label. A value of 0 in the PPDU Length field position shall only occur if both the Start Indicator field and the Start Indicator field are 0. This conditi... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.3.1.3 fragment_id Field | This 3 bit field is present in all PPDU types but the FULL PPDU. A receiver shall be able to concurrently receive PPDUs for of up to 8 ALPDUs from each possible transmitter (then all possible Fragment ID values are in use by all possible transmitters). All PPDUs carrying data from the same ALPDU shall use the same frag... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.3.1.4 alpdu_label_type Field | This 2 bit field is present in the START PPDU and in the FULL PPDU. It indicates either the length and contents of the ALPDU label and the implicit protocol type (if any). There are four possible values allowing four different label formats and implicit protocol types. The correspondence between the label type value an... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.3.1.5 protocol_type_suppressed Field | This 1 bit field is present in the START PPDU and in the FULL PPDU. The inclusion of the protocol_type field in the ALPDU is indicated by the Protocol Type Suppressed flag set to "0". The omission of the protocol_type field, and thus the use of an implicit protocol type for the SDU is indicated by the Protocol Type Sup... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.3.1.6 ppdu_label_byte Field (optional) | This one byte field holds one byte of the PPDU label and may be present in any PPDU type. The size and format of the PPDU labels applicable for the PPDUs in a given payload is indicated either explicitly in the optional FPDU header or the size that applies for a given payload is specified in the system specification or... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.3.1.7 large_alpdus Field | This is an internal configuration variable for both the transmitter and receiver which can assume the following two values: 1) Value "0". The maximum ALPDU length is 4 095 bytes. The total_length field of the PPDU is 12 bits long and the use of the alpdu_crc field or the sequence_number field is signalled for each sing... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.3.1.8 use_alpdu_crc Field (optional) | This one-bit field is present in the START PPDU when the large_alpdus field has a value of "0". It indicates whether the ALPDU Sequence Number or the ALPDU CRC is used. If the bit is set, the ALPDU CRC is included. If the bit is cleared, the ALPDU Sequence Number is included. If large_alpdus is set to "1" then the use_... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.3.1.9 total_length Field | The 12 or 13 bit total_length field is present in the START PPDU. It indicates the size of the ALPDU. The field size allows a maximum size of 4 095 or 8 191 bytes. The maximum ALPDU size may be further restricted by the system specification or signalling. ETSI ETSI TS 103 179 V1.2.1 (2023-06) 21 |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.3.1.10 alpdu_byte Field | This field represents one single byte of the ALPDU from the section of contiguous ALPDU bytes contained in the given ALPDU. The ALPDU is specified in clause 5.2. An ALPDU may be fragmented into contiguous sections where the first section is put into one PPDU, the next section into another PPDU transmitted later and so ... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.3.2 The PPDU Label | The PPDU label conveys information attached to the PPDU. Its size, format and syntax is defined in the system specification for each transmission context. When the ppdu_label_length field is not used in the FPDU (see clause 5.4.1.3) only a single size, format and syntax is available per transmission context. If the ppd... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.4 The Frame PDU (FPDU) | |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.4.0 General | The transmitter shall build transmission frame payloads as required by the underlying layer. Different transmission contexts may use different variants of frame payload structure. The configurable options for each transmission context are specified in the system specification and may additionally be modified dynamicall... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.4.1 The FPDU Format and Syntax | |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.4.1.0 General | The transmission FPDU format and syntax for a frame for user traffic shall be in accordance with Table 5.3. Depending on the context this specifies the payload of a transmission burst or a transmission frame. Table 5.3: FPDU Format and Syntax Syntax No. of bits Mnemonic Reserved Information frame_pdu() { if (use_explic... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.4.1.1 use_explicit_payload_header_map Field | The use_explicit_payload_header_map is an internal field for both the transmitter and the receiver for a given transmission context. It has the same value for both the transmitter and the receiver. This value is defined in the system specification or by signalling. The field can have one of the following two values: 1)... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.4.1.2 payload_label_length Field (optional) | This field holds the length of the payload label for this FPDU in bytes. The supported range is 0 to 15 bytes. If this fields is present the ppdu_label_length shall also be present. The presence of both fields is controlled by the use_explicit_payload_header_map flag. If this field is not present the label length defin... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.4.1.3 ppdu_label_length Field (optional) | This field holds the length of the Payload-adapted PDU label in bytes. The supported range is 0 to 15 bytes. If this fields is present the payload_label_length shall also be present. The presence of both fields is controlled by the use_explicit_payload_header_map flag. If this field is not present the label length defi... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.4.1.4 payload_label_byte Field (optional) | One byte of the Payload Label. The payload label size is specified by the payload_label_length field or the system specification and signalling if this fields is not present. The Payload Label can be used to transport information associated to the FPDU. ETSI ETSI TS 103 179 V1.2.1 (2023-06) 23 |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.4.1.5 ppdu_byte (optional) | A sequence of X1(n) of this 8 bit field contains one PPDU with structure and semantics as specified in clause 5.3. The contiguous section of ppdu_bytes holds N1 complete PPDUs. |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.4.1.6 padding_byte (optional) | One byte from a variable size padding field. Any bytes from this position and up to the FPDU end, but not including the optional protection bytes, are padding bytes and shall be set to zero. A single remaining byte following in the payload after the last PPDU is padding. |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.4.1.7 use_frame_protection field | This is an internal field for both the transmitter and the receiver for a given transmission context. It has the same value for both the transmitter and the receiver. This value is defined in the system specification or by signalling. The field can have one of the following two values: 1) Value "0". No frame protection... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.4.1.8 protection_byte (optional) | Contains the error detection bytes for FPDU protection. This field is only present if use_frame_protection is set to "1". The length and kind of error detection is system specific. |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.4.1.9 padding_bit (optional) | One bit out of 0-7 padding bits that all shall be set to zero. This field is present only when the payload size of the frame or burst carrying the FPDU is not a multiple of 8 bits. |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.4.2 The FPDU Payload Label | The FPDU Payload Label conveys information attached to the FPDU. Its size, format and syntax is defined in the system specification for each transmission context. When the payload_label_length field is not used in the FPDU only a single size, format and syntax is available per transmission context. If the payload_label... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 5.4.3 FPDU error protection | The RLE protocol assumes a quasi-error-free physical layer. If the physical layer is not quasi-error-free error an optional error detection mechanism can be used to protect the entire FPDU (excluding the padding bits). The kind of error detection mechanism (CRC, for example) and the length of the information used for e... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 6 RLE Configuration and Tailoring | |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 6.0 General | The present clause lists all the configuration options of the protocol. ETSI ETSI TS 103 179 V1.2.1 (2023-06) 24 |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 6.1 System Specification and Signalling | RLE offers a number of options that can be used to adapt the protocol to the concrete transmission context. A number of options is signalled in-band an thus can be changed on the fly. Other options are more static in nature and their use shall be either fixed by means of system specification or static configuration or ... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 6.2 Higher layer SDU | |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 6.2.1 Maximum SDU size | The maximum size of the ALPDU is 4 095 or 8 191 bytes depending on large_alpdus configuration setting. Depending on the use of compressed and implied protocol types and the length of the ALPDU labels the maximum SDU size is: label proto Max ALPDU RLE Max SDU Max SDU L L L L L − − = ≤ , , , , (1) Where Max SDU L , is th... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 6.3 Addressed Link PDU (ALPDU) | |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 6.3.1 Protocol type table | The protocol type table provides the protocol types and extension header types supported by the transmission system. If protocol type compression is used, the compressed values are also provided. The protocol type configuration includes the following information: 1) 16-bit protocol type. This provides the uncompressed ... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 6.3.2 Label type table | For each of the four label types supported by the alpdu_label_type the following values shall be configured: 1) Length and syntax of the ALPDU label. The length shall be in the range from 0 to 15 bytes. 2) Protocol type compression. This configuration variable can have two values: - Value "0". The protocol type cannot ... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 6.3.3 Extension headers | Extension headers are used to tag arbitrary data on higher layer PDUs or to add additional processing in the different stack layers (FEC, encryption) [4]. Because of the way extension headers work it is necessary to carefully specify the list of extension headers the transmitter may produce and the list of extension he... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 6.3.4 Maximum ALPDU Length | The configuration variable large_alpdus selects the maximum size of the ALPDU to be 4 095 (if the value is "0") or 8 191 bytes (if the value is "1"). |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 6.3.5 Integrity Protection | ALPDUs that are fragmented into more than one PPDU have an integrity protection that uses either a 1-byte sequence number or a 4-byte CRC. Two configuration flags are conceptually attached to the two methods: 1) Allow sequence number. If set to "1" the sequence number method can be used; if set to "0" it cannot be used... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 6.4 Payload-adapted PDU (PPDU) | |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 6.4.0 General | Most of the PPDU configuration options are shared with the ALPDU (label types, integrity protection and others). |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 6.4.1 PPDU Label | For each transmission context the length, format and syntax of the PPDU label shall be defined. The protocol supports a limited kind of flexibility of the PPDU label. Its length may be signalled in the FPDU, but the length is restricted to change from FPDU to FPDU. All PPDUs in a single FPDU shall use the same PPDU lab... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 6.4.2 ALPDU Fragmentation | An implementation may choose to disallow fragmentation for certain types of ALPDUs or label types. This can be necessary for ALPDUs that carry timing information which shall be accessed at layers below RLE, for example. This is a transmitter-only option. ETSI ETSI TS 103 179 V1.2.1 (2023-06) 27 |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 6.5 Frame PDU (FPDU) | |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 6.5.1 Payload Header Map | If there is more than one possible lengths of the PPDU label or more than one possible length of the Payload label and these lengths are chosen by the transmitter on a FPDU by FPDU basis for a given transmission context, then the Payload Header Map field consisting of the payload_label_length field and the ppdu_label_l... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 6.5.2 Payload Label | The possible Payload Label lengths, formats and syntaxes shall be defined. If more than one label length needs to be supported for a given transmission context and that length can change from FPDU to FPDU the Payload Header Map field shall be used to signal the actual label length. The label length is restricted to the... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 6.5.3 Frame Protection | Based on the characteristics of the underlying physical layer of the given transmission context the kind of frame protection shall be chosen. If the physical layer supports quasi-error-free transmission the frame protection may be omitted. Otherwise an appropriate error detection scheme shall be selected (CRC, for exam... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 7 RLE Reassembly Error Check | |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 7.0 General | The present clause describes details of the transmitter and receiver processing of the RLE protocol for the reassembly error check. |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 7.1 Principles | The RLE protocol allows parallel fragmentation and reassembly of several higher layer SDUs from the same sender at the same time. This is achieved by combining the information in the fragment_id header field of the PPDU with either the sequence_number field (if the use_alpdu_crc header field is set to "0"), or with the... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 7.2 Reassembly error check algorithm with sequence number | If the sequence number is applied for reassembly error check, the following rules shall be applied: 1) The transmitter has a variable next_sequence_number for every fragment_id from 0 to 7. When emitting an END PPDU the fragmentation process appends the value of next_sequence_number to the encapsulated higher layer pac... |
ec98b24719461dc9223daa92c56ce747 | 103 179 | 7.3 Reassembly error checking algorithm with CRC-32 | If the CRC-32 is applied for reassembly error check, the following rules shall be applied: 1) When emitting an END PPDU the fragmentation process includes the alpdu_crc field calculated according to clause 5.2.1.7 into the transmitted PPDU. 2) When the receiver receives an END PPDU and the corresponding START PPDU had ... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 1 Scope | The present document specifies the Filecasting user application which permits the non-linear delivery of multimedia content using DAB. Whilst the main focus of the present document is the delivery of audio files over a broadcast network, it is also applicable to other media formats too, such as video files and document... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI EN 300 401: "Radio Broadcasting Systems; Digital Audio Broadcasting (DAB) to mobile, portable and fixed receivers". [2] ETSI EN 301 234: "Digital Audio Broadcasting (DAB); Multimedia Object Transfer (MOT) Protocol". [... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI ES 201 980: "Digital Radio Mondiale (DRM); System Specification". [i.2] ETSI TS 102 818: "Digital Audio Broadcasting (DAB); Digital Radio Mondial... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 3 Definitions and abbreviations | |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in EN 300 401 [1] and the following apply: dynamic broadcast information: Broadcast information relating to the media files and basic presentational information for receivers that do not support the ability to decode the EPG channel dynamic conte... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in EN 300 401 [1] and the following apply: CA Conditional Access DAB Digital Audio Broadcasting EPG Electronic Programme Guide FEC Forward Error Correction HE AAC High Efficiency AAC HTML Hyper Text Markup Language HTTP Hyper Text Transfer Protocol IP In... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 4 Introduction | A Filecasting application consists of two components: 1) Media files: The content itself. 2) Dynamic broadcast information: This provides signalling information that aids a receiver in downloading specific media files, as well as basic presentational information. When broadcast on a DAB multiplex, the media files and d... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5 Filecast channel | |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.1 Transport mechanism | The Filecast channel may be transported in either a packet mode sub-channel with FEC applied or in the PAD of an audio subchannel. MOT in Directory Mode [2] shall be used to transport the Filecast channels. The MOT Directory within the Filecast channel can be compressed. For any carousels containing Filecasting objects... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.2 Filecast MOT carousel | The media files are broadcast as MOT objects within the Filecast channel. They are referenced from the MOT Directory. The MOT Directory is also used as a means of transporting the Dynamic Broadcast Information that is required by the Basic Filecast receiver. The scope of the MOT Directory is set by the service provider... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.2.1 MOT header core | The ContentType and ContentSubType parameters shall be set according to the MOT specification [2]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.