IP Library Granted Patent US 12,401,860
Granted Patent B2
US 12,401,860 · App. 17/953,105 · Granted Aug 26, 2025

Systems and methods for providing notifications of critical events occurring in live content based on activity data

Inventor: Jordan Mendell (Boca Raton, FL)
Assignee: DK Crown Holdings Inc.
H04N21/4882G07F17/3211G07F17/3237G07F17/3288H04N21/2187H04N21/2353H04N21/25808H04N21/26208H04N21/2625H04N21/41407H04N21/4316H04N21/4518H04N21/4524H04N21/4532H04N21/458H04N21/4753H04N21/478H04N21/6543H04N21/6547H04N21/8126H04N21/8133
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,401,860
App. No.
17/953,105
Granted
Aug 26, 2025
Kind
B2
Abstract

The present disclosure provides live event systems having one or more processors coupled to memory. The live event system can access a plurality of messages associated with a live event broadcasted to a plurality of broadcast receiver devices via a broadcast provider system. The live event system can determine that at least one message of the messages satisfies a condition of a notification generation policy relating to the live event. The live event system can identify, from the broadcast receiver devices, a subset of broadcast receiver devices that satisfy a notification transmission policy relating to the live event. The live event system can transmit instructions to the broadcast provider system, instructions causing the broadcast provider system to communicate with each broadcast receiver device of the subset of broadcast receiver devices and cause each broadcast receiver device of the subset to display a notification identifying the live event.

Claims (33)

1. A method, comprising:

accessing, by one or more processors coupled to memory, a content source that maintains a plurality of messages;

determining, by the one or more processors, based on the plurality of messages accessed via the content source, an increase in a volume of a subset of the plurality of messages that identify a first live event by a determined amount within a first time window relative to a baseline time window;

determining, by the one or more processors, that the increase in the volume of the subset of the plurality of messages that identify the first live event by the determined amount within the first time window satisfies a notification generation threshold;

receiving, by the one or more processors, a request for content from a broadcast receiver device that is presenting a broadcast of a second live event;

selecting, by the one or more processors, a content item that identifies the first live event based on the increase in the volume satisfying the notification generation threshold; and

responsive to the request for content and responsive to determining that the increase in the volume of the subset of the plurality of messages that identify the first live event by the determined amount within the first time window satisfies the notification generation threshold, transmitting, by the one or more processors, instructions to the broadcast receiver device, the instructions configured to cause the broadcast receiver device to display the content item identifying the first live event and including an actionable object that, when interacted with, causes the broadcast receiver device to navigate to a broadcast of the first live event.

2. The method of claim 1 , wherein determining that the notification generation threshold is satisfied is further based on a change in odds associated with the first live event.

3. The method of claim 2 , wherein determining that the change in odds satisfies the notification generation threshold further comprises determining, by the one or more processors, that the change in odds is greater than a predetermined threshold.

4. The method of claim 1 , further comprising maintaining, by the one or more processors, a plurality of user profiles, each user profile of the plurality of user profiles corresponding to a respective user consuming a service of the one or more processors, each of the plurality of user profiles associated with a respective one of a plurality of broadcast receiver devices.

5. The method of claim 4 , further comprising identifying, by the one or more processors, the broadcast receiver device from the plurality of broadcast receiver devices based on the request and one or more attributes of each user profile of the plurality of user profiles.

6. The method of claim 1 , wherein the plurality of messages comprises a plurality of wagers, and wherein accessing the plurality of messages further comprises receiving, by the one or more processors, the plurality of wagers that identify the first live event.

7. The method of claim 6 , wherein receiving the plurality of wagers comprises receiving, by the one or more processors, the plurality of wagers that satisfy a predetermined wager type condition.

8. The method of claim 1 , wherein the plurality of messages comprises a plurality of social media posts, and wherein accessing the plurality of messages further comprises retrieving, by the one or more processors, the plurality of social media posts that identify the first live event.

9. The method of claim 1 , wherein the content item further comprises a second actionable object identifying the second live event that, when interacted with, causes the broadcast receiver device to display a second content item with the broadcast of the second live event.

10. The method of claim 1 , wherein the content item further comprises a second actionable object that, when interacted with, causes the broadcast receiver device to transmit, to the one or more processors, a request to place a wager on the first live event.

11. A system, comprising:

one or more processors coupled to a non-transitory memory, the one or more processors configured to:

access a content source that maintains a plurality of messages;

determine, based on the plurality of messages accessed via the content source, an increase in a volume of a subset of the plurality of messages that identify a first live event by a determined amount within a first time window relative to a baseline time window;

determine that the increase in the volume of the subset of the plurality of messages that identify the first live event by the determined amount within the first time window satisfies a notification generation threshold;

receive a request for content from a broadcast receiver device that is presenting a broadcast of a second live event;

