Digital key sharing method for vehicle and apparatus therefor

Abstract

This invention provides a method and apparatus for sharing digital keys for vehicles. The method includes: receiving a service instruction for a vehicle and authorization information for the vehicle's digital key from a first party; setting up a service group in response to the service instruction, the service group including the first party and a second party providing services to the vehicle; generating a shared key for the vehicle based on the authorization information; and assigning the shared key to the second party in the service group, allowing the second party to obtain operating rights to the vehicle. Furthermore, this invention also provides a digital key sharing system for vehicles. Through this invention, a service group can be set up to share the vehicle's digital key when services are needed, thereby facilitating the vehicle's operation by the service provider.

Description

Technical Field

[0001] This invention relates to vehicles, and more specifically, to a method and apparatus for sharing digital keys for vehicles. Background Technology

[0002] With the widespread adoption of mobile devices such as smartphones and advancements in technology, more and more drivers are using these mobile devices as car keys, namely digital keys or virtual keys. This technology provides a convenient solution for unlocking, starting, and sharing vehicles without the need for traditional physical keys. For example, digital keys can use devices such as smartphones and smartwatches, utilizing communication technologies such as BLE (Bluetooth), NFC (Near Field Communication), and UWB (Ultra Wideband), to enable keyless entry and start of vehicles.

[0003] One important application of digital keys is vehicle sharing, which simplifies the car-borrowing process. With digital keys, car owners can easily share their vehicles with others without physically exchanging keys. However, while increasing convenience, this trend also brings new challenges to remote sharing technology. For example, in this context, we need to consider how to provide services such as vehicle delivery, maintenance, valet parking, and breakdown repair without traditional physical keys, thereby ensuring the security and manageability of the vehicle after it is lent out.

[0004] Accordingly, in order to achieve remote sharing, there is a need in the field for technology that allows vehicle owners to share the digital key of their vehicle with specific individuals, so that valet parking service personnel or maintenance technicians can access the vehicle after obtaining authorization without a physical key. Summary of the Invention

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

[0006] In view of the deficiencies of the prior art, the purpose of the present invention is to provide a digital key sharing method and apparatus for vehicles, which enables vehicle owners to securely share their digital keys with one or more specific persons through a service platform or application, thereby authorizing the one or more specific persons to access the vehicle.

[0007] According to one aspect of the present invention, a method for sharing a digital key for a vehicle is provided, comprising: receiving a service instruction for the vehicle and authorization information of the vehicle's digital key from a first party; setting up a service group in response to the service instruction, the service group including the first party and a second party providing services for the vehicle; generating a shared key for the vehicle based on the authorization information; and assigning the shared key to the second party in the service group so that the second party can obtain operating rights for the vehicle.

[0008] According to one embodiment, the digital key sharing method further includes deleting the shared key upon determining that service to the vehicle is complete.

[0009] According to one embodiment, the first party includes a user of the vehicle, and receiving service instructions for the vehicle and authorization information for the vehicle's digital key from the first party further includes receiving service instructions and authorization information from the user's smart terminal.

[0010] According to one embodiment, service instructions include valet parking, vehicle maintenance, breakdown repair, or any combination thereof.

[0011] According to one embodiment, the second party includes multiple service personnel of the vehicle, and assigning the shared key to the second party in the service group further includes: assigning the shared key to one or more of the multiple service personnel based on their identity information.

[0012] According to one embodiment, the digital key sharing method further includes: receiving service status information from parties in a service group; updating the progress of the service based on the status information, and sharing the progress with the parties in the service group.

[0013] According to one embodiment, assigning a shared key to a second party in a service group further includes sending a link to the shared key to the second party so that the second party can obtain the shared key via the link.

[0014] According to one embodiment, the vehicle's operating permissions include opening the doors and starting the vehicle.

[0015] According to another aspect of the present invention, a digital key sharing device for a vehicle is provided, comprising: a memory; a communication interface; and at least one controller communicatively coupled to the memory and the communication interface, the at least one controller being configured to: receive a service instruction for the vehicle and authorization information of the vehicle's digital key from a first party; set up a service group in response to the service instruction, the service group including the first party and a second party providing services for the vehicle; generate a shared key for the vehicle based on the authorization information; and assign the shared key to the second party in the service group so that the second party can obtain operating rights for the vehicle.

[0016] According to one embodiment, the at least one controller is further configured to delete the shared key upon determining that the service to the vehicle is complete.

[0017] According to one embodiment, the second party includes multiple service personnel of the vehicle, and assigning a shared key to the second party in the service group further includes: assigning the shared key to one or more of the multiple service personnel based on their identity information.

[0018] According to one embodiment, the at least one controller is further configured to: receive service status information from all parties in the service group; update the service progress based on the status information, and share the progress with all parties in the service group.

[0019] According to one embodiment, assigning a shared key to a second party in a service group further includes sending a link to the shared key to the second party so that the second party can obtain the shared key via the link.

[0020] According to another aspect of the present invention, a digital key sharing system for a vehicle is provided, the digital key sharing system comprising: a vehicle having a wireless communication device and a security system for obtaining operating permissions of the vehicle via a digital key; and a digital key sharing device for a vehicle according to the present invention.

[0021] According to another aspect of the invention, a non-transient computer-readable storage medium is provided that stores computer-executable instructions, which, when executed by a processor, cause the processor to perform a digital key sharing method for a vehicle according to the invention.

[0022] By employing the method and apparatus of this invention, vehicle users can share digital keys with one or more appropriate service personnel who will be involved in vehicle services.

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

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

[0025] Figure 1A flowchart illustrating a digital key sharing method for vehicles according to an embodiment of the present invention is provided.

[0026] Figure 2 A block diagram of a digital key sharing device for a vehicle according to an embodiment of the present invention is described.

[0027] Figure 3 An architecture diagram of a digital key sharing system for vehicles according to an embodiment of the present invention is explained.

[0028] Figure 4 A schematic diagram illustrating a shared digital key for a vehicle according to an embodiment of the present invention is provided.

[0029] Figure 5 The illustration shows the effect of a user terminal implementing digital key sharing according to an embodiment of the present invention.

[0030] Figure 6 A block diagram of an exemplary computing device according to an embodiment of the present invention has been described. Detailed Implementation

[0031] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the exemplary embodiments described. However, it will be apparent to those skilled in the art that the described embodiments can be practiced without some or all of these specific details. In other exemplary embodiments, well-known structures or processing steps have not been described in detail to avoid unnecessarily obscuring the concepts of this disclosure.

[0032] Figure 1 A flowchart of a digital key sharing method 100 for a vehicle according to an embodiment of the present invention is provided.

[0033] At box 110, method 100 may include receiving service instructions for the vehicle from a first party, as well as authorization information for the vehicle's digital key.

[0034] As a non-limiting embodiment, the authorization information may include access permissions for the vehicle, such as allowing the authorized party (i.e., the second party hereinafter referred to as the authorized party) to unlock, start, and use the air conditioning. Additionally, the authorization information may also restrict the authorized party's use of certain vehicle functions, such as limiting the vehicle's maximum speed or specific driving areas. Furthermore, the authorization information may include vehicle device information, but for privacy reasons, it may not include access permissions to certain information about the vehicle and / or the owner (i.e., the first party). In summary, through this authorization information, the vehicle owner can control who can access and use their vehicle, while protecting their privacy and security. This information forms the basis of the digital key sharing service, enabling vehicle owners to conveniently share vehicle usage rights with family, friends, or service personnel.

[0035] In one embodiment, the first party may include the user of the vehicle. Accordingly, receiving service instructions and authorization information for the vehicle's digital key from the first party may include receiving the service instructions and authorization information from the user's smart terminal. For example, the vehicle user (such as the owner) may input service instructions and digital key authorization information via a mobile phone, tablet, computer, or other device.

[0036] In another embodiment, service instructions may include valet parking, vehicle maintenance, breakdown repair, or any combination thereof. For example, a first party (such as a vehicle owner) may send instructions such as finding someone to park, vehicle maintenance, or vehicle repair, depending on the actual situation. It can be understood that the first party may also send other instructions that require another party to operate the vehicle, such as chauffeur services.

