CN113475088A

CN113475088A - Transmitting/receiving method and transmitting/receiving device

Info

Publication number: CN113475088A
Application number: CN202180001660.XA
Authority: CN
Inventors: 广田敦志
Original assignee: Hisense Visual Technology Co Ltd; Toshiba Visual Solutions Corp
Current assignee: Hisense Visual Technology Co Ltd; Toshiba Visual Solutions Corp
Priority date: 2020-01-31
Filing date: 2021-01-26
Publication date: 2021-10-01
Also published as: WO2021151376A1

Abstract

A transceiving method and a transceiving apparatus are provided for reducing the problem of reception of partial TLV streams. The transmitting device is provided with 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, wherein the TLV stream extraction mechanism receives a broadcast signal based on an MMT/TLV mode and acquires a TLV stream in which a UDP/IP packet is stored; the UDP/IP packet extraction mechanism extracts the UDP/IP packet from the TLV stream; an IP/UDP packet separating means for separating the UDP/IP packet into a 1 st UDP/IP packet containing the designated data and a 2 nd UDP/IP packet containing no designated data; the empty packet generating mechanism deletes the UDP/IP payload from the 2 nd UDP/IP packet, thereby generating a UDP/IP empty packet only with a UDP/IP header; the partial TLV flow generation mechanism at least comprises a 1 st UDP/IP packet and a UDP/IP empty packet to generate partial TLV flows in-situ; the partial TLV stream transmission mechanism transmits the partial TLV stream to the external device.

Description

Transmitting/receiving method and transmitting/receiving device

The present application claims the priority of japanese patent applications filed on 31/1/2020, having application numbers 2020-.

Technical Field

The embodiment of the application relates to a transmitting and receiving method and a transmitting and receiving device.

Background

In the specifications of advanced broadband digital satellite broadcasting, UDP/IP packets for MMTP packet transmission, which store resources such as images, audio, and subtitles constituting services, and MMT-SI, are header-compressed and transmitted. The television receiving apparatus 1 selects an asset of a service selected from the received broadcast signal and a necessary MMT-SI, generates a partial TLV stream, and outputs the partial TLV stream to an external apparatus. The television receiving apparatus 1 selects and rejects assets of a service selected from the received broadcast signal and a necessary MMT-SI, and records (records) the selected assets in the form of TLV streams to a recording/playing apparatus such as a hard disk.

Prior art documents

Non-patent document

Non-patent document 1: ARIBSTD-B392.3 edition "advanced broadband digital satellite broadcasting operation Specification"

Non-patent document 2: ARIBSTD-B631.9 edition "Standard Specification for receiving device for advanced broadband digital satellite broadcasting"

Disclosure of Invention

In the partial TLV stream created by editing a part of the TLV stream of the initial broadcast signal, IP information other than UDP/IP packets for storing the resources of the selected service and the necessary MMT-SI is lacking. In particular, when the header of the UDP/IP packet stored in the discarded TLV packet is a full header (uncompressed header), there is a possibility that delay or interruption may occur in display of service and presentation of related information when the partial TLV stream is received and played.

In addition, the record data inputted to the record reproduction apparatus lacks IP information other than the selected record data. In particular, when the header of the UDP/IP packet stored in the discarded TLV packet is a full header (uncompressed header), there is a problem that delay or interruption may occur when a playback display of a service or presentation of related information is performed when the recorded data is received and played.

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

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

The transmitter according to one embodiment of the present application includes a TLV stream extraction unit that receives a broadcast signal based on an MMT/TLV scheme and acquires a TLV stream in which a UDP/IP packet is stored, a UDP/IP packet extraction unit, an IP/UDP packet separation unit, an empty packet generation unit, and a partial TLV stream generation unit; the UDP/IP packet extraction mechanism extracts the UDP/IP packet from the TLV stream; an IP/UDP packet separating means for separating the UDP/IP packet into a 1 st UDP/IP packet containing the designated data and a 2 nd UDP/IP packet containing no designated data; the empty packet generating mechanism deletes the UDP/IP payload from the 2 nd UDP/IP packet, thereby generating a UDP/IP empty packet only with a UDP/IP header; the partial TLV flow generation mechanism at least comprises a 1 st UDP/IP packet and a UDP/IP empty packet to generate partial TLV flows in-situ; the partial TLV stream transmission mechanism transmits the partial TLV stream to the external device.

The receiving device according to an embodiment of the present application includes TLV stream extracting means for receiving a broadcast signal based on an MMT/TLV system and acquiring a TLV stream in which UDP/IP packets are stored, UDP/IP packet extracting means for extracting UDP/IP packets from the TLV stream, UDP/IP packet separating means for separating the UDP/IP packets into a 1 st UDP/IP packet including data of a specified video and a 2 nd UDP/IP packet including no data of the specified video, null packet generating means for deleting a UDP/IP payload from the 2 nd UDP/IP packet, thereby generating a UDP/IP null packet including a UDP/IP header, and the recording means records the packet including at least the 1 st UDP/IP packet and the UDP/IP null packet.

Drawings

Fig. 1 is a diagram showing an example of a television receiving apparatus corresponding to digital broadcasting based on MMT/TLV scheme and an electronic device receiving a partial TLV stream of an embodiment;

fig. 2 is a block diagram showing an example of a functional structure of a television receiving apparatus corresponding to digital broadcasting based on the MMT/TLV system of the embodiment;

fig. 3 is a block diagram showing an example of a functional configuration of a TLV/MMT separation processing unit in the television receiving apparatus according to the embodiment;

fig. 4A is a diagram showing an example of a multiplexing structure of TLV streams to be processed by the television receiving apparatus of the embodiment;

fig. 4B is a diagram showing one example of the configuration of each packet stored in the TLV flow of the embodiment;

fig. 4C is a diagram illustrating an example of header information of UDP/IP packets stored in TLV streams of the embodiment;

fig. 4D is a diagram illustrating another example of a structure of a null packet stored in a partial TLV stream of an embodiment;

fig. 5 is a block diagram showing an example of a functional configuration of a partial TLV stream generation section in the television receiving apparatus according to the embodiment;

fig. 6A is a block diagram illustrating one example of a functional structure of an electronic device receiving a partial TLV stream of an embodiment;

fig. 6B is a block diagram showing an example of a functional structure of a record playing section that records and plays part of TLV streams of the embodiment;

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

fig. 8 is a flowchart showing an example of processing operation of the TLV/MMT separation processing unit in the television receiving apparatus according to the embodiment;

fig. 9 is a flowchart showing an example of a processing operation of a partial TLV generation unit in the television receiving apparatus according to the embodiment;

fig. 10A is a flowchart showing an example of a processing operation of a partial TLV stream processing section in the electronic device according to the embodiment;

fig. 10B is a flowchart showing an example of the processing operation of the partial TLV stream processing section in the record playing section of the embodiment;

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

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

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

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

Description of the reference numerals

1 … television 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 … prompt unit, 16 … peripheral function, 17 … system bus, 18 … remote controller, 19 … record 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 NTP 72 TLV-SI extraction unit, 123 … extraction processing unit, 124 … IP/UDP header decompression unit, 125 … IP/UDP packet separation unit, 126 MMTP packet separation unit, 127 … t-SI extraction unit, MMTP 128 service/resource selection control unit, 129 … empty packet generation unit, … generation unit, MMTP 72 MMTP generation unit, MMTP 72 MMTP generation unit, and MMTP 142 MMTP packet generation unit, 144 … IP/UDP packet generating section, 145 … TLV packet generating section, 146 … TLV packet multiplexing section, 147 … TLV-SI generating section, 221 … TLV packet separating section, 222 … TLV-SI extracting section, 223 … NTP extracting processing section, 224 … IP/UDP packet header decompressing section, 225 … IP/UDP packet separating section, 226 … MMTP packet separating section, 227 … MMT-SI extracting section, 2251 … empty packet detecting section.

