A power plant mobile application method and system based on the hon g meng next system

Abstract

This invention provides a method and system for mobile applications in power plants based on the HarmonyOS NEXT system, belonging to the field of power plant mobile application technology. The invention includes an adaptation layer, a front-end service layer, a business application layer, and a back-end service layer. The adaptation layer interacts with the kernel of the HarmonyOS NEXT system to unify and integrate the native capability interfaces of the HarmonyOS NEXT system. The front-end service layer provides functional interfaces based on the unified and integrated native capability interfaces of the HarmonyOS NEXT system. The business application layer contains several business application modules, each implementing corresponding business functions by calling the functional interfaces. The back-end service layer contains several back-end service modules, each interacting with the front-end service layer and the business application layer, and connecting to the power plant's information system. This invention solves the problem of narrow applicability and inability to fully reflect the actual business scenarios and operational needs of power plants.

Description

Technical Field

[0001] This invention belongs to the field of power plant mobile application technology, specifically relating to a power plant mobile application method and system based on the HarmonyOS NEXT system. Background Technology

[0002] With the deep integration of Industry 4.0 and the industrial mobile internet, and the rapid rise of the domestic operating system HarmonyOS ecosystem, power plants, as core energy enterprises, are gradually undergoing mobile transformation in their core business scenarios such as equipment inspection, safety management, material management, and operation. However, the current construction and operation of mobile applications in power plants faces several industry pain points: 1. Distributed application architecture Most existing mobile applications are developed and deployed independently by various business departments, lacking a unified technical architecture and management framework, resulting in a large number of "application silos". Data exchange between different applications is difficult, making it impossible to achieve efficient collaboration across departments and businesses.

[0003] 2. Poor system compatibility Existing mobile platforms are mostly developed based on foreign operating systems such as Android and iOS, and their adaptation and support for the HarmonyOS NEXT system are severely insufficient, making it impossible to fully leverage HarmonyOS NEXT's distributed capabilities, cross-device collaboration capabilities, and the advantages of domestically developed underlying security.

[0004] 3. Inefficient development and maintenance The redundant development of basic functional components (such as photo taking, QR code scanning, unified login, etc.) by various applications has resulted in a serious waste of development resources. Furthermore, the fragmented application system leads to high costs for later version iterations, troubleshooting, and system maintenance, resulting in extremely low operational efficiency.

[0005] 4. Lack of safety management The lack of a unified security management system and inconsistent security standards for identity authentication, data transmission, and data storage across applications pose security risks such as data leakage, unauthorized access, and difficulty in tracing operational origins, failing to meet the high security requirements of energy companies such as power plants.

[0006] 5. Poor business adaptability General-purpose mobile platforms cannot meet the industrial-grade business characteristics of power plants. They lack sufficient encapsulation of the unique business logic of power plants, such as work orders, operation orders, equipment inspections, and defect management. Application development requires a lot of secondary customization and has a long development cycle.

[0007] For example, patent application CN 116382642 A discloses a military service-oriented framework based on the HarmonyOS operating system. This framework designs a high-performance service-oriented framework, adopts an nginx service engine based on the epoll model, and can provide high-throughput service request response. At the same time, different application services run in independent process spaces to avoid the situation where the failure of one service leads to the failure of all services. However, this military service-oriented framework based on HarmonyOS is geared towards military scenarios and focuses on lightweight, survivability and service-oriented deployment. It is not adapted to the characteristics and business logic of industrial-grade terminals in power plants, which leads to a narrow scope of application and cannot fully reflect the actual business scenarios and operational needs of power plants. Summary of the Invention

[0008] The purpose of this invention is to provide a mobile application method and system for power plants based on the HarmonyOS NEXT system, in order to solve the problem that the existing technology has a narrow scope of application and cannot fully reflect the actual business scenarios and operational needs of power plants.

