IP Library Granted Patent US 11,726,934
Granted Patent B2
US 11,726,934 · App. 17/822,525 · Granted Aug 15, 2023

Systems and methods for configuration of sequence handlers

Inventor: William Crowder (Camarillo, CA)
Assignee: Level 3 Communications, LLC
G06F13/20G06F2213/40
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 11,726,934
App. No.
17/822,525
Granted
Aug 15, 2023
Kind
B2
Abstract

A method for registering a handler in a configured sequence of handlers includes: receiving, by a processor and memory implementing a sequencer infrastructure, a configuration script defining a sequence including one or more handler identifiers and corresponding one or more handler arguments; invoking a handler initialization entry point for a handler corresponding to a handler identifier, the invoking the handler initialization entry point including: selecting, based on the corresponding one or more handler arguments, a handler type from among two or more of: a configured instance of the handler; a configured alternate handler different from the handler; an alternate sequence of handlers; an expression; and a no-op handler; and initializing a configured handler based on the handler type selected and the corresponding one or more handler arguments; and adding the configured handler to a configured sequence of handlers.

Claims (66)

1. A method for registering a handler in a configured sequence of handlers, the method comprising:

receiving, by a processor and memory storing instructions implementing a sequencer infrastructure, a configuration script defining a sequence comprising one or more handler identifiers and corresponding one or more handler arguments;

invoking, by the processor, a handler initialization entry point for a handler corresponding to a handler identifier of the one or more handler identifiers, the invoking the handler initialization entry point comprising:

selecting, based on the corresponding one or more handler arguments, a handler type from among two or more of:

a configured instance of the handler;

a configured alternate handler different from the handler;

an alternate sequence of handlers;

an expression; and

a no-op (no-operation) handler; and

initializing a configured handler based on the handler type selected and the corresponding one or more handler arguments;

adding, by the processor, the configured handler to a configured sequence of handlers; and

executing, by a sequencer of the sequencer infrastructure, the configured sequence of handlers to generate an output in response to an input.

2. The method of claim 1 , wherein the selecting the handler type is further based on a plurality of parameters of an execution environment of the sequencer.

3. The method of claim 2 , wherein the parameters of the execution environment comprise:

a version number of the sequencer infrastructure;

a handler registry of handlers available to the sequencer infrastructure;

a plurality version numbers of corresponding ones of the handlers of the handler registry;

descriptions of hardware capabilities of a server comprising the processor and memory and configured to execute the sequencer; or

a location of the server.

4. The method of claim 2 , wherein the invoking the handler initialization entry point further comprises dynamically registering the handler with the execution environment.

5. The method of claim 4 , wherein the handler is retrieved from a remote source over a network.

6. The method of claim 1 , wherein the sequencer executing the configured sequence of handlers processes requests and generates responses in a content delivery network.

7. The method of claim 1 , wherein the sequencer executing the configured sequence of handlers processes requests and generates responses in a web application server.

8. The method of claim 1 , wherein the sequencer processes input data in a stream processing pipeline corresponding to the configured sequence of handlers.

9. The method of claim 1 , further comprising omitting the configured handler from the configured sequence of handlers when the handler type is the no-op handler.

10. A computing system comprising:

at least one processor; and

memory storing instructions that, when executed by the at least one processor, cause the system to:

register a handler in a configured sequence of handlers by:

receiving a configuration script defining a sequence comprising one or more handler identifiers and corresponding one or more handler arguments;

invoking a handler initialization entry point for a handler corresponding to a handler identifier of the one or more handler identifiers, the invoking the handler initialization entry point comprising:

selecting, based on the corresponding one or more handler arguments, a handler type from among two or more of:

 a configured instance of the handler;

 a configured alternate handler different from the handler;

 an alternate sequence of handlers;

 an expression; and

 a no-op handler; and

initializing a configured handler based on the handler type selected and the corresponding one or more handler arguments; and

adding, by the processor, the configured handler to a configured sequence of handlers; and

implement a sequencer infrastructure configured to execute the configured sequence of handlers to generate an output in response to an input.

11. The computing system of claim 10 , wherein the selecting the handler type is further based on a plurality of parameters of an execution environment of the sequencer.

12. The computing system of claim 11 , wherein the parameters of the execution environment comprise:

a version number of the sequencer infrastructure;

a handler registry of handlers available to the sequencer infrastructure;

a plurality version numbers of corresponding ones of the handlers of the handler registry;

descriptions of hardware capabilities of a server comprising the processor and memory and configured to execute the sequencer; or

a location of the server.

13. The computing system of claim 11 , wherein the invoking the handler initialization entry point further comprises dynamically registering the handler with the execution environment.

14. The computing system of claim 13 , wherein the handler is retrieved from a remote source over a network.

15. The computing system of claim 10 , wherein the sequencer executing the configured sequence of handlers processes requests and generates responses in a content delivery network.

16. The computing system of claim 10 , wherein the sequencer executing the configured sequence of handlers processes requests and generates responses in a web application server.

17. The computing system of claim 10 , wherein the sequencer processes input data in a stream processing pipeline corresponding to the configured sequence of handlers.

18. The computing system of claim 10 , wherein the memory further stores instructions that, when executed by the at least one processor, cause the system to omit the configured handler from the configured sequence of handlers when the handler type is the no-op handler.

19. A method, for registering a handler in a configured sequence of handlers, the method comprising:

receiving, by a processor and memory storing instructions implementing a sequencer infrastructure, a configuration script defining a sequence comprising one or more handler identifiers and corresponding one or more handler arguments;

invoking, by the processor, a handler initialization entry point for a handler corresponding to a handler identifier of the one or more handler identifiers, the invoking the handler initialization entry point comprising:

selecting, based on the corresponding one or more handler arguments and a plurality of parameters of an execution environment of a sequencer, a handler type from among two or more of:

a configured instance of the handler;

a configured alternate handler different from the handler;

an alternate sequence of handlers;

an expression; and

a no-op handler; and

initializing a configured handler based on the handler type selected and the corresponding one or more handler arguments;

adding, by the processor, the configured handler to a configured sequence of handlers; and

executing, by the sequencer of the sequencer infrastructure, the configured sequence of handlers to generate an output in response to an input.

20. The method of claim 19 , wherein the invoking the handler initialization entry point further comprises dynamically registering the handler with the execution environment.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 9, 2024
From: LEVEL 3 COMMUNICATIONS, LLC
To: SANDPIPER CDN, LLC
Reel/Frame 068256/0091 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 26, 2022
From: CROWDER, WILLIAM
To: LEVEL 3 COMMUNICATIONS, LLC
Reel/Frame 060912/0939 →