Digital key management method and device, vehicle and computer readable storage medium

Abstract

The invention relates to the field of digital keys, in particular to a digital key management method and device, a vehicle and a computer readable storage medium. The method comprises the following steps: responding to a digital key management request; analyzing the request message to obtain a target identifier; the target identifier comprises an identifier representing a target vehicle and / or a target digital key; determining a target object corresponding to the target identifier according to a preset target mapping relationship; the target object comprises a target vehicle cloud service and / or a target terminal equipment cloud service; the target mapping relationship comprises a first mapping relationship between the vehicle identifier and the vehicle cloud service and a second mapping relationship between the digital key identifier and the terminal equipment cloud service; and forwarding the digital key management request to the target object. The digital key management efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the field of digital key technology, and in particular to a digital key management method, device, vehicle and computer-readable storage medium. Background Art

[0002] With the rapid development of intelligent connected cars, digital key technology has become an important bridge between car owners and vehicles. Digital keys provide a convenient way to access vehicles. Car owners can use mobile phones, smart watches and other terminal devices as digital keys corresponding to their vehicles. Furthermore, remote management and monitoring of key status can be achieved through the cloud services corresponding to terminal devices and vehicles.

[0003] In the process of implementing the prior art, the inventors found that an existing vehicle manufacturer often has multiple sub-brands, and each sub-brand may adopt a self-developed cloud service system. This leads to a complex many-to-many relationship between the terminal device cloud service when connecting to the vehicle. That is, a mobile phone cloud service needs to interact with the cloud services corresponding to multiple manufacturers and their sub-brands to achieve the management of the digital key life cycle, such as creation, deletion, and suspension of digital keys. This increases the connection cost between the mobile phone cloud service and the sub-brands and affects the efficiency of digital key management.

[0004] Therefore, a more efficient digital key management solution is needed. Summary of the invention

[0005] In view of this, the embodiments of the present application provide a digital key management method, device, vehicle and computer-readable storage medium, which can solve the problem of low efficiency of existing digital key management.

[0006] In a first aspect, an embodiment of the present application provides a digital key management method, the digital key management method comprising: responding to a digital key management request; Parsing the digital key management request according to the target digital key protocol to obtain a target identifier; the target identifier includes an identifier representing the target vehicle and / or the target digital key; Determine the target object corresponding to the target identifier according to a preset target mapping relationship; the target object includes a target vehicle cloud service and / or a target terminal device cloud service; the target mapping relationship includes a first mapping relationship between the vehicle identifier and the vehicle cloud service and a second mapping relationship between the digital key identifier and the terminal device cloud service; The digital key management request is forwarded to the target object.

[0007] By adopting the above technical solution, the request message of the digital key management request is parsed to obtain the identifier representing the vehicle or digital key, and the target identifier is further mapped to the target vehicle cloud service or the target terminal device cloud service according to the target mapping relationship to forward the digital key management request. Therefore, in the scenario where multiple terminal device cloud services and multiple vehicle cloud services need to be connected, there is no need for terminal devices such as mobile phone manufacturers or vehicle parties such as OEMs to develop and connect to the cloud services corresponding to each different manufacturer. The embodiment of the present application can parse the digital key management request to obtain the target vehicle cloud service or target terminal device cloud service to which the request needs to be forwarded, thereby improving the management efficiency of digital keys.

[0008] In some embodiments, the method further comprises: Parsing the digital key management request to obtain a request type and request parameters of the digital key management request; The request parameters are parsed according to a target parsing method to obtain the target identifier; wherein the target parsing method is determined according to the request type.

[0009] In some embodiments, the request type includes the management operation requested by the digital key management request and the identity of the sender who initiated the digital key management request; the target resolution method includes an extraction method and a processing method; the extraction method is determined according to the management operation; the processing method is determined according to the sender identity and / or the management operation; The process of determining the target identifier includes: Extracting field value information of the request parameter according to the extraction method to obtain original extracted data; The target identifier is determined according to the original extracted data and the processing method.

[0010] In some embodiments, the extraction method defines a target field of the source of the field value information; wherein, if the management operation represents a key creation operation, the target field includes an encrypted data field, and the original extracted data includes encrypted data; if the management operation represents a non-key creation operation, the target field includes a key identification field, and the original extracted data includes a target key identification.

[0011] In some embodiments, if the management operation represents a create key operation, the method further comprises: Determine, according to the sender identity, a static key corresponding to the sender of the digital key management request; Parsing the encrypted data to obtain an encrypted data packet and a dynamic key; Decrypting the encrypted data packet according to the target key to obtain a target digital key certificate; wherein the target key is obtained by combining the static key and the dynamic key; Extracting a target vehicle identifier from the target digital key certificate, and determining the target vehicle identifier as the target identifier; and / or, If the management operation represents a non-key creation operation and the sender identity represents a terminal device cloud service, the processing method includes: mapping the target key identifier according to a preset third mapping relationship between the vehicle identifier and the digital key identifier, and determining the target vehicle identifier to which the target key identifier is mapped as the target identifier; and / or, If the management operation represents a non-key creation operation and the sender identity represents a terminal device cloud service, the processing method includes: determining the target key identifier as the target identifier.

[0012] In some embodiments, if the management operation represents a key creation operation, the target field further includes the key identification field, the original extracted data includes the encrypted data and the target key identification; the method further includes: The target key identifier and the target vehicle identifier are associated and stored to obtain the third mapping relationship.

[0013] In some embodiments, the digital key management request is forwarded to the target object via the target processing node; the target processing node is one of a plurality of candidate processing nodes in a preset processing node cluster; the method further includes: Monitoring data transmission quality of a target connection; the target connection is used to forward the digital key management request from the target processing node to the target object; The target processing node is switched within the processing node cluster according to the data transmission quality.

[0014] In a second aspect, an embodiment of the present application further provides a digital key management device, the digital key management device comprising: An acquisition module, configured to respond to a digital key management request; A parsing module, used to parse the digital key management request according to the target digital key protocol to obtain a target identifier; the target identifier includes an identifier representing a target vehicle and / or a target digital key; A mapping module, used to determine a target object corresponding to the target identifier according to a preset target mapping relationship; the target object includes a target vehicle cloud service and / or a target terminal device cloud service; the target mapping relationship includes a first mapping relationship between the vehicle identifier and the vehicle cloud service and a second mapping relationship between the digital key identifier and the terminal device cloud service; A forwarding module is used to forward the digital key management request to the target object.

[0015] In a third aspect, an embodiment of the present application also provides a vehicle, comprising a processor and a memory, wherein the memory is used to store instructions, and the processor is used to call the instructions in the memory so that the vehicle executes the digital key management method as described in the first aspect.

[0016] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on a processor, the processor executes the digital key management method as described in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 The present invention is a flowchart of the steps of a digital key management method provided according to an embodiment of the present application.

[0018] Figure 2 A flowchart of a sub-step of a digital key management method provided according to an embodiment of the present application.

[0019] Figure 3 A flowchart of a sub-step of a digital key management method provided according to an embodiment of the present application.

[0020] Figure 4 A flowchart of a sub-step of a digital key management method provided according to an embodiment of the present application.

[0021] Figure 5 A flowchart of a sub-step of a digital key management method provided according to an embodiment of the present application.

[0022] Figure 6 A schematic diagram of the structure of a digital key management device provided according to an embodiment of the present application.

[0023] Figure 7 It is a schematic diagram of the structure of a vehicle provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0024] In order to more clearly understand the above-mentioned purposes, features and advantages of the present application, the present application is described in detail below in conjunction with the accompanying drawings and specific implementation methods. It should be noted that the implementation methods of the present application and the features in the implementation methods can be combined with each other without conflict.

[0025] In the following description, many specific details are set forth to facilitate a full understanding of the present application. The described implementations are only part of the implementations of the present application, rather than all the implementations.

[0026] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein in the specification of this application are only for the purpose of describing specific embodiments and are not intended to limit this application.

[0027] It should be further noted that, in this article, the terms "comprises", "includes" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0028] In this application, "at least one" means one or more, and "more than one" means two or more than two. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The terms "first", "second", "third", "fourth", etc. (if any) in the specification, claims and drawings of this application are used to distinguish similar objects, rather than to describe a specific order or sequence.

[0029] In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0030] In related technologies, mobile phones, smart watches and other terminal devices are used as digital key devices, and the digital key devices interact with the vehicle to achieve control of the vehicle. In order to facilitate the monitoring and management of the life cycle of the digital key, the terminal device and the vehicle correspond to cloud services respectively, and the management and monitoring of the life cycle of the digital key are achieved through the interaction between the terminal device cloud service and the vehicle cloud service. For example, the terminal device cloud service can send a key creation request to the vehicle cloud service. Optionally, the terminal device cloud service and the vehicle cloud service can also send digital key management requests such as deleting the key, suspending the key, and restoring the key.

[0031] Furthermore, in the process of implementing the prior art, the inventors found that more and more car manufacturers will develop multiple sub-brands, and one sub-brand corresponds to one cloud service. This means that when the terminal device is connected with the car manufacturer, the terminal device cloud service needs to be connected with the cloud services corresponding to multiple sub-brands one by one, thereby increasing the connection cost and complexity of terminal device parties such as mobile phone manufacturers, and affecting the efficiency of digital key management.

[0032] From the above, it can be seen that there is currently a problem of low efficiency in digital key management.

[0033] In view of this, the embodiments of the present application provide a digital key management method, device, vehicle and computer-readable storage medium, which can improve the management efficiency of digital keys, and are particularly suitable for digital key management in multi-terminal device cloud service and multi-vehicle cloud service scenarios.

[0034] See also Figure 1 , which is a flowchart of the steps of the digital key management method provided in one embodiment of the present application. According to different requirements, the order of the steps in the flowchart can be changed, and some steps can be omitted. The embodiment of the present application may be based on an electronic device, which may include a vehicle, a terminal device, a middleware device, and the like. Among them, the terminal device may include a mobile phone, a tablet computer, a smart watch, and other devices with certain data storage, data processing, and communication capabilities. The middleware device may include devices such as a gateway that have certain data storage, data processing, and communication capabilities. The following embodiment takes the electronic device as a gateway as an example to illustrate the digital key management method of the embodiment of the present application.

[0035] See also Figure 1 As shown, the digital key management method may include the following steps: Step 101: Respond to a digital key management request.

[0036] The digital key management request is used to request to perform a digital key management operation of a target type. The target type may be one of multiple optional types specified by the target digital key protocol corresponding to the digital key management request, such as creating a key, deleting a key, restoring a key, etc.

[0037] After detecting or receiving the digital key management request, a request message corresponding to the digital key management request is obtained. Specifically, the request message may be a request message sent by a sender of the digital key management request, wherein the sender of the digital key management request may be a vehicle.

[0038] Step 102: Parse the digital key management request to obtain a target identifier; the target identifier includes an identifier representing a target vehicle and / or a target digital key.

[0039] Among them, considering that the digital key management request generally follows a specific protocol standard, the digital key management request can be parsed according to the target digital key protocol corresponding to the digital key management request to obtain the target identifier. The target digital key protocol can be one of the existing digital key protocols, and the existing digital key protocols can include CCC (Car Connectivity Consortium) protocol, ICCE (Intelligent Car Connectivity Industry Ecosystem) protocol, ICCOA (Intelligent Car Connectivity Open Alliance) protocol, etc., and the embodiments of the present invention are not limited to this. Before responding to the digital key management request, the gateway can pre-announce the target digital key protocol that the gateway can respond to and adapt, such as specifying that the gateway supports the CCC protocol. Optionally, the target digital key protocol can also be negotiated in advance through the gateway or with the potential request sender.

[0040] Optionally, the target digital key protocol can also be obtained by analyzing the message format of the request message. Considering that the format standards of request messages specified by different digital key protocols generally differ, the message format of the received request message can be matched with the message format specified by each candidate digital key protocol, and the candidate digital key protocol that matches the message format can be determined as the target digital key protocol.

[0041] Considering that different digital key protocols have different provisions for the content and form of request messages corresponding to various types of digital key management operations, the content includes the parameters that must and / or can be included in the request message, and the form includes the combination of the aforementioned parameters and the recording method. Therefore, in an embodiment of the present application, the request message can be parsed and the parsing result can be converted according to the combination and conversion method of the parameters specified in the protocol standard corresponding to the digital key management request to obtain the target identifier. The conversion can include encryption and decryption.

[0042] In some embodiments, see Figure 2 , step 102 further includes: Step 1021: Parse the digital key management request to obtain the request type and request parameters of the digital key management request.

[0043] Among them, considering the digital key management operations performed for different requesters and / or different requests, the way of writing the target identifier into the request parameters and constructing the request message according to the request parameters may be different. For example, there are differences in the content and construction method of the request message corresponding to the digital key creation operation and the digital key deletion operation. Correspondingly, the content and construction method of the request message sent by the terminal device cloud service such as the mobile phone cloud service may be different from that sent by the vehicle cloud service. Therefore, in an embodiment of the present application, the request type includes the identity type of the sender of the digital key management request and the type of operation requested to be performed. According to the location where the information of the request sender and the information of the type of operation requested to be performed specified by the target digital key protocol are written, the request type is extracted from the request message, and the information in the request message other than the characterization of the request type is determined as the request parameter. Optionally, the request message includes a request path, a request header, and a request body, and the content in the request body can be used as a request parameter. For example, the target digital key protocol can be a CCC protocol, the type of operation requested to be performed is determined according to the request path, and the identity information of the request sender is determined according to the request header of the request message. For example, when the request path is " / keyApi / v1 / trackKey", it includes "trackKey" indicating key tracking, thus indicating that the request is a request to create a key, and the identifier of the OEM (Original Equipment Manufacturer) server that sends the request is extracted from the "x-requestId" (required identifier) ​​and / or "x-device-oemId" (terminal device server identifier) ​​in the request header. The corresponding terminal device cloud service or vehicle cloud service can be uniquely determined based on the server identifier. Correspondingly, when the request path is " / keyApi / v1 / manageKey", it includes "manageKey" indicating the management of the life cycle of the digital key, which is a non-key creation request, such as a possible key deletion request, and the information under the keyID field is extracted from the request body as the target key identifier.

[0044] Step 1022: Parse the request parameters according to a target parsing method to obtain the target identifier; wherein the target parsing method is determined according to the request type.

[0045] Among them, considering that according to the provisions of the target digital key protocol, the digital key management operations performed for different requesters and / or different requests, the methods of writing the target identifier into the request parameters and constructing the request message according to the request parameters may be different, therefore, the target parsing method for the request parameters is determined according to the request type, so as to disassemble and convert the request parameters to obtain the target identifier. The method of writing the target identifier into the request parameters under the request type is reversed to obtain the target parsing method. For example, the reverse operation for encryption includes decryption, and the reverse operation for the combined parameters includes disassembling the parameters.

[0046] Optionally, the request type includes the management operation requested by the digital key management request and the identity of the sender who initiated the digital key management request. For example, the management operation may be a key creation operation, a key deletion operation, a key recovery operation, a key loss report operation, etc. The sender identity may be a terminal device cloud service or a vehicle cloud service.

[0047] The target parsing method includes an extraction method and a processing method; the extraction method is determined according to the management operation; the processing method is determined according to the sender identity and / or the management operation. The extraction method is used to extract information under the field related to the target identifier from the request parameters, and the processing method is used to process the information under the field related to the target identifier to obtain the target identifier. The field related to the target identifier may include the field where the target identifier is stored.

[0048] In some embodiments, Figure 3 As shown, the target identification determination process also includes: Step 110: extracting field value information of the request parameter according to the extraction method to obtain original extracted data. The target identification related fields are determined according to the management operation, and the field value information under the target identification related fields is extracted from the request parameters as the original extracted data.

[0049] Specifically, the extraction method defines a target field from which the field value information is derived. The field value information under the target field is the original extracted data. If the management operation represents a key creation operation, the target field includes an encrypted data field, and the original extracted data includes encrypted data.

