# US 2019/0319930 A1 · Container deployment for a network

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

- Number: US 2019/0319930 A1
- Document ID: US20190319930A1
- Status: Published application
- Kind: A1
- Application number: 16/454,490
- Filed: 2019-06-27
- Published: 2019-10-17
- Earliest claimed: 2017-03-17
- Assignees: Verizon Patent and Licensing Inc.
- Applicants: Verizon Patent and Licensing Inc.
- Inventors: Yuhang ZHAO; Manish CHUGTU; Girish S. WELLING; Anmol WADHWA
- Web page: https://patentgrep.com/patent/US20190319930A1

## CPC

- H04L 63/0281: {Proxies}
- H04L 63/029: {Firewall traversal, e.g. tunnelling or, creating pinholes}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A device can determine that a container is deployed in a front-end of a private network. The container can include a self-contained execution environment. The container can include an interface that is configured for directing network traffic between the front-end of the private network and one or more applications operating in a back-end of the private network. The device can configure an interface of the container for directing network traffic between an external network and the container. The device can configure a firewall of the front-end of the private network to permit routing of network traffic between the external network and the container. The device can advertise a route for directing network traffic between the external network and the container. The device can perform routing of network traffic between the one or more applications operating in the back-end of the private network and the external network using the container.

## Claims

### Claim 1

A method, comprising:
identifying, by a device, a container that is deployed in a first portion of a first network,
the container including a first interface that is configured for directing network traffic between the first portion of the first network and one or more applications operating in a second portion of the first network;
configuring, by the device, a second interface of the container for directing network traffic between a second network and the container; and
performing, by the device and using the container, routing of network traffic between the one or more applications operating in the second portion of the first network and the second network.

### Claim 2 (depends on 1)

The method of claim 1, wherein the container is a proxy container,
the proxy container providing, for the network traffic, at least one of:
firewall functionality,
threat detection functionality,
data analytics functionality, or
data processing functionality.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
transmitting a notification to a border gateway protocol (BGP) controller,
the notification including data that causes the BGP controller to configure a host route for directing other network traffic between the container and the second network.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
receiving, from the one or more applications, other network traffic directed to the second network; and
routing the other network traffic to the second network.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
receiving a request for a particular service associated with the container;
obtaining, based on the particular service, the container from a repository of containers; and
deploying the container based on the request.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
monitoring a running state of the container;
detecting, based on monitoring the running state, that the container has been exited; and
removing, based on detecting that the container has been exited, a route associated with the container.

### Claim 7 (depends on 6)

The method of claim 6, further comprising:
analyzing the container, prior to removing the route and using a set of application programming interface (API) calls associated with the first network, to confirm that the container has exited.

### Claim 8

A device, comprising:
one or more memories; and
one or more processors, communicatively coupled to the one or more memories, to:
identify a container that is deployed in a first portion of a first network,
the container including a first interface that is configured for directing network traffic between the first portion of the first network and one or more applications operating in a second portion of the first network;
configure a second interface of the container for directing network traffic between a second network and the container; and
perform, using the container, routing of network traffic between the one or more applications operating in the second portion of the first network and the second network.

### Claim 9 (depends on 8)

The device of claim 8, wherein the container is a proxy container,
the proxy container providing, for the network traffic, at least one of:
firewall functionality,
threat detection functionality,
data analytics functionality, or
data processing functionality.

### Claim 10 (depends on 8)

The device of claim 8, wherein the one or more processors are further to:
transmit a notification to a border gateway protocol (BGP) controller,
the notification including data that causes the BGP controller to configure a host route for directing other network traffic between the container and the second network.

### Claim 11 (depends on 8)

The device of claim 8, wherein the one or more processors are further to:
receive, from the one or more applications, other network traffic directed to the second network; and
route the other network traffic to the second network.

### Claim 12 (depends on 8)

The device of claim 8, wherein the one or more processors are further to:
receive a request for a particular service associated with the container;
obtain, based on the particular service, the container from a repository of containers; and
deploy the container based on the request.

### Claim 13 (depends on 8)

The device of claim 8, wherein the one or more processors are further to:
monitor a running state of the container;
detect, based on monitoring the running state, that the container has been exited; and
remove, based on detecting that the container has been exited, a route associated with the container.

### Claim 14 (depends on 13)

The device of claim 13, wherein the one or more processors are further configured to:
analyze the container, prior to removing the route and using a set of application programming interface (API) calls associated with the first network, to confirm that the container has exited.

### Claim 15

A non-transitory computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors, cause the one or more processors to:
identify a container that is deployed in a first portion of a first network,
the container including a first interface that is configured for directing network traffic between the first portion of the first network and one or more applications operating in a second portion of the first network;
configure a second interface of the container for directing network traffic between a second network and the container; and
perform, using the container, routing of network traffic between the one or more applications operating in the second portion of the first network and the second network.

### Claim 16 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the container is a proxy container,
the proxy container providing, for the network traffic, at least one of:
firewall functionality,
threat detection functionality,
data analytics functionality, or
data processing functionality.

### Claim 17 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
transmit a notification to a border gateway protocol (BGP) controller,
the notification including data that causes the BGP controller to configure a host route for directing other network traffic between the container and the second network.

### Claim 18 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
receive, from the one or more applications, other network traffic directed to the second network; and
route the other network traffic to the second network.

### Claim 19 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
receive a request for a particular service associated with the container;
obtain, based on the particular service, the container from a repository of containers; and
deploy the container based on the request.

### Claim 20 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
monitor a running state of the container;
detect, based on monitoring the running state, that the container has been exited; and
remove, based on detecting that the container has been exited, a route associated with the container.
