AVALONIA-based cross-platform environment monitoring system

Abstract

The invention relates to the technical field of environment monitoring, in particular to an AVALONIA-based cross-platform environment monitoring system, a front-end and rear-end separation framework is adopted, a front end uses an Avalia framework to realize a cross-platform UI, a rear end uses a. NET framework to construct core service logic, the system realizes dynamic loading of an equipment protocol and a transmission protocol through plug-in design, and the real-time performance of the system is improved. The access of various environment monitoring devices is supported, front and back end communication is carried out by adopting gRPC, multi-database support is realized by adopting a FreeSql ORM framework, system logs are recorded by Log4Net, real-time data are cached by Memory Cache, the functions of real-time acquisition, processing, storage, analysis and reporting of environment monitoring data are realized, various service requirements of automatic environment monitoring are met, and the environment monitoring efficiency is improved. The system has the advantages of high stability, high expansibility and good cross-platform compatibility, guarantees the continuous and stable operation of the system for 7 * 24 hours, and is suitable for an unattended environmental protection monitoring station.

Description

Technical Field

[0001] This invention relates to the field of environmental monitoring technology, and specifically to an AVALONIA-based cross-platform environmental monitoring system. Background Technology

[0002] With the rapid development of my country's economy and urbanization, environmental protection plays an increasingly crucial role in urban construction. For a long time, excessive emissions and illegal discharges have occurred frequently, resulting in heavy tasks, great difficulties, and great pressure for environmental monitoring. In order to supervise and manage industrial pollution sources and enforce the law effectively, environmental monitoring systems are used to monitor the status of various environmental elements in real time, accurately, and comprehensively, providing scientific data support for environmental management, pollution prevention and control, and decision-making.

[0003] Current environmental monitoring systems suffer from the following technical problems: poor system platform compatibility, typically only supporting Windows systems and struggling to adapt to diverse deployment environments; insufficient device access scalability, requiring modifications to the core system code to add new device types; difficulty in guaranteeing real-time data acquisition, failing to meet the stringent requirements of environmental monitoring; insufficient system stability, making it difficult to achieve 24 / 7 uninterrupted operation; complex user interface operation, resulting in low efficiency in data querying and analysis; and existing environmental monitoring systems typically employ a single-platform architecture, with device protocols integrated into the system core, leading to difficulties in system upgrades and maintenance, and hindering adaptation to rapidly changing environmental monitoring needs. Therefore, this paper proposes a cross-platform environmental monitoring system based on AVALONIA. Summary of the Invention

[0004] To address the technical problems existing in the prior art, the present invention provides a cross-platform environmental monitoring system based on AVALONIA.

[0005] To solve the above technical problems, the present invention provides the following technical solution: a cross-platform environment monitoring system based on AVALONIA, comprising a front-end module, a back-end module, a front-end and back-end communication module, a device access module, a data storage module, a log recording module, a data caching module, a data visualization module, and a remote monitoring module. The front-end module is used to provide a unified user interface, the back-end module is used to implement the core business logic of the system, and the front-end module and the back-end module achieve bidirectional data communication through the front-end and back-end communication module.

[0006] The device access module is used to enable rapid access and adaptation of different monitoring devices. The data storage module supports the configuration and switching of multiple data. The log recording module is used to capture, store, and manage various event information during system operation. The data caching module is used to temporarily store data that is frequently accessed, computationally expensive, or time-consuming to obtain. The data visualization module is used to display environmental monitoring data. The remote monitoring module is used to support remote monitoring and management by operation and maintenance personnel.

[0007] Preferably, the front-end module is built using the Avalonia cross-platform UI framework, which is compatible with multiple operating system platforms and supports running on Windows, Linux, macOS, and domestic operating systems, achieving a consistent UI experience across platforms.

[0008] Preferably, the backend module is developed based on the .NET framework. Through the .NET framework's built-in Task-based asynchronous programming model and I / O Completion Ports mechanism, it realizes high-concurrency, low-resource-consumption data acquisition services. Its core business logic includes device management, data acquisition, data processing, data storage, data analysis, and data reporting.

[0009] Preferably, the front-end and back-end communication modules are constructed using the gRPC communication framework.

[0010] Preferably, the device access module adopts a plug-in structure design. By defining a unified device plug-in interface, it supports loading different device protocol parsers and communication drivers in the form of dynamic libraries or modules, so as to realize the rapid access and adaptation of new types of monitoring devices.

