IP Library Granted Patent US 12,324,060
Granted Patent B2
US 12,324,060 · App. 18/417,045 · Granted Jun 3, 2025

System and method for using a mobile device as an input device for surveys at a live event

Inventor: Jovan Hutton Pulitzer (Frisco, TX)
Assignee: Tesla Laboratories, LLC
H04W88/02G06F16/40G06F16/9554G06Q10/02G06Q30/0203H04L12/1859H04L43/10H04L67/306H04W4/021H04W4/029H04W4/21H04W4/33G06F2212/15H04L51/48H04L67/52
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,324,060
App. No.
18/417,045
Granted
Jun 3, 2025
Kind
B2
Abstract

A method is provided for interacting with audience members in an event, each of the potential attendees having available thereto a unique identifier. The method comprises creating, for an attendee, a unique ID (UID) on a mobile wireless device (MWD) by the steps of inputting to the MWD one of the unique identifiers, combining the obtained unique identifier with a UID time stamp at the time of creation of the UID; receiving with a server on a first wireless channel communications from the MWD; registering the UID at the physical location of the event; generating a visual query; displaying on the MWD response indicators; receiving at the server from the registered attendee a response, to the query over the first wireless channel; and storing in a database on the server the received response in association with the displayed query.

Claims (41)

1. A method comprising:

creating, for a participating attendee of an event, a unique ID (UID) on a mobile wireless device (MWD), including:

scanning a code by the MWD as a unique potential attendee identifier (UPAI);

combining the UPAI with a UID time stamp to provide the UID, wherein the UID includes a UPAI portion and a UID timestamp portion so as to distinguish two different UIDs having a duplicate UPAI portion;

verifying, by a server, the UID is unique by comparing the UID to one or more other UIDs in a database on the server to determine if a duplicate UID exists in the database, resulting in a verified UID; and

accepting and storing the verified UID in the database.

2. The method of claim 1 , wherein the unique ID created for the participating attendee of the event is created proximate in time to an occurrence of a predetermined time of the event.

3. The method of claim 1 , wherein the event is defined as occurring at a predetermined time, wherein the event has a finite number of participating attendees and an associated finite number of UPAIs allocated to the event, and wherein each of the participating attendees have available thereto one of the UPAIs for the event.

4. The method of claim 3 , wherein the event is a physical venue location associated with the event and wherein each of the participating attendees is in physical proximity to the physical venue location associated with the event.

5. The method of claim 1 , wherein the code is a machine-readable code or an identifier on a ticket.

6. The method of claim 1 , wherein the participating attendee is prompted via an external prompting source proximate in time to the event to scan the code using the MWD.

7. The method of claim 1 , further comprising:

generating at the server a visual query;

displaying the visual query;

displaying response indicators for responding to the visual query on the MWD;

receiving, at the server, at least one response to the visual query; and

storing in the database on the server the received at least one response in association with the visual query.

8. The method of claim 7 , wherein the response indicators comprise at least one of one or more alphabetic symbols, one or more numeric symbols, one or more shapes, one or more colors, and one or more icons.

9. The method of claim 7 , further comprising generating, at the server, another visual query, wherein the generation of the other visual query is influenced by the received at least one response.

10. The method of claim 7 , further comprising defining the received at least one response as a confirmation that at least one participating attendee participated.

11. A system comprising:

a mobile wireless device (MWD) to create, for a participating attendee of an event, a unique ID (UID), wherein, to create the UID, the MWD is configured to:

scan a code as a unique potential attendee identifier (UPAI); and

combine the UPAI with a UID time stamp to provide the UID, wherein the UID includes a UPAI portion and a UID timestamp portion so as to distinguish two different UIDs having a duplicate UPAI portion; and

a server configured to:

verify the UID is unique by comparing the UID to one or more other UIDs in a database on the server to determine if a duplicate UID exists in the database, resulting in a verified UID; and

accept and store the verified UID in the database.

12. The system of claim 11 , wherein the unique ID created for the participating attendee of the event is created proximate in time to an occurrence of a predetermined time of the event.

13. The system of claim 11 , wherein the event is defined as occurring at a predetermined time, wherein the event has a finite number of participating attendees and an associated finite number of UPAIs allocated to the event, and wherein each of the participating attendees have available thereto one of the UPAIs for the event.

14. The system of claim 13 , wherein the event is a physical venue location and wherein each of the participating attendees is in physical proximity to the physical venue location associated with the event.

