Topology checking method, device and equipment for internet-of-things carrier equipment

Abstract

The invention relates to a topology checking method, device and equipment for internet-of-things carrier equipment. The method comprises the following steps: in response to an equipment checking request for a target power grid, controlling a management machine in the target power grid, sending an information reporting request to managed internet-of-things carrier equipment, receiving current equipment topological data reported by the management machine, and checking the internet-of-things carrier equipment according to the current equipment topological data and historical equipment topological data of the target power grid, determining whether the equipment topological relation of the target power grid is changed or not, and when it is determined that the equipment topological relation of the target power grid is changed, according to the node depth of each node in the current equipment topological data, the number of branches associated with each node and a preset placement rule of a primitive corresponding to the power distribution terminal, determining that the equipment topological relation of the target power grid is changed; and generating a current distribution network single line diagram of the target power grid, and checking the topological structure of the target power grid according to the current distribution network single line diagram. By adopting the method, the reliability of power grid operation management can be ensured.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a topology verification method, apparatus, and device for Internet of Things carrier devices. Background Technology

[0002] As the power grid continues to expand, the frequency of grid connection changes and mode adjustments is increasing, which places increasingly higher demands on the level of power grid operation and management. Existing technologies can use IoT carrier devices to collect operational information from corresponding distribution terminals, thereby enabling power grid operation management.

[0003] However, by directly collecting the operating information of the distribution terminals through IoT carrier devices using the above method, the topological relationship between the distribution terminals cannot be identified, which reduces the reliability of power grid operation and management. Summary of the Invention

[0004] Therefore, it is necessary to provide a topology verification method, apparatus, and device for IoT carrier devices that can ensure the reliability of power grid operation and management, addressing the aforementioned technical problems.

[0005] Firstly, this application provides a device verification method, including:

[0006] In response to a device verification request for the target power grid, the management unit in the target power grid is controlled to send an information reporting request to the managed IoT carrier devices; wherein, the information reporting request is used to request the IoT carrier devices to obtain the current device topology data of the corresponding power distribution terminal;

[0007] Receive current device topology data reported by the management unit;

[0008] Based on the current equipment topology data and the historical equipment topology data of the target power grid, determine whether there have been changes in the equipment topology relationships of the target power grid;

[0009] When it is determined that there are changes in the equipment topology of the target power grid, the current distribution network single-line diagram of the target power grid is generated based on the node depth of each node in the current equipment topology data, the number of branches of each node's associated branches, and the preset placement rules of the corresponding graphic elements of the distribution terminal.

[0010] Based on the current distribution network single-line diagram, the topology of the target power grid is verified.

[0011] In one embodiment, the information reporting request is used to request the IoT carrier device to obtain the device data of the corresponding power distribution terminal, and to determine the current device topology data based on the device data; wherein, the current device topology data includes the node identifier, parent node identifier, topology level, and device operation information of the power grid node where the power distribution terminal is located.

[0012] In one embodiment, determining whether there have been changes in the device topology relationships of the target power grid based on current device topology data and historical device topology data of the target power grid includes:

[0013] If the number of current nodes in the current equipment topology data is consistent with the standard number of nodes in the target power grid, determine the current node attributes and current topology relationships of each node in the target power grid based on the current equipment topology data; determine the historical node attributes and historical topology relationships of each node in the target power grid based on the historical equipment topology data of the target power grid; and determine whether there have been changes in the equipment topology relationships of the target power grid based on the consistency between the current node attributes and historical node attributes, as well as the consistency between the current topology relationships and historical topology relationships.

[0014] In one embodiment, the method further includes:

[0015] When the current number of nodes differs from the standard number of nodes, the equipment topology of the target power grid is determined to be different.

[0016] In one embodiment, based on the node depth of each node in the current device topology data, the number of branches associated with each node, and the preset placement rules of the corresponding graphic elements of the distribution terminal, a current distribution network single-line diagram of the target power grid is generated, including:

[0017] Based on the node depth of each node in the current equipment topology data, determine the main line in the target power grid; based on the number of branches associated with each node in the current equipment topology data, and the preset placement rules of the corresponding graphic elements of the distribution terminal, add the graphic elements corresponding to the distribution terminal on the main line to obtain the current distribution network single-line diagram of the target power grid.

[0018] In one embodiment, the method further includes:

[0019] The display page presents the current single-line diagram of the distribution network to the operation and maintenance personnel. Based on the operation and maintenance personnel's behavior data on the display page, the target graphic element is determined from the current single-line diagram of the distribution network. The display page also presents the graphic element information of the target graphic element to the operation and maintenance personnel. The graphic element information includes the attribute information of the distribution terminal corresponding to the target graphic element, the current line, and the address of the associated IoT carrier device.

[0020] Secondly, this application also provides a topology verification device for IoT carrier devices, comprising:

[0021] The request sending module is used to respond to the device verification request for the target power grid, control the management unit in the target power grid to send an information reporting request to the managed IoT carrier device; wherein, the information reporting request is used to request the IoT carrier device to obtain the current device topology data of the corresponding power distribution terminal;

[0022] The data receiving module is used to receive the current device topology data reported by the management unit;

[0023] The change verification module is used to determine whether there are any changes in the equipment topology relationships of the target power grid based on the current equipment topology data and the historical equipment topology data of the target power grid.

[0024] The generation module is used to generate the current distribution network single-line diagram of the target power grid when it is determined that there are changes in the equipment topology relationship of the target power grid, based on the node depth of each node in the current equipment topology data, the number of branches of each node's associated branches, and the preset placement rules of the corresponding graphic elements of the distribution terminal.

[0025] The verification module is used to verify the topology of the target power grid based on the current distribution network single-line diagram.

[0026] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0027] In response to a device verification request for the target power grid, the management unit in the target power grid is controlled to send an information reporting request to the managed IoT carrier devices; wherein, the information reporting request is used to request the IoT carrier devices to obtain the current device topology data of the corresponding power distribution terminal;

[0028] Receive current device topology data reported by the management unit;

[0029] Based on the current equipment topology data and the historical equipment topology data of the target power grid, determine whether there have been changes in the equipment topology relationships of the target power grid;

[0030] When it is determined that there are changes in the equipment topology of the target power grid, the current distribution network single-line diagram of the target power grid is generated based on the node depth of each node in the current equipment topology data, the number of branches of each node's associated branches, and the preset placement rules of the corresponding graphic elements of the distribution terminal.

[0031] Based on the current distribution network single-line diagram, the topology of the target power grid is verified.

[0032] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0033] In response to a device verification request for the target power grid, the management unit in the target power grid is controlled to send an information reporting request to the managed IoT carrier devices; wherein, the information reporting request is used to request the IoT carrier devices to obtain the current device topology data of the corresponding power distribution terminal;

[0034] Receive current device topology data reported by the management unit;

[0035] Based on the current equipment topology data and the historical equipment topology data of the target power grid, determine whether there have been changes in the equipment topology relationships of the target power grid;

[0036] When it is determined that there are changes in the equipment topology of the target power grid, the current distribution network single-line diagram of the target power grid is generated based on the node depth of each node in the current equipment topology data, the number of branches of each node's associated branches, and the preset placement rules of the corresponding graphic elements of the distribution terminal.

