JP6268245B1 - Program and information distribution apparatus - Google Patents

Abstract

A program and an information distribution apparatus are provided that notify an external device that an event that is set to an inline moving image has occurred in a user terminal that is restricted from reproducing inline moving images. According to an embodiment, a program for managing an inline video embedded in a Web page causes a processor to acquire the inline video and capture a frame while advancing the playback time of the inline video at a predetermined interval. The captured frame is displayed, the occurrence of an event set in the inline moving image is detected, and the external device is notified of the occurrence of the event. [Selection] Figure 4

Description

  Embodiments described herein relate generally to a program and an information distribution apparatus related to moving image distribution on the Internet or the like.

  Some user terminals restrict the playback of inline moving images embedded in Web pages as a function restriction of the OS or browser. For example, such a user terminal displays a thumbnail of an inline moving image, and when the thumbnail is clicked, reproduces the moving image with a dedicated application.

  For such a user terminal, an inline moving image may be reproduced in a Web page using a Canvas tag. However, conventionally, when a moving image is reproduced in a Campas tag, there is a problem that it is impossible to notify an external device that an event set to an inline moving image has occurred in the user terminal.

JP 2014-203410 A

  In order to solve the above-described problems, a program and an information distribution device are provided that notify an external device that an event set to an inline moving image has occurred in a user terminal that is restricted from reproducing inline moving images.

  According to the embodiment, a program for managing an inline video embedded in a web page causes a processor to acquire the inline video, capture a frame while advancing the playback time of the inline video at a predetermined interval, and The frame is displayed, an event set in the inline moving image is detected, and an external device is notified that the event has occurred.

  According to the embodiment, the moving image management program sets and captures an inline moving image in a non-displayed Video tag, and causes the Canvas tag to describe the captured frame. Further, the moving image management program causes the above operation to be continuously performed while advancing the playback time of the inline moving image. As a result, the moving image management program can virtually display an inline moving image in the Canvas tag. Therefore, the moving image management program can virtually display the inline moving image even when the reproduction of the inline moving image is limited.

  The moving image management program also determines whether an event set for an inline moving image has occurred. Further, when it is determined that an event has occurred, the moving image management program can notify an external device that the event has occurred. As a result, even when there is a restriction on the reproduction of the inline moving image, the external device can be notified of the occurrence of an event set in the inline moving image.

FIG. 1 is a block diagram illustrating a configuration example of a moving image distribution system according to the embodiment. FIG. 2 is a block diagram illustrating a configuration example of the CDN according to the embodiment. FIG. 3 is a block diagram illustrating a configuration example of the user terminal according to the embodiment. FIG. 4 is a sequence diagram illustrating an operation example of the moving image distribution system according to the embodiment. FIG. 5 is a flowchart illustrating an operation example of the user terminal according to the embodiment. FIG. 6 is a flowchart illustrating an operation example of the user terminal according to the embodiment. FIG. 7 is a flowchart illustrating an operation example of the user terminal according to the embodiment. FIG. 8 is a flowchart illustrating an operation example of the user terminal according to the embodiment.