[0009] To achieve the above objectives, the present invention adopts the following technical solution: In a first aspect, the present invention provides a power plant mobile application system based on the HarmonyOS NEXT system, including an adaptation layer, a front-end service layer, a business application layer and a back-end service layer. The adaptation layer interacts with the kernel of the HarmonyOS NEXT system to unify and integrate the native capability interfaces of the HarmonyOS NEXT system. The front-end service layer provides functional interfaces based on the native capability interfaces of the unified and integrated HarmonyOS NEXT system; The business application layer contains several business application modules, and each business application module implements its corresponding business function by calling the functional interface. The backend service layer contains several backend service modules. Each backend service module interacts with the frontend service layer and the business application layer, and is connected to the power plant information system.

[0010] A further improvement of the present invention is that the adaptation layer also includes a security underlying support module, which is connected to the Star Shield security architecture and Ark Compiler of the HarmonyOS NEXT system, and is used to perform dynamic permission control on the adaptation layer and provide a hardware-level trusted execution environment for the business application layer.

[0011] A further improvement of the present invention is that the native capability interface includes a distributed soft bus interface, a cross-device collaboration interface, a permission management interface, and a national cryptographic algorithm security library interface.

[0012] A further improvement of the present invention is that the functional interface includes a basic functional interface and a general functional interface.

[0013] A further improvement of this invention is that each business application module calls the functional interface through ArkWeb technology and JSBridge technology to implement the corresponding business functions.

[0014] A further improvement of this invention is that each business application module implements its corresponding business function by calling the functional interface, specifically: Each business application module implements application operation business functions, security control business functions, material management business functions, and auxiliary management business functions by calling the functional interfaces.

[0015] A further improvement of this invention is that it also includes a specification module for standardizing the data interaction behavior between the adaptation layer, the front-end service layer, the business application layer, and the back-end service layer.

[0016] A further improvement of the present invention is that it also includes a centralized security management module for centralized security management of the adaptation layer, the front-end service layer, the business application layer, and the back-end service layer.

[0017] A further improvement of this invention is that each backend service module interacts with the frontend service layer and the business application layer through the network interface of HarmonyOS NEXT.

[0018] Secondly, this invention provides a mobile application method for power plants based on the HarmonyOS NEXT system, including: Unify and integrate the native capability interfaces of the HarmonyOS NEXT system; Based on the native capability interfaces of the unified and integrated HarmonyOS NEXT system, functional interfaces are provided; Each business application module implements its corresponding business function by calling the aforementioned functional interface; Each back-end service module interacts with data and connects to the power plant's information system.

[0019] Compared with the prior art, the present invention has the following beneficial effects: The mobile application system for power plants based on the HarmonyOS NEXT system proposed in this invention has two main advantages. First, the adaptation layer unifies and integrates the native capability interfaces of the HarmonyOS NEXT system, making the mobile application system no longer dependent on a specific version or type of hardware capability, thus expanding its applicability. Second, the business application layer does not need to repeatedly develop interfaces to implement business functions; it only needs to call the function interfaces provided by the front-end service layer according to actual business needs to achieve the corresponding business functions. This operation also expands the applicability of the mobile application system for power plants. Moreover, this invention splits the business application layer into several independent business application modules, each corresponding to one or more business processes in the actual operation scenario of a power plant. These modules can be loaded, combined, and expanded on demand, enabling more comprehensive adaptation to the diverse business scenarios and operational needs of power plants. Attached Figure Description

[0020] Figure 1 This is a schematic diagram of the structure of the power plant mobile application system based on the HarmonyOS NEXT system in Embodiment 3 of the present invention. Detailed Implementation

[0021] To further understand the content of this invention, the invention will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the embodiments are merely illustrative and not limiting of the invention.

[0022] Example 1: This embodiment discloses a power plant mobile application system based on the HarmonyOS NEXT system. The power plant mobile application system based on the HarmonyOS NEXT system includes an adaptation layer, a front-end service layer, a business application layer, and a back-end service layer.

[0023] The adaptation layer interacts with the kernel of the HarmonyOS NEXT system to unify and integrate the native capability interfaces of the HarmonyOS NEXT system.

[0024] The front-end service layer provides functional interfaces based on the native capability interfaces of the unified and integrated HarmonyOS NEXT system.

[0025] The business application layer contains several business application modules, each of which implements its corresponding business functions by calling functional interfaces.

[0026] The backend service layer contains several backend service modules. Each backend service module interacts with the frontend service layer and the business application layer, and is connected to the power plant information system.

[0027] Example 2: This embodiment discloses a power plant mobile application system based on the HarmonyOS NEXT system. The power plant mobile application system based on the HarmonyOS NEXT system includes an adaptation layer, a front-end service layer, a business application layer, and a back-end service layer.

[0028] The adaptation layer interacts with the kernel of the HarmonyOS NEXT system to unify and integrate the native capability interfaces of the HarmonyOS NEXT system.

[0029] The front-end service layer provides functional interfaces based on the native capability interfaces of the unified and integrated HarmonyOS NEXT system.

[0030] The business application layer contains several business application modules, each of which implements its corresponding business functions by calling functional interfaces.

[0031] The backend service layer contains several backend service modules. Each backend service module interacts with the frontend service layer and the business application layer, and is connected to the power plant information system.

[0032] This embodiment's adaptation layer also includes a security underlying support module, which connects to the HarmonyOS NEXT system's Star Shield security architecture and Ark Compiler. This module is used to dynamically manage permissions for the adaptation layer and provide a hardware-level trusted execution environment for the business application layer.

[0033] The native capability interfaces in this embodiment include a distributed soft bus interface, a cross-device collaboration interface, a permission management interface, and a national cryptographic algorithm security library interface.

[0034] The functional interfaces in this embodiment include basic functional interfaces and general functional interfaces.

[0035] In this embodiment, each business application module implements its corresponding business functions by calling the functional interfaces through ArkWeb and JSBridge technologies.

[0036] In this embodiment, each business application module implements its corresponding business function by calling the aforementioned functional interface, specifically as follows: Each business application module implements its operational application functions, security control functions, materials management functions, and auxiliary management functions by calling functional interfaces. The following provides a detailed explanation of the operational application functions, security control functions, materials management functions, and auxiliary management functions: A. Running application services It covers the core operations of power plants, including mobile approval and execution of work orders, operation orders, and measure orders; reporting, dispatching, and handling of equipment defects; mobile recording and traceability of daily and periodic equipment inspections; and online filling and synchronization of operation logs.

[0037] 2. Security Management and Control Operations To achieve full-process control of safe production in power plants, including safety training, hazard investigation, violation detection and reporting, and safety briefings.

[0038] 3. Materials Management Operations It covers the entire lifecycle management of power plant materials, including material warehousing, outbound, inventory, inventory query, location and traceability of spare parts, and mobile approval of material procurement applications.

[0039] 4. Supporting management operations The auxiliary management functions include personnel attendance, work order management, equipment ledger query, data statistical analysis, message push, and other auxiliary management functions.

[0040] Each business application module is developed independently and deployed and released independently on the server side. There is no need to upgrade the mobile installation package, which enables real-time release. It can be flexibly added, removed and customized according to the business needs of the power plant, and supports the collaborative operation and data interoperability of multiple applications.

[0041] This embodiment of the power plant mobile application system based on the HarmonyOS NEXT system also includes a specification module, which is used to standardize the data interaction behavior between the adaptation layer, the front-end service layer, the business application layer and the back-end service layer.

[0042] This embodiment of the power plant mobile application system based on the HarmonyOS NEXT system also includes a centralized security management module, which is used to perform centralized security management of the adaptation layer, front-end service layer, business application layer and back-end service layer.

[0043] In this embodiment, each backend service module interacts with the frontend service layer and the business application layer through the network interface of HarmonyOS NEXT.

[0044] Example 3: The structural diagram of the power plant mobile application system based on the HarmonyOS NEXT system (hereinafter referred to as the system) of this invention is shown below. Figure 1 As shown, the following describes the mobile application system for power plants based on the HarmonyOS NEXT system (in...). Figure 1 The HarmonyOS mobile application framework will be used to describe this in detail.

[0045] This embodiment of the power plant mobile application system based on the HarmonyOS NEXT system includes an adaptation layer (in... Figure 1 In the context of HarmonyOS adaptation layer, the front-end service layer (represented by 1 HarmonyOS system adaptation layer) is used. Figure 1 The basic capability service layer is used to represent the business application layer (in the context of the two layers). Figure 1 In Chinese, the application layer (referred to as application) and the backend service layer (in...) are used to represent the business application layer and the backend service layer. Figure 1 (This is represented by a 4-layer backend service layer).

[0046] The adaptation layer interacts with the kernel of the HarmonyOS NEXT system to unify and integrate the native capability interfaces of the HarmonyOS NEXT system.

[0047] The front-end service layer provides functional interfaces based on the native capability interfaces of the unified and integrated HarmonyOS NEXT system.

[0048] The business application layer contains several business application modules, each implementing its corresponding business function by calling functional interfaces. In this embodiment, the business application layer specifically includes three business application modules: a runtime application module, a security control module, and a materials management module. These modules utilize ArkWeb and JSBridge technologies to call functional interfaces to implement the runtime application's business function, the security control's business function, and the materials management's business function, respectively.

[0049] The backend service layer contains several backend service modules. Each backend service module interacts with the frontend service layer and the business application layer via the HarmonyOS NEXT network interfaces (such as HTTP, HTTPS, and WebSocket). Figure 1 (represented by network communication), and respectively connected to the power plant's information system (such as SIS, ERP, and equipment management system, where SIS stands for Supervisory Information System, and ERP stands for Enterprise Resource Planning). This embodiment has four backend service modules specifically set up in the backend service layer (user backend service module, application runtime backend service module, security control backend service module, and materials management backend service module).

[0050] This embodiment's adaptation layer also includes a security underlying support module, which connects to the HarmonyOS NEXT system's Star Shield security architecture and Ark Compiler. This module is used to dynamically manage permissions for the adaptation layer and provide a hardware-level trusted execution environment for the business application layer.

[0051] The native capability interfaces in this embodiment include a distributed soft bus interface, a cross-device collaboration interface, a permission management interface, and a national cryptographic algorithm security library interface.

[0052] The adaptation layer will be described in detail below. The functions implemented by the adaptation layer include: A. Encapsulation of native system capabilities It provides secondary encapsulation of the native capabilities interfaces of the HarmonyOS NEXT system (including distributed soft bus, cross-device collaboration, system permission management, national cryptographic algorithm security library, etc.), shielding the underlying technical details and providing a unified system call entry point for the upper layers.

[0053] B. Standardization of Industrial Peripheral Drivers The industrial communication protocols and hardware drivers commonly used in power plants, such as NFC, infrared temperature measurement, Bluetooth, and QR code / barcode scanning, are encapsulated into a unified cross-platform API, so that the business application layer does not need to care about the specific hardware model.

[0054] 3. Business-oriented distributed capabilities The distributed soft bus of HarmonyOS NEXT is encapsulated into business-level interfaces, including "high-speed cross-device file transfer", "cross-device capability call" (such as using a mobile phone to call the NFC / camera module of a tablet or drone) and "real-time synchronization of device status".

[0055] 4. Security underlying support The Star Shield security architecture and Ark Compiler connect the HarmonyOS NEXT system, enabling dynamic permission control of the adaptation layer and providing a hardware-level trusted execution environment for the business application layer.

[0056] The backend service layer functionality in this embodiment is implemented through the following modules: A. Data Service Module: Provides unified database management (relational database and non-relational database), realizes centralized storage, query, update and backup of business data, connects to the database of the power plant information system, and realizes cross-system data synchronization and sharing.

[0057] B. Business Logic Processing Module: Encapsulates the core business logic of various business operations in the power plant (such as work order approval process, defect handling process, and material entry and exit rules), providing logical calculation and process control support for the business application layer.

[0058] C. Interface Service Module: Provides standardized backend interfaces to enable bidirectional data interaction with the business application layer, and also provides functions such as interface authentication, traffic control, and data format conversion.

[0059] C. Backend Management Module: Enables centralized control of the entire mobile application platform (power plant mobile application system), including functions such as user management, permission management, application management, data statistics, log query and system monitoring, and supports the visual operation and management of the platform (power plant mobile application system).

[0060] The functional interfaces in this embodiment include basic functional interfaces and general functional interfaces. Basic functional interfaces are implemented through basic functional component modules, while general functional interfaces are implemented through general service component modules. The basic functional component modules and general service component modules are described in detail below: A. Basic Functional Component Modules The basic functional component modules specifically include: General-purpose hardware interaction components: taking photos, recording videos, recording audio, and scanning codes (supporting QR codes / barcodes / industrial DM codes).

[0061] Industrial-grade interactive components: NFC tag reading and writing (for device electronic ID recognition), Bluetooth / infrared data acquisition (for vibration, temperature, and partial discharge measurement), positioning (GPS / BeiDou / indoor positioning), electronic signature and handwriting pad.

[0062] Data and storage components: local encrypted storage (SQLite + SM4 encryption), offline data caching and synchronization (for power plant network blind spots), and distributed file sharing.

[0063] System and sensing components: sensors (accelerometer, gyroscope, barometer), version updates, anomaly detection and logging.

[0064] B. General Service Component Module The general service component module specifically includes: Unified Identity and Permission Service Components: Unified Login (supports multi-account system, single sign-on, and integration with enterprise LDAP / AD), multi-dimensional identity authentication (account password, SMS verification, hardware terminal binding, biometrics), and fine-grained role and permission allocation (by department, position, and business domain).

[0065] The "Two Tickets" dedicated process component encapsulates the entire lifecycle of work tickets, operation tickets, and measure tickets—including creation, circulation, approval, electronic signatures, safety measure confirmation, and closed-loop archiving—into standardized service interfaces. Any upper-layer business application can directly call this component to complete the "Two Tickets" business without needing to repeatedly develop a process engine.

[0066] Unified Messaging and Alarm Component: Based on HarmonyOS NEXT push service, it enables hierarchical and categorized push of production alarms and task reminders, supports linkage with smart wearable devices (watches, smart helmets), and supports offline message caching and resending.

[0067] Data security components include: data transmission encryption (national cryptographic standard SM2 / SM4), data storage encryption (SM4), operation log recording (operator, time, content, terminal, location), and security auditing.

[0068] In this embodiment, the business application layer adopts a hybrid development model: the UI and non-sensitive business logic are developed using H5 / JS and deployed on the backend service layer 4 to achieve rapid iteration.

[0069] This embodiment of the power plant mobile application system based on the HarmonyOS NEXT system also includes a specification module, which is used to standardize the data interaction behavior between the adaptation layer, the front-end service layer, the business application layer, and the back-end service layer. The specification module is described in detail below: The specification module specifically includes: a. Interface Specification The interface types, calling methods, parameter formats, return formats, and error code systems are uniformly defined between different levels, business applications, and the platform and external systems. Synchronous / asynchronous interface calls are supported to ensure the universality and compatibility of the interfaces.

[0070] b. Data Specifications The format, encoding rules, naming conventions, and data types of core business data of power plants are uniformly defined to achieve standardized data management and support data sharing and interaction across applications and systems.

[0071] c. Development Specifications Establish application development standards based on the HarmonyOS NEXT system, including code writing standards, component development standards, version management standards, and testing standards, to ensure the standardization and normalization of platform development.

[0072] d. Deployment Specifications Establish deployment, upgrade, and rollback specifications for mobile application systems and applications in power plants, supporting unified deployment and batch upgrades across multiple terminals within the HarmonyOS NEXT ecosystem.

[0073] This embodiment of the power plant mobile application system based on the HarmonyOS NEXT system also includes a centralized security management module, which is used to centrally manage the security of the adaptation layer, front-end service layer, business application layer, and back-end service layer. The centralized security management module is described in detail below: The centralized security management module specifically includes: A. Identity Security Based on unified login and unified identity authentication, it realizes multi-dimensional identity verification (account password, SMS verification, hardware binding) and supports fine-grained role permission allocation (by department, by position, by business).

[0074] B. Transmission security National cryptographic algorithms are used to encrypt data transmitted between the cloud and between devices to ensure the confidentiality and integrity of data transmission.

[0075] C. Storage Security: Sensitive data in local and cloud storage is encrypted to implement hierarchical storage and access control, preventing data leakage.

[0076] D. Operational safety It enables full-process operation log recording (operator, operation time, operation content, operation terminal), supports the traceability and auditing of operation behavior, and provides real-time warnings and interception of illegal operations.

[0077] E. Endpoint Security The terminal security mechanism connected to the HarmonyOS NEXT system enables device authentication and access control for mobile terminals, and supports remote locking and data erasure of lost terminals.

[0078] The present invention has the following advantages: 1. It fills the technological gap in the field of mobile operation of HarmonyOS NEXT in power plants. Existing power industry frameworks are not based on the HarmonyOS system, and HarmonyOS-based frameworks are not geared towards power plant operations. This invention is the first to deeply integrate HarmonyOS NEXT's distributed soft bus, Star Shield security architecture, Ark Compiler, and core business processes of power plants, such as the "two-ticket, three-system" mechanism, achieving an independent and controllable full-stack technical solution.

[0079] 2. It has achieved true decoupling between "capabilities" and "business". Compared to the repetitive development of basic functions (such as taking photos, scanning codes, and logging in) in various business systems, this invention standardizes industrial interaction components and process components through the basic capability service layer (2), thereby improving the efficiency of new business development by more than 70% and the code reuse rate by more than 80%.

[0080] 3. A new mobile operation model integrating "device-edge-cloud" collaboration has been created. By leveraging the distributed soft bus of HarmonyOS NEXT, the framework of this invention supports seamless collaboration and low-latency data synchronization between mobile terminals and field intelligent devices (such as explosion-proof handheld terminals, inspection drones, intelligent robots, and smart helmets), realizing a real-time business closed loop such as "on-site photography - edge recognition - central archiving," which is impossible for traditional iOS / Android-based frameworks.

[0081] 4. Deeply adapted to the characteristics of industrial site operations in power plants This invention encapsulates industrial peripheral interfaces such as NFC, infrared, and Bluetooth, as well as dedicated process components such as work tickets and operation tickets, so that business application development does not need to worry about the underlying hardware and complex processes, significantly shortening the development cycle of power plant mobile applications.

[0082] 5. An independent and controllable security system covering "pipe-terminal-cloud" has been established. Based on the HarmonyOS NEXT Star Shield security model and national cryptographic algorithms, it achieves full-stack domestic security protection from terminal hardware, operating system, application framework to communication transmission and backend services, meeting the security and compliance requirements of critical infrastructure of energy enterprises.

[0083] Example 4: This embodiment describes how to use the power plant mobile application system based on the HarmonyOS NEXT system of the present invention to achieve collaborative inspection of "mobile terminal + explosion-proof handheld terminal + inspection drone". The process is described in detail below: Scenario description: The inspection task of the substation requires simultaneous inspection of high-altitude insulators, ground equipment cabinets, and surge arrester counters.

[0084] The following is a detailed explanation of the implementation process of collaborative inspection using "mobile terminal + explosion-proof handheld terminal + inspection drone": 1. Task Initiation: The operations personnel in the central control center issue the "Booster Station Inspection" task to the designated work team through the backend service layer. The inspection module in the business application layer receives the task and pushes it to the main equipment (HarmonyOS NEXT mobile phone) of the on-site personnel.

[0085] 2. Device Collaborative Networking: On-site personnel arrive at the site carrying a main mobile phone and an explosion-proof handheld terminal. The main mobile phone automatically discovers and securely authenticates nearby explosion-proof terminals and drones through the distributed soft bus interface of the adapter layer, establishing a trusted device group. Inspection tasks and route maps are migrated to the explosion-proof terminal screen with one click via a distributed file transfer interface.

[0086] 3. Drone Access and Data Acquisition: During high-altitude insulator inspections, personnel use their main mobile phone to call the "cross-device capability call" interface of the front-end service layer to wake up the drone and acquire real-time video streams. The mobile phone screen simultaneously displays the drone's image and control interface, allowing personnel to operate the drone to perform infrared and visible light photography of the insulators. Images acquired by the drone are transmitted back to the mobile phone in real time via a distributed soft bus.

[0087] 4. Ground equipment inspection: Maintenance personnel use an explosion-proof handheld terminal to approach the equipment cabinet, call the NFC component to read the equipment's electronic tag (KKS code), and call the Bluetooth component to connect to the handheld thermometer to obtain temperature data. All data is synchronized to the main mobile phone through a distributed file channel.

[0088] 5. Data Fusion and Reporting: The inspection application on the main mobile phone encapsulates drone images, NFC device information, temperature measurement data, and on-site photos into a complete inspection record. This inspection record is encrypted with SM4 and reported to the backend service layer via the 5G / power dedicated network, and is automatically archived in the equipment management system.

[0089] Example 5: The mobile application method for power plants based on the HarmonyOS NEXT system of this invention includes the following steps: Unify and integrate the native capability interfaces of the HarmonyOS NEXT system; Based on the native capability interfaces of the unified and integrated HarmonyOS NEXT system, functional interfaces are provided; Each business application module implements its corresponding business function by calling the aforementioned functional interface; Each back-end service module interacts with data and connects to the power plant's information system.

[0090] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that modifications or equivalent substitutions can still be made to the specific implementation of the present invention. Any modifications or equivalent substitutions that do not depart from the spirit and scope of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A mobile application system for power plants based on the HarmonyOS NEXT system, characterized in that, It includes an adaptation layer, a front-end service layer, a business application layer, and a back-end service layer; The adaptation layer interacts with the kernel of the HarmonyOS NEXT system to unify and integrate the native capability interfaces of the HarmonyOS NEXT system. The front-end service layer provides functional interfaces based on the native capability interfaces of the unified and integrated HarmonyOS NEXT system; The business application layer contains several business application modules, and each business application module implements its corresponding business function by calling the functional interface. The backend service layer contains several backend service modules. Each backend service module interacts with the frontend service layer and the business application layer, and is connected to the power plant information system.

2. The power plant mobile application system based on HarmonyOS NEXT system according to claim 1, characterized in that, The adaptation layer also includes a security underlying support module, which connects to the HarmonyOS NEXT system's Star Shield security architecture and Ark Compiler. This module is used to dynamically manage permissions for the adaptation layer and provide a hardware-level trusted execution environment for the business application layer.

3. The power plant mobile application system based on HarmonyOS NEXT system according to claim 1, characterized in that, The native capability interfaces include a distributed soft bus interface, a cross-device collaboration interface, a permission management interface, and a national cryptographic algorithm security library interface.

4. The power plant mobile application system based on HarmonyOS NEXT system according to claim 1, characterized in that, The functional interfaces include basic functional interfaces and general functional interfaces.

5. The power plant mobile application system based on HarmonyOS NEXT system according to claim 1, characterized in that, Each business application module uses ArkWeb and JSBridge technologies to call the functional interfaces to implement corresponding business functions.

6. The power plant mobile application system based on HarmonyOS NEXT system according to claim 1, characterized in that, Each business application module implements its corresponding business function by calling the functional interface, specifically: Each business application module implements application operation business functions, security control business functions, material management business functions, and auxiliary management business functions by calling the functional interfaces.

7. The power plant mobile application system based on HarmonyOS NEXT system according to claim 1, characterized in that, It also includes a specification module, which is used to standardize the data interaction behavior between the adaptation layer, the front-end service layer, the business application layer, and the back-end service layer.

8. The power plant mobile application system based on HarmonyOS NEXT system according to claim 1, characterized in that, It also includes a centralized security management module, which is used for centralized security management of the adaptation layer, front-end service layer, business application layer and back-end service layer.

9. A mobile application system for power plants based on the HarmonyOS NEXT system, characterized in that, Each backend service module interacts with the frontend service layer and the business application layer through the network interface of HarmonyOS NEXT.

10. A method for mobile application of power plants based on HarmonyOS NEXT system, characterized in that, Includes the following steps: Unify and integrate the native capability interfaces of the HarmonyOS NEXT system; Based on the native capability interfaces of the unified and integrated HarmonyOS NEXT system, functional interfaces are provided; Each business application module implements its corresponding business function by calling the aforementioned functional interface; Each back-end service module interacts with data and connects to the power plant's information system.

Images