JP7807940B2 - Receiving device, transmitting device, receiving method, sending method, and program - Google Patents

Description

The present invention relates to a receiving device, a transmitting device , a receiving method, a sending method, and a program.

The standard MPEG (Moving Picture Experts Group)-DASH (Dynamic Adaptive Streaming over HTTP) (ISO/IEC23009-1) has traditionally been used for streaming video distribution over the Internet, such as video-on-demand (VOD) (see, for example, Patent Document 1). The use of MPEG-DASH in next-generation television broadcasting networks, such as terrestrial digital broadcasting, is also being considered.

Japanese Patent Application Laid-Open No. 2021-022898

However, MPEG-DASH requires a program called a DASH player to receive video, and when a viewer selects a channel and then receives the DASH player transmitted by each broadcasting station via airwaves, there is a problem in that it can take a long time from selecting a channel to displaying the video due to the time it takes to receive the DASH player.

The present invention has been made in view of the above circumstances, and provides a receiving device, a transmitting device , a receiving method, a sending method, and a program that can reduce the time from when a viewer selects a channel until the video is displayed.

This invention has been made to solve the above-mentioned problems, and one aspect of the present invention is a receiving device that includes a tuner unit that receives television broadcast signals, a demultiplexing unit that acquires content and DASH player information indicating the DASH player required to play the content from the signals, and a control unit that, if the device itself has a DASH player indicated by the DASH player information, reads out the DASH player that it has.

In another aspect of the present invention, in the above-mentioned receiving device, the DASH player information includes information indicating the name of the DASH player and information indicating the range of version numbers of the DASH player capable of playing the content.

In another aspect of the present invention, in the above-mentioned receiving device, the DASH player information includes information indicating the identification number of the DASH player and information indicating the range of version numbers of the DASH player that can play the content.

In another aspect of the present invention, in the receiving device described above, the DASH player information includes information indicating at least one of the category, profile, and level of receiving devices capable of playing the content, and information indicating the range of version numbers of the DASH players capable of playing the content.

In another aspect of the present invention, the receiving device described above includes a DASH player storage unit, and when the control unit does not store the DASH player indicated by the DASH player information, the control unit instructs the demultiplexing unit to acquire the DASH player indicated by the DASH player information, and the DASH player storage unit stores the DASH player acquired by the demultiplexing unit.

In another aspect of the present invention, the receiving device described above includes a communication unit that communicates with other devices via an IP (Internet Protocol) network, and when the device itself does not have the DASH player indicated by the DASH player information and the communication unit can communicate with the other device that has the DASH player indicated by the DASH player information, the control unit instructs the communication unit to acquire the DASH player indicated by the DASH player information.

In another aspect of the present invention, the receiving device described above includes a DASH player storage unit, and the DASH player information further includes the version number of the latest DASH player. When the device does not have the latest DASH player, the control unit instructs the demultiplexing unit to acquire the latest DASH player from the signal, and the DASH player storage unit stores the DASH player acquired by the demultiplexing unit.

In another aspect of the present invention, the receiving device described above includes a communication unit that communicates with other devices via an IP (Internet Protocol) network, and when the device itself does not have the latest DASH player and the communication unit can communicate with the other device that has the latest DASH player, the control unit instructs the communication unit to acquire the latest DASH player.

Another aspect of the present invention is a transmitting device that includes a multiplexing unit that multiplexes content with DASH player information indicating the DASH player required to play the content to generate a single stream, and a transmitting unit that converts the stream into a television broadcast signal and transmits it.

In another aspect of the present invention, in the above-mentioned transmission device, the DASH player information includes information indicating the name of the DASH player and information indicating the range of version numbers of the DASH player that can play the content.

In another aspect of the present invention, in the above-mentioned transmission device, the DASH player information includes information indicating the identification number of the DASH player and information indicating the range of version numbers of the DASH player that can play the content.

In another aspect of the present invention, in the above-mentioned transmitting device, the DASH player information includes information indicating at least one of the category, profile, and level of receiving devices capable of playing the content, and information indicating the range of version numbers of the DASH players capable of playing the content.