[0037] At box 120, method 100 may include setting up a service group in response to a service instruction received from a first party, the service group including the first party and a second party providing services to the vehicle.

[0038] At box 130, method 100 may include generating a shared key for the vehicle based on authorization information received from the first party.

[0039] At box 140, method 100 may include assigning the generated shared key to a second party in the service group so that the second party can obtain operating rights to the vehicle.

[0040] In one embodiment, the second party may be a service personnel of the vehicle. That is, the established service group may include the vehicle owner and the vehicle's service personnel. Accordingly, assigning the shared key to the second party in the service group may include assigning the shared key to that service personnel. In another embodiment, the second party may include multiple service personnel of the vehicle. That is, the established service group may include the vehicle owner and multiple service personnel of the vehicle. For example, depending on the type of service, the service group may include the vehicle owner, the vehicle's after-sales manager, technicians, etc. Accordingly, assigning the shared key to the second party in the service group may include: assigning the shared key to one or more of the multiple service personnel based on their identity information. For example, when maintenance or repair of a certain part of the vehicle is required, the shared key may only be assigned to one or more specific technicians in the service group responsible for that part.

[0041] It is understood that, for service groups that include multiple service personnel, shared keys can be assigned to all members of the service group as needed, such as assigning vehicle dealers and / or technicians.

[0042] In another embodiment, assigning a shared key to a second party in the service group may include sending a link to the shared key to the second party so that the second party can obtain the shared key via the link.

[0043] Optionally, method 100 may further include: receiving service status information from each party of the service group, updating the service progress based on the received status information, and sharing the progress with each party of the service group. As a non-limiting example, when the vehicle is undergoing maintenance or repair, one or more technicians of the vehicle may send corresponding service status change information after completing operations on one or more parts of the vehicle, thereby adjusting the service progress accordingly, and each party of the service group may, for example, view the current service progress through their respective terminal devices. For instance, each member of the service group may update the maintenance status in the group chat through an application on their respective terminal, which simultaneously displays the maintenance progress to each member.

[0044] In another embodiment, vehicle operating permissions may include unlocking the doors and starting the vehicle. For example, a second party may use a obtained shared key to unlock the doors and start the vehicle.

[0045] Optionally, method 100 may further include deleting the shared key upon determining that the service to the vehicle has been completed. For example, after the second party completes the service to the vehicle, because the shared key has been deleted, it can no longer use the shared key to open the door and start the vehicle.

[0046] Figure 2 A block diagram illustrating a digital key sharing device 200 for a vehicle according to an embodiment of the present invention is provided. It should be noted that the digital key sharing device 200 is illustrative only and not limiting. The digital key sharing device 200 of the present invention may include, but is not limited to, [other components]. Figure 2 The digital key sharing device shown has 200 or more components.

[0047] like Figure 2 As shown, the digital key sharing device 200 may include a memory 210, a communication interface 230, and at least one controller 220 communicatively coupled to the memory 210 and the communication interface 230.

