A vehicle sharing method and device, vehicle and storage medium

Abstract

The application provides a vehicle sharing method and device, a vehicle and a storage medium. The method comprises the following steps: receiving verification information of a first account sent by a vehicle owner terminal, the first account being an account logged in by a shared person terminal, and the vehicle owner terminal being a terminal logged in by a second account; verifying the first account according to the received verification information; and in the case that the first account is verified, granting the shared person terminal the right to operate a target vehicle, the target vehicle being a vehicle bound to the second account. The method can share vehicles, so that family users or friends can experience convenient vehicle network connection functions, thereby improving the utilization rate of the vehicle.

Description

Technical Field

[0001] This application relates to the field of vehicle networking technology, and more specifically, to a vehicle sharing method, apparatus, vehicle, and storage medium in the field of vehicle networking technology. Background Technology

[0002] Currently, vehicle connectivity typically involves one user, one vehicle, and one app, allowing users to remotely control their vehicles via a mobile app, such as remotely turning on the air conditioning or starting the engine. However, vehicle usage is currently very low, with vehicles remaining idle most of the time. Therefore, how to share vehicles with family members or friends, enabling multiple people to experience the convenience of vehicle connectivity features and thereby increasing vehicle utilization, has become a pressing issue. Summary of the Invention

[0003] This application provides a vehicle sharing method, apparatus, vehicle, and storage medium, which enables vehicle sharing and thereby improves vehicle utilization.

[0004] Firstly, a vehicle-sharing method is provided, applied to a cloud platform, the method comprising:

[0005] Receive verification information for the first account sent by the vehicle owner's terminal. The first account is the account logged in by the shared terminal, and the vehicle owner's terminal is the terminal logged in to the second account.

[0006] Verify the first account based on the received verification information;

[0007] Once the first account is verified, the user's terminal is granted permission to operate the target vehicle, which is the vehicle bound to the second account.

[0008] In the above technical solution, the account logged in by the recipient's terminal is verified. If the verification is successful, the recipient's terminal can operate the target vehicle. That is, this embodiment of the application allows vehicle sharing only after the recipient's account is verified, thus improving the security of vehicle sharing. Furthermore, it enables family users or friends to experience convenient vehicle connectivity functions, thereby increasing vehicle utilization.

[0009] In conjunction with the first aspect, in some possible implementations, before receiving the verification information sent by the vehicle owner's terminal, the method further includes:

[0010] Receive a verification information generation request for the first account sent by the vehicle owner's terminal, generate verification information, and send the generated verification information to the shared terminal so that the shared terminal can send the generated verification information to the vehicle owner's terminal;

[0011] Verify the first account based on the received verification information, including:

[0012] Compare the received verification information with the generated verification information;

[0013] Verify the first account based on whether the received verification information and the generated verification information are consistent.

[0014] In the above technical solution, the verification of the target vehicle's operating permissions is improved by comparing whether the generated verification information is consistent with the verification information received from the target vehicle's terminal. This prevents the target vehicle's operating permissions from being mistakenly shared with other accounts.

[0015] Combining the first aspect and the above implementation methods, in some possible implementation methods, granting the user's terminal permission to operate the target vehicle includes:

[0016] Obtain permission setting instructions from the vehicle owner's terminal for multiple functions in the target vehicle;

[0017] Based on the permission setting instructions, determine the target function, which is a function that the recipient's terminal has permission to use;

[0018] Grant the user's terminal permission to operate the target function in the target vehicle.

[0019] In the above technical solution, the vehicle owner's terminal can independently set the permissions for the shared terminal to use the target vehicle's functions. This can improve the flexibility of sharing control permissions for the target vehicle and further enhance the user experience.

[0020] In combination with the first aspect and the above implementation methods, in some possible implementations, after granting the user's terminal permission to operate the target vehicle, the method further includes:

[0021] Receive operation instructions for the target function sent by the terminal of the recipient;

[0022] Send an operation command to the target vehicle so that the target vehicle responds to the operation command.

[0023] In combination with the first aspect and the above implementation methods, in some possible implementations, after granting the user's terminal permission to operate the target vehicle, the method further includes:

[0024] Receive control commands for permissions sent by the vehicle owner's terminal. The control commands include any one or a combination of the following: permission modification command, permission deactivation command, and permission validity period setting command;

[0025] Control commands are used to control the permissions of the user's terminal to operate the target vehicle.

[0026] In the above technical solution, the vehicle owner's terminal can modify or close the permissions of the shared terminal to operate the target vehicle, and can also set the effective duration of the permissions, which improves the security and flexibility of sharing control permissions of the target vehicle and further enhances the user experience.

[0027] In combination with the first aspect and the above implementation methods, in some possible implementations, after granting the user's terminal permission to operate the target vehicle, the method further includes:

[0028] Receive abnormal alarm notifications sent by the target vehicle;

[0029] Anomaly alerts will be pushed to the device of the person being shared with and / or the device of the vehicle owner.

[0030] The above technical solution can promptly notify the sharing user's terminal and / or the vehicle owner's terminal of abnormal vehicle alarms. This can solve the problem of the shared user not receiving timely alarm notifications when encountering abnormal situations while using the vehicle, thus preventing vehicle usage problems or accidents. Moreover, the vehicle owner's terminal can also be notified of abnormal vehicle conditions in a timely manner.

[0031] In combination with the first aspect and the above implementation methods, in some possible implementations, after granting the user's terminal permission to operate the target vehicle, the method further includes:

[0032] When the first query instruction is received from the vehicle owner terminal, the system queries the records of the target vehicle being operated on according to the first query instruction, obtains the first query result, and sends the first query result to the vehicle owner terminal.

[0033] When a second query instruction is received from the shared terminal, the system queries the records of the shared terminal's operations on the target vehicle according to the second query instruction, obtains the second query result, and sends the second query result to the shared terminal.

[0034] Secondly, a vehicle-sharing device is provided, the device comprising:

[0035] The first receiving module is used to receive the verification information of the first account sent by the vehicle owner terminal. The first account is the account logged in by the shared terminal, and the vehicle owner terminal is the terminal logged in to the second account.

[0036] The verification module is used to verify the first account based on the received verification information;

[0037] The permission granting module is used to grant the terminal of the shared user permission to operate the target vehicle, which is the vehicle bound to the second account, after the first account has been verified.

[0038] In conjunction with the second aspect, in some possible implementations, the device further includes:

[0039] The first sending module is used to receive a verification information generation request for the first account sent by the vehicle owner terminal, generate verification information, and send the generated verification information to the shared terminal so that the shared terminal sends the generated verification information to the vehicle owner terminal.

[0040] The verification module is used for:

[0041] Compare the received verification information with the generated verification information;

[0042] Verify the first account based on whether the received verification information and the generated verification information are consistent.

[0043] Combining the second aspect and the above implementation methods, in some possible implementations, the permission granting module is used for:

[0044] Obtain permission setting instructions from the vehicle owner's terminal for multiple functions in the target vehicle;

[0045] Based on the permission setting instructions, determine the target function, which is a function that the recipient's terminal has permission to use;

[0046] Grant the user's terminal permission to operate the target function in the target vehicle.

[0047] In conjunction with the second aspect and the above-described implementations, in some possible implementations, the device further includes:

[0048] The second receiving module is used to receive operation instructions for the target function sent by the terminal of the recipient;

[0049] The second sending module is used to send operation commands to the target vehicle so that the target vehicle can respond to the operation commands.

[0050] In conjunction with the second aspect and the above-described implementations, in some possible implementations, the device further includes:

[0051] The third receiving module is used to receive control instructions for permissions sent by the vehicle owner terminal. The control instructions include any one or a combination of the following: permission modification instructions, permission deactivation instructions, and instructions for setting the validity period of permissions.

[0052] The control module is used to control the access rights of the user's terminal to operate the target vehicle according to control commands.

[0053] In conjunction with the second aspect and the above-described implementations, in some possible implementations, the device further includes:

[0054] The fourth receiving module is used to receive abnormal alarm notifications sent by the target vehicle;

[0055] The push module is used to push abnormal alarm notifications to the terminals of the recipients and / or the vehicle owner's terminals.

[0056] In conjunction with the second aspect and the above-described implementations, in some possible implementations, the device further includes:

[0057] The first query module is used to query the records of the target vehicle being operated on according to the first query instruction when it receives the first query instruction sent by the vehicle owner terminal, obtain the first query result, and send the first query result to the vehicle owner terminal.

[0058] The second query module is used to query the records of the target vehicle operated by the shared terminal according to the second query instruction when it receives the second query instruction sent by the shared terminal, obtain the second query result, and send the second query result to the shared terminal.

[0059] Thirdly, a vehicle is provided, including a memory and a processor. The memory is used to store executable program code, and the processor is used to call and run the executable program code from the memory, causing the vehicle to perform the methods described in the first aspect or any possible implementation thereof.

[0060] Fourthly, a computer program product is provided, comprising: computer program code, which, when run on a computer, causes the computer to perform the methods described in the first aspect or any possible implementation thereof.

[0061] Fifthly, a computer-readable storage medium is provided that stores computer program code, which, when executed on a computer, causes the computer to perform the methods described in the first aspect or any possible implementation thereof. Attached Figure Description

[0062] Figure 1 This is a schematic diagram of a system architecture provided in an embodiment of this application;

[0063] Figure 2 This is a schematic flowchart illustrating a vehicle sharing method provided in an embodiment of this application;

[0064] Figure 3 This is a schematic flowchart illustrating another vehicle-sharing method provided in an embodiment of this application;

[0065] Figure 4 This is a schematic diagram of the structure of a vehicle sharing device provided in an embodiment of this application;

[0066] Figure 5 This is a schematic diagram of the structure of a vehicle provided in an embodiment of this application. Detailed Implementation

[0067] The technical solutions in this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0068] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.

[0069] Before providing a detailed explanation of the vehicle sharing method provided in the embodiments of this application, the application scenarios and system architecture provided in the embodiments of this application will be introduced first.

[0070] Typically, after a vehicle is sold, the online platform (cloud platform) binds the owner and the vehicle. The owner can then remotely operate the vehicle and use its smart connectivity applications by logging into the account linked to the vehicle. However, when the owner needs to share the vehicle with someone else, the non-owner (the person being shared with) cannot use the vehicle's smart connectivity applications through their own account. Furthermore, if the vehicle experiences abnormal warnings while the non-owner is using it, such as an open door, the non-owner may not be aware of this in time, potentially leading to subsequent accidents.

[0071] Based on this, this application provides a vehicle sharing method that enables vehicle sharing, thereby improving vehicle utilization. Furthermore, it can promptly alert the shared user when a vehicle experiences an abnormal alarm.

[0072] Please refer to Figure 1 , Figure 1 This is a schematic diagram of a system architecture provided in an embodiment of this application. For example, as shown... Figure 1 As shown, the system architecture 100 includes a vehicle owner terminal 101, at least one shared user terminal 102, a cloud platform 103, and a target vehicle 104. The cloud platform 103 communicates with the vehicle owner terminal 101, the shared user terminal 102, and the target vehicle 104. The vehicle owner terminal 101 also communicates with the shared user terminal 102. These communication connections can be wired or wireless, and this embodiment does not limit the specific connection.

[0073] The vehicle owner terminal 101 is used to obtain the account information of the first account and send a verification information generation request for the first account to the cloud platform 103 based on the account information. The vehicle owner terminal 101 is also used to receive the verification information of the first account and send the received verification information to the cloud platform 103. The first account is the account logged in by the sharing terminal 102, and the vehicle owner terminal 101 is the terminal for logging in to the second account.

[0074] It should be noted that the account in this embodiment can be understood as the account already logged in to the APP used to control the target vehicle on the terminal. That is, the first account is the account already logged in to the APP used to control the target vehicle 104 on the shared terminal 102, and the second account is the account already logged in to the APP used to control the target vehicle 101 on the vehicle owner terminal 101. In other words, the shared user can log in to the APP by entering the first account on the shared terminal 102, and the vehicle owner can log in to the APP by entering the second account on the vehicle owner terminal 101.

[0075] Example of the account information for the first account: the mobile phone number of the person whose account is being shared with; example of the account information for the second account: the mobile phone number of the car owner.

[0076] The cloud platform 103 receives a verification information generation request from the vehicle owner terminal 101, generates verification information, and sends the generated verification information to the shared user terminal 102, so that the shared user terminal 102 sends the generated verification information back to the vehicle owner terminal 101. The cloud platform 103 also receives verification information for a first account from the vehicle owner terminal 101 and verifies the first account based on the received verification information. If the first account is successfully verified, the shared user terminal 102 is granted permission to operate the target vehicle 104. The target vehicle 104 is the vehicle bound to the second account. The process by which the cloud platform 103 grants the shared user terminal 102 permission to operate the target vehicle 104 will be described in detail later and will not be elaborated upon here.

[0077] The recipient terminal 102 is used to receive the verification information generated by the cloud platform 103 and send the generated verification information to the vehicle owner terminal 101.

[0078] The vehicle owner terminal 101 and the shared user terminal 102 can be any electronic product capable of human-computer interaction with the user through one or more methods such as a keyboard, touchpad, touchscreen, remote control, voice interaction, or handwriting device. Examples include personal computers (PCs), mobile phones, smartphones, personal digital assistants (PDAs), pocket PCs (PPCs), and tablet computers. This application embodiment does not limit the types of the vehicle owner terminal 101 and the shared user terminal 102.

[0079] Cloud platform 103 can be a single server, a server cluster consisting of multiple servers, or a cloud computing service center.

[0080] The target vehicle 104 is a vehicle driven by an engine. This application embodiment does not limit the type of the target vehicle.

[0081] Furthermore, those skilled in the art should understand that the aforementioned vehicle owner terminal 101, shared user terminal 102, cloud platform 103, and target vehicle 104 are merely examples. Other existing or future terminals, cloud platforms, and vehicles that are applicable to the embodiments of this application should also be included within the protection scope of the embodiments of this application, and are hereby incorporated by reference.

[0082] The vehicle sharing method provided in the embodiments of this application will be explained in detail below.

[0083] Figure 2 This is a schematic flowchart illustrating a vehicle-sharing method provided in an embodiment of this application. The method is exemplarily applied to… Figure 1 The cloud platform in the system architecture shown. Figure 2 As shown, the method 200 includes:

[0084] Step 201: Receive verification information of the first account sent by the vehicle owner terminal. The first account is the account logged in by the shared terminal, and the vehicle owner terminal is the terminal logged in to the second account.

[0085] The cloud platform can interact between the vehicle owner's terminal and the shared user's terminal, ensuring that both parties are aware of the information and that the operation is secure. Since the verification information for the first account on the vehicle owner's terminal is sent by the shared user's terminal, in some embodiments, before step 201, the cloud platform can first receive a verification information generation request for the first account sent by the vehicle owner's terminal, generate verification information, and send the generated verification information to the shared user's terminal, so that the shared user's terminal can send the generated verification information back to the vehicle owner's terminal. The verification information can, for example, be a verification code, or other types of information; this application embodiment does not limit this.

[0086] Specifically, when a vehicle owner shares a target vehicle with a recipient, the owner can fill in the account information of the recipient's logged-in account (i.e., the first account's account information) on their own terminal and click "Get Verification Information." In response to the owner's action, the vehicle owner's terminal sends a verification information generation request for the first account to the cloud platform. The cloud platform receives this request, generates the verification information, and sends it to the recipient's terminal. When the recipient's terminal receives the verification information generated by the cloud platform, it can send the generated verification information back to the vehicle owner's terminal. In this way, the vehicle owner's terminal can send the received verification information to the cloud platform, enabling the cloud platform to verify the first account according to step 202.

[0087] Step 202: Verify the first account based on the received verification information.

[0088] In some embodiments, step 202 can be implemented by: comparing the received verification information with the generated verification information; and verifying the first account based on whether the received verification information and the generated verification information are consistent.

[0089] Specifically, after the cloud platform receives the verification information sent by the vehicle owner's terminal, it compares the received verification information with the previously generated verification information and verifies the primary account based on the comparison result. If the received verification information matches the generated verification information, the primary account is confirmed to have been verified successfully. This prevents the target vehicle's operating permissions from being mistakenly shared with other accounts, thus improving the security of vehicle sharing.

[0090] Step 203: If the first account is verified, grant the user's terminal permission to operate the target vehicle, which is the vehicle bound to the second account.

[0091] Once the first account is verified, the cloud platform can grant the shared user's terminal permission to operate the target vehicle, enabling the shared user's terminal to control the target vehicle through the first account.

[0092] If the initial account verification fails, the cloud platform will refuse to grant the recipient's terminal permission to operate the target vehicle. This enhances the security of vehicle sharing.

[0093] In some embodiments, step 203 can be implemented as follows: obtaining permission setting instructions from the vehicle owner's terminal for multiple functions in the target vehicle; determining the target function based on the permission setting instructions, wherein the target function is a function that the shared terminal has permission to use; and granting the shared terminal permission to operate the target function in the target vehicle.

[0094] The permission setting instructions are generated based on the permission settings for multiple functions of the target vehicle made by the car owner in the app installed on the car owner's terminal. The car owner can set the functions of the target vehicle that the shared user can use on their terminal, and the terminal generates permission setting instructions based on the owner's actions. The cloud platform obtains these permission setting instructions and, based on them, determines the functions of the target vehicle that the shared user can use, i.e., identifies the target functions. It then grants the shared user's terminal permission to operate the target function. Thus, the shared user's terminal can control the target vehicle by operating the target function. These functions can also include applications.

[0095] Examples of target functions include engine control, air conditioning control, fuel consumption query, and mileage query.

[0096] After granting the shared user's terminal permission to operate the target vehicle, in some embodiments, the cloud platform can also receive operation instructions for the target function sent by the shared user's terminal; and send operation instructions to the target vehicle so that the target vehicle responds to the operation instructions.

[0097] When the shared terminal can control the target vehicle, the shared user can set operations for the target function on the shared terminal, and the shared terminal generates operation instructions based on these operations. The cloud platform receives the operation instructions and sends them to the target vehicle, so that the remote communication terminal (Telematics Box, TBOX) in the target vehicle can execute the operations in the operation instructions.

[0098] For example, when the recipient wants to remotely turn on the air conditioning of a target vehicle, they can click to turn on the air conditioning in the air conditioning control application on their own device. The device then generates an air conditioning start command. The cloud platform receives this command and sends it to the target vehicle, where the TBOX turns on the air conditioning. In this way, the recipient can remotely control the target vehicle through their own device, improving the user experience of sharing the vehicle.

[0099] After granting the shared user's terminal permission to operate the target vehicle, in some embodiments, the cloud platform can also receive control instructions for the permissions sent by the vehicle owner's terminal. The control instructions include any one or a combination of the following: permission modification instructions, permission deactivation instructions, and permission validity duration setting instructions; and control the shared user's terminal permission to operate the target vehicle according to the control instructions.

[0100] Specifically, vehicle owners can set permissions for the shared user's operation of the target vehicle on their own devices, such as modifying permissions, disabling permissions, and setting the duration of permission validity. The vehicle owner's device generates control commands based on these operations, and the cloud platform receives these control commands and controls the shared user's device's permissions to operate the target vehicle accordingly.

[0101] For example, a car owner can set the effective duration of the shared user's control over the target vehicle on their own terminal, such as one week. The car owner's terminal generates a control command based on the owner's settings, and the cloud platform receives this command and sets the effective duration of the shared user's control over the target vehicle to one week. Alternatively, after the shared user's terminal has operated the target vehicle, if the car owner wants to temporarily modify or disable the shared user's control over the target vehicle, they can do so on their own terminal. The cloud platform, based on the received control command, will modify or disable the shared user's control over the target vehicle accordingly. This enhances the car owner's control over the shared user's control over the target vehicle, further improving the flexibility of vehicle sharing.

[0102] Furthermore, in this embodiment, the vehicle owner can share the target vehicle multiple times to allow more family members or friends to experience the vehicle sharing function. Moreover, in this embodiment, the shared user can query their own records of operating the target vehicle, while the vehicle owner can query all records of shared users operating the target vehicle.

[0103] Based on this, in some embodiments, when a first query instruction is received from the vehicle owner's terminal, the cloud platform can query the records of operations performed on the target vehicle according to the first query instruction, obtain a first query result, and send the first query result to the vehicle owner's terminal. When a second query instruction is received from the shared user's terminal, the cloud platform can query the records of operations performed on the target vehicle by the shared user's terminal according to the second query instruction, obtain a second query result, and send the second query result to the shared user's terminal.

[0104] Specifically, when a car owner wants to check the full operation record, they can query the records of operations performed on the target vehicle on their terminal. The terminal generates a first query command based on this command, and the cloud platform queries the records of operations performed on the target vehicle based on the first query command, obtains the first query result, and sends the first query result to the terminal, so that the car owner can promptly understand the operations performed on the target vehicle by the shared user. In other words, the car owner can perform a full query on their terminal.

[0105] When the recipient wants to check their personal operation records, they can perform a query on their terminal regarding the records of their operations on the target vehicle. The recipient's terminal generates a second query command based on this command. The cloud platform then uses this second query command to search for the records of the target vehicle's operations on the recipient's terminal, obtains the second query result, and sends it back to the recipient's terminal so that the recipient can promptly understand their personal operation status. In other words, the recipient can only perform personal operation queries on their own terminal.

[0106] In addition, in some embodiments, the cloud platform can also receive abnormal alarm notifications sent by the target vehicle and push the abnormal alarm notifications to the terminal of the person being shared with and / or the vehicle owner's terminal.

[0107] Specifically, when the user operates the target vehicle, if the target vehicle detects abnormal alarms such as an open door or the presence of a biological entity inside, it can send an alarm notification to the cloud platform. The cloud platform then pushes the alarm notification to the user's terminal and / or the vehicle owner's terminal, so that the user and / or the vehicle owner can be informed of the target vehicle's status in a timely manner. Examples of methods for the cloud platform to push alarm notifications include SMS and email, but this embodiment does not limit the specific method used.

[0108] Among them, the method of the cloud platform pushing abnormal alarm notifications to the terminal of the user being shared with can effectively solve the problem of the user not being able to receive timely notifications when encountering abnormal situations while using the vehicle, which may lead to vehicle use problems or accidents.

[0109] Furthermore, when the abnormal alarm notification indicates a major accident such as a traffic accident, the cloud platform can determine the information of the current user of the target vehicle and send rescue information to the rescue center based on the abnormal alarm notification. This rescue information may include the current location of the target vehicle and the information of the current user; the rescue center can be, for example, 110 and / or 120.

[0110] The following will combine Figure 3 The vehicle sharing method in this application embodiment will be further explained and illustrated.

[0111] Figure 3This is a schematic flowchart illustrating another vehicle-sharing method provided in an embodiment of this application. Figure 3 As shown, the recipient's terminal first registers and logs in, and the cloud platform records the new user. When the car owner shares the target vehicle with the recipient, the car owner's terminal sends a verification information generation request for the first account to the cloud platform. The cloud platform generates verification information based on the request and sends the generated verification information to the recipient's terminal, enabling the recipient's terminal to send the generated verification information back to the car owner's terminal. The car owner's terminal then sends the received verification information to the cloud platform, which verifies the first account based on the received verification information and the previously generated verification information. If the first account is successfully verified, the recipient's terminal is granted permission to operate the target vehicle. In other words, the car owner can set the permissions for the recipient's terminal to operate the target vehicle on their own terminal. After successful sharing, both the car owner's terminal and the recipient's terminal receive a sharing success notification.

[0112] When the user's terminal operates the target vehicle, the user's terminal first logs into the first account and controls the functions of the target vehicle, that is, sends operation instructions for the target functions to the cloud platform. The cloud platform records the user's terminal usage history and sends the operation instructions to the target vehicle so that the TBOX in the target vehicle responds to the operation instructions to control the actual vehicle.

[0113] Furthermore, the vehicle owner's terminal can send control commands regarding permissions to the cloud platform. These commands include any one or a combination of the following: permission modification commands, permission deactivation commands, and commands to set the duration of permission validity. The cloud platform controls the permissions of the shared terminal to operate the target vehicle based on these control commands. Upon successful operation, both the vehicle owner's terminal and the shared terminal receive a success notification.

[0114] In addition, car owners can also view their full operation history on their vehicle's terminal. The vehicle owner's terminal sends a first query command to the cloud platform, which then queries the records of operations performed on the target vehicle based on the first query command, obtains the first query result, and sends the first query result back to the vehicle owner's terminal. The shared user can view their personal operation history on their terminal. The shared user's terminal sends a second query command to the cloud platform, which then queries the records of operations performed on the target vehicle based on the second query command, obtains the second query result, and sends the second query result back to the shared user's terminal.

[0115] In addition, when the target vehicle detects an abnormal alarm, it can send the abnormal alarm notification to the cloud platform, so that the cloud platform can push the abnormal alarm notification to the terminal of the person being shared with and / or the terminal of the vehicle owner.

[0116] In summary, this embodiment verifies the account logged into the user's terminal. Upon successful verification, the user's terminal can operate the target vehicle. This means the embodiment enables vehicle sharing, fulfilling the desire of families and friends to conveniently share vehicles. Furthermore, the added verification method prevents accidental sharing of vehicle operation permissions to other accounts, improving vehicle sharing security. Additionally, the cloud platform pushes anomaly alerts to the user's terminal, effectively resolving issues or accidents caused by the user not receiving timely notifications of abnormal situations.

[0117] Figure 4 This is a schematic diagram of the structure of a vehicle sharing device provided in an embodiment of this application.

[0118] For example, such as Figure 4 As shown, the device 400 includes:

[0119] The first receiving module 401 is used to receive the verification information of the first account sent by the vehicle owner terminal. The first account is the account logged in by the shared terminal, and the vehicle owner terminal is the terminal logged in to the second account.

[0120] Verification module 402 is used to verify the first account based on the received verification information;

[0121] The permission granting module 403 is used to grant the terminal of the shared user permission to operate the target vehicle, which is the vehicle bound to the second account, after the first account has been verified.

[0122] Optionally, the device 400 further includes:

[0123] The first sending module is used to receive a verification information generation request for the first account sent by the vehicle owner terminal, generate verification information, and send the generated verification information to the shared terminal so that the shared terminal sends the generated verification information to the vehicle owner terminal.

[0124] Verification module 402 is used for:

[0125] Compare the received verification information with the generated verification information;

[0126] Verify the first account based on whether the received verification information and the generated verification information are consistent.

[0127] Optionally, the permission granting module 403 is used for:

[0128] Obtain permission setting instructions from the vehicle owner's terminal for multiple functions in the target vehicle;

[0129] Based on the permission setting instructions, determine the target function, which is a function that the recipient's terminal has permission to use;

[0130] Grant the user's terminal permission to operate the target function in the target vehicle.

[0131] Optionally, the device 400 further includes:

[0132] The second receiving module is used to receive operation instructions for the target function sent by the terminal of the recipient;

[0133] The second sending module is used to send operation commands to the target vehicle so that the target vehicle can respond to the operation commands.

[0134] Optionally, the device 400 further includes:

[0135] The third receiving module is used to receive control instructions for permissions sent by the vehicle owner terminal. The control instructions include any one or a combination of the following: permission modification instructions, permission deactivation instructions, and instructions for setting the validity period of permissions.

[0136] The control module is used to control the access rights of the user's terminal to operate the target vehicle according to control commands.

[0137] Optionally, the device 400 further includes:

[0138] The fourth receiving module is used to receive abnormal alarm notifications sent by the target vehicle;

[0139] The push module is used to push abnormal alarm notifications to the terminals of the recipients and / or the vehicle owner's terminals.

[0140] Optionally, the device 400 further includes:

[0141] The first query module is used to query the records of the target vehicle being operated on according to the first query instruction when it receives the first query instruction sent by the vehicle owner terminal, obtain the first query result, and send the first query result to the vehicle owner terminal.

[0142] The second query module is used to query the records of the target vehicle operated by the shared terminal according to the second query instruction when it receives the second query instruction sent by the shared terminal, obtain the second query result, and send the second query result to the shared terminal.

[0143] This application embodiment verifies the account logged into the shared user's terminal. Upon successful verification, the shared user's terminal can operate the target vehicle. In other words, this application embodiment enables vehicle sharing, fulfilling the desire of family users and friends to conveniently share vehicles in daily life. Furthermore, this application embodiment adds a verification method to prevent the accidental sharing of operating permissions for the target vehicle to other accounts, improving the security of vehicle sharing. In addition, the cloud platform pushes abnormal alarm notifications to the shared user's terminal, effectively solving the problem of users not receiving timely notifications of abnormal situations while using the vehicle, thus preventing vehicle-related problems or accidents.

[0144] Figure 5 This is a schematic diagram of the structure of a vehicle provided in an embodiment of this application.

[0145] For example, such as Figure 5 As shown, the vehicle 500 includes a memory 501 and a processor 502. The memory 501 stores executable program code 5011, and the processor 502 is used to call and execute the executable program code 5011 to perform a vehicle sharing method.

[0146] This embodiment can divide the vehicle into functional modules according to the above method example. For example, each function can be assigned to a separate module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0147] When each functional module is divided according to its corresponding function, the vehicle may include: a first receiving module, a verification module, and a permission granting module, etc. It should be noted that all relevant content of each step involved in the above method embodiments can be referenced from the functional descriptions of the corresponding functional modules, and will not be repeated here.

[0148] The vehicle provided in this embodiment is used to execute the vehicle sharing method described above, and thus can achieve the same effect as the above implementation method.

[0149] When using integrated units, the vehicle may include a processing module and a storage module. The processing module is used to control and manage the vehicle's actions. The storage module supports the vehicle in executing program code and data.

[0150] The processing module may be a processor or a controller, which can implement or execute various exemplary logic blocks, modules, and circuits as disclosed in this application. The processor may also be a combination of computing functions, such as a combination of one or more microprocessors, a combination of digital signal processing (DSP) and microprocessors, etc., and the storage module may be a memory.

[0151] This embodiment also provides a computer-readable storage medium storing computer program code. When the computer program code is run on a computer, the computer executes the above-described related method steps to implement a vehicle sharing method in the above embodiment.

[0152] This embodiment also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned steps to implement a vehicle sharing method as described in the above embodiment.

[0153] In addition, the vehicle provided in the embodiments of this application may include a connected processor and a memory; wherein the memory is used to store instructions, and when the vehicle is running, the processor may call and execute the instructions to make the vehicle perform a vehicle sharing method in the above embodiments.

[0154] In this embodiment, the vehicle, computer-readable storage medium, computer program product, or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0155] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0156] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0157] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A vehicle-sharing method, characterized in that, Applied to a cloud platform, the method includes: The system receives verification information for a first account sent by the vehicle owner's terminal. The first account is the account logged into by the shared user's terminal, and the vehicle owner's terminal is the terminal logged into the second account. Verify the first account based on the received verification information; If the first account is verified, the user's terminal is granted permission to operate the target vehicle, which is the vehicle bound to the second account. Before receiving the verification information sent by the vehicle owner's terminal, the method further includes: The system receives a verification information generation request for the first account sent by the vehicle owner's terminal, generates verification information, and sends the generated verification information to the shared user's terminal, so that the shared user's terminal sends the generated verification information to the vehicle owner's terminal. The step of verifying the first account based on the received verification information includes: The received verification information and the generated verification information are compared; The first account is verified based on whether the received verification information and the generated verification information are consistent.

2. The method according to claim 1, characterized in that, Granting the user's terminal permission to operate the target vehicle includes: Obtain permission setting instructions from the vehicle owner's terminal for multiple functions in the target vehicle; Based on the permission setting instructions, the target function is determined, and the target function is the function that the user's terminal has permission to use; Grant the user's terminal permission to operate the target function in the target vehicle.

3. The method according to claim 2, characterized in that, After granting the user's terminal permission to operate the target vehicle, the method further includes: Receive operation instructions for the target function sent by the terminal of the user being shared with; The operation command is sent to the target vehicle so that the target vehicle responds to the operation command.

4. The method according to claim 1 or 2, characterized in that, After granting the user's terminal permission to operate the target vehicle, the method further includes: The system receives control commands for the permissions sent by the vehicle owner terminal. The control commands include any one or a combination of the following: permission modification command, permission deactivation command, and permission validity period setting command. According to the control instructions, the permissions of the shared user's terminal to operate the target vehicle are controlled.

5. The method according to claim 1 or 2, characterized in that, After granting the user's terminal permission to operate the target vehicle, the method further includes: Receive abnormal alarm notifications sent by the target vehicle; The abnormal alarm notification will be pushed to the terminal of the person being shared with and / or the terminal of the vehicle owner.

6. The method according to claim 1 or 2, characterized in that, After granting the user's terminal permission to operate the target vehicle, the method further includes: When a first query instruction is received from the vehicle owner terminal, the system queries the records of the target vehicle being operated on according to the first query instruction, obtains a first query result, and sends the first query result to the vehicle owner terminal. When a second query instruction is received from the shared user's terminal, the system queries the records of the shared user's terminal operating the target vehicle according to the second query instruction, obtains a second query result, and sends the second query result to the shared user's terminal.

7. A vehicle-sharing device, characterized in that, The device includes: The first receiving module is used to receive verification information of the first account sent by the vehicle owner terminal, wherein the first account is the account logged in by the shared user terminal, and the vehicle owner terminal is the terminal logged in to the second account; The verification module is used to verify the first account based on the received verification information; The permission granting module is used to grant the terminal of the person being shared permission to operate the target vehicle, which is the vehicle bound to the second account, when the first account is verified. The first sending module is used to receive a verification information generation request for the first account sent by the vehicle owner terminal, generate verification information, and send the generated verification information to the shared user terminal, so that the shared user terminal sends the generated verification information to the vehicle owner terminal. The verification module is further configured to compare the received verification information with the generated verification information; and verify the first account based on whether the received verification information and the generated verification information are consistent.

8. A vehicle, characterized in that, The vehicles include: Memory, used to store executable program code; A processor for calling and running the executable program code from the memory, causing the vehicle to perform the method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed, implements the method as described in any one of claims 1 to 6.

Images