A monitoring method and system based on tag-lock collaboration

Abstract

This invention discloses a monitoring method and system based on tag-lock collaboration. The method includes: selecting the nearest smart light pole as a proxy light pole based on the signal strength of the smart light pole scanned by the guardian's tag, establishing a delegation relationship, and transferring the scanning task to the proxy light pole, causing the guardian's tag to enter a low-power broadcast mode; triggering a proxy switch by comparing the signal strength detected by different light poles during the child's movement; sending alarm information to the door lock and guardian's tag through a hierarchical multicast mechanism based on the result of the proxy light pole continuously monitoring the signal strength of the child's tag; and notifying relevant devices to deactivate the alarm and restore normal monitoring mode by optimizing the multicast path based on events such as the guardian finding the child or the light pole re-detecting the child. Using this invention, low-cost, seamless relay monitoring from indoor to outdoor public areas can be achieved, improving the accuracy and timeliness of alarms.

Description

Technical Field

[0001] This invention belongs to the field of smart door lock technology, and in particular to a monitoring method and system based on tag-based door lock collaboration. Background Technology

[0002] In the field of child safety monitoring, traditional area monitoring methods mainly rely on close parental supervision or single electronic devices (such as Bluetooth anti-lost devices). These methods have significant limitations: the former is labor-intensive and prone to negligence, while the latter is limited by short device communication distances and susceptible to environmental interference, making it impossible to achieve stable and continuous tracking in open environments such as communities and shopping malls. While some existing technologies attempt to use fixed nodes for positioning, these nodes often operate independently, lacking effective coordination mechanisms. This results in fixed monitoring ranges, poor continuity, and blind spots during child movement, making it impossible to accurately alert authorities before a child truly leaves the safe area. Summary of the Invention

[0003] The purpose of this invention is to provide a monitoring method and system based on tag-lock collaboration to overcome the shortcomings of the prior art, enabling low-cost, seamless relay monitoring from indoor to outdoor public areas, and improving the accuracy and timeliness of alarms.

[0004] One embodiment of this application provides a monitoring method based on tag-lock collaboration, the method comprising:

[0005] Proxy delegation establishment: Based on the signal strength of the smart light pole scanned by the guardian tag, the nearest light pole is selected as the proxy light pole, a delegation relationship is established, and the scanning task is transferred to the proxy light pole, so that the guardian tag enters the low power broadcast mode;

[0006] Dynamic relay detection: Based on the changes in signal strength detected by different lampposts during the child's movement, the system triggers a switch of proxy rights by comparing signal strength, thereby enabling automatic relay replacement of the proxy lamppost;

[0007] Intelligent alarm triggering: Based on the results of continuous monitoring of the child tag signal strength by the agent light pole, when the signal strength is consistently below the threshold, an alarm message is sent to the door lock and guardian tag through a hierarchical multicast mechanism;

[0008] Collaborative alarm deactivation: Based on events such as a guardian finding a child or a light pole detecting a child again, the alarm status is deactivated and normal monitoring mode is restored by optimizing the multicast path to notify relevant devices.

[0009] Optionally, the establishment of the proxy delegation includes:

[0010] Agent light pole selection: Based on the broadcast signal strength of each smart light pole within the range of the guardian's tag scanning, select the light pole with the strongest RSSI as the agent light pole;

[0011] Establishment of delegation relationship: Based on the delegation request sent by the guardian tag to the agent light pole, the agent light pole confirms and establishes the delegation relationship. The guardian tag stops actively scanning and switches to periodic broadcast mode.

[0012] Agent announcement multicast: Upon successful establishment of the delegation relationship, the agent light pole notifies the corresponding door lock via a multicast message carrying the child tag ID, and notifies all light poles via a multicast message carrying the light pole type identifier;

[0013] Task execution switch: Based on the established delegation relationship, the agent light pole begins to continuously scan for child tags, while the guardian tag only broadcasts a keep-alive signal periodically.

[0014] Optionally, the dynamic relay detection includes:

[0015] Signal strength monitoring: Based on the continuous scanning of the children's tag broadcast signal by each light pole, the detected signal strength value is recorded in real time;

[0016] Takeover condition judgment: Based on the difference between the signal strength detected by the candidate light pole and the signal strength of the previous agent light pole, the takeover process is triggered when the difference exceeds a preset threshold;

[0017] Agency handover: Based on the takeover request and confirmation response sent by the candidate light pole to the previous agent light pole, the agency handover is completed from the original light pole to the new light pole;

[0018] Switching information synchronization: Based on the successful switching of agency rights, the new agent light pole updates the agent light pole ID stored in the door lock via multicast and notifies all light poles of the change in agency relationship.

[0019] Optionally, the intelligent alarm triggering includes:

[0020] Distance event determination: Based on the continuous monitoring of the child tag signal strength by the agent light pole, when the signal strength is continuously lower than the threshold for a preset time, a child distance event is determined to have occurred.

[0021] Tiered alarm notification: Based on the determination of the distance event, the agent light pole triggers the door lock sound and light alarm through a multicast message carrying the child tag ID, and at the same time sends a guardian tag paging request to the light poles in the commonly used light pole set directly via Bluetooth or through limited multicast.

[0022] Global paging rollback: If no response confirmation is received within a preset time based on the limited multicast, the agent light pole switches to global multicast mode and sends a guardian tag paging request to all light poles;

[0023] Alarm information transmission: Based on the results of scanning the guardian tag broadcast signal on each light pole, alarm information is directly transmitted to the guardian tag via Bluetooth.

[0024] Optionally, the coordinated alarm cancellation includes:

[0025] Alarm clearance condition detection: The alarm clearance process is triggered when the guardian's tag is re-scanned and the child's tag is detected and the signal strength is higher than the threshold, or when any light pole re-detects the child's tag and the signal strength is higher than the threshold.

[0026] Alarm status clearing: Based on the event that the alarm clearance conditions are met, the light pole notifies the corresponding door lock to clear the alarm status via a multicast message carrying a child tag ID;

[0027] Optimized Guardian Notification: Based on the relative position of the detected light pole and the guardian tag, an alarm cancellation message is sent to the guardian tag via direct Bluetooth communication or through a limited multicast of commonly used light poles. If no response confirmation is received within a preset time after the limited multicast, the detected light pole switches to global multicast mode and sends a guardian tag paging request to all light poles. Based on the results of each light pole scanning the guardian tag broadcast signal, the alarm cancellation message is directly transmitted to the guardian tag via Bluetooth.

[0028] Normal mode restoration: After the alarm is cleared, the guardian tag re-enters the entrusted status, and the system returns to normal guardianship mode.

[0029] Optionally, the method also includes a common agent light pole set learning and optimization mechanism:

[0030] Historical data collection: Based on the multicast notifications received by the door lock from each agent light pole ID, record the number of agent times and time information for each light pole;

[0031] Commonly used set generation: Based on the statistical results of the proxy frequency of each light pole within a preset time period, select the top N light pole IDs with the highest proxy frequency to generate a commonly used proxy light pole set;

[0032] Limited multicast execution: Based on the establishment of a set of commonly used proxy poles, when announcing a proxy relationship, the proxy poles only send multicast messages to poles within the set, significantly reducing network load;

[0033] Dynamic update of the set: Based on the result of determining whether the new agent light pole ID belongs to the existing commonly used set, the set of commonly used agent light poles is dynamically updated and synchronized to the relevant light poles.

[0034] Another embodiment of this application provides a monitoring system based on tag-lock collaboration, the system comprising:

[0035] The module is used to establish a proxy delegation: based on the signal strength of the smart light pole scanned by the guardian tag, the nearest light pole is selected as the proxy light pole, a delegation relationship is established, and the scanning task is transferred to the proxy light pole, so that the guardian tag enters the low power broadcast mode;

[0036] The detection module is used for dynamic relay detection: based on the changes in signal strength detected by different lampposts during the child's movement, the module triggers the switching of proxy rights by comparing the signal strength, thereby realizing the automatic relay replacement of the proxy lamppost;

[0037] The trigger module is used for intelligent alarm triggering: based on the results of continuous monitoring of the child tag signal strength by the agent light pole, when the signal strength is continuously lower than the threshold, alarm information is sent to the door lock and guardian tag through a hierarchical multicast mechanism;

[0038] The alarm cancellation module is used for coordinated alarm cancellation: based on events such as a guardian finding a child or a light pole detecting a child again, it notifies relevant devices to cancel the alarm status and restore normal monitoring mode by optimizing the multicast path.

[0039] Another embodiment of this application provides a storage medium storing a computer program, wherein the computer program is configured to execute the method described in any of the preceding claims when running.

[0040] Another embodiment of this application provides an electronic device including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the method described in any of the preceding claims.

[0041] Compared with existing technologies, this invention provides a tag-based door lock collaborative monitoring method. Based on the signal strength of the smart light pole scanned by the guardian's tag, the nearest light pole is selected as a proxy light pole, establishing a delegation relationship and transferring the scanning task to the proxy light pole, causing the guardian's tag to enter a low-power broadcast mode. Based on the signal strength changes detected by different light poles during the child's movement, a proxy switch is triggered by comparing signal strength. Based on the proxy light pole's continuous monitoring of the child's tag signal strength, when the signal strength remains below a threshold, an alarm message is sent to the door lock and guardian's tag via a hierarchical multicast mechanism. Based on events such as the guardian finding the child or the light pole re-detecting the child, the relevant devices are notified to deactivate the alarm and restore normal monitoring mode by optimizing the multicast path. This enables low-cost, seamless relay monitoring from indoor to outdoor public areas, improving the accuracy and timeliness of alarms. Attached Figure Description

[0042] Figure 1 A hardware structure block diagram of a computer terminal for a tag-lock collaborative monitoring method provided in an embodiment of the present invention;

[0043] Figure 2 A flowchart illustrating a tag-based door lock collaborative monitoring method provided in an embodiment of the present invention;

[0044] Figure 3 This is a schematic diagram of a monitoring system based on tag-lock collaboration provided in an embodiment of the present invention. Detailed Implementation

[0045] The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and should not be construed as limiting the present invention.

[0046] The risk of children getting lost while playing in residential areas due to brief periods of inattention from guardians (such as nannies or elderly people) remains a constant. The mainstream solution is for children to wear smartwatches, which upload the child's location data to a cloud server, allowing parents to track them in real-time and trigger geofence alerts via a mobile app. However, smartwatches have high battery consumption and short battery life, and their reliance on cloud platforms makes reliability and timeliness uncertain.

[0047] The present invention first provides a monitoring method based on tag-lock collaboration, which can be applied to electronic devices, such as computer terminals, specifically ordinary computers.

[0048] The following detailed explanation uses a computer terminal as an example. Figure 1 This is a hardware structure block diagram of a computer terminal for a tag-based door lock collaborative monitoring method provided in an embodiment of the present invention. Figure 1 As shown, the computer device includes a processor, memory, and network interface connected via a system bus, wherein the memory may include non-volatile storage media and internal memory.

[0049] The non-volatile storage medium can store an operating system and a computer program. This computer program includes program instructions that, when executed, cause the processor to perform any tag-based door lock collaborative monitoring method.

[0050] The processor provides computing and control capabilities, supporting the operation of the entire computer device.

