IP Library Granted Patent US 12706914
Granted Patent B2
US 12706914 · App. 18/890,821 · Granted Aug 11, 2026

Method and system for secure container application framework

Inventors: Jim Sienicki (New York, NY); Roger Lucas (New York, NY); Perry Wintner (New York, NY); Nick Jelbert (New York, NY); Clint Smith (New York, NY)
Assignee: VEEA INC.
H04L63/101G06F11/1464G06F11/1469G06F21/105H04L63/0435H04L63/102H04L63/20H04L67/1097G06F21/1075
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 12706914
App. No.
18/890,821
Granted
Aug 11, 2026
Kind
B2
Abstract

An edge computing gateway (ECG) includes a processor configured to establish a distributed container network that includes a plurality of interconnected ECGs, each of which includes an orchestrator and containers. The processor may determine available resources on one or more additional ECGs in the distributed container network, select one of the additional ECGs in the distributed container network to run a container based on the available resources determined by the orchestrator of the ECG, and allocate resources from the selected ECG to execute the container. In response to changes in resource demands, the processor may dynamically reallocate resources between the ECG and the selected ECG to adjust container performance across the distributed container network.

Claims (43)

1 . A method for dynamic resource allocation across a distributed edge computing network, the method comprising:

establishing a distributed container network comprising a plurality of edge computing gateways (ECGs), wherein each ECG includes an orchestrator and containers, and the ECGs are interconnected via a network;

determining, by the orchestrator of a first ECG in the plurality of ECGs, available resources on one or more additional ECGs in the distributed container network;

selecting, by the orchestrator of the first ECG, a second ECG in the plurality of ECGs in the distributed container network to run a container based on the available resources;

reallocating, by the orchestrator of the first ECG, resources from the second ECG to run the container; and

in response to changes in resource demands, dynamically reallocating, by the orchestrator of the first ECG, resources between the first ECG and the second ECG to adjust performance of the container.

2 . The method of claim 1 , further comprising maintaining access to a shared storage capability across the ECGs in the distributed container network to provide data persistence for applications running in containers.

3 . The method of claim 1 , further comprising deploying a compute distribution process across the ECGs in the distributed container network to horizontally scale the network by using newly available resources.

4 . The method of claim 1 , further comprising using a dynamic resource allocation scheme for the distributed container network to move a secure container application running on the distributed container network between different ECGs based on orchestration policies, wherein the application may be moved back to its original ECG when the resources on the original ECG are freed up.

5 . The method of claim 1 , further comprising using distributed computing capabilities within the distributed container network to dynamically reallocate applications between ECGs to offload tasks and improve resource distribution across multiple nodes.

6 . The method of claim 1 , wherein the orchestrator utilizes multiple wide area network (WAN) connections from different ECGs in the distributed container network to provide upstream connectivity to a cloud network, wherein the WAN connections are aggregated to increase bandwidth or provide alternative paths for application communication.

7 . The method of claim 1 , further comprising reassigning containers or applications between ECGs in response to hardware failures, network congestion, or resource shortages.

8 . The method of claim 1 , wherein the orchestrator is configured to operate using an orchestration platform selected from a platform group comprising Kubernetes (K8), Docker Swarm, and K3S.

9 . The method of claim 1 , wherein the orchestrator determines and applies real-time orchestration policies based on resource availability and workload demands, wherein the orchestration policies govern movement of applications between ECGs to enhance performance across the distributed container network.

10 . An edge computing gateway (ECG), comprising:

a processor configured with processor-executable instructions to:

establish a distributed container network comprising a plurality of ECGs, wherein each ECG includes an orchestrator and containers, and the ECGs are interconnected via a network;

determine, by the orchestrator of the ECG, available resources on one or more additional ECGs in the distributed container network;

select one of the additional ECGs in the distributed container network to run a container based on the available resources determined by the orchestrator of the ECG;

allocate resources from the selected ECG to execute the container; and

in response to changes in resource demands, dynamically reallocate resources between the ECG and the selected ECG to adjust container performance across the distributed container network.

11 . The ECG of claim 10 , wherein the processor is further configured to maintain access to a shared storage capability across the ECGs in the distributed container network to provide data persistence for applications running in containers.

12 . The ECG of claim 10 , wherein the processor is further configured to deploy a compute distribution process across the ECGs in the distributed container network to horizontally scale the network by using newly available resources.

