Digital key sharing method and device, intelligent equipment and medium

Abstract

Disclosed is a digital key sharing method, comprising: requesting a server to create a digital key pre-sharing session, the request comprising location information, a verification code and a timestamp of an intelligent device; in response to the creation of the digital key pre-sharing session, information of matched receiver equipment returned by the server is received, and the matched receiver equipment is the receiver equipment which is detected by the server and inputs the same verification code within a preset range of the intelligent equipment within a preset time period; generating a digital key sharing session in response to the selection of the target recipient device; and in response to the generation of the digital key sharing session, requesting the server to issue the digital key of the vehicle to the target receiver device. The invention further relates to a digital key sharing device, intelligent equipment and a medium.

Description

Technical Field

[0001] This application relates to the field of connected vehicles, and more particularly to methods, apparatuses, smart devices, and computer-readable storage media for sharing digital keys. Background Technology

[0002] Today, with the rapid development of technology, digital keys for vehicles are widely used. They allow car owners to lock, unlock, or start their vehicles using portable devices such as smartphones and watches. Furthermore, car owners can remotely share their digital keys with friends in various ways (e.g., via SMS, QR code, etc.), or they can share them with nearby users using proximity sharing technology.

[0003] However, current proximity sharing methods (such as AirDrop) still require the recipient device (i.e., the device being shared with) to be known to the car owner's device, which is inconvenient when sharing with multiple unknown devices (e.g., devices not saved as contacts). Furthermore, current proximity sharing methods struggle with cross-platform key sharing; for example, iOS users cannot share digital keys with Android users via AirDrop.

[0004] Therefore, in order to support simultaneous proximity key sharing to multiple unknown devices, it is desirable to provide an improved solution for digital key sharing, thereby further enhancing the convenience and security of proximity key sharing and improving the user experience. Summary of the Invention

[0005] This summary is provided to introduce, in a simplified form, some concepts that will be further described in the following detailed description. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to help determine the scope of the claimed subject matter.

[0006] To address the above problems, according to a first aspect of the present invention, a digital key sharing method executed by a smart device is provided, the smart device having a digital key for a vehicle, the method comprising: requesting a server to create a digital key pre-sharing session, wherein the request includes location information, verification code, and timestamp of the smart device; in response to the creation of the digital key pre-sharing session, receiving information of a matched receiving device returned by the server, wherein the matched receiving device is a receiving device detected by the server that has entered the same verification code as the smart device within a predetermined time period and a preset range; in response to the selection of a target receiving device among the matched receiving devices, generating a digital key sharing session; and in response to the generation of the digital key sharing session, requesting the server to issue the digital key of the vehicle to the target receiving device.

[0007] In the technical solution of this invention, by having the potential receiving device (i.e. the device being shared with) and the vehicle owner's device simultaneously enter the same verification code, the verified receiving device can join the sharing session and receive the digital key shared by the vehicle owner's device. This enables key sharing without needing to know the relevant information of the receiving device, making close-range key sharing more convenient and secure, and further improving the user experience.

[0008] According to one embodiment of the present invention, the matched receiving device is obtained by the server through the following verification methods: receiving a search session request from the receiving device, wherein the search session request includes the location information, verification code, and timestamp of the receiving device; verifying whether the receiving device has entered the same verification code as the smart device within a predetermined time period and a preset range based on the session creation request of the smart device and the search session request of the receiving device; if the verification is successful, adding the receiving device to the digital key pre-sharing session to confirm that the receiving device is a matched receiving device.

[0009] According to a further embodiment of the present invention, the request to issue the digital key includes a sharing link for the digital key and a device identifier for the target recipient device, wherein the device identifier includes a device name or a friend's nickname.

[0010] According to a further embodiment of the present invention, in response to the generation of the digital key sharing session, requesting the server to issue the digital key of the vehicle to the target receiving device further includes: in response to the generation of the digital key sharing session, sending a sharing link of the digital key to the target receiving device via the server; and in response to the target receiving device accepting the sharing link, creating the digital key of the vehicle at the target receiving device.