[0037] Based on the current distribution network single-line diagram, the topology of the target power grid is verified.

[0038] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0039] In response to a device verification request for the target power grid, the management unit in the target power grid is controlled to send an information reporting request to the managed IoT carrier devices; wherein, the information reporting request is used to request the IoT carrier devices to obtain the current device topology data of the corresponding power distribution terminal;

[0040] Receive current device topology data reported by the management unit;

[0041] Based on the current equipment topology data and the historical equipment topology data of the target power grid, determine whether there have been changes in the equipment topology relationships of the target power grid;

[0042] When it is determined that there are changes in the equipment topology of the target power grid, the current distribution network single-line diagram of the target power grid is generated based on the node depth of each node in the current equipment topology data, the number of branches of each node's associated branches, and the preset placement rules of the corresponding graphic elements of the distribution terminal.

[0043] Based on the current distribution network single-line diagram, the topology of the target power grid is verified.

[0044] The aforementioned method, apparatus, and equipment for topology verification of IoT carrier devices control a management unit in the target power grid to send information reporting requests to the managed IoT carrier devices. After receiving the current device topology data reported by the management unit, the method determines whether there are changes in the device topology relationships of the target power grid based on the current device topology data and the historical device topology data of the target power grid. If changes are found, the method generates a current distribution network single-line diagram of the target power grid based on the node depth of each node, the number of branches associated with each node, and the preset placement rules of the corresponding elements of the distribution terminals in the current device topology data. The topology structure of the target power grid is then verified based on this single-line diagram. Compared to related technologies that directly collect operating information of distribution terminals through IoT carrier devices, the above method, by reconstructing the current distribution network single-line diagram based on the node depth of each node, the number of branches associated with each node, and the preset placement rules of the corresponding elements of the distribution terminals, ensures the reliability of the topology verification and thus improves the reliability of power grid operation and management. Attached Figure Description

[0045] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0046] Figure 1 This is a flowchart illustrating a device verification method in one embodiment;

[0047] Figure 2 This is a schematic diagram of the installation of an IoT carrier device in one embodiment;

[0048] Figure 3 This is a flowchart illustrating the process of determining changes in device topology in one embodiment;

[0049] Figure 4 This is a flowchart illustrating the process of determining the current single-line diagram of the distribution network in one embodiment;

[0050] Figure 5 This is a schematic diagram illustrating the changes in a single-line diagram of the distribution network in one embodiment;

[0051] Figure 6 This is a flowchart illustrating the device verification method in another embodiment;

[0052] Figure 7 This is a structural block diagram of a topology verification device for an IoT carrier device in one embodiment;

[0053] Figure 8 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0054] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0055] As the power grid continues to expand, the frequency of grid connection changes and mode adjustments is increasing, which places increasingly higher demands on the level of power grid operation and management. Existing technologies can use IoT carrier devices to collect operational information from corresponding distribution terminals, thereby enabling power grid operation management.

[0056] However, by directly collecting the operating information of the distribution terminals through IoT carrier devices using the above method, the topological relationship between the distribution terminals cannot be identified, which reduces the reliability of power grid operation and management.

[0057] Based on this, in an exemplary embodiment, a device verification method is provided, which will be described using an application of this method to a server as an example. Figure 1 As shown, the specific steps include:

[0058] S101, in response to the device verification request for the target power grid, controls the management unit in the target power grid to send an information reporting request to the managed IoT carrier device.

[0059] Among them, the so-called IoT carrier device is a dedicated device that realizes data transmission on power lines based on power line carrier technology. The so-called target power grid is the distribution network with verification requirements. The so-called device verification request is a request to verify each distribution terminal in the power grid. The so-called management unit is used to manage each IoT carrier device in its line. The information reporting request is used to request the IoT carrier device to obtain the current device topology data of the corresponding distribution terminal. The so-called current device topology data is the operating data between each device in the target power grid at the current moment, which can include the operating status of the distribution terminal and the topological relationship between each distribution terminal.

[0060] Understandably, in order to ensure the reliability of data transmission of IoT carrier devices, IoT carrier devices can be directly connected to power distribution terminals. The management unit can access the network management system of the target power grid through a wireless network, ultimately ensuring the normal communication links between the power distribution terminal, IoT carrier devices, management unit, and system software. In the network management system, a Common Information Model (CIM) is created for the management unit and IoT carrier devices.

[0061] Optionally, users can initiate a device verification request for a target power grid through the power grid management page associated with the server. Upon detecting the device verification request, the user can control the management unit in the target power grid to send an information reporting request to the IoT carrier devices managed by the management unit. At this time, the IoT carrier devices will send characteristic signals to the connected power distribution terminals to obtain the current device topology data of the power distribution terminals.

[0062] S102, Receive the current device topology data reported by the management unit.

[0063] Optionally, the management unit can query the information collection status of each managed IoT carrier device individually. After processing the collected information from each managed IoT carrier device, the management unit can report the acquired current device topology data to the server. Correspondingly, the server can receive the current device topology data reported by the management unit.

[0064] S103, Based on the current equipment topology data and the historical equipment topology data of the target power grid, determine whether there have been any changes in the equipment topology relationships of the target power grid.

[0065] The so-called historical equipment topology data refers to the equipment topology data of the target power grid within a historical period. The so-called equipment topology relationship refers to the topological relationship between various devices in the power grid.

[0066] Optionally, the change in the device topology of the target power grid can be determined based on the data differences between the current device topology data and the historical device topology data of the target power grid. For example, the current device topology can be determined based on the current device topology data, and the historical device topology can be determined based on the historical device topology data. If the current device topology is consistent with the historical device topology, it is determined that the device topology of the target power grid has not changed. If the current device topology is inconsistent with the historical device topology, it is determined that the device topology of the target power grid has changed.

[0067] S104. If it is determined that there is a change in the equipment topology relationship of the target power grid, the current distribution network single-line diagram of the target power grid is generated based on the node depth of each node in the current equipment topology data, the number of branches of each node's associated branches, and the preset placement rules of the corresponding graphic elements of the distribution terminal.

[0068] Node depth is used to characterize the location of a node on a power line. A distribution network single-line diagram is a simplified visual map of the distribution network. Graphical elements are standardized graphic symbols / icons representing various devices, lines, and topological relationships within the network system. Preset placement rules are the principles governing the placement of graphic elements in the distribution network single-line diagram. The current distribution network single-line diagram is the distribution network single-line diagram based on the current device topology data.

[0069] Optionally, if it is determined that the equipment topology of the target power grid remains unchanged, the verification of the target power grid topology is proven to be successful.

[0070] If the topology of the target power grid has changed, it is necessary to further determine the details of the topology change. Specifically, based on the node depth of each node in the current equipment topology data, the number of branches associated with each node, and the preset placement rules of the elements corresponding to the distribution terminals, the elements corresponding to the distribution terminals can be arranged to obtain the current single-line diagram of the target power grid.

[0071] Alternatively, the current device topology data can be input into a trained single-line diagram generation model. The single-line diagram generation model will output the current distribution network single-line diagram of the target power grid based on the node depth of each node in the current device topology data, the number of branches of each node's associated branches, and the preset placement rules of the corresponding graphic elements of the distribution terminal.

[0072] S105, Based on the current distribution network single-line diagram, verify the topology of the target power grid.

