A low-code visual optimization method and system for power signal development

Abstract

The application relates to a low-code visual optimization method and system for power signal creation development, which comprises the following steps: S1: acquiring data in a signal creation environment, identifying interface differences and performance bottleneck points among various components through a compatibility test matrix, and establishing a standardized adaptive interface specification; S2: acquiring a standardized business object model based on the standardized adaptive interface specification; defining the attributes, relationships and constraint rules of various business entities based on the business object model, forming a data dictionary and an interface specification special for the power field; S3: constructing a power visual field-specific language DSL based on the data dictionary and the interface specification special for the power field; S4: converting the visual operation into a DSL configuration file by adopting a drag-and-drop interactive design; and S5: automatically converting the DSL configuration into a React or Vue component code by a code generation engine, and performing compatibility optimization on a signal creation browser kernel. The application effectively improves the power signal creation development efficiency.

Description

Technical Field

[0001] This invention relates to the field of information technology innovation development, and in particular to a low-code visualization optimization method and system for power industry information technology innovation development. Background Technology

[0002] In recent years, with the continuous advancement of the national strategy of "Information Technology Application Innovation Industry," the power industry's information systems have gradually shifted from the traditional ecosystem of "imported hardware and software + proprietary protocols" to a foundational platform based on independently controllable domestic operating systems, databases, middleware, and domestic browsers. This transformation has enhanced the security and controllability of information infrastructure, but it has also brought multi-dimensional technical heterogeneity and compatibility challenges, including operating system kernels, database syntax, middleware interfaces, and front-end rendering and driver capabilities.

[0003] Meanwhile, the power industry's business processes are complex, involving multiple systems such as dispatching, monitoring, energy consumption, metering, and operation and maintenance. Business models and data standards are numerous, and data visualization needs are becoming increasingly diverse, requiring adaptation to the real-time, massive, and high-concurrency data access and display from production to management. Traditional development methods suffer from prominent problems such as high technical barriers, long customized development cycles, high adaptation costs, and difficulties in upgrading and maintenance. Especially in the context of information technology innovation, engineering experience and tools accumulated based on foreign technology stacks are difficult to directly transfer, resulting in slow progress in the industry's digital transformation. Summary of the Invention

[0004] To address the aforementioned issues, the present invention aims to provide a low-code, visual optimization method and system for power information technology innovation development. Through component-based and configurable development, it significantly reduces the threshold for building power business systems, decouples business definition from interface generation, and improves development efficiency.

[0005] To achieve the above objectives, the present invention adopts the following technical solution:

[0006] A low-code visual optimization method for power information technology innovation includes the following steps:

[0007] S1: Obtain the operating system version, database type, middleware components, and front-end browser kernel support status in the domestic IT innovation environment. Through the compatibility test matrix, identify the interface differences and performance bottlenecks between components and establish standardized adaptation interface specifications.

[0008] S2: Based on standardized adaptation interface specifications, analyze core business scenarios of power dispatching, equipment monitoring, and energy consumption metering to obtain standardized business object models; and based on the business object models, define the attributes, relationships, and constraint rules of each business entity to form a data dictionary and interface specifications specific to the power field.

[0009] S3: Based on the data dictionary and interface specifications specific to the power industry, construct a domain-specific language (DSL) for power visualization and obtain the DSL specification document;

[0010] S4: The modeling platform is based on the DSL specification document and adopts a drag-and-drop interactive design. It provides a dedicated component library for the power industry. Users can drag and drop components onto the canvas and configure data sources, styles and interactive behaviors through the property panel. These visual operations are converted into DSL configuration files.

[0011] S5: Based on the generated DSL configuration file, the code generator converts it into a front-end application that can run in the domestic IT innovation environment. Through the code generation engine, the DSL configuration is automatically converted into React or Vue component code, and compatibility optimization is performed for domestic IT innovation browser kernels. At the same time, a high-performance rendering engine is built, and virtual DOM technology and incremental update mechanism are adopted to ensure the smoothness of the interface when a large amount of data is updated.

[0012] Furthermore, the system obtains information on the operating system version, database type, middleware components, and front-end browser kernel support in the domestic IT innovation environment. Using a compatibility testing matrix, it identifies interface differences and performance bottlenecks between components and establishes standardized adaptation interface specifications, as detailed below:

[0013] First, information about the basic information technology innovation environment is collected through a combination of automated script detection and manual verification, including the operating system, database, middleware components, and browser kernel.

[0014] After the environmental information is collected, a domestic IT innovation compatibility test matrix is ​​constructed to systematically evaluate the adaptation performance between different components. The matrix takes the four-dimensional combination of operating system, database, middleware, and browser as the core test dimensions, and each combination represents a potential deployment scenario.

[0015] For each combination, functional compatibility testing, performance testing, and stability testing are performed; JMeter or a domestic performance testing platform is used to simulate typical power business scenarios, and performance indicators are monitored throughout the entire process from interface calls to rendering output by combining database stress test scripts and middleware load simulation scripts.

[0016] By comparing the test results of different component combinations, potential interface incompatibilities and performance bottlenecks are identified; the output of the test matrix is ​​presented in the form of a score, with each combination receiving a compatibility and performance index;

[0017] Based on the analysis results of the test matrix, a domestic IT innovation adaptation layer is established at the system architecture level. Cross-component compatibility and performance optimization are achieved through abstract interface design and unified calling specifications.

[0018] Furthermore, cross-component compatibility and performance optimization are achieved through abstract interface design and unified calling specifications, as detailed below:

[0019] The interface specification design defines a standard data access layer interface, uniformly encapsulates different database drivers, and enables upper-layer business to transparently call the underlying database through a unified access protocol; it defines a unified middleware interaction interface, shielding multiple JNDI configuration methods, session management modes, and log output mechanisms; at the same time, it provides a unified cross-browser data communication adaptation layer for the front end, with built-in Polyfill and event proxy mechanisms to balance the execution characteristics of different kernels.

[0020] The encapsulation implementation strategy adopts a modular encapsulation mechanism, with the framework built using the adapter pattern and the factory pattern. It automatically identifies the current component type based on the runtime environment and dynamically loads the corresponding driver module. Asynchronous I / O and thread pool mechanisms are introduced in performance-sensitive parts to offset the bottleneck effect caused by the insufficient performance of some components.

[0021] Establish interface acceptance standards to ensure consistency of business logic and performance stability under different operating system and database combinations. Establish a continuous integration process to automatically trigger compatibility re-checks after each system update or change of domestically developed components.

[0022] Furthermore, based on standardized adaptation interface specifications, core business scenarios such as power dispatching, equipment monitoring, and energy consumption metering are analyzed to obtain standardized business object models, as follows:

[0023] In the field of power dispatching, the focus is on the business processes of power generation, transmission, distribution, and dispatching command execution, clarifying dispatching orders, operation plans, load forecasting data entities, and their dynamic interaction characteristics; in the field of equipment monitoring, with substations as the core, it covers the status data of switches, busbars, circuit breakers, relay protection, and sensor equipment, analyzing the business chain of equipment operation status, parameter monitoring, and alarm reporting; in the field of energy consumption metering, it abstracts the processes of energy collection, statistics, and analysis, identifying metering points, energy consumption data, abnormal record objects, and their relationships.

[0024] Based on object-oriented modeling principles, a unified business object model system is constructed to achieve standardized expression of data structures, interactive behaviors, and business semantics, including substation models, equipment operation models, power metering models, and alarm event models.

[0025] The substation model includes static information entities and dynamic operating entities, along with computational attributes;

[0026] The equipment operation model covers the equipment's basic attributes, operation attributes, and maintenance attributes;

[0027] The electricity metering model focuses on energy consumption and quality measurement, including basic attributes of metering points, data acquisition attributes, and statistical attributes.

[0028] The alarm event model carries the system's operational security logic, defining event level, triggering conditions, alarm objects, processing status, and response duration attributes;

[0029] In addition, each type of object has an extensible field interface, which allows for the configuration of differentiated attributes while maintaining a standard structure. Through a unified identification system, data consistency and reliability of association between different modules are ensured.

[0030] Furthermore, based on the business object model, the attributes, relationships, and constraint rules of each business entity are defined, forming a data dictionary and interface specifications specifically for the power sector. Specifically, after completing the business object model design, a system of inter-object relationships and consistency constraints is constructed. The inter-object relationships are based on UML class diagrams and ER modeling methods, establishing a four-level progressive relationship structure: substation—equipment—measuring point—alarm. Substations are connected to multiple devices through topological relationships, each device has several measuring points attached, and each measuring point is associated with real-time data and alarm events, thus forming a traceable spatiotemporal data link. For interactions between different business domains, cross-level logical relationships are defined. The consistency constraint system includes basic data constraints, business logic constraints, and integrity constraints. Finally, a unified power business data dictionary is compiled, defining the name, type, value range, unit, interpretation, and constraints of each data item at the granularity level. Simultaneously, a power business object interface specification is formed, standardizing the data call format, interface protocol, return value structure, and exception handling mechanism between each object.

[0031] Furthermore, based on the data dictionary and interface specifications specific to the power industry, a domain-specific language (DSL) for power visualization is constructed, resulting in the DSL specification document, as follows:

[0032] Based on the power data dictionary and interface specifications, DSL designs a syntax structure system through a layered modeling approach, including a data layer, a presentation layer, and an interaction layer;

[0033] The data layer defines the data sources, object types, data binding relationships, and refresh strategies used by the visualization page. Each data node references a business object in the power sector using the `source` keyword and configures specific field mappings. The presentation layer describes the page structure and visual presentation, uses declarative syntax to configure components, and defines styles, layouts, and bound data fields through attribute configuration. The interaction layer defines user behavior and component linkage logic. After completing the syntax structure system design, a power visualization DSL language specification document is compiled.

[0034] Furthermore, the DSL language specification document includes syntax definitions, keyword descriptions and semantic descriptions, object mapping rules, component library specifications, and extension and compatibility mechanisms, as detailed below:

[0035] Syntax definition: The syntax rules of the DSL are defined in BNF or EBNF form to ensure semantic uniqueness and parsing consistency;

[0036] Keyword description and semantic description: Define all keywords and reserved words in the DSL, and give their lexical meaning, data type requirements and default value conventions;

