WO2018180572A1

WO2018180572A1 - Information processing apparatus, reception apparatus, and information processing method

Info

Publication number: WO2018180572A1
Application number: PCT/JP2018/010390
Authority: WO
Inventors: 山岸　靖明
Original assignee: ソニー株式会社
Priority date: 2017-03-31
Filing date: 2018-03-16
Publication date: 2018-10-04
Also published as: JP7160030B2; JPWO2018180572A1

Abstract

The present technology relates to an information processing apparatus, a receive apparatus, and an information processing method for making it possible to perform multicast delivery via broadcast-synchronized communication. The information processing apparatus reserves a multicast session in advance for a communication content which is multicast-delivered simultaneously with a broadcast content, and, in response to a communication content request, transfers the communication content for delivery using the multicast session to a request source. The present technology may be applied in an apparatus for transferring a multicast-delivered content, for example.

Description

Information processing apparatus, receiving apparatus, and information processing method

The present technology relates to an information processing device, a receiving device, and an information processing method, and more particularly, to an information processing device, a receiving device, and an information processing method capable of performing multicast distribution via communication synchronized with broadcasting.

As a system for distributing content, a technique for performing multicast distribution via a broadband network capable of simultaneous broadcast distribution in addition to unicast distribution has been proposed (for example, see Patent Document 1).

Japanese Patent Laying-Open No. 2015-192407

By the way, a multicast distribution method via a broadband network synchronized with broadcasting such as terrestrial broadcasting has begun to be studied, but the technical method has not been established, and a method for performing multicast distribution via communication synchronized with broadcasting. Proposals have been requested.

This technology has been made in view of such a situation, and enables multicast distribution via communication synchronized with broadcasting to be performed.

The information processing apparatus according to the first aspect of the present technology reserves in advance a multicast session of communication content that is multicast distributed simultaneously with broadcast content, and is distributed using the multicast session when the communication content is requested. The information processing apparatus includes a processing unit that transfers the communication content to the request source.

The information processing apparatus according to the first aspect of the present technology may be an independent apparatus or may be an internal block constituting one apparatus. The information processing method according to the first aspect of the present technology is an information processing method corresponding to the information processing apparatus according to the first aspect of the present technology described above.

In the information processing apparatus and the information processing method according to the first aspect of the present technology, when a multicast session of communication content to be multicast distributed simultaneously with broadcast content is reserved in advance and the communication content is requested, the multicast session The communication content distributed using is transferred to the request source.

A receiving device according to a second aspect of the present technology includes a first receiving unit that receives broadcast content transmitted as a broadcast wave, and second reception that receives communication content distributed by multicast via a communication network. And a request to start a multicast session of the communication content that is multicast-delivered simultaneously with the broadcast content at a first timing, and at a second timing that is later in time than the first timing. And a processing unit that requests content.

The receiving device according to the second aspect of the present technology may be an independent device, or may be an internal block constituting one device. Moreover, the information processing method of the 2nd side surface of this technique is an information processing method corresponding to the receiver of the 2nd side surface of this technique mentioned above.

In the reception device and the information processing method according to the second aspect of the present technology, the broadcast content transmitted as a broadcast wave is received, the communication content distributed by multicast is received via the communication network, and the first At the timing, the start of a multicast session of the communication content that is multicast-delivered simultaneously with the broadcast content is requested, and the communication content is requested at a second timing that is later in time than the first timing.

According to the first aspect and the second aspect of the present technology, multicast distribution via communication synchronized with broadcasting can be performed.

It should be noted that the effects described here are not necessarily limited, and may be any of the effects described in the present disclosure.

It is a figure showing an example of composition of a contents distribution system to which this art is applied. It is a figure which shows the example of a display of the screen in a broadcast receiving device. It is a block diagram which shows the structural example of a broadcast receiving device. It is a block diagram which shows the detail of a structure of a process part. It is a block diagram which shows the structural example of a multicast termination | terminus device. It is a figure which shows the example of the content of the nmc.sdp file. It is a figure which shows the example of description of sdp. It is a figure which shows the example of the message in the case of sending the contents of a nmc.sdp file by http-post. It is a figure which shows the example of the message in the case of sending nmc.sdp file URL by http-post. It is a figure which shows the example in the case of sending the content of SDP as a URL query character string of http-get. It is a flowchart explaining the flow of a process with a 1st delivery system. It is a flowchart explaining the flow of a process with a 1st delivery system. It is a figure explaining a multicast reservation notification function. It is a figure explaining a multicast cancellation | release notification function. It is a figure which shows the example of the structure of MIT. It is a figure which shows the example of PID allocated to MIT. It is a figure which shows the example of table ID allocated to MIT. It is a figure which shows the example of the structure of a multicast session descriptor. It is a figure which shows the example of the tag value of a multicast session descriptor. It is a flowchart explaining the flow of a process with a 2nd delivery system. It is a flowchart explaining the flow of a process with a 2nd delivery system. It is a flowchart explaining the flow of a process with a 3rd delivery system. It is a flowchart explaining the flow of a process with a 4th delivery system. It is a flowchart explaining the flow of a process with a 4th delivery system. It is a flowchart explaining the flow of a process with a 5th delivery system. It is a flowchart explaining the flow of a process with a 5th delivery system. It is a flowchart explaining the flow of a process by the 6th delivery system. It is a flowchart explaining the flow of a process with a 7th delivery system. It is a flowchart explaining the flow of a process with a 7th delivery system. It is a flowchart explaining the flow of a process with a 7th delivery system. It is a figure which shows the example of a 1st stack structure. It is a figure which shows the example of a 2nd stack structure. It is a figure which shows the example of a 3rd stack structure. It is a figure which shows the example of a 4th stack structure. It is a figure which shows the example of a 5th stack structure. It is a figure which shows the example of a 6th stack structure. It is a figure which shows the example of a 7th stack structure. It is a figure which shows the example of an 8th stack structure. It is a figure which shows the example of a 9th stack structure. It is a figure which shows the example of a 10th stack structure. It is a figure which shows the example of an 11th stack structure. It is a figure which shows the example of a 12th stack structure. It is a figure which shows the structural example of a computer.

Hereinafter, embodiments of the present technology will be described with reference to the drawings. The description will be made in the following order.

1. 1. System configuration Multicast distribution method of the present technology (1) First distribution method: Method in which broadcast application promotes multicast participation (2) Second distribution method: Method in which broadcast signaling prompts multicast participation (3) Third distribution method: All (4) Fourth distribution method: a method in which a broadcast application encourages multicast participation when multicast distribution signaling is distributed in multicast (5) Fifth distribution method: broadband distribution signaling is unicast distribution (6) Sixth distribution method: a method in which broadcast signaling prompts multicast participation when broadband distribution signaling is unicast distributed (7) Seventh distribution method : Broadband content Method 3 for switching the delivery form, to the multicast distribution from unicast distribution. 3. Protocol stack configuration of the present technology Modification 5 Computer configuration

<1. System configuration>

(Configuration example of content distribution system)
FIG. 1 is a diagram illustrating a configuration example of a content distribution system to which the present technology is applied.

The content distribution system 1 in FIG. 1 is a system for distributing content via a broadband network synchronized with broadcasting such as terrestrial broadcasting.

In FIG. 1, a content distribution system 1 includes a broadcast content management system 10, a terrestrial broadcast stream server 20, a terrestrial broadcast server 30, a broadband stream server 40, a broadband server 50, a broadcast receiving device 60, and a multicast termination device 70. Consists of

In FIG. 1, the terrestrial broadcast server 30 and the broadcast receiving device 60 perform data transmission in one direction via the terrestrial broadcast network 2. In addition, the broadband server 50 and the multicast termination device 70 perform bidirectional data transmission via the broadband network 3.

In the broadband network 3, a plurality of routers such as multicast relay routers 80-1 to 80-5 are provided. The plurality of routers relay data between different networks constituting the broadband network 3 based on the routing table.

As the broadband network 3, for example, a communication network (communication line) such as NGN (Next Generation Network) provided by a communication carrier such as a fixed telephone or a mobile phone can be used.

The broadcast content management system 10 generates content and provides it to the stream server 20 for terrestrial broadcasting and the stream server 40 for broadband. Here, as the content, for example, a broadcast program that can be distributed together with a multicast program and a program that is a source of the multicast combined distribution program are generated.

Also, the broadcast content management system 10 generates data such as a broadcast application and signaling, and provides the data to the stream server 20 for terrestrial broadcasting.

Here, the broadcast application is an application distributed via broadcast, and can be developed in a markup language such as HTML5 (HyperTextHMarkup Language 5) or a script language such as JavaScript (registered trademark). For example, the broadcast application can be a web application such as a hybrid cast application. Signaling is control information processed on the broadcast receiving device 60 side.

The terrestrial broadcast stream server 20 processes the content provided from the broadcast content management system 10 (for example, processing such as encoding), generates a broadcast distribution stream, and provides it to the terrestrial broadcast server 30.

The terrestrial broadcast server 30 processes the broadcast distribution stream provided from the terrestrial broadcast stream server 20 and the broadcast application and signaling data provided from the broadcast content management system 10 (for example, processing such as multiplexing). . The terrestrial broadcast server 30 transmits a multiplexed stream (terrestrial broadcast transport) obtained as a result of the processing.

The multiplexed stream transmitted from the terrestrial broadcast server 30 is received by the broadcast receiving device 60 as a broadcast wave via the terrestrial broadcast network 2 such as a transmitting station or a relay station.

The terrestrial broadcast server 30 is connected to a transmission facility installed at the transmitting station via a predetermined line such as a dedicated line. The transmission facility in the transmitting station applies necessary processing (for example, processing such as modulation) to the data from the terrestrial broadcast server 30, so that a broadcast wave (broadcast signal) obtained as a result is terrestrial broadcast. It is transmitted via the network 2. In the following description, for simplification of description, processing performed by the transmission facility in the transmitting station is omitted.

The broadcast receiving device 60 is, for example, a fixed receiver such as a television receiver, a set top box (STB), a personal computer, or a game machine, or a mobile receiver such as a smartphone, a mobile phone, or a tablet computer. Composed.

The broadcast receiving device 60 may be a wearable computer such as a head-mounted display (HMD). Furthermore, the broadcast receiving device 60 may be a device mounted on an automobile such as an in-vehicle television. As described above, the broadcast receiving device 60 may be any device as long as it can reproduce and record content.

The broadcast receiving device 60 receives broadcast waves transmitted via the terrestrial broadcast network 2 and processes them (for example, processes such as demodulation, demultiplexing, and decoding) to reproduce terrestrial content, The video and audio are output. Here, as the terrestrial content (broadcast content), for example, a broadcast program capable of distributing a combined program by multicast can be reproduced.

Also, the broadcast receiving device 60 can acquire and execute a broadcast application included in a multiplexed stream obtained from a broadcast wave.

On the other hand, the stream server for broadband 40 processes the content provided from the broadcast content management system 10 (for example, processing such as encoding), generates a broadband distribution stream, and provides it to the broadband server 50.

The broadband server 50 processes the broadband distribution stream provided from the broadband stream server 40 (for example, processing such as packetization). The broadband server 50 multicasts an IP stream obtained as a result of the processing.

In addition, although the case where the broadband server 50 performs multicast distribution will be described here, the broadband server 50 can also perform unicast distribution.

The IP multicast stream distributed by multicast from the broadband server 50 is received by the multicast termination device 70 via the plurality of multicast relay routers 80 in the broadband network 3.

The multicast termination device 70 is configured as, for example, a broadband router or gateway, a dedicated server, a television receiver, a set top box (STB), a network storage, a game machine, or the like.

The multicast termination device 70 processes the IP multicast stream received via the plurality of multicast relay routers 80 in the broadband network 3 and transfers the processed IP multicast stream to the broadcast receiving device 60.

Note that the broadcast receiving device 60 and the multicast termination device 70 are connected to each other via a bidirectional network such as a home LAN (Local Area Network) constructed at the end user's home.

The broadcast receiving device 60 receives the IP multicast stream transferred from the multicast terminating device 70, processes it (for example, processes such as depacketization and decoding), reproduces broadband content, and plays the video and audio. Output. Here, as a broadband content (communication content), for example, a multicast combined delivery program can be reproduced.

Here, the broadcast receiving device 60 can reproduce terrestrial content distributed via broadcasting and broadband content distributed via communication (multicast distribution). These contents are shown in FIG. It can be switched in the way shown.

That is, in the broadcast receiving device 60 shown in FIG. 2, A in FIG. 2 schematically represents a state at the time of reproduction of the terrestrial content (broadcast program that can be used together with multicast). FIG. 2B schematically shows a state of reproducing broadband content (multicast combined delivery program).

In FIG. 2A, an image 61A displayed by a broadcast application is superimposed on the video of the terrestrial content, and the end user who confirms the content of the image 61A operates the remote controller or the like to broadcast. In the receiving device 60, the content to be played is switched from, for example, 2K resolution terrestrial content (A in FIG. 2) to 4K resolution broadband content (B in FIG. 2).

On the other hand, in FIG. 2B, an image 61B displayed by the broadcast application is superimposed on the broadband content video, and the end user confirming the content of the image 61B operates the remote controller or the like. In the broadcast receiving device 60, the content to be reproduced is switched from, for example, 4K resolution broadband content (B in FIG. 2) to 2K resolution terrestrial content (A in FIG. 2).

As described above, in the broadcast receiving device 60, transition between streaming distributed via broadcast or streaming distributed via communication is controlled by the broadcast application based on the intention of the end user.

The distribution processing performed in the content distribution system 1 configured as described above is summarized as follows.

That is, first, a broadcast program from the broadcast content management system 10 is transmitted based on predetermined organization information. This broadcast program is encoded for terrestrial broadcast by the stream server 20 for terrestrial broadcast, and is encoded for broadband by the stream server 40 for broadband.

