Target proxy device determination method, program product, operation and maintenance device and storage medium

Abstract

The invention provides a target proxy device determination method, a program product, an operation and maintenance device and a storage medium, and is applied to the technical field of electric power engineering application, and the target proxy device determination method comprises the following steps: for any terminal device, obtaining routing information corresponding to the terminal device, the routing information comprises a hierarchy of the terminal device in a multi-layer network architecture and a file transmission performance parameter of each candidate proxy device on a data transmission path of the terminal device, and the data transmission path is a communication link from the operation and maintenance device to the terminal device; and according to a predetermined proxy device selection strategy, on the basis of the routing information and the size of the operation and maintenance file to be issued, one candidate proxy device is determined from a plurality of candidate proxy devices on the data transmission path as a target proxy device responsible for subsequently issuing the operation and maintenance file to the terminal device.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of power engineering application, in particular to a target proxy device determination method, program product, operation and maintenance device and storage medium. BACKGROUND

[0002] In the Internet of Things system of the power engineering site (such as new energy equipment access, substation monitoring and other scenarios), the terminal device is usually connected through a complex network architecture including a cloud server, a gateway and multi-level data forwarding devices. When performing remote operation and maintenance (such as software upgrade, parameter configuration) on these terminal devices, challenges such as scattered device distribution, inconvenient installation location operation, long-term sleep state, etc. are often faced.

[0003] The existing remote operation and maintenance scheme mainly has the following limitations: 1. Direct public network connection scheme: requires terminal devices to be online in real time and have good public network communication capability, not suitable for low-power or network-limited terminals; 2. Single-layer gateway proxy scheme: only through a layer of gateway device for file transfer, unable to effectively utilize and coordinate the forwarding resources in the multi-layer network architecture; 3. Gateway temporary storage and forwarding scheme: although it can deal with the situation of device offline, it only considers single-point storage and does not optimize the file distribution path in the global perspective of multi-level and multi-device.

[0004] In particular, when there are multi-level data forwarding devices in the network, and different communication technologies may be used between levels, the data transmission requirements of the remote operation and maintenance process cannot be met, resulting in high operation and maintenance difficulty and long cycle. SUMMARY

[0005] The purpose of the embodiments of the present application is to provide a target proxy device determination method, program product, operation and maintenance device and storage medium, to solve the technical problems of high operation and maintenance difficulty and long cycle in the prior art.

[0006] In a first aspect, the embodiments of the present application provide a method for determining a target proxy device, applied to an operation and maintenance device, wherein the operation and maintenance device is configured to remotely operate and maintain at least one terminal device deployed in a multi-layer network architecture, the terminal device is arranged at a power engineering site, and the multi-layer network architecture further includes a plurality of proxy devices at different levels; the method includes: for any terminal device, obtaining routing information corresponding to the terminal device, wherein the routing information includes a level of the terminal device in the multi-layer network architecture, and a file transmission performance parameter of each candidate proxy device on a data transmission path of the terminal device, and the data transmission path is a communication link from the operation and maintenance device to the terminal device; according to a predetermined proxy device selection strategy, based on the routing information and a size of an operation and maintenance file to be delivered, a candidate proxy device is determined from a plurality of candidate proxy devices on the data transmission path as a target proxy device responsible for subsequently delivering the operation and maintenance file to the terminal device; wherein the proxy device selection strategy is a first strategy or a second strategy, the first strategy is used to select a candidate proxy device closest to the terminal device in the network level from the plurality of candidate proxy devices when the remaining memory space is not less than the size of the operation and maintenance file, and the second strategy is used to select a candidate proxy device closest to the operation and maintenance device in the network level from the plurality of candidate proxy devices when the remaining memory space is not less than the size of the operation and maintenance file.

[0007] In the above scheme, by intelligently determining a target proxy device for each terminal device, a complex multi-layer network operation and maintenance path planning problem is decomposed into a local optimal decision based on an explicit strategy. It provides two parallel core strategies (i.e. the first strategy and the second strategy), which provides a preset, computable solution for different operation and maintenance scenarios, which fundamentally overcomes the defect that the prior art cannot efficiently plan an operation and maintenance path in a multi-level, heterogeneous network, provides a systematic method basis for reducing the overall operation and maintenance time and complexity, and further makes full use of network performance to achieve more efficient remote operation and maintenance.

[0008] In an optional implementation, the file transmission performance parameter includes: a transmission time required by each candidate proxy device to transmit the operation and maintenance file to a device at a next level, and a remaining memory space of each candidate proxy device.

[0009] In the above scheme, by explicitly defining the file transmission performance parameter as two quantifiable network state indicators, namely transmission time and remaining memory space, the policy decision process has a solid objective data basis. Transmission time is directly related to operation and maintenance efficiency, and remaining memory space determines the carrying capacity of the node. Based on the two, the decision can ensure that the selected target proxy device meets the timeliness requirement and physical storage constraint, significantly improving the feasibility and reliability of the scheme in actual network deployment.

[0010] In an optional implementation, the first strategy is used to determine a target proxy device that meets the following conditions: condition one: the remaining memory space of the target proxy device is not less than the size of the operation and maintenance file; and condition two: among the candidate proxy devices that meet the condition one, the target proxy device is closest to the terminal device in the network level.

[0011] In an optional implementation, if the proxy device selection strategy is the first strategy, the determining, according to the predetermined proxy device selection strategy, of a candidate proxy device as a target proxy device from a plurality of candidate proxy devices on the data transmission path based on the routing information and the size of the operation and maintenance file comprises: starting from a candidate proxy device on the data transmission path that is closest to the terminal device in the network level, querying the candidate proxy devices on the data transmission path layer by layer upwards until the target proxy device is determined, wherein for a currently queried candidate proxy device, the following steps are repeatedly performed: judging whether the remaining memory space of the candidate proxy device is not less than the size of the operation and maintenance file; if the remaining memory space of the candidate proxy device is not less than the size of the operation and maintenance file, the candidate proxy device is determined as the target proxy device, and the remaining memory space of the candidate proxy device is updated; otherwise, a candidate proxy device of the next level is queried.

[0012] In the above scheme, the deterministic execution process of the first strategy corresponding to the bottom-up layer-by-layer query is defined. The process has low computational complexity and can quickly locate the proxy device closest to the terminal and with sufficient memory; that is, under the premise of meeting the storage condition, the process can maximize the shortening of the operation and maintenance file transmission distance of a single terminal device, thereby minimizing the single operation and maintenance delay of the device, and is particularly suitable for single-device emergency operation and maintenance scenarios with high real-time requirements or unstable communication links.

[0013] In an optional implementation, the determining, according to the predetermined proxy device selection strategy, the target proxy device from the plurality of candidate proxy devices on the data transmission path based on the routing information and the size of the operation and maintenance file further comprises: updating, for the currently queried candidate proxy device, the operation and maintenance duration according to the transmission time corresponding to the candidate proxy device, wherein the operation and maintenance duration represents a time required for transmitting the operation and maintenance file from the target proxy device to the terminal device.

[0014] In the above scheme, the abstract path selection process is converted into a specific and predictable time cost metric in real time, thereby providing intuitive progress management and time estimation basis for the operation and maintenance personnel and improving the visualization and controllability of the operation and maintenance process.

[0015] In an optional implementation, the second strategy is used to determine the target proxy device that satisfies the following conditions: condition three: the remaining memory space of the target proxy device is not less than the size of the operation and maintenance file; condition four: an operation and maintenance duration of the operation and maintenance file from the target proxy device to the terminal device is not greater than a transmission duration threshold of the terminal device; and condition five: among the candidate proxy devices that satisfy the condition three and the condition four, the target proxy device is closest to the terminal device in the network level.