[0037] Object mapping rules: Based on the object attributes defined in the power business data dictionary, clarify the mapping relationship between DSL keywords and backend data fields and interface parameters, and standardize field naming standards and referencing methods;

[0038] Component Library Specification: Describes the DSL configuration template, required and optional attributes, cross-browser compatibility strategy, and graphics rendering optimization parameters for each visual component in the domestic IT innovation environment;

[0039] Extension and compatibility mechanism: Reserved extension interfaces to allow for smooth extension of DSL semantics when adding new visualization components, connecting new data sources, or introducing AI analysis modules in the future.

[0040] At the implementation level, the DSL parser module is responsible for compiling the DSL configuration file into an intermediate representation and automatically generating the corresponding front-end component tree based on the low-code engine. The parser calls the standardized back-end API interface through the adaptation layer to achieve seamless connection with the database and middleware in the domestic IT innovation environment.

[0041] Furthermore, the generated DSL configuration file is converted into a front-end application that can run in the domestic IT innovation environment through a code generator. The code generation engine automatically converts the DSL configuration into React or Vue component code and optimizes it for compatibility with domestic IT innovation browser kernels, as follows:

[0042] Parse the structure definitions, binding rules, and event logic in the DSL file to generate an intermediate syntax tree; the syntax tree describes the page hierarchy, data dependencies, and component interaction relationships.

[0043] Based on the syntax tree node type, the built-in template library is automatically matched and the corresponding front-end component code is generated. The template library predefines component templates for two mainstream frameworks, React and Vue. Through the placeholder replacement mechanism, DSL properties are injected into the template structure to achieve accurate translation from semantics to code.

[0044] The build engine incorporates the Webpack bundling system, automatically generates the project structure, and modularizes and encapsulates the generated code into a static front-end project that can be directly run in a domestically developed browser.

[0045] Furthermore, a high-performance rendering engine is built, employing virtual DOM technology and incremental update mechanisms to ensure interface smoothness during large-scale data updates, as detailed below:

[0046] The high-performance rendering engine core uses virtual DOM technology to identify the range of data changes by comparing state nodes. When the collection system pushes new data, it only updates the corresponding sub-component area instead of the entire page, thereby reducing the number of DOM repaints and ensuring that the interface remains smooth even under high-frequency refreshes.

[0047] The high-performance rendering engine is divided into a UI layer, a drawing layer, and a rendering layer. The UI layer is responsible for managing component states and interactive responses. The drawing layer uses Canvas for graphics drawing scheduling. The rendering layer dynamically selects WebGL or Canvas Offscreen mode according to the component type. The rendering layer adopts a multi-threaded Worker mechanism, which allows background drawing to be separated from the main thread.

[0048] For power GIS map optimization, the engine uses spatial indexing and dynamic layer aggregation algorithms to achieve continuous scaling display of equipment points; and combines Tile caching technology to reduce the overhead of repeated drawing; for complex power grid topologies, the engine adopts a force-directed layout algorithm to adaptively adjust the node positions, while caching the calculation results to ensure topology stability; and GPU path rendering is used for the connection between nodes instead of pure CSS drawing.

[0049] A low-code visualization optimization system for power industry information technology innovation includes a processor, a memory, and a computer program stored in the memory. When the processor executes the computer program, it specifically performs the steps in the low-code visualization optimization method for power industry information technology innovation as described above.

[0050] The present invention has the following beneficial effects:

[0051] 1. This invention fully considers the diversity of operating systems, databases, middleware and browsers in the domestic IT innovation environment. Through compatibility testing and standardized interface specifications, it effectively solves the problems of interface differences and performance bottlenecks in the domestic software and hardware ecosystem. The standardized adaptation interface lays a solid and secure technical baseline for subsequent low-code development, enabling the platform to quickly adapt to and migrate to different domestic IT innovation system environments, and significantly improves product delivery efficiency and system stability.

[0052] 2. This invention focuses on core business scenarios such as power dispatching, equipment monitoring, and energy consumption metering. Through standardized business object modeling, it refines attributes, relationships, and constraints to form a unified data dictionary and interface specifications. This achieves complete decoupling between the business model and the basic technical environment. Based on the domain DSL derived from the data dictionary, it further provides a sufficient semantic foundation for visualization development and automation platforms. This enables the unification and reuse of business rules, indicator definitions, and object semantics unique to the power industry, effectively improving the standardization level of subsequent application development and data governance.

[0053] 3. This invention integrates domain DSL, drag-and-drop modeling, and a code generation engine to create a professional low-code development process for power visualization. The platform allows business personnel to complete page design through drag-and-drop and parameter configuration, which is automatically converted into DSL descriptions. Then, the code generator generates React / Vue front-end applications. It also performs compatibility, adaptive rendering, and WebGL / Canvas optimization for domestically developed browsers, integrates virtual DOM and incremental update mechanisms, and provides high-performance enhancements for GIS maps and complex topology rendering, effectively ensuring a smooth visualization experience in high-frequency refresh scenarios with big data. Attached Figure Description

[0054] Figure 1 This is a flowchart of the method of the present invention. Detailed Implementation

[0055] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments:

[0056] refer to Figure 1 In this embodiment, a low-code visualization optimization method for power information technology innovation is provided, including the following steps:

[0057] S1: Obtain the operating system version, database type, middleware components, and front-end browser kernel support status in the domestic IT innovation environment. Through the compatibility test matrix, identify the interface differences and performance bottlenecks between components and establish standardized adaptation interface specifications.

[0058] S2: Based on standardized adaptation interface specifications, analyze core business scenarios of power dispatching, equipment monitoring, and energy consumption metering to obtain standardized business object models, such as substation topology, equipment operating status, power quality indicators, alarm events, etc.; and based on the business object models, define the attributes, relationships, and constraint rules of each business entity to form a data dictionary and interface specifications specifically for the power industry.

[0059] S3: Based on the data dictionary and interface specifications specific to the power industry, construct a domain-specific language (DSL) for power visualization and obtain the DSL specification document;

[0060] S4: The modeling platform is based on the DSL specification document and adopts a drag-and-drop interactive design. It provides a dedicated component library for the power industry, including various instruments, charts, maps, and topology diagrams. Users can drag and drop components onto the canvas and configure data sources, styles, and interactive behaviors through the property panel, converting these visualization operations into DSL configuration files.

[0061] S5: Based on the generated DSL configuration file, the code generator converts it into a front-end application that can run in the domestic IT innovation environment. Through the code generation engine, the DSL configuration is automatically converted into React or Vue component code, and compatibility optimization is performed for domestic IT innovation browser kernels. At the same time, a high-performance rendering engine is built, and virtual DOM technology and incremental update mechanism are adopted to ensure the smoothness of the interface when a large amount of data is updated.

[0062] In this embodiment, the operating system version, database type, middleware components, and front-end browser kernel support status in the domestic IT innovation environment are obtained. A compatibility test matrix is ​​used to identify interface differences and performance bottlenecks among the components, and a standardized adaptation interface specification is established, as follows:

[0063] First, information about the basic information technology innovation environment is collected through a combination of automated script detection and manual verification, including the operating system, database, middleware components, and browser kernel.

[0064] Regarding operating systems: The focus is on identifying currently deployed domestic operating system versions, such as Kylin V10, UnionTech UOSServer, and Desktop series. Obtain their kernel version (e.g., 4.19 or 5.10), package management mechanism (RPM / DEB), system library support (glibc, openssl, etc.), and confirm whether they include government-issued security hardening. Regarding databases: Analyze database types and versions, such as DM8 / DM7, KingbaseES, and HighGo, recording their SQL dialect characteristics, connection driver versions, storage engine differences, and clustering methods. For middleware: We identified application server types, including TongWeb, Kingdee Apusic, and Primeton EOS, and obtained their supported Java EE specification versions, JVM dependencies, thread pool and connection pool implementations, and log management mechanisms. For front-end browser engines: we tested the support of mainstream domestic browsers (such as 360 Domestic, Qi An Xin, and Red Flag) in the domestic IT innovation environment for JavaScript ES6 features, WebGL, WebAssembly, Canvas, WebSocket, etc., and analyzed differences in CSS rendering, DOM manipulation latency, and compatibility differences in event mechanisms. This information was summarized using a unified "Environment Information Collection Report," outputting a quantifiable and traceable data list to provide input for subsequent compatibility testing.

[0065] After the environmental information is collected, a domestic IT innovation compatibility test matrix is ​​constructed to systematically evaluate the adaptation performance between different components. The matrix takes the four-dimensional combination of operating system, database, middleware, and browser as the core test dimensions, and each combination represents a potential deployment scenario.

[0066] For each combination, functional compatibility testing (including database connectivity, transaction consistency, and encoding format support), performance testing (response latency, throughput, CPU and memory utilization), and stability testing (long-term operational stability and resource release) are conducted. JMeter or a domestic performance testing platform is used to simulate typical power business scenarios (such as SCADA real-time data entry, large-scale alarm information writing, and visualization chart rendering). Combined with database stress test scripts and middleware load simulation scripts, performance indicators are monitored throughout the entire process from interface calls to rendering output.

[0067] By comparing the test results of different component combinations, potential interface incompatibility issues (such as database driver exceptions, session sharing failures, and API return format mismatches) and performance bottlenecks (such as Canvas rendering delays in specific browsers, I / O blocking of the Eastcom middleware, and database connection pool exhaustion under high concurrency) are identified. The output results of the test matrix are presented in the form of scores, with each combination receiving a compatibility and performance index.

[0068] Based on the analysis results of the test matrix, a domestic IT innovation adaptation layer is established at the system architecture level. Cross-component compatibility and performance optimization are achieved through abstract interface design and unified calling specifications.

[0069] In this embodiment, cross-component compatibility and performance optimization are achieved through abstract interface design and unified calling specifications, as detailed below:

[0070] The interface specification design defines a standard Data Access Layer (DAO) interface, uniformly encapsulates different database drivers, and enables upper-layer business to transparently call the underlying database through a unified access protocol; it defines a unified middleware interaction interface, shielding multiple JNDI configuration methods, session management modes, and log output mechanisms; at the same time, it provides a unified cross-browser data communication adaptation layer for the front end, with built-in Polyfill and event proxy mechanisms to balance the execution characteristics of different kernels;

