Pairing relationship management method and related apparatus

Abstract

A pairing relationship management method and a related apparatus, applied to the technical field of digital keys. In the present application, a vehicle can acquire a first pairing list currently stored by a Bluetooth chip and acquire a second pairing list from a first storage unit, wherein the second pairing list is a backup of a pairing list stored by the Bluetooth chip at a second moment, and the second moment is earlier than a generation moment of the first pairing list. The first pairing list and the second pairing list respectively comprise pairing parameters, and the vehicle can identify, on the basis of the first pairing list and the second pairing list, a pairing parameter that has been lost by the Bluetooth chip, and report the lost pairing parameter to a server, so as to trigger the server to send prompt information to a terminal corresponding to the lost pairing parameter, such that the terminal senses a digital key ID on a vehicle side. The present application can find a lost pairing relationship in advance and notify the terminal, thereby being conducive to guiding the terminal paired with the vehicle to find and solve the problem of a vehicle-side digital key ID, and improving the user experience.

Description

A method and related apparatus for managing pairing relationships

[0001] This application claims priority to Chinese Patent Application No. 202411233918.0, filed on September 2, 2024, entitled "A Pairing Relationship Management Method and Related Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of digital key technology, and in particular to a pairing relationship management method and related apparatus. Background Technology

[0003] A digital key is a security tool that uses digital information (such as digital codes or passwords) to authorize access to specific systems or services. Especially in the automotive industry, digital key technology allows users to unlock and control their vehicles using smartphones or wearable devices, significantly improving convenience and vehicle intelligence. When using a smartphone's digital key function, the device and the vehicle need to establish a connection and obtain pairing parameters beforehand. When the user approaches the vehicle with the device, the vehicle authenticates the device's identity based on the pairing parameters, granting the device control permissions.

[0004] Digital keys rely on digital information (such as digital codes or passwords), which is easily lost during storage. If lost, the digital key function on the terminal becomes unusable. For example, pairing parameters in a vehicle are stored in a Bluetooth chip. When the Bluetooth chip's storage space is full, or if the storage space is accidentally formatted, the pairing parameters on the vehicle side may be lost. The vehicle cannot authenticate the terminal's identity based on these pairing parameters, and when a user approaches the vehicle with the terminal, they cannot control the vehicle using the digital key. Furthermore, even if the pairing parameters on the vehicle side are lost, the pairing information still exists on the terminal. Users may repeatedly turn the digital key function on and off, move the terminal, or repeatedly turn the terminal's Bluetooth switch on and off, but none of these methods can resolve the issue of the digital key malfunctioning, resulting in a poor user experience. Summary of the Invention

[0005] This application provides a pairing relationship management method and related apparatus, which can proactively sense whether pairing parameters between a terminal and a vehicle are lost, thereby discovering lost pairing relationships in advance and alerting the terminal. This helps guide the terminal paired with the vehicle to discover and resolve the problem of lost vehicle digital key identification (ID), thus improving the user experience.

[0006] In a first aspect, this application provides a pairing relationship management method, comprising: obtaining a first pairing list currently stored in a Bluetooth chip, the first pairing list including N first pairing parameters, the first pairing list being generated at a first moment, each first pairing parameter including the Bluetooth media access control (MAC) address and the digital key ID of a terminal that completed digital key pairing with the vehicle before the first moment; obtaining a second pairing list from a first storage unit, the second pairing list including M second pairing parameters, the second pairing list being a backup of the pairing list stored in the Bluetooth chip at a second moment, the second moment being earlier than the first moment, each second pairing parameter including the Bluetooth MAC address and the digital key ID of a terminal that completed digital key pairing with the vehicle before the second moment; determining that at least one second pairing parameter in the second pairing list does not exist in the first pairing list, sending a target pairing parameter to a server, the target pairing parameter including at least one digital key ID from at least one second pairing parameter, to trigger the server to send a first prompt message to the target terminal corresponding to the digital key ID in the target pairing parameter, the first prompt message being used to indicate that the digital key ID corresponding to the target terminal in the vehicle is lost.

[0007] Where N is an integer and N≥0, and M is an integer and M>0.

[0008] This method can be applied to vehicles, for example, implemented by the vehicle or modules within it. These modules can include software modules, hardware modules, or a combination of both. For instance, the method can be executed by a chip or processor within the vehicle. For ease of description, the following explanation uses a vehicle as the executing entity.

[0009] The digital key pairing process between the vehicle and the terminal is primarily executed on the vehicle side via a Bluetooth chip. Once paired, the Bluetooth chip stores the terminal's MAC address and digital key ID. If the pairing list is updated due to reasons such as insufficient storage space or accidental formatting, the Bluetooth chip will consider the digital key ID not to have been paired with the terminal. When a user attempts to pair the terminal with the vehicle, pairing will undoubtedly fail, preventing the terminal from communicating with the vehicle.

[0010] In this application, a second pairing list is added to additionally and backuply record a pairing list between the vehicle and the terminal. This backup is earlier than the first pairing list and can back up the pairing parameters of terminals that have been paired with the vehicle. By comparing the first and second pairing lists, the vehicle can detect missing pairing parameters (i.e., target pairing parameters) in the Bluetooth chip and alert the terminal corresponding to the missing pairing parameters through the server. Accordingly, the server can look up the device information of the corresponding terminal based on the digital key ID and send a corresponding alert message to the corresponding terminal so that the terminal can perceive the digital key ID on the vehicle side.

[0011] For security reasons, pairing parameters stored in Bluetooth chips typically cannot be directly rewritten or recovered. When the digital key ID is lost, it can only be re-paired between the terminal and the vehicle to retrieve the corresponding pairing parameters. In the current pairing process, since the pairing information in the first terminal is not lost, it is difficult to trigger a solution on the terminal side. However, the solution provided in this application allows the vehicle to recognize the lost pairing parameters, facilitating subsequent guidance for the terminal to discover and resolve the vehicle-side digital key ID issue, thus improving the user experience.

[0012] Furthermore, in this application, each pairing parameter in the first pairing list and the second pairing list includes the terminal's Bluetooth MAC address and digital key ID. Since the terminal may have used other functions in the vehicle via Bluetooth connection, combining the Bluetooth MAC address and digital key ID as pairing parameters ensures that the pairing parameters are dedicated to the digital key process, accurately identifying the loss of pairing parameters corresponding to the digital key function, and specifically solving the problem of pairing failure caused by the loss of digital key ID.

[0013] Understandably, if pairing information is lost for non-digital key functions, such as when pairing for using the vehicle's entertainment functions is lost, the user can directly select to re-pair within the vehicle.

[0014] In one possible implementation of the first aspect, the Bluetooth chip can also be replaced with a communication module based on short-range communication technology, wherein the short-range communication technology includes one or more short-range wireless communication technologies such as Bluetooth, wireless-fidelity (Wi-Fi), ultra-wideband (UWB) technology, radio frequency identification (RFID), and stroboscopic technology. For example, the Bluetooth chip can replace the Wi-Fi chip, stroboscopic chip, etc.

[0015] In one possible implementation of the first aspect, the target pairing parameter further includes at least one Bluetooth MAC address from the second pairing parameter.

[0016] In the above implementation, the terminal can not only send the lost digital key ID to the server, but also provide the MAC address of the corresponding terminal. This makes it easier for the server to query the corresponding terminal and check and confirm the specific identity of the terminal, thus achieving accurate prompting of digital key loss.

[0017] In one possible implementation of the first aspect, the terminal's digital key ID is associated with the terminal's user credentials, which refer to the identity credentials of the terminal's user.

[0018] As one possible implementation, user credentials are communication numbers. Optionally, the terminal's communication number includes a cellular communication number defined in the subscriber identity module (SIM) installed on the terminal. Alternatively, the terminal's communication number may include the terminal's instant messaging number, such as a pre-set video communication number on the terminal, or a communication number pre-applied for in an application (such as the application's user ID). It should be understood that the terminal's user credentials can be registered with the server by the user and used after obtaining the user's consent.

[0019] In the above implementation, the digital key ID is associated with the terminal's communication number. Thus, the server can index the terminal's communication number through the digital key ID and send corresponding reminder information to the terminal. This simplifies the process of finding the terminal and ensures that the first reminder information is accurately delivered to the terminal, achieving accurate reminders of digital key loss.

[0020] In one possible implementation of the first aspect, the method is applied to a microcontroller unit (MCU).

[0021] Optionally, the first storage unit is an MCU. For example, the second pairing list described above is stored in the memory or registers of the MCU. Alternatively, the first storage unit may be a memory connected to the MCU.

[0022] In one possible implementation of the first aspect, the method further includes: periodically backing up the pairing list currently stored in the Bluetooth chip from the Bluetooth chip at a first time interval. By retrieving the pairing list from the Bluetooth chip and backing it up at a certain period, the vehicle can proactively obtain updates to its pairing parameters, improving the accuracy of missing parameter identification.

[0023] In one possible implementation of the first aspect, the method further includes: after pairing the Bluetooth chip with the first terminal, backing up the pairing list currently stored by the Bluetooth chip, the pairing list including first pairing parameters, the first pairing parameters including the Bluetooth MAC address of the first terminal and the digital key ID of the first terminal.

[0024] In the above method, if the Bluetooth chip and the terminal complete a new pairing process, the pairing list will be updated so that the pairing parameters of the paired terminal can be saved in a timely manner, avoiding the problem of inaccurate identification of lost pairing parameters due to long-term lack of backup, and improving the user experience.

[0025] In another possible implementation of the first aspect, the vehicle further includes a long-range communication module, through which the vehicle communicates with the server. The long-range communication module is a communication module that supports long-distance communication technology, such as a T-box terminal.

[0026] In another possible implementation of the first aspect, the method further includes: when the target terminal approaches the vehicle, outputting a non-pairing prompt message, the non-pairing prompt message being used to prompt the target terminal that the digital key ID corresponding to the target terminal in the vehicle is lost.

[0027] In the above implementation, the vehicle can output prompt information, such as sound, light, or electrical prompts, to remind the target terminal that the digital key ID on the vehicle side is lost, so that the target terminal can perform corresponding operations to resolve the pairing failure problem.

[0028] In another possible implementation of the first aspect, the Bluetooth chip in the vehicle can also be re-paired with the target terminal.

[0029] Secondly, this application provides a pairing relationship management method, including: receiving target pairing parameters from a first vehicle, determining the communication number of the target terminal based on the target pairing parameters and a communication number relationship table between the target pairing parameters and the terminal, and sending a first prompt message to the communication number of the target terminal, the first prompt message being used to indicate that the digital key ID corresponding to the target terminal in the first vehicle is lost.

[0030] This method can be applied to servers, for example, implemented by a server or a module within a server. These modules can include software modules, hardware modules, or a combination of both. For instance, the method can be executed by a chip or processor within the server. For ease of description, the following explanation uses a server as the executing entity.

[0031] In the above embodiments, the server can receive target pairing parameters from a first vehicle (exemplarily described as a vehicle). These target pairing parameters are pairing parameters not present in the Bluetooth chip, indicating a lost pairing relationship in the first vehicle. Based on the target pairing parameters, the server can query the communication number of the target terminal and send a prompt to the target terminal's communication number, enabling the target terminal to be aware of the loss of the digital key ID in the first vehicle in advance. This facilitates subsequent guidance for terminals paired with the first vehicle to discover and resolve the issue of the lost vehicle-side digital key ID, improving the user experience.

[0032] In one possible implementation of the second aspect, the target pairing parameters include the digital key ID of the target terminal, or the target pairing parameters include the Bluetooth MAC address of the target terminal and the digital key ID of the target terminal.

[0033] In one possible implementation of the second aspect, the first prompt information includes information about the first vehicle. This information uniquely identifies the first vehicle and may include, for example, one or more of the following: the first vehicle's Bluetooth MAC address, the first vehicle's VIN, and the first vehicle's device serial number. For example, the first prompt information includes the first vehicle's Bluetooth MAC address.

[0034] In the above embodiments, the information of the first vehicle makes it easier for users to find pairing information with the first vehicle and to accurately delete the pairing information corresponding to the first vehicle.

[0035] In one possible implementation of the second aspect, the terminal's digital key ID is associated with the terminal's user credentials, which refer to the identity credentials of the terminal's user.

[0036] As one possible implementation, the user credentials are a communication number. Optionally, the terminal's communication number includes the cellular communication number defined in the SIM card installed on the terminal. Alternatively, the terminal's communication number may include the terminal's instant messaging number, such as a pre-set video communication number in the terminal, a communication number pre-applied for in the application (such as the application's user ID), etc.

[0037] In one possible implementation of the second aspect, the first notification information includes at least one of SMS, Push message, or in-app message of the target application, the target application being installed on the first terminal.

[0038] In another possible implementation of the second aspect, the target terminal meets the reminder conditions, which include: the target terminal has not been reminded, or the target terminal has been reminded, the first terminal has not responded with a pairing relationship update and the interval between the current time and the time when the target terminal was last reminded exceeds a first duration threshold.

[0039] In the above implementation, the server will not indiscriminately trigger frequent reminders for target terminals corresponding to lost pairing parameters. For example, the server can pre-set reminder conditions, triggering reminders only for terminals that meet the conditions, thereby improving the user experience.

[0040] For example, when the first digital key ID is identified, the first terminal can be determined based on the first pairing parameters. If the first terminal has not been alerted, a first prompt message is sent to the first terminal. If the first terminal has been alerted, no first prompt message is sent to the first terminal.

[0041] As another example, the terminal can report back to the server whether it has performed the relevant operation. If the first terminal has already been alerted but has not received feedback, it will send an alert again after a first time threshold is reached. This first time threshold can be predefined, pre-configured in the server, or defined by the user.

[0042] In another possible implementation of the second aspect, the method further includes: receiving feedback information from the target terminal, the feedback information indicating that the target terminal has deleted the pairing information with the vehicle.

[0043] Thirdly, this application provides a pairing relationship management method, comprising: pairing a digital key with a first vehicle to obtain target pairing information with the first vehicle; receiving a first prompt from a server; and, in response to the first prompt, deleting the target pairing information with the first vehicle or displaying a second prompt indicating that the target pairing information with the first vehicle needs to be deleted. The first pairing information includes the Bluetooth MAC address of the first vehicle, and the first prompt is used to indicate that the digital key ID corresponding to the terminal in the first vehicle is lost.

[0044] This method can be applied to a terminal, for example, implemented by the terminal or a module within the terminal. This module can include software modules, hardware modules, or a combination of both. For example, the method can be executed by a chip or processor module within the terminal. For ease of description, the following explanation uses the first terminal as the executing entity.

[0045] In the above implementation, the terminal can receive a first prompt message to detect that the digital key ID stored in the first vehicle is lost, and delete the target pairing relationship with the first vehicle, or display a prompt message to remind the user that the target pairing information with the first vehicle needs to be deleted. In this way, the terminal paired with the first vehicle can be guided to discover and resolve the problem of the lost digital key ID on the vehicle side, avoiding failure when the user approaches the vehicle with the terminal to perform digital key pairing, thus improving the user experience.

[0046] In another possible implementation of the third aspect, the pairing information is used to enable the digital key in the corresponding terminal, which is used to control the vehicle.

[0047] In another possible implementation of the third aspect, the target pairing information further includes the digital key ID corresponding to the first vehicle.

[0048] In another possible implementation of the third aspect, the first prompt information further includes the Bluetooth MAC address of the first vehicle, the first pairing information is stored in a Bluetooth pairing list, the Bluetooth pairing list includes multiple pairing information entries, each pairing information entry includes the Bluetooth MAC address of a vehicle paired with the terminal and the digital key ID corresponding to the vehicle, and the multiple pairing information entries include the target pairing information.

[0049] Deleting the target pairing information with the first vehicle includes: searching for the target pairing information in the Bluetooth pairing list based on the first vehicle's Bluetooth MAC address. The target pairing information includes the first vehicle's Bluetooth MAC address and the digital key ID corresponding to the first vehicle. The target pairing information is then deleted from the Bluetooth pairing list.

[0050] In another possible implementation of the third aspect, the method further includes: re-pairing with the vehicle to re-obtain the pairing information with the first vehicle.

[0051] In another possible implementation of the third aspect, the first notification information includes at least one of SMS, push notification, or in-app message from the target application. The target application may be pre-installed on the terminal.

[0052] Fourthly, this application provides a pairing relationship management device, including a unit or module for performing the method described in the first aspect or any possible implementation of the first aspect. Exemplarily, the pairing relationship management device includes a processing unit and / or a communication unit. The processing unit is used to perform one or more operations such as processing, determining, generating, or calculating, and the communication unit is used to perform one or more operations such as acquiring, sending, and receiving.

[0053] Fifthly, this application provides a pairing relationship management apparatus, including units or modules for performing the methods described in the second aspect or any possible implementation of the second aspect. Exemplarily, the pairing relationship management apparatus includes a processing unit and / or a communication unit.

[0054] In a sixth aspect, this application provides a pairing relationship management apparatus, including a unit or module for performing the method described in the third aspect or any possible implementation of the third aspect. Exemplarily, the pairing relationship management apparatus includes a processing unit and / or a communication unit.

[0055] In a seventh aspect, this application provides a pairing relationship management device, which includes a processor and a memory. The memory provides storage space for storing computer instructions. The processor invokes the computer instructions stored in the memory to implement the method described in the first aspect or any possible implementation of the first aspect.

[0056] Eighthly, this application provides a pairing relationship management device, which includes a processor and a memory. The memory provides storage space for storing computer instructions. The processor invokes the computer instructions stored in the memory to implement the method described in the second aspect or any possible implementation of the second aspect.

[0057] Ninthly, this application provides a pairing relationship management device, which includes a processor and a memory. The memory provides storage space for storing computer instructions. The processor invokes the computer instructions stored in the memory to implement the method described in the third aspect or any possible implementation of the third aspect.

[0058] In a tenth aspect, this application provides a chip including a processor and an interface circuit. The interface circuit is used to receive signals from other devices (such as a pairing relationship management device) and transmit them to the processor, or to send signals from the processor to other devices (such as a pairing relationship management device). The processor is used through logic circuits or execution code instructions to implement the method described in the first aspect or any possible implementation of the first aspect, or to implement the method described in the second aspect or any possible implementation of the second aspect, or to implement the method described in the third aspect or any possible implementation of the third aspect.

[0059] In the eleventh aspect, this application provides a vehicle, which includes a Bluetooth chip, a first storage unit, and a pairing relationship management device. A first communication module is used to pair with a terminal. The pairing relationship management device includes a processor and a memory. The memory is used to provide storage space and to store computer instructions. The processor is used to call the computer instructions stored in the memory to execute the method described in the first aspect or any possible implementation of the first aspect.

[0060] Optionally, the first storage unit and the pairing relationship management device can be integrated into one device, for example, both the first storage unit and the pairing relationship management device can be integrated into the MCU. Alternatively, the first storage unit and the pairing relationship management device can be set separately, for example, the pairing relationship management device is the MCU, and the first storage unit is a memory connected to the MCU.

[0061] In a twelfth aspect, this application provides a server, which includes a pairing relationship management device. The pairing relationship management device includes a processor and a memory. The memory is used to provide storage space for storing computer instructions. The processor is used to invoke the computer instructions stored in the memory to execute the method described in the first aspect or any possible implementation of the first aspect, or to execute the method described in the second aspect or any possible implementation of the second aspect.

[0062] In a thirteenth aspect, this application provides a terminal, which includes a pairing relationship management device, a processor, and a memory. The memory provides storage space for storing computer instructions, and the processor invokes the computer instructions stored in the memory to execute the method described in the third aspect or any possible implementation thereof.

[0063] In a fourteenth aspect, this application provides a pairing relationship management system, which includes a vehicle (as described in the eleventh aspect), a server (as described in the twelfth aspect), and a terminal (as described in the thirteenth aspect). Furthermore, the pairing relationship management device also includes the server (as described in the twelfth aspect).

[0064] In a fifteenth aspect, this application provides a readable storage medium for storing a computer program that, when executed by a processor, causes a pairing management device including a processor to implement the method described in the first aspect or any possible implementation of the first aspect, or to implement the method described in the second aspect or any possible implementation of the second aspect, or to implement the method described in the third aspect or any possible implementation of the third aspect.

[0065] In a sixteenth aspect, this application provides a computer program product that, when executed by a processor, causes a pairing relationship management device including the processor to implement the method described in the first aspect or any possible implementation of the first aspect, or to implement the method described in the second aspect or any possible implementation of the second aspect, or to implement the method described in the third aspect or any possible implementation of the third aspect.

[0066] The beneficial effects of aspects two through sixteen of this application can be found in the beneficial effects of the scheme in aspect one. Attached Figure Description

[0067] The accompanying drawings used in the description of the embodiments will be briefly introduced below.

[0068] Figure 1 is a schematic diagram of the architecture of a pairing relationship management system provided in an embodiment of this application;

[0069] Figure 2 is a flowchart illustrating a pairing relationship management method provided in an embodiment of this application;

[0070] Figure 3 is a schematic diagram of information stored in a vehicle according to an embodiment of this application;

[0071] Figure 4 is a schematic diagram of information stored in a vehicle according to an embodiment of this application;

[0072] Figure 5 is a schematic diagram of a scenario in which a vehicle outputs an unpaired prompt message according to an embodiment of this application;

[0073] Figures 6-8 are schematic diagrams of the display interface provided in the embodiments of this application;

[0074] Figure 9 is a schematic diagram of a pairing relationship management device provided in an embodiment of this application;

[0075] Figure 10 is a schematic diagram of another pairing relationship management device provided in an embodiment of this application. Detailed Implementation

[0076] The following section provides an exemplary description of the systems and scenarios in which this application may be applied. It should be noted that the system architecture and business scenarios described in this application are for the purpose of more clearly illustrating the technical solutions of this application and do not constitute a limitation on the technical solutions provided in this application. It should be understood that as system architectures evolve and new business scenarios emerge, the technical solutions provided in this application are equally applicable to similar technical problems.

[0077] Please refer to Figure 1. Figure 1 is a schematic diagram of the architecture of a pairing relationship management system provided in an embodiment of this application. The pairing relationship management system includes a terminal 10, a vehicle 20, and a server 30. Wherein:

[0078] Terminal 10 is a communication-capable device capable of short-range communication with other devices. Terminal 10 can be used to receive user information input and output processing results, etc. It should be understood that Figure 1 uses a mobile phone as an example for illustration, but in specific implementations, terminal 10 can be, but is not limited to, mobile phones, tablets, handheld computers, desktop computers, laptops, ultra-mobile personal computers (UMPCs), netbooks, cellular phones, personal digital assistants (PDAs), smart home devices such as smart TVs and smart cameras, wearable devices such as smart bracelets, smartwatches, and smart glasses, extended reality (XR) devices such as augmented reality (AR), virtual reality (VR), and mixed reality (MR), and smart city devices, etc. In short, this application embodiment does not impose special limitations on the specific type of terminal 10.

[0079] In this application, terminal 10 and vehicle 20 have been paired. As shown in Figure 1, pairing information is stored in terminal 10, which indicates the pairing relationship between terminal 10 and vehicle 20.

[0080] Terminal 10 includes a short-range communication module and a long-range communication module. The short-range communication module refers to a module that supports communication using short-range communication technologies. For example, short-range communication technologies include, but are not limited to, SparkLink (or NearLink), 802.11b / g, Bluetooth, Zigbee, radio frequency identification (RFID), ultra-wideband (UWB) technology, or wireless short-range communication systems. For instance, the short-range communication module can be a Bluetooth chip. Long-range communication technologies include, but are not limited to, communication technologies based on Long Term Evolution (LTE), 5th Generation Mobile Networks (5th Generation Mobile Networks or 5th Generation Wireless Systems, 5th Generation, abbreviated as 5G or 5G technology), Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), and Universal Mobile Telecommunications System (UMTS), etc. The above explanations use wireless communication technologies as examples. In some solutions, the communication module may also support one or more of the following wired communication technologies: fiber optic connection, Ethernet, controller area network (CAN), local interconnect network (LIN), and CAN flexible data-rate (CAN FD).

[0081] In this application, terminal 10 also includes a digital key module, which implements the functions of a digital key and can be considered as a carrier for implementing these functions. The digital key module can control the vehicle based on digital information. In this application, the digital key module can be granted permissions; when the digital key module has the permission to control the vehicle, it can control the vehicle. This control includes, but is not limited to, unlocking the car, opening / or closing the car doors, or opening or closing in-vehicle functions (such as air conditioning, fragrance, etc.), one or more of these. Optionally, the digital key module can be a software module (such as a computer program, computer code, computer instructions, etc.), such as a digital key application (APP). Alternatively, the digital key module can also be a hardware module (such as a processor), or a combination of software and hardware. Exemplarily, the digital key module can include a digital key application module and a digital key pairing module, wherein the digital key application module is used to apply for a digital key from server 30, and correspondingly, the server returns digital key information to the terminal. The digital key pairing module is used to pair the digital key with vehicle 20. The main function of pairing is to enable the vehicle confirmation terminal to have the authority to control the vehicle, so that the digital key function in terminal 10 can be used.

[0082] Vehicle 20 is a means of transportation with both mobility and communication capabilities. It should be understood that the aforementioned "vehicle" is a vehicle in a broad sense, and can include means of transportation (such as commercial vehicles, passenger cars, motorcycles, electric bicycles, flying cars, trains, etc.), industrial vehicles (such as forklifts, trailers, tractors, etc.), engineering vehicles (such as excavators, bulldozers, cranes, etc.), agricultural equipment (such as lawnmowers, harvesters, etc.), etc. Vehicle 20 may include communication modules (such as short-range communication module 21 and long-range communication module 23), computing devices 22, and one or more subsystems. Among them:

[0083] The communication module includes a short-range communication module 21 for short-range communication and a long-range communication module 23 for long-range communication. For example, vehicle 20 can pair with terminal 10 via a Bluetooth chip (considered short-range communication module 21). Alternatively, vehicle 20 can send information to the server via a T-box (considered long-range communication module 23).

[0084] A computing device includes at least one processor, which is a circuit with processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a central processing unit (CPU), microprocessor unit (MPU), microcontroller unit (MCU), graphics processing unit (GPU), or electronic control unit (ECU). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits, which can be fixed or reconfigurable. For example, the processor may be a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as a field-programmable gate array (FPGA). In reconfigurable hardware circuits, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the corresponding function. Furthermore, a processor can also be a hardware circuit designed for artificial intelligence, which can be understood as a type of ASIC, such as a neural network processing unit (NPU), tensor processing unit (TPU), or deep learning processing unit (DPU). In some implementations, the computing device includes at least one processor integrated as a system-on-chip (SOC), commonly referred to as a SOC by those skilled in the art. This SOC may include at least one processor; when the SOC includes multiple processors, the types of processors can be different, such as including a CPU and an MCU.

[0085] For example, the computing device may be a data key controller, which can be an MCU. A digital key controller is a controller used to implement digital key technology. In some solutions, the functions performed by the digital key controller can be implemented by software, in which case the digital key controller can be a software module. Of course, this application also applies to cases where the digital key is a hardware module, or a hybrid hardware and software module.

[0086] Subsystems include, for example, a motion system, a control system, a sensing system, one or more peripheral devices, and a power supply and computing device. A subsystem may include one or more components, and subsystems or components may be interconnected via wired or wireless means.

[0087] Server 30, also known as a server-side application, cloud platform, etc., is a device with computing and communication capabilities. Server 30 typically concentrates a significant amount of computing resources, which can include physical devices or virtual units or software modules. For example, server 30 may include one or more physical servers, such as blade servers or rack servers. Alternatively, server 30 may contain one or more computing instances, which are virtualizations of computing resources, such as virtual machines or containers. In some solutions, server 30 can be a cloud service, providing corresponding interfaces to the outside world. Other devices can interact with the cloud service by calling these interfaces, and the cloud service can also transmit information to other devices through these interfaces.

[0088] In this embodiment of the application, the terminal 10 and the server 30 can communicate (i.e., they can transmit information to each other), and the server 30 and the vehicle 20 can also communicate (i.e., they can transmit information to each other).

[0089] We know that for two devices that have previously established a pairing relationship, such as terminal 10 and vehicle 20, when terminal 10 requests to establish a connection with vehicle 20 again, since they have previously paired and have saved pairing parameters (or pairing information), a fast pairing process can be performed based on the saved pairing parameters. Usually, no complex authentication is required, making the connection more convenient.

[0090] Because the pairing parameters are stored electronically, there is a risk of loss. If one of the terminals 10 and vehicle 20 loses its digital key ID, the terminal with the lost digital key ID cannot properly pair and connect with the terminal that has the pairing parameters, causing the pairing process to fail. In this situation, the user of the terminal whose pairing information has not been lost may repeatedly turn the connection on and off, restart, or reinstall the device, but these methods cannot resolve the pairing failure, resulting in a poor user experience.

[0091] Taking the use of the digital key of terminal 10 to control vehicle 20 as an example, when the digital key function is used for the first time, if terminal 10 and vehicle 20 are paired via Bluetooth, a complex digital key application process can be carried out between vehicle 20, server 30, and terminal 10. After each process is completed, the Bluetooth chip on the vehicle side can store the digital key ID and Bluetooth MAC address of terminal 10. Subsequently, when terminal 10 approaches vehicle 20 and communicates with vehicle 20, vehicle 20 can compare the Bluetooth MAC address of terminal 10 to determine that terminal 10 has the authority to use the digital key to control vehicle 20, enabling terminal 10 to control vehicle 20, such as starting the vehicle, opening the doors, opening the trunk, and other vehicle control operations.

[0092] Because the digital key ID and Bluetooth MAC address of terminal 10 are stored electronically, they are at risk of being lost. If the digital key ID and Bluetooth MAC address stored on vehicle 20 are lost, terminal 10 cannot unlock vehicle 20 using the digital key. Since the vehicle cannot detect the lost information, it is difficult to notify terminal 10. Without the user's awareness, when the user approaches the vehicle with terminal 10, the vehicle cannot be unlocked. Furthermore, because the pairing information still exists on terminal 10, it cannot detect the loss of pairing parameters on vehicle 20. When pairing failure is displayed, it cannot promptly locate the problem. At this point, the user may repeatedly turn the mobile terminal's Bluetooth switch on and off, or reapply for a key, without resolving the issue, resulting in a poor user experience.

[0093] Beyond vehicle control scenarios, the aforementioned issues also exist in other scenarios where devices connect via pairing, such as electric bicycle control, smart homes, smart factories, and smart showrooms. For example, in a smart home scenario, various devices connect using short-range communication technology. In this case, a digital key ID on a particular device might cause it to lose control. For instance, the control device for smart curtains needs to establish a pairing relationship with the gateway. The user sends commands to the control device through the gateway to control the curtains, such as opening, closing, or changing their light transmission mode. If the pairing relationship between the smart curtains and the gateway is lost, the gateway cannot pair with the smart curtains and thus cannot control them.

[0094] To address the aforementioned issues, this application provides a pairing relationship management method and related apparatus. In this application, the Bluetooth chip itself stores a first pairing list, which includes the Bluetooth MAC address and digital key ID of the terminal that has completed digital key pairing with the vehicle. Furthermore, the first storage unit also stores a second pairing list, which also records the Bluetooth MAC address and digital key ID of the terminal that has completed digital key pairing with the vehicle. This second pairing list is backed up from the Bluetooth chip, and the backup time is earlier than the generation time of the first pairing list; that is, the second storage unit pre-backs up the pairing list. Thus, by comparing the first and second pairing lists, the vehicle can detect missing pairing parameters (i.e., target pairing parameters) in the Bluetooth chip and alert the terminal corresponding to the missing pairing parameter via a server. Correspondingly, the server can look up the device information of the corresponding terminal based on the digital key ID and send a corresponding alert message to the corresponding terminal, enabling the terminal to perceive the digital key ID on the vehicle side.

[0095] The solution provided in this application enables vehicles to identify lost pairing parameters, thereby facilitating the subsequent guidance of the terminal to discover and resolve issues related to the vehicle's digital key ID and improving the user experience.

[0096] Furthermore, in this application, each pairing parameter in the first pairing list and the second pairing list includes the terminal's Bluetooth MAC address and digital key ID. Since the terminal may have used other functions in the vehicle via Bluetooth connection, combining the Bluetooth MAC address and digital key ID as pairing parameters ensures that the pairing parameters are dedicated to the digital key process, accurately identifying the loss of pairing parameters corresponding to the digital key function, and specifically solving the problem of pairing failure caused by the loss of digital key ID.

[0097] The pairing relationship management method provided in the embodiments of this application will be described below. It should be noted that, for ease of explanation, the embodiments described below use the loss of pairing parameters between a first vehicle and a first terminal as an example. Here, the first vehicle includes vehicles or equipment such as cars, bicycles, electric bicycles, trains, and mobile robots. In specific implementations, the vehicle can also be replaced with other pairable devices, such as home appliances, industrial equipment, smart exhibition hall equipment, and urban facilities.

[0098] Please refer to Figure 2, which is a flowchart illustrating a pairing relationship management method provided in an embodiment of this application. Optionally, this method can be applied to the aforementioned pairing relationship management system, as shown in Figure 1. The pairing relationship management method shown in Figure 2 may include one or more steps S201 to S208. It should be understood that, for ease of description, the method is described in the order of steps S201 to S208, and is not intended to limit the execution to the above order. This application embodiment does not limit the order of execution, execution time, or number of executions of the above one or more steps. Steps S201 to S208 are as follows:

[0099] Step S201: The first terminal pairs with the first vehicle using a digital key to obtain target pairing information.

[0100] Correspondingly, the first vehicle is also paired with the first terminal using a digital key. Here, "first vehicle" is used to exemplarily describe a vehicle, and "first terminal" is used to exemplarily describe a terminal, and "terminal" is used to exemplarily describe a terminal. Digital key pairing is performed between the terminal (e.g., the first terminal) and the vehicle (e.g., the first vehicle) for the authorization process of the terminal using a digital key (or digital key module) to control the vehicle. Its main function is to verify whether the terminal has the authority to control the vehicle. When digital key pairing is successful, the first terminal can save the pairing information, which indicates the pairing relationship with the vehicle. For example, the target pairing information includes a digital key ID and information about the first vehicle, or includes one or more of the following: digital key ID, information about the first vehicle, pairing code, key information, security algorithm information, random number information, or other information used for connection. For example, the pairing information may include a long-term key (LTK). In some schemes, this pairing information is used to use the digital key and can also be called data key information.

[0101] One possible digital key pairing process is as follows: The terminal obtains a first pairing code issued by the server and sends the first pairing code to the vehicle. The vehicle receives the first pairing code from the terminal and compares it with a locally generated second pairing code. If the comparison matches, it indicates that the terminal has the authority to control the vehicle, and the digital key pairing is successful. The vehicle may include the terminal's digital key ID and the terminal's Bluetooth MAC address. The vehicle can indicate successful pairing to the terminal, and the terminal saves the pairing information. For example, the vehicle can send an activation command to the terminal to activate the terminal's digital key function. The terminal receives the activation command and saves the pairing information for use of the digital key function. The terminal can use the digital key module to send control commands to the vehicle, and the vehicle responds to the control commands by performing corresponding control operations. These control operations include, but are not limited to, unlocking the car, opening / or closing the car doors, or turning on or off in-vehicle functions (such as air conditioning, fragrance, etc.) one or more of these.

[0102] Of course, the aforementioned method of directly sending the pairing code is merely an example and not intended to limit the digital key pairing process. As another example of a digital key pairing process, the terminal can use a first pairing code from the server to encrypt, scramble, or derive verification information and send it to the vehicle. The vehicle uses a local second pairing code to obtain the verification information in the same way and compares the verification information with the check information to determine if the terminal has obtained a pairing code consistent with the vehicle's. Alternatively, the digital key pairing process can also refer to some existing digital key pairing processes.

[0103] In this application, the first vehicle includes a communication module, and the first terminal can be paired with the communication module in the first vehicle. Optionally, the communication module can communicate based on short-range communication technology, including one or more communication technologies such as Bluetooth, Wi-Fi, UWB, RFID, and satellite navigation. For example, the communication module can be a Bluetooth chip; this application embodiment uses a Bluetooth chip as an example for illustration.

[0104] Referring to Figure 3, after the digital key pairing process between the first terminal (Bluetooth MAC address D1) and the first vehicle (Bluetooth MAC address V1), the communication module of the first vehicle, such as a Bluetooth chip, can store the pairing parameters corresponding to the first terminal, for example, referred to as pairing parameter P1. This pairing parameter P1 can be stored in a pairing list, and includes the Bluetooth MAC address of the first terminal and the digital key ID of the first terminal. For example, if the first terminal successfully pairs with the Bluetooth chip of the first vehicle, the Bluetooth chip stores the following pairing parameter P1 in the pairing list S1: the Bluetooth MAC address of the first terminal (denoted as D1) and the digital key ID of the first terminal (denoted as S001). This pairing list S1 can be generated at time T0. Furthermore, the pairing between the first terminal and the first vehicle is completed before time T0.

[0105] Since pairing parameters are stored in the communication chip as digital information, the pairing parameters stored in the Bluetooth chip may be lost after a period of time. Referring to Figure 4, after a period of time, the digital key ID corresponding to the first terminal in the pairing list S3 currently stored in the Bluetooth chip (e.g., at time T1) has been lost, and time T1 is after time T0.

[0106] Understandably, a Bluetooth pairing table can also be stored in the terminal. This table includes multiple pairing entries, each containing the Bluetooth MAC address of a vehicle paired with the terminal and the corresponding digital key ID. For example, the first terminal can store a pairing table as shown in Table 1. The Bluetooth pairing table may include target pairing information, such as: Bluetooth MAC address V1, digital key ID S001.

[0107] Table 1 Bluetooth Pairing Table for the First Terminal

[0108] It should be understood that the various embodiments of this application use tables to display the stored relationships for ease of description. In actual implementation, relationships, pairing lists, etc., can be stored in tabular form, or in the form of a set of corresponding relationships or a database table; their form is not limited here.

[0109] Step S202: The first vehicle obtains the first pairing list.

[0110] Specifically, step S202 can be executed by a pairing relationship management device in the first vehicle. This pairing relationship management device can be a software module, a hardware module, or a combination of software and hardware. For example, the pairing relationship management device can be a computing device 22 in the vehicle 20, such as an MCU.

[0111] The first pairing list is the pairing list currently stored in the Bluetooth chip. The first pairing list may include N first pairing parameters, where N is an integer and N≥0. This first pairing list can be generated at the first moment. Each first pairing parameter includes the Bluetooth MAC address and the digital key ID of a terminal that has completed digital key pairing with the first vehicle before the first moment.

[0112] Please refer to Figure 4. The first pairing list is, for example, the pairing list S3 generated at time T1. The pairing list S3 includes one first pairing parameter. Each first pairing parameter includes the Bluetooth MAC address (e.g., D3) and the digital key ID (e.g., S003) of a terminal that has completed digital key pairing with the first vehicle before time T1.

[0113] Optionally, the first pairing list can be empty. In this case, there are no pairing parameters in the first pairing list. That is, before time T1, from the perspective of the Bluetooth chip, no terminal has completed digital key pairing with the first vehicle.

[0114] In this embodiment, each pairing parameter in the first pairing list includes the terminal's Bluetooth MAC address and digital key ID. The Bluetooth MAC address uniquely identifies the terminal's hardware address, while the digital key ID is associated with the terminal's user credentials and indicates the terminal's authority to control the first vehicle. Since the terminal may have used other functions of the first vehicle via Bluetooth connection, combining the Bluetooth MAC address and digital key ID as pairing parameters ensures that the pairing parameters are specifically used in the digital key process, accurately identifying the loss of pairing parameters corresponding to the digital key function.

[0115] Optionally, the terminal's Bluetooth MAC address can be replaced with other unique identifiers that distinguish the terminal, such as the terminal's device serial number, ID, etc.

[0116] Step S203: The first vehicle obtains the second pairing list.

[0117] Specifically, step S203 can be executed by the pairing relationship management device in the first vehicle. This pairing relationship management device can be a software module, a hardware module, or a combination of software and hardware. For example, the pairing relationship management device can be a computing device in the first vehicle, such as an MCU, CPU, etc.

[0118] The second pairing list comes from the first storage unit. That is, the second pairing list is stored by the first storage unit, and the first vehicle can specifically obtain the second pairing list from the first storage unit. The second pairing list includes M second pairing parameters and includes a backup of the pairing list stored by the Bluetooth chip at the second time point. As shown in Figure 3, the first storage unit stores a backup of the pairing list stored by the Bluetooth chip at time T0. Therefore, the pairing list S2 includes the pairing parameters corresponding to terminal D1 (i.e., the terminal with Bluetooth MAC address D1) and terminal D2 (i.e., the terminal with Bluetooth MAC address D2), respectively. Referring to Figures 3 and 4, the second time point T0 is earlier than the first time point T1.

[0119] In the M second pairing parameters of the second pairing list, each second pairing parameter includes the Bluetooth MAC address and digital key ID of a terminal that completed digital key pairing with the first vehicle before the second time. Referring to Figures 3 and 4, the second pairing list can be regarded as a partial list of pairing list S2, that is, the second pairing list includes the pairing parameters of terminals D1 and D2 backed up at time T0, both of which completed digital key pairing with the first vehicle before the second time T0.

[0120] Of course, the pairing list S2 may also include pairing lists backed up at other times. Referring to Figure 4, the pairing list S2 also includes the pairing parameters corresponding to terminal D3. Terminal D3 can complete pairing with the first vehicle after the first moment.

[0121] In some possible implementations, the first storage unit may be integrated into the pairing relationship management device, or the first storage unit may be separately configured from the pairing relationship management device but connected to it. Exemplarily, step S203 is executed by the MCU, and the first storage unit is the MCU. Even more exemplaryly, step S203 is executed by the MCU, and the first storage unit is a memory connected to the MCU, located outside the MCU.

[0122] As mentioned earlier, the second pairing list is a backup of the pairing list generated in the Bluetooth chip at a certain point in time. In some possible designs, the timing of the backup can vary; two designs are illustrated below:

[0123] Design 1: The first vehicle periodically backs up the pairing list currently stored in the Bluetooth chip from the Bluetooth chip at a time interval. By retrieving the pairing list from the Bluetooth chip and backing it up at a certain period, the first vehicle can proactively obtain updates to its pairing parameters, improving the accuracy of missing parameter identification. This first time interval can be pre-designed, pre-defined, or pre-configured in the first vehicle. For example, the first time interval can be 1 minute, meaning that the first vehicle (or specifically the MCU) copies the pairing list stored in the Bluetooth chip and backs it up in the first storage unit every 1 minute. Of course, this first time interval can also be additionally designed; for example, the first time interval can have different values ​​in different scenarios.

[0124] Design 2: When the backup conditions are met, the first vehicle backs up the currently stored pairing list from the Bluetooth chip. The backup conditions can be designed according to actual needs, such as one or more of the following: after executing a new pairing process, before locking the vehicle, after the vehicle is powered on.

[0125] For example, after the Bluetooth chip and the first terminal are paired, the pairing list currently stored by the Bluetooth chip is backed up. The pairing list includes first pairing parameters, which include the Bluetooth MAC address and digital key ID of the first terminal. That is, if the Bluetooth chip and the terminal complete a new pairing process, the pairing list is updated to ensure that the pairing parameters corresponding to the paired terminals are saved in a timely manner. This avoids the problem of inaccurate identification of lost pairing parameters due to a lack of backup for a long time, thus improving the user experience.

[0126] Step S204: Determine that at least one second pairing parameter in the second pairing list does not exist in the first pairing list.

[0127] At least one of the second pairing parameters is a pairing parameter that the Bluetooth chip has lost. Referring to Figure 4, the pairing parameters corresponding to terminals D1 and D2 in pairing list S2 are not present in pairing list S3. Referring to Figures 3 and 4, at least one of the second pairing parameters may be lost due to reasons such as insufficient storage space, chip upgrades, or accidental formatting of the storage space, resulting in the loss of the digital key ID. Of course, this application does not limit the reasons for the loss of the digital key ID.

[0128] Taking the first terminal (Bluetooth MAC address D1) as an example, after time T1, when the user of the first terminal approaches the vehicle with the first terminal to pair it, the pairing cannot be successful because the Bluetooth chip of the first vehicle no longer contains the pairing parameters corresponding to the first terminal, thus rendering the digital key function in the first terminal unusable.

[0129] In some possible implementations, when a user determines that the pairing parameters have been lost, the first vehicle outputs a non-pairing prompt message when the target terminal (e.g., the first terminal) approaches the first vehicle. This non-pairing prompt message is used to alert the target terminal that the digital key ID corresponding to the target terminal in the vehicle is lost. For example, the non-pairing prompt message can be in the form of sound, light, or electricity to remind the corresponding terminal. Taking the first terminal as an example, when the first vehicle recognizes the digital key ID corresponding to the first terminal, if the user brings the first terminal near the first vehicle, the first vehicle can output a prompt, facilitating the first terminal to perform corresponding operations to resolve the pairing failure. Several possible prompt formats are described below:

[0130] Prompt Form 1: Audio Prompt. As shown in Figure 5, for example, the first vehicle has already identified terminal 10 and its digital key ID. When a user brings terminal 10 close to vehicle 20, vehicle 20 obtains the identifier of terminal 10 (e.g., Bluetooth MAC address) and determines that the pairing relationship corresponding to terminal 10 has been lost. Vehicle 20 can output a voice prompt, "The vehicle's pairing parameters have been lost. Please delete the digital key information and re-pair," thereby indicating that the pairing relationship between vehicle 20 and terminal 10 has been lost and prompting terminal 10 to delete the pairing relationship with vehicle 20, such as deleting the target pairing information and re-pairing with vehicle 20.

[0131] Prompt Form 2: Indicator Light Prompt. For example, the first vehicle has predefined pairing relationship indicator lights, such as the left front light, contour light, fog light, or high beam of the reusable vehicle. When these lights are lit in a certain color and flashing frequency, it indicates that the pairing relationship between the first vehicle and the first terminal has been lost, thus prompting the first terminal to delete the pairing relationship with the first vehicle and re-pair with the first vehicle.

[0132] Prompt Form 3: Projection Instruction. As shown in Figure 5, a projection device is installed in the vehicle 20. This projection device can project graphic or text information. Through the projected image, it can prompt the user that the pairing relationship between the vehicle 20 and the terminal 10 has been lost, or prompt the terminal 10 to delete the pairing relationship with the vehicle 20, or prompt the terminal 10 to re-pair with the vehicle 20.

[0133] Step S205: The first vehicle sends target pairing parameters to the server. Correspondingly, the server receives the target pairing parameters from the first vehicle.

[0134] The target pairing parameter includes at least one digital key ID from at least one second pairing parameter. This at least one second pairing parameter refers to the pairing parameter identified in step S204 as existing in the second pairing list but not in the first pairing list, such as the pairing parameters corresponding to terminals D1 and D2 in pairing list S2 shown in Figure 4. The target pairing parameter includes the digital key ID of at least one second pairing parameter; taking Figure 4 as an example, the target pairing parameters are S001 and S002.

[0135] The terminal's digital key ID is associated with the terminal's user credentials, which refer to the user's identity credentials. Furthermore, the server can index the terminal's user credentials through the digital key ID, thereby enabling it to send alert messages to the terminal.

[0136] As one possible implementation, user credentials are communication numbers. Optionally, the terminal's communication number includes the cellular communication number defined in the SIM card installed on the terminal. Alternatively, the terminal's communication number may include the terminal's instant messaging number, such as a pre-set video communication number on the terminal, or a communication number pre-applied for in an application (such as the application's user ID). It should be understood that the terminal's user credentials can be registered with the server by the user and used after obtaining the user's consent.

[0137] In some possible implementations, the target pairing parameters also include the terminal's Bluetooth MAC address. For example, referring to Figure 4, the target pairing parameters are the pairing parameters corresponding to terminal D1 (i.e., D1 and S001) and the pairing parameters corresponding to terminal D2 (i.e., D2 and S001). The terminal can not only send the lost digital key ID to the server, but also provide the corresponding terminal's Bluetooth MAC address. This facilitates the server in querying the corresponding terminal and verifying its specific identity, enabling accurate alerts for lost digital keys.

[0138] Furthermore, the first vehicle also includes a long-range communication module, such as a T-box. The first vehicle communicates with the server via the long-range communication module.

[0139] Step S206: The server determines the target terminal based on the target pairing parameters and the table showing the relationship between the target pairing parameters and the terminal communication number.

[0140] Step S206 described above can be executed by a module in the server. The target pairing parameter includes at least one digital key ID from the second pairing parameter. The terminal's digital key ID is associated with the terminal's user credentials (e.g., a communication number). The server can use the target pairing parameter to find the terminal's device information, thereby determining the target terminal corresponding to the target pairing parameter. The terminal's device information is used to send information to the terminal. For example, the terminal's device information includes one or more of the terminal's user credentials, the terminal's communication address, or the terminal's contact information.

[0141] Please refer to Table 2, which is a table showing the relationship between target pairing parameters and terminal communication numbers provided in this application. This table indicates the correspondence between the terminal's key ID and its communication number. The server can query the terminal's communication number from this correspondence using the target pairing parameters, thereby determining the target terminal corresponding to the target pairing parameters. For example, the target pairing parameters include the digital key ID corresponding to terminal D1. Accordingly, the server can determine the communication number of terminal D1 as NUM1 based on the digital key ID corresponding to terminal D1.

[0142] Table 2 Relationship between target pairing parameters and terminal communication number

[0143] Understandably, the communication number can also be replaced with other user credentials, such as the terminal's device information; Table 2 here is just an example.

[0144] Understandably, the target terminal may include one or more terminals. The following description will continue with the first terminal in the target terminal as an example.

[0145] Step S207: The server sends a first prompt message to the first terminal. Accordingly, the first terminal receives the first prompt message from the server.

[0146] The first prompt message is used to indicate the digital key ID corresponding to a first terminal in the vehicle. This first terminal is an exemplary terminal among the target terminals. When the target terminals include multiple terminals, the server can send the first prompt message to each of the multiple terminals respectively, thereby indicating the digital key ID of that terminal stored in the vehicle.

[0147] Optionally, the first prompt information includes information about the first vehicle. This information uniquely identifies the first vehicle and may include, for example, one or more of the following: the first vehicle's Bluetooth MAC address, the first vehicle's VIN, and the first vehicle's device serial number. For example, the first prompt information includes the first vehicle's Bluetooth MAC address.

[0148] In some possible implementations, the server will not indiscriminately trigger frequent reminders for target terminals corresponding to lost pairing parameters. For example, the server can pre-set reminder conditions, triggering reminders only for terminals that meet the conditions, thereby improving the user experience. For instance, when the first vehicle detects that pairing parameter P1 is lost, it can report the digital key ID in pairing parameter P1 to the server. The server can then identify the first terminal based on the digital key ID corresponding to the first terminal. If the first terminal has not been reminded, a first prompt message is sent to the first terminal. If the first terminal has been reminded, no first prompt message is sent. As another example, the terminal can provide feedback to the server regarding whether it has performed a relevant operation. In this case, if the first terminal has already been reminded but has not received feedback, a reminder message is sent again after a first time threshold is reached. This first time threshold can be pre-defined, pre-configured in the server, or defined by the user.

[0149] Step S208: The first terminal deletes the target pairing information or displays a second prompt message indicating that the target pairing information needs to be deleted.

[0150] The target pairing information is obtained after the first terminal and the first vehicle are paired using a digital key. When the digital key ID corresponding to the first terminal stored in the first vehicle is lost, this target pairing information can no longer be used to connect to the first vehicle, and the digital key function in the first terminal can no longer be used. The first terminal needs to re-execute the digital key pairing process with the first vehicle to establish a pairing relationship and obtain new pairing information.

[0151] As one possible implementation, the first terminal responds to the first prompt message and deletes the currently invalid pairing information, so as to trigger the re-pairing process when it approaches the first vehicle.

[0152] Consider a possible scenario: if the first terminal does not detect the loss of pairing parameters in the first vehicle, it might use the pairing parameters obtained during the last pairing to connect to the first vehicle, hoping to use the digital key function. However, the first vehicle can no longer recognize the terminal, resulting in connection failure and rendering the terminal's digital key function unusable. In this embodiment, the terminal can detect the loss of pairing parameters in the first vehicle and actively delete the pairing information with the first vehicle. Therefore, the two can directly re-perform the digital key pairing process, i.e., the initial configuration process of the terminal's digital key, reactivating the first terminal's digital key function and facilitating its restoration to normal operation.

[0153] As another possible implementation, after receiving the first prompt information, the first terminal can output a second prompt information to remind the user that the target pairing information needs to be deleted. For example, the second prompt information could indicate that the digital key ID of the first vehicle is lost, or prompt the user to delete the pairing information with the first vehicle, or prompt the user to re-pair with the first vehicle. For instance, the second prompt information could be in the form of sound, light (including the user interface display), or electricity, to remind the user that the digital key ID corresponding to the first terminal on the vehicle side has been lost, thereby guiding the user to perform the appropriate operation to resolve the pairing failure.

[0154] For example, the terminal can display a first interface, which includes a second prompt message. As shown in Figure 6, which is a schematic diagram of the display interface of a terminal according to an embodiment of this application, the first prompt message can be an SMS message. The terminal 10 can display a third interface 12, which may include a second prompt message 13. The second prompt message 13 can be presented as text, graphics, or symbols, etc., to prompt the user that the pairing relationship between the first vehicle and the first terminal has been lost, or to prompt the user to delete the pairing relationship with the first vehicle, or to prompt the user to re-pair the first terminal with the first vehicle, etc. For example, referring to Figure 6, the second prompt message is a text-based prompt, such as "The digital key ID of vehicle XXXX has been lost, the digital key service is unavailable, please delete the local pairing information and re-pair."

[0155] Figure 7 is a schematic diagram of the display interface of another terminal provided in this application embodiment. The first prompt message can be in the form of a PUSH message. As shown in Figure 7(a), the terminal 10 can display a third interface 12. When the third interface 12 can be a main interface, a lock screen interface, or an application interface, the third interface 12 can include a second prompt message 13. The second prompt message 13 is presented in the form of a notification bar card, and can specifically include one or more of text, graphics, or symbols. Referring to Figure 7(a), the second prompt message is a text prompt, such as "The pairing information for vehicle XXXX has been lost. Please delete the local pairing information and re-pair."

[0156] Alternatively, the third interface 12 can also be a drop-down notification bar interface. As shown in Figure 7(b), the third interface can also display a second prompt message 13, which is presented in the form of a notification bar card.

[0157] Figure 8 is a schematic diagram of the display interface of another terminal provided in this application embodiment. The target application is installed in the terminal 10, and the third interface 12 is the main page (or in-system message interface) of the third application. The third interface 12 may include a second prompt message 13. The second prompt message 13 may include one or more of the following: text, graphics, or symbols. Referring to Figure 8, the second prompt message includes the symbol "!" and the text "Digital key ID has been lost", which can prompt the digital key ID corresponding to the terminal 10 on the first vehicle side.

[0158] It should be noted that the two implementations mentioned above can be combined. For example, the first terminal displays a second prompt message indicating that the target pairing information needs to be deleted, and deletes the target pairing information after receiving the first operation instruction message input by the user (or if no cancellation operation instruction is received from the user within a certain period of time).

[0159] In one possible implementation, the first terminal may also send feedback information to the server, which indicates that the first terminal has deleted the pairing relationship with the first vehicle.

[0160] In the embodiment shown in Figure 2, the vehicle's first storage unit backs up the second pairing list, thereby additionally and backuply recording a pairing list between the vehicle and terminals within the vehicle. This backup occurs earlier than the generation time of the first pairing list, allowing for the backup recording of pairing parameters of terminals paired with the vehicle. By comparing the first and second pairing lists, the vehicle can identify missing pairing parameters (i.e., target pairing parameters) in the Bluetooth chip and alert the corresponding terminal via the server. Correspondingly, the server can locate the device information of the corresponding terminal based on the digital key ID and send a corresponding alert message to the terminal, enabling it to perceive the vehicle's digital key ID. This facilitates subsequent guidance for the terminal to discover and resolve issues related to the vehicle's digital key ID, improving the user experience.

[0161] In some possible implementations, the first vehicle may not need to identify lost pairing parameters. Instead, it can provide a first pairing list and a second pairing list to the server (e.g., send them to the server), and the server can identify the lost pairing parameters. A first notification message is then sent to the terminal corresponding to the lost pairing parameter. In other words, the aforementioned step S204 can be performed by the server.

[0162] The methods of the embodiments of this application have been described in detail above. The apparatus of the embodiments of this application is provided below.

[0163] It should be understood that the division of units in the apparatus provided in this application embodiment is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units in the apparatus can be implemented by a processor calling software. For example, the apparatus includes a processor connected to a memory, which stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of each unit of the apparatus. The processor is, for example, a general-purpose processor, such as a CPU or MPU, and the memory is either internal or external to the apparatus.

[0164] Alternatively, the units in the device can be implemented as hardware circuits. The functionality of some or all of the units can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an ASIC, and the functionality of some or all of the above units is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a PLD (Programmable Logic Controller). Taking an FPGA as an example, it can include a large number of logic gates, and the connection relationships between these logic gates are configured through configuration files to achieve the functionality of some or all of the above units.

[0165] In the embodiments of this application, each unit in the device may be one or more processors (or processing circuits) configured to implement the above methods, such as: CPU, GPU, NPU, TPU, DPU, MPU, digital signal processor (DSP), ASIC, FPGA, or a combination of at least two of these processor forms.

[0166] Furthermore, the units in the above devices can be integrated in whole or in part, or they can be implemented independently. In one implementation, these units are integrated together and implemented in the form of a System-on-Chip (SoC). The SoC may include at least one processor for implementing any of the above methods or implementing the functions of the units in the device. The at least one processor may be of different types, such as including a CPU and an FPGA, or including a CPU and an MCU, or including a CPU and a GPU, etc. Several possible devices are listed below.

[0167] Please refer to Figure 9, which is a schematic diagram of a pairing relationship management device provided in an embodiment of this application. Optionally, the pairing relationship management device 90 can be an independent device, such as a vehicle, terminal, server, computing device (e.g., computing device 22), etc. Alternatively, the pairing relationship management device 90 can also be a component in an independent device (such as a pairing relationship management device), such as a chip or integrated circuit. The pairing relationship management device 90 is used to implement the aforementioned pairing relationship management method, such as the pairing relationship management method and its possible implementations shown in the embodiment of Figure 2.

[0168] For example, the pairing relationship management device 90 includes a processing unit 901 and a communication unit 902. The processing unit 901 is used to perform one or more operations such as processing, determining, generating, calculating, and updating, while the communication unit 902 is used to perform one or more operations such as sending, receiving, and acquiring. It should be understood that the unit division here is only illustrative; in a specific implementation, some units may be combined together, or a single unit may be divided into multiple units.

[0169] In one possible design, the pairing relationship management device 90 is used to implement the method on the first vehicle side in the aforementioned pairing relationship management method.

[0170] In one possible implementation, the communication unit 902 is used to obtain a first pairing list currently stored in the Bluetooth chip, and to obtain a second pairing list from the first storage unit. The processing unit 901 is used to determine that at least one second pairing parameter in the second pairing list does not exist in the first pairing list, and the communication unit 902 is also used to send the target pairing parameter to the server.

[0171] In one possible implementation, the processing unit 901 and the communication unit 902 are further configured to periodically back up the pairing list currently stored in the Bluetooth chip from the Bluetooth chip for a first duration.

[0172] In one possible implementation, the communication unit 902 is also used to back up the pairing list currently stored in the Bluetooth chip after the Bluetooth chip has been paired with the first terminal.

[0173] In another possible implementation, the pairing relationship management device 90 further includes an output unit. The output unit is used to output a non-pairing prompt message when the target terminal approaches the vehicle. The non-pairing prompt message is used to indicate to the target terminal that the digital key ID corresponding to the target terminal in the vehicle has been lost.

[0174] For a detailed description of the above design, please refer to the description of the aforementioned method embodiments.

[0175] In one possible design, the pairing relationship management device 90 is used to implement the server-side method in the aforementioned pairing relationship management method.

[0176] In another possible implementation, the communication unit 902 is used to receive target pairing parameters from the first vehicle, and the processing unit 901 is used to determine the communication number of the target terminal according to the target pairing parameters and the communication number relationship table between the target pairing parameters and the terminal. The communication unit 902 is also used to send a first prompt message to the communication number of the target terminal. The first prompt message is used to indicate that the digital key ID corresponding to the target terminal in the first vehicle is lost.

[0177] In another possible implementation, the communication unit 902 is also configured to receive feedback information from the target terminal, the feedback information indicating that the target terminal has deleted the pairing information with the vehicle.

[0178] In one possible design, the pairing relationship management device 90 is used to implement the method on the first terminal side of the aforementioned pairing relationship management method.

[0179] In one possible implementation, the processing unit 901 and the communication unit 902 are used to pair a digital key with the first vehicle to obtain target pairing information with the first vehicle. The communication unit 902 is also used to receive a first prompt message from the server. The processing unit 901 is further used to, in response to the first prompt message, delete the target pairing information with the first vehicle or display a second prompt message indicating that the target pairing information with the first vehicle needs to be deleted. The first pairing information includes the Bluetooth MAC address of the first vehicle, and the first prompt message indicates that the digital key ID corresponding to the terminal in the first vehicle is lost.

[0180] In another possible implementation, the first prompt information also includes the Bluetooth MAC address of the first vehicle, and the first pairing information is stored in a Bluetooth pairing list. The Bluetooth pairing list includes multiple pairing information entries, each of which includes the Bluetooth MAC address of a vehicle paired with the terminal and the digital key ID corresponding to the vehicle. The multiple pairing information entries include target pairing information.

[0181] The processing unit 901 is further configured to search for target pairing information in the Bluetooth pairing list based on the Bluetooth MAC address of the first vehicle. The target pairing information includes the Bluetooth MAC address of the first vehicle and the digital key ID corresponding to the first vehicle. The processing unit 901 is further configured to delete the target pairing information from the Bluetooth pairing list.

[0182] In another possible implementation, the processing unit 901 and the communication unit 902 are also used to re-pair with the vehicle in order to regain the pairing information with the vehicle.

[0183] Please refer to Figure 10, which is a schematic diagram of a pairing relationship management device provided in an embodiment of this application. As shown in Figure 10, the pairing relationship management device 100 can be an independent device, such as a vehicle, terminal, server, or computing device. Alternatively, the pairing relationship management device 100 can also be a component within an independent device, such as a chip or integrated circuit. This pairing relationship management device 100 is used to implement the aforementioned pairing relationship management method, such as the pairing relationship management method and its possible implementations shown in the embodiment of Figure 2.

[0184] The pairing relationship management device 100 may include at least one processor 1001 and a memory 1003. Optionally, it may also include a communication interface 1002. Further optionally, it may also include a connection line 1004, wherein the processor 1001, the communication interface 1002 and / or the memory 1003 are connected via the connection line 1004, and / or communicate with each other via the connection line 1004 to transmit control signals and / or data signals.

[0185] in:

[0186] Processor 1001 is a module that performs arithmetic and / or logical operations, and may specifically include one or more of the following modules: CPU, application processor (AP), MCU, ECU, GPU, MPU, ASIC, image signal processor (ISP), DSP, FPGA, complex programmable logic device (CPLD), or coprocessor, etc.

[0187] The communication interface 1002 can be used to provide information input or output to at least one processor, or to receive and / or transmit signals to externally transmitted signals. For example, the communication interface 1002 may include interface circuitry. For instance, the communication interface 1002 may include a wired link interface such as an Ethernet cable, or a wireless link interface (Wi-Fi, Bluetooth, general wireless transmission, vehicular short-range communication technology, and other short-range wireless communication technologies, etc.). Optionally, the communication interface 1002 may also include a radio frequency transmitter, an antenna, etc. If the communication interface 1002 includes an antenna, the number of antennas can be one or more.

[0188] As one possible design, if the pairing management device 100 is a standalone device, the communication interface 1002 may include a receiver and a transmitter. The receiver and transmitter may be the same component or different components. When the receiver and transmitter are the same component, this component may be referred to as a transceiver.

[0189] As another possible design, if the pairing relationship management device 100 is a chip or circuit, the communication interface 1002 may include an input interface and an output interface. The input interface and the output interface may be the same interface or they may be different interfaces.

[0190] Alternatively, the functions of the communication interface 1002 can be implemented by a transceiver circuit or a dedicated transceiver chip.

[0191] The memory 1003 provides storage space, in which data such as the operating system and computer programs can be stored. The memory 1003 can be one or a combination of several of the following: random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM).

[0192] The functions and actions of each module or unit in the pairing relationship management device 100 listed above are merely illustrative examples.

[0193] Each functional unit in the pairing relationship management device 100 can be used to implement the aforementioned pairing relationship management method, such as the pairing relationship management method and its possible implementations shown in the embodiment of FIG2. For example, the pairing relationship management device 100 is used to execute the method executed by the first terminal, or the method executed by the first vehicle, or the method executed by the server in the pairing relationship management method shown in the embodiment of FIG2.

