WO2016171008A1 - Appareil d'émission, procédé d'émission, appareil de réception, et procédé de réception - Google Patents

Appareil d'émission, procédé d'émission, appareil de réception, et procédé de réception Download PDF

Info

Publication number
WO2016171008A1
WO2016171008A1 PCT/JP2016/061522 JP2016061522W WO2016171008A1 WO 2016171008 A1 WO2016171008 A1 WO 2016171008A1 JP 2016061522 W JP2016061522 W JP 2016061522W WO 2016171008 A1 WO2016171008 A1 WO 2016171008A1
Authority
WO
WIPO (PCT)
Prior art keywords
header
information
packet
udp
transmission
Prior art date
Application number
PCT/JP2016/061522
Other languages
English (en)
Japanese (ja)
Inventor
高橋　和幸
山岸　靖明
Original Assignee
ソニー株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ソニー株式会社 filed Critical ソニー株式会社
Publication of WO2016171008A1 publication Critical patent/WO2016171008A1/fr

Links

Images

Definitions

  • the present technology relates to a transmission apparatus, a transmission method, a reception apparatus, and a reception method, and in particular, for example, a transmission apparatus, a transmission method, and a reception that can broadcast IP packets efficiently and process them quickly and appropriately.
  • the present invention relates to an apparatus and a reception method.
  • ATSC Advanced Television Systems Systems Committee
  • UDP User Datagram Protocol / Internet Protocol
  • TS Transport Stream
  • IP packets contain various information in the header and have a large overhead. Therefore, as a technique for compressing the header of the IP packet for efficiently transmitting the IP packet, there is RoHC (Robust header compression) defined by IETF (Internet Engineering Task Force).
  • RoHC Robot header compression
  • an IP packet including all header information (hereinafter also referred to as a complete IP packet) is transmitted, and for the subsequent IP packet header, information on the difference from the header of the previous complete IP packet is transmitted.
  • IP packet header compression technology that transmits complete IP packets, and then transmits IP packets that contain the difference information from the complete IP packet header, as in RoHC. .
  • a differential compression method is defined as a technique for compressing the header of an IP packet (Non-patent Document 1).
  • IP packets may not be broadcast efficiently.
  • the differential compression method after receiving a complete IP packet, the subsequent IP packet can be restored on the receiving side. Therefore, in order to restore the IP packet on the receiving side, it is necessary to broadcast the complete IP packet frequently to some extent, and it is difficult to expect a large compression effect.
  • the received IP packet cannot be restored until the first complete IP packet is received. After receiving a complete IP packet.
  • the information constituting the header of the IP packet or the header of the UDP packet differs depending on the service form after the IP packet is received.
  • the destination IP address (destination IP address) is essential, and in the header of the UDP packet, The destination port number (destination port number) is mandatory.
  • the Fragment information is further required as the IP packet header.
  • IP / UDP header the information essential in the header of the IP packet and the header of the UDP packet (hereinafter also referred to as IP / UDP header) differs depending on the form of service after the IP packet is received by the receiver. is there.
  • using a predetermined fixed value may change the service form after the IP packet is received by the receiver.
  • the required information may be set to a fixed value, and the IP packet may not be appropriately processed.
  • the present technology has been made in view of such a situation.
  • the IP packet can be efficiently broadcast and quickly transmitted.
  • the processing can be appropriately performed.
  • the transmission device includes a type information indicating whether an IP (Internet Protocol) header and a UDP (User Datagram Protocol) header are compressed, and a transmission packet that transmits an IP packet including the UDP packet.
  • a header composed of length information indicating a length, a destination IP address of the IP packet, a destination port number of the UDP packet, predetermined information included in the IP header, and a predetermined information included in the UDP header Transmission information that specifies information to be transmitted among the information, and the predetermined information included in the IP header and the predetermined information included in the UDP header based on the transmission specific information.
  • a generation unit configured to generate the transmission packet including information specified as information to be transmitted and a payload including the payload of the UDP packet, and the transmission And a transmission unit that transmits a transmission packet.
  • the predetermined information included in the IP header can include a destination IP address and fragment information.
  • the predetermined information included in the UDP header includes a destination port number and a check of the UDP packet. Sum information can be included.
  • the transmission specifying information includes first specifying information indicating whether the destination IP address and the destination port number are specified as information to be transmitted, and whether to specify the fragment information as information to be transmitted. And second specific information indicating whether or not the checksum information is specified as information to be transmitted can be included.
  • a storage unit that stores setting data for setting the transmission specific information and an operation unit that edits the setting data stored in the storage unit based on an operation signal according to a user operation are further included.
  • the generation unit generates the transmission specific information based on the setting data, and the predetermined information included in the IP header based on the transmission specific information, and the UDP header Information specified as information to be transmitted among predetermined information included in the IP packet, and using the destination IP address of the IP packet and the destination port number of the UDP packet, the IP header and the UDP header And generating the transmission packet using the generated IP header and UDP header.
  • the transmission method includes an IP (Internet Protocol) header and a type information indicating whether a UDP (User Datagram Protocol) header is compressed, and a transmission packet that transmits an IP packet including a UDP packet.
  • IP Internet Protocol
  • UDP User Datagram Protocol
  • a receiving apparatus includes an IP (Internet Protocol) header and a type information indicating whether a UDP (User Datagram Protocol) header is compressed, and a transmission packet that transmits an IP packet including a UDP packet.
  • IP Internet Protocol
  • a header composed of length information indicating a length, a destination IP address of the IP packet, a destination port number of the UDP packet, predetermined information included in the IP header, and a predetermined information included in the UDP header Transmission information that specifies information to be transmitted among the information, and the predetermined information included in the IP header and the predetermined information included in the UDP header based on the transmission specific information.
  • a receiving unit configured to receive the transmission packet including information specified as information to be transmitted and a payload including the payload of the UDP packet;
  • the receiving apparatus includes a restoration unit that restores the IP packet from a transmission packet.
  • the restoration unit restores information specified as information to be transmitted among predetermined information included in the IP header and predetermined information included in the UDP header, Based on the transmission specifying information, information that is not specified as information to be transmitted among predetermined information included in the IP header and predetermined information included in the UDP header is set to a predetermined fixed value.
  • the destination IP address and the destination port number are restored as the destination IP address included in the IP header and the destination port number included in the UDP header, respectively, and from the length information to the IP header
  • the IP packet length information included and the UDP packet length information included in the UDP packet can be restored.
  • the predetermined information included in the IP header can include a destination IP address and fragment information.
  • the predetermined information included in the UDP header includes a destination port number and a check of the UDP packet. Sum information can be included.
  • the transmission specifying information includes first specifying information indicating whether the destination IP address and the destination port number are specified as information to be transmitted, and whether to specify the fragment information as information to be transmitted. And second specific information indicating whether or not the checksum information is specified as information to be transmitted can be included.
  • the reception method includes: IP (Internet Protocol) header and type information indicating whether UDP (User Datagram Protocol) header is compressed; and transmission packets that transmit IP packets including UDP packets.
  • IP Internet Protocol
  • a header composed of length information indicating a length, a destination IP address of the IP packet, a destination port number of the UDP packet, predetermined information included in the IP header, and a predetermined information included in the UDP header Transmission information that specifies information to be transmitted among the information, and the predetermined information included in the IP header and the predetermined information included in the UDP header based on the transmission specific information.
  • the transmission packet composed of information identified as information and a payload composed of the payload of the UDP packet is generated, and the transmission packet Is transmitted and received, and the transmission packet is restored.
  • the transmission device and the reception device may be independent devices, or may be a block that performs transmission processing and reception processing.
  • IP packets can be efficiently broadcast and processed quickly.
  • FIG. 18 is a block diagram illustrating a configuration example of an embodiment of a computer to which the present technology is applied.
  • FIG. 1 is a diagram illustrating a configuration example of an embodiment of a broadcasting system to which the present technology is applied.
  • the broadcasting system includes a transmitting device 10 and a receiving device 20.
  • the transmission device 10 is a transmission device compliant with a predetermined broadcast standard such as ATSC 3.0, and performs data transmission using IP packets including UDP packets.
  • the transmission device 10 includes a generation unit 11, a transmission unit 12, and an operation unit 13.
  • the generation unit 11 is supplied with a UDP / IP IP packet including actual data to be broadcast, that is, an IP packet in which a UDP packet including actual data is arranged.
  • the generation unit 11 generates a generic packet, which will be described later, as a transmission packet for transmitting the IP packet supplied thereto, and supplies it to the transmission unit 12.
  • the generation unit 11 stores setting data 11 a that is set according to information input by the operation unit 13.
  • the generation unit 11 generates a generic packet by switching the compression type of the header of the IP packet (IP ⁇ ⁇ ⁇ Header) and the header of the UPD packet (UDP Header) based on the information of the setting data 11a.
  • the transmission unit 12 transmits the generic packet supplied from the generation unit 11 via, for example, a transmission path 30 that is a terrestrial wave.
  • the receiving device 20 is a transmitting device compliant with a predetermined broadcast standard such as ATSC 3.0, and receives an IP packet transmitted from the transmitting device 10.
  • a predetermined broadcast standard such as ATSC 3.0
  • the receiving device 20 includes a receiving unit 21 and a restoring unit 22.
  • the reception unit 21 receives a generic packet transmitted from the transmission device 10 via the transmission path 30 and supplies the generic packet to the restoration unit 22.
  • the restoration unit 22 restores the IP packet from the generic packet from the reception unit 21 and outputs the IP packet. At this time, the restoration unit 22 determines the compression type of the header of the IP packet, and restores the IP packet based on the determination result.
  • FIG. 1 only one receiving device 20 is shown for simplicity of explanation, but a plurality of receiving devices 20 can be provided, and the generic packet transmitted (broadcasted) by the transmitting device 10 is: A plurality of receiving devices 20 can receive simultaneously.
  • a plurality of transmission devices 10 can be provided.
  • Each of the plurality of transmitting apparatuses 10 transmits a generic packet as a separate channel, for example, in a separate frequency band, and the receiving apparatus 20 receives a generic packet from each of the channels of the plurality of transmitting apparatuses 10.
  • a channel can be selected.
  • terrestrial waves are employed as the transmission line 30, however, for example, a satellite line or a cable (wired line) can be employed as the transmission line 30.
  • FIG. 2 is a diagram illustrating an example of the format of a generic packet.
  • the generic packet has a header and a payload.
  • the payload of the generic packet has a variable length, and for example, an IP packet including a UDP packet can be arranged in the variable length payload.
  • the header is composed of a fixed length such as 2 bytes (16 bits).
  • a fixed length such as 2 bytes (16 bits).
  • 3-bit type information (Type)
  • 11-bit length information (Length)
  • 1-bit Ext 1-bit Flg are arranged from the head.
  • the type information indicates whether the IP header of the IP packet placed in the payload and the UDP header of the UDP packet included in the IP packet are compressed. Details of the type information will be described later.
  • the length information represents the length (for example, the number of bytes) of the generic packet.
  • the length represented by the length information may be the length of the generic packet itself, that is, the total length of the header and payload of the generic packet, or the length of the payload of the generic packet.
  • the length information represents the length of the generic packet, for example, the length of the generic packet payload.
  • the header of the generic packet can specify the data length, if the payload length of the generic packet is known, the length of the generic packet itself can be uniquely specified.
  • the generic packet header is also referred to as a generic header
  • the generic packet payload is also referred to as a generic payload.
  • Ext represents whether the Generic header is a normal header or an extension header.
  • the normal header is a 2-byte header shown in FIG.
  • the extension header is, for example, a header configured with a data length of 3 bytes when, for example, 1 byte is added after the normal header.
  • the data length added after the normal header can be a variable length of 1 byte or more.
  • the length information is 11 bits
  • 11-bit length information cannot represent the length of a generic payload of 2048 bytes or more.
  • the extension header is, for example, a header in which 1 byte is added after the normal header, and the added 1 byte is also referred to as an additional byte.
  • the length of the generic packet (its payload) is represented by the length information and part or all of the additional bytes.
  • the additional bytes can have a variable length of 1 byte or more.
  • Ext When the Generic header is a normal header, for example, Ext is set to 0, and when the Generic header is an extension header, for example, Ext is set to 1.
  • the maximum length of an IP packet that can be placed in one Ethernet (registered trademark) frame is the maximum length of the Ethernet (registered trademark) frame. Limited by about 1500 bytes. For this reason, it is assumed that it is not so many that an IP packet exceeds 2047 bytes that can be represented by 11-bit length information.
  • Flg is type information indicating the compression type of the IP header and UDP header when the IP header of the IP packet arranged in the payload and the UDP header of the UDP packet included in the IP packet are compressed. is there. Details of the type information will be described later.
  • the Generic header can be configured without providing one or both of Ext and Flg.
  • the size of type information or length information can be increased accordingly.
  • Ext is assumed to be 0, and Flg is treated as any fixed value and not particularly related to processing.
  • FIG. 3 is a diagram showing the format of an IP packet whose IP version is IPv4 (IP version 4), including a UDP packet.
  • an IP packet has, for example, a 20-byte IP header (IP header) and a UDP packet arranged in a variable-length payload.
  • IP header IP header
  • UDP packet UDP packet arranged in a variable-length payload.
  • the UDP packet has an 8-byte UDP header (UDP Header) and a variable-length payload. Actual data is arranged in the payload of the UDP packet.
  • UDP Header 8-byte UDP header
  • variable-length payload 8-byte payload
  • Actual data is arranged in the payload of the UDP packet.
  • FIG. 4 is a diagram showing the format of the IPv4 IP header.
  • IP header includes version (Version), IHL, DSCP, ECN, IP packet length (Total Length), Identification, Flags, Fragment , Offset, Time To Live, Protocol, checksum (Header Checksum), source IP address (Source IP) Address), destination IP address (Destination IP Address), and necessary options.
  • the version indicates whether the IP version is IPv4 (IP version 4) or IPv6 (IP version 6). In the example of FIG. 4, the IP version is IPv4.
  • IHL represents the length of the IP header, and IHL is set to the value obtained by dividing the length of the IP header by 4.
  • DSCP represents the priority of the IP packet
  • ECN is used for IP packet congestion control.
  • IP packet length (Total Length) represents the length of the entire IP packet.
  • Identification, Flags, and Fragment Offset are information (fragment information) related to fragmentation of the IP packet.
  • the IP packet arranged in the generic packet may be divided and the information is recorded as fragment information. That is, one (or more) IP packets may be divided and placed in the generic payload.
  • Time ToLive represents the lifetime of the IP packet, that is, the number of routers through which the IP packet can pass, for example.
  • Protocol represents the protocol included in the payload of the IP packet.
  • the IP packet payload includes a UDP packet. Since UDP is represented by 17, 17 is set in Protocol.
  • the checksum (Header Checksum) is used to detect errors in the IP header.
  • the IP checksum is calculated by dividing the IP header in 16-bit units, calculating the 1's complement of each 16-bit unit, and calculating the 1's complement of the sum.
  • the IP address of the source of the IP packet is set in the source IP address (Source IP Address).
  • Destination IP address (Destination IP IP Address) is set to the destination IP address of the IP packet.
  • IP packet When the IP packet is broadcast as a generic packet, it is necessary for the receiving apparatus 20 to restore the IP header in the format of FIG. 4 (hereinafter also referred to as a formal IP header) in the items of the IP header of FIG.
  • the essential items are the IP packet length (Total Length) and the destination IP address (Destination IP Address).
  • the receiving device 20 items other than the IP packet length and the destination IP address that are essential items in the items of the IP header are hindered to be handled by the receiving device 20 by using predetermined fixed values. There is no official IP header can be restored. However, the IP packet length (Total Length) can also be obtained from the Length in the Generic header.
  • the source IP address (Source (IP Address) among the IP header items other than the IP packet length and the destination IP address is set to a fixed value and can be obtained from a higher layer protocol. it can.
  • the transmission source IP address can be acquired from information on the broadcasting station acquired in the upper layer.
  • the source IP address may be a fixed value as described above.
  • FIG. 5 is a diagram showing the format of the UDP header.
  • the UDP header has a source port number (Source port), a destination port number (Destination port), a UDP packet length (Length), and a checksum (Checksum).
  • the port number of the UDP packet source is set in the source port number (Source port).
  • the destination port number (Destination port) is set to the destination port number of the UDP packet.
  • the UDP packet length (Length) represents the length of the entire UDP packet.
  • UDP checksum is used to detect errors in UDP packets.
  • the UDP checksum is calculated using 1's complement arithmetic as the target of the UDP pseudo header, UDP header, and UDP packet payload.
  • the UDP pseudo header is virtual data used only for the calculation of the UDP checksum.
  • the receiving device 20 uses a UDP header in the format of FIG. 5 (hereinafter also referred to as a formal UDP header) in the items of the UDP header of FIG. 5 (hereinafter also referred to as a formal UDP header) in the items of the UDP header of FIG. Necessary items necessary for restoration are a destination port number (Destination port) and a UDP packet length (Length). However, the UDP packet length (Length) can also be obtained by obtaining the IP packet length (Total Length) from the Length in the Generic header and subtracting the data length of the IP header.
  • items other than the required destination port number and UDP packet length (source port number and checksum) among the items of the UDP header use predetermined fixed values, etc. It is possible to restore a formal UDP header that does not interfere with the reception device 20.
  • the source port number (Source (port) among the items of the UDP header other than the UDP packet length and the destination port number is set to a fixed value and can be acquired from a higher layer protocol. .
  • the transmission source port number can be acquired from information on the broadcasting station acquired in the upper layer.
  • the transmission source port number may be a fixed value as described above.
  • the essential items in the IP header are the IP packet length and the destination IP address. Further, as described with reference to FIG. 5, the essential items in the UDP header are the UDP packet length and the destination port number.
  • the IP header can be compressed into a compressed IP header having only information about the IP packet length and the destination IP address, and the UDP header is the UDP packet length and destination. It can be compressed into a compressed UDP header with only information about the port number.
  • the IP header and UDP header are fixed length of 20 bytes and 8 bytes, respectively, so the IP packet length and UDP packet length are It can be obtained from the length information (FIG. 2) of the Generic header.
  • the IP header and the UDP header can be compressed into information on the destination IP address and the destination port number, and even if such compression is performed, the formal IP that does not hinder the handling by the receiving device 20 Headers and UDP headers can be restored.
  • the generation unit 11 of the transmission device 10 converts the IP header and the UDP header included in the IP packet, the destination IP address, and the destination port number as necessary. Are compressed into a compressed IP header and a compressed UDP header including at least the above information.
  • the compressed IP header and the compressed UDP header can appropriately restore the IP packet by including at least the information of the destination IP address and the destination port number, other information can be selectively added.
  • other information can be selectively added.
  • FIG. 6 is a diagram for explaining type information (Type) of the Generic header of FIG.
  • the type information includes the presence or absence of compression of the IP header and the UDP header, that is, the IP header of the IP packet arranged in the generic payload and the UDP header of the UDP packet included in the IP packet. Indicates whether it is compressed.
  • the type information represents information related to the type of data arranged in the generic payload in addition to the presence or absence of compression of the IP header and UDP header in the IP packet arranged in the generic payload.
  • the type information is set to 000b (b represents that the value immediately before it is a binary number).
  • the type information is set to 001b.
  • IPv4 IP packet in which the IP header and UDP header are not compressed is arranged in the generic payload, that is, when the IP packet is arranged as it is in the generic payload, the type information is set to 010. .
  • the type information is set to 011.
  • the type information is set to 100.
  • the type information is set to 101.
  • the type information is set to 110.
  • the type information of other values that is, the type information of 111 is undefined (Reserved).
  • the type information it is possible to recognize whether the IP packet arranged in the generic payload is an IPv4 IP packet or an IPv6 IP packet, and the version (Version) of the IP header (Fig. 4) can be restored.
  • FIG. 7 is a diagram showing the format of an IP packet whose IP version is IPv6 (IP version 6), including UDP packets.
  • IPv6 IP version 6
  • UDP packets UDP packets
  • the IP packet in FIG. 7 has, for example, a 36-byte IP header (IP header) and a UDP packet arranged in a variable-length payload.
  • IP header IP header
  • UDP packet UDP packet arranged in a variable-length payload.
  • FIG. 8 is a diagram showing the format of the IPv6 IP header.
  • the IP header has a version (Version), Traffic Class, Flow Level, Payload Length, Next Header, Hop Limit, source IP address (Source IP Address), and destination IP address (Destination IP Address).
  • the version indicates whether the IP version is IPv4 (IP version 4) or IPv6 (IP version 6). In the example of FIG. 8, the IP version is IPv6.
  • Traffic Class is information corresponding to DSCP and ECN in IPv4, and is used for IP packet priority and congestion control.
  • the Flow Level is used to identify packets that require the same treatment, and is used with a label indicating a request that causes a specific traffic flow to be treated specially.
  • Payload Length indicates the packet size excluding the header.
  • Next Header indicates what kind of header is next. For example, in the case of only basic header, it indicates whether TCP header or UDP header is provided next, followed by extension header. The extension header is provided.
  • Hop Limit corresponds to Time ToLive (TTL) in IPv4, and represents the lifetime of the IP packet, that is, the number of routers through which the IP packet can pass, for example.
  • the IP address of the source of the IP packet is set in the source IP address (Source IP Address).
  • Destination IP address (Destination IP IP Address) is set to the destination IP address of the IP packet.
  • IPv6 IP header format is only the basic header, and the structure is simpler than in IPv4.
  • Most of the remaining information set in IPv4 is an extension header. It is configured to be added. For example, fragment information such as Identification, Flags, Fragment Offset, etc. in IPv4 is added as an extension header as necessary.
  • FIG. 9 shows, in time series, IP packets of broadcast programs that are sequentially input in time series toward the right in the figure.
  • the IP packet is composed of an uncompressed header including all information required as the IP packet header, and is expressed as a full IP packet 51-1 and 51-2 indicated as a full packet. Yes. Between the uncompressed complete IP packets 51-1 and 51-2, compressed packets 52-1 to 52-6 each including a compressed header, which is displayed as “Partial packet”, are provided.
  • the complete IP packet 51 is provided at a predetermined interval, and the same information is omitted during that time.
  • An IP packet 52 is provided.
  • the absolutely essential information in the IP header is the destination IP address in the IP header and the destination port number in the UDP header.
  • the receiving device 20 is a terminal at which a generic packet is received.
  • fragment information is insufficient.
  • the source IP address (Source ⁇ ⁇ ⁇ ⁇ IP Address) in the IP header and the source port number (Source port) in the UDP header may be added.
  • fragment information may be added to the IP header, and a checksum may be added to the UDP header.
  • the header of the IP packet including the UDP packet in the present technology whether or not to add each information described above can be set in the setting data 11a by operating the operation unit 13. And the production
  • step S11 the generation unit 11 determines whether the operation unit 13 is operated and setting data is input. When the operation unit 13 is operated and setting data is input, the processing is performed in step S11. Proceed to S12. In step S11, when it is determined that the operation unit 13 is not operated and there is no input to the setting data 11a, the process of step S12 is skipped.
  • step S12 the generation unit 11 records the setting data 11a based on information input by operating the operation unit 13. More specifically, the setting data 11a is used to identify a pattern of information remaining after being compressed among information included in the IP header and the UDP header, that is, a compression type of the IP header and the UDP header. Information HC_Type is recorded.
  • HC_Type is 1-byte information for identifying the compression type according to the information pattern added to the compressed IP header and the compressed UDP header. For example, as shown in the top row of FIG. 11, when the LSB (Least Significant Bit) is 1 (when 0b0000 0001), the compressed IP header and the compressed UDP header are absolutely required as the HC_type. Destination IP address and destination port number information in the UDP header are added with the source IP address (Source IP Address) in the IP header and the destination port number (Destination port) in the UDP header. Represents that. When LSB (Least Significant Bit) is not 1 (0b0000 -0000), the source IP address (Source IP IP Address) in the IP header and the destination port number (Destination Port) in the UDP header are added. It will not be configured.
  • the compressed IP header and compression represents a configuration in which fragment information is added to the IP header in addition to the destination IP address of the IP header and the destination port number of the UDP header, which are absolutely essential. It should be noted that, in the 1-byte information of HC_Type, when the value that is 1 larger than LSB is not 1 (when 0b0000 0000), the fragment information is not added to the IP header.
  • the compressed IP header and the compressed The UDP header represents a configuration in which fragment information is added to the UDP header in addition to the information of the destination IP address of the IP header that is absolutely required and the destination port number of the UDP header. Note that when the value that is 2 higher than LSB is not 1 (0b0000b0000), the fragment information is not added to the UDP header.
  • step S13 the generation unit 11 determines whether or not the operation unit 13 has been operated to instruct the end of the setting data setting process. If the end is not instructed, the process returns to step S11, The subsequent processing is repeated. In step S13, when the operation unit 13 is operated to instruct the end of the setting data setting process, the process ends.
  • HC_Type which is the compression type (header compression type) of the compressed IP header and the compressed UDP header stored in the setting data 11a, is set.
  • HC_Type which is a compression type of the compressed IP header and the compressed UDP header (header compression type)
  • the data structure recorded in the setting data 11a indicates the structure of the compressed IP header and the compressed UDP header generated when transmitting the IP packet to the generating unit 11.
  • FIG. It will be as shown in
  • the description on the first line in FIG. 12 indicates that HC_Type consisting of 8 bits is recorded in the compressed IP header as information indicating the compression type of the compressed IP header.
  • the description in the second to third lines in FIG. 12 is a transmission target of a 32-bit destination IP address (destination_IP_address) and a 16-bit destination port number (destination_port_number), which are absolutely essential information. It is instructed to read from the IP header and UDP header of a legitimate IP packet and record in the compressed IP header and the compressed UDP header.
  • the description in the 4th to 7th lines in FIG. 12 indicates that when the LSB of HC_Type is 1, a 32-bit source IP address (source_IP_address) and a 16-bit source port number (source_port_number) are transmitted. It is instructed to read from the IP header and UDP header of the target regular IP packet and record them in the compressed IP header and the compressed UDP header.
  • the description on the 8th to 12th lines in FIG. 12 is that when the value of the next position of the LSB of HC_Type is 1, a 16-bit identifier (Identification), a 3-bit flag (Flags), and a 13-bit Is read from the IP header of the regular IP packet to be transmitted, and recorded in the compressed IP header as fragment information.
  • the description in the 13th to 15th lines in FIG. 12 indicates that when the value above the LSB of HC_Type is 1, the checksum (UDP_CRC) is displayed for the regular IP packet to be transmitted. It instructs to read from the UDP header and record in the compressed UDP header.
  • the generation unit 11 reads out necessary information from the IP header and the UDP header of the regular IP packet to be transmitted based on the information of the setting data 11a having such a data structure, and compresses the compressed IP. Configure headers and compressed UDP headers.
  • step S31 the generation unit 11 waits for an IP packet to be supplied thereto, and acquires one IP packet (IP packet including a UDP packet) supplied thereto as an IP packet to be transmitted. The process proceeds to step S32.
  • step S32 the generation unit 11 reads the information of HC_Type and recognizes the compression type according to the description of the first line recorded in the setting data 11a described with reference to FIG.
  • step S33 the generation unit 11 acquires the destination IP address from the IP header of the transmission target IP packet and also acquires the destination port number from the UDP header of the transmission target IP packet, and the process proceeds to step S34. move on.
  • step S34 the generation unit 11 records a 32-bit destination IP address (Destination_IP_Address) in the compressed IP header according to the description in the second line recorded in the setting data 11a described with reference to FIG. That is, the generation unit 11 records the destination IP address (Destination_IP_Address) at the 10th to 13th bytes, for example, as shown in the IP header format of FIG.
  • step S35 the generation unit 11 records a 16-bit destination port number (Destination_port) in the compressed UDP header according to the description in the third line recorded in the setting data 11a described with reference to FIG. That is, the generation unit 11 records the destination port number (Destination_port) at the third and fourth bytes, for example, as shown in the compressed UDP header format of FIG.
  • step S36 the generation unit 11 reads the HC_Type recorded in the setting data 11a described with reference to FIG. 12, and records it in the compressed IP header. At this time, for example, in the case of IPv4, as illustrated in FIG. 14, the generation unit 11 records 1-byte HC_Type information in the first byte of the compressed IP header.
  • step S37 the generation unit 11 determines whether the LSB of HC_Type is 1 based on the description in the fourth line recorded in the setting data 11a described with reference to FIG. If there is, the process proceeds to step S38.
  • step S38 the generation unit 11 records a 32-bit transmission source IP address (Source_IP_address) in the compressed IP header based on the description in the fifth line recorded in the setting data 11a described with reference to FIG. To do. That is, the generation unit 11 records the source IP address (Source_IP_address) at the 6th to 9th bytes, for example, as shown in the IP header format of FIG.
  • step S39 the generation unit 11 records the 16-bit source port number (Source_port) in the compressed UDP header according to the description in the sixth line recorded in the setting data 11a described with reference to FIG. That is, the generation unit 11 records the transmission source port number (Source_port) in the first and second bytes, for example, as shown in the compressed UDP header format of FIG.
  • step S37 If the LSB of HC_Type is not 1 in step S37, the processes in steps S38 and S39 are skipped.
  • step S ⁇ b> 40 the generation unit 11 determines whether or not the value of the one place above the LSB of HC_Type is 1 based on the description of the eighth line recorded in the setting data 11 a described with reference to FIG. 12. If it is 1, the process proceeds to step S41.
  • step S41 the generation unit 11 determines a 16-bit identifier (Identification), a 3-bit flag (Flags) based on the descriptions in the 9th to 11th lines recorded in the setting data 11a described with reference to FIG. ) And a 13-bit fragment position (Fragment Offset) are recorded as fragment information. That is, for example, as shown in the IP header format of FIG. 14, the generation unit 11 has a 16-bit identifier (Identification), a 3-bit flag (Flags), and a 13-bit fragment position in the second to fifth bytes. Record (Fragment Offset).
  • step S40 when the value of the LSB of HC_Type that is higher than 1 is not 1, the process of step S41 is skipped.
  • step S42 the generation unit 11 determines whether or not the value of the LSB of HC_Type is 2 based on the description in the 13th row recorded in the setting data 11a described with reference to FIG. If it is 1, the process proceeds to step S43.
  • step S43 the generation unit 11 records an 8-bit checksum (UDP_CRC) in the UDP header according to the description in the 14th line recorded in the setting data 11a described with reference to FIG. That is, the generation unit 11 records a checksum at the fifth byte, for example, as shown in the UDP header format of FIG.
  • UDP_CRC 8-bit checksum
  • step S42 when the value of the upper 2 of the LSB of HC_Type is not 1, the process of step S43 is skipped.
  • step S44 the generation unit 11 adds the generated IP header.
  • step S45 the generation unit 11 adds the generated UDP header.
  • step S46 the generation unit 11 adds a UDP payload.
  • the transmission unit 12 transmits the IP packet using the compressed IP header and the compressed UDP header to the receiving device 20 via the transmission path 30.
  • the IP header can be composed of 13 bytes even if all options are included, that is, even if HC_Type is 0b0000 0111, the general header shown in FIG. It becomes possible to make 7 bytes smaller than the IPv4 format.
  • the source IP address and fragment information can be omitted, for example, all of them can be omitted, that is, when HC_Type is 0b0000 ⁇ ⁇ ⁇ 0000, the minimum can be 5 bytes.
  • HC_Type including all options is 0b0000 ⁇ ⁇ ⁇ ⁇ 0111
  • it can be 5 bytes smaller than 8 bytes shown in FIG. 5, and can be reduced by 3 bytes.
  • adding or omitting the transmission source port number and checksum it is possible to make 2 bytes at the minimum.
  • the receiving unit 21 receives the generic packet via the transmission path 30 and supplies the generic packet to the restoration unit 22, and the type information (Type) of the generic header is, for example, 011. It is assumed that the IP header and UDP header of the IP packet placed in are compressed, and the IP header is of the IPv4 compression type.
  • step S71 after waiting for one generic packet to be supplied from the receiving unit 21, the generic packet from the receiving unit 21 is acquired as a generic packet to be restored, and the process proceeds to step S72.
  • step S72 the restoration unit 22 recognizes the value represented by the length information of the generic header, which is a normal header, as the length of the generic payload, and the process proceeds to step S73.
  • step S73 the restoration unit 22 restores the IP packet length and the UDP packet length (size) from the length of the generic payload recognized in step S72, and arranges (includes) them in the IP header and the UDP header, respectively. (Set), the process proceeds to step S74.
  • step S74 the restoration unit 22 acquires the destination IP address (Destination IP Address) from the compressed IP header arranged at the head of the generic payload, restores it, and places it in the regular IP header.
  • the destination IP address (Destination IP Address)
  • step S75 the restoration unit 22 acquires the destination port number (Destination Port) from the compressed UDP header, restores it, and places it in the regular UDP header.
  • Destination Port Destination Port
  • step S76 the restoration unit 22 reads HC_Type from the compressed IP header.
  • step S77 the restoration unit 22 determines whether or not the LSB of HC_Type is 1, that is, whether or not information on the source IP address and source port number is registered. In step S77, when the LSB of HC_Type is 1, the process proceeds to step S78.
  • step S78 the restoration unit 22 reads the source IP address recorded in the compressed IP header, restores it, and places it in the regular IP header.
  • step S79 the restoration unit 22 reads the source port number information from the compressed UDP header, restores it, and places it in the regular UDP header.
  • step S77 if the LSB of HC_Type is 1 in step S77, the process proceeds to step S80.
  • step S80 the restoration unit 22 sets the source IP address and source port number used at a predetermined frequency in association with the destination IP address and destination port number of the IP packet to be transmitted, respectively, as a regular IP header. , And place in the UDP header. That is, the restoration unit 22 records the source IP address and source port recorded in association with the destination IP address and destination port number of the IP packet recorded in the above-described full IP packet (Full packet).
  • Full IP packet Full IP packet
  • step S81 the restoration unit 22 determines whether or not the value of the HC_Type LSB that is one place above is 1, that is, whether or not fragment information is registered. In step S81, when the value of the LSB of HC_Type that is one place above is 1, the process proceeds to step S82.
  • step S82 the restoration unit 22 reads the information of the fragment that is transmitted and registered in the compressed IP header and includes the identifier (Identification), the flag (Flags), and the fragment position (Fragment Offset) and restores the information. And place it in a regular IP header.
  • step S81 when the value on the LSB of HC_Type is not 1, the process proceeds to step S83.
  • step S83 the restoration unit 22 uses fragment information including a predetermined identifier (Identification), a flag (Flags), and a fragment position (Fragment ⁇ ⁇ Offset) as a restoration result.
  • step S84 the restoration unit 22 determines whether the value of the LSB of HC_Type 2 is 1, that is, whether a checksum is registered. In step S84, if the value of the HC_Type LSB above 2 is 1, the process proceeds to step S85.
  • step S85 the restoration unit 22 reads and restores the transmitted checksum information registered in the compressed IP header.
  • step S84 when the value of the upper 2 of LSB of HC_Type is not 1, the process proceeds to step S86.
  • step S86 the restoration unit 22 restores the checksum by calculation and places it in the regular IP header for use.
  • step S87 the restoration unit 22 restores the IP packet using default values for information other than the information obtained as described above.
  • the compressed IP header and the compressed UDP header by selectively switching the presence or absence of the checksum.
  • the destination IP address and the destination port number can be included in the compressed IP header and the compressed UDP header.
  • the fragment information can be further included in the compressed UDP header.
  • the IP packet can be transmitted by switching the configuration of the compressed IP header and the compressed UDP header according to the service form of the IP packet, the overhead size in the compressed IP header and the compressed UDP header is controlled. Thus, it is possible to efficiently compress and transmit the IP packet according to the service form of the IP packet.
  • the transmission device 10 when broadcast station information is transmitted by an upper layer, and the reception device 20 can recognize the transmission source IP address and the transmission source port number from the information of the broadcast station.
  • the transmission source IP address of the IP header and the transmission source port number of the UDP header a transmission source IP address and a transmission source port number recognized from information on the broadcasting station can be used.
  • the transmission source IP address and the transmission source port number may be fixed values as described above.
  • IP header of the IP packet is IPv4
  • IP header may be IPv6.
  • the data structure recorded in the setting data 11a is, for example, IPv6, the configuration is as shown in FIG.
  • the description on the first line in FIG. 17 indicates that HC_Type consisting of 8 bits is recorded in the compressed IP header as information indicating the compression type of the compressed IP header.
  • the description in the second to third lines in FIG. 17 describes a 128-bit destination IP address (destination_IP_address) and a 16-bit destination port number (destination_port_number), which are essential information, as a regular IP to be transmitted. It is instructed to read from the IP header and UDP header of the packet and to record in the compressed IP header and the compressed UDP header.
  • the transmission source IP address (source_IP_address) of 16 bits and the transmission source port number (source_port_number) of 16 bits are set as transmission targets. It is instructed to read from the IP header and UDP header of the regular IP packet and record it in the compressed IP header and the compressed UDP header.
  • the description in the 8th to 10th lines in FIG. 17 indicates that when the value next to the LSB of HC_Type is 1, the 64-bit fragment information is represented in the IP header of the regular IP packet to be transmitted. It is instructed to read from the extension header and record as the extension header of the compressed IP header.
  • the checksum (UDP_CRC) is used as the UDP header of the regular IP packet to be transmitted. To record in the compressed UDP header.
  • the generation unit 11 reads out necessary information from the IP header and the UDP header based on the data structure of the setting data 11a set as described above, and configures the compressed IP header and the compressed UDP header.
  • the IPv6 compressed IP header format includes HC_Type, destination IP address (Destination IP Address), destination port number (Destination Port Number), and fragment information (Fragment).
  • a 128-bit destination IP address (Destination IP address) is, for example, as shown in FIG. , 18th to 34th bytes are recorded.
  • the 128-bit transmission source IP address (Source IP address) is shown in the format of the IP header of FIG. 18, for example. As shown, the second to 17th bytes are recorded.
  • the 64-bit fragment extension header is 35 to 35 as shown in the IP header format of FIG. Recorded at the 43rd byte.
  • the compressed IP header of FIG. 18 can be configured with 37 bytes even if all options are included, that is, even if the HC_Type is 0b0000110111 and the fragment extension header is included. 7 bytes can be reduced compared to the 44-byte configuration in which an 8-byte extension header is added to the general IPv6 format shown. Furthermore, since the source IP address and the information of the fragment extension header can be omitted, for example, all can be omitted, that is, when HC_Type is 0b0000b0000, the minimum can be 17 bytes.
  • HC_Type is composed of 1 byte.
  • information indicating whether or not to add a transmission source IP address and a transmission source port number to the header It is only necessary to be able to indicate the presence or absence of addition of three types of information: information indicating whether to add fragment information and information indicating whether to add a checksum. Therefore, if HC_Type has 3 bits, it is possible to express the compression type. For this reason, by configuring HC_Type with 3 bits, it is possible to further reduce the overhead by 5 bits from the IP header.
  • FIG. 19 shows a configuration example of an embodiment of a computer in which a program for executing the series of processes described above is installed.
  • the program can be recorded in advance in a hard disk 105 or a ROM 103 as a recording medium built in the computer.
  • the program can be stored (recorded) in the removable recording medium 111.
  • a removable recording medium 111 can be provided as so-called package software.
  • examples of the removable recording medium 111 include a flexible disk, a CD-ROM (Compact Disc Read Only Memory), an MO (Magneto Optical) disc, a DVD (Digital Versatile Disc), a magnetic disc, and a semiconductor memory.
  • the program can be installed on the computer from the removable recording medium 111 as described above, or can be downloaded to the computer via the communication network or the broadcast network and installed on the built-in hard disk 105. That is, the program is transferred from a download site to a computer wirelessly via a digital satellite broadcasting artificial satellite, or wired to a computer via a network such as a LAN (Local Area Network) or the Internet. be able to.
  • a network such as a LAN (Local Area Network) or the Internet.
  • the computer includes a CPU (Central Processing Unit) 102, and an input / output interface 110 is connected to the CPU 102 via the bus 101.
  • CPU Central Processing Unit
  • the CPU 102 executes a program stored in a ROM (Read Only Memory) 103 accordingly. .
  • the CPU 102 loads a program stored in the hard disk 105 into a RAM (Random Access Memory) 104 and executes it.
  • the CPU 102 performs processing according to the flowchart described above or processing performed by the configuration of the block diagram described above. Then, the CPU 102 outputs the processing result as necessary, for example, via the input / output interface 110, from the output unit 106, transmitted from the communication unit 108, and further recorded in the hard disk 105.
  • the input unit 107 includes a keyboard, a mouse, a microphone, and the like.
  • the output unit 106 includes an LCD (Liquid Crystal Display), a speaker, and the like.
  • the processing performed by the computer according to the program does not necessarily have to be performed in chronological order 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 individually (for example, parallel processing or object processing).
  • program may be processed by one computer (processor), or may be distributedly processed by a plurality of computers.
  • the system means a set of a plurality of components (devices, modules (parts), etc.), and it does not matter whether all the components are in the same housing. Accordingly, a plurality of devices housed in separate housings and connected via a network and a single device housing a plurality of modules in one housing are all systems. .
  • each step described in the above-described flowchart can be executed by one device or can be shared by a plurality of devices.
  • the plurality of processes included in the one step can be executed by being shared by a plurality of apparatuses in addition to being executed by one apparatus.
  • this technology can be applied not only to ATSC, but also to broadcasts other than ATSC, for example, broadcast standards such as DVB (Digital Video Broadcasting) and ISDB (Integrated Services Digital Broadcasting).
  • broadcast standards such as DVB (Digital Video Broadcasting) and ISDB (Integrated Services Digital Broadcasting).
  • this technique can take the following structures.
  • Type information indicating whether an IP (Internet Protocol) header and a UDP (User Datagram Protocol) header are compressed, A header composed of length information indicating the length of a transmission packet for transmitting an IP packet including a UDP packet, and A destination IP address of the IP packet, a destination port number of the UDP packet, Transmission information specifying the predetermined information included in the IP header, and information to be transmitted among the predetermined information included in the UDP header; Based on the transmission identification information, the information specified as information to be transmitted among the predetermined information included in the IP header and the predetermined information included in the UDP header; A generation unit that generates the transmission packet configured by a payload configured by the payload of the UDP packet; and A transmission device comprising: a transmission unit that transmits the transmission packet.
  • the predetermined information included in the IP header includes a destination IP address and fragment information
  • the transmission specific information is: First specifying information indicating whether to specify the destination IP address and the destination port number as information to be transmitted; Second specifying information indicating whether to specify the fragment information as information to be transmitted; The transmission device according to ⁇ 2>, further including third specifying information indicating whether the checksum information is specified as information to be transmitted.
  • a storage unit that stores setting data for setting the transmission specific information;
  • the operation unit further edits the setting data stored in the storage unit based on an operation signal corresponding to a user operation,
  • the generation unit generates the transmission specific information based on the setting data, and based on the transmission specific information, the predetermined information included in the IP header and the predetermined information included in the UDP header.
  • the information specified as the information to be transmitted, the destination IP address of the IP packet, and the destination port number of the UDP packet are used to generate the IP header and the UDP header, and the generated The transmission device according to ⁇ 1>, wherein the transmission packet is generated using an IP header and the UDP header.
  • IP Internet Protocol
  • UDP User Datagram Protocol
  • the restoration unit Based on the transmission identification information, the information specified as information to be transmitted among the predetermined information included in the IP header and the predetermined information included in the UDP header is restored, Based on the transmission specifying information, information that is not specified as information to be transmitted among predetermined information included in the IP header and predetermined information included in the UDP header is set to a predetermined fixed value. Restore, The destination IP address and the destination port number are restored as the destination IP address included in the IP header and the destination port number included in the UDP header, respectively.
  • the receiving device according to ⁇ 6>, wherein the length information of the IP packet included in the IP header and the length information of the UDP packet included in the UDP packet are restored from the length information.
  • the predetermined information included in the IP header includes a destination IP address and fragment information
  • the transmission specific information is: First specifying information indicating whether to specify the destination IP address and the destination port number as information to be transmitted; Second specifying information indicating whether to specify the fragment information as information to be transmitted; The receiving device according to ⁇ 8>, further including third specifying information indicating whether the checksum information is specified as information to be transmitted.
  • IP Internet Protocol
  • UDP User Datagram Protocol

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente technique concerne un appareil d'émission, un procédé d'émission, un appareil de réception et un procédé de réception, par lesquels des paquets IP peuvent être efficacement diffusés et rapidement traités. Un paquet de transport comprenant un paquet IP est émis et reçu. Sont comprises des premières informations de détermination représentatives de la détermination d'une adresse IP de destination et d'un numéro de port de destination en tant qu'informations à transporter, des deuxièmes informations de détermination représentatives de la détermination d'informations fragmentaires en tant qu'informations à transporter, et des troisièmes informations de détermination représentatives de la détermination d'informations de total de contrôle en tant qu'informations à transporter, et un en-tête IP compressé et un en-tête UDP compressé qui sont constitués uniquement par des informations déterminées comme pouvant être configurées. Des informations qui ne sont pas transportées sont rétablies en tant que valeur fixe prédéterminée. La présente technique peut être appliquée, par exemple, à la diffusion de paquets IP.
PCT/JP2016/061522 2015-04-24 2016-04-08 Appareil d'émission, procédé d'émission, appareil de réception, et procédé de réception WO2016171008A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2015-089693 2015-04-24
JP2015089693 2015-04-24

Publications (1)

Publication Number Publication Date
WO2016171008A1 true WO2016171008A1 (fr) 2016-10-27

Family

ID=57144094

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2016/061522 WO2016171008A1 (fr) 2015-04-24 2016-04-08 Appareil d'émission, procédé d'émission, appareil de réception, et procédé de réception

Country Status (1)

Country Link
WO (1) WO2016171008A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112333850A (zh) * 2020-11-24 2021-02-05 展讯半导体(成都)有限公司 防止下行失步方法、通信装置和可读存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6032197A (en) * 1997-09-25 2000-02-29 Microsoft Corporation Data packet header compression for unidirectional transmission
US20130039278A1 (en) * 2010-05-03 2013-02-14 Nokia Corporation Protocol overhead reduction

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6032197A (en) * 1997-09-25 2000-02-29 Microsoft Corporation Data packet header compression for unidirectional transmission
US20130039278A1 (en) * 2010-05-03 2013-02-14 Nokia Corporation Protocol overhead reduction

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112333850A (zh) * 2020-11-24 2021-02-05 展讯半导体(成都)有限公司 防止下行失步方法、通信装置和可读存储介质
CN112333850B (zh) * 2020-11-24 2022-08-16 展讯半导体(成都)有限公司 防止下行失步方法、通信装置和可读存储介质

Similar Documents

Publication Publication Date Title
US10367921B2 (en) Transmission apparatus, transmission method, reception apparatus, and reception method
KR102616590B1 (ko) 송신 장치, 송신 방법, 수신 장치 및 수신 방법
US6711164B1 (en) Method and apparatus for performing IP-ID regeneration to improve header compression efficiency
KR101835340B1 (ko) 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법
US20190037055A1 (en) Transmission apparatus, transmission method, reception apparatus, and reception method
KR102117445B1 (ko) 패킷 헤더 압축을 위한 방법 및 장치
KR102533481B1 (ko) 송신 장치, 송신 방법, 수신 장치, 및 수신 방법
US20170134763A1 (en) Method for compressing transmission packet in ip-based broadcast network
US8228909B2 (en) Method of compressing and restoring IP packets transmitted through broadcast network
CN109526030B (zh) 报文的处理方法、装置和设备
EP2472813A1 (fr) Procédé et dispositif de compression et de décompression de paquets à protocole de datagramme
WO2014061487A1 (fr) Dispositif de traitement de données, méthode de traitement de données et programme
JP5011239B2 (ja) 放送用パケット生成装置、データ補完サーバ、受信端末、および、それらのプログラム
WO2016171008A1 (fr) Appareil d'émission, procédé d'émission, appareil de réception, et procédé de réception
KR102001014B1 (ko) 차세대 지상파 방송 네트워크 장치, 송신 장치 및 패킷 전송방법
KR20180037307A (ko) 멀티미디어 시스템에서 신호 송수신 장치 및 방법
JP5544863B2 (ja) 受信装置、受信方法及び受信プログラム
US10135895B2 (en) Method and apparatus for repeatedly transmitting segment based broadcasting contents
JP5142667B2 (ja) 変換装置、ｔｓパケット変換方法及びプログラム
JP6201840B2 (ja) 送信装置、送信方法、受信装置、及び、受信方法
WO2017047423A1 (fr) Dispositif d'émission, dispositif de réception et procédé de traitement de données
JP2018160752A (ja) 送信装置、受信装置及びプログラム
KR100734377B1 (ko) 방송 신호 복호 방법
JP2004007171A (ja) 伝送装置、受信端末およびプログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16783029

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16783029

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP