WO2021151376A1

WO2021151376A1 - Reception/transmission method and reception/transmission apparatus

Info

Publication number: WO2021151376A1
Application number: PCT/CN2021/073818
Authority: WO
Inventors: 廣田敦志
Original assignee: 海信视像科技股份有限公司; 东芝视频解决方案株式会社
Priority date: 2020-01-31
Filing date: 2021-01-26
Publication date: 2021-08-05
Also published as: CN113475088A

Abstract

The present invention provides a reception/transmission method and a reception/transmission apparatus, used for reducing partial TLV stream reception problems. A sending apparatus possesses a TLV stream extraction mechanism, a UDP/IP packet extraction mechanism, an IP/UDP packet separation mechanism, an empty packet generation mechanism, and a partial TLV stream generation mechanism; the TLV stream extraction mechanism receives a MMT/TLV-based broadcast signal and obtains a TLV stream containing a UDP/IP packet; the UDP/IP packet extraction mechanism extracts the UDP/IP packet from the TLV stream; the IP/UDP packet separation mechanism separates the UDP/IP packet into a first UDP/IP packet that includes designated data and a second UDP/IP packet that does not include designated data; the empty packet generation mechanism deletes a UDP/IP valid payload from the second UDP/IP packet, thereby generating a UDP/IP empty packet only having a UDP/IP header; the partial TLV stream generation mechanism generates a partial TLV stream at least including the first UDP/IP packet and the UDP/IP empty packet; a partial TLV stream sending mechanism sends the partial TLV stream to an external apparatus.

Description

Transceiving method and transceiving device

This application requires the priority of a Japanese patent application filed with the Japanese Patent Office, application number 2020-015883, and the title of the invention "transmitting method, transmitting and receiving device" on January 31, 2020, and a Japanese patent filed on January 31, 2020 Office, the application number is 2020-015884, and the title of the invention is "receiving method, receiving device" Japanese patent application priority, the entire content of which is incorporated into this application by reference.

Technical field

The embodiments of the present application relate to a transceiving method and a transceiving device.

Background technique

In the specifications of advanced broadband digital satellite broadcasting, the UDP/IP packets used for transmission of MMTP packets that store resources such as images, sounds, captions, and MMT-SI constituting the service are header compressed and transmitted. The television receiving device 1 selects the assets of the service selected from the received broadcast signals and the necessary MMT-SI, generates a partial TLV stream, and outputs it to an external device. In addition, the television receiving device 1 selects the assets of the service selected from the received broadcast signals and the necessary MMT-SI, and records (records) in the form of a TLV stream to a recording and playback device such as a hard disk.

Prior technical literature

Non-patent literature

Non-Patent Document 1: ARIBSTD-B392.3 "Regulations on the Operation of Advanced Broadband Digital Satellite Broadcasting"

Non-Patent Document 2: ARIBSTD-B631.9 Edition "Standard Specification for Receiving Devices for Advanced Broadband Digital Satellite Broadcasting"

Summary of the invention

In the partial TLV stream created by editing a part of the TLV stream of the initial broadcast signal, IP information other than the UDP/IP packet storing the resources of the selected service and the necessary MMT-SI is lacking. Especially in the case where the header of the UDP/IP packet stored in the discarded TLV packet is a full header (uncompressed header), when receiving and playing part of the TLV stream, it may be displayed or displayed in the playback of the service. Delays and interruptions occurred in the prompting of related information.

In addition, the recording data input to the recording and playback device may lack IP information other than the selected recording data. Especially when the header of the UDP/IP packet stored in the discarded TLV packet is a full header (uncompressed header), when the recording data is received and played, it is displayed in the playback of the service, and the related information is displayed. Sometimes there may be delays and interruptions.

The technical problem to be solved by this application is to provide a transceiving method and a transceiving device for reducing the problem of receiving part of the TLV stream.

Another technical problem to be solved by the present application is to provide a receiving method and receiving device for reducing problems when recording broadcast signal data.

The sending device of an embodiment of the present application includes a TLV stream extraction mechanism, a UDP/IP packet extraction mechanism, an IP/UDP packet separation mechanism, an empty packet generation mechanism, and some TLV stream generation mechanisms. The TLV stream extraction mechanism receives based on the MMT/TLV method UDP/IP packet extraction mechanism extracts UDP/IP packets from the TLV flow; IP/UDP packet separation mechanism separates UDP/IP packets into designated data The first UDP/IP packet and the second UDP/IP packet that does not contain the specified data; the empty packet generator deletes the UDP/IP payload from the second UDP/IP packet, thereby generating a UDP/IP packet with only the UDP/IP header. IP empty packets; part of the TLV flow generation mechanism includes at least the first UDP/IP packet and UDP/IP empty packets to generate part of the TLV flow in the mainland; some TLV flow sending mechanisms send part of the TLV flow to external devices.

In addition, the receiving device of an embodiment of the present application includes a TLV stream extraction mechanism, a UDP/IP packet extraction mechanism, an IP/UDP packet separation mechanism, an empty packet generation mechanism, and a recording mechanism. The TLV stream extraction mechanism receives MMT/TLV-based Broadcast the signal and obtain the TLV stream storing the UDP/IP packet, the UDP/IP packet extraction mechanism extracts the UDP/IP packet from the TLV stream, and the IP/UDP packet separation mechanism separates the UDP/IP packet into data containing the specified recording. The first UDP/IP packet inside and the second UDP/IP packet that does not contain the specified recorded data. The empty packet generating mechanism deletes the UDP/IP payload from the second UDP/IP packet, thereby generating a UDP/IP header that contains the UDP/IP header. For the UDP/IP empty packets in the internal, the recording organization includes at least the first UDP/IP packet and UDP/IP empty packets to record in the Mainland.

Description of the drawings

FIG. 1 is a diagram showing an example of a television receiver corresponding to digital broadcasting based on the MMT/TLV method and an electronic device that receives partial TLV streams according to an embodiment;

2 is a block diagram showing an example of the functional structure of a television receiving device corresponding to digital broadcasting based on the MMT/TLV method according to the embodiment;

3 is a block diagram showing an example of the functional configuration of a TLV/MMT separation processing unit in the television receiving device of the embodiment;

4A is a diagram showing an example of a multiplexing structure of TLV streams processed by the television receiving device of the embodiment;

4B is a diagram showing an example of the configuration of each packet stored in the TLV stream of the embodiment;

4C is a diagram showing an example of the header information of the UDP/IP packet stored in the TLV stream of the embodiment;

4D is a diagram showing another example of the structure of a null packet stored in a partial TLV stream of the embodiment;

5 is a block diagram showing an example of the functional configuration of a partial TLV stream generating unit in the television receiving device of the embodiment;

6A is a block diagram showing an example of the functional structure of an electronic device that receives a partial TLV stream according to the embodiment;

6B is a block diagram showing an example of the functional structure of a recording and playback unit that records and plays a part of the TLV stream according to the embodiment;

7 is a block diagram showing an example of the functional structure of the electronic device and the partial TLV stream processing unit of the recording and playback unit according to the embodiment;

8 is a flowchart showing an example of the processing operation of the TLV/MMT separation processing unit in the television receiving device of the embodiment;

9 is a flowchart showing an example of processing operations of the partial TLV generation unit in the television receiving device of the embodiment;

10A is a flowchart showing an example of processing operations of a partial TLV stream processing unit in the electronic device of the embodiment;

10B is a flowchart showing an example of processing operations of the partial TLV stream processing unit in the recording and playback unit of the embodiment;

FIG. 11A is a diagram showing the data structure of the AMT of the embodiment;

FIG. 11B is a diagram showing the IP version of the embodiment;

11C is a diagram showing the data structure of the PLT of the embodiment;

FIG. 11D is a diagram showing the reference relationship between PLT and MPT according to the embodiment.

Description of Reference Signs

1...TV receiver, 3A...interface, 11A...TLV stream extraction unit, 12A...TLV/MMT separation processing unit, 13...content output unit, 14...partial TLV stream generation unit, 15...presentation unit, 16...peripheral functions, 17...system bus, 18...remote control, 19...recording and playback unit, 21...interface unit, 22...partial TLV stream processing unit, 23...decoding processing unit, 24...content output unit, 25...prompt unit, 26...control unit , 120...TLV stream selection processing unit, 121...TLV packet separation unit, 122...TLV-SI extraction unit, 123...NTP extraction processing unit, 124...IP/UDP header decompression unit, 125...IP/UDP packet separation unit, 126 ...MMTP packet separation unit, 127...MMT-SI extraction unit, 128...service/resource selection control unit, 129...empty packet generation unit, 141...MMT-SI generation unit, 142...MMT-SI update unit, 143...MMTP packet Generation unit, 144...IP/UDP packet generation unit, 145...TLV packet generation unit, 146...TLV packet multiplexing unit, 147...TLV-SI generation unit, 221...TLV packet separation unit, 222...TLV-SI extraction unit, 223...NTP extraction processing unit, 224...IP/UDP header decompression unit, 225...IP/UDP packet separation unit, 226...MMTP packet separation unit, 227...MMT-SI extraction unit, 2251...empty packet detection unit.