Here, when there is a difference in encoding parameters such as screen resolution between a broadcast distribution stream for terrestrial broadcasting and a broadband distribution stream for broadband, for example, in distribution for terrestrial broadcasting, 2K resolution (2K- MPEG2), and for broadband distribution, it is encoded in a different format to cope with cases such as 4K resolution (4K-HEVC).

The program encoded in this way is transmitted to the terrestrial broadcast network 2 by the terrestrial broadcast server 30 according to the terrestrial broadcast transport protocol, and is also transmitted by the broadband server 50 according to the broadband unicast / multicast transport protocol. And sent to the broadband network 3.

For example, as a terrestrial broadcast transport protocol, in the case of MPEG2-TS / PHY frame, MP4 / MMT / UDP / IP / TLV / PHY frame, MP4 / DASH / ROUTE (FLUTE) / UDP / IP / MPEG2 -TS / PHY frame is applicable.

Also, for example, MP4 / DASH / HTTP / TCP / IP can be applied as a broadband unicast protocol, and MP4 / DASH / ROUTE (FLUTE) / UDP / IP can be applied as a broadband multicast protocol. is there.

Note that “/” means a layer break in the hierarchical structure of the protocol stack, and the left layer with the “/” in between indicates a layer higher than the right layer.

MMT stands for MPEG Media Transport, UDP stands for User Datagram Protocol, IP stands for Internet Protocol, and TLV stands for Type Length Length Value. DASH is an abbreviation for Dynamic-Adaptive-Streaming-over-HTTP, ROUTE is an abbreviation for Real-time Object-Delivery-over Unidirectional Transport, and FLUTE is an abbreviation for File-Delivery-over Unidirectional Transport.

The detailed configuration of these protocol stacks will be described later with reference to FIGS.

In the content distribution system 1 of FIG. 1, for simplicity of explanation, a case where one terrestrial broadcasting server 30 and one broadband server 50 are provided is illustrated. As the broadcast server 30 and the broadband server 50, for example, a plurality of servers can be provided for each provider such as a broadcasting station.

1 shows a case where one broadcast receiving device 60 and one multicast terminating device 70 are provided. As the broadcast receiving device 60 and multicast terminating device 70, FIG. For example, a plurality of devices can be provided for each end user home.

Furthermore, FIG. 1 illustrates a case where the broadcast receiving device 60 and the multicast termination device 70 are configured as separate devices, but an apparatus in which the broadcast reception device 60 and the multicast termination device 70 are integrated (hereinafter, referred to as “device”). It may also be configured as a bundled device).

For example, by providing the multicast termination device 70 as a multicast termination module and including it in the function of the broadcast receiving device 60, it can be configured as a bundled device. In this bundled device, it is not necessary to communicate with each other via, for example, a home LAN.

In the description of FIG. 1 described above, the broadcast receiving device 60 and the multicast termination device 70 have been described as being arranged in the end user's house. However, the multicast termination device 70 is not limited to the end user's house, but may be, for example, a cable operator. It may be installed in a head end of the mobile phone or a base station of a mobile network so that a wider area can be covered.

That is, for example, when the multicast termination device 70 is installed at the cable operator's head end, the broadcast receiving device 60 is installed not at the same end user's house but at each end user's house that has contracted for cable television services. Will be.

Further, for example, when the multicast termination device 70 is installed in a base station of a mobile network, the broadcast receiving device 60 is a device (mobile reception) that an end user with a mobile service contracts possesses indoors or outdoors. Machine).

Furthermore, in the description of FIG. 1 described above, terrestrial broadcasting has been described as a broadcasting method of broadcast content. For example, satellite broadcasting using a broadcasting satellite (BS: Broadcasting Satellite) or a communication satellite (CS: Communications Satellite), Alternatively, broadcast content, broadcast applications, and the like may be distributed by a broadcasting system such as cable broadcasting using a cable (CATV: Common Antenna TeleVision).

(Broadcast receiving device configuration example)
FIG. 3 is a block diagram showing a configuration example of the broadcast receiving device 60 of FIG.

In FIG. 3, the broadcast receiving device 60 includes a processing unit 101, an input unit 102, a storage unit 103, a tuner 104, a broadcast middleware 105, a DASH client 106, a renderer 107, an output unit 108, a browser 109, and a communication I / F 110. Is done.

The processing unit 101 includes, for example, a CPU (Central Processing Unit) and a microprocessor. The processing unit 101 operates as a central processing device in the broadcast receiving device 60 such as various arithmetic processes and operation control of each unit. The processing unit 101 can exchange various data with each unit in the broadcast receiving device 60.

The input unit 102 is, for example, a physical button or the like, and supplies an operation signal corresponding to an end user operation to the processing unit 101. The processing unit 101 controls the operation of each unit based on the operation signal supplied from the input unit 102.

The storage unit 103 includes, for example, a semiconductor memory, a hard disk drive (HDD: Hard Disk Drive), or the like. The storage unit 103 stores various data according to control from the processing unit 101.

The tuner 104 receives and processes the broadcast wave from the terrestrial broadcast network 2 via the antenna 121, and supplies data obtained as a result to the broadcast middleware 105.

The broadcast middleware 105 processes the data supplied from the tuner 104 and supplies it to the processing unit 101, the DASH client 106, or the browser 109 according to the type of data obtained as a result.

Here, the stream data (DASH segment) of the terrestrial content among the data to be processed is supplied to the DASH client 106, and the data of the broadcast application is supplied to the browser 109. Further, the signaling is supplied to the processing unit 101.

The DASH client 106 processes the DASH segment supplied from the broadcast middleware 105 and supplies video and audio data obtained as a result to the renderer 107. Although not described here, video and audio data obtained by processing the DASH segment is supplied to the renderer 107 after being decoded by a decoder.

The renderer 107 performs rendering processing on the video and audio data supplied from the DASH client 106 and supplies the resulting data to the output unit 108.

The output unit 108 outputs video and audio data supplied from the renderer 107. As a result, the broadcast receiving device 60 reproduces the terrestrial content such as a broadcast program that can be distributed together by multicast, and outputs the video and audio.

The browser 109 is a browser that supports, for example, HTML5 and JavaScript (registered trademark). The browser 109 processes broadcast application data (for example, an HTML format file or an image file) supplied from the broadcast middleware 105, and supplies the resulting data to the output unit 108. Thereby, the broadcast receiving device 60 displays the image (video) of the broadcast application.

The communication I / F 110 is composed of a communication interface circuit and the like. The communication I / F 110 exchanges various data with the multicast termination device 70 via a bidirectional network such as a home LAN.

Here, of the data to be received, the broadband content stream data (DASH segment) is supplied to the DASH client 106. When signaling or an application is distributed via communication, the signaling is supplied to the processing unit 101 and the application is supplied to the browser 109.

In addition, since the process with respect to the data acquired via communication is the same as the process with respect to the data acquired via broadcasting, the broadband content acquired via communication is omitted here. By processing this stream data, the broadcast receiving device 60 reproduces broadband content such as a multicast combined delivery program and outputs the video and audio.

It should be noted that terrestrial content and broadband content may be recorded. Further, a display for displaying video and a speaker for outputting sound may be provided outside the broadcast receiving device 60 or provided outside to be supplied with data from the output unit 108.

The broadcast receiving device 60 is configured as described above.

(Configuration of processing unit)
FIG. 4 is a block diagram showing details of the configuration of the processing unit 101 in FIG.

4, the processing unit 101 includes a broadcast control unit 131, a communication control unit 132, a network distribution reservation preparation processing unit 133, and a signaling processing unit 134.

The broadcast control unit 131 controls processing for data acquired via broadcasting, which is performed by each unit in the broadcast receiving device 60. For example, the broadcast control unit 131 controls the tuner 104, the broadcast middleware 105, the DASH client 106, the renderer 107, and the output unit 108 so that the terrestrial content is reproduced.

The communication control unit 132 controls processing for data acquired via communication, which is performed by each unit in the broadcast receiving device 60. For example, the communication control unit 132 controls the communication I / F 110, the DASH client 106, the renderer 107, and the output unit 108 so that broadband content is reproduced.

The net distribution reservation preparation processing unit 133 requests the multicast termination device 70 to start a multicast session of broadband content according to the analysis result of the broadcast application or signaling.

The signaling processing unit 134 processes the signaling acquired by the broadcast middleware 105 and supplies the processing result to the broadcast control unit 131. The broadcast control unit 131 controls the operation of each unit based on the signaling processing result from the signaling processing unit 134.

(Configuration example of multicast termination device)
FIG. 5 is a block diagram illustrating a configuration example of the multicast termination device 70 of FIG.

5, the multicast termination device 70 includes a processing unit 201, a communication I / F 202, and a communication I / F 202.

The processing unit 201 includes, for example, a CPU and a microprocessor. The processing unit 201 operates as a central processing device in the multicast termination device 70 such as various arithmetic processes and operation control of each unit.

The processing unit 201 includes a multicast middleware 231, a web server 232, and a signaling processing unit 233.

The multicast middleware 231 performs processing related to multicast distribution of broadband content.

For example, the multicast middleware 231 reserves a multicast session of broadcast content in advance (participates in multicast) in response to a request from the broadcast receiving device 60, and participates in the multicast session when the broadband content is requested. The broadcast content distributed using is transferred to the requesting broadcast receiving device 60.

Here, on the web server 232, the multicast termination module operates as a server-side script. The multicast middleware 231 exchanges various data with the multicast termination module.

The signaling processing unit 233 acquires and analyzes signaling distributed via the broadband network 3 (broadband distribution signaling). The analysis result of this signaling is supplied to the multicast middleware 231. The multicast middleware 231 reserves a multicast session based on the signaling analysis result.

The communication I / F 202 includes, for example, a communication interface circuit. The communication I / F 202 exchanges various data with the broadcast receiving device 60 via a bidirectional network (for example, a home LAN).

The communication I / F 203 includes, for example, a communication interface circuit, and exchanges various data with the broadband server 50 via the broadband network 3 (multicast relay router 80).

For convenience of explanation, the multicast termination device 70 of FIG. 5 shows a configuration in which two communication I / Fs, a communication I / F 202 and a communication I / F 203, are provided. May be configured as a single communication I / F.

The multicast termination device 70 is configured as described above.

<2. Multicast distribution method of this technology>

By the way, when considering the realization of net multicast terrestrial broadcasting, the study of typical use cases has begun. As a main use case, it is assumed that a broadband content stream with higher image quality than the same program (terrestrial content) is distributed via the broadband network 3 during terrestrial broadcasting. The

In this use case, when the broadband content is distributed via a server on a CDN (Content Delivery Network) provided by a communication carrier such as a fixed telephone or a mobile phone instead of the general Internet, the broadcast receiving device 60 Then, a broadcast application distributed simultaneously with the terrestrial content is started via the terrestrial broadcast network 2 to allow the end user to select whether or not to view the broadband content.