[0194] Optionally, the processor 1001 may be a processor specifically designed to execute the aforementioned methods (for ease of distinction, referred to as a dedicated processor), or a processor that executes the aforementioned methods by calling a computer program (for ease of distinction, referred to as a dedicated processor). Optionally, at least one processor may include both dedicated processors and general-purpose processors.

[0195] Optionally, if the pairing relationship management device 100 includes at least one memory 1003, and the processor 1001 implements the aforementioned pairing relationship management method by calling a computer program, the computer program can be stored in the memory 1003.

[0196] This application also provides a chip, which includes logic circuitry and a communication interface. The communication interface is used to receive or transmit signals; the logic circuitry is used to receive or transmit signals through the communication interface. The chip is used to implement the aforementioned pairing relationship management method, such as the pairing relationship management method and its possible implementations shown in the embodiment of Figure 2.

[0197] This application also provides a computer-readable storage medium storing instructions that, when executed on at least one processor (or pairing management device), implement the aforementioned pairing management method, such as the pairing management method and its possible implementations shown in the embodiment of FIG2.

[0198] This application also provides a computer program product, which includes computer instructions for implementing the aforementioned pairing relationship management method, such as the pairing relationship management method and its possible implementations shown in the embodiment of FIG2.

[0199] This application embodiment also provides a pairable device, which includes the aforementioned pairing relationship management device 90 and / or pairing relationship management device 100. The pairable device includes intelligent terminals or transportation vehicles such as vehicles, robots, drones, ships, and vessels. Alternatively, it may include smart home devices, smart exhibition hall devices, smart factory devices, smart city devices, entertainment devices, etc. The robot may be an automated guided vehicle (AGV), a walking conversational robot, a service robot, or other similar robots.

[0200] This application embodiment also provides a server, which includes the aforementioned pairing relationship management device 90 and / or pairing relationship management device 100.

[0201] This application embodiment also provides a terminal, which includes the aforementioned pairing relationship management device 90 and / or pairing relationship management device 100.

[0202] It should be noted that, in the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplarily" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0203] In this embodiment, the names of information and devices are exemplarily chosen for ease of understanding of the content of this solution. In specific implementations, their names may be designed differently. Furthermore, the names of the same thing may also be designed differently in different scenarios (e.g., different communication layers).

[0204] In the embodiments of this application, "at least one" refers to one or more items, and "more than one" refers to two or more items. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items.

[0205] For example, at least one of a, b, or c can be represented as: a, b, c, (a and b), (a and c), (b and c), or (a and b and c), where a, b, and c can be single or multiple. "AND / OR" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects have an "OR" relationship.

[0206] Furthermore, unless otherwise stated, the use of ordinal numbers such as "first," "second," etc., in the embodiments of this application is for distinguishing multiple objects and is not for limiting the order, sequence, priority, or importance of multiple objects. Similarly, terms like "first pairing relationship management device" and "second pairing relationship management device" are merely for convenience in describing pairing relationship management devices in different embodiments and do not indicate differences in their importance, structure, etc.

[0207] In the above embodiments, the term "when..." can be interpreted, depending on the context, as meaning "if...", "after...", "in response to determining...", or "in response to detecting...". The above descriptions are merely optional embodiments of this application and are not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the concept and principles of this application should be included within the protection scope of this application.

[0208] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

Claims

1. A method for managing pairing relationships, characterized in that, The method includes: Obtain the first pairing list currently stored in the Bluetooth chip. The first pairing list includes N first pairing parameters, where N is an integer and N≥0. The first pairing list is generated at a first moment. Each first pairing parameter includes the Bluetooth media storage control MAC address of a terminal that has completed digital key pairing with the vehicle before the first moment and the digital key identifier ID of the terminal. Obtain a second pairing list from the first storage unit. The second pairing list includes M second pairing parameters, where M is an integer and M > 0. The second pairing list is a backup of the pairing list stored by the Bluetooth chip at a second time point, which is earlier than the first time point. Each second pairing parameter includes the Bluetooth MAC address of a terminal that completed digital key pairing with the vehicle before the second time point and the digital key ID of the terminal. Determine that at least one second pairing parameter in the second pairing list does not exist in the first pairing list; Send a target pairing parameter to the server, the target pairing parameter including at least the digital key ID in the at least one second pairing parameter, to trigger the server to send a first prompt message to the target terminal corresponding to the digital key ID in the target pairing parameter, the first prompt message being used to indicate that the digital key ID in the vehicle corresponding to the target terminal is lost.

2. The method according to claim 1, characterized in that, The target pairing parameters also include the Bluetooth MAC address from the at least one second pairing parameter.

3. The method according to claim 1 or 2, characterized in that, The digital key ID of the terminal is associated with the terminal's communication number.

4. The method according to claim 3, characterized in that, The communication number of the terminal includes the cellular communication number defined in the SIM card installed on the terminal. Alternatively, the communication number of the terminal may include the terminal's instant messaging number.

5. The method according to any one of claims 1-4, characterized in that, The method is applied to microcontroller units (MCUs). The first storage unit is the MCU, or the first storage unit is a memory connected to the MCU.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: The pairing list currently stored in the Bluetooth chip is periodically backed up from the Bluetooth chip at a first time interval.

7. The method according to any one of claims 1-5, characterized in that, The method further includes: After the Bluetooth chip is paired with the first terminal, the pairing list currently stored by the Bluetooth chip is backed up from the Bluetooth chip. The pairing list includes a first pairing parameter, which includes the Bluetooth MAC address of the first terminal and the digital key ID of the first terminal.

8. A method for managing pairing relationships, characterized in that, include: Receive target pairing parameters from a first vehicle, the target pairing parameters including at least a digital key identifier ID; The communication number of the target terminal is determined based on the target pairing parameters and the table showing the relationship between the target pairing parameters and the terminal's communication number. A first prompt message is sent to the communication number of the target terminal, the first prompt message being used to indicate that the digital key ID corresponding to the target terminal in the first vehicle has been lost.

9. The method according to claim 8, characterized in that, The first notification message includes the Bluetooth MAC address of the first vehicle.

10. The method according to claim 9, characterized in that, The communication number of the terminal includes the cellular communication number defined in the SIM card installed on the terminal, or the communication number of the terminal includes the instant messaging number of the terminal.

11. A method for managing pairing relationships, characterized in that, The method is applied to a terminal, and the method includes: Pair with a digital key of a first vehicle to obtain target pairing information between the first vehicle and the first vehicle, the target pairing information including the Bluetooth MAC address of the first vehicle; Receive a first prompt message from the server, the first prompt message being used to indicate that the digital key identifier ID corresponding to the terminal in the first vehicle is lost; In response to the prompt message, delete the target pairing information with the first vehicle; or display a second prompt message indicating that the target pairing information with the first vehicle needs to be deleted.

12. The method according to claim 11, characterized in that, The target pairing information also includes the digital key ID corresponding to the first vehicle.

13. The method according to claim 12, characterized in that, The first notification message also includes the Bluetooth MAC address of the first vehicle. The first pairing information is stored in a Bluetooth pairing list, which includes multiple pairing information entries. Each pairing information entry includes the Bluetooth MAC address of a vehicle paired with the terminal and the digital key ID corresponding to the vehicle. The multiple pairing information entries include the target pairing information. The deletion of the target pairing information with the first vehicle includes: Based on the Bluetooth MAC address of the first vehicle, the target pairing information is searched in the Bluetooth pairing list. The target pairing information includes the Bluetooth MAC address of the first vehicle and the digital key ID corresponding to the first vehicle. Delete the target pairing information from the Bluetooth pairing list.

14. The method according to any one of claims 11-13, characterized in that, The first notification includes at least one of SMS, push notification, or in-app message from the target application. The target application is installed on the terminal.

15. A pairing relationship management device, characterized in that, The pairing relationship management device includes a processor and a memory. The memory provides storage space for storing computer instructions. The processor is configured to invoke computer instructions stored in the memory to execute the method as described in any one of claims 1-7, or to execute the method as described in any one of claims 8-10, or to execute the method as described in any one of claims 11-14.

16. A vehicle, characterized in that, The vehicle includes a Bluetooth chip, a first storage unit, and a pairing relationship management device. The Bluetooth chip is used for pairing with the terminal. The pairing relationship management device includes a processor and a memory, the memory being used to provide storage space for storing computer instructions. The processor is used to invoke computer instructions stored in the memory to execute the method as described in any one of claims 1-7.

17. A server, characterized in that, The server includes a pairing relationship management device, which includes a processor and a memory. The memory provides storage space for storing computer instructions. The processor is used to invoke computer instructions stored in the memory to implement the method as described in any one of claims 8-10.

18. A terminal, characterized in that, The terminal includes a pairing relationship management device, which includes a processor and a memory. The memory provides storage space for storing computer instructions. The processor is used to invoke computer instructions stored in the memory to cause the method described in any one of claims 11-14 to be executed.

19. A pairing relationship management system, characterized in that, The pairing relationship management system includes the vehicle as described in claim 16, the server as described in claim 17, and the terminal as described in claim 16.

20. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store computer instructions; When the instruction is executed by the processor, it causes the method as described in any one of claims 1-7 to be executed, or the method as described in any one of claims 8-10 to be executed, or the method as described in any one of claims 11-14 to be executed.

21. A computer program product, characterized in that, The computer program product includes computer language code or computer instructions; When the computer program product is executed by a processor, the method as described in any one of claims 1-7 is executed, or the method as described in any one of claims 8-10 is executed, or the method as described in any one of claims 11-14 is executed.

Images