IP Library Granted Patent US 12,226,699
Granted Patent B2
US 12,226,699 · App. 18/300,902 · Granted Feb 18, 2025

Systems and methods for prioritizing content packets based on a dynamically updated list of content filtering rules

Inventors: Jonathan Nguyen (Cambridge, MA); Daniel Kesack (Ipswich, MA); William Hester (Boston, MA); Sophie Dasinger (Cambridge, MA); Edward Zaleski (New Berlin, WI); Ethan Haskell (Boston, MA); Corey Shtasel-Gottlieb (Cambridge, MA)
Assignee: DK Crown Holdings Inc.
A63F13/65A63F13/355A63F13/46A63F13/828H04L67/141H04L67/55H04W4/18H04W4/21G06F40/106H04L67/01H04L67/02
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,226,699
App. No.
18/300,902
Granted
Feb 18, 2025
Kind
B2
Abstract

Systems and methods for prioritizing content packets based on a dynamically updated list of content filtering rules are described. A system is configured to identify an application executing on a client device to which to transmit content, the application associated with an account and determine that the application is configured with a configuration setting to apply a content filtering policy corresponding to a list of players including one or more players included in one or more lineups associated with the account. The system can receive a content item from a content source and determine one or more player tags associated with the content item. The system can determine that the content item includes a player tag corresponding to a player included in the list of players and transmit the content item to the client device for insertion in a content feed provided by the application responsive to the determination.

Claims (57)

1. A method, comprising:

determining, by one or more servers, that a first content item of a plurality of candidate content items includes a player tag that identifies a player included in a lineup associated with a client device;

upon determining that the first content item includes the player tag, transmitting, by the one or more servers, the first content item to the client device to update a content feed of an application executing on the client device, the content feed updated based on a first priority score of the first content item and a second priority score of a second content item in the content feed;

upon receiving a request to disable a content filtering policy, selecting, by the one or more servers, a third content item of the plurality of candidate content items having a second player tag that does not identify any player included in the lineup; and

transmitting, by the one or more servers, the third content item to the client device for presentation by the application in the content feed presented by the application.

2. The method of claim 1 , further comprising:

receiving, by the one or more servers, a request for content from the client device; and

transmitting, by the one or more servers, the first content item to the client device in response to the request.

3. The method of claim 1 , wherein the first content item is selected responsive to detecting an update to the lineup associated with the client device.

4. The method of claim 1 , further comprising:

establishing, by the one or more servers, a web socket connection between the one or more servers and the application executing on the client device; and

transmitting, by the one or more servers, the first content item to the client device responsive to determining that the web socket connection is active.

5. The method of claim 4 , further comprising storing, by the one or more servers, a request to transmit the first content item in a queue prior to the web socket connection being active.

6. The method of claim 1 , wherein the client device accesses functionality of the one or more servers via an account, the method further comprising:

maintaining, by the one or more servers, a plurality of lineups associated with the account, the plurality of lineups including the lineup; and

updating, by the one or more servers, the account by modifying an existing lineup of the plurality of lineups or adding a new lineup to the plurality of lineups.

7. The method of claim 1 , further comprising:

determining, by the one or more servers, that a third player has been added to the lineup;

selecting, by the one or more servers, a fourth content item including a third player tag corresponding to the third player; and

transmitting, by the one or more servers, the fourth content item to the client device to update the content feed of the application executing on the client device.

8. The method of claim 1 , further comprising:

determining, by the one or more servers, that a second lineup including a set of players associated with the client device has expired;

removing, by the one or more servers, at least one player of the set of players from the second lineup responsive to determining that the second lineup has expired; and

updating, by the one or more servers, the content feed of the application by removing a fourth content item including a fourth player tag that corresponds to the at least one player.

9. The method of claim 1 , wherein the application is configured to display an actionable item that when selected, applies the content filtering policy to filter the content presented by the application.

10. The method of claim 1 , further comprising:

receiving, by the one or more servers, the first content item from a first content source in a first content format; and

converting, by the one or more servers, the first content item from the first content format to a second content format configured to be presented in the application executing on the client device.

11. A system, comprising:

one or more servers configured to:

determine that a first content item of a plurality of candidate content items includes a player tag that identifies a player included in a lineup associated with a client device;

upon determining that the first content item includes the player tag, transmit the first content item to the client device to update a content feed of an application executing on the client device, the content feed updated based on a first priority score of the first content item and a second priority score of a second content item in the content feed;

upon receiving a request to disable a content filtering policy, select a third content item of the plurality of candidate content items having a second player tag that does not identify any player included in the lineup; and

transmit the third content item to the client device for presentation by the application in the content feed presented by the application.

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

receive a request for content from the client device; and

transmit the first content item to the client device in response to the request.

13. The system of claim 11 , wherein the one or more servers are further configured to select the first content item responsive to detecting an update to the lineup associated with the client device.

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

establish a web socket connection between the one or more servers and the application executing on the client device; and

transmit the first content item to the client device responsive to determining that the web socket connection is active.

15. The system of claim 14 , wherein the one or more servers are further configured to store a request to transmit the first content item in a queue prior to the web socket connection being active.

16. The system of claim 11 , wherein the client device accesses functionality of the one or more servers via an account, and wherein the one or more servers are further configured to:

maintain a plurality of lineups associated with the account, the plurality of lineups including the lineup; and

update the account by modifying an existing lineup of the plurality of lineups or adding a new lineup to the plurality of lineups.

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

determine that a third player has been added to the lineup;

select a fourth content item including a third player tag corresponding to the third player; and

transmit the fourth content item to the client device to update the content feed of the application executing on the client device.

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

determine that a second lineup including a set of players associated with the client device has expired;

remove at least one player of the set of players from the second lineup responsive to determining that the second lineup has expired; and

update the content feed of the application by removing a fourth content item including a fourth player tag that corresponds to the at least one player.

19. The system of claim 11 , wherein the application is configured to display an actionable item that when selected, applies the content filtering policy to filter the content presented by the application.

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

receive the first content item from a first content source in a first content format; and

convert the first content item from the first content format to a second content format configured to be presented in the application executing on the client device.

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 Apr 14, 2023
From: NGUYEN, JONATHAN; KESACK, DANIEL; HESTER, WILLIAM; DASINGER, SOPHIE; ZALESKI, EDWARD; HASKELL, ETHAN; SHTASEL-GOTTLIEB, COREY
To: DRAFTKINGS, INC.
Reel/Frame 063330/0044 →
CHANGE OF NAME Recorded Apr 14, 2023
From: DRAFTKINGS, INC.
To: DK CROWN HOLDINGS INC.
Reel/Frame 063348/0823 →
Continuity (5)
Continuation 17333988 · May 28, 2021
Continuation 16123730 · Sep 6, 2018
Provisional Application 62555606 · Sep 7, 2017
Provisional Application 62555600 · Sep 7, 2017
Related Publication 20230249081A1 · Aug 10, 2023
References Cited (27)
US 9003294B1 · Ames et al. · 2015 [cited by applicant]
US 10744413B2 · Kesack et al. · 2020 [cited by applicant]
US 11547940B2 · Kesack et al. · 2023 [cited by applicant]
US 11654361B2 · Nguyen · 2023 [cited by examiner]
US 20070021165A1 · Ma et al. · 2007 [cited by applicant]
US 20130060361A1 · Gabrail et al. · 2013 [cited by applicant]
US 20130158688A1 · Barber · 2013 [cited by applicant]
US 20130158984A1 · Myslinski · 2013 [cited by applicant]
US 20130282839A1 · Alcala · 2013 [cited by applicant]
US 20140018135A1 · Fernandez et al. · 2014 [cited by applicant]
US 20160255409A1 · Feldstein · 2016 [cited by examiner]
US 20160271501A1 · Balsbaugh · 2016 [cited by applicant]
US 20170115857A1 · Hughes et al. · 2017 [cited by applicant]
US 20200162796A1 · Azuolas et al. · 2020 [cited by applicant]
Final Office Action on U.S. Appl. No. 16/123,730 dated Aug. 21, 2020. [cited by applicant]
Final Office Action on U.S. Appl. No. 16/994,942 dated May 24, 2022. [cited by applicant]
Non-Final Office Action in U.S. Appl. No. 16/123,740, dated Nov. 29, 2019. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 16/123,730, dated Mar. 30, 2020. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 16/994,942 dated Jan. 28, 2022. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 16/994,942 dated Sep. 21, 2021. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 17/333,988 dated Sep. 12, 2022. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 16/123,740, dated Apr. 14, 2020. [cited by applicant]
Notice of Allowance on U.S. Appl. No. 16/994,942 dated Sep. 15, 2022. [cited by applicant]
Notice of Allowance on U.S. Appl. No. 16/123,730 dated Feb. 4, 2021. [cited by applicant]
Notice of Allowance on U.S. Appl. No. 17/333,988 dated Jan. 17, 2023. [cited by applicant]
Non-Final Office Action on U.S. Appl. No. 18/094,911 dated Apr. 26, 2024. [cited by applicant]
Final Office Action on U.S. Appl. No. 18/094,911 dated Oct. 4, 2024. [cited by applicant]