Vehicle authorization method, apparatus, and electronic device

Abstract

The application discloses a vehicle authorization method and device and electronic equipment. Vehicle authorization information is associated with authorization user information and stored as evidence when the vehicle is authorized. The authorization user information is used to explicitly identify the identity of an authorization operator. After the authorization operation is completed, the stored vehicle authorization information and authorization user information can be used to explicitly identify the identity of the authorization operator by the vehicle owner or the automobile company, ensure the authenticity of the vehicle authorization information, and improve the security and reliability of the data.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of software development, in particular to a vehicle authorization method and device and electronic equipment, relates to vehicle authorization technology and alliance chain technology, and can effectively solve the trust problem in vehicle authorization and facilitate the solution of after-sales problems. BACKGROUND

[0002] With the popularization of intelligent vehicles, vehicle authorization has become an important function. In the current market, the owner of an intelligent vehicle can authorize the vehicle, and the authorized user can control the vehicle through authorization.

[0003] In the prior art, the owner performs authorization operations through a mobile phone client. This operation is simple, but the owner's identity can be used by others, and the vehicle can be authorized to people who are not approved by the owner in violation of the owner's will, resulting in poor security and causing a trust crisis between the owner and the car company. SUMMARY

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

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

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

[0007] Receiving vehicle authorization information and authorized user information, the vehicle authorization information including owner information, vehicle information and authorized user information, and the authorized user information including the face information of the authorized user;

[0008] Performing an authorization operation according to the vehicle information and the authorized user information;

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

[0010] Optionally, associating and storing the vehicle authorization information and the authorized user information comprises:

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

[0012] Storing the binding information in a predetermined cloud database, and / or uploading the binding information to an alliance chain for on-chain storage.

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

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

[0015] Optionally, if it is determined that the storage fails, the authorized user is sent information of authorization failure.

[0016] Optionally, before the authorization operation according to the vehicle information and the authorized user information, it further comprises:

[0017] checking whether the vehicle authorization information meets the preset requirements, and if not, sending the authorized user information of authorization failure; 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 are correct;

[0019] The owner information and the vehicle information have an association relationship;

[0020] The owner information and the authorized user information have an association relationship.

[0021] Optionally, the authorization operation specifically comprises:

[0022] associating the vehicle information and the authorized user information.

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

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

[0025] An information receiving unit is configured to receive vehicle authorization information and authorized user information, wherein the vehicle authorization information includes owner information, vehicle information and authorized user information, and the authorized user information includes face information of the authorized user.

[0026] An authorization unit is configured to perform an authorization operation according to the vehicle information and the authorized user information.

[0027] An association and storage unit is configured to associate and store the vehicle authorization information and the authorized user information if the authorization operation is successful.

[0028] In a third aspect, an electronic device is provided for receiving vehicle authorization information input by an authorized user, collecting authorized user information, and sending the vehicle authorization information and the authorized user information to a vehicle authorization device; the vehicle authorization information includes owner information, vehicle information, and authorized user information, and the authorized user information includes facial information of the authorized user.

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

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

[0031] In a fifth aspect, the application further provides a computer readable storage medium, which stores a computer program, and 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 application further provides a computer program product, which includes a computer program, and when the computer program is executed by a computer, the computer executes the method provided in the first aspect.

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

[0034] The vehicle authorization method, device and electronic device provided by the application associate and store the vehicle authorization information and the authorized user information when the vehicle is authorized, the authorized user information is used to determine the identity of the authorized operator, and after the authorization operation is completed, the stored vehicle authorization information and authorized user information can be used by the owner or the car company to determine 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 a summary of the technical scheme of the application, in order to more clearly understand the technical means of the application, the application can be implemented according to the content of the specification, and in order to make the above and other purposes, characteristics and advantages of the application more obvious and easy to understand, the following specific embodiments of the application are described. BRIEF DESCRIPTION OF DRAWINGS

[0036] Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The accompanying drawings are included to provide a description of the preferred embodiments and are not meant to limit the present application. Moreover, the same reference numerals in the attached drawings refer to the same or like components throughout the several drawings. In the drawings:

[0037] Figure 1A vehicle authorization method flowchart in the embodiment of the present application;

[0038] Figure 2 A vehicle authorization flowchart between a vehicle owner user and an automobile company in the embodiment of the present application;

[0039] Figure 3 A flowchart of the automobile cloud simultaneously performing database storage and alliance chain storage in the embodiment of the present application;

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

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

[0042] Figure 6 A wireframe diagram of the association and storage unit in the embodiment of the present application;

[0043] Figure 7 A server schematic diagram in the embodiment of the present application. DETAILED DESCRIPTION

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

[0045] Various structural schematic diagrams according to the embodiments of the present application are shown in the accompanying drawings. These diagrams are not drawn to scale, in which certain details are exaggerated for the purpose of clarity and certain details can be omitted. The shapes of various regions, layers shown in the drawings, and their relative sizes and positional relationships can deviate in actuality due to manufacturing tolerances or technical limitations, and regions / layers with different shapes, sizes, relative positions can be additionally designed by those skilled in the art according to actual needs.

[0046] In order to better understand the above technical solutions, the above technical solutions will be described in detail below in combination with specific embodiments, it should be understood that the embodiments of the present disclosure and the specific features in the embodiments are detailed descriptions of the technical solutions of the present application, and not limitations of the technical solutions of the present application, and the technical features in the embodiments of the present application and the embodiments can be combined with each other without conflict.

[0047] With the popularity of intelligent vehicles, vehicle authorization has become an important function. In the current market, the owner of an intelligent vehicle selects the vehicle to be authorized and the authorized user on the client side, and performs the authorization operation, and 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 problem is particularly prominent.

[0048] The authorization record is stored in the cloud platform of the automobile company, which realizes the basic vehicle authorization function, but exposes many problems in actual application.

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

[0050] Risk of owner misoperation: the owner may authorize the vehicle to a stranger due to negligence or misoperation during operation, resulting in property loss. At this time, the owner may question the data record provided by the automobile company, claiming that the automobile company has tampered with the data, thereby causing a crisis of trust.

[0051] Automobile company program vulnerability or misoperation: the automobile company cloud platform may have program vulnerabilities or misoperations, resulting in the vehicle being incorrectly authorized to a stranger. At this time, the automobile company may deny the problem and tamper with the database to evade responsibility, further exacerbating the trust problem.

[0052] Therefore, the present application provides a vehicle authorization method, please refer to Figure 1 , Figure 1 The vehicle authorization method includes the following steps:

[0053] S101, receive vehicle authorization information and authorized user information, the vehicle authorization information includes: owner information, vehicle information and authorized user information, the authorized user information includes: the face information of the authorized user.

[0054] The authorized user refers to the user who performs the vehicle authorization operation on the mobile phone client, the owner information includes the owner's mobile phone number, the owner's ID number, the owner's account number, the owner's face information, the owner's fingerprint information, and other information related to the owner. The vehicle information includes the vehicle frame number of the vehicle authorized to others, or other information related to the vehicle. The authorized user information includes the authorized user's mobile phone number, the authorized user's ID number, the authorized user's account number, or the authorized user's face information, fingerprint information, and other information related to the authorized user.

[0055] It can be understood that when the authorized user is the owner himself, the owner information and the vehicle information have a correlation.

[0056] S102, according to the vehicle information and the authorized user information, perform the authorization operation.

[0057] Generally, the authorization operation is performed by the cloud platform of the automobile company, and after the authorized user inputs the vehicle authorization information and the authorized user information through the client and submits, the cloud platform of the automobile company performs the authorization operation according to the vehicle authorization information. The specific authorization operation includes: associating the vehicle information and 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, associating and storing the vehicle authorization information with the authorized user information.

[0059] The authorized user can be the owner of the authorized vehicle, can be a person known to the owner, or can be a person unknown to the owner. When the authorized user is not the owner, the authorized user information has no association with the vehicle information. After the vehicle authorization operation, the information of the authorized user, such as the face information, is associated with and stored with the vehicle authorization information. If the owner makes a mistake, such as inputting incorrect authorization information, resulting in the vehicle being authorized to an authorized user approved by the owner, or the vehicle being authorized to a stranger not approved by the owner, causing property loss, the stored vehicle authorization information and the associated face information can also clearly indicate that the result is caused by the owner's negligence or mistake, thereby avoiding the owner's misunderstanding of the car company and to some extent avoiding the trust crisis.

[0060] In another case, if the owner's identity is used, the stored vehicle authorization information and the associated face information can help the owner find out who the authorized person is. If the authorized person is not the person approved by the owner, the police can determine the person who used the owner's identity based on the face information, thereby improving the security and reliability of the authorization process.

[0061] It can be understood that the authorized user can also be further limited to the owner. The owner's mobile phone number, portrait, ID number, and other information can be pre-stored in the database and bound to the vehicle license plate number. After receiving the vehicle authorization information and the authorized user information, the owner information in the vehicle authorization information is compared with the authorized user information, such as comparing the face information of the authorized user with the pre-stored portrait information of the owner. If the authorized user is determined to be the owner based on the comparison result, the authorization operation can be performed. This can further improve the security of vehicle authorization and prevent the owner's identity from being used to authorize the vehicle to others, causing property loss to the owner.

[0062] In some optional embodiments, before the authorization operation is performed based on the vehicle information and the authorized user information, the method further comprises:

[0063] verifying whether the vehicle authorization information meets the preset requirements, and if not, sending 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 are correct;

[0065] The owner information and the vehicle information have an association;

[0066] The owner information and the authorized user information have a correlation.

[0067] Exemplarily, after the authorized user inputs the vehicle authorization information and the authorized user information through the client, the server of the automobile cloud platform receives the information, checks the integrity, correctness and legality of the data to make the permission determination, avoids other users from impersonating the owner to authorize the vehicle to people not approved by the owner, avoids the authorized user from inputting incorrect vehicle authorization information, the number of authorized users exceeding the number limit, the authorized user authorizing the vehicle to people not approved by the owner, and the like, and improves the security of the authorization operation.

[0068] Exemplarily, the preset requirement can be set as that the owner information and the authorized user information have a correlation and the owner information and the vehicle information have a correlation, i.e., the owner and the authorized user must be the same person, and the mobile phone number of the owner and the vehicle frame number are bound. When the authorized user inputs the vehicle authorization information into the mobile phone client, the face recognition module installed through the mobile phone client collects the face information of the authorized user, compares the face information of the authorized user with the pre-stored face information of the owner, and executes the authorization operation after determining that the authorized user is the owner himself.

[0069] The introduction of the face recognition verification further improves the security of the authorization process. Only the owner user who passes the face recognition verification can perform the authorization operation, thereby preventing the risk of identity impersonation.

[0070] In some optional embodiments, it is verified whether the vehicle authorization information meets the preset requirement. If yes, the authorized user is sent the information of passing the verification, so as to facilitate the authorized user to understand the current progress.

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

[0072] The authorization operation of the automobile cloud platform usually associates the vehicle information and 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 authorized user is fed back the result of the authorization operation failure, so as to enable the authorized user to understand the situation and submit the vehicle authorization information again.

[0073] The reasons for the authorization failure in the operation include, but are not limited to, the server exception of the automobile cloud platform, the function of the automobile cloud platform being limited, and the like.

[0074] In some optional embodiments, if the authorization operation succeeds, the authorized user is sent a message of the authorization operation success.

[0075] It can be understood that the authorization operation is successful, and the authorization is successful. The message of the success of the authorization operation is sent to the authorized user to show the progress of the operation of S102. In S103, if the vehicle authorization information is associated with the authorized user information and the storage is successful, the message of the authorization function is sent to the authorized user. At this point, the vehicle authorization is completed.

[0076] In some optional embodiments, the association and storage of the vehicle authorization information and the authorized user information include:

[0077] The vehicle authorization information and the authorized user information are bound to obtain binding information.

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

[0079] Although the automobile company cloud platform can be supervised by a corresponding regulatory agency, and all operations can be backed up. However, this solution requires high cost, and there is currently no such specialized regulatory agency. In contrast, the operation of associating and storing the vehicle authorization information and the authorized user information provided in the embodiments of the present application has more advantages in 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 consensus mechanism to generate and update data, and uses smart contracts to achieve automation. Its decentralized, tamper-proof and traceable features solve the problem of absolute rights in traditional system database operations, making it a decentralized self-regulating system that does not rely on third parties and is governed by multiple parties.

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

[0082] Once the consortium chain is on the chain, no modification operation can be performed, which also ensures that the final data is tamper-proof and absolutely reliable, and can avoid the problem of the automobile company tampering with the vehicle authorization information to avoid responsibility when the vehicle is mistakenly authorized to a stranger due to possible program vulnerabilities or errors in the automobile company's cloud platform. Thus, the trust problem between the automobile company and the vehicle owner is further avoided.

[0083] The vehicle authorization information is associated with the authorized user information and is stored on the alliance chain, so that the uniqueness and authenticity of the vehicle authorization operation are ensured, and the security and credibility of the data are improved.

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

[0085] It can be understood that the design of the alliance chain and the design of the blockchain browser provided to the outside can form a corresponding patent, for example, the blockchain browser needs to provide a user with the authorization information of the vehicle, but the privacy of other users needs to be protected.

[0086] During the on-chain process of the alliance chain, the operation may fail due to contract compilation failure, transaction encapsulation failure, fee acquisition failure, server exception, etc., and if repeated on-chain operation still fails, it is determined that the storage fails, and the authorized user is sent information of authorization failure.

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

[0088] The binding information is stored in the preset cloud database, which can facilitate the authorized user to view at any time, and during the process of storing the binding information in the preset cloud database, the operation may fail due to server exception, etc., and if it is determined that the storage fails, the authorized user is sent information of authorization failure.

[0089] The cloud database and the alliance chain double storage, first perform automobile cloud database storage, and then perform on-chain storage of the alliance chain, because the cloud database can be rolled back, the alliance chain cannot be modified once on-chain, which also ensures that the authorized user or the vehicle owner can view the authorization information at any time, and ensures that the data of the authorization information is tamper-proof and absolutely credible.

[0090] Through the face recognition verification and the double storage mechanism, the vehicle authorization method provided by the embodiment of the application effectively solves the trust problem in vehicle authorization. Whether the problem is caused by the vehicle owner's misoperation or the program vulnerability of the automobile company, the responsibility can be clearly defined through the tamper-proof data record.

[0091] It can be understood that if the storage fails, the vehicle authorization information and the authorized user information cannot be obtained, and if the vehicle is authorized to a stranger, causing the owner's property loss, the responsibility cannot be determined through the vehicle authorization information and the authorized user information, which will exacerbate the trust crisis between the owner and the car company. Therefore, even if the vehicle information and the authorized user information are associated in the authorization operation of S102, and the vehicle authorization information and the authorized user information are successfully associated in S103, if the storage fails, the authorization failure still needs to be confirmed based on security considerations.

[0092] In some optional embodiments, the operation of storing the binding information in the preset cloud database and / or uploading the binding information to the alliance chain for on-chain storage specifically includes:

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

[0094] After the data is stored in the cloud database of the car company, the data is uploaded to the alliance chain. This design not only utilizes the efficient storage and processing capability of the cloud database, but also guarantees the credibility of the data through the non-tamperability and traceability of the alliance chain. This mechanism ensures data security while solving the limitations of traditional single storage methods.

[0095] The vehicle authorization method provided by the embodiments of the present application, S101 to S103, realizes the automation and standardization of the vehicle authorization process through the application of the smart contract. Through the preset smart contract, each link of the authorization process can be automatically executed according to the predetermined rules, reducing the possibility of manual intervention and errors.

[0096] The vehicle authorization method provided by the embodiments of the present application can be applied to the authorization of a vehicle bound to an owner user to an authorized user, and the specific operation is as shown in Figure 2 Figure 2 The vehicle authorization process diagram between the owner user and the car company in the embodiments of the present application.

[0097] As Figure 2 ​As shown, at the beginning, the vehicle owner user completes all the steps of vehicle authorization, 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, the car cloud checks the data integrity, correctness and legality, makes the permission judgment, if the permission judgment does not pass, the vehicle owner user is fed back the authorization failure, and the process ends. If the permission judgment passes, the car cloud performs the authorization operation. If the authorization is not successful, the vehicle owner user is fed back the authorization failure, and the process ends. If the authorization is successful, the car cloud simultaneously performs database storage and alliance chain storage, and requires both to be successfully stored. The contents of storage include the authorization information input by the vehicle owner user, and before authorization, the vehicle owner user is guided to read the vehicle authorization related agreement, and the face recognition verification is performed, and the face image of the vehicle owner user is obtained. If the storage is not successful, the vehicle owner user is fed back the authorization failure, and the process ends. If the storage is successful, the vehicle owner user is fed back the authorization success, and the process ends.

[0098] As shown, Figure 3 Figure 3 The flow chart of simultaneously performing database storage and alliance chain storage by the car cloud in the embodiment of the application is shown in the figure. At the beginning, the car cloud database performs storage. If the cloud database storage is not successful, it is determined that the storage fails, and the process ends. If the cloud database storage is successful, the alliance chain performs the chain. If the alliance chain chain is not successful, the chain is recycled until the number of failures is greater than 30, the car cloud database performs rollback, determines that the storage fails, and ends the process. If the alliance chain chain is successful, it is determined that the storage is successful, and the process ends.

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

[0100] 1. Solve the trust problem: by introducing face recognition verification and double storage mechanism, the application effectively solves the trust problem in vehicle authorization. Whether it is a vehicle owner misoperation or a problem caused by a program bug of a car company, the responsibility can be clearly defined through the tamper-proof data record.

[0101] 2. Improve safety: the introduction of face recognition verification further improves the safety of the authorization process. Only the vehicle owner user who has passed the face recognition verification can perform the authorization operation, thereby preventing risks such as identity fraud.

[0102] 3. Improve efficiency: the application of smart contract realizes the automation and standardization of the vehicle authorization process. Through the pre-set smart contract, 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 by the embodiments of the present application can also be applied to authorization of a vehicle that is not bound to a vehicle owner to a user authorized by a non-vehicle owner. The operation process is consistent with the operation of authorization of a vehicle by a vehicle owner, which is not repeated here. The non-vehicle owner can be a person recognized or not recognized by the vehicle owner. If the non-vehicle owner is a person not recognized by the vehicle owner, the image of the non-vehicle owner is associated with the authorization information input by the non-vehicle owner and stored as evidence. If the vehicle owner suffers property loss, the identity of the non-vehicle owner can be queried through the stored information, which facilitates responsibility division.

[0104] Based on the same inventive concept, the embodiments of the present application also provide a vehicle authorization device. Figure 4 As shown in the figure, Figure 4 The vehicle authorization device in the embodiments of the present application is a wireframe Figure 1 The vehicle authorization device 400 comprises:

[0105] An information receiving unit 401 is configured to receive vehicle authorization information and authorized user information. The vehicle authorization information comprises vehicle owner information, vehicle information and authorized user information. The authorized user information comprises facial information of the authorized user.

[0106] The authorized user refers to a user who performs a vehicle authorization operation on a mobile phone client. The vehicle owner information comprises a mobile phone number of the vehicle owner, an ID number of the vehicle owner, an account number of the vehicle owner, facial information of the vehicle owner, fingerprint information of the vehicle owner and other information related to the vehicle owner. The vehicle information comprises a vehicle frame number of a vehicle authorized to be used by others or other information related to the vehicle. The authorized user information comprises a mobile phone number of the authorized user, an ID number of the authorized user, an account number of the authorized user, facial information of the authorized user, fingerprint information of the authorized user and other information related to the authorized user.

[0107] An authorization unit 402 is configured to perform an authorization operation according to the vehicle information and the authorized user information.

[0108] For example, a cloud platform of an automobile company performs an authorization operation according to the vehicle authorization information. The specific authorization operation comprises associating the vehicle information and the authorized user information.

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

[0110] After the vehicle authorization operation, the information of the authorized user, such as the face information, is associated with and stored with the vehicle authorization information. If the vehicle owner makes a mistake, such as inputting incorrect authorization information, the vehicle is not authorized to the authorized user recognized by the vehicle owner, or the vehicle is authorized to a stranger not recognized by the vehicle owner, resulting in property loss. According to the stored vehicle authorization information and the face information associated therewith, it can be determined that the result is caused by the owner's negligence or mistake, thereby avoiding the owner's misunderstanding of the car company and avoiding the trust crisis to some extent.

[0111] In some optional embodiments, as shown in Figure 5 Figure 5 The vehicle authorization device line frame in the embodiments of the present application is as shown in Figure 2 The vehicle authorization device 400 further comprises:

[0112] The inspection unit 501 is configured to inspect whether the vehicle authorization information meets preset requirements, and send an authorization failure message to the authorized user if the vehicle authorization information does not meet the preset requirements. The preset requirements include at least one of the following requirements:

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

[0114] The vehicle owner information and the vehicle information have an association relationship;

[0115] The vehicle owner information and the authorized user information have an association relationship.

[0116] After the authorized user inputs the vehicle authorization information and the authorized user information through the client, the inspection unit 501 of the server of the automobile cloud platform checks the completeness, correctness, and legality of the data to make an authority determination, so as to avoid other users from using the vehicle owner's identity to authorize the vehicle to a person not recognized by the vehicle owner, avoid the authorized user from inputting incorrect vehicle authorization information, the number of authorized users exceeding the number limit, the authorized user authorizing the vehicle to a person not recognized by the vehicle owner, and the like, and improve the security of the authorization operation.

[0117] In some optional embodiments, 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, as shown in Figure 6 Figure 6 The association and storage unit line frame in the embodiments of the present application is as shown in

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

[0120] ​​The storage unit 602 is configured to store the binding information in a preset cloud database and / or upload the binding information to a consortium chain for on-chain storage.

[0121] In some optional embodiments, the storage unit 602 is further configured to, if the operation of uploading the binding information to the consortium chain for on-chain storage fails, re-upload the binding information to the consortium chain for on-chain storage until the number of failures reaches a preset upper limit of the number of failures, and determine that the storage fails, and / or if the operation of storing the binding information in the preset cloud database fails, determine that the storage fails.

[0122] In some optional embodiments, the storage unit 602 is further configured to, if it is determined that the storage fails, send a message of authorization failure to the authorized user.

[0123] If the storage fails, the vehicle authorization information and the authorized user information cannot be obtained, and if the vehicle is authorized to a stranger, resulting in a problem of property loss of the vehicle owner, the responsibility cannot be determined through the stored vehicle authorization information and authorized user information, which will exacerbate the trust crisis between the vehicle owner and the automobile company. Therefore, if the storage fails, the authorization failure still needs to be confirmed based on security considerations.

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

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

[0126] The on-chain unit 6022 is configured to upload the binding information to a consortium chain for on-chain storage.

[0127] It can be understood that after the storage in the cloud database of the automobile company, the data is uploaded to the consortium chain. This design not only utilizes the high storage and processing capacity of the cloud database, but also guarantees the credibility of the data through the non-tamperability and traceability of the consortium chain. This mechanism ensures data security while solving the limitations of traditional single storage methods.

[0128] The vehicle authorization device 400 provided by the embodiments of the present application associates and stores the vehicle authorization information and the authorized user information during vehicle authorization, and the authorized user information is used to explicitly identify the identity of the authorization 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 explicitly identify the identity of the authorization operator, guarantee the authenticity of the vehicle authorization information, and improve the security and credibility of the data.

[0129] Based on the same inventive concept, the embodiments of the present application also provide an electronic device. As shown in Figure 7 Figure 7 ​The electronic device line frame diagram in the embodiments of the present application is shown in the figure. The electronic device 700 provided by the embodiments of the present application is configured to receive vehicle authorization information input by an authorized user 701, collect 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 owner information, vehicle information and authorized user information, and the authorized user information includes face information of the authorized user 701. The electronic device 700 is also configured to receive information of authorization success or authorization failure sent by the vehicle authorization device 400.

[0130] The embodiments of the present application also provide a computer readable storage medium, which stores a computer program. When the computer program is executed by a computer, the computer program causes the computer to execute the method provided by the above embodiments.

[0131] The embodiments of the present application also provide a server, as shown in the figure. 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 by the above embodiments. Figure 7

[0132] The embodiments of the present application also provide a computer program product, which includes a computer program. When the computer program is executed, the computer program causes a computer to execute the method provided by the above embodiments.

[0133] Those skilled in the art can understand that all or part of the steps of the above-mentioned method embodiments can be completed by program instruction related hardware. The foregoing 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 foregoing storage medium includes ROM, RAM, magnetic disk or optical disk and various storage 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, and not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacement for part or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

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

Claims

1. A vehicle authorization method, characterized in that, include: 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: the facial information of the authorized user. Based on the vehicle information and the authorized user information, the authorization operation is performed; If the authorization operation is successful, the vehicle authorization information is associated with and stored as evidence of the authorized user information; wherein, associating and storing the vehicle authorization information with the authorized user information includes: The vehicle authorization information and the authorized user information are bound together to obtain binding information; The binding information is stored in a preset cloud database, and / or uploaded to the consortium blockchain for on-chain evidence storage.

2. The vehicle authorization method as described in claim 1, characterized in that, If the operation of uploading the binding information to the consortium blockchain for on-chain notarization fails, the binding information will be uploaded to the consortium blockchain again for on-chain notarization until the number of failures reaches the preset failure limit, at which point the notarization is determined to have failed.

3. The vehicle authorization method as described in claim 1, characterized in that, If the operation of storing the binding information in the preset cloud database fails, then the evidence storage is determined to have failed.

4. The vehicle authorization method as described in claim 2 or 3, characterized in that, If the evidence storage fails, an authorization failure message is sent to the authorized user.

5. The vehicle authorization method as described in claim 1, characterized in that, Before performing the authorization operation based on the vehicle information and the authorized user information, the process also includes: The system checks whether the vehicle authorization information meets preset requirements. If not, it sends an authorization failure message to the authorized user. The preset requirements include at least one of the following: 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 related; The vehicle owner information and the authorized user information are related.

6. The vehicle authorization method as described in claim 1, characterized in that, The authorization operation specifically includes: The vehicle information and the authorized user information are associated.

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

8. A vehicle authorization device, characterized in that, include: An information receiving unit 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: the facial information of the authorized user. The authorization unit is used to perform authorization operations based on 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; wherein, associating and storing the vehicle authorization information with the authorized user information includes: The vehicle authorization information and the authorized user information are bound together to obtain binding information; The binding information is stored in a preset cloud database, and / or uploaded to the consortium blockchain for on-chain evidence storage.

9. An electronic device, characterized in that, The method for performing the vehicle authorization method according to any one of claims 1-7 includes receiving vehicle authorization information input by an authorized user, collecting authorized user information, and sending 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, wherein the authorized user information includes: the facial information of the authorized user; Receive information from the vehicle authorization device indicating whether authorization was successful or failed.

Images