Novel software architecture for helicopter airborne system and construction method of novel software architecture

Abstract

The invention belongs to the technical field of aviation airborne system design, and provides a helicopter airborne system-oriented novel software architecture and a construction method thereof, and the architecture comprises a hardware abstraction layer, a framework resource layer, an intelligent platform service layer and an application software layer from bottom to top. And the hardware abstraction layer realizes decoupling of hardware and basic software of an operating system. The framework resource layer supports operation of a hybrid key operating system, supports and isolates tasks and application programs with different key levels, software bases and computing power requirements, and provides basic computing communication resources and AI computing power resources. The intelligent platform service layer comprises middleware, a servitization function unit and a servitization management unit, and the servitization function unit comprises atomic services and enhanced services. And the application layer interacts with the intelligent platform service layer and is decoupled from a bottom software and hardware environment. The framework is suitable for unmanned / manned helicopters, and generalization of platform support and maximum reuse of software assets are achieved.

Description

Technical Field

[0001] This invention belongs to the field of avionics and airborne system design technology, and relates to a novel software architecture for helicopter airborne systems and its construction method. Background Technology

[0002] As the central nervous system of an unmanned helicopter, the airborne system integrates multiple subsystems, including avionics, electromechanical systems, flight control, communication and navigation, and mission systems. With the development of information technology, more and more flight capabilities are being defined by airborne system software, highlighting the increasingly central role of software in airborne systems.

[0003] Currently, mainstream airborne system software architectures, such as the widely used GARMIN G1000 series, generally adopt a three-layer structure: the bottom layer consists of hardware drivers that directly interact with various hardware components; the middle layer is the operating system responsible for managing and coordinating the operation of various software modules in the system; and the upper layer contains application programs that include functions such as air-to-ground communication, flight navigation, weather monitoring, terrain awareness, and aircraft status monitoring. In this architecture, to pursue ultimate operating efficiency, application software or functional software relies on the operating system to access underlying hardware resources, forming a strong binding relationship between the operating system and the underlying hardware resources.

[0004] This traditional, tightly coupled architecture has many insurmountable drawbacks: 1. Difficulty in expanding functionality: Adding any new functionality or modifying existing functionality often requires custom development at the operating system or even driver level, which is time-consuming and risky.

[0005] 2. Complex system upgrades: Upgrading hardware or operating systems often has far-reaching consequences, requiring the entire software stack to be re-adapted and verified, resulting in high costs.

[0006] 3. High lifecycle costs: Due to the deep integration of software and hardware, software cannot be reused across different platforms, resulting in a huge amount of repetitive development work and high maintenance costs.

[0007] 4. Lack of agility: Faced with rapidly changing task requirements, traditional architectures struggle to quickly generate new capabilities and cannot meet the agile iteration requirements of modern unmanned systems.

[0008] 5. Weak security protection: Security mechanisms are mostly peripheral additions, lacking a defense-in-depth system that penetrates both hardware and software, making it difficult to cope with increasingly complex network attacks.

[0009] While decoupling concepts such as Hardware Abstraction Layer (HAL) and microservices have emerged in the field of general-purpose computing, these technologies face significant challenges when directly applied to high-real-time and high-security airborne systems. For example, the communication overhead introduced by service-oriented architecture may compromise the deterministic nature of the system's real-time performance; static service composition cannot adapt to dynamic task scenarios; and the lack of proactive management of the system's runtime health status leads to insufficient system resilience.

[0010] Therefore, there is an urgent need for a brand-new software architecture designed specifically for highly reliable systems such as unmanned helicopters, which can completely break down the barriers between software and hardware while ensuring high real-time performance and high security of the system, and achieve agile development, rapid integration, dynamic optimization and inherent security protection of functions. Summary of the Invention

