JP7082007B2 - Content receivers and programs - Google Patents

Description

The present invention relates to a content receiving device and a program that receives content such as a moving image and realizes a service linked to the content.

Conventionally, hybridcast is known as a broadcasting / communication cooperation system operated in Japan (see, for example, Non-Patent Document 1). The receiver device compatible with hybrid cast is equipped with an HTML browser, and can execute an HTML application acquired by communication.

A receiver device that supports hybrid cast can realize a service linked to the broadcast content by operating the HTML application triggered by the reception of the event message (Event Message: hereinafter referred to as EM) superimposed on the broadcast wave. can.

In addition, the hybrid cast compatible receiving device provides a function of exchanging messages between an HTML application operating on the receiving device and an application operating on a terminal such as a smartphone (hereinafter referred to as a linked terminal). ..

As a result, it is possible to realize a service linked with the broadcast content on the linked terminal. For example, in a soccer match program, when a player scores a score, detailed information about the player and the scoring scene can be displayed on the screen of the linked terminal (see, for example, Non-Patent Document 2). ..

IPTV regulations, broadcast communication cooperation system specifications, IPTVFJ STD-0010 2.1 version Ogawa et al., "Study of architecture for IoT device cooperation operation based on broadcast contents", Jijo Daizen, 7C-02, 2017

Conventionally, the EM is described as a simple character string and can function as a trigger for notifying that an event has occurred. However, it is difficult to express what happened in a certain scene in a program with a simple character string.

For example, suppose that "Kinuta_Ogawa_Goal" is transmitted from a broadcasting station to a content receiving device as an EM during a soccer match program. The person who wrote the EM can understand the contents accurately, but other people cannot understand the contents accurately. Specifically, "Team Kinuta's Ogawa scored the score" or "Team Kinuta was the FW (forward) of Team Ogawa and scored the score", or "Goalkeeper Kinuta scored Ogawa". It is difficult to tell whether the score has been decided. "

In order to understand the contents of such an EM, it is necessary to share the rules of the EM description method between the person who described the EM and the person who receives the EM.

However, since the scenes appearing in the program are diverse and the methods for expressing the scenes are also diverse, it is practically difficult to share the rules between the sender and the receiver of the EM.

In this way, in the current broadcasting, it is difficult to develop an application that realizes a service linked to the contents of the scene unless the developer of the application running on the linked terminal is the same as the sender of the EM. There was a problem.

Therefore, it has been desired that the developer of the application operating on the linked terminal can understand the contents of the EM and develop the application according to the contents of the EM.

That is, it has been desired that the linked terminal can receive a message that can interpret the content, not a message consisting of a simple character string, when the service linked to the content is realized. If the linked terminal can receive a message that can interpret the content, the developer can develop an application that interprets the content, and the linked terminal can realize a service linked to the content. Because.

Therefore, the present invention has been made to solve the above-mentioned problems, and an object of the present invention is to enable a linked terminal to interpret the content of a message when realizing a service linked with the content of the content. It is an object of the present invention to provide a content receiving device and a program for generating structured data in which the above is reflected.

In order to solve the above problem, the content receiving device according to claim 1 is a content receiving device that receives a signal of the content by broadcasting or communication and transmits a message for realizing a service linked to the content of the content to the terminal. In, a definition file is acquired based on the EM (event message) included in the signal of the content, structured data is acquired based on the EM and the definition file, and sEM (semantic) including the structured data is acquired. The EM / sEM conversion function unit for generating (event message) is provided, element information including the acquisition destination of the definition file is described in the EM, and the structured data is acquired in the definition file. A function for the purpose is defined, and in the structured data, each data constituting the message and the meaning of the data are structurally defined, and the EM / sEM conversion function unit of the content. The definition file is acquired from the EM extraction unit that extracts the EM from the signal and the acquisition destination described in the EM extracted by the EM extraction unit, and the function defined in the definition file is executed. , The structured data acquisition unit for acquiring the structured data and the element information described in the EM extracted by the EM extraction unit are replaced with the structured data acquired by the structured data acquisition unit. The sEM generation unit including the structured data is provided, and the sEM generated by the sEM generation unit is transmitted to the terminal.

Further, in the content receiving device according to claim 1, the content receiving device according to claim 1 includes a conversion identifier indicating whether or not the EM can be converted into the sEM in the element information of the EM. When the conversion identifier indicates that the EM can be converted to the sEM, the EM describes the element information including the acquisition destination of the definition file in addition to the conversion identifier. When the conversion identifier indicates that the EM cannot be converted to the sEM, the element information including the conversion identifier is described in the EM, and the EM / sEM conversion function unit further obtains the EM / sEM conversion function unit. The structured data acquisition unit includes an sEM determination unit that determines whether or not the EM can be converted to the sEM based on the conversion identifier described in the EM extracted by the EM extraction unit. If it is determined by the sEM determination unit that conversion is possible, the definition file is acquired from the acquisition destination described in the EM, and the function defined in the definition file is executed to execute the structured data. When the sEM generation unit determines that the sEM generation unit can be converted by the sEM determination unit, the element information described in the EM is replaced with the structured data, and the sEM is generated and output. When it is determined by the sEM determination unit that the conversion is not possible, the EM extracted by the EM extraction unit is output, and the content receiving device outputs the sEM or the EM output by the sEM generation unit. It is characterized by sending to a terminal.

Further, when the content receiving device according to claim 3 indicates that the conversion identifier of the EM can convert the EM to the sEM in the content receiving device according to the second aspect, the EM may be referred to. When the conversion identifier and the element information including the acquisition destination of the definition file are described, and the conversion identifier of the EM indicates that the EM cannot be converted to the sEM, the EM shall be: When the element information consisting of the conversion identifier and the character string is described and the conversion identifier is not described in the EM, the element information consisting of the character string is described in the EM. When the sEM determination unit indicates that the conversion identifier described in the EM extracted by the EM extraction unit indicates that the EM can be converted into the sEM, the sEM determination unit determines that the EM can be converted, and the conversion is performed. If the identifier indicates that the EM cannot be converted to the sEM, or if the conversion identifier is not described in the EM extracted by the EM extraction unit, it is determined that the conversion is not possible. It is a feature.

Further, the content receiving device according to claim 4 is the content receiving device according to any one of claims 1 to 3, wherein the acquisition destination included in the element information of the EM is an external server or an internal storage. When the information indicating the unit and the address of the external server are described and the acquisition destination described in the EM indicates the external server, the structured data acquisition unit is based on the address of the external server. When the acquisition destination indicates the internal storage unit, the definition file is acquired from the internal storage unit provided in the content receiving device.

Further, in the content receiving device according to claim 5, in the content receiving device according to claim 4, the structured data acquisition unit indicates the internal storage unit, and the acquisition destination described in the EM indicates the internal storage unit. When the definition file is not stored in the storage unit, the definition file is acquired based on the address of the external server, and the definition file is stored in the internal storage unit.

Further, the content receiving device according to claim 6 is the content receiving device according to any one of claims 1 to 5, wherein the EM further selects one from a plurality of structured data. Element information including an index is described, and the plurality of structured data are further defined in the definition file, and the structured data acquisition unit is described from the acquisition destination described in the EM. The definition file is acquired, the function defined in the definition file is executed, and one is selected from the plurality of structured data defined in the definition file based on the index described in the EM. This is characterized by acquiring the structured data.

Further, the content receiving device according to claim 7 is the content receiving device according to any one of claims 1 to 5, wherein the EM further constitutes the message transmitted to the terminal. Element information including an index for selecting the data from a plurality of elements is described, and the definition file further includes variables of the data that constitute the message and the variables corresponding to the variables. A plurality of elements are defined, and the structured data acquisition unit acquires the definition file from the acquisition destination described in the EM, executes the function defined in the definition file, and executes the function defined in the definition file in the EM. It is characterized in that the structured data is acquired by selecting one from the plurality of elements corresponding to each of the variables defined in the definition file based on the described index.

Further, the program of claim 8 is characterized in that the computer functions as the content receiving device according to any one of claims 1 to 7.

As described above, according to the present invention, when a service linked with the content of the content is realized, structured data reflecting the content of the message is generated so that the linked terminal can interpret the content of the message. Is possible.

It is a figure explaining the outline of the service example of the whole system including the content receiving apparatus by embodiment of this invention. It is a schematic diagram of the whole system including the content receiving apparatus by embodiment of this invention. It is a figure explaining the relationship between EM, sEM definition file f and sEM. It is a figure which shows the functional configuration example of the content receiving apparatus. It is a figure which shows the functional configuration example of the cooperation terminal. It is a block diagram which shows the configuration example of the content receiving apparatus. It is a block diagram which shows the structural example of the EM / sEM conversion function part. It is a flowchart which shows the processing example of the EM / sEM conversion function part. It is a flowchart which shows the detail of the sEM generation processing example (step S805). It is a figure which shows the 1st description example of EM. It is a figure which shows the 1st description example of the sEM definition file f. It is a figure which shows the 2nd description example of EM. It is a figure which shows the 2nd description example of the sEM definition file f. It is a figure which shows the 3rd description example of EM. It is a figure which shows the 3rd description example of the sEM definition file f. It is a figure explaining the outline of the service example of the other whole system including the content receiving apparatus by embodiment of this invention.

Hereinafter, embodiments for carrying out the present invention will be described in detail with reference to the drawings. The content receiving device of the present invention generates structured data reflecting the content so that the content of the message can be interpreted by the linked terminal when realizing a service linked with the content of the content, and the structured data is concerned. It is characterized by transmitting data to a linked terminal.

In the above example, using structured data means that, in response to the message "Tsuki_Ogawa_Goal", each of "Tsuki", "Ogawa", and "Goal" is a "team to which the action subject belongs" and "action subject (human)". ) Name ”and“ behavior ”. That is, the structured data is a definition sentence in which each data (content) constituting the message and the meaning of the data (meaning of the content) are structurally defined.

As a result, the linked terminal can understand the content of the message by interpreting the structured data. In other words, by using structured data, message recipients can understand the meaning of messages and develop applications according to them, without having to share rules with senders in advance.

By the way, by a broadcasting station generating an EM including structured data and transmitting the EM to a cooperative terminal via a content receiving device, a service linked with the content of the content can be realized.

However, the band of the broadcast wave is limited, and the amount of data that can be described in the private_data (private data) element (hereinafter referred to as pd element) of the EM transmitted from the broadcasting station is limited to 244 bytes or less (operational limitation). Refer to terrestrial digital television broadcasting operation regulations, ARIB TR-B14 6.3 version). On the other hand, structured data is not a simple character string but a structural definition statement including the meaning of the content of the message, so it is difficult to fit it within 244 bytes. Therefore, even if the broadcasting station generates an EM containing structured data, it cannot transmit it as a broadcasting signal.

Therefore, the content receiving device according to the embodiment of the present invention acquires structured data based on the contents described in the pd element of the EM when the EM including the pd element of 244 bytes or less is received. It has a function. Then, the content receiving device replaces the content of the pd element of the EM with the acquired structured data, thereby generating a new EM including the structured data, and transmitting the new EM to the linked terminal.

The linked terminal receives the new EM and interprets the structured data contained in the new EM. As a result, it is possible to realize a service linked to the content of the content. In this case, since the structured data is predetermined, the recipient of the message can develop an application based on the structured data in advance.

Here, since the new EM having structured data in the pd element is an event message expressing a semantic (semantic), it is called a semantic event message (Semantic Event Message). Hereinafter, the semantic event message is referred to as sEM. The sEM is a message for realizing a service linked with the content of the content in the linked terminal.

In addition, since broadcasting has the characteristic of simultaneity, if the content receiving device inquires of the server for the information necessary to acquire structured data every time it receives an EM on the broadcast wave, the server will be instantaneously used. Access to is concentrated, and the server load may increase.

Therefore, the content receiving device according to the embodiment of the present invention stores the information necessary for acquiring the structured data in the storage unit in advance, and receives the EM as an opportunity to store the information without accessing the server. It has a function to be used directly.

[Overall system]
First, an overall system that realizes a service linked to the content will be described. FIG. 1 is a diagram illustrating an outline of a service example of an overall system including a content receiving device according to an embodiment of the present invention, and FIG. 2 is a schematic diagram of an overall system including a content receiving device 2 according to an embodiment of the present invention. Is.

This system includes a broadcast transmission device 1, a content reception device 2, a cooperation terminal 3, an sEM server 4, a reception device service server 5, and a cooperation terminal service server 6. The content receiving device 2, the sEM server 4, and the receiving device service server 5 are connected to each other via the Internet 8. The linked terminal service server 6 and the linked terminal 3 are connected to each other via the Internet 8. Further, the content receiving device 2 and the cooperation terminal 3 are connected to each other via a communication path 7 such as Wi-Fi (registered trademark) by a function such as Hybridcast (hybridcast).

The broadcast transmission device 1 is provided in a broadcasting station, and distributes a broadcast signal of program contents (including EM) by a broadcast wave.

When the content receiving device 2 receives the broadcast signal including the EM and determines that the EM can be converted into the sEM based on the contents of the EM, the content receiving device 2 specifies the sEM definition file f based on the contents of the EM, for example, the sEM. Receive the sEM definition file f from the server 4. Then, the content receiving device 2 acquires structured data based on the contents of the EM and the sEM definition file f, and generates an sEM including the structured data. The content receiving device 2 transmits the sEM to the linked terminal 3 connected by a function such as a hybrid cast.

The cooperative terminal 3 is a terminal such as a smartphone, a communication robot, or a smart home appliance, and operates in cooperation with the content receiving device 2. The cooperative terminal 3 receives the sEM from the content receiving device 2, interprets the content based on the structured data included in the sEM, and realizes a service linked with the content of the content.

The sEM server 4 manages the sEM definition file f, and transmits the sEM definition file f to the content receiving device 2 in accordance with the request from the content receiving device 2.

The receiving device service server 5 manages the HTML application main body executed by the content receiving device 2 and the content used in the HTML application, and the HTML application main body and the content are transferred to the content receiving device 2 in accordance with the request from the content receiving device 2. Send to.

The linked terminal service server 6 manages the application executed by the linked terminal 3 and the content used by the linked terminal 3, and transmits the application and the content to the linked terminal 3 in accordance with the request from the linked terminal 3.

In this case, the content receiving device 2 has already downloaded the HTML application main body or the like for realizing the service linked with the content of the content from the receiving device service server 5, and executes the application. Further, the linked terminal 3 has already downloaded an application or the like for realizing a service linked with the content of the content from the linked terminal service server 6, and it is assumed that the application is executed.

FIG. 3 is a diagram illustrating the relationship between the EM, the sEM definition file f, and the sEM. (1) shows a specific example of EM, (2) shows a configuration example of the sEM definition file f, and (3) shows a specific example of sEM.

The content receiving device 2 specifies the sEM definition file f shown in (2) based on the contents of the EM pd element shown in (1), and is structured based on the contents of the EM pd element and the sEM definition file f. Get the data. Then, the content receiving device 2 replaces the content of the pd element of the EM with the structured data, and generates the sEM shown in (3).

The EM is a message transmitted from the broadcast transmission device 1, and a pd element is described. The pd element of EM includes the following (a1) to (a6). In addition, the pd element of EM may not include (a5), (a6) and the like among (a1) to (a6). Specific examples will be described with reference to FIGS. 10, 12, and 14 described later.
(A1) Identifier indicating whether or not EM can be converted to sEM (sEM conversion identifier, "true" or "false")
(A2) Acquisition destination a2 of the sEM definition file f (external server (sEM server 4, "external") or internal memory (storage unit 46, "internal" described later))
(A3) Name of sEM definition file f (file name)
(A4) Acquisition URL (address) of the sEM definition file f
(A5) Information required to acquire structured data (hereinafter referred to as index)
(A6) Other information

The sEM definition file f is a file transmitted from the sEM server 4, and is information necessary for acquiring structured data, that is, what kind of structured data is acquired when converting EM to sEM. Rule is defined. The sEM definition file f includes the following (b1) to (b4). The sEM definition file f may not include (b3) or the like among (b1) to (b4).
(B1) Structured data or an array of structured data (multiple structured data)
(B2) Function for acquiring structured data (b3) Time-to-live of sEM definition file f (b4) Other information

As shown in (3), the sEM includes a pd element containing structured data. The sEM is generated by replacing the pd element of the EM with the structured data.

[Functional configuration of content receiving device 2 and linked terminal 3]
Next, the functional configurations of the content receiving device 2 and the cooperative terminal 3 will be described. FIG. 4 is a diagram showing a functional configuration example of the content receiving device 2. From a functional point of view, the content receiving device 2 is composed of hardware 20, OS 21, resident 22, and application execution function unit 23.

The hardware 20 is a CPU, ROM, RAM, cache memory, etc., and physically executes each function of the resident 22. The OS 21 is an iOS or the like, which is executed by a CPU and manages each element of the hardware 20 as a basic function of the content receiving device 2.

The resident 22 includes a receiver function unit 24, a terminal cooperation function unit 25, an EM / sEM conversion function unit 26, and the like. The receiver function unit 24 receives the broadcast signal, decodes the broadcast signal into video and audio, and reproduces the broadcast signal. The terminal cooperation function unit 25 connects the content receiving device 2 and the cooperation terminal 3 via the communication path 7, and transmits / receives text messages.

The EM / sEM conversion function unit 26 is a function provided in the embodiment of the present invention, and converts EM into sEM.

The application execution function unit 23 is an HTML browser (hybrid cast browser) and executes a hybrid cast application downloaded from the receiving device service server 5.

FIG. 5 is a diagram showing a functional configuration example of the cooperative terminal 3. From a functional point of view, the linked terminal 3 is composed of the hardware 50, the OS 51, the native application execution function unit 52, and the linked application 53.

The hardware 50 is a CPU, ROM, RAM, cache memory, etc., like the hardware 20 of FIG. 4, and physically executes each function of the native application execution function unit 52. The OS 51 is executed by the CPU in the same manner as the OS 21 of FIG. 4, and manages each element of the hardware 50 as a basic function of the linked terminal 3.

The native application execution function unit 52 executes the application provided by the OS 51. It is assumed that the linked application 53 operates in the native application execution function unit 52. The cooperation application 53 in the hybrid cast is realized between the hybrid cast application operated by the hybrid cast browser of the content receiving device 2 and the cooperation application 53 of the cooperation terminal 3. The linked application 53 sends and receives text messages using, for example, the extended API defined in Non-Patent Document 1 described above.

[Configuration and processing of content receiving device 2]
Next, the configuration and processing of the content receiving device 2 will be described. FIG. 6 is a block diagram showing a configuration example of the content receiving device 2. The content receiving device 2 includes a resident 22', an application execution unit 30, and an HTML application 31.

The resident 22'receives a broadcast signal from the broadcast transmission device 1, extracts an EM from the broadcast signal, and determines whether or not the EM can be converted into an sEM based on the content of the pd element of the EM.

When the resident 22'determines that the EM can be converted into the sEM, the resident 22'generates the sEM and transmits the sEM to the cooperation terminal 3. On the other hand, when the resident 22'determines that the EM cannot be converted into the sEM, the resident 22'transmits the EM to the cooperation terminal 3.

The application execution unit 30 is a browser that executes the HTML application 31. The HTML application 31 is an application for transmitting and receiving text messages between the content receiving device 2 and the linked terminal 3 in order to link broadcasting and communication, and is acquired from a receiving device service server 5 (not shown). Here, the application execution unit 30 executes the HTML application 31 at the timing when the EM is extracted from the broadcast signal data by, for example, the EM / sEM conversion function unit 26, and executes the HTML application 31 with the content receiving device 2 and the cooperation terminal 3. Send and receive text messages between.

The resident 22'includes an EM / sEM conversion function unit 26, a broadcast receiving unit 27, a separation unit 28, a broadcast communication cooperation unit 29, and a terminal cooperation unit 32. Although this resident 22'corresponds to the resident 22 shown in FIG. 4, only the components directly related to the present invention are shown, and the components not directly related to the present invention are omitted.

The broadcast receiving unit 27 receives the broadcast signal of the broadcast wave transmitted from the broadcast transmission device 1 and performs a predetermined reception process. The separation unit 28 separates the multiplex signal from the broadcast signal received and processed by the broadcast reception unit 27, extracts video, audio, and data, and outputs the data to the EM / sEM conversion function unit 26.

The EM / sEM conversion function unit 26 inputs data from the separation unit 28, and determines whether or not the EM can be converted to the sEM based on the EM included in the data.

