A vehicle pickup method and device, a vehicle pickup system, and an electronic device

Abstract

This application provides a vehicle pick-up method and apparatus, a vehicle pick-up system, and an electronic device. The vehicle pick-up method includes: determining the date type and date subtype of the current time information; obtaining predicted trip information based on the current time information using a trip prediction model corresponding to the date subtype; determining a corresponding trip push strategy based on the date type; sending the predicted trip information to a terminal based on the trip push strategy; the terminal confirming or adjusting the received predicted trip information and sending the final trip information to a server; receiving the final trip information sent by the terminal and sending a pick-up instruction carrying the final trip information to the vehicle; the trip information includes the pick-up time, pick-up location, and destination; the pick-up instruction instructs the vehicle to automatically drive to the final pick-up location before the final pick-up time and to automatically drive to the final destination after the pick-up is completed.

Description

Technical Field

[0001] This application relates to the field of autonomous driving technology, specifically to a vehicle pick-up method and device, a vehicle pick-up system, and electronic equipment. Background Technology

[0002] With the maturity of autonomous driving technology, more and more vehicles are equipped with the ability to automatically pick up passengers. In related technologies, predicted trip information is obtained through a trip prediction model. Users then confirm or adjust this predicted trip information via a mobile app, and finally use the confirmed or adjusted trip information to control the vehicle to initiate the automatic pick-up. However, this type of automatic pick-up method directly pushes predicted trip information to the user, resulting in low accuracy of the pushed trip information and failing to meet users' travel needs on different date types. Summary of the Invention

[0003] This application provides a vehicle pick-up method and device, a vehicle pick-up system, and an electronic device to improve the accuracy of trip information pushed to users.

[0004] To achieve the above objectives, the technical solution adopted in this application is as follows: In a first aspect, embodiments of this application provide a vehicle pick-up method applied to a server. The method includes: determining the date type and date subtypes of the current time information; obtaining predicted trip information based on the current time information using a trip prediction model corresponding to the date subtype; determining a corresponding trip push strategy based on the date type; sending a trip confirmation message carrying the predicted trip information to a terminal based on the trip push strategy; the terminal confirming or adjusting the received predicted trip information and sending a trip feedback message carrying the final trip information to the server; receiving the trip feedback message and sending a pick-up instruction carrying the final trip information to the vehicle; wherein the trip information includes the pick-up time, pick-up location, and destination; the pick-up instruction instructs the vehicle to automatically drive to the final pick-up location before the final pick-up time and to automatically drive to the final destination after the pick-up is completed.

[0005] The vehicle pick-up method provided in this application determines the date type and sub-date type of the current time information, inputs the current time information into a trip prediction model corresponding to the date sub-date type, and obtains predicted trip information. Since users' travel habits differ under different date sub-dates, the trip information obtained through the trip prediction model for a specific date sub-date is more accurate. Furthermore, by pushing the predicted trip information using a trip push strategy corresponding to the date type, the trip information pushed to the terminal is more in line with the user's car usage needs under different date types, thereby effectively improving the accuracy of trip information push.

[0006] In some embodiments, when the date type is a holiday, the trip push strategy is a holiday trip push strategy; when the time interval between the current time information and the predicted time of use is greater than or equal to a first time interval, if the predicted destination is the target historical destination, a trip confirmation message carrying the predicted trip information is sent to the terminal.

[0007] In this embodiment, by ensuring that the time interval between the current time and the pick-up time exceeds a set time interval, the terminal can receive the trip confirmation message in advance, allowing users to make sufficient preparations for holiday travel. Furthermore, the trip confirmation message is only sent to the terminal when the predicted destination is the target historical destination, thereby reducing interference from irrelevant information and improving the user experience.

[0008] In some embodiments, if the predicted destination is not the target historical destination, a recommended trip information is determined based on the vehicle's historical destination during holidays using a trip recommendation model; a trip confirmation message carrying the recommended trip information is sent to the terminal; the terminal confirms or adjusts the received recommended trip information and sends a trip feedback message carrying the final trip information to the server.

[0009] In this embodiment of the application, when the predicted destination is not the target historical destination, a trip recommendation model is used to analyze the historical destination, so that the trip recommendation information combines the user's travel preferences and patterns during historical holidays, thereby making the trip recommendation information recommended to the user more in line with the user's travel needs.

[0010] In some embodiments, when the time interval is less than a first time interval but greater than or equal to a second time interval, a trip confirmation message carrying predicted trip information is sent to the terminal.

[0011] In this embodiment, by setting a small time interval to push the predicted itinerary information to the terminal again, the user can be reminded of the holiday itinerary and to travel on time. Furthermore, when the user wants to temporarily change their travel plans, the predicted itinerary information can be modified, making the pick-up method of this application more flexible and improving the convenience and satisfaction of the user's travel.

[0012] In some embodiments, when the date type is weekend or weekday, the trip push strategy corresponds to a weekend trip push strategy or a weekday trip push strategy; when the time interval between the current time information and the predicted time of use is greater than or equal to a third time interval, a trip confirmation message carrying the predicted trip information is sent to the terminal.

[0013] In this embodiment, users' travel patterns during the week and weekends are relatively regular. Uniform push conditions reduce the complexity of the algorithm and reduce computational overhead. At the same time, setting a small time interval to push predicted travel information to users can effectively address users' advance travel arrangements and allow users to modify the predicted travel information in advance, thus better meeting users' personalized needs.

[0014] In some embodiments, when the date type is a public holiday or weekday, a pick-up instruction carrying the final itinerary information corresponding to the public holiday is sent to the vehicle; when the date type is a public holiday or weekend, a pick-up instruction carrying the final itinerary information corresponding to the public holiday is sent to the vehicle.

[0015] In this embodiment, when there are two date types, only the pick-up instruction corresponding to the holidays is sent to the terminal; this ensures that even when the date types overlap, the terminal can effectively receive the trip confirmation message and also prioritize meeting the user's travel needs during holidays.

[0016] Secondly, embodiments of this application provide a vehicle pick-up method applied to a terminal. The method includes: receiving a trip confirmation message carrying predicted trip information sent by a server; the predicted trip information is sent by the server based on a trip push strategy corresponding to a date type; the predicted trip information is obtained by the server based on current time information through a trip prediction model corresponding to a date subtype under the date type; the date type and the date subtype under the date type are determined by the server based on current time information; confirming or adjusting the predicted trip information, and sending a trip feedback message carrying final trip information to the server; the trip information includes the pick-up time, pick-up location, and destination; the server receives the trip feedback message and sends a pick-up instruction carrying the final trip information to the vehicle; the pick-up instruction instructs the vehicle to automatically drive to the final pick-up location before the final pick-up time, and to automatically drive to the final destination after the pick-up is completed.

[0017] In this embodiment, since the received predicted trip information is sent by the server based on a specific trip push strategy, and the trip push strategy corresponds to the date type of the current time information, and the predicted trip information is obtained through a trip prediction model corresponding to the date subtype under the date type, the predicted trip information received by the terminal is more in line with the user's car usage needs under different date types, thereby effectively improving the accuracy of trip information push.

[0018] Thirdly, embodiments of this application provide a vehicle pick-up system, the system including a server, a terminal, and a vehicle; the server is used to determine the date type and date subtype of the current time information; based on the current time information, it obtains predicted trip information through a trip prediction model corresponding to the date subtype; it determines the corresponding trip push strategy based on the date type; it sends a trip confirmation message carrying the predicted trip information to the terminal based on the trip push strategy; the terminal confirms or adjusts the received predicted trip information and sends a trip feedback message carrying the final trip information to the server; the server is also used to receive the trip feedback message and send a pick-up instruction carrying the final trip information to the vehicle; wherein, the trip information includes the pick-up time, the pick-up location, and the destination; the vehicle is used to automatically drive to the final pick-up location before the final pick-up time according to the received pick-up instruction, and automatically drive to the final destination after the pick-up is completed.

