IP Library Granted Patent US 8,275,851
Granted Patent B1
US 8,275,851 · App. 13/449,183 · Granted Sep 25, 2012

Systems and methods for invoking commands across a federation

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 8,275,851
App. No.
13/449,183
Granted
Sep 25, 2012
Kind
B1
Abstract

Some embodiments provide different frameworks for seamlessly issuing and executing commands across servers of different federation participants. Each framework facilitates issuance and execution of a command that originates from a first federation participant and that is intended for execution at servers of a second federation participant. In some embodiments, a framework implements a method for enabling command interoperability between distributed platforms that each operate a set of servers on behalf of content providers. The method involves receiving a command targeting a particular configuration that a first distributed platform deploys to a server that is operated by a second distributed platform. The method identifies the server of the second distributed platform that is deployed with the particular configuration. The method communicably couples to a command invocation system of the second distributed platform and issues the command to the command invocation system for issuance of the command to the identified server.

Claims (34)

1. A computer-implemented method for command invocation in a federation comprising a plurality of distributed platforms that each operate a set of servers, the computer-implemented method comprising:

performing a login of a customer of a first distributed platform of the plurality of distributed platforms;

identifying at least one deployed configuration of the customer based on the customer login;

identifying deployment of the customer configuration to (i) a first server that is operated by the first distributed platform and (ii) a second server that is operated by a second distributed platform of the plurality of distributed platforms, whereby the first and second servers collectively execute the customer configuration;

receiving a command to modify execution of the customer configuration; and

issuing the command to the first distributed platform to modify execution of the customer configuration by the first server and to the second distributed platform to modify execution of the customer configuration by the second server.

2. The computer-implemented method of claim 1 further comprising (i) formatting the command according to a first command format of the first distributed platform prior to issuing the command to the first distributed platform and (ii) formatting the command according to a second command format of the second distributed platform prior to issuing the command to the second distributed platform.

3. The computer-implemented method of claim 1 , wherein modifying execution of the customer configuration by the first server comprises preloading the first server with content identified in the command before said content is requested from the first server.

4. The computer-implemented method of claim 1 , wherein modifying execution of the customer configuration by the first server comprises purging content identified in the command from the first server.

5. The computer-implemented method of claim 1 further comprising peering with a command invocation system of the first distributed platform and a command invocation system of the second distributed platform, wherein issuing the command to the first distributed platform comprises issuing the command to the command invocation system of the first distributed platform for distribution of the command to the first server, and wherein issuing the command to the second distributed platform comprises issuing the command to the command invocation system of the second distributed platform for distribution of the command to the second server.

6. The computer-implemented method of claim 1 further comprising peering with the first server and a command invocation system of the second distributed platform, and wherein issuing the command to the first distributed platform comprises directly issuing the command to the first server and issuing the command to the command invocation system of the second distributed platform for distribution of the command to the second server.

7. The computer-implemented method of claim 1 , wherein each distributed platform of the plurality of distributed platforms is at least one of a different Content Delivery Network (CDN) operator and CDN service provider.

8. A non-transitory computer-readable storage medium with an executable program stored thereon, the program for facilitating command invocation in a federation comprising a plurality of distributed platforms that each operate a set of servers, wherein the program instructs a microprocessor to perform sets of instructions for:

receiving a command to modify execution of a customer configuration;

identifying deployment of the customer configuration to (i) a first server that is operated by the first distributed platform and (ii) a second server that is operated by a second distributed platform of the plurality of distributed platforms, whereby the first and second servers collectively execute the customer configuration;

formatting the command to conform to a first command format of the first distributed platform;

issuing the command in the first command format to the first distributed platform to modify execution of the configuration by the first server;

formatting the command to conform to a second command format of the second distributed platform, wherein the first command format is incompatible with the second command format; and

issuing the command in the second command format to the second distributed platform to modify execution of the configuration by the second server.

9. The non-transitory computer-readable storage medium of claim 8 , wherein the program further comprises a set of instructions for monitoring execution status of the command issued to the first distributed platform and the second distributed platform.

10. The non-transitory computer-readable storage medium of claim 9 , wherein the program further comprises a set of instructions for providing an interface to report the execution status of the command across the first and second distributed platforms.

11. The non-transitory computer-readable storage medium of claim 8 , wherein the set of instructions for receiving the command comprises a set of instructions for receiving the command in a federation command format that is different than the first command format and the second command format.

12. The non-transitory computer-readable storage medium of claim 8 , wherein the set of instructions for receiving the command comprises a set of instructions for receiving the command in a third command format of a third distributed platform that is different than the first command format and the second command format.

13. The non-transitory computer-readable storage medium of claim 8 , wherein the set of instructions for receiving the command comprises a set of instructions for receiving the command in the first command format and formatting the command to conform to the first command format requires no modification of the command.

14. The non-transitory computer-readable storage medium of claim 8 , wherein the first command format is a native format used within the first distributed platform to issue commands internally to the set of servers that is operated by the first distributed platform and the second command format is a native format used within the second distributed platform to issue commands internally to the set of servers that is operated by the second distributed platform, and wherein the native format of the first distributed platform is different than the native format of the second distributed platform.

15. A federation promoting interoperation between a plurality of distributed platforms that each operate a set of servers, the federation comprising:

a memory device having a database that maps deployment of each of a plurality of configurations to at least (i) a first server that is operated by a first distributed platform of the plurality of distributed platforms and (ii) a second server that is operated by a second distributed platform of the plurality of distributed platforms;

an application programming interface (API) storing command formats for each of the plurality of distributed platforms; and

a command broker issuing a command for a particular configuration of the plurality of configurations to the first distributed platform and the second distributed platform based on a mapping of the particular configuration obtained from the database, wherein the command broker formats the command according to a first command format of the first distributed platform stored to the API when issuing the command to the first distributed platform, and wherein the command broker formats the command according to a second command format of the second distributed platform stored to the API when issuing the command to the second distributed platform.

16. The federation of claim 15 , wherein the API further stores a federation command format.

17. The federation of claim 16 , wherein the command broker is further for receiving the command in the federation command format, converting the command to the first command format in advance of issuing the command to the first distributed platform, and converting the command to the second command format in advance of issuing the command to the second distributed platform.

18. The federation of claim 15 , wherein the command broker is further for monitoring execution status of the command by the first distributed platform and the second distributed platform.

19. The federation of claim 18 further comprising a portal presenting the execution status of the command across the first and second distributed platforms.

20. The federation of claim 19 , wherein the portal further comprises an input interface for originating the command for the particular configuration.

Assignments (11)
RELEASE OF PATENT SECURITY AGREEMENT [RECORDED AT REEL/FRAME 065597/0406] Recorded Jul 9, 2025
From: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION
To: UPLYNK, INC. (F/K/A EDGIO, INC.)
Reel/Frame 071875/0105 →
RELEASE OF PATENT SECURITY AGREEMENT [RECORDED AT REEL/FRAME 065597/0212] Recorded Jul 3, 2025
From: LYNROCK LAKE MASTER FUND LP
To: UPLYNK, INC. (F/K/A EDGIO, INC.); MOJO MERGER SUB, LLC
Reel/Frame 071817/0877 →
RELEASE OF PATENT SECURITY AGREEMENT [RECORDED AT REEL/FRAME 068763/0276] Recorded Jul 3, 2025
From: LYNROCK LAKE MASTER FUND LP
To: UPLYNK, INC. (F/K/A EDGIO, INC.); MOJO MERGER SUB, LLC
Reel/Frame 071818/0022 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 30, 2025
From: EDGIO, INC.
To: DRNC HOLDINGS, INC.
Reel/Frame 070071/0327 →
PATENT SECURITY AGREEMENT Recorded Aug 23, 2024
From: EDGIO, INC.; MOJO MERGER SUB, LLC
To: LYNROCK LAKE MASTER FUND LP [LYNROCK LAKE PARTNERS LLC, ITS GENERAL PARTNER]
Reel/Frame 068763/0276 →
PATENT SECURITY AGREEMENT Recorded Nov 15, 2023
From: EDGIO, INC.; MOJO MERGER SUB, LLC
To: LYNROCK LAKE MASTER FUND LP [LYNROCK LAKE PARTNERS LLC, ITS GENERAL PARTNER]
Reel/Frame 065597/0212 →
PATENT SECURITY AGREEMENT Recorded Nov 15, 2023
From: EDGIO, INC.; MOJO MERGER SUB, LLC
To: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION
Reel/Frame 065597/0406 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 21, 2022
From: EDGECAST INC.
To: EDGIO, INC.
Reel/Frame 061738/0972 →
CHANGE OF NAME Recorded Mar 15, 2022
From: VERIZON DIGITAL MEDIA SERVICES INC.
To: EDGECAST INC.
Reel/Frame 059367/0990 →
CHANGE OF NAME Recorded Apr 25, 2016
From: EDGECAST NETWORKS, INC
To: VERIZON DIGITAL MEDIA SERVICES INC.
Reel/Frame 038511/0045 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 29, 2012
From: SAKATA, JAYSON G.; PETERS, ROBERT J.
To: EDGECAST NETWORKS, INC.
Reel/Frame 029206/0877 →