IP Library Granted Patent US 12,298,958
Granted Patent B2
US 12,298,958 · App. 18/064,552 · Granted May 13, 2025

System and method for capturing data sent by a mobile device

Inventor: Todd Michael Cohan (New York, NY)
Assignee: MOBILEGUARD INC.
G06F16/2291H04L63/0263H04M1/66H04W4/14H04W12/08H04W12/12H04W24/08H04L63/30
View Patent ↗
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 12,298,958
App. No.
18/064,552
Granted
May 13, 2025
Kind
B2
Abstract

Systems and methods for providing capture, archival, and analysis of data sent by mobile devices over a carrier network, with the systems and methods not requiring the installation of any additional software on the mobile devices, the systems and methods also providing for alerts to be generated based on the content of the data.

Claims (54)

1. A method for capturing and controlling data originating from at least one device, the method comprising:

receiving, from at least one device and via an application programming interface (API), an indication of rules for controlling data;

retrieving, via the API, the data from at least one network element corresponding to a network, wherein the data was sent over the network by the at least one device and the data was received at the at least one network element; and

outputting instructions for a computing device associated with the API to perform one or more actions based at least in part on the rules for controlling the data, each of the one or more actions being associated with data security, device security, and/or remote access to the data, wherein the one or more actions comprises (i) auditing the data and (ii) in response to the data indicating performance of one or more unauthorized actions by the at least one device, locking the at least one device from one or more predetermined activities for a predetermined duration.

2. The method of claim 1 , wherein the one or more actions comprises logging and/or storing the data.

3. The method of claim 1 , wherein the one or more actions comprises blocking or filtering a communication attempt or access to a website or other information source.

4. The method of claim 1 , wherein the one or more actions comprises archiving the data and tagging the data for subsequent searchability and retrieval.

5. The method of claim 1 , wherein:

the at least one device comprises a plurality of devices; and

receiving the indication of rules for controlling the data comprises a single instance of receiving the indication of rules, wherein the rules are associated with controlling the data from each of the plurality of devices.

6. The method of claim 1 , wherein receiving the indication of rules comprises receiving, via the API, a user selection from a plurality of predetermined rules options.

7. The method of claim 1 , wherein receiving the indication of rules comprises receiving, via the API, a user-generated set of rules.

8. The method of claim 1 , further comprising:

receiving, from the at least one device and via the API, authentication credentials;

authenticating the at least one device based at least in part on the authentication credentials; and

permitting the at least one device to access at least some of the data.

9. A method for capturing and controlling data originating from at least one device, the method comprising:

receiving, from at least one device and via an application programming interface (API), an indication of rules for controlling data;

retrieving, via the API, the data from at least one network element corresponding to a network, wherein the data was sent over the network by the at least one device and the data was received at the at least one network element;

outputting instructions for a computing device associated with the API to perform one or more actions based at least in part on the rules for controlling the data, each of the one or more actions being associated with data security, device security, and/or remote access to the data;

receiving, from the at least one device and via the API, authentication credentials, wherein the authentication credentials are first authentication credentials that are associated with a first device of the at least one device and a first level of rules;

authenticating the at least one device based at least in part on the authentication credentials;

permitting the at least one device to access at least some of the data;

receiving, from a second device of the at least one device and via the API, second authentication credentials;

authenticating the second device based at least in part on the second authentication credentials; and

receiving, from the second device, instructions for modifying the indication of rules received from the first device.

10. A system for capturing and controlling data originating from at least one device, the system comprising:

at least one processor operative to:

receive, from at least one device and via an application programming interface (API), an indication of rules for controlling data;

retrieve, via the API, the data from at least one network element corresponding to a network, wherein the data was sent over the network by the at least one device and the data was received at the at least one network element; and

perform one or more actions based at least in part on the rules for controlling the data, each of the one or more actions being associated with data security, device security, and/or remote access to the data, wherein the one or more actions comprises (i) auditing the data and (ii) in response to the data indicating performance of one or more unauthorized actions by the at least one device, locking the at least one device from one or more predetermined activities for a predetermined duration.

