Method and apparatus for sharing digital car key, and storage medium

Abstract

The present disclosure provides a method and device for sharing a digital vehicle key, and a storage medium. The method comprises: sending a uniform resource locator (URL) address for sharing the digital vehicle key to a specified server; and the specified server is configured to forward the URL address to a parsing component of a to-be-shared end device. The present disclosure can forward the URL address for sharing the digital vehicle key to the parsing component of the to-be-shared end device through the server, avoid other devices except the to-be-shared end device from obtaining the URL address, and improve the security of sharing the digital vehicle key.

Description

Technical Field

[0001] This disclosure relates to the field of digital car keys, and more particularly to a method, apparatus, and storage medium for sharing digital car keys. Background Technology

[0002] Currently, the CCC (Car Connectivity Consortium) standard defines the sharing process for digital car keys. The Owner device and the Friend device (the device to be shared with) can establish an end-to-end connection. The specific process includes: the Owner device generating a URL (Uniform Resource Locator) for sharing the digital car key. This URL may include the session ID for the connection to be established and information about the vehicle to be shared. The Friend device then uses this URL to determine the digital car key shared by the Owner device.

[0003] However, in the above process, the Owner device cannot determine whether the URL address has been sent to the intended Friend device, and other devices can also obtain the URL address to get the digital car key, making the process of sharing the digital car key less secure. Summary of the Invention

[0004] In view of this, this application discloses a method, apparatus, and storage medium for sharing digital car keys.

[0005] According to a first aspect of the present disclosure, a method for sharing a digital car key is provided, the method being applied to a vehicle owner's terminal device, the method comprising:

[0006] The Uniform Resource Locator (URL) address used to share the digital car key is sent to a designated server; wherein the designated server is used to forward the URL address to the parsing component of the device to be shared.

[0007] Optionally, the method further includes:

[0008] Determine the second device brand corresponding to the device to be shared and the device identifier of the device to be shared;

[0009] At least the device identifier of the device to be shared is sent to the designated server.

[0010] Optionally, the designated server is a third-party server;

[0011] Sending the Uniform Resource Locator (URL) address used to share the digital car key to the designated server includes:

[0012] The URL address is sent to the third-party server through the first server corresponding to the first device brand; wherein, the first device brand is the device brand corresponding to the vehicle owner's terminal device;

[0013] Sending at least the device identifier of the device to be shared to the designated server includes:

[0014] The second device brand and the device identifier of the device to be shared are sent to the third-party server through the first server.

[0015] Optionally, if the first device brand corresponding to the vehicle owner's terminal device is the same as the second device brand, the designated server is the first server corresponding to the first device brand;

[0016] Sending at least the device identifier of the end device to be shared to the designated server includes any one of the following:

[0017] Send the device identifier of the device to be shared to the first server;

[0018] Send the second device brand and the device identifier of the device to be shared to the first server.

[0019] Optionally, before sending the Uniform Resource Locator (URL) address used to share the digital car key to the designated server, the method further includes:

[0020] Send a specified message to the device to be shared; wherein the specified message does not include the URL address, and the specified message includes at least the first token information of the vehicle owner device, the specified message is used by the device to be shared to initiate a registration request to the specified server, and the specified server determines the binding relationship of the digital car key sharing process between the vehicle owner device and the device to be shared based at least on the registration request.

[0021] Optionally, the method further includes:

[0022] Receive the second token information of the terminal device to be shared, which is bound to the vehicle owner's terminal device, sent by the designated server;

[0023] When the URL address is sent to the designated server, target token information is sent to the designated server so that the designated server forwards the URL address to the parsing component of the device to be shared based on the target token information; wherein the target token information is at least one of the second token information.

[0024] Optionally, the parsing component is a digital key frame.

[0025] According to a second aspect of the present disclosure, a method for sharing a digital car key is provided, the method being applied to a designated server, the method comprising:

[0026] Receive the Uniform Resource Locator (URL) address sent by the vehicle owner's device for sharing the digital car key;

[0027] The URL address is forwarded to the parsing component of the device to be shared.

[0028] Optionally, the designated server is a third-party server;

[0029] The Uniform Resource Locator (URL) address sent by the receiving vehicle owner's device for sharing the digital car key includes:

[0030] The system receives the URL address sent by the vehicle owner's terminal device through a first server corresponding to a first device brand; wherein, the first device brand is the device brand corresponding to the vehicle owner's terminal device.

[0031] Optionally, the method further includes:

[0032] The vehicle owner's terminal device receives the second device brand corresponding to the terminal device to be shared and the device identifier of the terminal device to be shared, sent by the first server through the first server.

[0033] Based on the second device brand, determine the second server corresponding to the second device brand;

[0034] The parsing component that forwards the URL address to the device to be shared includes:

[0035] The device identifier of the device to be shared and the URL address are sent to the second server. After the second server determines the device to be shared based on the device identifier, it sends the URL address to the parsing component of the device to be shared.

[0036] Optionally, the designated server is a first server corresponding to a first device brand; wherein, the first device brand is the device brand corresponding to the vehicle owner's terminal device;

[0037] The method further includes:

[0038] Receive the second device brand and device identifier of the device to be shared from the vehicle owner's terminal device;

[0039] If the first device brand and the second device brand are the same, after determining the device to be shared based on the device identifier of the device to be shared, the step of forwarding the URL address to the parsing component of the device to be shared is executed.

[0040] Optionally, the designated server is a first server corresponding to a first device brand; wherein, the first device brand is the device brand corresponding to the vehicle owner's terminal device;

[0041] The method further includes:

[0042] Receive the device identifier of the device to be shared from the vehicle owner's terminal device when the first device brand and the second device brand corresponding to the device to be shared are the same;

[0043] After determining the device to be shared based on the device identifier of the device to be shared, the step of forwarding the URL address to the parsing component of the device to be shared is executed.

[0044] Optionally, before receiving the Uniform Resource Locator (URL) address sent by the vehicle owner's device for sharing the digital car key, the method further includes:

[0045] Receive registration information sent by the device to be shared; wherein the registration message includes the first token information of the vehicle owner device;

[0046] Based on the registration information, register the second token information corresponding to the device to be shared on the designated server, and register the first token information of the vehicle owner's device.

[0047] Based on the registration information, the first token information, and the second token information, the binding relationship of the digital car key sharing process between the car owner's terminal device and the terminal device to be shared is determined;

[0048] The parsing component that forwards the URL address to the device to be shared includes:

[0049] Based on the binding relationship, the URL address is forwarded to the parsing component of the device to be shared.

[0050] Optionally, the method further includes:

[0051] Send the second token information of the sharing terminal device that has the binding relationship with the vehicle owner terminal device to the vehicle owner terminal device;

[0052] Receive target token information sent by the vehicle owner's terminal device; wherein the target token information is at least one of the second token information;

[0053] The parsing component that forwards the URL address to the device to be shared includes:

[0054] Based on the target token information, the URL address is forwarded to the parsing component of the device to be shared.

[0055] Optionally, the parsing component is a digital key frame.

[0056] According to a third aspect of the present disclosure, a method for sharing a digital car key is provided, the method being applied to a device to be shared, the method comprising:

[0057] The parsing component receives the Uniform Resource Locator (URL) address of the digital car key forwarded by the designated server for sharing the vehicle owner's device; based on the URL address, it generates the digital car key shared by the vehicle owner's device.

[0058] Optionally, the designated server is a third-party server;

[0059] The step of receiving the Uniform Resource Locator (URL) address of the digital car key forwarded by the designated server through the parsing component for sharing the vehicle owner's device includes:

[0060] The parsing component receives the URL address sent by the second server corresponding to the second device brand; wherein, the second device brand is the device brand corresponding to the device to be shared, and the URL address is forwarded by the designated server to the second server.

[0061] Optionally, the designated server is a first server corresponding to a first device brand; wherein, the first device brand is the device brand corresponding to the vehicle owner's terminal device.

[0062] Optionally, before receiving the Uniform Resource Locator (URL) address of the digital car key for sharing the vehicle owner's device forwarded by the specified server through the parsing component, the method further includes:

[0063] Receive a specified message sent by the vehicle owner's terminal device; wherein the specified message does not include the URL address, and the specified message includes the first token information of the vehicle owner's terminal device;

[0064] Based on the specified message, registration information is sent to the specified server; wherein the registration message includes the first token information, and the registration information is used to register the second token information of the device to be shared on the specified server, as well as to register the first token information.

[0065] Optionally,

[0066] The step of generating the digital car key shared by the vehicle owner's device based on the URL address includes:

[0067] The parsing component generates the digital car key shared by the car owner's device based on the URL address.

[0068] Optionally, after generating the digital car key shared by the vehicle owner's device, the method further includes:

[0069] Output a prompt message; wherein the prompt message is used to indicate that the digital car key shared by the vehicle owner's terminal device has been generated.

[0070] Optionally, the parsing component is a digital key frame.

[0071] According to a fourth aspect of the present disclosure, an apparatus for sharing a digital car key is provided, the apparatus being applied to a vehicle owner's device, the apparatus comprising:

[0072] The first sending module is configured to send a Uniform Resource Locator (URL) address for sharing the digital car key to a designated server; wherein the designated server is used to forward the URL address to the parsing component of the device to be shared.

[0073] According to a fifth aspect of the present disclosure, an apparatus for sharing a digital car key is provided, the apparatus being applied to a designated server, the apparatus comprising:

[0074] The first receiving module is configured to receive a Uniform Resource Locator (URL) address sent by the vehicle owner's device for sharing the digital car key; the second sending module is configured to forward the URL address to the parsing component of the device to be shared.

[0075] According to a sixth aspect of the present disclosure, an apparatus for sharing a digital car key is provided, the apparatus being applied to a device to be shared, the apparatus comprising:

[0076] The second receiving module is configured to receive, through a parsing component, a Uniform Resource Locator (URL) address forwarded by a designated server for sharing the digital car key on the vehicle owner's device; the generating module is configured to generate the digital car key shared by the vehicle owner's device based on the URL address.

[0077] According to a seventh aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the steps of the method for sharing a digital car key as described in any of the above-described methods for the owner's device.

[0078] According to an eighth aspect of the present disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the method for sharing a digital car key as described in any of the above-described methods for a designated server side.

[0079] According to a ninth aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the steps of the method for sharing a digital car key as described in any of the above-described methods for sharing a terminal device.

[0080] According to a tenth aspect of the present disclosure, an apparatus for sharing a digital car key is provided, comprising:

[0081] processor;

[0082] Memory used to store processor-executable instructions;

[0083] The processor is configured to execute the executable instructions to implement the steps of the method for sharing a digital car key as described in any of the above-described methods on the vehicle owner's device side.

[0084] According to an eleventh aspect of the present disclosure, an apparatus for sharing a digital car key is provided, comprising:

[0085] processor;

[0086] Memory used to store processor-executable instructions;

[0087] The processor is configured to execute the executable instructions to implement the steps of the method for sharing a digital car key as described in any of the above-mentioned specified server-side methods.

[0088] According to a twelfth aspect of the present disclosure, an apparatus for sharing a digital car key is provided, comprising:

