A method, device, system and readable storage medium for automatically generating a graphical configuration

Abstract

The application discloses a kind of graphic configuration automatic generation method, device, system and readable storage medium, it is related to graphic configuration technical field, the method includes in response to graphic configuration generation instruction, the operating data of terminal equipment is obtained;The operating data is processed by graphic configuration layout algorithm, and graphic configuration data is obtained;Graphic rendering is carried out based on the graphic configuration data, and terminal equipment graphic configuration interface is generated.The application has the effect of improving graphic configuration generation efficiency, reduces the professional dependency of graphic configuration.

Description

Technical Field

[0001] This application relates to the field of graphic configuration technology, and in particular to a method, apparatus, system and readable storage medium for automatic generation of graphic configurations. Background Technology

[0002] In energy storage EMS (Energy Management System) services, graphical configuration is used to visually display the operating status, equipment parameters, alarm information, etc. of the energy storage system, and is an important part of human-machine interaction. Traditionally, graphical configuration in energy storage EMS systems relies on professional engineers to manually draw and maintain it through drag-and-drop. This method requires engineers to drag icons one by one and adjust connections, consuming a lot of time and effort, resulting in low efficiency. Furthermore, any changes to the energy storage system layout or the need to adjust the graphical style require manual modification, making it highly dependent on professional expertise. Summary of the Invention

[0003] The purpose of this application is to at least solve one of the technical problems existing in the prior art, and to provide a method, apparatus, system and readable storage medium for automatic generation of graphical configurations, aiming to improve the efficiency of graphical configuration generation and reduce the professional dependence of graphical configurations.

[0004] In a first aspect, embodiments of this application provide a method for automatically generating graphical configurations, including: In response to the graphical configuration generation command, the operating data of the terminal device is obtained; The running data is processed by a graphical configuration layout algorithm to obtain graphical configuration data; Based on the graphical configuration data, graphical rendering is performed to generate a graphical configuration interface for the terminal device. The operational data includes the number of terminal devices, the graphical configuration data includes the location of device nodes and the location of device labels used to display the operational information of the terminal devices, and the graphical configuration layout algorithm includes: determining the location of device nodes based on the number of terminal devices and the total width of the container used to render the graphical configuration, and determining the location of device labels associated with the device nodes based on the location of the device nodes.

[0005] The technical solution according to the embodiments of this application has at least the following beneficial effects: According to some embodiments of this application, the positioning position of the device node includes a horizontal positioning position and a vertical positioning position, and the positioning position of the device tag includes a horizontal positioning position and a vertical positioning position. The step of determining the positioning position of the device node based on the number of terminal devices and the total width of the container used for rendering the graphics configuration, and determining the positioning position of the device tag associated with the device node based on the positioning position of the device node, includes: The horizontal spacing between nodes is obtained based on the number of terminal devices and the total width of the container; The horizontal positioning position of the device node is determined based on the horizontal spacing between the nodes and the preset first offset. The horizontal positioning position of the device tag is determined based on the positioning position of each device node and a preset second offset. Based on the device type of the terminal device, determine the vertical positioning position of the device node and the device tag.

[0006] According to some embodiments of this application, the graphical configuration layout algorithm further includes: Based on the device type of the terminal device and the location of the device node, edge data for connecting the device node is obtained, and the graphical configuration data also includes the edge data.

[0007] According to some embodiments of this application, the graphical configuration layout algorithm further includes: Based on the total width of the container, the horizontal position of the centered title is obtained. Combining the horizontal position of the centered title with the preset vertical position of the title, the title data is obtained. The graphic configuration data also includes the title data.

[0008] According to some embodiments of this application, the total width of the container is obtained through the following steps: The first total width is obtained based on the number of terminal devices and the preset minimum horizontal spacing; Obtain the preset width of the container, and take the larger value between the first total width and the preset width as the total width of the container.

[0009] According to some embodiments of this application, after preprocessing and format conversion of the original runtime data to obtain runtime data in a format suitable for graphics rendering, the automatic graphics configuration generation method further includes: A listener is set on the graphical configuration interface of the terminal device and the device node. The listener is used to adjust the scaling ratio of the graphical configuration interface of the terminal device and the device node when the size of the graphical configuration interface of the terminal device or the device node changes.

[0010] According to some embodiments of this application, the step of obtaining the operating data of the terminal device in response to the graphical configuration generation instruction includes: In response to the graphical configuration generation command, the raw operating data of the terminal device is obtained; The original runtime data is preprocessed and converted to obtain runtime data in a format suitable for graphics rendering.

[0011] According to some embodiments of this application, it also includes: The running data is stored in a preset database, which is used to send the running data to a graphics processing engine for graphics rendering in response to a data request command.

[0012] According to some embodiments of this application, the step of performing graphic rendering based on the graphic configuration data to generate a graphical configuration interface for a terminal device includes: Based on the device type of the terminal device, determine the corresponding preset custom node type; Based on the graphical configuration data and the custom node type, graphical rendering is performed to generate a graphical configuration interface for the terminal device.

[0013] According to some embodiments of this application, before processing the running data through a graphical configuration layout algorithm to obtain graphical configuration data, the graphical configuration automatic generation method further includes: If the running data exceeds the corresponding preset threshold, an alarm mechanism is triggered to remind the user that there is an anomaly in the current running data.

[0014] In a second aspect, embodiments of this application provide an operation control device, characterized in that it includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the automatic generation method of graphic configuration described in the first aspect above.

[0015] Thirdly, embodiments of this application provide an energy storage management system, including the operation control device described in the second aspect above.

[0016] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which are used to cause a computer to execute the graphical configuration automatic generation method as described in the first aspect above.

[0017] Other features and advantages of this application will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures particularly pointed out in the description, claims and drawings. Attached Figure Description

[0018] The accompanying drawings are used to provide a further understanding of the technical solutions of this application and constitute a part of the specification. They are used together with the embodiments of this application to explain the technical solutions of this application and do not constitute a limitation on the technical solutions of this application.

[0019] The present application will be further described below with reference to the accompanying drawings and embodiments; Figure 1 This is a flowchart of an embodiment of the graphical configuration automatic generation method provided in this application; Figure 2 This is a flowchart of a graphical configuration layout algorithm provided in one embodiment of this application; Figure 3 This is a flowchart of a graphical configuration layout algorithm provided in another embodiment of this application; Figure 4 This is a flowchart of a graphical configuration layout algorithm provided in another embodiment of this application; Figure 5 This is a flowchart of a graphical configuration layout algorithm provided in another embodiment of this application; Figure 6 This is a flowchart of an automatic graphical configuration generation method provided in another embodiment of this application; Figure 7 This is a first graphical configuration example diagram provided in another embodiment of this application; Figure 8 This is a second graphical configuration example diagram provided in another embodiment of this application; Figure 9 This is a flowchart of an automatic graphical configuration generation method provided in another embodiment of this application; Figure 10 This is a flowchart of an automatic graphical configuration generation method provided in another embodiment of this application; Figure 11 This is a flowchart of an automatic graphical configuration generation method provided in another embodiment of this application; Figure 12 This is a flowchart of an automatic graphical configuration generation method provided in another embodiment of this application; Figure 13 This is a schematic diagram of an operation control device for executing a graphical configuration automatic generation method according to an embodiment of this application. Detailed Implementation

[0020] This section will describe in detail the specific embodiments of this application. Preferred embodiments of this application are shown in the accompanying drawings. The purpose of the drawings is to supplement the textual description with graphics, so that people can intuitively and vividly understand each technical feature and the overall technical solution of this application, but they should not be construed as limiting the scope of protection of this application.

[0021] In the description of this application, it should be understood that the orientation descriptions, such as up, down, front, back, left, right, etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this application.

[0022] In the description of this application, "several" means one or more, "more than" means two or more, "greater than," "less than," and "exceeding" are understood to exclude the stated number, while "above," "below," and "within" are understood to include the stated number. The use of "first" and "second" in the description is merely for distinguishing technical features and should not be construed as indicating or implying relative importance, or implicitly indicating the number of indicated technical features, or implicitly indicating the order of the indicated technical features.

[0023] In the description of this application, unless otherwise expressly defined, terms such as "setup," "installation," and "connection" should be interpreted broadly, and those skilled in the art can reasonably determine the specific meaning of the above terms in this application in conjunction with the specific content of the technical solution.

[0024] The various embodiments of the automatic graphical configuration generation method of this application will be further described below with reference to the accompanying drawings.

[0025] like Figure 1 As shown, Figure 1 This is a flowchart of an embodiment of the automatic generation method of graphical configuration provided in this application. The automatic generation method of graphical configuration may include, but is not limited to, steps S110, S120 and S130.

[0026] Step S110: In response to the graphical configuration generation command, obtain the operating data of the terminal device; Step S120: Process the running data through the graphical configuration layout algorithm to obtain graphical configuration data.

[0027] Step S130: Perform graphical rendering based on the graphical configuration data to generate a graphical configuration interface for the terminal device; wherein, the running data includes the number of terminal devices, and the graphical configuration data includes the location of the device nodes and the location of the device labels used to display the running information of the terminal devices.

[0028] like Figure 2 As shown, Figure 2 This is a flowchart of a graphical configuration layout algorithm provided in one embodiment of this application. The graphical configuration layout algorithm may include, but is not limited to, steps S010 and S020.

[0029] Step S010: Determine the positioning position of the device nodes based on the number of terminal devices and the total width of the container used for rendering the graphics configuration; Step S020: Determine the location of the device tag associated with the device node based on the device node's location.

[0030] Understandably, graphical configuration is necessary in energy storage management systems. Graphical configuration can intuitively display the operating status and key data of the energy storage system, so that staff can quickly understand and make decisions. Through a graphical interface, graphical configuration allows complex energy storage devices, energy flow and battery status to be presented in a concise and clear way. For example, dynamic charts can be used to display the charging and discharging process, battery health or power change trends.

[0031] It is understandable that when an energy storage management system is put into operation, or when the configuration of energy storage devices in the energy storage management system changes, or when the configuration interface needs to be updated, the operation of automatically generating graphical configurations is required. Specifically, when the energy storage system is deployed for the first time, an initial graphical configuration monitoring interface can be built based on the energy storage system architecture and equipment parameters, allowing staff to grasp the system's operating status without having to manually draw each component. During operation, if energy storage devices are added, removed, or replaced, such as adding battery packs, replacing inverters, or adjusting energy dispatch strategies, the configuration interface can be adjusted synchronously by automatically detecting hardware changes and triggering configuration updates, or by manually inputting commands, ensuring that the visual interface is consistent with the actual system. As maintenance needs evolve or user interaction experiences are optimized, the configuration interface may need to be updated periodically or new monitoring indicators may need to be added. In this case, commands can be manually initiated to generate the configuration, or the configuration can be automatically reconfigured based on a preset cycle (such as daily, weekly, or monthly), ensuring that the interface always meets the latest management requirements.

[0032] Understandably, when the graphical configuration generation command is triggered, the current device topology, real-time data source, and user-defined configuration can be scanned first. Through the pre-set template library and layout algorithm, the device nodes can be automatically arranged and the visual presentation optimized. For example, newly added battery clusters will be embedded in the existing interface with standardized icons, and their key data points such as voltage and temperature will be automatically associated with the trend chart. If a device goes offline, the interface will gray out the corresponding node in real time and issue an alarm prompt.

[0033] Understandably, in energy storage management systems, graphical configurations can be automatically generated through a visual configuration and monitoring platform. This platform includes a front-end display layer and a back-end logic processing layer. Within the same operating platform, the front-end operates as an independent process, while the back-end operates as a data processing process. The front-end is used for rendering the graphical interface, responding to user operations, and dynamically displaying real-time data. It can be implemented based on a web technology stack (such as HTML5, Canvas, or SVG) combined with an open-source graphics engine (such as ECharts, AntV X6, or industrial configuration-specific QCAD, Node-RED, etc.). The back-end is used for device data acquisition, graphical rule parsing, automatic generation of logical operations, and storage management. It can be built using languages ​​such as Python and Java, through open-source frameworks (such as Spring Boot, Django, or FastAPI), and associated with databases (such as MySQL, InfluxDB) and real-time communication middleware (such as MQTT, WebSocket).

[0034] In one embodiment, the visualization configuration and monitoring platform can automatically generate basic monitoring screens based on the device list and network topology. For example, devices such as battery arrays, PCS (energy storage converters), and EMS (energy management systems) are presented on the canvas with standardized icons and associated with corresponding operating data. When devices are expanded or replaced, the backend identifies the newly connected hardware by scanning the communication protocol, triggers the graphical configuration generation command, the graphical configuration engine recalculates the layout, and the frontend updates the configuration interface accordingly.