[0011] According to a further embodiment of the present invention, the verification code is either user-defined or randomly generated by the smart device.

[0012] According to a further embodiment of the present invention, the digital key includes an NFC digital key, a BLE digital key, or a UWB digital key.

[0013] According to a second aspect of the present invention, a digital key sharing method executed by a server is provided, the method comprising: in response to receiving a request from a smart device communicatively connected to the server to create a digital key pre-sharing session, creating the digital key pre-sharing session, wherein the smart device has a digital key for a vehicle, the request including location information, a verification code, and a timestamp of the smart device; in response to receiving a search session request from a receiving device, verifying whether the receiving device has entered the same verification code as the smart device within a predetermined time period and within a predetermined range, wherein the search session request includes location information, a verification code, and a timestamp of the receiving device; if the verification is successful, returning information of the matched receiving device to the smart device; and in response to a key sharing request from the smart device to a target receiving device among the receiving devices, issuing the digital key of the vehicle to the target receiving device.

[0014] According to one embodiment of the present invention, the key sharing request includes a sharing link for the digital key and a device identifier for the target recipient device, wherein the device identifier includes a device name or a friend's nickname.

[0015] According to a further embodiment of the present invention, in response to a key sharing request from the smart device to a target receiving device in the receiving device, issuing the digital key of the vehicle to the target receiving device further includes: in response to the key sharing request, receiving a sharing link of the digital key from the smart device; and sending the sharing link of the digital key to the target receiving device so that the target receiving device can accept the digital key.

[0016] According to a further embodiment of the present invention, the verification code is either user-defined or randomly generated by the smart device.

[0017] According to a further embodiment of the present invention, the digital key includes an NFC digital key, a BLE digital key, or a UWB digital key.

[0018] According to a third aspect of the present invention, a digital key sharing device configured in a smart device is provided, the smart device having a vehicle digital key, the device comprising: a pre-sharing session creation module configured to request a server to create a digital key pre-sharing session, wherein the request includes location information, a verification code, and a timestamp of the smart device, and the smart device having a vehicle digital key; a target device selection module configured to, in response to the creation of the digital key pre-sharing session, receive information of a matched receiving device returned by the server, wherein the matched receiving device is a receiving device detected by the server that has entered the same verification code as the smart device within a preset range during a predetermined time period; and a digital key sharing module configured to: generate a digital key sharing session in response to the selection of a target receiving device among the matched receiving devices; and, in response to the generation of the digital key sharing session, request the server to issue the vehicle digital key to the target receiving device.

[0019] According to one embodiment of the present invention, the request to issue the digital key includes a sharing link for the digital key and a device identifier for the target recipient device, wherein the device identifier includes a device name or a friend's nickname.

[0020] According to a fourth aspect of the present invention, a smart device is provided, comprising: a communication unit communicatively coupled to a server; a processor; and a memory coupled to the processor, the memory storing processor-executable instructions that, when executed by the processor, cause the processor to perform the method as described in any of the preceding aspects.

[0021] According to a fifth aspect of the present invention, a non-transient processor-readable storage medium is provided, comprising processor-executable instructions that, when executed by the processor, cause the processor to perform the method as described in any of the preceding aspects.

[0022] To address the problems existing in the prior art, the present invention provides a solution for short-range digital key sharing. By having devices (including the owner's device and the device being shared) within a certain short distance simultaneously enter the same verification code, the device being shared joins the sharing session and receives the digital key shared by the owner's device. This makes short-range key sharing more convenient and secure, and further improves the user experience.

[0023] These and other features and advantages will become apparent from the following detailed description and with reference to the accompanying drawings. It should be understood that the foregoing general description and the following detailed description are illustrative only and do not limit the scope of the claims. Attached Figure Description

[0024] To gain a more detailed understanding of the manner in which the features of this disclosure are described above, reference can be made to the various embodiments for a more specific description of the above-briefly summarized aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and should not be considered as limiting its scope, as this description may allow for other equivalent and effective aspects.

[0025] Figure 1 A data flow diagram illustrating a method for proximity key sharing between a smart device, multiple receiving devices, and a server according to an embodiment of the present disclosure is shown.

[0026] Figure 2 This diagram illustrates a scenario of proximity key sharing between a smart device and multiple receiving devices according to an embodiment of the present disclosure.

[0027] Figure 3 A schematic flowchart illustrating a digital key sharing method performed by a smart device according to an embodiment of the present disclosure is shown.

[0028] Figure 4 A schematic flowchart illustrating a digital key sharing method performed by a server according to an embodiment of the present disclosure is shown.

[0029] Figure 5 A schematic architecture diagram of an apparatus for sharing digital keys according to an embodiment of the present disclosure is shown.

[0030] Figure 6 An example computing device architecture diagram is shown, illustrating an example computing device that can implement the various technologies described herein, according to an embodiment of the present disclosure. Detailed Implementation

[0031] The following detailed description is sufficient to enable any person skilled in the art to understand the technical content of one or more embodiments of this specification and to implement them accordingly. Furthermore, based on the specification, claims, and drawings disclosed herein, those skilled in the art can easily understand the objects and advantages associated with one or more embodiments of this specification. Throughout this specification, the term "vehicle" refers to any type of automobile, including but not limited to cars, vans, trucks, buses, etc. For simplicity, the invention is described in relation to "automobile." The terms "A or B" as used in this specification mean "A and B" and "A or B," and do not imply that A and B are exclusive unless otherwise stated.

[0032] As mentioned above, current vehicle digital key sharing typically requires knowledge of the recipient's device information (e.g., stored as a contact), and proximity key sharing is also difficult to implement across platforms.

[0033] To address this issue, embodiments of this specification envision a digital key sharing scheme that enables verified receiving devices to join a sharing session and receive the digital key shared by the vehicle owner's device by having one or more potential receiving devices in close proximity simultaneously enter the same verification code. This makes close-proximity key sharing more convenient and secure.

[0034] For example, see Figure 1 It illustrates an embodiment of the present disclosure in which a smart device (i.e., a vehicle owner device with a digital key) (labeled od), multiple receiving devices (in) Figure 1 The diagram shows a data flow diagram of a method 100 for proximity key sharing between two receiving devices, namely receiving device 1 (labeled d1) and receiving device 2 (labeled d2)), and a digital key server (labeled s).

[0035] Method 100 begins at step S1, where a smart device (e.g., a smartphone, watch, or other wearable smart device) requests a digital key server to create a pre-shared session, wherein the request includes the smart device’s GPS location information, current timestamp, and a one-time verification code (e.g., a numeric code) entered by the user in the smart device.

[0036] The aforementioned digital key can be, for example, an NFC digital key, a BLE digital key, or a UWB digital key.

[0037] In one implementation, a user can issue a digital key sharing request via an interactive interface in the relevant digital key sharing application on a smart device (e.g., which may be an extension of an existing vehicle application or a standalone application).

[0038] In addition, to ensure the security of digital key sharing, user identity can be verified before sharing. Specifically, this can be done by requesting user authorization, such as entering a device password, screen lock, wallet security code, fingerprint lock, or other security password, to determine whether the user is the owner of the device or vehicle, and allowing the user to perform the digital key sharing operation only if the verification is successful.

[0039] In step S2, a pre-shared session is created on the server side, and in step S3, an event notification is returned to the smart device that the session has been created.

[0040] Subsequently, in step S4, the receiving device (including d1 and d2) sends a search session request to the server. The request includes the GPS location information of the corresponding receiving device, the current timestamp, and the one-time verification code entered by the user in the corresponding receiving device.

