Transmission of network management data over an extensible scripting file format
US-2015052256-A1 · Feb 19, 2015 · US
US9769139B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9769139-B2 |
| Application number | US-201414771745-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 10, 2014 |
| Priority date | Feb 7, 2014 |
| Publication date | Sep 19, 2017 |
| Grant date | Sep 19, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems, devices, and methods are disclosed for an agent device within a company's network firewall to initiate an HTTP connection with a cloud-based gateway and then upgrade the connection to a WebSockets protocol in order to have an interactive session. Over this interactive session, a mobile device, which connects to the cloud-based intermediary, can request data from servers inside the company's firewalls. Because the firewall is traversed using HTTP protocols (with WebSockets), it can be as safe as letting employees browse the web from inside the company's network.
Opening claim text (preview).
What is claimed is: 1. A method of facilitating offsite access to an enterprise computer network, the method comprising: initiating, by an agent executing on a computer behind a firewall on an enterprise network, a hypertext transport protocol (HTTP) connection with a cloud-based gateway outside of the firewall; responsive to initiating the HTTP connection, automatically upgrading the HTTP connection with the cloud-based gateway to a WebSocket protocol connection; receiving, from the cloud-based gateway, by the agent, over the WebSocket protocol connection, a first request for data stored on a server behind the firewall on the enterprise network, wherein the first request has a WebSocket format compliant for the WebSocket protocol connection; translating, by the agent, the first request received from the cloud-based gateway into a second request having an HTTP format for communication with the server on the enterprise network, wherein translating includes converting the WebSocket format of the first request to the HTTP format for the second request for communication with the server; sending, from the agent, the second request to the server on the enterprise network; receiving, by the agent, a first response to the second request from the server, the first response having the HTTP format; creating, by the agent, a second response having the WebSocket format, wherein the second response is created based on converting the first response from the HTTP format to the WebSocket format; and sending, by the agent, over the WebSocket protocol connection, to the cloud-based gateway, the second response. 2. The method of claim 1 further comprising: receiving, at the cloud-based gateway, a third request from a mobile device; reformatting, at the cloud-based gateway, the third request from the mobile device into the first request for data over the WebSocket protocol connection; receiving, at the cloud-based gateway, the second response from the agent; creating, at the cloud-based gateway, a third response from the second response from the agent; and sending the third response to the mobile device. 3. The method of claim 1 further comprising: packaging, by the agent, the first response from the server into a string, a binary object, or an ArrayBuffer of the second response before sending the second response. 4. The method of claim 1 wherein the server is a local web server. 5. The method of claim 1 wherein the server is running an enterprise application. 6. The method of claim 1 wherein the WebSocket protocol connection is a secure WebSocket protocol connection. 7. The method of claim 1 further comprising: checking, by the agent with the cloud-based gateway, for an update of an agent software; downloading, to the agent, a software update; and installing, at the agent, the downloaded software update. 8. The method of claim 7 further comprising: determining a time window acceptable or unacceptable for the software update; and performing the checking, downloading, or installing based on the determined time window. 9. The method of claim 7 further comprising: rolling back the installing of the downloaded software update to a previous version of the agent software. 10. A machine-readable non-transitory medium embodying information indicative of instructions for causing one or more machines to perform operations comprising: initiating, by an agent executing on a computer behind a firewall on an enterprise network, a hypertext transport protocol (HTTP) connection with a cloud-based gateway outside of the firewall; responsive to initiating the HTTP connection, automatically upgrading the HTTP connection with the cloud-based gateway to a WebSocket protocol connection; receiving, from the cloud-based gateway, by the agent, over the WebSocket protocol connection, a first request for data stored on a server behind the firewall on the enterprise network, wherein the first request has a WebSocket format compliant for the WebSocket protocol connection; translating, by the agent, the first request received from the cloud-based gateway into a second request having an HTTP format for communication with the server on the enterprise network, wherein translating includes converting the WebSocket format of the first request to the HTTP format for the second request for communication with the server; sending, from the agent, the second request to the server on the enterprise network; receiving, by the agent, a first response to the second request from the server, the first response having the HTTP format; creating, by the agent, a second response having the WebSocket format, wherein the second response is created based on converting the first response from the HTTP format to the WebSocket format; and sending, by the agent, over the WebSocket protocol connection, to the cloud-based gateway, the second response. 11. The machine-readable non-transitory medium of claim 10 wherein the operations further comprise: receiving, at the cloud-based gateway, a third request from a mobile device; reformatting, at the cloud-based gateway, the third request from the mobile device into the first request for data over the WebSocket protocol connection; receiving, at the cloud-based gateway, the second response from the agent; creating, at the cloud-based gateway, a third response from the second response from the agent; and sending the third response to the mobile device. 12. The machine-readable non-transitory medium of claim 10 wherein the operations further comprise: checking, by the agent with the cloud-based gateway, for an update of an agent software; downloading, to the agent, a software update; and installing, at the agent, the downloaded software update. 13. The machine-readable non-transitory medium of claim 12 wherein the operations further comprise: determining a time window acceptable or unacceptable for the software update; and performing the checking, downloading, or installing based on the determined time window. 14. A system for facilitating offsite access to an enterprise computer network, the system comprising: at least one processor; and a memory operatively coupled with the at least one processor, the at least one processor executing instructions from the memory for: initiating, by an agent executing on a computer behind a firewall on an enterprise network, a hypertext transport protocol (HTTP) connection with a cloud-based gateway outside of the firewall; responsive to initiating the HTTP connection, automatically upgrading the HTTP connection with the cloud-based gateway to a WebSocket protocol connection; receiving, from the cloud-based gateway, by the agent, over the WebSocket protocol connection, a first request for data stored on a server behind the firewall on the enterprise network, wherein the first request has a WebSocket format compliant for the WebSocket protocol connection; translating, by the agent, the first request received from the cloud-based gateway into a second request having an HTTP format for communication with the server on the enterprise network, wherein translating includes converting the WebSocket format of the first request to the HTTP format for the second request for communication with the server; sending, from the agent, the second request to the server on the enterprise network; receiving, by the agent, a first response to the second request from the server, the first response having the HTTP format; creating, by the agent, a second response having the WebSocket format, wherein the second response is created based on converting the first response from the HTTP
by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity · CPC title
Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals · CPC title
Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70) · CPC title
Proxies · CPC title
Updates (security arrangements therefor G06F21/57) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.