[0071] The encapsulation implementation strategy adopts a modular encapsulation mechanism, using the Adapter Pattern and Factory Pattern to build the framework, automatically identifying the current component type based on the runtime environment and dynamically loading the corresponding driver module; asynchronous I / O and thread pool mechanisms are introduced in performance-sensitive parts to offset the bottleneck effect caused by the insufficient performance of some components;

[0072] Establish interface acceptance standards to ensure consistency of business logic and performance stability under different operating system and database combinations. Establish a continuous integration process to automatically trigger compatibility re-checks after each system update or change of domestically developed components.

[0073] In this embodiment, based on standardized adaptation interface specifications, core business scenarios such as power dispatching, equipment monitoring, and energy consumption metering are analyzed to obtain a standardized business object model, as detailed below:

[0074] In the field of power dispatching, the focus is on the business processes of power generation, transmission, distribution, and dispatching command execution, clarifying dispatching orders, operation plans, load forecasting data entities, and their dynamic interaction characteristics; in the field of equipment monitoring, with substations as the core, it covers the status data of switches, busbars, circuit breakers, relay protection, and sensor equipment, analyzing the business chain of equipment operation status, parameter monitoring, and alarm reporting; in the field of energy consumption metering, it abstracts the processes of energy collection, statistics, and analysis, identifying metering points, energy consumption data, abnormal record objects, and their relationships.

[0075] Based on object-oriented modeling principles, a unified business object model system is constructed to achieve standardized expression of data structures, interactive behaviors, and business semantics, including substation models, equipment operation models, power metering models, and alarm event models.

[0076] The substation model includes static information entities (such as substation number, name, geographical location, voltage level, etc.) and dynamic operating entities (real-time voltage, current, power, bus status, switch status, etc.), and also includes calculated attributes (such as load factor, power factor, power supply reliability, etc.).

[0077] The equipment operation model covers basic equipment attributes (model, manufacturer, rated parameters), operating attributes (temperature, current, vibration value, status code), and maintenance attributes (maintenance cycle, health score, fault record).

[0078] The electricity metering model focuses on energy consumption and quality measurement, including basic attributes of metering points (number, level, meter location), data acquisition attributes (sampling period, measurement accuracy), and statistical attributes (total electricity, peak and valley values, loss rate).

[0079] The alarm event model carries the system's operational security logic, defining event level, triggering conditions, alarm objects, processing status, and response duration attributes;

[0080] In addition, each type of object has an extensible field interface, which allows for the configuration of differentiated attributes while maintaining a standard structure. Through a unified identification system (such as device ID, event ID, and measurement point ID), data consistency and reliability of association between different modules are ensured.

[0081] In this embodiment, based on the business object model, the attributes, relationships, and constraint rules of each business entity are defined to form a data dictionary and interface specifications specific to the power industry. Specifically, after completing the business object model design, a system of inter-object relationships and consistency constraints is further constructed. The inter-object relationships are based on UML class diagrams and ER modeling methods, establishing a four-level progressive relationship structure: substation—equipment—measuring point—alarm. The substation is associated with multiple devices through topological relationships, and each device has several measuring points attached. Each measuring point is associated with real-time data and alarm events, thus forming a traceable spatiotemporal data link. For interactions between different business domains, cross-level logical relationships are defined, such as the relationship between dispatch commands and equipment. The system establishes mapping relationships between execution states and statistical correlations between energy consumption metering data and load dispatching data. A consistency constraint system includes basic data constraints (field type, length, required attributes), business logic constraints (operation status and operation linkage rules, alarm triggering conditions, data validity period), and integrity constraints (unique device number, directed acyclic topology, alarm events must be bound to measurement points). Finally, a unified power business data dictionary is compiled, defining the name, type, value range, unit, interpretation, and constraints of each data item. Simultaneously, a power business object interface specification is established, standardizing the data call format, interface protocol, return value structure, and exception handling mechanism between various objects.

[0082] In this embodiment, based on the data dictionary and interface specifications specific to the power industry, a domain-specific language (DSL) for power visualization is constructed, resulting in the DSL specification document, as follows:

[0083] Based on the power data dictionary and interface specifications, DSL designs a syntax structure system through a layered modeling approach, including a data layer, a presentation layer, and an interaction layer;

[0084] The data layer defines the data sources, object types, data binding relationships, and refresh strategies used by the visualization page. Each data node references power industry business objects (such as Substation, Device, and PowerQuality) using the `source` keyword and configures specific field mappings (such as voltage, current, and power). The visualization layer describes the page structure and visual presentation, using declarative syntax to configure components such as charts, tables, maps, and indicators, defining styles, layouts, and binding data fields through attribute configuration. The interaction layer defines user behavior and component linkage logic, such as clicking a device node to trigger drill-down, hovering the mouse to display real-time indicators, and selecting a region to trigger data filtering. After completing the syntax structure design, a power visualization DSL language specification document is compiled.

[0085] In this embodiment, the DSL language specification document includes syntax definitions, keyword descriptions and semantic descriptions, object mapping rules, component library specifications, and extension and compatibility mechanisms, as detailed below:

[0086] Syntax definition: The syntax rules of the DSL are defined in BNF or EBNF form to ensure semantic uniqueness and parsing consistency;

