An intelligent charging management method, terminal device, and storage medium

Abstract

This application belongs to the field of communication technologies, and particularly relates to an intelligent charging management method, a terminal device, and a storage medium. The method can schedule the entire process of each task even when there is no power outage. Then, when a power outage occurs, it can determine the intervals for each task end to execute subtasks after the power outage based on the previous schedule, and adjust the execution schedule of each task end after the power outage according to these intervals, reducing the intervals of the subtasks. As a result, the task end can complete multiple subtasks during a single activation process, thereby reducing the activation times of the task end, significantly reducing the large amount of power consumption caused by repeated activations, saving the electrical energy of the power source, and enabling the power source with limited electrical energy to supply power to each task end for a longer time.

Description

Technical Field

[0001] This application belongs to the field of communication technologies, and particularly relates to an intelligent charging management method, a terminal device, and a storage medium. Background Art

[0002] With the development of information technology, data information is generated all the time. Processing and analyzing this data information often requires multiple task ends (such as servers) to cooperate with each other to complete;

[0003] For a task, it is often divided into several subtasks (each subtask often has a timing relationship, for example, the execution of one subtask requires the result of another subtask), and is assigned to each task end, that is, each task end only needs to complete the assigned subtask; in a period of time, multiple tasks may need to be completed, that is, each task end needs to complete the corresponding subtasks multiple times, and due to the fact that the time points for receiving tasks are often different, there are also time deviations in the execution of each subtask by the task end (not always executed continuously). When there is no power outage, each task end is powered by the mains electricity and has sufficient power, and often always operates in a standard state (even in the period when no task is being executed); while in the event of a power outage, each task end is powered by a backup power supply. Since the power of the power supply is limited, the prior art often charges each task end according to the timing relationship of the corresponding subtasks completed by each task end, that is, when the task end is not executing a task, the task end enters a sleep state, and when a task needs to be executed, power is supplied to the task end to activate the task end, so as to complete the corresponding subtask; however, since each task end may need to intermittently execute subtasks multiple times, according to this charging method, each task end needs to be converted between sleep and activation multiple times, and this kind of conversion often consumes a lot of power, resulting in waste of power, being unfavorable for saving the power of the power supply, and it is difficult to ensure the working duration of each task end during a power outage. Summary of the Invention

[0004] In view of this, the embodiments of this application provide an intelligent charging management method, a terminal device, and a storage medium, which can solve the above technical problems.

[0005] The first aspect of the embodiments of this application provides an intelligent charging management method, and the intelligent charging management method includes:

[0006] S1: Identify a plurality of task ends connected to the power supply, and obtain the timing diagram of each task end executing tasks, where the timing diagram includes each subtask of the task, the task end corresponding to each subtask, and the execution sequence of each subtask;

[0007] S2: Monitor whether a task instruction input by the user is received. The task instruction is an instruction for instructing each task end to cooperate in executing a task once, and the task instruction further includes the task volume of this task.

[0008] S3: Each time a task instruction is received, generate a task timeline for this task, and generate a progress bar for each subtask on the task timeline according to the task volume of this task. The task timeline is used to represent the execution time arrangement of each subtask of this task, and the time interval corresponding to each progress bar on the task timeline is the time interval during which the corresponding subtask is executed.

[0009] S4: Forward the task timeline to each task end, so that each task end cooperates in executing the task instructed by the task instruction.

[0010] S5: When a power outage occurs, determine the remaining timelines of each task timeline, and then obtain the distribution of the progress bars on each remaining timeline.

[0011] S6: Determine the execution arrangement of the subtasks of each task end according to the distribution of the progress bars on each remaining timeline. Without disturbing the sequence of the progress bars on each remaining timeline, adjust the execution arrangement of the subtasks of each task end so that each task end can complete multiple subtasks in one activation process, thereby reducing the activation times of this task end.

[0012] S7: For each task end, determine the corresponding activation time point according to the adjusted execution arrangement of the subtasks of this task end, and control the power supply to charge this task end before the activation time point, and send the adjusted subtask arrangement to this task end, so that this task end can be activated at the corresponding activation time point and complete the adjusted execution arrangement of the subtasks.

[0013] In the second aspect of the embodiments of the present application, a terminal device is provided, including a memory and a processor. A computer program is stored in the memory. When the computer program is executed by the processor, the processor is caused to execute the steps of the intelligent charging management method.

[0014] In the third aspect of the embodiments of the present application, a storage medium is provided. A computer program is stored on the storage medium. When the computer program is executed by a processor, the processor is caused to execute the steps of the intelligent charging management method.

