WO2022261810A1 - 数据获取系统的构建方法及装置 - Google Patents

数据获取系统的构建方法及装置 Download PDF

Info

Publication number
WO2022261810A1
WO2022261810A1 PCT/CN2021/099995 CN2021099995W WO2022261810A1 WO 2022261810 A1 WO2022261810 A1 WO 2022261810A1 CN 2021099995 W CN2021099995 W CN 2021099995W WO 2022261810 A1 WO2022261810 A1 WO 2022261810A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
node
module
processing
information
Prior art date
Application number
PCT/CN2021/099995
Other languages
English (en)
French (fr)
Inventor
杨俊峰
王天星
余宏伟
汪洪潮
孙正阳
刘若琳
张雷
宋克柱
Original Assignee
中国科学技术大学
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中国科学技术大学 filed Critical 中国科学技术大学
Priority to PCT/CN2021/099995 priority Critical patent/WO2022261810A1/zh
Publication of WO2022261810A1 publication Critical patent/WO2022261810A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2455—Query execution
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems

Definitions

  • the present invention relates to the technical field of data acquisition, in particular to a method and device for constructing a data acquisition system.
  • streaming data is a set of sequential, large, and fast-arriving data sequences.
  • a data stream can be regarded as a network that grows infinitely over time.
  • a collection of dynamic data In different application fields and different application scenarios, there are huge differences in the acquisition methods and systems of streaming data.
  • the present invention provides a method and device for constructing a data acquisition system.
  • the present invention by using standard stream processing nodes to construct a data acquisition system, the difficulty of constructing a data acquisition system is reduced, and the present invention can be applied to multiple A scenario for building a data acquisition system is more universal and convenient.
  • the present invention provides the following technical solutions:
  • a method for constructing a data acquisition system comprising:
  • module information and module interconnection information of each of the collection and processing modules various workflows included in the data acquisition system are abstracted;
  • the interface application information includes the information provided by each collection and processing module that the workflow passes through for the workflow.
  • interface information of the interface based on the data space information of the workflow, the interface application information, and the data processing mode information, determine each data domain included in the processing path of the workflow, wherein the data domain is The workflow has a data area with the same flow data frame granularity during processing, and the level of the data field increases with the increase of the flow data frame granularity;
  • each acquisition and processing module that the workflow passes through is determined as a target module, and the data domain information of the workflow is determined, and the data domain information contains information related to the work Attribute information of the data domain where each stream processing node corresponding to the stream is located; interface application information based on the workflow, data processing mode information, data domain information, and module information and module interconnection information of each target module , determining a target module corresponding to each stream processing node corresponding to the workflow, and determining position information of each stream processing node in the corresponding target module;
  • each of the collection and processing modules determine each stream processing node corresponding to the collection and processing module, and generate module construction information of the collection and processing module based on the location information of each stream processing node;
  • each of the collection and processing modules determine the cross-module interface node of the collection and processing module, based on the cross-module interface node, determine the collection and processing module that has a connection relationship with the collection and processing module, and connect the collection and processing module Connect with the collection and processing modules that have a connection relationship with it;
  • each collection processing module For each collection processing module, according to the module construction information of the collection processing module, determine the node information of each stream processing node corresponding to the collection processing module, based on the node information of each stream processing node, Connect each stream processing node of the acquisition processing module with a cross-module interface node using a standardized packaged standard interface to obtain a module design file corresponding to the acquisition processing module, and deploy the module design file to the acquisition In the processing module, the construction of the data acquisition system corresponding to the construction request is completed.
  • the determining the cross-module interface node of the acquisition processing module includes:
  • cross-module interface node If there is no standard cross-module interface node corresponding to the cross-module interface type, construct the cross-module interface node of the collection and processing module based on the physical layer transmission medium and interface information of the collection and processing module.
  • the determining each stream processing node corresponding to the acquisition processing module includes:
  • the process of standardized encapsulation of standard interfaces includes:
  • For each data interface in the collection and processing module determine the processing unit type of the collection and processing module where each data interface is located;
  • each of the data interfaces is standardized and encapsulated to obtain a standard interface corresponding to each data interface.
  • a standardized encapsulated standard interface to connect each stream processing node of the acquisition processing module with a cross-module interface node, including:
  • For each of the stream processing nodes based on the connection information of the stream processing node, determine the target port of the target connection node corresponding to each port of the stream processing node, and the target connection node is connected to the stream processing node a stream processing node with a node connection relationship, and the target port is a port connected to the stream processing node in the target connection node;
  • connection mode of the port is determined based on the node type of the stream processing node where the port is located, and the target connection node corresponding to the port is determined to be connected to the port. Whether the stream processing nodes at the location are all in the same collection and processing module;
  • the target connection node corresponding to the port is not in the same collection and processing module as the stream processing node where the port is located, then determine the standard port corresponding to the port in the standard conversion module, and combine the port and the The interfaces between the standard ports corresponding to the ports are standardized and encapsulated, and after the working parameters of the standard conversion module are determined based on the data domain attributes of the ports, the standard conversion module is used to connect the ports with the Inter-module interface node connection, so that the port is connected to the target port corresponding to the port through the inter-module interface node;
  • the target connection node corresponding to the port is in the same collection and processing module as the stream processing node where the port is located, standardize the interface between the port and the target port corresponding to the port, so as to A standard interface is obtained, and the connection mode of the port is applied through the standard interface, so that the port is connected to the target port corresponding to the port.
  • a construction device for a data acquisition system comprising:
  • the response unit is configured to determine the module information and module interconnection information of each collection and processing module contained in the data acquisition system to be constructed in response to the construction request sent by the user for construction of the data acquisition system;
  • An abstraction unit configured to abstract various workflows contained in the data acquisition system according to the module information and module interconnection information of each of the collection and processing modules;
  • a first determining unit configured to determine the data space information of the data transmitted in each of the workflows based on the number of channels and the length of working time of each of the workflows;
  • the second determining unit is configured to, for each of the workflows, determine the data processing mode information and interface application information of the workflow, the interface application information includes each collection and processing module that the workflow passes through Interface information of the interface provided for the workflow; based on the data space information of the workflow, the interface application information and the data processing mode information, determine each data field included in the processing path of the workflow, wherein, the data domain is a data area having the same stream data frame granularity during workflow processing, and the level of the data domain increases as the stream data frame granularity increases;
  • the third determining unit is configured to, for each of the workflows, determine each collection and processing module that the workflow passes through as a target module, and determine the data domain information of the workflow, the data domain
  • the information includes attribute information of the data domain where each stream processing node corresponding to the workflow is located; interface application information, data processing mode information, data domain information and each target module based on the workflow Module information and module interconnection information, determining the target module corresponding to each stream processing node corresponding to the workflow, and determining the position information of each stream processing node in the corresponding target module;
  • a generating unit configured to, for each of the collection and processing modules, determine each stream processing node corresponding to the collection and processing module, and generate module construction information of the collection and processing module based on the location information of each stream processing node;
  • the fourth determining unit is configured to, for each of the collection and processing modules, determine a cross-module interface node of the collection and processing module, and determine a collection and processing module that has a connection relationship with the collection and processing module based on the cross-module interface node, and connecting the collection and processing module with the collection and processing module with which it has a connection relationship;
  • the connection unit is configured to, for each of the acquisition processing modules, determine the node information of each stream processing node corresponding to the acquisition processing module according to the module construction information of the acquisition processing module, and based on each of the stream processing For the node information of the node, use the standard interface after standardized encapsulation to connect each stream processing node of the acquisition and processing module with the cross-module interface node to obtain the module design file corresponding to the acquisition and processing module, and convert the module design file to Deployed to the acquisition processing module to complete the construction of the data acquisition system corresponding to the construction request.
  • the fourth determination unit includes:
  • a first determining subunit configured to determine the cross-module interface type of the acquisition processing module
  • the first judging subunit is used to judge whether there is a standard cross-module interface node corresponding to the cross-module interface type in the preset standard cross-module interface node library;
  • the second determining subunit is configured to use the standard cross-module interface node corresponding to the cross-module interface type as the cross-module of the acquisition processing module if there is a standard cross-module interface node corresponding to the cross-module interface type interface node;
  • the generating unit includes:
  • An acquisition subunit configured to acquire information about each node type of the acquisition processing module
  • the second judging subunit is configured to, for each of the node type information, determine whether there is a standard processing node corresponding to the node type information in the standard node library corresponding to the processing unit type of the acquisition processing module;
  • the third determining subunit is configured to use the standard processing node corresponding to the node type information as the stream processing node corresponding to the collection processing module if there is a standard processing node corresponding to the node type information;
  • the second construction subunit is configured to construct a stream processing node corresponding to the node type information based on the node information corresponding to the node type information if there is no standard processing node corresponding to the node type information, and The constructed stream processing node is used as the stream processing node corresponding to the acquisition processing module.
  • the above-mentioned device optionally, also includes:
  • the fifth determining unit is configured to, for each data interface in the collection and processing module, determine the processing unit type of the collection and processing module where each data interface is located;
  • the sixth determination unit is configured to determine the data domain attribute of each of the data interfaces, and determine the flow data frame parameters and flow data frame information segment content of each of the data interfaces based on the data domain attributes of each of the data interfaces ;
  • the input unit is configured to, for each of the data interfaces, apply the stream data frame parameters and stream data frame information segment content of the data interface to a preset standard stream data frame format module to obtain the standard stream of the data interface data frame format;
  • the acquisition unit is configured to standardize and encapsulate each of the data interfaces based on the standard data interface type, working parameters, and standard stream data frame format of each of the data interfaces to obtain a standard interface corresponding to each of the data interfaces.
  • connection unit includes:
  • a parsing subunit configured to parse the node information of each of the stream processing nodes to obtain the node type and connection information of each of the stream processing nodes;
  • the fourth determining subunit is configured to, for each of the stream processing nodes, determine a target port of a target connection node corresponding to each port of the stream processing node based on the connection information of the stream processing node, the target
  • the connection node is a stream processing node that has a connection relationship with the stream processing node, and the target port is a port connected to the stream processing node in the target connection node;
  • the third judging subunit is configured to, for each port in each of the stream processing nodes, determine the connection mode of the port based on the node type of the stream processing node where the port is located, and determine the port corresponding to the Whether the target connection node and the stream processing node where the port is located are both in the same collection and processing module;
  • the first connection subunit is configured to determine the standard corresponding to the port in the standard conversion module if the target connection node corresponding to the port is not in the same collection and processing module as the stream processing node where the port is located port, standardize and encapsulate the interface between the port and the standard port corresponding to the port, and use the standard conversion module to apply the port after determining the working parameters of the standard conversion module based on the data domain attributes of the port
  • the port is connected to the cross-module interface node in a connection manner, so that the port is connected to the target port corresponding to the port through the cross-module interface node;
  • the second connection subunit is configured to, if the target connection node corresponding to the port and the stream processing node where the port is located are in the same collection and processing module, then perform a connection between the port and the target port corresponding to the port Standardized encapsulation is performed on the interfaces between them to obtain a standard interface, and the connection mode of the port is applied through the standard interface, so that the port is connected to the target port corresponding to the port.
  • the present invention has the following advantages:
  • the present invention provides a method and device for constructing a data acquisition system, the method comprising: in response to a construction request sent by a user for constructing a data acquisition system, determining the module information and module interaction of the acquisition processing module corresponding to the construction request Connect information, abstract the various workflows contained in the data acquisition system, determine the data space information of the data transmitted in each workflow, determine the various data domains that the workflow passes through in the processing path, and finally determine the Module build information for processing modules. Acquisition and processing modules whose interconnection relationship is determined through cross-module interface nodes. For each collection and processing module, each stream processing node is connected or connected to a cross-module interface node using a standardized packaged standard interface, so as to obtain a module design file with the collection and processing module.
  • the stream processing nodes and connection methods in the design files of each module are deployed to the acquisition and processing modules where they are located, and the construction of the entire data acquisition system is completed.
  • the method provided by the present invention should be used to abstract the workflow of the data acquisition system into a series of stream processing, abstract the stream processing process into a series of stream processing node connections, and use data space and data domain attributes to describe each stream processing node working parameters, so that the stream processing nodes used to construct the data acquisition system can be determined, and the required data acquisition system can be quickly constructed using the stream processing nodes.
  • the stream processing nodes in the constructed data acquisition system are reusable, and can be used in When the system is adjusted or modified, there is no need to redesign, which saves a lot of time, and the construction method of the data system provided by the present invention is simple, uncomplicated and universal. Use the method provided by the invention to construct the required data acquisition system.
  • Fig. 1 is a method flowchart of a construction method of a data acquisition system provided by an embodiment of the present invention
  • Fig. 2 is another method flowchart of a construction method of a data acquisition system provided by an embodiment of the present invention
  • Fig. 3 is another method flowchart of the construction method of a kind of data acquisition system provided by the embodiment of the present invention.
  • Fig. 4 is another method flowchart of a construction method of a data acquisition system provided by an embodiment of the present invention.
  • FIG. 5 is an example diagram of the definition of a stream data frame format of a stream data frame provided by an embodiment of the present invention
  • FIG. 6 is a model schematic diagram of a multi-channel point-to-point interface model provided by an embodiment of the present invention.
  • FIG. 7 is an internal implementation block diagram of a multi-channel point-to-point interface model provided by an embodiment of the present invention.
  • Fig. 8 is yet another method flowchart of a construction method of a data acquisition system provided by an embodiment of the present invention.
  • FIG. 9 is an example diagram of a data format of an index shared memory provided by an embodiment of the present invention.
  • FIG. 10 is an example diagram of the relationship between a data space and a data domain of a stream provided by an embodiment of the present invention.
  • Fig. 11 is an implementation block diagram of a collection unit for constructing a data acquisition system provided by an embodiment of the present invention.
  • FIG. 12 is a schematic diagram of a model of a sensor readout node provided by an embodiment of the present invention.
  • Fig. 13 is an implementation block diagram of a data summarization unit for building a data acquisition system provided by an embodiment of the present invention
  • FIG. 14 is a block diagram of a data display and recording unit for building a data acquisition system provided by an embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram of a construction device for a data acquisition system provided by an embodiment of the present invention.
  • the term “comprising”, “comprising” or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, but also includes none. other elements specifically listed, or also include elements inherent in such a process, method, article, or apparatus.
  • an element defined by the phrase “comprising a " does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.
  • the present invention can be used to build platforms or systems of various data acquisition systems.
  • the present invention can be used to build data acquisition systems.
  • the data acquisition system constructed by applying the present invention has high reusability and reduces the cost of building data acquisition systems. Design effort to speed up data acquisition system implementation.
  • the subject of execution of the method provided by the present invention may be a server or a processor in a platform for constructing a data acquisition system, wherein the processor includes a Field Programmable Gate Array (Field Programmable GateArray, FPGA); one provided by the present invention
  • FPGA Field Programmable GateArray
  • the user When the user needs to build a data acquisition system, he sends a construction request for building a data acquisition system to the execution subject, and the execution subject responds to the construction request sent by the user for building a data acquisition system, analyzes the construction request, and determines the required Module information and module interconnection information of each acquisition and processing module included in the constructed data acquisition system.
  • the acquisition processing module described in the present invention refers to the hardware module that actually works in the data acquisition system, including but not limited to the hardware board for sensor data readout, the FPGA board for completing the data real-time processing function or Other hardware boards or computers containing single-chip microcomputers, CPUs or GPUs, etc.
  • Each acquisition and processing module in the present invention is respectively subordinate to a certain module structure layer according to function, position and connection relationship, and all acquisition and processing modules are organized in a hierarchical manner, and the acquisition and processing of the same type with the same function and connection mode Modules are placed on the same module structure level.
  • a data acquisition system contains at least one module structure layer, and each module interface layer contains at least one acquisition and processing module; further, when there are multiple module structure layers in the data acquisition system, each module structure layer is divided according to the distance sensor/ The near and far positions of the detectors increase layer by layer in order from near to far.
  • Each module structure layer only has direct data channels between its internal collection and processing modules, or between its internal collection and processing modules and its adjacent upper and lower level collection and processing modules, that is, between adjacent module structure layers There is a direct data channel, such as optical fiber, twisted pair, coaxial cable, wireless signal, etc.; there is no direct data channel between non-adjacent module structure layers.
  • the module interconnection information of the acquisition processing module in the present invention refers to the upper-lower relationship and the adjacent relationship of the module structure layer where the acquisition processing module is located, as well as the module structure layer where the acquisition processing module is located and the module structure layer Information such as the interconnection mode, number of connections, and transmission capabilities between each acquisition and processing module in the module structure layer of other levels.
  • the module information of the collection and processing module in the present invention includes but not limited to the module type of the collection and processing module, interface information, the number of connected sensor channels and module processing capabilities, etc., wherein the interface information includes but is not limited to the number of input interfaces and the number of output interfaces , the interface type and data transmission capability of the input interface and output interface.
  • workflows include but are not limited to data flow, command flow, log flow, status flow, and command feedback flow.
  • the streams in the present invention have the same data transmission direction and the same processing method.
  • a series of data channels with the same data content and data structure frame the data within a certain channel range and time range according to a certain organization method, and send data frames in chronological order.
  • the workflow of the entire data acquisition system is abstracted into a corresponding independent workflow.
  • the data of sensors/detectors and their corresponding processing methods are abstracted as data streams and the cascade of various stream processing nodes on the data streams, and operations such as parameter configuration and work control of sensors/detectors are abstracted into command streams and their processing nodes Abstract the return result of the read command as a command feedback flow, abstract the output of temperature and voltage sensors on various acquisition and processing modules as a state flow, and abstract various work messages in the system into an emergency message flow according to the degree of urgency and log streams etc.
  • the characteristics of streams include but not limited to the type of stream, the data source and generation method of the stream, the transmission direction and final destination of the stream, the number of channels in the stream and the definition of data structure , the types of acquisition and processing modules actually passed through in the transmission of stream data frames, the number of input and output ports of streams in each acquisition and processing module, and the processing methods that need to be performed on streams (such as the number of merge or fan-out operations required and location, and other operations such as flow control, information extraction, and data filtering).
  • the data space in the present invention refers to the time range and channel range that all data in the workflow may contain, wherein the time range is determined by the working time length, and the channel range can be determined by the number of channels.
  • the interface application information includes each collection and processing module that the workflow passes through as the workflow The interface information of the provided interface; based on the data space information of the workflow, the interface application information and the data processing method information, determine each data field included in the processing path of the workflow, wherein the data A domain is a data area with the same flow data frame granularity during workflow processing, and the level of the data domain increases as the flow data frame granularity increases.
  • the interface application information includes the interface information of the interface provided for the workflow by each collection and processing module that the workflow flows through, wherein, the interface provided by the collection and processing module for the workflow includes an input interface and an output interface, and the interface information includes The number of input interfaces and the number of output interfaces.
  • the data field in the present invention is a data area that has the same flow data frame granularity in the workflow process, wherein the flow data frame granularity is the number of channels and the size of the time range; wherein, there are levels in the data field, and the level of the data field can be based on
  • the granularity of stream data frame is defined according to the granularity of stream data frame.
  • the data domain with smaller granularity of stream data frame is defined as low-level data domain, and the data domain with larger granularity of stream data frame is defined as high-level data domain. The larger the value, the higher the level of the data domain.
  • the workflow in the present invention contains at least one data domain during the processing process.
  • On the processing path of the workflow there are often multiple data domains accompanied by multiple merge or fan-out operations.
  • the data field where the flow data frame is located will change. Therefore, the data frame of the low-level data field from multiple ports can be merged to generate a data frame of the high-level data field, and the data frame from the high-level data field can also be passed through
  • the fanout operation results in data frames of multiple low-level data fields destined for multiple ports.
  • the merging operation can be implemented through the merging node, and the fan-out operation can be implemented through the fan-out node.
  • the data domain information also becomes the data domain attribute, wherein, the data domain information is composed of the attribute information of the data domain, and the attribute information includes but not limited to the data organization granularity (channel range and time range size), the channel position and time position offset of the current data domain in its superior data domain, the information fields contained in the stream data frame in the current data domain, and the specific format parameters of each information field, etc.
  • the data domain information is composed of the attribute information of the data domain
  • the attribute information includes but not limited to the data organization granularity (channel range and time range size), the channel position and time position offset of the current data domain in its superior data domain, the information fields contained in the stream data frame in the current data domain, and the specific format parameters of each information field, etc.
  • each collection and processing module that the workflow passes through as a target module determines the data domain information of the workflow, and the data domain information contains information related to the attribute information of the data domain where each stream processing node corresponding to the workflow is located; interface application information, data processing mode information, data domain information, and module information and module interaction of each target module based on the workflow Link information, determine the target module corresponding to each stream processing node corresponding to the workflow, and determine the position information of each stream processing node in the corresponding target module.
  • the stream processing node in the present invention is a software process running on FPGA logic unit or CPU that is located on each acquisition processing module and configured through different working parameters to complete specific basic functions.
  • the module construction information of the acquisition processing module includes but is not limited to the type of stream processing node running in the acquisition processing module, the working parameters of the stream processing node and its connection information.
  • the data processing process of the workflow is abstracted into a series of stream processing that completes data processing operations such as merging, fan-out, broadcasting, information extraction, and filtering Cascading of nodes; further, the data fields of the workflow during the transmission process will change as they pass through the merge node or fan-out node, and the granularity of the current data field will also be inserted into each data field for other flow processing of data processing operations Node; because the location of the merge node and the fan-out node is related to the collection and processing module information and its interconnection information that the workflow passes through, the data domain of each workflow is directly related to the division of the module structure in the data acquisition system .
  • each flow processing node of the workflow is assigned to each module structure layer, and the current module structure layer is determined.
  • Types of stream processing nodes that need to be run in each collection and processing module data domain information, and connection relationships of stream processing nodes.
  • each collection processing module For each collection processing module, determine each stream processing node corresponding to the collection processing module, and generate module construction information of the collection processing module based on the location information of each stream processing node.
  • each collection and processing module For each collection and processing module, determine each stream processing node in the collection and processing module, and generate the module construction information of the collection and processing module according to the location information of each flow processing node; wherein the location information includes but not limited to stream Handles node information and connection information for a node.
  • each collection processing module determines the cross-module interface node of the collection processing module, determine the collection processing module that has a connection relationship with the collection processing module based on the cross-module interface node, and connect the collection The processing module is connected with the collection and processing module with which it has a connection relationship.
  • the interface information of the collection processing module includes, but is not limited to, the interface type and the number of the output interface and the input interface of the collection processing module.
  • the functional information of the collection and processing module may specifically include information such as the function of the collection and processing module and the type of operation that the collection and processing module can process the data frame, such as merging, normalizing, decoding, encoding and other operations on the data frame; wherein,
  • the cascading information includes the specific position of the data processing module in the data acquisition system to be constructed;
  • the module interconnection information includes but is not limited to the information of the acquisition and processing module to be connected to the acquisition and processing module and the corresponding information in the acquisition and processing module. According to the connection information of the stream processing module, the collection and processing module to be connected to the collection and processing module can be determined according to the module connection information, and the collection and processing module to be connected to the collection and processing module can be connected.
  • the cross-module interface node of the present invention is a special stream processing node, and the cross-module interface node exists in the form of an FPGA module or a software process, and its function is based on the data transmission channel between two collection and processing modules. Encapsulation, so as to provide a transparent data channel including two directions and multiple point-to-point connections for the transmission of multiple streams between two collection and processing modules, and connect with other stream processing nodes through standard interfaces.
  • the specific implementation of the cross-module interface node is related to the type of data channel actually used between the two collection and transmission modules.
  • a pair of cross-module interface nodes (located in the two collection and processing modules respectively) needs to be constructed between any two collection and transmission modules.
  • multiple groups of cross-module interface nodes need to be constructed. Since there may be multiple flows from two directions (uplink or downlink) between two collection and processing modules for data transmission through the same actual data transmission channel, it is necessary to base Assign information, set the number of uplink ports and downlink ports facing stream processing node side of cross-module interface nodes.
  • the connection unit also needs to connect the corresponding data channels between the interconnected collection and processing modules to complete the connection of the cross-module interface node.
  • each collection processing module determines the node information of each stream processing node corresponding to the collection processing module, based on the node information of each stream processing node Information, using standardized encapsulated standard interfaces to connect each stream processing node of the collection processing module with the cross-module interface node to obtain a module design file corresponding to the collection processing module, and deploy the module design file to the In the collection and processing module mentioned above, to complete the construction of the data acquisition system corresponding to the construction request.
  • the module design file When deploying the module design file to the acquisition and processing module, the module design file can be deployed to the acquisition and processing module by means of FPGA logic compilation and download, CPU process operation, etc. Further, the acquisition and processing module of the deployed module design file is real-life The collection and processing modules of the system; after all the collection and processing modules are deployed, the construction of the data acquisition system is completed.
  • the module information and module interconnection information of each collection and processing module included in the data acquisition system to be constructed are determined; according to each Collect the module information and module interconnection information of the processing module, and abstract the various workflows contained in the data acquisition system; based on the number of channels and working time length of each workflow, determine the data space information of the transmitted data in each workflow ;
  • the interface application information includes the interface information of the interface provided for the workflow by each collection and processing module that the workflow flows through; based on the workflow According to the data space information, interface application information and data processing information, determine the various data domains included in the workflow processing path; for each workflow, determine each collection and processing module that the workflow flows through as the target module , and determine the data domain information of the workflow; according to the workflow interface application information, data processing method information, data domain information, module information and module interconnection information of each target module, determine
  • the module information and module interconnection information of the acquisition processing module corresponding to the construction request are determined, and each workflow in the data acquisition system is abstracted, based on each The data space information transmitted in each workflow, determine the data field information in the processing path of each workflow, and finally determine the module construction information of each collection and processing module; based on the module construction information and cross-module interface nodes, there will be a connection relationship connected to the collection and processing modules; connect the stream processing nodes and cross-module interface nodes in each collection and processing module using standardized encapsulated standard interfaces to obtain the module design files of the collection and processing modules, and deploy the module design files to the collection In the processing module, the construction of the data acquisition system is completed.
  • the present invention uses stream processing nodes to build a data acquisition system without designing each functional module, and the stream processing nodes in the constructed data acquisition system have reusability, and do not need to be redesigned when adjusting or modifying the system. It saves a lot of time, and the construction method of the data system provided by the present invention has a simple, uncomplicated and universal construction process, which reduces the difficulty of constructing the data acquisition system, so that non-specialized personnel can also use the present invention
  • the provided methods build the required data acquisition system.
  • FIG. 2 it is a flowchart of a method for determining cross-module interface nodes of an acquisition processing module provided by an embodiment of the present invention, and the specific description is as follows:
  • the cross-module interface type of the acquisition and processing module is determined, and the cross-module interface type is used to represent the type of cross-module interface node required by the acquisition and processing module.
  • S202 Determine whether there is a standard cross-module interface node corresponding to the cross-module interface type in the preset standard cross-module interface node library; if there is a standard cross-module interface node corresponding to the cross-module interface type, execute S203: If there is no standard cross-module interface node corresponding to the fast module interface type, execute S204.
  • the standard cross-module interface node library is used to save the standard cross-module interface node; in the method provided by the present invention, regardless of the physical layer, link layer and transport layer of the transmission interface between the collection and processing modules Regardless of the method, the transmission interfaces between the acquisition and processing modules are abstracted into a unified model, that is, the form of cross-module interface nodes.
  • the specific characteristics are: 1. Cross-module interface nodes always appear in pairs, respectively located in the 2. There is a pair of cross-module interface nodes between every two interconnected collection and processing modules; 3. There may be multiple cross-module interface nodes in a pair of cross-module interface nodes. Stream transmission channel; 4.
  • each stream transmission channel is independent of each other; 5.
  • Each stream transmission channel in the cross-module interface node is "transparent" to the stream data frame transmitted in it, that is, for each stream
  • the ports in the cross-module interface nodes use the same interface.
  • the standard cross-module interface node corresponding to the cross-module interface type is used as the cross-module interface node of the acquisition processing module, and the working parameters are configured for the cross-module interface node, so that the cross-module interface node can work according to the working parameters.
  • the function information, module construction information, module interconnection information, and port application information of the collection and processing module can be analyzed to obtain the cross-module interface node information of the collection and processing module.
  • the cross-module interface node information includes the node position and Working parameters, the obtained working parameters can be configured as a cross-module interface node, or the working parameters can be configured to the standard cross-module interface node corresponding to the cross-module interface type, and the standard cross-module interface node with working parameters configured As a cross-module interface node of the collection and processing module.
  • the cross-module interface node in the present invention uses optical fiber, network cable, twisted pair, coaxial cable, computer bus, etc. to connect with the acquisition process that has a connection relationship with the node according to the difference in the physical layer transmission medium and material interface used in the design. module.
  • FIG. 3 it is a flowchart of a method for determining each stream processing node corresponding to the acquisition processing module provided by the embodiment of the present invention, and the specific description is as follows:
  • each node type information corresponds to a stream processing node
  • the node type information includes the node type and Work parameter information.
  • the processing unit types of the acquisition processing module include but are not limited to FPGA types and CPU types, and different processing unit types correspond to different standard node libraries.
  • a number of standard processing nodes are stored in the standard node library.
  • the standard processing nodes in the standard node library include some flow control nodes commonly used in traditional stream processing systems, as well as the specific nodes corresponding to the data acquisition process in this solution.
  • a series of standard processing nodes, the unique standard processing nodes in the present invention all have the following characteristics: 1), the interfaces in the nodes are standard interfaces after standardized encapsulation; 2) the functions of the nodes all involve data related to the definition of standardized interface protocols Operation; 3) are all through the abstraction of the common basic data processing process in the data acquisition system, so that a limited type of standard stream processing can be grounded, which covers most of the data processing operations in the data acquisition system.
  • the node type information can be traversed through each standard processing node in the standard node library, and then judge whether there is a standard processing node corresponding to the node type information in the standard node library. processing nodes.
  • the data frame normalization node which is characterized by: the input and output ports of the node are located in the same data field, and it has multiple input ports and one output port.
  • the output of the output port is to send the data frames with the same time coordinates input to all input ports in sequence according to the spatial coordinates, keeping the content of the data frames unchanged, and actually completing the spatial sorting of each data frame;
  • the data frame is distributed to nodes (Map_T, Map_S) according to time/space, which is characterized by: the input and output ports of the nodes are located in the same data domain, and there is one input port and multiple output ports. For each data frame arriving at the input port, the node selects a certain output port to output according to the time offset address information (distributed by time) or space offset address information (distributed by space) of its superior data field, which is actually completed Each data frame is parallelized according to a simple hash expression (modulo).
  • the data merge node which is characterized in that the input port of the node is located in the low-level data domain, including all the sub-data domain entries of the upper-level data domain (it can be multiple input ports, or it can be sorted by the Regularizer node An input port of ), and the output port is located in the superordinate data domain.
  • the operation of merging the data frames of multiple low-level data domains into the data frame of the upper-level data domain is completed.
  • the basic implementation algorithm is the bucket sorting algorithm of hardware or software (for dense data organization) or merge sort (for sparse data organization) case), the algorithm implementation parameters are determined by the attributes of the two data domains;
  • the data distribution node (Map), whose function is just opposite to the Merge node, is characterized in that the input port of the node is located in the upper-level data domain, and the output ports are respectively connected to each sub-data domain.
  • the node determines the route of the data frame (the location of the output port) through the space address information in the data frame, and sends the input data frame to the corresponding output port. Please note that its function is different from that of Map_T and Map_S nodes.
  • data feature extraction node which is a stream data processing node that exists in the form of a filter
  • the input is a data stream
  • the output is a state stream.
  • Its feature is to maintain a one-dimensional array, the length of the array is the same as the spatial range of the data field, and it is used to store the data characteristics of the corresponding spatial coordinates. For each data in the flowing data stream, it is stored in the array of the corresponding channel. A two-operand operation, the result of the operation is stored in the array as a new array value.
  • the optional two operands include: replacement (used to save the latest data update of each channel), numerical summation (used to save the cumulative energy of a certain channel), plus 1 operation (used to save the cumulative data number of a certain channel )Wait.
  • replacement used to save the latest data update of each channel
  • numerical summation used to save the cumulative energy of a certain channel
  • plus 1 operation used to save the cumulative data number of a certain channel )Wait.
  • the data of the array is used as the starting point of the state flow, which can be used to detect the operating state of the system;
  • Trigger node which is a stream processing node in the form of a filter, its input is a data stream interface, a command stream interface (or an external trigger signal line), and its output is a data stream interface.
  • the command stream is required to send the trigger command frame regularly at the interval of the current data field time width of the data stream, and the trigger command frame will be received in the node.
  • the trigger command frame is not empty (or when the trigger signal line has a valid signal)
  • select The data frames within a certain time range (time window) before and after the time stamp (or trigger moment) in the current trigger command flow are used to implement the trigger selection operation in the data acquisition system.
  • the command distribution node located in the FPGA physical node, its main function is to forward the received command to the path where the command object is received; it is composed of the broadcast node of the command stream and the filter node for judging its path It is composed of the corresponding encoder/decoder; the input is the AXIS interface, and the output is the AXIS interface to the lower node and the SDMF interface to the local node.
  • the command feedback flow merging node located in the FPGA physical node, its main function is to summarize the local and subsequent level command feedback flow data frames and forward them to the upper level, and the multiplexer and corresponding encoder of the command feedback flow /decoder configuration.
  • the input interface is the AXIS interface from the lower physical node and the SDMF interface from the local node
  • the output interface is the AXIS interface sent to the upper physical node.
  • the snapshot node located in the software node, its main function is to save a copy of the latest data frame for the input data frame of a flow, for the use of the back-end monitoring system and data analysis system.
  • the standard processing nodes contained in the standard node library are not limited to the above-mentioned standard processing nodes, and may also include encoding/interface conversion between the AXIS interface and the SDMF interface inside the FPGA.
  • the decoding node decoder/encoder
  • the sending/receiving node Transmit/Receive
  • the storage node Save
  • the display node Display
  • the process management node Process Management node
  • various nodes for flow control such as flow broadcast (Broadcast), Multiplexing/demultiplexing (Mux/Demux), demultiplexing (Switcher), etc.
  • FIFO for data caching
  • vFIFO virtual FIFO built using DDR
  • each standard processing node is related to the data processing tasks to be executed by the data acquisition system to be built, each standard processing node is a standardized stream processing node, and the data acquisition system constructed using the standard processing node
  • the system can complete common online data processing such as data information extraction, case trigger judgment, and case assembly (data merging) in a unified manner.
  • the standard processing node corresponding to the node type information is used as the stream processing node corresponding to the collection processing module, and further, the working parameter information in the node type information can be used as the stream processing node The working parameters of the stream processing node to work based on the working parameters.
  • the node information corresponding to the node type information determines the node information corresponding to the node type information, and construct a stream processing node corresponding to the node type information according to the node information, and convert the work in the node type information to
  • the parameter information is configured as the working parameters of the stream processing node, and the configured stream processing node is used as the stream processing node corresponding to the acquisition processing module; the node information includes the node type, node function and other information of the stream processing node to be constructed . Further, after the stream processing node is constructed, the stream processing node can be saved in the standard node library as a standard stream processing node.
  • the standard processing nodes in the standard node library can be directly used.
  • the required standard processing nodes do not exist in the standard node library, the required standard processing nodes can be directly constructed.
  • Standard processing nodes whose construction is simple and easy to understand, have great convenience, which can further improve the practicability and flexibility of building data processing modules, and the built standard processing nodes are reusable, without repeated construction The same nodes further improve the efficiency of building a data processing system and simplify the process of building a data acquisition system.
  • the processing unit types of the acquisition processing module include but are not limited to FPGA types and CPU types.
  • S402. Determine the data domain attribute of each of the data interfaces, and determine the stream data frame parameters and stream data frame information segment content of each of the data interfaces based on the data domain attributes of each of the data interfaces.
  • the data field attribute can be determined according to the ports at both ends of the data interface, and according to the determined data field attribute, the parameters of the flow data frame and the content of the information segment of the flow data frame can be determined.
  • Stream data frame parameters include but not limited to the attribute information of the data space corresponding to the acquisition processing module and the attribute information of the data domain corresponding to the data interface; further, the stream data frame parameters of these data interfaces determine the data acquisition system to be built The time and space scale of the stream data space, the specific format and information extraction method of metadata in the stream data space, the specific length of each information segment in the stream data frame, the organization mode of metadata, etc.; among them, each data interface The stream data frame parameter also determines the mapping relationship between the data blocks in the stream data frame transmitted by the data interface and the data blocks in the stream data frame transmitted by the data interface associated with the data interface.
  • the stream data frame information segment which includes but is not limited to: Stream Frame Head, Stream Frame Length, Father Domain Start Time Index, The time offset address of the current data domain in the upper-level data domain,), the starting space coordinates of the parent data domain (Father Domain Start Space Index, the space offset address of the current data domain in the upper-level data domain), and the current data frame contains The number of data blocks (Block Number), the properties of each data block (Block Properties), the data payload (Block Data) of each data block, and the reserved frame tail (Stream Frame Tail) and out-of-band data (Outband Data) , user-defined information field) and other content; wherein the stream data frame header (Stream Frame Head) includes but not limited to: stream ID, data field number, start and stop criteria, empty/non-empty flag and other information; the data block Attributes (Block Properties) include but are not limited to: the start time address (Start Time Index) and start space address (Start Space Index) of the current data block in the current data domain,
  • the stream data frame parameters and stream data segment content can be applied to the preset standard stream data frame format template, thereby determining the data The stream data frame format of the stream data frame transmitted by the interface, thereby defining the data structure of the stream data frame of the data interface.
  • the definition of the stream data frame format of the stream data frame includes the definition of the stream data frame information segment in the stream data frame format, the definition of the data block attributes in the stream data frame information segment, and the data about the data block in the stream data frame information segment Definition of the payload; specifically, the definition of the stream data frame format of the stream data frame includes the data frame header, the length of the data frame, the starting time coordinates of the parent data field, the starting space coordinates of the parent data field, and the data of the current data frame Number of blocks, data block attributes, data payload of data blocks, out-of-band data, data frame tail, etc.
  • the data block attributes may include the starting time address of the current data block in the current data domain, the starting space address of the current data block in the current data domain, the time address length of the current data block, the space address length of the current data block, the data block Data arrays such as length and content such as data.
  • the organization of data block properties and its data payload is determined by different data block types.
  • FIG. 5 it is an example diagram of the definition of a stream data frame format of a stream data frame provided by an embodiment of the present invention.
  • FIG. 5 can also be called an example diagram of the definition of a standard protocol frame format of a stream data frame, as
  • the standard protocol frame 502 consists of data frame header, data frame length, parent data field start time coordinates, parent data field start space coordinates, number of data blocks, out-of-band data, data frame tail, multiple data blocks Attributes and their data payloads, where the data block attributes and data payloads exist in pairs.
  • data blocks can be divided into four possible types, namely "fixed data width, fixed number of data” type, “fixed data width, variable number of data” type, “data Width change” type and “sub-data frame” type; the structure definition of each type of data block attribute and its corresponding data payload is shown as 501 and 503 in FIG. 5 .
  • the working scenario represented by the type of "fixed data width and fixed number of data” is: the data corresponding to each channel at each moment has a fixed length, and all channels within the range of a continuous channel with a certain length in the current data domain, in The data at each moment is continuously output within a time range of a certain length to constitute the content in the data block.
  • the data payload contains a certain number of metadata, which are organized in the form of a data matrix, that is, each metadata of each channel within the effective time range is output in sequence according to the order of the channels, and all metadata depends on its presence in the data
  • the offset position in the matrix is used to determine its time and space coordinates in the data domain, without explicitly transmitting the time and space coordinate information of each data.
  • the data block attribute can be defined by starting time address, time address length, starting space address and space address length.
  • the working scenario represented by the "fixed data width, variable number of data” type is: the data corresponding to each channel has a fixed width at each moment, but there will be a random number of channels within the time and space range of the current data domain Output data at random times.
  • all the data in the data domain is divided into one or more data blocks for transmission.
  • the data payload of each data block contains each metadata that is sequentially output according to the channel and time sequence.
  • Each metadata is generated by the currently generated data.
  • the space address of the channel in the current data block, the time address in the current data block at the moment corresponding to the current data, and the data content are spliced together, and each metadata also has a certain width.
  • the attribute of the data block can be defined by the start time address and the start space address of the current block in the data field, and the total length of the data payload in the data block (data block length).
  • a channel may have variable width data at a certain moment. At this time, each such data in the space-time range corresponding to a data field is treated as a separate block, and the data payload is this variable-length data.
  • the attribute of the data block can be the starting time address of the current data in the data field , start space address and data block length (that is, the width of the current data) to define.
  • the working scenario represented by the "sub-data frame” type is: the data payload of each data block is a complete data frame (sub-data frame) in its subordinate data domain.
  • the data block attribute only contains the data of the current sub-data frame Length information (data block length), the time address offset and space address offset of each sub-data frame in the current data domain can be described by the parent data domain start time coordinate and parent data domain start space coordinate in the sub-data frame .
  • the stream data frame transmitted by the data interface contains a certain information segment, the specific length of the included information segment, the specific organization of the data block, etc. are all determined by the data frame parameters; among them, in the same data field
  • the stream data frames transmitted between the data interfaces of the stream processing nodes below all use the same stream data frame format, that is, the stream data frames transmitted between the data interfaces under the same data domain all adopt the same data structure.
  • the stream data frame may flow in a serial frame, and the internal information segments of the stream data frame may also exist in the data of the stream processing node in a parallel manner. interface.
  • the present invention standardizes and encapsulates the data interface to obtain a standard interface, and applies the standard interface so that the data frame processed in the data acquisition system to be constructed has a standard transmission form and processing method.
  • the standard data interface type specifically includes the following types:
  • AXI4-Stream interface (abbreviated as AXIS interface), wherein, the interface is inside the FPGA, the interface used for data transmission between the stream processing node and the link layer interface of the external interface, and is used to transmit standard stream data frame;
  • SDMF interface Standard D-Matrix FPGAinterface interface
  • the interface is inside the FPGA, the interface used for data transmission between two stream processing nodes, this interface is a custom interface, its basic idea
  • SDMF interface Standard D-Matrix FPGAinterface interface
  • the file descriptor interface is inside the computer, and the interface is essentially a software interface, which is used for data transmission between the stream processing node and the external communication interface (driver program).
  • Standard character device file descriptors (similar to sockets, pipes, and FIFOs) are implemented to conform to the general practice within the operating system;
  • SDMS interface Standard D-Matrix Software interface
  • this interface is inside the computer, this interface is used for data transmission between stream processing nodes, this interface is a custom interface, its basic design idea It is a task queue + shared memory interface, and each stream processing node is designed as a computer internal process, using shared memory to complete data exchange, and using task queues to be responsible for the transfer of stream data frame processing tasks between processes to reduce unnecessary data replication overhead.
  • each data interface of the stream processing node mainly responsible for data processing adopts SDMF interface or SDMS interface.
  • the SDMF interface when the SDMF interface transmits data frames, there are two types of data frames: non-empty data frames and empty data frames, and the working sequence of the SDMF interface is different when transmitting non-empty data frames and transmitting empty data frames.
  • the interface model encapsulated into the data interface is a multi-way point-to-point interface model.
  • the multi-way point-to-point interface model is described.
  • the model schematic diagram of the multi-way point-to-point interface model is shown in Figure 6.
  • the multi-way point-to-point interface model includes an uplink transport layer and a downlink transport layer. There are multiple uplink transmission channels, and the downlink transmission layer also contains multiple downlink transmission channels.
  • each stream transmitted in the data interface is represented as a pair of transparent input/output interface pairs in the model, and each stream is logically independent from each other. Among them, the data interface Each stream transferred corresponds to a data transfer channel.
  • each flow has a blocking feature through this data interface, that is, when the data receiving end cannot receive When data (blocking), the sender should stop sending through appropriate data buffering and notification mechanisms until the blocking state ends.
  • the system has data compression requirements for some streams, it can also be realized by adding compression/decompression modules that appear in pairs at the sending end and receiving end.
  • various interfaces are encapsulated into the same model in the present invention, so that the data transmission process in the data acquisition system separate from data processing.
  • each data interface of the stream processing node is preprocessed to define the interface of each data interface and the format of the stream data frame transmitted by the data interface, so that the same
  • the data frame transmitted by the data interface defined by the interface definition and the format of the stream data frame has the same characteristics, so that such data interfaces can be connected to each other, and the flexibility is higher when using the stream processing node to build a data processing module.
  • the multi-way point-to-point interface model adds different designs according to the situation of the actual data interface.
  • the data rate of the uplink channel (data flow/status flow/error report flow) in the constructed data acquisition system is far greater than that of the downlink
  • the node, combined with data buffering, implements the blocking characteristics of each flow in the uplink channel.
  • nodes such as data frame check code generation/data frame check code check, data frame splitting/reassembly, data compression/decompression, channel arbitration/distribution, etc. are selectively added.
  • the present invention provides an internal implementation block diagram of a multi-way point-to-point interface model, specifically as shown in Figure 7, shown in the figure is a fiber channel that only includes the basic physical layer/link layer interface
  • the block diagram of the model above contains multiple components, among which data compression and data decompression are optional components, and different components are selected in different data transmission layers.
  • the interface of each component in the figure is a unified AXIS interface.
  • AXIS interface By selectively adding components to different transmission paths, a variety of standardized components are provided for the data transmission of different streams, and finally ensure that cross-physical nodes transparent connection.
  • the unified standard AXIS interface is used in the figure, so for different interfaces (optical fiber, differential cable, network port, etc.) Modules implement support for different interfaces, so as not to affect the design of other parts of the data acquisition system.
  • the node information is obtained by parsing the module construction information of the acquisition processing module, and the node information includes information such as the node type, working parameters, and connection information of the stream processing node.
  • each of the stream processing nodes based on the connection information of the stream processing node, determine a target port of a target connection node corresponding to each port of the stream processing node, where the target connection node is connected to the The stream processing node has a connection relationship with the stream processing node, and the target port is a port connected to the stream processing node in the target connection node.
  • each port in each of the stream processing nodes determine the connection mode of the port based on the node type of the stream processing node where the port is located, and determine the target connection node corresponding to the port and the Whether the stream processing nodes where the port is located are all in the same collection and processing module; if the target connection node corresponding to the port is not in the same collection module as the stream processing node where the port is located, then execute S804; if the The target connection node corresponding to the port is in the same collection and processing module as the stream processing node where the port is located, and S805 is executed.
  • the node types of stream processing nodes can be divided into two types, one is a stream processing node in the form of an FPGA module, and the other is in the form of a software process Stream processing nodes.
  • the port connection method of the stream processing node in the form of an FPGA module is to generate an FPGA top-level design file, and use the signal in the FPGA top-level design file to directly connect the stream processing node in the form of an FPGA module that needs to be connected, and finally obtain a complete top-level design document.
  • connection mode of stream processing nodes in the form of software processes is to use inter-process communication, and the connection is completed by referencing the same shared resources in the stream processing nodes that need to be connected, such as shared memory, semaphore or message queue.
  • the stream processing nodes in the form of software processes are connected through the SDMS interface.
  • the SDMS interface uses shared memory as a container for data storage, and uses a standard message queue as a channel for task delivery between nodes. Different processes in the same physical node can achieve data interaction by accessing data frames in the same piece of memory, which can reduce the copying overhead caused by data flowing inside the physical node.
  • the shared memory management adopts the memory pool management method. When the physical node is initialized, it first applies for a large piece of continuous memory and divides it into two parts, key_shm and aux_shm. Each node applies for shared memory from the memory pool using a method similar to the application method of kernel malloc to allocate memory.
  • the shared memory pool is divided into the following two sub-pools: 1) data shared memory key_shm, used to store standard data frames in each stream; 2) index shared memory aux_shm, used to store index information of a data frame.
  • the data format of the index contribution memory in the present invention includes the overall description information of the data frame, a data block list and a channel list; wherein, the data block list includes at least one data block, and the channel list includes at least one channel.
  • the index contribution memory in the present invention also includes a FrameDescriptor structure, a BlockDescriptor structure and a Struct Channel Descriptor structure; wherein, the FrameDescriptor structure is used to preserve the overall description information for a data frame; the BlockDescriptor structure is used to preserve the data block Description.
  • the data format of the indexed shared memory is shown in FIG. 9.
  • the data format of the indexed shared memory is composed of a frame descriptor 901, a block descriptor list 902, and a channel descriptor list 903, wherein the block descriptor
  • the linked list 902 contains descriptors of 4 data blocks, which are respectively data block 1 descriptor, data block 2 descriptor, data block 3 descriptor and data block 4 descriptor;
  • the channel descriptor linked list 903 contains multiple Descriptors, specifically, each channel has two descriptors, as shown in the figure, it specifically includes descriptor 1 and descriptor 2 of channel 1, and descriptor 1 and descriptor 2 of channel 2.
  • the frame descriptor 901 is composed of a FrameDescriptor structure 904, which is obtained by encoding the FrameDescriptor structure 904, and the encoding content of the FrameDescriptor structure 904 is as follows:
  • the descriptor of the data block in the block descriptor link table is composed of the BlockDescriptor structure 905, which is defined by coding.
  • the BlockDescriptor structure 905 in the data block 2 descriptor is used as an example for illustration.
  • the BlockDescriptor structure The encoded content of 905 is as follows:
  • the channel descriptor in the channel description list is composed of a ChannelDescriptor structure 903, which is defined by coding, and is exemplified by the ChannelDescriptor structure 903 in the No. 2 descriptor of channel 1 in the channel description link list Instructions, the encoded content of the ChannelDescriptor structure 903 is as follows:
  • the above content is the content of explaining the data format of the index shared memory based on FIG. 9 .
  • the inter-node transmission interface adopts message queues, and the underlying implementation of queues can also be queues based on shared memory and synchronization primitives (semaphore, etc.), or boost.mqueue can also be used.
  • the interface is a standard single-producer single-consumer model. The previous node puts the aux_shm_addr type task of the FrameDesc starting address into the queue, and the subsequent node takes the task out of the queue, and accesses the FrameDesc and BlockDesc in aux_shm to complete further data frame analysis.
  • the port of the stream processing node in the present invention is connected to the port that has a connection relationship with the port by calling a standardized packaged standard interface, so that the stream processing node can be connected to the stream processing node that has a connection relationship with the stream processing node;
  • the ports in the invention need to adopt the same type of standard interface.
  • the construction of a data acquisition system for marine time-lapse seismic is taken as an example for illustration, wherein, the data processing module of the data acquisition system for marine time-lapse seismic to be constructed has three parts, which are water Lower streamer system, data collection unit and data display recording unit.
  • the collection and processing module can be a basic module for building a data acquisition system, and this module is used to collect electrical signals, where the collection and processing module can be a detector system, further, here The detector system can be called a stream data source module.
  • the detector system has different organization and connection relationships, and often shows different hierarchical relationships in space, and has different organizational granularity at different levels; for example: a detector system One front-end electronics chip is responsible for reading the data of 32 channels, one front-end electronics plug-in contains 4 such chips (128 channels/plug-in), one chassis contains 8 front-end electronics plug-ins (1024 channels/chassis) , the entire sub-detector system may contain 8 chassis (8192 channels/system).
  • the streaming data source module In addition to showing different levels in space, the streaming data source module also has different hierarchical relationships in the time range of collection based on the spatial hierarchical relationship of the streaming data source module; the streaming data source module reflects these hierarchical relationships in the data organization , so that the data flow collected by the stream data source module has a data space with a related hierarchical relationship, wherein there are data fields with nested levels in the data space, and each data field represents a different data space range and data time organization granularity,
  • the data in each data domain has its own time and space range, which is defined as the data domain space.
  • the introduction of the data domain space is mainly to achieve the purpose of compressing the data rate by reducing the size of the time and space information segments associated with the data.
  • the division of data domains is related to physical factors such as the organization of stream data source modules and the time scale of information processing.
  • FIG. 10 it is an example diagram of the relationship between the data space and the data domain in the data stream formed by the electronic signal collected by the stream data source module provided by the present invention
  • 1001 in the figure is metadata
  • 1002 in the figure, 1003 and 1004 are both data domains; there are 8 data domains 1002 in the figure; 2 data domains 1003 and 1 data domain 1004; among them, each metadata 1001 constitutes the data layer 1 of the first level; 8 data domains 1002 constitute the first level The data layer 2 of the second level; two data fields 1003 constitute the data layer 3 of the third level; one data field 1004 constitutes the data layer 3 of the third level; wherein, the level of the data layer 1 is lower than the level of the data layer 2, and the data The level of layer 2 is lower than that of data layer 3; as shown in the figure, each data field 1002 contains 8 pieces of metadata, and the metadata contained in each data field 1002 is different.
  • the data space and data domain of the stream data source module have the following characteristics:
  • Each data domain space is spliced by one (the bottom data domain) or multiple sub-data domain spaces;
  • the sub-data domain space must be completely included in a higher-level data domain, and the sub-data domain space is not allowed to be included in multiple upper-level data domains of the same layer at the same time;
  • the splicing of the parent data domain space by the child data domain space is two-dimensional, that is, the child data domain space may have different granularity from the parent data domain in both time and space dimensions.
  • the number of child data domains contained in the parent data domain in the time and space dimensions should be an integer power of 2; among them, the parent data domain and the child data domain are relative, as shown in Figure 10, with a data domain
  • the data domain 1003 is the parent data domain of the data domain 1002, wherein each data domain 1002 in the data domain 1003 is a child data domain of the data 1003;
  • the construction information is the information for constructing the underwater streamer system, the data collection unit, and the data display and recording unit respectively, and describes the constructed underwater streamer system, the data collection unit, and the data display and recording unit.
  • the underwater streamer system is composed of multiple acquisition units.
  • the acquisition unit consists of a working state sensor readout node, an SDMF encoder node (also called an SDMF_encoder node), a multiplexer node (also called a MUX node), and a command feedback stream merging node (also called Can be called Reduce_CMD_FB node), command broadcast node (also called Map_CMD node), transport layer interface node, ADC readout node, normalization node (also called Regularizer node), SDMF decoder node (also called SDMF_decoder node) and a merge node (also called a Merge node) are connected to form, wherein, the transport layer interface node supports 8B/10B encoding, verification, and back pressure control functions, and the working status sensor reading node is used to read temperature, Voltage and other parameters
  • the command stream is broadcast by the upper node to the local nodes and lower nodes that need command control by the Map_CMD node, and the Reduce_CMD_FB node collects the command feedback sent by each local node and the subsequent acquisition unit Stream data frames and forward them to the upstream.
  • the data flow comes from the ADC readout node and the transport layer interface node connected to the subsequent acquisition unit.
  • Each acquisition unit contains two ADC readout nodes, and each ADC readout node is responsible for connecting with the ADC data interface and the ADC control interface.
  • the ADC data interface and the ADC control interface can be the interface of the stream data source module; the data streams from the two ADC data interfaces are spatially sorted by the Regularizer node and enter the Merge node to complete the data merging.
  • the data field is composed of ADC-level data
  • the domain is transformed into an acquisition unit-level data domain.
  • the second Regularizer node spatially sorts the local data frame and the data frame from the subsequent acquisition unit before uploading. In this way, the data frames from each acquisition unit are uploaded step by step and summarized into the data flow of the entire streamer.
  • the status stream comes from a separate working status sensor readout node. Since the status stream is uploaded in units of acquisition units, data merging is not required, so the local status stream and the subsequent status stream are simply multiplexed and uploaded .
  • the ADC readout node shown in the figure is a sensor readout node, which can be set according to actual needs.
  • FIG 12 it is a schematic diagram of a model of a sensor readout node provided by the present invention.
  • all the external interfaces of the flow use the SDMF interface.
  • the register device configuration system control in the figure is used to maintain the time according to the timestamp
  • the allocated clock/second pulse signal controls the generation of streams, such as generating status streams, data streams, error reporting/command feedback streams, and other streams, etc., and stream scheduling is used to output the generated streams.
  • the sensor reading node provided by the present invention has at least one command flow (downlink), one data flow (uplink), and one command feedback flow (used to transmit response information to commands, uplink).
  • the data summarizing unit is made up of transport layer interface node, data buffer node (also can be referred to as vFIFO node), SDMF coder node (also can be called as vFIFO node) Can be called SDMF_decoder node), multiplexer node (also called MUX node), normalization node (also called Regularizer node), command feedback stream merge node (also called Reduce_CMD_FB node), command broadcast Node (also called Map_CMD node), SDMF broadcast node (also called SDMF_broadcast node), feature extraction node (also called Feature_extractor node), trigger filter node (also called Trigger node) and merge node ( It can also be called Merge node) connected.
  • data buffer node also can be referred to as vFIFO node
  • SDMF coder node also can be called as vFIFO node
  • MUX node multiplexer node
  • normalization node also called Regularizer node
  • the transport layer interface connected to the data cache node in the figure is used to connect with the underwater streamer system, where one transport layer interface node is connected to an underwater streamer system, and the transport layer interface node here supports 8B/10B encoding, calibration Functions such as test and back pressure control;
  • the transport layer interface node connected with the SDMF encoder node is used to connect with the data display recording unit, where the transport layer interface node can be used as a PCI-E interface and a DMA controller, and also supports 8B/10B encoding, verification, back pressure control, data frame splitting/assembly and other functions.
  • the data summary unit includes status flow, command feedback flow, command flow, monitoring flow and data flow.
  • the interfaces applied to nodes are different, and different interfaces apply different definitions and transmissions.
  • the formats of the streams are different, and the streams output by different interfaces in the figure are represented by different arrows; as shown in the figure, SDMF interfaces have corresponding status streams, command feedback streams, command streams, monitoring streams, and data streams.
  • AXI4- The Stream interface has its corresponding status flow, command flow, monitoring flow, and data flow; the data aggregation unit shown in the figure is responsible for information exchange and data aggregation with the four-way underwater streamer system.
  • the data flow is cached and normalized by the Regularizer node in the data aggregation unit, and the space-sorted data frames are sent to the two processing nodes.
  • the feature extraction node the latest data in each channel is extracted from the data in the data frame, and sent to the software as a monitoring stream for monitoring the operating status of the streamer (vibrator diagram).
  • the Trigger node is controlled to output all data frames within the time window to be recorded according to the gun control signal. Due to the limitation of cache space, all the data in a trigger window cannot be fully buffered in the data summary unit. Select an appropriate data field time range in the Merge node to merge these data frames, and finally send them to the data display and recording unit for data Record usage.
  • the data display and recording unit is composed of a transport layer interface node, a receiving node (also referred to as a Receive node), and a sending node (also referred to as a Receive node).
  • Transmit node broadcast node (also called Broadcast node), display node (also called Display node), merge node (also called Merge node), error check node (also called Error Check node ), process manager node (also called Process Keeper), readback node (also called Load node), command broadcast node (also called Map_CMD node), multi-way switching node (also called Switcher node ), a storage node (also called a Save node), a command console node (also called a CMD Console node), an FFT transformation node, and a result analysis node.
  • broadcast node also called Broadcast node
  • display node also called Display node
  • merge node also called Merge node
  • error check node also called Error Check node
  • process manager node also called Process Keeper
  • readback node also called Load node
  • command broadcast node also called Map_CMD node
  • multi-way switching node also called Switcher node
  • storage node also
  • the data display and recording unit is connected to the data summary unit through the transport layer interface.
  • the data display and recording unit includes status flow, monitoring flow, command feedback flow, command flow and data flow.
  • the types of interfaces used by different nodes are different.
  • the formats and definitions of the output streams are also different.
  • both the SDMS interface and the file descriptor interface have corresponding status streams, data streams, monitoring streams, and command streams.
  • the status flow and monitoring flow are directly connected to the display node to display the current working status of the system, but the error information in the status flow will be reported to the command console to complete the corresponding error handling.
  • the command console also serves as the starting point of the command flow and the end point of the command feedback flow.
  • the third level of data merging is required to finally obtain all the data in the time window corresponding to each trigger. While these data are being saved, they also need to be sent to a data quality analysis module (FFT, result analysis) for use in quality control.
  • FFT data quality analysis module
  • the construction of the data acquisition system for offshore time-lapse seismic can be completed.
  • the underwater streamer system, the data summarization unit, and the data display record provided by the embodiments of the present invention
  • most of the stream processing nodes used are standard stream processing nodes (nodes with solid lines in the figure), such as the command broadcast node in the acquisition unit of the underwater streamer system, and the specifications in the data summary unit
  • the process of real-time data collection, transmission, processing, monitoring and system control is abstracted into a series of cascading and combination of stream processing nodes.
  • These nodes adopt standard interface mode and standard stream data frame format, and have two implementation modes: hardware (logic module in FPGA) or software (computer process), and stream processing nodes under the same data domain can be connected arbitrarily.
  • the basic processing methods of each stream in the data acquisition system are abstracted into a series of standard stream processing nodes, and the modules are improved on the premise of ensuring the real-time data processing capability of the system. Reusability reduces the design workload and accelerates the design and implementation of the entire data acquisition system.
  • the method provided by the invention is also a set of open data acquisition system standard framework.
  • users can add custom sensor front-end electronics readout nodes and personalized data processing nodes to achieve data acquisition and real-time data processing requirements for various common application scenarios, with Good versatility and scalability.
  • the original transmission interface can also be seamlessly replaced, thereby completing the upgrading and transformation of the high-speed transmission interface, thereby simplifying the upgrading and transformation process of the data acquisition system.
  • the data acquisition system constructed by applying the method provided by the present invention adopts standard transmission interfaces and data frame protocols between each flow processing node, so it has the characteristics of arbitrary connection, so by increasing the input and output ports of each flow processing node Debug nodes such as analog data source, data protocol check, data frame display, storage, etc. can easily debug a single node, and can also easily insert various debug nodes on the path of each flow, thus greatly simplifying the system debugging process .
  • the method for constructing the data acquisition system provided by the present invention does not require the user to have very professional design ability and professional knowledge during application, and the data acquisition system can be freely customized through the connection of simple modules, thereby facilitating the user's use.
  • the embodiment of the present invention provides a device for constructing a data acquisition system, which can be applied to a computer device or platform for constructing a data acquisition system.
  • the schematic structural diagram of the device provided by the present invention is shown in As shown in Figure 15, the specific instructions are as follows:
  • the response unit 1501 is configured to determine the module information and module interconnection information of each collection and processing module included in the data acquisition system to be built in response to the construction request sent by the user for building the data acquisition system;
  • An abstraction unit 1502 configured to abstract various workflows contained in the data acquisition system according to the module information and module interconnection information of each of the acquisition processing modules;
  • the first determining unit 1503 is configured to determine the data space information of the data transmitted in each of the workflows based on the number of channels and the length of working time of each of the workflows;
  • the second determining unit 1504 is configured to, for each of the workflows, determine the data processing mode information and interface application information of the workflow, and the interface application information includes each collection process that the workflow passes through The interface information of the interface provided by the module for the workflow; based on the data space information of the workflow, the interface application information and the data processing mode information, determine each data field included in the processing path of the workflow , wherein, the data domain is a data area having the same stream data frame granularity during workflow processing, and the level of the data domain increases as the stream data frame granularity increases;
  • the third determining unit 1505 is configured to, for each of the workflows, determine each collection and processing module that the workflow passes through as a target module, and determine the data field information of the workflow, the data
  • the domain information includes attribute information of the data domain where each stream processing node corresponding to the workflow is located; interface application information, data processing mode information, data domain information and each target module based on the workflow module information and module interconnection information, determine the target module corresponding to each stream processing node corresponding to the workflow, and determine the position information of each stream processing node in the corresponding target module;
  • the generating unit 1506 is configured to, for each of the collection and processing modules, determine each stream processing node corresponding to the collection and processing module, and generate module construction information of the collection and processing module based on the location information of each stream processing node;
  • the fourth determining unit 1507 is configured to, for each of the collection and processing modules, determine the cross-module interface node of the collection and processing module, and determine the collection and processing module that has a connection relationship with the collection and processing module based on the cross-module interface node , and connecting the collection and processing module with its collection and processing modules that have a connection relationship;
  • the connection unit 1508 is configured to, for each of the collection processing modules, determine the node information of each stream processing node corresponding to the collection processing module according to the module construction information of the collection processing module, based on each of the stream
  • the node information of the processing node is connected with each flow processing node of the acquisition processing module and the cross-module interface node using a standardized interface after encapsulation, and a module design file corresponding to the acquisition processing module is obtained, and the module design The file is deployed to the acquisition processing module to complete the construction of the data acquisition system corresponding to the construction request.
  • the module information and module interconnection information of each collection and processing module contained in the data acquisition system to be constructed are determined; according to each Collect the module information and module interconnection information of the processing module, and extract the various workflows contained in the data acquisition system; based on the number of channels and working hours of each workflow, determine the data space for transmitting data in each workflow information; for each workflow, determine the data processing method and interface application information of the workflow, the interface application information includes the interface information of the interface provided for the workflow by each collection and processing module that the workflow flows through; based on the work The data space information, interface application information, and data processing information of the flow determine the various data fields included in the processing path of the workflow; for each workflow, each acquisition and processing module that the workflow passes through is determined as the target module, and determine the data domain information of the workflow; determine each flow corresponding to the workflow according to the interface application information of the workflow, data processing method information, data domain information, module information and module
  • the module information and module interconnection information of the acquisition processing module corresponding to the construction request are determined, and each workflow in the data acquisition system is abstracted, based on each The data space information transmitted in each workflow, determine the data field information in the processing path of each workflow, and finally determine the module construction information of each collection and processing module; based on the module construction information and cross-module interface nodes, there will be a connection relationship connected to the collection and processing modules; connect the stream processing nodes and cross-module interface nodes in each collection and processing module using standardized encapsulated standard interfaces to obtain the module design files of the collection and processing modules, and deploy the module design files to the collection In the processing module, the construction of the data acquisition system is completed.
  • the present invention uses stream processing nodes to build a data acquisition system without designing each functional module, and the stream processing nodes in the constructed data acquisition system have reusability, and do not need to be redesigned when adjusting or modifying the system. It saves a lot of time, and the construction method of the data system provided by the present invention has a simple, uncomplicated and universal construction process, which reduces the difficulty of constructing the data acquisition system, so that non-specialized personnel can also use the present invention
  • the provided methods build the required data acquisition system.
  • the device provided by the embodiment of the present invention, the fourth determining unit 1507, may be configured as:
  • a first determining subunit configured to determine the cross-module interface type of the acquisition processing module
  • the first judging subunit is used to judge whether there is a standard cross-module interface node corresponding to the cross-module interface type in the preset standard cross-module interface node library;
  • the second determining subunit is configured to use the standard cross-module interface node corresponding to the cross-module interface type as the cross-module of the acquisition processing module if there is a standard cross-module interface node corresponding to the cross-module interface type interface node;
  • the generating unit 1506 may be configured as:
  • An acquisition subunit configured to acquire information about each node type of the acquisition processing module
  • the second judging subunit is configured to, for each of the node type information, determine whether there is a standard processing node corresponding to the node type information in the standard node library corresponding to the processing unit type of the acquisition processing module;
  • the third determining subunit is configured to use the standard processing node corresponding to the node type information as the stream processing node corresponding to the collection processing module if there is a standard processing node corresponding to the node type information;
  • the second construction subunit is configured to construct a stream processing node corresponding to the node type information based on the node information corresponding to the node type information if there is no standard processing node corresponding to the node type information, and The constructed stream processing node is used as the stream processing node corresponding to the acquisition processing module.
  • the fifth determining unit is configured to, for each data interface in the collection and processing module, determine the processing unit type of the collection and processing module where each data interface is located;
  • the sixth determination unit is configured to determine the data domain attribute of each of the data interfaces, and determine the flow data frame parameters and flow data frame information segment content of each of the data interfaces based on the data domain attributes of each of the data interfaces ;
  • the input unit is configured to, for each of the data interfaces, apply the stream data frame parameters and stream data frame information segment content of the data interface to a preset standard stream data frame format module to obtain the standard stream of the data interface data frame format;
  • the acquisition unit is configured to standardize and encapsulate each of the data interfaces based on the standard data interface type, working parameters, and standard stream data frame format of each of the data interfaces to obtain a standard interface corresponding to each of the data interfaces.
  • connection unit 1508 can be configured as:
  • a parsing subunit configured to parse the node information of each of the stream processing nodes to obtain the node type and connection information of each of the stream processing nodes;
  • the fourth determining subunit is configured to, for each of the stream processing nodes, determine a target port of a target connection node corresponding to each port of the stream processing node based on the connection information of the stream processing node, the target
  • the connection node is a stream processing node that has a connection relationship with the stream processing node, and the target port is a port connected to the stream processing node in the target connection node;
  • the third judging subunit is configured to, for each port in each of the stream processing nodes, determine the connection mode of the port based on the node type of the stream processing node where the port is located, and determine the port corresponding to the Whether the target connection node and the stream processing node where the port is located are both in the same collection and processing module;
  • the first connection subunit is configured to determine the standard corresponding to the port in the standard conversion module if the target connection node corresponding to the port is not in the same collection and processing module as the stream processing node where the port is located port, standardize and encapsulate the interface between the port and the standard port corresponding to the port, and use the standard conversion module to apply the port after determining the working parameters of the standard conversion module based on the data domain attributes of the port
  • the port is connected to the cross-module interface node in a connection manner, so that the port is connected to the target port corresponding to the port through the cross-module interface node;
  • the second connection subunit is configured to, if the target connection node corresponding to the port and the stream processing node where the port is located are in the same collection and processing module, then perform a connection between the port and the target port corresponding to the port Standardized encapsulation is performed on the interfaces between them to obtain a standard interface, and the connection mode of the port is applied through the standard interface, so that the port is connected to the target port corresponding to the port.
  • each embodiment in this specification is described in a progressive manner, the same and similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments.
  • the description is relatively simple, and for related parts, please refer to the part of the description of the method embodiment.
  • the systems and system embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is It can be located in one place, or it can be distributed to multiple network elements. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. It can be understood and implemented by those skilled in the art without creative effort.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computational Linguistics (AREA)
  • Fuzzy Systems (AREA)
  • Mathematical Physics (AREA)
  • Probability & Statistics with Applications (AREA)
  • Software Systems (AREA)
  • Computer And Data Communications (AREA)

