JP6632131B2 - Viewing amount analysis device and program - Google Patents

Description

  The present invention relates to a viewing amount analysis device and a program for analyzing a viewing amount of video and audio contents.

  Acceleration of communication via the Internet and the development of storage technology capable of recording and storing large amounts of digital data at high density have led to the storage and distribution of large amounts of content such as video as files. It became possible.

For example, Patent Literature 1 describes a time shift viewing / listening service capable of zapping. According to this technique, a broadcasted program file is stored in a server, and the stored broadcast program is distributed in response to a request from a viewer to enable viewing. This service allows a viewer to search for a desired video content while jumping in the time direction while viewing a distributed broadcast program. That is, the viewer can search for a desired program while jumping over a plurality of past broadcast programs, or search for a desired scene while jumping over a plurality of scenes in the program.
Patent Document 2 describes a viewing service that allows a user to search for a desired program using tags attached to scenes in the program. In this service, tags (data representing keywords and the like) related to the scenes are assigned to each scene of a broadcast program stored for the video-on-demand service, and the tags are managed in a database. Thus, the viewer can search for a broadcast program to be watched or a scene to watch while jumping in the time direction at a high speed by narrowing the interests using the tag as a key.
Patent Literature 3 describes a technique of a database device for adding and managing the above-described tags to scenes of a broadcast program.

On the other hand, there is a technology for collectively managing various logs output from a computer system. By accumulating and managing various log data such as an access log and an error log by using such a technique, it becomes easy to identify a failure point even when a trouble or the like occurs in the system.
For example, a server device that provides web content usually has a function of outputting an error log and an access log. By analyzing the access log, it is possible to know which content (which page) is frequently accessed. This allows the web operator to know popular content. In addition, if the content with high access is identified, it is possible to distribute the access and avoid load concentration on the device by taking measures such as placing the same content on other server devices. It becomes.
According to the technology described in Non-Patent Document 1, it is possible to collect and manage various logs at one place.

Japanese Patent No. 5789450 JP 2014-178949 A JP 2015-154105 A

"What is Fluentd?", [Online], Fluentd project, [searched February 10, 2016], Internet <URL: http://www.fluentd.org/architecture>

  However, in the related art, there is a problem that the web server device can only take an access log for access on a file basis. Here, the file is an HTML (Hyper Text Markup Language) file, an image file, a moving image file, or the like. In addition, even in a server device that performs streaming distribution of a moving image, there is a problem that an access log can be obtained only in units of a streaming request from a client. Due to these problems, conventionally, it has not been possible to accurately grasp the viewing amount of the distributed content.

The present invention has been made in view of the above-described circumstances, and enables a system that distributes content such as video on demand to accurately grasp the amount of video actually viewed. An object of the present invention is to provide a viewing amount analysis device and a program therefor.
A secondary problem is to provide a viewing amount analysis device and a program capable of grasping and analyzing a viewing amount in relation to a tag assigned in association with a scene.

  [1] In order to solve the above-described problem, a viewing amount analysis apparatus according to an aspect of the present invention provides a viewing / listening apparatus that generates a viewing log indicating frames distributed for program contents distributed via a communication network for each distribution destination. A log generation unit, a viewing log storage unit that collects and stores the viewing log generated by the viewing log generation unit, and a viewing amount for each frame distributed by reading the viewing log from the viewing log storage unit. And a viewing data analysis unit for determining

  [2] Further, according to an aspect of the present invention, in the viewing amount analyzing apparatus, the program content is already broadcasted program content, and the viewing log generation unit includes information of a broadcast date and time for each frame. The viewing log is generated.

  [3] One embodiment of the present invention is the above-described viewing amount analysis device, further comprising: a tag data storage unit that stores information of a tag assigned to each frame, wherein the viewing data analysis unit includes the tag data. The amount of viewing for each tag is obtained by adding information of the tag to information of the frame represented by the viewing log based on a relationship between a frame and a tag stored in a storage unit. .

  [4] Further, according to an aspect of the present invention, in the viewing amount analyzing apparatus, the viewing log generating unit includes information on a frame rate indicating the number of frames per unit time when the frames are distributed. The viewing log is generated, and the number of frames when the frames are distributed is converted into a value of the number of frames at a reference frame rate or a value of the number of unit times having a predetermined length. The audiovisual data analyzing unit further includes an amount converting unit, and the viewing data analyzing unit obtains the viewing amount using a result converted by the viewing amount converting unit.

  [5] One embodiment of the present invention provides a viewing log generation unit that generates a viewing log representing a frame distributed for program content distributed via a communication network for each distribution destination, and the viewing log generation. A viewing log storage unit that collects and stores the viewing log generated by the unit; and a viewing data analysis unit that obtains a viewing amount for each frame distributed by reading the viewing log from the viewing log storage unit. It is a program for.

  According to the present invention, it is possible to analyze a detailed viewing amount in a system that distributes contents such as broadcast programs. That is, it is possible to count the amount of viewing in association with the number of frames based on the information of the log of the actually viewed location in the content as well as the log related to the request for the content. In addition, it is possible to total the amount of viewing for each tag that has been viewed for each tag attached to the scene of the program content.

1 is a block diagram illustrating a schematic functional configuration of a viewing amount analysis device according to a first embodiment of the present invention. FIG. 2 is a block diagram showing a schematic functional configuration of the log server device according to the embodiment. FIG. 3 is a schematic diagram showing a data configuration of a viewing log in the embodiment. FIG. 2 is a block diagram illustrating a schematic functional configuration of a log collection and accumulation server device according to the embodiment. FIG. 2 is a block diagram illustrating a schematic functional configuration of the tag database device according to the embodiment. FIG. 3 is a schematic diagram showing a configuration and data example of tag data held by the tag database device according to the embodiment. It is the schematic which showed the content of the tag represented by the tag data which the tag database apparatus by the embodiment shows along the time axis. FIG. 2 is a block diagram illustrating a schematic functional configuration of a log analysis server device according to the embodiment. It shows an example of the analysis result by the viewing data analysis unit according to the embodiment, and is an example in which the viewing amount for each frame (for each time) is totaled. It shows an example of the analysis result by the viewing data analysis unit according to the embodiment, and is an example in which the viewing amount for each tag is totaled. It is a flowchart which shows the procedure of the process which the log collection accumulation | storage server apparatus by the embodiment collects and saves the viewing log of the program content generated by the log server apparatus. It is a flowchart which shows the procedure of the process which the log analysis server apparatus by the embodiment analyzes a viewing log. The following describes a procedure in a case where the analysis client device specifies a start time / end time condition and analyzes the viewing amount for each broadcast time (for each frame). It is a flowchart which shows the procedure of the process which the log analysis server apparatus by the embodiment analyzes a viewing log. The following describes a procedure for analyzing a viewing amount for each broadcast time (for each frame) by specifying a period length from an analysis client device. It is a flowchart which shows the procedure of the process which the log analysis server apparatus by the embodiment analyzes a viewing log. The following describes a procedure for analyzing a viewing amount for each tag by specifying a start time / end time condition from an analysis client device. FIG. 4 is a schematic diagram illustrating a data configuration when a viewing log according to the embodiment is associated with tag information. It is a flowchart which shows the procedure of the process which the log analysis server apparatus by the embodiment analyzes a viewing log. The following describes a procedure for analyzing a viewing amount for each tag by specifying a period length from an analysis client device. FIG. 11 is a block diagram illustrating a schematic functional configuration of a log analysis server device 800 according to a second embodiment. FIG. 3 is a schematic diagram showing a data configuration of a viewing log in the embodiment. FIG. 4 is a schematic diagram illustrating a data configuration when a viewing log according to the embodiment is associated with tag information.

Next, an embodiment of the present invention will be described with reference to the drawings.
[First Embodiment]
FIG. 1 is a block diagram showing a schematic functional configuration of the viewing amount analyzing apparatus according to the first embodiment. As shown in FIG. 1, the viewing amount analysis device 1 includes a log server device 100-1, 100-2,..., 100-X, a log collection / storage server device 200, a tag database device 300, a log analysis device. It is configured to include a server device 400 and an analysis client device 500. Each of the plurality of log server devices 100-1, 100-2, ..., 100-X may be simply referred to as "log server device 100" below. Here, the number of log server devices 100 is X (X is an arbitrary positive integer). Each device shown in FIG. 1 is connected by a communication network. The communication network includes, for example, the Internet, a LAN (local area network) inside an organization such as a company, a dedicated line connecting remote locations, or a combination thereof. Between the distribution server device 50 and the log server device 100, between the log server device 100 and the log collection and storage server device 200, between the log collection and storage server device 200 and the log analysis server device 400, between the tag database device 300 and the log Data can be mutually transmitted and received between the analysis server device 400 and the log analysis server device 400 and the analysis client device 500 via the communication network.

  The log server devices 100-1, 100-2,..., 100-X generate viewing logs based on information obtained from the distribution server devices 50-1, 50-2,. Generate. The log server devices 100-1, 100-2,..., 100-X transmit the generated viewing logs to the log collection and accumulation server device 200. Each of the distribution server devices 50-1, 50-2,..., 50-X may be simply referred to as “distribution server device 50” below. Here, the number of distribution server devices 50 is X, which corresponds to the log server device 100 on a one-to-one basis. However, the number of distribution server devices 50 is arbitrary, and the correspondence between the distribution server device 50 and the log server device 100 is also arbitrary.