[0050] Taking the target digital key protocol as the CCC protocol as an example, the encrypted data field can be the "keyData" field representing the encrypted data. The "keyData" field includes the "version" representing the version, the "ephemeralPublicKey" representing the sender's temporary public key, the "publicKeyHash" field representing the key protocol public key fingerprint of the receiver, and the Base64-encoded "data" field representing the encrypted data. Among them, the encrypted data includes the "data" field and the field value information under the "ephemeralPublicKey" field.

[0051] Optionally, if the management operation represents a non-key creation operation, the target field includes a key identification field, and the original extracted data includes a target key identification.

[0052] Taking the target digital key protocol as the CCC protocol as an example, the key identification field can be the "keyID" field, and the target key identification is the field value under "keyID", such as 4938205039594.

[0053] Step 120: Determine the target identifier according to the original extracted data and the processing method.

[0054] Among them, the method of extracting the target identifier from the original data is determined according to the management operation. Optionally, considering that the generation of some types of digital key management request messages needs to be signed according to the identity information of the request sender, such as encrypting the target identifier according to the key of the request sender, therefore, in some embodiments, the processing method can also be determined according to the management operation and the sender's identity.

[0055] Specifically, if the management operation represents a key creation operation, in some embodiments, Figure 4 As shown, the processing method includes: Step 1201: Determine the static key corresponding to the sender of the digital key management request according to the sender identity.

[0056] Among them, the identification information of the sender of the digital key management request is determined according to the sender identity, and a query is performed in the preset static key library according to the identification information to obtain the static key used by the sender of the current digital key management request. The static key library stores static keys corresponding to multiple candidate identity identifiers. Specifically, the static key can be the static part of the encryption certificate used by the sender in accordance with the provisions of the target digital key management protocol, and the dynamic part of the encryption certificate will be temporarily generated with each digital key management request, such as the dynamic part can be randomly generated each time a request is sent. In order to improve the efficiency of digital key management, it is possible to first negotiate with the terminal device cloud service and / or the vehicle cloud service to obtain the corresponding static key, so that in the subsequent digital key management process, the sender only needs to send the dynamically changing key part. It should be noted that some digital key management protocols have restrictions on the identity of the sender of the key creation request. For example, taking the target digital key protocol as the CCC protocol, the CC protocol stipulates that the terminal device cloud service can initiate a digital key creation request. Therefore, in this case, it is only necessary to conduct a preliminary negotiation with the terminal device cloud service to obtain a static key that is agreed upon, so as to facilitate the subsequent parsing of the encrypted data part of the key creation request sent by the terminal device cloud service in accordance with the agreed method.

[0057] Step 1202: Parse the encrypted data to obtain an encrypted data packet and a dynamic key.

[0058] Among them, the encrypted data packet is an encrypted data packet, which includes actual parameters for performing digital key management operations. The operation parameters include the target identification dynamic key, which is a dynamic key dynamically generated with the digital key request. Taking the target digital key protocol as the CCC protocol as an example, the encrypted data includes the "data" field and the field value information under the "ephemeralPublicKey" field. Among them, the field value information under the "data" field is extracted to obtain an encrypted data packet. The field value information under the "ephemeralPublicKey" field is extracted to obtain a dynamic key.

[0059] Step 1203: Decrypt the encrypted data packet according to the target key to obtain a target digital key certificate; wherein the target key is obtained by combining the static key and the dynamic key.

[0060] According to the provisions of the target digital key protocol, the static key and the dynamic key are combined to obtain the target key, and the encrypted data packet is decrypted according to the target key to obtain the target digital key certificate. Taking the target digital key protocol as the CCC protocol as an example, the target digital key certificate can be a Digital Key Certificate.

[0061] Step 1204: extract the target vehicle identifier from the target digital key certificate, and determine the target vehicle identifier as the target identifier.

[0062] Specifically, the target certificate format is determined according to the target digital key protocol, and the target digital key certificate is parsed according to the target certificate format to obtain the target vehicle identification. Taking the target digital key protocol as the CCC protocol as an example, the target certificate can be an X.509 certificate, and the target vehicle identification can be the field value information under the "vehicleId" field stored in the extended field of the target digital key certificate. Optionally, vehicleId can be composed of the car manufacturer brand number, region, and vehicle unique identification.

[0063] In some embodiments, if the management operation represents a non-key creation operation and the sender identity represents a terminal device cloud service, the processing method includes: The target key identifier is mapped according to a preset third mapping relationship between the vehicle identifier and the digital key identifier, and the target vehicle identifier to which the target key identifier is mapped is determined as the target identifier.

[0064] Among them, when the terminal cloud service manages the life cycle of the digital key that has been created, it generally only needs to specify the digital key identifier it wants to manage, and considering that more and more OEMs correspond to multiple vehicle sub-brands, and each vehicle sub-brand manages a large number of digital keys through the corresponding cloud service, therefore, in an embodiment of the present invention, in order to reduce the connection cost between the terminal device cloud service and multiple vehicle cloud services, the third mapping relationship between the vehicle identifier and the digital key identifier is maintained, and the target key identifier extracted from the request message is mapped to the target vehicle identifier according to the third mapping relationship, so as to query the corresponding vehicle cloud service.

[0065] Wherein, in some embodiments, if the management operation represents a key creation operation, the target field further includes the key identification field, and the original extracted data includes the encrypted data and the target key identification; the process of determining the third mapping relationship further includes: The target key identifier and the target vehicle identifier are associated and stored to obtain the third mapping relationship.

[0066] Taking into account that the request message sent by the terminal device cloud service generally only specifies the target digital key identifier it wants to manage, the terminal device cloud service is generally not directly responsible for maintaining the mapping relationship between the digital key identifier and the vehicle cloud service to which the digital key identifier belongs. When the vehicle cloud services corresponding to multiple different brands belong to the same OEM, the mapping relationship between the digital key and the vehicle cloud service is more complex and massive. Therefore, in an embodiment of the present application, in order to reduce the docking workload of the terminal device and the vehicle, after detecting the key creation request, the target key identifier and the target vehicle identifier are also associated and stored to obtain a third mapping relationship, so as to facilitate the subsequent mapping of the target key identifier to the corresponding target vehicle identifier, thereby forwarding the digital key management request to the vehicle cloud service corresponding to the target vehicle identifier.

[0067] In some embodiments, if the management operation represents a non-key creation operation and the sender identity represents a terminal device cloud service, the processing method includes: determining the target key identifier as the target identifier.

[0068] Since the security requirements for non-key creation operations are lower than those for key creation operations, the structure of the request message for non-key creation operations is also simpler. Taking the target digital key protocol as the CCC protocol as an example, the key identification field can be the "keyID" field, and the target key identification is the field value under "keyID", such as 4938205039594. The extracted target key identification is used as the target identification.

[0069] Step 103: Determine the target object corresponding to the target identifier according to a preset target mapping relationship; the target object includes a target vehicle cloud service and / or a target terminal device cloud service; the target mapping relationship includes a first mapping relationship between the vehicle identifier and the vehicle cloud service and a second mapping relationship between the digital key identifier and the terminal device cloud service.

[0070] Among them, the adapted mapping relationship is selected from the first mapping relationship and the second mapping relationship according to the type of the target identifier, and the adapted mapping relationship can map the target identifier to the cloud service. For example, when the target identifier represents the target vehicle, the first mapping relationship is used, and when the target identifier represents the target digital key, the second mapping relationship is used for mapping.

[0071] Step 104: Forward the digital key management request to the target object.

[0072] The digital key management request is forwarded to the corresponding target object through the gateway, eliminating the need for a lot of docking work between the terminal device cloud service and the vehicle cloud service, thereby improving the management efficiency and reliability of the digital key life cycle.

[0073] In some embodiments, the digital key management request is forwarded to the target object via the target processing node; the target processing node is one of a plurality of candidate processing nodes in a preset processing node cluster. Considering that the network performance of the processing node may change dynamically, such as Figure 5 As shown, step 104 also includes: Step 1041: Monitor the data transmission quality of the target connection; the target connection is used to forward the digital key management request from the target processing node to the target object.

[0074] The data transmission quality can be determined by detecting the target connection in a preset network health detection method. It is understandable that after determining the target object, a target connection is established between the target processing node and the target object to forward the digital key management request to the target object through the target connection, wherein the target processing node can be implemented based on the aforementioned gateway, vehicle, or one of the terminal devices as a digital key device.

