WO2017145790A1 - 受信装置、送信装置、及び、データ処理方法 - Google Patents
受信装置、送信装置、及び、データ処理方法 Download PDFInfo
- Publication number
- WO2017145790A1 WO2017145790A1 PCT/JP2017/004848 JP2017004848W WO2017145790A1 WO 2017145790 A1 WO2017145790 A1 WO 2017145790A1 JP 2017004848 W JP2017004848 W JP 2017004848W WO 2017145790 A1 WO2017145790 A1 WO 2017145790A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- packet
- header
- payload
- alp
- transmission
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0056—Systems characterized by the type of code used
- H04L1/0061—Error detection codes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0078—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location
- H04L1/0083—Formatting with frames or packets; Protocol or part of protocol for error control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
Definitions
- the present technology relates to a receiving device, a transmitting device, and a data processing method, and more particularly, to a receiving device, a transmitting device, and a data processing method that can prevent packets from being discarded unnecessarily.
- ATSC Advanced Television Systems Committee
- the present technology has been made in view of such a situation, and is to be able to prevent packets from being discarded unnecessarily.
- the receiving device is a plurality of transmission packets arranged in a payload of a baseband packet after demodulation, which is an IP including a header including an error detection code and a UDP (User Datagram Protocol) packet Internet Protocol)
- a processing unit configured to process the transmission packet including a payload in which the packet is arranged, the processing unit performs an error detection process using the error detection code included in the header of the transmission packet It is a receiver.
- the receiving device may be an independent device or an internal block that constitutes one device.
- a data processing method is a data processing method corresponding to the receiving device according to the first aspect of the present technology described above.
- a plurality of transmission packets are arranged in a payload of a baseband packet after demodulation, and include a header including an error detection code and a UDP packet.
- the transmission packet including the payload in which the IP packet is arranged is processed, and an error detection process is performed using the error detection code included in the header of the transmission packet.
- the transmission device is a transmission packet disposed in the payload of a baseband packet before modulation, and includes a header including an error detection code and a payload in which an IP packet including a UDP packet is disposed.
- the processing unit includes a processing unit configured to generate the transmission packet, and the processing unit is a transmitting device that arranges a plurality of the transmission packets in a payload of the baseband packet.
- the transmission device of the second aspect of the present technology may be an independent device or an internal block that constitutes one device. Further, a data processing method according to a second aspect of the present technology is a data processing method corresponding to the transmission device according to the second aspect of the present technology described above.
- a transmission packet is disposed in the payload of a baseband packet before modulation, and includes a header including an error detection code and an IP including a UDP packet.
- the transmission packet including the payload in which the packet is arranged is generated, and a plurality of the transmission packets are arranged in the payload of the baseband packet.
- the receiving device is a baseband packet after demodulation, and includes a plurality of transmission packets including a header including an error detection code and a payload in which an IP packet including a UDP packet is arranged.
- a processing unit configured to process the baseband packet including the arranged payload, wherein the processing unit performs the error detection processing using the error detection code included in the header of the baseband packet is there.
- the receiving device of the third aspect of the present technology may be an independent device or an internal block that constitutes one device. Further, a data processing method according to a third aspect of the present technology is a data processing method corresponding to the receiving device according to the third aspect of the present technology described above.
- the baseband packet after demodulation includes a header including an error detection code and a payload in which an IP packet including a UDP packet is arranged.
- the baseband packet composed of a payload in which a plurality of transport packets are arranged is processed, and an error detection process is performed using the error detection code included in the header of the baseband packet.
- the transmission device is a transmission packet disposed in a payload of a baseband packet before modulation, the transmission packet including a payload in which an IP packet including a UDP packet is disposed.
- the transmission unit may include a processing unit that generates an error detection code in the header of the baseband packet, and the plurality of transmission packets in the payload of the baseband packet.
- the transmission device of the fourth aspect of the present technology may be an independent device or an internal block that constitutes one device. Further, a data processing method according to a fourth aspect of the present technology is a data processing method corresponding to the transmission device according to the fourth aspect of the present technology described above.
- the transmission packet is placed in the payload of the baseband packet before modulation, and includes the payload in which the IP packet including the UDP packet is placed.
- the transmission packet configured is generated, an error detection code is placed in the header of the baseband packet, and a plurality of the transmission packets are placed in the payload of the baseband packet.
- FIG. 1 is a diagram illustrating a configuration of an embodiment of a transmission system to which the present technology is applied. It is a figure which shows the structural example of a transmitter. It is a figure which shows the structural example of a receiver. It is a figure which shows the correlation of the packet used by this technique. It is a figure which shows the structure of BB header added to BB packet. It is a figure which shows the example of an optional field flag. It is a figure which shows the example of the syntax of the ALP header of an ALP packet. It is a figure which shows the example of the syntax of additional_header_for_single_packet ().
- FIG. 1 is a diagram showing the configuration of an embodiment of a transmission system to which the present technology is applied.
- a system is a system in which a plurality of devices are logically gathered.
- the transmission system 1 includes a transmitting device 10 and a receiving device 20.
- data transmission conforming to the digital broadcast standard such as ATSC 3.0 is performed.
- IP including UDP / IP packets, that is, UDP (User Datagram Protocol) packets, not TS (Transport Stream) packets
- UDP User Datagram Protocol
- TS Transport Stream
- the transmitter 10 transmits the content via the transmission path 30.
- the transmitting apparatus 10 transmits a broadcast stream including signaling and video, audio, and the like that constitute content such as a broadcast program and the like via a transmission path 30 as a broadcast wave.
- the receiving device 20 receives and outputs the content transmitted from the transmitting device 10 via the transmission path 30.
- the receiving device 20 receives a broadcast wave from the transmitting device 10, acquires from the broadcast stream video and audio (components of the content) and signaling that constitute the content, and generates video and audio of content such as a broadcast program. To play.
- the transmitting device 10 transmits Broadcast waves to be distributed can be received simultaneously by a plurality of receiving devices 20 via the transmission path 30.
- a plurality of transmission devices 10 can also be provided.
- Each of the plurality of transmitting devices 10 transmits a broadcast wave including a broadcast stream as a separate channel, for example, in a separate frequency band, and in the receiving device 20, from among the respective channels of the plurality of transmitting devices 10 , A channel to receive the broadcast stream can be selected.
- the transmission path 30 is satellite broadcasting using, for example, a broadcasting satellite (BS: Broadcasting Satellite) or a communication satellite (CS: Communications Satellite) in addition to terrestrial waves (terrestrial broadcasting).
- BS Broadcasting Satellite
- CS Communications Satellite
- CATV cable broadcasting
- FIG. 2 is a diagram showing a configuration example of the transmission device 10 of FIG.
- the transmitting apparatus 10 includes an AV encoder 101, a FLUTE encoder 102, a UDP / IP packetizer 103, an ALP packetizer 104, a BB packetizer 105, a scrambler 106, a BCH encoder 107, an LDPC encoder 108, a parity interleaver 109, column twist.
- the AV encoder 101 encodes (components of) video and audio data according to a predetermined coding scheme, and supplies the encoded data to the FLUTE encoder 102.
- the FLUTE encoder 102 processes (encodes) the data from the AV encoder 101 to generate data corresponding to a File Delivery over Unidirectional Transport (FLUTE) format, and supplies the data to the UDP / IP packetizer 103.
- FLUTE File Delivery over Unidirectional Transport
- the UDP / IP packetizer 103 processes the data from the FLUTE encoder 102 to generate an IP packet (UDP / IP packet) including a UDP packet, and supplies the IP packet to the ALP packetizer 104.
- the ALP packetizer 104 processes UDP / IP packets from the UDP / IP packetizer 103 to generate ALP (ATSC Link layer Protocol) packets and supplies them to the BB packetizer 105.
- ALP ATSC Link layer Protocol
- the BB packetizer 105 processes the ALP packet from the ALP packetizer 104 to generate a BB (Base Band) packet and supplies it to the scrambler 106.
- the scrambler 106 scrambles the data (BB packet) from the BB packetizer 105, and supplies the resultant data to the BCH encoder 107.
- the BCH encoder 107 performs BCH (Bose-Chaudhuri-Hocquenghem) encoding on the data from the scrambler 106, and supplies the resulting data to the LDPC encoder 108.
- the LDPC encoder 108 performs low density parity check (LDPC) coding on the data from the BCH encoder 107, and supplies the resulting data to the parity interleaver 109.
- BCH Bit-Chaudhuri-Hocquenghem
- the parity interleaver 109 performs parity interleaving on the data from the LDPC encoder 108, and supplies the data after the parity interleaving to the column twist interleaver 110.
- the column twist interleaver 110 performs column twist interleaving on the data from the parity interleaver 109, and supplies the data after the column twist interleaving to the data mapper 111.
- the data mapper 111 maps the data from the column twist interleaver 110 to signal points representing one symbol of orthogonal modulation in units of one or more code bits (symbols) of the data (LDPC code). Orthogonal modulation (multi-level modulation) is performed.
- the data obtained by the processing by the data mapper 111 is supplied to the cell interleaver 113 via the CQ delay unit 112.
- the cell interleaver 113 performs cell interleaving on the data from the CQ delay unit 112, and supplies the data after cell interleaving to the time interleaver 114.
- the time interleaver 114 performs time interleaving on the data from the cell interleaver 113, and supplies the data after time interleaving to the frame mapper 115.
- the frame mapper 115 processes the data from the time interleaver 114 regarding frames (physical layer frames), and supplies the resulting data to the frequency interleaver 116.
- the frequency interleaver 116 performs frequency interleaving on the data from the frame mapper 115, and supplies the data after frequency interleaving to the OFDM transmission unit 117.
- the OFDM transmitting unit 117 processes the data from the frequency interleaver 116 to generate an orthogonal frequency division multiplexing (OFDM) signal and supplies the signal to the RF output unit 118.
- the RF output unit 118 is connected to an antenna (not shown), and transmits the OFDM signal from the OFDM transmission unit 117 via the transmission path 30 as an RF (Radio Frequency) signal.
- the transmitter 10 is configured as described above.
- FIG. 3 is a diagram showing a configuration example of the receiving device 20 of FIG.
- the receiving apparatus 20 includes an RF input unit 201, an OFDM receiving unit 202, a frequency deinterleaver 203, a frame demapper 204, a time deinterleaver 205, a cell deinterleaver 206, a CQ delay unit 207, and a data demapper.
- column twist deinterleaver 209 parity deinterleaver 210, LDPC decoder 211, BCH decoder 212, descrambler 213, BB depacketizer 214, ALP depacketizer 215, UDP / IP depacketizer 216, FLUTE decoder 217, and AV decoder 218 Configured
- the RF input unit 201 is connected to an antenna (not shown), receives an RF signal transmitted from the transmission apparatus 10 via the transmission path 30, and supplies the signal as an OFDM signal to the OFDM reception unit 202.
- the OFDM receiving unit 202 processes the OFDM signal from the RF input unit 201 and supplies data obtained thereby to the frequency deinterleaver 203.
- the frequency deinterleaver 203 frequency deinterleaves the data from the OFDM reception unit 202, and supplies the data after frequency deinterleaving to the frame demapper 204.
- the frame demapper 204 performs processing on a frame (physical layer frame) on the data from the frequency deinterleaver 203, and supplies the resulting data to the time deinterleaver 205.
- the time deinterleaver 205 subjects the data from the frame demapper 204 to time deinterleaving, and supplies the data after time deinterleaving to the cell deinterleaver 206.
- the cell deinterleaver 206 performs cell deinterleaving on the data from the time deinterleaver 205, and supplies the data after cell deinterleaving to the data demapper 208 via the CQ delay unit 207.
- the data demapper 208 demaps the data (data on the constellation) from the CQ delay unit 207 based on the arrangement (constellation) of the signal points determined by the orthogonal modulation performed on the transmitting device 10 side.
- Point constellation decoding is performed to perform orthogonal demodulation, and the resulting data (LDPC code) is supplied to the column twist deinterleaver 209.
- the column twist deinterleaver 209 performs column twist deinterleaving on the data from the data demapper 208, and supplies the data after the column twist deinterleaving to the parity deinterleaver 210.
- the parity deinterleaver 210 performs parity deinterleave on the data from the column twist deinterleaver 209, and supplies the data after the parity deinterleave to the LDPC decoder 211.
- the LDPC decoder 211 performs LDPC decoding on the data from the parity deinterleaver 210, and supplies the resulting data to the BCH decoder 212.
- the BCH decoder 212 BCH decodes the data from the LDPC decoder 211, and supplies the resulting data to the descrambler 213.
- the descrambler 213 descrambles the data from the BCH decoder 212, and supplies the resulting data to the BB depacketizer 214.
- the BB depacketizer 214 extracts and processes BB packets from the data from the descrambler 213, and supplies the resulting data to the ALP depacketizer 215. Further, error correction information is input to the BB depacketizer 214 from the LDPC decoder 211 or the BCH decoder 212. This error correction information is information indicating that an error has occurred in the processing of LDPC decoding or BCH decoding, and in the BB depacketizer 214, data that can not be corrected by LDPC decoding or BCH decoding by the error correction information. It can recognize that exists.
- the ALP depacketizer 215 extracts and processes ALP packets from the data from the BB depacketizer 214 and supplies the resulting data to the UDP / IP depacketizer 216.
- the UDP / IP depacketizer 216 extracts and processes UDP / IP packets from the data from the ALP depacketizer 215 and supplies the resulting data to the FLUTE decoder 217.
- the FLUTE decoder 217 processes (decodes) data (data corresponding to the FLUTE format) from the UDP / IP depacketizer 216 and supplies the resultant data to the AV decoder 218.
- the AV decoder 218 decodes the data from the FLUTE decoder 217 according to a predetermined decoding scheme, and outputs (the component of) video and audio data obtained as a result.
- the receiving device 20 is configured as described above.
- FIG. 4 is a diagram showing the correlation of packets used in the present technology.
- the BB (Base Band) packet is a baseband layer 1 packet.
- An ALP (ATSC Link layer Protocol) packet is a packet (transmission packet) of layer 2 which is an upper layer of layer 1.
- An IP (Internet Protocol) packet is a packet of layer 3 which is an upper layer of layer 2.
- the IP packet includes a UDP (User Datagram Protocol) packet.
- the BB packet is composed of a BB header and a payload (BB packet payload).
- One or more ALP packets are arranged in the payload of the BB packet.
- the BB header contains information such as packet length and pointer. This pointer represents the position of the first ALP packet placed in the payload of the BB packet. In the following description, this pointer is referred to as a leading ALP pointer.
- the maximum size of the BB packet is 8196 bytes.
- An ALP packet is composed of an ALP header (ALP Header) and a payload (ALP payload).
- ALP header contains information such as the packet length.
- the ALP packet has a variable length, and its maximum size is 65536 bytes.
- one or more ALP packets arranged in the payload of the BB packet can be extracted by using the head ALP pointer of the BB header and the packet length of the ALP header (packet length of the ALP packet). That is, if the position of a given ALP packet is specified using a leading ALP pointer in a given BB packet, the packet length of the ALP header is assumed even if the ALP packet is placed across the next BB packet. By using this, the position of the next ALP packet can be identified.
- FIG. 4 illustrates the case where three ALP packets are arranged for three BB packets
- some BB packets include ALP packets arranged across a plurality of BB packets. Existing.
- the second ALP packet is placed across the first to third BB packets.
- the position of the first (head) ALP packet is specified by the head ALP pointer of the BB header of the first (head) BB packet, so that the payload of the first (head) BB packet is determined. It is extracted.
- the third ALP packet is extracted from the payload of the third BB packet by specifying its position by the top ALP pointer of the BB header of the third BB packet.
- the position according to the packet length is specified from the top ALP pointer (of the BB header of the first BB packet) by the packet length of the ALP header of the first and second ALP packets It is extracted from the payloads of the first to third BB packets.
- the value of the beginning ALP pointer of the BB header of the second BB packet is “0”.
- ALP_packet_header which is a basic header (ALP Base Hdr) as the ALP header of the ALP packet
- ALP_header which is an additional header
- ALP Add Hdr an additional header
- An extension header which is ALP Opt Hdr
- IP packet is composed of an IP header (IP Header) and a data part (Data).
- IP Header IP header
- Data data part
- a UDP packet is placed in the data portion of the IP packet.
- the IP header of the IP packet is: Version (Ver), Header Length (Head Len), Service, Total Length (Total Len), ID, Flag, Flag offset, TTL (Time To Live), Protocol, Checksum, Source IP address ( Src Add), Destination IP address (Dest Add), and Option.
- the maximum size of the IP packet is 65536 bytes.
- the UDP packet is composed of a UDP header (UDP Header) and a data part (Data). In the data portion of the UDP packet, components such as video and audio and data of signaling are arranged.
- the UDP header of the UDP packet has Source port number (Src Port), Destination port number (Dest Port), Length, and Checksum.
- the maximum size of the UDP packet is 65,507 bytes.
- FIG. 5 is a diagram showing the structure of the BB header added to the BB packet.
- the BB packet is composed of a BB header and a payload.
- BB header in addition to a 1- or 2-byte base field (Base Field), an optional field (Optional Field) and an extension field (Extension Field) can be arranged.
- Base Field base field
- Optional Field optional field
- Extension Field Extension Field
- a 7-bit pointer (Pointer (LSB)) is arranged.
- This pointer is the top ALP pointer described above, and indicates the position of the top ALP packet placed in the payload of the BB packet. For example, when data of an ALP packet placed last in a certain BB packet is placed across the next BB packet, the position of the first ALP packet placed in the next BB packet is set as the first ALP pointer. It can be set.
- a 6-bit pointer (Pointer (MSB))
- an optional 2-bit flag besides a 7-bit pointer (OPTI: OPTIONAL)
- the optional flag is information indicating whether or not to extend the header by arranging an optional field and an extension field.
- the optional flag when extension of the optional field and the extension field is not performed, "00" is set in the optional flag.
- the optional flag is set to “01”, which is a short extension mode.
- the optional flag is set to "10" or "11”, and Long Extension Mode or Mixed Extension Mode It becomes.
- extension_TYPE 3-bit extension type
- EXT_TYPE 3-bit extension type
- EXT_TYPE 5-bit extension data length
- Extension 0 to 31 bytes of extension data
- extension_TYPE extension type
- EXT_LEN 5-bit extension data length
- MSB 8-bit extension data length
- Extension Extension
- FIG. 7 is a diagram showing an example of the syntax of the ALP header.
- the 3-bit packet_type indicates the packet type of the ALP packet.
- One-bit payload_configuration is set to "0" or "1" according to the information set in the ALP header.
- header_mode When “0" is specified as payload_configuration, header_mode and length are arranged in the ALP header.
- One-bit header_mode indicates a header mode.
- the 11-bit length indicates the packet length of the ALP packet (ALP packet length).
- additional_header_for_single_packet is placed in the ALP header as an additional header.
- the detailed structure of this additional_header_for_single_packet () will be described later with reference to FIG.
- segmentation_concatenation length is placed in the ALP header. “1” is set to “0” or “1” according to the type of the additional header in 1 bit of segmentation_concatenation.
- the 11-bit length indicates the packet length of the ALP packet (ALP packet length).
- additional_header_for_segmentation is placed in the ALP header as an additional header.
- the detailed structure of this additional_header_for_segmentation () will be described later with reference to FIG.
- additional_header_for_concatenation is placed as an additional header in the ALP header.
- the detailed structure of this additional_header_for_concatenation () will be described later with reference to FIG.
- uimsbf unsigned integer most significant bit first
- bslbf bit string, left bit first
- FIG. 8 is a diagram illustrating an example of the syntax of additional_header_for_single_packet () of FIG. 7.
- the 5-bit length_MSB indicates the packet length of the most significant bit (MSB: Most Significant Bit).
- One-bit SIF indicates a flag indicating whether a substream ID (sub_stream_identification) exists. If there is a substream ID, SIF is set to "1".
- sub_stream_identification is placed in the ALP header. The detailed structure of this sub_stream_identification () will be described later with reference to FIG.
- header_extension () is arranged in the ALP header as an extension header. The detailed structure of this header_extension () will be described later with reference to FIG.
- FIG. 9 is a diagram illustrating an example of the syntax of additional_header_for_segmentation () in FIG. 7.
- segment_sequence_number indicates a segment sequence number.
- last_segment_indicator indicates an indicator of the last segment.
- SIF indicates a flag indicating whether a substream ID exists. If "1" is specified as SIF, sub_stream_identification () is placed in the ALP header. Moreover, HEF shows the flag of whether the extension header exists. If “1" is specified as HEF, header_extension () is placed in the ALP header. The detailed structures of sub_stream_identification () and header_extension () will be described later with reference to FIGS. 11 and 12.
- FIG. 10 is a diagram illustrating an example of the syntax of additional_header_for_concatenation () of FIG. 7.
- the 5-bit length_MSB indicates the packet length of the most significant bit (MSB).
- the 3-bit count indicates a count value. In accordance with this count value, 12 bits of component_length are arranged.
- component_length indicates the component length.
- the 1-bit HEF indicates a flag indicating whether an extension header is present. If "1" is specified as HEF, header_extension () is placed in the ALP header. The detailed structure of header_extension () will be described later with reference to FIG.
- FIG. 11 is a diagram illustrating an example of a syntax of sub_stream_identification () in FIGS. 8 and 9.
- the 8-bit SID indicates a substream ID.
- FIG. 12 is a diagram illustrating an example of the syntax of header_extension () in FIGS. 8 to 10.
- the 8-bit extension_type indicates an extension type.
- the 8-bit extension_length indicates the extension data length. In the extension loop according to the extension data length, 8-bit extension_byte is arranged. As this extension_byte, data of the extension type specified by the extension_type is arranged according to the extension data length specified by the extension_length.
- extension type specified by the extension_type of the extension header (header_extension) of the ALP header is distinguished from the extension type (EXT_TYPE) of the optional field (Optional Field) of the BB header shown in FIG. For convenience, it is called "extended data type”.
- one or more ALP packets placed in the payload of the BB packet have the header ALP pointer of the BB header and the packet length of the ALP header (packet of ALP packet By using long), it is read from the BB packet.
- the BB depacketizer 214 can recognize that an error that can not be corrected by LDPC or BCH has occurred using this error correction information, only information indicating the presence or absence of an error is notified. I can not recognize if an error has occurred.
- FIG. 13 is a diagram for explaining the current packet processing.
- an error that can not be corrected by LDPC or BCH occurs in the payload of the first ALP packet among a plurality of ALP packets arranged in the payload of the BB packet.
- the BB depacketizer 214 can recognize that an error that can not be corrected by LDPC or BCH is occurring according to the error correction information, the error occurred because the error occurrence position can not be identified. Discard not only the first ALP packet but also all ALP packets placed in the payload of the BB packet.
- the current packet processing is executed by the BB depacketizer 214 to the UDP / IP depacketizer 216 (FIG. 3) of the reception apparatus 20 (FIG. 1) or the like.
- step S511 the BB depacketizer 214 acquires the next processing target BB packet.
- step S512 the BB depacketizer 214 applies the BB packet (a plurality of ALP packets arranged in the payload) acquired in the process of step S511 based on the error correction information from the LDPC decoder 211 or the BCH decoder 212. It is determined whether an error (LDPC / BCH error) that can not be corrected by the LDPC decoder 211 or the BCH decoder 212 has occurred.
- step S512 If it is determined in step S512 that an LDPC / BCH error has occurred in the processing-targeted BB packet, the process returns to step S511, and the next processing-targeted BB packet is acquired (S511).
- the BB depacketizer 214 when an error that can not be corrected by the LDPC decoder 211 or BCH decoder 212 occurs, all ALP packets placed in the payload of the BB packet in which the LDPC / BCH error has occurred. To get the next BB packet to be processed.
- step S512 determines whether the ALP packet placed in the payload of the BB packet to be processed is in the middle of the ALP packet.
- step S513 If it is determined in step S513 that the packet is not in the middle of the ALP packet, the process proceeds to step S514.
- step S514 the BB depacketizer 214 acquires the BB header of the BB packet to be processed. Also, in step S515, the BB depacketizer 214 acquires the leading ALP pointer included in the BB header acquired in the process of step S514.
- step S516 the BB depacketizer 214 acquires the ALP header of the processing target ALP packet (head ALP packet) based on the position specified by the top ALP pointer acquired in the process of step S515.
- step S517 the BB depacketizer 214 acquires the ALP packet length (packet length of ALP packet) included in the ALP header acquired in the process of step S516.
- step S518 the BB depacketizer 214 obtains the payload of the ALP packet to be processed.
- the process proceeds to step S519.
- step S519 it is determined whether the processing-targeted BB packet has ended. If it is determined in step S519 that the BB packet to be processed has not ended, the process proceeds to step S520.
- step S520 it is determined whether the ALP packet to be processed has ended. If it is determined in step S520 that the ALP packet to be processed has not ended, the process returns to step S518, and the subsequent processing is repeated. That is, the payload of the processing target ALP packet is acquired until the processing target BB packet ends ("YES" in S519) or the processing target ALP packet ends ("YES" in S520) ( S518).
- step S520 If it is determined in step S520 that the ALP packet to be processed has ended, the process proceeds to step S521.
- step S521 UDP / IP processing is performed.
- step S521 ends, the process proceeds to step S516.
- the next ALP packet to be processed (ALP header or payload) is processed according to the position specified by the ALP packet length (packet length of ALP packet) acquired in the process of step S517.
- a process similar to the process (the process after S516) on the acquired ALP packet to be processed is performed.
- step S519 If it is determined in step S519 that the BB packet to be processed has ended, the process proceeds to step S511. Then, the next processing target BB packet is acquired, and the same processing as the processing (processing after S511) on the processing target BB packet described above is performed.
- step S513 If it is determined in step S513 that the ALP packet is in the middle, the process proceeds to step S522.
- step S522 the BB depacketizer 214 blanks the BB header of the BB packet to be processed.
- step S528 the process proceeds to step S518, and the subsequent processes are performed.
- the BB to be processed is All ALP packets placed in the packet payload are discarded, and the next BB packet to be processed is acquired (S511). That is, when an error that can not be corrected by LDPC or BCH occurs in a specific ALP packet, not only the ALP packet in which the error occurs but all the ALP packets in the BB packet to be processed are extracted. It will not be possible (all ALP packets will be discarded).
- error detection code can be placed in the BB header of the BB packet or the ALP header of the ALP packet, so that the error correction by the LDPC or BCH can not be performed on the ALP packet in the BB packet. Even when an error occurs, the position where the error occurs can be detected to prevent the ALP packet in the target BB packet from being discarded unnecessarily.
- FIG. 15 is a diagram showing an example of syntax of an ALP packet.
- the structure of the ALP header described below is an extension of the structure of the ALP header shown in FIGS. 7 to 12 described above.
- an ALP packet is composed of an ALP header and a payload.
- the ALP header includes an ALP packet header (ALP_packet_header), an additional header (additional_header), and an extension header (header_extension).
- the ALP packet header has packet_type, PC (payload_configuration), HM (header_mode), and length. However, as described above, by specifying “0” as the 1-bit payload_configuration, HM (header_mode) and length are arranged in the ALP packet header.
- the 3-bit packet_type indicates the packet type of the ALP packet.
- this packet type "000" is fixedly specified.
- FIG. 16 shows an example of the packet type.
- the packet is an IPv4 (Internet Protocol version 4) packet.
- 1-bit HM header_mode indicates a header mode. As this header mode, "1" is fixedly specified. As described above, by specifying “1” as the header_mode, an additional header (additional_header) is placed in the ALP header.
- the 11-bit length indicates the packet length of the ALP packet (ALP packet length).
- the additional header has length_MSB, SIF (Substream Identification Flag), and HEF (Header Extension Flag).
- the 5-bit length_MSB indicates the packet length of MSB (Most Significant Bit).
- One-bit SIF indicates a flag indicating whether a substream ID (sub_stream_identification) exists. If there is a substream ID, SIF is set to "1".
- data of the extension data type designated by extension_type can be arranged according to the extension data length designated by extension_length.
- extension_type one or more extension data types (extension_type) can be specified by extending the 8-bit num_extension_type so that the number of extension data types can be specified.
- Data (DATA [i] [j]) according to the extension data length (extension_length [i]) can be arranged for each [i]).
- FIG. 18 shows an example of the extended data type.
- extension data type extension_type
- data (DATA) in a loop according to the extension data length extension_length
- CRC Cyclic Redundancy Check: Cyclic Redundancy Check
- the data structure of CRC_DATA of FIG. 19 can be arranged as data (DATA) in a loop corresponding to the extended data length of FIG. In FIG. 19, mode and CRC are arranged in CRC_DATA.
- the 8-bit mode indicates a CRC mode (hereinafter referred to as a CRC mode).
- a CRC mode of "0" represents CRC-8.
- a CRC mode of "1" represents CRC-16.
- CRC CRC data corresponding to the CRC mode specified by mode is arranged.
- CRC-8 and CRC-16 due to differences in polynomial, here, for example, CRC-8 defined by CCITT (Comite Consultatif International Circuitique et Telephonique: International Brass and Telephone Consultative Committee) -CCITT (X 8 + X 7 + X 3 + X 2 + 1) or CRC-16-CCITT (X 16 + X 12 + X 5 + 1) can be used.
- CRC-8s other than CRC-8-CCITT
- CRC-16s other than CRC-16-CCITT
- CRC-32 and CRC-64 may of course be used, for example, other CRCs such as CRC-32 and CRC-64.
- the CRC is an example of an error detection code, and another error detection code may be used.
- 0xff When “0xff” is specified as the extension data type in FIG. 18, it indicates that private user data (Private User Data) is arranged in data (DATA) in a loop according to the extension data length. ing. As this private user data, arbitrary data such as data to be notified between devices can be arranged, for example. Further, in FIG. 18, the extended data type of “0x01” to “0xfe” is set as a region for future extension (Reserved).
- the CRC mode such as CRC-8 and CRC-16 is specified by CRC_DATA of FIG. 19, but the CRC corresponding to the CRC mode is It may be specified by the extended data type.
- FIG. 20 shows an example of an extended data type that can specify a CRC according to the CRC mode.
- extension data type extension_type
- data of CRC-8 is included in the data (DATA) in the loop according to the extension data length (extension_length) of FIG. It represents that it is arranged.
- extension data length extension_length
- an error detection code for example, CRC-8 or CRC-16
- the depacketizer 2114 performs error detection processing using the error detection code included in the ALP header, and the payload of the BB packet according to the detected position (the position where an error can not be corrected by LDPC or BCH). Can be processed ALP packets placed in
- Second method place an error detection code in the BB header
- FIG. 21 is a diagram illustrating an example of a data structure in the case of arranging a CRC in the BB header of the BB packet.
- the structure of the BB header in FIG. 21 corresponds to the structure of the BB header shown in FIG. 5 described above, and the description of the portions where the description is repeated will be omitted as appropriate.
- the BB packet is composed of a BB header and a payload.
- BB header in addition to a base field (Base Field), an optional field (Optional Field) and an extension field (Extension Field) can be arranged.
- Base Field Base Field
- Optional Field optional field
- Extension Field Extension Field
- a 2-bit optional flag (OPTI: OPTIONAL) is placed.
- OPTIONAL optional flag
- optional fields and extension fields are expanded.
- EXT_TYPE 3-bit extension type
- extension type the type of extension field is specified. For example, when “001" is specified as the extension type, it indicates that data of CRC-8 is placed in the extension field. When “010” is specified as the extension type, it indicates that data of CRC-16 is placed in the extension field.
- CRC-8 and CRC-16 e.g., CRC-8-CCITT (X 8 + X 7 + X 3 + X 2 + 1) or, CRC-16 -CCITT (X 16 + X 12 + X 5 + 1) can be used.
- CRC-8s other than CRC-8-CCITT, and other CRC-16s other than CRC-16-CCITT may of course be used, for example, other CRCs such as CRC-32 and CRC-64.
- the CRC is an example of an error detection code, and another error detection code may be used.
- extension types of “011” to “110” are considered as areas for future extension.
- “000” is specified as the extension type, it means that a counter is arranged, and when "111" is specified, it means that padding is performed.
- an error detection code for example, CRC-8 or CRC-16
- BB header extension field of the BB packet.
- the depacketizer 214) can perform error detection processing using the error detection code contained in the BB header.
- either the first method or the second method may be employed, or both methods may be employed simultaneously.
- an error detection code is arranged for each of the ALP header of the ALP packet and the BB header of the BB packet.
- the processing content for the ALP packet changes according to the detected position of the error (the position where the error can not be corrected by LDPC or BCH), so the detected position of the error is the ALP packet below.
- the detected position of the error is the ALP packet below.
- FIG. 22 is a diagram for explaining packet processing of the present technology in the case where the error detection position is the payload of the ALP packet.
- the error detection processing using an error detection code (for example, CRC-8 or CRC-16) included in the ALP header of the ALP packet is placed in the payload of the BB packet to be processed. It is detected that an error that can not be corrected by LDPC or BCH has occurred in the payload of the leading ALP packet among a plurality of ALP packets.
- an error detection code for example, CRC-8 or CRC-16
- the error detection processing using the error detection code of the ALP header not only recognizes that an error that can not be corrected by LDPC or BCH is occurring, but also detects the position where the error has occurred. Therefore, by identifying (the payload of) an ALP packet in which an error has occurred and making sure that the variable-length chain of ALP packets is not interrupted in the payload of the BB packet to be processed, an error occurs. ALP packets are not discarded.
- FIG. 23 is a diagram for explaining packet processing of the present technology in the case where an error detected position is an ALP header of an ALP packet.
- the error detection processing using an error detection code (for example, CRC-8 or CRC-16) included in the ALP header of the ALP packet is placed in the payload of the BB packet to be processed.
- an error detection code for example, CRC-8 or CRC-16
- the packet processing of the present technology in FIG. 23 it is detected (recognized) that an error has occurred in the ALP header of the second ALP packet, so the information in the ALP header is not necessarily correct. Although the ALP packet after the second ALP packet is discarded, the first ALP packet is not discarded because the first ALP packet does not have an error.
- the error detection processing using the error detection code of the ALP header not only recognizes that an error that can not be corrected by LDPC or BCH is occurring, but also detects the position where the error has occurred. Therefore, identify the ALP packet (the ALP header) in which the error has occurred, and ensure that the error-free ALP packet is not discarded as much as possible in the payload of the BB packet to be processed. There is.
- the ALP header of the ALP packet placed in the payload of the BB packet is included in the payload of the BB packet to be processed.
- the ALP packet can be extracted continuously until the ALP packet immediately before the containing ALP packet.
- step S101 packet processing is performed on data of content such as a broadcast program.
- processing of generating UDP / IP packets, ALP packets, and BB packets is performed by the UDP / IP packetizer 103, the ALP packetizer 104, and the BB packetizer 105.
- the ALP header of the ALP packet generated in the process of step S101 is an error such as CRC-8 or CRC-16, for example.
- a detection code is placed.
- an error detection code (DATA) corresponding to the extension data type (extension_type) is arranged in the extension header (header_extension) of the ALP header.
- the BB header of the BB packet generated in the process of step S101 is an error such as CRC-8 or CRC-16, for example.
- a detection code is placed.
- an error detection code for example, CRC-8 or CRC-16
- EXT_TYPE extension type
- step S102 an error correction coding process is performed on the data obtained in the process of step S101.
- this error correction coding process processes such as BCH coding by the BCH encoder 107 and LDPC coding by the LDPC encoder 108 are performed.
- step S103 modulation processing is performed on the data subjected to the error correction coding processing in the processing of step S102.
- interleaving processing by various interleavers, processing by the data mapper 111, the OFDM transmission unit 117, and the like are performed.
- an RF signal (OFDM signal) obtained by this modulation processing is transmitted through the transmission path 30.
- step S201 demodulation processing is performed on the RF signal (OFDM signal) transmitted from the transmission apparatus 10 through the transmission path 30.
- processing by the OFDM receiving unit 202 or the data demapper 208, deinterleave processing by various deinterleavers, and the like are performed.
- step S202 an error correction decoding process is performed on the data demodulated in the process of step S201.
- this error correction decoding process processes such as LDPC decoding by the LDPC decoder 211 and BCH decoding by the BCH decoder 212 are performed.
- step S203 packet processing is performed on the data subjected to the error correction decoding process in the process of step S202.
- packet processing is performed on BB packets, ALP packets, and UDP / IP packets by the BB depacketizer 214, the ALP depacketizer 215, and the UDP / IP depacketizer 216.
- an extension data type (extension header (header_extension)) of the ALP header of the ALP packet processed in the process of step S203 is Since an error detection code (for example, CRC-8 or CRC-16) corresponding to the extension_type is arranged, an error detection process is performed using the error detection code of the ALP header.
- an error detection code for example, CRC-8 or CRC-16
- the extension type (Extension Field) of the BB header of the BB packet processed in the process of step S203 is Since an error detection code (for example, CRC-8 or CRC-16) corresponding to the EXT_TYPE is disposed, an error detection process using the error detection code of the BB header is performed.
- an error detection code for example, CRC-8 or CRC-16
- the data after packet processing is decoded by the AV decoder 218 or the like, whereby the receiving apparatus 20 reproduces content such as a broadcast program.
- step S211 the BB depacketizer 214 acquires the next BB packet to be processed.
- step S212 the BB depacketizer 214 determines whether the ALP packet placed in the payload of the processing-target BB packet acquired in the process of step S211 is in the middle of the ALP packet.
- step S212 If it is determined in step S212 that the packet is not in the middle of the ALP packet, the process proceeds to step S213.
- step S213 the BB depacketizer 214 acquires the BB header of the BB packet to be processed.
- step S213A the BB depacketizer 214 acquires a CRC value (BB CRC value) included in (the extension field of) the BB header acquired in the process of step S213.
- step S213B the BB depacketizer 214 calculates a CRC value (BB CRC value) based on the CRC value (BB CRC value) acquired in the process of step S213A.
- step S213C the BB depacketizer 214 determines whether a comparison error of a CRC value (BB CRC value) has occurred according to the calculation result of step S213B.
- the comparison error determination process (S213C) using the BB CRC value is processed in the same manner as the comparison error determination process (S218) using the ALP CRC value described later, so here The description is omitted.
- step S213C If it is determined in step S213C that a CRC value (BB CRC value) comparison error has occurred, the process returns to step S211. Then, the next processing target BB packet is acquired, and the same processing as the processing (processing after S211) on the processing target BB packet described above is performed.
- step S213C determines whether a CRC value (BB CRC value) comparison error has occurred. If it is determined in step S213C that a CRC value (BB CRC value) comparison error has not occurred, the process proceeds to step S214.
- the BB depacketizer 214 acquires the leading ALP pointer included in the BB header acquired in the process of step S213.
- step S215 the BB depacketizer 214 acquires the ALP header of the processing target ALP packet (head ALP packet) based on the position specified by the top ALP pointer acquired in the process of step S214.
- step S216 the BB depacketizer 214 acquires a CRC value (ALP CRC value) included in (the extension header of) the ALP header acquired in the process of step S215.
- step S217 the BB depacketizer 214 calculates a CRC value (ALP CRC value) based on the CRC value (ALP CRC value) acquired in the process of step S216.
- step S218 the BB depacketizer 214 determines whether a comparison error of a CRC value (ALP CRC value) has occurred according to the calculation result of step S217.
- a predetermined calculation is performed on the input data string from transmission device 10 through transmission path 30, and the remainder is used for checking. Since the data added as a value is transmitted, the receiver 20 (of the BB depacketizer 214) performs the same calculation (predetermined calculation) using the data from the transmitter 10, and checks the calculation result By comparing with the value of, it is determined whether the data is corrupted.
- step S218 If it is determined in step S218 that a CRC value (ALP CRC value) comparison error has occurred, the process returns to step S211. Then, the next processing target BB packet is acquired, and the same processing as the processing (processing after S211) on the processing target BB packet described above is performed.
- a CRC value ALP CRC value
- step S218 if it is determined in step S218 that a comparison error of a CRC value (ALP CRC value) has not occurred, the process proceeds to step S219.
- step S219 the BB depacketizer 214 acquires the ALP packet length (packet length of ALP packet) included in the ALP header acquired in the process of step S215. Since the ALP packet length acquired here is data acquired from the ALP header for which no error was detected by the error detection processing of the CRC, it can be said that it is reliable information.
- step S220 the BB depacketizer 214 obtains the payload of the ALP packet to be processed.
- the process proceeds to step S211.
- step S221 it is determined whether the BB packet to be processed has ended. If it is determined in step S211 that the BB packet to be processed has not ended, the process proceeds to step S222.
- step S222 it is determined whether the processing target ALP packet has ended. If it is determined in step S222 that the ALP packet to be processed has not ended, the process returns to step S220, and the subsequent processing is repeated. That is, the payload of the processing target ALP packet is acquired until the processing target BB packet ends ("YES" in S221) or the processing target ALP packet ends ("YES" in S222) ( S220).
- step S222 If it is determined in step S222 that the processing target ALP packet has ended, the process proceeds to step S223.
- step S223 UDP / IP processing is performed.
- step S223 ends, the process proceeds to step S215.
- the next ALP packet to be processed (ALP header or payload) is processed according to the position specified by the ALP packet length (packet length of ALP packet) acquired in the process of step S219.
- a process similar to the process (the process after S215) on the acquired ALP packet to be processed is performed.
- step S221 If it is determined in step S221 that the BB packet to be processed has ended, the process proceeds to step S211. Then, the next processing target BB packet is acquired, and the same processing as the processing (processing after S211) on the processing target BB packet described above is performed.
- step S212 If it is determined in step S212 that the process is in the middle of the ALP packet to be processed, the process proceeds to step S224.
- step S224 the BB depacketizer 214 blanks the BB header of the BB packet to be processed.
- step S220 the process proceeds to step S220, and the subsequent processes are performed.
- the ATSC in particular, ATSC 3.0
- ATSC 3.0 which is a system adopted in the United States and the like
- DVB Digital Video Broadcasting
- the ATSC 3.0 in which the IP transmission method using the IP packet is adopted is described as an example, but not limited to the IP transmission method, for example, other than the MPEG2-TS (Transport Stream) method etc. It may be applied to the method of
- satellite broadcasting that uses broadcasting satellites (BS) and communication satellites (CS), etc., and cable broadcasting (CATV), etc., should be applied as standards for digital broadcasting. Can.
- BB packet Basic Packet
- BBS Baseband Stream
- BBF Baseband Frame
- ALP ATSC Link layer Protocol
- the present technology prescribes a predetermined standard (assuming use of a transmission line other than a broadcast network, ie, a communication line (communication network) such as the Internet or a telephone network) as a transmission line.
- a communication line such as the Internet or a telephone network may be used as the transmission line 30 of the transmission system 1 (FIG. 1), and the transmission device 10 may be a server provided on the Internet.
- the transmitting device 10 server
- the transmitting device 10 processes data transmitted from the transmitting device 10 (server) via the transmission path 30 (communication line).
- FIG. 27 is a diagram showing an example of a hardware configuration of a computer that executes the series of processes described above according to a program.
- a central processing unit (CPU) 1001, a read only memory (ROM) 1002, and a random access memory (RAM) 1003 are mutually connected by a bus 1004.
- An input / output interface 1005 is further connected to the bus 1004.
- An input unit 1006, an output unit 1007, a recording unit 1008, a communication unit 1009, and a drive 1010 are connected to the input / output interface 1005.
- the input unit 1006 includes a keyboard, a mouse, a microphone and the like.
- the output unit 1007 includes a display, a speaker, and the like.
- the recording unit 1008 includes a hard disk, a non-volatile memory, and the like.
- the communication unit 1009 includes a network interface or the like.
- the drive 1010 drives removable media 1011 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory.
- the CPU 1001 loads the program stored in the ROM 1002 or the recording unit 1008 into the RAM 1003 via the input / output interface 1005 and the bus 1004, and executes the program. A series of processing is performed.
- the program executed by the computer 1000 can be provided by being recorded on, for example, a removable medium 1011 as a package medium or the like. Also, the program can be provided via a wired or wireless transmission medium such as a local area network, the Internet, or digital satellite broadcasting.
- the program can be installed in the recording unit 1008 via the input / output interface 1005 by mounting the removable media 1011 in the drive 1010. Also, the program can be received by the communication unit 1009 via a wired or wireless transmission medium and installed in the recording unit 1008. Besides, the program can be installed in advance in the ROM 1002 and the recording unit 1008.
- the processing performed by the computer according to the program does not necessarily have to be performed chronologically in the order described as the flowchart. That is, the processing performed by the computer according to the program includes processing executed in parallel or separately (for example, parallel processing or processing by an object). Further, the program may be processed by one computer (processor) or may be distributed and processed by a plurality of computers.
- the present technology can have the following configurations.
- Processing unit for processing the transmission packet A receiving unit that performs an error detection process using the error detection code included in a header of the transmission packet; (2) The receiver according to (1), wherein the processing unit performs processing according to the detected position of the error when an error is detected by the error detection processing using the error detection code included in the header of the transmission packet.
- the processing unit extracts the transmission packet disposed after the detection position of the error in the payload of the baseband packet and processes the transmission packet as it is 2) The receiving device as described in 2).
- the transmission packet when the detection position of the error is a header of the transmission packet, the transmission packet disposed after the detection position of the error in the payload of the baseband packet is discarded (2).
- Receiving device (5) The receiver according to any one of (1) to (4), wherein the error detection code is a cyclic redundancy check (CRC).
- CRC cyclic redundancy check
- the transmission packet is a variable-length packet
- the header of the baseband packet includes a pointer indicating the position of the beginning of the transmission packet;
- the header of the transmission packet includes the data length of the transmission packet,
- the receiving device according to any one of (1) to (5), wherein arrangement positions of the plurality of transmission packets arranged in the payload of the baseband packet are specified by the pointer and the data length.
- the receiving device A plurality of transmission packets arranged in the payload of the baseband packet after demodulation, the transmission packet including a header including an error detection code and a payload in which an IP packet including a UDP packet is arranged
- a data processing method comprising the step of performing an error detection process using the error detection code.
- a processing unit for generating the transmission packet the transmission packet being disposed in the payload of the baseband packet before modulation, the header including an error detection code, and the payload in which the IP packet including the UDP packet is disposed. Equipped The processing unit places a plurality of the transmission packets in the payload of the baseband packet.
- the transmitting device A transmission packet disposed in a payload of a baseband packet before modulation, the transmission packet being composed of a header including an error detection code and a payload in which an IP packet including a UDP packet is disposed;
- a data processing method comprising: arranging a plurality of the transmission packets in a payload of the baseband packet.
- the baseband packet which is a baseband packet after demodulation, including a header including an error detection code, and a payload including a plurality of transmission packets including a payload including an IP packet including a UDP packet.
- Processing unit to process A receiving unit that performs an error detection process using the error detection code included in a header of the baseband packet;
- the error detection code is a cyclic redundancy check (CRC).
- the transmission packet is a variable-length packet
- the header of the baseband packet includes a pointer indicating the position of the beginning of the transmission packet;
- the header of the transmission packet includes the data length of the transmission packet,
- the receiving device according to (10) or (11), wherein arrangement positions of the plurality of transmission packets arranged in the payload of the baseband packet are specified by the pointer and the data length.
- the receiving device In the data processing method of the receiving device, The receiving device
- the baseband packet which is a baseband packet after demodulation, including a header including an error detection code, and a payload including a plurality of transmission packets including a payload including an IP packet including a UDP packet. Performing an error detection process using the error detection code included in the header of the data processing method.
- a transmission packet disposed in a payload of a baseband packet before modulation the processing unit generating the transmission packet including a payload in which an IP packet including a UDP packet is disposed;
- the processing unit places an error detection code in the header of the baseband packet, and places a plurality of the transmission packets in the payload of the baseband packet.
- the transmitting device A transmission packet disposed in the payload of the baseband packet before modulation, wherein the transmission packet is configured to include the payload in which the IP packet including the UDP packet is disposed;
- An error detection code is placed in the header of the baseband packet, and a plurality of the transmission packets are placed in the payload of the baseband packet.
- Reference Signs List 1 transmission system 10 transmission devices, 20 reception devices, 30 transmission paths, 101 AV encoder, 102 FLUTE encoder, 103 UDP / IP packetizer, 104 ALP packetizer, 105 BB packetizer, 106 scrambler, 107 BCH encoder, 108 LDPC encoder, 109 parity interleaver, 110 column twist interleaver, 111 data mapper, 112 CQ delay block, 113 cell interleaver, 114 time interleaver, 115 frame mapper, 116 frequency interleaver, 117 OFDM transmitter, 118 RF output block, 201 RF input, 202 OFDM receiver, 203 frequency deinterleaver, 204 frame demapper, 205 time day Tarleaver, 206 Cell Deinterleaver, 207 CQ Delay Unit, 208 Data Demapper, 209 Column Twist Deinterleaver, 210 Parity Deinterleaver, 211 LDPC Decoder, 212 BCH Decoder, 213 Descram
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Communication Control (AREA)
- Detection And Prevention Of Errors In Transmission (AREA)
Abstract
Description
2.現状の規格の概要
3.本技術の実施の形態
(1)第1の方式:ALPヘッダに誤り検出符号を配置
(2)第2の方式:BBヘッダに誤り検出符号を配置
(3)本技術のパケット処理
4.変形例
5.コンピュータの構成
図1は、本技術を適用した伝送システムの一実施の形態の構成を示す図である。なお、システムとは、複数の装置が論理的に集合したものをいう。
図2は、図1の送信装置10の構成例を示す図である。
図3は、図1の受信装置20の構成例を示す図である。
図4は、本技術で用いられるパケットの相関を示す図である。
図5は、BBパケットに付加されるBBヘッダの構造を示す図である。
図7は、ALPヘッダのシンタックスの例を示す図である。
図8は、図7のadditional_header_for_single_packet()のシンタックスの例を示す図である。
図9は、図7のadditional_header_for_segmentation()のシンタックスの例を示す図である。
図10は、図7のadditional_header_for_concatenation()のシンタックスの例を示す図である。
図11は、図8及び図9のsub_stream_identification()のシンタックスの例を示す図である。
図12は、図8乃至図10のheader_extension()のシンタックスの例を示す図である。
上述したように、受信装置20(のBBデパケタイザ214)において、BBパケットのペイロードに配置される1又は複数のALPパケットは、BBヘッダの先頭ALPポインタと、ALPヘッダのパケット長(ALPパケットのパケット長)を用いることで、BBパケットから読み出されることになる。
ここで、図14のフローチャートを参照して、現状のパケット処理の流れについて説明する。なお、この現状のパケット処理は、受信装置20(図1)のBBデパケタイザ214乃至UDP/IPデパケタイザ216(図3)などにより実行される。
図15は、ALPパケットのシンタックスの例を示す図である。なお、以下で説明するALPヘッダの構造は、上述した図7乃至図12に示したALPヘッダの構造を拡張したものである。
図21は、BBパケットのBBヘッダにCRCを配置する場合のデータ構造の例を示す図である。なお、図21のBBヘッダの構造は、上述した図5に示したBBヘッダの構造に対応しており、説明が繰り返しになる部分については、その説明を適宜省略するものとする。
次に、上述した第1の方式や第2の方式によって、ALPパケットのALPヘッダやBBパケットのBBヘッダに、誤り検出符号が配置された場合の具体的なパケット処理の内容について説明する。ここでは、パケット内の誤り検出符号の伝送方式として、第1の方式が採用された場合に、受信装置20(のBBデパケタイザ214)で実行される、ALPパケットのALPヘッダに含まれる誤り検出符号(例えばCRC-8やCRC-16)を用いた誤り検出処理について説明する。
図22は、エラーの検出位置がALPパケットのペイロードである場合における、本技術のパケット処理を説明する図である。
図23は、エラーの検出位置がALPパケットのALPヘッダである場合における、本技術のパケット処理を説明する図である。
まず、図24のフローチャートを参照して、送信装置10(図1)により実行される送信側データ処理の流れを説明する。
次に、図25のフローチャートを参照して、受信装置20(図1)により実行される受信側データ処理の流れを説明する。
最後に、図26のフローチャートを参照して、図25のステップS203の処理に対応する本技術のパケット処理の流れを説明する。なお、この本技術のパケット処理は、受信装置20(図1)のBBデパケタイザ214乃至UDP/IPデパケタイザ216(図3)などにより実行される。
復調後のベースバンドパケットのペイロートに複数配置される伝送パケットであって、誤り検出符号を含むヘッダと、UDP(User Datagram Protocol)パケットを含むIP(Internet Protocol)パケットを配置したペイロードとから構成される前記伝送パケットを処理する処理部を備え、
前記処理部は、前記伝送パケットのヘッダに含まれる前記誤り検出符号を用いて、誤り検出処理を行う
受信装置。
(2)
前記処理部は、前記伝送パケットのヘッダに含まれる前記誤り検出符号を用いた誤り検出処理によりエラーが検出された場合、前記エラーの検出位置に応じた処理を行う
(1)に記載の受信装置。
(3)
前記処理部は、前記エラーの検出位置が、前記伝送パケットのペイロードである場合、前記ベースバンドパケットのペイロードにおいて、前記エラーの検出位置以降に配置される前記伝送パケットを抽出してそのまま処理する
(2)に記載の受信装置。
(4)
前記伝送パケットは、前記エラーの検出位置が、前記伝送パケットのヘッダである場合、前記ベースバンドパケットのペイロードにおいて、前記エラーの検出位置以降に配置される前記伝送パケットを破棄する
(2)に記載の受信装置。
(5)
前記誤り検出符号は、巡回冗長検査(CRC:Cyclic Redundancy Check)である
(1)乃至(4)のいずれかに記載の受信装置。
(6)
前記伝送パケットは、可変長のパケットであり、
前記ベースバンドパケットのヘッダは、前記伝送パケットの先頭の位置を示すポインタを含み、
前記伝送パケットのヘッダは、前記伝送パケットのデータ長を含み、
前記ベースバンドパケットのペイロードに配置される複数の前記伝送パケットの配置位置は、前記ポインタと前記データ長により特定される
(1)乃至(5)のいずれかに記載の受信装置。
(7)
受信装置のデータ処理方法において、
前記受信装置が、
復調後のベースバンドパケットのペイロートに複数配置される伝送パケットであって、誤り検出符号を含むヘッダと、UDPパケットを含むIPパケットを配置したペイロードとから構成される前記伝送パケットのヘッダに含まれる前記誤り検出符号を用いて、誤り検出処理を行う
ステップを含むデータ処理方法。
(8)
変調前のベースバンドパケットのペイロードに配置される伝送パケットであって、誤り検出符号を含むヘッダと、UDPパケットを含むIPパケットを配置したペイロードとから構成される前記伝送パケットを生成する処理部を備え、
前記処理部は、前記ベースバンドパケットのペイロードに、複数の前記伝送パケットを配置する
送信装置。
(9)
送信装置のデータ処理方法において、
前記送信装置が、
変調前のベースバンドパケットのペイロードに配置される伝送パケットであって、誤り検出符号を含むヘッダと、UDPパケットを含むIPパケットを配置したペイロードとから構成される前記伝送パケットを生成し、
前記ベースバンドパケットのペイロードに、複数の前記伝送パケットを配置する
ステップを含むデータ処理方法。
(10)
復調後のベースバンドパケットであって、誤り検出符号を含むヘッダと、UDPパケットを含むIPパケットを配置したペイロードを含んで構成される伝送パケットを複数配置したペイロードとから構成される前記ベースバンドパケットを処理する処理部を備え、
前記処理部は、前記ベースバンドパケットのヘッダに含まれる前記誤り検出符号を用いて、誤り検出処理を行う
受信装置。
(11)
前記誤り検出符号は、巡回冗長検査(CRC)である
(10)に記載の受信装置。
(12)
前記伝送パケットは、可変長のパケットであり、
前記ベースバンドパケットのヘッダは、前記伝送パケットの先頭の位置を示すポインタを含み、
前記伝送パケットのヘッダは、前記伝送パケットのデータ長を含み、
前記ベースバンドパケットのペイロードに配置される複数の前記伝送パケットの配置位置は、前記ポインタと前記データ長により特定される
(10)又は(11)に記載の受信装置。
(13)
受信装置のデータ処理方法において、
前記受信装置が、
復調後のベースバンドパケットであって、誤り検出符号を含むヘッダと、UDPパケットを含むIPパケットを配置したペイロードを含んで構成される伝送パケットを複数配置したペイロードとから構成される前記ベースバンドパケットのヘッダに含まれる前記誤り検出符号を用いて、誤り検出処理を行う
ステップを含むデータ処理方法。
(14)
変調前のベースバンドパケットのペイロードに配置される伝送パケットであって、UDPパケットを含むIPパケットを配置したペイロードを含んで構成される前記伝送パケットを生成する処理部を備え、
前記処理部は、前記ベースバンドパケットのヘッダに、誤り検出符号を配置し、前記ベースバンドパケットのペイロードに、複数の前記伝送パケットを配置する
送信装置。
(15)
送信装置のデータ処理方法において、
前記送信装置が、
変調前のベースバンドパケットのペイロードに配置される伝送パケットであって、UDPパケットを含むIPパケットを配置したペイロードを含んで構成される前記伝送パケットを生成し、
前記ベースバンドパケットのヘッダに、誤り検出符号を配置し、前記ベースバンドパケットのペイロードに、複数の前記伝送パケットを配置する
ステップを含むデータ処理方法。
Claims (15)
- 復調後のベースバンドパケットのペイロートに複数配置される伝送パケットであって、誤り検出符号を含むヘッダと、UDP(User Datagram Protocol)パケットを含むIP(Internet Protocol)パケットを配置したペイロードとから構成される前記伝送パケットを処理する処理部を備え、
前記処理部は、前記伝送パケットのヘッダに含まれる前記誤り検出符号を用いて、誤り検出処理を行う
受信装置。 - 前記処理部は、前記伝送パケットのヘッダに含まれる前記誤り検出符号を用いた誤り検出処理によりエラーが検出された場合、前記エラーの検出位置に応じた処理を行う
請求項1に記載の受信装置。 - 前記処理部は、前記エラーの検出位置が、前記伝送パケットのペイロードである場合、前記ベースバンドパケットのペイロードにおいて、前記エラーの検出位置以降に配置される前記伝送パケットを抽出してそのまま処理する
請求項2に記載の受信装置。 - 前記伝送パケットは、前記エラーの検出位置が、前記伝送パケットのヘッダである場合、前記ベースバンドパケットのペイロードにおいて、前記エラーの検出位置以降に配置される前記伝送パケットを破棄する
請求項2に記載の受信装置。 - 前記誤り検出符号は、巡回冗長検査(CRC:Cyclic Redundancy Check)である
請求項1に記載の受信装置。 - 前記伝送パケットは、可変長のパケットであり、
前記ベースバンドパケットのヘッダは、前記伝送パケットの先頭の位置を示すポインタを含み、
前記伝送パケットのヘッダは、前記伝送パケットのデータ長を含み、
前記ベースバンドパケットのペイロードに配置される複数の前記伝送パケットの配置位置は、前記ポインタと前記データ長により特定される
請求項1に記載の受信装置。 - 受信装置のデータ処理方法において、
前記受信装置が、
復調後のベースバンドパケットのペイロートに複数配置される伝送パケットであって、誤り検出符号を含むヘッダと、UDPパケットを含むIPパケットを配置したペイロードとから構成される前記伝送パケットのヘッダに含まれる前記誤り検出符号を用いて、誤り検出処理を行う
ステップを含むデータ処理方法。 - 変調前のベースバンドパケットのペイロードに配置される伝送パケットであって、誤り検出符号を含むヘッダと、UDPパケットを含むIPパケットを配置したペイロードとから構成される前記伝送パケットを生成する処理部を備え、
前記処理部は、前記ベースバンドパケットのペイロードに、複数の前記伝送パケットを配置する
送信装置。 - 送信装置のデータ処理方法において、
前記送信装置が、
変調前のベースバンドパケットのペイロードに配置される伝送パケットであって、誤り検出符号を含むヘッダと、UDPパケットを含むIPパケットを配置したペイロードとから構成される前記伝送パケットを生成し、
前記ベースバンドパケットのペイロードに、複数の前記伝送パケットを配置する
ステップを含むデータ処理方法。 - 復調後のベースバンドパケットであって、誤り検出符号を含むヘッダと、UDPパケットを含むIPパケットを配置したペイロードを含んで構成される伝送パケットを複数配置したペイロードとから構成される前記ベースバンドパケットを処理する処理部を備え、
前記処理部は、前記ベースバンドパケットのヘッダに含まれる前記誤り検出符号を用いて、誤り検出処理を行う
受信装置。 - 前記誤り検出符号は、巡回冗長検査(CRC)である
請求項10に記載の受信装置。 - 前記伝送パケットは、可変長のパケットであり、
前記ベースバンドパケットのヘッダは、前記伝送パケットの先頭の位置を示すポインタを含み、
前記伝送パケットのヘッダは、前記伝送パケットのデータ長を含み、
前記ベースバンドパケットのペイロードに配置される複数の前記伝送パケットの配置位置は、前記ポインタと前記データ長により特定される
請求項10に記載の受信装置。 - 受信装置のデータ処理方法において、
前記受信装置が、
復調後のベースバンドパケットであって、誤り検出符号を含むヘッダと、UDPパケットを含むIPパケットを配置したペイロードを含んで構成される伝送パケットを複数配置したペイロードとから構成される前記ベースバンドパケットのヘッダに含まれる前記誤り検出符号を用いて、誤り検出処理を行う
ステップを含むデータ処理方法。 - 変調前のベースバンドパケットのペイロードに配置される伝送パケットであって、UDPパケットを含むIPパケットを配置したペイロードを含んで構成される前記伝送パケットを生成する処理部を備え、
前記処理部は、前記ベースバンドパケットのヘッダに、誤り検出符号を配置し、前記ベースバンドパケットのペイロードに、複数の前記伝送パケットを配置する
送信装置。 - 送信装置のデータ処理方法において、
前記送信装置が、
変調前のベースバンドパケットのペイロードに配置される伝送パケットであって、UDPパケットを含むIPパケットを配置したペイロードを含んで構成される前記伝送パケットを生成し、
前記ベースバンドパケットのヘッダに、誤り検出符号を配置し、前記ベースバンドパケットのペイロードに、複数の前記伝送パケットを配置する
ステップを含むデータ処理方法。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2018501567A JPWO2017145790A1 (ja) | 2016-02-26 | 2017-02-10 | 受信装置、送信装置、及び、データ処理方法 |
US16/078,138 US20200044774A1 (en) | 2016-02-26 | 2017-02-10 | Reception apparatus, transmission apparatus, and data processing method |
EP17756231.1A EP3422618A4 (en) | 2016-02-26 | 2017-02-10 | RECEIVING DEVICE, SENDING DEVICE AND DATA PROCESSING METHOD |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2016-035731 | 2016-02-26 | ||
JP2016035731 | 2016-02-26 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017145790A1 true WO2017145790A1 (ja) | 2017-08-31 |
Family
ID=59686119
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2017/004848 WO2017145790A1 (ja) | 2016-02-26 | 2017-02-10 | 受信装置、送信装置、及び、データ処理方法 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20200044774A1 (ja) |
EP (1) | EP3422618A4 (ja) |
JP (1) | JPWO2017145790A1 (ja) |
WO (1) | WO2017145790A1 (ja) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019239695A1 (ja) * | 2018-06-13 | 2019-12-19 | ソニーセミコンダクタソリューションズ株式会社 | 復調回路、処理方法、および処理装置 |
JP2020043524A (ja) * | 2018-09-13 | 2020-03-19 | 株式会社日立国際電気 | 配信システム |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110601971B (zh) * | 2019-09-17 | 2021-10-26 | 南京林业大学 | 一种数据传输方法、装置、电子设备及存储介质 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2006352897A (ja) * | 2006-07-07 | 2006-12-28 | Toshiba Corp | 通信装置、通信方法、および通信システム |
JP2013520036A (ja) * | 2010-02-26 | 2013-05-30 | パナソニック株式会社 | デジタル放送システムにおける物理レイヤシグナリング |
US20150229443A1 (en) * | 2014-02-13 | 2015-08-13 | Lg Electronics Inc. | Apparatus and method for sending and receiving broadcast signals |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2010036739A1 (en) * | 2008-09-26 | 2010-04-01 | Telegent Systems, Inc. | Devices and methods of digital video and/or audio reception and/or output having error detection and/or concealment circuitry and techniques |
KR101670723B1 (ko) * | 2011-01-04 | 2016-11-01 | 삼성전자주식회사 | 비디오 및 오디오 통신 시스템에서 가변 길이의 전송 패킷 지원 방법 및 장치 |
EP2552042B1 (de) * | 2011-07-28 | 2013-03-13 | Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. | Demultiplexen eines paketbasierten Transportstroms |
WO2015055256A1 (en) * | 2013-10-18 | 2015-04-23 | Huawei Technologies Co., Ltd. | Transmission and receiving method in a wireless communication system |
US9917930B2 (en) * | 2015-01-07 | 2018-03-13 | Samsung Electronics Co., Ltd. | Transmitting apparatus and receiving apparatus and signal processing method thereof |
-
2017
- 2017-02-10 JP JP2018501567A patent/JPWO2017145790A1/ja not_active Abandoned
- 2017-02-10 EP EP17756231.1A patent/EP3422618A4/en not_active Withdrawn
- 2017-02-10 WO PCT/JP2017/004848 patent/WO2017145790A1/ja active Application Filing
- 2017-02-10 US US16/078,138 patent/US20200044774A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2006352897A (ja) * | 2006-07-07 | 2006-12-28 | Toshiba Corp | 通信装置、通信方法、および通信システム |
JP2013520036A (ja) * | 2010-02-26 | 2013-05-30 | パナソニック株式会社 | デジタル放送システムにおける物理レイヤシグナリング |
US20150229443A1 (en) * | 2014-02-13 | 2015-08-13 | Lg Electronics Inc. | Apparatus and method for sending and receiving broadcast signals |
Non-Patent Citations (2)
Title |
---|
PHYSICAL LAYER PROTOCOL, 28 September 2015 (2015-09-28) |
See also references of EP3422618A4 |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019239695A1 (ja) * | 2018-06-13 | 2019-12-19 | ソニーセミコンダクタソリューションズ株式会社 | 復調回路、処理方法、および処理装置 |
KR20210018994A (ko) * | 2018-06-13 | 2021-02-19 | 소니 세미컨덕터 솔루션즈 가부시키가이샤 | 복조 회로, 처리 방법, 및 처리 장치 |
US11432036B2 (en) | 2018-06-13 | 2022-08-30 | Sony Semiconductor Solutions Corporation | Demodulation circuit, processing method, and processing device |
KR102654958B1 (ko) | 2018-06-13 | 2024-04-05 | 소니 세미컨덕터 솔루션즈 가부시키가이샤 | 복조 회로, 처리 방법, 및 처리 장치 |
JP2020043524A (ja) * | 2018-09-13 | 2020-03-19 | 株式会社日立国際電気 | 配信システム |
JP7058576B2 (ja) | 2018-09-13 | 2022-04-22 | 株式会社日立国際電気 | 配信システム |
Also Published As
Publication number | Publication date |
---|---|
EP3422618A4 (en) | 2019-03-13 |
JPWO2017145790A1 (ja) | 2018-12-20 |
US20200044774A1 (en) | 2020-02-06 |
EP3422618A1 (en) | 2019-01-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
TWI501579B (zh) | 使用透過單播系統接收之增量冗餘以在廣播系統中接收資料的接收器與接收方法 | |
US7889707B2 (en) | Method and system for unequal error protection with block codes for wireless transmission | |
KR100913108B1 (ko) | 수신 시스템 및 데이터 처리 방법 | |
KR102445458B1 (ko) | 송신 장치, 송신 방법, 수신 장치 및 수신 방법 | |
US8406211B2 (en) | Forward error correction for broadcast/multicast service | |
US20070240027A1 (en) | Forward Error Correction Decoders | |
KR100998454B1 (ko) | 인 밴드 에러 패턴을 사용한 에러 복원 | |
US20070277209A1 (en) | Robust transmission system and method for mobile television applications | |
KR102386821B1 (ko) | 방송 시스템에서 시스템 시간 정보를 송수신하는 기법 | |
KR20090031323A (ko) | 디지털 방송 시스템 및 데이터 처리 방법 | |
CN111373759B (zh) | 广播信号传输设备、广播信号传输方法、广播信号接收设备及广播信号接收方法 | |
KR102603460B1 (ko) | 방송 신호 송신 장치, 방송 신호 송신 방법, 방송 신호 수신 장치 및 방송 수신 신호 방법 | |
WO2017145790A1 (ja) | 受信装置、送信装置、及び、データ処理方法 | |
KR102163338B1 (ko) | 방송 및 통신 시스템에서 패킷 송수신 장치 및 방법 | |
KR100955814B1 (ko) | 순방향 오류 정정을 포함하는 수신기를 동작시키기 위한장치 및 방법 | |
JP3730977B2 (ja) | データ伝送方法およびデータ処理方法 | |
WO2021153301A1 (ja) | 情報処理装置、情報処理方法、及び、プログラム | |
JP2018160752A (ja) | 送信装置、受信装置及びプログラム | |
US20040114599A1 (en) | Massive packet transmitter in wide area network and transmitting and receiving method thereof | |
JP2009201117A (ja) | データ受信装置及びそのプログラム | |
WO2017130724A1 (ja) | データ処理装置、及び、データ処理方法 | |
CN101938439A (zh) | 移动多媒体广播系统中复用数据的传送方法与装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 2018501567 Country of ref document: JP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2017756231 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2017756231 Country of ref document: EP Effective date: 20180926 |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 17756231 Country of ref document: EP Kind code of ref document: A1 |