CN116887221B - Cross-protocol digital key sharing method, system and computer readable storage medium - Google Patents

Cross-protocol digital key sharing method, system and computer readable storage medium Download PDF

Info

Publication number
CN116887221B
CN116887221B CN202311145789.5A CN202311145789A CN116887221B CN 116887221 B CN116887221 B CN 116887221B CN 202311145789 A CN202311145789 A CN 202311145789A CN 116887221 B CN116887221 B CN 116887221B
Authority
CN
China
Prior art keywords
key
sharing
ccc
server
friend
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202311145789.5A
Other languages
Chinese (zh)
Other versions
CN116887221A (en
Inventor
王颖
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ingeek Information Security Consulting Associates Co ltd
Original Assignee
Ingeek Information Security Consulting Associates Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ingeek Information Security Consulting Associates Co ltd filed Critical Ingeek Information Security Consulting Associates Co ltd
Priority to CN202311145789.5A priority Critical patent/CN116887221B/en
Publication of CN116887221A publication Critical patent/CN116887221A/en
Application granted granted Critical
Publication of CN116887221B publication Critical patent/CN116887221B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00—Individual registration on entry or exit
    • G07C9/00174—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
    • G07C9/00571—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated by interacting with a central unit
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H04W12/043—Key management, e.g. using generic bootstrapping architecture [GBA] using a trusted network node as an anchor
    • H04W12/0431—Key distribution or pre-distribution; Key agreement
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/50—Secure pairing of devices
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00—Individual registration on entry or exit
    • G07C9/00174—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
    • G07C9/00309—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated with bidirectional data transmission between data carrier and locks
    • G07C2009/00412—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated with bidirectional data transmission between data carrier and locks the transmitted data signal being encrypted

Abstract

The embodiment of the invention relates to the technical field of digital keys, and discloses a trans-protocol digital key sharing method, a trans-protocol digital key sharing system and a computer readable storage medium. The method comprises the following steps: generating a CCC (common control code) main key based on the main equipment, a fleet management server, an SBOD (base station outside data) and the OEM server of the vehicle factory and issuing the CCC main key to the vehicle terminal for the vehicle terminal to sign the CCC sharing key of the friend equipment according to the CCC main key; establishing a key sharing bidirectional encryption channel between the SBOD and the friend equipment based on the friend equipment, a fleet management server, the SBOD, a vehicle manufacturer OEM server and the friend equipment server; and acquiring the CCC sharing key generated by the SBOD by the friend equipment based on the bidirectional encryption channel. The embodiment of the invention solves the problem that ICCE and CCC digital keys cannot be shared across protocols, and can improve the sharing convenience of the digital keys and the user experience.

Description

Cross-protocol digital key sharing method, system and computer readable storage medium
Technical Field
The embodiment of the invention relates to the technical field of digital keys, in particular to a trans-protocol digital key sharing method, a trans-protocol digital key sharing system and a computer readable storage medium.
Background
In the rapid development process of digital keys, the international standard CCC of digital keys, which is pushed by the automobile connection alliance (Car Connectivity Consortium, abbreviated as CCC), becomes one of the digital key standards with the most influence, and other digital key standards with influence also have the ICCE protocol of the intelligent car co-production industry ecological alliance (Intelligent Car Connectivity Industry Ecosystem Alliance, ICCE). The vehicle factories have different demands and consideration points for different digital key protocols, so the current digital key field is in a stage of multi-protocol coexistence and rapid development. However, the CCC and other digital key protocols, such as ICCE, cannot be interconnected and intercommunicated, so that a vehicle owner supporting the ICCE protocol but not the CCC protocol cannot share the digital key with a user supporting the CCC but not the ICCE protocol, which seriously affects the convenience of sharing the digital key.
Disclosure of Invention
The embodiment of the invention provides a trans-protocol digital key sharing method, a trans-protocol digital key sharing system and a computer readable storage medium, which can realize that an ICCE owner user shares a digital key to CCC equipment, solve the problem that the digital key cannot be shared in a trans-protocol manner, and can improve the sharing convenience of the digital key and user experience.
In a first aspect, an embodiment of the present invention provides a cross-protocol digital key sharing method, which is applied to a dual-protocol digital key system, where the dual-protocol digital key system includes: an ICCE subsystem and a CCC subsystem; the ICCE subsystem includes: the vehicle owner equipment, the vehicle machine end, the OEM server of the vehicle factory and the ICCE digital key server; the vehicle-mounted terminal is configured with an ICCE protocol and a CCC protocol; the CCC subsystem includes: friend equipment, friend equipment server, fleet management server FMS, key tracking service KTS and CCC digital key server SBOD;
the method comprises the following steps:
generating a CCC (common control code) main key based on the main equipment, a fleet management server, an SBOD (base station outside data) and the OEM server of the vehicle factory and issuing the CCC main key to the vehicle terminal for the vehicle terminal to sign the CCC sharing key of the friend equipment according to the CCC main key;
establishing a key sharing bidirectional encryption channel between the SBOD and the friend equipment based on the friend equipment, a fleet management server, the SBOD, a vehicle manufacturer OEM server and the friend equipment server;
and acquiring the CCC sharing key generated by the SBOD by the friend equipment based on the bidirectional encryption channel.
As one embodiment, the generating CCC master key based on the master device, the fleet management server, the SBOD, and the OEM server and issuing the CCC master key to the vehicle terminal includes:
the vehicle owner equipment requests the FMS, the SBOD and the OEM server to add the VIN number of the vehicle end;
the OEM server of the vehicle factory requests the SBOD to generate a CCC main key of the vehicle terminal, and the SBOD sends the generated CCC main key to the vehicle terminal for the vehicle terminal to sign the CCC sharing key of the friend equipment according to the CCC main key.
As one embodiment, the establishing a two-way encryption channel for key sharing between the SBOD and the friend device based on the friend device, the fleet management server, the SBOD, the OEM server of the vehicle factory, and the friend device server includes:
the friend equipment initiates a key sharing request to the fleet management server according to the sharing request of the vehicle owner equipment;
the SBOD sends a sharing session creation request to the OEM server of the garage according to the key sharing request, and the OEM server of the garage creates the sharing session and binds the identification of the CCC owner key with the sharing session;
The SBOD associates the sharing session with the fleet management server according to the sharing session creation information fed back by the OEM server of the vehicle factory, and generates a session key of the sharing session;
the fleet management server sends the URL of the sharing session and a session key fed back by the SBOD to the friend equipment;
the friend equipment associates the handle of the friend equipment with the sharing session and sends the handle of the friend equipment to the friend equipment server;
the friend device server binding the sharing session and the friend device handle;
and after binding the sharing session, the identification of the CCC owner key and the handle of the friend equipment, the OEM server of the vehicle factory informs the SBOD that the sharing session is ready to be completed.
As one embodiment, before the friend device initiates a key sharing request to the fleet management server according to the sharing request of the owner device, the method further includes:
the fleet management server sends the shared key configuration data obtained from the OEM server to the SBOD.
As one embodiment, the acquiring, by the friend device, the CCC sharing key generated by the SBOD based on the bidirectional encryption channel includes:
The SBOD packages and shares a key creation request and sends the key creation request to the OEM server of the vehicle factory;
the OEM server and the friend equipment server send the sharing key creation request to the friend equipment sequentially based on the handle of the friend equipment;
the friend equipment analyzes the sharing key creation request, generates an asymmetric sharing key pair, generates a signature request according to the asymmetric sharing key pair, and sends the signature request to the SBOD through the friend equipment server and the OEM server of the vehicle factory;
the SBOD generates the CCC sharing key according to the signature request, and sends the CCC sharing key to the friend equipment through the OEM server of the vehicle factory and the friend equipment server;
and the friend equipment acquires the CCC sharing key and stores the key.
As one embodiment, after the friend device obtains the CCC sharing key and stores the CCC sharing key, the method further comprises:
registering the CCC sharing key based on the friend device server, the OEM server of the vehicle manufacturer, and the KTS.
As an embodiment, before the establishing the two-way encryption channel for key sharing between the SBOD and the friend device based on the friend device, the fleet management server, the SBOD, the OEM server of the vehicle factory, and the friend device server, the method further includes:
And the friend equipment determines that the sharing key is a CCC sharing key according to the key sharing request sent by the owner equipment.
As an embodiment, before the CCC master key is generated and issued to the vehicle side based on the vehicle owner device, the fleet management server, the SBOD, and the vehicle factory OEM server, the method further includes:
and adding the OEM server of the vehicle factory into the CCC subsystem.
In a second aspect, an embodiment of the present invention provides a trans-protocol digital key sharing system configured in a dual-protocol digital key system, where the dual-protocol digital key system includes: an ICCE subsystem and a CCC subsystem; the ICCE subsystem includes: the vehicle owner equipment, the vehicle machine end, the OEM server of the vehicle factory and the ICCE digital key server; the vehicle-mounted terminal is configured with an ICCE protocol and a CCC protocol; the CCC subsystem includes: friend equipment, friend equipment server, fleet management server FMS, key tracking service KTS and CCC digital key server SBOD;
the cross-protocol digital key sharing system comprises:
the CCC owner key presetting module is used for generating a CCC owner key based on the owner equipment, the fleet management server, the SBOD and the OEM server of the garage and sending the CCC owner key to the vehicle terminal for the vehicle terminal to sign the CCC sharing key of the friend equipment according to the CCC owner key;
The two-way encryption channel establishment module is used for establishing a key sharing two-way encryption channel between the SBOD and the friend equipment based on the friend equipment, the fleet management server, the SBOD, the OEM server of a vehicle factory and the friend equipment server;
and the sharing key generation module is used for acquiring the CCC sharing key generated by the SBOD based on the two-way encryption channel and the friend equipment.
In a third aspect, embodiments of the present invention provide a computer readable storage medium having stored thereon a computer program which when executed by a processor implements a key sharing method as described above.
Compared with the prior art, the technical scheme provided by the embodiment of the invention has at least the following positive effects:
according to the embodiment of the invention, the CCC motorcade digital key system and the ICCE digital key system are opened, so that the ICCE owner equipment can share the digital key with the CCC friend equipment, the problem that the existing ICCE and CCC digital keys cannot be shared across protocols is solved, and the convenience of digital key sharing is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of a cross-protocol digital key sharing method according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a sub-process example of presetting an ICCE and CCC master key in a cross-protocol digital key sharing method according to an embodiment of the present invention;
fig. 3 is a sub-flowchart of establishing a bidirectional encryption channel for sharing a CCC sharing key between a friend device and a CCC digital key server in the cross-protocol digital key sharing method according to the embodiment of the present invention;
FIG. 4 is a sub-flowchart of CCC key sharing by using a bidirectional encryption channel in the cross-protocol digital key sharing method according to the embodiment of the present invention;
fig. 5 is a schematic structural diagram of a cross-protocol digital key sharing system according to an embodiment of the present invention.
Description of the embodiments
The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings.
According to the technical scheme, the problem that an ICCE owner user cannot share the digital key with CCC friend equipment in the prior art is solved, and the inter-protocol digital key sharing system is constructed to realize interconnection and intercommunication of ICCE and CCC protocols, so that the ICCE owner device shares the inter-protocol digital key with the CCC friend equipment, the inter-protocol digital key sharing capability and convenience are improved, and the user experience is improved.
Example 1
The inter-protocol digital key sharing method provided by the embodiment of the invention is used for realizing the interconnection and intercommunication of ICCE and CCC digital key protocols, thereby realizing the sharing of digital keys from the ICCE owner equipment to the CCC friend equipment. The embodiment of the invention can be applied to a double-protocol digital key system, and the double-protocol digital key system can comprise: ICCE subsystem and CCC subsystem. The ICCE subsystem comprises: the vehicle owner equipment, the vehicle end, the OEM server of the vehicle factory and the ICCE digital key server are configured with an ICCE protocol and a CCC protocol. The CCC subsystem may include: friend device, friend device server, fleet management server FMS, key tracking service KTS, and CCC digital key server SBOD. As shown in FIG. 1, the cross-protocol digital key sharing method in the embodiment of the invention comprises steps 102-106.
Step 102: and generating a CCC (common control code) main key based on the main equipment, the fleet management server, the SBOD (base station outside data) and the OEM server of a vehicle factory, and issuing the CCC main key to a vehicle terminal, and signing the CCC sharing key of the friend equipment by the vehicle terminal according to the CCC main key.
Step 102 may specifically include: the vehicle owner equipment requests the FMS, the SBOD and the OEM server of the vehicle factory to add the VIN number of the vehicle terminal, so that the FMS, the SBOD and the OEM server of the vehicle factory can acquire the identity information of the vehicle terminal. The OEM server of the automobile factory requests the SBOD to generate a CCC owner key of the automobile machine side, wherein the CCC owner key is a pair of asymmetric key pairs. And the SBOD sends the generated CCC owner key to the vehicle machine end, and the vehicle machine end signs the CCC sharing key of the friend equipment according to the CCC owner key. The SBOD sends the public key in the asymmetric key pair to the vehicle terminal, and the CCC sharing key signs the private key in the asymmetric key pair, so that the vehicle terminal can sign the friend equipment.
It should be noted that, before generating the CCC master key based on the master device, the fleet management server, the SBOD, and the OEM server of the vehicle factory and issuing the CCC master key to the vehicle terminal, the method may further include: the OEM server of the vehicle factory is added to the CCC subsystem, thereby enabling the ICCE subsystem to communicate with the CCC subsystem.
Step 104: and establishing a key sharing bidirectional encryption channel between the SBOD and the friend device based on the friend device, the fleet management server, the SBOD, the OEM server of the garage and the friend device server.
The two-way encryption channel enables the friend equipment and the SBOD to be in safe communication, and safe transmission of key sharing data is achieved.
Specifically, step 104 may include: the friend equipment initiates a key sharing request to the fleet management server according to the sharing request of the owner equipment, the SBOD sends a sharing session creation request to the OEM server of the garage according to the key sharing request, the OEM server of the garage creates a sharing session and binds the identification of the CCC owner key with the sharing session, and the SBOD associates the sharing session with the fleet management server according to the sharing session creation information fed back by the OEM server of the garage and generates a session key of the sharing session; the fleet management server sends the uniform resource location system (uniform resource locator, URL) address of the sharing session fed back by the SBOD and the session key to the friend device, which has acquired the session key. And the friend equipment associates and sends the handle of the friend equipment with the sharing session to a friend equipment server, the friend equipment server binds the sharing session with the handle of the friend equipment, and the OEM server of the vehicle factory binds the sharing session, the identification of the CCC owner key and the handle of the friend equipment and then notifies the SBOD of the completion of the sharing session preparation.
It should be noted that, before step 104, the method may further include: the fleet management server sends the shared key configuration data obtained from the OEM server of the fleet to the SBOD. The shared key configuration data may include information about friend devices, key rights, etc., and is not particularly limited herein.
Step 106: and acquiring the CCC sharing key generated by the SBOD based on the bidirectional encryption channel friend equipment.
Step 106 may specifically include: the SBOD packages and shares the key to create the request and sends to the OEM server of the garage; the OEM server of the vehicle factory and the friend equipment server sequentially send a sharing key creation request to the friend equipment based on the handle of the friend equipment; the friend equipment analyzes the sharing key creation request, generates an asymmetric sharing key pair, generates a signature request according to the asymmetric sharing key pair, and sends the signature request to the SBOD through the friend equipment server and the OEM server of the vehicle factory; the SBOD generates a CCC sharing key according to the signature request, and sends the CCC sharing key to friend equipment through an OEM server of a vehicle factory and a friend equipment server; and the friend equipment acquires and stores the CCC sharing key.
The CCC sharing key in the friend equipment adopts the private key signature of the CCC owner key, and can be checked and signed by the CCC owner key (public key) at the vehicle machine end. The SBOD may configure the usage rights of the sharing key, etc., according to the sharing key configuration data.
It is noted that, after step 106, the method may further include: CCC sharing keys are registered based on the friend device server, the driver OEM server, and the KTS.
Fig. 2 shows a sub-flow of presetting an ICCE and a CCC master key at a vehicle side, and fig. 3 shows a sub-flow of establishing a bidirectional encrypted channel between a CCC master key server and a CCC Friend Device (Friend Device); fig. 4 shows a flow of sharing a CCC digital key, etc., based on an established bi-directional encrypted channel. In the figure, owner Device Wallet App is wallet application of owner equipment, owner Device OEM APP is ICCE digital key application of owner equipment, vehicle (ICCE/CCC) is a Vehicle end supporting ICCE and CCC dual protocols, vehicle OEM Server is a Vehicle factory OEM Server, ICCE DK Server is an ICCE digital key Server, KTS is a key tracking Server, server Based Owner Device (SBOD) is a CCC digital key Server, FMS is a fleet management Server, friend Device is Friend Device, and Friend Device OEM Server is Friend Device OEM Server. The following details of the embodiments of the present invention are described with reference to the sub-flowcharts shown in fig. 2 to 4:
as shown in fig. 2, the process of presetting an ICCE, a CCC master key and opening a wallet key at a vehicle end comprises the following steps:
And step 1, applying for opening the digital key service from the OEM server of the vehicle factory by the vehicle owner equipment.
Specifically, the owner device downloads and installs an OEM APP (ICCE digital key application), and the user can establish a man-car binding relationship based on an interface provided by the owner device, and then apply for opening a digital key service, i.e. the owner device obtains an ICCE owner key, which is a symmetric key.
And 2, requesting key data between the OEM server of the vehicle factory and the ICCE digital key server.
Specifically, the OEM server of the vehicle factory may transmit the acquired key data to the ICCE digital key server according to a request of the ICCE digital key server. The ICCE owner digital key is generated according to ICCE protocol specifications, and is not described in detail herein.
And 3, the ICCE digital key server transmits ICCE key data to the vehicle owner equipment.
The ICCE digital key server generates an ICCE owner key based on rules known to those skilled in the art, and the ICCE key data comprises the ICCE owner key.
And 4, pairing the vehicle owner equipment with the vehicle machine end and completing key data verification.
The vehicle-mounted terminal supports an ICCE/CCC double-digital key protocol, so that the ICCE owner key of the owner equipment can be checked, and the CCC owner key of the friend equipment can be checked.
And 5, storing an ICCE owner key at the vehicle end.
Thus, the ICCE owner digital key can be preset at the vehicle end.
Before the foregoing steps are performed, the following steps are required to be performed:
0.1, fleet management server issues FMSID, publish (FMSID), to CCC digital key server. The FMSID is a fleet management server ID.
The 0.2, CCC digital key server issues FMSID and SBODID, i.e., public (FMSID, SBODID) to the OEM server of the garage.
0.3, the OEM server of the vehicle manufacturer issues VOEMID, i.e., public (SBODID), which is the ID of the OEM server of the vehicle manufacturer, to the CCC digital key server.
And the 0.4 CCC digital key server issues VOEMID (OEMID) and SBODID to the fleet management server.
Through the steps 0.1-0.4, the fleet management server, the SBOD and the like can obtain the identity of the OEM server of the vehicle factory, so that the CCC subsystem can interact with different OEM servers of the vehicle factory.
And 6, the vehicle owner equipment sends a request to the vehicle team management server to add the corresponding VIN into the FMS.
The vehicle identification code (Vehicle Identification Number, VIN) is a unique code specified by the vehicle manufacturer for identifying the vehicle. After the vehicle owner device requests the VIN of the vehicle to be added into the fleet management server, the fleet management server can store the vehicle identity information.
And 7, step 8, sequentially sending an InFleet (FMSID, VIN) request to the CCC digital key server and the CCC digital key server by the fleet management server to the OEM server of the vehicle factory, so that the SBOD and the OEM server of the vehicle factory obtain the association information of the FMS and the vehicle machine side.
The FMSID is a random character string and is unique in a host factory system, so that different fleet management servers are identified.
And 9, the OEM server of the vehicle factory sends a CCC owner key creation request to the CCC digital key server.
creatOwnerkey (FMSID, vehicleID, DK _create_ DATA, vehicleReaderInfo, vehicleProtocolInfo), i.e., CCC owner key CREATION request, carries parameters in which VehicleID is 8 bytes of data defined by the CCC specification, used as a vehicle identifier. The dk_create_data may include vehicle-side information and vehicle owner device information. The VehicleReaderInfo may specifically be a vehicle identifier and a protocol version. The VehicleProtocolInfo may indicate a digital key protocol supported by the vehicle side, such as ICCE and CCC dual protocol.
And 10, verifying the digital key creation data by the CCC digital key server, and generating a CCC owner key after verification is successful.
After receiving a request of creating a vehicle owner key (creatOwnerkey) of an OEM server of a vehicle factory, the CCC digital key server side executes a verify DK_CREATION and generates a CCC vehicle owner key Create Owner.key, namely, whether DK_CREATION_DATA sent by the OEM server of the vehicle factory is correct or not is verified, if the DK_CREATION_DATA is correct, the CCC vehicle owner key is continuously generated, and the CCC vehicle owner key is an asymmetric key pair.
And step 11, the CCC digital key server transmits CCC owner key data to the OEM server of the garage.
I.e., SBOD CA Cert, instance_Atteststation, DK_creation_Atteststation. Wherein, CCC owner key data may include: CA Cert, instance_ Attestation, DK _Creation_Atteststation. The CA Cert is a CA certificate, an issuer of the certificate, and an instance_attach is a vehicle owner equipment certificate, and comprises an Instance ID, a parent certificate public key and the like, which are used for proving the validity of the Instance. Dk_creation_attestation is certification data of digital key Creation data, proving validity of the Creation data.
And 12, the OEM server of the vehicle factory requests to register a CCC vehicle owner key (Owner. Key) in the KTS and acquires KTS certification.
And 13, the OEM server of the automobile factory sends the CCC owner key to the automobile machine end.
Specifically, the public key in the key pair of the asymmetric owner key generated by the SBOD can be sent to the OEM server of the garage, and the CCC digital key server side can store the corresponding private key.
And 14, verifying the owner key created by the SBOD and storing the owner key at the vehicle end as a CCC vehicle owner key for signature verification of the CCC sharing key.
Thus, the vehicle machine end finishes presetting the ICCE and CCC two main keys.
And step 15, informing the vehicle owner equipment of finishing the opening of the digital key by the OEM server of the vehicle factory.
And step 16, the owner equipment prompts the user that the digital key is opened, and inquires whether the ICCE wallet key is opened.
And step 17, if the instruction of agreeing to open the ICCE wallet key is received by the user, opening the ICCE wallet key by the owner equipment.
And step 18, opening a wallet key.
The first initialization of the digital key can be completed after the wallet key is opened, so that the vehicle has the digital key capability. The wallet application of the owner device may act as a sharing portal for the owner device side CCC digital key.
Referring to fig. 3, after the wallet key is turned on, the process of establishing a two-way encryption channel between the SBOD and CCC friend device includes the following steps:
and step 1, applying a sharing key to friend equipment by the vehicle owner equipment from the OEM server of the vehicle manufacturer, and generating a sharing authorization code by the OEM server of the vehicle manufacturer.
The friend device may receive the sharing key by means of the sharing authorization code SharingToken.
And step 2, the OEM server of the vehicle factory sends a notification to friend equipment to inform friend users of extracting the sharing key.
The friend user can be informed of extracting the sharing key in a short message or link mode.
And step 3, if the operation of extracting the sharing key is triggered, the friend equipment judges whether the friend equipment supports the CCC protocol or not.
If the friend equipment does not support CCC, entering an ICCE digital key sharing flow, generating an ICCE digital key by an OEM server of a vehicle factory and issuing the ICCE digital key to the friend equipment, and if the friend equipment supports CCC protocol, continuing to execute the following cross-protocol CCC digital key sharing step. It should be noted that, the process of generating the ICCE sharing digital key by the OEM server of the vehicle factory and issuing the ICCE sharing digital key to the friend device belongs to the known sharing process of the ICCE digital key, which is not described herein again.
And 4, requesting the FMS to initiate a CCC key sharing process by the friend equipment.
The request carries the parameter SharingToken. CCC then exchanges key configuration information, getEntitlements (SharingToken), between the FMS and the OEM server of the garage.
If the OEM server verifies that the sharing authorization code SharingToken transmitted by the FMS corresponds to the sharing authorization code generated in advance, the FMS is authorized to share the CCC digital key.
And 5, preparing digital key sharing information by the FMS and sending the digital key sharing information to the SBOD.
I.e., prepareDKSharing (VehicleID, accountID, fmsSharingID, dk.Entitlements)), where AccountID is friend user identity information, fmsSharingID is sharing session ID, dk.Entitlements, which can be configured by the vehicle owner device.
And 6, the SBOD requests the OEM server of the vehicle factory to generate a sharing session.
I.e. GenerateSharingSession (OwnerKeyID). The sharing session (SharingSession) carries the session parameter OwnerKeyID.
And 7, generating a Sharing Session by the OEM server of the vehicle factory, and binding the Sharing Session with the Owner Key ID.
I.e., bind (SharingSession, ownerKeyID).
And 8, returning the SBOD to generate the sharing session ready by the OEM server of the vehicle factory.
I.e. generateSharingResponse (SharingSession).
Step 9, SBOD binds the sharing session and FmsSharingID.
I.e., bind (SharingSession, fmsSharingID).
The SBOD also generates a session key for the sharing session upon request, generate Sharing Password If required, generate Privacy Protection symetric Key:prKey. prKey is the shared session key, which is a symmetric key.
Step 10, the SBOD responds to the FMS digital key sharing session readiness.
I.e. prepareDKSharingResponse (SharingURL, sharingPassword).
The SharingURL is an extraction address of the CCC sharing key, and SharingPassword is a session key.
Step 11, the FMS invites friend equipment to join the sharing session.
I.e. invite with SharingSession ContainIng vehicle OEM URL, sharingSession, prKey and other metadata for display over whatsAPP, SMS, vehicleOEMApp or other channel in URL format.
The parameters carried by the sharing session for inviting to join comprise: the OEM URL of the vehicle factory, the sharing session (SharingSession), the private key (prKey), and other metadata (other metadata) that may be presented in URL format through WhatsAPP, SMS, vehicleOEMApp or other channels. The OEM URL of the vehicle factory is a link to open a digital key.
Step 12, the ICCE digital key application of the friend device sends the URL to the wallet application via the application program interface API.
I.e., vehicleOEMApp send the URL to wallet via API), the wallet application parses URL (Wallet decode the URL).
Step 13, the friend device requests the friend device OEM server to claim the sharing session.
I.e. redeem SharingSession (SharingSession, friendDeviceHandler).
Step 14, the friend equipment OEM server binds the sharing session and handles of the friend equipment.
I.e., the friend device OEM server executes bind (SharingSession, friendDeviceHandler) binding the sharing session with the handle of the friend device.
And step 15, the friend equipment OEM server sends a claim sharing session request to the vehicle manufacturer OEM server.
I.e. redeem SharingSession (SharingSession, friendDeviceHandler). The claim sharing session request carries parameters including handles to the sharing session and friend devices.
Step 16, the OEM server of the garage binds the sharing session, CCC owner key and handles of friend devices.
I.e., bind (SharingSession, ownerKeyID, friendDeviceHandler).
Step 17, the OEM server of the driver sends the claim session response ready to the OEM server of the friend device.
I.e. redeemSessionResponse.
Step 18, the friend device OEM server sends a claim session response to the friend device.
I.e. redeemSessionResponse.
Step 19, the OEM server of the vehicle factory pushes a session ready acknowledgement message to the SBOD.
I.e. push confirm session ready (SharingSession).
Thereafter, the establishment of the bi-directional encrypted channel between the SBOD and the Friend Device is completed, and the SBOD and the Friend Device can begin exchanging subsequent CCC key sharing data.
Referring to fig. 4, after the establishment of the bi-directional encryption channel between the SBOD and the friend device is completed, the process of exchanging CCC key sharing data between the SBOD and the friend device includes the following steps:
step 20, the SBOD packages the sharing key creation request.
I.e., wrap 'Key Creation Request'.
Step 21, the SBOD sends a sharing key creation request to the OEM server of the vehicle factory.
I.e., createSharedKey (ownerKeyId, keyCreationRequest, sharingSession).
Step 22, the OEM server in the factory obtains the device identification (i.e. handle of friend device) of the registered friend device based on the sharing session (SharingSession).
Step 23, the OEM server of the garage sends event notification created by the sharing key to the OEM server of the friend device.
eventNotification (CREAT_SHARED_ KEY, keyCreationRequest, sharingSession), the notification described in step 23.
Step 24, the friend device OEM server obtains the device identification (i.e., friendDeviceHandler) of the registered friend device based on the sharing session (SharingSession).
Step 25, the friend equipment OEM server pushes a sharing key creation request to the friend equipment.
I.e. PUSH (KeyCreationRequest, sharingSession).
Step 26, the friend device OEM server sends an event notification response to the truck OEM server.
I.e. eventnottification response.
Step 27, the friend device unpacks the sharing key creation request and generates a pair of asymmetric CCC sharing keys, and then packages the sharing key signature request.
The unique key creation request is unpacked, and the unique key signature request is packed.
Step 28, the friend device sends a share key signature request to the friend device OEM server.
I.e., sign sharedkey (KeySigningRequest, sharingSession).
Step 29, the friend equipment OEM server sends a share key signature request to the garage OEM server.
I.e., sign sharedkey (KeySigningRequest, sharingSession).
Step 30, the OEM server of the vehicle factory obtains the owner key identification (OwnerKeyID) based on the sharing session (SharingSession).
Step 31, the OEM server of the vehicle factory sends an event notification sharing the key signature to the SBOD.
eventNotification (sign_SHARED_ KEY, keySigningRequest, ownerKeyId, sharingSesison), the notification described in step 31.
Step 32, the SBOD generates a CCC sharing key and the SBOD binds friend key information and fleet management server sharing information.
I.e., bind (friendKeyId, fmsSharingId). The SBOD also packages the shared key import request, wrap (importRequest).
Step 33, the SBOD sends a shared key import request to the OEM server of the vehicle factory.
I.e., inportsharedkey (inportrequest, sharingSession).
Step 34, the OEM server in the factory obtains the handle of the registered friend device based on the sharing session (SharingSession).
Step 35, the OEM server of the garage sends a sharing key import request to the friend device server.
I.e., eventnotifiiton (impurt _ SHARED _ KEY, inportrequest, sharingSession).
Step 36, the friend device server obtains the handle of the registered friend device based on the sharing session (SharingSession).
Step 37, the friend device server pushes a sharing key import request to the friend device.
I.e. PUSH (inportrequest, sharingSession).
Step 38, the friend device feeds back the response sent by the sharing key import request to the OEM server of the vehicle factory.
I.e. eventnottification response.
Step 39, the OEM server of the vehicle factory sends a response to the SBOD that the shared key import request has been sent.
I.e., the inportsharedkeyresponse.
And step 40, the friend equipment unpacks the sharing key introduction request to obtain the CCC sharing key generated by the SBOD.
I.e., unrapkey 'inportrequest'. After the friend equipment is led in the sharing key, the sharing key and the vehicle terminal can be used for checking the signature, so that the digital key function is realized.
Step 41, the friend device sends a key tracking request to the friend device OEM server.
I.e., a trackKey (codetchain, inportrequest, devicePrivacyEncryptionKey,
devicePrivacyEncryptionVersion)。
the key tracking request carries parameters including: certificate chain (certChain), input request (importRequest), signature private key (devicelivacy encryptionkey), private key version (devicelivacy encryptionversion) for KTS registration CCC sharing keys.
Step 42, the friend equipment OEM server sends the key tracking request to the driver equipment server. Namely the trackKey (… …).
And step 43, the vehicle factory equipment server transmits the key tracking request to the KTS.
Step 44, KTS sends a key tracking complete response to the vehicle factory equipment server.
I.e., trackResponse (ktsSignature, uiIdentifier, keyValidFrom, keyValidTo).
Step 45, the vehicle factory equipment server sends the tracking completion response to the friend equipment OEM server. Namely trackResponse (… …).
Step 46, the friend device OEM server pushes the update request to the friend device.
I.e., PUSH (Update). The update request is for the friend device to activate the sharing key.
Step 47, the vehicle factory equipment server acquires the FMSID based on the sharing session (SharingSession).
And 48, the vehicle factory equipment server sends event notification that the sharing key is added to the SBOD.
Namely eventNotification (SHARED_KEY_Added, ownerKeyId, eventData). The CCC is notified that the sharing key has been activated.
Step 49, SBOD binds the owner user and the sharing key certificate instance.
I.e., bind (accountId, sharedkey.instanceca).
Compared with the prior art, the embodiment of the invention opens the fleet management server of the CCC protocol and the digital key system of the ICCE, and generates the CCC sharing key for the friend equipment by using the SBOD, so that the vehicle owner equipment only supporting the ICCE protocol can share the digital key with the friend equipment supporting the CCC, and the digital key sharing convenience among different protocols is improved.
Example two
The embodiment of the invention provides a trans-protocol digital key sharing system, which is configured in a double-protocol digital key system, wherein the double-protocol digital key system comprises: ICCE subsystem and CCC subsystem. The ICCE subsystem comprises: vehicle owner equipment, vehicle machine end, OEM server of vehicle factory and ICCE digital key server. The vehicle side is configured with an ICCE protocol and a CCC protocol. The CCC subsystem includes: friend device, friend device server, fleet management server FMS, key tracking service KTS, and CCC digital key server SBOD. The cross-protocol digital key sharing system 500 includes: CCC master key preset module 502, bi-directional encryption channel setup module 504, and shared key generation module 506.
The CCC master key presetting module 502 is configured to generate a CCC master key based on a master device, a fleet management server, an SBOD, and a factory OEM server, and send the CCC master key to a vehicle terminal, where the vehicle terminal signs a CCC sharing key of a friend device according to the CCC master key.
The bi-directional encryption channel establishment module 504 is configured to establish a key-sharing bi-directional encryption channel between the SBOD and the friend device based on the friend device, the fleet management server, the SBOD, the OEM server, and the friend device server.
The sharing key generation module 506 is configured to obtain the CCC sharing key generated by the SBOD based on the two-way encrypted channel friend device.
Optionally, the CCC master key preset module 502 is specifically configured to request, by a master device, a FMS, a SBOD, and a VIN number of a vehicle-side to which an OEM server of a vehicle factory is added; the OEM server of the automobile factory requests the SBOD to generate a CCC main key of the automobile machine end, the SBOD sends the generated CCC main key to the automobile machine end, and the automobile machine end signs the CCC sharing key of the friend equipment according to the CCC main key.
Optionally, the bidirectional encryption channel establishment module 504 is specifically configured to initiate a key sharing request to the fleet management server by the friend device according to the sharing request of the vehicle owner device; the SBOD sends a sharing session creation request to the OEM server of the garage according to the key sharing request, and the OEM server of the garage creates the sharing session and binds the identification of the CCC owner key with the sharing session; the SBOD associates the sharing session with the fleet management server according to the sharing session creation information fed back by the OEM server of the vehicle factory, and generates a session key of the sharing session; the fleet management server sends the URL of the sharing session and a session key fed back by the SBOD to the friend equipment; the friend equipment associates the handle of the friend equipment with the sharing session and sends the handle of the friend equipment to the friend equipment server; the friend device server binding the sharing session and the friend device handle; and after binding the sharing session, the identification of the CCC owner key and the handle of the friend equipment, the OEM server of the vehicle factory informs the SBOD that the sharing session is ready to be completed.
Optionally, the bidirectional encryption channel establishment module 504 is further configured to send, by the fleet management server, the shared key configuration data obtained from the OEM server of the vehicle factory to the SBOD before the friend device initiates a key sharing request to the fleet management server according to the sharing request of the vehicle owner device.
Optionally, the sharing key generating module 506 is specifically configured to package the request for creating the sharing key by using the SBOD and send the request to the OEM server of the vehicle factory; the OEM server and the friend equipment server send the sharing key creation request to the friend equipment sequentially based on the handle of the friend equipment; the friend equipment analyzes the sharing key creation request, generates an asymmetric sharing key pair, generates a signature request according to the asymmetric sharing key pair, and sends the signature request to the SBOD through the friend equipment server and the OEM server of the vehicle factory; the SBOD generates the CCC sharing key according to the signature request, and sends the CCC sharing key to the friend equipment through the OEM server of the vehicle factory and the friend equipment server; and the friend equipment acquires the CCC sharing key and stores the key.
Optionally, the sharing key generating module 506 may be further configured to register the CCC sharing key based on the friend device server, the OEM server of the vehicle factory, and the KTS after the friend device obtains and stores the CCC sharing key.
Optionally, the cross-protocol digital key sharing system 500 may further include: the determining module is configured to trigger the sharing key generating module 506 when the friend device determines that the sharing key is the CCC sharing key according to the key sharing request sent by the owner device.
Optionally, the cross-protocol digital key sharing system 500 may also include a pre-configuration module for adding a vehicle factory OEM server to the CCC subsystem.
A third embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, which, when being executed by a computer processor, is adapted to carry out the technical solution of any of the method embodiments.
From the above description of embodiments, it will be clear to a person skilled in the art that the present invention may be implemented by means of software and necessary general purpose hardware, but of course also by means of hardware, although in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, etc., including several instructions for causing a computer device (which may be a personal computer, a server, a grid device, etc.) to execute the method according to the embodiments of the present invention.
It should be noted that, in the embodiment of the sharing device, each unit and module included are only divided according to the functional logic, but not limited to the above-mentioned division, so long as the corresponding functions can be implemented; in addition, the specific names of the functional units are also only for distinguishing from each other, and are not used to limit the protection scope of the present invention.
Note that the above is only a preferred embodiment of the present invention and the technical principle applied. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, while the invention has been described in connection with the above embodiments, the invention is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the invention, which is set forth in the following claims.

