IP Library Granted Patent US 9,686,747
Granted Patent B1
US 9,686,747 · App. 15/341,486 · Granted Jun 20, 2017

Regulate current battery usage of a mobile device

Inventors: James K. Noble, Jr. (Marietta, GA); Christopher S. Haggerty (Atlanta, GA)
Assignee: NOBLE SYSTEMS CORPORATION
H04W52/0261G08B21/182H02J7/0047H02J7/0054
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 9,686,747
App. No.
15/341,486
Granted
Jun 20, 2017
Kind
B1
Abstract

Various embodiments of the invention provide methods, systems, and computer-program products for charging a battery of a first mobile device from a battery of a second mobile device. In particular embodiments, a request is received identifying an amount of charge to provide from the battery of the second device to the battery of the first device. Accordingly, a determination is made as to whether the amount of charge requested is likely to result in a battery charge of the second device dropping below a threshold value before the battery of the device is recharged based on historical battery charge usage data of the device over a past period of time. If the amount of charge is not likely to result in the battery charge dropping below the threshold value, then the battery of the first device is charged with the amount of charge from the battery of the second device.

Claims (33)

1. A method for regulating current battery usage of a mobile device, the method comprising the steps of:

taking a first reading of a current battery charge of a battery of the mobile device by a computer-program application residing in the mobile device upon detecting a triggering event;

taking a second reading of the current battery charge of the battery by the computer-program application after a period of time has passed from when the triggering event was detected;

determining the current battery usage based on a difference between the first reading and the second reading of the current battery charge by the computer-program application;

determining by the computer-program application whether the current battery usage is likely to result in the current battery charge of the battery dropping below a threshold value before the battery is recharged based on historical battery charge usage data of the mobile device over a past period of time; and

advising a user of the mobile device via the computer-program application in response to determining the current battery usage is likely to result in the current battery charge of the mobile device dropping below the threshold value before the battery of the mobile device is recharged.

2. The method of claim 1 , wherein the triggering event comprises an activity beginning that requires power to be provided from the battery of the mobile device to function or an indication being provided by the user of the mobile device.

3. The method of claim 2 , wherein the activity beginning comprises one of another computer-program application residing in the mobile device being activated or a peripheral being connected to the mobile device.

4. The method of claim 2 , wherein the indication provided by the user of the mobile device comprises the user selecting a control within the computer-program application.

5. The method of claim 1 further comprising the step of determining the period of time by the computer-program application based on at least one of a number of activities currently activated that require power to be provided from the battery of the mobile device to function and types of activities currently activated that require power to be provided from the battery of the mobile device to function.

6. The method of claim 1 , wherein the historical battery charge usage data comprises a mean battery charge provided by the battery of the mobile device over a period of time starting from a time the triggering event was detected to a time the battery is likely to be recharged that is calculated based on battery charge usage for the mobile device over the past period of time.

7. A mobile device comprising a computer-program application residing in the mobile device configured to:

take a first reading of a current battery charge of a battery of the mobile device upon detecting a triggering event;

take a second reading of the current battery charge of the battery after a period of time has passed from when the triggering event was detected;

determine the current battery usage based on a difference between the first reading and the second reading of the current battery charge;

determine whether the current battery usage is likely to result in the current battery charge of the battery dropping below a threshold value before the battery is recharged based on historical battery charge usage data of the mobile device over a past period of time; and

advise a user of the mobile device in response to determining the current battery usage is likely to result in the current battery charge of the mobile device dropping below the threshold value before the battery of the mobile device is recharged.

8. The mobile device of claim 7 , wherein the triggering event comprises an activity beginning that requires power to be provided from the battery of the mobile device to function or an indication being provided by the user of the mobile device.

9. The mobile device of claim 8 , wherein the activity beginning comprises one of another computer-program application residing in the mobile device being activated or a peripheral being connected to the mobile device.

10. The mobile device of claim 8 , wherein the indication provided by the user of the mobile device comprises the user selecting a control within the computer-program application.

11. The mobile device of claim 7 , wherein the computer-program application is configured to determine the period of time based on at least one of a number of activities currently activated that require power to be provided from the battery of the mobile device to function and types of activities currently activated that require power to be provided from the battery of the mobile device to function.

12. The mobile device of claim 7 , wherein the historical battery charge usage data comprises a mean battery charge provided by the battery of the mobile device over a period of time starting from a time the triggering event was detected to a time the battery is likely to be recharged that is calculated based on battery charge usage for the mobile device over the past period of time.