[0011] To address the core issues in existing technologies, such as strong coupling between hardware and software, difficulty in functional expansion, complexity of system upgrades, high lifecycle costs, and weak security protection, this invention discloses a novel software architecture for helicopter airborne systems. This novel software architecture achieves platform universality, independent evolution of functional software, plug-and-play hardware, and adaptive optimization of task execution through an integrated, layered, and decoupled design. Specifically, the novel software architecture includes a hardware abstraction layer, a framework resource layer, an intelligent platform service layer, and a platform application layer.

[0012] The hardware abstraction layer is deployed at the bottom layer and includes a standardized hardware interface encapsulation module. This module encapsulates the complex interfaces of the underlying hardware into standardized and universal application programming interfaces (APIs), thereby decoupling the hardware from the operating system's basic software. The framework resource layer is deployed on top of the hardware abstraction layer and includes a hybrid critical operating system runtime environment module, basic computing and communication resources, and AI computing power resources. The hybrid critical operating system runtime environment module supports the collaborative operation of real-time operating systems and non-real-time operating systems. The intelligent platform service layer is deployed on top of the framework resource layer and includes middleware, service-oriented functional units, and service-oriented management units. The platform application layer is deployed on top of the intelligent platform service layer, interacts with the intelligent platform service layer, and is decoupled from the underlying software and hardware environment.

[0013] Furthermore, the hardware abstraction layer also includes a functional clustering unit. The functional clustering unit divides the underlying hardware resources into a detection and sensing unit, an information access unit, a computing and storage unit, an actuation and control unit, and an energy and power unit according to the OODA integrated construction logic, and uniformly encapsulates the hardware resource interfaces within each unit.

[0014] Furthermore, when the architecture is deployed on a manned helicopter, the hardware abstraction layer also includes a cockpit human-machine interface unit, which encapsulates hardware interfaces related to pilot interaction.

[0015] Furthermore, in the framework resource layer, the hybrid critical operating system runtime environment module is used to provide a hybrid critical operating system environment that supports the coexistence of high-risk (critical mission) and low-risk (non-critical mission) operations in the aviation field; the basic computing and communication resources include general computing resources, low-speed high real-time network resources accessed on-site, and high-bandwidth business network resources for big data; the AI ​​computing power resources include intelligent operator libraries, algorithm libraries, lightweight model libraries, etc.

[0016] Furthermore, the service-oriented functional unit includes multiple atomic services and multiple enhanced services. Each atomic service encapsulates a single core function, and each enhanced service is formed by combining multiple atomic services according to predetermined logic.

[0017] Furthermore, the service-oriented functional unit also includes an intelligent health management module, which is a lightweight adaptive health management system that connects the framework resource layer and the intelligent platform service layer. It is used to monitor the performance indicators of each device in the airborne system and the overall system status performance indicators in real time, and to trigger service degradation, service migration, or operating system resource quota reallocation when performance degradation and / or potential faults are detected.

[0018] Furthermore, the service management unit includes a service framework and an orchestration and scheduling management framework. The service framework provides functions for registering, discovering, deploying, running, and governing atomic services and enhanced services. The orchestration and scheduling management framework connects the service functional units and, based on current task requirements, system resource status, and perception information, coordinates atomic services and / or enhanced services in an orderly manner according to rules to ensure stable and reliable operation.

[0019] Furthermore, the service management unit also includes a security framework that provides access control and access authorization services to verify the trusted proof provided by the atomic service when the service framework of the service management unit receives the atomic service registration, and to verify the trusted proof again before the call.

[0020] Furthermore, the middleware includes communication middleware, which is based on a standardized and universal interface supported by the operating system, unifies communication protocols, data formats and interface specifications, and adopts an identity-based zero-trust network communication mechanism to realize data transmission across devices, systems and networks.

[0021] Furthermore, the platform application layer includes an automatic flight function module, an autonomous planning function module, and a landing and return function module. The automatic flight function module, the autonomous planning function module, and the landing and return function module only interact with the intelligent platform service layer and are decoupled from the underlying software and hardware environment.