[0087] Keyword description and semantic description: Define all keywords and reserved words (such as data, chart, bind, interaction, layout, etc.) in the DSL, and give their lexical meaning, data type requirements and default value conventions;

[0088] Object mapping rules: Based on the object attributes defined in the power business data dictionary, clarify the mapping relationship between DSL keywords and backend data fields and interface parameters, and standardize field naming standards and referencing methods;

[0089] Component Library Specification: Describes the DSL configuration template, required and optional attributes, cross-browser compatibility strategy, and graphics rendering optimization parameters for each visual component in the domestic IT innovation environment;

[0090] Extension and compatibility mechanism: Reserved extension interfaces to allow for smooth extension of DSL semantics when adding new visualization components, connecting new data sources, or introducing AI analysis modules in the future.

[0091] At the implementation level, the DSL parser module is responsible for compiling the DSL configuration file into an intermediate representation (IR) and automatically generating the corresponding front-end component tree based on the low-code engine. The parser calls the standardized back-end API interface through the adaptation layer to achieve seamless connection with the database and middleware in the domestic IT innovation environment.

[0092] In this embodiment, the generated DSL configuration file is converted into a front-end application that can run in the domestic IT innovation environment through a code generator. The code generation engine automatically converts the DSL configuration into React or Vue component code and optimizes for compatibility with domestic IT innovation browser kernels, as follows:

[0093] Parse the structural definitions, binding rules, and event logic in the DSL file to generate an intermediate syntax tree (AST); the syntax tree describes the page hierarchy, data dependencies, and component interaction relationships.

[0094] Based on the syntax tree node type, the built-in template library is automatically matched and mapped to generate the corresponding front-end component code. The template library predefines component templates for two mainstream frameworks, React and Vue, such as chart components, topology components, alarm pop-ups, and GIS map layers. Through the placeholder replacement mechanism, DSL attributes (such as bind, style, interaction, etc.) are injected into the template structure to achieve accurate translation from semantics to code.

[0095] The build engine incorporates the Webpack bundling system, automatically generating the project structure (including routes, styles, resource configurations, data interface adaptations, etc.), and modularizing and encapsulating the generated code into a static front-end project that can be directly run in a domestically developed browser.

[0096] In this embodiment, a high-performance rendering engine is constructed, employing virtual DOM technology and an incremental update mechanism to ensure the smoothness of the interface when large amounts of data are updated, as detailed below:

[0097] To meet the performance requirements of power system visualization for large data volumes, high-concurrency updates, and real-time rendering, a high-performance rendering engine (Visualization Rendering Engine) is built in this phase and integrated into the generated front-end application to achieve a balance and optimization between graphics display and data refresh.

[0098] The high-performance rendering engine core adopts Virtual DOM technology, which identifies the range of data changes through state node comparison (Diff algorithm); when the acquisition system pushes new data (such as current, voltage, temperature, etc.), only the corresponding sub-component area is updated instead of the entire page, thereby reducing the number of DOM repaints and ensuring that the interface remains smooth under high-frequency refresh.

[0099] The high-performance rendering engine is divided into a UI layer, a drawing layer, and a rendering layer. The UI layer is responsible for managing component states and interactive responses. The drawing layer uses Canvas for graphics drawing scheduling. The rendering layer dynamically selects WebGL or Canvas Offscreen mode based on the component type. The rendering layer adopts a multi-threaded Worker mechanism, which allows background drawing to be separated from the main thread, effectively avoiding interface "lag".

[0100] For power GIS map optimization, the engine uses spatial indexing (R-Tree / QuadTree) and dynamic layer aggregation algorithms to achieve continuous scaling display of equipment points; it also combines Tile caching technology to reduce the overhead of repeated drawing; for complex power grid topologies, the engine adopts a force-directed layout algorithm to adaptively adjust the node positions, while caching the calculation results (Layout Cache) to ensure topology stability; the connection between nodes uses GPU path rendering instead of pure CSS drawing, improving frame rate performance by more than 60%.

[0101] A low-code visualization optimization system for power industry information technology innovation includes a processor, a memory, and a computer program stored in the memory. When the processor executes the computer program, it specifically performs the steps in the low-code visualization optimization method for power industry information technology innovation as described above.

[0102] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied 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.

[0103] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. 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 illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0104] 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.

[0105] 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.

[0106] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention in any other way. Any person skilled in the art may make changes or modifications to the above-disclosed technical content to create equivalent embodiments. However, any simple modifications, equivalent changes, and modifications made to the above embodiments based on the technical essence of the present invention without departing from the scope of the present invention shall still fall within the protection scope of the present invention.

Claims

