IP Library Granted Patent US 12,341,837
Granted Patent B2
US 12,341,837 · App. 18/610,039 · Granted Jun 24, 2025

Out-of-home internet connected household identification

Inventors: Fabrizio Blanco (Los Angeles, CA); Giuseppe Di Mauro (San Diego, CA)
Assignee: VIANT TECHNOLOGY LLC
H04L65/612H04L61/5007H04L65/1069H04L65/1076H04L67/30H04L43/16
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,341,837
App. No.
18/610,039
Granted
Jun 24, 2025
Kind
B2
Abstract

A system and method provide media content based on a household when out-of-home. A first request for media content is received that originates from a first IP address and includes a first data element identification that is associated with a first user. A determination is made that the first IP address is associated with a first internet connected household (ICH). The first data element identification is aliased with the first ICH. A second request (that includes the first data element identification) for media content is received that originates from a second IP address that corresponds to a non-household IP address. In response to the second request and the aliasing, media content is retrieved (based on the first ICH) and transmitted to the first user at the second IP address.

Claims (93)

1. A computer-implemented method for providing media content comprising:

(a) receiving a first request for media content, wherein:

(i) the first request originates from a first Internet Protocol (IP) address; and

(ii) the first request comprises a first data element identification, wherein the first data element identification comprises a publisher generated 1st party cookie, and wherein the first data element identification does not comprise a 3rd party cookie;

(iii) the first data element is associated with a first device; (b) determining, based on the first IP address that the first IP address is associated with a first internet connected household (ICH);

(c) aliasing the first data element identification with the first ICH;

(d) receiving a second request for media content, wherein:

(i) the second request originates from a second IP address; and

(ii) the second IP address corresponds to a non-household IP address;

(iii) the second request comprises the first data element identification;

(e) based on the first data element in the second request, recognizing that the same publisher generated 1st party cookie is received from both the first ICH and a non-household; and

(f) in response to the second request and based on the recognizing and the aliasing of the first data element identification with the first ICH:

(1) retrieving media content based on the first ICH; and

(2) transmitting the media content to the first device at the non-household location.

2. The computer-implemented method of claim 1 , wherein the first data element identification comprises a device ID.

3. The computer-implemented method of claim 1 , wherein the determining that the first IP address is associated with a first ICH comprises:

determining a device activity status based on whether device activity from the first IP address exceeds a defined activity threshold; and

determining whether the first IP address is associated with the first ICH based on the device activity status.

4. The computer-implemented method of claim 1 , wherein the determining that the first IP address is associated with a first ICH comprises:

determining an IP assignment age status based on whether an IP assignment age for the first IP address is greater than a defined threshold age; and

determining whether the first IP address is associated with the first ICH based on the IP assignment age status.

5. The computer-implemented method of claim 1 , wherein the aliasing the first data element identification with the first ICH comprises:

maintaining a household alias table, wherein:

the household alias table maintains a mapping from each data element identification to a household identification; and

each household identification identifies an ICH.

6. The computer-implemented method of claim 1 , further comprising:

providing an option to select a preferred identifier to utilize at a campaign level, wherein the option is between a traditional device ID or a household identifier;

receiving selection of the household identifier as the preferred identifier;

based on the selection, using any IP address for a frequency cap and a household IP address for audience targeting, wherein:

the frequency cap comprises a maximum number of times media content is delivered to any IP address; and

the household IP address comprises any IP address that has been associated with the first ICH or any other ICH.

7. The computer-implemented method of claim 1 , wherein the first data element identification is only permitted to be aliased to a single ICH at any given time.

8. The computer-implemented method of claim 7 , further comprising:

determining a first frequency of requests comprising the first data element identification that originates from the first IP address;

determining a second frequency of requests comprising the first data element identification that originates from the second IP address;

comparing the first frequency to the second frequency;

aliasing the first data element identification with the first ICH when a first frequency is higher than the second frequency; and

aliasing the first data element identification with the second ICH when the second frequency is higher than the first frequency.

9. A computer-implemented method for receiving media content comprising:

(a) sending, from a first device to a server, a first request for media content, wherein:

(i) the first request originates form a first Internet Protocol (IP) address;

(ii) the first request comprises a first data element identification, wherein the first data element identification comprises a publisher generated 1st party cookie, and wherein the first data element identification does not comprise a 3rd party cookie;

(iii) the first data element is associated with the first device;

(b) determining, on the server, based on the first IP address that the first IP address is associated with a first internet connected household (ICH);

(c) aliasing, on the server, the first data element identification with the first ICH;

(d) sending, from the first device to the server, a second request for media content, wherein:

(i) the second request originates from a second IP address; and

(ii) the second IP address corresponds to a non-household IP address;

(iii) the second request comprises the first data element identification;

(e) based on the first data element in the second request, the server recognizing that the same publisher generated 1st party cookie is received from both the first ICH and a non-household; and

(f) the first device receiving, from the server, media content at the non-household location in response to the second request and based on the recognizing and the aliasing of the first data element identification with the first ICH.

10. A system for providing media content, comprising:

(a) a server computer comprising a memory, and a processor;

(b) the processor executing on the server computer;

(c) the memory storing a set of instructions, wherein the set of instructions, when executed by the processor, cause the processor to perform operations comprising:

(i) receiving a first request for media content, wherein:

(1) the first request originates from a first Internet Protocol (IP) address; and

(2) the first request comprises a first data element identification, wherein the first data element identification comprises a publisher generated 1st party cookie, and wherein the first data element identification does not comprise a 3rd party cookie;

(3) the first data element is associated with a first device;

(ii) determining, based on the first IP address that the first IP address is associated with a first internet connected household (ICH);

(iii) aliasing the first data element identification with the first ICH;

(iv) receiving a second request for media content, wherein:

(1) the second request originates from a second IP address; and

(2) the second IP address corresponds to a non-household IP address;

(3) the second request comprises the first data element identification;

(v) based on the first data element in the second request, recognizing that the same publisher generated 1st party cookie is received from both the first ICH and a non-household; and

(vi) in response to the second request and based on the recognizing and the aliasing of the first data element identification with the first ICH:

(1) retrieving media content based on the first ICH; and

(2) transmitting the media content to the first device at the non-household location.

11. The system of claim 10 , wherein the first data element identification comprises a device ID.

12. The system of claim 10 , wherein the operations determine that the first IP address is associated with a first ICH by:

determining a device activity status based on whether device activity from the first IP address exceeds a defined activity threshold; and

determining whether the first IP address is associated with the first ICH based on the device activity status.

13. The system of claim 10 , wherein the operations determine that the first IP address is associated with a first ICH by:

determining an IP assignment age status based on whether an IP assignment age for the first IP address is greater than a defined threshold age; and

determining whether the first IP address is associated with the first ICH based on the IP assignment age status.

14. The system of claim 10 , wherein the operations alias the first data element identification with the first ICH by:

maintaining a household alias table, wherein:

the household alias table maintains a mapping from each data element identification to a household identification; and

each household identification identifies an ICH.

15. The system of claim 10 , wherein the operations further comprise:

providing an option to select a preferred identifier to utilize at a campaign level, wherein the option is between a traditional device ID or a household identifier;

receiving selection of the household identifier as the preferred identifier;

based on the selection, using any IP address for a frequency cap and a household IP address for audience targeting, wherein:

the frequency cap comprises a maximum number of times media content is delivered to any IP address; and

the household IP address comprises any IP address that has been associated with the first ICH or any other ICH.

16. The system of claim 10 , wherein the first data element identification is only permitted to be aliased to a single ICH at any given time.

17. The system of claim 16 , wherein the operations further comprise:

determining a first frequency of requests comprising the first data element identification that originates from the first IP address;

determining a second frequency of requests comprising the first data element identification that originates from the second IP address;

comparing the first frequency to the second frequency;

aliasing the first data element identification with the first ICH when a first frequency is higher than the second frequency; and

aliasing the first data element identification with the second ICH when the second frequency is higher than the first frequency.

