Intelligent charging management method, terminal equipment and storage medium

Abstract

The invention belongs to the technical field of communication, and particularly relates to an intelligent charging management method, terminal equipment and a storage medium, and the method can carry out the whole-process time arrangement of each task when the power is not cut off, and then can determine the interval condition of subtasks executed by each task end after the power is cut off according to the previous time arrangement when the power is cut off. The execution time arrangement of each task end after power failure is adjusted according to the interval condition, so that the interval of the sub-tasks is reduced, the task end can complete a plurality of sub-tasks in one activation process, the activation frequency of the task end is reduced, a large amount of electric energy loss caused by repeated activation can be remarkably reduced, and the service life of the task end is prolonged. And the electric energy of the power supply is saved, so that the power supply with limited electric energy can supply power for each task end for a longer time.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and in particular, relates to an intelligent charging management method, terminal equipment and storage medium. Background Art

[0002] With the development of information technology, data information is generated all the time. The processing and analysis of this data information often requires the coordination of multiple task ends (such as servers) to complete; A task is often divided into several subtasks (each subtask often has a time sequence relationship, for example, the execution of a subtask requires the result of another subtask) and assigned to any end, that is, each task end only needs to complete the assigned subtask; in a time period, multiple tasks may need to be completed, that is, each task end needs to complete the corresponding subtasks multiple times, and because the time points of receiving tasks are often different, there is also a time deviation in the execution of each subtask by the task end (not always continuous execution). When there is no power outage, each task end is powered by the mains and has sufficient power, and often always maintains a standard state of operation (even when the task is not executed); in the event of a power outage, Each task end is powered by a backup power supply. Since the power supply has limited power, the prior art often charges each task end according to the timing relationship of each task end completing the corresponding subtask, that is, when the task end is not executing a task, the task end enters a sleep state, and when the task needs to be executed, the task end is powered to activate the task end, thereby completing the corresponding subtask; but since each task end may need to execute subtasks intermittently multiple times, according to this charging method, each task end needs to be converted from sleep to activation multiple times, and this conversion often consumes a lot of power, resulting in a waste of power, which is not conducive to saving power and it is difficult to ensure the working time of each task end during a power outage. Summary of the invention

[0003] In view of this, an embodiment of the present application provides an intelligent charging management method, a terminal device and a storage medium, which can solve the above technical problems.

[0004] A first aspect of an embodiment of the present application provides an intelligent charging management method, the intelligent charging management method comprising: 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 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 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 indicated by the task instruction; 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 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 on each remaining time axis, so that each task end can complete multiple subtasks in one activation process, thereby reducing the number of activation times of the task end; S7: For each task end, determine the corresponding activation time point according to the adjusted subtask execution schedule of the task end, 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.

[0005] A second aspect of an embodiment of the present application provides a terminal device, including 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.

[0006] A third aspect of an embodiment of the present application provides a storage medium, on which a computer program is stored. When the computer program is executed by a processor, the processor executes the steps of the intelligent charging management method.

[0007] Compared with the prior art, the embodiments of the present application have the following beneficial effects: the method provided by the present invention includes identifying a plurality of task terminals connected to a power source, and obtaining a timing diagram of each task terminal executing a task; monitoring whether a task instruction input by a user is received; each time a task instruction is received, a task timeline of the current task is generated, and a progress bar of each subtask is generated on the task timeline according to the task amount of the current task; forwarding the task timeline to each task terminal, so that each task terminal cooperates to execute the task indicated by the task instruction; when a power outage occurs, determining the remaining timeline of each task timeline, and then obtaining the distribution of the progress bars on each remaining timeline; determining the subtask execution arrangement of each task terminal according to the distribution of the progress bars on each remaining timeline, and adjusting the subtask execution arrangement of each task terminal without disrupting the sequence of the progress bars of each remaining timeline; for each task terminal, according to the distribution of the progress bars on each remaining timeline, The adjusted subtask execution schedule of the end determines the corresponding activation time point, and controls the power supply to charge the task end before the activation time point, and sends 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; it is possible to schedule the time of the entire process of each task when there is no power outage, and then when there is a power outage, it is possible to determine the interval of the execution of subtasks by each task end after the power outage according to the previous schedule, and adjust the execution schedule of each task end after the power outage according to this interval, so that the interval of the subtask is reduced, and then the task end can complete multiple subtasks in one activation process, thereby reducing the number of activation times of the task end, and can significantly reduce the large amount of power loss caused by repeated activation, save the power of the power supply, so that the power supply with limited power can provide power supply for each task end for a longer time. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0009] Figure 1 It is a schematic diagram of the implementation process of the intelligent charging management method provided in the embodiment of the present application; Figure 2 It is a schematic diagram of the implementation environment of the intelligent charging management method provided in the embodiment of the present application; Figure 3 It is a schematic diagram of the task timeline of the intelligent charging management method provided in an embodiment of the present application; Figure 4 It is a schematic diagram of the remaining time axis of the intelligent charging management method provided in an embodiment of the present application; Figure 5It is a first timeline schematic diagram of the intelligent charging management method provided in an embodiment of the present application; Figure 6 It is a schematic diagram of a terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0010] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may 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 prevent unnecessary details from obstructing the description of the present application.