Another aspect of the present invention is a transmission/reception system including the above-mentioned receiving device and the above-mentioned transmitting device.

Another aspect of the present invention is a receiving method using a receiving device, comprising the steps of receiving a television broadcast signal, acquiring content and DASH player information indicating a DASH player required to play the content from the signal, and, if the device itself has the DASH player indicated by the DASH player information, reading out the DASH player.

Another aspect of the present invention is a transmission method using a transmitting device, which includes the steps of multiplexing content with DASH player information indicating the DASH player required to play the content to generate a single stream, and converting the stream into a television broadcast signal and transmitting it.

Another aspect of the present invention is a program for causing a computer to function as a tuner unit that receives television broadcast signals, a demultiplexer unit that acquires content and DASH player information indicating the DASH player required to play the content from the signals, and a control unit that, when the computer itself has a DASH player indicated by the DASH player information, reads the DASH player it has.

Another aspect of the present invention is a program that causes a computer to function as a multiplexing unit that multiplexes content with DASH player information indicating the DASH player required to play the content to generate a single stream, and as a sending unit that converts the stream into a television broadcast signal and sends it out.

This invention reduces the time between when a viewer selects a channel and when the video is displayed.

1 is a schematic block diagram showing an example of the configuration of a television broadcast transmission/reception system 10 according to a first embodiment of the present invention. FIG. 2 is a schematic diagram illustrating an example of a television broadcast signal in the embodiment. 10 is a table showing an example of the configuration of an MPT in the embodiment. 10 is a table showing the configuration of DASH player information in the same embodiment. 10 is a flowchart illustrating a reception start process performed by a browser unit 106 in the embodiment. 10 is a table showing the configuration of DASH player information in the second embodiment of the present invention. 10 is a flowchart illustrating a reception start process by a browser unit 106 in the embodiment. 13 is a table showing the configuration of DASH player information in the third embodiment of the present invention. FIG. 2 is a schematic diagram illustrating an example of a television broadcast signal in the embodiment. 10 is a flowchart illustrating a reception start process by a browser unit 106 in the embodiment.

First Embodiment
Hereinafter, embodiments of the present invention will be described with reference to the drawings. A television broadcast transmission/reception system 10 in a first embodiment includes both television broadcast networks such as terrestrial broadcast networks, satellite broadcast networks, and cable television networks, and content distribution via IP (Internet Protocol) networks such as the Internet. In this embodiment, streaming distribution using MPEG-DASH, which has traditionally been used on IP networks, is also used on television broadcast networks. In MPEG-DASH, content reception and playback are controlled by the receiving side executing a program called a DASH player, written in Javascript or the like.

FIG. 1 is a schematic block diagram showing an example configuration of a television broadcast transmission/reception system 10 according to a first embodiment of the present invention. The transmission/reception system 10 includes a receiving device 100, a transmitting device (broadcasting system) 200, a network 300, a DASH server 400, a streaming server 500, and a display device 600. The receiving device 100 is capable of receiving both television broadcasts from the transmitting device 200 and streaming services from the streaming server 500. The receiving device 100 is installed, for example, in the residence of a television broadcast viewer. The transmitting device 200 transmits television broadcast signals via a terrestrial broadcast network, satellite broadcast network, cable television network, or the like. This signal is an MMT (MPEG Media Transport) stream in which, for example, video, audio, closed captions, control information (signaling information), and the like are multiplexed. Note that MMT is standardized as MPEG-H Part 1 by ISO/IEC 23008-1. Furthermore, the transmitting device 200 is installed, for example, at a broadcasting company that broadcasts television programs.

Network 300 is an IP network such as the Internet. In response to a request from receiving device 100, DASH server 400 transmits a DASH player to receiving device 100 via network 300. Streaming server 500 performs MPEG-DASH streaming distribution to receiving device 100 via network 300. Display device 600 has video display means such as a liquid crystal display or organic EL (Electro Luminescence) display, and audio output means such as a speaker, and displays video and outputs audio in accordance with the video and audio signals output by receiving device 100. Note that in this embodiment, display device 600 is separate from receiving device 100, but it may also be built into receiving device 100.

