Data collection method, device, computer equipment and storage medium

Abstract

The present application relates to a data collection method, device, computer equipment and storage medium. The method comprises: a first node receives a report message sent by a second node; the report message comprises a data identifier and current report data, and the data identifier is used to uniquely indicate a historical report data of the second node; the first node parses the report message to obtain the data identifier and the current report data; the historical report data is obtained according to the data identifier and data record information, and the data record information is used to indicate the mapping relationship between multiple historical report data and multiple data identifiers. The use of this method can reduce the size of the report message. During the transmission of the report message, the bandwidth occupancy is reduced to avoid the waste of network resources.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a data acquisition method, device, computer equipment and storage medium. Background Art

[0002] Telemetry is a technology that collects data remotely from physical or virtual devices at high speed. It collects device information by periodically sending interface traffic statistics, CPU, or memory data to the server.

[0003] In the process of collecting device information, the server often collects specific information content. For example, when collecting the traffic of a certain interface in real time, it often collects the device information to which the interface belongs, the interface name information of the interface, the status information of the interface, the current time, and the specific traffic information of the interface at the current time.

[0004] The above information collection method often causes the server to collect a large amount of duplicate information, such as the device information to which the above interface belongs, the interface name information, and the interface status information, which results in high bandwidth usage and waste of network resources. Summary of the invention

[0005] The present application proposes a data collection method, apparatus, computer equipment and storage medium, which can replace repeated information in reported information by identification, reduce the size of reported messages, thereby reducing bandwidth occupancy and avoiding waste of network resources.

[0006] In a first aspect, the present application provides a data collection method. The method comprises:

[0007] The first node receives a report message sent by the second node; the report message includes a data identifier and current reported data, and the data identifier is used to uniquely indicate a historical reported data of the second node;

[0008] The first node parses the report message to obtain the data identifier and the current report data;

[0009] The historical reported data is acquired according to the data identifier and the data record information, where the data record information is used to indicate a mapping relationship between a plurality of historical reported data and a plurality of data identifiers.

[0010] In one of the embodiments, the data collection method further includes: the first node receives data record information sent by the second node; the data record information is generated according to the data identifier of each historical reported data when the second node collects multiple historical reported data.

[0011] In one of the embodiments, the data collection method further includes: receiving a plurality of historical reported data sent by the second node, and assigning a unique data identifier to each historical reported data; and generating data record information according to a mapping relationship between the plurality of historical reported data and the data identifier.

[0012] In one of the embodiments, allocating a unique data identifier to each historically reported data includes: allocating a data identifier to the historically reported data according to device information corresponding to the historically reported data.

[0013] In one of the embodiments, the data collection method further includes: sending data record information to the second node.

[0014] In one embodiment, the historically reported data is data corresponding to a single attribute parameter, or is data corresponding to multiple attribute parameters.

[0015] In one embodiment, the first node is a decoder and the second node is an encoder.

[0016] In a second aspect, the present application also provides a data collection method. The method comprises:

[0017] The second node determines the data to be reported, and determines the historical reported data and the current reported data corresponding to the data to be reported according to the data repeatability; the data identifier is used to uniquely indicate a historical reported data of the second node;

[0018] Determine the data identifier corresponding to the historical reported data according to the data record information; the data record information is used to indicate the mapping relationship between multiple historical reported data and multiple data identifiers;

[0019] A reporting message is generated according to the data identifier and the current reporting data, and the reporting message is sent to the first node.

[0020] In one of the embodiments, the data collection method further includes: after collecting the historical reported data, assigning a unique data identifier to the historical reported data according to the device information corresponding to the historical reported data; and generating data record information according to the mapping relationship between multiple historical reported data and the data identifiers.

[0021] In one of the embodiments, the data collection method further includes: updating or deleting the data identifier in the data record information according to the change of the data content.

[0022] In a third aspect, the present application also provides a data acquisition device. The device comprises:

[0023] A receiving module, used to receive a report message sent by the second node; the report message includes a data identifier and current reported data, and the data identifier is used to uniquely indicate a historical reported data of the second node;

[0024] A parsing module, used to parse the reported message to obtain the data identifier and the current reported data;

[0025] The acquisition module is used to acquire historical reported data according to the data identifier and data record information, where the data record information is used to indicate the mapping relationship between multiple historical reported data and multiple data identifiers.

[0026] In a fourth aspect, the present application also provides a data acquisition device. The device comprises:

[0027] The module for determining data to be reported is used to determine the data to be reported, and determine the historical reported data and the current reported data corresponding to the data to be reported according to the data repeatability; the data identifier is used to uniquely indicate a historical reported data of the second node;

[0028] A data identification determination module is used to determine the data identification corresponding to the historical reported data according to the data record information; the data record information is used to indicate the mapping relationship between multiple historical reported data and multiple data identifications;

[0029] The generating module is used to generate a reporting message according to the data identifier and the current reporting data, and send the reporting message to the first node.

[0030] In a fifth aspect, the present application further provides a computer device. The computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:

[0031] The first node receives a report message sent by the second node; the report message includes a data identifier and current reported data, and the data identifier is used to uniquely indicate a historical reported data of the second node;

[0032] The first node parses the report message to obtain the data identifier and the current report data;

[0033] The historical reported data is acquired according to the data identifier and the data record information, where the data record information is used to indicate a mapping relationship between a plurality of historical reported data and a plurality of data identifiers.

[0034] The second node determines the data to be reported, and determines the historical reported data and the current reported data corresponding to the data to be reported according to the data repeatability; the data identifier is used to uniquely indicate a historical reported data of the second node;

[0035] Determine the data identifier corresponding to the historical reported data according to the data record information; the data record information is used to indicate the mapping relationship between multiple historical reported data and multiple data identifiers;

[0036] A reporting message is generated according to the data identifier and the current reporting data, and the reporting message is sent to the first node.

[0037] In a sixth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0038] The first node receives a report message sent by the second node; the report message includes a data identifier and current reported data, and the data identifier is used to uniquely indicate a historical reported data of the second node;

[0039] The first node parses the report message to obtain the data identifier and the current report data;

[0040] The historical reported data is acquired according to the data identifier and the data record information, where the data record information is used to indicate a mapping relationship between a plurality of historical reported data and a plurality of data identifiers.

[0041] The second node determines the data to be reported, and determines the historical reported data and the current reported data corresponding to the data to be reported according to the data repeatability; the data identifier is used to uniquely indicate a historical reported data of the second node;

[0042] Determine the data identifier corresponding to the historical reported data according to the data record information; the data record information is used to indicate the mapping relationship between multiple historical reported data and multiple data identifiers;

[0043] A reporting message is generated according to the data identifier and the current reporting data, and the reporting message is sent to the first node.

[0044] In a seventh aspect, the present application further provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0045] The first node receives a report message sent by the second node; the report message includes a data identifier and current reported data, and the data identifier is used to uniquely indicate a historical reported data of the second node;

[0046] The first node parses the report message to obtain the data identifier and the current report data;

[0047] The historical reported data is acquired according to the data identifier and the data record information, where the data record information is used to indicate a mapping relationship between a plurality of historical reported data and a plurality of data identifiers.

[0048] The second node determines the data to be reported, and determines the historical reported data and the current reported data corresponding to the data to be reported according to the data repeatability; the data identifier is used to uniquely indicate a historical reported data of the second node;

[0049] Determine the data identifier corresponding to the historical reported data according to the data record information; the data record information is used to indicate the mapping relationship between multiple historical reported data and multiple data identifiers;

[0050] A reporting message is generated according to the data identifier and the current reporting data, and the reporting message is sent to the first node.

[0051] The present application provides a data collection method, device, computer equipment and storage medium. The second node can replace the historical reported data in the data to be reported by the data identifier, and send the report message generated according to the data identifier and the current reported data to the first node. The first node can obtain the data identifier in the report message by parsing the report message sent by the second node, and obtain the historical reported data corresponding to the data identifier in the above report message according to the one-to-one correspondence between the data identifier and the historical reported data in the data record information, so that the complete reported data can be determined according to the historical reported data and the current reported data. It can be seen that the present application can reduce the size of the reported data by replacing the historical reported data with the data identifier, and further reduce the size of the reported message. Thereby, the bandwidth occupancy can be reduced during the transmission of the report message to avoid the waste of network resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1 An application environment diagram of a data collection method in an embodiment;

[0053] Figure 2 A schematic diagram of a flow chart of a data collection method in one embodiment;

[0054] Figure 3 Another schematic diagram of a data collection method in one embodiment;

[0055] Figure 4 Another schematic diagram of a data collection method in one embodiment;

[0056] Figure 5 Another schematic diagram of a data collection method in one embodiment;

[0057] Figure 6 is a structural block diagram of a data acquisition device in one embodiment;

[0058] Figure 7 is another structural block diagram of a data acquisition device in one embodiment;

[0059] Figure 8 is an internal structure diagram of a computer device in one embodiment;

[0060] Fig. 9 FIG. 4 is another internal structure diagram of a computer device in one embodiment. DETAILED DESCRIPTION

[0061] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0062] The data collection method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. Figure 1 The application environment may include a server 10 and a terminal 20. The server 10 may receive information sent by the terminal 20.

[0063] The server 10 may be implemented as an independent server or a server cluster composed of multiple servers. The terminal 20 may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, IoT devices, and portable wearable devices, etc. The IoT devices may be smart speakers, smart TVs, smart air conditioners, smart car-mounted devices, etc. The portable wearable devices may be smart watches, smart bracelets, head-mounted devices, etc. The server 10 and the terminal 20 may communicate via wired or wireless means, which is not limited in this application.

[0064] It should be noted that the application environment applicable to the method may include not only a server and a terminal, but also any two devices that can report and receive information, or any two modules that can report and receive information. For example, an encoder is installed on the terminal, and a decoder is installed on the corresponding server. The data processing system composed of the encoder and the decoder implements the data collection method provided in the embodiment of the present application.

[0065] At present, in the process of collecting device information, the way of collecting the specific content of the information often causes the server to collect a large amount of duplicate information, which in turn causes a high bandwidth occupancy during the information reporting process, resulting in a waste of network resources.

[0066] Based on this, the present application provides a data collection method, which can replace repeated information in reported information by identification, thereby reducing the size of the reported message, reducing bandwidth occupancy, and avoiding waste of network resources. Figure 2 The flowchart of the data collection method provided in the embodiment of the present application is illustrated by taking the method applied to the first node as an example, and specifically includes the following steps:

[0067] Step 201: A first node receives a report message sent by a second node; the report message includes a data identifier and current reported data, and the data identifier is used to uniquely indicate a historical reported data of the second node;

[0068] The first node is a device or module for receiving information, for example, the first node can be a server, a decoder installed on the server, or a separate decoding device; the second node is a device or module for sending information, for example, the second node can be a terminal, an encoder installed on the terminal, or a separate encoding device. The report message is information sent by the second node, and can include a data identifier and current reported data; the data identifier is used to uniquely indicate a historical reported data of the second node; the current reported data is data that has not been sent by the second node before the current moment; the historical reported data is repeated data in the reported data, that is, data that has been sent by the second node before the current moment.

[0069] For example, when the first node needs to collect the flow information of a certain interface of the second node in real time, the information that the second node needs to report includes the device identifier to which the interface belongs, the interface identifier, the current time, and the flow of the interface at the current time. Among them, the device identifier to which the interface belongs and the interface identifier are historical reporting data, and the current time and the flow of the interface at the current time are current reporting data.

[0070] For example, when the first node needs to periodically collect usage information of a certain memory area of ​​the second node, the information that the second node needs to report includes the device identifier of the memory area, the name of the data item using the memory area, the identifier of the data item using the memory area, the identifier of the memory area, the current time, and the size of the memory capacity currently used by the memory area. Among them, the device identifier of the memory area, the name of the data item using the memory area, the identifier of the data item using the memory area, and the identifier of the memory area are historically reported data, and the current time and the size of the memory capacity currently used by the memory area are currently reported data.

[0071] In a specific implementation, when the first node collects data from the second node, the first node may collect data by receiving a report message actively sent by the second node.

[0072] Step 202: The first node parses the report message to obtain a data identifier and current report data;

[0073] In a specific implementation, after receiving the report message sent by the second node, the first node may parse the report message. Specifically, the first node may decapsulate the report message to obtain the data identifier encapsulated in the report message and the current report data.

[0074] Step 203: Acquire historical reported data according to the data identifier and the data record information, where the data record information is used to indicate a mapping relationship between a plurality of historical reported data and a plurality of data identifiers.

[0075] In the embodiment of the present application, in order to obtain the complete reported data sent by the second node, the first node may parse the data identifier.

[0076] The reported data includes historical reported data and current reported data. The data record information is used to indicate the mapping relationship between multiple historical reported data and multiple data identifiers. Specifically, the mapping relationship between multiple historical reported data and multiple data identifiers can be one data identifier corresponding to one historical reported data, one data identifier corresponding to multiple historical reported data, or multiple data identifiers corresponding to one historical reported data.

[0077] In a specific implementation, the first node can query the historical reported data corresponding to the data identifier in the report message in the data record information according to the data identifier in the report message, and the historical reported data and the current reported data in the report message are a complete report data.

[0078] In the embodiment of the present application, the first node can obtain the data identifier in the report message by parsing the report message sent by the second node, and obtain the historical reported data corresponding to the data identifier in the above report message according to the one-to-one correspondence between the data identifier and the historical reported data in the data record information, so that the complete reported data can be determined according to the historical reported data and the current reported data. It can be seen that the present application can reduce the size of the reported data by replacing the historical reported data with the data identifier, and further reduce the size of the report message. Thereby, the bandwidth occupancy can be reduced during the transmission of the report message to avoid the waste of network resources.

[0079] In the embodiment of the present application, the first node may also receive data record information sent by the second node, specifically including:

[0080] The first node receives the data record information sent by the second node; the data record information is generated according to the data identifier of each historical reported data when the second node collects multiple historical reported data.

[0081] In the embodiment of the present application, the first node also needs to obtain data record information in order to obtain the historical reported data corresponding to the data identifier according to the data record information.

[0082] In a specific implementation, the first node can obtain the data record information by receiving the data record information actively sent by the second node. The data record information is used to indicate the mapping relationship between multiple data identifiers and multiple historical reported data in the second node. The second node can collect multiple historical reported data and establish a mapping relationship between multiple historical reported data and multiple data identifiers, thereby generating data record information.

[0083] In the embodiment of the present application, the first node can receive the data record information established and actively sent by the second node, so that the first node can obtain the historical reported data corresponding to the data identifier according to the data record information. It can be seen that in the embodiment of the present application, the first node can determine the historical reported data corresponding to the data identifier according to the received data record information, avoiding the situation of repeatedly receiving the historical reported data sent by the second node, reducing the size of the reported message, reducing the bandwidth occupied by the reported message during the transmission process, and avoiding the waste of network resources.

[0084] In the embodiment of the present application, the first node may also generate data record information, specifically including: Figure 3 Steps shown:

[0085] Step 301: Receive multiple historical reported data sent by the second node, and assign a unique data identifier to each historical reported data;

[0086] In the embodiment of the present application, the first node may first obtain the historical reported data of the second node when generating data record information.

[0087] In a specific implementation, the first node may receive the historical reported data sent by the second node, and then sequentially assign a unique data identifier to each historical reported data. For example, data identifiers such as A, B, C, D, E, and F may be sequentially assigned to each historical reported data, or data identifiers such as 1, 2, 3, 4, 5, and 6 may be sequentially assigned to each historical reported data.

[0088] Step 302: Generate data record information according to the mapping relationship between multiple historical reported data and data identifiers.

[0089] In a specific implementation, the first node can record each historically reported data and the data identifier corresponding to each historically reported data, and record the mapping relationship between the two. Then, according to the mapping relationship between each historically reported data and the data identifier recorded above, the above mapping relationship is integrated to generate data record information. For example, after the first node has allocated the data identifier corresponding to each historically reported data, it can record that the data identifier corresponding to the first historically reported data is 1, the data identifier corresponding to the second historically reported data is 2, and the data identifier corresponding to the third historically reported data is 3, and the above information is integrated to generate data record information.

[0090] In the embodiment of the present application, the first node can assign a data identifier to each historically reported data in the second node, establish a mapping relationship between the historically reported data and the data identifier, and generate data record information. It can be seen that the first node can realize the generation of data record information, so as to determine the historically reported data corresponding to the data identifier according to the generated data record information, avoid the situation of repeatedly receiving the historically reported data sent by the second node, reduce the size of the reported message, reduce the bandwidth occupied by the reported message during the transmission process, and avoid the waste of network resources.

[0091] The above-mentioned embodiment introduces a scheme in which the first node assigns a unique data identifier to each historically reported data. In another embodiment of the present application, a unique hierarchical data identifier may be assigned to each historically reported data. For example, the above-mentioned “assigning a unique data identifier to each historically reported data” specifically includes:

[0092] A data identifier is assigned to the historically reported data according to device information corresponding to the historically reported data.

[0093] In a specific implementation, when allocating data identifiers for historically reported data, the first node may allocate hierarchical data identifiers of data identifiers corresponding to certain historically reported data to part of the historically reported data according to the relationship between the historically reported data.

[0094] In a possible implementation, data identifiers may be assigned to some of the historically reported data according to the device information corresponding to the historically reported data. For example, when data identifiers are assigned to multiple interfaces belonging to the same terminal, if the data identifier assigned to the terminal is A, the data identifiers assigned to each interface on the terminal in turn may be Aa, Ab, Ac, etc.

[0095] In a possible implementation, data identifiers may also be assigned to some of the historically reported data according to the interface information corresponding to the historically reported data. For example, when data identifiers are assigned to multiple sub-interfaces belonging to the same interface, if the data identifier assigned to the interface is 10, the data identifiers assigned to each sub-interface of the interface may be 101, 102, 103, etc.

[0096] As long as there are subordinate relationships or inclusion relationships among the multiple historical reported data, hierarchical data identifiers can be assigned to the above multiple historical reported data, and this application does not impose any restrictions on this.

[0097] An embodiment of the present application provides a method for a first node to assign data identifiers to historical reported data. Specifically, the first node can assign hierarchical data identifiers to historical reported data that have a subordinate relationship or other relationship, thereby establishing a connection between multiple historical reported data, making the data identification system of the historical reported data more orderly and clearer, facilitating the first node or the second node to search for data identifiers, and improving the efficiency of using data identifiers.

[0098] In the embodiment of the present application, the first node may also send the generated data record information to the second node, specifically including:

[0099] The data record information is sent to the second node.

[0100] In a specific implementation, after generating the data record information, the first node may send the data record information to the second node, so that the second node may generate a report message according to the content of the data record information.

[0101] In an embodiment of the present application, the first node can send the generated data record information to the second node, so that the second node can generate a reporting message based on the content of the data record information, so that the second node can use the data rules set by the first node to process its own data, thereby ensuring the correctness and effectiveness of data transmission between the first node and the second node.

[0102] The historical reported data in the embodiment of the present application may correspond to parameters of one or more attributes, specifically including:

[0103] The historically reported data is data corresponding to a single attribute parameter, or data corresponding to multiple attribute parameters.

[0104] In a possible implementation, the historically reported data may be data corresponding to an attribute parameter. For example, when the first node needs to collect the power of the second node in real time, the information that the second node needs to report includes the device identification of the second node, the current time, and the power of the device at the current time. Among them, the device identification of the second node is the historically reported data, that is, the historically reported data is the data corresponding to the attribute parameter of the device.

[0105] In a possible implementation, the historically reported data may be data corresponding to multiple attribute parameters. For example, when the first node needs to collect the flow information of a certain interface of the second node in real time, the information that the second node needs to report includes the device identifier to which the interface belongs, the interface identifier, the current time, and the flow of the interface at the current time. Among them, the device identifier to which the interface belongs and the interface identifier are historically reported data, that is, the historically reported data is data corresponding to the two attribute parameters of the device and the interface.

[0106] In the embodiment of the present application, the historically reported data may be not only data corresponding to one attribute parameter, but also data corresponding to multiple attribute parameters. When the historically reported data is data corresponding to one attribute parameter, the historically reported data containing one attribute parameter may be replaced with a data identifier; when the historically reported data is data corresponding to multiple attribute parameters, the historically reported data containing multiple attribute parameters may be replaced with a data identifier. This avoids repeated reception of a large amount of data, effectively reduces the size of the reported message, reduces the bandwidth occupied by the reported message during transmission, and avoids waste of network resources.

[0107] Figure 4 The flowchart of the data collection method provided in the embodiment of the present application is illustrated by taking the method applied to the second node as an example, and specifically includes the following steps:

[0108] Step 401: The second node determines the data to be reported, and determines the historical reported data and the current reported data corresponding to the data to be reported according to the data repeatability; the data identifier is used to uniquely indicate a historical reported data of the second node;

[0109] In a specific implementation, before sending the report message, the second node first determines the data to be reported, and then determines the data to be reported that needs to be reported repeatedly. The data to be reported repeatedly is determined as the historical reported data, and the data to be reported other than the data to be reported repeatedly is determined as the current reported data.

[0110] For example, the first node needs to collect the flow information of a certain interface of the second node in real time. Before sending the report message, the second node first determines that the data to be reported includes the device identifier to which the interface belongs, the interface identifier, the current time, and the flow of the interface at the current time. Then, the two data that need to be reported repeatedly, the device identifier to which the interface belongs and the interface identifier, are determined as the historical reporting data; and the remaining current time and the flow of the interface at the current time are determined as the current reporting data.

[0111] Step 402: determine the data identifier corresponding to the historically reported data according to the data record information; the data record information is used to indicate the mapping relationship between multiple historically reported data and multiple data identifiers;

[0112] In a specific implementation, the second node may query the data record information according to the historical reported data determined above, and query the data identifier corresponding to the historical reported data determined above according to the one-to-one correspondence between the historical reported data and the data identifier in the data record information.

[0113] The data record information records the mapping relationship between multiple historical reported data and multiple data identifiers.

[0114] Step 403: Generate a reporting message according to the data identifier and the current reporting data, and send the reporting message to the first node.

[0115] In a specific implementation, the second node may replace the historical reported data in the data to be reported with the data identifier corresponding to the historical reported data, and then encapsulate the data identifier and the current reported data in the data to be reported into a report message, and finally send the encapsulated report message to the first node.

[0116] In the embodiment of the present application, the second node can replace the historical reported data in the data to be reported with the data identifier, and send the data identifier encapsulated as the reported message and the current reported data in the data to be reported to the first node. It can be seen that the present application can reduce the size of the reported data by replacing the historical reported data with the data identifier, and further reduce the size of the reported message. Thereby, the bandwidth occupation can be reduced during the transmission of the reported message, and the waste of network resources can be avoided.

[0117] In the embodiment of the present application, the second node may also generate data record information, specifically including: Figure 5 Steps shown:

[0118] Step 501: after collecting historical reported data, assign a unique data identifier to the historical reported data according to the device information corresponding to the historical reported data;

[0119] In the embodiment of the present application, before generating data record information, the second node must first collect historical reported data that needs to be reported repeatedly.

[0120] In a specific implementation, the second node may collect historically reported data according to the repeatability of the data. Then, a data identifier is assigned to each historically reported data in turn according to the device information corresponding to the historically reported data. For example, when data identifiers are assigned to multiple interfaces belonging to the same terminal in all reported data, if the data identifier assigned to the terminal is A, then the data identifiers assigned to each interface on the terminal in turn may be Aa, Ab, Ac, etc.

[0121] In a possible implementation, a data identifier may be assigned to each historically reported data according to the interface information corresponding to the historically reported data. For example, when data identifiers are assigned to multiple sub-interfaces belonging to the same interface in all reported data, if the data identifier assigned to the interface is 10, the data identifiers assigned to each sub-interface of the interface may be 101, 102, 103, etc.

[0122] As long as there are subordinate relationships or inclusion relationships among the multiple historical reported data, hierarchical data identifiers can be assigned to the above multiple historical reported data, and this application does not impose any restrictions on this.

[0123] Step 502: Generate data record information according to the mapping relationship between multiple historical reported data and data identifiers.

[0124] In a specific implementation, the second node can record each historical reported data and the data identifier corresponding to each historical reported data, and record the mapping relationship between the two. Then, according to the mapping relationship between each historical reported data and the data identifier recorded above, the above mapping relationship is integrated to generate data record information. For example, after the second node has allocated the data identifier corresponding to each historical reported data, it can record that the data identifier corresponding to the first historical reported data is 10, the data identifier corresponding to the second historical reported data is 101, and the data identifier corresponding to the third historical reported data is 102, and the above information is integrated to generate data record information.

[0125] In the embodiment of the present application, the second node can collect historical reported data, and assign a data identifier to each historical reported data, establish a mapping relationship between historical reported data and data identifiers, and generate data record information. It can be seen that the second node can realize the generation of data record information, so as to determine the historical reported data corresponding to the data identifier according to the generated data record information, avoid the situation of repeatedly receiving the historical reported data sent by the second node, reduce the size of the reported message, reduce the bandwidth occupied by the reported message during the transmission process, and avoid the waste of network resources. In addition, the second node can assign hierarchical data identifiers to historical reported data with subordinate relationships or other relationships, thereby establishing a connection between multiple historical reported data, making the data identification system of historical reported data more orderly and clearer, so as to facilitate the first node or the second node to search for the data identifier, and improve the efficiency of the use of the data identifier.

[0126] In the embodiment of the present application, the second node may also dynamically manage the data record information, specifically including:

[0127] Update or delete the data identifier in the data record information according to the changes in the data content.

[0128] In a possible implementation, if the historically reported data corresponding to a certain data identifier changes, the second node may send a data record information update request to the first node, and the data record information update request includes the data identifier corresponding to the changed historically reported data and the changed historically reported data, so that the first node can update the data record information stored locally according to the data record information update request.

[0129] In a possible implementation, if the historically reported data corresponding to a certain data identifier stops being used, the second node may send a data record information deletion request to the first node, and the data record information deletion request includes the data identifier corresponding to the historically reported data that stops being used. So that the first node can delete the mapping relationship corresponding to the data identifier in the data record information stored locally according to the data record information deletion request. Optionally, the second node can determine whether the historically reported data corresponding to the data identifier stops being used according to the idle time of the data identifier. For example, if the idle time of the data identifier exceeds a preset time, it is determined that the historically reported data corresponding to the data identifier stops being used, thereby deleting the relevant information of the data identifier in the data record information.

[0130] In an embodiment of the present application, the second node can promptly instruct the first node to dynamically update or delete the data identifier and historically reported data in the data recording information based on changes in the historically reported data, thereby realizing flexible and dynamic management of the data recording information, ensuring data consistency between the first node and the second node, and ensuring accuracy during data transmission.

[0131] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0132] Based on the same inventive concept, the embodiment of the present application also provides a data acquisition device for implementing the data acquisition method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more data acquisition device embodiments provided below can refer to the limitations on the data acquisition method above, and will not be repeated here.

[0133] In one embodiment, Figure 6 As shown, a data acquisition device is provided, including: a receiving module, a parsing module and an acquisition module, wherein:

[0134] The receiving module 601 is used to receive a report message sent by the second node; the report message includes a data identifier and current reported data, and the data identifier is used to uniquely indicate a historical reported data of the second node;

[0135] The parsing module 602 is used to parse the reported message to obtain the data identifier and the current reported data;

[0136] The acquisition module 603 is used to acquire the historical reported data according to the data identifier and the data record information, where the data record information is used to indicate the mapping relationship between a plurality of historical reported data and a plurality of data identifiers.

[0137] In one embodiment, the data collection device further includes a data record information receiving module for receiving data record information sent by the second node; the data record information is generated according to the data identifier of each historical reported data when the second node collects multiple historical reported data.

[0138] In one embodiment, the data collection device also includes a data record information generation module for receiving multiple historical reported data sent by the second node, assigning a unique data identifier to each historical reported data; and generating data record information based on the mapping relationship between the multiple historical reported data and the data identifier.

[0139] In one embodiment, allocating a unique data identifier to each historically reported data includes: allocating a data identifier to the historically reported data according to device information corresponding to the historically reported data.

[0140] In one embodiment, the data collection device further includes a sending module for sending data record information to the second node.

[0141] In one embodiment, the historically reported data is data corresponding to a single attribute parameter, or data corresponding to multiple attribute parameters.

[0142] In one embodiment, the first node is a decoder and the second node is an encoder.

[0143] In one embodiment, Figure 7 As shown, a data collection device is provided, including: a module for determining data to be reported, a module for determining data identification, and a generating module, wherein:

[0144] The module 701 for determining data to be reported is used to determine the data to be reported, and determine the historical reported data and the current reported data corresponding to the data to be reported according to the data repeatability; the data identifier is used to uniquely indicate a historical reported data of the second node;

[0145] The data identification determination module 702 is used to determine the data identification corresponding to the historical reported data according to the data record information; the data record information is used to indicate the mapping relationship between multiple historical reported data and multiple data identifications;

[0146] The generating module 703 is used to generate a reporting message according to the data identifier and the current reporting data, and send the reporting message to the first node.

[0147] In one embodiment, the data collection device also includes a data record information generation module, which is used to collect historical reported data and assign a unique data identifier to the historical reported data according to the device information corresponding to the historical reported data; and generate data record information according to the mapping relationship between multiple historical reported data and data identifiers.

[0148] In one embodiment, the data collection device further includes a data record information management module, which is used to update or delete the data identifier in the data record information according to the change of the data content.

[0149] Each module in the above data acquisition device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module.

[0150] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 8 As shown. The computer device includes a processor, a memory and a network interface connected via a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store some data related to the data collection method described in the embodiment of the present application, for example, the reported data, historical reported data, current reported data, etc. described above. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a data collection method is implemented.

[0151] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Fig. 9As shown. The computer device includes a processor, a memory, a communication interface, a display screen and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a data acquisition method is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covered on the display screen, or a key, trackball or touchpad set on the computer device housing, or an external keyboard, touchpad or mouse, etc.

[0152] Those skilled in the art will understand that Figure 8 as well as Fig. 9 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0153] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.

[0154] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0155] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0156] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0157] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0158] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0159] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A data collection method, characterized in that: The method comprises: The first node receives a plurality of historical reported data sent by the second node, assigns hierarchical data identifiers to the plurality of historical reported data having a subordinate relationship or a containing relationship, and establishes a connection between the plurality of historical reported data; The first node generates data record information according to a mapping relationship between the plurality of historical reported data and the hierarchical data identifiers; The first node receives a report message sent by the second node; the report message includes a layered data identifier and current reported data, and the layered data identifier is used to uniquely indicate a historical reported data of the second node; The first node decapsulates the reporting message to obtain the layered data identifier and the current reporting data encapsulated in the reporting message; The first node obtains the historical reported data according to the hierarchical data identifier and the data record information, and determines complete reported data according to the historical reported data and the current reported data.

2. The method according to claim 1, characterized in that Before the first node receives the reporting message sent by the second node, the method further includes: The first node receives the data record information sent by the second node; the data record information is generated according to the hierarchical data identifier of each of the historical reported data when the second node collects the multiple historical reported data.

3. The method according to claim 1, characterized in that The step of allocating hierarchical data identifiers to a plurality of historical reported data having a subordinate relationship or a containing relationship includes: The first node allocates hierarchical data identifiers to a plurality of historical reported data having a subordinate relationship or a containing relationship according to the device information corresponding to the historical reported data.

4. The method according to any one of claims 1 to 3, characterized in that: After the first node generates the data record information, the method further includes: The first node sends the data record information to the second node.

5. The method according to any one of claims 1 to 3, characterized in that: The historically reported data is data corresponding to a single attribute parameter, or is data corresponding to multiple attribute parameters.

6. The method according to any one of claims 1 to 3, characterized in that: The first node is a decoder, and the second node is an encoder.

7. A data collection method, characterized in that: The method comprises: The second node determines the data to be reported, and determines the historical reported data and the current reported data corresponding to the data to be reported according to the data repeatability; The second node determines the hierarchical data identifier corresponding to the historical reported data according to the data record information; the data record information is generated by the first node receiving multiple historical reported data sent by the second node, allocating hierarchical data identifiers to multiple historical reported data with a subordinate relationship or a containing relationship, and establishing a connection between the multiple historical reported data, and is used to indicate a mapping relationship between the multiple historical reported data and the hierarchical data identifier; The second node encapsulates the layered data identifier and the current reported data into a reporting message, and sends the reporting message to the first node to instruct the first node to determine complete reporting data based on the historical reported data corresponding to the layered data identifier and the current reported data.

8. The method according to claim 7, characterized in that Before the second node determines the hierarchical data identifier corresponding to the historical reported data according to the data record information, the method further includes: After the second node collects the historical reported data, it allocates a unique data identifier to the historical reported data according to the device information corresponding to the historical reported data; The second node generates the data record information according to the mapping relationship between the multiple historical reported data and the hierarchical data identifiers.

9. The method according to claim 7, characterized in that: The method further comprises: The second node updates or deletes the hierarchical data identifier in the data record information according to the change of the data content.

10. A data acquisition device, characterized in that: The device comprises: A data record information generating module, configured to receive a plurality of historical reported data sent by the second node, assign hierarchical data identifiers to the plurality of historical reported data having a subordinate relationship or a containing relationship, and establish a connection between the plurality of historical reported data; and generate data record information according to a mapping relationship between the plurality of historical reported data and the hierarchical data identifiers; A receiving module, configured to receive a report message sent by the second node; the report message includes a hierarchical data identifier and current report data, and the hierarchical data identifier is used to uniquely indicate a historical report data of the second node; A parsing module, used for decapsulating the reported message, and obtaining the hierarchical data identifier and the current reported data encapsulated in the reported message; The acquisition module is used to acquire the historical reported data according to the hierarchical data identifier and the data record information, and determine the complete reported data according to the historical reported data and the current reported data.

11. A data acquisition device, characterized in that: The device comprises: A module for determining data to be reported, used to determine the data to be reported, and to determine the historical reported data and the current reported data corresponding to the data to be reported according to the data repeatability; the data identifier is used to indicate the historical reported data of the second node, and one data identifier corresponds to multiple historical reported data; a data identification determination module, used to determine the data identification corresponding to the historical reported data according to the data record information; the data record information is generated by the first node receiving multiple historical reported data sent by the second node, allocating hierarchical data identifications to multiple historical reported data having a subordinate relationship or a containing relationship, establishing a connection between the multiple historical reported data, and indicating the mapping relationship between the multiple historical reported data and the hierarchical data identification; A generation module is used to encapsulate the layered data identifier and the current reported data into a reporting message, and send the reporting message to the first node to instruct the first node to determine complete reporting data based on the historical reporting data corresponding to the layered data identifier and the current reported data.

12. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 9 are implemented.

13. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.

14. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.

Images