Payload (DVB-RCS2)
Payload is a parameter group within the Frame Definition tab containing the following parameters:
Generation vs. analysis: DVB-RCS2 signal generation fills the Frame PDU (protocol data unit) The data unit exchanged between peer entities of the same protocol layer. On the downward direction, it is the data unit generated for the next lower layer. On the upward direction, it is the data unit received from the previous lower layer. payload with the selected Payload sequence (PN 1) part number, or 2) packet number / Custom / AllOnes / AllZeros) and FEC Forward Error Correction: An encoding technique that allows a limited number of errors in digital stream to be corrected based on knowledge of the encoding scheme used.-encodes it; it does not construct RLE payload adapted PDUs (PPDUs) or ALPDU labels. RLE decapsulation happens only on the analysis side. As a result, the decode-only controls — Type-0 ALPDU Label Size and the "Measured at SDU (post-RLE)" option of Reference Bits Plane — affect only decapsulation/BER Bit Error Ratio - A ratio of the number of errors to data bits received on a digital circuit. of a captured or hand-crafted RLE burst and never change a generated waveform.
– Specifies the payload data sequence.
- Unknown - specifies that the payload is unknown (known modulation).
- AllOnes - specifies that the payload bits are all 1s.
- AllZeros - specifies that the payload bits are all 0s.
- PN9 - specifies a PN9 bit sequence, as specified in CCITT T-REC-O.153.
- PN11 - specifies a PN11 bit sequence, as specified in CCITT T-REC-O.153.
- PN15 - specifies a PN15 bit sequence, as specified in CCITT T-REC-O.151.
- PN20 - specifies a PN20 bit sequence, as specified in CCITT T-REC-O.153.
- PN23 - specifies a PN23 bit sequence, as specified in CCITT T-REC-O.151.
- Custom - specifies a custom sequence. After selecting the Custom, enter or paste the sequence into the field below the Payload parameter. The sequence is an array of integers where each integer is 0 or 1, representing a binary bit.
- Import - Import a custom bit sequence to use as the payload data. The import feature accepts None-, Comma-, Tab- or Newline-delimited data.
- Export - Export the bit sequence in the Custom Payload data field to a .txt file for later reuse. In the drop-down, select the type of delimiter to insert between data bits (None, Comma, Tab or Newline).
Default: Unknown
Choices: Unknown, AllOnes, AllZeros, PN9, PN11, PN15, PN20, PN23, Custom
– Enables LDPC low-density parity check and BCH Broadcast Channel channel decoding for payload. Per-carrier support.
Default: Disabled
– Per-carrier. RLE decapsulation always runs; this control only selects which bit plane feeds the BER reading and the Meas BER Bits / Ref BER Bits traces.
- Measured at Frame PDU (Default) - BER is measured on the raw Frame PDU bits, before RLE decapsulation. Type-0 ALPDU Label Size has no effect in this mode.
- Measured at SDU (post-RLE) - BER is measured on the reassembled SDU bits, after RLE decapsulation. SDU boundaries are located using Type-0 ALPDU Label Size. Only complete (non-fragmented) PPDUs are included; fragmented/reassembled SDUs are skipped.
Default: Measured at Frame PDU
– Enables payload Bit Error Rate calculation. Per-carrier support. When enabled, the payload data is included in Bit Errors, Bit Count and BER metrics. See Frame Summary, Carrier Summary and Syms/Errs for more information.
BER calculations are supported if the payload sequence is either AllOnes, AllZeros, a PN type or a custom bit sequence.
Default: Disabled
See Also