The receiving device 100 includes a tuner unit 101, a demultiplexing unit 102, a decoder unit 103, a DASH player storage unit 104, a network I/F unit 105, a browser unit 106, and a DASH player execution unit 107. The tuner unit 101 receives television broadcast signals transmitted by the transmitting device 200.

The demultiplexing unit 102 separates and acquires content and DASH player information indicating the DASH player required to play the content from the signal received by the tuner unit 101. The content includes at least one of video, audio, and closed captions. The DASH player information is located in control information such as the MPT (MMT Package Table) and SDT (Service Description Table). The DASH player information also includes information indicating the name (file name) and version number of the DASH player capable of playing the corresponding content. The corresponding content may be indicated, for example, by the location where the DASH player information is located in the control information. For example, when DASH player information is located in the MPT, the content indicated by the MMT package ID written in the MPT is the corresponding content. The demultiplexing unit 102 also separates and acquires the DASH player from the signal received by the tuner unit 101 based on instructions from the browser unit 106 (control unit).

The DASH player storage unit 104 stores DASH players acquired by the demultiplexing unit 102. The DASH player storage unit 104 also supplies the stored DASH players based on requests from the browser unit 106. The network I/F unit 105 (communication unit) communicates with the DASH server 400 and streaming server 500 via the network 300.

The browser unit 106 is a browser for HTML (Hyper Text Markup Language), BML (Broadcast Markup Language), etc., and also controls the acquisition of DASH players. For example, if the DASH player indicated by the DASH player information acquired by the demultiplexing unit 102 is stored in the browser unit 106's own device (DASH player storage unit 104), the browser unit 106 reads out the stored DASH player and causes the DASH player execution unit 107 to execute it. Furthermore, if the DASH player indicated by the DASH player information is not stored in the browser unit 106's own device (DASH player storage unit 104), the browser unit 106 downloads the DASH player from a television broadcast signal or the DASH server 400.

The DASH player execution unit 107 executes the DASH player and instructs the demultiplexing unit 102 and network I/F unit 105 on the video, audio, and closed captions to be acquired. The DASH player execution unit 107 decodes the video, audio, and closed captions acquired via the demultiplexing unit 102 and network I/F unit 105, and the decoder unit 103 decodes the video, audio, and closed captions acquired via the demultiplexing unit 102 and network I/F unit 105 to generate video and audio signals, which are then output to the display device 600.

Transmitting device 200 comprises a content generation unit 201, an SI (Signaling Information) generation unit 202, a multiplexing unit 203, and a sending unit 204. The content generation unit 201 generates content such as video, audio, and closed captions. Note that a DASH player may be included in the content. The SI generation unit 202 generates control information including DASH player information. For example, the SI generation unit 202 generates control information in MMT-SI format, such as MPT, SDT, or PAT (Package Access Table). The multiplexing unit 203 multiplexes the content generated by the content generation unit 201 and the control information generated by the SI generation unit 202 to generate a single stream. The sending unit 204 converts the stream generated by the multiplexing unit 203 into a television broadcast signal and sends it to receiving device 100.

Figure 2 is a schematic diagram illustrating an example of a television broadcast signal in this embodiment. Each rectangle in Figure 2 represents a packet storing data. Packet V stores encoded video. Packet A stores encoded audio. Packet V stores encoded video. Packet D stores a DASH player. Packet M stores control information such as an MPT that includes DASH player information. Television broadcast signals in this embodiment are streams such as MMT, and as shown in Figure 2, each is composed of packets storing video, audio, a DASH player, control information, etc. Figure 2 shows packets storing video, audio, a DASH player, and control information, but packets storing other data may also be included, or packets storing video or audio may not be included. Furthermore, the size (duration) of the packets may be the same or different.