13 . The ECG of claim 10 , wherein the processor is further configured to use a dynamic resource allocation scheme for the distributed container network to move a secure container application running on the distributed container network between different ECGs based on orchestration policies, wherein the application may be moved back to its original ECG when the resources on the original ECG are freed up.

14 . The ECG of claim 10 , wherein the processor is further configured to use distributed computing capabilities within the distributed container network to dynamically reallocate applications between ECGs to offload tasks and improve resource distribution across multiple nodes.

15 . The ECG of claim 10 , wherein the processor is further configured to use multiple wide area network (WAN) connections from different ECGs in the distributed container network to provide upstream connectivity to a cloud network, wherein the WAN connections are aggregated to increase bandwidth or provide alternative paths for application communication.

16 . The ECG of claim 10 , wherein the processor is further configured to reassign containers or applications between ECGs in response to hardware failures, network congestion, or resource shortages.

17 . The ECG of claim 10 , wherein the processor is further configured to operate the orchestrator using an orchestration platform selected from a platform group comprising Kubernetes (K8), Docker Swarm, and K3S.

18 . The ECG of claim 10 , wherein the processor is further configured to determine and apply real-time orchestration policies based on resource availability and workload demands, wherein the orchestration policies govern movement of applications between ECGs to enhance performance across the distributed container network.

19 . A non-transitory computer readable storage medium having stored thereon processor-executable software instructions configured to cause a processor in an edge computing gateway (ECG) to perform operations for dynamic resource allocation across a distributed edge computing network, the operations comprising:

establishing a distributed container network comprising a plurality of edge computing gateways (ECGs), wherein each ECG includes an orchestrator and containers, and the ECGs are interconnected via a network;

determining, by the orchestrator of a first ECG, available resources on one or more additional ECGs in the distributed container network;

selecting, by the orchestrator of the first ECG, a second ECG in the distributed container network to run a container based on the available resources;

reallocating resources from the second ECG to run the container, wherein the orchestrator determines an appropriate node to adjust resource utilization; and

in response to changes in resource demands, dynamically reallocating resources between the first ECG and the second ECG to adjust performance of the container.

20 . The non-transitory computer readable storage medium of claim 19 , wherein the stored processor-executable instructions are configured to cause the processor in the ECG to perform operations further comprising maintaining access to a shared storage capability across the ECGs in the distributed container network to provide data persistence for applications running in containers.

21 . The non-transitory computer readable storage medium of claim 19 , wherein the stored processor-executable instructions are configured to cause the processor in the ECG to perform operations further comprising deploying a compute distribution process across the ECGs in the distributed container network to horizontally scale the network by using newly available resources.

22 . The non-transitory computer readable storage medium of claim 19 , wherein the stored processor-executable instructions are configured to cause the processor in the ECG to perform operations further comprising using a dynamic resource allocation scheme for the distributed container network to move a secure container application running on the distributed container network between different ECGs based on orchestration policies, wherein the application may be moved back to its original ECG when the resources on the original ECG are freed up.

23 . The non-transitory computer readable storage medium of claim 19 , wherein the stored processor-executable instructions are configured to cause the processor in the ECG to perform operations further comprising using distributed computing capabilities within the distributed container network to dynamically reallocate applications between ECGs to offload tasks and improve resource distribution across multiple nodes.

24 . The non-transitory computer readable storage medium of claim 19 , wherein the stored processor-executable instructions are configured to cause the processor in the ECG to perform operations further comprising using multiple wide area network (WAN) connections from different ECGs in the distributed container network to provide upstream connectivity to a cloud network, wherein the WAN connections are aggregated to increase bandwidth or provide alternative paths for application communication.

25 . The non-transitory computer readable storage medium of claim 19 , wherein the stored processor-executable instructions are configured to cause the processor in the ECG to perform operations further comprising reassigning containers or applications between ECGs in response to hardware failures, network congestion, or resource shortages.

26 . The non-transitory computer readable storage medium of claim 19 , wherein the stored processor-executable instructions are configured to cause the processor in the ECG to perform operations further comprising operate the orchestrator using an orchestration platform selected from a platform group comprising Kubernetes (K8), Docker Swarm, and K3S.

27 . The non-transitory computer readable storage medium of claim 19 , wherein the stored processor-executable instructions are configured to cause the processor in the ECG to perform operations further comprising determining and applying real-time orchestration policies based on resource availability and workload demands, wherein the orchestration policies govern movement of applications between ECGs to enhance performance across the distributed container network.