13. A non-transitory, computer-readable medium comprising computer-executable instructions configured when executed to cause a mobile device to:

take a first reading of a current battery charge of a battery of the mobile device upon detecting a triggering event;

take a second reading of the current battery charge of the battery after a period of time has passed from when the triggering event was detected;

determine the current battery usage based on a difference between the first reading and the second reading of the current battery charge;

determine whether the current battery usage is likely to result in the current battery charge of the battery dropping below a threshold value before the battery is recharged based on historical battery charge usage data of the mobile device over a past period of time; and

advise a user of the mobile device in response to determining the current battery usage is likely to result in the current battery charge of the mobile device dropping below the threshold value before the battery of the mobile device is recharged.

14. The non-transitory, computer-readable medium of claim 13 , wherein the triggering event comprises an activity beginning that requires power to be provided from the battery of the mobile device to function or an indication being provided by the user of the mobile device.

15. The non-transitory, computer-readable medium of claim 14 , wherein the activity beginning comprises one of another computer-program application residing in the mobile device being activated or a peripheral being connected to the mobile device.

16. The non-transitory, computer-readable medium of claim 14 , wherein the indication provided by the user of the mobile device comprises the user selecting a control within the computer-program application.

17. The non-transitory, computer-readable medium of claim 13 , wherein the computer-executable instructions are configured when executed to cause the mobile device to determine the period of time based on at least one of a number of activities currently activated that require power to be provided from the battery of the mobile device to function and types of activities currently activated that require power to be provided from the battery of the mobile device to function.

18. The non-transitory, computer-readable medium of claim 13 , wherein the historical battery charge usage data comprises a mean battery charge provided by the battery of the mobile device over a period of time starting from a time the triggering event was detected to a time the battery is likely to be recharged that is calculated based on battery charge usage for the mobile device over the past period of time.

Assignments (11)
RELEASE OF SECURITY INTEREST Recorded Oct 27, 2025
From: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
To: ALVARIA CAYMAN (WEM); ALVARIA CAYMAN (CXIP)
Reel/Frame 073360/0209 →
PATENT SECURITY AGREEMENT Recorded Mar 20, 2024
From: ALVARIA CAYMAN (WEM); ALVARIA CAYMAN (CXIP)
To: JEFFERIES FINANCE LLC
Reel/Frame 066850/0334 →
RELEASE OF SECURITY INTEREST Recorded Mar 20, 2024
From: JEFFRIES FINANCE LLC
To: ALVARIA, INC.; NOBLE SYSTEMS, LLC
Reel/Frame 066850/0384 →
RELEASE OF SECURITY INTEREST Recorded Mar 20, 2024
From: JEFFRIES FINANCE LLC
To: ALVARIA, INC.; NOBLE SYSTEMS, LLC
Reel/Frame 066850/0428 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 20, 2024
From: NOBLE SYSTEMS, LLC
To: ALVARIA CAYMAN (CX)
Reel/Frame 066850/0556 →
CERTIFICATE OF CONVERSION Recorded Mar 12, 2024
From: NOBLE SYSTEMS CORPORATION, A GEORGIA CORPORATION
To: NOBLE SYSTEMS, LLC, A DELAWARE LIMITED LIABILITY COMPANY
Reel/Frame 066794/0435 →
RELEASE OF SECURITY INTEREST Recorded May 10, 2021
From: WELLS FARGO CAPITAL FINANCE, LLC
To: NOBLE SYSTEMS CORPORATION
Reel/Frame 056193/0363 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded May 6, 2021
From: NOBLE SYSTEMS CORPORATION; ASPECT SOFTWARE, INC.
To: JEFFERIES FINANCE LLC
Reel/Frame 057674/0664 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded May 6, 2021
From: NOBLE SYSTEMS CORPORATION; ASPECT SOFTWARE, INC.
To: JEFFERIES FINANCE LLC
Reel/Frame 057261/0093 →
SECURITY INTEREST Recorded Apr 23, 2020
From: NOBLE SYSTEMS CORPORATION
To: WELLS FARGO CAPITAL FINANCE, LLC
Reel/Frame 052495/0287 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 2, 2016
From: NOBLE, JAMES K, JR; HAGGERTY, CHRISTOPHER S
To: NOBLE SYSTEMS CORPORATION
Reel/Frame 040198/0679 →
Continuity (2)
Continuation 15210939 · Jul 15, 2016
Continuation 14454938 · Aug 8, 2014