[0019] Fourthly, embodiments of this application provide a vehicle pick-up device, comprising: a determining unit, configured to determine the date type and date subtype of the current time information; and determine a corresponding trip push strategy based on the date type; an acquiring unit, configured to acquire predicted trip information based on the current time information using a trip prediction model corresponding to the date subtype; a sending unit, configured to send a trip confirmation message carrying the predicted trip information to a terminal based on the trip push strategy; the terminal is configured to confirm or adjust the received predicted trip information and send a trip feedback message carrying the final trip information to a server; a receiving unit, configured to receive the trip feedback message; and the sending unit is further configured to send a pick-up instruction carrying the final trip information to the vehicle; wherein the trip information includes the pick-up time, pick-up location, and destination; the pick-up instruction instructs the vehicle to automatically drive to the final pick-up location before the final pick-up time and to automatically drive to the final destination after the pick-up is completed.

[0020] Fifthly, embodiments of this application provide an electronic device, including a memory and a processor. The memory stores a computer program that can run on the processor, and the processor executes the program to implement the steps of the method in the first or second aspect.

[0021] In a sixth aspect, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method in the first or second aspect.

[0022] In a seventh aspect, embodiments of this application provide a computer program product including instructions, comprising a computer program or instructions that, when executed by a processor, implement the steps of the method in the first or second aspect. Attached Figure Description

[0023] Figure 1 This application provides a schematic diagram of the implementation process of a vehicle pick-up method. Figure 1 ; Figure 2 This application provides a schematic diagram of the implementation process of a vehicle pick-up method. Figure 2 ; Figure 3 This application provides a schematic diagram of the implementation process of a vehicle pick-up method. Figure 3 ; Figure 4 A schematic diagram of the structure of a vehicle pick-up system provided in this application embodiment. Figure 1 ; Figure 5 A schematic diagram of the structure of a vehicle pick-up system provided in this application embodiment. Figure 2 ; Figure 6 This application provides a schematic diagram of a boarding point planning. Figure 7 A schematic diagram illustrating the implementation process of a vehicle pick-up method during holidays, provided in an embodiment of this application; Figure 8 A schematic diagram illustrating the implementation process of a weekend vehicle pick-up method provided in this application embodiment; Figure 9 A schematic diagram illustrating the implementation process of a vehicle pick-up method during the week, provided in an embodiment of this application; Figure 10 This application provides a schematic diagram of the implementation process of a vehicle pick-up method. Figure 4 ; Figure 11 This is a schematic diagram of the vehicle pick-up device proposed in the embodiments of this application; Figure 12 This is a schematic diagram of the structure of the electronic device proposed in the embodiments of this application. Detailed Implementation

[0024] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0025] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described below in conjunction with the accompanying drawings. The embodiments described below are only some embodiments of this application, not all embodiments. Therefore, the described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0026] In the following description, references to "some embodiments" or "other embodiments" describe a subset of all possible embodiments, but "some embodiments" or "other embodiments" may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0027] In the following description, the terms "first" and "second" are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first" and "second" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0028] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0029] The current automatic pick-up method in related technologies involves directly sending predicted trip information to the terminal, where the user then confirms or adjusts the predicted trip information before the system automatically picks them up. This method, which directly pushes predicted trip information to the user, results in low accuracy and fails to meet the user's travel needs across different date types.

[0030] To address the aforementioned issues, this application proposes a vehicle pick-up method. In this method, a server inputs the current time information into a specific trip prediction model to obtain corresponding predicted trip information. Then, based on a corresponding trip push strategy, the server sends the predicted trip information to the terminal. The terminal receives the predicted trip information, confirms or adjusts it, and sends the confirmed or adjusted trip information as the final trip information to the server. After receiving the final trip information, the server sends the final trip information to the vehicle. Since the trip prediction model corresponds to the date subtype of the current time information, and the trip push strategy corresponds to the date type of the current time, the predicted trip information obtained using this application's vehicle pick-up method can incorporate the user's driving habits under different date subtypes, and the trip information pushed to the terminal considers the user's driving needs under different date types, making the trip information pushed by this application more accurate.

[0031] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0032] Embodiments of this application propose a vehicle pick-up method applied to a server, such as... Figure 1 As shown, the method includes the following steps: Step 101: Determine the date type and date subtypes under the current time information.

[0033] In this embodiment of the application, each date type is used to represent a predefined time range, and the date type may include, but is not limited to, weekdays, weekends and public holidays.

[0034] For example, the time range corresponding to the week is Monday to Friday, a total of five days.

[0035] In some embodiments, the date type of the current time information is determined by judging the time range in which the current time information is located.

[0036] For example, if the current time information is 17:00:00 on March 2, 2026, since March 2, 2026 falls within the time range of Monday to Friday, the date type of the current time information is determined to be weekday.

[0037] In the embodiments of this application, each date type includes its corresponding date subtype, and each date subtype is used to characterize a predefined sub-time range.

[0038] For example, the date subtypes belonging to the week include Monday, Tuesday, Wednesday, Thursday, and Friday; the date subtypes belonging to the weekend include Saturday and the weekend; the date subtypes belonging to holidays include, but are not limited to, Spring Festival, Qingming Festival, and Labor Day; the sub-time range corresponding to Labor Day is from May 1st to May 5th.

[0039] In some embodiments, the date subtype to which the current time information belongs is determined by judging the sub-time range in which the current time information is located.

[0040] For example, if the current time information is 16:03:20 on February 18, 2026, since February 18, 2026 is within the sub-time range of Wednesday and also within the time range of Chinese New Year, the date sub-type of the date type to which the current time information belongs is determined to be Wednesday and Chinese New Year.

[0041] Step 102: Based on the current time information, obtain the predicted travel information through the travel prediction model corresponding to the date subtype.

[0042] In this embodiment, the trip prediction model is a machine learning model trained based on the user's historical trip information, which is used to predict future trip information.

[0043] In some embodiments, each date subtype has a corresponding trip prediction model. Before training these trip prediction models, historical trip information and request time information of the user's vehicle under the corresponding date subtype are collected. The historical trip information includes the historical pick-up time, pick-up location, and destination. The request time information is the time before the historical pick-up time. Corresponding labels are added to the historical pick-up time, pick-up location, and destination in the historical trip information. When training the trip prediction model corresponding to each date subtype, the historical trip information and request time information are used as input to the trip prediction model to obtain predicted trip information. The predicted trip information includes the user's predicted pick-up time, pick-up location, and destination under that date subtype. Then, the loss value between the predicted pick-up time, pick-up location, and destination in the predicted trip information and the corresponding labels (e.g., the label corresponding to the predicted pick-up time and the historical pick-up time) is calculated. Finally, the parameters of the trip prediction model are updated based on the calculated loss value.

[0044] In this embodiment of the application, the predicted trip information is used to characterize the user's future travel arrangements, and may include, but is not limited to, the predicted pick-up time, pick-up location and destination.

[0045] In some embodiments, before training the trip prediction model for each date subtype, historical trip information and request time information of the user under that date subtype are collected. Historical trip information includes historical pick-up time, historical boarding location, historical destination, historical parking location, and historical driving mileage and time. Corresponding labels are added to the historical pick-up time, boarding location, historical destination, historical parking location, and historical driving mileage and time in the historical trip information. When training the trip prediction model for each date subtype, the historical trip information and request time information are used as input to the trip prediction model to obtain predicted trip information. This predicted trip information includes the user's predicted pick-up time, boarding location, destination, parking location, and driving mileage and time under that date subtype. Then, the loss value between the predicted pick-up time, boarding location, destination, parking location, and driving mileage and time in the predicted trip information and the corresponding labels is calculated. Finally, the parameters of the trip prediction model are updated based on the calculated loss value. The system includes historical parking locations, both before and after vehicle start-up and after completion of the journey. Predicted parking locations include both before and after vehicle start-up. The predicted parking location before start-up enables the vehicle to automatically drive from that location to the predicted pick-up point, and upon arrival at the predicted destination, automatically park back in the predicted location after the user exits and closes the door. Predicted parking locations allow users to see where the vehicle will be parked before holidays and after their trip, further enabling them to plan their parking. Predicted mileage and time allow users to understand the estimated travel time and route, helping them adjust their travel plans and vehicle usage needs accordingly.

[0046] In some embodiments, after determining the date subtype under the date type to which the current time information belongs, the current time information is input into the trip prediction model corresponding to the date subtype, and the output of the trip prediction model is used as the predicted trip information.