Abstract

本发明提供一种数据获取系统的构建方法及装置，该方法包括：响应于用户发送的用于构建数据获取系统的构建请求，确定与所述构建请求对应的采集处理模块的模块信息和模块互连信息，抽象出数据获取系统中包含的各种工作流；确定每种工作流中所传输数据的数据空间信息；对于每种工作流，确定工作流所包含的各个数据域和所流经的采集处理模块所提供的接口的接口信息；对于每个采集处理模块，使用标准化封装后的标准接口将各个流处理节点和跨模块接口节点进行连接，并将得到的模块设计文件部署至采集处理模块中，以完成数据获取系统的构建。本发明使用流处理节点构建数据获取系统，无需对每个功能模块进行设计，降低了构建数据获取系统的难度。

Description

数据获取系统的构建方法及装置 技术领域
本发明涉及数据获取技术领域，特别涉及一种数据获取系统的构建方法及装置。
背景技术
随着科学技术的进步，流数据开始广泛应用在各种领域中，流数据是一组顺序、大量、快速到达的数据序列，一般情况下，数据流可以被视为一个随时间延续而无限增长的动态数据集合。在不同的应用领域以及不同的应用场景，对流数据的获取方式和系统有着巨大的差异。
目前，在不同的应用领域或是不同的应用场景在构建用于获取流数据的数据获取系统时，通常需要根据特定的场景或是领域对系统进行针对性的设计，在设计系统的过程中要求设计人员必须有丰富的专业知识，设计过程复杂，并且设计过程并没有将流处理框架应用于构建数据获取系统，使得设计出的系统中的各种功能模块不具通用性，在调整或是修改数据获取系统时，都需要重新设计数据获取系统中的各种功能模块，由此增加了构建数据获取系统的难度。
发明内容
有鉴于此，本发明提供一种数据获取系统的构建方法及装置，应用本发明，通过使用标准的流处理节点构建数据获取系统，降低了构建数据获取系统的难度，并且本发明可以适用于多种构建数据获取系统的场景，更具有普遍性和便利性。
为实现上述目的，本发明提供如下技术方案：
一种数据获取系统的构建方法，包括：
响应于用户发送的用于构建数据获取系统的构建请求，确定所要构建的数据获取系统中所包含的各个采集处理模块的模块信息和模块互连信息；
根据各个所述采集处理模块的模块信息和模块互连信息，抽象出所述数据获取系统中包含的各种工作流；
基于每种所述工作流的通道数量和工作时间长度，确定每种所述工作流中所传输数据的数据空间信息；
对于每种所述工作流，确定所述工作流的数据处理方式信息以及接口应用信息，所述接口应用信息中包含所述工作流所流经的每个采集处理模块为所述工作流提供的接口的接口信息；基于所述工作流的数据空间信息、所述接口应用信息以及所述数据处理方式信息，确定所述工作流的处理路径中包含的各个数据域，其中，所述数据域为工作流在处理过程中具有相同流数据帧粒度的数据区域，所述数据域的等级随着流数据帧粒度的增大而升高；
对于每种所述工作流，将所述工作流所流经的每个采集处理模块均确定为目标模块，并确定所述工作流的数据域信息，所述数据域信息中包含与所述工作流对应的每个流处理节点所处的数据域的属性信息；基于所述工作流的接口应用信息、数据处理方式信息、数据域信息以及每个所述目标模块的模块信息和模块互连信息，确定与所述工作流对应的每个流处理节点所对应的目标模块，并确定每个所述流处理节点在与其对应的目标模块中的位置信息；
对于每个所述采集处理模块，确定与所述采集处理模块对应的各个流处理节点，基于每个流处理节点的位置信息，生成所述采集处理模块的模块构建信息；
对于每个所述采集处理模块，确定所述采集处理模块的跨模块接口节点，基于所述跨模块接口节点，确定与该采集处理模块存在连接关系的采集处理模块，并将所述采集处理模块与其存在连接关系的采集处理模块相连接；
对于每个所述采集处理模块，根据所述采集处理模块的模块构建信息，确定与所述采集处理模块对应的每个流处理节点的节点信息，基于每个所述流处理节点的节点信息，使用标准化封装后的标准接口将所述采集处理模块的各个流处理节点和跨模块接口节点进行连接，得到与所述采集处理模块对应的模块设计文件，将所述模块设计文件部署至所述采集处理模块中，以完成与所述构建请求对应的数据获取系统的构建。
上述的方法，可选的，所述确定所述采集处理模块的跨模块接口节点，包 括：
确定所述采集处理模块的跨模块接口类型；
在预设的标准跨模块接口节点库中判断是否存在与所述跨模块接口类型对应的标准跨模块接口节点；
若存在与所述跨模块接口类型对应的标准跨模块接口节点，则将与所述跨模块接口类型对应的标准跨模块接口节点作为所述采集处理模块的跨模块接口节点；
若不存在与所述跨模块接口类型对应的标准跨模块接口节点，则基于所述采集处理模块的物理层传输介质和接口信息，构建所述采集处理模块的跨模块接口节点。
上述的方法，可选的，所述确定与所述采集处理模块对应的各个流处理节点，包括：
获取所述采集处理模块的各个节点类型信息；
对于每个所述节点类型信息，在与所述采集处理模块的处理单元类型对应的标准节点库中，确定是否存在与所述节点类型信息对应的标准处理节点；
若存在与所述节点类型信息对应的标准处理节点，则将与所述节点类型信息对应的标准处理节点作为与所述采集处理模块对应的流处理节点；
若未存在与所述节点类型信息对应的标准处理节点，则基于与所述节点类型信息对应的节点信息，构建与所述节点类型信息对应的流处理节点，并将构建的流处理节点作为与所述采集处理模块对应的流处理节点。
上述的方法，可选的，标准接口的标准化封装的过程，包括：
对于所述采集处理模块中的每个数据接口，确定每个所述数据接口所处的采集处理模块的处理单元类型；
确定每个所述数据接口的数据域属性，基于每个所述数据接口的数据域属性，确定每个所述数据接口的流数据帧参数以及流数据帧信息段内容；
对于每个所述数据接口，将所述数据接口的流数据帧参数和流数据帧信息段内容应用于预设的标准流数据帧格式模板，得到所述数据接口的标准流数据帧格式；
基于每个所述数据接口的标准数据接口类型、工作参数以及标准流数据帧 格式，将每个所述数据接口进行标准化封装，得到与每个数据接口对应的标准接口。
上述的方法，可选的，所述基于每个所述流处理节点的节点信息，使用标准化封装后的标准接口将所述采集处理模块的各个流处理节点和跨模块接口节点进行连接，包括：
对每个所述流处理节点的节点信息进行解析，得到每个所述流处理节点的节点类型和连接信息；
对于每个所述流处理节点，基于所述流处理节点的连接信息，确定所述流处理节点的每个端口所对应的目标连接节点的目标端口，所述目标连接节点为与所述流处理节点存在连接关系的流处理节点，所述目标端口为所述目标连接节点中与所述流处理节点连接的端口；
对于每个所述流处理节点中的每个端口，基于所述端口所处的流处理节点的节点类型确定所述端口的连接方式，确定所述端口所对应的目标连接节点与所述端口所处的流处理节点是否均处于同一采集处理模块内；
若所述端口所对应的目标连接节点与所述端口所处的流处理节点未处于同一采集处理模块内，则在标准转换模块中确定与所述端口对应的标准端口，将所述端口和与所述端口对应的标准端口之间的接口进行标准化封装，基于所述端口的数据域属性确定标准转换模块的工作参数后，使用所述标准转换模块应用所述端口的连接方式将所述端口与跨模块接口节点连接，使得所述端口通过所述跨模块接口节点与该端口所对应的目标端口相连接；
若所述端口所对应的目标连接节点与所述端口所处的流处理节点处于同一采集处理模块内，则对所述端口和所述端口所对应的目标端口之间的接口进行标准化封装，以得到标准接口，通过所述标准接口应用所述端口的连接方式，使得所述端口和所述端口所对应的目标端口相连接。
一种数据获取系统的构建装置，包括：
响应单元，用于响应于用户发送的用于构建数据获取系统的构建请求，确定所要构建的数据获取系统中所包含的各个采集处理模块的模块信息和模块互连信息；
抽象单元，用于根据各个所述采集处理模块的模块信息和模块互连信息， 抽象出所述数据获取系统中包含的各种工作流；
第一确定单元，用于基于每种所述工作流的通道数量和工作时间长度，确定每种所述工作流中所传输数据的数据空间信息；
第二确定单元，用于对于每种所述工作流，确定所述工作流的数据处理方式信息以及接口应用信息，所述接口应用信息中包含所述工作流所流经的每个采集处理模块为所述工作流提供的接口的接口信息；基于所述工作流的数据空间信息、所述接口应用信息以及所述数据处理方式信息，确定所述工作流的处理路径中包含的各个数据域，其中，所述数据域为工作流在处理过程中具有相同流数据帧粒度的数据区域，所述数据域的等级随着流数据帧粒度的增大而升高；
第三确定单元，用于对于每种所述工作流，将所述工作流所流经的每个采集处理模块均确定为目标模块，并确定所述工作流的数据域信息，所述数据域信息中包含与所述工作流对应的每个流处理节点所处的数据域的属性信息；基于所述工作流的接口应用信息、数据处理方式信息、数据域信息以及每个所述目标模块的模块信息和模块互连信息，确定与所述工作流对应的每个流处理节点所对应的目标模块，并确定每个所述流处理节点在与其对应的目标模块中的位置信息；
生成单元，用于对于每个所述采集处理模块，确定与所述采集处理模块对应的各个流处理节点，基于每个流处理节点的位置信息，生成所述采集处理模块的模块构建信息；
第四确定单元，用于对于每个所述采集处理模块，确定所述采集处理模块的跨模块接口节点，基于所述跨模块接口节点，确定与该采集处理模块存在连接关系的采集处理模块，并将所述采集处理模块与其存在连接关系的采集处理模块相连接；
连接单元，用于对于每个所述采集处理模块，根据所述采集处理模块的模块构建信息，确定与所述采集处理模块对应的每个流处理节点的节点信息，基于每个所述流处理节点的节点信息，使用标准化封装后的标准接口将所述采集处理模块的各个流处理节点和跨模块接口节点进行连接，得到与所述采集处理模块对应的模块设计文件，将所述模块设计文件部署至所述采集处理模块中， 以完成与所述构建请求对应的数据获取系统的构建。
上述的装置，可选的，所述第四确定单元，包括：
第一确定子单元，用于确定所述采集处理模块的跨模块接口类型；
第一判断子单元，用于在预设的标准跨模块接口节点库中判断是否存在与所述跨模块接口类型对应的标准跨模块接口节点；
第二确定子单元，用于若存在与所述跨模块接口类型对应的标准跨模块接口节点，则将与所述跨模块接口类型对应的标准跨模块接口节点作为所述采集处理模块的跨模块接口节点；
构建子单元，用于若不存在与所述跨模块接口类型对应的标准跨模块接口节点，则基于所述采集处理模块的物理层传输介质和接口信息，构建所述采集处理模块的跨模块接口节点。
上述的装置，可选的，所述生成单元，包括：
获取子单元，用于获取所述采集处理模块的各个节点类型信息；
第二判断子单元，用于对于每个所述节点类型信息，在与所述采集处理模块的处理单元类型对应的标准节点库中，确定是否存在与所述节点类型信息对应的标准处理节点；
第三确定子单元，用于若存在与所述节点类型信息对应的标准处理节点，则将与所述节点类型信息对应的标准处理节点作为与所述采集处理模块对应的流处理节点；
第二构建子单元，用于若未存在与所述节点类型信息对应的标准处理节点，则基于与所述节点类型信息对应的节点信息，构建与所述节点类型信息对应的流处理节点，并将构建的流处理节点作为与所述采集处理模块对应的流处理节点。
上述的装置，可选的，还包括：
第五确定单元，用于对于所述采集处理模块中的每个数据接口，确定每个所述数据接口所处的采集处理模块的处理单元类型；
第六确定单元，用于确定每个所述数据接口的数据域属性，基于每个所述数据接口的数据域属性，确定每个所述数据接口的流数据帧参数以及流数据帧信息段内容；
输入单元，用于对于每个所述数据接口，将所述数据接口的流数据帧参数和流数据帧信息段内容应用于预设的标准流数据帧格式模块，得到所述数据接口的标准流数据帧格式；
获取单元，用于基于每个所述数据接口的标准数据接口类型、工作参数以及标准流数据帧格式，将每个所述数据接口进行标准化封装，得到与每个数据接口对应的标准接口。
上述的装置，可选的，所述连接单元，包括：
解析子单元，用于对每个所述流处理节点的节点信息进行解析，得到每个所述流处理节点的节点类型和连接信息；
第四确定子单元，用于对于每个所述流处理节点，基于所述流处理节点的连接信息，确定所述流处理节点的每个端口所对应的目标连接节点的目标端口，所述目标连接节点为与所述流处理节点存在连接关系的流处理节点，所述目标端口为所述目标连接节点中与所述流处理节点连接的端口；
第三判断子单元，用于对于每个所述流处理节点中的每个端口，基于所述端口所处的流处理节点的节点类型确定所述端口的连接方式，确定所述端口所对应的目标连接节点与所述端口所处的流处理节点是否均处于同一采集处理模块内；
第一连接子单元，用于若所述端口所对应的目标连接节点与所述端口所处的流处理节点未处于同一采集处理模块内，则在标准转换模块中确定与所述端口对应的标准端口，将所述端口和与所述端口对应的标准端口之间的接口进行标准化封装，基于所述端口的数据域属性确定标准转换模块的工作参数后，使用所述标准转换模块应用所述端口的连接方式将所述端口与跨模块接口节点连接，使得所述端口通过所述跨模块接口节点与该端口所对应的目标端口相连接；
第二连接子单元，用于若所述端口所对应的目标连接节点与所述端口所处的流处理节点处于同一采集处理模块内，则对所述端口和所述端口所对应的目标端口之间的接口进行标准化封装，以得到标准接口，通过所述标准接口应用所述端口的连接方式，使得所述端口和所述端口所对应的目标端口相连接。
与现有技术相比，本发明具有以下优点：
本发明提供一种数据获取系统的构建方法及装置，该方法包括：响应于用户发送的用于构建数据获取系统的构建请求，确定与所述构建请求对应的采集处理模块的模块信息及模块互连信息，抽象出数据获取系统中所包含的各种工作流，确定每种工作流中所传输数据的数据空间信息，确定工作流在处理路径中经过的各个数据域，并最终确定每个采集处理模块的模块构建信息。通过跨模块接口节点确定互连关系的采集处理模块。对于每个采集处理模块，使用标准化封装后的标准接口将各个所述流处理节点进行连接或连接到跨模块接口节点，以得到与采集处理模块的模块设计文件。使用FPGA逻辑编译下载、CPU进程运行等手段，将各个模块设计文件中的流处理节点和连接方式部署到所在的采集处理模块，完成整个数据获取系统的搭建工作。应该用本发明提供的方法通过将数据获取系统的工作流程抽象为一系列流的处理，将流处理的过程抽象为一系列流处理节点的连接，使用数据空间和数据域属性描述各个流处理节点的工作参数，由此可以确定用于构建数据获取系统的流处理节点，应用流处理节点快速构建出所需的数据获取系统，构建的数据获取系统中的流处理节点具有复用性，在对系统进行调整或是修改时，无需重新进行设计，节省了大量的时间，并且本发明提供的构建数据系统的构建方法，构建过程简单、不复杂且具有普遍性，专业性不强的人员也可使用本发明提供的方法构建所需的数据获取系统。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据提供的附图获得其他的附图。
图1为本发明实施例提供的一种数据获取系统的构建方法的方法流程图；
图2为本发明实施例提供的一种数据获取系统的构建方法的又一方法流程图；
图3为本发明实施例提供的一种数据获取系统的构建方法的再一方法流程 图；
图4为本发明实施例提供的一种数据获取系统的构建方法的另一方法流程图；
图5为本发明实施例提供的一种流数据帧的流数据帧格式的定义的示例图；
图6为本发明实施例提供的一种多路点到点接口模型的模型示意图；
图7为本发明实施例提供的一种多路点到点接口模型的内部实现框图；
图8为本发明实施例提供的一种数据获取系统的构建方法的又另一方法流程图；
图9为本发明实施例提供的一种索引共享内存的数据格式的实例图；
图10为本发明实施例提供的一种流的数据空间和数据域的关系的示例图；
图11为本发明实施例提供的一种用于构建数据获取系统的采集单元的实现框图；
图12为本发明实施例提供的一种传感器读出节点的模型示意图；
图13为本发明实施例提供的一种用于构建数据获取系统的数据汇总单元的实现框图；
图14为本发明实施例提供的一种用于构建数据获取系统的数据显示记录单元的实现框图；
图15为本发明实施例提供的一种数据获取系统的构建装置的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
在本发明中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一 个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
本发明可用于构建各种数据获取系统的平台或是系统中，本发明可用于构建数据获取系统，应用本发明所构建的数据获取系具有很高的复用性，减少了构建数据获取系统的设计工作量，加快数据获取系统的实现。
本发明提供的方法的执行主体可为用于构建数据获取系统的平台中的服务器或处理器，其中，处理器包含现场可编程逻辑门阵列(Field Programmable GateArray，FPGA)；本发明提供的一种数据获取系统的构建方法的方法流程图具体如图1所示，具体说明如下所述：
S101、响应于用户发送的用于构建数据获取系统的构建请求，确定所要构建的数据获取系统中所包含的各个采集处理模块的模块信息和模块互连信息。
当用户需要构建数据获取系统时，向执行主体发送用于构建数据获取系统的构建请求，执行主体响应于用户发送的用于构建数据获取系统的构建请求，对所述构建请求进行解析，确定所要构建的数据获取系统中所包含的各个采集处理模块的模块信息和模块互连信息。
本发明中所述的采集处理模块是指在数据获取系统中实际工作的硬件模块，包括但不限于用于传感器数据读出的硬件板卡、用于完成数据实时处理功能的FPGA板卡或是含有单片机、CPU或GPU等的其他硬件板卡或计算机等。
本发明中的各个采集处理模块根据功能、位置和连接关系分别从属于某个模块结构层，所有的采集处理模块以层次化的方式进行组织，将具有相同功能和连接方式的同一类型的采集处理模块置于同一个模块结构层。在一个数据获取系统中包含至少一个模块结构层，每个模块接口层中包含至少一个采集处理模块；进一步的，当数据获取系统中存在多个模块结构层时，各个模块结构层按照距离传感器/探测器的远近位置以从近到远的顺序逐层升高。
每个模块结构层仅在其内部各个采集处理模块之间，或其内部采集处理模块到其相邻上下级层级的采集处理模块之间存在直接的数据通道，即相邻的模块结构层之间存在直接的数据通道，数据通道如光纤、双绞线、同轴电缆、无线信号等；不相邻的模块结构层之间不存在直接的数据通道。进一步的，本发明中的采集处理模块的模块互连信息是指采集处理模块所处的模块结构层的 上下级关系和相邻关系，以及采集处理模块所处的模块结构层以及该模块结构层与其他层级的模块结构层中的各个采集处理模块之间的互连方式、连接数量和传输能力等信息。
本发明中的采集处理模块的模块信息包括但不限于采集处理模块的模块类型、接口信息、连接的传感器通道数以及模块处理能力等，其中接口信息中包含但不限于输入接口数量、输出接口数量、输入接口和输出接口的接口类型和数据传输能力。
S102、根据各个所述采集处理模块的模块信息和模块互连信息，抽象出所述数据获取系统中包含的各种工作流。
对所要构建的数据获取系统中的工作流程进行抽象，得到数据获取系统中实际运行的各种流的特征，根据各种流的特征确定所要构建的数据获取系统中实际运行的各种工作流；本发明中的工作流具有多种类型，不同类型的工作流具有不同的功能，工作流包括但不限于数据流、命令流、日志流、状态流以及命令反馈流等。
本发明中的流为具有相同的数据传输方向、相同的处理方式。具备相同数据内容和数据结构的一系列数据通道，将在一定的通道范围内和时间范围内的数据按照一定的组织方式进行组帧，并按照时间顺序进行发送的数据帧的集合。
本发明在对数据获取系统中的工作流程进行抽象时，从数据获取系统的实际设计需求出发，将整个数据获取系统的工作流程抽象出对应的独立的工作流，具体如，将对同一类传感器/探测器的数据及其相应处理方式抽象为数据流和数据流上的各种流处理节点的级联，将对传感器/探测器的参数配置、工作控制等操作抽象为命令流及其处理节点，将对读命令的返回结果抽象为命令反馈流，将各种采集处理模块上的温度、电压传感器的输出抽象为状态流，将系统中的各种工作消息根据紧急程度不同抽象为紧急消息流和日志流等等。
对本发明中抽象出的各种流的特征进行说明，流的特征包括但不限于流的类型、流的数据来源和产生方式、流的传输方向和最终终点、流中的通道数量和数据结构定义、流数据帧传输中实际经过的采集处理模块的种类、在每种采集处理模块中流的输入和输出端口个数、以及对流需要进行的处理方式(如其 中需要的合并或扇出操作的次数和位置、以及其他流向控制、信息提取和数据过滤等操作)等信息。
S103、基于每种所述工作流的通道数量和工作时间长度，确定每种所述工作流中所传输数据的数据空间信息。
本发明中的数据空间为工作流中所有数据可能包含的时间范围和通道范围，其中，时间范围由工作时间长度确定，通道范围可由通道数量进行确定。
S104、对于每种所述工作流，确定所述工作流的数据处理方式信息以及接口应用信息，所述接口应用信息中包含所述工作流所流经的每个采集处理模块为所述工作流提供的接口的接口信息；基于所述工作流的数据空间信息、所述接口应用信息以及所述数据处理方式信息，确定所述工作流的处理路径中包含的各个数据域，其中，所述数据域为工作流在处理过程中具有相同流数据帧粒度的数据区域，所述数据域的等级随着流数据帧粒度的增大而升高。
接口应用信息中包含工作流所流经的每个采集处理模块为该工作流提供的接口的接口信息，其中，采集处理模块为该工作流提供的接口包含输入接口和输出接口，接口信息中包含输入接口数量和输出接口数量。
本发明中的数据域为工作流在处理过程中具有相同流数据帧粒度的数据区域，其中，流数据帧粒度为通道数目和时间范围大小；其中，数据域存在等级，数据域的层级可根据流数据帧粒度的大小进行定义，将流数据帧粒度较小的数据域定义为低级数据域，将流数据帧粒度较大的数据域定义为高级数据域，即数据域的流数据帧粒度越大，数据域的等级越高。
本发明中的工作流在处理过程中至少包含一个数据域，在工作流的处理路径上，往往伴随着多次合并或扇出操作而存在多个数据域，工作流在经过了合并或扇出操作后，流数据帧所在的数据域会发生改变，因此，来自多个端口的低级数据域的数据帧可以通过合并操作产生一个高级数据域的数据帧，同样来自高级数据域的数据帧可以通过扇出操作得到发往多个端口的多个低级数据域的数据帧。进一步的，进行合并操作可通过合并节点实现，进行扇出操作可通过扇出节点实现。
不同的数据域有不同的数据域信息，数据域信息还成为数据域属性，其中，数据域信息由数据域的属性信息组成，属性信息包括但不限于数据域内的数据 组织粒度(通道范围和时间范围大小)、当前数据域在其上级数据域内的通道位置和时间位置偏移、当前数据域内的流数据帧中包含的信息字段以及每一个信息字段的具体格式参数等。
S105、对于每种所述工作流，将所述工作流所流经的每个采集处理模块均确定为目标模块，并确定所述工作流的数据域信息，所述数据域信息中包含与所述工作流对应的每个流处理节点所处的数据域的属性信息；基于所述工作流的接口应用信息、数据处理方式信息、数据域信息以及每个所述目标模块的模块信息和模块互连信息，确定与所述工作流对应的每个流处理节点所对应的目标模块，并确定每个所述流处理节点在与其对应的目标模块中的位置信息。
本发明中的流处理节点为位于各个采集处理模块上，通过不同工作参数配置，进而完成特定基础功能的FPGA逻辑单元或CPU上运行的软件进程。采集处理模块的模块构建信息包括但不限于采集处理模块中运行的流处理节点类型、流处理节点工作参数其连接信息。
本发明中，根据工作流的数据帧所需要的进行的数据处理方式信息，将工作流的数据处理过程抽象为一系列完成合并、扇出、广播、信息提取、过滤等数据处理操作的流处理节点的级联；进一步，工作流在传输处理过程中的数据域会随着经过合并节点或扇出节点而改变，在各个数据域内也会插入当前数据域的粒度进行数据处理操作的其他流处理节点；由于合并节点和扇出节点所在的位置和工作流所经过的采集处理模块信息及其互联信息有关，因此各个工作流的数据域和数据获取系统中的模块结构成的划分有着直接的关联。
对于每种工作流，根据工作流所经过的采集处理模块的模块信息和模块互连信息，将该工作流的各个流处理节点分配至各个模块结构层下，并确定在当前模块结构层内的各个采集处理模块内需要运行的流处理节点的类型、数据域信息及流处理节点的连接关系。
S106、对于每个所述采集处理模块，确定与所述采集处理模块对应的各个流处理节点，基于每个流处理节点的位置信息，生成所述采集处理模块的模块构建信息。
对于每个采集处理模块，确定处于该采集处理模块中的各个流处理节点，并根据每个流处理节点的位置信息，生成该采集处理模块的模块构建信息；其 中位置信息中包含但不限于流处理节点的节点信息和连接信息。
S107、对于每个所述采集处理模块，确定所述采集处理模块的跨模块接口节点，基于所述跨模块接口节点，确定与该采集处理模块存在连接关系的采集处理模块，并将所述采集处理模块与其存在连接关系的采集处理模块相连接。
对于每个采集处理模块，根据采集处理模块的功能信息、模块构建信息、模块互连信息以及接口信息，确定采集处理模块的跨模块接口节点，并通过跨模块接口节点，将与该采集处理模块存在连接关系的采集处理模块相连接。进一步的，采集处理模块的接口信息包含但不限于采集处理模块的输出接口与输入接口的接口类型和接口数量。
采集处理模块的功能信息具体可包含采集处理模块的功能以及该采集处理模块可对数据帧进行处理的操作类型等信息，例如将数据帧进行合并、规格化、解码、编码等操作处理；其中，级联信息中包含该数据处理模块在所要构建的数据获取系统中的具体位置；进一步的，模块互连信息中包含但不限于采集处理模块所要连接的采集处理模块的信息以及采集处理模块中对应的流处理模块的连接信息，可根据模块连接信息确定该采集处理模块所要连接的采集处理模块，并将该采集处理模块所要连接的采集处理模块相连接。
本发明的跨模块接口节点，是一种特殊的流处理节点，跨模块接口节点以FPGA模块或软件进程的方式存在，其功能是在两个采集处理模块之间的数据传输通道的基础上进行封装，从而为两个采集处理模块之间的多个流的传输提供的包含两个方向、多个点到点连接的透明数据通道，并通过标准接口与其他流处理节点进行连接。
跨模块接口节点的具体实现和在两个采集传输模块之间实际使用的数据通道类型有关，任意两个采集传输模块之间均需要构建一对跨模块接口节点(分别位于两个采集处理模块)，如果一个采集传输模块需要同时和多个其他采集处理模块进行连接，则需要构建多组跨模块接口节点。由于两个采集处理模块之间可能有来自两个方向(上行或下行)的多个流通过同一个实际的数据传输通道进行数据传输，因此需要根据各个流的流处理节点在采集处理模块的位置分配信息，设置跨模块接口节点的面向流处理节点端的上行端口输目和下行端口数目。当跨模块接口节点构建完毕中，在所述连接单元中还需要将有互 连关系的采集处理模块之间对应的数据通道进行连接，完成跨模块接口节点的连接。
S108、对于每个所述采集处理模块，根据所述采集处理模块的模块构建信息，确定与所述采集处理模块对应的每个流处理节点的节点信息，基于每个所述流处理节点的节点信息，使用标准化封装后的标准接口将所述采集处理模块的各个流处理节点和跨模块接口节点进行连接，得到与所述采集处理模块对应的模块设计文件，将所述模块设计文件部署至所述采集处理模块中，以完成与所述构建请求对应的数据获取系统的构建。
将模块设计文件部署至采集处理模块中时，可使用FPGA逻辑编译下载、CPU进程运行等手段将模块设计文件部署至采集处理模块中，进一步的，部署模块设计文件的采集处理模块为现实生活中的采集处理模块；在将所有的采集处理模块进行部署后，完成数据获取系统的构建工作。
本发明实施例提供的方法中，响应于用户发送的用于构建数据获取系统的构建请求，确定所要构建的数据获取系统中所包含的各个采集处理模块的模块信息和模块互连信息；根据各个采集处理模块的模块信息和模块互连信息，抽象出数据获取系统中包含的各种工作流；基于每种工作流的通道数量和工作时间长度，确定每种工作流中传输数据的数据空间信息；对于每种工作流，确定工作流的数据处理方式以及接口应用信息，所述接口应用信息中包含工作流所流经的每个采集处理模块为工作流提供的接口的接口信息；基于工作流的数据空间信息、接口应用信息以及数据处理方式信息，确定工作流的处理路径中包含的各个数据域；对于每种工作流，将工作流所流经的每个采集处理模块均确定为目标模块，以及确定工作流的数据域信息；根据工作流的接口应用信息、数据处理方式信息、数据域信息以及每个目标模块的模块信息和模块互连信息，确定与工作流对应的每个流处理节点所对应的目标模块，并确定每个流处理节点在与其对应的目标模块中的位置信息；对于每个采集处理模块，确定与该采集处理模块对应的各个流处理节点，基于每个流处理节点的位置信息，生成采集处理模块的模块构建信息；确定采集处理模块的块模块接口节点，基于跨模块接口节点，确定与该采集处理模块存在连接关系的采集处理模块，并将该采集处理模块与其存在连接关系的采集处理模块相连接；根据采集处理模块 的模块构建信息，确定与采集处理模块对应的每个流处理节点的节点信息，基于每个流处理节点的节点信息，使用标准化封装后的标准接口将采集处理模块的各个流处理节点和跨模块接口节点进行连接，得到与采集处理模块对应的模块设计文件，并将该模块设计文件部署至采集处理模块中，进而完成数据获取系统的构建。应用本发明，响应于用户发送的用于构建数据获取系统的构建请求，确定与构建请求对应的采集处理模块的模块信息和模块互连信息，抽象出数据获取系统中的各个工作流，基于每种工作流中所传输的数据空间信息，确定每种工作流的处理路径中的数据域信息，最终确定每个采集处理模块的模块构建信息；基于模块构建信息和跨模块接口节点将存在连接关系的采集处理模块相连接；将每个采集处理模块中的流处理节点和跨模块接口节点使用标准化封装后的标准接口进行连接，得到采集处理模块的模块设计文件，并将模块设计文件部署至采集处理模块中，完成数据获取系统的构建。本发明使用流处理节点构建数据获取系统，无需对每个功能模块进行设计，构建的数据获取系统中的流处理节点具有复用性，在对系统进行调整或是修改时，无需重新进行设计，节省了大量的时间，并且本发明提供的构建数据系统的构建方法，构建过程简单、不复杂且具有普遍性，降低了构建数据获取系统的难度，使得专业性不强的人员也可使用本发明提供的方法构建所需的数据获取系统。
参照图2，为本发明实施例提供的确定采集处理模块的跨模块接口节点的方法流程图，具体说明如下所述：
S201、确定所述采集处理模块的跨模块接口类型。
基于采集处理模块的物理层传输介质和接口类型，确定采集处理模块的跨模块接口类型，跨模块接口类型用于表征采集处理模块所需要的跨模块接口节点的类型。
S202、在预设的标准跨模块接口节点库中判断是否存在与所述跨模块接口类型对应的标准跨模块接口节点；若存在与所述跨模块接口类型对应的标准跨模块接口节点，则执行S203；若不存在与所述快模块接口类型对应的标准跨模块接口节点，则执行S204。
本发明实施例提供的方法中，标准跨模块接口节点库用于保存标准跨模块 接口节点；本发明提供的方法中，无论采集处理模块之间的传输接口的物理层、链路层和传输层为何种方式，均将采集处理模块之间的传输接口都抽象为统一的模型，即跨模块接口节点的形式，其具体特征为：1、跨模块接口节点总是成对出现，分别位于有互连关系的两个采集处理模块上；2、每两个有互连关系的采集处理模块之间均包含一对跨模块接口节点；3、一对跨模块接口节点中可能具有多个不同方向的流传输通道；4、各个流传输通道之间的工作相互独立；5、跨模块接口节点中的每个流传输通道对其中传输的流数据帧来说是“透明”的，即对每一个流传输通道中传输的流数据帧，在其经过一对跨模块接口节点后，维持原有的接口方式和流数据帧格式不改变；6、跨模块接口节点中的端口使用相同的接口。
S203、将与所述跨模块接口类型对应的标准跨模块接口节点作为所述采集处理模块的跨模块接口节点。
将与跨模块接口类型对应的标准跨模块接口节点作为采集处理模块的跨模块接口节点，并为该跨模块接口节点配置工作参数，使得跨模块接口节点可以根据工作参数进行工作。
进一步的，可对采集处理模块的功能信息、模块构建信息、模块互连信息以及端口应用信息进行解析，获得采集处理模块的跨模块接口节点信息，所述跨模块接口节点信息中包含节点位置和工作参数，可将获得的工作参数为跨模块接口节点进行配置，或是将工作参数配置至与跨模块接口类型对应的标准跨模块接口节点中，并将配置完工作参数的标准跨模块接口节点作为采集处理模块的跨模块接口节点。
S204、基于所述采集处理模块的物理层传输介质和接口信息，构建所述采集处理模块的跨模块接口节点。
当标准跨模块接口节点库中不存在与跨模块接口类型对应的标准跨模块接口节点时，根据采集处理模块的物理层传输介质和接口信息，构建与跨模块接口类型对应的跨模块接口节点，并将构建的跨模块接口节点作为标准跨模块接口节点保存至标准跨模块接口节点库中；进一步的，在将构建的跨模块接口节点作为采集处理模块的跨模块接口节点后，可采集处理模块的跨模块接口节点配置工作参数，使得采集处理模块的跨模块接口节点根据工作参数进行工 作。
本发明中的跨模块接口节点根据在设计时使用的物理层传输介质和物力接口的不同，使用光纤、网线、双绞线、同轴电缆、计算机总线等连接与该节点具有连接关系的采集处理模块。
参照图3，为本发明实施例提供的确定采集处理模块对应的各个流处理节点的方法流程图，具体说明如下所述：
S301、获取所述采集处理模块的各个节点类型信息。
对采集处理模块的模块构建信息进行解析，以得到模块构建信息中所包含的各个节点类型信息，其中，每个节点类型信息对应一个流处理节点，节点类型信息中包含流处理节点的节点类型和工作参数信息。
S302、对于每个所述节点类型信息，在与所述采集处理模块的处理单元类型对应的标准节点库中，确定是否存在与所述节点类型信息对应的标准处理节点；若存在与所述节点类型信息对应的标准处理节点，则执行S303；若未存在与所述节点类型信息对应的标准处理节点，则执行S304。
采集处理模块的处理单元类型包括但不限于FPGA类型和CPU类型，不同的处理单元类型对应不同的标准节点库。
标准节点库中保存多个标准处理节点，其中，标准节点库中的标准处理节点既有传统的流处理系统中常用的一些流向控制方面的节点，也有本方案特有的与数据获取过程相对应的一系列标准处理节点，本发明中特有的标准处理节点均具有以下特点：1)、节点中的接口均为标准化封装后的标准接口；2)节点的功能均涉及和标准化接口协议定义有关的数据操作；3)均是通过对数据获取系统中常见的基本数据处理过程的抽象，从而使得可以用有限种类的标准流处理接地那涵盖大部分数据获取系统中的数据处理操作。
在确定标准节点库中是否存在与节点类型信息对应的标准处理节点时，可将节点类型信息遍历标准节点库中的各个标准处理节点，进而判断标准节点库中是否存在与节点类型信息对应的标准处理节点。
对标准节点库中包含的标准处理节点进行举例说明，具体如下所述：
1)、数据帧规格化节点(Regularizer)，其特点为：节点的输入、输出端 口均位于同一个数据域下，具有多个输入端口和一个输出端口。输出端口的输出为对所有输入端口输入的具有相同时间坐标的数据帧按照空间坐标依次发送，保持数据帧内容不变，事实上完成了对各个数据帧的空间排序；
2)、数据帧按时间/空间分发节点(Map_T，Map_S)，其特点为：节点的输入、输出端口均位于同一个数据域下，具有一个输入端口和多个输出端口。在输入端口到来的每一个数据帧，节点根据其上级数据域时间偏移地址信息(按时间分发)或空间偏移地址信息(按空间分发)，选择一个确定的输出端口输出，事实上完成了各个数据帧按照简单的哈希表达式(求模)进行的并行化操作。
3)、数据合并节点(Merge)，其特点在于：节点的输入端口位于低级数据域内，包含了上级数据域的所有子数据域入口(可以是多个输入端口，也可以是经过Regularizer节点排序后的一个输入端口)，输出端口位于上级数据域中。在节点内完成由多个低级数据域的数据帧合并出上级数据域数据帧的操作，基本实现算法为硬件或软件的桶装排序算法(对稠密数据组织情况)或归并排序(对稀疏数据组织情况)，算法实现参数由两个数据域的属性决定；
4)、数据分发节点(Map)，其功能刚好与Merge节点相反，其特点在于：节点的输入端口位于上级数据域内，输出端口分别连接到各个子数据域。节点通过数据帧中的空间地址信息决定数据帧的路由(输出端口位置)，将输入的数据帧发送到对应的输出端口。请注意其功能与Map_T、Map_S节点的不同。
5)、数据特征提取节点(Feature extractor)，这是一种以过滤器方式存在的流数据处理节点，输入为一个数据流，输出为一个状态流。其特点在于维护一个一维数组，数组长度与所在数据域的空间范围相同，用于存储对应空间坐标的数据特征，对于流经的数据流中的每一个数据，都和对应通道的数组存储进行一个二操作数操作，操作结果作为新的数组取值存入数组。可选的二操作数包括：替换(用于保存每个通道的最新数据更新)、数值求和(用于保存某通道的累计能量)、加1操作(用于保存某通道的累计数据个数)等。数组的数据作为状态流的起点，可以用于系统运行状态的检测；
6)、触发节点(Trigger)，这是一种以过滤器方式存在的流处理节点，其输入为一个数据流接口，一个命令流接口(或外部触发信号线)，输出为一个数 据流接口。工作时要求命令流以数据流当前数据域时间宽度为间隔定时发送触发命令帧，在节点内会接收触发命令帧，当触发命令帧为非空时(或触发信号线有有效信号时)，选择当前触发命令流中的时间戳(或触发时刻)前后的确定时间范围(时间窗口)内的数据帧通过，用于实现数据获取系统中的触发判选操作。
7)、命令分发节点(Map_CMD)，位于FPGA物理节点，其主要功能为将接收到的命令转发至命令对象接收所在的路径；由命令流的广播节点、对其路径进行判断的过滤器节点构成和相应的编码器/译码器构成；输入为AXIS接口，输出为到下级节点的AXIS接口和到本地节点SDMF接口。
8)、命令反馈流合并节点(Reduce_CMD_FB)，位于FPGA物理节点，其主要功能为汇总本地和后级的命令反馈流数据帧并向上级转发，由命令反馈流的复用器和相应的编码器/解码器构成。输入接口为来自下级物理节点的AXIS接口和来自本地节点的SDMF接口，输出接口为发往上级物理节点的AXIS接口。
9)、快照节点(Snapshot)，位于软件节点，其主要功能是对一个流的输入数据帧保存一个最新的数据帧副本，供后端的监测系统和数据分析系统使用。
进一步的，在对各个标准处理节点描述中，所提及的输入端口和输出端口均为使用接口实现连接组件。
本发明实施例提供的方法中，标准节点库中包含的标准处理节点并不局限于上述举例的标准处理节点，还可以包含在FPGA内部用于AXIS接口和SDMF接口之间进行接口转换的编码/解码节点(decoder/encoder)、用于在软件进程间完成从字符型设备到SDMS接口之间转换的发送/接收节点(Transmit/Receive)、用于实现数据存储的存储节点(Save)，和对标准协议帧进行实时刷新显示的显示节点(Display)、用于软件进程、共享内存和任务队列管理的进程管理节点(ProcessKeeper)、用于流向控制的各种节点，如流的广播(Broadcast)、多路复用/解复用(Mux/Demux)、多路选择切换(Switcher)等，用于数据缓存的FIFO，vFIFO(使用DDR构建的虚拟FIFO)等。
本发明实施例提供的方法中，各个标准处理节点都与所要构建的数据获取 系统所需要执行的数据处理任务相关，各个标准处理节点均为标准化的流处理节点，使用标准处理节点构建的数据获取系统，可以以统一的方式完成数据信息提取、事例触发判断、事例组装(数据合并)等常见的在线数据处理。
S303、将与所述节点类型信息对应的标准处理节点作为与所述采集处理模块对应的流处理节点。
本发明实施例提供的方法中，将与节点类型信息对应的标准处理节点作为与所述采集处理模块对应的流处理节点，进一步的，可将节点类型信息中的工作参数信息作为该流处理节点的工作参数，以使该流处理节点基于工作参数进行工作。
S304、基于与所述节点类型信息对应的节点信息，构建与所述节点类型信息对应的流处理节点，并将构建的流处理节点作为与所述采集处理模块对应的流处理节点。
在确定标准节点库中不存在与节点类型信息对应的标准处理节点时，确定节点类型信息对应的节点信息，并根据节点信息构建与节点类型信息对应的流处理节点，将节点类型信息中的工作参数信息配置为流处理节点的工作参数，并将配置后的流处理节点作为与采集处理模块对应的流处理节点；其中，节点信息中包含所要构建的流处理节点的节点类型、节点功能等信息。进一步的，在构建出流处理节点后，可将流处理节点作为标流准处理节点保存在标准节点库中。
本发明实施例提供的方法中，在构建数据获取系统的过程中，可以直接使用标准节点库中的标准处理节点，标准节点库中不存在所需的标准处理节点时，可直接构建所需的标准处理节点，其构建简单易懂，具有极大的便利性，由此可以进一步提高构建数据处理模块的实用性和灵活性，并且，构建的标准处理节点具有复用性，无需重复多次构建相同的节点，进而提高了构建数据处理系统的效率，简化了构建数据获取系统的流程。
此处对采集处理模块中标准接口的标准化封装的过程进行说明，具体流程可参照图4，具体说明如下所述：
S401、对于所述采集处理模块中的每个数据接口，确定每个所述数据接口 所处的采集处理模块的处理单元类型。
采集处理模块的处理单元类型包括但不限于FPGA类型和CPU类型。
S402、确定每个所述数据接口的数据域属性，基于每个所述数据接口的数据域属性，确定每个所述数据接口的流数据帧参数以及流数据帧信息段内容。
在确定数据接口的数据域属性时，可根据数据接口的两端端口确定数据域属性，并根据确定的数据域属性，确定流数据帧参数以及流数据帧信息段内容。
流数据帧参数包括但不限于与采集处理模块对应的数据空间的属性信息以及数据接口所对应的数据域的属性信息；进一步的，这些数据接口的流数据帧参数决定了所要构建的数据获取系统的流数据空间的时间和空间尺度、流数据空间下的元数据的具体格式和信息提取方式、流数据帧内的各个信息段的具体长度、元数据的组织方式等；其中，每个数据接口的流数据帧参数还决定了该数据接口传输的流数据帧中的数据块，以及和该数据接口相关联的数据接口所传输的流数据帧中的数据块之间的映射关系。
对流数据帧信息段进行说明，流数据帧信息段包括但不限于：数据帧头(Stream Frame Head)、数据帧长度(Stream Frame Length)、父数据域起始时间坐标(Father Domain Start Time Index，当前数据域在上级数据域中的时间偏移地址，)、父数据域起始空间坐标(Father Domain Start Space Index，当前数据域在上级数据域中的空间偏移地址)、当前数据帧内包含的数据块个数(Block Number)、每个数据块的属性(Block Properties)、各个数据块的数据净荷(Block Data)以及预留的帧尾(Stream Frame Tail)和带外数据(Outband Data，用户自定义信息字段)等内容；其中流数据帧头(Stream Frame Head)中包含但不限于：流ID、数据域编号、起始停止标准、空/非空标志等信息；所述数据块属性(Block Properties)包括但不限于：当前数据块在当前数据域内的起始时间地址(Start Time Index)和起始空间地址(Start Space Index)，当前数据块的时间地址长度(Time Index Length)和空间地址长度(Space Index Length)，数据块长度(Block Length)等信息。
S403、对于每个所述数据接口，将所述数据接口的流数据帧参数和流数据帧信息段内容应用于预设的标准流数据帧格式模板，得到所述数据接口的标准流数据帧格式。
本发明实施例提供的方法中，基于数据接口的流数据帧参数以及流数据帧信息段，可将流数据帧参数和流数据段内容应用于预设的标准流数据帧格式模板，从而确定数据接口所传输的流数据帧的流数据帧格式，由此可对数据接口的流数据帧的数据结构进行定义。
流数据帧的流数据帧格式的定义中包含流数据帧格式中关于流数据帧信息段的定义、流数据帧信息段中关于数据块属性的定义以及流数据帧信息段中关于数据块的数据净荷的定义；具体的，流数帧的流数据帧格式的定义的内容包含数据帧头、数据帧长度、父数据域起始时间坐标、父数据域起始空间坐标、当前数据帧的数据块个数、数据块属性、数据块的数据净荷、带外数据、数据帧尾等。其中数据块属性可能包括当前数据块在当前数据域内的起始时间地址、当前数据块在当前数据域内的起始空间地址、当前数据块的时间地址长度、当前数据块的空间地址长度、数据块长度等数据数组以及数据等内容。数据块属性及其数据净荷的组织方式由不同的数据块类型决定。
参照图5，为本发明实施例提供的一种流数据帧的流数据帧格式的定义的示例图，换言之，图5也可称为流数据帧的标准协议帧格式的定义的示例图，如图所示，标准协议帧502由数据帧头、数据帧长度、父数据域起始时间坐标、父数据域起始空间坐标、数据块个数、带外数据、数据帧尾、多个数据块属性及其数据净荷组成，其中，数据块属性和数据净荷成对存在。
根据流描述的数据空间的具体特征，可以将数据块分为四种可能的类型，分别为“数据宽度固定、数据个数固定”类型、“数据宽度固定、数据个数变化”类型、“数据宽度变化”类型以及“子数据帧”类型；每种类型的数据块属性及其对应的数据净荷的结构定义如图5中的501和503所示。
“数据宽度固定、数据个数固定”类型代表的工作场景为：每个通道在每个时刻对应的数据具有固定的长度，由当前数据域内的一个确定长度的连续通道范围内的所有通道，在一个确定长度的时间范围内连续输出每一个时刻的数据构成数据块内的内容。此时数据净荷中包含确定个数的元数据，通过数据矩阵的方式进行组织，即按照通道顺序依次输出每个通道在有效时间范围内的每个元数据，所有的元数据依靠其在数据矩阵中的偏移位置来确定其在数据域内的时间坐标和空间坐标，而不需要显性地传输每一个数据的时间坐标和空间坐 标信息。此时数据块属性可以用起始时间地址、时间地址长度、起始空间地址和空间地址长度来定义。
“数据宽度固定、数据个数变化”类型代表的工作场景为：每个通道在每个时刻对应的数据具有固定的宽度，但是在当前数据域的时间和空间范围内会有随机个数的通道在随机时刻输出数据。此时将数据域中的所有数据分成一个或多个数据块传输，每个数据块的数据净荷中包含按照通道和时间顺序依次输出的每个元数据，每个元数据由当前产生数据的通道在当前数据块内的空间地址、对应当前数据的时刻在当前数据块内的时间地址、以及数据内容拼接构成，每个元数据也具有一个确定的宽度。此时数据块的属性可以用当前块在数据域内的起始时间地址、起始空间地址以及数据块内的数据净荷总长度(数据块长度)来定义。
“数据宽度变化”类型代表的工作场景为：某个通道在某个时刻可能会有可变宽度的数据产生。此时将一个数据域对应的时空范围中的每个这样的数据作为一个单独的块处理，数据净荷为这一个变长数据，数据块的属性可以用当前数据在数据域内的起始时间地址、起始空间地址和数据块长度(即当前数据的宽度)来定义。
“子数据帧”类型代表的工作场景为：每一个数据块的数据净荷为其下级数据域内的一个完整的数据帧(子数据帧)，此时数据块属性中仅仅包含当前子数据帧的长度信息(数据块长度)，每个子数据帧在当前数据域内的时间地址偏移和空间地址偏移可以用子数据帧内部的父数据域起始时间坐标和父数据域起始空间坐标来描述。
进一步进行说明，数据接口所传输的流数据帧中是否包含某个信息段、已经包含的信息段的具体长度、数据块的具体组织方式等均有数据帧参数决定；其中，在同一个数据域下的流处理节点的数据接口之间所传输的流数据帧均使用相同的流数据帧格式，即在同一数据域下的数据接口之间所传输的流数据帧均采用相同的数据结构。
进一步的，随着流处理节点之间的数据接口的不同，流数据帧可能以串行的帧方式流动，而流数据帧的内部的信息段也可能以并行的方式存在于流处理 节点的数据接口上。
S404、基于每个所述数据接口的标准数据接口类型、工作参数以及标准流数据帧格式，将每个所述数据接口进行标准化封装，得到与每个数据接口对应的标准接口。
本发明通过将数据接口进行标准化封装进而得到标准接口，通过应用标准接口，使得所要构建的数据获取系统中所处理的数据帧具有标准的传输形式和处理方式。
本发明实施例提供的方法中，标准数据接口类型具体包含以下几种类型：
1)、AXI4-Stream接口(简称为AXIS接口)，其中，该接口在FPGA内部，在流处理节点与外部接口的链路层接口之间进行数据传输时所采用的接口，用于传输标准的流数据帧；
2)、Standard D-Matrix FPGAinterface接口(简称为SDMF接口)，其中，该接口在FPGA内部，在两个流处理节点之间进行数据传输时所用的接口，该接口为自定义接口，其基本思想为在AXIS接口上进行封装，满足最快可以在一个时钟节拍处理一个数据的同时，将标准的流数据帧中的流数据帧信息段作为伴随数据的user数据段并行传输，以提高数据的并行处理能力；同时增加额外的信号用于传输在数据获取系统中为保证数据驱动而设计的空数据帧；同时允许一个数据帧内包含多个数据块结构。
3)、文件描述符接口，该接口在计算机内部，该接口实质为软件类接口，该接口为在流处理节点与外部通信接口(驱动程序)之间进行数据传输时所用的接口，该通常采用标准的字符型设备的文件描述符(类似socket，管道和FIFO)来实现，以符合操作系统内的一般做法；
4)、Standard D-Matrix Software interface(简称为SDMS接口)，该接口在计算机内部，该接口为流处理节点之间进行数据传输时所用于的接口，该接口为自定义接口，其基本设计思想为任务队列+共享内存型的接口，将各个流处理节点设计为计算机内部进程的方式，使用共享内存完成数据交换，使用任务队列负责进程之间的流数据帧处理任务传递，以减小不必要的数据复制开销。
本发明实施例提供的方法中，上述的四种类型的数据接口中，除了与流跨界点传输有关的流处理节点外，主要负责数据处理的流处理节点的各个数据接 口都采用SDMF接口或SDMS接口。
本发明实施例提供的方法中，对SDMF接口在实际应用的过程中涉及的信号的定义进行说明，具体如表1所示：
Figure PCTCN2021099995-appb-000001
Figure PCTCN2021099995-appb-000002
Figure PCTCN2021099995-appb-000003
Figure PCTCN2021099995-appb-000004
表1
其中，SDMF接口在传输数据帧时，数据帧有非空数据帧与空数据帧两种情形，而SDMF接口传输非空数据帧与传输空数据帧时的工作时序是不同。
本发明实施例提供的方法中，在对数据接口进行标准化封装时，需要将与数据接口的接口类型所对应的接口模型封装至数据接口中，以完成数据接口的标准化封装，得到与数据接口对应的标准接口；其中，封装至数据接口的接口模型为多路点到点接口模型。
对多路点到点接口模型进行说明，多路点到点接口模型的模型示意图如图6所示，多路点到点接口模型中包含上行传输层和下行传输层，上行传输层中包含过个上行传输通道，下行传输层中同样也包含多个下行传输通道。在该多 路点到点模型下，数据接口中传输的每一个流，在模型中都表现为一对透明的输入/输出接口对，各个流之间从逻辑上彼此独立，其中，数据接口中传输的每个流对应一个数据传输通道。通过在数据接口中封装多路点到点模型，除了保证传输的正确性、各个流具备合理的调度机制外，还要求各个流之间通过此数据接口具备阻塞特性，即当数据接收端不能接收数据(阻塞)时，应通过适当的数据缓存和通知机制使得发送端停止发送，直到阻塞状态结束为止。此外，如果系统在某些流有数据压缩等方面的需求，也通过在发送端和接收端加入成对出现的压缩/解压缩模块来实现。
本发明实施例提供的方法中，为了方便多种不同的流复用同一物理通道进行数据传输，本发明中将各种不同的接口封装为同样的模型，从而将数据获取系统中的数据传输过程和数据处理过程分离。
本发明实施例提供的方法中，通过对流处理节点的每个数据接口进行预处理，以对每个数据接口的接口进行定义以及数据接口所传输的流数据帧的格式进行定义，使得具有相同的接口定义和流数据帧的格式定义的数据接口所传输的数据帧具有相同的特性，使得这样的数据接口可以相互连接，使得在使用流处理节点构建数据处理模块时的灵活性更高。
在实际应用中，多路点对点接口模型根据实际数据接口的情况添加不同的设计，本发明中，所构建的数据获取系统中上行信道(数据流/状态流/报错流)数据率远远大于下行信道(命令流)中的数据率，在下行方向仅仅进行简单地数据缓存，不考虑下行数据阻塞时的出错处理；在上行方向中，通过增加成对出现的数据反压通知/数据反压响应节点，结合数据缓存实现上行信道中各个流的阻塞特性。同时根据各个流的具体传输需求不同，选择性的添加数据帧校验码产生/数据帧校验码检查、数据帧拆分/重组、数据压缩/解压缩、通道仲裁/分发等节点。基于上述的内容，本发明提供一种多路点到点接口模型的内部实现框图，具体如图7所示，图中所示的是在一个仅仅包含基本物理层/链路层接口的光纤信道上的模型实现框图，图中包含多个组件，其中，数据压缩和数据解压缩为可选组件，在不同的数据传输层选用不同的组件。图中的各个组件的接口均为统一的AXIS接口，通过选择性的将组件添加在不同的传输路径上，从而为不同流的数据传输提供多种标准化的组件，最终保证了跨物理节点 之间的透明连接。图中均采用统一的标准的AXIS接口，因此对于在构建数据获取系统中可能用到的不同接口(光纤、差分电缆、网口等)，均可以通过替换其中用到的物理层和链路层模块实现对不同接口的支持，从而不影响对数据获取系统的其他部分的设计。
在构建数据获取系统的过程中，需要将采集处理模块所对应的各个流处理节点和跨模块接口节点进行连接，具体流程图可参照图8，针对图8的说明如下所述：
S801、对每个所述流处理节点的节点信息进行解析，得到每个所述流处理节点的节点类型和连接信息。
节点信息是对采集处理模块的模块构建信息进行解析得到的，节点信息中包含流处理节点的节点类型、工作参数以及连接信息等信息。
S802、对于每个所述流处理节点，基于所述流处理节点的连接信息，确定所述流处理节点的每个端口所对应的目标连接节点的目标端口，所述目标连接节点为与所述流处理节点存在连接关系的流处理节点，所述目标端口为所述目标连接节点中与所述流处理节点连接的端口。
S803、对于每个所述流处理节点中的每个端口，基于所述端口所处的流处理节点的节点类型确定所述端口的连接方式，确定所述端口所对应的目标连接节点与所述端口所处的流处理节点是否均处于同一采集处理模块内；若所述端口所对应的目标连接节点与所述端口所处的流处理节点未处于同一采集模块内，则执行S804；若所述端口所对应的目标连接节点与所述端口所处的流处理节点处于同一采集处理模块内，则执行S805。
针对不同类型的流处理节点提供不同的连接方式，其中，流处理节点的节点类型可分为两种，一种是以FPGA模块形式存在的流处理节点，另一种是以软件进程形式存在的流处理节点。
以FPGA模块形式存在的流处理节点的端口的连接方式是生成一个FPGA顶层设计文件，在FPGA顶层设计文件中使用信号直接连接需要连接的FPGA模块形式的流处理节点，最终得到一个完整的顶层设计文件。
以软件进程形式存在的流处理节点的连接方式是使用进程间通讯的方式，通过在需要连接的流处理节点中引用相同的共享资源，如共享内存、信号量或消息队列等的形式完成连接。
软件进程形式的流处理节点之间通过SDMS接口连接，SDMS接口使用共享内存作为数据存储的容器，使用标准消息队列作为节点间任务传递的通道。同一物理节点内部不同进程通过访问同一片内存中的数据帧，实现数据交互，可以减少数据在物理节点内部流动时所带来的复制开销。在共享内存管理采用内存池的管理方式，物理节点初始化时首先申请一大片连续内存，并分成key_shm和aux_shm两部分，各节点使用类似内核malloc分配内存的申请方式从内存池中申请共享内存使用。共享内存池分为如下两个子池：1)数据共享内存key_shm，用于存储各个流中标准数据帧；2)索引共享内存aux_shm，用于存储一个数据帧的索引信息。
本发明中的索引贡献内存的数据格式包含数据帧的总体描述信息、数据块列表以及通道列表；其中，数据块列表中包含至少一个数据块，通道列表中包含至少一个通道。本发明中的索引贡献内存还包含FrameDescriptor结构体，BlockDescriptor结构体以及Struct Channel Descriptor结构体；其中，FrameDescriptor结构体用于保存对于一个数据帧的总体描述信息；BlockDescriptor结构体用于保存对数据块的描述信息。
进一步的，关于索引共享内存的数据格式如图9所示，参照图9，索引共内存的数据格式由帧描述符901、块描述符链表902以及通道描述符链表903组成，其中，块描述符链表902中包含4个数据块的描述符，分别为数据块1描述符、数据块2描述符、数据块3描述符以及数据块4描述符；通道描述符链表903中包含每个通道的多个描述符，具体为每个通道有两个描述符，如图具体包含通道1的1号描述符和2号描述符，通达2的1号描述符和2号描述符。
进一步的，帧描述符901由FrameDescriptor结构体904构成，FrameDescriptor结构体904用编码编写得到，FrameDescriptor结构体904的编码内容如下所示：
Figure PCTCN2021099995-appb-000005
Figure PCTCN2021099995-appb-000006
块描述符链路表中的数据块的描述符由BlockDescriptor结构体905构成，BlockDescriptor结构体905使用编码编写定义而成，以数据块2描述符中的BlockDescriptor结构体905进行示例说明，BlockDescriptor结构体905的编码内容如下所示：
Figure PCTCN2021099995-appb-000007
通道描述链表中的通道描述符由ChannelDescriptor结构体903构成，ChannelDescriptor结构体903由编码编写定义而成，以通道描述链路表中的通道1的2号描述符中的ChannelDescriptor结构体903进行示例性的说明，ChannelDescriptor结构体903的编码内容如下所示：
Figure PCTCN2021099995-appb-000008
Figure PCTCN2021099995-appb-000009
以上内容为基于图9对索引共享内存的数据格式进行说明的内容。
进一步的，节点间传输接口采用消息队列，队列底层实现方式可以同样是基于共享内存和同步原语(信号量等)的队列，也可以采用采用boost.mqueue。接口处是标准的单生产者单消费者模型，前一节点将FrameDesc起始地址的aux_shm_addr类型的task投入队列，后续节点从队列中取出task，访问aux_shm中FrameDesc和BlockDesc完成进一步的数据帧解析。
S804、在标准转换模块中确定与所述端口对应的标准端口，将所述端口和与所述端口对应的标准端口之间的接口进行标准化封装，基于所述端口的数据域属性确定标准转换模块的工作参数后，使用所述标准转换模块应用所述端口的连接方式将所述端口与跨模块接口节点连接，使得所述端口通过所述跨模块接口节点与该端口所对应的目标端口相连接。
S805、对所述端口和所述端口所对应的目标端口之间的接口进行标准化封装，以得到标准接口，通过所述标准接口应用所述端口的连接方式，使得所述端口和所述端口所对应的目标端口相连接。
本发明中的流处理节点的端口通过调用标准化封装的标准接口与和该端口存在连接关系的端口进行连接，使得流处理节点可与和该流处理节点存在连接关系的流处理节点进行连接；本发明中的端口与端口相连时，端口中需采用同种类型的标准接口。
本发明实施例提供的方法中，以构建一个用于海上时移地震的数据获取系统为例进行说明，其中，所要构建的海上时移地震的数据获取系统的数据处理模块有三部分，分别为水下拖缆系统、数据汇总单元和数据显示记录单元。
当接收到用户发送的用于构建数据获取系统的构建请求时，响应于该构建 请求，其中，该构建请求用于构建海上时移地震的数据获取系统。确定与构建请求对应的采集处理模块，其中，采集处理模块可为构建数据获取系统的基本模块，该模块用于采集电信号，其中，采集处理模块可以为探测器系统，进一步的，此处的探测器系统可称为流数据源模块，探测器系统有不同的组织和连接关系，往往会在空间上表现出不同的层次关系，不同的层次下具有不同的组织粒度；例如：某探测器系统中一个前端电子学芯片负责读出32个通道的数据，一个前端电子学插件中包含4个这样的芯片(128通道/插件)，一个机箱中包含8个前端电子学插件(1024通道/机箱)，整个子探测器系统可能包含8个机箱(8192通道/系统)。而流数据源模块除了在空间上表现出不同的层次外，基于流数据源模块的空间的层次关系，采集的时间范围也有不同的层次关系；流数据源模块将这些层次关系反应到数据组织中，使得流数据源模块采集的数据流具有相关的层次关系的数据空间，其中，数据空间中存在具有嵌套层次的数据域，每个数据域代表了不同是数据空间范围和数据时间组织粒度，每个数据域内的数据均有着自己的时间空间范围，定义为数据域空间。数据域空间的引入主要是为了通过减少数据关联的时间和空间信息段大小，从而达到压缩数据率的目的。数据域的划分和流数据源模块的组织、信息处理的时间尺度等物理因素有关。
参考图10，为本发明提供的流数据源模块所采集的电子信号所形成的数据流中的数据空间和数据域的关系的一示例图，图中的1001为元数据，图中的1002、1003以及1004均为数据域；图中共有8个数据域1002；2个数据域1003，一个数据域1004；其中，各个元数据1001构成第一层级的数据层1；8个数据域1002构成第二层级的数据层2；2个数据域1003构成第三层级的数据层3；一个数据域1004构成第三层级的数据层3；其中，数据层1的层级低于数据层2的层级，数据层2的层级低于数据层3的层级；如图，每个数据域1002中包含8个元数据，每个数据域1002中包含的元数据是不相同的。如图10可知，流数据源模块的数据空间和数据域存在以下特点：
a)每个数据域空间均由一个(最底层数据域)或多个子数据域空间拼接而成；
b)子数据域空间必完全包含于一个更高层次的数据域内，不允许子数据域 空间同时包含在多个同层的上级数据域内；
c)不允许一个子数据域中的数据拆分后分别位于多个同层的上级数据域内。当需要进行上述操作时，应通过流过滤器生成一个新的流数据空间来实现；
d)父数据域空间由子数据域空间的拼接是二维的，即子数据域空间可能在时间和空间两个维度上的粒度都与父数据域不同。原则上，父数据域在时间和空间维度上包含的子数据域的个数应为2的整数次幂；其中，父数据域和子数据域是相对的，如图10所示，以一个数据域1003所示，数据域1003为数据域1002的父数据域，其中，数据域1003中的各个数据域1002为数据1003的子数据域；
e)整个数据空间可以被看做最顶层数据域。
在确定与流数据源模块对应的数据空间后，获取该数据空间的数据结构信息，以及获取构建请求中的系统功能信息，基于数据接口信息和系统功能信息，生成各个模块构建信息，其中，模块构建信息分别为构建水下拖缆系统、数据汇总单元、数据显示记录单元的信息，对构建成的水下拖缆系统、数据汇总单元以及数据显示记录单元进行说明。
参照图11，为构建的水下拖缆系统的采集单元的实现框图，需要说明的是，水下拖缆系统由多个采集单元连接组成。如图所示，采集单元由工作状态传感器读出节点、SDMF编码器节点(还可称为SDMF_encoder节点)、多路复用器节点(还可称为MUX节点)、命令反馈流合并节点(还可称为Reduce_CMD_FB节点)、命令广播节点(还可称为Map_CMD节点)、传输层接口节点、ADC读出节点、规格化节点(还可称为Regularizer节点)、SDMF解码器节点(还可称为SDMF_decoder节点)以及合并节点(还可以称为Merge节点)连接构成，其中，传输层接口节点支持8B/10B编码、校验以及反压控制等功能，工作状态传感器读取节点用于读取温度、电压等参数，其中，ADC读出节点与ADC数据接口相连接，图中与SDMF解码器节点连接的传输层接口节点与后级采集单元相连接或与数据汇总单元相连接，与SDMF编码器节点连接的传输层接口节点与前级采集单元相连接。采集单元中有四种流，分别为状态流、命令反馈流、命令流以及数据流，其中，由于节点处理数据任务的特性，节点中应用到的接口有所不同，不同的接口应用不同的定义以及传输的流的格式有所不同，图中不同的接口输出的流用不同的箭头表示，如图所示，AXI4-Stream接口和SDMF 接口均存在与其对应的状态流、命令反馈流、命令流和数据流。
具体的，如图所示，在采集单元内，命令流由上级节点被Map_CMD节点广播至本地各个需要命令控制的节点和下级节点，同时Reduce_CMD_FB节点收集本地各个节点和后级采集单元发送的命令反馈流数据帧并向前级转发。
数据流来自ADC读出节点以及与后级采集单元连接的传输层接口节点，在每个采集单元内包含两个ADC读出节点，每个ADC读出节点负责与ADC数据接口和ADC控制接口相连，其中，ADC数据接口与ADC控制接口可为流数据源模块的接口；来自两个ADC数据接口的数据流经过Regularizer节点进行空间排序后进入Merge节点完成数据合并，此时数据域由ADC级数据域变换为采集单元级数据域。在采集单元级数据域下，第二个Regularizer节点将本地数据帧和来自后级采集单元的数据帧进行空间排序后上传。这样来自各个采集单元的数据帧被逐级上传，汇总成整条拖缆的数据流。
在采集单元内，状态流来自单独的工作状态传感器读出节点，由于状态流以采集单元为单位进行上传，不需要进行数据合并，因此简单地将本地状态流与后级状态流复用后上传。
图中所示的ADC读出节点为一种传感器读出节点，可根据实际需求进行设置，参照图12，为本发明提供的一种传感器读出节点的模型示意图，传感器读出节点作为数据获取系统中数据流的起点和命令流的终点，图中所示的传感器读出节点的模型示意图中所有流对外的接口均使用SDMF接口，图中的寄存器器件配置系统控制用于根据时间戳维护时间分配的时钟/秒脉冲信号控制流的产生，例如产生状态流、数据流、报错/命令反馈流以及其他流等，流调度用于输出产生的流。本发明提供的传感器读取节点中至少具备一个命令流(下行)，一个数据流(上行)，一个命令反馈流(用于传输对命令的响应信息，上行)。
参照图13，为本发明实施例提供的数据汇总单元的实现框图，由图所示，数据汇总单元由传输层接口节点、数据缓存节点(还可称为vFIFO节点)、SDMF编码器节点(还可称为SDMF_decoder节点)、多路复用器节点(还可称为MUX节点)、规格化节点(还可称为Regularizer节点)、命令反馈流合并节点(还可称为Reduce_CMD_FB节点)、命令广播节点(还可称为Map_CMD节点)、SDMF 广播节点(还可称为SDMF_broadcast节点)、特征提取节点(还可称为Feature_extractor节点)、触发过滤器节点(还可称为Trigger节点)以及合并节点(还可以称为Merge节点)连接而成。
图中与数据缓存节点连接的传输层接口用于与水下拖缆系统连接，其中，一个传输层接口节点连接一个水下拖缆系统，此处的传输层接口节点支持8B/10B编码、校验以及反压控制等功能；与SDMF编码器节点连接的传输层接口节点用于与数据显示记录单元相连接，此处的传输层接口节点可作为PCI-E接口和DMA控制器，并且还支持8B/10B编码、校验、反压控制以及数据帧拆分/组装等功能。
数据汇总单元中包含状态流、命令反馈流、命令流、监控流以及数据流，其中，由于节点处理数据任务的特性，节点中应用到的接口有所不同，不同的接口应用不同的定义以及传输的流的格式有所不同，图中不同的接口输出的流用不同的箭头表示；如图所示，SDMF接口存在与其对应的状态流、命令反馈流、命令流、监控流以及数据流，AXI4-Stream接口存在与其对应的状态流、命令流、监控流以及数据流；图中所示的数据汇总单元中负责与四路水下拖缆系统进行信息交换和数据汇总。其中，对于命令流、命令反馈流和状态流，不需要进行数据处理，在数据汇总单元中仅仅进行简单的通道复用或分发。而对于数据流，在数据汇总单元内将来自各个水下拖缆的数据流在缓存后经过Regularizer节点规格化，并将经过空间排序后的数据帧发向两个处理节点。在特征提取节点中，对数据帧中的数据抽取出每个通道中的最新数据，作为监控流发送给软件，供监测拖缆运行状态(振子图)使用。在另一路中，根据枪控信号来控制Trigger节点输出待记录的时间窗口内的所有数据帧。由于缓存空间的限制，在数据汇总单元内并不能完全缓冲一个触发窗口内的所有数据，在Merge节点中选择一个合适数据域时间范围对这些数据帧进行合并，最终发送到数据显示记录单元供数据记录使用。
参考图14，为本发明实施例提供的数据显示记录单元的实现框图，如图所示，数据显示记录单元由传输层接口节点、接收节点(还可称为Receive节点)、发送节点(还可称为Transmit节点)、广播节点(还可称为Broadcast节点)、显示节点(还可以称为Display节点)、合并节点(还可以称为Merge节点)、错误 检查节点(还可称为Error Check节点)、进程管理器节点(还可以称为Process Keeper)、回读节点(还可以称为Load节点)、命令广播节点(还可称为Map_CMD节点)、多路切换节点(还可称为Switcher节点)、存储节点(还可以称为Save节点)、命令控制台节点(还可以称为CMD Console节点)、FFT变换节点以及结果分析节点连接组成。
数据显示记录单元通过传输层接口接口与数据汇总单元相连接，在数据显示记录单元中包含状态流、监控流、命令反馈流、命令流以及数据流，不同的节点所应用的接口的类型不同，输出的流的格式以及定义也有所不同，如图所示，SDMS接口以及文件描述符接口都存在与其对应的状态流、数据流、监控流以及命令流。如图所示，状态流和监控流被直接接入显示节点，显示当前系统的工作状态，但是状态流中的错误信息会被报告给命令控制台完成相应的出错处理。同时，命令控制台也作为命令流的起点和命令反馈流的终点。对于数据流，需要进行第三级数据合并，最终得到每次触发对应的时间窗口内的全部数据。这些数据在进行保存的同时，还需要发往数据质量分析模块(FFT，结果分析)供质量控制使用。
将水下拖缆系统、数据汇总单元以及数据显示记录单元连接，即可完成海上时移地震的数据获取系统的构建，本发明实施例提供的水下拖缆系统、数据汇总单元以及数据显示记录单元中，绝大部分用到的流处理节点均为标准的流处理节点(图中为实线的节点)，例如水下拖缆系统的采集单元中的命令广播节点，数据汇总单元中的规格化节点以及数据显示记录单元中的多路切换节点；在构建数据获取系统中，仅需要根据设计处理需求和面向的传感器接口，针对性的设计若干定制模块，例如ADC读出节点、工作状态读出节点、错误检查节点、相应的结果分析和处理节点(FFT变换节点，结果分析节点)以及和系统工作流程对应的命令控制台节点，就可以完成数据获取系统的设计及构建；采用本发明提供的方法，大大简化了数据获取系统的设计过程，使得构建数据获取系统更加简便，并且，本发明中采用了相同的接口和通信协议，定制的节点可以通过简单修改后应用于类似的数据获取系统的设计和构建中，本发明所提供的数据获取系统的构建方法具有良好的泛化能力和具有良好的通用性。
本发明提供的方法中，通过将数据的实时采集、传输、处理、监控和系统控制过程抽象为一系列流处理节点的级联和组合。这些节点之间采用标准的接口方式和标准的流数据帧格式，具有硬件(FPGA内逻辑模块)或软件(计算机进程)两种实现方式，同一数据域下的流处理节点可以任意地连接。在进行数据获取系统的设计和构建时，通过将数据获取系统中的各个流的基本处理方法抽象为一系列标准的流处理节点，在保证系统对数据的实时处理能力的前提下，提高模块的复用性，减少设计工作量，加速整个数据获取系统的设计与实现。
同时，本发明提供的方法也是一套开放的数据获取系统标准框架。通过提供开放的接口和协议供用户使用，用户可以通过添加自定义的传感器前端电子学读出节点和个性化的数据处理节点来实现面向各种常见应用场景的数据获取和实时数据处理需求，具备良好的通用性和可扩充性能。
应用本发明实施例提供的方法构建数据获取系统，通过采用标准化的流处理节点的连接，构建具有触发判选、合并、传输、存储、显示等常见的各项功能的数据获取系统，加快了数据获取系统的开发速度。使用本发明提供的方法构建数据获取系统，在面对数据获取系统的通道数的增加、集成度的增加、使用高速的传输接口等升级改造，只要数据获取系统的底层的传感器采集模块不发生变化，可以利用各种标准化的流处理节点构建更大规模的数据获取系统，从而方便地完成通道数和系统集成度增加方面的升级改造。在增加对新传输接口的支持单元后，也可以无缝地替代原有的传输接口，由此可以完成高速传输接口方面的升级改造，从而简化了数据获取系统的升级改造过程。并且，应用本发明提供的方法构建的数据获取系统，各个流处理节点之间采用标准的传输接口和数据帧协议，因此具备任意连接的特性，因此通过对各个流处理节点的输入、输出端口增加模拟数据源、数据协议检查、数据帧显示、存储等调试节点即可以方便地进行单个节点的调试，在各个流的路径上也可以方便的插入各种调试节点，从而大大简化了系统的调试过程。本发明提供的构建数据获取系统的方法在应用时不要求用户需要有很专业的设计能力和具有很专业的知识，可以通过简单的模块的连接的方式自由定制数据获取系统，由此方便用户的使用。
与图1所示的方法相对应的，本发明实施例提供一种数据获取系统的构建装置，该装置可应用于构建数据获取系统的计算机装置或平台中，本发明提供的装置的结构示意图如图15所示，具体说明如下所述：
响应单元1501，用于响应于用户发送的用于构建数据获取系统的构建请求，确定所要构建的数据获取系统中所包含的各个采集处理模块的模块信息和模块互连信息；
抽象单元1502，用于根据各个所述采集处理模块的模块信息和模块互连信息，抽象出所述数据获取系统中包含的各种工作流；
第一确定单元1503，用于基于每种所述工作流的通道数量和工作时间长度，确定每种所述工作流中所传输数据的数据空间信息；
第二确定单元1504，用于对于每种所述工作流，确定所述工作流的数据处理方式信息以及接口应用信息，所述接口应用信息中包含所述工作流所流经的每个采集处理模块为所述工作流提供的接口的接口信息；基于所述工作流的数据空间信息、所述接口应用信息以及所述数据处理方式信息，确定所述工作流的处理路径中包含的各个数据域，其中，所述数据域为工作流在处理过程中具有相同流数据帧粒度的数据区域，所述数据域的等级随着流数据帧粒度的增大而升高；
第三确定单元1505，用于对于每种所述工作流，将所述工作流所流经的每个采集处理模块均确定为目标模块，并确定所述工作流的数据域信息，所述数据域信息中包含与所述工作流对应的每个流处理节点所处的数据域的属性信息；基于所述工作流的接口应用信息、数据处理方式信息、数据域信息以及每个所述目标模块的模块信息和模块互连信息，确定与所述工作流对应的每个流处理节点所对应的目标模块，并确定每个所述流处理节点在与其对应的目标模块中的位置信息；
生成单元1506，用于对于每个所述采集处理模块，确定与所述采集处理模块对应的各个流处理节点，基于每个流处理节点的位置信息，生成所述采集处理模块的模块构建信息；
第四确定单元1507，用于对于每个所述采集处理模块，确定所述采集处 理模块的跨模块接口节点，基于所述跨模块接口节点，确定与该采集处理模块存在连接关系的采集处理模块，并将所述采集处理模块与其存在连接关系的采集处理模块相连接；
连接单元1508，用于对于每个所述采集处理模块，根据所述采集处理模块的模块构建信息，确定与所述采集处理模块对应的每个流处理节点的节点信息，基于每个所述流处理节点的节点信息，使用标准化封装后的标准接口将所述采集处理模块的各个流处理节点和跨模块接口节点进行连接，得到与所述采集处理模块对应的模块设计文件，将所述模块设计文件部署至所述采集处理模块中，以完成与所述构建请求对应的数据获取系统的构建。
本发明实施例提供的装置中，响应于用户发送的用于构建数据获取系统的构建请求，确定所要构建的数据获取系统中所包含的各个采集处理模块的模块信息和模块互连信息；根据各个采集处理模块的模块信息和模块互连信息，抽闲出数据获取系统中包含的各种工作流；基于每种工作流的通道数量和工作时间长度，确定每种工作流中传输数据的数据空间信息；对于每种工作流，确定工作流的数据处理方式以及接口应用信息，所述接口应用信息中包含工作流所流经的每个采集处理模块为工作流提供的接口的接口信息；基于工作流的数据空间信息、接口应用信息以及数据处理方式信息，确定工作流的处理路径中包含的各个数据域；对于每种工作流，将工作流所流经的每个采集处理模块均确定为目标模块，以及确定工作流的数据域信息；根据工作流的接口应用信息、数据处理方式信息、数据域信息以及每个目标模块的模块信息和模块互连信息，确定与工作流对应的每个流处理节点所对应的目标模块，并确定每个流处理节点在与其对应的目标模块中的位置信息；对于每个采集处理模块，确定与该采集处理模块对应的各个流处理节点，基于每个流处理节点的位置信息，生成采集处理模块的模块构建信息；确定采集处理模块的块模块接口节点，基于跨模块接口节点，确定与该采集处理模块存在连接关系的采集处理模块，并将该采集处理模块与其存在连接关系的采集处理模块相连接；根据采集处理模块的模块构建信息，确定与采集处理模块对应的每个流处理节点的节点信息，基于每个流处理节点的节点信息，使用标准化封装后的标准接口将采集处理模块的各个流处理节点和跨模块接口节点进行连接，得到与采集处理模块对应的模 块设计文件，并将该模块设计文件部署至采集处理模块中，进而完成数据获取系统的构建。应用本发明，响应于用户发送的用于构建数据获取系统的构建请求，确定与构建请求对应的采集处理模块的模块信息和模块互连信息，抽象出数据获取系统中的各个工作流，基于每种工作流中所传输的数据空间信息，确定每种工作流的处理路径中的数据域信息，最终确定每个采集处理模块的模块构建信息；基于模块构建信息和跨模块接口节点将存在连接关系的采集处理模块相连接；将每个采集处理模块中的流处理节点和跨模块接口节点使用标准化封装后的标准接口进行连接，得到采集处理模块的模块设计文件，并将模块设计文件部署至采集处理模块中，完成数据获取系统的构建。本发明使用流处理节点构建数据获取系统，无需对每个功能模块进行设计，构建的数据获取系统中的流处理节点具有复用性，在对系统进行调整或是修改时，无需重新进行设计，节省了大量的时间，并且本发明提供的构建数据系统的构建方法，构建过程简单、不复杂且具有普遍性，降低了构建数据获取系统的难度，使得专业性不强的人员也可使用本发明提供的方法构建所需的数据获取系统。
本发明实施例提供的装置，所述第四确定单元1507，可配置为：
第一确定子单元，用于确定所述采集处理模块的跨模块接口类型；
第一判断子单元，用于在预设的标准跨模块接口节点库中判断是否存在与所述跨模块接口类型对应的标准跨模块接口节点；
第二确定子单元，用于若存在与所述跨模块接口类型对应的标准跨模块接口节点，则将与所述跨模块接口类型对应的标准跨模块接口节点作为所述采集处理模块的跨模块接口节点；
构建子单元，用于若不存在与所述跨模块接口类型对应的标准跨模块接口节点，则基于所述采集处理模块的物理层传输介质和接口信息，构建所述采集处理模块的跨模块接口节点。
本发明实施例提供的装置，所述生成单元1506，可配置为：
获取子单元，用于获取所述采集处理模块的各个节点类型信息；
第二判断子单元，用于对于每个所述节点类型信息，在与所述采集处理模块的处理单元类型对应的标准节点库中，确定是否存在与所述节点类型信息对应的标准处理节点；
第三确定子单元，用于若存在与所述节点类型信息对应的标准处理节点，则将与所述节点类型信息对应的标准处理节点作为与所述采集处理模块对应的流处理节点；
第二构建子单元，用于若未存在与所述节点类型信息对应的标准处理节点，则基于与所述节点类型信息对应的节点信息，构建与所述节点类型信息对应的流处理节点，并将构建的流处理节点作为与所述采集处理模块对应的流处理节点。
本发明实施例提供的装置，还可配置为：
第五确定单元，用于对于所述采集处理模块中的每个数据接口，确定每个所述数据接口所处的采集处理模块的处理单元类型；
第六确定单元，用于确定每个所述数据接口的数据域属性，基于每个所述数据接口的数据域属性，确定每个所述数据接口的流数据帧参数以及流数据帧信息段内容；
输入单元，用于对于每个所述数据接口，将所述数据接口的流数据帧参数和流数据帧信息段内容应用于预设的标准流数据帧格式模块，得到所述数据接口的标准流数据帧格式；
获取单元，用于基于每个所述数据接口的标准数据接口类型、工作参数以及标准流数据帧格式，将每个所述数据接口进行标准化封装，得到与每个数据接口对应的标准接口。
本发明实施例提供的装置，所述连接单元1508，可配置为：
解析子单元，用于对每个所述流处理节点的节点信息进行解析，得到每个所述流处理节点的节点类型和连接信息；
第四确定子单元，用于对于每个所述流处理节点，基于所述流处理节点的连接信息，确定所述流处理节点的每个端口所对应的目标连接节点的目标端口，所述目标连接节点为与所述流处理节点存在连接关系的流处理节点，所述目标端口为所述目标连接节点中与所述流处理节点连接的端口；
第三判断子单元，用于对于每个所述流处理节点中的每个端口，基于所述端口所处的流处理节点的节点类型确定所述端口的连接方式，确定所述端口所对应的目标连接节点与所述端口所处的流处理节点是否均处于同一采集处理 模块内；
第一连接子单元，用于若所述端口所对应的目标连接节点与所述端口所处的流处理节点未处于同一采集处理模块内，则在标准转换模块中确定与所述端口对应的标准端口，将所述端口和与所述端口对应的标准端口之间的接口进行标准化封装，基于所述端口的数据域属性确定标准转换模块的工作参数后，使用所述标准转换模块应用所述端口的连接方式将所述端口与跨模块接口节点连接，使得所述端口通过所述跨模块接口节点与该端口所对应的目标端口相连接；
第二连接子单元，用于若所述端口所对应的目标连接节点与所述端口所处的流处理节点处于同一采集处理模块内，则对所述端口和所述端口所对应的目标端口之间的接口进行标准化封装，以得到标准接口，通过所述标准接口应用所述端口的连接方式，使得所述端口和所述端口所对应的目标端口相连接。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统或系统实施例而言，由于其基本相似于方法实施例，所以描述得比较简单，相关之处参见方法实施例的部分说明即可。以上所描述的系统及系统实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
专业人员还可以进一步意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
对所公开的实施例的上述说明，使本领域专业技术人员能够实现或使用本发明。对这些实施例的多种修改对本领域的专业技术人员来说将是显而易见的，本文中所定义的一般原理可以在不脱离本发明的精神或范围的情况下，在其它实施例中实现。因此，本发明将不会被限制于本文所示的这些实施例，而是要符合与本文所公开的原理和新颖特点相一致的最宽的范围。

