Mobile device traffic splitter

Patent metadata

Field	Value
Publication number	US-10595205-B2
Application number	US-201715815451-A
Country	US
Kind code	B2
Filing date	Nov 16, 2017
Priority date	Mar 31, 2014
Publication date	Mar 17, 2020
Grant date	Mar 17, 2020

Abstract

A mobile device traffic splicer is disclosed. In various embodiments, a network communication associated with a destination is received from a mobile device. A stored routing data associated with the mobile device is used to determine, based at least in part on the destination, to redirect the network communication to a proxy associated with the destination. The network communication is sent to the proxy associated with the destination. In various embodiments, one or both of metering network traffic by destination and/or domain and filtering network communications and/or portions thereof based on the destination and/or domain may be performed.

First claim

What is claimed is:

1. A method of managing a mobile device, comprising:
receiving, at a traffic splitter from a mobile device, a network communication associated with a destination, wherein an agent installed on the mobile device causes the mobile device to provide to the traffic splitter the network communication associated with the destination, wherein the mobile device is configured to be controlled by a mobile device management server associated with the destination via the agent;
using a stored routing data associated with the mobile device to determine, based at least in part on the destination, to redirect the network communication to a proxy server associated with the destination, wherein the stored routing data associated with the mobile device includes configuration data indicating that network communications between the mobile device and the destination is to be routed to the proxy server associated with the destination, wherein the stored routing data is provided to the traffic splitter from the mobile device management server associated with the destination;
sending the network communication to the proxy server associated with the destination; and
metering, by the traffic splitter, traffic usage from the mobile device to the proxy server associated with the destination, wherein the metered traffic usage includes a measure of an amount and/or percentage of data traffic between the mobile device and the proxy server associated with the destination.

2. The method of claim 1 , wherein the traffic splitter is configured to receive and store said routing data.

3. The method of claim 2 , wherein the routing data is provided via a mobile device management (MDM) broker by the MDM server associated with the destination.

4. The method of claim 1 , wherein the destination comprises a domain or portion thereof.

5. The method of claim 1 , wherein the destination comprises a subnetwork or other IP address range.

6. The method of claim 1 , further comprising providing traffic security features.

7. The method of claim 6 , wherein the traffic security features include one or more of traffic audit logging, application programming interface (API) level filtering, and/or other protection or security.

8. The method of claim 1 , further comprising using a stored policy to determine to perform inline processing with respect to the network communication.

9. The method of claim 8 , wherein the inline processing includes encrypting at least a portion of data comprising the network communication.

10. The method of claim 1 , wherein the proxy server is associated with the mobile device management (MDM) server associated with the destination.

11. The method of claim 1 , further comprising updating a usage statistic associated with the destination to reflect the network communication.

12. The method of claim 11 , further comprising using the usage statistic to generate a report.

13. The method of claim 11 , further comprising using the usage statistic to generate an automatic reimbursement payment.

14. A system, comprising:
a communication interface; and
a processor coupled to the communication interface and configured to:
receive from a mobile device, via the communication interface, a network communication associated with a destination, wherein an agent installed on the mobile device causes the mobile device to provide to the traffic splitter the network communication associated with the destination wherein the mobile device is configured to be controlled by a mobile device management server associated with the destination via the agent;
use a stored routing data associated with the mobile device to determine, based at least in part on the destination, to redirect the network communication to a proxy server associated with the destination, wherein the stored routing data associated with the mobile device includes configuration data indicating that network communications between the mobile device and the destination is to be routed to the proxy server associated with the destination, wherein the stored routing data is provided to the traffic splitter from the mobile device management server associated with the destination;
send the network communication to the proxy server associated with the destination; and
meter traffic usage from the mobile device to the proxy server associated with the destination, wherein the metered traffic usage includes a measure of an amount and/or percentage of data traffic between the mobile device and the proxy server associated with the destination.

15. The system of claim 14 , further comprising a storage device configured to store said routing data.

16. The system of claim 15 , wherein the processor is further configured to receive via an administrative user interface a definition of said routing data and to store said routing data in said storage device.

17. The system of claim 16 , wherein the routing data is provided via a mobile device management (MDM) broker by the mobile device management server associated with the destination.

18. The system of claim 14 , wherein the destination comprises a subnetwork or other IP address range.

19. The system of claim 14 , wherein the processor is further configured to provide traffic security features, wherein the traffic security features include one or more of traffic audit logging, API level filtering, and/or other protection or security.

20. A computer program product to manage a mobile device, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
receiving from a mobile device a network communication associated with a destination, wherein an agent installed on the mobile device causes the mobile device to provide to the traffic splitter the network communication associated with the destination, wherein the mobile device is configured to be controlled by a mobile device management server associated with the destination via the agent;
using a stored routing data associated with the mobile device to determine, based at least in part on the destination, to redirect the network communication to a proxy server associated with the destination, wherein the stored routing data associated with the mobile device includes configuration data indicating that network communications between the mobile device and the destination is to be routed to the proxy server associated with the destination, wherein the stored routing data is provided to the traffic splitter from the mobile device management server associated with the destination;
sending the network communication to the proxy server associated with the destination; and
metering traffic usage from the mobile device to the proxy server associated with the destination, wherein the metered traffic usage includes a measure of an amount and/or percentage of data traffic between the mobile device and the proxy server associated with the destination.

Assignees

• Mobile Iron Inc

Inventors

• Batchu Suresh Kumar
• Kim Mansu

Classifications

• H04L63/0281

  Proxies · CPC title

• H04L41/046

  comprising network management agents or mobile agents therefor · CPC title

• H04L12/08

  Allotting numbers to messages; Counting characters, words or messages · CPC title

• H04L41/0893

  Assignment of logical groups to network elements · CPC title

• H04L63/107

  wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals · CPC title