select a content item that identifies the first live event based on the change in the volume of the subset of the plurality of messages that identify the first live event satisfying the notification generation threshold; and

responsive to the request for content and responsive to determining that increase in the volume of the subset of the plurality of messages that identify the first live event by the determined amount within the first time window satisfies the notification generation threshold is satisfied, transmit instructions to the broadcast receiver device, the instructions configured to cause the broadcast receiver device to display the content item identifying the first live event and including an actionable object that, when interacted with, causes the broadcast receiver device to navigate to a broadcast of the first live event.

12. The system of claim 11 , wherein the one or more processors are further configured to determine that the notification generation threshold is satisfied further based on a change in odds associated with the first live event.

13. The system of claim 12 , wherein the one or more processors are further configured to determine that the change in odds satisfies the notification generation threshold by performing operations comprising determining that the change in odds is greater than a predetermined threshold.

14. The system of claim 11 , wherein the one or more processors are further configured to maintain a plurality of user profiles, each user profile of the plurality of user profiles corresponding to a respective user consuming a service of the one or more processors, each of the plurality of user profiles associated with a respective one of a plurality of broadcast receiver devices.

15. The system of claim 14 , wherein the one or more processors are further configured to identify the broadcast receiver device from the plurality of broadcast receiver devices based on the request and one or more attributes of each user profile of the plurality of user profiles.

16. The system of claim 11 , wherein the plurality of messages comprises a plurality of wagers, and wherein the one or more processors are further configured to access the plurality of messages by performing operations comprising receiving the plurality of wagers that identify the first live event.

17. The system of claim 16 , wherein the one or more processors are further configured to receive the plurality of wagers by performing operations comprising receiving the plurality of wagers that satisfy a predetermined wager type condition.

18. The system of claim 11 , wherein the plurality of messages comprises a plurality of social media posts, and wherein the one or more processors are further configured to access the plurality of messages by performing operations comprising retrieving the plurality of social media posts that identify the first live event.

19. The system of claim 11 , wherein the content item further comprises a second actionable object identifying the first live event that, when interacted with, causes the broadcast receiver device to display a second content item with the broadcast of the second live event.

20. The system of claim 11 , wherein the content item further comprises a second actionable object that, when interacted with, causes the broadcast receiver device to transmit, to the one or more processors, a request to place a wager on the first live event.

