Time sequence data acquisition and storage method for airborne equipment

Abstract

The invention provides an airborne equipment-oriented time sequence data acquisition and storage method, which comprises the following steps of: acquiring a communication protocol and configuration parameters of airborne edge equipment and airborne field equipment as a drive, acquiring a digital mirror image of the airborne field equipment as an asset, and creating a communication model based on the drive and the asset; developing a driving program of a field protocol according to the communication model, obtaining a plurality of data points of the asset through the driving program, and independently mapping each data point into a channel; collecting time sequence data of the assets through the channel; based on the tag information of the airborne field equipment, metadata of the time series data and the hierarchical relation of the metadata are analyzed, and a time series data model of a tree structure is mapped; and integrating the time sequence data according to the time sequence data model and storing the time sequence data in a time sequence database.

Description

Technical Field

[0001] The present invention relates to the technical field of integrated circuits, and particularly to a method for collecting and storing timing data for airborne equipment. Background Art

[0002] With the development of the complexity, integration, and intelligence of airborne products, the amount of airborne data has increased sharply, bringing huge challenges to the collection and storage of airborne data.

[0003] Airborne data is generally a collection of parameters related to the working states of various airborne on-site equipment, the flight state of the aircraft, the external flight environment, etc. recorded during the operation of the aircraft, and often has time tags (changing in chronological order), that is, timing data.

[0004] Timing data, also known as time series data, refers to a set of data of the same indicator recorded in chronological order. The main sources of airborne timing data are various airborne equipment and on-site equipment. Due to problems such as a large number of airborne cross-link interfaces, the diversity of on-site protocols, and the heterogeneity of acquisition equipment, there are often many bottlenecks in the acquisition of airborne timing data. The traditional solution is to interconnect with airborne equipment through different bus interfaces to complete functions such as data acquisition and recording of airborne cross-link equipment, and it cannot well balance issues such as on-site protocol scalability and acquisition performance.

[0005] At the same time, airborne timing data usually has the characteristics of a huge amount of data and complex and diverse data formats. The traditional file storage mode is difficult to meet the current requirements for the storage and management of massive timing data. Therefore, it is necessary to design unified acquisition standards for various timing data, construct a unified storage model for timing data to improve management efficiency, and make the isolated timing data generated by various airborne equipment and on-site equipment more hierarchically and organizedly associated.

[0006] In summary, it is necessary to develop a method for collecting and storing timing data for airborne equipment to achieve the ability to centrally collect and efficiently store airborne timing data, and meet the growing management and application requirements of current airborne timing data. Summary of the Invention

[0007] In a first aspect of the present disclosure, there is provided a method for collecting and storing timing data for airborne equipment, including the following steps:

[0008] Obtain the communication protocols and configuration parameters of the airborne edge equipment and the airborne on-site equipment as drivers, and obtain the digital mirror of the airborne on-site equipment as assets, and create a communication model based on the drivers and assets;

[0009] Develop a driver for the field protocol according to the communication model, obtain multiple data points of the asset through the driver, and map each data point to a separate channel;

[0010] Collect the time-series data of the asset through the channel;

[0011] Parse the metadata and its hierarchical relationship of the time-series data based on the tag information of the airborne field device, and map it into a time-series data model in a tree structure;

[0012] Integrate the time-series data according to the time-series data model and store it in the time-series database.

[0013] Combined with the first aspect, the creating of the communication model based on the driver and the asset includes:

[0014] Obtain the communication protocols and configuration parameters of the airborne edge device and the airborne field device, where the communication protocols include network protocols, data transmission protocols, and application protocols;

[0015] Based on the communication protocols and configuration parameters, determine the data exchange method, data frame format, communication interface, and transmission rate, and create a communication model.

[0016] Combined with the first aspect, the obtaining of multiple data points of the asset through the driver includes:

[0017] Create a driver instance of the driver, configure the global parameters of the driver instance, and establish a physical connection with the airborne field device;

[0018] Obtain multiple data points of the corresponding asset through the driver instance, and map each data point to a separate channel.

[0019] Combined with the first aspect, the collecting of the time-series data of the asset through the channel includes:

[0020] Configure the channel by writing configuration parameters through the driver, where the configuration parameters include channel identifier, read / write mode, register address, byte order, data type;