[0015] The beneficial effects of the embodiments of the present application compared with the prior art are as follows: The method provided by the present invention includes identifying a plurality of task terminals connected to a power source and obtaining the timing diagrams of the tasks executed by each task terminal; monitoring whether a task instruction input by a user is received; for each received task instruction, generating a task timeline for the current task, and generating a progress bar for each subtask on the task timeline according to the task volume of the current task; forwarding the task timeline to each task terminal so that each task terminal collaboratively executes the task indicated by the task instruction; when a power outage occurs, determining the remaining timelines of each task timeline, and then obtaining the distribution of the progress bars on each remaining timeline; determining the execution arrangement of the subtasks of each task terminal according to the distribution of the progress bars on each remaining timeline, and adjusting the execution arrangement of the subtasks of each task terminal without disturbing the sequence of the progress bars on each remaining timeline; for each task terminal, determining the corresponding activation time point according to the adjusted execution arrangement of the subtasks of the task terminal, controlling the power source to charge the task terminal before the activation time point, and sending the adjusted subtask arrangement to the task terminal so that the task terminal can be activated at the corresponding activation time point and complete the adjusted execution arrangement of the subtasks; it is possible to arrange the time for the whole process of each task before a power outage, and then determine the interval of the execution of the subtasks by each task terminal after the power outage according to the previous time arrangement, and adjust the execution time arrangement of each task terminal after the power outage according to this interval, so as to reduce the interval of the subtasks, and further enable the task terminal to complete multiple subtasks in one activation process, thereby reducing the activation times of the task terminal, significantly reducing the large amount of power consumption caused by repeated activation, saving the power of the power source, and enabling the power source with limited power to supply power to each task terminal for a longer time. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the following drawings are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0017] Figure 1 It is a schematic flowchart of the implementation of the intelligent charging management method provided by the embodiments of the present application;

[0018] Figure 2 It is a schematic diagram of the implementation environment of the intelligent charging management method provided by the embodiments of the present application;

[0019] Figure 3 It is a schematic diagram of the task timeline of the intelligent charging management method provided by the embodiments of the present application;

[0020] Figure 4It is a schematic diagram of the remaining time axis of the intelligent charging management method provided by an embodiment of the present application;

[0021] Figure 5 It is a schematic diagram of the first time axis of the intelligent charging management method provided by an embodiment of the present application;

[0022] Figure 6 It is a schematic diagram of the terminal device provided by an embodiment of the present application. Detailed implementation manners

[0023] In the following description, specific details such as specific system structures and technologies are presented for the purpose of illustration rather than limitation, so as to thoroughly understand the embodiments of the present application. However, those skilled in the art should clearly understand that the present application can also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid unnecessary details from interfering with the description of the present application.

[0024] In order to illustrate the technical solutions described in the present application, the following will be described through specific embodiments.

[0025] Figure 1 An intelligent charging management method provided by Embodiment 1 of the present application is shown. The intelligent charging management method includes:

[0026] S1: Identify a plurality of task terminals connected to the power supply, and obtain the timing diagrams of each task terminal executing tasks. Among them, the timing diagram includes each subtask of the task, the task terminal corresponding to each subtask, and the execution sequence of each subtask;

[0027] S2: Monitor whether a task instruction input by the user is received. Among them, the task instruction is an instruction for instructing each task terminal to cooperate to execute a task once, and the task instruction also includes the task amount of this task;

[0028] S3: Every time a task instruction is received, generate a task time axis for this task, and generate a progress bar for each subtask on the task time axis according to the task amount of this task. Among them, the distribution of the progress bars on the task time axis represents the execution time arrangement of each subtask of this task, and the time interval corresponding to each progress bar on the task time axis is the time interval during which the corresponding subtask is executed;

[0029] S4: Forward the task time axis to each task terminal, so that each task terminal cooperates to execute the task according to the task time axis;

[0030] S5: When a power outage occurs, determine the remaining time axes of each task time axis, and then obtain the distribution of the progress bars on each remaining time axis;

[0031] S6: Determine the execution arrangement of the subtasks of each task end according to the distribution of the progress bars on each remaining time axis. Without disrupting the sequence of the progress bars on each remaining time axis, adjust the execution arrangement of the subtasks of each task end so that each task end can complete multiple subtasks during one activation process, thereby reducing the activation times of that task end;

[0032] S7: For each task end, determine the corresponding activation time point according to the adjusted execution arrangement of the subtasks of that task end, and control the power supply to charge that task end before that activation time point, and send the adjusted subtask arrangement to that task end, so that that task end can be activated at the corresponding activation time point and complete the adjusted execution arrangement of the subtasks.

