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

• US 10,477,454 B2
• Filed: 06/21/2017
• Issued: 11/12/2019
• Est. Priority Date: 05/08/2013
• Status: Active Grant

• Current Assignee: Cellcontrol, Inc.
• Original Assignee: Cellcontrol, Inc.
• Inventors: Breaux, Joseph E., Wright, John
• Primary Examiner(s): Tran, Congvan
• Application Number:
  US15/629,710
• Publication Number:
  US 20180070290A1
• Time in Patent Office: 874 Days
• Field of Search: 455418-420, 4554561, 4554564, 455550
• CPC Class Codes: G06F 3/0227 Cooperation and interconnection of the input arrangement with other functional units of a computer G06F3/023 - G06F3/037 take precedence
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04M 1/724098 Interfacing with an on-board device of a vehicle for hands-free speaking in vehicles H04M1/6075
• CPC Class Codes: H04M 1/72463 to restrict the functionality of the device
• CPC Class Codes: H04M 1/724631 by limiting the access to the user interface, e.g. locking a touch-screen or a keypad
• CPC Class Codes: H04R 2420/07 Applications of wireless loudspeakers or wireless microphones
• CPC Class Codes: H04R 2499/13 Acoustic transducers and sound field adaptation in vehicles
• CPC Class Codes: H04R 3/12 for distributing signals to two or more loudspeakers specially adapted for hearing aids H04R25/407
• CPC Class Codes: H04W 4/027 using movement velocity, acceleration information
• CPC Class Codes: H04W 4/029 Location-based management or tracking services
• CPC Class Codes: H04W 4/33 for indoor environments, e.g. buildings
• CPC Class Codes: H04W 4/40 for vehicles, e.g. vehicle-to-pedestrians [V2P]
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 48/04 based on user or terminal location or mobility data, e.g. moving direction, speed
• CPC Class Codes: H04W 76/14 Direct-mode setup
• CPC Class Codes: H04W 84/12 WLAN [Wireless Local Area Networks]
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks

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

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.