[0016] In an optional implementation, if the proxy device selection strategy is the second strategy, the determining, according to the predetermined proxy device selection strategy, the target proxy device from the plurality of candidate proxy devices on the data transmission path based on the routing information and the size of the operation and maintenance file comprises: querying the candidate proxy devices on the data transmission path from the candidate proxy device closest to the terminal device in the network level in the data transmission path to the upper layer until the target proxy device is determined, wherein the following steps are repeatedly performed for the currently queried candidate proxy device: judging whether the remaining memory space of the candidate proxy device is not less than the size of the operation and maintenance file and updating the operation and maintenance duration according to the transmission time corresponding to the candidate proxy device; if the remaining memory space is not less than the size of the operation and maintenance file, marking the candidate proxy device as a first state, wherein the first state represents that the candidate proxy device is available; otherwise, marking the proxy device as a second state, wherein the second state represents that the candidate proxy device is unavailable; judging whether the operation and maintenance duration is greater than the transmission duration threshold; if the operation and maintenance duration is greater than the transmission duration threshold, determining, as the target proxy device, the candidate proxy device closest to the operation and maintenance device in the network level among the candidate proxy devices marked as the first state and updating the remaining memory space of the candidate proxy device; otherwise, querying the candidate proxy device of the upper layer.

[0017] In the above scheme, the second strategy corresponds to a bottom-up layer-by-layer query deterministic execution process, the core of which is to find a proxy device closer to the operation and maintenance side upwards under the premise of meeting the time threshold. This process realizes the aggregation and reuse of operation and maintenance files at higher level nodes. When multiple lower terminal devices share the same upper proxy as the target, the operation and maintenance file only needs to be issued from the cloud once, thereby significantly reducing the repeated traffic and total issuance time of the cloud exit, which is particularly beneficial to the batch upgrade scenario of large-scale terminal devices, and optimizes the utilization efficiency of network bandwidth resources.

[0018] In an optional implementation, if there is no candidate proxy device marked as the first state when the operation and maintenance duration is greater than the transmission duration threshold value, the target proxy device is determined from the multiple candidate proxy devices on the data transmission path according to the predetermined proxy device selection strategy based on the routing information and the size of the operation and maintenance file, and the method further comprises: querying the candidate proxy devices of the upper level until the candidate proxy device with the remaining memory space not less than the size of the operation and maintenance file is found, and the candidate proxy device is determined as the target proxy device.

[0019] In the above scheme, the alternative processing scheme when the upward query times out but no available device is found is specified, that is, the upward query is continued until an available device is found. This ensures the robustness and certainty of the second strategy under harsh network conditions; that is, even in the case where the ideal time threshold cannot be met, the algorithm can still give a feasible solution, ensuring that the operation and maintenance task can be finally arranged and executed, avoiding the interruption of the algorithm due to no solution, and improving the overall fault tolerance of the system.

[0020] In a second aspect, the embodiments of the present application provide a target proxy device determination apparatus, applied to an operation and maintenance device, the operation and maintenance device being configured to remotely operate and maintain at least one terminal device deployed in a multi-layer network architecture, the terminal device being arranged at a power engineering site, and the multi-layer network architecture further comprising a plurality of proxy devices at different levels; the apparatus comprises: an acquisition module configured to acquire, for any terminal device, routing information corresponding to the terminal device, wherein the routing information comprises a level of the terminal device in the multi-layer network architecture, and a file transmission performance parameter of each candidate proxy device on a data transmission path of the terminal device, the data transmission path being a communication link from the operation and maintenance device to the terminal device; and a determination module configured to determine, according to a predetermined proxy device selection strategy, a candidate proxy device from a plurality of candidate proxy devices on the data transmission path as a target proxy device responsible for subsequently issuing an operation and maintenance file to the terminal device based on the routing information and a size of the operation and maintenance file to be issued; wherein the proxy device selection strategy is a first strategy or a second strategy, the first strategy being used to select, from the plurality of candidate proxy devices, a candidate proxy device closest to the terminal device in a network level when a remaining memory space of the candidate proxy device is not less than the size of the operation and maintenance file, and the second strategy being used to select, from the plurality of candidate proxy devices, a candidate proxy device closest to the operation and maintenance device in the network level when the remaining memory space of the candidate proxy device is not less than the size of the operation and maintenance file.

[0021] In the above scheme, by intelligently determining a target proxy device for each terminal device, a complex multi-layer network operation and maintenance path planning problem is decomposed into a local optimal decision based on an explicit strategy. It provides two parallel core strategies (i.e. the first strategy and the second strategy), which provides a preset, computable solution for different operation and maintenance scenarios, which fundamentally overcomes the defect that the prior art cannot efficiently plan an operation and maintenance path in a multi-level, heterogeneous network, and provides a systematic method basis for reducing the overall operation and maintenance time and complexity, and thus fully utilizes the network performance to achieve more efficient remote operation and maintenance.

[0022] In an optional implementation, the file transmission performance parameter comprises: a transmission time required by each candidate proxy device to transmit the operation and maintenance file to a device at a next level, and a remaining memory space of each candidate proxy device.

[0023] In the above scheme, by explicitly defining the file transmission performance parameter as two quantifiable network state indicators, namely transmission time and remaining memory space, the policy decision process has a solid objective data basis. Transmission time is directly related to operation and maintenance efficiency, and remaining memory space determines the carrying capacity of the node. Based on the two, the decision can ensure that the selected target proxy device meets the timeliness requirement and physical storage constraint, significantly improving the feasibility and reliability of the scheme in actual network deployment.

[0024] In an optional implementation, the first policy is used to determine a target proxy device that meets the following conditions: condition one: the remaining memory space of the target proxy device is not less than the size of the operation and maintenance file; and condition two: among the candidate proxy devices that meet the condition one, the target proxy device is closest to the terminal device in the network level.

[0025] In an optional implementation, if the proxy device selection policy is the first policy, the determination module is specifically configured to: start from the candidate proxy device closest to the terminal device in the network level in the data transmission path, query the candidate proxy devices in the data transmission path layer by layer upwards until the target proxy device is determined, wherein for the currently queried candidate proxy device, the following steps are repeatedly executed: judging whether the remaining memory space of the candidate proxy device is not less than the size of the operation and maintenance file; if the remaining memory space of the candidate proxy device is not less than the size of the operation and maintenance file, the candidate proxy device is determined as the target proxy device, and the remaining memory space of the candidate proxy device is updated; otherwise, the candidate proxy device of the upper level is queried.

[0026] In the above scheme, the deterministic execution process of the first policy corresponding to the bottom-up layer-by-layer query is limited. The process has low computational complexity and can quickly locate the proxy device closest to the terminal and with sufficient memory; that is, under the premise of meeting the storage condition, the process can maximize the shortening of the operation and maintenance file transmission distance of a single terminal device, thereby minimizing the single operation and maintenance delay of the device, and is especially suitable for single-device emergency operation and maintenance scenarios with high real-time requirements or unstable communication links.

[0027] In an optional implementation, the determination module is further configured to: for the currently queried candidate proxy device, update the operation and maintenance duration according to the transmission time corresponding to the candidate proxy device, wherein the operation and maintenance duration represents the time required for the operation and maintenance file to be transmitted from the target proxy device to the terminal device.

[0028] In the above scheme, the abstract path selection process is converted into specific and predictable time cost metrics in real time, thereby providing intuitive progress management and time estimation basis for the operation and maintenance personnel, and improving the visualization and controllability of the operation and maintenance process.

[0029] In an optional implementation, the second strategy is used to determine a target agent device that meets the following conditions: condition three: the remaining memory space of the target agent device is not less than the size of the operation and maintenance file; condition four: the operation and maintenance time length of the operation and maintenance file from the target agent device to the terminal device is not greater than the transmission time length threshold of the terminal device; and condition five: among the candidate agent devices that meet the condition three and the condition four, the target agent device is closest to the operation and maintenance device in the network level.