Claims (10)

1. A cross-protocol digital key sharing method, which is characterized by being applied to a double-protocol digital key system, wherein the double-protocol digital key system comprises: an ICCE subsystem and a CCC subsystem; the ICCE subsystem includes: the vehicle owner equipment, the vehicle machine end, the OEM server of the vehicle factory and the ICCE digital key server; the vehicle-mounted terminal is configured with an ICCE protocol and a CCC protocol; the CCC subsystem includes: friend equipment, friend equipment server, fleet management server FMS, key tracking service KTS and CCC digital key server SBOD;
The method comprises the following steps:
generating a CCC (common control code) main key based on the main equipment, a fleet management server, an SBOD (base station outside data) and the OEM server of the vehicle factory and issuing the CCC main key to the vehicle terminal for the vehicle terminal to sign the CCC sharing key of the friend equipment according to the CCC main key;
establishing a key sharing bidirectional encryption channel between the SBOD and the friend equipment based on the friend equipment, a fleet management server, the SBOD, a vehicle manufacturer OEM server and the friend equipment server;
and acquiring the CCC sharing key generated by the SBOD by the friend equipment based on the bidirectional encryption channel.
2. The cross-protocol digital key sharing method according to claim 1, wherein the generating and issuing the CCC master key to the vehicle side based on the vehicle owner device, the fleet management server, the SBOD, and the vehicle factory OEM server includes:
the vehicle owner equipment requests the FMS, the SBOD and the OEM server to add the VIN number of the vehicle end;
the OEM server of the vehicle factory requests the SBOD to generate a CCC main key of the vehicle terminal, and the SBOD sends the generated CCC main key to the vehicle terminal for the vehicle terminal to sign the CCC sharing key of the friend equipment according to the CCC main key.
3. The cross-protocol digital key sharing method according to claim 1, wherein the establishing a two-way encrypted channel for key sharing between the SBOD and the friend device based on the friend device, the fleet management server, the SBOD, the vehicle-factory OEM server, and the friend device server comprises:
the friend equipment initiates a key sharing request to the fleet management server according to the sharing request of the vehicle owner equipment;
the SBOD sends a sharing session creation request to the OEM server of the garage according to the key sharing request, and the OEM server of the garage creates the sharing session and binds the identification of the CCC owner key with the sharing session;
the SBOD associates the sharing session with the fleet management server according to the sharing session creation information fed back by the OEM server of the vehicle factory, and generates a session key of the sharing session;
the fleet management server sends the URL of the sharing session and a session key fed back by the SBOD to the friend equipment;
the friend equipment associates the handle of the friend equipment with the sharing session and sends the handle of the friend equipment to the friend equipment server;
The friend device server binding the sharing session and the friend device handle;
and after binding the sharing session, the identification of the CCC owner key and the handle of the friend equipment, the OEM server of the vehicle factory informs the SBOD that the sharing session is ready to be completed.
4. The cross-protocol digital key sharing method according to claim 3, wherein before the friend device initiates a key sharing request to the fleet management server according to the sharing request of the vehicle owner device, the method further comprises:
the fleet management server sends the shared key configuration data obtained from the OEM server to the SBOD.
5. The cross-protocol digital key sharing method according to claim 1, wherein the acquiring the CCC sharing key generated by the SBOD by the friend device based on the bidirectional encryption channel includes:
the SBOD packages and shares a key creation request and sends the key creation request to the OEM server of the vehicle factory;
the OEM server and the friend equipment server send the sharing key creation request to the friend equipment sequentially based on the handle of the friend equipment;
The friend equipment analyzes the sharing key creation request, generates an asymmetric sharing key pair, generates a signature request according to the asymmetric sharing key pair, and sends the signature request to the SBOD through the friend equipment server and the OEM server of the vehicle factory;
the SBOD generates the CCC sharing key according to the signature request, and sends the CCC sharing key to the friend equipment through the OEM server of the vehicle factory and the friend equipment server;
and the friend equipment acquires the CCC sharing key and stores the key.
6. The cross-protocol digital key sharing method of claim 1, wherein after the friend device obtains and stores the CCC sharing key, the method further comprises:
registering the CCC sharing key based on the friend device server, the OEM server of the vehicle manufacturer, and the KTS.
7. The cross-protocol digital key sharing method of claim 1, wherein prior to the establishing a two-way encrypted channel of key sharing between the SBOD and the friend device based on the friend device, fleet management server, SBOD, factory OEM server, friend device server, the method further comprises:
And the friend equipment determines that the sharing key is a CCC sharing key according to the key sharing request sent by the owner equipment.
8. The cross-protocol digital key sharing method of claim 1, wherein before the generating and issuing CCC master keys to the vehicle side based on the vehicle owner device, fleet management server, SBOD, and the vehicle factory OEM server, the method further comprises:
and adding the OEM server of the vehicle factory into the CCC subsystem.
9. A cross-protocol digital key sharing system configured in a dual-protocol digital key system, the dual-protocol digital key system comprising: an ICCE subsystem and a CCC subsystem; the ICCE subsystem includes: the vehicle owner equipment, the vehicle machine end, the OEM server of the vehicle factory and the ICCE digital key server; the vehicle-mounted terminal is configured with an ICCE protocol and a CCC protocol; the CCC subsystem includes: friend equipment, friend equipment server, fleet management server FMS, key tracking service KTS and CCC digital key server SBOD;
the cross-protocol digital key sharing system comprises:
the CCC owner key presetting module is used for generating a CCC owner key based on the owner equipment, the fleet management server, the SBOD and the OEM server of the garage and sending the CCC owner key to the vehicle terminal for the vehicle terminal to sign the CCC sharing key of the friend equipment according to the CCC owner key;
The two-way encryption channel establishment module is used for establishing a key sharing two-way encryption channel between the SBOD and the friend equipment based on the friend equipment, the fleet management server, the SBOD, the OEM server of a vehicle factory and the friend equipment server;
and the sharing key generation module is used for acquiring the CCC sharing key generated by the SBOD based on the two-way encryption channel and the friend equipment.
10. A computer readable storage medium having stored thereon a computer program, wherein the program when executed by a processor implements the key sharing method of any of claims 1-8.
CN202311145789.5A 2023-09-07 2023-09-07 Cross-protocol digital key sharing method, system and computer readable storage medium Active CN116887221B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311145789.5A CN116887221B (en) 2023-09-07 2023-09-07 Cross-protocol digital key sharing method, system and computer readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311145789.5A CN116887221B (en) 2023-09-07 2023-09-07 Cross-protocol digital key sharing method, system and computer readable storage medium

Publications (2)

Publication Number Publication Date
CN116887221A CN116887221A (en) 2023-10-13
CN116887221B true CN116887221B (en) 2023-11-24

Family

ID=88257253

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311145789.5A Active CN116887221B (en) 2023-09-07 2023-09-07 Cross-protocol digital key sharing method, system and computer readable storage medium

Country Status (1)

Country Link
CN (1) CN116887221B (en)

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6108425A (en) * 1997-06-30 2000-08-22 International Business Machines Corporation Method and apparatus for controlling the configuration of a cryptographic processor
CN101706372A (en) * 2009-11-10 2010-05-12 奇瑞汽车股份有限公司 Electronic-control vehicle remote diagnosis system and diagnosis method thereof
WO2015056410A1 (en) * 2013-10-17 2015-04-23 株式会社デンソー Electronic key system, in-vehicle apparatus, and handheld device
WO2020218627A1 (en) * 2019-04-20 2020-10-29 (주)케이스마텍 Method and system for digital key sharing service for vehicle
CN111935302A (en) * 2020-08-20 2020-11-13 捷德(中国)科技有限公司 Key management device, method and equipment
CN112584355A (en) * 2020-12-13 2021-03-30 北京明朝万达科技股份有限公司 Key cooperation method, system and medium for inter-vehicle communication
CN113989958A (en) * 2021-10-14 2022-01-28 广州小鹏汽车科技有限公司 Digital key sharing system, method and apparatus, vehicle and storage medium
CN115766021A (en) * 2022-10-27 2023-03-07 联合汽车电子有限公司 Back-end system
CN115966038A (en) * 2021-10-13 2023-04-14 华为技术有限公司 Digital key opening method, equipment and system
CN116489621A (en) * 2023-04-18 2023-07-25 小米汽车科技有限公司 Vehicle key sharing method, device, equipment and medium
WO2023137757A1 (en) * 2022-01-24 2023-07-27 Oppo广东移动通信有限公司 Digital vehicle key sharing method and apparatus, and device and storage medium

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6635102B2 (en) * 2017-10-24 2020-01-22 トヨタ自動車株式会社 Information processing apparatus, information processing method, and program
US20230130457A1 (en) * 2021-10-25 2023-04-27 Salesforce.Com, Inc. Key management providing high availability without key replication

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6108425A (en) * 1997-06-30 2000-08-22 International Business Machines Corporation Method and apparatus for controlling the configuration of a cryptographic processor
CN101706372A (en) * 2009-11-10 2010-05-12 奇瑞汽车股份有限公司 Electronic-control vehicle remote diagnosis system and diagnosis method thereof
WO2015056410A1 (en) * 2013-10-17 2015-04-23 株式会社デンソー Electronic key system, in-vehicle apparatus, and handheld device
WO2020218627A1 (en) * 2019-04-20 2020-10-29 (주)케이스마텍 Method and system for digital key sharing service for vehicle
CN111935302A (en) * 2020-08-20 2020-11-13 捷德(中国)科技有限公司 Key management device, method and equipment
CN112584355A (en) * 2020-12-13 2021-03-30 北京明朝万达科技股份有限公司 Key cooperation method, system and medium for inter-vehicle communication
CN115966038A (en) * 2021-10-13 2023-04-14 华为技术有限公司 Digital key opening method, equipment and system
CN113989958A (en) * 2021-10-14 2022-01-28 广州小鹏汽车科技有限公司 Digital key sharing system, method and apparatus, vehicle and storage medium
WO2023137757A1 (en) * 2022-01-24 2023-07-27 Oppo广东移动通信有限公司 Digital vehicle key sharing method and apparatus, and device and storage medium
CN115766021A (en) * 2022-10-27 2023-03-07 联合汽车电子有限公司 Back-end system
CN116489621A (en) * 2023-04-18 2023-07-25 小米汽车科技有限公司 Vehicle key sharing method, device, equipment and medium

