A log management method, device, system and storage medium

Abstract

The application provides a log management method, device, system and storage medium. The method comprises the following steps: obtaining original log data of a terminal in a data source, performing data cleaning on the original log data to obtain log data of the terminal, processing the log data by using a preset point rule table to obtain current binding information of the terminal, and generating log information of the terminal according to the log data and the current binding information. The method improves the efficiency and flexibility of log management.

Description

Technical Field

[0001] This application relates to log processing technology, and more particularly to a log management method, apparatus, system and storage medium. Background Technology

[0002] With the development of IoT technology and the widespread adoption of smart devices and terminals, establishing a connection between smart devices and terminal devices allows for more convenient control, such as remote control via a terminal. To ensure a stable connection between the terminal and the smart device and to provide timely information on the device's usage, processing the log data of the interaction between the terminal and the smart device becomes crucial.

[0003] In existing technologies, Java technology is typically used to process terminal and smart device logs and binding information. Elasticsearch (ES) is used as the data storage location and an internal timer is used to achieve batch processing of log data. All points related to this information are set in the program.

[0004] However, existing technologies using Java struggle to achieve millisecond time intervals, making it impossible to process log data in real time. Furthermore, storing log data in Elasticsearch, retrieving it, and then processing it again results in low efficiency. The location information is fixed in the program and cannot be adjusted at any time, leading to a lack of flexibility. Summary of the Invention

[0005] This application provides a log management method, apparatus, system, and storage medium to solve the problems of low efficiency and poor flexibility in log data processing.

[0006] Firstly, this application provides a log management method, including:

[0007] Retrieve raw log data from the terminal in the data source;

[0008] The raw log data is cleaned to obtain the terminal's log data;

[0009] The log data is processed using a preset location rule table to obtain the current binding information of the terminal;

[0010] Log information for the terminal is generated based on the log data and the current binding information.

[0011] Secondly, this application provides a log management device, comprising:

[0012] Acquisition module: Used to acquire raw log data from the terminal in the data source;

[0013] Cleaning module: Used to clean the raw log data to obtain the terminal's log data;

[0014] Processing module: Used to process the log data using a preset point rule table to obtain the current binding information of the terminal;

[0015] Generation module: Generates the terminal's log information based on the log data and the current binding information.

[0016] Thirdly, this application provides a log management system, including: a log management device, equipment, and terminal;

[0017] The log management device is used to process log information generated during the device-terminal binding process, and to manage the logs according to the log management methods in the first aspect and various possible designs of the first aspect.

[0018] Fourthly, this application provides an electronic device, comprising:

[0019] A processor, and a memory communicatively connected to the processor;

[0020] The memory stores computer-executed instructions;

[0021] The processor executes computer execution instructions stored in the memory to implement the log management method as described in the first aspect and various possible designs of the first aspect.

[0022] Fifthly, this application provides a computer-readable storage medium, including computer-executable instructions stored therein, which, when executed by a processor, are used to implement the log management method as described in the first aspect and various possible designs of the first aspect.

[0023] Sixthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the log management method as described in the first aspect and various possible designs of the first aspect.

[0024] This application provides a log management method, apparatus, system, and storage medium. The method includes: acquiring raw log data from a terminal in a data source; cleaning the raw log data to obtain the terminal's log data; processing the log data using a preset point rule table to obtain the terminal's current binding information; and generating the terminal's log information based on the log data and the current binding information. This method improves both the efficiency and flexibility of log management. Attached Figure Description

[0025] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0026] Figure 1 This is a schematic diagram of a network architecture on which this application is based;

[0027] Figure 2 This is a flowchart illustrating a signal fault monitoring method provided in this application;

[0028] Figure 3 This is a schematic diagram of the structure of a signal fault monitoring device provided in this application;

[0029] Figure 4 This is a schematic diagram of a signal fault monitoring system provided in this application;

[0030] Figure 5 This is a schematic diagram of the hardware structure of the electronic device provided in this application.

[0031] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0032] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0033] With the development of IoT and computer technologies, the connection between smart devices and terminals is becoming increasingly close. By binding smart devices to terminals, it is possible to control the smart devices and understand their usage. In the era of big data, the log data generated between these two devices based on near-field communication has certain research value, which makes the study of log data and binding information between smart devices and terminals a current research hotspot.

[0034] In existing technologies, Java technology is typically used to process log data and binding information generated between smart devices and terminals. This involves pre-setting a timer function in the program to process log data and binding information within a certain time interval. The processed data comes from a database specifically designed for collecting log data and binding information between smart devices and terminals using embedded tracking technology. The acquired data is then transferred to Elasticsearch (ES), where it is extracted in batches, cleaned, and matched with location information to determine the binding stage of the log data and binding information. The processed data is then cached and finally stored in MySQL for subsequent visualization on the terminal interface or for processing in other subsequent processes.

[0035] Clearly, existing technologies using Java are limited by their inherent limitations, making it difficult to set preset alarm intervals in milliseconds. Therefore, real-time processing of log data and binding information is not feasible. Transferring small amounts of data to Elasticsearch (ES) wastes significant storage resources and reduces processing efficiency. The location information used to determine log data and binding information is written in a fixed program. Subsequent changes to the location information—either due to changes in the tracking points or user binding methods—can alter the business process for processing log data. These changes, in turn, affect the location information associated with the process. Currently, modifying location information only requires changes to the program, making the processing of log data and binding information neither flexible nor efficient.

[0036] To address these technical challenges, this application utilizes a method provided by the Flink framework to achieve real-time processing and monitoring of log data. Specifically, real-time log data is retrieved from a database with data collection via event tracking and then connected to Kafka. Data is processed one log entry at a time. After preprocessing, the processed data is compared and matched with an imported location information table to determine the binding stage, type, and process of each log entry. The cached log database is then updated based on the processed log data, and the updated log data is matched with a invoked device dimension table to identify the corresponding device. Finally, the complete log data and its binding information are output to MySQL for subsequent processing.

[0037] Specifically, this application provides a log management method. The method includes: acquiring raw log data from a terminal in a data source; cleaning the raw log data to obtain the terminal's log data; processing the log data using a preset point rule table to obtain the terminal's current binding information; and generating the terminal's log information based on the log data and the current binding information. This method improves both the efficiency and flexibility of log management.

[0038] The technical solutions of the embodiments of this application and how the technical solutions of this application solve the above-mentioned technical problems are described in detail below with specific examples. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0039] refer to Figure 1 , Figure 1 This is a schematic diagram of a network architecture on which this application is based, such as... Figure 1 As shown, the network architecture includes server 1, smart device 2, and terminal 3.

[0040] Specifically, server 1 is a server cluster capable of processing massive amounts of data. It may integrate or install the log management device provided in this application. This log management device can process the log data of the bound communication between terminal 3 and smart device 2 based on the signal log management method provided in this application. Furthermore, server 1 can call a database with embedded tracking technology specifically designed for collecting bound log data information, in order to process the log data of smart device 2 in real time.

[0041] The smart device 2 can be a smart TV, smart speaker, etc., which can upload its own log data and its operating status information to a database with data tracking technology specifically used to collect and bind log data information in real time or periodically.

[0042] Terminal 3 can be a user's mobile phone, desktop computer, tablet computer, or other hardware device, which establishes a connection with smart device 2 based on near-field communication.

[0043] Example 1

[0044] Figure 2 This is a flowchart illustrating a log management method provided in this application, such as... Figure 2 As shown, the method includes:

[0045] Step 201: Obtain the raw log data of the terminal in the data source;

[0046] Step 202: Clean the raw log data to obtain the terminal's log data;

[0047] Step 203: Process the log data using a preset point rule table to obtain the current binding information of the terminal;

[0048] Step 204: Generate the terminal's log information based on the log data and the current binding information.

[0049] Specifically, the log management method provided in this application is implemented by the aforementioned log management device, which, as mentioned above, can be installed or carried in the aforementioned server 1.

[0050] Before executing step 201, it should be noted that the data in this application comes from other databases. That is to say, the data in this application is collected from a database based on the defined tracking points. When a user binds a device to a smart device or engages in other interactions, the smart device will report its own log data and its operating status information. If the database detects that the user's operation event matches the content of the tracking points, the log data information generated by the interaction between the collection terminal and the smart device will be uploaded to the database for the log management device in the server to call and process the log data information.

[0051] Specifically, in step 201, the log management device obtains the original log data of the terminal from the data source. That is, the log management device calls the log data from the data source. The data source is the log data of the interaction between the terminal and the smart device collected according to the tracking technology. The tracking technology refers to the related technologies and implementation processes for capturing, processing and sending specific user behaviors or events. It is used to monitor events during the operation of the software application and to judge and capture relevant data information when the events that need to be paid attention to occur.

[0052] After obtaining the raw log data from the terminal in the data source, the raw data will be cleaned so that subsequent processing can obtain regular and effective log data. In step 202, the log management device connects the raw log data from the terminal obtained from the data source to Kafka so as to realize real-time processing of the log data. Then, the raw log data is cleaned here to obtain the log data that needs to be processed later.

[0053] Specifically, the log management device first filters out data that is not in a preset format, retaining the original data that conforms to the preset data format as intermediate log data. Then, it filters out data with empty content in the intermediate log data, thus completing the processing of the original data for the subsequent execution of step 203. The preset format conforms to the data format of the Flink framework, such as the JOIN format.

[0054] Specifically, in step 203, after obtaining the cleaned log data, the log management device sorts it by time, then obtains the location information of the sorted log data, compares and matches the location information with the location information rule table in the server, and then determines the stage and binding process of each log, thereby obtaining the current binding information of the terminal.

[0055] The aforementioned point information includes: access request, call interface, system used, device model, binding type, etc., which are used to record key point information of the binding and interaction process between the device and smart home appliances; the information in the point information rule table above includes: stage, system, interface, type, step, etc.

[0056] Furthermore, by comparing the location information in the log data with the location rule table, the binding type of the log data is first determined. Then, the binding type of the log data is determined by matching the field information of the called interface. The binding type may include LAN binding, Bluetooth binding, QR code binding, etc.

[0057] Then, the binding stage of the log data information is determined. The binding process can be divided into the selection stage, that is, what method the terminal should choose to bind with the smart home appliance; the network preparation stage, that is, after the terminal selects the binding method, the smart device responds to the user matching and makes corresponding preparations; the network configuration stage, that is, the process of establishing communication between the terminal and the smart device; and the binding stage, that is, the process of the terminal and the smart home appliance having completed the establishment of communication.

[0058] Next, the log management device updates the cached log data with the processed log data information, and then calls a preset device dimension table to obtain the device information to generate the log information. Optionally, the preset device dimension table is used to determine the terminal device data and associate it with the processed log data to obtain the log information. The device dimension table can provide a remote dictionary service, acting as a remote storage system. The preset device dimension table includes device type, model, and basic device manufacturing information.

[0059] The aforementioned update of cached log data refers to comparing the processed log data with the data in the original cached logs, and then replacing the information in the original cache with the latest log data information according to the device model.

[0060] In step 304, after obtaining the current binding information of the terminal, the log management device associates and integrates it according to the device model to generate the terminal's log information, which includes: device type, device model, stage, system, interface, type and step, etc.

[0061] Based on the above implementation method, after generating the terminal log information, it is also necessary to update the log data and binding information of the smart device. Optionally, this can be implemented according to the following implementation method.

[0062] Specifically, the log management data first obtains the intelligent update log data, matches and compares this information with the preset point rule table in the server, and determines the binding information after the binding interaction between the smart device and the terminal by following the steps in the above embodiment.

[0063] Furthermore, the updated binding information of the smart device and the updated log information will be obtained, and they will be associated and integrated according to the device model field value. Finally, the log information of the smart device will be updated.

[0064] The updated terminal and smart device binding information and log data are finally entered into the MySQL database for subsequent processing operations, such as using UI technology to display the binding information to users of the terminal in a visual form, or using this data to analyze the usage of the device.

[0065] This application provides a log management method. The method includes: acquiring raw log data from a terminal in a data source; cleaning the raw log data to obtain the terminal's log data; processing the log data using a preset point rule table to obtain the terminal's current binding information; and generating the terminal's log information based on the log data and the current binding information. This method improves both the efficiency and flexibility of log management.

[0066] Example 2

[0067] Corresponding to the signal fault monitoring method of this application, Figure 3 This is a schematic diagram of a log management device provided in this application. For ease of explanation, only the parts relevant to this application are shown.

[0068] Reference Figure 3 The log management device includes:

[0069] Acquisition Module 10: Used to acquire raw log data from the terminal in the data source;

[0070] Cleaning module 20: Used to clean the raw log data to obtain the terminal's log data;

[0071] Processing module 30: Used to process the log data using a preset point rule table to obtain the current binding information of the terminal;

[0072] Generation module 40: Generates the log information of the terminal based on the log data and the current binding information.

[0073] Optionally, the log management device further includes: an update module;

[0074] The update module is specifically used for:

[0075] Obtain update log data from smart devices;

[0076] The update log data is processed using the preset location rule table to obtain the updated binding information of the smart device;

[0077] The updated binding information and update log data are used to update the log information of the smart device.

[0078] Optionally, the log management device further includes:

[0079] Based on the terminal's log data, determine the terminal's device data in a preset device dimension table;

[0080] Accordingly, generating the log information of the log device based on the log data and the current binding information includes:

[0081] The log information is generated based on the log data, device data, and current binding information.

[0082] Optionally, the terminal's log information is stored in a MySQL database.

[0083] Cleaning module 20 is specifically used for:

[0084] The data format of the raw log data is filtered, and raw log data that conforms to the preset data format is retained as intermediate log data;

[0085] The data content in the intermediate log data is filtered to obtain the log data of the terminal.

[0086] The implementation principle of the log management device provided in this application is similar to that in any of the above embodiments, and will not be described in detail here.

[0087] This application provides a log management device. The method includes: acquiring raw log data from a terminal in a data source; cleaning the raw log data to obtain the terminal's log data; processing the log data using a preset point rule table to obtain the terminal's current binding information; and generating the terminal's log information based on the log data and the current binding information. This method improves both the efficiency and flexibility of log management.

[0088] Example 3

[0089] Corresponding to the log management method provided in this application, Figure 4 This is a schematic diagram of a log management system provided in this application. For ease of explanation, only the parts relevant to this application are shown.

[0090] Reference Figure 4 The signal fault monitoring and management system includes: log management device 101, intelligent device 2 and terminal 3.

[0091] The log management device is used to process log information generated during the device-terminal binding process, and to manage logs according to the log management method described in any one of the embodiments of the first embodiment.

[0092] Example 4

[0093] The electronic device provided in this application can be used to execute the technical solutions of the above-described method embodiments. Figure 5 This is a schematic diagram of the hardware structure of the electronic device provided in this application. For ease of explanation, only the parts relevant to this application are shown.

[0094] refer to Figure 5 The diagram illustrates a structural schematic suitable for implementing an electronic device 1000 according to an embodiment of this application. The electronic device 1000 can be a terminal device. The terminal device can include, but is not limited to, mobile terminals such as mobile phones, laptops, digital radio receivers, personal digital assistants (PDAs), portable Android devices (PADs), portable media players (PMPs), and in-vehicle devices (e.g., in-vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. Figure 5 The electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0095] like Figure 5As shown, the electronic device 1000 may include a management device (e.g., a central processing unit, a graphics processing unit, etc.) 1001, which can perform various appropriate actions and processes according to programs stored in read-only memory (ROM) 1002 or programs loaded from storage device 1009 into random access memory (RAM) 1003. The RAM 1003 also stores various programs and data required for the operation of the electronic device 1000. The management device 1001, ROM 1002, and RAM 1003 are interconnected via a bus 1004. An input / output (I / O) interface 1006 is also connected to the bus 1004.

[0096] Typically, the following devices can be connected to the I / O interface 1006: input devices 1006 including, for example, a touchscreen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 1007 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 1009 including, for example, magnetic tape, hard disk, etc.; and communication devices 10010. Communication device 10010 allows electronic device 1000 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 5 An electronic device 1000 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0097] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication device 10010, or installed from storage device 1009, or installed from ROM 1002. When the computer program is executed by management device 1001, it performs the functions defined in the methods of embodiments of this application.

[0098] It should be noted that the computer-readable medium described above in this application may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof.

[0099] In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination thereof.

[0100] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0101] The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the methods shown in the above embodiments.

[0102] This application provides a computer program product that can be written in one or more programming languages ​​or a combination thereof to perform the operations of this disclosure. These programming languages ​​include object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on a user's computer, partially on a user's computer, as a standalone software package, partially on a user's computer and partially on a remote computer, or entirely on a remote computer or media library. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0103] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0104] The units described in the embodiments of this application can be implemented in software or in hardware. The name of a unit does not necessarily limit the unit itself; for example, the first acquisition unit can also be described as "a unit that acquires at least two Internet Protocol addresses".

[0105] The functions described above in this document can be performed at least in part by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), and so on.

[0106] In the context of this application, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0107] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0108] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A log management method, comprising: Obtain the raw log data generated during the binding process between the terminal and the smart device in the data source; The raw log data is cleaned to obtain the terminal's log data; The cleaned log data is sorted by time to obtain the location information of the sorted log data; The point information in the sorted log data is compared and matched with a preset point rule table to determine the stage and binding process of each log entry, thereby obtaining the current binding information of the terminal. The current binding information includes the binding type and binding stage. The point information is used to record key point information of the binding interaction process between the terminal and the smart device. The information in the point information rule table includes: stage, system, interface, type, and step. Based on the terminal's log data, determine the terminal's device data in a preset device dimension table; Log information for the terminal is generated based on the log data, device data, and current binding information.

2. The log management method according to claim 1, characterized by, Also includes: Obtain update log data from smart devices; The update log data is processed using the preset location rule table to obtain the updated binding information of the smart device; The updated binding information and update log data are used to update the log information of the smart device.

3. The log management method according to claim 1, characterized by, include: The terminal's log information is stored in a MySQL database.

4. The log management method according to claim 1, characterized by, Data cleaning of raw log data includes: The data format of the raw log data is filtered, and raw log data that conforms to the preset data format is retained as intermediate log data; The data content in the intermediate log data is filtered to obtain the log data of the terminal.

5. A log management device, comprising: Acquisition module: Used to acquire raw log data generated by the terminal and smart device during the binding process in the data source; Cleaning module: Used to clean the raw log data to obtain the terminal's log data; The cleaned log data is sorted by time to obtain the location information of the sorted log data; Processing module: used to process the location information in the log data using a preset location rule table to obtain the current binding information of the terminal; wherein, the current binding information includes binding type and binding stage; The processing module is specifically used to compare and match the point information in the sorted log data with a preset point rule table, determine the stage and binding process of each log, and obtain the current binding information of the terminal; wherein, the point information is used to record the key point information of the binding interaction process between the terminal and the smart device; the information in the point information rule table includes: stage, system, interface, type, and step; Based on the terminal's log data, determine the terminal's device data in a preset device dimension table; Generation module: used to generate the terminal's log information based on the log data, device data, and current binding information.

6. A log management system, comprising: Log management devices, smart devices and terminals; The log management device is used to process log information generated during the device-terminal binding process, and to manage the logs according to any one of claims 1-4.

7. An electronic device comprising: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-4.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-4.

9. A computer program product comprising a computer program that, when executed by a processor, implements the method of any one of claims 1-4.

Images