A method and system for standardizing access of power grid equipment based on a hon g meng system

Abstract

The application discloses a power grid equipment access standardization method and system based on a Hongmeng system, and the method creates a standardized architecture based on an HDF driving framework of the Hongmeng system, carries out interface standardization processing through a hardware access layer, can automatically adapt to power grid equipment of different manufacturers and different types, does not need manual intervention for driving development, truly realizes that equipment is 'plug and play', greatly reduces the time and labor cost of equipment access, carries out protocol standardization processing through a protocol conversion layer, completely solves the multi-protocol compatibility problem, carries out security standardization processing by using a security enhancement layer, can effectively prevent security threats such as equipment counterfeiting and man-in-the-middle attacks, and meets the high security requirements of the power system on equipment access. In addition, batch collaborative access of group equipment can be realized, manual operation is not needed, the efficiency of large-scale equipment access is greatly improved, resource dispersion is avoided, system load is reduced, and the efficiency and scalability of access management are improved.

Description

Technical Field

[0001] This invention relates to the field of equipment access standardization technology, and in particular, to a method and system for standardizing power grid equipment access based on the HarmonyOS system, electronic equipment, and computer-readable storage medium. Background Technology

[0002] The construction of new power systems has become a core direction of energy transformation. New power elements such as distributed photovoltaics, wind power, energy storage devices, and electric vehicle charging piles are rapidly becoming widespread. Simultaneously, the digital transformation of the power industry is accelerating, significantly increasing the demand for interconnected and collaborative equipment, efficient data flow, and intelligent operation and maintenance. Against this backdrop, the standardization of grid equipment access has become a core prerequisite for overcoming system compatibility bottlenecks and supporting the implementation of new power systems. However, current technologies in the power industry still have many pain points and are difficult to meet actual needs. For example, Chinese invention patent application CN119691724A discloses a device access and monitoring method, system, and storage medium based on a HarmonyOS terminal. This technical solution includes receiving access requests and information data from at least one device through a HarmonyOS terminal and transmitting the device's information data to an information processing module; based on the device's information data, the information processing module performs access authentication on the device and generates an authentication result; when the authentication result is successful, access success information is generated on the interactive terminal, allowing the device to access the HarmonyOS terminal; for devices accessing the HarmonyOS terminal, the working data of the device is synchronized to the interactive terminal in real time through the HarmonyOS terminal and the information processing module within a preset interval. However, this technical solution does not implement the protocol conversion process and does not define a unified hardware access standard or interface specification, which limits the range of access devices. When adding new devices, repeated adaptation and debugging are required, making it difficult to achieve efficient "plug and play" access. At the same time, the above solution does not involve protocol conversion logic, only synchronizing raw working data. It does not achieve the unification of common standards in the power grid industry, and does not consider the limited bandwidth and latency sensitivity of power grid edge nodes. Directly transmitting raw data can easily lead to link congestion and fail to meet real-time control requirements. In addition, the above solution does not mention the distributed collaboration mechanism between the HarmonyOS terminal and the information processing module. When the number of access devices reaches hundreds or even thousands, it will lead to computing resource overload, resulting in problems such as request response delays, authentication timeouts, and data synchronization lag. Summary of the Invention

[0003] This invention provides a standardized method and system for power grid equipment access based on the HarmonyOS system, as well as electronic devices and computer-readable storage media. It enables plug-and-play functionality for power grid equipment, converts proprietary protocols into industry-standard protocols, completely solves the multi-protocol compatibility problem, effectively prevents security threats such as device forgery and man-in-the-middle attacks, meets the high security requirements of power systems for equipment access, and significantly improves the efficiency of large-scale equipment access, the efficiency of access management, and scalability.

[0004] According to one aspect of the present invention, a method for standardizing the access of power grid equipment based on the HarmonyOS system is provided, comprising the following: A standardized architecture is created based on the HDF driver framework of the HarmonyOS system. The standardized architecture includes a hardware access layer, a protocol conversion layer, and a security enhancement layer. The hardware access layer is used to standardize the interfaces of the grid devices to be connected. The protocol conversion layer is used to standardize the protocols of the grid devices to be connected. The security enhancement layer is used to standardize the security of the grid devices to be connected. The system acquires the grid equipment to be connected and performs interface standardization, protocol standardization, and security standardization on it using the hardware access layer, protocol conversion layer, and security enhancement layer, respectively. The standardized power grid equipment is registered in the access terminal to complete the power grid equipment access.

[0005] Furthermore, the process of standardizing the interfaces of power grid equipment using the hardware access layer includes the following: Interact with the grid equipment to be connected, collect parameter data of the grid equipment to be connected, and map the parameter data into a standardized metadata model; The standardized metadata model is matched with the meta-model of the driver template in the power grid equipment driver template library to obtain the matched driver template; Based on the matching driver template, the device-private driver functions built into the power grid device to be connected are mapped to the HDF standard interface function set. If no driver template is matched, the parameter data of the power grid device to be connected is semantically parsed to obtain the functional semantics corresponding to the parameter data. Multiple rounds of exploratory interaction are conducted with the device to be connected to generate the optimal driver call sequence for the adapted device. The functional semantics and the optimal driver call sequence are encapsulated into temporary matching rules. Based on the temporary matching rules, the device-private driver functions built into the power grid device to be connected are mapped to the HDF standard interface function set.

[0006] Furthermore, it also includes the following: When the number of times similar grid devices to be connected is detected to reach a preset threshold, the temporary matching rules are converted into new driver templates and updated synchronously in the grid device driver template library.

[0007] Furthermore, the process of standardizing the protocols of power grid equipment using the protocol conversion layer includes the following: The original protocol of the equipment to be connected to the power grid is obtained and parsed to get the protocol fields; Construct a semantic standard mapping knowledge graph, match the protocol fields in the mapping knowledge graph, and convert the protocol fields into the power grid industry standard format based on the matching results to obtain a standardized protocol; The system senses the operating scenario of the equipment to be connected to the power grid. If the operating scenario is an edge scenario, the standardized protocol is lightweighted to obtain a lightweight protocol.

[0008] Furthermore, regarding the sensing of the operating scenario of the grid equipment to be connected, if the operating scenario is an edge scenario, the standardized protocol is lightweighted to obtain the lightweight protocol. The process includes the following: Obtain the operating status commands, network environment data, and operating conditions of the equipment to be connected to the power grid; Based on the aforementioned operating status instructions, the power grid business-data mapping strategy library is invoked to determine the protocol fields that need to be reconstructed; Based on the network environment data, determine whether the environment in which the power grid device to be connected is an edge scenario; If it is determined to be an edge scenario, the optimal trimming strategy is selected from the predefined lightweight strategy library based on the operating conditions, and the protocol fields that need to be reconstructed are trimmed based on the optimal trimming strategy to trim the standardized protocol into a lightweight protocol.

[0009] Furthermore, it also includes the following: The lightweight protocol undergoes syntax verification, semantic verification, interaction verification, and twin pre-verification. Syntax verification includes checking whether the protocol conforms to the frame structure specifications of the power grid industry standard protocol and determining whether the syntax error rate exceeds a preset error rate threshold. Semantic verification includes comparing whether the semantics of the protocol fields before and after conversion are consistent. Interaction verification includes simulating the access terminal to send standardized control commands and checking whether the response of the device to be accessed conforms to the protocol specifications. Twin pre-verification includes calling the digital twin of the power grid device to be accessed, simulating the execution of the standardized control commands to be issued in the digital twin, analyzing the state of the digital twin after the execution of the standardized control commands, obtaining simulation results, and determining whether the simulation results violate preset power grid safety operation rules.

[0010] Furthermore, the process of applying a security enhancement layer to standardize the safety of power grid equipment includes the following: Obtain the device certificate stored in the hardware security module built into the device to be connected to the power grid. Perform hierarchical verification between the device certificate and the system root certificate of the access terminal. After the verification is successful, extract the public key of the device to be connected to the power grid and then randomly generate a challenge code. After the device to be connected to the power grid signs the challenge code with its private key, verify the validity of the signature with the public key of the device to be connected to the power grid. If the verification is successful, the security standardization is completed and the power grid device is allowed to access the grid.

[0011] In addition, the present invention also provides a standardized system for grid equipment access based on the HarmonyOS system, comprising: A standardized architecture creation module is used to create a standardized architecture based on the HDF driver framework of the HarmonyOS system. The standardized architecture includes a hardware access layer, a protocol conversion layer, and a security enhancement layer. The hardware access layer is used to perform interface standardization processing on the grid devices to be connected, the protocol conversion layer is used to perform protocol standardization processing on the grid devices to be connected, and the security enhancement layer is used to perform security standardization processing on the grid devices to be connected. The equipment standardization processing module is used to acquire the power grid equipment to be connected, and to perform interface standardization processing, protocol standardization processing, and security standardization processing on it using the hardware access layer, protocol conversion layer, and security enhancement layer, respectively. The device registration module is used to register standardized power grid devices in the access terminal, thereby completing the power grid device access.

[0012] In addition, the present invention also provides an electronic device, including a processor and a memory, wherein the memory stores a computer program, and the processor executes the steps of the method described above by calling the computer program stored in the memory.

[0013] In addition, the present invention also provides a computer-readable storage medium for storing a computer program for standardizing the access of power grid equipment based on the HarmonyOS system, wherein the computer program executes the steps of the method described above when running on a computer.

[0014] The present invention has the following beneficial effects: This invention presents a standardized method for power grid equipment access based on the HarmonyOS system. It establishes a standardized architecture based on the HarmonyOS HDF driver framework, comprising a hardware access layer, a protocol conversion layer, and a security enhancement layer. After acquiring the power grid equipment to be accessed, the hardware access layer performs interface standardization, automatically adapting to different manufacturers and types of power grid equipment without manual intervention in driver development, truly achieving "plug and play" and significantly reducing the time and labor costs of equipment access. The protocol conversion layer performs protocol standardization, converting proprietary protocols into industry-standard protocols, completely resolving multi-protocol compatibility issues. The security enhancement layer performs security standardization, effectively preventing security threats such as device forgery and man-in-the-middle attacks, meeting the high security requirements of power systems for equipment access. Furthermore, the standardized architecture is built upon the HDF driver framework, which adopts a master-slave design, enabling batch collaborative access of group devices without manual operation, significantly improving the efficiency of large-scale device access, avoiding resource dispersion, reducing system load, and enhancing the efficiency and scalability of access management.

[0015] In addition, the standardized system for power grid equipment access based on the HarmonyOS system of the present invention also has the above-mentioned advantages.

[0016] In addition to the objectives, features, and advantages described above, the present invention has other objectives, features, and advantages. The invention will now be described in further detail with reference to the figures. Attached Figure Description

[0017] The accompanying drawings, which form part of this application, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an undue limitation of the invention. In the drawings: Figure 1 This is a flowchart illustrating a preferred embodiment of the standardization method for power grid equipment access based on the HarmonyOS system in this application. Figure 2 yes Figure 1 A schematic diagram of the sub-process of step S2; Figure 3 yes Figure 1 Another sub-process diagram of step S2; Figure 4 yes Figure 1 A schematic diagram of another sub-process of step S2; Figure 5 yes Figure 4 A schematic diagram of the sub-process of step S23b; Figure 6 yes Figure 4 Another sub-process diagram of step S23b; Figure 7This is a schematic diagram of the module structure of a standardized system for accessing power grid equipment based on the HarmonyOS system, according to another embodiment of this application. Detailed Implementation

[0018] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0019] Reference Figure 1 A preferred embodiment of this application provides a standardization method for power grid equipment access based on the HarmonyOS system, including the following: Step S1: Create a standardized architecture based on the HDF driver framework of the HarmonyOS system; wherein, the standardized architecture includes a hardware access layer, a protocol conversion layer and a security enhancement layer, the hardware access layer is used to perform interface standardization processing on the grid equipment to be accessed, the protocol conversion layer is used to perform protocol standardization processing on the grid equipment to be accessed, and the security enhancement layer is used to perform security standardization processing on the grid equipment to be accessed. Step S2: Obtain the power grid equipment to be connected, and perform interface standardization, protocol standardization, and security standardization on it using the hardware access layer, protocol conversion layer, and security enhancement layer respectively; Step S3: Register the standardized power grid equipment in the access terminal to complete the power grid equipment access.