[0030] In an optional implementation, if the agent device selection strategy is the second strategy, the determination module is specifically configured to: start from a candidate agent device closest to the terminal device in the network level in the data transmission path, query the candidate agent devices in the data transmission path layer by layer upwards until the target agent device is determined, wherein for a currently queried candidate agent device, the following steps are repeatedly performed: judging whether the remaining memory space of the candidate agent device is not less than the size of the operation and maintenance file, and updating the operation and maintenance time length according to the transmission time corresponding to the candidate agent device; if the remaining memory space is not less than the size of the operation and maintenance file, marking the candidate agent device as a first state, wherein the first state represents that the candidate agent device is available; otherwise, marking the agent device as a second state, wherein the second state represents that the candidate agent device is unavailable; judging whether the operation and maintenance time length is greater than the transmission time length threshold; if the operation and maintenance time length is greater than the transmission time length threshold, determining a candidate agent device closest to the operation and maintenance device in the network level in the candidate agent devices marked as the first state as the target agent device, and updating the remaining memory space of the candidate agent device; otherwise, querying the candidate agent devices of the upper level.

[0031] In the above scheme, the deterministic execution process of the second strategy corresponding to the bottom-up layer-by-layer query is limited, and the core is to find an agent device closer to the operation and maintenance side upwards on the premise of meeting the time threshold. The process realizes the aggregation and reuse of operation and maintenance files at higher level nodes. When multiple lower terminal devices share the same upper agent as the target, the operation and maintenance file only needs to be issued from the cloud once, thereby significantly reducing the repeated traffic and total issuing time of the cloud outlet, which is particularly beneficial to the batch upgrade scene of large-scale terminal devices, and optimizes the utilization efficiency of network bandwidth resources.

[0032] In an optional implementation, if there is no candidate proxy device marked as the first state when the operation and maintenance duration is greater than the transmission duration threshold value, the determination module is further configured to: query a candidate proxy device at a previous level until a candidate proxy device with a remaining memory space not less than a size of the operation and maintenance file is found, and determine the candidate proxy device as the target proxy device.

[0033] In the above scheme, an alternative processing scheme is specified when an available device is not found after an upward query times out, i.e., the upward query is continued until an available device is found. This ensures the robustness and solvability of the second strategy under harsh network conditions; that is, even if the ideal time threshold cannot be met, the algorithm can still give a feasible solution, ensuring that the operation and maintenance task can be finally arranged and executed, avoiding the interruption of the algorithm due to no solution, and improving the overall fault tolerance of the system.

[0034] In a third aspect, an embodiment of the present application provides a multi-layer network architecture, comprising: an operation and maintenance device configured to execute the method for determining a target proxy device according to the first aspect; a plurality of proxy devices at different levels; and at least one terminal device.

[0035] In a fourth aspect, an embodiment of the present application provides a computer program product, comprising computer program instructions, which, when read and executed by a processor, perform the method for determining a target proxy device according to the first aspect.

[0036] In a fifth aspect, an embodiment of the present application provides an operation and maintenance device, comprising: a processor, a memory and a bus; the processor and the memory complete mutual communication through the bus; the memory stores computer program instructions executable by the processor, and the processor calling the computer program instructions can execute the method for determining a target proxy device according to the first aspect.

[0037] In a sixth aspect, an embodiment of the present application provides a computer readable storage medium, which stores computer program instructions, and the computer program instructions, when executed by a computer, cause the computer to execute the method for determining a target proxy device according to the first aspect.

[0038] In order to make the above objectives, characteristics and advantages of the present application more apparent and easy to understand, the following describes embodiments of the present application in detail, and the accompanying drawings are referred to, as follows. BRIEF DESCRIPTION OF DRAWINGS

[0039] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments of the present application. It should be understood that the following drawings only show some embodiments of the present application, and therefore should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can also be obtained without creative labor on the basis of these drawings.

[0040] Figure 1 A structural schematic diagram of a multi-layer network architecture provided by the embodiments of the present application; Figure 2 A flowchart of a method for determining a target proxy device provided by the embodiments of the present application; Figure 3 A flowchart of a method for determining a target proxy device corresponding to a first policy provided by the embodiments of the present application; Figure 4 A flowchart of a method for determining a target proxy device corresponding to a second policy provided by the embodiments of the present application; Figure 5 A structural block diagram of a device for determining a target proxy device provided by the embodiments of the present application; Figure 6 A structural block diagram of an operation and maintenance device provided by the embodiments of the present application. DETAILED DESCRIPTION

[0041] In the application process of power engineering, when performing operation and maintenance on terminal devices, the following three difficulties will be encountered, greatly increasing the operation and maintenance difficulty and operation and maintenance cycle: 1. The distribution range of terminal devices is scattered (for example, in the scene of connecting new energy devices in Hubei, each device is distributed on each rural residential house, and the distance between villages is dozens of kilometers); 2. It is not convenient to take down the terminal device after installation (for example, the user needs to operate power off); 3. The terminal device is in a sleep state for a long time (for example, a battery-powered sensor device in a substation).

[0042] In the face of these situations, there are generally three remote operation and maintenance schemes: 1. Directly using a public network to connect terminal devices with an operation and maintenance device (or integrating an operation and maintenance server in a cloud server) to realize remote operation and maintenance of terminal devices (for example, intelligent automobile OTA service); 2. Using a gateway device to connect terminal devices with an operation and maintenance device (or integrating an operation and maintenance server in a cloud server) to realize remote operation and maintenance of terminal devices (for example, software wireless update (Over-the-Air, OTA) service of intelligent household appliances); 3. Using a gateway device to save the operation and maintenance files of terminal devices in the gateway device, and realizing remote operation and maintenance of terminal devices after the device is online (for example, using a communication machine to upgrade a sensor terminal in a substation).

[0043] However, the above three remote operation and maintenance solutions can generally only be applied to scenarios in which there is no multi-level data forwarding device in the network architecture (for example, a sensor directly accesses a cloud server or a gateway device). When there is a multi-level data forwarding device, or even multiple fusion communication technologies exist between data forwarding devices (for example, in the Hubei new energy device access scenario, there are high-speed power line carrier (HPLC) communication and long range (LoRa) communication between the QY-6183 device and the system control unit (SCU) device), the above remote operation and maintenance solutions cannot meet the data transmission requirements in the remote operation and maintenance process.

[0044] In view of this, the embodiments of the present application provide a method for determining a target proxy device. In a scenario in which a terminal device and an operation and maintenance device do not communicate in real time, a layer of multi-layer proxy devices is selected as a target proxy device for performing operation and maintenance according to a pre-determined proxy device selection strategy based on multi-layer routing information obtained from the terminal device, thereby achieving more efficient remote operation and maintenance by utilizing network performance. The pre-determined proxy device selection strategy can include a first strategy and a second strategy. The first strategy is used to select a proxy device closest to the terminal device in the network hierarchy from the multi-layer proxy devices, and the second strategy is used to select a proxy device closest to the operation and maintenance device in the network hierarchy from the multi-layer proxy devices.

[0045] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

[0046] First, a multi-layer network architecture related to the embodiments of the present application will be introduced. Please refer to Figure 1 , Figure 1 A structural schematic diagram of a multi-layer network architecture provided by the embodiments of the present application. The multi-layer network architecture refers to a communication network with a hierarchical relationship established for connecting numerous terminal devices in a power engineering site (such as a substation or a distributed new energy site), and data needs to be forwarded through multiple layers before reaching the target. In the embodiments of the present application, the multi-layer network architecture can include an operation and maintenance device, multiple proxy devices located at different levels, and at least one terminal device.

[0047] The operation and maintenance device refers to an entity that initiates and manages a remote operation and maintenance task, and has the topology information and decision-making capability of the entire network. In actual deployment, it is usually one or more servers (i.e., operation and maintenance servers) deployed in a data center or cloud for running operation and maintenance management software, and has sufficient computing resources, storage resources, and network bandwidth. For example, in a small system, the operation and maintenance device can also be a special computer directly operated by an operation and maintenance personnel. In the embodiments of the present application, the operation and maintenance device is used to perform a target agent device determination method, and the specific implementation of the target agent device determination method will be described in detail in subsequent embodiments, which will not be described here.

[0048] The hierarchy refers to the vertical position number of the device in the multi-layer network architecture. For example, a first-layer agent device can be defined, the next level of which is a second-layer agent device, and so on, until the terminal device of the last layer. In the embodiments of the present application, a plurality of agent devices are located at different levels of the multi-layer network architecture, for example, one agent device at the first layer, two agent devices at the second layer, one agent device at the third layer, three agent devices at the fourth layer, and so on.

[0049] The agent device refers to a network node located between the operation and maintenance device and the terminal device, which has certain data storage and forwarding capability, and is responsible for data uplink convergence and downlink distribution. In the embodiments of the present application, the agent device is mainly used to store and forward operation and maintenance files. For example, the agent device can be one or more of a cloud server, a gateway device, and a data forwarding device, and the number of each device can be adjusted according to actual conditions. For example, the multi-layer network architecture includes ten data forwarding devices and one cloud server.

[0050] The terminal device refers to various devices deployed at the end of the power engineering site and needing to be operated and maintained, which are used to perform the final business function. For example, the operation and maintenance device can operate and maintain one or more (for example, batch upgrade, etc.) terminal devices. It should be noted that the specific implementation of the terminal device is not limited in the embodiments of the present application, and those skilled in the art can make appropriate adjustments according to actual conditions, for example, smart meters, environmental sensors, intelligent circuit breakers, and charging pile controllers.

[0051] Figure 1 In the shown multi-layer network architecture, the first layer includes one terminal device (i.e., a to-be-operated device), the second layer to the fourth layer include a total of three terminal devices (i.e., to-be-operated devices), the second layer to the fourth layer include a total of three data forwarding devices (i.e., operation and maintenance agent devices), and the first layer includes a cloud server or a gateway device. The first layer includes one terminal device (i.e., a to-be-operated device), the second layer to the fourth layer include a total of three terminal devices (i.e., to-be-operated devices), the second layer to the fourth layer include a total of three data forwarding devices (i.e., operation and maintenance agent devices), and the first layer includes a cloud server or a gateway device. The first layer includes one terminal device (i.e., a to-be-operated device), the second layer to the fourth layer include a total of three terminal devices (i.e., to-be-operated devices), the second layer to the fourth layer include a total of three data forwarding devices (i.e., operation and maintenance agent devices), and the first layer includes a cloud server or a gateway device. The first layer includes one terminal device (i.e., a to-be-operated device), the second layer to the fourth layer include a total of three terminal devices (i.e., to-be-operated devices), the second layer to the fourth layer include a total of three data forwarding devices (i.e., operation and maintenance agent devices), and the first layer includes a cloud server or a gateway device. The first layer includes one terminal device (i.e., a to-be-operated device), the second layer to the fourth layer include a total of three terminal devices (i.e., to-be-operated devices), the second layer to the fourth layer include a total of three data forwarding devices (i.e., operation and maintenance agent devices), and the first layer includes a cloud server or a gateway device.

[0052] Based on the above multi-layer network architecture, there are generally two scenarios: the first scenario is that the operation and maintenance device communicates with the terminal device in real time, for example, the terminal device is online in real time, and the operation and maintenance time is short; the second scenario is that the operation and maintenance device does not communicate with the terminal device in real time, for example, the terminal device is in a sleep state for a long time and cannot directly communicate with the operation and maintenance device; the terminal device is online in real time, but the communication link causes the operation and maintenance time to be long; due to information security or cost problems, the operation and maintenance device cannot directly communicate with each terminal device during batch upgrading.

[0053] For the above first scenario (i.e., the operation and maintenance device communicates with the terminal device in real time), since the operation and maintenance device can communicate with the terminal device in real time, the operation and maintenance channel can be directly established, thereby realizing remote operation and maintenance of the terminal device.