Detailed ways

Hereinafter, embodiments will be described with reference to the drawings.

Implementation

Fig. 1 shows the MMT/TLV-based method of the embodiment

A diagram of an example of a television receiver corresponding to a digital broadcast and an electronic device that receives part of the TLV stream.

The television receiving device 1 receives a broadcasting signal of digital broadcasting based on the MMT/TLV method, and obtains content transmitted by the broadcasting signal (or also described as a service). The

electronic devices

2A, 2B, 2C (when no special distinction is required, they are called electronic devices 2) have

interfaces

3A, 3B, and 3C that can communicate with the television receiving device 1, respectively (when no special distinction is needed, they are called As interface 3), the content sent through the broadcast signal is acquired through the interface 3, and the display output is performed. In addition, in the present embodiment, the number of electronic devices 2 is assumed to be three, but depending on the interface of the television receiver 1, it can be any number of one or more.

The electronic device 2 has the capability (resolution, frame rate, etc.) capable of using all or part of the content transmitted by the television receiving device 1. The electronic device 2 may be, for example, a tablet computer terminal, a monitor, a television receiving device, and the like. In addition, as long as it has an interface capable of communicating with the television receiver 1, the electronic device 2 may also be a smart phone.

The

interfaces

3A, 3B, and 3C (referred to as interface 3 if no special distinction is required) are interfaces for data communication between the television receiving device 1 and the electronic device 2, and may be wired or wireless. In addition, as the interface 3, a network conforming to DLNA (registered trademark) (Digital Living Network Alliance) or its extension method may also be used, so that the television receiving device 1 and the electronic device 2 can communicate.

FIG. 2 is a block diagram showing an example of the functional configuration of a television receiving device corresponding to digital broadcasting of the MMT/TLV method according to the embodiment.

The television receiver 1 receives a broadcast signal of digital broadcasting based on the MMT/TLV method, and presents the content transmitted by the broadcast signal to the user from a monitor and a speaker.

The TLV

stream extraction units

11A, 11B, and 11C (referred to as the TLV stream extraction unit 11 unless otherwise distinguished) include a tuner unit 111A, a demodulation unit 112A, a descrambling unit 113A, and a CAS module 114A, and receive broadcast signals , And output the TLV stream as digital data.

The tuner 111A extracts a signal of a desired frequency band (broadcast channel) from a broadcast signal received through a wired method such as an antenna not shown or through an optical line based on cable broadcast, and performs frequency conversion and the like as necessary, and It is output to the demodulation unit 112A. The demodulation unit 112A performs demodulation, error correction decoding, etc. on the input broadcast signal, and obtains and outputs digital data in the form of TLV (Type Length Value). The acquired digital data is usually encrypted based on scrambling, and the descrambler 113A descrambles the scrambled digital data (scrambling data) and outputs it as a TLV stream. The CAS module 114A holds a secret key and the like required when the descrambler 113A descrambles the scrambled data, and provides it to the descrambler 113A as needed.

The TLV/MMT

separation processing units

12A, 12B, and 12C (referred to as the TLV/MMT separation processing unit 12 unless otherwise distinguished) acquire various control signals and components from the TLV stream output by the TLV stream extraction unit 11, The coded asset data of the service (content) (hereinafter referred to as coded resource data) is output. The TLV/MMT separation processing unit 12 can also convert the input TLV stream into an IP/UDP stream, further into an MMT (MPEG Media Transport) stream, and separate it into coded resource data and SI (as control information data). Signaling Information: Signaling information) data. In addition, the TLV/MMT separation processing unit 12 may separate and output the time information data in the NTP format stored in the IP/UDP format from the TLV stream. In addition, the TLV/MMT separation processing unit 12 may also output the TLV packet (or the extracted TLV stream) extracted from the input TLV stream. The TLV/MMT

separation processing units

12A, 12B, and 12C respectively process at the same time, and the respective outputs (streams, packets) obtained can be respectively input to the content output unit 13, the partial TLV stream generation unit 14, etc., for example.

The content output unit 13 decodes the encoded resource data, and outputs content data such as sound, image, and text.

The sound decoding unit 131 decodes and plays the encoded sound data in the encoded resource data, and outputs sound content data. The image decoding unit 132 decodes and plays the encoded image data in the encoded resource data, and outputs the image content data.

In addition, the encoded character data in the encoded resource data is decoded and reproduced by a character decoding unit (not shown), and is output as character content data.

The output processing unit 133 adjusts the output time, display method, etc. of the image content data (may include audio content data, text content data, etc.), and outputs it. In addition, the output processing unit 133 may also obtain the NTP data (time information data) output by the TLV/MMT separation processing unit 12, and play a clock synchronization signal to use it for time control.

In addition to the encoded resource data, control data and various commands from the control unit 163 described later may be input to the various decoding units described above. The control data may also be control information related to the broadcast system, such as information related to broadcast programs, control information related to multiplexing of UDP/IP packets. Various decoding units may use SI data to select resource data of the program and content data designated by the control unit 163, and decode the selected resource data to obtain content data.

The partial TLV stream generation unit 14 extracts and edits the resource data and control information data that constitute the selected content (broadcast program) from the TVL stream and MMT stream separated and obtained in the TLV/MMT separation processing unit 12, and generates Part of the TLV stream.

The presentation unit 15 presents the content data output by the content output unit 13 as content to the user. The speaker unit 151 outputs audio content data, text content data, and the like as sounds. The display unit 152 is, for example, a monitor, and displays image content data, text content data, and the like.

The peripheral function 16 includes a user interface unit 161, an interface unit 162, and a control unit 163.

The user interface unit 161 is, for example, a switch, a button, or the like provided in the main body of the television receiver 1, the speaker unit 151, the display unit 152, and the like. The user can also perform various settings and adjustments, such as screen adjustment, volume adjustment, and channel selection, on the television receiving device 1 via the user interface unit 161.

The interface unit 162 is various interfaces between the television receiver 1 and the outside, and may include, for example, infrared communication, mouse, keyboard, Ethernet, DLNA (registered trademark), HDMI (registered trademark), Wifi (registered trademark), and Various wired and wireless communication interfaces such as 5th generation mobile communication (5G). The interface unit 162 includes a communication interface constituted by the interface 3. The interface unit 162 generates frame data corresponding to a predetermined communication protocol for the input digital data, and transmits it based on a medium such as wired or wireless. In addition, it demodulates a signal received through a wired or wireless medium to obtain digital data, and decomposes the frame data in accordance with the communication protocol to output the digital data. The interface unit 162 may also have a function of encrypting and decrypting digital data such as scrambling.

The control unit 163 may also control various functions inside the television receiver 1 based on control signals input from the user interface unit 161, the interface unit 162, and the like.

The system bus 17 is a data transmission path for data exchange between various functions in the television receiving device 1, and is, for example, a serial bus. In addition, the data interaction between various functions in the television receiving device 1 is not limited to the system bus 17, and may be other transmission paths.

The remote control 18 is a remote control attached to the television receiving device 1, and the user can use the remote control 18 to perform various operations on the television receiving device 1. For example, if the user makes an operation designation through the remote control 18, a control command is output from the remote control. The control command is received by the television receiver 1 via the infrared communication of the interface unit 162. The interface unit 162 outputs the received control command to the control unit 163, and the control unit 163 analyzes the received control command, extracts it as control information, and controls various functions in the television receiver 1 based on the control information.

The recording and playback unit 19 is, for example, a hard disk (HDD), and records data received and processed by the television receiver 1. In the recording and playback unit 19, the output of the TLV stream extraction unit 11, the TLV/MMT separation processing unit 12, the content output unit 13, and the partial TLV stream generation unit 14 can be input.

3 is a block diagram showing an example of the functional configuration of a TLV/MMT separation processing unit in the television receiving device of the embodiment.

The TLV/MMT separation processing unit 12 has the function of separating the TLV stream into IP/UDP packets, MMT packets, and into coded resource data and SI data as control information data, and therefore uses the relationship of each stream, packet, data, etc. To illustrate the functional structure.

4A is a diagram showing an example of the multiplexing structure of the TLV stream processed by the television receiving device of the embodiment, which complies with ARIB TR-B392.3 Edition (Volume 5), Volume 4, Advanced Broadband CS Digital Broadcasting SI Operation Regulations 13 chapter.

The display box 50 shows a transponder as a physical layer. The transponder is installed in the CS satellite (Communication Satellite), and outputs the broadcast wave signal of the advanced broadband CS digital broadcast.

The display box 51 shows the layer of the TLV stream sent by the transponder shown in the display box 50.

The display box 52 shows the layer of UDP/IP stored in the TLV stream shown in the display box 51.

The display box 53 shows the TLV-NIT (Network Information Table) stored in the TLV stream shown in the display box 51. TLV-NIT is a part of TLV-SI stored in the TLV stream. The TLV-NIT stores various transponders in the broadcast media, the physical structure of the TLV stream transmitted here, the designated service or which TLV stream the designated content belongs to, and other information used for location resolution of the TLV stream.

The display box 54 shows the AMT (Address Map Table) stored in the TLV stream shown in the display box 51. AMT is also a part of TLV-SI stored in the TLV stream. The AMT stores all the services in the TLV stream and transmits the IP data stream of the PLT (a collection of UDP/IP packets with the same IP protocol type, source and destination IP addresses, and source and destination UDP port numbers). ) IP information such as the source IP address.

The display box 55 shows the flow of UDP/IP packets dedicated to the NTP format transmitted through the layer of the UDP/IP flow shown in the display box 52. The part of the display frame 55 that overlaps the display frame 52 can also be regarded as the header of the UDP/IP packet (also referred to as the IP header in some cases). The display box 551 can also be regarded as the payload of the UDP/IP packet, and the NTP data is stored in the display box 551.

The display box 56 shows the layer of MMTP transmitted through the layer of the UDP/IP flow shown in the display box 52.

The display box 57 shows a UDP/IP stream (IP data stream) dedicated to SI data stored in the TLV stream shown in the display box 51. In particular, the part of the display frame 55 that overlaps the display frame 52 can also be regarded as the header of the UDP/IP packet (also referred to as the IP header in some cases). In addition, the part of the display frame 57 above the display frame 56 can also be regarded as data transmitted in the form of an MMTP packet as the payload of the UDP/IP packet. Stores and transmits control signal data common to all services in the TLV stream including PLT, that is, content (program).

The display frame 58A, the display frame 58B, and the display frame 58C (referred to as the display frame 58 unless otherwise distinguished) respectively show the UDP/IP stream (IP data stream) of each service stored in the TLV stream. . In particular, the part of the display frame 55 that overlaps the display frame 52 can also be regarded as the header of the UDP/IP packet (also referred to as an IP header in some cases). The upper part of the display frame 58 than the display frame 56 can also be regarded as data transmitted in the form of MMTP packets as the payload of the UDP/IP packet. The UDP/IP stream (IP data stream) of the display frame 58A, the display frame 58B, and the display frame 58C usually stores different services (service 1, service 2, service 3 in the figure), that is, different content (program ) Associated data. The IP information in the UDP/IP stream (IP data stream) in the display frame 58A, the display frame 58B, and the display frame 58C is different, especially the IP address of the respective transmission source is different.

The display box 59 shows the same UDP/IP flow as the display box 58, and particularly shows the UDP/IP flow shared by the service. For example, in the UDP/IP streams of display box 58A, display box 58B, and display box 58C, service 1, service 2, and service 3 are respectively sent, and in the UDP/IP stream of display box 59, service 1, service 2, and Data shared by all or part of service 3 (in the figure, subtitle superimposed MPU is shown). The IP information of the UDP/IP stream in the display frame 59, especially the IP address of the transmission source, is different from the IP address of the transmission source of the UDP/IP stream in the display frame 58A, 58B, and 58C.

Returning to FIG. 3, the functional structure of the TLV/MMT separation processing unit 12 will be described.

For example, when a plurality of TLV streams are transmitted on one transponder, the TLV stream selection processing unit 120 selects a TLV stream in which content (program) designated by the user is transmitted based on the data of TLV-NIT.

The TLV packet separation unit 121 separates the TLV stream output from the TLV stream selection processing unit 120 into TLV-SI data (display box 53, display box 54), and UDP/UDP/ which stores NTP data (display box 55) for each TLV packet. Three systems of IP packets and UDP/IP packets storing MMTP packets (display box 53, display box 54). The TLV packet separation unit 121 divides the TLV stream based on the packet identifier (identifier: packet_type) stored in the header of the TLV stream (or TLV header in some cases), which is not shown, in the TLV stream layer of the display box 51. Divided into 3 systems.

The TLV-SI extraction unit 122 extracts the TLV-NIT and AMT output by the TLV packet separation unit 121, and outputs them.

The NTP extraction processing unit 123 extracts NTP information from the UDP/IP packet in the display frame 55 output by the TLV packet separation unit 121, and outputs it. The extracted NTP information is used to broadcast on the receiver's system clock.

The IP header decompression unit 124 processes the IP header (corresponding to the display box 52) of the UDP/IP packet in the header compression method of the MMTP packet (display box 53, display box 54) output by the TLV packet separation unit 121. Specifically, there are two types of IP headers attached to MMTP packets: headers including IP information including IP addresses and port numbers (the lower part of Figure 4C, which is also referred to as full header in some cases); and The header that does not contain the IP information (the middle section of FIG. 4C, which is also called the compressed header in some cases). The full-head IP packet is specified to be transmitted at least once every 500 [msec]. The IP header decompression unit 124 uses the full header information received in the past for each UDP/IP packet (IP data stream) that has the same IP information, and converts the UDP/IP packet with a compressed header (sometimes also called To compress the UDP/IP packet), convert it into a full-head UDP/IP packet (also referred to as UDP/IP packet in some cases) and output. Alternatively, it is also possible to output the compressed UDP/IP packet as a series of UDP/IP streams for each IP data stream.

The IP/UDP packet separation unit 125 selects the UDP/IP stream (IP data stream) input from the IP header decompression unit 124, and separates the UDP/IP packet of the selected UDP/IP stream, thereby extracting the MMTP packet, and outputting the MMTP Packet flow (also called MMTP flow in some cases). In more detail, the IP/UDP packet separation unit 125 uses the CID included in the IP header to select a UDP/IP stream (IP data stream). In Figure 4A, the

display boxes

57, 58, 59 are transmitting MMTP streams. When the IP/UDP packet separation unit 125 selects to separate the UDP/IP packet, it may also use the IP information stored in the AMT, the IP information stored in the PLT, MPT, etc. obtained in the subsequent processing.

The IP/UDP packet separation unit 125 also outputs in the form of a TLV packet selected from the received TLV packets. The output TLV packet may be a TLV packet input to the IP/UDP header decompression unit 124 (a TLV packet in which a compressed IP packet that has not been converted into a full header is stored).

The MMTP packet separation unit 126 outputs control signal data and coded resource data based on the MMTP stream input from the IP/UDP packet separation unit 125. In FIG. 4A, the image MPU, sound MPU, subtitle MPU, application MPU, and subtitle superimposition MPU of the display frame 58 in the display frame 58 are equivalent to encoding resource data. In addition, the data other than the coded resource data of the display frame 58 and the data of the display frame 57 correspond to control signal data.

The MMT-SI extraction unit 127 extracts and outputs control information such as PLT and MPT based on MMT-SI, which is the control signal data input from the MMTP packet separation unit 126. In the PLT, the packet ID of the MMTP packet of the MPT corresponding to the full service (or content) transmission in the TLV stream (refer to the MMTP packet 63 in FIG. 4B) is stored, and the stored UDP/IP packet is further stored. The IP information, headed by the source IP address, is used to resolve the location of MPT transmission. In the MPT, information for location resolution for resource transmission, such as the packet ID of the MMTP for each resource constituting the service, is stored. The information stored in PLT and MPT may also be used in the IP/UDP packet separation unit 125. In addition, the MMT-SI extraction unit 127 extracts and outputs EPG information and the like from the MMT-SI.

The service/resource selection control unit 128 receives information from each function in the television receiving device 1, and outputs a control signal based on the received information, or extracts and outputs further detailed information. In addition, when the user has issued a control command to the television receiving device 1 via the remote control 18, the control unit 163 outputs the analyzed control command to the service/resource selection control unit 128. The service/resource selection control unit 128 outputs control signals and detailed information to each function in accordance with control commands.

The empty packet generating unit 129 generates and outputs a header compressed IP packet (called IP /UDP empty packet). In addition, it is also possible to extract and output only the UDP/IP header. An example of the structure of an empty packet is shown in FIG. 4D.

4B is a diagram showing an example of the structure of each packet stored in the TLV stream of the embodiment.

The TLV packet 61 is composed of a header and a payload, and fixed bits, packet_type and length as identifiers are stored in the header.

The UDP/IP packet 62 is composed of an IP/UDP header and an IP/UDP payload. In particular, the identifiers CID, SN, CID_header_type are stored in the IP/UDP header of the header compressed IP packet. The "partial IPv6 header/partial/UDP header" of the IP/UDP header contains header information used in the full header.

The MMTP packet 63 is composed of an MMTP header and an MMTP payload, and a packet_id as an identifier is stored in the MMTP header. The UDP/IP packet 62 is stored in the payload of the TLV packet 61, and the MMTP packet 63 is stored in the IP/UDP payload. Data such as resource data and SI data are stored in the MMTP payload.

4C is a diagram showing an example of the header information of the UDP/IP packet stored in the TLV stream of the embodiment, and is a detailed view of the header information of the UDP/IP packet 62 in FIG. 4B. As shown in Figure 4C, in the header compressed IP/UDP packet, the source IP address (source_address) and the destination IP address (destination_address) are configured in the IP/UDP header. In addition, for a normal IP/UDP packet, the source IP address (source_address) and the destination IP address (destination_address) are arranged in the IP header. NTP transmission does not apply IP header compression, and is usually transmitted at 33msec intervals. MMTP packet transmission uses IP header compression and is transmitted in full headers at 500msec intervals.

The source IP address (source_address) in the NTP dedicated IP data stream and the source address in the SI dedicated IP data stream use the same source IP address (source_address).

Specifically, in the NTP dedicated IP data flow and SI dedicated IP data flow in FIG. 4A, Src.add0 is used as the source IP address, and in the data flow of service 1 in FIG. 4A, the source IP address is used Src.add1, in the data stream of service 2, use Src.add2 as the source IP address, and in the data stream of service 3, use Src.add3 as the source IP address.

Therefore, based on the IP/UDP packet transmission source IP address (source_address) of the NTP dedicated IP data stream, the IP/UDP packet of the SI can be determined from the multiplexed stream.

4D is a diagram showing an example of the structure of a null packet stored in a partial TLV stream according to the embodiment.

Fig. 5 is a block diagram showing an example of a functional configuration of a partial TLV stream generating unit in the television receiving device of the embodiment.

The partial TLV stream generating unit 14 of the present embodiment generates not only coded resource data and MMT-SI control signal data, but also generates a TLV packet including NTP data, and outputs it as a partial TLV stream.

The MMT-SI generation unit 141 selects and extracts necessary information from the control information extracted and output by the MMT-SI extraction unit 127, and generates partial control information for the TLV stream based on the extracted information (in separate processing from the TLV/MMT When the control signal data of the section 12 is distinguished, it is referred to as partial control signal data). Specifically, for example, MH-SIT (Selection Information Table) and MH-DIT (Discontinuity Information Table) specified in ARIBSTD-B63. Generally, the control information for partial TLV streams is less than the control information extracted by the MMT-SI extraction unit 127 (that is, the control information for broadcast signal transmission).

The MMT-SI update unit 142 updates the contents of PLT or MPT stored in the payload of the UDP/IP packet (MMTP packet). The PLT included in the TLV stream (TLV stream transmitted by a broadcast signal) output by the TLV stream extraction unit 11 contains information about the full service. When sending as a partial TLV stream, it is necessary to update the PLT to the only included PLT. Information about the specified service. The same applies to MPT. When transmitting as a partial TLV stream, it is necessary to update the MPT to include only the information of the specified resource data. However, the IP header of the UDP/IP packet containing PLT or MPT is not updated.

The MMTP packet generation unit 143 uses the partial control signal data for the TLV stream input from the MMT-SI generation unit 141 as a payload, and adds predetermined MMTP header information to generate and output an MMTP packet.

The IP/UDP packet generation unit 144 outputs the UDP/IP packet input from the MMT-SI update unit 142 as it is. In addition, the MMTP packet input from the MMTP packet generation unit 143 is used as the payload, and the header information of the UDP/IP packet input from the MMT-SI update unit 142 is referred to, while the values of CID and SN are integrated, the IP header, UDP header to generate and output UDP/IP packets.

The UDP/IP packet and the IP/UDP empty packet output from the IP/UDP packet generating unit 144 are input to the TLV packet generating unit 145, and a TLV header is added to each to generate and output a TLV packet. In addition, the TLV packet storing the IP/UDP empty packet is output in the same order/time as the original IP data stream. However, the TLV packet header changes the payload length, so the value of the length field is updated, which is different from the original TLV header.

The TLV packet multiplexing unit 146 multiplexes TLV packets input from each function, and outputs it as a partial TLV stream. Specifically, a TLV packet containing NTP data, a TLV packet output by the TLV packet generating unit 145, and a TLV packet containing resource data are input to the TLV packet multiplexing unit 146 and output as a partial TLV stream. The partial TLV stream is transmitted from the interface unit 163 as a partial TLV stream signal in accordance with a predetermined communication method.

The TLV-SI generating unit 147 generates TLV-SI information in the mainland including the update information of the AMT and outputs it to the TLV packet multiplexing unit 146. However, in this embodiment, since TLV-SI information is not multiplexed in some TLV streams, this function may not be provided.

6A is a block diagram showing an example of the functional structure of an electronic device that receives a partial TLV stream according to the embodiment.

The electronic device 2 receives part of the TLV stream signal sent by the television receiver 1 through the interface unit 21. The interface unit 21 includes a communication interface constituted by the interface 3. The interface unit 21 extracts digital data from the received partial TLV stream signal and outputs it as a partial TLV stream. The interface unit 21 generates frame data corresponding to a predetermined communication protocol for the input digital data, and transmits it based on a medium such as wired or wireless. In addition, it demodulates signals received through wired, wireless and other media to obtain digital data, and decomposes the frame data corresponding to the communication protocol, and outputs the digital data. The interface unit 21 may also have encryption and decryption functions such as scrambling. The interface unit 21 in this embodiment can communicate with the interface unit 162 based on, for example, DLNA (registered trademark) or its extended method.

The partial TLV stream processing unit 22 processes the partial TLV stream input from the interface unit 21, and obtains and outputs coded resource data and SI data. The coded resource data is input to the decoding processing unit 23 together with the SI data, and converted into content data such as images, sounds, and texts. The converted content data is output to the content output unit 24. The content output unit 24 adjusts the output time, display method, etc. of the content data, and outputs to the presentation unit 25.

The presentation unit 25 is, for example, a signal display device (monitor), a speaker, etc., and outputs as images, audio, text, etc. based on the input content data.

The control unit 26 controls each function of the electronic device 2. For example, the control unit 26 performs connection establishment of external communication via various interfaces including the interface unit 21.

6B is a block diagram showing an example of a functional structure of a recording and playback unit that records and plays a partial TLV stream according to the embodiment.

The recording and playback unit 19 records (records) a part of the TLV stream, or plays a part of the TLV stream, wherein the part of the TLV stream is generated from the TLV stream included in the broadcast signal received by the television receiver 1. The recording unit 191 is, for example, a hard disk, and stores part of the TLV stream according to the control from the control unit 26.

The partial TLV stream processing unit 22 processes the partial TLV stream input from the recording unit 191, obtains and outputs coded resource data and SI data. The coded resource data is input to the content output unit 13 together with the SI data, and is converted into content data such as images, sounds, and texts by the audio decoding unit 131 and the image decoding unit 132. The converted content data is output to the output processing unit 133. The output processing unit 133 adjusts the output time, the display method, and the like with respect to the content data, and outputs to the presentation unit 15.

The control unit 26 controls each function of the recording and playback unit 19. For example, when the user wants to record the content of the broadcast signal in a partial TLV stream, if the user outputs a recording command signal from the remote control 18, the recording command signal is received by the interface part 162 and output to the control part 163. The control unit 163 analyzes the recording command signal, and sends the control signal of the recording command to the control unit 26. When the control unit 26 receives the control signal of the recording command, it receives the partial TLV stream from the partial TLV stream generation unit 14 and saves it in the recording unit 191. For example, when the user wants to play the content saved in the recording section 191 in the form of partial TLV, if the user outputs a play command signal from the remote control 18, the play command signal is received by the interface unit 162 and output to the control section 163. The control unit 163 analyzes the playback command signal, and sends the control signal of the playback command to the control unit 26. Upon receiving the control signal of the play command, the control unit 26 outputs the partial TLV stream of the recording unit 191 to the partial TLV stream processing unit 22. When the partial TLV stream processing unit 22 processes part of the TLV stream, the resource data is obtained, and the user can watch the content from the prompt unit 15 and the like.

In addition, in FIGS. 6A and 6B, data interaction (including control) can also be performed between functional modules that are not connected to the control unit 26.

7 is a block diagram showing an example of the functional configuration of the electronic device and the partial TLV stream processing unit of the recording and playback unit according to the embodiment.

The functional structure of part of the TLV stream processing unit 22 in FIG. 7 is explained using the data layer of the TLV stream in FIG. 4A.

The partial TLV stream processing unit 22 separates the partial TLV stream into IP/UDP packets and MMTP packets, and obtains and outputs coded resource data and SI data as control signal data. The function of the partial TLV stream processing unit 22 is the same as the function of the TLV/MMT separation processing unit 12 of the television receiver 1.

In the partial TLV stream processing unit of the electronic device, the TLV packet separation unit 221 separates the partial TLV stream input from the interface unit 21 into TLV-SI data for each TLV packet (equivalent to the display box 53, the display box in FIG. 4A). 54). Three systems of UDP/IP packets storing NTP data (equivalent to display box 55) and UDP/IP packets storing MMTP packets (equivalent to display box 56). In the partial TLV stream processing unit of the recording and playback unit, the TLV packet separation unit 221 separates the partial TLV stream input from the recording unit 191 into TLV-SI data for each TLV packet (equivalent to the display box 53 in FIG. 4A, display Box 54), UDP/IP packets storing NTP data (equivalent to display box 55), and UDP/IP packets storing MMTP packets (equivalent to display box 56) are three systems. The TLV packet separation unit 221 divides the partial TLV stream into three systems based on the packet identifier (identifier: packet_type) stored in the TLV header (refer to the TLV packet in FIG. 4B) in the TLV stream layer of the display box 51.

If the TLV-SI output by the TLV packet separation unit 221 exists, the TLV-SI extraction unit 222 may also extract and output necessary information from the TLV-SI. However, in this embodiment, because TLV-SI is not required, and usually TLV-SI is not included in part of the TLV stream, this function may not be available.

The NTP extraction processing unit 223 extracts and outputs NTP data from the UDP/IP packet in the display frame 55 output from the TLV packet separation unit 221. In addition, the NTP extraction processing unit 223 extracts the IP address of the transmission source of the NTP data from the UDP/IP packet in which the NTP data is stored.

The IP header decompression unit 224 processes the IP header (equivalent to the display box 52) of the UDP/IP packet in the header compression format of the MMTP packet (equivalent to the display box 56) output by the TLV packet separation unit 221. Specifically, there are two types of IP headers attached to MMTP packets: headers including IP information including IP addresses and port numbers (or full headers in some cases); and headers that do not include IP information ( In some cases, it is also called compression header). The IP header decompression unit 224 uses the information of all IP headers received in the past for each UDP/IP packet (IP data stream) with the same IP information to convert the UDP/IP packet with a compressed header (or in some cases) Called compressed UDP/IP packets) are converted into full-headed UDP/IP packets (also called UDP/IP packets in some cases), and output. Or, according to each IP data stream, the compressed UDP/IP packet can be output as a series of UDP/IP streams.

The IP/UDP packet separation unit 225 separates the UDP/IP packet input from the IP header decompression unit 224, extracts the MMTP packet, and outputs a stream of MMTP packets (also referred to as an MMTP stream in some cases). In more detail, the empty packet detection unit 2251 determines whether the UDP/IP packet input from the IP header decompression unit 224 is an empty packet. When the UDP/IP packet is a packet with only an IP header (UDP/IP empty packet), the empty packet detection unit 2251 skips the subsequent processing. That is, the empty packet detection unit 2251 does not output the UDP/IP packet to the MMTP packet separation unit 226 in the case of a UDP/IP empty packet. On the other hand, when it is not a UDP/IP empty packet, the empty packet detection unit 2251 outputs the UDP/IP packet to the MMTP packet separation unit 226 which is the subsequent process. The IP/UDP packet separation unit 225 in FIG. 7 uses the information stored in the PLT, MPT, etc. obtained in the subsequent processing when selecting to separate the UDP/IP packet.

The MMTP packet separation unit 226 outputs control signal data and coded resource data based on the MMTP stream input from the IP/UDP packet separation unit 225.

The MMT-SI extraction unit 227 extracts and outputs control information such as PLT and MPT from MMT-SI, which is the control signal data input from the MMTP packet separation unit 226. The information stored in PLT and MPT may also be used in the IP/UDP packet separation unit 225.

An operation example of the system of this embodiment will be described. 8 is a flowchart showing an example of the processing operation of the TLV/MMT separation processing unit in the television receiving device of the embodiment.

To specify a service (content) to be output as a partial TLV stream from the television receiving device 1, or to specify a service (content) to be recorded as a partial TLV stream in the TLV stream received from the television receiving device 1, the user passes The remote controller 18 performs a designated operation. The remote control 18 outputs a control command for specifying a service, and the interface unit 162 of the television receiver 1 receives the control command. The interface unit 162 outputs the received control command to the control unit 163, and the control unit 163 analyzes the control command to extract information (designated service information) of the service designated by the user, and outputs it to the service/resource selection control unit 128. The service/resource selection control unit 128 outputs the designated service information (service_id) to the TLV/MMT separation processing unit 12 (step S11). In the TLV/MMT separation processing unit 12, the TLV stream selection processing unit 120 selects the TLV stream storing the designated service based on the TLV-NIT extracted by the TLV-SI extraction unit 122 and the designated service information, and outputs it to the TLV packet separation Section 121 (Step S12).

The TLV packet separation unit 121 separates the TLV stream input from the TLV stream selection processing unit 120 into three systems based on the packet identifier (identifier: packet_type) stored in the header shown in the TLV packet 61 of FIG. 4B (step S13). Specifically, according to the different types of data stored in the payload of the TLV packet, it is separated into three types: TLV-SI data, UDP/IP packet storing NTP data, and header compressed UDP/IP packet storing MMTP packet. System, and input to the TLV-SI extraction unit 122, the NTP extraction processing unit 123, and the IP header decompression unit 124, respectively.

The TLV-SI extraction unit 122 extracts TLV-NIT data and AMT data, and outputs them to the service/resource selection control unit 128 (step S14). The NTP extraction processing unit 123 extracts the NTP data stored in the UDP/IP packet, and outputs it to the service/resource selection control unit 128 (step S15). At the same time, the NTP extraction processing unit 123 outputs the input TLV packet as it is (step S15). The TLV packet including the header compressed UDP/IP packet in which the MMTP packet is stored is input to the IP header decompression unit 124 and the IP/UDP packet separation unit 125 and processed (step S16). The IP/UDP packet separation unit 125 uses the CID of the IP header information of the input TLV packet (refer to UDP/IP packet 62 in FIG. 4B) and the IP information input from the service/resource selection control unit 128 to confirm the IP data flow (step S17). The correspondence between the input IP information and the CID can be judged by comparing with the IP information recorded in the full header. If it is not confirmed that the IP data stream is an IP data stream selected based on the IP information, the next TLV packet is confirmed (No in step S18, S13). If it is confirmed that the IP data stream is the IP data stream selected based on the IP information, the subsequent processing is performed (Yes in step S18). The TLV packet of the selected IP data stream is input to the MMTP packet separation unit 126, and the packet_id of the MMTP header is confirmed (step S19). The MMTP packet separation unit 126 confirms the packet_id, and when the selected MMT-SI is stored in the input TLV packet, that is, when the PLT, the MPT related to the service_id specified by the user, and the specified MMT-SI are stored Next, output the UDP/IP packet stored in the input TLV packet (Yes in step S20, S21). The MMTP packet separation unit 126 confirms the packet_id. If the selected MMT-SI is not stored in the input TLV packet, that is, if the MMT-SI related to the service_id specified by the user is not stored, confirm the input Whether the selected resource is stored in the TLV packet (No in S20, step S22). The MMTP packet separation unit 126 extracts the MPT of service_id that identifies the service selected by the user from the PLT of the MMT-SI extracted in step S20. The MMTP packet separation unit 126 can specify the resources constituting the service specified by the user based on the extracted information of the MPT. Among them, it is possible to appropriately select (for example, only images, sounds, subtitles, etc.) resources required by part of the TLV stream. The MMTP packet separation unit 126 confirms the MPT information of the MMT-SI extracted in step S20 and the packet_id of the input TLV packet, and if the selected resource is stored in the input TLV packet, that is, in the storage When there is a resource of service_id specified by the user, the input TLV packet is output (Yes in step S22, step S23). In step S23, the TLV packet output by the MMTP packet separation unit 126 is the TLV packet input to the IP header decompression unit 124. On the other hand, the MMTP packet separation unit 126 confirms the MPT information of the MMT-SI extracted in step S20 and the packet_id of the input TLV packet, and if the selected resource is not stored in the input TLV packet, The payload part of the UDP/IP packet stored in the TLV packet is eliminated, and an empty UDP/IP packet is generated and output (step S24). Here, the UDP/IP empty packet means that the UDP/IP header can be output as it is.

In addition, steps S18 to S20 of the above-mentioned flow are supplemented. First, in order to obtain PLT, determine the IP information of the SI dedicated IP data stream based on the information of the AMT and select the IP information. Since the packet_id of the PLT is fixed at 0x0000 (fixed value), the PLT can be extracted through the processing of the MMTP packet separation unit 126 and the MMT-SI extraction unit 127.

Next, based on the acquired PLT, the IP information of the IP data stream to be transmitted to the MPT of the service specified by the user is determined, and the IP information is selected. Since the packet_id of the MPT is also described in the PLT, the MPT can be extracted through the processing of the MMTP packet separation unit 126 and the MMT-SI extraction unit 127. In addition, because each resource constituting the service is also included in the same IP data stream, and each packet_id is also described in the MPT, the resource can be extracted through the processing of the MMTP packet separation unit 126.

In addition, as needed, refer to the MPT to determine the IP information of the service common IP data stream, and select the IP information. Since this IP information and packet_id are also described in the MPT, the resource can be extracted through the processing of the MMTP packet separation unit 126. The step S20 of the above-mentioned flow will be described in detail. The MMTP packet separation unit 126 extracts and outputs control signal data from the input TLV packet, UDP/IP header analysis information, and the like. The output control signal data is input to the MMT-SI extraction unit 127, and the MMT-SI extraction unit 127 receives from the service/resource selection control unit 128 IP information such as the IP address of the designated service source stored in the AMT, and based on the received Information to extract PLT. The MMT-SI extraction unit 127 outputs the extracted PLT to the service/resource selection control unit 128. Furthermore, the MMT-SI extraction unit 127 extracts MPT based on the extracted PLT. The step S22 of the above-mentioned flow will be described in detail. The MMT-SI extraction unit 127 outputs the extracted MPT to the service/resource selection control unit 128. The MMTP packet separation unit 126 extracts encoded resource data from the input MMTP packet (TLV packet) based on the extracted MPT.

FIG. 9 is a flowchart showing an example of the processing operation of the partial TLV generation unit in the television receiving device of the embodiment.

In the partial TLV stream generating unit 14, the TLV packet of the resource data is input to the TLV packet multiplexing unit 146 (step S101A). In the partial TLV flow generating unit 14, the UDP/IP empty packet is output to the TLV packet generating unit 145 (step S101B). In the partial TLV stream generating unit 14, the control signal data is input to the MMT-SI generating unit 141. The MMT-SI generating unit 141 generates partial control signal data for output included in the partial TLV stream, namely MH-SIT, MH-DIT, etc., and outputs it to the MMTP packet generating unit 143 (step S102A). In addition, PLT and MPT in the control signal data input to the partial TLV stream generation unit 14 are input to the MMT-SI update unit 142, and the content is updated as necessary, and is output to the IP/UDP packet generation unit 144 (step S102B). The partial TLV stream generating unit 14 inputs the received TLV packet storing the NTP data to the TLV packet multiplexing unit 146 (step S103).

The MMTP packet generating unit 143 converts the input partial control signal data into an MMTP packet, and outputs it to the IP/UDP packet generating unit 144 (step S104). Here, when distinguishing from the MMTP packet input to the MMTP packet separation unit 126, the MMTP packet output in step S104 is referred to as a partial MMTP packet. The IP/UDP packet generation unit 144 adds an IP header, a UDP header, etc. to the input partial MMTP packet, generates a UDP/IP packet, and outputs the UDP/IP packet to the TLV packet generation unit 145 (step S105). In addition, in step S102B, the UDP/IP packet input from the MMT-SI update unit 142 is output as it is (step S105). When distinguishing from the UDP/IP packet input to the IP/UDP packet separation unit 125, the UDP/IP packet output in step S105 is referred to as a partial UDP/IP packet.

Input some UDP/IP packets including empty UDP/IP packets to the TLV packet generation unit 145. The TLV packet generation unit 145 takes part of the UDP/IP packets as the payload and adds the necessary TLV-SI and TLV headers, thereby A TLV package is generated (step S106). When distinguishing from the TLV packet input to the TLV packet separation unit 121, the TLV packet output in step S106 is referred to as a partial TLV packet. The generated part of the TLV packet, the resource data obtained in step S101A and step S103, and the TLV packet including NTP are input to the TLV packet multiplexing unit 146. The TLV packet multiplexing unit 146 outputs the input TLV packet as a partial TLV stream. From the interface unit 162 via the interface 3, a communication method such as DLNA (registered trademark) or an extended method is used to output the partial TLV stream as a partial TLV stream signal (step S107).

Next, the processing operation when recording and playing the partial TLV stream of the recording and playing unit 19 will be described. For example, when the user outputs a play command signal from the remote control 18, the control section 26 causes the partial TLV stream processing section 22 to acquire a partial TLV stream related to the content specified by the user from the recording section 191, and process the partial TLV stream.

10A is a flowchart showing an example of the processing operation of the partial TLV stream processing unit in the electronic device of the embodiment.

In the electronic device 2, part of the TLV stream signal output from the television receiver 1 is received through the interface unit 21. The interface unit 21 obtains the partial TLV stream by performing processing such as demodulation on the partial TLV stream signal. The obtained partial TLV stream is input to the TLV packet separation unit 221 of the partial TLV stream processing unit 22 (step S201). The TLV packet separation unit 221 divides the part of the TLV stream into a stream of TLV-SI data, UDP/IP packets of NTP data, and a stream of MMTP packets stored in the TLV header based on the packet identifier (identifier: packet_type) stored in the TLV header of the partial TLV stream. UDP/IP packet flow and other systems (step S202). The TLV-SI data is input to the TLV-SI extraction unit 222, and the TLV-SI extraction unit 222 extracts data necessary for processing part of the TLV stream. In addition, in the example of this embodiment, TLV-SI data is not included in some TLV streams.

The UDP/IP packet storing the NTP data is input to the NTP extraction processing unit 223, and the NTP extraction processing unit 223 extracts the NTP data (step S203). Simultaneously with step S203, the UDP/IP stream storing the MMTP packet is input to the IP header decompression unit 224 and converted into a full-head UDP/IP packet (step S204). In step S204, the same process is performed for the UDP/IP empty packet. The converted full-head UDP/IP packet is input to the IP/UDP packet separation unit 225, and the IP/UDP packet separation unit 225 extracts the MMTP packet and outputs it to the MMTP packet separation unit 226 (step S205). The MMTP packet separation unit 226 extracts the MMTP packet related to the SI data among the input MMTP packets, and inputs the extracted MMTP packet to the MMT-SI extraction unit 227 (step S206).

The MMT-SI extraction unit 227 extracts PLT from the input MMTP packet (step S207). In more detail, the PLT is extracted using the packet ID of the IP header given in the MMTP packet extracted in step S206.

Furthermore, the MMT-SI extraction unit 227 extracts the MPT based on the information described in the extracted PLT (step S208). The MMTP packet separation unit 226 extracts coded resource data from the input MMTP packet based on the extracted MPT (step S209). The extracted encoded resource data is output to the content output unit 24 (step S210).

The content output unit 24 decodes the encoded resource data, etc., and outputs content data such as sound, image, and text. The output content data is presented to the user as content such as images, sounds, texts, etc., from a speaker or a monitor in the presentation unit 25.

According to the above sequence, the electronic device 2 receives part of the TLV stream sent by the television receiver 1, and the user can use the electronic device 2 to watch the content.

In the embodiment, the television receiver 1 as the source device transmits only the header part of the UDP/IP packet (UDP/IP empty packet) in the partial TLV for data other than the selected service. The electronic device 2 skips the processing of the UDP/IP empty packets included in the part of the TLV stream, thereby being able to obtain the content data sent by the part of the TLV stream.

10B is a flowchart showing an example of the processing operation of the partial TLV stream processing unit of the recording and playback unit according to the embodiment.

Upon receiving the command to record the partial TLV stream (step S2001), the control unit 26 causes the recording and playback unit 19 to record the partial TLV stream output by the partial TLV stream generating unit 14 (step S2002).

When the control unit 26 receives a command to play the partial TLV stream recorded in the recording and playback unit 19 (step S200), the partial TLV stream input from the recording unit 191 to the partial TLV stream processing unit 22 is input to the partial TLV stream processing The TLV packet separation unit 221 of the unit 22 (step S201). The TLV packet separation unit 221 divides the part of the TLV stream into a stream of TLV-SI data, UDP/IP packets of NTP data, and a stream of MMTP packets stored in the TLV header based on the packet identifier (identifier: packet_type) stored in the TLV header of the partial TLV stream. UDP/IP packet flow and other systems (step S202). The TLV-SI data is input to the TLV-SI extraction unit 222, and the TLV-SI extraction unit 222 extracts data necessary for processing part of the TLV stream. In addition, in the example of this embodiment, TLV-SI data is not included in some TLV streams.

The UDP/IP packet storing the NTP data is input to the NTP extraction processing unit 223, and the NTP extraction processing unit 223 extracts the NTP data (step S203). Simultaneously with step S203, the UDP/IP stream storing the MMTP packet is input to the IP header decompression unit 224 and converted into a full-head UDP/IP packet (step S204). In step S204, the same process is performed for the UDP/IP empty packet. The converted full-head UDP/IP packet is input to the IP/UDP packet separation unit 225, and the IP/UDP packet separation unit 225 extracts the MMTP packet, and outputs it to the MMTP packet separation unit 226 (step S205). The MMTP packet separation unit 226 extracts the MMTP packet related to the SI data among the input MMTP packets, and inputs the extracted MMTP packet to the MMT-SI extraction unit 227 (step S206).

According to the above sequence, the recording and playback unit 19 can play a part of the TLV stream recorded in the recording unit 191. By playing part of the TLV stream, users can watch the content. In the embodiment, for data other than the specified service, only the header part of the UDP/IP packet (UDP/IP empty packet) is included in part of the TLV stream and recorded. The recording and playback unit 19 skips the processing of the UDP/IP empty packets included in the partial TLV stream, thereby being able to obtain the content data transmitted by the partial TLV stream. In addition, it is also possible to set whether to put IP null packets in part of the TLV stream.

In the specifications of advanced broadband digital satellite broadcasting, IP packets for transmission of MMTP packets that store images, sounds, subtitles, etc., and MMT-SI constituting the service are header-compressed and transmitted. The television receiving device 1 selects the service selected from the received broadcast signal and the necessary MMT-SI, generates a partial TLV stream, and outputs it to an external device or records it in the recording and playback unit 19. Therefore, generally, for some TLV streams, the data contained in the broadcast signal is lacking. In particular, the information contained in the header of the UDP/IP packet is lacking, so there is a problem that the continuity of the UDP/IP packet (set by the SN field) is destroyed. In addition, for full-head UDP/IP packets, the original transmission frequency is low, and there may be problems if they are not included in part of the TLV stream. For example, in the electronic device 2 or the recording and playback unit 19, when receiving and playing part of the TLV stream, there may be delays or interruptions in the playback and display of the service and the prompting of related information. At present, although this problem has not been surfaced, it is considered that problems will occur due to higher functions, multi-functionalization, and larger capacity in the future. Therefore, it is hoped to deal with it as a mechanism. According to the embodiment of this application, it is possible to prevent it from occurring. The sending and receiving or recording and playback of part of the TLV stream in the above-mentioned problem.

In addition, in this embodiment, an example applied to the standardized TLV stream of the advanced broadband CS digital broadcasting shown in FIG. 4B is shown, but it can also be applied to ARIB TR-B39 version 2.3 (third volume). The fourth part of the Advanced Broadband BS Digital Broadcasting SI Application Regulations Chapter 13 is based on the Advanced Broadband BS Digital Broadcasting. Different from the case of advanced broadband CS digital broadcasting, in the case of advanced broadband BS digital broadcasting, multiple TLV streams are output from the transponder. Each TLV stream contains TLV-SI data (AMT, TLV-NIT) and stores NTP UDP/IP packets, UDP/IP packets storing MMTP packets. In the case of advanced broadband CS digital broadcasting, there is a TLV-NIT, AMT, and NTP dedicated IP data stream respectively in a TLV stream. MMTP packet transmission is used for the SI dedicated IP data stream, and multiple services (equivalent to Figure 4A The display frames 58A, 58B, 58C) respectively constitute different IP data streams. On the other hand, in the case of advanced broadband BS digital broadcasting, there is still a TLV-NIT, AMT, and NTP dedicated IP data stream in a TLV stream, but for MMTP transmission, even if there are multiple services, all Consists of an IP data stream. Such multiple TLV streams are output from one transponder. In this case, when a service is selected from the TLV stream of the broadcast signal and a partial TLV stream is generated, compared with the case of the data structure shown in FIG. 4A, UDP/ in the partial TLV stream frequently occurs. The lack of IP packets. Therefore, in the case of a TLV stream structure such as an advanced broadband BS digital broadcast, if the embodiments of the present application are used, the problems caused by the lack of UDP/IP packets can be further reduced.

In this embodiment, an example is shown in which a partial TLV stream includes a UDP/IP empty packet and is recorded in the recording and playback unit 19, but the recording format is not limited to a strict partial TLV stream format. For example, in normal recording, when the selected broadcast program (service) is recorded in the recording and playback unit 19, the IP header of the UDP/IP packet storing the content data of the unselected program is recorded to the recording and playback unit 19 at the same time. In the section 19, by this, it is possible to obtain the same effect as in the present embodiment. In addition, it is also possible to output data storing content data recorded in the above-mentioned normal recording as a partial TLV stream to an external device.

In addition, according to this embodiment, the TLV stream output by the broadcasted TLV stream extraction unit 11 is recorded in the recording and playback unit 19 as it is, and then a part of the TLV stream including empty packets is generated at any time (not real-time), It can be recorded separately as part of the TLV stream. For example, all TLV streams received by the television receiver 1 are recorded (referred to as all recording). When the television receiving device 1 receives the designation from the user's remote control 18, among all the TLV streams recorded in the recording and playback unit 19, the TLV stream of the program designated by the user is input from the recording and playback unit 19 to the TLV/MMT separation process Department 12. According to the flowchart of FIG. 8, the data output from the TLV/MMT separation processing unit 12 is input to the partial TLV stream generating unit 14, so that a partial TLV stream including IP null packets can be generated for the content data of the program specified by the user. The generated part of the TLV stream can be recorded again in the recording and playback unit 19 (dubbing function). In addition, by combining the functions of the examples shown above, various forms can be easily conceived.

Below, AMT and PLT related to the above-mentioned embodiment are shown. Based on ARIBSTD-B60.

FIG. 11A is a diagram showing the data structure of the AMT according to the embodiment. The data included in the AMT is shown together with the number of bits and the data flag in each row. The content of each data is as follows.

·Table_id (table ID): set to 0xFE, which means that the table is identified according to the extended value of the table ID.

· Section_syntax_indicator (segment syntax indicator): set to "1" indicating the extended form.

Section_length (section length): specifies the number of bytes from the end of the section length field to the last section including CRC_32.

·Table_id_extension (table identification extension): set to 0x0000 representing the address mapping table.

· Version_number (version number): set to the area of the version number written to the table. Add 1 when the information in the table changes. When its value becomes 31, it returns to 0 next time.

·Current_next_indicator (current follow-up indication): In the case of "1", it means that the table is currently valid. In the case of "0", it means that the sent table has not been applied yet, and it is a scheduled table that becomes effective next.

·Section_number (section number): indicates the number of the section. The segment number of the first segment is 0x00. Each time a segment with the same table ID and table ID extension is added, the segment number is increased by 1.

Last_section_number (final section number): Specifies the number of the last section (ie, the section with the largest section number) of the table to which the section belongs.

·Num_of_service_id (number of service IDs): indicates the number of service_id described in the address mapping table.

·Service_id (service identification): plays the role of a label used to identify the service. It has the same function as the service ID described in the service catalog descriptor.

·Ip_version (IP version): Indicates the version of the IP package described in the directory, which is coded according to Table 5-3.

FIG. 11B is a diagram showing the IP version of the embodiment.

When the IP version is 0, it means IPv4, and when the IP version is 1, it means IPv6.

·Service_loop_length (service loop length): represents the bytes from after this field to before the next service identification field.

·Src_address_32 (send source IPv4 address): Describe the source IP address of the IPv4 packet that constitutes the service.

·Src_address_mask_32 (sender IPv4 address mask): For the IP address specified in the sender IPv4 address, specify the number of bits from the beginning (MSB) that becomes valid. Cannot take a value greater than 32.

·Dst_address_32 (destination IPv4 address): Describe the destination IP address of the IPv4 packet that constitutes the service.

·Dst_address_mask_32 (destination IPv4 address mask): For the IP address specified in the destination IPv4 address, specify the number of bits from the beginning (MSB) that becomes valid. Cannot take a value greater than 32. In addition, the multicast group that constitutes the service is set to both the source IPv4 address recognized as valid based on the source IPv4 address mask and the destination IPv4 address recognized as valid based on the destination IPv4 address mask. The address matches the multicast group.

·Src_address_128 (sender IPv6 address): Describe the source IP address of the IPv6 packet that constitutes the service.

·Src_address_mask_128 (sender IPv6 address mask): For the IP address specified in the sender IPv6 address, specify the number of bits from the beginning (MSB) that becomes valid. Cannot take a value greater than 128.

·Dst_address_128 (destination IPv6 address): Describe the destination IP address of the IPv6 packet that constitutes the service.

·Dst_address_mask_128 (destination IPv6 address mask): For the IP address specified in the destination IPv6 address, specify the number of bits from the beginning (MSB) that becomes valid. Cannot take a value greater than 128. In addition, the multicast group that constitutes the service is set to both the source IPv6 address recognized as valid based on the source IPv6 address mask and the destination IPv6 address recognized as valid based on the destination IPv6 address mask. The address matches the multicast group.

·Private_data_byte: store individually defined data.

CRC_32(CRC): set to comply with ITU-T recommendation H.222.0.

FIG. 11C is a diagram showing the data structure of the PLT (Package Table of Contents) according to the embodiment. The data included in the PLT is shown in each row together with the number of bits and the data flag. PLT shows a list of IP data streams and packet IDs for transmitting PA messages of MMT packets provided as broadcast services, and IP data streams for transmitting IP services. The descriptor stored in the PLT is set to the descriptor specified in the specification.

The contents of each data included in the PLT are as follows.

· Num_of_package (number of packages): indicates the number of packages that record location information in this table.

·MMT_package_id_length (package ID length): Express the length of package ID bytes in byte units.

·MMT_package_id_byte (package ID byte): indicates the package ID.

· MMT_general_location_info (location information): Represents the location information for transmitting the PA message of the package indicated by the package ID.

·Num_of_ip_delivery (number of IP release streams): indicates the number of IP services with location information recorded in this table.

·Transport_file_id (transport file ID): represents a label used to uniquely identify the file to be transferred.

·Location_type (location type): indicates the type of location information. 0x01 means IPv4 data flow, 0x02 means IPv6 data flow, and 0x05 means URL.

·Ipv4_src_addr (send source IPv4 address): indicates the source address of the IPv4 data stream.

·Ipv4_dst_addr (destination IPv4 address): Represents the destination address of the IPv4 data flow.

·Dst_port (destination port number): Represents the destination port number of the IP data stream.

·Ipv6_src_addr (send source IPv6 address): indicates the source address of IPv6 data flow.

·Ipv6_dst_addr (destination IPv6 address): Represents the destination address of the IPv6 data flow.

URL_length (URL length): indicates the bytes of the URL when the location information is indicated by the URL.

·URL_byte (URL byte): Represents the URL of the IP service.

· Descriptor_loop_length (descriptor length): represents the full bytes of the following descriptor.

Descriptor (descriptor area): Set as an area for the descriptor that shows the detailed information of the IP service.

The MMTP packet with a packet ID of 0x0000 indicates the transmission of a PA message (the PA message shown on the left side of FIG. 11D). When multiple packets are multiplexed, the PA message includes a packet directory table (PLT). The package list table provides a list of package IDs of MMTP packages that transmit PA messages including MPTs of other packages. Therefore, by analyzing the package list table, it is possible to specify the MMTP package that transmits the PA message including the MPT as the entry point of the service based on the package ID.

According to the above-mentioned embodiments, there is provided a transceiving method and a transceiving device for partial TLV streams for reducing reception problems.

Although several embodiments of the present application have been described, these embodiments are shown as examples and are not intended to limit the scope of the application. These new embodiments can be implemented in various other forms, and various omissions, substitutions, and changes can be made without departing from the scope of the application. These embodiments and their modifications are included in the scope and gist of the application, and are included in the application described in the scope of protection and the equivalent scope thereof. In addition, among the constituent elements of the technical solution, even when the constituent elements are expressed by dividing them, or by combining a plurality of them, or by combining them, they belong to the scope of the present application. In addition, a plurality of embodiments may be combined, and examples constructed by the combination also belong to the scope of the application.

In addition, in some cases, the drawings schematically show the width, thickness, shape, etc. of each part in comparison with the actual form in order to make the description clearer. In the block diagram, data and signals are exchanged between modules that are not connected or even if they are connected without showing the direction of the arrow. The functions shown in the block diagrams, the flowcharts, and the processes shown in the sequence diagrams can also be implemented by hardware (IC chip, etc.) or software (programs, etc.) or a combination of hardware and software. In addition, when the technical solution is expressed as control logic, when it is expressed as a program containing instructions to be executed by a computer, and when it is expressed as a computer-readable storage medium in which the instructions are recorded, it can also be expressed Apply the device of this application. In addition, there are no limitations on the names and terms used, and even if they are other expressions, if they have substantially the same content and the same subject, they are also included in this application.

Claims

A sending device, wherein the sending device includes:

TLV stream extraction mechanism, which receives broadcast signals based on MMT/TLV mode and obtains TLV streams stored with UDP/IP packets;

UDP/IP packet extraction mechanism, which extracts UDP/IP packets from the TLV stream;

An IP/UDP packet separation mechanism, which separates the UDP/IP packet into a first UDP/IP packet containing specified data and a second UDP/IP packet that does not contain the specified data;

An empty packet generating mechanism, which deletes the UDP/IP payload from the second UDP/IP packet, thereby generating an empty UDP/IP packet with only a UDP/IP header;

A partial TLV stream generating mechanism, which generates a partial TLV stream in a manner that includes at least the first UDP/IP packet and the UDP/IP empty packet; and

A partial TLV stream sending mechanism, which sends the partial TLV stream to an external device.
The transmitting device according to claim 1, wherein:

The IP header is a full header.
The transmitting device according to claim 1 or 2, wherein:

The IP header is either a full header or a compressed header.
The transmitting device according to any one of claims 1 to 3, wherein:

The specified data is specified by the user.
A method of sending, in which,

Receive broadcast signals based on the MMT/TLV method and obtain TLV streams storing UDP/IP packets,

Extract UDP/IP packets from the TLV stream,

Separate the UDP/IP packet into the first UDP/IP packet containing the specified data and the second UDP/IP packet not containing the specified data,

Delete the UDP/IP payload from the second UDP/IP packet, thereby generating an empty UDP/IP packet with only the UDP/IP header,

Generate a part of the TLV stream in a manner that includes at least the first UDP/IP packet and the UDP/IP empty packet,

The part of the TLV stream is sent to the external device.
A receiving device is a receiving device that generates part of the TLV stream from a TLV stream obtained by receiving a broadcast signal based on the MMT/TLV method, wherein:

The receiving device includes:

An IP/UDP packet extraction mechanism that extracts UDP/IP packets from the part of the TLV stream; and

An empty packet detection mechanism, which detects whether the UDP/IP packet has a payload,

The UDP/IP packet determined to have the payload is processed.
A receiving method is a method of receiving part of the TLV stream generated from the TLV stream obtained by receiving the broadcast signal based on the MMT/TLV method, where:

Extract UDP/IP packets from the part of the TLV stream,

Detect whether the UDP/IP packet has a payload,

The UDP/IP packet determined to have the payload is processed.
A receiving device, wherein the receiving device includes:

TLV stream extraction mechanism, which receives broadcast signals based on MMT/TLV mode and obtains TLV streams stored with UDP/IP packets;

UDP/IP packet extraction mechanism, which extracts UDP/IP packets from the TLV stream;

An IP/UDP packet separation mechanism that separates the UDP/IP packet into a first UDP/IP packet including the specified recorded data and a second UDP/IP packet that does not include the specified recorded data;

An empty packet generating mechanism that deletes the UDP/IP payload from the second UDP/IP packet, thereby generating an empty UDP/IP packet including the UDP/IP header; and

A recording mechanism that records at least the first UDP/IP packet and the UDP/IP empty packet.
The receiving device according to claim 8, wherein:

The receiving device further includes a partial TLV stream generating mechanism that generates a partial TLV stream in a manner that includes at least the first UDP/IP packet and the UDP/IP empty packet,

The recording mechanism records part of the TLV stream.
The receiving device according to claim 9, wherein:

The recording mechanism records all the TLV streams obtained from the broadcast signal,

The partial TLV stream generating mechanism converts the content contained in the TLV stream of the recording mechanism into the partial TLV stream, and records it again.
The receiving device according to any one of claims 8 to 10, wherein:

The receiving device includes a setting mechanism capable of setting whether the UDP/IP null packet is included in the partial TLV stream.
The receiving device according to any one of claims 8 to 11, wherein:

The receiving device is provided with a partial TLV stream playback mechanism, the partial TLV stream playback mechanism plays a part of the TLV stream, and causes the prompting unit to prompt the content,

The part of the TLV streaming mechanism has:

An IP/UDP packet extraction mechanism that extracts UDP/IP packets from the part of the TLV stream; and

An empty packet detection mechanism, which detects whether the UDP/IP packet has a payload,

The partial TLV streaming mechanism processes the UDP/IP packets determined to have the payload.
The receiving device according to any one of claims 8 to 12, wherein:

The IP header of the UDP/IP packet is a full header.
The receiving device according to any one of claims 8 to 13, wherein:

The IP header of the UDP/IP packet is either a full header or a compressed header.
A receiving method, in which,

Receive broadcast signals based on the MMT/TLV method and obtain TLV streams storing UDP/IP packets,

Extract UDP/IP packets from the TLV stream,

Separate the UDP/IP packet into a first UDP/IP packet including the specified recorded data and a second UDP/IP packet that does not include the specified recorded data,

Delete the UDP/IP payload from the second UDP/IP packet, thereby generating an empty UDP/IP packet including the UDP/IP header,

Recording is performed in a manner including at least the first UDP/IP packet and the UDP/IP empty packet.