IP Library Granted Patent US 10,477,454
Granted Patent B2
US 10,477,454 · App. 15/629,710 · Granted Nov 12, 2019

Managing iOS-based mobile communication devices by creative use of CallKit API protocols

Inventors: Joseph E. Breaux (Baton Rouge, LA); John Wright (Baton Rouge, LA)
Assignee: CELLCONTROL, INC.
H04W48/04G06F3/0227G06F9/546H04W4/027H04W4/029H04W4/043H04W4/40H04W4/80H04W76/14H04R3/12H04R2420/07H04R2499/13H04W4/33H04W84/12H04W84/18
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 10,477,454
App. No.
15/629,710
Filed
Jun 21, 2017
Granted
Nov 12, 2019
Kind
B2
Art Unit
2645
USPC
455/456.4
Abstract

Systems, methods, and devices for managing predetermined functions on a mobile device, the operating system (OS) installed on the device including an event application programming interface (API) configured to enable voice over internet protocol (VoIP) applications to assume priority over other applications and functions of the mobile device when VoIP calls are detected. A mobile device management software application installed and running on the mobile device emulates a VoIP software application and uses event API calls to trick the OS into believing that a VoIP call has been detected and, in response, causes the OS to block or interfere with one or more predetermined functions on the mobile device based on the status and location of the mobile device.

Claims (53)

1. A method for preventing user interaction in a mobile device, comprising:

determining, by a processor of the mobile device, a status associated with the mobile device, wherein the status is indicative that user interaction with the mobile device is to be prevented;

detecting activity in a first application, wherein the activity is prohibited based on the determined status of the mobile device; and

in response to the detected activity, invoking one or more Voice over Internet Protocol (VoIP) application programming interface (API) functions by a second application to prevent user interaction with the first application on the mobile device, wherein invoking the one or more VoIP API functions causes the mobile device to display the second application in the foreground of the mobile device.

2. The method of claim 1 , wherein to display the second application in the foreground of the mobile device prevents user interaction with the first application.

3. The method of claim 1 , wherein invoking the one or more API functions causes the mobile device to:

generate a VoIP call notification by the second application; and

display the VoIP call notification in the foreground of the mobile device, wherein to display the VoIP call notification prevents user interaction with the first application.

4. The method of claim 3 , wherein the VoIP call notification includes a caller name, and further comprising:

changing the caller name in the VoIP call notification to an indication that the activity is being prevented.

5. The method of claim 1 , further comprising:

generating a notification indicating that the activity is prohibited; and

displaying the notification in the foreground of the mobile device.

6. The method of claim 1 , wherein the detected activity is further prohibited based on the first application corresponding to a blacklisted application.

7. A computer-readable storage medium storing computer-executable instructions, which, when executed on a processor of a mobile device, cause a mobile device to perform an operation for preventing user interaction in a mobile device, the operation causing the mobile device to:

determine, by the processor, a status associated with the mobile device, wherein the status is indicative that user interaction with the mobile device is to be prevented;

detect activity in a first application, wherein the activity is prohibited based on the determined status of the mobile device; and

in response to the detected activity, invoke one or more Voice over Internet Protocol (VoIP) application programming interface (API) functions by a second application to prevent user interaction with the first application on the mobile device, wherein to invoke the one or more VoIP API functions causes the mobile device to display the second application in the foreground of the mobile device.

8. The computer-readable storage medium of claim 7 , wherein to display the second application in the foreground of the mobile device prevents user interaction with the first application.

9. The computer-readable storage medium of claim 7 , wherein to invoke the one or more API functions causes the mobile device to:

generate a VoIP call notification by the second application; and

display the VoIP call notification in the foreground of the mobile device, wherein to display the VoIP call notification prevents user interaction with the first application.

10. The computer-readable storage medium of claim 9 , wherein the VoIP call notification includes a caller name, and wherein the computer-executable instructions further cause the mobile device to:

change the caller name in the VoIP call notification to an indication that the activity is being prevented.

11. The computer-readable storage medium of claim 7 , wherein the operation further causes the mobile device to:

generate a notification indicating that the activity is being prevented; and

display the notification in the foreground of the mobile device.

12. The computer-readable storage medium of claim 7 , wherein the detected activity is further prohibited based on the first application corresponding to a blacklisted application.

13. A mobile device comprising:

a processor; and

a memory storing computer-executable instructions, which, when executed on the processor, causes a mobile device to perform an operation for preventing user interaction in a mobile device, the operation causing the mobile device to:

determine, by the processor, a status associated with the mobile device, wherein the status is indicative that user interaction with the mobile device is to be prevented;

detect activity in a first application, wherein the activity is prohibited based on the determined status of the mobile device; and

in response to the detected activity, invoke one or more application programming interface (API) functions by a second application to prevent user interaction with the first application on the mobile device, wherein to invoke the one or more VoIP API functions causes the mobile device to display the second application in the foreground of the mobile device, and wherein to display the second application in the foreground of the mobile device prevents user interaction with the first application.

14. The mobile device of claim 13 , wherein to invoke the one or more API functions further causes the mobile device to:

generate a VoIP call notification by the second application; and

display the VoIP call notification in the foreground of the mobile device, wherein to display the VoIP call notification prevents user interaction with the first application.

15. The mobile device of claim 14 , wherein the VoIP call notification includes a caller name, and wherein the computer-executable instructions further cause the mobile device to:

change the caller name in the VoIP call notification to an indication that the activity is being prevented.

16. The mobile device of claim 13 , wherein the operation further causes the mobile device to:

generate a notification indicating that the activity is being prevented; and

display the notification in the foreground of the mobile device.

17. The mobile device of claim 13 , wherein the detected activity is further prohibited based on the first application corresponding to a blacklisted application.

18. A method for preventing user interaction in a mobile device, comprising:

determining, by a processor of the mobile device, a status associated with the mobile device, wherein the status is indicative that user interaction with the mobile device is to be prevented;

detecting activity in a first application, wherein the activity is prohibited based on the determined status of the mobile device; and

in response to the detected activity, invoking one or more Voice over Internet Protocol (VoIP) application programming interface (API) functions by a second application to prevent user interaction with the first application on the mobile device, wherein invoking the one or more API functions causes the mobile device to (i) generate a VoIP call notification by the second application and (ii) display the VoIP call notification in the foreground of the mobile device, wherein to display the VoIP call notification prevents user interaction with the first application.

19. A method for preventing user interaction in a mobile device, comprising:

determining, by a processor of the mobile device, a status associated with the mobile device, wherein the status is indicative that user interaction with the mobile device is to be prevented;

detecting activity in a first application, wherein the activity is prohibited based on the determined status of the mobile device;

in response to the detected activity, invoking one or more Voice over Internet Protocol (VoIP) application programming interface (API) functions by a second application to prevent user interaction with the first application on the mobile device;

generating a notification indicating that the activity is prohibited; and

displaying the notification in the foreground of the mobile device.

Assignments (5)
RELEASE OF SECURITY INTEREST Recorded Oct 14, 2021
From: WESTERN ALLIANCE BANK
To: CELLCONTROL, INC. D/B/A TRUCE SOFTWARE, INC.
Reel/Frame 057793/0937 →
CORRECTIVE ASSIGNMENT TO CORRECT THE THE NATURE OF CONVEYANCE NEEDS TO BE SWITCHED FROM ASSIGNMENT TO SECURITY INTEREST PREVIOUSLY RECORDED AT REEL: 053089 FRAME: 0001. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 8, 2020
From: CELLCONTROL, INC.
To: WESTERN ALLIANCE BANK
Reel/Frame 053718/0545 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 30, 2020
From: CELLCONTROL, INC.
To: WESTERN ALLIANCE BANK
Reel/Frame 053089/0001 →
SIMULTANEOUS ENTITY CONVERSION, DOMICILE CHANGE, AND NAME CHANGE Recorded Apr 16, 2018
From: OBDEDGE, LLC
To: CELLCONTROL, INC.
Reel/Frame 045953/0552 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 28, 2017
From: BREAUX, JOSEPH E, III; WRIGHT, JOHN
To: OBDEDGE, LLC
Reel/Frame 044230/0940 →
Continuity (9)
Continuation In Part 15191353 · Jun 23, 2016
Continuation In Part 14944178 · Nov 17, 2015
Continuation 14273505 · May 8, 2014
Provisional Application 62353015 · Jun 21, 2016
Provisional Application 62183452 · Jun 23, 2015
Provisional Application 61936152 · Feb 5, 2014
Provisional Application 61892406 · Oct 17, 2013
Provisional Application 61821019 · May 8, 2013
Related Publication 20180070290A1 · Mar 8, 2018
Cited By (6)
US 12,376,069 US 12,581,269 US 12,621,639 US 12,658,018 US 12,696,173 US 12,707,371