When the end user selects viewing of broadband content, the broadcast application activates, for example, a DASH player (DASH client 106 in FIG. 3), and the DASH player performs multicast termination device 70 (for example, High-quality broadband content is streamed and played back using a unicast protocol such as HTTP via a broadband router.

At this time, when the use of the multicast protocol is assumed in the CDN of the communication carrier, the multicast termination device 70 (for example, a broadband router or the like) must terminate the multicast protocol used in the CDN. The realization method will be studied.

In the present technology, as one implementation method thereof, a method is proposed in which a broadcast application executed by the broadcast receiving device 60 requests a multicast termination device 70 (for example, a broadband router) to start a multicast session.

Note that the broadcast application requests the start of the multicast session when the end user selects viewing of broadband content via the broadband network 3 or a protocol for establishing a multicast session (for example, multicast reservation). In order to reduce the overhead, there are variations such as requesting the start of a multicast session regardless of whether or not the end user selects.

Hereinafter, as a specific embodiment of the method proposed by the present technology, seven distribution methods of the first distribution method to the seventh distribution method will be described.

(1) First distribution method

The first distribution method is a method in which a broadcast application executed by the broadcast receiving device 60 requests the multicast terminal device 70 (multicast terminal module operating on the multicast terminal) to start a multicast session.

That is, in the first distribution method, the broadcast reception device 60 transfers the broadcast program that can be distributed with the multicast program on the air via the terrestrial broadcast network 2 over MPEG2-TS or MMT, or broadband. The broadcast application started by AIT (Application Information Table) acquired via the network 3 is sent to the multicast termination module URL (Uniform Resource Locator) via the API (Application Programming Interface) and the multicast address of the broadcast program. Notify the control information.

The multicast termination module operates on the web server 232 of the multicast termination device 70 as a server-side script.

AIT starts broadcasting at the same time as the start of a broadcast program that can distribute a program that uses multicast, or slightly before the start of the broadcast program, and ends at the end of the broadcast program. The broadcast receiving device 60 that has received the AIT activates a broadcast application based on information obtained from the AIT.

At the same time that the broadcast application is activated, for example, a query character string after the URL is added to the multicast termination module that operates on the multicast termination device 70, and control information of the target multicast address or its control is added. Pass the URL of the file where the information is stored.

For example, if the URL of the server-side script of the module running on the multicast termination device 70 is “http: // localgateway / nmcm”, http-post the contents of the nmc.sdp file as shown in FIG. Can do. In this URL, “localgateway” is a character string that resolves to a pair of IP address and port number, such as “192.168.0.1:8080”.

Also, here is not limited to http-post the contents of nmc.sdp file, for example, http-post the URL of nmc.sdp file, or as the query string parameter of URL of http-get You may pass the same contents. Http-post and http-get correspond to operations executed by the POST method and the GET method among the methods defined by HTTP.

Here, the content of the nmc.sdp file is, for example, when the broadcast application is developed in a language such as HTML5 or JavaScript (registered trademark), the content is described in hard code in the script, Alternatively, the broadcast receiving device 60 is notified by transferring the file including the nmc.sdp file as one of the resource files of the broadcast application.

FIG. 6 is a diagram showing an example of the contents of the nmc.sdp file.

Since SDP (Session Description Protocol) is a session description protocol, the nmc.sdp file can be said to be session description information.

As shown in FIG. 6, the nmc.sdp file contains the IP address of the sending server, the number of channels in the multicast session, the destination multicast IP address and UDP port number of each channel in each multicast session, and the FLUTE TSI (Transport Session Identifier), multicast session start / end time, protocol ID, media type, data rate, FEC (Forward Error Correction) attribute information, and service language attribute.

Based on the contents of this nmc.sdp file, the multicast termination device 70 is connected to the CDN (Content Delivery Network) network side where QoS (Quality Service of Service) is guaranteed via an interface such as NGN (Next Generation Network), for example. Multicast session reservation is performed according to the protocol.

FIG. 7 is a diagram showing a description example of SDP.

In FIG. 7, “0” is described as the required protocol version (v =), and “user123user2890844526 2890842807 IN IP6 2201: 056D :: 112E: 144A: 1E24 as the owner information (o =) of the required session "Is described.

Also, “File delivery session example” is described as the required session name (s =), “2873397496 2873404696” is described as the required session valid period start / end time (t =), and the session level FEC attribute ( As “a =),“ FEC-declaration: 0 "encoding-id = 1” is described.

Also, "IP source-filter:" incl "IN" IP6 "*" 2001: 210: 1: 2: 240: 96FF: FE25: 8EC9 "is described as the IP address (a =). Here, “2001: 210: 1: 2: 240: 96FF: FE25: 8EC9” is provided as the source IP address, and an arbitrary destination multicast IP address is designated.

Also, "flute-tsi: 3" is described as FLUTE TSI (a =), and FLUTE session attributes (media type, UDP port number, protocol type) (m =) are "application 12345 FLUTE / UDP “0” is described, and “IN IP6 FF1E: 03AD :: 7F2E: 172A: 1E24 / 1” is described as the destination multicast IP address (c =).

Also, “8000” is described as the bit rate (b =), “lang: EN (English)” is described as the service language attribute (a =), and “FEC” is specified as the media level FEC attribute (a =). : 0 "is specified.

The description example in FIG. 7 shows an example in which the session description information is described in the SDP format, but the session description information is, for example, an XML (Extensible Markup Language) format or a JSON (JavaScript Object Notation) format. , May be described in other formats. Further, the session description information is not limited to information in text format, but may be information in binary format.

As a message sent from the broadcast receiving device 60 to the multicast terminating device 70, for example, a message as shown in FIG. 8 or FIG. 9 can be sent.

FIG. 8 is a diagram showing an example of a message when the content of the nmc.sdp file is sent by http-post.

The message shown in FIG. 8 is an HTTP request, the POST method is specified in the first request line, and the host name (URL) of the multicast termination module URL of the multicast termination device 70 is specified in the second message header. Host: localgateway) is described.

In addition, the contents of the nmc.sdp file are directly described as a message body across a blank line.

FIG. 9 is a diagram showing an example of a message when the URL of the nmc.sdp file is sent by http-post.

The message shown in FIG. 9 is an HTTP request, and the description of the request line in the first line and the message header in the second line is the same as the message in FIG.

Also, the URL of the nmc.sdp file is described as the message body with a blank line in between. For example, “http://a.com/nmc.sdp” is designated as this URL.

The multicast termination device 70 can acquire the nmc.sdp file by accessing a predetermined server or the like based on the URL “http://a.com/nmc.sdp”. That is, when sending the URL of the nmc.sdp file, the contents of the nmc.sdp file are acquired indirectly.

Then, the multicast termination device 70 acquires the contents of the nmc.sdp file directly or indirectly based on a message sent from the broadcast receiving device 60, for example, the message shown in FIG. Make a reservation.

In addition, when notifying the content of the nmc.sdp file as a query character string parameter of the URL of http-get, for example, the content shown in FIG. 10 may be specified as the parameter.

Here, a mark “?” Is added at the end of the URL, followed by “name = value” format. As this name, “owner”, “sessionName” as shown in FIG. , “Time”, “fecAttribute”, “address”, “tsi”, “sessionAttribute”, “destinationAddress”, “bitRate”, “language”, and “mediaFecAttribute” are described together with their values. However, multiple values are separated by the mark “&”.

(Processing of the first distribution method)
Next, the flow of processing executed by each device of the content distribution system 1 when the first distribution method is adopted will be described with reference to the flowcharts of FIGS. 11 and 12.

11 and 12 show processing performed by one multicast relay router 80 for convenience of explanation, but actually, in the broadband network 3, a plurality of multicast relay routers 80 are arranged in multiple stages. The data is relayed by these multicast relay routers 80.

In step S101, the broadcast content management system 10 generates content such as a program. The content generated by the process in step S101 is transmitted to the broadcast stream server 20 and the broadband stream server 40 (S102).

In step S111, the broadcast stream server 20 processes the content transmitted from the broadcast content management system 10, and generates a broadcast distribution stream. The broadcast distribution stream generated in step S111 is transmitted to the terrestrial broadcast server 30 (S112).

In step S121, the broadband stream server 40 processes the content transmitted from the broadcast content management system 10 and generates a broadband distribution stream. The broadband distribution stream generated by the process of step S121 is transmitted to the broadband server 50 (S122).

In step S103, the broadcast content management system 10 generates a broadcast application. The broadcast application generated in step S103 is transmitted to the terrestrial broadcast server 30 (S104).

The terrestrial broadcast server 30 receives the broadcast distribution stream from the broadcast stream server 20 and the broadcast application from the broadcast content management system 10.

In step S131, the terrestrial broadcast server 30 performs broadcast distribution by processing the received broadcast distribution stream and the broadcast application (for example, processing such as multiplexing). Thereby, the broadcast wave including the broadcast distribution stream and the multiplexed stream of the broadcast application is transmitted through the terrestrial broadcast network 2.

Then, the broadcast wave transmitted through the terrestrial broadcast network 2 is received by the tuner 104 via the antenna 121 at the broadcast receiving device 60, and processed by the broadcast middleware 105, the DASH client 106, the browser 109, etc. at the subsequent stage. .

Meanwhile, the broadband server 50 receives the broadband distribution stream from the broadband server 40.

In step S141, the broadband server 50 processes the received broadband distribution stream (for example, packetization) and performs multicast distribution. As a result, the IP multicast stream is transmitted via the broadband network 3.

Here, multicast packets (IP packets) constituting an IP multicast stream multicast-distributed from the broadband server 50 are received by the multicast relay router 80 that interconnects the networks in the broadband network 3, and a plurality of multicast relays are received. Transferred between routers 80.

12, the broadcast middleware 105 and the DASH client 106 of the broadcast receiving device 60 play back the terrestrial content by processing the multiplexed stream received via the terrestrial broadcast network 2. Then, in the broadcast receiving device 60, the rendering process is performed by the renderer 107, so that the video and audio of the terrestrial content as a broadcast program that can be distributed together with the multicast program is output.

In step S182, the browser 109 acquires and activates a broadcast application obtained from the stream processed by the broadcast middleware 105 based on the AIT. The AIT is an example of application control information, and is acquired via broadcast or communication.

The broadcast application activated in this manner notifies the multicast termination module operating on the multicast termination device 70 of the network distribution reservation preparation in accordance with the control from the network distribution reservation preparation processing unit 133 (S183).

In this network distribution reservation preparation notification, the broadcast application executed by the browser 109 in the broadcast receiving device 60 uses the multicast reservation notification function (first argument in FIG. 13) provided as an API, and the multicast termination module. In response to this, a multicast reservation instruction is given by notifying the nmc.sdp file.

Here, the multicast reservation notification function will be described with reference to FIG.

MulticastJoin () is a multicast reservation notification function for requesting participation in a multicast session, and a multicast session description (for example, nmc.sdp file) is passed as the first argument. In addition, if the multicast session description passed in the first argument is returned as the return value, it means that the process has been successful, and if null is returned, it means that the process has failed. To do.

As described above, the multicast reservation notification function is a function that requests the multicast session reservation by passing the contents of the multicast session description (for example, nmc.sdp file) passed by the first argument to the multicast termination device 70.

In this first delivery method, the first argument is passed as an argument of multicastJoin (), but a service identifier as a second argument may be passed. When the second argument is passed, if the service identifier passed in the second argument is returned as the return value, it means that the process has succeeded. If null is returned, the process has failed. Means.

In this way, the multicast reservation notification function is a function that requests the multicast session reservation by passing the service identifier passed in the second argument to the multicast termination device 70. For example, a fourth distribution method or a fifth distribution method, which will be described later, is assumed as a distribution method for passing the second argument (service identifier) as an argument when using the multicast reservation notification function.

Returning to the description of FIG. 12, the multicast termination device 70 receives the nmc.sdp file notified from the broadcast receiving device 60. Here, as shown in FIG. 8 to FIG. 10, the contents of the nmc.sdp file, the method of sending the URL by http-post, the method of specifying the parameter of the query string of the URL of http-get, etc. Can be used.

In step S161, the multicast middleware 231 of the multicast termination device 70 makes a multicast (multicast group) by making a multicast reservation to the multicast relay router 80 in the broadband network 3 based on the contents of the nmc.sdp file. participate.

In the multicast relay router 80, when the multicast termination device 70 participates in the multicast, the process of step S151 is executed. That is, in step S 151, the multicast relay router 80 transfers the IP multicast stream distributed by multicast from the broadband server 50 to the multicast termination device 70.

In this way, multicast transmission is started in the multicast relay router 80, and the IP multicast stream is received by the multicast termination device 70.

That is, in the multicast relay router 80, when the IP multicast stream is relayed, a multicast tree (route information) between the plurality of multicast relay routers 80 is dynamically generated. When the device 70 joins the multicast (multicast group), a multicast tree is generated.

Thereby, before the broadband content is requested from the broadcast receiving device 60, the multicast tree is generated, and the IP multicast stream is transferred from the multicast relay router 80 to the multicast terminating device 70. When broadband content is requested from 60, the IP multicast stream can be immediately transferred.

In other words, it can be said that the IP multicast stream is blocked by the multicast relay router 80 configured in multiple stages in the broadband network 3 until the multicast termination device 70 participates in the multicast.

In other words, the IP multicast stream is blocked in this way by any one of the plurality of multicast relay routers 80 that relay data in the broadband network 3, and the multicast termination device 70 is By participating in multicast and generating a multicast tree, the path of the target IP multicast stream (multicast packets constituting the target) is determined.

However, the IP multicast stream is not limited to the multicast relay router 80 but may be the broadband server 50. In this case, when the multicast termination device 70 participates in the multicast, the broadband server 50 performs the multicast. Distribution will be started.

In addition, the route of the IP multicast stream (which constitutes the multicast packet) determined in this way is based on a multicast tree corresponding to the notification of preparation for distribution of the net distribution from the broadcast receiving device 60 (its broadcast application), In other words, since the route is selected because of its high priority, the load on the broadband network 3 can be suppressed.

Here, when a request for broadband content is made in the broadcast receiving device 60, the request is notified (S184) and is received by the multicast termination device 70.

Here, for example, as shown in FIG. 2, when the broadcast application performs a display for the end user to select whether or not to view the broadband content, and the end user selects the viewing of the broadband content. In addition, a request for broadband content is made.

In step S162, the multicast middleware 231 of the multicast termination device 70 transfers the broadband content included in the IP multicast stream multicast-transferred from the multicast relay router 80 to the broadcast receiving device 60.

The broadcast receiving device 60 receives broadband content (including an IP multicast stream) from the multicast termination device 70 through the communication I / F 110.

In step S185, the DASH client 106 processes the IP multicast stream received via the broadband network 3 to reproduce the broadband content. Then, in the broadcast receiving device 60, the rendering process is performed by the renderer 107, whereby the video and audio of the broadband content as the multicast combined delivery program are output.

At this time, the DASH client 106 acquires an MPD (Media Presentation Description) from the multicast termination device 70 as necessary, processes the DASH segment obtained from the IP multicast stream, and reproduces the broadband content. May be. Here, MPD is control information of a video or audio file used for performing streaming delivery compliant with MPEG-DASH (Dynamic Adaptive Streaming over HTTP).

Thereafter, when the reproduction of the broadband content is terminated, the broadcast application notifies the multicast termination device 70 of cancellation of the network distribution reservation (S186).

In this net distribution reservation cancellation, the broadcast application executed by the browser 109 in the broadcast receiving device 60 uses the multicast cancellation notification function provided as an API to the multicast termination module operating in the multicast termination device 70. On the other hand, by notifying the nmc.sdp file, an instruction to leave the multicast is issued.

Here, the multicast cancellation notification function will be described with reference to FIG.

MulticastLeave () is a multicast cancellation notification function for requesting to leave a multicast session, and a multicast session description (for example, nmc.sdp file) is passed as the first argument. In addition, if the multicast session description passed in the first argument is returned as the return value, it means that the process has been successful, and if null is returned, it means that the process has failed. To do.

As described above, the multicast cancellation notification function is a function that requests the multicast session withdrawal by passing the contents of the multicast session description (for example, nmc.sdp file) passed by the first argument to the multicast termination device 70.

In this first delivery method, the first argument is passed as an argument of multicastLeave (), but a service identifier as a second argument may be passed. When the second argument is passed, if the service identifier passed in the second argument is returned as the return value, it means that the process has succeeded. If null is returned, the process has failed. Means.

