Vehicle sharing method, device, equipment, storage medium and computer program product

Abstract

The invention relates to the technical field of Internet of Vehicles, in particular to a vehicle sharing method, device and equipment, a storage medium and a computer program product. The method comprises the following steps: when a group joining request of a user is received, distributing a private key to the user; when a vehicle use request is received, generating a vehicle use signature based on the private key; sending the vehicle use signature to the to-be-used vehicle, so that the to-be-used vehicle verifies the vehicle use signature based on the group public key; if the vehicle use signature passes verification, the to-be-used vehicle is controlled to open the use permission, and the safety of the vehicle sharing process is improved.

Description

Technical Field

[0001] The present application relates to the field of vehicle networking technology, and in particular to a vehicle sharing method, device, equipment, storage medium and computer program product. Background Art

[0002] As an important part of the sharing economy, vehicle sharing provides users with efficient and economical travel options, and has significant advantages in reducing resource waste and reducing traffic pressure. However, vehicle sharing also faces many technical challenges, including user information leakage, illegal use of vehicles, and difficulty in tracing responsibility. Existing vehicle sharing methods usually rely on traditional authentication methods (such as usernames, passwords, or QR codes). These methods often require users to provide identity information or account information, which can easily lead to personal privacy leakage during shared use. In addition, authentication methods that rely on static credentials (such as passwords or fixed tokens) are easily forged or stolen, and cannot effectively prevent illegal access and use, resulting in poor security in the vehicle sharing process. Therefore, how to improve the security of the vehicle sharing process has become a technical problem that needs to be solved urgently. Summary of the invention

[0003] The main purpose of this application is to provide a vehicle sharing method, device, equipment, storage medium and computer program product, aiming to solve the technical problem of how to improve the security of the vehicle sharing process.

[0004] To achieve the above object, the present application provides a vehicle sharing method, which comprises the following steps:

[0005] When receiving a group joining request from a user, assigning a private key to the user;

[0006] When a vehicle use request is received, generating a vehicle use signature based on the private key;

[0007] Sending the vehicle use signature to the vehicle to be used, so that the vehicle to be used verifies the vehicle use signature based on the group public key;

[0008] If the vehicle usage signature passes the verification, the use authority of the vehicle to be used is controlled to be opened.

[0009] In one embodiment, before the step of allocating a user private key to the user upon receiving a group joining request from the user, the step further includes:

[0010] Based on the number of group members, determine the generation of basic elements and random security parameters;

[0011] The group public key and private key generation rules are determined according to the generation basic element and the random security parameter.

[0012] In one embodiment, when receiving a group joining request from a user, the step of allocating a private key to the user includes:

[0013] When receiving a group joining request from a user, verifying the legitimacy of the group joining request;

[0014] If the group joining request passes the verification, obtaining the user identity information in the group joining request;

[0015] Generate the private key based on the user identity information and the private key generation rule;

[0016] Based on a preset encrypted communication channel, the private key is distributed to the user.

[0017] In one embodiment, when a vehicle use request is received, the step of generating a vehicle use signature based on the private key includes:

[0018] When receiving a vehicle use request, obtaining summary information in the vehicle use request;

[0019] Assigning a random number to the private key, and encrypting the summary information based on the private key and the random number to obtain preliminary signature data;

[0020] The vehicle use signature is generated based on the preliminary signature data and the group public key.

[0021] In one embodiment, if the vehicle use signature passes the verification, the step of controlling the opening of the use permission of the vehicle to be used includes:

[0022] If the vehicle use signature passes the verification, checking the vehicle status of the vehicle to be used;

[0023] If the vehicle status is available and the hardware system works normally, the vehicle control system and the preset monitoring mechanism of the vehicle to be used are unlocked, and the access permission of the vehicle to be used is controlled.

[0024] In one embodiment, after the step of controlling the opening of the use right of the vehicle to be used if the vehicle use signature passes the verification, the method further includes:

[0025] Continuously monitoring the real-time vehicle status of the vehicle to be used, and collecting behavior data of the vehicle to be used;

[0026] Using the real-time vehicle status and the behavior data of the vehicle to be used as vehicle usage information, and uploading the vehicle usage information regularly;

[0027] When the end-of-use instruction is received, the vehicle control system is disabled and the vehicle status is updated, and the end-of-use time is recorded.

[0028] In addition, to achieve the above-mentioned purpose, the present application also proposes a vehicle sharing device, the vehicle sharing device comprising:

[0029] A private key distribution module, configured to distribute a private key to a user upon receiving a group joining request from the user;

[0030] A signature generation module, configured to generate a vehicle use signature based on the private key when a vehicle use request is received;

[0031] A signature verification module, used for sending the vehicle use signature to the vehicle to be used, so that the vehicle to be used verifies the vehicle use signature based on the group public key;

[0032] The target module is used to control the opening of the use permission of the vehicle to be used if the vehicle use signature passes the verification.

[0033] In addition, to achieve the above-mentioned purpose, the present application also proposes a vehicle sharing device, which includes: a memory, a processor, and a vehicle sharing program stored on the memory and executable on the processor, wherein the vehicle sharing program is configured to implement the steps of the vehicle sharing method described above.

[0034] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, on which a vehicle sharing program is stored, and when the vehicle sharing program is executed by a processor, the steps of the vehicle sharing method described above are implemented.

[0035] In addition, to achieve the above objectives, the present application also proposes a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the vehicle sharing method described above are implemented.

[0036] This application assigns a private key to the user upon receiving a group joining request from the user; generates a vehicle use signature based on the private key upon receiving a vehicle use request; sends the vehicle use signature to the vehicle to be used so that the vehicle to be used verifies the vehicle use signature based on the group public key; if the vehicle use signature passes the verification, controls the access rights of the vehicle to be used. This application ensures the uniqueness of the user identity by assigning a private key when the user joins the group; generates a vehicle use signature based on the private key upon receiving a vehicle use request to ensure the authenticity and unforgeability of the request; sends the signature to the vehicle to be used, and verifies the legitimacy of the signature through the public key of the vehicle use group to prevent illegal requests; after the signature verification passes, controls the access rights of the vehicle to be used to ensure that the vehicle is only used by authorized users, thereby improving the security of the vehicle sharing process. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0038] Figure 2 This is a schematic diagram of a sub-process in the second embodiment of the vehicle sharing method of the present application;

[0039] Figure 3 This is a schematic diagram of a sub-process in the third embodiment of the vehicle sharing method of the present application;

[0040] Figure 4 This is a schematic diagram of a vehicle sharing interaction process in an embodiment of a vehicle sharing method of the present application;

[0041] Figure 5 This is a schematic diagram of the module structure of the vehicle sharing device according to an embodiment of the present application;

[0042] Figure 6 This is a schematic diagram of the device structure of the hardware operating environment involved in the vehicle sharing method in the embodiment of the present application.

[0043] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0044] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0045] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0046] It should be noted that vehicle sharing, as an important part of the sharing economy, provides users with efficient and economical travel options, and has significant advantages in reducing resource waste and reducing traffic pressure. However, vehicle sharing also faces many technical challenges, including user information leakage, illegal use of vehicles, and difficulty in tracing responsibility. Existing vehicle sharing methods usually rely on traditional identity authentication methods (such as usernames, passwords, or QR codes). These methods often require users to provide identity information or account information, which can easily lead to personal privacy leakage during shared use. In addition, authentication methods that rely on static credentials (such as passwords or fixed tokens) are easily forged or stolen, and cannot effectively prevent illegal access and use, resulting in poor security in the vehicle sharing process. Therefore, how to improve the security of the vehicle sharing process has become a technical problem that needs to be solved urgently.

[0047] The main solution of this application is: when a user's group joining request is received, a private key is assigned to the user; when a vehicle use request is received, a vehicle use signature is generated based on the private key; the vehicle use signature is sent to the vehicle to be used, so that the vehicle to be used verifies the vehicle use signature based on the group public key; if the vehicle use signature passes the verification, the use permission of the vehicle to be used is controlled.

[0048] This application ensures the uniqueness of user identity by allocating private keys when users join a group; upon receiving a vehicle use request, a vehicle use signature is generated based on the private key to ensure the authenticity and non-forgeability of the request; the signature is sent to the vehicle to be used, and the legitimacy of the signature is verified by the public key of the vehicle use group to prevent illegal requests; after the signature verification is passed, the vehicle's open access permissions are controlled to ensure that the vehicle is only used by authorized users, thereby improving the security of the vehicle sharing process.

[0049] It should be noted that the execution subject of the method of this embodiment can be a computing service device with data processing, network communication and program running functions, or it can be the above-mentioned vehicle sharing device with the same or similar functions. This embodiment and the following embodiments will be described by taking the vehicle sharing device as an example.

[0050] Based on this, the first embodiment of the vehicle sharing method of this application is proposed, please refer to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the vehicle sharing method of the present application.

[0051] In this embodiment, the vehicle sharing method includes the following steps:

[0052] S1: when receiving a group joining request from a user, assigning a private key to the user;

[0053] It should be noted that a group refers to a logical collection of multiple users and vehicles. Members of a group share a group public key to verify signatures while ensuring anonymity among members. A user refers to an individual who wishes to join a group and participate in vehicle sharing. Identity verification and vehicle use are completed through a private key assigned by a group administrator. A group join request refers to a request from a user to a group administrator, indicating that the user wishes to join the group and obtain permission to participate in sharing. The private key is generated by the group administrator and uniquely assigned to the user. It is used to generate a vehicle use signature to ensure the legitimacy of the user's identity and the unforgeability of the signature.

[0054] Specifically, when a user first participates in car sharing, he / she sends a group joining request to the group administrator through a preset communication channel (such as a mobile application or website). The joining request usually includes the user's identity information, authentication credentials, etc., which are used to verify whether the user meets the joining conditions. After receiving the request, the administrator verifies the user's identity and permissions.

