Networking topology information acquisition method, system, device and medium
By establishing a topology information exchange mechanism among power equipment and dynamically aggregating network connection relationships, the problem of time-consuming manual configuration in hybrid photovoltaic power plant networking is solved, and efficient topology construction and deployment are achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- SHANGHAI SIGE DIGITAL TECHNOLOGY CO LTD
- Filing Date
- 2026-03-11
- Publication Date
- 2026-07-14
AI Technical Summary
In existing technologies, the configuration of hybrid grid topology for photovoltaic power plants relies on a large amount of manual operation, which is time-consuming and labor-intensive, and is difficult to adapt to the efficient deployment requirements of multi-scenario and large-scale applications.
By establishing a topology information exchange mechanism among power equipment, network information is generated and broadcast based on locally stored network topology information, and network connection relationships are dynamically aggregated to achieve automatic perception and construction of topology structure, reducing the workload of manual configuration.
It improves network deployment efficiency, adapts to the high-efficiency deployment needs of photovoltaic power plants in multiple scenarios, reduces unnecessary communication overhead and the frequency of manual intervention, and enhances the accuracy and flexibility of topology information.
Smart Images

Figure CN122395061A_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of communication technology, and in particular relates to a method, system, device and medium for obtaining network topology information. Background Technology
[0002] In commercial, industrial, and residential photovoltaic power plants, the communication network of the power control system is crucial for achieving energy dispatch and remote monitoring. With the rapid growth of distributed photovoltaic installations, single communication methods are limited by factors such as transmission distance, interference resistance, and deployment conditions, making it difficult to meet the data transmission and command interaction requirements of the power control system. Therefore, a hybrid networking architecture integrating multiple communication technologies needs to be constructed to balance the requirements of transmission distance, data bandwidth, and deployment cost in different scenarios.
[0003] In related technologies, the topology configuration of hybrid networking relies on a lot of manual operation, which is time-consuming, labor-intensive, and inefficient, making it difficult to adapt to the efficient deployment needs of photovoltaic power plants in multiple scenarios and large-scale applications. Summary of the Invention
[0004] This application aims to address at least one of the technical problems existing in the prior art. To this end, this application proposes a method, system, device, and medium for obtaining network topology information, so as to reduce the workload of manual configuration in network deployment and improve the deployment efficiency of network.
[0005] Firstly, this application provides a method for obtaining network topology information, applicable to any power device in a power system, wherein at least some power devices in the power system support at least two different types of physical links; the method includes: Under the condition that the target conditions are met, first network information is generated based on the first network topology information stored locally; the first network topology information includes at least the target physical link currently connected and the device information of the neighboring power equipment connected on the target physical link. The first network information is broadcast periodically through the currently connected physical links within the target duration; Obtain the second network information of the neighboring power equipment; the second network information is generated based on the second network topology information stored locally by the neighboring power equipment. Update the locally stored first network topology information according to the second network information.
[0006] According to the network topology information acquisition method of this application, by generating first network information based on the first network topology information stored locally under the condition of meeting the target, and broadcasting the first network information through the currently connected physical link, it can actively share its link connection relationship and device identity information with other power devices on the link, and establish a topology information exchange mechanism between devices. By obtaining the second network information generated by the neighboring power devices based on the second network topology information stored locally, and updating the first network topology information stored locally, it can dynamically aggregate network connection relationships within a multi-hop range, realize the automatic perception and construction of topology structure in mixed network scenarios with multiple physical link types. Therefore, it does not need to rely on tedious topology configuration operations by manual means, reduces the workload of manual configuration for network deployment, improves the deployment efficiency of network, and thus better adapts to the efficient deployment needs of photovoltaic power plants in multiple scenarios and large-scale applications.
[0007] According to one embodiment of this application, the target condition includes at least one of the following: Power-on initialization complete; The locally stored network topology information has been updated; The physical link status of the current connection has changed; The communication interface status has changed.
[0008] In this embodiment, by setting at least one of the following as target triggering conditions—power-on initialization completion, local storage network topology information update, change of the current physical link status, and change of communication interface status—network information generation and broadcast can be triggered at the moment of device startup, network structure change, physical connection status switch, or communication port status change. This improves the timeliness of topology information synchronization and can adaptively respond to various dynamic networking needs such as device network entry, link switching, and topology reconstruction, reducing invalid communication overhead and the frequency of manual intervention.
[0009] According to one embodiment of this application, the step of periodically broadcasting the first network information through the currently connected physical link within a target duration includes: Broadcasts are initiated for different physical links, and the first network information carries the link identification information of the corresponding physical link.
[0010] In this embodiment, by broadcasting separately for different physical links, the power devices on each physical link can obtain the network information of the corresponding link. By carrying the link identification information of the corresponding physical link in the first network information, the power devices receiving the network information can identify the physical link type corresponding to the network information, distinguish the connection relationship of different links, and accurately associate and match the network information with the corresponding link, thereby further improving the accuracy of topology construction in mixed network scenarios with multiple physical link types.
[0011] According to one embodiment of this application, obtaining the second network information of the neighboring power equipment includes: The second network information generated and broadcast by the neighboring power devices under the condition that the target conditions are met is obtained; Alternatively, an inquiry request can be sent to the neighboring power equipment to obtain the second network information fed back by the neighboring power equipment based on the inquiry request.
[0012] In this embodiment, by acquiring the second network information generated and broadcast by neighboring power devices under the condition of meeting the target, it is possible to passively receive the topology information actively reported by neighboring devices, reducing the interaction overhead between devices. By sending query requests to neighboring power devices and acquiring the second network information, it is possible to actively acquire the network topology information of neighboring devices when needed, improving the flexibility of topology information acquisition and reducing the problem of incomplete topology information due to broadcast delays or loss. Therefore, by adopting a dual information acquisition method that combines active querying and passive reception, the accuracy of topology structure construction in mixed networking scenarios with multiple physical link types is further improved.
[0013] According to one embodiment of this application, updating the locally stored first network topology information based on the second network information includes: Extract the second network topology information from the second network information; Based on the second network topology information, the device information of the neighboring power devices in the first network topology information stored locally is updated.
[0014] In this embodiment, by extracting the second network topology information from the second network information, the link connection relationship and device information corresponding to the neighboring power devices can be obtained. Based on these data, the device information of the neighboring power devices in the first network topology information stored locally can be updated. The local topology information can be corrected according to the actual status of the neighboring power devices, thereby improving the consistency between the network topology information maintained by each device and the real network structure.
[0015] According to one embodiment of this application, updating the device information of the neighboring power devices in the locally stored first network topology information based on the second network topology information includes: Detect whether the device information updated from the second group network topology information to the neighboring power equipment forms a topology loop; If no topology loop is detected, the device information of the neighboring power devices in the first network topology information stored locally is updated.
[0016] In this embodiment, by detecting whether there is a topology loop before updating the first network topology information stored locally, unreasonable topology structures with data loop forwarding can be identified in advance before the topology information is updated. This reduces problems such as repeated data forwarding, network congestion, and decreased communication efficiency caused by topology loops, and further improves the accuracy of network topology information updates.
[0017] According to one embodiment of this application, detecting whether the device information updated from the second network topology information to the neighboring power equipment forms a topology loop includes: Obtain the topology path after updating the device information of the neighboring power equipment with the second group network topology information; If there are duplicate power devices on the same type of physical link in the topology path, it is determined that a topology loop exists.
[0018] In this embodiment, by obtaining the topology path after the device information of the neighboring power equipment is updated from the second network topology information, the updated network connection path can be restored. Thus, based on whether there are duplicate power equipment on the same type of physical link in the topology path, it can be determined whether there is a topology loop, which improves the accuracy and efficiency of topology loop determination.
[0019] According to one embodiment of this application, the updated first network topology information includes: the device information of the currently connected target physical link and the n-level neighbor power devices connected on the target physical link; or the device information of each power device in the power system; wherein n is greater than or equal to 1.
[0020] In this embodiment, by configuring the updated first network topology information to include the target physical link currently connected and the device information of the n-level neighbor power devices connected on the target physical link, a global complete network topology or a local network topology can be constructed. The local mode or global mode can be flexibly selected according to the device performance, network scale and application scenario.
[0021] According to one embodiment of this application, the method further includes: A topology path is constructed based on the data flow path in the power system in response to cloud service requests. The topology path is saved to the updated first network topology information, and the topology path is deleted if there is no data flow for a preset period of time.
[0022] In this embodiment, a topology path is constructed through the data flow path, and the topology path is saved to the updated first network topology information. This allows for the recording and maintenance of service-related topology paths. If no data flow occurs in the topology path for a preset duration, the topology path is deleted, which reduces the occupation of system resources by redundant topology information and improves resource utilization.
[0023] According to one embodiment of this application, the method further includes: If the topology information of the first network group is updated, the broadcast timeout is updated according to the broadcast duration.
[0024] In this embodiment, by updating the broadcast timeout based on the broadcast duration when the first network topology information is updated, the validity period of the network information broadcast is dynamically adjusted, reducing the broadcast lag or resource waste caused by fixed timeout time, improving the real-time performance of network communication, and thus better adapting to the timely synchronization requirements and accuracy of topology information in the dynamic networking environment of the power system.
[0025] Secondly, this application provides a power system including multiple power devices, at least some of which support at least two different types of physical links; The power equipment is used to perform the above-described method for obtaining network topology information.
[0026] According to the power system of this application, by generating first network information based on locally stored first network topology information under the condition of meeting the target, and broadcasting the first network information through the currently connected physical links, it can actively share its link connection relationship and device identity information with other power devices on the link, and establish a topology information exchange mechanism between devices. By obtaining the second network information generated by neighboring power devices based on locally stored second network topology information and updating the locally stored first network topology information, it can dynamically aggregate network connection relationships within a multi-hop range, realizing the automatic perception and construction of topology structure in mixed networking scenarios with multiple physical link types. Therefore, it does not need to rely on tedious manual topology configuration operations, reduces the workload of manual configuration for network deployment, improves the deployment efficiency of network, and thus better adapts to the efficient deployment needs of photovoltaic power plants in multiple scenarios and large-scale applications.
[0027] According to one embodiment of this application, a power device connecting a single physical link is an edge node, and a power device connecting multiple physical links is a gateway node; The edge node is used to send the request data to the gateway node when it receives request data from the cloud service; The gateway node is configured to receive request data, extract the device identifier of the target power equipment carried in the request data, and if the device identifier exists in the locally stored network topology information, forward the request data to the physical link corresponding to the device identifier; if the device identifier does not exist in the locally stored network topology information, broadcast the request data through the currently connected physical link.
[0028] In this embodiment, by defining power devices connected to a single physical link as edge nodes and power devices connected to multiple physical links as gateway nodes, the functional responsibilities of different power devices in network communication can be determined, thereby improving the efficiency of cloud service request data processing in hybrid network scenarios.
[0029] Thirdly, this application provides a power device for performing the above-described method for obtaining network topology information.
[0030] Fourthly, this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the above-described method for obtaining network topology information.
[0031] Fifthly, this application provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the above-described method for obtaining network topology information.
[0032] Sixthly, this application provides a chip, which includes a processor and a communication interface, the communication interface being coupled to the processor, and the processor being used to run programs or instructions to implement the above-described method for obtaining network topology information.
[0033] Seventhly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method for obtaining network topology information.
[0034] The above-described one or more technical solutions in the embodiments of this application have at least one of the following technical effects: According to the network topology information acquisition method of this application, by generating first network information based on the first network topology information stored locally under the condition of meeting the target, and broadcasting the first network information through the currently connected physical link, it can actively share its link connection relationship and device identity information with other power devices on the link, and establish a topology information exchange mechanism between devices. By obtaining the second network information generated by the neighboring power devices based on the second network topology information stored locally, and updating the first network topology information stored locally, it can dynamically aggregate network connection relationships within a multi-hop range, realize the automatic perception and construction of topology structure in mixed network scenarios with multiple physical link types. Therefore, it does not need to rely on tedious topology configuration operations by manual means, reduces the workload of manual configuration for network deployment, improves the deployment efficiency of network, and thus better adapts to the efficient deployment needs of photovoltaic power plants in multiple scenarios and large-scale applications.
[0035] In some embodiments, by setting at least one of the following as target triggering conditions—power-on initialization completion, local storage network topology information update, change of the current physical link status, and change of communication interface status—network information generation and broadcast can be triggered at the moment of device startup, network structure change, physical connection status switch, or communication port status change. This improves the timeliness of topology information synchronization and can adaptively respond to various dynamic networking needs such as device network entry, link switching, and topology reconstruction, reducing invalid communication overhead and the frequency of manual intervention.
[0036] In some embodiments, by broadcasting separately for different physical links, power devices on each physical link can obtain the network information of the corresponding link. By carrying the link identification information of the corresponding physical link in the first network information, the power devices receiving the network information can identify the physical link type corresponding to the network information, distinguish the connection relationship of different links, and accurately associate and match the network information with the corresponding link, thereby further improving the accuracy of topology construction in mixed network scenarios with multiple physical link types.
[0037] In some embodiments, by acquiring the second network information generated and broadcast by neighboring power devices when the target conditions are met, it is possible to passively receive the topology information actively reported by neighboring devices, reducing the interaction overhead between devices. By sending query requests to neighboring power devices and acquiring the second network information, it is possible to actively acquire the network topology information of neighboring devices when needed, improving the flexibility of topology information acquisition and reducing the problem of incomplete topology information due to broadcast delays or loss. Therefore, by adopting a dual information acquisition method that combines active querying and passive reception, the accuracy of topology construction in mixed networking scenarios with multiple physical link types is further improved.
[0038] In some embodiments, by extracting the second network topology information from the second network information, the link connection relationship and device information corresponding to the neighboring power devices can be obtained. Based on these data, the device information of the neighboring power devices in the first network topology information stored locally can be updated. The local topology information can be corrected according to the actual status of the neighboring power devices, thereby improving the consistency between the network topology information maintained by each device and the real network structure.
[0039] In some embodiments, by detecting whether a topology loop exists before updating the first network topology information stored locally, unreasonable topology structures with data loop forwarding can be identified in advance before the topology information is updated, reducing problems such as repeated data forwarding, network congestion, and decreased communication efficiency caused by topology loops, and further improving the accuracy of network topology information updates.
[0040] In some embodiments, by obtaining the topology path after updating the device information of neighboring power devices with the second network topology information, the updated network connection path can be restored. This allows for the determination of whether a topology loop exists based on whether there are duplicate power devices on the same type of physical links in the topology path, thereby improving the accuracy and efficiency of topology loop determination.
[0041] In some embodiments, by configuring the updated first network topology information to include the target physical link currently connected and the device information of the n-level neighbor power devices connected on the target physical link, a global complete network topology or a local network topology can be constructed, and the local mode or global mode can be flexibly selected according to device performance, network scale and application scenario.
[0042] In some embodiments, a topology path is constructed through a data flow path, and the topology path is saved to the updated first network topology information. This allows for the recording and maintenance of service-related topology paths. If no data flow occurs on a topology path for a preset duration, the topology path is deleted, which reduces the occupation of system resources by redundant topology information and improves resource utilization.
[0043] In some embodiments, by updating the broadcast timeout based on the broadcast duration when the first network topology information is updated, the validity period of the network information broadcast is dynamically adjusted, reducing the broadcast lag or resource waste caused by fixed timeout time, improving the real-time performance of network communication, and thus better adapting to the timely synchronization requirements and accuracy of topology information in the dynamic networking environment of the power system.
[0044] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description
[0045] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. 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 the network topology information acquisition method provided in an embodiment of this application; Figure 2 This is a schematic diagram of the first network information provided in the embodiments of this application; Figure 3 This is one of the schematic diagrams of the power system architecture provided in the embodiments of this application; Figure 4 This is one of the network topology information of the power equipment provided in the embodiments of this application; Figure 5 This is the second type of network topology information for power equipment provided in the embodiments of this application; Figure 6 This is the third type of network topology information for power equipment provided in the embodiments of this application; Figure 7 This is the fourth type of network topology information for power equipment provided in the embodiments of this application; Figure 8 This is the fifth type of network topology information for power equipment provided in the embodiments of this application; Figure 9 This is the sixth type of network topology information for power equipment provided in the embodiments of this application; Figure 10 This is the seventh type of network topology information for power equipment provided in the embodiments of this application; Figure 11 This is the second schematic diagram of the power system architecture provided in the embodiments of this application; Figure 12 This is the eighth example of the network topology information for power equipment provided in this application embodiment; Figure 13 This is the ninth example of the network topology information for power equipment provided in the embodiments of this application; Figure 14 This is the tenth of the network topology information for power equipment provided in the embodiments of this application; Figure 15 This is the eleventh of the network topology information for power equipment provided in the embodiments of this application; Figure 16 This is the twelfth example of the network topology information for power equipment provided in the embodiments of this application; Figure 17This is the thirteenth type of network topology information for power equipment provided in the embodiments of this application; Figure 18 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation
[0047] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.
[0048] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.
[0049] The following description, in conjunction with the accompanying drawings, details the network topology information acquisition method, system, device, and medium provided in this application through specific embodiments and application scenarios.
[0050] The network topology information acquisition method provided in this application can be widely applied to various power systems related to power production, transmission, distribution, and monitoring and control, including new energy power generation systems, traditional power distribution systems, power storage systems, and integrated energy management systems. New energy power generation systems can include photovoltaic grid-connected power generation systems, wind power grid-connected power generation systems, and integrated photovoltaic-storage-charging systems. These power systems typically contain a large number of distributed devices, requiring data interaction between devices and information communication with the monitoring center. Traditional power distribution systems can include urban distribution network systems and industrial park distribution systems, involving communication needs of distributed terminals such as distribution switches, ring main units, and distribution transformer monitoring equipment. Of course, it can also be applied to other power systems, and this application does not limit this application.
[0051] The network topology information acquisition method provided in this application can be applied to hybrid networking scenarios in power systems where at least some power devices support at least two different types of physical links. In actual power system deployments, different types of physical links have their own transmission characteristics and applicable scenarios. For example, Power Line Communication (PLC) can utilize existing power lines for data transmission and is suitable for scenarios where cabling is difficult; Ethernet has the advantages of high bandwidth and low latency, making it suitable for large data volume transmission; wireless communication (such as WiFi, ZigBee, LoRa, etc.) is flexible in deployment and suitable for mobile devices or areas with limited cabling; RS485 bus is inexpensive and has strong anti-interference capabilities, making it suitable for short-distance device interconnection; fiber optic communication has large bandwidth, long transmission distance, and strong anti-electromagnetic interference capabilities, making it suitable for backbone network transmission. By supporting hybrid networking with multiple physical links, power systems can flexibly select communication methods according to device distribution, transmission requirements, and environmental conditions, improving the adaptability and reliability of the network.
[0052] In hybrid networking scenarios, the topology configuration of hybrid networks relies heavily on manual operation, which is time-consuming, labor-intensive, and inefficient, making it difficult to meet the high-efficiency deployment requirements of photovoltaic power plants in multiple scenarios and on a large scale.
[0053] The network topology information acquisition method provided in this application generates first network information based on locally stored first network topology information under certain target conditions and broadcasts the first network information through the currently connected physical links. It can proactively share its link connection relationship and device identity information with other power devices on the link, establishing a topology information exchange mechanism between devices. By acquiring second network information generated by neighboring power devices based on locally stored second network topology information and updating the locally stored first network topology information, it can dynamically aggregate network connection relationships within a multi-hop range. This achieves automatic perception and construction of topology structure in mixed network scenarios with multiple physical link types. Therefore, it eliminates the need for tedious manual topology configuration operations, reduces the workload of manual configuration for network deployment, and improves network deployment efficiency, thus better adapting to the efficient deployment needs of photovoltaic power plants in multiple scenarios and large-scale applications.
[0054] Depending on the power system, power equipment can be of different types. For example, in a photovoltaic grid-connected power generation system, power equipment may include photovoltaic inverters, photovoltaic module monitors, combiner boxes, grid-connected switches, etc.; in a wind power grid-connected power generation system, power equipment may include wind turbine controllers, pitch system actuators, yaw system monitoring equipment, wind power combiner equipment, etc.; in a power energy storage system, power equipment may include energy storage converters, battery management systems, energy storage battery pack monitoring units, energy storage system operation and maintenance terminals, etc.
[0055] The network topology information acquisition method provided in this application embodiment can be executed by power equipment in a power system. The following description uses power equipment as the execution subject to illustrate the network topology information acquisition method provided in this application embodiment.
[0056] like Figure 1 As shown, the method for obtaining network topology information includes steps 110, 120, 130, and 140.
[0057] Step 110: If the target conditions are met, generate the first network information based on the first network topology information stored locally; the first network topology information includes at least the target physical link currently connected and the device information of the neighboring power equipment connected on the target physical link.
[0058] In this application embodiment, the target conditions may include power-on initialization completion, local storage network topology information update, current connection physical link status change, and communication interface status change; they may also include the local storage first network topology information being updated for a preset time, receiving a topology reconstruction instruction, and entering a topology update cycle, etc. This application embodiment does not limit these conditions.
[0059] By setting at least one of the following as target trigger conditions: completion of power-on initialization, update of locally stored network topology information, change of the status of the currently connected physical link, and change of the communication interface status, network information generation and broadcast can be triggered at the moment of device startup, network structure change, physical connection status switch, or communication port status change. This improves the timeliness of topology information synchronization and can adaptively respond to various dynamic networking needs such as device network entry, link switching, and topology reconstruction, reducing invalid communication overhead and the frequency of manual intervention.
[0060] When the target conditions are met, the power equipment generates first network information based on the first network topology information stored locally. The first network topology information is topology relationship data maintained locally by the power equipment, which records the network connection relationships currently known to the power equipment. It may include the target physical link type (such as PLC, Ethernet, wireless, etc.), link identifier, communication parameters (such as baud rate, IP address range), and link connection status (connected / disconnected), etc.; it may also include the device information of neighboring power equipment connected on the target physical link, such as the device identifier, device type, communication address, link port identifier, and link quality parameters of the neighboring power equipment.
[0061] It should be noted that, in the initial state, the first network topology information may only include the information of the power equipment itself and the information of the detected direct neighbor power equipment.
[0062] The first network information is generated after the first network topology information has been standardized in format. It is topology data used for interaction between power equipment and may include the core data in the first network topology information.
[0063] In some embodiments, the content of the first network information is as follows: Figure 2 As shown, the data may include one or more types of information, such as protocol information, current frame information, and network topology information. Protocol information, current frame information, and network topology information can be combined into a single data frame or sent separately.
[0064] The protocol information may include the protocol version and extended information. The protocol version is used to indicate the compatibility of different versions of power equipment; the extended information is used to carry extended function information and can adopt a TLV structure, namely T: Type, L: Length, and V: Value.
[0065] Current frame information may include: Link Identifier: Used to identify the physical link from which data originates. Each power device uses a unified sequence number or identifier for each physical link, such as 1. FE (Fast Ethernet) network, 2. SUB1G network, 3. WIFI network, 4. CAN bus, etc. The sequence number of each physical link is not fixed and can be set as needed.
[0066] Unique Identifier: Unique information about the device, which can be a serial number (SN), a MAC address (Media Access Control) of any network, etc., used to uniquely identify the device.
[0067] Frame Identifier: Used to mark the type of the current frame, such as data frame, management frame, forwarding frame, etc.; used to characterize different frame functions, and can be used in combination or independently. If both the data frame identifier and the forwarding frame identifier are set, it indicates that this data is forwarded data and not from the original sender.
[0068] Frame time: The current frame transmission time, used to evaluate network frame status. When the sender sends a request, it needs a response from the other end. After the other end responds, the transmission delay can be measured.
[0069] Frame sequence number: Used to detect out-of-order data and as a marker for sending request acknowledgments.
[0070] Frame forwarding count: Used to indicate how many times the current frame has been forwarded to reach its destination, and is used to evaluate network stability.
[0071] Network topology information may include: Number of links: The broadcaster indicates how many physical links it supports.
[0072] Device information: The broadcaster describes how many other devices exist on its different physical links, in order to indirectly obtain information about other network topologies.
[0073] Device information may include: Current physical link: The physical link through which the broadcaster or device obtained the information.
[0074] Link score: A link score obtained by the broadcaster according to a certain link scoring mechanism. Unique device identifier: A unique identifier of the device collected by the broadcaster.
[0075] Network topology information: Information about other devices collected by the broadcaster, including the network topology information of other power devices obtained by this power device.
[0076] Step 120: Periodically broadcast the first network information through the currently connected physical link within the target duration.
[0077] The target duration can be configured based on factors such as the scale of power system equipment, the transmission rate of physical links, and topology update requirements. For example, in small power systems with fewer power devices and higher link transmission rates, the target duration can be set to a shorter time, such as 10-30 seconds; in large power systems with larger equipment and heavier link loads, the target duration can be appropriately extended, such as 60-120 seconds. By setting the target duration, neighboring power devices can stably receive the first network information, while reducing excessively frequent broadcast operations that consume too much link bandwidth and affect the normal transmission of other power system service data (such as power dispatch commands and equipment operating status data).
[0078] In this embodiment of the application, the power equipment can broadcast the first network information through the currently connected physical link according to a preset broadcast cycle (such as broadcasting once every 5 seconds) within the target duration, or it can select a physical link for broadcasting according to the physical link priority.
[0079] Step 130: Obtain the second network information of the neighboring power equipment; the second network information is generated based on the second network topology information stored locally by the neighboring power equipment.
[0080] In this embodiment of the application, the execution logic of the neighboring power devices of the executing subject (power device) of the method is consistent with that of the executing subject (power device). That is, the neighboring power devices will also generate second network information based on the second network topology information stored locally when the target conditions are met, and periodically broadcast the second network information within the target duration.
[0081] The structure and content of the second network topology information are the same as those of the first network topology information, including the physical link information currently connected to the neighboring power equipment and the information of the neighboring power equipment on the corresponding physical link; the second network information is the interactive data generated by the neighboring power equipment after standardizing the second network topology information, and the data format is the same as that of the first network information.
[0082] It should be noted that the first and second network topology information are network topology information stored by different power devices. For each power device, the network topology information stored locally is the first network topology information, and the network topology information stored locally by neighboring power devices is the second network topology information. The content and structure of the first and second network topology information can be found by referring to... Figure 2 The network topology information in the middle.
[0083] In this embodiment, when a power device broadcasts its first network information, it listens to the currently connected physical links and receives second network information broadcast by neighboring power devices. By receiving the second network information from neighboring power devices, the power device can learn about network connections beyond a one-hop range, such as information about other devices connected to by neighboring power devices through other physical links. This hop-by-hop information exchange mechanism allows the topology awareness range to gradually expand with each round of information interaction, thereby achieving the convergence of topology relationships within a multi-hop range.
[0084] Step 140: Update the locally stored first network topology information according to the second network information.
[0085] In this embodiment, the power equipment can parse the second network information, extract the network topology information, and compare and update it with the locally stored first network topology information. For example, it can add newly discovered power equipment nodes and link relationships, update the link status information of existing power equipment, and delete offline power equipment records that have timed out and not been updated.
[0086] In some embodiments, when the second network information contains device information (such as multi-hop neighboring power devices) and physical link information of neighboring power devices that are not stored by the power device, this information can be added to the first network topology information. When the neighboring power device status and link connection status contained in the second network information are inconsistent with the locally stored first network topology information (such as a neighboring power device adding a physical link or the link status changing from disconnected to connected), the data in the second network information is used to update the locally stored first network topology information. When the second network information does not contain locally stored neighboring device information and link information, and the power device confirms through link detection that the neighboring power device has exited operation or the link has been disconnected, this invalid information can be deleted from the local first network topology information to improve the accuracy of the topology data.
[0087] In some embodiments, after the first network topology information is updated, steps 110 and 120 can be executed to generate the first network information and broadcast the first network information periodically through the currently connected physical links within a target duration.
[0088] The network topology information acquisition method provided in this application realizes the automatic acquisition and maintenance of network topology information through autonomous interaction and self-updating between power equipment. It eliminates the need for manual participation in link identification, equipment ownership registration, and topology relationship entry, reducing the workload of manual configuration for network deployment and improving the on-site deployment efficiency of large-scale power systems. It is especially suitable for scenarios with a large number of devices, wide distribution, and complex link types in new energy power plants such as photovoltaic power stations.
[0089] Furthermore, the network topology information acquisition method provided in this application does not require additional independent topology management equipment, which reduces networking costs and the space occupied by equipment deployment and the workload of subsequent maintenance.
[0090] According to the network topology information acquisition method of this application, by generating first network information based on the first network topology information stored locally under the condition of meeting the target, and broadcasting the first network information through the currently connected physical link, it can actively share its link connection relationship and device identity information with other power devices on the link, and establish a topology information exchange mechanism between devices. By obtaining the second network information generated by the neighboring power devices based on the second network topology information stored locally, and updating the first network topology information stored locally, it can dynamically aggregate network connection relationships within a multi-hop range, realize the automatic perception and construction of topology structure in mixed network scenarios with multiple physical link types. Therefore, it does not need to rely on tedious topology configuration operations by manual means, reduces the workload of manual configuration for network deployment, improves the deployment efficiency of network, and thus better adapts to the efficient deployment needs of photovoltaic power plants in multiple scenarios and large-scale applications.
[0091] In some embodiments, broadcasting first network information periodically via the currently connected physical links within a target duration includes: Broadcasts are initiated for different physical links, and the first group of network information carries the link identification information of the corresponding physical link.
[0092] In this embodiment, since the power equipment supports multiple different types of physical links, each physical link differs in transmission medium, communication protocol, bandwidth characteristics, and coverage. Therefore, a broadcast operation can be initiated for each type of currently connected physical link. Specifically, the power equipment identifies the locally active physical link interface and sends the first network information to each interface, enabling the first network information to be sent to the neighboring devices connected to each physical link.
[0093] In some embodiments, to facilitate accurate identification of the information source by the receiving device, the first network information may carry link identification information corresponding to the physical link. The link identification information uniquely identifies the type of physical link through which the broadcast is transmitted. For example, it may include a link type code (e.g., 0x01 for PLC, 0x02 for Ethernet, 0x03 for wireless, etc.), a link port number, a link priority level, or link quality parameters.
[0094] In this embodiment, by broadcasting separately for different physical links, the power devices on each physical link can obtain the network information of the corresponding link. By carrying the link identification information of the corresponding physical link in the first network information, the power devices receiving the network information can identify the physical link type corresponding to the network information, distinguish the connection relationship of different links, and accurately associate and match the network information with the corresponding link, thereby further improving the accuracy of topology construction in mixed network scenarios with multiple physical link types.
[0095] In some embodiments, obtaining second network information of neighboring power devices includes: Obtain and broadcast the second group of network information generated by neighboring power devices when the target conditions are met; Alternatively, send an inquiry request to neighboring electrical equipment to obtain the second network information fed back by the neighboring electrical equipment based on the inquiry request.
[0096] In this embodiment, neighboring power devices can generate second network information based on locally stored second network topology information when they meet the target conditions, according to the logic in step 110. After generating the second network information, the neighboring power devices can periodically broadcast the second network information through their currently connected physical links within a target duration, according to the logic in step 120.
[0097] Power equipment can continuously monitor physical links that are currently in a normal connection state, capturing and filtering broadcast information transmitted on those links. Since multiple power devices in a power system may broadcast network information simultaneously, the power equipment can verify the captured broadcast information and filter out secondary network information broadcast by neighboring power devices.
[0098] In some embodiments, the power device can also send an inquiry request to neighboring power devices to obtain second network information fed back by the neighboring power devices based on the inquiry request. For example, the power device may trigger an active inquiry operation if it detects that the information of a neighboring power device in the local first network topology information is missing or abnormal, the power device does not receive broadcast information from a neighboring power device within a preset time period, or the power device receives a topology query instruction from an upper-level device.
[0099] After triggering an active query operation, a query request can be generated and sent to the neighboring power device via the currently connected physical link. The query request can include the power device's unique identifier (such as device serial number (SN) and MAC address), query type identifier, and request timestamp. Upon receiving the query request, the neighboring power device generates second-group network information based on its locally stored second-group network topology information and sends this information back to the power device.
[0100] In this embodiment, by acquiring the second network information generated and broadcast by neighboring power devices under the condition of meeting the target, it is possible to passively receive the topology information actively reported by neighboring devices, reducing the interaction overhead between devices. By sending query requests to neighboring power devices and acquiring the second network information, it is possible to actively acquire the network topology information of neighboring devices when needed, improving the flexibility of topology information acquisition and reducing the problem of incomplete topology information due to broadcast delays or loss. Therefore, by adopting a dual information acquisition method that combines active querying and passive reception, the accuracy of topology structure construction in mixed networking scenarios with multiple physical link types is further improved.
[0101] In some embodiments, updating the locally stored first network topology information according to the second network information includes: Extract the second network topology information from the second network information; Based on the second network topology information, update the device information of neighboring power devices in the locally stored first network topology information.
[0102] In this embodiment, after receiving the second network information, the second network information can be parsed and processed. According to the preset data format and field rules, the second network topology information of the neighboring power equipment can be extracted. Then, the equipment information of the neighboring power equipment in the locally stored first network topology information can be updated according to the second network topology information.
[0103] Specifically, the second network topology information can be compared with the locally stored first network topology information to determine the corresponding device information entries for neighboring power devices. The latest device information recorded in the second network topology information is then used to overwrite, supplement, or correct the original device information for the corresponding neighboring power devices in the local first network topology information, thereby achieving dynamic updates to the local network topology information.
[0104] In this embodiment, by extracting the second network topology information from the second network information, the link connection relationship and device information corresponding to the neighboring power devices can be obtained. Based on these data, the device information of the neighboring power devices in the locally stored first network topology information can be updated. The local topology information can be corrected according to the actual status of the neighboring power devices, thereby improving the consistency between the network topology information maintained by each device and the real network structure.
[0105] In a power system, various power devices are networked through multiple types of physical links. The network topology information of neighboring power devices may include information about multi-hop neighbor devices connected to the neighboring power devices themselves. If this network topology information is directly updated to the local first network topology information, it may cause the locally recorded network links to form a loop, i.e., a topology loop. This can lead to problems such as data packets being forwarded in a loop during data transmission, failing to reach the target power device normally. Consequently, link bandwidth is occupied, data transmission latency increases, and even communication failures occur in the entire control network. Therefore, in some embodiments, the device information of neighboring power devices in the locally stored first network topology information is updated according to the second network topology information, including: Detect whether there is a topology loop when updating the device information of neighboring power equipment in the second group of network topology information; If no topology loop is detected, update the device information of neighboring power devices in the first group of network topology information stored locally.
[0106] In this embodiment, a temporary network topology model can be constructed by combining the locally stored first network topology information and the device information of neighboring power devices in the extracted second network topology information. A preset topology loop detection algorithm is then used to traverse and analyze the temporary topology model to determine if a closed link loop exists. For example, depth-first search or breadth-first search algorithms can be used to traverse the connection relationships between power device nodes and physical links in the temporary topology model. The algorithm determines if there is a closed path that starts from a certain power device, passes through several power device nodes and physical links, and then returns to the same power device. If a closed path exists, a topology loop is detected; otherwise, no topology loop is detected.
[0107] If no loop is detected in the topology, it means that updating the device information of neighboring power devices in the second network topology information to the local first network topology information will not form a closed link loop and will not affect the normal communication of the power system. Therefore, the update operation can be performed.
[0108] In this embodiment, by detecting whether there is a topology loop before updating the first network topology information stored locally, unreasonable topology structures with data loop forwarding can be identified in advance before the topology information is updated. This reduces problems such as repeated data forwarding, network congestion, and decreased communication efficiency caused by topology loops, and further improves the accuracy of network topology information updates.
[0109] In some embodiments, detecting whether the device information updated from the second network topology information to the neighboring power equipment forms a topology loop includes: The topology path after obtaining the second group of network topology information and updating the device information of neighboring power equipment; If there are duplicate power devices on the same type of physical link in the topology path, a topology loop is determined to exist.
[0110] In this embodiment, the currently unupdated first network topology information can be used as a basis, and the device information of neighboring power devices in the extracted second network topology information can be temporarily imported to construct a temporary network topology structure. The topology paths in the temporary network topology structure can then be extracted.
[0111] Specifically, a power device can use itself as a node to traverse all power devices directly or indirectly connected to it, extracting the complete path from itself, through one or more physical links and several power devices, leading to other device nodes. Since at least some power devices in a power system support multiple types of physical links, and connections between different types of links do not form a data transmission loop, the topology path extraction can be categorized by physical link type. That is, topology paths on the same type of physical link are extracted separately, while topology paths on different types of physical links are processed independently.
[0112] Specifically, for each topology path extracted on the same type of physical link, node traversal and verification can be performed one by one to check whether the same power equipment is recorded repeatedly in a single topology path, that is, whether a certain power equipment appears twice or more in the same topology path.
[0113] If the same power device appears only once in a certain topological path, it means that the path is a one-way path and does not form a closed loop, and there is no topological loop. If the same power device appears twice or more in a certain topological path, it means that a closed link loop has been formed, and it is determined that there is a topological loop.
[0114] For example, in the topology path corresponding to an Ethernet link, if the extracted path is "Executive Entity (Power Equipment) → Neighbor Power Equipment A → Neighbor Power Equipment B → Neighbor Power Equipment A", then Neighbor Power Equipment A appears twice in this path, indicating that there are duplicate power equipment on the same type of physical link, and it is determined that there is a topology loop; if the path is "Executive Entity (Power Equipment) → Neighbor Power Equipment A → Neighbor Power Equipment B → Neighbor Power Equipment C", each device appears only once, and it is determined that there is no topology loop.
[0115] In this embodiment, by obtaining the topology path after the device information of the neighboring power equipment is updated from the second network topology information, the updated network connection path can be restored. Thus, based on whether there are duplicate power equipment on the same type of physical link in the topology path, it can be determined whether there is a topology loop, which improves the accuracy and efficiency of topology loop determination.
[0116] In some embodiments, the updated first network topology information includes: the device information of the currently connected target physical link and the n-level neighbor power devices connected on the target physical link; or the device information of each power device in the power system; wherein n is greater than or equal to 1.
[0117] In this embodiment, the updating of the first network topology information can be carried out in different ways depending on the network size of the power system, the computing power of the equipment, and the topology application requirements.
[0118] In some embodiments, a local topology maintenance mode can be adopted. The updated first network topology information includes the target physical link currently connected and the device information of the n-level neighbor power devices connected on the target physical link. Here, n is the neighbor level, and n≥1. The n-level neighbor represents the set of power devices that can be reached from a certain power device via a maximum of n physical links. For example, the level 1 neighbor power devices of the executing entity are the power devices that are directly connected to the executing entity through the target physical link, i.e., the direct neighbors of the executing entity; the level 2 neighbor power devices are the power devices that are directly connected to the level 1 neighbor power devices through the target physical link but do not have a direct connection relationship with the executing entity, i.e., the indirect neighbors of the executing entity; and so on, the n-level neighbor power devices are the power devices that are directly connected to the (n-1)-level neighbor power devices.
[0119] The executing entity can gradually aggregate multi-level neighbor device information on the target physical link based on the second-level network topology information fed back by neighboring power devices. Specifically, during the initial update, it can first obtain the device information of level 1 neighboring power devices to initially update the local first-level network topology information. As it continuously receives the second-level network topology information from each neighboring power device, the executing entity gradually extracts the device information of level 2, level 3, and even higher-level neighboring power devices and updates it to the local first-level network topology information, forming topology data containing information on n levels of neighboring power devices. The specific value of n can be set according to the actual needs of the power system. For example, in a small power system, n=1 can be set to update only the information of level 1 neighboring power devices, which can meet the topology management requirements and reduce the information processing load of each power device. In a large distributed power system, n≥3 can be set according to the device information processing capacity and topology control requirements, so that each power device can have a more comprehensive understanding of the network status on the target physical link.
[0120] In some embodiments, a global topology maintenance mode may be adopted, and the updated first network topology information includes the equipment information of each power device in the power system.
[0121] Specifically, as the implementing entity continuously receives the second network topology information broadcast or fed back by neighboring power devices and updates its local first network topology information, it gradually aggregates information from other power devices in the power system fed back by neighboring power devices. Through multiple rounds of topology information updates and aggregation, the implementing entity gradually improves its local first network topology information.
[0122] The following scenario example illustrates the topology information of the first network group under global topology maintenance mode. Figure 3 Taking the power system architecture shown as an example, it includes power equipment A, power equipment B, power equipment C, and power equipment D. Each power equipment supports communication methods such as WIFI and FE. Power equipment B and power equipment C are connected to a USB SUB1G communication network card. Each power equipment can act as an execution subject to perform each step of the above-mentioned network topology information acquisition method.
[0123] When each power device completes its power-on initialization, it can generate network information based on the locally stored network topology information and broadcast it. Due to the different data transmission speeds of different physical links, the network topology information between power device A and power device B via wired communication is generated as follows: Both devices first obtain their respective data topologies from the wired connection. Figure 4 and Figure 5 As shown.
[0124] Similarly, power equipment C and power equipment D also generate network topology information such as... Figure 6 and Figure 7 As shown, power equipment A and power equipment B contain each other's network topology information, and power equipment C and power equipment D contain each other's network topology information.
[0125] After the network topology information of each power device is updated, the generation and broadcast of network information will be triggered. After power device B and power device C interact, the generated network topology information is as follows: Figure 8 and Figure 9 As shown, with the generation and broadcast of network information, each power device gradually gathers information from other power devices in the power system fed back by neighboring power devices. Through multiple rounds of topology information updates and aggregation, the local first network topology information is gradually improved. The improved first network topology information of power device A is shown below. Figure 10 As shown, this includes the complete network topology of the power system.
[0126] The following scenario example illustrates the topology information of the first network group under the local topology maintenance mode. Figure 11 Taking the power system architecture shown as an example, it includes power equipment A, power equipment B, power equipment C, power equipment D, power equipment E and power equipment F. Each power equipment supports communication methods such as WIFI and FE. Each power equipment can act as an execution subject to execute each step of the above-mentioned network topology information acquisition method.
[0127] After power-on, each power device broadcasts information for a period of time. The first network topology information updated by each power device includes the target physical link and the device information of the first-level neighbor power devices connected to the target physical link. The resulting network topology information is as follows: Figure 12-17 As shown. Of course, in the local topology maintenance mode, the first network topology information updated by each power device can also include the device information of the target physical link and the second-level neighbor power devices connected on the target physical link, or the device information of higher-level neighbor power devices.
[0128] In this embodiment, by configuring the updated first network topology information to include the target physical link currently connected and the device information of the n-level neighbor power devices connected on the target physical link, a global complete network topology or a local network topology can be constructed. The local mode or global mode can be flexibly selected according to the device performance, network scale and application scenario.
[0129] The first network topology information in the local topology maintenance mode contains limited network topology information, and multiple addressing and broadcasting processes may occur during data transmission, which can easily lead to message flooding. Therefore, in some embodiments, the method further includes: Construct a topology path based on the data flow path in the power system in response to cloud service requests; Save the topology path to the updated first network topology information, and delete the topology path if there is no data flow for a preset duration.
[0130] In this embodiment, a cloud service request refers to various service requests initiated by power equipment in the power system (including the executing entity itself, neighboring power equipment of the executing entity, and other power equipment within the power system) to the cloud management platform, or various service requests initiated by the cloud management platform to power equipment in the power system, such as data upload requests, instruction issuance requests, status reporting requests, and operation and maintenance query requests. During the transmission of cloud service requests, a data flow path is formed, which reflects the actual communication links established between power equipment and the cloud, and between power equipment, to achieve cloud service interaction.
[0131] In this embodiment, cloud service request data frames transmitted within the power system can be captured via the currently connected physical link. The data frames are then parsed to extract the initiating device identifier, the target power equipment identifier (or cloud identifier), the identifiers of each intermediate power equipment traversed during data transmission, and the physical link type and identifier used during transmission. The extracted information is then integrated to reconstruct the data flow path corresponding to the cloud service request, forming a corresponding topology path.
[0132] After the topology path is constructed, it can be saved to the local first network topology information according to preset storage rules. For example, a unique path identifier can be assigned to the constructed topology path, and data such as the construction time of the topology path, the corresponding cloud service request type, and the power equipment on the path can be recorded and saved in the designated storage area of the first network topology information.
[0133] Because cloud service requests in power systems are dynamic, some topology paths may only have data flow within specific time periods. Storing topology paths with no data flow for extended periods would lead to redundancy in the local primary network topology information, increasing storage and management burdens. Therefore, after storing the topology paths, the data flow status of these paths can be monitored. During monitoring, the time of the last data flow on the topology path can be recorded, and a timer can be started to determine whether the topology path has been without data flow for a preset duration. The preset duration can be set according to the cloud service interaction frequency and topology update requirements of the power system, for example, it can be set to 30 minutes, 1 hour, or 24 hours.
[0134] If a certain topology path is found to have no data flow for a preset duration after the last data flow ends, that topology path can be deleted from the local first network topology information.
[0135] In this embodiment, a topology path is constructed through the data flow path and saved to the updated first network topology information. This allows for the recording and maintenance of service-related topology paths. If no data flow occurs on the topology path for a preset duration, the topology path is deleted, which reduces the occupation of redundant topology information on system resources and improves resource utilization.
[0136] In some embodiments, the method further includes: If the first network topology information is updated, the broadcast timeout is updated according to the broadcast duration.
[0137] In this embodiment, in order to improve the timeliness of network topology information broadcasting and network resource utilization efficiency, the status changes of the first network topology information stored locally can be monitored. When an update to the network topology information is detected, the broadcast timeout is recalculated and updated.
[0138] For example, if the original preset broadcast timeout is T, and the broadcast duration up to the time the first network topology information is updated is t, then the broadcast timeout can be updated to T+t. New network information can be generated based on the updated first network topology information and broadcast. The broadcast will be terminated when the broadcast timeout is reached.
[0139] In this embodiment, by updating the broadcast timeout based on the broadcast duration when the first network topology information is updated, the validity period of the network information broadcast is dynamically adjusted, reducing the broadcast lag or resource waste caused by fixed timeout time, improving the real-time performance of network communication, and thus better adapting to the timely synchronization requirements and accuracy of topology information in the dynamic networking environment of the power system.
[0140] This application also provides a power system including multiple power devices, at least some of which support at least two different types of physical links; The power equipment is used to perform the above-mentioned method for obtaining network topology information.
[0141] According to the power system of this application, by generating first network information based on locally stored first network topology information under the condition of meeting the target, and broadcasting the first network information through the currently connected physical links, it can actively share its link connection relationship and device identity information with other power devices on the link, and establish a topology information exchange mechanism between devices. By obtaining the second network information generated by neighboring power devices based on locally stored second network topology information and updating the locally stored first network topology information, it can dynamically aggregate network connection relationships within a multi-hop range, realizing the automatic perception and construction of topology structure in mixed networking scenarios with multiple physical link types. Therefore, it does not need to rely on tedious manual topology configuration operations, reduces the workload of manual configuration for network deployment, improves the deployment efficiency of network, and thus better adapts to the efficient deployment needs of photovoltaic power plants in multiple scenarios and large-scale applications.
[0142] In some embodiments, power devices connected to a single physical link are edge nodes, and power devices connected to multiple physical links are gateway nodes; Edge nodes are used to send request data to gateway nodes when they receive request data from cloud services; The gateway node is used to receive request data, extract the device identifier of the target power device carried in the request data, and forward the request data to the physical link corresponding to the device identifier if the device identifier exists in the locally stored network topology information; if the device identifier does not exist in the locally stored network topology information, the request data is broadcast through the currently connected physical link.
[0143] In this embodiment, a power device that connects to a single physical link can be defined as an edge node, which is typically deployed at the end of the network topology; a power device that connects to multiple physical links can be defined as a gateway node, which has the ability to exchange data across links.
[0144] When an edge node receives a request from a cloud service, it lacks path selection capabilities because it only has a single physical link connection. Therefore, it can send the request data to the gateway node connected to the edge node, which will then make routing decisions and forward the data.
[0145] For the gateway node, upon receiving request data, it first parses the data and extracts the device identifier of the target power device. This device identifier uniquely identifies the final destination node of the cloud service request. The gateway node then queries its locally stored network topology information to retrieve the reachable path record corresponding to the device identifier. If the device identifier exists in the network topology information, it means the gateway node has grasped the link mapping relationship to the target power device and can forward the request data to the physical link corresponding to that device identifier. If the gateway node does not find the device identifier of the target power device in its local network topology information, it means the target power device is outside the current gateway node's topology awareness range. In this case, it can initiate a broadcast forwarding mechanism, flooding the request data across the entire network through all currently connected physical links, exploring paths to the target power device through hop-by-hop broadcasting.
[0146] In this embodiment, by defining power devices connected to a single physical link as edge nodes and power devices connected to multiple physical links as gateway nodes, the functional responsibilities of different power devices in network communication can be determined, thereby improving the efficiency of cloud service request data processing in hybrid network scenarios.
[0147] This application also provides a power device for performing the above-described method for obtaining network topology information.
[0148] like Figure 18 As shown, this application embodiment also provides an electronic device 1800, including a processor 1801, a memory 1802, and a computer program stored in the memory 1802 and executable on the processor 1801. When the program is executed by the processor 1801, it implements the various processes of the above-described network topology information acquisition method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0149] Electronic devices can be the aforementioned power equipment, or components within power equipment, such as integrated circuits or chips.
[0150] This application also provides a non-transitory computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the various processes of the above-described network topology information acquisition method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here.
[0151] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.
[0152] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method for obtaining network topology information.
[0153] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.
[0154] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described network topology information acquisition method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0155] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.
[0156] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
[0157] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.
[0158] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.
[0159] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "illustrative embodiment," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.
[0160] Although embodiments of this application have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of this application, the scope of which is defined by the claims and their equivalents.
Claims
1. A method for obtaining network topology information, characterized in that, The method is applied to any electrical device in a power system, wherein at least some of the electrical devices support at least two different types of physical links; the method includes: Under the condition that the target conditions are met, first network information is generated based on the first network topology information stored locally; the first network topology information includes at least the target physical link currently connected and the device information of the neighboring power equipment connected on the target physical link. The first network information is broadcast periodically through the currently connected physical links within the target duration; Obtain the second network information of the neighboring power equipment; the second network information is generated based on the second network topology information stored locally by the neighboring power equipment. Update the locally stored first network topology information according to the second network information.
2. The method according to claim 1, characterized in that, The target condition includes at least one of the following: Power-on initialization complete; The locally stored network topology information has been updated; The physical link status of the current connection has changed; The communication interface status has changed.
3. The method according to claim 1, characterized in that, The step of periodically broadcasting the first network information through the currently connected physical links within a target duration includes: Broadcasts are initiated for different physical links, and the first network information carries the link identification information of the corresponding physical link.
4. The method according to claim 1, characterized in that, The acquisition of the second network information of the neighboring power equipment includes: The second network information generated and broadcast by the neighboring power devices under the condition that the target conditions are met is obtained; Alternatively, an inquiry request can be sent to the neighboring power equipment to obtain the second network information fed back by the neighboring power equipment based on the inquiry request.
5. The method according to claim 1, characterized in that, The step of updating the locally stored first network topology information according to the second network information includes: Extract the second network topology information from the second network information; Based on the second network topology information, the device information of the neighboring power devices in the first network topology information stored locally is updated.
6. The method according to claim 5, characterized in that, The step of updating the device information of neighboring power devices in the locally stored first network topology information according to the second network topology information includes: Detect whether the device information updated from the second group network topology information to the neighboring power equipment forms a topology loop; If no topology loop is detected, the device information of the neighboring power devices in the first network topology information stored locally is updated.
7. The method according to claim 6, characterized in that, The step of detecting whether the device information updated from the second network topology information to the neighboring power equipment forms a topology loop includes: Obtain the topology path after updating the device information of the neighboring power equipment with the second group network topology information; If there are duplicate power devices on the same type of physical link in the topology path, it is determined that a topology loop exists.
8. The method according to claim 1, characterized in that, The updated first network topology information includes: the device information of the currently connected target physical link and the n-level neighbor power devices connected on the target physical link; or the device information of each power device in the power system; wherein n is greater than or equal to 1.
9. The method according to claim 1, characterized in that, The method further includes: A topology path is constructed based on the data flow path in the power system in response to cloud service requests. The topology path is saved to the updated first network topology information, and the topology path is deleted if there is no data flow for a preset period of time.
10. The method according to claim 1, characterized in that, The method further includes: If the topology information of the first network group is updated, the broadcast timeout is updated according to the broadcast duration.
11. An electric power system, characterized in that, It includes multiple power devices, at least some of which support at least two different types of physical links; The power equipment is used to perform the method as described in any one of claims 1-10.
12. The power system according to claim 11, characterized in that, Power devices that connect to a single physical link are called edge nodes, and power devices that connect to multiple physical links are called gateway nodes. The edge node is used to send the request data to the gateway node when it receives request data from the cloud service; The gateway node is used to receive request data, extract the device identifier of the target power equipment carried in the request data, and forward the request data to the physical link corresponding to the device identifier if the device identifier exists in the locally stored network topology information. If the device identifier is not present in the locally stored network topology information, the request data is broadcast through the currently connected physical link.
13. An electrical device, characterized in that, Used to perform the method as described in any one of claims 1-10.
14. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the method as described in any one of claims 1-10.
15. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-10.