Detailed Description

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

Detailed description of the preferred embodiments

FIG. 1 illustrates an MMT/TLV-based approach to embodiments

Fig. 2 shows an example of a television receiving apparatus corresponding to digital broadcasting and an electronic device receiving a partial TLV stream.

The television receiving apparatus 1 receives a broadcast signal based on digital broadcasting of the MMT/TLV system, and acquires content (or also referred to as a service) transmitted by the broadcast signal. The

electronic devices

2A, 2B, and 2C (referred to as electronic devices 2 when no particular distinction is necessary) have

interfaces

3A, 3B, and 3C (referred to as interfaces 3 when no particular distinction is necessary) that can communicate with the television receiving apparatus 1, respectively, and acquire content transmitted by a broadcast signal via the interfaces 3 and display and output the content. In the present embodiment, the number of the electronic devices 2 is assumed to be 3, but any number of the electronic devices 2 may be 1 or more depending on the interface of the television receiving apparatus 1.

The electronic device 2 has a capability (resolution, frame rate, and others) of being able to use all or a part of the content transmitted by the television receiving apparatus 1. The electronic device 2 may be, for example, a tablet terminal, a monitor, a television receiving apparatus, or the like. The electronic device 2 may be a smartphone as long as it has an interface capable of communicating with the television receiving apparatus 1.

The

interfaces

3A, 3B, and 3C (referred to as an interface 3 when no particular distinction is required) are interfaces for performing data communication between the television receiving apparatus 1 and the electronic device 2, and may be wired or wireless. Further, as the interface 3, a Network conforming to DLNA (registered trademark) or an extension thereof may be used so that the television receiving apparatus 1 and the electronic device 2 can communicate with each other.

Fig. 2 is a block diagram showing an example of a functional configuration of a television receiving apparatus for digital broadcasting based on the MMT/TLV system of the embodiment.

The television receiving apparatus 1 receives a broadcast signal based on MMT/TLV system digital broadcasting, and presents the content transmitted by the broadcast signal to the user from a monitor or a speaker.

The TLV

stream extraction units

11A, 11B, and 11C (referred to as TLV stream extraction unit 11 without particular distinction) include a tuning unit 111A, a demodulation unit 112A, a descrambling unit 113A, and a CAS module 114A, and receive a broadcast signal and output a TLV stream as digital data.

The tuner unit 111A extracts a signal of a desired frequency band (broadcast channel) from a broadcast signal received by a cable system such as an antenna (not shown) or an optical line by cable broadcasting, performs frequency conversion and the like as necessary, and outputs the signal to the demodulator unit 112A. The demodulation unit 112A demodulates the input broadcast signal, performs error correction decoding, and the like, acquires digital data in the form of TLV (Type Length Value) and outputs the digital data. The acquired digital data is usually encrypted by scrambling, and the descrambling section 113A descrambles the scrambled digital data (scrambled data) and outputs it as a TLV stream. The CAS module 114A holds a key and the like necessary for the descrambling unit 113A to descramble the scrambled data, and supplies the key and the like to the descrambling unit 113A as necessary.

The TLV/MMT

separation processing units

12A, 12B, and 12C (which are referred to as TLV/MMT separation processing unit 12 without particular distinction) acquire encoded resource data (Asset data) (hereinafter, referred to as encoded resource data) constituting various control signals and services (contents) from the TLV stream output from the TLV stream extraction unit 11, and output the acquired encoded resource data. The TLV/MMT separation processing unit 12 may convert the input TLV stream into an IP/UDP stream, further convert the TLV stream into an MMT (MPEG Media Transport) stream, and separate the MMT stream into encoded resource data and SI (Signaling Information) data as control Information data. The TLV/MMT separation processing unit 12 may separate and output NTP time information data stored in IP/UDP format from the TLV stream. The TLV/MMT separation processing unit 12 may output the TLV packet extracted from the input TLV stream (or the extracted TLV stream). The TLV/MMT

separation processing units

12A, 12B, and 12C may simultaneously process and input respective outputs (streams and packets) to the content output unit 13, the partial TLV stream generation unit 14, and the like.

The content output unit 13 decodes the encoded resource data and outputs content data such as audio, images, and characters.

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

The encoded character data in the encoded resource data is decoded and played back by a character decoding unit, not shown, and output as character content data.

The output processing unit 133 adjusts and outputs the output timing, display method, and the like of the image content data (which may include audio content data, character content data, and the like). The output processing unit 133 may acquire NTP data (time information data) output from the TLV/MMT separation processing unit 12, and may play a clock synchronization signal for use in 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 be broadcast system-related control information such as information related to a broadcast program and control information related to multiplexing of UDP/IP packets. The various decoding units may select the resource data of the program or content data specified by the control unit 163 using the SI data, and decode the selected resource data to acquire the content data.

The partial TLV stream generator 14 extracts the resource data and control information data constituting the selected content (broadcast program) from the TVL stream and MMT stream separated and acquired by the TLV/MMT separation processor 12, and edits the extracted data to generate a partial TLV stream.

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

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

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

The interface unit 162 is various interfaces between the television receiving apparatus 1 and the outside, and may include various wired and wireless communication interfaces such as infrared communication, a mouse, a keyboard, ethernet, DLNA (registered trademark), HDMI (registered trademark), Wifi (registered trademark), and 5 th generation mobile communication (5G). The interface unit 162 includes a communication interface constituted by the interface 3. The interface unit 162 generates frame data according to a predetermined communication protocol with respect to input digital data, and transmits the generated frame data via a medium such as a wired or wireless medium. Further, a signal received via a medium such as a wired or wireless medium is demodulated to obtain digital data, and frame data according to a communication protocol is decomposed to output the digital data. The interface unit 162 may have a function of encrypting and decrypting digital data such as scrambling.

The control unit 163 may control various functions within the television receiving apparatus 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 performing data exchange between various functions in the television receiving apparatus 1, and is, for example, a serial bus. The interaction of data between the various functions in the television receiver 1 is not limited to the system bus 17, and may be another transmission path.

The remote controller 18 is a remote controller attached to the television receiving apparatus 1, and the user can perform various operations on the television receiving apparatus 1 using the remote controller 18. For example, when the user performs an operation designation through the remote controller 18, a control command is output from the remote controller. The control command is received by the television receiving apparatus 1 through infrared communication via the interface unit 162. The interface unit 162 outputs the received control command to the control unit 163, and the control unit 163 analyzes and extracts the received control command as control information to control various functions in the television receiving apparatus 1 based on the control information.

The recording/reproducing unit 19 is, for example, a Hard Disk Drive (HDD) and records data received and processed by the television receiving apparatus 1. The outputs 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 may be inputted to the record/playback unit 19.

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

The TLV/MMT separation processing unit 12 has a function of separating TLV streams into IP/UDP packets and MMT packets, and separating them into encoded resource data and SI data as control information data, and therefore, the functional configuration will be described using the relationship between the respective streams, packets, data, and the like.

Fig. 4A is a diagram showing an example of a multiplexing structure of TLV streams handled by the television receiving apparatus according to the embodiment, and chapter 13 of the fourth edition advanced broadband CS digital broadcasting SI operation regulation according to ARIB TR-B392.3 version (fifth edition).

The display box 50 shows a transponder (transponder) as a physical layer. The transponder is provided to a CS Satellite (Communication Satellite) and outputs a broadcast wave signal of an advanced broadband CS digital broadcast.

Display box 51 shows the layers of the TLV stream sent by the transponder shown in display box 50.

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

The display box 53 shows TLV-NIT (Network Information Table) stored in the TLV stream shown in the display box 51. The TLV-NIT is part of the TLV-SI stored in the TLV stream. The TLV-NIT stores information for the location resolution of the TLV stream, such as the physical structure of each transponder in the broadcast medium and the TLV stream transmitted thereto, and information specifying a service or what TLV stream the content belongs to.

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

Display box 55 shows a stream of UDP/IP packets dedicated to the NTP format sent through the layer of UDP/IP streams shown in display box 52. The portion of the display frame 55 overlapping the display frame 52 may be regarded as a header of a UDP/IP packet (also simply referred to as an IP header in some cases). The display box 551 may also be regarded as a payload (payload) of the UDP/IP packet, and the NTP data is stored in the display box 551.

The display box 56 shows the layers of MMTP sent through the layers of UDP/IP streams shown in display box 52.

The display box 57 shows UDP/IP streams (IP data streams) dedicated to SI data stored in TLV streams shown in the display box 51. In particular, the portion of the display frame 55 that overlaps the display frame 52 may be regarded as a header (also referred to as an IP header in some cases) of a UDP/IP packet. The upper part of the display frame 57 than the display frame 56 may be regarded as data transmitted as an MMTP packet as a payload of a UDP/IP packet. Control signal data common to all services, i.e., contents (programs), in TLV streams including PLTs is stored and transmitted.

The display boxes 58A, 58B, 58C (referred to as the display boxes 58 without particular distinction) respectively show UDP/IP streams (IP data streams) of each service stored in the TLV streams. In particular, the portion of the display frame 55 that overlaps the display frame 52 may be regarded as a header (also referred to as an IP header in some cases) of a UDP/IP packet. The upper portion of the display frame 58 than the display frame 56 may be regarded as data transmitted in the form of an MMTP packet as a payload of a UDP/IP packet. The UDP/IP streams (IP data streams) of the display boxes 58A, 58B, 58C typically store data associated with respectively different services (service 1, service 2, service 3 in the figure), i.e., different contents (programs). The UDP/IP streams (IP data streams) in the display boxes 58A, 58B, and 58C have different IP information, and in particular, have different IP addresses of transmission sources.

Display box 59 shows the same UDP/IP streams as display box 58, in particular UDP/IP streams common to the services. For example, the service 1, the service 2, and the service 3 are transmitted in the UDP/IP streams of the display frame 58A, the display frame 58B, and the display frame 58C, respectively, and data common to all or a part of the service 1, the service 2, and the service 3 is transmitted in the UDP/IP stream of the display frame 59 (in the figure, a caption superimposing MPU is shown). The IP information of the UDP/IP stream in the display box 59, particularly 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 boxes 58A, 58B, and 58C.

Referring back to fig. 3, the functional configuration of the TLV/MMT separation processing unit 12 will be described.

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

The TLV packet separation unit 121 separates the TLV stream output from the TLV stream selection processing unit 120 into 3 systems, that is, TLV-SI data (display frame 53 and display frame 54), UDP/IP packets in which NTP data (display frame 55) is stored, and UDP/IP packets in which MMTP packets (display frame 53 and display frame 54) are stored, for each TLV packet. The TLV packet separator 121 divides the TLV stream into 3 systems based on a packet identifier (packet _ type) stored in a header (also referred to as TLV header in some cases) of the TLV stream (not shown) in the layer of the TLV stream in the display box 51.

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

The NTP extraction processing unit 123 extracts NTP information from the UDP/IP packet of the display frame 55 output from the TLV packet separation unit 121 and outputs the extracted NTP information. The extracted NTP information is utilized for system clock playback at the receiver.

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 in which the MMTP packet (the display boxes 53 and 54) output from the TLV packet separation unit 121 is stored. Specifically, the following 2 kinds of IP headers attached to the MMTP packet exist: a header (also referred to as a Full header in some cases in the lower stage of fig. 4C) including IP information including an IP address and a port number; and a header (also referred to as a compression header in some cases, in the middle of fig. 4C) that does not contain IP information. Full-header IP packets are specified to be transmitted at least 1 time every 500[ msec ]. The IP packet header decompression unit 124 converts a UDP/IP packet having a compressed header (also referred to as a compressed UDP/IP packet in some cases) into a UDP/IP packet having a full header (also referred to as a UDP/IP packet in some cases) using information of the full header received in the past for each UDP/IP packet (IP data stream) having the same IP information, and outputs the UDP/IP packet. Alternatively, the UDP/IP packet may be compressed for each IP data stream and output as a series of UDP/IP streams.

The IP/UDP packet separation unit 125 selects a UDP/IP stream (IP data stream) input from the IP packet header decompression unit 124, separates UDP/IP packets of the selected UDP/IP stream, extracts MMTP packets, and outputs a stream of MMTP packets (also referred to as MMTP stream in some cases). More specifically, the IP/UDP packet separation unit 125 selects a UDP/IP stream (IP data stream) using the CID included in the IP header. In fig. 4A,

boxes

57, 58, 59 are shown transmitting MMTP streams. When selecting to separate UDP/IP packets, the IP/UDP packet separation unit 125 may use IP information stored in the AMT and IP information stored in PLT, MPT, or the like acquired in the subsequent processing.

The IP/UDP packet separation unit 125 also outputs a selected TLV packet from the received TLV packets. The outputted TLV packet may be a TLV packet (TLV packet storing a compressed IP packet that is not converted into a full header) inputted to the IP/UDP header decompression unit 124.

The MMTP packet separator 126 outputs control signal data and encoded resource data from the MMTP stream input from the IP/UDP packet separator 125. In fig. 4A, the video MPU, audio MPU, caption MPU, application MPU, and caption superimposition MPU of the display frame 58 correspond to the encoding resource data. Data other than the encoded resource data in the display box 58 and data in the display box 57 correspond to control signal data.

The MMT-SI extraction unit 127 extracts and outputs control information such as PLT and MPT from the MMT-SI, which is control signal data input from the MMTP packet separation unit 126. The PLT stores the packet ID of the MMTP packet of the MPT corresponding to the all-service (or content) transfer in the TLV stream (see the MMTP packet 63 in fig. 4B), and further stores information for solving the position of the MPT transfer, such as IP information including the source IP address of the UDP/IP packet stored therein. The MPT stores information for location resolution for resource transfer, such as a packet ID of MMTP for each resource constituting a service. The information stored in the PLT and MPT may be used in the IP/UDP packet separation unit 125. The MMT-SI extraction unit 127 extracts EPG information and the like from the MMT-SI and outputs the extracted information.

The service/resource selection control unit 128 receives information from each function in the television receiving apparatus 1, and outputs a control signal based on the received information or extracts and outputs further detailed information. When the user has given a control command to the television receiving apparatus 1 via the remote controller 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 a control signal and detailed information to each function in accordance with the control command.

The null packet generating unit 129 generates and outputs a header-compressed IP packet (referred to as an IP/UDP null packet) without a payload (not storing an MMTP packet) for, for example, a UDP/IP stream that is not selected within the IP data stream in the IP/UDP packet separating unit 125. In addition, only the UDP/IP header may be extracted and output. Fig. 4D shows an example of the structure of the null packet.

Fig. 4B is a diagram illustrating an example of the structure of each packet stored in a TLV flow of the embodiment.

The TLV packet 61 is composed of a header and a payload, and a fixed bit and 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, and particularly, 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 in which a packet _ id is stored as an identifier, and an MMTP payload. UDP/IP packets 62 are stored in the payload of the TLV packet 61, and MMTP packets 63 are stored in the IP/UDP payload. Resource data, SI data, and the like are stored in the MMTP payload.

