Internet of vehicles identity management method and system, and storage medium

Abstract

The embodiment of the invention provides an Internet of Vehicles identity management method and system and a storage medium, and the method comprises the steps that an identity management node receives a plurality of identity verification requests sent by an intra-domain node, and the plurality of identity verification requests are used for verifying the identity information of a plurality of nodes in other domains; when it is determined that the multiple nodes do not belong to nodes in the domain according to the multiple nodes, data preprocessing is carried out on the multiple identity verification requests corresponding to the multiple nodes to obtain multiple pieces of preprocessed data, and the multiple pieces of preprocessed data are compressed to obtain compressed data; performing signature processing on the compressed data and private key data of the identity management node to obtain compressed transaction data, and sending the compressed transaction data to an identity management contract for identity verification; and the identity management node receives an identity verification result of the compressed transaction data returned by the identity management contract, and the identity management node provides services for the intra-domain node according to the plurality of verification results.

Description

Technical Field

[0001] The present application belongs to the field of computer software technology, and specifically relates to a method, system and storage medium for managing identity in an Internet of Vehicles. Background Art

[0002] Internet of Vehicles (IoV) systems require efficient and reliable identity management to ensure secure interactions between vehicles and infrastructure.

[0003] The existing vehicle network identity management solution based on blockchain relies on a single blockchain network, that is, it verifies the single identity of the node in the domain by receiving the node's identity authentication information. It cannot realize the simultaneous verification of multiple identities, and has the problems of poor scalability, low processing efficiency and inability to effectively handle multi-domain identity management. Summary of the invention

[0004] The present application provides a method, system and storage medium for vehicle network identity management, which can realize simultaneous identity verification and improve the scalability and processing efficiency of identity authentication.

[0005] In a first aspect, the present application provides a method for managing an Internet of Vehicles identity, the method comprising the following steps:

[0006] The identity management node receives multiple identity authentication requests sent by nodes in the domain, wherein the multiple identity authentication requests are used to verify identity information of multiple nodes in other domains;

[0007] When the identity management node determines, based on the multiple nodes, that the multiple nodes do not belong to nodes within the domain, the multiple identity authentication requests corresponding to the multiple nodes are respectively pre-processed to obtain multiple pre-processed data, the multiple pre-processed data are compressed to obtain compressed data, the compressed data and the private key data of the identity management node are signed to obtain compressed transaction data, and the compressed transaction data is sent to the identity management contract for identity authentication;

[0008] The identity management node receives the identity authentication result of the compressed transaction data returned by the identity management contract, and the identity authentication result includes: multiple verification results of identity information of multiple nodes, and the identity management node provides services for the nodes in the domain based on the multiple verification results.

[0009] In a second aspect, a vehicle network identity management system is provided, the system comprising: an identity management node, the identity management node comprising:

[0010] A communication unit, configured to receive multiple identity authentication requests sent by a node in a domain, wherein the multiple identity authentication requests are used to verify identity information of multiple nodes in other domains;

[0011] A transaction unit, configured to, when determining, based on the multiple nodes, that the multiple nodes do not belong to nodes within the domain, respectively pre-process the multiple identity authentication requests corresponding to the multiple nodes to obtain multiple pre-processed data, compress the multiple pre-processed data to obtain compressed data, perform signature processing on the compressed data and private key data of the identity management node to obtain compressed transaction data, and send the compressed transaction data to the identity management contract for identity authentication;

[0012] The communication unit is used to receive the identity authentication result of the compressed transaction data returned by the identity management contract, wherein the identity authentication result includes: multiple verification results of identity information of multiple nodes;

[0013] A service unit is used to provide services to the nodes in the domain according to the multiple verification results.

[0014] In a third aspect, the present application provides a computer storage medium storing a computer program for electronic data exchange, wherein the computer program enables a computer to execute some or all of the steps described in the first aspect of the present application.

[0015] The embodiments of the present application have the following beneficial effects:

[0016] The technical solution provided by the present application is that the identity management node receives multiple identity authentication requests sent by the nodes in the domain, and the multiple identity authentication requests are used to verify the identity information of multiple nodes in other domains; when the identity management node determines that the multiple nodes do not belong to the nodes in the domain based on the multiple nodes, the multiple identity authentication requests corresponding to the multiple nodes are respectively pre-processed to obtain multiple pre-processed data, the multiple pre-processed data are compressed to obtain compressed data, the compressed data and the private key data of the identity management node are signed to obtain compressed transaction data, and the compressed transaction data is sent to the identity management contract for identity authentication; the identity management node receives the identity authentication result of the compressed transaction data returned by the identity management contract, and the identity authentication result includes: multiple verification results of the identity information of multiple nodes, and the identity management node provides services for the nodes in the domain based on the multiple verification results. The above technical solution can effectively improve the performance and scalability of the system through the off-chain compression technology. In the domain, identity authentication is performed through the domain. For multiple requests from other domains, by aggregating multiple requests into one transaction, the computing pressure and transaction load on the blockchain main chain are greatly reduced, thereby optimizing resource utilization and throughput, realizing multi-person identity management, and improving processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0018] Figure 1 is a schematic diagram of a vehicle network provided in an embodiment of the present application;

[0019] Figure 2 It is a flowchart of a method for managing an Internet of Vehicles identity provided by an embodiment of the present application;

[0020] Figure 3 It is a flowchart of a method for managing an Internet of Vehicles identity provided in Example 1 of the present application;

[0021] Figure 4 This is a flow chart of a method for managing an Internet of Vehicles identity provided in Example 2 of the present application;

[0022] Figure 5 It is a structural diagram of a vehicle network identity management system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0023] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0024] The terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, systems, products or devices.

[0025] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0026] The following is an introduction to the relevant terms involved in this application.

[0027] Blockchain is a distributed ledger technology with the characteristics of decentralization, transparency and immutability. It has been applied in many fields such as finance, supply chain management, medical care, and the Internet of Things.

[0028] The Internet of Vehicles refers to a network system that connects vehicles, road infrastructure, pedestrians and other traffic participants through the Internet. This technology aims to improve traffic safety, optimize traffic flow, enhance driving experience and promote the development of autonomous driving.

[0029] Smart contracts are self-executing contracts embedded in blockchain platforms that automatically execute and verify contract terms based on pre-set conditions. They can ensure the reliable execution and enforcement of agreements without the need for third-party intermediaries.

[0030] The following describes the system architecture of a computer related to an embodiment of the present application.

[0031] The present application also provides a vehicle network, such as Figure 1 The schematic diagram of a vehicle network provided by the present application is shown, which includes: a blockchain, a second-layer network, multiple domains and multiple vehicle-mounted terminals, wherein the vehicle-mounted terminal may include: at least one processor (processor) and a memory (memory) communication interface (Communications Interface) and a bus. Among them, the processor, memory and communication interface can communicate with each other through the bus. The communication interface can transmit information. The processor can call the logic instructions in the memory to execute the method in the above embodiment.

[0032] In addition, the logic instructions in the above-mentioned memory can be implemented in the form of software functional units and can be stored in a computer-readable storage medium when sold or used as an independent product. The above-mentioned logic instructions can also become an operating system, application or computer program, etc.

[0033] The memory, as a computer-readable storage medium, can be configured to store software programs, computer executable programs, such as program instructions or modules corresponding to the methods in the embodiments of the present disclosure. The processor executes functional applications and data processing by running the software programs, instructions or modules stored in the memory, that is, implementing the methods in the above embodiments.

[0034] It is understandable that the domain in this embodiment can be a computer device or a communication node. The above-mentioned second-layer network and blockchain can be composed of multiple computer devices. The above-mentioned computer can be understood as a server. For example, the server includes a cloud server or an edge server. There is no unique limitation here. Of course, in an optional technical scenario, the above-mentioned computer can also be a personal computer (PC), a tablet computer, a laptop computer, and other smart devices. This application does not limit the specific form of the above-mentioned computer, as long as the above-mentioned computer has an operating system and shortcuts.

[0035] The specific methods are introduced in detail below.

[0036] See also Figure 2 , This application also provides a method for managing vehicle network identity, Figure 2 A flowchart of a vehicle networking identity management method provided in this application, the above method can be used in Figure 1 The above computer can be a personal computer, a server, a tablet computer, a laptop computer or other smart devices. The above computer can form a blockchain network or a cloud network. The above method is as follows Figure 2 As shown, the following steps are included:

[0037] Step S201: The identity management node receives multiple identity authentication requests sent by nodes in a domain, where the multiple identity authentication requests are used to verify identity information of multiple nodes in other domains;