Thus, the multicast cancellation notification function is a function for requesting the multicast session withdrawal by passing the service identifier passed in the second argument to the multicast termination device 70. For example, a fourth distribution method or a fifth distribution method, which will be described later, is assumed as a distribution method for passing the second argument (service identifier) as an argument when using the multicast cancellation notification function.

Returning to the description of FIG. 12, the multicast termination device 70 receives the nmc.sdp file from the broadcast receiving device 60. Here, as shown in FIG. 8 to FIG. 10, the contents of the nmc.sdp file, the method of sending the URL by http-post, the method of specifying the parameter of the query string of the URL of http-get, etc. Can be used.

In step S163, the multicast middleware 231 of the multicast termination device 70 leaves the multicast by canceling the participation of the multicast to the multicast relay router 80 in the broadband network 3 based on the contents of the nmc.sdp file.

In the multicast relay router 80, when the multicast termination device 70 leaves the multicast, the process of step S152 is executed. That is, in step S152, the multicast relay router 80 stops transferring the IP multicast stream distributed by multicast from the broadband server 50 to the multicast termination device 70.

On the other hand, the broadcast receiving device 60 receives the multiplexed stream broadcast from the terrestrial broadcast server 30 via the terrestrial broadcast network 2 and resumes the reproduction of the terrestrial content (S132, S187). .

That is, when the multicast termination device 70 leaves the participating multicast, the broadcast receiving device 60 cannot receive the broadband distribution stream, but since the reception of the broadcast distribution stream is resumed, the content to be reproduced is Switching from content to terrestrial content.

Here, the processing of steps S161, S151, and S162 described above, that is, the data relay processing performed by the plurality of multicast relay routers 80 in the broadband network 3, is performed as follows.

That is, in the present technology, the multicast termination device 70 participates in the multicast (S161) to make a priority reservation for multicast. The reason why this priority reservation is necessary is as follows.

A multicast protocol is used as a general IP broadcast method using IPTV (Internet Protocol TV). However, a multicast router that supports the IP multicast protocol (for example, the multicast relay router 80) is connected to a network segment connected to itself. In addition, a multicast group management protocol such as IGMP (Internet Group Management Protocol) is used to manage whether or not there is a client device (for example, broadcast receiving device 60) participating in each multicast group.

The client device that receives the multicast distribution designates the multicast address where the desired multicast is performed, and declares participation in the multicast group to the multicast router by the multicast group management protocol.

When a multicast router receives a multicast packet from a higher-level router that forms the multicast tree, the multicast router transmits the multicast packet only when there is a client device participating in the multicast group on the network segment connected to the multicast router. To the network segment. Further, when the client device stops receiving the multicast distribution, the client device declares the multicast router to leave the multicast group.

Here, it is assumed that the multicast router is located at the boundary between the home network and the access network, and the client device is connected on the home network segment. In this client device, each time an IP multicast stream is selected or switched (channel selection or switching), the multicast router is joined or disconnected from the multicast.

In general, since the process of joining or leaving a multicast takes time, the screen may be interrupted each time selection or switching is performed. For example, end users who are familiar with frequent channel switching (so-called channel zapping) on analog television. Therefore, it is assumed that the poor response cannot be tolerated.

In order to cope with such a problem, an intelligent multicast router participates in a multicast group corresponding to a plurality of channels that can be selected by an end user using a client device on a home network that is connected to the intelligent router in advance ( For example, it is possible to reduce the overhead of switching a multicast tree higher than the multicast router by joining a multicast group corresponding to several tens of channels in advance.

However, when such a method is adopted, as the number of multicast routers connected to the access network increases, the number of multicast groups that must be joined in advance increases, so that a large number of IPs on the access network. A multicast stream will flow. As a result, a great load is applied to the network, capacity overflow occurs, and conversely, the response deteriorates.

In addition, participation to the same multicast address from different multicast routers is performed, and even if there are IP multicast streams shared by multiple multicast routers, the number of multicast groups that need to participate in advance increases. There is no.

Therefore, in order to reduce the number of IP multicast streams that always flow on this access network and to minimize the overhead of channel zapping as much as possible, priorities are assigned in advance to the multicast groups to which individual multicast routers participate. It is necessary to select and join the multicast group that the user is likely to select.

Therefore, in the first distribution method, when the multicast termination device 70 joins the multicast (multicast group), a multicast tree is generated so that broadband content is requested from the broadcast receiving device 60. Before that, a multicast tree is generated in accordance with the notification of preparation for distribution of network delivery from the broadcast receiving device 60 (its broadcast application).

Therefore, since the IP multicast stream is transferred from the multicast relay router 80 to the multicast terminal device 70 before the broadband content is requested from the broadcast receiving device 60, the broadband content is requested from the broadcast receiving device 60. The IP multicast stream can be transferred immediately.

Further, the route of this IP multicast stream (the multicast packet constituting the IP multicast stream) is based on a multicast tree in response to a notice of preparation for net distribution reservation from the broadcast receiving device 60 (its broadcast application), and so has a high priority. Therefore, the load on the broadband network 3 can be suppressed.

The flow of processing when the first distribution method is adopted has been described above.

(2) Second delivery method

The second distribution method uses a multicast termination table (operating on a multicast termination device 70) using a multicast information table (hereinafter also referred to as MIT (Multicast Information Table)) that stores the nmc.sdp file or equivalent content. ) To request the start of a multicast session.

FIG. 15 is a diagram showing an example of the structure of the MIT.

MIT is included in, for example, PSI / SI (Program Specific Information / Service Information) and is transmitted in section format.

As shown in FIG. 16, the packet identifier (PID) of the TS packet that transmits the MIT table is indirectly specified by PMT (Program Map Table). The PMT is a table storing PIDs such as images and sounds included in a program.

In FIG. 15, Multicast_information_section () is an 8-bit table_id, a 1-bit section_syntax_indicator, a 1-bit reserved_future_use, a 2-bit reserved, a 12-bit section_length, a 12-bit descriptors_loop_length, a descriptor () in a descriptor loop, and a 32-bit descriptor It consists of a CRC_32 field.

Table_id is an 8-bit field of a table ID for identifying a table. For example, as shown in FIG. 17, “0x76” is set as the table ID of MIT.

The multicast session descriptor is placed in descriptor () in the descriptor loop.

FIG. 18 is a diagram illustrating an example of the structure of a multicast session descriptor.

In FIG. 18, Multicast_session_descriptor () is composed of fields of 8-bit descriptor_tag, 8-bit descriptor_length, and 8-bit text_char.

Descriptor_tag is an 8-bit field of a tag value for identifying the descriptor. For example, as shown in FIG. 19, “0xE5” is set as the tag value of the multicast session descriptor.

Text_char is an 8-bit field that contains the nmc.sdp file or equivalent content. The nmc.sdp file includes, for example, the contents shown in FIG.

When the broadcast receiving device 60 obtains such an MIT via broadcast, the broadcast receiving device 60 uses the nmc.sdp file included in the MIT or equivalent content to the multicast termination device 70 (multicast termination module operating in). , Requesting the start of a multicast session.

(Processing of the second distribution method)
Next, the flow of processing executed by each device of the content distribution system 1 when the second distribution method is adopted will be described with reference to the flowcharts of FIGS.

In steps S201 to S202, content such as a program is generated by the broadcast content management system 10 as in steps S101 to S102 of FIG.

In steps S211 to S212, a broadcast distribution stream is generated by the broadcast stream server 20 as in steps S111 to S112 of FIG.

In steps S221 to S222, a broadband distribution stream is generated by the broadband server 40 as in steps S121 to S122 of FIG.

In steps S203 to S204, a broadcast application is generated by the broadcast content management system 10 as in steps S103 to S104 of FIG.

In step S205, the broadcast content management system 10 generates an MIT. The MIT generated in step S206 is transmitted to the terrestrial broadcast server 30 (S206).

The terrestrial broadcast server 30 receives the broadcast application and MIT from the broadcast content management system 10 and the broadcast distribution stream from the broadcast stream server 20.

In step S231, the terrestrial broadcast server 30 performs broadcast distribution by processing (for example, multiplexing) the received broadcast distribution stream, the broadcast application, and the MIT. Thereby, the broadcast wave including the broadcast distribution stream, the broadcast application, and the multiplexed stream of MIT is transmitted via the terrestrial broadcast network 2.

In step S241, the broadband server 50 processes the broadband distribution stream from the broadband stream server 40 (for example, packetization) and performs multicast distribution. As a result, the IP multicast stream is transmitted via the broadband network 3.

21, the broadcast middleware 105 of the broadcast receiving device 60 acquires the MIT by processing the multiplexed stream received via the terrestrial broadcast network 2. This MIT has the structure shown in FIG. 15, and the multicast session descriptor (FIG. 18) arranged in the descriptor loop includes the nmc.sdp file or equivalent content.

In step S282, the broadcast middleware 105 (or the net distribution reservation preparation processing unit 133) makes a net distribution reservation to the multicast termination module operating in the multicast termination device 70 based on the MIT obtained in the process of step S281. Notify preparation.

In this network distribution reservation preparation notification, the broadcast middleware 105 (or the network distribution reservation preparation processing unit 133) in the broadcast receiving device 60 sends the nmc.sdp file obtained from the MIT acquired in step S281 to the multicast termination module. Alternatively, a multicast reservation instruction is given by notifying the equivalent content.

The multicast termination device 70 receives the nmc.sdp file from the broadcast receiving device 60 or the equivalent content. Here, as shown in FIGS. 8 to 10, http-post and http-get messages can be used.

In steps S261 and S251, similarly to steps S161 and S151 of FIG. 12, the multicast middleware 231 of the multicast termination device 70 uses the nmc.sdp file or equivalent content to participate in the multicast. Then, the multicast termination device 70 starts receiving an IP multicast stream that is multicast-transferred from the multicast relay router 80.

That is, in the second distribution method, a multicast tree is generated when the multicast termination device 70 participates in a multicast (multicast group), as in the first distribution method described above.

Therefore, since the multicast tree is generated before the broadband content is requested from the broadcast receiving device 60 and the IP multicast stream is transferred from the multicast relay router 80 to the multicast terminating device 70, the broadcast receiving device 60 When broadband content is requested from the Internet, the IP multicast stream can be immediately transferred.

Further, until the multicast termination device 70 participates in the multicast, the IP multicast stream is blocked by the multicast relay router 80 or the broadband server 50, but the multicast termination device 70 participates in the multicast and a multicast tree is generated. Thus, the route of the target IP multicast stream (multicast packets constituting the target) is determined.

The path of the IP multicast stream (which constitutes the multicast packet) thus determined is based on the multicast tree corresponding to the network distribution reservation preparation notification from the broadcast receiving device 60 that has received the MIT. Since the route is selected because the priority is high, the load on the broadband network 3 can be suppressed.

On the other hand, in the broadcast receiving device 60, the broadcast middleware 105, the DASH client 106, and the like process the stream received via the terrestrial broadcast network 2 to reproduce the terrestrial content (S283). Then, in the broadcast receiving device 60, the rendering process is performed by the renderer 107, so that the video and audio of the terrestrial content as a broadcast program that can be distributed together with the multicast program is output.

In the broadcast receiving device 60, the browser 109 acquires and activates a broadcast application obtained from the multiplexed stream processed by the broadcast middleware 105 based on the AIT (S284). Then, the broadcast application performs display for selecting whether or not to view the broadband content, and when the end user selects viewing of the desired broadband content, a request for the broadband content is made (S285). .

In steps S285, S262, and S286, as in steps S184, S162, and S185 of FIG. 12, the multicast termination device 70 transfers the IP multicast stream in response to a request from the broadcast receiving device 60, thereby receiving the broadcast. The device 60 reproduces broadband content as a multicast combined delivery program.

Note that although not shown in the flowchart of FIG. 21, the multicast is removed by performing the same processing as steps S186, S163, S152, S132, and S187 of FIG. The content to be played back by the receiving device 60 may be switched from broadband content to terrestrial content.

The flow of processing when the second delivery method is adopted has been described above.

(3) Third distribution method

The third distribution method is a method in which MITs of all channels broadcasted at that time are acquired, and multicast reservation is made in advance for the multicast termination device 70 (multicast termination module operating in).

However, in this method, since it is necessary to select all channels, in the broadcast receiving device 60, for example, a multi-tuner needs to be mounted as the tuner 104.

(Process of the third distribution method)
Next, with reference to the flowchart of FIG. 22, the flow of processing executed by each device of the content distribution system 1 when the third distribution method is adopted will be described.

Note that the previous process of the third delivery method is the same as the previous process of the second delivery method, and the description thereof is omitted. That is, the process in the first stage of the third delivery method is the same as the process shown in the flowchart of FIG. 20 described above, and the process in the latter part of the third delivery method shown in FIG. 22 is shown in the flowchart of FIG. It is assumed that the process is executed following the process.

In step S381, the tuner 104 (multi-tuner) of the broadcast receiving device 60 selects (tunes) all channels, and all of the multiplexed streams received via the terrestrial broadcast network 2 are simultaneously transferred in parallel. The MIT is acquired by the broadcast middleware 105.

In step S382, the broadcast middleware 105 (or the network distribution reservation preparation processing unit 133) determines all the multicast termination modules operating in the multicast termination device 70 based on all the MITs obtained in the process of step S381. Notify online delivery reservation preparation.

In this all-net distribution reservation preparation notification, in the broadcast receiving device 60, the broadcast middleware 105 (or the net distribution reservation preparation processing unit 133) is obtained from all the MITs acquired in step S381 for the multicast termination module. A multicast reservation instruction is issued by notifying the nmc.sdp file for all channels or the equivalent content.

