Prompt method and apparatus for on-board terminal, and device and storage medium

Abstract

Disclosed in the present application are a prompt method and apparatus for an on-board terminal, and a device and a storage medium, which are used for solving conflicts between various services in a smart cockpit. The method in the present application comprises: acquiring configuration parameters of a first prompt event that has occurred, wherein the configuration parameters comprise a prompt mode; determining whether there is a second prompt event; if it is determined that there is a second prompt event, acquiring configuration parameters of the second prompt event; on the basis of the configuration parameters of the first prompt event and the configuration parameters of the second prompt event, determining a target prompt event from the first prompt event and the second prompt event; and on the basis of a prompt mode corresponding to the target prompt event, displaying target prompt content corresponding to the target prompt event. In the present application, when there is a second prompt event, if a first prompt event has occurred, the execution sequence of the second prompt event and the first prompt event is determined on the basis of set configuration parameters, thereby avoiding conflict between the prompt events.

Description

A reminder method, device, equipment and storage medium for a vehicle terminal

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on August 30, 2023, with application number 202311128892.9 and application name “A reminder method, device, equipment and storage medium for a vehicle-mounted terminal”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the technical field of terminal equipment, and in particular to a reminder method, device, equipment and storage medium for a vehicle-mounted terminal. Background Art

[0003] With the gradual development of smart cockpits, various manufacturers are planning or implementing smart reminder services within the cockpit, proactively providing users with more personalized and immersive "smart reminder services" and allowing them to more deeply perceive the "intelligence" of their products. In related technologies, the increasing number of services integrated into smart cockpits has led to a significant increase in conflicts among these smart reminder services. Without a standardized conflict resolution mechanism, this can lead to confusion in the processing logic of smart reminder services.

[0004] Summary of the Invention

[0005] In view of this, the present application provides a reminder method, device, equipment and storage medium for a vehicle terminal to facilitate resolving conflicts between various services in a smart cockpit.

[0006] In a first aspect, an embodiment of the present application provides a reminder method for a vehicle-mounted terminal, the method comprising:

[0007] Obtaining configuration parameters of a first reminder event, wherein the configuration parameters include a reminder mode;

[0008] Determine whether there is a second reminder event; the second reminder event includes: a reminder event currently being executed or a reminder event in a queue of reminder events to be executed;

[0009] If it is determined that the second reminder event exists, obtaining configuration parameters of the second reminder event;

[0010] Determining a target reminder event from the first reminder event and the second reminder event based on the configuration parameters of the first reminder event and the configuration parameters of the second reminder event;

[0011] The target reminder content corresponding to the target reminder event is displayed based on the reminder mode corresponding to the target reminder event.

[0012] In the present application, if a first reminder event occurs while a second reminder event is being executed, the execution order of the second reminder event and the first reminder event is determined by setting configuration parameters, thereby avoiding conflicts between reminder events.

[0013] In some possible embodiments, obtaining the configuration parameters of the first reminder event includes:

[0014] The configuration parameters of the first reminder event are obtained from a cloud; the cloud is used to store the configuration parameters of the first reminder event and to update at least one configuration parameter of at least one of the first reminder events.

[0015] In this application, in the later application process, technical personnel can update the configuration parameters of the first reminder event according to user needs, further ensuring the user experience.

[0016] In some possible embodiments, the configuration parameters further include an event priority corresponding to the reminder event; and determining a target reminder event from the first reminder event and the second reminder event based on the configuration parameters of the first reminder event and the configuration parameters of the second reminder event includes:

[0017] comparing the event priority of the first reminder event with the event priority of the second reminder event;

[0018] If the event priority of the first reminder event is higher than the event priority of the second reminder event, taking the first reminder event as the target reminder event;

[0019] If the event priority of the first reminder event is lower than the event priority of the second reminder event, taking the second reminder event as the target reminder event;

[0020] If the event priority of the first reminder event is equal to the event priority of the second reminder event, the first reminder event or the second reminder event is used as the target reminder event.

[0021] In this application, event priorities are set, and the target reminder event can be accurately determined by comparing the event priorities, thereby avoiding event conflicts.

[0022] In some possible embodiments, the configuration parameters include a mode priority corresponding to the reminder mode, and determining a target reminder event from the first reminder event and the second reminder event based on the configuration parameters of the first reminder event and the configuration parameters of the second reminder event includes:

[0023] comparing the mode priority corresponding to the reminder mode of the first reminder event with the mode priority corresponding to the reminder mode of the second reminder event;

[0024] If the mode priority of the first reminder event is higher than the mode priority of the second reminder event, taking the first reminder event as the target reminder event;

[0025] If the mode priority of the first reminder event is lower than the mode priority of the second reminder event, taking the second reminder event as the target reminder event;

[0026] If the mode priority of the first reminder event is equal to the mode priority of the second reminder event, the first reminder event or the second reminder event is used as the target reminder event.

[0027] In this application, the mode priority of the reminder mode can be set, and the target reminder event can be accurately determined by comparing the mode priorities, thereby avoiding event conflicts.

[0028] In some possible embodiments, the configuration parameters further include an event priority; and determining a target reminder event from the first reminder event and the second reminder event based on the configuration parameters of the first reminder event and the configuration parameters of the second reminder event includes:

[0029] comparing the categories of the reminder mode of the first reminder event and the categories of the reminder mode of the second reminder event, the categories of the reminder mode including displaying a card, playing a voice, and displaying a card and playing a voice;

[0030] If the category of the reminder mode of the first reminder event is the same as the category of the reminder mode of the second reminder event, comparing the event priority of the first reminder event with the event priority of the second reminder event;

[0031] If the event priority of the first reminder event is higher than the event priority of the second reminder event, taking the first reminder event as the target reminder event;

[0032] If the event priority of the first reminder event is lower than the event priority of the second reminder event, taking the second reminder event as the target reminder event;

[0033] If the event priority of the first reminder event is equal to the event priority of the second reminder event, the first reminder event or the second reminder event is used as the target reminder event.

[0034] In the present application, the target reminder event can be determined by the category of the reminder mode and the event priority, so that the determination of the target reminder event is more accurate.

[0035] In some possible embodiments, the first reminder event includes at least one reminder content, the second reminder event includes at least one reminder content, and the configuration parameter further includes a content priority corresponding to the reminder content; after comparing the category of the reminder mode of the first reminder event and the category of the reminder mode of the second reminder event, the method further includes:

[0036] If the category of the reminder mode of the first reminder event is different from the category of the reminder mode of the second reminder event, determining the category of the reminder mode corresponding to the reminder content in the first reminder event and the category of the reminder mode corresponding to the reminder content in the second reminder event;

[0037] If the category of the reminder mode corresponding to the reminder content in the first reminder event is different from the category of the reminder mode corresponding to the reminder content in the second reminder event, then the first reminder event and the second reminder event are used as target reminder events;

[0038] If it is determined that the first reminder event contains reminder content of the same category as the reminder mode corresponding to the reminder content in the second reminder event, the content priority of the first target reminder content is compared with the content priority of the second target reminder content to obtain the target reminder event; wherein the first target reminder content is the reminder content of the same category as the reminder mode corresponding to the reminder content included in the first reminder event, and the second target reminder content is the reminder content of the same category as the reminder mode corresponding to the reminder content included in the second reminder event.

[0039] In some possible embodiments, comparing the content priority of the first target reminder content with the content priority of the second target reminder content to obtain the target reminder event includes:

[0040] If the content priority of the first target reminder content is higher than the content priority of the second target reminder content, taking the first reminder event as the target reminder event;

[0041] If the content priority of the first target reminder content is lower than the content priority of the second target reminder content, taking the second reminder event as the target reminder event;

[0042] If the content priority of the first target reminder content is equal to the content priority of the second target reminder content, the first reminder event or the second reminder event is used as the target reminder event.

[0043] In some possible embodiments, the reminder mode includes any one of the following: displaying a static card, displaying a dynamic card, displaying a dynamic card and playing a voice, displaying a static card and playing a voice, and playing a voice.

[0044] In this application, multiple reminder modes are set up to make this application more universal and further ensure the user experience.

[0045] In some possible embodiments, determining whether a second reminder event exists includes:

[0046] If it is determined that there is a reminder event currently being executed, then it is determined that there is a second reminder event, where the second reminder event is the reminder event currently being executed;

[0047] If it is determined that there is no reminder event currently being executed, and it is determined that there is a reminder event in the reminder event queue to be executed, then it is determined that there is the second reminder event, and the second reminder event is determined based on the reminder event queue to be executed.

[0048] In some possible embodiments, after determining a target reminder event from the first reminder event and the second reminder event based on the configuration parameters of the first reminder event and the configuration parameters of the second reminder event, the method further includes:

[0049] Ignore non-target reminder events; or add the non-target reminder events to a queue of reminder events to be executed;

[0050] If the first reminder event is a target reminder event, the non-target reminder event is the second reminder event; if the second reminder event is a target reminder event, the non-target reminder event is the first reminder event.

[0051] In some possible embodiments,

[0052] Ignoring non-target reminder events includes:

[0053] If the non-target reminder event is the second reminder event, terminating the execution of the second reminder event; or,

[0054] If the non-target reminder event is the first reminder event, the first reminder event is eliminated.

[0055] In some possible embodiments, the configuration parameter further includes an event priority; and adding the non-target reminder event to a queue of reminder events to be executed includes:

[0056] Determining whether the non-target reminder event is a reminder event in a queue of reminder events to be executed;

[0057] If yes, then add the non-target reminder event to the end of the reminder event queue to be executed; or

[0058] determining a target position of the non-target reminder event in the queue of reminder events to be executed according to the event priority of the non-target reminder event and the event priority of the reminder events in the queue of reminder events to be executed;

[0059] The non-target reminder event is added to the target position in the reminder event queue to be executed.

[0060] In some possible embodiments, the method further includes:

[0061] Based on the exit signal of the target reminder event, the target reminder event is ignored.

[0062] In some possible embodiments, the method further includes:

[0063] Based on an exit signal corresponding to a reminder event in the to-be-executed reminder event queue, the reminder event is removed from the to-be-executed reminder event queue.

[0064] In some possible embodiments, after determining whether the second reminder event exists, the method further includes:

[0065] If it is determined that the second reminder event does not exist, the first reminder event is used as the target reminder event.

[0066] In a second aspect, an embodiment of the present application provides a reminder device for a vehicle-mounted terminal, the device comprising:

[0067] An acquisition module, configured to acquire configuration parameters of the first reminder event, wherein the configuration parameters include a reminder mode;

[0068] A second reminder event determination module is configured to determine whether a second reminder event exists; the second reminder event includes a reminder event currently being executed or a reminder event in a queue of reminder events to be executed;

[0069] a target reminder event determination module, configured to, when determining that the second reminder event exists, determine a target reminder event from the first reminder event and the second reminder event based on the configuration parameters of the first reminder event and the configuration parameters of the second reminder event;

[0070] An execution module is configured to display target reminder content corresponding to the target reminder event based on a reminder mode corresponding to the target reminder event.

[0071] In some possible embodiments, the acquisition module is specifically configured to:

[0072] The configuration parameters of the first reminder event are obtained from the cloud.

[0073] In some possible embodiments, the configuration parameters further include event priority; and the target reminder event determination module is specifically configured to:

[0074] comparing the event priority of the first reminder event with the event priority of the second reminder event;

[0075] If the event priority of the first reminder event is higher than the event priority of the second reminder event, taking the first reminder event as the target reminder event;

[0076] If the event priority of the first reminder event is lower than the event priority of the second reminder event, taking the second reminder event as the target reminder event;

[0077] If the event priority of the first reminder event is equal to the event priority of the second reminder event, the first reminder event or the second reminder event is used as the target reminder event.

[0078] In some possible embodiments, the configuration parameters include a mode priority corresponding to the reminder mode, and the target reminder event determination module is specifically configured to:

[0079] comparing the mode priority corresponding to the reminder mode of the first reminder event with the mode priority corresponding to the reminder mode of the second reminder event;

[0080] If the mode priority of the first reminder event is higher than the mode priority of the second reminder event, taking the first reminder event as the target reminder event;

[0081] If the mode priority of the first reminder event is lower than the mode priority of the second reminder event, taking the second reminder event as the target reminder event;

[0082] If the mode priority of the first reminder event is equal to the mode priority of the second reminder event, the first reminder event or the second reminder event is used as the target reminder event.

[0083] In some possible embodiments, the configuration parameters further include event priority; and the target reminder event determination module is specifically configured to:

[0084] comparing the categories of the reminder mode of the first reminder event and the categories of the reminder mode of the second reminder event, the categories of the reminder mode including displaying a card, playing a voice, and displaying a card and playing a voice;

[0085] If the category of the reminder mode of the first reminder event is the same as the category of the reminder mode of the second reminder event, comparing the event priority of the first reminder event with the event priority of the second reminder event;

[0086] If the event priority of the first reminder event is higher than the event priority of the second reminder event, taking the first reminder event as the target reminder event;

[0087] If the event priority of the first reminder event is lower than the event priority of the second reminder event, taking the second reminder event as the target reminder event;

[0088] If the event priority of the first reminder event is equal to the event priority of the second reminder event, the first reminder event or the second reminder event is used as the target reminder event.

[0089] In some possible embodiments, the first reminder event includes at least one reminder content, the second reminder event includes at least one reminder content, and the configuration parameter further includes a content priority corresponding to the reminder content; the target reminder event determination module is further configured to:

[0090] If the category of the reminder mode of the first reminder event is different from the category of the reminder mode of the second reminder event, determining the category of the reminder mode corresponding to the reminder content in the first reminder event and the category of the reminder mode corresponding to the reminder content in the second reminder event;

[0091] If the category of the reminder mode corresponding to the reminder content in the first reminder event is different from the category of the reminder mode corresponding to the reminder content in the second reminder event, then the first reminder event and the second reminder event are used as target reminder events;

[0092] If it is determined that the first reminder event contains reminder content of the same category as the reminder mode corresponding to the reminder content in the second reminder event, the content priority of the first target reminder content is compared with the content priority of the second target reminder content to obtain the target reminder event; wherein the first target reminder content is the reminder content of the same category as the reminder mode corresponding to the reminder content included in the first reminder event, and the second target reminder content is the reminder content of the same category as the reminder mode corresponding to the reminder content included in the second reminder event.

[0093] In some possible embodiments, the target reminder event determination module is specifically configured to:

[0094] If the content priority of the first target reminder content is higher than the content priority of the second target reminder content, taking the first reminder event as the target reminder event;

[0095] If the content priority of the first target reminder content is lower than the content priority of the second target reminder content, taking the second reminder event as the target reminder event;

[0096] If the content priority of the first target reminder content is equal to the content priority of the second target reminder content, the first reminder event or the second reminder event is used as the target reminder event.

[0097] In some possible embodiments, the reminder mode includes any one of the following: displaying a static card, displaying a dynamic card, displaying a dynamic card and playing a voice, displaying a static card and playing a voice, and playing a voice.

[0098] In some possible embodiments, the second reminder event determination module is specifically configured to:

[0099] If it is determined that there is a reminder event currently being executed, then it is determined that there is a second reminder event, where the second reminder event is the reminder event currently being executed;

[0100] If it is determined that there is no reminder event currently being executed, and it is determined that there is a reminder event in the reminder event queue to be executed, then it is determined that there is the second reminder event, and the second reminder event is determined based on the reminder event queue to be executed.

[0101] In some possible embodiments, the target reminder event determination module is further configured to:

[0102] Ignore non-target reminder events; or add the non-target reminder events to a queue of reminder events to be executed;

[0103] If the first reminder event is a target reminder event, the non-target reminder event is the second reminder event; if the second reminder event is a target reminder event, the non-target reminder event is the first reminder event.

[0104] In some possible embodiments, the target reminder event determination module is specifically configured to:

[0105] If the non-target reminder event is the second reminder event, terminating the execution of the second reminder event; or,

[0106] If the non-target reminder event is the first reminder event, the first reminder event is eliminated.

[0107] In some possible embodiments, the configuration parameters further include event priority; and the target reminder event determination module is specifically configured to:

[0108] Determining whether the non-target reminder event is a reminder event in a queue of reminder events to be executed;

[0109] If yes, then add the non-target reminder event to the end of the reminder event queue to be executed; or

[0110] determining a target position of the non-target reminder event in the queue of reminder events to be executed according to the event priority of the non-target reminder event and the event priority of the reminder events in the queue of reminder events to be executed;

[0111] The non-target reminder event is added to the target position in the reminder event queue to be executed.

[0112] In some possible embodiments, the execution module is further configured to:

[0113] Based on the exit signal of the target reminder event, the target reminder event is ignored.

[0114] In some possible embodiments, the execution module is further configured to:

[0115] Based on an exit signal corresponding to a reminder event in the to-be-executed reminder event queue, the reminder event is removed from the to-be-executed reminder event queue.

[0116] In some possible embodiments, the second reminder event determination module is further configured to:

[0117] If it is determined that the second reminder event does not exist, the first reminder event is used as the target reminder event.

[0118] In the third aspect, another embodiment of the present application also provides an electronic device, comprising at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute any one of the methods provided in the embodiment of the first aspect of the present application.

[0119] In a fourth aspect, another embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute any method provided in the embodiment of the first aspect of the present application.

[0120] Other features and advantages of the present application will be described in the following description, and in part will become apparent from the description, or will be understood by practicing the present application. The purposes and other advantages of the present application can be realized and obtained by the structures particularly pointed out in the written description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0121] FIG1 is a schematic diagram of a display method of a reminder event in a related art of a reminder method for an in-vehicle terminal provided in an embodiment of the present application;

[0122] FIG2 is a schematic diagram corresponding to another reminder event in the related art of a reminder method for an in-vehicle terminal provided in an embodiment of the present application;

[0123] FIG3 is a schematic diagram of an in-vehicle terminal and a cloud for processing a reminder event in a related art of a reminder method for an in-vehicle terminal provided in an embodiment of the present application;

[0124] FIG4 is a schematic diagram of the interaction flow between an in-vehicle terminal and a cloud terminal when processing a reminder event in a reminder method of an in-vehicle terminal provided by an embodiment of the present application;

[0125] FIG5 is a schematic diagram of an application scenario of a reminder method for a vehicle terminal provided in an embodiment of the present application;

[0126] FIG6A is a flow chart of a reminder method for a vehicle terminal provided in an embodiment of the present application;

[0127] FIG6B is a schematic diagram of a static card displayed in a reminder method of an in-vehicle terminal provided in an embodiment of the present application;

[0128] FIG6C is a schematic diagram of a dynamic card displayed in a reminder method of an in-vehicle terminal provided in an embodiment of the present application;

[0129] FIG6D is a schematic diagram of a method for displaying a dynamic card and playing voice in a vehicle-mounted terminal reminder according to an embodiment of the present application;

[0130] FIG7 is a flow chart of determining a target reminder event based on event priority in a reminder method for an in-vehicle terminal provided by an embodiment of the present application;

[0131] FIG8 is a schematic diagram showing the event priority of a reminder method of a vehicle terminal provided in an embodiment of the present application;

[0132] FIG9 is a schematic diagram showing the content priority of a reminder method for an in-vehicle terminal provided in an embodiment of the present application;

[0133] FIG10 is a flow chart of determining a target reminder event based on mode priority in a reminder method for an in-vehicle terminal according to an embodiment of the present application;

[0134] FIG11 is a schematic diagram showing a reminder mode of a reminder method of a vehicle-mounted terminal provided by an embodiment of the present application displayed on a display screen of the vehicle-mounted terminal;

[0135] FIG12 is a schematic diagram of a measurement index of the priority of a reminder mode of a reminder method of a vehicle-mounted terminal provided in an embodiment of the present application;

[0136] FIG13 is a schematic diagram of the measurement indicators and weights of the priority of the reminder mode of a reminder method of an in-vehicle terminal provided in an embodiment of the present application;

[0137] FIG14 is a schematic diagram of the mode priority of a reminder method of a vehicle terminal provided in an embodiment of the present application;

[0138] FIG15 is a flow chart of determining a target reminder event based on a reminder mode and an event priority in a reminder method for an in-vehicle terminal according to an embodiment of the present application;

[0139] 16 is a schematic diagram of a flow chart of determining a target reminder event when the category of the reminder mode of the reminder event is different from the category of the reminder mode of the second reminder event in a reminder method of a vehicle-mounted terminal provided by an embodiment of the present application;

[0140] FIG17 is a schematic diagram of categories of reminder modes of a reminder method of a vehicle-mounted terminal provided in an embodiment of the present application;

[0141] FIG18 is a flow chart of obtaining a target reminder event based on content priority in a reminder method for an in-vehicle terminal provided by an embodiment of the present application;

[0142] FIG19 is another flowchart of a reminder method for a vehicle terminal provided in an embodiment of the present application;

[0143] FIG20 is a schematic diagram showing a priority specification corresponding to a reminder event of a reminder method of a vehicle-mounted terminal provided in an embodiment of the present application;

[0144] FIG21 is a schematic diagram of an event processing strategy of a reminder method of a vehicle terminal provided in an embodiment of the present application;

[0145] FIG22 is a flow chart of a reminder method for an in-vehicle terminal according to an embodiment of the present application in which a second reminder event does not exist;

[0146] FIG23 is a schematic diagram of the overall flow of a reminder method for a vehicle terminal provided in an embodiment of the present application;

[0147] FIG24 is a schematic diagram of the overall software-level flow of a reminder method for an in-vehicle terminal provided in an embodiment of the present application;

[0148] FIG25 is a schematic diagram of a reminder method for an in-vehicle terminal provided in an embodiment of the present application, in which the first reminder event is “indoor navigation reminder”;

[0149] FIG26 is a schematic diagram of a reminder method of an in-vehicle terminal provided in an embodiment of the present application, in which the first reminder event is “extreme weather low visibility reminder”;

[0150] FIG27 is a schematic diagram of a configuration process of configuration parameters of a reminder method for a vehicle-mounted terminal provided in an embodiment of the present application;

[0151] FIG28 is a schematic diagram of a device for a vehicle-mounted terminal reminder method provided in an embodiment of the present application;

[0152] Figure 29 is a schematic diagram of an electronic device for a reminder method of a vehicle terminal provided in an embodiment of the present application. DETAILED DESCRIPTION

[0153] The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and should not be construed as limiting the present application.

[0154] It should be clear that the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0155] The terms used in the embodiments of the present application are for the purpose of describing specific embodiments only and are not intended to limit the present application. The singular forms "a", "an", "the" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise.

[0156] It should be understood that the term "and / or" as used herein simply describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A alone, A and B together, or B alone. Furthermore, the character " / " in this document generally indicates an "or" relationship between the associated objects.

[0157] With the gradual development of smart cockpits, various manufacturers are planning or implementing smart reminder services within the cockpit, proactively providing users with more personalized and immersive "smart reminder services" and allowing them to more deeply perceive the "intelligence" of their products. In related technologies, the increasing number of services integrated into smart cockpits has led to a significant increase in conflicts among these smart reminder services. Without a standardized conflict resolution mechanism, this can lead to confusion in the processing logic of smart reminder services.

[0158] As shown in Figure 1, a vehicle terminal in the related art displays a smart reminder service. Smart reminder service displays can be divided into card reminders and card plus voice reminders. For example, a card corresponding to "Meditation Mode" may be displayed on the vehicle terminal's display screen, with the message "It's been a tiring day. Would you like to turn on meditation mode to relax?"; and / or a card corresponding to "Audiobook Subscription Update" may be displayed on the vehicle terminal's display screen, with the message "Your subscribed audiobook 'XXXX' has been updated. Would you like to play it?" Simultaneously, the vehicle terminal announces the corresponding voice packet of "Your subscribed audiobook 'XXXX' has been updated. Would you like to play it?"; and / or a card corresponding to "Collision Recognition" may be displayed on the vehicle terminal's display screen, with the message "A vehicle collision has been detected. We recommend that you learn about post-collision safety measures. Do you want to enable them?". The related art uses a single card type and lacks a standardized conflict resolution strategy. For example, when the card corresponding to "collision recognition" is being played, it is determined that "meditation mode" is triggered and the card corresponding to "meditation mode" needs to be displayed. For the user, "collision recognition" is obviously a more important event. If the card corresponding to "meditation mode" is played directly at this time, it will lead to a poor user experience.

[0159] As shown in Figure 2, it is a schematic diagram of the vehicle terminal corresponding to another reminder event in the related technology. In this method, after determining that the user gets on the vehicle, active service is provided to the user through voice. The active service form of this method is single and there is no standardized conflict handling strategy.

[0160] Figure 3 shows a schematic diagram of the vehicle terminal and cloud for processing reminder events in related technologies. The vehicle terminal includes a dialogue management module (DM), a decision service module (DS), a context awareness module (CA), a service center, and a voice processing module (Voice App). The voice processing module includes a voice kit and an ability kit. The cloud includes a dialogue management module (DM).

[0161] As shown in Figure 4, it is a schematic diagram of the interaction process when the vehicle terminal and the cloud process reminder events, in which: after the CA in the vehicle terminal senses that the first reminder event has been triggered, the first reminder event is reported to the DS in the vehicle terminal; after receiving the first reminder event, the DS reports the first reminder event to the Voice App in the vehicle terminal; the Voice App reports the first reminder event to the DM in the vehicle terminal and the DM in the cloud; after receiving the first reminder event reported by the DS, the DM in the vehicle terminal generates an event processing instruction based on the first reminder event and sends the event processing instruction to the Voice App; at the same time, after receiving the first reminder event reported by the DS, the DM in the cloud generates an event processing instruction based on the first reminder event and sends the event processing instruction to the Voice App; based on the event processing instruction received first, the Voice App calls the ability kit to obtain the card corresponding to the first reminder event from the service center; the service center returns the card to the Voice App; after receiving the card, the Voice App displays the card, and after displaying the card, the Voice App sends the processed data to the CA in the vehicle terminal.

[0162] Based on Figures 3 and 4, it can be seen that the card classification standards for active services in related technologies are not clear enough, there are many vertical categories of card scenarios but no clear specifications for card interactions, and the form of active services is single; and with the increase in active services connected, the problem of event conflicts on the voice side has increased significantly, and there is no standardized conflict handling mechanism, which leads to problems such as confusion in business processing logic.

[0163] In response to the above problems, the embodiments of the present application provide a reminder method, device, equipment and storage medium for an in-vehicle terminal, which are used to solve the above problems. The inventive concept of the present application can be summarized as follows: obtaining the configuration parameters of the first reminder event that occurs, the configuration parameters including the reminder mode; determining whether there is a second reminder event, the second reminder event including: the reminder event currently being executed or the reminder event in the queue of reminder events to be executed; if it is determined that the second reminder event exists, obtaining the configuration parameters of the second reminder event; based on the configuration parameters of the first reminder event and the configuration parameters of the second reminder event, determining the target reminder event in the first reminder event and the second reminder event; displaying the target reminder content corresponding to the target reminder event based on the reminder mode corresponding to the target reminder event.

[0164] For ease of understanding, the following describes in detail a reminder method for a vehicle terminal provided by an embodiment of the present application with reference to the accompanying drawings:

[0165] As shown in FIG5 , an application scenario diagram of a reminder method of a vehicle terminal in an embodiment of the present application is shown. The application scenario shown in FIG5 includes: a vehicle terminal 10 and a cloud 20; wherein:

[0166] The vehicle terminal 10 obtains the configuration parameters of the first reminder event that occurs, and the configuration parameters include the reminder mode; wherein the configuration parameters can be stored in the cloud 20, and can also be stored in the vehicle terminal 10; determines whether there is a second reminder event, and if it is determined that there is a second reminder event, obtains the configuration parameters of the second reminder event; based on the configuration parameters of the first reminder event and the configuration parameters of the second reminder event, determines the target reminder event in the first reminder event and the second reminder event; based on the reminder mode corresponding to the target reminder event, displays the target reminder content corresponding to the target reminder event.

[0167] The description of this application only details a single vehicle-mounted terminal 10 and cloud 20. However, those skilled in the art will appreciate that the illustrated vehicle-mounted terminal 10 and cloud 20 are intended to illustrate the operations of the vehicle-mounted terminal 10 and cloud 20 involved in the technical solution of this application. This does not imply any limitation on the number, type, or location of the vehicle-mounted terminals 10 and cloud 20. It should be noted that adding additional modules to the illustrated environment or removing individual modules from it does not change the underlying concepts of the exemplary embodiments of this application.

[0168] It should be noted that the reminder method of the vehicle-mounted terminal proposed in this application is not only applicable to the application scenario shown in Figure 5, but also applicable to any device with a reminder requirement of the vehicle-mounted terminal.

[0169] FIG6A is a flow chart of a reminder method for a vehicle terminal provided in an embodiment of the present application, wherein:

[0170] In step 601: the configuration parameters of the first reminder event that occurs are obtained, and the configuration parameters include the reminder mode.

[0171] In the present application, after determining that a first reminder event occurs, the vehicle-mounted terminal obtains configuration parameters of the first reminder event.

[0172] In some possible embodiments, the vehicle terminal may obtain event parameters through optical sensors, pressure sensors, sound sensors, radars, and other devices installed on the vehicle body, and determine whether the first reminder event has occurred based on the event parameters. For example, a child is captured by a camera in the back seat, and the pressure sensor installed on the back seat determines that the object corresponding to the current pressure value is a child; the vehicle terminal determines that a child is present in the vehicle based on the image of the child and the pressure value of the pressure sensor in the back seat, and further determines that the first reminder event has occurred, and the first reminder event is "child on board." The event parameters represent the parameter values ​​detected by the device installed on the vehicle body. For example, if the device is a pressure sensor, the event parameters are the pressure values ​​detected by the pressure sensor.

[0173] It is important to know that the correspondence between the event parameters obtained by vehicle-mounted equipment such as optical sensors, pressure sensors, sound sensors, and radars and the first reminder event is pre-set by technical personnel, that is, the vehicle-mounted terminal can determine the unique first reminder event based on the event parameters obtained by optical sensors, pressure sensors, sound sensors, radars and other equipment.

[0174] In some possible embodiments, obtaining the configuration parameters for the first reminder event can be specifically implemented by obtaining the configuration parameters for the first reminder event from the cloud. The cloud is used to store the configuration parameters for the first reminder event and to update at least one configuration parameter for at least one first reminder event. That is, when the vehicle-mounted terminal obtains the configuration parameters for the first reminder event, it can obtain the configuration parameters corresponding to the first reminder event from the cloud based on the identity identifier of the first reminder event.

[0175] In another embodiment, if the memory in the vehicle terminal has a large memory, all configuration parameters corresponding to the first reminder event can be stored in the memory in the vehicle terminal. That is, the storage method of the configuration parameters is not limited in this application, and technicians can set the storage method of the configuration parameters at their own discretion.

[0176] In some possible embodiments, in addition to storing the configuration parameters of the first reminder event, the cloud is also used to update at least one configuration parameter of at least one first reminder event. Specifically, this can be implemented by: obtaining user evaluations of each first reminder event; determining a score corresponding to each first reminder event based on the user's evaluations of each first reminder event; and adjusting the configuration parameters of each first reminder event based on the score corresponding to each first reminder event. Adjusting the configuration parameters of the first reminder event based on the user's evaluation ensures that the configuration parameters of different first reminder events better meet user needs, thereby ensuring a better user experience.

[0177] Among them, when obtaining the user's evaluation of each first reminder event, it can be obtained through a third-party platform, or through a customer group, or by actively asking the user to obtain the user's evaluation of each first reminder event. This application does not limit the method of obtaining the user's evaluation of each first reminder event.