[0054] For the above second scenario (i.e., the operation and maintenance device does not communicate with the terminal device in real time), since the operation and maintenance device does not communicate with the terminal device in real time, the file that needs to be operated and maintained can be downloaded to the proxy device (such as the proxy device in Figure 1 , and the remote operation and maintenance of the terminal device is completed by the proxy device. Therefore, in this scenario, the target proxy device for remotely operating and maintaining the terminal device needs to be determined.

[0055] The method for determining the target proxy device provided by the embodiments of the present application will be introduced below. As an implementation manner, when the operation and maintenance device needs to operate and maintain one or more terminal devices, it is first judged whether real-time connection can be used, and if not, the method for determining the target proxy device provided by the embodiments of the present application is executed; as another implementation manner, when the operation and maintenance device needs to operate and maintain one or more terminal devices, the method for determining the target proxy device provided by the embodiments of the present application can also be directly executed.

[0056] Please refer to Figure 2 , Figure 2 the flowchart of the method for determining the target proxy device provided by the embodiments of the present application. The method can be, but is not limited to, executed by an operation and maintenance device, Figure 6 the possible structure of the operation and maintenance device is shown, and specific reference can be made to the description of Figure 6 below. The method for determining the target proxy device can specifically include: S101: For any terminal device, the routing information corresponding to the terminal device is obtained.

[0057] For convenience of description, the operation and maintenance scenario is set as follows: there are terminal devices in the power engineering field that need to be operated and maintained, and the operation and maintenance file size of each terminal device is ( ).

[0058] The routing information refers to a set of information describing how a terminal device is connected to the operation and maintenance device through the network, which not only includes a path, but also includes the status of each node on the path. For example, the routing information can include the level of the terminal device in the multi-layer network architecture, and the file transmission performance parameters of each candidate proxy device on the data transmission path of the terminal device. Among them, the data transmission path refers to a complete and orderly communication link from the operation and maintenance device to a certain terminal device through a series of proxy devices; the file transmission performance parameter is used to quantitatively evaluate the index of the processing ability of the operation and maintenance file of each candidate proxy device, for example: the transmission time required by each candidate proxy device to transmit the operation and maintenance file to the next level device, the remaining memory space of each candidate proxy device, etc.

[0059] Among them, the transmission time refers to the estimated time required to complete the transmission of a specific size of operation and maintenance file from the current proxy device to the next level device through the communication link between them; for example, the transmission time can be calculated according to the historical transmission rate, the current network condition and the file size. The remaining memory space refers to the size of the non-volatile storage space currently available to the proxy device, which is used to determine whether the entire operation and maintenance file can be stored.

[0060] For example, the terminal device The corresponding routing information includes: the level of the terminal device wherein the terminal device is located , the time required by each layer proxy device (the first layer) on the path of the terminal device to transmit the operation and maintenance file ( ), and the remaining memory space of each layer proxy device (the first layer) on the path of the terminal device .

[0061] It should be noted that the specific implementation of the operation and maintenance device obtaining the routing information corresponding to the terminal device is not limited in the embodiments of the present application, and those skilled in the art can make appropriate adjustments according to the actual situation. For example, the operation and maintenance device can query and extract the routing information of the terminal device from the network topology database and the state monitoring system maintained by it; or the operation and maintenance device can also receive the routing information of the terminal device sent by other devices, etc.

[0062] ​​For each terminal device in the list, the operation and maintenance device queries and extracts routing information of the device from a network topology database and a state monitoring system maintained by the operation and maintenance device. The routing information includes a level (for example, Layer 3) of the terminal device itself and a transmission time and a remaining memory of each proxy device on a path from the terminal device back to the operation and maintenance device.

[0063] S102: According to a predetermined proxy device selection strategy, a candidate proxy device is determined as a target proxy device responsible for subsequent delivery of the operation and maintenance file to the terminal device from the multiple candidate proxy devices on the data transmission path based on the routing information and a size of the operation and maintenance file to be delivered.

[0064] The proxy device selection strategy refers to a set of rules or algorithms defined in advance and used to guide how to select the most suitable target proxy device from the multiple candidate proxy devices. Two fixed strategies are provided in the embodiments of the present application: a first strategy and a second strategy, that is, the proxy device selection strategy is the first strategy or the second strategy.

[0065] The first strategy is a decision rule with a core target of minimizing single-device operation and maintenance delay. Specifically, the first strategy is used to determine a target proxy device that meets the following conditions: condition one: a remaining memory space of the target proxy device is not less than a size of the operation and maintenance file; and condition two: among the candidate proxy devices meeting the condition one, the target proxy device is closest to the terminal device in a network level.

[0066] The second strategy is a decision rule with a core target of maximizing file reuse and reducing total delivery amount within an acceptable time threshold. Specifically, the second strategy is used to determine a target proxy device that meets the following conditions: condition three: a remaining memory space of the target proxy device is not less than a size of the operation and maintenance file; condition four: an operation and maintenance time for transmission of the operation and maintenance file from the target proxy device to the terminal device is not greater than a transmission time threshold value of the terminal device; and condition five: among the candidate proxy devices meeting the condition three and the condition four, the target proxy device is closest to the operation and maintenance device in the network level.

[0067] The operation and maintenance file refers to a file that needs to be delivered to the terminal device by a remote mode, for example, a firmware upgrade package, a configuration file, a diagnostic command script, etc. The candidate proxy device refers to all proxy devices on a data transmission path for a specific terminal device. The target proxy device refers to a proxy device finally selected to store and forward the operation and maintenance file for a specific terminal device through the method for determining the target proxy device provided in the embodiments of the present application.

[0068] It can be understood that the above specific proxy device selection strategy can be determined and configured in the operation and maintenance device in the implementation of the operation and maintenance process; then, according to the proxy device selection strategy, combined with the obtained routing information and the size of the specific operation and maintenance file to be delivered, the corresponding decision algorithm is run; wherein the decision algorithm can traverse the candidate proxy device on the terminal device path, evaluate and screen according to the conditions set by the strategy, and finally determine the target proxy device.

[0069] In the above scheme, by intelligently determining a target proxy device for each terminal device, the complex multi-layer network operation and maintenance path planning problem is decomposed into a local optimal decision based on a clear strategy. It provides two parallel core strategies (i.e. the first strategy and the second strategy), which provides a preset, computable solution for different operation and maintenance scenarios, which fundamentally overcomes the defects of the prior art that cannot efficiently plan operation and maintenance paths in multi-level, heterogeneous networks, provides a systematic method basis for reducing the overall operation and maintenance time and complexity, and further makes full use of network performance to achieve more efficient remote operation and maintenance.

[0070] The decision algorithm corresponding to the first strategy is introduced below, that is, if the proxy device selection strategy is the first strategy, S102 can specifically include: Starting from the candidate proxy device closest to the terminal device in the network level in the data transmission path, querying the candidate proxy device in the data transmission path layer by layer upwards until the target proxy device is determined, wherein for the currently queried candidate proxy device, the following steps are repeatedly executed: S201: Determine whether the remaining memory space of the candidate proxy device is not less than the size of the operation and maintenance file.

[0071] S202: If the remaining memory space of the candidate proxy device is not less than the size of the operation and maintenance file, the candidate proxy device is determined as the target proxy device, and the remaining memory space of the candidate proxy device is updated; otherwise, the candidate proxy device of the upper level is queried.

[0072] Specifically, for the terminal device currently being processed , find the candidate proxy device at the end of its data transmission path, that is, the one closest to itself (level ), and set it as the current query node; read the remaining memory space of the current query node, and determine whether it is true. If is true (i.e. the remaining memory space of the candidate proxy device is not less than the size of the operation and maintenance file), the query is immediately terminated, and the current query node is determined as the target proxy device serving the terminal device , and the remaining memory value of the node is updated to ; if If not (i.e., the remaining memory space of the candidate proxy device is less than the size of the operation and maintenance file), the query node is moved to the last candidate proxy device on the path, and then step S201 and step S202 are re-executed. When the target proxy device is found, the decision-making process of the terminal device ends.

[0073] Therefore, the decision-making algorithm corresponding to the first strategy ensures that the determined target proxy device is the first (counted from the terminal device) candidate proxy device that meets the memory condition, i.e., the candidate proxy device closest to the terminal.

[0074] In the above scheme, the deterministic execution process of the first strategy corresponding to the bottom-up layer-by-layer query is limited. The process has low computational complexity and can quickly locate the proxy device closest to the terminal and having sufficient memory; that is, under the premise of meeting the storage condition, the process can maximize the shortening of the transmission distance of the operation and maintenance file of a single terminal device, thereby minimizing the single operation and maintenance delay of the device, and is particularly suitable for single-device emergency operation and maintenance scenarios with high real-time requirements or unstable communication links.

[0075] Further, on the basis of the above embodiment, the S102 can further include: S301: For the currently queried candidate proxy device, updating the operation and maintenance duration according to the transmission time corresponding to the candidate proxy device.

[0076] Specifically, the S301 is an enhancement of the decision-making algorithm process corresponding to the first strategy, i.e., the time cost is calculated synchronously during the query process. The operation and maintenance duration represents the time required for the operation and maintenance file to be transmitted from the target proxy device to the terminal device.

[0077] When starting to perform operation and maintenance for the terminal device Before querying, initializing the operation and maintenance time ; When a new level of candidate proxy device is queried each time (before or after checking the memory), the transmission time of the level is first accumulated to , i.e. At this time, the represents the total time required for the operation and maintenance file to be transmitted from the candidate proxy device to the terminal device if the candidate proxy device of the current level or a lower level is selected as the target proxy device. When the target proxy device is finally selected according to the memory condition, the accumulated value at this time is the accurate operation and maintenance duration.

[0078] In the above scheme, the abstract path selection process is converted into a specific and predictable time cost measure in real time, thereby providing intuitive progress management and time estimation basis for the operation and maintenance personnel, and improving the visualization and controllability of the operation and maintenance process.

[0079] Please refer to Figure 3 , Figure 3 A flowchart illustrating a method for determining the target agent device corresponding to the first strategy provided in this application embodiment. (Total...) Each terminal device requires maintenance; each terminal device The sizes of the operation and maintenance files are respectively ( ); let terminal device serial number The expected total time for initial operation and maintenance is Poll the terminal devices sequentially : Step 1), Read terminal device The routing table is used to obtain the terminal device. Routing information.

[0080] Step 2), query upwards from the bottom layer... layer( Candidate agent devices, recording maintenance time. and initialize .

[0081] Step 3), the first The file transfer time for layer candidate agent devices is added to the total maintenance time. .

[0082] Step 4), determine the first Layer candidate agent device memory Is there enough space to store maintenance files? :if If so, it means that the candidate agent device in this layer has enough memory to store the operation and maintenance files, proceed to step 5); if This indicates that the candidate agent device in this layer has insufficient memory and needs to be queried from the next higher layer. Then proceed to step 3).

[0083] Step 5), record the terminal device. The corresponding number The candidate agent device at layer 1 is the target agent device; update the layer 2. Remaining memory for candidate agent devices at the layer Update the total expected maintenance duration. .

[0084] Step 6), poll the next device (i.e. Repeat steps 1) through 5) until a target agent device has been identified for all terminal devices, then proceed to step 7).

[0085] Step 7) Output the target agent device for maintenance of each terminal device and the total expected maintenance time.

[0086] The decision algorithm corresponding to the second strategy is described below. If the agent device selects the second strategy, then the above S102 may specifically include: Starting with the candidate proxy device that is closest to the terminal device at the network layer in the data transmission path, query the candidate proxy devices in the data transmission path layer by layer upwards until the target proxy device is determined. For the currently queried candidate proxy device, repeat the following steps: S401: Determine whether the remaining memory space of the candidate agent device is not less than the size of the maintenance file, and update the maintenance duration according to the transmission time corresponding to the candidate agent device.

[0087] S402: If the remaining memory space is not less than the size of the operation and maintenance file, mark the candidate agent device as the first state; otherwise, mark the agent device as the second state.

[0088] S403: Determine whether the maintenance time exceeds the transmission time threshold.

[0089] S404: If the maintenance duration exceeds the transmission duration threshold, the candidate proxy device that is closest to the maintenance device at the network layer among the candidate proxy devices marked as first state is determined as the target proxy device, and the remaining memory space of the candidate proxy device is updated; otherwise, the candidate proxy device at the next higher level is queried.

[0090] Specifically, for the terminal devices currently being processed... Find the candidate proxy device at the very end of its data transmission path, that is, the one closest to it (at the level of...). Set it as the current query node; read the remaining memory space of the current query node. and judge Is it valid?; Update maintenance duration .if If the condition is met (i.e., the remaining memory space of the candidate agent device is not less than the size of the operation and maintenance file), then the current queried node is marked as the first state, where the first state indicates that the candidate agent device corresponding to the current queried node is available; if If the condition is not met (i.e., the remaining memory space of the candidate agent device is less than the size of the operation and maintenance file), then the current query node is marked as the second state, where the second state indicates that the candidate agent device corresponding to the current query node is unavailable.

[0091] judge Whether it is valid; among which, the transmission duration threshold. is the maximum time limit of a single file transfer that can be accepted for each terminal device, usually determined by service requirements (e.g. 3 minutes, etc.), The greater the value, the longer the terminal device is allowed to transfer files. If the condition is met, stop querying upwards and query all candidate proxy devices in the level where the current query node is located, starting from the lower level (i.e. the level closer to the terminal device) that has been queried, to find out which candidate proxy devices are marked in the first state; if there are candidate proxy devices marked in the first state, select the candidate proxy device with the largest level number (i.e. the uppermost, farthest from the terminal device) as the target proxy device, and update the remaining memory value of the node to ; if there are no candidate proxy devices marked in the first state, execute the backup process in the subsequent embodiments.

[0092] If the condition is not met, there is still a time margin, move the query node to the previous layer of candidate proxy devices on the path, and then re-execute steps S401 to S404.

[0093] In the above scheme, the deterministic execution process of the second strategy corresponding to the bottom-up layer-by-layer query is limited, and the core is to find a proxy device closer to the operation and maintenance side upwards under the premise of meeting the time threshold. This process realizes the aggregation and reuse of operation and maintenance files in higher level nodes. When multiple lower terminal devices share the same upper proxy as the target, the operation and maintenance file only needs to be downloaded from the cloud once, thereby significantly reducing the repeated traffic and total download time of the cloud outlet, which is particularly beneficial to the batch upgrade scenario of large-scale terminal devices, and optimizes the utilization efficiency of network bandwidth resources.

[0094] The backup process when there is no candidate proxy device marked in the first state will be introduced below, i.e. if there is no candidate proxy device marked in the first state when the operation and maintenance time is greater than the transmission time threshold value, S102 can also include: S501: Query the candidate proxy devices of the previous level until a candidate proxy device with a remaining memory space not less than the size of the operation and maintenance file is found, and determine the candidate proxy device as the target proxy device.

[0095] Specifically, when the condition is met, but there is no candidate proxy device marked in the first state from the lower level, the decision algorithm is not terminated, but the state of the current is ignored, and the query is continued to the upper layer candidate proxy device. For each layer of candidate proxy devices in the subsequent query, only two operations are performed: adding the transmission time of the layer to , and judging whether the memory of the candidate proxy device of the layer meets the condition . ​ Once a candidate agent device at a certain layer is found to meet the requirements... Immediately identify it as the target agent device, and simultaneously update the remaining memory value of that node to... .

[0096] The above scheme specifies an alternative handling method when the upward query times out and no available device is found, namely, continuing to query upwards until an available device is found. This ensures the robustness and solvability of the second strategy under harsh network conditions; that is, even if the ideal time threshold cannot be met, the algorithm can still provide a feasible solution, ensuring that the operation and maintenance task can eventually be scheduled and executed, avoiding algorithm interruption due to lack of a solution, and improving the overall fault tolerance of the system.

[0097] Please refer to Figure 4 , Figure 4 A flowchart illustrating the method for determining the target agent device corresponding to the second strategy provided in this application embodiment. (Total...) Each terminal device requires maintenance; each terminal device The sizes of the operation and maintenance files are respectively ( ); let terminal device serial number The expected total time for initial operation and maintenance is Poll the terminal devices sequentially : Step 1), Read terminal device The routing table is used to obtain the terminal device. Routing information.

[0098] Step 2), query upwards from the bottom layer... layer( Candidate agent devices, recording maintenance time. and initialize .

[0099] Step 3), determine the first Layer candidate agent device memory Is there enough space to store maintenance files? :if This indicates that the candidate agent device at this layer has sufficient memory to store operation and maintenance files and record the first... The candidate agent device at the layer is "available"; if This indicates that the proxy device at this layer has insufficient memory, and the record is incomplete. The candidate agent device for the layer is "unavailable".

[0100] Step 4), the first The file transfer time for layer candidate agent devices is added to the total maintenance time. And determine the operation and maintenance time And the relationship with the transmission time threshold value: if , it means that the operation and maintenance time has exceeded the threshold value, and step 5) is entered; if , it means that the operation and maintenance time still has room for increase, and it can be tried to query the upper layer again, that is , and then step 3) is entered.

[0101] Step 5), query whether there is a "available" agent in the first layer to the first layer: if there is, it means that the terminal device operation and maintenance file transmission time meets the threshold requirement, and step 6) needs to find the candidate agent device of the corresponding layer; if not, it means that the first layer to the first layer does not have enough memory to store the terminal device operation and maintenance file, although it does not meet the transmission time threshold value requirement, it can only choose to continue to try to query the upper layer again, that is , and then step 3) is entered.

[0102] Step 6), query whether there is a "available" agent in the first layer to the first layer: if there is, it means that the terminal device operation and maintenance file transmission time meets the threshold requirement, and the uppermost device (i.e., the device with the largest number of layers, recorded as the first layer) in the "available" candidate agent device needs to be found. The first layer is selected as the target agent device, the operation and maintenance expected time is calculated, and then step 7) is entered; if not, it means that only the first layer has enough storage space in the first layer to the first layer, and the shortest transmission time of the terminal device operation and maintenance file is , although it does not meet the transmission time threshold value requirement, it can only choose the first layer candidate agent device as the target agent device (i.e. ) of the terminal device , and step 7) is entered.

[0103] Step 7), record that the first layer candidate agent device is selected to perform operation and maintenance on the terminal device , update the remaining memory of the first layer candidate agent device, and update the operation and maintenance expected total time . ​

[0104] Step 8), polling the next device (i.e. ), repeating steps 1) to 7); until the target proxy device is determined for all terminal devices, entering step 9).

[0105] Step 9), outputting the target proxy device for each terminal device and the expected total time for operation and maintenance.

[0106] Please refer to Figure 5 , Figure 5 A structural block diagram of a target proxy device determination apparatus provided by the embodiment of the present application is provided, which is applied to an operation and maintenance device and can specifically include: an acquisition module 601 configured to acquire, for any terminal device, routing information corresponding to the terminal device, wherein the routing information includes a level of the terminal device in the multi-layer network architecture and a file transmission performance parameter of each candidate proxy device on a data transmission path of the terminal device, and the data transmission path is a communication link from the operation and maintenance device to the terminal device; a determination module 602 configured to determine, according to a pre-determined proxy device selection strategy, a candidate proxy device as a target proxy device responsible for subsequent delivery of an operation and maintenance file to the terminal device based on the routing information and a size of the operation and maintenance file from a plurality of candidate proxy devices on the data transmission path; wherein the proxy device selection strategy is a first strategy or a second strategy, the first strategy is used to select a candidate proxy device closest to the terminal device in a network level from the plurality of candidate proxy devices when the remaining memory space is not less than the size of the operation and maintenance file, and the second strategy is used to select a candidate proxy device closest to the operation and maintenance device in a network level from the plurality of candidate proxy devices when the remaining memory space is not less than the size of the operation and maintenance file.

[0107] In the above scheme, a target proxy device is intelligently determined for each terminal device, and a complex multi-layer network operation and maintenance path planning problem is decomposed into a local optimal decision based on an explicit strategy. Two parallel core strategies (i.e. the first strategy and the second strategy) are provided, which provide a pre-set, calculable solution for different operation and maintenance scenarios, which fundamentally overcomes the defect that the prior art cannot efficiently plan an operation and maintenance path in a multi-level, heterogeneous network, provides a systematic method basis for reducing the overall operation and maintenance time and complexity, and further makes full use of network performance to achieve more efficient remote operation and maintenance.

[0108] Further, in the above embodiment, the file transmission performance parameter includes: a transmission time required by each candidate proxy device to transmit the operation and maintenance file to a device of a next level, and a remaining memory space of each candidate proxy device.

[0109] In the above scheme, by explicitly defining the file transmission performance parameter as two quantifiable network state indicators, namely transmission time and remaining memory space, the policy decision process has a solid objective data basis. Transmission time is directly related to operation and maintenance efficiency, and remaining memory space determines the carrying capacity of the node. Based on the two, the decision can ensure that the selected target proxy device meets the timeliness requirement and physical storage constraint, significantly improving the feasibility and reliability of the scheme in actual network deployment.

[0110] Further, on the basis of the above embodiment, the first strategy is used to determine a target proxy device that satisfies the following conditions: condition one: the remaining memory space of the target proxy device is not less than the size of the operation and maintenance file; condition two: among the candidate proxy devices that satisfy the condition one, the target proxy device is closest to the terminal device in the network level.

[0111] Further, on the basis of the above embodiment, if the proxy device selection strategy is the first strategy, the determination module 602 is specifically configured to: starting from the candidate proxy device closest to the terminal device in the network level in the data transmission path, query the candidate proxy devices in the data transmission path layer by layer upwards until the target proxy device is determined, wherein for the currently queried candidate proxy device, the following steps are repeatedly executed: judging whether the remaining memory space of the candidate proxy device is not less than the size of the operation and maintenance file; if the remaining memory space of the candidate proxy device is not less than the size of the operation and maintenance file, the candidate proxy device is determined as the target proxy device, and the remaining memory space of the candidate proxy device is updated; otherwise, the candidate proxy device of the upper level is queried.

[0112] In the above scheme, the deterministic execution process of the first strategy corresponding to the self-bottom-to-top layer-by-layer query is limited. This process has low computational complexity and can quickly locate the proxy device closest to the terminal and with sufficient memory; that is, under the premise of meeting the storage condition, this process can maximize the shortening of the operation and maintenance file transmission distance of a single terminal device, thereby minimizing the single operation and maintenance delay of the device, and is especially suitable for single-device emergency operation and maintenance scenarios with high real-time requirements or unstable communication links.

[0113] Further, on the basis of the above embodiment, the determination module 602 is further configured to: for the currently queried candidate proxy device, updating the operation and maintenance duration according to the transmission time corresponding to the candidate proxy device, wherein the operation and maintenance duration represents the time required for the operation and maintenance file to be transmitted from the target proxy device to the terminal device.

[0114] In the above scheme, the abstract path selection process is converted into specific and predictable time cost metrics in real time, thereby providing intuitive progress management and time estimation basis for operation and maintenance personnel, and improving the visualization and controllability of the operation and maintenance process.

[0115] Further, on the basis of the above embodiment, the second strategy is used to determine the target agent device that meets the following conditions: condition three: the remaining memory space of the target agent device is not less than the size of the operation and maintenance file; condition four: the operation and maintenance time length of the operation and maintenance file from the target agent device to the terminal device is not greater than the transmission time length threshold of the terminal device; and condition five: among the candidate agent devices that meet the condition three and the condition four, the target agent device is closest to the operation and maintenance device in the network level.

[0116] Further, on the basis of the above embodiment, if the agent device selection strategy is the second strategy, the determination module 602 is specifically configured to: start from the candidate agent device closest to the terminal device in the network level in the data transmission path, query the candidate agent devices in the data transmission path layer by layer upwards until the target agent device is determined, wherein for the currently queried candidate agent device, the following steps are repeatedly executed: judging whether the remaining memory space of the candidate agent device is not less than the size of the operation and maintenance file, and updating the operation and maintenance time length according to the transmission time corresponding to the candidate agent device; if the remaining memory space is not less than the size of the operation and maintenance file, marking the candidate agent device as a first state, wherein the first state represents that the candidate agent device is available; otherwise, marking the agent device as a second state, wherein the second state represents that the candidate agent device is unavailable; judging whether the operation and maintenance time length is greater than the transmission time length threshold; if the operation and maintenance time length is greater than the transmission time length threshold, determining the candidate agent device closest to the operation and maintenance device in the network level among the candidate agent devices marked as the first state as the target agent device, and updating the remaining memory space of the candidate agent device; otherwise, querying the candidate agent device of the upper level.

[0117] In the above scheme, the second strategy corresponds to the deterministic execution process of querying layer by layer from bottom to top, and the core is to find the agent device closer to the operation and maintenance side upwards under the premise of meeting the time threshold. This process realizes the aggregation and reuse of operation and maintenance files at higher level nodes. When multiple lower terminal devices share the same upper agent as the target, the operation and maintenance file only needs to be issued from the cloud once, thereby significantly reducing the repeated traffic and total issuing time of the cloud outlet, which is particularly beneficial to the batch upgrade scene of large-scale terminal devices, and optimizes the utilization efficiency of network bandwidth resources.

[0118] Further, on the basis of the above embodiment, if there is no candidate proxy device marked as the first state when the operation and maintenance duration is greater than the transmission duration threshold value, the determination module 602 is further configured to: query a candidate proxy device of an upper level until a candidate proxy device with a remaining memory space not less than the size of the operation and maintenance file is found, and determine the candidate proxy device as the target proxy device.

[0119] In the above scheme, an alternative processing scheme is specified when an available device is not found after querying upwards, that is, continue to query upwards until an available device is found. This ensures the robustness and solvability of the second strategy under harsh network conditions; that is, even if the ideal time threshold cannot be met, the algorithm can still give a feasible solution, ensuring that the operation and maintenance task can be finally arranged and executed, avoiding the interruption of the algorithm due to no solution, and improving the overall fault tolerance of the system.

[0120] Please refer to Figure 6 , Figure 6 A structural block diagram of an operation and maintenance device is provided in the embodiments of the present application, and the operation and maintenance device 700 includes at least one processor 701, at least one communication interface 702, at least one memory 703, and at least one communication bus 704. The communication bus 704 is used to realize direct connection communication of these components, the communication interface 702 is used for signaling or data communication with other node devices, and the memory 703 stores machine readable instructions executable by the processor 701. When the operation and maintenance device 700 is running, the processor 701 and the memory 703 communicate through the communication bus 704, and the machine readable instructions are executed by the processor 701 when called.

[0121] For example, the processor 701 of the embodiments of the present application reads the computer program from the memory 703 through the communication bus 704 and executes the computer program to implement the following method: for any terminal device, obtain the routing information corresponding to the terminal device, wherein the routing information includes the level of the terminal device in the multi-layer network architecture, and the file transmission performance parameter of each candidate proxy device on the data transmission path of the terminal device, the data transmission path being a communication link from the operation and maintenance device to the terminal device; according to a predetermined proxy device selection strategy, based on the routing information and the size of the operation and maintenance file to be issued, determine a candidate proxy device from the multiple candidate proxy devices on the data transmission path as a target proxy device responsible for subsequently issuing the operation and maintenance file to the terminal device.

[0122] The processor 701 includes one or more, which can be an integrated circuit chip having a processing capability of signals. The processor 701 described above can be a general-purpose processor, including a central processing unit (CPU), a micro controller unit (MCU), a network processor (NP), or other conventional processors; it can also be a special-purpose processor, including a neural-network processing unit (NPU), a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component. Moreover, when the processor 701 is multiple, a part of them can be general-purpose processors and the other part can be special-purpose processors.

[0123] The memory 703 includes one or more, which can be, but is not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM), etc.

[0124] It can be understood that Figure 6 The structure shown is only schematic, and the operation and maintenance equipment 700 can also include more or fewer components than those shown in Figure 6 or have a different configuration from Figure 6 that shown. Figure 6The components shown in the figure can be implemented in hardware, software or a combination thereof. In the embodiments of the present application, the operation and maintenance device 700 can be, but is not limited to, a desktop computer, a notebook computer, a smart phone, a smart wearable device, a vehicle-mounted device and the like, and can also be a virtual machine and the like. In addition, the operation and maintenance device 700 is not necessarily a single device, but can also be a combination of multiple devices, such as a server cluster, and the like.

[0125] The embodiments of the present application also provide a computer program product, comprising a computer program stored on a computer readable storage medium, the computer program comprising computer program instructions, when the computer program instructions are executed by a computer, the computer can execute the steps of the target proxy device determination method in the above embodiments, for example, comprising: S201: determining whether the remaining memory space of the candidate proxy device is not less than the size of the operation and maintenance file. S202: if the remaining memory space of the candidate proxy device is not less than the size of the operation and maintenance file, the candidate proxy device is determined as the target proxy device, and the remaining memory space of the candidate proxy device is updated; otherwise, the candidate proxy device of the upper level is queried.

[0126] The embodiments of the present application also provide a computer readable storage medium, which stores computer program instructions, when the computer program instructions are executed by a computer, the computer program instructions make the computer execute the target proxy device determination method in the foregoing method embodiments.

[0127] In the embodiments provided by the present application, it should be understood that the disclosed device and method can be implemented in other manners. The described device embodiments are only schematic. For example, the division of the units is only a logical function division. There can be another division manner for the actual implementation, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections between the units can be indirect couplings or communication connections through some interfaces, and can be electrical, mechanical or other forms.

[0128] In addition, the units described as separate components can or can not be physically separate, and the components displayed as units can or can not be physical units, that is, they can be located in one place, or can be distributed on multiple network units. According to actual needs, some or all of the units can be selected to achieve the purposes of the embodiments of the present application.

[0129] In addition, each functional module in each embodiment of the present application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0130] It should be noted that if the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application or the parts of the present application that essentially contribute to the prior art or the parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0131] In this document, relational terms such as first and second and the like can be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.

[0132] The above only describes the embodiments of the present application and is not used to limit the protection scope of the present application. For those skilled in the art, the present application can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for determining a target agent device, characterized in that, The method is applied to maintenance equipment configured to remotely maintain at least one terminal device deployed in a multi-layer network architecture, the terminal device being located at a power engineering site, and the multi-layer network architecture further including multiple proxy devices located at different layers; the method includes: For any terminal device, obtain the routing information corresponding to the terminal device, wherein the routing information includes the level of the terminal device in the multi-layer network architecture, and the file transfer performance parameters of each candidate proxy device on the data transmission path of the terminal device, wherein the data transmission path is the communication link from the operation and maintenance device to the terminal device; Based on the predetermined proxy device selection strategy, and based on the routing information and the size of the maintenance file to be distributed, a candidate proxy device is selected from multiple candidate proxy devices on the data transmission path as the target proxy device responsible for subsequently distributing the maintenance file to the terminal device. The proxy device selection strategy is either a first strategy or a second strategy. The first strategy is used to select the candidate proxy device that is closest to the terminal device at the network layer from the plurality of candidate proxy devices, provided that the remaining memory space is not less than the size of the operation and maintenance file. The second strategy is used to select the candidate proxy device that is closest to the operation and maintenance device at the network layer from the plurality of candidate proxy devices, provided that the remaining memory space is not less than the size of the operation and maintenance file.

2. The method for determining the target agent device according to claim 1, characterized in that, The file transfer performance parameters include: the transfer time required for each candidate agent device to transfer the maintenance file to the next level device, and the remaining memory space of each candidate agent device.

3. The method for determining the target agent device according to claim 2, characterized in that, If the proxy device selection strategy is the first strategy, the step of determining a candidate proxy device as the target proxy device from multiple candidate proxy devices on the data transmission path based on the routing information and the size of the operation and maintenance file, according to the pre-determined proxy device selection strategy, includes: Starting with the candidate proxy device that is closest to the terminal device at the network layer in the data transmission path, the process proceeds upwards layer by layer in the data transmission path until the target proxy device is determined. For the currently queried candidate proxy device, the following steps are repeated: Determine whether the remaining memory space of the candidate agent device is not less than the size of the maintenance file; If the remaining memory space of the candidate agent device is not less than the size of the operation and maintenance file, then the candidate agent device is determined as the target agent device, and the remaining memory space of the candidate agent device is updated; otherwise, the candidate agent device at the next higher level is queried.

4. The method for determining the target agent device according to claim 3, characterized in that, The step of determining a candidate proxy device as the target proxy device from multiple candidate proxy devices on the data transmission path based on the routing information and the size of the operation and maintenance files, according to a pre-determined proxy device selection strategy, further includes: For the currently queried candidate proxy device, the operation and maintenance duration is updated according to the transmission time corresponding to the candidate proxy device, wherein the operation and maintenance duration represents the time required for the operation and maintenance file to be transmitted from the target proxy device to the terminal device.

5. The method for determining the target agent device according to claim 2, characterized in that, If the proxy device selection strategy is the second strategy, the step of determining a candidate proxy device as the target proxy device from multiple candidate proxy devices on the data transmission path based on the routing information and the size of the operation and maintenance file, according to the pre-determined proxy device selection strategy, includes: Starting with the candidate proxy device that is closest to the terminal device at the network layer in the data transmission path, the process proceeds upwards layer by layer in the data transmission path until the target proxy device is determined. For the currently queried candidate proxy device, the following steps are repeated: Determine whether the remaining memory space of the candidate agent device is not less than the size of the maintenance file, and update the maintenance duration according to the transmission time corresponding to the candidate agent device; If the remaining memory space is not less than the size of the operation and maintenance file, the candidate agent device is marked as a first state, wherein the first state indicates that the candidate agent device is available; otherwise, the agent device is marked as a second state, wherein the second state indicates that the candidate agent device is unavailable. Determine whether the maintenance duration is greater than the transmission duration threshold. If the maintenance duration exceeds the transmission duration threshold, the candidate proxy device that is closest to the maintenance device at the network layer among the candidate proxy devices marked in the first state is determined as the target proxy device, and the remaining memory space of the candidate proxy device is updated; otherwise, the candidate proxy device at the next higher level is queried.

6. The method for determining the target agent device according to claim 5, characterized in that, If no candidate proxy device marked as the first state exists when the maintenance duration exceeds the transmission duration threshold, then the step of determining a candidate proxy device as the target proxy device from multiple candidate proxy devices on the data transmission path based on the routing information and the size of the maintenance file, according to a pre-determined proxy device selection strategy, further includes: The system queries the candidate proxy devices at the next higher level until it finds a candidate proxy device whose remaining memory space is not less than the size of the operation and maintenance file, and then identifies that candidate proxy device as the target proxy device.

7. A multi-layer network architecture, characterized in that, include: Maintenance equipment is used to perform the method for determining the target agent device as described in any one of claims 1-6; Multiple agent devices located at different levels; At least one terminal device.

8. A computer program product, characterized in that, It includes computer program instructions, which, when read and executed by a processor, perform the method for determining a target agent device as described in any one of claims 1-6.

9. A maintenance equipment, characterized in that, include: Processor, memory, and bus; The processor and the memory communicate with each other via the bus; The memory stores computer program instructions that can be executed by the processor, which can invoke the computer program instructions to perform the method for determining the target agent device as described in any one of claims 1-6.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions, which, when executed by a computer, cause the computer to perform the method for determining a target agent device as described in any one of claims 1-6.

Images