[0020] It is understood that the standardized grid device access method based on the HarmonyOS system in this embodiment creates a standardized architecture based on the HarmonyOS HDF driver framework. This standardized architecture includes a hardware access layer, a protocol conversion layer, and a security enhancement layer. After acquiring the grid devices to be accessed, the hardware access layer performs interface standardization processing, automatically adapting to different manufacturers and types of grid devices without manual intervention in driver development, truly achieving "plug and play" for devices and significantly reducing the time and manpower costs of device access. The protocol conversion layer performs protocol standardization processing, converting proprietary protocols into industry-standard protocols, completely solving the multi-protocol compatibility problem. The security enhancement layer performs security standardization processing, effectively preventing security threats such as device forgery and man-in-the-middle attacks, meeting the high security requirements of power systems for device access. Furthermore, the standardized architecture is built on the HDF driver framework, which adopts a master-slave mode design, enabling batch collaborative access of group devices without manual operation, significantly improving the efficiency of large-scale device access, avoiding resource dispersion, reducing system load, and improving the efficiency and scalability of access management.

[0021] In step S1, the HarmonyOS HDF driver framework provides unified hardware resource management, driver loading management, and device node management. It adopts a master-slave design, consisting of a device manager and device hosts. The device manager centrally manages multiple device hosts, with drivers for the same type of device deployed on the same host. The device manager provides unified driver management; upon startup, it provides driver information based on device conditions, loads the corresponding driver device host, and controls the device host to complete driver loading. The device host provides the environment for driver execution and, in conjunction with the pre-configured host framework, collaborates with the device manager to complete driver loading and invocation. Developers should place devices of the same type on the same host. When adding a new device, they should check if a host of the same type already exists. If a host already exists, the device should be configured on that host. Duplicate host configurations are prohibited. A driver device should belong to only one driver type; therefore, configuring the same device on different hosts is also prohibited, thus achieving centralized management and unified scheduling of drivers of the same type.

[0022] It is understandable that existing technologies typically employ a single-device, one-to-one access mode. When the number of access devices reaches hundreds or even thousands, this can easily lead to problems such as computing resource overload, authentication timeouts, and data synchronization lag. Furthermore, the dispersed deployment of drivers for similar devices results in low management efficiency and makes it difficult to support the batch access and collaborative control of large-scale devices. This invention, however, creates a standardized architecture based on the HDF driver framework of the HarmonyOS system. Compared to existing technologies, the master-slave design of the HDF driver framework facilitates the batch collaborative access of group devices, eliminating the need for manual operation one by one and significantly improving the efficiency of large-scale device access. Moreover, the master-slave driver deployment avoids resource dispersion, reduces system load, and improves the efficiency and scalability of access management. The standardized architecture includes a hardware access layer, a protocol conversion layer, and a security enhancement layer. The hardware access layer is used for interface standardization processing of the grid devices to be accessed; the protocol conversion layer is used for protocol standardization processing of the grid devices to be accessed; and the security enhancement layer is used for security standardization processing of the grid devices to be accessed.

[0023] In addition, in step S2, after obtaining the power grid equipment to be connected, interface standardization, protocol standardization, and security standardization are performed on it using the hardware access layer, protocol conversion layer, and security enhancement layer, respectively. For example, Figure 2 As shown, the process of standardizing the interfaces of power grid equipment using the hardware access layer includes the following: Step S21a: Interact with the grid equipment to be connected, collect parameter data of the grid equipment to be connected, and map the parameter data into a standardized metadata model; Step S22a: Match the standardized metadata model with the meta-model of the driver template in the power grid equipment driver template library to obtain the matched driver template; Step S23a: Based on the matched driver template, map the device-private driver functions built into the power grid device to the HDF standard interface function set; if no driver template is matched, perform semantic parsing on the parameter data of the power grid device to be connected to obtain the functional semantics corresponding to the parameter data, conduct multiple rounds of exploratory interaction with the device to be connected, generate the optimal driver call sequence for the adapted device, encapsulate the functional semantics and the optimal driver call sequence into a temporary matching rule, and map the device-private driver functions built into the power grid device to the HDF standard interface function set based on the temporary matching rule.

[0024] Specifically, the intelligent detection module of the hardware access layer first actively interacts with the power grid equipment to be connected, collecting parameter data of the equipment. The parameter data includes equipment model, manufacturer information, original interface type (such as RS485, CAN, Ethernet, fiber optic, etc.), communication baud rate, signal level standard, etc., and maps the parameter data into a standardized metadata model. The standardized metadata model has a three-level structure, where the first level is the basic equipment information layer, including equipment model, manufacturer, access time, etc.; the second level is the interface feature layer, mapping the interface type, pin definition and electrical characteristic parameters in the physical interface parameters, etc.; and the third level is the data interaction layer, mapping the baud rate, verification method, etc. in the communication parameters.

[0025] Then, the standardized metadata model is matched with the meta-model of the driver templates in the power grid equipment driver template library to obtain a matched driver template. The specific matching process is as follows: The graph structure similarity between the standardized metadata model and the meta-model is calculated. The purpose of the graph structure similarity calculation is to determine whether the business semantics (e.g., overcurrent protection value, A-phase voltage measurement, etc.) in the standardized metadata model are consistent with the functional semantics supported by the power grid equipment driver template. For example, the "equipment type" (e.g., protection device, measurement and control device) in the equipment basic information layer of the standardized metadata model is matched with the "applicable equipment category" in the power grid equipment driver template to filter out the common driver logic for similar equipment; the "interface driver identifier" in the interface feature layer of the standardized metadata model is matched with the "template identifier" in the power grid equipment driver template. Perform precise matching to ensure that the power grid equipment driver template supports this type of physical interface; perform interval matching between the "communication parameter range" of the data interaction layer in the standardized metadata model and the "parameter compatibility range" of the power grid equipment driver template to verify the power grid equipment driver template's support capability for the current device's baud rate and verification method; the matching process can be automatically executed by the HarmonyOS system's driver adaptation engine. When the matching degree is ≥95%, the adaptation is confirmed to be successful; otherwise, the dynamic adjustment mechanism of the power grid equipment driver template is triggered.