11. The system of claim 10 , wherein the one or more actions comprises logging and/or storing the data.

12. The system of claim 10 , wherein the one or more actions comprises blocking or filtering a communication attempt or access to a website or other information source.

13. The system of claim 10 , wherein the one or more actions comprises archiving the data and tagging the data for subsequent searchability and retrieval.

14. The system of claim 10 , wherein:

the at least one device comprises a plurality of devices; and

receiving the indication of rules for controlling the data comprises a single instance of receiving the indication of rules, wherein the rules are associated with controlling the data from each of the plurality of devices.

15. The system of claim 10 , wherein receiving the indication of rules comprises receiving, via the API, a user selection from a plurality of predetermined rules options.

16. The system of claim 10 , wherein receiving the indication of rules comprises receiving, via the API, a user-generated set of rules.

17. The system of claim 10 , wherein the at least one processor is further operative to:

receive, from the at least one device and via the API, authentication credentials;

authenticate the at least one device based at least in part on the authentication credentials; and

permit the at least one device to access at least some of the data.

18. A system for capturing and controlling data originating from at least one device, the system comprising:

at least one processor operative to:

receive, from at least one device and via an application programming interface (API), an indication of rules for controlling data;

retrieve, via the API, the data from at least one network element corresponding to a network, wherein the data was sent over the network by the at least one device and the data was received at the at least one network element;

perform one or more actions based at least in part on the rules for controlling the data, each of the one or more actions being associated with data security, device security, and/or remote access to the data;

receive, from the at least one device and via the API, authentication credentials, wherein the authentication credentials are first authentication credentials that are associated with a first device of the at least one device and a first level of rules;

authenticate the at least one device based at least in part on the authentication credentials;

permit the at least one device to access at least some of the data;

receive, from a second device of the at least one device and via the API, second authentication credentials;

authenticate the second device based at least in part on the second authentication credentials; and