[0073] Optionally, the current distribution network single-line diagram can be compared with the standard distribution network single-line diagram of the target power grid. If the comparison results are consistent, the topology verification of the target power grid is deemed successful; if the comparison results are inconsistent, the topology verification of the target power grid is deemed unsuccessful. Alternatively, the current distribution network single-line diagram can be shown to the operation and maintenance personnel, who can then verify the topology of the target power grid based on the current diagram.

[0074] In the aforementioned equipment verification method, the management unit in the target power grid sends an information reporting request to the managed IoT carrier devices. After receiving the current equipment topology data reported by the management unit, it determines whether there are any changes in the equipment topology relationships of the target power grid based on the current equipment topology data and the historical equipment topology data of the target power grid. If changes are found, a current distribution network single-line diagram of the target power grid is generated based on the node depth of each node, the number of branches associated with each node, and the preset placement rules of the corresponding elements of the distribution terminal in the current equipment topology data. The topology structure of the target power grid is then verified based on this single-line diagram. Compared to related technologies that directly collect the operating information of the distribution terminals through IoT carrier devices, this method, by reconstructing the current distribution network single-line diagram based on the node depth of each node, the number of branches associated with each node, and the preset placement rules of the corresponding elements of the distribution terminal, verifies the topology structure of the target power grid. This ensures the reliability of the topology verification and improves the reliability of power grid operation and management.

[0075] Furthermore, in some optional implementations, taking a medium-voltage IoT carrier device as an example, a method for deploying the medium-voltage IoT carrier device is provided. Specifically, the medium-voltage IoT carrier device can be directly physically connected to a power distribution terminal (such as a power distribution terminal unit (DTU) or a feeder terminal unit (FTU)) via an RS485 / Ethernet interface, ensuring the privacy and stability of data transmission. For example, the RS485 interface 1 of a power distribution terminal is hard-wired to the RS485 interface A of the medium-voltage IoT carrier device, forming a dedicated communication channel.

[0076] Furthermore, logical binding is achieved through device identifier association in the system database. For example, the medium-voltage IoT carrier device identifier (Identity Document, ID) is C-10kV-001, and the corresponding distribution terminal ID is DTU-10kV-001. The binding relationship is stored in the configuration relationship table (device_binding table) of a relational database (such as MySQL), and the fields include medium-voltage IoT carrier device carrier_id, distribution terminal dtu_id, binding time, etc.

[0077] CIM is a standardized data model for power systems. CIM models need to be established in the network management system for the management unit and medium-voltage IoT carrier devices. Specifically, the management unit's CIM documentation follows the core standard family of power system information systems, defined as an instance of the EquipmentContainer class, containing the following attributes:

[0078] Identification information: mRID (e.g., M-10kV-Line1-001), name (10kV Line 1 Management Unit); Technical parameters: manufacturerName (Equipment Manufacturer), modelName (Equipment Model), communicationCapability (List of Supported Communication Protocols); Topology attributes: Terminal (Communication Interface Terminal), ConnectivityNode (Network Connection Node).

