Method and system for calling a multi-communication group fusion of an intelligent door lock

Abstract

The application discloses a kind of multi-communication group fusion of intelligent door lock and system, method includes: according to the communication group request initiated by each main control door lock, establish the independent multicast tree with feature vector as identification;According to the merging request sent by first main control door lock, generate multicast message containing target communication group feature vector and digital signature;According to the feature vector exchanged by both main control door locks through secure channel, feature listening registration is initiated by target main control door lock, and boundary feature label rewriting rule is negotiated and established;According to the forwarding path and rewriting rule established, the audio and video stream of both communication groups is realized after feature label rewriting by network boundary router Bidirectional intercommunication.It is realized that multi-communication group can be dynamically isolated and seamlessly fused by using the embodiment of the application, reduce network load and transmission delay, while terminal door lock does not need to perceive opposite end network address or change configuration to realize audio and video intercommunication, improve the expansibility, security and user experience of system.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of intelligent door locks, and particularly relates to a multi-communication group fusion calling method and system of an intelligent door lock. BACKGROUND

[0002] In recent years, with the popularization of smart home and security systems, the demand for audio and video communication between intelligent door locks is increasing, and traditional single-group communication or centralized communication group systems cannot support dynamic, safe and efficient interconnection and intercommunication of multiple door locks. The existing technology relies on central server forwarding or complex network address translation, and has problems such as high delay, poor scalability, complex terminal configuration, and difficulty in direct isolation and fusion between different communication groups, which cannot meet the needs of intelligent door lock clusters in flexible networking, low-delay interaction and privacy protection. SUMMARY

[0003] The purpose of the present application is to provide a multi-communication group fusion calling method and system of an intelligent door lock, to solve the problems in the prior art, to realize dynamic and safe isolation and seamless fusion of multiple communication groups, to reduce network load and transmission delay, and to realize audio and video intercommunication without the need for terminal door locks to perceive the network address of the opposite end or to change the configuration, thereby improving the scalability, security and user experience of the system.

[0004] One embodiment of the present application provides a multi-communication group fusion calling method of an intelligent door lock, which comprises the following steps:

[0005] Independent communication group establishment: according to the communication group request initiated by each master door lock, the participating door locks send IGMP join messages carrying the feature vectors of the groups to the multicast network, and establish independent multicast trees identified by the feature vectors, to realize isolation of audio and video data of different communication groups;

[0006] Communication group merging request triggering: according to the merging request issued by the first master door lock, multicast messages containing the feature vectors and digital signatures of the target communication group are generated, and are forwarded to the target communication group master door lock through the multicast network, to complete the verification and discovery of the merging request;

[0007] Multicast router cooperation: according to the feature vectors exchanged by the master door locks of both sides through a secure channel, the target master door lock initiates feature listening registration, triggers the routers along the way to add out-interface associations for the feature vectors of the other party in the multicast forwarding table, and negotiates to establish boundary feature label rewriting rules;

[0008] Terminal non-perception intercommunication: according to the established forwarding path and rewriting rules, the audio and video streams of the communication groups of both sides realize bidirectional intercommunication after being subjected to feature label rewriting by the network boundary routers, and the participating door locks only perceive the newly added media streams of the group and do not need to perceive the network address of the other party.

[0009] Optionally, the independent communication group establishment comprises:

[0010] The master door lock initiates a communication group: according to the feature vector extracted by the face recognition module of the master door lock, an IGMP join message containing the feature vector, device type and multicast group address is generated, and is sent to the local gateway router;

[0011] Multicast tree establishment: according to the IGMP join message received by the router, the feature vector identifier is attached to the multicast forwarding table (*, G) for the receiving interface, and the mapping relationship from the feature vector to the out-interface is established;

[0012] Participating door lock joining: according to the IGMP join message sent by the participating door lock carrying the same feature vector, the multicast tree is gradually expanded by the routers along the way, forming an independent multicast forwarding path with the master door lock gateway as the root;

[0013] Media stream isolation transmission: according to the feature label header inserted in the audio and video data packet by the sender, the router performs feature matching and only forwards to the associated out-interface, realizing data isolation of different communication groups.

[0014] Optionally, the communication group merging request trigger comprises:

[0015] Merging request generation: according to the merging operation of the first master door lock, an MFTH format multicast message containing the source feature vector, target feature vector, timestamp, random number and digital signature is constructed;

[0016] Multicast network forwarding: according to the multicast group address in the message, the router performs multicast forwarding and floods to all out-interfaces registered with the target feature vector;

[0017] Target master door lock verification: according to the similarity matching between the feature vector built-in the target master door lock and the target feature vector in the message, and verifying the digital signature to confirm the legality and authority of the request;

[0018] Merging confirmation establishment: according to the result of successful verification, the target master door lock generates a merging confirmation message containing session parameters and signature, and replies to the source master door lock through unicast.

[0019] Optionally, the multicast router cooperation comprises:

[0020] Feature vector exchange: according to the secure channel established by the merging confirmation, the original feature vectors of both master door locks are exchanged;

[0021] Listen to the registration trigger: according to the feature vector received by the target master door lock, a feature listening registration message containing the multicast group address, feature vector and lifetime is generated, and is sent to the source master door lock through unicast;

[0022] Router interface association: according to the registration message listened by the router along the way, the multicast group address and the feature vector are extracted, and the out interface association of the opposite feature vector is added on the interface providing forwarding for the message;

[0023] Border rewriting rule establishment: according to the judgment result of the gateway router of the target master lock, the border rewriting rule table item is created for subsequent directional feature replacement of the media stream.

[0024] Optionally, the terminal non-aware interworking includes:

[0025] Media stream directional forwarding: according to the established multicast forwarding path, the media stream of one party is forwarded to the gateway router of another party;

[0026] Feature label rewriting: according to the rewriting rule table of the border router, the matching and replacement operation of the feature label header of the incoming media packet are performed;

[0027] Control instruction proxy execution: according to the cross-communication group control instruction issued by the master lock, the target communication group master lock receives, verifies and executes proxy, and returns the result to the source master lock;

[0028] Session termination cleaning: according to the termination request issued by the master lock, the target master lock coordinates to trigger the network router to gradually clean up the temporarily added out interface association and feature rewriting rule, and restores the independent communication group state.

[0029] Another embodiment of the application provides a multi-communication group fusion call system of an intelligent door lock, the system comprising:

[0030] The establishment module is configured to establish an independent communication group: according to the communication group request initiated by each master lock, the participating door lock sends an IGMP join message carrying the feature vector of the group to the multicast network, establishes an independent multicast tree identified by the feature vector, and realizes the isolation of audio and video data of different communication groups;

[0031] The trigger module is configured to trigger a communication group merging request: according to the merging request issued by the first master lock, a multicast message containing the feature vector and digital signature of the target communication group is generated, and is forwarded to the target communication group master lock through the multicast network to complete the verification and discovery of the merging request;

[0032] The coordination module is configured to coordinate the multicast router: according to the feature vector exchanged by the master locks of both parties through the secure channel, the target master lock initiates feature listening registration, triggers the routers along the way to add out interface association for the feature vector of the opposite party in the multicast forwarding table, and negotiates to establish the border feature label rewriting rule;

[0033] An intercommunication module is used for terminal non-aware intercommunication, according to the established forwarding path and rewriting rules, the audio and video streams of the communication groups of the two parties are intercommunicated bidirectionally after feature label rewriting by the network border router, and the participant door lock only perceives the newly added media stream of the group and does not need to perceive the network address of the other party.

[0034] Yet another embodiment of the present application provides a storage medium having a computer program stored therein, wherein the computer program is configured to execute the method described in any of the above embodiments when running.

[0035] Yet another embodiment of the present application provides an electronic device comprising a memory having a computer program stored therein and a processor configured to execute the computer program to perform the method described in any of the above embodiments.

[0036] Compared with the prior art, the method for calling a meeting of multiple communication groups of a smart door lock provided by the present application can realize dynamic and safe isolation and seamless fusion of multiple communication groups, reduce network load and transmission delay, and enable the terminal door lock to realize audio and video intercommunication without perceiving the network address of the other end or changing the configuration, thereby improving the expansibility, security and user experience of the system. BRIEF DESCRIPTION OF DRAWINGS

[0037] Figure 1 A hardware structure block diagram of a computer terminal of the method for calling a meeting of multiple communication groups of a smart door lock provided by the embodiment of the present application;

[0038] Figure 2 A flowchart of the method for calling a meeting of multiple communication groups of a smart door lock provided by the embodiment of the present application;

[0039] Figure 3 A meeting calling mechanism diagram of the method for calling a meeting of multiple communication groups of a smart door lock provided by the embodiment of the present application;

[0040] Figure 4 A structure diagram of a system for calling a meeting of multiple communication groups of a smart door lock provided by the embodiment of the present application. DETAILED DESCRIPTION

[0041] The embodiments described below with reference to the drawings are exemplary and are intended to explain the present application only, and cannot be interpreted as a limitation on the present application.

[0042] With the rapid development of smart home and community security technology, smart door locks have evolved from simple access control devices to important portals for home and community communication. Modern smart door locks integrate cameras, microphones, speakers and network modules, supporting not only remote door opening, video intercom, but also initiating multi-party video communication groups. In many communities and homes, multiple door lock communication groups may be conducted simultaneously, for example, A, B and C are holding a meeting to discuss community security matters, while D, E and F are holding a family communication group in another area. When there is a need for multi-party joint decision-making or emergency coordination, it is necessary to temporarily merge two independent communication groups into a plenary session without interrupting the original communication group process and exposing the real network address of each door lock.

[0043] Traditional communication group merging methods usually require a central server to forward media streams, which not only increases bandwidth consumption and transmission delay, but also requires terminals to re-negotiate network addresses and session parameters, which is extremely unsuitable for door lock devices with limited computing resources. Although existing multicast technology can reduce bandwidth consumption, it lacks flexible communication group isolation and merging mechanisms, and cannot achieve fine-grained management of "different meetings in the same group". Therefore, there is an urgent need for a lightweight, secure and automatically merged multi-communication group interworking solution that can seamlessly integrate communication groups while maintaining multicast efficiency.

[0044] The embodiment of the present application first provides a multi-communication group fusion and holding method of a smart door lock, which can be applied to electronic devices such as computer terminals, specifically, ordinary computers, etc.

[0045] The following will be described in detail by taking the computer terminal as an example. Figure 1 The hardware structure block diagram of the computer terminal of the multi-communication group fusion and holding method of a smart door lock provided by the embodiment of the present application is shown in the figure. Figure 1 As shown in the figure, the computer device includes a processor, a memory and a network interface connected through a system bus, wherein the memory can include a non-volatile storage medium and an internal memory.

[0046] The non-volatile storage medium can store an operating system and a computer program. The computer program includes program instructions that, when executed, can cause the processor to execute any multi-communication group fusion and holding method of a smart door lock.

[0047] The processor is used to provide computing and control capabilities to support the operation of the entire computer device.

[0048] The internal memory provides an environment for the running of a computer program in a nonvolatile storage medium, which, when executed by the processor, can enable the processor to perform any kind of intelligent door lock multi-communication group fusion method.

[0049] The network interface is used for network communication, such as sending assigned tasks. Figure 1 The structure shown in the figure is only a block diagram of part of the structure related to the scheme of the present application, and does not constitute a limitation on the computer device to which the scheme of the present application is applied. The specific computer device can include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0050] It should be understood that the processor can be a central processing unit (CPU), and the processor 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 gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0051] Referring to Figure 2 and Figure 3 Embodiments of the present application provide a multi-communication group fusion method for intelligent door locks, which can include the following steps:

[0052] S201, independent communication group establishment: according to the communication group request initiated by each master door lock, the participating door lock sends an IGMP join message carrying the feature vector of the group to the multicast network, establishes an independent multicast tree identified by the feature vector, and realizes the isolation of audio and video data of different communication groups; specifically, the independent communication group establishment includes:

[0053] Master door lock initiates communication group: according to the feature vector extracted by the face recognition module of the master door lock, an IGMP join message containing the feature vector, device type and multicast group address is generated and sent to the local gateway router;

[0054] Multicast tree establishment: according to the IGMP join message received by the router, the feature vector identifier is attached to the multicast forwarding table (*, G) for the receiving interface, and the mapping relationship from the feature vector to the out-interface is established;

[0055] Meeting lock join: according to the IGMP join message carrying the same feature vector sent by the meeting lock, the multicast tree is gradually expanded by the routers along the way, forming an independent multicast forwarding path with the master lock gateway as the root;

[0056] Media stream isolation transmission: according to the feature label header inserted in the audio and video data packet by the sender, the router performs feature matching and only forwards to the associated out interface, realizing data isolation of different communication groups.

[0057] S202, communication merging request trigger: according to the merging request issued by the first master lock, a multicast message containing the target communication group feature vector and digital signature is generated, which is forwarded to the target communication group master lock through the multicast network to complete the verification and discovery of the merging request; Specifically, the communication merging request trigger includes:

[0058] Merging request generation: according to the merging operation of the first master lock, an MFTH format multicast message containing the source feature vector, target feature vector, timestamp, random number and digital signature is constructed;

[0059] Multicast network forwarding: according to the multicast group address in the message, the router performs multicast forwarding and floods to all out interfaces registered with the target feature vector;

[0060] Target master lock verification: according to the similarity matching between the feature vector built-in the target master lock and the target feature vector in the message, and verifying the digital signature to confirm the legality and authority of the request;

[0061] Merging confirmation establishment: according to the result of successful verification, the target master lock generates a merging confirmation message containing the session parameters and signature, and replies to the source master lock through unicast.

[0062] S203, multicast router coordination: according to the feature vectors exchanged by the two master locks through the secure channel, the target master lock initiates feature listening registration, triggers the routers along the way to add out interface association for the other feature vector in the multicast forwarding table, and negotiates to establish boundary feature label rewriting rules; Specifically, the multicast router coordination includes:

[0063] Feature vector exchange: according to the secure channel established by the merging confirmation, the original feature vectors are exchanged by the two master locks;

[0064] Listening registration trigger: according to the feature vector received by the target master lock, a feature listening registration message containing the multicast group address, feature vector and lifetime is generated and sent to the source master lock through unicast;

[0065] Router interface association: according to the registration message heard by the router along the way, the multicast group address and the feature vector are extracted, and the out interface association of the opposite feature vector is added on the interface providing forwarding for the message;

[0066] Border rewriting rule establishment: according to the judgment result of the gateway router which controls the target door lock, the border rewriting rule table item is created for subsequent directional feature replacement of the media stream.

[0067] S204, terminal non-perception interworking: according to the established forwarding path and rewriting rule, the audio and video stream of the communication group of the two parties realizes bidirectional interworking after the feature label rewriting of the network border router, and the participating door lock only perceives the newly added media stream of the group and does not need to perceive the opposite network address. Specifically, the terminal non-perception interworking includes:

[0068] Media stream directional forwarding: according to the established multicast forwarding path, the media stream of one party is forwarded to the gateway router of the other party;

[0069] Feature label rewriting: according to the rewriting rule table of the border router, the feature label header of the incoming media packet is matched and replaced;

[0070] Control instruction proxy execution: according to the cross-communication group control instruction issued by the master door lock, the target communication group master door lock receives, verifies and executes proxy, and returns the result to the source master door lock;

[0071] Session termination cleaning: according to the termination request issued by the master door lock, the target master door lock coordinates to trigger the network router to gradually clean up the temporarily added out interface association and feature rewriting rule, and restores the independent communication group state.

[0072] In practical application, one technical scheme example includes the following:

[0073] Core idea:

[0074] The present scheme proposes an intelligent communication group (hereinafter referred to as a conference) fusion mechanism based on "feature label". When each communication group is convened, a unique feature label will be allocated in addition to the use of a unified multicast group address. This label serves as the "pass" for the communication group. The door lock and the router register the multicast group when registering the group address, and associate the feature label. The router forwards the media stream according to the feature label, thereby realizing data isolation of "different meetings in the same group".

[0075] When two communication groups need to be merged, the master door lock of one group initiates a merge request with digital signature to the master door lock of the other group. After verifying the signature and authority, the two groups exchange the original feature vectors through a secure channel. Along the way, the routers automatically learn how to forward the feature labels of the opposite communication group by listening to specific registration messages, and set up "label rewriting points" at the network boundaries to replace the feature labels in the media stream of one group with those of the other group. Finally, the media streams of the two groups are interconnected while maintaining the original multicast paths, and the terminals do not need to be aware of the existence and address of the opposite group. The master door lock and the border router execute the control instructions on behalf of the terminals, realizing truly "end-side unaware" communication group merging.

[0076] Core process:

[0077] Initial establishment phase of independent communication group:

[0078] Door lock A (which internally stores feature a) establishes a first communication group with door locks B and C as the master, using communication group identifier ID_X and associated feature vector a (i.e., ABC all send IGMP join, containing feature a, and the out-interface of the (*, G) entry is attached with feature a), and the multicast group address is G. The audio and video data sent between ABC all contain feature a, so the router will only forward the audio and video data from the interface registered with feature a, and the door locks of non-communication groups cannot receive the communication group audio and video data of this group.

[0079] Door lock D (which internally stores feature d) establishes a second communication group with door locks E and F as the master, using communication group identifier ID_Y and associated feature vector d (i.e., DEF all send IGMP join, containing feature d, and the out-interface of the (*, G) entry is attached with feature d), and the multicast group address is also G. The audio and video data sent between DEF all contain feature d, so the router will only forward the audio and video data from the interface registered with feature d, and the door locks of non-communication groups cannot receive the communication group audio and video data of this group.

[0080] The two multicast trees do not have a common multicast router. Assume that the gateway router of door lock A is router A, and the gateway router of door lock D is router D. All network nodes of the two multicast trees are already networked and can intercommunicate. Door lock A cannot obtain the addresses of door locks D, E, and F, and door lock D cannot obtain the addresses of door locks A, B, and C.

[0081] Communication group merge request triggering phase:

[0082] When door lock A needs to merge ID_X and ID_Y communication groups, it sends a merge request message to multicast router A with the destination address being the multicast group address G. The message contains the target communication group feature vector d and a digital signature (generated by feature vector a). Multicast router A verifies the validity of the signature and confirms that A has the master authority over ID_X.

[0083] The merge request message will be propagated in the large tree of multicast group address G (including the above two multicast trees) and sent out to the interface registered with feature d. Therefore, all door locks DEF can receive the message, but only door lock D has feature d built-in, so door lock D processes the message after similarity comparison and matching; and the source IP is contacted with door lock A.

[0084] Multicast router coordination phase:

[0085] Door lock A sends feature a to door lock D, and door lock D sends a unicast message of feature detection registration message to door lock A, which contains feature a and multicast group G. All routers along the way from gateway router D of door lock D to gateway router A of door lock A can detect the message, and all routers along the way extract multicast group G and feature a from the message and register feature a on the (*, G) table item for the interface receiving the above message. At the same time, door lock D negotiates with router D, and router D is responsible for replacing feature a in the audio and video stream carrying feature a with feature d. Therefore, router A will forward the audio and video stream of communication group ID_X to router D, and router D is responsible for replacing the feature and forwarding the audio and video stream to door locks DEF.

[0086] Similarly, door lock D sends feature d to door lock A...

[0087] Terminal non-aware interworking phase:

[0088] B and C only perceive the addition of media stream of ID_X multicast group, but cannot obtain the real address of the sender; E and F only perceive the addition of media stream of ID_Y multicast group, and also cannot trace the sender. A and D exchange control instructions (such as mute, kick) through a secure channel, and the instructions are executed after being converted by the multicast router: when A requests to mute E, the multicast router converts the instruction into a control message for ID_Y multicast group, which is executed by D.

[0089] Detailed technical solutions:

[0090] System composition and infrastructure:

[0091] The system is composed of multiple intelligent door locks (such as A, B, C, D, E, F), their respective home gateway routers (such as router A, router D), and upstream multicast routers. Each door lock is built-in with a face recognition module that can extract a 256-dimensional face feature vector. All communication groups use the same multicast group address (for example, 239.1.1.1), but use different feature vectors as internal identifiers.

[0092] Each router maintains two kinds of key table entries: Multicast Out Interface Table ( *, G) records the out interface information of multicast group address G, each interface is attached with a set of feature tags; Feature Tracking Table (FTM) indexes the interface set by "multicast group address G + feature vector", records the source interface and lifetime of the feature.

[0093] Initial communication group establishment process:

[0094] The communication group establishment is divided into two stages: multicast tree establishment and communication group session establishment.

[0095] Stage one, multicast tree establishment:

[0096] Communication group X (A, B, C) uses feature vector a, and communication group Y (D, E, F) uses feature vector d. Door lock A, as the master of communication group X, first extracts feature vector a through face recognition. Then it sends an IGMP join message to local router A, which carries feature vector a and device type (master door lock) in the optional field. Router A, upon receiving the message, appends feature a to interface A connected to door lock A in the Multicast Out Interface Table ( *, G), and records the mapping "G + a → interface A (interface connected to door lock A)" in the Feature Tracking Table with a lifetime of T1 (e.g. 3600 seconds).

[0097] Door locks B and C, as participants, also send IGMP join messages to their respective routers, carrying feature vector a and device type (participant door lock). The routers along the way gradually establish forwarding paths, eventually forming a multicast tree rooted at router A. The establishment process of communication group Y is similar, forming another multicast tree rooted at router D.

[0098] Stage two, communication group session establishment:

[0099] After the multicast tree is established, the actual communication group session needs to be established. Door lock A, as the initiator of the communication group, sends a communication group invitation message, which contains the following fields:

[0100] Message type: INVITE (0x01);

[0101] Communication group ID: ID_X;

[0102] Feature vector: a;

[0103] Media capability description: supported audio and video encoding formats, resolutions, frame rates, etc.

[0104] Security parameters: encryption algorithm, key exchange method;

[0105] Sequence number: 1001;

[0106] Timestamp: current system time.

[0107] After receiving the invitation, the door locks B and C send a response message:

[0108] Message type: ACK (0x02);

[0109] Communication group ID: ID_X;

[0110] Feature vector: a;

[0111] Selected media parameters: encoding format, etc. selected from the capability list;

[0112] Security confirmation: agree to encryption scheme;

[0113] Sequence number: 1002 (associated with the sequence number of the invitation message).

[0114] Through this negotiation process, the communication group X is formally established. When transmitting media streams, the sender inserts a feature tag header (MFTH: Multicast Feature Tag Header) in front of the UDP payload, which contains fields such as message type, multicast group address, feature ID, and communication group identification. Routers match the feature ID and only forward media streams to interfaces that have registered the corresponding feature ID, achieving communication group isolation.

[0115] Communication group merging triggers and discovery:

[0116] When the master door lock A of communication group X needs to merge communication group Y, A first constructs a merge request message. This message is sent through multicast group address G, uses MFTH format, and contains the following key fields: message type set to MergeReq (0x01), multicast group address as G (239.1.1.1), source feature vector as a, target feature vector as d, timestamp (e.g., 2025-08-20T10:00:00Z), random number (0x93ab...), sequence number (10086), and digital signature of "{G, ID_X, a, d, timestamp, random number}".

[0117] This message is flooded in the multicast network. The master door lock D of communication group Y has the original feature vector d built-in, which can calculate d and match the target feature ID in the message (cosine similarity > 0.9). After verifying the digital signature to confirm the identity and authority of door lock A, door lock D generates a merge confirmation message and unicast replies to door lock A. The confirmation message contains the certificate fingerprint of door lock D, acceptable session parameters (such as maximum delay, whether to allow media rewriting, etc.), and the signature of the response information.

[0118] Feature registration and path establishment:

[0119] After receiving the merge acknowledgement, the door lock A sends the original feature vector a to the door lock D through a secure channel (e.g., a DTLS: Datagram Transport Layer Security connection). After the door lock D computes a, it sends a feature listening registration message to A unicast, which contains the multicast group address G, the feature vector a, a lifetime (e.g., 120 seconds), a sequence number, and the like.

[0120] Each router that the unicast message passes through listens to the message, extracts G and a, and marks the interface that received the message as a source interface of "G+a", and adds the feature a to the relevant out-interface in the multicast forwarding table entry (*, G). For example, after receiving the message, the router D adds the feature a to the interface that leads to the door lock D; after receiving the message, the router A adds the feature a to the interface that leads to the door lock D.

[0121] The router D listens to the message and determines that it is the multicast IGMP gateway, which sets itself as a border rewriter. This process involves detailed table entry maintenance and message conversion mechanisms.

[0122] Table entry records on the router D:

[0123] The router D maintains two key table entries: a feature listening table (FTM) and a rewriting rule table (RWT).

[0124] Feature listening table (FTM) record example:

[0125] Index: FTM-001;

[0126] Multicast group address: 239.1.1.1;

[0127] Feature ID: a;

[0128] Out-interface list: IF_to_A (interface pointing to the router A);

[0129] Source interface: IF_from_D (interface connected to the door lock D);

[0130] Lifetime: 120 seconds;

[0131] Status: Active;

[0132] Update time: 2025-08-20T10:00:30Z.

[0133] Rewriting rule table (RWT) record example:

[0134] Rule ID: RWT-001;

[0135] In-interface: IF_to_A;

[0136] Match feature: a;

[0137] Action: rewrite-feature;

[0138] New feature: d;

[0139] Direction: to-local;

[0140] Byte count: 0;

[0141] Lifetime: 120 seconds;

[0142] Creation time: 2025-08-20T10:00:35Z.

[0143] Rule ID: RWT-002

[0144] In interface: IF_from_D;

[0145] Match feature: d;

[0146] Action: rewrite-feature;

[0147] New feature: a;

[0148] Direction: to-remote;

[0149] Byte count: 0;

[0150] Lifetime: 120 seconds;

[0151] Creation time: 2025-08-20T10:00:35Z.

[0152] Packet conversion process:

[0153] When a media packet from communication group X (feature a) destined for communication group Y (feature d) arrives at router D:

[0154] The packet arrives on interface IF_to_A with feature tag header:

[0155] MFTH version: 1

[0156] Message type: Media Stream (0x03);

[0157] Multicast group address: 239.1.1.1;

[0158] Feature vector: a (0xA1A1...A1);

[0159] Communication group ID: ID_X;

[0160] Sequence number: 2001.

[0161] Router D queries the rewriting rule table and finds the matching rule RWT-001;

[0162] Perform feature rewriting operation, change feature vector from a to d;

[0163] Update byte counter, recalculate packet length;

[0164] Forward to local interfaces IF_to_E and IF_to_F.

[0165] The rewritten packet feature tag header becomes:

[0166] MFTH version: 1;

[0167] Message type: media stream (0x03);

[0168] Multicast group address: 239.1.1.1;

[0169] Feature vector: d (0xD2D2...D2);

[0170] Communication group ID: ID_X;

[0171] Sequence number: 2001.

[0172] The reverse transmission process is similar, and the feature d to a conversion is realized through rule RWT-002.

[0173] Control instruction proxy mechanism:

[0174] Control instructions are executed by the master lock agent. For example, lock A wants to mute E in communication group Y, lock A sends a control instruction proxy message, specifying the target communication group ID (ID_Y), the target device (E), the action (mute), the sequence number, and the signature.

[0175] Router D (border router): only packet routing and forwarding according to feature tags.

[0176] Lock D (proxy execution party): as the master of communication group Y, it receives and parses instructions, verifies permissions, and executes the instructions on behalf of it within its communication group. It is a "smart proxy".

[0177] Step 1: instruction initiation and encapsulation;

[0178] When lock A needs to mute device E in communication group Y, it constructs a control instruction request packet.

[0179] The packet uses MFTH format, and the destination address is multicast group address G, but its feature ID is set to the feature d of the target communication group

[0180] Step 2: network routing and forwarding;

[0181] The door-lock A sends the message to the multicast address G.

[0182] The multicast routers (including router A, D) consult their multicast forwarding table (*, G) according to the feature vector d in the message.

[0183] The router discovers that the message needs to be forwarded to all interfaces that have registered the feature d, i.e. the members of the communication group Y (door-locks D, E, F).

[0184] The message is delivered to door-locks D, E, F.

[0185] Third step: instruction reception, verification and proxying;

[0186] Identification and filtering:

[0187] Door-locks E and F receive this message, parse it and find out that the message type is Control_Request and the target communication group is ID_Y, but they are not the master, so they ignore and discard the message.

[0188] Door-lock D, as the master of the communication group Y, recognizes that this is an external control instruction that needs to be processed by it.

[0189] Verification and authorization:

[0190] Door-lock D verifies the digital signature using the pre-stored public key of door-lock A, confirming that the instruction indeed comes from the legitimate external master door-lock A.

[0191] Door-lock D consults the local policy to determine whether door-lock A has the right to perform the "mute" operation on device E of the communication group Y.

[0192] Instruction conversion and execution:

[0193] After verification, door-lock D starts "proxying".

[0194] Door-lock D generates a new mute instruction according to the instruction content, which conforms to the internal format of the communication group Y.

[0195] Door-lock D performs the mute operation on device E through the internal communication mechanism of the communication group Y (for example, sending a communication group internal control packet with feature ID d to the multicast group address G).

[0196] Fourth step: result return;

[0197] After door-lock D finishes execution, it generates a control instruction response message and returns it directly to door-lock A.

[0198] The response message is routed through the network and finally reaches door-lock A.

[0199] After door lock A verifies the signature of door lock D, it confirms that the instruction has been executed successfully.

[0200] Session termination and cleanup:

[0201] Either master door lock can initiate the session termination procedure. When door lock A, the master of communication group X, decides to terminate the merged session with communication group Y, it constructs a specific session termination request message. The message is in the MFTH format, with the following key fields set: message type is Terminate (0x06), multicast group address is the unified multicast group G (e.g. 239.1.1.1), but the feature ID field is set to the feature d of the target communication group Y. This setting is crucial, as it ensures that the termination request message can be accurately delivered to all participants of communication group Y, especially its master door lock D, through the existing multicast forwarding path. The payload of the message contains the termination scope (indicating termination of the merged session only, not the original communication group), a termination reason code (e.g. normal end, error, etc.), a unique sequence number, and a digital signature generated based on the private key of door lock A, to verify the legitimacy and integrity of the request.

[0202] After the termination request message is sent, the multicast routers in the network forward it according to its destination multicast address G and feature vector d. These routers do not parse or process the payload content of the message, but only act as a forwarding pipeline to ensure that the message eventually reaches all members of communication group Y, including door locks D, E, and F. Door locks E and F, as ordinary participants, discover after parsing the message that the message type is a termination request and that they are not the master, and will choose to ignore and discard the message. Door lock D, as the master of communication group Y, is responsible for receiving and processing the request. Door lock D first verifies the digital signature of the message to confirm that the request indeed comes from the legitimate initiator door lock A, and checks its authority. After verification, door lock D immediately begins to coordinate the termination and cleanup process. It first marks the state of the merged session as "terminating" locally, and stops generating or forwarding any media streams related to this session.

[0203] Subsequently, door lock D needs to trigger the cleanup work at the network level. Instead of directly instructing the routers, it sends a "de-register feature" instruction message to its local gateway router D. This message is a unicast message, whose content indicates that router D needs to clear the temporary out-interface associations and feature rewriting rules added when providing forwarding services for feature vector a. After receiving the instruction from door lock D, router D starts a gradual, multi-stage cleanup procedure to ensure smooth transition of the network and avoid traffic interruption.

[0204] The first stage of the cleanup process is to immediately stop media forwarding. Router D, on its forwarding plane, first suspends forwarding any media stream carrying feature d to the out-interface temporarily added for the merged session (i.e. the interface pointing to the direction of communication group X). At the same time, it also buffers the media stream from the direction of communication group X, feature a, or directly returns a stream unreachable notification, thus quickly blocking the bidirectional media data transmission. The first stage is usually completed within milliseconds.

[0205] The second stage is to clear the relevant dynamic entries in the feature tracking table (FTM). Router D queries all the entries related to the current merged session in its FTM table, especially those out-interface records dynamically added for feature a. The system checks the creation time and sequence number source of these entries, and confirms that they match the termination request. After confirmation, the status of these entries is marked as "to be deleted", and a short delay (e.g. 1 second) is started to ensure that all ongoing messages are properly processed before the forwarding rules are completely removed from the data plane.

[0206] The third stage is to update the multicast forwarding table (G). After confirming that the FTM table is cleaned up, router D begins to adjust its core multicast forwarding table. It completely removes the out-interface associations temporarily added in the (G) table entries to support feature a. For example, it deletes the association "out-interface IF_to_A: feature set {a}", so that the forwarding table returns to the state before the merged session was established, and only retains the relevant information for feature d of communication group Y. All released resources, such as memory and counters, are also recovered in this stage.

[0207] The entire cleanup process is designed to be completed within 10 seconds. After completing its own cleanup, router D may propagate this cleanup information to upstream routers. Finally, door lock D sends a termination confirmation response message to door lock A, which is routed using feature vector a, carries the final status code and signature, and announces the successful termination and cleanup of the entire session. At this point, the network state returns to its original state, and communication group X and communication group Y return to the state of independent multicast tree, and continue to operate normally as if the merged session never happened.

[0208] Advantages:

[0209] The present scheme realizes the safe and seamless fusion of multiple communication groups, and has the following significant advantages:

[0210] Firstly, the terminal does not need to be aware of the address and state of the other party, and the addressing and forwarding are automatically completed by the network, reducing the complexity and power consumption of the terminal. Tests show that the power consumption of the door lock during the communication group fusion process increases by less than 5%, and the battery life is slightly affected.

[0211] Second, through feature label isolation and rewriting, both the security isolation between communication groups and the seamless interconnection after merging are realized, and both privacy and collaboration needs are considered. The control instruction answering mechanism ensures the reliability and security of the operation, and all operations can be audited and traced.

[0212] Third, the system has good scalability, supports multiple communication groups merging at the same time, supports dynamic joining and exiting, supports different network topologies and device types, and can be widely applied to smart home, community security, remote care and other scenarios.

[0213] This scheme realizes technical innovation in many aspects:

[0214] The concept of "feature tag header" (MFTH) is proposed, which sinks the communication group identifier from the application layer to the network layer, so that the router can perform fine flow isolation and forwarding based on the feature label. This design maintains the efficiency of multicast and realizes accurate control similar to unicast.

[0215] The "on-the-way listening registration" mechanism is designed, which triggers the router to automatically learn the cross-domain feature label path through unicast messages, without the need for manual configuration of the route, realizing the plug-and-play communication group fusion. This mechanism is more flexible and efficient than traditional multicast routing protocols.

[0216] The "boundary label rewriting" strategy is introduced, which realizes the seamless interconnection of double communication groups by rewriting the feature label on the premise of maintaining end-to-end media encryption. This scheme not only guarantees security, but also avoids the computational overhead of media re-encryption.

[0217] A complete control instruction answering and state synchronization mechanism is constructed, which enables the master door lock to execute control operations across communication groups, and the entire process is auditable and traceable. This mechanism is more lightweight and flexible than the traditional gateway proxy scheme.

[0218] As can be seen, according to the communication group request initiated by each master door lock, the participating door locks send IGMP join messages carrying the feature vector of the group to the multicast network, establishing an independent multicast tree identified by the feature vector; according to the merging request issued by the first master door lock, a multicast message containing the feature vector of the target communication group and a digital signature is generated; according to the feature vector exchanged by the master door locks of both sides through the secure channel, the target master door lock initiates feature listening registration and negotiates to establish boundary feature label rewriting rules; according to the established forwarding path and rewriting rules, the audio and video streams of both communication groups are rewritten by the network border router after the feature label, realizing bidirectional interconnection, so as to realize dynamic security isolation and seamless fusion of multiple communication groups, reduce network load and transmission delay, and at the same time, the terminal door lock does not need to perceive the network address of the opposite end or change the configuration to realize audio and video interconnection, improving the scalability, security and user experience of the system.

[0219] Another embodiment of the present invention provides a multi-communication group fusion calling system for smart door locks, see [link to relevant documentation]. Figure 4 The system may include:

[0220] Module 401 is used to establish independent communication groups: based on the communication group requests initiated by each master door lock, the participating door locks send IGMP join messages carrying the feature vector of their group to the multicast network to establish an independent multicast tree identified by the feature vector, thereby achieving audio and video data isolation between different communication groups;

[0221] Trigger module 402 is used for communication combination and request triggering: based on the merger request issued by the first master lock, it generates a multicast message containing the target communication group feature vector and digital signature, and forwards it to the target communication group master lock through the multicast network to complete the verification and discovery of the merger request;

[0222] The collaboration module 403 is used for multicast router collaboration: based on the feature vectors exchanged by the two master control locks through the secure channel, the target master control lock initiates feature listening registration, triggers the routers along the way to add the outgoing interface association for the other party's feature vector in the multicast forwarding table, and negotiates to establish boundary feature label rewriting rules;

[0223] Interoperability module 404 is used for seamless interoperability between terminals: Based on the established forwarding path and rewriting rules, the audio and video streams of both communication groups are rewritten with feature tags by the network boundary router to achieve bidirectional interoperability. The participating door locks only need to be aware of the newly added media streams in their own group and do not need to be aware of the other party's network address.

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

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

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

[0227] 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 fusion conferencing multiple communication groups in a smart door lock, characterized in that, The method includes: Independent communication group establishment: Based on the communication group request initiated by each master door lock, the participating door lock sends an IGMP join message carrying the face feature vector of the group to the multicast network, and establishes an independent multicast tree identified by the feature vector to achieve audio and video data isolation between different communication groups; Communication group merge request trigger: Based on the merge request issued by the first master lock, a multicast message containing the target communication group feature vector and digital signature is generated and forwarded to the target communication group master lock through the multicast network to complete the verification and discovery of the merge request; Multicast router collaboration: Based on the feature vectors exchanged between the two master control locks through the secure channel, the target master control lock initiates feature listening registration, triggering the routers along the way to add the outgoing interface association for the other party's feature vector in the multicast forwarding table, and negotiate to establish boundary feature label rewriting rules; Terminal-insensitive interoperability: Based on the established forwarding path and rewriting rules, the audio and video streams of both communication groups are rewritten with feature tags by the network boundary router to achieve bidirectional interoperability. The participating door locks only need to be aware of the newly added media streams in their own group and do not need to be aware of the other party's network address.

