Dynamic reminding method and system based on travel

Abstract

The invention provides a dynamic reminding method and system based on a travel. The method comprises the following steps: acquiring an event or a behavior associated with a user in the travel; determining a reminding trigger condition for the acquired event or behavior according to the type of the event or behavior; acquiring current journey information about the journey, wherein the current journey information includes at least a time to arrive at a destination of the current journey; determining whether a reminding trigger condition is satisfied based on the acquired current travel information; and sending a prompt to the user in response to the condition that the prompt trigger condition is met.

Description

Technical Field

[0001] The present invention relates to the technical field of intelligent travel, and more particularly, to a trip-based dynamic reminder method and system. Background Art

[0002] Taking a vehicle such as a car is a common way for people to travel. As a driver, a user usually uses a navigation application to provide route planning and to obtain trip information, such as real-time traffic congestion, distance to the destination, and time to reach the destination, etc. Based on this trip information, the user can have some control over the trip, for example, usually judge whether they can arrive at the destination within the expected time and whether it will delay subsequent appointments and trip arrangements. In contrast to being a driver, when being a passenger, the user usually cannot obtain trip information at any time like a driver, unless the user also keeps the navigation application open and frequently checks it like a driver. Therefore, when the user is resting or entertaining during the trip, they may be suddenly interrupted due to changes in the trip. For example, the user starts a game but has to interrupt the game and get off the vehicle before it ends because they have reached the destination, which causes a certain bad experience for the user. The same situation may also occur in the scenario of a vehicle in fully autonomous driving mode or a driverless vehicle. Summary of the Invention

[0003] The Summary of the Invention is provided to introduce in a simplified form some concepts that will be further described in the following Detailed Description. The Summary of the Invention is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to help determine the scope of the claimed subject matter.

[0004] In view of the above problems, the present invention provides a trip-based dynamic reminder solution, which can generate dynamic reminders according to the user's current trip, and the reminder timing is more flexible and intelligent. In addition, this solution can continuously monitor the real-time changes of the trip and timely inform the user when it may have an adverse impact on the user, so that the user can timely master the latest situation and have the opportunity to take measures.

[0005] According to one aspect of the present invention, there is provided a trip-based dynamic reminder method, the dynamic reminder method comprising: obtaining an event or behavior associated with a user who is in a trip; determining a reminder trigger condition for the type of the event or behavior for the obtained event or behavior; obtaining current trip information about the trip, wherein the current trip information at least includes the time expected to reach the destination of the current trip; determining whether the reminder trigger condition is satisfied based on the obtained current trip information; and in response to the reminder trigger condition being satisfied, sending a reminder to the user.

[0006] According to a further embodiment of the present invention, obtaining an event or behavior associated with a user who is in the process of traveling further includes one or more of the following: obtaining the user's schedule information; obtaining the application usage status of the user on the mobile terminal; receiving an instruction from the user to establish a reminder event; or identifying the user's behavior via a sensor.

[0007] According to a further embodiment of the present invention, the types of events or behaviors include: events or behaviors with a predetermined start time, events or behaviors with an estimated end time, and continuous events or behaviors.

[0008] According to a further embodiment of the present invention, events or behaviors with a predetermined start time include: existing events in the user's schedule or newly created events by the user in the schedule, events or behaviors with an estimated end time include: the user opening a game application or the user browsing a media directory or selecting media in a multimedia application, and continuous events or behaviors include the user being in a sleep state, the user being in a reading state, or the user being in a voice call.

[0009] According to a further embodiment of the present invention, determining a reminder trigger condition for the obtained event or behavior based on the type of the event or behavior further includes: for an event or behavior with a predetermined start time, the reminder trigger condition is to determine that the current itinerary may cause the user to be unable to execute the event or behavior at the predetermined start time; for an event or behavior with an estimated end time, the reminder trigger condition is to determine that the current itinerary may cause the user to be unable to complete the event or behavior before the estimated end time; and for a continuous event or behavior, the reminder trigger condition is to determine that the remaining time until the expected arrival at the destination of the current itinerary is less than a predetermined time threshold.

[0010] According to a further embodiment of the present invention, determining whether the trigger condition is satisfied based on the obtained current itinerary information further includes: determining that the trigger condition is satisfied in response to any one of the following situations: the time expected to arrive at the destination of the current itinerary is later than the predetermined start time of the event or behavior; the time by which the time expected to arrive at the destination of the current itinerary is earlier than the predetermined start time of the event or behavior is less than a threshold time amount; the time expected to arrive at the destination of the current itinerary is earlier than the estimated end time of the event or behavior; or the remaining time until the expected arrival at the destination of the current itinerary is less than a predetermined time threshold.

