A 4G Cat.1 module-based household power detection and management system and method

Abstract

The application relates to a 4GCat.1 module-based household power detection and management system and method, which comprises a cloud management platform, a user terminal and multiple terminal devices; each terminal device is provided with a 4GCat.1 communication module and corresponds to different household power objects. The cloud management platform responds to the management request of the user terminal for the target household power object, and issues a management instruction to the target terminal device; after the target terminal device executes corresponding power-on control or power-off control, a control confirmation record including the execution result and the on-off state after execution is generated. When a communication anomaly occurs, the target terminal device locally saves the control confirmation record, and uploads it to the cloud management platform before the unuploaded power consumption data after the communication is restored, so that the cloud management platform updates the management state according to the execution result and the on-off state, thereby improving the timeliness and reliability of the confirmation of the remote on-off control result and reducing the risk of inconsistency between the cloud display state and the terminal actual state.

Description

Technical Field

[0001] This application relates to the field of smart home power management technology, and in particular to a home power detection and control system and method based on a 4GCat.1 module. Background Technology

[0002] With the development of smart homes and home energy management, home electricity detection and control systems have been gradually applied to scenarios such as home electricity safety monitoring, remote on / off control, and electricity management. Existing solutions mostly rely on local area communication methods such as WiFi and Bluetooth to achieve data interaction between terminal devices and the control terminal. However, in remote independent electricity use scenarios such as self-built houses in rural areas, independent kitchens in courtyards, pump rooms, and rooftop water heater branches, there is often a problem of insufficient local area communication coverage, making it difficult for the corresponding terminal devices to reliably connect to the control system.

[0003] In such scenarios, users are often more concerned with remote on / off control of high-risk household electrical appliances such as electric heaters, water pumps, and heating loads. Although existing systems can send remote control commands to terminal devices, when communication anomalies, short-term link interruptions, or unstable recovery occur between the terminal devices and the cloud control platform, the cloud control platform may not be able to obtain the execution results of the control commands and the actual on / off status after execution in a timely manner. This can easily lead to inconsistencies between the status displayed on the cloud and the actual status on the terminal.

[0004] Furthermore, after communication is restored, if the terminal device prioritizes retransmitting the large amount of electricity consumption data accumulated during the communication anomaly, while the execution results and actual on / off status related to remote on / off control are not prioritized for uploading, the cloud management platform will still find it difficult to confirm in a timely manner whether the target household electricity user has actually been powered on or off. This is especially true in the scenario of power outage control for high-risk household electricity users, which will affect the reliability of the confirmation of remote management results and the safety of household electricity use.

[0005] Therefore, there is a need to provide a household electricity detection and control system and method to solve the problem that it is difficult to confirm the results of remote control in a timely manner when the communication of independent household electricity users is abnormal or during the communication recovery process. Summary of the Invention

[0006] The purpose of this application is to provide a household electricity detection and control system and method based on the 4GCat.1 module, so as to solve the problem that the remote control results are difficult to confirm in a timely manner when the communication of remote independent household electricity users is abnormal or during the communication recovery process.

[0007] According to one aspect of this application, a household electricity detection and control system based on a 4GCat.1 module is provided, including a cloud control platform, a user terminal, and multiple terminal devices; the multiple terminal devices correspond to different household electricity objects, which are household electricity branches or electrical devices;

[0008] Each of the terminal devices is equipped with a 4GCat.1 communication module. Each of the terminal devices is used to collect electricity consumption data of the corresponding household electricity user and to transmit data bidirectionally with the cloud management platform through its respective 4GCat.1 communication module.

[0009] The cloud-based management and control platform is used to respond to the management and control requests issued by the user terminal for the target household electricity user, and to issue management and control instructions to the target terminal device corresponding to the target household electricity user;

[0010] The target terminal device is used to execute the corresponding power-on control or power-off control after receiving the control command, and generate a control confirmation record corresponding to the control command. The control confirmation record includes the execution result of the control command and the on / off status of the target household electricity user after executing the control command.

[0011] The target terminal device is also used to locally save the control confirmation record when a communication anomaly occurs before the control confirmation record is uploaded, and upload the control confirmation record to the cloud management platform before the unuploaded electricity data after communication is restored, so that the cloud management platform updates the management status of the target household electricity user based on the execution result and the on / off status.

[0012] According to another aspect of this application, a method for detecting and controlling household electricity consumption based on a 4GCat.1 module is provided. This method is applied to a household electricity consumption detection and control system including a cloud-based management platform, a user terminal, and multiple terminal devices. The multiple terminal devices correspond to different household electricity users, and each terminal device is equipped with a 4GCat.1 communication module. The method includes:

[0013] In response to the control request issued by the user terminal for the target household electricity user, the system determines the target terminal device corresponding to the target household electricity user and issues control instructions to the target terminal device.

[0014] The system controls the target terminal device to execute the corresponding power-on or power-off control after receiving the control command, and generates a control confirmation record corresponding to the control command. The control confirmation record includes the execution result of the control command and the on / off status of the target household electricity user after executing the control command.

[0015] If a communication error occurs before the control confirmation record is uploaded, the target terminal device is controlled to locally save the control confirmation record.

[0016] After communication is restored, the target terminal device is controlled to upload the control confirmation record to the cloud management platform before any unuploaded power consumption data is uploaded.

[0017] The cloud-based management platform updates the management status of the target household electricity user based on the execution results and on / off status in the control confirmation record.

[0018] This application has the following beneficial effects:

[0019] This application generates a control confirmation record, including the execution result and the on / off status after the terminal device receives the control command and executes the corresponding power-on or power-off control, so that the remote control process is no longer limited to "the cloud has issued the control command", but further forms a confirmation basis that can reflect "whether the terminal has completed the control action" and "the current actual on / off status of the target household electricity user".

[0020] Meanwhile, if a communication anomaly occurs before the control confirmation record is uploaded, the target terminal device locally saves the control confirmation record and uploads it before the unuploaded power consumption data after communication is restored. This allows the cloud management platform to obtain key information affecting the judgment of safety management status first, avoiding the need for a large amount of historical power consumption data to be re-uploaded and occupy the communication opportunity after restoration, thereby improving the timeliness of remote on / off control result confirmation.

[0021] Therefore, in remote independent household electronics scenarios, even if a short-term communication anomaly occurs between the terminal device and the cloud management platform, the risk of inconsistency between the cloud-displayed status and the actual status of the terminal can be reduced, thereby improving the reliability of confirmation and the safety of household electricity use when implementing remote on / off control of high-risk household electricity users. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0023] Figure 1 This is a structural connection diagram of the household electricity detection and control system described in one embodiment of this application.

[0024] Figure 2 This is a connection diagram of the household electricity detection and control system described in one embodiment of this application.

[0025] Figure 3 This is a flowchart illustrating the steps of a household electricity detection and control method according to an embodiment of this application.

[0026] The following are the definitions of the reference numerals: 100, Household electricity detection and control system; 10, Cloud control platform; 20, User terminal; 30, Terminal equipment; 31, Household electricity user; 32, 4GCat.1 communication module; 311, Household electricity branch; 312, Electrical equipment. Detailed Implementation

[0027] To facilitate understanding of this application, it will be described below with reference to the accompanying drawings. It should be noted that the following embodiments are used to illustrate the technical solution of this application and are not intended to limit the scope of protection of this application.

[0028] See Figures 1-3 This application provides a home electricity detection and control system 100 based on a 4GCat.1 module. The home electricity detection and control system 100 is suitable for residential scenarios with multiple dispersed home electricity users 31, and at least some of these users are located in areas where the home local area network (LAN) coverage is unstable. For example, in a rural self-built house scenario, the main house has lighting and socket branches, the independent kitchen in the yard has an electric heater, the corner pump room has a water pump, and the roof has a water heater branch. Because the independent kitchen, pump room, and roof branch are separated from the main house by distance, walls, or metal structures, using local area communication methods such as WiFi or Bluetooth can easily lead to insufficient signal coverage, link fluctuations, or terminal offline issues, making it difficult to ensure timely confirmation of remote control results.

[0029] Specifically, the household electricity monitoring and control system 100 includes a cloud-based management platform 10, a user terminal 20, and multiple terminal devices 30. Each terminal device 30 corresponds to a different household electricity user 31, which can be a household electricity branch 311 or a household appliance 312. For users requiring overall management, the terminal device 30 can be connected to the corresponding household electricity branch 311; for users requiring individual management, the terminal device 30 can be connected to the corresponding household appliance 312. This configuration allows the household electricity monitoring and control system 100 to adapt to both branch-level and device-level management scenarios, improving deployment flexibility in household settings. The user terminal 20 is used to allow users to view the current status of each household electricity user 31 and initiate control requests for the target household electricity user 31; the cloud control platform 10 is used to receive the control requests sent by the user terminal 20 and forward the control requests to the corresponding target terminal device 30 according to the correspondence between the target household electricity user 31 and the terminal device 30; the terminal device 30 is used to collect the electricity consumption data of the corresponding household electricity user 31 and execute the power-on or power-off control issued by the cloud.

[0030] Furthermore, each of the terminal devices 30 is equipped with a 4GCat.1 communication module 32, and each terminal device 30 transmits data bidirectionally to the cloud management platform 10 through its respective 4GCat.1 communication module 32. By enabling each terminal device 30 to have independent cellular communication capabilities, even if a household electricity user 31 is located in an independent area within the yard, on the roof, or in an outbuilding, it can bypass the coverage limitations of the main building's local area network and directly establish a communication link with the cloud management platform 10, thereby improving the access capability of the household electricity detection and management system 100 to distributed household electricity users 31. Specifically, each of the terminal devices 30 continuously collects the electricity consumption data of the corresponding household electricity user 31 and uploads it to the cloud management platform 10 through its respective 4GCat.1 communication module 32. The electricity consumption data may include one or more of the following: current data, voltage data, power data, circuit continuity status data, and runtime data. After receiving the electricity consumption data uploaded by each terminal device 30, the cloud-based management platform 10 can display the operation information of the corresponding household electricity user 31 on the user terminal 20, so that users can remotely view and manage it daily.

[0031] It should be noted that the electricity consumption data in this application is not limited to data collected only in the power-on control scenario, but refers to at least one type of data that can characterize the operating status, power supply circuit status, or post-control status of the household electricity object 31. When the household electricity object 31 is in the power-on state, the electricity consumption data may include current, voltage, power, and running time data. When the household electricity object 31 is in the power-off state or after the power-off control is executed, the electricity consumption data may include circuit conduction status data and historical operating data collected before control but not yet uploaded.

[0032] The implementation process in this embodiment is described below with reference to a specific scenario. For example, after leaving home, a user needs to confirm whether the electric heater in the independent kitchen in the yard has been de-energized. At this time, the user selects the household electrical object 31 corresponding to the electric heater through the user terminal 20 and sends a power-off request. After the power-off request is uploaded to the cloud management platform 10, the cloud management platform 10 determines the target terminal device 30 corresponding to the electric heater based on the pre-established correspondence between household electrical objects 31 and terminal devices 30, and issues a control command corresponding to the power-off control to the target terminal device 30. After receiving the control command, the target terminal device 30 executes the corresponding power-off control on the power supply circuit where the electric heater is located. Specifically, the target terminal device 30 can disconnect the power supply circuit where the electric heater is located through its internal relay, switch drive unit, or other power-on / off execution components. Accordingly, after executing the power outage control, the target terminal device 30 generates a control confirmation record corresponding to the control command. The control confirmation record includes the execution result of the control command and the on / off status of the target household electricity user 31 after executing the control command.

[0033] Furthermore, after the target terminal device 30 generates the control confirmation record, if a communication anomaly occurs before the control confirmation record is uploaded, the target terminal device 30 will save the control confirmation record locally. The communication anomaly can manifest as a two-way data transmission interruption between the target terminal device 30 and the cloud management platform 10, data transmission failure, response timeout, or unstable link recovery. In this case, the target terminal device 30 does not discard the control confirmation record but saves it locally as key result information directly related to this remote control action. Furthermore, after communication is restored, the target terminal device 30 uploads the control confirmation record to the cloud management platform 10 before uploading any unuploaded electricity consumption data. This is because ordinary electricity consumption data mainly reflects historical operating conditions. Although it has monitoring and analytical value, its timeliness requirement is relatively low compared to the remote control action just initiated by the user. The control confirmation record directly corresponds to the power-on or power-off control initiated by the user, especially in scenarios involving power outages of high-risk household electrical appliances 31 such as electric heaters, water pumps, and water heaters, where users are more concerned about whether the equipment has actually been powered off. Therefore, prioritizing the uploading of the control confirmation record after communication is restored enables the cloud management platform 10 to obtain information directly related to the remote control result first, thereby completing the status confirmation more quickly.

[0034] For example, in this embodiment, if the target terminal device 30 corresponding to the electric heater has completed the power-off control and the power supply circuit where the electric heater is located is in a disconnected state, but due to communication abnormalities, the cloud has not yet received the control confirmation record in a timely manner, the user terminal 20 may still display the original state or the pending confirmation state. When communication is restored, the target terminal device 30 prioritizes uploading the control confirmation record to the cloud management platform 10. After receiving the control confirmation record, the cloud management platform 10 updates the management status of the target household electricity user 31 according to the execution result and on / off status therein. For example, when the execution result shows that the power-off control has been completed, and the on / off status indicates that the current state is power-off, the cloud management platform 10 updates the management status corresponding to the electric heater to the power-off state and displays it synchronously on the user terminal 20. After that, the target terminal device 30 continues to upload the electricity consumption data accumulated during the communication abnormality period that was not uploaded.

[0035] In one specific embodiment, in the aforementioned household electricity detection and control system 100, the control request can be limited to a power-on or power-off request targeting the household electricity user 31. Correspondingly, the control instructions issued by the cloud control platform 10 can be power-on control instructions or power-off control instructions. The execution result generated by the target terminal device 30 can be distinguished as control completed or control incomplete. The state of the target household electricity user 31 after control can be distinguished as a power-on state or a power-off state. The request initiated by the user through the user terminal 20 is not a generalized control request, but a power-on or power-off operation specifically targeting the target household electricity user 31, thereby ensuring consistency between the user's control intent, the cloud-side scheduling logic, and the terminal-side execution direction.

[0036] For example, when a user needs to remotely start the household electricity branch 311 corresponding to the rooftop water heater, they can send a power-on request through the user terminal 20; when a user is worried about the electric heater in the independent kitchen in the yard continuing to work after leaving home, they can send a power-off request for that electrical device 312 through the user terminal 20. Thus, different types of household electricity objects 31, whether household electricity branch 311 or electrical device 312, can all be uniformly mapped as power-on and power-off targets within the household electricity detection and control system 100, facilitating unified scheduling by the cloud control platform 10 and enabling the terminal devices 30 to execute on-site control under a unified logic. Furthermore, after receiving a request from the user terminal 20, the cloud control platform 10 generates corresponding control instructions based on the request type. When a power-on request is received, the cloud control platform 10 generates and issues a power-on control instruction; when a power-off request is received, the cloud control platform 10 generates and issues a power-off control instruction.

[0037] In one specific embodiment, to ensure that remote control requests from different household electricity users 31 are accurately routed to the corresponding terminal devices 30, the cloud management platform 10 pre-stores the correspondence between household electricity users 31 and terminal devices 30. Specifically, the cloud management platform 10 can set up an object correspondence table, which records the object identifiers corresponding to each of the multiple household electricity users 31, as well as the device identifiers of the terminal devices 30 corresponding to each object identifier. Specifically, in this embodiment, a household electricity user 31 can be a household electricity branch 311 or an electrical device 312. Therefore, the object correspondence table can record the correspondence between household electricity branch 311 and terminal devices 30, or the correspondence between electrical device 312 and terminal devices 30. For example, the rooftop water heater branch can be designated as object identifier A01 and associated with the device identifier T01 of the first terminal device 30; the kitchen heater in the yard can be designated as object identifier A02 and associated with the device identifier T02 of the second terminal device 30; the water pump in the corner pump room can be designated as object identifier A03 and associated with the device identifier T03 of the third terminal device 30. In this way, when different household electricity users 31 initiate control requests, the cloud-based management platform 10 can quickly locate the corresponding terminal device 30 based on the object identifier.

[0038] In one specific implementation, when a user initiates a control request for a target household electricity user 31 through the user terminal 20, the control request carries the identifier of the target household electricity user. Specifically, the user terminal 20 can display a list of names of multiple household electricity users 31 in the operation interface. After the user selects a certain object, the user terminal 20 writes the identifier of the target household electricity user corresponding to that object into the current control request and sends the control request to the cloud control platform 10. With this setting, the cloud control platform 10 no longer receives general power-on or power-off requests, but rather power-on or power-off requests specifically targeting a particular household electricity user 31.

[0039] For example, if a user wants to turn off the electric heater in the kitchen after leaving the house, the user selects the corresponding object of the kitchen electric heater through the user terminal 20 and sends a power-off request; similarly, if a user wants to turn on the rooftop water heater branch in advance, the user selects the corresponding object of the rooftop water heater branch through the user terminal 20 and sends a power-on request. Further, after receiving the control request, the cloud management platform 10 reads the target household electricity object identifier in the control request and searches for the terminal device 30 corresponding to the target household electricity object identifier in a pre-stored object correspondence table, thereby determining the target terminal device 30 for this control. Specifically, when the cloud management platform 10 reads object identifier A02, it searches for the device identifier T02 corresponding to object identifier A02 in the object correspondence table, thereby determining the second terminal device 30 as the target terminal device 30 for this control; when the cloud management platform 10 reads object identifier A01, it searches for the device identifier T01 corresponding to object identifier A01 in the object correspondence table, thereby determining the first terminal device 30 as the target terminal device 30 for this control.

[0040] After identifying the target terminal device 30, the cloud-based management platform 10 generates and sends a management command to the target terminal device 30. Specifically, the management command carries a target household electricity object identifier and a control type field. The target household electricity object identifier enables the target terminal device 30 to confirm the specific household electricity object 31 targeted by this control, and the control type field indicates whether the control is a power-on or power-off control. Upon receiving the management command, the target terminal device 30 first identifies the corresponding household electricity object 31 based on the target household electricity object identifier, and then executes the corresponding power-on or power-off control based on the control type field. By confirming the object before executing the action, the problem of confused control objects or incorrect control actions being applied to the wrong object can be avoided on the terminal side.

[0041] For example, after receiving a control command containing object identifier A02 and a power-off control type field, the second terminal device 30 first parses object identifier A02 and confirms in its locally stored object information that the object identifier corresponds to the electrical device 312, the kitchen electric heater. After confirming the object, it then disconnects the power supply circuit containing the electric heater according to the power-off control type field. As another example, after receiving a control command containing object identifier A01 and a power-on control type field, the first terminal device 30 first confirms that object identifier A01 corresponds to the rooftop water heater branch circuit 311, a household electrical branch circuit. Then, according to the power-on control type field, it connects the water heater branch circuit. After completing the corresponding power-on or power-off control, the target terminal device 30 continues to acquire the execution result of the control and the on / off status after execution, and generates a control confirmation record corresponding to the control command. Since the control command already includes the target household electricity user identifier and control type fields, the target terminal device 30 can clearly associate the execution result and on / off status with the corresponding target household electricity user 31 when generating the control confirmation record. Subsequently, the target terminal device 30 uploads the control confirmation record to the cloud control platform 10; if a communication failure occurs before the upload is complete, it is saved locally and uploaded first after communication is restored.

[0042] After receiving the control confirmation record, the cloud-based management platform 10 determines which household electricity user 31 corresponds to the returned result based on the corresponding target household electricity user identifier. Then, combining the execution result and on / off status, it updates the management status of that household electricity user 31. In this way, the control object selected by the user when initiating the request through the user terminal 20, the target terminal device 30 found in the cloud, the actual on-site object executed by the target terminal device 30, and the object to which the final update status is applied in the cloud are always the same household electricity user 31, thus forming a complete one-to-one correspondence closed loop.

[0043] For example, in a scenario where a kitchen heater in a courtyard experiences a power outage, the user selects object identifier A02 through user terminal 20 and issues a power outage request. The cloud-based management platform 10 locates the second terminal device 30 based on object identifier A02. After receiving the management instruction carrying object identifier A02 and a power outage control type field, the second terminal device 30 first confirms that the controlled object is the kitchen heater in the courtyard, and then performs the disconnection operation. After execution, the second terminal device 30 generates a control confirmation record corresponding to object identifier A02 and uploads it to the cloud-based management platform 10. The cloud-based management platform 10 updates the management status of the kitchen heater in the courtyard based on object identifier A02 in the control confirmation record. Thus, the complete control process from user selection of object, cloud-based device location, terminal confirmation of object, on-site execution of control, to cloud-based status update is completed. Furthermore, in scenarios with multiple objects deployed in a distributed manner, this implementation method can also support the parallel access and independent control of multiple household electricity objects 31. For example, a user can initiate different control requests for the rooftop water heater branch, the kitchen heater in the yard, and the water pump in the corner pump room. The cloud-based management platform 10 can find the corresponding terminal device 30 in the object mapping table based on the target household electricity object identifier in each control request, and issue a control instruction carrying the target household electricity object identifier and control type field to the corresponding terminal device 30. Each terminal device 30 confirms the control object based on the object identifier it carries and executes the corresponding control. In this way, even if multiple household electricity objects 31 are scattered in different locations, the household electricity detection and management system 100 can still ensure that every control is accurately applied to the correct object.

[0044] In one specific embodiment, after completing the power-on or power-off control, the target terminal device 30 does not directly record the control as successful or unsuccessful. Instead, it continues to confirm the control process and the status of the on-site circuit after the control. Specifically, after executing the power-on or power-off control, the target terminal device 30 obtains control execution feedback and the status detection result of the power supply circuit where the target household electricity user 31 is located, and determines the execution result and the on / off status after execution based on these results. The control execution feedback reflects whether the control action inside the terminal device 30 has been completed, and the status detection result reflects the actual conduction status of the power supply circuit where the target household electricity user 31 is located after the control action is executed. The control execution feedback can be generated by the execution drive unit, relay drive unit, switch action feedback unit, or other feedback unit used to characterize the completion of the control action in the terminal device 30; the status detection result can be generated by the voltage detection unit, current detection unit, circuit continuity detection unit, or other detection unit used to characterize the current status of the power supply circuit in the terminal device 30.

[0045] To ensure a clear basis for determining the execution result, in this embodiment, the target terminal device 30 first determines the target on / off state corresponding to this control based on the control type field. Specifically, when the control type field indicates power-on control, the target terminal device 30 determines the target on / off state as power-on; when the control type field indicates power-off control, the target terminal device 30 determines the target on / off state as power-off. Subsequently, the target terminal device 30 compares the acquired status detection result with the target on / off state and, in conjunction with the control execution feedback, makes a judgment on the execution result of this control. Specifically, when the control execution feedback indicates that the control action is completed, and the status detection result is consistent with the target on / off state corresponding to the control type field, the target terminal device 30 determines the execution result as control completion; when the control execution feedback does not indicate that the control action is completed, or the status detection result is inconsistent with the target on / off state corresponding to the control type field, the target terminal device 30 determines the execution result as control incomplete.

[0046] For example, in a power outage scenario, a user sends a power-off request to the electric heater in the kitchen via user terminal 20. The cloud management platform 10 then sends a power-off control command to the corresponding target terminal device 30. After the target terminal device 30 performs the disconnection operation, it obtains relay action completion feedback as control execution feedback and obtains the continuity detection result of the power supply circuit where the electric heater is located as the status detection result. If the control execution feedback indicates that the disconnection action has been completed, and the status detection result indicates that the power supply circuit is in a disconnected state, then the target terminal device 30 determines the execution result as control completion and simultaneously determines the continuity state as a power outage state. Furthermore, when the control execution feedback does not indicate that the control action has been completed, or the status detection result is inconsistent with the target continuity state, the target terminal device 30 determines the execution result as control incomplete. For example, if the control execution feedback indicates that the disconnection action has been completed, but the status detection result still indicates that the power supply circuit is in a continuous state, for example, due to contact adhesion, abnormal wiring, or on-site circuit abnormalities causing the power not to be truly disconnected, then the target terminal device 30 also determines the execution result as control incomplete.

[0047] While determining the execution result, the target terminal device 30 also determines the on / off state after execution based on the status detection result. Specifically, when the status detection result indicates that the power supply circuit of the target household electricity object 31 is in a conductive state, the target terminal device 30 determines the on / off state as "power on"; when the status detection result indicates that the power supply circuit of the target household electricity object 31 is in a disconnected state, the target terminal device 30 determines the on / off state as "power off". In other words, the determination of the on / off state does not directly depend on whether the user initiates a power on request or a power off request, but directly depends on the actual detection result of the on-site power supply circuit after the control action is executed. In this way, the target terminal device 30 can distinguish between "what state should be reached" and "what state is actually reached", which facilitates more accurate status updates by the cloud management platform 10 in the future.

[0048] For example, in a power-on scenario, a user sends a power-on request to the rooftop water heater branch via user terminal 20. After the target terminal device 30 executes the connection operation, if the control execution feedback indicates that the connection action has been completed and the status detection result indicates that the corresponding power supply circuit is in a conducting state, then the target terminal device 30 determines the execution result as control completion and the on / off state as power-on. If the control execution feedback indicates that the connection action has been completed, but the status detection result indicates that the corresponding power supply circuit is still in a disconnected state, then the target terminal device 30 determines the execution result as control incomplete and the on / off state as power-off. As another example, in a power-off scenario, if the control execution feedback does not indicate that the disconnection action has been completed, but the status detection result indicates that the power supply circuit is already in a disconnected state, then the target terminal device 30 still determines the execution result as control incomplete and the on / off state as power-off. With this setting, the execution result reflects that the control action itself was incomplete, while the on / off state reflects that the current situation is a power-off state. Therefore, after receiving the control confirmation record, the cloud-based management platform 10 can know that the on-site status has changed and that there is an anomaly in the control process, thus avoiding misjudging "the on-site status just reached the target status" as "the control process was completed completely normally".

[0049] Furthermore, after the target terminal device 30 determines the execution result and on / off status, it writes both into the control confirmation record corresponding to this control command. Subsequently, the target terminal device 30 uploads the control confirmation record to the cloud control platform 10. If a communication anomaly occurs before the upload is complete, the record is first saved locally as described above, and then uploaded first after communication is restored. Upon receiving the control confirmation record, the cloud control platform 10 can distinguish between different scenarios based on the execution result and on / off status, such as "control action completed and on-site status meets target," "control action not completed," and "control action completed but on-site status does not meet target," thus providing a basis for subsequent updates to the control status of the target household electricity user 31.

[0050] In one specific embodiment, after the target terminal device 30 completes a power-on or power-off control and determines the execution result and on / off status corresponding to the control, it generates a control confirmation record corresponding to that control. To ensure that this control confirmation record can be accurately identified and retrieved during subsequent uploading, caching, re-uploading, and cloud status updates, the control confirmation record includes an instruction identifier, a household electricity object identifier, a terminal device identifier, an execution result field, an on / off status field, a record generation time field, and an upload flag field. Specifically, the instruction identifier identifies which control instruction corresponds to this control confirmation record; the household electricity object identifier identifies the household electricity object 31 targeted by this control; the terminal device identifier identifies the terminal device 30 that generated the control confirmation record; the execution result field records the execution result corresponding to this control; the on / off status field records the actual on / off status after the control is executed; the record generation time field records the time when the control confirmation record was generated; and the upload flag field indicates whether the control confirmation record has been successfully uploaded to the cloud management platform 10.

[0051] Furthermore, in this embodiment, the target terminal device 30 writes the execution result and on / off status corresponding to the same control command into the same control confirmation record. That is, for a specific power-on or power-off control, the target terminal device 30 does not generate two separate records to record the execution result and on / off status, but instead merges these two pieces of information into a single control confirmation record. With this setting, a single control action corresponds to only one result record at the record level, thus avoiding the problem of multiple result information for the same control being scattered and difficult to match during subsequent uploads or re-uploads. For example, in a specific scenario, a user sends a power-off request to the kitchen heater in the yard through the user terminal 20. The cloud control platform 10 issues a power-off control command with the instruction identifier C20260422001 to the corresponding target terminal device 30. The household electricity object identifier corresponding to this command is A02, and the target terminal device identifier is T02. After the target terminal device 30 executes the power-off control, it determines that the execution result is control completion and the on / off status is power-off. At this time, the target terminal device 30 generates a control confirmation record, which includes: instruction identifier C20260422001, household electricity object identifier A02, terminal device identifier T02, execution result field "control completed", on / off status field "power off status", record generation time field, and upload flag field.

[0052] In one specific embodiment, after the target terminal device 30 generates the control confirmation record, it typically attempts to upload the control confirmation record to the cloud management platform 10. If a communication anomaly occurs during the upload process, or if a communication anomaly is detected before the upload begins, the target terminal device 30 sets the upload flag field of the control confirmation record to an unuploaded state. Further, in this embodiment, the target terminal device 30 is equipped with a local storage unit. The local storage unit is divided into a control record area and an electricity consumption data record area. The control record area is used to store control confirmation records that have not yet been successfully uploaded or need to be retained locally; the electricity consumption data record area is used to store electricity consumption data continuously collected during the communication anomaly but not yet uploaded. That is, in this embodiment, control confirmation records and ordinary electricity consumption data are stored in separate partitions, rather than all mixed in the same storage area. With this setting, after communication is restored, the target terminal device 30 can first extract the control confirmation record from the control record area and then extract the ordinary electricity consumption data from the electricity consumption data record area, thus matching the subsequent processing logic of prioritizing the upload of control confirmation records.

[0053] For example, in a scenario where a kitchen heater experiences a power outage, just as the target terminal device 30 generates the corresponding control confirmation record, bidirectional data transmission between the 4GCat.1 communication module 32 and the cloud management platform 10 is interrupted, causing the control confirmation record to fail to upload. At this point, the target terminal device 30 saves the control confirmation record to the control record area and sets the upload flag to the "not uploaded" state. Simultaneously, during the continued communication anomaly, the target terminal device 30 continues to collect current, voltage, power, or conduction status data of the power supply circuit where the heater is located, and saves this unuploaded power consumption data to the power consumption data record area. In this way, although the communication link is interrupted, the result information of this remote power outage control is not lost, thus completing a local retention loop of the control result in abnormal scenarios.

[0054] In one specific embodiment, the aforementioned communication anomaly is limited to an interruption of bidirectional data transmission between the target terminal device 30 and the cloud management platform 10. Further, when the target terminal device 30 detects the restoration of bidirectional data transmission between the 4GCat.1 communication module 32 and the cloud management platform 10, it initiates a communication recovery upload process. In this communication recovery upload process, the target terminal device 30 first scans the control record area in its local storage unit to find control confirmation records with an upload flag indicating they are not uploaded, and prioritizes uploading these control confirmation records to the cloud management platform 10. After confirming that no control confirmation records in the control record area are not yet uploaded, the target terminal device 30 then scans the electricity data record area and uploads the ordinary electricity data collected during the communication anomaly but not yet uploaded to the cloud management platform 10.

[0055] For example, in a scenario where a kitchen heater experiences a power outage, communication is restored after 30 minutes. After detecting the restoration of bidirectional data transmission, the target terminal device 30 first reads the corresponding power outage control confirmation record from the control record area and prioritizes its upload to the cloud management platform 10. Once this control confirmation record is uploaded, it then reads the accumulated current, voltage, and power data from the power consumption data record area during the communication outage and uploads it to the cloud management platform 10. Thus, the cloud management platform 10 can prioritize recognizing the power outage control result without delaying confirmation due to the priority re-upload of ordinary monitoring data, thereby completing the priority re-upload closed loop after communication restoration. If the target terminal device 30 finds control confirmation records with an unuploaded flag field while scanning the control record area, it maintains the current recovery upload process in the control record upload stage without switching to the power consumption data upload stage. Only after all control confirmation records in the control record area have been successfully uploaded and their flags updated does the target terminal device 30 enter the scanning and upload stage of the power consumption data record area.

[0056] In one specific embodiment, during the aforementioned communication recovery upload process, the target terminal device 30 does not simply upload records according to the general category order of "control confirmation records first, then power consumption data records." Instead, after forming a set of records to be uploaded, it calculates the corresponding upload priority value P_i for each record and uploads them in descending order of upload priority value P_i. The records to be uploaded here include control confirmation records and power consumption data records. Further, for each record to be uploaded, the target terminal device 30 reads the record category, execution result, and generation time of that record, and determines the corresponding control confirmation identifier C_i, incomplete identifier U_i, and generation time t_i accordingly. If the i-th record to be uploaded is a control confirmation record, C_i is set to 1; if the i-th record to be uploaded is a power consumption data record, C_i is set to 0. U_i is set to 1 only when the i-th record to be uploaded is a control confirmation record, and the execution result in that control confirmation record indicates that the corresponding control instruction has not been completed; otherwise, U_i is set to 0.

[0057] Furthermore, after obtaining C_i and U_i, the target terminal device 30 calculates the upload priority value P_i of the i-th record to be uploaded according to the following expression:

[0058] P_i=2×C_i+U_i

[0059] Wherein, P_i is the upload priority value of the i-th record to be uploaded, C_i is the control confirmation identifier, and U_i is the incomplete identifier. Specifically, in this embodiment, the records to be uploaded have at least the following three priority requirements during the recovery upload phase: The first type is control confirmation records of incomplete control, which correspond to situations where remote on / off control is still incomplete or abnormal, and has the highest priority for user confirmation of control risks and timely cloud identification of abnormal states; the second type is control confirmation records of completed control, which, although indicating that the control process is relatively normal, is still directly related to the on / off control result just initiated by the user, and should be prioritized over ordinary monitoring data upload; the third type is ordinary electricity consumption data records, which are mainly used to restore historical operating information during communication anomalies, and their timeliness is usually lower than that of control result confirmation. Therefore, the upload order target determined in this embodiment is: control confirmation records of incomplete control have the highest priority, control confirmation records of completed control have the second highest priority, and ordinary electricity consumption data records have the third highest priority.

[0060] Based on the above three-layer upload rules, further, "whether it is a control confirmation record" is abstracted as a control confirmation identifier C_i, and "whether it is an incomplete control confirmation record" is abstracted as an incomplete identifier U_i. Since ordinary electricity data records do not belong to control confirmation records, their C_i is 0 and U_i is 0; completed control confirmation records belong to control confirmation records but not incomplete records, so their C_i is 1 and U_i is 0; incomplete control confirmation records belong to both control confirmation records and incomplete records, so their C_i is 1 and U_i is 1. To ensure a stable numerical distinction among the three types of records, this embodiment sets "whether it is a control confirmation record" as the basic priority level and assigns it a weight of 2; then, "whether it is an incomplete record" is set as an additional priority level for further distinction within control confirmation records and assigns it a weight of 1. Thus, the upload priority value expression P_i = 2 × C_i + U_i is obtained. After calculation according to the above expression, when the i-th record to be uploaded is a regular electricity consumption data record, P_i=0; when the i-th record to be uploaded is a control confirmation record that has been completed, P_i=2; and when the i-th record to be uploaded is a control confirmation record that has not been completed, P_i=3. Therefore, the natural order is: "Control confirmation records that have not been completed are uploaded first, control confirmation records that have been completed are uploaded later, and regular electricity consumption data records are uploaded last."

[0061] For example, in a specific scenario, a target terminal device 30 accumulates four records to be uploaded during a communication anomaly. The first record, R1, is a control confirmation record corresponding to the power outage control of the kitchen heater in the courtyard, and the execution result is control incomplete. The second record, R2, is a control confirmation record corresponding to the power on / off control of the rooftop water heater branch, and the execution result is control completed. The third record, R3, is a current monitoring data collected during the communication anomaly. The fourth record, R4, is a voltage monitoring data collected during the communication anomaly. After communication is restored, the target terminal device 30 calculates the upload priority value for R1 to R4 respectively. R1's P_1=3, R2's P_2=2, and R3 and R4's P_3=P_4=0. Therefore, the upload order should be R1 first, R2 second, and R3 and R4 last. When different records to be uploaded have the same upload priority value P_i, they are uploaded in order of their generation time t_i from earliest to latest. By sorting by upload priority first and then by generation time, the upload order can meet the requirements of prioritizing control confirmation records and giving higher priority to incomplete control, as well as the requirement of restoring similar records in chronological order.

[0062] In one specific embodiment, after receiving the control confirmation record uploaded by the target terminal device 30, the cloud-based management platform 10 does not directly update the target household electricity object 31 corresponding to this control to a power-on or power-off state. Instead, it combines the execution result and power-on / off state in the control confirmation record with the target power-on / off state corresponding to this control request to determine the control status of the target household electricity object 31 before performing a status update. In other words, the status update on the cloud side is not based solely on "what the user requested" or solely on "the terminal returned a single result," but rather on the correspondence between "target status—execution result—actual status" to complete the status confirmation. Specifically, when the execution result in the control confirmation record indicates that the corresponding control instruction has been executed, and the on / off status in the control confirmation record is consistent with the target on / off status corresponding to this control request, the cloud control platform 10 updates the control status of the target household electricity user 31 to the status corresponding to the on / off status; when the execution result in the control confirmation record indicates that the corresponding control instruction has not been executed, or the on / off status in the control confirmation record is inconsistent with the target on / off status corresponding to this control request, the cloud control platform 10 does not directly update the target household electricity user 31 to the power-on or power-off status, but updates its control status to the pending confirmation status.

[0063] In one specific embodiment, to avoid inconsistent state update logic and implementation due to relying solely on textual judgments of execution results and on / off states, the aforementioned two judgment conditions—"whether the execution result indicates control completion" and "whether the actual on / off state is consistent with the target on / off state"—are further converted into a unified state confirmation value Q_m. The control status of the corresponding target household electricity user 31 is then updated based on the state confirmation value Q_m. The calculation expression is as follows:

[0064] Q_m = E_m × (1 - |G_m - S_m|)

[0065] Wherein, Q_m is the status confirmation value corresponding to the m-th control instruction; E_m is the execution completion flag, which is 1 when the execution result of the m-th control instruction indicates that the control instruction has been completed, otherwise E_m=0; G_m is the target on / off status flag, which is 1 when the control request corresponding to the m-th control instruction is a power-on request, and 0 when the control request corresponding to the m-th control instruction is a power-off request; S_m is the on / off status flag, which is 1 when the on / off status corresponding to the m-th control instruction is a power-on status, and 0 when the on / off status corresponding to the m-th control instruction is a power-off status.

[0066] It should be noted that the above expression is not derived from the physical circuit model, but rather from the mathematical expression of the judgment rules followed by the cloud management platform 10 when updating the status of the target household electricity object 31. Specifically, when updating the control status of the target household electricity object 31, the cloud management platform 10 only focuses on two issues: first, whether the current control command has been executed; and second, whether the actual on / off state after execution is consistent with the target on / off state that the current control aims to achieve. Only when both of these conditions are met will the cloud management platform 10 update the target household electricity object 31 to a definite on or off state; otherwise, the cloud management platform 10 updates it to a pending confirmation state. Based on this judgment approach, this embodiment abstracts "execution completed" as an execution completion identifier E_m, and "whether the target state is consistent with the actual state" as 1-|G_m-S_m|, and then multiplies the two to obtain the status confirmation value Q_m. Since both G_m and S_m represent states in a binary manner, with power on being recorded as 1 and power off as 0, 1 - |G_m - S_m| is 1 when the actual on / off state matches the target on / off state; and 1 - |G_m - S_m| is 0 when the actual on / off state does not match the target on / off state. Multiplying E_m by 1 - |G_m - S_m|, Q_m is only 1 when both "execution completed" and "state consistent" are met; otherwise, Q_m is 0. Thus, the aforementioned cloud state update rule is transformed into a unified binary judgment result, facilitating direct invocation by the cloud management platform 10 in its program implementation.

[0067] In a specific implementation process, after receiving the control confirmation record corresponding to the m-th control instruction, the cloud-based management platform 10 first retrieves the original control task information corresponding to the control instruction based on the instruction identifier, reads the control request type, and determines the target on / off state corresponding to the control instruction. If the control request corresponding to the control instruction is a power-on request, G_m is set to 1; if the control request corresponding to the control instruction is a power-off request, G_m is set to 0. Subsequently, the cloud-based management platform 10 reads the execution result field and the on / off state field from the control confirmation record, and determines the value of E_m based on the execution result field and the value of S_m based on the on / off state field. After determining the values ​​of E_m, G_m, and S_m, the cloud-based management platform 10 substitutes the values ​​into the above expressions to calculate the state confirmation value Q_m, and performs subsequent state updates based on Q_m.

[0068] For example, in a specific scenario, a user sends a power-on request to the household electricity branch 311 corresponding to the rooftop water heater branch via user terminal 20. The cloud management platform 10 issues a power-on control command to the corresponding target terminal device 30. After the target terminal device 30 performs the connection operation, it returns a control confirmation record, where the execution result is control completed and the on / off status is "powered on". At this time, the cloud management platform 10 determines G_m=1 based on the power-on request, E_m=1 based on the execution result in the control confirmation record, and S_m=1 based on the on / off status in the control confirmation record. Substituting these values ​​into the expression, we get Q_m=1. Therefore, the cloud management platform 10 updates the management status of the household electricity object 31 corresponding to the rooftop water heater branch to "powered on". For example, in a scenario where a kitchen heater in the yard experiences a power outage, if the returned control confirmation record indicates that the control was completed, but the on / off status remains "powered," then G_m=0, E_m=1, S_m=1. Substituting these values ​​into the expression yields Q_m=0. In this case, the cloud management platform 10 does not directly update the heater to a power-off state, but instead updates its control status to a pending confirmation state. As another example, if a user issues a power outage request to a water pump in a corner pumping station, and the target terminal device 30 returns a control confirmation record indicating that the control was not completed, but the on / off status remains "power-off," then G_m=0, E_m=0, S_m=0. Substituting these values ​​into the expression, Q_m remains 0. In this case, the cloud management platform 10 still updates the control status of the water pump to a pending confirmation state, instead of directly updating it to a power-off state.

[0069] Furthermore, in this embodiment, Q_m has only two possible values. When Q_m=1, the cloud management platform 10 updates the control status of the target household electricity object 31 to the status corresponding to the on / off state; if S_m=1 at this time, it updates to the on state; if S_m=0 at this time, it updates to the off state. When Q_m=0, the cloud management platform 10 updates the control status of the target household electricity object 31 to the pending confirmation state. That is to say, the pending confirmation state corresponds to all situations that "do not meet the requirements of execution completion and status consistency", which includes at least two situations: the first situation is that the execution result indicates that the control is not completed; the second situation is that although the execution result indicates that the control is completed, the actual on / off state is inconsistent with the target on / off state. By uniformly classifying these two types of situations into the pending confirmation state, the cloud management platform 10 can handle abnormal control results with a consistent standard, while reserving an interface for subsequent reconfirmation, re-issuance of control, or prompting the user for manual inspection.

[0070] In a specific implementation process, the cloud-based management platform 10 can also save Q_m along with the corresponding instruction identifier, household electricity object identifier, and record generation time to the cloud log for subsequent traceability of control results. For example, when a user queries the control history of a certain household electricity object 31 within a certain time period, the cloud-based management platform 10 can directly distinguish which controls have reached a definite state and which controls have entered a pending confirmation state based on the saved Q_m value, thereby improving the traceability of the household electricity detection and management system 100 in abnormal scenarios.

[0071] In one specific embodiment, a method for detecting and controlling household electricity consumption based on a 4GCat.1 module is provided, which is applied to the aforementioned household electricity consumption detection and control system 100, and includes the following steps:

[0072] S10. After selecting a household electricity object 31 through user terminal 20, the user sends a power-on or power-off request on user terminal 20. After the control request is sent to cloud control platform 10, cloud control platform 10 reads the target household electricity object identifier carried in the control request and finds the target terminal device 30 corresponding to the target household electricity object 31 in the pre-stored correspondence between household electricity objects 31 and terminal devices 30. Subsequently, cloud control platform 10 generates the corresponding control command and sends the control command to target terminal device 30 through the 4GCat.1 communication link corresponding to target terminal device 30. For example, if the user is worried about the electric heater in the independent kitchen in the yard continuing to work after leaving, they can select the corresponding electrical device 312 through user terminal 20 and send a power-off request; or, for example, if the user wants to turn on the roof water heater branch in advance before returning home, they can select the corresponding household electricity branch 311 through user terminal 20 and send a power-on request. This completes the first closed loop, from the user selecting the control object to the cloud locating and executing the device, and then to the cloud issuing control tasks.

[0073] S20. After receiving the control command, the target terminal device 30 first confirms the household electricity user 31 targeted by this control, and then executes the corresponding power-on or power-off control according to the control type in the control command. After completing the control action, the target terminal device 30 further obtains the control execution feedback and the status detection result of the power supply circuit where the target household electricity user 31 is located, and determines the execution result of this control and the on / off status after execution accordingly. Then, the target terminal device 30 writes the execution result and on / off status corresponding to this control into the same control confirmation record. For example, in the scenario of a power outage of an electric heater in a kitchen in the yard, after receiving the power-off control command, the target terminal device 30 performs a disconnection operation on the power supply circuit where the electric heater is located; after execution, if the control action has been completed and the power supply circuit is detected to be in a disconnected state, the execution result is determined as control completion, the on / off status is determined as power off state, and a corresponding control confirmation record is generated. For example, in a scenario where the rooftop water heater branch is powered on, if the control action has been completed and the power supply circuit is detected to be in a conductive state, the execution result is determined as control completion, the on / off state is determined as power-on state, and a corresponding control confirmation record is generated. This completes the second-stage closed loop, from issuing commands from the cloud to executing control on-site and then generating a result record.

[0074] S30. If a communication anomaly occurs after the target terminal device 30 generates a control confirmation record but before it is successfully uploaded to the cloud management platform 10, the target terminal device 30 will not discard the control confirmation record, but will instead save it in its local storage unit. Furthermore, the target terminal device 30 can write the control confirmation record to the control record area in its local storage unit and set its upload flag to an unuploaded state. Simultaneously, during the communication anomaly, the target terminal device 30 continues to collect ordinary electricity consumption data from the target household electricity user 31 and saves any unuploaded electricity consumption data in the electricity consumption data record area of ​​its local storage unit. In this way, although the communication link is interrupted, the result information of this remote control is not lost, thus completing the local retention loop of the control result in an abnormal scenario.

[0075] S40. When the target terminal device 30 detects that bidirectional data transmission between the 4GCat.1 communication module 32 and the cloud management platform 10 has been restored, it initiates a communication restoration upload process. In this communication restoration upload process, the target terminal device 30 first scans the control record area in the local storage unit, searches for control confirmation records with the upload flag set to "not uploaded," and prioritizes uploading these control confirmation records to the cloud management platform 10. After finding no control confirmation records in the control record area that are not yet uploaded, the target terminal device 30 then scans the electricity data record area and uploads the ordinary electricity data collected during the communication anomaly but not yet uploaded to the cloud management platform 10. In one embodiment, an upload priority value P_i can be calculated for the records to be uploaded, and uploads can be performed in descending order of upload priority value P_i to ensure that control confirmation records with incomplete control are uploaded first, control confirmation records with completed control are uploaded second, and ordinary electricity data records are uploaded last. This completes the priority retransmission closed loop after communication restoration.

[0076] After receiving the control confirmation record uploaded by the target terminal device 30, the cloud-based management platform 10 determines the corresponding management request and the target household electricity user 31 based on the instruction identifier and household electricity user identifier corresponding to the control confirmation record. It then judges the execution result and on / off status in the control confirmation record in conjunction with the target on / off status corresponding to the management request. When the execution result indicates that the corresponding management instruction has been completed and the on / off status matches the target on / off status, the management status of the target household electricity user 31 is updated to the status corresponding to that on / off status. When the execution result indicates that the corresponding management instruction has not been completed, or the on / off status does not match the target on / off status, the management status of the target household electricity user 31 is updated to a pending confirmation status. In one embodiment, the above status update logic can also be uniformly expressed through a status confirmation value Q_m, thereby completing the cloud-based status confirmation closed loop.

[0077] The embodiments described above are merely examples of several implementations of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these modifications and improvements all fall within the scope of protection of this application.

Claims

1. A household electricity consumption detection and control system based on a 4GCat.1 module, characterized in that, It includes a cloud-based management and control platform, user terminals, and multiple terminal devices; each of the multiple terminal devices corresponds to a different household electricity user, which is a household electricity branch or electrical equipment; Each of the terminal devices is equipped with a 4GCat.1 communication module. Each of the terminal devices is used to collect electricity consumption data of the corresponding household electricity user and to transmit data bidirectionally with the cloud management platform through its respective 4GCat.1 communication module. The cloud-based management and control platform is used to respond to the management and control requests issued by the user terminal for the target household electricity user, and to issue management and control instructions to the target terminal device corresponding to the target household electricity user; The target terminal device is used to execute the corresponding power-on control or power-off control after receiving the control command, and generate a control confirmation record corresponding to the control command. The control confirmation record includes the execution result of the control command and the on / off status of the target household electricity user after executing the control command. The target terminal device is also used to locally save the control confirmation record when a communication anomaly occurs before the control confirmation record is uploaded, and upload the control confirmation record to the cloud management platform before the unuploaded electricity data after communication is restored, so that the cloud management platform updates the management status of the target household electricity user based on the execution result and the on / off status.

2. The household electricity consumption detection and control system based on the 4GCat.1 module according to claim 1, characterized in that, The control request is a power-on or power-off request for the target household electricity user; The control instructions include power-on control instructions corresponding to the power-on request, or power-off control instructions corresponding to the power-off request; The execution result includes whether control is completed or not. The on / off state includes a powered-on state or a powered-off state.

3. The household electricity detection and control system based on the 4GCat.1 module according to claim 2, characterized in that, The cloud-based management platform stores the correspondence between household electricity users and terminal devices; The cloud-based management platform is used to determine the corresponding target terminal device in the correspondence based on the target household electricity object identifier in the management request, and to send a management instruction carrying the target household electricity object identifier and control type field to the target terminal device; The target terminal device is used to identify the corresponding household electricity user based on the target household electricity user identifier, and to perform the corresponding power-on control or power-off control based on the control type field.

4. The household electricity detection and control system based on the 4GCat.1 module according to claim 3, characterized in that, The target terminal device is used to obtain control execution feedback and the status detection result of the power supply circuit where the target household electricity user is located after executing the power-on control or power-off control; When the control execution feedback indicates that the control action is completed, and the status detection result is consistent with the target on / off status corresponding to the control type field, the target terminal device determines the execution result as control completion; When the control execution feedback does not indicate that the control action is completed, or when the status detection result is inconsistent with the target on / off state, the target terminal device determines the execution result as control not completed. When the status detection result indicates that the power supply circuit is in a conducting state, the target terminal device determines the on / off state as a power-on state; When the status detection result indicates that the power supply circuit is in an open state, the target terminal device determines the on / off state as a power-off state.

5. The household electricity detection and control system based on the 4GCat.1 module according to claim 4, characterized in that, The control confirmation record includes an instruction identifier, a household electricity user identifier, a terminal device identifier, an execution result field, an on / off status field, a record generation time field, and an upload flag field. The target terminal device is used to write the execution result and connection / disconnection status corresponding to the same control command into the same control confirmation record, and when the communication abnormality occurs, to set the upload flag field of the control confirmation record to the non-uploaded state; The target terminal device is also used to save the control confirmation record to the control record area in the local storage unit, and to save the power consumption data collected during the communication anomaly but not yet uploaded to the power consumption data record area in the local storage unit.

6. The household electricity detection and control system based on the 4GCat.1 module according to claim 5, characterized in that, The communication anomaly is an interruption in bidirectional data transmission between the target terminal device and the cloud management platform; The target terminal device is used to initiate a communication recovery upload process after detecting the restoration of bidirectional data transmission between the 4GCat.1 communication module and the cloud management platform; In the first communication recovery upload process, the target terminal device first scans the control confirmation records in the control record area where the upload flag field is in an unuploaded state, and then uploads the scanned control confirmation records to the cloud management platform; After no control confirmation record with the upload flag field in the control record area is found to be in an unuploaded state, the target terminal device scans the electricity consumption data in the electricity consumption data record area for any unuploaded electricity consumption data and uploads the electricity consumption data to the cloud management platform.

7. The household electricity detection and control system based on the 4GCat.1 module according to claim 6, characterized in that, For the i-th record to be uploaded, the target terminal device calculates the corresponding upload priority value P_i and uploads the records in descending order of upload priority value P_i. The records to be uploaded include the control confirmation record and the power consumption data record, wherein: P_i=2×C_i+U_i In the formula: P_i is the upload priority value of the i-th record to be uploaded; C_i is the control confirmation identifier. When the i-th record to be uploaded is the control confirmation record, C_i=1; otherwise, C_i=0. U_i is the incomplete flag. When the i-th record to be uploaded is the control confirmation record and the execution result therein indicates that the corresponding control instruction has not been completed, U_i=1; otherwise, U_i=0. When different records to be uploaded have the same upload priority value P_i, the target terminal device uploads them in order from earliest to latest according to their generation time t_i, where t_i is the generation time of the i-th record to be uploaded.

8. The household electricity detection and control system based on the 4GCat.1 module according to claim 6, characterized in that, The cloud-based management platform is used to update the management status of the target household electricity user after receiving the control confirmation record, based on the execution result and on / off status in the control confirmation record and in conjunction with the target on / off status corresponding to the management request. When the execution result indicates that the control command has been executed and the on / off state is consistent with the target on / off state, the cloud control platform updates the control status of the target household electricity user to the state corresponding to the on / off state. When the execution result indicates that the control command has not been completed, or the on / off status is inconsistent with the target on / off status, the cloud control platform updates the control status of the target household electricity user to a pending confirmation status.

9. The household electricity detection and control system based on the 4GCat.1 module according to claim 8, characterized in that, For the m-th control instruction, the cloud-based control platform calculates the corresponding status confirmation value Q_m, and updates the control status of the target household electricity user based on the status confirmation value Q_m, wherein: Q_m = E_m × (1 - |G_m - S_m|) In the formula: Q_m is the status confirmation value corresponding to the m-th control instruction; E_m is the execution completion flag. When the execution result of the m-th control instruction indicates that the control instruction has been completed, E_m=1; otherwise, E_m=0. G_m is the target on / off status identifier. When the control request corresponding to the m-th control instruction is a power-on request, G_m=1; when the control request corresponding to the m-th control instruction is a power-off request, G_m=0. S_m is the on / off status identifier. When the on / off status corresponding to the m-th control command is the power-on state, S_m=1; when the on / off status corresponding to the m-th control command is the power-off state, S_m=0. When Q_m=1, the cloud management platform updates the management status of the target household electricity user to the status corresponding to the on / off status; When Q_m=0, the cloud-based management platform updates the management status of the target household electricity user to a pending confirmation status.

10. A method for detecting and controlling household electricity consumption based on a 4GCat.1 module, characterized in that, A home electricity consumption detection and control system is applied to a cloud-based management platform, user terminals, and multiple terminal devices, wherein the multiple terminal devices correspond to different home electricity users, and each terminal device is equipped with a 4GCat.1 communication module. The method includes: S10. In response to the control request issued by the user terminal for the target household electricity user, determine the target terminal device corresponding to the target household electricity user, and issue control instructions to the target terminal device; S20. Control the target terminal device to execute the corresponding power-on control or power-off control after receiving the control command, and generate a control confirmation record corresponding to the control command. The control confirmation record includes the execution result of the control command and the on / off status of the target household electricity user after executing the control command. S30. If a communication abnormality occurs before the control confirmation record is uploaded, control the target terminal device to locally save the control confirmation record. S40. After communication is restored, control the target terminal device to upload the control confirmation record to the cloud management platform before the power consumption data that has not been uploaded. S50. Control the cloud management platform to update the management status of the target household electricity user based on the execution result and on / off status in the control confirmation record.

Images