[0011] In order to illustrate the technical solution described in this application, a specific embodiment is provided below for illustration.

[0012] Figure 1 An intelligent charging management method provided in Embodiment 1 of the present application is shown, and the intelligent charging management method includes: 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 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 on each remaining time axis, so that each task end can complete multiple subtasks in one activation process, thereby reducing the number of activation times of the task end; S7: For each task end, determine the corresponding activation time point according to the adjusted subtask execution schedule of the task end, 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.

[0013] In this embodiment, if Figure 2 As shown, the method is executed in a terminal device, which may be an independent physical server or terminal, or a server cluster composed of multiple physical servers, or a cloud server that provides 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, and when the terminal device receives a task instruction (the user directly inputs it on the terminal device or the user sends it to the terminal device through the user end), it can control each task end to perform the corresponding task; each task end is connected to a power supply, and when a power outage occurs, the power supply provides power to the terminal device to maintain continuous control of each end, and the terminal device can control the power supply to charge the task end so that the task end can still complete the corresponding task when a power outage occurs; In this embodiment, the tasks indicated by each received task instruction in this method are the same type of tasks, but the task amounts are different. Each task end in this method is a task end configured according to the subtasks of the task, and each task end is used to execute a subtask of the task. In this embodiment, each time the terminal device receives a task instruction, such as Figure 3 As shown, a task timeline that reflects the overall execution time arrangement of the task can be generated. After the task timeline is sent to each task end, the task end can identify the progress bar of the corresponding subtask on the task timeline, and determine the time period for executing the subtask according to the time interval corresponding to the progress bar on the timeline, and then execute the subtask in the time period; the progress bar is parallel to the timeline, and the progress bar can represent the completion status 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 end edge of the progress bar, and the higher the completion ratio of the corresponding subtask is. In this embodiment, when a power outage occurs, for tasks that have not been completed (completed tasks are not considered), the subtasks corresponding to some progress bars on the task time axis have been completed, and these subtasks are not considered. Only the progress bars corresponding to the unfinished subtasks are considered, that is, the distribution of progress bars on the remaining time axis; for the progress bars on each remaining time axis, the progress bars belonging to the same task end are summarized and aggregated, so that the execution schedule of each subtask execution of each task end can be obtained, so as to determine the time interval for each execution of the subtask (the task end needs to sleep and reactivate at the time interval), and then the execution schedule is adjusted accordingly to eliminate the time interval, thereby reducing the number of sleep and reactivation times of the task end, so as to save power; furthermore, in the process of adjusting the subtask execution schedule, the order of the progress bars on each remaining time axis is kept unchanged, that is, the time sequence relationship of each subtask will not be disrupted, so as to ensure the smooth progress of the task; the adjusted subtask execution schedule can be sent to each task end, and the terminal device can isolate the subtask execution schedule control power supply to charge each task end, so that each task end is activated at the corresponding time point and completes the subtask execution schedule; In the present application, the entire process of each task can be scheduled when there is no power outage, and then when there is a power outage, the intervals for executing subtasks by each task end after the power outage can be determined based on the previous schedule, and the execution schedule of each task end after the power outage can be adjusted based on this interval, so that the intervals between subtasks are reduced, and the task end can complete multiple subtasks in one activation process, thereby reducing the number of activation times of the task end, which can significantly reduce the large amount of energy loss caused by repeated activation and save the power supply energy, so that a power supply with limited energy can provide power supply to each task end for a longer time.

[0014] As a preferred embodiment, generating a task timeline for this task and generating a progress bar for each subtask on the task timeline according to the task amount of this task includes: 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.

[0015] 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 the terminal device to generate and send the task timeline; the task amount-execution duration comparison table is a comparison table preset according to historical data, and the historical data includes the duration of each task execution in history. Since the task amount of each task is inconsistent, the execution time of the task under all task amounts can be obtained; the historical data also includes the ratio of the sub-execution duration to the execution time of each subtask when the task is executed each time; therefore, for each subtask, the corresponding execution time ratio of the subtask can be obtained by calculating the average of the ratio of the sub-execution duration to the execution time of the subtask when the task is executed each time in history; the length of the progress bar represents the sub-execution time of executing the corresponding subtask, so the execution progress of the subtask can be determined according to the ratio of the length of the time axis corresponding to the length of the progress bar to the length of the subtask that has been executed; In this embodiment, when a task end completes a subtask, it can trigger the next task end to start the corresponding subtask. That is, the task process of each task end can be regarded as continuous. Therefore, the progress bar on each task time axis is a progress bar connected from beginning to end. As a preferred embodiment, Figure 4 As shown, determining the remaining time axis of each task time axis, and then obtaining the distribution of the progress bar on each remaining time axis includes: Determine the time of power outage; For each task timeline, identifying a 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.

[0016] The truncated progress bar is the progress bar of the corresponding subtask being executed by the corresponding task end, and between step S5 and step S6, the following is also included: 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.

[0017] 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, and 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 they are executing; and for the task ends that are not performing tasks, they can be controlled to enter a sleep state to avoid unnecessary energy waste.

[0018] As a preferred embodiment, the subtask execution arrangement of each task end is determined according to the distribution of the progress bars on each remaining time axis, and the subtask execution arrangement of each task end is adjusted 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: Determine whether there is a gap between the backup progress bars on the first time axis. If so, 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. When adjusting the backup progress bar on the first time axis, adjust the progress bars on the remaining time axes accordingly 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.

[0019] In this embodiment, the time interval corresponding to the initial position of each backup progress bar on the first time axis is consistent with the time interval corresponding to the corresponding initial progress bar on the remaining time axis; Figure 5 As shown, when there is no gap between the backup progress bars on the first time axis, the backup progress bars may not be adjusted, or the front backup progress bar may be moved to the back backup progress bar to make the backup progress bars more compact, thereby reducing the total power consumption.

[0020] As a preferred embodiment, moving the front backup progress bar to the back backup progress bar so that there is no gap between the backup progress bars 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.

[0021] In this embodiment, the tasks are connected end to end in sequence, that is, they are connected end to end in the time sequence corresponding to the backup progress bar when it is in the initial position; since the starting edges of the backup progress bars overlap, when the combined progress bar is combined, its starting edge automatically overlaps with the starting edge of the longest alternative progress bar; the task end has marginal benefits when executing tasks, that is, the more tasks the task end executes simultaneously, the less energy is consumed by individual tasks; when the task end executes only one subtask in a period of time, its energy consumption is the lowest cost-effective; through this embodiment, the total duration of the task end executing the task after one activation can be controlled to the shortest, that is, the duration corresponding to the length of the longest backup progress bar, and the positions of the backup progress bars 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 at the same time; further, the last layer of combined progress bars can be only one backup progress bar), so that the time period for the task end to execute a subtask alone is minimized, which can further save power energy.

[0022] As a preferred embodiment, 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.

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

[0024] As a preferred embodiment, determining the corresponding activation time point according to the adjusted subtask execution arrangement of the task end includes: 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.