The devices constituting the viewing amount analysis device 1 may be in a form in which they are all stored in one housing, or may be in a form in which functions are distributed to a plurality of housings.
Further, some of the plurality of devices constituting the viewing amount analysis device 1 may be realized as the same device. For example, the distribution server device 50 and the log server device 100 may be different programs running on the same server device (computer). When the viewing amount analyzing apparatus 1 is configured as a plurality of housings, each housing may be placed in a place close to each other (for example, in one data center) or may be placed in a remote place. . When the viewing amount analysis device 1 is configured as a plurality of housings, the viewing amount analysis device 1 may be referred to as a viewing amount analysis system. However, hereinafter, they are collectively referred to as "viewing amount analyzing device 1".
In this description, the distribution server device 50 and the log server device 100 are described as different devices, but may be different programs that operate on the same device (computer).

An example of the content distribution system assumed in the present embodiment is as follows. The content distribution system mainly includes a plurality of distribution server devices 50, a communication network (not shown), and a number of viewing client devices (not shown). Note that the viewing client device is, for example, an information device such as a television receiver, a television recorder, a personal computer (PC), a tablet, a smartphone (smartphone), a smartwatch, and a wearable terminal. The viewing client device can send a content distribution request to the distribution server device 50 via the communication network based on an operation by a viewer or the like. The distribution server device 50 distributes video and audio data of the television program to the requesting viewing client device at an arbitrary time after the broadcast of the television program in response to a distribution request from the viewing client device.
The distribution server device 50 is configured to distribute contents of a plurality of broadcast services by a plurality of broadcast stations. However, the distribution server device 50 may be configured to distribute contents of a plurality of broadcast services by a single broadcast station, or to distribute only contents of a single broadcast service by a single broadcast station. May be configured.
The distribution request from the viewing client device includes information for specifying the broadcast service, information for specifying the broadcasting time of the distribution start (year, month, day, hour, minute, second, etc.), and a distribution request from the viewing client device. And information for specifying the date and time at which the operation was performed. Here, the information for specifying the broadcast service is represented by, for example, a combination of an area ID and a broadcast station ID. Note that information for specifying a broadcast service may be expressed by another method.
Also, by sequentially transmitting information of different broadcast times from the viewing client device side, the viewer can search for the scene to watch while jumping in the time direction, that is, jumping a plurality of scenes in the program. it can. In other words, the viewing client device side can request a plurality of scenes desired by the viewer in a discrete manner.
The content distribution system described here is only an example, and the viewing amount analysis device according to the present embodiment can be applied to other content distribution systems.

  The distribution server device 50 passes, to the log server device 100, information of a distribution request from each viewing client device and information of a distribution result based on the distribution request. The viewing client device communicates with the distribution server device 50 via, for example, the Internet. By using such a content distribution system, a viewer can view a television broadcast program even after the broadcast time (including so-called “chase-up playback (viewing)”).

The log server device 100 records, as a viewing log, data of a distribution request access passed from the distribution server device 50 when there is a distribution request access to the distribution server device 50. The log server device 100 transmits the recorded viewing log to the log collection and accumulation server device 200.
The log collection / storage server device 200 receives and stores the viewing log transmitted from the log server device 100. When the log collection / storage server device 200 receives a request for a viewing log from the log analysis server device 400, the log collection / storage server device 200 transmits the requested viewing log to the log analysis server device 400.

  The tag database device 300 manages and stores tags attached to scenes of program contents. Further, when tag data is requested from the log analysis server device 400, the tag database device 300 converts the tag data attached to the scene of the program content into the log analysis server device in response to the request. 400.

  The log analysis server device 400 receives a viewing log from the log collection and accumulation server device 200 based on a request from the analysis client device 500. Note that the request from the analysis client device 500 includes a condition relating to the viewing log, and the log analysis server device 400 requests the log collection / storage server device 200 to receive a viewing log that satisfies the condition. . The log analysis server device 400 counts the number of viewing logs for each video frame based on the information on the time code of the program content included in the received viewing log. That is, the log analysis server device 400 calculates the viewing amount for each video frame based on the viewing log.

  Further, the log analysis server device 400 may calculate the viewing amount for each tag. Specifically, the log analysis server device 400 acquires a viewing log from the log collection / storage server device 200 based on the condition requested from the analysis client device 500. Then, it requests the tag database device 300 for information on tags associated with those viewing logs, and receives information on the corresponding tags from the tag database device 300. Then, the log analysis server device 400 counts the number of viewing logs for each tag. That is, the log analysis server device 400 counts the number of frames viewed for each tag based on the conditions specified by the analysis client device 500. That is, the log analysis server device 400 calculates the viewing amount for each tag based on the conditions specified by the analysis client device 500.

  Video frames occupy a predetermined amount of time. The length of time is a frame period. That is, viewing one video frame and generating a viewing log corresponding to the video frame corresponds to viewing the program content for the length of the frame period. That is, the viewing amount is proportional to the number of viewing logs. The frame period is a reciprocal of a frame rate described later.

  The analysis client device 500 requests the log analysis server device 400 to analyze the viewing log based on the measurement conditions input by the user. The user can input desired conditions to the analysis client device 500 for the measurement and analysis of the viewing amount. The analysis client device 500 receives the data of the analysis result of the viewing amount transmitted from the log analysis server device 400 as a response. The analysis client device 500 displays the received data of the analysis result on the screen as character information representing a numerical value, or displays the data on the screen as a graph. The method of displaying the viewing amount information on the analysis client device 500 is not particularly limited, and is arbitrary. The analysis client device 500 is, for example, an information device such as a personal computer (PC), a tablet, a smartphone (smartphone), a smart watch, or a wearable terminal.

  As described above, in the viewing amount analysis device 1, the log server device 100 records the viewing log indicating the status of the distribution of the program content from the distribution server device 50 to the viewing client device. Then, the log collection and accumulation server device 200 collects all viewing logs. In the viewing amount analysis device 1, the log collection / storage server device 200 transmits the viewing log requested by the analysis client device 500 to the log analysis server device 400 among the stored viewing logs. Further, the tag database device 300 transmits information on the tag attached to the program content to be analyzed to the log analysis server device 400. The log analysis server device 400 counts the number of viewed video frames based on the viewing log. Further, the log analysis server device 400 counts the number of viewed video frames in association with the tag. The log analysis server device 400 transmits the information on the viewing amount obtained in this manner to the analysis client device 500 that has made the request. The analysis client device 500 displays the received viewing amount information.

Next, a more detailed functional configuration of the main devices included in FIG. 1 will be described.
FIG. 2 is a block diagram showing a schematic functional configuration of the log server device 100. As shown, the log server device 100 includes a viewing log generation unit 101, a viewing log recording unit 102, a viewing log transmission unit 103, and a viewing log storage unit 104.

The viewing log generation unit 101 generates a viewing log that represents, for each distribution destination, a frame distributed with respect to the program content distributed via the communication network. Specifically, when the distribution server device 50 distributes the program content in response to a request from the viewing client device, the viewing log generation unit 101 generates a viewing log based on information obtained from the distribution server device 50. Then, the viewing log generation unit 101 passes the generated viewing log to the viewing log recording unit 102 and the viewing log transmission unit 103.
The viewing log recording unit 102 writes the viewing log received from the viewing log generating unit 101 into the viewing log storage unit 104.
The viewing log transmission unit 103 transmits the viewing log received from the viewing log generation unit 101 to the log collection / storage server device 200 via the communication network.
The viewing log storage unit 104 has a function of storing a viewing log. The viewing log storage unit 104 includes a storage medium (for example, a magnetic hard disk device (HDD), a semiconductor disk device (SSD), and the like).

  FIG. 3 is a schematic diagram showing a data configuration of the viewing log. As shown in the figure, the viewing log is data including distribution destination identification information, distribution date and time, program content broadcast date and time, area ID, and broadcast station ID. The data shown is one viewing log, and corresponds to viewing of one frame. The meaning of each data item included in the viewing log is as follows.

  The distribution destination identification information is information for identifying a distribution destination. Specifically, the distribution destination identification information is information for identifying a viewing client device, information for identifying a viewer, or the like. As the information for identifying the viewing client device, for example, a character string of an IP address or a host name is used. In the illustrated example, the IP address “192.168.1.15” is the distribution destination identification information.

The distribution date and time is the date and time when one frame of the video in the program content was distributed. The date and time are represented in the format of “YYYY / MM / DD hh: mm: ss” (year, month, day, hour, minute, second). The information of the delivery date and time may include the number of the frame which is a unit below the second. When the frame number is included, the delivery date and time is expressed in the format of “YYYY / MM / DD hh: mm: ss; nn”. Here, “nn” below the second is the serial number of the frame within the second. In the illustrated example, the distribution date and time is “2015/10/29 19: 06: 27; 06”. This represents "frame number 06 at 19:06:27 on October 29, 2015". Note that the number of frames per second is appropriately determined according to a broadcast standard or the like. In the present embodiment, the video of the program content includes 30 frames per second. However, the number of frames per second is not limited to 30.
The program content broadcast date and time is the broadcast date and time of the program content that is viewed in accordance with a request from the viewing client device. Note that the program content has been broadcast, and can be distributed from the distribution server device 50 after the broadcast date and time. The broadcast date and time of the program content is expressed up to the frame unit. The broadcast date and time of the program content is represented in the format of “YYYY / MM / DD hh: mm: ss; nn”. In the illustrated example, the program content broadcast date and time is “2012/08/18 19: 00: 58; 06”. This represents "frame number 06 at 19:00:58 on August 18, 2012".
The area ID is information for identifying the area where the program content was broadcast. In Japan, terrestrial television broadcasting is unique to each region, and television broadcasting by broadcasting satellites covers the whole country as a single service area. The area ID is information representing an area such as "Kanto", "Kinki", "nationwide", and the like.
The broadcast station ID is information for identifying a broadcast station or a service.

In the illustrated viewing log, the service is specified by a combination of the area ID and the broadcast station ID. The service may be specified by another method. For example, the service may be specified only by the broadcast station ID.
The program content broadcast date and time is information for specifying a video frame targeted by the viewing log.
The distribution destination identification information is information for specifying a distribution destination.
That is, in the illustrated viewing log data, the frame indicated by the program content broadcast date and time of the service specified by the area ID “nationwide” and the broadcast station ID “BS1” is viewed at the distribution destination indicated by the distribution destination identification information. This is data indicating that the operation has been performed. Thus, the viewing log is generated for each service, each frame time, and each distribution destination (viewer). That is, by collecting and accumulating the viewing log, the viewing amount in the entire system can be grasped in frame units.

  FIG. 4 is a block diagram showing a schematic functional configuration of the log collection and accumulation server device 200. As shown, the log collection and accumulation server device 200 includes a viewing log receiving unit 201, a viewing log recording unit 202, a viewing log request receiving unit 203, a viewing log reading unit 204, a viewing log transmitting unit 205, A log storage unit 206 is included.

The viewing log receiving unit 201 receives viewing logs transmitted from the plurality of log server devices 100 and passes them to the viewing log recording unit 202.
The viewing log recording unit 202 writes the viewing log received from the viewing log receiving unit 201 into the viewing log storage unit 206.
The viewing log request receiving unit 203 receives a request for transmitting a viewing log from the log analysis server device 400, and reads a viewing log that matches a condition included in the request from the viewing log storage unit 206 so as to read the viewing log reading unit. 204.
The viewing log reading unit 204 reads the viewing log from the viewing log storage unit 206 based on the request from the viewing log request receiving unit 203, and passes it to the viewing log transmitting unit 205.
The viewing log transmitting unit 205 transmits the viewing log passed from the viewing log reading unit 204 to the log analysis server device 400 via the communication network.
The viewing log storage unit 206 has a function of storing a viewing log. The viewing log stored by the viewing log storage unit 206 is originally generated by the viewing log generation unit 101 of the log server device 100 and received by the viewing log receiving unit 201. The viewing log storage unit 206 includes a storage medium (for example, a magnetic hard disk device (HDD), a semiconductor disk device (SSD), etc.) inside.

  FIG. 5 is a block diagram showing a schematic functional configuration of the tag database device 300. As illustrated, the tag database device 300 includes a tag data request receiving unit 301, a tag data reading unit 302, a tag data transmitting unit 303, and a tag data storage unit 304.

The tag data request receiving unit 301 receives a request for tag data from the log analysis server device 400. The request from the log analysis server device 400 includes information for specifying a broadcast service (for example, a broadcast station ID and a region ID) and information on a period during which tag data is to be obtained. As the period for which the tag data is to be obtained, information of the start date and time (frame unit) and the end date and time (frame unit) of the period is specified. The tag data request receiving unit 301 requests the tag data reading unit 302 to read the tag data added to the frame within the period of the requested program content.
In response to the request from the tag data request receiving unit 301, the tag data reading unit 302 searches the tag data storage unit 304 based on the specified area ID, broadcasting station ID, and period (start date and time and end date and time). . Then, the tag data reading unit 302 reads the corresponding tag data from the tag data storage unit 304. Then, the tag data reading unit 302 passes the read tag data to the tag data transmitting unit 303.
The tag data transmitting unit 303 transmits the tag data passed from the tag data reading unit 302 to the log analysis server device 400 via a communication network.
The tag data storage unit 304 has a function of storing tag data. That is, the tag data storage unit 304 stores the information of the tag assigned to each distributed frame. The tag data storage unit 304 includes a storage medium (for example, a magnetic hard disk device (HDD), a semiconductor disk device (SSD), and the like).

  FIG. 6 is a schematic diagram showing a configuration of tag data held by the tag database device 300 and a data example. As illustrated, the tag data in the present embodiment is represented as tabular data. This table has items of a number, a region ID, a broadcast station ID, a start frame, an end frame, and a tag. Each row (record) of this table corresponds to a tag attached to a frame included in a predetermined period in the distributed program content. The meaning of each data item included in this table is as follows.

The number is a numerical value assigned to identify each record (row) of the tag data.
The area ID is information for identifying the area of the television broadcast.
The broadcast station ID is information for identifying a broadcast station.
In the present embodiment, a broadcast service is uniquely specified by a combination of the above-mentioned area ID and broadcast station ID.
The start frame is information indicating the first frame of the period in which the tag represented by the record is added in the broadcast service. The start frame is represented in the format of “YYYY / MM / DD hh: mm: ss; nn” (year / month / day, hour / minute / second, frame number). Here, “nn” is a frame number within the second. Here, the number of frames per second is 30, and the frame number is an integer in the range from 00 to 29. The value of the start frame corresponds to the date and time when the program content was broadcast.
The end frame is information indicating the last frame of the period in which the tag represented by the record is added in the broadcast service. The end frame is also expressed in the form of “YYYY / MM / DD hh: mm: ss; nn” (year / month / day, hour / minute / second, frame number), similarly to the start frame.
The combination of the above-mentioned start frame and end frame represents a period in which the tag is provided.
A tag is data provided as a character string. The tag represents a keyword relating to the content of the program content. The words used as tags include general nouns related to program contents, personal names (including cast names) related to program contents, place names related to program contents, and the like. Generally, words related to a program can be used as tags, and there are no special restrictions.

  In the illustrated example, the record with the number 1 has the area ID “Kanto”, the broadcasting station ID “General TV”, and the start frame “2016/04/08 10: 02: 00; 10”. , The end frame is “2016/04/08 10: 09: 39: 00”, and the tag is “dish”. In the example shown in the figure, tag data such as “curry”, “Tao * huo” (person name), “Satoko” (person name), and “Samosa” are also stored.

  FIG. 7 is a schematic diagram showing the content of the tag represented by the tag data held by the tag database device 300 along a time axis. In the figure, the horizontal axis represents time. Here, the time is represented by year, month, day, hour, minute, second, and frame number (serial number within seconds). The content of the tag shown in FIG. 7 corresponds to the data example shown in FIG. For example, the tag “cooking” has a period from “2016/04/08 10: 02: 00; 10” to “2016/04/08 10: 09: 00: 00” (including a start time and an end time, Frame during that period). The tag “curry” is given to a period from “2016/04/08 10: 02: 31; 14” to “2016/04/08 10: 07: 17; 18”. The tag “Tanaka Oo” is added to the period from “2016/04/08 10: 03: 38; 24” to “2016/04/08 10: 06: 33; 04”. The same applies to other tags. As is clear from the above example, the period of a certain tag and the period of another tag may overlap.

  FIG. 8 is a block diagram showing a schematic functional configuration of the log analysis server device 400. As shown in the figure, the log analysis server device 400 includes an analysis condition receiving unit 401, a viewing data analysis unit 402, a viewing log requesting unit 403, a viewing log receiving unit 404, a viewing data recording unit 405, and a reading of the viewing data. Section 406, viewing data erasing section 407, tag requesting section 408, tag data receiving section 409, analysis data recording section 410, analysis data reading section 411, analysis data display section 412, and viewing data storage section 413. And an analysis data storage unit 414.

Here, the viewing amount analyzed by the log analysis server device 400 will be described. The viewing amount is a numerical value obtained by counting how many times a certain video frame in the program content is distributed. In other words, the viewing amount here is the total number of times the video frame distributed from the distribution server devices (50-1 to 50-X) has been viewed by all viewers. For example, when the area ID is “Kanto”, the broadcasting station ID is “general television”, and the frame is specified as “15 frames at 15:01:20 on April 08, 2016”, the log analysis server device 400 Then, all the viewing logs related to the video frame are extracted and counted. Accordingly, the log analysis server device 400 obtains the viewing amount of the video frame.
As described above, the viewing amount is obtained by counting frames. The fact that one frame has been viewed means that the program content for the reciprocal of the frame rate has been viewed. In other words, counting the viewing log for a frame at a certain time means determining how many times the frame has been viewed in all the viewing client devices. By multiplying the number of the viewing logs by the reciprocal of the frame rate, the total time during which the content corresponding to the frame has been viewed can be obtained.

Here, the analysis conditions passed from the analysis client device 500 to the log analysis server device 400 will be described.
The first pattern of the analysis condition is a designation of an access period from the analysis client device 500. The access period is specified by a start time and an end time. Note that the access period can be specified by omitting the end time.
For example, if the start time is specified as 10:00:00 on April 04, 2016 and the end time is specified as 17:59:59 on April 11, 2016, only the viewing log within the access period is analyzed. Be eligible. Here, whether or not a certain viewing log is included in the designated access period is determined by whether or not the distribution date and time included in the viewing log (see FIG. 3) is included in this access period.
Further, for example, when the specification of the end time is omitted and the start time is specified as 18:00:00 on April 12, 2016, all the viewing logs after the specified start time are transmitted to the log analysis server. It is an object of analysis processing by the device 400. If the end time is not specified, the newly generated viewing log is accumulated in the log collection and accumulation server device 200 with time, and increases. In this case, the log analysis server device 400 also targets the newly stored viewing log for the analysis processing.

The second pattern of the analysis condition is a method of designating an access period “from the present to the past, in the direction of ○ hour, minute, and second”. For example, the analysis client device 500 specifies an analysis condition of “2 hours 00 minutes 00 seconds from the present to the past”. Also in this case, the viewing log newly generated with the passage of time becomes a target of the analysis processing. When the analysis condition of the second pattern is received, the log analysis server device 400 immediately acquires the current time by referring to the clock managed by itself. Then, the viewing log from the current time to a point in time when the designated time has elapsed is set as an analysis target.
Also in the second pattern, whether or not a certain viewing log is included in the designated access period is determined by whether or not the distribution date and time included in the viewing log is included in this access period.

Another element of the analysis condition is whether to analyze the viewing amount for each time (for each frame) or to analyze the viewing amount for each tag.
That is, as the combination of the analysis conditions described here, there are the following four types of analysis conditions. That is, the viewing amount per time (per frame) is analyzed by the first pattern, the viewing amount per time (per frame) is analyzed by the second pattern, and the viewing amount per tag is analyzed by the first pattern. The viewing amount is analyzed, and the viewing amount for each tag is analyzed using the second pattern described above.

Next, the function of each unit constituting the log analysis server device 400 will be described individually.
The analysis condition receiving unit 401 receives the data of the analysis condition of the viewing amount transmitted from the analysis client device 500 and notifies the viewing data analysis unit 402 of the data.

The viewing data analysis unit 402 performs an analysis process based on the viewing amount analysis condition notified from the analysis condition receiving unit 401. The viewing data analysis unit 402 obtains the viewing amount for each frame of the distributed program content based on the viewing log read from the viewing log storage unit 206 of the log collection and accumulation server device 200. In addition, the viewing amount for each tag attached to the frame can be obtained.
Specifically, the viewing data analysis unit 402 determines the access period (that is, the range of date, time, hour, minute, and second of the distribution date and time) of the viewing log to be acquired based on the analysis conditions. Then, the viewing data analysis unit 402 notifies the viewing log requesting unit 403 of the information of the access period. The requested viewing log is received by a viewing log receiving unit 404 described later, and written into a viewing data storage unit 413 by a viewing data recording unit 405 described later.
When analyzing the viewing amount for each tag, the viewing data analysis unit 402 requests the tag requesting unit 408 to acquire tag information related to the acquired viewing log. Specifically, the viewing data analysis unit 402 requests the tag requesting unit 408 to obtain information on the tag added to the video frame of the obtained viewing log. When acquiring the requested tag information, the viewing data analysis unit 402 adds the tag information to the viewing log.
Further, the viewing data analysis unit 402 requests the viewing data deletion unit 407 to delete the viewing log out of the conditions based on the analysis condition of the viewing amount notified from the analysis condition reception unit 401. It is necessary to delete the viewing log out of the condition when the viewing log acquired for the past analysis remains in the viewing data storage unit 413.
The viewing data analysis unit 402 counts the number of viewing logs to be analyzed. The viewing data analysis unit 402 counts the number of viewing logs at each time (for each frame) or counts the number of viewing logs for each tag according to the analysis conditions. The number of viewing logs is counted for each tag only when tag information is added to the viewing log. The viewing data analysis unit 402 passes the data of the analysis result to the analysis data recording unit 410.

The viewing log request unit 403 requests the log collection / storage server device 200 for a viewing log corresponding to the access period based on the data (access period information) notified from the viewing data analysis unit 402.
The viewing log receiving unit 404 receives the viewing log transmitted from the log collection / accumulation server device 200 based on the request from the viewing log requesting unit 403, and passes it to the viewing data recording unit 405.

  The viewing data recording unit 405 writes the viewing log passed from the viewing log receiving unit 404 into the viewing data storage unit 413. Also, the viewing data recording unit 405 writes the tag information passed from the tag data receiving unit 409 described later in the viewing data storage unit 413 in association with the viewing log. That is, the viewing data recording unit 405 associates the information of the tag attached to the video frame of the program content with the data of the broadcast date and time (unit of frame) of the program content in the viewing log in association with the viewing log. Write. As a result, the viewing log written in the viewing data storage unit 413 also has information on the tag added to the video frame corresponding to the viewing log.

The viewing data reading unit 406 reads a viewing log from the viewing data storage unit 413 in response to a request from the viewing data analysis unit 402. In addition, the viewing data reading unit 406 reads a viewing log to which tag data is added from the viewing data storage unit 413 in response to a request from the viewing data analysis unit 402.

  The viewing data deletion unit 407 deletes unnecessary viewing data remaining in the viewing data storage unit 413 when requested by the viewing data analysis unit 402. Specifically, the viewing data deletion unit 407 searches the viewing data storage unit 413 based on the conditions (conditions of the range of the access period) notified from the viewing data analysis unit 402. Then, when data to be deleted is found, the viewing data deletion unit 407 deletes the data from the viewing data storage unit 413.

The tag request unit 408 includes a broadcast station ID of the program content notified from the viewing data analysis unit 402, a broadcast area ID, a date on which the program content was broadcast, and an hour, minute, and second when the program content was broadcast. Based on this, the tag database device 300 is requested for a tag attached to the corresponding program content.
The tag data receiving unit 409 receives the tag transmitted from the tag database device 300. Then, the tag data receiving unit 409 passes the tag information to the viewing data recording unit 405.

The analysis data recording unit 410 writes the analysis data passed from the viewing data analysis unit 402 into the analysis data storage unit 414. A specific example of the analysis data will be described later in detail.
The analysis data reading unit 411 reads analysis data from the analysis data storage unit 414 based on a request from the viewing data analysis unit 402. Then, the analysis data reading unit 411 passes the read analysis data to the analysis data display unit 412.
The analysis data display unit 412 transmits the analysis data passed from the analysis data reading unit 411 to the analysis client device 500 as visual data such as characters and graphs. Thus, the analysis data can be displayed on the analysis client device 500.

The viewing data storage unit 413 stores a viewing log. The viewing data storage unit 413 stores tag information in a form associated with the viewing log. Writing to the viewing data storage unit 413 is performed by the viewing data recording unit 405. The data in the viewing data storage unit 413 may be deleted by a signal from the viewing data deletion unit 407 in some cases.
The analysis data storage unit 414 stores analysis data as a result of the analysis processing by the viewing data analysis unit 402. The data stored in the analysis data storage unit 414 is read by the analysis data reading unit 411.

  FIG. 9 shows an example of the analysis result by the viewing data analysis unit 402, and is an example in which the viewing amount for each frame (for each time) is totaled. The illustrated analysis data is tabular data. The analysis data has items of a region ID, a broadcasting station ID, a frame, and a viewing amount. A broadcast service is specified by a combination of the area ID and the broadcast station ID. A frame is specified by information of year, month, day, hour, minute, second, and frame number. The viewing amount is a value obtained by counting the viewing log. That is, the viewing amount indicates the number of times the frame has been viewed (distributed) during the access period specified as the analysis condition.

  FIG. 10 shows an example of the analysis result by the viewing data analysis unit 402, and is an example in which the viewing amount for each tag is totaled. The illustrated analysis data is tabular data. This analysis data has items of tag and viewing amount. That is, the viewing amount here indicates the total number of times that the tag has been added to the frame viewed (distributed) in the access period specified as the analysis condition.

Next, a procedure of main processing in the viewing amount analyzing apparatus 1 will be described.
FIG. 11 is a flowchart illustrating a procedure of processing until the log collection / accumulation server device 200 collects and stores the viewing log of the program content generated by the log server device 100. The log collection and accumulation server device 200 performs a process of collecting, from the log server device 100, the viewing logs of the program contents distributed from all the distribution server devices 50 according to the procedure described below. Hereinafter, the procedure will be described along the flowchart.

First, in step S11, the viewing log generation unit 101 of the log server device 100 generates a viewing log. Specifically, when a viewer client device on the viewer side issues a distribution request for program content to the distribution server device 50, and the distribution server device 50 distributes the program content in accordance with this request, the viewing log generation unit 101 Generate a log. At this time, the distribution server device 50 transfers the recording of the distribution of the program content to the corresponding log server device 100. The viewing log generation unit 101 in the log server device 100 receiving this generates one viewing log for each frame. In other words, when the frame rate is 30 frames per second and the program content is viewed for one second in a certain viewing client device, the viewing log generation unit 101 generates 30 viewing logs accordingly. The data structure of the viewing log is as described above, and includes information on the broadcast date and time of the program content. This program content broadcast date and time is represented by a date (year, month, day), a time (hour, minute, second), and a frame number (0 to 29) within the second. The viewing log also includes information on the distribution date and time.
The viewing log generation unit 101 transfers the generated viewing log to the viewing log recording unit 102 and also to the viewing log transmission unit 103.

  Next, in step S12, the viewing log recording unit 102 writes the viewing log received from the viewing log generation unit 101 into the viewing log storage unit 104.

Next, in step S13, the viewing log transmission unit 103 transmits the viewing log received from the viewing log generation unit 101 to the log collection and accumulation server device 200 via the communication network.
When the process in step S13 ends, the log server device 100 returns to the process in step S11 to generate a viewing log.

  On the log collection / storage server device 200 side, the viewing log receiving unit 201 receives the viewing log transmitted from the log server device 100 in step S14. The viewing log receiving unit 201 passes the received viewing log to the viewing log recording unit 202.

Next, in step S15, the viewing log recording unit 202 writes the viewing log received from the viewing log receiving unit 201 into the viewing log storage unit 206.
When the process of step S15 ends, the log collection and accumulation server device 200 returns to the process of step S14, and further generates a viewing log.

  As described in the above flowchart, the log server device 100 and the log collection / storage server device 200 perform the operation of collecting and storing the viewing log regardless of the operation of the log analysis server device 400. Further, the log server device 100 and the log collection / storage server device 200 repeatedly perform the process of collecting the viewing log many times.

  Note that the timing at which the viewing log transmitting unit 103 transmits the viewing log in step S13 of FIG. 11 may be immediately after the viewing log transmitting unit 103 receives the viewing log from the viewing log generating unit 101, or may be a predetermined time. It may be at intervals. When transmitting at a predetermined time interval, the viewing log transmitting unit 103 temporarily stores the viewing log in a transmission buffer or the like until the transmission timing comes. However, in order to avoid that the viewing log stored on the log collection / storage server device 200 is in an old state, the viewing log transmitting unit 103 transmits the viewing log at least every few seconds or every tens of seconds, for example. It is desirable. Since the viewing log transmission unit 103 frequently transmits the viewing log, the storage state on the log collection / storage server device 200 side can be kept fresh. In addition, this allows the log analysis server device 400 to perform an analysis process based on the viewing log in a fresh state.

  Next, processing by the log analysis server device 400 will be described. FIG. 12, FIG. 13, FIG. 14, and FIG. 16 are flowcharts each showing a process according to the pattern of the analysis condition. Each of these flowcharts will be described in turn below.

  FIG. 12 is a flowchart of a process in which the log analysis server device 400 analyzes the viewing log based on the conditions of the start time and the end time designated by the analysis client device 500, and analyzes the viewing amount for each broadcast time of the program content. It is a flowchart which shows. Hereinafter, description will be given along this flowchart.

First, in step S41, the analysis condition receiving unit 401 receives the analysis condition transmitted from the analysis client device 500. The analysis condition includes information for specifying the broadcast service (in the present embodiment, the area ID and the broadcast station ID) and the access period. The condition of the access period is indicated by a start time and an end time. However, as described above, the specification of the end time may be omitted. Note that the analysis conditions sent from the analysis client device 500 are specified by the user (analysis user) of the analysis client device 500.
Note that the analysis condition receiving unit 401 passes the received information on the analysis condition to the viewing data analysis unit 402.

Next, in step S42, the viewing data analysis unit 402 determines, based on the analysis conditions, the broadcasting service (region ID and broadcasting station ID) and the access period (that is, the date and time of the distribution date and time) of the viewing log to be acquired. Minutes and seconds). Then, the viewing data analysis unit 402 notifies the viewing log requesting unit 403 of the information of the access period. Then, the viewing log request unit 403 requests the log collection / storage server device 200 for a viewing log that has been recorded within the notified access period based on the notified region ID and broadcast station ID.
The request from the viewing log request unit 403 is received by the viewing log request receiving unit 203 of the log collection and accumulation server device 200. Then, the viewing log reading unit 204 searches the viewing log storage unit 206 according to the received analysis condition. Then, the viewing log reading unit 204 reads a viewing log that matches the analysis condition from the viewing log storage unit 206. Then, the viewing log transmission unit 205 transmits all of the viewing logs read by the viewing log reading unit 204 to the log analysis server device 400.

Next, in step S43, the viewing log receiving unit 404 receives the viewing log transmitted from the log collection and accumulation server device 200. The viewing log received by the viewing log receiving unit 404 is passed to the viewing data recording unit 405.
Next, in step S44, the viewing data recording unit 405 writes all the received viewing logs into the viewing data storage unit 413.

Next, in step S45, the viewing data reading unit 406 reads the viewing log recorded in the viewing data storage unit 413, and passes it to the viewing data analysis unit 402. Then, the viewing data analysis unit 402 obtains the viewing amount for each time based on the passed viewing log. More specifically, the viewing data analysis unit 402 obtains the viewing amount by counting the number of viewing logs for each program content broadcast date and time. Here, the program content broadcast date and time is a frame unit, and is expressed in the format of “YYYY / MM / DD hh: mm: ss; nn” as described above. Then, the viewing data analysis unit 402 outputs the viewing amount specified by the area ID, the broadcasting station ID, and the frame as numerical data for each frame. Here, the data as a result of the analysis processing by the viewing data analysis unit 402 is the data described with reference to FIG. Note that the viewing data analysis unit 402 performs processing (sorting) to arrange the output data in chronological order as necessary.
Then, in step S46, the analysis data recording unit 410 writes the analysis data output by the viewing data analysis unit 402 into the analysis data storage unit 414.

Then, in step S47, the analysis data reading unit 411 reads the analysis data stored in the analysis data storage unit 414. The analysis data reading unit 411 passes the read analysis data to the analysis data display unit 412.
Next, in step S48, the analysis data display unit 412 transmits the obtained analysis data to the analysis client device 500 so that the analysis client device 500 can display the obtained analysis data. The display form of the analysis data at this time may be character information as it is (sequentially listed), or may be a graphical display such as a graph. As the graph, for example, a line graph, a bar graph, or the like representing a viewing amount in a time series may be used, but the form of the graph is not limited to these. Specifically, the analysis data display unit 412 transmits data in a format corresponding to a desired display format to the analysis client device 500. The data format is, for example, a text format, an image format, a hypertext format, or the like. The analysis client device 500 displays the received analysis data on its own screen or the like.

  If the end time of the access period specified by the analysis client device 500 is omitted as the analysis condition, the newly generated viewing log is displayed even after the above-described analysis processing by the log analysis server device 400. The log is stored in the log collection storage server 200. In this case, the log analysis server device 400 performs the log analysis process again at a predetermined timing as appropriate. Along with this, the analysis data display unit 412 causes the analysis client device 500 to display the analysis data as a result of the reprocessing. The frequency of the re-analysis process performed by the log analysis server device 400 may be, for example, the same as the frequency at which the viewing log is sent from the log server device 100 to the log collection / storage server device 200, or may be lower. Good.

  FIG. 13 shows that the log analysis server device 400 analyzes the viewing log based on the condition of the length of the period (the length from the present to the past) designated by the analysis client device 500, and analyzes the broadcast log for each broadcast time of the program content. 6 is a flowchart showing a procedure of a process of analyzing a viewing amount of a game. Hereinafter, description will be given along this flowchart.

First, in step S61, the analysis condition receiving unit 401 receives the analysis condition transmitted from the analysis client device 500. The analysis condition includes information for specifying a broadcast service and an access period. Here, the length of time is specified as a condition of the access period. In this method, the access point is started at a point in time that is a specified length from the present and ends at the end of the access period. For example, when “2 hours” is specified as the length of time, the access period is from 2 hours before to the current time. As will be described later, as time elapses, the start time and end time of the access period are reset based on the latest time.
Note that the analysis condition receiving unit 401 passes the received information on the analysis condition to the viewing data analysis unit 402.