[0033] In this embodiment, as Figure 2 shown, this method is executed in a terminal device. The terminal device can be an independent physical server or terminal, or a server cluster composed of multiple physical servers, and can be a cloud server providing basic cloud computing services such as cloud servers, cloud databases, cloud storage, and CDN; the terminal device communicates with each task end that performs data processing tasks. When the terminal device receives a task instruction (input directly on the terminal device by the user or sent by the user to the terminal device through the user side), it can control each task end to execute the corresponding task; each task end is connected to the power supply. When there is a power outage, the power supply provides electrical energy for the terminal device to maintain continuous control of each end. The terminal device can control the power supply to charge the task end so that the task end can still complete the corresponding task during a power outage;

[0034] In this embodiment, the task indicated by each received task instruction in this method is the same type of task, only the task volume is different. Each task end in this method is the task end configured according to the subtasks of that task, and each task end is used to execute a subtask of that task;

[0035] In this embodiment, every time the terminal device receives a task instruction, as Figure 3 shown, it can generate a task time axis reflecting the overall execution time arrangement of the task. After sending the task time axis to each task end, the task end can identify the progress bar of the corresponding subtask on the task time axis, and determine the time period for it to execute that subtask according to the time interval corresponding to the progress bar on the time axis, and then execute that subtask during that time period; the progress bar is parallel to the time axis, and the progress bar can represent the completion situation of a subtask. For example, the farther the current time point is from the starting edge of the progress bar, the closer it is to the ending edge of the progress bar, and the higher the proportion of the corresponding subtask that is completed;

[0036] In this embodiment, when a power outage occurs, for the tasks that have not been completed (completed tasks are not considered), some of the sub-tasks corresponding to the progress bars on the task timeline have been completed, and these sub-tasks are not considered. Only the progress bars corresponding to the uncompleted sub-tasks are considered, that is, the progress bar distribution on the remaining timeline; for the progress bars on each remaining timeline, the progress bars belonging to the same task end are summarized, so as to obtain the execution arrangement of each sub-task executed by each task end each time, and then determine the time interval between the executions of each sub-task (the task end needs to sleep and then be activated at the time interval). Subsequently, the execution arrangement is adjusted accordingly to eliminate this time interval, thereby reducing the number of times the task end sleeps and is reactivated, so as to save the power of the power supply; furthermore, during the process of adjusting the execution arrangement of the sub-tasks, the order of the progress bars on each remaining timeline is kept unchanged, that is, the timing relationship of each sub-task is not disrupted, and thus the smooth progress of the task can be ensured; the adjusted execution arrangement of the sub-tasks can be sent to each task end, and the terminal device can isolate the power supply for charging each task end according to the execution arrangement of the sub-tasks, so that each task end is activated at the corresponding time point and completes the execution arrangement of the sub-tasks.

[0037] In this application, the whole process time arrangement of each task can be carried out when there is no power outage. Then, when a power outage occurs, the interval situation of each task end executing sub-tasks after the power outage can be determined according to the previous time arrangement, and the execution time arrangement of each task end after the power outage is adjusted according to this interval situation, so as to reduce the interval of the sub-tasks. Thus, the task end can complete multiple sub-tasks in one activation process, thereby reducing the activation times of the task end, significantly reducing the large amount of power loss caused by repeated activation, saving the power of the power supply, and enabling the power supply with limited power to supply power to each task end for a longer time.

[0038] As a preferred embodiment, generating the task timeline of this task and generating the progress bar of each sub-task on the task timeline according to the task volume of this task includes:

[0039] Determine the execution duration of this task according to the task volume of this task and the task volume - execution duration comparison table, where the task volume - execution duration comparison table includes the execution durations corresponding to several task volumes;

[0040] Obtain the execution duration ratio of each sub-task, and multiply the execution duration ratio by the determined execution duration to obtain the sub-execution duration corresponding to this sub-task;

[0041] Determine the starting time point for executing this task as the time point after a set duration from the current time point;

[0042] Generate a task timeline, determine the start time point on the task timeline, generate a start edge based on the position of the start time point, and generate a progress bar corresponding to the first subtask from the start edge, where the duration of the time interval corresponding to the progress bar on the task timeline is equal to the sub-execution duration corresponding to the subtask;

[0043] Use the end edge of the previous progress bar as the start edge, and generate a progress bar corresponding to the next subtask from this start edge, and repeat this step until progress bars corresponding to each subtask are generated.

[0044] In this embodiment, the set duration can be 1 second, 2 seconds, or other durations. By setting the set duration, sufficient time can be provided for generating and sending the task timeline to the terminal device; the task volume - execution duration comparison table is a comparison table preset according to historical data. The historical data includes the duration of each task execution in history. Since the task volume of each task is inconsistent, the execution duration of tasks in all task volume cases can be obtained; the historical data also includes the ratio of the sub-execution duration of each subtask to the execution duration when each task is executed. Therefore, for each subtask, the corresponding execution duration ratio of the subtask can be obtained by calculating the average value of the ratio of the sub-execution duration of the subtask to the execution duration when each task is executed in history; the length of the progress bar represents the sub-execution duration of the corresponding subtask. Therefore, the execution progress of the subtask can be determined according to the ratio of the length of the time axis corresponding to the duration of the executed subtask to the length of the progress bar.