15. The system of claim 11 , wherein the code is a machine-readable code or an identifier on a ticket.

16. The system of claim 11 , wherein the participating attendee is prompted via an external prompting source proximate in time to the event to scan the code using the MWD.

17. The system of claim 11 , wherein the server is further configured to:

generate a visual query;

cause the visual query to be displayed;

cause response indicators for responding to the visual query to be displayed on the MWD;

receive at least one response to the visual query; and

store in the database the received at least one response in association with the visual query.

18. The system of claim 17 , wherein the response indicators comprise at least one of one or more alphabetic symbols, one or more numeric symbols, one or more shapes, one or more colors, and one or more icons.

19. The system of claim 17 , wherein the server is further configured to generate another visual query, wherein the generation of the other visual query is influenced by the received at least one response.

20. The system of claim 17 , wherein the server is further configured to define the received at least one response as a confirmation that at least one participating attendee participated.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 19, 2024
From: PULITZER, JOVAN HUTTON
To: TESLA LABORATORIES, LLC
Reel/Frame 066177/0601 →
Continuity (54)
Continuation 17879899 · Aug 3, 2022
Continuation 17073866 · Oct 19, 2020
Continuation 16730328 · Dec 30, 2019
Continuation 16242258 · Jan 8, 2019
Continuation 15601849 · May 22, 2017
Continuation In Part 15453226 · Mar 8, 2017
Continuation In Part 15402738 · Jan 10, 2017
Continuation In Part 15360697 · Nov 23, 2016
Continuation In Part 15146464 · May 4, 2016
Provisional Application 62350947 · Jun 16, 2016
Provisional Application 62350838 · Jun 16, 2016
Provisional Application 62351026 · Jun 16, 2016
Provisional Application 62351015 · Jun 16, 2016
Provisional Application 62350819 · Jun 16, 2016
Provisional Application 62350984 · Jun 16, 2016
Provisional Application 62350826 · Jun 16, 2016
Provisional Application 62350911 · Jun 16, 2016
Provisional Application 62350966 · Jun 16, 2016
Provisional Application 62350999 · Jun 16, 2016
Provisional Application 62347946 · Jun 9, 2016
Provisional Application 62347927 · Jun 9, 2016
Provisional Application 62347957 · Jun 9, 2016
Provisional Application 62347954 · Jun 9, 2016
Provisional Application 62347940 · Jun 9, 2016
Provisional Application 62319161 · Apr 6, 2016
Provisional Application 62316745 · Apr 1, 2016
Provisional Application 62305349 · Mar 8, 2016
Provisional Application 62305417 · Mar 8, 2016
Provisional Application 62305427 · Mar 8, 2016
Provisional Application 62305408 · Mar 8, 2016
Provisional Application 62305354 · Mar 8, 2016
Provisional Application 62305345 · Mar 8, 2016
Provisional Application 62305420 · Mar 8, 2016
Provisional Application 62305431 · Mar 8, 2016
Provisional Application 62277918 · Jan 12, 2016
Provisional Application 62277899 · Jan 12, 2016
Provisional Application 62277888 · Jan 12, 2016
Provisional Application 62277914 · Jan 12, 2016
Provisional Application 62277917 · Jan 12, 2016
Provisional Application 62277941 · Jan 12, 2016
Provisional Application 62277943 · Jan 12, 2016
Provisional Application 62277903 · Jan 12, 2016
Provisional Application 62277270 · Jan 11, 2016
Provisional Application 62258990 · Nov 23, 2015
Provisional Application 62258988 · Nov 23, 2015
Provisional Application 62258987 · Nov 23, 2015
Provisional Application 62258985 · Nov 23, 2015
Provisional Application 62258989 · Nov 23, 2015
Provisional Application 62258996 · Nov 23, 2015
Provisional Application 62258994 · Nov 23, 2015
Provisional Application 62258983 · Nov 23, 2015
Provisional Application 62258982 · Nov 23, 2015
Provisional Application 62258997 · Nov 23, 2015
Related Publication 20240206015A1 · Jun 20, 2024
References Cited (55)
US 5226177A · Nickerson · 1993 [cited by applicant]
US 5273437A · Caldwell · 1993 [cited by applicant]
US 5801754A · Ruybal et al. · 1998 [cited by applicant]
US 5993314A · Dannenberg · 1999 [cited by applicant]
US 6650903B2 · Inselberg · 2003 [cited by applicant]
US 6760595B2 · Inselberg · 2004 [cited by applicant]
US 8229093B2 · Martin · 2012 [cited by applicant]
US 8391825B2 · Arseneau · 2013 [cited by applicant]
US 8417221B2 · Shaw · 2013 [cited by applicant]
US 8520502B2 · Tenny et al. · 2013 [cited by applicant]
US 9060039B2 · Walsh et al. · 2015 [cited by applicant]
US 9160692B2 · Socolof · 2015 [cited by applicant]
US 9226156B2 · O'Toole · 2015 [cited by applicant]
US 9646382B2 · Hawkins · 2017 [cited by applicant]
US 9817557B2 · Gresham et al. · 2017 [cited by applicant]
US 9836755B2 · Zamer et al. · 2017 [cited by applicant]
US 10176486B2 · Pulitzer · 2019 [cited by applicant]
US 10178710B2 · Pulitzer · 2019 [cited by applicant]
US 10353982B1 · Kumar et al. · 2019 [cited by applicant]
US 10524309B2 · Pulitzer · 2019 [cited by applicant]
US 10547742B2 · Pulitzer · 2020 [cited by applicant]
US 10813168B2 · Pulitzer · 2020 [cited by applicant]
US 11012536B2 · Awad · 2021 [cited by examiner]
US 11412575B2 · Pulitzer · 2022 [cited by applicant]
US 11683414B2 · Pulitzer · 2023 [cited by examiner]
US 11882628B2 · Pulitzer · 2024 [cited by examiner]
US 20040158865A1 · Kubler et al. · 2004 [cited by applicant]
US 20070028272A1 · Lockton · 2007 [cited by applicant]
US 20070112648A1 · Martin · 2007 [cited by applicant]
US 20070294096A1 · Randall et al. · 2007 [cited by applicant]
US 20090271740A1 · Ryan-Hutton et al. · 2009 [cited by applicant]
US 20100262932A1 · Pan · 2010 [cited by applicant]
US 20100306064A1 · Inselburg · 2010 [cited by applicant]
US 20110028213A1 · Dusenberry et al. · 2011 [cited by applicant]
US 20110271295A1 · Redmann et al. · 2011 [cited by applicant]
US 20120221962A1 · Lew et al. · 2012 [cited by applicant]
US 20130116044A1 · Schwartz · 2013 [cited by applicant]
US 20130157693A1 · Mercuri et al. · 2013 [cited by applicant]
US 20150012308A1 · Snyder · 2015 [cited by applicant]
US 20150149619A1 · Tsuji et al. · 2015 [cited by applicant]
US 20150271631A1 · Porter · 2015 [cited by applicant]
US 20150281878A1 · Roundtree et al. · 2015 [cited by applicant]
US 20160110467A1 · Hern · 2016 [cited by applicant]
US 20160156638A1 · Somani et al. · 2016 [cited by applicant]
US 20160335564A1 · Downy et al. · 2016 [cited by applicant]
US 20170018004A1 · Walden · 2017 [cited by applicant]
US 20170155761A1 · Pulitzer · 2017 [cited by applicant]
US 20170280298A1 · Mycek et al. · 2017 [cited by applicant]
US 20190082049A1 · Pulitzer · 2019 [cited by applicant]
US 20210281677A1 · Pulitzer · 2021 [cited by applicant]
Anonymous: “Does an app exist to auto-launch an app when . . . | Android Development and Hacking”, Jun. 5, 2017 (Jun. 5, 2017), pp. 1-4, XP055652647, Retrieved from the Internet: URL: https://forum.xda-developers.com/sh… [cited by applicant]
Anonymous: “NFC Basics | Android Developers”, Feb. 19, 2014 (Feb. 19, 2014), XP055332687, Retrieved from the Internet: URL: http://web.archive.org/web/20140219150611/http://developer.android.com/guide/topics/connectivit… [cited by applicant]
EP: Article 94(3) Communication of 16869004.8 (related case); Jan. 2, 2020; 8 pages. [cited by applicant]
EPO: Extended European Search Report of EP Application No. 21217336.3; Mar. 9, 2022; David Hardeman; 8 pages. [cited by applicant]
PCT: International Search Report and Written Opinion of PCT/US16/31015; Aug. 23, 2016. [cited by applicant]