[0011] Preferably, the data storage module supports flexible configuration and switching of Microsoft SQL Server, MySQL, PostgreSQL, SQLite and domestic databases through the FreeSql ORM framework, ensuring the diversity and portability of data storage.

[0012] Preferably, the logging module adopts the Log4Net logging framework to uniformly record and manage system operation logs, operation logs, and exception logs.

[0013] Preferably, the data caching module uses the MemoryCache component to cache the real-time collected environmental monitoring data.

[0014] Preferably, the data visualization module is based on Avalonia's cross-platform 2D rendering engine and integrates the LiveCharts.Avalonia open-source charting library.

[0015] The collected environmental monitoring data is generated into charts in real time, and historical trend analysis is performed. The data is dynamically updated and provided with real-time charts, historical trends, alarm prompts and statistical reports.

[0016] Preferably, the remote monitoring module is implemented through bidirectional gRPC streaming communication between the front-end and back-end. When maintenance personnel operate on the front-end interface, the front-end calls the gRPC client to send control command messages to the back-end. The device management service in the back-end business layer receives the commands, converts them into native device commands through the corresponding protocol plugin of the device access module, and sends them to the target device. The device response status is transmitted back to the front-end in real time through the same gRPC stream, updating the UI status, and supporting maintenance personnel to remotely manage device status, view real-time data, and adjust system parameters through the front-end interface.

[0017] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0018] 1. This invention utilizes a combination of technologies including Avalonia's native cross-platform UI, efficient gRPC communication, pluggable device access, real-time caching via MemoryCache, and support for multiple databases via FreeSql. It does not rely on a browser engine and supports bidirectional streaming communication, strong type contracts, efficient serialization, and edge-center collaborative deployment. It is specifically designed for high-real-time, high-reliability, and high-scalability automatic environmental monitoring scenarios. By dynamically loading a protocol parser through a unified interface, it addresses the shortcomings of existing systems in terms of industrial-grade data acquisition performance, device compatibility flexibility, and edge deployment adaptability.

[0019] 2. Strong cross-platform compatibility, flexible device access, and convenient expansion: The front end is based on the Avalonia framework, providing higher performance graphics rendering and lower system resource consumption, and supports mainstream and domestic operating systems. The back end is based on .NET and can be deployed and run on multiple platforms, adapting to the IT environments of different users and regulatory agencies. Through the plug-in architecture, it supports dynamic loading of device protocols and transmission drivers, and new devices can be connected without modifying the main program, which greatly reduces the system maintenance and upgrade costs and improves scalability.

[0020] 3. High real-time performance of data acquisition and processing, and stable and reliable system: The system adopts efficient communication, caching and asynchronous processing mechanisms to ensure low latency in the entire process of environmental monitoring data collection and reporting, meeting the real-time requirements of environmental monitoring. At the same time, through log recording, anomaly management, cache optimization and high availability design, the system ensures continuous and stable operation 24 / 7, making it suitable for unattended environmental monitoring stations. It optimizes communication for industrial-grade real-time monitoring scenarios and ensures second-level response capability for key environmental parameters.

[0021] 4. User-friendly operation and efficient operation and maintenance: It provides an intuitive cross-platform user interface and remote management functions, supports real-time monitoring, parameter adjustment and data display, significantly reduces front-end and back-end communication overhead, improves the efficiency of high-frequency monitoring data push, and enhances the efficiency and scientific nature of environmental supervision. It is suitable for online automatic monitoring scenarios of pollution sources, such as CEMS system, VOC system and air station system monitoring needs. Attached Figure Description

[0022] Figure 1 This is a schematic diagram of the application architecture of the environmental monitoring system of the present invention;

[0023] Figure 2 This is a schematic diagram of the technical architecture of the environmental monitoring system of the present invention. Detailed Implementation

[0024] The present invention will be further described below with reference to the accompanying drawings and embodiments, which illustrate the above and other technical features and advantages of the present invention. However, the following embodiments are merely preferred embodiments of the present invention and are not exhaustive.

[0025] Example 1:

[0026] like Figure 1-2 As shown, the present invention provides an AVALONIA-based cross-platform environmental monitoring system, including a front-end module, a back-end module, a front-end and back-end communication module, a device access module, a data storage module, a log recording module, a data caching module, and a data visualization module. The front-end module is used to provide a unified user interface, the back-end module is used to implement the core business logic of the system, and the front-end module and the back-end module communicate bidirectionally through the front-end and back-end communication module.

[0027] The device access module is used to enable the rapid access and adaptation of different monitoring devices; the data storage module supports the configuration and switching of multiple data; the log recording module is used to capture, store, and manage various event information during system operation; the data caching module is used to temporarily store data that is frequently accessed, computationally expensive, or time-consuming to obtain; and the data visualization module is used to display environmental monitoring data.

[0028] The system supports dynamic adjustment of data acquisition frequency, caching strategy, log level and communication parameters through configuration files or management interface to adapt to different field operating environments and business needs.

[0029] In this embodiment, the front-end module is built using the Avalonia cross-platform UI framework to provide a unified user interface that is compatible with multiple operating system platforms and supports running on Windows, Linux, macOS, and domestic operating systems, achieving a consistent UI experience across platforms.

[0030] In this embodiment, the backend module is developed based on the .NET framework and utilizes its built-in Task-based asynchronous programming model (TAP) and I / O Completion Ports (IOCP) mechanism to achieve high-concurrency, low-resource-consumption data acquisition services.

[0031] In practice, the data acquisition service establishes a device connection via System.IO.Ports (serial port) or System.Net.Sockets (TCP / UDP), and asynchronously reads the raw data stream using an async / await mode; the protocol parser (loaded via a plugin) parses and verifies the data packets in an independent thread pool; the processed structured data is then transmitted through a Channel. <t>The (producer-consumer channel) transmits data to the data storage service and caching service, realizing parallel processing of the pipeline for collection, processing and storage, avoiding blocking. The asynchronous programming model is implemented using the .NET platform standard asynchronous I / O. The core business logic implemented includes device management, data collection, data processing, data storage, data analysis and data reporting.

[0032] In this embodiment, the front-end and back-end communication module is built using the gRPC communication framework. It uses gRPC Core + Protocol Buffers to define service contracts and implements real-time data push and remote control through bidirectional streams. This enables high-performance, low-latency bidirectional data communication between the front-end and back-end.

[0033] In this embodiment, the device access module is designed with a plug-in structure. By defining a unified device plug-in interface, it supports loading different device protocol parsers and communication drivers in the form of dynamic libraries or modules, so as to achieve rapid access and adaptation to new types of monitoring devices.

[0034] It enables "zero-code" support for new devices, requiring only the deployment of a plugin DLL by maintenance personnel, significantly reducing the complexity of system upgrades and downtime, and adapting to monitoring scenarios involving rapid iteration of devices from multiple vendors.

[0035] In this embodiment, the data storage module supports flexible configuration and switching of Microsoft SQL Server, MySQL, PostgreSQL, SQLite and domestic databases through the FreeSql ORM framework, ensuring the diversity and portability of data storage.

[0036] In this embodiment, the logging module adopts the Log4Net logging framework to uniformly record and manage system operation logs, operation logs, and exception logs, providing strong support for system operation and maintenance and fault diagnosis, and enhancing system stability and traceability.

[0037] In this embodiment, the data caching module uses the MemoryCache component to cache the real-time collected environmental monitoring data, which shortens the data access time, reduces the pressure on the backend data source, improves the overall system response speed and throughput, effectively improves data access efficiency and system response speed, and optimizes real-time data processing performance.

[0038] The data caching module (using Microsoft.Extensions.Caching.Memory.MemoryCache) and the data storage module (based on FreeSql) work together. Data processing adopts a "Write-Through + Time-BasedEviction" strategy: When writing, valid monitoring data parsed by the business layer is written to both the data caching module and the database simultaneously (Write-Through) to ensure data consistency; when reading, the front-end requests real-time data and first reads from the data caching module. If the data caching module does not hit (e.g., after a system restart), it is loaded from the database and the data caching module is populated.

[0039] Caching strategy: Set a sliding expiration time (e.g., 5 minutes) for cached items to ensure that data that has not been accessed for a long time is automatically released;

[0040] Error handling: If the database write fails, the system records the error log and retains the cached data. After the network / database is restored, the data is retransmitted through a Hangfire scheduled task (see Example 2) to ensure data integrity, avoid high-frequency database write pressure, ensure second-level refresh of the front end, and still provide the latest cached data when the network is disconnected, thus improving system robustness.

