Receiving device, system, and program

Abstract

To provide a receiver capable of appropriately controlling effects caused by delivered event information.SOLUTION: A receiver includes a content reception part, a content presentation part, an event information acquisition part, an event notification control part, and an event presentation part. The content reception part receives content. The content presentation part presents the contend having been received. The event information acquisition part acquires event information and an event presentation condition which are related to the content. The event notification control part determines the event presentation condition, thereby controlling whether the event information is presented. The event presentation part presents the event information only when the event notification control part determines to present the event information.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a receiving device, a system, and a program. [Background technology]

[0002] Using existing technology, it is now possible to provide metadata in conjunction with the distribution of video and audio content. Such content can be distributed either by broadcast or by communication (e.g., the Internet). Event messages that describe the details of an event can be provided as a type of metadata. In broadcasting, event messages are used, for example, in television quiz shows. In addition, the MTE (Media Timed Event) system has been established as a system for providing event messages in conjunction with video content distributed over the Internet.

[0003] By providing event messages as a type of metadata, various services can be realized in a form linked to content. For example, information such as the location of an upcoming event can be provided as an event message in conjunction with content introducing the contents of an exhibition or the like. Also, information on the location and business hours of restaurants and other establishments can be provided as an event message in conjunction with content referencing restaurants and other establishments. Furthermore, information related to event tourism (how to enjoy visiting drama filming locations and anime settings) can be provided as an event message in conjunction with the distribution of video content. In addition, various other information related to content can be provided as an event message.

[0004] Patent Document 1 discloses a technology for an information providing method and system. In the technology of Patent Document 1, widely distributed coupon information is associated with a broadcast program. By using this system, it is possible to identify a broadcast program based on the coupon information. There is also a mechanism in place where the coupon becomes valid when a user watches the broadcast program. In other words, only users who watch the broadcast program can enjoy the value of the coupon. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2015-187838 Summary of the Invention [Problem to be solved by the invention]

[0006] The above-mentioned conventional technologies have the following problems. Whether broadcasting or communication, content can be distributed simultaneously to an unspecified number of users. However, physical stores, tourist facilities, and the like have a limit to the number of visitors they can accommodate or handle at one time. Furthermore, when services are provided via communication via the Internet, the number of users that can be handled at one time is limited, depending on factors such as the size of the web server device. In either case, there is an appropriate number of people that can be handled at one time (per unit of time). However, conventional technologies have no mechanism for controlling the distribution of event messages in accordance with the number of people that can be handled. As a result, if event messages are distributed simultaneously to an unspecified number of users, confusion or congestion may occur in the stores, facilities, equipment, etc. that are hosting the messages.

[0007] The present invention has been made in consideration of the above circumstances, and aims to provide a receiving device, system, and program that enable appropriate control of the quantitative scale of the impact caused by the provision of event information (event messages). [Means for solving the problem]

[0008] [1] In order to solve the above problem, a receiving device according to one aspect of the present invention includes a content receiving unit that receives content, a content presenting unit that presents the received content, an event information acquiring unit that acquires event information and event presentation conditions related to the content, an event notification control unit that determines the event presentation conditions to control whether or not to present the event information, and an event presentation unit that presents the event information only when the event notification control unit determines that the event information should be presented.

[0009] [2] Furthermore, one aspect of the present invention is that the receiving device further includes an event notification history management unit that manages a history indicating that the event presentation unit has presented the event information as an event notification history and transmits the event notification history to an external device.

[0010] [3] Furthermore, one aspect of the present invention is that, in the above-mentioned receiving device, the event notification history includes information on user behavior corresponding to the event presentation unit presenting the event information.

[0011] [4] In one aspect of the present invention, in the receiving device, the event presentation condition includes a condition regarding a start time of a time period during which the event information can be presented.

[0012] [5] In one aspect of the present invention, in the receiving device, the event presentation condition further includes a condition regarding an end time of a time period during which the event information can be presented.

[0013] [6] In one aspect of the present invention, in the receiving device, the event presentation condition includes a condition regarding an event presentation ratio that indicates a ratio at which the event information is presented.

[0014] [7] In addition, according to one aspect of the present invention, in the receiving device, the event presentation condition includes a condition relating to a location where the receiving device is located.

[0015] [8] Furthermore, one aspect of the present invention is that the above-mentioned receiving device further comprises a viewing history memory unit that stores a viewing history representing a history of the content presented by the content presentation unit, and the event presentation condition includes a condition as to whether a viewing history of a specific content is stored in the viewing history memory unit.

[0016] [9] Furthermore, in one aspect of the present invention, in the above-mentioned receiving device, the event notification control unit repeatedly determines the event presentation conditions, and when a predetermined presentation termination condition is satisfied, the event notification control unit terminates the repeated determination of the event presentation conditions and terminates control of whether or not to present the event information, and the presentation termination condition includes either completion of presentation of the event a predetermined number of times or completion of presentation of the content by the content presentation unit.

[0017]

[10] Another aspect of the present invention is a system including a receiving device and a distribution device, wherein the receiving device includes a content receiving unit that receives content, a content presentation unit that presents the received content, an event information acquisition unit that acquires event information and event presentation conditions related to the content, an event notification control unit that determines the event presentation conditions to control whether or not to present the event information, and an event presentation unit that presents the event information only when the event notification control unit determines that the event information should be presented, and the distribution device distributes the content, the event information, and the event presentation conditions to the receiving device.

[0018]

[11] Another aspect of the present invention is a program that causes a computer to function as a receiving device that includes a content receiving unit that receives content, a content presenting unit that presents the received content, an event information acquiring unit that acquires event information and event presentation conditions related to the content, an event notification control unit that determines the event presentation conditions to control whether or not to present the event information, and an event presenting unit that presents the event information only when the event notification control unit determines that the event information should be presented. [Effects of the Invention]

[0019] According to the present invention, the event notification control unit in the receiving device determines whether to present event information by determining the event presentation conditions. That is, according to the present invention, it is possible to appropriately set the event presentation conditions and appropriately control the quantitative scale of the impact caused by the provision of event information. [Brief explanation of the drawings]

[0020] [Figure 1] 1 is a block diagram showing a schematic functional configuration of a receiving device according to an embodiment of the present invention. [Figure 2]FIG. 2 is a block diagram showing a schematic functional configuration of a distribution device according to the embodiment. [Figure 3] 2 is a block diagram showing a schematic configuration of a system including a receiving device and a distribution device according to the embodiment. FIG. [Figure 4] FIG. 2 is a processing sequence diagram showing the operation procedure of the system according to the embodiment. [Figure 5] FIG. 10 is a schematic diagram showing an example of the configuration of metadata for implementing a first presentation condition determination example in the system according to the embodiment. [Figure 6] FIG. 10 is a schematic diagram showing an example of the configuration of metadata for implementing a second presentation condition determination example in the system according to the embodiment. [Figure 7] FIG. 10 is a schematic diagram showing an example of the configuration of metadata for implementing a third presentation condition determination example in the system according to the embodiment. [Figure 8] FIG. 11 is a schematic diagram showing an example (1 / 2) of the configuration of metadata for implementing a fourth presentation condition determination example in the system according to the embodiment. [Figure 9] FIG. 11 is a schematic diagram showing an example (2 / 2) of the configuration of metadata for implementing a fourth presentation condition determination example in the system according to the embodiment. [Figure 10] FIG. 2 is a block diagram showing an example of the internal configuration of each device constituting the system according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0021] Next, an embodiment of the present invention will be described with reference to the drawings. In this embodiment, a distribution device provides metadata when distributing content. A receiving device receives the content data and metadata. The metadata includes event information and event presentation conditions. The event information may be data in the form of a standardized MTE (Media Timed Event).

[0022] The receiving device presents an event to a user in accordance with the event presentation condition. The event presentation condition is a condition whose truth value changes at different times for each user. In other words, instead of multiple receiving devices presenting an event to users all at once, each receiving device presents the event to the user when the event presentation condition becomes true. In other words, this system can stagger the timing of presenting an event to each user. This makes it possible to control the number of users to whom an event is presented at a given time.

[0023] The event presentation condition depends on the user's content viewing history, place of residence (receiving location), and other factors. The event presentation condition may also be determined to be true or false depending on a random factor (e.g., a pseudo-random number). The distribution device can estimate the number of users whose behavior will change as a result of the issuance of an event and provide metadata (event information and event presentation condition).

[0024] After presenting an event, the receiving device transmits event notification history information to the distribution device. The event notification history includes information identifying the event and information on the timing at which each receiving device presented the event to the user. Furthermore, the event notification history may include information on the user's behavior after the event was presented on the distribution device. The information on the user's behavior may include information such as whether the user clicked on the information presented on the receiving device, what operations the user performed on the receiving device, and whether the user visited a specific location. Note that information on the locations visited by the user can be obtained, for example, using the GPS function of the receiving device. GPS stands for Global Positioning System.

[0025] FIG. 1 is a block diagram showing a schematic functional configuration of a receiving device according to this embodiment. As shown in the figure, the receiving device 1 includes an instruction unit 11, a content receiving unit 21, a content presenting unit 22, an event information acquiring unit 31, an event information storage unit 32, an event notification control unit 33, a user information storage unit 34, an event presenting unit 35, and an event notification history management unit 36. Each of these functional units can be realized, for example, by a computer and a program. Each functional unit also includes a storage unit as needed. The storage unit is, for example, a memory for storing program variables or allocated by program execution. Non-volatile storage units such as a magnetic hard disk drive or a solid-state drive (SSD) may also be used as needed. At least some of the functions of each functional unit may be realized as a dedicated electronic circuit rather than a program.

[0026] The receiving device 1 may be, for example, a television set for receiving broadcast signals. The receiving device 1 may also be a personal computer (PC), a tablet terminal, a smartphone, a wristwatch-type terminal device, or other types of terminal devices. The receiving device 1 can receive content data distributed by broadcast or communication. The receiving device 1 can receive event information (event messages) as metadata along with the content data. The receiving device 1 can also transmit data via communication to a distribution device 2, which will be described later. The functions of each part of the receiving device 1 are as follows:

[0027] The instruction unit 11 controls the operation of the receiving device 1 based on instructions from the user of the receiving device 1. For example, the instruction unit 11 controls the content receiving unit 21 to request the distribution device to view specified content based on instructions from the user. The instruction unit 11 may also control other operations based on instructions from the user. The instruction unit 11 accepts instructions by the user operating the screen or by voice input from the user.

[0028] The content receiving unit 21 receives content from the distribution device. For example, based on an instruction to view content from the instruction unit 11, the content receiving unit 21 requests the distribution device to distribute predetermined content and receives the content from the distribution device. Alternatively, the content receiving unit 21 may receive content distributed as a broadcast signal by selecting a specific broadcast service based on an instruction from the instruction unit 11. The content receiving unit 21 passes the received content (data including video and audio) to the content presenting unit 22.

[0029] If the content data includes metadata, the content receiving unit 21 passes the metadata to the event information acquiring unit 31. The metadata includes event information.

[0030] The content presenting unit 22 presents to the user the content received by and passed from the content receiving unit 21. Specifically, the content presenting unit 22 displays the video included in the content on a screen or the like, and outputs the audio included in the content from a speaker or the like. The content presenting unit 22 may retain information identifying the presented content and information on the date and time the content was presented as user viewing history information. The content presenting unit 22 may write this user viewing history information to a user information storage unit 34, which will be described later.

[0031] The event information acquisition unit 31 acquires metadata related to content received by the content receiving unit 21. The event information acquisition unit 31 may acquire this metadata from the content receiving unit 21. Alternatively, the event information acquisition unit 31 may identify the content being received by the content receiving unit 21 and acquire metadata related to the content directly from the distribution device. The metadata acquired by the event information acquisition unit 31 includes event information and event presentation conditions. In other words, the event information acquisition unit 31 acquires event information and event presentation conditions related to the content from the distribution device.

[0032] When the metadata is embedded in the content (in-band method), the event information acquisition unit 31 acquires the above metadata from the content receiving unit 21. When the metadata is not embedded in the content but is provided from a distribution device (out-of-band method), the event information acquisition unit 31 acquires the metadata directly from an external distribution device rather than from the content receiving unit 21.

[0033] The event information storage unit 32 stores the metadata acquired by the event information acquisition unit 31. As described above, the metadata includes event information and event presentation conditions. This information stored in the event information storage unit 32 is read by the event notification control unit 33.

[0034] The event notification control unit 33 controls the timing of presenting event information based on the event presentation conditions stored in the event information storage unit 32. In other words, the event notification control unit 33 determines whether the event presentation condition is met and thereby controls whether or not the event presentation unit 35 presents the event information at that time. That is, the event notification control unit 33 controls whether or not to present the event information. When an event should be presented according to the event presentation condition, the event notification control unit 33 passes the event information read from the event information storage unit 32 to the event presentation unit 35.

[0035] The event notification control unit 33 may read user information from the user information storage unit 34 to determine whether or not to present event information. In other words, if the truth value of the event presentation condition depends on the user information, the event notification control unit 33 controls the presentation of the event based on the read user information. In this case, the user information read by the event notification control unit 33 may include the user's content viewing history, location information of the receiving device 1 itself, and the like.

[0036] The user information storage unit 34 stores information about the user of the receiving device 1. The information stored in the user information storage unit 34 may include location information about the receiving device 1 and information about the content viewing history of the user of the receiving device 1. The location information about the receiving device 1 is determined, for example, by a GPS function of the receiving device 1. Alternatively, the location information about the receiving device 1 may be based on information identifying a base station of a wireless communication network accessed by the receiving device 1. The content viewing history information may be automatically accumulated when the receiving device 1 receives and presents content from a distribution device. The user information storage unit 34 may store information input by the user as other information about the user. The user information storage unit 34 may manage and store information about multiple users separately.

[0037] The event presentation unit 35 is controlled by the event notification control unit 33 and presents event information to the user. In other words, the event presentation unit 35 presents an event based on the result of the event notification control unit 33 determining whether it is the timing to present the event. That is, the event presentation unit 35 presents the event information only when the event notification control unit 33 determines that the event information should be presented. The event presentation unit 35 presents the event, for example, by displaying information in the form of text or images on a screen or the like. The event presentation unit 35 may also display clickable link information on a screen or the like. When the user clicks on the link information, the event presentation unit 35 can obtain and display more detailed event information via a communication network.

[0038] The event presentation unit 35 can also acquire information on the user's actions after the event is presented. The user's actions here include obtaining other content by clicking on predetermined link information. The user's actions also include moving to a predetermined location (for example, a location (store, facility, etc.) guided by the presented event) while carrying the receiving device 1. The user's location change can be detected, for example, by the GPS function of the receiving device 1.

[0039] The event presentation unit 35 passes history information related to the presentation of the event to the event notification history management unit 36. The history information here includes information that uniquely identifies the presented event (for example, an event ID, which will be described later), information on the date and time when the event was presented, and information on the user's actions after the event was presented.

[0040] The event notification history management unit 36 ​​acquires the user's viewing history of the event information and the user's behavior history after the event is presented, and feeds this information back to the distribution device as an event notification history. The information that the event notification history management unit 36 ​​feeds back to the distribution device includes information passed to the event notification history management unit 36 ​​from the event presentation unit 35. In other words, the event notification history management unit 36 ​​manages, as an event notification history, a history indicating that the event presentation unit 35 has presented the event information, and transmits this event notification history to an external distribution device. The event notification history may include information about the user's behavior in response to the event presentation unit 35 presenting the event information.

[0041] As described above, the receiving device 1 receives event information and data on its presentation conditions from the distribution device. The receiving device 1 controls the presentation of events based on the presentation conditions received from the distribution device. Furthermore, the receiving device 1 transmits data on the history of event presentation to the distribution device.

[0042] FIG. 2 is a block diagram showing a schematic functional configuration of a distribution device according to this embodiment. As shown in the figure, the distribution device 2 includes an event issuance management unit 51, a content distribution unit 52, an event information transmission unit 53, and an event issuance history acquisition unit 54. At least some of the functions of the distribution device 2 can be realized, for example, by a computer and a program. Each functional unit also has a storage unit as necessary. At least some of the functions of each functional unit may be realized as a dedicated electronic circuit rather than a program.

[0043] As a typical configuration example, the distribution device 2 may be a device that distributes content by broadcast signals. As another configuration example, the distribution device 2 may be a device that distributes content using IP (Internet Protocol) via a communication line such as the Internet. The distribution device 2 can also receive event issuance history data via a communication line from the receiving device 1 that receives the content. The functions of each part of the distribution device 2 are as follows.

[0044] The event issuance management unit 51 manages content received from the content supply device 3. The event issuance management unit 51 generates metadata including event information and event presentation conditions, and passes the metadata to the event information transmission unit 53. The event issuance management unit 51 also receives event issuance history data from the event issuance history acquisition unit 54. The event issuance history data is feedback information related to event issuance transmitted from the event notification history management unit 36 ​​on the receiving device 1 side. The event issuance history data includes information identifying the event, information individually identifying the receiving device 1 to which the event was presented, information on the date and time the event was presented, information on user behavior after the event was presented, and the like. The event issuance management unit 51 may adjust subsequent event presentation conditions based on the received event issuance history. This allows the distribution device 2 to control the number of receiving devices 1 to simultaneously present an event, the distribution of user attributes (viewing history, location, etc.), and the like.

[0045] The content distribution unit 52 distributes content (video and audio) to the receiving device 1. When providing metadata using the in-band method described above, the content distribution unit 52 embeds the metadata received from the event information transmission unit 53 in the content and distributes it to the receiving device 1. Note that the content distribution unit 52 may distribute the content by broadcasting, or may distribute the content by communication via the Internet or the like.

[0046] The event information transmission unit 53 transmits metadata including the event information and the event presentation conditions. When the metadata is transmitted in-band, the event information transmission unit 53 passes the metadata to the content distribution unit 52. When the metadata is transmitted out-band, the event information transmission unit 53 transmits the metadata directly to the receiving device 1 without passing it to the content distribution unit 52.

[0047] The event issuance history acquisition unit 54 receives the event issuance history from the receiving device 1. The contents of the event issuance history are as already explained. The event issuance history acquisition unit 54 passes the event issuance history from the receiving device 1 to the event issuance management unit 51. In other words, the presentation status of the events issued by the event issuance management unit 51 and the like are fed back to the event issuance management unit 51.

[0048] A content supply device 3 in the figure supplies content and related data to the distribution device 2.

[0049] 3 is a block diagram showing a schematic functional configuration of a system according to this embodiment. As shown in the figure, the system 7 includes a receiving device 1, a distribution device 2, and a content supply device 3. The functional configurations of the receiving device 1, the distribution device 2, and the content supply device 3 have already been described. The system 7 may be configured to include multiple receiving devices 1. The system 7 may also include one or more distribution devices 2 and one or more content supply devices 3.

[0050] The content supply device 3 is a device operated by, for example, a content creator or provider. The content supply device 3 supplies content to the distribution device 2. The distribution device 2 is a device operated by a broadcasting company, an Internet content distribution company, or the like. The distribution device 2 distributes content to the receiving device 1 via broadcasting or communication. The distribution device 2 also provides metadata including event information and event presentation conditions to the receiving device 1. The receiving device 1 is used by a user. The user uses the receiving device 1 to view content. The receiving device 1 also presents events to the user. The receiving device 1 feeds back the above-mentioned event issuance history information to the distribution device 2.

[0051] 4 is a sequence diagram showing the operation procedure of the system 7. Here, the operation procedure of this embodiment will be described along the flow shown in the diagram.

[0052] In process P1, the content supply device 3 passes content to the distribution device 2. At this time, the content supply device 3 may pass event information and event presentation condition information related to the content. The distribution device 2 receives this content data, etc. The distribution device 2 is now ready to distribute the content to the receiving device 1. The distribution device 2 also determines the event presentation conditions based on the information passed from the content supply device 3 or based on its own unique processing.

[0053] Next, in process P2, the receiving device 1 requests playback of the content. If the content is distributed via communication, the receiving device 1 requests distribution of specific content from the distribution device 2. If the content is distributed via broadcasting, the receiving device 1 tunes in to a specific broadcasting service to receive the content.

[0054] In process P3, the distribution device 2 distributes content to the receiving device 1. The content is, for example, video and audio content. The distribution device 2 can also provide metadata related to the content to the receiving device 1. The metadata may include event information and event presentation conditions. The event information may include events that are presented based on presentation conditions and events that are presented without presentation conditions. The receiving device 1 receives the content and related data.

[0055] In process P4, the receiving device 1 presents the content received in process P3. Specifically, the receiving device 1 displays video on the screen and outputs audio to speakers or the like (including earphones or the like). Furthermore, for event information without presentation conditions, the receiving device 1 presents it at an appropriate timing and by an appropriate means. Process P4 outputs video and audio, and is performed continuously for a predetermined period of time. In parallel with process P4, the receiving device 1 executes a loop of process P5 described below.

[0056] In process P5, the receiving device 1 repeats processes P6 and P7 described below. If the loop break condition in process P10 is satisfied, the receiving device 1 exits the loop of process P5.

[0057] In process P6 in the loop of process P5, the receiving device 1 determines the presentation conditions of the event. The presentation conditions of the event are those that the receiving device 1 has already received in the above process P3.

[0058] In process P7 in the loop of process P5, the receiving device 1 performs processing according to the result of the presentation condition determination in process P6. Specifically, if the presentation condition is met (determination: true), processes P8 and P9 are executed. Otherwise, that is, if the presentation condition is not met (determination: false), process P7 ends without performing any particular processing. In either case, after process P7 ends, the process proceeds to process P10.

[0059] In the above process P8 (first process when the presentation condition is true), the event presentation unit 35 of the receiving device 1 presents the metadata (event information) with the presentation condition. Specifically, the receiving device 1 presents the event information to the user by, for example, displaying it on a screen. This allows the user to recognize the presented event.

