Edge calculation-based automatic planning and scheduling method for cooperation task of live maintenance mechanical device

Abstract

The invention discloses an edge calculation-based automatic planning and scheduling method for cooperative tasks of a live-line maintenance mechanical device, and relates to the technical field of task planning and scheduling. The method comprises the following steps: acquiring a scheduling device for real-time scheduling; obtaining a maintenance task of the scheduling device and recording the maintenance task as a scheduling maintenance task, and extracting other devices assisting the scheduling device to complete the scheduling maintenance task from other devices and recording the other devices as first devices; obtaining task conditions of the first devices, and selecting a second device from the first devices; obtaining task levels of the second devices, and selecting a third device from the second devices; the device position of a third device is acquired, and a cooperation device is selected from the third device; and transmitting task data for scheduling the maintenance task to the cooperation device, and cooperating with the scheduling device to complete the maintenance task. According to the invention, the maintenance efficiency of edge calculation-based automatic cooperative task planning and scheduling of the hot-line maintenance mechanical device is improved.

Description

Technical Field

[0001] The present application relates to the technical field of task planning and scheduling, and in particular to a method for automatic planning and scheduling of collaborative tasks of live maintenance mechanical devices based on edge computing. Background Art

[0002] Live maintenance machinery refers to mechanical equipment or robots specifically designed to perform maintenance tasks in live environments. These mechanical devices typically possess high insulation performance and adaptability, enabling them to safely and efficiently complete maintenance operations in high-voltage electric fields. During the maintenance process, due to the large number of maintenance equipment and the high number of maintenance requirements, maintenance tasks need to be planned to improve maintenance efficiency. Existing maintenance task planning typically only considers single task requirements, but in reality, many tasks require collaboration. Single-task planning is not suitable for scheduling collaborative tasks, which affects the efficiency of live maintenance. Summary of the Invention

[0003] The purpose of the present invention is to provide an automatic planning and scheduling method for collaborative tasks of live maintenance mechanical devices based on edge computing to solve the problems raised in the above background technology.

[0004] Obtain the live maintenance mechanical devices that are scheduled in real time and record them as scheduled devices. Other live maintenance mechanical devices other than the scheduled devices are recorded as other devices.

[0005] Obtaining a maintenance task of the scheduling device and recording it as the scheduling maintenance task; extracting other devices from other devices according to the scheduling maintenance task to assist the scheduling device in completing the scheduling maintenance task and recording them as the first device;

[0006] Obtaining a task status of the first device, and selecting a second device from the first device according to the task status;

[0007] Obtaining a task level of the second device, and selecting a third device from the second device according to the task level;

[0008] Obtaining a device location of a third device, and selecting a cooperating device from the third device according to the device location;

[0009] The task data of the scheduling and maintenance task is transmitted to the collaborative device, and the scheduling device is cooperated to complete the maintenance task.

[0010] Preferably, the step of obtaining the task status of the first device and selecting the second device from the first device according to the task status is specifically as follows:

[0011] Determine whether the first device is performing a maintenance task, and if the first device is not performing the maintenance task, record the first device as the second device;

[0012] If the first device is performing a maintenance task, determining whether the maintenance task of the first device is in a paused state;

[0013] If the maintenance task of the first device is in a suspended state, the impact degree of the suspended maintenance task is obtained, and the second device is selected according to the impact degree;

[0014] If the maintenance task of the first device does not have a pause state, the first device does not serve as the second device.

[0015] Preferably, if the maintenance task of the first device is in a suspended state, the step of obtaining the impact degree of the suspended maintenance task and selecting the second device according to the impact degree is specifically as follows:

[0016] Recording the maintenance task of the first device as a first maintenance task, determining whether the first maintenance task changes the state of the corresponding maintenance equipment, and if the first maintenance task changes the state of the corresponding maintenance equipment, obtaining the real-time state of the corresponding maintenance equipment;

[0017] Obtain maintenance environment data, and obtain the degree to which the real-time morphology is affected by the environment based on the maintenance environment data and record it as the environmental impact degree;

[0018] Obtain historical maintenance data, extract the accident probability in real-time form from the historical maintenance data and record it as the safety impact;

[0019] Count the number of live maintenance mechanical devices working together in the first maintenance task, establish a correlation curve between the number of live maintenance mechanical devices and resource impact, and find the corresponding resource impact based on the correlation curve;

[0020] The impact of suspending the first maintenance task is obtained by combining the environmental impact, the safety impact, and the resource impact;

[0021] If the first maintenance task does not change the state of the corresponding maintenance equipment, the resource impact is recorded as the suspension impact;

[0022] A pause impact threshold is set, and the first device whose pause impact does not reach the pause impact threshold is selected and recorded as the second device.

[0023] Preferably, the step of obtaining the task level of the second device and selecting the third device from the second device according to the task level is specifically as follows:

[0024] Obtain task information data of maintenance tasks, and match corresponding task levels for different maintenance tasks according to the task information data;

[0025] The task level of the second device is recorded as the second task level, and the task level corresponding to the scheduling maintenance task is recorded as the scheduling task level;

[0026] A second device whose second task level is smaller than the scheduled task level is selected and recorded as the third device.

[0027] Preferably, the steps of obtaining task information data of the maintenance task and matching corresponding task levels for different maintenance tasks according to the task information data are specifically as follows:

[0028] Obtain the necessary maintenance conditions for the maintenance task, and obtain the remaining existence time and condition stability of the necessary maintenance conditions;

[0029] Determine whether the maintenance task meets the necessary conditions for maintenance. If the maintenance task meets the necessary conditions for maintenance, it will be recorded as a pending maintenance task; otherwise, it will be recorded as a first-level maintenance task;

[0030] Obtain the tension of the necessary conditions for the pending maintenance task based on the remaining existence time and condition stability of the necessary conditions, and set the threshold of the tension;

[0031] Obtain the maintenance optimization conditions of the pending maintenance tasks, and obtain the remaining existence time and condition stability of the maintenance optimization conditions;

[0032] The optimization condition tension of the pending maintenance task is obtained according to the remaining existence time and condition stability of the maintenance optimization condition;

[0033] Set the optimization tension threshold, and classify the pending maintenance tasks that meet both the required tension threshold and the optimized tension threshold as level 5 maintenance tasks, classify the pending maintenance tasks that only meet the required tension threshold as level 4 maintenance tasks, classify the pending maintenance tasks that only meet the optimized tension threshold as level 3 maintenance tasks, and classify the pending maintenance tasks that do not meet both the required tension threshold and the optimized tension threshold as level 2 maintenance tasks.

[0034] Preferably, the step of obtaining the remaining existence time and condition stability of the necessary maintenance conditions is specifically as follows:

[0035] Determine whether the necessary maintenance conditions have a fixed existence time range. If the necessary maintenance conditions have a fixed existence time range, obtain the real-time time point;

[0036] Calculate the remaining existence time based on the fixed existence time range and the real-time time point;

[0037] If the maintenance prerequisite does not have a fixed existence time range, then obtain the historical existence data of the maintenance prerequisite;

[0038] The existence frequency of necessary maintenance conditions in different time periods is obtained based on historical existence data;

[0039] Set a frequency threshold, use the time period with the highest frequency and reaching the frequency threshold as the daily time range, and calculate the remaining time based on the real-time time point;

[0040] If the daily time range cannot be extracted based on the historical existence data, the average continuous existence time of the necessary maintenance conditions is extracted based on the historical existence data;

[0041] Obtain the real-time existence duration of the maintenance prerequisites, and calculate the remaining existence duration based on the real-time existence duration and the average continuous existence duration;

[0042] The stability of the necessary maintenance conditions is analyzed based on historical existing data to obtain the conditional stability.

[0043] Preferably, the step of analyzing the stability of the necessary maintenance conditions based on historical existing data to obtain the condition stability is specifically as follows:

[0044] The change frequency and average change speed of the necessary maintenance conditions are obtained based on the historical existing data;

[0045] Obtain the maintenance duration of the necessary maintenance conditions, calculate the degree of change of the necessary maintenance tasks based on the maintenance duration and the average change rate, and calculate the basic degree of change based on the change frequency;

[0046] The existence probability of the necessary maintenance conditions in different environments is obtained based on historical existence data;

[0047] According to the maintenance environment data matching, the corresponding existence probability is obtained and recorded as the environmental change degree;

[0048] The change weight ratios of the basic change degree and the environmental change degree are set respectively, and the conditional stability is calculated according to the basic change degree, the environmental change degree and the corresponding change weight ratios.

[0049] Preferably, the step of obtaining the device location of the third device and selecting a cooperating device from the third device according to the device location is specifically:

[0050] Obtain the device location of the third device, obtain the task location of the scheduling device, count all routes from the device location to the task location and record them as pending routes;

[0051] Count the number of obstacles on the pending route and obtain the route distance of the pending route;

[0052] Obtaining route convenience based on the number of obstacles and the route distance, setting a route convenience threshold, and recording the third device that reaches the route convenience threshold as a candidate device;

[0053] Determine whether the number of candidate devices is greater than 1. If the number of candidate devices is greater than 1, select the candidate device with the greatest route convenience as the cooperative device.

[0054] If the number of the devices to be selected is not greater than 1, determining whether the number of the devices to be selected is 1, and if so, taking the devices to be selected as cooperative devices;

[0055] If the number of devices to be selected is not 1, there is no cooperating device, and the scheduling device stops the maintenance task and waits for other devices to be dispatched.

[0056] Preferably, the step of transmitting the task data of the scheduled maintenance task to the collaboration device and cooperating with the scheduling device to complete the maintenance task is specifically as follows:

[0057] Obtain the task data of the scheduled maintenance task and the device number of the collaborative device;

[0058] Selecting the undetermined route corresponding to the cooperative device with the highest route convenience as the moving route;

[0059] Obtain the transmission location of the task data and find the point on the moving route with the shortest distance to the transmission location as the transmission point;

[0060] The data transmission device corresponding to the task data detects the live maintenance mechanical device that has arrived at the transmission point and confirms whether it is a cooperative device based on the device number;

[0061] If it is a cooperative device, the task data is sent to the cooperative device.

[0062] In summary, this application includes at least one of the following beneficial technical effects:

[0063] 1. Determine the dispatching device. Based on the dispatching requirements, task status, task level, and device location, select the collaborative device that will assist the dispatching device in completing the maintenance task. The optimal route is chosen. During the movement, the task data is transmitted to the closest point to the task data transmission device, enabling the scheduling of the collaborative task and thus completing the maintenance task. By determining and selecting the collaborative device from multiple perspectives, the impact of scheduling on other maintenance tasks is greatly reduced, improving the overall maintenance efficiency of the automatic planning and scheduling of collaborative tasks for live maintenance mechanical devices based on edge computing.

[0064] 2. By determining whether the maintenance task is paused, the impact of the environment on the maintenance equipment during the paused maintenance task, as well as the safety and resource impacts of the paused state, is comprehensively determined. Considering whether the device is currently performing the maintenance task, the device that is most suitable for assisting the dispatching device in completing the collaborative task is selected. By determining the impact of other devices assisting in the task, the accuracy of device selection is improved, and the accuracy of the automated planning and scheduling of collaborative tasks for live maintenance mechanical devices based on edge computing is enhanced.

[0065] 3. By distinguishing between essential maintenance conditions and optimized maintenance conditions, the corresponding remaining duration is determined based on the actual existence of each condition. The historical change frequency of the condition, as well as the average change rate of the condition and the maintenance duration, are used to determine the degree of change in the essential maintenance task, and the basic degree of change is comprehensively calculated. The corresponding existence probability of the essential maintenance condition in different environments is then matched to obtain the environmental degree of change, and finally the condition stability. The stability of the condition facilitates subsequent determination and confirmation of the maintenance task level. Determining the stability of the condition based on actual conditions improves the intelligence of the automatic planning and scheduling of collaborative tasks for live maintenance mechanical devices based on edge computing. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] Figure 1 It is a schematic diagram of the specific steps of an embodiment of the method for automatic planning and scheduling of collaborative tasks of live maintenance mechanical devices based on edge computing of the present invention. DETAILED DESCRIPTION

[0067] Below is a combination of the embodiments and Figure 1 The present invention will be described in further detail, but the embodiments of the present invention are not limited thereto.

[0068] The present invention discloses an automatic planning and scheduling method for collaborative tasks of live maintenance mechanical devices based on edge computing, which specifically includes the following steps:

[0069] Step S1: obtain the live maintenance mechanical device that is scheduled in real time and record it as the scheduled device, and record other live maintenance mechanical devices other than the scheduled device as other devices.

[0070] Live maintenance equipment is divided into zones. Different live maintenance equipment has its own zone tasks. The live maintenance equipment that requires real-time scheduling is determined based on the equipment's maintenance status. For example, if equipment A is responsible for zone A and equipment B is responsible for zone B, and equipment A's task is complete and needs to be assigned to the next task, then equipment A needs to be scheduled and becomes the scheduling device. If equipment B is currently undergoing maintenance or has already been assigned a task, then equipment B becomes a "other" device.

[0071] Step S2: Obtain the maintenance task of the scheduling device and record it as the scheduling maintenance task; extract other devices that assist the scheduling device in completing the scheduling maintenance task from other devices according to the scheduling maintenance task and record them as the first device.

[0072] During maintenance, some tasks require the collaboration of multiple live maintenance devices. Therefore, it's necessary to identify the devices that will assist in the scheduled maintenance task. For example, if device A is the scheduling device, and the next scheduled maintenance task requires the collaboration of device A, and devices B and E are type A, and devices C and D are type B, then the devices that can assist device A in completing the scheduled maintenance task are devices B and E. These devices are recorded as the first devices.

[0073] Step S3: Obtain the task status of the first device, and select the second device from the first device according to the task status.

[0074] Step S4: Obtain the task level of the second device, and select a third device from the second devices according to the task level.

[0075] Step S5: Acquire the device location of the third device, and select a cooperative device from the third device according to the device location.

[0076] Step S6: transmit the task data of the scheduled maintenance task to the cooperation device, and cooperate with the scheduling device to complete the maintenance task.

[0077] In practice, when overhauling live mechanical equipment, some tasks require the assistance of multiple devices. To improve efficiency, these tasks are often assigned to different areas, allowing for faster completion of independent tasks. When collaborative tasks are required, dispatching devices is necessary. Selecting the optimal device for dispatching can improve both efficiency and effectiveness while minimizing the impact on maintenance tasks.

[0078] The steps of obtaining the task status of the first device and selecting the second device from the first device according to the task status are specifically as follows:

[0079] Step S31, determining whether the first device is performing a maintenance task. If the first device is not performing a maintenance task, the first device is recorded as a second device.

[0080] If the first device is not performing a maintenance task, it means that the first device is in an idle state at this time, and scheduling can be performed directly.

[0081] Step S32: If the first device is performing a maintenance task, it is determined whether the maintenance task of the first device is in a paused state.

