WO2016196500A1

WO2016196500A1 - Operating system based event verification

Info

Publication number: WO2016196500A1
Application number: PCT/US2016/035072
Authority: WO
Inventors: Srinivasa Dharmaji; Pavel S. Veselov
Original assignee: Goldspot Media, Inc.
Priority date: 2015-05-29
Filing date: 2016-05-31
Publication date: 2016-12-08

Abstract

A system and method for tracking beacon execution using event verification capability of an operating system, where the authenticity of the platform itself is verified. Targeted advertisements are displayed during content viewing and/or web browsing, while the rendered and displayed advertisements are tracked for payment, wherein payment is based on completion of viewing the events. The system and method keeps count of beacon execution, with verifiable IDs, using the operating system to verify, authenticate and guarantee execution of event activity.

Description

OPERATING SYSTEM BASED EVENT

VERIFICATION

CROSS REFERENCE TO RELATED APPLICATIONS

This patent application claims priority to U.S Patent Application No. 14/726,284 filed May 29, 2015, which is incorporated herein in its entirety by this reference thereto.

BACKGROUND OF THE INVENTION

TECHNICAL FIELD

[001 ] The invention relates to targeted advertising. More specifically, the invention relates to a system and method for trustworthy and guaranteed tracking of rendered and displayed advertisements for payment based on completion of viewing.

DESCRIPTION OF THE RELATED ART

[002] Targeted and focused advertising is a way to reach people directly with items of interest to them. The wide spread use of mobile handheld display devices (MHDDs), like cell phones and personal digital assistants (PDAs), in conjunction with stationary display devices (DDs), have made the rendering and execution of content, including the targeted advertisements, a very complex process. Since the MHDDs can be used to view preloaded content even when they are disconnected from a network, targeted advertisements are also pre- stored on the MHDDs to be rendered and displayed when the selected content is viewed on the MHDDs. [003] Typically, payment for content and the advertisements used in the content is based on the number of times the content and the associated advertisement is viewed by the customer. This payment model necessitates tracking the content and viewing the content to ensure that the content and advertisements are effectively presented in a predefined fashion, and hence are eligible for payment. According to the prior art, this is done by the use of beacons attached to the content. Using beacons, the tracking of the rendering and of the display of the content is explained in terms of the content. The systems for tracking the viewing of content are explained using MHDD as the basis as viewing of the content on DDs form a simpler subset of that on the MHDD.

[004] Figure 1 shows a typical implementation of the prior art system 1000 for evaluating and tracking the viewing of content 103 including associated advertisements on an MHDD. Content providers 101 generate the content 103 and supply them to the web server 201 . The content 103 contains beacons 104, which are embedded executable script, as part of the content. The web server 201 generates web pages 202 by combining content 103 from multiple content providers 101 . These web pages 202 are stored in a library 203 on the web server. The web pages contain, as part of the content 103, the beacons 104. During connected time, when the MHDD 301 is connected to the net, the content 103 can be downloaded on to the MHDD 301 and stored. When this content 103 is viewed, as the specific portion of the content 103 with the beacon 104 is rendered and displayed, the beacons 104 are executed on the web browser 302. The number of times each beacon 104 is executed on the web server 302 is transferred 306, by the web server, to a tracking server 401 directly when the MHDD 301 is connected to the internet. If not, this beacon 104 execution count on the web browser 302, is stored on the MHDD 301 , and transferred to the tracking server 401 when an active connection is established. The tracking server 401 uses this count to establish the payment criteria, as per predefined agreements, to the content and advertisement providers 101 . [005] The use of beacon 104 execution counts on the web browser 302 is not a very trustworthy indication of the rendering and display of the content 103 and advertisements. This is due to the fact that it is possible to invisibly encapsulate beacons 104 and add them to the content 103. As a result a larger than actual count may be produced during rendering of a content 103 without really displaying the content multiple times. Similarly it is possible to make beacons 104 inactive during content 103 display such that the beacon 104 execution count that is provided to the tracking server is less than the number of times the content 103 is actually rendered and displayed.

SUMMARY OF THE INVENTION

[006] The invention relates to display of targeted advertisements during content viewing and web browsing and especially to trustworthy tracking of rendered and displayed advertisements for payment based on completion of viewing.

[007] The method of using the capability of operating systems, wherein an application can ask the Operating system to verify an applicable activity within the system, to provide a count of execution of beacons embedded in the content.

[008] The method and system for enabling a trust worthy means for keeping count, with verifiable IDs, of beacon execution during content viewing, using the operating system capability to verify application activity. BRIEF DESCRIPTION OF THE DRAWINGS

[009] Figure 1 shows a typical implementation of the prior art system for evaluating and tracking the viewing of content including associated advertisements on an MHDD according to some embodiments of the invention;

[0010] Figure 2 shows an exemplary and non limiting block diagram of a system for tracking beacon execution using event verification capability of an operating system according to some embodiments of the invention; and

[001 1 ] Figure 3 is a simplified, exemplary and non-limiting flowchart of a method of for tracking beacon execution using event verification capability of an operating system according to some embodiments of the invention.

DETAILED DESCRIPTION OF THE INVENTION

[0012] As explained above in the discussion of Figure 1 , the use of beacon 104 execution counts on the web browser 302 is not a very trustworthy indication of the rendering and display of the content 103 and advertisements. This is due to the fact that it is possible to invisibly encapsulate beacons 104 and add them to the content 103. As a result a larger than actual count may be produced during rendering of a content 103 without really displaying the content multiple times. Similarly it is possible to make beacons 104 inactive during content 103 display such that the beacon 104 execution count that is provided to the tracking server is less than the number of times the content 103 is actually rendered and displayed.

[0013] Hence it would be advantageous if a fully trustable means for generation of the count of the content 103 rendering by execution of beacons 104 may be established, and further provided to a tracking server 401 to enable a reliable payment criteria.

[0014] Today targeted advertisements are displayed during browsing the web or viewing content. On display devices (DDs) which may be mobile handheld display devices (MHDDs) the advertisements and content for viewing are downloaded and stored enabling these advertisements and content to be displayed even when the MHDD has no connection to the internet. Payment is made only for viewed content and the associated viewed advertisements. Today a method based on count of completed viewings, using embedded tracking beacons, which are typically small scripts, executed on the browser, is used for tracking this. This is an un-trustworthy system as simulated beacon execution and beacon elimination are both possible on the browser.

[0015] A new method of tracking the beacon execution using event verification capability of an operating system is disclosed as a trustable alternate to browser based beacon execution. The execution counts are sent to a tracking server, during connected time, to enable compilation and payment. [0016] Operating systems related operations are a well understood and trusted. Hence in order to get an accurate and trusted measure of the content and advertisement display it is better if the capabilities of the operating system can be used. In operating systems, an application can ask the operating system to verify an applicable activity within the system. This capability is used to confirm the execution of the content and the advertisements. This capability is used with a unique library and an application programming interface (API), in the disclosed verifiable and trustable implementation, to confirm the number of executions of a specific functionality in a verifiable manner. As an example of authenticity verification, the authenticity of the platform itself is verified using X509 or analogous certification methods. This capability can be applied to the execution of beacons and to provide a verifiable count to a registered tracking server with caller ID and event ID both of which ensure the correctness of the event execution. The operating system can store the execution count information on the MHDD if the connection to the server via the network is unavailable and download the information when connection is established in an authenticated manner. The communication between the tracking server and the MHDD can be enabled using any suitable up to date methods of encryption and authentication available. This prevents tampering of the data at the display end and also during transmission of the data to the registered tracking server. Since an aim of some embodiments is to provide guaranteed event counts of events such as viewing (impression), clicking (click through and engagement) and follow up (conversion) reducing or eliminating the capability for fraud, the capability for authentication, verification and encryption play a major role in providing and enabling the guarantee and preventing fraud. Here again the system explanation is provided based on the content being rendered and displayed on MHDDs as rendering and displaying on DDs form a simpler sub set.

[0017] Figure 2 shows an exemplary and non limiting block diagram 2000 of a system implementing the present invention. Content providers 101 generate the content 103 and supply them to the web server 201 . The content 103 will contain beacons 104 as part of the content. The web server 201 generates web pages 202 by combining content 103 from multiple content providers 101 . These web pages 202 are stored in a library 203 on the web server. The web pages contain as part of the content 103 the beacons 104. During the period or time when the MHDD 301 is connected to the net (connected time) the content 103 can be downloaded on to the MHDD 301 and stored. An API 303 with an associated library 304 is preloaded on the MHDD 301 , which enables the operating system 305 of the MHDD to identify, verify and confirm the number of executions of a specific functionality, namely the execution of each of the embedded beacons 104, identified by the library, in a verifiable manner with an associated caller ID and event ID. Hence the operating system 305 is able to provide a verifiable count of the execution of the beacons 104, and thereby the rendering of the content and advertisement, to the tracking server 401 . This verified beacon 104 execution count is fully trustable as operating system 305 based verification of the execution of any applicable activity is trust worthy and difficult to manipulate. The information is transferred 307, to the tracking server 401 by the operating system 305. This can be done in an encrypted and secure fashion using any available method. This information can be used to generate a payment based on a payment criteria, pre- established for the content 103 including the advertisements, that is verifiable and trustable by all. [0018] Figure 3 is a simplified, exemplary and non-limiting flowchart 3000 of the current invention executed by system shown in Fig.2. The content 103 and advertisement providers 101 generate and supply the content 103 and advertisements with embedded beacons 104 (S3010). These beacons 104 are embedded in the content and advertisements to enable verification of the rendering and display of the content and advertisements 103. This content 103 and advertisements are supplied to the web server 201 with payment criteria established based on a count of the number of times a content 103 and associated advertisements are displayed (S3020). The web server 201 receives content 103 and associated advertisements from a number of content suppliers 101 and generates and stores these as web pages 202 in a library of web pages (S3030). When a user of a DD or MHDD 301 requests a web page 202 the web page 202 is supplied with built in content 103 and associated advertisements. This content 103 has the embedded beacons 104 associated with the content (S3040). During rendering and display of the content and associated advertisements on the web browser, the embedded beacons are executed on the browser (S3050). A pre-loaded API 303 with a library 304 is used to request the operating system 305 of the DD or MHDD to verify selected beacon 103 executions in the system of the DD or MHDD 301 (S3060). The operating system 305, based on the request, verifies and confirms the selected beacon 104 executions on the browser of the system. Each selected beacon 104 execution is identified by the operating system 305 with a caller ID and an event ID. Since the caller ID and event ID are specific capability of the operating system 305, these are not modifiable and hence are trust worthy. The operating system 305 is hence able to keep a verifiable and trustable count of the number of times each selected beacon 104 is executed during the rendering and display of the web page 202 with content 103 viewing on the browser 302 (S3070). Whenever the DD or MHDD 301 is connected to the web, the operating system is able to transfer the verifiable and trustable count of the execution of selected beacons to a pre-defined tracking server 401 (S3080). The tracking server based on the verified count, with caller id and event id, is able to generate a payment, for the viewed content 103 and advertisements, based on the payment criteria previously established (S309).

[0019] The principles of the invention or part thereof are implemented as hardware, firmware, software, or any combination thereof. Moreover, the software is preferably implemented as an application program tangibly embodied on a program storage unit or non-transitory computer readable medium or a non- transitory machine-readable storage medium that can be in a form of a digital circuit, an analogy circuit, a magnetic medium, or combination thereof. The application program may be uploaded to, and executed by, a machine comprising any suitable architecture. Preferably, the machine is implemented on a computer or communication platform having hardware such as one or more central processing units ("CPUs"), a memory, and input/output interfaces. The platform may also include one or more operating systems and microinstruction codes. The various processes and functions described herein may be either part of the microinstruction code or part of the application program, or any combination thereof, which may be executed by a CPU, whether or not such computer, communication system or processor is explicitly shown. In addition, various other peripheral units may be connected to the platform such as an additional data storage unit and a printing unit. [0020] Even though the implementations disclosed and described herein are the preferred ones, it is not meant to be limiting. There may be modifications and improvements which may be applicable and are clear to practitioners of the art. There are also many different applications of the trustable verification process, which are not enumerated, herein. These modifications of the invention, not presently described or foreseen, may nonetheless represent equivalents thereto which are also covered by this disclosure.

[0021 ] As will be understood by those familiar with the art, the invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. Likewise, the particular naming and division of the members, features, attributes, and other aspects are not mandatory or significant, and the mechanisms that implement the invention or its features may have different names, divisions and/or formats. Accordingly, the disclosure of the invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following Claims.

Claims

1 . A system for tracking of a rendered and displayed advertisement for payment based on completion of an event on a display device, the system comprising: a processor associated with the display device; and

a memory operatively coupled to the processor;

wherein the processor is enabled to perform a method comprising:

running an operating system;

verifying the authenticity of a platform associated with the display device;

running a library and an application programming interface (API) configured to allow the operating system to identify, confirm, verify and authenticate the execution of an event relating to the at least one advertisement in the form a count of one or more verified and authenticated beacons;

storing the count as encrypted data in the memory;

coupling the display device to a tracking server over a network; and transferring the encrypted data over the network to the tracking server for payment processing.

2. The system of Claim 1 , wherein the system is enabled to guarantee trustworthy tracking of the rendered and displayed advertisement.

3. The system of Claim 1 , wherein the execution of the event comprises any of an impression, a click-though, and a conversion.

4. The system of Claim 1 , wherein the verified execution of content guarantees rendering and display of the associated advertisement.

5. The system of Claim 1 , wherein the payment for the associated advertisement is based on the verifiable count of the embedded beacons.

6. The system of Claim 1 , wherein the display device is a mobile display device.

7. The system of Claim 6, wherein the content and associated advertisements are pre-stored on the mobile display device for rendering and display when the mobile handheld device has no web connection.

8. A method of verifying, authenticating and guaranteeing an event execution on a display device running an operating system thereon, the method comprising: establishing an application programming interface (API) on the display device that enables the operating system to identify, confirm, verify and authenticate the execution of an event relating to at least one advertisement, using one or more verified and authenticated beacons;

downloading, rendering and displaying digital content on the display device, wherein the digital content includes an advertisement;

identifying and confirming the execution of the advertisement by the API on the operating system, wherein the confirmation comprises authentication and verification of information and generating an authenticated and verified beacon; encrypting and saving a count of the authenticated and verified beacons from the operating system in a memory; and

transferring the saved beacons over a network to a tracking server, wherein the beacons allow the tracking server to determine how the content provider is paid for the execution of the advertisement.

9. The method of Claim 8, wherein the event execution comprises any of an impression, a click through, and a conversion.

10. The method of Claim 8, wherein the memory is located on the display device.

1 1 . The method of Claim 8, wherein the verification of the authenticity of the platform is performed by any of X509 or analogous certification methods.

12. The method of Claim 8, further comprising:

providing a plurality of content providers and a plurality of display devices.

13. The method of Claim 12, wherein the plurality of display devices comprises at least one network of handheld mobile devices.

14. The method of Claim 8, further comprising:

encrypting the verification information before transfer to the tracking server.

15. The method of Claim 8, further comprising:

establishing one or more payment criteria that determines how the content provider is to be paid for the execution of the advertisement.

16. The method of Claim 15, further comprising:

delivering payment to the content provider based on the accounted for verified beacons according to the payment criteria.

17. The method of Claim 8, further comprising:

pre-storing the advertisement on the display device for rendering and displaying in the absence of a connection to the server.

18. A mobile device, comprising:

a processor coupled with a memory;

a network interface operatively coupled with the processor and configured to establish a connection between the mobile device and a content provider via a server; and

a media player operatively coupled with the processor and configured to render digital content for display, and

ingest digital content published by the content provider, wherein the digital content comprises actual content and at least one advertisement; wherein the processor configured to run an operating system to:

identify and confirm the display of one or more advertisements by execution of count of one or more verified beacons,

save the execution count of the one or more verified beacons as encrypted data in the memory to preserve the execution count of the one or more verified beacons when the mobile device is not connected to the at least one server, and

transfer the encrypted data to the server when the mobile device is connected to the server.

19. The mobile device of Claim 18, wherein the device is enabled to guarantee trustworthy tracking of the rendered and displayed advertisement.

20. The mobile device of Claim 18, wherein the execution of the event comprises any of an impression, a click-though, and a conversion.