# US 2020/0287868 A1 · Systems and methods for in-band remote management

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

- Number: US 2020/0287868 A1
- Document ID: US20200287868A1
- Status: Published application
- Kind: A1
- Application number: 16/293,362
- Filed: 2019-03-05
- Published: 2020-09-10
- Earliest claimed: 2019-03-05
- Assignees: Cradlepoint, Inc.
- Applicants: CradlePoint, Inc.
- Inventors: GREGORY T. ANDERSEN; J. SEAN FRESK; SCOTT BONAR
- Web page: https://patentgrep.com/patent/US20200287868A1

## CPC

- H04L 63/029: {Firewall traversal, e.g. tunnelling or, creating pinholes}
- H04L 43/0817: by checking functioning
- H04L 61/2564: {for a higher-layer protocol, e.g. for session initiation protocol [SIP]}
- H04L 61/2567: for reachability, e.g. inquiring the address of a correspondent behind a NAT server
- H04L 63/0281: {Proxies}
- H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70)
- H04L 61/2514: between local and global IP addresses
- H04L 61/59: using proxies for addressing
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems and methods for in-band remote management of a network asset are disclosed. Embodiments include a router, configured to provide Network Address Translation (NAT) to a private network. Communications originating outside the private network are controlled by the router. At least one network server asset is in communication with the private network and configured to run a Secure Socket Shell (SSH) protocol. The network server asset and the router initiate an SSH tunnel with remote port mapping to enable communication with another network asset.

## Claims

### Claim 1

A system for in-band remote management of a network asset, the system comprising:
a router, configured to provide Network Address Translation (NAT);
a private network, wherein communications originating outside the private network are controlled by the router; and
at least one network server asset in communication with the private network and configured to run a Secure Socket Shell (SSH) protocol, and wherein the at least one network server asset and the router initiate an SSH tunnel with remote port mapping to another network asset.

### Claim 2 (depends on 1)

The system of claim 1 wherein the communications originating outside the private network originate from an external actor.

### Claim 3 (depends on 2)

The system of claim 2 further comprising a NetCloud Management (NCM) interface configured to communicate with the router.

### Claim 4

A method for in-band remote management of a network asset, the method comprising:
initiating a stream session between a router communicating on a private network, and an NetCloud Management (NCM) interface;
initiating a web session with the NCM interface;
creating with the NCM interface an isolated secure private session with the router by utilizing a stream session;
receiving a target Uniform Resource Identifier (URI) at the NCM interface and initiating an isolated secure private session with the router;
initiating a Secure Socket Shell (SSH) tunnel within the isolates secure private session;
receiving translated requests through the SSH tunnel and communicating the translated requests to a server device on the private network; and
transmitting responses to the translated requests through the SSH tunnel.

### Claim 5

A method for in-band remote management of a network asset, the method comprising:
initiating a stream session between a router communicating on a private network, and an NetCloud Management (NCM) interface;
initiating a web session with the NCM interface;
initiating a Socket Secure (SOCKS) proxy session between the NCM interface and the router;
initiating a SOCKS tunnel within the proxy session;
receiving SOCKS requests through the SOCKS tunnel and communicating the SOCKS requests to a network asset on the private network; and
transmitting responses to the SOCKS requests through the SSH tunnel.
