Content exposure attribution based on renderings of related content across multiple devices

• US 10,631,068 B2
• Filed: 12/01/2017
• Issued: 04/21/2020
• Est. Priority Date: 11/26/2008
• Status: Active Grant

• Current Assignee: Samba TV Incorporated
• Original Assignee: Free Stream Media Corporation
• Inventors: Navin, Ashwin, Harrison, David
• Primary Examiner(s): Chae, Kyu
• Application Number:
  US15/829,869
• Publication Number:
  US 20180091873A1
• Time in Patent Office: 872 Days
• CPC Class Codes: G06F 16/40 of multimedia data, e.g. slideshows comprising image and additional audio data retrieval of still image data G06F16/50; retrieval of audio data G06F16/60; retrieval of video data G06F16/70
• CPC Class Codes: G06F 16/783 using metadata automatically derived from the content
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06F 21/53 by executing in a restricted environment, e.g. sandbox or secure virtual machine
• CPC Class Codes: G06F 2221/033 Test or assess software
• CPC Class Codes: G06F 3/14 Digital output to display device ; Cooperation and interconnection of the display device with other functional units
• CPC Class Codes: G06Q 30/0255 based on user history
• CPC Class Codes: G06Q 30/0269 based on user profile or attribute
• CPC Class Codes: G06Q 30/0277 Online advertisement
• CPC Class Codes: G08C 17/02 using a radio link
• CPC Class Codes: H04L 12/18 for broadcast or conference , e.g. multicast
• CPC Class Codes: H04L 2101/668 Internet protocol [IP] address subnets
• CPC Class Codes: H04L 61/2514 between local and global IP addresses
• CPC Class Codes: H04L 61/2517 using port numbers
• CPC Class Codes: H04L 61/256 NAT traversal
• CPC Class Codes: H04L 61/2575 using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4541 Directories for service discovery
• CPC Class Codes: H04L 61/5007 Internet protocol [IP] addresses
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/102 : Entity profiles
• CPC Class Codes: H04L 63/107 : wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals
• CPC Class Codes: H04L 65/1069 : Session establishment or de-establishment
• CPC Class Codes: H04L 65/611 : for multicast or broadcast systems for broadcast or conference H04L12/18; arrangements for broadcast or distribution combined with broadcast H04H20/00; arrangements for broadcast applications with a direct linkage to broadcast information or to broadcast space-time H04H60/00; selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS], H04W4/06
• CPC Class Codes: H04L 65/612 : for unicast
• CPC Class Codes: H04L 67/02 : based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 : in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/141 : Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/51 : Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/53 : using third party service providers
• CPC Class Codes: H04N 21/23424 : involving splicing one content stream with another content stream, e.g. for inserting or substituting an advertisement
• CPC Class Codes: H04N 21/237 : Communication with additional data server
• CPC Class Codes: H04N 21/2541 : Rights Management protecting software against unauthorised usage in a vending or licensing environment G06F21/10; security in data switching network management H04L41/28; security management or policies for network security H04L63/20; access security in wireless networks H04W12/08
• CPC Class Codes: H04N 21/25841 : involving the geographical location of the client retrieval from the Internet by querying based on geographical locations G06F16/9537; arrangements for identifying locations of receiving stations in broadcast systems H04H60/51; location of the user terminal in data switching networks H04L67/52; services making use of the location of users or terminals in wireless networks H04W4/02; locating users or terminals in wireless networks H04W64/00
• CPC Class Codes: H04N 21/278 : Content descriptor database or directory service for end-user access details of content or meta data based information retrieval of video data in video databases G06F16/739
• CPC Class Codes: H04N 21/41265 : having a remote control device for bidirectional communication between the remote control device and client device unidirectional remote control device H04N21/42204
• CPC Class Codes: H04N 21/41407 : embedded in a portable device, e.g. video client on a mobile phone, PDA, laptop constructional details of equipment or arrangements specially adapted for portable computer application G06F1/1626; arrangements specially adapted for mobile receivers in broadcast systems H04H20/57
• CPC Class Codes: H04N 21/4147 : PVR [Personal Video Recorder] H04N5/76 takes precedence ; arrangements for broadcast with accumulation-type receivers H04H20/40
• CPC Class Codes: H04N 21/435 : Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream
• CPC Class Codes: H04N 21/4415 : using biometric characteristics of the user, e.g. by voice recognition or fingerprint scanning cryptography using biological data H04L9/3231; authentication in networks using biometric H04L63/0861
• CPC Class Codes: H04N 21/466 : Learning process for intelligent management, e.g. learning user preferences for recommending movies services using the results of monitoring in broadcast systems H04H60/61
• CPC Class Codes: H04N 21/6175 : involving transmission via Internet broadcast-related systems characterised by the transmission system being the Internet H04H60/82
• CPC Class Codes: H04N 21/64322 : IP
• CPC Class Codes: H04N 21/812 : involving advertisement data advertising per se G06Q30/02
• CPC Class Codes: H04N 21/835 : Generation of protective data, e.g. certificates protecting software against unauthorised usage in a vending or licensing environment G06F21/10
• CPC Class Codes: H04N 21/8352 : involving content or source identification data, e.g. Unique Material Identifier [UMID]
• CPC Class Codes: H04N 21/8358 : involving watermark protecting executable software by watermarking G06F21/16; image watermarking in general G06T1/0021; watermarks inserted in still images for transmission purposes H04N1/32144; inserting watermarks during video coding H04N19/467
• CPC Class Codes: H04N 21/84 : Generation or processing of descriptive data, e.g. content descriptors systems specially adapted for using meta-information in broadcast systems H04H60/73

Abstract

A method of an attribution server is disclosed. The method includes determining that one or more request(s) is received through the computer network from a first device based on accessing first data related to renderings of a first content on the first device, and determining rendering of a second content on a second device based on accessing second data related to renderings of content on the second device. The method also includes determining that the first content and the second content are related, determining likely association of the first device and the second device with a same user, and determining that the same user is likely to have rendered the second content on the second device based on exposure thereof to the first content on the first device.

Claims

1. A method of an attribution server comprising:

determine that at least one request is received through a computer network from a first device based on accessing first data related to renderings of first content on the first device, the first data comprising data related to the at least one request, and the at least one request being made in response to one of;

a request for the first content on the first device and the first content being rendered on the first device;

determining rendering of a second content on a second device based on accessing second data related to renderings of content on the second device;

determining that the first content and the second content are related based on identifiers thereof;

determining likely association of the first device and the second device with a same user based on determining at least one of;

a public network identifier shared between the first device and the second device in the first data and the second data, mapping between device identifiers thereof through at least one of;

the first data and the second data, and a third party server, a mutually visible base station signal, another mutually visible signal, a postal address identifier, a geolocation, and a discovery service available through the computer network to determine presence of the first device and the second device on a same private network of the computer network; and

determining that the same user is likely to have rendered the second content on the second device based on exposure thereof to the first content on the first device in accordance with additionally determining that the rendering of the second content on the second device and the at least one request from the first device are separated in time within a threshold value thereof, the determined relation between the first content and the second content, and the determined likely association of the first device and the second device with the same user.

2. The method of claim 1, wherein:

the first data is logged at a first server of a network data provider,

the second data is logged at a second server of a content identification (ID) data provider, and

the attribution server is communicatively coupled to the first server and the second server through the computer network.

3. The method of claim 1, wherein:

the first content comprises at least one of an advertisement, a promotion, and a piece of content which is one of;

broadcast, streamed, downloaded, and executed, and

the second content comprises at least one of;

a TV show, a movie, a TV channel, a radio program, a game, and another piece of content which is one of;

broadcast, streamed, downloaded and executed.

4. The method of claim 1, comprising:

executing, in a constrained environment within a security sandbox, a sandboxed application on the first device; and

rendering the first content through the sandboxed application.

5. The method of claim 2, wherein at least one of:

at least two of;

the attribution server, the first server and the second server are the same device, and

the first device and the second device are the same device.

6. The method of claim 1, comprising obtaining at least a portion of the second data accessed by the attribution server using at least one of:

an audio automatic content recognition (ACR), a video ACR, audio watermarks, video watermarks, an embedded metadata, and a channel change data correlated against a TV schedule.

7. The method of claim 1, wherein the at least one request is a network request comprising at least one of:

a public Internet Protocol (IP) address of the first device, a cookie, and a requested resource.

8. The method of claim 1, wherein the public network identifier shared between the first device and the second device in the first data and the second data is a public IP address shared between the first device and the second device at any time within a predefined time range.

9. The method of claim 1, further comprising verifying association of the first device and the second device with the same user when the same user one of:

explicitly pairs the first device and the second device and pairs the first device and the second device using at least one of;

a user name and a short code.

10. The method of claim 1, wherein the determination of whether the first device and the second device are likely associated with the same user occurs after the at least one request from the first device and the rendering of the second content on the second device.

11. A method of an attribution server comprising:

determining that at least one request is received through a computer network from a first device based on accessing first data related to renderings of a first content on the first device, the first data comprising data related to the at least one request, and the at least one request being made in response to one of;

a request for the first content on the first device and the first content being rendered on the first device;

determining rendering of a second content on a second device based on accessing second data related to renderings of content on the second device;

determining that the first content and the second content are related based on identifiers thereof;

determining likely association of the first device and the second device with a same user based on determining at least one of;

a public network identifier shared between the first device and the second device in the first data and the second data, mapping between device identifiers thereof through at least one of;

the first data and the second data, and a third party server, a mutually visible base station signal, another mutually visible signal, a postal address identifier, a geolocation, and a discovery service available through the computer network to determine presence of the first device and the second device on a same private network of the computer network; and

determining that the same user is likely to have originated the at least one request from the first ice based on exposure thereof to the second content on the second device in accordance with additionally determining that the rendering of the second content on the second device and the at least one request from the first device are separated in time within a threshold value thereof, the determined relation between the first content and the second content, and the determined likely association of the first device and the second device with the same user.

12. The method of claim 11, wherein:

the first data is logged at a first server of a site data provider,

the second data is logged at a second server a content ID data provider, and

the attribution server is communicatively coupled to the first server and the second server through the computer network.

13. The method of claim 11, wherein:

the first content comprises at least one of a web site, a mobile application, and a desktop application, and

the second content comprises at least one of a TV show, a movie, a TV channel, a radio program, a game, and another piece of content that is one of broadcast, streamed, downloaded and executed.

14. The method of claim 11, comprising:

executing, in a constrained environment within a security sandbox, a sandboxed application on the first device; and

rendering the first content through the sandboxed application.

15. The method of claim 12, wherein at least one of:

at least two of;

the attribution server, the first server and the second server are the same device, and

the first device and the second device are the same device.

16. The method of claim 11, comprising obtaining at least a portion of the second data accessed by the attribution server using at least one of:

an audio ACR, a video ACR, audio watermarks, video watermarks, an embedded metadata, and a channel change data correlated against a TV schedule.

17. The method of claim 11, wherein the at least one request is a network request comprising at least one of:

a public IP address of the first device, a cookie, and a requested resource.

18. The method of claim 11, wherein the public network identifier shared between the first device and the second device in the first data and the second data is a public IP address shared between the first device and the second device at any time within a predefined time range.

19. The method of claim 11, further comprising verifying association of the first device and the second device with the same user when the same user one of:

explicitly pairs the first device and the second device and pairs the first device and the second device using at least one of;

a user name and a short code.

20. The method of claim 11, wherein the determination of whether the first device and the second device are likely associated with the same user occurs after the at least one request from the first device and the rendering of the second content on the second device.

21. A method of an attribution server communicatively coupled to a server of a content ID data provider through a computer network, comprising:

determining that at least one request is received through the computer network from a first device based on accessing first data related to renderings of a first content logged at the server, the first data comprising data related to the at least one request, and the at least one request being made in response to one of;

a request for the first content on the first device and the first content being rendered on the first device;

determining rendering of a second content on a second device based on accessing second data logged at the server, the second data related to renderings of content on the second device;

determining that the first content and the second content are related based on identifiers thereof;

determining likely association of the first device and the second device with a same user based on determining at least one of;

a public network identifier shared between the first device and the second device in the first data and the second data, mapping between device identifiers thereof through at least one of;

the first data and the second data, and a third party server, a mutually visible base station signal, another mutually visible signal, a postal address identifier, a geolocation, and a discovery service available through the computer network to determine presence of the first device and the second device on a same private network of the computer network; and

determining that the same user is likely to have rendered the second content on the second device after exposure thereof to the first content on the first device in accordance with additionally determining that the rendering of the second content on the second device and the at least one request from the first device are separated in time within a threshold value thereof, the determined relation between the first content and the second content, and the determined likely association of the first device and the second device with the same user.