[0089] processor;

[0090] Memory used to store processor-executable instructions;

[0091] The processor is configured to execute the executable instructions to implement the steps of the method for sharing a digital car key as described in any of the above-described methods for sharing a digital car key on the device to be shared.

[0092] The technical solutions provided by the embodiments of this disclosure may include the following beneficial effects:

[0093] In this disclosure, the URL address used for sharing a digital car key can be forwarded by the server to the parsing component of the device to be shared, thereby preventing other devices besides the device to be shared from obtaining the URL address and improving the security of sharing digital car keys.

[0094] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0095] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0096] Figure 1 This is a flowchart illustrating a method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0097] Figure 2 This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0098] Figure 3 This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0099] Figure 4 This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0100] Figure 5A This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0101] Figure 5B This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0102] Figure 6 This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0103] Figure 7 This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0104] Figure 8 This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0105] Figure 9 This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0106] Figure 10A This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0107] Figure 10B This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0108] Figure 11 This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0109] Figure 12 This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0110] Figure 13 This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0111] Figure 14 This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0112] Figure 15 This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0113] Figure 16 This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0114] Figure 17 This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0115] Figure 18 This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0116] Figure 19 This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0117] Figure 20 This is a flowchart illustrating another method for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0118] Figure 21 This is a block diagram illustrating an apparatus for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0119] Figure 22 This is a block diagram illustrating another device for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0120] Figure 23This is a block diagram illustrating another device for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0121] Figure 24 This is a schematic diagram of a device for sharing a digital car key according to an exemplary embodiment of the present disclosure;

[0122] Figure 25 This is a schematic diagram of another device for sharing a digital car key, as illustrated in an exemplary embodiment of this disclosure;

[0123] Figure 26 This is a schematic diagram of another device for sharing digital car keys according to an exemplary embodiment of the present disclosure. Detailed Implementation

[0124] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the invention as detailed in the appended claims.

[0125] In related technologies, for example, device #A (corresponding to brand #1), device #B (corresponding to brand #2), and device #C (corresponding to brand #3) all support the digital car key corresponding to car model a. Brand #1, brand #2, and brand #3 can be the same or different; this disclosure does not impose any limitations on this.

[0126] In this scenario, device #A, acting as the Owner device, wants to share the digital car key for car model a with device #B, which acts as the Friend device. Device #A can then send an SMS or WeChat message to device #B in an end-to-end manner. This message or message can include a URL address for sharing the digital car key. This URL address is visible to both device #A and the receiving device. If device #C receives this URL address from device #A (the Owner device) and meets the certificate chain requirements, device #C can create the digital car key based on the received URL address (which is also visible to device #C). Clearly, this digital car key sharing process has poor security.

[0127] To address the aforementioned technical issues, this disclosure provides the following method for sharing digital car keys, which prevents other devices besides the device to be shared from obtaining the URL address used for sharing the digital car key, thereby improving the security of digital car key sharing.

[0128] The following section will introduce the method for sharing digital car keys provided in this publication, starting with the car owner's device.

[0129] Reference Figure 1 As shown, Figure 1 This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key. This embodiment is described from the perspective of the vehicle owner's device, where the vehicle owner's device is a terminal device used by the vehicle owner, including but not limited to mobile phones, laptops, desktop computers, iPads, etc. Figure 1 As shown, the method for sharing a digital car key may include the following steps:

[0130] In step 101, the Uniform Resource Locator (URL) address used to share the digital car key is sent to the designated server.

[0131] In this embodiment of the disclosure, the device to be shared refers to a peer device that expects to obtain a digital car key from the vehicle owner's device, and the designated server is a parsing component used to forward the URL address to the device to be shared.

[0132] In one possible implementation, the parsing component could be the DK framework (Digital Keyframework). The DK framework is a built-in component in the backend of the device to be shared, used to generate or parse URL addresses.

[0133] In one possible implementation, the vehicle owner's device can generate the URL address in the background using its own parsing component, such as DKframework, and send the URL address to a designated server. The designated server can then forward the URL address to the parsing component of the device to be shared, such as the DK framework of the device to be shared.

[0134] In another possible implementation, the device to be shared receives the URL address forwarded by the designated server directly through its own digital framework, and the URL address will not be displayed on the foreground of the device to be shared.

[0135] In another possible implementation, the URL address is not visible to the foreground of the vehicle owner's device; that is, the URL address will not be displayed on the foreground of the vehicle owner's device.

[0136] In the above embodiments, the URL address used to share the digital car key can be forwarded by the server to the parsing component of the device to be shared. Compared with the method of the car owner device directly sharing and presenting the URL address to the device to be shared, the URL address disclosed in this invention is not visible to either the car owner device or the device to be shared, thus preventing other devices besides the device to be shared from obtaining the URL address and improving the security of sharing the digital car key.

[0137] In some alternative embodiments, refer to Figure 2 As shown, Figure 2 This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key. The method can be applied to a vehicle owner's terminal device, which is a terminal device used by the vehicle owner. The method includes the following steps:

[0138] In step 201, the second device brand corresponding to the device to be shared and the device identifier of the device to be shared are determined.

[0139] Among them, the device to be shared refers to the device that expects to obtain the digital car key from the vehicle owner's device. The device identifier of the device to be shared includes, but is not limited to, the phone number of the device to be shared or other information that can identify the device to be shared.

[0140] In one possible implementation, the vehicle owner's device can output a prompt message, prompting the user of the vehicle owner's device to input the brand of the second device and the device identifier of the device to be shared. The vehicle owner's device then obtains the brand of the second device and the device identifier of the device to be shared input by the user.

[0141] In step 202, the URL address for sharing the digital car key is sent to a third-party server through the first server corresponding to the first device brand.

[0142] In this embodiment of the disclosure, the first device brand is the device brand corresponding to the vehicle owner's terminal device, and the designated server can be a third-party server, that is, a trusted third-party server other than the first server and the second server corresponding to the second device brand. The second device brand is the device brand corresponding to the terminal device to be shared, and the third-party server includes, but is not limited to, parking lot servers, public servers, etc.

[0143] In one possible implementation, the vehicle owner's device can generate the URL address in the background using the device's parsing component, such as the DK framework, thereby making the URL address invisible to the foreground of the vehicle owner's device.

[0144] Furthermore, the vehicle owner's device identifies its own primary device brand and sends the URL to the primary server corresponding to that brand. The primary server then forwards the URL to a third-party server. This third-party server then forwards the URL to the parsing component of the device to be shared; this parsing component can be a digital key framework.

[0145] In step 203, the second device brand and the device identifier of the device to be shared are sent to the third-party server through the first server.

[0146] In this embodiment, the vehicle owner's device can send the second device brand and the device identifier of the device to be shared to the first server, which then forwards the information to a third-party server. Subsequently, the third-party server can determine the second server corresponding to the second device brand, and then send the URL address and the device identifier of the device to be shared to the second server. The second server, after determining the device to be shared based on the device identifier, sends the URL address to the parsing component of the device to be shared, such as the DK framework of the device to be shared, thereby achieving the purpose of making the URL address invisible to the foreground of the sharing device.

[0147] It should be noted that steps 202 and 203 above can be executed simultaneously. That is, the vehicle owner's device can send the URL address, the brand of the second device, and the device identifier of the device to be shared to the designated server through the first server. In one possible implementation, the URL address can include the brand of the second device and the device identifier of the device to be shared.

[0148] Alternatively, step 202 can be performed first, followed by step 203, or step 203 can be performed first, followed by step 202. This disclosure does not limit the order of execution of the steps. In one possible implementation, the second device brand and the device identifier of the device to be shared can be sent separately to a third-party server using information other than the URL address.

[0149] It should also be noted that when the designated server is a third-party server, the brand of the first device and the brand of the second device can be the same or different, and this disclosure does not impose any restrictions on this.

[0150] In the above embodiments, a third-party server can be used to transmit the URL address for sharing digital car keys between two devices of different brands or the same brand. Compared with the method of the car owner device directly sharing and presenting the URL address to the device to be shared, the URL address disclosed in this invention is invisible to both the car owner device and the device to be shared, thus preventing other devices besides the device to be shared from obtaining the URL address and achieving the goal of improving the security of sharing digital car keys.

[0151] In some alternative embodiments, refer to Figure 3 As shown, Figure 3 This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key. The method can be applied to a vehicle owner's terminal device, which is a terminal device used by the vehicle owner. The method includes the following steps:

[0152] In step 301, the second device brand corresponding to the device to be shared and the device identifier of the device to be shared are determined.

[0153] Among them, the device to be shared refers to the device that expects to obtain the digital car key from the vehicle owner's device. The device identifier of the device to be shared includes, but is not limited to, the phone number of the device to be shared or other information that can identify the device to be shared.

[0154] In one possible implementation, the vehicle owner's device can output a prompt message asking the user to input the brand of the second device and the device identifier of the device to be shared. The vehicle owner's device then obtains the user-inputted brand of the second device and the device identifier of the device to be shared.

[0155] In step 302, if the first device brand corresponding to the vehicle owner's device is the same as the second device brand, the URL address used to share the digital car key is sent to the first server corresponding to the first device brand.

[0156] In step 303, the device identifier of the device to be shared is sent to the first server.

[0157] In this embodiment of the disclosure, if the first server does not receive the second device brand, it can search for the device to be shared among its own multiple devices based on the device identifier of the device to be shared, and then send the URL address directly to the parsing component of the device to be shared. The parsing component can be a digital key framework.

[0158] It should be noted that steps 302 and 303 above can be executed simultaneously. That is, the vehicle owner's device can send the URL address and the device identifier of the device to be shared to the designated server through the first server. In one possible implementation, the URL address includes the device identifier of the device to be shared.

[0159] Alternatively, step 302 can be performed first, followed by step 303, or step 303 can be performed first, followed by step 302. This disclosure does not limit the order of execution of the steps.

[0160] In another possible implementation, the URL address does not include the device identifier of the device to be shared, which is sent to the first server by the vehicle owner's device through separate information.

[0161] In the above embodiments, the first server corresponding to the vehicle owner device can transmit the URL address for sharing digital car keys between two devices of the same brand. Compared with the method of the vehicle owner device directly sharing and presenting the URL address to the device to be shared, the URL address disclosed in this invention is invisible to both the vehicle owner device and the device to be shared, thus preventing other devices besides the device to be shared from obtaining the URL address and achieving the purpose of improving the security of sharing digital car keys.

[0162] In some alternative embodiments, refer to Figure 4 As shown, Figure 4 This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key. The method can be applied to a vehicle owner's terminal device, which is a terminal device used by the vehicle owner. The method includes the following steps:

[0163] In step 401, the second device brand corresponding to the device to be shared and the device identifier of the device to be shared are determined.

[0164] Among them, the device to be shared refers to the device that expects to obtain the digital car key from the vehicle owner's device. The device identifier of the device to be shared includes, but is not limited to, the phone number of the device to be shared or other information that can identify the device to be shared.

[0165] In one possible implementation, the vehicle owner's device can output a prompt message asking the user to input the brand of the second device and the device identifier of the device to be shared. The vehicle owner's device then obtains the user-inputted brand of the second device and the device identifier of the device to be shared.