[0047] For example, when the date subtype is Dragon Boat Festival, the trip prediction model is a Dragon Boat Festival trip prediction model. The trip information predicted by this Dragon Boat Festival trip prediction model includes the pick-up time of 18:30 on June 17, 2026, the pick-up location as Exit A of the Administrative Center, and the destination as the South Parking Lot of the Visitor Center.

[0048] Step 103: Determine the corresponding trip push strategy based on the date type.

[0049] In this embodiment, the trip push strategy refers to a pre-configured set of rules and methods for sending trip confirmation messages to the terminal based on different date types. Since users' travel habits and car usage needs differ across date types—for example, during holidays, users need to prepare adequately for their trips and therefore prefer to receive trip reminders well in advance—on weekdays, users' travel is more regular and requires less preparation time, so predicted trip information can be pushed to them a shorter period before departure. The trip push strategy aims to improve the efficiency of users receiving and processing trip information by pushing predicted trip information to users in an appropriate manner and at the right time based on these differences.

[0050] In some embodiments, the server may pre-establish a mapping relationship between date types and trip push strategies. After determining the date type to which the current time information belongs, the server finds the corresponding trip push strategy based on the mapping relationship.

[0051] For example, the trip push strategy may include, but is not limited to, holiday trip push strategy, weekday trip push strategy, and weekend trip push strategy.

[0052] In some embodiments, the trip push strategy may include, but is not limited to, push time, push method, etc.

[0053] For example, in a holiday trip push strategy, when it is determined that the time interval between the current time information and the predicted travel time is 2 days, the predicted trip information is pushed to the user via SMS notification.

[0054] In this application embodiment, corresponding trip push strategies are set according to different date types, so that the vehicle pick-up method of this application can flexibly adjust the trip push strategy according to the characteristics and needs of users under different date types, thereby enabling users to obtain trip information more timely, reasonably and conveniently, thereby improving users' awareness, participation and satisfaction with the trip arrangements.

[0055] Step 104: Send a trip confirmation message carrying predicted trip information to the terminal based on the trip push strategy; The terminal is used to confirm or adjust the received predicted trip information and send a trip feedback message carrying the final trip information to the server.

[0056] In the embodiments of this application, the terminal refers to the device used by the user.

[0057] For example, the terminal includes mobile phones, tablets, and in-vehicle screens.

[0058] In this embodiment of the application, the trip confirmation message refers to the message sent by the server to the terminal, through which the predicted trip information can be presented to the user.

[0059] In some embodiments, when a communication connection is established with a terminal, the server sends a trip confirmation message to the terminal using the corresponding communication protocol.

[0060] In this embodiment of the application, the trip feedback message refers to the message sent by the terminal to the server. Through this trip feedback message, the user's confirmation of the trip information can be fed back to the terminal.

[0061] In this embodiment of the application, the final trip information refers to the trip information obtained after the user confirms or adjusts the trip information sent by the server through the terminal, including but not limited to the final pick-up time, pick-up location and destination.

[0062] In some embodiments, after the terminal receives a trip confirmation message carrying the predicted trip information, it will present the predicted trip information to the user. The user can confirm or adjust the predicted trip information through the terminal, and use the confirmed or adjusted predicted trip information as the final trip information. Then, a trip feedback message carrying the final trip information is sent to the server.

[0063] In some embodiments, when the date type is a holiday, the corresponding trip push strategy is a holiday trip push strategy; when sending a trip confirmation message carrying predicted trip information to the terminal based on the trip push strategy, the following steps may be included: Step 1041: If the time interval between the current time information and the time of vehicle use is greater than or equal to the first time interval, and the predicted destination is the target historical destination, send a trip confirmation message carrying the predicted trip information to the terminal.

[0064] In this embodiment, the first time interval refers to a pre-set time interval, which characterizes the timing of pushing travel information before holidays. This application does not impose a specific limit on the value of the first time interval, and it can be adjusted according to needs.

[0065] For example, the first time interval is 1 day.

[0066] In the embodiments of this application, the time interval refers to the time difference between the current time information and the predicted travel time in the trip information.

[0067] In this embodiment of the application, the target historical destination is a destination that the user frequently visited in the past. It can be a destination that the user has set in advance, or it can be obtained by statistical analysis of the vehicle's historical destinations during holidays. That is, destinations with a frequency or number of visits exceeding a set threshold are used as target historical destinations.