[0041] In step S5, after the server receives the search session request from each receiving device, it can determine whether each receiving device has entered the same verification code within a preset range (e.g., 50m) of the smart device within a predetermined time period (e.g., the time of the request is no more than 10s) based on the received GPS location information, timestamps, and input verification codes of the smart device and each receiving device.

[0042] If the verification is successful (i.e., it is determined that the smart device and the receiving device enter the same verification code at almost the same close range), the corresponding receiving device can be added to the pre-sharing session.

[0043] In step S6, information about the receiving devices in the pre-sharing session (e.g., device name (which may be, for example, the mobile phone number corresponding to the device)) is sent to the smart device and each successfully verified receiving device.

[0044] In step S7, after receiving the successfully verified recipient device information at the smart device, the user can select the target recipient device (i.e., the device to be shared) (e.g., d1) through the device's UI interface, and generate a digital key sharing session for subsequent key sharing processes (which has been defined, for example, in the CCC digital key specification).

[0045] Subsequently, in step S8, the smart device sends a digital key sharing request to the server to request the server to distribute the vehicle's digital key to the selected target recipient device.

[0046] The aforementioned request may include, for example, a sharing link for the digital key (e.g., a URL link, which may include information such as carOEMUrl, sessionID, prKey, etc.) and information about the device being shared (e.g., phone number, device name, friend's nickname, etc.).

[0047] Subsequently, in step S9, the server may send a sharing link for the digital key to the target receiving device (d1 in this case), and in step S10, if the target receiving device accepts the sharing link, a digital key is created on the target receiving device.

[0048] Of course, after sharing is complete, the corresponding sharing information (such as information about the shared device) can be displayed on the in-vehicle system and the owner's device.

[0049] See further Figure 2 , Figure 2 Scenario 200 also illustrates the aforementioned key-sharing process. Figure 2In this scenario, User 1 initiates a sharing process and enters a one-time verification code (0000) through the interactive interface of a key-sharing application on their mobile device. Simultaneously, nearby Users 2 and 3 open their respective application interfaces and enter the same verification code (0000). User 1 then receives information about the device names of Users 2 and 3 (e.g., d1, d2) through the application's interactive interface. In response to User 1's selection of a target device (e.g., d1), a sharing link for the digital key can be sent to the corresponding target device. Device d1 then accepts the sharing link and generates a shared digital key (such as...). Figure 2 (NFC digital key card).

[0050] Therefore, digital key sharing can be achieved by having the potential recipient device and the vehicle owner device in close proximity simultaneously enter the same verification code, without the need for a cumbersome sharing process. This also avoids the aforementioned cross-platform and device-unknown issues, further improving the flexibility and convenience of digital key sharing.

[0051] Figure 3 A schematic flowchart illustrates a digital key sharing method 300 performed by a smart device according to an embodiment of the present disclosure, wherein the smart device is equipped with a digital key for a vehicle. The digital key may be an NFC, BLE, or UWB digital key.

[0052] Method 300 begins at step 302, which requests the server to create a digital key pre-sharing session, wherein the request includes the location information of the smart device, a verification code, and a current timestamp.

[0053] In one implementation, to ensure the security of key sharing, the verification code can be a one-time verification code, which can be user-defined or randomly generated by a smart device, and can be synchronized to the recipient before the sharing process.

[0054] In step 304, in response to the creation of the digital key pre-sharing session, information of the matched recipient device (e.g., device name, friend nickname, etc.) returned by the server is received, wherein the matched recipient device may be a recipient device detected by the server that has entered the same verification code as the smart device within a preset range during a predetermined time period.

[0055] Specifically, the server can receive search session requests from each receiving device. These requests may include, for example, the location information of the receiving device, a verification code, and a current timestamp. Then, based on the session creation request of the smart device and the search session request of the receiving device, it can verify whether the receiving device has entered the same verification code as the smart device within a preset range during a predetermined time period. If the verification is successful, the corresponding receiving device is added to the digital key pre-sharing session to confirm that the receiving device is a matched receiving device.

[0056] In step 306, in response to the selection of a target receiver device among the matched receiver devices, a digital key sharing session is generated.

[0057] Specifically, users can select the target device to share the key with based on the displayed matching device name or friend nickname on the smart device's interface, so that the target device can join the sharing session.

[0058] In step 308, in response to the generation of a digital key sharing session, the server is requested to issue the vehicle's digital key to the target receiving device.

[0059] Specifically, in response to the generation of a digital key sharing session, a sharing link (e.g., a URL link) for the digital key can be sent to the target device via the server, and in response to the target device accepting the sharing link, a digital key for the vehicle can be created on the target device, as referenced above. Figure 2 Further description.

[0060] and Figure 3 Correspondingly, in the method process, Figure 4 The diagram shows a schematic flowchart of a digital key sharing method 400 performed by a server according to an embodiment of the present disclosure.

[0061] Method 400 begins at step 402, in response to receiving a request from a smart device communicatively connected to the server to create a digital key pre-sharing session, wherein the smart device has a digital key for the vehicle, and the request includes the smart device’s location information, verification code and timestamp.

[0062] In step 404, in response to receiving a search session request from the receiving device, it is verified whether the receiving device has entered the same verification code as the smart device within a predetermined time period and within a preset range. The search session request includes the location information of the receiving device, the verification code, and a timestamp.

[0063] In step 406, if the verification is successful, the information of the matched receiving device is returned to the smart device.

[0064] In step 408, in response to the smart device's key sharing request to the target receiving device in the receiving device, the digital key of the vehicle is issued to the target receiving device.

[0065] In one implementation, the key sharing request may include, for example, a sharing link for the digital key and the device name or friend nickname of the target recipient's device.

[0066] Figure 5 This diagram illustrates a schematic architecture of a device 500 for sharing digital keys configured in a smart device (i.e., a vehicle owner's device with a vehicle digital key) according to an embodiment of the present disclosure.

[0067] like Figure 5 As shown, the device 500 may include at least a pre-shared session creation module 502, a target device selection module 504, and a digital key sharing module 506.

[0068] The pre-share session creation module 502 can request the server to create a digital key pre-share session, wherein the request may include the location information of the smart device, the verification code, and the current timestamp.

[0069] The target device selection module 504 can receive information (e.g., device name) of the matched recipient device returned by the server in response to the creation of the digital key pre-sharing session. The matched recipient device is a recipient device detected by the server that has entered the same verification code as the smart device within a preset range within a predetermined time period (verification is based on the location information of the smart device and each recipient device, the entered verification code, and the timestamp).

[0070] The digital key sharing module 506 can generate a digital key sharing session in response to the selection of a target receiving device in the matched receiving device, and request the server to issue the vehicle's digital key to the target receiving device.

[0071] In one implementation, the request to issue a digital key may include a sharing link for the digital key and a device identifier for the target recipient's device, wherein the device identifier may include the device name or a friend's nickname, etc.

[0072] Those skilled in the art will understand that the digital key sharing device of the present invention can be implemented in hardware or software, and the modules can be combined or merged in any suitable manner.

[0073] Figure 6 An example computing device architecture 600 is shown, illustrating an example computing device that can implement the various technologies described herein, according to one embodiment of the present disclosure. The computing device may be implemented as, for example, a smartphone, a smartwatch, or other smart wearable device, etc.

[0074] The components of computing device architecture 600 are shown to be in electrical communication with each other using bus 614. The example computing device architecture 600 includes a processor 604 and a bus 614 that couples various computing device components, including memory 602 (such as read-only memory (ROM) and random access memory (RAM)), to the processor 604.

[0075] The memory 602 may store computer-executable instructions that, when executed by the processor 604, cause the at least one processor to perform various functions described herein, including: requesting a server to create a digital key pre-sharing session, wherein the request includes location information, verification code, and timestamp of the smart device; in response to the creation of the digital key pre-sharing session, receiving information from the server regarding matched recipient devices, wherein the matched recipient devices are those detected by the server that have entered the same verification code as the smart device within a predetermined time period and a preset range; in response to the selection of a target recipient device among the matched recipient devices, generating a digital key sharing session; and in response to the generation of the digital key sharing session, requesting the server to issue the vehicle's digital key to the target recipient device.

[0076] Processor 604 may include a CPU, which in some examples may be a multi-core CPU. Instructions executed at the CPU may be loaded, for example, from program memory associated with the CPU or from memory 602. The one or more processors 604 may also include additional processing components tailored for specific functions, such as a graphics processing unit (GPU), a digital signal processor (DSP), a neural processing unit (NPU), or a multimedia processing unit. In some examples, the one or more processors may be based on the ARM or RISC-V instruction set.

[0077] The computing device architecture 600 may also include a cache 606 of high-speed memory that is directly connected to, adjacent to, or integrated into the processor 604. The computing device architecture 600 can copy data from the memory 602 to the cache 606 for fast access by the processor 604. In this way, the cache provides a performance boost, preventing latency for the processor 604 while waiting for data. These and other modules can control or be configured to control the processor 604 to perform various actions. Other computing device memories 602 may also be available. Memory 602 may include various different types of memory with different performance characteristics. The processor 604 may include any general-purpose processor and special-purpose processor (where software instructions are incorporated into the processor design). The processor 604 may be a self-contained system containing multiple cores or processors, buses, memory controllers, caches, etc. Multi-core processors may be symmetric or asymmetric.

[0078] To enable user interaction with computing device architecture 600, input device 608 can represent any number of input mechanisms, such as a microphone for voice, a touchscreen for gesture or graphical input, a keyboard, a mouse, etc. Output device 610 can also be one or more of a variety of output mechanisms known to those skilled in the art, such as a display, projector, television, or speaker device. In some instances, multimodal computing devices enable users to provide multiple types of input to communicate with computing device architecture 600. Communication interface 612 generally manages and controls user input and computing device output. There are no limitations on operation on any particular hardware arrangement, and therefore the underlying features here can be easily replaced to obtain improved hardware or firmware arrangements as they are developed.

[0079] Understandable. Figure 6 This is merely one example of a computing device, and other computing devices that include fewer, additional, or alternative aspects may also be consistent with this disclosure.

[0080] Furthermore, this application also discloses a computer-readable storage medium including computer-executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the methods of the embodiments described herein.

[0081] In addition, this application also discloses an apparatus including a processor and a memory storing computer-executable instructions that, when executed by the processor, cause the processor to perform the methods of the embodiments described herein.

[0082] The various illustrative blocks and modules described herein can be implemented or executed using a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternatives, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, or any other such configuration).

[0083] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored or transmitted as one or more instructions or code on a computer-readable medium. Other examples and implementations fall within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions can also be physically located in various locations, including being distributed such that different parts of the function are implemented at different physical locations.

[0084] The foregoing description includes examples of various aspects of the claimed subject matter. It is certainly impossible to describe every conceivable combination of components or methods for the purpose of depicting the claimed subject matter, but those skilled in the art will recognize that many further combinations and arrangements of the claimed subject matter are possible. Thus, the disclosed subject matter is intended to cover all such changes, modifications, and variations that fall within the spirit and scope of the appended claims.

Claims

1. A digital key sharing method executed by a smart device, said smart device having a digital key for a vehicle, the method comprising: A request is made to the server to create a digital key pre-sharing session, wherein the request includes the location information, verification code, and timestamp of the smart device; In response to the creation of the digital key pre-sharing session, information of the matched receiving device returned by the server is received, wherein the matched receiving device is a receiving device detected by the server that has entered the same verification code as the smart device within a preset range during a predetermined time period. In response to the selection of a target receiving device among the matched receiving devices, a digital key sharing session is generated; as well as In response to the generation of the digital key sharing session, the server is requested to issue the digital key of the vehicle to the target receiving device.

2. The method as described in claim 1, characterized in that, The matched receiving device is obtained by the server through the following verification method: Receive a search session request from a receiving device, wherein the search session request includes the location information, verification code, and timestamp of the receiving device; The system verifies whether the receiving device has entered the same verification code as the smart device within a predetermined time period and a preset range based on the session creation request of the smart device and the search session request of the receiving device. If the verification is successful, the receiving device is added to the digital key pre-sharing session to confirm that the receiving device is a matched receiving device.

3. The method as described in claim 1, characterized in that, The request to issue the digital key includes a sharing link for the digital key and a device identifier for the target recipient's device, which may include the device name or a friend's nickname.

4. The method as described in claim 3, characterized in that, In response to the generation of the digital key sharing session, requesting the server to issue the vehicle's digital key to the target receiving device further includes: In response to the generation of the digital key sharing session, a sharing link for the digital key is sent via the server to the target receiving device; and In response to the target receiving device accepting the shared link, a digital key for the vehicle is created on the target receiving device.

5. The method as described in claim 1, characterized in that, The verification code is either user-defined or randomly generated by the smart device.

6. The method as described in claim 1, characterized in that, The digital key includes an NFC digital key, a BLE digital key, or a UWB digital key.

7. A digital key sharing method executed by a server, the method comprising: In response to receiving a request from a smart device communicatively connected to the server to create a digital key pre-sharing session, the digital key pre-sharing session is created, wherein the smart device has a digital key for a vehicle, and the request includes the location information, verification code, and timestamp of the smart device; In response to receiving a search session request from a receiving device, it verifies whether the receiving device has entered the same verification code as the smart device within a predetermined time period and within a preset range. The search session request includes the location information of the receiving device, the verification code, and a timestamp. If the verification is successful, the information of the matched receiving device is returned to the smart device; as well as In response to a key sharing request from the smart device to the target receiving device in the receiving device, the digital key of the vehicle is issued to the target receiving device.

8. The method as described in claim 7, characterized in that, The key sharing request includes a sharing link for the digital key and a device identifier for the target recipient's device, the device identifier including the device name or a friend's nickname.

9. The method as described in claim 8, characterized in that, In response to the smart device's key sharing request to the target receiving device in the receiving device, issuing the vehicle's digital key to the target receiving device further includes: In response to the key sharing request, a sharing link for the digital key is received from the smart device; and Send a sharing link for the digital key to the target receiving device so that the target receiving device can accept the digital key.

10. The method as described in claim 7, characterized in that, The verification code is either user-defined or randomly generated by the smart device.

11. The method as described in claim 7, characterized in that, The digital key includes an NFC digital key, a BLE digital key, or a UWB digital key.

12. A digital key sharing device configured in a smart device, the smart device having a digital key for a vehicle, the device comprising: A pre-shared session creation module is configured to request the creation of a digital key pre-shared session from the server, wherein the request includes the location information, verification code, and timestamp of the smart device. A target device selection module, configured to receive information about matched recipient devices returned by the server in response to the creation of the digital key pre-sharing session, wherein the matched recipient devices are those detected by the server that have entered the same verification code as the smart device within a preset range over a predetermined time period; and Digital key sharing module, the digital key sharing module is configured to: In response to the selection of a target receiving device among the matched receiving devices, a digital key sharing session is generated; as well as In response to the generation of the digital key sharing session, the server is requested to issue the digital key of the vehicle to the target receiving device.

13. The apparatus as claimed in claim 12, characterized in that, The request to issue the digital key includes a sharing link for the digital key and a device identifier for the target recipient's device, which may include the device name or a friend's nickname.

14. A smart device, comprising: A communication unit that is coupled to communicate with the server; processor; as well as A memory coupled to the processor stores processor-executable instructions that, when executed by the processor, cause the processor to perform the method as described in any one of claims 1-6.

15. A non-transient processor-readable storage medium comprising processor-executable instructions that, when executed by the processor, cause the processor to perform the method as described in any one of claims 1-6.

Images