[0166] In step 402, if the first device brand corresponding to the vehicle owner's device is the same as the second device brand, the URL address used to share the digital car key is sent to the first server corresponding to the first device brand.

[0167] In step 403, the second device brand and the device identifier of the device to be shared are sent to the first server.

[0168] In this embodiment of the disclosure, the first server receives the second device brand and can first determine whether the device to be shared belongs to its own brand based on the second device brand. If the second device brand is the same as the first device brand, it can search for the device to be shared among its own multiple devices based on the device identifier of the device to be shared, and then send the URL address directly to the parsing component of the device to be shared. The parsing component can be a digital key frame.

[0169] Of course, if the first server determines that the brand of the second device is different from that of the first device, it can send the URL address, the brand of the second device, and the device identifier of the device to be shared to a third-party server. The third-party server will then determine the second server corresponding to the brand of the second device, send the URL address and the device identifier of the device to be shared to the second server, and the second server will then determine the device to be shared and send the URL address to the parsing component of the device to be shared. This parsing component can be a digital key frame.

[0170] It should be noted that steps 402 and 403 above can be executed simultaneously. That is, the vehicle owner's device can send the URL address, the brand of the second device, and the device identifier of the device to be shared to the designated server through the first server. In one possible implementation, the URL address can include the brand of the second device and the device identifier of the device to be shared.

[0171] Alternatively, step 402 can be performed first, followed by step 403, or step 403 can be performed first, followed by step 402. This disclosure does not limit the order of execution of the steps.

[0172] In one possible implementation, the second device brand and the device identifier of the device to be shared can be sent separately to a third-party server using information other than the URL address.

[0173] In the above embodiments, the first server corresponding to the vehicle owner device can also transmit the URL address for sharing digital car keys between two devices of the same brand. Compared with the method of the vehicle owner device directly sharing and presenting the URL address to the device to be shared, the URL address disclosed in this invention is not visible to the vehicle owner device and the device to be shared, thus preventing other devices besides the device to be shared from obtaining the URL address and achieving the purpose of improving the security of sharing digital car keys.

[0174] In some alternative embodiments, refer to Figure 5A As shown, Figure 5A This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key. The method can be applied to a vehicle owner's terminal device, which is a terminal device used by the vehicle owner. The method includes the following steps:

[0175] In step 501, a specified message is sent to the device to be shared.

[0176] In this embodiment of the disclosure, the device to be shared refers to a friend device that wishes to obtain a digital car key from the vehicle owner device. The specified message does not include the URL address, and the specified message includes at least the first token information of the vehicle owner device. The specified message is used by the device to be shared to initiate a registration request to the specified server, and the specified server determines the binding relationship between the vehicle owner device and the device to be shared in the digital car key sharing process based at least on the registration request. This binding relationship means that once the specified server receives the URL address for sharing the digital car key from the vehicle owner device, the specified server will forward the URL address to another device with a binding relationship, i.e., send it to the device to be shared.

[0177] In one possible implementation, the specified message can be a specified SMS message or a specified WeChat message, etc.

[0178] In step 502, the Uniform Resource Locator (URL) address used to share the digital car key is sent to the designated server.

[0179] In this embodiment of the disclosure, the designated server can be a trusted third-party server or a public server. Based on the aforementioned binding relationship, after receiving a URL address from the vehicle owner's device, the designated server directly forwards the URL address to the parsing component of the device to be shared. This parsing component can be a digital key framework.

[0180] In the above embodiments, the URL address used to share the digital car key can be forwarded to the device to be shared by the server. Compared with the method of the car owner device directly sharing and presenting the URL address to the device to be shared, the URL address disclosed in this invention is not visible to the car owner device and the device to be shared, thus preventing other devices besides the device to be shared from obtaining the URL address and improving the security of sharing the digital car key.

[0181] In some alternative embodiments, refer to Figure 5B As shown, Figure 5B This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key. The method can be applied to a vehicle owner's terminal device, which is a terminal device used by the vehicle owner. The method includes the following steps:

[0182] In step 501, a specified message is sent to the device to be shared.

[0183] In this embodiment of the disclosure, the device to be shared refers to a friend device that wishes to obtain a digital car key from the vehicle owner device. The specified message does not include the URL address, and the specified message includes at least the first token information of the vehicle owner device. The specified message is used by the device to be shared to initiate a registration request to the specified server, and the specified server determines the binding relationship between the vehicle owner device and the device to be shared in the digital car key sharing process based at least on the registration request. This binding relationship means that once the specified server receives the URL address for sharing the digital car key from the vehicle owner device, the specified server will forward the URL address to another device with a binding relationship, i.e., send it to the device to be shared.

[0184] In one possible implementation, the specified message can be a specified SMS message or a specified WeChat message, etc.

[0185] In step 502, the Uniform Resource Locator (URL) address used to share the digital car key is sent to the designated server.

[0186] In this embodiment of the disclosure, the designated server can be a trusted third-party server or a public server.

[0187] In step 503, the second token information of the sharing terminal device, which has the binding relationship with the vehicle owner terminal device, is received from the designated server.

[0188] In one possible implementation, if the designated server determines that a vehicle owner's device and a device to be shared are bound together, it may not send a second token to the vehicle owner's device. After receiving the URL address for sharing the digital car key from the vehicle owner's device, the designated server can directly forward the URL address to the parsing component of the device to be shared, based on the binding relationship. The parsing component can be a digital key framework. Therefore, steps 503 to 504 of this disclosure are optional.

[0189] In another possible implementation, if the designated server determines that a vehicle owner's device is bound to a device to be shared, or that a vehicle owner's device is bound to multiple devices to be shared, then the designated server can send the second token information of the devices to be shared that are bound to the vehicle owner's device to the vehicle owner's device, which can then receive it.

[0190] In another possible implementation, if the designated server determines that a vehicle owner's device is bound to multiple devices to be shared, the designated server can send the second token information of the devices to be shared that are bound to the vehicle owner's device to the vehicle owner's device, which can then receive it.

[0191] In step 504, the Uniform Resource Locator (URL) address used to share the digital car key is sent to the designated server.

[0192] In step 505, if the URL address is sent to the designated server, the target token information is sent to the designated server.

[0193] The target token information is at least one of the second token information.

[0194] In one possible implementation, the number of times the vehicle owner's device receives the second token information sent by the designated server is one, and the vehicle owner's device can send the second token information as the target token information to the designated server.

[0195] In another possible implementation, the vehicle owner device receives multiple second token messages sent by a designated server. The vehicle owner device can determine at least one of the multiple second token messages as the target token message and send the target token message to the designated server.

[0196] In this embodiment, steps 504 and 505 can be executed simultaneously, meaning the vehicle owner's device can send the URL address and target token information together to the designated server. In one possible implementation, the target token information can be included in the URL address.

[0197] Alternatively, step 504 can be executed first, followed by step 505, or step 505 can be executed first, followed by step 504. This disclosure does not limit the order of execution of the steps. In one possible implementation, the target token information can be sent separately to the designated server using information other than the URL address.

[0198] The designated server can forward the URL address to the parsing component of the device to be shared, based on the target token information. The parsing component can be a digital key framework.

[0199] In the above embodiments, the URL address used to share the digital car key can be forwarded to the device to be shared by the server. Compared with the method of the car owner device directly sharing and presenting the URL address to the device to be shared, the URL address disclosed in this invention is not visible to the car owner device and the device to be shared, thus preventing other devices besides the device to be shared from obtaining the URL address and improving the security of sharing the digital car key.

[0200] The following section will introduce the method for sharing digital car keys provided in this publication from the perspective of a designated server.

[0201] Reference Figure 6 As shown, Figure 6 This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key, which can be applied to a specified server, such as... Figure 6 As shown, the method for sharing a digital car key may include the following steps:

[0202] In step 601, the vehicle owner's device sends a Uniform Resource Locator (URL) address for sharing the digital car key.

[0203] In this embodiment of the disclosure, the vehicle owner's device is a terminal device used by the vehicle owner. This URL address is not visible to the foreground of the vehicle owner's device.

[0204] In step 602, the URL address is forwarded to the parsing component of the device to be shared.

[0205] In this embodiment of the disclosure, the device to be shared refers to a peer device that expects to obtain a digital car key from the vehicle owner's device. The parsing components of the device to be shared include, but are not limited to, the digital key frame of the device to be shared. The designated server forwards the URL address to the digital key frame of the device to be analyzed; therefore, this URL address is also invisible to the device to be shared.

[0206] In the above embodiments, the URL address used to share the digital car key can be forwarded by the server to the digital key framework of the device to be shared. Compared with the method of the car owner device directly sharing and presenting the URL address to the device to be shared, the URL address disclosed in this invention is not visible to either the car owner device or the device to be shared, thus preventing other devices besides the device to be shared from obtaining the URL address and improving the security of sharing the digital car key.

[0207] In some alternative embodiments, refer to Figure 7 As shown, Figure 7 This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key. The method can be applied to a designated server, which can be a third-party server. The method includes the following steps:

[0208] In step 701, the vehicle owner's device receives a URL address for sharing the digital car key sent by the first server corresponding to the first device brand.

[0209] The first device brand is the device brand corresponding to the vehicle owner's terminal device. The vehicle owner's terminal device is the terminal device used by the vehicle owner.

[0210] In one possible implementation, the first server could be the manufacturer's server corresponding to the vehicle owner's device.

[0211] In step 702, the second device brand corresponding to the device to be shared and the device identifier of the device to be shared are received by the vehicle owner device through the first server.

[0212] Among them, the device to be shared refers to the device that expects to obtain the digital car key from the car owner's device.

[0213] It should be noted that steps 701 and 702 above can be executed simultaneously, meaning the third server can receive the URL address, the second device brand, and the device identifier of the device to be shared from the vehicle owner's device via the first server. In one possible implementation, the URL address includes the second device brand and the device identifier of the device to be shared.

[0214] Alternatively, step 701 can be performed first, followed by step 702, or step 702 can be performed first, followed by step 701. This disclosure does not limit the order of execution of the steps. In one possible implementation, the second device brand and the device identifier of the device to be shared can be sent separately to the third server using information other than the URL.

[0215] In step 703, a second server corresponding to the second device brand is determined based on the second device brand.

[0216] In one possible implementation, the second server could be the vendor's server corresponding to the device to be shared with.

[0217] In step 704, the device identifier of the device to be shared and the URL address are sent to the second server. After the second server determines the device to be shared based on the device identifier, it sends the URL address to the parsing component of the device to be shared.

[0218] In one possible implementation, the URL address includes the brand of the second device and the device identifier of the device to be shared, in which case the third-party server can directly send the URL address to the second server.

[0219] In another possible implementation, if the URL does not include the brand of the second device and the device identifier of the device to be shared, the third-party server sends the URL to the second server and sends the device identifier of the device to be shared to the second server separately.

[0220] In this embodiment of the disclosure, the parsing component of the device to be shared can be the digital key frame of the device to be shared.

[0221] In the above embodiments, a trusted third-party server can receive the URL address, the second device brand, and the device identifier of the device to be shared from the vehicle owner's device via the first server. The third server then determines the second server corresponding to the second device brand and forwards the URL address and the device identifier of the device to be shared to the second server. The second server can then send the URL address to the parsing component of the device to be shared, which is determined based on the device identifier of the device to be shared. This achieves the purpose of forwarding the URL address used to share the digital car key to the desired device on the vehicle owner's device via the server, thereby improving the security of sharing the digital car key.

[0222] In some alternative embodiments, refer to Figure 8 As shown, Figure 8 This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key. The method can be applied to a designated server, which can be a first server corresponding to a first device brand. The method includes the following steps:

[0223] In step 801, the URL address for sharing the digital car key sent by the vehicle owner's device is received.

[0224] The first device brand is the device brand corresponding to the vehicle owner's terminal device. The vehicle owner's terminal device is the terminal device used by the vehicle owner.

[0225] In step 802, the device identifier of the device to be shared is received by the vehicle owner device when the first device brand and the second device brand are the same.

[0226] Among them, the device to be shared refers to the device that expects to obtain the digital car key from the vehicle owner's device. The device identifier of the device to be shared includes, but is not limited to, the phone number of the device to be shared.

[0227] It should be noted that steps 801 and 802 above can be executed simultaneously, meaning the first server can receive the URL address sent by the vehicle owner's device and the device identifier of the device to be shared. In one possible implementation, the URL address includes the device identifier of the device to be shared.

[0228] Alternatively, step 801 can be performed first, followed by step 802, or step 802 can be performed first, followed by step 801. This disclosure does not limit the order of execution of the steps. In one possible implementation, the device identifier of the device to be shared can be sent separately to the first server using information other than the URL.

[0229] In step 803, the device to be shared is determined based on the device identifier of the device to be shared.

[0230] In step 804, the URL address is sent to the parsing component of the device to be shared.

[0231] The URL address may include the brand of the second device and the device identifier of the device to be shared, or it may not include the brand of the second device and the device identifier of the device to be shared. The parsing component of the device to be shared can be the digital key frame of the device to be shared.

[0232] In the above embodiments, the purpose of forwarding the URL address used to share the digital car key to the parsing component of the vehicle owner's device is achieved, thereby improving the security of sharing the digital car key.

[0233] In some alternative embodiments, refer to Figure 9 As shown, Figure 9 This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key. The method can be applied to a designated server, which can be a first server corresponding to a first device brand. The method includes the following steps:

[0234] In step 901, the URL address for sharing the digital car key sent by the vehicle owner's device is received.

[0235] The first device brand is the device brand corresponding to the vehicle owner's terminal device. The vehicle owner's terminal device is the terminal device used by the vehicle owner.

[0236] In step 902, the second device brand corresponding to the device to be shared and the device identifier of the device to be shared are received from the vehicle owner's terminal device.

[0237] Among them, the device to be shared refers to the device that expects to obtain the digital car key from the vehicle owner's device. The device identifier of the device to be shared includes, but is not limited to, the phone number of the device to be shared.

[0238] If the first device brand and the second device brand are the same, perform the following steps 903 to 904; if the first device brand and the second device brand are different, perform the following steps 905 to 906.

[0239] In step 903, the device to be shared is determined based on the device identifier of the device to be shared.

[0240] In step 904, the URL address is sent to the parsing component of the device to be shared.

[0241] The URL address may or may not include the second device brand and the device identifier of the device to be shared; this disclosure does not limit this. The parsing component of the device to be shared can be the digital key frame of the device to be shared.

[0242] In step 905, the second server corresponding to the second device brand is determined.

[0243] In step 906, the URL address and the device identifier of the device to be shared are sent to the second server. After the second server determines the device to be shared based on the device identifier, it sends the URL address to the parsing component of the device to be shared.

[0244] In one possible implementation, the URL address includes the second device brand and the device identifier of the device to be shared.

[0245] In another possible implementation, the URL address does not include the second device brand and the device identifier of the device to be shared. In this case, the device identifier of the device to be shared is sent to the second server by the third-party server as separate information.

[0246] Among them, the parsing component of the device to be shared can be the digital key frame of the device to be shared.

[0247] In the above embodiments, after receiving the second device brand, the first server corresponding to the first device brand can first determine whether the second device brand is the same as the first device brand, and then execute the corresponding subsequent steps. This also achieves the purpose of forwarding the URL address used to share the digital car key to the parsing component of the car owner's terminal device, which is expected to be shared, thereby improving the security of sharing the digital car key.

[0248] In some alternative embodiments, refer to Figure 10A As shown, Figure 10A This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key. The method can be applied to a designated server and includes the following steps:

[0249] In step 1001, the registration information sent by the device to be shared is received.

[0250] The registration message includes the first token information of the vehicle owner's terminal device. The vehicle owner's terminal device is the terminal device used by the vehicle owner, and the sharing terminal device refers to the peer device that expects to obtain a digital car key from the vehicle owner's terminal device.

[0251] In step 1002, based on the registration information, the second token information corresponding to the device to be shared is registered on the designated server, and the first token information of the vehicle owner device is registered.

[0252] In this embodiment of the disclosure, the designated server can register a handle corresponding to the device to be shared, i.e., the second token information, and a handle corresponding to the vehicle owner's device, i.e., the first token information, based on the registration information.

[0253] In step 1003, based on the registration information, the first token information, and the second token information, the binding relationship of the digital car key sharing process between the vehicle owner terminal device and the terminal device to be shared is determined.

[0254] In this embodiment of the disclosure, the binding relationship means that once the designated server receives the URL address sent from the vehicle owner's device for sharing the digital car key, the designated server will forward the URL address to another device with a binding relationship, that is, send it to the device to be shared.

[0255] In step 1004, the vehicle owner's device sends a Uniform Resource Locator (URL) address for sharing the digital car key.

[0256] In step 1005, based on the binding relationship, the URL address is forwarded to the parsing component of the device to be shared.

[0257] Among them, the parsing component of the device to be shared can be the digital key frame of the device to be shared.

[0258] In the above embodiments, the designated server can determine the binding relationship between the vehicle owner's device and the device to be shared in the digital car key sharing process based on the registration information from the device to be shared. Upon receiving the URL address from the vehicle owner's device, the server forwards the URL address to the parsing component of the device to be shared, based on this binding relationship. This achieves the goal of forwarding the URL address used for sharing the digital car key to the parsing component of the intended device on the vehicle owner's device via the server, thereby improving the security of digital car key sharing.

[0259] In some alternative embodiments, refer to Figure 10B As shown, Figure 10B This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key. The method can be applied to a designated server and includes the following steps:

[0260] In step 1001, the registration information sent by the device to be shared is received.

[0261] The registration message includes the first token information of the vehicle owner's terminal device. The vehicle owner's terminal device is the terminal device used by the vehicle owner, and the sharing terminal device refers to the peer device that expects to obtain a digital car key from the vehicle owner's terminal device.

[0262] In step 1002, based on the registration information, the second token information corresponding to the device to be shared is registered on the designated server, and the first token information of the vehicle owner device is registered.

[0263] In this embodiment of the disclosure, the designated server can register a handle corresponding to the device to be shared, i.e., the second token information, and a handle corresponding to the vehicle owner's device, i.e., the first token information, based on the registration information.

[0264] In step 1003, based on the registration information, the first token information, and the second token information, the binding relationship of the digital car key sharing process between the vehicle owner terminal device and the terminal device to be shared is determined.

[0265] In this embodiment of the disclosure, the binding relationship means that once the designated server receives the URL address sent from the vehicle owner's device for sharing the digital car key, the designated server will forward the URL address to another device with a binding relationship, that is, send it to the device to be shared.

[0266] In step 1004', the second token information of the sharing terminal device that has the binding relationship with the vehicle owner terminal device is sent to the vehicle owner terminal device.

[0267] In one possible implementation, the designated server may not send a second token to the vehicle owner's device if the binding relationship exists between the vehicle owner's device and the device to be shared.

[0268] In another possible implementation, the server sends a second token to the vehicle owner device when the vehicle owner device has the binding relationship with a device to be shared, or when the vehicle owner device has the binding relationship with multiple devices to be shared.

[0269] In another possible implementation, the designated server sends a second token to the vehicle owner's device when the binding relationship exists between a vehicle owner's device and multiple devices to be shared.

[0270] In step 1005', the vehicle owner's device sends a Uniform Resource Locator (URL) address for sharing the digital car key.

[0271] In step 1006', the target token information sent by the vehicle owner terminal device is received.

[0272] The target token information is at least one of the second token information.

[0273] In step 1007', based on the target token information, the URL address is forwarded to the device to be shared.

[0274] In this embodiment of the disclosure, the designated server can determine the device to be shared based on the binding relationship and target token information, and then forward the URL address to the parsing component of the device to be shared. The parsing component of the device to be shared can be the digital key frame of the device to be shared.

[0275] In the above embodiments, the designated server can determine the binding relationship between the vehicle owner's device and the device to be shared in the digital car key sharing process based on the registration information from the device to be shared. Upon receiving the URL address from the vehicle owner's device, the server forwards the URL address to the parsing component of the device to be shared, based on the binding relationship and the target token information sent by the vehicle owner's device. This achieves the goal of forwarding the URL address used for sharing the digital car key to the parsing component of the intended device on the vehicle owner's device via the server, thereby improving the security of digital car key sharing.

[0276] Next, we will introduce the method for sharing digital car keys provided in this publication from the perspective of the device to be shared.

[0277] Reference Figure 11 As shown, Figure 11This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key. This embodiment is described from the perspective of the device to be shared, where the device to be shared refers to a peer device that desires to obtain a digital car key from the car owner's device, including but not limited to mobile phones, laptops, desktop computers, iPads, etc. Figure 11 As shown, the method for sharing a digital car key may include the following steps:

[0278] In step 1101, the parsing component receives the Uniform Resource Locator (URL) address of the digital car key, which is forwarded by the designated server and used to share the vehicle owner's device.

[0279] In this embodiment of the disclosure, the vehicle owner's device is a terminal device used by the vehicle owner. The parsing component can be a digital key frame.

[0280] In step 1102, the digital car key shared by the vehicle owner's device is generated based on the URL address.

[0281] In this embodiment of the disclosure, the digital car key can be generated by the DK framework of the device to be shared based on the URL address.

[0282] In the above embodiments, the URL address can be avoided by other devices besides the device to be shared, thus improving the security of digital car key sharing.

[0283] In some alternative embodiments, refer to Figure 12 As shown, Figure 12 This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key. The method can be applied to a device to which the key is to be shared, where the device is a peer device that desires to obtain a digital car key from a vehicle owner's device. The method includes the following steps:

[0284] In step 1201, the URL address sent by the second server corresponding to the second device brand is received through the parsing component.

[0285] The second device brand refers to the device brand corresponding to the device to be shared. The URL address specifies the server, such as a third-party server forwarding the URL to the second server; the parsing component can be a digital key framework.

[0286] In step 1202, the digital car key shared by the vehicle owner's device is generated based on the URL address.

[0287] In this embodiment of the disclosure, the digital car key can be generated by the DK framework of the device to be shared based on the URL address.

[0288] In the above embodiments, the URL address can be avoided by other devices besides the device to be shared, thus improving the security of digital car key sharing.

[0289] In some alternative embodiments, refer to Figure 13 As shown, Figure 13 This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key. The method can be applied to a device to which the key is to be shared, where the device is a peer device that desires to obtain a digital car key from a vehicle owner's device. The method includes the following steps:

[0290] In step 1301, the parsing component receives the URL address for sharing the digital car key sent by the first server corresponding to the first device brand.

[0291] Here, the first device brand is the device brand corresponding to the vehicle owner's terminal device. If the first device brand is the same as the second device brand corresponding to the terminal device to be shared, the terminal device to be shared can directly receive the URL address from the first server. The vehicle owner's terminal device is the terminal device used by the vehicle owner, and the parsing component can be a digital key frame.

[0292] In step 1302, the digital car key shared by the vehicle owner's device is generated based on the URL address.

[0293] In this embodiment of the disclosure, the digital car key can be generated by the DK framework of the device to be shared based on the URL address.

[0294] In the above embodiments, the URL address can be avoided by other devices besides the device to be shared, thus improving the security of digital car key sharing.

[0295] In some alternative embodiments, refer to Figure 14 As shown, Figure 14 This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key. The method can be applied to a device to which the key is to be shared, where the device is a peer device that desires to obtain a digital car key from a vehicle owner's device. The method includes the following steps:

[0296] In step 1401, a specified message is received from the vehicle owner's device.

[0297] The specified message does not include the URL address, but includes the first token information of the vehicle owner's terminal device. The vehicle owner's terminal device is the terminal device used by the vehicle owner. The specified message can be a specified SMS message or a specified WeChat message, etc.

[0298] In step 1402, registration information is sent to the designated server based on the specified message.

[0299] In this embodiment of the disclosure, once the device to be shared receives a specified message, it automatically sends the registration information to a specified server. The registration message includes the first token information, which is used to register the second token information of the device to be shared on the specified server, as well as to register the first token information.

[0300] The designated server can determine the binding relationship between the vehicle owner's terminal device and the terminal device to be shared in the digital car key sharing process based on the registration information, the first token information and the second token information.

[0301] In step 1403, the parsing component receives the URL address for sharing the digital car key sent by the designated server based on the binding relationship between the vehicle owner's device and the device to be shared in the digital car key sharing process.

[0302] The parsing component can be a digital key frame.

[0303] In step 1404, the digital car key shared by the vehicle owner's device is generated based on the URL address.

[0304] In this embodiment of the disclosure, the digital car key can be generated by the DK framework of the device to be shared based on the URL address.

[0305] In the above embodiments, it is also possible to prevent other devices besides the device to be shared from obtaining the URL address, thereby improving the security of digital car key sharing.

[0306] In some alternative embodiments, refer to Figure 15 As shown, Figure 15 This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key. The method can be applied to a device to which the key is to be shared, where the device is a peer device that desires to obtain a digital car key from a vehicle owner's device. The method includes the following steps:

[0307] In step 1501, the parsing component receives the Uniform Resource Locator (URL) address of the digital car key, which is forwarded by the designated server and used to share the vehicle owner's device.

[0308] The vehicle owner's device is the terminal device used by the vehicle owner. This means that even after the sharing device receives the URL address, it will not display the URL address on the foreground, such as on the device screen. The parsing component can be a digital key framework.

[0309] In step 1502, the parsing component generates the digital car key shared by the vehicle owner's device based on the URL address.

[0310] In the above embodiments, after the device to be shared receives the URL address, it directly submits it to the parsing component for processing through the background, and no longer provides the user with an interface containing the URL, thereby improving the security of sharing digital car keys.

[0311] In some alternative embodiments, refer to Figure 16 As shown, Figure 16 This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key. The method can be applied to a device to which the key is to be shared, where the device is a peer device that desires to obtain a digital car key from a vehicle owner's device. The method includes the following steps:

[0312] In step 1601, the parsing component receives the Uniform Resource Locator (URL) address of the digital car key, which is forwarded by the designated server and used to share the vehicle owner's device.

[0313] The vehicle owner's device is the terminal device used by the vehicle owner. This means that even after the sharing device receives the URL address, it will not display the URL address on the foreground, such as on the device screen. The parsing component can be a digital key framework.

[0314] In step 1602, the digital car key shared by the vehicle owner's device is generated based on the URL address.

[0315] In this embodiment of the disclosure, the digital car key can be generated by the DK framework of the device to be shared based on the URL address.

[0316] In step 1603, a prompt message is output.

[0317] The notification message indicates that the digital car key shared by the vehicle owner's device has been generated.

[0318] In the above embodiments, after a digital car key is generated on the device to be shared, a prompt message can be displayed to notify the user of the device to be shared that the digital car key shared by the car owner's device has been generated. This improves the security of sharing digital car keys, is simple to implement, and has high usability.

[0319] In some alternative embodiments, if the device identifier of the device to be shared corresponds to multiple devices, for example, the same phone number corresponds to a mobile phone and a personal computer assistant (iPad), then the user of the device to be shared can determine the digital car key that is valid on one or more devices.

[0320] The above process is further illustrated with examples below.

[0321] Reference Figure 17 As shown, Figure 17 This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key, the method comprising the following steps:

[0322] In step 1701, the vehicle owner device determines the second device brand corresponding to the device to be shared and the device identifier of the device to be shared.

[0323] The vehicle owner's device is the terminal device used by the vehicle owner, and the sharing device refers to a peer device that wants to obtain a digital car key from the vehicle owner's device. The device identifier of the sharing device can be its phone number.

[0324] In step 1702, the vehicle owner device sends the Uniform Resource Locator (URL) address used to share the digital car key, the second device brand, and the device identifier of the device to be shared to the first server corresponding to the first device brand.

[0325] The first device brand is the device brand corresponding to the vehicle owner's terminal device. This URL address is not visible on the foreground of the vehicle owner's terminal device. In one possible implementation, the URL address includes the second device brand and the device identifier of the terminal device to be shared.

[0326] In another possible implementation, the URL address may not include the second device brand and the device identifier of the device to be shared, which are sent to the first server as separate information.

[0327] In step 1703, the first server sends the URL address, the second device brand, and the device identifier of the device to be shared to a third-party server.

[0328] Alternatively, the third-party server can be a parking lot server.

[0329] In one possible implementation, the URL address could include the second device brand and the device identifier of the device to be shared.

[0330] In another possible implementation, the URL address may not include the second device brand and the device identifier of the device to be shared, which are sent to the third server as separate information.

[0331] In step 1704, the third-party server determines the second server corresponding to the second device brand based on the second device brand.

[0332] In step 1705, the third-party server sends the URL address and the device identifier of the device to be shared to the second server.

[0333] In one possible implementation, the URL address includes the brand of the second device and the device identifier of the device to be shared. Once the third-party server identifies the brand server corresponding to the device to be shared, i.e., the second server, it can forward the URL address to the second server.

[0334] In another possible implementation, the URL address does not include the brand of the second device and the device identifier of the device to be shared. In this case, after the third-party server determines the brand server corresponding to the device to be shared, i.e., the second server, it can send the URL address and the device identifier of the device to be shared to the second server respectively.

[0335] In the above embodiments, the second server may be the manufacturer's server of the device to be shared.

[0336] In step 1706, after the second server determines the device to be shared based on the device identifier of the device to be shared, it sends the URL address to the parsing component of the device to be shared.

[0337] In this embodiment, the second server pushes the URL address to the parsing component of the device to be shared. Prior to this, the URL address is not visible to either the vehicle owner's device or the device to be shared. This parsing component can be a digital key framework.

[0338] In step 1707, the parsing component of the device to be shared generates the digital car key shared by the vehicle owner's device based on the URL address.

[0339] In step 1708, the device to be shared outputs a prompt message.

[0340] The notification message is used to indicate that the digital car key shared by the vehicle owner's device has been generated.

[0341] In the above embodiments, the URL address used to share digital car keys can be avoided from being shared to unauthorized devices, thus improving the security of sharing digital car keys.

[0342] In some alternative embodiments, refer to Figure 18 As shown, Figure 18 This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key, the method comprising the following steps:

[0343] In step 1801, the vehicle owner device determines the second device brand corresponding to the device to be shared and the device identifier of the device to be shared.

[0344] The vehicle owner's device is the terminal device used by the vehicle owner, and the sharing device refers to a peer device that wants to obtain a digital car key from the vehicle owner's device. The device identifier of the sharing device can be its phone number.

[0345] In step 1802, if the first device brand corresponding to the vehicle owner device is the same as the second device brand, the vehicle owner device sends the URL address for sharing the digital car key and the device identifier of the device to be shared to the first server corresponding to the first device brand.

[0346] The URL address is not visible to the front end of the vehicle owner's device.

[0347] In one possible implementation, the URL address may include the device identifier of the device to be shared.

[0348] In another possible implementation, the URL address does not include the device identifier of the device to be shared. The identifier information of the device to be shared can be sent to the first server by the vehicle owner's device through separate information.

[0349] In step 1803, after the first server determines the device to be shared based on the device identifier of the device to be shared, it sends the URL address to the parsing component of the device to be shared.

[0350] The parsing component can be a digital key frame.

[0351] In step 1804, the parsing component of the device to be shared generates the digital car key shared by the vehicle owner's device based on the URL address.

[0352] In step 1805, the device to be shared outputs a prompt message.

[0353] The notification message is used to indicate that the digital car key shared by the vehicle owner's device has been generated.

[0354] In the above embodiments, the URL address used to share digital car keys can be avoided from being shared to unauthorized devices, thus improving the security of sharing digital car keys.

[0355] In some alternative embodiments, refer to Figure 19 As shown, Figure 19 This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key, the method comprising the following steps:

[0356] In step 1901, the vehicle owner device determines the second device brand corresponding to the device to be shared and the device identifier of the device to be shared.

[0357] The vehicle owner's device is the terminal device used by the vehicle owner, and the sharing device refers to a peer device that wants to obtain a digital car key from the vehicle owner's device. The device identifier of the sharing device can be its phone number.

[0358] In step 1902, the vehicle owner device sends the URL address used to share the digital car key, the second device brand, and the device identifier of the device to be shared to the first server corresponding to the first device brand.

[0359] The first device brand is the device brand corresponding to the vehicle owner's terminal device. The URL address is not visible to the front end of the vehicle owner's terminal device.

[0360] In one possible implementation, the URL address may include a second device brand and the device identifier of the device to be shared.

[0361] In another possible implementation, the URL address does not include the brand of the second device and the device identifier of the device to be shared. The brand of the second device and the identifier of the device to be shared can be sent to the first server separately.

[0362] In step 1903, if the first device brand and the second device brand are the same, the first server determines the sharing terminal device based on the device identifier of the sharing terminal device, and then sends the URL address to the parsing component of the sharing terminal device.

[0363] The parsing component can be a digital key frame.

