Method and device for transmitting vehicle identification number

Abstract

Disclosed are a method and device for transmitting a vehicle identification number. According to an embodiment of the present disclosure, the method for transmitting a vehicle identification number performed by a server may comprise the steps of: encrypting the vehicle identification number by using a symmetric key to generate an encrypted vehicle identification number, and transmitting vehicle identification number data including a parameter for the encrypted vehicle identification number to an electronic control device via a gateway; receiving vehicle identification number reception confirmation data from the electronic control device via the gateway on the basis that the electronic control device decrypts the encrypted vehicle identification number to generate the vehicle identification number and hashes the vehicle identification number and the symmetric key to generate a hashed vehicle identification number; verifying an electronic signature on the basis of the vehicle identification number reception confirmation data; and generating the hashed vehicle identification number by hashing the vehicle identification number and the symmetric key when the electronic signature is verified.

Description

Method and device for transmitting vehicle identification number

[0001] The present invention relates to a method and device for transmitting a Vehicle Identification Number (VIN). More specifically, the present invention relates to a method and device for encrypting a VIN and transmitting it to an Electronic Control Unit (ECU) via a vehicle gateway.

[0002] The content described below merely provides background information related to the present embodiment and does not constitute prior art.

[0003] The electric vehicle market is steadily growing, driven by battery development and the development of charging infrastructure. Furthermore, advancements in technologies like artificial intelligence, mobile / wireless communications, cloud computing, sensors, and precision positioning are driving the advancement of autonomous driving in automobiles. In this environment, vehicles are equipped with devices driven by electronic control units (ECUs) to perform various functions and services, including driving safety, driver assistance, and autonomous driving. As the number of devices installed in vehicles increases, the importance of software to efficiently operate these devices grows.

[0004] Devices installed in vehicles connect to external networks via the in-vehicle network (IVN). This allows these devices to exchange driving-related information both internally and externally with other devices within the vehicle, other vehicles, or external devices. The IVN is a wired and wireless communication network between sensors and electronic control units within the vehicle.

[0005] In these network environments, vehicle security, which protects personal information, smart keys, and vehicle operation software registered in the vehicle from external attacks, becomes crucial. Malfunctions in the vehicle's internal software due to external attacks can have devastating consequences for the vehicle and its driver. Therefore, research is needed on technologies that strengthen security against external attacks when data is transmitted between in-vehicle devices and external devices.

[0006] The purpose of this disclosure is to have a server encrypt a vehicle identification number (VIN) and transmit it to an electronic control unit.

[0007] Additionally, according to one embodiment, the electronic control unit is configured to decrypt the encrypted vehicle identification number, hash the vehicle identification number, and use the hashed vehicle identification number.

[0008] The problems to be solved by the present invention are not limited to the problems mentioned above, and other problems not mentioned will be clearly understood by those skilled in the art from the description below.

[0009] According to the present disclosure, a method for transmitting a vehicle identification number performed by a server may include a process of encrypting a vehicle identification number using a symmetric key to generate an encrypted vehicle identification number, transmitting vehicle identification number data including parameters for the encrypted vehicle identification number to an electronic control device through a gateway, a process of receiving vehicle identification number reception confirmation data from the electronic control device through the gateway based on the electronic control device decrypting the encrypted vehicle identification number to generate the vehicle identification number and hashing the vehicle identification number and the symmetric key to generate a hashed vehicle identification number, a process of verifying an electronic signature based on the vehicle identification number reception confirmation data, and a process of hashing the vehicle identification number and the symmetric key to generate the hashed vehicle identification number when the electronic signature is verified.

[0010] According to the present disclosure, a method for transmitting a vehicle identification number performed by an electronic control device may include a process of receiving vehicle identification number data including parameters for an encrypted vehicle identification number from a server through a gateway, a process of verifying an electronic signature based on the vehicle identification number data, a process of decrypting the encrypted vehicle identification number based on the vehicle identification number data to generate a vehicle identification number, a process of hashing the vehicle identification number and a symmetric key based on the vehicle identification number data to generate a hashed vehicle identification number, and a process of transmitting vehicle identification number reception confirmation data to the server through the gateway.

[0011] According to the present disclosure, a server includes a memory and a plurality of processors, and at least one processor among the plurality of processors encrypts a vehicle identification number using a symmetric key to generate an encrypted vehicle identification number, transmits vehicle identification number data including parameters for the encrypted vehicle identification number to an electronic control unit through a gateway, and based on the electronic control unit decrypting the encrypted vehicle identification number to generate the vehicle identification number and hashing the vehicle identification number and the symmetric key to generate a hashed vehicle identification number, receives vehicle identification number reception confirmation data from the electronic control unit through the gateway, verifies an electronic signature based on the vehicle identification number reception confirmation data, and when the electronic signature is verified, hashes the vehicle identification number and the symmetric key to generate the hashed vehicle identification number.