[0051] The internal memory provides an environment for the execution of computer programs in non-volatile storage media. When the computer program is executed by the processor, it enables the processor to execute any tag-based door lock collaborative monitoring method.

[0052] This network interface is used for network communication, such as sending assigned tasks. Those skilled in the art will understand that... Figure 1The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0053] It should be understood that the processor can be a Central Processing Unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among these, a general-purpose processor can be a microprocessor or any conventional processor.

[0054] See Figure 2 The present invention provides a monitoring method based on tag-lock collaboration, which may include the following steps:

[0055] S201, Proxy Delegation Establishment: Based on the signal strength of the smart light pole scanned by the guardian tag, the nearest light pole is selected as the proxy light pole, a delegation relationship is established, and the scanning task is transferred to the proxy light pole, causing the guardian tag to enter low-power broadcast mode; specifically, the proxy delegation establishment includes:

[0056] Agent light pole selection: Based on the broadcast signal strength of each smart light pole within the range of the guardian's tag scanning, select the light pole with the strongest RSSI as the agent light pole;

[0057] Establishment of delegation relationship: Based on the delegation request sent by the guardian tag to the agent light pole, the agent light pole confirms and establishes the delegation relationship. The guardian tag stops actively scanning and switches to periodic broadcast mode.

[0058] Agent announcement multicast: Upon successful establishment of the delegation relationship, the agent light pole notifies the corresponding door lock via a multicast message carrying the child tag ID, and notifies all light poles via a multicast message carrying the light pole type identifier;

[0059] Task execution switch: Based on the established delegation relationship, the agent light pole begins to continuously scan for child tags, while the guardian tag only broadcasts a keep-alive signal periodically.

[0060] The forwarding mechanism for multicast messages in proxy-announced multicast includes:

[0061] Router entry establishment: Based on the improved IGMP / PIM join message sent by the device, the router registers the device type identifier and ID information on the multicast forwarding table output interface;

[0062] Precise message matching: Based on the device type identifier and ID information carried in the multicast message, the router forwards the message only to the matching outgoing interface;

[0063] Message classification and processing: Based on the completeness of the identification field in the multicast message, the router performs differentiated processing, such as forwarding only to a specific light pole, forwarding to all light poles, or forwarding to a specific door lock.

[0064] S202, Dynamic relay detection: Based on the changes in signal strength detected by different lampposts during the child's movement, a proxy switching is triggered by comparing signal strength, realizing automatic relay replacement of the proxy lamppost; specifically, the dynamic relay detection includes:

[0065] Signal strength monitoring: Based on the continuous scanning of the children's tag broadcast signal by each light pole, the detected signal strength value is recorded in real time;

[0066] Takeover condition judgment: Based on the difference between the signal strength detected by the candidate light pole and the signal strength of the previous agent light pole, the takeover process is triggered when the difference exceeds a preset threshold;

[0067] Agency handover: Based on the takeover request and confirmation response sent by the candidate light pole to the previous agent light pole, the agency handover is completed from the original light pole to the new light pole;

[0068] Switching information synchronization: Based on the successful switching of agency rights, the new agent light pole updates the agent light pole ID stored in the door lock via multicast and notifies all light poles of the change in agency relationship.

[0069] The conflict resolution mechanism for the transfer of agency includes:

[0070] Multi-candidate identification: When multiple light poles simultaneously meet the takeover conditions, each candidate light pole sends a takeover request to the forward agent light pole;

[0071] Optimal selection: Based on the comparison results of the signal strength of each candidate light pole received by the previous agent light pole, select the light pole with the highest signal strength for confirmation response;

[0072] Single handover: Based on the previous agent light pole, a takeover confirmation is sent to the optimal candidate light pole to ensure that only one light pole obtains the agent right at any given time.

[0073] S203, Intelligent Alarm Trigger: Based on the results of continuous monitoring of the child tag signal strength by the agent light pole, when the signal strength remains below a threshold, an alarm message is sent to the door lock and guardian tag via a hierarchical multicast mechanism; specifically, the intelligent alarm trigger includes:

[0074] Distance event determination: Based on the continuous monitoring of the child tag signal strength by the agent light pole, when the signal strength is continuously lower than the threshold for a preset time, a child distance event is determined to have occurred.

[0075] Tiered alarm notification: Based on the determination of the distance event, the agent light pole triggers the door lock sound and light alarm through a multicast message carrying the child tag ID, and at the same time sends a guardian tag paging request to the light poles in the commonly used light pole set directly via Bluetooth or through limited multicast.

[0076] Global paging rollback: If no response confirmation is received within a preset time based on the limited multicast, the agent light pole switches to global multicast mode and sends a guardian tag paging request to all light poles;

[0077] Alarm information transmission: Based on the results of scanning the guardian tag broadcast signal on each light pole, alarm information is directly transmitted to the guardian tag via Bluetooth.

[0078] S204, Collaborative Alarm Deactivation: Based on events such as a guardian finding a child or a light pole detecting a child again, the alarm status is deactivated and normal monitoring mode is restored by optimizing the multicast path. Specifically, the collaborative alarm deactivation includes:

[0079] Alarm clearance condition detection: The alarm clearance process is triggered when the guardian's tag is re-scanned and the child's tag is detected and the signal strength is higher than the threshold, or when any light pole re-detects the child's tag and the signal strength is higher than the threshold.

[0080] Alarm status clearing: Based on the event that the alarm clearance conditions are met, the light pole notifies the corresponding door lock to clear the alarm status via a multicast message carrying a child tag ID;

[0081] Optimized Guardian Notification: Based on the relative position of the detected light pole and the guardian tag, an alarm cancellation message is sent to the guardian tag via direct Bluetooth communication or through a limited multicast of commonly used light poles. If no response confirmation is received within a preset time after the limited multicast, the detected light pole switches to global multicast mode and sends a guardian tag paging request to all light poles. Based on the results of each light pole scanning the guardian tag broadcast signal, the alarm cancellation message is directly transmitted to the guardian tag via Bluetooth.

[0082] Normal mode restoration: After the alarm is cleared, the guardian tag re-enters the entrusted status, and the system returns to normal guardianship mode.

[0083] Furthermore, the method also includes a learning and optimization mechanism for commonly used agent light pole sets:

[0084] Historical data collection: Based on the multicast notifications received by the door lock from each agent light pole ID, record the number of agent times and time information for each light pole;

[0085] Commonly used set generation: Based on the statistical results of the proxy frequency of each light pole within a preset time period, select the top N light pole IDs with the highest proxy frequency to generate a commonly used proxy light pole set;

[0086] Limited multicast execution: Based on the establishment of a set of commonly used proxy poles, when announcing a proxy relationship, the proxy poles only send multicast messages to poles within the set, significantly reducing network load;

[0087] Dynamic update of the set: Based on the result of determining whether the new agent light pole ID belongs to the existing commonly used set, the set of commonly used agent light poles is dynamically updated and synchronized to the relevant light poles.

[0088] This invention constructs an autonomous, distributed IoT network within a residential community by using Bluetooth tags carried by children and guardians, utilizing fixed light poles and door locks of each household. By having fixed light poles act as proxies and take over the continuous scanning tasks performed by mobile guardian tags, the guardian tags are kept in an ultra-low-power broadcast state most of the time, achieving a battery life of several weeks or even months. By learning and distributing a "set of commonly used proxy light poles" through door locks, the communication of proxy light poles is upgraded from "global multicast" to "precise, limited-range multicast," significantly reducing network load and avoiding resource waste from irrelevant nodes. An optimized set of commonly used proxy light poles and a mechanism for switching back to global multicast in case of limited multicast failure are designed, improving system response speed and reliability. Solution:

[0089] I. Prerequisites:

[0090] Child tag: A Bluetooth tag carried by a child, supporting broadcast mode and sending broadcast signals periodically.

[0091] Guardian Tag: A Bluetooth tag carried by a guardian (such as a nanny). It supports scanning and broadcasting modes. In its initial state, the guardian tag scans for broadcasting signals from the child tag and the community light poles at high frequency.

[0092] Smart light poles: Fixedly deployed within the community, integrating Bluetooth and network modules, supporting scanning and broadcast modes, and possessing communication and computing capabilities. They join and listen to multicast group G (using a unified multicast group address across the network, such as 229.1.1.1) for communication between light poles. When a light pole sends an IGMP join message with multicast group 229.1.1.1, it adds a light pole type identifier "Post" and its own light pole ID (e.g., PostA) to the original IGMP message structure. Simultaneously, to achieve network-wide forwarding of multicast messages, the PIM join message is also improved, adding a light pole type identifier "Post" and its own light pole ID (e.g., PostA) to the original PIM join message structure.

[0093] Smart door lock: Installed on the resident's door, integrating a network module. It joins and listens to multicast group G (using a unified multicast group address across the network, such as 229.1.1.1) for communication between the light pole and the door lock. When the door lock sends an IGMP join message with multicast group 229.1.1.1, it adds a corresponding child tag ID to the original IGMP message structure. Simultaneously, to achieve network-wide forwarding of multicast messages, the PIM join message is also improved, adding a corresponding child tag ID to the original PIM join message structure.

[0094] Multicast routers are responsible for receiving IGMP and PIM join messages from light poles or door locks, generating (*, G) entries, and registering the ID information from the received IGMP or PIM join messages at each outgoing interface of the entry. This ID information includes the light pole type identifier "Post" and the light pole ID or its corresponding child tag ID. Only messages matching the light pole type identifier "Post" and the light pole ID or its corresponding child tag ID at the outgoing interface will be forwarded by the router.

[0095] 1) If the forwarding message carries a combined field of the pole type identifier "Post" and the pole ID (e.g., PostA), the router will check the interface for matching. If both the pole type identifier "Post" and the pole ID match, the multicast message will be forwarded from the outgoing interface, so only pole A will receive the message. If the forwarding message only carries the pole type identifier "Post" but does not contain the pole ID, the router will check the interface for matching. If the pole type identifier "Post" matches, the multicast message will be forwarded from the outgoing interfaces of all poles, so all poles will receive the message.

[0096] 2) If the forwarded message carries the corresponding child tag ID, the router will query the interface for matching. If the corresponding child tag ID is matched, the multicast message will be forwarded from the outgoing interface. In this way, only the door locks bound to the corresponding child tag ID will receive the message.

[0097] 3) If the forwarded message does not carry the light pole type identifier "Post" and the light pole ID, nor does it carry the corresponding child tag ID, it does not match the forwarding table of the router's outgoing interface and the message is directly discarded.

[0098] II. Solution Steps:

[0099] 1. Agency Process:

[0100] Each smart light pole's Bluetooth module broadcasts data packets at a fixed frequency, containing the device type ("Post") and a unique ID. In scanning mode, the guardian tag receives and parses these broadcast packets. If the device type is Post, the guardian tag considers it to have found a usable "proxy light pole." If multiple light poles are found simultaneously, the light pole with the strongest RSSI signal (closest to the guardian tag) is selected as the proxy light pole. The guardian tag sends a "delegation request" message to proxy light pole A, containing its own guardian tag ID and child tag ID. Upon receiving the request, light pole A replies with a "delegation confirmation" message. Upon receiving the confirmation message, the guardian tag immediately stops scanning for the child tag, switches to a low-power state, and periodically (e.g., every 5 seconds) broadcasts a keep-alive signal containing its own guardian tag ID and child tag ID. When proxy light pole A periodically receives the keep-alive signal, it indicates that the guardian tag is still within the light pole's coverage area, and light pole A continues to perform the high-frequency scanning task for the child tag.

[0101] After accepting the delegation, agent light pole A immediately notifies the corresponding child-tagged door lock via multicast, including its own light pole ID, guardian tag ID, and child tag ID, thus announcing its agency relationship. The multicast operation between the light pole and the door lock is as follows: agent light pole A sends a message to the multicast router via multicast group address 229.1.1.1, adding a child tag ID field to the message. After receiving the message, the multicast router matches the child tag ID with the locally stored packets and forwards the message to the outgoing interface registered with the corresponding child tag ID. In this way, only the door lock bound to the corresponding child tag ID receives the message and stores the ID information of the agent light pole.

[0102] After accepting the mandate, proxy light pole A periodically multicasts a message to all light poles in the community, containing its own light pole ID, guardian tag ID, child tag ID, and signal strength RSSI_A. RSSI_A refers to the signal strength of the child tag scanned by proxy light pole A, thus announcing its proxy relationship. The multicast operation between light poles is as follows: proxy light pole A sends a message to the router via the multicast group address 229.1.1.1. The message includes a post field for light pole type identification but does not contain the light pole ID. After receiving the message, the multicast router matches the light pole type identification with the locally stored packets and forwards the multicast message to the outgoing interface registered with the corresponding light pole type identification. This ensures that all light poles receive the multicast message.

[0103] 2. Relay testing process:

[0104] When a child moves, light pole B scans for broadcast signals from the child's tag and measures the signal strength RSSI_B. Light pole B checks the latest multicast message from light pole A, determining that light pole A is the current agent and its signal strength RSSI_A. Comparing the two signal strengths, if RSSI_B is significantly greater than RSSI_A (i.e., RSSI_B - RSSI_A ≥ a preset threshold), it indicates the child is closer to light pole B. Light pole B then unicasts a "takeover request" message to light pole A, containing its own light pole ID, guardian tag ID, child tag ID, and signal strength RSSI_B. Upon receiving this, light pole A unicasts a "takeover confirmation" message back to light pole B. After successfully taking over, light pole B immediately notifies the corresponding door lock via multicast (the message includes a child tag ID field), and the corresponding door lock stores the agent light pole ID information. After successfully taking over, light pole B periodically announces itself as the new agent light pole to all light poles in the community via multicast (the message includes a light pole type identifier Post field, but does not include the light pole ID). The guardian tag only broadcasts a keep-alive signal periodically throughout the process, without any awareness or operation of agent switching, maintaining the lowest power consumption.

[0105] The direct trigger for light pole A to stop scanning is the successful completion of the takeover confirmation process, not based on whether a keep-alive signal from the guardian tag is received. This is because the keep-alive signal from the guardian tag may remain within range but weaken temporarily due to signal obstruction or temporary interference. If light pole A prematurely stops its proxy based solely on the absence of a keep-alive signal from the guardian tag, it creates a monitoring vulnerability. However, if light pole A does not receive a keep-alive signal from the guardian tag for an extended period (e.g., 1 minute) during the proxy period and does not receive a takeover request from other light poles (possibly due to guardian tag malfunction or leaving the community), light pole A will automatically stop scanning.

[0106] If a child moves to the boundary of multiple light poles, several light poles may meet the takeover criteria (the light pole detects a significantly stronger signal strength in the child's tag broadcast signal than in the latest multicast message from the previous agent light pole). Each of these candidate light poles then unicasts a "Takeover Request" message to light pole A, containing its own light pole ID, guardian tag ID, child tag ID, and signal strength RSSI. Light pole A selects the light pole with the highest RSSI and replies with a "Takeover Confirmation" message.

[0107] The activities of nannies and children within the community are generally quite regular. Each time a light pole acts as an agent or takes over a guardian's tag, it multicasts its own light pole ID (with the child's tag ID field added to the message) to the corresponding door lock. After a period of time (e.g., one month), the door lock obtains a set R of frequently used light poles, such as {A, B, C, D}. One month later, when light pole E acts as an agent or takes over a guardian's tag, it immediately notifies the door lock with the corresponding child tag via multicast. Upon receiving the multicast message, the door lock first checks if the ID of the agent light pole belongs to set R. If the ID is already in set R, R remains unchanged, and the door lock returns the set R of frequently used light poles. If the ID is not in set R, R is updated, such as {A, B, C, D, E}, and the updated set R of frequently used light poles is returned. When the door lock received the multicast message from the agent light pole a month ago, it only stored it and did not return set R. After light pole E acquires set R, it replaces the locally cached set R (if any) and periodically multicasts messages to the light poles within set R (not all light poles in the community) to announce its proxy relationship. The multicast operation is as follows: the proxy light pole E sends a message to the router via multicast group address 229.1.1.1, adding a combined field of the light pole type identifier (POST) and the light pole ID from set R. Upon receiving the message, the multicast router matches the light pole type identifier and light pole ID against its locally stored packets and forwards the multicast message to the outgoing interface that has both the corresponding light pole type identifier and the light pole ID from set R registered. In this way, only the light poles within set R receive the multicast message.

[0108] Further optimization can be achieved by increasing the proxy frequency for the set of commonly used light poles, such as {(A, 100 times), (B, 80 times), (C, 70 times), (D, 10 times)}. After a period of time (such as one month), the door lock sorts the light poles according to the proxy frequency and selects the top N light pole IDs with the highest frequency (e.g., N=5) to generate a set of commonly used proxy light poles.

[0109] 3. Alarm triggering process:

[0110] Agent light pole B actively scans the target child's tag ID. Each time a child's tag is scanned, its RSSI value is recorded. If the RSSI value is found to be below the threshold (e.g., -80dBm) for a continuous period of T, it is considered that a child has moved away from the target.

[0111] Agent light pole B notifies the door locks with the corresponding child tag via multicast (the message includes a child tag ID field). Only the door locks bound to the corresponding child tag ID receive the alarm message, triggering an audible and visual alarm.

[0112] Simultaneously, agent light pole B sends an alarm message to the guardian's tag. Specifically, it's necessary to consider whether the guardian's tag is currently within the scanning range of agent light pole B.

[0113] 1) If the guardian tag is within the scanning range of the agent light pole B, that is, if the agent light pole B can scan the broadcast keep-alive signal of the guardian tag, then the agent light pole B will directly send an alarm message to the guardian tag via Bluetooth.

[0114] 2) If the guardian tag is not within the scanning range of proxy light pole B, meaning proxy light pole B cannot scan the broadcast keep-alive signal of the guardian tag, then proxy light pole B sends a message to the router via multicast group address 229.1.1.1. The message includes a combined field of the light pole type identifier (POST) and the light pole ID within set R. Upon receiving the message, the multicast router matches the light pole type identifier and light pole ID with its locally stored packets and forwards the multicast message to the outgoing interface that has both the corresponding light pole type identifier and the light pole ID within set R registered. Thus, only light poles within set R receive the multicast message. After receiving the message, these light poles scan for the broadcast keep-alive signal of the guardian tag within their respective ranges. If detected, they forward an alarm message to the guardian tag via Bluetooth and return a "notification successful" message to proxy light pole B. If proxy light pole B does not receive a "success notification" message from any light pole within time t, proxy light pole B continues to send a message to the router via multicast group address 229.1.1.1. This message includes a post field with a light pole type identifier, but does not contain the light pole ID. Upon receiving the message, the multicast router matches the light pole type identifier with its locally stored message data and forwards the multicast message to the outgoing interface registered with the corresponding light pole type identifier. This ensures that all light poles receive the multicast message. After receiving the message, all light poles scan for the broadcast keep-alive signal of the guardian tag within their respective ranges. If detected, they forward an alarm message to the guardian tag via Bluetooth.

[0115] 4. Alarm cancellation procedure:

[0116] After receiving an alarm message from a light pole, the guardian tag switches from low-power broadcast mode back to active scanning mode and supports periodic broadcasts so that the light pole can detect the guardian tag. However, in alarm mode, the guardian tag no longer establishes a delegation relationship with any light pole.

[0117] (1) If the guardian's tag is scanned first to the child's tag:

[0118] If the guardian tag detects that the child tag's RSSI is higher than a threshold (e.g., -50dBm) and simultaneously scans the light pole's broadcast signal, it selects the light pole C with the strongest RSSI (i.e., the closest distance) and sends a "Target Found" message containing its own guardian tag ID and the child tag ID. The receiving light pole performs a matching verification. Upon successful verification, it sends a targeted multicast notification to the corresponding resident to deactivate the alarm, the message containing the child tag ID. After the alarm is deactivated, the guardian tag can be reassigned to a nearby light pole.

[0119] (2) If a light pole D is scanned first and a child tag is detected:

[0120] If light pole D detects that the RSSI of a child tag is higher than a threshold (e.g., -50dBm), light pole D sends a directed multicast message to the door lock containing the child tag ID, notifying the corresponding homeowner to deactivate the alarm. Light pole D attempts to notify the guardian tag: 1) If the guardian tag is within the scanning range of light pole D (i.e., light pole D can scan the guardian tag's broadcast signal), light pole D directly sends an alarm deactivation message to the guardian tag via Bluetooth; 2) If the guardian tag is not within the scanning range of light pole D (i.e., light pole D cannot scan the guardian tag's broadcast signal), light pole D sends a message to the router via multicast group address 229.1.1.1. The message includes a combined field of the light pole type identifier (POST) and the light pole ID from set R. Upon receiving the message, the multicast router matches the light pole type identifier and light pole ID with its locally stored messages and forwards the multicast message to the outgoing interface registered with the corresponding light pole type identifier and light pole ID from set R. Thus, only light poles within set R receive this multicast message. Upon receiving the message, these light poles scan for the broadcast keep-alive signal of the guardian tag within their respective ranges. If a signal is detected, they forward the alarm cancellation message to the guardian tag via Bluetooth and return a "notification success" message to the agent light pole D. If the agent light pole D does not receive a "notification success" message from any light pole within time t, it continues to send a message to the router via multicast group address 229.1.1.1. This message includes a post field for the light pole type identifier but does not contain the light pole ID. Upon receiving the message, the multicast router matches the light pole type identifier with its locally stored message and forwards the multicast message to the outgoing interface registered with the corresponding light pole type identifier. This ensures all light poles receive the multicast message. After receiving the message, all light poles scan for the broadcast keep-alive signal of the guardian tag within their respective ranges. If a signal is detected, they forward the alarm cancellation message to the guardian tag via Bluetooth. Upon receiving the message, the guardian tag stops scanning and learns the ID and location information of the discovered light pole from the message, then proceeds to find the target child. After the alarm is cleared, the guardian tag can be reassigned to a nearby light pole.

[0121] Beneficial effects:

[0122] 1. By using light poles to perform high-frequency scanning tasks on behalf of guardian tags, the power consumption of guardian tags is significantly reduced;

[0123] 2. Optimize multicast technology for accurate and rapid message forwarding. 3. Implement limited multicast by automatically creating a set of frequently used light poles, reducing interference with unrelated light poles and lowering network load. Protection Points:

[0124] 1. Through daily proxying and takeover, the door lock automatically establishes a dedicated set of frequently used light poles R based on historical learning. When an alarm is triggered or deactivated, it first sends a notification via multicast to a limited range to reduce interference with unrelated light poles and reduce network load. If no successful notification message is received within a certain period of time, it intelligently falls back to multicast to all light poles, ensuring system reliability.

[0125] 2. A decentralized task delegation method: The guardian tag dynamically delegates high-power Bluetooth scanning tasks to the nearest smart light pole and enters low-power sleep mode, achieving extreme energy saving of the terminal device and extending the service life of the terminal device;

[0126] 3. A distributed relay mechanism based on signal strength: Agent light poles autonomously and seamlessly hand over detection tasks by comparing the signal strength of the guardian tag, without the need for a central server, thus ensuring the continuity and robustness of monitoring;

[0127] 4. A collaborative alarm and alarm clearing method based on optimized multicast: When a proxy light pole detects an abnormal child signal, it simultaneously executes two actions: "notifying the nanny" and "notifying the door lock." Alarm messages, through different multicast addresses and type identifiers, precisely trigger local alarms on resident door locks and a collaborative search of all light poles in the community. Whether the nanny or the light pole discovers the lost child first, they all broadcast through a unified "alarm clearer" role, ensuring that the status of all alarm devices (door locks, light poles) can be synchronously and reliably cleared.

[0128] As can be seen, based on the signal strength of the smart light pole scanned by the guardian tag, the nearest light pole is selected as the proxy light pole, a delegation relationship is established, and the scanning task is transferred to the proxy light pole, causing the guardian tag to enter a low-power broadcast mode. Based on the changes in signal strength detected by different light poles during the child's movement, the proxy right is switched by comparing the signal strength. Based on the results of the proxy light pole's continuous monitoring of the child's tag signal strength, when the signal strength is consistently below the threshold, an alarm message is sent to the door lock and guardian tag through a hierarchical multicast mechanism. Based on the event of the guardian finding the child or the light pole re-detecting the child, the relevant devices are notified to deactivate the alarm state and restore the normal monitoring mode by optimizing the multicast path. This enables low-cost, seamless relay monitoring from indoor to outdoor public areas, improving the accuracy and timeliness of alarms.

[0129] Another embodiment of the present invention provides a monitoring system based on tag-lock collaboration, see [link to relevant documentation]. Figure 3 The system may include:

[0130] Module 301 is used for proxy delegation establishment: based on the signal strength of the smart light pole scanned by the guardian tag, the nearest light pole is selected as the proxy light pole, a delegation relationship is established, and the scanning task is transferred to the proxy light pole, so that the guardian tag enters the low power broadcast mode;

[0131] The detection module 302 is used for dynamic relay detection: based on the changes in signal strength detected by different light poles during the child's movement, the module triggers the switching of proxy rights by comparing the signal strength, thereby realizing the automatic relay replacement of the proxy light pole;

[0132] Trigger module 303 is used for intelligent alarm triggering: based on the results of continuous monitoring of the child tag signal strength by the agent light pole, when the signal strength is continuously lower than the threshold, alarm information is sent to the door lock and guardian tag through a hierarchical multicast mechanism;

[0133] The alarm cancellation module 304 is used for coordinated alarm cancellation: based on events such as a guardian finding a child or a light pole detecting a child again, it notifies relevant devices to cancel the alarm status and restore normal monitoring mode by optimizing the multicast path.

[0134] This invention also provides a storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when running.

[0135] This invention also provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0136] Specifically, the aforementioned electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the aforementioned processor, and the input / output device is connected to the aforementioned processor.

[0137] The above description, based on the embodiments shown in the figures, details the structure, features, and effects of the present invention. The above description is only a preferred embodiment of the present invention, but the present invention is not limited to the scope of implementation shown in the figures. Any changes made in accordance with the concept of the present invention, or equivalent embodiments modified to have equivalent changes, that do not exceed the spirit covered by the specification and figures, should be within the protection scope of the present invention.

Claims

1. A monitoring method based on tag-lock collaboration, characterized in that, The method includes: Proxy delegation establishment: Based on the signal strength of the smart light pole scanned by the guardian tag, the nearest light pole is selected as the proxy light pole, a delegation relationship is established, and the scanning task is transferred to the proxy light pole, so that the guardian tag enters the low power broadcast mode; Dynamic relay detection: Based on the changes in signal strength detected by different lampposts during the child's movement, the system triggers a switch of proxy rights by comparing signal strength, thereby enabling automatic relay replacement of the proxy lamppost; Intelligent alarm triggering: Based on the results of continuous monitoring of the child tag signal strength by the agent light pole, when the signal strength is consistently below the threshold, an alarm message is sent to the door lock and guardian tag through a hierarchical multicast mechanism; Collaborative alarm deactivation: Based on events such as a guardian finding a child or a light pole detecting a child again, the alarm status is deactivated and normal monitoring mode is restored by optimizing the multicast path to notify relevant devices.

2. The method according to claim 1, characterized in that, The establishment of the agency delegation includes: Agent light pole selection: Based on the broadcast signal strength of each smart light pole within the range of the guardian's tag scanning, select the light pole with the strongest RSSI as the agent light pole; Establishment of delegation relationship: Based on the delegation request sent by the guardian tag to the agent light pole, the agent light pole confirms and establishes the delegation relationship. The guardian tag stops actively scanning and switches to periodic broadcast mode. Agent announcement multicast: Upon successful establishment of the delegation relationship, the agent light pole notifies the corresponding door lock via a multicast message carrying the child tag ID, and notifies all light poles via a multicast message carrying the light pole type identifier; Task execution switch: Based on the established delegation relationship, the agent light pole begins to continuously scan for child tags, while the guardian tag only broadcasts a keep-alive signal periodically.

3. The method according to claim 2, characterized in that, The dynamic relay detection includes: Signal strength monitoring: Based on the continuous scanning of the children's tag broadcast signal by each light pole, the detected signal strength value is recorded in real time; Takeover condition judgment: Based on the difference between the signal strength detected by the candidate light pole and the signal strength of the previous agent light pole, the takeover process is triggered when the difference exceeds a preset threshold; Agency handover: Based on the takeover request and confirmation response sent by the candidate light pole to the previous agent light pole, the agency handover is completed from the original light pole to the new light pole; Switching information synchronization: Based on the successful switching of agency rights, the new agent light pole updates the agent light pole ID stored in the door lock via multicast and notifies all light poles of the change in agency relationship.

4. The method according to claim 3, characterized in that, The intelligent alarm triggering includes: Distance event determination: Based on the continuous monitoring of the child tag signal strength by the agent light pole, when the signal strength is continuously lower than the threshold for a preset time, a child distance event is determined to have occurred. Tiered alarm notification: Based on the determination of the distance event, the agent light pole triggers the door lock sound and light alarm through a multicast message carrying the child tag ID, and at the same time sends a guardian tag paging request to the light poles in the commonly used light pole set directly via Bluetooth or through limited multicast. Global paging rollback: If no response confirmation is received within a preset time based on the limited multicast, the agent light pole switches to global multicast mode and sends a guardian tag paging request to all light poles; Alarm information transmission: Based on the results of scanning the guardian tag broadcast signal on each light pole, alarm information is directly transmitted to the guardian tag via Bluetooth.

5. The method according to claim 4, characterized in that, The coordinated alarm cancellation includes: Alarm clearance condition detection: The alarm clearance process is triggered when the guardian's tag is re-scanned and the child's tag is detected and the signal strength is higher than the threshold, or when any light pole re-detects the child's tag and the signal strength is higher than the threshold. Alarm status clearing: Based on the event that the alarm clearance conditions are met, the light pole notifies the corresponding door lock to clear the alarm status via a multicast message carrying a child tag ID; Optimized Guardian Notification: Based on the relative position of the detected light pole and the guardian tag, an alarm cancellation message is sent to the guardian tag via direct Bluetooth communication or through a limited multicast of commonly used light poles. If no response confirmation is received within a preset time after the limited multicast, the detected light pole switches to global multicast mode and sends a guardian tag paging request to all light poles. Based on the results of each light pole scanning the guardian tag broadcast signal, the alarm cancellation message is directly transmitted to the guardian tag via Bluetooth. Normal mode restoration: After the alarm is cleared, the guardian tag re-enters the entrusted status, and the system returns to normal guardianship mode.

6. The method according to claim 5, characterized in that, The method also includes a common agent light pole set learning and optimization mechanism: Historical data collection: Based on the multicast notifications received by the door lock from each agent light pole ID, record the number of agent times and time information for each light pole; Commonly used set generation: Based on the statistical results of the proxy frequency of each light pole within a preset time period, select the top N light pole IDs with the highest proxy frequency to generate a commonly used proxy light pole set; Limited multicast execution: Based on the establishment of a set of commonly used proxy poles, when announcing a proxy relationship, the proxy poles only send multicast messages to poles within the set, significantly reducing network load; Dynamic update of the set: Based on the result of determining whether the new agent light pole ID belongs to the existing commonly used set, the set of commonly used agent light poles is dynamically updated and synchronized to the relevant light poles.

7. A monitoring system based on tag-lock collaboration, characterized in that, The system includes: The module is used to establish a proxy delegation: based on the signal strength of the smart light pole scanned by the guardian tag, the nearest light pole is selected as the proxy light pole, a delegation relationship is established, and the scanning task is transferred to the proxy light pole, so that the guardian tag enters the low power broadcast mode; The detection module is used for dynamic relay detection: based on the changes in signal strength detected by different lampposts during the child's movement, the module triggers the switching of proxy rights by comparing the signal strength, thereby realizing the automatic relay replacement of the proxy lamppost; The trigger module is used for intelligent alarm triggering: based on the results of continuous monitoring of the child tag signal strength by the agent light pole, when the signal strength is continuously lower than the threshold, alarm information is sent to the door lock and guardian tag through a hierarchical multicast mechanism; The alarm cancellation module is used for coordinated alarm cancellation: based on events such as a guardian finding a child or a light pole detecting a child again, it notifies relevant devices to cancel the alarm status and restore normal monitoring mode by optimizing the multicast path.

8. The system according to claim 7, characterized in that, The establishment module is specifically used for: Agent light pole selection: Based on the broadcast signal strength of each smart light pole within the range of the guardian's tag scanning, select the light pole with the strongest RSSI as the agent light pole; Establishment of delegation relationship: Based on the delegation request sent by the guardian tag to the agent light pole, the agent light pole confirms and establishes the delegation relationship. The guardian tag stops actively scanning and switches to periodic broadcast mode. Agent announcement multicast: Upon successful establishment of the delegation relationship, the agent light pole notifies the corresponding door lock via a multicast message carrying the child tag ID, and notifies all light poles via a multicast message carrying the light pole type identifier; Task execution switch: Based on the established delegation relationship, the agent light pole begins to continuously scan for child tags, while the guardian tag only broadcasts a keep-alive signal periodically.

9. A storage medium, characterized in that, The storage medium stores a computer program, wherein the computer program is configured to execute the method of any one of claims 1-6 when it is run.

10. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to run the computer program to perform the method of any one of claims 1-6.

Images