[0060] Next, in the above-mentioned process P9 (second process when the presentation condition is true), the event notification history management unit 36 ​​of the receiving device 1 saves the record of the event presentation in the above-mentioned process P8 as history information. The event presentation history includes information indicating whether the event was presented to the user, information about the time of presentation, and information about the user's behavior in response to the presented event. Completion of this process P9 ends process P7.

[0061] When the above process P7 ends, in process P10 within the loop of process P5, the receiving device 1 determines the condition for breaking (exiting) the loop. Specifically, if the condition for ending presentation is true, in process P11, the event notification history management unit 36 ​​of the receiving device 1 transmits the metadata notification history (event notification history) that it has saved and accumulated to the distribution device 2, and exits the loop of process P5.

[0062] In the above process P10, if the condition for ending presentation is false, the loop of process P5 is repeated.

[0063] For example, if the event presentation condition determined in the above process P6 is set to "present an event between 7:00 PM and 7:30 PM on October 16th," the event presentation condition will become true when 7:00 PM arrives on that day and will remain true until 7:30 PM. Before 7:00 PM on that day or after 7:30 PM on that day, the event presentation condition will become false.

[0064] The condition for ending the event presentation determined in the above process P10 becomes true, for example, when the presentation has been made a predetermined number of times, when the predetermined presentation time range has ended, when the receiving device 1 is outside the area to be presented (including when it has moved outside the area to be presented), or when viewing of the content has ended.

[0065] That is, the event notification control unit 33 can repeatedly determine the event presentation conditions in a loop (the above-described process P5). Furthermore, when a predetermined presentation end condition is satisfied, the event notification control unit 33 exits the repeated determination of the event presentation conditions and ends the control of whether or not to present the event information (the break in the above-described process P10). The presentation end condition includes either that a predetermined number of events have been presented or that the content presenter 22 has ended the presentation of the content due to a change in the channel selection state, etc.

[0066] Next, several examples of determining whether an event presentation condition is met will be described.

[0067] [Example of first presentation condition judgment] In this example, a travel program distributed as a broadcast is assumed as an example of video content to be presented. The travel program introduces a specific, relatively small-scale event (such as a festival) in a local area. The event is held for a limited period of time, but because it is a small-scale event, it is undesirable for a large number of people to visit the event location at once by introducing it in a broadcast program. Therefore, the event presentation conditions are set so that at least some of the metadata information is presented only after the festival, etc. has ended.

[0068] Specifically, for example, presentation conditions are not set for information among metadata that aims to promote understanding of a program (for example, historical information about the local area, subtitle information for the program, etc.). Such information can be presented immediately after the receiving device 1 receives the metadata while the user is watching the content. On the other hand, presentation conditions are set for information that has the effect of encouraging a visit to the local area (for example, route information to the local area, transportation information, URLs of web pages for booking tourist facilities and accommodations, etc.), so that the information is presented only after a specified date and time. Such information is not presented to the user immediately after the receiving device 1 receives the metadata, but is presented only after the specified date and time has arrived.

[0069] By setting the presentation conditions as described above, it is possible to provide information that will help users who view the content to deepen their understanding, while suppressing the concentration of visitors to festivals, etc. The receiving device 1 notifies the distribution device 2 of the event presentation history information.

[0070] The mechanism described in this example can also be used, for example, to promote tourist visits to a specific region by suppressing visits during a specific peak season and increasing the promotion effect during off-peak seasons. In other words, the receiving device 1 can be controlled so that it displays event information only when the off-season arrives. This makes it possible to promote tourism in the region throughout the year while suppressing peaks. In other words, it is possible to suppress the phenomenon known as tourist pollution or overtourism.

[0071] 5 is a schematic diagram showing an example of the configuration of metadata for implementing the first presentation condition determination example. As shown in the figure, the metadata can be expressed in JSON format (JavaScript Object Notation) or a format equivalent thereto. In the figure, eventId is data representing an event identifier, condition is data representing a presentation condition, and eventObject is data representing the entity of the event object.

[0072] The event identifier is information for uniquely identifying event information distributed from the distribution device 2. In the illustrated example, the event identifier is "12345678."

[0073] The presentation condition is a condition for presenting an event. As already explained, the event notification control unit 33 of the receiving device 1 determines whether or not the event should be presented to the user at the current timing by evaluating this presentation condition. In the illustrated example, the event presentation condition is "availableStartTime:20210901T100000+0900". This event presentation condition specifies the time (date and time) at which presentation of the event information can begin. Here, the time is expressed in the format "YYYYMMDDThhmmss±zzzz". "YYYYMMDD" corresponds to the year, month, and day in the Gregorian calendar (in this example, September 1, 2021). "T" is a fixed symbol separating the year, month, and day from the hour, minute, and second. "hhmmss" corresponds to the hour, minute, and second in 24-hour notation (in this example, 10:00:00). "±zzzz" represents the time zone, and in this example "+0900" represents the time zone 9 hours ahead of Coordinated Universal Time (UTC) (for example, Japan Standard Time).

[0074] The entity of an event object can be represented as a set of pairs of key information and value information. In the example shown, key1, key2, and key3 are key information, and value1, value2, and value3 are value information corresponding to the key information, respectively. The entity of an event object may be, for example, historical information about a region, subtitle information corresponding to the content of a program, route information for visiting a specific region, or other information.

[0075] In the data illustrated in FIG. 5, only the presentable start time is specified as the event presentation condition, and no presentable end time is specified. In such a case, the loop can be exited only by determining the break condition (process P10 in FIG. 4) in the presentation processing loop (process P5 in FIG. 4). The break condition may be, for example, "exit the loop once the event information has been presented to the user," or "exit the loop once the service (channel) selected by the receiving device 1 is changed."

[0076] [Second example of presentation condition judgment] In the above "First Presentation Condition Determination Example," it was assumed that the same event presentation conditions were distributed to all destination receiving devices 1. In this example (Second Presentation Condition Determination Example), the distribution device 2 provides event presentation conditions that are not necessarily the same for all users (all receiving devices 1).

[0077] For example, it is assumed that in content (entertainment content as an example) that is distributed simultaneously to all users via broadcasting or communication, transition information (such as a URL) for accessing a website is provided as event information. Content distributors want many users (viewers) to access their websites, but may want to distribute access as much as possible over time, taking into account factors such as the access load on the web server. Therefore, the presentation conditions are varied so that the timing of presenting event information varies for each user (each receiving device 1). Each receiving device 1 that receives the metadata presents the event to users based on the presentation conditions received by that device. This makes it possible to control the distribution of access to the website so that it is nearly uniform (or close to it) throughout the entire content distribution time period, rather than concentrating access to the website at a specific point during the content distribution time period.

[0078] For example, the distribution device 2 can set the event presentation conditions so that the timing of event presentation is dispersed among, for example, the beginning, middle, and end of a program. Alternatively, the distribution device 2 can set the event presentation conditions so that the timing of event presentation is dispersed depending on the development of other programs. Furthermore, the distribution device 2 may refer to feedback information on the presentation history from the receiving device 1 and reflect the analysis results of the history in the event presentation conditions. For example, the event presentation conditions may be changed depending on the number of responses or response rate to the event information calculated from the feedback information.

[0079] Furthermore, in the case of broadcasts (e.g., nationwide broadcasts) spanning multiple regions (multiple broadcast stations), different event presentation conditions may be set for each broadcast station (e.g., Tokyo, Nagoya, Osaka, Fukuoka, etc.). In other words, the event presentation time period can be different for each broadcast station. The event presentation time period is determined by the event presentation start time and event presentation end time included in the metadata. In broadcasts, event information is basically expected to be provided in-band, and it is relatively easy to distribute different metadata for each broadcast station in this way.

[0080] When the metadata is provided out-of-band, the distribution device 2 may provide metadata having different patterns of presentation conditions for each metadata request from a user, for example.

[0081] FIG. 6 is a schematic diagram showing an example of the configuration of metadata related to the implementation of the second presentation condition determination example. As in the example shown in FIG. 5, the metadata can be expressed in JSON format or the like. As in the example shown in FIG. 5, the metadata includes data for each item: eventId (event identifier), condition (presentation condition), and eventObject (event object entity). A feature of the data in FIG. 6 is that the condition (event presentation condition) specifies not only availableStartTime (presentable start time) but also availableEndTime (presentable end time). In the illustrated example, the presentable start time is "July 16, 2021, 10:00:00 (UTC+9)," and the presentable end time is "July 16, 2021, 10:30:00 (UTC+9)." According to the event presentation condition of this example, the receiving device 1 presents the event of this metadata only between 10:00 and 10:30 on the relevant day. During other time periods (before the presentable start time or after the presentable end time), the receiving device 1 does not present the event.

[0082] In the second presentation condition determination example described above, the distribution device 2 can specify different time periods as time periods during which the event can be presented to different users' receiving devices 1. This allows the system 7 to present event information to the receiving devices 1 in a distributed manner according to the times specified in the event presentation conditions, rather than concentrating the presentation of event information at a single time.

[0083] [Third presentation condition judgment example] In this example, the receiving device 1 makes a determination based on an event presentation condition that depends on the location of the receiving device. Also, in this example, the receiving device 1 presents an event with a probability according to a presentation ratio specified in the event presentation condition. Using the above mechanism, in this example, when distributing the content of a travel program, for example, the probability of presenting an event can be controlled according to the distance (distance) from a focused area (for example, an area where a festival introduced in the content is being held).

[0084] As an example, in areas near a focused area, the presentation rate of event information (such as route information to a location where a festival is being held) may be set to 10%. In areas at a medium distance from the focused area, the presentation rate of event information may be set to 50%. In areas at a long distance from the focused area, the presentation rate of event information may be set to 100%. Alternatively, conversely, the presentation rate may be set relatively high in areas close to the focused area and relatively low in areas far from the focused area.

[0085] The receiving device 1 determines whether to present an event to the user according to the presentation ratio specified as the event presentation condition. This allows control such as attracting more visitors from a desired area to a festival, for example. Furthermore, depending on how the presentation condition is set, it is also possible to control the event so that visitors from various dispersed areas are attracted, or visitors from a specific concentrated area or its neighboring areas are attracted.

[0086] Fig. 7 is a schematic diagram showing an example of the configuration of metadata related to the implementation of the third presentation condition determination example. As in the example shown in Fig. 5, the metadata can be expressed in JSON format or the like. As in the example shown in Fig. 5, the metadata includes data for each item: eventId (event identifier), condition (presentation condition), and eventObject (event object entity).

[0087] One of the features of the metadata shown in Fig. 7 is that in addition to these items, it also has data for a presentation rate item. The presentation rate indicates the presentation rate, and in the example shown here, the presentation rate is 100%. The numerical value of this presentation rate indicates the rate (probability) at which the receiving device 1, having received this metadata, will present the event information contained in the metadata to the user. The receiving device 1 presents the event information at a rate (probability) according to this presentation rate, based on random factors such as random numbers or pseudo-random numbers generated within the device.

[0088] Another feature of the metadata shown in FIG. 7 is that availableUserArea is specified as a presentation condition. availableUserArea specifies the area of ​​the user to whom the event can be presented. In the data of this example, a list of multiple areas is specified as the area where the user (receiving device 1) is located. In the data of FIG. 7, a list of area information is specified that includes an area where the areaId (area identifier) ​​is "12345678" and the areaName (area name) is "kinuta" (Kinuta), and an area where the areaId (area identifier) ​​is "12345679" and the areaName (area name) is "sakuragaoka" (Sakuragaoka).

[0089] 7, the receiving device 1 controls the presentation of events at a presentation rate according to presentationRate in the areas included in the list specified by availableUserArea. Note that the receiving device 1 can ascertain its own location using, for example, a GPS function or a function for identifying base stations in a wireless communication network. While FIG. 7 shows only data when the presentation rate is 100%, by providing presentation conditions in which the presentation rate is changed for each area, such as 50%, 30%, or 10%, it is possible to control the presentation of events at different presentation rates for each area.

[0090] [Example of fourth presentation condition judgment] In this example, event presentation is controlled based on the viewing history of the distributed content. As described above, the receiving device 1 stores the content viewing history. The receiving device 1 controls the presentation of events by referencing this viewing history. For example, the receiving device 1 stores information indicating whether the user of the receiving device 1 viewed each broadcast of a certain content series as the viewing history. Therefore, based on this viewing history, for example, core users of the series (important users who have a high degree of loyalty and contribution to the content by continuously viewing it) can be provided with beneficial information or information that improves the probability of winning a prize. Furthermore, for example, light users (users who view content relatively casually) can be provided with information that provides supplementary explanations of the content or information aimed at promoting the content.

[0091] Fig. 8 is a schematic diagram showing an example of the configuration of metadata related to the implementation of the fourth presentation condition determination example. Similar to the data example shown in Fig. 7, the metadata in Fig. 8 includes data for each item: eventId (event identifier), condition (presentation condition), presentationRate (presentation rate), and eventObject (event object entity).

[0092] A feature of the metadata shown in FIG. 8 is that a viewing history (userHistory) is specified as an event presentation condition (condition). This viewing history specifies a list of content identified by a content identifier (contentId) or the like. Note that content identifiers exemplified in FIG. 8 are "12345678" and "12345679." Additionally, the metadata shown in FIG. 8 specifies "10%" as a presentation rate (presentationRate). In other words, this metadata indicates that the content presentation condition is determined so that the presentation rate (probability) is 10% for a receiving device 1 having a viewing history of content represented by a content identifier such as "12345678" or "12345679." Note that the meaning of the data in FIG. 8 may be determined as appropriate, such that receiving devices 1 having a viewing history of at least one of the multiple contents specified as the viewing history are controlled (i.e., an OR condition for the contents) or receiving devices 1 having a viewing history of all of the contents are controlled (i.e., an AND condition for the contents). On the other hand, the data in FIG. 9 described below determines the presentation ratio in the receiving device 1 for a different viewing history.

[0093] FIG. 9 is a schematic diagram showing metadata different from that shown in FIG. 8 relating to the implementation of a fourth example of presentation condition determination. The data shown in FIG. 9 also has data for each of the items: eventId (event identifier), condition (presentation condition), presentationRate (presentation ratio), and eventObject (event object entity). A feature of the data shown in FIG. 9 is that no content is specified as the viewing history (userHistory) in the presentation condition (condition) (an empty set). Furthermore, in the data shown in FIG. 9, "1%" is specified as the presentation rate (presentationRate). This means that there is no condition for the viewing history, such as having viewed a specific content, and the presentation rate is set to 1%.

[0094] That is, in this example, the distribution device 2 provides both the metadata shown in FIG. 8 and the metadata shown in FIG. 9 to the receiving device 1. On the receiving device 1 side that receives these metadata, if the viewing history of the content identifiers "12345678" or "12345679" is present, the presentation rate (probability) is set to 10% in accordance with the metadata shown in FIG. 8, and in other cases (if the viewing history of the content identifiers "12345678" or "12345679" is not present), the presentation rate (probability) is set to 1% in accordance with the metadata shown in FIG. 9. Note that the entity of the event object (eventObject) in the metadata in FIG. 8 and the entity of the event object (eventObject) in the metadata in FIG. 9 may be the same or different. That is, in this example, it is possible to present event information in different ways depending on the viewing history of the user of the receiving device 1.

[0095] As described above with respect to the first to fourth examples of determining the presentation condition, the event presentation condition may be various types of conditions. Based on these various conditions, the event notification control unit 33 determines whether to present the event information.

[0096] That is, the event presentation condition may include a condition regarding the start time of the time period during which the event information can be presented (see the first presentation condition determination example).The event presentation condition may also include a condition regarding the end time of the time period during which the event information can be presented (see the second presentation condition determination example).

[0097] The event presentation condition may also include a condition regarding an event presentation ratio, which indicates the ratio (probability) of presenting event information (see the third and fourth presentation condition determination examples). The ratio here refers to the ratio of receiving devices 1 that present the event among the relevant receiving devices 1.

[0098] The event presentation condition may also include a condition regarding the location of the receiving device 1 (see the third presentation condition determination example).The event presentation condition may also include a condition regarding whether or not a viewing history of a specific content is stored in the viewing history storage unit (see the fourth presentation condition determination example).

[0099] It should be noted that a plurality of these event presentation conditions may be used in combination as appropriate.

[0100] FIG. 10 is a block diagram showing an example of the internal configuration of each device constituting the system 7 in the above embodiment. Each device (receiving device 1, distribution device 2, content supply device 3) can be realized using a computer. As shown in the figure, the computer includes a central processing unit 901, RAM 902, an input / output port 903, input / output devices 904 and 905, etc., and a bus 906. The computer itself can be realized using existing technology. The central processing unit 901 executes instructions contained in a program read from RAM 902 or the like. In accordance with each instruction, the central processing unit 901 writes data to RAM 902, reads data from RAM 902, and performs arithmetic and logical operations. RAM 902 stores data and programs. Each element contained in RAM 902 has an address and can be accessed using the address. RAM is an abbreviation for "random access memory." The input / output port 903 is a port through which the central processing unit 901 exchanges data with external input / output devices, etc. Input / output devices 904 and 905 are input / output devices. The input / output devices 904 and 905 exchange data with the central processing unit 901 via an input / output port 903. A bus 906 is a common communication path used within the computer. For example, the central processing unit 901 reads and writes data from / to RAM 902 via the bus 906. Also, for example, the central processing unit 901 accesses the input / output port via the bus 906.

[0101] At least some of the functions of the receiving device 1, distribution device 2, and content supply device 3 in the above-described embodiments can be realized by a computer and a program. In this case, the functions can be realized by recording a program for realizing the functions on a computer-readable recording medium and loading and executing the program recorded on the recording medium into a computer system. Note that the term "computer system" as used herein includes hardware such as an OS and peripheral devices. Furthermore, the term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, CD-ROMs, DVD-ROMs, and USB memory, as well as storage devices such as hard disks built into computer systems. In other words, a "computer-readable recording medium" may be a non-transitory computer-readable recording medium. Furthermore, the term "computer-readable recording medium" may also include media that temporarily and dynamically store programs, such as communication lines used when transmitting programs via networks such as the Internet or telephone lines, or media that store programs for a certain period of time, such as volatile memory within a computer system that serves as a server or client in such cases. The program may be designed to realize some of the functions described above, or may be capable of realizing the functions described above in combination with a program already stored in the computer system.

[0102] [Variations] The above embodiment can also be implemented with the following modifications. The event notification history management unit 36 ​​of the receiving device 1 may be configured not to transmit information about the event notification history to the distribution device 2. Furthermore, the event notification history management unit 36 ​​of the receiving device 1 may be configured not to transmit information about the user's behavior after the event is presented, which is included in the event notification history, to the distribution device 2.

[0103] Although an embodiment of the present invention has been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and includes designs within the scope of the gist of the present invention. [Industrial Applicability]

[0104] The present invention can be used in systems for distributing content via broadcasting or communication, for example, but the scope of use of the present invention is not limited to the examples given here. [Explanation of symbols]

[0105] 1. Receiving device 2. Distribution Device 3 Content supply device 7. System 11 Instruction part 21 Content receiving unit 22 Content presentation section 31 Event information acquisition unit 32 Event information storage unit 33 Event notification control section 34 User information storage unit 35 Event Presentation Section 36 Event notification history management unit 51 Event Publishing Management Department 52 Content Distribution Department 53 Event Information Transmission Department 54 Event issuing history acquisition unit 901 Central Processing Unit 902 RAM 903 Input / Output Ports 904,905 Input / Output Devices 906 Bus

Claims

1. a content receiving unit that receives content; a content presenting unit that presents the received content; an event information acquisition unit that acquires event information and event presentation conditions related to the content; an event notification control unit that determines the event presentation condition and controls whether or not to present the event information; an event presentation unit that presents the event information only when the event notification control unit determines that the event information should be presented; an event notification history management unit that manages a history indicating that the event information has been presented by the event presentation unit as an event notification history and transmits the event notification history to an external device; A receiving device comprising:

2. the event notification history includes information on user behavior corresponding to the event information being presented by the event presentation unit; 2. The receiving device according to claim 1.

3. A content receiving unit that receives content; a content presenting unit that presents the received content; an event information acquisition unit that acquires event information and event presentation conditions related to the content; an event notification control unit that determines the event presentation condition and controls whether or not to present the event information; an event presentation unit that presents the event information only when the event notification control unit determines that the event information should be presented; Equipped with the event presentation condition includes a condition regarding an event presentation ratio that indicates a ratio at which the event information is presented; Receiving device.

4. A content receiving unit that receives content; a content presenting unit that presents the received content; an event information acquisition unit that acquires event information and event presentation conditions related to the content; an event notification control unit that determines the event presentation condition and controls whether or not to present the event information; an event presentation unit that presents the event information only when the event notification control unit determines that the event information should be presented; a viewing history storage unit that stores a viewing history indicating a history of the content presented by the content presenting unit; Equipped with the event presentation condition includes a condition as to whether a viewing history of a specific content is stored in the viewing history storage unit; Receiving device.

5. the event presentation condition includes a condition regarding a start time of a time period during which the event information can be presented; 5. A receiving device according to any one of claims 1 to 4.

6. the event presentation condition further includes a condition regarding an end time of a time period during which the event information can be presented; 6. The receiving device according to claim 5.

7. the event presentation condition includes a condition related to a location where the receiving device is located; 7. A receiving device according to any one of claims 1 to 6.

8. the event notification control unit repeatedly determines whether the event presentation condition is met, and when a predetermined presentation termination condition is met, ends the repeated determination of the event presentation condition and terminates control of whether or not to present the event information; the presentation end condition includes either that a predetermined number of events have been presented or that the content presenter has ended presentation of the content; 8. Receiving device according to any one of claims 1 to 7.

9. A system including a receiving device and a distribution device, The receiving device is a receiving device according to any one of claims 1 to 8, the distribution device distributes the content, the event information, and the event presentation conditions to the receiving device; system.

10. A program that causes a computer to function as a receiving device described in any one of claims 1 to 8.

Images