[0026] As an example, assume the standardized metadata model of the equipment to be connected to the power grid is as follows: Node 1 (Equipment Type): Circuit Breaker - [Attributes] --> Model: NM63-2025; Node 2 (Function): Overcurrent Protection - [Attributes] --> Action Value: 0.5-1.5 times rated; Node 3 (Function): Status Monitoring - [Attributes] --> Remote Signaling: Open / Close / Fault; Node 4 (Interface): RS485 - [Attributes] --> Baud Rate: 9600; Edge 1: Equipment Type - [Available] --> Function (Overcurrent Protection); Edge 2: Equipment Type - [Available] --> Function (Status Monitoring); Edge 3: Equipment Type - [Through] --> Interface (RS485). The metamodel of candidate driver template A in the matched driver template library is as follows: Node A (Applicable Category): Circuit Breaker; Node B (Supported Function): Overcurrent Protection - [Attribute] --> Action Value: Settable; Node C (Supported Function): Status Monitoring - [Attribute] --> Signal: Open / Close; Node D (Compatible Interface): RS485 - [Attribute] --> Baud Rate: 9600, 19200; Edge A: Applicable Category - [Implementation] --> Supported Function (Overcurrent Protection); Edge B: Applicable Category - [Implementation] --> Supported Function (Status Monitoring); Edge C: Applicable Category - [Requirement] --> Compatible Interface (RS485). The specific process for calculating graph structure similarity is as follows: First, calculate the semantic similarity of corresponding nodes in the two metadata models. For example, "circuit breaker" and "circuit breaker" are completely matched (similarity 1.0), "overcurrent protection" and "overcurrent protection" are completely matched (similarity 1.0), "status monitoring" and "status monitoring" are completely matched (similarity 1.0), and "RS485" and "RS485" are completely matched (similarity 1.0). Then, perform edge relationship matching, specifically by calculating the matching degree of edges in the two metadata models. For example, the [possess] relationship and the [implement] relationship are highly similar in functional semantics (similarity 1.0). (The value is 0.9). Next, the graph structure similarity is synthesized. Specifically, the matching scores of all nodes and edges are combined, and their weights in the semantics of power grid business are considered (e.g., the weight of functional nodes is higher than that of interface nodes). The overall similarity is calculated by a graph matching algorithm (e.g., embedding methods based on graph edit distance or graph neural networks). In this example, the calculated overall graph structure similarity reaches 98%. Finally, a decision is made. Specifically, if the current overall graph structure similarity is 98%, which is greater than 95% (preset threshold), then it is confirmed that the driver template A is highly compatible with the power grid equipment to be connected, and the driver template is automatically loaded to complete the subsequent mapping.

[0027] If a driver template is successfully matched, the device-specific driver functions built into the grid-connected equipment are mapped to the HDF standard interface function set based on the matched driver template. These device-specific driver functions include vendor-defined device initialization functions (such as VendorSpecificInit()) for configuring device registers and starting hardware modules; private data read / write functions (such as CustomReadReg() / CustomWriteCmd()) using vendor-specific data frame formats and verification logic; and device status monitoring functions (such as DeviceStatusCheck()) returning vendor-defined private status codes. The HDF standard interface function set includes DevInit(): device initialization (including register configuration and baud rate setting); DevRead() / DevWrite(): data read / write operations (supporting blocking / non-blocking modes); DevCtrl(): device control (such as parameter configuration and status query); and DevRelease(): resource release. The mapping process specifically involves encapsulating the functional logic of VendorSpecificInit() into the HDF standard DevInit() interface, converting the data reading logic of CustomReadReg() into the unified calling format of DevRead(), and so on. After mapping, the private function serves only as the underlying implementation of the standard interface, exposing the HDF standardized call entry point to the outside world.

[0028] In addition, if the driver template is not successfully matched, the intelligent detection module will call the built-in device autonomous cognition engine to generate temporary matching rules. The device autonomous cognition engine uses the built-in power grid-specific large model to perform semantic analysis on the parameter data of the device to be connected to the power grid, infer the functional semantics corresponding to the parameter data, and conduct multiple rounds of exploratory interactions with the device to be connected to the power grid based on a preset deep reinforcement learning model, including issuing exploratory instructions, receiving feedback data, and adjusting the interaction strategy to generate the optimal driver call sequence for the device. The parsed functional semantics and the optimal driver call sequence generated by the interaction are then encapsulated into temporary matching rules, and the device-private driver functions built into the device to be connected to the power grid are mapped to the HDF standard interface function set based on the temporary matching rules.

[0029] Optional, such as Figure 3 As shown, the process of standardizing the interfaces of power grid equipment using the hardware access layer also includes the following: Step S24a: When the number of access attempts of similar grid devices reaches a preset threshold, the temporary matching rule is converted into a new driver template and updated synchronously in the grid device driver template library.

[0030] It is understandable that power grid equipment is diverse in type and interface (such as RS485, CAN, Ethernet, etc.), and the proprietary driver functions of these devices are incompatible with each other. Traditional device access methods rely on manual adaptation and driver development. When adding new devices, protocol parsing and interface debugging must be repeated, making it difficult to achieve "plug and play." The access cycle is long and the labor cost is high, which seriously restricts the rapid deployment and operation and maintenance efficiency of large-scale equipment. This invention creates a hardware access layer in the HDF driver framework of the HarmonyOS system. The hardware access layer actively interacts with the power grid equipment to be connected through a built-in intelligent detection module, collects device information, and maps it into a standardized metadata model containing a three-level structure of basic device information, interface characteristics, and data interaction. Then, the standardized metadata model is compared with the metamodel attached to the driver template in the power grid equipment driver template library to calculate the graph structure similarity. The matching degree is comprehensively evaluated from multiple dimensions. When the matching degree reaches a preset threshold, the corresponding driver template is automatically loaded. When there is no matching template, the intelligent detection module calls the device's autonomous cognition engine to generate the optimal driver call sequence, dynamically encapsulates it into temporary rules for mapping, and after the number of accesses of similar devices reaches a threshold, the temporary rules are automatically converted into fixed templates. Therefore, traditional driver adaptation relies on precise identifier matching, which cannot handle devices without pre-installed support. In contrast, the device autonomous cognition engine of this invention achieves zero-sample adaptation through semantic parsing of a large-scale power grid model combined with deep reinforcement learning. Traditional driver adaptation lacks self-learning capabilities, while the device autonomous cognition engine can automatically convert temporary rules into templates that can be reused when similar devices are connected, thus accumulating knowledge. Traditional driver adaptation, which requires weeks of manual driver development, can achieve automatic adaptation within minutes, significantly improving efficiency. Therefore, the interface standardization process of this invention requires no manual intervention in driver development, significantly reducing the time and labor costs for device access and truly achieving a "plug and play" effect. In addition, such as Figure 4 As shown, the process of standardizing the protocol of power grid equipment using the protocol conversion layer includes the following: Step S21b: Obtain the original protocol of the equipment to be connected to the power grid and parse it to obtain the protocol fields; Step S22b: Construct a semantic standard mapping knowledge graph, match the protocol fields in the mapping knowledge graph, and convert the protocol fields into the power grid industry standard format based on the matching results to obtain a standardized protocol; Step S23b: Sensing the operating scenario of the equipment to be connected to the power grid. If the operating scenario is an edge scenario, the standardized protocol is lightweighted to obtain a lightweight protocol.

[0031] Specifically, the protocol parsing engine of the protocol conversion layer first parses the original protocol of the grid equipment to be connected to obtain the protocol fields. For example, for manufacturer-specific protocols, the protocol parsing engine can identify the frame start character, frame length field, function code field, and data field format through a preset protocol feature library, and extract the protocol fields using a recursive descent analysis method. For general protocols such as Modbus and DL / T 645, the protocol parsing engine can directly call the pre-compiled protocol parsing plugin to extract the protocol fields. At the same time, during the parsing process, the integrity of the data frame is verified by CRC check, frames that fail the check are discarded, and an exception log is recorded.

[0032] Then, a semantic standard mapping knowledge graph is constructed based on the logical node model using power industry standard protocols (such as IEC 61850). Specifically, the mapping knowledge graph includes a field mapping table, data type conversion rules, and service mapping rules. The field mapping table is used to establish a correspondence between the parsed private protocol fields and IEC 61850 data objects. For example, the "current sampling value" field of the manufacturer's private protocol is mapped to "MMXU1.A.phsA.cVal.mag.f". The service mapping rules are used to map private control commands (such as 0x01 representing closing) to IEC 61850 MMS services (such as Operate service) and supplement the parameters required for the service. The rule base supports dynamic updates and can be synchronized to each access terminal through the distributed configuration center of the HarmonyOS system. The protocol fields are then matched against the mapped knowledge graph. Based on the matching results, the protocol fields are converted into the power grid industry standard format to obtain a standardized protocol. The conversion includes semantic conversion, format encapsulation, and timing alignment. Semantic conversion refers to converting vendor-defined status codes into IEC 61850 standard status descriptions. Format encapsulation refers to encapsulating sampled value messages according to the IEC 61850-9-2 standard, including metadata such as dataset identifier, configuration version number, and sampling counter. Timing alignment refers to obtaining precise timestamps through the PTPv2 protocol and adding timestamps to the converted data to ensure synchronization with the clock of the access terminal. Furthermore, the converted standardized protocol data is transmitted through a dedicated channel of the HarmonyOS distributed soft bus. The channel uses a priority scheduling mechanism to reduce the transmission latency of real-time data. For example, if the original protocol of the power grid equipment to be connected is the Modbus protocol, and the parsed protocol fields are: fault_level:3, temp:45℃, the protocol fields can be converted into the standard format: PTRC.Fault=3, MMXU.Temp=45.

[0033] Next, the operating scenario of the equipment to be connected to the power grid is sensed. If the operating scenario is an edge scenario, the standardized protocol is lightweighted to obtain a lightweight protocol. For example, Figure 5 As shown, the specific process includes the following: Step S231b: Obtain the operating status instructions, network environment data, and operating conditions of the equipment to be connected to the power grid; Step S232b: Based on the operating status instruction, call the power grid service-data mapping strategy library to determine the protocol fields that need to be reconstructed; Step S233b: Based on the network environment data, determine whether the environment in which the power grid device to be connected is located is an edge scenario; Step S234b: If it is determined to be an edge scenario, select the optimal pruning strategy from the predefined lightweight strategy library based on the operating conditions, and prune the protocol fields that need to be reconstructed based on the optimal pruning strategy to prune the standardized protocol into a lightweight protocol.

[0034] Specifically, the system first acquires the operating status instructions (such as fault recovery and power supply priority instructions), network environment data, and operating conditions of the grid equipment to be connected. Then, based on the operating status instructions, it calls the grid business-data mapping strategy library to determine the protocol fields that need to be reconstructed, i.e., the unimportant protocol fields. Next, based on the network environment data and preset scenario conditions, it determines whether the environment of the grid equipment to be connected is an edge scenario (such as bandwidth-limited or latency-sensitive). If it is not an edge scenario, the standardized protocol output is maintained. If it is an edge scenario, the protocol optimization process is triggered. Based on the current operating conditions (such as whether it is in the fault recovery stage, load level, etc.), the optimal trimming strategy is selected from the predefined lightweight strategy library, and the protocol fields that need to be reconstructed are trimmed based on the optimal trimming strategy to trim the standardized protocol into a lightweight protocol. This is transmitted through the low-latency channel of the HarmonyOS soft bus, which significantly reduces the protocol transmission overhead and improves the real-time performance and reliability of edge device access while ensuring the integrity of business semantics. For example, the steady-state lightweight strategy only uploads simple measurement values ​​and removes metadata such as configuration information when the device is running normally; the fault emergency strategy switches to a minimalist mode when the device fails, only uploading key status quantities (such as switch on / off) and fault codes to ensure the real-time nature of critical information.