[0035] In one embodiment, the visualization configuration and monitoring platform of the energy storage management system may include a front-end module, a graphics rendering module, a user interaction module, a status management module, and a communication adaptation module. The data request module requests data from the back-end; the graphics rendering module uses a graphics engine to display the data graphically on the user interface; the user interaction module handles drag-and-drop, zoom-and-click operations on the interface, providing real-time feedback of manual adjustments to the graphical layout, and supports custom toolbars, shortcut keys, and gesture control; the status management module maintains the overall operating status of the front-end application, such as the currently active view, selected device node, and user permission level, ensuring data consistency during multi-user collaboration or multi-tab operation; and the communication adaptation module acts as a bridge between the front-end and back-end, receiving real-time data updates via communication protocols such as WebSocket or MQTT, and handling events such as disconnection reconnection, data compression, and message queue optimization. The backend may include an interface service module, a data processing module, a data acquisition module, an access control module, a task scheduling module, and a log auditing module. The data acquisition module collects real-time operational data from energy storage devices. The data processing module cleans, transforms, calculates, and stores the collected data. The interface service module provides RESTful APIs, GraphQL APIs, and other interfaces for frontend data requests. The access control module manages different users' access permissions for configuration generation, device configuration, and data viewing using role-based or attribute-based access control models. The task scheduling module coordinates the execution of automated tasks, ensuring the reliability of critical tasks through priority queues and failover mechanisms. The log auditing module records all system operations, including user-triggered interface modifications, the execution results of automatically generated tasks, and abnormal alarm events. In addition, there can be a middleware layer capability that can enhance collaboration between the front-end and the back-end. For example, the version management module exists on both ends. The front-end provides a graphical version comparison and rollback function, while the back-end implements incremental storage and distributed synchronization. The caching module also exists on both ends. The front-end reduces duplicate requests through local caching, while the back-end uses high-speed caches such as Redis to store hot graph data. Based on this, through a front-end and back-end collaborative processing mechanism, the front-end is responsible for graphics rendering and interaction, while the back-end is responsible for data collection and processing. The front-end and back-end communicate through a standard data format, realizing seamless data flow and efficient processing. Furthermore, the modular design decouples the various functional modules, making it easy to expand and maintain.

[0036] It is understandable that the graphical configuration generation instructions can be front-end generated instructions that can be triggered manually on the front-end interface.

[0037] In this embodiment, the terminal device refers to the energy storage device in the energy storage system. The terminal device may include battery packs, PCS, battery management systems (BMS), etc. In addition, in the energy storage system, the devices used to collect real-time operating data of the energy storage device may include intelligent data acquisition devices, communication gateways, and sensor networks. The intelligent data acquisition device is embedded inside the energy storage device or connected through an external interface. For example, the acquisition module in the battery management system can directly read the voltage, current, and temperature of individual battery cells, while the PCS has built-in power and frequency monitoring functions. The communication gateway, as a data aggregation node, is responsible for uniformly processing and forwarding the information from the distributed acquisition devices to the back-end system. It can be an industrial protocol conversion gateway or an edge computing gateway. The sensor network is used for physical environment monitoring of the energy storage device, including temperature and humidity sensors and smoke detectors installed in the battery compartment, as well as flow meters and pressure sensors connected to the cooling system. These devices can transmit signals to the gateway via wired or wireless means. The acquisition devices used to collect real-time operating data of the energy storage device can communicate directly with the monitoring platform through 4G / 5G networks, and the data is in JSON or Protocol format. After being encapsulated in Buffers format, the data is uploaded via HTTPS / MQTT protocol, or the raw data is uploaded directly and then converted in the format by the backend data processing module. The underlying sensors can be connected to the area gateway via fieldbus. After the gateway performs preliminary filtering and normalization on the data, it is transmitted to the plant-level monitoring server via industrial Ethernet or fiber optic cable. Finally, the server interfaces with the backend via OPC UA or RESTful API.

[0038] In this embodiment, the operating data generated by the energy storage device includes the battery pack's SOC (State of Charge), SOH (State of Health), charging and discharging power, voltage, current, and insulation resistance; the PCS's AC side voltage, frequency, harmonics, DC-AC conversion efficiency, and operating mode; the BMS's individual cell voltage range, temperature range, and equilibrium status; the cooling system's water pump speed, radiator temperature, alarm information, and protection status; and the battery compartment's temperature and humidity distribution, vibration, and noise levels. It is understood that during the automatic generation of the graphical configuration, data used for graphical configuration can be filtered, such as the battery pack's SOC, power, and temperature data, and the BMS's alarm signals.

[0039] Based on this, in response to the graphical configuration generation command, the operating data of the terminal device is acquired. This can be done by obtaining the data from the data storage module or by acquiring the data from the data acquisition device used to collect real-time operating data of the energy storage device through the data processing module. After obtaining the operating data of the terminal device, it can be rendered by the automatic layout algorithm provided by the graphics engine, or the operating data can be processed by the graphical configuration layout algorithm in this embodiment. In this embodiment, the graphics engine can be AntVX6.

[0040] In this embodiment, the graphical configuration layout algorithm is used to determine the position of each device node, improving the rationality and aesthetics of the graphical layout. The graphical configuration layout algorithm includes: determining the positioning position of the device nodes based on the number of terminal devices and the total width of the container used to render the graphical configuration. The container used to render the graphical configuration typically refers to the canvas area in the front-end interface that carries visual elements. This container can be a full-screen webpage view, a window panel embedded in a desktop application, a display area on an industrial HMI (Human Machine Interface) device, etc. It can be understood that this container is essentially an HTML5 Canvas element, SVG vector graphics layer, or WebGL 3D scene operated by the graphics engine. Its size and resolution depend on the final display hardware device. In common energy storage system monitoring scenarios, the machines used to display the graphical configuration interface include industrial control computers or industrial PCs, mobile terminals of maintenance personnel, video walls in large dispatch centers, etc. Therefore, during actual rendering, the graphics engine can dynamically adjust the logical size of the canvas according to the physical size and pixel density of different devices.

[0041] In addition, in the graphical configuration, the nodes used to represent energy storage devices are usually represented by specific icons or symbols. When the graphics engine is actually rendering, it also needs to consider the size of these icons or symbols to balance information density and operability. In some embodiments, the width of the device nodes is between 80 and 150 pixels, and the node spacing can be 30% to 50% of the node width. For example, if 20 device nodes need to be arranged on a canvas that is 1920 pixels wide, if the spacing is equal, the algorithm may first deduct the 20-pixel margins on the left and right, and divide the remaining 1880 pixels by 130 pixels per node to get a maximum of 14 nodes per row. Then it is determined that two rows need to be displayed (14 in the first row and 6 in the second row), and the row spacing is automatically adjusted to center the overall layout.

[0042] In addition, the adaptability of container aspect ratio can be considered in the graphical configuration layout. For example, on a mobile terminal with a vertical display, the battery pack can be arranged vertically and the canvas height can be extended using scroll bars; while in an ultra-wide screen dispatch center, horizontal expansion can be prioritized to keep all key equipment visible in the same viewport. The priority of equipment type can also be considered. For example, high-voltage equipment such as PCS and transformers can have larger node sizes than environmental sensors. Therefore, they can be classified in advance and differentiated placeholder rules can be set.

[0043] Based on this, when multiple conditions are combined, the number of rows and columns, the number of device nodes in each row and column, the arrangement order of each device node, and the spacing width can be determined according to the number of terminal devices and the total width of the container used for rendering graphics configuration. This allows for the determination of the positioning of the device nodes, so that the device nodes are arranged in an orderly and aesthetically pleasing manner.