[0055] Furthermore, after verification, the administrator generates a private key for the user according to the key distribution rules of the group. The private key is unique and only corresponds to the user. The generated private key is distributed to the user through a secure and encrypted communication channel to ensure that it will not be intercepted or tampered with during the transmission process. Once the private key is successfully distributed, the administrator records the operation log of the user joining the group and includes the user in the group member management scope.

[0056] By assigning private keys to users, we ensure that each user's identity in the group is unique, preventing unauthorized individuals from pretending to be members and joining the group; the uniqueness and security of the private key ensure the legitimacy and unforgeability of subsequent signature operations, and build the basic security framework of the sharing system. In addition, the secure transmission and distribution process of the private key effectively avoids the risk of key leakage, provides a guarantee for the security of the system, and realizes the trusted management of users, improving the operating efficiency of the group and the trust of users in participation.

[0057] S2: When a vehicle use request is received, a vehicle use signature is generated based on the private key;

[0058] It should be noted that a vehicle use request refers to an operation request issued by a user to a sharing system, which includes information such as the vehicle ID and usage time that the user wishes to use, and is a key input to the vehicle sharing process. The vehicle use signature is a digital signature generated by the user through encryption calculation of the vehicle use request based on the private key, which is used to prove that the source and content of the request have not been tampered with.

[0059] Specifically, when a user wants to use a vehicle, he or she sends a vehicle use request through a sharing platform (such as a mobile phone application or terminal device). The request content includes the vehicle's identification information, expected usage time or mileage, etc. The system organizes this information into structured data as input data for the signature.

[0060] Furthermore, the user generates a vehicle use request signature based on his or her private key and request content through a preset signature algorithm. This process usually uses random numbers or other dynamic parameters to enhance the uniqueness of the signature and prevent the same request from being reused. After the signature is generated, it is sent to the vehicle to be used together with the original request data for subsequent verification.

[0061] By generating a vehicle use request signature based on a private key, the authenticity and unforgeability of the user request is ensured, preventing unauthorized users from forging requests to use the vehicle. At the same time, the signing process ensures the integrity of the request, that is, the request content cannot be tampered with or forged during transmission, thereby improving the security of the sharing system. In addition, the signature generation process introduces randomness, enhances the uniqueness of the signature, effectively prevents repeated request attacks, and further improves the reliability of the system and the ability to protect user privacy.

[0062] S3: sending the vehicle use signature to the vehicle to be used, so that the vehicle to be used verifies the vehicle use signature based on the group public key;

[0063] It should be noted that the vehicle to be used refers to the target vehicle selected by the user in the vehicle sharing system, and the vehicle use request issued by the user needs to be verified by the vehicle. The group public key is a public key distributed to the vehicle and the user, which is used to verify the validity of the vehicle use signature and ensure that the request comes from a legitimate user. Verification means that the vehicle checks the authenticity and integrity of the signature through a preset algorithm to confirm whether the request is legitimate and has not been tampered with.

[0064] Specifically, the user sends the generated vehicle use signature and request information to the vehicle to be used through the sharing platform. The sending process uses a secure communication protocol (such as an encrypted communication channel) to prevent the signature data from being intercepted or tampered with during the transmission process. After the vehicle to be used receives the signature, it temporarily stores it in the local memory for verification processing.

[0065] Furthermore, the vehicle to be used uses the group public key to verify the signature. The verification content includes: whether the signature matches the information in the user request to ensure the integrity of the request; whether the signature complies with the algorithm generation rules to ensure the authenticity of the request source; whether the random value in the signature is valid to prevent repeated requests from being used. If the verification is successful, the vehicle confirms the legitimacy of the user's request and enters the next step of the permission opening process; if the verification fails, the vehicle rejects the request and sends a verification failure message to the user.

[0066] The legitimacy and authenticity of the user's request is ensured by sending the vehicle usage signature to the vehicle to be used and verifying it. The signature verification process effectively prevents the forging of requests or tampering with the request content, and eliminates threats to the system from illegal users or malicious operations. In addition, the vehicle to be used verifies the signature through the group public key without directly accessing the user's private key, further protecting user privacy, building a safe and reliable sharing environment, and improving the operating efficiency and user trust of the vehicle sharing system.

[0067] S4: If the vehicle usage signature passes the verification, the use permission of the vehicle to be used is controlled.

[0068] It should be noted that usage rights refer to the operating permissions open to users for the vehicle to be used, including unlocking doors, starting the vehicle, etc., so that users can actually use the vehicle.

[0069] Specifically, when the vehicle to be used successfully verifies the vehicle use signature submitted by the user, it confirms that the request is a legitimate request. The vehicle control system receives the verification result and starts the subsequent process to open the permission. Common operations include unlocking the door, activating the vehicle start system, or opening the user interaction interface.

[0070] Furthermore, after the vehicle is granted access rights, it will update its status to "in use" to prevent other users from sending access requests at the same time. The sharing platform also records relevant information of the operation, including user ID, start time of use, vehicle ID, etc., for subsequent management and tracking. If an abnormality occurs during the process of granting access rights (such as vehicle hardware failure), the system will immediately notify the administrator and reject the operation.

[0071] By verifying the vehicle usage signature and controlling the access permissions of the vehicle to be used, strict security management of the vehicle sharing process is achieved, ensuring that only verified legitimate users can use the vehicle, eliminating the risk of illegal access and malicious use. The permission opening is directly linked to the signature verification result, forming a security closed loop, further improving the reliability of the system. In addition, the status update and logging functions provide data support for subsequent management, which helps with responsibility tracking and exception handling, and enhances the system's management capabilities and user trust.

[0072] This embodiment allocates a private key to the user upon receiving a group joining request from the user; generates a vehicle use signature based on the private key upon receiving a vehicle use request; sends the vehicle use signature to the vehicle to be used so that the vehicle to be used verifies the vehicle use signature based on the group public key; if the vehicle use signature passes the verification, controls the access rights of the vehicle to be used. This embodiment ensures the uniqueness of the user identity by allocating a private key when the user joins the group; generates a vehicle use signature based on the private key upon receiving a vehicle use request to ensure the authenticity and unforgeability of the request; sends the signature to the vehicle to be used, and verifies the legitimacy of the signature through the public key of the vehicle use group to prevent illegal requests; after the signature verification passes, controls the access rights of the vehicle to be used to ensure that the vehicle is only used by authorized users, thereby improving the security of the vehicle sharing process.

[0073] Based on the above first embodiment, a second embodiment of the vehicle sharing method of the present application is proposed. Figure 2 , Figure 2 This is a schematic diagram of a sub-process in the second embodiment of the vehicle sharing method of the present application.

[0074] like Figure 2 As shown, in this embodiment, before step S1, the following is further included:

[0075] S1a: Determine the generation of basic elements and random security parameters based on the number of group members;

[0076] S1b: Determine the group public key and private key generation rules according to the generation basic element and the random security parameter.

[0077] It should be noted that the number of group members refers to the total number of users who have joined the group and are able to use the car sharing system, which is used to determine the scale and security requirements of the encryption system. The generation base elements are the initial mathematical elements used to build the encryption system, which serve as the core basis for the generation of group public and private keys. Random security parameters are a set of randomly generated security values ​​used to enhance the security and unpredictability of keys and prevent attackers from speculating key information. Group public and private key generation rules are predefined algorithmic rules used to generate group public and private keys based on the base elements and security parameters.

[0078] Specifically, according to the estimated number of group members, select the appropriate key size and security parameters (such as the number of security bits, random value range). The more members there are, the more complex the security parameters need to be to resist potential attacks and improve the strength of the key.

[0079] Furthermore, a set of basic elements is generated to build the core structure of the encryption algorithm, such as the basic calculation parameters required for key generation and signature verification. On this basis, combined with random security parameters, group public and private key generation rules are formulated. The rules ensure that each private key is unique and corresponds to a specific user, while ensuring the verifiability of the group public key, which is convenient for subsequent signature verification.

[0080] By selecting and generating basic elements and random security parameters based on the number of group members, the flexibility and scalability of the encryption system are ensured, and the security strength can be dynamically adjusted according to the size of the group. The formulation of group public and private key generation rules provides a clear technical basis for subsequent user private key distribution and signature verification, ensuring the uniqueness and security of the key generation process, thereby enhancing the security and reliability of the entire vehicle sharing system.

[0081] Based on the above first embodiment, in this embodiment, step S1 includes:

[0082] S11: When receiving a group joining request from a user, verify the legitimacy of the group joining request;

[0083] S12: If the group joining request passes the verification, obtain the user identity information in the group joining request;

[0084] S13: Generate the private key based on the user identity information and the private key generation rule;

[0085] S14: Based on a preset encrypted communication channel, distribute the private key to the user.

[0086] It should be noted that legitimacy verification refers to the review of group joining requests to confirm whether the user's identity information and application content meet the requirements for group joining. User identity information refers to the unique identification information submitted by the user (such as user ID, account information or biometrics), which is used to generate and bind the user's private key. The private key generation rule is a preset algorithm or rule for generating a user's private key based on the group public key and user identity information, ensuring that each private key is unique and unpredictable. The preset encrypted communication channel refers to a pre-set communication method for securely transmitting private keys (such as an end-to-end encrypted channel) to ensure that data during transmission cannot be intercepted or tampered with.

[0087] Specifically, the user initiates a group joining request through a sharing platform (such as a mobile application or management website), and the request content includes user identity information, authentication credentials, etc. After receiving the request, the system verifies whether the user's identity information is legal, whether the authentication credentials are correct, and whether the user meets the conditions for joining the group. If the verification fails, the system directly rejects the request and feedbacks the reason.

[0088] Furthermore, when the group joining request is verified, the system extracts the user identity information in the request and generates a unique private key for the user according to the preset private key generation rules. The generated private key is bound to the user identity information and sent to the user through a secure and encrypted communication channel. After the user receives the private key, he needs to confirm receipt and store it securely. The system also records the distribution log for subsequent auditing.

[0089] By verifying the legitimacy of group joining requests, we ensure that only qualified users are allowed to join the group, preventing unauthorized users from entering the shared system. Private keys are generated based on user identity information and private key generation rules to ensure that each user's private key is unique and unforgeable, and is bound to the user's identity to provide security for subsequent signature operations. The use of encrypted communication channels prevents private keys from being intercepted or tampered with during transmission, further improving the security and reliability of the system and enhancing users' sense of trust.

[0090] This embodiment allocates a private key to the user upon receiving a group joining request from the user; generates a vehicle use signature based on the private key upon receiving a vehicle use request; sends the vehicle use signature to the vehicle to be used so that the vehicle to be used verifies the vehicle use signature based on the group public key; if the vehicle use signature passes the verification, controls the access rights of the vehicle to be used. This embodiment ensures the uniqueness of the user identity by allocating a private key when the user joins the group; generates a vehicle use signature based on the private key upon receiving a vehicle use request to ensure the authenticity and unforgeability of the request; sends the signature to the vehicle to be used, and verifies the legitimacy of the signature through the public key of the vehicle use group to prevent illegal requests; after the signature verification passes, controls the access rights of the vehicle to be used to ensure that the vehicle is only used by authorized users, thereby improving the security of the vehicle sharing process.

[0091] Based on the above second embodiment, a third embodiment of the vehicle sharing method of the present application is proposed. Figure 3 , Figure 3 This is a schematic diagram of a sub-process in the third embodiment of the vehicle sharing method of the present application.

[0092] In this embodiment, step S2 includes:

[0093] S21: when a vehicle use request is received, obtaining summary information in the vehicle use request;

[0094] S22: assigning a random number to the private key, and encrypting the summary information based on the private key and the random number to obtain preliminary signature data;

[0095] S23: Generate the vehicle usage signature based on the preliminary signature data and the group public key.

[0096] It should be noted that summary information is important information extracted from the vehicle use request. It is fixed-length data processed by hash or other algorithms to ensure the integrity and immutability of the request. The random number refers to the random value introduced in the signature generation process, which is used to enhance the uniqueness and security of the signature and prevent duplicate signatures from being used by attackers. The preliminary signature data is the intermediate data obtained by encrypting the summary information with the private key and the random number, and is the basis of the vehicle use signature.

[0097] Specifically, when a user sends a request to use a vehicle, the system extracts summary information from the request, which includes the core content of the request (such as vehicle identification, time, etc.). A random number is assigned to the user's private key, and the summary information is encrypted based on the private key and the random number to generate preliminary signature data. The encryption process ensures that the summary information cannot be tampered with, and the introduction of random numbers enhances the uniqueness of the signature and prevents replay attacks.

[0098] Furthermore, the preliminary signature data is combined with the group public key and a preset signature algorithm is applied to generate a vehicle use signature. This signature not only contains the legitimacy information of the user's request, but also ensures that the signature is consistent with the group's encryption rules through a public key verification chain. After the signature is generated, it is attached to the vehicle use request for subsequent verification.

[0099] By encrypting the summary information, the core content of the vehicle use request is ensured to maintain integrity and security during the signature generation process. The introduction of random numbers prevents repeated signatures from being maliciously exploited, and improves the uniqueness and anti-attack capabilities of the signature. The final signature is generated in combination with the group public key to ensure the legitimacy of the signature and the consistency within the system. The above mechanism builds a safe and reliable signature generation process, provides technical support for subsequent signature verification and permission management, and effectively improves the security and credibility of the vehicle sharing system.

[0100] Based on the above second embodiment, in this embodiment, step S4 includes:

[0101] S41: If the vehicle use signature passes the verification, the vehicle status of the vehicle to be used is checked;

[0102] S42: If the vehicle status is an available status and the hardware system is working normally, unlock the vehicle control system and the preset monitoring mechanism of the vehicle to be used, and control the opening of the use permission of the vehicle to be used.

[0103] It should be noted that the vehicle status refers to the current operating status of the vehicle, such as whether it is idle, occupied, or in a faulty state. The hardware system refers to the internal hardware equipment of the vehicle, including the communication module, control module, power system, etc., to ensure the normal operation of the vehicle. The vehicle control system is the core operating system of the vehicle, which controls the unlocking, starting and operation of the vehicle. The preset monitoring mechanism is a pre-set monitoring function configured during the operation of the vehicle, such as recording the location, speed and operating status, to ensure safety and management. Open access rights refer to the vehicle opening up operating rights to users, including unlocking the doors and allowing the vehicle to start.

[0104] Specifically, when the vehicle usage signature is verified, the control system of the vehicle to be used checks the vehicle status to confirm whether the vehicle is idle and not occupied by other users. At the same time, the system performs a self-check on the vehicle's hardware system to ensure that core components such as the communication module, control module, and power system are operating normally and can support the user's safe use. If the vehicle status is unavailable or there is an abnormality in the hardware system, the system refuses to open the permission and notifies the user of the reason.

[0105] Furthermore, if the vehicle status is available and the hardware system is normal, the system unlocks the vehicle control system and allows the user to operate the vehicle. At the same time, the preset monitoring mechanism is activated to record the real-time operating status of the vehicle (such as location, speed, power, etc.) and the user's operating behavior to ensure the safety and traceability of the operation process. After the permission is opened, the vehicle updates its status to "in use" to avoid duplicate allocation, and uploads the usage log to the shared management platform.

[0106] By checking the vehicle status and hardware system, we ensure that the vehicle is in a safe and normal working state before opening the access rights, effectively avoiding the use risks caused by hardware failure or vehicle occupation. Unlocking the vehicle control system and enabling the monitoring mechanism not only meets the user's use needs, but also realizes real-time monitoring and management of vehicle operation, improving the safety and reliability of the system. In addition, the status update and log recording functions make it easy for system managers to track and optimize the operation of the vehicle, thereby enhancing the stability and user experience of the vehicle sharing service.

[0107] Based on the above second embodiment, in this embodiment, after step S4, the following is further included:

[0108] S4a: continuously monitoring the real-time vehicle status of the vehicle to be used, and collecting behavior data of the vehicle to be used;

[0109] S4b: using the real-time vehicle status and the behavior data of the vehicle to be used as vehicle usage information, and uploading the vehicle usage information regularly;

[0110] S4c: When receiving the end-of-use instruction, the vehicle control system is disabled and the vehicle status is updated, and the end-of-use time is recorded.

[0111] It should be noted that real-time vehicle status refers to status information updated in real time during the use of the vehicle, such as location, speed, power (or fuel level) and whether there are any abnormal conditions. Behavioral data refers to the operational information generated by the user during the use of the vehicle, such as acceleration, braking, mileage, parking location, etc., which is used to analyze user behavior and vehicle usage. Vehicle usage information is composed of real-time vehicle status and vehicle behavior data, reflecting the comprehensive operation of the vehicle during use. The end-of-use instruction is a command issued by the user or the system, marking the end of vehicle use, including locking the vehicle and shutting down related systems. The end of use time refers to the specific time point when the use of the vehicle is recorded to generate a usage report.

[0112] Specifically, after the vehicle is opened for use, the real-time monitoring mechanism is activated to record the vehicle's operating status, such as key parameters such as current location, speed, and power, and collect user operation behavior data (such as driving mode and mileage). The real-time monitoring data and behavior data are organized into vehicle usage information, and the information is uploaded to the sharing platform according to a preset cycle (for example, every minute or after each status change). The platform stores this data for subsequent analysis, management, and user bill calculation.

[0113] Furthermore, after the user has finished using the vehicle, he / she sends an end-of-use instruction through the terminal. After receiving the instruction, the system disables the vehicle control system to prevent the vehicle from being operated again, unlocks the monitoring mechanism and stops data collection. The vehicle status is updated to "idle" or "pending maintenance", and the end time of use is recorded to generate a complete usage report. All data is stored on the shared platform, and a log is generated for tracking and auditing.

[0114] By continuously monitoring the real-time status and behavior data of the vehicle, the system can timely grasp the vehicle operation status, detect and handle anomalies, and ensure the safety and controllability of the use process. Regularly uploading vehicle usage information to the sharing platform will help achieve refined management and provide data support for user bill calculation and system optimization. The end of use instruction triggers the vehicle control system to disable and update the status to prevent subsequent illegal operations, while fully recording the usage information for auditing and tracking, thereby further improving the reliability, safety and user experience of the vehicle sharing system.

[0115] This embodiment allocates a private key to the user upon receiving a group joining request from the user; generates a vehicle use signature based on the private key upon receiving a vehicle use request; sends the vehicle use signature to the vehicle to be used so that the vehicle to be used verifies the vehicle use signature based on the group public key; if the vehicle use signature passes the verification, controls the access rights of the vehicle to be used. This embodiment ensures the uniqueness of the user identity by allocating a private key when the user joins the group; generates a vehicle use signature based on the private key upon receiving a vehicle use request to ensure the authenticity and unforgeability of the request; sends the signature to the vehicle to be used, and verifies the legitimacy of the signature through the public key of the vehicle use group to prevent illegal requests; after the signature verification passes, controls the access rights of the vehicle to be used to ensure that the vehicle is only used by authorized users, thereby improving the security of the vehicle sharing process.

[0116] For example, in order to help understand the technical concept or technical principle of the vehicle sharing method of the above embodiment, please refer to Figure 4 , Figure 4 This is a schematic diagram of the vehicle sharing interaction process in one embodiment of the vehicle sharing method of the present application.

[0117] The specific implementation of the vehicle sharing method in this embodiment includes four steps: system initialization, signing, verification and opening, and the participants include administrators, users, groups and vehicles.

[0118] Specific plan for system initialization: When the administrator initializes the system, a parameter n (the number of group members) is used as input, and the steps are divided into the following steps:

[0119] 1. Select group elements and random integers And set group elements u, v∈G1 so that

[0120] 2. Choose a random integer And set the group element

[0121] 3. Use γ to generate an SDH tuple (A i ,x i ):choose

[0122] 4. The group public key is gpk = (g1, g2, h, u, v, w), and the group administrator's private key is gmsk = (ξ1, ξ2). Each user's private key is gsk[i] = (A i ,x i ). γ is known only to group administrators.

[0123] Specific plan for signature:

[0124] When user i applies to use a vehicle, a signature is generated with the group public key gpk = (g1, g2, h, u, v, w) and the user private key gsk[i] = (A i ,x i ) and message M∈{0,1} * As input, calculate the signature σ =

[0125] (T1,T2,T3,c,s α ,s β ,s x ,s δ1 ,s δ2 ), the steps are as follows:

[0126] 1. Choose a random number And calculate the signature intermediate value

[0127] T1=u α ,

[0129] T3=A i ·h α+β ;

[0130] 2. Calculate auxiliary values

[0131] δ1=x i α,

[0133] 3. Given a random integer And calculate the random value

[0134]

[0135] 4. User i sends (T1, T2, T3, R1, R2, R3, R4, R5) to the vehicle.

[0136] 5. The vehicle will select a random challenge And send it to user i.

[0137] 6. User i calculates the response:

[0138] s α =r α +cα,

[0139] s β =r β +cβ ,

[0140] s x =r x +cx i ,

[0141] s δ1 =r δ1 +cδ1,

[0142] s δ2 =r δ2 +cδ2 ;

[0143] 7. The final signature is σ=(T1,T2,T3,c,s α ,s β ,s x ,s δ1 ,s δ2 ).

[0144] Specific verification scheme:

[0145] After user i sends the signature to the vehicle, the vehicle needs to verify the signature. Given the group public key gpk = (g1, g2, h, u, v, w), the message M and the group signature σ, the verification steps are as follows:

[0146] 1. Recalculate the random value in the signature:

[0147]

[0148]

[0149] 2. Verify that the following equation holds true:

[0150]

[0151] If it is established, the verification is passed and the user can use the vehicle, otherwise not.

[0152] Specific programs opened:

[0153] This algorithm is used when the vehicle breaks down, is damaged, or an illegal behavior occurs. The administrator can track the user through the signature. With the group public key gpk = (g1, g2, h, u, v, w), the administrator private key gmsk = (ξ1, ξ2), the message M and the signature σ = (T1, T2, T3, c, s α ,s β ,s x ,s δ1 ,s δ2 ) as input, the steps are as follows:

[0154] 1. Verify that σ is a valid signature on M.

[0155] 2. Treat the first three elements (T1, T2, T3) as a linear encryption and restore the user's elements

[0156]

[0157] 3. The administrator holds the element of the user's private key i}, the user index can be found and the user identity can be tracked based on the identity A recovered from the signature.

[0158] The present application also provides a vehicle sharing device, please refer to Figure 5 , Figure 5 This is a schematic diagram of the module structure of a vehicle sharing device according to an embodiment of the present application, wherein the vehicle sharing device comprises:

[0159] The private key distribution module 501 is used to distribute a private key to a user when receiving a group joining request from the user;

[0160] The signature generation module 502 is used to generate a vehicle use signature based on the private key when receiving a vehicle use request;

[0161] A signature verification module 503, configured to send the vehicle use signature to the vehicle to be used, so that the vehicle to be used verifies the vehicle use signature based on the group public key;

[0162] The target module 504 is used to control the opening of the use authority of the vehicle to be used if the vehicle use signature passes the verification.

[0163] The vehicle sharing device provided in the embodiment of the present application adopts the vehicle sharing method in the above embodiment, which can solve the technical problem of how to improve the safety of the vehicle sharing process. Compared with the prior art, the beneficial effects of the vehicle sharing device provided in the embodiment of the present application are the same as the beneficial effects of the vehicle sharing method provided in the above embodiment, and the other technical features in the vehicle sharing device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0164] The present application provides a vehicle sharing device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the vehicle sharing method in the above-mentioned embodiment.

[0165] Reference below Figure 6 , Figure 6 The schematic diagram of the device structure of the hardware operating environment involved in the vehicle sharing method in the embodiment of the present application shows a schematic diagram of the structure of the vehicle sharing device suitable for implementing the embodiment of the present application. The vehicle sharing device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 6 The vehicle sharing device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0166] like Figure 6As shown, the vehicle sharing device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the vehicle sharing device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the vehicle sharing device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a vehicle sharing device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.

[0167] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0168] The vehicle sharing device provided by the present application adopts the vehicle sharing method in the above embodiment, which can solve the technical problem of how to improve the safety of the vehicle sharing process. Compared with the prior art, the beneficial effects of the vehicle sharing device provided by the present application are the same as the beneficial effects of the vehicle sharing method provided by the above embodiment, and the other technical features in the vehicle sharing device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0169] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0170] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0171] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the vehicle sharing method in the above-mentioned embodiment.

[0172] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0173] The computer-readable storage medium may be included in the vehicle sharing device; or may exist independently without being assembled into the vehicle sharing device.

[0174] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the vehicle sharing device, the vehicle sharing device: when receiving a group joining request from a user, assigns a private key to the user; when receiving a vehicle use request, generates a vehicle use signature based on the private key; sends the vehicle use signature to the vehicle to be used, so that the vehicle to be used verifies the vehicle use signature based on the group public key; if the vehicle use signature passes the verification, controls the vehicle to be used to open the use permission. The computer program code for performing the operations of the present application can be written in one or more programming languages ​​or a combination thereof, and the programming languages ​​include object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or it can be connected to an external computer (for example, through the Internet using an Internet service provider).

[0175] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0176] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0177] The readable storage medium provided in this application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned vehicle sharing method, and can solve the technical problem of how to improve the safety of the vehicle sharing process. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the vehicle sharing method provided in the above-mentioned embodiment, and will not be repeated here.

[0178] An embodiment of the present application provides a computer program product, including a computer program, which implements the steps of the vehicle sharing method as described above when executed by a processor.

[0179] The computer program product provided in this application can solve the technical problem of how to improve the safety of the vehicle sharing process. Compared with the prior art, the beneficial effects of the computer program product provided in the embodiment of this application are the same as the beneficial effects of the vehicle sharing method provided in the above embodiment, which will not be repeated here.

[0180] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent processing scope of the present application.

Claims

1. A vehicle sharing method, characterized in that: The method comprises: When receiving a group joining request from a user, assigning a private key to the user; When a vehicle use request is received, generating a vehicle use signature based on the private key; Sending the vehicle use signature to the vehicle to be used, so that the vehicle to be used verifies the vehicle use signature based on the group public key; If the vehicle usage signature passes the verification, the use permission of the vehicle to be used is controlled.

2. The method according to claim 1, characterized in that Before the step of allocating a user private key to the user when receiving a group joining request from the user, the method further includes: Based on the number of group members, determine the generation of basic elements and random security parameters; The group public key and private key generation rules are determined according to the generation basic element and the random security parameter.

3. The method according to claim 2, characterized in that The step of allocating a private key to the user upon receiving a group joining request from the user comprises: When receiving a group joining request from a user, verifying the legitimacy of the group joining request; If the group joining request passes the verification, obtaining the user identity information in the group joining request; Generate the private key based on the user identity information and a private key generation rule; Based on a preset encrypted communication channel, the private key is distributed to the user.

4. The method according to claim 1, characterized in that The step of generating a vehicle use signature based on the private key when a vehicle use request is received includes: When receiving a vehicle use request, obtaining summary information in the vehicle use request; Assigning a random number to the private key, and encrypting the summary information based on the private key and the random number to obtain preliminary signature data; The vehicle use signature is generated based on the preliminary signature data and the group public key.

5. The method according to claim 1, characterized in that If the vehicle use signature passes the verification, the step of controlling the opening of the use permission of the vehicle to be used comprises: If the vehicle use signature passes the verification, checking the vehicle status of the vehicle to be used; If the vehicle status is available and the hardware system works normally, the vehicle control system and the preset monitoring mechanism of the vehicle to be used are unlocked, and the access permission of the vehicle to be used is controlled.

6. The method according to claim 5, characterized in that After the step of controlling the opening of the use right of the vehicle to be used if the vehicle use signature passes the verification, the method further includes: Continuously monitoring the real-time vehicle status of the vehicle to be used, and collecting behavior data of the vehicle to be used; Using the real-time vehicle status and the behavior data of the vehicle to be used as vehicle usage information, and uploading the vehicle usage information regularly; When the end-of-use instruction is received, the vehicle control system is disabled and the vehicle status is updated, and the end-of-use time is recorded.

7. A vehicle sharing device, characterized in that: The device comprises: A private key distribution module, configured to distribute a private key to a user upon receiving a group joining request from the user; A signature generation module, configured to generate a vehicle use signature based on the private key when a vehicle use request is received; A signature verification module, used for sending the vehicle use signature to the vehicle to be used, so that the vehicle to be used verifies the vehicle use signature based on the group public key; The target module is used to control the opening of the use permission of the vehicle to be used if the vehicle use signature passes the verification.

8. A computer device, characterized in that: The device comprises: a memory, a processor, and a vehicle sharing program stored in the memory and executable on the processor, wherein the vehicle sharing program is configured to implement the steps of the vehicle sharing method according to any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium stores a vehicle sharing program, and when the vehicle sharing program is executed by the processor, the steps of the vehicle sharing method according to any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the vehicle sharing method according to any one of claims 1 to 6 are implemented.

Images