[0045] In this embodiment, when a task end completes a subtask, it can trigger the next task end to start corresponding to the subtask, that is, the task processes of each task end can be regarded as continuous. Therefore, the progress bars on each task timeline are progress bars connected end to end;

[0046] As a preferred embodiment, as Figure 4 shown, determine the remaining timeline of each task timeline, and further obtain the distribution of the progress bars on each remaining timeline, including:

[0047] Determine the power outage time point;

[0048] For each task timeline, identify the power outage time point on the task timeline;

[0049] Draw a cut-off line perpendicular to the task timeline through the power outage time point, and determine the remaining timeline of the task timeline after the cut-off line;

[0050] Identify the progress bars cut off by the cut-off line, and use the progress bars after the cut-off progress bars as the progress bars distributed on the remaining timeline.

[0051] The truncated progress bar is the progress bar corresponding to the subtask being executed by the corresponding task end. Between step S5 and step S6, it further includes:

[0052] Controlling the task ends of the unexecuted tasks to enter the sleep state;

[0053] Identifying each truncated progress bar, and then determining all the task ends of the subtasks corresponding to the executed truncated progress bars;

[0054] Controlling the power supply to supply power to the determined task ends until the determined task ends complete the subtasks corresponding to the executed truncated progress bars, and then controlling the determined task ends to enter the sleep state.

[0055] In this embodiment, the time axis after the truncation line is the time axis on the positive side of the truncation line time axis; when a power outage occurs, some task ends are performing subtasks. At this time, the power supply is controlled to continuously supply the required power to these task ends to ensure that they complete the subtasks being executed; for the task ends that have no tasks to execute, they can be controlled to enter the sleep state to avoid unnecessary energy waste.

[0056] As a preferred embodiment, determining the execution arrangements of the subtasks of each task end according to the distribution of the progress bars on each remaining time axis, and adjusting the execution arrangements of the subtasks of each task end without disturbing the order of the progress bars on each remaining time axis includes:

[0057] S61: Numbering each subtask in the sequence diagram according to the execution sequence of each subtask. Among them, the earlier the execution sequence of the subtask, the smaller the corresponding number;

[0058] S62: Marking the number of the corresponding subtask on each progress bar on each remaining time axis;

[0059] S63: Identifying the smallest number among all the numbers of the progress bars as the target number;

[0060] S64: Generating the first time axis corresponding to the target number;

[0061] S65: Copying each progress bar marked with the target number to obtain the corresponding backup progress bar, and moving the backup progress bar to the first time axis. Among them, the distribution of the backup progress bars on the first time axis represents the execution arrangements of the subtasks of the task end corresponding to the target number;

[0062] S66: Determine whether there are intervals between the backup progress bars on the first time axis. If so, move the earlier backup progress bar towards the later one to make the intervals between the backup progress bars disappear. While adjusting the backup progress bars on the first time axis, correspondingly adjust the progress bars on each remaining time axis to maintain the order of the progress bars on the remaining time axes.

[0063] S67: Determine the next number as the target number, and execute steps S64 to S67 until the adjustment of the progress bar corresponding to the largest number is completed.

[0064] In this embodiment, the time interval corresponding to the initial position of each backup progress bar on the first time axis is the same as the time interval corresponding to the corresponding initial progress bar on the remaining time axes. As Figure 5 shown, when there are no intervals between the backup progress bars on the first time axis, the backup progress bars may not be adjusted, or the earlier backup progress bar may be moved towards the later one to make the backup progress bars more compact, thereby reducing the total power consumption.

[0065] As a preferred embodiment, moving the earlier backup progress bar towards the later one to make the intervals between the backup progress bars disappear includes:

[0066] S661: Move the first backup progress bar on the first time axis towards the second one to make the starting edge of the first backup progress bar coincide with that of the second one.

[0067] S662: Move the backup progress bars whose starting edges have coincided simultaneously so that the starting edge of the next backup progress bar also coincides with that of the moved backup progress bar. Repeat this step until the starting edges of all the backup progress bars on the first time axis coincide.

[0068] S663: Identify the longest backup progress bar.

[0069] S664: Select at least one backup progress bar from the remaining backup progress bars so that the sum of the lengths of the selected backup progress bars just does not exceed the length of the longest backup progress bar.

