Equipment data collection method and related device

Abstract

This application discloses a device data collection method and related apparatus. The method includes receiving a topology request from a server; collecting topology data of a target device based on the topology request and sending the topology data to the server; receiving data collection rules from the server based on the topology data; collecting data from the target device based on the data collection rules, and sending the collected data to the server. Through this approach, the application improves data collection efficiency.

Description

Technical Field

[0001] The present application relates to the field of data acquisition, and in particular to a device data acquisition method and related devices. Background Art

[0002] In the commercial air conditioning industry, data access is typically achieved using a physical model of the air conditioning system and its corresponding TCC (Terminal Communication Conventions). However, an air conditioning system typically consists of multiple components, such as a logic board, slave units, indoor units, and driver boards. The number of each component may vary from system to system. Therefore, a physical model must be established for each air conditioning system for management and data collection, which consumes considerable time and labor. Summary of the Invention

[0003] This application mainly provides a device data collection method and related devices, which can solve the problem of high data collection costs when different device systems are connected to the server, and improve data collection efficiency.

[0004] In a first aspect, the present application provides a device data collection method. The method is applied to a gateway device, which is in communication with a server and a target device. The method includes receiving a topology request message from the server; collecting topology data of the target device based on the topology request message, and sending the topology data to the server; receiving a data collection rule from the server based on the topology data; collecting data from the target device based on the data collection rule, and sending the collected data to the server.

[0005] In a second aspect, the present application provides a device data collection method. The method is applied to a server, the server being in communication with a gateway device, and the gateway device being in communication with a target device. The method comprises sending a topology request message to the gateway device; receiving topology data of the target device collected by the gateway device based on the topology request message; generating data collection rules based on the topology data; sending the data collection rules to the gateway device; and receiving data collected from the target device by the gateway device based on the data collection rules.

[0006] In a third aspect, the present application provides a gateway device, which includes a memory and a processor, wherein the memory is used to store program data, and the program data can be executed by the processor to implement the method described in the first aspect.

[0007] In a fourth aspect, the present application provides a server comprising a memory and a processor, wherein the memory is used to store program data, and the program data can be executed by the processor to implement the method described in the second aspect.

[0008] In a fifth aspect, the present application provides a device data acquisition system, which includes the gateway device described in the third aspect and the server described in the fourth aspect.

[0009] The beneficial effects of this application are as follows: this application collects the topological data of the target device through the gateway device, and further allows the server to generate data collection rules for the target device based on the topological data, so that the gateway device can collect data from the target device according to the received data collection rules. By obtaining the topological data corresponding to the target device and configuring the corresponding data collection rules for the gateway device of the target device, it is avoided that the server needs to build a corresponding physical model for the data collection work of each device, saving the time and labor costs of the data collection work, allowing the target device to quickly access the server, and improving the efficiency of data collection. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0011] Figure 1 This is a flow chart of the first embodiment of the device data collection method of the present application;

[0012] Figure 2 This is a flow chart of the second embodiment of the device data collection method of the present application;

[0013] Figure 3 This is a flow chart of the third embodiment of the device data collection method of the present application;

[0014] Figure 4 This is a flow chart of the fourth embodiment of the device data collection method of the present application;

[0015] Figure 5 This is a flowchart of the fifth embodiment of the device data collection method of the present application;

[0016] Figure 6 This is a flow chart of the sixth embodiment of the device data collection method of the present application;

[0017] Figure 7 This is a flow chart of the seventh embodiment of the device data collection method of the present application;

[0018] Figure 8 This is a flow chart of a specific embodiment of the device data collection method of the present application;

[0019] Figure 9 This is a schematic diagram of the structure of an embodiment of a gateway device of the present application;

[0020] Figure 10 This is a schematic diagram of the structure of an embodiment of the server of this application;

[0021] Figure 11 It is a structural diagram of an embodiment of the device data acquisition system of the present application. DETAILED DESCRIPTION

[0022] The following embodiments of the technical solution of the present application will be described in detail with reference to the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present application and are therefore only examples and are not intended to limit the scope of protection of the present application.

[0023] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application belongs; the terms used herein are only for the purpose of describing specific embodiments and are not intended to limit this application; the terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned figure descriptions are intended to cover non-exclusive inclusions.

[0024] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0025] In the description of the embodiments of this application, the technical terms "first" and "second" are used only to distinguish different objects and should not be understood to indicate or imply relative importance or implicitly specify the quantity, specific order, or primary and secondary relationship of the indicated technical features. In the description of the embodiments of this application, the meaning of "plurality" is more than two, unless otherwise clearly and specifically defined.

[0026] In the description of the embodiments of this application, the term "and / or" is simply a description of the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent the following three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0027] In the description of the embodiments of the present application, the term "multiple" refers to more than two (including two). Similarly, "multiple groups" refers to more than two groups (including two groups), and "multiple pieces" refers to more than two pieces (including two pieces).

[0028] In the description of the embodiments of the present application, the technical terms "center", "longitudinal", "lateral", "length", "width", "thickness", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside", "clockwise", "counterclockwise", "axial", "radial", "circumferential", etc., indicating the orientation or position relationship, are based on the orientation or position relationship shown in the accompanying drawings, and are only for the convenience of describing the embodiments of the present application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the embodiments of the present application.

[0029] In the description of the embodiments of the present application, unless otherwise expressly specified or limited, technical terms such as "installed," "connected," "connected," and "fixed" should be understood in a broad sense. For example, they can refer to fixed connections, detachable connections, or integration; mechanical connections or electrical connections; direct connections or indirect connections through an intermediate medium; internal connections between two components or interactions between two components. Those skilled in the art can understand the specific meanings of the above terms in the embodiments of the present application based on specific circumstances.

[0030] A typical air conditioning system primarily consists of three components: the air conditioning unit, a gateway device, and a server. The air conditioning unit may include multiple control modules, such as a logic board, slave units, internal units, and driver boards connected to the logic board. These slave units and internal units may also be connected to multiple driver boards. The gateway device communicates with the logic board, enabling data exchange between the server and the air conditioning unit. Typically, there is a one-to-one correspondence between the gateway device and the air conditioning unit. The gateway device is responsible for receiving data collection rules issued by the server and collecting data from the air conditioning unit according to these rules.

[0031] Typically, because air conditioners include varying types and quantities of control modules, servers collect data from these devices by building corresponding object models for each device to manage the data. This means that if a large number of air conditioners are connected to a server, the server must build a large number of object models, which increases the workload and affects the server's efficiency in collecting data from the air conditioners. Furthermore, building a large number of object models consumes server space and increases data management costs.

[0032] Therefore, the present application proposes a device data collection method and related devices to improve the working efficiency of the server when collecting device data through a gateway device and reduce the space occupied by the data collection work on the server.

[0033] Reference Figure 1 , Figure 1This is a flow chart of the first embodiment of the device data collection method of this application. The method is applied to a gateway device, which is in communication with a server and a target device. It includes but is not limited to the following steps.

[0034] S11: Receive topology request information sent by the server.

[0035] Topology refers to the physical layout characteristics that connect various devices to each other. It is described by borrowing the two most basic graphic elements in geometry: points and lines, to abstractly represent the connection status of each device end.

[0036] The topology structure request information in this embodiment includes information related to how the gateway device obtains topology data, such as the communication address corresponding to each module in the target device.

[0037] S12: Collect topology data of the target device based on the topology structure request information, and send the topology data to the server.

[0038] The gateway device determines the topology data of the target device based on the topology request information. In this embodiment, the topology data of the target device collected includes the number of each control module in the target device. After obtaining the topology data, the gateway device sends it to the server in the agreed data transmission format.

[0039] S13: Receive data collection rules sent by the server based on the topology data.

[0040] The server selects corresponding data collection rules based on the received topology data and sends them to the gateway device. These data collection rules include the TCC, which refers to a set of rules and standards followed during data transmission or communication between devices. These conventions are crucial to ensuring the accuracy, reliability, and efficiency of data transmission.

[0041] The server sets an initial physical model for a specific target device type, maps the topology structure to data collection rules, and sets corresponding data collection rules for each topology structure. The initial physical model for a specific target device type includes the types and quantities of all control modules within that type of device, allowing it to adapt to the topology data of different target devices.

[0042] For example, consider setting up physical models for two types of air conditioners, A and B. Assume that Type A air conditioners include a logic board, up to three indoor units, up to two indoor unit driver boards per indoor unit, up to three slave units, up to two slave unit driver boards per slave unit, and up to six driver boards. Type B air conditioners include a logic board, up to six indoor units, up to two indoor unit driver boards per indoor unit, up to six slave units, up to three slave unit driver boards per slave unit, and up to four driver boards. The initial physical models corresponding to Types A and B air conditioners include a logic board, up to six indoor units, up to two indoor unit driver boards per indoor unit, up to six slave units, up to three slave unit driver boards per slave unit, and up to six driver boards.

[0043] The initial physical model may also be provided with communication addresses corresponding to modules in the target device, so that topology request data can be generated according to the communication address, so that the gateway device receiving the topology request data can obtain the topology data of the target device according to the communication address therein.

[0044] S14: Collect data from the target device based on the data collection rules, and send the collected data to the server.

[0045] The gateway device collects data according to the data collection rules corresponding to the topology data of the target device and sends the data to the server, which processes the data accordingly.

[0046] In the embodiment of the present application, the gateway device corresponds to the target device for data collection. If the server needs to collect data from multiple devices, each device has a unique gateway device to establish a communication connection with the server and provide data exchange services.

[0047] This embodiment uses a gateway device to collect topological data from target devices, and then allows the server to generate data collection rules for the target devices based on the topological data, allowing the gateway device to collect data from the target devices according to the received data collection rules. By obtaining the topological data corresponding to the target device and configuring the corresponding data collection rules for the target device's gateway device, the server does not need to build a corresponding physical model for each device's data collection work, saving the time and labor costs of data collection work, allowing the target device to quickly access the server, and improving data collection efficiency.

[0048] Reference Figure 2 , Figure 2 This is a flow chart of the second embodiment of the device data acquisition method of this application. This method is a further extension of the above embodiment. It includes but is not limited to the following steps.

[0049] S21: Send the device identification information of the target device to the server.

[0050] Before the gateway device receives the topology request information sent by the server, it first needs to authenticate the target device. The gateway device will send the target device's device identification information to the server. The device identification information is a unique identifier that distinguishes the target device and may include, for example, an SN code.

[0051] S22: Receive the authentication result generated by the server based on the device identification information.

[0052] The server performs identity authentication based on the received device identification information to determine whether the target device has been registered with the server. If the target device has been registered with the server, the server will store its device identification information. If it has not been registered with the server, the server will not store its device identification information. If so, the authentication succeeds; otherwise, the authentication fails and the process ends.

[0053] In one embodiment, after determining that the device identification information of the target device is stored, it is also possible to determine whether the registration information of the target device has expired. The starting point for determining whether the registration information has expired can be the time when the target device last performed identity authentication. If the registration information has not expired, the authentication is successful; otherwise, the authentication fails and the process ends.

[0054] In one embodiment, it is also possible to determine whether the login method of the gateway device is legal when sending the device identification information to the server, for example, whether the login password is correct. If the login method is legal, the authentication is successful; otherwise, the authentication fails and the process ends.

[0055] When generating the authentication result, the server may include one or more of the above authentication methods. If all the authentication methods are successful, the authentication result based on the device identification information is considered a success; otherwise, the authentication fails.

[0056] When the server determines that the authentication result of the target device is successful, it will send the authentication result of successful authentication to the gateway device, notifying the gateway device that the target device has been successfully authenticated.

[0057] If the authentication fails, the server can notify the user of the authentication failure result, so that the user can make corresponding adjustments based on the authentication failure result or the type of failure result, and then perform subsequent re-authentication.

[0058] In this embodiment, before the server sends the topology request information and the gateway device sends the topology request information, the gateway device sends its device identification information to the server for identity authentication. This is to ensure the server's system security and data integrity. Once the device identification information is verified, only legitimate target devices can access the server system, preventing unauthorized access and improving system security. Once the device identification information is verified, the specific device interacting with the data is clearly identified, enabling data traceability and ensuring data security.

[0059] In one embodiment, after receiving the authentication result generated by the server based on the device identification information, the method includes: when the authentication result is successful, monitoring the topology request information sent by the server.

[0060] Monitoring can be done in a publish-subscribe model. This can be implemented using message queues such as MQTT, Kafka, and RabbitMQ. In this model, the server publishes multiple topics, each used to send specific information. When a gateway device subscribes to a topic, it actively listens to that topic. Once the gateway device subscribes to a topic, it automatically receives and processes any information published by the server under that topic.

[0061] Reference Figure 3 , Figure 3 This is a flow chart of the third embodiment of the device data acquisition method of this application. This method is a further extension of the above embodiment. It includes but is not limited to the following steps.

[0062] S31: Monitor the key information sent by the server.

[0063] The key information may include key information of the target device and key information of the gateway device.

[0064] S32: Receive the key information sent by the server and store it.

[0065] After receiving the key information, the gateway device will store it in the memory.

[0066] Before the gateway device listens for the server's topology request information, it listens for the key information sent by the server. Before sending the topology request information to the gateway device, the server sends the key information to the gateway device as data protection during subsequent communication. The gateway device and server can use this key information for authentication during subsequent communications to ensure data security.

[0067] The monitoring method may include monitoring in a publish-subscribe mode, which is similar to the above-mentioned monitoring topology request information method and will not be described in detail here.

[0068] Reference Figure 4 , Figure 4 This is a flow chart of the fourth embodiment of the device data acquisition method of this application. This method is a further extension of the above embodiment. It includes but is not limited to the following steps.

[0069] S41: Determine whether to adjust the data collection rules currently used by the target product.

[0070] After sending the topology data to the server, the gateway device can determine whether to use the new data collection rule or continue to use the current data collection rule according to the received user instruction.

[0071] The judgment process may be started before, simultaneously with, or after the new data collection rules are received.

[0072] If the received data collection rules are selected, step S42 is executed. If the historical data collection rules are selected, step S43 is executed. If the data collection rules currently used by the target product are selected to continue to be used, step S44 is executed.

[0073] S42: Using the received data collection rule, the data collection rule currently used by the target product is updated, and the version number of the received data collection rule is sent to the server.

[0074] If you choose to use the received data collection rules, they will be used to update the currently used data collection rules. When the server issues the data collection rules, the server also issues the version number corresponding to the data collection rules. To notify the server that the gateway device has completed the data collection rule update, the gateway device will send the version number of the received data collection rules or the updated data collection rules to the server after the update is complete. The server then determines whether the data collection rules have been successfully issued based on this version number.

[0075] S43: Send the version number corresponding to the historical data collection rule to the server.

[0076] When determining whether to adjust the data collection rules for the current data of the target product, if you do not want to use the data collection rules generated by the server based on the topology data, nor do you want to use the current data collection rules, and want to use the historical data collection rules used before, you can send the version number corresponding to the historical data collection rules to the server. The server will send the corresponding historical data collection rules to the gateway device based on the version number. After receiving the historical data collection rules, the network management device will use the historical data collection rules to update the currently used data collection rules. After the update, the version number corresponding to the historical data collection rules is sent to the server to notify the server that the update is complete. It can be understood that the version number of the historical data collection rules sent and the corresponding historical data collection rules need to be stored in the server, otherwise the server cannot send the corresponding historical data collection rules to the gateway device.

[0077] S44: Keep the data collection rules currently used by the target product.

[0078] If you do not use the received data collection rules, do not update the data collection rules, and continue to use the current data collection rules, then no changes are required.

[0079] In this embodiment, the gateway device determines whether to update the data collection rules through user instructions. When the data collection rules do not need to be updated, the current data collection rules continue to be used, eliminating the data collection rule update step and improving data collection efficiency.

[0080] Reference Figure 5 , Figure 5 This is a flowchart of the fifth embodiment of the device data collection method of the present application. The method is applied to a server, the server is in communication with a gateway device, and the gateway device is in communication with a target device. The method includes but is not limited to the following steps.