In steps S361 and S351, as in steps S261 and S251 of FIG. 21, the multicast middleware 231 of the multicast termination device 70 uses the nmc.sdp file for all channels or the equivalent content to participate in the multicast. become. Then, the multicast termination device 70 starts receiving IP multicast streams for all channels that are multicast-transferred from the multicast relay router 80.

That is, in the third distribution method, a multicast tree is generated when the multicast termination device 70 joins a multicast (multicast group), as in the second distribution method described above.

Therefore, before a broadband content is requested from the broadcast receiving device 60, a multicast tree is generated, and IP multicast streams for all channels are transferred from the multicast relay router 80 to the multicast termination device 70. When broadband content of a desired channel is requested from the broadcast receiving device 60, an IP multicast stream of the desired channel can be immediately transferred from all channels.

Until the multicast termination device 70 participates in the multicast, the IP relay stream for all channels is blocked by the multicast relay router 80 or the broadband server 50. However, the multicast termination device 70 participates in the multicast and the multicast tree Is generated, the routes of the IP multicast streams (multicast packets constituting the same) for all the target channels are determined.

The routes of the IP multicast streams for all channels determined in this way (multicast packets constituting the IP multicast streams) are based on the multicast tree corresponding to the all-net distribution reservation preparation notification from the broadcast receiving device 60 that has received the MIT. In other words, since the route is selected because it has a high priority, the load on the broadband network 3 can be suppressed.

On the other hand, in the broadcast receiving device 60, the terrestrial content is reproduced (S383), and the broadcast application is activated (S384). Then, the broadcast application performs a display for selecting whether or not to view the broadband content, and when the end user selects the viewing of the broadband content of a desired channel, a request for the broadband content is made ( S385).

In steps S385, S362, and S386, similarly to steps S285, S262, and S286 in FIG. 21, the multicast termination device 70 transfers the IP multicast stream in response to a request from the broadcast receiving device 60. Since broadband contents for all channels are transferred from the multicast relay router 80, the following points are different.

That is, the multicast termination device 70 selects the broadband content of the desired channel selected by the end user from the broadband content for all the channels multicast-transferred from the multicast relay router 80 and transfers it to the broadcast receiving device 60. To do. Thereby, the broadcast receiving device 60 reproduces broadband content of a desired channel.

Note that although not shown in the flowchart of FIG. 22, the same processing as steps S186, S163, S152, S132, and S187 of FIG. The content to be played back by the receiving device 60 may be switched from broadband content to terrestrial content.

The flow of processing when the third distribution method is adopted has been described above.

(4) Fourth distribution method

The fourth distribution method is a method in which, when broadband distribution signaling is distributed by multicast, the broadcast application notifies the service identifier and encourages multicast participation.

(Process of the fourth distribution method)
Next, the flow of processing executed by each device of the content distribution system 1 when the fourth distribution method is adopted will be described with reference to the flowcharts of FIGS.

In steps S401 to S402, content such as a program is generated by the broadcast content management system 10 as in steps S201 to S202 of FIG.

In steps S403 to S404, a broadcast application is generated by the broadcast content management system 10 as in steps S203 to S204 of FIG.

In steps S405 to S406, an MIT is generated by the broadcast content management system 10 as in steps S205 to S206 of FIG. This MIT is transmitted to the stream server 40 for broadband.

In steps S411 to S412, a broadcast distribution stream is generated by the broadcast stream server 20 as in steps S211 to S212 of FIG.

In step S421, the broadband server 40 generates broadband distribution signaling. Here, for example, as broadband distribution signaling, signaling such as SLT (Service List) and SLS (Service Layer Signaling) is generated based on the MIT received from the broadcast content management system 10.

Note that the MIT has the structure shown in FIG. 15, and the multicast session descriptor (FIG. 18) arranged in the descriptor loop includes the nmc.sdp file or equivalent content. That is, the nmc.sdp file or equivalent content is included for signaling such as SLT and SLS.

SLT and SLS are signaling defined in ATSC (Advanced Television Systems Committee) 3.0, which is one of the next generation terrestrial broadcasting standards. The detailed contents of SLT and SLS are described in Non-Patent Document 1 below. SLT and SLS are provided as XML format files.

Non-patent document 1: ATSC Candidate Standard: Signaling, Delivery, Synchronization, and Error Protection (A / 331)

In steps S423 to S424, a broadband distribution stream is generated by the broadband server 40 as in steps S221 to S222 of FIG.

In step S431, broadcast distribution is performed by the terrestrial broadcast server 30, as in step S231 of FIG. Broadcast waves from the terrestrial broadcast server 30 are received by the broadcast receiving device 60 via the terrestrial broadcast network 2.

In step S441, multicast distribution is performed by the broadband server 50, as in step S241 of FIG. The IP multicast stream from the broadband server 50 is received by the multicast relay router 80 in the broadband network 3.

However, this IP multicast stream includes broadband distribution signaling as well as the broadband distribution stream.

24, the multicast middleware 231 of the multicast termination device 70 participates in the broadband distribution signaling multicast by performing a predetermined procedure with respect to the multicast relay router 80.

Here, the broadband distribution signaling multicast is a multicast for transferring broadband distribution signaling (for example, SLT and SLS files), and the multicast distribution (for example, SLT and SLS files) by participating in this multicast. Can be obtained.

In the multicast relay router 80, when the multicast termination device 70 participates in the broadband distribution signaling multicast, the process of step S451 is executed. That is, in step S451, the multicast relay router 80 transfers the signaling distributed from the broadband server 50 to the multicast termination device 70.

In this way, signaling multicast transfer is started in the multicast relay router 80, and broadband distribution signaling is received by the multicast termination device 70.

In step S462, the signaling processing unit 233 of the multicast termination device 70 analyzes the received signaling. Based on this analysis result, the nmc.sdp file or equivalent content can be obtained from signaling such as SLT or SLS.

On the other hand, in the broadcast receiving device 60, the terrestrial content is played back (S481), and the broadcast application is activated (S482). The activated broadcast application notifies the multicast termination module running on the multicast termination device 70 of the preparation for net distribution reservation (S483).

In this network distribution reservation preparation notification, a broadcast application uses a multicast reservation notification function (second argument in FIG. 13) to specify a service identifier for identifying a service (channel) that provides the terrestrial content being played back. Then, an instruction to participate in multicast is given. This service identifier is received by the multicast termination device 70.

In steps S463 and S452, the service identifier and the nmc.sdp file or equivalent content are processed by the multicast middleware 231 of the multicast termination device 70 and participate in the multicast.

More specifically, by obtaining the nmc.sdp file associated with the service identifier or the equivalent content from the analysis result of signaling such as SLT or SLS, it is possible to multicast the broadband content identified by the service identifier. Parameters necessary for participation are acquired. For example, the service identifier is associated with an SLT global service ID (globalServiceID) or the like.

Thereby, the multicast termination device 70 starts receiving an IP multicast stream that is multicast-transferred from the multicast relay router 80.

That is, in the fourth distribution method, a multicast tree is generated when the multicast termination device 70 joins a multicast (multicast group), as in the first distribution method described above.

Further, until the multicast termination device 70 participates in the multicast, the IP multicast stream is blocked by the multicast relay router 80 or the broadband server 50, but the multicast termination device 70 participates in the multicast and a multicast tree is generated. As a result, the route of the IP multicast stream of the target service (channel) (multicast packet constituting it) is determined.

The path of the IP multicast stream (which constitutes the multicast packet) determined in this way is based on the multicast tree corresponding to the result of the signaling analysis using the service identifier, which is so high in priority. Since the route is selected, the load on the broadband network 3 can be suppressed.

On the other hand, in the broadcast receiving device 60, the broadcast application performs a display for selecting whether or not to view the broadband content, and the end user identifies the broadband content identified by the service identifier of the terrestrial content being reproduced. When viewing is selected, a request for the broadband content is made (S484).

In steps S484, S464, and S485, as in steps S184, S162, and S185 in FIG. 12, the multicast termination device 70 transfers the IP multicast stream in response to a request from the broadcast receiving device 60, thereby receiving the broadcast. The device 60 reproduces broadband content.

Note that although not shown in the flowchart of FIG. 24, multicast is disconnected by performing the same processing as steps S186, S163, S152, S132, and S187 of FIG. The content to be played back by the receiving device 60 may be switched from broadband content to terrestrial content. However, here, when using the multicast cancellation notification function, the service identifier is passed by the second argument (second argument in FIG. 14).

The flow of processing when the fourth distribution method is adopted has been described above.

(5) Fifth distribution method

The fifth distribution method is a method in which, when broadband distribution signaling is distributed by unicast, the broadcast application notifies the service identifier to encourage multicast participation.

This fifth distribution method is a variation of the above-described fourth distribution method, and is a scenario that can be used in an environment in which signaling about the service broadcast at that time can be acquired at once in the broadband multicast service.

(Process of the fifth distribution method)
Next, the flow of processing executed by each device of the content distribution system 1 when the fifth distribution method is adopted will be described with reference to the flowcharts of FIGS. 25 and 26.

25 and 26, as the broadband server 50, the processing of the broadband server 50A that performs multicast distribution and the processing of the broadband server 50B that performs unicast distribution are illustrated.

25 and 26, for convenience of explanation, the processing of the broadcast stream server 20 and the processing of the terrestrial broadcasting server 30 are omitted, but the terrestrial content is transmitted via the terrestrial broadcasting network 2. And broadcast applications can also be distributed.

In steps S501 to S502, content such as a program is generated by the broadcast content management system 10 as in steps S401 to S402 of FIG.

In steps S503 to S504, an MIT is generated by the broadcast content management system 10 as in steps S405 to S406 of FIG.

In steps S521 to S522, broadband distribution signaling is generated as in steps S421 to S422 of FIG. This broadband distribution signaling is signaling including an nmc.sdp file or equivalent content such as SLT and SLS, and is transmitted to the broadband server 50B.

In steps S523 to S524, a broadband distribution stream is generated as in steps S423 to S424 in FIG. This broadband distribution stream is transmitted to the broadband server 50A.

In step S546, similarly to step S441 in FIG. 23, the broadband server 50A performs multicast distribution of the broadband distribution stream. The IP multicast stream from the broadband server 50A is received by the multicast relay router 80 in the broadband network 3.

In step S561, the signaling processing unit 233 of the multicast termination device 70 requests broadband distribution signaling to the broadband server 50B via the broadband network 3.

In step S541, the broadband server 50B returns broadband distribution signaling via the broadband network 3 in response to a request from the multicast termination device 70.

In the multicast termination device 70, the communication I / F 203 receives broadband distribution signaling from the broadband server 50B.

26, the signaling processing unit 233 of the multicast termination device 70 analyzes the received broadband distribution signaling. Based on this analysis result, the nmc.sdp file or equivalent content can be obtained from signaling such as SLT or SLS.

On the other hand, in the broadcast receiving device 60, the terrestrial content is played back (S581), and the broadcast application is activated (S582). The activated broadcast application notifies the multicast termination module running on the multicast termination device 70 of the preparation for net distribution reservation (S583).

In this network distribution reservation preparation notification, a broadcast application uses a multicast reservation notification function (second argument in FIG. 13) to specify a service identifier for identifying a service (channel) that provides the terrestrial content being played back. Then, an instruction to participate in multicast is given.

In steps S563 and S551, as in steps S463 and S452 of FIG. 24, the service identifier and the nmc.sdp file or equivalent content are processed by the multicast middleware 231 of the multicast termination device 70 and participate in multicast. Become.

More specifically, by obtaining the nmc.sdp file associated with the service identifier or the equivalent content from the analysis result of signaling such as SLT or SLS, it is possible to multicast the broadband content identified by the service identifier. Parameters necessary for participation are acquired.

That is, in the fifth distribution method, a multicast tree is generated when the multicast termination device 70 participates in a multicast (multicast group), as in the fourth distribution method described above.

On the other hand, in the broadcast receiving device 60, the broadcast application performs a display for selecting whether or not to view the broadband content, and the end user identifies the broadband content identified by the service identifier of the terrestrial content being reproduced. When viewing is selected, the broadband content is requested (S584).

In steps S584, S564, and S585, as in steps S484, S464, and S485 of FIG. 24, the multicast termination device 70 transfers the IP multicast stream in response to a request from the broadcast receiving device 60, thereby receiving the broadcast. The device 60 reproduces broadband content.

26 is omitted in the flowchart of FIG. 26, the multicast is disconnected by performing the same processing as steps S186, S163, S152, S132, and S187 of FIG. The content to be played back by the receiving device 60 may be switched from broadband content to terrestrial content. However, here, when using the multicast cancellation notification function, the service identifier is passed by the second argument (second argument in FIG. 14).

The flow of processing when the fifth distribution method is adopted has been described above.

(6) Sixth delivery method

The sixth distribution method is a method in which broadcast signaling prompts multicast participation when broadband distribution signaling is unicast distributed.

This sixth distribution method is a variation of the fifth distribution method described above, and is a scenario in which MIT is acquired instead of a broadcast application and multicast reservation is made in advance.

(Process of the sixth distribution method)
Next, a flow of processing executed by each device of the content distribution system 1 when the sixth distribution method is adopted will be described with reference to the flowchart of FIG.

Note that the previous process of the sixth distribution method is the same as the previous process of the fifth distribution method, and the description thereof will be omitted. That is, the process in the former stage of the sixth distribution method is the same as the process shown in the flowchart of FIG. 25 described above, and the process in the latter stage of the sixth distribution method shown in FIG. 27 is shown in the flowchart of FIG. It is assumed that the process is executed following the process.

