CN115314546A - Dynamic self-adaptive architecture of aircraft avionics system - Google Patents
Dynamic self-adaptive architecture of aircraft avionics system Download PDFInfo
- Publication number
- CN115314546A CN115314546A CN202210793293.8A CN202210793293A CN115314546A CN 115314546 A CN115314546 A CN 115314546A CN 202210793293 A CN202210793293 A CN 202210793293A CN 115314546 A CN115314546 A CN 115314546A
- Authority
- CN
- China
- Prior art keywords
- service
- layer
- platform
- specific
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 230000005540 biological transmission Effects 0.000 claims abstract description 25
- 230000006978 adaptation Effects 0.000 claims abstract description 14
- 238000004891 communication Methods 0.000 claims abstract description 8
- 238000006243 chemical reaction Methods 0.000 claims description 16
- 230000003044 adaptive effect Effects 0.000 claims description 12
- 230000006870 function Effects 0.000 claims description 12
- 230000036541 health Effects 0.000 claims description 12
- 238000012544 monitoring process Methods 0.000 claims description 12
- 230000007246 mechanism Effects 0.000 claims description 8
- 238000012545 processing Methods 0.000 claims description 4
- 230000006399 behavior Effects 0.000 claims description 3
- 238000005192 partition Methods 0.000 claims description 3
- 238000004458 analytical method Methods 0.000 claims description 2
- 238000004364 calculation method Methods 0.000 claims description 2
- 238000013519 translation Methods 0.000 claims description 2
- 238000009472 formulation Methods 0.000 claims 1
- 239000000203 mixture Substances 0.000 claims 1
- 238000013461 design Methods 0.000 abstract description 4
- 238000007726 management method Methods 0.000 description 27
- 238000010586 diagram Methods 0.000 description 5
- 230000008520 organization Effects 0.000 description 4
- 230000003993 interaction Effects 0.000 description 3
- 206010063385 Intellectualisation Diseases 0.000 description 2
- 238000000034 method Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 230000007723 transport mechanism Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000007717 exclusion Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/2885—Hierarchically arranged intermediate devices, e.g. for hierarchical caching
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
- G06F13/4204—Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus
- G06F13/4221—Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus being an input/output bus, e.g. ISA bus, EISA bus, PCI bus, SCSI bus
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
Abstract
The application belongs to the technical field of structural design of aircraft avionics systems, and particularly relates to a dynamic self-adaptive architecture of an aircraft avionics system, which comprises the following steps: the application layer is used for residing a platform service instance and providing a platform high-level abstract service; the specific service layer is used for residing a specific service instance of the platform and providing platform specific service for the application layer; the service framework layer is used for managing a middleware, a platform service instance and a platform specific service instance for the service; the transmission service layer is composed of communication services and provides transmission service interfaces for the specific service layer, the application layer and the service framework layer; the I/O service layer provides adaptation of a hardware driving interface and provides a hardware driving standardized interface for a specific service layer; and the operating system layer is used for residing basic system services, providing and controlling access to resources of the computing platform and providing support for running the application layer, the specific service layer, the service framework layer, the transmission service layer and the I/O service layer.
Description
Technical Field
The application belongs to the technical field of structural design of aircraft avionics systems, and particularly relates to a dynamic self-adaptive architecture of an aircraft avionics system.
Background
At present, most of airplane avionic system architectures adopt tightly coupled system architectures, flexible and dynamic system capability organization modes are not supported, single airplanes and even sharing of information, resources and services in the whole system are difficult to realize, interaction and coordination capabilities are weak, and intellectualization and self-organization of a cross-platform multi-airplane system cannot be effectively supported.
The present application has been made in view of the above-mentioned technical drawbacks.
It should be noted that the above background disclosure is only for the purpose of assisting understanding of the inventive concept and technical solutions of the present invention, and does not necessarily belong to the prior art of the present patent application, and the above background disclosure should not be used for evaluating the novelty and inventive step of the present application without explicit evidence to suggest that the above content is already disclosed at the filing date of the present application.
Disclosure of Invention
It is an object of the present application to provide an aircraft avionics system dynamic adaptive architecture to overcome or mitigate the technical drawbacks of at least one aspect of the known existence.
The technical scheme of the application is as follows:
an aircraft avionics system dynamic adaptation architecture, comprising:
the application layer is used for residing a platform service instance and providing a platform high-level abstract service;
the specific service layer is used for residing a specific service instance of the platform and providing platform specific service for the application layer;
the service framework layer is used for managing a middleware, a platform service instance and a platform specific service instance for the service;
the transmission service layer is composed of communication services and provides transmission service interfaces for a specific service layer, an application layer and a service framework layer;
the I/O service layer provides adaptation of a hardware driving interface and provides a hardware driving standardized interface for a specific service layer;
the operating system layer is used for residing basic system services, providing and controlling access to computing platform resources and providing support for the operation of an application layer, a specific service layer, a service framework layer, a transmission service layer and an I/O service layer.
According to at least one embodiment of the application, in the dynamic adaptive architecture of the aircraft avionics system, the platform high-level abstract service includes ICDs fusing different devices, data calculation analysis and policy making.
According to at least one embodiment of the application, in the aircraft avionics system dynamic adaptive architecture, the platform-specific services include device ICD processing and specific data management and conversion.
According to at least one embodiment of the present application, in the aircraft avionics system dynamic adaptive architecture, the platform service instance and the platform specific service instance are managed specifically, the platform service instance and the platform specific service instance are supported by registration, update, location, distribution, service route management, state management, qoS management, log service, configuration service, and health monitoring service.
According to at least one embodiment of the application, in the aircraft avionics system dynamic adaptive architecture, the operating system layer comprises an operating system, a low-level health monitoring component, a program language runtime, a component framework, a life cycle management and a low-level configuration service.
According to at least one embodiment of the present application, in the dynamic adaptive architecture of an aircraft avionics system, the specific service layer includes:
the platform specific equipment service module is used for providing data service of equipment for the application layer;
and the platform specific common service module provides platform general service components including configuration service, log service and health monitoring service.
According to at least one embodiment of the present application, in the aircraft avionics system dynamic adaptive architecture, the service framework layer includes:
the RPC layer is used for requesting/responding platform service examples and platform specific service examples;
the service calling function chain provides platform service examples and platform specific service example calling sections for users to expand;
the service registration center is responsible for recording, inquiring and notifying the platform service instance and the platform specific service instance;
the service administration center visually monitors and maintains the service examples of the platform and the health condition, monitoring information, state data and call chains of the specific service examples of the platform.
According to at least one embodiment of the present application, in the above dynamic adaptive architecture of an aircraft avionics system, the transport service layer includes:
the data distribution module abstracts a specific transmission mechanism and provides a transmission service interface for a specific service layer, an application layer and a service framework layer;
the configuration management module is used for providing a configuration management function and a transmission mechanism selection;
the QoS management module is used for adjusting data distribution behaviors;
the data conversion module is used for realizing the conversion of data of different data types;
and the paradigm conversion module is used for realizing the conversion of the message paradigm and the protocol paradigm.
According to at least one embodiment of the present application, in the above dynamic adaptive architecture for an aircraft avionics system, the I/O service layer includes:
the I/O service management module initializes and configures the specified I/O equipment according to the configuration file and manages the equipment state;
and the I/O data moving module is used for moving the I/O equipment data to the platform specific service assembly when the I/O equipment data and the corresponding platform specific service assembly are not in the same partition or address space.
The application has at least the following beneficial technical effects:
the dynamic self-adaptive architecture of the aircraft avionics system is provided, wherein a service framework layer, a transmission service layer, an I/O service layer and an operating system layer are designed to provide functional interfaces for service examples of a specific service layer and an application layer together, the inconsistency of a bottom layer can be shielded for the service examples, so that the dynamic self-adaptive architecture has stronger dynamic self-adaptive capacity, a flexible and dynamic system capacity organization mode can be supported, the sharing of information, resources and services in a single aircraft and even the whole system can be realized, the interaction and coordination capacity is enhanced, and the intellectualization and self-organization of the cross-platform multi-aircraft system can be effectively supported.
Drawings
FIG. 1 is a schematic diagram of a dynamic adaptive architecture of an aircraft avionics system provided by an embodiment of the present application;
FIG. 2 is a schematic diagram of an I/O service layer provided by an embodiment of the present application;
FIG. 3 is a schematic diagram of a particular service layer provided by an embodiment of the present application;
fig. 4 is a schematic diagram of a transport service layer provided in an embodiment of the present application;
fig. 5 is a schematic diagram of a servitization framework layer provided by an embodiment of the present application.
For a better understanding of the present embodiments, certain elements of the drawings may be omitted, enlarged or reduced, and do not represent actual product dimensions, and the drawings are for illustrative purposes only and are not to be construed as limiting the present patent.
Detailed Description
In order to make the technical solutions and advantages of the present application clearer, the technical solutions of the present application will be further clearly and completely described in the following detailed description with reference to the accompanying drawings, and it should be understood that the specific embodiments described herein are only some of the embodiments of the present application, and are only used for explaining the present application, but not limiting the present application. It should be noted that, for convenience of description, only the parts related to the present application are shown in the drawings, other related parts may refer to general designs, and the embodiments and technical features in the embodiments in the present application may be combined with each other to obtain a new embodiment without conflict.
In addition, unless otherwise defined, technical or scientific terms used in the description of the present application shall have the ordinary meaning as understood by one of ordinary skill in the art to which the present application belongs. The terms "upper", "lower", "left", "right", "center", "vertical", "horizontal", "inner", "outer", and the like used in the description of the present application, which indicate orientations, are used only to indicate relative directions or positional relationships, and do not imply that the devices or elements must have a specific orientation, be constructed and operated in a specific orientation, and when the absolute position of the object to be described is changed, the relative positional relationships may be changed accordingly, and thus, should not be construed as limiting the present application. The use of "first," "second," "third," and the like in the description of the present application is for descriptive purposes only to distinguish between different components and is not to be construed as indicating or implying relative importance. The use of the terms "a," "an," or "the" and similar referents in the description of the application should not be construed as an absolute limitation of quantity, but rather as the presence of at least one. The word "comprising" or "comprises", and the like, when used in this description, is intended to specify the presence of stated elements or items, but not the exclusion of other elements or items.
Further, it is noted that, unless expressly stated or limited otherwise, the terms "mounted," "connected," and the like are used in the description of the invention in a generic sense, e.g., connected as either a fixed connection or a removable connection or integrally connected; can be mechanically or electrically connected; they may be directly connected or indirectly connected through an intermediate medium, or they may be connected through the inside of two elements, and those skilled in the art can understand their specific meaning in this application according to the specific situation.
The present application is described in further detail below with reference to fig. 1 to 5.
An aircraft avionics system dynamic adaptation architecture, comprising: an application layer, a specific service layer, a servitization framework layer, a transport service layer, an I/O service layer, and an operating system layer, as shown in FIG. 1.
The service instance of the airplane onboard system can reside in a specific service layer and an application layer, wherein the service instance refers to a component which runs in the system and provides a certain service, and is different from the traditional onboard application, the service instance emphasizes a dynamic concept, dynamically joins and exits, and can be discovered by a service caller, and the service framework layer provides the function of service management middleware and supports registration, updating, positioning and the like of the service instance.
The service instance residing in the specific service layer is related to the processing of the on-board platform device ICD, and provides platform specific services; service instances residing at the application layer provide services with higher level abstractions, such as fusing ICDs of different devices, providing data analysis, computation, policy making, and the like.
The operating system layer is where the underlying system services reside, provides and controls access to computing platform resources, and provides support for the running of all other layer components, including various operating systems, low-level health monitoring components, programming language runtime, component frameworks, lifecycle management, low-level configuration services, and the like.
The I/O service layer provides adaptation to a hardware device driving interface provided by a supplier, and provides a standardized interface of hardware devices and drivers for a specific service layer, so that the specific service layer does not need to concern specific parts of a driver manufacturer, and only needs to concern interface data.
The specific service layer is responsible for the management of platform specific data, translation (the transition between ICD and service management layers). Platform-specific service instances reside at this layer, such as a platform-specific display service abstracting the interface of a GPU or other display device as a display service instance. The service instance of the layer interacts with the I/O service layer downwards, accesses specific hardware equipment, interacts with the service supporting layer upwards and provides specific equipment service for the application layer.
The transmission service layer is composed of various communication services, shields the difference of a transmission mechanism and data access, provides a uniform transmission service interface for a service instance and a service caller, is responsible for data distribution between the service instance and the caller, and can also comprise functions of priority management, protocol conversion and the like.
The service framework layer provides a unified management function for the service instance by using a transmission service interface provided by the transmission service layer, and the unified management function comprises the following steps: service routing management, service registration, distribution, state management, qoS management, higher level (where higher level corresponds to lower level in the operating system layer) logging services, configuration services, health monitoring services, etc.
The service instance residing in the application layer, unlike the service instance residing in a particular service layer, contains functionality to provide business logic, and because of the cooperation of the first layers, the application layer does not need to be concerned with hardware and sensors, and is not tied to an operating system or communication mechanism, which is highly portable.
In some alternative embodiments, the I/O service layer mainly includes an I/O service management module, an I/O data movement module, as shown in fig. 2.
The I/O service management module is responsible for initializing and configuring the specified I/O equipment according to the configuration file and managing the equipment state; a plurality of I/O service components can share one I/O service management module to realize centralized I/O service management.
When the I/O service components and the platform specific service components providing the I/O service are not in the same partition or address space, the I/O data moving module can complete the movement of the I/O device data to the platform specific service components, and when the I/O service components and the platform specific service components are in the same address space, the I/O data moving module encapsulates the original I/O bus interface.
In some alternative embodiments, the specific service layer is composed of platform specific device service modules, platform specific common service modules, as shown in fig. 3.
The platform specific device service module provides data services of certain onboard devices to the upper layer application. An onboard device may occupy a platform-specific device service component by itself or share a service component with multiple devices of the same type. At this time, the service component has the capability of managing the replacement between the devices, and the redundancy of the service of the onboard device can be increased.
The platform specific common services module includes service components that provide common services for the platform, such as configuration services, logging services, health monitoring services, and the like.
The service component of the specific service layer can register service information into the service framework layer in an initialization stage, when the application layer establishes connection with the component of the specific service layer through the service framework layer, communication can be carried out through the transmission service layer, and the platform specific service component reads equipment information through an interface of the I/O service layer and sends the equipment information to the application layer after processing.
In some optional embodiments, the transport service layer provides a communication service framework independent of a specific data transport mechanism, provides communication services and standard API interfaces for upper layer applications, and mainly includes a data distribution module, a configuration management module, a QoS management module, a data conversion module, and a paradigm conversion module, as shown in fig. 4.
The data distribution module abstracts a specific transmission mechanism and can provide a standard transmission service interface for upper-layer services.
The configuration management module provides configuration management functions and transport mechanism selection, improving cross-platform portability by avoiding software code binding to specific hardware.
The QoS management module allows the transmission of information to meet specific requirements and quality of service, adjusting data distribution behavior.
The data conversion module realizes the conversion of data of different data types.
The paradigm conversion module realizes the conversion of the message paradigm and the protocol paradigm.
In some optional embodiments, the servitization framework layer splits the traditional onboard service to improve scalability, make deployment more flexible, and improve fault tolerance and development efficiency, and mainly includes an RPC layer, a service call responsibility chain, a service registration center, and a service administration center, as shown in fig. 5.
The RPC layer is used for request/response type service instances, and comprises serialization and deserialization components and an interface proxy layer for shielding the implementation of the underlying calls. For a service caller, the interface of a service provider is packaged into a remote service call; for the service provider, the implementation maps the method name, parameter value in the caller request message to the local interface implementation and performs the return result.
The service call responsibility chain provides a plurality of service call sections for the user to expand, such as service call performance statistics, service call failure retransmission mechanism and the like.
The service registration center is responsible for recording, inquiring and notifying the service, is an intermediary of the service instance and does not participate in the service instance using process, so that the addition of a new service is only influenced even if the service registration center is unavailable, and the calling of an old service is not influenced.
Service administration centers are typically used by ground test personnel who use service administration interfaces or terminals to visually monitor and maintain the health, monitoring information, status data, call chains, etc. of the service to determine that the service is operating as expected.
The dynamic self-adaptive architecture of the aircraft avionics system disclosed by the application functionally supports the avionics system nodes and the application intelligent organization which are distributed on various heterogeneous aircrafts, and the avionics system nodes and the application intelligent organization cooperate with each other to complete tasks; logically, based on a unified architecture and an interface, a system grading mode is adopted to realize the separation of the application and the platform, support the mixed operation of multi-level application, and simultaneously, a standardization mode is adopted to support the internal function iteration of the system, the application and the platform; on the aspect of interaction, information and data are seamlessly shared in the whole battle field based on interconnection among nodes with dynamically variable topology.
It will be appreciated by those skilled in the art that the various modules, units, and/or modules of the aircraft avionics system dynamic adaptive architecture disclosed in the embodiments of the present application can be implemented in electronic hardware, computer software, or a combination of both, and for clarity of illustrating the interchangeability of hardware and software, the functions described herein are generally described in terms of whether they are implemented in hardware or software, and depending on the particular application and design constraints of the solution, those skilled in the art can choose different ways to implement the described functions for each particular application and its actual constraints, but such implementation should not be considered as exceeding the scope of the present application.
The embodiments are described in a progressive mode in the specification, the emphasis of each embodiment is on the difference from the other embodiments, and the same and similar parts among the embodiments can be referred to each other.
Having thus described the present application in connection with the preferred embodiments illustrated in the accompanying drawings, it will be understood by those skilled in the art that the scope of the present application is not limited to those specific embodiments, and that equivalent modifications or substitutions of related technical features may be made by those skilled in the art without departing from the principle of the present application, and those modifications or substitutions will fall within the scope of the present application.
Claims (9)
1. An aircraft avionics system dynamic adaptive architecture, comprising:
the application layer is used for residing a platform service instance and providing a platform high-level abstract service;
the specific service layer is used for residing a specific service instance of the platform and providing platform specific service for the application layer;
the service framework layer is used for managing a middleware, a platform service instance and a platform specific service instance for the service;
the transmission service layer is composed of communication services and provides transmission service interfaces for the specific service layer, the application layer and the service framework layer;
the I/O service layer provides adaptation of a hardware driving interface and provides a hardware driving standardized interface for a specific service layer;
and the operating system layer is used for residing basic system services, providing and controlling access to resources of the computing platform and providing support for running the application layer, the specific service layer, the service framework layer, the transmission service layer and the I/O service layer.
2. The aircraft avionics system dynamic adaptation architecture of claim 1,
the platform high-level abstract service comprises ICD fusing different devices, data calculation analysis and strategy formulation.
3. The aircraft avionics system dynamic adaptation architecture of claim 1,
platform specific services include device ICD processing, management and translation of specific data.
4. The aircraft avionics system dynamic adaptation architecture of claim 1,
the management platform service instance and the platform specific service instance specifically comprise support platform service instance, registration, update, positioning, distribution, service route management, state management, qoS management, log service, configuration service and health monitoring service of the platform specific service instance.
5. The aircraft avionics system dynamic adaptation architecture of claim 1,
the operating system layer comprises an operating system, a low-level health monitoring component, a program language runtime, a component framework, life cycle management and low-level configuration services.
6. The aircraft avionics system dynamic adaptation architecture of claim 1,
the specific service layer includes:
the platform specific equipment service module is used for providing data service of equipment for the application layer;
and the platform specific common service module provides platform general service components including configuration service, log service and health monitoring service.
7. The aircraft avionics system dynamic adaptation architecture of claim 1,
the service framework layer comprises:
the RPC layer is used for requesting/responding platform service instances and platform specific service instances;
the service calling function chain provides platform service examples and platform specific service example calling sections for users to expand;
the service registration center is responsible for recording, inquiring and notifying the platform service instance and the platform specific service instance;
the service administration center visually monitors and maintains the service examples of the platform and the health condition, monitoring information, state data and call chains of the specific service examples of the platform.
8. The aircraft avionics system dynamic adaptation architecture of claim 1,
the transport service layer includes:
the data distribution module abstracts a specific transmission mechanism and provides a transmission service interface for a specific service layer, an application layer and a service framework layer;
the configuration management module is used for providing a configuration management function and a transmission mechanism selection;
the QoS management module is used for adjusting data distribution behaviors;
the data conversion module is used for realizing the conversion of data of different data types;
and the paradigm conversion module is used for realizing the conversion of the message paradigm and the protocol paradigm.
9. The aircraft avionics system dynamic adaptation architecture of claim 1,
the I/O service layer includes:
the I/O service management module initializes and configures the specified I/O equipment according to the configuration file and manages the equipment state;
and the I/O data moving module is used for moving the I/O equipment data to the platform specific service component when the I/O equipment data and the corresponding platform specific service component are not in the same partition or address space.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210793293.8A CN115314546A (en) | 2022-07-05 | 2022-07-05 | Dynamic self-adaptive architecture of aircraft avionics system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210793293.8A CN115314546A (en) | 2022-07-05 | 2022-07-05 | Dynamic self-adaptive architecture of aircraft avionics system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115314546A true CN115314546A (en) | 2022-11-08 |
Family
ID=83856987
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210793293.8A Pending CN115314546A (en) | 2022-07-05 | 2022-07-05 | Dynamic self-adaptive architecture of aircraft avionics system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115314546A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070127460A1 (en) * | 2005-12-02 | 2007-06-07 | The Boeing Company | Scalable On-Board Open Data Network Architecture |
| US20160057075A1 (en) * | 2014-08-20 | 2016-02-25 | At&T Intellectual Property I, L.P. | Load Adaptation Architecture Framework for Orchestrating and Managing Services in a Cloud Computing System |
| CN107943459A (en) * | 2017-11-20 | 2018-04-20 | 中国运载火箭技术研究院 | A kind of generalization spacecraft Integrated Electronic System |
| CN109583002A (en) * | 2018-09-29 | 2019-04-05 | 中国航空无线电电子研究所 | Aviation electronics integral design method |
| CN110502795A (en) * | 2019-07-23 | 2019-11-26 | 中国航空无线电电子研究所 | External simulation model accesses middleware |
| CN114398747A (en) * | 2021-09-30 | 2022-04-26 | 西南电子技术研究所（中国电子科技集团公司第十研究所） | Flight training simulator communication navigation simulation loose coupling architecture |
-
2022
- 2022-07-05 CN CN202210793293.8A patent/CN115314546A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070127460A1 (en) * | 2005-12-02 | 2007-06-07 | The Boeing Company | Scalable On-Board Open Data Network Architecture |
| US20160057075A1 (en) * | 2014-08-20 | 2016-02-25 | At&T Intellectual Property I, L.P. | Load Adaptation Architecture Framework for Orchestrating and Managing Services in a Cloud Computing System |
| CN107943459A (en) * | 2017-11-20 | 2018-04-20 | 中国运载火箭技术研究院 | A kind of generalization spacecraft Integrated Electronic System |
| CN109583002A (en) * | 2018-09-29 | 2019-04-05 | 中国航空无线电电子研究所 | Aviation electronics integral design method |
| CN110502795A (en) * | 2019-07-23 | 2019-11-26 | 中国航空无线电电子研究所 | External simulation model accesses middleware |
| CN114398747A (en) * | 2021-09-30 | 2022-04-26 | 西南电子技术研究所（中国电子科技集团公司第十研究所） | Flight training simulator communication navigation simulation loose coupling architecture |
Non-Patent Citations (1)
| Title |
|---|
| 周庆等: "面向服务的先进航空电子系统架构研究", 《航空电子技术》, vol. 49, no. 4, pages 1 - 7 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US5937388A (en) | System and method for performing scalable distribution of process flow activities in a distributed workflow management system | |
| US20090158246A1 (en) | Method and system for building transactional applications using an integrated development environment | |
| CN113253710B (en) | Control software implementation architecture of block gateway electronic control unit | |
| EP1518163B1 (en) | Mobile application service container | |
| US8719780B2 (en) | Application server with a protocol-neutral programming model for developing telecommunications-based applications | |
| CN110266815B (en) | Micro service network system based on block chain | |
| US20080109828A1 (en) | Application component communication apparatus of sca-based system and method thereof | |
| CN110196731A (en) | A kind of operational system, method and storage medium | |
| CN112230987A (en) | System and method for realizing distributed modular plug-in framework | |
| US7539743B2 (en) | Method and system of administration in a JMX environment comprising an administration application and software systems to be administered | |
| US20110035477A1 (en) | Network clustering technology | |
| CN115827223A (en) | Service grid hosting method and system based on cloud native platform | |
| CN114826869A (en) | Device management method and device management system | |
| CN115314546A (en) | Dynamic self-adaptive architecture of aircraft avionics system | |
| CN115242565A (en) | System architecture, communication method and device for realizing DDS communication based on AUTOSAR | |
| CN115543661B (en) | Data distribution device and method, and architecture of vehicle electronic operation system | |
| CN116389552A (en) | Heterogeneous data transmission system based on publish-subscribe model | |
| CN115883637A (en) | Service architecture SOA-based vehicle-mounted android VHAL system and implementation method | |
| CN114936071A (en) | Civil aircraft airborne distributed simulation system based on edge calculation | |
| CN114615268A (en) | Service network, monitoring node, container node and equipment based on Kubernetes cluster | |
| Gerhards | Digital twin for fleet management of connected vehicles | |
| US20040221003A1 (en) | System and method for transmitting supporting requests in a data center with a support meta language | |
| Anke et al. | Seamless integration of distributed OSGi bundles into enterprise processes using BPEL | |
| US20020169624A1 (en) | Event publishing service system and method | |
| KR102523389B1 (en) | Information processing system and control method of information processing system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |