Providing access to an application programming interface through a named pipe
US-9183065-B1 · Nov 10, 2015 · US
US9350644B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9350644-B2 |
| Application number | US-201414560609-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 4, 2014 |
| Priority date | Apr 13, 2012 |
| Publication date | May 24, 2016 |
| Grant date | May 24, 2016 |
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.
A method implemented by an agent operating on a mobile device communicating to a cloud-based system includes opening up local listening sockets on the mobile device; redirecting outgoing traffic from all application on the mobile device except the agent to the local listening sockets; and forwarding the outgoing traffic from the local listening sockets to the cloud-based system with additional information included therein for the cloud-based system.
Opening claim text (preview).
What is claimed is: 1. A method implemented by an agent operating on a mobile device communicating to a cloud-based system, the method comprising: opening up local listening sockets on the mobile device; redirecting outgoing traffic from all applications on the mobile device except the agent to the local listening sockets; and forwarding the outgoing traffic from the local listening sockets to the cloud-based system with additional information included therein for the cloud-based system. 2. The method of claim 1 , wherein the local listening sockets are a Transmission Control Protocol (TCP) listening socket for Web traffic and a User Datagram Protocol (UDP) listening socket for Domain Name System (DNS) traffic. 3. The method of claim 1 , wherein the redirecting outgoing traffic comprises using an Internet Protocol (IP) tables, firewall rules-based approach where the agent configures firewall rules to reroute the outgoing traffic to the local listening sockets. 4. The method of claim 1 , wherein the redirecting outgoing traffic comprises using a tunnel interface approach using a tunnel interface to reroute the outgoing traffic to the local listening sockets. 5. The method of claim 1 , further comprising: applying local policies at the mobile device, through the agent, prior to forwarding the outgoing traffic. 6. The method of claim 5 , wherein the cloud-based system is configured to apply remote policies subsequent to the forwarding the outgoing traffic. 7. The method of claim 5 , further comprising: blocking an outgoing request based on the outgoing traffic based on the local policies and displaying a locally generated end user notification. 8. The method of claim 5 , wherein the local policies comprise bandwidth quota limits. 9. The method of claim 1 , wherein the additional information comprises any of app unique package name, app version, operating system version, device model, and agent app version. 10. A mobile device, comprising: a network interface communicatively coupled to a network, a processor communicatively coupled to the network interface, and memory storing instructions that when executed cause the processor to: open up local listening sockets on the mobile device; redirect outgoing traffic from all applications on the mobile device except an agent to the local listening sockets; and forward the outgoing traffic from the local listening sockets to a cloud-based system with additional information included therein for the cloud-based system. 11. The mobile device of claim 10 , wherein the local listening sockets are a Transmission Control Protocol (TCP) listening socket for Web traffic and a User Datagram Protocol (UDP) listening socket for Domain Name System (DNS) traffic. 12. The mobile device of claim 10 , wherein the outgoing traffic is redirected using an Internet Protocol (IP) tables, firewall rules-based approach where the agent configures firewall rules to reroute the outgoing traffic to the local listening sockets. 13. The mobile device of claim 10 , wherein the outgoing traffic is redirected using a tunnel interface approach using a tunnel interface to reroute the outgoing traffic to the local listening sockets. 14. The mobile device of claim 10 , wherein the memory storing instructions that when executed further cause the processor to: apply local policies at the mobile device, through the agent, prior to forwarding the outgoing traffic. 15. The mobile device of claim 14 , wherein the cloud-based system is configured to apply remote policies subsequent to the forwarding the outgoing traffic. 16. The mobile device of claim 14 , wherein the memory storing instructions that when executed further cause the processor to: block an outgoing request based on the outgoing traffic based on the local policies and displaying a locally generated end user notification. 17. The mobile device of claim 14 , wherein the local policies comprise bandwidth quota limits. 18. The mobile device of claim 14 , wherein the additional information comprises any of app unique package name, app version, operating system version, device model, and agent app version.
Rule management · CPC title
Countermeasures against malicious traffic (countermeasures against attacks on cryptographic mechanisms H04L9/002) · CPC title
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
Active monitoring, e.g. heartbeat, ping or trace-route · CPC title
Routing performance; Theoretical aspects · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.