Vehicle authorization method and device and electronic equipment

Abstract

The invention discloses a vehicle authorization method and device and electronic equipment, during vehicle authorization, vehicle authorization information and authorized user information are associated and stored, the authorized user information is used for defining the identity of an authorized operator, and after the authorization operation is completed, the stored vehicle authorization information and the authorized user information are stored in the vehicle authorization information and the authorized user information. The identity of an authorized operator can be clearly authorized by a vehicle owner or a vehicle company, the authenticity of vehicle authorization information is ensured, and the safety and credibility of data are improved.

Description

Technical Field

[0001] The present invention relates to the field of software development technology, and in particular to a vehicle authorization method, device and electronic device, and to vehicle authorization technology and alliance chain technology. Through this invention, the trust problem in vehicle authorization can be effectively solved, and after-sales problems can be conveniently solved. Background Art

[0002] With the popularity of smart cars, vehicle authorization has become an important function. In the current market, smart car owners can authorize their vehicles, and authorized users can perform vehicle control operations through authorization.

[0003] In the prior art, the car owner performs authorization operation through a mobile client, which is simple to operate, but there is a possibility that the car owner's identity may be impersonated and the vehicle may be authorized to a person not recognized by the car owner against the car owner's will. Therefore, the security is poor and it may cause a crisis of trust between the car owner and the car company. Summary of the invention

[0004] The present application provides a vehicle authorization method, device and electronic device, which improve the security and credibility of vehicle authorization by associating and storing vehicle authorization information with authorized user information.

[0005] In view of the above problems, the present application is proposed to provide a vehicle authorization method, device and electronic device that overcome the above problems or at least partially solve the above problems.

[0006] In a first aspect, a vehicle authorization method is provided, comprising:

[0007] Receive vehicle authorization information and authorized user information, the vehicle authorization information includes: vehicle owner information, vehicle information and authorized user information, the authorized user information includes: authorized user's facial information;

[0008] Perform authorization operations based on vehicle information and authorized user information;

[0009] If the authorization operation is successful, the vehicle authorization information and the authorized user information will be associated and stored.

[0010] Optionally, the vehicle authorization information is associated and stored with the authorized user information, including:

[0011] Bind the vehicle authorization information and the authorized user information to obtain binding information;

[0012] The binding information is stored in a preset cloud database, and / or the binding information is uploaded to the consortium chain for on-chain evidence storage.

[0013] Optionally, if the operation of uploading the binding information to the alliance chain for on-chain evidence storage fails, the binding information is uploaded to the alliance chain again for on-chain evidence storage until the number of failures reaches a preset upper limit of failures, and then it is determined that the evidence storage has failed.

[0014] Optionally, if the operation of storing the binding information in the preset cloud database fails, it is determined that the evidence storage fails.

[0015] Optionally, if it is determined that the evidence storage has failed, a message indicating the authorization failure is sent to the authorized user.

[0016] Optionally, before performing the authorization operation based on the vehicle information and the authorized user information, the following steps are also included:

[0017] Check whether the vehicle authorization information meets the preset requirements. If not, send an authorization failure message to the authorized user; the preset requirements include at least one of the following requirements:

[0018] The content and format of the owner information, vehicle information or authorized user information are correct;

[0019] The owner information and the vehicle information are associated;

[0020] The vehicle owner information and the authorized user information are associated.

[0021] Optional, authorization operations, including:

[0022] Associate vehicle information with authorized user information.

[0023] Optionally, if the authorization operation fails, an authorization failure message is sent to the authorized user.

[0024] In a second aspect, a vehicle authorization device is provided, comprising:

[0025] An information receiving unit, used to receive vehicle authorization information and authorized user information, the vehicle authorization information includes: vehicle owner information, vehicle information and authorized user information, the authorized user information includes: authorized user's facial information;

[0026] An authorization unit, used to perform authorization operations according to vehicle information and authorized user information;

[0027] The association and evidence storage unit is used to associate and store the vehicle authorization information with the authorized user information if the authorization operation is successful.

[0028] In a third aspect, an electronic device is provided, which is used to receive vehicle authorization information input by an authorized user, collect authorized user information, and send the vehicle authorization information and authorized user information to a vehicle authorization device; the vehicle authorization information includes: vehicle owner information, vehicle information and authorized user information, and the authorized user information includes: authorized user's facial information;

[0029] Receive authorization success or authorization failure information sent by the vehicle authorization device.

[0030] In a fourth aspect, the present application also provides a server, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the server executes the method provided in the first aspect.

[0031] In a fifth aspect, the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the computer executes the method provided in the first aspect.

[0032] In a sixth aspect, the present application also provides a computer program product, including a computer program, which, when executed by a computer, enables the computer to execute the method provided in the first aspect.

[0033] The technical solution provided by this application has at least the following technical effects or advantages:

[0034] The vehicle authorization method, device and electronic device provided in the present application associate and store the vehicle authorization information with the authorized user information when authorizing the vehicle. The authorized user information is used to clarify the identity of the authorized operator. After the authorization operation is completed, the stored vehicle authorization information and authorized user information can be used by the vehicle owner or automobile company to clarify the identity of the authorized operator, ensure the authenticity of the vehicle authorization information, and improve the security and credibility of the data.

[0035] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present application. Also, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0037] Figure 1This is a flow chart of the vehicle authorization method in the embodiment of the present application;

[0038] Figure 2 This is a flow chart of vehicle authorization between the car owner and the car company in the embodiment of the present application;

[0039] Figure 3 This is a flow chart of the automobile cloud performing simultaneous database evidence storage and alliance chain evidence storage in an embodiment of the present application;

[0040] Figure 4 The vehicle authorization device wireframe in the embodiment of the present application Figure 1 ;

[0041] Figure 5 The vehicle authorization device wireframe in the embodiment of the present application Figure 2 ;

[0042] Figure 6 It is a wireframe diagram of the association and evidence storage unit in the embodiment of the present application;

[0043] Figure 7 This is a schematic diagram of a server in an embodiment of the present application. DETAILED DESCRIPTION

[0044] Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings.

[0045] Various structural schematic diagrams according to embodiments of the present application are shown in the accompanying drawings. These figures are not drawn to scale, and some details are magnified and some details may be omitted for the purpose of clear expression. The shapes of various regions and layers shown in the figures and the relative sizes and positional relationships therebetween are only exemplary, and may deviate in practice due to manufacturing tolerances or technical limitations, and those skilled in the art may further design regions / layers with different shapes, sizes, and relative positions according to actual needs.

[0046] In order to better understand the above-mentioned technical scheme, the above-mentioned technical scheme will be described in detail below in combination with specific implementation methods. It should be understood that the embodiments of the present disclosure and the specific features in the embodiments are detailed descriptions of the technical scheme of the present application, rather than limitations on the technical scheme of the present application. In the absence of conflict, the embodiments of the present application and the technical features in the embodiments can be combined with each other.

[0047] With the popularity of smart cars, vehicle authorization has become an important function. In the current market, smart car owners select the vehicle and authorized user to be authorized on the client and perform authorization operations. The authorized user can perform vehicle control operations through authorization. However, this traditional vehicle authorization method has many problems and hidden dangers, especially the trust issue is particularly prominent.

[0048] Authorization records are stored on the automobile company's cloud platform. Although this method realizes the basic vehicle authorization function, it exposes many problems in actual application.

[0049] The two most obvious problems are as follows:

[0050] Risk of misoperation by the car owner: The car owner may authorize the vehicle to an unfamiliar user due to negligence or misoperation during operation, resulting in property loss. At this time, the car owner may question the data records provided by the car company and claim that the car company has tampered with the data, thus causing a crisis of trust.

[0051] Car company program loopholes or misoperation: Car company cloud platforms may have program loopholes or misoperation, causing vehicles to be mistakenly authorized to unfamiliar users. At this point, the car company may refuse to acknowledge the problem and tamper with the database to evade responsibility, further exacerbating the trust problem.

[0052] In view of this, this application provides a vehicle authorization method, please refer to Figure 1 , Figure 1 This is a flow chart of a vehicle authorization method in an embodiment of the present application, and the vehicle authorization method includes:

[0053] S101. Receive vehicle authorization information and authorized user information. The vehicle authorization information includes: vehicle owner information, vehicle information and authorized user information. The authorized user information includes: authorized user's facial information.

[0054] Authorized users refer to users who authorize vehicles on mobile clients. Vehicle owner information includes the owner's mobile phone number, ID number, account number, facial information, fingerprint information, and other information related to the owner. Vehicle information includes the vehicle frame number of the vehicle authorized for use by others, or other information related to the vehicle. Authorized user information includes the authorized user's mobile phone number, ID number, account number, or facial information, fingerprint information, and other information related to the authorized user.

[0055] It is understandable that when the authorized user is the vehicle owner himself, the vehicle owner information and the vehicle information are correlated.

[0056] S102: Perform authorization operation according to vehicle information and authorized user information.

[0057] Usually, the authorization operation is performed by the automobile company's cloud platform. After the authorized user enters the vehicle authorization information and the authorized user information through the client and submits them, the automobile company's cloud platform performs the authorization operation based on the vehicle authorization information. The specific authorization operation includes: associating the vehicle information with the authorized user information. After the authorization operation is successful, the authorized user obtains the right to use the vehicle.

[0058] S103. If the authorization operation is successful, the vehicle authorization information is associated with the authorized user information and stored as evidence.

[0059] The authorized user may be the owner of the authorized vehicle, someone the owner knows, or someone the owner does not know. When the authorized user is not the owner, there is no correlation between the authorized user information and the vehicle information. After the vehicle authorization operation, the authorized user's information, such as facial information, is associated and stored with the vehicle authorization information. If the owner makes an operational error, such as entering incorrect authorization information, resulting in the vehicle not being authorized to the authorized user recognized by the owner, or the vehicle being authorized to a stranger who is not recognized by the owner, resulting in property loss, based on the stored vehicle authorization information and the facial information associated with it, it can also be clearly stated that it was the result of the owner's negligence or misoperation, thereby avoiding the owner's misunderstanding of the car company and, to a certain extent, avoiding a crisis of trust.

[0060] In another case, if the car owner's identity is impersonated, the stored vehicle authorization information and the facial information associated with it can help the car owner find out who authorized the operation. If the person who authorized the operation is not someone recognized by the car owner, it will help the police identify the person who impersonated the car owner based on the facial information, thereby improving the security and reliability of the authorization process.

[0061] It is understandable that a further restriction condition can be set that the authorized user must be the car owner himself. The car owner's mobile phone number, portrait, ID number and other information can be pre-stored in the database and bound to the vehicle's license plate number. After receiving the vehicle authorization information and authorized user information, the car owner information in the vehicle authorization information is compared with the authorized user information. For example, the authorized user's facial information is compared with the pre-stored car owner's portrait information. If it is determined according to the comparison result that the authorized user is the car owner himself, the authorization operation can be performed. This can further enhance the security of vehicle authorization and prevent the car owner's identity from being impersonated and the vehicle from being authorized to other people, causing property loss to the car owner.

[0062] In some optional implementations, before performing the authorization operation according to the vehicle information and the authorized user information, the method further includes:

[0063] Check whether the vehicle authorization information meets the preset requirements. If not, send an authorization failure message to the authorized user; the preset requirements include at least one of the following requirements:

[0064] The content and format of the owner information, vehicle information or authorized user information are correct;

[0065] The owner information and the vehicle information are associated;

[0066] The vehicle owner information and the authorized user information are associated.

[0067] For example, after the authorized user enters the vehicle authorization information and authorized user information through the client, the server of the automobile cloud platform receives this information, checks the integrity, correctness, and legality of the data to make an authority decision, and prevents other users from impersonating the vehicle owner and authorizing the vehicle to a person the car owner does not recognize. It also prevents the authorized user from entering incorrect vehicle authorization information, the number of authorized users exceeding the limit, the authorized user authorizing the vehicle to a person the car owner does not recognize, and other problems, thereby improving the security of authorization operations.

[0068] Exemplarily, the preset requirements can be set as the car owner information and the authorized user information are associated with each other and the car owner information and the vehicle information are associated with each other, that is, the car owner and the authorized user must be the same person, the car owner's mobile phone number and the vehicle's frame number are bound, and when the authorized user enters the vehicle authorization information into the mobile client, the facial recognition module installed on the mobile client collects the authorized user's facial information, and compares the authorized user's facial information with the pre-stored car owner's facial information. After determining that the authorized user is the car owner himself, the authorization operation is performed.

[0069] The introduction of facial recognition verification further improves the security of the authorization process. Only car owners who have passed facial recognition verification can perform authorization operations, thus preventing risks such as identity fraud.

[0070] In some optional implementations, the vehicle authorization information is checked to see if it meets preset requirements. If so, a message indicating that the inspection is passed is sent to the authorized user to facilitate the authorized user to understand the current progress.

[0071] In some optional implementations, if the authorization operation fails, a message indicating the authorization failure is sent to the authorized user.

[0072] The authorization operation of the automotive cloud platform usually associates the vehicle information with the authorized user information. If the association fails, the authorized user does not obtain the permission to use the vehicle. Therefore, if the authorization fails, the result of the authorization operation failure is fed back to the authorized user so that the authorized user can understand the situation and submit the vehicle authorization information again.

[0073] The reasons leading to the authorization failure during the operation include, but are not limited to: abnormality of the car cloud platform server, restricted functions of the car cloud platform, etc.

[0074] In some optional implementations, if the authorization operation is successful, a message indicating the success of the authorization operation is sent to the authorized user.

[0075] It is understandable that a successful authorization operation does not mean that the authorization is successful. The purpose of sending a message indicating the successful authorization operation to the authorized user is to show the authorized user the progress of the operation in S102. In S103, if the vehicle authorization information is successfully associated with the authorized user information and the evidence is stored successfully, a message indicating the authorization function is sent to the authorized user. At this point, the vehicle authorization is completed.

[0076] In some optional implementations, the vehicle authorization information is associated with the authorized user information and stored as evidence, including:

[0077] Bind the vehicle authorization information and the authorized user information to obtain binding information;

[0078] The binding information is stored in a preset cloud database, and / or the binding information is uploaded to the consortium chain for on-chain evidence storage.

[0079] Although the cloud platform of the automobile company can be supervised by the corresponding regulatory agency and all operations can be backed up. However, this solution requires a high cost, and there is currently no such specialized regulatory agency. In contrast, the operation of associating and storing the vehicle authorization information with the authorized user information provided in the embodiment of the present application is more advantageous in terms of cost and feasibility.

[0080] Blockchain technology, also known as distributed ledger technology, is the underlying technology of cryptocurrencies such as Bitcoin and Ethereum. Blockchain uses a cryptographic signature algorithm to package transaction data into blocks. It uses a decentralized consensus mechanism to generate and update data and uses smart contracts to achieve automation. Its decentralized, tamper-proof and traceable characteristics solve the absolute rights problem of operating databases in traditional systems, making it a decentralized self-made system that does not rely on third parties and is jointly governed by multiple parties.

[0081] The consortium chain is a blockchain managed by some organizations, and some or all of its functions are only open to members within the consortium. It can be seen as a compromise between public and private chains. The information reading and accounting rules of the consortium chain are stipulated by the consortium's agreement, also known as a permissioned chain. The consortium chain has low transaction costs, high accounting efficiency, strong controllability, and privacy protection. At present, most blockchain applications in my country are developed based on the consortium chain.

[0082] Once the alliance chain is uploaded to the chain, no modification operation can be performed. This also ensures that the final data is tamper-proof and absolutely reliable. It can avoid the problem that when the vehicle is mistakenly authorized to an unfamiliar user due to program loopholes or misoperation in the automobile company's cloud platform, the automobile company tampers with the vehicle authorization information to evade responsibility, thereby further avoiding trust issues between the automobile company and the car owner.

[0083] The vehicle authorization information is associated with the authorized user information and combined with the on-chain evidence storage of the alliance chain to ensure the uniqueness and authenticity of the vehicle authorization operation, while improving the security and credibility of the data.