[0022] This invention also provides a method for constructing a novel software architecture for helicopter airborne systems. This method employs a parameterized digital prototype to perform full-stack simulation and testing on the hardware abstraction layer, the framework resource layer, the intelligent platform service layer, and the application layer. It also utilizes agile iteration to quickly verify the correctness and performance of the software version. The method includes the following steps: S1. Deploy standardized hardware interface encapsulation modules in the hardware abstraction layer, and abstract the interfaces of various physical hardware devices of the target helicopter platform to generate a unified hardware access application programming interface (API). S2. Deploy hybrid critical operating system runtime environment modules, basic computing and communication resources, and AI computing power resources at the framework resource layer; S3. Deploy middleware, service-oriented functional units, and service-oriented management units in the intelligent platform service layer. The service-oriented functional units include atomic services defined by standardized interfaces, enhanced services composed of atomic services, and an intelligent health management module. The service-oriented management units include a loosely coupled service framework, an orchestration and scheduling management framework, and a security framework. S4. Deploy a task application software module in the platform application layer. The task application software module only implements its functions by calling the services provided by the intelligent platform service layer. S5. Construct a digital twin simulation verification platform based on a parameterized digital prototype, and complete the full-stack functional simulation and shadow mode testing of the hardware abstraction layer, the framework resource layer, the intelligent platform service layer and the application layer in a virtual environment.

[0023] Compared with the prior art, the beneficial effects that at least one technical solution adopted in the embodiments of this specification can achieve include at least: 1. By encapsulating modules through standardized hardware interfaces in the hardware abstraction layer, the strong binding relationship between the operating system and the underlying hardware is successfully decoupled, achieving complete software-hardware decoupling. This design enables plug-and-play hardware and eliminates the need for the operating system to depend on a specific hardware platform, thereby enhancing the system's flexibility and adaptability.

[0024] 2. By presenting functionalities as atomic services, the system supports "develop once, reuse many times," demonstrating significant agility and scalability. Developing new features only requires combining or adding atomic services without altering the underlying architecture, greatly accelerating the rapid generation and iteration of capabilities. Furthermore, this modular design allows for flexible reuse of services across different application scenarios, further enhancing development efficiency.

[0025] 3. The introduction of a Dynamic Service Orchestration Engine (DSOE) and a Runtime Adaptive and Health Management System (RAHMS) enables the system to dynamically adjust and self-repair based on task requirements, system resource status, and environmental awareness. This not only improves the system's flexibility but also significantly enhances task success rate and system survivability in complex and adversarial environments.

[0026] 4. From Trusted Execution Environment (TEE) support at the Hardware Abstraction Layer, to trusted proofs and zero-trust communication mechanisms at the Intelligent Platform Service Layer, and behavior monitoring at the Platform Application Layer, an intrinsic security system is constructed that spans the entire software and hardware stack. This system effectively defends against advanced threats such as supply chain attacks and man-in-the-middle attacks, ensuring the security of the entire system.

[0027] 5. A digital twin simulation verification platform built using parametric digital prototypes has achieved deep integration of development and verification. This platform significantly shortens the software iteration cycle, reduces the high costs and security risks associated with physical testing, and improves the correctness and performance of new software versions.

[0028] The novel software architecture of this invention achieves complete decoupling between the platform application layer and the underlying layer, enabling the same application software to be seamlessly ported to different unmanned helicopters and even other unmanned platforms. This design maximizes the value of software assets and lays a solid foundation for building a cross-platform, cross-domain general-purpose resource pool. Attached Figure Description

[0029] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0030] Figure 1 This is a schematic diagram of the novel software architecture for an unmanned helicopter airborne system according to the present invention; Figure 2 This is a schematic diagram of a novel software architecture for manned helicopter airborne systems according to the present invention. Detailed Implementation