[0044] In addition, the graphical configuration layout algorithm also includes: determining the location of the device tags associated with the device nodes based on their location. A device tag is a tag used to display the operating information of the terminal device, that is, a tag that displays real-time voltage, current, and other operating data of the energy storage device. A device tag is essentially a data frame; data collected and processed from the energy storage device is displayed on the device tag so that staff can clearly view it. Each device tag is associated with a corresponding device node. One device tag displays multiple operating data points for one device node, or multiple device tags in different locations display multiple operating data points for one device node. Therefore, to ensure that staff can clearly view the data corresponding to each device node, the location of each device tag needs to be determined based on the device node it is associated with. For example, the device tag can be positioned near the device node it is associated with, such as displaying the voltage value 10 to 15 pixels directly above the battery node, and arranging the input and output voltage and power data in a vertical list to the right of the converter node. This completes the determination of the location of the device nodes and the location of the device tags used to display the operating information of the terminal devices.

[0045] In this embodiment, when the data type of the energy storage device in the energy storage system changes, or when the data type of the energy storage device that needs to be displayed in the configuration interface changes, the operation data is processed by the graphical configuration layout algorithm to obtain graphical configuration data. Based on the graphical configuration data, graphical rendering is performed to generate the graphical configuration interface of the terminal device.

[0046] Based on this, graphical rendering is performed using graphical configuration data to generate a graphical configuration interface for the terminal device. It is understood that this application's embodiments employ the open-source graphics editing engine AntV X6, fully leveraging its powerful graphics capabilities, rich interactive functions, and data-driven characteristics to provide a novel method for automatically generating graphical configurations for energy storage management systems. By parsing data from energy storage devices, graphical configurations are automatically generated, eliminating the need for manual dragging and configuration. In one embodiment, this reduces configuration time by over 80%. After data updates, the graphics automatically update, achieving dynamic and intelligent graphical configuration. In one embodiment, maintenance costs are reduced by over 70%. In one embodiment, after generating the graphical configuration interface for terminal devices, users can freely view the status of energy storage devices through panning, zooming, and other operations, enabling deeper exploration and analysis, thus improving user experience and decision-making efficiency. Furthermore, by customizing node styles and layout algorithms, exclusive node styles can be customized based on the characteristics of energy storage devices (e.g., different colors represent different power states). Simultaneously, node positions can be automatically calculated based on the number of devices and canvas size, ensuring a reasonable and aesthetically pleasing graphical layout. This reduces reliance on professional engineers, allowing ordinary users to easily complete graphical configuration and maintenance, thus reducing labor costs.

[0047] In another embodiment of the graphical configuration automatic generation method provided in this application, the positioning position of the device node includes a horizontal positioning position and a vertical positioning position, and the positioning position of the device tag includes a horizontal positioning position and a vertical positioning position. like Figure 3 As shown, Figure 3 This is a flowchart of a graphical configuration layout algorithm provided in another embodiment of this application. The graphical configuration layout algorithm may include, but is not limited to, steps S030, S040, S050 and S060.

[0048] S030. Based on the number of terminal devices and the total width of the container, obtain the horizontal spacing between nodes; S040. Determine the horizontal positioning position of the device node based on the horizontal spacing between nodes and the preset first offset. S050. Determine the horizontal positioning position of the device tag based on the positioning position of each device node and the preset second offset. S060. Determine the vertical positioning position of the device node and the device tag according to the device type of the terminal device.

[0049] In this embodiment, the positioning position of the device node includes a horizontal positioning position and a vertical positioning position, and the positioning position of the device tag includes a horizontal positioning position and a vertical positioning position. Therefore, the positioning positions of the device node and the device tag can be determined by determining the horizontal positioning position and the vertical positioning position of the device node, and the horizontal positioning position and the vertical positioning position of the device tag, respectively.

[0050] In this embodiment, before performing graphical configuration layout, the container's width and height dimensions can be obtained first.

[0051] In this embodiment, the layout of the graphical configuration layout algorithm depends on the attributes of the terminal device's operating data, such as the PCS operating data group, the battery pack operating data group, etc. These data groups have a one-to-one correspondence based on their indexes. The index of the operating data group is a key identifier used to match and associate the device entity with its operating data, so that the operating data can be accurately mapped to the corresponding graphical node. When processing the PCS operating data group or the battery pack operating data group, each device is assigned a unique index code in the database. The index code can include multi-dimensional information such as device type, installation location, and communication address. For example, "PCS-01" represents the No. 1 energy storage converter, and "BAT-03-25" corresponds to the 25th battery module in the No. 3 battery compartment. Therefore, through the index, the collected real-time data streams such as voltage and current can automatically find the corresponding device node in the visualization interface. In addition, in some energy storage systems, PCS may be associated with corresponding battery packs. Therefore, the association between PCS and corresponding battery packs can be represented by indexes. Thus, when automatically generating graphical configurations, PCS with association can be connected to corresponding battery packs by connecting edges to characterize the association between PCS and corresponding battery packs.

[0052] In this embodiment, the graphical configuration layout algorithm can first calculate the horizontal spacing between nodes based on the number of terminal devices and the total width of the container. The horizontal spacing between nodes refers to the specified spacing between each device node in the horizontal direction during graphical configuration layout. Layout based on the horizontal spacing between nodes can ensure the aesthetics and simplicity of the interface. In addition, since the index code can represent the number of multiple energy storage devices, for example, "PCS-01" represents energy storage converter No. 1 and "PCS-02" represents energy storage converter No. 2, the horizontal position of each device node can be determined by the index and the horizontal spacing between nodes. For example, by multiplying the horizontal spacing between nodes by the index code value corresponding to each energy storage device, the reference position of the device node corresponding to each energy storage device in the horizontal position can be obtained. Then, the horizontal positioning position of the device node is determined by subtracting the preset first offset from the reference position of each device node in the horizontal position.

[0053] Understandably, in the graphical configuration layout of an energy storage management system, the preset first offset and the preset second offset are used to ensure that the overall layout is neat and orderly. The offset can be a pixel value preset according to the equipment type, importance level, and interface aesthetic requirements, which may range from a few pixels to tens of pixels. The preset first offset and the preset second offset can create visual hierarchy and operational space in the grid layout, which can avoid the "chessboard effect" caused by mechanical arrangement, allowing the staff's eyes to naturally focus on the equipment nodes. At the same time, the offset also reserves space for auxiliary elements such as lines and labels.

[0054] Therefore, after the horizontal positioning position of the device node is determined, the horizontal positioning position of the device tag associated with the device node can be determined based on the horizontal positioning position of the device node. In this embodiment, the horizontal positioning position of the device tag can be determined by subtracting a preset second offset from the horizontal positioning position of the device node. That is to say, the horizontal positioning position of the device tag is based on the horizontal positioning position of the device node, and the horizontal positioning position of the device tag can only be determined after the horizontal positioning position of the device node is determined.

[0055] In addition, in this embodiment, the vertical positioning of the device node and the device tag is preset according to the device type of the energy storage device. For example, different types of device nodes are placed on preset Y coordinates, where the title y=20, the PCS node y=100, and the battery node y=300. That is to say, the vertical coordinates of the same type of energy storage device in the container can be the same.

[0056] Understandably, in the graphical configuration layout of an energy storage management system, the horizontal position of device nodes uses dynamic width calculation while the vertical position uses a preset fixed value. This is mainly due to the unique visualization requirements and usage habits of industrial monitoring scenarios. The dynamic calculation in the horizontal direction is primarily to adapt to energy storage systems of different sizes. When adding or removing devices, the number of devices displayed in each row can be automatically adjusted according to the container width to maintain reasonable horizontal spacing and ensure the best display effect from small interfaces for home energy storage to ultra-wide topology diagrams for grid-scale energy storage power stations. The preset value for the vertical position is because energy storage devices usually have a clear hierarchical relationship in actual physical space, such as the rack layering of battery compartments and the vertical arrangement of PCS devices. The preset vertical position can intuitively represent the real spatial structure.

[0057] Additionally, after determining the location of the device nodes and device labels, a suitable scaling level can be calculated using a function to adapt the node graphic content into the container while taking into account width and height limitations.

[0058] In another embodiment of the graphical configuration automatic generation method provided in this application, the graphical configuration data further includes edge data, such as... Figure 4 As shown, Figure 4 This is a flowchart of a graphical configuration layout algorithm provided in another embodiment of this application. The graphical configuration layout algorithm may also include, but is not limited to, step S070.

[0059] Step S070: Based on the device type of the terminal device and the location of the device node, obtain the edge data used to connect the device node.

[0060] Understandably, in the graphical configuration of an energy storage management system, edges are graphical elements used to visually represent the energy flow or logical connections between devices, and to dynamically display the internal operating relationships of the energy storage system.

[0061] In one embodiment, in the graphical configuration of the energy storage management system, the vertical coordinates of energy storage devices of the same type within the container can be the same. Two related energy storage devices of different types can have the same horizontal coordinate but different vertical coordinates. Therefore, two related energy storage devices of different types can be connected by vertically connected edges. In one embodiment, the vertically connected edges can be directional arrow lines, whose thickness, color, or animation effects can be changed according to real-time data. For example, when the PCS charges the battery pack, the edge will display a blue gradient animation pointing vertically downwards from the PCS node to the battery node, while during discharge, it will become an upward-flowing red arrow. The line thickness is dynamically adjusted according to the power value. In another embodiment, dashed edges can represent virtual connections indicating communication interruptions, and flashing edges can be used to warn of abnormal current or voltage fluctuations in the link. Therefore, the graphical configuration data also includes edge data.

[0062] In this embodiment, energy storage devices with related relationships can be determined based on the device type of the terminal device. Subsequently, based on the location of these related energy storage devices, edges are established to connect them, resulting in edge data for connecting device nodes. It is important to note that in the automatic placement algorithm, the path planning for these edges needs to be calculated to avoid intersections and overlaps, while maintaining precise alignment with device nodes. Additionally, interactive functions can be added to the edges, such as displaying key indicators like real-time power and cumulative transmitted energy when the mouse hovers over them, and popping up a detailed parameter panel when double-clicked.

[0063] In another embodiment of the graphical configuration automatic generation method provided in this application, the graphical configuration data also includes title data, such as... Figure 5 As shown, Figure 5 This is a flowchart of a graphical configuration layout algorithm provided in another embodiment of this application. The graphical configuration layout algorithm may also include, but is not limited to, step S080.

[0064] Step S080: Based on the total width of the container, obtain the horizontal position of the centered title. Combine the horizontal position of the centered title with the preset vertical position of the title to obtain the title data.

[0065] Understandably, in the graphical configuration interface of an energy storage management system, the title is a text label located at the top of the screen or above a specific functional area, used to summarize the attributes and scope of the currently displayed content. The title typically includes factors such as the system name, location identifier, and view type. For example, "Eastern Energy Storage Power Station Battery Compartment 1 - Real-time Operation Topology Diagram" indicates the specific physical facility location and real-time monitoring status. Therefore, graphical configuration data also includes title data.

[0066] In this embodiment, the title of the graphical configuration interface of the energy storage management system can be placed in the center. Therefore, the horizontal position of the centered title can be determined based on the total width of the container and the width of the title itself. It is understood that the text content of the title can be pre-set, and staff can input a prepared title as the title content data, and the width of the title itself can be determined based on the title content. In addition, in this embodiment, the vertical positioning positions of the device nodes and device tags are preset according to the device type of the energy storage device. Different types of energy storage devices can have the same horizontal coordinate but different vertical coordinates. Therefore, the vertical positioning position of the title can also be preset, and the vertical positioning position of the title is different from the vertical positioning position of the energy storage device. Based on this, by combining the centered horizontal position of the title and the preset vertical position of the title, title data including the horizontal and vertical positioning positions of the title is obtained.

[0067] In one embodiment, the title can use a bold, large font and a dark background, and form a visual partition with the operation buttons and status bar on the interface, ensuring that maintenance personnel can quickly identify which interface they are currently viewing; in addition, the title can also dynamically embed key status information, such as automatically adding the words "alarm status" in red when a system anomaly is detected, or displaying auxiliary prompts such as "night mode" according to the time.

[0068] In another embodiment of the graphical configuration automatic generation method provided in this application, the total width of the container in the above-mentioned graphical configuration layout algorithm can be obtained through the following steps: The first total width is obtained based on the number of terminal devices and the preset minimum horizontal spacing; Get the container's preset width, and take the larger value between the first total width and the preset width as the container's total width.

[0069] Understandably, in the design of the graphical configuration of an energy storage management system, the preset minimum horizontal spacing between device nodes can be obtained through calculation and verification in actual operation and maintenance scenarios. For example, the preset minimum horizontal spacing based on calculation should first consider the physical interaction needs of operators. For instance, in a touchscreen operating environment, according to international human-computer interaction standards, the clickable area of ​​a single operable element is usually no less than 48 pixels, and the center-to-center distance between two adjacent elements is recommended to be more than 96 pixels. This ensures that operators wearing gloves will not accidentally touch adjacent devices. Secondly, to meet the basic requirements of information display, each device node needs to reserve sufficient space to display core parameter labels. For example, battery voltage values ​​typically require a width of 30-40 pixels, plus a safety margin with adjacent labels. In addition, the visual width of the connections between devices can be added. Arrows representing energy flow in the topology diagram typically require an 8-12 pixel outline. To avoid visual confusion caused by the overlap of connections and node icons, an additional buffer space of about 20 pixels can be added. The preset minimum horizontal spacing based on actual operation and maintenance scenarios can be based on configuration layout templates with different spacings. Staff can conduct operation tests in a simulated control room environment, record data such as device recognition speed and error rate, and finally select the critical value that can meet safe operation within a 95% confidence interval.

[0070] Based on this, the first total width can be obtained according to the number of terminal devices and the preset minimum horizontal spacing. The first total width represents the minimum container width required for the current number of terminal devices.

[0071] The preset width of the container is obtained. The preset width of the container refers to the width of the container in the stationary interface. The larger value between the first total width and the preset width is taken as the total width of the container. It can be understood that when the preset width is the larger value, it means that all device nodes can be placed directly in the container without affecting the minimum spacing required between the nodes, and without causing the nodes to exceed the visible area. However, when the first total width exceeds the container width, some nodes will exceed the visible area. In this case, a horizontal scroll bar can be used to ensure that the content that exceeds the visible area of ​​the stationary interface can also be placed in the configuration interface. Because the preset minimum spacing of device nodes is a hard standard calculated by taking into account multiple factors such as touch operation accuracy, connection visibility, and label display space, it can be considered that the preset minimum spacing standard must be followed.

[0072] like Figure 6 As shown, Figure 6 This is a flowchart of a graphical configuration automatic generation method provided in another embodiment of this application. The graphical configuration automatic generation method may also include, but is not limited to, step S140.

[0073] Step S140: Set a listener on the terminal device's graphical configuration interface and device nodes. The listener is used to adjust the scaling ratio of the terminal device's graphical configuration interface and device nodes when the size of the terminal device's graphical configuration interface or device nodes changes.

[0074] Understandably, after rendering the graphical elements such as device nodes, device labels, edges, and titles, the terminal device graphical configuration interface can be obtained. At this point, the terminal device graphical configuration interface can display the device parameters and other information required by the user. In order to further enhance the interactive experience of the terminal graphical configuration interface, interactive functions can be added to the terminal device graphical configuration interface.

[0075] In this embodiment, listeners can be set on the graphical configuration interface of the terminal device and on the device node. The listeners are used to respond to changes in the size of the graphical configuration interface of the terminal device or the device node and trigger a graphic size adjustment function. The graphic size adjustment function can perform operations such as adjusting the canvas, recalculating the optimal scaling ratio and applying the new scaling, and re-centering to ensure that the layout can adapt to the changing container size while maintaining the relative arrangement structure of the elements.

[0076] In one embodiment, when a device node is unloaded, the listener of that device node is removed and the corresponding graph instance is destroyed.

[0077] In one embodiment, taking the AntV X6 graphics engine as an example, the energy storage device includes associated PCS and battery pack, and the graphics configuration layout algorithm may include the following steps: Step 1, Initialization: In response to the graphical configuration generation command, an X6 Graph instance is created and panning and specific mouse wheel zoom functions are configured. Node movement is disabled. Step 2, Dimension Calculation: Get the container dimensions (width, height); Calculate the total width of the container (total width of the container = max(first total width, preset width)); Calculate the horizontal node spacing (horizontal node spacing = total width of container / (number of PCS + 1)); Step 3, Title Placement: Place a dedicated title-node at the top and center it horizontally according to the calculated total width of the container; Step 4: Traverse each associated PCS and battery pack item (based on the index). For each associated PCS and battery pack item, include: Calculate the horizontal positioning position of the PCS nodes (baseX = node horizontal spacing * (index value + 1) - first offset) to evenly distribute these device pairs within the available width; Obtain the fixed Y coordinate level of the PCS node, that is, the vertical positioning position (baseY=100); The corresponding PCS data labels (text-block nodes for name, status, and power values) are located using a second offset relative to the PCS node; The associated battery pack node (using the same index as the associated PCS) is placed at the same baseX position as the associated PCS, but at a lower fixed Y coordinate level, i.e., a vertically positioned position (baseY=300). The corresponding battery pack data tags (text-block nodes for name, SOC, status, and power value) are located using a second offset relative to the battery pack node; Draw a pcs-edge that vertically connects the PCS node to its associated battery node; Step 5, Rendering: Assemble all node and edge data; The calculated node and edge data are passed to the front end to render the graph structure; Step 6: Calculate and apply the initial zoom level, then center the view; Step 7: Add a listener to respond to changes in the size of the container or window. Step 8: After the graphic is displayed, wait for user interaction or resizing events.

[0078] like Figure 7 As shown, Figure 7 This is a first graphical configuration example diagram provided in another embodiment of this application. The diagram includes three energy storage cabinet graphics. The graphical configurations of the energy storage cabinets in the diagram are automatically generated and do not require manual configuration. The energy storage cabinet modules are represented graphically, and various operating parameters of the current energy storage cabinet are displayed below each energy storage cabinet module. Users can quickly understand the status of the entire energy storage through graphical configuration and formulate operating strategies based on the operating status.

[0079] like Figure 8 As shown, Figure 8 This is a second graphical configuration example diagram provided in another embodiment of this application. The diagram includes associated PCS and battery box graphics, as well as edges connecting the PCS and battery box. By automatically generating graphical configurations from real-time data collected from the PCS and battery box, users can monitor the operating status of the entire device and the health status of the battery in real time, and formulate different energy storage operation strategies based on the operating status.

[0080] like Figure 9 As shown, Figure 9 This is a flowchart of an automatic graphical configuration generation method provided in another embodiment of this application; regarding the above step S110, it may include, but is not limited to, steps S210 and S310.

[0081] Step S210: In response to the graphical configuration generation command, obtain the original operating data of the terminal device; Step S310: Preprocess and convert the original running data to obtain running data in a format suitable for graphics rendering.

[0082] Understandably, after responding to the graphical configuration generation command, the front-end data request module can request the terminal device's operating data from the back-end. The operating data collected by the acquisition device is the raw operating data, which is usually unprocessed and may include invalid, erroneous, or other data unsuitable for graphical configuration. Furthermore, the raw operating data is collected from different energy storage devices, and the formats of the raw operating data from different energy storage devices may differ, requiring a unified data format for graphical configuration. Therefore, after responding to the graphical configuration generation command, the front-end data request module requests the terminal device's operating data from the back-end. The back-end data processing module can preprocess and convert the raw operating data to obtain the operating data in a format suitable for graphical rendering. Based on the back-end interface service module, the front-end can request data from the back-end via a RESTful API or GraphQL API. After receiving the data returned by the back-end, the front-end parses it and extracts the data needed for graphical rendering.

[0083] In this embodiment, the data processing module can perform operations such as removing invalid data, processing missing values, and correcting erroneous data on the raw operating data to ensure the accuracy and integrity of the data; it can also perform calculations and analyses on the raw operating data according to business needs, such as calculating the total capacity, total power, and average temperature of the battery pack; and it can also convert the collected raw operating data into JSON format suitable for front-end use.