Also Published As

Publication number Publication date
CN116887221A (en) 2023-10-13

Similar Documents

Publication Publication Date Title
US10768918B2 (en) Method and device for downloading profile of operator
US20170161721A1 (en) Method and system for opening account based on euicc
US20130194068A1 (en) Method for providing wireless vehicle access
WO2021135258A1 (en) Method and apparatus for using vehicle based on smart key
JP5952973B2 (en) Mutual authentication method between terminal and remote server via third-party portal
CN112956155B (en) Apparatus and method for negotiating digital certificate between SSP device and server
CN110535665B (en) Method, device and system for signing and issuing same-root certificate on line
CN110381103B (en) Method, device and system for downloading operator configuration file
EP4068834A1 (en) Initial security configuration method, security module, and terminal
CN111783068A (en) Device authentication method, system, electronic device and storage medium
CN110288729A (en) A kind of vehicle starting method and system based on wireless near field communication
CN109583154A (en) A kind of system and method based on Web middleware access intelligent code key
WO2021109967A1 (en) Initial configuration method and terminal device
CN111376865A (en) Vehicle digital key activation method, system and storage medium
US20220311625A1 (en) Certificate Application Method And Device
CN112784310A (en) Certificate management method, certificate authorization center, management node and Internet of vehicles terminal
CN108632037B (en) Public key processing method and device of public key infrastructure
CN109451483B (en) eSIM data processing method, equipment and readable storage medium
CN111163063B (en) Edge application management method and related product
CN116887221B (en) Cross-protocol digital key sharing method, system and computer readable storage medium
CN112514323A (en) Electronic device for processing digital key and operation method thereof
CN110827018A (en) Method for two-dimensional code intercommunication use between public traffic APP clients
CN112616148B (en) Authentication method, authentication platform and authentication system
WO2016065919A1 (en) Method for transmitting configuration information, mobile terminal and device management server as well as storage medium
CN116346978B (en) Terminal device and data processing method of terminal device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant