Sensor data management method, electronic device and storage medium

Abstract

The present application discloses a sensor data management method, electronic device and storage medium, which relate to the field of server technology, including: after the sensor is connected to the server through a first interface position, a sensor identifier is generated, and the sensor identifier is used to indicate the sensor currently connected to the server. Then, based on the sensor identifier and the first interface position, the sensor's first record information and event log are generated, wherein the sensor's first record information and event log are associated through the sensor identifier and the first interface position. Since the sensor identifier is used to indicate the sensor currently connected to the server, the only record information associated with the sensor's event log is the current record information of the sensor. This avoids the situation where the sensor's event log is associated with the record information of other sensors due to the reuse of the sensor's connection location information, thereby improving the accuracy of sensor data management.

Description

Technical Field

[0001] The present application relates to the field of server technology, and in particular to a sensor data management method, electronic device, and storage medium. Background Art

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

[0003] In related technologies, a sensor can connect to a server via a connection location on the Intelligent Platform Management Interface (IPMI). The server generates a sensor data record (SDR) and a sensor event log (SEL) for the sensor, and the SDR and SEL are associated via this connection location. By querying the SEL, the operating status of network devices can be monitored or operational failures of network devices can be troubleshooted. Specifically, after receiving a query request, the server parses the SEL based on the SDR associated with the SEL and then displays the parsed SEL. Based on the parsed SEL, the operating status of network devices can be monitored or operational failures of network devices can be troubleshooted.

[0004] However, after a sensor is disconnected from the server, the connection location may be reused, meaning that other sensors may connect to the server through the same connection location. In this case, the server will associate the sensor's SEL with the SDR of another sensor based on the connection location, leading to confusion in SEL management. Therefore, a sensor data management method is urgently needed. Summary of the Invention

[0005] The present application provides a sensor data management method, electronic device, and storage medium to improve the accuracy of sensor data management.

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

[0007] When the sensor is connected to the server through the first interface position, generating a sensor identifier, the sensor identifier being used to indicate the sensor currently connected to the server;

[0008] Generate first record information of the sensor according to the sensor identifier and the first interface position; wherein the first record information includes the sensor identifier 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, the event log including the sensor identification and the sensor connection location information;

[0010] The first record information and the event log are associated with each other.

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

[0012] The present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned sensor data management methods are implemented.

[0013] The present application also provides a computer program product, including a computer program, which implements the steps of any of the above-mentioned sensor data management methods when executed by a processor.

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

[0015] In order to more clearly illustrate the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0016] Figure 1 A schematic diagram of connection location information reuse provided in an embodiment of the present application;

[0017] Figure 2 Schematic diagram of application scenarios provided by embodiments of the present application;

[0018] Figure 3 A flow chart of a sensor data management method provided in an embodiment of the present application;

[0019] Figure 4 A flow chart of another sensor data management method provided in an embodiment of the present application;

[0020] Figure 5 A schematic diagram of a sensor recording information management process provided in an embodiment of the present application;

[0021] Figure 6 A schematic diagram of a sensor event log query process provided in an embodiment of the present application;

[0022] Figure 7 A schematic diagram of an IPMI management system provided in an embodiment of the present application;

[0023] Figure 8 A schematic diagram of a process for establishing a connection between a sensor and a server provided in an embodiment of the present application;

[0024] Figure 9 A schematic diagram of a process flow when a sensor is disconnected from a server according to an embodiment of the present application;

[0025] Figure 10 A schematic diagram of a process for converting event logs provided in an embodiment of the present application;

[0026] Figure 11 A flowchart of adjusting operating parameters of a target device provided in an embodiment of the present application;

[0027] Figure 12 A schematic diagram of the structure of a sensor data management device provided in an embodiment of the present application;

[0028] Figure 13 This is a schematic diagram of the structure of the electronic device provided in this application. DETAILED DESCRIPTION

[0029] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0030] It should be noted that, in the description of this application, the terms "comprises," "includes," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or 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 particular order or sequence.

[0031] First, let’s explain the terms involved in this application:

[0032] IPMI is a standard interface for remotely managing and monitoring the operational status of network devices. It is used to monitor and manage the physical health of network devices. For example, IPMI monitors the device's temperature, voltage, fan status, and power supply status. Network devices can include servers, storage devices, and other devices.

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

[0034] The SEL is used to record sensor-related events. The related events may include, for example, abnormal events triggered by the sensor and / or state change events triggered by the sensor.

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

[0036] In related technologies, one or more sensors can connect to a server via IPMI, which generates the sensor's SDR and SEL. It should be noted that both the SDR and SEL include the sensor's connection location information, and the SDR and SEL are associated through this connection location information. When checking the operation of a network device, staff can determine the SDR associated with the SEL based on the connection location information in the SEL. They can then convert the SEL based on the SDR associated with the SEL and display the converted SEL.

[0037] However, when a sensor is disconnected from the server, the server deletes the sensor's SDR. At this point, the sensor's SEL has no associated SDR, making it impossible to parse the sensor's SEL. Furthermore, when a new sensor is connected to the server via IPMI, and the new sensor's connection location on IPMI matches that of the previous sensor, the connection location information is reused, meaning the new sensor's connection location information matches that of the previous sensor. At this point, the server associates the sensor's SEL with the new sensor's SDR, resulting in incorrect sensor SEL association. In summary, the above method disrupts sensor log management.

[0038] Can be combined Figure 1 To understand, Figure 1 This is a schematic diagram of a connection location information reuse method provided in an embodiment of the present application. Figure 1 The sensor includes an IPMI controller, a first storage area and an IPMI function module, and the network device is deployed with sensor 1 and sensor 2.

[0039] After sensor 1 connects to the server via connection location a on the IPMI, the IPMI controller creates an SDR for sensor 1 and stores it in the first storage area. It then generates an SEL for sensor 1. This SEL is associated with the SDR using connection location information 0x01, which corresponds to connection location a. When sensor 1 disconnects from the server, the IPMI controller deletes the SDR from the first storage area.

[0040] After sensor 2 is connected to the server through connection location a on the IPMI, the IPMI controller creates an SDR for sensor 2 and stores the SDR for sensor 2 in the first storage area. Then, the SEL for sensor 2 is generated. The SEL for sensor 2 is associated with the SDR for sensor 2 through the connection location information 0x01.

[0041] When the IPMI function module receives a query request for sensor 1's SEL, it determines the SDR associated with that sensor's SEL based on the connection location information 0x01 in sensor 1's SEL. However, because sensor 1's SDR has been deleted and sensor 2's SDR includes the connection location information 0x01, the IPMI function module determines that the SDR associated with sensor 1's SEL is sensor 2's SDR, resulting in an incorrect parsing of sensor 1's SEL.

[0042] The sensor data management method provided by the present application generates a sensor identifier after the sensor is connected to the server via the first interface location on the IPMI. The sensor identifier is used to indicate the sensor currently connected to the server, and the sensor connection location information is determined based on the first interface location. Then, based on the sensor identifier and the first interface location, the sensor's first record information and the sensor's event log are generated. Since the sensor identifier is used to indicate the sensor currently connected to the server, after the sensor's first record information and the sensor's event log are associated via the sensor identifier and the sensor's connection location information, the only record information associated with the sensor's event log is the sensor's current first record information. This avoids the situation where the sensor's event log is associated with the record information of other sensors due to the reuse of the sensor's connection location information, thereby improving the accuracy of sensor data management.

[0043] In order to enable those skilled in the art to better understand the present application, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0044] In conjunction with the specific application environment architecture or specific hardware architecture on which the execution of the sensor data management method depends, the specific application environment architecture or specific hardware architecture is described herein. Figure 2 , Figure 2 This is a schematic diagram of an application scenario provided by an embodiment of the present application. Figure 2 As shown, it includes: a network device 11 and a server 12, wherein the network device 11 includes a temperature sensor 13 and a pressure sensor 14, wherein 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 actual use, temperature sensor 13 and pressure sensor 14 can be connected to server 12 via the IPMI in server 12. Taking temperature sensor 13 as an example, after temperature sensor 13 is connected to server 12, server 12 generates first record information and an event log for temperature sensor 13, and the first record information of temperature sensor 13 is associated with the event log. When a staff member queries the event log of temperature sensor 13, server 12 determines the first record information associated with the event log of temperature sensor 13 based on the event log of temperature sensor 13, then converts the event log of temperature sensor 13 based on the first record information to obtain a converted event log, and displays the converted event log.

[0046] It should be noted that Figure 2 This is just an example to illustrate an application scenario, and is not intended to limit the application scenario.

[0047] The following specific embodiments describe in detail the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems. The following 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 in conjunction with the accompanying drawings.

[0048] Figure 3 A flow chart of a sensor data management method provided in an embodiment of the present application is shown as follows: Figure 3 As shown, the embodiment of the present application provides a sensor data management method, which is described in detail as follows:

[0049] S301: When a sensor is connected to a server through a first interface, a sensor identifier is generated, where the sensor identifier is used to indicate the sensor currently connected to the server.

[0050] The execution subject of this application can be a server, which is the background server of the IPMI management system, or a data management device of a sensor set in the server. The data management device of the sensor can be implemented through software, or through a combination of software and hardware.

[0051] Sensors are sensors deployed in network devices to detect the operation of network devices. Sensors may include temperature sensors, pressure sensors, power sensors, fan sensors, etc.

[0052] The server includes an IPMI, which includes multiple interface locations, and the multiple interface locations are used to connect to sensors. A first interface location is an interface location connected to the sensor among the multiple interface locations. The sensor can be connected to the server through the first interface location on the IPMI.

[0053] It should be noted that after a sensor is connected to a server, the server will generate an ID for the sensor, which is used to indicate the sensor currently connected to the server.

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

[0055] The first recorded information refers to recorded information of a sensor connected to the server. For example, the first recorded information of the sensor may be the sensor's SDR. The first recorded information includes the sensor's identifier and the sensor's connection location information. The sensor's connection location information indicates the location of the first interface connected to the sensor on the IPMI. Therefore, the sensor's connection location information can be determined based on the first interface location.

[0056] In some embodiments, the IPMI includes multiple interface locations, and each interface location corresponds to a piece of connection location information. Therefore, when a sensor is connected to a server via a first interface location on the IPMI, the server determines the connection location information corresponding to the first interface location based on the first interface location connected to the sensor, and determines the connection location information corresponding to the first interface location as the connection location information of the sensor.

[0057] In some embodiments, the connection location information may be represented by hexadecimal encoding, for example, 0x01, 0x02, and so on.

[0058] For example, assume that the interface locations on the IPMI include interface location 1, interface location 2, and interface location 3, where the connection location information corresponding to interface location 1 is 0x01, the connection location information corresponding to interface location 2 is 0x02, and the connection location information corresponding to interface location 3 is 0x03. After sensor A connects to the server through interface location 2 on the IPMI, the server determines that the sensor's connection location information is 0x02.

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

[0060] The event log of the sensor is used to record 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 sends detection data to the server via IPMI. The detection data is data obtained by the sensor when detecting the network device. For example, assuming that the sensor is a temperature sensor, the detection data sent by the temperature sensor to the server via IPMI is data obtained by the temperature sensor when detecting the network device. After receiving the detection data sent by the sensor, the server determines whether the detection data is abnormal. In the case that the detection data is abnormal, the abnormal event triggered by the sensor is recorded in the event log of the sensor. Therefore, the server can generate an event log for the sensor and detect the operation status of the network device through the event log of the sensor.

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

[0062] S304: Associating the first record information with the event log.

[0063] Since the first record information includes the sensor identifier and the sensor connection location information, and the event log also includes the sensor identifier and the sensor connection location information, the first record information and the event log can be associated with each other through the sensor identifier and the sensor connection location information.

[0064] After the first record information and the event log are associated, an association relationship is established between the first record information and the event log. Thus, the first record information associated with the event log can be determined based on the sensor identifier and the sensor connection location information in the event log. Because the sensor identifier indicates the sensor currently connected to the server, the first record information associated with a sensor's event log is the current first record information for that sensor.

[0065] exist Figure 3 In the illustrated embodiment, after the sensor is connected to the server via the first interface location on the IPMI, the server generates an identifier for the sensor. Then, based on the identifier and the first interface location of the sensor, 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 with each other 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 sensor currently connected to the server, 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 the management of the sensor log.

[0066] exist Figure 3 Based on the embodiment shown below, combined with Figure 4 The sensor data management method provided in the embodiment of the present application is further described.

[0067] Figure 4 A flow chart of another sensor data management method provided in an embodiment of the present application is shown as follows: Figure 4 As shown, the process may include the following steps:

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

[0069] For details on connecting the sensor to the server through the first interface, see Figure 3S301 in the illustrated embodiment will not be described in detail here.

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

[0071] In some embodiments, the sensor identifier is primarily composed of two parts: one part indicates the time when the sensor established a connection with the server via the first interface location, and the second part is a random number generated by the server. Because the sensor identifier includes the time when the sensor established a connection with the server and the random number generated by the server, when the sensor connects to the server, the server generates the sensor identifier to uniquely identify the sensor currently connected to the server.

[0072] The server may generate the sensor identifier in the following manner: determining the time when the sensor establishes a connection with the server through the first interface location; and generating the sensor identifier according to the time when the sensor establishes a connection with the server through the first interface location.

[0073] For example, assuming that sensor A connects to the server via the first interface location and the time at which the connection is established is 8:30:25, then the server may generate a sensor identifier of 083025890512 based on the event of the sensor connecting to the server via the first interface location. 083025 indicates that the time at which the connection is established is 8:30:25, and 890512 is a random number generated by the server.

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

[0075] The method of generating the first record information of the sensor can be as follows: determining the type of the sensor and the first state between the sensor and the server, wherein the first state is a connection establishment state; processing the sensor identifier, the first interface location, the sensor type, and the state between the sensor and the server according to a preset format of the record information to generate the first record information; the first record information includes the sensor type, the state between the sensor and the server, the sensor identifier, and the connection location information.

[0076] The sensor type indicates the function of the sensor. For example, the sensor type can be a temperature sensor, a pressure sensor, or the like. For example, if the sensor type is a temperature sensor, the temperature sensor indicates that the sensor's function is to detect the temperature of the network device during operation. In some embodiments, after the sensor establishes a connection with the server via the first interface location, the sensor receives the sensor type sent by the client.

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

[0078] In some embodiments, to unify the format of sensor recording information, a preset format of the recording information can be set. The preset format of the recording information can be set according to the content included in the recording information. For example, assuming that the recording information includes the type of sensor, the status between the sensor and the server, the sensor's identification and connection location information, the preset format of the recording information can be as shown in Table 1:

[0079] Table 1

[0080]

[0081] Therefore, when the type of the sensor, the identification of the sensor, the connection location information, and the status between the sensor and the server are determined, the first recording information of the sensor can be determined according to the preset format of the recording information.

[0082] For example, assuming that the sensor type is a temperature sensor, the sensor identifier 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 determined as shown in Table 2:

[0083] Table 2

[0084]

[0085] In some embodiments, the first recorded information of the sensor may also include the time when the sensor established a connection with the server, where the time when the sensor established a connection with the server may be represented by a timestamp. For example, assuming that the time when the sensor established a connection with the server was 2:30 PM on May 9, 2023, the first recorded information of the sensor may also include the timestamp of 2:30 PM on May 9, 2023.

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

[0087] For details on generating sensor event logs, see Figure 3 S303 in the illustrated embodiment will not be described in detail here.

[0088] S405: The server associates the first record information with the event log.

[0089] For details on how to associate the first record information with the event log, see Figure 3 S304 in the illustrated embodiment will not be described in detail here.

[0090] exist Figure 4 In the illustrated embodiment, a sensor identifier is generated based on the event of establishing a connection between a sensor and a server. A random number is added to the sensor identifier, allowing the generated sensor identifier to uniquely identify the sensor currently connected to the server. Therefore, after correlating the sensor's first recorded information with its event log based on the sensor identifier and its connection location information, the only recorded information associated with the sensor's event log is the sensor's first recorded information. This avoids the situation where a sensor's event log becomes associated with recorded information from other sensors due to reuse of sensor connection location information, thereby improving the accuracy of sensor data management.

[0091] In the sensor data management method described in the above embodiment, the main focus is on the management of the sensor event log after the sensor is connected to the server. In addition, the sensor data management method provided in the embodiment of the present application also includes: managing the recorded information of the sensor when the sensor is disconnected from the server. Figure 5 This section describes the process of managing sensor log information when the sensor is disconnected from the server.

[0092] Figure 5 This is a flow chart of sensor record information management provided by an embodiment of the present application. Figure 5 , the process may include the following steps:

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

[0094] The second state is used to indicate that the sensor is disconnected from the server. Therefore, when the sensor is disconnected from the server, the first state between the sensor and the server is updated to the second state.

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

[0096] The second recorded information is recorded information about a sensor that has been disconnected from the server. The second recorded information includes the sensor type, the status between the sensor and the server, the sensor identifier, and the connection location. It should be noted that the status between the sensor and the server in the second recorded information is the second status.

[0097] For example, it is assumed that the first recorded information of sensor A is as shown in Table 3:

[0098] Table 3

[0099]

[0100] The first record information of sensor A is updated according to the second state, and the second record information of sensor A is obtained as shown in Table 4:

[0101] Table 4

[0102]

[0103] In some embodiments, if the first recorded information of the sensor also includes the time when the connection between the sensor and the server was established, and if the sensor and the server are disconnected, the time of disconnection is recorded, and the time when the connection between the sensor and the server was established in the first recorded information is updated to the time when the connection between the sensor and the server was disconnected. In other words, the second recorded information may also include the time when the sensor and the server were disconnected, and the time of disconnection in the second recorded information is represented by a timestamp.

[0104] S503: 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 the sensor that is currently disconnected from the server.

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

[0106] After a sensor is disconnected from the server, the server deletes the sensor's recorded information from the first storage area. Therefore, after the sensor is disconnected from the server, the sensor's second recorded information needs to be stored in the second storage area. This way, even after the sensor is disconnected from the server, the server still stores the sensor's recorded information.

[0107] exist 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. The second record information is then 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, and finally the second record information is stored in the second storage area. Therefore, even if the sensor is disconnected from the server and the server deletes the record information of the sensor in the first storage area, the record information of the sensor will still be stored in the second storage area. In this way, it can be ensured that the record information associated with the event log of the sensor is always present, and the event log of the sensor can be converted even if the sensor is disconnected from the server.

[0108] In the above embodiment, the sensor data management method is introduced, which includes a method for managing the sensor event log when the sensor is connected to the server; and a method for managing the sensor recorded information when the sensor is disconnected from the server. In addition, the sensor data management method provided in the embodiment of the present application also includes querying the sensor event log. Figure 6 The embodiment shown illustrates the event log query process of the sensor provided in the embodiment of the present application.

[0109] Figure 6 For a flow chart of event log query of a sensor provided in an embodiment of the present application, please refer to Figure 6 , the process may include the following steps:

[0110] S601: Receive a query request, where the query request is used to query an event log of a sensor.

[0111] In some embodiments, the operation status of a network device can be queried by querying the event log of a sensor, where the network device is the device where the sensor is located. For example, assuming that sensors A, B, and C are deployed in the network device, the operation status of the network device can be queried by querying the event logs of sensor A, sensor B, and sensor C.

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

[0113] S602: Determine 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] If necessary, the event log also includes the sensor type code and sensor detection results. The sensor type code is an encrypted code of the sensor type, and the sensor detection result refers to the event triggered by the sensor's detection data. For example, assuming sensor A is a temperature sensor and its detection data is greater than or equal to a preset threshold, the sensor's detection result is "overtemperature."

[0115] Because the sensor type code is an encrypted representation of the sensor type, if the sensor event log is displayed directly, the staff cannot directly determine the sensor type based on the sensor type code. Therefore, after receiving the query request, the server needs to determine the record information associated with the sensor event log and convert the sensor event log based on the sensor type 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 based on the sensor connection location information and the sensor identifier in the event log of the sensor.

[0117] In some embodiments, the method for determining the record information associated with the event log can be as follows: based on the connection location information of the sensor, determine whether third record information is stored in the first storage area, and the third record information includes the connection location information of the sensor; if the third record information is stored in the first storage area, determine whether the third record information includes the identification of the sensor; if the third record information includes the identification of the sensor, determine the third record information as the record information associated with the event log; if the third record information is not stored in the first storage area, or if the third record information does not include the identification of the sensor, determine the record information associated with the event log in the second storage area based on the connection location information of the sensor and the identification of the sensor.

[0118] Since the first storage area is used to store real-time log information, the third log information including the sensor's connection location information can be determined from the real-time log information in the first storage area based on the sensor's connection location information. If the third log information is stored in the first storage area, a determination is made as to whether the third log information includes the sensor's identifier. If so, the third log information is determined to be log information associated with the event log. This prevents incorrect log information from being determined due to reuse of location information.

[0119] If the third record information does not exist in the first storage area, or the third record information does not include the sensor identifier, it indicates that the sensor's record information 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 based on the sensor's connection location information and the sensor identifier.

[0120] The method for determining the record information associated with the event log in the second storage area can be as follows: based on the connection location information of the sensor, determine at least one fourth record information including the connection location information of the sensor in the second storage area; and determine the record information including the identification of the sensor in the at least one fourth record information 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 sensor's connection location information. It should be noted that due to the possibility of connection location reuse, there may be multiple fourth record information items in the second storage area. Therefore, based on the sensor's connection location information, at least one fourth record information item can be determined in the second storage area.

[0122] Then, for each fourth record information in the at least one fourth record information, it is determined whether the fourth record information includes the sensor identifier. The fourth record information including the sensor identifier 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, search for at least one fifth record information, and the at least one fifth record information includes the connection location information of the sensor; determine the record information including the identification of the sensor in the at least one fifth record information as the record information associated with the event log.

[0124] The fifth record information is the real-time record information in the first storage area and the record information in the second storage area, including the sensor's connection location information. Because connection location information may be reused, at least one fifth record information is included in the first and second storage areas.

[0125] After determining at least one fifth record information, according to the identification of the sensor, determine the fifth record information including the identification of the sensor in the at least one fifth record information, and determine the fifth record information including the identification of the sensor as the record information associated with the event log.

[0126] S603: Convert the event log according to the record information associated with the event log to obtain a converted event log.

[0127] In some embodiments, the event log is converted based on the record information associated with the event log, and the method for obtaining the converted event log can be as follows: based on the type of sensor in the record information associated with the event log, the type code of the sensor is converted to obtain the converted type code of the sensor; the converted event log includes: the connection location information of the sensor, the identification of the sensor, the converted type code of the sensor, and the detection result of the sensor.

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

[0129] For example, assuming that the sensor type in the record information associated with the event log is a temperature sensor and the sensor type code is XFWX, the sensor type code is converted according to the sensor type, and the converted sensor type code 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 staff viewing.

[0132] Since the converted event log includes the sensor's connection location information, sensor identification, converted sensor type code, and sensor detection results, after displaying the converted event log, staff can directly determine the operating status of the network device through the converted event log.

[0133] exist Figure 6In the illustrated embodiment, after receiving a query request, the server determines the recorded information associated with the event log in the first and second storage areas based on the sensor's connection location information and the sensor's identifier. The server then converts the event log based on the sensor type in the recorded information associated with the event log, and finally displays the converted event log to facilitate staff viewing the event log. In the above-described method, the server determines the recorded information associated with the event log in the first and second storage areas based on the sensor's connection location and the sensor's identifier. Because the sensor's identifier uniquely identifies the sensor currently connected to the server, the correct recorded information associated with the event log can be determined even if the sensor's connection location is reused, avoiding incorrect conversion of the sensor's event log. Furthermore, even if the sensor is disconnected from the server and the sensor's connection location is not reused, the server can still determine the recorded information associated with the event log, avoiding the issue of being unable to convert the event log due to the absence of the recorded 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 this application. It should be noted that the data management method of the sensor provided by this application is implemented based on the IPMI management system. Figure 7 The IPMI management system provided in the embodiment of the present application is further introduced.

[0135] Figure 7 This is a schematic diagram of an IPMI management system provided in this application embodiment. Figure 7 The IPMI management system includes an IPMI control module, an IPMI query module, a first storage area, and a second storage area. The IPMI control module may be, for example, an IPMI controller, including a sensor monitoring submodule and an identifier generation submodule; the IPMI query module may be, for example, an IPMI function module, including a conversion submodule and a display submodule.

[0136] In some embodiments, upon detecting that a sensor is connected to a server, the sensor monitoring submodule determines the time at which the sensor and server established the connection and sends an indication to the identifier generation submodule, including the time at which the sensor and server established the connection. Upon receiving the indication, the identifier generation submodule generates an identifier for the sensor and sends the identifier to the sensor monitoring submodule. The sensor monitoring submodule generates first recorded information for the sensor and stores the first recorded information in a first storage area.

[0137] Can be combined Figure 8 To understand, Figure 8For a flow chart of establishing a connection between a sensor and a server provided in an embodiment of the present application, see Figure 8 , the process may include the following:

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

[0139] S802: The IPMI monitoring submodule detects that a connection is established between the sensor and the server.

[0140] After the IPMI monitoring submodule detects that the sensor has established a connection with the server, it sends an indication message to the identifier generation submodule. The indication message includes the time when the sensor and server established the connection. The indication message instructs the identifier generation submodule to generate a sensor identifier based on the time when the sensor and server established the connection.

[0141] S803: The identification generation submodule generates an identification of the sensor.

[0142] After receiving the indication information, the identification generation submodule generates the sensor identification and sends the sensor identification to the IPMI monitoring submodule.

[0143] S804: The IPMI monitoring submodule determines the type of the sensor and the connection location information of the sensor.

[0144] S805: The IPMI monitoring submodule obtains a preset format of the recording information.

[0145] S806: The IPMI monitoring submodule generates first record information according to a preset format of the record information.

[0146] The first record information includes the sensor's identifier, connection location information, sensor type, 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 not the first status.

[0147] S807: The IPMI monitoring submodule writes the first recorded information of the sensor into the first storage area.

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

[0149] If yes, execute S809;

[0150] If not, execute S811.

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

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

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

[0154] S811: The IPMI monitoring submodule triggers an error first record information writing failure event.

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

[0156] Can be combined Figure 9 To understand, Figure 9 For a flow chart of a sensor disconnected from a server provided in an embodiment of the present application, see Figure 9 , the process may include the following:

[0157] S901: The sensor is disconnected from the server through the first interface location on the IPMI.

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

[0159] S903: The IPMI monitoring submodule queries, based on the type of the sensor, a list of sensors currently connected to the server to determine whether there is first record information of the sensor.

[0160] If yes, execute S904;

[0161] If not, execute S909.

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

[0163] S905: The IPMI monitoring submodule updates the state between the sensor and the server in the first record information from the first state to the second state, and obtains second record information of the sensor.

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

[0165] S907: The IPMI monitoring submodule stores the second recorded information of the sensor in the second storage area.

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

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

[0168] S909: The IPMI monitoring submodule triggers a warning that the sensor is an invalid sensor.

[0169] In some embodiments, upon receiving a query request, the conversion submodule in the IPMI query module determines, in a first storage area, recorded information associated with the event log based on the sensor connection location information and sensor identification in the event log. If no recorded information associated with the event log is stored in the first storage area, the conversion submodule determines the recorded information associated with the event log in a second storage area. The conversion submodule then converts the event log based on the sensor type in the recorded information associated with the event log and sends the converted event log to the display submodule. Upon receiving the converted event log, the display submodule displays the converted event log.

[0170] Can be combined Figure 10 To understand, Figure 10 For a flow chart of converting event logs provided in an embodiment of the present application, please refer to Figure 10 , the process may include the following:

[0171] S1001: The conversion submodule obtains an event log.

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

[0173] S1003: The conversion submodule determines whether third record information exists in the first storage area according to the connection position information of the sensor.

[0174] If yes, execute S1004;

[0175] If not, execute S1006.

[0176] S1004: The conversion submodule determines whether the third record information includes the sensor identifier.

[0177] If yes, execute S1005;

[0178] If not, execute S1006.

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

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

[0181] If yes, execute S1007;

[0182] If not, execute S1009.

[0183] S1007: The conversion submodule converts the event log according to the record information associated with the event log to obtain a converted event log.

[0184] S1008: The display submodule displays the converted event log.

[0185] S1009: The display submodule displays “Unknown sensor”.

[0186] In the case where no record information associated with the event log is found, 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] exist Figure 7 In the IPMI management system shown, after a sensor establishes a connection with a server, the identifier generation submodule generates an identifier for the sensor. The sensor monitoring submodule then generates first recorded information for the sensor and stores the first recorded information in a first storage area. After the sensor disconnects from the server, the sensor monitoring submodule updates the first recorded information for the sensor, obtains second recorded information for the sensor, and stores the second recorded information in a second storage area. Thus, upon receiving a query request, the conversion submodule determines the recorded information associated with the event log in the first and second storage areas based on the sensor's connection location information and the sensor identifier in the event log. The conversion submodule then converts the event log based on the recorded information associated with the event log to obtain a converted event log. The display submodule displays the converted event log.

[0188] Since the sensor's identifier indicates the sensor currently connected to the server, the sensor's event log and first record information are associated through the sensor's connection location information and the sensor's identifier. The sensor's event log is uniquely associated with the sensor's first record information, and in the event that the sensor's connection location is reused, it will not be associated with the record information of other sensors. In addition, when the sensor is disconnected from the server, the sensor's second record information is stored in the second storage area. In this way, even when the sensor is disconnected from the server, the record information associated with the sensor's event log still exists 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 embodiment of the present application improves the accuracy of managing sensor data.

[0189] On the basis of the above embodiment, the sensor data management method provided in the embodiment of the present application further includes: adjusting the network device operating parameters when the sensor detection data is abnormal. Figure 11 , further introducing the method of adjusting the operating parameters of the network device provided in the embodiment of the present application.

[0190] Figure 11 For a flow chart of adjusting the operating parameters of a target device provided in an embodiment of the present application, please refer to Figure 11 , the process may include the following steps:

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

[0192] For example, it is assumed that the sensor is a temperature sensor, the target device is a network device where the temperature sensor is located, and the detection data is the temperature sensor detecting the target device to obtain a temperature value of the target device during operation.

[0193] In some embodiments, after the sensor establishes a connection with 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 based on the type of sensor and the detection data.

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

[0196] For example, suppose the sensor is a temperature sensor, and the server receives detection data of 40 degrees Celsius. The preset threshold is 35 degrees Celsius. Therefore, the temperature sensor's detection data is abnormal. Suppose the sensor is a card sensor. A card sensor detects the presence of a card in the target device. If the card is present, the detection data is 0; if the card is absent, the detection data is 1. Therefore, the preset threshold for this card sensor is 1. If the server receives detection data of 0, the card sensor's detection data is normal.

[0197] In some embodiments, the cause of abnormal detection data can be determined based on the sensor type and detection data. Specifically, the following method can be used: obtaining detection information corresponding to at least one candidate sensor type; wherein, for each candidate sensor type in the at least one candidate sensor type, the detection information corresponding to the candidate sensor type includes at least one set of historical detection data for the candidate sensor and the cause of abnormal detection data corresponding to each set of historical detection data; determining target detection information from the historical detection information corresponding to the at least one candidate sensor type based on the sensor type; and determining the cause of abnormal detection data from the target detection information based on the detection data.

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

[0199] Therefore, when the server receives sensor detection data and determines that the sensor detection data is abnormal data, it can identify a candidate sensor type that is the same as the sensor type from at least one candidate sensor type. Furthermore, from at least one set of historical detection data corresponding to the candidate sensor type, it can identify a set of historical detection data corresponding to the sensor detection data. Finally, the abnormality cause corresponding to the set of historical detection data can be determined as the abnormality 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] According to the abnormal cause of the detection data, the method of adjusting the operating parameters of the target device can be as follows: determining the corresponding adjustment parameters according to the abnormal cause of the detection data; sending instructions to the target device, the instructions are used to instruct the target device to adjust the operating parameters of the target device according to the adjustment parameters.

[0202] In some embodiments, the operating parameters of the target device may be adjusted based on the cause of the abnormality in the detection data, so that the detection data of the sensor can return to normal while the target device is operating according to the adjusted parameters.

[0203] For example, assume that the fan speed of the target device is 5 rpm, the sensor is a temperature sensor, and the abnormality in the temperature sensor's detection data is due to the fan speed being too slow. In this case, the fan speed parameter of the target device can be adjusted while the target device is running, increasing the fan speed to 10 rpm.

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

[0205] For example, assuming that the current fan speed of the target device is 5 rpm and the adjustment parameter is to increase the fan speed to 10 rpm, after receiving the instruction, the target device increases the current fan speed from 5 rpm to 10 rpm.

[0206] exist Figure 11 In the illustrated embodiment, after a sensor establishes a connection with a server, the server receives the sensor's detection data. If the detection data is abnormal, the server determines the cause of the abnormality based on the sensor type and the detection data, and from the detection information corresponding to at least one candidate sensor type. Finally, the target device's operating parameters are adjusted based on the cause of the abnormality. In this implementation, by dynamically analyzing the cause of the abnormality in the sensor detection data and promptly adjusting the target device's operating parameters, the probability of target device failure is reduced and the reliability of the target device's operation is improved.

[0207] Figure 12 This is a schematic diagram of the structure of a sensor data management device provided in an embodiment of the present application. Figure 12 As shown, an embodiment of the present application further provides a sensor data management device 120, which includes a first generation module 121, a second generation module 122, a third generation module 123 and a processing module 124, wherein:

[0208] A first generating module 121 is configured to generate a sensor identifier when the sensor is connected to the server through the first interface location, where the sensor identifier is used to indicate the sensor currently connected to the server;

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

[0210] A third generating module 123 is configured to generate an event log of the sensor, wherein the event log includes an identification of the sensor and information about the connection location of the sensor;

[0211] The processing module 124 is configured to perform association processing on the first record information and the event log.

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

[0213] Figure 13 This is a schematic diagram of the structure of the electronic device provided in this application. Figure 13 As shown, the electronic device 130 provided in this embodiment includes: at least one processor 131 and a memory 132. Optionally, the electronic device 130 also includes a communication component 133. The processor 131, the memory 132 and the communication component 133 are connected via a bus.

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

[0215] The specific implementation process of the processor 131 can be found in the above method embodiment. Its implementation principle and technical effects are similar and will not be repeated here in this embodiment.

[0216] In the above embodiments, it should be understood that the processor may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the application may be directly executed by a hardware processor or by a combination of hardware and software modules within the processor.

[0217] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage.

[0218] A bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. Buses can be categorized as address buses, data buses, and control buses. For ease of illustration, the buses in the drawings of this application are not limited to just one bus or just one type of bus.

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

[0220] In an exemplary embodiment, the 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), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0221] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps of any of the above-mentioned sensor data management method embodiments are implemented.

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

[0223] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0224] The above is a detailed introduction to the data management method, electronic device and storage medium of a sensor provided by the present application. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method and core ideas of the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the claims of the present application.

Claims

1. A sensor data management method, characterized in that: The method comprises: When a sensor is connected to a server through a first interface location, generating an identifier of the sensor, wherein the identifier of the sensor is used to indicate the sensor currently connected to the server; generating first record information of the sensor according to the identifier of the sensor and the position of the first interface; wherein the first record information includes the identifier of the sensor and connection position information of the sensor, and the connection position information is used to indicate the position of the first interface; generating an event log of the sensor, wherein the event log includes an identifier of the sensor and connection location information of the sensor; performing association processing on the first record information and the event log; When the sensor is disconnected from the server, updating a first state between the sensor and the server to obtain a second state between the sensor and the server; the first state is a connection established state, and the second state is a disconnected state; updating the first record information according to the second state to obtain second record information; The second record information is stored 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 the sensor that is currently disconnected from the server.

2. The method according to claim 1, characterized in that Generating the identification of the sensor includes: determining a time when the sensor establishes a connection with the server through the first interface location; An identifier of the sensor is generated 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 Generating first record information of the sensor according to the identifier of the sensor and the first interface position includes: determining a type of the sensor and a first status between the sensor and the server; The sensor identifier, the first interface location, the sensor type, and the status between the sensor and the server are processed according to a preset format of the record information to generate the first record information; the first record information includes the sensor type, the status between the sensor and the server, the sensor identifier, 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. The first storage area is a storage area for storing real-time record information. The real-time record information is record information of a sensor currently connected to the server.

5. The method according to claim 4, characterized in that The method further comprises: receiving a query request, wherein the query request is used to request querying an event log of the sensor; determining, according to the connection location information of the sensor and the identifier of the sensor in the event log, record information associated with the event log; Converting the event log according to the record information associated with the event log to obtain a converted event log; Displays the converted event log.

6. The method according to claim 5, characterized in that The determining, based on the connection location information of the sensor and the identifier of the sensor in the event log, record information associated with the event log includes: determining, according to the connection location information of the sensor, whether third record information is stored in the first storage area, the third record information including the connection location information of the sensor; In a case where the third record information is stored in the first storage area, determining whether the third record information includes the identifier of the sensor; In a case where the third record information includes the identifier of the sensor, determining the third record information as record information associated with the event log; When the third record information is not stored in the first storage area, or the third record information does not include the identification of the sensor, the record information associated with the event log is determined in the second storage area based on the connection location information of the sensor and the identification of the sensor.

7. The method according to claim 6, characterized in that The determining, in the second storage area according to the connection location information of the sensor and the identifier of the sensor, record information associated with the event log includes: determining, in the second storage area, according to the connection location information of the sensor, at least one fourth record information including the connection location information of the sensor; The record information including the identifier of the sensor in the at least one fourth record information is determined as the record information associated with the event log.

8. The method according to claim 5, characterized in that The determining, based on the connection location information of the sensor and the identifier of the sensor in the event log, record information associated with the event log includes: searching for at least one fifth record information in the first storage area and the second storage area, wherein the at least one fifth record information includes the connection location information of the sensor; The record information including the identification of the sensor in the at least one fifth record information is determined as the record information associated with the event log.

9. The method according to claim 5, characterized in that The event log also includes the type code of the sensor and the detection result of the sensor; the event log is converted according to the record information associated with the event log to obtain a converted event log, including: converting the sensor type code according to the sensor type in the record information associated with the event log to obtain a converted sensor type code; The converted event log includes: the connection location information of the sensor, the identification of the sensor, 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 comprises: receiving detection data sent by the sensor, wherein the detection data is data obtained by the sensor detecting a target device; the target device is the device where the sensor is located; In the case where the detection data is abnormal, determining the cause of the abnormality of the detection data based on 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, based on the type of the sensor and the detection data, a cause of abnormality in the detection data includes: Acquiring detection information corresponding to a type of at least one candidate sensor; wherein, for each candidate sensor type of the at least one candidate sensor type, the detection information corresponding to the candidate sensor type includes at least one set of historical detection data of the candidate sensor and an abnormality cause corresponding to each set of historical detection data; determining target detection information from historical detection information corresponding to the type of the at least one candidate sensor according to the type of the sensor; Based on the detection data, a cause of abnormality of the detection data is determined in the target detection information.

12. The method according to claim 10, characterized in that The adjusting the operating state of the target device according to the cause of the abnormality of the detected data includes: Determining corresponding adjustment parameters according to the abnormal cause of the detection data; An instruction is sent to the target device, where the instruction is used to instruct the target device to adjust an operating parameter of the target device according to the adjustment parameter.

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

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

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

Images