[0038] For example, the nodes within the domain may be vehicle-mounted terminals, and the vehicle-mounted terminals may be in various forms, such as mobile terminals or vehicle-mounted smart terminals and other devices. The present application does not limit the specific forms of expression of the nodes within the domain. The above-mentioned domain may be a domain with geographical areas as basic units. For example, vehicles on a certain road may be divided into one domain. Of course, in practical applications, it can also be divided in other ways, such as by the brand of the vehicle-mounted terminal. For example, the vehicle-mounted terminal of brand 1 is one domain, and the vehicle-mounted terminal of brand 2 is another domain, and so on. Of course, the division of the above-mentioned domains can also be determined by brand + region, or divided by various other conditions, such as brand +

[0039] The above-mentioned identity authentication request can be implemented in a variety of ways, such as carrying the above-mentioned identity authentication request through a communication message of an existing communication protocol. Of course, a customized dedicated message can also be used to transmit the above-mentioned identity authentication request. This application does not limit the specific form of the above-mentioned identity authentication request.

[0040] Step S202: When the identity management node determines that the multiple nodes do not belong to the nodes in the domain based on the multiple nodes, the multiple identity authentication requests corresponding to the multiple nodes are respectively pre-processed to obtain multiple pre-processed data, the multiple pre-processed data are compressed to obtain compressed data, the compressed data and the private key data of the identity management node are signed to obtain compressed transaction data, and the compressed transaction data is sent to the identity management contract for identity authentication;

[0041] For example, the multiple identity authentication requests corresponding to the multiple nodes are respectively pre-processed to obtain the multiple pre-processed data, which may specifically include:

[0042] Acquire multiple identity authentication request information, filter each identity authentication request information to obtain pre-processed data corresponding to each processed identity request information, wherein the filtering process specifically includes: extracting necessary parameters and non-essential parameters in an identity authentication request, deleting the non-essential parameters to obtain primary data, identifying the first necessary parameter of the primary data to determine whether there are multiple first necessary parameters, if there are multiple first necessary parameters, retaining the data in which the first necessary parameter appears for the first time in the primary data, deleting the data in which the first necessary parameter appears subsequently, traversing all necessary parameters to obtain an identity authentication request and processed data, and traversing all identity authentication requests to obtain multiple pre-processed data.

[0043] For example, the above-mentioned necessary parameters can be customized parameters, such as organization identification (ID), domain ID, signature (sign), identity certificate, etc. Of course, the above-mentioned necessary parameters can also include other parameters, and the specific form of the necessary parameters is not limited here. The above-mentioned non-essential parameters, such as vehicle terminal brand, message protocol, etc.

[0044] The following example illustrates the corresponding filtering method. Assume that an authentication request contains: NodeID0X00101, OID 0x01, NCA KKKK, sign OX1234, PPID 0001, OID 0x01, NCA KKKK; Assume that the necessary parameters here are: domain ID (NodeID), organization ID (OID), identity certificate (NCA) and sign, then first filter out the non-essential parameters, that is, delete PPID, and get NodeID 0X00101, OID 0x01, NCA KKKK, signOX1234, OID 0x01, NCA KKKK, then determine that NodeID 0X00101 has no overlap, and continue to the next parameter. OID 0x01 has overlap, so delete the next OID 0x01, and continue to the next parameter NCA KKKK. If there is overlap, delete the next NCA KKKK. For sign OX1234 determines that there is no overlap, so the preprocessed data is: NodeID 0X00101, OID 0x01, NCAKKKK, sign OX1234.

[0045] The above numbers and letters are only for illustration and do not represent actual meanings. In application scenarios, the above numbers and subtitles can be replaced according to the application scenarios.

[0046] If there are two of the multiple identity authentication requests, the two identity authentication requests are filtered and processed respectively to obtain processed data, which are then arranged in order to obtain multiple pre-processed data.

[0047] For example, compressing a plurality of pre-processed data to obtain compressed data, and performing signature processing on the compressed data and the private key data of the identity management node to obtain compressed transaction data specifically includes:

[0048] Arrange multiple necessary parameters in each of the multiple preprocessed data in sequence, and then arrange them into a first data column in the sequence of each preprocessed data, add output header data to the header of the first data column to obtain compressed data, sign each preprocessed data and the private data to obtain each preprocessed signature data, arrange each signature data in sequence into a second data column, add signature header data to the second data column to obtain signature data, and combine the compressed data and the signature data to obtain compressed transaction data.