[0041] In this embodiment, the data visualization module is based on Avalonia's cross-platform 2D rendering engine and integrates the LiveCharts.Avalonia open-source chart library.

[0042] By binding with the front-end ViewModel using the MVVM pattern, it receives the latest data points pushed by gRPC in real time and dynamically updates line charts (such as PM2.5 trends) and dashboards (such as current data). Data includes concentration, bar charts (such as daily average comparisons), alarm information is presented through highlighting or pop-up notifications; report generation uses the FastReport.NET library to export historical data to PDF / Excel format, and generates real-time charts from collected environmental monitoring data, performs historical trend analysis, dynamically updates and provides generated real-time charts, historical trends, alarm notifications and statistical reports to help users intuitively understand the environmental quality and equipment operating status.

[0043] In this embodiment, the remote monitoring module is implemented through bidirectional gRPC streaming communication between the front-end and back-end. When maintenance personnel operate on the front-end interface (such as "restarting the device" or "modifying the sampling frequency"), the front-end calls the gRPC client to send control command messages to the back-end. The device management service in the back-end business layer receives the commands and converts them into native device commands (such as Modbus register write and HJ212 setting commands) through the corresponding protocol plugin of the device access module, and sends them to the target device. The device response status is transmitted back to the front-end in real time through the same gRPC stream, updating the UI status (such as "online / offline" or "parameters updated"), ensuring low latency and reliability of remote operation. This allows maintenance personnel to remotely manage device status, view real-time data, and adjust system parameters through the front-end interface, achieving efficient operation and maintenance and system management. It meets the dual needs of local operation and remote central supervision of monitoring stations and is adaptable to a wider range of environmental infrastructure IT environments.

[0044] In this embodiment, the system architecture adopts a four-layer application architecture, which is suitable for enterprise-level business systems with complex functions, requiring long-term stable operation and supporting multi-platform and multi-database deployment. It is especially suitable for environmental automatic monitoring scenarios with high requirements for module decoupling, maintainability, scalability, and localization adaptation. Through layered responsibility isolation, it effectively supports 24 / 7 unattended operation. The four-layer application architecture, from top to bottom, are as follows:

[0045] Presentation layer: Developed using the Avalonia cross-platform UI framework, it follows the MVVM design pattern to build interface logic and supports Windows, Linux, macOS and domestic operating systems;

[0046] The main functional modules include: user management, role and permission management, device management, measurement point management, real-time data display, historical data query, alarm management, data reports, system configuration, log viewing, device control, data import and export, and user operation interface. It provides users with a unified operation entry point and supports functions such as device monitoring, data viewing, parameter configuration, and system management. All operations are implemented by calling the business layer interface.

[0047] Business Layer: As the core logic hub of the system, the core functional modules include: measurement point management, equipment communication management, data acquisition service, data processing service, data storage service, data analysis service, alarm service, reporting service, task scheduling, plug-in management, cache management, and interface services (such as external APIs). It implements the core business logic of the system and is responsible for the entire process of data acquisition, processing, storage, analysis and display, anomaly alarm, and data reporting.

[0048] It interacts with the general service layer to call common services such as permission verification, logging, message queues, and task scheduling.

[0049] General service layer: The main functional modules include: authorization authentication, log service, message notification, caching service, scheduled tasks, file management, configuration management, and message queue. It provides general technical support for the business layer, including user authentication, operation log recording, exception alarm, cache acceleration, and scheduled data collection.

[0050] Data layer: Stores environmental monitoring indicator data (such as...) The system collects PM2.5, VOC, temperature, and humidity data, log data (such as system operation logs, operation records, and device communication logs), and configuration information data (such as device configuration, communication parameters, user permissions, and collection strategies). It supports multiple databases (such as MySQL, SQL Server, PostgreSQL, SQLite, and domestic databases) through the FreeSql ORM framework, enabling efficient storage and flexible configuration of structured and unstructured data.

[0051] The specific operation process is as follows: When the backend service starts, it automatically loads: FreeSql database connection configuration, Log4Net log configuration, MemoryCache caching strategy configuration, gRPC service port configuration, and all device access modules in the device plugin directory. When the device is connected, a plug-in architecture design is adopted. The system automatically scans the plugin directory and dynamically loads compatible device protocol plugins such as HJ212, Modbus, and MQTT. A communication link with the monitoring device is established based on serial port or network communication, so as to realize flexible expansion of device access.

[0052] During data acquisition and processing, raw data from the device is collected via serial port or RJ45 (Ethernet) communication link according to the set acquisition frequency. After protocol parsing, data verification, and format conversion by the business layer, the data is stored in the cache and database. The front end obtains the latest monitoring data in real time through gRPC and displays it visually. When the pollution source detection data or equipment operating status data exceeds the threshold, an alarm is triggered and a log is recorded. The system periodically packages the data and reports it to the upper-level platform in accordance with environmental protection standards. Maintenance personnel can remotely manage the equipment, adjust parameters, and view logs through the management interface.

[0053] Example 2:

[0054] In this embodiment, the module division is the same as in Embodiment 1; the system architecture adopts a five-layer application architecture, which is suitable for medium and large-scale industrial software systems with higher requirements for communication performance, system evolvability, localization adaptation, and engineering standardization. It is especially suitable for scenarios that need to support high real-time bidirectional communication (such as remote control of environmental monitoring), long-term technology evolution (such as future expansion to Web / mobile multi-terminal), deployment in a domestic IT innovation environment (such as Kylin OS + domestic database), and edge-center collaborative deployment. By making the communication mechanism an independent dedicated layer and refining the responsibilities of the system operating environment and basic components, the decoupling, testability, and technology stack flexibility of the system are significantly improved, providing solid architectural support for the stable operation and continuous iteration of complex environmental monitoring systems. The five-layer application architecture from top to bottom is as follows:

[0055] Presentation Layer: The technology chosen is Avalonia UI (MVVM architecture), which supports platforms including Windows, Linux, macOS, and domestic operating systems. It can be expanded to be a web front-end (Blazor or WASM) or a mobile terminal (such as MAUI or Xamarin, which is not deployed in this embodiment but supports future expansion). It provides a user interface to realize functions such as data display, device control, and parameter configuration, and communicates with the backend service through gRPC.

[0056] Communication layer: Adopting the gRPC communication framework, it supports high-performance, low-latency, bidirectional streaming communication between the front-end and back-end, and is used for real-time data interaction and remote control command issuance between the front-end and back-end services.

[0057] Business layer: The core technology adopts the dependency injection (IOC) pattern, which replaces the hard-coded instantiation of dependencies inside the module with external container injection, realizes the weak coupling design between modules based on abstract interfaces, and relies on the replaceable characteristics of abstract dependencies to quickly inject simulation to complete unit tests, effectively improving the testability of system code;

[0058] The Mediator pattern, based on the MediatR or Rebus framework, encapsulates the interaction logic between modules through standardized mediator components, unifies the handling of module communication and message scheduling, and realizes the modularization and event-driven nature of business logic.

[0059] It adopts a modular or plug-in architecture, supporting the dynamic loading of device protocols, data processors, etc. in the form of plug-ins; it uses multi-threading and asynchronous IO technology to improve concurrent acquisition and processing capabilities; it has multi-standard device access compatibility through serial port or network communication, supporting device access methods such as RS232 / RS485 / RS422 serial communication and RJ45 Ethernet;

[0060] It implements core business logic such as device communication, data acquisition, processing, storage, and analysis.

[0061] The foundation layer: The technical components adopt the FreeSql ORM framework. Relying on the multi-database adaptation capabilities and data access layer abstraction design of the FreeSql ORM framework, unified data access control across database types is achieved.

[0062] The MemoryCache component is used to implement in-process caching of real-time data. By keeping frequently accessed real-time data in memory, the data access time is greatly reduced and the overall system access efficiency is improved.

[0063] The Log4Net component is used to complete system logging, supporting multiple levels and multiple output targets;

[0064] The Hangfire framework is used to implement the system's background scheduled tasks, which can support the automated execution of periodic tasks such as data supplementation, scheduled reporting, and log cleaning, ensure the standardization of system operation and maintenance tasks, and achieve unattended operation.

[0065] It provides basic capabilities such as data persistence, caching, logging, and task scheduling for the business layer.

[0066] System layer: It adopts the .NET cross-platform runtime as the runtime environment, supporting deployment and adaptation on Windows, Linux, macOS and the domestic Kylin operating system;