[0031] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0032] The following specific examples illustrate the implementation of this application. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. This application can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be noted that, in the absence of conflict, the following embodiments and features of the embodiments can be combined with each other. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0033] Traditional airborne system software architectures, such as flight control and avionics systems, are generally divided into three layers. Taking the widely used GARMIN G1000 series system as an example, the bottom layer consists of hardware drivers responsible for interacting with various hardware components; the middle layer is the operating system, which manages and coordinates the operation of various software modules within the system; and the upper layer comprises application programs, including functional modules such as air-to-ground communication, flight navigation, weather monitoring, terrain awareness, and aircraft status monitoring, enabling normal flight and mission execution. In this architecture, application software or functional software relies on the operating system to access the underlying hardware resources, creating a strong binding relationship between the operating system and the underlying hardware resources for higher operating efficiency. However, this also leads to problems such as difficulty in functional expansion, high upgrade complexity, and high lifecycle costs. With the rapid development of integrated circuits and software technologies, plug-and-play hardware, agile software iteration, and rapid capability generation have become the goals pursued by various fields, including aviation. However, the traditional layered architecture of airborne systems is no longer suitable for these new requirements.

[0034] This invention discloses a novel software architecture for helicopter airborne systems, adhering to the design principles of hardware-software decoupling, elastic scalability, and functional service encapsulation. It employs software-defined design technologies such as component-based design and standardized interfaces, combined with parametric digital prototypes, enabling development once and reuse multiple times. This agile thinking permeates all stages, achieving the goal of platform universality. This novel software architecture coordinates the requirements of various systems such as flight control and avionics, and through an integrated layered decoupling design approach, reconstructs the overall system software architecture into four layers, achieving platform universality, independent evolution of functional software, plug-and-play hardware, and adaptive optimization of mission execution.

[0035] Specifically, see Figure 1 and Figure 2As shown, the novel software architecture includes a hardware abstraction layer, a framework resource layer, an intelligent platform service layer, and a platform application layer.

[0036] The hardware abstraction layer is deployed at the bottom layer and includes a standardized hardware interface encapsulation module. This module encapsulates the complex interfaces of the underlying hardware into standardized and universal application programming interfaces (APIs), thereby decoupling the hardware from the operating system's basic software. The framework resource layer is deployed on top of the hardware abstraction layer and includes a hybrid critical operating system runtime environment module, basic computing and communication resources, and AI computing power resources. The hybrid critical operating system runtime environment module supports the collaborative operation of real-time operating systems and non-real-time operating systems. The intelligent platform service layer is deployed on top of the framework resource layer and includes communication middleware, service-oriented functional units, and service-oriented management units. The platform application layer is deployed on top of the intelligent platform service layer, interacts with the intelligent platform service layer, and is decoupled from the underlying software and hardware environment.

[0037] By decoupling the elements at each layer, a reconfigurable resource pool is provided for building an agile and flexible system. Simultaneously, each functional layer utilizes a software-defined common technology product platform based on airborne applications, achieving positive penetration of new technologies, ease of use, and intelligent empowerment throughout the entire process. This architecture supports single-aircraft flight missions for unmanned aerial vehicles (UAVs) as well as manned-unmanned collaborative tasks such as information detection, information sharing, and support coordination.

[0038] Furthermore, the design of the hardware abstraction layer allows the operating system to manage and control hardware resources simply by calling a unified interface, without needing to concern itself with hardware details, thus shielding the dependencies between basic software and hardware. The hardware abstraction layer in the new airborne system software architecture incorporates a functional clustering unit. This unit, following the integrated construction approach of OODA (Observe-Orientation-Decide-Act), redistributes and clusters the resources of traditional general-purpose airborne system subsystems such as avionics, flight control, electromechanical, electrical, and fuel and environmental control, enabling unified management and control, forming a unified system. Figure 1 and Figure 2 The system comprises five main logical functional units: a detection and sensing unit, an information access unit, a computing and storage unit, an actuation and control unit, and an energy and power unit. The hardware devices within each unit share the same logical function: to acquire the operating status and data of each hardware device and drive the device to execute corresponding control commands. Resource interfaces for each functional unit's hardware are uniformly encapsulated, and each part provides hardware access interfaces to services via APIs, shielding differences in hardware functional implementation and reducing customization and redundant development work for access devices.