[0049] The following example illustrates the compression method. Here, it is assumed that multiple pre-processed data are: NodeID0X00101, OID 0x01, NCA KKKK, sign OX1234;: NodeID 0X00102, OID 0x02, NCA KKKM, sign OX1235. Then the two pre-processed data are arranged in order to obtain the first data column, that is, NodeID 0X00101, OID 0x01, NCAKKKK, sign OX1234;: NodeID 0X00102, OID 0x02, NCA KKKM, sign OX1235. The header data is added, that is, input to obtain the compressed data: input [NodeID 0X00101, OID 0x01, NCA KKKK, sign OX1234;: NodeID 0X00102, OID 0x02, NCA KKKM, sign OX1235】, the signature data obtained by signing the preprocessed data is: OX4684, OX1375, OX1188, OX137542, OX4685, OX1385, OX1288, OX137544, adding the signature header data to get the proof [OX4684, OX1375, OX1188, OX137542, OX4685, OX1385, OX1288, OX137544], which are combined to get the compressed transaction data, namely, input [NodeID 0X00101, OID 0x01, NCAKKKK, sign OX1234; NodeID 0X00102, OID 0x02, NCA KKKM, sign OX1235], proof [OX4684, OX1375, OX1188, OX137542, OX4685, OX1385, OX1288, OX137544]; where input is the output header data and proof is the signature header data. In other application scenarios, the above header data can be expressed in other forms, which will not be described here.

[0050] Step S203: The identity management node receives the identity authentication result of the compressed transaction data returned by the identity management contract, wherein the identity authentication result includes: multiple verification results of identity information of multiple nodes, and the identity management node provides services for the nodes within the domain based on the multiple verification results.

[0051] For example, the above-mentioned identity management contract can be set in any node of the blockchain, and of course it can also be jointly set in multiple blockchain nodes. This application does not limit the specific form of the identity management contract.

[0052] The technical solution provided by the present application is that the identity management node receives multiple identity authentication requests sent by the nodes in the domain, and the multiple identity authentication requests are used to verify the identity information of multiple nodes in other domains; when the identity management node determines that the multiple nodes do not belong to the nodes in the domain based on the multiple nodes, the multiple identity authentication requests corresponding to the multiple nodes are respectively pre-processed to obtain multiple pre-processed data, the multiple pre-processed data are compressed to obtain compressed data, the compressed data and the private key data of the identity management node are signed to obtain compressed transaction data, and the compressed transaction data is sent to the identity management contract for identity authentication; the identity management node receives the identity authentication result of the compressed transaction data returned by the identity management contract, and the identity authentication result includes: multiple verification results of the identity information of multiple nodes, and the identity management node provides services for the nodes in the domain based on the multiple verification results. The above technical solution can effectively improve the performance and scalability of the system through the off-chain compression technology. In the domain, identity authentication is performed through the domain. For multiple requests from other domains, by aggregating multiple requests into one transaction, the computing pressure and transaction load on the blockchain main chain are greatly reduced, thereby optimizing resource utilization and throughput, realizing multi-person identity management, and improving processing efficiency.

[0053] For example, the above method may further include: the identity management contract performs identity authentication based on the compressed transaction data to obtain an identity authentication result, specifically including:

[0054] Extract multiple necessary parameters corresponding to an identity request message in the compressed transaction data and signature data corresponding to the multiple necessary parameters, identify the multiple necessary parameters to determine the domain ID corresponding to the identity request message, if the domain ID is not a non-local domain, send an assistance verification message to the domain ID node, the assistance verification message includes an identity certificate corresponding to the identity request message, receive public key information corresponding to the identity certificate returned by the domain ID node, use the public key information to decrypt the signature data to obtain decrypted data, if the decrypted data is different from the corresponding necessary parameters, discard the identity authentication message, determine that the identity request message verification is unsuccessful, if the decrypted data is the same as the corresponding necessary parameters, determine that the identity request message verification is successful, and traverse all the identity request information in the transaction data to obtain the identity authentication result.

[0055] The above technical solution obtains the corresponding public key information by requesting assistance from the node of the corresponding domain ID for identity authentication requests that do not belong to the domain ID, and then verifies the identity information with its signature data (i.e. encrypted data). It directly verifies the identity request information within the domain, so that only cross-domain identity authentication will be requested, reducing the amount of data transmission and improving verification efficiency.

[0056] For example, the above method may further include:

[0057] The identity management node receives the identity authentication request from the node in the domain again, and when it is determined that other nodes in the identity authentication request belong to the node in this domain, it extracts the identity certificate in the identity request, performs local verification on the identity certificate, and provides services to the node in the domain after successful verification.

[0058] For local nodes, the identity management node performs verification directly without submitting it to the identity management contract. This reduces the amount of data transmission and further improves the efficiency of data transmission.

[0059] Embodiment 1

[0060] Embodiment 1 of the present application provides a method for managing an Internet of Vehicles identity. Figure 3 A flowchart of a method for managing an Internet of Vehicles identity is provided in Example 1 of the present application. The method can be used in Figure 1 The computer can be a personal computer, a server, a tablet computer, a laptop computer or other smart devices. The method of the present application takes node A of domain 1 as an example. The computer can form a blockchain network or a cloud network. The method is as follows Figure 3 As shown, the following steps are included:

[0061] Step S301: Node A prepares data or ID required for identity authentication.

[0062] Step S302: Node A initiates an identity authentication request to the Rollup1 component (ie, the identity management node) of domain 1, requesting to verify the identity information of another node B in domain 1.

[0063] Step S303: After receiving the request, Rollup1 verifies the legitimacy of the request and prepares to interact with the identity management contract in domain 1;

[0064] Note that at this time Rollup can aggregate multiple verification requests into one transaction. Since there is only one verification request here, no aggregation is required.

[0065] Step S304: Rollup1 sends the identity authentication request of node A to the identity management contract of domain 1.

[0066] Step S305: The identity management contract queries the identity information repository in domain 1 according to the ID (unique identifier, such as: "0x951753") of node B in the identity authentication request, and searches for the identity information of node B (including but not limited to domain ID, organization ID, authority information, node status, reputation information, location information, insurance information, etc.).

[0067] Step S306: The identity management contract confirms the legitimacy of node B’s identity and generates a verification response event, which Rollup1 monitors.

[0068] Note that the verification response event monitored at this time actually includes the results of multiple verification requests. For the sake of example, only the verification result of node B is pointed out.

[0069] Step S307: After Rollup1 monitors the verification response event of the identity management contract, it further processes the identity authentication result and generates response data for all verification requests.

[0070] Taking node A as an example, verification response data RA for the node will be generated here.

[0071] Step S308: Rollup1 returns the verification response data RA to node A, completes the identity authentication process, and provides services for node A.

[0072] The technical solution provided in the embodiment of the present application realizes the identity authentication request for the local node A, and then provides corresponding services for node A.

[0073] Embodiment 2

[0074] Embodiment 2 of the present application provides a method for managing an Internet of Vehicles identity. Figure 4 This is a flow chart of a method for managing an Internet of Vehicles identity provided in Example 2 of the present application. The method can be used in Figure 1 The system architecture shown in the figure is executed, the above-mentioned computer can be a personal computer, a server, a tablet computer, a laptop computer or other smart devices. The method of the present application takes node A of domain 1 as an example. The above-mentioned computer can form a blockchain network or a cloud network. The above-mentioned method is as follows Figure 4 As shown, the following steps are included:

[0075] Step S401: Node A initiates an identity authentication request for node B in domain 2.

[0076] The request is processed by Rollup1.

[0077] Step S402: Rollup1 detects that this is a cross-domain verification request and cannot be completed within domain 1, so it sends the request to the identity management contract.

[0078] Step S403: The multi-domain interaction contract of the identity management contract receives the request from Rollup1, and identifies the target as domain 2 based on the ID of node B (assuming that the first two digits represent the domain number, such as "0x021753", "02" represents domain 2).

[0079] Step S404: The multi-domain interaction contract interacts with the identity management contract of domain 2 and requests the identity information related to node B from the domain 2 node.

[0080] Step S405: The identity management contract of domain 2 searches for the identity information of node B according to the request of the multi-domain interaction contract and confirms the legitimacy.

[0081] Step S406: The identity management contract returns the desensitized identity information to the multi-domain interaction contract (ie, the public key information of node B).

[0082] This information only contains necessary verification data (public key information) to ensure that sensitive information will not be leaked. In other application scenarios, it may also contain other verification data. This is only for example purposes. In other application scenarios, the specific form of the above verification data is not limited.

[0083] Step S407: The multi-domain interaction contract processes the response from domain 2 and sends the verification result back to the Rollup1 component of domain 1.

[0084] Step S408: After receiving the cross-domain verification result, Rollup1 performs further processing and returns the result to node A that initiated the request, providing services for node A.

[0085] Specifically, within each domain, the off-chain compression component will batch process identity authentication and information access requests from nodes, package and aggregate them into a single transaction and submit it to the multi-domain interaction contract on the blockchain (the specific packaging and aggregation method can be found in the detailed scheme of step S202, which will not be repeated here). This not only reduces the number of transactions on the chain, but also avoids repeated calculation operations. For example, when multiple nodes request cross-domain identity authentication in the same period, all necessary calculations and verification logic will be completed off-chain first, and only the final verification results will be packaged and submitted to the chain. This aggregation process ensures the simplicity of on-chain calculations and avoids redundant calculations on the same identity data. At the same time, since some redundant calculations are avoided on the chain, this also means that some private information does not have to be sent to the chain, thereby achieving the purpose of privacy protection.

[0086] From the data point of view, suppose that each domain generates N transaction requests in a certain period of time. At this time, if this solution is not available, the transaction throughput faced by the contract can only be N*4. With Rollup technology, N transactions can be compressed into M transactions according to batch size B. Then M=N / B. At this time, through the aggregation of the second-layer network, the transaction pressure faced by the blockchain is reduced to M*4 (0<M<N). As a result, the transaction load pressure of the main chain is reduced.

[0087] Therefore, the above-mentioned packaging and aggregation technical solution not only improves the efficiency of identity authentication and information access, but also significantly improves the throughput of the blockchain system by adhering to the principles of batch processing and aggregated transactions, reduces the consumption of on-chain resources, and enhances the overall scalability and responsiveness of the system.

[0088] See also Figure 5 , Figure 5 A vehicle network identity management system provided in this application includes: an identity management node, and the identity management node includes:

[0089] A communication unit, configured to receive multiple identity authentication requests sent by a node in a domain, wherein the multiple identity authentication requests are used to verify identity information of multiple nodes in other domains;

[0090] A transaction unit, configured to, when determining, based on the multiple nodes, that the multiple nodes do not belong to nodes within the domain, respectively pre-process the multiple identity authentication requests corresponding to the multiple nodes to obtain multiple pre-processed data, compress the multiple pre-processed data to obtain compressed data, perform signature processing on the compressed data and private key data of the identity management node to obtain compressed transaction data, and send the compressed transaction data to the identity management contract for identity authentication;

[0091] The communication unit is used to receive the identity authentication result of the compressed transaction data returned by the identity management contract, wherein the identity authentication result includes: multiple verification results of identity information of multiple nodes;

[0092] A service unit is used to provide services to the nodes in the domain according to the multiple verification results.

[0093] For example,

[0094] The transaction unit is specifically used to obtain multiple identity authentication request information, filter each identity authentication request information to obtain pre-processed data corresponding to each processed identity request information, and the filtering process specifically includes: extracting necessary parameters and non-essential parameters in an identity authentication request, deleting the non-essential parameters to obtain primary data, identifying the first necessary parameter of the primary data to determine whether there are multiple first necessary parameters, if there are multiple first necessary parameters, retaining the data where the first necessary parameter appears for the first time in the primary data, deleting the data where the first necessary parameter appears subsequently, traversing all necessary parameters to obtain an identity authentication request and processed data, and traversing all identity authentication requests to obtain multiple pre-processed data.

[0095] For example,

[0096] The transaction unit is specifically used to arrange multiple necessary parameters in each of the multiple preprocessed data in sequence, and then arrange them into a first data column in the sequence of each preprocessed data, add output header data to the header of the first data column to obtain compressed data, sign each preprocessed data and the private data to obtain each preprocessed signature data, arrange each signature data in sequence into a second data column, add signature header data to the second data column to obtain signature data, and combine the compressed data and the signature data to obtain compressed transaction data.

[0097] For example, the system further includes: an identity management contract, which is used to perform identity authentication based on the compressed transaction data to obtain an identity authentication result, specifically including:

[0098] Extract multiple necessary parameters corresponding to an identity request message in the compressed transaction data and signature data corresponding to the multiple necessary parameters, identify the multiple necessary parameters to determine the domain ID corresponding to the identity request message, if the domain ID is not a non-local domain, send an assistance verification message to the domain ID node, the assistance verification message includes an identity certificate corresponding to the identity request message, receive public key information corresponding to the identity certificate returned by the domain ID node, use the public key information to decrypt the signature data to obtain decrypted data, if the decrypted data is different from the corresponding necessary parameters, discard the identity authentication message, determine that the identity request message verification is unsuccessful, if the decrypted data is the same as the corresponding necessary parameters, determine that the identity request message verification is successful, and traverse all the identity request information in the transaction data to obtain the identity authentication result.

[0099] An embodiment of the present application also provides a computer storage medium, wherein the computer storage medium stores a computer program for electronic data exchange, wherein the computer program enables a computer to execute part or all of the steps of any method described in the above method embodiments, and the above computer includes an electronic device.

[0100] The embodiment of the present application also provides a computer program product, the computer program product includes a non-transitory computer-readable storage medium storing a computer program, the computer program is operable to cause a computer to execute some or all of the steps of any method described in the method embodiment. The computer program product may be a software installation package, and the computer includes an electronic device.

[0101] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0102] In the several embodiments provided in the present application, it should be understood that the disclosed methods, systems and systems can be implemented in other ways. For example, the system embodiments described above are only schematic; for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation; for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of systems or units, which can be electrical, mechanical or other forms.

