IP Library › Granted Patent US 12,200,311
Granted Patent B2
US 12,200,311 · App. 17/976,107 · Granted Jan 14, 2025

Systems and methods for generating recording instructions based on detected conditions of live events

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,200,311
App. No.
17/976,107
Granted
Jan 14, 2025
Kind
B2
Abstract

A method is shown. The method includes maintaining a plurality of player profiles corresponding to players consuming a service of the one or more processors, each of the plurality of player profiles associated with a respective one of the plurality of broadcast receiver devices. The method includes maintaining a plurality of live events to monitor. The method includes identifying a subset having one or more attributes that satisfy a content selection policy relating to a live event. The method includes determining from data identifying the live event accessed via a data feed, that the live event has started. The method includes transmitting instructions to the broadcast provider system that cause the broadcast provider system to communicate with each broadcast receiver device and cause the broadcast receiver device to i) display a notification indicating that the live event has started or ii) initiate recording of the live event.

Claims (41)

1. A method, comprising:

maintaining, by one or more processors coupled to memory in communication with a plurality of broadcast receiver devices, a plurality of player profiles corresponding to players consuming a service of the one or more processors, each of the plurality of player profiles associated with a respective broadcast receiver device of the plurality of broadcast receiver devices;

maintaining, by the one or more processors, a plurality of live events to monitor;

identifying, by the one or more processors, a player profile of the plurality of player profiles that indicates the respective broadcast receiver device corresponding to the player profile is to record a broadcast of a live event of the plurality of live events according to a broadcast schedule;

determining, by the one or more processors, from data identifying the live event accessed via a data feed, that a start time of the live event has deviated from the broadcast schedule;

determining, by the one or more processors, that the player profile includes a first configuration setting that authorizes the respective broadcast receiver device to receive updated recording schedules for live events, and a second configuration setting that authorizes the respective broadcast receiver device to receive notifications for display with broadcast content;

responsive to determining that the player profile includes the first configuration setting and the second configuration setting, generating, by the one or more processors, instructions for the respective broadcast receiver device corresponding to the player profile, the instructions configured to cause the respective broadcast receiver device to (i) display a notification indicating that the live event has started at the start time and (ii) initiate recording of the broadcast of the live event at the start time; and

transmitting, by the one or more processors, responsive to determining that the live event has started, the instructions to the respective broadcast receiver device corresponding to the player profile, causing the respective broadcast receiver device to (i) display the notification indicating that the live event has started at the start time and (ii) initiate recording of the broadcast of the live event at the start time.

2. The method of claim 1 , wherein the data identifying the live event is obtained from a conditional event service via which conditional events of the live event are monitored.

3. The method of claim 1 , wherein the data feed is the broadcast of the live event, and wherein determining that the live event has started comprises detecting a start condition in the broadcast of the live event.

4. The method of claim 1 , wherein maintaining the plurality of live events to monitor further comprises:

receiving, by the one or more processors, from a broadcast provider system, an indication of an additional live event; and

updating, by the one or more processors, the plurality of live events to include the additional live event.

5. The method of claim 1 , wherein identifying the player profile further comprises:

calculating, by the one or more processors, a content selection score for each player profile of the plurality of player profiles; and

identifying, by the one or more processors, the player profile further based on the content selection score for each player profile of the plurality of player profiles.

6. The method of claim 1 , wherein determining the start time of the live event comprises monitoring, by the one or more processors, the data feed for an indication that the live event has started.

7. The method of claim 1 , wherein determining the start time of the live event comprises detecting, by the one or more processors, that a predetermined event type has occurred in the broadcast corresponding to the live event.

8. The method of claim 1 , further comprising generating, by the one or more processors, the notification indicating that the live event has started, the notification comprising an actionable object that causes the broadcast receiver device displaying the notification to display the broadcast of the live event.

9. The method of claim 1 , further comprising determining, by the one or more processors, a duration of the live event, and wherein the instructions further include an indication of the duration of the live event.

10. A system, comprising:

one or more processors coupled to memory and in communication with a plurality of broadcast receiver devices, the one or more processors configured to:

maintain a plurality of player profiles corresponding to players consuming a service of the one or more processors, each of the plurality of player profiles associated with a respective broadcast receiver device of the plurality of broadcast receiver devices;

maintain a plurality of live events to monitor;

identify a player profile of the plurality of player profiles that indicates the respective broadcast receiver device corresponding to the player profile is to record a broadcast of a live event of the plurality of live events according to a broadcast schedule;

determine, from data identifying the live event accessed via a data feed, that a start time of the live event has deviated from the broadcast schedule;

determine that the player profile includes a first configuration setting that authorizes the respective broadcast receiver device to receive updated recording schedules for live events, and a second configuration setting that authorizes the respective broadcast receiver device to receive notifications for display with broadcast content;

responsive to determining that the player profile includes the first configuration setting and the second configuration setting, generate instructions for the respective broadcast receiver device corresponding to the player profile, the instructions configured to cause the respective broadcast receiver device to (i) display a notification indicating that the live event has started at the start time and (ii) initiate recording of the broadcast of the live event at the start time; and

transmit, responsive to determining that the live event has started, the instructions to the respective broadcast receiver device corresponding to the player profile, causing the respective broadcast receiver device to (i) display the notification indicating that the live event has started at the start time or (ii) initiate recording of the live event at the start time.

11. The system of claim 10 , wherein the data identifying the live event is obtained from a conditional event service via which conditional events of the live event are monitored.

12. The system of claim 10 , wherein the data feed is the broadcast of the live event, and wherein to determine that the live event has started, the one or more processors are further configured to detect a start condition in the broadcast of the live event.

13. The system of claim 10 , wherein to maintain the plurality of live events to monitor, the one or more processors are further configured to:

receive, from a broadcast provider system, an indication of an additional live event; and

update the plurality of live events to include the additional live event.

14. The system of claim 10 , wherein to identify the player profile, the one or more processors are further configured to:

calculate a content selection score for each player profile of the plurality of player profiles; and

identify the player profile further based on the content selection score for each player profile of the plurality of player profiles.

15. The system of claim 10 , wherein to determine the start time of the live event, the one or more processors are further configured to monitor the data feed for an indication that the live event has started.

16. The system of claim 10 , wherein to determine the start time of the live event, the one or more processors are further configured to detect that a predetermined event type has occurred in the broadcast corresponding to the live event.

17. The system of claim 10 , wherein the one or more processors are further configured to generate the notification indicating that the live event has started, the notification comprising an actionable object that causes the broadcast receiver device displaying the notification to display the broadcast of the live event.

18. The system of claim 10 , wherein the one or more processors are further configured to determine a duration of the live event, and wherein the instructions further include an indication of the duration of the 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 →
SECURITY INTEREST Recorded Jan 3, 2023
From: DK CROWN HOLDINGS INC.
To: PACIFIC WESTERN BANK
Reel/Frame 062266/0013 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 28, 2022
From: MENDELL, JORDAN
To: DRAFTKINGS, INC.
Reel/Frame 061583/0233 →
Continuity (2)
Provisional Application 63273580 · Oct 29, 2021
Related Publication 20230137066A1 · May 4, 2023
References Cited (118)
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 applicant]
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 · 2008 [cited by examiner]
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 · 2009 [cited by examiner]
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 · 2012 [cited by examiner]
US 20120162515A1 · Lee et al. · 2012 [cited by applicant]
US 20130002716A1 · Walker et al. · 2013 [cited by applicant]
US 20130013625A1 · Yoshida et al. · 2013 [cited by applicant]
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 examiner]
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 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 · 2016 [cited by examiner]
US 20160337702A1 · Klappert et al. · 2016 [cited by applicant]
US 20170034594A1 · Francis et al. · 2017 [cited by applicant]
US 20170064378A1 · Webster · 2017 [cited by examiner]
US 20170064396A1 · Yun et al. · 2017 [cited by applicant]
US 20170070769A1 · Bostick et al. · 2017 [cited by applicant]
US 20180048936A1 · Gupta · 2018 [cited by examiner]
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 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 examiner]
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 et al. · 2021 [cited by applicant]
US 20210076099A1 · Ganschow et al. · 2021 [cited by applicant]
US 20210217269A1 · Huke et al. · 2021 [cited by applicant]
US 20220103905A1 · Montgomery et al. · 2022 [cited by applicant]
US 20220114339A1 · Aher et al. · 2022 [cited by applicant]
US 20220157127A1 · Tadepalli et al. · 2022 [cited by applicant]
US 20220309873A1 · Russ · 2022 [cited by examiner]
US 20220321951A1 · Chandrashekar et al. · 2022 [cited by applicant]
US 20220377427A1 · Montgomery et al. · 2022 [cited by applicant]
EP 1484723A2 · 2004 [cited by applicant]
EP 4024322A1 · 2022 [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/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]
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/516,150 dated Mar. 10, 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,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,097 dated Jul. 10, 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,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/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]
Notice of Allowance on U.S. Appl. No. 17/976,097 dated Nov. 7, 2023. [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,130 dated Jan. 26, 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/953,105 dated Jul. 5, 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/953,105 dated Nov. 21, 2024. [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. 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]