Method and System for Controlling Targets Using a MESH Network

Abstract

This disclosure provides a method and system for controlling a target object using a MESH network. The method for controlling the target object includes the steps of: configuring the target object in the MESH network using a configurator; and transmitting control commands from a digital key corresponding to the target object to the target object via the MESH network. Remote control of the target object using a digital key can be achieved.

Description

Technical Field

[0001] This application claims priority to a Chinese invention patent titled "Method for Controlling a Target Object and Object Control System Using a MESH Network" filed on April 12, 2023, with application number 202310389561.4, the full text of which is incorporated herein by reference.

[0002] This application relates to the field of the Internet of Things (IoT), and particularly to a method for controlling a target object using a MESH network, an object control system, a MESH network, and a computing device.

Background Art

[0003] With the rapid development of network technology, digital keys are gradually becoming popular. For example, digital keys are widely used in various scenarios such as automobiles, enterprise access control, home door locks, safes, bicycles, etc.

[0004] As an example of application, a digital key is a new product due to the improvement of automotive technology. An automobile owner can use devices such as a mobile terminal, an electronic bracelet, an electronic watch, etc. as the key of the automobile to perform operations such as unlocking the vehicle, starting the engine to drive the automobile, and controlling the temperature inside the vehicle without a physical key.

[0005] Digital keys adopt remote control (for example, Remote Keyless Entry (RKE)) technology to transmit data with a target object (for example, a vehicle) using a low-frequency signal. Such electromagnetic wave signals have a long wavelength and a good diffraction effect of the signal, so the communication between the digital key and the target object is not easily blocked by other obstacles.

[0006] With the development of communication technologies related to the carriers of digital keys (e.g., mobile devices), data communication protocols currently used in digital keys include near-field communication (NFC), Bluetooth Low Energy (BLE), and ultra-wideband (UWB), all of which transmit data using high-frequency signals, in order to improve compatibility with various communication protocols. However, when using high-frequency signals to transmit data and control a target object as a digital key, it is first necessary to establish a communication link with the target object. However, high-frequency signals are easily interfered with by obstacles, so in places with many obstacles, the transmission of high-frequency signals is easily interfered with, and the effective range of the digital key is greatly reduced.

[0007] Therefore, even in areas with many obstacles, a solution is needed that allows digital keys to communicate data with the target using high-frequency signals. [Overview of the project]

[0008] According to a first aspect of the present application, a method for controlling a target object using a MESH network is provided, comprising the steps of: configuring the target object in the MESH network using a configurator; and transmitting a control command from a digital key corresponding to the target object to the target object via the MESH network.

[0009] A second aspect of the present invention provides a method for controlling a target object using a MESH network, wherein the MESH network includes a plurality of objects including a target object, and the method includes the steps of: at least one object in the MESH network receiving a control command for the target object from a digital key corresponding to the target object; and if the at least one object determines that it is not an object that can be targeted by the control command, forwarding the control command to the target object via a link between nodes in the MESH network.

[0010] A third aspect of the present invention further provides a target control system including a configurator for locating target objects in a MESH network, and a MESH network for transmitting control commands for digital keys corresponding to the target objects to the target objects.

[0011] According to a fourth aspect of the present application, a MESH network comprising a plurality of objects is further provided, each object comprising a processor and a memory storing computer-readable instructions, wherein when the instructions in the memory of the plurality of objects are executed, the processors of the plurality of objects jointly execute the target object control method described in the second aspect.

[0012] Therefore, according to the target control method using a MESH network of the present invention, multiple objects, including the target object, can be arranged in the same MESH network. Even if the digital key cannot communicate with the target object via a high-frequency communication link (e.g., BLE link, NFC link, UWB link) due to interference from obstacles, if the control command transmitted by the digital key can be transmitted to one object in the MESH network, it can be forwarded to the target object based on the links between nodes in the MESH network, thereby enabling control of the target object. Consequently, long-distance control of a target object using a digital key can be realized. [Brief explanation of the drawing]

[0013] Below, in order to more clearly explain the embodiments of this application or the prior art, the drawings used in the explanation of the embodiments of this application or the prior art are briefly introduced. Naturally, the drawings described below are only a part of the embodiments described in this application. Those skilled in the art can obtain other drawings based on these drawings of the embodiments of this application.

[0014] [Figure 1]Figure 1 is a schematic diagram illustrating a scenario in which the digital key cannot establish a high-frequency communication link with the vehicle. [Figure 2] Figure 2 is a schematic diagram showing a system for controlling a vehicle using a digital key according to an embodiment of the present invention. [Figure 3] Figure 3 is a schematic flowchart illustrating a method for controlling a target object using a MESH network according to an embodiment of the present invention. [Figure 4] Figure 4 shows each substep of step S320 in the control method for the target object shown in Figure 3. [Figure 5] Figure 5 is a schematic flowchart illustrating a method for controlling a target object using a MESH network according to another embodiment of the present invention. [Figure 6] Figure 6 shows the interaction process between the digital key, the configurator, and each object (vehicle 1 and vehicle 2). [Figure 7] Figure 7 shows the interaction process between the digital key, the configurator, and each object (vehicle 1 and vehicle 2). [Figure 8] Figure 8 is a schematic diagram illustrating an exemplary pre-configured network configuration. [Figure 9] Figure 9 is a schematic flowchart illustrating a method for controlling a target object using a MESH network according to another embodiment of the present invention. [Figure 10] Figure 10 is a schematic diagram illustrating the transfer of control commands via links between nodes in a MESH network. [Figure 11] Figure 11 is a schematic diagram illustrating the transfer of control commands via links between nodes in a MESH network. [Figure 12] Figure 12 is a schematic diagram showing a model configured at the nodes for mutually controlling the sounding of alarms between nodes. [Figure 13] Figure 13 is a schematic block diagram showing the target control system according to an embodiment of the present application. [Figure 14]FIG. 14 is a schematic block diagram showing a computing device according to an embodiment of the present application.

DETAILED DESCRIPTION OF THE INVENTION

[0015] Hereinafter, in combination with the drawings in the embodiments of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described. Naturally, the described embodiments are only a part of the embodiments of the present application, not all of the embodiments. Based on the embodiments of the present application, all other embodiments obtained without creative labor by those skilled in the art should be included in the protection scope of the present application.

[0016] As described above, in a place with many obstacles, the transmission of high-frequency signals is likely to be interfered, and there is a possibility that the digital key cannot control the target object corresponding thereto. FIG. 1 is a schematic diagram showing a scenario where a digital key cannot establish a high-frequency communication link with a vehicle.

