JP7814136B2 - Receiving device, system, and program - Google Patents

Description

The present invention relates to a receiving device, a system, and a program.

Using existing technology, it is now possible to provide metadata in conjunction with the distribution of video and audio content. This content can be distributed either via broadcast or communication (Internet, etc.). Event messages describing 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 mechanism for providing event messages in conjunction with video content distributed over the Internet.

By providing event messages as a type of metadata, various services can be realized in conjunction with 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 exhibits at an exhibition or the like. Also, information about 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 (enjoying visiting TV drama filming locations or 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 event messages.

Patent Document 1 discloses information provision method and system technology. The technology in Patent Document 1 associates widely distributed coupon information with broadcast programs. Using this system, it is possible to identify broadcast programs based on the coupon information. There is also a mechanism in place where coupons become 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.

JP 2015-187838 A

The above-mentioned conventional technologies have the following issues. Whether via broadcast or communication, content can be distributed simultaneously to an unspecified number of users. However, physical stores, tourist facilities, etc. have a limit to the number of visitors they can accommodate or handle at one time. Furthermore, when services are provided via communication over the Internet, there is a limit to the number of users that can be handled at one time, 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 did not have a 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 were distributed simultaneously to an unspecified number of users, confusion or congestion could occur at the hosting stores, facilities, or equipment.

The present invention was made in consideration of the above circumstances, and aims to provide a receiving device, system, and program that makes it possible to appropriately control the quantitative scale of the impact caused by the provision of event information (event messages).

[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 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 if the event notification control unit determines that the event information should be presented.

[2] In another aspect of the present invention, the receiving device described above 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.

[3] In another aspect of the present invention, in the receiving device described above, the event notification history includes information about user actions corresponding to the event information being presented by the event presenting unit.

[4] In another aspect of the present invention, in the receiving device described above, the event presentation conditions include a condition regarding the start time of a time period during which the event information can be presented.

[5] In another aspect of the present invention, in the receiving device described above, the event presentation conditions further include a condition regarding the end time of a time period during which the event information can be presented.

[6] Another aspect of the present invention is that, in the above-mentioned receiving device, the event presentation conditions include a condition regarding an event presentation ratio that indicates the ratio at which the event information is presented.

[7] Another aspect of the present invention is that, in the receiving device described above, the event presentation conditions include a condition related to the location of the receiving device.

[8] In another aspect of the present invention, the receiving device further includes a viewing history storage unit that stores a viewing history indicating a history of when the content presentation unit has presented the content, and the event presentation condition includes a condition regarding whether a viewing history of a specific content item is stored in the viewing history storage unit.

[9] In another aspect of the present invention, in the receiving device described above, the event notification control unit repeatedly determines whether the event presentation conditions are met, and when a predetermined presentation end condition is met, the event notification control unit stops the repeated determination of the event presentation conditions and ends control of whether or not to present the event information, and the presentation end condition includes either the completion of a predetermined number of event presentations or the content presentation unit ending presentation of the content.

[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.

[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 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 and controls whether or not to present the event information, and an event presentation unit that presents the event information only if the event notification control unit determines that the event information should be presented.

According to the present invention, the event notification control unit in the receiving device determines the event presentation conditions and controls whether or not to present event information. In other words, according to the present invention, by appropriately setting the event presentation conditions, it is possible to appropriately control the quantitative scale of the impact caused by the provision of event information.

1 is a block diagram showing a schematic functional configuration of a receiving device according to an embodiment of the present invention. FIG. 2 is a block diagram showing a schematic functional configuration of a distribution device according to the embodiment. 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. FIG. 2 is a processing sequence diagram showing the operation procedure of the system according to the embodiment. 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. 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. 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. 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. FIG. 10 is a schematic diagram showing an example (2/2) of the configuration of metadata for implementing the fourth presentation condition determination example in the system according to the embodiment. FIG. 2 is a block diagram showing an example of the internal configuration of each device constituting the system according to the embodiment.

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

The receiving device presents the event to the user in accordance with the event presentation conditions. The event presentation conditions are conditions whose truth value changes at different times for each user. In other words, instead of multiple receiving devices presenting the event to the user 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 the event to each user. This makes it possible to control the number of users to whom an event is presented at a given time.

Event presentation conditions depend on the user's content viewing history, place of residence (receiving location), and other factors. Event presentation conditions may also be true or false depending on random factors (e.g., pseudo-random numbers). 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 conditions).

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 about the timing at which each receiving device presented the event to the user. Furthermore, the event notification history may include information about the user's behavior after the event was presented on the distribution device. Information about 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 about locations visited by the user can be obtained, for example, using the GPS function of the receiving device. GPS stands for Global Positioning System.

Figure 1 is a block diagram showing the general 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 implemented, for example, by a computer and a program. Each functional unit also has storage means as needed. Storage means is, for example, program variables or memory allocated by program execution. Non-volatile storage means such as a magnetic hard disk drive or solid-state drive (SSD) may also be used as needed. At least some of the functions of each functional unit may also be implemented as dedicated electronic circuits rather than by programs.

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

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.

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 specified 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.

If the content data includes metadata, the content receiving unit 21 passes the metadata to the event information acquisition unit 31. The metadata includes event information.

The content presentation unit 22 presents to the user the content received by and passed from the content receiving unit 21. Specifically, the content presentation 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 presentation 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 presentation unit 22 may write this user viewing history information to the user information storage unit 34, which will be described later.

The event information acquisition unit 31 acquires metadata related to the 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 that 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.

When 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 metadata is not embedded in the content but is provided by 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.

The event information storage unit 32 stores the metadata acquired by the event information acquisition unit 31. As mentioned 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.

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 the event presentation conditions and controls whether or not to cause the event presentation unit 35 to present event information at that time. In other words, the event notification control unit 33 controls whether or not to present event information. When an event should be presented according to the event presentation conditions, the event notification control unit 33 passes the event information read from the event information storage unit 32 to the event presentation unit 35.

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, etc.

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

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's determination of whether or not it is the timing to present the event. In other words, the event presentation unit 35 presents event information only when the event notification control unit 33 determines that the event information should be presented. The event presentation unit 35 presents an event, for example, by displaying information in the form of text or images on a screen, etc. The event presentation unit 35 may also display clickable link information on a screen, etc. When the user clicks on the link information, the event presentation unit 35 can obtain and display more detailed event information via a communications network.

The event presentation unit 35 can also acquire information about the user's actions after the event is presented. User actions here include obtaining other content by clicking on specific link information. User actions also include moving to a specific 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.

The event presentation unit 35 passes historical information related to the presentation of the event to the event notification history management unit 36. This historical information includes information that uniquely identifies the presented event (for example, an event ID, described below), information on the date and time the event was presented, and information on the user's actions after the event was presented.

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 was presented, and feeds this information back to the distribution device as 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 the history indicating that the event presentation unit 35 presented the event information as event notification history, 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.

As explained 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 event presentation history to the distribution device.

Figure 2 is a block diagram showing the general 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 also be implemented, for example, by a computer and a program. Furthermore, each functional unit has a storage means as necessary. At least some of the functions of each functional unit may be implemented as a dedicated electronic circuit rather than a program.

As a typical configuration example, the distribution device 2 may be a device that distributes content via a broadcast signal. 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 the communication line from the receiving device 1 that receives the content. The functions of each part of the distribution device 2 are as follows:

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, and information on user behavior after the event was presented. 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.

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 into the content and distributes it to the receiving device 1. Note that the content distribution unit 52 may distribute content by broadcasting, or by communication via the Internet, etc.

The event information transmission unit 53 transmits metadata including event information and event presentation conditions. When metadata is transmitted in-band, the event information transmission unit 53 passes the metadata to the content distribution unit 52. When 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.

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 events issued by the event issuance management unit 51 is fed back to the event issuance management unit 51.

Note that the content supply device 3 in the figure supplies content and related data to the distribution device 2.

Figure 3 is a block diagram showing the general 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, distribution device 2, and 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.

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 provides feedback of the aforementioned event issuance history information to the distribution device 2.

Figure 4 is a sequence diagram showing the operating procedure of system 7. Here, the operating procedure of this embodiment will be explained following the flow shown in the diagram.

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 in a state where it can 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.

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 broadcast, the receiving device 1 tunes in to a specific broadcast service to receive the content.

In process P3, the distribution device 2 distributes content to the receiving device 1. The content may be, 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 this content and related data.

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, etc. (including earphones, etc.). Furthermore, for event information with no presentation conditions, the receiving device 1 presents it at an appropriate time and by an appropriate means. Process P4 outputs video and audio, and continues for a predetermined period of time. In parallel with process P4, the receiving device 1 executes the loop of process P5 described below.

In process P5, the receiving device 1 repeats processes P6 and P7, described below. Note that if the loop break condition in process P10 is met, the receiving device 1 exits the loop of process P5.

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

In process P7 within the process P5 loop, 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 moves to process P10.

In the above process P8 (first process when the presentation condition is true), the event presentation unit 35 of the receiving device 1 presents 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 the screen. This allows the user to recognize the presented event.

Next, in the above 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 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 actions in response to the presented event. Completion of this process P9 ends process P7.

When the above process P7 is completed, 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.

If the condition for ending presentation is false in process P10 above, the process P5 loop is repeated.

For example, if the event presentation condition determined in process P6 above is set to "present the 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 that way 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.

The condition for ending the event presentation determined in process P10 above becomes true when, for example, the event has been presented a predetermined number of times, the presentation time period has expired, the receiving device 1 is outside the area where the event is being presented (including when the receiving device 1 has moved outside the area where the event is being presented), or viewing of the content has ended.

In other words, the event notification control unit 33 can repeatedly determine the event presentation conditions in a loop (process P5 above). Furthermore, if a predetermined presentation termination condition is met, the event notification control unit 33 exits the repeated determination of the event presentation conditions and terminates control of whether or not to present event information (break in process P10 above). The presentation termination condition includes either the completion of a predetermined number of event presentations or the content presentation unit 22 ending content presentation due to a change in the channel selection state, etc.

Next, we will explain several examples of how to determine event presentation conditions.

[First Presentation Condition Determination Example]
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 or other event has ended.

Specifically, for example, presentation conditions are not set for metadata information that promotes understanding of the program (e.g., local historical information, program subtitle information, 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 encourages users to visit the local area (e.g., 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.

By setting the presentation conditions described above, it is possible to provide information that will help users who view the content to deepen their understanding, while also preventing a large number of visitors from concentrating on events such as festivals. The receiving device 1 also notifies the distribution device 2 of the event presentation history information.

The mechanism described in this example can also be used, for example, to promote tourist visits to a particular region, but suppress visits during a particular peak season and increase the promotion effect during off-peak seasons. In other words, the receiving device 1 can be controlled so that it only displays event information once 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 curb the phenomenon known as tourist pollution or overtourism.

Figure 5 is a schematic diagram showing an example of the configuration of metadata for implementing the first example of presentation condition determination. 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 the event identifier, condition is the presentation condition, and eventObject is the entity of the event object.

The event identifier is information used to uniquely identify event information distributed from the distribution device 2. In the example shown, the event identifier is "12345678."

The presentation conditions are the conditions for presenting an event. As already explained, the event notification control unit 33 of the receiving device 1 evaluates these presentation conditions to determine whether or not the event should be presented to the user at the current timing. 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 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 used to separate 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 a time zone 9 hours ahead of Coordinated Universal Time (UTC) (for example, Japan Standard Time).

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 the key information, and value1, value2, and value3 are the 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.

In the example data shown in Figure 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 simply by determining the break condition (process P10 in Figure 4) within the presentation processing loop (process P5 in Figure 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."

[Second Presentation Condition Determination Example]
In the above-described "first presentation condition determination example," it was assumed that the same event presentation conditions were distributed to all distribution 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).

For example, it is assumed that transition information (such as a URL) for accessing a website is provided as event information in content (entertainment content, for example) that is distributed simultaneously to all users via broadcasting or communication.
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 approximately uniform (or nearly so) throughout the entire content distribution time period, rather than concentrating access to the website at a specific point during the content distribution time period.

For example, the distribution device 2 can set event presentation conditions so that the timing of event presentation is dispersed, for example, at the beginning, middle, and end of a program. Alternatively, the distribution device 2 can set 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 results of an analysis of that 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.

Furthermore, in the case of broadcasts spanning multiple regions (multiple broadcast stations) (e.g., nationwide broadcasts), different event presentation conditions can 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 generally expected to be provided in-band, and it is relatively easy to distribute different metadata for each broadcast station in this way.

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

Figure 6 is a schematic diagram showing an example of the metadata configuration related to the implementation of the second presentation condition determination example. Similar to the example shown in Figure 5, the metadata can be expressed in JSON format, etc. Similar to the example shown in Figure 5, the metadata includes data for the following items: eventId (event identifier), condition (presentation condition), and eventObject (event object entity). A feature of the data in Figure 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 conditions 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 will not present the event.

In the second presentation condition determination example described here, the distribution device 2 can specify different time periods as time periods during which events can be presented to the receiving devices 1 of different users. As a result, in the system 7, the presentation of event information on the receiving devices 1 is not concentrated at one time, but is instead distributed according to the times specified in the event presentation conditions.

[Third Presentation Condition Determination 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 1. Furthermore, 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 content for a travel program, for example, the probability of event presentation can be controlled according to the distance (distance) from a region of interest (e.g., a region where a festival introduced in the content is being held).

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 a medium distance from the focused area, the presentation rate of event information may be set to 50%. In areas 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.

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 makes it possible to control events, such as attracting more visitors from desired areas to a festival. Furthermore, depending on how the presentation conditions are set, it is also possible to control events, such as attracting visitors from various dispersed areas, or visitors from a specific concentrated area or its neighboring areas.

Figure 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 with the example shown in Figure 5, the metadata can be expressed in JSON format or the like. As with the example shown in Figure 5, the metadata includes data for the following items: eventId (event identifier), condition (presentation condition), and eventObject (event object entity).

One of the features of the metadata shown in Figure 7 is that, in addition to these items, it also has data for the presentationRate item. PresentationRate represents the presentation ratio, and in the example shown here, the presentation ratio is 100%. The numerical value of this presentation ratio represents the rate (probability) at which the receiving device 1, upon receiving this metadata, will present the event information contained in that metadata to the user. The receiving device 1 presents the event information at a rate (probability) in accordance with this presentation ratio, based on random elements such as random numbers or pseudo-random numbers generated within the device.

One of the other features of the metadata shown in Figure 7 is that availableUserArea is specified as a presentation condition. availableUserArea specifies the area of users to whom the event can be presented. In this example, the data specifies a list of multiple areas where the user (receiving device 1) is located. The data in Figure 7 specifies a list of area information including 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).

In other words, the metadata shown in Figure 7 causes the receiving device 1 to control the presentation of events in the areas included in the list specified by availableUserArea at a presentation rate according to presentationRate. Note that the receiving device 1 can determine its own location using, for example, a GPS function or a function for identifying base stations in a wireless communication network. While Figure 7 only shows data when the presentation rate is 100%, by providing presentation conditions that change the presentation rate 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.

[Fourth Presentation Condition Determination Example]
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 event presentation by referencing this viewing history. The receiving device 1 retains, as the viewing history, information indicating whether the user of the receiving device 1 viewed each broadcast of a certain content series. 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 continuing to watch) can be provided with beneficial information or information that improves the probability of winning a prize. Furthermore, for example, light users (users who watch content relatively casually) can be provided with information that provides supplementary information about the content or information aimed at promoting the content.

Figure 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 Figure 7, the metadata in Figure 8 includes data for the following items: eventId (event identifier), condition (presentation condition), presentationRate (presentation rate), and eventObject (event object entity).

The metadata shown in Figure 8 is characterized by the specification of a viewing history (userHistory) as the event presentation condition. This viewing history specifies a list of content identified by a content identifier (contentId) or the like. The content identifiers shown in Figure 8 are "12345678" and "12345679." The metadata also specifies a presentation rate of "10%." This indicates that the content presentation condition is set so that the presentation rate (probability) is 10% for receiving devices 1 with viewing histories of content represented by content identifiers such as "12345678" and "12345679." The data in Figure 8 can be appropriately defined to control receiving devices 1 with viewing histories of at least any of the multiple contents specified in the viewing history (i.e., an OR condition for the contents) or receiving devices 1 with viewing histories of all of the contents (i.e., an AND condition for the contents). On the other hand, the data in Figure 9, which will be explained below, determines the presentation ratio on the receiving device 1 for a different viewing history.

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

In other words, 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. Upon receiving this metadata, the receiving device 1 sets the presentation rate (probability) to 10% in accordance with the metadata shown in FIG. 8 if the receiving device 1 has a viewing history for content identifiers "12345678" or "12345679." In other cases (if the receiving device 1 does not have a viewing history for content identifiers "12345678" or "12345679"), the presentation rate (probability) is set to 1% in accordance with the metadata shown in FIG. 9. The event object entity (eventObject) in the metadata in FIG. 8 and the event object entity (eventObject) in the metadata in FIG. 9 may be the same or different. In other words, 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.

As explained above in the first through fourth presentation condition determination examples, the event presentation conditions may be of various types. Based on these various conditions, the event notification control unit 33 determines whether or not to present event information.

In other words, the event presentation conditions may include a condition regarding the start time of the time period during which event information can be presented (see the first presentation condition determination example). Furthermore, the event presentation conditions may further include a condition regarding the end time of the time period during which event information can be presented (see the second presentation condition determination example).

The event presentation conditions may also include a condition related to the 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 all applicable receiving devices 1.

The event presentation condition may also include a condition related to the location of the receiving device 1 (see the third presentation condition determination example). The event presentation condition may also include a condition related to whether a viewing history for a specific content item is stored in the viewing history storage unit (see the fourth presentation condition determination example).

You can also use multiple of these event presentation conditions in combination as appropriate.

Figure 10 is a block diagram showing an example of the internal configuration of each device constituting system 7 in the above embodiment. Each device (receiving device 1, distribution device 2, content supply device 3) can be implemented using a computer. As shown in the figure, the computer includes a central processing unit 901, RAM 902, input/output port 903, input/output devices 904 and 905, etc., and bus 906. The computer itself can be implemented using existing technology. The central processing unit 901 executes instructions contained in programs read from RAM 902, etc. 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. Note that 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 the input/output port 903. The bus 906 is a common communication path used within the computer. For example, the central processing unit 901 reads and writes data from RAM 902 via the bus 906. Also, for example, the central processing unit 901 accesses the input/output port via the bus 906.

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 program for realizing this function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be loaded into a computer system and executed. Note that the term "computer system" here includes hardware such as an OS and peripheral devices. Furthermore, "computer-readable recording medium" refers to portable media such as floppy 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, a "computer-readable recording medium" may also include media that temporarily and dynamically store programs, such as communication lines used when transmitting programs via networks like the Internet or communication lines like telephone lines, or media that store programs for a certain period of time, such as volatile memory within the computer systems that serve as the server or client in such cases. Furthermore, the above 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 recorded on the computer system.

[Modification]
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.

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

The present invention can be used, for example, in systems that distribute content via broadcasting or communications. However, the scope of use of the present invention is not limited to the examples given here.

REFERENCE SIGNS LIST 1 Receiving device 2 Distribution device 3 Content supply device 7 System 11 Instruction unit 21 Content receiving unit 22 Content presenting unit 31 Event information acquiring unit 32 Event information storage unit 33 Event notification control unit 34 User information storage unit 35 Event presenting unit 36 Event notification history management unit 51 Event issuance management unit 52 Content distribution unit 53 Event information transmitting unit 54 Event issuance history acquiring unit 901 Central processing unit 902 RAM
903 Input/output port 904, 905 Input/output device 906 Bus

Claims (10)

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 : 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 . 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. 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. 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 . 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 . 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 . 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 . 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. A program that causes a computer to function as the receiving device according to any one of claims 1 to 8 .