IP Library Granted Patent US 12,067,594
Granted Patent B2
US 12,067,594 · App. 16/683,788 · Granted Aug 20, 2024

Visitor detection unit and identification system

Inventor: Ruddman Davis (San Francisco, CA)
Assignee: BYTEDANCE INC.
G06Q30/0261
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,067,594
App. No.
16/683,788
Granted
Aug 20, 2024
Kind
B2
Abstract

A visitor detection unit includes a digital processor, an RF transceiver, a sensor and digital memory. Preferably, the digital memory includes code segments executable on the digital processor for transmitting a beacon signal via a transmitter portion of the RF transceiver, monitoring via the sensor for a visitor event monitoring via a receiver portion of the RF transceiver for a beacon response event, and selectively transmitting metadata via the transmitter portion of the RF transceiver that is related at least one of the visitor event and the beacon response event. In this example embodiment, an enclosure is provided for the digital processor, the RF transceiver and the digital memory such that the visitor detection unit can be mounted on a surface proximate to a physical area to be monitored.

Claims (49)

1. An apparatus comprising at least one processor and at least one memory including program code, the at least one memory and the program code configured to, with the processor, cause the apparatus to at least:

receive, from a visitor detection unit, visitor event metadata comprising presence data associated with a visitor event at a merchant location, wherein:

the visitor event metadata is generated in response to a passive infrared motion detection event, and

the visitor event metadata comprises visitor event type data indicating a direction of travel of the consumer device and visitor event timestamp data;

receive consumer device data associated with the consumer device, wherein the consumer device data comprises application data from at least one application executing on the consumer device, and wherein the consumer device data is generated in response to a BLE event of the at least one application executing on the consumer device;

in a circumstance in which the visitor event metadata is received from the visitor detection unit and the consumer device data is received prior to expiration of a timeout period:

correlate the visitor event metadata and the consumer device data to generate multisource correlated data associated with a user of the consumer device based at least in part by associating user information, application information, and consumer device information associated with the visitor event metadata and the consumer device data, wherein correlating the visitor event metadata and the consumer device data to generate multisource data comprises reconciling inconsistencies between the visitor event metadata and the consumer device data;

identify, from a customer profile database, a consumer profile associated with the visitor event, wherein the consumer profile comprises point-of-sale information and historical visitor event data from the merchant location that are associated with the user; and

update the consumer profile based at least in part on the multisource correlated data, wherein the updated consumer profile is used to facilitate communications with a server.

2. The apparatus of claim 1 , wherein the program code is further configured to, with the processor, cause the apparatus to identify the consumer profile by:

receiving beacon response event metadata associated with the consumer device, wherein the beacon response event metadata is generated by a merchant device in response to communicating with the consumer device; and

identifying the consumer profile based on the beacon response event metadata.

3. The apparatus of claim 2 , wherein the beacon response event metadata comprises application data, location data, or timestamp data.

4. The apparatus of claim 1 , wherein the program code is further configured to, with the processor, cause the apparatus to at least:

provide, for display on the merchant device, an indication of at least one or more of the visitor event and the updated consumer profile.

5. The apparatus of claim 4 , wherein the consumer device data further comprises a customer identifier associated with the user, and wherein the consumer profile is identified based at least in part on the customer identifier.

6. A computer-implemented method comprising:

receiving, from a visitor detection unit, visitor event metadata comprising presence data associated with a visitor event at a merchant location, wherein:

the visitor event metadata is generated in response to a passive infrared motion detection event, and

the visitor event metadata comprises visitor event type data indicating a direction of travel of the consumer device and visitor event timestamp data;

receiving consumer device data associated with the consumer device, wherein the consumer device data comprises application data from at least one application executing on the consumer device, and wherein the consumer device data is generated in response to a BLE event of the at least one application executing on the consumer device;

in a circumstance in which the visitor event metadata is received from the visitor detection unit and the consumer device data is received prior to expiration of a timeout period:

correlating the visitor event metadata and consumer device data to generate multisource correlated data associated with a user of the consumer device based at least in part by associating user information, application information, and consumer device information associated with the visitor event metadata and the consumer device data, wherein correlating the visitor event metadata and the consumer device data to generate multisource data comprises reconciling inconsistencies between the visitor event metadata and the consumer device data;

identifying, from a customer profile database, a consumer profile associated with the visitor event, wherein the consumer profile comprises point-of-sale information and historical visitor event data from the merchant location that are associated with the user; and

updating the consumer profile based at least in part on the multisource correlated data, wherein the updated consumer profile is used to facilitate communications with a server.

7. The computer-implemented method of claim 6 , wherein identifying the consumer profile comprises:

receiving beacon response event metadata associated with the consumer device, wherein the beacon response event metadata is generated by a merchant device in response to communicating with the consumer device; and

identifying the consumer profile based on the beacon response event metadata.

8. The computer-implemented method of claim 7 , wherein the beacon response event metadata comprises application data, location data, or timestamp data.

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

providing, for display on the merchant device, an indication of at least one or more of the visitor event and the updated consumer profile.

10. The computer-implemented method of claim 9 , wherein the consumer device data further comprises a customer identifier associated with the user, and wherein the consumer profile is identified based at least in part on the customer identifier.

11. A computer program product comprising at least one non-transitory computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions configured to:

receive, from a visitor detection unit, visitor event metadata comprising presence data associated with a visitor event at a merchant location, wherein:

the visitor event metadata is generated in response to a passive infrared motion detection event, and

the visitor event metadata comprises visitor event type data indicating a direction of travel of the consumer device and visitor event timestamp data;

receive consumer device data associated with the consumer device, wherein the consumer device data comprises application data from at least one application executing on the consumer device, and wherein the consumer device data is generated in response to a BLE event of the at least one application executing on the consumer device;

in a circumstance in which the visitor event metadata is received from the visitor detection unit and the consumer device data is received prior to expiration of a timeout period:

correlate the visitor event metadata and consumer device data to generate multisource correlated data associated with a user of the consumer device based at least in part by associating user information, application information, and consumer device information associated with the visitor event metadata and the consumer device data, wherein correlating the visitor event metadata and the consumer device data to generate multisource data comprises reconciling inconsistencies between the visitor event metadata and the consumer device data;

identify, from a customer profile database, a consumer profile associated with the visitor event, wherein the consumer profile comprises point-of-sale information and historical visitor event data from the merchant location that are associated with the user; and

update the consumer profile based at least in part on the multisource correlated data, wherein the updated consumer profile is used to facilitate communications with a server.

12. The computer program product of claim 11 , wherein the computer-readable program code portions are further configured to identify the consumer profile by:

receiving beacon response event metadata associated with the consumer device, wherein the beacon response event metadata is generated by a merchant device in response to communicating with the consumer device; and

identifying the consumer profile based on the beacon response event metadata.

13. The computer program product of claim 12 , wherein the beacon response event metadata comprises application data, location data, or timestamp data.

14. The computer program product of claim 11 , wherein the computer-readable program code portions are further configured to:

provide, for display on the merchant device, an indication of at least one or more of the visitor event and the updated consumer profile.

15. The apparatus of claim 1 , wherein the program code is further configured to, with the processor, cause the apparatus to:

transmit a real-time indication of the updated consumer profile to a third-party server.

Assignments (7)
MERGER Recorded Jul 10, 2024
From: SWARM SOLUTIONS, INC.
To: GROUPON SWARM, LLC
Reel/Frame 068262/0756 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 10, 2024
From: GROUPON, INC.
To: BYTEDANCE INC.
Reel/Frame 068172/0344 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 10, 2024
From: DAVIS, RUDDMAN
To: SWARM SOLUTIONS, INC.
Reel/Frame 068262/0731 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 10, 2024
From: GROUPON SWARM, LLC
To: GROUPON, INC.
Reel/Frame 067944/0552 →
RELEASE OF SECURITY INTEREST Recorded Feb 26, 2024
From: JPMORGAN CHASE BANK, N.A.
To: GROUPON, INC.; LIVINGSOCIAL, LLC (F/K/A LIVINGSOCIAL, INC.)
Reel/Frame 066676/0001 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY RIGHTS Recorded Feb 26, 2024
From: JPMORGAN CHASE BANK, N.A.
To: GROUPON, INC.; LIVINGSOCIAL, LLC (F/K/A LIVINGSOCIAL, INC.)
Reel/Frame 066676/0251 →
SECURITY INTEREST Recorded Jul 23, 2020
From: GROUPON, INC.; LIVINGSOCIAL, LLC
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 053294/0495 →
Continuity (3)
Continuation 15926170 · Mar 20, 2018
Continuation 14283151 · May 20, 2014
Related Publication 20200258121A1 · Aug 13, 2020