[0017] FIG. 1 is a schematic diagram of a parking lot, where the target vehicle (the vehicle shown in shadow) is located far away from the user (there is a corresponding digital key on the user's mobile terminal). Since there are many obstacles in the parking lot, the user's mobile terminal cannot establish a high-frequency communication link (for example, a Bluetooth Low Energy (BLE) link) with the target vehicle, and the digital key of the mobile terminal cannot be used to control the target vehicle (for example, unlock, turn on / off the air conditioner), or find the position of the target vehicle.

[0018] To solve the above problems, the present application proposes a solution to control the target object using a wireless mesh network (MESH network). Thereby, even when the digital key and the target object cannot directly communicate via a high-frequency communication link, the communication between the digital key and the target object is realized by the MESH network.

[0019] A MESH network can include multiple network nodes (which may also be referred to as nodes), and each network node is a device equipped with a processing function and a communication function. There is a direct or indirect communication link between any two network nodes, that is, messages can be transmitted directly or indirectly (via a relay node) between any two network nodes. The communication between network nodes belongs to high-frequency communication. For example, based on BLE technology, the MESH network may be shown as a BLE MESH network. Or, the MESH network may be a WIFI MESH or Zigbee MESH network.

[0020] Also, a MESH network can include a single network or multiple networks (referred to as subnets). When including multiple subnets, from the perspective of the network layer concept, one network secret key (NetKey) corresponds to one subnet, and nodes with the same network secret key belong to the same subnet. Nodes that do not belong to the subnet cannot relay and transfer messages within the subnet.

[0021] Figure 2 shows a schematic diagram of a system for controlling a vehicle using a digital key according to an embodiment of the present application.

[0022] As shown in Figure 2, the system includes a first device 100, a second device 200, a vehicle 300 (a specific example as the target object controlled by the digital key), a first server 400 for the first device 100, a second server 500 for the second device 200, and a vehicle server for the vehicle 300. The first device 100 and the second device 200 may communicate directly in a point-to-point manner or communicate via a server.

[0023] For example, communication between the first device and the second device can be performed via link 2 between the first device and the first server, links 3 and 5 between the first server and the second server, and link 4 between the second server and the second device. For example, a digital key can be shared with the second device, and configuration information that can be set on the first device can be provided to the second device. The first device communicates with the first server 400 via link 2, and the second device communicates with the second server via link 4. Alternatively, the first and second devices may communicate directly with the vehicle server via links 6 and 7, or indirectly with the vehicle server via links 2 and 3, and links 4 and 5 of their respective servers. The first server 400 and the second server 500 are each responsible for managing the digital key lifecycle (data cycle), and update, delete, suspend, and restore the certificates (or certificate chains) of the first and second devices via links 2 and 4, respectively. Servers 400 and 500 can provide and renew necessary certificates, load and install digital key instances, and authorize the invalidation and deletion of digital keys. Vehicle server 600 can create pairing passwords, sign public keys, provide certificates to devices, manage keys, provide necessary authentication data to shareholders, and issue digital key structures for legitimate shareholders.

[0024] The first device, the second device, and the vehicle each include a high-frequency communication module, such as an NFC module, a BLE module, or a UWB module, and the first device and the second device can control the vehicle via high-frequency communication.

[0025] The first device 100 and the second device 200 are various mobile electronic devices capable of data processing and transmission, such as mobile phones, tablet computers, smartwatches, smart bracelets, and smart glasses, and can interact with a server via an application program once an application program is installed on them.

[0026] Servers 400, 500, or 600 include, but are not limited to, network hosts, a single network server, multiple network server sets, or cloud computing-based computer sets. Here, "cloud" consists of a large number of cloud computing-based hosts or network servers. Cloud computing, in particular, is a form of distributed computing, a virtual computer composed of a group of loosely coupled computer sets.

[0027] The first or second device transmits a generated digital key to the vehicle (smart vehicle) when it needs to be controlled. The vehicle receives the digital key from the device, verifies the information contained in the digital key, and if the verification is successful, performs actions such as unlocking the vehicle or turning on the air conditioning according to the control command.

[0028] As described above, if the first or second device cannot establish a high-frequency communication link with the vehicle, it may be necessary to improve the structure of the system.

[0029] Referring to Figures 3 to 13, a solution for controlling a target object using a wireless mesh network (MESH network) according to an embodiment of the present invention will be described in detail.

[0030] In the context of this application, for the sake of simplicity, the term "digital key" may also refer to a device equipped with a digital key. For example, "the digital key transmits information" means that information is transmitted via a device equipped with a digital key, and "the digital key is deployed in the MESH network" means that a device equipped with a digital key is deployed in the MESH network.

[0031] Figure 3 shows a schematic flowchart of a method for controlling a target object using a MESH network according to an embodiment of the present invention. At least part of the method shown in Figure 3 may be performed by a configurator. The configurator can configure the target object in the MESH network by performing high-frequency communication with the target object under predetermined conditions (e.g., a sufficiently close distance). For example, the configurator may be the entrance gate of a parking lot (where the MESH network configuration function is installed). In the short time it takes for a vehicle to enter the parking lot, the configurator completes the network configuration operation for the vehicle, and the vehicle drives from the parking lot entrance into the parking lot.

[0032] As shown in Figure 3, in step S310, the configurator places the target object into the MESH network.

[0033] For example, the configurator may receive network access-related information transmitted from the target object. For example, the configurator may receive a broadcast frame transmitted from the target object, and the broadcast frame may carry the network access-related information of the target object. The configurator may then deploy the target object to the MESH network based on the network access-related information of the target object.

[0034] If, as an option, the target that sent the broadcast frame does not have a MESH network (even if the MESH network is successfully deployed, the target may continue to send broadcast frames that are received by the configurator), the configurator decides that it expects the target to be deployed to a MESH network (i.e., to deploy a MESH network), and then performs the action of deploying a MESH network to the target.

[0035] Optionally, the network access-related information of the target may include various types of information about the target, such as identification information (such as an identifier), brand, model, and year of manufacture.

[0036] For example, if the target is a vehicle, a BLE MESH configurator (e.g., one integrated with the gate) is installed at the entrance to the parking lot. The BLE MESH configurator receives beacons broadcast from the vehicle, and the beacons contain network access-related information for the target.

[0037] For example, the BLE MESH configurator can activate the MESH network deployment function to discover beacons broadcast by vehicles when it detects the license plates of vehicles currently entering the parking lot.

[0038] Optionally, network access-related information within a beacon may include the beacon type (e.g., non-temporary device beacon type (0x00)), device identifier UUID (to uniquely identify the device), out-of-band (OOB) information (to indicate the availability of out-of-band (OOB) data), and uniform resource identifier (URI) information (to indicate vehicle-related information). For example, a partial example of a beacon structure transmitted from a vehicle is shown below.

[0039] Device UUID:70cf7c9732a345b691494810d2e9cbf4 OOB: Number, Inside Manual OOB Information: 4020 URI:https: / / www.ABC.com / mesh / products / def

[0040] In this example, at least the URI information and the device identifier UUID may be recognized as network access-related information for the vehicle. For example, based on the URI information, it can be determined that the vehicle manufacturer is ABC and the model is def.

[0041] Optionally, after deciding to deploy a target object to the MESH network, the configurator may receive and authenticate identity authentication information transmitted by the target object before deployment to the MESH network. Optionally, this authentication may be performed using either an output-type OOB method or an input-type OOB method. For example, in the output-type OOB method, the target vehicle displays a multi-digit random number, or the vehicle transmits a multi-digit random number to the configurator via sound or light, and the configurator generates OOB authentication information using the acquired random number. In the input-type OOB method, the configurator generates a multi-digit random number, and the user inputs this multi-digit random number through the vehicle's input device.

[0042] Optionally, the configurator and target further perform public key interactions, first calculating a symmetric secret key encrypted using an asymmetric secret key scheme, and then using the calculated symmetric secret key to encrypt and decrypt messages that subsequently need to be interacted with.

[0043] For example, since a MESH network contains multiple objects (each object corresponds to one network node, so "node" and "object" in the MESH network of this disclosure are interchangeable), multiple objects, including the target object, can be placed in the MESH network according to a pre-configured network configuration. Such pre-configured network configurations may include, for example, including objects from the same manufacturer in the same MESH network, including objects of the same brand in the same MESH network, including objects of the same model in the same MESH network, having the same number of objects in each MESH network, having an incrementing number of objects in each MESH network, and having each position in the object distribution diagram pre-grouped, with objects at each group's position belonging to the same MESH network. For example, if the manufacturer is determined to be ABC based on the URI information of the target object, it may be placed in a MESH network where all included objects are manufactured by the ABC manufacturer, or it may be placed as the first object in a new MESH network corresponding to the ABC manufacturer. The above pre-configured network configurations may be selected and combined. For example, suppose there are 20 vehicles manufactured by ABC Manufacturer, and the same number are distributed equally between two MESH networks, meaning each MESH network has 10 vehicles manufactured by ABC Manufacturer. In another example, a configurator (e.g., a gate) assigns a specific parking space to each vehicle. The configurator may combine distribution maps of parking spaces to construct the MESH network according to the distribution maps of parking spaces.

[0044] Furthermore, after the MESH network has been successfully deployed, the configurator may notify the digital key corresponding to each of the multiple objects of the address information of the MESH network to which the corresponding object is deployed. For example, via a high-frequency communication link (for example, if the distance between the vehicle and the configurator is short and the BLE connection can be maintained within a short time after the network deployment is successful), or if the application program of the digital key maintains a communication connection with the configurator's server, the configurator can notify the digital key of the address information via that server. Alternatively, each object may notify the corresponding digital key of the address information of the MESH network to which it is deployed after the MESH network has been successfully deployed. For example, at this point, each object generally still maintains a high-frequency communication link with the corresponding digital key (for example, if the car owner is still inside the vehicle within a short time after the network deployment is successful and the digital key and vehicle can still maintain a BLE connection).

[0045] Alternatively, regarding the network deployment process for each object in the MESH network, the configurator may, for each object, determine the MESH network corresponding to that object according to a pre-configured network deployment configuration based on the object's network access-related information (as described above), communicate with the object, and transmit network deployment data for the MESH network corresponding to that object to the object, thereby deploying the object to the MESH network. Optionally, during the network deployment process, communication between the configurator and the vehicle is conducted via a high-frequency communication link such as BLE. This is because the distance between the two is short during network deployment.

[0046] For example, a configurator may send a connection request and a network placement request (including network placement data) to the target, and upon receiving the network placement data, the target may join the MESH network based on that data. Optionally, the network placement data may include a network secret key (referring to a MESH subnet in the MESH network where the target is located at the network layer) or a unicast address (i.e., a unique address assigned to the target).

[0047] Thus, objects within the same MESH subnet can communicate directly or indirectly, but objects within a MESH subnet cannot communicate with objects in other MESH subnets. In this application, a MESH network includes multiple MESH subnets (each subnet corresponding to one multicast address), and since the control of target objects included in one MESH subnet is mainly described, the terms MESH network and MESH subnet may be interpreted interchangeably in this application.

[0048] When this step is performed, the target object (e.g., a vehicle) is usually located very close to the configurator and the digital key. For example, the configurator is set up at the entrance of a parking lot, and the MESH network deployment function is activated in response to the license plate recognition system (which can be configured in conjunction with the configurator) detecting a license plate. At this point, the vehicle is already near the configurator and can communicate with the configurator via high-frequency communication via a BLE link, etc., and its broadcast frame is received by the configurator. Also, at this point, the user is inside the vehicle, so the digital key on the user's mobile device can also establish a high-frequency communication link with the vehicle's communication module and the configurator and communicate. Based on this, the configurator can send network deployment data to the vehicle, and after successful network deployment, the vehicle or configurator can notify the digital key of the MESH network address information deployed in the vehicle. The digital key and the configurator can also establish a communication connection via a server. When the user leaves the vehicle, the high-frequency link between the vehicle and the digital key is disconnected. However, even if the digital key and the configurator cannot communicate directly via high-frequency, they can still communicate through a server, allowing the configurator to receive control commands for the target object from the digital key. For example, the digital key and the configurator may correspond to the same server, and the application program or client of the digital key and the application program or client of the configurator may interact with the same server. Alternatively, the digital key and the configurator may correspond to separate servers with which they have a communication link.

[0049] In step S320, a control command from the digital key corresponding to the target is transmitted to the target via the MESH network.

[0050] If the digital key needs to transmit a control command to a target, it may be determined in advance whether it can communicate directly with the target via a high-frequency communication link. For example, this typically refers to situations where the user knows the vehicle's location and does not need to search for it, or where the distance is short or obstacles do not affect communication. Only if it is determined that direct communication with the target is impossible, the control command is transmitted to the target via the MESH network. Of course, the control command may also be transmitted directly to the target via the MESH network without prior determination of whether direct communication with the target via a high-frequency communication link is possible.

[0051] In some embodiments, the digital key is not a network node in the MESH network. That is, the digital key is located outside the MESH network, and it sends control commands to the MESH network (for example, to the nearest node (target) within the MESH network), and then transmits these control commands to the target via links between nodes in the MESH network. The links between nodes in the MESH network are high-frequency communication links, such as BLE links.

[0052] As selectable, Figure 4 shows each substep of step S320.

[0053] In substep S320-1, the configurator receives a control command for the target and identification information for the target from the digital key corresponding to the target. Then, in substep S320-2, based on the identification information for the target, the configurator determines the address of the MESH network in which the target is located.

[0054] After the MESH network is deployed, the configurator can store the correspondence between the target object and the deployed MESH network, for example, the correspondence between the target object's identifier and the address of the deployed MESH network. Then, after receiving identification information (e.g., identifier, UID, or unicast address) indicating the target object from the digital key, it can determine that it is necessary to send the control command to the address of the MESH network where the target object is deployed. Optionally, the identification information of the target object may be included in the control command for the target object.

[0055] Then, in substep S320-3, the configurator sends the control command to the address of the MESH network where the target object is located, and transmits it to the target object via the MESH network.

[0056] For example, when a configurator sends a control command to a MESH network, it may send it directly to a target object in that MESH network. In other cases, when a configurator sends a control command to a MESH network, it cannot send it directly to a target object in the MESH network, but it can send it directly to a second object in the MESH network, so the control command can be forwarded or relayed to the target object via the second object. This application does not describe a situation in which the configurator cannot send a control command to any object in the MESH network due to link constraints. In other words, the configurator sends a control command to an address in the MESH network, and at least one object in the MESH network (for example, an object close to the configurator) receives the control command.

[0057] In other optional embodiments, a digital key may be added to the MESH network to transmit control commands to the target via at least one node (target) between the digital key and the target in the MESH network.

[0058] In such cases, as shown in Figure 5, method 300 may further include the following steps.

[0059] In step S330, the configurator receives network access-related information from the digital key corresponding to the target. The network access-related information of the digital key includes at least one of the MESH network address information, the target identification information, and the digital key identification information.

[0060] For example, before a target is deployed to the MESH network by the configurator, the target and its corresponding digital key may have established a high-frequency communication link (for example, if the user is inside a vehicle, the user's mobile device and the vehicle may have established a BLE link). After the target is deployed to the MESH network, the target can notify the digital key of the MESH network address information based on the high-frequency communication link. In response to this notification, the digital key may determine that the corresponding target has been successfully deployed to the MESH network and then send a network access request to the configurator (for example, via a broadcast frame). Since this network access request may include network access-related information for the digital key, the configurator can deploy the digital key to the same MESH network as the target based on this network access-related information.

[0061] In step S340, based on the network access-related information of the digital key, the digital key is deployed to the same MESH network as the target.

[0062] For example, the configurator can store the correspondence between the target object and the MESH network to which it is deployed. Therefore, after receiving network access-related information from the digital key, it can determine the MESH network to which the target object is deployed (i.e., the address of the MESH network to which the target object is deployed) based on this network access-related information, and deploy the digital key to the MESH network corresponding to that address. Alternatively, since the digital key knows the MESH network to which the target object is deployed, it can directly transmit the address information of the MESH network to the configurator. Alternatively, the configurator can store the correspondence between the identification information of the digital key and the identification of the target object. This allows the configurator to indirectly determine the MESH network to which the digital key needs to be deployed based on the identification information of the digital key. Optionally, the configurator may transmit network deployment data to the digital key so that the digital key can be deployed to the corresponding MESH network.

[0063] Therefore, in step S320, if the digital key needs to send a control command to the target object via the MESH network, and the target object (node) is one of the objects in the MESH network, the digital key sends the control command to the target object via at least one object in the MESH network.

[0064] For example, if the digital key cannot directly transmit a control command to a target object in the MESH network, the control command may be transmitted to at least one communicable object in the MESH network. Thereafter, until the control command is received and forwarded by the target object, the at least one object continues to forward the control command to at least one second communicable object in the MESH network. Generally, the control command may be transmitted with or separately from the target object's identification information (i.e., identification information such as, for example, an identifier or the aforementioned unicast address). If an object determines, based on the received target object's identification information, that it is not the target of the control command, it forwards the control command (and / or target object's identification information) to a communicable object.

[0065] Therefore, according to the target control method using a MESH network described with reference to Figures 3 to 5, by arranging multiple targets, including the target, in the same MESH network, even if the digital key cannot communicate directly with the target via a high-frequency communication link (e.g., BLE link, NFC link, UWB link), if the control command transmitted by the digital key can be sent to one target in the MESH network, it can be forwarded to the target based on the links between nodes in the MESH network, thereby enabling control of the target. Consequently, remote control of the target can be realized.

[0066] To more clearly explain the process of controlling a target object using a MESH network, an example of the interaction process between a digital key, a configurator, and each object is described in conjunction with Figures 6 and 7. Here, a vehicle is used as the object, and a BLE MESH configurator (for deploying the BLE MESH network) is installed at the entrance gate of a parking lot. Figure 6 applies when the digital key is not a node in the MESH network, and Figure 7 applies when the digital key is not a node in the MESH network.

[0067] As shown in Figure 6, in process 1, for example, when the vehicle identification system detects vehicle 1, the BLE MESH configurator is triggered and the MESH network deployment operation is activated.

[0068] In process 2, the BLE MESH configurator receives a beacon transmitted from vehicle 1. This beacon contains network access-related information for the corresponding vehicle. The specific information of the beacon transmitted by the vehicle has already been described above.

[0069] In process 3, the BLE MESH configurator determines, based on the received beacon, that vehicle 1 does not have a MESH network installed and needs to connect to vehicle 1 to install the network. Alternatively, if multiple vehicles transmit beacons simultaneously, the BLE MESH configurator can determine, based on each received beacon, which vehicle needs to connect to install the network. For example, in process 4, the BLE MESH configurator sends a connection request to vehicle 1 (which may include the vehicle 1 identifier UUID1), and in process 5, it sends a network installation request (including network installation data) to vehicle 1. For example, the network installation data sent from BLE MESH to vehicle 1 may include the network secret key and unicast address.

[0070] In process 6, after the BLE MESH configurator transmits network configuration data to vehicle 1, the BLE MESH configurator may transmit the MESH network information of vehicle 1 to the digital key.

[0071] In process 7, vehicle 1 performs a network placement operation based on the received network placement data and is placed in the MESH network, which may be, for example, the MESH network where vehicles of the same brand as vehicle 1 are located.

[0072] Processes 8 through 12 concern the network configuration of vehicle 2 and are essentially the same as processes 2 through 6.

[0073] In process 13, both vehicle 2 and vehicle 1 are deployed on the same MESH network (for example, vehicle 2 and vehicle 1 are of the same brand).

[0074] In process 14, the digital key 1 corresponding to vehicle 1 communicates with the BLE MESH configurator, and the digital key 1 sends control commands and identification information of vehicle 1 (the identification information of vehicle 1 may be the vehicle 1's UUID1) to the BLE MESH configurator.

[0075] In process 15, the BLE MESH configurator obtains the address of the BLE MESH network where vehicle 1 is located, based on the identification information of vehicle 1, and sends a control command to the BLE MESH network address. It is assumed that vehicle 1 can be controlled by sending the control command directly to vehicle 1.

[0076] Similarly, in process 16, the digital key 2 corresponding to vehicle 2 communicates with the BLE MESH configurator, and the digital key 2 sends control commands and identification information of vehicle 2 to the BLE MESH configurator.

[0077] In process 17, the BLE MESH configurator obtains the address of the BLE MESH network where vehicle 2 is located, based on the identification information of vehicle 2, and sends a control command to the BLE MESH network address. If the control command cannot be sent directly to vehicle 2 but can be sent directly to vehicle 1, then in process 18, it is forwarded to vehicle 2 via vehicle 1, and vehicle 2 can be controlled.

[0078] Through the interaction process between the digital key, the configurator, and each object shown in Figure 6, if Vehicle 1 and Vehicle 2 cannot directly receive control commands from the digital key, the control commands can be transmitted to Vehicle 1 and Vehicle 2 via the MESH network.

[0079] Furthermore, if the digital key functions as a single node in the MESH network, it may include multiple processes as shown in Figure 7.

[0080] As shown in Figure 7, in process 1, the digital key first establishes a high-frequency communication link (e.g., BLE connection) with the corresponding vehicle. That is, vehicle 1 establishes a high-frequency communication link with digital key 1, and vehicle 2 establishes a high-frequency communication link with digital key 2.

[0081] Processes 2 through 11 are the process of deploying networks for vehicles 1 and 2, and are the same as the corresponding processes explained with reference to Figure 6, so they will not be repeated here. Also, in Figure 7, for the sake of ease of diagramming, the interaction processes between vehicles 1 and 2 and the BLE MESH configurator are shown in parallel. Since vehicles 1 and 2 enter the parking lot at regular time intervals, after the MESH network for vehicle 1 is successfully deployed, vehicle 2 enters the parking lot, and the BLE MESH configurator begins deploying the MESH network for vehicle 2.

[0082] In process 12, vehicle 1 may transmit the MESH network address information of vehicle 1 to digital key 1 via a high-frequency communication link, and in process 13, vehicle 2 may transmit the MESH network address information of vehicle 2 to digital key 2 via a high-frequency communication link. Alternatively, the configurator may transmit the MESH network address information of vehicle 1 and vehicle 2 to the corresponding digital keys. Vehicles 2 and 1 are both located on the same MESH network (for example, vehicle 2 and vehicle 1 are of the same brand).

[0083] In process 14, the digital key 1 corresponding to vehicle 1 communicates with the BLE MESH configurator, or the digital key 1 sends a broadcast frame (e.g., a beacon) to the BLE MESH configurator, transmitting the identification information of the digital key 1 and the identification information of vehicle 1 to the BLE MESH configurator.

[0084] In process 15, the BLE MESH configurator places the digital key on the same MESH network as vehicle 1 based on the received identification information. For example, although not shown in the diagram, the BLE MESH configurator may send connection requests and network placement requests to the digital key, and the digital key may receive network placement data.

[0085] Thus, in process 16, digital key 1, vehicle 1, and vehicle 2 are placed on the same MESH network.

[0086] In process 17, since digital key 1 cannot directly send control commands to vehicle 1, it sends control commands to vehicle 2 on the same MESH network via links between nodes in the MESH network. Then, in process 18, vehicle 2 forwards the control commands to vehicle 1, and control of vehicle 2 by digital key 1 is realized.

[0087] As shown in Figure 7, through the interaction process between the digital key, the configurator, and each object, the digital key is also added to the MESH network where the corresponding vehicle is located. Therefore, even if the digital key cannot directly send control commands to the corresponding vehicle, the control commands can be transferred to the corresponding vehicle via other vehicles in the MESH network.

[0088] For example, as shown in Figure 8, the configurator (e.g., Gate) provides each vehicle with a specific parking space. The configurator can combine parking space distribution maps to construct two MESH subnets (MESH subnet 1 and MESH subnet 2) according to the parking space distribution maps. Each of the two MESH subnets corresponds to a group of vehicles parked in a parking space (shown as dashed and solid lines in the figure). Since vehicle A (shown in shadow) is located in MESH subnet 2 and cannot directly send control commands to the digital key (let's say one node in MESH subnet 2), control commands sent by the digital key can reach vehicle A via vehicles B, C, D, E, and F in MESH subnet 2.

[0089] In other aspects of the present application, a method for controlling target objects using a MESH network is also disclosed. The MESH network includes a plurality of objects arranged by the configurator as described above, and the plurality of objects include the target object.

[0090] Figure 9 is a schematic flowchart illustrating a method for controlling a target object using a MESH network according to an embodiment of the present invention.

[0091] As shown in Figure 9, in step S910, at least one object in the MESH network receives a control command for the target object from the digital key corresponding to the target object.

[0092] For example, if a digital key is not a node (target) in the MESH network, and the configurator sends a control command received from the digital key to a MESH network address, as mentioned above, if there is no high-frequency communication link between the configurator and the target, the control command cannot be sent directly to the target and can only be sent to another target in the MESH network. Alternatively, if a digital key is a node in the MESH network, and there is no direct node-to-node link between the digital key and the target, the digital key cannot send a control command directly to the target and can only send it to another target in the MESH network that has a direct node-to-node link (for example, the target corresponding to an adjacent node).

[0093] In step S920, if at least one object determines that it is not the target of the control command, it forwards the control command to the target object via the links between nodes in the MESH network.

[0094] For example, a control command may generally be transmitted with target identification information (i.e., identification information such as an identifier or the unicast address of the target mentioned above), or it may be transmitted separately from the identification information. If at least one target determines, based on the received target identification information, that it is not the target of the control command, the control command (and / or target identification information) is forwarded to a communicable target until the control command is successfully transmitted to the target.

[0095] In other words, the links between the nodes described above include a transfer path from the object receiving the control command to the target object, and this transfer path includes a second object adjacent to the target object in the MESH network.

[0096] In this case, the method 900 may further include the step of the target object transmitting an instruction relating to the control instruction to the second object after the target object has received the control instruction.

[0097] For example, the control command may be a vehicle search command, or after the target receives the control command, the target sends a remind command to a second target, which then performs a remind operation to indicate the approximate location of the target. For example, both targets may be vehicles, and the remind command may be a horn sound command or a light flash command. After hearing the horn sound command or seeing the lights flash, the user can determine the approximate location of the target vehicle based on the location of the second target which sounds the horn or flashes its lights, and then locate the target vehicle based on the location of the second target. The target vehicle may also sound its horn or flash its lights based on the control command.

[0098] For example, the control command is a vehicle lock command, and the command related to the control command is a horn sound command or a light flash command. After the target receives the vehicle lock command, it sends a horn sound command or a light flash command (for example, a command that controls the second target to sound its horn or flash its lights) to the second target, and the second target performs the horn sound or light flash action to indicate the approximate location of the target. For example, both targets are vehicles, and the user can determine the approximate location of the target vehicle based on the location of the second target that sounded its horn or flashed its lights after hearing the horn sound or seeing the lights, and then find the location of the target vehicle according to the location of the second target. The target vehicle can sound its horn or flash its lights based on the control command.

[0099] Alternatively, the links between the nodes described above include a first and a second transfer path from the object receiving the control command to the target object, the first transfer path including a second object adjacent to the target object in the MESH network, and the second transfer path including a fourth object adjacent to the target object in the MESH network and a third object adjacent to the fourth object.

[0100] In such a case, the method 900 may further include the step of the target object receiving the control command via the first and second transfer paths, respectively, and then transmitting commands relating to the control command to the second and fourth objects, respectively.

[0101] Selectively, the control command includes either a vehicle search command or a vehicle lock command, and after the target receives the vehicle search command or vehicle lock command, the target sends reminder commands to the second and fourth targets so that the second and fourth targets perform a reminder action to indicate the approximate location of the second target.

[0102] Furthermore, the fourth object can send a reminder command to the third object so that both the third and fourth objects perform a reminder action to form a reminder chain (for example, both sound a horn or both flash lights). This indicates the approximate location of the target object, which is very useful when the target object is far away from the digital key.

[0103] For example, all target objects may be vehicles, and the reminder command may be a horn sound command or a light flash command. This allows the user to determine the approximate location of the target vehicle based on the positions of the two objects that sounded the horn or flashed the lights, after hearing the horn sound or seeing the lights from the closer third object and the farther fourth object, and then locate the target vehicle according to the closer third object and the farther fourth object. The target vehicle may sound its horn or flash its lights in response to the control command.

[0104] In other words, since each node (target) can have multiple neighboring nodes (targets), the target node can receive control instructions transferred through multiple paths. After receiving the control instructions transferred through these paths, the target node can send back instructions related to the control instructions to its neighboring nodes along these paths (for example, the nodes corresponding to the second and fourth targets mentioned above). These neighboring nodes can then transfer the instructions related to the control instructions to their own neighboring nodes, and this analogy continues below. The target node can choose to send back instructions related to the control instructions to all neighboring nodes, or only to neighboring nodes along the transfer path that received the control instructions within a predetermined time period after initially receiving the control instructions.

[0105] Figures 10 to 11 are schematic diagrams illustrating the transfer of control commands via links between nodes in a MESH network. In both diagrams, the control command is a vehicle search command and the reminder command is either a horn sound command or a light flashing command. Furthermore, while Figures 10 to 11 show an example where node A is the digital key corresponding to the target vehicle and node B is the target object (when the digital key is located within the MESH network), it should be understood that node A may also be the node that receives the control command for the target object from the configurator (when the digital key is not located within the MESH network).

[0106] As shown in Figure 10, within a predetermined time period, node B continuously receives vehicle search commands transmitted multiple times by node A, and node B can send reminder commands, such as horn sounding commands and light flashing commands, to its neighboring nodes (e.g., nodes C and D) in the transfer path from node A to node B. The neighboring nodes of node B can be obtained through a record table of control commands received by node B.

[0107] As shown in Figure 11, after node C receives a reminder command (e.g., a command to sound the horn or a command to flash the lights) from node B, it can continue to send reminder commands to its neighboring node (e.g., node E).

[0108] If node B can optionally send a horn-sounding command to node C or node D, a model must be built at each node, as shown in Figure 12. Figure 12 is a schematic diagram showing the model set up at the nodes to control the horn-sounding operation between the nodes.

[0109] Node B contains a client model and a server model, and accordingly, Node C also contains a similar client model and server model. When Node B needs to control Node C through a horn command, Node B uses its client model to control the value of the state attribute of the server model in Node C, thereby enabling or disabling the horn operation in Node C. Alternatively, in other applications, Node B may be controlled by Node C to perform a horn operation. In such cases, Node C uses its client model to control the value of the state attribute of the server model in Node B, thereby enabling or disabling the horn operation in Node B.

[0110] Therefore, in this manner, even if the digital key cannot directly transmit control commands to the target, the control commands can be transferred to the target via at least one object in the MESH network to control the target. Furthermore, the target can send commands related to the control commands, such as reminder commands, back to its neighboring nodes, allowing the user to find the target according to the reminder. This is extremely useful when a car owner needs to find their vehicle and improves the user experience.

[0111] Other embodiments of the present invention further provide a target control system.

[0112] Figure 13 is a schematic block diagram showing a target control system according to an embodiment of the present invention. This system further includes more vehicles (forming a MESH network) and a first device compared to the system shown in Figure 2, and also includes a configurator.

[0113] The target control system 1300 may include a configurator 1310 and a MESH network 1320 to enable control from a digital key to a target, where the target is a single node located in the MESH network 1320 via the configurator 1310.

[0114] The configurator 1310 can deploy a target object to the MESH network, and for example, it can receive a broadcast frame transmitted by the target object. The broadcast frame contains network access-related information of the target object, and the configurator 1310 deploys the target object to the MESH network based on the network access-related information of the target object. For example, based on the manufacturer information of the target object, the configurator 1310 can deploy the target object to the MESH network where objects from the same manufacturer are located.

[0115] As per the options described above, the digital key corresponding to the target object is also deployed as a node in the MESH network where the target object is located.

[0116] The MESH network 1320 can transmit control commands from a digital key corresponding to the target object to the target object.

[0117] For example, at least one object in a MESH network receives a control command for that object from a digital key corresponding to the target object, and if that at least one object determines that it is not the target of the control command, it forwards the control command to the target object via the links between nodes in the MESH network.

[0118] Further details regarding the operations performed by configurator 1310 and MESH network 1320 can be found in the description above.

[0119] For example, before deploying the target object to the MESH network, the configurator 1310 receives the identity authentication information transmitted by the target object and authenticates the identity authentication information.

[0120] When the configurator 1310 places the target object in the MESH network, it can place the target object in the MESH network according to a pre-configured network placement configuration based on the network access-related information. However, the MESH network includes multiple objects, including the target object. For example, the configurator 1310 determines the MESH network corresponding to the target object according to a pre-configured network placement configuration based on the network access-related information of the target object, communicates with the target object, and places the target object in the MESH network by transmitting network placement data of the MESH network corresponding to the target object to the target object. After the network placement is completed, the configurator 1310 notifies the digital key corresponding to the target object of the address information of the MESH network to which the target object has been placed.

[0121] When transmitting a control command via a MESH network, if a digital key is not provided for the MESH network where the target object is located, the configurator 1310 receives the control command and target object identification information from the digital key, determines the address of the MESH network where the target object is located based on the target object identification information, and transmits the control command to the MESH network address where the target object is located, thereby transmitting it to the target object via the MESH network.

[0122] Optionally, the configurator may be a device having data processing and communication functions, and whose functions can be controlled by a corresponding server. The configurator may include various modules or further submodules for performing each of the operations described above. For example, the configurator may include one or more of a transmit module, a receive module, and a processing module. For example, the receive module can receive broadcast frames transmitted by the target. The processing module can also place the target in the MESH network based on the target's network access-related information. The transmit module can transmit the address information of the MESH network in which the target is placed to a digital key corresponding to the target.

[0123] Of course, each module can be partitioned to include more submodules depending on different functions and operations, or each module can be combined as a new module. In some embodiments, a module or its submodules can be implemented using electronic hardware (e.g., a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, individual gate or transistor logic, individual hardware components, etc.), computer software (e.g., stored in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), etc.), or a combination of the two.

[0124] If the target is a vehicle, the configurator may also be a parking lot entrance gate. The configurator 1310 may activate the MESH network deployment function in response to detecting the vehicle's license plate (either through a separate license plate identification system or one integrated with the configurator).

[0125] When transmitting a control command via a MESH network, if a digital key is located on the MESH network where the target object is located, the configurator 1310 receives network access-related information from the digital key corresponding to the target object. The network access-related information of the digital key includes at least one of the following: the address information of the MESH network, the identification information of the target object, or the identification information of the digital key. The configurator 1310 then places the digital key on the same MESH network as the target object based on the network access-related information of the digital key. For example, the configurator 1310 determines the MESH network where the target object is located based on the network access-related information of the digital key and places the digital key on the same MESH network as the target object. The digital key may broadcast a beacon containing network access-related information.

[0126] Thus, a digital key in a MESH network may transmit a control command to a target object via at least one object in the MESH network.

[0127] For further details on the operations performed in a MESH network, for example, refer to the explanations in Figures 9-12 above.

[0128] A MESH network consists of multiple objects, each object including a processor and memory storing computer-readable instructions, and when instructions in the memory of the multiple objects are executed, the processors of the multiple objects jointly perform the various operations described for the MESH network.

[0129] For example, each object may have data processing and communication functions, and these functions may be controlled by a corresponding server. It may also include various modules or further submodules for performing the various operations described above, such as a transmit module, a receive module, and a processing module. Of course, each module may be partitioned to include more submodules depending on different functions and operations, or each module may be combined as a new module. In some embodiments, a module or its submodule can be implemented using electronic hardware (e.g., a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, individual gate or transistor logic, individual hardware components, etc.), computer software (e.g., stored in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), etc.), or a combination of the two.

[0130] Figure 14 is a schematic block diagram showing a computing device according to an embodiment of the present invention. This computing device may be the target of a configurator or each node in a MESH network.

[0131] As shown in Figure 14, the computing device 1400 comprises one or more processors connected via a system bus, one or more memories, a network interface, an input device, and a display screen. However, the memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium of the terminal stores the operating system and may also store a computer executable program. When the computer executable program is executed by the processor, the processor can perform various operations of the digital key sharing method or the target control method using a digital key described above. The internal memory may also store a computer executable program. When the computer executable program is executed by the processor, the processor can perform various operations of the method described above.

[0132] The processor may be an integrated circuit chip having signal processing capabilities. The processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. Each method, step, and logic block diagram disclosed in the embodiments of this application can be implemented or performed. The general-purpose processor may be a microprocessor, or the processor may be any ordinary processor, and may be of an X84 architecture or an ARM architecture.

[0133] Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The memory in the methods described herein includes, but is not limited to, these and any other suitable types of memory.

[0134] The display screen of the computing device may be a liquid crystal display screen or an e-ink display screen. The input device of the computing device may be a touch layer covering the display screen, or buttons, a trackball, or a touchpad set in the housing of the device, or an external keyboard, touchpad, or mouse.

[0135] The computing device may be a terminal or a server. A terminal includes, but is not limited to, smartphones, tablet computers, laptops, desktop computers, and smart TVs. Various clients (applications, APPs), such as multimedia playback clients, social clients, browser clients, information flow clients, and educational clients, may run on the terminal. A server may be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDNs, big data, and artificial intelligence platforms.

[0136] In other embodiments of the present invention, a computer-readable storage medium in which a computer program is stored is further provided. When the computer program is executed by a processor, the processor performs each of the steps of the method described above.

[0137] According to other embodiments of the present invention, a computer program product including a computer program is further provided. Each step of the method described above is realized when the computer program is executed by a processor.

[0138] The flowcharts and block diagrams in the drawings illustrate feasible architectures, functions, and operations of methods and apparatus according to various embodiments of the present application. In this regard, each box in the flowchart or block diagram may represent a module, program segment, or part of code, and such module, program segment, or part of code may include at least one executable instruction for implementing a predetermined logic function. Furthermore, as some alternative means of implementation, the functions shown within a block may be executed in an order different from the order shown in the drawings. For example, two consecutively shown blocks may be executed substantially in parallel or in reverse order, depending on the function. Also, each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a dedicated hardware-based system that performs a predetermined function or operation, or by a combination of dedicated hardware and computer instructions.

[0139] The exemplary embodiments of the present application described in detail above are for illustrative purposes only and do not limit the present application. Those skilled in the art will understand that various modifications or combinations of these embodiments or their features can be made without departing from the principles and spirit of the present application, and that these modifications are also covered by the present application.

Claims

1. A method for controlling a target object using a MESH network, The steps include: deploying the target object to the MESH network using a configurator; The MESH network includes the step of transmitting a control command from a digital key corresponding to the target object to the target object, A method for controlling a target object.

2. The step of deploying the target object to the MESH network using the configurator is: The configurator receives a broadcast frame transmitted from the target, and the broadcast frame contains network access-related information of the target. The configurator includes the step of deploying the target to the MESH network based on the network access-related information of the target, A method for controlling a target object according to claim 1.

3. Before the step of deploying the target object to the MESH network using the configurator, The configurator further includes the step of receiving identity authentication information transmitted by the target and authenticating the identity authentication information, A method for controlling a target object according to claim 1.

4. The configurator, based on the network access-related information of the target, performs the step of deploying the target to the MESH network, The configurator, based on the network access-related information, arranges the target object in the MESH network according to a pre-configured network arrangement configuration, and the MESH network includes a plurality of objects including the target object. The configurator includes the step of notifying the digital key corresponding to the target of address information relating to the MESH network in which the target is located, A method for controlling a target object according to claim 2.

5. The configurator, based on the network access-related information, performs the step of arranging the target object in the MESH network according to a pre-configured network arrangement configuration, The configurator, based on the network access-related information of the target, determines the MESH network corresponding to the target according to a pre-configured network configuration. The configurator includes the step of communicating with the target object and transmitting network deployment data for the MESH network corresponding to the target object to the target object, thereby deploying the target object to the MESH network. A method for controlling a target object according to claim 4.

6. The aforementioned pre-configured network configuration is: This includes including products from the same manufacturer within the same MESH network. It includes the same MESH network and the same brand. The same MESH network includes the same model target, The number of targets included in each MESH network is the same, The number of targets included in each MESH network is incrementing, or, This involves pre-grouping each location in the distribution map of the target, and assigning the targets located in each group to the same MESH network. including at least one of the following: A method for controlling a target object according to claim 4.

7. The step of transmitting a control command from a digital key corresponding to the target object to the target object via the MESH network is: The configurator includes the steps of receiving the control command and the identification information of the target object from the digital key, The configurator takes the step of determining the address of the MESH network in which the target is located, based on the identification information of the target; The configurator includes the steps of transmitting the control command to the address of the MESH network where the target object is located, and transmitting it to the target object via the MESH network, A method for controlling a target object according to claim 1.

8. The configurator receives network access-related information from a digital key corresponding to the target object, and the network access-related information of the digital key includes at least one of the following: the address information of the MESH network, the identification information of the target object, and the identification information of the digital key. The configurator further includes the step of deploying the digital key to the same MESH network as the target object, based on the network access-related information of the digital key. A method for controlling a target object according to claim 1.

9. Before the target object is placed in the MESH network, the digital key establishes a high-frequency communication link with the target object. After the target object is deployed to the MESH network, the target object transmits the MESH network address information to the digital key based on the high-frequency communication link. A method for controlling a target object according to claim 8.

10. The configurator, based on the network access-related information of the digital key, takes the step of deploying the digital key to the same MESH network as the target object, The configurator includes the steps of determining the MESH network on which the target object is located based on the network access-related information of the digital key, and placing the digital key in the same MESH network as the target object. A method for controlling a target object according to claim 8.

11. The step of transmitting a control command from a digital key corresponding to the target object to the target object via the MESH network is: The step of transmitting the control command to the target object via at least one object in the MESH network using the digital key in the MESH network, A method for controlling a target object according to claim 8.

12. The target object is a vehicle, and the configurator is the entrance gate to the parking lot. The method for controlling the target object is: The further step includes the configurator activating the MESH network deployment function in response to the detection of a license plate of any vehicle, A method for controlling a target object according to claim 1.

13. A method for controlling a target object using a MESH network, The MESH network includes a plurality of targets, including the target target. The method for controlling the target object is: The steps include: receiving a control command for the target object from a digital key corresponding to the target object by at least one object in the MESH network; If the at least one object determines that it is not the target of the control command, the object forwards the control command to the target object via a link between nodes in the MESH network. A method for controlling a target object.

14. The steps include receiving identification information of the target object related to the control command from the digital key by at least one of the objects, The steps include determining, based on the identification information of the target object, that the object itself is not the target of the control command, and further including: A method for controlling a target object according to claim 13.

15. The MESH network includes the digital key or does not include the digital key. A method for controlling a target object according to claim 13.

16. The links between the nodes include at least one forwarding path, and the forwarding path includes a second target in the MESH network. The method for controlling the target object is: The step further includes the target object receiving the control command, and then transmitting a command relating to the control command to the second object. A method for controlling a target object according to claim 13.

17. The aforementioned control command is a vehicle search command or a vehicle lock command, After receiving the control command, the target object sends a reminder command to the second object so that the second object performs a reminder operation to indicate the approximate location of the target object. A method for controlling a target object according to claim 16.

18. The links between the nodes include a first forwarding path and a second forwarding path, the first forwarding path includes a second object in the MESH network, and the second forwarding path includes a third object and a fourth object in the MESH network. The method for controlling the target object is: The further step includes the target receiving the control command via the first and second transfer paths, respectively, and then transmitting commands relating to the control command to the second and fourth targets, respectively. A method for controlling a target object according to claim 13.

19. The control command includes a vehicle search command or a vehicle lock command, After the target receives a vehicle search command or vehicle lock command, it sends a reminder command to the second and fourth targets so that the second and fourth targets perform a reminder operation to indicate the approximate location of the target. A method for controlling a target object according to claim 18.

20. The method for controlling the target object is: The fourth object further includes the step of transmitting the reminder command to the third object so that the third and fourth objects perform reminder operations to form a reminder chain, thereby indicating the approximate location of the target object. A method for controlling a target object according to claim 19.

21. A configurator that deploys the target object to the MESH network, A MESH network that transmits control commands for a digital key corresponding to the target object to the target object, Target control system.

22. The aforementioned configurator, when deploying the target object to the MESH network, The system receives a broadcast frame transmitted by the target entity, and the broadcast frame contains network access-related information of the target entity. Based on the network access-related information of the target object, the target object is deployed to the MESH network. The target control system according to claim 21.

23. The configurator places the digital key in the same MESH subnet as the target object. The target control system according to claim 22.

24. At least one object in the MESH network receives a control command for the target object from a digital key corresponding to the target object. If at least one of the objects determines that it is not the target of the control command, it forwards the control command to the target object via the links between nodes in the MESH network. The target control system according to claim 22.

25. A MESH network composed of multiple objects, Each target is, Processor and Includes memory in which computer-readable instructions are stored, When the instruction in the memory of the plurality of targets is executed, the processors of the plurality of targets jointly execute the target control method according to any one of claims 13 to 20. MESH network.

Images