[0039] In addition, see Figure 2As shown, when the new software architecture is deployed on a manned helicopter, the hardware abstraction layer also includes a cockpit human-machine interaction unit, which encapsulates hardware interfaces related to pilot interaction.

[0040] Furthermore, the framework resource layer is used to rationally manage basic hardware and software resources, effectively maximize performance, and support the efficient operation of functional software. In response to the application requirements of airborne systems such as high real-time performance, high security, and multi-functional integration, it provides a basic operating environment for a hybrid critical operating system that simultaneously meets the requirements of real-time and non-real-time operating systems, basic computing and communication resources such as general computing, real-time networks, and business networks, as well as intelligent advanced computing resources such as AI computing power resource frameworks and operator libraries. This provides strong support for achieving northbound application expansion and southbound hardware rapid integration and upgrades in an integrated airborne system architecture.

[0041] Specifically, in the framework resource layer, the hybrid critical operating system runtime environment module is used to provide a hybrid critical operating system environment that supports the coexistence of high-risk (critical mission) and low-risk (non-critical mission) environments in the aviation field; the basic computing and communication resources include general computing resources, low-speed high real-time network resources accessed on-site, and high-bandwidth business network resources for big data; the AI ​​computing power resources include intelligent operator libraries, algorithm libraries, lightweight model libraries, etc.

[0042] Furthermore, the intelligent platform service layer is used to decouple the basic software and platform software / application software, and mainly includes middleware, service-oriented functional units, service-oriented management units and other functional modules and operation management modules.

[0043] The service-oriented functional unit includes multiple atomic services and application-oriented basic services such as enhanced services formed by combinations of different atomic services. Each atomic service is divided based on functional granularity, encapsulating a single core function to meet real-time requirements. By establishing standardized interface specifications to meet the needs of airborne system applications, and unifying interface specifications and data formats, the functional software and basic software are decoupled, achieving the goal of "develop once, reuse many times." In the enhanced services, multiple atomic services are combined according to predetermined logic to meet specific application needs in the airborne system domain, facilitating application software calls and improving code execution efficiency. Common enhanced services in airborne systems include combined navigation services, etc.

[0044] The service management unit includes a loosely coupled service framework that provides registration, discovery, deployment, operation, and governance functions for atomic and enhanced services.

[0045] Furthermore, in typical application scenarios, atomic services and enhanced services are statically defined and composed. To quickly respond to the complexity and variability of future applications, the intelligent platform service layer provides orchestration and scheduling management, including a Dynamic Service Orchestration Engine (DSOE). This engine can dynamically select, combine, and schedule atomic services at runtime based on current task requirements, system resource status (such as computing power, power consumption, and network bandwidth), and environmental awareness information, generating optimal execution paths. For example, when performing an "autonomous reconnaissance" task, the orchestration engine can dynamically adjust the priority and parameter configuration of "image recognition service," "path planning service," and "communication encryption service" based on visibility and threat level. This engine can push service-oriented architecture from "static configuration" to "dynamic optimization," achieving task-driven adaptive capabilities. This dynamic orchestration based on runtime context is absent in traditional airborne systems or static microservice architectures, solving the problem of efficient resource utilization under changing task scenarios.

[0046] In an improved embodiment, the service management unit further includes a security framework, which is loosely coupled with the service framework and orchestration / scheduling management resources. The security framework provides access control and authorization services, serving as perimeter protection. It is used to verify the trusted proof provided by an atomic service when the service framework of the service management unit receives an atomic service registration, and to verify the trusted proof again before invocation.