Hereinafter, embodiments will be described with reference to the drawings.
FIG. 1 is a diagram illustrating a configuration example of the moving image distribution system 100.
The moving image distribution system 100 distributes a moving image (inline moving image) that is reproduced in a Web page displayed by the browser of the user terminal 4. Here, it is assumed that the moving image distribution system 100 distributes an advertising moving image as an inline moving image. In addition, the moving image distribution system 100 detects that an event set for an inline moving image has occurred based on communication from the user terminal 4.

  As shown in FIG. 1, the moving image distribution system 100 includes an ad server 1, a Web server 2, a CDN (Contents Delivery Network) 3, a user terminal 4, and the like. The moving image distribution system 100 connects the ad server 1, the web server 2, the CDN 3, and the user terminal 4 to each other through a communication network 5 such as the Internet.

  The ad server 1 distributes to the user terminal 4 video information indicating a link destination for downloading an inline video (advertisement video) and an event notification destination set in the inline video via the communication network 5. The ad server 1 stores in advance moving image information corresponding to an inline moving image. The ad server 1 receives a request for moving image information from the user terminal 4. The ad server 1 transmits moving image information to the user terminal 4 as a response to the request. The ad server 1 may store a plurality of pieces of moving image information. Further, the ad server 1 may update the moving image information as appropriate. The moving image information will be described in detail later.

  Further, the ad server 1 receives a notification indicating that an event has occurred from the user terminal 4. Here, when the ad server 1 receives a request for a predetermined URL from the user terminal 4, the ad server 1 recognizes that an event corresponding to the URL has occurred.

  For example, the ad server 1 transmits VAST XML to the user terminal 4 in accordance with VAST (Video Ad-Serving Template). Further, the ad server 1 accepts notification of the occurrence of an event from the user terminal 4 according to, for example, VAST.

  The Web server 2 transmits Web pages (such as html and images) to the user terminal 4 through the communication network 5. The web server 2 stores web pages in advance. The web server 2 receives a web page request from the user terminal 4. The Web server 2 transmits a Web page as a response to the request to the user terminal 4.

  CDN 3 (information distribution device) transmits an inline moving image to user terminal 4. Also, the CDN 3 transmits a program (moving image management program) for displaying an inline moving image and notifying the occurrence of an event to the user terminal 4. The configuration of CDN3 will be described in detail later.

  The user terminal 4 is a terminal possessed by a general user. The user terminal 4 starts a browser based on a user operation (input). The user terminal 4 receives an input of a URL on the browser and displays a Web page corresponding to the URL. The configuration of the user terminal will be described in detail later.

  The communication network 5 connects the ad server 1, the Web server 2, the CDN 3, and the user terminal 4 so that they can communicate with each other. The communication network 5 is, for example, the Internet. The ad server 1, the Web server 2, the CDN 3, and the user terminal 4 access the communication network 5 by wire or wireless.

  Note that the ad server 1, the web server 2, and the CDN 3 may be configured by one information processing apparatus. Further, any two of the ad server 1, the web server 2, and the CDN 3 may be configured by one information processing apparatus.

Next, CDN3 will be described.
FIG. 2 is a block diagram illustrating a configuration example of the CDN 3.
In the configuration example illustrated in FIG. 2, the CDN 3 includes a CPU 11, a ROM 12, a RAM 13, an NVM 14, a communication unit 15, and the like as basic configurations. These units are connected to each other via a data bus. Note that the CDN 3 may have a configuration as required in addition to the configuration shown in FIG. 2 or may exclude a specific configuration.

  The CPU 11 has a function of controlling the operation of the entire CDN 3. The CPU 11 may include an internal cache and various interfaces. The CPU 11 implements various processes by executing programs stored in advance in the internal memory, the ROM 12 or the NVM 14.

  Note that some of the various functions realized by the CPU 11 executing the program may be realized by a hardware circuit. In this case, the CPU 11 controls functions executed by the hardware circuit.

  The ROM 12 is a non-volatile memory in which a control program and control data are stored in advance. The control program and control data stored in the ROM 12 are incorporated in advance according to the specifications of the CDN 3. For example, the ROM 12 stores a program (for example, BIOS) for controlling the circuit board of the CDN 3.

  The RAM 13 is a volatile memory. The RAM 13 temporarily stores data being processed by the CPU 11. The RAM 13 stores various application programs based on instructions from the CPU 11. The RAM 13 may store data necessary for executing the application program, an execution result of the application program, and the like.

  The NVM 14 is a nonvolatile memory capable of writing and rewriting data. The NVM 14 is configured by, for example, a hard disk, SSD, EEPROM (registered trademark), flash memory, or the like. The NVM 14 stores a control program, an application, and various data according to the operation usage of the CDN 3.

The NVM 14 includes a storage area 14a for storing inline moving images and a storage area 14b (storage unit) for storing moving image management programs.
The storage area 14a stores inline moving images in advance. The storage area 14a may store a plurality of inline moving images. Further, the inline moving image may be updated as appropriate.
The moving image management program stored in the storage area 14b will be described in detail later.

  The communication unit 15 is an interface for transmitting and receiving data to and from the user terminal 4 through the communication network 5. The communication unit 15 is an interface that supports LAN connection, for example.

  The CDN 3 may further include another configuration such as an operation unit or a display unit. Further, the CDN 3 may delete an unnecessary configuration.

  The CPU 11 transmits the moving image management program to the user terminal 4 through the communication unit 15 (transmission processing unit). For example, the CPU 11 transmits a moving image management program to the user terminal 4 as a response to the request from the user terminal 4.

Next, the user terminal 4 will be described.
FIG. 3 is a block diagram illustrating a configuration example of the user terminal 4.

  In the configuration example illustrated in FIG. 3, the user terminal 4 includes a CPU 21 (processor), a ROM 22, a RAM 23, an NVM 24, a communication unit 25, an operation unit 26, a display unit 27, and the like as a basic configuration. These units are connected to each other via a data bus. Note that the user terminal 4 may include a configuration as necessary in addition to the configuration illustrated in FIG. 3 or may exclude a specific configuration.

  The CPU 21 has a function of controlling the operation of the entire user terminal 4. The CPU 21 executes a program composed of codes that realize various functions.

The ROM 22 is a nonvolatile memory in which a control program and control data are stored in advance.
The RAM 23 is a volatile memory.

  The NVM 24 is a nonvolatile memory that can write and rewrite data.

  The communication unit 25 is an interface for transmitting / receiving data to / from an external device such as the ad server 1, the Web server 2, or the CDN 3 through the communication network 5.

  Various operation instructions are input to the operation unit 26 by an operator of the user terminal 4. The operation unit 26 transmits an operation instruction signal input to the operator to the CPU 21. The operation unit 26 is, for example, a keyboard, a numeric keypad, and a touch panel.

The display unit 27 is a display device that displays various information under the control of the CPU 21. The display unit 27 is, for example, a liquid crystal monitor. When the operation unit 26 is configured with a touch panel or the like, the display unit 27 may be formed integrally with the operation unit 26.
The user terminal 4 is, for example, a desktop PC, a notebook PC, a smartphone, a tablet PC, or a wearable terminal.

  The CPU 21 cannot reproduce the inline moving image within the Web page due to the function limitation of the OS or the browser. For example, the CPU 21 displays a thumbnail of the inline moving image in an area where the inline moving image is displayed in the web page. For example, when detecting a touch on a thumbnail or the like through the operation unit 26, the CPU 21 activates a predetermined moving image reproduction application and reproduces the moving image with the application.

Next, the moving image information will be described.
The video information is information for setting a notification destination corresponding to an event set for an inline video. That is, the moving image information sets a notification destination for each event. Here, the notification destination is a URL that notifies that an event has occurred. The URL is a link to the ad server 1. Further, since the inline video is an advertising video, the event is set to the advertising video.

  For example, an event corresponding to an inline video includes an event synchronized with the playback time of the inline video (synchronous event) or an event not synchronized with the playback time of the inline video (asynchronous event).

  For example, a synchronization event is that the playback time has elapsed to a predetermined rate. For example, a synchronization event is that an inline video has been played 0% (ie, the start of playback), 25%, 50%, 75%, or 100%. In this case, the moving image information indicates, for example, a list in which a percentage of moving image reproduction is associated with a URL as a notification destination.

  For example, an asynchronous event is an event related to a user operation. For example, the asynchronous event is an inline video pause, resume, mute, unmute or full screen. In this case, the moving image information indicates, for example, a list in which user operations are associated with URLs as notification destinations.

  Here, it is assumed that the synchronous event and the asynchronous event are events defined by VAST. For example, the moving image information indicates a list in which events defined by VAST are associated with URLs. In addition, the moving image information is incorporated into VAST XML or the like.

Note that an event need not be defined by VAST. The event is not limited to a specific content.
In the video information, a link destination for downloading an inline video (advertisement video) is set.

Next, the moving image management program will be described.
The moving image management program causes the CPU 21 of the user terminal 4 to display an inline moving image and notifies the ad server 1 that an event has occurred. For example, the moving image management program is described in JavaScript (registered trademark).

The moving image management program causes the CPU 21 of the user terminal 4 to realize the following functions.
CPU21 implement | achieves the function (reproduction | regeneration function) which reproduces | regenerates an inline moving image within a web page according to a moving image management program. First, the CPU 21 generates a non-displayed video tag. The CPU 21 further generates a Canvas tag. Further, the CPU 21 acquires an inline moving image from the CDN 3. The CPU 21 sets the inline moving image acquired in the Video tag.

  The CPU 21 captures the frame of the inline moving image at a predetermined reproduction time using the Video tag. The CPU 21 displays the captured image on the Canvas tag. When the CPU 21 displays an image on the Canvas tag, the CPU 21 advances the reproduction time by a predetermined time at a predetermined interval. By repeating the above operation, the CPU 21 can continuously display the frames of the inline moving image with the reproduction time shifted in the Canvas tag, and make it appear as if the inline moving image is being reproduced.

  Further, the CPU 21 realizes a function (detection function) for detecting that an event has occurred in accordance with the moving image management program. For example, the CPU 21 determines whether a synchronization event has occurred. For example, the CPU 21 calculates the ratio (percentage) at which the inline moving image is reproduced from the reproduction time of the frame captured by the Canvas tag. The CPU 21 determines whether the calculated ratio exceeds a predetermined threshold value for each synchronization event. When the CPU 21 determines that the calculated ratio has exceeded a certain synchronization event threshold, the CPU 21 determines that the event has occurred.

  For example, the CPU 21 determines whether an asynchronous event has occurred. For example, the CPU 21 determines whether an event related to a user operation has occurred. That is, the CPU 21 determines whether an event such as pause, restart, mute, unmute or full screen of an inline moving image has occurred.

  Further, the CPU 21 implements a function (notification function) for notifying the ad server 1 that an event has occurred according to the moving image management program. For example, the CPU 21 receives moving image information (for example, VAST XML) from the ad server 1 before starting detection of an event.

  The CPU 21 determines whether an event has occurred. When determining that an event has occurred, the CPU 21 notifies the ad server 1 that the event has occurred based on the moving image information. That is, the CPU 21 refers to the moving image information, acquires a URL corresponding to the event that has occurred, and transmits a predetermined request to the acquired URL.

The moving image management program causes the CPU 21 to realize a playback function, a detection function, and a notification function in parallel. That is, the moving image management program detects the occurrence of an event while capturing the frame of the inline moving image in the canvas tag, and notifies the ad server 1 that the detected event has occurred. Other functions may be further realized. Further, the moving image management program may be written in a language other than JavaScript.

Next, an operation example of the moving image distribution system 100 will be described.
FIG. 4 is a sequence diagram illustrating an operation example of the moving image distribution system 100.
Here, it is assumed that the user of the user terminal 4 tries to browse a predetermined Web page by inputting a URL in the browser of the user terminal 4 or clicking a predetermined link. In addition, the Web page includes an inline video (advertisement video).

  First, the user terminal 4 transmits a web page request to the web server 2 (S11). When receiving a web page request from the user terminal 4, the web server 2 transmits a web page (such as html) to the user terminal 4 as a response to the request (S12). Here, it is assumed that the html of the Web page includes a script for acquiring the moving image management program from the CDN 3.

  When receiving the Web page, the user terminal 4 transmits a request for the moving image management program to the CDN 3 according to the script of the Web page (S13). When receiving the request for the moving image management program, the CDN 3 transmits the moving image management program to the user terminal 4 as a response to the request (S14).

  When receiving the moving picture management program, the user terminal 4 transmits a request for moving picture information (for example, VAST XML) to the ad server 1 according to the moving picture management program (S15). When the ad server 1 receives the request for the moving image information, the ad server 1 transmits the moving image information to the user terminal 4 as a response to the request (S16).

  When receiving the moving image information, the user terminal 4 generates a Video tag and a Canvas tag according to the moving image management program (S17). Note that the generation timing of the Video tag and the Canvas tag is not limited to this timing, and can be any timing after reception of the moving image management program. When the Video tag and the Canvas tag are generated, the user terminal 4 transmits an inline video request to the CDN 3 based on the video information (S18). When the CDN 3 receives the request for the inline moving image, the CDN 3 transmits the inline moving image to the user terminal 4 as a response to the request (S19).

  When receiving the inline moving image, the user terminal 4 sets the inline moving image in the Video tag, and draws the capture of the frame of the inline moving image in the Canvas tag (S20). The user terminal 4 continues to describe the frame of the inline moving image in the Canvas tag while advancing the playback time of the inline moving image in the Video tag.

  When the capture is depicted, the user terminal 4 determines whether an event has occurred. When detecting that an event has occurred (S21), the user terminal 4 transmits a request to the URL corresponding to the event based on the moving image information (S22).

Next, an operation example of the user terminal 4 will be described.
FIG. 5 is a flowchart for explaining an operation example of the user terminal 4.
First, the CPU 21 of the user terminal 4 acquires the URL of the Web page through the operation unit 26 (S31). When acquiring the URL of the Web page, the CPU 21 acquires the Web page from the Web server 2 (S32) (corresponding to S11 and S12).

  When the web page is acquired, the CPU 21 displays an inline moving image (S33) (corresponding to S13 to S22). When the inline moving image is displayed, the CPU 21 displays a web page (S34).

  When the Web page is displayed, the CPU 21 ends the operation.

  Note that the CPU 21 continues S33 even after the Web page is displayed. That is, the CPU 21 continues to capture the inline moving image and draws it on the Canvas tag. In addition, the CPU 21 continues to detect the occurrence of an event. Further, the CPU 21 may display content other than the inline moving image on the Web page first.

Next, the display of inline moving images (S33) will be described.
FIG. 6 is a flowchart for explaining an operation example of displaying an inline moving image (S33).

  First, the CPU 21 acquires a moving image management program from the CDN 3 according to the html of the Web page (S41) (corresponding to S13 and S14). When the moving image management program is acquired, the CPU 21 executes the acquired moving image management program (S42) (corresponding to S15 to S22).

  When the moving image management program is executed, the CPU 21 ends the operation.

Next, an operation example (S42) of the CPU 21 that operates according to the moving image management program will be described.
7 and 8 are flowcharts for explaining an operation example of the CPU 21 that operates according to the moving image management program.

  First, the CPU 21 obtains placement location information (S51). The placement location information indicates settings related to the control of the moving image, such as an ID for specifying the placement location on the Web page or the size of the placement location. For example, the posting location information is incorporated in the html of the Web page.

  When the posting location information is acquired, the CPU 21 generates a URL (for example, VAST URL) for acquiring moving image information corresponding to the posting location indicated by the posting location information (S52). When the URL is generated, the CPU 21 acquires moving image information from the generated URL (S53). S53 corresponds to S15 and S16.

  When the moving image information is acquired, the CPU 21 determines whether or not there is an inline moving image (advertising moving image) at the placement location (S54).

  If it is determined that there is an inline moving image (S54, YES), the CPU 21 generates a Video tag (S55). When the Video tag is generated, the CPU 21 generates a Canvas tag (S56). S55 and S56 correspond to S17.

  When the Canvas tag is generated, the CPU 21 acquires an inline moving image from the CDN 3 based on the moving image information (S57) (corresponding to S18 and S19). When the inline moving image is acquired, the CPU 21 captures a frame of the inline moving image at a predetermined playback time (or start time if it is the first) (S58). When capturing the frame of the inline moving image, the CPU 21 draws the captured frame on the Canvas tag (S59). S58 and S59 correspond to S20.

  When the frame is depicted in the Canvas tag, the CPU 21 determines whether an asynchronous event has occurred (S60). If it is determined that an asynchronous event has occurred (S60, YES), the CPU 21 notifies the ad server 1 that the asynchronous event has occurred based on the moving image information (S61).

When it is determined that an asynchronous event has not occurred (S60, NO) or when the ad server 1 is notified that an asynchronous event has occurred (S61), the CPU 21 determines whether a synchronous event has occurred (S62). ). If it is determined that a synchronization event has occurred (S62, YES), the CPU 21 notifies the ad server 1 that the synchronization event has occurred based on the moving image information (S63).
S60 and S62 correspond to S21. S61 and S63 correspond to S22.

  When it is determined that a synchronization event has not occurred (S62, NO), or when the ad server 1 is notified that a synchronization event has occurred (S63), the CPU 21 determines the playback time of the inline video in the Video tag. (S64).

  When the reproduction time is advanced, the CPU 21 determines whether or not the reproduction of the inline moving image is completed (S65). For example, the CPU 21 determines whether or not the reproduction time is longer than the length of the inline moving image.

If it is determined that the reproduction of the inline moving image has not ended (S65, NO), the CPU 21 returns to S58.
If it is determined that the reproduction of the inline moving image has ended (S65, YES), the CPU 21 notifies the ad server 1 of a reproduction completion event (the moving image has been reproduced 100%) (S66). When it is determined that there is no inline moving image (S54, NO), or when a reproduction completion event is notified (S66), the CPU 21 ends the operation.

The ad server 1 may transmit a response to the user terminal 4 in response to the event notification.
Further, the moving image management program may be distributed by the Web server 2 or the like. Further, the inline moving image may be distributed by the Web server 2 or the like.

Further, the moving image management program may be incorporated in the html of the Web page. In this case, the CPU 21 of the user terminal 4 does not have to acquire the moving image management program from the CDN 3 or the like.
The notification destination of the event indicated by the moving image information may not be the ad server 1.

In addition, this invention is not limited to the said embodiment, In the implementation stage, it can change variously in the range which does not deviate from the summary. In addition, the embodiments may be appropriately combined as much as possible, and in that case, the combined effect can be obtained. Further, the above embodiments include inventions at various stages, and various inventions can be extracted by appropriately combining a plurality of disclosed constituent elements. For example, even if some constituent requirements are deleted from all the constituent requirements shown in the embodiment, the problem described in the column of the problem to be solved by the invention can be solved, and the effect described in the column of the effect of the invention Can be obtained as an invention.
The invention described in the scope of the claims at the beginning of the present application is added below.
[C1]
A program for managing an inline video embedded in a web page,
To the processor,
Get the inline video,
Capture frames while advancing the playback time of the inline video at a predetermined interval,
Display the captured frame,
Detect that the event set in the inline video has occurred,
Notifying an external device that the event has occurred,
program.
[C2]
In addition to the processor,
Get video information indicating the event notification destination,
The notifying is to notify the external device that the event has occurred based on the video information.
The program according to C1.
[C3]
The moving image information is stored in association with an event and a URL,
The notifying is to cause the request to be transmitted to a URL corresponding to the event whose occurrence is detected with reference to the moving image information.
The program according to C2.
[C4]
The program according to any one of C1 to C3, wherein the event whose occurrence is detected includes a synchronization event synchronized with a reproduction time.
[C5]
The synchronization event is that the playback time has elapsed to a predetermined rate.
The program according to C4.
[C6]
Events that are detected include asynchronous events related to operations on the inline video,
The program according to any one of C1 to C5.
[C7]
The asynchronous event includes at least one of pause, resume, mute, unmute or full screen of the inline video.
The program according to C6.
[C8]
Events whose occurrence is detected include events defined by VAST,
The moving image information is included in VAST XML.
The program according to C2.
[C9]
In addition to the processor,
Generate a hidden Video tag and a Canvas tag,
The inline video is set in the Video tag,
The capturing is to capture the frame in the Video tag;
The program according to any one of C1 to C8, wherein the displaying is the rendering of the frame on the Canvas tag.
[C10]
The inline video is an advertising video.
The program according to any one of C1 to C9.
[C11]
A communication unit that communicates with the terminal;
A storage unit for storing the program according to any one of C1 to C10;
A transmission processing unit that transmits the program stored in the storage unit to the terminal through the communication unit;
An information distribution apparatus comprising:

  DESCRIPTION OF SYMBOLS 1 ... Ad server, 2 ... Web server, 3 ... CDN, 4 ... User terminal, 5 ... Communication network, 11 ... CPU, 12 ... ROM, 13 ... RAM, 14 ... NVM, 14a and 14b ... Storage area, 15 ... Communication part 21 ... CPU, 22 ... ROM, 23 ... RAM, 24 ... NVM, 25 ... communication unit, 26 ... operation unit, 27 ... display unit, 100 ... video distribution system.

Claims (9)

A program for managing an inline video embedded in a web page,
To the processor,
Get the inline video,
Get video information indicating the event notification destination set in the inline video,
Capture frames while advancing the playback time of the inline video at a predetermined interval,
Display the captured frame,
Detect that the event set in the inline video has occurred,
Based on the video information, let the external device be notified that the event has occurred,
program. The moving image information is stored in association with an event and a URL,
The notifying is to cause the request to be transmitted to a URL corresponding to the event whose occurrence is detected with reference to the moving image information.
The program according to claim 1 . Events that are detected include sync events that are synchronized to the playback time,
The program according to claim 1 or 2 . The synchronization event is that the playback time has elapsed to a predetermined rate.
The program according to claim 3 . Events that are detected include asynchronous events related to operations on the inline video,
The program according to any one of claims 1 to 4 . The asynchronous event includes at least one of pause, resume, mute, unmute or full screen of the inline video.
The program according to claim 5 . Events whose occurrence is detected include events defined by VAST,
The moving image information is included in VAST XML.
The program according to claim 1 . In addition to the processor,
Generate a hidden Video tag and a Canvas tag,
The inline video is set in the Video tag,
The capturing is to capture the frame in the Video tag;
The program according to any one of claims 1 to 7 , wherein the displaying is drawing the frame on the Canvas tag. The inline video is an advertising video.
The program according to any one of claims 1 to 8 .