[0021] Collect the time-series data of the asset by referring to the corresponding channel of the asset.

[0022] Combined with the first aspect, the parsing of the metadata and its hierarchical relationship of the time-series data based on the tag information of the airborne field device includes dividing the metadata into a structure arranged in the order of tenant layer - edge gateway layer - sensor layer - physical quantity layer according to the airborne field device tag.

[0023] In combination with the first aspect, the time series data model adopts a tree - structured time series data model, where the root node is the tenant layer, the leaf nodes are specific physical quantity layers, and the path formed by each level of data from the root node to the leaf node forms a unique time series data identifier.

[0024] In combination with the first aspect, the time series database includes the Apache IoTDB time series database, which supports data storage in a tree - like structure.

[0025] In combination with the first aspect, the time series data is encoded in JSON format.

[0026] In a second aspect of the present disclosure, there is provided an electronic device, including:

[0027] One or more processors;

[0028] A storage unit for storing one or more programs, which, when executed by the one or more processors, enable the one or more processors to implement the time series data acquisition and storage method for airborne devices.

[0029] In a third aspect of the present disclosure, there is provided a computer - readable storage medium, on which a computer program is stored, characterized in that when the computer program is executed by a processor, it can implement the time series data acquisition and storage method for airborne devices.

[0030] Advantageous effects: In the traditional solution, data acquisition and recording of airborne cross - linked devices are completed by interconnecting with airborne devices through different bus interfaces, which cannot well balance issues such as on - site protocol scalability and acquisition performance. The present invention simplifies the communication between airborne edge devices and sensors by adopting a single model based on the concepts of drivers and assets, realizes the unified access of on - site protocols, and provides a more flexible and efficient edge device acquisition mode. Aiming at the problem that the traditional file storage mode is difficult to meet the current demand for massive time series data storage management, the present invention introduces a time series database service in airborne edge devices for time series data management, replacing the original method of directly collecting, recording, and storing data on disk, so that the airborne time series data management has high storage efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 It is a schematic flow chart of a time series data acquisition and storage method for airborne devices according to an embodiment of the present disclosure;

[0032] Figure 2 It is an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0033] Exemplary embodiments will be described in detail herein, and examples thereof are shown in the accompanying drawings. When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the embodiments of the present disclosure.

[0034] The terms used in the embodiments of the present disclosure are for the purpose of describing specific embodiments only and are not intended to limit the embodiments of the present disclosure. The singular forms "a", "the", and "said" used in the embodiments of the present disclosure and the appended claims are also intended to include the plural forms unless the context clearly dictates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0035] It should be understood that although the terms first, second, third, etc. may be used in the embodiments of the present disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the embodiments of the present disclosure, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "when" or "while" or "in response to determining".

[0036] With the application of the new generation of data acquisition and transmission devices on civil aircraft, time-series data has become the main body of big data in the civil aircraft PHM field.

[0037] Time-series data, also known as time-sequence data, refers to a data set of the same metric recorded in chronological order.

[0038] As Figure 1 shown, it is a schematic flowchart of a method for acquiring and storing time-series data for airborne devices according to an embodiment of the present disclosure, including:

[0039] S101: Obtain the communication protocol and configuration parameters of the airborne edge device and the airborne field device as a driver, and obtain the digital mirror of the airborne field device as an asset, and create a communication model based on the driver and the asset.

[0040] Specifically, the role of the driver is to encapsulate the protocol and its configuration parameters required for communicating with the airborne field device. Specifically, the driver is a software module used to handle the communication details with different field devices. For example, different devices may use different communication protocols (such as Modbus, CAN, RS-485, etc.), and the driver hides the complexity by adapting these protocols so that the upper-layer logic does not need to concern itself with the underlying communication implementation.

[0041] An asset is a logical abstraction and representation of on-board field devices. It creates a high-level model for field devices, making data management and operations more scalable and readable. An asset can be regarded as the "digital twin" of a device, describing the device behavior by defining device attributes, operation methods, and events.

[0042] The creation of a communication model based on the driver and the asset includes:

[0043] Obtain the communication protocols and configuration parameters of the on-board edge device and the on-board field device. The communication protocols include network protocols, data transmission protocols, and application protocols. Specifically, first analyze how the on-board edge device and the on-board field device communicate, such as using a serial port, TCP / IP, or other methods, and extract the parameters required for connection (such as IP address, port number, baud rate, etc.).

[0044] Based on the communication protocols and configuration parameters, determine the data exchange method, data frame format, communication interface, and transmission rate, and create a communication model. Then analyze the "digital mirror" of the on-board field device (that is, what data it can provide and how the data is organized). Finally, combine the communication method with the data structure of the device to determine which data points can be read through which methods, forming a complete communication framework.

[0045] Beneficial effects: By using the driver to encapsulate the communication protocol, the system can easily adapt to on-board field devices of different manufacturers and models without modifying the upper-layer applications. By abstracting the logical representation form of the device through the asset, the physical implementation of the device is separated from the functional representation, improving the scalability of the communication model. The edge device and the field device interact through the communication model, shielding the underlying details, enabling application developers to only care about the logical operations of the asset.

[0046] In addition, during flight, the asset can be used to collect the status data of multiple on-board devices (such as flight controllers, sensors) in real time, and ensure the data compatibility of devices with different protocols through the driver module. Using the logical representation of the asset and multiple data channels, the system can perform status monitoring and anomaly analysis for different devices. For example, monitor the engine temperature and vibration frequency. Once a certain parameter exceeds the preset threshold, an alarm event can be triggered.

[0047] S102: Develop a driver program for the field protocol according to the communication model, and obtain multiple data points of the asset through the driver program, and map each data point to a separate channel.

[0048] The communication model is a high-level abstraction that provides a general driver architecture, enabling different protocol driver programs to be created and managed in a unified manner.

[0049] The Field Protocol is a specification for the communication between on-board field devices and external systems, just like a "language". Different devices may use different protocols, such as:

[0050] Modbus, CAN, EtherCAT, ARINC 429 (avionics protocol), etc.

[0051] These protocols define the data transmission methods, including how to establish connections, how to read / write data, how to monitor events, etc.

[0052] Therefore, first obtain the initial driver architecture according to the communication model, and then develop specific driver programs based on the field protocol.

[0053] Implementation steps of the driver program:

[0054] 1. Factory Pattern: First define a general initial driver architecture according to the communication model;

[0055] 2. Then implement the driver programs for different protocols (Modbus, CAN, etc.) respectively.

[0056] Implementation of the driver program API:

[0057] connect() / disconnect() methods: Used to establish or disconnect connections.

[0058] read() / write() methods: Used for data interaction.

[0059] Monitor events (such as fault alarms, etc.).

[0060] This step ensures that the application can communicate with different field devices through the API without caring about the details of the underlying protocol.

[0061] For example, for the industrial field protocol MODBUS, according to its protocol specification, the functions to be implemented in the driver program for implementing the field protocol include:

[0062] [1] Communication modes based on TCP, UDP, and serial ports;

[0063] [2] Read and write data from the Coils, Discrete Inputs, Holding Registers, and Input Registers areas;

[0064] [3] Read / write digital data across multiple consecutive registers with different sizes and byte orders;

[0065] [4] Aggregate the read / write operations of continuous data automatically in larger batch requests to reduce the IO time.

[0066] In addition, the driver can also be installed as a plugin into the runtime environment.

[0067] Such as the OSGi framework (such as Equinox OSGi), which is a modular plugin system that allows different drivers (Modbus, ARINC 429, etc.) to be loaded into the on-board edge device in a plugin manner.

[0068] The advantage of this is that different protocol drivers can be loaded and managed dynamically without affecting other drivers.

[0069] For example, install the above MODBUS driver as a component plugin into the Equinox framework deployed on the on-board edge device. Since the OSGi component system can load and unload component plugins dynamically without affecting the normal operation of other components, it is possible to achieve unified access to on-site protocols by adding, deleting, or updating driver components without changing the application programs (acquisition application programs, storage application programs).

[0070] Next, obtaining multiple data points of the asset through the driver includes:

[0071] Create a driver instance of the driver, configure the global parameters of the driver instance, and establish a physical connection with the on-board field device;

[0072] Obtain multiple corresponding data points of the asset through the driver instance, and map each data point to a separate channel.