[0103] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

[0105] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform some steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: a USB flash drive, a mobile hard disk, a magnetic disk, an optical disk, a volatile memory or a non-volatile memory. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM) or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct memory bus random access memory (DBR RAM). RAM, rambus RAM, DR RAM). and other media that can store program codes.

[0106] Although the present invention is disclosed as above, the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions without departing from the spirit and scope of the present invention, and can make various changes and modifications, including the combination of the above-mentioned different functions and implementation steps, including software and hardware implementation methods, all of which are within the scope of protection of the present invention.

Claims

1. A method for managing identity in an Internet of Vehicles, characterized in that: The method comprises the following steps: The identity management node receives multiple identity authentication requests sent by nodes in the domain, wherein the multiple identity authentication requests are used to verify identity information of multiple nodes in other domains; When the identity management node determines, based on the multiple nodes, that the multiple nodes do not belong to nodes within the domain, the multiple identity authentication requests corresponding to the multiple nodes are respectively pre-processed to obtain multiple pre-processed data, the multiple pre-processed data are compressed to obtain compressed data, the compressed data and the private key data of the identity management node are signed to obtain compressed transaction data, and the compressed transaction data is sent to the identity management contract for identity authentication; The identity management node receives the identity authentication result of the compressed transaction data returned by the identity management contract, and the identity authentication result includes: multiple verification results of identity information of multiple nodes, and the identity management node provides services for the nodes in the domain based on the multiple verification results.

2. The vehicle networking identity management method according to claim 1, characterized in that: The step of pre-processing the multiple identity authentication requests corresponding to the multiple nodes to obtain the multiple pre-processed data specifically includes: Acquire multiple identity authentication request information, filter each identity authentication request information to obtain pre-processed data corresponding to each processed identity request information, wherein the filtering process specifically includes: extracting necessary parameters and non-essential parameters in an identity authentication request, deleting the non-essential parameters to obtain primary data, identifying the first necessary parameter of the primary data to determine whether there are multiple first necessary parameters, if there are multiple first necessary parameters, retaining the data in which the first necessary parameter appears for the first time in the primary data, deleting the data in which the first necessary parameter appears subsequently, traversing all necessary parameters to obtain an identity authentication request and processed data, and traversing all identity authentication requests to obtain multiple pre-processed data.

3. The vehicle networking identity management method according to claim 1 or 2, characterized in that: The step of compressing the plurality of pre-processed data to obtain compressed data and performing signature processing on the compressed data and the private key data of the identity management node to obtain compressed transaction data specifically includes: Arrange multiple necessary parameters in each of the multiple preprocessed data in sequence, and then arrange them into a first data column in the sequence of each preprocessed data, add output header data to the header of the first data column to obtain compressed data, sign each preprocessed data and the private data to obtain each preprocessed signature data, arrange each signature data in sequence into a second data column, add signature header data to the second data column to obtain signature data, and combine the compressed data and the signature data to obtain compressed transaction data.

4. The vehicle networking identity management method according to claim 3, characterized in that: The method further includes: the identity management contract performs identity authentication according to the compressed transaction data to obtain an identity authentication result, specifically including: Extract multiple necessary parameters corresponding to an identity request message in the compressed transaction data and signature data corresponding to the multiple necessary parameters, identify the multiple necessary parameters to determine the domain ID corresponding to the identity request message, if the domain ID is not a non-local domain, send an assistance verification message to the domain ID node, the assistance verification message includes an identity certificate corresponding to the identity request message, receive public key information corresponding to the identity certificate returned by the domain ID node, use the public key information to decrypt the signature data to obtain decrypted data, if the decrypted data is different from the corresponding necessary parameters, discard the identity authentication message, determine that the identity request message verification is unsuccessful, if the decrypted data is the same as the corresponding necessary parameters, determine that the identity request message verification is successful, and traverse all the identity request information in the transaction data to obtain the identity authentication result.

5. The vehicle networking identity management method according to claim 1, characterized in that: The method further comprises: The identity management node receives the identity authentication request from the node in the domain again, and when it is determined that other nodes in the identity authentication request belong to the node in this domain, it extracts the identity certificate in the identity request, performs local verification on the identity certificate, and provides services to the node in the domain after successful verification.

6. A vehicle networking identity management system, characterized in that: The system comprises: an identity management node, wherein the identity management node comprises: A communication unit, configured to receive multiple identity authentication requests sent by a node in a domain, wherein the multiple identity authentication requests are used to verify identity information of multiple nodes in other domains; A transaction unit, configured to, when determining, based on the multiple nodes, that the multiple nodes do not belong to nodes within the domain, respectively pre-process the multiple identity authentication requests corresponding to the multiple nodes to obtain multiple pre-processed data, compress the multiple pre-processed data to obtain compressed data, perform signature processing on the compressed data and private key data of the identity management node to obtain compressed transaction data, and send the compressed transaction data to the identity management contract for identity authentication; The communication unit is used to receive the identity authentication result of the compressed transaction data returned by the identity management contract, wherein the identity authentication result includes: multiple verification results of identity information of multiple nodes; A service unit is used to provide services to the nodes in the domain according to the multiple verification results.

7. The vehicle networking identity management system according to claim 6, characterized in that: The transaction unit is specifically used to obtain multiple identity authentication request information, filter each identity authentication request information to obtain pre-processed data corresponding to each processed identity request information, and the filtering process specifically includes: extracting necessary parameters and non-essential parameters in an identity authentication request, deleting the non-essential parameters to obtain primary data, identifying the first necessary parameter of the primary data to determine whether there are multiple first necessary parameters, if there are multiple first necessary parameters, retaining the data where the first necessary parameter appears for the first time in the primary data, deleting the data where the first necessary parameter appears subsequently, traversing all necessary parameters to obtain an identity authentication request and processed data, and traversing all identity authentication requests to obtain multiple pre-processed data.

8. The vehicle networking identity management system according to claim 6 or 7, characterized in that: The transaction unit is specifically used to arrange multiple necessary parameters in each of the multiple preprocessed data in sequence, and then arrange them into a first data column in the sequence of each preprocessed data, add output header data to the header of the first data column to obtain compressed data, sign each preprocessed data and the private data to obtain each preprocessed signature data, arrange each signature data in sequence into a second data column, add signature header data to the second data column to obtain signature data, and combine the compressed data and the signature data to obtain compressed transaction data.

9. The vehicle networking identity management system according to claim 8, characterized in that: The system further includes: an identity management contract, which is used to perform identity authentication based on the compressed transaction data to obtain an identity authentication result, specifically including: Extract multiple necessary parameters corresponding to an identity request message in the compressed transaction data and signature data corresponding to the multiple necessary parameters, identify the multiple necessary parameters to determine the domain ID corresponding to the identity request message, if the domain ID is not a non-local domain, send an assistance verification message to the domain ID node, the assistance verification message includes an identity certificate corresponding to the identity request message, receive public key information corresponding to the identity certificate returned by the domain ID node, use the public key information to decrypt the signature data to obtain decrypted data, if the decrypted data is different from the corresponding necessary parameters, discard the identity authentication message, determine that the identity request message verification is unsuccessful, if the decrypted data is the same as the corresponding necessary parameters, determine that the identity request message verification is successful, and traverse all the identity request information in the transaction data to obtain the identity authentication result.

10. A computer storage medium storing a computer program for electronic data exchange, characterized in that: The computer program enables a computer to execute the steps of the method according to any one of claims 1 to 5.

Images