[0067] At the hardware interface level, it supports multiple physical communication interfaces such as RS232, RS485, RS422, and RJ45 for connecting various environmental monitoring devices;

[0068] It uses MySQL database by default, but also supports flexible switching to other relational databases or domestic databases;

[0069] It provides the basic platform and hardware communication capabilities for system operation, ensuring that the system is portable, deployable, and scalable.

[0070] The above are merely preferred embodiments of the present invention and are illustrative in nature, not restrictive. Those skilled in the art will understand that many changes, modifications, and even equivalents can be made within the spirit and scope defined by the claims of the present invention, all of which will fall within the protection scope of the present invention.< / t>

Claims

1. An AVALONIA based cross platform environment monitoring system characterized in that, The system comprises a front-end module, a back-end module, a front-back communication module, a device access module, a data storage module, a log recording module, a data caching module, a data visualization module, and a remote monitoring module. The front-end module is configured to provide a unified user interface. The back-end module is configured to implement the core business logic of the system. The front-end module and the back-end module are connected through the front-back communication module to realize bidirectional data communication. The device access module is configured to realize the quick access and adaptation of different monitoring devices. The data storage module supports the configuration and switching of multiple data. The log recording module is configured to capture, store, and manage various event information during the operation of the system. The data caching module is configured to temporarily store data with high frequency access, high calculation cost, or long acquisition time. The data visualization module is configured to display environmental monitoring data. The remote monitoring module is configured to support remote monitoring and management by operation and maintenance personnel.

2. The AVALONIA based cross-platform environment monitoring system of claim 1, wherein, The front-end module is built by the Avalonia cross-platform UI framework, which is suitable for multiple operating system platforms and supports running on Windows, Linux, macOS, and domestic operating systems to achieve consistent UI experience across platforms.

3. The AVALONIA based cross-platform environment monitoring system of claim 1, wherein, The back-end module is developed based on the.NET framework. Through the built-in Task-based asynchronous programming model and I / OCompletionPorts mechanism of the.NET framework, the data collection service with high concurrency and low resource occupation is realized. The core business logic implemented by the back-end module includes device management, data collection, data processing, data storage, data analysis, and data reporting.

4. The AVALONIA based cross-platform environment monitoring system of claim 1, wherein, The front-back communication module is built by the gRPC communication framework.

5. The AVALONIA based cross-platform environment monitoring system of claim 1, wherein, The device access module is designed in a plug-in structure. By defining a unified device plug-in interface, different device protocol analyzers and communication drivers can be loaded in the form of dynamic libraries or modules to realize the quick access and adaptation of new types of monitoring devices.

6. The AVALONIA based cross-platform environment monitoring system of claim 1, wherein, The data storage module supports the flexible configuration and switching of Microsoft SQL Server, MySQL, PostgreSQL, SQLite, and domestic databases through the FreeSql ORM framework, ensuring the diversity and portability of data storage.

7. The AVALONIA based cross-platform environment monitoring system of claim 1, wherein, The log recording module uses the Log4Net log framework to record and manage system operation logs, operation logs, and exception logs.

8. The AVALONIA based cross-platform environment monitoring system of claim 1, wherein, The data caching module uses the MemoryCache component to cache real-time collected environmental monitoring data.

9. The AVALONIA based cross-platform environment monitoring system of claim 1, wherein, The data visualization module is based on the cross-platform 2D rendering engine of Avalonia and integrates the LiveCharts.Avalonia open-source chart library to realize; The collected environmental monitoring data is real-time charted, and historical trend analysis is performed. The generated real-time charts, historical trends, alarm prompts, and statistical reports are dynamically updated and provided.

10. The AVALONIA based cross-platform environment monitoring system of claim 1, wherein, The remote monitoring module is realized through front-end and back-end gRPC bidirectional streaming communication. When an operation personnel operates on the front-end interface, the front-end calls a gRPC client to send a control instruction message to the back-end. A device management service of a back-end business layer receives the instruction, converts the instruction into a device native instruction through a corresponding protocol plug-in of a device access module, and delivers the instruction to a target device. A device response state is returned to the front-end in real time through the same gRPC stream, the UI state is updated, and the operation personnel can remotely manage the device state, view real-time data, and adjust system parameters through the front-end interface.

Images