[0082] Whether the maintenance task of the first device has a pause status, that is, whether the maintenance task of the first device can be stopped midway. If pausing the maintenance task of the first device would cause damage to the equipment being maintained, explosion, or invalidation of all maintenance data, the maintenance task of the first device cannot be paused. In other words, the maintenance task of the first device does not have a pause status.

[0083] In step S33, if the maintenance task of the first device is in a suspended state, the impact degree of the suspended maintenance task is obtained, and the second device is selected according to the impact degree.

[0084] If the first device can suspend maintenance and continue the maintenance task after completing the assistance task, it is determined whether the scheduling device can be assisted based on the impact of the suspension.

[0085] Step S34: If the maintenance task of the first device does not have a pause state, the first device does not serve as the second device.

[0086] In practice, because different devices perform different maintenance tasks, the dispatch process needs to consider whether other devices can assist. If the consequences of other devices assisting the dispatched device in completing the maintenance task are serious, there is no need to dispatch other devices immediately. For example, if device A requires the assistance of device B to complete a maintenance task, but device B is currently performing maintenance, pausing the maintenance task at this moment would cause damage to the machine. In this case, device B should not be dispatched, and other devices can be sought for assistance.

[0087] If the maintenance task of the first device is in a suspended state, the impact degree of the suspended maintenance task is obtained, and the steps of obtaining the second device are selected according to the impact degree, specifically:

[0088] Step S331, record the maintenance task of the first device as the first maintenance task, and determine whether the first maintenance task changes the form of the corresponding maintenance equipment. If the first maintenance task changes the form of the corresponding maintenance equipment, obtain the real-time form of the corresponding maintenance equipment.

[0089] Different maintenance tasks require different operations on maintenance equipment. Some maintenance tasks require inspecting the interior of a machine or equipment, which requires opening the machine casing for inspection. This changes the appearance of the maintenance equipment. Maintenance equipment refers to the equipment that requires maintenance of live mechanical devices.

[0090] Step S332: Obtain maintenance environment data, and obtain the degree to which the real-time morphology is affected by the environment based on the maintenance environment data and record it as the environmental impact degree.

[0091] Maintenance environment data includes, but is not limited to, temperature, humidity, and electromagnetic interference. The standard environment required by the real-time state is compared with the maintenance environment, and the environmental impact is determined using a pre-set similarity-environmental impact table. The higher the similarity, the lower the environmental impact. For example, the outer casing of a maintenance device is designed to insulate heat. If the temperature is too low, causing damage to the equipment, then opening the casing will significantly impact the external temperature.

[0092] Step S333: Obtain historical maintenance data, extract the accident occurrence probability in real-time form from the historical maintenance data and record it as the safety impact.

[0093] At the same time, opening the casing of some equipment or adjusting parameters can increase the risk of dangerous accidents. For example, some equipment needs to be adjusted to extreme values ​​during maintenance to confirm whether the equipment's safety protection functions are functioning properly, and adjusting to extreme values ​​can increase the probability of accidents.

[0094] Step S334 , counting the number of live maintenance mechanical devices working together in the first maintenance task, establishing a correlation curve between the number of live maintenance mechanical devices and resource impact, and finding the corresponding resource impact according to the correlation curve.

[0095] Just because the first device is performing maintenance doesn't mean it's performing maintenance independently; it could also be performing a collaborative task. For example, if device A needs device B, and device B is currently performing a collaborative task with devices C and D, dispatching device B will put both devices C and D in a suspended state, wasting their resources.

[0096] Step S335 : The impact degree of suspending the first maintenance task is obtained by combining the environmental impact degree, the safety impact degree, and the resource impact degree.

[0097] The weight ratios of the environmental impact, security impact, and resource impact are set respectively, and the suspension impact is calculated based on the environmental impact, security impact, resource impact, and the corresponding weight ratios.

[0098] Step S336: If the first maintenance task does not change the state of the corresponding maintenance equipment, the resource impact is recorded as a suspension impact.

[0099] Step S337: Set a pause impact threshold, select a first device whose pause impact does not reach the pause impact threshold, and record it as the second device.

[0100] In practice, when scheduling devices, the reasonableness of the impact of the scheduling process must be fully considered. If the consequences of scheduling other devices are severe, the device is not suitable for scheduling. For example, device A can schedule device B for a collaborative task, but if device B stops its own maintenance task, it may damage the maintenance equipment, affect personnel safety, and cause other equipment to suspend operation, thereby wasting resources. Therefore, device B should not be scheduled and is not considered the second device.

[0101] The steps of obtaining the task level of the second device and selecting the third device from the second device according to the task level are specifically as follows:

[0102] Step S41: Acquire task information data of the maintenance task, and match corresponding task levels for different maintenance tasks according to the task information data.

[0103] Step S42: record the task level of the second device as the second task level, and record the task level corresponding to the scheduling maintenance task as the scheduling task level.

[0104] Step S43: Filter the second device whose second task level is smaller than the scheduled task level and record it as the third device.

