A method and system for multi-door lock cooperative processing

Abstract

The application discloses a kind of multi-door lock cooperative processing method and system, method includes: according to the preset trigger operation detected by first door lock B and read RFID identification information, generate assistance request IGMP multicast message, and send to router;According to assistance request IGMP multicast message, record the interface information associated with RFID identification information in multicast forwarding table item and effective period, and buffer multicast message;According to the same RFID identification information detected by second door lock A and read preset trigger operation, generate assisted request multicast message containing RFID identification information, and send to router;According to RFID identification information and multicast forwarding table item, after verifying that effective period is not expired, message is directionally forwarded to first door lock B, and assistance confirmation message is sent to second door lock A by first door lock B, triggers robot calling instruction.Utilize the embodiment of the application, multi-door lock cooperative control of low delay, high reliability can be realized.

Description

Technical Field

[0001] This invention belongs to the field of smart door lock technology, and in particular to a method and system for multi-door lock collaborative processing. Background Technology

[0002] In modern smart home and building management systems, multi-lock collaborative control is a key technology for improving security and convenience. Traditional lock systems typically operate independently. When users need to perform collaborative operations across multiple locks (such as guest assistance in opening doors), they often rely on a central server for complex permission verification and command forwarding, resulting in high response latency, heavy network load, and the risk of single points of failure. While existing multicast communication-based lock collaboration solutions can reduce reliance on a central node, they still suffer from low multicast message management efficiency, insufficient RFID tag matching accuracy, and poor timeliness of collaborative operations. Especially in distributed environments, real-time status synchronization and accurate message routing among multiple locks face challenges, and collaboration can easily fail due to network latency or tag conflicts. Summary of the Invention

[0003] The purpose of this invention is to provide a method and system for multi-lock collaborative processing to overcome the shortcomings of the prior art and achieve low-latency, high-reliability door lock collaborative control.

[0004] One embodiment of this application provides a method for multi-lock collaborative processing, the method comprising:

[0005] Triggering Assistance Request and Multicast Registration: Based on the preset triggering operation detected by the first door lock B and the RFID identification information read, generate an IGMP multicast message containing the RFID identification information and validity period, and send it to the router;

[0006] Multicast forwarding table entry construction and caching: Based on the IGMP multicast assistance request message received by the router, record the interface information and validity period associated with the RFID identification information in the multicast forwarding table entry, and cache the multicast message;

[0007] Assisted lock request triggering and multicast forwarding: Based on the preset triggering operation detected by the second lock A and the same RFID tag information read, generate an assistance request multicast message containing RFID tag information and send it to the router;

[0008] Precise message routing and assistance confirmation: Based on the router's matching of the RFID identification information in the multicast message of the assistance request with the multicast forwarding table entry, after verifying that the validity period has not expired, the message is forwarded to the first door lock B, and the first door lock B sends an assistance confirmation message to the second door lock A, triggering the robot summoning command.

[0009] Optionally, the triggering of the assistance request and multicast registration includes:

[0010] Trigger operation detection: Based on the detection of two consecutive doorbell button presses by the first door lock B, the assistance request process is initiated and a countdown begins;

[0011] RFID tag verification: Based on the RFID tag information read during the countdown, compare it with the resident registration form of the first door lock B. If there is no match, generate an abnormal prompt containing the RFID tag.

[0012] Multicast message generation: Based on the detection of two consecutive doorbell button presses, generate an IGMP multicast message carrying the RFID tag, expiration date, and door lock ID;

[0013] Multicast message sending: The router sends IGMP multicast messages to the preset multicast address, triggering the router to record the interface binding relationship containing the RFID tag and its validity period.

[0014] Optionally, the multicast forwarding table entry construction and caching includes:

[0015] Interface information registration: Based on the RFID identifier and source IP address in the IGMP multicast message parsed by the router, mark the interface connected to the first door lock B as the assisting interface in the multicast forwarding table entry and associate it with the validity period;

[0016] Message caching management: Caches complete IGMP multicast messages, sets a cache timeout, and automatically deletes messages if they are not matched within the timeout period;

[0017] Conflict handling: When multiple door locks simultaneously send IGMP multicast messages carrying different RFID tags, the router independently records the binding relationship between each RFID tag and the interface.

[0018] Optionally, the assisted door lock request triggering and multicast forwarding includes:

[0019] Assistance request detection: Based on the detection of two consecutive doorbell button presses by the second door lock A, the assistance request process is initiated and a countdown begins;

[0020] RFID tag matching: Based on the same RFID tag information read within the countdown, compare it with the resident registration form of the second door lock. If no match is found, generate a multicast message requesting assistance.

[0021] Multicast message encapsulation: Encapsulate the RFID tag, the lock ID of the second lock A, and the request type into the assistance request multicast message;

[0022] Multicast message targeted transmission: The router sends the assist request multicast message to the same multicast address, triggering the router's matching and forwarding logic.

[0023] Optionally, the precise message routing and assistance confirmation include:

[0024] RFID tag matching: Extract the RFID tag from the multicast message requesting assistance from the router, and query the associated assistance interface in the multicast forwarding table entry;

[0025] Validity verification: If the validity period of the assistance interface has not expired, the message will be forwarded to the interface of the first door lock B.

[0026] Assistance confirmation process: Based on the assistance request multicast message received by the first door lock B, verify the consistency between the RFID tag and the cache record, and generate a unicast reply message carrying the confirmation result;

[0027] Robot summoning triggered: Based on the confirmation result received by the second door lock A, a robot summoning command is sent to the platform, and the operation log is recorded.

[0028] Optionally, the robot summoning trigger includes:

[0029] Instruction encapsulation: Based on the door lock ID and RFID tag in the confirmation result, generate robot scheduling instructions containing target location and authorization verification parameters;

[0030] Platform interaction: The platform sends dispatch instructions to the robot, triggering the robot to navigate to the location of the second door lock A;

[0031] Facial recognition authorization: The facial information of the user collected after the robot arrives is compared with the resident registration form stored on the platform. If the verification is successful, the second door lock A will be unlocked.

[0032] Another embodiment of this application provides a system for multi-lock collaborative processing, the system comprising:

[0033] The triggering module is used to trigger assistance requests and multicast registration: based on the preset triggering operation detected by the first door lock B and the RFID identification information read, it generates an assistance request IGMP multicast message containing RFID identification information and validity period, and sends it to the router;

[0034] The construction module is used for multicast forwarding table entry construction and caching: based on the IGMP multicast assistance request message received by the router, it records the interface information and validity period associated with the RFID identification information in the multicast forwarding table entry, and caches the multicast message;

[0035] The forwarding module is used for the triggered and multicast forwarding of the requested assistance from the door lock: based on the preset triggering operation detected by the second door lock A and the same RFID tag information read, it generates a multicast message containing the RFID tag information for the requested assistance and sends it to the router;

[0036] The assistance module is used for precise message routing and assistance confirmation: based on the router's matching of the RFID identification information in the multicast message of the assistance request with the multicast forwarding table entry, after verifying that the validity period has not expired, the message is forwarded to the first door lock B, and the first door lock B sends an assistance confirmation message to the second door lock A, triggering the robot summoning command.

[0037] 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.

[0038] 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.

[0039] Compared with existing technologies, the present invention provides a method for multi-lock collaborative processing. Based on a preset trigger operation detected by a first lock B and the RFID tag information read, an assistance request IGMP multicast message is generated and sent to a router. Based on the assistance request IGMP multicast message, the interface information associated with the RFID tag information and its validity period are recorded in the multicast forwarding table entry, and the multicast message is cached. Based on a preset trigger operation detected by a second lock A and the same RFID tag information read, an assistance request multicast message containing the RFID tag information is generated and sent to the router. After verifying that the validity period has not expired based on the RFID tag information and the multicast forwarding table entry, the message is forwarded to the first lock B, and the first lock B sends an assistance confirmation message to the second lock A, triggering a robot summoning command. This enables low-latency, high-reliability collaborative control of the locks. Attached Figure Description

[0040] Figure 1 Hardware structure block diagram of a computer terminal for a multi-lock collaborative processing method provided in an embodiment of the present invention;

[0041] Figure 2 A flowchart illustrating a method for collaborative processing of multiple locks provided in an embodiment of the present invention;

[0042] Figure 3 This is a schematic diagram of a system for collaborative processing of multiple locks provided in an embodiment of the present invention. Detailed Implementation

[0043] 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.

[0044] This invention first provides a method for multi-lock collaborative processing, which can be applied to electronic devices, such as computer terminals, specifically ordinary computers.

[0045] 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 multi-lock collaborative processing 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.

[0046] Non-volatile storage media can store operating systems and computer programs. These computer programs include program instructions that, when executed, cause the processor to perform any method of multi-lock cooperative processing.

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

[0048] Internal memory provides an environment for the execution of computer programs stored in non-volatile storage media. When executed by a processor, the computer program enables the processor to perform any method of multi-lock cooperative processing.

[0049] This network interface is used for network communication, such as sending assigned tasks. Those skilled in the art will understand that... Figure 1 The 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.

[0050] 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.

[0051] See Figure 2The present invention provides a method for multi-lock collaborative processing, which may include the following steps:

[0052] S201, Triggering Assistance Request and Multicast Registration: Based on the preset triggering operation detected by the first door lock B and the read RFID tag information, generate an assistance request IGMP multicast message containing RFID tag information and validity period, and send it to the router; specifically, the triggering assistance request and multicast registration includes:

[0053] Trigger operation detection: Based on the detection of two consecutive doorbell button presses by the first door lock B, the assistance request process is initiated and a countdown begins;

[0054] RFID tag verification: Based on the RFID tag information read during the countdown, compare it with the resident registration form of the first door lock B. If there is no match, generate an abnormal prompt containing the RFID tag.

[0055] Multicast message generation: Based on the detection of two consecutive doorbell button presses, generate an IGMP multicast message carrying the RFID tag, expiration date, and door lock ID;

[0056] Multicast message sending: The router sends IGMP multicast messages to the preset multicast address, triggering the router to record the interface binding relationship containing the RFID tag and its validity period.

[0057] S202, Multicast forwarding table entry construction and caching: Based on the IGMP multicast assistance request message received by the router, the interface information and validity period associated with the RFID identification information are recorded in the multicast forwarding table entry, and the multicast message is cached; specifically, the multicast forwarding table entry construction and caching includes:

[0058] Interface information registration: Based on the RFID identifier and source IP address in the IGMP multicast message parsed by the router, mark the interface connected to the first door lock B as the assisting interface in the multicast forwarding table entry and associate it with the validity period;

[0059] Message caching management: Caches complete IGMP multicast messages, sets a cache timeout, and automatically deletes messages if they are not matched within the timeout period;

[0060] Conflict handling: When multiple door locks simultaneously send IGMP multicast messages carrying different RFID tags, the router independently records the binding relationship between each RFID tag and the interface.

[0061] S203, Assisted door lock request triggering and multicast forwarding: Based on the preset triggering operation detected by the second door lock A and the same RFID tag information read, an assistance request multicast message containing the RFID tag information is generated and sent to the router; specifically, the assisted door lock request triggering and multicast forwarding includes:

[0062] Assistance request detection: Based on the detection of two consecutive doorbell button presses by the second door lock A, the assistance request process is initiated and a countdown begins;

[0063] RFID tag matching: Based on the same RFID tag information read within the countdown, compare it with the resident registration form of the second door lock. If no match is found, generate a multicast message requesting assistance.

[0064] Multicast message encapsulation: Encapsulate the RFID tag, the lock ID of the second lock A, and the request type into the assistance request multicast message;

[0065] Multicast message targeted transmission: The router sends the assist request multicast message to the same multicast address, triggering the router's matching and forwarding logic.

[0066] S204, Precise Message Routing and Assistance Confirmation: Based on the router's matching of the RFID identification information in the multicast message requesting assistance with the multicast forwarding table entries, and after verifying that the validity period has not expired, the message is forwarded to the first door lock B, and the first door lock B sends an assistance confirmation message to the second door lock A, triggering the robot summoning command. Specifically, the precise message routing and assistance confirmation includes:

[0067] RFID tag matching: Extract the RFID tag from the multicast message requesting assistance from the router, and query the associated assistance interface in the multicast forwarding table entry;

[0068] Validity verification: If the validity period of the assistance interface has not expired, the message will be forwarded to the interface of the first door lock B.

[0069] Assistance confirmation process: Based on the assistance request multicast message received by the first door lock B, verify the consistency between the RFID tag and the cache record, and generate a unicast reply message carrying the confirmation result;

[0070] Robot summoning trigger: Based on the confirmation received by the second door lock A, a robot summoning command is sent to the platform, and the operation log is recorded. Specifically, the robot summoning trigger includes:

[0071] Instruction encapsulation: Based on the door lock ID and RFID tag in the confirmation result, generate robot scheduling instructions containing target location and authorization verification parameters;

[0072] Platform interaction: The platform sends dispatch instructions to the robot, triggering the robot to navigate to the location of the second door lock A;

[0073] Facial recognition authorization: The facial information of the user collected after the robot arrives is compared with the resident registration form stored on the platform. If the verification is successful, the second door lock A will be unlocked.

[0074] In practical applications, when the owner of a smart lock forgets their access card or mobile phone and finds it inconvenient to travel to the management center for services, they may wish to summon a robot to unlock the door. After consultation, nearby neighbors may offer assistance. This invention proposes a method where a neighbor's RFID card swipe and the door lock interact via IGMP to summon the robot. A specific technical solution includes:

[0075] 1. Core Idea: I didn't have my RFID card or phone, so I couldn't swipe my card to enter or call the robot. Seeing my neighbor was there, I asked them for help in calling the robot. My neighbor pressed two buttons on their own door lock to trigger it, then swiped their RFID card, pressed two more buttons to confirm, and immediately came to my door lock, swiped their RFID card, and pressed two buttons to summon the robot for me. The robot then unlocked the door for me using facial recognition. Since my door lock and the neighbor's lock don't know each other's IP addresses and can't interact directly, a design was added: Card B swipes on lock B, lock B sends a sign-up message to join the IGMP multicast (226.1.1.10), which the router receives and records on the interface connected to lock B; Card B then swipes on lock A, lock A sends a multicast (226.1.1.10) confirmation message, so this multicast message is only sent to lock B, thus avoiding harassment of other locks.

[0076] To avoid a situation where B assists A while D assists C, causing A's multicast messages to be forwarded to both B and D simultaneously, when IGMP messages sent by locks B and D carry access card RFID tags, the router, at the interface receiving the message, must record both the multicast group and the RFID tag. Simultaneously, multicast messages sent by locks A and C also carry RFID tags. When forwarding, the router needs to identify the RFID tags to accurately forward multicast messages sent by lock A from the output interface connected to lock B, and similarly, multicast messages sent by lock C from the output interface connected to lock D.

[0077] First, the router swipes lock A. Lock A detects that the card doesn't match its own and sends a multicast message (containing the RFID tag). The router generates a (*, G) entry based on this multicast message, registers the "assisted interface," and caches the multicast message. Then, the router swipes lock B. Lock B detects that the card matches its own and sends an igmp message, registering the "assisted interface" in the (*G) entry and marking the RFID tag. The router then retrieves the locally cached message containing the RFID tag and forwards it from the assisted interface.

[0078] To avoid routers frequently interpreting the internal information of non-standard multicast messages, a further improvement is made: the router registers the source IP address of lock A and the association information of the RFID tag on the assisted interface. This information is taken from the IGMP message sent by lock A. Whenever the router generates a new RFID tag on the assisted interface, it looks up the IP address associated with that RFID tag on the assisted interface, searches for the cached multicast packet based on that IP address (by comparing the source IP), and forwards the matching packet out from the assisted interface. Simultaneously, the information on both the assisted and assisted interfaces is deleted.

[0079] 2. The complete technical implementation process is as follows:

[0080] (1) Prerequisites:

[0081] The homeowner's front door is equipped with a smart lock that supports RFID card reading for unlocking. The lock stores a "resident registration information form" which includes the resident's name, RFID-ID number, etc.

[0082] The robot can autonomously walk to the door of a designated room; it is equipped with a display screen that supports facial recognition for comparison; it can connect to door locks and authorize unlocking of designated locks. The robot connects to the platform and receives tasks from it (such as delivering items to the homeowner or providing on-site facial recognition and door unlocking); the robot periodically synchronizes and stores the resident registration form from the platform (the information in this form is collected and recorded by the administrator, typically synchronized weekly), including room ID, door lock ID, door lock IP, homeowner's name, facial image / feature vector, RFID-ID number, etc.

[0083] (2) The owner of door lock A, a, did not have the door lock RFID card and could not unlock the door. He found that his neighbor (the owner of door lock B, b) was nearby and verbally negotiated with his neighbor for help.

[0084] Explanation: At this time, homeowner A does not have an RFID card and cannot unlock the door, nor does he have a mobile phone to contact the management center. Due to health reasons, carrying belongings, caring for infants or the elderly, he is unable to go to the management center and wishes to summon a robot from the door lock. When homeowner B, the owner of neighboring door lock B, is found in the hallway with his own door lock's RFID card (assuming the RFID ID number is RFID-ID(b), for convenience, this card is referred to as RFID(b)), A and B verbally agree that B will summon the robot to the door lock to perform facial recognition and unlock the door for A.

[0085] (3) Door lock B determines that the current process involves another door lock summoning the robot by reading the information from pressing the doorbell button and swiping the RFID-ID(b). It caches the record of summoning the robot and sends an IGMP multicast message carrying the RFID-ID(b), which is recorded by the router on the interface connected to door lock B in the (*,G) forwarding table entry. The reason why the owner b swipes the card on door lock B is twofold: first, to prove that it was indeed his action and to perform verification; and second, to prevent door lock A from disturbing other door locks when making a request.

[0086] The detailed implementation process is explained below:

[0087] After door lock B detects two doorbell button notifications (at this time, b presses the "doorbell" button twice on door lock B), the robot summoning process is initiated and a 30-second countdown begins (waiting for RFID card reading; if no RFID card is read within 30 seconds, the robot summoning process ends; to continue summoning the robot, the "doorbell" button needs to be pressed twice again on door lock B). If no RFID card is read within 30 seconds (at this time, it may be that a stranger pressed the "doorbell" button twice on door lock B, and the stranger does not have an RFID card), the process ends.

[0088] Instructions for Use: In this invention, pressing the "Doorbell" button twice on door lock B initiates the robot summoning process. After swiping the RFID card, pressing the "Doorbell" button twice again confirms the robot summoning. If the RFID card is not swiped after pressing the "Doorbell" button twice on door lock B initially, the robot summoning process stops. If the "Doorbell" button is not pressed twice again after swiping the RFID card, confirmation has not been made.

[0089] If door lock B reads RFID-ID(b) within 30 seconds (at this time, b swipes the RFID card of RFID(b) on door lock B), B extracts RFID-ID(b) and compares it with the RFID-ID numbers in B's resident registration information table one by one. If no match is found, there are two abnormal situations to handle: The first abnormal situation is that if door lock B reads the RFID card but cannot recognize it (at this time, it is possible that the RFID card swiped by b on door lock B is not within the ID range used by door locks in this community, or a stranger presses the "doorbell" button twice on door lock B and swipes a card from another community), then... The display screen of B shows "Invalid card, please swipe the card again". B should replace the card with the correct RFID card (RFID(b)) and swipe the card again. In the second abnormal situation, the RFID card read by the door lock B is not the RFID-ID number in the resident registration information table of this lock (for example, the RFID card read by the door lock B is the RFID-ID(z) of the door lock Z). Then B will follow the method of step (4) to determine that it is Z who summoned the robot on behalf of B and execute step (4). Before the door lock B reads and matches the RFID-ID(b), the door lock B cannot confirm who the person who just "pressed the doorbell button twice" is.

[0090] Door lock B reads RFID-ID(b) and successfully matches it with the RFID-ID number in B's resident registration information table. If it does not receive two doorbell button messages within 30 seconds, it indicates that the lock is calling the robot and the robot is called according to step (7). If two doorbell button messages are detected within 30 seconds (at this time, after swiping the card, b presses the "doorbell" button twice on door lock B, indicating that the robot is being called for another door lock), then door lock B sends an IGMP assistance message for "assistance call" to the target IP address 226.1.1.10, which includes the card number RFID-ID(b), validity period of 30 seconds, etc. The router receives and parses the IGMP assistance message "Assistance Call" sent by B, extracts the multicast group address 226.1.1.10 and RFID-ID(b), creates or updates the multicast forwarding table entry (*,226.1.1.10), and records the RFID-ID(b) and a 30-second validity period on the interface that received the "Assistance Call" IGMP assistance message in this forwarding table entry (at this time, the interface that connects to B, RFID-ID(b), and 30-second validity period are recorded). (When the router subsequently receives a multicast message with a destination address of 226.1.1.10 and containing RFID-ID(b), it will forward it only to this interface after determining the 30-second validity period; the information about the above interface in the multicast forwarding table entry (*,226.1.1.10) will be automatically deleted after the 30-second validity period). While sending the "Assistance Call" message, door lock B caches the dispatch robot event information, including the dispatch event ID number (numbered in the form of Assistance Lock ID (B) + timestamp), RFID-ID (b), Assistance Lock ID (B), validity period = 60 seconds, etc., and then starts a 60-second countdown (the 60-second countdown is set to accommodate the processing delay of door lock A, router, etc.). After 60 seconds, the dispatch robot event information is deleted.

[0091] (4) After neighbor B initiates the assistance action on door lock B, he goes to door lock A, presses the doorbell button twice, and swipes his card on door lock B. Door lock A determines that the door lock corresponding to RFID-ID (b) should summon the robot by reading the doorbell button information and the swipe card RFID-ID (b). It sends a multicast message "Request Assistance", which is forwarded by the router to door lock B. After confirmation by B, B replies unicastly to A. This method avoids disturbing other door locks. After receiving the confirmation message from B, door lock A initiates the summoning of the robot for tenant A. The reason why tenant B swipes his card on door lock A is to prove that he really wants to call the robot for tenant A; the reason why door lock A needs to send a message to door lock B is to confirm that no bad person wants to maliciously open door lock A or that someone accidentally swipes their card on door lock A.

[0092] Detailed explanation of the implementation process:

[0093] Following the method in step (3), after door lock A detects the doorbell button information twice (at this time, at the invitation of a, b leaves door lock B and immediately comes to door lock A, and presses the "doorbell" button twice on door lock A), the process of A summoning the robot is started and a 30-second countdown begins. If the RFID card is not read within 30 seconds, the process ends.

[0094] If lock A detects two doorbell button presses within 30 seconds, and then reads RFID-ID(b) (at this time, b swipes the RFID card of RFID(b) on lock A), A extracts RFID(b) and compares it with the RFID-ID numbers in A's resident registration information table one by one. If RFID(b) matches (at this time, RFID(b) may also be the RFID card registered to lock A), then after waiting for 30 seconds (at this time, the "doorbell" button is not pressed twice), the door can be unlocked by swiping the card again (at this time, the door is unlocked using lock A's own RFID card, because RFID(b) is now matched with A's door card). If two doorbell button presses are detected within 30 seconds, the process of summoning a robot for other locks is triggered (at this time, RFID(b) is the RFID card registered to lock A, and the process of pressing the "doorbell" button twice -> swiping the RFID card of this lock -> pressing the "doorbell" button twice) is executed. If RFID(b) does not match the RFID-ID number in the resident registration information table of A, the same as in step (3) applies, and there are two abnormal situations to handle: The first abnormal situation is that if door lock A reads the RFID card but cannot identify it (at this time, it is possible that the RFID card swiped by b on door lock A is not within the ID range used by door locks in this community, or a stranger presses the "doorbell" button twice on door lock A and swipes the card with a card from another community), then the display screen of A will display "Invalid card, please swipe the card again", and b should replace the correct RFID card (RFID(b)) and swipe the card again; The second abnormal situation is that the RFID card read by door lock A is not the RFID-ID number in the resident registration information table of this lock (for example, the RFID card read by door lock A is the RFID-ID(b) of door lock B; or the RFID-ID(z) of another door lock Z).

[0095] If A reads RFID-ID(b) and detects the doorbell button information twice within 30 seconds (at this time, b presses the "doorbell" button twice on door lock A, and after swiping RFID(b), b wants to summon the robot for A), A generates and sends a "Request for Assistance" multicast message to the target address 226.1.1.10, containing RFID-ID(b), door lock ID(A), etc. Simultaneously, door lock A starts a 30-second countdown. After receiving the multicast message, the router extracts the RFID-ID(b) and door lock ID(A) from the message. Then, the router checks the multicast forwarding table entry (*, 226.1.1.10) to see if it records interface information matching the RFID-ID(b) (including the interface connected to B, RFID-ID(b), and 30-second validity period), and determines if the interface information has expired. If the check result indicates that the interface information has not expired, the router only forwards the "Request for Assistance" multicast message sent by A to the interface connected to door lock B. If no interface information matching RFID-ID(b) exists in the multicast forwarding table entry (*, 226.1.1.10), or if the matching interface information has expired (i.e., more than 30 seconds have passed), the router discards the multicast message. In this case, lock B will not receive the query request from lock A, and naturally will not reply to lock A with the query result; that is, lock A will not receive a reply message from lock B. By accurately forwarding A's "Request for Assistance" multicast message to the interface connected to lock B after checking based on RFID-ID(b), the 30-second validity period, etc., the router avoids forwarding it to all other locks, thus preventing additional interference to other locks.

[0096] If A reads RFID-ID(z) (at this point, A reads RFID-ID(z) instead of RFID-ID(b), possibly because B took the wrong card), and detects the doorbell button information twice within 30 seconds (at this point, B might have taken the wrong card), A generates and sends a "Request for Assistance" multicast message to 226.1.1.10, containing RFID-ID(z), door lock ID(A), etc., and simultaneously, door lock A starts a 30-second countdown. The router receives this multicast message and checks the multicast forwarding table entry (*, 226.1.1.10) to see if it records interface information matching the RFID-ID(z) (at this point, the router's multicast forwarding table entry (*, 226.1.1.10) only records: the interface connected to B, RFID-ID(b), and interface information with a 30-second validity period), and determines whether the validity period of the interface information has expired. If the router fails to match the RFID-ID (z) information (at this point, the router's multicast forwarding table entry (*, 226.1.1.10) does not contain the interface information for RFID-ID (z), it cannot forward the multicast message containing RFID-ID (z) and discards it. After checking based on RFID-ID (b), 30-second validity period, etc., the router will not forward the multicast message to interfaces that cannot match the RFID-ID (z) information, nor will it forward it to other interfaces connected to other locks, thus avoiding additional interference to other locks caused by forwarding to all other locks.

[0097] If several other events occur during this process, such as lock D's owner d summoning a robot for lock C's owner d using RFID(d), then lock D sends an IGMP assistance message for "assistance call" to the target IP address 226.1.1.10, containing the card number RFID-ID(d) and a validity period of 30 seconds. The router receives and parses the IGMP assistance message for "assistance call" sent by D, extracts the multicast group address 226.1.1.10 and RFID-ID(d), creates or updates the multicast forwarding table entry (*, 226.1.1.10), and records the RFID-ID(d) and the 30-second validity period on the interface that received the above "assistance call" IGMP assistance message in the forwarding table entry (at this time, the interface connected to D, RFID-ID(d), and 30-second validity period are recorded on this interface). When door lock C sends a multicast message requesting assistance to 226.1.1.10, containing RFID-ID(d) and door lock ID(C), the router receives the message and extracts the RFID-ID(d) and door lock ID(C). Then, the router checks its multicast forwarding table entry (*, 226.1.1.10) to see if it records interface information matching the RFID-ID(d) (including the interface connected to door lock D, the RFID-ID(d), and a 30-second validity period). If the interface information's validity period has not expired, the router only forwards the "Request for Assistance" multicast message sent by door lock C to the interface connected to door lock D. Based on the check of the corresponding RFID number recorded in the interface information of the forwarding table entry, the router can only accurately forward the multicast message to the interface whose RFID matches the interface information, and will not forward it to other door locks or their corresponding interfaces.

[0098] When door lock B receives the "Request for Assistance" message from door lock A, it checks the cached robot summoning event information based on the RFID-ID(b) in the message. If it confirms that the RFID-ID(b) is the cached summoning event ID number (door lock ID(B) + timestamp) and other relevant information is also consistent, it unicasts a "Assistance Confirmation" message to door lock A (door lock IP(A) can be extracted from the message forwarded by the router), which includes the RFID-ID(b), door lock ID(B), and whether to confirm the summoning / yes.

[0099] When door lock A receives the "Assistance Confirmation" message from B, it checks if the "Confirm Recall?" result in the message is "Yes". If so, it sends a "Summon Robot" message to the platform, including the door lock ID (A). Simultaneously, door lock A stores the summon robot record for future reference, including the door lock ID (A), confirmation / yes status, summoning RFID / RFID (b), summoned door lock / door lock ID (B), and a timestamp (the clock at which B's reply message was received). The summon robot record is automatically deleted after one year.

[0100] (5) Optional method: Unlike the card swiping order in steps (3) and (4) (RFID card swiping B first and then A), the optional improvement this time is to use the RFID (b) card to swipe A first and then B, and the message sent by the A lock is triggered by the B lock IGMP message in the router to be forwarded to B to realize the forwarding mechanism of related messages.

[0101] The detailed implementation process is explained below:

[0102] When door lock A detects two doorbell button notifications (at this time, b presses the "doorbell" button twice on door lock A to trigger the robot summoning process), it reads RFID-ID(b) (at this time, b swipes the RFID(b) card on door lock A). A extracts RFID-ID(b) and compares it with the RFID-ID numbers in A's resident registration information table one by one. A match fails (at this time, RFID-ID(b) is not the RFID-ID number in A's resident registration information table). After detecting two doorbell button notifications (at this time, b presses the "doorbell" button twice on door lock A to confirm the robot summoning), door lock A sends a "assisted call" multicast message to the target IP address 226.1.1.10, containing the card number RFID-ID(b), validity period of 30 seconds, etc. Meanwhile, lock A caches the robot summoning event, including the summoning event ID (assisted lock ID (A) + timestamp), RFID-ID (b), assisted lock ID / pending, validity period = 60 seconds, etc., and then starts a 60-second countdown. Lock A sends a multicast message "assisted call" to request the router to forward it.

[0103] The router receives and parses the multicast message "Assisted Call" sent by A, extracts the multicast group address 226.1.1.10 and RFID-ID(b), creates or updates the multicast forwarding table entry (*, 226.1.1.10), registers the "Assisted Interface" on the outgoing interface of this forwarding table entry, including the RFID-ID(b), a validity period of 30 seconds, etc., and simultaneously caches the multicast message sent by A (at this time, the purpose of the router caching A's message is to wait for the door lock B to trigger, so as to forward it to B), with a cache time of 120 seconds, and automatically deletes it after expiration (this is to prevent storing too many expired multicast messages). The router creates or updates the multicast forwarding table entry (*, 226.1.1.10), where the outgoing interface of the "Assisted Interface" is connected to the door lock A, and caches A's "Assisted Interface" multicast message containing RFID(b), waiting for the router to find a suitable outgoing interface (*, 226.1.1.10) before forwarding it.

[0104] Door lock B detects two doorbell button notifications (at this time, at a request from a, b leaves door lock A and immediately returns to door lock B, pressing the "doorbell" button twice on door lock B), and reads RFID-ID(b) (at this time, b swipes RFID(b) card on door lock B). B extracts RFID(b) and matches it with the RFID-ID numbers in B's resident registration information table one by one, and a match is successful (at this time, RFID-ID(b) is the RFID-ID number in B's resident registration information table). After detecting two doorbell button notifications (at this time, b presses the "doorbell" button twice on door lock B to confirm the robot summoning), it generates and sends an IGMP assistance message for "assistance call" to the target address 226.1.1.10, including RFID-ID(b), door lock ID(B), etc. At the same time, door lock B caches the "assistance call" record, including the assistance summoning robot ID (door lock ID(B) + timestamp), RFID-ID(b), timestamp, etc. Lock B sends an IGMP message for assistance to request the router to build a multicast forwarding table entry for the outgoing connection B.

[0105] The router receives and parses the IGMP assistance message of "Assistance Call" sent by B, extracts the multicast group address 226.1.1.10 and RFID-ID(b), creates or updates the multicast forwarding table entry (*,226.1.1.10), adds "Assistance Interface" to the outgoing interface list of the forwarding table entry, and records the RFID-ID(b) and the validity period of 30 seconds. At this point, when the router periodically matches the cached "assisted call" multicast messages based on RFID-ID(b) (in this case, the router caches the "assisted call" multicast message sent by door lock A, which contains RFID-ID(b)), and finds that the "assisted interface" of the multicast forwarding table entry (*, 226.1.1.10) contains RFID-ID(b) information, the router forwards the successfully matched cached "assisted call" multicast message sent by door lock A to B through the "assisted interface" of the multicast forwarding table entry (*, 226.1.1.10). After successful forwarding, the router deletes the cached multicast message sent by door lock A (i.e., the "assisted call" multicast message sent by door lock A). The router constructs a multicast forwarding table entry with the outgoing interface record containing door lock B, RFID-ID(b), and a validity period of 30 seconds. It then queries and matches the cached message for A and forwards it to B.

[0106] Door lock B receives and extracts the "Assisted Call" message forwarded by the router from door lock A. It extracts the source IP address (door lock A's IP address, door lock IP (A)), the assisted door lock ID (A), RFID-ID (b), etc. After successfully matching the cached "Assisted Call" record using RFID-ID (b), it unicasts a "Assistance Confirmation" message to door lock IP (A), containing RFID-ID (b), door lock ID (B), and confirmation of the call / recall. Door lock A receives B's "Assistance Confirmation" message and checks if the "Confirmation of Call" result is "Yes." If so, it sends a "Summon Robot" message to the platform, containing door lock ID (A), etc. Simultaneously, door lock A stores the summon robot record for future reference, containing door lock ID (A), confirmation of the call / recall, the calling RFID / RFID (b), the calling door lock / door lock ID (B), and a timestamp (the clock at which B's reply message was received). The summon robot record is automatically deleted after one year.

[0107] (6) Further improvement: The router receives the "assisted call" IGMP message sent by door lock A, creates or updates the multicast forwarding table entry (*, 226.1.1.10), registers the "assisted interface" on the outgoing interface of the forwarding table entry, including the RFID-ID (b) and the source IP address (A) of A, and caches the "assisted call" multicast message sent by door lock A. When door lock B sends an IGMP assist message carrying the RFID-ID (b) and the "assisted call", the router queries the "assisted interface" to obtain the source IP address based on the RFID-ID (b), and then matches the source IP address in the multicast message header. This allows the router to quickly find the cached "assisted call" multicast message sent by A, and then forwards the multicast message to B through the "assisted interface".

[0108] In step (5), in order to forward messages accurately, the router needs to frequently view and understand the internal information of non-standard multicast messages (for example, it needs to query and match the RFID number from the "assisted call" multicast message sent by door lock A). This will cause the router to delve into the internal information of the multicast messages, which will affect the router's performance. Therefore, the following improvements are made:

[0109] The implementation process is explained in detail below, taking step (5) as an example:

[0110] When door lock A detects two doorbell button notifications, it reads the RFID-ID(b) and compares it with the RFID-ID numbers in A's resident registration information table. A match fails. After detecting two doorbell button notifications, door lock A sends two messages to the target IP address 226.1.1.10: first, an IGMP message for "Assisted Call," containing the card number, RFID-ID(b), and a validity period of 30 seconds; and second, a multicast message for "Assisted Call," containing the card number, RFID-ID(b), and a validity period of 30 seconds. Simultaneously, A caches the robot summoning event, containing the summoning event ID (Assisted Lock ID(A) + timestamp), RFID-ID(b), Assisted Lock ID / Pending, and validity period = 60 seconds, and then begins a 60-second countdown. Door lock A sends the IGMP message for "Assisted Call" and the multicast message for "Assisted Call" to request the router to forward the message.

[0111] The router first receives and parses the IGMP message "Assisted Call" sent by A, extracts the multicast group address 226.1.1.10 and RFID-ID(b), creates or updates the multicast forwarding table entry (*, 226.1.1.10), registers the "Assisted Interface" in the outgoing interface list of this forwarding table entry, and records the source IP address (taken from the source IP of the IGMP message, i.e., the IP address of door lock A, door lock IP (A)), RFID-ID(b), validity period of 30 seconds, interface connected to door lock A, etc.; then the router receives and parses the multicast message "Assisted Call" sent by A, and caches the multicast message (including the source IP in the message header, etc.) for 120 seconds, after which it is automatically deleted. The router creates or updates a multicast forwarding table entry (*, 226.1.1.10), associates the door lock IP (A) and RFID-ID (b) on the outgoing interface of the "assisted interface", and caches the multicast message of "assisted call" containing RFID (b) of A, and forwards it after the router finds a suitable outgoing interface (*, 226.1.1.10).

[0112] After detecting two doorbell button presses, door lock B reads the RFID-ID(b) and successfully matches it with the RFID-ID number in B's resident registration information table. It then generates and sends an IGMP assistance message for "Assistance Call" to the target address 226.1.1.10, containing the RFID-ID(b), door lock ID(B), etc. Simultaneously, door lock B caches the "Assistance Call" record, including the assistance summoning robot ID (door lock ID(B) + timestamp), RFID-ID(b), timestamp, etc. Door lock B sends the "Assistance Call" IGMP message to request the router to construct a multicast forwarding table entry for the outgoing connection to B.

[0113] The router receives and parses the IGMP assistance message of "Assistance Call" sent by B, extracts the multicast group address 226.1.1.10 and RFID-ID(b), creates or updates the multicast forwarding table entry (*,226.1.1.10), adds "Assistance Interface" to the outgoing interface list of the forwarding table entry, and records RFID-ID(b), the interface connected to B, etc. The router immediately queries and matches the RFID-ID (b) in the "Assisted Interface" of the multicast forwarding table entry (*, 226.1.1.10) (at this time, the information recorded in the "Assisted Interface" includes the RFID-ID (b)). If a match is found, the router queries the source IP address in the corresponding "Assisted Interface" using the RFID-ID (b) (at this time, the extracted IP address is the door lock IP (A)). Then, the router queries the cached multicast message using the door lock IP (A) (at this time, the multicast message with the door lock IP (A) address in the cache is a multicast message of "Assisted Call" sent by A. The multicast message can be directly queried by querying the multicast message header information without needing to understand the internal information of the multicast message). Then, the router forwards the queried multicast message through the "Assisted Interface" of the multicast forwarding table entry (*, 226.1.1.10) (at this time, the "Assisted Interface" corresponds to the interface of door lock B). The router uses the RFID number carried by B to query the source IP address in the "assisted interface," then uses that source IP address to find the cached multicast message, and finally forwards the multicast message from the "assisted interface" to B. This method can accurately locate the multicast message without in-depth analysis of the multicast message content; it can do so by associating the RFID number with the source IP address and directly matching the source IP address in the multicast message header.

[0114] Door lock B receives and extracts the multicast message from A's "Assisted Call" forwarded by the router. It extracts the source IP address (door lock A's IP address, door lock IP (A)), the assisted door lock ID (A), RFID-ID (b), etc. After successfully matching the cached "Assisted Call" event record using RFID-ID (b), it unicasts a "Assistance Confirmation" message to door lock IP (A), containing RFID-ID (b), door lock ID (B), and whether it confirms the call / yes. Door lock A receives B's "Assistance Confirmation" message, checks if the "Confirmation of Call" result is "yes," and sends a "Summon Robot" message to the platform, containing door lock ID (A), etc. Simultaneously, door lock A stores the summon robot record for future reference, containing door lock ID (A), confirmation / yes, summoning RFID / RFID (b), summoned door lock / door lock ID (B), and a timestamp (the clock at which B's reply message was received). The summon robot record is automatically deleted after one year.

[0115] (7) The platform receives the “Summon Robot” message sent by door lock A and assigns the robot to go to A to perform facial recognition and unlock the door for the owner a.

[0116] Detailed explanation of the implementation process: The platform receives and caches the "Summon Robot" message sent by door lock A, dispatches the robot (robot dispatching is not the focus of this invention and will not be elaborated further), sends the door lock ID (A), door lock IP (A), etc. from the "Summon Robot" message to the robot, and at the same time, the platform sends a reply message to door lock A indicating that the robot has been dispatched. Door lock A receives the reply message from the platform and displays "Robot successfully summoned, please wait" on its display screen. The robot receives the dispatch instructions from the platform, autonomously navigates to door lock A according to the room ID (A) (autonomous navigation and walking of the robot are not the focus of this invention and will not be elaborated further), establishes a connection with door lock A, and then performs facial recognition comparison for door lock A. If the facial recognition is successful, the door is unlocked and opened for door lock A.

[0117] The system ultimately determines whether a neighbor can summon the robot on behalf of another by using RFID card swiping authorization from a neighbor, coordinating with the doorbell button on the door lock, and confirming the countdown timer for the same RFID-activated robot summoning function on the platform.

[0118] As can be seen, based on the preset trigger operation detected by the first lock B and the RFID tag information read, an assistance request IGMP multicast message is generated and sent to the router; based on the assistance request IGMP multicast message, the interface information associated with the RFID tag information and the validity period are recorded in the multicast forwarding table entry, and the multicast message is cached; based on the preset trigger operation detected by the second lock A and the same RFID tag information read, an assistance request multicast message containing the RFID tag information is generated and sent to the router; based on the RFID tag information and the multicast forwarding table entry, after verifying that the validity period has not expired, the message is forwarded to the first lock B, and the first lock B sends an assistance confirmation message to the second lock A, triggering the robot summoning command, thereby achieving low-latency and high-reliability door lock collaborative control.

[0119] Another embodiment of the present invention provides a system for multi-door lock collaborative processing, see [link to relevant documentation]. Figure 3 The system may include:

[0120] Trigger module 301 is used to trigger assistance request and multicast registration: based on the preset trigger operation detected by the first door lock B and the RFID identification information read, it generates an assistance request IGMP multicast message containing RFID identification information and validity period, and sends it to the router;

[0121] Module 302 is used for constructing and caching multicast forwarding entries: based on the IGMP multicast assistance request message received by the router, it records the interface information and validity period associated with the RFID identification information in the multicast forwarding entry and caches the multicast message;

[0122] Forwarding module 303 is used for the triggered and multicast forwarding of the assisted door lock request: Based on the preset triggering operation detected by the second door lock A and the same RFID tag information read, it generates an assisted request multicast message containing RFID tag information and sends it to the router;

[0123] The assistance module 304 is used for precise message routing and assistance confirmation: based on the router matching the RFID identification information in the multicast message of the assistance request with the multicast forwarding table entry, after verifying that the validity period has not expired, the message is forwarded to the first door lock B, and the first door lock B sends an assistance confirmation message to the second door lock A, triggering the robot summoning command.

[0124] As can be seen, based on the preset trigger operation detected by the first lock B and the RFID tag information read, an assistance request IGMP multicast message is generated and sent to the router; based on the assistance request IGMP multicast message, the interface information associated with the RFID tag information and the validity period are recorded in the multicast forwarding table entry, and the multicast message is cached; based on the preset trigger operation detected by the second lock A and the same RFID tag information read, an assistance request multicast message containing the RFID tag information is generated and sent to the router; based on the RFID tag information and the multicast forwarding table entry, after verifying that the validity period has not expired, the message is forwarded to the first lock B, and the first lock B sends an assistance confirmation message to the second lock A, triggering the robot summoning command, thereby achieving low-latency and high-reliability door lock collaborative control.

[0125] 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.

[0126] Specifically, in this embodiment, the storage medium can be configured to store a computer program for performing the following steps:

[0127] S201, Trigger Assistance Request and Multicast Registration: Based on the preset trigger operation detected by the first door lock B and the RFID identification information read, generate an Assistance Request IGMP multicast message containing RFID identification information and validity period, and send it to the router;

[0128] S202, Multicast forwarding table entry construction and caching: Based on the IGMP multicast assistance request message received by the router, record the interface information and validity period associated with the RFID identification information in the multicast forwarding table entry, and cache the multicast message;

[0129] S203, Assisted Lock Request Triggering and Multicast Forwarding: Based on the preset triggering operation detected by the second lock A and the same RFID tag information read, generate an assisted request multicast message containing RFID tag information and send it to the router;

[0130] S204, Precise Message Routing and Assistance Confirmation: Based on the router's matching of the RFID identification information in the multicast message of the assistance request with the multicast forwarding table entry, after verifying that the validity period has not expired, the message is forwarded to the first door lock B, and the first door lock B sends an assistance confirmation message to the second door lock A, triggering the robot summoning command.

[0131] As can be seen, based on the preset trigger operation detected by the first lock B and the RFID tag information read, an assistance request IGMP multicast message is generated and sent to the router; based on the assistance request IGMP multicast message, the interface information associated with the RFID tag information and the validity period are recorded in the multicast forwarding table entry, and the multicast message is cached; based on the preset trigger operation detected by the second lock A and the same RFID tag information read, an assistance request multicast message containing the RFID tag information is generated and sent to the router; based on the RFID tag information and the multicast forwarding table entry, after verifying that the validity period has not expired, the message is forwarded to the first lock B, and the first lock B sends an assistance confirmation message to the second lock A, triggering the robot summoning command, thereby achieving low-latency and high-reliability door lock collaborative control.

[0132] 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.

[0133] 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.

[0134] Specifically, in this embodiment, the processor can be configured to perform the following steps via a computer program:

[0135] S201, Trigger Assistance Request and Multicast Registration: Based on the preset trigger operation detected by the first door lock B and the RFID identification information read, generate an Assistance Request IGMP multicast message containing RFID identification information and validity period, and send it to the router;

[0136] S202, Multicast forwarding table entry construction and caching: Based on the IGMP multicast assistance request message received by the router, record the interface information and validity period associated with the RFID identification information in the multicast forwarding table entry, and cache the multicast message;

[0137] S203, Assisted Lock Request Triggering and Multicast Forwarding: Based on the preset triggering operation detected by the second lock A and the same RFID tag information read, generate an assisted request multicast message containing RFID tag information and send it to the router;

[0138] S204, Precise Message Routing and Assistance Confirmation: Based on the router's matching of the RFID identification information in the multicast message of the assistance request with the multicast forwarding table entry, after verifying that the validity period has not expired, the message is forwarded to the first door lock B, and the first door lock B sends an assistance confirmation message to the second door lock A, triggering the robot summoning command.

[0139] As can be seen, based on the preset trigger operation detected by the first lock B and the RFID tag information read, an assistance request IGMP multicast message is generated and sent to the router; based on the assistance request IGMP multicast message, the interface information associated with the RFID tag information and the validity period are recorded in the multicast forwarding table entry, and the multicast message is cached; based on the preset trigger operation detected by the second lock A and the same RFID tag information read, an assistance request multicast message containing the RFID tag information is generated and sent to the router; based on the RFID tag information and the multicast forwarding table entry, after verifying that the validity period has not expired, the message is forwarded to the first lock B, and the first lock B sends an assistance confirmation message to the second lock A, triggering the robot summoning command, thereby achieving low-latency and high-reliability door lock collaborative control.

[0140] 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 method for collaborative processing of multiple door locks, characterized in that, The method includes: Triggering Assistance Request and Multicast Registration: Based on the preset triggering operation detected by the first door lock B and the RFID identification information read, generate an IGMP multicast message containing the RFID identification information and validity period, and send it to the router; Multicast forwarding table entry construction and caching: Based on the IGMP multicast assistance request message received by the router, record the interface information and validity period associated with the RFID identification information in the multicast forwarding table entry, and cache the multicast message; Assisted lock request triggering and multicast forwarding: Based on the preset triggering operation detected by the second lock A and the same RFID tag information read, generate an assistance request multicast message containing RFID tag information and send it to the router; Precise message routing and assistance confirmation: Based on the router's matching of the RFID identification information in the multicast message of the assistance request with the multicast forwarding table entry, after verifying that the validity period has not expired, the message is forwarded to the first door lock B, and the first door lock B sends an assistance confirmation message to the second door lock A, triggering the robot summoning command.

2. The method according to claim 1, characterized in that, The triggering of the assistance request and multicast registration includes: Trigger operation detection: Based on the detection of two consecutive doorbell button presses by the first door lock B, the assistance request process is initiated and a countdown begins; RFID tag verification: Based on the RFID tag information read during the countdown, compare it with the resident registration form of the first door lock B. If there is no match, generate an abnormal prompt containing the RFID tag. Multicast message generation: Based on the detection of two consecutive doorbell button presses, generate an IGMP multicast message carrying the RFID tag, expiration date, and door lock ID; Multicast message sending: The router sends IGMP multicast messages to the preset multicast address, triggering the router to record the interface binding relationship containing the RFID tag and its validity period.

3. The method according to claim 2, characterized in that, The construction and caching of the multicast forwarding table entries includes: Interface information registration: Based on the RFID identifier and source IP address in the IGMP multicast message parsed by the router, mark the interface connected to the first door lock B as the assisting interface in the multicast forwarding table entry and associate it with the validity period; Message caching management: Caches complete IGMP multicast messages, sets a cache timeout, and automatically deletes messages if they are not matched within the timeout period; Conflict handling: When multiple door locks simultaneously send IGMP multicast messages carrying different RFID tags, the router independently records the binding relationship between each RFID tag and the interface.

4. The method according to claim 3, characterized in that, The requested triggering and multicast forwarding of the assisted door lock includes: Assistance request detection: Based on the detection of two consecutive doorbell button presses by the second door lock A, the assistance request process is initiated and a countdown begins; RFID tag matching: Based on the same RFID tag information read within the countdown, compare it with the resident registration form of the second door lock. If no match is found, generate a multicast message requesting assistance. Multicast message encapsulation: Encapsulate the RFID tag, the lock ID of the second lock A, and the request type into the assistance request multicast message; Multicast message targeted transmission: The router sends the assist request multicast message to the same multicast address, triggering the router's matching and forwarding logic.

5. The method according to claim 4, characterized in that, The precise message routing and assistance confirmation include: RFID tag matching: Extract the RFID tag from the multicast message requesting assistance from the router, and query the associated assistance interface in the multicast forwarding table entry; Validity verification: If the validity period of the assistance interface has not expired, the message will be forwarded to the interface of the first door lock B. Assistance confirmation process: Based on the assistance request multicast message received by the first door lock B, verify the consistency between the RFID tag and the cache record, and generate a unicast reply message carrying the confirmation result; Robot summoning triggered: Based on the confirmation result received by the second door lock A, a robot summoning command is sent to the platform, and the operation log is recorded.

6. The method according to claim 5, characterized in that, The robot summoning trigger includes: Instruction encapsulation: Based on the door lock ID and RFID tag in the confirmation result, generate robot scheduling instructions containing target location and authorization verification parameters; Platform interaction: The platform sends dispatch instructions to the robot, triggering the robot to navigate to the location of the second door lock A; Facial recognition authorization: The facial information of the user collected after the robot arrives is compared with the resident registration form stored on the platform. If the verification is successful, the second door lock A will be unlocked.

7. A system for collaborative processing of multiple door locks, characterized in that, The system includes: The triggering module is used to trigger assistance requests and multicast registration: based on the preset triggering operation detected by the first door lock B and the RFID identification information read, it generates an assistance request IGMP multicast message containing RFID identification information and validity period, and sends it to the router; The construction module is used for multicast forwarding table entry construction and caching: based on the IGMP multicast assistance request message received by the router, it records the interface information and validity period associated with the RFID identification information in the multicast forwarding table entry, and caches the multicast message; The forwarding module is used for the triggered and multicast forwarding of the requested assistance from the door lock: based on the preset triggering operation detected by the second door lock A and the same RFID tag information read, it generates a multicast message containing the RFID tag information for the requested assistance and sends it to the router; The assistance module is used for precise message routing and assistance confirmation: based on the router's matching of the RFID identification information in the multicast message of the assistance request with the multicast forwarding table entry, after verifying that the validity period has not expired, the message is forwarded to the first door lock B, and the first door lock B sends an assistance confirmation message to the second door lock A, triggering the robot summoning command.

8. The system according to claim 7, characterized in that, The triggering module is specifically used for: Trigger operation detection: Based on the detection of two consecutive doorbell button presses by the first door lock B, the assistance request process is initiated and a countdown begins; RFID tag verification: Based on the RFID tag information read during the countdown, compare it with the resident registration form of the first door lock B. If there is no match, generate an abnormal prompt containing the RFID tag. Multicast message generation: Based on the detection of two consecutive doorbell button presses, generate an IGMP multicast message carrying the RFID tag, expiration date, and door lock ID; Multicast message sending: The router sends IGMP multicast messages to the preset multicast address, triggering the router to record the interface binding relationship containing the RFID tag and its validity period.

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