[0070] S665: Connect the selected backup progress bars end to end in sequence to form a combined progress bar, and make the starting edge of the combined progress bar coincide with that of the longest backup progress bar to keep the combined progress bar within the range of the longest backup progress bar.

[0071] S666: Repeat steps S664 to S666 until the combination and position adjustment of all the backup progress bars outside the longest backup progress bar are completed.

[0072] In this embodiment, the head and tail are connected in sequence, that is, they are connected in sequence according to the chronological order corresponding to the time when the backup progress bar is at the initial position; since the starting edges of each backup progress bar coincide, when the combined progress bar is completed, its starting edge automatically coincides with the starting edge of the longest alternative progress bar; the task end has marginal benefit when executing tasks, that is, the more tasks the task end executes simultaneously, the less energy consumption is allocated to individual tasks; when the task end only executes one subtask in a period, its energy consumption cost performance is the lowest; through this embodiment, the total duration of the task executed after the task end is activated once can be controlled to the shortest, that is, the duration corresponding to the length of the longest backup progress bar, and the positions of each backup progress bar can be reasonably arranged (that is, the longest backup progress bar is overlapped with other combined progress bars of similar length, so that the task end executes multiple subtasks simultaneously; furthermore, the last layer of combined progress bar can be only one backup progress bar), so that the time period for the task end to execute a single subtask alone is minimized, and the electric energy of the power supply can be further saved.

[0073] As a preferred embodiment, while adjusting the backup progress bar on the first time axis, the corresponding adjustment of the progress bars on each remaining time axis includes:

[0074] While adjusting each backup progress bar on the first time axis, determine the corresponding initial progress bar of the backup progress bar, and move the initial progress bar and the progress bars after the initial progress bar on the corresponding remaining time axes, where the backup progress bar is copied from the corresponding initial progress bar, and the moving distances of the initial progress bar and the progress bars after the initial progress bar are the same as the moving distance of the corresponding backup progress bar.

[0075] In this embodiment, while adjusting the backup progress bar on the first time axis, the corresponding adjustment of the progress bars on each remaining time axis can ensure that the position of the progress bar with a larger number is always behind the progress bar with a smaller serial number, thereby maintaining the execution order of each subtask of each task to ensure the smooth progress of the task.

[0076] As a preferred embodiment, determining the corresponding activation time point according to the adjusted subtask execution arrangement of the task end includes:

[0077] Identify the time point corresponding to the starting edge of the longest backup progress bar on the first time axis corresponding to the task end, and determine this time point as the activation time point.

[0078] In this embodiment, after determining the activation time point, the power supply can be controlled to start charging the task end before the activation time point, so that the task end has enough power to be activated and execute the corresponding subtasks according to the time intervals in which each backup progress bar is distributed on the first time axis.

[0079] An end device provided in the second embodiment of the present application includes a memory and a processor. A computer program is stored in the memory. When the computer program is executed by the processor, the processor executes the steps of the intelligent charging management method, which specifically includes:

[0080] S1: Identify a plurality of task terminals connected to the power supply, and obtain the timing diagrams of each task terminal executing tasks. Among them, the timing diagram includes each subtask of the task, the task terminal corresponding to each subtask, and the execution sequence of each subtask;

[0081] S2: Monitor whether a task instruction input by the user is received. Among them, the task instruction is an instruction for instructing each task terminal to cooperate to execute a task once, and the task instruction also includes the task amount of this task;

[0082] S3: Every time a task instruction is received, generate a task time axis for this task, and generate a progress bar for each subtask on the task time axis according to the task amount of this task. Among them, the task time axis is used to represent the execution time arrangement of each subtask of this task, and the time interval corresponding to each progress bar on the task time axis is the time interval during which the corresponding subtask is executed;

[0083] S4: Forward the task time axis to each task terminal, so that each task terminal cooperates to execute the task instructed by the task instruction;

[0084] S5: When a power outage occurs, determine the remaining time axes of each task time axis, and then obtain the distribution of the progress bars on each remaining time axis;

[0085] S6: Determine the subtask execution arrangements of each task terminal according to the distribution of the progress bars on each remaining time axis. Without disrupting the sequence of the progress bars on each remaining time axis, adjust the subtask execution arrangements of each task terminal so that each task terminal can complete multiple subtasks in one activation process, thereby reducing the activation times of this task terminal;

[0086] S7: For each task terminal, determine the corresponding activation time point according to the adjusted subtask execution arrangement of this task terminal, and control the power supply to charge this task terminal before the activation time point, and send the adjusted subtask arrangement to this task terminal, so that this task terminal can be activated at the corresponding activation time point and complete the adjusted subtask execution arrangement.

[0087] A storage medium provided in the third embodiment of the present application. A computer program is stored on the storage medium. When the computer program is executed by a processor, the processor executes the steps of the intelligent charging management method, which specifically includes:

[0088] S1: Identify several task terminals connected to the power supply, and obtain the timing diagrams of each task terminal executing tasks. Among them, the timing diagram includes each subtask of the task, the task terminal corresponding to each subtask, and the execution sequence of each subtask.

[0089] S2: Monitor whether a task instruction input by the user is received. Among them, the task instruction is an instruction for instructing each task terminal to cooperate to execute a task once, and the task instruction also includes the task volume of this task.

[0090] S3: Every time a task instruction is received, generate a task timeline for this task, and generate a progress bar for each subtask on the task timeline according to the task volume of this task. Among them, the task timeline is used to represent the execution time arrangement of each subtask of this task, and the time interval corresponding to each progress bar on the task timeline is the time interval during which the corresponding subtask is executed.

[0091] S4: Forward the task timeline to each task terminal, so that each task terminal cooperates to execute the task instructed by the task instruction.

[0092] S5: When a power outage occurs, determine the remaining timelines of each task timeline, and then obtain the distribution of the progress bars on each remaining timeline.

[0093] S6: Determine the execution arrangement of the subtasks of each task terminal according to the distribution of the progress bars on each remaining timeline. Without disrupting the sequence of the progress bars on each remaining timeline, adjust the execution arrangement of the subtasks of each task terminal so that each task terminal can complete multiple subtasks in one activation process, thereby reducing the activation times of this task terminal.

[0094] S7: For each task terminal, determine the corresponding activation time point according to the adjusted execution arrangement of the subtasks of this task terminal, and control the power supply to charge this task terminal before this activation time point, and send the adjusted subtask arrangement to this task terminal.

[0095] It should be understood that the magnitudes of the sequence numbers of the steps in the above embodiments do not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0096] It should be understood that when used in the specification of the present application, the term "comprising" indicates the existence of the described features, wholes, steps, operations, elements and / or components, but does not exclude the existence or addition of one or more other features, wholes, steps, operations, elements, components and / or their combinations.

[0097] It should also be understood that the term " / and" used in the specification of the present application refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0098] As used in the specification of this application, the term "if" may be construed, depending on the context, as "when", "once", "in response to determining", or "in response to detecting". Similarly, the phrase "if determined" or "if [the described condition or event] is detected" may be construed, depending on the context, to mean "once determined", "in response to determining", "once [the described condition or event] is detected", or "in response to detecting [the described condition or event]".

[0099] In addition, in the description of the specification of this application, the terms "first", "second", "third", etc. are only used for differentiating descriptions and cannot be construed as indicating or implying relative importance. It should also be understood that although the terms "first", "second", etc. are used in the text in some embodiments of this application to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, the first table may be named the second table, and similarly, the second table may be named the first table, without departing from the scope of the various described embodiments. The first table and the second table are both tables, but they are not the same table.

[0100] The reference to "one embodiment" or "some embodiments" etc. described in the specification of this application means that a specific feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of this application. Thus, the statements "in one embodiment", "in some embodiments", "in other some embodiments", "in still other embodiments", etc. that appear in different places in this specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "comprising", "including", "having", and their variants all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0101] The intelligent charging management method provided by the embodiments of this application can be applied to terminal devices such as mobile phones, tablet computers, wearable devices, in-vehicle devices, augmented reality (AR) / virtual reality (VR) devices, laptop computers, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), etc. The embodiments of this application do not impose any restrictions on the specific types of terminal devices.

[0102] For example, the terminal device may be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device, or other processing devices connected to a wireless modem, a vehicle-mounted device, a vehicle-to-everything (V2X) terminal, a computer, a laptop computer, a handheld communication device, a handheld computing device, a satellite wireless device, a wireless modem card, a television set-top box (STB), a customer premise equipment (CPE), and / or other devices for communicating on a wireless system, as well as next-generation communication systems, such as mobile terminals in a 5G network or mobile terminals in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0103] By way of example and not limitation, when the terminal device is a wearable device, the wearable device may also be a general term for devices that apply wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. A wearable device is not just a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable intelligent devices include those with full functions and large sizes that can achieve complete or partial functions without relying on a smartphone, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones, such as various smart bracelets and smart jewelry for monitoring physical signs.

[0104] Figure 6 is a schematic structural diagram of a terminal device provided by an embodiment of the present application. As Figure 6 shown, the terminal device of this embodiment includes: at least one processor ( Figure 6 only one is shown in the figure), and a memory. A computer program that can run on the processor is stored in the memory. When the processor executes the computer program, the steps in the above-mentioned embodiments of each intelligent charging management method are implemented, such as Figure 1 the steps S1 to S7 shown in the figure.