Next, in step S62, the viewing data analysis unit 402 determines a broadcasting service (region ID and broadcasting station ID) and an access period of the viewing log to be acquired based on the analysis conditions.
Here, the length of time from the present to the start of the access period is specified as the analysis condition. Therefore, the viewing data analysis unit 402 sets the start time of the access period to the time obtained by subtracting the designated time from the current time. The viewing data analysis unit 402 sets the end time of the access period as the current time. For example, when the current time is “13:55:51 on April 09, 2016” and the designated time length is “2 hours”, the viewing data analysis unit 402 starts as follows. Determine the time and end time. That is, the start time is set to “11:55:51 on April 09, 2016”. The end time is set to "13:55:51 on April 09, 2016".
Then, the viewing data analysis unit 402 notifies the viewing log request unit 403 of the information of the access period and the information for specifying the service. Then, the viewing log requesting unit 403 requests the log collection / storage server device 200 for a viewing log that has been recorded within the specified access period of the specified broadcasting service.
The log collection / storage server 200 receives a request from the viewing log request unit 403, and the log collection / storage server 200 transmits a viewing log matching the analysis condition to the log analysis server 400 in FIG. Is the same as the processing in step S42.

Next, in step S63, the viewing log receiving unit 404 receives the viewing log transmitted from the log collection and accumulation server device 200. When the process proceeds from step S62 to S63, the viewing log receiving unit 404 receives the viewing log requested in step S62. When the process proceeds from step S70 to S63, the viewing log receiving unit 404 receives the viewing log requested in step S69.
The viewing log received by the viewing log receiving unit 404 is passed to the viewing data recording unit 405.

  Next, in step S64, the viewing data recording unit 405 writes all the received viewing logs into the viewing data storage unit 413. At this time, if the same data as the viewing log to be written already exists in the viewing data storage unit 413, the viewing data recording unit 405 corresponds to the viewing data recording unit 405 in order to avoid duplication. Does not write data. Duplication of the same viewing log can occur when this step is executed a plurality of times by a processing loop.

Next, in step S65, the viewing data reading unit 406 reads the viewing log recorded in the viewing data storage unit 413, and passes it to the viewing data analysis unit 402. Then, the viewing data analysis unit 402 obtains the viewing amount for each time based on the passed viewing log. Specifically, the viewing data analysis unit 402 obtains the viewing amount by counting the number of viewing logs for each program content broadcast date and time (frame).
The process of obtaining the viewing amount by counting the viewing log is the same as the process of step S45 in FIG. Also in this processing, the data as a result of the analysis processing by the viewing data analysis unit 402 is the data described with reference to FIG.
Then, in step S66, the analysis data recording unit 410 writes the analysis data output by the viewing data analysis unit 402 into the analysis data storage unit 414.

  Next, in step S67, the analysis data reading unit 411 reads the analysis data stored in the analysis data storage unit 414. The analysis data reading unit 411 passes the read analysis data to the analysis data display unit 412.

  Next, in step S68, the analysis data display unit 412 transmits the obtained analysis data to the analysis client device 500 so that the analysis client device 500 can display the obtained analysis data. The process of enabling the analysis client device 500 to display the analysis data here is the same as the process of step S48 in FIG.

Next, in step S69, the viewing data analysis unit 402 waits until a predetermined time has elapsed, and then resets the access period. That is, the viewing data analysis unit 402 sets the start time of the access period to a time obtained by subtracting the designated time from the current time at that time. Also, the end time of the access period is the current time at that time. Then, the viewing data analysis unit 402 notifies the viewing log request unit 403 of the information of the access period and the information for specifying the service. Then, the viewing log requesting unit 403 requests the log collection / storage server device 200 for a viewing log that has been recorded within the specified access period of the specified broadcasting service.
In response to this request, the log collection and accumulation server device 200 transmits a viewing log that matches the analysis condition to the log analysis server device 400. That is, the viewing log to be analyzed is updated as time elapses.

  Next, in step S70, the viewing data deletion unit 407 performs a process of deleting the viewing log outside the access period from the viewing data stored in the viewing data storage unit 413. That is, the viewing data deletion unit 407 deletes the old viewing log that holds the distribution date and time before the start time of the latest access period.

After the processing of this step ends, the log analysis server device 400 returns control to step S63 and repeats the processing.
When the termination condition is satisfied, the log analysis server device 400 may exit the processing loop and terminate. The end condition is, for example, completion of a predetermined number of repetitions, elapse of a predetermined processing time, arrival of a predetermined time, or an end instruction from outside the device. This is what was accepted.

Next, the analysis of the viewing amount for each tag by the log analysis server device 400 will be described.
FIG. 14 is a flowchart illustrating a procedure of a process in which the log analysis server device 400 analyzes the viewing log based on the conditions of the start time and the end time designated by the analysis client device 500 and analyzes the viewing amount for each tag. is there. Hereinafter, description will be given along this flowchart.

  First, the processing from steps S81 to S83 is the same as the processing from steps S41 to S43 in FIG. 12, and thus the description is omitted here.

Next, in step S84, the viewing data analysis unit 402 checks the information (area ID and broadcast ID) specifying the broadcasting service, which is described in the received viewing log, and broadcasts the program content broadcast date and time (year, month, day, hour, minute, second) , And the frame number) to the tag request unit 408. The tag requesting unit 408 requests the tag attached to the video frame to the tag database device 300 based on the information received from the viewing data analyzing unit 402.
The request for the tag data in this step is made for each of the acquired viewing logs. However, when there are a plurality of viewing logs related to a certain video frame, the request for the tag for the video frame may be collectively performed only once.
The request from the tag request unit 408 to the tag database device 300 is also arbitrary as follows. For example, a tag request from the tag request unit 408 to the tag database device 300 may be individually made for each video frame. A plurality of tag requests related to a plurality of video frames may be sent together from the tag request unit 408 to the tag database device 300.

The processing on the tag database device 300 side that has received the request from the tag request unit 408 in step S84 is as follows.
The tag data request receiving unit 301 receives the request transmitted from the log analysis server device 400 and notifies the tag data reading unit 302 of the information (information for specifying a video frame).
The tag data reading unit 302 searches the tag data storage unit 304 based on the notified information. As a result, the tag data reading unit 302 reads information of the tag added to the requested video frame from the tag data storage unit 304. The configuration of the data stored in the tag data storage unit 304 is as described with reference to FIG. Therefore, the tag data reading unit 302 reads a tag that matches the designated broadcast service and has a designated video frame that is equal to or longer than the start frame and equal to or shorter than the end frame. In some cases, a plurality of tags are added to one video frame. Therefore, the tag data reading unit 302 reads out all the tags corresponding to the video frame. The tag data reading unit 302 notifies the tag data transmitting unit 303 of the read tag information. Then, the tag data transmission unit 303 transmits the notified tag data to the log analysis server device 400.
When a request for a plurality of video frames is collectively received from the log analysis server device 400, the tag database device 300 reads out tag information for each of the video frames, and then reads the video frames. , And transmits the information of the tags attached to each of them to the log analysis server device 400 collectively.

  Next, in step S85, the tag data receiving unit 409 receives the tag data transmitted from the tag database device 300. The tag data receiving unit 409 passes the received tag data to the viewing data analyzing unit 402.

Next, in step S86, the viewing data analysis unit 402 transfers the viewing log and the information of the tag added to the video frame of the viewing log to the viewing data recording unit 405. The viewing data recording unit 405 writes the received viewing log and the information of the tag in the viewing data storage unit 413 in such a manner that they are associated with each other. As described above, a plurality of tags may be associated with one viewing log. The structure of the data of the viewing log associated with the tag will be described later with reference to FIG.
The viewing data analysis unit 402 and the viewing data recording unit 405 perform this processing for all target viewing logs.

Next, in step S87, the viewing data reading unit 406 reads the viewing log recorded in the viewing data storage unit 413 and passes it to the viewing data analysis unit 402. Then, the viewing data analysis unit 402 obtains the viewing amount for each tag based on the passed viewing log. Specifically, the viewing data analysis unit 402 obtains the viewing amount by counting the number of viewing logs for each tag. That is, the viewing amount of a certain tag is the number of viewing logs associated with the tag. Then, the viewing data analysis unit 402 outputs data of the viewing amount for each tag. Here, the data of the result of the analysis processing by the viewing data analysis unit 402 is the data described with reference to FIG. Note that the viewing data analysis unit 402 performs processing (sorting) to arrange the output data in the order of the viewing amount as necessary.
Next, in step S88, the analysis data recording unit 410 stores the analysis data output from the viewing data analysis unit 402 in the analysis data storage unit 414.