Fig. 4C is a diagram showing an example of header information of UDP/IP packets stored in TLV streams according to the embodiment, and details of the header information of UDP/IP packet 62 in fig. 4B. As shown in fig. 4C, in the header-compressed IP/UDP packet, a source IP address (source _ address) and a destination IP address (destination _ address) are arranged in the IP/UDP header. In addition, in a normal IP/UDP packet, a source IP address (source _ address) and a destination IP address (destination _ address) are arranged in an IP header. NTP transmissions do not apply IP header compression and are typically transmitted at 33msec intervals. MMTP packet transmissions apply IP header compression and are transmitted in full headers at 500msec intervals.

The same source IP address (source _ address) is used for the source IP address in the NTP private IP data stream and the source address in the SI private IP data stream.

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

Therefore, it is possible to specify an IP/UDP packet of SI from among the multiplexed streams based on the source _ address of the IP/UDP packet source IP address of the NTP private IP data stream.

Fig. 4D is a diagram showing an example of the structure of a null packet stored in a partial TLV stream of 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 apparatus according to the embodiment.

The partial TLV stream generator 14 according to the present embodiment generates TLV packets including NTP data in addition to encoded resource data and MMT-SI control signal data, and outputs the TLV packets as partial TLV streams.

The MMT-SI generating unit 141 selects and extracts necessary information from the control information extracted and output by the MMT-SI extracting unit 127, and generates control information for the partial TLV stream (referred to as partial control signal data when distinguished from the control signal data of the TLV/MMT separation processing unit 12) based on the extracted information. Specifically, examples of the Information include MH-SIT (Selection Information Table) and MH-DIT (Discontinuity Information Table) specified in ARIBSTD-B63. Generally, the control information for the partial TLV stream is smaller than the control information extracted by the MMT-SI extraction section 127 (i.e., the control information transmitted by the broadcast signal).

The MMT-SI update unit 142 updates the content of the 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 the broadcast signal) output from the TLV stream extractor 11 is described with information of all services, and when the TLV stream is transmitted as a partial TLV stream, the PLT needs to be updated to include information of only a specified service. The same applies to the MPT, and the MPT needs to be updated to include only the information of the specified resource data when transmitted as a partial TLV stream. However, the IP header of the UDP/IP packet containing the PLT or MPT is not updated.

The MMTP packet generator 143 generates and outputs an MMTP packet by adding predetermined MMTP header information to the control signal data for the partial TLV stream input from the MMT-SI generator 141 as a payload.

The IP/UDP packet generation unit 144 outputs the UDP/IP packet input from the MMT-SI update unit 142 as it is. Further, the MMTP packet input from the MMTP packet generation unit 143 is referred to as a payload, and the UDP/IP packet header is added to the header information of the UDP/IP packet input from the MMT-SI update unit 142 while integrating the values of CID and SN, thereby generating and outputting a UDP/IP packet.

The UDP/IP packet and the IP/UDP null packet output from the IP/UDP packet generator 144 are input to the TLV packet generator 145, and TLV packets are generated and output by attaching TLV headers to the packets, respectively. Furthermore, the TLV packet storing the IP/UDP null packet is output in the same order/time as the original IP data stream. However, the header of the TLV packet changes the payload length, and thus the value of the length field is updated differently from the original TLV header.

The TLV packet multiplexer 146 multiplexes TLV packets input from the respective functions and outputs the multiplexed TLV packets as a partial TLV stream. Specifically, the TLV packet including the NTP data, the TLV packet output from the TLV packet generation unit 145, and the TLV packet including the 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 section 163 as a partial TLV stream signal according to a predetermined communication method.

The TLV-SI generation unit 147 generates TLV-SI information including the update information of the AMT and outputs the TLV-SI information to the TLV packet multiplexing unit 146. However, in the present embodiment, TLV-SI information is not multiplexed in a partial TLV stream, and thus the present function may not be provided.

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

The electronic device 2 receives the partial TLV stream signal transmitted from the television receiver 1 via the interface unit 21. The interface unit 21 includes a communication interface constituted by the interface 3. The interface section 21 extracts digital data from the received partial TLV stream signal and outputs the digital data as a partial TLV stream. The interface unit 21 generates frame data according to a predetermined communication protocol with respect to input digital data, and transmits the generated frame data via a medium such as a wired or wireless medium. Further, a signal received via a medium such as a wired or wireless medium is demodulated to obtain digital data, and frame data corresponding to a communication protocol is decomposed to output the digital data. The interface unit 21 may have encryption and decryption functions such as scrambling. The interface unit 21 according to the present embodiment can perform communication with the interface unit 162 by DLNA (registered trademark) or an extension thereof, for example.

The partial TLV stream processing unit 22 processes the partial TLV stream input from the interface unit 21, acquires encoded resource data and SI data, and outputs the encoded resource data and SI data. The encoded 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 characters. The converted content data is output to the content output unit 24. The content output unit 24 adjusts output time, display method, and the like for the content data, and outputs the content data to the presentation unit 25.

The presentation unit 25 is, for example, a signal display device (monitor), a speaker, or the like, and outputs an image, an audio, a character, or the like based on input content data.

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

Fig. 6B is a block diagram showing an example of a functional structure of a record playback section that records and plays back a part of TLV streams according to the embodiment.

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

The partial TLV stream processing unit 22 processes the partial TLV stream input from the recording unit 191, acquires encoded resource data and SI data, and outputs the encoded resource data and SI data. The encoded resource data is input to the content output unit 13 together with the SI data, and is converted into content data such as an image, voice, and text by the voice 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 output time, display method, and the like for the content data, and outputs the content data to the presentation unit 15.

The control unit 26 controls each function of the recording and reproducing unit 19. For example, when the user wants to record the content of the broadcast signal in the partial TLV stream form, if the user outputs a record command signal from the remote controller 18, the record command signal is received by the interface section 162 and output to the control section 163. The control unit 163 analyzes the video recording command signal and transmits a control signal of the video recording command to the control unit 26. When the control unit 26 receives the control signal of the video recording command, the partial TLV stream is received from the partial TLV stream generating unit 14 and stored in the recording unit 191. For example, when the user wants to play the content saved in the partial TLV form in the recording section 191, if the user outputs a play command signal from the remote controller 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 transmits a control signal of the playback command to the control unit 26. Upon receiving the control signal of the play command, the control section 26 outputs the partial TLV stream of the recording section 191 to the partial TLV stream processing section 22. When the partial TLV stream is processed by the partial TLV stream processing section 22, the resource data is obtained, and the user can view the content from the prompting section 15 or the like.

In fig. 6A and 6B, data exchange (including control) may be performed between functional blocks not connected to the control unit 26.

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

The functional structure of the partial TLV stream processing section 22 in fig. 7 will be described using the data layer of the TLV stream in fig. 4A.

The partial TLV stream processing unit 22 separates the partial TLV stream into an IP/UDP packet and an MMTP packet, and acquires and outputs encoded resource data and SI data as control signal data. The function of the partial TLV stream processing unit 22 is the same as that of the TLV/MMT separation processing unit 12 of the television receiving apparatus 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 3 systems of TLV-SI data (corresponding to the display boxes 53 and 54 in fig. 4A), UDP/IP packets in which NTP data (corresponding to the display box 55) is stored, and UDP/IP packets in which MMTP packets (corresponding to the display box 56) are stored, for each TLV packet. In the partial TLV stream processing unit of the recording/playback unit, the TLV packet separation unit 221 separates the partial TLV stream input from the recording unit 191 into 3 systems of TLV-SI data (corresponding to the display boxes 53 and 54 in fig. 4A), UDP/IP packets in which NTP data (corresponding to the display box 55) is stored, and UDP/IP packets in which MMTP packets (corresponding to the display box 56) are stored, for each TLV packet. The TLV packet separation unit 221 divides the partial TLV stream into 3 systems based on the packet identifier (packet _ type) stored in the TLV header (see the TLV packet in fig. 4B) in the layer of the TLV stream in the display frame 51.