[0035] For example, in practical applications, if the bandwidth of the power distribution room is detected to be only 700Kbps (<1Mbps, which is an edge scenario), based on the selected strategy, redundant fields (such as equipment production batch number, historical operation log, non-critical telemetry, etc.) are identified and stripped, while core power grid business semantic fields (such as “MMXU1.PhV.phsA.cVal.mag.f” corresponding to the instantaneous value of phase A voltage) are lightly retained. After trimming, the protocol frame size can be reduced by 40%~70%, and it is re-encapsulated into a protocol frame that conforms to the IEC 6185 extended specification, and bound to the soft bus low latency mode (transmission latency ≤40ms).

[0036] It is understandable that power grid equipment commonly employs multiple communication protocols (such as Modbus, DL / T 645, and vendor-specific protocols), lacking a unified protocol conversion mechanism. Existing technologies typically transmit raw data directly without achieving unified conversion to power grid industry standards (such as IEC 61850). Furthermore, they fail to consider the actual operating conditions of limited bandwidth and latency sensitivity at edge nodes, easily leading to link congestion and failing to meet the needs of real-time regulation and coordinated control. This invention constructs a protocol conversion layer within the HDF driver framework, enabling standardized protocol conversion and lightweight reconfiguration. It not only achieves unified conversion from proprietary protocols to the IEC 61850 standard protocol, solving the multi-protocol compatibility problem, but also triggers protocol stream trimming in edge scenarios, generating lightweight protocols. While ensuring the integrity of business semantics, it significantly reduces protocol transmission overhead and improves the real-time performance and reliability of edge device access. Furthermore, conventional protocol pruning methods only consider parameters such as network bandwidth and latency, while this invention can obtain operational status instructions such as fault recovery and power supply priority issued by the power grid dispatching system in real time, using power grid business semantics as decision-making indicators. In addition, conventional pruning methods use static rules or simple threshold judgments, while this invention, by calling the power grid business-data mapping strategy library, dynamically reconstructs fields based on business semantics, and can perform dynamic adaptive lightweight optimization according to the actual operating status of the power grid. While ensuring necessary communication quality, it maximizes the utilization efficiency of edge-side resources. At the same time, conventional pruning methods aim to save bandwidth, while this invention aims to optimize bandwidth while ensuring the integrity of core business semantics. Compared with conventional pruning methods, this invention can significantly reduce protocol transmission overhead and improve the real-time performance and reliability of edge device access while ensuring the integrity of business semantics.

[0037] In addition, such as Figure 6 As shown, it also includes the following: Step S235b: Perform syntax verification, semantic verification, interactive verification, and twin pre-verification on the lightweight protocol.

[0038] The process includes: syntax verification (checking if the protocol conforms to the frame structure specifications of power grid industry standard protocols (such as IEC 61850) and determining if the syntax error rate exceeds a preset error rate threshold); semantic verification (comparing the semantics of protocol fields before and after conversion); interaction verification (simulating the access terminal sending standardized control commands and checking if the response of the device to be accessed conforms to the protocol specifications); and digital twin pre-verification (calling the digital twin of the power grid device to be accessed, simulating the execution of the standardized control commands to be issued in the digital twin, analyzing the state of the digital twin after the execution of the standardized control commands, obtaining simulation results, and determining whether the simulation results violate preset power grid safety operation rules. If a violation occurs, a termination command for the device to be substituted is issued or the device is forced to access in "read-only" mode, and risk alarms and correction strategy suggestions are generated. It can be understood that this invention ensures the accuracy, reliability, and security of the lightweight protocol through multiple verifications.

[0039] In addition, the process of using the security enhancement layer to perform security standardization processing on power grid equipment includes the following: Obtain the device certificate stored in the hardware security module built into the device to be connected to the power grid. Perform hierarchical verification between the device certificate and the system root certificate of the access terminal. After the verification is successful, extract the public key of the device to be connected to the power grid and then randomly generate a challenge code. After the device to be connected to the power grid signs the challenge code with its private key, verify the validity of the signature with the public key of the device to be connected to the power grid. If the verification is successful, the security standardization is completed and the power grid device is allowed to access the grid.

[0040] Specifically, the system first reads the device certificate stored in the hardware security module built into the device to be connected to the power grid. This device certificate, issued by the device manufacturer's secondary certification authority, includes the device's unique identifier, manufacturer information, device public key, and certificate validity period. Then, the device certificate is compared with the system root certificate of the access terminal at a hierarchical level. This includes: decrypting the device certificate's signature value using the device manufacturer's secondary certification authority's public key and comparing it with the hash value of the device certificate's plaintext; if they match, it confirms that the device certificate has not been tampered with and was indeed issued by the device manufacturer's secondary certification authority; retrieving the pre-stored industry root certificate, decrypting the secondary certification authority's certificate's signature value using the industry root certificate's public key, and comparing it with the hash value of the secondary certification authority's certificate's plaintext; if they match, it confirms the legitimacy of the secondary certification authority's certificate; and checking whether the industry root certificate is in the security enhancement layer's preset trust list and whether it has expired. After the hierarchical verification is successful, a challenge code is randomly generated. After the device to be connected to the power grid signs the challenge code using its private key, the security enhancement layer verifies the signature's validity using the device's public key. If the verification passes, security standardization is completed, and the power grid device is allowed to access the network.

[0041] It is understandable that the lack of a unified security authentication mechanism during the grid equipment access process leads to significant security risks such as device identity forgery and certificate tampering. Existing solutions often rely on simple passwords or single certificate verification, which is insufficient to meet the high security requirements of power systems for device access and poses risks of malicious access and data tampering. Therefore, this invention constructs a security enhancement layer within the HDF driver framework, establishing a multi-level device identity authentication mechanism, including hierarchical verification of device certificates, challenge-response signature verification, and binding of access authorization with security policies. This multi-layered security defense effectively prevents security threats such as device forgery and man-in-the-middle attacks, and can well meet the high security requirements of power systems for device access.

[0042] In addition, in step S3, after the grid equipment to be connected completes interface standardization, protocol standardization, and security standardization, the standardized grid equipment sends a registration request to the access terminal through the HarmonyOS system's soft bus. The access terminal verifies the received registration request, assigns a standardized device identifier to the verified grid equipment, and transmits the device identifier to the grid equipment to complete the registration. The registration request includes a standardized metadata model (including device type, interface characteristics, and protocol conversion identifier), a valid authentication credential issued by the security enhancement layer (including session ID and SM3 signature), and a snapshot of the device's current operating status (such as power supply status and communication link quality). Furthermore, the registration request message is encapsulated in JSON format and transmitted through a secure channel (such as SM4 encryption) to ensure the integrity of the registration information.

[0043] Furthermore, this invention can leverage the distributed capabilities of the HarmonyOS system to achieve batch collaborative access for device groups. When a main grid device is accessed, its associated auxiliary device groups are automatically discovered and accessed in batches. Virtual logical devices are created for the auxiliary device groups within the HDF driver framework, and group keys and collaborative security policies are assigned to these virtual logical devices. Through interaction with the virtual logical devices, unified and standardized access to the group devices is achieved. Specifically, when a main grid device (such as a relay protection device for a distribution line) is successfully accessed at the hardware access layer, its standardized metadata model already contains a list of logically associated device identifiers. For example, the unique identifiers of the power transformers and corresponding circuit breakers protected by the protection device. After the main device is successfully registered, the associated device list in its metadata model will trigger the group access coordinator (this module is located within the access terminal and is implemented based on the HarmonyOS distributed task scheduling framework). The group access coordinator discovers these associated auxiliary devices (i.e., power transformers, circuit breakers, etc.) through the HarmonyOS distributed soft bus by broadcasting them in a targeted manner within the local area network based on the identifiers in the list. The near-field discovery capability of the soft bus can quickly locate these associated auxiliary devices (i.e., power transformers, circuit breakers, etc.). The group access coordinator, controlling the standardized hardware access layer, protocol conversion layer, and security enhancement layer of the architecture, executes standardized access procedures for discovered associated auxiliary devices in parallel or pipelined manner, without the need for upper-layer application intervention. After all associated devices (main protection device and each auxiliary device) have completed individual access, the group access coordinator creates a virtual logical device within the HDF driver framework. This virtual device is not a physical entity but a logical abstraction representing the entire "protection functional unit." The security enhancement layer assigns a group key to the entire virtual logical device. Communication between devices within the group is encrypted using this group key, while communication with devices outside the group uses their respective independent device keys. Therefore, based on HarmonyOS's distributed capabilities, this invention can automatically discover associated auxiliary devices after the main device is connected, and achieve standardized batch access of group devices by creating virtual logical devices.

[0044] In addition, such as Figure 7 As shown, another embodiment of the present invention also provides a power grid equipment access standardization system based on the HarmonyOS system, preferably employing the power grid equipment access standardization method based on the HarmonyOS system as described above, including: A standardized architecture creation module is used to create a standardized architecture based on the HDF driver framework of the HarmonyOS system. The standardized architecture includes a hardware access layer, a protocol conversion layer, and a security enhancement layer. The hardware access layer is used to perform interface standardization processing on the grid devices to be connected, the protocol conversion layer is used to perform protocol standardization processing on the grid devices to be connected, and the security enhancement layer is used to perform security standardization processing on the grid devices to be connected. The equipment standardization processing module is used to acquire the power grid equipment to be connected, and to perform interface standardization processing, protocol standardization processing, and security standardization processing on it using the hardware access layer, protocol conversion layer, and security enhancement layer, respectively. The device registration module is used to register standardized power grid devices in the access terminal, thereby completing the power grid device access.

[0045] It is understood that the standardized power grid equipment access system based on the HarmonyOS system in this embodiment uses the HDF driver framework of HarmonyOS to create a standardized architecture. This standardized architecture includes a hardware access layer, a protocol conversion layer, and a security enhancement layer. After acquiring the power grid equipment to be accessed, the hardware access layer performs interface standardization processing, automatically adapting to different manufacturers and types of power grid equipment without manual intervention in driver development, truly achieving "plug and play" for devices and significantly reducing the time and manpower costs of device access. The protocol conversion layer performs protocol standardization processing, converting proprietary protocols into industry-standard protocols, completely solving the multi-protocol compatibility problem. The security enhancement layer performs security standardization processing, effectively preventing security threats such as device forgery and man-in-the-middle attacks, meeting the high security requirements of power systems for device access. Furthermore, the standardized architecture is built on the HDF driver framework, which adopts a master-slave mode design, enabling batch collaborative access of group devices without manual operation, significantly improving the efficiency of large-scale device access, avoiding resource dispersion, reducing system load, and improving the efficiency and scalability of access management.

[0046] In addition, another embodiment of the present invention provides an electronic device including a processor and a memory, wherein the memory stores a computer program, and the processor executes the steps of the method described above by calling the computer program stored in the memory.

[0047] In addition, another embodiment of the present invention provides a computer-readable storage medium for storing a computer program for standardizing power grid equipment access based on the HarmonyOS system, wherein the computer program executes the steps of the method described above when running on a computer.

[0048] Common computer-readable storage media include: floppy disks, flexible disks, hard disks, magnetic tapes, any other magnetic media, CD-ROMs, any other optical media, punch cards, paper tape, any other physical media with perforated patterns, random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), flash-erasable programmable read-only memory (FLASH-EPROM), any other memory chips or cartridges, or any other media readable by a computer. Instructions may further be transmitted or received by a transmission medium. The term transmission medium can include any tangible or intangible medium used to store, encode, or carry instructions for execution by a machine, and includes digital or analog carrier communication signals or intangible media that facilitate communication of such instructions. Transmission media include coaxial cables, copper wires, and optical fibers, which contain conductors for transmitting a bus of computer data signals.

[0049] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code. The solutions in the embodiments of this application can be implemented in various computer languages, such as the object-oriented programming language Java and the interpreted scripting language JavaScript.

[0050] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0051] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0052] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0053] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0054] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

[0055] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A standardized method for grid equipment access based on the HarmonyOS system, characterized in that, Includes the following: A standardized architecture is created based on the HDF driver framework of the HarmonyOS system. The standardized architecture includes a hardware access layer, a protocol conversion layer, and a security enhancement layer. The hardware access layer is used to standardize the interfaces of the grid devices to be connected. The protocol conversion layer is used to standardize the protocols of the grid devices to be connected. The security enhancement layer is used to standardize the security of the grid devices to be connected. The system acquires the grid equipment to be connected and performs interface standardization, protocol standardization, and security standardization on it using the hardware access layer, protocol conversion layer, and security enhancement layer, respectively. The standardized power grid equipment is registered in the access terminal to complete the power grid equipment access.

2. The standardization method for power grid equipment access based on the HarmonyOS system as described in claim 1, characterized in that, The process of standardizing the interfaces of power grid equipment using the hardware access layer includes the following: Interact with the grid equipment to be connected, collect parameter data of the grid equipment to be connected, and map the parameter data into a standardized metadata model; The standardized metadata model is matched with the meta-model of the driver template in the power grid equipment driver template library to obtain the matched driver template; Based on the matching driver template, the built-in device-private driver functions of the equipment to be connected to the power grid are mapped to the HDF standard interface function set; If no driver template is matched, the parameter data of the device to be connected to the power grid is semantically parsed to obtain the functional semantics corresponding to the parameter data. Multiple rounds of exploratory interaction are conducted with the device to be connected to generate the optimal driver call sequence for the adapted device. The functional semantics and the optimal driver call sequence are encapsulated into temporary matching rules. Based on the temporary matching rules, the device-private driver functions built into the device to be connected to the power grid are mapped to the HDF standard interface function set.

3. The standardization method for power grid equipment access based on the HarmonyOS system as described in claim 2, characterized in that, Also includes the following: When the number of times similar grid devices to be connected is detected to reach a preset threshold, the temporary matching rules are converted into new driver templates and updated synchronously in the grid device driver template library.

4. The standardization method for power grid equipment access based on the HarmonyOS system as described in claim 1, characterized in that, The process of standardizing power grid equipment protocols using a protocol conversion layer includes the following: The original protocol of the equipment to be connected to the power grid is obtained and parsed to get the protocol fields; Construct a semantic standard mapping knowledge graph, match the protocol fields in the mapping knowledge graph, and convert the protocol fields into the power grid industry standard format based on the matching results to obtain a standardized protocol; The system senses the operating scenario of the equipment to be connected to the power grid. If the operating scenario is an edge scenario, the standardized protocol is lightweighted to obtain a lightweight protocol.

5. The standardization method for power grid equipment access based on the HarmonyOS system as described in claim 4, characterized in that, If the operating scenario of the sensing device to be connected to the power grid is an edge scenario, then the standardized protocol is lightweighted to obtain the lightweight protocol. The process includes the following: Obtain the operating status commands, network environment data, and operating conditions of the equipment to be connected to the power grid; Based on the aforementioned operating status instructions, the power grid business-data mapping strategy library is invoked to determine the protocol fields that need to be reconstructed; Based on the network environment data, determine whether the environment in which the power grid device to be connected is an edge scenario; If it is determined to be an edge scenario, the optimal trimming strategy is selected from the predefined lightweight strategy library based on the operating conditions, and the protocol fields that need to be reconstructed are trimmed based on the optimal trimming strategy to trim the standardized protocol into a lightweight protocol.

6. The standardization method for power grid equipment access based on the HarmonyOS system as described in claim 4, characterized in that, Also includes the following: The lightweight protocol undergoes syntax verification, semantic verification, interaction verification, and twin pre-verification. Syntax verification includes checking whether the protocol conforms to the frame structure specifications of the power grid industry standard protocol and determining whether the syntax error rate exceeds a preset error rate threshold. Semantic verification includes comparing whether the semantics of the protocol fields before and after conversion are consistent. Interaction verification includes simulating the access terminal to send standardized control commands and checking whether the response of the device to be accessed conforms to the protocol specifications. Twin pre-verification includes calling the digital twin of the power grid device to be accessed, simulating the execution of the standardized control commands to be issued in the digital twin, analyzing the state of the digital twin after the execution of the standardized control commands, obtaining simulation results, and determining whether the simulation results violate preset power grid safety operation rules.

7. The standardization method for power grid equipment access based on the HarmonyOS system as described in claim 1, characterized in that, The process of applying a security enhancement layer to standardize the safety of power grid equipment includes the following: Obtain the device certificate stored in the hardware security module built into the device to be connected to the power grid. Perform hierarchical verification between the device certificate and the system root certificate of the access terminal. After the verification is successful, extract the public key of the device to be connected to the power grid and then randomly generate a challenge code. After the device to be connected to the power grid signs the challenge code with its private key, verify the validity of the signature with the public key of the device to be connected to the power grid. If the verification is successful, the security standardization is completed and the power grid device is allowed to access the grid.

8. A standardized system for grid equipment access based on the HarmonyOS system, characterized in that, include: A standardized architecture creation module is used to create a standardized architecture based on the HDF driver framework of the HarmonyOS system. The standardized architecture includes a hardware access layer, a protocol conversion layer, and a security enhancement layer. The hardware access layer is used to perform interface standardization processing on the grid devices to be connected, the protocol conversion layer is used to perform protocol standardization processing on the grid devices to be connected, and the security enhancement layer is used to perform security standardization processing on the grid devices to be connected. The equipment standardization processing module is used to acquire the power grid equipment to be connected, and to perform interface standardization processing, protocol standardization processing, and security standardization processing on it using the hardware access layer, protocol conversion layer, and security enhancement layer, respectively. The device registration module is used to register standardized power grid devices in the access terminal, thereby completing the power grid device access.

9. An electronic device, characterized in that, The method includes a processor and a memory, wherein the memory stores a computer program, and the processor executes the steps of the method as described in any one of claims 1 to 7 by calling the computer program stored in the memory.

10. A computer-readable storage medium for storing a computer program for standardizing power grid equipment access based on the HarmonyOS system, characterized in that, The computer program, when run on a computer, performs the steps of the method as described in any one of claims 1 to 7.

Images