[0047] Specifically, based on the needs of the task system, functional expansion can be achieved through a modular approach within a software-defined architecture, adding security mechanisms at each layer to build an internal security (Security-by-Design) system. For example, at the hardware abstraction layer, hardware abstraction supporting Trusted Execution Environments (TEEs) provides hardware-level isolation for mission-critical services. At the intelligent platform service layer, corresponding atomic services are required to provide trusted attestations upon registration, and the service framework verifies these attestations before invocation to ensure services have not been tampered with. For communication middleware, combining the high-performance and high-security requirements of the mission, identity-based zero-trust network communication is constructed. In this case, inter-service communication is untrusted by default and requires dynamic authentication and authorization. At the platform application layer, abnormal behavior of application software is detected by introducing behavioral baseline monitoring. This internal security (Security-by-Design) system shifts from "boundary defense" to "end-to-end trust," constructing a defense-in-depth system that spans both hardware and software. Trusted attestations and zero-trust communication are effective means of countering modern network attacks (such as supply chain attacks and man-in-the-middle attacks), creatively integrating information security with system architecture.

[0048] In an improved solution, besides design-level decoupling, the operating system lacks proactive management of system health and performance degradation during runtime. Therefore, an intelligent health management module can be deployed in the intelligent platform service layer. This module can be a lightweight adaptive health management system (RAHMS). RAHMS connects the framework resource layer and the intelligent platform service layer, and can be used to continuously monitor the performance indicators of each device (such as service response latency, CPU utilization, memory leaks, and hardware status) and the overall machine performance. For example, when performance degradation and / or potential faults are detected, RAHMS can trigger the following adaptive strategies: when computing power is insufficient, automatically switch the high-precision "AI target recognition service" to a low-precision mode for service degradation. When an abnormal fault occurs, migrate the relevant service from one computing node to another healthy node for service migration. It can also dynamically adjust the operating system's resource quotas for critical tasks to achieve resource reallocation. The RAHMS system can achieve intrinsic resilience, moving from passive fault tolerance to proactive health management. The closed-loop "Monitor-Analysis-Decision-Execution (MAPE)" adaptive loop is unmatched by traditional fixed architectures, significantly improving the system's survivability and task success rate in complex environments.

[0049] The middleware mainly includes communication middleware, which is based on standardized and universal interfaces supported by the operating system, unifies communication protocols, data formats and interface specifications, and adopts an identity-based zero-trust network communication mechanism to shield network protocols and hardware differences, select the optimal path, and provide efficient transmission across devices, systems and networks.

[0050] Furthermore, the platform application layer includes an automatic flight function module, an autonomous planning function module, and a landing and return function module. Through functional software / application software, it realizes functions such as automatic flight, autonomous planning, landing and return of the unmanned helicopter system. It is decoupled from the underlying software and hardware environment, and the required resources only interact with the intelligent platform service layer, which facilitates combination and expansion and enables cross-platform reuse.

[0051] Furthermore, this invention also provides a method for constructing the aforementioned novel software architecture for helicopter airborne systems. The development and integration of new functions of this novel software architecture rely on physical hardware, resulting in high costs and long cycles. This novel software architecture is constructed based on software-defined design technology using parametric digital prototypes. It can also support full-stack simulation and testing through parametric digital prototypes by building a digital twin simulation verification platform that is completely corresponding to the real system, thereby verifying the correctness and performance of the new version of the software.

[0052] The platform has the following functions: 1. Simulate the behavior of all hardware devices in a virtual environment; 2. Supports developers to complete full-stack simulation and testing, from atomic service development and service orchestration to application-layer functions, without physical hardware; 3. Provides "Shadow Mode" to run the new version of the software in parallel with the currently running software, and verifies its correctness and performance by comparing the output; This platform extends the concept of "software-defined" to the development and verification process, realizing "development is verification," which greatly shortens the software iteration cycle and reduces development risks. This is a disruptive improvement to the traditional linear process of "design-implementation-testing-deployment."

