# US 2017/0286139 A1 · Dynamically Loaded Plugin Architecture

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0286139 A1
- Document ID: US20170286139A1
- Status: Published application
- Kind: A1
- Application number: 15/623,500
- Filed: 2017-06-15
- Published: 2017-10-05
- Earliest claimed: 2013-03-14
- Assignees: Bitvore Corp.
- Applicants: Bitvore Corp.
- Inventors: Alan Chaney; Clay Cover; Gregory A. Bolcer; Andrey Mogilev
- Web page: https://patentgrep.com/patent/US20170286139A1

## CPC

- G06F 9/44526: {Plug-ins; Add-ons}
- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method and architecture for using dynamically loaded plugins is described herein. The dynamically loaded plugin architecture comprises a parent context and a plugin repository. The parent context may define one or more reusable software components. The plugin repository may store one or more plugins. When a plugin is loaded, a child context may be created dynamically. The child context is associated with the plugin and inherits the one or more reusable software components from the parent context.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

A non-transitory computer-readable storage medium storing instructions which, when executed by one or more processors, provides an architecture for dynamically loading plugins, the architecture comprising:
a parent context comprising data to configure one or more reusable software components;
a plugin repository operable to store a first plugin and a second plugin;
a first child context produced dynamically when the first plugin is loaded, the first child context being associated with a first version of the first plugin, the first child context inheriting the one or more reusable software components from the parent context; and
a second child context produced dynamically when the first plugin is loaded a second time, the second child context being associated with a second version of the first plugin, the second child context inheriting the one or more reusable software components from the first child context, wherein a violation is indicated if the first plugin returns a plugin object that belongs to the second plugin.

### Claim 22 (depends on 21)

The architecture of claim 21, wherein the first version of the first plugin and the second version of the first plugin are operable to run concurrently and independently.

### Claim 23 (depends on 21)

The architecture of claim 21, wherein the parent context is defined by an application programming interface (API).

### Claim 24 (depends on 21)

The architecture of claim 21, wherein a violation is indicated if a service invoked from the first child context contains a strong reference to a plugin class.

### Claim 25 (depends on 21)

The architecture of claim 21, wherein the first child context indicates whether the first plugin is loaded.

### Claim 26 (depends on 21)

The architecture of claim 21, wherein a timed action invoked by the first plugin determines whether the first plugin is loaded.

### Claim 27 (depends on 21)

The architecture of claim 21, wherein an event-based action invoked by the first plugin determines whether the first plugin is loaded.

### Claim 28

A method for dynamically loading plugins, the method comprising:
defining an initial configuration of one or more reusable software components according to data in a parent context;
storing a first plugin and a second plugin in a plugin repository;
dynamically creating a first child context when the first plugin is loaded a first time, the first child context being associated with a first version of the first plugin;
passing the one or more reusable software components from the parent context to the first child context;
dynamically creating a second child context when the first plugin is loaded a second time, the second child context being associated with a second version of the first plugin;
passing the one or more reusable software components from the first child context to the second child context; and
indicating a violation if the first plugin returns a plugin object that belongs to the second plugin.

### Claim 29 (depends on 28)

The method of claim 28, wherein the first version of the first plugin and the second version of the first plugin are operable to run concurrently and independently.

### Claim 30 (depends on 28)

The method of claim 28, wherein the method comprises:
defining the parent context by an application programming interface (API).

### Claim 31 (depends on 28)

The method of claim 28, wherein the method comprises:
indicating a violation if a service invoked from the first child context contains a strong reference to a plugin class.

### Claim 32 (depends on 28)

The method of claim 28, wherein the method comprises:
indicating, in the first child context, whether the first plugin is loaded.

### Claim 33 (depends on 28)

The method of claim 28, wherein the method comprises:
invoking a timed action to indicate whether the first plugin is loaded.

### Claim 34 (depends on 28)

The method of claim 28, wherein the method comprises:
invoking an event-based action to indicate whether the first plugin is loaded.

### Claim 35

A system for dynamically loading plugins, the system comprising:
a plugin repository memory operable to store a first plugin and a second plugin;
a context memory to store a parent context, a first child context, and a second child context, the parent context comprising data to configure one or more reusable software components; and
a hardware processor operable to:
produce a first child context when the first plugin is loaded, the first child context being associated with a first version of the first plugin, the first child context inheriting the one or more reusable software components from the parent context;
produce a second child context when the first plugin is loaded a second time, the second child context being associated with a second version of the first plugin, the second child context inheriting the one or more reusable software components from the first child context; and
indicate a violation if the first plugin returns a plugin object that belongs to the second plugin.

### Claim 36 (depends on 35)

The system of claim 35, wherein the hardware processor is operable to run the first version of the first plugin and the second version of the first plugin concurrently and independently.

### Claim 37 (depends on 35)

The system of claim 35, wherein the parent context is defined by an application programming interface (API).

### Claim 38 (depends on 35)

The system of claim 35, wherein the hardware processor is operable to indicate a violation if a service invoked from the first child context contains a strong reference to a plugin class.

### Claim 39 (depends on 35)

The system of claim 35, wherein the first child context indicates whether the first plugin is loaded.

### Claim 40 (depends on 35)

The system of claim 35, wherein a timed action and/or an event-based action invoked by the first plugin determines whether the first plugin is loaded.
