Data management method of sensor, electronic equipment and storage medium

Abstract

The invention discloses a data management method of a sensor, electronic equipment and a storage medium, and relates to the technical field of servers, and the method comprises the steps that after the sensor is connected with the server through a first interface position, an identifier of the sensor is generated, and the identifier of the sensor is used for indicating the sensor currently connected with the server. According to the identification of the sensor and the first interface position, first record information and an event log of the sensor are generated, and the first record information and the event log of the sensor are associated through the identification of the sensor and the first interface position. Since the identifier of the sensor is used for indicating the sensor currently connected with the server, the record information associated with the event log of the sensor only has the current record information of the sensor. The condition that the event log of the sensor is associated with the recorded information of other sensors due to multiplexing of the connection position information of the sensor is avoided, so that the accuracy of managing the data of the sensor is improved.

Description

Technical Field

[0001] This application relates to the technical field of servers, and in particular, to a method for managing sensor data, an electronic device, and a storage medium. Background Art

[0002] For network devices with high requirements for the operating environment, to ensure the stability of the operation of the network device, one or more sensors can be deployed in the network device to detect the operating conditions of the network device in real time.

[0003] In the related art, a sensor can be connected to a server through a certain connection position of the Intelligent Platform Management Interface (IPMI). The server generates a Sensor Data Record (SDR) and a Sensor Event Log (SEL) of the sensor, and the SDR and the SEL are associated through this connection position. By querying the SEL, the operating conditions of the network device can be monitored or the operating faults of the network device can be troubleshot. Specifically, after receiving a query request, the server parses the SEL according to the SDR associated with the SEL, and then displays the parsed SEL. According to the parsed SEL, the operating conditions of the network device can be monitored or the operating faults of the network device can be troubleshot.

[0004] However, when the sensor is disconnected from the server, there may be a situation where this connection position is reused, that is, other sensors establish a connection with the server through this connection position. At this time, the server will associate the SEL of this sensor with the SDR of other sensors according to this connection position, resulting in chaotic management of the SEL. Therefore, there is an urgent need for a method for managing sensor data. Summary of the Invention

[0005] This application provides a method for managing sensor data, an electronic device, and a storage medium, so as to improve the accuracy of managing sensor data.

[0006] This application provides a method for managing sensor data, including:

[0007] When the sensor is connected to the server through the first interface position, generating an identifier of the sensor, where the identifier of the sensor is used to indicate the sensor currently establishing a connection with the server;

[0008] Generating first record information of the sensor according to the identifier of the sensor and the first interface position; wherein, the first record information includes the identifier of the sensor and the connection position information of the sensor, and the connection position information is used to indicate the first interface position;

[0009] Generate an event log of the sensor, where the event log includes the identifier of the sensor and the connection location information of the sensor;

[0010] Perform an association process on the first record information and the event log.

[0011] This application also provides an electronic device, including: a memory for storing a computer program; a processor for implementing the steps of any of the above sensor data management methods when executing the computer program.

[0012] This application also provides a computer-readable storage medium storing a computer program, wherein the computer program implements the steps of any of the above sensor data management methods when executed by a processor.

[0013] This application also provides a computer program product including a computer program that implements the steps of any of the above sensor data management methods when executed by a processor.

[0014] In the sensor data management method, electronic device, and storage medium provided by the embodiments of this application, after the sensor is connected to the server through the first interface location on IPMI, the server generates an identifier of the sensor, and based on the identifier of the sensor and the first interface location, generates the first record information of the sensor and the event log of the sensor. Since both the first record information of the sensor and the event log of the sensor include the identifier of the sensor and the connection location information of the sensor, therefore, the first record information of the sensor and the event log of the sensor can be associated based on the identifier of the sensor and the connection location information of the sensor. In the above method, since the identifier of the sensor is used to indicate the currently connected sensor, after the first record information of the sensor and the event log of the sensor are associated based on the identifier of the sensor and the connection location information of the sensor, the only record information associated with the event log of the sensor is the current first record information of the sensor. This avoids the situation where the event log of the sensor is associated with the record information of other sensors due to the reuse of the connection location information of the sensor, thereby improving the accuracy of managing the data of the sensor. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] To more clearly illustrate the embodiments of this application, the following will briefly introduce the drawings required for the embodiments. Obviously, the drawings in the following description are only some embodiments of this application. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0016] Figure 1 It is a schematic diagram of the reuse of connection location information provided by the embodiments of this application;

[0017] Figure 2 Schematic diagram of the application scenario provided by the embodiment of the present application;

[0018] Figure 3 Schematic flowchart of a data management method for a sensor provided by the embodiment of the present application;

[0019] Figure 4 Schematic flowchart of another data management method for a sensor provided by the embodiment of the present application;

[0020] Figure 5 Schematic flowchart of the record information management process for a sensor provided by the embodiment of the present application;

[0021] Figure 6 Schematic flowchart of the event log query process for a sensor provided by the embodiment of the present application;

[0022] Figure 7 Schematic diagram of an IPMI management system provided by the embodiment of the present application;

[0023] Figure 8 Schematic flowchart when a sensor establishes a connection with a server provided by the embodiment of the present application;

[0024] Figure 9 Schematic flowchart when a sensor disconnects from a server provided by the embodiment of the present application;

[0025] Figure 10 Schematic flowchart of the process of converting and processing event logs provided by the embodiment of the present application;

[0026] Figure 11 Schematic flowchart of the adjustment of the operating parameters of the target device provided by the embodiment of the present application;

[0027] Figure 12 Schematic diagram of the structure of a data management device for a sensor provided by the embodiment of the present application;

[0028] Figure 13 Schematic diagram of the structure of the electronic device provided by the present application. Detailed implementation manners

[0029] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the protection scope of the present application.

[0030] It should be noted that in the description of this application, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or further includes elements inherent to such process, method, article or device. The terms "first", "second", etc. in this application are used to distinguish similar objects and are not used to describe a specific order or sequence.

[0031] First, the nouns involved in this application are explained:

[0032] IPMI is a standard interface for remotely managing and monitoring the operating status of network devices. IPMI is used to monitor and manage the physical health status of network devices. Exemplarily, IPMI is used to monitor the temperature, voltage, fan operating status, power status, etc. of network devices. Network devices may include devices such as servers and storage devices.

[0033] SDR is used to store metadata information of sensors. The metadata information may include, for example: the type of sensor, the connection location information of the sensor, etc.

[0034] SEL is used to record relevant events of sensors. The relevant events may include, for example, abnormal events triggered by sensors, and / or status change events triggered by sensors, etc.

[0035] For network devices with high requirements for the operating environment, one or more sensors can be deployed in the network devices to detect the operating conditions of the network devices in real time.

[0036] In the related art, one or more sensors can be connected to a server through IPMI, and the server generates SDR and SEL of the sensors. It should be noted that both SDR and SEL include the connection location information of the sensors, and SDR and SEL are associated through the connection location information. When staff members view the operating conditions of network devices, they can determine the SDR associated with SEL according to the connection location information in SEL, and convert SEL according to the SDR associated with SEL, and display the converted SEL.

[0037] However, when the sensor is disconnected from the server, the server will delete the SDR of the sensor. At this time, the SEL of the sensor has no associated SDR, so the SEL of the sensor cannot be parsed. In addition, when a new sensor is connected to the server through IPMI and the connection position of the new sensor on IPMI is the same as that of this sensor, it causes the reuse of connection position information, that is, the connection position information of the new sensor is the same as that of this sensor. At this time, the server will associate the SEL of this sensor with the SDR of the new sensor, resulting in an incorrect association of the sensor's SEL. In summary, the above method has a chaotic management of sensor logs.

[0038] It can be understood in combination with Figure 1 as follows. Figure 1 FIG. is a schematic diagram of the reuse of connection position information provided by an embodiment of the present application. Please refer to Figure 1 , the sensor includes an IPMI controller, a first storage area, and an IPMI function module, and sensors 1 and 2 are deployed in the network device.

[0039] After sensor 1 is connected to the server through connection position a on IPMI, the IPMI controller creates the SDR of sensor 1, stores the SDR of sensor 1 in the first storage area, then generates the SEL of sensor 1, and the SEL of sensor 1 is associated with the SDR of sensor 1 through connection position information 0x01, where the connection position information 0x01 is the connection position information corresponding to connection position a. When sensor 1 is disconnected from the server, the IPMI controller deletes the SDR of sensor 1 in the first storage area.

[0040] After sensor 2 is connected to the server through connection position a on IPMI, the IPMI controller creates the SDR of sensor 2, stores the SDR of sensor 2 in the first storage area, then generates the SEL of sensor 2, and the SEL of sensor 2 is associated with the SDR of sensor 2 through connection position information 0x01.

[0041] When the IPMI function module receives a query request, and the query request is used to request to query the SEL of sensor 1, according to the connection position information 0x01 in the SEL of sensor 1, the SDR associated with the SEL of the sensor is determined. At this time, since the SDR of sensor 1 has been deleted and the SDR of sensor 2 includes the connection position information 0x01. Therefore, the IPMI function module determines that the SDR associated with the SEL of sensor 1 is the SDR of sensor 2, resulting in an incorrect parsing of the SEL of sensor 1.

[0042] The data management method for the sensor provided by this application generates an identifier for the sensor after the sensor is connected to the server through the first interface position on IPMI. The identifier of the sensor is used to indicate the currently connected sensor to the server, and the connection position information of the sensor is determined according to the first interface position. Then, according to the identifier of the sensor and the first interface position, the first record information of the sensor and the event log of the sensor are generated. Since the identifier of the sensor is used to indicate the currently connected sensor to the server, therefore, after the first record information of the sensor and the event log of the sensor are associated through the identifier of the sensor and the connection position information of the sensor, the only record information associated with the event log of the sensor is the current first record information of the sensor. This avoids the situation where the event log of the sensor is associated with the record information of other sensors due to the reuse of the connection position information of the sensor, thereby improving the accuracy of managing the data of the sensor.

[0043] In order to enable those skilled in the art of this technology to better understand the solution of this application, the following further elaborates on this application in conjunction with the accompanying drawings and specific embodiments.

[0044] Combined with the specific application environment architecture or specific hardware architecture on which the execution of the data management method of the sensor depends, the specific application environment architecture or specific hardware architecture is described herein. Refer to Figure 2 , Figure 2 is a schematic diagram of the application scenario provided by the embodiment of this application. As Figure 2 shown, it includes: a network device 11 and a server 12. Among them, the network device 11 includes a temperature sensor 13 and a pressure sensor 14. Among them, the temperature sensor 13 can detect the temperature of the network device 11 during operation in real time, and the pressure sensor 14 can detect the pressure value of the network device 11 during operation in real time.

[0045] In the actual application process, the temperature sensor 13 and the pressure sensor 14 can be connected to the server 12 through IPMI in the server 12. Taking the temperature sensor 13 as an example, after the temperature sensor 13 is connected to the server 12, the server 12 will generate the first record information and event log of the temperature sensor 13, and the first record information of the temperature sensor 13 is associated with the event log. When the staff queries the event log of the temperature sensor 13, the server 12 will determine the associated first record information according to the event log of the temperature sensor 13, then convert the event log of the temperature sensor 13 according to the first record information to obtain the converted event log, and display the converted event log.

[0046] It should be noted that Figure 2 only schematically shows an application scenario in the form of an example, and is not a limitation on the application scenario.

[0047] The technical solution of the present application and how the technical solution of the present application solves the above technical problems will be described in detail below with specific embodiments. The following several specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below with reference to the accompanying drawings.

[0048] Figure 3 As shown in the flowchart of a data management method for a sensor provided by an embodiment of the present application, Figure 3 as shown, an embodiment of the present application provides a data management method for a sensor, and a detailed description of this method is as follows:

[0049] S301: When the sensor is connected to the server through the first interface position, generate an identifier of the sensor, where the identifier of the sensor is used to indicate the sensor currently connected to the server.

[0050] The execution subject of the present application can be a server. The server is the background server of the IPMI management system, or can be a data management device for sensors provided in the server. The data management device for sensors can be implemented by software, or by a combination of software and hardware.

[0051] The sensor is a sensor deployed in a network device and is used to detect the operating conditions of the network device. The sensor can include, for example, a temperature sensor, a pressure sensor, a power sensor, a fan sensor, etc.

[0052] The server includes IPMI, and there are multiple interface positions on the IPMI, and the multiple interface positions are used to connect to sensors. The first interface position is the interface position among the multiple interface positions that is connected to the sensor. The sensor can be connected to the server through the first interface position on the IPMI.

[0053] It should be noted that after the sensor is connected to the server, the server will generate an identifier of the sensor. The identifier of the sensor is used to indicate the sensor connected to the server at the current moment.

[0054] S302: Generate first record information of the sensor according to the identifier of the sensor and the first interface position; wherein, the first record information includes the identifier of the sensor and the connection position information of the sensor, and the connection position information is used to indicate the first interface position.

[0055] The first record information refers to the record information of the sensor connected to the server. For example, the first record information of the sensor can be the SDR of the sensor. The first record information includes the identifier of the sensor and the connection location information of the sensor. Among them, the connection location information of the sensor is used to indicate the position of the first interface on the IPMI connected to the sensor. Therefore, the connection location information of the sensor can be determined according to the position of the first interface.

[0056] In some embodiments, the IPMI includes multiple interface positions, and each interface position corresponds to a connection location information. Therefore, after the sensor is connected to the server through the first interface position on the IPMI, the server determines the connection location information corresponding to the first interface position according to the first interface position connected to the sensor, and determines the connection location information corresponding to the first interface position as the connection location information of the sensor.

[0057] In some embodiments, the connection location information can be represented by a hexadecimal code. Exemplarily, the connection location information can be represented as 0x01, 0x02, etc.

[0058] Exemplarily, assume that the interface positions on the IPMI include interface position 1, interface position 2, and interface position 3. Among them, the connection location information corresponding to interface position 1 is 0x01, the connection location information corresponding to interface position 2 is 0x02, and the connection location information corresponding to interface position 3 is 0x03. After sensor A is connected to the server through interface position 2 on the IPMI, the server determines that the connection location information of the sensor is 0x02.

[0059] S303: Generate an event log of the sensor. The event log includes the identifier of the sensor and the connection location information of the sensor.

[0060] The event log of the sensor is used to record the events triggered by the sensor. The event log of the sensor can be, for example, the SEL of the sensor. In some embodiments, the sensor will send detection data to the server through the IPMI. The detection data is the data obtained by the sensor detecting the network device. Exemplarily, assume that the sensor is a temperature sensor. The detection data sent by the temperature sensor to the server through the IPMI is the data obtained by the temperature sensor detecting the network device. After the server receives the detection data sent by the sensor, it determines whether the detection data is abnormal. In the case where the detection data is abnormal, an abnormal event triggered by the sensor is recorded in the event log of the sensor. Therefore, the server can generate an event log of the sensor and detect the running status of the network device through the event log of the sensor.

[0061] It should be noted that the event log also includes the identifier of the sensor and the connection location information of the sensor.

[0062] S304: Perform an association process on the first record information and the event log.

[0063] Since the first record information includes the identifier of the sensor and the connection location information of the sensor, and the event log also includes the identifier of the sensor and the connection location information of the sensor. Therefore, the first record information and the time log can be associated through the identifier of the sensor and the connection location information of the sensor.

[0064] After performing the association process on the first record information and the event log, there is an association relationship between the first record information and the event log. In this way, the first record information associated with the event log can be determined according to the identifier of the sensor and the connection location information of the sensor in the event log. Since the identifier of the sensor is used to indicate the sensor currently connected to the server, the first record information associated with the event log of the sensor is the current first record information of the sensor.

[0065] In Figure 3 In the illustrated embodiment, after the sensor is connected to the server through the first interface location on the IPMI, the server generates the identifier of the sensor. Then, according to the identifier of the sensor and the first interface location, the first record information of the sensor and the event log of the sensor are generated. Since both the first record information of the sensor and the event log of the sensor include the identifier of the sensor and the connection location information of the sensor, the first record information of the sensor and the event log of the sensor can be associated through the identifier of the sensor and the connection location information of the sensor. In the above method, since the identifier of the sensor is used to indicate the sensor currently connected to the server, the record information associated with the event log of the sensor is only the current first record information of the sensor. This avoids the situation where the event log of the sensor is associated with the record information of other sensors due to the reuse of the connection location information of the sensor, thereby improving the accuracy of managing the sensor log.

[0066] In Figure 3 Based on the illustrated embodiment, below, in combination with Figure 4 The data management method for sensors provided by the embodiments of the present application will be further described.

[0067] Figure 4 For another data management method for sensors provided by the embodiments of the present application, as shown in Figure 4 The process may include the following steps:

[0068] S401: The sensor is connected to the server through the first interface location.

[0069] For a specific introduction to how the sensor is connected to the server through the first interface location, refer to Figure 3In the embodiment shown in S301, it will not be elaborated here.

[0070] S402: The server generates an identifier for the sensor.

[0071] In some embodiments, the identifier of the sensor is mainly divided into two parts. One part is used to indicate the time when the sensor establishes a connection with the server through the first interface position, and the second part is a random number generated by the server. Since the identifier of the sensor includes the moment when the sensor establishes a connection with the server and the random number generated by the server, when the sensor connects to the server, the server generates the identifier of the sensor to uniquely identify the sensor currently connected to the server.

[0072] The way for the server to generate the identifier of the sensor can be as follows: Determine the time when the sensor establishes a connection with the server through the first interface position; Generate the identifier of the sensor according to the time when the sensor establishes a connection with the server through the first interface position.

[0073] Exemplarily, assume that sensor A connects to the server through the first interface position, and the time when sensor A establishes a connection with the server through the first interface position is 8:30:25. Then the server generates the identifier of the sensor according to the event that the sensor establishes a connection with the server through the first interface position, which can be 083025890512. Among them, 083025 is used to indicate that the time when sensor A establishes a connection with the server through the first interface position is 8:30:25; 890512 is the random number generated by the server.

[0074] S403: The server generates the first record information of the sensor according to the identifier of the sensor and the first interface position.

[0075] The way to generate the first record information of the sensor can be as follows: Determine the type of the sensor and the first state between the sensor and the server. Among them, the first state is the connection established state; Process the identifier of the sensor, the first interface position, the type of the sensor, and the state between the sensor and the server according to the preset format of the record information to generate the first record information; The first record information includes the type of the sensor, the state between the sensor and the server, the identifier of the sensor, and the connection location information.

[0076] The type of the sensor is used to indicate the function of the sensor. Exemplarily, the type of the sensor can be, for example, a temperature sensor, a pressure sensor, etc. Taking the type of the sensor as a temperature sensor as an example, the temperature sensor is used to indicate that the function of the sensor is to detect the temperature of the network device during operation. In some embodiments, after the sensor establishes a connection with the server through the first interface position, the sensor will receive the type of the sensor sent by the client.

[0077] The first state between the sensor and the server is the connection established state, which means that a connection is established between the sensor and the server.

[0078] In some embodiments, to unify the format of the recorded information of the sensor, a preset format of the recorded information can be set, and the preset format of the recorded information can be set according to the content included in the recorded information. Exemplarily, assuming that the recorded information includes the type of the sensor, the state between the sensor and the server, the identifier of the sensor, and the connection location information, the preset format of the recorded information can be as shown in Table 1:

[0079] Table 1

[0080]

[0081] Therefore, in the case of determining the type of the sensor, the identifier of the sensor, the connection location information, and the state between the sensor and the server, the first recorded information of the sensor can be determined according to the preset format of the recorded information.

[0082] Exemplarily, assuming that the type of the sensor is a temperature sensor, the identifier of the sensor is 083025890512, the connection location information is 0x01, the state between the sensor and the server is the first state, and the preset format of the recorded information is as shown in Table 1. Then the first recorded information of the sensor can be as shown in Table 2:

[0083] Table 2

[0084]

[0085] In some embodiments, the first recorded information of the sensor may further include the moment when the sensor establishes a connection with the server, and the moment when the sensor establishes a connection with the server can be represented by a timestamp. Exemplarily, assuming that the moment when the sensor establishes a connection with the server is 14:30 on May 9, 2023, the first recorded information of the sensor further includes the timestamp of 14:30 on May 9, 2023.

[0086] S404: The server generates an event log of the sensor.

[0087] For a detailed introduction to generating the event log of the sensor, reference can be made to Figure 3 S303 in the illustrated embodiment, which will not be elaborated here.

[0088] S405: The server performs an association process on the first recorded information and the event log.

[0089] For a detailed introduction to performing an association process on the first recorded information and the event log, reference can be made to Figure 3 S304 in the illustrated embodiment, which will not be elaborated here.

[0090] In Figure 4 In the illustrated embodiment, according to the event of establishing a connection between the sensor and the server, the identifier of the sensor is generated, and at the same time, a random number part is added to the identifier of the sensor, so that the generated sensor identifier can uniquely indicate the currently connected sensor to the server. Therefore, after correlating the first record information of the sensor and the event log of the sensor according to the identifier of the sensor and the connection location information of the sensor, the only record information associated with the event log of the sensor is the first record information of the sensor. This avoids the situation where the event log of the sensor is associated with the record information of other sensors due to the reuse of the connection location information of the sensor, thereby improving the accuracy of managing the data of the sensor.

[0091] In the method for managing the data of the sensor introduced in the above embodiment, it mainly focuses on the management of the event log of the sensor after the sensor establishes a connection with the server. In addition, the method for managing the data of the sensor provided in the embodiments of the present application further includes: managing the record information of the sensor in the case where the sensor is disconnected from the server. Below, in combination with Figure 5 The process of managing the record information of the sensor in the case where the sensor is disconnected from the server will be described.

[0092] Figure 5 FIG. Figure 5 shows a schematic diagram of the process for managing the record information of a sensor provided in an embodiment of the present application. Please refer to

[0093] S501: In the case where the sensor is disconnected from the server, update the first state to obtain a second state between the sensor and the server, and the second state is a disconnected state.

[0094] The second state is used to indicate that the sensor is disconnected from the server. Therefore, in the case where the sensor is disconnected from the server, update the first state between the sensor and the server to the second state.

[0095] S502: Update the first record information according to the second state to obtain second record information.

[0096] The second record information is the record information of the sensor disconnected from the server. Among them, the second record information includes the type of the sensor, the state between the sensor and the server, the identifier of the sensor, and the connection location information. It should be noted that the state between the sensor and the server in the second record information is the second state.

[0097] Exemplarily, assume that the first record information of sensor A is as shown in Table 3:

[0098] Table 3

[0099]

[0100] Update the first recorded information of sensor A according to the second state, and the second recorded information of sensor A can be as shown in Table 4:

[0101] Table 4

[0102]

[0103] In some embodiments, if the first recorded information of the sensor further includes: the moment when the connection between the sensor and the server is established. In the case where the sensor is disconnected from the server, record the moment when the sensor is disconnected from the server, and update the time when the connection between the sensor and the server in the first recorded information to the moment when the sensor is disconnected from the server. That is, the second recorded information may further include the moment when the sensor is disconnected from the server, and the moment when the sensor is disconnected from the server in the second recorded information is represented in the form of a timestamp.

[0104] S503: Store the second recorded information in the second storage area in the server; the second storage area is a storage area for storing historical record information, and the historical record information is the record information of sensors that are currently disconnected from the server.

[0105] It should be noted that the first recorded information is stored in the first storage area in the server, and the first storage area is a storage area for storing real-time record information, and the real-time record information is the record information of sensors that are currently connected to the server.

[0106] Since the server will delete the record information of the sensor in the first storage area after the sensor is disconnected from the server. Therefore, after the sensor is disconnected from the server, it is necessary to store the second recorded information of the sensor in the second storage area. In this way, even if the sensor is disconnected from the server, the record information of the sensor is still stored in the server.

[0107] In Figure 5In the illustrated embodiment, when the sensor is disconnected from the server, the state between the sensor and the server is updated from the first state to the second state, and the first record information is updated according to the second state to obtain the second record information of the sensor. Then, the second record information is stored from the first storage area to the second storage area. Through the above method, after the sensor is disconnected from the server, the first record information of the sensor is updated to the second record information, and the state between the sensor and the server in the second record information is the second state. Finally, the second record information is stored in the second storage area. Therefore, even if the server deletes the record information of the sensor in the first storage area after the sensor is disconnected from the server, the record information of the sensor will be stored in the second storage area. In this way, it can be ensured that there is always record information associated with the event log of the sensor, and even when the sensor is disconnected from the server, the event log of the sensor can be converted.

[0108] In the above embodiment, the method for managing the data of the sensor is introduced, including the method for managing the event log of the sensor when the sensor is connected to the server, and the method for managing the record information of the sensor when the sensor is disconnected from the server. In addition, the method for managing the data of the sensor provided in the embodiment of the present application further includes querying the event log of the sensor. Next, with reference to Figure 6 the illustrated embodiment, the process of querying the event log of the sensor provided in the embodiment of the present application will be described.

[0109] Figure 6 The following is a schematic diagram of the event log query process of a sensor provided in the embodiment of the present application. Please refer to Figure 6 and the process may include the following steps:

[0110] S601: Receive a query request for querying the event log of the sensor.

[0111] In some embodiments, the operating condition of the network device where the sensor is located can be queried by querying the event log of the sensor. Exemplarily, it is assumed that sensors A, B, and C are deployed in the network device. The operating condition of the network device can be queried by querying the event logs of sensors A, B, and C.

[0112] Therefore, when it is necessary to query the operating condition of the network device, a query request can be sent to the server, and the query request is used to request to query the time log of the sensor.

[0113] S602: Determine the record information associated with the event log according to the connection location information of the sensor and the identifier of the sensor in the event log.

[0114] It should be noted that the event log also includes the type code of the sensor and the detection result of the sensor; among them, the type code of the sensor is the code after encrypting the type of the sensor; the detection result of the sensor refers to the event triggered according to the detection data of the sensor. Exemplarily, assume that sensor A is a temperature sensor, and the detection data of sensor A is greater than or equal to the preset threshold. At this time, the detection result of the sensor is that the temperature is too high.

[0115] Since the type code of the sensor is the encrypted type of the sensor, if the event log of the sensor is directly displayed, the staff cannot directly determine the type of the sensor based on the type code of the sensor. Therefore, after receiving the query request, the server needs to determine the record information associated with the event log of the sensor, and perform conversion processing on the event log of the sensor according to the type of the sensor in the record information associated with the event log.

[0116] For each sensor, the record information associated with the event log of the sensor is the record information of the sensor. Therefore, the record information associated with the event log can be determined according to the connection position information of the sensor and the identifier of the sensor in the event log.

[0117] In some embodiments, the method for determining the record information associated with the event log may be as follows: According to the connection position information of the sensor, determine whether the third record information including the connection position information of the sensor is stored in the first storage area; in the case where the third record information is stored in the first storage area, determine whether the third record information includes the identifier of the sensor; in the case where the third record information includes the identifier of the sensor, determine the third record information as the record information associated with the event log; in the case where the third record information is not stored in the first storage area, or the third record information does not include the identifier of the sensor, determine the record information associated with the event log in the second storage area according to the connection position information of the sensor and the identifier of the sensor.

[0118] Since the first storage area is a storage area for storing real-time record information. Therefore, according to the connection position information of the sensor, the third record information including the connection position information of the sensor can be determined from the real-time record information in the first storage area. If the third record information is stored in the first storage area, then determine whether the third record information includes the identifier of the sensor. In the case where the third record information includes the identifier of the sensor, determine the third record information as the record information associated with the event log. In this way, it is possible to avoid determining incorrect record information due to the reuse of location information.

[0119] When the third record information does not exist in the first storage area or the third record information does not include the identifier of the sensor, it indicates that the record information of the sensor is not stored in the first storage area. Therefore, the record information associated with the event log can be determined in the second storage area according to the connection position information of the sensor and the identifier of the sensor.

[0120] The method for determining the record information associated with the event log in the second storage area can be as follows: According to the connection position information of the sensor, at least one fourth record information including the connection position information of the sensor is determined in the second storage area; the record information including the identifier of the sensor among the at least one fourth record information is determined as the record information associated with the event log.

[0121] The fourth record information is the record information in the second storage area that includes the connection position information of the sensor. It should be noted that due to the possible situation of connection position reuse, there may be multiple fourth record information in the second storage area. Therefore, at least one fourth record information can be determined in the second storage area according to the connection position information of the sensor.

[0122] Then, for each fourth record information among the at least one fourth record information, it is determined whether the fourth record information includes the identifier of the sensor. The fourth record information including the identifier of the sensor is determined as the record information associated with the event log.

[0123] In some embodiments, the method for determining the record information associated with the event log can also be as follows: In the first storage area and the second storage area, at least one fifth record information is searched for, and the at least one fifth record information includes the connection position information of the sensor; the record information including the identifier of the sensor among the at least one fifth record information is determined as the record information associated with the event log.

[0124] The fifth record information is the record information in the real-time record information in the first storage area and the historical record information in the second storage area that includes the connection position information of the sensor. Due to the possible situation of connection position information reuse, there is at least one fifth record information in the first storage area and the second storage area.

[0125] After determining the at least one fifth record information, according to the identifier of the sensor, among the at least one fifth record information, the fifth record information including the identifier of the sensor is determined, and the fifth record information including the identifier of the sensor is determined as the record information associated with the event log.

[0126] S603: According to the record information associated with the event log, perform conversion processing on the event log to obtain the converted event log.

[0127] In some embodiments, according to the record information associated with the event log, the way to perform conversion processing on the event log to obtain the converted event log can be as follows: According to the type of the sensor in the record information associated with the event log, perform conversion processing on the type code of the sensor to obtain the converted type code of the sensor; The converted event log includes: the connection location information of the sensor, the identifier of the sensor, the converted type code of the sensor, and the detection result of the sensor.

[0128] Since the type code of the sensor is the encrypted code of the type of the sensor, therefore, according to the type of the sensor in the record information associated with the event log, conversion processing can be performed on the type code of the sensor, and the converted type code of the sensor is the type of the sensor.

[0129] Exemplarily, assume that the type of the sensor in the record information associated with the event log is a temperature sensor, and the type code of the sensor is XFWX. Then, according to the type of the sensor, conversion is performed on the type code of the sensor, and the converted type code of the sensor is a temperature sensor.

[0130] S604: Display the converted event log.

[0131] After obtaining the converted event log, the server displays the converted event log to facilitate the staff to view.

[0132] Since the converted event log includes the connection location information of the sensor, the identifier of the sensor, the converted type code of the sensor, and the detection result of the sensor. In this way, after displaying the converted event log, the staff can directly determine the operating conditions of the network device through the converted event log.

[0133] In Figure 6In the illustrated embodiment, after receiving a query request, the server determines the record information associated with the event log in the first storage area and the second storage area according to the connection location information of the sensor and the identifier of the sensor. Then, according to the type of the sensor in the record information associated with the event log, the event log is converted, and finally the converted event log is displayed to facilitate the staff to view the event log. In the above manner, the server determines the record information associated with the event log in the first storage area and the second storage area according to the connection location of the sensor and the identifier of the sensor. Since the identifier of the sensor is used to uniquely identify the sensor currently connected to the server, in the case of multiplexing of the connection locations of the sensors, the correct record information associated with the event log can be determined, avoiding incorrect conversion of the event logs of the sensors; in addition, in the case where the sensor is disconnected from the server and there is no multiplexing of the connection locations of the sensors, the server can still determine the record information associated with the event log, avoiding the problem that the event log cannot be converted due to the lack of record information associated with the event log after the sensor is disconnected from the server.

[0134] The above embodiment introduces the data management method of the sensor provided by the present application. It should be noted that the data management method of the sensor provided by the present application is implemented based on the IPMI management system. Next, in combination with Figure 7 the IPMI management system provided by the embodiments of the present application will be further introduced.

[0135] Figure 7 FIG. is a schematic diagram of an IPMI management system provided by an embodiment of the present application. Please refer to Figure 7 , the IPMI management system includes an IPMI control module, an IPMI query module, a first storage area, and a second storage area. Among them, the IPMI control module can be, for example, an IPMI controller, and the IPMI control module includes a sensor monitoring sub-module and an identifier generation sub-module; the IPMI query module can be, for example, an IPMI function module, and the IPMI query module includes a conversion sub-module and a display sub-module.

[0136] In some embodiments, when the sensor monitoring sub-module detects that a sensor is connected to the server, it determines the moment when the sensor establishes a connection with the server, and sends indication information to the identifier generation sub-module. The indication information includes the moment when the sensor establishes a connection with the server. After receiving the indication information, the identifier generation sub-module generates an identifier for the sensor and sends the identifier of the sensor to the sensor monitoring sub-module. The sensor monitoring sub-module generates the first record information of the sensor and stores the first record information of the sensor in the first storage area.

[0137] It can be understood in combination with Figure 8 Figure 8 ​The following is a schematic flow diagram of a sensor establishing a connection with a server provided by an embodiment of the present application. Please refer to Figure 8 , and this process may include the following:

[0138] S801: The sensor establishes a connection with the server through the first interface position on IPMI.

[0139] S802: The IPMI monitoring sub-module detects that the sensor has established a connection with the server.

[0140] After the IPMI monitoring sub-module detects that the sensor has established a connection with the server, it sends indication information to the identification generation sub-module. The indication information includes the moment when the sensor establishes a connection with the server. The indication information is used to instruct the identification generation sub-module to generate an identification of the sensor according to the moment when the sensor establishes a connection with the server.

[0141] S803: The identification generation sub-module generates an identification of the sensor.

[0142] After receiving the indication information, the identification generation sub-module generates an identification of the sensor and sends the identification of the sensor to the IPMI monitoring sub-module.

[0143] S804: The IPMI monitoring sub-module determines the type of the sensor and the connection position information of the sensor.

[0144] S805: The IPMI monitoring sub-module obtains the preset format of the record information.

[0145] S806: The IPMI monitoring sub-module generates the first record information according to the preset format of the record information.

[0146] The first record information includes the identification of the sensor, the connection position information, the type of the sensor, and the status between the sensor and the server. It should be noted that the status between the sensor and the server in the first record information is the first status.

[0147] S807: The IPMI monitoring sub-module writes the first record information of the sensor into the first storage area.

[0148] S808: The IPMI monitoring sub-module determines whether the writing of the first record information is successful.

[0149] If so, execute S809;

[0150] If not, execute S811.

[0151] S809: The IPMI monitoring sub-module records the time when the sensor establishes a connection with the server in the first record information.

[0152] S810: The IPMI monitoring sub-module updates the list of sensors currently connected to the server.

[0153] Updating the list of sensors currently connected to the server means adding the first record information of the sensor to the list of sensors currently connected to the server.

[0154] S811: The IPMI monitoring sub-module triggers an event that the writing of the first record information of the error fails.

[0155] In some embodiments, when the sensor monitoring sub-module detects that a sensor is disconnected from the server, it updates the first record information of the sensor to obtain the second record information of the sensor, and stores the second record information of the sensor in the second storage area.

[0156] It can be understood in combination with Figure 9 For Figure 9 FIG. Figure 9 is a schematic flow diagram of a sensor being disconnected from the server provided by an embodiment of the present application. Please refer to

[0157] S901: The sensor disconnects from the server through the first interface position on the IPMI.

[0158] S902: The IPMI monitoring sub-module detects that the sensor is disconnected from the server.

[0159] S903: The IPMI monitoring sub-module queries whether there is the first record information of the sensor in the list of sensors currently connected to the server according to the type of the sensor.

[0160] If so, execute S904;

[0161] If not, execute S909.

[0162] S904: The IPMI monitoring sub-module determines the first record information of the sensor in the first storage area according to the identifier of the sensor.

[0163] S905: The IPMI monitoring sub-module updates the status between the sensor and the server in the first record information from the first status to the second status to obtain the second record information of the sensor.

[0164] S906: The IPMI monitoring sub-module records the time when the sensor is disconnected from the server in the second record information.

[0165] S907: The IPMI monitoring sub-module stores the second record information of the sensor in the second storage area.

[0166] S908: The IPMI monitoring sub-module updates the list of sensors currently connected to the server.

[0167] At this time, updating the list of sensors currently connected to the server means deleting the first record information of this sensor from the list of sensors currently connected to the server.

[0168] S909: The IPMI monitoring sub-module triggers a warning that this sensor is an invalid sensor.

[0169] In some embodiments, after receiving a query request, the conversion sub-module in the IPMI query module determines the record information associated with the event log in the first storage area according to the connection location information of the sensor and the identifier of the sensor in the event log, and in the case where no record information associated with the event log is stored in the first storage area, determines the record information associated with the event log in the second storage area. Then, according to the type of the sensor in the record information associated with the event log, the event log is converted, and the converted event log is sent to the display sub-module. After receiving the converted event log, the display sub-module displays the converted event log.

[0170] It can be understood in combination with Figure 10 For Figure 10 FIG. is a schematic flowchart of a process for converting and processing an event log provided by an embodiment of the present application. Please refer to Figure 10 , and this process may include the following contents:

[0171] S1001: The conversion sub-module obtains the event log.

[0172] S1002: The conversion sub-module obtains the connection location information of the sensor and the identifier of the sensor in the event log.

[0173] S1003: The conversion sub-module determines whether there is third record information in the first storage area according to the connection location information of the sensor.

[0174] If so, execute S1004;

[0175] If not, execute S1006.

[0176] S1004: The conversion sub-module determines whether the third record information includes the identifier of the sensor.

[0177] If so, execute S1005;

[0178] If not, execute S1006.

[0179] S1005: The conversion sub-module determines that the third record information is the record information associated with the event log.

[0180] S1006: The conversion sub-module determines whether there is record information associated with the event log in the second storage area according to the connection position information of the sensor and the identifier of the sensor.

[0181] If so, execute S1007;

[0182] If not, execute S1009.

[0183] S1007: The conversion sub-module performs conversion processing on the event log according to the record information associated with the event log to obtain the converted event log.

[0184] S1008: The display sub-module displays the converted event log.

[0185] S1009: The display sub-module displays "unknown sensor".

[0186] In the case where record information associated with the event log is not queried, since the event log cannot be converted, an unknown sensor is displayed to indicate that the type of the sensor corresponding to the event log cannot be determined.

[0187] In Figure 7 In the IPMI management system shown, after the sensor is connected to the server, the identifier generation sub-module generates the identifier of the sensor, and then the sensor monitoring sub-module generates the first record information of the sensor and stores the first record information in the first storage area. After the sensor is disconnected from the server, the sensor monitoring sub-module updates the first record information of the sensor to obtain the second record information of the sensor and stores the second record information in the second storage area. In this way, when the conversion sub-module receives a query request, it determines the record information associated with the event log in the first storage area and the second storage area according to the connection position information of the sensor and the identifier of the sensor in the event log, and converts the event log according to the record information associated with the event log to obtain the converted event log. The display sub-module displays the converted event log.

[0188] Since the identifier of the sensor indicates the sensor currently connected to the server, after the event log of the sensor and the first record information are associated through the connection location information of the sensor and the identifier of the sensor, the event log of the sensor is uniquely associated with the first record information of the sensor. In the case where the connection location of the sensor is reused, it will not be associated with the record information of other sensors. And in the case where the sensor is disconnected from the server, the second record information of the sensor is stored in the second storage area. In this way, even when the sensor is disconnected from the server, there is still record information associated with the event log of the sensor in the server. Therefore, after receiving the query information, the event log can be accurately converted and then the converted event log can be displayed. In summary, the IPMI management system provided by the embodiments of the present application improves the accuracy of managing the data of the sensor.

[0189] Based on the above embodiments, the method for managing sensor data provided by the embodiments of the present application further includes: adjusting the operating parameters of the network device when the detection data of the sensor is abnormal. Next, in combination with Figure 11 , a further introduction to the adjustment method of the operating parameters of the network device provided by the embodiments of the present application will be given.

[0190] Figure 11 The following is a flowchart for adjusting the operating parameters of a target device provided by the embodiments of the present application. Please refer to Figure 11 , and this process may include the following steps:

[0191] S1101: Receive the detection data sent by the sensor. The detection data is the data obtained by the sensor detecting the target device; the target device is the device where the sensor is located.

[0192] Exemplarily, assume that the sensor is a temperature sensor, the target device is the network device where the temperature sensor is located, and the detection data is the temperature value obtained by the temperature sensor detecting the target device during operation.

[0193] In some embodiments, after the sensor is connected to the server, the sensor periodically sends detection data to the server.

[0194] S1102: When the detection data is abnormal, determine the cause of the abnormality of the detection data according to the type of the sensor and the detection data.

[0195] After receiving the detection data, the server determines whether the detection data is abnormal. Specifically, when the detection data is greater than or equal to the preset threshold, it is determined that the detection data is abnormal; when the detection data is less than the preset threshold, it is determined that the detection data is normal.

[0196] Exemplarily, assume the sensor is a temperature sensor, the detection data received by the server is 40 degrees, and the preset threshold is 35 degrees. Then, the detection data of the temperature sensor is abnormal data. Assume the sensor is a board sensor, which is used to detect whether the board in the target device is in place. When the board is detected to be in place, the detection data is 0; when the board is detected not to be in place, the detection data is 1. Therefore, for this board sensor, the preset threshold is 1. Assume the detection data received by the server is 0, which indicates that the detection data of the board sensor is normal data.

[0197] In some embodiments, the abnormal cause of the detection data can be determined according to the type of the sensor and the detection data. The specific method can be as follows: Obtain the detection information corresponding to the type of at least one candidate sensor; wherein, for each candidate sensor type in the type of at least one candidate sensor, the detection information corresponding to the candidate sensor type includes at least one set of historical detection data of the candidate sensor and the abnormal cause corresponding to each set of historical detection data; Determine the target detection information in the historical detection information corresponding to the type of at least one candidate sensor according to the type of the sensor; Determine the abnormal cause of the detection data in the target detection information according to the detection data.

[0198] The type of at least one candidate sensor may include, for example, a temperature sensor, a voltage sensor, etc. Taking the candidate sensor type as a temperature sensor as an example, the detection information corresponding to the temperature sensor includes at least one set of historical detection data. It should be noted that at least one set of historical detection data is the abnormal data of the temperature sensor at a historical moment, and for each set of historical detection data, the detection information corresponding to the temperature sensor also includes the abnormal cause corresponding to this set of historical detection data.

[0199] Therefore, when the server receives the detection data of the sensor and determines that the detection data of the sensor is abnormal data, it can determine the candidate sensor type that is the same as the type of this sensor among the type of at least one candidate sensor. And in at least one set of historical detection data corresponding to this candidate sensor type, determine the historical detection data set corresponding to the detection data of this sensor, and finally determine the abnormal cause corresponding to this set of historical detection data as the abnormal cause of the detection data.

[0200] S1103: Adjust the operating parameters of the target device according to the abnormal cause of the detection data.

[0201] The method of adjusting the operating parameters of the target device according to the abnormal cause of the detection data can be as follows: Determine the corresponding adjustment parameter according to the abnormal cause of the detection data; Send an instruction to the target device, and the instruction is used to instruct the target device to adjust the operating parameters of the target device according to the adjustment parameter.

[0202] In some embodiments, the operating parameters of the target device can be adjusted according to the abnormal cause of the detection data, so that during the operation of the target device according to the adjusted parameters, the detection data of the sensor can return to normal.

[0203] Exemplarily, assume that the fan speed of the target device is 5 revolutions per second, the sensor is a temperature sensor, and the abnormal cause of the detection data of the temperature sensor is that the fan speed is relatively slow. At this time, during the operation of the target device, the fan speed parameter of the target device can be adjusted to increase the fan speed to 10 revolutions per second.

[0204] Then, send an instruction to the target device. After receiving the instruction, the target device adjusts its current operating parameters according to the operating parameters of the target device indicated in the instruction.

[0205] Exemplarily, assume that the current fan speed of the target device is 5 revolutions per second and the adjustment parameter is to increase the fan speed to 10 revolutions per second. After receiving the instruction, the target device increases the current fan speed of 5 revolutions per second to 10 revolutions per second.

[0206] In Figure 11 In the shown embodiment, after the sensor establishes a connection with the server, the server receives the detection data sent by the sensor, and in the case of abnormal detection data, determines the abnormal cause of the detection data from the detection information corresponding to the type of at least one candidate sensor according to the type of the sensor and the detection data, and finally adjusts the operating parameters of the target device according to the abnormal cause. In the above implementation manner, by dynamically analyzing the abnormal cause of the sensor detection data and timely adjusting the operating parameters of the target device, the probability of failure of the target device is reduced, and the reliability of the operation of the target device is improved.

[0207] Figure 12 This is a schematic structural diagram of a data management device for sensors provided by an embodiment of the present application. As Figure 12 shown, an embodiment of the present application also provides a data management device 120 for sensors. The device includes a first generation module 121, a second generation module 122, a third generation module 123, and a processing module 124, where:

[0208] The first generation module 121 is configured to generate an identifier of the sensor when the sensor is connected to the server through the first interface position, and the identifier of the sensor is used to indicate the sensor currently connected to the server;

[0209] The second generation module 122 is configured to generate first record information of the sensor according to the identifier of the sensor and the first interface position; wherein, the first record information includes the identifier of the sensor and the connection position information of the sensor, and the connection position information is used to indicate the first interface position;

[0210] A third generation module 123 for generating an event log of the sensor, where the event log includes the identification of the sensor and the connection location information of the sensor;

[0211] A processing module 124 for performing an association process on the first record information and the event log.

[0212] For the description of the features in the corresponding embodiment of the sensor data management device 120, reference can be made to the relevant description in the corresponding embodiment of the sensor data management method, which will not be elaborated here one by one.

[0213] Figure 13 This is a schematic structural diagram of the electronic device provided by this application. As Figure 13 shown, the electronic device 130 provided in this embodiment includes at least one processor 131 and a memory 132. Optionally, the electronic device 130 further includes a communication component 133. Among them, the processor 131, the memory 132, and the communication component 133 are connected through a bus.

[0214] In the specific implementation process, at least one processor 131 executes the computer execution instructions stored in the memory 132, so that at least one processor 131 executes the above-mentioned embodiment of the sensor data management method.

[0215] For the specific implementation process of the processor 131, reference can be made to the above method embodiment, and its implementation principle and technical effects are similar, which will not be elaborated here in this embodiment.

[0216] In the above embodiment, it should be understood that the processor may be a central processing unit (Central Processing Unit, abbreviated as: CPU), or other general-purpose processors, digital signal processors (Digital Signal Processor, abbreviated as: DSP), application specific integrated circuits (Application Specific Integrated Circuit, abbreviated as: ASIC), etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the application can be directly implemented by the hardware processor, or implemented by a combination of hardware and software modules in the processor.

[0217] The memory may include a high-speed memory (Random Access Memory, RAM), and may also include a non-volatile memory (Non-volatile Memory, NVM), such as at least one disk memory.

[0218] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the buses in the drawings of the present application are not limited to only one bus or one type of bus.

[0219] An embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored. Wherein, the computer program is configured to execute the steps in any of the above-mentioned embodiments of the data management method for a sensor when running.