[0053] Specifically, the method includes the following steps: S1. Deploy standardized hardware interface encapsulation modules in the hardware abstraction layer, and abstract the interfaces of various physical hardware devices of the target helicopter platform to generate a unified hardware access application programming interface (API). S2. Deploy hybrid critical operating system runtime environment modules, basic computing and communication resources, and AI computing power resources at the framework resource layer; S3. Deploy middleware, service-oriented functional units, and service-oriented management units in the intelligent platform service layer. The service-oriented functional units include atomic services defined by standardized interfaces, enhanced services composed of atomic services, and an intelligent health management module. The service-oriented management units include a loosely coupled service framework, an orchestration and scheduling management framework, and a security framework. S4. Deploy a task application software module in the platform application layer. The task application software module only implements its functions by calling the services provided by the intelligent platform service layer. S5. Construct a digital twin simulation verification platform based on a parameterized digital prototype, and complete the full-stack functional simulation and shadow mode testing of the hardware abstraction layer, the framework resource layer, the intelligent platform service layer and the application layer in a virtual environment.

[0054] Compared with the prior art, the beneficial effects of the embodiments in this specification include at least the following: 1. By encapsulating modules through standardized hardware interfaces in the hardware abstraction layer, the strong binding relationship between the operating system and the underlying hardware is successfully decoupled, achieving complete software-hardware decoupling. This design enables plug-and-play hardware and eliminates the need for the operating system to depend on a specific hardware platform, thereby enhancing the system's flexibility and adaptability.

[0055] 2. By presenting functionalities as atomic services, the system supports "develop once, reuse many times," demonstrating significant agility and scalability. Developing new features only requires combining or adding atomic services without altering the underlying architecture, greatly accelerating the rapid generation and iteration of capabilities. Furthermore, this modular design allows for flexible reuse of services across different application scenarios, further enhancing development efficiency.

[0056] 3. The introduction of a Dynamic Service Orchestration Engine (DSOE) and a Runtime Adaptive and Health Management System (RAHMS) enables the system to dynamically adjust and self-repair based on task requirements, system resource status, and environmental awareness. This not only improves the system's flexibility but also significantly enhances task success rate and system survivability in complex and adversarial environments.

[0057] 4. From Trusted Execution Environment (TEE) support at the Hardware Abstraction Layer, to trusted proofs and zero-trust communication mechanisms at the Intelligent Platform Service Layer, and behavior monitoring at the Platform Application Layer, an intrinsic security system is constructed that spans the entire software and hardware stack. This system effectively defends against advanced threats such as supply chain attacks and man-in-the-middle attacks, ensuring the security of the entire system.

[0058] 5. A digital twin simulation verification platform built using parametric digital prototypes has achieved deep integration of development and verification. This platform significantly shortens the software iteration cycle, reduces the high costs and security risks associated with physical testing, and improves the correctness and performance of new software versions.

[0059] In summary, the novel software architecture of this invention achieves complete decoupling between the platform application layer and the underlying layer, enabling the same application software to be seamlessly ported to different unmanned helicopters and even other unmanned platforms. This design maximizes the value of software assets and lays a solid foundation for building a cross-platform, cross-domain general-purpose resource pool.

[0060] Obviously, those skilled in the art should understand that the above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Various modifications and variations of the embodiments of the present invention are possible for those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A novel software architecture for helicopter airborne systems, characterized in that, include: The hardware abstraction layer, deployed at the bottom layer, includes standardized hardware interface encapsulation modules. It encapsulates the complex interfaces of the underlying hardware into standardized and general-purpose application programming interfaces (APIs), thereby decoupling the hardware from the operating system's basic software. The framework resource layer, deployed on top of the hardware abstraction layer, includes a hybrid critical operating system runtime environment module, basic computing and communication resources, and AI computing power resources. The hybrid critical operating system runtime environment module supports the collaborative operation of real-time operating systems and non-real-time operating systems. The intelligent platform service layer is deployed on top of the framework resource layer and includes middleware, service-oriented functional units, and service-oriented management units. The platform application layer is deployed on top of the intelligent platform service layer, interacts with the intelligent platform service layer, and is decoupled from the underlying software and hardware environment.

2. The novel software architecture for helicopter airborne systems according to claim 1, characterized in that, The hardware abstraction layer also includes a functional clustering unit. The functional clustering unit divides the underlying hardware resources into a detection and sensing unit, an information access unit, a computing and storage unit, an actuation and control unit, and an energy and power unit according to the OODA integrated construction logic, and uniformly encapsulates the hardware resource interfaces in each unit.

3. The novel software architecture for helicopter airborne systems according to claim 2, characterized in that, When the architecture is deployed on a manned helicopter, the hardware abstraction layer also includes a cockpit human-machine interface unit, which encapsulates hardware interfaces related to pilot interaction.

4. The novel software architecture for helicopter airborne systems according to claim 1, characterized in that, The service-oriented functional unit includes multiple atomic services and multiple enhanced services. Each atomic service encapsulates a single core function, and each enhanced service is formed by combining multiple atomic services according to predetermined logic.

5. The novel software architecture for helicopter airborne systems according to claim 4, characterized in that, The service-oriented functional unit also includes an intelligent health management module, which is a lightweight adaptive health management system that connects the framework resource layer and the intelligent platform service layer. It is used to monitor the performance indicators of each device in the airborne system and the overall system status performance indicators in real time, and to trigger service degradation, service migration or operating system resource quota reallocation when performance degradation and / or potential faults are detected.

6. The novel software architecture for helicopter airborne systems according to claim 1 or 4, characterized in that, The service-oriented management unit includes a service framework and an orchestration and scheduling management framework. The service framework provides functions for registering, discovering, deploying, running, and governing atomic services and enhanced services. The orchestration and scheduling management framework connects the service-oriented functional units and, based on current task requirements, system resource status, and perception information, coordinates atomic services and / or enhanced services in an orderly manner according to rules to ensure stable and reliable operation.

7. The novel software architecture for helicopter airborne systems according to claim 6, characterized in that, The service management unit also includes a security framework that provides access control and access authorization services. When the service framework of the service management unit receives an atomic service registration, it verifies the trusted proof provided by the atomic service and verifies the trusted proof again before invocation.

8. The novel software architecture for helicopter airborne systems according to claim 1, characterized in that, The middleware includes communication middleware, which is based on a standardized and universal interface supported by the operating system, unifying communication protocols, data formats and interface specifications, and adopting an identity-based zero-trust network communication mechanism to realize data transmission across devices, systems and networks.

9. The novel software architecture for helicopter airborne systems according to claim 1, characterized in that, The platform application layer includes an automatic flight function module, an autonomous planning function module, and a landing and return function module. The automatic flight function module, the autonomous planning function module, and the landing and return function module only interact with the intelligent platform service layer and are decoupled from the underlying software and hardware environment.

10. A method for constructing a novel software architecture for helicopter airborne systems as described in claims 1 to 9, characterized in that, A parametric digital prototype is used to perform full-stack simulation and testing on the hardware abstraction layer, the framework resource layer, the intelligent platform service layer, and the application layer, and to perform agile iteration to quickly verify the correctness and performance of the software version. The method includes: Deploy standardized hardware interface encapsulation modules in the hardware abstraction layer, and abstract the interfaces of various physical hardware devices of the target helicopter platform to generate a unified hardware access application programming interface (API). Deploy hybrid critical operating system runtime environment modules, basic computing and communication resources, and AI computing power resources at the framework resource layer; The middleware, service-oriented functional units, and service-oriented management units are deployed in the intelligent platform service layer. The service-oriented functional units include atomic services defined by standardized interfaces, enhanced services composed of atomic services, and an intelligent health management module. The service-oriented management units include a loosely coupled service framework, an orchestration and scheduling management framework, and a security framework. A task application software module is deployed at the platform application layer. The task application software module implements its functions only by calling the services provided by the intelligent platform service layer. A digital twin simulation and verification platform is built based on a parameterized digital prototype. In a virtual environment, the full-stack functional simulation and shadow mode testing of the hardware abstraction layer, the framework resource layer, the intelligent platform service layer, and the application layer are completed.

Images