[0012] According to the present disclosure, an electronic control device includes a memory and a plurality of processors, and at least one processor among the plurality of processors receives vehicle identification number data including parameters for an encrypted vehicle identification number from a server through a gateway, verifies an electronic signature based on the vehicle identification number data, decrypts the encrypted vehicle identification number based on the vehicle identification number data to generate a vehicle identification number, hashes the vehicle identification number and a symmetric key based on the vehicle identification number data to generate a hashed vehicle identification number, and transmits vehicle identification number reception confirmation data to the server through the gateway.

[0013] According to the present disclosure, the Vehicle Identification Number (VIN) is encrypted, so that the plaintext VIN cannot be disclosed to an attacker.

[0014] Additionally, according to one embodiment, there is an effect of preventing theft of a vehicle identification number by using a hashed vehicle identification number.

[0015] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

[0016] FIG. 1 is a diagram for explaining a process of using a functional subscription service according to one embodiment of the present disclosure.

[0017] FIG. 2 is a diagram for explaining a certificate-based FoD (Feature of Demand) service ecosystem using a public key structure according to one embodiment of the present disclosure.

[0018] FIG. 3 is a diagram illustrating a vehicle connected to a server via a network according to one embodiment of the present disclosure.

[0019] FIG. 4 is a block diagram illustrating a vehicle connected to an external network according to one embodiment of the present disclosure.

[0020] FIG. 5 is a block diagram illustrating a gateway according to one embodiment of the present disclosure.

[0021] FIG. 6 is a block diagram illustrating a server according to one embodiment of the present disclosure.

[0022] FIG. 7 is a diagram for explaining a process of encrypting and transmitting a vehicle identification number (VIN) according to one embodiment of the present disclosure.

[0023] FIG. 8 is a flowchart illustrating a process in which a server transmits a vehicle identification number according to one embodiment of the present disclosure.

[0024] FIG. 9 is a flowchart illustrating a process in which an electronic control device transmits vehicle identification number reception confirmation data according to one embodiment of the present disclosure.

[0025] FIG. 10 is a block diagram schematically illustrating an exemplary computing device that can be used to implement a method according to the present disclosure.

[0026] Hereinafter, some embodiments of the present disclosure will be described in detail using exemplary drawings. When designating components in each drawing, it should be noted that, where possible, identical components are given the same reference numerals, even if they appear in different drawings. Furthermore, when describing the present disclosure, detailed descriptions of related known components or functions will be omitted if they are deemed to obscure the gist of the present disclosure.

[0027] In describing components of embodiments according to the present disclosure, symbols such as first, second, i), ii), a), b) may be used. These symbols are only for distinguishing the components from other components, and the nature, order, or sequence of the components are not limited by the symbols. When a part in the specification is said to "include" or "have" a component, this does not mean that other components are excluded, but rather that other components may be included, unless explicitly stated otherwise.

[0028] The detailed description set forth below, together with the accompanying drawings, is intended to explain exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure may be practiced.

[0029] FIG. 1 is a diagram for explaining a process of using a functional subscription service according to one embodiment of the present disclosure.

[0030] Referring to FIG. 1, in the FoD (Feature of Demand) ecosystem, a driver (110) can subscribe to or cancel a necessary feature of a vehicle, and when a feature expires, the feature can no longer be used. If the driver (110) no longer needs the feature, the driver (110) can transfer the feature to another driver. The driver (110) checks a list of features available for subscription in the vehicle (120) and requests a subscription to a new feature using the driver's (110) personally identifying information (PII), the vehicle identification number (VIN) of the vehicle (120), and payment information (1).

[0031] The vehicle (120) transmits subscription request data to the FoD server (130) to check for new functions (2).

[0032] The FoD server (130) verifies the driver's (110) PII, the vehicle identification number (120) and payment information (3).

[0033] The FoD server (130) installs new features into the vehicle (120) using OTA (Over The Air) updates (4).

[0034] The central control unit (CCU) of the vehicle (120) receives installation data for a new function and then verifies the format of the installation data using the Unified Diagnostic Services (UDS) protocol. Here, the UDS protocol is a standard protocol for vehicle diagnosis.

[0035] The central control unit of the vehicle (120) routes installation data to the electronic control device using the ID of the electronic control device (5).

[0036] The electronic control unit activates and operates new functions through this routing (6). For example, the electronic control unit can activate the Lane Support System (LSS) function.

[0037] Assets of a FoD service may include software, cryptographic data, communication data, personal information, and log data. Software is required to operate the FoD service. Cryptographic data includes public keys, private keys, certificates, passwords, seeds, and salts for encryption, decryption, and hash calculation. Communication data may include data between the vehicle, central control unit, electronic control unit, and FoD server for installing features in the vehicle. Personal information may include PII for driver and vehicle identification, vehicle identification number, payment information, and the driver's FoD service subscription list. Log data may include data regarding CCU / ECU status, feature ON / OFF events, and feature subscription timestamps.

[0038] In the FoD ecosystem, various security threats may exist, such as DDoS replay, attacker attacks, and impersonation against the assets of these FoD services.

[0039] For example, an attacker may exploit the payment information of the driver (110) when the driver (110) requests a subscription to a new feature in the vehicle (120). Accordingly, the driver (110) may subscribe to the feature requested by the attacker. The attacker may exploit the vehicle identification number (VIN) when the FoD server (130) installs a new feature in the vehicle (120) to prevent the installation. The attacker may eavesdrop on the feature installation data transmitted by the FoD server (130) to the vehicle (120) and exploit the feature installation data to subscribe to the feature without paying the subscription fee. The attacker may attack the FoD server (130) and the central control unit to manipulate the feature installation data, thereby causing a malfunction of the electronic control unit or triggering a function that the driver (110) does not want. An attacker can disrupt the installation by performing a DDoS attack on the FoD server (130), the central control unit, or the electronic control unit when the FoD server (130) installs a new feature in the vehicle (120).

[0040] There are various methods to prevent security attacks by these attackers.

[0041] The first method encrypts payment information, stores PII and vehicle identification numbers separately from other personal information, and destroys payment information that is no longer needed so that it cannot be recovered.

[0042] The second method is to use an encrypted VIN or a value that replaces the VIN in the FoD service.

[0043] The third method is to encrypt the function installation data using an encryption mechanism that uses a symmetric key or asymmetric key.

[0044] The fourth method is to maintain the integrity of the function installation data by using a digital signature or hash function.

[0045] The fifth method is to defend against DDoS attacks by using firewalls, traffic monitoring, etc.

[0046] FIG. 2 is a diagram for explaining a certificate-based FoD (Feature of Demand) service ecosystem using a public key structure according to one embodiment of the present disclosure.

[0047] Referring to FIG. 2, the integrity and confidentiality of the functional installation data transmitted by the FoD server (210) to the vehicle (220) are guaranteed based on a certificate using a public key infrastructure (PKI). The certificate-based FoD service ecosystem using a public key structure includes two major processes: certificate issuance and certificate use.

[0048] Certificate issuance

[0049] When a driver subscribes to a new feature, the vehicle (220) transmits subscription request data to the FoD server (210). The subscription request data may include the type of feature, PII, vehicle identification number, and payment information. The FoD server (210) receives the subscription request data, stores the type of feature, and then transmits the subscription request data to a CA server (Certificate Authority server, 230). The CA server (230) verifies the subscription request data and issues a certificate. The certificate may be composed of a version, a serial number, a tag, a vehicle identification number, an electronic control unit ID, a function flag, a challenge, an issuer, an order ID, an issuance date, an effective date, an expiration date, a reservation, and a signature.

[0050] The CA server (230) issues a certificate and then signs the certificate based on a digital signature technology using a private key. The CA server (230) encrypts the certificate using a symmetric key-based encryption mechanism. Here, the symmetric key can be safely distributed in advance. The CA server (230) transmits the encrypted data to the FoD server (210). The FoD server (210) searches for the ID of the corresponding electronic control device using the type of the pre-stored function and adds the ID of the corresponding electronic control device to the encrypted data. The FoD server (210) transmits the encrypted data with the ID of the corresponding electronic control device added to the vehicle (220). The central control unit of the vehicle (220) routes the encrypted data to the corresponding electronic control device using the ID of the corresponding electronic control device.

[0051] The electronic control unit may be composed of a host and an HSM (Hardware Security Module). The host receives encrypted data and transmits it to the HSM. The HSM decrypts the encrypted data using a pre-shared symmetric key and verifies the signature using the public key of the CA server (230). The HSM shares the verification result with the host. If the verification result is correct, the general fields such as the vehicle identification number, electronic control unit ID, and function flags are verified to be correct. If all fields are correct, the HSM re-verifies the signature, encrypts both the general fields and the signature using the pre-shared symmetric key, and stores the encrypted data in a storage. The electronic control unit signs the challenge field of the certificate and returns both the field and the signature to the CA server (230). The CA server (230) verifies the signature using the public key of the electronic control unit. Accordingly, mutual authentication between the CA server (230) and the electronic control unit is guaranteed.

[0052] Use of certificates

[0053] When the vehicle (220) is turned on, the central control unit of the vehicle (220) identifies the list of pre-installed functions and the ID of the corresponding electronic control unit. The electronic control unit obtains encrypted data from the storage and verifies the signature in the HSM. The host verifies general fields such as the vehicle identification number, function flag, and expiration date. If the verification result is correct, the electronic control unit activates the function.

[0054] FIG. 3 is a diagram illustrating a vehicle connected to a server via a network according to one embodiment of the present disclosure.

[0055] Referring to FIG. 3, a vehicle (310) may be connected to a server (320) that provides functions or services related to the vehicle (310) through a mobile network or wireless network such as LTE, 5G, or Wi-Fi.

[0056] FIG. 4 is a block diagram illustrating a vehicle connected to an external network according to one embodiment of the present disclosure.

[0057] Referring to FIG. 4, the vehicle (310) includes all or part of a gateway (410) connected to an external network and an internal network, and subsystems connected to the internal network. The vehicle (310) and each of its components may be implemented in hardware or software, or a combination of hardware and software. Furthermore, the functions of each component may be implemented in software, and one or more processors may be implemented to execute the functions of the software corresponding to each component.

[0058] The gateway (410) is a system that controls communication and has the function of safely transmitting data within the vehicle (310). The subsystems may include a power train subsystem, a body subsystem, a chassis subsystem, an infotainment subsystem, etc. A subsystem includes one or more components that perform similar functions and are connected by the same type of internal bus. Each component is controlled and driven by one or more ECUs (420).

[0059] The powertrain subsystem is a collection of components that generate the driving force of the vehicle (310). The powertrain subsystem may include components such as an engine, motor, transmission, battery, and generator. The body subsystem is a collection of components that enhance driver convenience and safety. The body subsystem may include components such as seats, heating / ventilation / air conditioning, lighting, doors, and windows. The chassis subsystem is a collection of components necessary for driving the vehicle (310). The chassis subsystem may include components related to steering, brakes, and tires. The infotainment subsystem is a collection of components related to driving guidance or multimedia of the vehicle (310). The infotainment subsystem may include components such as a navigation system, a multimedia system, and a head-up display.

[0060] The internal network connecting the gateway (410) and the components constituting the subsystems may be a communication protocol such as LIN (Local Interconnect Network), CAN (Control Area Network), CAN-FD, FlexRay, MOST (Media Oriented Systems Transport), Ethernet, etc. The components within the subsystems transmit and receive data to each other through the gateway (410). The gateway (410) may transmit an encrypted vehicle identification number received from the server (320) to one or more ECUs (420). The gateway (410) may transmit vehicle identification number reception confirmation data received from one or more ECUs (420) to the server (320).

[0061] FIG. 5 is a block diagram illustrating a gateway according to one embodiment of the present disclosure.

[0062] Referring to FIG. 5, the gateway (410) may include all or part of a central control unit (510), a communication unit (520), an ECU list storage unit (530), and a storage unit (540). The gateway (410) and each of its components may be implemented in hardware or software, or a combination of hardware and software. In addition, the functions of each component may be implemented in software, and one or more processors may be implemented to execute the functions of the software corresponding to each component.

[0063] The central control unit (510) controls the overall operation of the vehicle (310). The central control unit (510) can control the operation of the vehicle (310) by controlling the electronic control device included in at least one subsystem according to the driver's request, driving conditions, etc. The functions performed by the central control unit (510) may include driving management, parking management, remote diagnosis, remote control, FoD management, software update, and security management. FoD management is a type of subscription service management, such as downloading and activating a new function from a server or activating a deactivated function. The central control unit (510) performs the setup or cancellation of the subscription service. The central control unit (510) can check whether the activated function is a function selected by the customer or whether the activation of the function is due to an illegal method, and can activate or deactivate the function based on the results.

[0064] Software update is a service performed by the central control unit (510) when software update conditions are met in a vehicle to which OTA is applied. Software update may include updating the software that manages the overall operation of the vehicle as well as the firmware installed in the electronic control unit of each component.

[0065] Security management may include functions or services related to vehicle security or the authentication of external devices accessing the in-vehicle network. Security threats related to vehicles may include firmware tampering, remote control hacking, CAN tampering, illegal vehicle operation, and denial of service. Security threats related to external networks may also include communication eavesdropping and message tampering. Security management may include functions for detecting and responding to intrusions into the vehicle's internal network via external networks (Intrusion Detection System (IDS)) and services for recording data related to security events (Event Data Recorder (EDR).

[0066] The communication unit (520) transmits and receives data with the server (320) through an external network, and transmits and receives data with the subsystem components and electronic control devices through an internal network.

[0067] The ECU list storage unit (530) stores a list of ECUs and determines an electronic control device matching the ID of the electronic control device within the list of ECUs.

[0068] The storage unit (540) stores data received from an external network and an internal network or data related to the operation of the vehicle (310).

[0069] FIG. 6 is a block diagram illustrating a server according to one embodiment of the present disclosure.

[0070] Referring to FIG. 6, the server (320) may include all or part of a management unit (610), a communication unit (620), a storage unit (630), and an encryption unit (640). The server (320) and each of its components may be implemented in hardware or software, or a combination of hardware and software. In addition, the functions of each component may be implemented in software, and one or more processors may be implemented to execute the functions of the software corresponding to each component. The server (320) may be a general back-end server capable of communicating with the vehicle (310).

[0071] The management unit (610) manages operations according to the request of the vehicle (310). For example, the management unit (610) can manage operations such as software updates, transmission of data related to FoD, and security / authentication of the vehicle.

[0072] The communication unit (620) connects to the vehicle (310) through an external network and transmits and receives data.

[0073] The storage unit (630) stores data related to driving of the vehicle (310) and manages the version of software installed in each vehicle, activated functions, and authentication-related information.

[0074] The encryption unit (640) manages a symmetric key and a key for electronic signatures, and encrypts the vehicle identification number using the symmetric key. The encryption unit (640) generates data composed of parameters including the encrypted vehicle identification number. The encryption unit (640) verifies the value of the electronic signature of the parameters, hashes the vehicle identification number, and generates and stores the hashed vehicle identification number.

[0075] FIG. 7 is a diagram for explaining a process of encrypting and transmitting a vehicle identification number according to one embodiment of the present disclosure.

[0076] Referring to FIG. 7, the server (320) and the electronic control device (420) share, store, and manage encryption methods using symmetric keys, hash methods, HMAC (Hash-based Message Authentication Code), and electronic signature methods in advance.

[0077] For example, encryption methods using symmetric keys can be AES (Advanced Encryption Standard)-128, AES-192, and AES-256, etc. Hash methods can be SHA (Secure Hash Algorithm)-0, SHA-1, and SHA-256, etc. Digital signature methods can be RSA (Rivest-Shamir-Adleman), Elgamal, and ECDSA (Elliptic Curve Digital Signature Algorithm), etc.

[0078] The server (320) and the electronic control unit (420) can be connected wirelessly via OTA or connected wiredly via OBD (On-Board Diagnostics)-II.

[0079] In addition to sharing an encryption method using a symmetric key, the server (320) and the electronic control device (420) can derive and use a key using a key derivation function (KDF) based on the symmetric key.

[0080] The server (320) loads a symmetric key and uses the symmetric key to encrypt the vehicle identification number of the vehicle (310) to generate an encrypted vehicle identification number. The server (320) transmits vehicle identification number data including the encrypted vehicle identification number to the gateway (410) (1).

[0081] The vehicle identification number data is data composed of parameters. Here, the parameters constituting the vehicle identification number data may include a parameter indicating an encryption method using a symmetric key (e.g., Enc Flag), a parameter indicating an electronic signature method (e.g., Sign Flag), a parameter indicating a hash method (e.g., Hash Flag), a parameter indicating an ID of an electronic control unit (e.g., ECU ID), a parameter indicating an encrypted vehicle identification number (e.g., Enc_VIN), and a parameter indicating a value obtained by electronically signing the parameters using a key for electronic signature (Sign). Here, the Enc Flag, Sign Flag, and Hash Flag may be targets of attacks if they are disclosed during transmission, and thus may be encrypted and transmitted using a symmetric key.

[0082] The gateway (410) determines an electronic control unit matching the ECU ID among the parameters of the vehicle identification number data by using the ECU ID among the ECU list. The gateway (410) transmits the vehicle identification number data to the electronic control unit (420) matching the ECU ID (2).

[0083] The electronic control unit (420) verifies the method of the electronic signature using the Sign Flag among the parameters of the vehicle identification number data. The electronic control unit (420) verifies the Sign using a key for verifying the electronic signature. The electronic control unit (420) verifies the encryption method using a symmetric key using the Enc Flag among the parameters of the vehicle identification number data and loads the necessary symmetric key. The electronic control unit (420) decrypts the Enc_VIN using the symmetric key to generate the vehicle identification number. The electronic control unit (420) verifies the hash method using the Hash Flag among the parameters of the vehicle identification number data. The electronic control unit (420) hashes the vehicle identification number and the symmetric key using the verified hash method to generate a hashed vehicle identification number (e.g., Hash_VIN). Here, the electronic control unit (420) may generate the Hash_VIN using HMAC instead of using the hash method. When HMAC is used, a symmetric key may be used. The electronic control unit (420) can use Hash_VIN for SDV (Software Defined Vehicle), OTA or FoD services, etc.

[0084] The electronic control unit (420) generates vehicle identification number (VIN) confirmation data and transmits it to the gateway (410) (3). The VIN confirmation data may include Enc_VIN, the ID of the electronic control unit (420), and a sign. The gateway (410) transmits the VIN confirmation data to the server (320) (4).

[0085] The server (320) verifies the Sign among the vehicle identification number (VIN) receipt confirmation data. The server (320) can hash the VIN and a symmetric key to generate a Hash_VIN, which can then be managed by matching it with the VIN. Here, the server (320) can generate the Hash_VIN using HMAC instead of the hash method. When using HMAC, a symmetric key can be used.

[0086] When generating a Hash_VIN, the VIN and symmetric key are hashed, preventing the plaintext VIN from being exposed. A Hash_VIN can encompass both the uniqueness of the VIN and the confidentiality of the symmetric key. For example, if the VIN is 1A2B and the symmetric key is OJ89, the input parameter of the hash function could be 1A2BOJ89. Even if an attacker knows the VIN (1A2B), they cannot deduce the hash value because they do not know the symmetric key.

[0087] FIG. 8 is a flowchart illustrating a process in which a server transmits a vehicle identification number according to one embodiment of the present disclosure.

[0088] Referring to FIG. 8, the management unit (610) of the server (320) loads a symmetric key to be used from the storage unit (630), and the encryption unit (640) of the server (320) encrypts the vehicle identification number using the loaded symmetric key to generate an encrypted vehicle identification number (Enc_VIN) (S810).

[0089] The server (320) transmits the vehicle identification number data including parameters for the encrypted vehicle identification number to the electronic control unit (420) via the gateway (520) through the communication unit (620) (S820).

[0090] The vehicle identification number data may include a parameter for an encrypted vehicle identification number (Enc_VIN), a parameter for an encryption method using a symmetric key (Enc Flag), a parameter for an electronic signature method (Sign Flag), a parameter for a hash method (Hash Flag), a parameter for an ID of an electronic control unit (ECU ID), and a parameter for a value of an electronic signature (Sign).

[0091] The server (320) receives vehicle identification number reception confirmation data from the electronic control device (420) via the gateway (410) based on the electronic control device (420) decrypting the encrypted vehicle identification number to generate a vehicle identification number and hashing the vehicle identification number and a symmetric key to generate a hashed vehicle identification number (Hash_VIN) (S830).

[0092] The vehicle identification number receipt confirmation data may include a parameter for the encrypted vehicle identification number (Enc_VIN), a parameter for the ID of the electronic control unit (ECU ID), and a parameter for the value of the electronic signature (Sign).

[0093] The server (320) verifies the electronic signature based on the vehicle identification number receipt confirmation data (S840).

[0094] When an electronic signature is verified, the server (320) can hash the vehicle identification number and symmetric key to generate a hashed vehicle identification number and manage it by matching it with the vehicle identification number (S850).

[0095] FIG. 9 is a flowchart illustrating a process in which an electronic control device transmits vehicle identification number reception confirmation data according to one embodiment of the present disclosure.

[0096] Referring to FIG. 9, the electronic control device (420) receives vehicle identification number data including parameters for an encrypted vehicle identification number from the server (320) through the gateway (410) (S910).

[0097] The vehicle identification number data may include a parameter for an encrypted vehicle identification number (Enc_VIN), a parameter for an encryption method using a symmetric key (Enc Flag), a parameter for an electronic signature method (Sign Flag), a parameter for a hash method (Hash Flag), a parameter for an ID of an electronic control unit (ECU ID), and a parameter for a value of an electronic signature (Sign).

[0098] The electronic control unit (420) verifies an electronic signature based on the vehicle identification number data (S920). Specifically, the electronic control unit (420) verifies which electronic signature the vehicle identification number data is signed with based on a parameter (Sign Flag) for the electronic signature method, loads a key for signature verification based on the verification, and verifies a parameter (Sign) for the electronic signature value using the loaded key.

[0099] The electronic control unit (420) decrypts the encrypted vehicle identification number based on the vehicle identification number data to generate the vehicle identification number (S930). Specifically, the electronic control unit (420) can determine which symmetric key is used for encryption based on a parameter (Enc Flag) for an encryption method using a symmetric key, load the required symmetric key based on the determination, and decrypt the parameter (Enc_VIN) for the encrypted vehicle identification number using the symmetric key to generate the vehicle identification number.

[0100] The electronic control unit (420) generates a hashed vehicle identification number (VIN) by hashing the VIN and a symmetric key based on the VIN data (S940). Specifically, the electronic control unit (420) can determine which hashing method to use based on a parameter (Hash Flag) for the hashing method, and generate a hashed VIN (Hash_VIN) by hashing the decrypted VIN and symmetric key.

[0101] The electronic control unit (420) generates vehicle identification number (VIN) reception confirmation data and transmits it to the server (320) via the gateway (410) (S950). The VIN reception confirmation data may include a parameter for an encrypted VIN (Enc_VIN), a parameter for the ID of the electronic control unit (ECU ID), and a parameter for the value of an electronic signature (Sign).

[0102] When the server (320) and the electronic control unit (420) encrypt and transmit the VIN, even if an attacker steals the encrypted VIN transmitted and received on the CAN (Controller Area Network) bus section, the plaintext VIN cannot be confirmed. When the server (320) and the electronic control unit (420) encrypt and transmit the VIN, even if an attacker modifies the encrypted VIN transmitted and received on the CAN bus section, the modulation of the VIN can be detected using an electronic signature. Since the electronic control unit (420) uses a hashed VIN, the plaintext VIN can not be exposed within the vehicle. Accordingly, when an attacker steals the VIN, an attack that steals the VIN can be prevented because the hashed VIN is used. Since a symmetric key and an electronic signature are used together, confidentiality, integrity, non-repudiation, and two-way authentication can be guaranteed.

[0103] FIG. 10 is a block diagram schematically illustrating an exemplary computing device that can be used to implement a method according to the present disclosure.

[0104] The computing device (1000) may include some or all of a memory (1010), a processor (1020), storage (1040), an input / output interface (1060), and a communication interface (1080). The computing device (1000) may structurally and / or functionally include at least a portion of a server (320), a gateway (410), and an electronic control device (420). The computing device (1000) may be a stationary computing device such as a desktop computer, a server, an AI accelerator, etc., as well as a portable computing device such as a laptop computer, a smart phone, etc.

[0105] The memory (1010) may store a program that causes the processor (1020) to perform a method or operation according to various embodiments of the present disclosure. For example, the program may include a plurality of instructions executable by the processor (1020), and the methods illustrated in FIGS. 8 and 9 may be performed by executing the plurality of instructions by the processor (1020).

[0106] Memory (1010) may be a single memory or multiple memories. In this case, information required to perform methods or operations according to various embodiments of the present disclosure may be stored in a single memory or divided and stored across multiple memories. If memory (1010) is comprised of multiple memories, the multiple memories may be physically separated.

[0107] The memory (1010) may include at least one of volatile memory and non-volatile memory. The volatile memory includes SRAM (Static Random Access Memory) or DRAM (Dynamic Random Access Memory), and the non-volatile memory includes flash memory.

[0108] The processor (1020) may include at least one core capable of executing at least one instruction. The processor (1020) may execute instructions stored in the memory (1010). The processor (1020) may be a single processor or multiple processors.

[0109] Storage (1040) maintains stored data even when power supplied to the computing device (1000) is cut off. For example, storage (1040) may include non-volatile memory or a storage medium such as magnetic tape, optical disk, or magnetic disk.

[0110] A program stored in storage (1040) may be loaded into memory (1010) before being executed by processor (1020). Storage (1040) may store a file written in a programming language, and a program generated from the file by a compiler or the like may be loaded into memory (1010). Storage (1040) may store data to be processed by processor (1020) and / or data processed by processor (1020).

[0111] The input / output interface (1060) may include input devices such as a keyboard, mouse, etc., and output devices such as a display device, printer, etc. A user may trigger execution of a program by the processor (1020) and / or check the processing results of the processor (1020) through the input / output interface.

[0112] The communication interface (1080) may provide access to an external network. For example, the computing device (1000) may communicate with other devices via the communication interface (1080).

[0113] Each component of the device or method according to the present invention may be implemented in hardware, software, or a combination of hardware and software. Furthermore, the functions of each component may be implemented in software, with a microprocessor executing the software functions corresponding to each component.

[0114] Various implementations of the systems and techniques described herein may be implemented as digital electronic circuits, integrated circuits, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include implementations of one or more computer programs executable on a programmable system. The programmable system includes at least one programmable processor (which may be a special purpose processor or a general purpose processor) coupled to receive data and instructions from and transmit data and instructions to a storage system, at least one input device, and at least one output device. Computer programs (also known as programs, software, software applications, or code) include instructions for the programmable processor and are stored on a "computer-readable recording medium."

[0115] A computer-readable recording medium includes any type of recording device that stores data that can be read by a computer system. Such a computer-readable recording medium may be a non-volatile or non-transitory medium such as a ROM, CD-ROM, magnetic tape, floppy disk, memory card, hard disk, magneto-optical disk, storage device, and may further include a transitory medium such as a data transmission medium. Furthermore, the computer-readable recording medium may be distributed across network-connected computer systems, so that computer-readable code can be stored and executed in a distributed manner.

[0116] Although the flowchart of this specification describes each process as being executed sequentially, this is merely an illustrative description of the technical idea of ​​one embodiment of the present disclosure. In other words, a person of ordinary skill in the art to which one embodiment of the present disclosure belongs can modify and apply various modifications and variations by changing the order described in the flowchart without departing from the essential characteristics of one embodiment of the present disclosure, or by executing one or more of the processes in parallel. Therefore, the flowchart is not limited to a chronological order.

[0117] The above description is merely an example of the technical idea of ​​the present embodiment, and those skilled in the art will appreciate that various modifications and variations can be made without departing from the essential characteristics of the present embodiment. Therefore, the present embodiments are not intended to limit the technical idea of ​​the present embodiment, but rather to explain it, and the scope of the technical idea of ​​the present embodiment is not limited by these embodiments. The scope of protection of the present embodiment should be interpreted by the claims below, and all technical ideas within a scope equivalent thereto should be interpreted as being included in the scope of rights of the present embodiment.

[0118]

[0119] CROSS-REFERENCE TO RELATED APPLICATION

[0120] This patent application claims priority to Korean patent application No. 10-2024-0050884, filed in Korea on April 16, 2024, and Korean patent application No. 10-2025-0025658, filed in Korea on February 27, 2025, the entire contents of which are incorporated herein by reference.

Claims

1. In a method performed by a server, A process of generating an encrypted vehicle identification number by encrypting the vehicle identification number using a symmetric key, and transmitting vehicle identification number data including parameters for the encrypted vehicle identification number to an electronic control unit through a gateway; A process of receiving vehicle identification number reception confirmation data from the electronic control device through the gateway based on the electronic control device decrypting the encrypted vehicle identification number to generate the vehicle identification number and hashing the vehicle identification number and the symmetric key to generate a hashed vehicle identification number; A process for verifying an electronic signature based on the above vehicle identification number receipt confirmation data; and A method comprising a process of generating a hashed vehicle identification number by hashing the vehicle identification number and the symmetric key when the electronic signature is verified.

2. In paragraph 1, A method in which the vehicle identification number data includes parameters for the encrypted vehicle identification number, parameters for an encryption method using the symmetric key, parameters for an electronic signature method, parameters for a hash method, parameters for an ID of the electronic control device, and parameters for a value of an electronic signature.

3. In paragraph 1, A method wherein the vehicle identification number reception confirmation data includes parameters for the encrypted vehicle identification number, parameters for the ID of the electronic control device, and parameters for the value of the electronic signature.

4. In a method performed by an electronic control device, A process of receiving vehicle identification number data including parameters for encrypted vehicle identification numbers from a server through a gateway; A process of verifying an electronic signature based on the above vehicle identification number data; A process of generating a vehicle identification number by decrypting the encrypted vehicle identification number based on the vehicle identification number data; A process of generating a hashed vehicle identification number by hashing the vehicle identification number and a symmetric key based on the vehicle identification number data; and A method comprising a process of transmitting vehicle identification number reception confirmation data to the server through the gateway.

5. In paragraph 4, A method in which the vehicle identification number data includes parameters for the encrypted vehicle identification number, parameters for an encryption method using a symmetric key, parameters for an electronic signature method, parameters for a hash method, parameters for an ID of the electronic control device, and parameters for a value of an electronic signature.

6. In paragraph 4, A method wherein the vehicle identification number reception confirmation data includes parameters for the encrypted vehicle identification number, parameters for the ID of the electronic control device, and parameters for the value of the electronic signature.

7. Memory; and In a server including multiple processors, At least one processor among the plurality of processors, Encrypting the vehicle identification number using a symmetric key to generate an encrypted vehicle identification number, and transmitting vehicle identification number data including parameters for the encrypted vehicle identification number to the electronic control unit through a gateway, Based on the electronic control device decrypting the encrypted vehicle identification number to generate the vehicle identification number and hashing the vehicle identification number and the symmetric key to generate a hashed vehicle identification number, the electronic control device receives vehicle identification number reception confirmation data from the electronic control device through the gateway, Verify the electronic signature based on the above vehicle identification number receipt confirmation data, A server that generates the hashed vehicle identification number by hashing the vehicle identification number and the symmetric key when the above electronic signature is verified.

8. In paragraph 7, The above vehicle identification number data includes parameters for the encrypted vehicle identification number, parameters for the encryption method using the symmetric key, parameters for the electronic signature method, parameters for the hash method, parameters for the ID of the electronic control device, and parameters for the value of the electronic signature.

9. In paragraph 7, The server, wherein the above vehicle identification number reception confirmation data includes parameters for the encrypted vehicle identification number, parameters for the ID of the electronic control device, and parameters for the value of the electronic signature.

10. Memory; and In an electronic control device including multiple processors, At least one processor among the plurality of processors, Receives vehicle identification number data including parameters for encrypted vehicle identification numbers from the server through the gateway, Verify the electronic signature based on the above vehicle identification number data, Based on the above vehicle identification number data, the encrypted vehicle identification number is decrypted to generate a vehicle identification number, Based on the above vehicle identification number data, the vehicle identification number and symmetric key are hashed to generate a hashed vehicle identification number, An electronic control device that transmits vehicle identification number reception confirmation data to the server through the gateway.

11. In paragraph 10, An electronic control device, wherein the above vehicle identification number data includes parameters for the encrypted vehicle identification number, parameters for an encryption method using a symmetric key, parameters for an electronic signature method, parameters for a hash method, parameters for an ID of the electronic control device, and parameters for a value of an electronic signature.

12. In paragraph 10, An electronic control device, wherein the vehicle identification number reception confirmation data includes parameters for the encrypted vehicle identification number, parameters for the ID of the electronic control device, and parameters for the value of the electronic signature.

Images