[0068] In some embodiments, when the predicted destination is a target historical destination, it indicates that the predicted destination is a place the user frequently visits (e.g., the parents' home). In this case, the predicted destination is more likely to meet the user's travel needs during the holiday. Therefore, if a trip confirmation message carrying the predicted trip information is sent directly to the terminal, the user is more likely to confirm the trip directly when the terminal receives the trip confirmation message.

[0069] By ensuring that the time interval between the current time and the pick-up time exceeds a first time interval, the terminal can receive the trip confirmation message in advance, allowing users to make sufficient preparations for holiday travel. Furthermore, the trip confirmation message will only be sent to the terminal if the predicted destination is the target historical destination, which can reduce the interference of irrelevant information and improve the user experience.

[0070] In some embodiments, when the date type is a public holiday, such as Figure 2 As shown, the vehicle pick-up method for a server provided in this embodiment of the application further includes the following steps: Step 201: If the predicted destination is not the target historical destination, obtain recommended trip information based on the vehicle's corresponding historical destination during holidays through the trip recommendation model.

[0071] In this embodiment of the application, "historical destination" refers to the destination reached by the vehicle during past holidays. These holidays can be the same (e.g., Labor Day) or different (e.g., Labor Day and National Day).

[0072] In some embodiments, when the predicted destination is not the target historical destination, it means that the predicted destination is not a place of interest to the user. Therefore, it is necessary to further utilize the user's travel patterns during historical holidays to recommend travel information that meets the user's needs, so as to reduce the push of irrelevant information.

[0073] In this embodiment of the application, the itinerary recommendation model is a machine learning model trained based on historical destination information. This itinerary recommendation model can learn the degree of correlation and pattern between destinations based on the input historical destination information, and use it to recommend corresponding itinerary information to users.

[0074] In some embodiments, before training the trip recommendation model, the system collects the user's historical destinations, pick-up times, and boarding locations during holidays, and adds corresponding labels to these locations. During training, the historical destinations, pick-up times, and boarding locations are used as input to the model to obtain recommended trip information, including the recommended destination, pick-up time, and boarding location. Then, the loss value between the recommended destination, pick-up time, and boarding location in the recommended trip information and the corresponding labels is calculated. Finally, the parameters of the trip prediction model are updated based on the calculated loss value.

[0075] In some embodiments, the recommended trip information is obtained by the trip recommendation model based on the vehicle's historical destinations during holidays, combined with the learned correlation and patterns, to meet the user's car usage needs during holidays. The recommended trip information includes, but is not limited to, recommended pick-up time, pick-up location, and destination.

[0076] Step 202: Send a trip confirmation message carrying recommended trip information to the terminal; the terminal confirms or adjusts the received recommended trip information and sends a trip feedback message carrying the final trip information to the server. The trip information includes the pick-up time, pick-up location, and destination; the pick-up instruction instructs the vehicle to automatically drive to the final pick-up location before the final pick-up time and to automatically drive to the final destination after pick-up is completed.

[0077] In this embodiment of the application, when the server obtains the recommended itinerary information, the itinerary confirmation information sent to the terminal carries the recommended itinerary information.

[0078] In some embodiments, after the terminal receives a trip confirmation message carrying recommended trip information, it will present the recommended trip information to the user. The user can confirm or adjust the recommended trip information through the terminal, and use the confirmed or adjusted recommended trip information as the final trip information. Then, a trip feedback message carrying the final trip information is sent to the server.

[0079] In this embodiment of the application, when the predicted destination is not the target historical destination, recommended travel information is pushed to the user. On the one hand, this can reduce the push of irrelevant information; on the other hand, since the recommended travel information combines the user's travel preferences and patterns during historical holidays, the recommended travel information can better meet the user's travel needs.

[0080] In some embodiments, when the date type is a public holiday, when sending a trip confirmation message carrying predicted trip information to the terminal based on the trip push strategy, the following steps may also be included: Step 1042: If the time interval is less than the first time interval but greater than or equal to the second time interval, send a trip confirmation message carrying the predicted trip information to the terminal.

[0081] In this embodiment, the second time interval is a preset time interval, which is shorter than the first time interval, and is used to characterize the timing of a second push of holiday travel information. This application does not impose a specific limitation on the value of the second time interval, and it can be adjusted according to needs.

[0082] For example, the second time interval is 60 minutes.

[0083] In some embodiments, when the time interval is between the first time interval and the second time interval, the server will send a trip confirmation message carrying the predicted trip information to the terminal again, so that when the user changes their travel needs temporarily during holidays, they can modify the trip through this trip confirmation message, thereby improving the user's travel convenience and satisfaction.

[0084] In some embodiments, when the date type is weekend or weekday, the trip push strategy corresponding to that date type is a weekend trip push strategy or a weekday trip push strategy; when sending a trip confirmation message carrying predicted trip information to the terminal based on the trip push strategy, the following steps may be included: Step 1043: If the time interval between the current time information and the predicted time of travel is greater than or equal to the third time interval, send a trip confirmation message carrying the predicted trip information to the terminal.

[0085] In this application embodiment, the third time interval refers to a preset time interval, which is used to characterize the timing of pushing travel information before the weekend or weekday. This application does not impose a specific limitation on the value of the third time interval, and it can be adjusted according to needs.

[0086] For example, the third time interval is 30 minutes.

[0087] In some embodiments, when the time interval between the current time information and the predicted travel time exceeds a third time interval, a trip confirmation message carrying the predicted trip information is sent to the terminal, allowing the user to receive the predicted trip information in advance through the terminal. Furthermore, since users' car usage habits are highly regular on weekends, the predicted trip information is highly accurate in this case; therefore, the predicted trip information can be directly pushed to the user.

[0088] In this embodiment, users' travel patterns during the week and weekends are relatively regular. Uniform push conditions reduce the complexity of the algorithm and reduce computational overhead. At the same time, setting a small time interval to push predicted travel information to users allows users to modify the predicted travel information in advance, better meeting users' personalized needs.

[0089] Step 105: Receive trip feedback message and send a pick-up instruction to the vehicle carrying the final trip information.

[0090] In this embodiment of the application, the pick-up command refers to the command used to control the vehicle to automatically pick up the passenger.

[0091] In some embodiments, when a communication connection is established between the server and the vehicle, a pick-up instruction carrying the final trip information is sent to the vehicle using the appropriate communication protocol.

[0092] In some embodiments, after the vehicle receives a pick-up instruction carrying the final trip information, it will start the vehicle before the final pick-up time in the final trip information, drive autonomously to the final pick-up location before the pick-up time, wait for the user to get in after arriving at the final pick-up location, and drive autonomously to the final destination after detecting that the pick-up is completed.

[0093] For example, a method to detect that the pick-up is complete could be that the user is in the driver's seat of the vehicle, has fastened their seatbelt, and the doors are closed.

[0094] In some embodiments, sending a pick-up instruction carrying final trip information to a vehicle may include the following steps: Step 1051: If the date type is a holiday or weekday, send a pick-up instruction to the vehicle corresponding to the holiday, carrying the final itinerary information.

[0095] Step 1052: If the date type is a holiday or weekend, send a pick-up instruction to the vehicle corresponding to the holiday, carrying the final itinerary information.

[0096] In this application embodiment, the date type of the current time information may be both a holiday and a weekday, or both a holiday and a weekend. Since users' travel needs may change more frequently during holidays, as long as users confirm or adjust their holiday travel information, priority will be given to pushing pick-up instructions corresponding to the holiday to the vehicle. In this way, while avoiding pick-up instruction conflicts, the user's car use experience during holidays can also be improved.

[0097] In summary, the vehicle pick-up method for servers provided in this application, because the predicted trip information is obtained through a trip prediction model corresponding to the date subtype of the current time information, makes the predicted trip information more consistent with users' car usage habits at different times. Furthermore, by specifying different trip push strategies based on the date type, the predicted trip information is pushed to the user's terminal in a targeted manner, making the trip information pushed to the user's terminal more consistent with the user's car usage needs under different date types, thereby effectively improving the accuracy of the trip information. When the date type is a holiday, it also determines whether it is the target historical destination and pushes different trip information accordingly, making the trip information pushed to the terminal even more consistent with the user's car usage needs. Moreover, by pushing the predicted trip information to the terminal when the time interval exceeds a set value, users can prepare for their trip in advance, improving the user experience.

[0098] Based on the above embodiments, another embodiment of this application proposes a vehicle pick-up method applied to a terminal, such as... Figure 3 As shown, the method includes the following steps: Step 301: Receive a trip confirmation message from the server carrying predicted trip information; the predicted trip information is sent by the server based on the trip push strategy corresponding to the date type; the predicted trip information is obtained by the server based on the current time information through the trip prediction model corresponding to the date subtype under the date type; the date type and the date subtype under the date type are determined by the server based on the current time information.

[0099] In this embodiment of the application, after the terminal establishes a communication connection with the server, it will receive a trip confirmation message carrying the predicted trip information sent by the server.

[0100] In some embodiments, the predicted trip information is obtained by the server through a corresponding trip prediction model, and when the server sends a trip confirmation message to the terminal, it pushes the message based on a trip push strategy corresponding to the date type. The date type corresponds to the current time information.

[0101] Step 302: Confirm or adjust the predicted trip information and send a trip feedback message carrying the final trip information to the server; the trip information includes the pick-up time, pick-up location and destination; the server is used to receive the trip feedback message and send a pick-up instruction carrying the final trip information to the vehicle; the pick-up instruction is used to instruct the vehicle to automatically drive to the final pick-up location before the final pick-up time, and to automatically drive to the final destination after the pick-up is completed.

[0102] In this embodiment of the application, after receiving a trip confirmation message carrying predicted trip information, the user can further confirm or adjust the predicted trip information through the terminal, and send the confirmed or adjusted trip information as the final trip information to the server.

[0103] For example, the predicted trip information shows the pick-up time as 18:30 on June 17, 2026, the pick-up location as Entrance A of the Administrative Center, and the destination as the South Parking Lot of the Visitor Center; if the user adjusts the pick-up time to 19:30 on June 17, 2026, without adjusting the pick-up location and destination, then the final trip information will show the pick-up time as 19:30 on June 17, 2026, the pick-up location as Entrance A of the Administrative Center, and the destination as the South Parking Lot of the Visitor Center.

[0104] In summary, the vehicle pick-up method for terminals provided in this application, because the predicted trip information received by the terminal is obtained through a trip prediction model corresponding to the date subtype, makes the predicted trip information received by the terminal more consistent with the user's car usage habits at different times. Furthermore, because the server further targets the predicted trip information according to the date type, the trip information received by the terminal is more consistent with the user's car usage needs under different date types, thereby effectively improving the accuracy of the trip information received by the terminal. When the date type is a holiday, the trip information received by the terminal also considers whether it is the target historical destination, making the trip information received by the terminal even more consistent with the user's car usage needs. Moreover, the terminal can receive the predicted trip information in advance, allowing users to prepare for their trip accordingly, thus improving the user experience.

[0105] Based on the above embodiments, another embodiment of this application proposes a vehicle pick-up system, such as... Figure 4 As shown, the vehicle pick-up system 400 includes a server 401, a terminal 402, and a vehicle 403.

[0106] Server 401 is used to determine the date type and date subtype of the current time information; based on the current time information, it obtains the predicted travel information through the travel prediction model corresponding to the date subtype; it determines the corresponding travel push strategy based on the date type; and it sends a travel confirmation message carrying the predicted travel information to the terminal based on the travel push strategy.

[0107] Terminal 402 is used to confirm or adjust the received predicted itinerary information and send a itinerary feedback message carrying the final itinerary information to the server.

[0108] Server 401 is also used to receive trip feedback messages and send pick-up instructions to the vehicle carrying the final trip information, including the pick-up time, pick-up location, and destination.

[0109] Vehicle 403 is used to automatically drive to the final pick-up location before the final pick-up time based on the received pick-up instructions, and to drive to the final destination after the pick-up is completed.

[0110] In some embodiments, the terminal may include both a mobile phone and the vehicle's central control screen. In this case, after obtaining the predicted trip information, the server can simultaneously send a trip confirmation message carrying the predicted trip information to both the mobile phone and the vehicle's central control screen. This allows the user to confirm or adjust the predicted trip information using either the mobile phone or the vehicle's central control screen. Furthermore, after obtaining the final trip information, both the mobile phone and the vehicle's central control screen can send a trip feedback message carrying the final trip information to the server, and can also directly send a pick-up command carrying the final trip information to the vehicle, thus enabling the vehicle to receive the pick-up command more quickly.

[0111] Based on the above embodiments, another embodiment of this application proposes a vehicle pick-up method, including an autonomous driving interactive control method based on user driving habits.

[0112] For example, the following is an exemplary description of possible implementations of the autonomous driving interactive control method based on user driving habits proposed in the embodiments of this application.

[0113] As autonomous driving technology matures, more and more vehicles are equipped with capabilities such as automatic pick-up, automatic parking, and automatic driving. To improve user experience, related technologies attempt to enable interaction between autonomous vehicles and mobile apps, allowing for functions such as booking rides, setting pick-up and drop-off points, and route planning. However, these technologies still have significant shortcomings, mainly reflected in: 1. Inability to learn user driving habits according to their daily routines (such as differences between weekdays, weekends, and holidays); 2. Crude reminder mechanisms, prone to accidental triggering; 3. Inability to learn user habits across multiple driving times throughout the day; 4. Lack of a complete closed-loop interaction process of "reminder—confirmation—pick-up—destination confirmation—parking—next trip notification"; 5. Inability to proactively push reminders based on user habits.

[0114] To address the aforementioned issues, this application proposes a user habit learning method based on three date models (an autonomous driving interaction control method based on user driving habits), and combines a mobile app with autonomous vehicles to achieve intelligent interaction throughout the entire process.

[0115] This application provides an autonomous driving interactive control method based on user driving habits. Its core is to divide the user's driving habits into three major date models: weekdays (within the week), weekends, and holidays. It then learns the user's driving time, pick-up point, drop-off point, and vehicle parking point from morning to night throughout the day, thereby achieving accurate reminders and fully automated control.

[0116] like Figure 5 As shown, the autonomous driving interactive control system 500 corresponding to the user's driving habits-based autonomous driving interactive control method provided in this application embodiment consists of a mobile APP 501, a cloud 502 (server), a central control screen 503, and a vehicle 504. The mobile APP 501, cloud 502, and central control screen 503 are connected wirelessly, and the central control screen 503 and the vehicle 504 realize data interaction and command transmission through in-vehicle Ethernet and CAN bus.

[0117] The cloud-based APP 502 collects and categorizes users' historical vehicle usage data, generates user habit prediction models corresponding to three date categories, and sends usage reminders and predicted trip information to the mobile phone 501 and the central control screen 503. The mobile APP 501 displays reminders, receives user confirmation or adjustment commands, displays pick-up and drop-off times and locations, and sends confirmed or adjusted trip information to the cloud. The central control screen 503 displays reminders, receives trip information, receives user confirmation or adjustment commands to confirm or adjust trip information, displays pick-up and drop-off times, locations, routes, parking prompts, and next trip previews, and sends confirmed or adjusted trip information to the cloud 502. The vehicle 503's control module receives pick-up commands from the cloud 502 via the central control screen 503. These pick-up commands control the vehicle's automatic pick-up, automatic driving, and automatic parking.

[0118] The cloud-based (server-based) user habit prediction models, comprising 14 subcategories across 3 main types, include: weekday models, weekend models, and holiday models. The weekday models use vehicle usage data from Monday to Friday for independent learning and storage; the weekend models use vehicle usage data from Saturday and Sunday for independent learning and storage; and the holiday models are built according to different holidays. Holidays are categorized into seven national statutory holidays: New Year's Day, Spring Festival, Qingming Festival, Labor Day, Dragon Boat Festival, Mid-Autumn Festival, and National Day. Seven corresponding holiday models are built for each of these seven holidays, using vehicle usage data for their respective holidays for independent learning and storage. For example, the New Year's Day model uses vehicle usage data from New Year's Day for learning.

[0119] In some embodiments, considering that users may travel earlier and return later before holidays, when learning the weekend model, the vehicle usage data of the set X1 hour (e.g., 10 hours) before the start of the weekend and the X2 hour (e.g., 11 hours) after the end of the weekend can also be used; when learning the holiday model, the vehicle usage data of the set Y1 day (e.g., 3 days) before the start of the holiday and the Y2 day (e.g., 3 days) after the end of the holiday can also be used.

[0120] Each time a user uses the vehicle, the cloud collects the following usage data: usage date, pick-up and drop-off times in hours, minutes, and seconds; pick-up point coordinates and name; drop-off point coordinates and name; vehicle parking point coordinates and name before starting; vehicle final parking point coordinates and name after the user gets off; and the mileage and time consumed during the trip. For the three date models, the data collection volume is as follows: at least one week of weekday and weekend usage data, and at least one year of holiday usage data.

[0121] After collecting vehicle usage data corresponding to 17 different date categories, this application stores these 17 categories of data separately and then trains 17 models to ensure that the 17 models are independent of each other. During training, the 17 categories of vehicle usage data need to be labeled. The principle of data standardization is: prioritize labeling holidays, then weekends, and finally weekdays.

[0122] If the day is a public holiday or Y3 days before or after a public holiday (e.g., 3 days), mark it as a public holiday; if the day is a Saturday, Sunday, or X3 hours before or after a Saturday or Sunday (e.g., 10 hours), mark it as a weekend; if the day is one of the days from Monday to Friday, mark it as a weekday.

[0123] This application uses these 17 types of vehicle usage data to train the corresponding date models. For each sub-category of date models, historical vehicle usage data is statistically analyzed separately. Then, algorithms such as K-means clustering, DBSCAN (Density-Based Spatial Clustering of Applications with Noise) density clustering, and Gaussian probability distribution are used to extract the vehicle usage time, pick-up point, drop-off point, coordinates and name of the parking point before vehicle start, coordinates and name of the final parking point after drop-off, and mileage and time of a single driving cycle. These extracted data are used as both input and output of the date model to achieve date model learning. After learning, a structured model is formed, which is used for subsequent vehicle usage prediction and reminder push.

[0124] Before the data volume is small and the boarding and alighting points have been learned, such as Figure 6As shown, the pick-up point is recommended based on the vehicle's parking location and the user's mobile phone's GPS (Global Positioning System) location information. The pick-up point is the closest available pick-up point to the GPS location information. When the destination is the departure point, the drop-off point corresponding to the destination is the pick-up point at the departure point.

[0125] When the cloud-based system performs real-time ride prediction, it first determines whether the current date falls under one of the three major categories: holidays, weekends, or weekdays. If the date belongs to only one major category, it only invokes the corresponding trip push process (trip push strategy) for that category. If the date belongs to two major categories, it invokes the trip push processes for both categories. Each major category date model then invokes its respective sub-category's ride prediction model (trip prediction model), with a maximum of two sub-category models invoked at a time. Each ride prediction model uses the predicted ride trip information (predicted trip information) obtained at the current time, including: predicted ride time, pick-up point, drop-off point, vehicle parking location, single driving cycle mileage, and time.

[0126] When it is determined that the current time falls within a holiday period, the holiday itinerary push notification process is initiated, such as... Figure 7 As shown, it includes the following steps: Step 701: Obtain the current time.

[0127] The current moment (current time information) is obtained in real time from the cloud.

[0128] Step 702: Determine whether the current day is D1 days before the predicted car usage time.

[0129] Based on the current time, determine whether the current day is D1 days before the predicted usage time (the predicted usage time). That is, calculate whether the time interval between the current time and the predicted usage time is D1 days (the first time interval). If yes, proceed to step 703; otherwise, proceed to step 709. This application does not impose a specific limit on the value of D1 and it can be adjusted according to requirements.

[0130] Step 703: Read the predicted vehicle trip.

[0131] Read the first travel trip predicted by the travel prediction model corresponding to the date type of the current time.

[0132] Step 704: Determine if there are any frequently used destinations.

[0133] Determine whether the drop-off point (predicted destination) in the first ride trip is a frequently used destination (target historical destination). If yes, proceed to step 705; otherwise, proceed to step 706. Frequently used destinations can be user-defined or calculated by the cloud based on the vehicle's historical destinations during the holiday period.

[0134] Step 705 reminds the user of their car usage needs and recommends a car trip.

[0135] The cloud sends notifications to users' mobile apps to remind them of their car usage needs during holidays, and recommends the first car trip predicted by the car usage prediction model to users through the mobile app.

[0136] Step 706: Call the vehicle infotainment system's large model and let it recommend routes.

[0137] The system calls up the vehicle's large-scale model (trip recommendation model), inputs the collected holiday destinations into the model, and queries for trip recommendations to obtain a second travel itinerary (recommended trip information). The holiday destinations are those the vehicle has reached during historical holidays.

[0138] Step 707 reminds the user of their car usage needs and recommends a large-scale trip.

[0139] The cloud sends notifications to the user's mobile app to remind them of their car usage needs during holidays, and recommends second-trip plans predicted by the vehicle's big data model to the user through the mobile app.

[0140] Step 708: Determine whether the user confirms or adjusts the car rental trip.

[0141] After receiving the first or second ride-hailing trip via a mobile app, the user confirms or adjusts the corresponding trip. The mobile app then sends the confirmed or adjusted trip (final trip information) to the cloud. If the cloud receives the trip information from the mobile app, it means the user has confirmed or adjusted the first or second ride-hailing trip, and step 713 is executed; if the cloud does not receive the trip information from the mobile app, it means the user has not confirmed or adjusted the first or second ride-hailing trip, and step 714 is executed.

[0142] Step 709: Determine if the current time is M1 minutes before the predicted car usage time.

[0143] Determine whether the current time is M1 minutes before the predicted car usage time, that is, calculate whether the time interval between the current time and the predicted car usage time is M1 minutes (the second time interval). If yes, proceed to step 710; if no, proceed to step 714. This application does not impose a specific limit on the value of M1, which can be adjusted according to requirements.

[0144] Step 710: Read the predicted car trip.

[0145] Read the first travel trip predicted by the travel prediction model corresponding to the holiday.

[0146] Step 711 reminds the user of their car usage needs and recommends car trips.

[0147] The cloud sends notifications to users' mobile apps to remind them of their car usage needs during holidays, and recommends the first car trip predicted by the car usage prediction model to users through the mobile app.

[0148] Step 712: Determine whether the user confirms or adjusts the car rental trip.

[0149] After receiving the first ride-hailing trip via the mobile app, the user will confirm or adjust the trip. The mobile app then sends the confirmed or adjusted trip to the cloud. If the cloud receives the first ride-hailing trip from the mobile app, it means the user has confirmed or adjusted the trip, and step 713 is executed; if the cloud does not receive the first ride-hailing trip from the mobile app, it means the user has not confirmed or adjusted the trip, and step 714 is executed.

[0150] Step 713: Activate autonomous driving on time.

[0151] The vehicle is controlled to activate its autonomous driving function, arriving at the pick-up point (pick-up location) before the predicted pick-up time, and then automatically driving to the drop-off point after the user gets in.

[0152] Step 714: Keep the vehicle in its original state.

[0153] The vehicle will not use its autonomous driving function to pick up and drop off users, in order to maintain the vehicle's original state.

[0154] When it is determined that the current time is a weekend, the weekend itinerary push notification process is initiated (weekend itinerary push notification strategy), such as... Figure 8 As shown, it includes the following steps: Step 801: Obtain the current time.

[0155] Step 802: Determine whether the current time is H2 before the predicted car usage time.

[0156] Determine whether the current time is H2 hours before the predicted car usage time. If yes, proceed to step 803; otherwise, proceed to step 806. Note that this application does not impose a specific limit on the value of H2, which can be adjusted according to requirements.

[0157] Step 803: Read the predicted vehicle trip.

[0158] Read the third-party travel trip predicted by the travel prediction model corresponding to the date type of the current time.

[0159] Step 804 reminds the user of their car usage needs and recommends a car trip.

[0160] The cloud sends notifications to the user's mobile app to remind the user of their car usage needs for the weekend, and recommends third-party car trips predicted by the car usage prediction model corresponding to that weekend to the user through the mobile app.

[0161] Step 805: Determine whether the user confirms or adjusts the car rental trip.

[0162] After receiving a third-party ride-hailing trip via a mobile app, the user confirms or adjusts the trip. The app then sends the confirmed or adjusted trip to the cloud. If the cloud receives the trip information from the mobile app, it means the user has confirmed or adjusted the trip, and step 810 is executed. If the cloud does not receive the trip information from the mobile app, it means the user has not confirmed or adjusted the trip, and step 811 is executed.

[0163] Step 806: Determine if the current time is M2 minutes before the predicted car usage time.

[0164] Determine whether the current time is M2 minutes before the predicted car usage time, that is, calculate whether the time interval between the current time and the predicted car usage time is M2 minutes (the third time interval). If yes, proceed to step 807; otherwise, proceed to step 811. Note that this application does not impose a specific limit on the value of M2, and it can be adjusted according to requirements.

[0165] Step 807: Read the predicted vehicle trip.

[0166] Read the third-party vehicle trip predicted by the vehicle use prediction model corresponding to the date type of the current time, or read the third-party vehicle trip confirmed or adjusted by the user in the steps.

[0167] Step 808 reminds the user of their car usage needs and recommends a car trip.

[0168] Step 809: Determine whether the user confirms or adjusts the car rental trip.

[0169] Step 810: Activate autonomous driving on time.

[0170] Step 811: Keep the vehicle in its original state.

[0171] In this embodiment, the process of pushing weekend trip information involves two checks on the time interval between the current moment and the predicted travel time. This is to provide a second trip notification to the user, allowing for adjustments to the predicted trip if the user wishes to change their itinerary. If this is not required, only one notification is sent to the user during the weekend trip information push process.

[0172] When it is determined that the current time is a weekday, the weekday schedule push notification process (weekly schedule push notification strategy) is initiated, such as... Figure 9 As shown, it includes the following steps: Step 901: Obtain the current time.

[0173] Step 902: Determine if the current time is M3 minutes before the predicted car usage time.

[0174] Determine if the current time is M3 minutes before the predicted car usage time. If yes, proceed to step 903; otherwise, proceed to step 907. Note that this application does not impose a specific limit on the value of M3, which can be adjusted according to requirements.

[0175] Step 903: Read the predicted vehicle trip.

[0176] Read the fourth trip predicted by the car usage prediction model corresponding to the date type of the current time.

[0177] Step 904 reminds the user of their car usage needs and recommends a car trip.

[0178] The cloud platform sends notifications to users' mobile apps via a mobile app to remind them of their car usage needs on weekdays, and recommends the fourth car usage trip predicted by the car usage prediction model corresponding to that weekday to users through the mobile app.

[0179] Step 905: Determine whether the user confirms or adjusts the car rental trip.

[0180] After receiving a ride-hailing trip, the user will confirm or adjust the trip. The mobile app then sends the confirmed or adjusted trip to the cloud. If the cloud receives the ride-hailing trip from the mobile app, it means the user has confirmed or adjusted the trip, and step 906 is executed; if the cloud does not receive the ride-hailing trip from the mobile app, it means the user has not confirmed or adjusted the trip, and step 907 is executed.

[0181] Step 906: Start autonomous driving on time.

[0182] The vehicle is controlled to activate its autonomous driving function, arriving at the pick-up point of the fourth ride before the predicted pick-up time, and then automatically driving to the drop-off point of the fourth ride after the user gets in.

[0183] Step 907: Keep the vehicle in its original state.

[0184] In this embodiment, if it is determined that the current time falls on both a holiday and a weekday, both holiday and weekday trip push notification processes are activated simultaneously, but the push notifications and reminders are based on holiday trips. If it is determined that the current time falls on both a holiday and a weekend, both holiday and weekend trip push notification processes are activated simultaneously, but the push notifications and reminders are based on holiday trips. If it is determined that the current time falls on both a weekend and a weekday, both weekend and weekday trip push notification processes are activated simultaneously, but the push notifications and reminders are based on weekend trips.

[0185] When a user needs to engage autonomous driving mode 1006 after getting into the car, such as Figure 10 As shown, it includes the following steps: Step 1001: Power on the vehicle.

[0186] The user starts the vehicle.

[0187] Step 1002: Read the predicted vehicle trip.

[0188] Read the fifth car trip predicted by the car trip prediction model corresponding to the date type of the current time.

[0189] Step 1003: Push notification of car trip details.

[0190] The cloud pushes the fifth vehicle trip information to the vehicle's central control screen.

[0191] Step 1004: Determine whether the user confirms or adjusts the car rental trip.

[0192] After receiving the fifth car rental trip information via the central control screen, the user will confirm or adjust the trip. The central control screen will then send the confirmed or adjusted trip information to the cloud. If the cloud receives the trip information from the central control screen, it means the user has confirmed or adjusted the trip, and step 1005 is executed; if the cloud does not receive the trip information from the central control screen, it means the user has not confirmed or adjusted the trip, and step 1011 is executed.

[0193] Step 1005: Start autonomous driving to the destination.

[0194] Control the vehicle to activate the automatic driving function, and drive it to the drop-off point of the fifth vehicle trip.

[0195] Step 1006: Determine whether the destination has been reached.

[0196] The cloud platform determines whether the vehicle has reached the drop-off point in the fifth car rental trip based on the vehicle's real-time location information. If yes, step 1007 is executed; otherwise, step 1011 is executed.

[0197] Step 1007: Obtain the next predicted car trip.

[0198] After the vehicle arrives at the drop-off point, the system will remind the user of the vehicle's parking location and read the sixth trip predicted by the vehicle usage prediction model corresponding to the current date type.

[0199] Step 1008: Push notification of car trip details.

[0200] The cloud pushes the sixth trip information to the vehicle's central control screen.

[0201] Step 1009: Determine whether the user confirms or adjusts the car rental trip.

[0202] After receiving the sixth car-hailing trip information via the central control screen, the user will confirm or adjust the trip. The central control screen will then send the confirmed or adjusted trip to the cloud. If the cloud receives the sixth car-hailing trip information from the central control screen, it means the user has confirmed or adjusted the trip, and step 1010 is executed. If the cloud does not receive the sixth car-hailing trip information from the central control screen, it means the user has not confirmed or adjusted the trip, and step 1011 is executed.

[0203] Step 1010: Activate autonomous driving on time.

[0204] The vehicle is controlled to activate its autonomous driving function, arriving at the pick-up point of the sixth trip before the predicted pick-up time, and then automatically driving to the drop-off point of the sixth trip after the user gets in.

[0205] Step 1011: Keep the vehicle in its original state.

[0206] In this embodiment, the mobile app pushes predicted car-hailing trip information in the form of text, images, and voice. For example, your next car-hailing time is 17:35 tomorrow afternoon, the pick-up point is Hotel A, the destination is Resort B, and the estimated travel time is 10 hours. Xiao An will pick you up on time. Please confirm or adjust the trip information. After the user confirms or adjusts, the user controls the vehicle to activate the autonomous driving function to achieve automatic pick-up and drop-off.

[0207] The autonomous driving interactive control method based on user driving habits provided in this application effectively avoids interference between different lifestyles by dividing the driving prediction model into three major categories and 17 subcategories according to date type, with each model learning independently. This allows each driving prediction model to predict driving trips more accurately on different dates. When pushing trip information, it avoids pushing weekday reminders on weekends or holidays, making the trip reminders more accurate. In the closed-loop logic from reminder to parking, only user confirmation or adjustment is required, eliminating complex interface operations and settings, simplifying the operation and achieving a high degree of automation throughout the trip push process. Each driving prediction model predicts entirely based on the user's individual driving habits, fulfilling personalized needs. Since users do not need to repeatedly input pick-up and drop-off points, the user experience is improved.

[0208] Based on the above embodiments, Figure 11 This is a schematic diagram of a vehicle pick-up device provided in an embodiment of this application, as shown below. Figure 11 As shown, the vehicle pick-up device 1100 includes: a determining unit 1101, an acquiring unit 1102, a sending unit 1103, and a receiving unit 1104; wherein: The determining unit 1101 is used to determine the date type to which the current time information belongs and the date subtype under the date type; and to determine the corresponding trip push strategy based on the date type.

[0209] The acquisition unit 1102 is used to acquire predicted travel information based on the current time information and through the travel prediction model corresponding to the date subtype.

[0210] The sending unit 1103 is used to send a trip confirmation message carrying predicted trip information to the terminal based on the trip push strategy; the terminal is used to confirm or adjust the received predicted trip information and send a trip feedback message carrying the final trip information to the server.

[0211] The receiving unit 1104 is used to receive trip feedback messages.

[0212] The sending unit 1103 is also used to send a pick-up instruction to the vehicle carrying the final trip information; wherein, the trip information includes the time of pick-up, the pick-up location and the destination; the pick-up instruction is used to instruct the vehicle to automatically drive to the final pick-up location before the final time of pick-up, and to automatically drive to the final destination after the pick-up is completed.

[0213] In some embodiments, when the date type is a holiday, the trip push strategy is a holiday trip push strategy; the sending unit 1103 is further configured to send a trip confirmation message carrying the predicted trip information to the terminal if the time interval between the current time information and the predicted time of use is greater than or equal to a first time interval, and if the predicted destination is the target historical destination.

[0214] In some embodiments, if the predicted destination is not the target historical destination, the determining unit 1101 is further configured to determine recommended trip information based on the historical destination corresponding to the vehicle during the holiday by using a trip recommendation model; the sending unit 1103 is further configured to send a trip confirmation message carrying the recommended trip information to the terminal; the terminal is configured to confirm or adjust the received recommended trip information and send a trip feedback message carrying the final trip information to the server.

[0215] In some embodiments, the sending unit 1103 is further configured to send a trip confirmation message carrying the predicted trip information to the terminal when the time interval is less than a first time interval but greater than or equal to a second time interval.

[0216] In some embodiments, when the date type is weekend or weekday, the trip push strategy corresponds to a weekend trip push strategy or a weekday trip push strategy; the sending unit 1103 is further configured to send a trip confirmation message carrying the predicted trip information to the terminal when the time interval between the current time information and the predicted trip time is greater than or equal to a third time interval.

[0217] In some embodiments, the sending unit 1103 is further configured to send a pick-up instruction carrying the final itinerary information corresponding to a holiday to the vehicle when the date type is a public holiday or a weekday; and to send a pick-up instruction carrying the final itinerary information corresponding to a holiday to the vehicle when the date type is a public holiday or a weekend.

[0218] The descriptions of the above device embodiments are similar to those of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0219] It should be noted that the module division in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, exist as separate physical units, or have two or more units integrated into one unit. The integrated units can be implemented in hardware, as software functional units, or a combination of software and hardware.

[0220] It should be noted that, in the embodiments of this application, if the above methods are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause an electronic device to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0221] This application provides an electronic device. Figure 12 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application, such as... Figure 12 As shown, the electronic device 1200 includes a memory 1201 and a processor 1202. The memory 1201 stores a computer program that can run on the processor 1202. When the processor 1202 executes the program, it implements the steps in the method provided in the above embodiments.

[0222] It should be noted that the memory 1201 is configured to store instructions and applications executable by the processor 1202, and can also cache data to be processed or already processed (e.g., image data, audio data, voice communication data and video communication data) in the processor 1202 and various modules in the electronic device 1200. It can be implemented by flash memory or random access memory (RAM).

[0223] This application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the method provided in the above embodiments.

[0224] This application provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the steps in the method provided in the above-described method embodiments.

[0225] It should be noted that the descriptions of the above storage medium and electronic device embodiments are similar to the descriptions of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the storage medium and electronic device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0226] It should be understood that the phrases "one embodiment," "an embodiment," or "some embodiments" mentioned throughout the specification mean that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment," "in one embodiment," or "in some embodiments" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above-described processes do not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above-described embodiments are merely for descriptive purposes and do not represent the superiority or inferiority of the embodiments. The descriptions of the various embodiments above tend to emphasize the differences between the various embodiments; their similarities or commonalities can be referred to mutually, and for the sake of brevity, they will not be repeated here.

[0227] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three kinds of relationships. For example, object A and / or object B can represent three situations: object A exists alone, object A and object B exist simultaneously, and object B exists alone.

[0228] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or electronic device. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0229] In the several embodiments provided in this application, it should be understood that the disclosed electronic devices and methods can be implemented in other ways. The embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple modules or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of electronic devices or modules can be electrical, mechanical, or other forms.

[0230] The modules described above as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules. They may be located in one place or distributed across multiple network units. Some or all of the modules may be selected to achieve the purpose of this embodiment according to actual needs.

[0231] In addition, each functional module in the various embodiments of this application can be integrated into one processing unit, or each module can be a separate unit, or two or more modules can be integrated into one unit; the integrated modules can be implemented in hardware or in the form of hardware plus software functional units.

[0232] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, read-only memory (ROM), magnetic disks, or optical disks.

[0233] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause an electronic device to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0234] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0235] The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0236] The features disclosed in the several method or electronic device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method or electronic device embodiments.

[0237] The above are merely embodiments 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.

[0238] It should be understood that if this disclosure references any user data and personal information (including but not limited to device information, behavioral data, location information, etc.) and before applying the technical solutions described in the embodiments of this disclosure, the relevant products or services should comply with the laws and regulations concerning the protection of user data and personal information, strictly process users' personal information and data in accordance with the provisions of applicable laws and regulations throughout the entire data processing lifecycle, follow the principles of legality, legitimacy, necessity, good faith, openness, and transparency, and adopt reasonable privacy design schemes and technical measures to ensure the security of user data and personal information, protect users' legitimate rights and interests, and prevent the risks of leakage, theft, or tampering of user data and personal information.

[0239] Specifically, the company must publish and display its privacy policy in a prominent position on the user interface, clearly informing users of the types, purposes, uses, and methods of processing personal information, as well as other matters that should be disclosed as required by laws and regulations; obtain users' prior informed consent or explicit authorization regarding data processing through user-initiated interaction (such as confirmation pop-ups); process or store user data securely within the legally required timeframe; adopt a series of security technologies and management measures, including but not limited to data encryption and access control; share and transfer user data within the scope permitted by law and in a legally required manner; and process user rights, including the rights to query, access, correct, delete, withdraw authorization and consent, cancel registration, and obtain copies of personal information, within the legally required timeframe.

Claims

1. A method for picking up and dropping off a vehicle, characterized in that, Applied to a server, the method includes: Determine the date type to which the current time information belongs, as well as the date subtypes under that date type; Based on the current time information, the predicted travel information is obtained through the travel prediction model corresponding to the date subtype; The corresponding itinerary push strategy is determined based on the date type; Based on the trip push strategy, a trip confirmation message carrying the predicted trip information is sent to the terminal; the terminal is used to confirm or adjust the received predicted trip information and send a trip feedback message carrying the final trip information to the server. Receive the trip feedback message and send a pick-up instruction to the vehicle carrying the final trip information; The trip information includes the pick-up time, pick-up location, and destination; the pick-up instruction is used to instruct the vehicle to automatically drive to the final pick-up location before the final pick-up time, and to automatically drive to the final destination after the pick-up is completed.

2. The method according to claim 1, characterized in that, When the date type is a holiday, the trip push strategy is a holiday trip push strategy; sending a trip confirmation message carrying the predicted trip information to the terminal based on the trip push strategy includes: If the time interval between the current time information and the predicted time of travel is greater than or equal to a first time interval, and if the predicted destination is the target historical destination, a trip confirmation message carrying the predicted trip information is sent to the terminal.

3. The method according to claim 2, characterized in that, The method further includes: If the predicted destination is not the target historical destination, the recommended trip information is determined by the trip recommendation model based on the historical destination of the vehicle during the holiday. The terminal sends a trip confirmation message carrying the recommended trip information to the terminal; the terminal confirms or adjusts the received recommended trip information and sends a trip feedback message carrying the final trip information to the server.

4. The method according to claim 2, characterized in that, The step of sending a trip confirmation message carrying the predicted trip information to the terminal based on the trip push strategy further includes: If the time interval is less than the first time interval but greater than or equal to the second time interval, a trip confirmation message carrying the predicted trip information is sent to the terminal.

5. The method according to any one of claims 1 to 3, characterized in that, When the date type is weekend or weekday, the trip push strategy corresponds to either a weekend trip push strategy or a weekday trip push strategy. The step of sending a trip confirmation message carrying the predicted trip information to the terminal based on the trip push strategy includes: If the time interval between the current time information and the predicted travel time is greater than or equal to a third time interval, a trip confirmation message carrying the predicted trip information is sent to the terminal.

6. The method according to any one of claims 1 to 3, characterized in that, Sending the pick-up instruction to the vehicle carrying the final trip information includes: When the date type is a holiday or weekday, send a pick-up instruction to the vehicle corresponding to the holiday, carrying the final itinerary information; In the case where the date type is a holiday or weekend, a pick-up instruction carrying the final itinerary information corresponding to the holiday is sent to the vehicle.

7. A method for picking up and dropping off a vehicle, characterized in that, Applied to a terminal, the method includes: The server receives a trip confirmation message carrying predicted trip information; the predicted trip information is sent by the server based on a trip push strategy corresponding to the date type; the predicted trip information is obtained by the server based on the current time information through a trip prediction model corresponding to the date subtype under the date type; the date type and the date subtype under the date type are determined by the server based on the current time information. The predicted trip information is confirmed or adjusted, and a trip feedback message carrying the final trip information is sent to the server. The trip information includes the pick-up time, pick-up location, and destination. The server receives the trip feedback message and sends a pick-up instruction carrying the final trip information to the vehicle. The pick-up instruction instructs the vehicle to automatically drive to the final pick-up location before the final pick-up time and to automatically drive to the final destination after the pick-up is completed.

8. A vehicle pick-up and drop-off system, characterized in that, The system includes a server, a terminal, and a vehicle; The server is configured to determine the date type to which the current time information belongs and the date subtypes under the date type; based on the current time information, obtain predicted travel information through a travel prediction model corresponding to the date subtype; determine the corresponding travel push strategy based on the date type; and send a travel confirmation message carrying the predicted travel information to the terminal based on the travel push strategy. The terminal is used to confirm or adjust the received predicted itinerary information and send an itinerary feedback message carrying the final itinerary information to the server. The server is also used to receive the trip feedback message and send a pick-up instruction to the vehicle carrying the final trip information; wherein, the trip information includes the pick-up time, pick-up location and destination; The vehicle is used to automatically drive to the final pick-up location before the final pick-up time according to the received pick-up instruction, and to drive to the final destination after the pick-up is completed.

9. A vehicle pick-up and drop-off device, characterized in that, The device includes: The determining unit is used to determine the date type to which the current time information belongs and the date subtypes under the date type; and to determine the corresponding trip push strategy based on the date type; The acquisition unit is used to acquire predicted travel information based on the current time information and through a travel prediction model corresponding to the date subtype. The sending unit is used to send a trip confirmation message carrying the predicted trip information to the terminal based on the trip push strategy; the terminal is used to confirm or adjust the received predicted trip information and send a trip feedback message carrying the final trip information to the server. A receiving unit is configured to receive the trip feedback message; The sending unit is also used to send a pick-up instruction carrying the final trip information to the vehicle; The trip information includes the pick-up time, pick-up location, and destination; the pick-up instruction is used to instruct the vehicle to automatically drive to the final pick-up location before the final pick-up time, and to automatically drive to the final destination after the pick-up is completed.

10. An electronic device comprising a memory and a processor, the memory storing a computer program executable on the processor, characterized in that, When the processor executes the program, it implements the method of any one of claims 1 to 6, or the method of claim 7.

Images