Claims (10)

  1. 一种数据获取系统的构建方法，其特征在于，包括：
    响应于用户发送的用于构建数据获取系统的构建请求，确定所要构建的数据获取系统中所包含的各个采集处理模块的模块信息和模块互连信息；
    根据各个所述采集处理模块的模块信息和模块互连信息，抽象出所述数据获取系统中包含的各种工作流；
    基于每种所述工作流的通道数量和工作时间长度，确定每种所述工作流中所传输数据的数据空间信息；
    对于每种所述工作流，确定所述工作流的数据处理方式信息以及接口应用信息，所述接口应用信息中包含所述工作流所流经的每个采集处理模块为所述工作流提供的接口的接口信息；基于所述工作流的数据空间信息、所述接口应用信息以及所述数据处理方式信息，确定所述工作流的处理路径中包含的各个数据域，其中，所述数据域为工作流在处理过程中具有相同流数据帧粒度的数据区域，所述数据域的等级随着流数据帧粒度的增大而升高；
    对于每种所述工作流，将所述工作流所流经的每个采集处理模块均确定为目标模块，并确定所述工作流的数据域信息，所述数据域信息中包含与所述工作流对应的每个流处理节点所处的数据域的属性信息；基于所述工作流的接口应用信息、数据处理方式信息、数据域信息以及每个所述目标模块的模块信息和模块互连信息，确定与所述工作流对应的每个流处理节点所对应的目标模块，并确定每个所述流处理节点在与其对应的目标模块中的位置信息；
    对于每个所述采集处理模块，确定与所述采集处理模块对应的各个流处理节点，基于每个流处理节点的位置信息，生成所述采集处理模块的模块构建信息；
    对于每个所述采集处理模块，确定所述采集处理模块的跨模块接口节点，基于所述跨模块接口节点，确定与该采集处理模块存在连接关系的采集处理模块，并将所述采集处理模块与其存在连接关系的采集处理模块相连接；
    对于每个所述采集处理模块，根据所述采集处理模块的模块构建信息，确定与所述采集处理模块对应的每个流处理节点的节点信息，基于每个所述流处理节点的节点信息，使用标准化封装后的标准接口将所述采集处理模块的各个 流处理节点和跨模块接口节点进行连接，得到与所述采集处理模块对应的模块设计文件，将所述模块设计文件部署至所述采集处理模块中，以完成与所述构建请求对应的数据获取系统的构建。
  2. 根据权利要求1所述的方法，其特征在于，所述确定所述采集处理模块的跨模块接口节点，包括：
    确定所述采集处理模块的跨模块接口类型；
    在预设的标准跨模块接口节点库中判断是否存在与所述跨模块接口类型对应的标准跨模块接口节点；
    若存在与所述跨模块接口类型对应的标准跨模块接口节点，则将与所述跨模块接口类型对应的标准跨模块接口节点作为所述采集处理模块的跨模块接口节点；
    若不存在与所述跨模块接口类型对应的标准跨模块接口节点，则基于所述采集处理模块的物理层传输介质和接口信息，构建所述采集处理模块的跨模块接口节点。
  3. 根据权利要求1所述的方法，其特征在于，所述确定与所述采集处理模块对应的各个流处理节点，包括：
    获取所述采集处理模块的各个节点类型信息；
    对于每个所述节点类型信息，在与所述采集处理模块的处理单元类型对应的标准节点库中，确定是否存在与所述节点类型信息对应的标准处理节点；
    若存在与所述节点类型信息对应的标准处理节点，则将与所述节点类型信息对应的标准处理节点作为与所述采集处理模块对应的流处理节点；
    若未存在与所述节点类型信息对应的标准处理节点，则基于与所述节点类型信息对应的节点信息，构建与所述节点类型信息对应的流处理节点，并将构建的流处理节点作为与所述采集处理模块对应的流处理节点。
  4. 根据权利要求1所述的方法，其特征在于，标准接口的标准化封装的过程，包括：
    对于所述采集处理模块中的每个数据接口，确定每个所述数据接口所处的采集处理模块的处理单元类型；
    确定每个所述数据接口的数据域属性，基于每个所述数据接口的数据域属 性，确定每个所述数据接口的流数据帧参数以及流数据帧信息段内容；
    对于每个所述数据接口，将所述数据接口的流数据帧参数和流数据帧信息段内容应用于预设的标准流数据帧格式模板，得到所述数据接口的标准流数据帧格式；
    基于每个所述数据接口的标准数据接口类型、工作参数以及标准流数据帧格式，将每个所述数据接口进行标准化封装，得到与每个数据接口对应的标准接口。
  5. 根据权利要求1所述的方法，其特征在于，所述基于每个所述流处理节点的节点信息，使用标准化封装后的标准接口将所述采集处理模块的各个流处理节点和跨模块接口节点进行连接，包括：
    对每个所述流处理节点的节点信息进行解析，得到每个所述流处理节点的节点类型和连接信息；
    对于每个所述流处理节点，基于所述流处理节点的连接信息，确定所述流处理节点的每个端口所对应的目标连接节点的目标端口，所述目标连接节点为与所述流处理节点存在连接关系的流处理节点，所述目标端口为所述目标连接节点中与所述流处理节点连接的端口；
    对于每个所述流处理节点中的每个端口，基于所述端口所处的流处理节点的节点类型确定所述端口的连接方式，确定所述端口所对应的目标连接节点与所述端口所处的流处理节点是否均处于同一采集处理模块内；
    若所述端口所对应的目标连接节点与所述端口所处的流处理节点未处于同一采集处理模块内，则在标准转换模块中确定与所述端口对应的标准端口，将所述端口和与所述端口对应的标准端口之间的接口进行标准化封装，基于所述端口的数据域属性确定标准转换模块的工作参数后，使用所述标准转换模块应用所述端口的连接方式将所述端口与跨模块接口节点连接，使得所述端口通过所述跨模块接口节点与该端口所对应的目标端口相连接；
    若所述端口所对应的目标连接节点与所述端口所处的流处理节点处于同一采集处理模块内，则对所述端口和所述端口所对应的目标端口之间的接口进行标准化封装，以得到标准接口，通过所述标准接口应用所述端口的连接方式，使得所述端口和所述端口所对应的目标端口相连接。
  6. 一种数据获取系统的构建装置，其特征在于，包括：
    响应单元，用于响应于用户发送的用于构建数据获取系统的构建请求，确定所要构建的数据获取系统中所包含的各个采集处理模块的模块信息和模块互连信息；
    抽象单元，用于根据各个所述采集处理模块的模块信息和模块互连信息，抽象出所述数据获取系统中包含的各种工作流；
    第一确定单元，用于基于每种所述工作流的通道数量和工作时间长度，确定每种所述工作流中所传输数据的数据空间信息；
    第二确定单元，用于对于每种所述工作流，确定所述工作流的数据处理方式信息以及接口应用信息，所述接口应用信息中包含所述工作流所流经的每个采集处理模块为所述工作流提供的接口的接口信息；基于所述工作流的数据空间信息、所述接口应用信息以及所述数据处理方式信息，确定所述工作流的处理路径中包含的各个数据域，其中，所述数据域为工作流在处理过程中具有相同流数据帧粒度的数据区域，所述数据域的等级随着流数据帧粒度的增大而升高；
    第三确定单元，用于对于每种所述工作流，将所述工作流所流经的每个采集处理模块均确定为目标模块，并确定所述工作流的数据域信息，所述数据域信息中包含与所述工作流对应的每个流处理节点所处的数据域的属性信息；基于所述工作流的接口应用信息、数据处理方式信息、数据域信息以及每个所述目标模块的模块信息和模块互连信息，确定与所述工作流对应的每个流处理节点所对应的目标模块，并确定每个所述流处理节点在与其对应的目标模块中的位置信息；
    生成单元，用于对于每个所述采集处理模块，确定与所述采集处理模块对应的各个流处理节点，基于每个流处理节点的位置信息，生成所述采集处理模块的模块构建信息；
    第四确定单元，用于对于每个所述采集处理模块，确定所述采集处理模块的跨模块接口节点，基于所述跨模块接口节点，确定与该采集处理模块存在连接关系的采集处理模块，并将所述采集处理模块与其存在连接关系的采集处理模块相连接；
    连接单元，用于对于每个所述采集处理模块，根据所述采集处理模块的模块构建信息，确定与所述采集处理模块对应的每个流处理节点的节点信息，基于每个所述流处理节点的节点信息，使用标准化封装后的标准接口将所述采集处理模块的各个流处理节点和跨模块接口节点进行连接，得到与所述采集处理模块对应的模块设计文件，将所述模块设计文件部署至所述采集处理模块中，以完成与所述构建请求对应的数据获取系统的构建。
  7. 根据权利要求6所述的装置，其特征在于，所述第四确定单元，包括：
    第一确定子单元，用于确定所述采集处理模块的跨模块接口类型；
    第一判断子单元，用于在预设的标准跨模块接口节点库中判断是否存在与所述跨模块接口类型对应的标准跨模块接口节点；
    第二确定子单元，用于若存在与所述跨模块接口类型对应的标准跨模块接口节点，则将与所述跨模块接口类型对应的标准跨模块接口节点作为所述采集处理模块的跨模块接口节点；
    构建子单元，用于若不存在与所述跨模块接口类型对应的标准跨模块接口节点，则基于所述采集处理模块的物理层传输介质和接口信息，构建所述采集处理模块的跨模块接口节点。
  8. 根据权利要求6所述的装置，其特征在于，所述生成单元，包括：
    获取子单元，用于获取所述采集处理模块的各个节点类型信息；
    第二判断子单元，用于对于每个所述节点类型信息，在与所述采集处理模块的处理单元类型对应的标准节点库中，确定是否存在与所述节点类型信息对应的标准处理节点；
    第三确定子单元，用于若存在与所述节点类型信息对应的标准处理节点，则将与所述节点类型信息对应的标准处理节点作为与所述采集处理模块对应的流处理节点；
    第二构建子单元，用于若未存在与所述节点类型信息对应的标准处理节点，则基于与所述节点类型信息对应的节点信息，构建与所述节点类型信息对应的流处理节点，并将构建的流处理节点作为与所述采集处理模块对应的流处理节点。
  9. 根据权利要求6所述的装置，其特征在于，还包括：
    第五确定单元，用于对于所述采集处理模块中的每个数据接口，确定每个所述数据接口所处的采集处理模块的处理单元类型；
    第六确定单元，用于确定每个所述数据接口的数据域属性，基于每个所述数据接口的数据域属性，确定每个所述数据接口的流数据帧参数以及流数据帧信息段内容；
    输入单元，用于对于每个所述数据接口，将所述数据接口的流数据帧参数和流数据帧信息段内容应用于预设的标准流数据帧格式模块，得到所述数据接口的标准流数据帧格式；
    获取单元，用于基于每个所述数据接口的标准数据接口类型、工作参数以及标准流数据帧格式，将每个所述数据接口进行标准化封装，得到与每个数据接口对应的标准接口。
  10. 根据权利要求6所述的装置，其特征在于，所述连接单元，包括：
    解析子单元，用于对每个所述流处理节点的节点信息进行解析，得到每个所述流处理节点的节点类型和连接信息；
    第四确定子单元，用于对于每个所述流处理节点，基于所述流处理节点的连接信息，确定所述流处理节点的每个端口所对应的目标连接节点的目标端口，所述目标连接节点为与所述流处理节点存在连接关系的流处理节点，所述目标端口为所述目标连接节点中与所述流处理节点连接的端口；
    第三判断子单元，用于对于每个所述流处理节点中的每个端口，基于所述端口所处的流处理节点的节点类型确定所述端口的连接方式，确定所述端口所对应的目标连接节点与所述端口所处的流处理节点是否均处于同一采集处理模块内；
    第一连接子单元，用于若所述端口所对应的目标连接节点与所述端口所处的流处理节点未处于同一采集处理模块内，则在标准转换模块中确定与所述端口对应的标准端口，将所述端口和与所述端口对应的标准端口之间的接口进行标准化封装，基于所述端口的数据域属性确定标准转换模块的工作参数后，使用所述标准转换模块应用所述端口的连接方式将所述端口与跨模块接口节点连接，使得所述端口通过所述跨模块接口节点与该端口所对应的目标端口相连接；
    第二连接子单元，用于若所述端口所对应的目标连接节点与所述端口所处的流处理节点处于同一采集处理模块内，则对所述端口和所述端口所对应的目标端口之间的接口进行标准化封装，以得到标准接口，通过所述标准接口应用所述端口的连接方式，使得所述端口和所述端口所对应的目标端口相连接。
PCT/CN2021/099995 2021-06-15 2021-06-15 数据获取系统的构建方法及装置 WO2022261810A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/099995 WO2022261810A1 (zh) 2021-06-15 2021-06-15 数据获取系统的构建方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/099995 WO2022261810A1 (zh) 2021-06-15 2021-06-15 数据获取系统的构建方法及装置

Publications (1)

Publication Number Publication Date
WO2022261810A1 true WO2022261810A1 (zh) 2022-12-22

Family

ID=84526793

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/099995 WO2022261810A1 (zh) 2021-06-15 2021-06-15 数据获取系统的构建方法及装置

Country Status (1)

Country Link
WO (1) WO2022261810A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116009459A (zh) * 2023-01-18 2023-04-25 华中科技大学 一种数控系统边缘计算模块的数据采集平台及数控系统
CN117234977A (zh) * 2023-11-10 2023-12-15 浪潮电子信息产业股份有限公司 数据处理方法、系统、设备及计算机可读存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130268936A1 (en) * 2012-04-09 2013-10-10 Yu-Hung Hsu Workflow management system and method
CN103731298A (zh) * 2013-11-15 2014-04-16 中国航天科工集团第二研究院七〇六所 一种大规模分布式网络安全数据采集方法与系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130268936A1 (en) * 2012-04-09 2013-10-10 Yu-Hung Hsu Workflow management system and method
CN103731298A (zh) * 2013-11-15 2014-04-16 中国航天科工集团第二研究院七〇六所 一种大规模分布式网络安全数据采集方法与系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
WANG HONGCHAO, YANG JUNFENG; WANG TIANXING; SUN ZHENGYANG; SONG KEZHU: "Implementation of Versatile Data Display Module for Stream Processing Data Acquisition System", SHUJU CAIJI YU CHULI - JOURNAL OF DATA ACQUISITION & PROCESSING, SHUJU CAIJI YU CHULI, XINXIANG, CN, vol. 36, no. 2, 31 March 2021 (2021-03-31), CN , pages 374 - 383, XP093016112, ISSN: 1004-9037, DOI: 10.16337/j.1004-9037.2021.02.019 *
WANG TIANXING; YANG JUNFENG; WANG HONGCHAO; YU HONGWEI; SUN ZHENGYANG; ZHANG LEI; LIU RUOLIN: "A Generic Streaming Software Platform Design for High-Energy Physics Data Acquisition Systems", IEEE TRANSACTIONS ON NUCLEAR SCIENCE, IEEE, USA, vol. 68, no. 2, 8 January 2021 (2021-01-08), USA, pages 101 - 109, XP011837727, ISSN: 0018-9499, DOI: 10.1109/TNS.2021.3050140 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116009459A (zh) * 2023-01-18 2023-04-25 华中科技大学 一种数控系统边缘计算模块的数据采集平台及数控系统
CN117234977A (zh) * 2023-11-10 2023-12-15 浪潮电子信息产业股份有限公司 数据处理方法、系统、设备及计算机可读存储介质
CN117234977B (zh) * 2023-11-10 2024-02-27 浪潮电子信息产业股份有限公司 数据处理方法、系统、设备及计算机可读存储介质

Similar Documents

Publication Publication Date Title
US20220197714A1 (en) Training a neural network using a non-homogenous set of reconfigurable processors
Khriji et al. Design and implementation of a cloud-based event-driven architecture for real-time data processing in wireless sensor networks
US20220198114A1 (en) Dataflow Function Offload to Reconfigurable Processors
JP4889471B2 (ja) セパレートプロセッシングコンポーネント間のバッファ間データ転送を減らす方法およびシステム
JP3929554B2 (ja) ファイル・オブジェクトの生成をバリデーションし、ファイル・オブジェクトへのメッセージをルーチングする方法
US8438578B2 (en) Network on chip with an I/O accelerator
CN101957863B (zh) 数据并行处理方法、装置及系统
US20160004578A1 (en) Realtime processing of streaming data
CN111381983B (zh) 虚拟试验靶场验证系统的轻量级消息中间件系统及方法
US20070011156A1 (en) RSS enabled logging
US20180063290A1 (en) Networked device management data collection
WO2022261810A1 (zh) 数据获取系统的构建方法及装置
US20040233237A1 (en) Development environment for DSP
CN103268230B (zh) 用于构建可拓展服务的云计算信息管理平台的方法
Peltenburg et al. Tens of gigabytes per second JSON-to-Arrow conversion with FPGA accelerators
CN116996112A (zh) 一种遥感卫星数据实时预处理方法
CN113312394B (zh) 数据获取系统的构建方法及装置
US20190163404A1 (en) Methods and systems that efficiently store metric data to enable period and peak detection
US11687513B2 (en) Virtual data source manager of data virtualization-based architecture
Nath et al. IrisNet: An architecture for compute-intensive wide-area sensor network services
Marcu et al. In support of push-based streaming for the computing continuum
Kiran et al. A complexity effective communication model for behavioral modeling of signal processing applications
CN115051979B (zh) 监控数据调试系统、方法、车辆和计算机可读存储介质
CN114356688A (zh) 一种通用数据管理软件架构
Huang et al. Design of Cloud Platform for Efficient Remote Sensing Big Data Processing Based on Open Stack

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21945403

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21945403

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 04/06/2024)

122 Ep: pct application non-entry in european phase

Ref document number: 21945403

Country of ref document: EP

Kind code of ref document: A1