[0081] S51: Send topology request information to the gateway device.

[0082] S52: Receive topology data of the target device collected by the gateway device based on the topology structure request information.

[0083] S53: Generate data collection rules based on the topology data.

[0084] S54: Send the data collection rules to the gateway device.

[0085] S55: Receive data collected by the gateway device from the target device based on the data collection rule.

[0086] The relevant descriptions in this embodiment can refer to the descriptions in the above embodiments and will not be repeated here.

[0087] In one embodiment, generating data collection rules based on topology data includes: matching the topology data with the local topology data of the target device on the server to obtain a matching result; updating the local topology data of the target device based on the matching result, and generating corresponding data collection rules based on the updated local topology data.

[0088] After receiving the topology data of the target device from the gateway device, it is compared with the local topology data of the target device stored locally on the server. The local topology data of the target device on the server also includes the number of each control module in the target device. If the received topology data is the same as the local topology data, the process ends and waits for the collection data sent by the gateway device. The gateway device does not need to change the data collection rules and can collect data from the target device according to the existing data collection rules. If the received topology data is different from the local topology data, the local topology data is updated with the received topology data, and the data collection rules are determined based on the new local topology data. The new data collection rules obtained based on the new local topology data need to be sent to the gateway device to update the data collection rules.

[0089] Reference Figure 6 , Figure 6 This is a flow chart of the sixth embodiment of the device data acquisition method of this application. This method is a further extension of the above embodiment. It includes but is not limited to the following steps.

[0090] S61: Receive device identification information of the target device sent by the gateway device.

[0091] S62: Perform authentication based on the device identification information to obtain an authentication result.

[0092] Before sending the topology request information to the gateway device, the device identification information sent by the gateway device is received to perform identity authentication on the target device.

[0093] In one embodiment, after obtaining an authentication result through authentication based on the device identification information, the method includes: when the authentication result is successful, sending the authentication result to the gateway platform, and sending key information and topology request information to the gateway platform in sequence.

[0094] The relevant descriptions in this embodiment can refer to the descriptions in the above embodiments and will not be repeated here.

[0095] Reference Figure 7 , Figure 7 This is a flow chart of the seventh embodiment of the device data acquisition method of this application. This method is a further extension of the above embodiment. It includes but is not limited to the following steps.

[0096] S71: Receive the version number of the data collection rule sent by the gateway device.

[0097] S72: Match the version number of the data collection rule with the version number of the data collection rule previously sent to the gateway device to obtain a matching result.

[0098] S73: If the matching result is consistent, it is determined that the data collection rule is sent successfully.

[0099] After the data collection rules are sent to the gateway device, if the gateway device is updated according to the data collection rules sent by the server, it will send the version number of the received data collection rules or the updated data collection rules to the server to notify the server that the update is completed at the gateway device.

[0100] In one embodiment, upon receiving the version number of the data collection rules sent by the gateway device, a determination is made as to whether the version number is consistent with the version number of the data collection rules previously sent by the server to the gateway device. If inconsistent, the user is notified of an abnormality in the gateway device data collection rule update, prompting the user to take appropriate action. If consistent, the data collection rules are determined to have been sent successfully.

[0101] After confirming that the data collection rule is sent successfully, the server waits to receive the data collected by the gateway device based on the sent data collection rule.

[0102] In one embodiment, if the gateway device chooses to use the historical data collection rules, the gateway device will send the version number corresponding to the historical data collection rules to the server. If the version number of the data collection rules received by the server from the gateway device is inconsistent with the version number of the data collection rules previously sent to the gateway device, but is consistent with the version number of the historical data collection rules of the target device that is already stored locally on the server, the historical data collection rules corresponding to the version number will be sent to the gateway device. After the gateway device is updated according to the historical data collection rules, it will receive the version number sent by the gateway device again. At this time, the version number sent by the gateway device is the version number of the historical data collection rules. When the server receives the version number, if it determines that the version number is consistent with the version number of the historical data collection rules previously issued, it determines that the data collection rules have been sent successfully.