[0364] In step 1904, the parsing component of the device to be shared generates the digital car key shared by the vehicle owner's device based on the URL address.

[0365] In step 1905, the device to be shared outputs a prompt message.

[0366] The notification message is used to indicate that the digital car key shared by the vehicle owner's device has been generated.

[0367] In step 1906, if the first device brand and the second device brand are different, the first server sends the URL address, the second device brand, and the device identifier of the device to be shared to a third-party server.

[0368] Alternatively, the third-party server can be a parking lot server.

[0369] In one possible implementation, the URL address could include the second device brand and the device identifier of the device to be shared.

[0370] In another possible implementation, the URL address may not include the second device brand and the device identifier of the device to be shared, which are sent to the third server as separate information.

[0371] In step 1907, the third-party server determines the second server corresponding to the second device brand based on the second device brand.

[0372] In step 1908, the third-party server sends the URL address and the device identifier of the device to be shared to the second server.

[0373] In one possible implementation, the URL address includes the brand of the second device and the device identifier of the device to be shared. Once the third-party server identifies the brand server corresponding to the device to be shared, i.e., the second server, it can forward the URL address to the second server.

[0374] In another possible implementation, the URL address does not include the brand of the second device and the device identifier of the device to be shared. In this case, after the third-party server determines the brand server corresponding to the device to be shared, i.e., the second server, it can send the URL address and the device identifier of the device to be shared to the second server.

[0375] In the above embodiments, the second server may be the manufacturer's server of the device to be shared.

[0376] In step 1909, after the second server determines the device to be shared based on the device identifier of the device to be shared, it sends the URL address to the parsing component of the device to be shared.

[0377] In this embodiment, the second server pushes the URL address to the digital key frame of the device to be shared. Prior to this, the URL address is not visible to either the vehicle owner's device or the device to be shared.

[0378] In step 1910, the parsing component of the device to be shared generates the digital car key shared by the vehicle owner's device based on the URL address.

[0379] In step 1911, the device to be shared outputs a prompt message.

[0380] The notification message is used to indicate that the digital car key shared by the vehicle owner's device has been generated.

[0381] In the above embodiments, after receiving the second device brand, the first server can first determine whether the second device brand is the same as the first device brand of the car owner's device. This avoids forwarding the URL address through a third-party server when the two brands are the same, thereby improving the security of sharing digital car keys and saving signaling resources.

[0382] Reference Figure 20 As shown, Figure 20 This is a flowchart illustrating an exemplary embodiment of a method for sharing a digital car key, the method comprising the following steps:

[0383] In step 2001, the vehicle owner device sends a specified message to the device to be shared.

[0384] The specified message does not include the URL address, and it includes at least the first token information of the vehicle owner's device. The vehicle owner's device is the terminal device used by the vehicle owner, and the sharing device is a peer device that wants to obtain a digital car key from the vehicle owner's device. The specified message can be a specified WeChat account or a specified SMS message.

[0385] In step 2002, the device to be shared sends registration information to the designated server based on the designated message.

[0386] The registration message includes the first token information, and the specified server can be a public server.

[0387] In step 2003, the designated server registers the second token information corresponding to the device to be shared and the first token information of the vehicle owner device on the designated server based on the registration information.

[0388] In this embodiment of the disclosure, based on a specified message initiated by the vehicle owner's device, the purpose of registering the vehicle owner's device and the device to be shared on a specified server can be achieved.

[0389] In step 2004, the designated server determines the binding relationship of the digital car key sharing process between the vehicle owner's terminal device and the terminal device to be shared based on the registration information, the first token information, and the second token information.

[0390] In step 2005, the vehicle owner's device sends the URL address used to share the digital car key to the designated server.

[0391] In step 2006, the designated server forwards the URL address to the parsing component of the device to be shared, based on the binding relationship.

[0392] The parsing component can be a digital key frame.

[0393] In step 2007, the parsing component of the device to be shared generates the digital car key shared by the vehicle owner's device based on the URL address.

[0394] In step 2008, the device to be shared outputs a prompt message.

[0395] The notification message is used to indicate that the digital car key shared by the vehicle owner's device has been generated.

[0396] In the above embodiments, when a vehicle owner device and multiple devices to be shared are bound together, the designated server can send the second token information of the multiple devices to be shared to the vehicle owner device. The vehicle owner device can then determine the target token information when sending the URL address and send the target token information to the designated server. Based on the binding relationship and the target token information, the designated server can determine the devices to be shared and forward the URL address to the parsing component of the devices to be shared.

[0397] In the above embodiments, the URL address used to share digital car keys can be avoided from being shared to unauthorized devices, thus improving the security of sharing digital car keys.

[0398] Corresponding to the aforementioned embodiments of the application function implementation method, this disclosure also provides embodiments of the application function implementation apparatus.

[0399] Reference Figure 21 , Figure 21 This is a block diagram illustrating a device for sharing a digital car key according to an exemplary embodiment. The device is applied to a vehicle owner's device and includes:

[0400] The first sending module 2101 is configured to send a Uniform Resource Locator (URL) address for sharing the digital car key to a designated server; wherein the designated server is used to forward the URL address to the parsing component of the device to be shared.

[0401] The specific implementation method is the same as described above. Figure 1 The implementation of the illustrated embodiments is similar and will not be described again here.

[0402] In some alternative embodiments, the apparatus further includes:

[0403] The first determining module is configured to determine the second device brand corresponding to the device to be shared and the device identifier of the device to be shared.

[0404] The third sending module is configured to send at least the device identifier of the device to be shared to the designated server.

[0405] Optionally, the designated server is a third-party server;

[0406] The first sending module includes:

[0407] The first sending submodule is configured to send the URL address to the third-party server through the first server corresponding to the first device brand; wherein, the first device brand is the device brand corresponding to the vehicle owner's terminal device;

[0408] The third sending module includes:

[0409] The second sending submodule is configured to send the second device brand and the device identifier of the device to be shared to the third-party server through the first server.

[0410] The specific implementation method is the same as described above. Figure 2 The implementation of the illustrated embodiments is similar and will not be described again here.

[0411] In some alternative embodiments, the apparatus further includes:

[0412] The first determining module is configured to determine the second device brand corresponding to the device to be shared and the device identifier of the device to be shared.

[0413] The third sending module is configured to send at least the device identifier of the device to be shared to the designated server.

[0414] Optionally, if the first device brand corresponding to the vehicle owner's terminal device is the same as the second device brand, the designated server is the first server corresponding to the first device brand;

[0415] The third sending module includes any one of the following:

[0416] The third sending submodule is configured to send the device identifier of the device to be shared to the first server;

[0417] The fourth sending submodule is configured to send the second device brand and the device identifier of the device to be shared to the first server.

[0418] The specific implementation method is the same as described above. Figure 3 or Figure 4The implementation of the illustrated embodiments is similar and will not be described again here.

[0419] In some alternative embodiments, the apparatus further includes:

[0420] The fourth sending module is configured to send a specified message to the device to be shared; wherein the specified message does not include the URL address, and the specified message includes at least the first token information of the vehicle owner device, and the specified message is used by the device to be shared to initiate a registration request to the specified server, and the specified server determines the binding relationship of the digital car key sharing process between the vehicle owner device and the device to be shared based at least on the registration request.

[0421] The specific implementation method is the same as described above. Figure 5A The implementation of the illustrated embodiments is similar and will not be described again here.

[0422] In some alternative embodiments, the apparatus further includes:

[0423] The third receiving module is configured to receive the second token information of the sharing terminal device sent by the designated server, which has the binding relationship with the vehicle owner terminal device;

[0424] The fifth sending module is configured to send target token information to the designated server when the URL address is sent to the designated server, so that the designated server forwards the URL address to the parsing component of the terminal device to be shared based on the target token information; wherein the target token information is at least one of the second token information.

[0425] The specific implementation method is the same as described above. Figure 5B The implementation of the illustrated embodiments is similar and will not be described again here.

[0426] Optionally, the parsing component is a digital key frame.

[0427] Reference Figure 22 , Figure 22 This is a block diagram of an apparatus for sharing a digital car key according to an exemplary embodiment. The apparatus is applied to a designated server, and the apparatus includes:

[0428] The first receiving module 2201 is configured to receive a Uniform Resource Locator (URL) address sent by the vehicle owner's terminal device for sharing the digital car key; the second sending module 2202 is configured to forward the URL address to the parsing component of the terminal device to be shared.

[0429] The specific implementation method is the same as described above. Figure 6 The implementation of the illustrated embodiments is similar and will not be described again here.

[0430] In some alternative embodiments, the designated server is a third-party server;

[0431] The first receiving module includes:

[0432] The first receiving submodule is configured to receive the URL address sent by the vehicle owner's terminal device through a first server corresponding to the first device brand; wherein, the first device brand is the device brand corresponding to the vehicle owner's terminal device.

[0433] Optionally, the device further includes:

[0434] The fourth receiving module is configured to receive the second device brand corresponding to the device to be shared and the device identifier of the device to be shared, sent by the vehicle owner terminal device through the first server.

[0435] The second determining module is configured to determine the second server corresponding to the second device brand based on the second device brand.

[0436] The second sending module includes:

[0437] The fifth sending submodule is configured to send the device identifier of the device to be shared and the URL address to the second server. After the second server determines the device to be shared based on the device identifier, it sends the URL address to the parsing component of the device to be shared.

[0438] The specific implementation method is the same as described above. Figure 7 The implementation of the illustrated embodiments is similar and will not be described again here.

[0439] In some optional embodiments, the designated server is a first server corresponding to a first device brand; wherein, the first device brand is the device brand corresponding to the vehicle owner's terminal device;

[0440] The device further includes:

[0441] The fifth receiving module is configured to receive the second device brand and the device identifier of the device to be shared from the vehicle owner's terminal device.

[0442] The first control module is configured to, when the first device brand and the second device brand are the same, determine the sharing terminal device based on the device identifier of the sharing terminal device, and then control the second sending module to forward the URL address to the parsing component of the sharing terminal device.

[0443] The specific implementation method is the same as described above. Figure 8The implementation of the illustrated embodiments is similar and will not be described again here.

[0444] In some optional embodiments, the designated server is a first server corresponding to a first device brand; wherein, the first device brand is the device brand corresponding to the vehicle owner's terminal device;

[0445] The device further includes:

[0446] The sixth receiving module is configured to receive the device identifier of the device to be shared, sent by the vehicle owner's terminal device when the first device brand and the second device brand are the same.

[0447] The second control module is configured to, after determining the device to be shared based on the device identifier of the device to be shared, control the second sending module to forward the URL address to the parsing component of the device to be shared.

[0448] The specific implementation method is the same as described above. Figure 9 The implementation of the illustrated embodiments is similar and will not be described again here.

[0449] In some alternative embodiments, the apparatus further includes:

[0450] The seventh receiving module is configured to receive registration information sent by the device to be shared; wherein the registration message includes the first token information of the vehicle owner device;

[0451] The registration module is configured to register the second token information corresponding to the device to be shared, and the first token information of the vehicle owner device, on the designated server based on the registration information.