In FIG. 27, as the broadband server 50, processing of a broadband server 50A that performs multicast distribution and processing of a broadband server 50B that performs unicast distribution are shown. In FIG. 27, for convenience of explanation, the processing of the broadcast stream server 20 and the processing of the terrestrial broadcast server 30 are omitted, but the terrestrial content and the broadcast application are transmitted via the terrestrial broadcast network 2. Is also possible.

In step S681, the broadcast middleware 105 of the broadcast receiving device 60 acquires the MIT by processing the stream received via the terrestrial broadcast network 2.

In step S682, the broadcast middleware 105 (or the net distribution reservation preparation processing unit 133) prepares the net distribution reservation for the multicast termination module operating in the multicast termination device 70 when MIT is acquired in the process of step S681. To be notified.

In step S661, the signaling processing unit 233 of the multicast termination device 70 requests broadband distribution signaling to the broadband server 50B via the broadband network 3.

In step S662, the signaling processing unit 233 of the multicast termination device 70 analyzes the broadband distribution signaling received from the broadband server 50B. Based on this analysis result, the nmc.sdp file or equivalent content can be obtained from signaling such as SLT or SLS.

In steps S663 and S651, the nmc.sdp file or equivalent content is processed by the multicast termination device 70 and participates in the multicast.

That is, in the sixth distribution method, a multicast tree is generated when the multicast termination device 70 participates in a multicast (multicast group) as in the fifth distribution method described above.

The route of the IP multicast stream (which constitutes the multicast packet) determined in this way is based on the multicast tree corresponding to the analysis result of the signaling, which is a route selected because it has a high priority. Therefore, the load on the broadband network 3 can be suppressed.

On the other hand, in the broadcast receiving device 60, the terrestrial content is reproduced (S683), and the broadcast application is activated (S684). Then, the broadcast application performs display for selecting whether or not to view the broadband content, and when the end user selects viewing of the desired broadband content, a request for the broadband content is made (S685). .

In steps S685, S664, and S686, as in steps S584, S564, and S585 in FIG. 26, the multicast termination device 70 transfers the IP multicast stream in response to a request from the broadcast receiving device 60, thereby receiving the broadcast. The device 60 reproduces broadband content.

Note that although not shown in the flowchart of FIG. 27, multicast is disconnected by performing the same processing as steps S186, S163, S152, S132, and S187 of FIG. The content to be played back by the receiving device 60 may be switched from broadband content to terrestrial content.

In the above description of the sixth distribution method, the case where the nmc.sdp file obtained from signaling such as SLT or SLS or the equivalent content is used has been described. However, the broadcast receiving device 60 obtains from MIT. The multicast termination device 70 may be notified of the nmc.sdp file to be transmitted or the equivalent content so that multicast participation may be performed.

The flow of processing when the sixth distribution method is adopted has been described above.

(7) Seventh delivery method

The seventh distribution method is a method of switching the distribution format of broadband content from unicast distribution to multicast distribution. In the seventh distribution method, for example, the following scenario is assumed.

Here, it is assumed that the broadcast receiving device 60 is playing broadband content distributed by unicasting HTTP (Hypertext Transfer Protocol) via normal communication by the broadcast application.

However, this broadband content has higher resolution and higher sound quality than terrestrial content and is distributed as DASH streaming. The broadcast receiving device 60 reproduces the broadband content transferred by the multicast termination device 70. In this case, the multicast termination device 70 simply functions as a proxy, and functions related to the above-described multicast session and the like. Is not running.

Here, for example, the number of client apparatuses (for example, broadcast receiving devices 60 such as television receivers) that simultaneously view the same program (broadband content) via the broadband network 3 increases, and the broadband network 3 becomes congested. Imagine a scene where you start

This congestion is detected by the broadband server 50 that performs unicast distribution, and the combined distribution in the multicast distribution of broadband content is instructed. However, this congestion detection is not limited to the broadband server 50 but may be performed by, for example, a dedicated network traffic monitoring module that monitors unicast traffic.

The broadcast content management system 10 that has received the combined delivery instruction from the broadband server 50 generates a new broadcast application or generates an event message to notify the broadcast application, and the updated broadcast application or event message is received. The broadcast receiving device 60 receives the data.

In the broadcast receiving device 60 that has received the updated broadcast application or event message, the broadcast application is restarted or the event message is notified to the active broadcast application.

In the broadcast receiving device 60, the broadcast application requests the multicast termination module operating on the multicast termination device 70 to start a multicast session.

The subsequent processing is the same as in the first distribution method described above, and the multicast termination device 70 changes the broadband content acquisition destination from the broadband server 50B that performs unicast distribution to the broadband server 50A that performs multicast distribution. Switch to. That is, the multicast termination device 70 does not function as a proxy, but performs functions related to the above-described multicast session and the like.

Note that the multicast control flow here uses the signaling system of ATSC 3.0 as in the case of using the direct SDP as in the first distribution method described above and the fourth distribution method as described above. Applicable to both patterns.

(Process of the seventh distribution method)
Next, the flow of processing executed by each device of the content distribution system 1 when the seventh distribution method is adopted will be described with reference to the flowcharts of FIGS.

In addition, in FIG. 28 thru | or 30, the process of the broadband server 50A which performs multicast delivery, and the process of the broadband server 50B which performs unicast delivery are shown as the broadband server 50, respectively.

In steps S701 to S702, content such as a program is generated by the broadcast content management system 10 as in steps S101 to S102 of FIG.

In steps S711 to S712, a broadcast delivery stream is generated by the broadcast stream server 20 as in steps S111 to S112 of FIG.

In steps S721 to S722, a broadband distribution stream for unicast distribution is generated by the broadband stream server 40 as in steps S121 to S122 of FIG.

In steps S703 to S704, a broadcast application is generated by the broadcast content management system 10 as in steps S103 to S104 of FIG.

In step S731, broadcast distribution is performed by the terrestrial broadcast server 30 as in step S131 of FIG. Broadcast waves from the terrestrial broadcast server 30 are received by the broadcast receiving device 60 via the terrestrial broadcast network 2.

Then, as shown in FIG. 29, the broadcast receiving device 60 reproduces the terrestrial content (S781), and the broadcast application is activated (S782).

In step S783, the communication control unit 132 of the processing unit 101 controls the communication I / F 110 to request the multicast termination device 70 for broadband content for unicast distribution.

In the multicast termination device 70 that has received this request, the processing unit 201 requests the broadband content of the unicast distribution to the broadband server 50B via the broadband network 3 (S761).

The broadband server 50B then unicasts the broadband content via the broadband network 3 in response to a request from the multicast termination device 70 (S741). This IP unicast stream is received by the multicast termination device 70 via the broadband network 3 and transferred to the broadcast receiving device 60 (S762).

Thereby, the broadcast receiving device 60 reproduces the unicast-distributed broadband content (S784).

That is, this broadband content has higher resolution and higher sound quality than terrestrial content, and the content to be played back by the broadcast receiving device 60 is switched from, for example, 2K resolution terrestrial content to 4K resolution broadband content. It is done.

Here, in the broadband server 50B, the unicast traffic in the broadband network 3 is monitored, and overload detection in the unicast traffic is performed (S742). If congestion in the broadband network 3 is detected in the overload detection process in step S742, the process in step S743 is performed.

That is, the broadband server 50B notifies (instructs) the broadcast content management system 10 and the broadband stream server 40 of the combined delivery in the multicast delivery of broadband content (S743).

In step S705, the broadcast content management system 10 generates a new broadcast application and updates the broadcast application or notifies the broadcast application of an event message (hereinafter, referred to as “broadcast application”) in response to the instruction for combined delivery from the broadband server 50B. (Also called an app event).

The updated broadcast application or application event obtained in the process of step S705 is transmitted to the terrestrial broadcast server 30.

In step S732, broadcast distribution is performed by the terrestrial broadcast server 30 as in step S131 of FIG. Here, the broadcast wave from the terrestrial broadcast server 30 includes the updated broadcast application or application event, and is received by the broadcast receiving device 60 via the terrestrial broadcast network 2.

In steps S723 to S724, a broadband distribution stream for multicast distribution is generated by the broadband stream server 40 as in steps S121 to S122 of FIG.

In step S746, as in step S141 of FIG. 11, the broadband distribution stream for multicast distribution from the broadband stream server 40 is processed by the broadband server 50A, and multicast distribution is performed. As a result, the IP multicast stream is transmitted via the broadband network 3.

On the other hand, in the broadcast receiving device 60, when the updated broadcast application is obtained from the multiplexed stream processed by the broadcast middleware 105, the process of step S785 in FIG. If so, the process of step S786 in FIG. 30 is executed.

That is, in step S785, the updated broadcast application obtained from the multiplexed stream is acquired and activated. On the other hand, in step S786, an application event obtained from the multiplexed stream is detected by a running broadcast application.

When the process of step S785 or S786 ends, the process proceeds to step S787. Then, in step S787, the network distribution reservation preparation is notified to the multicast termination module operating in the multicast termination device 70 by the updated broadcast application or the broadcast application that has detected the application event.

In this network distribution reservation preparation, the broadcast reception device 60 uses the multicast reservation notification function (first argument in FIG. 13) provided as an API by the updated broadcast application or the broadcast application that has detected an application event. Then, the multicast termination module is instructed by notifying the multicast termination module of the nmc.sdp file or the equivalent content.

The multicast termination device 70 receives the nmc.sdp file from the broadcast receiving device 60 or the equivalent content.

In steps S763 and S751, as in steps S161 and S151 of FIG. 12, the multicast middleware 231 of the multicast termination device 70 uses the nmc.sdp file or equivalent content to participate in the multicast. Then, the multicast termination device 70 starts receiving an IP multicast stream that is multicast-transferred from the multicast relay router 80.

That is, in the seventh distribution method, a multicast tree is generated when the multicast termination device 70 participates in a multicast (multicast group) as in the first distribution method described above.

The route of the IP multicast stream (which constitutes the multicast packet) determined in this way is based on the multicast tree corresponding to the net distribution reservation preparation notification from the broadcast receiving device 60, and so has a high priority. Therefore, the load on the broadband network 3 can be suppressed because the route is selected for this purpose.

In steps S788, S764, and S789, similarly to steps S184, S162, and S185 in FIG. 12, the multicast termination device 70 transfers the IP multicast stream in response to a request from the broadcast receiving device 60, thereby receiving the broadcast. The device 60 reproduces the broadband content distributed by multicast.

That is, when congestion of the broadband network 3 is detected, the broadcast receiving device 60 switches the broadband content to be reproduced from the broadband content distributed by unicast to the broadband content distributed by multicast.

This completes the description of the processing flow when the seventh distribution method is adopted.

<3. Protocol stack configuration of this technology>

By the way, in the system proposed by the present technology, various protocols can be used as a terrestrial broadcast transport protocol, a broadband unicast protocol, and a broadband multicast protocol.

Therefore, hereinafter, a first stack configuration to a twelfth stack configuration will be described as protocol stack configurations applicable to the scheme proposed by the present technology.

(1) First stack configuration

FIG. 31 is a diagram showing an example of the first stack configuration.

In the first stack configuration in FIG. 31, the stack configuration of the broadcast receiving device 60 is shown on the right side of the drawing, and the stack configuration of the multicast termination device 70 is shown on the left side of the drawing.

In these stack configurations, the lowest layer of the hierarchical structure is the first layer corresponding to the physical layer and the link layer, and the layer one layer above the first layer is the network layer. The corresponding second layer is used. In addition, a layer one level above the second level is a third level corresponding to the transport layer, and a level one level above the third level is a fourth level corresponding to the application layer. Is done.

And by implementing such a four-layer protocol stack, various middleware and applications can be implemented in the broadcast receiving device 60 and the multicast termination device 70.

The broadcast receiving device 60 includes a tuner 104 (FIG. 3) and a communication I / F 110 (FIG. 3) and is compatible with both broadcasting and communication systems. A stack is also written.

As the broadcast stack, the first layer is the broadcast PHY, the second layer is MPEG2-TS (Transport Stream), and the third layer is PES (Packetized Elementary Stream) or Section. The fourth hierarchy is Audio / Video ES (Elementary Stream) or PSI / SI (Program Specific Information / Service Information).

In addition, AIT (Application Information Table) and MIT (Multicast Information Table) are included in PSI / SI and transmitted in section format.

As the communication stack, the first layer is Ethernet / Wifi, the second layer is IP (Internet Protocol), the third layer is TCP (Transmission Control Protocol), and the fourth layer The layer of HTTP is Hypertext Transfer Protocol.

By implementing such a protocol stack, the broadcast receiving device 60 is equipped with a broadcast middleware 105, a DASH client 106 (DASH player) as a net player or a broadcast player, or a browser 109 that executes a broadcast application. .

On the other hand, the multicast termination device 70 is configured to include the communication I / F 202 (FIG. 5) and the communication I / F 203 (FIG. 5), and can support two communication methods. A stack and a stack of the second communication system are written together.

As the stack of the first communication system, the first layer is Ethernet / Wifi, the second layer is IP, the third layer is TCP, and the fourth layer is HTTP. Is done. That is, the first communication system stack is the same as the communication system stack of the broadcast receiving device 60.