[0103] In one embodiment, if the server does not receive the version number of the data collection rules sent by the gateway device after sending the data collection rules to the gateway device, in order to avoid situations such as abnormal reception by the gateway device, the data collection rules can be repeatedly sent a preset number of times. If the version number of the data collection rules sent by the gateway device is still not received after repeated transmission, it can be determined that the gateway device does not use the data collection rules sent, but retains the data collection rules currently used by the gateway device. The process is terminated and the data collected by the gateway device based on the data collection rules sent can be received. The device data collection method of the present application is described in more detail by taking a specific embodiment as an example.

[0104] Reference Figure 8 , Figure 8 This is a flow chart of a specific embodiment of the device data collection method of this application.

[0105] First, an initial object model is created in the server. Subsequently, the corresponding initial object model is selected according to the type of target device to match the topology structure with the data collection rules.

[0106] After the target device is registered in the server, the gateway device connected to the target device is powered on and logs into the server.

[0107] After logging in, the gateway device will send device identification information to the server for the server to authenticate the identity of the target device. The server authentication process can refer to the description in the above embodiment.

[0108] After the server completes authentication, it sends a successful authentication result to the gateway device. After confirming successful authentication, the gateway device subscribes to the key information topic and the topology request information topic. The intercepted key information is saved for subsequent communication authentication. Based on the intercepted topology request information, the gateway device obtains the target device's topology data and sends it to the server.

[0109] The server generates data collection rules based on the obtained topology data. Similar steps can be referred to the description in the above embodiment.

[0110] After receiving the data collection rules, the gateway device collects data from the target device based on them. Before collecting data, it can also determine whether to use the data collection rules issued by the server. Similar steps can be referred to the description in the above embodiment.

[0111] After data collection, the gateway device sends the collected data to the server, and the server stores the collected data.

[0112] like Figure 9 As shown, Figure 9 This is a schematic diagram of the structure of an embodiment of the gateway device of the present application.

[0113] The gateway device includes a processor 110 and a memory 120 .

[0114] Processor 110 controls the operation of the gateway device and may also be referred to as a CPU (Central Processing Unit). Processor 110 may be an integrated circuit chip with signal processing capabilities. Processor 110 may also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. A general-purpose processor may be a microprocessor or any conventional processor.

[0115] The memory 120 stores instructions and program data required for the processor 110 to operate.

[0116] The processor 110 is used to execute instructions to implement the method provided by any one of the first to fourth embodiments of the device data acquisition method of the present application and any possible combination thereof.

[0117] like Figure 10 As shown, Figure 10 This is a structural diagram of an embodiment of the server of this application.

[0118] The server includes a processor 210 and a memory 220 .

[0119] Processor 210 controls the operation of the server and may also be referred to as a CPU (Central Processing Unit). Processor 210 may be an integrated circuit chip with signal processing capabilities. Processor 210 may also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. A general-purpose processor may be a microprocessor or any conventional processor.

[0120] The memory 220 stores instructions and program data required for the processor 210 to operate.

[0121] The processor 210 is used to execute instructions to implement the method provided by any one of the fifth to seventh embodiments of the device data acquisition method of the present application and any possible combination thereof.

[0122] like Figure 11 As shown, Figure 11 This is a structural diagram of an embodiment of the device data acquisition system of the present application.

[0123] The device data collection system includes a server 310 and a gateway device 320 .

[0124] The server 310 may establish a communication connection with one or more gateway devices 320 .

[0125] The server 310 includes the server described in the above server embodiment of the present application. The gateway device 320 includes the gateway device described in the above gateway device embodiment of the present application.

[0126] In summary, the present application collects the topological data of the target device through the gateway device, and further allows the server to generate data collection rules for the target device based on the topological data, so that the gateway device can collect data from the target device according to the received data collection rules. By obtaining the topological data corresponding to the target device and configuring the corresponding data collection rules for the gateway device of the target device, it is avoided that the server needs to build a corresponding physical model for the data collection work of each device, saving the time and manpower costs of the data collection work, allowing the target device to quickly access the server, and improving the work efficiency of data collection.

[0127] In the several embodiments provided in this application, it should be understood that the disclosed methods and devices can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the modules or units is merely a logical functional division. In actual implementation, other division methods may be used, such as combining or integrating multiple units or components into another system, or ignoring or not implementing certain features.

[0128] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of this embodiment.

[0129] In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The above-mentioned integrated units may be implemented in the form of hardware or software functional units.

[0130] If the integrated units in the other embodiments described above are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program code, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0131] The above description is merely an embodiment of the present application and does not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A device data collection method, characterized in that: Applied to a gateway device, the gateway device being in communication with a server and a target device, the method comprising: Receiving topology structure request information sent by the server, the topology structure request information including communication addresses corresponding to all control modules in the target device, the communication addresses corresponding to all control modules in the target device being obtained from an initial physical model corresponding to the category of the target device in the server, the initial physical model corresponding to the category of the target device including the types and quantities of all control modules included in the device of the category, so as to adapt to topology data of different target devices; collecting topology data of the target device based on the topology structure request information, and sending the topology data to the server; receiving a data collection rule sent by the server based on the topology data; Data is collected from the target device based on the data collection rules, and the collected data is sent to the server.

2. The method according to claim 1, characterized in that Before receiving the topology structure request information sent by the server, the method includes: Sending device identification information of the target device to the server; Receive an authentication result generated by the server based on the device identification information.

3. The method according to claim 2, characterized in that After receiving the authentication result generated by the server based on the device identification information, the method further includes: When the authentication result is successful, monitoring the topology request information sent by the server.

4. The method according to claim 3, characterized in that Before monitoring the topology structure request information sent by the server, the method includes: Monitoring the key information sent by the server; Receive and store the key information sent by the server.

5. The method according to claim 1, characterized in that After sending the topology data to the server, the method further includes: Determining whether to adjust the data collection rule currently used by the target device; If the received data collection rule is selected to be used, the data collection rule currently used by the target device is updated using the received data collection rule, and the version number of the received data collection rule is sent to the server; If the historical data collection rule is selected, the version number corresponding to the historical data collection rule is sent to the server; If it is chosen to continue using the data collection rule currently used by the target device, the data collection rule currently used by the target device is retained.

6. A device data collection method, characterized in that: Applied to a server, the server being communicatively connected to a gateway device, the gateway device being communicatively connected to a target device, the method comprising: Sending topology request information to the gateway device, the topology request information including communication addresses corresponding to all control modules in the target device, the communication addresses corresponding to all control modules in the target device being obtained from an initial physical model corresponding to the category of the target device in the server, the initial physical model corresponding to the category of the target device including types and quantities of all modules included in the device of the category, so as to adapt topology data of different target devices; receiving topology data of the target device collected by the gateway device based on the topology structure request information; generating data collection rules based on the topological data; Sending the data collection rules to the gateway device; Receive data collected by the gateway device from the target device based on the data collection rule.

7. The method according to claim 6, characterized in that Before sending the topology request information to the gateway device, the method includes: receiving device identification information of the target device sent by the gateway device; Authentication is performed based on the device identification information to obtain an authentication result.

8. The method according to claim 7, characterized in that After the authentication is performed based on the device identification information to obtain an authentication result, the method includes: When the authentication result is successful, the authentication result is sent to the gateway device, and key information and the topology request information are sequentially sent to the gateway device.

9. The method according to claim 6, characterized in that After sending the data collection rules to the gateway device, the method includes: Receiving the version number of the data collection rule sent by the gateway device; Matching the version number of the data collection rule with the version number of the data collection rule previously sent to the gateway device to obtain a matching result; If the matching result is consistent, it is determined that the data collection rule is sent successfully.

10. A gateway device, characterized in that: The system comprises a memory and a processor, wherein the memory is used to store program data, and the program data can be executed by the processor to implement the method according to any one of claims 1 to 5.

11. A server, characterized in that: The system comprises a memory and a processor, wherein the memory is used to store program data, and the program data can be executed by the processor to implement the method according to any one of claims 6 to 9.

12. A device data acquisition system, characterized in that: The method comprises the gateway device as claimed in claim 10 and the server as claimed in claim 11.

Images