1. A low-code visual optimization method for power information technology innovation development, characterized in that, Includes the following steps: S1: Obtain the operating system version, database type, middleware components, and front-end browser kernel support status in the domestic IT innovation environment. Through the compatibility test matrix, identify the interface differences and performance bottlenecks between components and establish standardized adaptation interface specifications. S2: Based on standardized adaptation interface specifications, analyze core business scenarios of power dispatching, equipment monitoring, and energy consumption metering to obtain standardized business object models; and based on the business object models, define the attributes, relationships, and constraint rules of each business entity to form a data dictionary and interface specifications specific to the power field. S3: Based on the data dictionary and interface specifications specific to the power industry, construct a domain-specific language (DSL) for power visualization and obtain the DSL specification document; S4: The modeling platform is based on the DSL specification document and adopts a drag-and-drop interactive design. It provides a dedicated component library for the power industry. Users can drag and drop components onto the canvas and configure data sources, styles and interactive behaviors through the property panel, converting these visual operations into DSL configuration files. S5: Based on the generated DSL configuration file, the code generator converts it into a front-end application that can run in the domestic IT innovation environment. Through the code generation engine, the DSL configuration is automatically converted into React or Vue component code, and compatibility optimization is performed for domestic IT innovation browser kernels. At the same time, a high-performance rendering engine is built, and virtual DOM technology and incremental update mechanism are adopted to ensure the smoothness of the interface when a large amount of data is updated. Based on standardized adaptation interface specifications, the core business scenarios of power dispatching, equipment monitoring, and energy consumption metering are analyzed to obtain standardized business object models, as detailed below: In the field of power dispatching, the focus is on the business processes of power generation, transmission, distribution, and dispatching command execution, clarifying dispatching orders, operation plans, load forecasting data entities, and their dynamic interaction characteristics; in the field of equipment monitoring, with substations as the core, it covers the status data of switches, busbars, circuit breakers, relay protection, and sensor equipment, analyzing the business chain of equipment operation status, parameter monitoring, and alarm reporting; in the field of energy consumption metering, it abstracts the processes of energy collection, statistics, and analysis, identifying metering points, energy consumption data, abnormal record objects, and their relationships. Based on object-oriented modeling principles, a unified business object model system is constructed to achieve standardized expression of data structures, interactive behaviors, and business semantics, including substation models, equipment operation models, power metering models, and alarm event models. The substation model includes static information entities and dynamic operating entities, along with computational attributes; The equipment operation model covers the equipment's basic attributes, operation attributes, and maintenance attributes; The electricity metering model focuses on energy consumption and quality measurement, including basic attributes of metering points, data acquisition attributes, and statistical attributes. The alarm event model carries the system's operational security logic, defining event level, triggering conditions, alarm objects, processing status, and response duration attributes; Furthermore, each type of object has an extensible field interface, allowing for the configuration of differentiated attributes while maintaining a standard structure. A unified identification system ensures data consistency and reliable association between different modules. Based on the business object model, the attributes, relationships, and constraint rules of each business entity are defined, forming a data dictionary and interface specifications specific to the power industry. Specifically, after completing the business object model design, a system of relationships and consistency constraints between objects is further constructed. The relationships between objects are based on UML class diagrams and ER modeling methods, establishing a four-level progressive association structure of substation—equipment—measuring point—alarm: substations are associated with multiple devices through topological relationships, equipment is connected to measuring points, and each measuring point is associated with real-time data and alarm events, thus forming a traceable spatiotemporal data link. For interactions between different business domains, cross-level logical associations are defined. The consistency constraint system includes basic data constraints, business logic constraints, and integrity constraints. Finally, a unified power business data dictionary is compiled, defining the name, type, value range, unit, interpretation, and constraints of data items at the granularity level. Simultaneously, a power business object interface specification is formed, standardizing the data call format, interface protocol, return value structure, and exception handling mechanism between objects.

2. The low-code visualization optimization method for power information technology innovation development according to claim 1, characterized in that, The process involves obtaining the operating system version, database type, middleware components, and front-end browser kernel support in the domestic IT innovation environment. A compatibility test matrix is ​​then used to identify interface differences and performance bottlenecks between components, and standardized adaptation interface specifications are established, as detailed below: First, information about the basic information technology innovation environment is collected through a combination of automated script detection and manual verification, including the operating system, database, middleware components, and browser kernel. After the environmental information is collected, a domestic IT innovation compatibility test matrix is ​​constructed to evaluate the adaptation performance between different components. The matrix takes the four-dimensional combination of operating system, database, middleware, and browser as the core test dimensions, and each combination represents a potential deployment scenario. Perform functional compatibility testing, performance testing, and stability testing on each combination; Using JMeter or a domestic performance testing platform, we simulated typical power business scenarios and combined database stress test scripts and middleware load simulation scripts to monitor performance indicators throughout the entire process from interface calls to rendering output. By comparing the test results of different component combinations, potential interface incompatibilities and performance bottlenecks are identified; the output of the test matrix is ​​presented in the form of a score, with each combination receiving a compatibility and performance index; Based on the analysis results of the test matrix, a domestic IT innovation adaptation layer is established at the system architecture level. Cross-component compatibility and performance optimization are achieved through abstract interface design and unified calling specifications.

3. The low-code visualization optimization method for power information technology innovation development according to claim 2, characterized in that, The method of achieving cross-component compatibility and performance optimization through abstract interface design and unified calling specifications is as follows: The interface specification design defines a standard data access layer interface, uniformly encapsulates different database drivers, and enables upper-layer business to transparently call the underlying database through a unified access protocol; it defines a unified middleware interaction interface, shielding multiple JNDI configuration methods, session management modes, and log output mechanisms; at the same time, it provides a unified cross-browser data communication adaptation layer for the front end, with built-in Polyfill and event proxy mechanisms to balance the execution characteristics of different kernels. The encapsulation implementation strategy adopts a modular encapsulation mechanism, using the adapter pattern and factory pattern to build the framework, automatically identifying the current component type based on the runtime environment and dynamically loading the corresponding driver module; asynchronous I / O and thread pool mechanisms are introduced in performance-sensitive parts. Establish interface acceptance standards to ensure consistency of business logic and performance stability under different operating system and database combinations. Establish a continuous integration process to automatically trigger compatibility re-checks after each system update or change of domestically developed components.

4. The low-code visualization optimization method for power information technology innovation development according to claim 1, characterized in that, Based on the data dictionary and interface specifications specific to the power industry, a domain-specific language (DSL) for power visualization is constructed, resulting in the DSL specification document, as follows: Based on the power data dictionary and interface specifications, DSL designs a syntax structure system through a layered modeling approach, including a data layer, a presentation layer, and an interaction layer; The data layer defines the data sources, object types, data binding relationships, and refresh strategies used by the visualization page. Each data node references a business object in the power sector using the `source` keyword and configures specific field mappings. The presentation layer describes the page structure and visual presentation, uses declarative syntax to configure components, and defines styles, layouts, and bound data fields through attribute configuration. The interaction layer defines user behavior and component linkage logic. After completing the syntax structure system design, a power visualization DSL language specification document is compiled.

5. The low-code visualization optimization method for power information technology innovation development according to claim 4, characterized in that, The DSL language specification document includes syntax definitions, keyword descriptions and semantic descriptions, object mapping rules, component library specifications, and extension and compatibility mechanisms, as detailed below: The syntax rules of the DSL are defined using BNF or EBNF to ensure semantic uniqueness and parsing consistency. Keyword description and semantic description: Define all keywords and reserved words in the DSL, and give their lexical meaning, data type requirements and default value conventions; Object mapping rules: Based on the object attributes defined in the power business data dictionary, clarify the mapping relationship between DSL keywords and backend data fields and interface parameters, and standardize field naming standards and referencing methods; Component Library Specification: Describes the DSL configuration template, required and optional attributes, cross-browser compatibility strategy, and graphics rendering optimization parameters for each visual component in the domestic IT innovation environment; Expansion and compatibility mechanism: Reserved extension interfaces allow for smooth semantic expansion of the DSL when adding new visualization components, connecting new data sources, or introducing AI analysis modules in the future; At the implementation level, the DSL parser module is responsible for compiling the DSL configuration file into an intermediate representation and automatically generating the corresponding front-end component tree based on the low-code engine. The parser calls the standardized back-end API interface through the adaptation layer to achieve seamless connection with the database and middleware in the domestic IT innovation environment.

6. The low-code visual optimization method for power information technology innovation development according to claim 1, characterized in that, The generated DSL configuration file is converted into a front-end application that can run in the domestic IT innovation environment through a code generator. The code generation engine automatically converts the DSL configuration into React or Vue component code and optimizes for compatibility with domestic IT innovation browser kernels, as detailed below: Parse the structure definitions, binding rules, and event logic in the DSL file to generate an intermediate syntax tree; the syntax tree describes the page hierarchy, data dependencies, and component interaction relationships. Based on the syntax tree node type, the built-in template library is automatically matched and the corresponding front-end component code is generated. The template library predefines component templates for two mainstream frameworks, React and Vue. Through the placeholder replacement mechanism, DSL properties are injected into the template structure to achieve accurate translation from semantics to code. The build engine incorporates the Webpack bundling system, automatically generates the project structure, and modularizes and encapsulates the generated code into a static front-end project that can be directly run in a domestically developed browser.

7. The low-code visualization optimization method for power information technology innovation development according to claim 6, characterized in that, The high-performance rendering engine is constructed using virtual DOM technology and an incremental update mechanism to ensure the smoothness of the interface when large amounts of data are updated, as detailed below: The high-performance rendering engine core uses virtual DOM technology, which identifies the range of data changes by comparing state nodes. When the collection system pushes new data, it only updates the corresponding sub-component area instead of the entire page, thereby reducing the number of DOM repaints and ensuring that the interface remains smooth even with high-frequency refreshes. The high-performance rendering engine is divided into a UI layer, a drawing layer, and a rendering layer. The UI layer is responsible for managing component states and interactive responses. The drawing layer uses Canvas for graphics drawing scheduling. The rendering layer dynamically selects WebGL or CanvasOffscreen mode based on the component type. The rendering layer adopts a multi-threaded Worker mechanism, which allows background drawing to be separated from the main thread. For power GIS map optimization, the engine uses spatial indexing and dynamic layer aggregation algorithms to achieve continuous scaling display of equipment points; and combines Tile caching technology to reduce the overhead of repeated drawing; for complex power grid topologies, the engine adopts a force-directed layout algorithm to adaptively adjust the node positions, while caching the calculation results to ensure topology stability. The connections between nodes use GPU path rendering instead of pure CSS drawing.

8. A low-code visual optimization system for power industry information technology innovation, characterized in that, It includes a processor, a memory, and a computer program stored in the memory. When the processor executes the computer program, it specifically performs the steps in the low-code visualization optimization method for power information technology innovation as described in any one of claims 1-7.

Images