receive, from the second device, instructions for modifying the indication of rules received from the first device.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 13, 2025
From: MOBILEGUARD, LLC
To: SMARSH INC.
Reel/Frame 072544/0833 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 14, 2022
From: COHAN, TODD MICHAEL
To: MOBILEGUARD INC.
Reel/Frame 062084/0345 →
Continuity (7)
Continuation 16834668 · Mar 30, 2020
Continuation 15698098 · Sep 7, 2017
Continuation 14820986 · Aug 7, 2015
Continuation In Part 14322997 · Jul 3, 2014
Continuation 13287523 · Nov 2, 2011
Continuation In Part 12287868 · Oct 14, 2008
Related Publication 20230214376A1 · Jul 6, 2023
References Cited (67)
US 6456706B1 · Blood et al. · 2002 [cited by applicant]
US 7069003B2 · Lehikoinen et al. · 2006 [cited by applicant]
US 7069316B1 · Gryaznov · 2006 [cited by applicant]
US 7113977B1 · Baker et al. · 2006 [cited by applicant]
US 7142848B2 · Owen et al. · 2006 [cited by applicant]
US 7197321B2 · Erskine et al. · 2007 [cited by applicant]
US 7263353B2 · Forsberg et al. · 2007 [cited by applicant]
US 7302272B2 · Ackley · 2007 [cited by applicant]
US 7516219B2 · Moghaddam et al. · 2009 [cited by applicant]
US 7519990B1 · Xie · 2009 [cited by applicant]
US 7546334B2 · Redlich et al. · 2009 [cited by applicant]
US 7603294B2 · Singh et al. · 2009 [cited by applicant]
US 7647047B2 · Moghaddam et al. · 2010 [cited by applicant]
US 7689510B2 · Lamkin et al. · 2010 [cited by applicant]
US 7787863B2 · Van De Groenendaal · 2010 [cited by applicant]
US 7813822B1 · Hoffberg · 2010 [cited by applicant]
US 8078739B1 · Somasundaram et al. · 2011 [cited by applicant]
US 9015253B1 · Jarrett · 2015 [cited by applicant]
US 20020012445A1 · Perry · 2002 [cited by applicant]
US 20020078384A1 · Hippelainen · 2002 [cited by applicant]
US 20030220093A1 · Fellenstein et al. · 2003 [cited by applicant]
US 20040116842A1 · Mardirossian · 2004 [cited by applicant]
US 20040117478A1 · Triulzi et al. · 2004 [cited by applicant]
US 20040210773A1 · Markosi, III · 2004 [cited by applicant]
US 20050069096A1 · Claudatos et al. · 2005 [cited by applicant]
US 20050075097A1 · Lehikoinen et al. · 2005 [cited by applicant]
US 20050113130A1 · Weinzierl · 2005 [cited by applicant]
US 20050130633A1 · Hill et al. · 2005 [cited by applicant]
US 20050175156A1 · Afshar et al. · 2005 [cited by applicant]
US 20060079215A1 · Perrella et al. · 2006 [cited by applicant]
US 20060209809A1 · Ellingham et al. · 2006 [cited by applicant]
US 20060217136A1 · Bantukul et al. · 2006 [cited by applicant]
US 20070061211A1 · Ramer et al. · 2007 [cited by applicant]
US 20070111704A1 · Linkert et al. · 2007 [cited by applicant]
US 20070150948A1 · De Spiegeleer · 2007 [cited by applicant]
US 20070281664A1 · Kaneko et al. · 2007 [cited by applicant]
US 20070297418A1 · Lee · 2007 [cited by applicant]
US 20070299631A1 · Macbeth et al. · 2007 [cited by applicant]
US 20080045201A1 · Kies · 2008 [cited by examiner]
US 20080114862A1 · Moghaddam et al. · 2008 [cited by applicant]
US 20080148358A1 · Denny et al. · 2008 [cited by applicant]
US 20080233919A1 · Kenney · 2008 [cited by applicant]
US 20090012806A1 · Ricordi · 2009 [cited by examiner]
US 20090092108A1 · Hargrave et al. · 2009 [cited by applicant]
US 20090157708A1 · Bandini et al. · 2009 [cited by applicant]
US 20090164522A1 · Fahey · 2009 [cited by applicant]
US 20090217343A1 · Bellwood · 2009 [cited by examiner]
US 20090264104A1 · Lee et al. · 2009 [cited by applicant]
US 20100272262A1 · Boubion et al. · 2010 [cited by applicant]
US 20100321183A1 · Donovan et al. · 2010 [cited by applicant]
US 20110176451A1 · Uchida · 2011 [cited by applicant]
US 20120224826A1 · Caudle et al. · 2012 [cited by applicant]
US 20120284345A1 · Costenaro et al. · 2012 [cited by applicant]
US 20130091564A1 · Fitzgerald et al. · 2013 [cited by applicant]
US 20130152171A1 · Kindler et al. · 2013 [cited by applicant]
US 20130300764A1 · Gardenfors et al. · 2013 [cited by applicant]
US 20140146911A1 · Eliaz · 2014 [cited by applicant]
US 20150256666A1 · Peterson · 2015 [cited by applicant]
JP 2005258855A · 2005 [cited by applicant]
KR 20110022446A · 2011 [cited by applicant]
KR 1020130116458A · 2013 [cited by applicant]
KR 101402518B1 · 2014 [cited by applicant]
WO 02076046A2 · 2002 [cited by applicant]
WO 2006107161A1 · 2006 [cited by applicant]
International Preliminary Report on Patentability for International Application No. PCT/US2016/045529, mailed Feb. 22, 2018, 13 Pages. [cited by applicant]
International Search Report and Written Opinion for International Application No. PCT/US2016/045529, mailed Nov. 9, 2016, 14 Pages. [cited by applicant]
Yin J., et al., “Engineering Server-Driven Consistency for Large Scale Dynamic Web Services,” Tenth International World Wide Web Conference, WWW10, Hong Kong, May 1-5, 2001, pp. 1 and 2, Retrieved from URL: http://porta… [cited by applicant]