When the EM / sEM conversion function unit 26 determines that the EM can be converted to the sEM, the EM / sEM conversion function unit 26 specifies the sEM definition file f based on the contents of the pd element of the EM, and obtains the sEM definition file f from the sEM server 4, for example. do. Then, the EM / sEM conversion function unit 26 acquires structured data based on the contents of the pd element of the EM and the sEM definition file f, replaces the contents of the pd element of the EM with the structured data, and generates the sEM. The sEM is output to the broadcast communication cooperation unit 29.

On the other hand, when the EM / sEM conversion function unit 26 determines that the EM cannot be converted to the sEM, the EM / sEM conversion function unit 26 outputs the EM to the broadcast communication cooperation unit 29. Details of the EM / sEM conversion function unit 26 will be described later.

The broadcast communication cooperation unit 29 inputs sEM or EM from the EM / sEM conversion function unit 26, and transmits the sEM or EM from the terminal cooperation unit 32 to the cooperation terminal 3 by the HTML application 31.

The broadcast communication cooperation unit 29 performs a process of merging the data obtained from the broadcast and the data obtained from the communication, and the terminal cooperation unit 32 performs a process of linking the content receiving device 2 and the cooperation terminal 3. And send and receive text messages to each other by communication.

[EM / sEM conversion function unit 26]
Next, the EM / sEM conversion function unit 26 will be described in detail. FIG. 7 is a block diagram showing a configuration example of the EM / sEM conversion function unit 26, and FIG. 8 is a flowchart showing a processing example of the EM / sEM conversion function unit 26.

The EM / sEM conversion function unit 26 includes an EM extraction unit 40, an sEM determination unit 41, a structured data acquisition unit 42, an external resource acquisition unit 43, a storage management unit 44, a cache unit 45, a storage unit 46, and an sEM generation unit 47. It is equipped with.

The EM extraction unit 40 inputs data from the separation unit 28 (step S801) and extracts EM from the data (step S802). Then, the EM extraction unit 40 outputs the EM to the sEM determination unit 41 and the sEM generation unit 47.

The sEM determination unit 41 inputs an EM from the EM extraction unit 40, and determines whether or not the EM can be converted to the sEM based on the sEM conversion identifier a1 included in the pd element of the EM (step S803).

When the sEM determination unit 41 determines that the sEM conversion identifier a1 is "true" and sEM conversion is possible (step S804: Y), the sEM determination unit 41 outputs conversion possible to the sEM generation unit 47 and outputs the EM to the structured data. Output to the acquisition unit 42.

When the sEM generation unit 47 inputs conversion possible from the sEM determination unit 41, the sEM generation unit 47 replaces the content of the EM pd element input from the EM extraction unit 40 with the structured data input from the structured data acquisition unit 42, and generates an sEM. (Step S805), and output the sEM to the broadcast communication cooperation unit 29 (step S806). Specifically, the sEM generation process in step S805 is performed by the structured data acquisition unit 42 to the sEM generation unit 47. Details of the sEM generation process in step S805 will be described later.

Here, the structured data acquisition unit 42 to the sEM generation unit 47 specify the sEM definition file f based on the contents of the EM pd element, and the structured data based on the contents of the EM pd element and the sEM definition file f. Is acquired, the contents of the pd element of EM are replaced with structured data, and sEM is generated.

On the other hand, when the sEM determination unit 41 determines that the sEM conversion identifier a1 is "false" and the sEM conversion is not possible (step S804: N), the sEM determination unit 41 outputs the non-conversion to the sEM generation unit 47. When the sEM generation unit 47 inputs that conversion is not possible from the sEM determination unit 41, the sEM generation unit 47 outputs the EM input from the EM extraction unit 40 to the broadcast communication cooperation unit 29 as it is (step S807).

In steps S802 and S803, the sEM determination unit 41 determines that the sEM conversion is not possible even if the pd element of the EM does not include the sEM conversion identifier a1, and outputs that conversion is not possible to the sEM generation unit 47. In the EM determined not to be sEM convertible, a message consisting of a simple character string is described as in the conventional case.

(SEM generation process)
Next, the sEM generation process in step S805 of FIG. 8 will be described in detail. FIG. 9 is a flowchart showing the details of the sEM generation processing example (step S805). The processing shown in FIG. 9 is performed by the structured data acquisition unit 42 to the sEM generation unit 47.

When the sEM determination unit 41 determines that the sEM conversion is possible, the structured data acquisition unit 42 acquires the sEM definition file f based on the contents of the EM pd element, and acquires the sEM definition file f, and the contents of the EM pd element and sEM. The structured data is acquired based on the definition file f.

The external resource acquisition unit 43 has a function of acquiring necessary resources by communication with the sEM server 4, and acquires the sEM definition file f from the sEM server 4.

The storage management unit 44 manages the cache unit 45 and the storage unit 46. Specifically, the storage management unit 44 acquires the sEM definition file f, which is a resource necessary for acquiring structured data, from the sEM server 4 via the external resource acquisition unit 43, and stores it in the storage unit 46. Further, the storage management unit 44 reads the sEM definition file f from the storage unit 46 and stores it in the cache unit 45. Further, the storage management unit 44 searches for and deletes unnecessary data among the data stored in the storage unit 46.

The storage unit 46 and the cache unit 45 hold the sEM definition file f, which is a resource.

With reference to FIGS. 7 and 9, the structured data acquisition unit 42 inputs an EM from the sEM determination unit 41, and based on the acquisition destination a2 of the sEM definition file f included in the pd element of the EM, the acquisition destination a2. Is external or internal (step S901).

When the structured data acquisition unit 42 determines that the acquisition destination a2 of the sEM definition file f is "external" and the acquisition destination is external (step S902: external), the sEM server via the external resource acquisition unit 43. Acquire the sEM definition file f from 4 (step S903). Then, the structured data acquisition unit 42 shifts to step S911.

Specifically, the structured data acquisition unit 42 outputs the acquisition destination URL a4 of the sEM definition file f included in the pd element of the EM to the external resource acquisition unit 43. The external resource acquisition unit 43 inputs the acquisition destination URL a4 of the sEM definition file f from the structured data acquisition unit 42, sends an httpGET request request to the sEM server 4 indicated by the acquisition destination URL a4, and the sEM server 4 sends the sEM definition file f. To get. Then, the external resource acquisition unit 43 outputs the sEM definition file f to the structured data acquisition unit 42.

On the other hand, when the structured data acquisition unit 42 determines in step S902 that the acquisition destination a2 of the sEM definition file f is "internal" and the acquisition destination is internal (step S902: internal), the sEM definition file f. (Step S904). The storage destination of the sEM definition file f is basically the cache unit 45 or the storage unit 46, but if it is not stored in either the cache unit 45 or the storage unit 46, it is acquired from the sEM server 4.

Specifically, the structured data acquisition unit 42 outputs the name a3 of the sEM definition file f and the acquisition destination URL a4 included in the pd element of the EM to the storage management unit 44. The storage management unit 44 inputs the name a3 of the sEM definition file f and the acquisition destination URL a4 from the structured data acquisition unit 42.

The storage management unit 44 compares the name a3 of the sEM definition file f with the name of the file stored in the cache unit 45, and determines whether or not the sEM definition file f is stored in the cache unit 45 (. Step S905).

When the storage management unit 44 determines that the file names match and the sEM definition file f is stored in the cache unit 45 (step S905: Y), the storage destination of the sEM definition file f is the cache unit 45. It is determined that the process proceeds to step S909.

On the other hand, when the storage management unit 44 determines that the file names do not match and the sEM definition file f is not stored in the cache unit 45 (step S905: N), the storage management unit 44 proceeds to step S906. Then, the storage management unit 44 compares the name a3 of the sEM definition file f with the name of the file stored in the storage unit 46, and determines whether or not the sEM definition file f is stored in the storage unit 46. (Step S906).

When the storage management unit 44 determines that the file names match and the sEM definition file f is stored in the storage unit 46 (step S906: Y), the storage destination of the sEM definition file f is the storage unit 46. It is determined that the process proceeds to step S908.

On the other hand, when the storage management unit 44 determines that the file names do not match and the sEM definition file f is not stored in the storage unit 46 (step S906: N), the sEM definition file f is stored in the cache unit 45 and the storage unit f. It is determined that the file is not stored in any of the parts 46. Then, the storage management unit 44 acquires the sEM definition file f from the sEM server 4 via the external resource acquisition unit 43. The storage management unit 44 stores the sEM definition file f in the storage unit 46 under the name a3 of the sEM definition file f or a predetermined name set by the user (step S907), and proceeds to step S908.

Specifically, the storage management unit 44 outputs the acquisition destination URL a4 of the sEM definition file f to the external resource acquisition unit 43 in the same manner as in step S903. The external resource acquisition unit 43 sends an httpGET request request to the sEM server 4 indicated by the acquisition destination URLa4, acquires the sEM definition file f from the sEM server 4, and outputs the sEM definition file f to the storage management unit 44.

The storage management unit 44 proceeds from step S906 (Y) or step S907, reads the sEM definition file f from the storage unit 46, saves the sEM definition file f in the cache unit 45 (step S908), and proceeds to step S909. do.

The storage management unit 44 shifts from step S905 (Y) or step S908 and outputs a completion notification to the structured data acquisition unit 42 (step S909). That is, the storage management unit 44 determines that the sEM definition file f is stored in the cache unit 45, or determines that the sEM definition file f is stored in the storage unit 46, and caches the sEM definition file f from the storage unit 46. When copying to the unit 45, or when the sEM definition file f is not stored in either the cache unit 45 or the storage unit 46 and is acquired from the sEM server 4 and stored in the cache unit 45 and the storage unit 46. Notify the completion.

When the structured data acquisition unit 42 inputs the completion notification from the storage management unit 44, the structured data acquisition unit 42 reads the sEM definition file f from the cache unit 45 (step S910). Then, the structured data acquisition unit 42 shifts from step S903 or step S910 to acquire structured data based on the contents of the pd element of EM and the sEM definition file f (step S911), and sEM the structured data. Output to the generation unit 47.

For example, in step S911, the structured data acquisition unit 42 executes the function b2 defined in the sEM definition file f with the index a5 included in the pd element of the EM as an argument, and various data defined in the sEM definition file f. Get structured data using. In the sEM definition file f, a predetermined number of structured data of 1 or more may be defined, or data such as variables for generating the structured data may be defined. Details will be described with reference to FIGS. 10 to 15 described later.

The sEM generation unit 47 inputs structured data from the structured data acquisition unit 42, replaces the pd element of the EM input from the EM extraction unit 40 with the structured data, and converts the EM into the sEM to generate the sEM. (Step S912).

If the structured data acquisition unit 42 fails to acquire the structured data, the structured data acquisition unit 42 outputs the acquisition failure to the sEM generation unit 47. Specifically, when the structured data acquisition unit 42 does not input the sEM definition file f even after a predetermined time has elapsed after outputting the acquisition destination URL a4 of the sEM definition file f to the external resource acquisition unit 43, the sEM definition file If the completion notification is not input even after a predetermined time has elapsed since the name a3 and the acquisition destination URL a4 of f are output to the storage management unit 44, or after the request for reading the sEM definition file f is output to the cache unit 45. If the reading cannot be performed even after the lapse of a predetermined time, it is determined that the acquisition of the structured data has failed.

Then, the structured data acquisition unit 42 outputs the processing stop notification to the external resource acquisition unit 43, the storage management unit 44, and the cache unit 45, respectively, and outputs the acquisition failure to the sEM generation unit 47.

When the sEM generation unit 47 inputs an acquisition failure from the structured data acquisition unit 42, the sEM generation unit 47 outputs the EM input from the EM extraction unit 40 to the broadcast communication cooperation unit 29 as it is.

In this way, the EM / sEM conversion function unit 26 determines whether or not the EM can be converted to the sEM based on the contents of the pd element of the EM, and if the EM can be converted to the sEM, the sEM definition file f is displayed. It is acquired from the sEM server 4, the cache unit 45 or the storage unit 46, and the structured data is acquired based on the contents of the pd element of the EM and the sEM definition file f. Then, an sEM containing structured data is generated.

As a result, the sEM including the structured data is transmitted to the linked terminal 3, so that the linked terminal 3 can interpret the contents of the EM based on the structured data, and realizes a service linked with the contents of the contents. can do.

[Description example of EM and sEM definition file f]
Next, a description example of the EM and the sEM definition file f will be specifically described. As described above, the sEM definition file f is information necessary for acquiring structured data, and rules for converting EM to sEM are defined.

If the sender of the EM and the writer of the sEM definition file f are the same, the contents described in the EM and the sEM definition file f may be freely determined for each use case except for some essential items. Hereinafter, three typical description examples of the EM and sEM definition files f for each use case will be described.

(First description example)
The first description example is a case where the format of the message to be transmitted during the program is predetermined. For example, a recorded program or a live broadcast program that progresses according to a scenario. In the first description example, since it is possible to determine in advance what kind of message should be transmitted in which scene of the program, a plurality of structured data are described in advance as an array in the sEM definition file f.

The content receiving device 2 saves the sEM definition file f in the cache unit 45 before the timing when the sEM fires. The EM is then used to indicate the timing of firing the sEM and to indicate the index of the required structured data in the structured data array.

FIG. 10 is a diagram showing a first description example of EM. In the pd element of this EM, the sEM conversion identifier a1, the acquisition destination a2 of the sEM definition file f, the name a3 of the sEM definition file f, the acquisition destination URL a4 of the sEM definition file f, and the index a5 are described.

The sEM conversion identifier a1 "" is_transposable ": true" indicates that the EM can be converted into an sEM.

In "" sEM_source_type ":" internal "", which is the acquisition destination a2 of the sEM definition file f, the sEM definition file f related to the EM is stored inside the content receiving device 2 (cache unit 45 or storage unit 46). Indicates that there is a possibility. Further, if it is not stored internally, it indicates that the content receiving device 2 should store the sEM definition file f internally after acquiring the sEM definition file f from the sEM server 4.

The “sEM_source_file_name:“ program_1 ””, which is the name a3 of the sEM definition file f, indicates a file name used when confirming the existence of the sEM definition file f or when saving the sEM definition file f in the storage unit 46. ing. For example, the storage management unit 44 uses this name when confirming which sEM definition file f the file stored in the cache unit 45 or the storage unit 46 is.

““ SEM_source_url ”: http: // ...”, which is the acquisition destination URL a4 of the sEM definition file f, indicates the URL of the sEM server 4. When the sEM definition file f is not stored in the cache unit 45 and the storage unit 46, the storage management unit 44 acquires the sEM definition file f from the sEM server 4 via the external resource acquisition unit 43.

The index a5 "" index ": 1" is an argument (select one structured data) that specifies which structured data to acquire from the structured data array defined in the sEM definition file f. Arguments to do) are shown. In this example, it is shown that the first structured data is acquired.

FIG. 11 is a diagram showing a first description example of the sEM definition file f. In this sEM definition file f, an array b1, a function b2, a survival time b3, and the like of structured data are defined.

“Var file_status” indicates general information related to the sEM definition file f. ““ Program id ”: ...” indicates an identifier indicating which program the sEM definition file f is related to.

The “expiration date”: ... ”, which is the survival period b3, indicates the survival period of the sEM definition file f. The storage management unit 44 has a function of periodically organizing the sEM definition file f stored in the storage unit 46. The storage management unit 44 deletes the sEM definition file f when the survival period b3 is earlier than the current time according to the survival period b3 defined in the sEM definition file f stored in the storage unit 46.

Further, in "var data_set" which is an array b1 of structured data, two structured data are defined as an array of structured data. Here, each element of the array is shown to be structured data of the sEM that fires at one event.

The function b2 "get_data = function (EM) ..." indicates a function that specifies an element of an array of structured data by the value of the index a5 described in the pd element of EM.

In the first description example shown in FIGS. 10 and 11, the structured data acquisition unit 42 executes the function b2 defined in the sEM definition file f with the index a5 described in the pd element of the EM as an argument. Then, the structured data indicated by the index a5 is acquired from the structured data array.

(Second description example)
The second description example is a case where the format of the message to be transmitted during the program is determined, but the variables need to be replaced. For example, a soccer match broadcast is applicable. Events (fouls, PKs, goals, etc.) that occur during a soccer match are limited to some extent and can be determined in advance.

However, the factors related to the event (players who scored goals, assisted players, their teams, time of occurrence, etc.) cannot be determined in advance. Therefore, in the second description example, the format information and the value information that can be assigned to the variable part of the format are described in the sEM definition file f. The EM is also used to notify the firing timing of the event and information for specifying variables related to the event.

FIG. 12 is a diagram showing a second description example of EM. In the pd element of this EM, the sEM conversion identifier a1, the acquisition destination a2 of the sEM definition file f, the name a3 of the sEM definition file f, the acquisition destination URL a4 of the sEM definition file f, the index a5, and other information a6 are described. There is.

The sEM conversion identifier a1 "" is_transposable ": true" indicates that the EM can be converted into an sEM.

““ SEM_source_type ”:“ internal ””, which is the acquisition destination a2 of the sEM definition file f, indicates that the sEM definition file f related to the EM may be stored inside the content receiving device 2. ..

The “sEM_source_file_name:“ program_1 ””, which is the name a3 of the sEM definition file f, indicates a file name used when confirming the existence of the sEM definition file f or when saving the sEM definition file f in the storage unit 46. ing.

““ SEM_source_url ”: http: // ...”, which is the acquisition destination URL a4 of the sEM definition file f, indicates the URL of the sEM server 4.

The index a5 "" index ": [1,1,1,1]" is an array of arguments that specify which element is to be acquired for each of the plurality of variables defined in the sEM definition file f. Shows. In this example, it is shown that the first element is acquired for each of the four variables.

The other information a6, "" time: ... "", Indicates the time when the event occurred.

FIG. 13 is a diagram showing a second description example of the sEM definition file f. In this sEM definition file f, a function b2, a survival time b3, other information b4, and the like are defined.

“Var file_status” indicates general information related to the sEM definition file f. ““ Program id ”: ...” indicates an identifier indicating which program the sEM definition file f is related to. The “expiration date”: ... ”, which is the survival period b3, indicates the survival period of the sEM definition file f.

The function b2 "get_data = function (EM) ..." specifies the time when the event occurred from the other information a6 "" time: ... "" described in the pd element of EM. , The function that specifies the element from the array of variables is shown by the value of the index a5 described in the pd element of EM.

Other information b4, such as "var event = ...", indicates a variable or the like. The variable "event" is an array indicating the type of event. Each element that makes up this array defines the types of events that occur during the match (“foul”, “penalty_kick”, “goal”).

Similarly, the variable "player_name" is an array showing the names of the players involved in the event, and the variables "role" and "belonging" indicate the role played by that player in the event and the team to which the player belongs, respectively. It is the arrangement shown.

The sender of the EM knows the contents of each variable in advance. Then, when some event occurs during the match, an EM including an array of index a5 is transmitted in order to acquire structured data from the contents of these variables. That is, the index a5 is set with an array of arguments that specify which element (content) to acquire for each of the four variables.

For example, when the event "Team Kinuta's foul was taken" occurs, as shown in FIG. 12, the index a5 in which the argument array [1,1,1,1] is set is included. EM is sent.

The first "1" in the argument array [1,1,1,1] indicates the event type "foul", and the second "1" is the player's name "kinuta taro" (砧). Taro) is shown. Also, the third "1" indicates the player's role "offender" (the violator who was fouled as an event), and the fourth "1" is the player's team "kinuta" (team).砧) indicates that it is.

The function b2 (get_data function) described in the sEM definition file f acquires the time when the event occurred from "" time: ... "", which is other information a6 described in the pd element of the EM, and also obtains the time when the event occurred. By specifying one element from the array of four variables "event", "player_name", "role", and "belonging" according to the value of index a5 and acquiring each element, the time when the event occurred. And generate structured data consisting of each element.

In the second description example shown in FIGS. 12 and 13, the structured data acquisition unit 42 uses the function b2 defined in the sEM definition file f as the index a5 and other information a6 described in the pd element of the EM. By executing it as an argument, the time when the event occurs is acquired from EM, the elements are acquired from the array of variables defined in the sEM definition file f, and the structured data including these elements is generated.

(Third description example)
The third description example is a case where the format of the message to be transmitted during the program is not determined. For example, a live program is applicable. In live programs, it may not be possible to predict in advance what kind of event will occur. In this case, the content receiving device 2 acquires the sEM definition file f from the sEM server 4 every time the EM is received.

FIG. 14 is a diagram showing a third description example of EM. In the pd element of this EM, the sEM conversion identifier a1, the acquisition destination a2 of the sEM definition file f, and the acquisition destination URL a4 of the sEM definition file f are described.

The sEM conversion identifier a1 "" is_transposable ": true" indicates that the EM can be converted into an sEM.

““ SEM_source_type ”:“ external ””, which is the acquisition destination a2 of the sEM definition file f, indicates that the sEM definition file f related to the EM is stored in the external sEM server 4. Further, since this sEM definition file f is temporary, it is shown that it is not necessary to save it in the storage unit 46 of the content receiving device 2.

““ SEM_source_url ”: http: // ...”, which is the acquisition destination URL a4 of the sEM definition file f, indicates the URL of the sEM server 4.

FIG. 15 is a diagram showing a third description example of the sEM definition file f. Structured data b1 and function b2 are defined in this sEM definition file f.

The structured data b1 "var sEM = ..." indicates that the structured data is not an array but a JSON object.

The function b2 "get_sEM = function () ..." indicates that it is a function that simply returns the structured data b1 "var sEM = ...".

In the third description example shown in FIGS. 14 and 15, the structured data acquisition unit 42 executes the function b2 defined in the sEM definition file f to obtain the structured data defined in the sEM definition file f. get.

As described above, according to the content receiving device 2 of the embodiment of the present invention, the EM extraction unit 40 of the EM / sEM conversion function unit 26 extracts the EM from the data included in the broadcast signal, and the sEM determination unit 41 , It is determined whether or not EM can be converted to sEM based on the sEM conversion identifier a1 included in the pd element of EM.

When the structured data acquisition unit 42 determines that the EM can be converted to the sEM, the structured data acquisition unit 42 acquires the sEM definition file f from the external sEM server 4 or from the internal cache unit 45 or the storage unit 46, and obtains the sEM definition file f of the EM. Structured data is acquired based on the contents of the pd element and the sEM definition file f.

When it is determined that the EM can be converted into the sEM, the sEM generation unit 47 replaces the contents of the pd element of the EM with the structured data, generates the sEM, and outputs the sEM. Then, the sEM is transmitted to the cooperation terminal 3.

As a result, the linked terminal 3 can interpret the content of the message based on the structured data included in the sEM by receiving the sEM. In the above example, in the prior art, the collaborative terminal 3 could not interpret the contents only by receiving the EM "Ku_Ogawa_Goal".

In the embodiment of the present invention, in the linked terminal 3, each of "砧", "stream", and "goal" represents "the team to which the action subject belongs", "the name of the action subject (human)", and "action". Receive an sEM containing the structured data shown. That is, the linked terminal 3 can interpret the content based on the structured data included in the sEM, and can realize a service linked to the content of the content. In this case, since the structured data is predetermined, the developer of the application of the linked terminal 3 can perform the development based on the structured data in advance.

In other words, by using the contents of the EM as structured data, a third party other than the sender of the EM interprets the meaning expressed by the EM and develops an application for the linked terminal 3 according to the contents of the scene. Is possible.

Further, in the embodiment of the present invention, the content receiving device 2 replaces the content of the pd element of the EM with the structured data to generate the sEM. This can solve the problem of the amount of data (within 244 bytes) of the EM pd element limited by the terrestrial digital television broadcasting operation regulations. That is, the broadcast transmission device 1 can transmit the EM with the data amount of the pd element of the EM within 244 bytes in accordance with the terrestrial digital television broadcasting operation regulations.

Therefore, when realizing a service linked with the content of the content, it is possible to generate structured data reflecting the content of the EM so that the linked terminal can interpret the content of the EM.

Further, in the embodiment of the present invention, the content receiving device 2 stores the sEM definition file f necessary for acquiring the structured data in the cache unit 45 or the storage unit 46 in advance. As a result, the content receiving device 2 does not need to access the sEM server 4 in order to acquire the sEM definition file f each time the EM is received. Therefore, since the momentary access to the sEM server 4 is not concentrated, the load on the sEM server 4 can be reduced.

[Other examples of the entire system]
Next, another example of the whole system that realizes the service linked with the content will be described. FIG. 16 is a diagram illustrating an outline of a service example of another overall system including a content receiving device according to an embodiment of the present invention.

This system includes a content distribution server 9, a content receiving device 2', a linked terminal 3, an sEM server 4, a receiving device service server 5, and a linked terminal service server 6. The content receiving device 2'is connected to the content distribution server 9, the sEM server 4, and the receiving device service server 5 via the Internet 8. The linked terminal service server 6 and the linked terminal 3 are connected to each other via the Internet 8 as in FIG. 1. Further, the content receiving device 2'and the cooperation terminal 3 are connected to each other via the communication path 7 as in FIG.

Comparing the system shown in FIG. 1 with the system shown in FIG. 16, both systems are common in that they include a cooperation terminal 3, an sEM server 4, a receiving device service server 5, and a cooperation terminal service server 6. On the other hand, the system of FIG. 16 includes a content distribution server 9 and a content reception device 2'instead of the broadcast transmission device 1 and the content reception device 2 of FIG. 1, and the content reception device 2'and the content distribution server 9 connect to the Internet 8. It differs from the system shown in FIG. 1 in that it is connected via.

In FIG. 16, the parts common to FIG. 1 are designated by the same reference numerals as those in FIG. 1, and detailed description thereof will be omitted.

The content distribution server 9 transmits a packet of content (including EM) such as a moving image to the content receiving device 2'via the Internet 8.

The content receiving device 2'is a terminal such as a smartphone, receives a packet transmitted from the content distribution server 9, performs the same processing as the content receiving device 2 shown in FIG. 1, and transmits an sEM to the linked terminal 3. do. In the configuration shown in FIG. 6, the content receiving device 2'provides a receiving unit for receiving a packet instead of the broadcast receiving unit 27.

The content distribution server 9 may transmit the content such as a moving image by the MPEG-DASH method or the HLS method protocol. In the case of the MPEG-DASH method, the Event metadata of the EventStream tag is used as a function corresponding to EM. Further, in the case of the HLS method, the metadata of TimedMetaData is used as a function corresponding to EM.

As described above, according to the content receiving device 2'of the embodiment of the present invention, the same effect as that of the content receiving device 2 shown in FIG. 1 is obtained.

Although the present invention has been described above with reference to embodiments, the present invention is not limited to the above-described embodiment and can be variously modified without departing from the technical idea. In the above-described embodiment, the content receiving device 2 is provided with the respective components shown in FIGS. 4 and 6, but the configuration of the content receiving device 2 is not limited to this. For example, as shown in FIG. 4, the content receiving device 2 is provided with the EM / sEM conversion function unit 26 in the resident 22, but the EM / sEM conversion function unit 26 may be implemented as an application.

Further, in the content receiving device 2, the EM / sEM conversion function unit 26 provided in the resident 22 generates an sEM by replacing the content of the pd element of the EM with structured data, and passes the sEM to the browser. On the other hand, the content receiving device 2 implements the EM / sEM conversion function unit 26 as a browser, and the browser acquires the pd element from the EM, acquires the structured data corresponding to the pd element, and acquires the pd element of the EM. The sEM may be generated by replacing the contents of the above with structured data.

Further, the EM and the sEM definition files f are not limited to the description examples 1 to 3 shown in FIGS. 10 to 15. For example, if the amount of structured data is small (within 244 bytes), or if there is no limit to the amount of EM data, the structured data may be written directly in the EM.

As the hardware configuration of the content receiving device 2 according to the embodiment of the present invention, a normal computer can be used. The content receiving device 2 is composed of a computer provided with a volatile storage medium such as a CPU and RAM, a non-volatile storage medium such as a ROM, and an interface.

Resident 22'(EM / sEM conversion function unit 26, broadcast reception unit 27, separation unit 28, broadcast communication cooperation unit 29 and terminal cooperation unit 32), application execution unit 30 and HTML application 31 provided in the content receiving device 2. The functions are realized by causing the CPU to execute a program describing these functions.

These programs are stored in the storage medium, read by the CPU, and executed. In addition, these programs can be stored and distributed in storage media such as magnetic disks (floppy (registered trademark) disks, hard disks, etc.), optical disks (CD-ROM, DVD, etc.), semiconductor memories, etc., and can be distributed via a network. You can also send and receive.

1 Broadcast transmission device 2, 2'Content reception device 3 Linked terminal 4 sEM server 5 Receiver service server 6 Linked terminal service server 7 Communication path 8 Internet 9 Content distribution server 20, 50 Hardware 21, 51 OS
22, 22'Resident 23 Application execution function unit 24 Receiver function unit 25 Terminal cooperation function unit 26 EM / sEM conversion function unit 27 Broadcast reception unit 28 Separation unit 29 Broadcast communication cooperation unit 30 Application execution unit 31 HTML application 32 Terminal cooperation unit 40 EM extraction unit 41 sEM judgment unit 42 Structured data acquisition unit 43 External resource acquisition unit 44 Storage management unit 45 Cache unit 46 Storage unit 47 sEM generation unit 52 Native application execution function unit 53 Linked application

Claims (8)

In a content receiving device that receives a content signal by broadcasting or communication and sends a message to a terminal to realize a service linked to the content.
An sEM (semantic event) that acquires a definition file based on the EM (event message) included in the signal of the content, acquires structured data based on the EM and the definition file, and includes the structured data. Equipped with an EM / sEM conversion function unit that generates a message)
The element information including the acquisition destination of the definition file is described in the EM.
The definition file defines a function for acquiring the structured data.
In the structured data, each data constituting the message and the meaning of the data are structurally defined.
The EM / sEM conversion function unit
An EM extraction unit that extracts the EM from the signal of the content,
Structured data acquisition that acquires the definition file from the acquisition destination described in the EM extracted by the EM extraction unit, executes the function defined in the definition file, and acquires the structured data. Department and
The sEM generation unit that replaces the element information described in the EM extracted by the EM extraction unit with the structured data acquired by the structured data acquisition unit and generates the sEM including the structured data. And with
A content receiving device characterized in that the sEM generated by the sEM generation unit is transmitted to the terminal. In the content receiving device according to claim 1,
The element information of the EM includes a conversion identifier indicating whether or not the EM can be converted to the sEM.
When the conversion identifier indicates that the EM can be converted to the sEM, the EM describes the element information including the acquisition destination of the definition file in addition to the conversion identifier.
When the conversion identifier indicates that the EM cannot be converted to the sEM, the EM describes the element information including the conversion identifier.
The EM / sEM conversion function unit further
A sEM determination unit for determining whether or not the EM can be converted to the sEM based on the conversion identifier described in the EM extracted by the EM extraction unit is provided.
The structured data acquisition unit is
When it is determined by the sEM determination unit that conversion is possible, the definition file is acquired from the acquisition destination described in the EM, and the function defined in the definition file is executed to obtain the structured data. Acquired,
The sEM generation unit
When it is determined by the sEM determination unit that conversion is possible, the element information described in the EM is replaced with the structured data, and the sEM is generated and output.
When it is determined by the sEM determination unit that conversion is not possible, the EM extracted by the EM extraction unit is output.
The content receiving device is a content receiving device characterized in that the sEM or the EM output by the sEM generation unit is transmitted to the terminal. In the content receiving device according to claim 2,
When the conversion identifier of the EM indicates that the EM can be converted to the sEM, the EM describes the conversion identifier and the element information including the acquisition destination of the definition file. ,
When the conversion identifier of the EM indicates that the EM cannot be converted to the sEM, the EM describes the element information consisting of the conversion identifier and the character string.
When the conversion identifier is not described in the EM, the element information consisting of a character string is described in the EM.
The sEM determination unit
When the conversion identifier described in the EM extracted by the EM extraction unit indicates that the EM can be converted into the sEM, it is determined that the conversion is possible, and the conversion identifier is the EM. Is not convertible to the sEM, or if the conversion identifier is not described in the EM extracted by the EM extraction unit, it is determined that the conversion is not possible. Device. The content receiving device according to any one of claims 1 to 3.
Information indicating an external server or an internal storage unit and an address of the external server are described in the acquisition destination included in the element information of the EM.
The structured data acquisition unit is
When the acquisition destination described in the EM indicates the external server, the definition file is acquired based on the address of the external server, and when the acquisition destination indicates the internal storage unit, the content receiving device is used. A content receiving device characterized in that the definition file is acquired from the internal storage unit provided. In the content receiving device according to claim 4,
The structured data acquisition unit is
When the acquisition destination described in the EM indicates the internal storage unit and the definition file is not stored in the internal storage unit, the definition file is acquired based on the address of the external server and the definition file is acquired. A content receiving device characterized in that a definition file is stored in the internal storage unit. In the content receiving device according to any one of claims 1 to 5.
In the EM, element information including an index for selecting one from a plurality of structured data is further described.
Further, the plurality of structured data are defined in the definition file.
The structured data acquisition unit is
The definition file is acquired from the acquisition destination described in the EM, the function defined in the definition file is executed, and the definition file is defined based on the index described in the EM. A content receiving device characterized in that the structured data is acquired by selecting one from a plurality of structured data. In the content receiving device according to any one of claims 1 to 5.
The EM further describes element information including an index for selecting each of the data constituting the message transmitted to the terminal from a plurality of elements.
The definition file further defines variables of the data that make up the message, and a plurality of elements corresponding to the variables.
The structured data acquisition unit is
The definition file is acquired from the acquisition destination described in the EM, the function defined in the definition file is executed, and each of the definitions is defined in the definition file based on the index described in the EM. A content receiving device, characterized in that the structured data is acquired by selecting one from the plurality of elements corresponding to the variable. A program for causing a computer to function as the content receiving device according to any one of claims 1 to 7.

Images