[0075] Optionally, when establishing a target connection, in order to provide a more personalized and flexible forwarding solution for digital key management requests, the corresponding target processing node can also be determined based on the identity information of the sender of the digital key management request. Among them, the corresponding target transmission quality can be determined based on the identity information of the sender, and based on the target transmission quality and the current transmission quality of each candidate processing node, the candidate processing node that can meet the target transmission quality is selected as the target processing node. Specifically, the transmission demand influencing factors such as the sender's payment type, importance, and historical transmission quality can be determined based on the sender's identity information, and the target transmission quality can be determined based on the transmission demand influencing factors.

[0076] Step 1042: Switch the target processing node within the processing node cluster according to the data transmission quality.

[0077] The data transmission quality is compared with a preset transmission quality threshold, and when the data transmission quality is greater than the transmission quality threshold, a candidate processing node that can meet the transmission quality threshold is selected as a new target processing node based on the current data transmission quality of multiple candidate processing nodes. For example, the candidate processing node with the highest current data transmission quality is determined as the target processing node.

[0078] It should be noted that the processing node cluster provides a forwarding service for digital key management requests as a whole, that is, for the sender of the digital key management request, the switching of the processing node is imperceptible.

[0079] Please refer to Figure 6 , is a schematic diagram of the hardware structure of the digital key management device 20 provided in the embodiment of the present application. Figure 6 As shown, the digital key management device 20 may include: The acquisition module 201 is used to respond to a digital key management request. The parsing module 202 is used to parse the digital key management request according to the target digital key protocol to obtain a target identifier; the target identifier includes an identifier representing a target vehicle and / or a target digital key. Mapping module 203 is used to determine the target object corresponding to the target identifier according to a preset target mapping relationship; the target object includes a target vehicle cloud service and / or a target terminal device cloud service; the target mapping relationship includes a first mapping relationship between the vehicle identifier and the vehicle cloud service and a second mapping relationship between the digital key identifier and the terminal device cloud service.

[0080] The forwarding module 204 is configured to forward the digital key management request to the target object.

[0081] Please refer to Figure 7 , is a schematic diagram of the hardware structure of the vehicle 30 provided in the embodiment of the present application. Figure 7 As shown, the vehicle 30 may include a processor 301 and a memory 302. The memory 302 is used to store one or more computer programs 303. The one or more computer programs 303 are configured to be executed by the processor 301. The one or more computer programs 303 include instructions, and the above instructions can be used to implement the above digital key management method in the vehicle 30.

[0082] It is understood that the structure shown in this embodiment does not constitute a specific limitation on the vehicle 30. In other embodiments, the vehicle 30 may include more or fewer components than shown, or combine some components, or separate some components, or arrange the components differently.

[0083] The processor 301 may include one or more processing units, for example, the processor 301 may include an application processor (AP), a modem, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0084] The processor 301 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 301 is a cache memory. The memory may store instructions or data that the processor 301 has just used or circulated. If the processor 301 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 301, and thus improves the efficiency of the system.

[0085] In some embodiments, the processor 301 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a SIM interface, and / or a USB interface, etc.

[0086] In some embodiments, the processor 301 is used to execute acceleration schemes such as single instruction multiple data (SIMD) and very long instruction word (VLIW).

[0087] In some embodiments, the memory 302 may include a high-speed random access memory and may also include a non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) card, a flash card (Flash Card), at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0088] This embodiment also provides a computer-readable storage medium, which stores computer instructions. When the instructions are executed on a processor, the vehicle executes the above-mentioned related method steps to implement the digital key management method in the above-mentioned embodiment.

[0089] Among them, the digital key management device, vehicle, and computer-readable storage medium provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0090] In practical applications, the above functions can be distributed to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0091] In several embodiments provided in the present application, the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are schematic. For example, the division of the modules or units is a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0092] The unit described as a separate component may or may not be physically separated, and the component shown as a unit may be one physical unit or multiple physical units, that is, it may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiment.

[0093] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0094] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program code.

[0095] The above description is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application should be included in the protection scope of the present application.

Claims

1. A digital key management method, characterized in that: The method comprises: Responding to a digital key management request; Parsing the digital key management request to obtain a target identifier; the target identifier includes an identifier representing a target vehicle and / or a target digital key; Determine the target object corresponding to the target identifier according to a preset target mapping relationship; the target object includes a target vehicle cloud service and / or a target terminal device cloud service; the target mapping relationship includes a first mapping relationship between the vehicle identifier and the vehicle cloud service and a second mapping relationship between the digital key identifier and the terminal device cloud service; The digital key management request is forwarded to the target object.

2. The method according to claim 1, characterized in that The step of parsing the digital key management request to obtain a target identifier includes: Parsing the digital key management request to obtain a request type and request parameters of the digital key management request; The request parameters are parsed according to a target parsing method to obtain the target identifier; wherein the target parsing method is determined according to the request type.

3. The method according to claim 2, characterized in that The request type includes the management operation requested by the digital key management request and the identity of the sender of the digital key management request; the target parsing method includes an extraction method and a processing method; the extraction method is determined according to the management operation; The processing method is determined according to the sender identity and / or the management operation; The process of determining the target identifier includes: Extracting field value information of the request parameter according to the extraction method to obtain original extracted data; The target identifier is determined according to the original extracted data and the processing method.

4. The method according to claim 3, characterized in that The extraction method defines a target field that is the source of the field value information; wherein, if the management operation represents a key creation operation, the target field includes an encrypted data field, and the original extracted data includes encrypted data; if the management operation represents a non-key creation operation, the target field includes a key identification field, and the original extracted data includes a target key identification.

5. The method according to claim 4, characterized in that If the management operation represents a key creation operation, the processing method includes: Determine, according to the sender identity, a static key corresponding to the sender of the digital key management request; Parsing the encrypted data to obtain an encrypted data packet and a dynamic key; Decrypting the encrypted data packet according to the target key to obtain a target digital key certificate; wherein the target key is obtained by combining the static key and the dynamic key; Extracting a target vehicle identifier from the target digital key certificate, and determining the target vehicle identifier as the target identifier; and / or, If the management operation represents a non-key creation operation and the sender identity represents a terminal device cloud service, the processing method includes: mapping the target key identifier according to a preset third mapping relationship between the vehicle identifier and the digital key identifier, and determining the target vehicle identifier to which the target key identifier is mapped as the target identifier; and / or, If the management operation represents a non-key creation operation and the sender identity represents a terminal device cloud service, the processing method includes: determining the target key identifier as the target identifier.

6. The method according to claim 5, characterized in that If the management operation represents a key creation operation, the target field further includes the key identification field, and the original extracted data includes the encrypted data and the target key identification; the method further includes: The target key identifier and the target vehicle identifier are associated and stored to obtain the third mapping relationship.

7. The method according to any one of claims 1 to 6, characterized in that: The digital key management request is forwarded to the target object through a target processing node; the target processing node is one of a plurality of candidate processing nodes in a preset processing node cluster; the method further includes: Monitoring data transmission quality of a target connection; the target connection is used to forward the digital key management request from the target processing node to the target object; The target processing node is switched within the processing node cluster according to the data transmission quality.

8. A digital key management device, characterized in that: The digital key management device comprises: An acquisition module, configured to respond to a digital key management request; A parsing module, used to parse the digital key management request to obtain a target identifier; the target identifier includes an identifier representing a target vehicle and / or a target digital key; A mapping module, used to determine a target object corresponding to the target identifier according to a preset target mapping relationship; the target object includes a target vehicle cloud service and / or a target terminal device cloud service; the target mapping relationship includes a first mapping relationship between the vehicle identifier and the vehicle cloud service and a second mapping relationship between the digital key identifier and the terminal device cloud service; A forwarding module is used to forward the digital key management request to the target object.

9. A vehicle, comprising a processor and a memory, characterized in that: The memory is used to store instructions, and the processor is used to call the instructions in the memory, so that the vehicle executes the digital key management method according to any one of claims 1 to claim 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and when the computer instructions are executed on a processor, the processor executes the digital key management method according to any one of claims 1 to 7.

Images