Blockchain-based methods, devices, and electronic devices for protecting in-vehicle software copyright.

Abstract

This invention discloses a blockchain-based method, apparatus, and electronic device for protecting the copyright of in-vehicle software. The method includes: generating a unique copyright identifier based on the copyright ownership certificate, software package hash value, and authorized usage scope of the target in-vehicle software, and storing it in a blockchain node; when the target in-vehicle software is installed / run in the vehicle, generating a first hash value to be verified for the target in-vehicle software, obtaining the vehicle's software authorization certificate, and sending it to the blockchain node for verification; generating a unique upgrade package identifier based on the upgrade package hash value, upgrade applicability scope, and unique copyright identifier of the target in-vehicle software, and storing it in the blockchain node; when the target in-vehicle software is upgraded in the vehicle, generating a second hash value to be verified for the OTA upgrade package, obtaining the vehicle's software upgrade certificate, and sending it to the blockchain node for verification. This invention ensures the copyright security of in-vehicle software and the reliability of OTA upgrades, and can be widely applied in the field of vehicle technology.

Description

Technical Field

[0001] This invention relates to the field of vehicle technology, and in particular to a blockchain-based method, apparatus, and electronic device for protecting the copyright of in-vehicle software. Background Technology

[0002] Existing technologies for protecting in-vehicle software copyright and ensuring OTA upgrade security can be broadly categorized into three types: First, traditional encryption and licensing schemes, which verify software legitimacy through hardware keys or software licenses, but are vulnerable to mass cracking if keys are stolen; second, centralized copyright registration schemes, which rely on automakers or third-party servers to store copyright information, but are susceptible to data tampering due to server attacks; and third, basic OTA verification schemes, which only perform hash verification on upgrade packages without associating them with copyright information, thus failing to prevent pirated software from masquerading as genuine upgrade packages.

[0003] For example, the OTA upgrade systems of mainstream car models on the market only verify the integrity of the upgrade package through a single hash value, without verifying the ownership of the software copyright. Pirated software can bypass the verification by tampering with the hash value. The copyright protection of some in-vehicle software relies on the encryption dongle provided by the supplier, which is costly and easily cracked, and cannot achieve full life-cycle copyright traceability. In addition, once the centralized copyright database is attacked, the legitimacy of the genuine software that users have installed cannot be verified, and there is a risk of it being misjudged or forcibly uninstalled.

[0004] In summary, the existing technology has the following drawbacks: 1) Difficulty in tracing copyright: Copyright information stored in a centralized manner is easily tampered with, and it is impossible to provide an immutable copyright certificate, making it difficult to obtain evidence after software infringement. 2) Insufficient anti-piracy measures: Relying solely on local encryption or simple verification is insufficient to effectively prevent pirated software from being installed as genuine, posing security risks such as vehicle malfunctions and data leaks; 3) Weak security of OTA upgrades: The lack of copyright verification combined with upgrade package verification means that upgrade packages may be replaced with pirated or malicious software, threatening driving safety; 4) Key management risks: Traditional encryption schemes rely on centralized key storage, and key leakage will cause the entire software copyright protection to fail; 5) Poor compatibility and scalability: Software copyright protection schemes from different vendors are independent and lack a unified standard, making it difficult to adapt to the software management needs of multiple brands and vehicle models.

[0005] As can be seen from the above, existing technologies cannot meet the core requirements of "unalterable copyright information, accurate identification of pirated software, copyright verification for OTA upgrades, and full lifecycle traceability," making it difficult to guarantee the copyright security of in-vehicle software and the reliability of OTA upgrades. These problems urgently need to be solved. Summary of the Invention

[0006] The purpose of this invention is to at least partially solve one of the technical problems existing in the prior art.

[0007] Therefore, one objective of this invention is to provide a blockchain-based method for protecting the copyright of in-vehicle software. This method uses blockchain to realize distributed copyright registration, software installation / operation authentication, and OTA upgrade authentication for in-vehicle software, thereby ensuring the copyright security of in-vehicle software and the reliability of OTA upgrades.

[0008] Another objective of this invention is to provide a blockchain-based in-vehicle software copyright protection device.

[0009] To achieve the above-mentioned technical objectives, the technical solutions adopted in the embodiments of the present invention include: On one hand, embodiments of the present invention provide a blockchain-based method for protecting the copyright of in-vehicle software, comprising the following steps: A unique copyright identifier is generated based on the copyright ownership certificate, software package hash value, and authorized usage scope of the target vehicle software uploaded by the software vendor, and the unique copyright identifier is stored in the blockchain node; When the target vehicle software is installed / run on the vehicle, a first hash value to be verified for the target vehicle software is generated, and the software authorization certificate of the vehicle is obtained. Then, the first hash value to be verified and the software authorization certificate are sent to the blockchain node for verification. If the verification is successful, the vehicle is allowed to install / run the target vehicle software. A unique upgrade package identifier is generated based on the upgrade package hash value, upgrade scope, and unique copyright identifier of the target vehicle software uploaded by the software supplier, and the unique upgrade package identifier is stored in the blockchain node; When the vehicle upgrades the target vehicle software, it generates a second hash value to be verified for the OTA upgrade package and obtains the software upgrade certificate of the vehicle. Then, it sends the second hash value to be verified and the software upgrade certificate to the blockchain node for verification. If the verification is successful, the vehicle is allowed to perform an OTA upgrade according to the OTA upgrade package.

[0010] Furthermore, in one embodiment of the present invention, the step of generating a unique copyright identifier based on the copyright ownership certificate, software package hash value, and authorized usage scope of the target in-vehicle software uploaded by the software vendor, and storing the unique copyright identifier in a blockchain node, specifically includes: The copyright ownership certificate, the software package hash value, and the authorized usage scope are concatenated into a string, and a timestamp is added to obtain the first string; Perform a hash operation on the first string to obtain the unique copyright identifier; The copyright ownership certificate, the software package hash value, the authorized scope of use, and the unique copyright identifier are used to encrypt and encapsulate the copyright certificate data structure. The index value of the copyright certificate data structure is determined based on the software identifier of the target vehicle software, and the copyright certificate data structure is stored through the blockchain node.

[0011] Furthermore, in one embodiment of the present invention, the first hash value to be verified and the software authorization certificate are verified through the following steps: Based on the software identifier of the target vehicle software, the corresponding copyright certificate data structure is read from the blockchain node, and the copyright ownership certificate, the software package hash value, and the authorized scope of use are determined based on the copyright certificate data structure. The software copyright owner information is determined based on the copyright ownership certificate, and the software licensee information is determined based on the authorized scope of use; The software licensor information and software user information are determined based on the software license certificate; When the first hash value to be verified matches the hash value of the software package, the software licensor information matches the software copyright owner information, and the software user information matches the software licensee information, the verification is confirmed to be successful. If the first hash value to be verified is inconsistent with the hash value of the software package, or if the software licensor information is inconsistent with the software copyright owner information, or if the software user information does not match the software licensee information, the verification is determined to fail.

[0012] Furthermore, in one embodiment of the present invention, the step of generating a unique upgrade package identifier based on the upgrade package hash value, upgrade applicability scope, and unique copyright identifier of the target vehicle software uploaded by the software vendor, and storing the unique upgrade package identifier in the blockchain node, specifically includes: The hash value of the upgrade package and the scope of application of the upgrade are concatenated into a string, and a timestamp is added to obtain a second string; The second string is hashed and then concatenated with the unique copyright identifier to obtain the unique upgrade package identifier; The upgrade evidence storage data structure is obtained by encrypting and encapsulating the copyright ownership certificate, the upgrade package hash value, the upgrade application scope, and the unique upgrade package identifier. The index value of the upgrade evidence storage data structure is determined based on the software identifier of the target vehicle software, and the upgrade evidence storage data structure is stored through the blockchain node.

[0013] Furthermore, in one embodiment of the present invention, the second hash value to be verified and the software upgrade certificate are verified through the following steps: Based on the software identifier of the target vehicle software, the corresponding upgrade evidence storage data structure is read from the blockchain node, and the copyright ownership certificate, the upgrade package hash value, and the upgrade application scope are determined based on the upgrade evidence storage data structure. The software copyright owner information is determined based on the copyright ownership certificate, and the software licensee information is determined based on the scope of application of the upgrade. The information of the upgrade licensor and the software upgrade provider is determined based on the software upgrade certificate. When the second hash value to be verified matches the hash value of the upgrade package, the upgrade licensor information matches the software copyright owner information, and the software upgrader information matches the software licensee information, the verification is confirmed to be successful. If the second hash value to be verified is inconsistent with the hash value of the upgrade package, or if the upgrade licensor information is inconsistent with the software copyright owner information, or if the software upgrader information does not match the software licensee information, the verification is determined to fail.

[0014] Furthermore, in one embodiment of the present invention, the in-vehicle software copyright protection method further includes the following steps: When the target vehicle software is installed, run, or upgraded on the vehicle, the software copyright status and verification results of the target vehicle software are displayed on the central control screen of the vehicle. When verification fails, the reason for the failure is displayed on the central control screen, and guidance information on how to obtain the software is provided.

[0015] Furthermore, in one embodiment of the present invention, the blockchain nodes include vehicle manufacturer nodes, supplier nodes, and user nodes, and the vehicle manufacturer nodes, supplier nodes, and user nodes form a consortium blockchain through a consensus mechanism.

[0016] On the other hand, embodiments of the present invention provide a blockchain-based in-vehicle software copyright protection device, comprising: The copyright identifier storage module is used to generate a unique copyright identifier based on the copyright ownership certificate, software package hash value and authorized usage scope of the target vehicle software uploaded by the software supplier, and to store the unique copyright identifier in the blockchain node; The first verification module is used to generate a first hash value to be verified for the target vehicle software when the target vehicle software is installed / run on the vehicle terminal, and to obtain the software authorization certificate of the vehicle terminal. Then, the first hash value to be verified and the software authorization certificate are sent to the blockchain node for verification. If the verification is successful, the vehicle terminal is allowed to install / run the target vehicle software. The upgrade package identifier storage module is used to generate a unique upgrade package identifier based on the upgrade package hash value, upgrade scope and unique copyright identifier of the target vehicle software uploaded by the software supplier, and store the unique upgrade package identifier in the blockchain node; The second verification module is used to generate a second hash value to be verified for the OTA upgrade package when the vehicle upgrades the target vehicle software, and obtain the software upgrade certificate of the vehicle. Then, the second hash value to be verified and the software upgrade certificate are sent to the blockchain node for verification. If the verification is successful, the vehicle is allowed to perform OTA upgrade according to the OTA upgrade package.

[0017] On the other hand, embodiments of the present invention provide an electronic device, including: At least one processor; At least one memory for storing at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements the above-described blockchain-based in-vehicle software copyright protection method.

[0018] On the other hand, embodiments of the present invention also provide a computer-readable storage medium storing a processor-executable computer program that, when executed by a processor, implements the aforementioned blockchain-based in-vehicle software copyright protection method.

[0019] On the other hand, embodiments of the present invention also provide a computer program product, including a computer program that, when executed by a processor, implements the aforementioned blockchain-based in-vehicle software copyright protection method.

[0020] The advantages and beneficial effects of the present invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention: In this embodiment of the invention, a unique copyright identifier is generated based on the copyright ownership certificate, package hash value, and authorized usage scope of the target vehicle software uploaded by the software vendor. This unique copyright identifier is stored in a blockchain node. When the target vehicle software is installed / run on the vehicle, a first hash value to be verified for the target vehicle software is generated, and the vehicle's software authorization certificate is obtained. The first hash value to be verified and the software authorization certificate are then sent to the blockchain node for verification. If the verification is successful, the vehicle is allowed to install / run the target vehicle software. A unique upgrade package identifier is generated based on the upgrade package hash value, upgrade applicability scope, and unique copyright identifier of the target vehicle software uploaded by the software vendor. This unique upgrade package identifier is stored in a blockchain node. When the target vehicle software is upgraded on the vehicle, a second hash value to be verified for the OTA upgrade package is generated, and the vehicle's software upgrade certificate is obtained. The second hash value to be verified and the software upgrade certificate are then sent to the blockchain node for verification. If the verification is successful, the vehicle is allowed to perform an OTA upgrade based on the OTA upgrade package. This invention generates a unique copyright identifier based on the copyright ownership certificate, software package hash value, and authorized usage scope of the target in-vehicle software, and stores it on the blockchain. It also generates a unique upgrade package identifier based on the upgrade package hash value, upgrade applicability scope, and unique copyright identifier of the target in-vehicle software, and stores it on the blockchain. This enables distributed copyright registration, software installation / run authentication, and OTA upgrade authentication of in-vehicle software based on blockchain, ensuring the copyright security of in-vehicle software and the reliability of OTA upgrades. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the embodiments of the present invention are described below. It should be understood that the drawings described below are only for the convenience of clearly describing some embodiments of the technical solutions of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 A flowchart illustrating the steps of a blockchain-based method for protecting the copyright of in-vehicle software, as provided in this embodiment of the invention. Figure 2 A structural block diagram of a blockchain-based in-vehicle software copyright protection device provided in an embodiment of the present invention; Figure 3 This is a structural block diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0023] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. In the following description, when referring to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the embodiments of this invention; they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of this invention as detailed in the appended claims.

[0024] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. The terminology used herein is for the purpose of describing embodiments of the invention only and is not intended to limit the invention.

[0025] The blockchain-based in-vehicle software copyright protection method provided in this invention can be applied to terminals, servers, or software running on either a terminal or a server. In some embodiments, the terminal can be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, or in-vehicle terminal, but is not limited to these. The server can be configured as an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The server can also be a node server in a blockchain network. The software can be an application implementing the blockchain-based in-vehicle software copyright protection method, but is not limited to the above forms.

[0026] This invention can be used in a wide variety of general-purpose or special-purpose computer system environments or configurations. Examples include: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, and distributed computing environments including any of the above systems or devices. This invention can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform specific tasks or implement specific abstract data types. This invention can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0027] It should be noted that in various specific embodiments of the present invention, when processing data related to user identity or characteristics, such as user information, user behavior data, user historical data, and user location information, user permission or consent is obtained first. Furthermore, the collection, use, and processing of this data comply with relevant laws, regulations, and standards. In addition, when embodiments of the present invention require access to sensitive personal information of users, separate permission or consent from the user is obtained through pop-ups or redirection to a confirmation page. Only after obtaining the user's separate permission or consent is the necessary user-related data for the normal operation of the embodiments of the present invention acquired.

[0028] Reference Figure 1 This invention provides a blockchain-based method for protecting the copyright of in-vehicle software, specifically including the following steps: S101. Generate a unique copyright identifier based on the copyright ownership certificate, package hash value, and authorized scope of use of the target vehicle software uploaded by the software supplier, and store the unique copyright identifier in the blockchain node; S102. When the target vehicle software is installed / run on the vehicle, the first hash value to be verified of the target vehicle software is generated, and the software authorization certificate of the vehicle is obtained. Then, the first hash value to be verified and the software authorization certificate are sent to the blockchain node for verification. If the verification is successful, the vehicle is allowed to install / run the target vehicle software. S103. Generate a unique upgrade package identifier based on the upgrade package hash value, upgrade scope, and unique copyright identifier of the target vehicle software uploaded by the software supplier, and store the unique upgrade package identifier in the blockchain node; S104. When the vehicle upgrades the target vehicle software, it generates the second hash value to be verified for the OTA upgrade package and obtains the software upgrade certificate of the vehicle. Then, it sends the second hash value to be verified and the software upgrade certificate to the blockchain node for verification. If the verification is successful, the vehicle is allowed to perform OTA upgrade according to the OTA upgrade package.

[0029] This invention generates a unique copyright identifier based on the copyright ownership certificate, software package hash value, and authorized usage scope of the target in-vehicle software, and stores it on the blockchain. It also generates a unique upgrade package identifier based on the upgrade package hash value, upgrade applicability scope, and unique copyright identifier of the target in-vehicle software, and stores it on the blockchain. This enables distributed copyright registration, software installation / run authentication, and OTA upgrade authentication of in-vehicle software based on blockchain, ensuring the copyright security of in-vehicle software and the reliability of OTA upgrades.

[0030] As a further optional implementation, a unique copyright identifier is generated based on the copyright ownership certificate, package hash value, and authorized usage scope of the target in-vehicle software uploaded by the software vendor, and the unique copyright identifier is stored in a blockchain node, specifically including: S1011. Concatenate the copyright ownership certificate, the software package hash value, and the authorized scope of use into strings, and add a timestamp to obtain the first string; S1012. Perform a hash operation on the first string to obtain a unique copyright identifier; S1013. Based on the copyright ownership certificate, the software package hash value, the authorized scope of use, and the unique copyright identifier, the copyright certificate data structure is encrypted and encapsulated. S1014. Determine the index value of the copyright certificate data structure based on the software identifier of the target vehicle software, and store the copyright certificate data structure through a blockchain node.

[0031] Specifically, this invention implements a distributed, immutable record of software copyright information through blockchain copyright registration. Specifically: software suppliers upload basic software information (name, version number, function description), proof of copyright ownership, hash value (calculated using the SHA-256 algorithm to calculate the software installation package hash), and authorized usage scope (authorized vehicle manufacturers, compatible vehicle models, and usage period), generating a unique copyright identifier (CID). A consortium blockchain architecture is adopted (nodes include vehicle manufacturers, suppliers, users, and regulatory authorities). Once the copyright information is uploaded to the blockchain, it cannot be tampered with. Each node synchronously stores complete copyright data, ensuring data redundancy and anti-attack capabilities. When the software version iterates, a new version hash value and copyright information are automatically generated, associated with the historical version CID, forming a complete copyright traceability chain, supporting version tracing and infringement evidence collection.

[0032] As an optional implementation, the first hash value to be verified and the software license certificate are verified through the following steps: S1021. Based on the software identifier of the target vehicle software, read the corresponding copyright certificate data structure on the blockchain node, and determine the copyright ownership certificate, software package hash value and authorized usage scope based on the copyright certificate data structure. S1022. Determine the software copyright owner information based on the copyright ownership certificate, and determine the software licensee information based on the authorized scope of use; S1023. Determine the software licensor information and software user information based on the software license certificate; S1024. When the first hash value to be verified matches the hash value of the software package, the software licensor information matches the software copyright owner information, and the software user information matches the software licensee information, the verification is confirmed to be successful. S1025. If the first hash value to be verified is inconsistent with the hash value of the software package, or the software licensor information is inconsistent with the software copyright owner information, or the software user information does not match the software licensee information, the verification is determined to fail.

[0033] Specifically, this embodiment of the invention verifies the copyright legality of software during the installation / running phase through in-vehicle software authentication. Specifically: before software installation, the hash value of the installation package and the software authorization certificate are extracted and sent to the blockchain node for verification. Installation is allowed only if the hash value matches the blockchain record and the copyright is within the authorized scope; otherwise, installation is rejected and a piracy interception log is recorded. When the vehicle or software starts, the current hash value of the software and the blockchain copyright information are checked periodically (every 24 hours). If the software is detected to have been tampered with (inconsistent hash value) or the copyright has expired, the software operation is immediately suspended, and only the core driving-related functions are retained. In addition, the vehicle caches the copyright data that has passed the most recent three verifications. Basic authentication is completed through local caching in the absence of a network environment, and the verification results are automatically synchronized with the blockchain data after connecting to the network.

[0034] As a further optional implementation, a unique upgrade package identifier is generated based on the upgrade package hash value, upgrade scope, and unique copyright identifier of the target in-vehicle software uploaded by the software vendor, and the unique upgrade package identifier is stored in a blockchain node, specifically including: S1031. Concatenate the upgrade package hash value and the upgrade scope into a string, and add a timestamp to obtain the second string; S1032. Perform a hash operation on the second string and concatenate it with the unique copyright identifier to obtain the unique upgrade package identifier; S1033. Based on the copyright ownership certificate, upgrade package hash value, upgrade applicable scope and unique upgrade package identifier, the upgrade evidence data structure is obtained by encrypting and encapsulating it. S1034. Determine the index value of the upgrade evidence storage data structure based on the software identifier of the target vehicle software, and store the upgrade evidence storage data structure through a blockchain node.

[0035] As an optional implementation, the second hash value to be verified and the software upgrade certificate are verified through the following steps: S1041. Based on the software identifier of the target vehicle software, read the corresponding upgrade certificate data structure on the blockchain node, and determine the copyright ownership certificate, upgrade package hash value, and upgrade scope based on the upgrade certificate data structure. S1042. Determine the software copyright owner information based on the copyright ownership certificate, and determine the software licensee information based on the scope of application of the upgrade; S1043. Determine the upgrade licensor information and software upgrade provider information based on the software upgrade certificate; S1044. When the second hash value to be verified is consistent with the hash value of the upgrade package, the information of the upgrade licensor is consistent with the information of the software copyright owner, and the information of the software upgrader is consistent with the information of the software licensee, the verification is confirmed to be successful. S1045. If the second hash value to be verified is inconsistent with the hash value of the upgrade package, or the information of the upgrade licensor is inconsistent with the information of the software copyright owner, or the information of the software upgrader does not match the information of the software licensee, the verification is determined to fail.

[0036] Specifically, this embodiment of the invention achieves dual protection of upgrade package copyright and integrity through upgrade package copyright binding and upgrade package verification. Specifically: when the automaker releases an OTA upgrade package, it puts the upgrade package hash value, corresponding software copyright CID, upgrade applicable scope and other information on the blockchain to generate a unique upgrade package authorization certificate; after the vehicle receives the OTA upgrade package, it first verifies the consistency between the upgrade package hash value and the blockchain record, and then verifies the legality of the copyright CID and the legality of the authorization scope. Only after multiple verifications are passed is the upgrade allowed; after the upgrade is completed, the upgrade result (success / failure), vehicle VIN code and upgrade package CID are associated with the blockchain to form a complete upgrade traceability chain, which facilitates supervision and problem investigation.

[0037] In some optional embodiments, embodiments of the present invention ensure the security of transmission and storage of copyright information and authentication data through a data encryption module, including: 1) Transmission encryption unit: The "SM2 asymmetric encryption + AES-256 symmetric encryption" combination scheme is adopted. When transmitting copyright information, authentication requests and other data, the session key is negotiated through SM2 first, and then the data is encrypted with the session key to prevent theft during transmission. 2) Encrypted storage unit: Copyright cache data and authentication logs stored on the vehicle are encrypted using a hardware security module (HSM), and copyright information stored on the blockchain nodes is encrypted and fragmented, requiring authorization from multiple nodes to access; 3) Key Management Unit: Distributed key generation and storage are adopted, and the root key is jointly managed by multiple consortium blockchain nodes to avoid the risk of key leakage from a single node.

[0038] As an optional implementation, the in-vehicle software copyright protection method further includes the following steps: S201. When the target vehicle software is installed, run, or upgraded on the vehicle side, the software copyright status and verification results of the target vehicle software are displayed on the vehicle's central control screen. S202. When verification fails, the reason for the failure will be displayed on the central control screen, and guidance information on the software acquisition channel will be provided.

[0039] Specifically, this embodiment of the invention displays the copyright status and authentication results in real time. Specifically: the central control screen displays the software copyright status (genuine authorization / unauthorized / pirated / copyright expired), OTA upgrade verification progress and results; the mobile APP simultaneously pushes piracy interception reminders and copyright expiration warnings; it supports users and regulatory authorities to query software installation authentication logs and OTA upgrade traceability logs, and the log information is associated with the blockchain CID, which can be used as evidence of infringement; when piracy interception or authentication fails, the reason is clearly indicated (such as "software hash value does not match, suspected piracy" or "copyright has expired, please contact the supplier for renewal"), and guidance on obtaining genuine software is provided.

[0040] As an optional implementation, the blockchain nodes include car manufacturer nodes, supplier nodes, and user nodes, which form a consortium blockchain through a consensus mechanism.

[0041] Specifically, this embodiment of the invention forms a consortium blockchain based on a consensus mechanism among vehicle manufacturer nodes, supplier nodes, and user nodes. A node management module ensures the stable operation and access control of the consortium blockchain, including: 1) Node Admission Unit: New nodes (such as new software vendors) need to submit qualification certificates and can only join after being reviewed and approved by a majority of nodes in the consortium blockchain to ensure the legitimacy of the nodes; 2) Hierarchical permission unit: Different nodes are assigned different permissions (vehicle manufacturer nodes can manage the authorization of adapted vehicle models, user nodes can query the full copyright data, and supplier nodes can only manage their own software copyright). 3) Consensus Mechanism Unit: The "Practical Byzantine Fault Tolerance (PBFT)" consensus algorithm is adopted to ensure the consistency between copyright information on the chain and verification, reduce consensus latency, and meet the real-time authentication requirements.

[0042] A complete process of an embodiment of the present invention is as follows: 1) Copyright Registration: Software vendors upload copyright information and hash values, which are then uploaded to the blockchain to generate a CID, forming an immutable copyright record; 2) Software authentication: When a user installs the software, the vehicle extracts the installation package hash and CID. After the blockchain node verifies the hash, installation is allowed. The authentication is repeated periodically during software operation. 3) OTA Upgrade: The automaker releases the upgrade package and binds the copyright CID to the blockchain. After receiving the package, the vehicle double-verifies the hash of the upgrade package and the legality of the copyright. Once verified, the upgrade is completed. 4) Status feedback: Real-time display of copyright status and authentication results, triggering alerts and blocking in case of anomalies; 5) Traceability and evidence collection: Regulatory authorities or users can query copyright and upgrade logs through the blockchain as a basis for handling infringement.

[0043] The method steps of the embodiments of the present invention have been described above. It can be understood that the embodiments of the present invention generate a unique copyright identifier based on the copyright ownership certificate of the target in-vehicle software, the software package hash value, and the authorized scope of use, and store it on the blockchain. Similarly, they generate a unique upgrade package identifier based on the upgrade package hash value, the upgrade application scope, and the unique copyright identifier of the target in-vehicle software, and store it on the blockchain. This achieves distributed copyright registration, software installation / run authentication, and OTA upgrade authentication for in-vehicle software based on blockchain, ensuring the copyright security of the in-vehicle software and the reliability of OTA upgrades.

[0044] Reference Figure 2 This invention provides a blockchain-based in-vehicle software copyright protection device, comprising: The copyright identifier storage module is used to generate a unique copyright identifier based on the copyright ownership certificate, software package hash value, and authorized scope of use of the target vehicle software uploaded by the software vendor, and to store the unique copyright identifier in the blockchain node; The first verification module is used to generate the first hash value to be verified of the target vehicle software when the target vehicle software is installed / run on the vehicle, and to obtain the software authorization certificate of the vehicle. Then, the first hash value to be verified and the software authorization certificate are sent to the blockchain node for verification. If the verification is successful, the vehicle is allowed to install / run the target vehicle software. The upgrade package identifier storage module is used to generate a unique upgrade package identifier based on the upgrade package hash value, upgrade scope, and unique copyright identifier of the target vehicle software uploaded by the software vendor, and store the unique upgrade package identifier to the blockchain node; The second verification module is used to generate a second hash value to be verified for the OTA upgrade package when the target vehicle software is upgraded, and to obtain the software upgrade certificate of the vehicle. Then, the second hash value to be verified and the software upgrade certificate are sent to the blockchain node for verification. If the verification is successful, the vehicle is allowed to perform OTA upgrade according to the OTA upgrade package.

[0045] It is understood that the content of the above method embodiments is applicable to the present device embodiments. The specific functions implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0046] Reference Figure 3 This invention provides an electronic device, comprising: At least one processor; At least one memory for storing at least one program; When the above-mentioned at least one program is executed by the above-mentioned at least one processor, the above-mentioned at least one processor implements the above-mentioned blockchain-based in-vehicle software copyright protection method.

[0047] It is understood that the content of the above method embodiments is applicable to this device embodiment. The specific functions implemented by this device embodiment are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0048] This invention also provides a computer-readable storage medium storing a processor-executable computer program that, when executed by a processor, implements the aforementioned blockchain-based in-vehicle software copyright protection method.

[0049] This invention provides a computer-readable storage medium that can execute a blockchain-based in-vehicle software copyright protection method provided in the method embodiments of this invention. It can execute any combination of the implementation steps of the method embodiments and has the corresponding functions and beneficial effects of the method.

[0050] This invention also provides a computer program product, including a computer program that, when executed by a processor, implements the aforementioned blockchain-based in-vehicle software copyright protection method.

[0051] It is understood that the content of the above method embodiments is applicable to the embodiments of this program product. The specific functions implemented by the embodiments of this program product are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0052] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory may optionally include memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0053] The embodiments described in this invention are for the purpose of more clearly illustrating the technical solutions of the embodiments of this invention, and do not constitute a limitation on the technical solutions provided by the embodiments of this invention. As those skilled in the art will know, with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of this invention are also applicable to similar technical problems.

[0054] The terms "first," "second," "third," "fourth," etc. (if present) in the specification and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0055] In some alternative embodiments, the functions / operations mentioned in the block diagrams may not occur in the order shown in the operation diagrams. For example, depending on the functions / operations involved, two consecutively shown blocks may actually be executed substantially simultaneously, or the aforementioned blocks may sometimes be executed in reverse order. Furthermore, the embodiments presented and described in the flowcharts of this invention are provided by way of example to provide a more comprehensive understanding of the technology. The disclosed methods are not limited to the operations and logic flows presented herein. Alternative embodiments are contemplated in which the order of various operations is changed and sub-operations described as part of a larger operation are executed independently.

[0056] Furthermore, although the invention has been described in the context of functional modules, it should be understood that, unless otherwise stated, one or more of the aforementioned functions and / or features may be integrated into a single physical device and / or software module, or one or more functions and / or features may be implemented in a separate physical device or software module. It is also understood that a detailed discussion of the actual implementation of each module is unnecessary for understanding the invention. Rather, given the properties, functions, and internal relationships of the various functional modules in the apparatus disclosed herein, the actual implementation of the module will be understood within the scope of conventional skill of an engineer. Therefore, those skilled in the art can implement the invention as set forth in the claims using ordinary techniques without excessive experimentation. It is also understood that the specific concepts disclosed are merely illustrative and not intended to limit the scope of the invention, which is determined by the full scope of the appended claims and their equivalents.

[0057] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0058] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-including system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device.

[0059] More specific examples (a non-exhaustive list) of computer-readable media include: electrical connections (electronic devices) having one or more wires, portable computer disk drives (magnetic devices), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Furthermore, computer-readable media can even be paper or other suitable media on which the aforementioned program can be printed, because the aforementioned program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in computer memory.

[0060] It should be understood that various parts of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0061] In the foregoing description of this specification, references to terms such as "one embodiment," "another embodiment," or "some embodiments" indicate that a specific feature, structure, material, or characteristic described in connection with an embodiment or example is included in at least one embodiment or example of the present invention. In this specification, illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0062] Although embodiments of the invention have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the claims and their equivalents.

[0063] The above is a detailed description of the preferred embodiments of the present invention. However, the present invention is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of the present invention. All such equivalent modifications or substitutions are included within the scope defined by the claims of the present invention.

Claims

1. A blockchain-based method for protecting the copyright of in-vehicle software, characterized in that, Includes the following steps: A unique copyright identifier is generated based on the copyright ownership certificate, software package hash value, and authorized usage scope of the target vehicle software uploaded by the software vendor, and the unique copyright identifier is stored in the blockchain node; When the target vehicle software is installed / run on the vehicle, a first hash value to be verified for the target vehicle software is generated, and the software authorization certificate of the vehicle is obtained. Then, the first hash value to be verified and the software authorization certificate are sent to the blockchain node for verification. If the verification is successful, the vehicle is allowed to install / run the target vehicle software. A unique upgrade package identifier is generated based on the upgrade package hash value, upgrade scope, and unique copyright identifier of the target vehicle software uploaded by the software supplier, and the unique upgrade package identifier is stored in the blockchain node; When the vehicle upgrades the target vehicle software, it generates a second hash value to be verified for the OTA upgrade package and obtains the software upgrade certificate of the vehicle. Then, it sends the second hash value to be verified and the software upgrade certificate to the blockchain node for verification. If the verification is successful, the vehicle is allowed to perform an OTA upgrade according to the OTA upgrade package.

2. The method for protecting in-vehicle software copyright based on blockchain according to claim 1, characterized in that, The process of generating a unique copyright identifier based on the copyright ownership certificate, software package hash value, and authorized usage scope of the target vehicle software uploaded by the software vendor, and storing the unique copyright identifier in a blockchain node, specifically includes: The copyright ownership certificate, the software package hash value, and the authorized usage scope are concatenated into a string, and a timestamp is added to obtain the first string; Perform a hash operation on the first string to obtain the unique copyright identifier; The copyright ownership certificate, the software package hash value, the authorized scope of use, and the unique copyright identifier are used to encrypt and encapsulate the copyright certificate data structure. The index value of the copyright certificate data structure is determined based on the software identifier of the target vehicle software, and the copyright certificate data structure is stored through the blockchain node.

3. The method for protecting the copyright of in-vehicle software based on blockchain according to claim 2, characterized in that, The first hash value to be verified and the software authorization certificate are verified through the following steps: Based on the software identifier of the target vehicle software, the corresponding copyright certificate data structure is read from the blockchain node, and the copyright ownership certificate, the software package hash value, and the authorized scope of use are determined based on the copyright certificate data structure. The software copyright owner information is determined based on the copyright ownership certificate, and the software licensee information is determined based on the authorized scope of use; The software licensor information and software user information are determined based on the software license certificate; When the first hash value to be verified matches the hash value of the software package, the software licensor information matches the software copyright owner information, and the software user information matches the software licensee information, the verification is confirmed to be successful. If the first hash value to be verified is inconsistent with the hash value of the software package, or if the software licensor information is inconsistent with the software copyright owner information, or if the software user information does not match the software licensee information, the verification is determined to fail.

4. The method for protecting in-vehicle software copyright based on blockchain according to claim 1, characterized in that, The step of generating a unique upgrade package identifier based on the upgrade package hash value, upgrade applicability scope, and unique copyright identifier uploaded by the software supplier, and storing the unique upgrade package identifier in the blockchain node, specifically includes: The hash value of the upgrade package and the scope of application of the upgrade are concatenated into a string, and a timestamp is added to obtain a second string; The second string is hashed and then concatenated with the unique copyright identifier to obtain the unique upgrade package identifier; The upgrade evidence storage data structure is obtained by encrypting and encapsulating the copyright ownership certificate, the upgrade package hash value, the upgrade application scope, and the unique upgrade package identifier. The index value of the upgrade evidence storage data structure is determined based on the software identifier of the target vehicle software, and the upgrade evidence storage data structure is stored through the blockchain node.

5. A blockchain-based method for protecting the copyright of in-vehicle software according to claim 4, characterized in that, The second hash value to be verified and the software upgrade certificate are verified through the following steps: Based on the software identifier of the target vehicle software, the corresponding upgrade evidence storage data structure is read from the blockchain node, and the copyright ownership certificate, the upgrade package hash value, and the upgrade application scope are determined based on the upgrade evidence storage data structure. The software copyright owner information is determined based on the copyright ownership certificate, and the software licensee information is determined based on the scope of application of the upgrade. The information of the upgrade licensor and the software upgrade provider is determined based on the software upgrade certificate. When the second hash value to be verified matches the hash value of the upgrade package, the upgrade licensor information matches the software copyright owner information, and the software upgrader information matches the software licensee information, the verification is confirmed to be successful. If the second hash value to be verified is inconsistent with the hash value of the upgrade package, or if the upgrade licensor information is inconsistent with the software copyright owner information, or if the software upgrader information does not match the software licensee information, the verification is determined to fail.

6. A blockchain-based method for protecting the copyright of in-vehicle software according to any one of claims 1 to 5, characterized in that, The method for protecting the copyright of in-vehicle software also includes the following steps: When the target vehicle software is installed, run, or upgraded on the vehicle, the software copyright status and verification results of the target vehicle software are displayed on the central control screen of the vehicle. When verification fails, the reason for the failure is displayed on the central control screen, and guidance information on how to obtain the software is provided.

7. A blockchain-based method for protecting the copyright of in-vehicle software according to any one of claims 1 to 5, characterized in that, The blockchain nodes include car manufacturer nodes, supplier nodes, and user nodes, which form a consortium blockchain through a consensus mechanism.

8. A blockchain-based in-vehicle software copyright protection device, characterized in that, include: The copyright identifier storage module is used to generate a unique copyright identifier based on the copyright ownership certificate, software package hash value and authorized usage scope of the target vehicle software uploaded by the software supplier, and to store the unique copyright identifier in the blockchain node; The first verification module is used to generate a first hash value to be verified for the target vehicle software when the target vehicle software is installed / run on the vehicle terminal, and to obtain the software authorization certificate of the vehicle terminal. Then, the first hash value to be verified and the software authorization certificate are sent to the blockchain node for verification. If the verification is successful, the vehicle terminal is allowed to install / run the target vehicle software. The upgrade package identifier storage module is used to generate a unique upgrade package identifier based on the upgrade package hash value, upgrade scope and unique copyright identifier of the target vehicle software uploaded by the software supplier, and store the unique upgrade package identifier in the blockchain node; The second verification module is used to generate a second hash value to be verified for the OTA upgrade package when the vehicle upgrades the target vehicle software, and obtain the software upgrade certificate of the vehicle. Then, the second hash value to be verified and the software upgrade certificate are sent to the blockchain node for verification. If the verification is successful, the vehicle is allowed to perform OTA upgrade according to the OTA upgrade package.

9. An electronic device, characterized in that, include: At least one processor; At least one memory for storing at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements a blockchain-based in-vehicle software copyright protection method as described in any one of claims 1 to 7.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements a blockchain-based in-vehicle software copyright protection method as described in any one of claims 1 to 7.

Images