[0048] The communication interface 230 can be configured to communicate with various parties in the vehicle (e.g., a user's smart terminal). In one example, the communication interface 230 can communicate with these parties wirelessly. This wireless connection can include any wireless connection known in the art and / or developed in the future. Examples of wireless connections include, but are not limited to, Bluetooth, Zigbee, etc. Accordingly, the digital key sharing device 200 can send and receive information from these parties via the communication interface 230. Additionally, the information or data can be stored in the memory 210.

[0049] One or more controllers 220 can be configured to execute various applications, such as those described above. Figure 1 The various operations described above. Specifically, the one or more controllers 220 can be configured to: receive a service instruction for the vehicle and authorization information for the vehicle's digital key from a first party via a communication interface 230; set up a service group in response to the received service instruction, the service group including the first party and a second party providing services for the vehicle; generate a shared key for the vehicle based on the authorization information; and assign the shared key to the second party in the service group via the communication interface 230, so that the second party can obtain operating rights for the vehicle.

[0050] Optionally, the one or more controllers 220 may be further configured to delete the shared key upon determining that the service to the vehicle is complete.

[0051] In one embodiment, the second party may include multiple service personnel of the vehicle. Accordingly, assigning the shared key to the second party in the service group may include assigning the shared key to one or more of the multiple service personnel based on their identity information.

[0052] In another embodiment, the one or more controllers 220 may be further configured to: receive service status information from the parties of the service group; update the progress of the service based on the received status information, and share the progress with the parties of the service group.

[0053] In yet another embodiment, assigning a shared key to a second party in the service group further includes sending a link to the shared key to the second party so that the second party can obtain the shared key via the link.

[0054] As you can understand, the digital key sharing device 200 can also achieve the combination of the above. Figure 1 Other operations in the digital key sharing method 100 have been described above and will not be repeated here.

[0055] Figure 3An architecture diagram of a digital key sharing system 300 for vehicles according to an embodiment of the present invention has been explained. It should be noted that... Figure 3 For illustrative purposes only, this invention is not limited to Figure 3 The various components and / or systems explained in the text are not applicable to, but can be adapted to, including, more. Figure 3 The system shown has more or fewer components.

[0056] like Figure 3 As shown, the digital key sharing system 300 may include one or more vehicles 401, and as described above. Figure 2 The digital key sharing device 200 is described above. Correspondingly, the digital key sharing system 300 can achieve the above-described combination. Figure 1 The digital key sharing method 100 is described above.

[0057] exist Figure 3 In this context, one or more vehicles 401 are equipped with wireless communication devices and a security system that grants access to the vehicle via a digital key.

[0058] For ease of explanation, Figure 3 The diagram shows a first party 310 and a second party 320, with mobile phones used as an example. However, it can be understood that in practice, the parties are not limited to using mobile phones for operation, and the second party 320 may include multiple service personnel.

[0059] The first party 310 can be a user of vehicle 401 (e.g., the vehicle owner), whose terminal (e.g., a mobile phone) may have a digital key sharing application 330 set up. In one example, the digital key sharing application 330 can be an existing application, such as a workshop application for repair or maintenance in a client application. For ease of explanation, a workshop application and corresponding equipment are used as an example here, but it can be understood that digital key sharing can also be performed through other applications and corresponding equipment. The corresponding application can be provided, for example, by the vehicle manufacturer.

[0060] like Figure 3As shown, in one embodiment, a first party 310 (e.g., a vehicle owner) books maintenance services via a mobile phone and agrees to authorize the digital key of vehicle 401 to relevant service personnel (e.g., a second party 320). The digital key sharing system 300 accordingly establishes a service group, creates a shared key 340, and automatically assigns the shared key 340 to the second party 320, i.e., a specific group member (e.g., a dealership employee and / or technician). This specific group member can access the shared key 340 on their mobile phone, thereby gaining operating access to vehicle 401. Optionally, after the maintenance is completed, the digital key sharing system 300 deletes the shared key 340. Thus, the second party 320 can conveniently remotely access the shared key 340 of vehicle 401, and the shared key 340 can also be automatically revoked after the service is completed.

[0061] The following will combine Figure 3 A detailed explanation of the digital key sharing process.

[0062] At point 301, the first party 310 sends a service instruction for vehicle 401 and authorization information for the digital key of vehicle 401 to the maintenance system backend 350 (e.g., SMACC) via the digital key sharing application 330.

[0063] At point 302, the maintenance system backend 350 sends an instruction to the service-based device 360 ​​to create a shared key 340 based on the received authorization information.

[0064] At 303, the workshop server 380 sends a request for the shared key 340 to the service-based device 360. Accordingly, at 305, in response to the request, the service-based device 360 ​​sends a shared link (URL) for the shared key 340 to the workshop server 380, which may be generated by the relay 370 as described below.

[0065] At point 306, the workshop server 380 sends a sharing invitation to a second party 320 (e.g., a service personnel's mobile phone) for the shared key 340.

[0066] Additionally, at 304, after receiving the instruction to create a shared key 340, the service-based device 360 ​​generates a shared key 340 and creates an email address, through which it sends the shared key 340 to the relay 370, which can then generate a shared link for the shared key 340 accordingly.

[0067] At 307, the second party 320 can obtain a shared key 340 from the relay 370 via a shared link by, for example, clicking a shared invitation from the workshop server 380.

[0068] At point 308, the second party 320 can obtain control of vehicle 401 via shared key 340.

[0069] In one example, the maintenance system backend 350, relay 370, and workshop server 380 can be existing equipment for maintenance or repair service applications. Based on this equipment, the digital key sharing system 300 adds a service-based device 360, thereby enabling the sharing of digital keys using existing automotive applications. Furthermore, the digital key sharing method, apparatus, and system for vehicles of the present invention can also remotely share or delete shared keys 340 of vehicle 401 in batches.

[0070] It is understood that the above-mentioned devices or applications are merely exemplary, and different devices or applications can be used to implement the digital key sharing method for vehicles of the present invention according to actual needs.

[0071] Figure 4 A flowchart illustrating an implementation of a digital key sharing architecture 400 for vehicles according to an embodiment of the present invention is provided. For ease of explanation, Figure 4 The image shows the car owner 410 (i.e. Figure 3 The first party (310) and service personnel (420) in the middle Figure 3 The second party (320) in the text can be understood to include multiple service personnel (420) in practice. Additionally, in... Figure 3 Based on the sharing of digital keys shown, Figure 4 The flowchart shown further explains the entire implementation process in conjunction with the scheduled maintenance service. The implementation process for other services can be referenced similarly, and will not be elaborated here.

[0072] like Figure 4 As shown, the digital key sharing architecture 400 includes a vehicle 401 (in practice, there may be multiple vehicles). The smart terminals of the vehicle owner 410 and service personnel 420 can be configured with a user-side application 402 (i.e., Figure 3 Digital key sharing application 330) and e-wallet 403 Figure 3 (Not shown in the image).

[0073] At point 4010, vehicle owner 410 can, for example, book maintenance services through the user application 402 on their smart terminal.

[0074] At 4020, in response to the reservation, the user application 402 of vehicle owner 410 sends a request to the backend 404 of the workshop (i.e., Figure 3The workshop server 380 creates a repair order. At 4030, the workshop backend 404 can send feedback to the vehicle owner 410's client application 402 regarding whether the repair order was successfully created. Steps 4020 and 4030 above are related to repair services. Accordingly, service personnel 420 can service vehicle 401 based on the repair order.

[0075] Additionally, at 4041, in response to this reservation, the vehicle owner 410's client application 402 sends authorization for the service key (i.e., the shared key) to the vehicle owner 410's e-wallet 403. At 4042, the vehicle owner 410's e-wallet 403 sends authorization to the digital key backend 405 (i.e., Figure 3 The authorization is forwarded to the maintenance system backend 350 in the middle. At 4050, the digital key backend 405 forwards the authorization to the service-based device server 406 (i.e., Figure 3 The service-based device 360 ​​sends a request to create a service key, and accordingly, the service-based device server 406 generates a service key. At 4070, the service-based device server 406 creates a mailbox and sends the service key to the relay server 407 (i.e., Figure 3 (Relay 370 in the middle). At 4080, relay server 407 generates the URL of the service key and sends the URL to service-based device server 406.

[0076] On the other hand, at 4060, after receiving the repair order from the user application 402 of the vehicle owner 410 in step 4020, the workshop backend 404 requests a service key from the service-based device server 406. At 4090, in response to the request, the service-based device server 406 forwards the URL of the service key obtained in step 4080 to the workshop backend 404.

[0077] At 4100, the workshop backend 404 synchronizes the created repair order and the URL of the service key to the client application 402 of the service personnel 420 (e.g., vehicle mechanics).

[0078] At point 4111, the client application 402 of service personnel 420 sends an instruction to service personnel 420's e-wallet 403 to obtain the service key via the URL of the service key. Accordingly, at point 4112, service personnel 420's e-wallet 403 connects to relay server 407 via the URL, and at point 4120, relay server 407 sends the service key to service personnel 420's e-wallet 403.

[0079] At location 4130, service personnel 420 obtains access to vehicle 401 via the service key in their electronic wallet 403.

[0080] It can be understood, such as Figure 4 The implementation flowchart shown is merely an example. Steps can be adjusted, modified, added, and / or deleted according to actual needs, as long as they achieve the desired effect. Figure 1 The aforementioned digital key sharing method is sufficient.

[0081] Figure 5 The illustration shows a user terminal implementing digital key sharing according to an embodiment of the present invention. For ease of explanation, Figure 5 In China, mobile phones are used as user terminals.

[0082] At position 502, such as car owner 410 (i.e. Figure 3 As shown on the mobile phone interface of the first party 310, the car owner 410 can make an appointment with the service personnel 420 (i.e., Figure 3 The second party (320) shares the vehicle key. As an example, the "Share my key" option can be displayed on the appointment service interface, which the vehicle owner (410) checks to determine whether to share their digital key. Alternatively, the vehicle key can be shared through other terminal operations; alternatively, the user can default to agreeing to share their key with the service provider when making an appointment.

[0083] At point 504, as shown on car owner 410's mobile phone interface, after car owner 410 books a service on their phone, a corresponding service group is created in the mobile application. The service group can include car owner 410 and other personnel related to the service. The digital key can be automatically authorized to specific members in the service group.

[0084] At point 506, as shown on the mobile phone interface of service personnel 420, service personnel 420 can obtain the vehicle key from the mobile application. As an example, the application may display a "Get car key" option, which service personnel 420 can click to obtain the digital key. Alternatively, the vehicle key can be obtained through other terminal operations; alternatively, service personnel 420 can automatically obtain the digital key without any operation. For example, the digital key sharing system of this invention can determine whether to assign a digital key to service personnel 420 based on their identity information.

[0085] At point 508, as shown on the service personnel's (420) mobile phone interface, the digital key is automatically deleted upon completion of the service. As an example, a "Delete car key" message may be displayed in the mobile applications of the vehicle owner (410) and / or service personnel (420) to inform them that the digital key has been deactivated. Alternatively or additionally, the vehicle owner (410) may confirm whether to delete the digital key via their mobile phone.

[0086] Figure 6 A block diagram of an exemplary computing device 600 according to an embodiment of the present invention has been described. The computing device 600 is an example of a hardware device applicable to various aspects of the present invention.

[0087] refer to Figure 6 A computing device 600 will now be described as an example of a hardware device (e.g., a digital key sharing device, user equipment, cloud server, vehicle control unit, etc.) applicable to various aspects of the present invention. The computing device 600 can be any machine configured to perform processing and / or computation, and can be, but is not limited to, a workstation, server, desktop computer, laptop computer, tablet computer, personal digital processor, smartphone, vehicle computer, or any combination thereof. The various methods / apparatus / servers / user equipment described above can be implemented wholly or at least partially by the computing device 600 or similar devices or systems.

[0088] The computing device 600 may include components that can be connected or communicated via one or more interfaces and a bus 602. For example, the computing device 600 may include a bus 602, one or more processors 604, one or more input devices 606, and one or more output devices 608. The one or more processors 604 may be any type of processor and may include, but are not limited to, one or more general-purpose processors and / or one or more dedicated processors (e.g., specialized processing chips). The input device 606 may be any type of device capable of inputting information to the computing device and may include, but is not limited to, a mouse, keyboard, touchscreen, microphone, and / or remote controller. The output device 608 may be any type of device capable of presenting information and may include, but is not limited to, a monitor, speaker, video / audio output terminal, vibrator, and / or printer. The computing device 600 may also include or be connected to a non-transient storage device 610. The non-transient storage device can be any non-transient storage device capable of data storage, and may include, but is not limited to, disk drives, optical storage devices, solid-state storage, floppy disks, hard disks, magnetic tapes or any other magnetic media, optical discs or any other optical media, ROM (read-only memory), RAM (random access memory), cache memory, and / or any memory chip or cassette tape, and / or any other medium from which a computer can read data, instructions, and / or code. The non-transient storage device 610 may be detachable from an interface. The non-transient storage device 610 may have data / instructions / code for implementing the methods and steps described above. The computing device 600 may also include a communication device 612. The communication device 612 can be any type of device or system capable of communicating with internal devices and / or with a network, and may include, but is not limited to, modems, network cards, infrared communication devices, wireless communication devices and / or chipsets, such as Bluetooth devices, IEEE 1302.11 devices, WiFi devices, WiMax devices, cellular communication devices and / or similar devices.

[0089] When the computing device 600 is used as an in-vehicle device, it can also be connected to external devices (e.g., a GPS receiver, sensors for sensing different environmental data such as accelerometers, wheel speed sensors, gyroscopes, etc.). In this way, the computing device 600 can, for example, receive positioning data and sensor data indicating the vehicle's driving status. When the computing device 600 is used as an in-vehicle device, it can also be connected to other devices used to control the vehicle's driving and operation (e.g., engine system, windshield wipers, anti-lock braking system, headlight control system, etc.).

[0090] Furthermore, the non-transient storage device 610 may contain map information and software components, enabling the processor 604 to perform route guidance processing. Additionally, the output device 608 may include a display for showing a map, displaying vehicle location markers, and displaying images indicating the vehicle's driving status. The output device 608 may also include a speaker or headphone jack for audio guidance.

[0091] Bus 602 may include, but is not limited to, Industry Standard Architecture (ISA) bus, Microchannel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and PCI bus. In particular, for automotive devices, bus 602 may also include Controller Area Network (CAN) bus or other architectures designed for automotive applications.

[0092] The computing device 600 may also include a working memory 614, which may be any type of working memory capable of storing instructions and / or data that are conducive to the operation of the processor 604, and may include, but is not limited to, random access memory and / or read-only memory devices.

[0093] Software components may reside in working memory 614, including but not limited to operating system 616, one or more application programs 618, drivers, and / or other data and code. Instructions for implementing the above methods and steps may be included in the one or more application programs 618, and the modules / units / components of the aforementioned various devices / servers / user equipment may be implemented by processor 604 reading and executing the instructions of the one or more application programs 618.

[0094] It should also be recognized that variations can be made to suit specific needs. For example, custom hardware and / or specific components may be used, and implementation may take place in hardware, software, firmware, middleware, microcode, hardware description language, or any combination thereof. Furthermore, connectivity with other computing devices, such as network input / output devices, may be employed. For example, some or all of the disclosed methods and apparatus may be implemented using the logic and algorithms according to the invention via programmable hardware (e.g., programmable logic circuits including field-programmable gate arrays (FPGAs) and / or programmable logic arrays (PLAs)) that uses assembly language or hardware programming languages ​​(e.g., Verilog, VHDL, C++).

[0095] Although various aspects of the invention have been described so far with reference to the accompanying drawings, the methods, systems, and apparatus described above are merely examples, and the scope of the invention is not limited to these aspects but is defined only by the appended claims and their equivalents. Various components may be omitted or replaced by equivalent components. Furthermore, the steps may be performed in a different order than that described in the invention. Moreover, various components can be combined in various ways. Importantly, as technology advances, many of the components described may be replaced by equivalent components that appear later.

[0096] List of reference numerals in the attached diagram:

[0097] 100 methods for sharing digital keys for vehicles

[0098] 110 receives vehicle service instructions and vehicle digital key authorization information from a first-party provider.

[0099] 120 sets up a service group in response to a service instruction received from the first party, the service group including the first party and a second party providing services to the vehicle.

[0100] 130 generates a shared key for the vehicle based on the authorization information received from the first party.

[0101] 140 assigns the generated shared key to a second party in the service group, granting the second party operating access to the vehicle.

[0102] 200 digital key sharing devices for vehicles

[0103] 210 Memory

[0104] 220 Controller

[0105] 230 Communication Interface

[0106] 300 Digital Key Sharing System for Vehicles

[0107] 310 First-party

[0108] 320 Second Party

[0109] 330 Digital Key Sharing Application

[0110] 340 Shared Key

[0111] 350 Maintenance System Backend

[0112] 360 Service-Based Devices

[0113] 370 relay

[0114] 380 Workshop Server

[0115] 400 Digital Key Sharing Architecture for Vehicles

[0116] Vehicle 401

[0117] 402 Client Application

[0118] 403 e-wallet

[0119] 404 workshop back end

[0120] 405 Digital Key Backend

[0121] 406 Service-Based Device Server

[0122] 407 Relay Server

[0123] 410 car owner

[0124] 420 Service Personnel

[0125] 500 User Terminal Interface

[0126] 600 computing devices

[0127] 602 bus

[0128] 604 processor

[0129] 606 Input Device

[0130] 608 Output Device

[0131] 610 Storage Device

[0132] 612 Communication equipment

[0133] 614 Working Memory

[0134] 616 Operating System

[0135] 618 App

Claims

1. A method for sharing a digital key for a vehicle, comprising: Receive service instructions for the vehicle and authorization information for the vehicle's digital key from a first party; A service group is set up in response to the service instruction, the service group including the first party and a second party providing services to the vehicle; Generate a shared key for the vehicle based on the authorization information; as well as The shared key is assigned to the second party in the service group so that the second party can obtain operating permissions for the vehicle.

2. The digital key sharing method as described in claim 1, further comprising: Upon completion of service for the vehicle, the shared key is deleted.

3. The digital key sharing method as described in claim 1, wherein the first party includes the user of the vehicle, and receiving service instructions for the vehicle and authorization information for the vehicle's digital key from the first party further includes: The service instructions and authorization information are received from the user's smart terminal.

4. The digital key sharing method as described in claim 1, wherein the service instructions include valet parking, vehicle maintenance, fault repair, or any combination thereof.

5. The digital key sharing method of claim 1, wherein the second party includes multiple service personnel of the vehicle, and assigning the shared key to the second party in the service group further includes: The shared key is assigned to one or more of the multiple service personnel based on their identity information.

6. The digital key sharing method as described in claim 1, further comprising: Receive the status information of the service from each party in the service group; as well as The progress of the service is updated based on the status information, and the progress is shared with all parties in the service group.

7. The digital key sharing method as described in claim 1, wherein assigning the shared key to the second party in the service group further comprises: Send a link to the shared key to the second party so that the second party can obtain the shared key via the link.

8. The digital key sharing method as described in claim 1, wherein the vehicle's operating permissions include opening the vehicle door and starting the vehicle.

9. A digital key sharing device for vehicles, comprising: Memory; Communication interface; as well as At least one controller communicatively coupled to the memory and the communication interface, the at least one controller being configured to: Receive service instructions for the vehicle and authorization information for the vehicle's digital key from a first party; A service group is set up in response to the service instruction, the service group including the first party and a second party providing services to the vehicle; Generate a shared key for the vehicle based on the authorization information; as well as The shared key is assigned to the second party in the service group so that the second party can obtain operating permissions for the vehicle.

10. The digital key sharing device of claim 9, wherein the at least one controller is further configured to: Upon completion of service for the vehicle, the shared key is deleted.

11. The digital key sharing device of claim 9, wherein the second party comprises multiple service personnel of the vehicle, and assigning the shared key to the second party in the service group further comprises: The shared key is assigned to one or more of the multiple service personnel based on their identity information.

12. The digital key sharing device of claim 9, wherein the at least one controller is further configured to: Receive the status information of the service from each party of the service group; and The progress of the service is updated based on the status information, and the progress is shared with all parties in the service group.

13. The digital key sharing device of claim 9, wherein assigning the shared key to the second party in the service group further comprises: Send a link to the shared key to the second party so that the second party can obtain the shared key via the link.

14. A digital key sharing system for vehicles, the digital key sharing system comprising: The vehicle has a wireless communication device and a security system that grants access to the vehicle via a digital key; as well as The digital key sharing device as described in any one of claims 9-13.

15. A non-transient computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, cause the processor to perform the method as described in any one of claims 1-8.

Images