[0084] like Figure 10 As shown, Figure 10 This is a flowchart of an automatic graphical configuration generation method provided in another embodiment of this application; regarding the above-mentioned automatic graphical configuration generation method, after step S310, it may include, but is not limited to, step S150.

[0085] Step S150: Store the running data in a preset database. The preset database is used to send the running data to the graphics processing engine for graphics rendering in response to the data request command.

[0086] In this embodiment, after the data processing module performs operations such as removing invalid data, processing missing values, correcting erroneous data, and performing calculations and analyses on the original running data, the processed running data can also be stored in a preset database for subsequent querying and analysis.

[0087] In this embodiment, the preset database is used to respond to data request commands and send runtime data to the graphics processing engine for graphics rendering. That is, after the data processing module preprocesses and converts the format of the raw runtime data, it can be made available to the front end for data requests via a RESTful API or GraphQL API through the interface service module, so as to quickly respond to the data requests of the front end data request module. Alternatively, after the data processing module preprocesses and converts the raw runtime data, it can store the obtained runtime data in the preset database. When the front end data request module sends a data request, the corresponding data content can be retrieved from the preset database through the interface service module. Alternatively, after the data processing module preprocesses and converts the raw runtime data, it can copy the obtained runtime data. One copy is made available to the front end for data requests via a RESTful API or GraphQL API through the interface service module, and the other copy is stored in the preset database, so as to meet the need for quick response to the data requests of the front end data request module, while ensuring data security.

[0088] like Figure 11 As shown, Figure 11 This is a flowchart of an automatic graphical configuration generation method provided in another embodiment of this application; regarding the above step S130, it may include, but is not limited to, steps S230 and S330.

[0089] Step S230: Determine the corresponding preset custom node type according to the device type of the terminal device; Step S330: Based on the graphical configuration data and custom node types, perform graphical rendering to generate the graphical configuration interface of the terminal device.

[0090] Understandably, traditional manually configured graphics are usually static, lacking flexibility and interactivity. Users can only passively accept the information and cannot explore or operate it in greater depth, which limits their understanding and control of the system. Therefore, it is possible to add a way to customize node styles, allowing Tonghu to customize exclusive node styles (such as different colors representing different power states) according to the characteristics of energy storage devices, thereby improving the flexibility and interactivity of automatic graphical configuration generation.

[0091] In this embodiment, after obtaining the graphic configuration data, that is, after determining the positions of each device node, device label, edge, and title element, when performing graphic rendering, the preset custom node type or preset fixed node type corresponding to each device node can be determined according to the device type of the terminal device. The preset custom node type refers to the node style type of the corresponding energy storage device set by the user. For example, a custom battery-node node type can be registered to represent the battery module, and different fill colors can be set according to the SOC value of the battery. The preset fixed node type refers to the preset node style type provided by the system.

[0092] After determining the node type corresponding to each device node, the graphical rendering can be performed based on the position of each device node, device label, edge and title element represented by the graphical configuration data, as well as the preset custom node type or preset fixed node type corresponding to each device node, to generate the graphical configuration interface of the terminal device.

[0093] like Figure 12 As shown, Figure 12 This is a flowchart of an automatic graphical configuration generation method provided in another embodiment of this application; regarding the above-mentioned automatic graphical configuration generation method, before step S120, there may be steps including but not limited to step S160.

[0094] Step S160: If the running data exceeds the corresponding preset threshold, trigger the alarm mechanism to remind the user that there is an abnormality in the current running data.

[0095] Understandably, the graphical configuration interface (GUI) of the terminal device is used to display the operating status of the energy storage system, enabling staff to understand the overall system's operational and health status. However, staff need to manually view and assess the system status based on the information displayed on the GUI. In some cases, if alarm information is displayed on the GUI but staff do not check it promptly, it may lead to an inability to handle abnormal situations in the energy storage system in a timely manner. Furthermore, for more urgent abnormal situations in the energy storage system, staff need to be able to respond quickly. If operational data from each terminal device can be collected through acquisition devices, and the backend data processing module can perform operations such as cleaning, transformation, calculation, and storage on the collected data, and the interface service module can provide this data via RESTful API or GraphQL... The API provides data requests to the front end. After the front end performs steps such as automatic layout and rendering of graphical configurations, the alarm information is displayed on the terminal device's graphical configuration interface. This may not meet the timeliness requirements. Therefore, when the backend data processing module performs operations such as cleaning, transformation, calculation, and storage on the collected data, an alarm mechanism can be triggered simultaneously based on preset anomaly thresholds or preset anomaly patterns. This triggers the alarm mechanism when the running data exceeds the corresponding preset threshold, alerting the user to an anomaly in the current running data. Alternatively, an alarm mechanism can be triggered in the backend preset database based on preset anomaly thresholds or preset anomaly patterns, alerting the user to an anomaly in the current running data.

[0096] In one embodiment, the graphical configuration automatic generation method provided in this application is applicable to energy storage EMS systems of various sizes and types, including but not limited to: Containerized energy storage: Used in large-scale industrial and commercial energy storage projects, involving a large number of devices and complex layouts. More intelligent layout algorithms, such as force-guided layout, are required to ensure a reasonable and aesthetically pleasing graphical arrangement. Residential energy storage: Used in home energy storage systems, with fewer devices and a simpler layout. Simpler layout options are available, such as horizontal or vertical arrangement. Grid energy storage: used for grid peak shaving and frequency regulation, involving numerous devices and large amounts of data. More efficient data processing and storage solutions are needed to ensure system real-time performance and stability. Microgrid energy storage: Suitable for microgrid systems, it can be customized according to the microgrid topology and clearly display the microgrid's operating status; In addition, the following customized configurations can be made for different application scenarios: Node type: Different node types can be customized according to the device type, such as nodes representing battery modules, PCS, and BMS; Layout algorithm: Select an appropriate layout algorithm based on the number of devices and layout requirements; Data Display: Based on business needs, different data indicators are displayed, such as battery SOC, SOH, power, voltage, current, etc. Interactive features: Add different interactive features, such as viewing device details, sending control commands, and viewing alarm information.

[0097] Based on the graphical configuration automatic generation method of the above embodiments, the following presents various embodiments of the operation control device, energy storage management system, computer-readable storage medium and computer program product of this application.

[0098] like Figure 13 As shown, Figure 13 This is a schematic diagram of a running control device for executing a graphical configuration automatic generation method according to an embodiment of this application. The running control device 1300 implemented in this application includes: a processor 1320, a memory 1310, and a computer program stored in the memory 1310 and executable on the processor 1320, wherein... Figure 13 The example uses a processor 1320 and a memory 1310.

[0099] Processor 1320 and memory 1310 can be connected via a bus or other means. Figure 13 Taking the example of a connection between China and Israel via a bus.

