Terminal device and method of processing data for terminal device
Patent Information
- Application Number
- IN202344072716
- Authority / Receiving Office
- IN · IN
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2023-03-24
- Filing Date
- 2023-10-25
- Publication Date
- 2026-10-26
- Estimated Expiration
- 2043-10-25
AI Technical Summary
Current digital vehicle key solutions have limited applicability and high configuration costs due to the need for specific terminal device components supporting proprietary protocols, restricting compatibility and increasing deployment costs.
A terminal device equipped with a communication device that detects the presence of public protocol components and communicates with target parties using public protocols like CCC or ICCOA, enabling digital vehicle key functions without requiring native system support, thereby reducing configuration costs and expanding compatibility.
The solution allows for the implementation of digital vehicle key functions across various terminal devices, even those without native support for public protocols, reducing deployment costs and enhancing user experience by expanding the scope of application for public protocols.
Abstract
Description
[0001] The disclosure relates to the field of mobile terminal technologies, in particular to aterminal device and a method of processing data for a terminal device.BACKGROUND
[0002] A terminal device used as a vehicle key is a popular technology that has emerged inrecent years, such a function is also called a digital vehicle key. Unlike traditional physical vehiclekeys, the digital vehicle key enables a user to place a mobile terminal device near a vehicle doorto lock and unlock the door. It may also be used to start the vehicle by integrating a vehicle keyfunction in a mobile terminal device. Currently, some vehicle manufacturers and mobile terminalmanufacturers have jointly developed solutions for digital vehicle keys. However, these solutionsstill have low applicability and relatively high configuration costs.SUMMARY
[0003] To overcome the problems in the related art, the disclosure provides a terminal deviceand a method of processing data for the terminal device.
[0004] According to a first aspect of embodiments the disclosure, a terminal device isprovided. The terminal device includes:
[0005] a communication device, configured to detect whether a native system of the terminaldevice comprises components for adapting a public protocol of a digital vehicle key, andcommunicate with a target communication party based on the public protocol in case of absenceof at least one of the components in the native system, in which the target communication partyis a participant of the public protocol.
[0006] Optionally, the communication device includes: a digital key module, a localapplication module, a digital key framework (DKF) module and a key management module.
[0007] The digital key module is capable of communicating with a vehicle server and isconfigured to implement functions of a vehicle manufacturer application specified in the publicprotocol.
[0008] The local application module is capable of communicating with a terminal deviceserver and is configured to implement functions of a terminal device manufacturer applicationspecified in the public protocol.
[0009] The DKF module is configured to implement functions of a DKF specified in the
[0010] The key management module is configured to implement functions of a digital keyprogram specified in the public protocol.
[0011] Optionally, the communication device includes an encryption white box module,configured to store data of the digital vehicle key.
[0012] Optionally, the local application module is configured to communicate with theterminal device server based on a terminal device service module in the vehicle server.
[0013] Optionally, the public protocol is a public protocol based on certificate authentication,the target communication party includes the vehicle server and the terminal device server, theterminal device is configured to, in response to receiving a key sharing request, communicate withthe vehicle server via the digital key module and communicate with the terminal device server viathe local application module, rendering that an authentication step for key sharing is completed,and a shared digital vehicle key is obtained.
[0014] Optionally, the public protocol is a Car Connectivity Consortium (CCC) protocol oran Intelligent Car Connectivity Open Alliance (ICCOA) protocol.
[0015] Optionally, the target communication party includes a vehicle, and the terminaldevice is configured to establish a secure channel by performing public protocol basedcommunication with the vehicle through the communication device, and send a target controlinstruction to the vehicle through the secure channel, in which the target control instruction isconfigured to control the vehicle to implement a target action.
[0016] According to a second aspect of embodiments the disclosure, a method of processingdata for a terminal device, performed by the terminal device according to any embodiment of thefirst aspect of the disclosure, is provided. The method includes:
[0017] detecting whether a native system of the terminal device includes components foradapting a public protocol of a digital vehicle key; and
[0018] communicating with a target communication party based on the public protocol incase of absence of at least one of the components in the native system, in which the targetcommunication party is a participant of the public protocol.
[0019] Optionally, the public protocol is a public protocol based on certificate authentication,the target communication party includes a vehicle server and a terminal device server, andcommunicating with the target communication party based on the public protocol includes:
[0020] in response to receiving a key sharing request, communicating with the vehicle servervia a digital key module in a communication device, and communicating with the terminal deviceserver via a local application module in the communication device, rendering that anauthentication step for key sharing is completed, and a shared digital vehicle key is obtained.
[0021] Optionally, the target communication party includes a vehicle, and communicating
[0022] establishing a secure channel by performing public protocol based communication withthe vehicle through the communication device; and
[0023] sending a target control instruction to the vehicle through the secure channel, in whichthe target control instruction is configured to control the vehicle to implement a target action.
[0024] In the above technical solutions, the communication device is provided in the terminaldevice. The communication device may detect whether the native system of the terminal deviceincludes the components for adapting the public protocol of the digital vehicle key, andcommunicates with the target communication party based on the public protocol in case of absenceof at least one of the components in the native system. The target communication party is aparticipant of the public protocol.
[0025] Therefore, the terminal device can perform the public protocol based communicationwith the target communication party through the communication device, to implement functionsof the digital vehicle key based on the public protocol. In this way, the public protocol can beapplied to various terminal devices, to expand the scope of application of the public protocol.Moreover, since the terminal devices that do not support the public protocol can also perform thepublic protocol based communication through the communication device, and further implement thefunctions of the digital vehicle key. Therefore, the terminal device may not be configured withcomponents for implementing the digital vehicle key based on a private protocol, deploymentcosts of the digital vehicle key are reduced.
[0026] It should be understood that the above general description and the following detaileddescription are only exemplary and explanatory, and cannot limit the disclosure.BRIEF DESCRIPTION OF THE DRAWINGS
[0027] The accompanying drawings, which are incorporated in and constitute a part of thisspecification, illustrate embodiments consistent with the disclosure and, together with thedescription, serve to explain the principles of the disclosure.
[0028] FIG. 1 is a structural diagram of a digital vehicle key system based on an ICCOAprotocol according to an embodiment of the present disclosure.
[0029] FIG. 2 is a block diagram of a terminal device according to an embodiment of thepresent disclosure.
[0030] FIG. 3 is a block diagram of a communication device according to an embodiment ofthe present disclosure.
[0031] FIG. 4 is a block diagram of a communication device and an encryption white boxaccording to an embodiment of the present disclosure.
[0032] FIG. 5 is a flowchart of activating a digital vehicle key according to an embodiment
[0033] FIG. 6 is a structural diagram of an ICCOA digital vehicle key according to anembodiment of the present disclosure.
[0034] FIG. 7 is a flowchart of key sharing according to an embodiment of the presentdisclosure.
[0035] FIG. 8 is a flowchart of standard authentication of a mobile terminal and a vehicleaccording to an embodiment of the present disclosure.
[0036] FIG. 9 is a flowchart of a method of processing data for a terminal device accordingto an embodiment of the present disclosure.DETAILED DESCRIPTION
[0037] Reference will now be made in detail to illustrative embodiments, examples of whichare illustrated in the accompanying drawings. The following description refers to theaccompanying drawings in which the same numbers in different drawings represent the same orsimilar elements unless otherwise represented. The implementations set forth in the followingdescription of illustrative embodiments do not represent all implementations consistent with thedisclosure. Instead, they are merely examples of apparatuses and methods consistent with aspectsrelated to the disclosure as recited in the appended claims.
[0038] Before introducing a terminal device and a method of processing data for a terminaldevice of the present disclosure, an application scenario of the present disclosure is introducedfirstly.
[0039] The terminal device as a vehicle key is a popular technology that has emerged inrecent years, and such a function is also called a digital vehicle key. Unlike traditional physicalvehicle keys, the digital vehicle key enables functions such as opening a door and starting thevehicle by integrating a vehicle key function in a mobile terminal device.
[0040] For example, in some scenarios, a vehicle company can develop a digital vehicle keybased on a private protocol. By encapsulating related data of the private protocol in an applicationof the vehicle company, the terminal device installed with the application can interact with avehicle and a vehicle server based on the private protocol, to realize functions of the digital vehiclekey, such as vehicle control, and key sharing, etc. In order to realize the functions of the digitalvehicle key, the application is required to run on the terminal device, such as running onforeground, or keeping alive on background, which consumes more resources of the terminaldevice. The vehicle server may be a server capable of communicating with a vehicle. The vehicleserver may be a server capable of communicating with a vehicle.
[0041] Therefore, some vehicle manufacturers and mobile terminal manufacturers havejointly developed a solution of the digital vehicle key, i.e., a solution of a digital vehicle key basedfunctions of the digital vehicle key based on an underlying operating system.
[0042] Taking an ICCOA public protocol as an example, FIG. 1 illustrates a structuraldiagram of a digital vehicle key system based on an ICCOA protocol. In the solution of the digitalvehicle key based on the public protocol, related operations of the digital vehicle key can beencapsulated as a digital key framework (DKF). The DKF can provide various ApplicationProgramming Interfaces (APIs) for upper-layer applications to call, such as devices pairing, keylife cycle management, key unlocking, locking and sharing, and vehicle control, etc. By settingthe DKF at the system level, the terminal device can implement the functions of the digital vehiclekey based on the underlying operating system, which has advantages of low resource consumptionand better user experience.
[0043] It should be noted that the public protocol is jointly developed by the vehiclemanufacturer and the mobile terminal manufacturer, therefore, there are restrictions on a type ofthe terminal device. For example, terminal manufacturer A and the vehicle manufacturer jointlydevelop public protocol 1, so that terminal device A1 of terminal manufacturer A can supportpublic protocol 1. However, for terminal device B1 of terminal manufacturer B, it is difficult tosupport public protocol 1, which affects the user experience. For example, in some scenarios,users of the vehicle can include an owner and a friend of the owner, but since the owner usesterminal device A1 which supports public protocol 1 and the friend uses terminal device B1 whichdoes not support public protocol 1, so that the owner cannot share the digital vehicle key to thefriend.
[0044] Therefore, in order to ensure compatibility, vehicle companies generally develop boththe solution of the digital vehicle key based on the private protocol and the solution of the digitalvehicle key based on the public protocol. Both solutions can be configured in the terminal device,which leads to higher development and deployment costs of digital vehicle key solutions.
[0045] Therefore, the disclosure provides a terminal device, which may be a mobile terminaldevice such as a cell phone, a tablet computer, or any other types of terminal device equippedwith digital key functions.
[0046] FIG. 2 is a block diagram of a terminal device according to an embodiment of thepresent disclosure. As illustrated in FIG. 2, the terminal device 10 includes a communicationdevice 100. The communication device 100 is configured to detect whether a native system of theterminal device 10 includes components for adapting a public protocol of a digital vehicle key,and communicate with a target communication party based on the public protocol in case ofabsence of at least one of the components in the native system, in which the target communicationparty is a participant of the public protocol.
[0047] The native system of the terminal device 10 can be a system that the terminal deviceterminal devices, such as an iOS system, a HarmonyOS system, an Android system, etc.,which will not be limited in the disclosure. In order to realize the digital vehicle key based on thepublic protocol, the terminal device may be configured with related components. Thesecomponents can include a security unit, a DKF, a trusted execution environment (TEE), etc., andtheir types can be specifically referred to a relevant description of the public protocol of the digitalvehicle key.
[0048] The communication device 100 may detect whether the native system of the terminaldevice 10 includes the components for adapting the public protocol of the digital vehicle key. Incase of absence of at least one of the components in the native system, the communication device100 may communicate with the target communication party based on the public protocol. Thetarget communication party is the participant of the public protocol.
[0049] The communication device 100 may be presented in the form of software, hardware,or a combination of software and hardware. For example, in a possible implementation, thecommunication device may be presented in the form of a software development kit (SDK). Thepublic protocol may be a public protocol based on a certificate system, such as a CCC (CarConnectivity Consortium) protocol or an ICCOA (Intelligent Car Connectivity Open Alliance)protocol. The public protocol may also be a public protocol based on secret key authentication,such as an Intelligent Car Connectivity Industry Ecosystem Alliance Digital Key System (ICCE)protocol.
[0050] The communication device 100 is described as following by taking the ICCOA publicprotocol as an example.
[0051] FIG. 3 is a block diagram of a communication device according to an embodiment ofthe present disclosure. In a possible implementation, the communication device 100 may includea digital key module 101. The digital key module 101 is capable of communicating with a vehicleserver and is configured to implement functions of a vehicle manufacturer application specifiedin the public protocol.
[0052] The ICCOA protocol specifies that the vehicle manufacturer application needs toprovide a functional interface related to the digital vehicle key to the user. Therefore, the relatedkey management function methods can be encapsulated to obtain the digital key module 101. Thekey management function methods can include key creation, key sharing, key deletion, RemoteKeyless Entry (RKE), etc. The digital key module 101 can also be presented in the form of a SDKand provide an interface of the above key management function methods.
[0053] As illustrated in FIG. 3, in a possible implementation, the communication device 100includes a local application module 102, configured to implement functions of a terminal devicemanufacturer application specified in the public protocol.server. In some implementation scenarios, the local application module 102 may be configured tocommunicate directly with the terminal device server. In some implementation scenarios, aterminal device service module may also be configured in the vehicle server. The local applicationmodule 102 is configured to communicate with the terminal device server based on the terminaldevice service module in the vehicle server. The terminal device server may be a server capableof communicating with a terminal device.
[0055] The ICCOA protocol specifies that the application of the terminal devicemanufacturer needs to provide a functional interface related to the digital vehicle key to the userand performs service processes such as activating, updating, sharing and revoking of the digitalvehicle key. Therefore, the above related functional methods can be encapsulated to obtain thelocal application module 102. The local application module 102 can also be presented in the formof a SDK and provide an interfaces for the service functions such as activating, updating, sharingand revoking of the vehicle keys. The terminal device server may be a server capable ofcommunicating with a terminal device.
[0056] As illustrated in FIG. 3, in a possible implementation, the communication device 100includes a DKF module103 , configured to implement functions of a DKF specified in the publicprotocol.
[0057] For example, operations related to a digital vehicle key Trusted Application (TA) ina digital vehicle key lifecycle can be encapsulated to obtain the DKF module 103. The DKFmodule 103can provide vehicle key management services in the form of an API to the digital keymodule 101 and the local application module 102 for calling. These functions include but notlimited to: devices pairing, key lifecycle management, key unlocking, locking and sharing, vehiclecontrol, etc. The DKF module can also interact with a key management module 104, so that thekey management module 104 can receive and respond to authentication messages sent by vehiclestimely.
[0058] In addition, the DKF module 1030may be configured to perform Bluetooth pairingand establish Bluetooth connection with the vehicle, and the Bluetooth pairing and connectionmay be in a general or customized manner. During interaction with the vehicle, the DKF modulemay also parse and encapsulate a Bluetooth authentication data packet.
[0059] As illustrated in FIG. 3, in a possible implementation, the communication device 100includes a key management module 104, configured to implement functions of a digital keyprogram specified in the public protocol.
[0060] The key management module 104 may include a TA module. The TA module maycall security capability provided by a secure storage unit, so as to construct and store key data.FIG. 4 is a block diagram of a communication device and an encryption white box according toElement (SE), unlike that, the TA module in this disclosure can store the key data by means ofencryption white box 105. In some implementation scenarios, the TA module can also store thekey data through a secure storage technology of the native system of the terminal device. Forexample, in the Android system, the key data can be stored via a key-store (Android secret key)technology.
[0061] In addition, the TA module can be used for data encryption, data decryption andsecurity control in the service processes of pairing, unlocking, locking, sharing, and vehiclecontrol, etc. of the digital vehicle key. In some implementation scenarios, the TA module can alsobe used to verify user identity.
[0062] In some implementation scenarios, the TA module may be constructed with a callinginterface. The key management module 104 may also include a Client Application (CA) module.The CA module may perform TA related functions by calling the interface of the TA module.
[0063] In addition, the communication device 100 may be encapsulated into an applicationin the terminal, which is not limited in the disclosure.
[0064] The terminal device may perform public protocol based communication with thetarget communication party based on the communication device 100.
[0065] For example, in a possible implementation, the public protocol is a public protocolbased on certificate authentication. The terminal device is configured, through the communicationdevice 100, to communicate with the vehicle server, the terminal device server, and the vehicle,to complete the step of activating the digital vehicle key and obtaining the digital vehicle key.
[0066] FIG. 5 is a flowchart of activating a digital vehicle key according to an embodimentof the present disclosure. FIG. 6 is a structural diagram of an ICCOA digital vehicle key accordingto an embodiment of the present disclosure. In the disclosure, the process of activating the digitalvehicle key based on the ICCOA protocol through the communication device may include thefollowing steps.
[0067] At steps 511 to 513, the user may initiate a key activating process through thecommunication device of the terminal device. The user may input pairing information. The pairinginformation may be generated by the vehicle server, and the digital key module in thecommunication device may obtain the pairing information from the vehicle server. It is to be notedthat the vehicle server may also send initial pairing parameters to the vehicle.
[0068] At step 52, the vehicle terminal can interact with the DKF module of the terminaldevice, and perform bidirectional authentication with the terminal device based on anSPAKE2+algorithm, to establish an SPAKE2+secure channel. When the vehicle has been boundto the terminal device of the vehicle owner, the key activating process will stop. When the vehicleis not bound to the terminal device of the vehicle owner, the subsequent processes may continue
[0069] The vehicle (or terminal device) may also check whether a current state has met a keyactivating condition. The condition may be set based on application requirements. At step 53, ina case that the key activating condition is satisfied, the vehicle transmits a vehicle public keycertificate [F] to the terminal device. The vehicle public key certificate [F] includes a vehiclepublic key and a vehicle server CA signature.
[0070] At steps 541 to 543, the key management module of the terminal device can verifythe vehicle public key certificate [F] based on a vehicle server CA certificate [C], which includesa vehicle server CA public key and a trusted CA signature. After successful verification, theterminal device can save the vehicle public key certificate [F]. For example, the terminal devicemay save the vehicle public key certificate to the encryption white box. In addition, the terminaldevice can generate a digital-vehicle-key public-private key pair [K], which includes a digitalvehicle-key public key and a digital-vehicle-key private key. The terminal device can also signthe digital-vehicle-key public key based on a key management module certificate [H], to generatea digital-vehicle-key public key certificate [L]. The key management module certificate [H]includes a CA public key and a CA private key of the key management module, and the digitalvehicle-key public key certificate [L] includes the digital-vehicle-key public key and a keymanagement module CA signature.
[0071] At step 55, the terminal device sends a terminal device server CA certificate [D], akey management module certificate [J] and the digital-vehicle-key public key certificate [L] tothe vehicle sequentially. The terminal device server CA certificate [D] includes a terminal deviceserver CA public key and a vehicle server CA signature. The key management module certificate[J] includes a key management module CA public key and a terminal device server CA signature.
[0072] At step 56, the vehicle sequentially verifies a certificate chain transmitted by theterminal device. The vehicle can verify the terminal device server CA certificate [D] via a vehicleserver CA certificate [G], which includes a vehicle server CA public key and a trusted CAsignature. The vehicle may also verify the key management module certificate [J] via the terminaldevice server CA certificate [D], which includes a terminal device server CA public key and avehicle server CA signature. The vehicle can also verify the digital-vehicle-key public keycertificate [L] by the key management module certificate [J].
[0073] In the case of successful verification, the vehicle can save the digital-vehicle-keypublic key and corresponding information of the digital vehicle key. In this way, the terminaldevice verifies and saves the vehicle public key, which completes generation and verificationsteps of a secret key for an owner's key pairing stage. At this time, the terminal device and thevehicle are successfully paired.
[0074] At step 57, the vehicle sends a status indication to the terminal device for indicating
[0075] At steps 581 to 583, the vehicle synchronizes an activating status of the digital vehiclekey of the vehicle to the vehicle server, and the terminal device sends an activating status of thedigital vehicle key of the terminal device to the terminal device server. The terminal device serversynchronizes the activating status of the digital vehicle key to the vehicle server.
[0076] At step 59, the vehicle server sends a key activating message to notify the owner ofthe vehicle.
[0077] At step 510, first standard authentication is performed between the terminal deviceand the vehicle, and a standard authentication secure channel is established.
[0078] At step 511, in response to a demand to set digital vehicle key service data, the vehiclesends a request of saving the digital vehicle key service data to the terminal device.
[0079] With the above technical solutions, for the terminal device whose native system doesnot support the ICCOA protocol, it is possible to validate the digital vehicle key that is based onthe ICCOA protocol through the communication device, thereby expanding the scope ofapplication of the ICCOA protocol.
[0080] In a possible implementation, the public protocol is a public protocol based oncertificate authentication. The target communication party includes a vehicle server and a terminaldevice server. The terminal device is configured to, in response to receiving a key sharing request,communicate with the vehicle server via the digital key module and communicate with theterminal device server via the local application module, rendering that an authentication step forkey sharing is completed, and a shared digital vehicle key is obtained. In some implementationscenarios, the terminal device can also act as an initiator of key sharing (i.e., terminal device ofthe owner) and share the digital vehicle key to another terminal device.
[0081] The following is an illustration for a process of sharing the digital vehicle key.
[0082] FIG. 7 is a flowchart of key sharing according to an embodiment of the presentdisclosure. As illustrated in FIG. 7, a process of key sharing includes the following steps.
[0083] At step 71, a user can set friend key sharing information, such as a validity period, apermission and other information. In a case that the native system of an owner terminal device,e.g., a terminal device of a vehicle owner, supports the ICCOA protocol, the user can set the friendkey sharing information in an application of a terminal device manufacturer of the owner terminaldevice, the application of the terminal device manufacturer can be, for example, a walletapplication. In a case that the native system of the owner terminal device does not support theICCOA protocol, the user may set the friend key sharing information via the communicationdevice.
[0084] At step 72, the owner terminal device signs the friend key sharing information basedon uses an owner digital-vehicle-key private key and generates a friend key sharing request.terminal device server, and the owner terminal device server forwards the sharing request to thevehicle server.
[0086] At step 74, the vehicle server receives the sharing request and verifies a signature ofthe sharing information based on the owner digital-vehicle-key public key.
[0087] At step 75, after the vehicle server successfully verifies the signature of the sharinginformation, the vehicle server generates an SessionID for a share link. The SessionID may berandomly generated by a random number generator to avoid a risk of incremental prediction.
[0088] At step 76, the vehicle server sends the SessionID for the share link to the ownerterminal device server, and the owner terminal device server forwards the SessionID for the sharelink to the owner terminal device.
[0089] At step 77, after receiving the SessionID for the share link, the owner terminal devicegenerates a share link including the SessionID, such that the owner may share the share link witha friend.
[0090] At step 78, the friend may open the share link through a friend terminal device, e.g.,a terminal device of the friend. In a case that a native system of the friend terminal device supportsthe ICCOA protocol, the friend terminal device may jump to the application of the terminal devicemanufacturer and obtain the friend key sharing information from a friend terminal device serverbased on the SessionID. The friend terminal device server may obtain the friend key sharinginformation from the vehicle server. In addition, in a case that the native system of the friendterminal device does not support the ICCOA protocol, the digital key module may obtain thefriend key sharing information from the friend terminal device server according to the SessionIDwhen the friend terminal device opens the share link.
[0091] At step 79, the vehicle server sends the friend key sharing information to the friendterminal device server, and the friend terminal server forwards the friend key sharing informationto the friend terminal device.
[0092] At step 710, the friend terminal device prompts related information of friend keysharing and continues after the user confirms the related information. When the current friendterminal device already has a key for the corresponding vehicle, the current friend terminal devicemay stop the key sharing process and prompts a corresponding message.
[0093] At step 711, the friend terminal device generates a public key-private key pair of afriend digital vehicle key.
[0094] At step 712, in a case where the native system of the friend terminal device supportsthe ICCOA protocol, the friend terminal device may generate a friend digital-vehicle-key publickey certificate by signing the generated friend digital-vehicle-key public key based on a trustedexecution environment CA. In a case that the native system of the friend terminal device does notkey public key certificate by signing the generated friend digital-vehicle-key public key based onthe key management module in the communication device.
[0095] At step 713, the friend terminal device initiates a transmission request to the friendterminal device server, with transmission contents including the friend digital-vehicle-key publickey certificate, the friend terminal device TEE CA certificate (or the key management module CAcertificate when the native system of the friend terminal device does not support the ICCOAprotocol, and the key management module CA certificate is obtained by signing the keymanagement module CA public key using the friend terminal server CA private key) and thefriend terminal device server CA certificate. The friend terminal device server forwards thetransmission contents to the vehicle server, and the vehicle server forwards the transmissioncontents to the owner terminal device server. After that, the owner terminal device server forwardsthe transmission contents to the owner terminal device.
[0096] At step 714, after receiving the above transmission contents, the owner terminaldevice may verify the friend terminal device server CA certificate with the vehicle server CAcertificate stored in the owner terminal device, and verify the friend terminal device TEE CAcertificate with the friend terminal device server CA certificate, and then verify the friend digitalvehicle-key public key certificate with the friend terminal device TEE CA certificate.
[0097] Alternatively, in a case that the transmission contents include the friend digitalvehicle-key public key certificate, the key management module CA certificate and the friendterminal device server CA certificate, the owner terminal device may verify the friend terminaldevice server CA certificate with the vehicle server CA certificate, and further verify the keymanagement module CA certificate with the friend terminal device server CA certificate, and thenverify the friend digital-vehicle-key public key certificate with the key management module CAcertificate.
[0098] At step 715, after confirming that the above certificate chain is successfully verified,the owner terminal device may obtain a friend digital-vehicle-key public key. In this way, theowner terminal device may sign the friend key sharing information and the friend digital-vehiclekeypublic key by using the owner digital-vehicle-key private key, and generates friend keyauthentication information.
[0099] At step 716, the owner terminal device initiates a transmission request to the ownerterminal device server, and the transmission contents may include the friend key authenticationinformation and the vehicle public key certificate. The owner terminal device server forwards thetransmission contents to the vehicle server, and the vehicle server further forwards thetransmission contents to the friend terminal device server, and then the friend terminal deviceserver forwards the transmission contents to the friend terminal device.vehicle public key certificate, the friend terminal device saves the friend key authenticationinformation and the vehicle public key certificate. The friend key authentication information isused for a first standard authentication between the friend key and the vehicle, and is deleted afterthe authentication is completed. By this way, activating of the friend key is completed.
[00101] The friend terminal device may further synchronize a status of the friend key tothe friend terminal device server, and the friend terminal device server further synchronizes thestatus of the friend key to the vehicle server, and then the vehicle server synchronizes the statusof the friend key to the owner terminal device server. After that, the owner terminal device serversynchronizes the status of the friend key to the owner terminal device.
[00102] At step 718, the vehicle server records and tracks the status change of the friendkey, and notifies the owner and the friend in a form of text message.
[00103] With the above technical solution, it is possible to perform the process of sharingthe digital vehicle key based on the communication device even for the terminal device whosenative system does not support the ICCOA protocol, thereby expanding the scope of applicationof the ICCOA protocol.
[00104] In a possible implementation, the target communication party includes a vehicle.The terminal device is configured to establish a secure channel by performing public protocolbased communication with the vehicle through the communication device, and send a targetcontrol instruction to the vehicle through the secure channel. The target control instruction isconfigured to control the vehicle to implement a target action.
[00105] For example, after the digital vehicle key is activated, the terminal device canuse the digital vehicle key. When using the digital vehicle key, the terminal device mayauthenticate with the vehicle based on the communication device.
[00106] The authentication process may include standard authentication or may includefast authentication. During the standard authentication, the vehicle may verify legitimacy of adigital vehicle key of a mobile terminal based on a pre-stored digital-vehicle-key public key.During the fast authentication, the vehicle verifies the legitimacy of the digital vehicle key of themobile terminal based on a fast authentication secret key generated and stored in the last standardauthentication.
[00107] FIG. 8 is a flowchart of standard authentication of a mobile terminal and a vehicleaccording to an embodiment of the present disclosure. As illustrated in FIG. 8, the standardverification process includes the following steps.
[00108] At step 81, the vehicle generates a temporary vehicle public-private key pair.
[00109] At step 82, the vehicle sends a public key exchange request to the mobile terminal,and transmits a temporary vehicle public key and a vehicle ID (Vehicle_ID). A generation rule of
[00110] At step 83, the mobile terminal generates a temporary digital-vehicle-key publicprivatekey pair. For example, the mobile terminal may generate a temporary public-private keypair through the key management module.
[00111] At step 84, the mobile terminal sends to the vehicle a response to public keyexchange request and returns the temporary digital-vehicle-key public key and the digital vehiclekey ID (KeyID). A generation rule of KeyID can refer to the ICCOA protocol.
[00112] At step 85, the vehicle generates vehicle authentication information, and thevehicle authentication information includes the temporary digital-vehicle-key public key, thetemporary vehicle public key, and related information of KeyID. The vehicle may also sign thevehicle authentication information based on the vehicle private key.
[00113] At step 86, the vehicle sends a standard authentication request to the mobileterminal and transmits a vehicle authentication information signature to the mobile terminal.
[00114] At step 87, the mobile terminal verify the signature based on the vehicle publickey, and the vehicle public key certificate has been issued to the mobile terminal in the keyactivating process. In this way, the mobile terminal can verify the signature of the vehicle by thevehicle public key, thereby verifying an identity of the vehicle and preventing counterfeit vehiclesfrom obtaining information of the mobile terminal.
[00115] At step 88, in a case that the vehicle authentication information signature isverified successfully, the mobile terminal generates digital-vehicle-key authenticationinformation, which can include the temporary digital-vehicle-key public key, the temporaryvehicle public key and information related to the vehicle ID. After that, the mobile terminal cansign the digital-vehicle-key authentication information based on the digital-vehicle-key privatekey.
[00116] At steps 891 and 892, the mobile terminal generates a secure channel secret keyand a fast authentication secret key using a KDF (key derivation function) algorithm based on anegotiated symmetric secret key. The vehicle terminal generates a secure channel secret key anda fast authentication secret key using the same secret key negotiation algorithm and the KDFalgorithm. Both parties establish a secure channel based on the same secure channel secret key.
[00117] At step 810, the mobile terminal sends, based on the secure channel established,to the vehicle a response to standard authentication request and transmits to the vehicle the digitalvehicle-key authentication information signature.
[00118] At step 811, the vehicle queries the digital vehicle key ID internally according tothe digital vehicle key ID transmitted by the mobile terminal, to obtain the digital-vehicle-keypublic key corresponding to the digital vehicle key ID. When the vehicle can query the digital35vehicle-key public key, step 815 is executed. When the vehicle cannot query the digital vehicle814 based on the established secure channel, and the vehicle obtains the digital-vehicle-key publickey of the friend key through steps 812 to 814.
[00119] At step 812, the vehicle sends a digital vehicle key data request to the mobileterminal, the digital vehicle key data request is used to obtain the friend key authenticationinformation.
[00120] At step 813, the mobile terminal sends to the vehicle a response to digital vehiclekey data request and returns the friend key authentication information.
[00121] At step 814, after the vehicle decrypt the friend key authentication informationbased on the secure channel secret key, the vehicle verifies a signature of the friend keyauthentication information based on an owner digital-vehicle-key public key. In response to theverification being successful, a friend digital-vehicle-key public key in the friend keyauthentication information is saved.
[00122] At step 815, the vehicle verifies the digital-vehicle-key authenticationinformation signature transmitted by the mobile terminal based on the digital-vehicle-key publickey corresponding to the digital vehicle key ID. In response to the verification being successful,the standard authentication is successful. After the standard authentication is passed, the vehicleand the mobile terminal may synchronously save the fast authentication secret key generated thistime for subsequent fast authentication. For example, the mobile terminal may save the fastauthentication secret key to an encryption white box module.
[00123] At step 816, after successful authentication, the vehicle sends a status conditionreport to the mobile terminal, to inform the mobile terminal of an authentication status of thevehicle. In some implementation scenarios, before sending the status condition report, the vehiclemay perform reading and writing operations on service data of the mobile terminal based on thesecure channel having been established already.
[00124] After the standard authentication, the mobile terminal may transmit an instructionbased on the secure channel established to control the vehicle.
[00125] The above described embodiment provides an illustratively example of themanner in which the mobile terminal of the disclosure performs public protocol communication,by taking key activating, key sharing and key use as examples. However, those skilled in the artshould know that the mobile terminal provided by the disclosure can perform various publicprotocol based communications based on the communication device and achieve thecorresponding functions. These functions include, but are not limited to, key activating, keysharing, key use, key revocation, and the like.
[00126] In addition, the implementation of the mobile terminal provided by the disclosureis illustrated in the above mentioned embodiments by taking the ICCOA protocol as an example.an ICCE protocol, etc.
[00127] For example, in the ICCE protocol, the digital key module in the communicationdevice is able to communicate with the vehicle server, and is configured to implement functionsof a vehicle manufacturer application specified in the public protocol. These functions can include:providing a user interface for key management and querying, providing an interaction channelbetween the key and the vehicle server, performing service processes such as activating, updating,sharing, and revoking, etc., pairing and connecting with a vehicle Bluetooth / Ultra Wide Band(UWB) during the key activating phase, transmitting instructions to the key management modulethrough an API provided by the DKF, etc. Therefore, the above functional methods can beencapsulated to obtain the digital key module. The digital key module can be presented in a formof SDK and provides interfaces for the above mentioned functions.
[00128] The local application module of the communication device is capable ofcommunicating with the terminal device server, and is configured to implement functions of aterminal device manufacturer application specified in the public protocol. These functions mayinclude: providing a functional user interface related to the digital vehicle key, interacting withthe vehicle server, performing service processes such as activating, updating, sharing andrevoking, etc., and triggering state synchronization with the vehicle server after completingoperations of changing a key life cycle state, etc. Therefore, the above related functional methodscan be encapsulated to obtain the local application module. The local application module can alsobe presented in a form of SDK and provides interfaces for the above mentioned functions.
[00129] The DKF module of the communication device is configured to implementfunctions of the DKF specified in the public protocol. These functions include devices pairing,and vehicle key distribution and management. The DKF module may also interact with the digitalvehicle key program, so that the key management module can receive and respond in a timelymanner to an authentication message sent by the vehicle. The DKF module may also performaccess control for the API of the key management module and maintain rules for access control.
[00130] The key management module is configured to implement functions of a digitalkey program specified in the public protocol. For example, the key management module mayprovide a secure transaction function based on the encryption white box. In addition, to meet arequirement of carrying more than one vehicle key, an instance of the key management modulemay use a unified Application Identifier (AID), ensure isolation of key data from differentmanufacturers, and block unauthorized query requests.
[00131] Based on the communication device, the terminal device may perform the ICCEprotocol based communication with the target communication party, and the communicationmanner may refer to the ICCE protocol, which will not be repeated in the present invention forimplement functions of the terminal device specified in the CCC protocol. The communicationdevice is configured to establish CCC protocol based communication between the terminal deviceand the target communication party, which is not repeated in the present disclosure.
[00132] Based on the same inventive concept, the disclosure also provides a method forprocessing data, performed by a terminal device provided in the disclosure. FIG. 9 is a flowchartof a method for processing data for a terminal device according to an embodiment of the presentdisclosure. As illustrated in FIG. 9, the method includes the following steps.
[00133] At step S91, the terminal device detects whether a native system of the terminaldevice includes components for adapting a public protocol of a digital vehicle key.
[00134] At step S92, the terminal device communicates with a target communication partybased on the public protocol in case of absence of at least one of the components in the nativesystem, in which the target communication party is a participant of the public protocol.
[00135] For example, in a possible implementation, the public protocol is a publicprotocol based on certificate authentication, the target communication party includes a vehicleserver and a terminal device server, and communicating with the target communication partybased on the public protocol includes:
[00136] communicating with the vehicle server, the terminal device server, and thevehicle via the communication device, so that the step of activating the digital vehicle keyspecified in the public protocol is completed, and the digital vehicle key is obtained.
[00137] As illustrated in FIG. 5 and FIG. 6, in the disclosure, a process of activating thedigital vehicle key based on the ICCOA protocol by the communication device includes thefollowing steps.
[00138] At step 511 to step 513, the user may initiate a key activating process through thecommunication device of the terminal device. The user may input pairing information. The pairinginformation may be generated by the vehicle server, and the digital key module in thecommunication device may obtain the pairing information from the vehicle server. It is to be notedthat the vehicle server may also send initial pairing parameters to the vehicle.
[00139] At step 52, the vehicle terminal can interact with the DKF module of the terminaldevice, and perform bidirectional authentication with the terminal device based on anSPAKE2+algorithm, to establish an SPAKE2+secure channel. When the vehicle has been boundto the terminal device of the vehicle owner, the key activating process will stop. When the vehicleis not bound to the terminal device of the vehicle owner, the subsequent process continues basedon the SPAKE2+secure channel.
[00140] The vehicle (or terminal device) may also check whether a current state has meta key activating condition. The condition may be set based on application requirements. At stepkey certificate [F] to the terminal device. The vehicle public key certificate [F] includes a vehiclepublic key and a vehicle server CA signature.
[00141] At steps 541 to 543, the key management module of the terminal device canverify the vehicle public key certificate [F] based on a vehicle server CA certificate [C], whichincludes a vehicle server CA public key and a trusted CA signature. After successful verification,the terminal device can save the vehicle public key certificate [F]. For example, the terminaldevice may save the vehicle public key certificate to the encryption white box. In addition, theterminal device can generate a digital-vehicle-key public-private key pair [K], which includes adigital-vehicle-key public key and a digital-vehicle-key private key of the. The terminal devicecan also sign the digital-vehicle-key public key based on a key management module certificate[H], to generate a digital-vehicle-key public key certificate [L]. The key management modulecertificate [H] includes a CA public key and a CA private key of the key management module,and the digital-vehicle-key public key certificate [L] includes the digital-vehicle-key public keyand a key management module CA signature.
[00142] At step 55, the terminal device sends a terminal device server CA certificate [D],a key management module certificate [J] and the digital-vehicle-key public key certificate [L] tothe vehicle sequentially. The terminal device server CA certificate [D] includes a terminal deviceserver CA public key and a vehicle server CA signature. The key management module certificate[J] includes a key management module CA public key and a terminal device server CA signature.
[00143] At step 56, the vehicle sequentially verifies a certificate chain transmitted by theterminal device. The vehicle can verify the terminal device server CA certificate [D] via a vehicleserver CA certificate [G], which includes a vehicle server CA public key and a trusted CAsignature. The vehicle may also verify the key management module certificate [J] via the terminaldevice server CA certificate [D], which includes a terminal device server CA public key and avehicle server CA signature. The vehicle can also verify the digital-vehicle-key public keycertificate [L] by the key management module certificate [J].
[00144] In the case of successful verification, the vehicle can save the digital-vehicle-keypublic key and corresponding information of the digital vehicle key. In this way, the terminaldevice verifies and saves the vehicle public key, which completes generation and verificationsteps of the secret key for an owner's key pairing stage. At this time, the terminal device and thevehicle are successfully paired.
[00145] At step 57, the vehicle sends a status indication to the terminal device forindicating a pairing status of the digital vehicle key of the vehicle.
[00146] At steps 581 to 583, the vehicle synchronizes an activating status of the digitalvehicle key of the vehicle to the vehicle server, and the terminal device sends an activating statusserver synchronizes the activating status of the digital vehicle key to the vehicle server.
[00147] At step 59, the vehicle server sends a key activating message to notify the ownerof the vehicle.
[00148] At step 510, first standard authentication is performed between the terminaldevice and the vehicle, and a standard authentication secure channel is established.
[00149] At step 511, in response to a demand to set digital vehicle key service data, thevehicle sends a request of saving the digital vehicle key service data to the terminal device.
[00150] With the above technical solutions, for the terminal device whose native systemdoes not support the ICCOA protocol, it is possible to validate the digital vehicle key that is basedon the ICCOA protocol through the communication device, thereby expanding the scope ofapplication of the ICCOA protocol.
[00151] In a possible implementation, the public protocol is a public protocol based oncertificate authentication, the target communication party includes a vehicle server and a terminaldevice server, and communicating with the target communication party based on the publicprotocol includes:
[00152] in response to receiving a key sharing request, communicating with the vehicleserver via a digital key module in a communication device, and communicating with the terminaldevice server via a local application module in the communication device, rendering that anauthentication step for key sharing is completed, and a shared digital vehicle key is obtained.
[00153] As illustrated in FIG. 7, a process of key sharing includes the following steps.
[00154] At step 71, a user can set friend key sharing information, such as a validity period,a permission and other information. In a case that the native system of an owner terminal device,e.g., a terminal device of a vehicle owner, supports the ICCOA protocol, the user can set the friendkey sharing information in an application of a terminal device manufacturer of the owner terminaldevice, the application of the terminal device manufacturer can be, for example, a walletapplication. In a case that the native system of the owner terminal device does not support theICCOA protocol, the user may set the friend key sharing information via the communicationdevice.
[00155] At step 72, the owner terminal device signs the friend key sharing informationbased on uses an owner digital-vehicle-key private key and generates a friend key sharing request.
[00156] At step 73, the owner terminal device sends the friend key sharing request to anowner terminal device server, and the owner terminal device server forwards the sharing requestto the vehicle server.
[00157] At step 74, the vehicle server receives the sharing request and verifies a signatureof the sharing information based on the owner digital-vehicle-key public key.sharing information, the vehicle server generates an SessionID for a share link. The SessionIDmay be randomly generated by a random number generator to avoid a risk of incrementalprediction.
[00159] At step 76, the vehicle server sends the SessionID for the share link to the ownerterminal device server, and the owner terminal device server forwards the SessionID for the sharelink to the owner terminal device.
[00160] At step 77, after receiving the SessionID for the share link, the owner terminaldevice generates a share link including the SessionID, such that the owner may share the sharelink with a friend.
[00161] At step 78, the friend may open the share link through a friend terminal device,e.g., a terminal device of the friend. In a case that a native system of the friend terminal devicesupports the ICCOA protocol, the friend terminal device may jump to the application of theterminal device manufacturer and obtain the friend key sharing information from a friend terminaldevice server based on the SessionID. The friend terminal device server may obtain the friend keysharing information from the vehicle server. In addition, in a case that the native system of thefriend terminal device does not support the ICCOA protocol, the digital key module may obtainthe friend key sharing information from the friend terminal device server according to theSessionID when the friend terminal device opens the share link.
[00162] At step 79, the vehicle server sends the friend key sharing information to thefriend terminal device server, and the friend terminal server forwards the friend key sharinginformation to the friend terminal device.
[00163] At step 710, the friend terminal device prompts related information of friend keysharing and continues after the user confirms the related information. When the current friendterminal device already has a key for the corresponding vehicle, the current friend terminal devicemay stop the key sharing process and prompts a corresponding message.
[00164] At step 711, the friend terminal device generates a public key-private key pair ofa friend digital vehicle key.
[00165] At step 712, in a case where the native system of the friend terminal devicesupports the ICCOA protocol, the friend terminal device may generate a friend digital-vehicle30key public key certificate by signing the generated friend digital-vehicle-key public key based ona trusted execution environment CA. In a case that the native system of the friend terminal devicedoes not support the ICCOA protocol, the friend terminal device may generate the friend digitalvehicle-key public key certificate by signing the generated friend digital-vehicle-key public keybased on the key management module in the communication device.
[00166] At step 713, the friend terminal device initiates a transmission request to thepublic key certificate, the friend terminal device TEE CA certificate (or the key managementmodule CA certificate when the native system of the friend terminal device does not support theICCOA protocol, and the key management module CA certificate is obtained by signing the keymanagement module CA public key using the friend terminal server CA private key) and thefriend terminal device server CA certificate. The friend terminal device server forwards thetransmission contents to the vehicle server, and the vehicle server forwards the transmissioncontents to the owner terminal device server. After that, the owner terminal device server forwardsthe transmission contents to the owner terminal device.
[00167] At step 714, after receiving the above transmission contents, the owner terminaldevice may verify the friend terminal device server CA certificate with the vehicle server CAcertificate stored in the owner terminal device, and verify the friend terminal device TEE CAcertificate with the friend terminal device server CA certificate, and then verify the friend digitalvehicle-key public key certificate with the friend terminal device TEE CA certificate.
[00168] Alternatively, in a case that the transmission contents include the friend digital15vehicle-key public key certificate, the key management module CA certificate and the friendterminal device server CA certificate, the owner terminal device may verify the friend terminaldevice server CA certificate with the vehicle server CA certificate, and further verify the keymanagement module CA certificate with the friend terminal device server CA certificate, and thenverify the friend digital-vehicle-key public key certificate with the key management module CAcertificate.
[00169] At step 715, after confirming that the above certificate chain is successfullyverified, the owner terminal device may obtain a friend digital-vehicle-key public key. In thisway, the owner terminal device may sign the friend key sharing information and the friend digitalvehicle-key public key by using the owner digital-vehicle-key private key, and generates friendkey authentication information.
[00170] At step 716, the owner terminal device initiates a transmission request to theowner terminal device server, and the transmission contents may include the friend keyauthentication information and the vehicle public key certificate. The owner terminal deviceserver forwards the transmission contents to the vehicle server, and the vehicle server furtherforwards the transmission contents to the friend terminal device server, and then the friendterminal device server forwards the transmission contents to the friend terminal device.
[00171] At step 717, after receiving the friend key authentication information and thevehicle public key certificate, the friend terminal device saves the friend key authenticationinformation and the vehicle public key certificate. The friend key authentication information isused for a first standard authentication between the friend key and the vehicle, and is deleted after
[00172] The friend terminal device may further synchronize a status of the friend key tothe friend terminal device server, and the friend terminal device server further synchronizes thestatus of the friend key to the vehicle server, and then the vehicle server synchronizes the statusof the friend key to the owner terminal device server. After that, the owner terminal device serversynchronizes the status of the friend key to the owner terminal device.
[00173] At step 718, the vehicle server records and tracks the status change of the friendkey, and notifies the owner and the friend in a form of text message.
[00174] With the above technical solution, it is possible to perform the process of sharingthe digital vehicle key based on the communication device even for the terminal device whosenative system does not support the ICCOA protocol, thereby expanding the scope of applicationof the ICCOA protocol.
[00175] In a possible implementation, the target communication party includes a vehicle,and communicating with the target communication party based on the public protocol includes:
[00176] establishing a secure channel by performing public protocol basedcommunication with the vehicle through the communication device; and
[00177] sending a target control instruction to the vehicle through the secure channel, inwhich the target control instruction is configured to control the vehicle to implement a targetaction.
[00178] FIG. 8 is a flowchart of standard authentication of a mobile terminal and a vehicleaccording to an embodiment of the present disclosure. As illustrated in FIG. 8, the standardverification process includes the following steps.
[00179] At step 81, the vehicle generates a temporary vehicle public-private key pair.
[00180] At step 82, the vehicle sends a public key exchange request to the mobile terminal,and transmits a temporary vehicle public key and a vehicle ID (Vehicle_ID). A generation rule ofVehicle_ID can refer to the ICCOA protocol.
[00181] At step 83, the mobile terminal generates a temporary digital-vehicle-key publicprivatekey pair. For example, the mobile terminal may generate a temporary public-private keypair through the key management module.
[00182] At step 84, the mobile terminal sends to the vehicle a response to public keyexchange request and returns the temporary digital-vehicle-key public key and the digital vehiclekey ID (KeyID). A generation rule of KeyID can refer to the ICCOA protocol.
[00183] At step 85, the vehicle generates vehicle authentication information, and thevehicle authentication information includes the temporary digital-vehicle-key public key, thetemporary vehicle public key, and related information of KeyID. The vehicle may also sign thevehicle authentication information based on the vehicle private key.terminal and transmits a vehicle authentication information signature to the mobile terminal.
[00185] At step 87, the mobile terminal verify the signature based on the vehicle publickey, and the vehicle public key certificate has been issued to the mobile terminal in the keyactivating process. In this way, the mobile terminal can verify the signature of the vehicle by thevehicle public key, thereby verifying an identity of the vehicle and preventing counterfeit vehiclesfrom obtaining information of the mobile terminal.
[00186] At step 88, in a case that the vehicle authentication information signature isverified successfully, the mobile terminal generates digital-vehicle-key authenticationinformation, which can include the temporary digital-vehicle-key public key, the temporaryvehicle public key and information related to the vehicle ID. After that, the mobile terminal cansign the digital-vehicle-key authentication information based on the digital-vehicle-key privatekey.
[00187] At steps 891 and 892, the mobile terminal generates a secure channel secret keyand a fast authentication secret key using a KDF (key derivation function) algorithm based on anegotiated symmetric secret key. The vehicle terminal generates a secure channel secret key anda fast authentication secret key using the same secret key negotiation algorithm and the KDFalgorithm. Both parties establish a secure channel based on the same secure channel secret key.
[00188] At step 810, the mobile terminal sends, based on the secure channel established,to the vehicle a response to standard authentication request and transmits to the vehicle the digital20vehicle-key authentication information signature.
[00189] At step 811, the vehicle queries the digital vehicle key ID internally according tothe digital vehicle key ID transmitted by the mobile terminal, to obtain the digital-vehicle-keypublic key corresponding to the digital vehicle key ID. When the vehicle can query the digitalvehicle-key public key, step 815 is executed. When the vehicle cannot query the digital vehiclekey ID and the corresponding digital-vehicle-key public key, the vehicle executes steps 812 to814 based on the established secure channel, and the vehicle obtains the digital-vehicle-key publickey of the friend key through steps 812 to 814.
[00190] At step 812, the vehicle sends a digital vehicle key data request to the mobileterminal, the digital vehicle key data request is used to obtain the friend key authenticationinformation.
[00191] At step 813, the mobile terminal sends to the vehicle a response to digital vehiclekey data request and returns the friend key authentication information.
[00192] At step 814, after the vehicle decrypt the friend key authentication informationbased on the secure channel secret key, the vehicle verifies a signature of the friend keyauthentication information based on an owner digital-vehicle-key public key. In response to theauthentication information is saved.
[00193] At step 815, the vehicle verifies the digital-vehicle-key authenticationinformation signature transmitted by the mobile terminal based on the digital-vehicle-key publickey corresponding to the digital vehicle key ID. In response to the verification being successful,the standard authentication is successful. After the standard authentication is passed, the vehicleand the mobile terminal may synchronously save the fast authentication secret key generated thistime for subsequent fast authentication. For example, the mobile terminal may save the fastauthentication secret key to an encryption white box module.
[00194] At step 816, after successful authentication, the vehicle sends a status conditionreport to the mobile terminal, to inform the mobile terminal of an authentication status of thevehicle. In some implementation scenarios, before sending the status condition report, the vehiclemay perform reading and writing operations on service data of the mobile terminal based on thesecure channel having been established already.
[00195] After the standard authentication, the mobile terminal may transmit an instructionbased on the secure channel established to control the vehicle.
[00196] In the above technical solutions, the communication device is provided in theterminal device. The communication device may detect whether the native system of the terminaldevice includes the components for adapting the public protocol of the digital vehicle key, andcommunicates with the target communication party based on the public protocol in case of absenceof at least one of the components in the native system. The target communication party is aparticipant of the public protocol.
[00197] Therefore, the terminal device can perform the public protocol basedcommunication with the target communication party through the communication device, toimplement functions of the digital vehicle key based on the public protocol. In this way, the publicprotocol can be applied to various terminal devices, to expand the scope of application of thepublic protocol. Moreover, since the terminal devices that do not support the public protocol canalso perform the public protocol based communication through the communication device, andfurther implement the functions of the digital vehicle key. Therefore, the terminal device may notbe configured with components for implementing the digital vehicle key based on a privateprotocol, deployment costs of the digital vehicle key are reduced.
[00198] In another illustrative embodiment, a computer program product is also provided.The computer program product includes computer programs capable of being executed by aprogrammable device. The computer programs have a code portion for performing the method forprocessing data for the terminal device described above when executed by the programmabledevice.from consideration of the specification and practice of the disclosure disclosed here. Thisapplication is intended to cover any variations, uses, or adaptations of the disclosure followingthe general principles thereof and including such departures from the disclosure as come withinknown or customary practice in the art. It is intended that the specification and examples beconsidered as exemplary only, with a true scope and spirit of the disclosure being indicated bythe following claims.
[00200] It will be appreciated that the disclosure is not limited to the exact constructionthat has been described above and illustrated in the accompanying drawings, and that variousmodifications and changes can be made without departing from the scope thereof. It is intendedthat the scope of the disclosure only be limited by the appended claims.
Claims
1. A terminal device (10), comprising: a communication device (100), configured to: detect whether a native system of the terminal device (10) comprises components for adapting a public protocol of a digital vehicle key; and communicate with a target communication party based on the public protocol in case of absence of at least one of the components in the native system; wherein the target communication party is a participant of the public protocol.
2. The terminal device (10) as claimed in claim 1, wherein the communication device (100) comprises: a digital key module (101), capable of communicating with a vehicle server, configured to implement functions of a vehicle manufacturer application specified in the public protocol; a local application module (102), capable of communicating with a terminal device server, configured to implement functions of a terminal device manufacturer application specified in the public protocol; a digital key framework module (103), configured to implement functions of a digital key framework specified in the public protocol; and a key management module (104), configured to implement functions of a digital key program specified in the public protocol.
3. The terminal device (10) as claimed in claim 2, wherein the communication device (100) comprises an encryption white box module (105), configured to store data of the digital vehicle key.
4. The terminal device (10) as claimed in claim 2, wherein the local application module (102) is configured to communicate with the terminal device server based on a terminal device service module in the vehicle server.
5. The terminal device (10) as claimed in claim 2, wherein the public protocol is a public protocol based on certificate authentication, the target communication party comprises the vehicle server and the terminal device server, the terminal device (10) is configured to, in response to receiving a key sharing request, communicate with the vehicle server via the digital key module (101) and communicate with the terminal device server via the local application module (102), key is obtained.
6. The terminal device as claimed in claim 5, wherein the public protocol is a Car Connectivity Consortium (CCC) protocol or an Intelligent Car Connectivity Open Alliance (ICCOA) protocol.
7. The terminal device (10) as claimed in claims 1, wherein the target communication party comprises a vehicle, and the terminal device (10) is configured to establish a secure channel by performing public protocol based communication with the vehicle through the communication device (100), and send a target control instruction to the vehicle through the secure channel, wherein the target control instruction is configured to control the vehicle to implement a target action.
8. A method of processing data for a terminal device, performed by the terminal device according to any one of claims 1-7, comprising: detecting (S91) whether a native system of the terminal device comprises components for adapting a public protocol of a digital vehicle key; and communicating (S92) with a target communication party based on the public protocol in case of absence of at least one of the components in the native system, wherein the target communication party is a participant of the public protocol.
9. The method as claimed in claim 8, wherein the public protocol is a public protocol based on certificate authentication, the target communication party comprises a vehicle server and a terminal device server, and communicating with the target communication party based on the public protocol comprises: in response to receiving a key sharing request, communicating with the vehicle server via a digital key module in a communication device, and communicating with the terminal device server via a local application module in the communication device, rendering that an authentication step for key sharing is completed, and a shared digital vehicle key is obtained.
10. The method as claimed in claim 8, wherein the target communication party comprises a vehicle, and communicating with the target communication party based on the public protocol comprises: establishing a secure channel by performing public protocol based communication with the vehicle through the communication device; and target control instruction is configured to control the vehicle to implement a target action.
