Method for carrying out personalized vehicle setting for driver and related device
Through the client, the target vehicle is detected and personalized setting information is obtained from the Internet of Vehicles platform, and the vehicle settings are automatically adjusted, which solves the problem of drivers needing to frequently adjust vehicle settings, improving driving experience and safety.
Patent Information
- Application Number
- CN202411415817.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-11
- Publication Date
- 2024-12-31
AI Technical Summary
In commercial vehicle usage scenarios, vehicle setting parameters (such as seat height, steering wheel, etc.) between drivers need to be adjusted frequently, resulting in cumbersome operation and reducing driving experience and safety.
The client detects the distance of the target vehicle, sends the vehicle usage application, obtains personalized vehicle setting information from the Internet of Vehicles platform, and automatically adjusts the vehicle settings to achieve the binding of the driver's account and vehicle setting information, ensuring that it can be used every time it is used Get the correct settings quickly.
It simplifies the vehicle setting adjustment process, improves the driver's driving experience and safety, and ensures that no matter which car you use, you can set up your personalized settings quickly and accurately.
Smart Images
Figure CN119232474A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of new energy vehicle technology, specifically to technical fields such as intelligent driving and data sharing, and in particular to a method and related devices for personalized vehicle settings for drivers. Background Art
[0002] At present, in the daily use of commercial vehicles, multiple drivers often drive the same vehicle for actual operation, and because the number of vehicles in the fleet is uncertain, each driver may use a different vehicle each time. However, due to the differences in height, weight, driving habits, etc. of each driver, the driver must manually adjust the relevant vehicle setting parameters (such as seat height, steering wheel, rearview mirror, etc.) after changing vehicles. The cumbersome adjustment operation brings inconvenience to the driver and reduces the driver's driving experience and safety. Summary of the invention
[0003] The present application provides a method and related devices for performing personalized vehicle settings for a driver, so as to solve the problems of cumbersomeness, inconvenience and poor driving experience caused by the existing manual adjustment of vehicle settings.
[0004] The technical solution is as follows:
[0005] In a first aspect, a method for personalizing vehicle settings for a driver is provided, comprising:
[0006] The first client with the driver account is logged in to detect whether the distance of the nearest target vehicle that is not in operation is less than a set threshold;
[0007] If yes, the first client sends a vehicle use application to the second client logged in with the fleet account through the driver account;
[0008] After obtaining the right to use the target vehicle, the first client obtains the personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform through the driver account, and sends it to the corresponding controller of the target vehicle to adjust the personalized vehicle setting; wherein the Internet of Vehicles platform stores multiple: binding relationships between driver accounts and personalized vehicle setting information;
[0009] After the personalized vehicle settings are completed, the first client feeds back the setting results to the Internet of Vehicles platform through the driver account.
[0010] In a possible implementation, the binding relationship between the driver account and the personalized vehicle setting information is determined in the following manner:
[0011] Log in to the second client with the fleet account, determine the driver account to be bound and multiple vehicles involved in the operation in the fleet; wherein the multiple vehicles include at least one model;
[0012] Based on the prompt of the second client with the fleet account logged in, the driver account to be bound is logged in on the vehicles corresponding to the different models, and based on the vehicle terminal logged in to the driver account to be bound, the personalized vehicle setting information of the driver corresponding to the driver account to be bound when operating the vehicles corresponding to the different models is collected, wherein the personalized vehicle setting information includes: signal data related to the whole vehicle control;
[0013] The vehicle terminal binds the collected personalized vehicle setting information, vehicle model and the driver account to be bound logged in by the vehicle terminal, and uploads them to the Internet of Vehicles platform for storage.
[0014] In a possible implementation, a driver account in the Internet of Vehicles platform is bound to personalized vehicle setting information corresponding to multiple different vehicle models;
[0015] The first client obtains the personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform through the driver account, and sends it to the corresponding controller of the target vehicle to adjust the personalized vehicle setting, specifically including:
[0016] The first client obtains the model of the target vehicle through the driver account; obtains personalized vehicle setting information bound to the driver account and corresponding to the model from the Internet of Vehicles platform, and sends it to the corresponding controller of the target vehicle to adjust the personalized vehicle settings.
[0017] In a possible implementation, the first client is a mobile terminal used by a driver, and a communication link is established between the mobile terminal and the target vehicle;
[0018] The first client obtains the personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform through the driver account, and sends it to the corresponding controller of the target vehicle to adjust the personalized vehicle setting, specifically including:
[0019] The mobile terminal obtains personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform through the driver account;
[0020] The mobile terminal sends the personalized vehicle setting information to the vehicle-mounted terminal of the target vehicle through the communication link;
[0021] The vehicle-mounted terminal forwards the personalized vehicle setting information to a corresponding controller of the target vehicle to adjust the personalized vehicle setting.
[0022] In a possible implementation, the method further includes:
[0023] The first client logged in with the driver account obtains personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform;
[0024] The first client performs one or a combination of viewing, adding, deleting, modifying and viewing the personalized vehicle setting information in response to the driver's input operation.
[0025] In a second aspect, a system for personalized vehicle settings for a driver is provided, the system comprising: a first client, a second client, a vehicle networking platform and a target vehicle; wherein:
[0026] The first client with the driver account is logged in to detect whether the distance of the nearest target vehicle that is not in operation is less than a set threshold;
[0027] If yes, the first client sends a vehicle use application to the second client logged in with the fleet account through the driver account;
[0028] After obtaining the right to use the target vehicle, the first client obtains the personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform through the driver account, and sends it to the corresponding controller of the target vehicle to adjust the personalized vehicle setting; wherein the Internet of Vehicles platform stores multiple: binding relationships between driver accounts and personalized vehicle setting information;
[0029] After the personalized vehicle settings are completed, the first client feeds back the setting results to the Internet of Vehicles platform through the driver account.
[0030] In a third aspect, a computer-readable storage medium is provided, wherein at least one instruction is stored in the storage medium, and the at least one instruction is loaded and executed by a processor to implement the method of the above-mentioned aspect and any possible implementation manner.
[0031] In a fourth aspect, an electronic device is provided, including:
[0032] at least one processor; and
[0033] a memory communicatively connected to the at least one processor; wherein,
[0034] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method of any possible implementation manner and the aspects described above.
[0035] According to a fifth aspect, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the above-mentioned aspects and any possible implementation method.
[0036] In a sixth aspect, a new energy commercial vehicle is provided, comprising the electronic device as described above.
[0037] The beneficial effects of the technical solution provided by this application include at least:
[0038] It can be seen from the above technical solution that the first client detects whether the distance of the target vehicle closest to it and in a non-operating state is less than the set threshold. If so, the first client sends a vehicle use application to the second client logged in with the fleet account through the driver account; after obtaining the right to use the target vehicle, the first client obtains the personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform through the driver account, and sends it to the corresponding controller of the target vehicle for personalized vehicle setting adjustment; after the personalized vehicle setting is completed, the first client feeds back the setting result to the Internet of Vehicles platform through the driver account. Thus, through the binding relationship between the driver account and the personalized vehicle setting information, it is ensured that no matter which vehicle in the fleet the driver uses, he can quickly and accurately obtain the binding relationship from the Internet of Vehicles platform, and adjust the personalized vehicle settings based on the personalized vehicle setting information corresponding to the vehicle in the binding relationship; simplify the adjustment operation, and improve driving safety and experience.
[0039] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0040] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0041] Figure 1 It is a schematic diagram of the method steps for performing personalized vehicle settings for a driver provided in an embodiment of the present application.
[0042] Figure 2 It is a block diagram of the personalized vehicle setting architecture provided in an embodiment of the present application.
[0043] Figure 3 It is a schematic diagram of the method steps for performing personalized vehicle settings for a driver provided in yet another embodiment of the present application.
[0044] Figure 4 This is a block diagram of a system structure for providing personalized vehicle settings for a driver, provided in yet another embodiment of the present application.
[0045] Figure 5 It is a block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION
[0046] The following is a description of exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description.
[0047] Obviously, the described embodiments are only part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.
[0048] It should be noted that the terminal devices involved in the embodiments of the present application may include but are not limited to mobile phones, personal digital assistants (PDAs), wireless handheld devices, tablet computers and other smart devices; display devices may include but are not limited to personal computers, televisions and other devices with display functions.
[0049] In addition, the term "and / or" in this article is only a description of the association relationship between the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.
[0050] In the current commercial vehicle field, it is often the case that a fleet or a company's vehicles are assigned to different drivers to perform transportation operations. After changing vehicles, drivers often need to manually adjust the seat height, steering wheel, rearview mirror and other related vehicle setting parameters. The cumbersome adjustment operation brings inconvenience to the driver and reduces the driver's driving experience and safety.
[0051] In view of this, the present application proposes a solution for personalized vehicle settings for drivers, and the inventive concept is that: the first client detects whether the distance of the target vehicle closest to it and in a non-operating state is less than a set threshold. If so, the first client sends a vehicle use application to the second client logged in with a fleet account through the driver account; after obtaining the right to use the target vehicle, the first client obtains the personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform through the driver account, and sends it to the corresponding controller of the target vehicle for personalized vehicle setting adjustment; after the personalized vehicle setting is completed, the first client feeds back the setting result to the Internet of Vehicles platform through the driver account. Thus, through the binding relationship between the driver account and the personalized vehicle setting information, it is ensured that the driver can quickly and accurately obtain the binding relationship from the Internet of Vehicles platform no matter which vehicle in the fleet he uses, and make personalized vehicle setting adjustments based on the personalized vehicle setting information corresponding to the vehicle in the binding relationship; simplifying the adjustment operation and improving driving safety and experience.
[0052] Reference Figure 1 , which is a schematic diagram of the method steps for providing personalized vehicle settings for a driver provided in an embodiment of the present application. The method may include the following steps:
[0053] Step 102: Log in to the first client with the driver account and detect whether the distance to the nearest target vehicle that is not in operation is less than a set threshold.
[0054] In the present application scheme, the first client can be a driver-side APP used by the driver, which can be installed on a mobile terminal (such as a mobile phone, PAD and other terminal devices), or a vehicle-mounted terminal (such as TBOX, etc.) that can communicate on the target vehicle that the driver is about to drive. When the driver enters the target vehicle, the driver-side APP installed on the mobile terminal can be used to log in to the driver account, and then the target vehicle is identified and detected based on the logged-in driver account, and the target vehicle is identified by obtaining the device identification of the target vehicle, and the distance of the target vehicle from the mobile terminal (i.e., the driver's location) is detected according to the radar positioning. If the target vehicle is detected to be in a non-operating state (which can be determined based on the acquired vehicle state), and the detected distance is less than the set threshold, it can be determined that the driver is on the target vehicle. If the target vehicle is detected to be in a non-operating state but the distance from the mobile terminal is greater than or equal to the set threshold; or, the distance from the mobile terminal to the target vehicle is detected to be less than the set threshold, but the target vehicle is in an operating state, it can be determined that although the driver is on the target vehicle, the target vehicle is unavailable. Similarly, after the driver logs in to the driver account based on the driver-side APP installed on the vehicle terminal of the target vehicle, the target vehicle can be identified and detected in a similar manner. In this case, if the distance between the target vehicle and the driver is less than the set threshold and the target vehicle is not in operation, it can be determined that the driver is in the target vehicle. Since the solution of logging in using the vehicle terminal must log in to the driver account on the vehicle terminal of the target vehicle, it is generally not the case that the target vehicle is in operation.
[0055] In the present application, the set threshold may be an empirical value obtained based on repeated experiments, for example, any value within a range of about 10 meters may be selected.
[0056] Step 104: If yes, the first client sends a vehicle use application to the second client logged in with the fleet account through the driver account.
[0057] Based on the result of step 102, if it is determined that the target vehicle is not in operation and the detected distance is less than the set threshold, the first client determines that the target vehicle is available and the driver is on the target vehicle. Then, the first client sends a vehicle use application to the second client logged in with the fleet account through the currently logged in driver account.
[0058] Considering that the vehicles in the fleet can be shared, in order to avoid assigning the same vehicle to different drivers at the same time, a status value can be set for each vehicle, where a status value of 1 means it is unassigned and available, and a status value of 0 means it is assigned and unavailable. All vehicles in the fleet are managed by the fleet account, and the vehicle information and status of all vehicles in the fleet can be stored under the fleet account or in the cloud accessible by the fleet account.
[0059] The first client sends a vehicle use application to the second client logged in with the fleet account through the driver account. The vehicle use application carries the device identification and other information of the target vehicle. The second client checks the status value of the target vehicle corresponding to the device identification according to the received vehicle use application, and issues the use right of the target vehicle to the first client when the status value is 1. At the same time, the assigned driver information is recorded in the vehicle information of the target vehicle, and its status value is modified to 0. In this way, it is ensured that the target vehicle cannot be repeatedly assigned to other drivers during the time the current driver uses it.
[0060] Step 106: After obtaining the right to use the target vehicle, the first client obtains the personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform through the driver account, and sends it to the corresponding controller of the target vehicle to adjust the personalized vehicle settings; wherein the Internet of Vehicles platform saves multiple binding relationships between driver accounts and personalized vehicle setting information.
[0061] In the present application, the binding relationship between the driver account and the personalized vehicle setting information is determined in the following manner:
[0062] First, log in to the second client with the fleet account, determine the driver account to be bound and multiple vehicles involved in the operation in the fleet; wherein the multiple vehicles include at least one model.
[0063] It should be understood that the fleet account can not only manage vehicle information, but also manage driver accounts at the same time. Therefore, after the fleet account logs in for the first time, it can count all driver accounts in the fleet by registering a driver account or actively adding a fleet account. Similarly, all vehicles in the fleet can be counted by registering or actively adding a fleet account.
[0064] Then, based on the prompt of the second client logged in with the fleet account, the driver account to be bound is logged in on the vehicles corresponding to the different models, and based on the vehicle terminal logged in to the driver account to be bound, the personalized vehicle setting information of the driver corresponding to the driver account to be bound when operating the vehicles corresponding to the different models is collected, wherein the personalized vehicle setting information includes: signal data related to the control of the whole vehicle.
[0065] After the second client determines the driver account to be bound and the multiple vehicles involved in the operation in the fleet under the fleet account, it can remind the driver online or offline to log in their respective driver accounts on the vehicles corresponding to different models, that is, log in to the driver account through the vehicle terminal. Afterwards, the vehicle terminal collects the personalized vehicle setting information of the corresponding driver when operating the vehicles corresponding to different models based on the logged-in driver account. For example, after the driver logs in to the driver account through the vehicle's vehicle terminal, he can adjust the seat position, steering wheel angle and position, speaker volume, and instrument panel display format through manual control, and these control contents can be collected by the vehicle terminal.
[0066] The multiple vehicles in the fleet can be of the same model or multiple models. If there is only one model in the fleet, each driver only needs to log in to the driver account on any vehicle to perform personalized control, and the vehicle terminal obtains the vehicle setting information for personalized control. If there are multiple models in the fleet, each driver needs to log in to the driver account on any vehicle of each model to perform personalized control, and the vehicle terminal obtains the vehicle setting information for the driver to perform personalized control on any vehicle of each model.
[0067] Finally, the vehicle terminal binds the collected personalized vehicle setting information, vehicle model and the driver account to be bound logged in by the vehicle terminal, and uploads it to the Internet of Vehicles platform for storage.
[0068] When the fleet contains only one model, that is, all vehicles belong to the same model, then each driver account can be bound to a set of personalized vehicle settings information, which may include: seat position, steering wheel angle, steering wheel position, audio volume, instrument panel display format, etc. When the fleet contains multiple models, each driver account can be bound to multiple sets of personalized vehicle settings information. For example, there are 100 vehicles in the fleet, with a total of 3 models, then driver account A-model 1-personalized vehicle settings information 1; driver account A-model 2-personalized vehicle settings information 2; driver account A-model 3-personalized vehicle settings information 3. Driver account B-model 1-personalized vehicle settings information 4; driver account B-vehicle 2-personalized vehicle settings information 5; driver account B-model 3-personalized vehicle settings information 6.
[0069] After the binding relationship is established, the vehicle terminal uploads the established binding relationship to the Internet of Vehicles platform for storage. In fact, it is not ruled out that the vehicle terminal also saves the binding relationship locally, so that the Internet of Vehicles platform can avoid being unable to access the driver's personalized setting information in time due to busy business, thereby improving processing flexibility.
[0070] It should be noted that the method of determining the above-mentioned binding relationship is not limited to the first login of the fleet account, that is, the first establishment of a binding relationship for the driver account. It can also be based on the established binding relationship to establish a binding relationship for a new driver account, or to add a binding relationship to a driver account that has already established a binding relationship.
[0071] Optionally, a driver account in the Internet of Vehicles platform is bound to personalized vehicle setting information corresponding to multiple different vehicle models; then, when the first client obtains the personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform through the driver account, and sends it to the corresponding controller of the target vehicle for personalized vehicle setting adjustment, the first client can obtain the model of the target vehicle through the driver account; obtain the personalized vehicle setting information bound to the driver account and corresponding to the model from the Internet of Vehicles platform, and send it to the corresponding controller of the target vehicle for personalized vehicle setting adjustment.
[0072] Optionally, the first client is a mobile terminal used by the driver, and a communication link is established between the mobile terminal and the target vehicle; the mobile terminal obtains personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform through the driver account; the mobile terminal sends the personalized vehicle setting information to the on-board terminal of the target vehicle through the communication link; the on-board terminal forwards the personalized vehicle setting information to the corresponding controller of the target vehicle to adjust the personalized vehicle settings.
[0073] In fact, when the first client is the on-board terminal of the target vehicle, the driver account can be logged in on the on-board terminal, and personalized vehicle setting information bound to the driver account can be obtained from the Internet of Vehicles platform. After that, the on-board terminal forwards the personalized vehicle setting information to the corresponding controller of the target vehicle for personalized vehicle setting adjustment.
[0074] Step 108: After the personalized vehicle settings are completed, the first client feeds back the setting results to the Internet of Vehicles platform through the driver account.
[0075] After completing the personalized vehicle setting adjustment for the corresponding controller of the target vehicle through the driver account, the vehicle terminal feeds back the setting result to the Internet of Vehicles platform through the driver account, or the vehicle terminal sends the setting result to the driver's mobile terminal, and the mobile terminal feeds back the setting result to the Internet of Vehicles platform.
[0076] Optionally, in the present application, the first client logged in with the driver account obtains the personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform; the first client responds to the driver's input operation and performs one or a combination of operations of viewing, adding, deleting, modifying and viewing the personalized vehicle setting information. Thus, convenient and efficient management of personalized vehicle setting information is improved.
[0077] By logging into the driver account through the vehicle, relevant information of the user's current settings (including but not limited to steering wheel height, seat height, volume, account related information, etc.) is collected and bound to the driver account logged in by the vehicle. An application can be automatically initiated by identifying that the distance between the vehicle and the device logged in by the driver account is less than a certain range. After the fleet account review is completed, the driver can log in to the driver account and send the settings to the corresponding vehicle. In this way, when the relevant vehicle is used by the driver, the driver can log in to the driver account through the car computer / mobile phone APP, quickly obtain the relevant information of the personalized settings under the corresponding driver account, and send it to the current vehicle for setting. Thereby, the convenience and efficiency of settings are improved, and the driving experience and safety of driver users are improved.
[0078] Figure 2 As shown, it is a block diagram of the personalized vehicle setting architecture provided in an embodiment of the present application, including mobile phone APP (fleet side (with fleet account logged in by default), driver side (with driver account logged in by default)), Internet of Vehicles backend, vehicle data collection terminal, vehicle controller, etc. Among them, mobile phone APP (fleet side, driver side): customer mobile phone APP software, after logging in to the APP through the account, different functions are displayed according to different roles, or they can be two independent APPs. Internet of Vehicles backend: SAAS service deployed based on the server. Vehicle data collection terminal: equipment for vehicle data collection, generally TBOX or CCU, etc. Vehicle controller: such as seat controller, body controller, vehicle-mounted MP5, audio and video entertainment, etc.
[0079] Reference Figure 3 As shown, based on the above Figure 2 The following method steps can be performed:
[0080] Step 302: The vehicle data acquisition terminal acquires vehicle controller related signal data via the CAN bus.
[0081] This includes but is not limited to steering wheel height, seat height, volume, account-related information, etc.
[0082] Step 304: The vehicle data collection terminal obtains common settings of the vehicle-mounted MP5 through WIFI, hard-wired signals or CAN.
[0083] Among them, the commonly used MP5 settings may include the default volume level, navigation volume level, etc.
[0084] Step 306: The vehicle-mounted data terminal uploads all collected data to the Internet of Vehicles backend.
[0085] Step 308: The driver APP can be matched with any vehicle in the fleet through positioning. If the current distance between the driver and the vehicle is less than 10m and the vehicle is not in operation, a vehicle use application will be automatically sent to the fleet APP.
[0086] Step 310: After approval by the fleet APP, the driver APP account obtains the right to use the corresponding vehicle.
[0087] Step 312: The Internet of Vehicles platform can select the personalized settings under the driver's APP account for distribution.
[0088] Step 314: After receiving the personalized data synchronized by the Internet of Vehicles background, the vehicle data collection terminal forwards the data to the corresponding controller for corresponding adjustment and execution.
[0089] Step 316: After receiving the response results from all controllers, the vehicle data collection terminal feeds back to the Internet of Vehicles backend.
[0090] Step 318: The driver APP displays the results accordingly.
[0091] In addition, the Internet of Vehicles background will synchronize the personalized data of the corresponding vehicle to the driver's APP account currently bound to the vehicle. The driver can view the personalized settings and details under the current account by logging into the APP, and supports related functions such as saving, adding, deleting, and sending. When the driver APP logs in for the first time, a text prompt will appear. If the current vehicle has not obtained the owner's personalized settings, the relevant settings can be made through the mobile phone APP or MP5.
[0092] This will enable interoperability of vehicle accounts within the fleet, enabling the driver to quickly change and connect personalized settings after changing vehicles, ensuring operational efficiency and improving safety and comfort.
[0093] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.
[0094] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
[0095] Figure 4 FIG. 1 shows a structural block diagram of a system for providing personalized vehicle settings for a driver according to an embodiment of the present application. Figure 4 As shown. The system 400 for setting personalized vehicles for drivers in this embodiment may include a first client 401, a second client 402, a vehicle networking platform 403, and a target vehicle 404. The first client 401 logged in with a driver account detects whether the distance of the target vehicle 404 closest to it and in a non-operating state is less than a set threshold; if so, the first client 401 sends a vehicle use application to the second client 402 logged in with a fleet account through the driver account; after obtaining the right to use the target vehicle 404, the first client 401 obtains the personalized vehicle setting information bound to the driver account from the vehicle networking platform 403 through the driver account, and sends it to the corresponding controller of the target vehicle 404 for personalized vehicle setting adjustment; wherein the vehicle networking platform 403 stores multiple: binding relationships between driver accounts and personalized vehicle setting information; after the personalized vehicle setting is completed, the first client 401 feeds back the setting result to the vehicle networking platform 403 through the driver account.
[0096] It should be noted that part or all of the system for personalized vehicle settings for drivers in this embodiment may be an application located in the local terminal of the target vehicle, or may also be a functional unit such as a plug-in or software development kit (SDK) set in the application located in the local terminal, or may also be a processing engine located in a network-side server, or may also be a distributed system located on the network side, for example, a processing engine or distributed system in a vehicle networking platform on the network side, etc. This embodiment does not specifically limit this.
[0097] It is understandable that the application may be a native program (nativeApp) installed on the local terminal of the vehicle, or may be a web page program (webApp) of a browser on the local terminal of the vehicle, which is not limited in this embodiment.
[0098] Optionally, in a possible implementation of this embodiment, the binding relationship between the driver account and the personalized vehicle setting information is determined in the following manner:
[0099] The second client 402 with a fleet account is logged in to determine the driver account to be bound and multiple vehicles involved in the operation in the fleet; wherein the multiple vehicles include at least one model; based on the prompt of the second client 402 with a fleet account, the driver account to be bound is logged in on the vehicles corresponding to different models, and based on the vehicle terminal logged in to the driver account to be bound, the personalized vehicle setting information of the driver corresponding to the driver account to be bound when operating the vehicles corresponding to different models is collected, wherein the personalized vehicle setting information includes: signal data related to vehicle control; the vehicle terminal binds the collected personalized vehicle setting information, the model and the driver account to be bound logged in by the vehicle terminal, and uploads them to the Internet of Vehicles platform 403 for storage.
[0100] Optionally, in a possible implementation of this embodiment, a driver account in the Internet of Vehicles platform is bound to personalized vehicle setting information corresponding to multiple different vehicle models;
[0101] When the first client 401 obtains the personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform 403 through the driver account, and sends it to the corresponding controller of the target vehicle 404 for personalized vehicle setting adjustment, it is specifically used to: obtain the model of the target vehicle through the driver account; obtain the personalized vehicle setting information bound to the driver account and corresponding to the model from the Internet of Vehicles platform 403, and send it to the corresponding controller of the target vehicle 404 for personalized vehicle setting adjustment.
[0102] Optionally, in a possible implementation of this embodiment, the first client 401 is a mobile terminal used by a driver, and a communication link is established between the mobile terminal and the target vehicle 404;
[0103] When the first client 401 obtains the personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform 403 through the driver account, and sends it to the corresponding controller of the target vehicle 404 for personalized vehicle setting adjustment, it is specifically used for: the mobile terminal obtains the personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform 403 through the driver account; the mobile terminal sends the personalized vehicle setting information to the on-board terminal of the target vehicle 404 through the communication link; the on-board terminal forwards the personalized vehicle setting information to the corresponding controller of the target vehicle 404 for personalized vehicle setting adjustment.
[0104] Optionally, in a possible implementation of this embodiment, the first client 401 is further used to:
[0105] The personalized vehicle setting information bound to the driver account is obtained from the Internet of Vehicles platform 403; in response to the driver's input operation, one or a combination of viewing, adding, deleting, modifying and viewing the personalized vehicle setting information is performed.
[0106] In this embodiment, the first client detects whether the distance of the target vehicle that is closest to it and is not in operation is less than a set threshold. If so, the first client sends a vehicle use application to the second client logged in with the fleet account through the driver account; after obtaining the right to use the target vehicle, the first client obtains the personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform through the driver account, and sends it to the corresponding controller of the target vehicle for personalized vehicle setting adjustment; after the personalized vehicle setting is completed, the first client feeds back the setting result to the Internet of Vehicles platform through the driver account. Thus, through the binding relationship between the driver account and the personalized vehicle setting information, it is ensured that the driver can quickly and accurately obtain the binding relationship from the Internet of Vehicles platform no matter which vehicle of the fleet is used, and adjust the personalized vehicle setting based on the personalized vehicle setting information corresponding to the vehicle in the binding relationship; simplify the adjustment operation, and improve driving safety and experience.
[0107] An embodiment of the present application provides a computer-readable storage medium, wherein the storage medium stores at least one instruction, and the at least one instruction is loaded and executed by a processor to implement the method for performing personalized vehicle settings for a driver as described above.
[0108] An embodiment of the present application provides an electronic device, which includes a processor and a memory, wherein the memory stores at least one instruction, and the instruction is loaded and executed by the processor to implement the method for personalized vehicle settings for a driver as described above.
[0109] An embodiment of the present application provides a new energy commercial vehicle, including the electronic device as described above. Specifically, the new energy commercial vehicle can be a transport vehicle of level L2 or above, for example, a new energy truck.
[0110] In the technical solution of this application, the collection, storage, use, processing, transmission, provision and disclosure of user personal information involved are in compliance with the relevant laws and regulations and do not violate public order and good morals.
[0111] Figure 5A schematic block diagram of an example electronic device 500 that can be used to implement an embodiment of the present application is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or required herein.
[0112] like Figure 5 As shown, the electronic device 500 includes a computing unit 501, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 502 or a computer program loaded from a storage unit 508 into a random access memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the electronic device 500 can also be stored. The computing unit 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.
[0113] Multiple components in the electronic device 500 are connected to the I / O interface 505, including: an input unit 506, such as a keyboard, a mouse, etc.; an output unit 507, such as various types of displays, speakers, etc.; a storage unit 508, such as a disk, an optical disk, etc.; and a communication unit 509, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 509 allows the electronic device 500 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.
[0114] The computing unit 501 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 501 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 501 performs the various methods and processes described above, such as a method for setting up a personalized vehicle for a driver. For example, in some embodiments, the method for setting up a personalized vehicle for a driver may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 508. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 500 via the ROM 502 and / or the communication unit 509. When the computer program is loaded into the RAM 503 and executed by the computing unit 501, one or more steps of the method for setting up a personalized vehicle for a driver described above may be performed. Alternatively, in other embodiments, the computing unit 501 may be configured to execute the method for performing personalized vehicle settings for the driver in any other appropriate manner (eg, by means of firmware).
[0115] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.
[0116] The program code for implementing the method of the present application can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, implements the functions / operations specified in the flow chart and / or block diagram. The program code can be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.
[0117] In the context of the present application, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, 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 foregoing.
[0118] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).
[0119] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.
[0120] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship with each other. The server may be a cloud server, a server of a distributed system, or a server combined with a blockchain.
[0121] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution disclosed in this application can be achieved, and this document is not limited here.
[0122] The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application should be included in the protection scope of this application.
Claims
1. A method for personalizing vehicle settings for a driver, characterized in that: include: The first client with the driver account is logged in to detect whether the distance of the nearest target vehicle that is not in operation is less than a set threshold; If yes, the first client sends a vehicle use application to the second client logged in with the fleet account through the driver account; After obtaining the right to use the target vehicle, the first client obtains the personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform through the driver account, and sends it to the corresponding controller of the target vehicle to adjust the personalized vehicle setting; wherein the Internet of Vehicles platform stores multiple: binding relationships between driver accounts and personalized vehicle setting information; After the personalized vehicle settings are completed, the first client feeds back the setting results to the Internet of Vehicles platform through the driver account.
2. The method according to claim 1, characterized in that The binding relationship between the driver account and the personalized vehicle setting information is determined in the following manner: Log in to the second client with the fleet account, determine the driver account to be bound and multiple vehicles involved in the operation in the fleet; wherein the multiple vehicles include at least one model; Based on the prompt of the second client with the fleet account logged in, the driver account to be bound is logged in on the vehicles corresponding to the different models, and based on the vehicle terminal logged in to the driver account to be bound, the personalized vehicle setting information of the driver corresponding to the driver account to be bound when operating the vehicles corresponding to the different models is collected, wherein the personalized vehicle setting information includes: signal data related to the whole vehicle control; The vehicle terminal binds the collected personalized vehicle setting information, vehicle model and the driver account to be bound logged in by the vehicle terminal, and uploads them to the Internet of Vehicles platform for storage.
3. The method according to claim 2, characterized in that A driver account in the Internet of Vehicles platform is bound to personalized vehicle setting information corresponding to multiple different vehicle models; The first client obtains the personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform through the driver account, and sends it to the corresponding controller of the target vehicle to adjust the personalized vehicle setting, specifically including: The first client obtains the model of the target vehicle through the driver account; obtains personalized vehicle setting information bound to the driver account and corresponding to the model from the Internet of Vehicles platform, and sends it to the corresponding controller of the target vehicle to adjust the personalized vehicle settings.
4. The method according to any one of claims 1 to 3, characterized in that: The first client is a mobile terminal used by the driver, and a communication link is established between the mobile terminal and the target vehicle; The first client obtains the personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform through the driver account, and sends it to the corresponding controller of the target vehicle to adjust the personalized vehicle setting, specifically including: The mobile terminal obtains personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform through the driver account; The mobile terminal sends the personalized vehicle setting information to the vehicle-mounted terminal of the target vehicle through the communication link; The vehicle-mounted terminal forwards the personalized vehicle setting information to a corresponding controller of the target vehicle to adjust the personalized vehicle setting.
5. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: The first client logged in with the driver account obtains personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform; The first client performs one or a combination of viewing, adding, deleting, modifying and viewing the personalized vehicle setting information in response to the driver's input operation.
6. A system for personalizing vehicle settings for a driver, characterized in that: The system includes: a first client, a second client, a vehicle networking platform, and a target vehicle; wherein, The first client with the driver account is logged in to detect whether the distance of the nearest target vehicle that is not in operation is less than a set threshold; If yes, the first client sends a vehicle use application to the second client logged in with the fleet account through the driver account; After obtaining the right to use the target vehicle, the first client obtains the personalized vehicle setting information bound to the driver account from the Internet of Vehicles platform through the driver account, and sends it to the corresponding controller of the target vehicle to adjust the personalized vehicle setting; wherein the Internet of Vehicles platform stores multiple: binding relationships between driver accounts and personalized vehicle setting information; After the personalized vehicle settings are completed, the first client feeds back the setting results to the Internet of Vehicles platform through the driver account.
7. An electronic device comprising: at least one processor; as well as 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 to enable the at least one processor to perform the method according to any one of claims 1 to 5.
8. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to cause the computer to execute the method according to any one of claims 1-5.
9. A computer program product, comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 5.
10. A new energy commercial vehicle, comprising the electronic device as claimed in claim 7.