[0084] In some optional implementations, if the operation of uploading the binding information to the alliance chain for on-chain evidence storage fails, the binding information is uploaded to the alliance chain again for on-chain evidence storage until the number of failures reaches a preset upper limit of failures, and then it is determined that the evidence storage has failed.

[0085] It is understandable that the design of the alliance chain and the design of the blockchain browser provided to the outside world can form corresponding patents. For example, the blockchain browser needs to allow users to query the vehicle's authorization information, but the privacy of other users needs to be protected.

[0086] During the consortium chain upload process, failures may occur due to contract compilation failure, transaction encapsulation failure, failure to obtain handling fees, server abnormalities, etc. If repeated uploads still fail, it is determined that the evidence has failed, and a message of authorization failure needs to be sent to the authorized user.

[0087] In some optional implementations, if the operation of storing the binding information in the preset cloud database fails, it is determined that the evidence storage has failed.

[0088] The binding information is stored in a preset cloud database, which is convenient for authorized users to view at any time. During the process of storing the binding information in the preset cloud database, it may fail due to server abnormalities and other reasons. If it is determined that the evidence storage has failed, an authorization failure message will be sent to the authorized user.

[0089] Dual evidence storage is carried out in the cloud database and the alliance chain. First, the car cloud database is used for evidence storage, and then the alliance chain is uploaded after success. Because the cloud database can be rolled back, the alliance chain cannot perform any modification operations once it is uploaded. This also ensures that the authorized user or car owner can check the authorization information at any time, while ensuring that the data of the authorization information cannot be tampered with and is absolutely reliable.

[0090] Through face recognition verification and dual evidence storage mechanism, the vehicle authorization method provided by the embodiment of the present invention effectively solves the trust problem in vehicle authorization. Whether it is caused by the owner's misoperation or the car company's program loopholes, the responsibility can be clarified through the tamper-proof data record.

[0091] It is understandable that if the evidence storage fails, the vehicle authorization information and authorized user information cannot be obtained. If the vehicle is authorized to an unfamiliar user, resulting in property loss to the owner, and the responsibility cannot be determined through the stored vehicle authorization information and authorized user information, the trust crisis between the owner and the automobile company will be exacerbated. Therefore, even if the authorization operation successfully associates the vehicle information and the authorized user information in S102, and the vehicle authorization information is successfully associated with the authorized user information in S103, if the evidence storage fails, the authorization failure still needs to be confirmed for security reasons.

[0092] In some optional implementations, the operations of storing the binding information in a preset cloud database and / or uploading the binding information to the consortium chain for on-chain evidence storage specifically include:

[0093] The binding information is stored in the preset cloud database. If the storage is successful, the binding information is uploaded to the alliance chain for on-chain evidence.

[0094] After the car company’s cloud database stores the data, it uploads it to the alliance chain. This design not only takes advantage of the cloud database’s efficient storage and processing capabilities, but also ensures the credibility of the data through the alliance chain’s immutability and traceability. This mechanism not only ensures data security, but also solves the limitations of the traditional single storage method.

[0095] The vehicle authorization method provided in the embodiment of the present application, the operations from S101 to S103, realize the automation and standardization of the vehicle authorization process through the application of smart contracts. Through the preset smart contracts, each link of the authorization process can be automatically executed according to the established rules, reducing the possibility of manual intervention and errors.

[0096] The vehicle authorization method provided in the embodiment of the present application can be applied to the vehicle owner user to authorize the vehicle bound to the vehicle owner user to be used by the authorized user. The specific operation is as follows: Figure 2 As shown, Figure 2 This is a flow chart of vehicle authorization between a car owner and a car company in an embodiment of the present application.

[0097] like Figure 2As shown in the figure, at the beginning, the car owner completes all steps of vehicle authorization, the car owner selects the vehicle to be authorized and the authorized user, and confirms the authorization operation. The authorization-related information is submitted to the car cloud, and the car cloud checks the data integrity, correctness, and legality, and makes a permission judgment. If the permission judgment fails, the car owner is fed back that the authorization failed, and the process ends. If the permission judgment passes, the car cloud performs the authorization operation. If the authorization fails, the car owner is fed back that the authorization failed, and the process ends. If the authorization is successful, the car cloud simultaneously performs database evidence and alliance chain evidence, and requires both to be successfully stored. The content of the evidence includes the authorization information entered by the car owner, and before authorization, the car owner is guided to read the vehicle authorization-related agreement, and perform face recognition verification to obtain the car owner's face image. If the evidence is unsuccessful, the car owner is fed back that the authorization failed, and the process ends. If the evidence is successful, the car owner is fed back that the authorization is successful, and the process ends.

[0098] like Figure 3 As shown, Figure 3 This is a flowchart of the automobile cloud performing database evidence and alliance chain evidence at the same time in the embodiment of the present application. At the beginning, the automobile cloud database performs evidence. If the cloud database evidence is unsuccessful, it is determined that the evidence failed and the process ends. If the cloud database evidence is successful, the alliance chain is uploaded. If the alliance chain is not successfully uploaded, the chain is cyclically uploaded until the number of failures is greater than 30 times, the automobile cloud database is rolled back, and the evidence is determined to have failed, and the process ends. If the alliance chain is successfully uploaded, the evidence is confirmed to be successful and the process ends.

[0099] The vehicle authorization method provided in the embodiment of the present application is applied to the vehicle owner to perform vehicle authorization, and has the following beneficial effects:

[0100] 1 Solve the trust problem: By introducing face recognition verification and dual evidence storage mechanism, the present invention effectively solves the trust problem in vehicle authorization. Whether it is caused by the owner's misoperation or the car company's program loopholes, the responsibility can be clarified through the tamper-proof data records.

[0101] 2. Improved security: The introduction of facial recognition verification further improves the security of the authorization process. Only car owners who have passed facial recognition verification can perform authorization operations, thus preventing risks such as identity fraud.

[0102] 3. Improve efficiency: The application of smart contracts realizes the automation and standardization of the vehicle authorization process. Through the preset smart contracts, each link of the authorization process can be automatically executed according to the established rules, reducing the possibility of manual intervention and errors.

[0103] The vehicle authorization method provided in the embodiment of the present application can also be applied to a non-owner user authorizing a vehicle that is not bound to the owner user to an authorized user for use. The operation process is consistent with the above-mentioned operation of the owner user authorizing the vehicle, and will not be repeated here. The non-owner user can be a person recognized or not recognized by the owner user. If the non-owner user is a person not recognized by the owner user, the image of the non-owner user is associated with the authorization information entered by the non-owner user for evidence storage. If the owner suffers property loss, the identity of the non-owner user can be queried through the stored information to facilitate the division of responsibilities.

[0104] With basically the same inventive concept, the present application also provides a vehicle authorization device, such as Figure 4 As shown, Figure 4 The vehicle authorization device wireframe in the embodiment of the present application Figure 1 The vehicle authorization device 400 comprises:

[0105] The information receiving unit 401 is used to receive vehicle authorization information and authorized user information. The vehicle authorization information includes: vehicle owner information, vehicle information and authorized user information. The authorized user information includes: authorized user's facial information.

[0106] Authorized users refer to users who authorize vehicles on mobile clients. Vehicle owner information includes the owner's mobile phone number, ID number, account number, facial information, fingerprint information, and other information related to the owner. Vehicle information includes the vehicle frame number of the vehicle authorized for use by others, or other information related to the vehicle. Authorized user information includes the authorized user's mobile phone number, ID number, account number, or facial information, fingerprint information, and other information related to the authorized user.

[0107] The authorization unit 402 is used to perform authorization operations according to the vehicle information and the authorized user information.

[0108] Exemplarily, the cloud platform of the automobile company performs authorization operations according to the vehicle authorization information, and the specific authorization operations include: associating the vehicle information with the authorized user information.

[0109] The association and evidence storage unit 403 is used to associate and store the vehicle authorization information with the authorized user information if the authorization operation is successful.

[0110] After the vehicle authorization operation, the authorized user's information, such as facial information, is associated and stored with the vehicle authorization information. If the owner makes an operational error, such as entering incorrect authorization information, resulting in the vehicle not being authorized to the authorized user recognized by the owner, or the vehicle being authorized to a stranger who is not recognized by the owner, resulting in property loss, based on the stored vehicle authorization information and the facial information associated with it, it can also be clearly seen that the result was caused by the owner's negligence or misoperation, thereby avoiding the owner's misunderstanding of the automobile company and to a certain extent avoiding a crisis of trust.

[0111] In some optional embodiments, such as Figure 5 As shown, Figure 5 The vehicle authorization device wireframe in the embodiment of the present application Figure 2 The vehicle authorization device 400 further includes:

[0112] The verification unit 501 is used to verify whether the vehicle authorization information meets the preset requirements. If not, a message indicating that the authorization failed is sent to the authorized user. The preset requirements include at least one of the following requirements:

[0113] The content and format of the owner information, vehicle information or authorized user information are correct;

[0114] The owner information and the vehicle information are associated;

[0115] The vehicle owner information and the authorized user information are associated.

[0116] After the authorized user inputs the vehicle authorization information and authorized user information through the client, the inspection unit 501 of the server of the automobile cloud platform checks the integrity, correctness and legality of the data to make an authority determination to prevent other users from impersonating the vehicle owner and authorizing the vehicle to a person the vehicle owner does not recognize, to prevent the authorized user from entering incorrect vehicle authorization information, the number of authorized users exceeding the limit, the authorized user authorizing the vehicle to a person the vehicle owner does not recognize, and other problems, thereby improving the security of the authorization operation.

[0117] In some optional implementations, the authorization unit 402 is further configured to send an authorization failure message to the authorized user if the authorization operation fails.

[0118] In some optional embodiments, such as Figure 6 As shown, Figure 6 This is a wireframe diagram of the association and evidence storage unit in the embodiment of the present application. The association and evidence storage unit 403 includes:

[0119] The association unit 601 is used to bind the vehicle authorization information and the authorized user information to obtain binding information.

[0120] The evidence storage unit 602 is used to store the binding information in a preset cloud database, and / or upload the binding information to the alliance chain for on-chain evidence storage.

[0121] In some optional embodiments, the evidence storage unit 602 is also used to upload the binding information to the alliance chain for on-chain evidence storage again if the operation of uploading the binding information to the alliance chain for on-chain evidence storage fails, until the number of failures reaches a preset upper limit of failures, then it is determined that the evidence storage has failed, and / or if the operation of storing the binding information in a preset cloud database fails, then it is determined that the evidence storage has failed.

[0122] In some optional implementations, the evidence storage unit 602 is further configured to send an authorization failure message to the authorized user if it is determined that the evidence storage has failed.

[0123] If the evidence storage fails, the vehicle authorization information and authorized user information cannot be obtained. If the vehicle is authorized to an unfamiliar user, resulting in property loss to the owner, and the responsibility cannot be determined through the stored vehicle authorization information and authorized user information, the trust crisis between the owner and the automobile company will be exacerbated. Therefore, if the evidence storage fails, the authorization failure still needs to be confirmed for safety reasons.

[0124] In some optional embodiments, Figure 6 As shown, the evidence storage unit 602 includes:

[0125] The cloud storage unit 6021 is used to store the binding information in a preset cloud database;

[0126] The on-chain unit 6022 is used to upload the binding information to the alliance chain for on-chain storage.

[0127] It is understandable that after the car company's cloud database is used for evidence storage, the data is uploaded to the alliance chain. This design not only utilizes the efficient storage and processing capabilities of the cloud database, but also ensures the credibility of the data through the immutability and traceability of the alliance chain. This mechanism not only ensures data security, but also solves the limitations of the traditional single evidence storage method.

[0128] The vehicle authorization device 400 provided in the embodiment of the present application associates and stores the vehicle authorization information with the authorized user information when the vehicle is authorized. The authorized user information is used to clarify the identity of the authorized operator. After the authorization operation is completed, the stored vehicle authorization information and authorized user information can be used by the vehicle owner or the automobile company to clarify the identity of the authorized operator, thereby ensuring the authenticity of the vehicle authorization information and improving the security and credibility of the data.

[0129] Based on the same inventive concept, the present application also provides an electronic device. Figure 7 As shown, Figure 7The electronic device 700 provided in the embodiment of the present application is used to receive the vehicle authorization information input by the authorized user 701, collect the authorized user information, and send the vehicle authorization information and the authorized user information to the vehicle authorization device 400; the vehicle authorization information includes: the owner information, the vehicle information and the authorized user information, and the authorized user information includes: the facial information of the authorized user 701; and is also used to receive the authorization success or authorization failure information sent by the vehicle authorization device 400.

[0130] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a computer, the computer executes the method provided in the above embodiment.

[0131] The present application also provides a server, such as Figure 7 As shown, the server 700 includes a memory 701, a processor 702, and a computer program 703 stored in the memory 701 and executable on the processor 702. When the processor 702 executes the computer program 703, the server 700 executes the method provided in the above embodiment.

[0132] The embodiments of the present application also provide a computer program product, including a computer program. When the computer program is executed, the computer executes the method provided in the above embodiments.

[0133] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0134] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

[0135] In the description provided herein, a large number of specific details are described. However, it is understood that the embodiments of the present application can be practiced without these specific details. In some instances, well-known methods, structures and techniques are not shown in detail so as not to obscure the understanding of this description.

Claims

1. A vehicle authorization method, characterized in that: include: Receiving vehicle authorization information and authorized user information, wherein the vehicle authorization information includes: vehicle owner information, vehicle information and authorized user information, and the authorized user information includes: facial information of the authorized user; Performing authorization operation according to the vehicle information and the authorized user information; If the authorization operation is successful, the vehicle authorization information is associated with the authorized user information and stored.

2. The vehicle authorization method according to claim 1, characterized in that: The associating and storing the vehicle authorization information with the authorized user information includes: Binding the vehicle authorization information and the authorized user information to obtain binding information; The binding information is stored in a preset cloud database, and / or the binding information is uploaded to the alliance chain for on-chain evidence storage.

3. The vehicle authorization method according to claim 2, characterized in that: If the operation of uploading the binding information to the alliance chain for on-chain evidence storage fails, the binding information is uploaded to the alliance chain again for on-chain evidence storage until the number of failures reaches the preset upper limit of the number of failures, and then it is determined that the evidence storage has failed.

4. The vehicle authorization method according to claim 2, characterized in that: If the operation of storing the binding information in the preset cloud database fails, it is determined that the evidence storage has failed.

5. The vehicle authorization method according to claim 3 or 4, characterized in that: If it is determined that the evidence storage fails, a message indicating the authorization failure is sent to the authorized user.

6. The vehicle authorization method according to claim 1, characterized in that: Before performing the authorization operation according to the vehicle information and the authorized user information, the method further includes: Check whether the vehicle authorization information meets the preset requirements. If not, send authorization failure information to the authorized user; the preset requirements include at least one of the following requirements: The content and format of the vehicle owner information, the vehicle information or the authorized user are correct; The vehicle owner information and the vehicle information are associated with each other; The vehicle owner information and the authorized user information are associated with each other.

7. The vehicle authorization method according to claim 1, characterized in that: The authorization operation specifically includes: The vehicle information is associated with the authorized user information.

8. The vehicle authorization method according to claim 1 or 7, characterized in that: If the authorization operation fails, an authorization failure message is sent to the authorized user.

9. A vehicle authorization device, comprising: An information receiving unit, used to receive vehicle authorization information and authorized user information, wherein the vehicle authorization information includes: vehicle owner information, vehicle information and authorized user information, and the authorized user information includes: facial information of the authorized user; An authorization unit, used to perform authorization operations according to the vehicle information and the authorized user information; The association and evidence storage unit is used to associate and store the vehicle authorization information with the authorized user information if the authorization operation is successful.

10. An electronic device, characterized in that: Used to receive vehicle authorization information input by an authorized user, collect authorized user information, and send the vehicle authorization information and the authorized user information to a vehicle authorization device; The vehicle authorization information includes: vehicle owner information, vehicle information and authorized user information, and the authorized user information includes: facial information of the authorized user; Receive authorization success or authorization failure information sent by the vehicle authorization device.

Images