CN114356688A - Universal data management software architecture - Google Patents

Abstract

The application provides a generic data management software architecture, the architecture comprising: the data management software running platform is used for providing services; the data management software runs on the data management software running platform and is used for managing data; the method and the system realize the building block design of four links of data acquisition, coding, transmission and storage, provide a key basic technology for the research and development of comprehensive data management software, and improve the reliability and the universality of the data management software.

Description

Universal data management software architecture

Technical Field

The application belongs to the technical field of data management software architecture, and particularly relates to a general data management software architecture.

Background

In an aeronautic and electrical system, an integrated data management system plays an important role and plays an important role in the aspects of flight task execution and effect evaluation after the task is completed. The integrated data management software is used as main control software of the integrated data management system, is mainly responsible for the functions of task data loading, service data recording, service command processing and the like, and is an airborne rear-end data processing center. As the kinds and quantity of airborne task data and business data increase, the integration level and complexity of integrated data management software also increase, which brings about the following problems:

firstly, the comprehensive data management equipment on the airplane and each sub-equipment have various physical interfaces in a cross-linking relation, the data characteristics transmitted on the physical interfaces are different, and how to design an Application Programming Interface (API) Interface with unified standards not only ensures the real-time performance of data acquisition, but also realizes Interface isolation;

secondly, users and subsystem equipment manufacturers pay attention to the recorded data, and how to design software ensures the reliability of the recorded data and whether fault monitoring is complete;

and thirdly, the devices installed on different airplanes are different, the data required to be processed by the devices are different greatly, so that the software universality is improved, and the repeated development is avoided.

Disclosure of Invention

In order to solve the above technical problem, the present application provides a generic data management software architecture, where the architecture includes:

the data management software running platform is used for providing services;

and the data management software runs on the data management software running platform and is used for managing data.

Preferably, the data management software operating platform comprises:

the domain service layer is used for providing a data management software framework; wherein, the data management software framework is an iSEE platform-based data management software framework;

the general service layer is used for extracting the commonality of specific software and performing componentization packaging on the data management field application by a reusable design method to obtain a target component;

and the basic service layer is used for realizing the isolation of the application software from the bottom hardware and the attributes of the operating system and meeting the cross-platform use of the application software.

Preferably, the specific software includes:

CPM main processing software used for data analysis and data forwarding;

IOM interface software for receiving, processing and transmitting data.

Preferably, the specific software further comprises:

VCM interface software for audio and video compression and transmission;

DLR records loading software for recording data and loading data.

Preferably, the target assembly comprises:

the general log service component is used for providing a log management function for the target machine; the log management function comprises recording, storing and reading log data;

and the universal loading service component is used for providing data loading service for the data management software.

Preferably, the general log service component is further configured to provide a log analysis tool for the host, and display the log in a graphical manner;

wherein the log analysis tool is configured to analyze the log data.

Preferably, the base service layer includes:

an operating system adaptation service for adapting to different operating systems;

the transmission protocol system is used for providing a plurality of data transmission modes;

a reliable file system for providing reliable data storage services;

and the dynamic memory queue is used for providing a buffer service of data.

Preferably, different interfaces of the architecture are packaged into IO interfaces of a unified standard.

The application has the following technical effects:

the method and the system realize the building block design of four links of data acquisition, coding, transmission and storage, provide a key basic technology for the research and development of comprehensive data management software, and improve the reliability and the universality of the data management software.

Drawings

FIG. 1 is a diagram of several pipe software architectures provided by embodiments of the present application;

FIG. 2 is a diagram of a platform-based generic data management software framework provided by an embodiment of the present application;

FIG. 3 is a diagram of a unified data model provided by an embodiment of the present application;

FIG. 4 is a block diagram of a conventional data transmission model provided by an embodiment of the present application;

fig. 5 is a UTP data transmission model provided in an embodiment of the present application;

fig. 6 is an internal block diagram of a logging component provided in an embodiment of the present application.

Detailed Description

Referring now to FIGS. 1-6, the present application will be described in further detail. The application provides a design method of a general data management software architecture, which can realize reliable and general data management capability under a heterogeneous integrated data management system under an embedded platform.

In the embodiment of the application, the application provides a method for designing a general data management software architecture, which mainly researches contents such as a longitudinal layered architecture of data management software, a platform-based general data management software framework, a unified data transmission model, a general data management software fault category and monitoring, changes process-oriented design into object-oriented design by integrating reusable software design technologies such as data acquisition, processing, storage and loading of data management equipment, improves reusability of software, and improves reliability and transportability of the data management software by researching reliable transmission and storage technologies.

According to the design method of the universal data management software architecture, a number management software architecture and a universal number management software frame which are longitudinally layered and transversely divided into objects are designed, a unified data transmission model and a universal data management software fault category and monitoring method are designed, an application software construction mode of the frame and an object template is realized, the isolation requirements of different bus data acquisition and processing are realized, and a unified processing interface is provided; the unified receiving and sending management and centralized monitoring of the recorded and stored data are realized; the building block design of four links of data acquisition, coding, transmission and storage is realized, a key basic technology is provided for the research and development of comprehensive data management software, and the reliability and the universality of the data management software are improved.

In a possible implementation manner, the method for designing a generic data management software architecture of the present application includes: the system comprises a data management software longitudinal layered architecture, a platform-based general data management software framework, a unified data transmission model, general data management software fault types and a monitoring method.

1. Longitudinal layered architecture of data management software

According to the application requirements of data management software, the universal data management software architecture needs to have the characteristics of openness and interoperability. Based on the idea of open type sectional architecture, software is designed in a layered and componentized mode, and an open type cross-platform software architecture of 'platform + application' is adopted, as shown in fig. 1.

The general data management software architecture is divided into a digital management software operating platform and data management application software. The digital management software operation platform is divided into a field service layer, a general service layer and a basic service layer. The domain service layer comprises two functions, namely, providing convenience and means for rapid integration of data management software, and providing a data management software framework aiming at the characteristics of the data management software to help developers to rapidly construct application software; the general service layer focuses on the data management field, extracts the commonality of specific application software by combining abstract application functions with the design idea of product line architecture, performs componentization packaging on the application in the data management field by a reusable design method, and calls the application by a data management software framework, wherein the general service layer comprises modules such as general log service and general loading service; the basic service layer is divided into an operating system adaptation component, a data transmission service component, a reliable file system and the like, so that the isolation of application software from bottom hardware and the attribute of the operating system is realized, and the cross-platform use of the application software is met.

2. Platform-based universal digital tube software framework

The software framework is the core of the software product line, and the software framework is the code implementation of the software framework. A reusable field framework design is provided for software products in the airborne digital management field based on a platform digital management software framework, and the framework is mainly designed from three dimensions.

a) Designing dimensions, and changing from process-oriented development to object-oriented development;

b) data dimension, which is converted from module thinking into data thinking;

c) communication dimension, I/O (Input/Output) driving interface standardization, and communication mode of unified software.

In the design dimension, the platform-based digital management software framework is divided into four layers, namely a service layer, an equipment layer, a transmission layer and an IO layer, each layer has a unique object, and a software block diagram is shown in FIG. 2:

and (3) a service layer: the layer mainly comprises five object modules, namely a main object module, a counting management service module, a counting management self-checking module, a log service module and a time service module. The main object module provides framework initialization service, thread scheduling service and version management service for a user; the counting management service module provides general counting management command and data service for users, including services of size end conversion, time correction, event processing, data encryption and the like; the digital management self-checking module provides universal digital management software self-checking services for users, including CPU self-checking, memory self-checking, NVRAM self-checking, memory card self-checking, digital management object self-checking services and the like; the log service module provides a log recording service interface for a user, and can provide log serial port printing, log NVRAM recording, log memory card recording and corresponding switch control services; the time service module provides time acquisition, correction and acquisition services for the user.

Equipment layer: the layer mainly aims at constructing an entity object for the cross-linking equipment, provides an entity object template, comprises input, processing, control, self-checking, output, ICD registration, ICD analysis and the like, and provides common services such as video acquisition, data storage, data loading and the like.

A transmission layer: the layer provides a plurality of data transmission modes for the comprehensive digital tube framework, including message queue, UTP transmission, ring buffer, SCP reliable transmission and the like. The system mainly comprises four objects, namely an IOM object, a VCM object, an internal object and a virtual object, wherein the four objects are in charge of related data transmission switches like a route, and can monitor the data volume of different service data and the data acquisition and loss conditions. Meanwhile, the transmission layer is also a transmission channel for data recording and data loading, and a zero copy mode and a pipeline design method are adopted in design.

IO layer: the layer provides IO registration service, bus handle encapsulation service, watchdog monitoring service and the like for the comprehensive digital management framework. Because data come from different physical channels, each physical channel BSP provides different drivers, software needs to call different driver interfaces API to realize the receiving of the data on the physical channels and the sending of the data, and the software universality is lost.

3. Building unified data model

In order to shield the influence of different physical channels on software, a software framework encapsulates all IO operations into an input/output class, transmits the input/output class to a kernel through UTP, distributes IO data to different processing modules for UTP routing configuration, and performs command and data conversion and processing, and a structural block diagram of the software framework is shown in fig. 3.

IO object data model: and encapsulating the bus handle to realize bus initialization, sending and receiving functions. The handle is registered, a completely consistent interface is provided for an upper layer, when the service logic calls an IO interface, a corresponding driving entity is selected during operation based on interface programming, decoupling of the interface related to hardware is realized, and the influence of IO fault on upper layer software is isolated;

device object data model: and packaging the equipment handle, realizing the functions of equipment initialization, processing, control, receiving and sending, and registering the external ICD. Each device handle may be constructed like an IO interface, providing data transceiving functionality.

UTP data transmission model: in the past, data acquisition and storage require a processor to participate in a copying process, and the memory copying operation completely occupies the computing capacity of the processor, so that the processor cannot process other transactions in the period, and accordingly the data throughput rate of the whole software is reduced. The platform-based data acquisition, transmission and storage of the multi-tube software framework by using the UTP are carried out, and the UTP route controls the data receiving and sending after the equipment object or the IO object is registered in the UTP route. The UTP shortens the path from data acquisition to final storage to the electronic disk, and improves the transmission efficiency of data.

4. Universal data management software fault category and monitoring method

And realizing log printing and record grading monitoring of the digital management software by monitoring each node of the digital management software data transmission.

The general log service component mainly provides log management functions for the target machine, including recording, storing, reading and analyzing log data, provides a log analysis tool for the host machine, and displays logs in a graphical mode. The component is developed and compiled aiming at an embedded operating system and a Windows operating system respectively to form a log recording component and a log analysis tool.

The logging component is a logging library based on C language, and provides stable and flexible logging function for application software. Using this component, log or trace debug information can be conveniently written into character streams, files, rollback files, local syslog, and remote syslog servers.

There are three important concepts of logging components, Category, appendix, Layout, and Priority. Category is used to distinguish different recorders. The appendix is used for describing the output stream, and by specifying an appendix for Category, it can decide where to output the log information, such as stdout, stderr, file or socket, etc. Layout format of the log information is specified by Layout, and by specifying a Layout for the appendix, it can be decided in which format the log information is output, such as whether to have a time stamp, whether to include file location information, and the like, and the output format in a piece of log information, and the like, and there are generally base and date. Priority is used to specify the Priority of Category.

The principle of logging by this component is as follows: each Category has a priority that can be set by a configuration file or relayed from its parent Category. Each log also has a priority, when the Category records the log, if the priority of the log is higher than that of the Category, the log is recorded, otherwise, the log is ignored.

FIG. 6 is an internal block diagram of a journaling component, which has three recorders Category, and when the recorders are used for journaling, the output end appendix of the recorders is used for writing the journals into files or NVRAMs according to the Layout format.

Claims (8)

1. A generic data management software architecture, the architecture comprising:

the data management software running platform is used for providing services;

and the data management software runs on the data management software running platform and is used for managing data.

2. The generic data management software architecture of claim 1, wherein the data management software runtime platform comprises:

the domain service layer is used for providing a data management software framework; wherein, the data management software framework is an iSEE platform-based data management software framework;

the general service layer is used for extracting the commonality of specific software and performing componentization packaging on the data management field application by a reusable design method to obtain a target component;

and the basic service layer is used for realizing the isolation of the application software from the bottom hardware and the attributes of the operating system and meeting the cross-platform use of the application software.

3. The generic data management software architecture according to claim 2, wherein the specific software comprises:

CPM main processing software used for data analysis and data forwarding;

IOM interface software for receiving, processing and transmitting data.

4. The generic data management software architecture according to claim 3, wherein the specific software further comprises:

VCM interface software for audio and video compression and transmission;

DLR records loading software for recording data and loading data.

5. The generic data management software architecture according to claim 2, wherein the target component comprises:

the general log service component is used for providing a log management function for the target machine; the log management function comprises recording, storing and reading log data;

and the universal loading service component is used for providing data loading service for the data management software.

6. The generic data management software architecture of claim 5, wherein the generic log services component is further configured to provide a log analysis tool for the host and display the log graphically;

wherein the log analysis tool is configured to analyze the log data.

7. The generic data management software architecture according to claim 2, wherein the base services layer comprises:

an operating system adaptation service for adapting to different operating systems;

the transmission protocol system is used for providing a plurality of data transmission modes;

a reliable file system for providing reliable data storage services;

and the dynamic memory queue is used for providing a buffer service of data.

8. The generic data management software architecture according to claim 1, characterized in that the different interfaces of the architecture are encapsulated into a unified IO interface.

Images