IP Library › Granted Patent US 12,363,393
Granted Patent B2
US 12,363,393 · App. 18/451,718 · Granted Jul 15, 2025

Systems and methods for controlling computer recorded data based on client messages

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,363,393
App. No.
18/451,718
Granted
Jul 15, 2025
Kind
B2
Abstract

The present disclosure provides event capture systems having one or more processors coupled to memory. The event capture system can identify a wager corresponding to a live event associated with a client device. The event capture system can identify a broadcast receiver device corresponding to the client device. The event capture system can generate recording instructions for the broadcast receiver device that cause the broadcast receiver device to initiate a recording of a broadcast of the live event. The event capture system can transmit the recording instructions to the broadcast receiver device to cause the broadcast receiver device to schedule a recording for the broadcast of the live event.

Claims (37)

1. A method, comprising:

receiving, by one or more processors coupled to memory, from a client device, a wager corresponding to a live event and identifying a player profile, the wager corresponding to a specified wager type;

determining, by the one or more processors, that the specified wager type of the wager matches a corresponding wager type identified in a configuration setting of the player profile, the configuration setting indicating that recordings are to be initiated for live events associated with wagers having the corresponding wager type; and

responsive to the wager and responsive to determining that the specified wager type matches the corresponding wager type of the configuration setting of the player profile:

identifying, by the one or more processors, a broadcast receiver device corresponding to the player profile;

generating, by the one or more processors, recording instructions for the broadcast receiver device that cause the broadcast receiver device to initiate a recording of a broadcast of the live event; and

transmitting, by the one or more processors, the recording instructions to the broadcast receiver device to cause the broadcast receiver device to schedule a recording for the broadcast of the live event.

2. The method of claim 1 , further comprising determining, by the one or more processors, that a start time of the live event has been delayed to a second start time.

3. The method of claim 2 , further comprising transmitting, by the one or more processors, second instructions that cause the broadcast receiver device to reschedule the recording for the broadcast of the live event based on the second start time.

4. The method of claim 2 , wherein determining that the start time of the live event has been delayed is based on a broadcast schedule of the live event received from a third-party data source.

5. The method of claim 1 , wherein the wager includes second instructions to update the player profile to include an indication to record live events associated with wagers.

6. The method of claim 1 , further comprising:

receiving, by the one or more processors, a request to update the configuration setting of the player profile; and

updating, by the one or more processors, the configuration setting of the player profile responsive to the request.

7. The method of claim 1 , further comprising maintaining, by the one or more processors, in the player profile, a data structure storing an identifier of the client device in association with an identifier of the broadcast receiver device.

8. The method of claim 1 , wherein the recording instructions cause the broadcast receiver device to initiate a recording of a portion of the live event corresponding to the wager.

9. The method of claim 1 , wherein generating the recording instructions comprises generating, by the one or more processors, a notification for display by the broadcast receiver device that indicates the recording of the broadcast of the live event has been scheduled.

10. The method of claim 9 , wherein the notification comprises information associated with the wager.

11. A system, comprising:

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

receive, from a client device, a wager corresponding to a live event and identifying a player profile, the wager corresponding to a specified wager type;

determine that the specified wager type of the wager matches a corresponding wager type identified in a configuration setting of the player profile, the configuration setting indicating that recordings are to be initiated for live events associated with wagers having the corresponding wager type; and

responsive to the wager and responsive to determining that the specified wager type matches the corresponding wager type of the configuration setting of the player profile:

identify a broadcast receiver device corresponding to the player profile;

generate recording instructions for the broadcast receiver device that cause the broadcast receiver device to initiate a recording of a broadcast of the live event; and

transmit the recording instructions to the broadcast receiver device to cause the broadcast receiver device to schedule a recording for the broadcast of the live event.

12. The system of claim 11 , wherein the one or more processors are further configured to determine that a start time of the live event has been delayed to a second start time.

13. The system of claim 12 , wherein the one or more processors are further configured to transmit second instructions that cause the broadcast receiver device to reschedule the recording for the broadcast of the live event based on the second start time.

14. The system of claim 12 , wherein the one or more processors are further configured to determine that the start time of the live event has been delayed based on a broadcast schedule of the live event received from a third-party data source.

15. The system of claim 11 , wherein the wager includes second instructions to update the player profile to include an indication to record live events associated with wagers.

16. The system of claim 11 , wherein the one or more processors are further configured to:

receive a request to update the configuration setting of the player profile; and

update the configuration setting of the player profile responsive to the request.

17. The system of claim 11 , wherein the one or more processors are further configured to maintain, in the player profile, a data structure storing an identifier of the client device in association with an identifier of the broadcast receiver device.

18. The system of claim 11 , wherein the recording instructions cause the broadcast receiver device to initiate a recording of a portion of the live event corresponding to the wager.

19. The system of claim 11 , wherein the one or more processors are further configured to generating the recording instructions to cause the broadcast receiver device to display a notification that indicates the recording of the broadcast of the live event has been scheduled.

20. The system of claim 19 , wherein the notification comprises information associated with the wager.

Assignments (3)
SECURITY INTEREST Recorded Nov 7, 2024
From: DK CROWN HOLDINGS INC.; JACKPOCKET LLC
To: MORGAN STANLEY SENIOR FUNDING, INC.
Reel/Frame 069320/0109 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 28, 2023
From: MENDELL, JORDAN
To: DRAFTKINGS, INC.
Reel/Frame 065057/0448 →
CHANGE OF NAME Recorded Sep 28, 2023
From: DRAFTKINGS, INC.
To: DK CROWN HOLDINGS INC.
Reel/Frame 065081/0172 →
Continuity (3)
Continuation 17976120 · Oct 28, 2022
Provisional Application 63273580 · Oct 29, 2021
Related Publication 20230396853A1 · Dec 7, 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 applicant]
US 20020054068A1 · Ellis · 2002 [cited by examiner]
US 20020174430A1 · Ellis · 2002 [cited by examiner]
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 · 2008 [cited by examiner]
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 · 2012 [cited by examiner]
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 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 20150324379A1 · Danovitz · 2015 [cited by examiner]
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 · 2020 [cited by examiner]
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 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 20210256797A1 · Huke et al. · 2021 [cited by applicant]
US 20220103905A1 · Montgomery · 2022 [cited by examiner]
US 20220114339A1 · Aher et al. · 2022 [cited by applicant]
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/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]
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]
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. 17/953,105 dated Jul. 5, 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/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]
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]
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/516,150 dated May 27, 2022. [cited by applicant]
Non-Final Office Action on US 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,150 dated Nov. 18, 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]
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,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/976,141 dated Mar. 16, 2023. [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]
Notice of Allowance on U.S. Appl. No. 17/976,120 dated May 9, 2023. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 18/398,538 dated Oct. 7, 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/672,565 dated Dec. 19, 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]
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/953,105 dated Apr. 30, 2025. [cited by applicant]