Methods for data acquisition, storage media, processors, and engineering vehicles

Abstract

This application provides a method, storage medium, processor, and engineering vehicle for data acquisition. The method is applied to a first terminal with an NIFI application installed. The method includes: obtaining a first operation command triggered by a user through the NIFI application's interface for a first icon, where the first icon is a display icon of a preset NIFI component in the NIFI application; obtaining configuration parameters input by the user for each preset NIFI component based on the first operation command; generating a first template file corresponding to a target device based on the configuration parameters of each preset NIFI component; and sending the first template file to a second terminal corresponding to the target device, so that the second terminal can perform corresponding data acquisition operations based on the first template file. Through this technical solution, there is no need to repeatedly develop a large number of components, shortening the data acquisition time cycle and significantly improving the efficiency of data acquisition.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more specifically to a method for acquiring data, a storage medium, a processor, and an engineering vehicle. Background Technology

[0002] As the intelligence level of Industrial Internet of Things (IIoT) devices increases, these devices generate massive amounts of real-time data. Currently, this real-time data is typically transmitted to the cloud via wireless networks, where it is parsed, stored, displayed, and analyzed. However, due to the diversity of IIoT devices and the different data bus transmission protocols they employ, some even using proprietary protocols for encrypted transmission, the data becomes diverse and heterogeneous, leading to a dramatic increase in data volume.

[0003] For data transmitted using proprietary encrypted protocols, traditional data acquisition methods typically involve writing application code to collect data from industrial IoT devices. This process requires first collecting data from the device's sensors, then aggregating it via the device's PLC bus to an edge terminal. The edge terminal then transmits the encrypted and converted data to the cloud via a wireless network. However, implementing this acquisition process requires customized embedded development at both the edge and cloud levels, depending on the type of industrial IoT device. This development is costly and time-consuming. Furthermore, the code used needs to be redeveloped depending on the type of industrial IoT device, increasing the workload and significantly reducing the efficiency of data acquisition. Summary of the Invention

[0004] The purpose of this application is to provide a method, storage medium, processor, and engineering vehicle for data acquisition.

[0005] To achieve the above objectives, a first aspect of this application provides a method for data collection, comprising: a first terminal acquiring a first operation command triggered by a user through the operation interface of a NIFI application for a first icon, the first icon being a display icon of a preset NIFI component in the NIFI application, the preset NIFI component being determined from multiple NIFI components according to a specific protocol type of the target device; the first terminal acquiring configuration parameters input by the user for each preset NIFI component according to the first operation command, the configuration parameters being determined according to a specific protocol type adopted by the target device and the data types that the target device can collect; the first terminal generating a first template file corresponding to the target device according to the configuration parameters of each preset NIFI component, and sending the first template file to a second terminal corresponding to the target device; the second terminal receiving the first template file and converting the first template file into a configuration file of a corresponding specific format; a cloud platform sending a data collection command to the second terminal; upon receiving the data collection command, the second terminal collecting device data of the target device in real time according to the configuration file of the specific format; and the second terminal sending the device data to the cloud platform.

[0006] A second aspect of this application provides a processor configured to perform the above-described method for acquiring data.

[0007] A third aspect of this application provides a machine-readable storage medium storing instructions that, when executed by a processor, configure the processor to perform the aforementioned method for acquiring data.

[0008] A fourth aspect of this application provides an engineering vehicle, the engineering vehicle including: a second terminal; and the processor described above, the processor being configured to execute the method described above for collecting data, the method being applied to the second terminal corresponding to a target device.

[0009] The above technical solution allows for different parameter configurations of preset NIFI components on the visual interface, thereby generating template files corresponding to the preset NIFI components. When the target device uses different protocol types, data acquisition from different target devices can be achieved by configuring different parameters of the preset NIFI components. This is convenient and fast, greatly reducing the manpower and time costs required for development, eliminating the need to repeatedly develop a large number of components, further shortening the data acquisition cycle, and significantly improving the efficiency of data acquisition.

[0010] Other features and advantages of the embodiments of this application will be described in detail in the following detailed description section. Attached Figure Description

[0011] The accompanying drawings are provided to further illustrate the embodiments of this application and form part of the specification. They are used together with the following detailed description to explain the embodiments of this application, but do not constitute a limitation on the embodiments of this application. In the drawings:

[0012] Figure 1 This illustration schematically shows an application environment diagram of a method for collecting data according to an embodiment of this application;

[0013] Figure 2 This schematically illustrates a first flowchart of a method for collecting data according to an embodiment of this application;

[0014] Figure 3 The illustration shows a schematic diagram of a first type of component parameter configuration for a method for acquiring data according to an embodiment of this application;

[0015] Figure 4 This illustration schematically shows a second component parameter configuration of a method for acquiring data according to an embodiment of this application;

[0016] Figure 5 This illustration schematically shows a third component parameter configuration of a method for acquiring data according to an embodiment of this application;

[0017] Figure 6 This illustration schematically shows a fourth component parameter configuration of a method for acquiring data according to an embodiment of this application;

[0018] Figure 7 This illustration schematically shows a second flowchart of a method for collecting data according to an embodiment of this application;

[0019] Figure 8 This schematically illustrates a third flowchart of a method for collecting data according to an embodiment of this application;

[0020] Figure 9 This illustration schematically shows a fifth component parameter configuration of a method for acquiring data according to an embodiment of this application;

[0021] Figure 10 This schematically illustrates a fourth flowchart of a method for collecting data according to an embodiment of this application;

[0022] Figure 11 This schematic diagram illustrates a structural block diagram of a system for acquiring data according to an embodiment of this application;

[0023] Figure 12 The diagram illustrates the internal structure of a computer device according to an embodiment of this application. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only for illustration and explanation of the embodiments of this application and are not intended to limit the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0025] The data collection method provided in this application can be applied to, for example... Figure 1 In the application environment shown, the first terminal 101 communicates with the second terminal 102 and the cloud platform 103 via a network. The second terminal 102 communicates with the first terminal 101 and the cloud platform 103 via a network. The cloud platform 103 communicates with both the first terminal 101 and the second terminal 102 via a network. The first terminal 101 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, and portable wearable devices. The first terminal 101 may have a MiniFi application installed. The second terminal 102 can refer to a second terminal corresponding to the target device. The second terminal 102 may have a MiniFi application installed. The target device can be an engineering vehicle. If the target device is an engineering vehicle, the second terminal 102 can be a device installed on the engineering vehicle, which has a display screen for displaying data acquisition time, etc.

[0026] Figure 2 A schematic flowchart illustrating a method for collecting data according to an embodiment of this application is shown. Figure 2 As shown, in one embodiment of this application, a method for collecting data is provided. This embodiment mainly applies this method to the above-mentioned... Figure 1 Taking the first terminal 101 as an example, the first terminal 101 has a NIFI application installed. The method is applied to the first terminal 101 with the NIFI application installed, and the method includes the following steps:

[0027] Step 201: Obtain the first operation command triggered by the user through the operation interface of the nifi application for the first icon. The first icon is the display icon of the preset nifi component in the nifi application. The preset nifi component is determined from multiple nifi components according to the specific protocol type of the target device.

[0028] Step 202: Obtain the configuration parameters for each preset NIFI component input by the user according to the first operation instruction. The configuration parameters are determined based on the specific protocol type adopted by the target device and the data types that the target device can collect.

[0029] Step 203: Generate a first template file corresponding to the target device based on the configuration parameters of each preset NIFI component.

[0030] Step 204: Send the first template file to the second terminal corresponding to the target device so that the second terminal can perform the corresponding data collection operation based on the first template file.

[0031] Before data collection, an NIFI application can be installed on the first terminal, and a MiniFI application can be installed on the second terminal of the target device. The NIFI application can include a user interface, which may contain multiple display icons. The target device can refer to the device from which data is to be collected. For example, the target device could be an engineering vehicle. When installing the NIFI application, the NIFI configuration information can be modified to ensure normal data transmission between the first and second terminals.

[0032] With the corresponding applications installed on both the first and second terminals, the processor can obtain a first operation command triggered by the user through the NIFI application's user interface, targeting a first icon. The user interface can refer to the web interface of the NIFI application. The user interface may include multiple first icons. The first icon may be a preset NIFI component's display icon within the NIFI application. The preset NIFI component may be determined from multiple NIFI components based on the specific protocol type of the target device. The NIFI component may refer to a data acquisition component. For example, NIFI components may include TailFile, ExtractText, EdgeDataProcess, ExecuteStreamCommand, PostHttp, etc.

[0033] After receiving the first operation command triggered by the user for the first icon, the processor can obtain the configuration parameters for each preset NiFi component input by the user according to the first operation command. These configuration parameters can be determined based on the specific protocol type used by the target device and the data types that the target device can collect. The specific protocol type can refer to a proprietary protocol, i.e., a private protocol. The data types that the target device can collect can include the target device's operating status data, operating trajectory data, communication log data, etc.

[0034] The processor can generate a first template file corresponding to the target device based on the configuration parameters of each preset NiFi component. This first template file can be an XML format template file. After generating the first template file, the processor can send it to the second terminal corresponding to the target device via a downlink remote upgrade channel, allowing the second terminal to perform corresponding data acquisition operations based on the first template file.

[0035] In one embodiment, such as Figure 3 The diagram illustrates a configuration of component parameters. TailFile, ExtractText, EdgeDataProcess, ExecuteStreamCommand, and PostHttp are the default NIFI component icons displayed in the NIFI application.

[0036] User-input configuration parameters for the TailFile component can include the data file location, name, and whether incremental collection is enabled. A configured TailFile component can be used to monitor device data changes and collect device data in real time. User-input configuration parameters for the ExtractText component can include regular expressions for data validation. A configured ExtractText component can be used to validate and evaluate the collected device data. User-input configuration parameters for the EdgeDataProcess component can include the parsing protocol type and bus protocol type used by the target device. A configured EdgeDataProcess component can be used to parse the collected device data from the target device. User-input configuration parameters for the ExecuteStreamCommand component can include shell scripts for executing data processing. User-input configuration parameters for the PostHttp component can include the cloud platform address and protocol type. A configured PostHttp component can be used to send the collected data to the cloud platform. The processor can obtain the user-input configuration parameters for each of the above-mentioned preset NIFI components according to the first operation instruction, and generate a first template file corresponding to the target device based on the configuration parameters of each preset NIFI component, and then send the first template file to the corresponding second terminal.

[0037] It should be noted that the aforementioned preset NiFi components can be customized according to NiFi specifications, and each developed component is reusable, eliminating the need to redevelop different components based on the target device's protocol type. That is, by configuring the configuration parameters of each developed component and generating a corresponding template file after configuration, data acquisition can be achieved using the template file. Furthermore, users are not restricted in the configuration order for each preset NiFi component; however, before completing the configuration and generating the template file, users can define the data flow direction to ensure that data processing and data storage operations are performed according to the data flow direction after the template file is generated.

[0038] The above technical solution allows for different parameter configurations of preset NIFI components on the visual interface, thereby generating template files corresponding to the preset NIFI components. When the target device uses different protocol types, data acquisition from different target devices can be achieved by configuring different parameters of the preset NIFI components. This is convenient and fast, greatly reducing the manpower and time costs required for development, eliminating the need to repeatedly develop a large number of components, further shortening the data acquisition cycle, and significantly improving the efficiency of data acquisition.

[0039] In one embodiment, the method further includes: receiving a data processing request initiated by a user, the data processing request being initiated by the user after obtaining device data of the target device by performing corresponding data collection operations on the second terminal according to the first template file; loading a second icon onto the operation interface according to the data processing request, wherein the second icon is a display icon of a preset data processing component in the NIFI application; obtaining a second operation instruction triggered by the user through the operation interface for the second icon; obtaining configuration parameters input by the user for each preset data processing component according to the second operation instruction, the configuration parameters being determined according to the specific protocol type adopted by the target device and the queue code of the data to be processed; generating a second template file corresponding to the target device according to the configuration parameters of each preset data processing component; and sending the second template file to a cloud platform, so that the cloud platform can perform corresponding data processing operations and data storage operations on the data collected by the second terminal according to the second template file.

[0040] When the second terminal acquires device data from the target device by performing corresponding data acquisition operations based on the first template file, the processor can receive a data processing request initiated by the user and load a second icon onto the operation interface according to the data processing request. The operation interface can refer to the web interface of the NIFI application. The operation interface can include multiple display icons. For example, the display icon can be the second icon. The second icon can be a preset data processing component's display icon in the NIFI application. The preset data processing component can refer to a component capable of data processing and data storage. The preset data processing component can be determined from multiple data processing components based on the acquired data type. For example, the preset data processing component can be ConsumerKafka_2.0, DataProcessor, ConvertJsonToAvro, QueryRecord, PuthbaseJson, AppendEscapeProcessor, etc.

[0041] The processor can obtain the second operation command triggered by the user through the operation interface for the second icon, and can obtain the configuration parameters for each preset data processing component input by the user based on the second operation command. These configuration parameters can be determined based on the specific protocol type used by the target device and the queue code of the data to be processed. Since the cloud platform stores device data in a corresponding Kafka topic according to the specific protocol type of the target device, the user can configure the parameters of each preset data processing component before processing the device data. Specifically, the user can input the specific protocol type of the target device corresponding to the device data to determine the corresponding Kafka topic. Then, the user can also input the queue code of the device data, i.e., the consumption address of the device data in the specified Kafka topic.

[0042] When the user inputs configuration parameters for each preset data processing component, the processor can obtain these parameters according to the second operation instruction. The processor can then generate a second template file corresponding to the target device based on the configuration parameters of each preset data processing component. This second template file can be a YAML format configuration file, i.e., a MiniFI configuration file. After generating the second template file, the processor can send it to a cloud platform so that the cloud platform can perform corresponding data processing and data storage operations on the data collected by the second terminal based on the second template file.

[0043] In one embodiment, such as Figure 4The diagram illustrates a configuration of component parameters. ConsumerKafka_2.0, DataProcessor, ConvertJsonToAvro, QueryRecord, ConvertAvroToJson, and PuthbaseJson are preset data processing components used when the data type is operational data. When the above data processing group is loaded into the NiFi application's interface according to a data processing request, the processor can obtain a second operation instruction and, based on the second operation instruction, retrieve the configuration parameters for each of the preset data processing components input by the user.

[0044] Specifically, the configuration parameters input by the user for the ConsumerKafka_2.0 component can include the Kafka topic, consumption address, and consumption strategy. A configured ConsumerKafka_2.0 component can retrieve data from Kafka for processing. In other words, the ConsumerKafka_2.0 component can be used to connect to data sources in Kafka. The configuration parameters input by the user for the DataProcessor component include data processing metadata and batch size. A configured DataProcessor component can be used to clean and transform data. The configuration parameters input by the user for the ConvertJsonToAvro component can include data structure metadata. A configured ConvertJsonToAvro component can be used to convert JSON data to Avro format data. The configuration parameters input by the user for the QueryRecord component can include SQL statements. A configured QueryRecord component can be used to filter data. Users can also configure the ConvertAvroToJson component, which can be used to convert Avro format data to JSON format data. The parameters that users input for the PutHbaseJson component can include the address of the ZooKeeper cluster and the name of the table in HBase. Once configured, the PutHbaseJson component can be used to store data in the HBase database.

[0045] The processor can obtain the configuration parameters of the aforementioned data processing components according to the second operation instruction, and generate a second template file corresponding to the target device based on the configuration parameters of the aforementioned data processing components, so as to send the second template file to the cloud platform. It should be noted that when the user configures the parameters for each preset data processing component, there is no restriction on the configuration order. However, before completing the configuration and generating the template file, the user can customize the data flow direction so that the data processing operation and data storage operation are completed according to the data flow direction after the template file is generated.

[0046] In one embodiment, such as Figure 5 The diagram illustrates a configuration of component parameters. ConsumerKafka_2.0, AppendEscapeProcessor, MergeContent, UpdateAtrribute, and PutHdfs are preset data processing components used when the data type is trajectory data. When the aforementioned data processing group is loaded into the NiFi application's user interface according to a data processing request, the processor can obtain a second operation instruction and, based on the second operation instruction, retrieve the configuration parameters for each of the preset data processing components input by the user.

[0047] Specifically, the configuration parameters input by the user for the ConsumerKafka_2.0 component can include the Kafka topic, Kafka brokers, consumer address, and consumption strategy. Once configured, the ConsumerKafka_2.0 component can retrieve the data to be processed from Kafka. In other words, the ConsumerKafka_2.0 component can be used to connect to data sources in Kafka. Users can omit configuration parameters for the AppendEscapeProcessor component, which can be used to add newline characters to the data. The configuration parameters input by the user for the MergeContent component can include MergeStrategy, Merge Format, Delimiter Strategy, Metadata Strategy, Tar Modified Time, etc. Once configured, the MergeContent component can be used to merge data files to avoid generating a large number of small files in HDFS. The configuration parameters that users input for the UpdateAttribute component can include auto-generation rules for filenames. A configured UpdateAttribute component can be used to name different data files to store data in specified HDFS files, thus distinguishing data within HDFS. The configuration parameters that users input for the PutHdfs component can include the HDFS path and the address of Hadoop-related configuration files. A configured PutHdfs component can be used to store data in the HDFS directory of a Hive database.

[0048] The processor can obtain the configuration parameters of the aforementioned data processing components according to the second operation instruction, and generate a second template file corresponding to the target device based on the configuration parameters of the aforementioned data processing components, so as to send the second template file to the cloud platform. It should be noted that when the user configures the parameters for each preset data processing component, there is no restriction on the configuration order. However, before completing the configuration and generating the template file, the user can customize the data flow direction so that the data processing operation and data storage operation are completed according to the data flow direction after the template file is generated.

[0049] In one embodiment, such as Figure 6The diagram illustrates a configuration of component parameters. ConsumerKafka_2.0, ZLRawDataProcessor, and PutHbaseJson are preset data processing components used when the data type is log data. When the aforementioned data processing group is loaded into the NiFi application's interface according to a data processing request, the processor can obtain a second operation instruction and, based on the second operation instruction, retrieve the configuration parameters for each of the preset data processing components input by the user.

[0050] Specifically, the configuration parameters input by the user for the ConsumerKafka_2.0 component can include the Kafka topic, consumption address, and consumption strategy. A configured ConsumerKafka_2.0 component can then retrieve the data to be processed from Kafka. In other words, the ConsumerKafka_2.0 component can be used to connect to data sources in Kafka. The configuration parameters input by the user for the ZLRawDataProcessor component can include the data direction and type. A configured ZLRawDataProcessor component can be used to convert data formats, parse data, add data tags, and add data fields. The parameters input by the user for the PutHbaseJson component can include the address of the ZooKeeper cluster and the name of the table in HBase. A configured PutHbaseJson component can be used to store data in an HBase database.

[0051] The processor can obtain the configuration parameters of the aforementioned data processing components according to the second operation instruction, and generate a second template file corresponding to the target device based on the configuration parameters of the aforementioned data processing components, so as to send the second template file to the cloud platform. It should be noted that when the user configures the parameters for each preset data processing component, there is no restriction on the configuration order. However, before completing the configuration and generating the template file, the user can customize the data flow direction so that the data processing operation and data storage operation are completed according to the data flow direction after the template file is generated.

[0052] The aforementioned preset data processing components can be customized according to NiFi specifications, and each developed component can be reused without needing to be redeveloped based on the target device's protocol type. This technical solution allows for the configuration parameters of each developed component to be configured, and a corresponding template file is generated upon configuration. This enables timely and accurate data processing and storage based on the template file, significantly improving data processing efficiency and facilitating subsequent data retrieval and analysis.

[0053] In one embodiment, a storage medium is provided having a program stored thereon that, when executed by a processor, implements the above-described method for acquiring data, the method being applied to a first terminal having an NIFI application installed.

[0054] In one embodiment, a processor is provided for running a program, wherein the program executes the above-described method for acquiring data, the method being applied to a first terminal having an NIFI application installed.

[0055] Figure 7 A schematic flowchart illustrating a method for collecting data according to an embodiment of this application is shown. Figure 7 As shown, in one embodiment of this application, a method for collecting data is provided. This embodiment mainly applies this method to the above-mentioned... Figure 1 Taking the second terminal 102 as an example, the method includes the following steps:

[0056] Step 701: Receive the first template file sent by the first terminal. The first template file is generated by the user configuring the corresponding parameters of the preset nifi components through the operation interface of the nifi application. The first terminal has the nifi application installed.

[0057] Step 702: Convert the first template file into a configuration file of the corresponding specific format.

[0058] Step 703: Upon receiving a data collection instruction from the cloud platform, collect device data from the target device in real time according to a configuration file in a specific format.

[0059] Before data collection, an NIFI application can be installed on the first terminal, and a MiniFI application can be installed on the second terminal of the target device. The processor can receive a first template file sent by the first terminal. The first terminal may have an NIFI application installed. The first template file is generated after the user configures the corresponding parameters of preset NIFI components through the NIFI application's interface. The first template file may refer to an XML format template file. The interface may refer to the web interface of the NIFI application. The interface may include multiple first icons. The first icons may be the display icons of preset NIFI components in the NIFI application. The preset NIFI components may be determined from multiple NIFI components based on the specific protocol type of the target device. NIFI components may refer to data acquisition components. For example, NIFI components may include TailFile, ExtractText, EdgeDataProcess, ExecuteStreamCommand, PostHttp, etc.

[0060] The processor can convert the first template file into a corresponding configuration file in a specific format. This specific format configuration file can refer to a YAML format configuration file, i.e., a MiniFI configuration file. The processor can receive data acquisition commands sent by the cloud platform and then collect device data from the target device in real time according to the specific format configuration file. The target device can refer to the device from which data is to be collected. For example, the target device could be an engineering vehicle. If the target device uses a specific protocol type, i.e., a private protocol, the device data collected by the processor in real time according to the specific format configuration file will be encrypted data.

[0061] The above technical solution can convert the template file sent by the first terminal into a configuration file of a specific format, and collect device data of the target device in real time according to the configuration file of the specific format when a data collection instruction is received. This is convenient and fast, greatly reduces the data collection time cycle, and significantly improves the efficiency of data collection.

[0062] In one embodiment, real-time acquisition of device data of a target device according to a configuration file of a specific format includes: real-time acquisition of encrypted data of the target device according to the configuration file of a specific format; parsing the encrypted data into plaintext data; and sending the plaintext data to a cloud platform for data storage.

[0063] The processor can collect encrypted data from the target device in real time according to a configuration file of a specific format. This specific format configuration file can refer to a YAML format configuration file, i.e., a Minifi configuration file. The encrypted data can refer to data encrypted using a private protocol; that is, the target device uses a private protocol. Upon collecting the encrypted data from the target device, the processor can parse it into plaintext data and send it to a cloud platform for data storage. The plaintext data can refer to unencrypted data.

[0064] In one embodiment, the target device uses a specific protocol type called a private protocol. Parsing the ciphertext data into plaintext data includes: loading a corresponding parser according to the private protocol to parse the ciphertext data, wherein the parser is generated according to the protocol type used by different types of target devices; and parsing the ciphertext data into plaintext data in a preset format using the parser.

[0065] The target device can use a private protocol. The parser can be generated based on the protocol type used by different types of target devices. Specifically, the cloud platform can obtain the bus transmission protocol and data parsing protocol of the target device. Then, the cloud platform can generate a class file corresponding to the bus transmission protocol and data parsing protocol of the target device based on its constructed parsing service, and compile the class file into the corresponding bytecode file, i.e., the parser. With the parser generated, the cloud platform can distribute the parser to the second terminal of the target device through a downlink remote upgrade channel.

[0066] When the processor collects encrypted data from the target device in real time according to a configuration file of a specific format, the processor can load the corresponding parser according to the privacy protocol to parse the encrypted data. Furthermore, the processor can use the parser to parse the encrypted data into plaintext data in a preset format. Plaintext data in the preset format can refer to plaintext data with the format "start character + command code + serial number + terminal ID + protocol type + terminal type + protocol version + data length + data block + checksum + end character".

[0067] In one embodiment, the second terminal is equipped with a minifi application, and converting the first template file into a corresponding configuration file of a specific format includes: calling a file converter in the minifi application; and converting the first template file into a minifi configuration file using the file converter.

[0068] The second terminal is equipped with a Minifi application. The processor can convert the first template file into a corresponding configuration file in a specific format. Specifically, the processor can invoke the file converter within the Minifi application, and use the file converter to convert the first template file into a Minifi configuration file. The first template file can be an XML file. The file converter can be the ToolKit converter within the Minifi application. The ToolKit converter can convert the XML template file into a YAML file. The YAML file is the Minifi configuration file.

[0069] The above technical solution can convert the first template file sent by the first terminal into a configuration file of a specific format, and collect and parse the device data of the target device through the configuration file of the specific format. This is convenient and fast, and greatly reduces the manpower and time costs required for development. It eliminates the need to repeatedly develop a large number of components, further shortens the data collection time cycle, and greatly improves the efficiency of data collection.

[0070] In one embodiment, an engineering vehicle is provided, the engineering vehicle including: a second terminal; and the processor described above, the processor being configured to execute the method described above for collecting data, the method being applied to the second terminal corresponding to the target device.

[0071] In one embodiment, a storage medium is provided on which a program is stored, which, when executed by a processor, implements the above-described method for collecting data, and the method is applied to a second terminal corresponding to the target device.

[0072] In one embodiment, a processor is provided for running a program, wherein the program executes the above-described method for collecting data, and the method is applied to a second terminal corresponding to the target device.

[0073] Figure 8 A schematic flowchart illustrating a method for collecting data according to an embodiment of this application is shown. Figure 8 As shown, in one embodiment of this application, a method for collecting data is provided. This embodiment mainly applies this method to the above-mentioned... Figure 1 Taking cloud platform 103 as an example, the method includes the following steps:

[0074] Step 801: Receive plaintext data from the target device sent by the second terminal of the target device. The plaintext data is determined by parsing the ciphertext data with a parser corresponding to the specific protocol type used by the target device. The ciphertext data is collected in real time by the second terminal according to a configuration file of a specific format.

[0075] Step 802: The plaintext data is temporarily stored in a designated topic of Kafka through a message queue. The designated topic refers to the topic corresponding to the specific protocol type of the target device.

[0076] Step 803: Receive the second template file sent by the first terminal. The second template file is generated by the user configuring the corresponding parameters of the preset data processing components through the operation interface of the first terminal's NIFI application.

[0077] Step 804: Preprocess the plaintext data according to the second template file to obtain structured plaintext data.

[0078] Step 805: Store the structured plaintext data in the database.

[0079] After the second terminal collects encrypted data in real time according to a configuration file of a specific format, it can load a parser corresponding to the specific protocol type used by the target device and use the parser to parse the collected encrypted data into plaintext data. Once the second terminal determines the plaintext data of the target device, it can send the plaintext data to the cloud platform.

[0080] The processor can receive plaintext data from the target device sent by the second terminal. The specific format configuration file can refer to a YAML format configuration file, i.e., a Minifi configuration file. The specific protocol type can refer to a private protocol. Ciphertext data can refer to data encrypted using a private protocol. Plaintext data can refer to plaintext data with a preset format of "start character + command code + serial number + terminal ID + protocol type + terminal type + protocol version + data length + data block + checksum + end character".

[0081] Processors can temporarily store plaintext data in a designated Kafka topic using a message queue. This designated topic can refer to a topic corresponding to a specific protocol type of the target device. For example, ... Figure 9 The diagram illustrates a configuration of component parameters. Here, `from Minifi` and `PublishKafka_2.0` can refer to the data acquisition components of the Minifi application. `from Minifi` and `PublishKafka_2.0` can be connected via a message queue, which provides queue caching. After configuring `from Minifi` and `PublishKafka_2.0` on the first terminal, a template file can be generated and sent to the cloud platform. The processor can receive plaintext data from the target device via `from Minifi` and temporarily store the plaintext data in a designated Kafka topic via the message queue and PublishKafka_2.0. A designated Kafka topic can refer to temporary storage space allocated according to the specific protocol type of the target device.

[0082] The processor can receive a second template file sent by the first terminal. The first terminal can refer to a terminal with the NIFI application installed. The second template file can refer to a YAML format configuration file, i.e., a MiniFI configuration file. The second template file is generated by the user configuring the corresponding parameters of the preset data processing components through the user interface of the NIFI application on the first terminal.

[0083] Upon receiving the second template file, the processor can preprocess the plaintext data according to the template file. Specifically, the processor can first obtain the corresponding plaintext data based on the second template file. Then, the processor can perform structured processing on the plaintext data, such as data transformation and data cleaning, to obtain structured plaintext data. That is, preprocessing methods can include data transformation and data cleaning. The processor can store the structured plaintext data in a database. The database can include HBase, Hive, Elasticsearch, and CansSandra, among others.

[0084] In one embodiment, the method further includes: determining the specific protocol type used by the target device before receiving plaintext data from the target device sent by the second terminal; compiling and generating a parser corresponding to the target device according to the specific protocol type; and sending the parser to the second terminal so that the second terminal can parse the collected ciphertext data into plaintext data through the parser.

[0085] Before receiving plaintext data from the target device sent by the second terminal, the processor can determine the specific protocol type used by the target device. This specific protocol type can be a private protocol. Then, the processor can compile and generate a parser corresponding to the target device based on the specific protocol type, and send the parser to the second terminal so that the second terminal can parse the collected ciphertext data into plaintext data. Here, the second terminal can refer to the target device's secondary terminal. The ciphertext data can refer to data encrypted using a private protocol. The plaintext data can refer to plaintext data with a preset format of "start character + command code + serial number + terminal ID + protocol type + terminal type + protocol version + data length + data block + checksum + end character".

[0086] The above technical solution converts collected plaintext data into structured data based on template files and stores the structured data in a corresponding database, enabling effective processing and classification of large amounts of data. This also allows for more convenient and faster retrieval of relevant data when subsequent data analysis is needed.

[0087] In one embodiment, a storage medium is provided on which a program is stored, which, when executed by a processor, implements the above-described method for acquiring data, the method being applied to a cloud platform.

[0088] In one embodiment, a processor is provided for running a program, wherein the program executes the above-described method for collecting data, the method being applied to a cloud platform.

[0089] Figure 10 A schematic flowchart illustrating a method for collecting data according to an embodiment of this application is shown. Figure 10 As shown in one embodiment of this application, a method for collecting data is provided, the method comprising the following steps:

[0090] Step 1001: The first terminal obtains a first operation command triggered by the user through the operation interface of the nifi application for a first icon. The first icon is a display icon of a preset nifi component in the nifi application. The preset nifi component is determined from multiple nifi components according to the specific protocol type of the target device.

[0091] Step 1002: The first terminal obtains the configuration parameters for each preset NIFI component input by the user according to the first operation instruction. The configuration parameters are determined according to the specific protocol type adopted by the target device and the data types that the target device can collect.

[0092] Step 1003: The first terminal generates a first template file corresponding to the target device based on the configuration parameters of each preset NIFI component, and sends the first template file to the second terminal corresponding to the target device.

[0093] Step 1004: The second terminal receives the first template file and converts the first template file into a configuration file of a specific format.

[0094] Step 1005: The cloud platform sends a data collection command to the second terminal.

[0095] Step 1006: When the second terminal receives the data acquisition instruction, the second terminal acquires the device data of the target device in real time according to the configuration file of a specific format.

[0096] Step 1007: The second terminal sends the device data to the cloud platform.

[0097] The first terminal may have an NIFI application installed. The NIFI application may include a user interface. This user interface may refer to the web interface of the NIFI application. The user interface may include multiple display icons. For example, the display icon may be a first icon. The first icon is the display icon of a preset NIFI component in the NIFI application. The preset NIFI component is determined from multiple NIFI components based on the specific protocol type of the target device. The NIFI component may refer to a data acquisition component. For example, NIFI components may include TailFile, ExtractText, EdgeDataProcess, ExecuteStreamCommand, PostHttp, etc.

[0098] When collecting data, the first terminal can first obtain the first operation command triggered by the user through the NiFi application's interface, targeting the first icon. Then, the first terminal can obtain the configuration parameters input by the user for each preset NiFi component based on the first operation command. These configuration parameters can be determined based on the specific protocol type used by the target device and the types of data that the target device can collect. The specific protocol type can refer to a proprietary protocol, i.e., a private protocol. The types of data that the target device can collect can include the target device's operating status data, operational trajectory data, communication log data, etc.

[0099] The first terminal can generate a first template file corresponding to the target device based on the configuration parameters of each preset NiFi component. This first template file can be an XML format template file. After generating the first template file, the first terminal can send it to the second terminal corresponding to the target device via a downlink remote upgrade channel. The second terminal can receive the first template file and convert it into a configuration file of a specific format. This specific format configuration file can be a YAML format configuration file, i.e., a MiniFi configuration file.

[0100] The cloud platform can send data collection commands to the second terminal. Upon receiving the command, the second terminal collects device data from the target device in real time according to a specific configuration file format. The target device can refer to the device from which data is to be collected. For example, the target device could be an engineering vehicle. If the target device uses a specific protocol type, the collected device data can be encrypted data. Once the second terminal has collected the device data from the target device, it can send the data to the cloud platform.

[0101] The above technical solution allows for different parameter configurations of preset NIFI components on the visual interface, thereby generating template files corresponding to the preset NIFI components. When the target device uses different protocol types, data acquisition from different target devices can be achieved by configuring different parameters of the preset NIFI components. This is convenient and fast, greatly reducing the manpower and time costs required for development, eliminating the need to repeatedly develop a large number of components, further shortening the data acquisition cycle, and significantly improving the efficiency of data acquisition.

[0102] In one embodiment, the second terminal is equipped with a minifi application, and converting the first template file into a corresponding configuration file of a specific format includes: the second terminal calling a file converter in the minifi application to convert the first template file into a corresponding minifi configuration file through the file converter.

[0103] The second terminal can have a Minifi application deployed on it. This application allows the second terminal to convert the first template file into a configuration file of a specific format. Specifically, the second terminal can call a file converter within the Minifi application to convert the first template file into a Minifi configuration file. The first template file can be an XML file. The file converter can be the ToolKit converter within the Minifi application. The ToolKit converter can convert the XML template file into a YAML file. The YAML file is the Minifi configuration file.

[0104] In one embodiment, the device data is encrypted data, and the method further includes: determining the specific protocol type used by the target device through a cloud platform; the cloud platform compiles and generates a parser corresponding to the target device according to the specific protocol type, and sends the parser to the second terminal; when the second terminal receives the parser, the second terminal loads the corresponding parser according to the private protocol, and parses the encrypted data into plaintext data of a preset format through the parser; the second terminal sends the plaintext data to the cloud platform.

[0105] The device data is encrypted data. Encrypted data refers to data encrypted using a private protocol. That is, the target device uses a private protocol. The specific protocol type used by the target device can be determined through a cloud platform. The cloud platform can compile and generate a parser corresponding to the target device based on the specific protocol type and send the parser to a second terminal. The second terminal can load the corresponding parser according to the private protocol and use the parser to parse the encrypted data into plaintext data of a preset format. The second terminal can then send the plaintext data to the cloud platform. Here, the second terminal can refer to a secondary terminal of the target device. The plaintext data can refer to plaintext data with a preset format of "start character + command code + serial number + terminal ID + protocol type + terminal type + protocol version + data length + data block + checksum + end character".

[0106] In one embodiment, the method further includes: a first terminal receiving a data processing request initiated by a user, the data processing request being initiated by the user after obtaining device data of the target device by performing a corresponding data acquisition operation on a second terminal according to a first template file; the first terminal loading a second icon onto the operation interface according to the data processing request, wherein the second icon is a display icon of a preset data processing component in the NIFI application; the first terminal obtaining a second operation instruction triggered by the user through the operation interface for the second icon; the first terminal obtaining configuration parameters for each preset data processing component input by the user according to the second operation instruction, the configuration parameters being determined according to the specific protocol type adopted by the target device and the queue code of the data to be processed; the first terminal generating a second template file corresponding to the target device according to the configuration parameters of each preset data processing component; and the first terminal sending the second template file to a cloud platform.

[0107] When the second terminal acquires device data from the target device by performing corresponding data acquisition operations based on the first template file, the first terminal can receive data processing requests initiated by the user and load a second icon onto the operation interface according to the data processing request. The operation interface can refer to the web interface of the NIFI application. The operation interface can include multiple display icons. For example, the display icon can be the second icon. The second icon can be a preset data processing component's display icon in the NIFI application. The preset data processing component can refer to a component capable of data processing and data storage. The preset data processing component can be determined from multiple data processing components based on the acquired data type. For example, the preset data processing component can be ConsumerKafka_2.0, DataProcessor, ConvertJsonToAvro, QueryRecord, PuthbaseJson, AppendEscapeProcessor, etc.

[0108] The first terminal can obtain a second operation command triggered by the user through the operation interface for the second icon, and can obtain the configuration parameters for each preset data processing component input by the user based on the second operation command. The configuration parameters can be determined based on the specific protocol type used by the target device and the queue code of the data to be processed. Since the cloud platform stores device data in a designated Kafka topic according to the specific protocol type of the target device, the user can configure the parameters for each preset data processing component before processing the device data. Specifically, the user can input the specific protocol type of the target device corresponding to the device data to determine the designated Kafka topic corresponding to the device data. Then, the user can also input the queue code of the device data, i.e., the consumption address of the device data in the designated Kafka topic. When the user inputs the configuration parameters for each preset data processing component, the first terminal can obtain the configuration parameters based on the second operation command.

[0109] The first terminal can generate a second template file corresponding to the target device based on the configuration parameters of each preset data processing component. This second template file can be a YAML format configuration file, i.e., a Minifi configuration file. The first terminal can send the second template file to a cloud platform, which will then perform corresponding data processing and data storage operations on the data collected by the second terminal based on the template file.

[0110] In one embodiment, the method further includes: a cloud platform receiving plaintext data from a target device sent by a second terminal; the cloud platform temporarily storing the plaintext data in a designated topic in Kafka via a message queue, wherein the designated topic refers to a topic corresponding to a specific protocol type of the target device; when the cloud platform receives a second template file sent by a first terminal, the cloud platform preprocesses the plaintext data temporarily stored in the designated topic in Kafka according to the second template file to obtain structured plaintext data; and the cloud platform stores the structured plaintext data in a database.

[0111] The cloud platform can receive plaintext data from the target device sent by a second terminal. This plaintext data can refer to data in a pre-defined format: "Start Character + Command Code + Serial Number + Terminal ID + Protocol Type + Terminal Type + Protocol Version + Data Length + Data Block + Checksum + End Character". Upon receiving the plaintext data from the target device, the cloud platform can temporarily store it in a designated Kafka topic using a message queue. This designated topic can be one corresponding to the specific protocol type of the target device.

[0112] The first terminal can refer to a terminal with the NiFi application installed. The second template file can refer to a MiniFi configuration file. The second template file is generated by the first terminal based on the configuration parameters of the preset data processing components after the user configures the corresponding parameters through the NiFi application's interface. When the first terminal generates the second template file and sends it to the cloud platform, the cloud platform can receive the second template file and preprocess the plaintext data temporarily stored in a specified topic in Kafka according to the second template file to obtain structured plaintext data. Preprocessing methods can include data transformation and data cleaning. Once the cloud platform obtains the structured plaintext data, it can store the structured plaintext data in a database. The database can be HBase, Hive, Elasticsearch, or CansSandra, among others.

[0113] In one embodiment, a storage medium is provided on which a program is stored, which, when executed by a processor, implements the above-described method for acquiring data.

[0114] In one embodiment, a processor is provided for running a program, wherein the program executes the above-described method for acquiring data during runtime.

[0115] In one embodiment, the target equipment can be an engineering vehicle. Here, an engineering vehicle refers to a vehicle capable of performing mechanical construction. For example, an engineering vehicle can be a loader, bulldozer, excavator, or concrete mixer truck.

[0116] Figure 2 , Figure 7 , Figure 8 as well as Figure 10 This is a flowchart illustrating a method for data acquisition in one embodiment. It should be understood that, although... Figure 2 , Figure 7 , Figure 8 as well as Figure 10 The steps in the flowchart are shown sequentially as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order in which these steps are executed, and they can be performed in other orders. Figure 2 , Figure 7 , Figure 8 as well as Figure 10At least some of the steps in the process may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least some of the sub-steps or stages of other steps.

[0117] In one embodiment, such as Figure 11 As shown, a system for collecting data is provided, including a first device 1101, a second device 1102, and a cloud device 1103, wherein:

[0118] The first device 1101 includes a processor 1, wherein the processor 1 is configured to execute the above-described method for acquiring data, and the first device 1101 is installed on a first terminal, the first terminal having an NIFI application installed.

[0119] The second device 1102 includes a processor 2, wherein the processor 2 is configured to perform the above-described method for acquiring data, and the second device 1102 is installed on the target device.

[0120] The cloud device 1103 includes a processor 3, wherein the processor 3 is configured to perform the above-described method for acquiring data, and the cloud device 1103 is installed on a cloud platform.

[0121] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 12 As shown in the figure, the computer device includes a processor A01, a network interface A02, a display screen A04, an input device A05, and a memory (not shown) connected via a system bus. The processor A01 provides computing and control capabilities. The memory includes internal memory A03 and a non-volatile storage medium A06. The non-volatile storage medium A06 stores an operating system B01 and a computer program B02. The internal memory A03 provides an environment for the operation of the operating system B01 and the computer program B02 stored in the non-volatile storage medium A06. The network interface A02 is used for communication with external terminals via a network connection. When the computer program is executed by the processor A01, it implements a method for data acquisition. The display screen A04 can be a liquid crystal display (LCD) or an e-ink display. The input device A05 can be a touch layer covering the display screen, buttons, a trackball, or a touchpad mounted on the computer device casing, or an external keyboard, touchpad, or mouse.

[0122] Those skilled in the art will understand that Figure 12The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0123] This application provides an apparatus including a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, it implements the steps of the above-described method for acquiring data.

[0124] This application also provides a computer program product that, when executed on a data processing device, is adapted to execute a program having method steps for initializing data acquisition.

[0125] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0126] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0127] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0128] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0129] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0130] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0131] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0132] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0133] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for collecting data, characterized in that, The method includes: The first terminal obtains a first operation command triggered by the user through the operation interface of the nifi application for a first icon. The first icon is a display icon of a preset nifi component in the nifi application. The preset nifi component is determined from multiple nifi components according to the specific protocol type of the target device. The first terminal obtains the configuration parameters for each preset NIFI component input by the user according to the first operation instruction. The configuration parameters are determined according to the specific protocol type adopted by the target device and the data types that the target device can collect. The first terminal generates a first template file corresponding to the target device based on the configuration parameters of each preset NiFi component, and sends the first template file to the second terminal corresponding to the target device; The second terminal receives the first template file and converts it into a configuration file of a specific format. The cloud platform sends a data collection command to the second terminal; When the second terminal receives the data acquisition instruction, the second terminal acquires the device data of the target device in real time according to the configuration file in the specific format; The second terminal sends the device data to the cloud platform.

2. The method for collecting data according to claim 1, characterized in that, The second terminal is equipped with a minifi application, which converts the first template file into a corresponding configuration file in a specific format, including: The second terminal invokes the file converter in the minifi application to convert the first template file into the corresponding minifi configuration file.

3. The method for collecting data according to claim 1, characterized in that, The device data is encrypted data, and the method further includes: The specific protocol type used by the target device is determined through the cloud platform; The cloud platform compiles and generates a parser corresponding to the target device according to the specific protocol type, and sends the parser to the second terminal; When the second terminal receives the parser, the second terminal loads the corresponding parser according to the privacy protocol and uses the parser to parse the ciphertext data into plaintext data in a preset format. The second terminal sends the plaintext data to the cloud platform.

4. The method for collecting data according to claim 1, characterized in that, The method further includes: The first terminal receives a data processing request initiated by the user. The data processing request is initiated by the user after the second terminal performs a corresponding data collection operation based on the first template file to obtain the device data of the target device. The first terminal loads the second icon onto the operation interface according to the data processing request, wherein the second icon is a preset display icon of the data processing component in the nifi application; The first terminal acquires a second operation command triggered by the user through the operation interface for the second icon; The first terminal obtains the configuration parameters for each preset data processing component input by the user according to the second operation instruction. The configuration parameters are determined according to the specific protocol type adopted by the target device and the queue code of the data to be processed. The first terminal generates a second template file corresponding to the target device based on the configuration parameters of each preset data processing component; The first terminal sends the second template file to the cloud platform.

5. The method for collecting data according to claim 1, characterized in that, The method further includes: The cloud platform receives plaintext data from the target device sent by the second terminal; The cloud platform temporarily stores the plaintext data to a designated topic in Kafka via a message queue. The designated topic refers to the topic corresponding to a specific protocol type of the target device. When the cloud platform receives the second template file sent by the first terminal, the cloud platform preprocesses the plaintext data of the specified topic temporarily stored in Kafka according to the second template file to obtain structured plaintext data; The cloud platform stores the structured plaintext data in a database.

6. The method for collecting data according to any one of claims 1 to 5, characterized in that, The target equipment is an engineering vehicle.

7. A processor, characterized in that, It is configured to perform the method for collecting data as described in any one of claims 1 to 5.

8. A machine-readable storage medium storing instructions thereon, characterized in that, When executed by a processor, this instruction causes the processor to be configured to perform the method for acquiring data according to any one of claims 1 to 5.

Images