Assignments (2)
SECURITY INTEREST Recorded Apr 29, 2026
From: VIANT TECHNOLOGY LLC
To: PNC BANK, NATIONAL ASSOCIATION
Reel/Frame 074521/0933 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 20, 2024
From: BLANCO, FABRIZIO; DI MAURO, GIUSEPPE
To: VIANT TECHNOLOGY LLC
Reel/Frame 066836/0719 →
Continuity (2)
Continuation 17546548 · Dec 9, 2021
Related Publication 20240223634A1 · Jul 4, 2024
References Cited (75)
US 5964839A · Johnson et al. · 1999 [cited by applicant]
US 6151601A · Papierniak et al. · 2000 [cited by applicant]
US 6427170B1 · Sitaraman et al. · 2002 [cited by applicant]
US 6681232B1 · Sistanizadeh et al. · 2004 [cited by applicant]
US 6792458B1 · Muret et al. · 2004 [cited by applicant]
US 6978270B1 · Carty et al. · 2005 [cited by applicant]
US 7039699B1 · Narin et al. · 2006 [cited by applicant]
US 7506360B1 · Wilkinson et al. · 2009 [cited by applicant]
US 7600016B2 · Bean · 2009 [cited by applicant]
US 8214486B2 · Britton et al. · 2012 [cited by applicant]
US 8533322B2 · Chamberlain et al. · 2013 [cited by applicant]
US 8996727B2 · DeFrancesco et al. · 2015 [cited by applicant]
US 9038178B1 · Lin · 2015 [cited by applicant]
US 9331921B2 · DeFrancesco et al. · 2016 [cited by applicant]
US 10728350B1 · Khanwalkar et al. · 2020 [cited by applicant]
US 10764240B2 · DeFrancesco et al. · 2020 [cited by applicant]
US 20020128925A1 · Angeles · 2002 [cited by applicant]
US 20030172136A1 · Katagawa et al. · 2003 [cited by applicant]
US 20040030931A1 · Chamandy et al. · 2004 [cited by applicant]
US 20040073533A1 · Mynarski et al. · 2004 [cited by applicant]
US 20050015584A1 · Takechi et al. · 2005 [cited by applicant]
US 20050033641A1 · Jha et al. · 2005 [cited by applicant]
US 20050114496A1 · Fang et al. · 2005 [cited by applicant]
US 20050286686A1 · Krstulich · 2005 [cited by applicant]
US 20060136372A1 · Schunemann · 2006 [cited by applicant]
US 20060288096A1 · Yim · 2006 [cited by applicant]
US 20080033794A1 · Ou et al. · 2008 [cited by applicant]
US 20080101353A1 · Streijl et al. · 2008 [cited by applicant]
US 20080201311A1 · Ertugrul et al. · 2008 [cited by applicant]
US 20080274736A1 · Hu · 2008 [cited by applicant]
US 20080281699A1 · Whitehead · 2008 [cited by applicant]
US 20090034521A1 · Kato · 2009 [cited by applicant]
US 20090113062A1 · Woodman · 2009 [cited by applicant]
US 20090125397A1 · Gomaa et al. · 2009 [cited by applicant]
US 20100191577A1 · Lu et al. · 2010 [cited by applicant]
US 20110016206A1 · Kodialam et al. · 2011 [cited by applicant]
US 20110087780A1 · McCann et al. · 2011 [cited by applicant]
US 20110231497A1 · Tovar · 2011 [cited by applicant]
US 20110276689A1 · Rosen · 2011 [cited by applicant]
US 20110287764A1 · Zitnik · 2011 [cited by applicant]
US 20110314495A1 · Zenor · 2011 [cited by applicant]
US 20120102169A1 · Yu et al. · 2012 [cited by applicant]
US 20120124607A1 · Georgakis · 2012 [cited by applicant]
US 20130006706A1 · Harvey et al. · 2013 [cited by applicant]
US 20130086245A1 · Lu · 2013 [cited by examiner]
US 20130212188A1 · Duterque et al. · 2013 [cited by applicant]
US 20130276027A1 · Sheehan et al. · 2013 [cited by applicant]
US 20130311649A1 · DeFrancesco et al. · 2013 [cited by applicant]
US 20140006951A1 · Hunter · 2014 [cited by applicant]
US 20140304397A1 · DeFrancesco et al. · 2014 [cited by applicant]
US 20150371272A1 · Vanderhook et al. · 2015 [cited by applicant]
US 20160253711A1 · Sankaran et al. · 2016 [cited by applicant]
US 20160275563A1 · Sankaran · 2016 [cited by examiner]
US 20170024778A1 · Knapp · 2017 [cited by examiner]
US 20180046465A1 · Jacoby et al. · 2018 [cited by applicant]
US 20190037358A1 · Jenkins et al. · 2019 [cited by applicant]
US 20220014496A1 · Anderson · 2022 [cited by applicant]
US 20220337562A1 · Sonawalla et al. · 2022 [cited by applicant]
KR 20090000995 · 2009 [cited by applicant]
WO 2006058274 · 2006 [cited by applicant]
WO 2010120359 · 2010 [cited by applicant]
PCT International Search Report & Written Opinion dated Feb. 7, 2023 for PCT Application No. PCT/US2022/080055. [cited by applicant]
“About publisher provided identifiers”, Google Ad Manager Help, https://support.google.com/admanager/answer/2880055?hl=en, pp. 1-4, as printed Nov. 2, 2021. [cited by applicant]
“identifierForVendor”, Apple Developer Documentation, https://developer.apple.com/documentation/uikit/uidevice/1620059-identifierforvendor, pp. 1-2, as printed Nov. 2, 2021. [cited by applicant]
“Quick Facts United States”, United States Census Bureau, Nov. 2, 2016. http://quickfacts.census.gov/qfd/meta/long_HSD310200.htm. [cited by applicant]
“Regional Internet registry”, Wikipedia, The Free Encyclopedia, Nov. 2, 2016. http://en.wikipedia.org/wiki/Regional_Internet_registry. [cited by applicant]
Mitchell, B., “What is an IP Address?”, Lifewire, Oct. 29, 2016. http://compnetworking.about.com/od/workingwithipaddresses/g/ip-addresses.htm. [cited by applicant]
“TCP/IP Introduction”, w3schools.com, WayBackMachine, May 5, 2012. https://web.archive.org/web/20120505075449/http://w3schools.com/tcpip/tcpip_intro.asp. [cited by applicant]
Mitchell, B., “HTTP—HyperText Transfer Protocol”, Lifewire, Jun. 30, 2016. http://compnetworking.about.com/od/networkprotocols/g/bldef_http.htm. [cited by applicant]
Crawford, Gregory S., “Household Internet Use: Implications for Online Competition and Market Structure”, Dept. of Economics, Duke University, 1999. http://ftp.econ.duke.edu/gsc/ecfacts.pdf. [cited by applicant]
Kihl, Maria, et al., “Traffic analysis and characterization of Internet user behavior”, Ultra Modern Telecommunications and Control Systems and Workshops (ICUMT), 2010 International Congress on IEEE, 2010. http://lup.lu… [cited by applicant]
Xie, Yinglian, et al., “How Dynamic are IP Addresses?”, ACM SIGCOMM '07, Kyoto, Japan, Computer Communication Review, vol. 37, No. 4, ACM, Aug. 27-31, 2007. http://131.107.65.14/pubs/63680/sigcomm07-onefile.pdf. [cited by applicant]
Canadian Office Action dated Mar. 27, 2025 for Canadian Patent Application No. 3,237,330. [cited by applicant]
Extended European Search Report dated Apr. 1, 2025 for European Patent Application No. 22905234.5. [cited by applicant]
Chen, Q., et al., “Cookie Swap Party: Abusing First-Party Cookies for Web Tracking”, Proceedings of the 17th ACM Conference On Security and Privacy in Wireless and Mobile Networks, Apr. 2021, pp. 2117-2129. [cited by applicant]