[0100] Memory 1310, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory 1310 may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory 1310 may optionally include remotely located memories 1310 relative to processor 1320, which can be connected to the operation control device 1300 via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0101] Those skilled in the art will understand that Figure 13 The device structure shown does not constitute a limitation on the operation control device 1300, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0102] exist Figure 13In the operation control device 1300 shown, the processor 1320 can be used to call the control program stored in the memory 1310, thereby realizing the above-described automatic graphic configuration generation method. Specifically, the non-transient software program and instructions required to implement the automatic graphic configuration generation method of the above embodiment are stored in the memory 1310. When executed by the processor 1320, the automatic graphic configuration generation method of the above embodiment is executed.

[0103] It is worth noting that, since the operation control device 1300 of this application embodiment can execute the automatic graphic configuration generation method of any of the above embodiments, the specific implementation method and technical effects of the operation control device 1300 of this application embodiment can refer to the specific implementation method and technical effects of the automatic graphic configuration generation method of any of the above embodiments.

[0104] Furthermore, one embodiment of this application also provides an energy storage management system, which includes the operation control device described in the above embodiment.

[0105] It is worth noting that, since the energy storage management system of this application includes the operation control device of the above embodiments, and the operation control device of the above embodiments can execute the automatic graphical configuration generation method of any of the above embodiments, the specific implementation method and technical effects of the energy storage management system of this application can refer to the specific implementation method and technical effects of the automatic graphical configuration generation method of any of the above embodiments.

[0106] Furthermore, one embodiment of this application provides a computer-readable storage medium storing computer-executable instructions for performing the above-described automatic graphical configuration generation method. Exemplarily, the above-described method is executed... Figures 1 to 6 , Figures 9 to 12 The methods and steps in the text.

[0107] It is worth noting that, since the computer-readable storage medium of this application embodiment can execute the automatic graphic configuration generation method of any of the above embodiments, the specific implementation and technical effects of the computer-readable storage medium of this application embodiment can be referred to the specific implementation and technical effects of the automatic graphic configuration generation method of any of the above embodiments.

[0108] It will be understood by those skilled in the art that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which may include computer storage media or non-transitory media and communication media or transient media. As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc DVD or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0109] In the several embodiments provided in this application, it should be understood that the disclosed systems, instruments, and methods can be implemented in other ways. For example, the instrument embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the shown or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between instruments or units may be electrical, mechanical, or other forms. Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, i.e., they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0110] It should also be understood that the various implementation methods provided in this application can be combined arbitrarily to achieve different technical effects.

[0111] The embodiments of this application have been described in detail above with reference to the accompanying drawings. However, this application is not limited to the above embodiments. Within the scope of knowledge possessed by those skilled in the art, various changes can be made without departing from the spirit of this application.

Claims

1. A method for automatically generating graphical configurations, characterized in that, include: In response to the graphical configuration generation command, the operating data of the terminal device is obtained; The running data is processed by a graphical configuration layout algorithm to obtain graphical configuration data; Based on the graphical configuration data, graphical rendering is performed to generate a graphical configuration interface for the terminal device. The operational data includes the number of terminal devices, the graphical configuration data includes the location of device nodes and the location of device labels used to display the operational information of the terminal devices, and the graphical configuration layout algorithm includes: determining the location of device nodes based on the number of terminal devices and the total width of the container used to render the graphical configuration, and determining the location of device labels associated with the device nodes based on the location of the device nodes.

2. The automatic generation method for graphical configurations according to claim 1, characterized in that, The positioning position of the device node includes a horizontal positioning position and a vertical positioning position, and the positioning position of the device tag includes a horizontal positioning position and a vertical positioning position. The step of determining the positioning position of the device node based on the number of terminal devices and the total width of the container used for rendering the graphics configuration, and determining the positioning position of the device tag associated with the device node based on the positioning position of the device node, includes: The horizontal spacing between nodes is obtained based on the number of terminal devices and the total width of the container; The horizontal positioning position of the device node is determined based on the horizontal spacing between the nodes and the preset first offset. The horizontal positioning position of the device tag is determined based on the positioning position of each device node and a preset second offset. Based on the device type of the terminal device, determine the vertical positioning position of the device node and the device tag.

3. The automatic generation method for graphical configurations according to claim 1, characterized in that, The graphical configuration layout algorithm also includes: Based on the device type of the terminal device and the location of the device node, edge data for connecting the device node is obtained, and the graphical configuration data also includes the edge data.

4. The automatic generation method for graphical configurations according to claim 1, characterized in that, The graphical configuration layout algorithm also includes: Based on the total width of the container, the horizontal position of the centered title is obtained. Combining the horizontal position of the centered title with the preset vertical position of the title, the title data is obtained. The graphic configuration data also includes the title data.

5. The automatic generation method for graphical configurations according to claim 1, characterized in that, The total width of the container is obtained through the following steps: The first total width is obtained based on the number of terminal devices and the preset minimum horizontal spacing; Obtain the preset width of the container, and take the larger value between the first total width and the preset width as the total width of the container.

6. The automatic generation method for graphical configurations according to claim 1, characterized in that, Also includes: A listener is set on the graphical configuration interface of the terminal device and the device node. The listener is used to adjust the scaling ratio of the graphical configuration interface of the terminal device and the device node when the size of the graphical configuration interface of the terminal device or the device node changes.

7. The automatic generation method for graphical configurations according to claim 1, characterized in that, The step of responding to the graphical configuration generation command and acquiring the terminal device's operating data includes: In response to the graphical configuration generation command, the raw operating data of the terminal device is obtained; The original runtime data is preprocessed and converted to obtain runtime data in a format suitable for graphics rendering.

8. The automatic generation method for graphical configurations according to claim 7, characterized in that, After preprocessing and format conversion of the original runtime data to obtain runtime data in a format suitable for graphics rendering, the automatic graphics configuration generation method further includes: The running data is stored in a preset database, which is used to send the running data to a graphics processing engine for graphics rendering in response to a data request command.

9. The automatic generation method for graphical configurations according to claim 1, characterized in that, The step of rendering graphics based on the graphics configuration data to generate a graphical configuration interface for the terminal device includes: Based on the device type of the terminal device, determine the corresponding preset custom node type; Based on the graphical configuration data and the custom node type, graphical rendering is performed to generate a graphical configuration interface for the terminal device.

10. The method for automatically generating graphical configurations according to claim 1, characterized in that, Before processing the runtime data using the graphical configuration layout algorithm to obtain graphical configuration data, the automatic graphical configuration generation method further includes: If the running data exceeds the corresponding preset threshold, an alarm mechanism is triggered to remind the user that there is an anomaly in the current running data.

11. An operation control device, characterized in that, The method includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the automatic generation method of graphical configuration as described in any one of claims 1 to 10.

12. An energy storage management system, characterized in that, Includes the operation control device as described in claim 11.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions for causing a computer to perform the automatic generation method of graphical configuration as described in any one of claims 1 to 10.

Images