In this way, packets containing DASH players are repeatedly distributed at time intervals. For this reason, when receiving device 100 acquires a DASH player from a television broadcast signal at the timing when a viewer selects a channel, it must wait until the packet containing the DASH player is distributed before it can acquire the player. The DASH player may also be stored in multiple packets. In this case, receiving device 100 cannot acquire the DASH player until all of the multiple packets into which the DASH player was divided and stored are distributed. Therefore, in this embodiment, the same DASH player is used across events (programs, content), such as using the same DASH player within a package (channel, service), and once acquired, it is stored in DASH player storage unit 104.

The broadcasting company then includes DASH player information indicating the DASH player required to play the current event in the MPT distributed in package units. The browser unit 106 references this DASH player information, and if a corresponding DASH player is stored in the DASH player storage unit 104 within its own device, it reads the DASH player from the DASH player storage unit 104 and has the DASH player execution unit 107 execute that DASH player. As a result, if a corresponding DASH player is stored in the DASH player storage unit 104, the content can be displayed without waiting for the DASH player to be distributed.

Figure 3 is a table showing an example of the configuration of an MPT in this embodiment. Figure 3 shows an excerpt from the beginning to the middle of the MPT configuration. In Figure 3, the Data Structure column shows the names of the data structures that make up the MPT. The Bit Count column shows the number of bits in each data structure. The Data Notation column shows the data notation for each data structure. The data notation "uimsbf" is an abbreviation for "unsigned integer most significant bit first." "bslbf" is an abbreviation for "bit string, left bit first." "char" is an abbreviation for "character."

As shown in Figure 3, the beginning of the MPT contains an 8-bit "table_id" indicating that this table is an MPT. This is followed by an 8-bit "version" indicating the version of the MPT, a 16-bit "length" indicating the length (number of bytes) of the MPT, a 6-bit "reserved" reserved bit, a 2-bit "MPT_mode" indicating the processing order when the MPT is divided into subsets, an 8-bit "MMT_package_id_length" indicating the length (number of bytes) of the MMT package ID, "MMT_package_id_byte" indicating each byte that makes up the MMT package ID for the length of the MMT package ID, a 16-bit "MPT_descriptors_length" indicating the length (number of bytes) of the MPT descriptor, "MPT_descriptors_byte" indicating each byte that makes up the MPT descriptor for the length of the MPT descriptor, and an 8-bit "number_of_assets" indicating the number of assets. Next, information about the number of assets indicated by "number_of_assets" is placed, but we will not go into detail here.

Here, an example will be described in which DASH player information is placed as an MPT descriptor. That is, an example will be described in which it is placed in an area configured by "MPT_descriptors_byte" in Figure 3, also known as the first loop. Figure 4 is a table showing the configuration of DASH player information in this embodiment. In this embodiment, the DASH player information is an MPEG_DASH_Player descriptor (MPEG_DASH_Player_Descriptor), which is an MPT descriptor. As shown in Figure 4, the MPEG_DASH_Player descriptor contains "descriptor_tag", "descriptor_length", "MPEG_DASH_Player_Name_length", "MPEG_DASH_Player_Name_byte", "MPEG_DASH_Player_Version_length", "MPEG_DASH_Player_Latest_Version_byte", and "MPEG_DASH_Player_Capability_Version_byte". Note that the number of bits and data notation shown in Figure 4 are examples, and other number of bits and data notation may be used. Also, the order of the items included in the MPEG_DASH_Player descriptor is an example, and other orders may be used, and not all items may be included.

"descriptor_tag" indicates that the descriptor is an MPEG_DASH_Player descriptor. "descriptor_length" indicates the length (number of bytes) of the descriptor. "MPEG_DASH_Player_Name_length" indicates the length (number of bytes) of the DASH player name (file name). "MPEG_DASH_Player_Name_byte" is placed for the length of the DASH player name, and stores the name of a DASH player that can play the program corresponding to the MPT in which the descriptor is stored.

"MPEG_DASH_Player_Version_length" indicates the length (number of bytes) of the DASH player's version number. "MPEG_DASH_Player_Latest_Version_byte" is allocated for the length of the DASH player's version number and stores the latest version number of the DASH player. "MPEG_DASH_Player_Capability_Version_byte" is allocated for the length of the DASH player's version number and indicates the oldest (smallest) version number of the DASH player that can play the program corresponding to the MPT in which this descriptor is stored.

Figure 5 is a flowchart illustrating the reception start process performed by the browser unit 106 in this embodiment. When the viewer selects a channel package, for example, and the receiving device 100 starts receiving a television broadcast, the browser unit 106 acquires DASH player information (step Sa1). Note that this DASH player information is separated by the demultiplexer unit 102 from the signal received by the tuner unit 101.

Next, the browser unit 106 determines whether the DASH player storage unit 104 holds a DASH player whose name matches the name of the DASH player indicated by the DASH player information (step Sa2). If it is determined that a matching DASH player is held (step Sa2-Yes), the browser unit 106 determines whether the version number of the DASH player determined to match in step Sa2 is the same as or newer than the oldest (smallest) version number of the playable DASH player indicated by the DASH player information (step Sa3).

If it is determined that the version number is the same or newer (step Sa3 - Yes), the browser unit 106 acquires the DASH player from the DASH player storage unit 104 and has the DASH player execution unit 107 execute it, thereby starting reception and playback of the package (step Sa5).

On the other hand, if it is determined in step Sa2 that the DASH player storage unit 104 does not hold a DASH player with a matching name (step Sa2—No), or if it is determined in step Sa3 that the version number is not the same or newer (step Sa3—No), the browser unit 106 downloads the DASH player indicated by the DASH player information (step Sa4). This download may be performed from the television broadcast signal by instructing the demultiplexing unit 102 by the browser unit 106, or from the DASH server 400 via the network I/F unit 105. The viewer may be able to set whether to prioritize the television broadcast signal or the DASH server 400, or the television broadcast signal or the DASH server 400 may be prioritized. The DASH player to be downloaded may be the one with the latest version number, but any version number that allows playback may be used. Once the DASH player is downloaded, the browser unit 106 causes the DASH player execution unit 107 to execute the DASH player, thereby starting reception and playback of the package (step Sa5). The downloaded DASH player is stored in the DASH player storage unit 104 in association with its name and version number.

After starting package reception and playback in step Sa5, the browser unit 106 determines whether the DASH player being executed matches the latest version indicated by the DASH player information (step Sa6). If it is determined that they match (step Sa6 - Yes), the browser unit 106 ends the reception start process. On the other hand, if it is determined that they do not match (step Sa6 - No), the browser unit 106 downloads the DASH player with the latest version number indicated by the DASH player information (step Sa7).

As with step Sa4, this download may be performed from the television broadcast signal, or from the DASH server 400. The viewer may be able to set whether to give priority to the television broadcast signal or the DASH server 400, or priority may be given to the television broadcast signal or the DASH server 400. After downloading the DASH player, the browser unit 106 ends the reception start process. The downloaded DASH player is stored in the DASH player storage unit 104 in association with its name and version number.

As such, the receiving device 100 in this embodiment comprises a tuner unit 101 that receives television broadcast signals, a demultiplexing unit 102 that acquires content and DASH player information indicating the DASH player required to play the content from the television broadcast signals, and a browser unit 106 that executes the DASH player stored on the device when the device itself has the DASH player indicated by the DASH player information. As a result, when the device itself has the DASH player required to play the content, there is no need to download it, which reduces the time between the viewer selecting a channel and the video being displayed.

Second Embodiment
In the first embodiment, a case where the DASH player information includes the name of the DASH player is described. In the second embodiment, a case where the DASH player information includes the identification number of the DASH player is described. In the following, only the parts of this embodiment that are different from the first embodiment are described. As the other parts are the same as those in the first embodiment, description thereof will be omitted.

Figure 6 is a table showing the configuration of DASH player information in this embodiment. In this embodiment, as in Figure 4, the DASH player information is an MPEG_DASH_Player descriptor, but it also has a 16-bit "MPEG_DASH_Player_ID." It does not have the "MPEG_DASH_Player_Name_length" and "MPEG_DASH_Player_Name_byte" that were present in Figure 4. The "MPEG_DASH_Player_ID" is an identification number for identifying the DASH player. This identification number may be the identification number of a television broadcast channel or the identification number of a television broadcasting entity. The number of bits and data notation shown in Figure 6 are merely examples, and other numbers of bits and data notations may also be used. The order of the items included in the MPEG_DASH_Player descriptor is also merely an example, and may be in a different order, or may not include all items.

Figure 7 is a flowchart explaining the reception start processing by the browser unit 106 in this embodiment. The only difference from the flowchart in Figure 7 is that it includes step Sb2 instead of step Sa2. In step Sb2, the browser unit 106 determines whether the DASH player storage unit 104 holds a DASH player whose identification number matches the DASH player identification number indicated by the DASH player information.

In this way, in this embodiment, an identification number is used instead of the name of the DASH player. As in the first embodiment, in this embodiment, the time from when a viewer selects a channel until the video is displayed can be reduced.
Furthermore, since the identification number can be the identification number of a television broadcast channel or the identification number of a television broadcasting business, DASH players can be easily identified between television broadcasting channels or businesses.

Third Embodiment
In the first embodiment, a case where the DASH player information includes the name of the DASH player has been described. In the second embodiment, a case where the DASH player information includes the identification number of the DASH player has been described. In the third embodiment, a case where the DASH player information includes the category, profile, and level of a receiving device capable of reproducing the content will be described. In the following, only the parts of this embodiment that are different from the first embodiment will be described. As the other parts are the same as those in the first embodiment, description thereof will be omitted.

Figure 8 is a table showing the configuration of DASH player information in this embodiment. In this embodiment, as in Figure 4, the DASH player information is an MPEG_DASH_Player descriptor, but it has an 8-bit "MPEG_DASH_Player_Category", an 8-bit "MPEG_DASH_Player_Profile", and an 8-bit "MPEG_DASH_Player_Level". However, it does not have the "MPEG_DASH_Player_Name_length" and "MPEG_DASH_Player_Name_byte" that were present in Figure 4.

"MPEG_DASH_Player_Category" indicates the category of receiving device 100 that can play content using the DASH player information. The category indicates the type of receiving device 100 (set-top box, portable terminal, etc.). "MPEG_DASH_Player_Profile" indicates the profile of receiving device 100 that can play content using the DASH player information. Here, the profile indicates the functions possessed by the receiving device (such as the encoding method that can be decoded, whether or not it is connected to the Internet, etc.). "MPEG_DASH_Player_Level" indicates the level (performance) of receiving device 100 that can play content using the DASH player information.

"MPEG_DASH_Player_Category", "MPEG_DASH_Player_Profile", and "MPEG_DASH_Player_Level" may each be in bitmap format. For example, each bit that makes up "MPEG_DASH_Player_Category" corresponds to one category, and multiple categories may be indicated by setting multiple bits to 1. The same applies to "MPEG_DASH_Player_Profile" and "MPEG_DASH_Player_Level".

Note that the number of bits and data notation shown in Figure 8 are merely examples, and other number of bits and data notation may be used. Furthermore, the order of the items included in the MPEG_DASH_player descriptor is also merely an example, and other orders may be used, or not all items may be included. Furthermore, multiple MPEG_DASH_player descriptors may be placed within control information such as the MPT and SDT as DASH player information corresponding to a single piece of content. The browser unit 106 of the receiving device 100 references the MPEG_DASH_player descriptor that matches the category/profile/level of its own device to determine which DASH players are capable of playback.

Figure 9 is a schematic diagram illustrating an example of a television broadcast signal in this embodiment. It differs from Figure 2 in that packets D1 and D2 are included instead of packet D. The DASH player stored in packet D1 is different from the DASH player stored in packet D2. For example, they differ in at least one of the category, profile, and level of the target receiving device 100.