As the stack of the second communication system, the first layer is Ethernet, the second layer is IP, the third layer is UDP (User Datagram Protocol) or TCP, The hierarchy is FLUTE (File (Delivery over Unidirectional Transport) or HTTP.

By implementing such a protocol stack, multicast middleware 231 and web server 232 are implemented in multicast termination device 70.

In the first stack configuration of FIG. 31, the broadcast receiving device 60 can receive a broadcast wave via a broadcast network such as a terrestrial network or a satellite network by mounting a broadcast-type stack. it can.

In addition, the broadcast receiving device 60 is mounted with a communication stack, and the multicast termination device 70 is mounted with a first communication system stack, so that, for example, each other via a home LAN (Local Area Network) or the like. Can communicate.

Furthermore, in the multicast termination device 70, by mounting the second communication stack, it is possible to communicate with each other via, for example, NGN (Next Generation Network) provided by a communication carrier.

(2) Second stack configuration

FIG. 32 is a diagram illustrating an example of a second stack configuration.

In the second stack configuration of FIG. 32, the stack configuration of the broadcast receiving device 60 and the multicast termination device 70 is shown as in the first stack configuration (FIG. 31) described above. The system stack is different.

In the second stack configuration, as the broadcast stack of the broadcast receiving device 60, the first layer is TLV (Type Length Value) / broadcast PHY, the second layer is IP, and the third layer The hierarchy is MMTP / UDP (MPEG Media Transport Protocol / User User Datagram Protocol), and the fourth hierarchy is Audio / Video ES or PSI / SI.

That is, in the broadcast stack of the second stack configuration, the IP packet is encapsulated in the TLV packet by using the IP transmission method instead of the MPEG2-TS method and included in the physical layer frame (broadcast PHY). Therefore, the IP protocol is used in all stacks and is common.

In the second stack configuration, the communication system stack of the broadcast receiving device 60, the first communication system stack, and the second communication system stack of the multicast termination device 70 are the first stack configuration ( Since it is the same as FIG. 31), the description is omitted.

(3) Third stack configuration

FIG. 33 is a diagram illustrating an example of a third stack configuration.

In the third stack configuration of FIG. 33, the stack configuration of the broadcast receiving device 60 and the multicast termination device 70 is shown as in the first stack configuration (FIG. 31) described above. The system stack is different.

In the third stack configuration, as a broadcast stack of the broadcast receiving device 60, the first hierarchy is the broadcast PHY, the second hierarchy is MPEG2-TS, and the third hierarchy is Section. The fourth hierarchy is IP, the fifth hierarchy is UDP, and the sixth hierarchy is ROUTE (Real-time Object Delivery over Unidirectional Transport) or FLUTE. Further, the fourth to sixth layers are PSI / SI.

That is, in the broadcast stack having the third stack configuration, not only PSI / SI but also IP packets including UDP packets are transmitted in a section format.

In the third stack configuration, the communication system stack of the broadcast receiving device 60 and the first communication system stack and the second communication system stack of the multicast termination device 70 are the first stack configuration ( Since it is the same as FIG. 31), the description is omitted.

(4) Fourth stack configuration

FIG. 34 is a diagram illustrating an example of a fourth stack configuration.

In the fourth stack configuration of FIG. 34, the stack configuration of the broadcast receiving device 60 and the multicast termination device 70 is shown as in the first stack configuration (FIG. 31) described above. The two communication stacks are different.

In the fourth stack configuration, as the second communication system stack of the multicast termination device 70, the first layer is Ethernet, the second layer is IP, and the third layer is UDP or TCP is set, and the fourth layer is set to SLT (Service List List), ROUTE, or HTTP.

That is, the second communication system stack of the fourth stack configuration corresponds to the ATSC3.0 protocol stack described in Non-Patent Document 1 above, so the multicast middleware 231, the web server 232, etc. It has functions equivalent to ATSC3.0 middleware. The details of the protocol stack of ATSC 3.0 are described in “Figure 5.1 ATSC 3.0 receiver protocol stack.” Of Non-Patent Document 1.

In the fourth stack configuration, the broadcast stack and communication stack of the broadcast receiving device 60 and the first communication stack of the multicast termination device 70 are the first stack configuration described above (FIG. 31). Since this is the same, the description thereof is omitted.

(5) Fifth stack configuration

FIG. 35 is a diagram illustrating an example of a fifth stack configuration.

In the fifth stack configuration of FIG. 35, the stack configuration of the broadcast receiving device 60 and the multicast termination device 70 is shown as in the fourth stack configuration (FIG. 34) described above. The system stack is different.

In the fifth stack configuration, as a broadcast system stack of the broadcast receiving device 60, the first hierarchy is TLV / broadcast PHY, the second hierarchy is IP, and the third hierarchy is MMTP / UDP is used, and the fourth layer is Audio / VideoPES or PSI / SI.

That is, in the broadcast stack having the fifth stack configuration, the IP packet is encapsulated in the TLV packet by using the IP transmission method instead of the MPEG2-TS method and included in the physical layer frame (broadcast PHY). Therefore, the IP protocol is used in all stacks and is common.

In addition, the second communication system stack of the fifth stack configuration corresponds to the ATSC3.0 protocol stack in the same way as the fourth stack configuration, so the multicast middleware 231 and the like are the middleware of ATSC3.0. Has the equivalent function.

In the fifth stack configuration, the communication stack of the broadcast receiving device 60 and the first communication stack of the multicast termination device 70 are the same as the above-described fourth stack configuration (FIG. 34). The description is omitted.

(6) Sixth stack configuration

FIG. 36 is a diagram illustrating an example of a sixth stack configuration.

In the sixth stack configuration of FIG. 36, the stack configuration of the broadcast receiving device 60 and the multicast termination device 70 is shown as in the above-described fourth stack configuration (FIG. 34). The system stack is different.

In the sixth stack configuration, as a broadcast system stack of the broadcast receiving device 60, the first hierarchy is the broadcast PHY, the second hierarchy is MPEG2-TS, and the third hierarchy is Section. The fourth hierarchy is IP, the fifth hierarchy is UDP, and the sixth hierarchy is ROUTE or FLUTE. Further, the fourth to sixth layers are PSI / SI.

That is, in the broadcast stack having the sixth stack configuration, not only PSI / SI but also IP packets including UDP packets are transmitted in a section format.

Similarly to the fourth stack configuration, the second communication stack in the sixth stack configuration corresponds to the ATSC3.0 protocol stack, so the multicast middleware 231 and the like are the same as the ATSC3.0 middleware. It has an equivalent function.

In the sixth stack configuration, the communication stack of the broadcast receiving device 60 and the first communication stack of the multicast termination device 70 are the same as the above-described fourth stack configuration (FIG. 34). The description is omitted.

(7) Seventh stack configuration

FIG. 37 is a diagram illustrating an example of a seventh stack configuration.

The seventh stack configuration in FIG. 37 shows a stack configuration when the broadcast receiving device 60 and the multicast termination device 70 are configured as an integrated device (a bundled device). Therefore, this bundled device does not need to communicate with each other via, for example, a home LAN, and can exchange data by, for example, a local loopback.

On the other hand, the bundled device is configured to include the tuner 104 (FIG. 3) and the communication I / F 203 (FIG. 5), and can support both broadcasting and communication systems. A broadcast-type stack and a communication-type stack are written together.

The broadcast stack is a broadcast PHY, the second layer is MPEG2-TS, the third layer is PES or Section, and the fourth layer is Audio / Video ES or PSI / SI. It is said.

As a communication stack, the first layer is Ethernet, the second layer is IP, the third layer is UDP or TCP, and the fourth layer is FLUTE or HTTP. The

By mounting these protocol stacks, in the bundled device, the broadcast middleware 105, the DASH client 106 (DASH player) as a net player or broadcast player, the browser 109 that executes a broadcast application, or the multicast middleware 231 or A web server 232 or the like is implemented.

In the seventh stack configuration of FIG. 37, the bundled device can receive broadcast waves via a broadcast network such as a terrestrial network or a satellite network by mounting a broadcast-type stack. it can. In addition, the multicast termination device 70 can perform communication with each other via, for example, an NGN provided by a communication carrier by mounting a communication stack.

(8) Eighth stack configuration

FIG. 38 is a diagram illustrating an example of an eighth stack configuration.

The eighth stack configuration of FIG. 38 shows a stack configuration of a bundled device in which the broadcast receiving device 60 and the multicast termination device 70 are integrated, similarly to the above-described seventh stack configuration (FIG. 37). However, the broadcast stack is different.

In the eighth stack configuration, the bundle of the broadcasting system of the bundled device has a first layer of TLV / broadcast PHY, a second layer of IP, and a third layer of MMTP / broadcast. UDP is used, and the fourth layer is Audio / VideoPES or PSI / SI.

That is, in the broadcast stack having the eighth stack configuration, the IP packet is encapsulated in the TLV packet by using the IP transmission method instead of the MPEG2-TS method, and included in the physical layer frame (broadcast PHY). Therefore, the IP protocol is used in all stacks and is common.

In the eighth stack configuration, the communication stack is the same as the above-described seventh stack configuration (FIG. 37), and a description thereof will be omitted.

(9) Ninth stack configuration

FIG. 39 is a diagram illustrating an example of a ninth stack configuration.

The ninth stack configuration of FIG. 39 shows a stack configuration of a bundled device in which the broadcast receiving device 60 and the multicast termination device 70 are integrated, similarly to the above-described seventh stack configuration (FIG. 37). However, the broadcast stack is different.

In the ninth stack configuration, as a broadcast stack of the bundled device, the first hierarchy is the broadcast PHY, the second hierarchy is MPEG2-TS, and the third hierarchy is Section. The fourth hierarchy is IP, the fifth hierarchy is UDP, and the sixth hierarchy is ROUTE or FLUTE. Further, the fourth to sixth layers are PSI / SI.

That is, in the broadcast stack having the ninth stack configuration, not only PSI / SI but also IP packets including UDP packets are transmitted in a section format.

In the ninth stack configuration, the communication stack is the same as the above-described seventh stack configuration (FIG. 37), and a description thereof will be omitted.

(10) Tenth stack configuration

FIG. 40 is a diagram illustrating an example of a tenth stack configuration.

The tenth stack configuration in FIG. 40 shows a stack configuration of a bundled device in which the broadcast receiving device 60 and the multicast termination device 70 are integrated, similarly to the above-described seventh stack configuration (FIG. 37). However, the communication stack is different.

In the tenth stack configuration, the communication stack of the bundled device has the first layer as Ethernet, the second layer as IP, and the third layer as UDP or TCP. The fourth layer is SLT, ROUTE, or HTTP.

That is, the communication stack having the tenth stack configuration corresponds to the ATSC3.0 protocol stack, similarly to the second communication stack having the fourth stack configuration (FIG. 34). Have functions equivalent to the middleware of ATSC3.0.

In the tenth stack configuration, the broadcast-type stack is the same as the above-described seventh stack configuration (FIG. 37), and a description thereof will be omitted.

(11) Eleventh stack configuration

FIG. 41 is a diagram showing an example of an eleventh stack configuration.

The eleventh stack configuration in FIG. 41 shows a stack configuration of a bundled device in which the broadcast receiving device 60 and the multicast termination device 70 are integrated, as in the tenth stack configuration (FIG. 40) described above. However, the broadcast stack is different.

In the eleventh stack configuration, as a broadcast stack of the bundled device, the first hierarchy is TLV / broadcast PHY, the second hierarchy is IP, and the third hierarchy is MMTP / UDP is used, and the fourth layer is Audio / VideoPES or PSI / SI.

That is, in the broadcast stack having the eleventh stack configuration, the IP packet is encapsulated in the TLV packet by using the IP transmission method instead of the MPEG2-TS method and included in the physical layer frame (broadcast PHY). Therefore, the IP protocol is used in all stacks and is common.

In addition, since the communication stack of the eleventh stack configuration corresponds to the ATSC3.0 protocol stack as in the tenth stack configuration (FIG. 40), the multicast middleware 231 etc. Has functions equivalent to middleware.

(12) Twelfth stack configuration

FIG. 42 is a diagram illustrating an example of a twelfth stack configuration.

The twelfth stack configuration in FIG. 42 shows a stack configuration of a bundled device in which the broadcast receiving device 60 and the multicast termination device 70 are integrated, as in the tenth stack configuration (FIG. 40) described above. However, the broadcast stack is different.

In the twelfth stack configuration, as a stack of the broadcasting system of the bundled device, the first hierarchy is the broadcast PHY, the second hierarchy is MPEG2-TS, and the third hierarchy is Section. The fourth hierarchy is IP, the fifth hierarchy is UDP, and the sixth hierarchy is ROUTE or FLUTE. Further, the fourth to sixth layers are PSI / SI.

That is, in the broadcast stack having the twelfth stack configuration, not only PSI / SI but also IP packets including UDP packets are transmitted in a section format.

In addition, the communication stack of the twelfth stack configuration corresponds to the ATSC3.0 protocol stack as in the tenth stack configuration (FIG. 40). Has functions equivalent to middleware.

So far, the protocol stack configuration applicable to the method proposed by this technology has been described.

<4. Modification>

(Target method proposed by this technology)
In the above description, ATSC (particularly ATSC 3.0), which is a system adopted in the United States and the like, has been described as a broadcasting system for digital broadcasting. However, the system proposed by this technology is not limited to ATSC, but Japan. The present invention may be applied to broadcasting systems such as ISDB (Integrated Services Digital Broadcasting), which is a system adopted by the European Union, etc., and DVB (Digital Video Broadcasting), which is a system adopted by European countries.

In addition to terrestrial broadcasting, the system proposed by this technology is applicable to broadcasting systems such as satellite broadcasting using broadcasting satellites (BS) and communication satellites (CS), and cable broadcasting such as cable TV (CATV). It is possible to apply. Furthermore, the scheme proposed by the present technology can also be applied to various data transmission schemes such as the MPEG2-TS scheme and the IP transmission scheme.

In addition, the method proposed by the present technology assumes that a transmission path other than a broadcasting network such as terrestrial broadcasting, that is, a communication line (communication network) such as the Internet or a telephone network is used as a transmission path. The present invention can also be applied to predetermined standards (standards other than digital broadcasting standards) defined in the above.

(Other examples of applications and content)
The broadcast application is not limited to an application developed in a markup language such as HTML5 or a script language such as JavaScript (registered trademark), but may be an application developed in a programming language such as Java (registered trademark). .

The broadcast application is not limited to an application executed by the browser 109 (FIG. 3), and may be executed as a so-called native application in an OS (Operating System) environment (presentation control environment).

Furthermore, in the above description, a broadcast application distributed via broadcast has been described as an application. However, the application is not limited to the broadcast application, and may be a communication application distributed via communication such as the broadband network 3.

In addition, the content such as the above-mentioned terrestrial content and broadband content can include any content such as moving images, still images, music, electronic books, games, advertisements, etc. in addition to programs and commercials.

(Other system configuration)
In the above description, the content distribution system 1 in FIG. 1 has a configuration in which a server is provided for each function to be provided, such as the terrestrial broadcast stream server 20 or the terrestrial broadcast server 30, the broadband stream server 40 or the broadband server 50. Although shown, all or some of these functions may be combined and provided by one or more servers.

(Other)
Further, the above-mentioned names such as signaling and packet are examples, and other names may be used. However, the difference between the names is a formal difference, and the substantial contents of the target signaling and packet are not different. A packet and a frame may be used in the same meaning.

For example, AIT (Application Information Table) is sometimes called AST (Application Signaling Table). For example, a TLV (Type (Length Value) packet may be referred to as an ALP (ATSC Link-Layer Protocol) packet or the like. In addition, other names may be used for MIT (Multicast Information Table).

In this specification, 2K resolution is an image corresponding to a screen resolution of approximately 1920 × 1080 pixels, and 4K resolution is an image corresponding to a screen resolution of approximately 4000 × 2000 pixels.

Further, in the above description, 4K resolution content has been described as high quality content, but higher quality content such as 8K resolution may be used. However, 8K resolution is a video that corresponds to a screen resolution of approximately 7680 × 4320 pixels.

<5. Computer configuration>

The series of processes described above can be executed by hardware or software. When a series of processing is executed by software, a program constituting the software is installed in the computer.

FIG. 43 is a diagram illustrating a configuration example of hardware of a computer that executes the above-described series of processes by a program.

In the computer 1000, a CPU (Central Processing Unit) 1001, a ROM (Read Only Memory) 1002, and a RAM (Random Access Memory) 1003 are connected to each other via a bus 1004. An input / output interface 1005 is further connected to the bus 1004. An input unit 1006, an output unit 1007, a recording unit 1008, a communication unit 1009, and a drive 1010 are connected to the input / output interface 1005.

The input unit 1006 includes a keyboard, a mouse, a microphone, and the like. The output unit 1007 includes a display, a speaker, and the like. The recording unit 1008 includes a hard disk, a nonvolatile memory, and the like. The communication unit 1009 includes a network interface or the like. The drive 1010 drives a removable recording medium 1011 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory.

In the computer 1000 configured as described above, the CPU 1001 loads the program recorded in the ROM 1002 or the recording unit 1008 to the RAM 1003 via the input / output interface 1005 and the bus 1004 and executes the program. A series of processing is performed.

The program executed by the computer 1000 (CPU 1001) can be provided by being recorded on a removable recording medium 1011 as a package medium, for example. The program can be provided via a wired or wireless transmission medium such as a local area network, the Internet, or digital satellite broadcasting.

In the computer 1000, the program can be installed in the recording unit 1008 via the input / output interface 1005 by attaching the removable recording medium 1011 to the drive 1010. The program can be received by the communication unit 1009 via a wired or wireless transmission medium and installed in the recording unit 1008. In addition, the program can be installed in the ROM 1002 or the recording unit 1008 in advance.

Here, in the present specification, the processing performed by the computer according to the program does not necessarily have to be performed in chronological order in the order described as the flowchart. That is, the processing performed by the computer according to the program includes processing executed in parallel or individually (for example, parallel processing or object processing). The program may be processed by a single computer (processor) or may be distributedly processed by a plurality of computers.

Note that the embodiments of the present technology are not limited to the above-described embodiments, and various modifications can be made without departing from the gist of the present technology.

Also, the present technology can take the following configurations.

(1)
A processing unit that reserves in advance a multicast session for communication content that is distributed simultaneously with broadcast content, and transfers the communication content distributed using the multicast session to a request source when the communication content is requested An information processing apparatus.
(2)
The information processing apparatus according to (1), wherein the processing unit establishes the multicast session when a multicast reservation instruction is issued from a first apparatus that reproduces the broadcast content or the communication content.
(3)
The processing unit transmits the multicast to and from a second device that relays multicast in a communication network based on session description information for establishing the multicast session notified from the first device. The information processing apparatus according to (2), wherein a session is established.
(4)
The communication network includes an IP (Internet Protocol) network,
The information processing apparatus according to (3), wherein the session description information includes at least a destination multicast IP address and a port number in the multicast session.
(5)
The second device includes a router device,
In the IP network, route information between a plurality of router devices that relay an IP multicast stream from a communication server that performs multicast distribution of the communication content is generated when the multicast session is established. ).
(6)
The processing unit includes the multicast session with a second device that performs multicast relay in a communication network based on session description information for establishing the multicast session included in signaling distributed by multicast. The information processing apparatus according to (2).
(7)
The processing unit is configured to transmit the multicast to and from a second device that performs multicast relay in a communication network based on session description information for establishing the multicast session included in unicast distributed signaling. The information processing apparatus according to (2), wherein a session is established.
(8)
A receiver that receives the communication content multicast-delivered from a communication server via a communication network;
The information processing apparatus according to any one of (1) to (7), further including: a transmission unit configured to transmit the received communication content to the first apparatus that reproduces the broadcast content or the communication content.
(9)
A first receiving unit that receives the broadcast content transmitted as a broadcast wave;
A second receiving unit that receives the communication content distributed by multicast via a communication network;
The information processing apparatus according to any one of (1) to (7), further including: a reproduction unit that reproduces the broadcast content or the communication content.
(10)
In the information processing method of the information processing apparatus,
The information processing apparatus is
Pre-reserving a multicast session of communication content to be distributed simultaneously with broadcast content, and transferring the communication content distributed using the multicast session to a request source when the communication content is requested Information processing method.
(11)
A first receiver for receiving broadcast content transmitted as a broadcast wave;
A second receiving unit that receives communication content distributed by multicast via a communication network;
Requesting the start of a multicast session of the communication content that is multicast-delivered simultaneously with the broadcast content at a first timing, and requesting the communication content at a second timing that is later in time than the first timing A receiving device.
(12)
The first receiving unit receives a broadcast application transmitted as a broadcast wave,
The receiving device according to (11), wherein the processing unit requests the start of the multicast session at the first timing according to the operation of the broadcast application.
(13)
The first receiving unit receives signaling transmitted as a broadcast wave,
The receiving device according to (11), wherein the processing unit requests the start of the multicast session at the first timing according to the analysis result of the signaling.
(14)
The first receiving unit receives the signaling for all receivable channels,
The receiving device according to (13), wherein the processing unit requests the start of the multicast session at the first timing according to the analysis result of the signaling for all channels.
(15)
The processing unit requests the start of the multicast session by notifying the first device that reserves the multicast session of session description information for establishing the multicast session at the first timing. The receiving device according to (11).
(16)
The communication network includes an IP network,
A communication server that performs multicast distribution of the communication content is connected to the IP network,
In the IP network, a plurality of router devices that perform multicast relay are arranged,
The reception apparatus according to (15), wherein the session description information includes at least a destination multicast IP address and a port number in the multicast session.
(17)
The second receiving unit receives communication content to be unicast distributed via the communication network,
The first receiving unit receives an updated broadcast application transmitted as a broadcast wave or an event for the broadcast application when congestion is detected in the communication network,
The processor is
According to the operation of the broadcast application after the update or the broadcast application that has detected the event, at the first timing, request the start of a multicast session of communication content,
Requesting communication content to be distributed by multicast at the second timing;
The receiving device according to (12), wherein the second receiving unit receives communication content distributed by multicast via the communication network.
(18)
The receiving device according to (12), wherein the processing unit requests the communication content at the second timing according to an operation of the broadcast application.
(19)
The receiving device according to any one of (11) to (18), further including a reproducing unit that reproduces the broadcast content or the communication content.
(20)
A first receiver for receiving broadcast content transmitted as a broadcast wave;
In an information processing method of a receiving device comprising: a second receiving unit that receives communication content distributed by multicast via a communication network;
The receiving device is
Requesting the start of a multicast session of the communication content that is multicast-delivered simultaneously with the broadcast content at a first timing, and requesting the communication content at a second timing that is later in time than the first timing An information processing method including a step.

1 content distribution system, 2 terrestrial broadcast network, 3 broadband network, 10 broadcast content management system, 20 terrestrial broadcast stream server, 30 terrestrial broadcast server, 40 broadband stream server, 50 broadband server, 60 broadcast receiving device, 70 multicast termination device, 80, 80-1 to 80-5 multicast relay router, 101 processing unit, 102 input unit, 103 storage unit, 104 tuner, 105 broadcast middleware, 106 DASH client, 107 renderer, 108 output unit, 109 browser , 110 Communication I / F, 131 Broadcast control unit, 132 Communication control unit, 133 Net distribution schedule About preparation processing unit, 134 signaling processing unit, 201 processing unit, 202 communication I / F, 203 communication I / F, 231 multicast middleware, 232 web server, 233 signaling processing unit, 1000 computer, 1001 CPU

Claims

A processing unit that reserves in advance a multicast session for communication content that is distributed simultaneously with broadcast content, and transfers the communication content distributed using the multicast session to a request source when the communication content is requested An information processing apparatus.
The information processing apparatus according to claim 1, wherein the processing unit establishes the multicast session when a multicast reservation instruction is issued from a first apparatus that reproduces the broadcast content or the communication content.
The processing unit transmits the multicast to and from a second device that relays multicast in a communication network based on session description information for establishing the multicast session notified from the first device. The information processing apparatus according to claim 2, wherein a session is established.
The communication network includes an IP (Internet Protocol) network,
The information processing apparatus according to claim 3, wherein the session description information includes at least a destination multicast IP address and a port number in the multicast session.
The second device includes a router device,
5. The route information between a plurality of router devices that relay an IP multicast stream from a communication server that performs multicast distribution of the communication content in the IP network is generated when the multicast session is established. The information processing apparatus described in 1.
The processing unit includes the multicast session with a second device that performs multicast relay in a communication network based on session description information for establishing the multicast session included in signaling distributed by multicast. The information processing apparatus according to claim 2.
The processing unit is configured to transmit the multicast to and from a second device that performs multicast relay in a communication network based on session description information for establishing the multicast session included in unicast distributed signaling. The information processing apparatus according to claim 2, wherein a session is established.
A receiver that receives the communication content multicast-delivered from a communication server via a communication network;
The information processing apparatus according to claim 1, further comprising: a transmission unit that transmits the received communication content to a first device that reproduces the broadcast content or the communication content.
A first receiving unit that receives the broadcast content transmitted as a broadcast wave;
A second receiving unit that receives the communication content distributed by multicast via a communication network;
The information processing apparatus according to claim 1, further comprising: a reproduction unit that reproduces the broadcast content or the communication content.
In the information processing method of the information processing apparatus,
The information processing apparatus is
Pre-reserving a multicast session of communication content to be distributed simultaneously with broadcast content, and transferring the communication content distributed using the multicast session to a request source when the communication content is requested Information processing method.
A first receiver for receiving broadcast content transmitted as a broadcast wave;
A second receiving unit that receives communication content distributed by multicast via a communication network;
Requesting the start of a multicast session of the communication content that is multicast-delivered simultaneously with the broadcast content at a first timing, and requesting the communication content at a second timing that is later in time than the first timing A receiving device.
The first receiving unit receives a broadcast application transmitted as a broadcast wave,
The receiving device according to claim 11, wherein the processing unit requests the start of the multicast session at the first timing in accordance with an operation of the broadcast application.
The first receiving unit receives signaling transmitted as a broadcast wave,
The receiving device according to claim 11, wherein the processing unit requests the start of the multicast session at the first timing according to the analysis result of the signaling.
The first receiving unit receives the signaling for all receivable channels,
The receiving device according to claim 13, wherein the processing unit requests the start of the multicast session at the first timing according to the analysis result of the signaling for all channels.
The processing unit requests the start of the multicast session by notifying the first device that reserves the multicast session of session description information for establishing the multicast session at the first timing. The receiving device according to claim 11.
The communication network includes an IP network,
A communication server that performs multicast distribution of the communication content is connected to the IP network,
In the IP network, a plurality of router devices that perform multicast relay are arranged,
The receiving apparatus according to claim 15, wherein the session description information includes at least a destination multicast IP address and a port number in the multicast session.
The second receiving unit receives communication content to be unicast distributed via the communication network,
The first receiving unit receives an updated broadcast application transmitted as a broadcast wave or an event for the broadcast application when congestion is detected in the communication network,
The processor is
According to the operation of the broadcast application after the update or the broadcast application that has detected the event, at the first timing, request the start of a multicast session of communication content,
Requesting communication content to be distributed by multicast at the second timing;
The receiving device according to claim 12, wherein the second receiving unit receives communication content distributed by multicast via the communication network.
The receiving device according to claim 12, wherein the processing unit requests the communication content at the second timing in accordance with an operation of the broadcast application.
The receiving device according to claim 11, further comprising a reproducing unit that reproduces the broadcast content or the communication content.
A first receiver for receiving broadcast content transmitted as a broadcast wave;
In an information processing method of a receiving device comprising: a second receiving unit that receives communication content distributed by multicast via a communication network;
The receiving device is
Requesting the start of a multicast session of the communication content that is multicast-delivered simultaneously with the broadcast content at a first timing, and requesting the communication content at a second timing that is later in time than the first timing An information processing method including a step.