IP Library Patent Application 14512386
Patent Application
App. No. 14/512,386

PARENTAL CONTROL OF MOBILE CONTENT ON A MOBILE DEVICE

Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US None
App. No.
14/512,386
Abstract

A method of parental control of content on a mobile device includes monitoring traffic activities on a mobile device and detecting suspicious traffic.

Claims (66)

1 . A method of parental control of content on a mobile device, the method, comprising:

monitoring, traffic activities, including inbound or outbound traffic, on the mobile device;

detecting, from suspicious traffic identified from the traffic activities, content identified from at least one of:

black listed websites or black listed mobile applications;

traffic activities generated upon click through activities tracked at the mobile device;

content identified based on feedback from one or more users;

content identified from identification of a potentially offending website or mobile application;

content identified from a destination address or a source address;

content identified based on a set of rules or policies;

content identified as gambling content, adult content, violent content, pornographic content, or other age inappropriate content; and

content identified as inappropriate content based on age, gender, or religion;

wherein the suspicious traffic is identified from the traffic activities from its timing characteristics including time of day, access frequency, day of week or other patterns in timing of access;

wherein, the content identified is detected from the traffic activities for websites and mobile applications on the mobile device;

preventing the content identified from being accessed at the mobile device;

in addition to preventing the content identified from being accessed at the mobile device, analyzing cached content stored in a local proxy at the mobile device;

screening the cached content to determine if the cached content includes the content identified; and

preventing the content identified in the cached content from being accessed at the mobile device.

2 . The method of claim 1 , wherein, the suspicious traffic is detected by a proxy server remote from the mobile device.

3 . The method of claim 2 , wherein, the proxy server communicates identification of the suspicious traffic to a local proxy on the mobile device, such that the suspicious traffic is blocked from access to or from the mobile device.

4 . The method of claim 1 , further comprising, prompting a parent or a supervising individual of the user of the mobile device with parameters of a request associated with the suspicious traffic to validate the request.

5 . The method of claim 1 , wherein, the suspicious traffic is detected, by a proxy server, based on heuristics measures.

6 . The method of claim 1 , wherein, the suspicious traffic is detected by a mobile platform or operating system native to the mobile device.

7 . The method of claim 1 , wherein, the set of rules or policies is specified by a parent or supervising individual of a user of the mobile device.

8 . The method of claim 1 , wherein, the set of rules or policies is configured through a web portal.

9 . The method of claim 1 , further comprising, logging a traffic pattern or sequence of events, including the timing characteristics, in detecting the suspicious traffic from the traffic activities.

10 . The method of claim 1 , further comprising,

detecting content identified at multiple mobile devices;

aggregating information regarding the content identified from multiple mobile devices;

creating a policy based on the information aggregated from the multiple mobile devices;

broadcasting the policy to other mobile devices of the content identified from the multiple mobile devices.

11 . The method of claim 1 , wherein, the monitoring of the traffic activities includes:

collecting information about a request or information about a response to the request at the mobile device;

using the information collected about the request or the response to identify or to detect the content identified.

12 . The method of claim 11 , wherein, the information collected about the request or response received for the request initiated at the mobile device is further used to determine cacheability of the response at the mobile device.

13 . A mobile device which implements parental control of content access thereon, the mobile device, comprising:

a processor;

a memory having instructions stored thereon, which when executed causes the processor to:

monitor traffic activities, including inbound or outbound traffic on the mobile device;

detect, from the traffic activities, content identified from at least one of:

black listed websites or black listed mobile applications;

traffic activities generated upon click through activities tracked at the mobile device;

content identified based on feedback from one or more users;

content identified from identification of a potentially offending website or mobile application;

content identified from a destination address or a source address;

content identified based on a set of rules or policies;

content identified as gambling content, adult content, violent content, pornographic content, or other age inappropriate content; and

content identified as inappropriate content based on age, gender, or religion;

use information about a request or a response in the inbound or outbound traffic to determine cacheability of the response to the request from the mobile device;

prevent the content identified from being accessed at the mobile device;

in addition to preventing the content identified from being accessed at the mobile device, analyzing cached content stored in a local proxy at the mobile device;

screening the cached content to determine if the cached content includes the content identified; and

preventing the content identified in the cached content from being accessed at the mobile device.

14 . The device of claim 13 , wherein the processor is further configured to cause the device to prompt a parent or a supervising individual of the user of the mobile device with parameters of a request associated with the suspicious traffic to validate the request.

15 . The device of claim 13 , wherein, the traffic activities are monitored by a mobile platform or operating system native to the mobile device.

16 . The device of claim 13 , wherein, the set of rules or policies is specified by a parent or supervising individual of a user of the mobile device.

17 . The device of claim 13 , wherein, the set of rules or policies is configured through a web portal, and the mobile device receives the rules or policies from the web portal.

18 . The device of claim 13 , wherein the memory having instructions stored thereon, which when executed causes the processor to log a traffic pattern or sequence of events, including the timing characteristics, in detecting the suspicious traffic from the traffic activities.

19 . The device of claim 13 , wherein the memory has instructions stored thereon, which when executed causes the processor to:

detect content identified at multiple mobile devices;

aggregate information regarding the content identified from multiple mobile devices;

create a policy based on the information aggregated from the multiple mobile devices; and

broadcast the policy to other mobile devices of the content identified from the multiple mobile devices.

20 . The device of claim 13 , wherein the memory has instructions stored thereon, which when executed causes the processor to:

collect information about a request or information about a response to the request at the mobile device; and

use the information collected about the request or the response to identify or to detect the content identified.

21 . The device of claim 20 , wherein, the information collected about the request or response received for the request initiated at the mobile device is further used to determine cacheability of the response at the mobile device.

Assignments (2)
ENTITY CONVERSION Recorded Aug 27, 2015
From: SEVEN NETWORKS, INC.
To: SEVEN NETWORKS, LLC
Reel/Frame 036485/0059 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 12, 2014
From: BOTT, ROSS
To: SEVEN NETWORKS, INC
Reel/Frame 034157/0311 →