Figure 10 is a flowchart illustrating reception start processing by the browser unit 106 in this embodiment. The flowchart in Figure 10 differs only in that it has steps Sc1 and Sc2 instead of step Sa1, and step Sc3 instead of step Sa2. In step Sc1, the browser unit 106 acquires the category, profile, and level of the receiving device 100 (its own device). In step Sc2, the browser unit 106 acquires DASH player information that matches the category, profile, and level of its own device. In step Sc3, the browser unit 106 determines whether the DASH player storage unit 104 holds a DASH player whose identification number matches the DASH player identification number indicated in the DASH player information.

In this way, in this embodiment, instead of the name of the DASH player, the category, profile, and level are used. As in the first embodiment, in this embodiment, the time from when a viewer selects a channel until the video is displayed can be reduced.
In addition, the DASH player can be changed depending on the category, profile, and level of the receiving device 100.

In addition, a program for realizing the functions of receiving device 100 or transmitting device 200 in Figure 1 may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read into a computer system and executed to realize receiving device 100 or transmitting device 200. Note that the term "computer system" here may be composed of multiple computers and also includes hardware such as an OS and peripheral devices.

In addition, "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into computer systems. Furthermore, "computer-readable recording medium" also includes devices that dynamically store programs for a short period of time, such as communication lines used when transmitting programs over networks like the Internet or communication lines like telephone lines, and devices that store programs for a fixed period of time, such as volatile memory within computer systems that serve as servers or clients in such cases. Furthermore, the above-mentioned programs may be those that implement some of the functions described above, or may be those that can implement the functions described above in combination with programs already stored in the computer system.

Furthermore, each functional block of the receiving device 100 or transmitting device 200 in FIG. 1 may be individually formed into a chip, or some or all of them may be integrated into a chip. The integrated circuit method is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor. Either a hybrid or monolithic method is also acceptable. Some functions may be realized by hardware and some by software.
Furthermore, with the advancement of semiconductor technology, if a technology for integrated circuitry that can replace LSIs emerges, it may be possible to use an integrated circuit based on that technology.

The above describes an embodiment of the present invention in detail with reference to the drawings, but the specific configuration is not limited to this embodiment and includes design modifications and the like that do not deviate from the gist of the present invention.

10...Transmission and Reception System 100...Receiving Device 101...Tuner Unit 102...Demultiplexing Unit 103...Decoder Unit 104...DASH Player Storage Unit 105...Network I/F Unit 106...Browser Unit 107...DASH Player Execution Unit 200...Transmitting Device 201...Content Generation Unit 202...SI Generation Unit 203...Multiplexing Unit 204...Sending Unit 300...Network 400...DASH Server 500...Streaming Server 600...Display Device

Claims (14)

a tuner unit for receiving television broadcast signals;
a demultiplexing unit that acquires content and DASH player information indicating a DASH player required to play the content from the signal;
a control unit that reads out the DASH player held by the device itself when the DASH player indicated by the DASH player information is held by the device itself;
Equipped with
A receiving device, wherein the DASH player information includes information indicating the name of the DASH player and information indicating a range of version numbers of the DASH player that can play the content. a tuner unit for receiving television broadcast signals;
a demultiplexing unit that acquires content and DASH player information indicating a DASH player required to play the content from the signal;
a control unit that reads out the DASH player held by the device itself when the DASH player indicated by the DASH player information is held by the device itself;
Equipped with
A receiving device, wherein the DASH player information includes information indicating an identification number of the DASH player and information indicating a range of version numbers of the DASH player that can play back the content. a tuner unit for receiving television broadcast signals;
a demultiplexing unit that acquires content and DASH player information indicating a DASH player required to play the content from the signal;
a control unit that reads out the DASH player held by the device itself when the DASH player indicated by the DASH player information is held by the device itself;
Equipped with
A receiving device, wherein the DASH player information includes information indicating at least one of a category, profile, and level of a receiving device capable of playing the content, and information indicating a range of version numbers of the DASH player capable of playing the content. A DASH player storage unit is provided,
When the control unit does not have the DASH player indicated by the DASH player information, the control unit instructs the demultiplexing unit to acquire the DASH player indicated by the DASH player information;
The receiving device according to claim 1 , wherein the DASH player storage unit holds the DASH player acquired by the demultiplexing unit. a communication unit that communicates with other devices via an IP (Internet Protocol) network;
The control unit
5. The receiving device according to claim 4, wherein when the device itself does not have the DASH player indicated by the DASH player information and the communication unit is capable of communicating with the other device that has the DASH player indicated by the DASH player information, the receiving device instructs the communication unit to acquire the DASH player indicated by the DASH player information. A DASH player storage unit is provided,
The DASH player information further includes a latest DASH player version number;
When the control unit does not have the latest DASH player, the control unit instructs the demultiplexing unit to acquire the latest DASH player from the signal;
The receiving device according to claim 1 , wherein the DASH player storage unit holds the DASH player acquired by the demultiplexing unit. a communication unit that communicates with other devices via an IP (Internet Protocol) network;
The control unit
The receiving device according to claim 6, wherein when the device itself does not have the latest DASH player and the communication unit can communicate with the other device that has the latest DASH player, the receiving device instructs the communication unit to acquire the latest DASH player. a multiplexing unit that multiplexes the content with DASH player information indicating a DASH player required for playback of the content to generate one stream;
a transmitting unit that converts the stream into a television broadcast signal and transmits it;
Equipped with
A transmitting device, wherein the DASH player information includes information indicating the name of the DASH player and information indicating a range of version numbers of the DASH player that can play the content. a multiplexing unit that multiplexes the content with DASH player information indicating a DASH player required for playback of the content to generate one stream;
a transmitting unit that converts the stream into a television broadcast signal and transmits it;
Equipped with
A transmitting device, wherein the DASH player information includes information indicating an identification number of the DASH player and information indicating a range of version numbers of the DASH player that can play back the content. a multiplexing unit that multiplexes the content with DASH player information indicating a DASH player required for playback of the content to generate one stream;
a transmitting unit that converts the stream into a television broadcast signal and transmits it;
Equipped with
A transmitting device, wherein the DASH player information includes information indicating at least one of a category, profile, and level of a receiving device capable of playing the content, and information indicating a range of version numbers of the DASH player capable of playing the content. A receiving method by a receiving device,
receiving a television broadcast signal;
obtaining content and DASH player information indicating a DASH player required to play the content from the signal;
and when the device itself holds the DASH player indicated by the DASH player information, reading out the DASH player held by the device itself ,
the DASH player information includes information indicating a range of version numbers of the DASH player capable of playing the content;
A receiving method, wherein the DASH player information further includes information indicating the name of the DASH player, information indicating an identification number of the DASH player, or information indicating at least one of a category, profile, and level of a receiving device capable of playing the content . A transmission method by a transmitting device,
a step of multiplexing the content with DASH player information indicating a DASH player required for playing the content to generate one stream;
and transmitting the stream as a television broadcast signal ,
the DASH player information includes information indicating a range of version numbers of the DASH player capable of playing the content;
A transmission method in which the DASH player information further includes information indicating the name of the DASH player, information indicating the identification number of the DASH player, or information indicating at least one of the category, profile, and level of a receiving device that can play the content . Computer,
a tuner unit for receiving television broadcast signals;
a demultiplexing unit that acquires, from the signal, the content and DASH player information indicating a DASH player required to play the content;
a program for causing the device to function as a control unit that reads out the DASH player held by the device itself when the device itself holds the DASH player indicated by the DASH player information ,
the DASH player information includes information indicating a range of version numbers of the DASH player capable of playing the content;
The DASH player information further includes information indicating the name of the DASH player, information indicating the identification number of the DASH player, or information indicating at least one of the category, profile, and level of a receiving device capable of playing the content . Computer,
a multiplexing unit that multiplexes the content with DASH player information indicating a DASH player required for playing the content to generate one stream;
a program for causing the stream to function as a sending unit that converts the stream into a television broadcast signal and sends it out ,
the DASH player information includes information indicating a range of version numbers of the DASH player capable of playing the content;
The DASH player information further includes information indicating the name of the DASH player, information indicating the identification number of the DASH player, or information indicating at least one of the category, profile, and level of a receiving device capable of playing the content .