Next, in step S89, the analysis data reading unit 411 reads the analysis data stored in the analysis data storage unit 414. The analysis data reading unit 411 passes the read analysis data to the analysis data display unit 412.
Next, in step S90, the analysis data display unit 412 transmits the obtained analysis data to the analysis client device 500 so that the analysis client device 500 can display the obtained analysis data. Regarding the display method by the analysis data display unit 412, the various variations described in the processing in step S48 can be taken here.

  If the end time of the access period specified by the analysis client device 500 is omitted as the analysis condition, the newly generated viewing log is displayed even after the above-described analysis processing by the log analysis server device 400. The log is stored in the log collection storage server 200. In this case, the log analysis server device 400 performs the log analysis process again at a predetermined timing as appropriate. Along with this, the analysis data display unit 412 causes the analysis client device 500 to display the analysis data as a result of the reprocessing. The frequency of the re-analysis process performed by the log analysis server device 400 may be, for example, the same as the frequency at which the viewing log is sent from the log server device 100 to the log collection / storage server device 200, or may be lower. Good.

FIG. 15 is a schematic diagram illustrating a data configuration when the viewing log stored in the viewing data storage unit 413 is associated with tag information. This data is written in the viewing data storage unit 413 in the process of step S86 in FIG.
The viewing log shown here holds data for associating with the tag list in addition to the data of the viewing log described in FIG. The tag list is a structure in which information of a plurality of tags is arranged. The viewing log shown in the figure shows that three tags “cooking”, “curry”, and “chicken” are added to the video frame represented by the viewing log.

  FIG. 16 shows that the log analysis server device 400 analyzes the viewing log based on the condition of the length of the period (the length from the present to the past) designated by the analysis client device 500, and determines the viewing amount for each tag. It is a flowchart which shows the procedure of a process to analyze. Hereinafter, description will be given along this flowchart.

First, the processing from steps S101 to S102 is the same as the processing from steps S61 to S62 described in FIG.
Next, in step S103, the viewing log receiving unit 404 receives the viewing log transmitted from the log collection and accumulation server device 200. When the process proceeds from step S102 to S103, the viewing log receiving unit 404 receives the viewing log requested in step S102. When the process proceeds from step S112 to step S103, the viewing log receiving unit 404 receives the viewing log requested in step S111.
The viewing log received by the viewing log receiving unit 404 is passed to the viewing data analysis unit 402.

  Next, in step S104, the viewing data analysis unit 402 checks the information (area ID and broadcast ID) for specifying the broadcasting service, which is described in the received viewing log, and broadcasts the program content broadcast date / time (year / month / day, hour / minute / second / second). , And the frame number) to the tag request unit 408. The tag requesting unit 408 requests the tag attached to the video frame to the tag database device 300 based on the information received from the viewing data analyzing unit 402. Note that the processing in this step is the same as the processing in step S84 in FIG. 14, and a detailed description thereof will be omitted here. The processing on the tag database device 300 side that has received the request from the tag request unit 408 is the same as the processing described in step S84 in FIG. 14, and thus detailed description is omitted here.

  Next, in step S105, the tag data receiving unit 409 receives the tag data transmitted from the tag database device 300. The tag data receiving unit 409 passes the received tag data to the viewing data analyzing unit 402.

  Next, in step S106, the viewing data analysis unit 402 passes the viewing log and the information of the tag added to the video frame of the viewing log to the viewing data recording unit 405. The viewing data recording unit 405 writes the received viewing log and the information of the tag in the viewing data storage unit 413 in such a manner that they are associated with each other. The processing in this step is the same as the processing in step S86 in FIG. The data of the viewing log associated with the tag information is as described with reference to FIG.

Next, in step S107, the viewing data reading unit 406 reads the viewing log recorded in the viewing data storage unit 413, and passes it to the viewing data analysis unit 402. Then, the viewing data analysis unit 402 obtains the viewing amount for each tag based on the passed viewing log. Since the processing in this step is the same as the processing in step S87 in FIG. 14, detailed description is omitted here.
Next, in step S108, the analysis data recording unit 410 stores the analysis data output from the viewing data analysis unit 402 in the analysis data storage unit 414.

  Next, in step S109, the analysis data reading unit 411 reads the analysis data stored in the analysis data storage unit 414. The analysis data reading unit 411 passes the read analysis data to the analysis data display unit 412.

  Next, in step S110, the analysis data display unit 412 transmits the obtained analysis data to the analysis client device 500 so that the analysis client device 500 can display the obtained analysis data. The process of enabling the analysis client device 500 to display the analysis data here is the same as the process of step S48 in FIG.

  Next, in step S111, the viewing data analysis unit 402 waits until a predetermined time has elapsed, and then resets the access period. Then, the viewing data analysis unit 402 notifies the viewing log request unit 403 of the information of the access period and the information for specifying the service. Then, the viewing log requesting unit 403 requests the log collection / storage server device 200 for a viewing log that has been recorded within the specified access period of the specified broadcasting service. The process in this step is the same as the process in step S69 in FIG. Then, similarly to step S69, the log collection / storage server device 200 also transmits the viewing log that matches the analysis condition to the log analysis server device 400. That is, the viewing log to be analyzed is updated as time elapses.

  Next, in step S112, the viewing data deletion unit 407 performs a process of deleting the viewing log outside the access period from the viewing data stored in the viewing data storage unit 413. The processing in this step is the same as the processing in step S70 in FIG. That is, the viewing data deletion unit 407 deletes the old viewing log that holds the distribution date and time before the start time of the latest access period.

After the processing of step S112, the log analysis server device 400 returns control to step S103 and repeats the processing.
When the termination condition is satisfied, the log analysis server device 400 may exit the processing loop and terminate. The end condition is, for example, completion of a predetermined number of repetitions, elapse of a predetermined processing time, arrival of a predetermined time, or an end instruction from outside the device. This is what was accepted.

  As described above, in the present embodiment, the number of viewing logs is used as it is as the viewing amount. Thus, the viewing amount analysis device 1 can analyze the viewing amount according to the number of frames actually viewed.

[Second embodiment]
Next, a second embodiment will be described. The description of the items described in the previous embodiment may be omitted here. Here, the description will focus on matters specific to the present embodiment.
The viewing amount analysis device according to the second embodiment includes a log analysis server device 800 instead of the log analysis server device 400 in the first embodiment.

  FIG. 17 is a block diagram illustrating a schematic functional configuration of the log analysis server device 800 according to the present embodiment. As shown, the log analysis server device 800 includes an analysis condition receiving unit 401, a viewing data analysis unit 402, a viewing log requesting unit 403, a viewing log receiving unit 404, a viewing data recording unit 405, and a reading of the viewing data. Section 406, viewing data erasing section 407, tag requesting section 408, tag data receiving section 409, analysis data recording section 410, analysis data reading section 411, analysis data display section 412, and viewing data storage section 413. , An analysis data storage unit 414, and a viewing amount conversion unit 802. A feature of the log analysis server device 800 is that the log analysis server device 800 includes a viewing amount conversion unit 802.

The viewing amount conversion unit 802 converts the number of viewing logs into a viewing amount by a predetermined process when the viewing data analysis unit 402 analyzes the viewing data. Specifically, the viewing amount conversion unit 802 converts the number of viewing logs (the number of frames) into a value of the number of frames at a reference frame rate or a value of a unit time having a predetermined length. is there.
In the first embodiment, the viewing amount is the number of viewing logs, but the premise is that the frame rates of all program contents are the same. The frame rate is the number of frames per unit time of the program content, and is a numerical value expressed in units of, for example, fps (frames per second). A typical frame rate for a program such as a television in Japan is 30 frames per second. However, a situation in which the frame rate differs for each program content may be assumed. In such a situation, it may be considered that it is more appropriate to measure the viewing amount by the length of viewing time rather than by the number of viewing logs, that is, the number of frames. The viewing amount conversion unit 802 converts the number of collected viewing logs (that is, the number of frames of the program content) into a viewing time length. Details of the processing by the viewing amount conversion unit 802 will be described later.

FIG. 18 is a schematic diagram showing the data configuration of the viewing log in the present embodiment. As shown in the figure, the viewing log is data including distribution destination identification information, distribution date and time, program content broadcast date and time, frame rate, region ID, and broadcast station ID. The data shown is one viewing log, and corresponds to viewing of one frame. The feature of the illustrated viewing log is that it has an item of frame rate. In the viewing log, the frame rate data is the frame rate when the program content targeted by the viewing log is distributed, and holds the above-described numerical value expressed in units of frames per second (fps). That is, the frame rate is a value representing the number of viewing logs per unit time for viewed program content. In the illustrated example, the frame rate of the viewing log on the first line is 30 frames per second, and the frame rate of the viewing log on the second line is 60 frames per second. Note that the frame rate may be a value other than 30 frames per second or 60 frames per second.
That is, in the present embodiment, the viewing log generation unit 101 of the log server device 100 generates the viewing log including frame rate information indicating the number of frames per unit time when the frame is distributed.

  In the present embodiment, the distribution server device 50 passes information on the frame rate of the viewed program content to the log server device 100. Then, the log server device 100 generates a viewing log including the above-mentioned frame rate information, and transfers the generated viewing log to the log collection / storage server device 200. The log collection / storage server device 200 collects a viewing log including frame rate information. Then, the log analysis server device 400 performs an analysis process on the viewing log including the information on the frame rate.

  FIG. 19 is a schematic diagram illustrating a data configuration when the log analysis server device 400 associates a viewing log to be analyzed with tag information. This data is written in the viewing data storage unit 413 in the processing of step S86 in FIG. 14 and the processing in step S106 of FIG. 16 described in the previous embodiment. The viewing log shown here holds data for associating with the tag list in addition to the data of the viewing log described with reference to FIG. The tag list is a structure in which information of a plurality of tags is arranged. The viewing log shown in the figure indicates that two tags “sports” and “soccer” are added to the video frame represented by the viewing log.

  Next, details of the processing performed by the viewing amount conversion unit 802 based on the data shown in FIG. 18 or FIG. 19 will be described. As described above, the viewing amount conversion unit 802 converts the number of viewing logs into the value of the viewing amount. The viewing amount calculated by the viewing amount conversion unit 802 is one of (1) the number of frames assuming a reference frame rate, and (2) the number of minute unit times. Each case is described below.

(1) Number of Frames assuming Reference Frame Rate In this case, assuming a reference frame rate (for example, 30 fps), the viewing amount conversion unit 802 determines the number of viewing logs (the number of frames actually viewed). Is calculated based on the reference frame rate. For a certain program content, the viewing amount is calculated by the following equation 1.
Formula 1: Viewing amount = Number of viewing logs × (Reference frame rate / Frame rate of the viewing log)
For example, when the reference frame rate is 30 fps and the frame rate recorded in the viewing log is 60 fps, if the number of viewing logs is 600 (for 10 seconds), the viewing amount calculated by Expression 1 is 300. It is.

(2) Number of minute unit times In this case, the length L of the unit time is appropriately determined. L is, for example, 1 second, 1/10 second, 1/30 second, 1/1000 second, or the like. Then, the viewing amount conversion unit 802 calculates the number of corresponding unit times based on the number of viewing logs (the number of frames actually viewed). For a certain program content, the viewing amount is calculated by the following equation (2).
Formula 2: Viewing amount (number of unit time) = Number of viewing logs / (L × frame rate of the viewing log)
For example, when L is 1/10 second and the frame rate recorded in the viewing log is 30 fps, if the number of viewing logs is 600 (for 20 seconds), the viewing amount calculated by Expression 2 is 200. Note that the viewing amount calculated by Expression 2 does not need to be an integer.

  The viewing data analysis unit 402 in the present embodiment performs the same analysis processing as in the previous embodiment. However, the viewing amount analyzed by the viewing data analysis unit 402 in the present embodiment is the viewing amount after being converted by the viewing amount conversion unit 802. In the present embodiment, as described above, even when program contents having different frame rates are distributed, the viewing amount conversion unit 802 converts the number of viewing logs into a standard viewing amount. Here, the standard viewing amount is the number of frames when a reference frame rate is assumed, or the number of unit times of a predetermined length (L seconds). Thus, the log analysis server device 400 can analyze the viewing amount that is proportional to the length of the viewing time regardless of the difference in the frame rate for each program content.

  The functions of each unit included in the viewing amount analysis device in the above-described embodiment may be realized by a computer. In that case, a program for implementing these functions may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read and executed by a computer system. Here, the “computer system” includes an OS and hardware such as peripheral devices. The “computer-readable recording medium” refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, and a CD-ROM, and a storage device such as a hard disk built in a computer system. Further, a "computer-readable recording medium" means that a program is dynamically held for a short time, such as a communication line for transmitting a program through a network such as the Internet or a communication line such as a telephone line. Such a program may include a program that holds a program for a certain period of time, such as a volatile memory in a computer system serving as a server or a client in that case. Further, the above-mentioned program may be for realizing a part of the above-mentioned functions, or may be for realizing the above-mentioned functions in combination with a program already recorded in a computer system.

As described above, a plurality of embodiments have been described, but the present invention can be further implemented in the following modified examples.
[Modification 1]
For example, in the first embodiment and the second embodiment, the viewing amount analysis device analyzes the viewing amount when distributing content including video. However, the viewing amount analysis device may analyze the viewing amount of the content including no video. The content that does not include a video is a content based on only audio (for example, a content of a radio program), a content based on data broadcasting, a content based on text data such as subtitles, and the like. In the case of content using only audio, the viewing amount is represented by a numerical value proportional to the total time that the content has been heard. In the case of a content including a visual expression other than a video, the viewing amount is represented by a numerical value proportional to the total viewing time of the content. The viewing amount may be represented by the number of “frames” (the frame period is, for example, 1/30 second) described in the first embodiment, or the unit time (length is L seconds) described in the second embodiment. The viewing amount may be represented by the number.

[Modification 2]
The log analysis server device 400 may perform an analysis process based on other analysis conditions other than the analysis conditions used in the first embodiment and the second embodiment. For example, when analyzing the viewing amount for each tag, tags to be analyzed may be narrowed down based on given conditions. Further, for example, not only the analysis of the viewing amount for each time (for each frame) and the analysis of the viewing amount for each tag, but also a cross tabulation based on a plurality of data items may be performed.

[Modification 3]
In the first and second embodiments, an independent viewing log is generated for each frame. Instead, the viewing log may be generated and analyzed in another form of equivalent data. As an example, information on a distribution start time and a distribution end time (both of which are frame units) and a corresponding program content broadcast date and time (start time and end time) of a certain broadcast service at a certain distribution destination are written in a viewing log. It may be. Even on the basis of such a viewing log, the log analysis server device 400 can perform the same processing as the analysis processing described in the first embodiment and the second embodiment.

  As described above, the embodiments of the present invention have been described in detail with reference to the drawings. However, the specific configuration is not limited to the embodiments, and includes a design and the like within a range not departing from the gist of the present invention.

  INDUSTRIAL APPLICABILITY The present invention is particularly applicable to a content distribution business, a business of providing information on a viewing amount of a content, a business of analyzing how a content is viewed, and the like.

1 viewing amount analysis device 50, 50-1, 50-2, ..., 50-X distribution server device 100, 100-1, 100-2, ..., 100-X log server device 101 viewing log generation unit 102 viewing log recording unit 103 viewing log transmission unit 104 viewing log storage unit 200 log collection and accumulation server device 201 viewing log reception unit 202 viewing log recording unit 203 viewing log request reception unit 204 viewing log reading unit 205 viewing log transmission unit 206 viewing log Storage unit 300 Tag database device 301 Tag data request reception unit 302 Tag data read unit 303 Tag data transmission unit 304 Tag data storage unit 400 Log analysis server device 401 Analysis condition reception unit 402 Viewing data analysis unit 403 Viewing log request unit 404 Viewing log Receiving section 405 viewing data recording section 406 viewing data reading section 40 Viewing data deleting unit 408 Tag requesting unit 409 Tag data receiving unit 410 Analysis data recording unit 411 Analysis data reading unit 412 Analysis data display unit 413 Viewing data storage unit 414 Analysis data storage unit 500 Analysis client device 800 Log analysis server device 802 Viewing amount Conversion section

Claims (5)

A viewing log generating unit that generates a viewing log representing a frame distributed for program content distributed via the communication network for each distribution destination;
A viewing log storage unit that collects and stores the viewing log generated by the viewing log generation unit,
A viewing data analysis unit that determines a viewing amount for each frame distributed by reading the viewing log from the viewing log storage unit,
A viewing amount analysis device comprising: The program content is already broadcasted program content,
The viewing log generation unit generates the viewing log including information on the broadcast date and time for each frame,
The viewing amount analysis device according to claim 1, wherein: The apparatus further includes a tag data storage unit that stores information of a tag provided for each frame,
The viewing data analysis unit adds the information of the tag to the information of the frame represented by the viewing log based on the relationship between the frame and the tag stored in the tag data storage unit. Find the quantity,
The viewing amount analyzing device according to claim 1 or 2, wherein: The viewing log generation unit is for generating the viewing log including information on a frame rate indicating the number of frames per unit time when the frame is distributed,
A viewing amount conversion unit that converts the number of frames when the frames are distributed into a value of the number of frames at a reference frame rate or a value of the number of unit times having a predetermined length,
The viewing data analysis unit obtains the viewing amount using a result converted by the viewing amount conversion unit,
The viewing amount analysis device according to any one of claims 1 to 3, wherein: Computer
A viewing log generation unit that generates a viewing log representing a frame distributed for the program content distributed via the communication network for each distribution destination,
A viewing log storage unit that collects and stores the viewing log generated by the viewing log generation unit,
A viewing data analysis unit that determines a viewing amount for each frame distributed by reading the viewing log from the viewing log storage unit,
Program to function as.

Images