[0105] In practice, the urgency of different tasks varies. Some maintenance tasks are more urgent and therefore have a higher level, while some maintenance tasks are less urgent and therefore have a lower level. If the second device has a higher level task, there is no reason to call the second device to complete the lower level task first.

[0106] The steps for obtaining task information data of maintenance tasks and matching corresponding task levels for different maintenance tasks according to the task information data are as follows:

[0107] Step S411, obtaining the necessary maintenance conditions for the maintenance task, and obtaining the remaining existence time and condition stability of the necessary maintenance conditions.

[0108] Maintenance prerequisites refer to conditions that must be met during the maintenance process; if they are not met, the maintenance task cannot be completed. For example, if maintenance task 1 requires the presence of an operator, then the presence of an operator is a maintenance prerequisite.

[0109] Step S412, determining whether the maintenance task meets the necessary maintenance conditions. If the maintenance task meets the necessary maintenance conditions, it is recorded as a pending maintenance task; otherwise, it is recorded as a first-level maintenance task.

[0110] If the maintenance task does not meet the necessary conditions for maintenance, it means that the maintenance task cannot be carried out at this moment, and the maintenance task corresponding to the device is the lowest level, the first level maintenance task.

[0111] Step S413: Obtain the tension of the necessary conditions for the pending maintenance task based on the remaining existence time of the necessary maintenance conditions and the stability of the conditions, and set a threshold for the tension.

[0112] The weight ratios of the remaining existence time and the conditional stability are set respectively, and the necessary tension threshold is calculated according to the remaining existence time, the conditional stability and the corresponding weight ratios.

[0113] Step S414: Obtain the maintenance optimization conditions of the pending maintenance task, and obtain the remaining existence time and condition stability of the maintenance optimization conditions.

[0114] Maintenance optimization conditions refer to conditions that are conducive to the maintenance tasks during the maintenance process. It doesn’t matter if they are not there, and it is better to have them.

[0115] Step S415: Obtain the tension of the optimization conditions of the pending maintenance task according to the remaining existence time of the maintenance optimization conditions and the stability of the conditions.

[0116] The calculation method of the optimization condition tension is the same as the calculation method of the necessary condition tension.

[0117] Step S416, setting the optimized tension threshold, classifying the pending maintenance tasks that reach both the required tension threshold and the optimized tension threshold as level five maintenance tasks, classifying the pending maintenance tasks that only reach the required tension threshold as level four maintenance tasks, classifying the pending maintenance tasks that only reach the optimized tension threshold as level three maintenance tasks, and classifying the pending maintenance tasks that do not reach both the required tension threshold and the optimized tension threshold as level two maintenance tasks.

[0118] In practice, the conditions for maintenance tasks aren't always present. For example, the essential condition for a maintenance task is the presence of an operator, but operators aren't always on-site. Similarly, if the optimization condition is a temperature of 25 degrees Celsius, the temperature changes in real time. The greater the condition's tension, the greater the probability that the condition will disappear, and therefore, the more timely maintenance is needed to minimize the time lost due to the condition's disappearance. The tension of the essential condition is more important than the tension of the optimal condition, so different tasks can be classified based on the tension of these two conditions. Within the same level, the greater the total tension of the two conditions, the higher the level. For example, if there are three devices in level 5, A, B, and C, the total tension of these three devices will be used to distinguish between sub-levels.

[0119] The steps for obtaining the remaining existence time and condition stability of the necessary maintenance conditions are as follows:

[0120] Step S4111, determine whether the necessary maintenance conditions have a fixed existence time range, and if the necessary maintenance conditions have a fixed existence time range, obtain the real-time time point.

[0121] Some necessary conditions have a fixed existence time. For example, the operator's working hours are from 9 am to 6 pm. The operator is always present from 9 am to 6 pm. Therefore, the operator's presence time is fixed and the existence time range is from 9 am to 6 pm.

[0122] Step S4112: Calculate the remaining existence time based on the fixed existence time range and the real-time time point.

[0123] For example, if the time range is from 9:00 AM to 6:00 PM and the real-time time is 5:00 AM, the remaining time is 1 hour.

[0124] Step S4113: If the necessary maintenance condition does not have a fixed existence time range, then obtain the historical existence data of the necessary maintenance condition.

[0125] Step S4114: extract the existence frequency of the necessary maintenance conditions in different time periods based on the historical existence data.

[0126] Step S4115: Set an existence frequency threshold, take the time period with the maximum existence frequency and reaching the existence frequency threshold as the daily time range, and calculate the remaining time in combination with the real-time time point.

[0127] Some conditions don't always exist for fixed periods of time, but their frequency can reveal patterns and provide a rough time range. For example, temperature fluctuations are lower in the morning and evening, and slightly higher during the day. This suggests that 25 degrees Celsius typically exists between 10 AM and 4 PM, so the daily time range is 10 AM to 4 PM.

[0128] Step S4116: If the daily time range cannot be extracted based on the historical existence data, the average continuous existence time of the maintenance prerequisite is extracted based on the historical existence data.

[0129] Step S4117: Acquire the real-time existence duration of the maintenance prerequisite, and calculate the remaining existence duration based on the real-time existence duration and the average continuous existence duration.

[0130] Some conditions exist with no apparent pattern. For these conditions, the remaining duration is calculated based on the average duration. For example, if a technician is required to be on-site but their arrival time is uncertain, the average on-site time is 2 hours. If the technician has already been on-site for 1 hour, the remaining duration is 1 hour.

[0131] Step S4118: Analyze the stability of the necessary maintenance conditions based on historical existing data to obtain the condition stability.

[0132] In practice, the remaining time for maintenance prerequisites needs to be determined based on the specific conditions. The remaining time and stability of maintenance optimization conditions are derived using the same method as for maintenance prerequisites: the remaining time and stability of maintenance optimization conditions are derived using the same method as for maintenance prerequisites. Determining the remaining time allows us to determine the urgency of maintenance and prioritize more pressing tasks, reducing waste of time and resources.

[0133] The steps to obtain the stability of the necessary conditions for maintenance based on historical existing data are as follows:

[0134] Step S41181: Extract the change frequency and average change speed of the necessary maintenance conditions based on historical data.

[0135] Step S41182: Obtain the maintenance duration of the necessary maintenance conditions, calculate the degree of change of the necessary maintenance tasks based on the maintenance duration and the average change rate, and obtain the basic change degree based on the change frequency.

[0136] For example, if the temperature increases by 1 degree per hour and the maintenance has been ongoing for two hours, the change is 2 degrees. If the temperature change range is 10 degrees Celsius, the degree of change is 20%. Then, set the degree of change and the percentage of the frequency of change respectively. The basic degree of change is calculated based on the degree of change, the frequency of change, and the corresponding percentages.

[0137] Step S41183, extract the existence probability of the necessary maintenance conditions in different environments based on historical existence data.

[0138] Step S41184: obtain the corresponding existence probability based on the maintenance environment data and record it as the environment change degree.

[0139] Step S41185, respectively set the change weight ratios of the basic change degree and the environmental change degree, and calculate the conditional stability based on the basic change degree, the environmental change degree and the corresponding change weight ratios.

[0140] In practice, if a condition's historical frequency of change is high, it indicates that the condition itself is less stable. The basic variability of the condition is calculated based on the actual changes. The variability of a condition varies in different environments, and determining the environmental variability based on actual conditions helps to obtain a more accurate variability. For example, humidity changes at different rates at different temperatures. At high temperatures, humidity is more difficult to maintain at its original value, resulting in lower stability. Air quality is easily affected by dust and ventilation, which can alter air quality. Therefore, air quality is more susceptible to change, resulting in a greater basic variability.

[0141] The steps of obtaining the device location of the third device and selecting a cooperating device from the third device according to the device location are specifically as follows:

[0142] Step S51, obtaining the device location of the third device, obtaining the task location of the scheduling device, counting all routes from the device location to the task location and recording them as pending routes.

[0143] Since the devices are performing maintenance tasks at different locations, when a collaborative device needs to be dispatched, it needs to be moved to the task location. According to the maintenance site layout map, all routes between two points can be obtained.

[0144] Step S52: Count the number of obstacles on the route to be determined and obtain the route distance of the route to be determined.

[0145] In step S53, the route convenience is obtained according to the number of obstacles and the route distance, a route convenience threshold is set, and the third device that reaches the route convenience threshold is recorded as a candidate device.

[0146] The greater the number of obstacles and the longer the route, the lower the convenience of the route. Set the percentage of the number of obstacles and the route distance respectively, and calculate the route convenience based on the number of obstacles, route distance and the corresponding percentage.

[0147] Step S54 , determining whether the number of the to-be-selected devices is greater than 1. If the number of the to-be-selected devices is greater than 1, selecting the to-be-selected device with the greatest route convenience as the cooperative device.

[0148] Step S55: If the number of the to-be-selected devices is not greater than 1, it is determined whether the number of the to-be-selected devices is 1. If it is 1, the to-be-selected device is used as a cooperative device.

[0149] Step S56: If the number of devices to be selected is not 1, there is no cooperative device, and the scheduling device stops the maintenance task and waits for other devices to be dispatched.

[0150] In actual use, multiple devices may be found during the scheduling process. Among these devices, the device with the highest route convenience is selected as the collaborative device. The route with the highest route convenience is selected from each device as the route convenience corresponding to the device, and then the devices are compared to select the collaborative device. If there is only one device to be selected, only this device can be selected as the collaborative device. Of course, there may be no suitable device, and scheduling cannot be performed. For example, at this time, other devices are performing maintenance tasks or have tasks to be implemented, and the task levels are higher than those of the scheduling device. In this case, it is not appropriate to schedule other devices to complete the collaborative task of the scheduling device. At this time, the scheduling device suspends the maintenance task and waits for the scheduling of other devices.

[0151] The steps for transmitting the task data of the scheduled maintenance task to the collaborative device and cooperating with the scheduling device to complete the maintenance task are as follows:

[0152] Step S61: Obtain task data of the scheduled maintenance task and obtain the device number of the coordinated device.

[0153] Different collaboration devices have their own unique device numbers.

[0154] Step S62: Select the pending route corresponding to the cooperative device with the highest route convenience as the moving route.

[0155] Step S63: Obtain the transmission location of the task data, and search for a point on the moving route with the shortest distance to the transmission location as a transmission point.

[0156] In step S64, the data transmission device corresponding to the task data detects the live maintenance mechanical device that has arrived at the transmission point, and confirms whether it is a cooperative device based on the device number.

[0157] Data usually needs to be sent to the central control system, and the data transmission device corresponding to the task data is the central control system.

[0158] Step S65: If it is a collaborative device, the task data is sent to the collaborative device.

[0159] In practice, edge computing is a distributed computing architecture that moves computing tasks and data storage from centralized cloud data centers to the edge of the network, close to devices or terminals. This architecture can significantly reduce data transmission latency, improve response speed, and reduce the load on cloud data centers. The transmission point is the point closest to the data transmission device during the collaborative device's journey to the task location. Transmitting data at this point improves data transmission efficiency. Furthermore, transmitting task data to the collaborative device reduces the burden on the central control system, allowing the collaborative device to complete the maintenance task's computing tasks, thus achieving edge computing.

[0160] The above are all preferred embodiments of the present application, and are not intended to limit the scope of protection of the present application. Therefore, any equivalent changes made based on the structure, shape, and principle of the present application should be included in the scope of protection of the present application.

Claims

1. The automatic planning and scheduling method for collaborative tasks of live maintenance mechanical devices based on edge computing is characterized by: The following steps are involved: Obtain the live maintenance mechanical devices that are scheduled in real time and record them as scheduled devices. Other live maintenance mechanical devices other than the scheduled devices are recorded as other devices. Obtaining a maintenance task of the scheduling device and recording it as the scheduling maintenance task; extracting other devices from other devices according to the scheduling maintenance task to assist the scheduling device in completing the scheduling maintenance task and recording them as the first device; Obtaining a task status of the first device, and selecting a second device from the first device according to the task status; Obtaining a task level of the second device, and selecting a third device from the second device according to the task level; Obtaining a device location of a third device, and selecting a cooperating device from the third device according to the device location; The task data of the scheduling and maintenance task is transmitted to the collaborative device, and the scheduling device is cooperated to complete the maintenance task.

2. The method for automatic planning and scheduling of collaborative tasks of live maintenance mechanical devices based on edge computing according to claim 1 is characterized in that: The step of obtaining the task status of the first device and selecting the second device from the first device according to the task status is specifically as follows: Determine whether the first device is performing a maintenance task, and if the first device is not performing the maintenance task, record the first device as the second device; If the first device is performing a maintenance task, determining whether the maintenance task of the first device is in a paused state; If the maintenance task of the first device is in a suspended state, the impact degree of the suspended maintenance task is obtained, and the second device is selected according to the impact degree; If the maintenance task of the first device does not have a pause state, the first device does not serve as the second device.

3. The method for automatic planning and scheduling of collaborative tasks of live maintenance mechanical devices based on edge computing according to claim 2 is characterized in that: If the maintenance task of the first device is in a suspended state, the step of obtaining the impact degree of the suspended maintenance task and selecting the second device according to the impact degree is specifically as follows: Recording the maintenance task of the first device as a first maintenance task, determining whether the first maintenance task changes the state of the corresponding maintenance equipment, and if the first maintenance task changes the state of the corresponding maintenance equipment, obtaining the real-time state of the corresponding maintenance equipment; Obtain maintenance environment data, and obtain the degree to which the real-time morphology is affected by the environment based on the maintenance environment data and record it as the environmental impact degree; Obtain historical maintenance data, extract the accident probability in real-time form from the historical maintenance data and record it as the safety impact; Count the number of live maintenance mechanical devices working together in the first maintenance task, establish a correlation curve between the number of live maintenance mechanical devices and resource impact, and find the corresponding resource impact based on the correlation curve; The impact of suspending the first maintenance task is obtained by combining the environmental impact, the safety impact, and the resource impact; If the first maintenance task does not change the state of the corresponding maintenance equipment, the resource impact is recorded as the suspension impact; A pause impact threshold is set, and the first device whose pause impact does not reach the pause impact threshold is selected and recorded as the second device.

4. The method for automatic planning and scheduling of collaborative tasks of live maintenance mechanical devices based on edge computing according to claim 3 is characterized in that: The step of obtaining the task level of the second device and selecting the third device from the second device according to the task level is specifically as follows: Obtain task information data of maintenance tasks, and match corresponding task levels for different maintenance tasks according to the task information data; The task level of the second device is recorded as the second task level, and the task level corresponding to the scheduling maintenance task is recorded as the scheduling task level; A second device whose second task level is smaller than the scheduled task level is selected and recorded as the third device.