The TLV-SI extracting section 222 may also extract and output necessary information from the TLV-SI if the TLV-SI output by the TLV-packet separating section 221 exists. However, in this embodiment, the TLV-SI is not required, and is not usually included in the partial TLV stream, so that the function may be omitted.

The NTP extraction processing unit 223 extracts and outputs NTP data from the UDP/IP packet of the display frame 55 output from the TLV packet separation unit 221. 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 packet header decompression unit 224 processes the IP header (corresponding to the display box 52) storing the UDP/IP packet in the header compression format of the MMTP packet (corresponding to the display box 56) output from the TLV packet separation unit 221. Specifically, the IP header attached to the MMTP packet has the following 2 types: a header (also referred to as a full header in some cases) including IP information of an IP address and a port number; and a header (also referred to as a compression header in some cases) that does not contain IP information. The IP packet header decompression unit 224 converts the UDP/IP packet having the compressed header (also referred to as a compressed UDP/IP packet in some cases) into an all-header UDP/IP packet (also referred to as a UDP/IP packet in some cases) using information of the all-IP header received in the past for each UDP/IP packet (IP data stream) having the same IP information, and outputs the all-header UDP/IP packet. Alternatively, the UDP/IP packet may be compressed for each IP data stream and output as a series of UDP/IP streams.

The IP/UDP packet separation unit 225 separates the UDP/IP packet input from the IP packet 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). More specifically, the null packet detection unit 2251 determines whether or not the UDP/IP packet input from the IP packet header decompression unit 224 is a null packet. The null packet detection unit 2251 skips the following processing when the UDP/IP packet is a packet with only an IP header (UDP/IP null packet). That is, the null packet detection unit 2251 does not output the UDP/IP packet to the MMTP packet separation unit 226 in the case of the UDP/IP null packet. On the other hand, if the packet is not a UDP/IP null packet, the null packet detection unit 2251 outputs the UDP/IP packet to the MMTP packet separation unit 226, which is a subsequent process. The IP/UDP packet separation unit 225 in fig. 7 uses information stored in the PLT, MPT, and the like obtained in the subsequent processing when selecting to separate UDP/IP packets.

The MMTP packet separator 226 outputs control signal data and encoded resource data from the MMTP stream input from the IP/UDP packet separator 225.

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

An example of the operation of the system according to the present embodiment will be described. Fig. 8 is a flowchart showing an example of the processing operation of the TLV/MMT separation processing unit in the television receiving apparatus according to the embodiment.

In order to specify a service (content) for output from the television receiving apparatus 1 as a partial TLV stream, or to specify a service (content) recorded as a partial TLV stream in a TLV stream received from the television receiving apparatus 1, the user performs a specifying operation through the remote controller 18. The remote controller 18 outputs a control command for specifying a service, and the interface unit 162 of the television receiving apparatus 1 receives the control command. The interface section 162 outputs the received control command to the control section 163, and the control section 163 analyzes the control command to extract information of the service designated by the user (designated service information) and outputs the information to the service/resource selection control section 128. The service/resource selection control unit 128 outputs the specified service information (service _ id) to the TLV/MMT separation processing unit 12 (step S11). In the TLV/MMT separation processor 12, the TLV stream selection processor 120 selects a TLV stream in which the specified service is stored based on the TLV-NIT extracted by the TLV-SI extractor 122 and the specified service information, and outputs the TLV stream to the TLV packet separator 121 (step S12).

The TLV packet separation unit 121 separates the TLV stream input from the TLV stream selection processing unit 120 into 3 systems based on the packet identifier (packet _ type) stored in the header indicated by the TLV packet 61 in fig. 4B (step S13). Specifically, the TLV packet is separated into 3 systems of TLV-SI data, UDP/IP packets in which NTP data is stored, and header-compressed UDP/IP packets in which MMTP packets are stored, depending on the type of data stored in the payload of the TLV packet, and the TLV-SI data, the UDP/IP packets, and the MMTP packets are input to the TLV-SI extraction unit 122, the NTP extraction processing unit 123, and the IP packet header decompression unit 124, respectively.

The TLV-SI extraction unit 122 extracts TLV-NIT data and AMT data, and outputs the extracted data 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 the extracted NTP data 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). TLV packets including the header-compressed UDP/IP packet in which the MMTP packet is stored are input to the IP packet header decompression unit 124 and the IP/UDP packet separation unit 125, and processed (step S16). The IP/UDP packet separation unit 125 confirms the IP data stream using the CID of the IP header information of the input TLV packet (see UDP/IP packet 62 in fig. 4B) and the IP information input from the service/resource selection control unit 128 (step S17). By comparing the input IP information with the IP information described in the entire header, the correspondence between the input IP information and the CID is determined. If it is not confirmed that the IP data flow is the IP data flow selected according to the IP information, the next TLV packet is confirmed (NO at 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 process is performed (yes at 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 checked (step S19). The MMTP packet separation unit 126 checks the packet _ id, and outputs the UDP/IP packet stored in the inputted TLV packet when the selected MMT-SI is stored in the inputted TLV packet, that is, when the PLT, the MPT associated with the service _ id specified by the user, and the predetermined MMT-SI are stored (yes in step S20, S21). The MMTP packet separation unit 126 checks the packet _ id, and when the selected MMT-SI is not stored in the inputted TLV packet, that is, when the MMT-SI related to the service _ id designated by the user is not stored, checks whether or not the selected resource is stored in the inputted TLV packet (no in S20, step S22). The MMTP packet separator 126 extracts the MPT of the service _ id identifying the service selected by the user from the PLTs of the MMT-SI extracted in step S20. The MMTP packet separation unit 126 can specify the resource constituting the service specified by the user from the extracted information of the MPT. Wherein the resources required for the partial TLV stream can be selected appropriately (e.g. only images, sound, subtitles, etc.). The MMTP packet separator 126 checks the MPT information of the MMT-SI extracted in step S20 and the packet _ id of the input TLV packet, and outputs the input TLV packet when the selected resource is stored in the input TLV packet, that is, when the service _ id resource specified by the user is stored (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 packet header decompression unit 124. On the other hand, the MMTP packet separator 126 checks the MPT information of MMT-SI extracted in step S20 and the packet _ id of the inputted TLV packet, and when the selected resource is not stored in the inputted TLV packet, removes the payload part of the UDP/IP packet stored in the TLV packet, and generates and outputs a UDP/IP null packet (step S24). Here, the UDP/IP null packet means that the UDP/IP header can be output as it is.

Further, steps S18 to S20 of the above-described flow are supplementary explained. First, to acquire PLT, IP information of the SI-dedicated IP data stream is determined based on information of the AMT and selected. Since the packet _ id of the PLT is fixed to 0x0000 (fixed value), the extraction of the PLT can be performed through the processing of the MMTP packet separator 126 and the MMT-SI extractor 127.

Next, based on the acquired PLT, IP information of an IP data stream to be transmitted to the MPT of the service specified by the user is specified, 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 separator 126 and the MMT-SI extractor 127. Further, since 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, IP information of the service common IP data stream is specified with reference to the MPT as necessary, and the IP information is selected. Since the IP information and the packet _ id are also described in the MPT, the resource can be extracted through the processing of the MMTP packet separator 126. Step S20 of the above flow is explained in detail. The MMTP packet separator 126 extracts and outputs control signal data from the inputted TLV packet, UDP/IP header analysis information, and the like. The output control signal data is input to the MMT-SI extraction section 127, and the MMT-SI extraction section 127 receives IP information such as an IP address specifying a service transmission source stored in the AMT from the service/resource selection control section 128, and extracts a PLT based on the received information. The MMT-SI extraction unit 127 outputs the extracted PLT to the service/resource selection control unit 128. Further, the MMT-SI extraction section 127 extracts MPT based on the extracted PLT. Step S22 of the above flow is explained in detail. The MMT-SI extraction unit 127 outputs the extracted MPT to the service/resource selection control unit 128. The MMTP packet separator 126 extracts encoded resource data from the inputted 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 apparatus according to the embodiment.

In the partial TLV stream generator 14, the TLV packet of the resource data is input to the TLV packet multiplexer 146 (step S101A). In the partial TLV stream generator 14, the UDP/IP null packet is output to the TLV packet generator 145 (step S101B). In the partial TLV stream generator 14, the control signal data is input to the MMT-SI generator 141. The MMT-SI generation unit 141 generates MH-SIT, MH-DIT, and the like, which are partial control signal data to be output to be included in the partial TLV stream, and outputs the generated data to the MMTP packet generation unit 143 (step S102A). The PLT and MPT in the control signal data input to the partial TLV stream generator 14 are input to the MMT-SI update unit 142, and the content is updated as necessary and output to the IP/UDP packet generator 144 (step S102B). The partial TLV stream generator 14 inputs the received TLV packet storing the NTP data to the TLV packet multiplexer 146 (step S103).

The MMTP packet generator 143 converts the input partial control signal data into an MMTP packet, and outputs the MMTP packet to the IP/UDP packet generator 144 (step S104). Here, when the MMTP packet is distinguished 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, and the like to the inputted partial MMTP packet, generates a UDP/IP packet, and outputs the UDP/IP packet to the TLV packet generation unit 145 (step S105). In step S102B, the UDP/IP packet input from the MMT-SI update unit 142 is output as it is (step S105). When the UDP/IP packet is distinguished 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.

The partial UDP/IP packet including the UDP/IP null packet is input to the TLV packet generation unit 145, and the TLV packet generation unit 145 generates a TLV packet by adding the necessary TLV-SI and TLV header to the partial UDP/IP packet as a payload (step S106). When the TLV packet is distinguished from the TLV packet input to the TLV packet separator 121, the TLV packet output in step S106 is referred to as a partial TLV packet. The generated partial TLV packet, the resource data acquired in step S101A and step S103, and the TLV packet including the NTP are input to the TLV packet multiplexer 146. The TLV packet multiplexer 146 outputs the inputted TLV packet as a partial TLV stream. The interface unit 162 outputs the partial TLV stream as a partial TLV stream signal using a communication scheme such as DLNA (registered trademark) or the extended scheme via the interface 3 (step S107).

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

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

In the electronic device 2, the partial TLV stream signal output from the television receiver 1 is received by the interface unit 21. The interface unit 21 acquires the partial TLV stream by performing processing such as demodulation on the partial TLV stream signal. The acquired partial TLV stream is input to the TLV packet separator 221 of the partial TLV stream processor 22 (step S201). The TLV packet separation unit 221 separates the partial TLV stream into TLV-SI data, a UDP/IP packet stream of NTP data, and a UDP/IP packet stream of MMTP packets based on the packet identifier (packet _ type) stored in the TLV header of the partial TLV stream (step S202). The TLV-SI data is input to the TLV-SI extraction section 222, and the TLV-SI extraction section 222 extracts data required in the processing of the partial TLV stream. In addition, in the example of the present embodiment, the partial TLV stream does not include TLV-SI data.

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 in which the MMTP packet is stored is input to the IP packet header decompression unit 224, and converted into a UDP/IP packet of the full header (step S204). In step S204, the same processing is performed for the UDP/IP null packet. The UDP/IP packet of the converted full header is input to the IP/UDP packet separation section 225, and the IP/UDP packet separation section 225 extracts the MMTP packet and outputs it to the MMTP packet separation section 226 (step S205). The MMTP packet separation section 226 extracts the MMTP packet related to the SI data among the inputted MMTP packets, and inputs the extracted MMTP packet to the MMT-SI extraction section 227 (step S206).

The MMT-SI extraction unit 227 extracts PLTs from the inputted MMTP packet (step S207). More specifically, the PLT is extracted using the packet ID of the IP header given to the MMTP packet extracted in step S206.

Further, the MMT-SI extraction unit 227 extracts the MPT based on the information described in the extracted PLT (step S208). The MMTP packet separator 226 extracts encoded resource data from the inputted 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, and outputs content data such as audio, images, and characters. The output content data is presented to the user from a speaker or a monitor as contents such as images, sounds, and characters in the presentation unit 25.

In the above sequence, the electronic device 2 receives the partial TLV stream transmitted from the television receiving apparatus 1, and the user can view the content using the electronic device 2.

In the embodiment, the television receiving apparatus 1 as the source device transmits only the header portion of the UDP/IP packet (UDP/IP null packet) including the partial TLV stream for data other than the selected service. The electronic device 2 skips the processing of the UDP/IP null packet included in the partial TLV stream, thereby being able to acquire the content data transmitted by the partial TLV stream.

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

The control unit 26, upon receiving the command to record the partial TLV stream (step S2001), causes the record playing unit 19 to record the partial TLV stream outputted from the partial TLV stream generating unit 14 (step S2002).

The control section 26, upon receiving the command to play the partial TLV stream recorded in the record playing section 19 (step S200), inputs the partial TLV stream input from the recording section 191 to the partial TLV stream processing section 22 to the TLV packet separating section 221 of the partial TLV stream processing section 22 (step S201). The TLV packet separation unit 221 separates the partial TLV stream into TLV-SI data, a UDP/IP packet stream of NTP data, and a UDP/IP packet stream of MMTP packets based on the packet identifier (packet _ type) stored in the TLV header of the partial TLV stream (step S202). The TLV-SI data is input to the TLV-SI extraction section 222, and the TLV-SI extraction section 222 extracts data required in the processing of the partial TLV stream. In addition, in the example of the present embodiment, the partial TLV stream does not include TLV-SI data.

In the above order, the record playing section 19 can play the partial TLV stream recorded in the recording section 191. By playing part of the TLV stream, the user can watch the content. In the embodiment, only the header portion of the UDP/IP packet (UDP/IP null packet) is recorded in the partial TLV stream for data other than the specified service. The record playing unit 19 skips the processing of the UDP/IP null packet included in the partial TLV stream, thereby being able to acquire the content data transmitted by the partial TLV stream. In addition, whether or not to put an IP null packet in a partial TLV stream can be set.

In the specifications of the advanced broadband digital satellite broadcasting, an IP packet for MMTP packet transmission, which stores MMT-SI, such as images, audio, and subtitles, which constitute a service, is header-compressed and transmitted. The television receiver 1 selects a service selected from the received broadcast signal and a necessary MMT-SI, generates a partial TLV stream, and outputs the partial TLV stream to an external device or records the partial TLV stream in the recording/playing unit 19. Therefore, in general, for partial TLV streams, the data contained in the broadcast signal is missing. In particular, information included in the header of the UDP/IP packet is insufficient, and thus there is a problem that the continuity of the UDP/IP packet (set by the SN field) is broken. In addition, the UDP/IP packet with the full header is originally transmitted less frequently, and may be problematic if it is not included in a partial TLV stream. For example, in the electronic device 2 or the recording/playback unit 19, there is a possibility that delay or interruption may occur in playback display of a service or presentation of related information during reception/playback processing of a partial TLV stream. Although this problem has not yet been surfaced, it is desirable to deal with this as a mechanism in view of the future problems that will occur due to higher functionality, higher capacity, and the like, and according to the embodiments of the present invention, partial TLV streams that do not cause the above problems can be transmitted and received or recorded and played.

In addition, although the present embodiment shows an example of applying the TLV stream in the specification of the advanced broadband CS digital broadcast shown in fig. 4B, the present invention can also be applied to an advanced broadband BS digital broadcast based on chapter 13 of the ARIB TR-B392.3 version (third division) fourth edition advanced broadband BS digital broadcast SI operation regulation. Unlike the advanced broadband CS digital broadcasting, in the advanced broadband BS digital broadcasting, a plurality of TLV streams are output from the responder, and each TLV stream contains TLV-SI data (AMT, TLV-NIT), a UDP/IP packet in which NTP is stored, and a UDP/IP packet in which MMTP packet is stored. In the case of advanced broadband CS digital broadcasting, one TLV-NIT, AMT, and NTP dedicated IP data stream exists in one TLV stream, the MMTP packet transfer is for the SI dedicated IP data stream, and a plurality of services (corresponding to display boxes 58A, 58B, and 58C in fig. 4A) constitute different IP data streams. On the other hand, in the case of advanced broadband BS digital broadcasting, one TLV-NIT, AMT, and NTP dedicated IP data stream still exists in one TLV stream, but even if there are a plurality of services for MMTP transmission, all of them are constituted by one IP data stream. Such multiple TLV streams are output from one transponder. In this case, when a partial TLV stream is generated by selecting one service from TLV streams of a broadcast signal, UDP/IP packets in the partial TLV stream are frequently missing as compared with the data structure shown in fig. 4A. Therefore, in the case of the TLV stream structure as the advanced broadband BS digital broadcast, if the embodiments of the present application are used, it is possible to further reduce the problem caused by the occurrence of the lack of UDP/IP packets.

In the present embodiment, an example is shown in which the partial TLV stream is recorded in the record playing section 19 so as to contain UDP/IP null packets, but the recording form is not limited to the strict partial TLV stream form. For example, in a normal recording, when recording a selected broadcast program (service) in the recording/playback unit 19, the same effect as that of the present embodiment can be obtained by recording the IP header of the UDP/IP packet storing the content data of the unselected program in the recording/playback unit 19. In addition, the data storing the content data recorded in the above-described normal recording may be outputted to an external device as a partial TLV stream.

Further, according to the present embodiment, the TLV stream outputted from the broadcasted TLV stream extracting section 11 is recorded as it is in the record playing section 19, and then a partial TLV stream including a null packet is generated at an arbitrary timing (non-real time), and it can be recorded separately as a partial TLV stream. For example, all TLV streams received by the television receiving apparatus 1 are recorded (referred to as full-video recording). When the television receiver 1 receives a designation from the remote controller 18 of the user, the TLV streams of the program designated by the user among all the TLV streams recorded in the recording/playing section 19 are input from the recording/playing section 19 to the TLV/MMT separation processing section 12. According to the flowchart of fig. 8, the data outputted from the TLV/MMT separation processing unit 12 is inputted to the partial TLV stream generating unit 14, and thereby a partial TLV stream including an IP null packet can be generated for the content data of the program specified by the user. The generated partial TLV stream may be recorded again in the recording and playing section 19(dubbing function). In addition, various forms can be easily conceived by combining the functions of the above-illustrated examples.

The AMT and PLT related to the above-described embodiments are shown below. Based on ARIBSTD-B60.

Fig. 11A is a diagram showing a data structure of an AMT of an embodiment, and data contained in the AMT is shown in each line together with the number of bits, and a data flag. The contents of each data are as follows.

Table _ id (table id): set to 0xFE, indicates that the table is identified from the value of the table identification extension.

Section _ syntax _ indicator (section syntax indication): set to "1" representing the extended form.

Section _ length (section length): the number of bytes of the segment from the end of the segment length field to the end including CRC 32 is specified.

Table _ id _ extension (table id extension): set to 0x0000 representing the address mapping table.

Version _ number (version number): set as an area of the version number of the write table. Plus 1 if there is a change in the information in the table. When the value becomes 31, the value returns to 0 next time.

Current _ next _ indicator (current subsequent indication): in the case of "1" this table is currently valid. In the case of "0", the table indicating transmission is not yet applied, and is a predetermined table that becomes valid next.

Section _ number (section number): indicating the number of segments. The segment number of the initial segment is 0x 00. Each time a segment is appended with the same table identification and table identification extension, the segment number is incremented by 1.

Last _ section _ number (final section number): the number of the last segment of the table to which the segment belongs (i.e., the segment with the largest segment number) is specified.

Num of service id (service identification number): indicates the number of service _ ids described in the address mapping table.

Service _ id (service identification): functioning as a tag for identifying the service. Has the same role as the service identification described in the service directory descriptor.

IP _ version (IP version): the version of the IP packet described in the directory is shown and encoded in accordance with table 5-3.

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

The IP version 0 indicates IPv4, and the IP version 1 indicates IPv 6.

Service _ loop _ length (service cycle length): indicating the bytes from after this field until before the next service identification field.

Src _ address _ 32 (transmission source IPv4 address): a transmission source IP address of an IPv4 packet constituting a service is described.

Src _ address _ mask _ 32 (transmission source IPv4 address mask): the number of bits from the valid start (MSB) is specified for the IP address specified in the source IPv4 address. Values larger than 32 cannot be taken.

Dst _ address _ 32 (destination IPv4 address): a destination IP address of an IPv4 packet constituting a service is described.

Dst _ address _ mask _ 32 (destination IPv4 address mask): the number of bits from the start (MSB) of validity is specified for the IP address specified in the destination IPv4 address. Values larger than 32 cannot be taken. The multicast group constituting the service is set to a multicast group matching both the source IPv4 address identified as valid by the source IPv4 address mask and the destination IPv4 address identified as valid by the destination IPv4 address mask.

Src _ address _ 128 (transmission source IPv6 address): a transmission source IP address of an IPv6 packet constituting a service is described.

Src _ address _ mask _ 128 (transmission source IPv6 address mask): the number of bits from the valid start (MSB) is specified for the IP address specified in the source IPv6 address. Values greater than 128 cannot be taken.

Dst _ address _ 128 (destination IPv6 address): a destination IP address of an IPv6 packet constituting a service is described.

Dst _ address _ mask _ 128 (destination IPv6 address mask): the number of bits from the start (MSB) of validity is specified for the IP address specified in the destination IPv6 address. Values greater than 128 cannot be taken. The multicast group constituting the service is set to a multicast group matching both the source IPv6 address identified as valid by the source IPv6 address mask and the destination IPv6 address identified as valid by the destination IPv6 address mask.

Private _ data _ byte: individually defined data is stored.

CRC _ 32 (CRC): is set to comply with ITU-T recommendation h.222.0.

Fig. 11C is a diagram showing a data structure of a PLT (packet directory table) according to the embodiment, and shows data included in the PLT, together with the number of bits and data flag, in each line. PLT shows an IP data stream and a packet ID for transmitting a PA message of an MMT packet provided as a broadcast service, and a list of IP data streams for transmitting an IP service. The descriptor stored in the PLT is set to the descriptor specified in the specification.

The content of each data included in the PLT is as follows.

Num of package: the number of packets in which the position information is described in this table is indicated.

MMT _ package _ ID _ length (packet ID length): the length of the packet ID byte is expressed in byte units.

MMT _ package _ ID _ byte (packet ID byte): indicating the packet ID.

MMT _ general _ location _ info (location information): and location information indicating the transmission of the PA message of the packet indicated by the packet ID.

Num of IP delivery (number of IP distribution streams): indicates the number of IP services for which the location information is described in this table.

Transport _ file _ id (transfer file identification): a tag is represented that uniquely identifies the file to be transferred.

Location _ type (location type): indicates the kind of the position information. 0x01 denotes IPv4 data flow, 0x02 denotes IPv6 data flow, and 0x05 denotes URL.

IPv4 _ src _ addr (transmission source IPv4 address): indicating the transmission source address of the IPv4 data flow.

IPv4 _ dst _ addr (destination IPv4 address): representing the destination address of the IPv4 data flow.

Dst _ port (destination port number): indicating the destination port number of the IP data flow.

IPv6 _ src _ addr (transmission source IPv6 address): indicating the transmission source address of the IPv6 data flow.

IPv6 _ dst _ addr (destination IPv6 address): representing the destination address of the IPv6 data flow.

URL _ length (URL length): a byte indicating a URL in the case where the location information is shown by the URL.

URL _ byte (URL byte): a URL representing an IP service.

Descriptor _ loop _ length (descriptor length): representing full bytes of the subsequent descriptor.

Descriptor (descriptor region): an area for a descriptor indicating detailed information of the IP service is set.

The MMTP packet having a packet ID of 0x0000 indicates the case of transmitting the PA message (PA message shown on the left side of fig. 11D). When a plurality of packets are multiplexed, the PA message includes a packet table (PLT). The packet directory table gives a directory of packet IDs of MMTP packets that transmit PA messages including MPTs of other packets. Therefore, by analyzing the packet directory table, it is possible to specify an MMTP packet to be transmitted to a PA message including an MPT as an entry point of the service, from the packet ID.

According to the above-mentioned embodiments, a partial TLV stream transceiving method and a transceiving apparatus for reducing the problem of reception are provided.

While several embodiments of the present application have been described, these embodiments have been presented by way of example, and are not intended to limit the scope of the application. These new embodiments may be implemented in various other forms, and various omissions, substitutions, and changes may be made without departing from the spirit of the present application. These embodiments and modifications thereof are included in the scope and gist of the application, and are included in the application described in the scope of claims and equivalents thereof. In addition, the present invention also encompasses a case where each component of the technical means is expressed by dividing the component, a case where a plurality of components are expressed by combining the components, or a case where the components are expressed by combining the components. In addition, a plurality of embodiments may be combined, and an example configured by the combination also belongs to the scope of the application.

In addition, the drawings schematically show the width, thickness, shape, and the like of each portion in comparison with the actual form in some cases for the sake of clarity of the description. In the block diagram, data and signals are exchanged between modules that are not connected or even when the modules are connected and the directions of arrows are not shown. The functions shown in the block diagrams, and the processes shown in the flowcharts and sequence diagrams may be realized by hardware (an IC chip or the like), software (a program or the like), or a combination of hardware and software. The apparatus of the present application can also be applied to a case where the technical means is expressed as control logic, a case where the technical means is expressed as a program including instructions to be executed by a computer, and a case where the technical means is expressed as a computer-readable storage medium on which the instructions are described. The names and terms used are not limited, and other expressions are also included in the present application if they have substantially the same contents and the same subjects.

Claims

A transmission device, comprising:

a TLV stream extraction mechanism which receives the broadcast signal based on the MMT/TLV mode and acquires the TLV stream storing the UDP/IP packet;

a UDP/IP packet extraction mechanism that extracts UDP/IP packets from the TLV stream;

an IP/UDP packet separating means for separating the UDP/IP packet into a 1 st UDP/IP packet containing specified data and a 2 nd UDP/IP packet not containing the specified data;

a null packet generation unit configured to delete the UDP/IP payload from the 2 nd UDP/IP packet, thereby generating a UDP/IP null packet having only a UDP/IP header;

a partial TLV stream generation mechanism that generates a partial TLV stream in a manner that includes at least the 1 st UDP/IP packet and the UDP/IP null packet; and

a partial TLV stream transmission mechanism that transmits the partial TLV stream to an external device.
The transmission apparatus according to claim 1,

the IP header is a full header.
The transmission apparatus according to claim 1 or 2,

the IP header is either a full header or a compressed header.
The transmission apparatus according to any one of claims 1 to 3,

the specified data is specified by a user.
A transmission method, wherein,

receiving the broadcast signal based on the MMT/TLV mode and acquiring the TLV stream storing the UDP/IP packet,

extracting UDP/IP packets from the TLV stream,

separating the UDP/IP packet into a 1 st UDP/IP packet containing the specified data and a 2 nd UDP/IP packet not containing the specified data,

deleting the UDP/IP payload from the 2 nd UDP/IP packet, thereby generating a UDP/IP null packet having only a UDP/IP header,

generating a partial TLV stream in a manner that includes at least the 1 st UDP/IP packet and the UDP/IP null packet,

and sending the partial TLV stream to an external device.
A reception device for receiving a partial TLV stream generated from a TLV stream obtained by receiving a broadcast signal based on an MMT/TLV scheme,

the receiving apparatus includes:

an IP/UDP packet extraction mechanism that extracts UDP/IP packets from the partial TLV stream; and

a null packet detection mechanism that detects the presence or absence of a payload in the UDP/IP packet,

and processing the UDP/IP packet determined to have the payload.
A receiving method of a partial TLV stream generated from a TLV stream obtained by receiving a broadcast signal based on an MMT/TLV scheme, wherein,

extracting UDP/IP packets from the partial TLV stream,

detecting whether the UDP/IP packet has a payload or not,

and processing the UDP/IP packet determined to have the payload.
A reception device, comprising:

a TLV stream extraction mechanism which receives the broadcast signal based on the MMT/TLV mode and acquires the TLV stream storing the UDP/IP packet;

a UDP/IP packet extraction mechanism that extracts UDP/IP packets from the TLV stream;

an IP/UDP packet separating means for separating the UDP/IP packet into a 1 st UDP/IP packet containing data of a specified video and a 2 nd UDP/IP packet not containing the data of the specified video;

a null packet generation unit configured to generate a UDP/IP null packet including a UDP/IP header by deleting a UDP/IP payload from the 2 nd UDP/IP packet; and

and a recording means for recording the data so as to include at least the 1 st UDP/IP packet and the UDP/IP null packet.
The receiving device of claim 8,

the receiving apparatus further includes a partial TLV stream generation unit that generates a partial TLV stream so as to include at least the 1 st UDP/IP packet and the UDP/IP null packet,

the recording mechanism records partial TLV streams.
The receiving device of claim 9,

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

the partial TLV flow generation mechanism converts the content contained in the TLV flow of the recording mechanism into the partial TLV flow and records again.
The receiving device of any one of claims 8 to 10,

the receiving device is provided with a setting means capable of setting whether or not the partial TLV stream includes the UDP/IP null packet.
The receiving device of any one of claims 8 to 11,

the receiving device is provided with a partial TLV stream playback mechanism which plays a partial TLV stream and causes a presentation unit to present the content,

the partial TLV stream playback mechanism includes:

an IP/UDP packet extraction mechanism that extracts UDP/IP packets from the partial TLV stream; and

a null packet detection mechanism that detects the presence or absence of a payload in the UDP/IP packet,

and the partial TLV stream playing mechanism processes the UDP/IP packets judged to have the payloads.
The receiving device of any one of claims 8 to 12,

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

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

receiving the broadcast signal based on the MMT/TLV mode and acquiring the TLV stream storing the UDP/IP packet,

extracting UDP/IP packets from the TLV stream,

separating the UDP/IP packet into a 1 st UDP/IP packet containing data of a specified video and a 2 nd UDP/IP packet not containing data of the specified video,

deleting the UDP/IP payload from the 2 nd UDP/IP packet to generate a UDP/IP null packet including a UDP/IP header,

recording is performed so as to include at least the 1 st UDP/IP packet and the UDP/IP null packet.