[0073] For example, create an instance of the above MODBUS driver, configure a set of global parameters of the instance. If it is in IP mode, configure the IP address and port; in serial mode, configure the path of the serial port and port configuration (baud rate, data bits, parity check, stop bits), etc., so as to establish a physical connection with the on-board field device.

[0074] Then communicate with the asset (on-board field device) through the driver instance. An asset has multiple data points, such as temperature, humidity, etc.

[0075] Map each data point to a separate channel. For example, temperature is one channel and humidity is another channel.

[0076] An asset can manage multiple data channels simultaneously to achieve parallel acquisition and processing of data from different dimensions of the device. The data is normalized into a unified format through the asset layer for easy storage in a time-series database or further transmission to the cloud. The data channels support real-time acquisition (such as real-time sensing data during flight) and batch upload (such as summary reports after flight).

[0077] S103: Collecting the time-series data of the asset through the channel includes:

[0078] Configuring the channel by writing configuration parameters through the driver, where the configuration parameters include channel identifier, read-write mode, register address, byte order, and data type;

[0079] Referring to the corresponding channel of the asset to collect the time-series data of the asset.

[0080] Specifically, the configuration parameters of each channel mainly include channel identifier, read-write mode, register address, byte order, data type, etc.

[0081] Channel identifier: It is to give a name to the channel;

[0082] Read-write mode: Whether to perform READ, WRITE, or READ_WRITE on the data point register;

[0083] Register address: The memory address of the data point in the on-board field device, which is the addressing method for the register mapped to the unified address space;

[0084] Byte order: The byte order of the register data read is MSW, LSW, MSB, or LSB;

[0085] Data type: It indicates what type of data is stored in the register, and then what type the upper-layer application is, and the conversion method is determined based on the configuration.

[0086] Then refer to the corresponding channel of the asset to collect the time-series data of the asset.

[0087] S104: Analyzing the metadata and its hierarchical relationship of the time-series data based on the tag information of the on-board field device includes:

[0088] Parsing the metadata of each time-series data from the tags of the on-board field device, including device identifier, data type, sampling period, and unit information, and dividing it into a structure arranged in the order of tenant layer - edge gateway layer - sensor layer - physical quantity layer.

[0089] Then it is mapped into a time-series data model in a tree structure. The time-series data model adopts a tree-structured time-series data model. The root node is the tenant layer, and the leaf nodes are the specific physical quantity layers. The path formed by each level of data from the root node to the leaf node forms a unique time-series data identifier. A time series is named by the path from the root node to the leaf node, and the levels are connected by ".". For example, a time series name can be expressed as root.t01.e01.d01.temp.

[0090] S105: Integrate the time-series data according to the time-series data model and store it in a time-series database.

[0091] Specifically, the airborne edge device selects the Apache IoTDB time-series database, which can support the efficient and stable writing of multi-frequency and massive time-series data, support the tree structure, and a single node can manage tens of millions of time series. The underlying TsFile with a low Schema structure can achieve the plug-and-play effect at the edge side.

[0092] Architecture Schema: Refers to the structure definition of the database, including tables, fields, data types, indexes, relationships, etc., and determines the organization method of data.

[0093] Data storage is organized according to a hierarchical relationship, storing data nodes in a tree structure, and supporting fast positioning, retrieval, and management through parent-child relationships.

[0094] For example, in a time-series database, any prefix path can be set as a database. If there are 4 time series root.t01.e01.d01.temp, root.t01.e01.d01.humidity, root.t01.e02.d02.temp, root.t01.e02.d02.humidity, the two edge device entities e01 and e02 under the path root.t01 may belong to the same aircraft. At this time, the prefix path root.t0 can be specified as a database. If new entities are added under root.t01 in the future, they will also belong to this database.

[0095] The time-series data is encoded in JSON format.

[0096] The electronic device 200 can be a desktop computer, a notebook, a handheld computer, a cloud server and other electronic devices. The electronic device 200 may include, but is not limited to, a processor 201 and a memory 202. Those skilled in the art can understand, Figure 2This is only an example of the electronic device 200, which does not constitute a limitation on the electronic device 200. It may include more or fewer components than those shown in the figure, or combine certain components, or different components. For example, the electronic device may also include input / output devices, network access devices, buses, etc.

[0097] The processor 201 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor, or the processor may also be any conventional processor, etc.