[0079] Medium-voltage IoT carrier equipment CIM filing: Defined as an instance of the Equipment class, associated with PowerSystemResource, including: basic attributes: mRID (e.g., C-10kV-Line1-002), locationName (installation location, e.g., 10kV line 1#3 pole-mounted switch); association relationship: Association (binding relationship with the distribution terminal, associated through the Asset class); topology parameters: BaseVoltage (10kV), Terminal (communication terminal with the management unit / distribution terminal).

[0080] After the CIM model is created, it is stored in Extensible Markup Language (XML) format and supports model interaction with other systems on the main station (such as SCADA data acquisition and monitoring control system and EMS energy management system).

[0081] For example, you can refer to Figure 2 The diagram shows the installation of medium-voltage IoT carrier equipment. On the left is the substation's 10kV busbar, from which three 10kV lines (Line 1, Line 2, and Line 3) extend. Each line is equipped with a management unit and multiple medium-voltage IoT carrier devices, forming an independent carrier communication network. The diagonally striped rectangles represent medium-voltage IoT carrier devices that have detected characteristic signals, indicating that the device has successfully received and identified the characteristic signals sent by other medium-voltage IoT carrier devices. The diamond-patterned rectangles represent medium-voltage IoT carrier devices that have not detected characteristic signals, possibly due to signal transmission distance, interference, or device-specific issues. The blank rectangles represent medium-voltage IoT carrier devices that are sending characteristic signals; these devices actively send characteristic signals to the medium-voltage lines for topology identification.

[0082] Taking each 10kV line as an example, the installation, deployment, and signal interaction of the carrier equipment are explained. Specifically, in 10kV line 1, the management unit is deployed at the beginning of the line, followed by multiple medium-voltage IoT carrier devices connected in series. Some medium-voltage IoT carrier devices (diagonal pattern) detect the characteristic signal, some (diamond pattern) do not detect it, and some medium-voltage IoT carrier devices (blank) actively send characteristic signals. The line topology is constructed through this signal interaction. The structure of 10kV line 2 is similar to that of line 1. The medium-voltage IoT carrier devices at different locations are in three states: signal detected, signal not detected, and signal sending, respectively, reflecting the signal propagation and topology identification process of the devices in the line. In 10kV line 3, the management unit also takes the lead. Each medium-voltage IoT carrier device completes its own position identification in the topology by transmitting and receiving characteristic signals. The distribution of different patterns intuitively presents the signal transmission effect in this line.

[0083] Based on the above embodiments, in this embodiment, the information reporting request is used to request the IoT carrier device to obtain the device data of the corresponding power distribution terminal, and to determine the current device topology data based on the device data.

[0084] The so-called equipment data refers to the relevant data of the power distribution terminal during operation, as well as the equipment's attribute information. The current equipment topology data includes the node identifier, parent node identifier, topology level, and equipment operation information of the power grid node where the power distribution terminal is located.

[0085] Optionally, after the management unit in the target power grid sends an information reporting request to the IoT carrier device under its management, the IoT carrier device will obtain the device data of the corresponding power distribution terminal, process the device data, extract the node-related information and device operation information in the device data, and thus generate the current device topology data.

[0086] For example, taking medium-voltage IoT carrier equipment as an example, the management unit can periodically schedule the medium-voltage IoT carrier equipment to send characteristic signals to the corresponding power distribution terminals. Specifically, the management unit adopts a fixed-period and actively triggered scheduling mode. The scheduling period is typically set to 5 minutes per cycle (which can be adjusted according to the frequency of changes in the distribution network topology; for example, it can be shortened to 3 minutes for important lines), triggered by a timer built into the management unit. The triggering condition can be set such that, in addition to periodic scheduling, if the management unit detects a change in its own or the communication status of the medium-voltage IoT carrier equipment (such as the addition of a new medium-voltage IoT carrier equipment or link recovery), it will also immediately trigger a temporary scheduling to ensure the real-time nature of the topology data.

[0087] The scheduling instructions issued by the management unit to the medium-voltage IoT carrier equipment include key parameters. These key parameters include: carrier frequency, selected as 100kHz~300kHz (e.g., 200kHz), which has low transmission attenuation and strong anti-interference capability in medium-voltage lines; signal duration set to 100ms, ensuring stable detection by adjacent medium-voltage IoT carrier equipment while avoiding prolonged occupation of the power line channel; signal power controlled within 5W, meeting the power requirements for coupled transmission in medium-voltage lines while avoiding electromagnetic interference to other equipment in the power grid; and a unique identifier, i.e., the characteristic signal must embed the device ID and node sequence number (e.g., C-10kV-Line1-002) of the sending medium-voltage IoT carrier equipment to ensure that the receiver can identify the signal source.

[0088] Specifically, the transmission and execution process of scheduling instructions includes: the scheduling instructions sent by the management unit adopt a custom binary format with the structure: [frame header 0xAA] + [device address] + [instruction code 0x02] + [frequency parameter] + [duration] + [check bit 0x55].

[0089] After receiving the instruction, the medium-voltage IoT carrier device starts the signal generation module and injects the characteristic signal into the 10kV line through a capacitive coupler. The signal contains its own device ID and node number, such as: characteristic signal = carrier frequency (200kHz) + device ID (C-10kV-Line1-002) + node number (002) + check code.

[0090] The management unit employs polling scheduling (rather than broadcasting), issuing commands to each medium-voltage IoT carrier device one by one to avoid channel conflicts caused by multiple devices simultaneously transmitting signals. It then waits for all medium-voltage IoT carrier devices to collect their data. It's important to note that waiting for all medium-voltage IoT carrier devices to collect data is crucial for reserving sufficient signal acquisition windows, ensuring that each device can complete the detection, capture, and preliminary processing of data from the devices on the line. The management unit sets a fixed acquisition duration for all medium-voltage IoT carrier devices, taking into account factors such as signal transmission delay and the sampling rate of the medium-voltage IoT carrier devices; this duration is typically set to 2 seconds.

[0091] The management unit queries each medium-voltage IoT carrier device to collect data. Specifically, the polling order is as follows: the management unit polls according to the ascending device ID of the medium-voltage IoT carrier devices (e.g., C-10kV-CD-001→C-10kV-CD-027) or the pre-assigned sequence number in the topology, avoiding duplicate queries or missing devices; alternatively, it can poll sequentially from the beginning to the end of the main line according to the hierarchical relationship of the line topology, adapting to the characteristics of the radial distribution network structure. The total duration of a single poll matches the signal acquisition window of S4, and the query response timeout for a single medium-voltage IoT carrier device is set to 500ms (adjustable via the management unit configuration interface), ensuring that the interaction is completed within the latency range of the distribution network carrier communication.

[0092] When the signal acquisition window ends, the polling module of the management unit will start automatically without manual intervention. If the management unit detects that a medium-voltage IoT carrier device is marked as having an acquisition anomaly, it will prioritize adding it to the polling queue to confirm the device status in advance.

[0093] After all medium-voltage IoT carrier devices have been polled once as described above, the current device topology data is generated through analysis. Specifically, after the management unit completes the polling of the medium-voltage IoT carrier devices, it transforms the raw collected data into structured current device topology data through signal strength analysis and parent-child node matching algorithms. The specific implementation steps are as follows: the management unit first cleans and filters the collected data in the temporary database.

[0094] The parent-child node relationship of each medium-voltage IoT carrier device is then determined through signal strength priority and hierarchical tracing. Specifically, for each medium-voltage IoT carrier device, the medium-voltage IoT carrier device with the strongest signal strength is selected as the candidate parent node for its valid acquisition records. For example, if medium-voltage IoT carrier device C-10kV-CD-003 acquires signals from C-002 (-30dBm) and C-001 (-42dBm), C-002 is preferentially selected as the candidate parent node. Then, considering the physical routing of the line and the pre-archived device installation location, the topology level of the candidate parent node is verified to ensure it is higher than that of the current medium-voltage IoT carrier device (e.g., the parent node's installation location is closer to the substation). If a contradiction arises where the child node's level is higher than the parent node's, the sender of the second strongest signal is reselected as the parent node. Finally, if two medium-voltage IoT carrier devices are detected as each other's candidate parent nodes (such as C-005 and C-006 collecting the strongest signals from each other), it is determined to be a distribution network ring network segment, marked as a ring network node, and the common upstream node of the ring network is set as the parent node of both.

[0095] The management unit periodically and proactively reports the current device topology data collected from each of its subordinate medium-voltage IoT carrier devices, including node number, parent node number, topology level, and anomaly information. Among these, the anomaly information proactively reported by the management unit is key data for distribution network topology monitoring and maintenance. It originates from the signal interaction, data acquisition, and topology analysis processes of the medium-voltage IoT carrier devices and can be categorized into three main types: communication anomalies, signal acquisition anomalies, and topology relationship anomalies. Each type of anomaly corresponds to a specific device status or topology problem and must be included in the reported topology data with a standardized description.

[0096] In this application embodiment, a process for collecting current device topology data is provided, which can ensure the reliability of current device topology data collection.

[0097] Based on the above embodiments, this application provides an optional method for determining changes in device topology, such as... Figure 3 As shown, the specific steps include:

[0098] S301, if the number of current nodes in the current device topology data is consistent with the standard number of nodes in the target power grid, determine the current node attributes and current topology relationships of each node in the target power grid based on the current device topology data.

[0099] The term "current node count" refers to the number of nodes contained in the current device topology data; the term "standard node count" refers to the number of nodes contained in the target power grid vehicle during operation. "Current node attributes" refers to the operational attributes of each node at the current moment, such as abnormal states and invalid attributes. "Current topology relationships" refers to the topological relationships between the nodes at the current moment.

[0100] In one optional implementation, it can be determined whether the current number of nodes in the current device topology data is consistent with the standard number of nodes in the target power grid. If the current number of nodes is consistent with the standard number of nodes, feature extraction can be performed on the current device topology data to obtain the current node attributes and current topology relationships of each node in the target power grid.

[0101] In another alternative implementation, if the current number of nodes differs from the standard number of nodes, it is determined that the equipment topology of the target power grid has changed. Specifically, if the current number of nodes differs from the standard number of nodes, it indicates that the operating state of a certain node has changed, and the equipment topology of the target power grid will also change accordingly.

[0102] In addition, changes in the nodes in the power grid can be determined directly based on changes in the current device topology data. For example, taking medium-voltage IoT carrier equipment as an example, if a medium-voltage IoT carrier equipment node number (such as C-10kV-CD-028) not included in the historical baseline data appears in the newly reported data, and the node has complete parent node number and topology level information, it is determined to be a newly added topology node; if a medium-voltage IoT carrier equipment node (such as C-10kV-CD-022) in the historical baseline data does not appear in the newly reported data for three consecutive cycles, and the management unit marks the node as having communication abnormalities, it is determined to be a topology node that is out of contact; if a node only fails to appear in the newly reported data once, it is temporarily determined to be a node that is temporarily offline and is not included in the scope of topology changes, and will be reviewed after the next report.

[0103] S302, Based on the historical equipment topology data of the target power grid, determine the historical node attributes and historical topology relationships of each node in the target power grid.

[0104] The so-called historical node attributes refer to the operational attributes of each node at a historical moment. The so-called historical topology refers to the topological relationships between the nodes at a historical moment.

[0105] Optionally, feature extraction can be performed on the historical equipment topology data of the target power grid to obtain the historical node attributes and historical topology relationships of each node in the target power grid.

[0106] S303, based on the consistency between the current node attributes and the historical node attributes, and the consistency between the current topology and the historical topology, determine whether there are any changes in the equipment topology of the target power grid.

[0107] Optionally, if the consistency between the current node attributes and the historical node attributes is consistent, and the consistency between the current topology relationship and the historical topology relationship is consistent, it is determined that the equipment topology relationship of the target power grid has not changed.

[0108] If the consistency between the current node attributes and the historical node attributes is inconsistent, and / or the consistency between the current topology and the historical topology is inconsistent, it is determined that the device topology of the target power grid has changed.

[0109] It is worth noting that for existing nodes, changes in node attributes can be compared to determine whether they affect the topology status. Specifically, if a node's historical anomaly information is "no valid characteristic signal," but the newly reported anomaly information changes to "communication overload," or the anomaly information changes from "present" to "absent," further judgment is needed based on the topology relationship to determine whether the attribute change is caused by a topology change. If only the description details of the anomaly information change (e.g., signal strength -52dBm to -55dBm) without involving the topology structure, it is determined to be a non-topology change attribute change.

[0110] In addition, changes in parent-child node relationships and topology levels can be compared. If the parent node number of a node is inconsistent with the historical baseline data in the newly reported data (e.g., the parent node of C-10kV-CD-015 changes from 014 to 013), and this change is not caused by abnormal information (e.g., signal interference), it is determined to be a change in topology connection relationship. If the topology level of a node changes with the change in parent node relationship (e.g., after the parent node changes from 014 to 013, the topology level changes from 5 to 4), or there is no change in parent node relationship but the topology level changes abnormally, it is determined to be a change in topology level. If there is no ring network marker in the historical data, and two IoT carrier devices appear in the new data as candidate parent nodes for each other, it is determined to be a newly added ring network topology; otherwise, it is a ring network topology removal.

[0111] For example, topology change identification can be achieved through node-by-node comparison and difference threshold determination algorithms. Specifically, based on the ascending order of IoT carrier device node numbers, the newly reported data is compared with the aforementioned three dimensions of historical baseline data one by one. Each discrepancy is immediately marked as a discrepancy to be determined, and the type of discrepancy (e.g., a new node's parent node has changed) is recorded. If there is a change in the number of nodes or a change in topology relationships, regardless of the number of discrepancies, it is directly determined that the topology has changed; if there is only a change in node attributes and no change in topology structure, it is determined that the topology has not changed; if the discrepancy is a temporarily offline node, it needs to be verified in conjunction with three consecutive reported data; if it fails to recover, it is included in the category of topology change.

[0112] In this embodiment of the application, by judging whether there are changes in the equipment topology of the target power grid from three dimensions—number of nodes, node attributes, and topology relationship—the reliability of the topology relationship analysis can be guaranteed.

[0113] Based on the above embodiments, this application provides an optional method for determining the current distribution network single-line diagram, such as... Figure 4 As shown, the specific steps include:

[0114] S401, determine the main line in the target power grid based on the node depth of each node in the current device topology data.

[0115] Optionally, based on the node depth of each node in the current device topology data, the branch line with the deepest node depth can be used as the main line in the target power grid.

[0116] S402, based on the number of branches associated with each node in the current device topology data and the preset placement rules of the corresponding graphic elements of the power distribution terminal, add the graphic elements corresponding to the power distribution terminal on the main line to obtain the current single-line diagram of the target power grid.

[0117] Optionally, it can be preset that any branch point on the line can extend into a maximum of three distribution network branch lines; otherwise, new branch points are extended downstream of the main line. The order and orientation of the generated child nodes are sorted by their serial numbers. For horizontal elements, the order of the generated child nodes is right, bottom, top. If a child node is in the top or bottom direction, the element is placed vertically by default. For vertically placed elements extending upwards on branch lines, the order of the generated child nodes is top, right, left. If a child node is in the right or left direction, the element is placed horizontally by default. For vertically placed elements extending downwards on branch lines, the order of the generated child nodes is bottom, right, left. If a child node is in the right or left direction, the element is placed horizontally by default.

[0118] Based on this, by combining the number of branches associated with each node in the current device topology data and the preset placement rules of the corresponding graphic elements of the distribution terminal, graphic elements corresponding to each distribution terminal in the target power grid can be added to the main line to obtain the current single-line diagram of the target power grid. For example, refer to Figure 5 The diagram shown illustrates the changes to the single-line distribution network diagram. By combining the above conditions, the single-line distribution network diagram configured in the original way is transformed to obtain a new single-line distribution network diagram, that is, by changing the position of D7.

[0119] In this embodiment of the application, by adding the corresponding graphic elements of the distribution terminal on the main line according to the number of branches associated with each node and the preset placement rules of the graphic elements corresponding to the distribution terminal, the current distribution network single-line diagram can be obtained, which can ensure the reliability of the construction of the current distribution network single-line diagram.

[0120] Based on the above embodiments, this application provides an optional method for determining changes in device topology relationships. Specifically, the current single-line diagram of the distribution network is displayed to the operation and maintenance party through a display page; the target graphic element is determined from the current single-line diagram of the distribution network based on the operation and maintenance party's behavior data on the display page; and the graphic element information of the target graphic element is displayed to the operation and maintenance party through the display page.

[0121] The display page is used to show the current single-line diagram of the distribution network. Behavioral data refers to the data generated by user actions on the display page. The target element is the element selected by the maintenance team from the current single-line diagram of the distribution network. Element information includes the attribute information of the distribution terminal corresponding to the target element, the current line, and the address of the associated IoT carrier device. The current line is the power line where the distribution terminal corresponding to the target element is located.

[0122] Optionally, after determining the current single-line diagram of the power distribution network, the diagram can be displayed to the operations and maintenance (O&M) party through a server-connected display page. After obtaining the O&M party's behavioral data on the display page, the target graphic element selected by the O&M party can be determined from the current single-line diagram based on the location parameters within the behavioral data.

[0123] Furthermore, the display page can show the attribute information (such as abnormal information, organization, and station) of the power distribution terminal corresponding to the target graphic element, the current line, and the address of the associated IoT carrier device for the operation and maintenance personnel to view.

[0124] In this embodiment of the application, the graphic element information of each graphic element is displayed to the operation and maintenance party through the display page, which facilitates the operation and maintenance party to query information.

[0125] Based on the above embodiments, this application embodiment takes the 10kV Chengdong Line medium-voltage distribution network as the application scenario to provide a detailed description of the method for automatically generating and updating the single-line diagram of the distribution network based on medium-voltage IoT carrier equipment. The 10kV Chengdong Line starts from the 10kV outgoing line bay of a 220kV substation, and includes 12 pole-mounted switches, 8 distribution transformers, and 6 ring main units along the line, with a total length of approximately 8.5km. A total of 28 medium-voltage IoT carrier devices (including 1 management unit and 27 carrier units) are deployed, and the distribution terminals adopt DTUs (Distribution Terminal Units), which are connected one-to-one with the carrier units.

[0126] The first step involves installing medium-voltage IoT carrier equipment at the pole-mounted switches, distribution transformers, ring main units, and other power distribution equipment along the 10kV Chengdong line, following the principle of one carrier unit per distribution terminal. The carrier unit is a ZW-35kV medium-voltage IoT carrier unit, which is directly physically connected to the distribution terminal (DTU) via an RS485 interface. It is installed in the secondary compartment of the power distribution equipment, fixed with a DIN rail, and has an IP65 protection rating, suitable for outdoor working environments of -40℃ to +70℃. The management unit is a ZW-M800 carrier communication management unit, installed in the first-end ring main unit of the 10kV Chengdong line. It connects to the main station network management system (using the State Grid Distribution Automation Main Station System V3.0) via a 4G / 5G wireless network module and establishes communication links with the 27 subordinate carrier units through power line carrier communication. The carrier frequency of the carrier equipment is selected in the 10kHz~450kHz medium-voltage power line carrier band, and the signal coupling method is capacitive coupling to ensure stable transmission of the carrier signal in the 10kV line.

[0127] The second step involves creating and binding files for the carrier generator and power distribution terminal. Specifically, the communication links between the power distribution terminal and the carrier generator, between the carrier generator and the management unit, and between the management unit and the main station network management system are tested sequentially. The baud rate is set to 9600bps, and the communication timeout is 3 seconds to ensure that the data transmission packet loss rate between each node is less than 0.1%. Device model files are then created for the management unit and the carrier generator in the network management system.

[0128] The management unit file includes information such as device ID (M-10kV-CD-001), device model, installation location (10kV Chengdong Line #1 ring main unit), IP address (192.168.10.1), and communication protocol (MQTT); the carrier unit file includes information such as device ID (C-10kV-CD-001~C-10kV-CD-027), corresponding distribution terminal number (DTU-001~DTU-027), installed equipment type (pole-mounted switch / distribution transformer / ring main unit), and node basic attributes (initial node sequence number, parent node default value); device binding: a one-to-one binding between the carrier unit and the distribution terminal is completed in the network management system. The binding relationship is associated through the device ID and stored in the system database to ensure the linkage between topology data and distribution terminal status data.

[0129] The third step involves the management unit periodically scheduling the carrier units to send characteristic signals. Specifically, the management unit schedules its subordinate carrier units to send characteristic signals every 5 minutes. The management unit sends scheduling instructions to all carrier units via carrier communication (instruction format: 0x01[device address][instruction code 0x02][checksum]), which includes parameters such as the frequency (200kHz), duration (100ms), and transmission power (5W) of the characteristic signal to be sent. After receiving the instructions, the carrier units send a uniquely identified carrier characteristic signal to the medium-voltage line via the power line. The characteristic signal contains its own device ID, node sequence number, and other identification information to ensure that other carrier units can identify the source of the signal.

[0130] The fourth step involves waiting for all carrier units to acquire characteristic signals. Specifically, after receiving the scheduling instruction from the management unit, all carrier units activate their signal acquisition modules and continuously acquire the carrier characteristic signals in the line for 2 seconds. The carrier unit's signal acquisition module uses a bandpass filter to filter 200kHz characteristic signals, with a sampling rate of 1MHz to ensure the accuracy of signal acquisition. If a carrier unit does not receive characteristic signals from other carrier units during the acquisition period, it is recorded as no signal acquisition, and the anomaly type is marked as signal loss.

[0131] The fifth step involves the management unit querying each carrier unit for its acquired information. Specifically, the management unit sends a polling query command to each carrier unit in ascending order of device ID (command format: 0x01[device address][command code 0x03][checksum]). Upon receiving the query command, each carrier unit feeds back its acquired characteristic signal information (including the signal source device ID, signal strength, and acquisition time) to the management unit via carrier communication. The management unit re-queries carrier units that fail to respond within 500ms three times; if no response is received, the carrier unit is marked as having a communication anomaly.

[0132] The sixth step involves polling all carrier machines once as described above, and then analyzing and generating topology data. Specifically, after the management unit completes polling of all 27 carrier machines, it generates topology data through signal strength analysis and a parent-child node matching algorithm.

[0133] Using the upstream carrier with the strongest signal strength as the parent node, determine the parent node number of each carrier. For example, if carrier C-10kV-CD-003 collects a signal strength of -30dBm from C-10kV-CD-002 (which is the strongest), then the parent node number of C-10kV-CD-003 is 002. Based on the hierarchical relationship between parent and child nodes, calculate the topology level of each carrier (the topology level of the first carrier is 1, its child nodes are 2, and so on). Integrate the node number, parent node number, topology level, and abnormal information (such as signal loss or communication anomalies) to generate structured topology data (data format is JSON).

[0134] The seventh step involves the medium-voltage carrier communication management unit actively reporting data. Specifically, the management unit actively reports topology data to the main station network management system via the 4G / 5G network every 10 minutes.

[0135] The management unit packages the topology data of all carriers into data frames (frame header is 0xAA, frame tail is 0x55, data length is 1024 bytes), encrypts the data using an encryption algorithm (AES-128) and sends it; if the reporting fails, the management unit will cache the topology data and re-report after 30 seconds. The cached data will be retained for a maximum of 1 hour to ensure that the data is not lost.

[0136] The eighth step is to identify whether the device topology has changed. Specifically, the network management system receives and parses the topology data reported by the management machine, and uses an algorithm that compares the old and new topology data to identify whether the topology has changed.

[0137] The system compares the newly reported topology data node by node with the historical topology data stored in the database. The comparison dimensions include the correspondence between the node sequence number and the parent node sequence number, the topology level, and abnormal information. If any node has a changed parent node sequence number, an adjusted topology level, or a newly added / deleted node, it is determined that the topology has changed, the change status is recorded (e.g., the parent node of node C-10kV-CD-015 changes from 014 to 013), and the process proceeds to S9. If the data is completely consistent, the process ends. In this embodiment, because a new distribution transformer (corresponding to carrier unit C-10kV-CD-028) was added at the #7 pole-mounted switch of the 10kV Chengdong line, the system identified the new node in the topology and determined that the topology had changed.

[0138] The ninth step involves the medium-voltage carrier network management system generating a topology file. Specifically, after identifying a topology change, the management system generates a modified device topology file in CIMXML format based on the latest topology data.

[0139] The system parses the reported topology data, extracts information such as device ID, parent-child node relationship, and topology level of all nodes, and constructs a topology model according to the classes such as ConnectivityNode, Equipment, and Association defined in the CIM standard. The generated topology file contains a node list, a connection relationship list, and abnormal node annotations. The file is named 10kV Chengdong Line_Topology_202X0X0X_1530.xml, stored in the topology file directory of the network management system, and synchronously backed up to the cloud database.

[0140] The tenth step involves generating a single-line diagram of the distribution network for the medium-voltage carrier system. Specifically, the network management system, based on the equipment model files established in S2, automatically generates a new version of the single-line diagram of the distribution network according to the constraints in S101~S104, and performs diagram-model verification. The specific process is as follows:

[0141] (1) Distinguishing the main line: The system determines the main line through the node depth calculation algorithm. Traverse the topology level of all carrier machines and calculate the depth of each node (the number of levels from the first node to the node). Among them, the node depth of carrier machine C-10kV-CD-027 is 8 (the deepest). Its branch line (substation → #1 ring network cabinet → #2 pole-mounted switch → … → #12 pole-mounted switch → C-10kV-CD-027) is determined as the horizontal main line. The system draws the main line horizontally in the core area of ​​the single-line diagram. The first node (substation outgoing line bay) is located on the left side of the diagram, and the last node is located on the right side of the diagram.

[0142] (2) Layout rules for multiple nodes: The system performs layout verification and adjustment on the branch points in the line.

[0143] The system detected that the #3 ring main unit (branch point) on the main line was originally intended to extend 4 distribution network branch lines, which exceeded the limit of a maximum of 3. The system added a new branch point (virtual node, device ID V-10kV-CD-001) 100 pixels downstream of the main line of the branch point, and adjusted 1 of the original 4 branch lines to extend to the new branch point to ensure that the extension of branch lines at each branch point does not exceed 3.

[0144] (3) The order and direction of child node placement after generation: The system sorts the child nodes according to their serial numbers and places them according to the specified rules.

[0145] Horizontal element placement: The #2 pole-mounted switch on the main line is a horizontal element, with three sub-nodes (C-10kV-CD-005, C-10kV-CD-006, C-10kV-CD-007). These are arranged in ascending order of node number, and placed sequentially to the right, below, and above the #2 pole-mounted switch. The sub-nodes below and above automatically switch to vertical placement. Vertical element placement: The #5 transformer (vertical element) extending upwards on the branch line has three sub-nodes (C-10kV-CD-012, C-...). The sub-nodes (C-10kV-CD-013 and C-10kV-CD-014) are arranged in ascending order and placed above, to the right, and to the left of the #5 transformer. The sub-nodes on the right and left sides are automatically switched to horizontal arrangement. The placement of sub-nodes of the downward-extending vertical elements: The #8 ring main unit (vertical element) on the branch line extends downward, and it has two sub-nodes (C-10kV-CD-020 and C-10kV-CD-021). After being arranged in ascending order, they are placed below and to the right of the #8 ring main unit. The sub-nodes on the right side are automatically switched to horizontal arrangement.

[0146] (4) Floating window information display. The system configures a floating window for each generated device element. When the mouse hovers over the element, the floating window automatically displays the following information: Organization: Distribution Operation and Maintenance Center of Municipal Power Supply Company; Station: Chengdong Distribution Operation and Maintenance Station; Current line: 10kV Chengdong Line; Associated carrier machine address: C-10kV-CD-XXX (corresponding carrier machine device ID); Abnormal information: None / Signal loss / Communication abnormality (updated in real time according to the abnormal information in the topology data).

[0147] The eleventh step involves the system performing a consistency check on the diagram and model after completing the single-line diagram drawing. Specifically, it checks whether all equipment elements on the single-line diagram have corresponding records in the CIM equipment model file, and verifies whether the carrier wave machine and distribution terminal in the model file are displayed on the single-line diagram. In this embodiment, the newly added C-10kV-CD-028 carrier wave machine element matches the model file without any missing elements. It also verifies whether the connection relationship of the equipment elements on the single-line diagram is consistent with the parent-child node relationship in the topology file. After verification, the connection relationship between the #7 pole-mounted switch and the newly added distribution transformer completely matches the topology data. Finally, it checks whether there are any isolated equipment elements in the single-line diagram. In this embodiment, all elements are connected to the main line or branch line, and there are no topology islands.

[0148] After verification, the system will set the new version of the distribution network single-line diagram as the effective version, display it in the graphical interface of the network management system, and synchronize it to the distribution automation dispatch terminal to achieve real-time consistency with the field topology.

[0149] This embodiment utilizes medium-voltage IoT carrier equipment deployed on the 10kV Chengdong line to achieve automatic collection, reporting, and topology change identification of distribution network topology data. Combined with CIM standard archiving and standardized topology file generation, it automatically generates single-line diagrams of the distribution network according to customized layout rules, achieving a 100% pass rate in diagram verification. Compared to the traditional method of manually drawing single-line diagrams, this method shortens the single-line diagram update cycle from two working days to within 10 minutes, significantly improving the efficiency of distribution network topology management. Simultaneously, the signal stability rate of the medium-voltage carrier signal transmitted in the 10kV line reaches 99.5%, and the data transmission rate reaches 200kbps, ensuring the real-time nature and accuracy of the topology data and providing reliable graphical and data support for distribution network dispatching, operation and maintenance, and fault location.

[0150] Figure 6 This is a flowchart illustrating the device verification method in another embodiment. Based on the above embodiments, this embodiment provides an optional example of the device verification method. (Combined with...) Figure 6 The specific implementation process is as follows:

[0151] S601, in response to a device verification request for the target power grid, controls the management unit in the target power grid to send an information reporting request to the managed IoT carrier devices.

[0152] The information reporting request is used to request the IoT carrier device to obtain the device data of the corresponding power distribution terminal, and to determine the current device topology data based on the device data. The current device topology data includes the node identifier, parent node identifier, topology level, and device operation information of the power grid node where the power distribution terminal is located.

[0153] S602, after receiving the current device topology data reported by the management unit, if the number of current nodes in the current device topology data is consistent with the standard number of nodes in the target power grid, determine the current node attributes and current topology relationships of each node in the target power grid based on the current device topology data.

[0154] Optionally, if the current number of nodes is inconsistent with the standard number of nodes, it can be determined that the equipment topology of the target power grid has changed.

[0155] S603, based on the historical equipment topology data of the target power grid, determine the historical node attributes and historical topology relationships of each node in the target power grid.

[0156] S604. Based on the consistency between the current node attributes and the historical node attributes, and the consistency between the current topology and the historical topology, determine whether there are any changes in the equipment topology of the target power grid.

[0157] S605, when it is determined that there is a change in the equipment topology of the target power grid, the main line in the target power grid is determined based on the node depth of each node in the current equipment topology data.

[0158] S606. Based on the number of branches associated with each node in the current device topology data and the preset placement rules of the corresponding graphic elements of the power distribution terminal, add the graphic elements corresponding to the power distribution terminal on the main line to obtain the current single-line diagram of the target power grid.

[0159] S607, based on the current distribution network single-line diagram, verifies the topology of the target power grid.

[0160] Optionally, the current distribution network single-line diagram can be displayed to the operation and maintenance party through the display page; the target graphic element can be determined from the current distribution network single-line diagram based on the operation and maintenance party's behavior data on the display page; the graphic element information of the target graphic element can be displayed to the operation and maintenance party through the display page; wherein, the graphic element information includes the attribute information of the distribution terminal corresponding to the target graphic element, the current line and the address of the associated IoT carrier device.

[0161] The specific processes of S601-S607 described above can be found in the description of the above method embodiments. Their implementation principles and technical effects are similar, and will not be repeated here.

[0162] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0163] Based on the same inventive concept, this application also provides a topology verification device for IoT carrier devices to implement the device verification method described above. The solution provided by this device is similar to the implementation described in the above method. Therefore, the specific limitations of one or more topology verification device embodiments for IoT carrier devices provided below can be found in the limitations of the device verification method above, and will not be repeated here.

[0164] In one exemplary embodiment, such as Figure 7As shown, a topology verification device 1 for IoT carrier devices is provided, comprising: a request sending module 10, a data receiving module 20, a change verification module 30, a generation module 40, and a verification module 50, wherein:

[0165] The request sending module 10 is used to control the management unit in the target power grid to send an information reporting request to the managed IoT carrier device in response to the device verification request for the target power grid; wherein, the information reporting request is used to request the IoT carrier device to obtain the current device topology data of the corresponding power distribution terminal;

[0166] Data receiving module 20 is used to receive the current device topology data reported by the management unit;

[0167] The change verification module 30 is used to determine whether there are any changes in the equipment topology relationships of the target power grid based on the current equipment topology data and the historical equipment topology data of the target power grid.

[0168] The generation module 40 is used to generate the current distribution network single-line diagram of the target power grid when it is determined that there is a change in the equipment topology relationship of the target power grid, based on the node depth of each node in the current equipment topology data, the number of branches of the branches associated with each node, and the preset placement rules of the corresponding graphic elements of the distribution terminal.

[0169] The verification module 50 is used to verify the topology of the target power grid based on the current distribution network single-line diagram.

[0170] In an exemplary embodiment, the information reporting request is used to request the IoT carrier device to obtain the device data of the corresponding power distribution terminal, and to determine the current device topology data based on the device data; wherein, the current device topology data includes the node identifier, parent node identifier, topology level, and device operation information of the power grid node where the power distribution terminal is located.

[0171] In one exemplary embodiment, the change verification module 30 is specifically used for:

[0172] If the number of current nodes in the current equipment topology data is consistent with the standard number of nodes in the target power grid, determine the current node attributes and current topology relationships of each node in the target power grid based on the current equipment topology data; determine the historical node attributes and historical topology relationships of each node in the target power grid based on the historical equipment topology data of the target power grid; and determine whether there have been changes in the equipment topology relationships of the target power grid based on the consistency between the current node attributes and historical node attributes, as well as the consistency between the current topology relationships and historical topology relationships.

[0173] In one exemplary embodiment, the change verification module 30 is further configured to:

[0174] When the current number of nodes differs from the standard number of nodes, the equipment topology of the target power grid is determined to be different.

[0175] In one exemplary embodiment, the generation module 40 is specifically used for:

[0176] Based on the node depth of each node in the current equipment topology data, determine the main line in the target power grid; based on the number of branches associated with each node in the current equipment topology data, and the preset placement rules of the corresponding graphic elements of the distribution terminal, add the graphic elements corresponding to the distribution terminal on the main line to obtain the current distribution network single-line diagram of the target power grid.

[0177] In an exemplary embodiment, the topology verification device 1 for IoT carrier devices further includes a display module, wherein the display module is specifically used for:

[0178] The display page presents the current single-line diagram of the distribution network to the operation and maintenance personnel. Based on the operation and maintenance personnel's behavior data on the display page, the target graphic element is determined from the current single-line diagram of the distribution network. The display page also presents the graphic element information of the target graphic element to the operation and maintenance personnel. The graphic element information includes the attribute information of the distribution terminal corresponding to the target graphic element, the current line, and the address of the associated IoT carrier device.

[0179] Each module in the aforementioned topology verification device for IoT carrier devices can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the corresponding operations of each module.

[0180] In one exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 8 As shown, this computer device includes a processor, memory, input / output interfaces (I / O), and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operating system and computer programs stored in the non-volatile storage media. The database stores device topology data. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When executed by the processor, the computer program implements a device verification method.

[0181] Those skilled in the art will understand that Figure 8 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0182] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0183] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0184] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0185] It should be noted that the data involved in this application (including but not limited to device topology data) are all data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0186] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0187] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0188] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A topology checking method for an Internet of Things carrier device, characterized in that, The method comprises: In response to a device checking request for a target power grid, controlling a management machine in the target power grid to send an information reporting request to a managed Internet of Things carrier device; wherein the information reporting request is used to request the Internet of Things carrier device to obtain current device topology data of a corresponding power distribution terminal; Receiving the current device topology data reported by the management machine; According to the current device topology data and the historical device topology data of the target power grid, it is determined whether the device topology relationship of the target power grid changes; In the case where it is determined that the device topology relationship of the target power grid changes, according to the node depth of each node in the current device topology data, the branch number of each node associated branch, and the preset placement rule of the graph element corresponding to the power distribution terminal, the current power distribution single-line diagram of the target power grid is generated; According to the current power distribution single-line diagram, the topology structure of the target power grid is checked.

2. The method of claim 1, wherein, The information reporting request is used to request the Internet of Things carrier device to obtain device data corresponding to the power distribution terminal, and according to the device data, the current device topology data is determined; wherein the current device topology data includes the node identifier, parent node identifier, topology level of the power grid node where the power distribution terminal is located, and device operation information.

3. The method of claim 1, wherein, According to the current device topology data and the historical device topology data of the target power grid, it is determined whether the device topology relationship of the target power grid changes, comprising: In the case where the current node number in the current device topology data is consistent with the standard node number of the target power grid, according to the current device topology data, the current node attribute and the current topology relationship of each node in the target power grid are determined; According to the historical device topology data of the target power grid, the historical node attribute and the historical topology relationship of each node in the target power grid are determined; According to the consistency between the current node attribute and the historical node attribute, and the consistency between the current topology relationship and the historical topology relationship, it is determined whether the device topology relationship of the target power grid changes.

4. The method of claim 3, wherein, The method further comprises: In the case where the current node number is inconsistent with the standard node number, it is determined that the device topology relationship of the target power grid changes.

5. The method of claim 1, wherein, According to the node depth of each node in the current device topology data, the main line in the target power grid is determined; According to the branch number of each node associated branch in the current device topology data, and the preset placement rule of the graph element corresponding to the power distribution terminal, the graph element corresponding to the power distribution terminal is added on the main line to obtain the current power distribution single-line diagram of the target power grid. The method further comprises:

6. The method of claim 1, wherein, Through a display page, the current power distribution single-line diagram is displayed to an operation and maintenance party; According to the behavior data of the operation and maintenance party in the display page, the target graph element is determined from the current power distribution single-line diagram; ​ The display page is used to display graph element information of the target graph element to the operation and maintenance party, wherein the graph element information comprises attribute information of a power distribution terminal corresponding to the target graph element, a current line, and an associated Internet of Things carrier device address.

7. A topology checking device for an Internet of Things carrier device, characterized in that The apparatus comprises: The request sending module is configured to, in response to a device checking request for a target power grid, control a management machine in the target power grid to send an information reporting request to a managed Internet of Things carrier device; wherein the information reporting request is used to request the Internet of Things carrier device to acquire current device topology data of a corresponding power distribution terminal. The data receiving module is configured to receive the current device topology data reported by the management machine. The change checking module is configured to determine whether there is a change in a device topology relationship of the target power grid according to the current device topology data and historical device topology data of the target power grid. The generation module is configured to, in a case where it is determined that there is a change in the device topology relationship of the target power grid, generate a current power distribution single-line diagram of the target power grid according to node depths of nodes in the current device topology data, branch numbers of branches associated with the nodes, and a preset placement rule of a graph element corresponding to the power distribution terminal. The checking module is configured to check a topology structure of the target power grid according to the current power distribution single-line diagram. 8.A computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the computer device is configured to perform the method according to any one of claims 1-7. The computer program is executed by the processor to implement the steps of the method of any one of claims 1 to 6.

9. A computer readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the method of any one of claims 1 to 6.

10. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the method of any one of claims 1 to 6.

Images