[0452] The third determining module is configured to determine the binding relationship of the digital car key sharing process between the car owner terminal device and the terminal device to be shared based on the registration information, the first token information and the second token information;

[0453] The second sending module includes:

[0454] The sixth sending submodule is configured to forward the URL address to the device to be shared based on the binding relationship.

[0455] The specific implementation method is the same as described above. Figure 10A The implementation of the illustrated embodiments is similar and will not be described again here.

[0456] In some alternative embodiments, the apparatus further includes:

[0457] The sixth sending module is configured to send the second token information of the sharing terminal device that has the binding relationship with the vehicle owner terminal device to the vehicle owner terminal device;

[0458] The eighth receiving module is configured to receive target token information sent by the vehicle owner's terminal device; wherein the target token information is at least one of the second token information;

[0459] The second sending module includes:

[0460] The seventh sending submodule is configured to forward the URL address to the parsing component of the device to be shared, based on the target token information.

[0461] The specific implementation method is the same as described above. Figure 10B The implementation of the illustrated embodiments is similar and will not be described again here.

[0462] Optionally, the parsing component is a digital key frame.

[0463] Reference Figure 23 , Figure 23 This is a block diagram illustrating an apparatus for sharing a digital car key according to an exemplary embodiment. The apparatus is applied to a device to which the key is to be shared, and the apparatus includes:

[0464] The second receiving module 2301 is configured to receive, through a parsing component, a Uniform Resource Locator (URL) address forwarded by a designated server for sharing the digital car key on the vehicle owner's device; the generating module 2302 is configured to generate the digital car key shared by the vehicle owner's device based on the URL address.

[0465] The specific implementation method is the same as described above. Figure 11 The implementation of the illustrated embodiments is similar and will not be described again here.

[0466] In some alternative embodiments, the designated server is a third-party server;

[0467] The second receiving module includes:

[0468] The second receiving submodule is configured to receive the URL address sent by the second server corresponding to the second device brand through a parsing component; wherein, the second device brand is the device brand corresponding to the device to be shared, and the URL address is forwarded by the designated server to the second server.

[0469] The specific implementation method is the same as described above. Figure 12 The implementation of the illustrated embodiments is similar and will not be described again here.

[0470] In some alternative embodiments, the designated server is a first server corresponding to a first device brand; wherein, the first device brand is the device brand corresponding to the vehicle owner's terminal device.

[0471] The specific implementation method is the same as described above. Figure 13 The implementation of the illustrated embodiments is similar and will not be described again here.

[0472] In some alternative embodiments, the apparatus further includes:

[0473] The ninth receiving module is configured to receive a specified message sent by the vehicle owner's terminal device; wherein the specified message does not include the URL address, and the specified message includes the first token information of the vehicle owner's terminal device;

[0474] The seventh sending module is configured to send registration information to the designated server based on the specified message; wherein the registration message includes the first token information, and the registration information is used to register the second token information of the device to be shared on the designated server, as well as to register the first token information.

[0475] The specific implementation method is the same as described above. Figure 14 The implementation of the illustrated embodiments is similar and will not be described again here.

[0476] In some alternative embodiments,

[0477] The generation module includes:

[0478] The generation submodule is configured to generate the digital car key shared by the vehicle owner's device based on the URL address by the parsing component.

[0479] The specific implementation method is the same as described above. Figure 15 The implementation of the illustrated embodiments is similar and will not be described again here.

[0480] In some alternative embodiments, the apparatus further includes:

[0481] The output module is configured to output a prompt message; wherein the prompt message is used to indicate that the digital car key shared by the vehicle owner's terminal device has been generated.

[0482] The specific implementation method is the same as described above. Figure 16 The implementation of the illustrated embodiments is similar and will not be described again here.

[0483] Optionally, the parsing component is a digital key frame.

[0484] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this disclosure according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0485] Accordingly, this disclosure also provides a computer-readable storage medium for storing a computer program, which, when executed by a processor, is used to implement the steps of the method for sharing a digital car key as described in any of the above-described methods for the vehicle owner's terminal device.

[0486] Accordingly, this disclosure also provides a computer-readable storage medium for storing a computer program, which, when executed by a processor, is used to implement the steps of the method for sharing a digital car key as described above on the designated server side.

[0487] Accordingly, this disclosure also provides a computer-readable storage medium for storing a computer program, which, when executed by a processor, is used to implement the steps of the method for sharing a digital car key as described in any of the above-described methods for sharing a digital car key on the end device side.

[0488] Accordingly, this disclosure also provides a device for sharing digital car keys, comprising:

[0489] processor;

[0490] Memory used to store processor-executable instructions;

[0491] The processor is configured to execute the executable instructions to implement the steps of the method for sharing a digital car key as described in any of the above-described methods on the vehicle owner's device side.

[0492] Figure 24 This is a block diagram illustrating an apparatus for sharing a digital car key according to an exemplary embodiment. For example, apparatus 2400 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, or other terminal device.

[0493] Reference Figure 24The device 2400 may include one or more of the following components: a processing component 2402, a memory 2404, a power supply component 2406, a multimedia component 2408, an audio component 2410, an input / output (I / O) interface 2412, a sensor component 2416, and a communication component 2418.

[0494] Processing component 2402 typically controls the overall operation of device 2400, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 2402 may include one or more processors 2420 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 2402 may include one or more modules to facilitate interaction between processing component 2402 and other components. For example, processing component 2402 may include a multimedia module to facilitate interaction between multimedia component 2408 and processing component 2402.

[0495] One of the processors 2420 in the processing component 2402 can be configured to perform the above-described method of sharing a digital car key.

[0496] Memory 2404 is configured to store various types of data to support the operation of device 2400. Examples of this data include instructions for any application or method operating on device 2400, contact data, phonebook data, messages, pictures, videos, etc. Memory 2404 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0497] Power supply component 2406 provides power to various components of device 2400. Power supply component 2406 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to device 2400.

[0498] Multimedia component 2408 includes a screen that provides an output interface between device 2400 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 2408 includes a front-facing camera and / or a rear-facing camera. When device 2400 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0499] Audio component 2410 is configured to output and / or input audio signals. For example, audio component 2410 includes a microphone (MIC) configured to receive external audio signals when device 2400 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 2404 or transmitted via communication component 2418. In some embodiments, audio component 2410 also includes a speaker for outputting audio signals.

[0500] I / O interface 2412 provides an interface between processing component 2402 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0501] Sensor assembly 2416 includes one or more sensors for providing state assessment of various aspects of device 2400. For example, sensor assembly 2416 may detect the on / off state of device 2400, the relative positioning of components such as the display and keypad of device 2400, changes in the position of device 2400 or a component of device 2400, the presence or absence of user contact with device 2400, the orientation or acceleration / deceleration of device 2400, and temperature changes of device 2400. Sensor assembly 2416 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 2416 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 2416 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0502] Communication component 2418 is configured to facilitate wired or wireless communication between device 2400 and other devices. Device 2400 can access wireless networks based on communication standards, such as WiFi, 3G, 4G, 5G, 6G, or combinations thereof. In one exemplary embodiment, communication component 2418 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 2418 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0503] In an exemplary embodiment, the apparatus 2400 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0504] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 2404 including instructions, which can be executed by a processor 2420 of the device 2400 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0505] Accordingly, this disclosure also provides a device for sharing digital car keys, comprising:

[0506] processor;

[0507] Memory used to store processor-executable instructions;

[0508] The processor is configured to execute the executable instructions to implement the steps of the method for sharing a digital car key as described in any of the above-mentioned specified server-side methods.

[0509] like Figure 25 As shown, Figure 25 This is a schematic diagram illustrating the structure of a device 2500 for sharing digital car keys according to an exemplary embodiment. The device 2500 can be provided as a designated server. (Refer to...) Figure 25 The device 2500 includes a processing component 2522, a wireless transmitting / receiving component 2524, an antenna component 2526, and a signal processing section specific to the wireless interface. The processing component 2522 may further include one or more processors.

[0510] One of the processors in processing component 2522 can be configured to perform the method of sharing a digital car key as described above on any of the specified server sides.

[0511] Accordingly, this disclosure also provides a device for sharing digital car keys, comprising:

[0512] processor;

[0513] Memory used to store processor-executable instructions;

[0514] The processor is configured to execute the executable instructions to implement the steps of the method for sharing a digital car key as described in any of the above-described methods for sharing a digital car key on the device to be shared.

[0515] Figure 26 This is a block diagram illustrating a device for sharing a digital car key according to an exemplary embodiment. For example, device 2600 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, or other terminal device.

[0516] Reference Figure 26 The device 2600 may include one or more of the following components: a processing component 2602, a memory 2604, a power supply component 2606, a multimedia component 2608, an audio component 2610, an input / output (I / O) interface 2612, a sensor component 2616, and a communication component 2618.

[0517] Processing component 2602 typically controls the overall operation of device 2600, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 2602 may include one or more processors 2620 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 2602 may include one or more modules to facilitate interaction between processing component 2602 and other components. For example, processing component 2602 may include a multimedia module to facilitate interaction between multimedia component 2608 and processing component 2602.

[0518] One of the processors 2620 in the processing component 2602 can be configured to perform the above-described method of sharing a digital car key.

[0519] Memory 2604 is configured to store various types of data to support the operation of device 2600. Examples of this data include instructions for any application or method operating on device 2600, contact data, phonebook data, messages, pictures, videos, etc. Memory 2604 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0520] Power supply component 2606 provides power to various components of device 2600. Power supply component 2606 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to device 2600.

[0521] Multimedia component 2608 includes a screen that provides an output interface between device 2600 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 2608 includes a front-facing camera and / or a rear-facing camera. When device 2600 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0522] Audio component 2610 is configured to output and / or input audio signals. For example, audio component 2610 includes a microphone (MIC) configured to receive external audio signals when device 2600 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 2604 or transmitted via communication component 2618. In some embodiments, audio component 2610 also includes a speaker for outputting audio signals.

[0523] I / O interface 2612 provides an interface between processing component 2602 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0524] Sensor assembly 2616 includes one or more sensors for providing state assessments of various aspects of device 2600. For example, sensor assembly 2616 may detect the on / off state of device 2600, the relative positioning of components such as the display and keypad of device 2600, changes in the position of device 2600 or a component of device 2600, the presence or absence of user contact with device 2600, the orientation or acceleration / deceleration of device 2600, and temperature changes of device 2600. Sensor assembly 2616 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 2616 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 2616 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0525] Communication component 2618 is configured to facilitate wired or wireless communication between device 2600 and other devices. Device 2600 can access wireless networks based on communication standards, such as WiFi, 3G, 4G, 5G, 6G, or combinations thereof. In one exemplary embodiment, communication component 2618 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 2618 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0526] In an exemplary embodiment, the apparatus 2600 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0527] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 2604 including instructions, which can be executed by a processor 2620 of the device 2600 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0528] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0529] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the disclosure herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0530] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A method for sharing digital car keys, characterized in that, The method is applied to a vehicle owner's terminal device, and the method includes: The Uniform Resource Locator (URL) address used to share the digital car key is sent to a designated server; wherein, the designated server is used to forward the URL address to the parsing component of the device to be shared. Before sending the Uniform Resource Locator (URL) address used to share the digital car key to the designated server, the method further includes: A specified message is sent to the device to be shared; wherein the specified message does not include the URL address, and the specified message includes at least the first token information of the vehicle owner device, the specified message is used by the device to be shared to initiate a registration request to the specified server, and the specified server determines the binding relationship of the digital car key sharing process between the vehicle owner device and the device to be shared based at least on the registration request; wherein the binding relationship means that when the specified server receives a URL address for sharing digital car keys sent from the vehicle owner device, the specified server forwards the URL address to the parsing component of the device to be shared that has the binding relationship; The method further includes: Receive the second token information of the terminal device to be shared, which is bound to the vehicle owner's terminal device, sent by the designated server; When the URL address is sent to the designated server, target token information is sent to the designated server so that the designated server forwards the URL address to the parsing component of the device to be shared based on the target token information; wherein the target token information is at least one of the second token information.