[0098] The memory 202 may be an internal storage unit of the electronic device 200. For example, the hard disk or memory of the electronic device 300. The memory 202 may also be an external storage device of the electronic device 200. For example, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device 200. Further, the memory 202 may also include both the internal storage unit and the external storage device of the electronic device 200. The memory 202 is used to store the computer program 203 and other programs and data required by the electronic device. The memory 202 may also be used to temporarily store the data that has been output or will be output.

[0099] In the embodiments provided by the present disclosure, it should be understood that the disclosed device / electronic device and method may be implemented in other ways. For example, the device / electronic device embodiments described above are only illustrative. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods. Multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point, the displayed or discussed coupling or direct coupling or communication connection between each other may be through some interfaces. The indirect coupling or communication connection of the device or unit may be in an electrical, mechanical or other form.

[0100] When the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such understanding, to implement all or part of the processes in the above-described embodiment methods of the present disclosure, it can also be completed by instructing relevant hardware through a computer program. The computer program can be stored in the computer-readable storage medium. When the computer program is executed by a processor, the steps of the above-described various method embodiments can be implemented. The computer program can include computer program code, and the computer program code can be in the form of source code, object code, executable file, or some intermediate form, etc. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disc, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, and software distribution medium, etc. It should be noted that the content included in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not include electrical carrier signals and telecommunication signals.

[0101] The above embodiments are only used to illustrate the technical solutions of the present disclosure, rather than to limit them; although the present disclosure has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements for some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the various embodiments of the present disclosure, and should all be included in the protection scope of the present disclosure.

Claims

1. A method for collecting and storing time series data for airborne equipment, characterized in that: The following steps are involved: Acquire the communication protocol and configuration parameters of the onboard edge device and the onboard field device as a driver, acquire the digital image of the onboard field device as an asset, and create a communication model based on the driver and the asset; Developing a driver of the field protocol according to the communication model, obtaining multiple data points of the asset through the driver, and mapping each data point individually into a channel; Collecting time series data of the asset through the channel; Parsing metadata of the time series data and its hierarchical relationship based on the tag information of the onboard field device, and mapping it into a time series data model with a tree structure; The time series data is integrated according to the time series data model and stored in a time series database.

2. The method according to claim 1, characterized in that The creating a communication model based on the driver and the asset includes: Acquire the communication protocol and configuration parameters of the airborne edge device and the airborne field device, wherein the communication protocol includes a network protocol, a data transmission protocol and an application protocol; Based on the communication protocol and configuration parameters, the data exchange method, data frame format, communication interface and transmission rate are determined to create a communication model.

3. The method according to claim 1, characterized in that The acquiring of a plurality of data points of the asset through the driver comprises: Creating a driver instance of the driver, configuring global parameters of the driver instance, and establishing a physical connection with the onboard field device; A plurality of data points of the corresponding asset are obtained through the driver instance, and each data point is individually mapped into a channel.

4. The method according to claim 3, characterized in that The collecting of the time series data of the asset through the channel includes: Write configuration parameters through the driver to configure the channel, the configuration parameters include channel identification, read / write mode, register address, byte order, data type; The corresponding channel of the asset is referenced to collect the time series data of the asset.

5. The method according to claim 1, characterized in that The step of parsing the metadata of the time series data and its hierarchical relationship based on the tag information of the onboard field device includes dividing the metadata into a structure arranged in the order of tenant layer-edge gateway layer-sensor layer-physical quantity layer according to the onboard field device tag.

6. The method according to claim 5, characterized in that The time series data model adopts a tree structure time series data model, the root node is the tenant layer, the leaf node is the specific physical quantity layer, and each level of data in the path from the root node to the leaf node forms a unique time series data identifier.

7. The method according to claim 1, characterized in that The time series database includes an Apache IoTDB time series database, which supports tree-structured data storage.

8. The method according to claim 1, characterized in that The time series data is encoded in JSON format.

9. An electronic device, characterized in that: include: one or more processors; A storage unit, used to store one or more programs, which, when executed by the one or more processors, enable the one or more processors to implement the timing data collection and storage method for airborne devices according to any one of claims 1 to 8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, it can implement the time series data collection and storage method for airborne devices according to any one of claims 1 to 8.

Images