Household electrical appliance internet of things communication module log offline grabbing method and system

Abstract

The application provides a household appliance Internet of Things communication module log offline grabbing method and system, and belongs to the technical field of household appliance maintenance. The method pre-enters the same unique identity mark, phase-specific exclusive suffix character and preset hash algorithm of the household appliance Internet of Things communication module into a mobile terminal. The household appliance Internet of Things communication module and the mobile terminal can respectively generate exclusive hotspot names of corresponding stages according to the exclusive suffix characters of the corresponding stages, in combination with the unique identity mark and the preset hash algorithm, and complete device wake-up, identity verification and hotspot connection in turn, to establish a hotspot connection. The household appliance Internet of Things communication module transmits log data to the mobile terminal to complete log grabbing after the establishment of the hotspot connection. The exclusive hotspot names generated independently in each stage replace the traditional fixed hotspot, can reduce the interference of surrounding wireless signals, avoid misconnection in a multi-device scene, and effectively prevent the risk of illegal theft of logs due to the difficulty of the exclusive hotspot names generated by the hash algorithm in being counterfeited by malicious devices.

Description

Technical Field

[0001] This application relates to the field of home appliance maintenance technology, and in particular to a method and system for offline capture of logs from home appliance Internet of Things (IoT) communication modules. Background Technology

[0002] With the rapid development of the smart home industry, various smart home appliances are generally equipped with IoT communication modules to achieve network control. The module operation log is a key basis for troubleshooting faults such as home appliances losing network connection or malfunctioning. After-sales maintenance often requires offline capture of module logs to complete fault location.

[0003] Existing module log capture mainly relies on disassembling the device and connecting it to the router or remotely reading logs by connecting the device to the local area network. Disassembling the device requires disassembling the device and disconnecting the power supply, which can easily cause failure at the fault site and make it impossible to reproduce occasional faults. Local area network capture depends on the home appliance being connected to the router normally. In the scenario where the home appliance is offline and disconnected from the network, it is impossible to form a network for communication.

[0004] Traditional methods for capturing temporary wireless access points (APs) often use unencrypted hotspots with fixed names for network configuration. These hotspots are easily interfered with by surrounding wireless signals, and misconnections can occur in multi-device scenarios. Furthermore, there is a risk of malicious devices spoofing hotspots with the same name to illegally steal logs. Therefore, it is difficult to securely and accurately capture module logs in offline scenarios without disassembling the device or relying on a local area network. Summary of the Invention

[0005] To address at least one of the aforementioned issues, this application provides an offline log capture method and system for home appliance IoT communication modules. The system aims to use a unified configuration of unique identifiers, phased exclusive suffix characters, and preset hash algorithms for both modules and mobile terminals. Both ends can dynamically generate the same exclusive hotspot name in stages and sequentially complete device wake-up, identity verification, and hotspot connection. This allows for secure and accurate capture of module logs offline without networking or disassembly, avoiding wireless interference and preventing hotspot spoofing.

[0006] According to a first aspect of the embodiments of this application, an offline log capture method for a home appliance IoT communication module is provided, wherein the home appliance IoT communication module pre-stores a unique identifier, a stage-specific exclusive suffix character, and a preset hash algorithm, and the method includes:

[0007] The mobile terminal is pre-loaded with the same unique identifier, the phased exclusive suffix characters, and the preset hash algorithm as the home appliance IoT communication module; During the wake-up phase, verification phase, and transmission phase, the home appliance IoT communication module and the mobile terminal generate a unique hotspot name for the corresponding phase based on the unique suffix characters of the corresponding phase, combined with the unique identifier and the preset hash algorithm, so as to complete the device wake-up, identity verification, and hotspot connection in sequence. After establishing a hotspot connection, the home appliance IoT communication module transmits log data to the mobile terminal to complete log capture.

[0008] The above technical solution has the following advantages or beneficial effects: In this embodiment, by pre-entering the mobile terminal with the same unique identifier, phased exclusive suffix characters, and preset hash algorithm as the home appliance IoT communication module, the mobile terminal and the communication module have completely consistent computing benchmarks and matching criteria, providing a prerequisite for subsequent accurate pairing and secure interaction. Based on the unified computing criteria, the home appliance IoT communication module and the mobile terminal can generate exclusive hotspot names for each stage in the wake-up, verification, and transmission stages by combining the corresponding stage-specific suffix characters, unique identifiers, and preset hash algorithms. This abandons the traditional fixed hotspot mode, effectively avoiding interference from surrounding wireless signals and eliminating the security risks of malicious devices forging fixed hotspots to steal logs. At the same time, the phased independent hotspot design can realize layered identity verification, effectively avoiding false wake-up and false connection problems in multi-device scenarios. After completing device wake-up, identity verification, and hotspot connection in sequence, the home appliance IoT communication module can transmit log data to the mobile terminal to complete log capture. It can complete log collection without disassembling the device or relying on local area network. It can complete log collection even when the device is offline, effectively avoiding the problems of failure on-site due to disassembly and power failure, and the inability to reproduce occasional faults. It greatly improves the accuracy, security, and ease of operation and maintenance of offline log capture of home appliance modules.

[0009] In one embodiment of this application, a unique hotspot name for the corresponding stage is generated based on the unique suffix character of the corresponding stage, combined with the unique identifier and the preset hash algorithm, including: The unique identifier is concatenated with the exclusive suffix character for the corresponding stage to obtain the original string; The original string is hashed using the preset hash algorithm to obtain a hash digest; Extract characters of a preset length from the hash digest to generate a unique hotspot name for the corresponding stage.

[0010] The above technical solution has the following advantages or beneficial effects: In this embodiment, the unique identifier is first concatenated with the exclusive suffix character of the corresponding stage to obtain the original string, which can associate the device identity with the interaction stage and distinguish the exclusive hotspots of different stages. Then, a preset hash algorithm is used to perform a hash operation on the original string to obtain a hash digest, which can hide the original identifier information and avoid the plaintext leakage of the device identity. Finally, characters of a preset length are extracted from the hash digest to generate the exclusive hotspot name of the corresponding stage. This not only adapts to the character length limit of the hotspot name, but also relies on the randomness of the hash digest to improve the uniqueness of the hotspot, greatly reducing the probability of hotspots being impersonated and irrelevant signals being mismatched, and further enhancing the security and stability of the phased hotspot interaction.

[0011] In one embodiment of this application, during the wake-up phase, verification phase, and transmission phase, the home appliance IoT communication module and the mobile terminal respectively generate a dedicated hotspot for the corresponding phase based on the unique suffix characters of the corresponding phase, combined with the unique identifier and the preset hash algorithm, to sequentially complete device wake-up, identity verification, and hotspot connection, including: During the wake-up phase, the mobile terminal generates a wake-up hotspot name and activates the corresponding wake-up hotspot based on the unique suffix character of the wake-up phase, combined with the unique identifier and the preset hash algorithm. The home appliance IoT communication module generates a wake-up hotspot name based on the unique suffix character of the wake-up phase, combined with the unique identifier and the preset hash algorithm, and uses the generated wake-up hotspot name as a matching benchmark for scanning to complete the wake-up process. During the verification phase, the mobile terminal generates a verification hotspot name and activates the corresponding verification hotspot based on the unique suffix character of the verification phase, combined with the unique identity identifier and the preset hash algorithm. The home appliance IoT communication module generates a verification hotspot name based on the unique suffix character of the verification phase, combined with the unique identity identifier and the preset hash algorithm, and uses the generated verification hotspot name as a matching benchmark for scanning to complete the identity verification. During the transmission phase, one of the mobile terminal or the home appliance IoT communication module generates a transmission hotspot name and activates the corresponding transmission hotspot based on the unique suffix character of the transmission phase, combined with the unique identifier and the preset hash algorithm. The other party scans using the generated transmission hotspot name as a matching benchmark to establish a hotspot connection.

[0012] The above technical solution has the following advantages or beneficial effects: In this embodiment, during the wake-up phase, the mobile terminal and the home appliance IoT communication module simultaneously generate a wake-up hotspot name by combining a wake-up-phase-specific suffix character, a unique identifier, and a preset hash algorithm. The module scans and matches based on its own generated wake-up hotspot name; only a successful match wakes up the device. This dedicated hash hotspot matching achieves accurate device wake-up, effectively preventing stray signals from triggering false wake-ups. During the verification phase, both ends switch to a verification-phase-specific suffix character and independently generate a verification hotspot name. A secondary identity scan and verification is completed using this new dedicated hotspot. Through a phase-isolated independent authentication mechanism, identity bypass issues caused by impersonation of a single hotspot are prevented, greatly improving the security and reliability of device identity verification. During the transmission phase, either end generates a transmission hotspot name and activates the hotspot; the other end matches and scans to establish a connection, flexibly adapting to data transmission scenario requirements. Through a three-stage, completely independent, and segmented hotspot system, the traditional interaction method of fixed hotspots throughout the entire process can be completely abandoned. This enables layered isolation and step-by-step verification of the wake-up, verification, and chain establishment processes, effectively avoiding cross-device mismatch, wireless signal interference, and malicious hotspot impersonation and data theft issues in multi-device coexistence scenarios, and ensuring the safe, orderly, and accurate execution of the entire offline log capture process.

[0013] In one embodiment of this application, during the wake-up phase, the home appliance IoT communication module initiates hotspot scanning after powering on or entering maintenance mode, and performs scanning using a first scanning cycle and the wake-up hotspot name generated by itself as a matching benchmark.

[0014] The above technical solution has the following advantages or beneficial effects: In this embodiment, during the wake-up phase, the home appliance IoT communication module only initiates hotspot scanning after power-on or entering maintenance mode. This avoids the module continuously performing RF scanning under normal conditions, thereby reducing standby power consumption. The module uses a first scanning cycle and performs scanning based on its own generated wake-up hotspot name, identifying and comparing only the target hotspot. This reduces the detection and computation of a large number of irrelevant wireless signals in the surrounding area. While ensuring normal wake-up by the terminal, it further reduces the RF operating time, thereby reducing operating power consumption and avoiding false scanning caused by other WiFi signals, improving the effectiveness of wake-up matching.

[0015] In one embodiment of this application, during the wake-up phase, when the home appliance IoT communication module scans the wake-up hotspot and the received signal strength of the wake-up hotspot is greater than or equal to a preset signal threshold, the wake-up is determined to be successful.

[0016] The above technical solution has the following advantages or beneficial effects: In this embodiment, during the scanning process, the home appliance IoT communication module only determines successful wake-up when it simultaneously identifies a wake-up hotspot and the received signal strength of that wake-up hotspot is greater than or equal to a preset signal threshold. By first matching the hotspot name and then constraining the communication distance using signal strength, it can intercept spoofed hotspots and environmental wireless interference signals at long distances, effectively preventing false wake-ups, improving the rigor of wake-up judgment, and reducing unnecessary program startup and radio frequency power consumption.

[0017] In one embodiment of this application, during the wake-up phase, when the home appliance IoT communication module fails to identify the wake-up hotspot after a preset number of consecutive scans, the home appliance IoT communication module enters a sleep state for a preset sleep duration, and resumes hotspot scanning at the first scan cycle after the sleep period ends.

[0018] The above technical solution has the following advantages or beneficial effects: In this embodiment, when the home appliance IoT communication module fails to identify the wake-up hotspot after a preset number of consecutive scans, the module enters a sleep state for a preset sleep duration. After the sleep period ends, it resumes scanning for hotspots according to the first scan cycle. This avoids the module continuously scanning for hotspots for extended periods, reducing power consumption caused by continuous operation of the RF circuit and preventing power waste due to invalid scans. Simultaneously, the automatic resumption of scanning after sleep reduces power consumption during unattended operation and allows the module to promptly re-enter the scanning state after a mobile terminal activates a hotspot, balancing low-power operation with the availability of the wake-up function.

[0019] In one embodiment of this application, during the verification phase, the home appliance IoT communication module uses a second scanning cycle and performs a scan using the verification hotspot name it generates as a matching benchmark. The second scanning cycle is shorter than the first scanning cycle.

[0020] The above technical solution has the following advantages or beneficial effects: In this embodiment, during the verification phase, the home appliance IoT communication module uses a second scanning cycle shorter than the first scanning cycle and performs scanning based on the verification hotspot name it generates itself. This shortens the single scanning interval, accelerates hotspot identification, and reduces the time required for identity verification. At the same time, matching is performed only on the exclusive verification hotspot name, which can filter out irrelevant wireless network signals. This improves pairing efficiency and speeds up connection establishment without introducing additional invalid detections, thus balancing the efficiency of identity verification with the accuracy of matching.

[0021] In one embodiment of this application, the verification stage includes a multi-level verification process executed sequentially. The home appliance IoT communication module and the mobile terminal generate exclusive verification hotspot names corresponding to each level of verification based on the exclusive suffix characters of each level of verification, combined with the unique identity identifier and the preset hash algorithm. During each level of verification, the mobile terminal generates a verification hotspot name for that level and activates the corresponding verification hotspot. The home appliance IoT communication module then scans using the generated verification hotspot name as a matching benchmark. If the home appliance IoT communication module identifies the current level verification hotspot within the preset time limit corresponding to this level, it is determined that the current level verification is passed and proceeds to the next level verification; If any level of verification fails to identify the corresponding verification hotspot within the corresponding preset time limit, the identity verification is deemed to have failed. When all multi-level verifications pass, the identity verification is confirmed to be complete.

[0022] The above technical solution has the following advantages or beneficial effects: In this embodiment, the verification phase employs a multi-level verification process executed sequentially. The home appliance IoT communication module and mobile terminal generate unique verification hotspot names for each level based on the unique suffix characters of each verification level, combined with a unique identifier and a preset hash algorithm. Each verification level uses an independent hotspot for pairing and verification, preventing identity verification from being bypassed by a single impersonated hotspot. During each verification level, the mobile terminal activates the verification hotspot for that level, and the home appliance IoT communication module scans using that hotspot name as a reference. Only when a hotspot is identified within the preset time limit for that level can the next level of verification proceed. Failure to match within any time limit results in verification failure. This progressively timed verification mechanism effectively controls identity, significantly increasing the difficulty for malicious devices to forge hotspots for illegal access. Furthermore, the matching time limit for each level prevents the module from scanning at unlimited high frequencies, improving log capture security while controlling RF scanning duration, thus balancing communication security and low-power device operation.

[0023] In one embodiment of this application, after establishing a hotspot connection, the method further includes: The mobile terminal and the home appliance IoT communication module establish a data link based on a preset communication protocol, enabling the home appliance IoT communication module to transmit log data to the mobile terminal through the data link.

[0024] The above technical solution has the following advantages or beneficial effects: In this embodiment, after establishing a hotspot connection, the mobile terminal and the home appliance IoT communication module establish a data link based on a preset communication protocol. This allows the home appliance IoT communication module to transmit log data to the mobile terminal via this data link. This standardizes the data interaction format between the two parties, ensuring the orderly and complete transmission of log files and avoiding issues such as data packet corruption or loss. The application layer protocol can also re-verify the identities of both communicating parties and protect the transmitted content, effectively preventing the log data from being stolen or tampered with during transmission. This further enhances the reliability of data transmission and information security during offline log capture.

[0025] According to a second aspect of the present application, an offline log capture system for a home appliance IoT communication module is provided, including a mobile terminal and a home appliance IoT communication module. The mobile terminal and the home appliance IoT communication module cooperate with each other to execute the method described in any embodiment of the present application.

[0026] The above technical solution has the following advantages or beneficial effects: In this embodiment, the system consists of a mobile terminal and a home appliance IoT communication module. The two work together to execute the aforementioned offline log capture method. Both ends are pre-configured with unique identifiers, phased exclusive suffix characters, and preset hash algorithms. This allows for the generation of exclusive hotspot names in stages and the layered completion of wake-up, identity verification, and hotspot connection. Offline log collection can be completed without disassembling the device or relying on a local area network. The hardware architecture is simple, relying on wireless hotspots for pairing and communication. This avoids external wireless signal interference, resists the risk of malicious hotspot spoofing and log theft, and completely preserves fault scene data, effectively improving the accuracy, security, and ease of operation of log capture during after-sales maintenance.

[0027] It should be understood that the above general description and the following detailed description are merely exemplary and do not limit this application. Attached Figure Description

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

[0029] Figure 1 This is a flowchart of an embodiment of the method for offline capture of logs of a home appliance Internet of Things communication module provided in this application.

[0030] Figure 2 This is a flowchart illustrating the interaction between the mobile terminal and the IoT communication module for home appliances during the wake-up phase, as provided in an embodiment of this application.

[0031] Figure 3 This is a flowchart illustrating the interaction between the mobile terminal and the IoT communication module for home appliances during the verification phase, as provided in this application embodiment.

[0032] Figure 4 This is a flowchart illustrating the interaction between the mobile terminal and the IoT communication module for home appliances during the transmission phase, as provided in an embodiment of this application.

[0033] Figure 5 This is an interactive flowchart of an embodiment of the method for offline capture of logs from a home appliance Internet of Things communication module provided in this application.

[0034] Figure 6 This is a flowchart of the hotspot name generation steps provided in an embodiment of this application. Detailed Implementation

[0035] To make the objectives, implementation methods, and advantages of this application clearer, exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these exemplary embodiments are provided to make the description of this application more comprehensive and complete, and to fully convey the concept of the exemplary embodiments to those skilled in the art. It should be noted that the brief descriptions of terminology in this application are merely for the convenience of understanding the embodiments described below, and are not intended to limit the embodiments of this application. Unless otherwise stated, these terms should be understood in their ordinary and common meaning.

[0036] In the description of this application, it should be understood that the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined as "first," "second," or "third" may explicitly or implicitly include one or more features.

[0037] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0038] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0039] Existing log capture solutions based on temporary wireless access points (APs) generally use plaintext fixed hotspot names for pairing. This is susceptible to interference from other wireless networks in the environment, and device mismatch is highly likely in scenarios with multiple smart home appliances deployed together. Furthermore, the lack of dynamic encryption protection for hotspot names allows malicious devices to easily replicate the access link of the same hotspot, leading to log leaks. Such solutions cannot meet the requirements of operating without disassembly or outside the local area network, making it difficult to achieve secure, reliable, and accurate one-to-one log capture of modules in offline fault scenarios.

[0040] Based on this, this application provides a method and system for offline capture of logs from home appliance IoT communication modules. The aim is to uniformly configure unique identifiers, phased exclusive suffix characters, and preset hash algorithms for both modules and mobile terminals. Both ends can dynamically generate the same exclusive hotspot name in stages and sequentially complete device wake-up, identity verification, and hotspot connection. This can avoid wireless interference and prevent hotspot spoofing, and securely and accurately capture module logs without offline networking or disassembly.

[0041] Reference Figure 1 , Figure 1 This is a flowchart of an embodiment of the method for offline log capture of a home appliance IoT communication module provided in this application, including but not limited to steps S110 to S130. The home appliance IoT communication module is pre-programmed with a unique identifier (such as SN code / MAC address), phased exclusive suffix characters, and a unified preset hash algorithm (such as SHA256 one-way hash algorithm) at the factory.

[0042] Step S110: Pre-enter the mobile terminal with the same unique identifier, phased exclusive suffix characters, and preset hash algorithm as the home appliance IoT communication module.

[0043] In this step, after-sales maintenance personnel can enter the unique identifier corresponding to the target module through a dedicated maintenance APP on the mobile terminal; the APP locally stores the phased exclusive suffix characters that are configured synchronously with the module, which correspond to the independent suffix identifiers of the wake-up stage, multi-level verification stage, and transmission stage respectively; at the same time, the mobile terminal has a built-in preset hash operation logic that is completely consistent with the module.

[0044] This step is a unified configuration step beforehand, which ensures that the mobile terminal and the home appliance IoT communication module have the same calculation basis for generating hotspot names. Subsequent stages can generate and match exclusive hotspot names independently, ensuring that the hotspot identifiers of the two ends can correspond one-to-one from the source, avoiding mismatches across devices. At the same time, it relies on hash algorithms to hide the original identity information of the devices and reduce the risk of hotspot spoofing.

[0045] In step S120, during the wake-up phase, verification phase, and transmission phase, the home appliance IoT communication module and the mobile terminal generate a unique hotspot name for the corresponding phase based on the unique suffix characters of the corresponding phase, combined with a unique identifier and a preset hash algorithm, so as to complete the device wake-up, identity verification, and hotspot connection in sequence.

[0046] This process is divided into three phases: wake-up, verification, and transmission link establishment. Each phase uses a unique suffix character to generate a differentiated hotspot name, and device verification is completed in layers. The segmented time handshake can avoid the interference and spoofing defects caused by traditional fixed hotspots.

[0047] Wake-up phase: The mobile terminal generates a wake-up hotspot name and opens the corresponding wake-up hotspot based on the unique suffix character of the wake-up phase, combined with the unique identifier and the preset hash algorithm. The home appliance IoT communication module generates a wake-up hotspot name based on the unique suffix character of the wake-up phase, combined with the unique identifier and the preset hash algorithm, and scans for matching based on the generated wake-up hotspot name to complete the wake-up.

[0048] Specifically, the home appliance IoT communication module only initiates hotspot scanning upon power-on or switching to maintenance mode, maintaining a low-frequency, long-cycle first scan cycle under normal conditions to reduce standby power consumption. The mobile terminal calculates the wake-up hotspot name using a unique suffix character specific to the wake-up phase, its unique identifier, and a preset hash algorithm, and then activates the corresponding wake-up hotspot. The module calculates the wake-up hotspot name using the same suffix character, its unique identifier, and a preset hash algorithm, and uses this as the scanning matching benchmark.

[0049] The module employs a dual-condition matching mechanism during scanning: first, it identifies a wake-up hotspot name that matches its own calculated result; second, the received signal strength of that hotspot is greater than or equal to a preset signal threshold (e.g., -50dBm, limiting close-range operation). Both conditions must be met simultaneously for a successful wake-up. If no wake-up hotspot is found after a preset number of scans, the module enters a preset sleep period. After the sleep period ends, it resumes scanning in the first scan cycle, preventing continuous power consumption from invalid RF scans. This dual verification mechanism, relying on a dedicated wake-up hotspot name and signal strength threshold, filters out spoofed hotspots and environmental noise signals from a distance, preventing unrelated devices from accidentally waking up the device. Simultaneously, the sleep scanning mechanism balances the device's wake-up response capability with low power consumption requirements.

[0050] Verification Phase: After successful wake-up, the mobile terminal generates a verification hotspot name and activates the corresponding verification hotspot based on the unique suffix character of the verification phase, combined with the unique identifier and the preset hash algorithm. The home appliance IoT communication module generates a verification hotspot name based on the unique suffix character of the verification phase, combined with the unique identifier and the preset hash algorithm, and uses the generated verification hotspot name as a matching benchmark for scanning to complete the identity verification.

[0051] The verification phase may include a multi-level verification process executed sequentially. The home appliance IoT communication module and the mobile terminal generate a unique verification hotspot name corresponding to each level of verification based on the unique suffix characters of each level of verification, combined with a unique identifier and a preset hash algorithm.

[0052] Specifically, the verification phase employs a second scan cycle shorter than the first scan cycle to improve scan response speed. During each level of verification, the mobile terminal generates its own verification hotspot name and activates the corresponding hotspot. The home appliance IoT communication module scans using its own generated verification hotspot name as a matching benchmark. If the module identifies the verification hotspot within the preset time limit, the verification is considered successful, and the process proceeds to the next level. If any level of verification fails to identify the corresponding verification hotspot within the preset time limit, the identity verification fails. Identity verification is only considered complete when all levels of verification pass.

[0053] By using multi-level independent hash hotspot layered verification to replace single-hotspot authentication, the difficulty of malicious devices imitating hotspots for illegal access can be greatly increased. The graded time limit mechanism avoids unlimited high-frequency scanning by the module, balancing identity verification security and module power consumption control.

[0054] Transmission Phase: After successful verification, the transmission phase begins. Either the mobile terminal or the home appliance IoT communication module combines the transmission phase-specific suffix characters, unique identifier, and preset hash algorithm to generate a transmission hotspot name and activate the corresponding transmission hotspot. The other party uses the transmission hotspot name calculated by itself as a matching benchmark to scan and match. After successful scanning and identification, the hotspot connection is completed, and a dedicated wireless communication link is established.

[0055] This application embodiment uses a phased independent hotspot isolation wake-up, verification, and transmission process to ensure that there is no fixed public hotspot throughout the process. In the scenario of multiple appliances coexisting for operation and maintenance, there will be no device mismatch. The segmented timing handshake only opens the transmission link under the premise of process compliance, which can prevent logs from being stolen by illegal devices.

[0056] In step S130, after establishing a hotspot connection, the home appliance IoT communication module transmits log data to the mobile terminal to complete log capture.

[0057] In this step, after the hotspot connection is established, the mobile terminal and the home appliance IoT communication module establish a stable data link based on a pre-defined communication protocol agreed upon by both parties (such as TCP, but also compatible with common transmission protocols such as UDP and HTTP). The home appliance IoT communication module reads the locally stored operation logs and pushes the complete log data to the mobile terminal through this dedicated data link. The mobile terminal then stores the log files locally, completing the offline log capture operation.

[0058] The method provided in this application does not require disassembling the home appliance or connecting the device to a local area network. It avoids the loss of critical logs for momentary faults and occasional faults during long-term operation due to disassembly and power outages, and completely preserves fault scene data. Relying on the pre-sequenced hotspot handshake link transmission log, the data interaction link undergoes multi-layer identity verification, which can ensure that the log transmission process is not tampered with or stolen, thus ensuring both the integrity of fault tracing and the security of data transmission.

[0059] Reference Figures 2-5 , Figure 2 This is a flowchart illustrating the interaction between the mobile terminal and the IoT communication module for home appliances during the wake-up phase, as provided in an embodiment of this application. Figure 3 This is a flowchart illustrating the interaction between the mobile terminal and the home appliance IoT communication module during the verification phase, as provided in an embodiment of this application. Figure 4 This is a flowchart illustrating the interaction between the mobile terminal and the home appliance IoT communication module during the transmission phase, as provided in an embodiment of this application. Figure 5 This is an interactive flowchart of an embodiment of the method for offline capture of logs from a home appliance Internet of Things communication module provided in this application.

[0060] Each home appliance IoT communication module is programmed with a unique identifier at the factory, serving as a unique identification credential for the module. This identifier is used in conjunction with a phased, unique suffix character and a preset hash algorithm to generate three types of unique hotspot names: wake-up, verification, and transmission. This unique identifier distinguishes individual devices, preventing multiple devices from being connected to the same device or unauthorized devices from impersonating hotspots.

[0061] The mobile terminal can run an operation and maintenance APP, which supports inputting the module's unique identification, starting and stopping wireless hotspots, and WiFi scanning and network configuration. It can completely execute terminal-side actions at each stage: generating and starting a wake-up hotspot during the wake-up stage, generating and starting a verification hotspot during the verification stage, and starting or scanning transmission hotspots during the transmission stage.

[0062] The module is equipped with WiFi scanning, AP hotspot activation, and TCP service capabilities. It also has built-in stage-specific exclusive suffix characters and preset hash algorithms that are completely consistent with those of mobile terminals. In accordance with the limitation of unified algorithm storage in the module, it can independently calculate the wake-up, verification, and transmission hotspot names that are the same as those of mobile terminals offline. It completes the scanning and identification of each stage based on the hotspot names it generates, and realizes the establishment of device wake-up, identity verification, and log transmission links in a layered manner.

[0063] Reference Figure 2 and Figure 5 During the wake-up phase, the mobile terminal mainly performs the following steps S11 to S12.

[0064] Step S11: Generate a wake-up hotspot name, which is generated based on the unique identifier, wake-up suffix characters, and preset hash algorithm pre-stored in the home appliance IoT communication module.

[0065] Specifically, the mobile terminal has a built-in preset hash algorithm, agreed-upon suffix rules, and hotspot naming format. After receiving the unique identifier of the target home appliance IoT communication module entered by the maintenance personnel, it generates a unique wake-up hotspot name in three steps: concatenation, hash operation, and character truncation. First, the module's unique identifier string is directly concatenated with the suffix characters specific to the wake-up phase to form the original string. Then, a hash digest operation is performed on the original string to obtain a long hash value. Finally, a fixed number of characters are truncated from the complete hash digest as the final wake-up hotspot name. This ensures that each module corresponds to a unique hotspot name and avoids false wake-ups caused by duplicate hotspot names.

[0066] Specifically, refer to Figure 6 , Figure 6 This is a flowchart illustrating the hotspot name generation steps according to an embodiment of this application. In this embodiment, the wake-up hotspot name, hotspot name verification, and hotspot name transmission all employ a unified generation logic, which can be progressively completed through steps S610, S620, and S630. This achieves dynamic, unique, and encrypted hotspot name generation based on the device's unique identity information, effectively solving the technical defects of traditional fixed hotspot names, such as easy duplication, easy forgery, and poor security. The following is a detailed explanation of each step, and this generation logic can be reused for all types of hotspot names.

[0067] Step S610: Concatenate the unique identifier with the exclusive suffix character of the corresponding stage to obtain the original string.

[0068] In this step, the mobile terminal and the home appliance IoT communication module pre-define unified program rules. Using the unique and tamper-proof identifier (i.e., unique identity identifier) ​​pre-stored at the target home appliance IoT communication module as the base character, it is directly concatenated with the specific suffix characters for the corresponding stage to form the original string to be encrypted. The unique identity identifier is the exclusive identification information burned into the module at the factory, ensuring device uniqueness. The specific suffix characters for the corresponding stage can be independently configured according to different functional scenarios in the wake-up, verification, and transmission stages, used to distinguish the hotspot types in different interaction stages, ensuring that hotspot functions in different stages are isolated from each other and avoiding process confusion.

[0069] For example, the unique identifier of the target home appliance IoT communication module is set as the device-specific SN code JD20260603001; the default suffix characters for the wake-up function are -wx, the first-level verification suffix character is -jy1, and the transmission suffix character is -cs. If a wake-up hotspot name is generated, the unique identifier and the wake-up suffix character are concatenated to obtain the original string: JD20260603001-wx; if a verification hotspot name or a transmission hotspot name is generated, they are concatenated to JD20260603001-jy1 and JD20260603001-cs respectively, thus completing the accurate construction of the original string.

[0070] Step S620: Perform a hash operation on the original string using a preset hash algorithm to obtain a hash digest.

[0071] In this step, after obtaining the original string, a pre-agreed hash algorithm, uniformly agreed upon by the mobile terminal and the home appliance IoT communication module, is invoked to perform irreversible hash encryption on the original string, generating a fixed-length, unique hash digest. This step utilizes the one-way encryption characteristic of the hash algorithm to de-identify the original plaintext information such as the module's unique identifier and function suffixes, preventing device-specific information from being directly exposed in the hotspot name. This effectively prevents third parties from stealing device information or initiating unauthorized connections by forging hotspots, significantly improving the security of the log capture interaction process. Simultaneously, identical original strings processed by the fixed hash algorithm yield completely consistent hash digests, ensuring a perfect match between the hotspot name generation results on both the mobile terminal and the module, avoiding identification anomalies.

[0072] For example, the preset hash algorithm uses the SHA-256 hash algorithm to perform a hash operation on the original wake-up string JD20260603001-wx obtained in the previous step, generating a fixed 64-bit hexadecimal hash digest. The example operation result is: 3f89d271ac45e096b32cf18d790a62e481f56c392b70d18ce619f45872109ac6, thereby completing the encryption conversion of the original plaintext data.

[0073] Step S630: Extract characters of a preset length from the hash digest to generate the corresponding hotspot name.

[0074] In this step, because the hash digest character length is relatively long and cannot be directly adapted to the character length specification of WiFi hotspot naming, this step performs fixed-point character truncation on the complete hash digest according to a preset fixed truncation rule and a preset character length, ultimately generating a concise and unique hotspot name that conforms to the wireless network naming specification. This truncation rule is uniformly fixed on both the mobile terminal and the module, ensuring that the truncation position and length on both ends are completely consistent, further ensuring that the hotspot names generated on both ends match accurately, while preserving the uniqueness and encryption characteristics of the hash operation.

[0075] For example, the preset hotspot name character truncation rule is to truncate the first 16 characters of the hash digest. Taking the 64-bit hash digest 3f89d271ac45e096b32cf18d790a62e481f56c392b70d18ce619f45872109ac6 obtained in the previous step, the final wake-up hotspot name is 3f89d271ac45e096. Similarly, verification hotspots and transmission hotspots can also generate their own unique hotspot names according to this unified truncation rule.

[0076] This application's embodiment employs a progressive design of "plaintext concatenation - hash encryption - standardized truncation." It ensures the uniqueness of a single device, scenario, and hotspot by relying on the device's unique identifier, completely eliminating the problem of false wake-up and false connection caused by duplicate hotspot names. Furthermore, it uses hash encryption to desensitize device privacy information, avoiding the risks of data leakage and illegal imitation. At the same time, it is compatible with general WiFi hotspot naming standards, thus balancing the security, uniqueness, and practicality of the solution.

[0077] Step S12: Enable wake-up hotspot, that is, create and enable the corresponding wake-up hotspot with the wake-up hotspot name.

[0078] Specifically, after the mobile terminal completes the aforementioned hotspot name generation steps and obtains a unique wake-up hotspot name, step S12 is executed, which activates the wake-up hotspot. Specifically, the mobile terminal, based on the generated dedicated wake-up hotspot name, completes the wireless hotspot parameter configuration, hotspot creation, and continuous activation, providing a scannable and identifiable wireless wake-up signal source for the home appliance IoT communication module, thereby establishing the basic wireless environment for offline wake-up interaction. This step is the core execution step for offline device wake-up. The entire process requires no router networking or device internet connection; only a point-to-point wireless hotspot is established locally on the mobile terminal to achieve short-range wireless interaction with the target home appliance IoT communication module.

[0079] In the specific implementation process, the mobile terminal's internal operation and maintenance program automatically calls the system's wireless hotspot interface, configuring the unique character name generated by the aforementioned unique identifier, wake-up suffix character, and hash algorithm as the SSID name of the hotspot to be created. Simultaneously, it defaults to configuring the general wireless frequency band, encryption parameters, and channel parameters compatible with IoT module identification, completing the initial creation of the wake-up hotspot. After the hotspot is created, the mobile terminal continuously keeps the wake-up hotspot active and maintains it for a preset effective duration, stably broadcasting the hotspot signal within this duration to ensure that the home appliance IoT communication module can effectively capture the wake-up hotspot signal during the low-frequency scanning cycle. Furthermore, the mobile terminal only generates and activates a dedicated wake-up hotspot for the current target module, avoiding the simultaneous activation of multiple hotspots. This effectively avoids issues such as crosstalk and channel occupancy conflicts from multiple hotspot signals, ensuring the singularity and stability of the wake-up signal.

[0080] For example, the unique identifier of the target home appliance IoT communication module is JD20260603001. After string concatenation, SHA-256 hash operation, and character truncation, the final generated wake-up hotspot name is 3f89d271ac45e096. The mobile terminal operation and maintenance program automatically configures the device hotspot SSID with this character, automatically matches the 2.4G general WiFi frequency band, completes the hotspot creation, and continuously broadcasts the hotspot signal. During the preset first preset duration of the activation period, the hotspot continuously broadcasts valid wireless signal sources to the outside world for home appliance IoT communication modules in low-frequency scanning state to scan and identify, providing a stable wireless interaction basis for subsequent module signal strength determination and wake-up status confirmation.

[0081] By setting up the above steps, a dedicated wake-up signal source can be accurately generated for the target module. Compared with the traditional wake-up method with fixed hotspot names, it can avoid the problem of accidental wake-up of nearby home appliances from the signal source level. At the same time, relying on the local network construction method of mobile terminals, it gets rid of the dependence on local area networks and adapts to various after-sales maintenance scenarios such as offline failure of home appliances and network outages, which greatly improves the adaptability and wake-up accuracy of offline log capture scenarios.

[0082] Reference Figure 2 During the wake-up phase, the home appliance IoT communication module is mainly used to perform the following steps S13 to S15.

[0083] Step S13: Generate wake-up hotspot name. After the home appliance IoT communication module is powered on or enters maintenance mode, a wake-up hotspot name is generated based on the unique identifier, wake-up suffix characters, and preset hash algorithm.

[0084] Specifically, when the module powers on or enters a preset maintenance mode after receiving a maintenance trigger command, the module's internal firmware automatically starts the hotspot name calculation logic. It performs calculations according to the same hotspot generation rules as the mobile terminal, generating a wake-up hotspot name that is identical to the mobile terminal's. This ensures that the hotspot name calculation rules are consistent across both ends, providing a matching benchmark for subsequent scanning and matching of wake-up hotspots. The module independently generates hotspot names locally, eliminating the need to receive name data from external terminals and avoiding the security risks of name transmission tampering. Locally fixed parameters ensure that the algorithm and splicing rules cannot be illegally modified externally.

[0085] It should be noted that the module can independently calculate hotspot names locally, which is different from the existing solution where the module passively receives hotspot configuration information. It can still independently complete hotspot name calculation even when the device is offline and disconnected from the network, and there is no external data interaction. This is suitable for the use scenario of capturing offline logs of faulty home appliances.

[0086] Step S14: Perform hotspot scanning in the first scanning cycle.

[0087] Specifically, after the home appliance IoT communication module completes the local calculation and generation of the wake-up hotspot name, the module enters a wake-up standby state and performs a scan using the self-generated wake-up hotspot name as the matching benchmark during the first scan cycle. The first scan cycle is a low-frequency scan cycle preset by the module firmware for the normal standby wake-up phase, and is the default scan parameter in the module's regular maintenance standby mode. The core logic of this step is: in standby scenarios where no valid maintenance wake-up signal is detected, the module periodically scans the surrounding wireless networks using a low-frequency, long-interval approach, selectively searching for wireless hotspots that match the locally calculated dedicated wake-up hotspot name, rather than traversing all surrounding WiFi signals.

[0088] Specifically, after the module powers on or enters maintenance mode, it defaults to using a low-frequency scanning strategy for the first scan cycle. It periodically triggers a hotspot scan at fixed time intervals. After each scan, the RF scanning function is disabled, and the module enters a sleep / standby state, awaiting the next scan cycle. This low-frequency scanning mechanism significantly reduces the module's wireless RF operating time and power consumption in standby mode, meeting the needs of home appliances requiring long-term power-on standby and low-power operation. Simultaneously, the module only matches its own unique wake-up hotspot name throughout the process, effectively blocking numerous irrelevant WiFi hotspots in the surrounding environment and avoiding invalid identification and response, thus mitigating issues such as false wake-ups and accidental triggering of log capture processes from the underlying layer.

[0089] For example, the first scan cycle is pre-defined as 300 seconds (5 minutes) in the module firmware. After the module enters maintenance standby mode and generates a unique wake-up hotspot name 3f89d271ac45e096, it initiates a low-frequency scanning mechanism with a 300-second cycle. The module initiates a wireless scan every 5 minutes, identifying only the target hotspot with the name 3f89d271ac45e096 during the scan, directly filtering out irrelevant signals such as other home WiFi networks and other device maintenance hotspots in the vicinity. After a single scan is completed, the module immediately shuts down the RF module and enters low-power sleep mode until the next scan cycle arrives, cyclically executing the scan standby logic.

[0090] It should be noted that this first scan cycle is a dedicated scan parameter for the wake-up phase. Compared with the second scan cycle in the subsequent verification phase, it has a longer duration and a lower scan frequency. It is specifically adapted to the standby scenario of the device. While ensuring that it can be woken up by the mobile terminal normally, it maximizes the balance between the module's standby power consumption and the success rate of operation and maintenance wake-up. It solves the technical defects of traditional modules that cause excessive standby power consumption and serious power consumption during long-term operation due to continuous high-frequency scanning.

[0091] Step S15: Scanning a wake-up hotspot and determining that the wake-up is successful. That is, when a wake-up hotspot corresponding to the wake-up hotspot name is scanned and the received signal strength is greater than or equal to a preset signal threshold, the wake-up is determined to be successful.

[0092] Specifically, during the low-frequency hotspot scanning process according to the first scanning cycle, the home appliance IoT communication module continuously compares the hotspot names obtained from surrounding scans with the locally pre-calculated exclusive wake-up hotspot names, and simultaneously collects the wireless received signal strength of the corresponding hotspots, executing the wake-up success determination logic. This step sets dual determination conditions: only when the module simultaneously scans and matches a consistent wake-up hotspot name, and the received signal strength of that hotspot is greater than or equal to the system's preset signal threshold, can the device be ultimately determined to have successfully woken up and enter the subsequent verification process; if either condition is not met, the wake-up is determined to have failed, and the module continues to maintain the low-frequency standby scanning state of the first scanning cycle.

[0093] Specifically, name matching ensures that the currently scanned hotspot is the dedicated maintenance hotspot for the corresponding target device, eliminating the risk of false wake-ups caused by other imitation or identically named hotspots in the vicinity. Signal strength threshold determination limits the effective maintenance distance, utilizing the physical characteristic that wireless signal strength attenuates with increasing transmission distance to ensure that wake-up is only triggered in maintenance scenarios where the mobile terminal and home appliance are in close proximity, effectively avoiding false triggering issues caused by long-distance environmental interference, remote wake-up, and wireless noise interference. This dual-binding determination mechanism precisely constrains wake-up conditions from two dimensions: identity uniqueness and physical space validity, significantly improving the accuracy and reliability of the log capture wake-up phase.

[0094] For example, the module's dedicated wake-up hotspot is named 3f89d271ac45e096, and the system's preset wake-up signal strength threshold is -60dBm. When the module performs a low-frequency scan in a first scan cycle of 300 seconds, if it finds a wake-up hotspot whose name exactly matches 3f89d271ac45e096, and the real-time detected received signal strength of this hotspot is -45dBm, which is greater than the preset threshold of -60dBm, both conditions are met. The system immediately determines that the module has successfully woken up, exits the low-frequency scan standby state, and prepares to switch to the second scan cycle to enter the verification stage. If the module only scans a hotspot with the same name, but the detected signal strength is -70dBm, which is lower than the preset threshold, it is determined to be an invalid wake-up. The module maintains its original low-frequency scan and standby state and does not proceed to the subsequent process.

[0095] This dual-condition judgment logic abandons the traditional crude judgment method that relies solely on hotspot name matching to complete the wake-up. It filters out invalid signals and environmental interference signals from a distance by using a signal strength threshold, and completes identity verification with a unique hash of the exclusive hotspot name. Without increasing hardware costs, it can effectively avoid the problems of false wake-up and false start log capture in complex wireless environments, and take into account the sensitivity and anti-interference capability of device maintenance wake-up.

[0096] In some embodiments, refer to Figure 2 During the wake-up phase, the mobile terminal is also used to perform the following steps S16.

[0097] Step S16: After a first preset duration, turn off the wake-up hotspot, that is, turn on the wake-up hotspot and continue for a first preset duration, then turn off the wake-up hotspot.

[0098] Specifically, the mobile terminal maintains continuous broadcasting of the wake-up hotspot and simultaneously activates a built-in timing mechanism. When the hotspot's duration reaches a pre-configured first preset duration, the mobile terminal actively and automatically shuts down the current wake-up hotspot, stops broadcasting the wake-up hotspot signal, and completes the timing termination of the wake-up phase. This step is the timing termination mechanism for the wake-up phase, used to strictly limit the effective broadcast window of the wake-up hotspot, achieve timing isolation between the wake-up phase and the subsequent verification phase, and ensure that the overall process is executed in a layered, orderly, and progressive manner.

[0099] The first preset duration is a fixed duration parameter pre-embedded in the mobile terminal operation and maintenance program during the R&D phase. This duration parameter, after adaptation and configuration, can fully cover the time window for the home appliance IoT communication module to complete at least one hotspot scan based on the first scanning cycle, ensuring that the module has sufficient scanning opportunities to complete wake-up matching and avoiding wake-up failure due to premature hotspot shutdown. Simultaneously, the timed automatic shutdown mechanism avoids problems such as long-term wireless channel occupation, channel interference, and spectrum resource waste caused by the continuous operation of wake-up hotspots. It also forcibly cuts off the signal source during the wake-up phase, preventing signal superposition interference caused by the simultaneous existence of wake-up hotspots and subsequent verification hotspots, providing a clean wireless environment for the subsequent time-division opening of multi-level verification hotspots. Furthermore, this automatic shutdown mechanism requires no manual intervention, enabling fully automated time-series management and improving the convenience of on-site operation and maintenance.

[0100] In some embodiments, after a successful wake-up, the home appliance IoT communication module can switch from a first scanning cycle to a second scanning cycle and continuously monitor the wake-up hotspot until it disappears. If the wake-up hotspot is detected to have not disappeared for a set period of time, the home appliance IoT communication module determines that there is an anomaly and returns to the initial standby state after a certain delay.

[0101] Specifically, after the home appliance IoT communication module is successfully woken up, it can dynamically switch the scanning cycle and has the ability to self-heal from faults: once the wake-up is successful, it switches from the low-frequency first scanning cycle to the high-frequency second scanning cycle and continuously monitors the wake-up hotspot; if the hotspot is not closed after the time limit, it is determined that the process is abnormal, and after waiting for a preset time, it automatically exits the operation and maintenance process and switches back to the low-frequency standby state to achieve self-healing and reset.

[0102] The first scanning cycle is a low-frequency scanning cycle during normal module standby, with lower power consumption and longer intervals. The second scanning cycle is a high-frequency scanning cycle during the operation and maintenance interaction phase, with higher scanning sensitivity and faster signal acquisition speed, which can adapt to the short-term identification requirements of subsequent multi-level verification hotspots. Under normal circumstances, the mobile terminal will automatically turn off the wake-up hotspot after the first preset time period. The module can quickly detect the disappearance of the wake-up hotspot and then seamlessly enter the hotspot matching process of the verification phase. If the wake-up hotspot remains stationary for a long time due to abnormal situations such as mobile terminal program abnormalities, user misoperation, or failure to turn off the mobile terminal hotspot, it will cause the overall process to stagnate and fail to enter the verification and transmission stage. This can easily cause the module to be locked in the high-frequency scanning state for a long time, resulting in continuous power consumption loss, and even causing the program to freeze and fail to respond to subsequent operation and maintenance commands. Based on this, the embodiments of this application add abnormality monitoring and self-healing logic to realize the automatic identification and reset of process abnormalities.

[0103] This application embodiment achieves a balance between low standby power consumption and high operation and maintenance response speed by dynamically switching the scanning cycle. At the same time, by using the abnormal judgment of overdue wake-up hotspots and the delayed self-healing reset mechanism, it can solve the defects of process blockage, continuous high-frequency power consumption of modules, and inability to automatically exit abnormal states in the prior art. It effectively improves the fault tolerance, stability and device operation security of the log offline capture process, and can complete the abnormal recovery without manual device restart, greatly optimizing the after-sales on-site operation and maintenance experience.

[0104] During the verification phase, the mobile terminal generates one or more verification hotspot names based on the unique identifier, the corresponding exclusive suffix characters, and the preset hash algorithm, and activates the verification hotspots corresponding to each verification hotspot name in rounds.

[0105] After the verification phase begins, the mobile terminal reuses the pre-agreed encryption generation rules with the home appliance IoT communication module. Based on the target module's unique identifier, preset suffix characters, and a unified preset hash algorithm, it sequentially generates one or more independent verification hotspot names according to the aforementioned standardized hotspot generation process. Subsequently, the mobile terminal activates the corresponding verification hotspots in rounds according to the generated verification hotspot names, broadcasting them in staggered time slots. Only a single verification hotspot signal exists at any given time, providing a layered and orderly identity verification source for the home appliance IoT communication module.

[0106] The specific implementation logic is as follows: For single-level or multi-level verification scenarios, the mobile terminal configures a corresponding number of exclusive verification suffix characters. Different verification suffix characters correspond to different verification nodes, ensuring that the functions of each verification hotspot are independent and their levels are not confused. For each verification node, the mobile terminal sequentially performs original string concatenation, hash digest operation, and fixed-length character truncation to generate a unique corresponding verification hotspot name. Simultaneously, the mobile terminal has a built-in time-sharing scheduling mechanism. After the previous level verification hotspot reaches its preset duration and is closed and its signal completely disappears, the creation and opening of the next level verification hotspot is initiated. This strictly ensures that only a single verification hotspot broadcasts its signal at any given time, completely avoiding issues such as channel overlap, signal crosstalk, and spectrum conflicts, thus guaranteeing the accuracy of module scanning and identification.

[0107] Compared to traditional solutions involving parallel broadcasting of multiple hotspots and verification of fixed hotspot names, this application dynamically generates exclusive verification hotspots using homogeneous hashing, ensuring the uniqueness of hotspots for each device and each level of verification, and eliminating false verifications across devices. At the same time, it adopts a time-sharing start-stop timing design to optimize the wireless communication environment, improve the stability and success rate of the verification process, balance maintenance efficiency and data interaction security, and adapt to various complex on-site after-sales debugging scenarios.

[0108] In some embodiments, refer to Figure 3 and Figure 5 During the verification phase, the mobile terminal is mainly used to perform the following steps S21-S22.

[0109] Step S21: Generate the first verification hotspot, that is, generate the first verification hotspot name based on the unique identity identifier, the first verification suffix character and the preset hash algorithm.

[0110] Specifically, the mobile terminal calls the pre-defined hotspot generation rules of the IoT communication module for home appliances to generate a unique first verification hotspot name, providing a unique and exclusive wireless source identifier for subsequent first-level identity verification.

[0111] This step is the first round of verification source generation in the multi-level verification mechanism. Unlike the generation logic of the wake-up hotspot, second verification hotspot, and transmission hotspot, this step specifically configures the first verification suffix character, giving the first verification hotspot independent functional attributes and naming characteristics. By binding the device's unique identifier to a hash operation to generate the hotspot name, it ensures that the first verification hotspot name corresponding to each home appliance IoT communication module is unique and non-repeating, effectively avoiding verification misjudgments caused by duplicate verification hotspot names across different devices and environmental noise interference. Simultaneously, the mobile terminal and the module use completely consistent calculation rules, requiring no additional data interaction. Hotspot name calculation can be completed independently in offline mode, adapting to scenarios involving device network outages and offline fault maintenance.

[0112] Step S22: Enable the first verification hotspot, that is, create and enable the first verification hotspot corresponding to the first verification hotspot name.

[0113] Specifically, the mobile terminal calls its own wireless AP configuration interface to configure the first verification hotspot name as the SSID of the wireless hotspot, matches the preset 2.4GHz communication frequency band and general WiFi channel parameters, completes the hotspot parameter initialization and starts hotspot broadcasting, so that the first verification hotspot continuously sends out wireless beacon frames for the home appliance IoT communication module to search and identify in the second scanning cycle.

[0114] For example, the target module's unique identifier is JD20260603001, and the first verification hotspot name is 2d71f39c82e6ab12. After the mobile terminal has finished waking up the hotspot and turned it off on time, it configures the hotspot SSID as 2d71f39c82e6ab12, selects the 2.4GHz frequency band to establish the first verification hotspot, and starts broadcasting. The preset single-time activation duration is 180s. During the verification window period, the home appliance module in the second high-frequency scanning cycle (5s / time) continuously searches for the hotspot signal; after 180s, the terminal automatically shuts down the first verification hotspot, terminates the signal broadcast, and enters the next verification stage.

[0115] Correspondingly, refer to Figure 3 and Figure 5 During the verification phase, the home appliance IoT communication module is used to perform the following steps S23-S24.

[0116] Step S23: Perform hotspot scanning in the second scanning cycle.

[0117] Specifically, during the verification phase, the home appliance IoT communication module first performs calculations according to the same hotspot generation rules as the mobile terminal to generate a first hotspot name that is the same as the mobile terminal, and then dynamically switches from the first scanning cycle in standby mode to the second scanning cycle to continuously perform surrounding wireless network scanning operations.

[0118] Meanwhile, during the second scanning cycle, the module performs accurate matching and identification based solely on the first verification hotspot name it generates, automatically filtering out irrelevant WiFi signals in the vicinity. This improves the scanning response speed while ensuring the anti-interference and uniqueness of the verification process.

[0119] Step S24: Scan and identify the first verification hotspot within the first preset time limit.

[0120] Specifically, after the home appliance IoT communication module switches to the high-frequency scanning state of the second scanning cycle, it scans using the corresponding verification hotspot name it generates as the matching benchmark. If the scanning and identification matching of the first verification hotspot is completed within the first preset time limit window corresponding to the first round of verification, this is crucial. The first preset time limit is a pre-configured effective identification time window for the first verification hotspot, which matches the activation duration of the mobile terminal's first verification hotspot, forming a timing synchronization constraint between the two parties. This step is the core judgment action of the first round of identity verification, requiring the module to complete the target hotspot identification within the specified effective window period to determine the validity of the first round of verification, thus preventing invalid matching behavior due to timeouts or delays.

[0121] By adding a time-limited identification mechanism, the timing of the verification process can be strictly standardized, avoiding misjudgments caused by the module's delayed scanning and matching after the terminal hotspot is turned off. At the same time, it can filter out expired hotspot signals and historical stray signals remaining in the environment, further improving the rigor and reliability of identity verification.

[0122] This step relies on a high-frequency scanning mechanism combined with time-limited window matching logic to accurately adapt to the working sequence of mobile terminals opening verification hotspots in a time-sharing manner. It effectively avoids problems such as wireless signal delay, scanning sequence misalignment, and interference from expired signals, ensuring that the first round of identity verification is accurate, orderly, and controllable. This provides a solid foundation for subsequent multi-level verification loops and improves the security level of the overall log capture process.

[0123] Continue to refer to Figure 3 and Figure 5 During the verification phase, the mobile terminal is also used to perform the following steps S25-S27.

[0124] Step S25: After maintaining the first set duration, close the first verification hotspot, that is, open the first verification hotspot and maintain it for the first set duration before closing the first verification hotspot.

[0125] Specifically, after creating and activating the first verification hotspot, the mobile terminal executes the timing control logic in step S25 to manage the broadcast duration of the first verification hotspot. Specifically, the mobile terminal starts a built-in timer the instant the first verification hotspot is activated, continuously maintaining the wireless beacon frame broadcast state of the first verification hotspot, providing a stable and effective first-level verification and identification window for the home appliance IoT communication module. When the hotspot's continuous activation duration reaches a preset first set duration, the mobile terminal actively executes a shutdown command, closing the current first verification hotspot, terminating the corresponding wireless signal broadcast, completing the timing termination of the first-level verification stage, and freeing up wireless channel resources for the time-sharing activation of the subsequent second verification hotspot.

[0126] Step S26: Generate a second verification hotspot name, that is, generate a second verification hotspot name based on the unique identity identifier, the second verification suffix character and the preset hash algorithm.

[0127] Specifically, after the first verification hotspot is closed on time and the first-level verification process is completed, the mobile terminal executes step S26 to complete the encryption generation operation of the second verification hotspot name in order to carry out the second-level device identity verification. Specifically, the mobile terminal generates a unique second verification hotspot name based on the unique identifier of the target home appliance IoT communication module, a preset suffix character, and a preset hash algorithm agreed upon by both parties, which constitutes the second identity verification source identifier in the multi-level verification system.

[0128] This step generates a second verification hotspot name by combining an independent suffix character with hash encryption, forming a dual differentiated verification mechanism with the first verification hotspot. This constructs a two-level progressive identity authentication system, which can significantly improve the access security of the offline log capture process of home appliance IoT communication modules. It effectively solves the technical defects of traditional single-point verification methods, such as easy cracking, easy false verification, and weak security, and ensures the uniqueness and legitimacy of operation and maintenance interaction objects.

[0129] Step S27: Enable the second verification hotspot, that is, create and enable the second verification hotspot corresponding to the second verification hotspot name.

[0130] Specifically, after successfully generating the second verification hotspot name and confirming that the first verification hotspot has been completely shut down on time and that wireless channel resources have been fully released, the mobile terminal creates and activates the second verification hotspot corresponding to the second verification hotspot name. This step is the core step in the deployment of the signal source for secondary identity verification. It belongs to the progressive stage of the multi-level time-division verification process and strictly follows the timing rule of single-time-period single-hotspot broadcasting. The initialization and signal broadcasting of the second verification hotspot are completed under the premise that the first-level verification process is completely finished and there is no residual signal interference, so as to realize the independent and orderly connection of the two levels of verification hotspots in a time-division manner.

[0131] Correspondingly, during the verification phase, the home appliance IoT communication module is used to perform the following steps S28.

[0132] Step S28: Scan and identify the second verification hotspot within the second preset time limit, and determine that the verification is successful.

[0133] Specifically, after the home appliance IoT communication module has successfully identified the first verification hotspot and maintained a high-frequency scanning state in the second scanning cycle, step S28 is executed. This step is the final determination step of the entire multi-level verification mechanism. The module scans using the name of the second verification hotspot it generates as the matching benchmark, and completes the accurate scanning and matching identification of the second verification hotspot within the second preset time limit window corresponding to the second round of verification. Only after passing the time-division matching verification of the first and second verification hotspots can the overall verification stage be finally determined to have passed, allowing the process to enter the subsequent log data transmission stage.

[0134] If the module successfully scans and identifies a second verification hotspot with a completely matching name within the second preset time limit, and has previously successfully identified the first verification hotspot within the first preset time limit, the module determines that all bidirectional multi-level identity verifications have passed, immediately locks the legitimate operation and maintenance connection status, exits the verification monitoring process, and enters the log transmission standby state, waiting to establish a data link with the mobile terminal; if a matching second verification hotspot is not identified after the second preset time limit, or any level of verification times out or the matching fails, the overall verification is determined to have failed, the module terminates the current offline log capture process, automatically resets, and falls back to the initial low-power standby state.

[0135] This step employs a two-level time-sharing, step-by-step verification, and dual-locking judgment logic. Compared to the traditional single-hotspot matching verification method, it can greatly improve the device identity authentication capability in offline operation and maintenance scenarios, effectively preventing the risk of unauthorized terminals forging single hotspots to bypass verification and maliciously stealing device log data. At the same time, through dual time-limited window constraints, it ensures that the overall verification process is time-sequential and has clear boundaries, avoiding process deadlocks and abnormal delays, and significantly improving the security, fault tolerance, and operational stability of the offline log capture solution for home appliance IoT modules.

[0136] In some embodiments, if the first verification hotspot is not identified within the first preset time limit, or the second verification hotspot is not identified within the second preset time limit, the verification is determined to be unsuccessful, the home appliance IoT communication module switches back to performing hotspot scanning with the first scanning cycle, and returns to the standby state.

[0137] In other words, a fail-safe reset logic is set up during the verification process: After the home appliance IoT communication module switches to the second scanning cycle and enters the high-frequency verification scan, it performs time-limited identification and judgment on the first verification hotspot and the second verification hotspot in stages. If the corresponding verification hotspot is not matched within the corresponding preset time limit in any verification stage, the entire round of verification judgment fails. After the verification fails, the module terminates the current operation and maintenance process, exits the high-frequency second scanning cycle, switches back to the normal low-power first scanning cycle, returns to the initial standby working state, and waits for the next legal wake-up.

[0138] Specifically, this solution adopts a tiered failure judgment rule: In the first failure scenario, if the module cannot find the first verification hotspot with a name matching the local pre-stored name within the first preset time limit, the first round of verification fails directly without waiting for the second-level verification; in the second failure scenario, if the module successfully identifies the first verification hotspot and enters the second-level verification window, but cannot scan and match the second verification hotspot within the second preset time limit, the entire round of verification is also judged to have failed. In the above two failure scenarios, the module no longer maintains the high-power second-cycle high-frequency scanning, immediately shuts down the redundant RF scanning logic, and the scanning parameters revert to the factory-preset first scanning cycle, returning to the device's normal standby mode. This design is used to cope with abnormal operating conditions such as mobile terminal failure to shut down hotspots, human error, harsh on-site wireless environment, and illegal hotspot interference, avoiding unnecessary power consumption and program hangs caused by the module being locked in the high-frequency scanning state for a long time. It achieves fault self-healing by relying on automatic hardware firmware reset, without the need for manual power-off and device restart.

[0139] Reference Figure 3 and Figure 5 During the verification phase, the mobile terminal is also used to perform the following step S29.

[0140] Step S29: After maintaining the second set duration, close the second verification hotspot, that is, open the second verification hotspot and maintain it for the second set duration before closing the second verification hotspot.

[0141] Specifically, after creating and activating the second verification hotspot, the mobile terminal initiates its built-in timing control logic and executes step S29. The mobile terminal continuously maintains the wireless signal broadcasting state of the second verification hotspot and keeps a real-time timer. When the duration of the second verification hotspot's activation reaches a preset second set duration, the mobile terminal actively shuts down the second verification hotspot, terminates the wireless beacon frame broadcast, and completes the source output process of the overall verification phase.

[0142] The second set duration is a fixed timing parameter pre-agreed between the mobile terminal and the home appliance IoT communication module. This duration is adapted to the high-frequency scanning mechanism of the module's second scanning cycle, ensuring that the module has sufficient scanning times and an identification window period to guarantee the successful completion of the secondary identity verification action. Simultaneously, this step is the closing timing logic of the multi-level time-sharing verification architecture, following the aforementioned first verification hotspot timed shutdown mechanism, to achieve time-limited and orderly start and stop of the second verification hotspot.

[0143] During the transmission phase, the mobile terminal works with the home appliance IoT communication module to perform the following operations: After verification, one of the mobile terminal or the home appliance IoT communication module starts the corresponding transmission hotspot based on its own generated transmission hotspot name, and the other party scans using its own generated transmission hotspot name as the matching benchmark to establish a hotspot connection in order to capture the log data of the home appliance IoT communication module.

[0144] Once all the aforementioned verification steps are passed and the mobile terminal and the home appliance IoT communication module are confirmed as legitimate paired maintenance entities, the system officially enters the offline log data transmission phase. This phase is completed through bidirectional collaboration between the mobile terminal and the home appliance IoT communication module, and includes three progressive steps: either party independently generates and activates its own dedicated transmission hotspot; the other party scans and accesses the transmission hotspot; and both parties establish a connection based on a preset communication protocol and complete log data transmission. The entire process requires no router, external network, or other public network support, enabling purely offline point-to-point secure data interaction.

[0145] In this embodiment, a flexible mechanism of adaptive network construction by either party is adopted, which greatly improves the adaptability of offline operation and maintenance scenarios; a dedicated transmission hotspot is generated by hash encryption based on a unique identifier, realizing one-to-one dedicated channel interaction between devices and preventing unauthorized access and data leakage; and a standardized preset communication protocol is used to establish a transmission chain, ensuring the integrity, stability and security of log data transmission in offline network environments, effectively solving the technical defects of traditional home appliance IoT devices such as easy interference, easy forgery, unstable transmission and poor security in offline log capture.

[0146] Specifically, refer to Figure 4 and Figure 5 During the transmission phase, the home appliance IoT communication module is mainly used to perform the following steps S31-S32.

[0147] Step S31: Generate a transmission hotspot name, which is generated based on a unique identifier, transmission suffix characters, and a preset hash algorithm.

[0148] After all pre-verification checks are passed during the transmission phase, the home appliance IoT communication module executes step S31 to independently calculate and generate the transmission hotspot name. The module's local firmware pre-embeds its own unique identifier, the suffix characters corresponding to the transmission phase, and a preset hash algorithm and character truncation rules that are completely consistent with those of the mobile terminal. It reuses the unified hotspot generation logic of this application to sequentially complete string concatenation, hash operation, and digest truncation to generate a unique transmission hotspot name that is only compatible with the paired device.

[0149] The module generates hotspot names locally and automatically, without needing to interact with mobile terminals to obtain hotspot information, making it suitable for fully offline operation and maintenance scenarios without external network access; the hash-based dynamic naming abandons the fixed SSID scheme, improves the transmission channel's anti-spoofing and anti-network theft capabilities, and lays the naming foundation for subsequent point-to-point secure log transmission.

[0150] Step S32: Enable transmission hotspot, that is, create and enable the corresponding transmission hotspot with the transmission hotspot name.

[0151] After the home appliance IoT communication module completes the calculation and generation of the exclusive transmission hotspot name in step S31, the module executes step S32 to complete the wireless hotspot parameter configuration, entity creation and start hotspot broadcasting based on the generated transmission hotspot name.

[0152] In practice, the module calls its built-in WiFi radio frequency driver and AP configuration module to configure the transmission hotspot name generated in step S31 as the SSID of the wireless hotspot. Simultaneously, it loads preset communication frequency bands, channels, encryption parameters, and other wireless configuration items to complete the initial creation of the transmission hotspot. After configuration, the module drives the radio frequency module to continuously send beacon frames, ensuring the transmission hotspot is in a normal broadcast state that can be scanned and detected by external devices. This transmission hotspot is only used for point-to-point transmission of log data. It is independent of wake-up hotspots and verification hotspots, and is only activated after the verification process is completed. There is no parallel broadcasting with preceding hotspots, thus avoiding interference and channel contention issues caused by multiple hotspots on the same frequency.

[0153] For example, the transmission hotspot generated by the module is named 5c42b873f1d6e902. The module uses this character as the hotspot SSID, selects the 2.4GHz IoT general channel to configure the AP parameters, completes the hotspot creation and starts signal broadcasting, and waits for mobile terminals to scan, match and access the network.

[0154] This step involves the home appliance IoT communication module autonomously creating and enabling a transmission hotspot, which is suitable for operation and maintenance scenarios where the module actively reports logs and mobile terminals passively access and collect data. A dedicated hotspot is generated based on a unique hash name, which can restrict access from unpaired devices and ensure the data security of subsequent log transmissions from the wireless access level.

[0155] Correspondingly, refer to Figure 4 and Figure 5 During the transmission phase, the mobile terminal is mainly used to perform the following steps S33-S35.

[0156] Step S33: Generate a transmission hotspot name, which is generated based on a unique identifier, transmission suffix characters, and a preset hash algorithm.

[0157] Corresponding to the transmission hotspot generation mechanism on the home appliance IoT communication module side, after the verification steps are fully passed and the device identity is legally verified, the transmission phase begins. The mobile terminal executes step S33, autonomously completing the offline generation of its own transmission hotspot name. This step uses the same standardized encryption generation rules as the aforementioned module-side step S31. The algorithms, splicing logic, and character truncation rules of both parties are pre-unified and fixed, ensuring that the mobile terminal and the home appliance IoT communication module can calculate completely identical transmission hotspot names offline, providing a unified identity matching benchmark for subsequent bidirectional scanning matching, hotspot access, and data link establishment.

[0158] This step is a prerequisite for the mobile terminal side transmission stage. It does not rely on external networks, routers or other network devices. Hotspot name generation can be completed through local offline calculations. It is fully compatible with application scenarios such as offline operation and maintenance of home appliances, on-site fault diagnosis and network-free log capture. Moreover, it is from the same source and synchronized with the generation logic on the module side, ensuring the compatibility and reliability of two-way interaction.

[0159] Step S34: Scan and connect to transmission hotspots, that is, scan and connect to the transmission hotspots corresponding to the transmission hotspot names.

[0160] After the verification is passed and the mobile terminal obtains the transmission hotspot name through step S33, the mobile terminal executes step S34: relying on its own wireless radio frequency module to start scanning for surrounding wireless networks, searching for transmission hotspots in the environment whose SSID is completely consistent with the aforementioned transmission hotspot name, and completing network access after identifying the legitimate hotspot.

[0161] The specific implementation process is as follows: The mobile terminal uses the transmission hotspot name calculated locally in step S33 as the matching keyword to filter the scan results, eliminating other wake-up hotspots, verification hotspots, and nearby third-party WiFi signals in the environment. When a transmission hotspot with a completely matching SSID and a wireless signal strength that meets a preset threshold is found, it is determined that the hotspot is a legitimate transmission hotspot opened by the home appliance IoT communication module in step S32. Subsequently, the mobile terminal initiates a connection handshake according to the WiFi encryption rules agreed upon by both parties, completes authentication and key negotiation, and realizes wireless channel binding and hotspot access.

[0162] This step relies on the results of the preceding same-source hash operation for accurate matching. It does not require additional plaintext information such as hotspot names and passwords from the module. Hotspot identification is completed offline throughout the process, avoiding the risk of leakage caused by the plaintext transmission of hotspot names. It also relies on dedicated transmission hotspot names to isolate irrelevant hotspots and avoid data transmission abnormalities caused by accidental connection to stray WiFi networks.

[0163] Step S35: Establish a data link, that is, establish a data link with the home appliance IoT communication module based on the preset communication protocol.

[0164] After the mobile terminal successfully scans and connects to the transmission hotspot enabled by the home appliance IoT communication module and completes physical layer wireless network connectivity, the mobile terminal executes step S35. Based on the pre-defined communication protocol unified by both parties, the mobile terminal completes the application layer handshake interaction with the home appliance IoT communication module to establish a dedicated point-to-point data link. This step is the core preparatory step for log data transmission, realizing a hierarchical upgrade from physical layer connectivity to reliable application layer transmission, and providing a standardized, controllable, and secure communication channel for subsequent unidirectional transmission of log data from the module to the terminal.

[0165] The preset communication protocol is a dedicated lightweight communication protocol customized for offline, non-internet-based maintenance scenarios. It is pre-embedded in the firmware of the mobile terminal and the IoT communication module of the home appliance. The protocol versions, handshake fields, verification rules, frame formats, and interaction sequences of both parties are completely consistent, requiring no online negotiation or external network configuration, and supporting pure offline point-to-point interaction. This protocol differs from the general WiFi communication protocol and is optimized for the transmission requirements of small batches, multiple fragments, and high integrity of device logs. It has handshake authentication, data verification, packet loss detection, abnormal retransmission, and link keep-alive mechanisms.

[0166] The specific link establishment process is as follows: After the mobile terminal connects to the transmission hotspot, it actively sends a link establishment request frame to the home appliance IoT communication module according to the handshake frame format of the preset communication protocol. After receiving the request frame, the home appliance IoT communication module completes frame header verification, protocol version verification, and identity legitimacy verification. After the verification is passed, the module returns a link confirmation response frame to the mobile terminal. The mobile terminal receives the response frame and completes a secondary verification. The handshake interaction between the two parties is completed, and a stable and exclusive dedicated data link is officially established. After the link is established, both parties lock the current point-to-point communication channel and reject protocol access requests from other unfamiliar devices to avoid problems such as multiple devices connecting together, data packet mixing, and illegal hijacking.

[0167] It should be noted that this data link can only be established after all the pre-verification steps have been passed and the dedicated transmission hotspot has been successfully matched and accessed. It is a dedicated operation and maintenance link with multi-level security constraints, and is completely isolated from the previous wake-up link and verification source. It is only used for the encrypted transmission of operation and maintenance data such as device operation logs, fault logs, and device parameters, further ensuring the privacy and security of operation and maintenance data.

[0168] For example, after a mobile terminal successfully connects to the transmission hotspot with SSID 5c42b873f1d6e902, it initiates a handshake process using a pre-defined dedicated maintenance communication protocol. The mobile terminal encapsulates a handshake request message according to the protocol frame format and sends it to the module. The module verifies the message format, protocol version, and device matching relationship. If the verification is valid, the module replies with an acknowledgment message. The terminal receives the acknowledgment message and verifies that it is correct. The two parties successfully establish a dedicated data link and enter a transmittable state, waiting for the home appliance IoT communication module to push log data.

[0169] In this step, application-layer link establishment is completed through a custom preset communication protocol, overcoming the shortcomings of traditional general WiFi which only provides physical connectivity without application-layer authentication, and achieving dual security protection of physical access and protocol authentication. Relying on the offline protocol handshake mechanism, it is adapted to on-site operation and maintenance scenarios without routers or external networks, greatly improving the environmental adaptability of the solution. At the same time, the standardized link establishment and verification mechanism effectively reduces the probability of packet loss, packet errors, and out-of-order transmission during log transmission, ensuring the integrity, stability, and reliability of subsequent log data transmission.

[0170] Understandably, the preset communication protocol is stored in the firmware of the mobile terminal and the IoT communication module of the home appliance. After the wireless link of the transmission hotspot is established, a standard general network protocol or a custom private application protocol can be selected to establish the data link and transmit logs. The standard general network protocol can be any one or more combinations of TCP, UDP, HTTP, and FTP.

[0171] Correspondingly, refer to Figure 4 and Figure 5 During the transmission phase, the home appliance IoT communication module is also used to perform the following steps S36.

[0172] Step S36: Transmit log data, that is, transmit log data to the mobile terminal through the data link.

[0173] After the mobile terminal and the home appliance IoT communication module successfully establish a dedicated data link based on the preset communication protocol, the home appliance IoT communication module executes step S36 to transmit various log data stored locally to the mobile terminal through the stable point-to-point data link.

[0174] Specifically, during data transmission, the home appliance IoT communication module first reads all the operation and maintenance data permanently stored in the local non-volatile storage area, including but not limited to device operation logs, operating parameter logs, fault alarm logs, abnormal reset records, module communication status logs, and device configuration change logs. The module then performs standardized encapsulation processing on the raw log data according to the currently enabled preset communication protocol specifications: for large-capacity log data, it performs ordered fragmentation, numbering, and checksum embedding to generate compliant transmission data packets; subsequently, through the established dedicated data link, it continuously and orderly pushes the log data packets to the mobile terminal in chronological order.

[0175] It should be noted that this log transmission is a dedicated point-to-point one-way transmission. Relying on the transmission hotspot generated by the unique hash and the dedicated data link, external device access and data interference are isolated. During the transmission, only the paired mobile terminal can receive and parse the log data of this group. Other devices in the vicinity cannot listen to, intercept or tamper with the transmission content, effectively ensuring the confidentiality and uniqueness of the equipment operation and maintenance logs.

[0176] In this step, a multi-protocol compatible transmission architecture is used to adapt to the log transmission needs of different operation and maintenance scenarios, greatly improving the versatility and adaptability of the solution. By combining the dual protection of standard network protocols and custom private verification mechanisms, the technical problems of easy packet loss, easy interference, and easy leakage in log transmission under offline operation and maintenance scenarios are completely solved while ensuring transmission efficiency. Relying on the multi-level verification and dedicated link mechanism, accurate, secure and complete offline capture of log data is achieved, effectively supporting on-site equipment fault diagnosis, operation status tracing and operation and maintenance data analysis.

[0177] In some embodiments, this application also provides an offline log capture system for home appliance IoT communication modules. The system comprises two main hardware components: a mobile terminal and a home appliance IoT communication module. The mobile terminal and the home appliance IoT communication module are equipped with matching firmware programs, and the two work together to execute the offline log capture method for home appliance IoT communication modules described in any of the foregoing embodiments.

[0178] This system achieves collaborative implementation of software and hardware based on the aforementioned offline capture method. Through a two-layer security architecture of identity verification and dedicated transmission link, it prevents unauthorized devices from accessing and stealing logs. The multi-protocol compatible transmission configuration can adapt to the data transmission and reception needs of different operation and maintenance scenarios. The system architecture is streamlined and the on-site deployment is convenient, effectively solving the shortcomings of traditional home appliance module log capture that rely on online networking and are easily interfered with and stolen.

[0179] The preferred embodiments of the present application have been described above with reference to the accompanying drawings, but this does not limit the scope of the claims of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and substance of the embodiments of the present application shall be within the scope of the claims of the present application.

Claims

1. A method for offline log capture of home appliance IoT communication modules, characterized in that, The home appliance IoT communication module pre-stores a unique identifier, a phased exclusive suffix character, and a preset hash algorithm. The method includes: The mobile terminal is pre-loaded with the same unique identifier, the phased exclusive suffix characters, and the preset hash algorithm as the home appliance IoT communication module; During the wake-up phase, verification phase, and transmission phase, the home appliance IoT communication module and the mobile terminal generate a unique hotspot name for the corresponding phase based on the unique suffix characters of the corresponding phase, combined with the unique identifier and the preset hash algorithm, so as to complete the device wake-up, identity verification, and hotspot connection in sequence. After establishing a hotspot connection, the home appliance IoT communication module transmits log data to the mobile terminal to complete log capture.

2. The method according to claim 1, characterized in that, Based on the unique suffix characters for the corresponding stage, combined with the unique identifier and the preset hash algorithm, a unique hotspot name for the corresponding stage is generated, including: The unique identifier is concatenated with the exclusive suffix character for the corresponding stage to obtain the original string; The original string is hashed using the preset hash algorithm to obtain a hash digest; Extract characters of a preset length from the hash digest to generate a unique hotspot name for the corresponding stage.

3. The method according to claim 2, characterized in that, In the wake-up phase, verification phase, and transmission phase, the home appliance IoT communication module and the mobile terminal respectively generate a unique hotspot for the corresponding phase based on the unique suffix characters of the corresponding phase, combined with the unique identifier and the preset hash algorithm, to sequentially complete device wake-up, identity verification, and hotspot connection, including: During the wake-up phase, the mobile terminal generates a wake-up hotspot name and activates the corresponding wake-up hotspot based on the unique suffix character of the wake-up phase, combined with the unique identifier and the preset hash algorithm. The home appliance IoT communication module generates a wake-up hotspot name based on the unique suffix character of the wake-up phase, combined with the unique identifier and the preset hash algorithm, and uses the generated wake-up hotspot name as a matching benchmark for scanning to complete the wake-up process. During the verification phase, the mobile terminal generates a verification hotspot name and activates the corresponding verification hotspot based on the unique suffix character of the verification phase, combined with the unique identity identifier and the preset hash algorithm. The home appliance IoT communication module generates a verification hotspot name based on the unique suffix character of the verification phase, combined with the unique identity identifier and the preset hash algorithm, and uses the generated verification hotspot name as a matching benchmark for scanning to complete the identity verification. During the transmission phase, one of the mobile terminal or the home appliance IoT communication module generates a transmission hotspot name and activates the corresponding transmission hotspot based on the unique suffix character of the transmission phase, combined with the unique identifier and the preset hash algorithm. The other party scans using the generated transmission hotspot name as a matching benchmark to establish a hotspot connection.

4. The method according to claim 3, characterized in that, During the wake-up phase, the home appliance IoT communication module initiates hotspot scanning after powering on or entering maintenance mode, and performs scanning using the wake-up hotspot name it generates as a matching benchmark in the first scanning cycle.

5. The method according to claim 4, characterized in that, During the wake-up phase, when the home appliance IoT communication module scans the wake-up hotspot and the received signal strength of the wake-up hotspot is greater than or equal to a preset signal threshold, the wake-up is determined to be successful.

6. The method according to claim 4, characterized in that, During the wake-up phase, if the home appliance IoT communication module fails to identify the wake-up hotspot after a preset number of consecutive scans, the home appliance IoT communication module enters a sleep state for a preset sleep duration. After the sleep period ends, it resumes hotspot scanning at the first scan cycle.

7. The method according to claim 4, characterized in that, During the verification phase, the home appliance IoT communication module uses a second scanning cycle and performs scanning based on the verification hotspot name it generates itself. The second scanning cycle is shorter than the first scanning cycle.

8. The method according to claim 3, characterized in that, The verification stage includes a multi-level verification process executed sequentially. The home appliance IoT communication module and the mobile terminal generate exclusive verification hotspot names corresponding to each level of verification based on the exclusive suffix characters of each level of verification, combined with the unique identity identifier and the preset hash algorithm. During each level of verification, the mobile terminal generates a verification hotspot name for that level and activates the corresponding verification hotspot. The home appliance IoT communication module then scans using the generated verification hotspot name as a matching benchmark. If the home appliance IoT communication module identifies the current level verification hotspot within the preset time limit corresponding to this level, it is determined that the current level verification is passed and proceeds to the next level verification; If any level of verification fails to identify the corresponding verification hotspot within the corresponding preset time limit, the identity verification is deemed to have failed. When all multi-level verifications pass, the identity verification is confirmed to be complete.

9. The method according to claim 3, characterized in that, After establishing a hotspot connection, the method further includes: The mobile terminal and the home appliance IoT communication module establish a data link based on a preset communication protocol, enabling the home appliance IoT communication module to transmit log data to the mobile terminal through the data link.

10. An offline log capture system for home appliance Internet of Things (IoT) communication modules, characterized in that, The device includes a mobile terminal and a home appliance IoT communication module, wherein the mobile terminal and the home appliance IoT communication module cooperate with each other to perform the method described in any one of claims 1-9.

Images