[go: up one dir, main page]

US11816002B2 - Method for a data backup unit to intelligently charge a mobile device - Google Patents

Method for a data backup unit to intelligently charge a mobile device Download PDF

Info

Publication number
US11816002B2
US11816002B2 US17/474,608 US202117474608A US11816002B2 US 11816002 B2 US11816002 B2 US 11816002B2 US 202117474608 A US202117474608 A US 202117474608A US 11816002 B2 US11816002 B2 US 11816002B2
Authority
US
United States
Prior art keywords
app
charging
mobile device
backup
unit
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US17/474,608
Other versions
US20230077858A1 (en
Inventor
Calvinson Chang
Stanley Chu
Chihhan Chou
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vinpower Inc
Original Assignee
Vinpower Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vinpower Inc filed Critical Vinpower Inc
Priority to US17/474,608 priority Critical patent/US11816002B2/en
Assigned to VINPOWER INC. reassignment VINPOWER INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CHANG, CALVINSON, CHOU, CHIHHAN, CHU, STANLEY
Priority to TW110139372A priority patent/TWI769946B/en
Publication of US20230077858A1 publication Critical patent/US20230077858A1/en
Application granted granted Critical
Publication of US11816002B2 publication Critical patent/US11816002B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1461—Backup scheduling policy
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26—Power supply means, e.g. regulation thereof
    • G06F1/30—Means for acting in the event of power-supply failure or interruption, e.g. power-supply fluctuations
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26—Power supply means, e.g. regulation thereof
    • G06F1/32—Means for saving power
    • G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
    • G06F1/3206—Monitoring of events, devices or parameters that trigger a change in power modality
    • G06F1/3212—Monitoring battery levels, e.g. power saving mode being initiated when battery voltage goes below a certain level
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3058—Monitoring arrangements for monitoring environmental properties or parameters of the computing system or of the computing system component, e.g. monitoring of power, currents, temperature, humidity, position, vibrations
    • G06F11/3062—Monitoring arrangements for monitoring environmental properties or parameters of the computing system or of the computing system component, e.g. monitoring of power, currents, temperature, humidity, position, vibrations where the monitored property is the power consumption
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • H—ELECTRICITY
    • H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
    • H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
    • H02J7/00—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries
    • H02J7/0047—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries with monitoring or indicating devices or circuits
    • H02J7/0048—Detection of remaining charge capacity or state of charge [SOC]
    • H—ELECTRICITY
    • H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
    • H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
    • H02J7/00—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries
    • H02J7/007—Regulation of charging or discharging current or voltage
    • H02J7/00712—Regulation of charging or discharging current or voltage the cycle being controlled or terminated in response to electric parameters
    • H02J7/007182—Regulation of charging or discharging current or voltage the cycle being controlled or terminated in response to electric parameters in response to battery voltage
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/02—Digital function generators
    • G06F1/03—Digital function generators working, at least partly, by table look-up
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26—Power supply means, e.g. regulation thereof
    • G06F1/28—Supervision thereof, e.g. detecting power-supply failure by out of limits supervision
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3013—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is an embedded system, i.e. a combination of hardware and software dedicated to perform a certain function in mobile devices, printers, automotive or aircraft systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/80—Database-specific techniques
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
    • G06F9/4451—User profiles; Roaming
    • H—ELECTRICITY
    • H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
    • H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
    • H02J2207/00—Indexing scheme relating to details of circuit arrangements for charging or depolarising batteries or for supplying loads from batteries
    • H02J2207/30—Charge provided using DC bus or data bus of a computer
    • H—ELECTRICITY
    • H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
    • H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
    • H02J7/00—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries
    • H02J7/00032—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries characterised by data exchange
    • H02J7/00045—Authentication, i.e. circuits for checking compatibility between one component, e.g. a battery or a battery charger, and another component, e.g. a power source

Definitions

  • the present invention relates to a method for charging a mobile device, especially a method for a data backup unit to intelligently charge a mobile device.
  • the amount of data stored in a mobile device is increasing day by day. Therefore, backing up data stored on a mobile device has become a routine chore that a mobile device user must face. Nevertheless, charging a mobile device battery is also an essential daily routine to normally operate the mobile device. Therefore, a shortened charging time and a lower charging cost are both constantly demanded by mobile device users.
  • the main purpose of the present invention is to provide a data backup unit to automatically back up files while intelligently charging a mobile device
  • the method for a data backup unit to intelligently charge a mobile device of the present invention is as follows.
  • the data backup unit includes a memory unit which includes charging preferences and backup preferences and the mobile device includes a battery
  • the method for a data backup unit to intelligently charge a mobile device of the present invention includes the following steps:
  • the power ON/OFF mode setting routine includes the following steps:
  • the power on mode routine includes the following actions:
  • the App determines whether a rapid charging option set by the charging preferences is TRUE, and if the rapid charging option is TRUE, charge the battery under a rapid charging mode, otherwise if the rapid charging option is FALSE, charge the battery under a normal charging mode.
  • the charging preferences include a maximum charge level data, a minimum charge level data, a mobile device usage starting time data, an off-peak time interval data, an off-peak charging option, and a rapid charging option.
  • step S 1 the following steps are further included before step S 1 :
  • the App when the App creates a user profile block in the memory unit of the data backup unit, the App also writes an identification code of the mobile device into the user profile block.
  • the App when the App creates a backup folder, the App also creates a backup folder pointer in the user profile block to point to the backup folder.
  • FIG. 1 is a schematic diagram of the data backup unit of the present invention
  • FIG. 2 shows the contents of the memory unit of the data backup unit of the present invention.
  • FIGS. 3 A, 3 B, 3 C, 3 D, and 3 E are flowcharts for the method for a data backup unit to intelligently charge a mobile device of the present invention.
  • FIG. 1 is a schematic diagram of the data backup unit 1 of the present invention.
  • the data backup unit 1 of the present invention includes a power input interface 11 , a mobile device interface 12 , an authentication component 13 , a power conversion and control circuitry 14 , a charging protocol component 15 , a master control circuitry 16 , and a memory unit 17 .
  • the power input interface 11 is used to connect to a power source 2 .
  • the power input interface 11 can be compatible with connection interfaces such as Universal Serial Bus (USB) TYPE A, USB TYPE C, or Lightning, etc.
  • the mobile device interface 12 is used to connect a first end of a cable 4 , while a second end of the cable 4 is connected to a mobile device 3 .
  • the mobile device interface 12 can be compatible with USB TYPE A, USB TYPE C, or Lightning, etc. In this way, the data backup unit 1 of the present invention is connected to the mobile device 3 via the cable 4 , and the data backup unit 1 of the present invention can provide power to the mobile device 3 .
  • the cable 4 can be a mobile device cable for charging and data transmission, such as a USB_A to Lightning cable, a Lightning to USB_C cable, a USB_A cable, a USB_C cable, a Lightning cable, or a USB_A to USB_C cable, etc.
  • the authentication component 13 can be an integrated circuit (IC), which is used for the mobile device 3 to authenticate the data backup unit 1 of the present invention.
  • the authentication component 13 may be an MFi (Made For iPhone/iPod/iPad) chip, so that an Apple® mobile device 3 can authenticate the data backup unit 1 of the present invention as a qualified device through the MFi chip when the data backup unit 1 is connected to the Apple® mobile device 3 .
  • the power conversion and control circuitry 14 communicates with the mobile device 3 in cooperation with the charging protocol component 15 and outputs appropriate voltage and current to the mobile device 3 to charge a rechargeable battery 33 (abbreviated as a battery, hereinafter) of the mobile device 3 .
  • a rechargeable battery 33 abbreviated as a battery, hereinafter
  • the cable 4 can be used to transmit data and power.
  • the master control circuitry 16 communicates with the mobile device 3 via the mobile device interface 12 and the cable 4 , so that the mobile device 3 can back up its data to the memory unit 17 .
  • the master control circuitry 16 can be a microcontroller, a central processing unit (CPU), a programmable logic array (FPGA) or an application-specific integrated circuit (ASIC).
  • the memory unit 17 can be static memory (SRAM), dynamic memory (DRAM), magnetic memory (MRAM), flash memory (FLASH memory), etc., or a combination thereof.
  • the memory unit 17 can also be an external memory device, such as a hard disk drive (HDD), a solid state drive (SSD), an SD memory card, a USB flash drive, and so on.
  • FIG. 2 shows the contents of the memory unit 17 .
  • the memory unit 17 is used to store information of multiple mobile devices 3 , wherein, with respect to each mobile device 3 , a user profile block 170 corresponding to a respective mobile device 3 is created in the memory unit 17 .
  • the user profile block 170 includes an identity field 171 for storing an identification code of the mobile device 3 , such as a mobile handset International Mobile Equipment Identity (IMEI) number, charging preferences 173 , backup preferences 174 , and a backup folder pointer 175 specifically for the respective mobile device 3 .
  • the backup folder pointer 175 points to a backup folder 176 which is also specifically for the respective mobile device 3 .
  • IMEI mobile handset International Mobile Equipment Identity
  • the charging preferences 173 include a maximum charge level data and a minimum charge level data for the battery 33 of the mobile device 3 , a mobile device usage starting time data, an off-peak time interval data, an off-peak charging option, a rapid charging option, a unit charging time, and a unit waiting time.
  • the backup preferences include a backup folder read-only option data, and a backup folder password option data.
  • a maximum charge level is set by the maximum charge level data to indicate completion of battery charging for the mobile device 3 , for example 95-99%; and a minimum charge level is set by the minimum charge level data to indicate the battery 33 of the mobile device 3 has minimum energy required to complete the data backup operation for the mobile device 3 , for example 50-60%; and a usage starting time is set by the mobile device usage starting time data to indicate the starting time expected by the user to use the mobile device in the beginning of a day, for example 7:00 AM; and an off-peak time interval is set by the off-peak time interval data to indicate an off-peak discount period, for example 10:00 PM-7:00 AM, during which users may save utility costs.
  • the off-peak charging option has two values TRUE and FALSE, if the off-peak charging option is TRUE, then charging the mobile device battery during the off-peak time interval shall be preferred; otherwise, there is no preferred time restriction for charging the mobile device.
  • the rapid charging option has two values TRUE and FALSE, if the rapid charging option is TRUE, then charging the mobile device battery shall be carried out in a rapid charging mode; otherwise, charging the mobile device battery shall be carried out in a normal charging mode. Whether the mobile device supporting the rapid charging mode or not depends on intrinsic functionalities of the mobile device and charging cables, and a user needs to figure out whether the mobile device and charging cables support the rapid charging mode. Examples for rapid charging technologies are USB Power Delivery (USB PD) and Quick Charge® (QC), etc. Those mobile devices that do not support the rapid charging mode shall support the normal charging mode which is a basic charging function, yet provides less output power than the rapid charging mode does.
  • USB PD USB Power Delivery
  • QC Quick Charge®
  • the backup folder 176 of the memory unit 17 stores the backup data of the mobile device 3 such as local files 31 and cloud files 32 .
  • the backup folder 176 of the memory unit 17 stores the backup data of the mobile device 3 such as local files 31 and cloud files 32 .
  • there are multiple user profile blocks 170 , 180 which respectively include backup folder pointers 175 , 185 pointing to backup folders 176 , 186 , respectively. Accordingly, the data backup unit 1 can provide data backup functions for multiple mobile devices.
  • FIGS. 3 A- 3 D are about the flow of the method for a data backup unit to intelligently charge a mobile device of the present invention.
  • the mobile device 3 must execute an application program (abbreviated as App, hereinafter) 30 to intelligently charge a mobile device and automatically back up the data accessible from the mobile device 3 to the memory unit 17 of the data backup unit 1 .
  • App application program
  • the mobile device 3 In the initialization step 0 _ 0 (S 0 _ 0 ) in FIG. 3 A , the mobile device 3 must be connected to the data backup unit 1 via the cable 4 , and then the mobile device 3 is recognized by the data backup unit 1 via the authentication component 13 and the power conversion and control circuitry 14 . Then, the App 30 is able to control the data backup unit 1 to supply power to the mobile device 3 .
  • the data accessible from the mobile device 3 includes local files 31 and cloud files 32 .
  • step 0 _ 1 (S 0 _ 1 ) in FIG. 3 A , the mobile device 3 decides whether the App 30 has been installed. If the mobile device 3 has not yet installed the App 30 , then in step 0 _ 2 (S 0 _ 2 ) in FIG. 3 A , the mobile device 3 shall remind the user of the mobile device 3 to install the App 30 .
  • step 1 (S 1 ) in FIG. 3 A the App 30 shall confirm whether the mobile device 3 has ever connected with the data backup unit 1 ; for example, the App 30 searches and compares all user profile blocks 170 , 180 , etc. in the memory unit 17 of the data backup unit 1 to confirm whether the content of the identity field 171 or the content of the identity field 181 is the same as that of the identification code of the mobile device 3 , such as an IMEI number, so as to confirm whether the mobile device 3 has ever used the data backup unit 1 . If the mobile device 3 has not used the data backup unit 1 , then in step 1 _ 1 (S 1 _ 1 ) in FIG.
  • the App 30 generates a user profile block 170 in the memory unit 17 of the data backup unit 1 , and the App 30 writes the identification code of the mobile device 3 , such as the IMEI number, to the identity field 171 of the profile 170 .
  • the user is also required to set the charging preferences 173 and the data backup preferences 174 , and then go to the next step; and if the mobile device 3 has ever connected with the data backup unit 1 before, go to the next step.
  • step 2 (S 2 ) in FIG. 3 A the App 30 shall confirm whether the mobile device 3 has ever backed up data in the data backup unit 1 .
  • the App 30 searches the corresponding user profile block 170 in the memory unit for whether there is a backup folder pointer 175 , so as to confirm that the mobile device 3 has backed up data in the data backup unit 1 .
  • step 2 _ 1 the App 30 generates a backup folder 176 in the memory unit 17 of the data backup unit 1 , and create a backup folder pointer 175 in the user profile block 170 to point to the newly generated backup folder 176 , and then go to the next step; and if the mobile device 3 has backed up data in the data backup unit 1 , go to the next step.
  • step 3 (S 3 ) in FIG. 3 A the App 30 shall read a present charge level of the battery 33 of the mobile device 3 from the mobile device 3 and determine whether said present charge level of the battery is lower than the minimum charge level. If the present charge level of the battery is lower than the minimum charge level, the flow jumps to step 4 (S 4 ), otherwise, if the present charge level of the battery is higher than or equal to the minimum charge level, the flow jumps to step 5 (S 5 ).
  • step 4 (S 4 ) of FIG. 3 A the App 30 shall determine whether a power-off mode is ongoing, and if the power-off mode is ongoing, the App enters a power-on mode routine; next, the App 30 waits for one unit charging time, and then the flow loops back to step 3 (S 3 ).
  • the power-off mode denotes that the App 30 stops the data backup unit from charging the mobile device. The power-on mode routine is discussed later.
  • step 5 (S 5 ) in FIG. 3 A based on the rapid charging option in charging preferences 173 , the App 30 shall estimate a charging time which is required for the data backup unit 1 to charge the battery 33 of the mobile device 3 from the present charge level to the maximum charge level; for example, if an estimated energy of 0.054 MJ (Mega Joule) is required to charge the battery from the present charge level to the maximum charge level, and the charging modes are known to be an output of 5 W for a normal charging mode and an output of 10 W for rapid charging mode, then the estimated charging time is 3 hours/1.5 hour respectively; the App 30 also estimates a backup time for the data backup unit 1 to complete the data backup for files to be backed up from the mobile device 3 , for example, for an estimated 24 GB (Giga Byte) data to be backed up, and the data transmission rate is known to be 40 MB (Mega Byte) per second, then the estimated backup time is 10 minutes. Finally, the App 30 sums up the charging time and the backup time
  • step 6 (S 6 ) of FIG. 3 A the App 30 shall calculate an available time interval which is equal to the time difference between a current time and the usage starting time.
  • step 7 (S 7 ) of FIG. 3 B the App 30 determines whether the required time interval is less than the available time interval, and if the required time interval is less than the available time interval, the flow jumps to step 8 (S 8 ), and if the required time interval is greater than or equal to the available time interval, the flow jumps to step 9 (S 9 ).
  • step 8 (S 8 ) of FIG. 3 C the App 30 starts to back up files to be backed up from the mobile device 3 for a unit backup time such as 1 to 10 minutes, and then the flow jumps to step 8 - 1 (S 8 - 1 ).
  • a unit backup time such as 1 to 10 minutes
  • step 8 - 1 (S 8 - 1 ) of FIG. 3 C the App 30 determines whether the file backup is done, and if the file backup is done, the flow jumps to step 8 - 2 (S 8 - 2 ) and if the file backup is not yet done, the flow jumps to step 8 - 3 (S 8 - 3 ).
  • step 8 - 2 (S 8 - 2 ) of FIG. 3 C the App 30 shall determine whether to set the files in the backup folder 176 as read-only, according to the backup folder read-only option data in the backup preferences 174 , so as to avoid accidental deletion or malicious hacking of the files; and at the same time, the App 30 shall determine whether to set password protection for the files in the backup folder 176 , according to the backup folder password option data in the backup preferences 174 , so that a password can be required for opening the files, which further protects the files. Then, the flow jumps to step 9 (S 9 ).
  • step 8 - 3 (S 8 - 3 ) of FIG. 3 C the App 30 shall determine whether the present charge level is lower than the minimum charge level, and if the present charge level is higher than or equal to the minimum charge level, then the flow jumps to step 8 - 5 (S 8 - 5 ).
  • step 8 - 4 (S 8 - 4 ) of FIG. 3 C the App 30 shall determine whether the power-off mode is ongoing, and if the power-off mode is ongoing, the App enters the power-on mode routine; next, the App 30 waits for one unit charging time, and then the flow loops back to step 8 - 3 (S 8 - 3 ).
  • step 8 - 5 (S 8 - 5 ) of FIG. 3 C the App 30 starts to execute a power ON/OFF mode setting routine, and then the flow jumps back to step S 8 (S 8 ).
  • step 9 (S 9 ) of FIG. 3 B the App 30 starts to execute the power ON/OFF mode setting routine.
  • step 10 (S 10 ) of FIG. 3 B the App 30 shall wait for one unit charging time, and then the flow loops back to step 9 (S 9 ).
  • the power-on mode routine includes the following actions: firstly, the App 30 determines whether the rapid charging option set by the charging preferences is TRUE, and if the rapid charging option is TRUE, the App 30 charges the battery under a rapid charging mode, otherwise if the rapid charging option is FALSE, the App 30 charges the battery under a normal charging mode.
  • the power-on mode routine is used in step 4 (S 4 ), step 8 - 4 (S 8 - 4 ) and also in the power ON/OFF mode setting routine.
  • the power ON/OFF mode setting routine includes the following steps:

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Software Systems (AREA)
  • Quality & Reliability (AREA)
  • Power Engineering (AREA)
  • Mathematical Physics (AREA)
  • Charge And Discharge Circuits For Batteries Or The Like (AREA)
  • Telephone Function (AREA)

Abstract

After a data backup unit connects to a mobile device, an App executed on the mobile device will create a user profile block in the memory unit of the data backup unit, help set up charging preferences and backup preferences in the profile block, and create a backup folder to store backup files from the mobile device. The App estimates a charging time required to charge the battery, a backup time required to complete the data backup and an available time interval, then the App sums up the charging time and the backup time to get a required time interval. Then, the App compares the required time interval and the available time interval to decide whether to perform both the backup task and the charging task or to perform just the charging task.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention
The present invention relates to a method for charging a mobile device, especially a method for a data backup unit to intelligently charge a mobile device.
2. Description of the Related Art
Mobile phones or tablets, collectively “Mobile Devices”, have become an indispensable part of modern life. Statistically, the amount of data stored in a mobile device is increasing day by day. Therefore, backing up data stored on a mobile device has become a routine chore that a mobile device user must face. Nevertheless, charging a mobile device battery is also an essential daily routine to normally operate the mobile device. Therefore, a shortened charging time and a lower charging cost are both constantly demanded by mobile device users.
Hence, there are urgent needs for intelligent charging methods well adopted to reduce time and costs, and there are also urgent needs for seamlessly incorporating both the action of charging and the action of data backup, so that common users of mobile devices can effortlessly utilize both functionalities in one act.
SUMMARY OF THE INVENTION
In view of the above-mentioned needs, the main purpose of the present invention is to provide a data backup unit to automatically back up files while intelligently charging a mobile device, and the method for a data backup unit to intelligently charge a mobile device of the present invention is as follows.
Firstly, provide a data backup unit, and an application program (abbreviated as App, hereinafter) executed on a mobile device. The data backup unit includes a memory unit which includes charging preferences and backup preferences and the mobile device includes a battery, and the method for a data backup unit to intelligently charge a mobile device of the present invention includes the following steps:
    • S1: The App determines whether the mobile device has ever connected with the data backup unit; if the mobile device has ever connected with the data backup unit, the flow jumps to S2;
    • S11: The App creates a user profile block in the memory unit of the data backup unit, and sets up the backup preferences and the charging preferences in the user profile block;
    • S2: The App determines whether the mobile device has ever backed up files in the charging unit; if the mobile device has ever backed up files in the charging unit, the flow jumps to S3; and
    • S2_1: The App creates a new backup folder in the memory unit;
    • S3: The App determines whether a present charge level of the battery provided by the mobile device is lower than a minimum charge level set by the charging preferences, and if the present charge level is higher than or equal to the minimum charge level, the flow jumps to S5;
    • S4: The App determines whether power-off mode is ongoing, and if power-off mode is ongoing, the App enters a power-on mode routine; waits for one unit charging time, and then the flow jumps to step S3;
    • S5: According to the charging preferences, the App estimates a charging time required to charge the battery to the maximum charge level and estimates a backup time required to complete the data backup, and then sums up the charging time and the backup time to get a required time interval;
    • S6: The App calculates an available time interval which is equal to a time difference between a current time provided by the mobile device and a usage starting time set by the charging preferences;
    • S7: The App determines whether the required time interval is less than the available time interval, and if the required time interval is greater than or equal to the available time interval, the flow jumps to S9, otherwise, if the required time interval is less than the available time interval, the flow jumps to S8;
    • S8: The App backs up files to be backed up for the mobile device for a unit backup time.
    • S8-1: The App determines whether the file backup is done, and if the file backup is not yet done, the flow jumps to step S8-3;
    • S8-2: The App determines whether to set the files been backed up as read-only according to the backup preferences; and the App determines whether to set the files been backed up with password protection according to the backup preferences; the flow jumps to step S9;
    • S8-3: The App determines whether the present charge level is lower than the minimum charge level, and if the present charge level of the battery is higher than or equal to the minimum charge level, the flow jumps to S8-5;
    • S8-4: The App determines whether power-off mode is ongoing, and if power-off mode is ongoing, the App enters the power-on mode routine; waiting for one unit charging time, and then the flow loops back to step S8-3;
    • S8-5: The App starts to execute a power ON/OFF mode setting routine, and then the flow jumps to step S8;
    • S9: The App starts to execute the power ON/OFF mode setting routine, and then the flow jumps to step S10; and
    • S10: The App waits for one unit charging time, and then the flow loops back to step S9.
Preferably, the power ON/OFF mode setting routine includes the following steps:
    • SR1: The App determines whether an off-peak charging option is FALSE or the current time is within an off-peak time interval, and if the off-peak charging option is FALSE or the current time is within the off-peak time interval, the flow jumps to step SR3;
    • SR2: The App stops the data backup unit from charging the mobile device, and next exits the power ON/OFF mode setting routine;
    • SR3: The App determines whether the present charge level is less than or equal to the maximum charge level, and if the present charge level is larger than the maximum charge level, the flow jumps to step SR2;
    • SR4: The App enters the power-on mode routine, and next exits the power ON/OFF mode setting routine.
Preferably, the power on mode routine includes the following actions:
The App determines whether a rapid charging option set by the charging preferences is TRUE, and if the rapid charging option is TRUE, charge the battery under a rapid charging mode, otherwise if the rapid charging option is FALSE, charge the battery under a normal charging mode.
Preferably, the charging preferences include a maximum charge level data, a minimum charge level data, a mobile device usage starting time data, an off-peak time interval data, an off-peak charging option, and a rapid charging option.
Preferably, the following steps are further included before step S1:
    • S0_0: The mobile device is connected to the data backup unit and the connection is authenticated;
    • S0_1: The mobile device decides whether the App has been installed, if the App is installed on the mobile device, then the mobile device executes step S1;
    • S0_2: The mobile device reminds the user of the mobile device to install the App.
Preferably, when the App creates a user profile block in the memory unit of the data backup unit, the App also writes an identification code of the mobile device into the user profile block.
Preferably, when the App creates a backup folder, the App also creates a backup folder pointer in the user profile block to point to the backup folder.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a schematic diagram of the data backup unit of the present invention;
FIG. 2 shows the contents of the memory unit of the data backup unit of the present invention; and
FIGS. 3A, 3B, 3C, 3D, and 3E are flowcharts for the method for a data backup unit to intelligently charge a mobile device of the present invention.
 DETAILED DESCRIPTION OF THE INVENTION
In the following, the technical solutions in the embodiments of the present invention will be clearly and fully described with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of, not all of, the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.
FIG. 1 is a schematic diagram of the data backup unit 1 of the present invention. The data backup unit 1 of the present invention includes a power input interface 11, a mobile device interface 12, an authentication component 13, a power conversion and control circuitry 14, a charging protocol component 15, a master control circuitry 16, and a memory unit 17.
The power input interface 11 is used to connect to a power source 2. The power input interface 11 can be compatible with connection interfaces such as Universal Serial Bus (USB) TYPE A, USB TYPE C, or Lightning, etc. The mobile device interface 12 is used to connect a first end of a cable 4, while a second end of the cable 4 is connected to a mobile device 3. The mobile device interface 12 can be compatible with USB TYPE A, USB TYPE C, or Lightning, etc. In this way, the data backup unit 1 of the present invention is connected to the mobile device 3 via the cable 4, and the data backup unit 1 of the present invention can provide power to the mobile device 3. The cable 4 can be a mobile device cable for charging and data transmission, such as a USB_A to Lightning cable, a Lightning to USB_C cable, a USB_A cable, a USB_C cable, a Lightning cable, or a USB_A to USB_C cable, etc.
The authentication component 13 can be an integrated circuit (IC), which is used for the mobile device 3 to authenticate the data backup unit 1 of the present invention. For example, the authentication component 13 may be an MFi (Made For iPhone/iPod/iPad) chip, so that an Apple® mobile device 3 can authenticate the data backup unit 1 of the present invention as a qualified device through the MFi chip when the data backup unit 1 is connected to the Apple® mobile device 3. The power conversion and control circuitry 14 communicates with the mobile device 3 in cooperation with the charging protocol component 15 and outputs appropriate voltage and current to the mobile device 3 to charge a rechargeable battery 33 (abbreviated as a battery, hereinafter) of the mobile device 3.
The cable 4 can be used to transmit data and power. The master control circuitry 16 communicates with the mobile device 3 via the mobile device interface 12 and the cable 4, so that the mobile device 3 can back up its data to the memory unit 17. The master control circuitry 16 can be a microcontroller, a central processing unit (CPU), a programmable logic array (FPGA) or an application-specific integrated circuit (ASIC). The memory unit 17 can be static memory (SRAM), dynamic memory (DRAM), magnetic memory (MRAM), flash memory (FLASH memory), etc., or a combination thereof. Moreover, the memory unit 17 can also be an external memory device, such as a hard disk drive (HDD), a solid state drive (SSD), an SD memory card, a USB flash drive, and so on.
FIG. 2 shows the contents of the memory unit 17. The memory unit 17 is used to store information of multiple mobile devices 3, wherein, with respect to each mobile device 3, a user profile block 170 corresponding to a respective mobile device 3 is created in the memory unit 17. The user profile block 170 includes an identity field 171 for storing an identification code of the mobile device 3, such as a mobile handset International Mobile Equipment Identity (IMEI) number, charging preferences 173, backup preferences 174, and a backup folder pointer 175 specifically for the respective mobile device 3. The backup folder pointer 175 points to a backup folder 176 which is also specifically for the respective mobile device 3. The charging preferences 173 include a maximum charge level data and a minimum charge level data for the battery 33 of the mobile device 3, a mobile device usage starting time data, an off-peak time interval data, an off-peak charging option, a rapid charging option, a unit charging time, and a unit waiting time. The backup preferences include a backup folder read-only option data, and a backup folder password option data.
A maximum charge level is set by the maximum charge level data to indicate completion of battery charging for the mobile device 3, for example 95-99%; and a minimum charge level is set by the minimum charge level data to indicate the battery 33 of the mobile device 3 has minimum energy required to complete the data backup operation for the mobile device 3, for example 50-60%; and a usage starting time is set by the mobile device usage starting time data to indicate the starting time expected by the user to use the mobile device in the beginning of a day, for example 7:00 AM; and an off-peak time interval is set by the off-peak time interval data to indicate an off-peak discount period, for example 10:00 PM-7:00 AM, during which users may save utility costs.
Moreover, the off-peak charging option has two values TRUE and FALSE, if the off-peak charging option is TRUE, then charging the mobile device battery during the off-peak time interval shall be preferred; otherwise, there is no preferred time restriction for charging the mobile device. The rapid charging option has two values TRUE and FALSE, if the rapid charging option is TRUE, then charging the mobile device battery shall be carried out in a rapid charging mode; otherwise, charging the mobile device battery shall be carried out in a normal charging mode. Whether the mobile device supporting the rapid charging mode or not depends on intrinsic functionalities of the mobile device and charging cables, and a user needs to figure out whether the mobile device and charging cables support the rapid charging mode. Examples for rapid charging technologies are USB Power Delivery (USB PD) and Quick Charge® (QC), etc. Those mobile devices that do not support the rapid charging mode shall support the normal charging mode which is a basic charging function, yet provides less output power than the rapid charging mode does.
In addition, the backup folder 176 of the memory unit 17 stores the backup data of the mobile device 3 such as local files 31 and cloud files 32. In FIG. 2 , there are multiple user profile blocks 170, 180, which respectively include backup folder pointers 175, 185 pointing to backup folders 176, 186, respectively. Accordingly, the data backup unit 1 can provide data backup functions for multiple mobile devices.
Please refer to FIGS. 3A-3D. FIGS. 3A-3D are about the flow of the method for a data backup unit to intelligently charge a mobile device of the present invention. The mobile device 3 must execute an application program (abbreviated as App, hereinafter) 30 to intelligently charge a mobile device and automatically back up the data accessible from the mobile device 3 to the memory unit 17 of the data backup unit 1.
In the initialization step 0_0 (S0_0) in FIG. 3A, the mobile device 3 must be connected to the data backup unit 1 via the cable 4, and then the mobile device 3 is recognized by the data backup unit 1 via the authentication component 13 and the power conversion and control circuitry 14. Then, the App 30 is able to control the data backup unit 1 to supply power to the mobile device 3. Wherein the data accessible from the mobile device 3 includes local files 31 and cloud files 32.
Then, in step 0_1 (S0_1) in FIG. 3A, the mobile device 3 decides whether the App 30 has been installed. If the mobile device 3 has not yet installed the App 30, then in step 0_2 (S0_2) in FIG. 3A, the mobile device 3 shall remind the user of the mobile device 3 to install the App 30.
After the mobile device 3 confirms that the App 30 has been installed, then in step 1 (S1) in FIG. 3A, the App 30 shall confirm whether the mobile device 3 has ever connected with the data backup unit 1; for example, the App 30 searches and compares all user profile blocks 170, 180, etc. in the memory unit 17 of the data backup unit 1 to confirm whether the content of the identity field 171 or the content of the identity field 181 is the same as that of the identification code of the mobile device 3, such as an IMEI number, so as to confirm whether the mobile device 3 has ever used the data backup unit 1. If the mobile device 3 has not used the data backup unit 1, then in step 1_1 (S1_1) in FIG. 3A, the App 30 generates a user profile block 170 in the memory unit 17 of the data backup unit 1, and the App 30 writes the identification code of the mobile device 3, such as the IMEI number, to the identity field 171 of the profile 170. Moreover, the user is also required to set the charging preferences 173 and the data backup preferences 174, and then go to the next step; and if the mobile device 3 has ever connected with the data backup unit 1 before, go to the next step.
In step 2 (S2) in FIG. 3A, the App 30 shall confirm whether the mobile device 3 has ever backed up data in the data backup unit 1. For example, the App 30 searches the corresponding user profile block 170 in the memory unit for whether there is a backup folder pointer 175, so as to confirm that the mobile device 3 has backed up data in the data backup unit 1. If the mobile device 3 has not backed up data in the data backup unit 1, then as shown in the figure in step 2_1 (S2_1), the App 30 generates a backup folder 176 in the memory unit 17 of the data backup unit 1, and create a backup folder pointer 175 in the user profile block 170 to point to the newly generated backup folder 176, and then go to the next step; and if the mobile device 3 has backed up data in the data backup unit 1, go to the next step.
Next, in step 3 (S3) in FIG. 3A, the App 30 shall read a present charge level of the battery 33 of the mobile device 3 from the mobile device 3 and determine whether said present charge level of the battery is lower than the minimum charge level. If the present charge level of the battery is lower than the minimum charge level, the flow jumps to step 4 (S4), otherwise, if the present charge level of the battery is higher than or equal to the minimum charge level, the flow jumps to step 5 (S5).
Next, in step 4 (S4) of FIG. 3A, the App 30 shall determine whether a power-off mode is ongoing, and if the power-off mode is ongoing, the App enters a power-on mode routine; next, the App 30 waits for one unit charging time, and then the flow loops back to step 3 (S3). Wherein the power-off mode denotes that the App 30 stops the data backup unit from charging the mobile device. The power-on mode routine is discussed later.
Then, in step 5 (S5) in FIG. 3A, based on the rapid charging option in charging preferences 173, the App 30 shall estimate a charging time which is required for the data backup unit 1 to charge the battery 33 of the mobile device 3 from the present charge level to the maximum charge level; for example, if an estimated energy of 0.054 MJ (Mega Joule) is required to charge the battery from the present charge level to the maximum charge level, and the charging modes are known to be an output of 5 W for a normal charging mode and an output of 10 W for rapid charging mode, then the estimated charging time is 3 hours/1.5 hour respectively; the App 30 also estimates a backup time for the data backup unit 1 to complete the data backup for files to be backed up from the mobile device 3, for example, for an estimated 24 GB (Giga Byte) data to be backed up, and the data transmission rate is known to be 40 MB (Mega Byte) per second, then the estimated backup time is 10 minutes. Finally, the App 30 sums up the charging time and the backup time, but not limited to such operation, to get a required time interval which is the estimation time interval to complete both tasks of charging and data backup.
Next, in step 6 (S6) of FIG. 3A, the App 30 shall calculate an available time interval which is equal to the time difference between a current time and the usage starting time.
Next, in step 7 (S7) of FIG. 3B, the App 30 determines whether the required time interval is less than the available time interval, and if the required time interval is less than the available time interval, the flow jumps to step 8 (S8), and if the required time interval is greater than or equal to the available time interval, the flow jumps to step 9 (S9).
Next, in step 8 (S8) of FIG. 3C, the App 30 starts to back up files to be backed up from the mobile device 3 for a unit backup time such as 1 to 10 minutes, and then the flow jumps to step 8-1 (S8-1). Please note that if the file backup is done before the expiration of one unit backup time, then depending on implementations, either the process is pending until one unit backup time is expired or the process immediately proceeds to the next step.
Next, in step 8-1 (S8-1) of FIG. 3C, the App 30 determines whether the file backup is done, and if the file backup is done, the flow jumps to step 8-2 (S8-2) and if the file backup is not yet done, the flow jumps to step 8-3 (S8-3).
Next, in step 8-2 (S8-2) of FIG. 3C, the App 30 shall determine whether to set the files in the backup folder 176 as read-only, according to the backup folder read-only option data in the backup preferences 174, so as to avoid accidental deletion or malicious hacking of the files; and at the same time, the App 30 shall determine whether to set password protection for the files in the backup folder 176, according to the backup folder password option data in the backup preferences 174, so that a password can be required for opening the files, which further protects the files. Then, the flow jumps to step 9 (S9).
Next, in step 8-3 (S8-3) of FIG. 3C, the App 30 shall determine whether the present charge level is lower than the minimum charge level, and if the present charge level is higher than or equal to the minimum charge level, then the flow jumps to step 8-5 (S8-5).
Next, in step 8-4 (S8-4) of FIG. 3C, the App 30 shall determine whether the power-off mode is ongoing, and if the power-off mode is ongoing, the App enters the power-on mode routine; next, the App 30 waits for one unit charging time, and then the flow loops back to step 8-3 (S8-3).
Next, in step 8-5 (S8-5) of FIG. 3C, the App 30 starts to execute a power ON/OFF mode setting routine, and then the flow jumps back to step S8 (S8).
Next, in step 9 (S9) of FIG. 3B, the App 30 starts to execute the power ON/OFF mode setting routine.
Next, in step 10 (S10) of FIG. 3B, the App 30 shall wait for one unit charging time, and then the flow loops back to step 9 (S9).
In FIG. 3D, the power-on mode routine is shown. The power-on mode routine includes the following actions: firstly, the App 30 determines whether the rapid charging option set by the charging preferences is TRUE, and if the rapid charging option is TRUE, the App 30 charges the battery under a rapid charging mode, otherwise if the rapid charging option is FALSE, the App 30 charges the battery under a normal charging mode. The power-on mode routine is used in step 4 (S4), step 8-4 (S8-4) and also in the power ON/OFF mode setting routine.
In FIG. 3E, the power ON/OFF mode setting routine is shown. The power ON/OFF mode setting routine includes the following steps:
    • SR1: The App 30 determines whether the off-peak charging option is FALSE or the current time is within the off-peak time interval, and if the off-peak charging option is FALSE or the current time is within the off-peak time interval, the flow jumps to step SR3;
    • SR2: The App 30 enters the power-off mode, i.e. the App 30 stops the data backup unit from charging the mobile device; and next, the flow exits the power ON/OFF mode setting routine;
    • SR3: The App 30 determines whether the present charge level is less than or equal to the maximum charge level, and if the present charge level is larger than the maximum charge level, the flow jumps to step SR2;
    • SR4: The App 30 enters the power-on mode routine; and next, the flow exits the power ON/OFF mode setting routine.
From the above steps of the method for a data backup unit to intelligently charge a mobile device of the present invention, it can be seen that after the data backup unit 1 is connected to the mobile device 3 and initialized, the App can make the data backup unit 1 and the mobile device 3 fully cooperate. Automatic charging can be accomplished and the file data accessible from the mobile device can be automatically backed up. This not only maintains the security of the data file stored on the mobile device, but also minimizes the burden upon the users and utility costs to back up data files accessible from the mobile device, therefore the urgent needs for intelligent charging methods which seamlessly incorporate the action of data backup can be achieved and the purpose of the present invention is fulfilled thereby.
The aforementioned are preferred embodiments of the present invention. It should be noted that for those of ordinary skill in the art, without departing from the principles of the present invention, certain improvements and retouches of the present invention can still be made which are nevertheless considered as within the protection scope of the present invention.
Even though numerous characteristics and advantages of the present invention have been set forth in the foregoing description, together with details of the structure and function of the invention, the disclosure is illustrative only. Changes may be made in detail, especially in matters of shape, size, and arrangement of parts within the principles of the invention to the full extent indicated by the broad general meaning of the terms in which the appended claims are expressed.

Claims (9)

What is claimed is:
1. A method for a data backup unit to intelligently charge a mobile device, the data backup unit having a memory unit which includes charging preferences and backup preferences, the mobile device having a battery and an application program (App), and the method including the following steps:
S3: the App determining whether a present charge level of the battery provided by the mobile device is lower than a minimum charge level set by the charging preferences, and if the present charge level is higher than or equal to the minimum charge level, the flow jumping to step S5;
S4: the App determining whether power-off mode is ongoing, and if power-off mode is ongoing, the App entering a power-on mode routine; waiting for one unit charging time, and then jumping to step S3;
S5: according to the charging preferences, the App estimating a charging time required to charge the battery to a maximum charge level and estimating a backup time required to complete the data backup, and then summing up the charging time and the backup time to get a required time interval;
S6: the App calculating an available time interval which is equal to a time difference between a current time provided by the mobile device and a usage starting time set by the charging preferences;
S7: the App determining whether the required time interval is less than the available time interval, if the required time interval is greater than or equal to the available time interval, jumping to step S9, and if the required time interval is less than the available time interval, jumping to step S8;
S8: the App backing up files to be backed up for the mobile device for a unit backup time;
S8-1: the App determining whether the file backup is done, and if the file backup is not yet done, the flow jumping to step S8-3;
S8-2: the App determining whether to set the files been backed up as read-only according to the backup preferences; and the App determining whether to set the files been backed up with password protection according to the backup preferences; the flow jumping to step S9;
S8-3: the App determining whether the present charge level is lower than the minimum charge level, and if the present charge level of the battery is higher than or equal to the minimum charge level, the flow jumping to S8-5;
S8-4: the App determining whether power-off mode is ongoing, and if power-off mode is ongoing, the App entering the power-on mode routine;
waiting for one unit charging time, and then looping back to step S8-3;
S8-5: the App starting to execute a power ON/OFF mode setting routine, and then jumping to step S8;
S9: the App starting to execute the power ON/OFF mode setting routine, and then jumping to step S10; and
S10: the App waiting for one unit charging time, and then looping back to step S9.
2. The method as claimed in claim 1, wherein the power ON/OFF mode setting routine includes the following steps:
SR1: the App determining whether an off-peak charging option is FALSE or the current time is within an off-peak time interval, and if the off-peak charging option is FALSE or the current time is within the off-peak time interval, jumping to step SR3;
SR2: the App stopping the data backup unit from charging the mobile device, and next exiting the power ON/OFF mode setting routine;
SR3: the App determining whether the present charge level is less than or equal to the maximum charge level, and if the present charge level is larger than the maximum charge level, jumping to step SR2;
SR4: the App entering the power-on mode routine, and next exiting the power ON/OFF mode setting routine.
3. The method as claimed in claim 1, wherein the power-on mode routine includes the following actions:
the App determining whether a rapid charging option set by the charging preferences is TRUE, and if the rapid charging option is TRUE, charging the battery under a rapid charging mode, otherwise if the rapid charging option is FALSE, charging the battery under a normal charging mode.
4. The method as claimed in claim 2, wherein the power-on mode routine includes the following actions:
the App determining whether a rapid charging option set by the charging preferences is TRUE, if the rapid charging option is TRUE, charging the battery under a rapid charging mode, otherwise if the rapid charging option is FALSE, charging the battery under a normal charging mode.
5. The method as claimed in claim 1, wherein the following steps are further included before step S3:
S1: the App determining whether the mobile device has ever connected with the data backup unit; if the mobile device has ever connected with the data backup unit, the flow jumping to S2;
S1_1: the App creating a user profile block in the memory unit of the data backup unit, and setting up the backup preferences and the charging preferences in the user profile block;
S2: the App determining whether the mobile device has ever backed up files in the charging unit; if the mobile device has ever backed up files in the charging unit, the flow jumping to S3; and
S2_1: the App creating a new backup folder in the memory unit.
6. The method as claimed in claim 1, wherein the charging preferences include a maximum charge level data, a minimum charge level data, a mobile device usage starting time data, an off-peak time interval data, the off-peak charging option, and a rapid charging option.
7. The method as claimed in claim 5, wherein, when the App creates a user profile block in the memory unit of the data backup unit, the App also writes an identification code of the mobile device into the user profile block.
8. The method as claimed in claim 5, wherein when the App creates a backup folder, the App also creates a backup folder pointer in the user profile block to point to the backup folder.
9. The method as claimed in claim 5, wherein the following steps are further included before step S1:
S0_0: the mobile device connected to the data backup unit and the connection being authenticated;
S0_1: the mobile device deciding whether the App has been installed, if the App is installed on the mobile device, then the mobile device executes step S1;
S0_2: the mobile device reminding the user of the mobile device to install the App.
US17/474,608 2021-09-14 2021-09-14 Method for a data backup unit to intelligently charge a mobile device Active 2042-07-08 US11816002B2 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US17/474,608 US11816002B2 (en) 2021-09-14 2021-09-14 Method for a data backup unit to intelligently charge a mobile device
TW110139372A TWI769946B (en) 2021-09-14 2021-10-22 Method for a data backup unit to intelligently charge a mobile device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US17/474,608 US11816002B2 (en) 2021-09-14 2021-09-14 Method for a data backup unit to intelligently charge a mobile device

Publications (2)

Publication Number Publication Date
US20230077858A1 US20230077858A1 (en) 2023-03-16
US11816002B2 true US11816002B2 (en) 2023-11-14

Family

ID=83439700

Family Applications (1)

Application Number Title Priority Date Filing Date
US17/474,608 Active 2042-07-08 US11816002B2 (en) 2021-09-14 2021-09-14 Method for a data backup unit to intelligently charge a mobile device

Country Status (2)

Country Link
US (1) US11816002B2 (en)
TW (1) TWI769946B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230185768A1 (en) * 2021-12-11 2023-06-15 Dropbox, Inc. Classifying and organizing digital content items automatically utilizing content item classification models

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TW201404002A (en) 2012-07-13 2014-01-16 Askey Computer Corp Mobile power supply with backup function and backup method thereof
US20140100671A1 (en) * 2012-10-09 2014-04-10 General Electric Company End-user based backup management
TWM486890U (en) 2014-04-03 2014-09-21 Giga Byte Tech Co Ltd Charging apparatus of integrated network
US9800291B1 (en) * 2016-04-21 2017-10-24 Lior Ben David Data backup and charging device for communication devices
TW202028999A (en) 2019-01-30 2020-08-01 智微科技股份有限公司 Transmission interface circuit

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TW201404002A (en) 2012-07-13 2014-01-16 Askey Computer Corp Mobile power supply with backup function and backup method thereof
US20140100671A1 (en) * 2012-10-09 2014-04-10 General Electric Company End-user based backup management
TWM486890U (en) 2014-04-03 2014-09-21 Giga Byte Tech Co Ltd Charging apparatus of integrated network
US20150288215A1 (en) * 2014-04-03 2015-10-08 Giga-Byte Technology Co., Ltd. Charger device with network connectivity
US9800291B1 (en) * 2016-04-21 2017-10-24 Lior Ben David Data backup and charging device for communication devices
TW202028999A (en) 2019-01-30 2020-08-01 智微科技股份有限公司 Transmission interface circuit
TWI736834B (en) 2019-01-30 2021-08-21 智微科技股份有限公司 Transmission interface circuit

Also Published As

Publication number Publication date
TWI769946B (en) 2022-07-01
TW202312623A (en) 2023-03-16
US20230077858A1 (en) 2023-03-16

Similar Documents

Publication Publication Date Title
US8793518B2 (en) Systems and methods for providing supplemental power to battery powered information handling systems
CN111463842B (en) Electronic equipment and communication method thereof
CA2374342C (en) System and method for powering and charging a mobile communication device
US11909243B2 (en) Information handling systems and improved battery charge control methods
US20160099608A1 (en) Power adapter with built-in battery and power storage and supply method thereof
US10671149B2 (en) System and methods for remotely applying battery management policies based on local user behavior
US8671291B2 (en) Method and device for charging energy storage devices
CN106655344B (en) Charging method and device for mobile terminal
CN111433999A (en) Electronic device including battery and method of controlling charging thereof
US9667072B2 (en) Mobile power device with memory storage feature which switches between master and slave roles
CN116914894B (en) Cut-off voltage adjusting method, electronic device and readable storage medium
US11816002B2 (en) Method for a data backup unit to intelligently charge a mobile device
US9252618B2 (en) Terminals, terminal systems and charging/discharging methods thereof
US20100180132A1 (en) Power Management Device for a Computer System and Related Power Management Method and Computer System
US10996726B1 (en) Runtime update of battery coefficients
CN106899067A (en) intelligent battery management method and system
CN106303096B (en) Electronic equipment and method for adjusting power management strategy thereof
WO2021227991A1 (en) Charging method and apparatus
US12184113B2 (en) Charge method for battery, storage medium, and terminal
CN113872303B (en) Charging control method, device, electronic device and storage medium
CN107037866B (en) Terminal reset circuit and terminal
US11921164B2 (en) Intelligent battery power discharge management
US20220405175A1 (en) Method for a charging unit that backs up data stored on a mobile device
US11755423B2 (en) Mobile device for protecting data stored in data backup device and data protection method thereof
US20200117468A1 (en) Shutdown sequence of thin clients

Legal Events

Date Code Title Description
FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY

AS Assignment

Owner name: VINPOWER INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CHANG, CALVINSON;CHU, STANLEY;CHOU, CHIHHAN;REEL/FRAME:057562/0852

Effective date: 20210611

FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO SMALL (ORIGINAL EVENT CODE: SMAL); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STPP Information on status: patent application and granting procedure in general

Free format text: AWAITING TC RESP., ISSUE FEE NOT PAID

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED

STCF Information on status: patent grant

Free format text: PATENTED CASE