2. The method according to claim 1, characterized in that, The method further includes: Determine the second device brand corresponding to the device to be shared and the device identifier of the device to be shared; At least the device identifier of the device to be shared is sent to the designated server.

3. The method according to claim 2, characterized in that, The designated server is a third-party server; Sending the Uniform Resource Locator (URL) address used to share the digital car key to the designated server includes: The URL address is sent to the third-party server through the first server corresponding to the first device brand; wherein, the first device brand is the device brand corresponding to the vehicle owner's terminal device; Sending at least the device identifier of the device to be shared to the designated server includes: The second device brand and the device identifier of the device to be shared are sent to the third-party server through the first server.

4. The method according to claim 2, characterized in that, If the first device brand corresponding to the vehicle owner's terminal device is the same as the second device brand, the designated server is the first server corresponding to the first device brand; Sending at least the device identifier of the end device to be shared to the designated server includes any one of the following: Send the device identifier of the device to be shared to the first server; Send the second device brand and the device identifier of the device to be shared to the first server.

5. The method according to any one of claims 1-4, characterized in that, The parsing component is a digital key frame.

6. A method for sharing digital car keys, characterized in that, The method is applied to a specified server, and the method includes: Receive the Uniform Resource Locator (URL) address sent by the vehicle owner's device for sharing the digital car key; The URL address is forwarded to the parsing component of the device to be shared; Before receiving the Uniform Resource Locator (URL) address sent by the vehicle owner's device for sharing the digital car key, the method further includes: Receive registration information sent by the device to be shared; wherein the registration message includes the first token information of the vehicle owner device; Based on the registration information, register the second token information corresponding to the device to be shared on the designated server, and register the first token information of the vehicle owner's device. Based on the registration information, the first token information, and the second token information, the binding relationship between the vehicle owner's terminal device and the terminal device to be shared is determined; wherein, the binding relationship means that when the designated server receives a URL address sent from the vehicle owner's terminal device for sharing the digital car key, the designated server forwards the URL address to the parsing component of the terminal device to be shared that has the binding relationship. The method further includes: Send the second token information of the sharing terminal device that has the binding relationship with the vehicle owner terminal device to the vehicle owner terminal device; The system receives target token information sent by the vehicle owner's terminal device; wherein the target token information is at least one of the second token information; wherein the target token information is used by the designated server to forward the URL address to the parsing component of the terminal device to be shared.

7. The method according to claim 6, characterized in that, The designated server is a third-party server; The Uniform Resource Locator (URL) address sent by the receiving vehicle owner's device for sharing the digital car key includes: The system receives the URL address sent by the vehicle owner's terminal device through a first server corresponding to a first device brand; wherein, the first device brand is the device brand corresponding to the vehicle owner's terminal device.

8. The method according to claim 7, characterized in that, The method further includes: The vehicle owner's terminal device receives the second device brand corresponding to the terminal device to be shared and the device identifier of the terminal device to be shared, sent by the first server through the first server. Based on the second device brand, determine the second server corresponding to the second device brand; The parsing component that forwards the URL address to the device to be shared includes: The device identifier of the device to be shared and the URL address are sent to the second server. After the second server determines the device to be shared based on the device identifier, it sends the URL address to the parsing component of the device to be shared.

9. The method according to claim 6, characterized in that, The designated server is the first server corresponding to the first device brand; wherein, the first device brand is the device brand corresponding to the vehicle owner's terminal device; The method further includes: Receive the device identifier of the device to be shared from the vehicle owner's terminal device when the first device brand and the second device brand corresponding to the device to be shared are the same; After determining the device to be shared based on the device identifier of the device to be shared, the step of forwarding the URL address to the parsing component of the device to be shared is executed.

10. The method according to claim 7, characterized in that, The designated server is the first server corresponding to the first device brand; wherein, the first device brand is the device brand corresponding to the vehicle owner's terminal device; The method further includes: Receive the second device brand and device identifier of the device to be shared from the vehicle owner's terminal device; If the first device brand and the second device brand are the same, after determining the device to be shared based on the device identifier of the device to be shared, the step of forwarding the URL address to the parsing component of the device to be shared is executed.

11. The method according to any one of claims 6-10, characterized in that, The parsing component is a digital key frame.

12. A method for sharing digital car keys, characterized in that, The method is applied to the device to be shared, and the method includes: The parsing component receives a Uniform Resource Locator (URL) address forwarded by a designated server for sharing the digital car key on the vehicle owner's device; wherein, the device to be shared and the vehicle owner's device are bound together, and the binding relationship means that when the designated server receives the URL address for sharing the digital car key sent from the vehicle owner's device, the designated server forwards the URL address to the parsing component of the bound device to be shared; Based on the URL address, the digital car key shared by the car owner's device is generated; Before receiving the Uniform Resource Locator (URL) address of the digital car key for sharing the vehicle owner's device, forwarded by the specified server through the parsing component, the method further includes: Receive a specified message sent by the vehicle owner's terminal device; wherein the specified message does not include the URL address, and the specified message includes the first token information of the vehicle owner's terminal device; Based on the specified message, registration information is sent to the specified server; wherein the registration message includes the first token information, and the registration information is used to register the second token information of the device to be shared on the specified server, as well as to register the first token information.

13. The method according to claim 12, characterized in that, The designated server is a third-party server; The step of receiving the Uniform Resource Locator (URL) address of the digital car key forwarded by the designated server through the parsing component for sharing the vehicle owner's device includes: The parsing component receives the URL address sent by the second server corresponding to the second device brand; wherein, the second device brand is the device brand corresponding to the device to be shared, and the URL address is forwarded by the designated server to the second server.

14. The method according to claim 12, characterized in that, The designated server is the first server corresponding to the first device brand; wherein, the first device brand is the device brand corresponding to the vehicle owner's terminal device.

15. The method according to claim 12, characterized in that, The step of generating the digital car key shared by the vehicle owner's device based on the URL address includes: The parsing component generates the digital car key shared by the car owner's device based on the URL address.

16. The method according to claim 12, characterized in that, After generating the digital car key shared by the vehicle owner's device, the method further includes: Output a prompt message; wherein the prompt message is used to indicate that the digital car key shared by the vehicle owner's terminal device has been generated.

17. The method according to any one of claims 12-16, characterized in that, The parsing component is a digital key frame.

18. A device for sharing digital car keys, characterized in that, The device is applied to a vehicle owner's terminal device, and the device includes: The first sending module is configured to send a Uniform Resource Locator (URL) address for sharing the digital car key to a designated server; wherein the designated server is used to forward the URL address to the parsing component of the device to be shared. The device is also configured to: A specified message is sent to the device to be shared; wherein the specified message does not include the URL address, and the specified message includes at least the first token information of the vehicle owner device, the specified message is used by the device to be shared to initiate a registration request to the specified server, and the specified server determines the binding relationship of the digital car key sharing process between the vehicle owner device and the device to be shared based at least on the registration request; wherein the binding relationship means that when the specified server receives a URL address for sharing digital car keys sent from the vehicle owner device, the specified server forwards the URL address to the parsing component of the device to be shared that has the binding relationship; The device is also configured to: Receive the second token information of the terminal device to be shared, which is bound to the vehicle owner's terminal device, sent by the designated server; When the URL address is sent to the designated server, target token information is sent to the designated server so that the designated server forwards the URL address to the parsing component of the device to be shared based on the target token information; wherein the target token information is at least one of the second token information.

19. A device for sharing digital car keys, characterized in that, The apparatus is used on a designated server, and the apparatus includes: The first receiving module is configured to receive a Uniform Resource Locator (URL) address sent by the vehicle owner's device for sharing the digital car key; The second sending module is configured to forward the URL address to the parsing component of the device to be shared; The device is also configured to: Receive registration information sent by the device to be shared; wherein the registration message includes the first token information of the vehicle owner device; Based on the registration information, register the second token information corresponding to the device to be shared on the designated server, and register the first token information of the vehicle owner's device. Based on the registration information, the first token information, and the second token information, the binding relationship between the vehicle owner's terminal device and the terminal device to be shared is determined; wherein, the binding relationship means that when the designated server receives a URL address sent from the vehicle owner's terminal device for sharing the digital car key, the designated server forwards the URL address to the parsing component of the terminal device to be shared that has the binding relationship. The device is also configured to: Send the second token information of the sharing terminal device that has the binding relationship with the vehicle owner terminal device to the vehicle owner terminal device; The system receives target token information sent by the vehicle owner's terminal device; wherein the target token information is at least one of the second token information; wherein the target token information is used by the designated server to forward the URL address to the parsing component of the terminal device to be shared.

20. A device for sharing digital car keys, characterized in that, The device is applied to the device to be shared, and the device includes: The second receiving module is configured to receive, via a parsing component, a Uniform Resource Locator (URL) address forwarded by a designated server for sharing the digital car key on the vehicle owner's device; wherein, the device to be shared and the vehicle owner's device are bound together, the binding relationship meaning that when the designated server receives the URL address for sharing the digital car key from the vehicle owner's device, the designated server forwards the URL address to the parsing component of the bound device to be shared; The generation module is configured to generate the digital car key shared by the vehicle owner's terminal device based on the URL address; The device is also configured to: Receive a specified message sent by the vehicle owner's terminal device; wherein the specified message does not include the URL address, and the specified message includes the first token information of the vehicle owner's terminal device; Based on the specified message, registration information is sent to the specified server; wherein the registration message includes the first token information, and the registration information is used to register the second token information of the device to be shared on the specified server, as well as to register the first token information.

21. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the steps of the method for sharing a digital car key as described in any one of claims 1-5.

22. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the steps of the method for sharing a digital car key as described in any one of claims 6-11.

23. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the steps of the method for sharing a digital car key as described in any one of claims 12-17.

24. A device for sharing digital car keys, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to execute the executable instructions to implement the steps of the method for sharing a digital car key as described in any one of claims 1-5.

25. A device for sharing digital car keys, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to execute the executable instructions to implement the steps of the method for sharing a digital car key as described in any one of claims 6-11.

26. A device for sharing digital car keys, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to execute the executable instructions to implement the steps of the method for sharing a digital car key as described in any one of claims 12-17.

Images