Method and device for sending requests
US-2016080529-A1 · Mar 17, 2016 · US
US10554480B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10554480-B2 |
| Application number | US-201715593181-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 11, 2017 |
| Priority date | May 11, 2017 |
| Publication date | Feb 4, 2020 |
| Grant date | Feb 4, 2020 |
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.
The various embodiments described herein include methods, devices, and systems for maintaining communication links. In one aspect, a computing system includes: (1) a client agent communicatively coupled to a client device, the client agent configured to: (a) facilitate communication between the client device and a remote server via a communication channel including a first portion of the communication channel between the client device and the client agent; and (b) maintain the first portion of the communication channel during a communication outage in a different portion of the communication channel; and (2) a communications server distinct from the client device and the remote server, the communications server configured to: (a) enable communication between the client device and the remote server via the communication channel; and (b) reestablish the communication channel in the event of a communication outage between the client agent and the remote server.
Opening claim text (preview).
What is claimed is: 1. A computing system, comprising: a client agent communicatively coupled to a client device, the client agent configured to: receive, from an application operating on the client device, a request to establish a communication channel with a remote server, the communication channel including a plurality of portions, a first portion, of the plurality of portions, being between the client device and the client agent; facilitate communication between the client device and the remote server via the communication channel; receive data indicating that a different portion, of the plurality of portions, is experiencing a communication outage, the communication outage being a result of at least one of: a network going offline, a server switching to a new network, or detecting a networking metric does not meet a threshold metric; receive, from the application, one or more network packets to be sent to the remote server via the communication channel; provide, during the communication outage, the application with one or more acknowledgements that correspond to each of the one or more network packets, the one or more acknowledgements providing the application with no indication of the communication outage; and maintain the first portion during the communication outage; and a communications server, separate from the client device and the remote server, the communications server configured to: enable communication between the client device and the remote server via the communication channel; and reestablish communications, via the communication channel, after the communication outage is resolved. 2. The computing system of claim 1 , wherein the client agent is a component of the client device. 3. The computing system of claim 1 , further comprising: a server agent communicatively coupled to the remote server, the server agent configured to: facilitate the communication between the remote server and the client device via the communication channel, wherein the different portion comprises a second portion of the communication channel between the remote server and the server agent; and maintain the second portion of the communication channel during the communication outage in the different portion of the communication channel. 4. The computing system of claim 3 , wherein the server agent is separate from the remote server. 5. The computing system of claim 1 , wherein the communication channel comprises a transmission control protocol (TCP) communication channel. 6. The computing system of claim 1 , wherein the different portion comprises at least one of a second portion, of the plurality of portions, between the client agent and a server agent or a third portion, of the plurality of portions, between the server agent and the remote server. 7. The computing system of claim 6 , wherein the second portion corresponds to one or more networks, including one or more wireless networks. 8. The computing system of claim 1 , wherein reestablishing the communication channel comprises re-enabling communication between the client device and the remote server without submission of user credentials. 9. A method comprising: at a computing system having one or more processors and memory: receiving, from an application operating on a client device, a request to establish a communication channel with a remote server, the communication channel including a plurality of portions, a first portion, of the plurality of portions, being between the client device and the computing system, and a second portion, of the plurality of portions, being between the computing system and the remote server; enabling communication between the client device and the remote server via the communication channel; detecting a communication failure of the second portion, the communication failure being a result of at least one of: a network going offline, a server switching to a new network, or detecting a networking metric does not meet a threshold metric; receiving, from the application, one or more network packets to be sent to the remote server via the communication channel; providing, during the communication failure, the application with one or more acknowledgements that correspond to each of the one or more network packets, the one or more acknowledgments providing the application with no indication of the communication failure; maintaining, during the communication failure, the communication channel; and based on detecting the communication failure, reestablishing communications, via the communication channel, while maintaining the communication channel. 10. The method of claim 9 , wherein enabling communication between the client device and the remote server comprises enabling communication via one or more networks; and wherein reestablishing the communication channel comprises enabling communication between the client device and the remote server via one or more second networks. 11. The method of claim 9 , further comprising receiving user credentials from a user of the client device; and wherein enabling communication between the client device and the remote server comprises enabling communication based on validation of the received user credentials. 12. The method of claim 11 , wherein reestablishing the communication channel comprises re-enabling communication between the client device and the remote server without validation of user credentials. 13. The method of claim 9 , wherein enabling communication between the client device and the remote server includes enabling the client device to access applications and resources stored at the remote server. 14. The method of claim 9 , wherein the communication channel comprises an encrypted communication channel. 15. The method of claim 9 , wherein maintaining the communication channel comprises maintaining a connection between the client device and a client agent. 16. The method of claim 9 , wherein maintaining the communication channel comprises maintaining a connection between the remote server and a server agent. 17. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by a computing system, cause the computing system to: receive, from an application operating on a client device, a request to establish a communication channel with a remote server, the communication channel including a plurality of portions, a first portion, of the plurality of portions, being between the client device and the computing system, and a second portion, of the plurality of portions, being between the computing system and the remote server; enable communication between the client device and the remote server via the communication channel; detect a communication failure of the second portion, the communication failure being a result of at least one of: a network going offline, a server switching to a new network, or detecting a networking metric does not meet a threshold metric; receive, from the application, one or more network packets to be sent to the remote server via the communication channel; provide, during the communication failure, the application with one or more acknowledgements that correspond to each of the one or more network packets, the one or more acknowledgements providing the application with no indication of the communication failure; maintain, during the communication failure, the communication channel; and based on detecting the communication failure, reestablish communication
Proxies · CPC title
for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06) · CPC title
providing single-sign-on or federations · CPC title
in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title
for controlling access to devices or network resources · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.