2. The method according to claim 1, characterized in that, The establishment of the independent communication group includes: The master door lock initiates a communication group: Based on the feature vector extracted by the face recognition module of the master door lock, it generates an IGMP join message containing the feature vector, device type and multicast group address, and sends it to the local gateway router; Multicast tree establishment: Based on the IGMP join message received by the router, a feature vector identifier is appended to the receiving interface in the multicast forwarding table (*,G), and a mapping relationship between the feature vector and the receiving interface is established; where G is the multicast group address. Joining the meeting door lock: Based on the IGMP join messages carrying the same feature vector sent by the meeting door lock, the multicast tree is gradually expanded by the routers along the way to form an independent multicast forwarding path with the master door lock gateway as the root; Media stream isolation transmission: Based on the feature tag header inserted by the sender in the audio and video data packets, the router performs feature matching and forwards the data only to the associated outgoing interface, thereby achieving data isolation between different communication groups.

3. The method according to claim 2, characterized in that, The communication combination and request triggering includes: Merge request generation: Based on the merge operation of the first master lock, construct a multicast message in MFTH format containing a feature tag header including source feature vector, target feature vector, timestamp, random number and digital signature; Multicast network forwarding: Based on the multicast group address in the message, the router performs multicast forwarding and floods the message to all outgoing interfaces that have registered the target feature vector. Target master lock verification: The similarity is matched between the feature vector built into the target master lock and the target feature vector in the message, and the digital signature is verified to confirm the legality and authorization of the request; Merge confirmation establishment: Based on the successful verification result, the target master lock generates a merge confirmation message containing session parameters and a signature, and replies to the source master lock via unicast.

4. The method according to claim 3, characterized in that, The multicast router collaboration includes: Feature vector exchange: Based on the established security channel confirmed by the merger, the original feature vectors are exchanged by the master locks of both parties; Listening registration trigger: Based on the feature vector received by the target master lock, generate a feature listening registration message containing the multicast group address, feature vector and lifetime, and send it to the source master lock via unicast; Router interface association: Based on the registration messages detected by routers along the route, extract the multicast group address and feature vector, and add the outgoing interface association of the other party's feature vector to the interface that provides message forwarding; Boundary rewriting rule establishment: Based on the judgment result of the gateway router of the target master lock, set itself as the boundary rewriter and create feature label rewriting rule entries for subsequent directional feature replacement of media streams.

5. The method according to claim 4, characterized in that, The seamless interoperability between terminals includes: Media stream forwarding: Based on the established multicast forwarding path, the media stream of one party is forwarded to the gateway router of the other party; Feature tag rewriting: Based on the rewriting rule table of the border router, the feature tag header of the incoming media packet is matched and replaced. Control command response and execution: Based on the cross-communication group control command issued by the master lock, the target communication group master lock receives, verifies and executes it on behalf of the master lock, and returns the result to the source master lock; Session termination cleanup: Based on the termination request issued by the master lock, the target master lock coordinates and triggers the network router to gradually clean up the temporarily added outgoing interface associations and feature rewriting rules, and restore the independent communication group state.

6. A multi-communication group fusion calling system for a smart door lock, characterized in that, The system includes: The module is used to establish independent communication groups: based on the communication group requests initiated by each master door lock, the participating door locks send IGMP join messages carrying the face feature vectors of their respective groups to the multicast network, establish an independent multicast tree identified by the feature vectors, and realize the isolation of audio and video data of different communication groups; The triggering module is used for communication combination and request triggering: based on the merging request issued by the first master lock, it generates a multicast message containing the target communication group feature vector and digital signature, and forwards it to the target communication group master lock through the multicast network to complete the verification and discovery of the merging request; The collaboration module is used for multicast router collaboration: based on the feature vectors exchanged between the two master control locks through the secure channel, the target master control lock initiates feature listening registration, triggering the routers along the way to add the outgoing interface association for the other party's feature vector in the multicast forwarding table, and negotiate to establish boundary feature label rewriting rules; Interoperability module for seamless interoperability between terminals: Based on the established forwarding path and rewriting rules, the audio and video streams of both communication groups are rewritten with feature tags by the network boundary router to achieve bidirectional interoperability. The participating door locks only need to be aware of the newly added media streams in their own group and do not need to be aware of the other party's network address.

7. The system according to claim 6, characterized in that, The establishment module is specifically used for: The master door lock initiates a communication group: Based on the feature vector extracted by the face recognition module of the master door lock, it generates an IGMP join message containing the feature vector, device type and multicast group address, and sends it to the local gateway router; Multicast tree establishment: Based on the IGMP join message received by the router, a feature vector identifier is appended to the receiving interface in the multicast forwarding table (*,G), and a mapping relationship between the feature vector and the receiving interface is established; where G is the multicast group address. Joining the meeting door lock: Based on the IGMP join messages carrying the same feature vector sent by the meeting door lock, the multicast tree is gradually expanded by the routers along the way to form an independent multicast forwarding path with the master door lock gateway as the root; Media stream isolation transmission: Based on the feature tag header inserted by the sender in the audio and video data packets, the router performs feature matching and forwards the data only to the associated outgoing interface, thereby achieving data isolation between different communication groups.

8. The system according to claim 7, characterized in that, The triggering module is specifically used for: Merge request generation: Based on the merge operation of the first master lock, construct a multicast message in MFTH format containing a feature tag header including source feature vector, target feature vector, timestamp, random number and digital signature; Multicast network forwarding: Based on the multicast group address in the message, the router performs multicast forwarding and floods the message to all outgoing interfaces that have registered the target feature vector. Target master lock verification: The similarity is matched between the feature vector built into the target master lock and the target feature vector in the message, and the digital signature is verified to confirm the legality and authorization of the request; Merge confirmation establishment: Based on the successful verification result, the target master lock generates a merge confirmation message containing session parameters and a signature, and replies to the source master lock via unicast.

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-5 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-5.

Images