5. The method for automatic planning and scheduling of collaborative tasks of live maintenance mechanical devices based on edge computing according to claim 4 is characterized in that: The steps of obtaining task information data of the maintenance task and matching corresponding task levels for different maintenance tasks according to the task information data are specifically as follows: Obtain the necessary maintenance conditions for the maintenance task, and obtain the remaining existence time and condition stability of the necessary maintenance conditions; Determine whether the maintenance task meets the necessary conditions for maintenance. If the maintenance task meets the necessary conditions for maintenance, it will be recorded as a pending maintenance task; otherwise, it will be recorded as a first-level maintenance task; Obtain the tension of the necessary conditions for the pending maintenance task based on the remaining existence time and condition stability of the necessary conditions, and set the threshold of the tension; Obtain the maintenance optimization conditions of the pending maintenance tasks, and obtain the remaining existence time and condition stability of the maintenance optimization conditions; The optimization condition tension of the pending maintenance task is obtained according to the remaining existence time and condition stability of the maintenance optimization condition; Set the optimization tension threshold, and classify the pending maintenance tasks that meet both the required tension threshold and the optimized tension threshold as level 5 maintenance tasks, classify the pending maintenance tasks that only meet the required tension threshold as level 4 maintenance tasks, classify the pending maintenance tasks that only meet the optimized tension threshold as level 3 maintenance tasks, and classify the pending maintenance tasks that do not meet both the required tension threshold and the optimized tension threshold as level 2 maintenance tasks.

6. The method for automatic planning and scheduling of collaborative tasks of live maintenance mechanical devices based on edge computing according to claim 5 is characterized in that: The steps of obtaining the remaining existence time and condition stability of the necessary maintenance conditions are specifically as follows: Determine whether the necessary maintenance conditions have a fixed existence time range. If the necessary maintenance conditions have a fixed existence time range, obtain the real-time time point; Calculate the remaining existence time based on the fixed existence time range and the real-time time point; If the maintenance prerequisite does not have a fixed existence time range, then obtain the historical existence data of the maintenance prerequisite; The existence frequency of necessary maintenance conditions in different time periods is obtained based on historical existence data; Set a frequency threshold, use the time period with the highest frequency and reaching the frequency threshold as the daily time range, and calculate the remaining time based on the real-time time point; If the daily time range cannot be extracted based on the historical existence data, the average continuous existence time of the necessary maintenance conditions is extracted based on the historical existence data; Obtain the real-time existence duration of the maintenance prerequisites, and calculate the remaining existence duration based on the real-time existence duration and the average continuous existence duration; The stability of the necessary maintenance conditions is analyzed based on historical existing data to obtain the conditional stability.

7. The method for automatic planning and scheduling of collaborative tasks of live maintenance mechanical devices based on edge computing according to claim 6 is characterized in that: The step of analyzing the stability of the necessary maintenance conditions based on historical existing data to obtain the condition stability is specifically as follows: The change frequency and average change speed of the necessary maintenance conditions are obtained based on the historical existing data; Obtain the maintenance duration of the necessary maintenance conditions, calculate the degree of change of the necessary maintenance tasks based on the maintenance duration and the average change rate, and calculate the basic degree of change based on the change frequency; The existence probability of the necessary maintenance conditions in different environments is obtained based on historical existence data; According to the maintenance environment data matching, the corresponding existence probability is obtained and recorded as the environmental change degree; The change weight ratios of the basic change degree and the environmental change degree are set respectively, and the conditional stability is calculated according to the basic change degree, the environmental change degree and the corresponding change weight ratios.

8. The method for automatic planning and scheduling of collaborative tasks of live maintenance mechanical devices based on edge computing according to claim 7 is characterized in that: The step of obtaining the device location of the third device and selecting a cooperating device from the third device according to the device location is specifically as follows: Obtain the device location of the third device, obtain the task location of the scheduling device, count all routes from the device location to the task location and record them as pending routes; Count the number of obstacles on the pending route and obtain the route distance of the pending route; Obtaining route convenience based on the number of obstacles and the route distance, setting a route convenience threshold, and recording the third device that reaches the route convenience threshold as a candidate device; Determine whether the number of candidate devices is greater than 1. If the number of candidate devices is greater than 1, select the candidate device with the greatest route convenience as the cooperative device. If the number of the devices to be selected is not greater than 1, determining whether the number of the devices to be selected is 1, and if so, taking the devices to be selected as cooperative devices; If the number of devices to be selected is not 1, there is no cooperating device, and the scheduling device stops the maintenance task and waits for other devices to be dispatched.

9. The method for automatic planning and scheduling of collaborative tasks of live maintenance mechanical devices based on edge computing according to claim 8 is characterized in that: The steps of transmitting the task data of the scheduled maintenance task to the collaboration device and cooperating with the scheduling device to complete the maintenance task are specifically as follows: Obtain the task data of the scheduled maintenance task and the device number of the collaborative device; Selecting the undetermined route corresponding to the cooperative device with the highest route convenience as the moving route; Obtain the transmission location of the task data and find the point on the moving route with the shortest distance to the transmission location as the transmission point; The data transmission device corresponding to the task data detects the live maintenance mechanical device that has arrived at the transmission point and confirms whether it is a cooperative device based on the device number; If it is a cooperative device, the task data is sent to the cooperative device.

Images