[0011] According to a further embodiment of the present invention, obtaining the current itinerary information about the itinerary includes obtaining the current itinerary information from the means of transportation the user is taking or a navigation application running on the user's mobile terminal, where the current itinerary information is dynamically updated.

[0012] According to a further embodiment of the present invention, in response to the current itinerary information being updated, re-determine whether the reminder trigger condition is satisfied.

[0013] According to a further embodiment of the present invention, the reminder trigger condition is set by self-learning based at least in part on the observation of the user's historical behavior.

[0014] According to a further embodiment of the present invention, the dynamic reminder method is executed by the vehicle in which the user is riding or by the user's mobile terminal.

[0015] According to another aspect of the present invention, there is provided a trip-based dynamic reminder system, including: a trip information acquisition module configured to acquire current trip information about a trip, where the current trip information includes at least the time expected to reach the destination of the current trip; a reminder management module configured to: acquire events or behaviors associated with the user; determine a reminder trigger condition for the acquired events or behaviors according to the type of the events or behaviors; determine whether the reminder trigger condition is satisfied based on the acquired current trip information; and generate a reminder trigger signal in response to the reminder trigger condition being satisfied; and a reminder module configured to issue a reminder to the user in response to the reminder trigger signal.

[0016] According to a further embodiment of the present invention, acquiring events or behaviors associated with a user who is in a vehicle further includes one or more of the following: acquiring the user's schedule information; acquiring the application usage status of the user on the mobile terminal; receiving an instruction from the user to establish a reminder event; or identifying the user's behavior via a sensor. Determining a reminder trigger condition for the acquired events or behaviors according to the type of the events or behaviors further includes: for an event or behavior with a predetermined start time, the reminder trigger condition is to determine that the current trip may cause the user to be unable to execute the event or behavior at the predetermined start time; for an event or behavior with an expected end time, the reminder trigger condition is to determine that the current trip may cause the user to be unable to complete the event or behavior before the expected end time; and for a continuous event or behavior, the reminder trigger condition is to determine that the remaining time until the expected arrival at the destination of the current trip is less than a predetermined duration threshold. Determining whether the trigger condition is satisfied based on the acquired current trip information further includes: determining that the trigger condition is satisfied in response to any one of the following situations: the time expected to reach the destination of the current trip is later than the predetermined start time of the event or behavior; the time amount by which the time expected to reach the destination of the current trip is earlier than the predetermined start time of the event or behavior is less than the threshold time amount; the time expected to reach the destination of the current trip is earlier than the expected end time of the event or behavior; or the remaining time until the expected arrival at the destination of the current trip is less than the predetermined duration threshold.

[0017] According to a further embodiment of the present invention, obtaining current trip information regarding a trip includes obtaining the current trip information from a vehicle in which a user is riding or from a navigation application running on the user's mobile terminal, where the current trip information is dynamically updated, and the reminder management module is further configured to: in response to the current trip information being updated, re-determine whether the trigger condition is satisfied.

[0018] According to a further embodiment of the present invention, the reminder management module is further configured to: set a reminder trigger condition through self-learning based at least in part on an observation of the user's historical behavior.

[0019] According to another aspect of the present invention, there is provided a vehicle including the dynamic reminder system as described in the present invention.

[0020] Compared with the prior art, the dynamic reminder method of the present invention has at least the following advantages:

[0021] 1. The timing of the reminder is more flexible. For example, it can be set to trigger a reminder at a certain time before arriving at the destination, and this trigger time can change dynamically as the trip changes;

[0022] 2. It allows for a more intelligent pre-reminder to be provided to the user. For example, before arriving at the destination, the user can be reminded not to start an activity that is not suitable to be interrupted; and

[0023] 3. In the case where the trip information can be updated in real time and dynamically, it enables the user to be notified in a timely manner of the adverse effects on the subsequent trip arrangement without the user having to pay attention to the dynamic changes of the trip (such as traffic congestion, etc.) by himself.

[0024] These and other features and advantages will become apparent by reading the following detailed description and referring to the associated drawings. It should be understood that the foregoing general description and the following detailed description are illustrative only and do not limit the various aspects claimed. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to understand in detail the manner in which the above-described features of the present invention are used, the above briefly summarized content can be described in more detail with reference to the various embodiments, some of which are shown in the drawings. However, it should be noted that the drawings only show certain typical aspects of the present invention and should not be considered to limit its scope, as the description may allow other equally effective aspects.

[0026] Figure 1 is a schematic flowchart of a trip-based dynamic reminder method according to an embodiment of the present invention.

[0027] Figure 2 is a schematic structure of a trip-based dynamic reminder system according to an embodiment of the present invention.

[0028] Figure 3 It is a schematic structural diagram of a vehicle according to an embodiment of the present invention. Detailed implementation manners

[0029] The present invention will be described in detail below with reference to the accompanying drawings, and the features of the present invention will be further revealed in the following detailed description. The term "transportation means" used throughout the specification refers to any type of transportation means, including but not limited to vehicles, trains, ships, aircraft, etc. "Vehicle" refers to any type of ground transportation means, including but not limited to cars, trucks, lorries, buses, motorcycles, bicycles, scooters, etc. At the same time, "vehicle" is not limited to the power type, including fuel vehicles, electric vehicles, hydrogen energy vehicles, etc. The term "A or B" used in the specification means "A and B" and "A or B", and does not mean that A and B are exclusive, unless otherwise specified.

[0030] Figure 1 It is a schematic flowchart of a trip-based dynamic reminder method 100 according to an embodiment of the present invention. As will be described in detail below in conjunction with the detailed implementation manners, the dynamic reminder method 100 can be executed by a transportation means (such as a vehicle) in which the user is riding or a mobile terminal used by the user.

[0031] As Figure 1 shown, the method 100 starts at step 102, obtaining events or behaviors associated with a user who is in a trip. "Trip" refers to the moving process from one location (departure place) to another location (destination), also known as the travel process. In various embodiments of the present invention, it will be mainly described that the user travels by taking a transportation means (for example, a vehicle, a train, a subway, a ship, an airplane, etc.), but it can also cover scenarios where the user travels by other means such as cycling or walking.

[0032] Events or behaviors associated with the user refer to events or behaviors that the user is participating in or will participate in. Depending on the relationship between the nature and time of these events or behaviors, the events or behaviors can be classified into different types. According to an embodiment of the present invention, the types of events or behaviors may include: events or behaviors with a predetermined start time, events or behaviors with an estimated end time, and continuous events or behaviors.

[0033] Events or behaviors with a predetermined start time may include: calendar events, also known as appointments, such as existing events in the user's calendar or new events created by the user in the calendar, and such calendar events usually have a clear start time.

[0034] Events or actions with an estimated end time may include: activities for which the duration of the event or action can be estimated relatively accurately, such as a user opening a game application or a user browsing a media catalog or selecting media in a multimedia application. Taking playing a game as an example, the concept of "round" is involved in many games, and players strongly hope not to be interrupted or disturbed during the round. For example, in popular battle games, a player quitting in the middle of a round is usually regarded as giving up and losing, and sometimes it will even be recorded as a loss of reputation on the game server side. In addition, even if a player manages to stay in the game without quitting, being interrupted by factors such as switching to a payment application, switching to manual driving, getting off and transferring, or walking will seriously affect the player's performance in the game. For such games with the concept of "round", the time spent on each round is generally fixed or can be estimated statistically, usually ranging from a few minutes to dozens of minutes. Therefore, when a user is about to start a new round of the game, the end time of this round of the game can be estimated. Similarly, if it is playing media, the time to finish playing the media can be determined, for example, by the length or remaining time of the media.

[0035] Continuous events or actions may include activities with uncertain time, such as a user being in a sleep state, a user being in a reading state, or a user being in a voice call state. For such activities, the end time cannot be accurately estimated. For example, it is impossible to predict when a user will wake up from sleep or end a call.

[0036] In contrast to the above examples of events or actions, obtaining events or actions associated with a user who is on a journey can be achieved through the following example methods, such as:

[0037] Obtaining the user's schedule information to determine the scheduled start time of the schedule event;

[0038] Obtaining the application usage status of the user on the mobile terminal to determine the estimated end time of an event or action that has already started or may start. For example, with the user's authorization, the status of each application can be read through the application programming interface on the mobile terminal, including which application the user has opened (such as a game application or a media application), the application the user is currently using, the user's usage in the application (such as the user being in the middle of a game round, during media playback, etc.), and the prediction of the user's future actions (such as when the user is on the game preparation interface, predicting that the user may start a new round; when the user is on the media selection interface, predicting that the user may start playing media). By obtaining the above statuses, the approximate end time of the event or action can be estimated based on these statuses;

[0039] Receive an instruction from the user to establish a reminder event. For example, the user may interact with a voice assistant on a mobile terminal or in a vehicle system by voice, asking the voice assistant to remind themselves at a certain static or dynamic time point, such as a reminder at 10 o'clock, a reminder half an hour later, or a reminder 10 minutes before arriving at the destination. By recognizing the user's instruction, a time point can be determined similarly, which is similar to the expected start time; or

[0040] Identify the user's behavior via sensors, such as the above-mentioned persistent events or behaviors. For example, it can be determined whether the user is sleeping, reading (including paper books or e-books), or making a voice call through vehicle sensors (such as cameras inside the vehicle) or sensors on the mobile terminal. Reading and voice calls can also be identified by the application usage status, especially when the user uses a reading application on the mobile terminal to read or uses a communication application on the mobile terminal to make a voice call. It can be understood that the above methods can be combined to more accurately obtain or identify the types of events or behaviors associated with the user who is on a journey and the relevant status information.

[0041] In step 104, determine a reminder trigger condition for the type of event or behavior that is the obtained event or behavior. As mentioned above, there are several different types of events or behaviors. For different types, the purpose and timing of the reminder may be different, so different reminder trigger conditions can be set according to the type. As some non-limiting examples, determining a reminder trigger condition for the type of event or behavior that is the obtained event or behavior may include but is not limited to:

[0042] For an event or behavior with a predetermined start time, the reminder trigger condition can be set to determine that the current journey may cause the user to be unable to execute the event or behavior at the predetermined start time. For example, the user has a schedule event to watch a movie at a certain cinema at 19:30. Then this event is an event with a predetermined start time (i.e., 19:30). Therefore, if it is determined based on the current journey dynamics that it is likely to cause the user to be unable to arrive at the cinema before 19:30, the user needs to be reminded of this situation;

[0043] For an event or behavior with an expected end time, the reminder trigger condition is to determine that the current journey may cause the user to be unable to complete the event or behavior before the expected end time. For example, the user opens an online battle game application, and the average duration of a game is 20 minutes. Therefore, this event is an event with an expected end time (i.e., 20 minutes later). So, if it is determined based on the current journey dynamics (such as there are still 15 minutes until the destination) that it is likely to cause the user to be unable to complete the game normally, it is necessary to remind the user before the user starts the game;

[0044] For a persistent event or behavior, the reminder trigger condition is that the remaining time to reach the destination of the current itinerary is less than a predetermined time threshold. For example, when it is recognized that the user is sleeping, the trigger condition can be determined based on the current itinerary dynamics to wake up the user 5 minutes before arriving at the destination. It can be understood that the above method of determining the trigger condition is only an example, and other suitable reminder trigger conditions in different forms can be determined for different events or behaviors.

[0045] In step 106, obtain the current itinerary information regarding the itinerary, where the current itinerary information includes at least the time expected to reach the destination of the current itinerary. Depending on the type of the user's current itinerary and the entity executing this method, the navigation application providing the current itinerary information may run on a vehicle (such as a car) or on the user's mobile terminal. Correspondingly, the current itinerary information can be obtained from the navigation application running on the vehicle the user is taking or on the user's mobile terminal. The current itinerary information may include, but is not limited to, the departure and destination of the current itinerary, the planned route, the real-time traffic congestion situation, the distance to the destination, and the time to reach the destination, etc., where the time to reach the destination is necessary for triggering a dynamic reminder based on the itinerary later. According to an embodiment of the present invention, the current itinerary information is dynamically updated. For example, when the navigation application is connected to the network, it will refresh the latest information in real time or periodically, such as the current location, the traffic congestion situation, and the updated estimated time to reach the destination calculated based on the traffic congestion situation, etc. In other words, the time expected to reach the destination in the obtained current itinerary information is also dynamically updated.

[0046] In step 108, determine whether the reminder trigger condition is satisfied based on the obtained current itinerary information. As previously described, for the user's events or behaviors, the corresponding reminder trigger conditions have been determined. These reminder trigger conditions are all based on the itinerary information, so it is necessary to determine whether the reminder trigger condition is satisfied according to the current itinerary information. As some non-limiting examples, determining whether the trigger condition is satisfied based on the obtained current itinerary information may include, but is not limited to, the following methods:

[0047] When the time expected to reach the destination of the current itinerary is later than the predetermined start time of the event or behavior, it can be considered that the trigger condition is satisfied. For example, as previously described, for an event or behavior with a predetermined start time, the reminder trigger condition can be set to determine that the current itinerary may cause the user to be unable to execute the event or behavior at the predetermined start time. Therefore, the time expected to reach the destination of the current itinerary being later than the predetermined start time of the event or behavior is obviously one of the situations that cause the user to be unable to execute the event or behavior at the predetermined start time. For example, the predetermined start time of the event is 11 am, but the current itinerary information shows that it will take 11:10 am to reach the destination, then the reminder trigger condition is satisfied;

[0048] Similarly, when the time expected to reach the destination of the current trip is less than the threshold time amount earlier than the scheduled start time of an event or action, the trigger condition can be considered to be met. It can be understood that when traveling by a means of transportation, there may not be a complete coincidence between the destination reached by the means of transportation and the location where the actual event takes place. For example, when going to the cinema to watch a movie, the means of transportation can only stop at the entrance of the shopping mall where the cinema is located or the parking lot, and it still takes a little time for the user to get off and walk to the cinema. It may also take a little time to buy or exchange movie tickets. Therefore, it is reasonable to reserve an appropriate amount of time (such as 10 minutes). In this case, if the scheduled start time of the event is 11 o'clock, and the current trip information shows that it will take until 10:55 to reach the destination, although it is earlier than the scheduled start time, it is less than the 10-minute margin that is expected to be reserved. Therefore, the reminder trigger condition is still met;

[0049] When the time expected to reach the destination of the current trip is earlier than the expected end time of an event or action, the trigger condition can be considered to be met. For example, as described before, for an event or action with an expected end time, the reminder trigger condition is to determine that the current trip may cause the user to be unable to complete the event or action before the expected end time. Therefore, the time expected to reach the destination of the current trip being earlier than the expected end time of an event or action is one of the situations that may cause the user to be unable to complete the event or action normally. For example, as previously exemplified, the time expected for a new game session is 20 minutes, but the current trip information shows that there are still 15 minutes to reach the destination. Therefore, the user may not be able to complete a new game session without being affected, and at this time the reminder trigger condition is also met; or

[0050] When the remaining time expected to reach the destination of the current trip is less than the preset duration threshold, the trigger condition can be considered to be met. As described before, for a continuous event or action, the reminder trigger condition is to determine that the remaining time expected to reach the destination of the current trip is less than the preset duration threshold. For example, when the user is sleeping, according to the reminder advance amount set by the user himself or the default advance amount, the user can be woken up before reaching the destination of the current trip. If this advance amount has been reached according to the current dynamic trip, such as 5 minutes or 10 minutes before arrival, then the reminder trigger condition is met.

[0051] Finally, at step 110, in response to the reminder trigger condition being satisfied, a reminder is sent to the user. The way of sending the reminder can be various, and it can be sent either by the means of transportation or by the user's mobile terminal. For example, if the user is taking a car, the in-vehicle audio system can be used to remind the user by voice that congestion may delay the next schedule, or that there is not enough time to start a new game, or the user can be woken up from sleep by one or a combination of ways such as music, alarm, ambient light, curtain opening, etc. Similarly, the mobile terminal can also remind the user by voice, or can remind the user who is using the mobile terminal through a banner notification on the mobile terminal. It can be understood that the above reminder methods are only examples, and any reminder method suitable for reminding the user of the impact of the itinerary dynamics on their schedule events or behaviors can also be adopted.

[0052] It can be understood that the current itinerary information of the present invention is continuously updated, which is also the basis for the dynamic trigger reminder of the present invention. Therefore, the judgment of whether the reminder trigger condition is satisfied is dynamic and repeated. For example, in response to the update of the current itinerary information, it can be determined again whether the trigger condition is satisfied. These reminders are very beneficial to the user. For example, the user can be notified as early as possible when they are not aware that the subsequent itinerary may be delayed, so that they can make preparations in advance. For example, when they may miss a flight or train, they can change the ticket as early as possible, and so on.

[0053] According to an optional embodiment of the present invention, the reminder trigger condition is set by self-learning based at least in part on the observation of the user's historical behavior. As previously exemplified, the advance amount of the reminder event for a persistent event can be set or defaulted by the user. In fact, this advance amount can be learned based on technologies such as machine learning. For example, the user has given an instruction to wake him up 10 minutes before arriving at the destination by himself, or when trying to wake up the user by default 5 minutes in advance, it is detected that the user does not have enough time to get ready to get off the vehicle within 5 minutes, then the default time amount can be extended to 10 minutes, and vice versa. As another example, how long it takes from the user's destination to the destination of the corresponding itinerary in the daily schedule, and whether more time needs to be reserved, can be learned and trained based on the statistical data and samples of the actual situations of different scenarios, so as to make a reasonable prediction. For example, the time required to complete a game for different games is different, and the time required to arrive at the airport and railway station in advance for taking a plane and a train is different, and so on.

[0054] The above describes the itinerary-based dynamic reminder method of the present invention. It can be seen that this dynamic reminder method allows adding many reminder times that were not originally supported, such as how many minutes before arriving at the destination to remind, which is not supported by the existing schedule or alarm functions. In addition, the itinerary-based dynamic reminder method can provide users with many additional intelligent reminders. For example, when the remaining itinerary time is not enough to complete an online game round, it can remind the user not to start a new game, which brings an enhanced user experience to the user.

[0055] Figure 2 FIG. 4 is a schematic structural diagram of an itinerary-based dynamic reminder system 200 according to an embodiment of the present invention. As previously described, the itinerary-based dynamic reminder method of the present invention can be executed either by the transportation means the user is taking or by the mobile terminal the user is using. Correspondingly, the dynamic reminder system 200 can be implemented either on the transportation means the user is taking or on the mobile terminal the user is using. For example, it can be part of the software and hardware of the transportation means and the mobile terminal.

[0056] As Figure 2 shown in FIG. 4, the itinerary-based dynamic reminder system 200 may include an itinerary information acquisition module 202, a reminder management module 204, and a reminder module 206. The itinerary information acquisition module 202 may be configured to acquire current itinerary information about the itinerary, where the current itinerary information at least includes the time expected to arrive at the destination of the current itinerary. The reminder management module 204 may be configured to: acquire events or behaviors associated with the user; determine reminder trigger conditions for the acquired events or behaviors according to the types of the events or behaviors; determine whether the reminder trigger conditions are satisfied based on the acquired current itinerary information; and generate a reminder trigger signal in response to the reminder trigger conditions being satisfied. The reminder module 206 may be configured to issue a reminder to the user in response to the reminder trigger signal. In addition, the information acquisition module 202, the reminder management module 204, and the reminder module 206 may perform, alone or in cooperation, each step and its variants of the method described above in conjunction with Figure 1 FIG. 1.

[0057] Figure 3 FIG. 5 is a schematic structural diagram of a vehicle 300 according to an embodiment of the present invention. As Figure 3 shown in FIG. 5, the vehicle 300 may include the itinerary-based dynamic reminder system 200 described in Figure 2 FIG. 4. The dynamic reminder system 200 is implemented as part of the vehicle 300 or as an independent hardware interacting with the vehicle 300. In the scenario of being implemented as part of the vehicle 300, one or more modules in the dynamic reminder system 200 may be software and hardware components included in the vehicle 300 itself.

[0058] For example, vehicle 300 may include one or more processors and a memory. The memory may include RAM, ROM, or a combination thereof. The memory may store computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform the various functions described herein (e.g., with respect to Figure 1 the functions described).

[0059] One or more processors may include a CPU, which in some examples may be a multi-core CPU. Instructions executed at the CPU may be loaded, for example, from a program memory associated with the CPU or may be loaded from memory 306. The one or more processors may also include additional processing components customized for specific functions, such as a graphics processing unit (GPU), a digital signal processor (DSP), a neural processing unit (NPU), a multimedia processing unit. In some examples, the one or more processors may be based on the ARM or RISC-V instruction set.

[0060] An NPU is generally a dedicated circuit configured to implement the control and arithmetic logic for performing machine learning algorithms, such as algorithms for processing artificial neural networks (ANNs), deep neural networks (DNNs), random forests (RFs), etc. The NPU may sometimes be alternatively referred to as a neural signal processor (NSP), a tensor processing unit (TPU), a neural network processor (NNP), an intelligent processing unit (IPU), or a vision processing unit (VPU). The NPU may be configured to accelerate the execution of common machine learning tasks, such as image classification and various other prediction tasks. In some examples, multiple NPUs may be instantiated on a single chip (such as a system-on-chip (SoC)), while in other examples, multiple NPUs may be part of a dedicated neural network accelerator. The NPU may be optimized for training or inference, or in some cases may be configured to balance performance between training and inference. For an NPU capable of performing both training and inference, these two tasks may generally still be performed independently. An NPU designed to accelerate training is generally configured to accelerate the optimization of a new model, which is a highly computationally intensive operation involving inputting an existing dataset (often labeled or tagged), iterating over the dataset, and then adjusting model parameters (such as weights and biases) to improve model performance. Generally, optimizing based on incorrect predictions involves passing back through the layers of the model and determining gradients to reduce the prediction error. An NPU designed to accelerate inference is generally configured to operate on a trained model. Such an NPU may thus be configured to input new data segments and quickly process the data segments through the already trained model to generate a model output (e.g., an inference).

[0061] In some cases, the memory may particularly include a BIOS, which may control basic hardware or software operations, such as interactions with peripheral components or devices. The processor may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof).

[0062] Vehicle 300 may include a sensor system that can be used to identify the behavior of a user inside the vehicle, such as when the user is sleeping, reading, or on a call.

[0063] In addition, vehicle 300 may further include hardware for implementing reminders, such as an audio system, ambient lighting, sunshades, seats, etc.

[0064] In addition, vehicle 300 may further include a vehicle controller 310, which may trigger a reminder operation in response to determining that a reminder condition is met.

[0065] In addition, vehicle 300 may further include one or more wireless transceivers 312 for transmitting and receiving data via various means, protocols, and standards. In some embodiments, wireless transceiver 312 may be configured to transmit and receive data messages and elements via a short-range wireless communication protocol (e.g., Bluetooth Low Energy etc.) and / or via a local area network and / or a wide area network, and / or via a cellular network, and / or via any suitable wireless network. Of course, it should be understood that these are merely examples of networks that can be utilized by vehicle 300 over a wireless link, and the claimed subject matter is not limited in this regard. In addition, vehicle 300 may further include a Global Navigation Satellite System (GNSS) receiver 314. GNSS receiver 314 may be configured to receive and digitally process signals from navigation satellites (and / or other vehicles) in order to provide the positioning, speed, and time of the receiver. GNSS receiver 314 may include hardware and / or software components. Through these communication and positioning devices, vehicle 300 is capable of supporting real-time positioning of navigation applications running thereon and the generation and update of dynamic trip information.

[0066] It will be appreciated that the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations fall within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. The features implementing the functions may also be physically located in various positions, including being distributed such that portions of the functions are implemented at different physical locations.

[0067] The above-described content includes examples of aspects of the claimed subject matter. Of course, it is not possible to describe every conceivable combination of components or methods for purposes of depicting the claimed subject matter, but one of ordinary skill in the art will recognize that many further combinations and permutations of the claimed subject matter are possible. Accordingly, the claimed subject matter is intended to cover all such alterations, modifications, and variations that fall within the spirit and scope of the appended claims.

Claims

1. A dynamic reminder method based on itinerary, characterized in that, The dynamic reminder method includes: Obtaining events or behaviors associated with a user who is in the middle of a journey; Determining a reminder trigger condition for the obtained events or behaviors according to the types of the events or behaviors; Obtaining current journey information about the journey, where the current journey information at least includes the time expected to reach the destination of the current journey; Determining whether the reminder trigger condition is satisfied based on the obtained current journey information; and Issuing a reminder to the user in response to the reminder trigger condition being satisfied.

2. The dynamic reminder method according to claim 1, characterized in that, Obtaining events or behaviors associated with a user who is in the middle of a journey further includes one or more of the following: Obtaining the user's schedule information; Obtaining the application usage status of the user on the mobile terminal; Receiving an instruction from the user to establish a reminder event; or Identifying the user's behavior via a sensor.

3. The dynamic reminder method according to claim 1, characterized in that, The types of the events or behaviors include: events or behaviors with a predetermined start time, events or behaviors with an expected end time, and continuous events or behaviors.

4. The dynamic reminder method according to claim 3, characterized in that, The events or behaviors with a predetermined start time include: existing events in the user's schedule or new events created by the user in the schedule, The events or behaviors with an expected end time include: the user opening a game application or the user browsing a media directory or selecting media in a multimedia application, The continuous events or behaviors include: the user being in a sleep state, the user being in a reading state, or the user being in a voice call state.

5. The dynamic reminder method according to claim 3, characterized in that, Determining a reminder trigger condition for the obtained events or behaviors according to the types of the events or behaviors further includes: For the events or behaviors with a predetermined start time, the reminder trigger condition is to determine that the current journey may cause the user to be unable to execute the events or behaviors at the predetermined start time; For the events or behaviors with an expected end time, the reminder trigger condition is to determine that the current journey may cause the user to be unable to complete the events or behaviors before the expected end time; and For the continuous events or behaviors, the reminder trigger condition is to determine that the remaining time until the expected arrival at the destination of the current journey is less than a predetermined duration threshold.

6. The dynamic reminder method according to claim 5, characterized in that, Determining whether the trigger condition is satisfied based on the obtained current journey information further includes: Determining that the trigger condition is satisfied in response to any one of the following situations: The time expected to reach the destination of the current journey is later than the predetermined start time of the event or behavior; The time amount by which the time expected to reach the destination of the current journey is earlier than the predetermined start time of the event or behavior is less than the threshold time amount; The time expected to reach the destination of the current journey is earlier than the expected end time of the event or behavior; or The remaining time until the expected arrival at the destination of the current journey is less than the predetermined duration threshold.

7. The dynamic reminder method according to claim 1, characterized in that, Obtaining current journey information about the journey includes obtaining current journey information from the means of transportation the user is taking or a navigation application running on the user's mobile terminal, where the current journey information is dynamically updated.

8. The dynamic reminder method according to claim 7, characterized in that, In response to the current journey information being updated, re-determining whether the reminder trigger condition is satisfied.

9. The dynamic reminder method according to claim 1, characterized in that, The reminder trigger condition is set at least partially through self-learning based on the observation of the user's historical behavior.

10. The dynamic reminder method according to any one of claims 1-9, characterized in that, The dynamic reminder method is executed by the vehicle in which the user is riding or by the user's mobile terminal.

11. A trip-based dynamic reminder system, comprising: A trip information acquisition module, which is configured to acquire current trip information regarding the trip, where the current trip information at least includes the time expected to reach the destination of the current trip; A reminder management module, which is configured to: Acquire events or behaviors associated with the user; Determine a reminder trigger condition for the acquired events or behaviors according to the type of the events or behaviors; Determine whether the reminder trigger condition is satisfied based on the acquired current trip information; And In response to the reminder trigger condition being satisfied, generate a reminder trigger signal; And A reminder module, which is configured to issue a reminder to the user in response to the reminder trigger signal.

12. The dynamic reminder system according to claim 11, wherein, Acquiring events or behaviors associated with the user in the vehicle further includes one or more of the following: Acquiring the user's schedule information; Acquiring the application usage status of the user on the mobile terminal; Receiving an instruction from the user to establish a reminder event; Or Identifying the user's behavior via a sensor, Determining a reminder trigger condition for the acquired events or behaviors according to the type of the events or behaviors further includes: For an event or behavior with a predetermined start time, the reminder trigger condition is to determine that the current trip may cause the user to be unable to execute the event or behavior at the predetermined start time; For an event or behavior with an expected end time, the reminder trigger condition is to determine that the current trip may cause the user to be unable to complete the event or behavior before the expected end time; and For a persistent event or behavior, the reminder trigger condition is to determine that the remaining time until the expected arrival at the destination of the current trip is less than a predetermined duration threshold, Determining whether the trigger condition is satisfied based on the acquired current trip information further includes: In response to any one of the following situations, determining that the trigger condition is satisfied: The time expected to reach the destination of the current trip is later than the predetermined start time of the event or behavior; The time by which the time expected to reach the destination of the current trip is earlier than the predetermined start time of the event or behavior is less than a threshold time amount; The time expected to reach the destination of the current trip is earlier than the expected end time of the event or behavior; or The remaining time until the expected arrival at the destination of the current trip is less than the predetermined duration threshold.

13. The dynamic reminder system according to claim 11, wherein, Acquiring current trip information regarding the trip includes acquiring current trip information from the vehicle in which the user is riding or from a navigation application running on the user's mobile terminal, where the current trip information is dynamically updated, and The reminder management module is further configured to: in response to the current trip information being updated, re-determine whether the trigger condition is satisfied.

14. The dynamic reminder system according to claim 11, wherein, The reminder management module is further configured to: set the reminder trigger condition through self-learning based at least in part on the observation of the user's historical behavior.

15. A vehicle, wherein, Including the dynamic reminder system according to any one of claims 11-14.

Images