[0025] In this embodiment, after the activation time point is determined, 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 activate, and execute the corresponding subtasks according to the time intervals distributed by the backup progress bars on the first timeline.

[0026] A terminal device provided in a second embodiment of the present application includes 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, specifically including: 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 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 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 indicated by the task instruction; 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 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 on each remaining time axis, so that each task end can complete multiple subtasks in one activation process, thereby reducing the number of activation times of the task end; S7: For each task end, determine the corresponding activation time point according to the adjusted subtask execution schedule of the task end, 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.

[0027] A storage medium is provided in a 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, specifically including: 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 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 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 indicated by the task instruction; 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 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 on each remaining time axis, so that each task end can complete multiple subtasks in one activation process, thereby reducing the number of activation times of the task end; S7: For each task end, determine the corresponding activation time point according to the adjusted subtask execution schedule of the task end, control the power supply to charge the task end before the activation time point, and send the adjusted subtask schedule to the task end.

[0028] It should be understood that the size of the serial numbers of the steps in the above embodiments does 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 on the implementation process of the embodiments of the present application.

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

[0030] It should also be understood that the term “and / or” 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.

[0031] As used in the present specification, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting" depending on the context. Similarly, the phrase "if it is determined" or "if [the described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [the described condition or event] is detected" or "in response to detecting [the described condition or event]" depending on the context.

[0032] In addition, in the description of the present specification, the terms "first", "second", "third", etc. are only used to distinguish descriptions, and cannot be understood as indicating or implying relative importance. It should also be understood that although the terms "first", "second", etc. are used to describe various elements in some embodiments of the present application in the text, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, the first table can be named as the second table, and similarly, the second table can be named as 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.

[0033] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

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

[0035] For example, the terminal device can 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 function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a vehicle networking terminal, a computer, a laptop computer, a handheld communication device, a handheld computing device, a satellite wireless device, a wireless modem card, a TV set top box (STB), a customer premises equipment (CPE) and / or other devices for communicating on a wireless system and a next-generation communication system, such as a mobile terminal in a 5G network or a mobile terminal in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0036] As an example but not limitation, when the terminal device is a wearable device, the wearable device can also be a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, 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 clothes or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0037] Figure 6 Schematic diagram of the structure of a terminal device provided by an embodiment of the present application. Figure 6 As shown, the terminal device of this embodiment includes: at least one processor ( Figure 6 Only one is shown in the figure), a memory, wherein the memory stores a computer program that can be run on the processor. When the processor executes the computer program, the steps in the above-mentioned embodiments of the intelligent charging management method are implemented, such as Figure 1 Steps S1 to S7 are shown.

[0038] The terminal device may be a computing device such as a desktop computer, a notebook, a PDA, or a cloud server. The terminal device may include, but is not limited to, a processor and a memory. Those skilled in the art will understand that Figure 6 It is only an example of a terminal device and does not constitute a limitation of the terminal device. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the terminal device may also include an input sending device, a network access device, a bus, etc.

[0039] The processor may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0040] In some embodiments, the memory may be an internal storage unit of the terminal device, such as a 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. Furthermore, the memory may include both an internal storage unit and an external storage device of the terminal device. The memory is used to store an operating system, an application program, 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 is to be sent.

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

[0042] An embodiment of the present application provides a computer program product. When the computer program product is run on a mobile terminal device, the mobile terminal device can implement the steps in the above-mentioned method embodiments when executing the computer program product.

[0043] 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, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device that can carry the computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal and software distribution medium, etc.

[0044] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0045] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

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

[0047] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present 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 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 on each remaining time axis, so that each task end can complete multiple subtasks in one activation process, thereby reducing the number of activation times of the task end; S7: For each task end, determine the corresponding activation time point according to the adjusted subtask execution schedule of the task end, 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, identifying a 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, and between step S5 and step S6, the following is also included: 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: Determine whether there is a gap between the backup progress bars on the first time axis. If so, 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. When adjusting the backup progress bar on the first time axis, adjust the progress bars on the remaining time axes accordingly 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 starting edges have overlapped, so that the starting edge of the next backup progress bar also overlaps with the starting edge of the moved backup progress bar, and repeat this step until the starting 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 according to 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