[0178] For example: the configuration parameters include event priority, and the first reminder events currently stored in the memory include: reminder event 1, reminder event 2, and reminder event 3. The event priority corresponding to reminder event 1 is 1, the event priority corresponding to reminder event 2 is 2, and the event priority corresponding to reminder event 3 is 3; based on the user's evaluation, it is determined that reminder event 3 is more urgent than reminder event 2, so the event priority of reminder event 2 is modified to 3, and the event priority of reminder event 3 is modified to 4.

[0179] In step 602 : determine whether there is a second reminder event; the second reminder event includes: a reminder event currently being executed or a reminder event in a queue of reminder events to be executed.

[0180] In this application, in order to avoid conflicts between displaying the first reminder event and displaying the second reminder event, before processing the second reminder event, it is necessary to first determine whether the second reminder event exists. If the second reminder event exists, it is necessary to obtain the configuration parameters of the second reminder event.

[0181] In some possible embodiments, when determining whether a second reminder event exists, it can be specifically implemented as follows: if it is determined that there is a reminder event that is currently being executed, then it is determined that there is a second reminder event, and the second reminder event is the reminder event that is currently being executed; if it is determined that there is no reminder event that is currently being executed, and it is determined that there is a reminder event in the reminder event queue to be executed, then it is determined that there is a second reminder event, and the second reminder event is determined based on the reminder event queue to be executed.

[0182] That is, when it is determined that there is a reminder event currently being executed, the reminder event currently being executed is used as the second reminder event; when it is determined that there is no reminder event currently being executed, it is determined whether there is a reminder event in the reminder event queue to be executed. If so, the second reminder event is determined based on the reminder event in the reminder event queue to be executed.

[0183] In some possible embodiments, the configuration parameters include: event priority; determining the second reminder event based on the presence of a reminder event in the reminder event queue to be executed, which can be specifically implemented as: determining the reminder event with the highest event priority in the reminder event queue to be executed, and using the reminder event with the highest event priority as the second reminder event.

[0184] In step 603 : based on the configuration parameters of the first reminder event and the configuration parameters of the second reminder event, a target reminder event is determined between the first reminder event and the second reminder event.

[0185] In the present application, the target reminder event is determined by comparing the configuration parameters of the first reminder event with the configuration parameters of the second reminder event, thereby avoiding the conflict between the first reminder event and the second reminder event.

[0186] In step 604 : the target reminder content corresponding to the target reminder event is displayed based on the reminder mode corresponding to the target reminder event.

[0187] In this application, after determining the target reminder event, the vehicle terminal needs to display the target reminder content corresponding to the target reminder event according to the reminder mode corresponding to the target reminder event when executing the target reminder event.

[0188] In some possible embodiments, the reminder modes include: displaying a static card, displaying a dynamic card, displaying a dynamic card and playing a voice message, displaying a static card and playing a voice message, and playing a voice message. Displaying static cards and displaying dynamic cards are displayed in the form of cards on the display screen of the vehicle terminal, and playing a voice message is displayed in the form of a voice package through the player of the vehicle terminal.

[0189] For example: if it is determined that the reminder mode corresponding to the target reminder event is to display a static card, then the static card corresponding to the target reminder event can be displayed at a specified position in the display screen of the vehicle terminal, as shown in Figure 6B1 in Figure 6B. The specified position is a position in the display screen that does not affect the display of the default card; it can also be shown as Figure B in Figure 19, covering other content in the display screen of the vehicle terminal and only displaying the static card corresponding to the target reminder event.

[0190] If it is determined that the reminder mode corresponding to the target reminder event is to display a dynamic card, the dynamic card corresponding to the target reminder event can be displayed at a specified position in the display screen of the vehicle terminal, as shown in Figure 6C1 in Figure 6C. The specified position is a position in the display screen that does not affect the display of the default card; it can also be shown as Figure 6C2 in Figure 6C, covering other content in the display screen of the vehicle terminal and only displaying the dynamic card corresponding to the target reminder event.

[0191] If it is determined that the reminder mode corresponding to the target reminder event is to display dynamic cards and play voice, the dynamic card and voice bar corresponding to the target reminder event can be displayed at a specified position in the display screen of the vehicle terminal, as shown in Figure 6D1 in Figure 6D. The specified position is a position in the display screen that does not affect the display of the default card; it can also be shown as Figure 6D2 in Figure 6D, covering other content in the display screen of the vehicle terminal, and only displaying the dynamic card and voice bar corresponding to the target reminder event.

[0192] It should be noted that the above two display formats for executing target reminder events are merely examples, and do not limit the display format of target reminder events. During specific implementation, technicians can set the display format of target reminder events according to their needs. For example, multiple card display areas can be set on the display screen, and multiple cards can be displayed simultaneously in the set card display area. When a pending event occurs, the card corresponding to the pending event is used to replace the lowest priority card among the multiple cards based on the priority.

[0193] For ease of understanding, the following is a detailed description of the method for determining target reminder events in this application: In some possible embodiments, the configuration parameters include: event priority, reminder mode, and mode priority corresponding to the reminder mode. Based on this, three methods for determining target reminder events are set in this application, which are described below:

[0194] 1. Determine target reminder events based on event priority

[0195] In some possible embodiments, based on the configuration parameters of the first reminder event and the configuration parameters of the second reminder event, determining the target reminder event from the first reminder event and the second reminder event can be specifically implemented as shown in FIG. 7 , wherein:

[0196] In step 701 : the event priority of the first reminder event is compared with the event priority of the second reminder event.

[0197] In this application, in order to clarify the unified interaction specifications, a clear event priority is defined, that is, corresponding event priorities are set for all first reminder events. For example, as shown in Figure 8, the event priority table shows that the first reminder event is "Mobile phone forgotten reminder" and the second reminder event is "Weather reminder". Through the event priority table, it can be determined that the event priority corresponding to the first reminder event "Mobile phone forgotten reminder" is 3, and the event priority corresponding to the second reminder event "Weather reminder" is 5.

[0198] It should be noted that FIG. 8 is only an embodiment and does not limit the priority of the first reminder event. During specific implementation, technicians can set the priority of the first reminder event according to their needs.

[0199] In step 702 : if the event priority of the first reminder event is higher than the event priority of the second reminder event, the first reminder event is used as the target reminder event.

[0200] For example: Continuing with Figure 8 as an example, through the event priority table, it can be determined that the event priority corresponding to the first reminder event "Mobile phone forgotten reminder" is 3, and the event priority corresponding to the second reminder event "Weather reminder" is 5. It is determined that the event priority of the first reminder event is higher than the event priority of the second reminder event, and the first reminder event "Mobile phone forgotten reminder" is used as the target reminder event.

[0201] In step 703 : if the event priority of the first reminder event is lower than the event priority of the second reminder event, the second reminder event is used as the target reminder event.

[0202] For example: determine that the first reminder event is "broadcast event reminder of third-party application", and continue to take Figure 8 as an example. Through the event priority table, it can be determined that the event priority corresponding to the first reminder event "broadcast event reminder of third-party application" is 6, and the event priority corresponding to the second reminder event "weather reminder" is 5. It is determined that the event priority of the first reminder event is lower than the event priority of the second reminder event, and the second reminder event "weather reminder" is used as the target reminder event.

[0203] In step 704 : if the event priority of the first reminder event is equal to the event priority of the second reminder event, the first reminder event or the second reminder event is used as the target reminder event.

[0204] For example: determine that the first reminder event is "traffic condition reminder", and continue to take Figure 8 as an example. Through the event priority table, it can be determined that the event priority corresponding to the first reminder event "traffic condition reminder" is 5, and the event priority corresponding to the second reminder event "weather reminder" is 5. Then it is determined that the event priority of the second reminder event is equal to the event priority of the first reminder event, and any one of the second reminder event and the first reminder event can be used as the target reminder event.

[0205] In other possible embodiments, in order to accurately determine the target reminder event when the event priority of the first reminder event is equal to the event priority of the second reminder event, the content priority can be set in the configuration parameters. The content priority is used to determine the target reminder event when the event priority of the first reminder event is equal to the event priority of the second reminder event.

[0206] For example: As shown in Figure 9, it is a content priority table, which determines that the first reminder event is "traffic condition reminder", and the second reminder event is "weather reminder"; through the event priority table, it can be determined that the event priority corresponding to the first reminder event "traffic condition reminder" is 5, and the event priority corresponding to the second reminder event "weather reminder" is 5, then the event priority of the second reminder event is equal to the event priority of the first reminder event, and the content priority of the first reminder event "traffic condition reminder" is determined to be 3, and the content priority of the second reminder event "weather reminder" is determined to be 5, then the content priority of the first reminder event "traffic condition reminder" is higher than the content priority of the second reminder event "weather reminder", and the first reminder event "traffic condition reminder" is used as the target reminder event.

[0207] It should be noted that Figure 9 only provides an embodiment and does not limit the content priority. In specific implementation, if the content priority of the first reminder event is the same as the content priority of the second reminder event, the second content priority can also be set until a unique target reminder event can be determined based on the priority. That is, this application does not limit the number of levels for setting content priority.

[0208] 2. Determine target reminder events based on mode priority

[0209] In some possible embodiments, based on the configuration parameters of the first reminder event and the configuration parameters of the second reminder event, determining the target reminder event from the first reminder event and the second reminder event can be specifically implemented as shown in FIG. 10 , wherein:

[0210] In step 1001 : the mode priority corresponding to the reminder mode of the first reminder event is compared with the mode priority corresponding to the reminder mode of the second reminder event.

[0211] In some possible embodiments, the present application divides the reminder mode into: displaying a static card, displaying a dynamic card, displaying a dynamic card and playing a voice, displaying a static card and playing a voice, and playing a voice. As shown in Figure 11, displaying a static card is displayed in card mode on the display screen of the vehicle terminal, displaying a dynamic card is displayed in the form of a dynamic card on the display screen, displaying a dynamic card and playing a voice is displayed in the form of a dynamic card and a voice bar on the display screen of the vehicle terminal and the voice is played through the player of the vehicle terminal at the same time, and playing a voice is displayed in the form of a voice bar on the display screen of the vehicle terminal and the voice is played through the player of the vehicle terminal.

[0212] When setting the mode priority of the reminder mode, importance, urgency and cost can be used as measurement indicators. As shown in Figure 12, importance represents the importance of the first reminder event to the user, which can be divided into unimportant, generally important and very important; urgency represents the urgency of the first reminder event to the user, which can be divided into unurgent, generally urgent and very urgent; cost represents the cognitive cost to the user, which can be divided into low cost, medium cost and high cost.

[0213] As shown in Figure 13, each reminder mode's score is calculated based on its importance, urgency, and cost, as well as its importance weight, urgency weight, and cost weight. Based on technical experience, the importance weight can be set to 50%, the urgency weight to 30%, and the cost weight to 20%. Reminder modes are prioritized based on their scores and pre-set scores.

[0214] For example, set 0-50 points to level 3, 50-80 to level 2, and 80-100 to level 1.

[0215] It should be noted that the method for setting the mode priority of the reminder mode given above in this application is only an embodiment and is not a limitation to this. During specific implementation, technical personnel can also set the mode priority of each reminder mode based on experience.

[0216] In step 1002 : if the mode priority of the first reminder event is higher than the mode priority of the second reminder event, the first reminder event is used as the target reminder event.

[0217] For example, as shown in Figure 14, the mode priority for displaying dynamic cards and playing voice is determined to be level 1, the mode priority for displaying static cards and playing voice is determined to be level 2, the mode priority for displaying dynamic cards is determined to be level 3, the mode priority for displaying static cards is determined to be level 4, and the mode priority for playing voice is determined to be level 5. If the reminder mode of the first reminder event 1 is determined to be a purely static reminder, then the mode priority of the first reminder event 1 is determined to be level 3, and if the reminder mode of the second reminder event is determined to be a purely voice reminder, then the mode priority of the second reminder event 1 is determined to be level 4; if the mode priority of the first reminder event 1 is determined to be higher than the mode priority of the second reminder event 1, then the first reminder event 1 is used as the target reminder event.

[0218] In step 1003 : if the mode priority of the first reminder event is lower than the mode priority of the second reminder event, the second reminder event is used as the target reminder event.

[0219] For example, as shown in Figure 14, the mode priority for displaying dynamic cards and playing voice is determined to be level 1, the mode priority for displaying static cards and playing voice is determined to be level 2, the mode priority for displaying dynamic cards is determined to be level 3, the mode priority for displaying static cards is determined to be level 4, and the mode priority for playing voice is determined to be level 5. If the reminder mode of the first reminder event 1 is determined to be displaying static cards, then the mode priority of the first reminder event 1 is determined to be level 4, and if the reminder mode of the second reminder event is determined to be displaying dynamic cards, then the mode priority of the second reminder event 1 is determined to be level 3; if the mode priority of the first reminder event 1 is determined to be lower than the mode priority of the second reminder event 1, then the second reminder event 1 is used as the target reminder event.

[0220] In step 1004 : if the mode priority of the first reminder event is equal to the mode priority of the second reminder event, the first reminder event or the second reminder event is used as the target reminder event.

[0221] For example: as shown in Figure 14, the mode priority of displaying dynamic cards and playing voice is determined to be level 1, the mode priority of displaying static cards and playing voice is determined to be level 2, the mode priority of displaying dynamic cards is determined to be level 3, the mode priority of displaying static cards is determined to be level 4, and the mode priority of playing voice is determined to be level 5. If the reminder mode of the first reminder event 1 is determined to be displaying static cards, then the mode priority of the first reminder event 1 is determined to be level 4. If the reminder mode of the second reminder event is determined to be displaying static cards, then the mode priority of the second reminder event 1 is determined to be level 4. If the mode priority of the first reminder event 1 is determined to be equal to the mode priority of the second reminder event 1, then either the second reminder event 1 or the first reminder event 1 can be used as the target reminder event.

[0222] 3. Determine target reminder events based on reminder mode and event priority

[0223] In some possible embodiments, based on the configuration parameters of the first reminder event and the configuration parameters of the second reminder event, determining the target reminder event from the first reminder event and the second reminder event can be specifically implemented as shown in FIG. 15 , wherein:

[0224] In step 1501 : the category of the reminder mode of the first reminder event and the category of the reminder mode of the second reminder event are compared.

[0225] In some possible embodiments, the categories of reminder modes include: card reminder, voice reminder, and card plus voice reminder.

[0226] In step 1502 : if the category of the reminder mode of the first reminder event is the same as the category of the reminder mode of the second reminder event, then the event priority of the first reminder event is compared with the event priority of the second reminder event.

[0227] In the present application, since the reminder methods of reminder modes of the same category are the same, if the category of the reminder mode of the first reminder event is the same as the category of the reminder mode of the second reminder event, it means that the display methods of the first reminder event and the second reminder event will conflict. In order to avoid the conflict, when the category of the reminder mode of the first reminder event is the same as the category of the reminder mode of the second reminder event, the target reminder event is determined by comparing the event priority of the first reminder event with the event priority of the second reminder event.

[0228] In some possible embodiments, the situation where the category of the reminder mode of the first reminder event is the same as the category of the reminder mode of the second reminder event includes any one of the following: the category of the reminder mode of the first reminder event is the card reminder category, and the category of the reminder mode of the second reminder event is the card reminder category; the category of the reminder mode of the first reminder event is the voice reminder category, and the category of the reminder mode of the second reminder event is the voice reminder category; the category of the reminder mode of the first reminder event is the card plus voice reminder category, and the category of the reminder mode of the second reminder event is the card plus voice reminder category.

[0229] In step 1503 : if the event priority of the first reminder event is higher than the event priority of the second reminder event, the first reminder event is used as the target reminder event.

[0230] The specific implementation method of this step is the same as step 702 and will not be repeated here.

[0231] In step 1504 : if the event priority of the first reminder event is lower than the event priority of the second reminder event, the second reminder event is used as the target reminder event.

[0232] The specific implementation method of this step is the same as step 703 and will not be repeated here.

[0233] In step 1505 : if the event priority of the first reminder event is equal to the event priority of the second reminder event, the first reminder event or the second reminder event is used as the target reminder event.

[0234] The specific implementation method of this step is the same as step 704 and will not be repeated here.

[0235] In some possible embodiments, after step 1501, if it is determined that the category of the reminder mode of the first reminder event is different from the category of the reminder mode of the second reminder event, the steps shown in FIG. 16 may be implemented, wherein:

[0236] In step 1601 : if the reminder mode category of the first reminder event is different from the reminder mode category of the second reminder event, the reminder mode category corresponding to the reminder content in the first reminder event and the reminder mode category corresponding to the reminder content in the second reminder event are determined.

[0237] In the present application, when the categories of reminder modes are different, in order to further accurately determine the target reminder event, it is necessary to determine the category of the reminder mode corresponding to the reminder content.

[0238] For example: if the reminder mode category of the reminder event is card, then the reminder mode category corresponding to the reminder content of the reminder event is card; if the reminder mode category of the reminder event is voice reminder, then the reminder mode category corresponding to the reminder content of the reminder event is voice; if the reminder mode category of the reminder event is card plus voice reminder, then the reminder mode category corresponding to the reminder content of the reminder event is card and voice.

[0239] In step 1602 : if the category of the reminder mode corresponding to the reminder content in the first reminder event is different from the category of the reminder mode corresponding to the reminder content in the second reminder event, the first reminder event and the second reminder event are used as target reminder events.

[0240] In the present application, the situations in which the category of the reminder content in the first reminder event is different from the category of the reminder content in the second reminder event include: the category of the reminder mode corresponding to the reminder content in the first reminder event is card, and the category of the reminder mode corresponding to the reminder content in the second reminder event is voice; the category of the reminder mode corresponding to the reminder content in the first reminder event is voice, and the category of the reminder mode corresponding to the reminder content in the second reminder event is card.

[0241] When the category of the reminder mode corresponding to the reminder content in the first reminder event is different from the category of the reminder mode corresponding to the reminder content in the second reminder event, it means that the first reminder event and the second reminder event will not conflict when displaying the corresponding reminder content. Therefore, the first reminder event and the second reminder event can both be used as target reminder events to jointly process the first reminder event and the second reminder event.

[0242] For example: as shown in Figure 17, the category of the reminder mode of the first reminder event 1 is determined to be a card category, and the category of the reminder mode of the second reminder event 1 is determined to be a voice reminder category. Then, the card corresponding to the first reminder event 1 can be displayed on the display screen of the vehicle terminal, and the voice package corresponding to the second reminder event 1 can be played through the player.

[0243] This method avoids the conflict between the first reminder event and the second reminder event during display, while ensuring the efficiency of event processing.

[0244] In step 1603: if it is determined that the first reminder event has reminder content of the same category as the reminder mode corresponding to the reminder content in the second reminder event, the content priority of the first target reminder content is compared with the content priority of the second target reminder content to obtain the target reminder event.

[0245] The first target reminder content is the reminder content included in the first reminder event and the reminder mode category corresponding to the reminder content included in the second reminder event, and the second target reminder content is the reminder content included in the second reminder event and the reminder mode category corresponding to the reminder content included in the first reminder event.

[0246] That is, in the present application, the category of the reminder mode corresponding to the reminder content in the first reminder event and the category of the reminder mode corresponding to the reminder content in the second reminder event are partially the same, including: the category of the reminder mode corresponding to the reminder content in the first reminder event is card, and the category of the reminder mode corresponding to the reminder content in the second reminder event is card and voice; the category of the reminder mode corresponding to the reminder content in the first reminder event is voice, and the category of the reminder mode corresponding to the reminder content in the second reminder event is card and voice; the category of the reminder mode corresponding to the reminder content in the first reminder event is card and voice, and the category of the reminder mode corresponding to the reminder content in the second reminder event is card; the category of the reminder mode corresponding to the reminder content in the first reminder event is card and voice, and the category of the reminder mode corresponding to the reminder content in the second reminder event is voice.

[0247] In this case, the first reminder event will conflict with the second reminder event, so the target reminder event needs to be further determined. In this case, the reminder contents with the same reminder mode category in the first reminder event and the second reminder event can be used as the first target reminder content and the second target reminder content, respectively. The target reminder event can then be determined by comparing the content priority of the first target reminder content with the content priority of the second target reminder content.

[0248] For example: the first reminder event includes reminder content 1, and the category of reminder mode corresponding to reminder content 1 is card. The second reminder event includes reminder content 2 and reminder content 3. The category of reminder mode corresponding to reminder content 2 is card, and the category of reminder mode corresponding to reminder content 3 is voice. Then the first target reminder content is reminder content 1, and the second target reminder content is reminder content 2.

[0249] In some possible embodiments, the content priority of the first target reminder content is compared with the content priority of the second target reminder content to obtain a target reminder event, which can be specifically implemented as shown in FIG18 , wherein:

[0250] In step 1801 : if the content priority of the first target reminder content is higher than the content priority of the second target reminder content, the first reminder event is used as the target reminder event.

[0251] The specific implementation method of this step is the same as step 702 and will not be repeated here.

[0252] In step 1802 : if the content priority of the first target reminder content is lower than the content priority of the second target reminder content, the second reminder event is used as the target reminder event.

[0253] The specific implementation method of this step is the same as step 703 and will not be repeated here.

[0254] In step 1803 : if the content priority of the first target reminder content is equal to the content priority of the second target reminder content, the first reminder event or the second reminder event is used as the target reminder event.

[0255] The specific implementation method of this step is the same as step 704 and will not be repeated here.

[0256] In order to further improve the user experience and ensure the efficiency of processing the first reminder event, the embodiment of the present application also provides a reminder method of the vehicle terminal, as shown in FIG19 , wherein:

[0257] In step 1901: the configuration parameters of the first reminder event that occurs are obtained, and the configuration parameters include the reminder mode.

[0258] The specific implementation of this step is the same as that of step 601 and will not be repeated here.

[0259] In step 1902: determine whether a second reminder event exists. If it is determined that a second reminder event exists, obtain configuration parameters of the second reminder event.

[0260] The specific implementation of this step is the same as that of step 602 and will not be repeated here.

[0261] In step 1903 : based on the configuration parameters of the first reminder event and the configuration parameters of the second reminder event, a target reminder event is determined between the first reminder event and the second reminder event.

[0262] The specific implementation of this step is the same as that of step 603 and will not be repeated here.

[0263] In step 1904: ignore the non-target reminder event; or, add the non-target reminder event to the queue of reminder events to be executed.

[0264] If the first reminder event is a target reminder event, the non-target reminder event is the second reminder event; if the second reminder event is a target reminder event, the non-target reminder event is the first reminder event.

[0265] That is, in this application, for non-target reminder events, you can no longer process them or add them to the queue of pending reminder events, that is, ignore them. In order to ensure the comprehensiveness of reminder event processing, you can also add non-target reminder events to the queue of pending reminder events. In this application, as long as you ensure that non-target reminder events do not interrupt target reminder events, the specific operations for handling non-target reminder events are not limited.

[0266] In some possible embodiments, ignoring non-target reminder events can be specifically implemented as follows: if the non-target reminder event is the second reminder event, terminating the execution of the second reminder event; or, if the non-target reminder event is the first reminder event, eliminating the first reminder event.

[0267] In some possible embodiments, adding a non-target reminder event to a queue of reminder events to be executed can be specifically implemented as follows: adding the non-target reminder event to the end of the queue of reminder events to be executed; or, determining the target position of the non-target reminder event in the queue of reminder events to be executed based on the event priority of the non-target reminder event and the event priority of the reminder events in the queue of reminder events to be executed; and adding the non-target reminder event to the target position in the queue of reminder events to be executed.

[0268] For example: it is determined that the queue of reminder events to be executed includes: event 1, event 2, event 3; it is determined that the non-target reminder event is event 4, then event 4 is added to the end of the queue of reminder events to be executed. After adding the non-target reminder event, the queue of reminder events to be executed includes: event 1, event 2, event 3, event 4.

[0269] Determine that the queue of reminder events to be executed includes: event 1, event 2, and event 3; determine that the non-target reminder event is event 4, determine that the event priority of event 1 is 1, determine that the event priority of event 2 is 2, determine that the priority of event 3 is 4, and determine that the priority of event 4 is 3, then the target position can be determined to be between event 2 and event 3, and event 4 is added to the queue of reminder events to be executed. The resulting queue of reminder events to be executed includes: event 1, event 2, event 4, and event 3.

[0270] Determine that the reminder event queue to be executed includes: event 1, event 2, and event 3; determine that the non-target reminder event is event 4, determine the event priority of event 1 to be 1, determine the event priority of event 2 to be 2, determine the priority of event 3 to be 2, and determine the priority of event 4 to be 2. At this time, the event priorities of event 2, event 3, and event 4 are the same, and event 4 can be added between event 1 and event 2, or between event 2 and event 3, or after event 3.

[0271] That is, when adding a non-target reminder event to the queue of reminder events to be executed, it is sufficient to ensure that the non-target reminder event is added after the event in the queue of reminder events to be executed whose event priority is higher than that of the non-target reminder event, and to ensure that the non-target reminder event is added before the event in the queue of reminder events to be executed whose event priority is lower than that of the non-target reminder event.

[0272] In the embodiment of the present application, if a reminder event is not yet completed but the corresponding exit signal of the reminder event has been received, if the reminder event is still executed, it will result in a waste of resources and reduce the user experience. Therefore, in the present application, during the execution of the target reminder event, if the exit signal of the target reminder event is detected, the target reminder event is ignored based on the exit signal of the target reminder event.

[0273] For example: the target reminder event being executed is the "child forgotten reminder". At this time, the camera of the vehicle terminal captures the child in the back seat being carried out by someone, and the pressure sensor installed in the back seat determines that the current pressure value corresponds to no one in the seat; the vehicle terminal determines that the child has been carried out based on the image of the child being carried out and the pressure value of the pressure sensor in the back seat, and determines that the exit signal corresponding to the "child forgotten reminder" has appeared, then stops executing the "child forgotten reminder", and ignores the "child forgotten reminder".

[0274] In some other possible embodiments, if a reminder event in the pending reminder event queue is terminated by the user, the following may be implemented: based on an exit signal corresponding to the reminder event in the pending reminder event queue, the reminder event is removed from the pending reminder event queue.

[0275] For example: the events currently included in the pending reminder event queue are: Event 1, Event 2, Event 3. The camera and sensor of the vehicle terminal determine that the exit signal corresponding to Event 3 has appeared, then Event 3 is removed from the pending reminder event queue. After removal, the pending reminder event queue includes: Event 1 and Event 2.

[0276] The following is an overall example of a reminder method for an in-vehicle terminal. For example, as shown in FIG20 , it is a priority specification table corresponding to a reminder event. Based on this table, the event priority, mode priority, and category of the reminder mode of the reminder event can be obtained. As shown in FIG21 , the event processing strategy is determined. A reminder event with a high event priority can interrupt a reminder event with a low event priority. When the event priorities are equal, the first reminder event is used as the target reminder event. If the event priority of the first reminder event is lower than the event priority of the second reminder event, and the difference between the event priority of the first reminder event and the event priority of the second reminder event is greater than 1, the first reminder event is ignored; if the event priority of the first reminder event is lower than the event priority of the second reminder event, and the difference between the event priority of the first reminder event and the event priority of the second reminder event is equal to 1, the first reminder event is added to the queue of reminder events to be executed.

[0277] In order to further improve the user experience and ensure the efficiency of processing the first reminder event, the embodiment of the present application also provides a reminder method of the vehicle terminal, as shown in FIG22 , wherein:

[0278] In step 2201: obtain configuration parameters of the first reminder event that occurs, the configuration parameters including the reminder mode.

[0279] The specific implementation of this step is the same as that of step 601 and will not be repeated here.

[0280] In step 2202 : determine whether a second reminder event exists. If it is determined that the second reminder event does not exist, use the first reminder event as the target reminder event.

[0281] In step 2203 : the target reminder content corresponding to the target reminder event is displayed based on the reminder mode corresponding to the target reminder event.

[0282] The specific implementation of this step is the same as that of step 604 and will not be repeated here.

[0283] The following describes the overall process of a reminder method for a vehicle-mounted terminal provided by this application in combination with the internal modules of the vehicle-mounted terminal: As shown in Figure 23, the vehicle-mounted terminal includes: vehicle-mounted DM, DS, Voice App, CA, and service center.

[0284] Among them: the configuration parameters are sent to the DS in advance through the Voice App. After sensing that the first reminder event has been triggered, the CA in the vehicle terminal reports the first reminder event to the DS in the vehicle terminal. After receiving the first reminder event, the DS determines the target reminder event based on the configuration parameters set in this application and reports the target reminder event to the Voice App in the vehicle terminal. The Voice App reports the target reminder event to the DM in the vehicle terminal and the DM in the cloud. After receiving the target reminder event reported by the DS, the DM in the vehicle terminal generates an event processing instruction based on the target reminder event and sends the event processing instruction to the Voice App. At the same time, after receiving the target reminder event reported by the DS, the DM in the cloud generates an event processing instruction based on the target reminder event and sends the event processing instruction to the Voice App. Based on the event processing instruction received first, the Voice App calls the ability kit to obtain the card corresponding to the target reminder event from the service center. The service center returns the card to the Voice App. After receiving the card, the Voice App displays the card. After displaying the card, the Voice App sends the processed data to the CA in the vehicle terminal. At the same time, during the execution of the above process, if the CA in the vehicle terminal detects an exit signal, the CA in the vehicle terminal sends the exit signal to the DS, and the DS sends the exit signal to the Voice App. The Voice App determines the reminder event that needs to be removed or stopped based on the exit signal.

[0285] The following describes the overall process of a reminder method for a vehicle terminal provided in an embodiment of the present application at the software level: As shown in Figure 24, after receiving the first reminder event 1 or the exit signal 2, the DS module sends the first reminder event 1 and the exit signal 2 to the Voice App, and the Voice App processes the incoming first reminder event 1 and the exit signal 2; for the first reminder event: 1.1 If it is determined that there is a second reminder event, the configuration parameters of the first reminder event are compared with the configuration parameters of the second reminder event; 1.2 If the comparison result indicates that the first reminder event is added to the reminder event queue to be executed, the first reminder event is added to the reminder event queue to be executed; if the comparison result indicates that the first reminder event is taken as the target reminder event and executed, the first reminder event is executed; if the comparison result indicates that the first reminder event is taken as the target reminder event and executed, and the reminder events in the reminder event queue to be executed are cleared at the same time, the reminder event is executed and the reminder events in the reminder event queue to be executed are cleared. For the exit signal: 2.1 determine the reminder event corresponding to the exit signal. If the reminder event is the second reminder event, stop executing the second reminder event; if the reminder event is a reminder event in the reminder event queue to be executed, remove the reminder event from the reminder event queue to be executed.

[0286] The following describes a reminder method for a vehicle-mounted terminal provided by an embodiment of the present application in conjunction with a specific application scenario:

[0287] As shown in Figure 25, the first reminder event is detected as "indoor navigation", and the target reminder event is determined to be "indoor navigation reminder" according to the steps in Figure 6. It is determined that the reminder mode corresponding to the "indoor navigation reminder" is to display dynamic cards and play voice. The process of executing the first reminder event is: first, the voice broadcast "This car manufacturer supports indoor navigation, do you want to start it?" If the user says the wake-up word (start, start, okay), the dynamic card corresponding to the navigation interface is obtained and displayed on the display screen of the vehicle terminal; if the user's voice "switch to Building A" is detected, the card corresponding to Building A is obtained and displayed on the display screen of the vehicle terminal, and "A parking space on the B1 floor of Building A has been recommended for you" is broadcast; if the user's voice "switch to B2 floor" is detected, the card corresponding to the B2 floor of Building A is obtained and displayed on the display screen of the vehicle terminal, and "A parking space on the B2 floor of Building A has been recommended for you" is broadcast.

[0288] As shown in Figure 26, the first reminder event is detected as "Extreme Weather Low Visibility Reminder," and the target reminder event is determined to be "Extreme Weather Low Visibility Reminder" according to the steps in Figure 6. The reminder mode corresponding to "Extreme Weather Low Visibility Reminder" is determined to be displaying a dynamic card and playing a voice message. The process for executing this first reminder event is as follows: displaying a dynamic card corresponding to "Extreme Weather Low Visibility Reminder" on the vehicle terminal's display screen. While the dynamic card is being pushed, if a user clicks on the dynamic card, it is determined that the user has initiated the subsequent process corresponding to "Extreme Weather Low Visibility Reminder." Then, the vehicle terminal's player plays a voice message stating, "Turning on the rear fog lights requires turning on the low beams at the same time. Are you sure you want to turn them on?" If the user confirms turning on the low beams and does so, the dynamic card is cleared and the message "OK, rear fog lights and heated mirrors are both on" is played. It should be noted that if, after the message "Turning on the rear fog lights requires turning on the low beams at the same time. Are you sure you want to turn them on?" is played, it is determined that the user has not turned on the low beams, a second voice message stating, "Turning on the rear fog lights requires turning on the low beams at the same time" is played.

[0289] If the voice message "Turning on the rear fog lights requires turning on the low beam lights at the same time, are you sure you want to turn them on" is broadcast through the player in the vehicle terminal, and it is detected that the user has clicked on the card corresponding to "Extreme weather with low visibility" on the display screen, it is determined that the user has confirmed turning on the rear fog lights, and then the voice message "OK, the rear fog lights and heated rearview mirrors are both turned on" is broadcast, and the dynamic card is closed after the dynamic card display time reaches the preset time.

[0290] If the player in the vehicle terminal broadcasts the voice "Turning on the rear fog lights requires turning on the low beam lights at the same time, are you sure you want to turn them on?", if the user's voice confirmation to turn them off is detected, the dynamic card will be turned off on the display screen.

[0291] If the voice message "Turning on the rear fog lights requires turning on the low beam lights at the same time, are you sure you need to turn them on" is broadcast through the player in the vehicle terminal, if a first reminder event is detected and it is determined that the first reminder event is a second reminder event, the dynamic card will be closed on the display screen and the second reminder event will be executed.

[0292] A dynamic card corresponding to "Extreme Weather Low Visibility Reminder" is displayed on the display screen of the vehicle terminal. During the push of the dynamic card, if it is detected that the user clicks on an area of ​​the vehicle terminal display screen other than the dynamic card, it is determined that the user has triggered the exit signal corresponding to "Extreme Weather Low Visibility Reminder", and the dynamic card is closed, or the dynamic card can be moved to a specified position and the voice corresponding to "Extreme Weather Low Visibility Reminder" is stopped.

[0293] To facilitate further understanding, the following describes the configuration process of the configuration parameters in the reminder method of the vehicle terminal provided in an embodiment of the present application:

[0294] As shown in FIG27 , in the parameter configuration platform on the cloud, technicians can configure the configuration parameters corresponding to each reminder event, including but not limited to: event priority, mode priority, category of reminder mode, content priority, and voice package. After the technicians have configured the configuration parameters corresponding to the reminder event, when executing the reminder method of the vehicle terminal provided by this application, the cloud will send the configuration parameters corresponding to the reminder event to the Voice App in the vehicle terminal, and the Voice App will report the target reminder event to the DM in the vehicle terminal and the DM in the cloud; after receiving the reported target reminder event, the DM in the vehicle terminal generates an event processing instruction based on the target reminder event and sends the event processing instruction to the Voice App. At the same time, after receiving the reported target reminder event, the DM in the cloud generates an event processing instruction based on the target reminder event and sends the event processing instruction to the Voice App; the Voice App obtains the voice package and / or card from the configuration parameters based on the event processing instruction received first.

[0295] To sum up, the reminder method of a vehicle terminal provided by the embodiment of the present application ensures that reminder events are executed accurately and efficiently according to urgency, importance and cost, avoids conflicts between events, ensures the execution efficiency of reminder events, and unifies the interaction specifications by clearly defining the mode priority, event priority level, category of reminder mode, etc., and ensures the diversity of proactive services.

[0296] Based on the same inventive concept, after introducing a battery system control method provided in an embodiment of the present application, as shown in FIG28 , a battery system control device 2800 provided in an embodiment of the present application is described below. The device includes:

[0297] An acquisition module 28001 is configured to acquire configuration parameters of a first reminder event, wherein the configuration parameters include a reminder mode;

[0298] The second reminder event determination module 28002 is used to determine whether a second reminder event exists; the second reminder event includes: a reminder event currently being executed or a reminder event in a reminder event queue to be executed;

[0299] a target reminder event determination module 28003, configured to, when determining that the second reminder event exists, determine a target reminder event from the first reminder event and the second reminder event based on the configuration parameters of the first reminder event and the configuration parameters of the second reminder event;

[0300] The execution module 28004 is configured to display the target reminder content corresponding to the target reminder event based on the reminder mode corresponding to the target reminder event.

[0301] In some possible embodiments, the acquisition module 28001 is specifically configured to:

[0302] The configuration parameters of the first reminder event are obtained from the cloud.

[0303] In some possible embodiments, the configuration parameters further include event priority; the target reminder event determination module 28003 is specifically configured to:

[0304] comparing the event priority of the first reminder event with the event priority of the second reminder event;

[0305] If the event priority of the first reminder event is higher than the event priority of the second reminder event, taking the first reminder event as the target reminder event;

[0306] If the event priority of the first reminder event is lower than the event priority of the second reminder event, taking the second reminder event as the target reminder event;

[0307] If the event priority of the first reminder event is equal to the event priority of the second reminder event, the first reminder event or the second reminder event is used as the target reminder event.

[0308] In some possible embodiments, the configuration parameters include a mode priority corresponding to the reminder mode, and the target reminder event determination module 28003 is specifically configured to:

[0309] comparing the mode priority corresponding to the reminder mode of the first reminder event with the mode priority corresponding to the reminder mode of the second reminder event;

[0310] If the mode priority of the first reminder event is higher than the mode priority of the second reminder event, taking the first reminder event as the target reminder event;

[0311] If the mode priority of the first reminder event is lower than the mode priority of the second reminder event, taking the second reminder event as the target reminder event;

[0312] If the mode priority of the first reminder event is equal to the mode priority of the second reminder event, the first reminder event or the second reminder event is used as the target reminder event.

[0313] In some possible embodiments, the configuration parameters further include event priority; the target reminder event determination module 28003 is specifically configured to:

[0314] comparing the categories of the reminder mode of the first reminder event and the categories of the reminder mode of the second reminder event, the categories of the reminder mode including displaying a card, playing a voice, and displaying a card and playing a voice;

[0315] If the category of the reminder mode of the first reminder event is the same as the category of the reminder mode of the second reminder event, comparing the event priority of the first reminder event with the event priority of the second reminder event;

[0316] If the event priority of the first reminder event is higher than the event priority of the second reminder event, taking the first reminder event as the target reminder event;

[0317] If the event priority of the first reminder event is lower than the event priority of the second reminder event, taking the second reminder event as the target reminder event;

[0318] If the event priority of the first reminder event is equal to the event priority of the second reminder event, the first reminder event or the second reminder event is used as the target reminder event.

[0319] In some possible embodiments, the first reminder event includes at least one reminder content, the second reminder event includes at least one reminder content, and the configuration parameter further includes a content priority corresponding to the reminder content; the target reminder event determination module 28003 is further configured to:

[0320] If the category of the reminder mode of the first reminder event is different from the category of the reminder mode of the second reminder event, determining the category of the reminder mode corresponding to the reminder content in the first reminder event and the category of the reminder mode corresponding to the reminder content in the second reminder event;

[0321] If the category of the reminder mode corresponding to the reminder content in the first reminder event is different from the category of the reminder mode corresponding to the reminder content in the second reminder event, then the first reminder event and the second reminder event are used as target reminder events;

[0322] If it is determined that the first reminder event contains reminder content of the same category as the reminder mode corresponding to the reminder content in the second reminder event, the content priority of the first target reminder content is compared with the content priority of the second target reminder content to obtain the target reminder event; wherein the first target reminder content is the reminder content of the same category as the reminder mode corresponding to the reminder content included in the first reminder event, and the second target reminder content is the reminder content of the same category as the reminder mode corresponding to the reminder content included in the second reminder event.

[0323] In some possible embodiments, the target reminder event determination module 28003 is specifically configured to:

[0324] If the content priority of the first target reminder content is higher than the content priority of the second target reminder content, taking the first reminder event as the target reminder event;

[0325] If the content priority of the first target reminder content is lower than the content priority of the second target reminder content, taking the second reminder event as the target reminder event;

[0326] If the content priority of the first target reminder content is equal to the content priority of the second target reminder content, the first reminder event or the second reminder event is used as the target reminder event.

[0327] In some possible embodiments, the reminder mode includes any one of the following: displaying a static card, displaying a dynamic card, displaying a dynamic card and playing a voice, displaying a static card and playing a voice, and playing a voice.

[0328] In some possible embodiments, the second reminder event determination module 28002 is specifically configured to:

[0329] If it is determined that there is a reminder event currently being executed, then it is determined that there is a second reminder event, where the second reminder event is the reminder event currently being executed;

[0330] If it is determined that there is no reminder event currently being executed, and it is determined that there is a reminder event in the reminder event queue to be executed, then it is determined that there is the second reminder event, and the second reminder event is determined based on the reminder event queue to be executed.

[0331] In some possible embodiments, the target reminder event determination module 28003 is further configured to:

[0332] Ignore non-target reminder events; or add the non-target reminder events to a queue of reminder events to be executed;

[0333] If the first reminder event is a target reminder event, the non-target reminder event is the second reminder event; if the second reminder event is a target reminder event, the non-target reminder event is the first reminder event.

[0334] In some possible embodiments, the target reminder event determination module 28003 is specifically configured to:

[0335] If the non-target reminder event is the second reminder event, terminating the execution of the second reminder event; or,

[0336] If the non-target reminder event is the first reminder event, the first reminder event is eliminated.

[0337] In some possible embodiments, the configuration parameters further include event priority; the target reminder event determination module 28003 is specifically configured to:

[0338] Determining whether the non-target reminder event is a reminder event in a queue of reminder events to be executed;

[0339] If yes, then add the non-target reminder event to the end of the reminder event queue to be executed; or

[0340] determining a target position of the non-target reminder event in the queue of reminder events to be executed according to the event priority of the non-target reminder event and the event priority of the reminder events in the queue of reminder events to be executed;

[0341] The non-target reminder event is added to the target position in the reminder event queue to be executed.

[0342] In some possible embodiments, the execution module 28004 is further configured to:

[0343] Based on the exit signal of the target reminder event, the target reminder event is ignored.

[0344] In some possible embodiments, the execution module 28004 is further configured to:

[0345] Based on an exit signal corresponding to a reminder event in the to-be-executed reminder event queue, the reminder event is removed from the to-be-executed reminder event queue.

[0346] In some possible embodiments, the second reminder event determination module 28002 is further configured to:

[0347] If it is determined that the second reminder event does not exist, the first reminder event is used as the target reminder event.

[0348] Corresponding to the above embodiment, the present application also provides an electronic device. Figure 29 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. The electronic device 2900 may include: a processor 2901, a memory 2902, and a communication unit 2903. These components communicate through one or more buses. Those skilled in the art will understand that the structure of the electronic device shown in the figure does not constitute a limitation on the embodiment of the present application. It can be a bus structure or a star structure, and can also include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0349] The communication unit 2903 is configured to establish a communication channel so that the electronic device can communicate with other devices, receive user data sent by other devices, or send user data to other devices.

[0350] The processor 2901 is the control center of the electronic device. It uses various interfaces and lines to connect the various parts of the entire electronic device. It runs or executes software programs and / or modules stored in the memory 2902, and calls data stored in the memory to perform various functions of the electronic device and / or process data. The processor can be composed of an integrated circuit (IC), for example, it can be composed of a single packaged IC, or it can be composed of multiple packaged ICs with the same or different functions. For example, the processor 2901 can include only a central processing unit (CPU). In the embodiment of the present application, the CPU can be a single computing core or multiple computing cores.

[0351] The memory 2902 is used to store the execution instructions of the processor 2901. The memory 2902 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0352] When the execution instructions in the memory 2902 are executed by the processor 2901 , the electronic device 2900 is enabled to execute part or all of the steps in the embodiment shown in FIG. 6 .

[0353] In a specific implementation, the present application further provides a computer storage medium, wherein the computer storage medium may store a program, and when the program is executed, the program may include some or all of the steps of each embodiment of the calling method provided in the present application. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0354] Those skilled in the art can clearly understand that the technology in the embodiments of the present application can be implemented by means of software plus the necessary general hardware platform. Based on this understanding, the technical solutions in the embodiments of the present application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application or certain parts of the embodiments.

[0355] In this specification, reference can be made to the same or similar parts between the various embodiments. In particular, for the device embodiment and the terminal embodiment, since they are basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description in the method embodiment.

[0356] The above describes in detail the structure, features and effects of the present application based on the embodiments shown in the drawings. The above is only a preferred embodiment of the present application, but the present application does not limit the scope of implementation to what is shown in the drawings. Any changes made in accordance with the concept of the present application, or modifications to equivalent embodiments with equivalent changes, which still do not exceed the spirit covered by the description and drawings, should be within the scope of protection of the present application.

Claims

1. A reminder method for a vehicle terminal, characterized in that: The method comprises: Obtaining configuration parameters of a first reminder event that occurs, wherein the configuration parameters include a reminder mode; Determine whether there is a second reminder event; the second reminder event includes: a reminder event currently being executed or a reminder event in a queue of reminder events to be executed; If it is determined that the second reminder event exists, obtaining configuration parameters of the second reminder event; Determining a target reminder event from the first reminder event and the second reminder event based on the configuration parameters of the first reminder event and the configuration parameters of the second reminder event; The target reminder content corresponding to the target reminder event is displayed based on the reminder mode corresponding to the target reminder event.

2. The method according to claim 1, characterized in that The configuration parameters of the first reminder event that occurs are obtained: The configuration parameters of the first reminder event are obtained from the cloud.

3. The method according to claim 1, characterized in that The configuration parameters also include an event priority corresponding to the reminder event; and determining a target reminder event from the first reminder event and the second reminder event based on the configuration parameters of the first reminder event and the configuration parameters of the second reminder event, including: comparing the event priority of the first reminder event with the event priority of the second reminder event; If the event priority of the first reminder event is higher than the event priority of the second reminder event, taking the first reminder event as the target reminder event; If the event priority of the first reminder event is lower than the event priority of the second reminder event, taking the second reminder event as the target reminder event; If the event priority of the first reminder event is equal to the event priority of the second reminder event, the first reminder event or the second reminder event is used as the target reminder event.

4. The method according to claim 1, characterized in that The configuration parameters include a mode priority corresponding to the reminder mode, and the determining a target reminder event from the first reminder event and the second reminder event based on the configuration parameters of the first reminder event and the configuration parameters of the second reminder event includes: comparing the mode priority corresponding to the reminder mode of the first reminder event with the mode priority corresponding to the reminder mode of the second reminder event; If the mode priority of the first reminder event is higher than the mode priority of the second reminder event, taking the first reminder event as the target reminder event; If the mode priority of the first reminder event is lower than the mode priority of the second reminder event, taking the second reminder event as the target reminder event; If the mode priority of the first reminder event is equal to the mode priority of the second reminder event, the first reminder event or the second reminder event is used as the target reminder event.

5. The method according to claim 1, characterized in that: The configuration parameters also include event priority; the determining of a target reminder event from the first reminder event and the second reminder event based on the configuration parameters of the first reminder event and the configuration parameters of the second reminder event includes: comparing the category of the reminder mode of the first reminder event and the category of the reminder mode of the second reminder event, the category of the reminder mode including displaying a card, playing a voice, and displaying a card and playing a voice; If the category of the reminder mode of the first reminder event is the same as the category of the reminder mode of the second reminder event, comparing the event priority of the first reminder event with the event priority of the second reminder event; If the event priority of the first reminder event is higher than the event priority of the second reminder event, taking the first reminder event as the target reminder event; If the event priority of the first reminder event is lower than the event priority of the second reminder event, taking the second reminder event as the target reminder event; If the event priority of the first reminder event is equal to the event priority of the second reminder event, the first reminder event or the second reminder event is used as the target reminder event.

6. The method according to claim 1, characterized in that The first reminder event includes at least one reminder content, the second reminder event includes at least one reminder content, and the configuration parameter further includes a content priority corresponding to the reminder content; After comparing the category of the reminder mode of the first reminder event and the category of the reminder mode of the second reminder event, the method further includes: If the category of the reminder mode of the first reminder event is different from the category of the reminder mode of the second reminder event, determining the category of the reminder mode corresponding to the reminder content in the first reminder event and the category of the reminder mode corresponding to the reminder content in the second reminder event; If the category of the reminder mode corresponding to the reminder content in the first reminder event is different from the category of the reminder mode corresponding to the reminder content in the second reminder event, the first reminder event and the second reminder event are used as target reminder events; If it is determined that the first reminder event contains reminder content of the same category as the reminder mode corresponding to the reminder content in the second reminder event, the content priority of the first target reminder content is compared with the content priority of the second target reminder content to obtain a target reminder event; wherein the first target reminder content is the reminder content of the same category as the reminder mode corresponding to the reminder content included in the first reminder event, and the second target reminder content is the reminder content of the same category as the reminder mode corresponding to the reminder content included in the first reminder event.

7. The method according to claim 6, characterized in that The step of comparing the content priority of the first target reminder content with the content priority of the second target reminder content to obtain a target reminder event includes: If the content priority of the first target reminder content is higher than the content priority of the second target reminder content, taking the first reminder event as the target reminder event; If the content priority of the first target reminder content is lower than the content priority of the second target reminder content, taking the second reminder event as the target reminder event; If the content priority of the first target reminder content is equal to the content priority of the second target reminder content, the first reminder event or the second reminder event is used as the target reminder event.

8. The method according to claim 1, characterized in that The reminder mode includes any one of the following: displaying a static card, displaying a dynamic card, displaying a dynamic card and playing a voice, displaying a static card and playing a voice, and playing a voice.

9. The method according to claim 1, characterized in that: The determining whether there is a second reminder event includes: If it is determined that there is a reminder event currently being executed, then it is determined that there is the second reminder event, and the second reminder event is the reminder event currently being executed; If it is determined that there is no reminder event currently being executed, and it is determined that there is a reminder event in the reminder event queue to be executed, then it is determined that there is the second reminder event, and the second reminder event is determined based on the reminder event queue to be executed.

10. The method according to claim 1, characterized in that After determining a target reminder event from the first reminder event and the second reminder event based on the configuration parameters of the first reminder event and the configuration parameters of the second reminder event, the method further includes: Ignore non-target reminder events; or, add the non-target reminder events to a queue of reminder events to be executed; If the first reminder event is a target reminder event, the non-target reminder event is the second reminder event; if the second reminder event is a target reminder event, the non-target reminder event is the first reminder event.

11. The method according to claim 10, characterized in that Ignoring non-target reminder events includes: If the non-target reminder event is the second reminder event, terminating the execution of the second reminder event; or, If the non-target reminder event is the first reminder event, the first reminder event is eliminated.

12. The method according to claim 9, characterized in that The configuration parameters also include event priority; the adding of the non-target reminder event to the reminder event queue to be executed includes: Determining whether the non-target reminder event is a reminder event in a queue of reminder events to be executed; If yes, then add the non-target reminder event to the end of the reminder event queue to be executed; or, Determining a target position of the non-target reminder event in the queue of reminder events to be executed according to the event priority of the non-target reminder event and the event priority of the reminder events in the queue of reminder events to be executed; The non-target reminder event is added to the target position in the reminder event queue to be executed.

13. The method according to claim 1, characterized in that The method further comprises: Based on the exit signal of the target reminder event, the target reminder event is ignored.

14. The method according to claim 1, characterized in that The method further comprises: Based on an exit signal corresponding to the reminder event in the to-be-executed reminder event queue, the reminder event is removed from the to-be-executed reminder event queue.

15. The method according to claim 1, characterized in that After determining whether the second reminder event exists, the method further includes: if it is determined that the second reminder event does not exist, taking the first reminder event as the target reminder event.

16. A reminder device for a vehicle terminal, characterized in that: The device comprises: An acquisition module, used to acquire configuration parameters of the first reminder event, wherein the configuration parameters include a reminder mode; A second reminder event determination module is used to determine whether a second reminder event exists; the second reminder event includes: a reminder event currently being executed or a reminder event in a reminder event queue to be executed; a target reminder event determination module, configured to determine a target reminder event from the first reminder event and the second reminder event based on configuration parameters of the first reminder event and configuration parameters of the second reminder event when determining that the second reminder event exists; The execution module is used to display the target reminder content corresponding to the target reminder event based on the reminder mode corresponding to the target reminder event.

17. An electronic device, characterized in that: The device comprises a memory for storing computer program instructions and a processor for executing the program instructions, wherein when the computer program instructions are executed by the processor, the electronic device is triggered to execute the method according to any one of claims 1 to 15.

18. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the method according to any one of claims 1 to 15.

Images