Assignments (5)
RELEASE OF SECURITY INTEREST Recorded Nov 7, 2024
From: BANC OF CALIFORNIA (FORMERLY KNOWN AS PACIFIC WESTERN BANK)
To: DK CROWN HOLDINGS INC.
Reel/Frame 069315/0578 →
SECURITY INTEREST Recorded Nov 7, 2024
From: DK CROWN HOLDINGS INC.; JACKPOCKET LLC
To: MORGAN STANLEY SENIOR FUNDING, INC.
Reel/Frame 069320/0109 →
CHANGE OF NAME Recorded Oct 3, 2023
From: DRAFTKINGS, INC.
To: DK CROWN HOLDINGS INC.
Reel/Frame 065103/0263 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 28, 2023
From: MENDELL, JORDAN
To: DRAFTKINGS, INC.
Reel/Frame 065057/0153 →
SECURITY INTEREST Recorded Jan 3, 2023
From: DK CROWN HOLDINGS INC.
To: PACIFIC WESTERN BANK
Reel/Frame 062266/0013 →
Continuity (3)
Continuation 17516134 · Nov 1, 2021
Provisional Application 63273580 · Oct 29, 2021
Related Publication 20230135514A1 · May 4, 2023
References Cited (133)
US 5830068A · Brenner et al. · 1998 [cited by applicant]
US 6735487B1 · Marshall et al. · 2004 [cited by applicant]
US 7904924B1 · Heer et al. · 2011 [cited by applicant]
US 8538563B1 · Barber · 2013 [cited by applicant]
US 10664138B2 · Carney et al. · 2020 [cited by applicant]
US 11190736B2 · Kawakami et al. · 2021 [cited by applicant]
US 11217067B1 · Huke et al. · 2022 [cited by applicant]
US 11457285B1 · Mendell · 2022 [cited by examiner]
US 20020054068A1 · Ellis et al. · 2002 [cited by applicant]
US 20020174430A1 · Ellis et al. · 2002 [cited by applicant]
US 20050005291A1 · McGinley · 2005 [cited by applicant]
US 20070157281A1 · Ellis et al. · 2007 [cited by applicant]
US 20080066111A1 · Ellis et al. · 2008 [cited by applicant]
US 20080112690A1 · Shahraray et al. · 2008 [cited by applicant]
US 20080148317A1 · Opaluch · 2008 [cited by applicant]
US 20080182651A1 · Marshall et al. · 2008 [cited by applicant]
US 20090082095A1 · Walker et al. · 2009 [cited by applicant]
US 20090133051A1 · Hildreth · 2009 [cited by applicant]
US 20090158374A1 · Malaure et al. · 2009 [cited by applicant]
US 20090183178A1 · Imai et al. · 2009 [cited by applicant]
US 20090288118A1 · Chang · 2009 [cited by applicant]
US 20100041482A1 · Kumar et al. · 2010 [cited by applicant]
US 20100058423A1 · Yaussy et al. · 2010 [cited by applicant]
US 20100144426A1 · Winner et al. · 2010 [cited by applicant]
US 20100262986A1 · Adimatyam et al. · 2010 [cited by applicant]
US 20110022471A1 · Brueck et al. · 2011 [cited by applicant]
US 20110069940A1 · Shimy et al. · 2011 [cited by applicant]
US 20110078717A1 · Drummond et al. · 2011 [cited by applicant]
US 20110086699A1 · Allen et al. · 2011 [cited by applicant]
US 20120033943A1 · Klappert et al. · 2012 [cited by applicant]
US 20120162515A1 · Lee et al. · 2012 [cited by applicant]
US 20130002716A1 · Walker et al. · 2013 [cited by applicant]
US 20130013625A1 · Yoshida · 2013 [cited by examiner]
US 20130027613A1 · Kim et al. · 2013 [cited by applicant]
US 20130173765A1 · Korbecki · 2013 [cited by applicant]
US 20130179925A1 · Woods et al. · 2013 [cited by applicant]
US 20130225298A1 · Hamlin et al. · 2013 [cited by applicant]
US 20130247120A1 · Milgramm · 2013 [cited by applicant]
US 20130282421A1 · Graff et al. · 2013 [cited by applicant]
US 20140036152A1 · Jackson et al. · 2014 [cited by applicant]
US 20140062696A1 · Packard et al. · 2014 [cited by applicant]
US 20140068692A1 · Archibong et al. · 2014 [cited by applicant]
US 20140129570A1 · Johnson · 2014 [cited by applicant]
US 20140130079A1 · Arora et al. · 2014 [cited by applicant]
US 20140201769A1 · Neumeier et al. · 2014 [cited by applicant]
US 20140282721A1 · Kuncl et al. · 2014 [cited by applicant]
US 20140372876A1 · Bliss et al. · 2014 [cited by applicant]
US 20150070516A1 · Shoemake et al. · 2015 [cited by applicant]
US 20150163547A1 · Whitten · 2015 [cited by applicant]
US 20150172338A1 · Moran et al. · 2015 [cited by applicant]
US 20160088352A1 · Agarwal et al. · 2016 [cited by applicant]
US 20160227281A1 · Abuelsaad et al. · 2016 [cited by applicant]
US 20160337702A1 · Klappert et al. · 2016 [cited by applicant]
US 20170034594A1 · Francis et al. · 2017 [cited by applicant]
US 20170064378A1 · Webster et al. · 2017 [cited by applicant]
US 20170064396A1 · Yun et al. · 2017 [cited by applicant]
US 20170070769A1 · Bostick et al. · 2017 [cited by applicant]
US 20180048936A1 · Gupta et al. · 2018 [cited by applicant]
US 20180060439A1 · Kula et al. · 2018 [cited by applicant]
US 20180108380A1 · Packard et al. · 2018 [cited by applicant]
US 20180214772A1 · Walsh · 2018 [cited by applicant]
US 20190205839A1 · Dotan-Cohen et al. · 2019 [cited by applicant]
US 20190236905A1 · Washington et al. · 2019 [cited by applicant]
US 20190262721A1 · Macinnes et al. · 2019 [cited by applicant]
US 20190268663A1 · Fischer · 2019 [cited by applicant]
US 20190349638A1 · Baek et al. · 2019 [cited by applicant]
US 20190362601A1 · Kline et al. · 2019 [cited by applicant]
US 20190384469A1 · Lo et al. · 2019 [cited by applicant]
US 20200077138A1 · Sawyer et al. · 2020 [cited by applicant]
US 20200213678A1 · Pleiman · 2020 [cited by applicant]
US 20200245017A1 · Ganschow et al. · 2020 [cited by applicant]
US 20200252664A1 · Weinraub · 2020 [cited by applicant]
US 20200294364A1 · Nelson et al. · 2020 [cited by applicant]
US 20200357246A1 · Nelson et al. · 2020 [cited by applicant]
US 20210031105A1 · Ganschow · 2021 [cited by examiner]
US 20210076099A1 · Ganschow et al. · 2021 [cited by applicant]
US 20210217269A1 · Huke et al. · 2021 [cited by applicant]
US 20210256797A1 · Huke et al. · 2021 [cited by applicant]
US 20220103905A1 · Montgomery et al. · 2022 [cited by applicant]
US 20220114339A1 · Aher · 2022 [cited by examiner]
US 20220157127A1 · Tadepalli et al. · 2022 [cited by applicant]
US 20220309873A1 · Russ et al. · 2022 [cited by applicant]
US 20220321951A1 · Chandrashekar et al. · 2022 [cited by applicant]
US 20220377427A1 · Montgomery et al. · 2022 [cited by applicant]
AU 2003100117A4 · 2003 [cited by applicant]
EP 1484723A2 · 2004 [cited by applicant]
EP 4024322A1 · 2022 [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 17/947,444 dated Oct. 11, 2023. [cited by applicant]
Notice of Allowance on U.S. Appl. No. 17/943,930 dated Oct. 17, 2023. [cited by applicant]
Final Office Action on U.S. Appl. No. 17/516,150 dated May 27, 2022. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 17/516,150 dated Jan. 28, 2022. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 17/516,134 dated Feb. 1, 2022. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 17/516,197 dated Jan. 13, 2022. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 17/516,200 dated Dec. 21, 2021. [cited by applicant]
Notice of Allowance on U.S. Appl. No. 17/516,134 dated Jun. 6, 2022. [cited by applicant]
Notice of Allowance on U.S. Appl. No. 17/516,197 dated May 6, 2022. [cited by applicant]
Notice of Allowance on U.S. Appl. No. 17/516,200 dated Apr. 27, 2022. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 17/976,130 dated Sep. 14, 2023. [cited by applicant]
Notice of Allowance on U.S. Appl. No. 17/516,150 dated Sep. 21, 2023. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 17/976,107 dated Jan. 5, 2024. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 17/976,141 dated Nov. 29, 2023. [cited by applicant]
Notice of Allowance on U.S. Appl. No. 17/976,097 dated Nov. 7, 2023. [cited by applicant]
Notice of Allowance on U.S. Appl. No. 17/976,130 dated Jan. 26, 2024. [cited by applicant]
Final Office Action on U.S. Appl. No. 17/516,150 dated Mar. 10, 2023. [cited by applicant]
Final Office Action on U.S. Appl. No. 17/976,097 dated Jul. 10, 2023. [cited by applicant]
Final Office Action on U.S. Appl. No. 17/976,107 dated Aug. 11, 2023. [cited by applicant]
Final Office Action on U.S. Appl. No. 17/976,130 dated Jun. 1, 2023. [cited by applicant]
Final Office Action on U.S. Appl. No. 17/976,141 dated Jul. 13, 2023. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 17/976,097 dated Mar. 2, 2023. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 17/976,107 dated Mar. 28, 2023. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 17/976,141 dated Mar. 16, 2023. [cited by applicant]
Notice of Allowance on U.S. Appl. No. 17/976,120 dated May 9, 2023. [cited by applicant]
Final Office Action on U.S. Appl. No. 17/976,107 dated May 8, 2024. [cited by applicant]
Final Office Action on U.S. Appl. No. 17/947,444 dated Apr. 3, 2024. [cited by applicant]
Final Office Action on U.S. Appl. No. 17/976,141 dated Mar. 12, 2024. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 17/516,150 dated Nov. 18, 2022. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 17/976,120 dated Jan. 25, 2023. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 17/976,130 dated Feb. 2, 2023. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 17/947,444 dated Sep. 23, 2024. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 18/398,538 dated Oct. 7, 2024. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 18/408,368 dated Sep. 12, 2024. [cited by applicant]
Notice of Allowance on U.S. Appl. No. 17/976,107 dated Sep. 3, 2024. [cited by applicant]
Notice of Allowance on U.S. Appl. No. 17/976,141 dated Jul. 17, 2024. [cited by applicant]
Notice of Allowance on U.S. Appl. No. 18/408,359 dated Aug. 5, 2024. [cited by applicant]
Final Office Action on U.S. Appl. No. 17/947,444 dated Feb. 26, 2025. [cited by applicant]
Final Office Action on U.S. Appl. No. 18/398,538 dated Mar. 20, 2025. [cited by applicant]
Notice of Allowance on U.S. Appl. No. 18/451,718 dated Mar. 14, 2025. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 18/451,718 dated Nov. 20, 2024. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 18/672,565 dated Dec. 19, 2024. [cited by applicant]
Final Office Action on U.S. Appl. No. 18/408,368 dated Apr. 3, 2025. [cited by applicant]
Final Office Action on U.S. Appl. No. 18/672,565 dated Mar. 31, 2025. [cited by applicant]
Notice of Allowance on U.S. Appl. No. 17/947,444 dated Jun. 10, 2025. [cited by applicant]
Notice of Allowance on U.S. Appl. No. 18/672,565 dated Jun. 27, 2025. [cited by applicant]