[0105] The terminal device may be a computing device such as a desktop computer, a notebook, a palm computer, and a cloud server. The terminal device may include, but is not limited to, a processor and a memory. Those skilled in the art can understand that Figure 6 merely examples of the terminal device, which do not constitute a limitation on the terminal device, may include more or fewer components than shown in the figure, or combine certain components, or different components. For example, the terminal device may further include an input and sending device, a network access device, a bus, etc.

[0106] The so-called processor may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), off-the-shelf programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0107] The memory may be an internal storage unit of the terminal device in some embodiments, such as the hard disk or memory of the terminal device. The memory may also be an external storage device of the terminal device, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the terminal device. Further, the memory may also include both the internal storage unit and the external storage device of the terminal device. The memory is used to store an operating system, application programs, a boot loader (BootLoader), data, and other programs, such as the program code of the computer program. The memory may also be used to temporarily store data that has been sent or will be sent.

[0108] In addition, in each embodiment of the present application, each functional unit may be integrated in a processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit. The above integrated unit may be implemented in the form of hardware or in the form of a software functional unit.

[0109] The embodiments of the present application provide a computer program product, which when running on a mobile terminal device enables the mobile terminal device to execute and implement the steps in the above-mentioned various method embodiments.

[0110] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, to implement all or part of the processes in the above-described embodiment methods of this application, it can also be completed by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, the steps of the above-described various method embodiments can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in the form of source code, object code, executable file, or some intermediate form, etc. The computer-readable medium can include: any entity or device that can carry the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disc, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, and software distribution medium, etc.

[0111] In the above embodiments, the descriptions of the various embodiments each have their own focuses. For the parts not detailed or recorded in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0112] Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed in this document can be implemented by electronic hardware, or by a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. A professional technician can use different methods for each specific application to implement the described functions, but such implementation should not be considered to exceed the scope of this application.

[0113] The unit described as a separate component may or may not be physically separated, and the component shown as a unit may or may not be a physical unit, that is, it can be located in one place, or can be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0114] The above-described embodiments are only used to illustrate the technical solutions of this application, rather than to limit it; although this application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements for some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the various embodiments of this application, and should all be included in the protection scope of this application.

Claims

1. An intelligent charging management method, characterized in that: The intelligent charging management method comprises: S1: Identify several task terminals connected to the power supply, and obtain a timing diagram of each task terminal executing the task, wherein the timing diagram includes each subtask of the task, the task terminal corresponding to each subtask, and the execution order of each subtask; S2: monitoring whether a task instruction input by a user is received, wherein the task instruction is an instruction to instruct each task end to collaboratively perform a task, and the task instruction also includes the task amount of this task; S3: Every time a task instruction is received, a task timeline of this task is generated, and a progress bar of each subtask is generated on the task timeline according to the task amount of this task, wherein the distribution of the progress bars on the task timeline represents the execution time arrangement of each subtask of this task, and the time interval corresponding to each progress bar on the task timeline is the time interval in which the corresponding subtask is executed; S4: forwarding the task timeline to each task end, so that each task end can collaboratively execute the task according to the task timeline; S5: when a power outage occurs, determining the remaining time axis of each task time axis, and then obtaining the distribution of the progress bar on each remaining time axis; S6: Determine the subtask execution schedule of each task end according to the distribution of the progress bars on each remaining time axis, and adjust the subtask execution schedule of each task end without disrupting the sequence of the progress bars on each remaining time axis; for the progress bars on each remaining time axis, summarize the progress bars belonging to the same task end to obtain the execution time schedule of the subtasks executed by each task end, determine the time interval of each subtask, and adjust the obtained execution time schedule to eliminate the time interval of each subtask; S7: For each task end, determine the corresponding activation time point according to the adjusted subtask execution schedule of the task end, and control the power supply to charge the task end before the activation time point, and send the adjusted subtask schedule to the task end, so that the task end is activated at the corresponding activation time point and completes the adjusted subtask execution schedule.

2. The method according to claim 1, characterized in that Generate the task timeline for this task. Generate the progress bar of each subtask on the task timeline based on the task amount of this task, including: Determine the execution time of this task based on the task amount of this task and the task amount-execution time comparison table, wherein the task amount-execution time comparison table includes the execution times corresponding to several task amounts; Obtain the execution time ratio of each subtask, and multiply the execution time ratio by the determined execution time to obtain the sub-execution time corresponding to the subtask; Determine the time point after the current time point as the starting time point for executing this task; Generate a task timeline, determine the starting time point on the task timeline, generate a starting edge according to the position of the starting time point, and generate a progress bar corresponding to the first subtask from the starting edge, wherein the duration of the time interval corresponding to the progress bar on the task timeline is equal to the sub-execution duration corresponding to the subtask; The end edge of the previous progress bar is used as the starting edge, and a progress bar corresponding to the next subtask is generated from the starting edge. This step is repeated until a progress bar corresponding to each subtask is generated.

3. The method according to claim 2, characterized in that Determine the remaining time axis of each task time axis, and then obtain the distribution of the progress bar on each remaining time axis, including: Determine the time of power outage; For each task timeline, identify the power outage time point on the task timeline; A truncation line perpendicular to the task time axis is drawn through the power outage time point, and the time axis after the truncation line is determined as the remaining time axis of the task time axis; The progress bar truncated by the truncation line is identified, and the progress bars after the truncated progress bar are used as progress bars distributed on the remaining time axis.

4. The method according to claim 3, characterized in that The truncated progress bar is the progress bar of the corresponding subtask being executed by the corresponding task end; Control the task end that has not executed the task to enter the dormant state; Identify each truncated progress bar, and then determine the task end of all subtasks corresponding to the truncated progress bar; The power supply is controlled to supply power to the determined task end until the determined task end completes the execution of the subtask corresponding to the interrupted progress bar, and then the determined task end is controlled to enter a dormant state.

5. The method according to claim 4, characterized in that Determine the subtask execution arrangement of each task end according to the distribution of the progress bars on each remaining time axis, and adjust the subtask execution arrangement of each task end without disrupting the sequence of the progress bars of each remaining time axis, including: S61: numbering each subtask in the timing diagram according to the execution order of each subtask, wherein the earlier the execution order of the subtask is, the smaller the corresponding number is; S62: marking the number of the corresponding subtask on each progress bar on each remaining time axis; S63: Identify the smallest number among all the progress bar numbers as the target number; S64: Generate a first time axis corresponding to the target number; S65: Copy each progress bar marked with a target number to obtain a corresponding backup progress bar, and move the backup progress bar to the first time axis, wherein the distribution of the backup progress bar on the first time axis represents the subtask execution arrangement of the task end corresponding to the target number; S66: determining whether there is a gap between the backup progress bars on the first time axis, and if so, moving the backup progress bar at the front to the backup progress bar at the back so that there is no gap between the backup progress bars, and while adjusting the backup progress bar on the first time axis, correspondingly adjusting the progress bars on the remaining time axes to maintain the order of the progress bars on the remaining time axes; S67: Determine the next number as the target number, and execute steps S64 to S67 until the adjustment of the progress bar corresponding to the largest number is completed.

6. The method according to claim 5, characterized in that Move the backup progress bar at the front to the backup progress bar at the back so that there is no gap between the backup progress bars. This includes: S661: moving the first backup progress bar on the first timeline toward the second backup progress bar so that the first backup progress bar coincides with the start edge of the second progress bar; S662: Simultaneously move the backup progress bars whose start edges have overlapped, so that the start edge of the next backup progress bar also overlaps with the start edge of the moved backup progress bar, and repeat this step until the start edges of all backup progress bars on the first timeline overlap; S663: Identify the longest backup progress bar; S664: Select at least one backup progress bar from the remaining backup progress bars, so that the sum of the lengths of the selected backup progress bars does not exceed the length of the longest backup progress bar; S665: Connect the selected backup progress bars end to end in order to form a combined progress bar, and make the starting edge of the combined progress bar coincide with the starting edge of the longest backup progress bar, so as to keep the combined progress bar within the range of the longest backup progress bar; S666: Repeat steps S664 to S666 until all backup progress bars except the longest backup progress bar are combined and their positions are adjusted.

7. The method according to claim 6, characterized in that While adjusting the backup progress bar on the first time axis, correspondingly adjusting the progress bars on the remaining time axes includes: While adjusting each backup progress bar on the first timeline, determine the initial progress bar corresponding to the backup progress bar, and move the initial progress bar and the progress bar after the initial progress bar on the corresponding remaining timeline, wherein the backup progress bar is copied from the corresponding initial progress bar, and the moving distance of the initial progress bar and the progress bar after the initial progress bar is consistent with the moving distance of the corresponding backup progress bar.

8. The method according to claim 7, characterized in that The corresponding activation time points are determined based on the adjusted subtask execution schedule of the task end, including: A time point corresponding to a starting edge of the longest backup progress bar on a first time axis corresponding to the task end is identified, and the time point is determined as an activation time point.

9. A terminal device, characterized in that: The invention comprises a memory and a processor, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the steps of the intelligent charging management method according to any one of claims 1 to 8.

10. A storage medium, characterized in that: A computer program is stored on the storage medium, and when the computer program is executed by the processor, the processor executes the steps of the intelligent charging management method according to any one of claims 1 to 8.

Images