[0220] In an exemplary embodiment, the above-mentioned computer-readable storage medium may include, but is not limited to: various media that can store computer programs such as a USB flash drive, a read-only memory (ROM for short), a random access memory (RAM for short), a mobile hard disk, a magnetic disk, or an optical disc.

[0221] An embodiment of the present application also provides a computer program product. The above-mentioned computer program product includes a computer program, and when the computer program is executed by a processor, the steps in any of the above-mentioned embodiments of the data management method for a sensor are implemented.

[0222] An embodiment of the present application also provides another computer program product, including a non-volatile computer-readable storage medium. The non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in any of the above-mentioned embodiments of the data management method for a sensor are implemented.

[0223] Those skilled in the art can further realize that the units and algorithm steps of each example described in combination with the embodiments disclosed in this article can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0224] The above has introduced in detail a data management method, an electronic device, and a storage medium of a sensor provided in this application. Specific examples are used in this article to elaborate on the principle and implementation manner of this application. The description of the above embodiments is only used to help understand the method and its core idea of this application. It should be noted that for those of ordinary skill in the art of this technology, without departing from the principle of this application, several improvements and modifications can still be made to this application, and these improvements and modifications also fall within the protection scope of the claims of this application.

Claims

1. A method for data management of a sensor, characterized in that, The method includes: Generating an identifier of the sensor when the sensor is connected to the server through a first interface location, where the identifier of the sensor is used to indicate the sensor currently establishing a connection with the server; Generating first record information of the sensor according to the identifier of the sensor and the first interface location; wherein, the first record information includes the identifier of the sensor and connection location information of the sensor, and the connection location information is used to indicate the first interface location; Generating an event log of the sensor, where the event log includes the identifier of the sensor and the connection location information of the sensor; Performing an association process on the first record information and the event log.

2. The method according to claim 1, wherein The generating the identifier of the sensor includes: Determining the time when the sensor establishes a connection with the server through the first interface location; Generating the identifier of the sensor according to the time when the sensor establishes a connection with the server through the first interface location.

3. The method according to claim 1 or 2, characterized in that, The generating the first record information of the sensor according to the identifier of the sensor and the first interface location includes: Determining the type of the sensor and a first state between the sensor and the server, where the first state is a connection established state; Processing the identifier of the sensor, the first interface location, the type of the sensor, and the state between the sensor and the server according to a preset format of record information to generate the first record information; the first record information includes the type of the sensor, the state between the sensor and the server, the identifier of the sensor, and the connection location information.

4. The method according to claim 3, characterized in that, The first record information is stored in a first storage area in the server, and the first storage area is a storage area for storing real-time record information, and the real-time record information is record information of a sensor currently establishing a connection with the server; The method further includes: Updating the first state when the sensor is disconnected from the server to obtain a second state between the sensor and the server, and the second state is a disconnected state; Updating the first record information according to the second state to obtain second record information; Storing the second record information in a second storage area in the server; the second storage area is a storage area for storing historical record information, and the historical record information is record information of a sensor currently disconnected from the server.

5. The method according to claim 4, wherein The method further includes: Receiving a query request, where the query request is used to request to query the event log of the sensor; Determining record information associated with the event log according to the connection location information of the sensor and the identifier of the sensor in the event log; Performing a conversion process on the event log according to the record information associated with the event log to obtain a converted event log; Displaying the converted event log.

6. The method according to claim 5, wherein The determining the record information associated with the event log according to the connection location information of the sensor and the identifier of the sensor in the event log includes: Determine whether third record information including the connection location information of the sensor is stored in the first storage area according to the connection location information of the sensor; When the third record information is stored in the first storage area, determine whether the sensor identifier is included in the third record information; When the sensor identifier is included in the third record information, determine the third record information as the record information associated with the event log; When the third record information is not stored in the first storage area, or when the sensor identifier is not included in the third record information, determine the record information associated with the event log in the second storage area according to the connection location information of the sensor and the sensor identifier; 7. The method according to claim 6, characterized in that, The determining the record information associated with the event log in the second storage area according to the connection location information of the sensor and the sensor identifier includes: Determine at least one fourth record information including the connection location information of the sensor in the second storage area according to the connection location information of the sensor; Determine the record information including the sensor identifier among the at least one fourth record information as the record information associated with the event log; 8. The method according to claim 5, wherein The determining the record information associated with the event log according to the connection location information of the sensor and the sensor identifier in the event log includes: Search for at least one fifth record information including the connection location information of the sensor in the first storage area and the second storage area; Determine the record information including the sensor identifier among the at least one fifth record information as the record information associated with the event log; 9. The method according to claim 5, wherein The event log further includes the type code of the sensor and the detection result of the sensor; the performing conversion processing on the event log according to the record information associated with the event log to obtain a converted event log includes: Perform conversion processing on the type code of the sensor according to the type of the sensor in the record information associated with the event log to obtain a converted type code of the sensor; The converted event log includes: the connection location information of the sensor, the sensor identifier, the converted type code of the sensor, and the detection result of the sensor; 10. The method according to claim 1 or 2, characterized in that, The method further includes: Receive the detection data sent by the sensor, where the detection data is the data obtained by the sensor detecting the target device; the target device is the device where the sensor is located; When the detection data is abnormal, determine the abnormal cause of the detection data according to the type of the sensor and the detection data; Adjust the operating parameters of the target device according to the abnormal cause of the detection data; 11. The method according to claim 10, characterized in that, The determining the abnormal cause of the detection data according to the type of the sensor and the detection data includes: Obtain detection information corresponding to the type of at least one candidate sensor; wherein, for each candidate sensor type among the types of the at least one candidate sensor, the detection information corresponding to the candidate sensor type includes at least one set of historical detection data of the candidate sensor, and the cause of abnormality corresponding to each set of historical detection data; Determine target detection information in the historical detection information corresponding to the type of the at least one candidate sensor according to the type of the sensor; Determine the cause of abnormality of the detection data in the target detection information according to the detection data.

12. The method according to claim 10, wherein Adjusting the operating state of the target device according to the cause of the abnormality of the detection data includes: Determine corresponding adjustment parameters according to the cause of the abnormality of the detection data; Send an instruction to the target device, and the instruction is used to instruct the target device to adjust the operating parameters of the target device according to the adjustment parameters.

13. An electronic device, characterized in that, Includes: A memory for storing computer programs; A processor, when executing the computer program, implements the steps of the data management method of the sensor according to any one of claims 1 to 12.

14. A computer-readable storage medium, characterized in that, A computer program is stored in the computer-readable storage medium, wherein the computer program, when executed by a processor, implements the steps of the data management method of the sensor according to any one of claims 1 to 12.

15. A computer program product, comprising a computer program, characterized in that, The computer program, when executed by a processor, implements the steps of the data management method of the sensor according to any one of claims 1 to 12.

Images