Method and device for sending requests
US-2016080529-A1 · Mar 17, 2016 · US
US10873497B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10873497-B2 |
| Application number | US-201916731157-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 31, 2019 |
| Priority date | May 11, 2017 |
| Publication date | Dec 22, 2020 |
| Grant date | Dec 22, 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 method, comprising detecting, by a network device, a communication failure associated with a communication channel between a client device and a server device, the communication failure being in at least one of: a first portion of the communication channel between the client device and the network device, or a second portion of the communication channel between the network device and the server device, and wherein the communication failure is 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, by the network device and from at least one of the client device or the server device, one or more network packets to be sent via the communication channel; selectively: providing, by the network device, during the communication failure, and when the one or more network packets are received from the client device, the client device with one or more client acknowledgments that correspond to each of the one or more network packets, the one or more client acknowledgments providing the client device with no indication of the communication failure, or providing, by the network device, during the communication failure, and when the one or more network packets are received from the server device, the server device with one or more server acknowledgments that correspond to each of the one or more network packets, the one or more server acknowledgments providing the server device with no indication of the communication failure; maintaining, by the network device and during the communication failure, the communication channel; and reestablishing communications, by the network device and via the communication channel, while maintaining the communication channel. 2. The method of claim 1 , wherein reestablishing the communications comprises: bypassing at least one of a validation procedure or an authentication procedure when reestablishing the communications. 3. The method of claim 1 , wherein providing the client device with the one or more client acknowledgments comprises: providing the one or more client acknowledgments to a user agent application operating on the client device. 4. The method of claim 1 , wherein providing the server device with the one or more server acknowledgments comprises: providing the one or more server acknowledgments to a server agent application associated with the server device. 5. The method of claim 1 , further comprising: storing, in local storage and based on detecting the communication failure, the one or more network packets; obtaining the one or more network packets from the local storage based on reestablishing the communications; and providing the one or more network packets via the communication channel. 6. The method of claim 1 , wherein reestablishing the communications comprises: performing an abbreviated validation process when reestablishing the communications. 7. The method of claim 1 , wherein the communication channel comprises an encrypted communication channel. 8. A network device, comprising: one or more memories; and one or more processors communicatively coupled to the one or more memories, configured to: detect a communication failure associated with a communication channel between a client device and a server device, the communication failure being in at least one of: a first portion of the communication channel between the client device and the network device, or a second portion of the communication channel between the network device and the server device, and wherein the communication failure is a result of at least one of: a network going offline, a server switching to a new network, or detect a networking metric does not meet a threshold metric; receive, from at least one of the client device or the server device, one or more network packets to be sent via the communication channel; selectively: provide, during the communication failure and when the one or more network packets are received from the client device, the client device with one or more client acknowledgments that correspond to each of the one or more network packets, the one or more client acknowledgments providing the client device with no indication of the communication failure, or provide, during the communication failure and when the one or more network packets are received from the server device, the server device with one or more server acknowledgments that correspond to each of the one or more network packets, the one or more server acknowledgments providing the server device with no indication of the communication failure; maintain, during the communication failure, the communication channel; and reestablish communications, via the communication channel, while maintaining the communication channel. 9. The network device of claim 8 , wherein the one or more processors, when reestablishing the communications, are configured to: bypass at least one of a validation procedure or an authentication procedure when reestablishing the communications. 10. The network device of claim 8 , wherein the one or more processors, when providing the client device with the one or more client acknowledgments, are configured to: provide the one or more client acknowledgments to a user agent application operating on the client device. 11. The network device of claim 8 , wherein the one or more processors, when providing the server device with the one or more server acknowledgments, are configured to: provide the one or more server acknowledgments to a server agent application associated with the server device. 12. The network device of claim 8 , wherein the one or more processors are further configured to: store, in local storage and based on detecting the communication failure, the one or more network packets; obtain the one or more network packets from the local storage based on reestablishing the communications; and provide the one or more network packets via the communication channel. 13. The network device of claim 8 , wherein the one or more processors, when reestablishing the communications, are configured to: perform an abbreviated validation process when reestablishing the communications. 14. The network device of claim 8 , wherein the communication channel comprises an encrypted communication channel. 15. A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by one or more processors of a network device, cause the one or more processors to: detect a communication failure associated with a communication channel between a client device and a server device, the communication failure being in at least one of: a first portion of the communication channel between the client device and the network device, or a second portion of the communication channel between the network device and the server device, and wherein the communication failure is a result of at least one of: a network going offline, a server switching to a new network, or detect a networking metric does not meet a threshold metric; receive, from at least one of the client device or the server device, one or more network packets to be sent via the communication channel; selectively: provide, during the communication failure and when the one or more network packets are received from the client device, the client device with one or more client acknowledgments that correspond to each of the one or more network packets, the one or more client ackno
Protocols · 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
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
Entity profiles · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.