Condition-triggered task configuration method and device
By automatically generating conditions to trigger IFTTT tasks, the problems of complex IFTTT task operations and environmental conflicts are solved, improving generation efficiency and accuracy, and enhancing user experience.
Patent Information
- Application Number
- CN202311363249.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-10-19
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2043-10-19
AI Technical Summary
IFTTT tasks rely entirely on user-created and configured tasks, which makes the process complex. Furthermore, user-configured tasks may conflict with the environment and require manual editing and optimization.
By acquiring event information of the target vehicle, multiple time-related event groups are formed. Based on the matching event groups, scene condition events and scene action events are determined, and condition-triggered IFTTT tasks are automatically generated.
It enables the automatic generation of condition-triggered tasks, improving generation efficiency and accuracy, avoiding interference from irrelevant events, and enhancing the user experience.
Smart Images

Figure CN117648043B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of artificial intelligence, and in particular to a method and apparatus for configuring condition-triggered tasks. Background Technology
[0002] IFTTT (If This Then That) means that if one event is triggered, another pre-defined event will be executed. IFTTT automates repetitive tasks, reducing redundant operations. IFTTT modules are widely used in the smart car industry, connecting to hundreds of smart devices in vehicles to help users automate IFTTT tasks.
[0003] Currently, IFTTT tasks require users to create them based on their individual needs through a software platform provided by the car manufacturer. Users need to manually configure the If condition event and Then action event in the IFTTT task and complete the creation of the IFTTT task based on AND, OR, NOT and other execution logic.
[0004] In the existing approach, IFTTT tasks rely entirely on user-created and configured tasks, which is a complex process. Furthermore, user-configured IFTTT tasks may conflict with the environment, requiring users to manually edit and optimize them when conflicts occur. Summary of the Invention
[0005] This application provides a condition-triggered task configuration method and apparatus to solve the problems that IFTTT tasks rely entirely on user-initiated creation and configuration, the operation of configuring IFTTT tasks is complex, and user-configured IFTTT tasks may conflict with the environment, requiring users to manually edit and optimize them when conflicts occur.
[0006] Firstly, this application provides a method for configuring condition-triggered tasks, including:
[0007] Obtain event occurrence information for the target vehicle; the event occurrence information includes the event occurrence time corresponding to the target event;
[0008] Multiple event groups are formed based on the occurrence time of the target events; each event group includes multiple target events that are related in time.
[0009] Scene condition events and scene action events are determined based on multiple matching event groups;
[0010] The IFTTT task is triggered based on the scene condition events and scene action events.
[0011] Optionally, forming multiple event groups based on the occurrence time of the target event includes:
[0012] Obtain multiple pre-configured preset time ranges;
[0013] For each preset time range, multiple target events occurring within that preset time range are grouped into an event group.
[0014] Optionally, forming multiple event groups based on the occurrence time of the target event includes:
[0015] Retrieve key target events and their corresponding event types from pre-configured target events; the event types include: conditions and actions;
[0016] Based on the event type, the event occurrence time, and the preset event time interval, the associated target events are determined, forming multiple event groups.
[0017] Optionally, the step of determining associated target events based on the event type, the event occurrence time, and a preset time interval between events to form multiple event groups includes:
[0018] In response to the key target event, the event type is action. Based on the preset event time interval and the event occurrence time, among the target events that occurred before the key target event, the first associated event that is related to the key target event and whose event type is condition is determined.
[0019] The first related event, the key target event, and the target events that occur between the first related event and the key target event are identified as related target events, forming an event group;
[0020] In response to the key target event, the event type is used as a condition. Based on the preset time interval and the time of occurrence of the event, among the target events that occur after the key target event, the last associated event that is associated with the key target event and whose event type is action is determined.
[0021] Key target events, last-ranking related events, and target events occurring between key target events and last-ranking related events are identified as related target events, forming event groups.
[0022] Optionally, based on a preset event time interval and the event occurrence time, among target events occurring before the key target event, a first associated event that is related to the key target event and whose event type is a condition is determined, including:
[0023] Determine at least one candidate first target event from the key target event and the target events that occurred consecutively before it, wherein the time interval between any two adjacent target events is less than a preset event time interval;
[0024] From at least one candidate primary target event, determine the primary associated event that is furthest from the key target event and whose event relationship type is conditional;
[0025] The method of determining the last associated event of type action among target events occurring after the key target event based on a preset time interval and the event occurrence time includes:
[0026] Determine at least one candidate last target event from the key target event and subsequent consecutive target events, wherein the time interval between any two adjacent target events is less than a preset event time interval;
[0027] From at least one candidate last target event, determine the last associated event that is furthest from the key target event and whose event relationship type is action.
[0028] Optionally, the event occurrence information further includes an event identifier; before determining the scene condition event and scene action event based on multiple matching event groups, the method further includes:
[0029] The event similarity between event groups is calculated based on the event occurrence information corresponding to the target event in multiple event groups, and the event similarity in the preset dimensions includes: event identifier similarity, event quantity similarity, and event triggering order similarity.
[0030] The event similarity of the preset dimensions is weighted and summed, and the weighted summation result is determined as the event group similarity between event groups;
[0031] Multiple event groups whose event group similarity is greater than a preset similarity threshold are identified as multiple matching event groups.
[0032] Optionally, determining scene condition events and scene action events based on multiple matching event groups includes:
[0033] The order and time interval of the target events in the matched event groups are determined based on the occurrence times of the target events in the matched event groups.
[0034] The scene condition events and scene action events are determined based on the sequence and event type of the target events in the matched event groups.
[0035] Optionally, after generating conditions to trigger the IFTTT task based on the scene condition events and scene action events, the method further includes:
[0036] In response to the detection that a scene condition event of a certain IFTTT task is triggered, the scene action event of the IFTTT task is displayed;
[0037] In response to receiving a confirmation operation from the user through the operation interface for a scene action event, control the corresponding vehicle components to perform actions according to the scene action event, and determine the number of times the user confirms the scene action event for the IFTTT task.
[0038] In response to the number of confirmation operations exceeding a preset confirmation threshold, the IFTTT task is configured as an automatically executed IFTTT task.
[0039] Optionally, after configuring the IFTTT task as an automatically executed IFTTT task in response to the number of confirmation operations exceeding a preset confirmation count threshold, the following steps are included:
[0040] In response to the user's activation of the IFTTT task through the operation interface, the scene condition events of the IFTTT task are monitored.
[0041] In response to the detection that a scene condition event of the IFTTT task is triggered, a control command is sent to the corresponding vehicle component to control the corresponding vehicle component to perform actions according to the scene action event of the IFTTT task.
[0042] Secondly, this application provides a condition-triggered task configuration device, comprising:
[0043] The monitoring module is used to acquire event occurrence information of the target vehicle; the event occurrence information includes the event occurrence time corresponding to the target event;
[0044] The event group determination module is used to form multiple event groups based on the occurrence time of the target event; the event group includes multiple target events that are related in time.
[0045] The event splitting module is used to determine scene condition events and scene action events based on multiple matching event groups;
[0046] The task generation module is used to generate conditions to trigger IFTTT tasks based on the scene condition events and scene action events.
[0047] Thirdly, this application provides an electronic device, including: a processor, and a memory and a transceiver communicatively connected to the processor;
[0048] The memory stores computer-executed instructions; the transceiver is used for sending and receiving data.
[0049] The processor executes computer execution instructions stored in the memory to implement the condition-triggered task configuration method described in any of the preceding aspects.
[0050] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the condition-triggered task configuration method described in any of the preceding aspects.
[0051] Fifthly, this application provides a computer program product, including computer execution instructions, which, when executed by a processor, implement the condition-triggered task configuration method described in any of the preceding aspects.
[0052] The condition-triggered task configuration method and apparatus provided in this application acquire event occurrence information of a target vehicle; the event occurrence information includes the event occurrence time corresponding to the target event; multiple event groups are formed according to the event occurrence time corresponding to the target event; the event groups include multiple target events that are temporally related; scene condition events and scene action events are determined based on the matching multiple event groups; and a condition-triggered IFTTT task is generated according to the scene condition events and scene action events. This achieves automatic generation of condition-triggered tasks, improving the generation efficiency of condition-triggered tasks; and by only monitoring target events, interference from irrelevant events is avoided, improving the accuracy of determining event groups, thereby improving the accuracy of the determined condition-triggered tasks. Attached Figure Description
[0053] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0054] Figure 1 A flowchart of the condition-triggered task configuration method provided in the embodiments of this application;
[0055] Figure 2 This is a schematic diagram illustrating the determination of event groups based on a preset time range, provided in an embodiment of this application.
[0056] Figure 3 This application provides another schematic diagram of determining an event group based on a preset time range in an embodiment of the present application;
[0057] Figure 4 This is a schematic diagram illustrating an example of a condition-triggered task configuration provided in an embodiment of this application.
[0058] Figure 5 This is a schematic diagram of the structure of the condition-triggered task configuration device provided in the embodiments of this application;
[0059] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.
[0060] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation
[0061] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.
[0062] The terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. In the following descriptions of embodiments, "a plurality of" means two or more, unless otherwise explicitly defined.
[0063] First, the prior art involved in this invention will be described and analyzed in detail.
[0064] In existing technologies, if users want to automate the execution of vehicle component actions through IFTTT tasks, they need to manually configure the IFTTT tasks, determine the If condition events and Then action events within the IFTTT tasks, and configure event parameters and the execution logic between events. This makes configuring IFTTT tasks complex and not very user-friendly. Furthermore, because IFTTT tasks are manually configured by the user, the configured IFTTT tasks may conflict with the environment, affecting the cabin experience and even driving safety, requiring manual editing and optimization by the user. For example, a user can configure an IFTTT task for automatically opening the sunroof, but opening the sunroof during rain can cause rainwater to enter the cabin, requiring the user to optimize the configuration of the automatic sunroof opening IFTTT task.
[0065] The inventors discovered in their research that they could acquire vehicle component data such as signal data from in-vehicle parts, perception data from in-vehicle sensors, and usage data from the cockpit central control screen. By combining this data with scenario information such as time, environmental weather, and geographical location, they could analyze regular data changes, determine If conditional events and Then action events based on the patterns of these data changes, and generate conditionally triggered IFTTT tasks.
[0066] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with relevant laws, regulations and standards, and corresponding operation entry points are provided for users to choose to authorize or refuse.
[0067] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.
[0068] Figure 1 This is a flowchart illustrating a condition-triggered task configuration method provided in this application embodiment. This application embodiment addresses the problems of IFTTT tasks relying entirely on user-generated and configured tasks, the complexity of configuring IFTTT tasks, and the potential for user-configured IFTTT tasks to conflict with the environment, requiring manual editing and optimization by the user in case of conflicts. The method in this embodiment is applied to a condition-triggered task configuration device, which can be located in an electronic device. The electronic device can be a digital computer of various forms, such as a laptop computer, desktop computer, workbench, personal digital assistant, server, blade server, mainframe computer, and other suitable computers.
[0069] like Figure 1 As shown, the specific steps of this method are as follows:
[0070] Step S101: Obtain event information for the target vehicle.
[0071] The event occurrence information includes: the time of occurrence of the target event; it should be understood that the event occurrence information may also include the target event identifier.
[0072] In this embodiment, the target event is an event that may occur under a preset scenario. Specifically, target events for each scenario can be pre-set in a preset scenario list. For example, for a rainy day scenario, target events may include: events corresponding to rainfall, window conditions, wiper conditions, air conditioning conditions, etc. As another example, target event identifiers in a rainy day scenario may include: whether it is raining according to the rain sensor (abbreviated as: raining according to the rain sensor), the degree of rain according to the rain sensor, driver's side window open / closed, driver's side window opening range, passenger side window open / closed, sunroof open / closed, wiper switch open / closed, wiper speed, air conditioning open / closed, air conditioning temperature, air conditioning mode, etc.
[0073] In this embodiment, target events can be configured in a preset scene list to avoid interference from events unrelated to the scene. The preset scene list predefines identifiers for each target event. If an event is determined to be a target event based on its identifier, and the occurrence of the target event is determined based on changes in its parameters, then the event occurrence time corresponding to the target event is stored in the event occurrence information.
[0074] Optionally, the event parameters first acquired after the vehicle is started or the vehicle door is opened can be determined as the event occurrence, and the acquired event parameters can be stored as event occurrence information.
[0075] Step S102: Form multiple event groups based on the occurrence time of the target event.
[0076] In this embodiment, the time-related target events can be target events with adjacent occurrence times. The occurrence time of each target event can be obtained from the event occurrence information, and target events with adjacent occurrence times can be identified as an event group.
[0077] In this embodiment of the application, the event type of the target event can be predefined. The event type of the target event can be condition, action, or condition and action.
[0078] Optionally, in this embodiment of the application, a preset time interval or preset time range for the continuous occurrence of events can be preset, and it can be determined whether multiple target events are temporally related based on the preset time interval or preset time range and the event type of the target event.
[0079] Optionally, the preset time interval can be divided into time intervals for similar events and time intervals for dissimilar events. Specifically, target events of the same type with an occurrence time shorter than the time interval for similar events can be identified as time-related target events, and target events of different types with an occurrence time shorter than the time interval for dissimilar events can be identified as time-related target events.
[0080] It should be understood that if target event 1 and target event 2 are time-related target events, and target event 2 and target event 3 are time-related target events, then target event 1, target event 2, and target event 3 are time-related target events.
[0081] Step S103: Determine scene condition events and scene action events based on the matched multiple event groups.
[0082] In this embodiment of the application, multiple event groups with similar corresponding event occurrence information can be identified as matching event groups.
[0083] It should be understood that two event groups can be matched with each other, or more than two event groups can be matched with each other.
[0084] Specifically, if it is determined that multiple matching event groups exist, it can be determined that the multiple matching event groups occur multiple times. The multiple matching event groups conform to the user's behavioral habits. Based on the multiple matching event groups, scene condition events and scene action events can be determined, and subsequent steps can be executed to generate condition-triggered tasks based on the event groups.
[0085] Among them, scene condition events are conditional events under a preset scene, and scene action events are action events under a preset scene. Under a preset scene, if a scene condition event occurs, the corresponding scene action event can be executed.
[0086] Optionally, after determining that the number of matching event groups exceeds a preset number of similar events, subsequent steps can be performed to generate an initial condition-triggered task based on the matching event groups.
[0087] Step S104: Generate conditions to trigger the IFTTT task based on scene condition events and scene action events.
[0088] The condition-triggered task can define: scene condition events and their corresponding preset condition parameters, and scene action events and their corresponding preset action parameters. Preset condition parameters are the event parameters of the scene condition event when the corresponding scene condition event is triggered, and preset action parameters are the desired event parameters of the scene action event after the scene action event is successfully executed according to the condition-triggered task.
[0089] In this embodiment, the conditional trigger task can be configured as an available conditional trigger task directly after it is generated; it can also be configured as an available conditional trigger task after the user confirms it; or it can be configured as an available conditional trigger task after the user's behavior meets the definition in the conditional trigger task multiple times.
[0090] The condition-triggered task configuration method provided in this application determines whether the event parameters of each target event in a preset scenario list have changed and stores the event occurrence information; based on the event occurrence information, multiple consecutive target events are identified as event groups; based on the event occurrence information corresponding to each of the multiple event groups, it is determined whether there are multiple matching event groups; based on the event occurrence time, current event parameters, and event type of each target event in the matching multiple event groups, an initial condition-triggered task is generated and configured. By monitoring event parameters, the automatic generation of condition-triggered tasks is achieved, improving the generation and configuration efficiency of condition-triggered tasks; and by setting a preset scenario list, only target events in the preset scenario list are monitored, avoiding interference from irrelevant events and improving the accuracy of determining event groups, thereby improving the accuracy of the determined condition-triggered tasks.
[0091] In an optional implementation, after step S104 generates a condition to trigger the IFTTT task based on scene condition events and scene action events, it may include:
[0092] Step S105: In response to the detection that a scene condition event of a certain IFTTT task is triggered, display the scene action event of the IFTTT task.
[0093] Step S106: In response to receiving a confirmation operation from the user through the operation interface for a scene action event, control the corresponding vehicle component to perform the action according to the scene action event, and determine the number of times the user confirms the scene action event for the IFTTT task.
[0094] Step S107: In response to the number of confirmation operations exceeding the preset confirmation number threshold, configure the IFTTT task as an automatically executed IFTTT task.
[0095] Specifically, after generating the condition-triggered task, the user needs to confirm the condition-triggered task; after the user confirms the condition-triggered task, the corresponding vehicle components are controlled to perform actions according to the scene action events, and the condition-triggered task can be determined as an automatically executed IFTTT task.
[0096] Optionally, a preset confirmation threshold can be set in advance. Only after the number of user confirmation operations exceeds the preset confirmation threshold will the IFTTT task be configured as an automatically executed IFTTT task.
[0097] The condition-triggered task configuration method provided in this application, in response to the detection of a scene condition event for an IFTTT task being triggered, displays the scene action event of the IFTTT task; in response to receiving a user's confirmation operation on the scene action event triggered through the operation interface, controls the corresponding vehicle component to perform actions according to the scene action event, and determines the number of times the user confirms the scene action event of the IFTTT task; in response to the number of confirmation operations exceeding a preset confirmation threshold, configures the IFTTT task as an automatically executed IFTTT task. This avoids situations where the generated condition-triggered tasks do not meet user needs, and allows condition-triggered tasks to be automatically executed only after user confirmation, making automatically executed condition-triggered tasks more in line with user habits. Dividing the configuration of condition-triggered tasks into two levels facilitates user confirmation of condition-triggered tasks, avoids the automatic execution of unconfirmed condition-triggered tasks, and improves the user experience.
[0098] Optionally, after determining the condition-triggered task as an automatically executed IFTTT task, the automatically executed IFTTT task can be enabled, and actions can be performed according to the enabled automatically executed IFTTT task, specifically including:
[0099] In response to the user's activation of the IFTTT task through the operation interface, the system monitors the scene condition events of the IFTTT task; in response to the detection that the scene condition event of the IFTTT task is triggered, the system sends control commands to the corresponding vehicle components to control the corresponding vehicle components to perform actions according to the scene action events of the IFTTT task.
[0100] In this embodiment of the application, after completing the configuration operation for the automatically executed IFTTT task, it can be directly determined to enable the automatically executed IFTTT task; alternatively, the automatically executed IFTTT task can be determined to be disabled first, and then manually enabled by the user. This embodiment of the application does not limit this.
[0101] In this embodiment of the application, a task enablement control can be provided in the operation interface so that the user can choose whether to enable automatically executed IFTTT tasks.
[0102] Specifically, to identify enabled automatically executed IFTTT tasks, the event parameters of scene condition events within those tasks can be monitored to determine if they have changed. If a change in the event parameters is detected, it is determined that the scene condition event of the IFTTT task has been triggered. Control commands are then sent to the corresponding vehicle components to control them to perform actions according to the scene action events of the IFTTT task.
[0103] The control commands may include scene action events and corresponding preset action parameters.
[0104] The condition-triggered task configuration method provided in this application embodiment can, after configuring and enabling the condition-triggered task, monitor whether the scene condition event in the condition-triggered task is triggered. If triggered, the scene action event in the condition-triggered task can be automatically executed to realize the automated execution of the condition-triggered task and improve the user experience.
[0105] In one optional implementation, step S102, which involves forming multiple event groups based on the occurrence time of the target event, can be achieved as follows:
[0106] Obtain multiple pre-configured preset time ranges; for each preset time range, form an event group from multiple target events occurring within that preset time range.
[0107] For example, one hour can be defined as a preset time range, and multiple target events that occur within one hour can be defined as an event group. Figure 2 This is a schematic diagram of event parameter monitoring provided in an embodiment of this application, such as... Figure 2 As shown, the target events in the preset scenario list can include target events 1 to 5, with a preset time range of one hour. The system determines whether the event parameters of the target events change every hour, and targets whose event parameters change within one hour are grouped into one event group. Specifically, if the event parameters of target events 1, 2, and 5 change within the time range of 7 o'clock, then target events 1, 2, and 5 are grouped into event group 1; if the event parameters of target events 3 and 4 change within the time range of 9 o'clock, then target events 3 and 4 are grouped into event group 2.
[0108] Figure 3 Another schematic diagram illustrating the determination of event groups based on a preset time range provided in this application embodiment, such as... Figure 3 As shown, during the 19:00 to 20:00 time period for four consecutive days, multiple matching event groups were recorded, specifically: location + music player on / off + navigation on / off + navigation settings. The event parameter corresponding to location is the workplace, the event parameter corresponding to music player on / off is "on", the event parameter corresponding to navigation on / off is "on", and the event parameter corresponding to navigation settings is "navigate home". Based on the matching event groups, a conditional trigger task can be generated. This conditional trigger task is that when the vehicle location is at the workplace between 19:00 and 20:00, the music player should be turned on to play music, the navigation should be turned on, and the navigation should be navigated home.
[0109] The condition-triggered task configuration method provided in this application obtains multiple pre-configured preset time ranges; for each preset time range, multiple target events occurring within the preset time range are grouped into an event group. When the target events are strongly correlated with the time range, the associated event group can be determined more accurately, thereby improving the accuracy of determining the initial condition-triggered task.
[0110] In another optional implementation, step S102, which involves forming multiple event groups based on the occurrence time of the target event, can be implemented as follows:
[0111] Retrieves key target events and their corresponding event types from pre-configured target events. Event types include: conditions and actions; based on event type, event occurrence time, and preset event time interval, it determines associated target events and forms multiple event groups.
[0112] Among them, key target events are those that require special attention and can be identified as target events that will occur in a specific scenario. It should be understood that when defining target events, the event type can be determined based on a pre-set list of scenarios, or the event type can be defined manually.
[0113] In this embodiment, there can be multiple key target events or just one. A key target event can be either a conditional event or an action event. An action event is an event of type action, and a conditional event is an event of type condition.
[0114] Specifically, a user can define a key target event, such as a conditional event or an action event, to listen for the associated target event when the defined conditional event or action event occurs. After determining that the event parameters of the key target event have changed, if the event type of the key target event is determined to be an action, step S201 can be executed; if the event type of the key target event is determined to be a condition, step S202 can be executed; if the event type of the key target event is determined to be both a condition and an action, steps S201 and S202 can be executed.
[0115] Step S201: In response to the key target event, the event type is action. Based on the preset event time interval and the target events that occurred before the key target event, the first associated event that is related to the key target event and whose event type is condition is determined. The first associated event, the key target event, and the target events that occur between the first associated event and the key target event are determined as associated target events to form an event group.
[0116] Among them, the first associated event is a target event that occurred before the key target event, and the event type is conditional. The occurrence time of each target event in the event group is less than the corresponding preset event time interval.
[0117] In this embodiment of the application, at least one candidate first target event can be determined from the target events that occurred consecutively before the key target event, wherein the time interval between any two adjacent target events is less than a preset event time interval; and from the at least one candidate first target event, the first associated event that is farthest from the key target event and whose event relationship type is conditional can be determined.
[0118] Specifically, if a key target event of an action type is detected, then the system searches for target events of action or condition type within a preset event time interval before the key target event occurs. If a target event within a preset event time interval before the target event occurs is found, the system continues to search for target events within the same preset event time interval until a target event of condition type is found. If no target event of condition type occurs within the same preset event time interval before the target event occurs, then the target event is identified as the first associated event. The first associated event, the key target event, and the target events occurring between the first associated event and the key target event are identified as an event group.
[0119] Step S202: In response to the event type of the key target event, based on the preset time interval and the event occurrence time, among the target events that occur after the key target event, determine the last associated event that is related to the key target event and whose event type is action; determine the key target event, the last associated event, and the target events that occur between the key target event and the last associated event as associated target events to form an event group.
[0120] Among them, the last target event is a target event that occurs before or after the key target event, and the event type includes actions. The occurrence time of each target event in the event group is less than the corresponding preset event time interval.
[0121] In the implementation of this application, at least one candidate last target event can be determined from the key target event and the target events that occur consecutively thereafter, wherein the time interval between any two adjacent target events is less than a preset event time interval; and from at least one candidate last target event, the last associated event that is farthest from the key target event and whose event relationship type is action can be determined.
[0122] Specifically, if a key target event of the condition type is detected, it is determined whether a target event of the action type occurs within a preset event time interval after the key target event occurs. If a target event of the action type occurs, it is possible to continue monitoring whether a target event of the action or condition type occurs within a preset event time interval after the target event occurs, until a target event of the action type occurs within the preset event time interval, and no target event occurs within the preset event time interval after the target event. In this case, the target event is identified as the last associated event, and the key target event, the last associated event, and the target events that occur between the key target event and the last associated event are identified as an event group.
[0123] In this embodiment, determining event groups based on preset event time intervals can avoid the limitation of preset time ranges, prevent an event group from being separated by time ranges, and accurately identify event groups that are not related to time ranges. By defining key target events, event groups can be identified only after key target events occur, which can reduce the resource consumption of identifying event groups.
[0124] Based on the above embodiments, the specific steps of step S101, which involves obtaining event occurrence information of the target vehicle, include:
[0125] Step S301: Obtain the reporting information sent by each component of the vehicle.
[0126] The reported information includes: the reporting interface identifier, the reported parameters, and the information type. The information type can be: status information, control information, request information, response information, or API interface information. The reported parameters include the parameter identifier and the parameter value.
[0127] Step S302: Determine the corresponding target vehicle atomic capabilities based on the reported information, and determine the events to be screened corresponding to the target vehicle atomic capabilities based on the mapping relationship between vehicle atomic capabilities and event identifiers.
[0128] In this application embodiment, different reporting interface identifiers and information types can correspond to the same target vehicle atomic capability. For example, the control information of the central control screen interface on the window and the window status information of the in-vehicle component interface can correspond to the target vehicle atomic capability of the window being open.
[0129] Specifically, based on the reporting interface identifier, information type, and parameter identifier in the reported information, the target vehicle atomic capabilities corresponding to the reported information can be determined. After determining the target vehicle atomic capabilities, the events to be filtered corresponding to the target vehicle atomic capabilities can be determined. Among them, the events to be filtered are the events corresponding to the reported information, which may or may not be target events.
[0130] After identifying the events to be filtered, steps S303 to S305 can be executed to determine whether the events to be filtered are target events in the preset scenario list.
[0131] In the embodiments of this application, the mapping relationship between vehicle atomic capabilities and event identifiers can be a one-to-one relationship or a many-to-many relationship, etc., and this application does not limit it in this way.
[0132] Step S303: Determine the event category of the event to be filtered, and determine whether the event category of each target event in the preset scene list includes the event category of the event to be filtered.
[0133] Step S304: If an event category including the event to be filtered is determined, then determine whether the event identifier of each target event in the preset scene list includes the event identifier of the event to be filtered.
[0134] Step S305: If it is determined that the event identifier includes the event to be filtered, then the event to be filtered is determined to be the target event in the preset scene list.
[0135] In this embodiment of the application, event categories for each event can be predefined. For example, an event category of "air conditioning" may include events such as "air conditioning heating up," "air conditioning cooling down," and "air conditioning recirculation." An event category of "driver getting out of the vehicle" may include events such as "driver sitting in the driver's seat" and "driver's door opening and closing." An event category of "rain" may include events such as "rain detected by the rain sensor" and "rain detected by the weather ecosystem."
[0136] Predefining event categories for each event facilitates event filtering, monitoring, and target event selection. For example, by selecting an event category, events within that category can be identified as target events.
[0137] In this embodiment of the application, if it is determined that the event category of each target event in the preset scenario list does not include the event category of the event to be filtered, then it can be determined that the event to be filtered is not a target event, and no further operation is required, which can improve the efficiency of determining whether the event to be filtered is a target event.
[0138] Step S306: If the target event in the preset scenario list of events to be filtered is determined, the reported parameters are converted into the current atomic capability parameters according to the preset atomic parameter conversion strategy of the target vehicle's atomic capability.
[0139] The current atomic capability information includes the reporting interface identifier and the current atomic capability parameters.
[0140] In this embodiment, the current atomic capability parameter may differ from the corresponding reported parameter. For example, the range of the parameters reported by the rain gauge sensor may be 0-4 mm / min, while the corresponding current atomic capability parameter may be no rain - 0, light rain - 1, moderate rain - 2, heavy rain - 3, or torrential rain - 4. The rain gauge sensor reported parameter can be converted into the corresponding current atomic capability parameter based on the corresponding preset atomic parameter conversion strategy.
[0141] It should be understood that due to differences in vehicle components, the reported parameters may vary and may be overly granular. By configuring a preset atomic parameter conversion strategy, the reported parameters can be converted into unified and appropriately granular current atomic capability parameters, which facilitates the determination of target events and event parameters.
[0142] Step S307: Convert the current atomic capability parameters into the current event parameters of the event to be filtered according to the preset event parameter conversion strategy of the event to be filtered.
[0143] For example, the current atomic capability parameter of the target vehicle's atomic capability - rain sensor can be no rain - 0, light rain - 1, moderate rain - 2, heavy rain - 3, and torrential rain - 4, while the corresponding event parameter of the rain sensor to be screened - rain can be no rain - 0 or rain - 1. It is necessary to pre-set the corresponding preset event parameter conversion strategy to convert the current atomic capability parameter no rain - 0 into the event parameter no rain - 0, and to convert the current atomic capability parameters light rain - 1, moderate rain - 2, heavy rain - 3, and torrential rain - 4 into the event parameter rain - 1.
[0144] Step S308: If it is determined that the current event parameter of the event to be filtered is different from the last event parameter of the corresponding event in the event occurrence information, then the event to be filtered is determined as the target event, and the current event parameter of the target event is determined as the current event parameter of the event to be filtered.
[0145] In this embodiment, the event to be filtered can be a target event or an event that has not occurred. After determining that the event to be filtered is a target event and confirming its current event parameters, the event parameters of the last record corresponding to the event identifier can be searched in the event occurrence information. If the current event parameters of the event to be filtered are different from the last event parameters of the corresponding event in the event occurrence information, it can be determined that the event to be filtered has occurred, and the event to be filtered can be identified as the target event. The current event parameters of the target event are then identified as the current event parameters of the event to be filtered. The last event parameters of the corresponding event are the event parameters of the last record corresponding to the event identifier in the event occurrence information.
[0146] Step S309: Determine the time of receiving the reported information as the time of occurrence of the target event.
[0147] Step S310: Store the event identifier of the target event, the event occurrence time of the target event, and the current event parameters of the target event as event occurrence information.
[0148] In this embodiment of the application, since the time accuracy requirement for the occurrence time of the target event is low, the time of receiving the reported information can be determined as the occurrence time of the target event, which facilitates the determination of the occurrence time of the target event.
[0149] Optionally, the reported information may also include the time when the reported parameters were obtained, and the time when the reported parameters were obtained in the reported information can be determined as the event occurrence time of the target event.
[0150] The following example illustrates the condition-triggered task configuration method provided in the above embodiments, specifically including the following steps:
[0151] Step S401: Obtain event occurrence information for the target vehicle.
[0152] Step S402: Form multiple event groups based on the occurrence time of the target event.
[0153] Step S403: Calculate the event similarity between event groups based on the event occurrence information corresponding to the target event in multiple event groups, using preset dimensions. The preset dimensions of event similarity include: event identifier similarity, event quantity similarity, and event triggering order similarity.
[0154] This application does not limit the method of calculating similarity. For example, algorithms such as Euclidean distance and Jaccard similarity coefficient can be used to calculate the above-mentioned similarities.
[0155] For example, the similarity of event identifiers can be determined using the Jaccard similarity coefficient algorithm, and the similarity of the number of events can be determined based on the ratio of the number of events between event groups; target events with the same event identifiers between event groups can be identified, and the similarity of event triggering order and event parameter similarity can be determined based on the target events with the same event identifiers.
[0156] Step S404: Perform a weighted summation on the event similarity of the preset dimensions, and determine the weighted summation result as the event group similarity between event groups.
[0157] Specifically, the weights of each similarity can be predetermined. After calculating each similarity, the similarities can be summed in weights based on their respective weights, and the result of the weighted summation can be determined as the similarity between event groups.
[0158] Step S405: Identify multiple event groups whose event group similarity is greater than a preset similarity threshold as multiple matching event groups.
[0159] Optionally, the similarity between event groups can be determined pairwise. If the similarity between at least two event groups is greater than a preset similarity threshold, then it can be determined that there are multiple matching event groups.
[0160] In this embodiment, multiple matching event groups are determined based on the similarity of event identifiers, the similarity of event quantity, the similarity of event triggering order, and the similarity of event parameters between event groups. This fully considers the influence of multiple perspectives on the similarity between event groups, improves the accuracy of determining multiple matching event groups, and thus improves the accuracy of determining the initial conditions for triggering tasks.
[0161] Step S406: Determine the order and time interval of the target events in the matching event groups based on the occurrence times of the target events in the matching event groups.
[0162] Step S407: Determine the scene condition events and scene action events based on the order and type of the target events in the matched event groups.
[0163] Specifically, high-frequency target events can be selected from multiple matching event groups; high-frequency target events with earlier occurrence times and event types including conditions are identified as scene condition events in the condition-triggered task; and high-frequency target events with later occurrence times and event types including actions are identified as scene action events in the condition-triggered task.
[0164] Step S408: Generate conditions to trigger the IFTTT task based on scene condition events and scene action events.
[0165] Figure 4 This is a schematic diagram illustrating a condition-triggered task configuration example provided in an embodiment of this application. An event category called "rain" can be predefined. The event identifiers within this "rain" event category include "rain from rain sensor" and "rain from weather and ecology," and the corresponding event parameters include: "no rain" and "rainy." For example... Figure 4As shown, target events defined as conditions in the preset scenario list include: rain sensor rain and weather / ecological rain, with corresponding event parameters including: no rain and rain; target events defined as actions include: window switch and air conditioner switch, with corresponding event parameters including: no rain and open / close. The key target event can be determined by the event category "rain" as either "rain sensor rain" or "weather / ecological rain," with the preset condition parameter for the key target event "rain sensor" being "rain" and the preset condition parameter for the key target event "weather / ecological rain" being "rain." The preset time interval is set to 30 seconds. By listening to the event parameters of each target event for 30 seconds after the key target event is triggered, six event groups can be identified: Event Group 1: Weather / ecological rain + rain sensor rain + window switch + air conditioner switch; Event Group 2: Weather / ecological rain + window switch + air conditioner switch; Event Group 3: Rain sensor rain + window open. The event groups are: 1. Rain on / off + air conditioning switch; 2. Rain sensor rain + window switch; 3. Rain on / off + rain sensor rain + window switch; 4. Rain on / off + window switch + air conditioning switch. Based on the event occurrence information corresponding to the six event groups, the matching event group is determined to be: Rain on / off + rain sensor rain + window switch + air conditioning switch. The event parameter for window switch is from open to closed, and the event parameter for air conditioning switch is from closed to open. Therefore, rain on / off and the corresponding preset condition parameter "rainy" and rain sensor rain and the corresponding preset condition parameter "rainy" are determined as the scene condition events and corresponding preset condition parameters in the conditional trigger task. The event parameter for window switch is "closed", and the event parameter for air conditioning switch is "open", and the event parameter for air conditioning switch is "open", are determined as the scene action events and corresponding preset action parameters in the conditional trigger task. The conditional trigger task is then recommended to the user.
[0166] Figure 5 This is a schematic diagram of the structure of a condition-triggered task configuration device provided in an embodiment of this application. The condition-triggered task configuration device provided in this embodiment can execute the processing flow provided in the embodiment of the condition-triggered task configuration method. For example... Figure 5 As shown, the condition-triggered task configuration device 50 includes: a listening module 501, an event group determination module 502, a matching module 503, a generation module 504, and a configuration module 505.
[0167] Specifically, the listening module 501 is used to acquire event occurrence information of the target vehicle; the event occurrence information includes the event occurrence time corresponding to the target event;
[0168] The event group determination module 502 is used to form multiple event groups based on the occurrence time of the target event; the event group includes multiple target events that are related in time.
[0169] Event splitting module 503 is used to determine scene condition events and scene action events based on multiple matching event groups;
[0170] The task generation module 504 is used to generate conditions to trigger IFTTT tasks based on scene condition events and scene action events.
[0171] The apparatus provided in this application embodiment can be specifically used to execute the method embodiment provided in the above embodiment, and the specific functions will not be repeated here.
[0172] Optionally, the event group determination module 502 is specifically used to: obtain multiple preset time ranges that are pre-configured; and for each preset time range, form multiple target events that occur within the preset time range into an event group.
[0173] Optionally, the event group determination module 502 is further used to: obtain key target events and corresponding event types from pre-configured target events; event types include: conditions and actions; determine associated target events based on event type, event occurrence time, and preset event time interval to form multiple event groups.
[0174] Optionally, the event group determination module 502 further includes an association determination unit, which is used to: in response to the key target event having an event type of action, determine the first associated event that is associated with the key target event and has an event type of condition among target events that occur before the key target event based on a preset event time interval and the event occurrence time; and determine the first associated event, the key target event, and the target events that occur between the first associated event and the key target event as associated target events to form an event group;
[0175] In response to the key target event, based on the event type as a condition, and considering the preset time interval and the event occurrence time, among the target events that occur after the key target event, the last associated event that is related to the key target event and whose event type is action is identified; the key target event, the last associated event, and the target events that occur between the key target event and the last associated event are identified as associated target events, forming an event group.
[0176] Optionally, the association determination unit is specifically used to: determine from the key target event and the target events that occurred consecutively before it, where the time interval between any two adjacent target events is less than a preset event time interval; and determine from the at least one candidate first target event the first associated event that is farthest from the key target event and whose event relationship type is conditional.
[0177] The association determination unit is also specifically used for: determining, from the key target event to the target events that occur consecutively after it, at least one candidate last target event, where the time interval between any two adjacent target events is less than a preset event time interval; and determining, from at least one candidate last target event, the last associated event that is furthest from the key target event and whose event relationship type is action.
[0178] Optionally, the event occurrence information also includes an event identifier, and the condition-triggered task configuration device 50 further includes a matching module, which is used to: calculate the event similarity between event groups in a preset dimension based on the event occurrence information corresponding to the target event in multiple event groups; the event similarity in the preset dimension includes: event identifier similarity, event quantity similarity, and event triggering order similarity; perform a weighted summation on the event similarity in the preset dimension, and determine the weighted summation result as the event group similarity between event groups; and determine multiple event groups whose event group similarity is greater than a preset similarity threshold as multiple matching event groups.
[0179] Optionally, the event splitting module 503 is specifically used to: determine the order and time interval of the target events in the matching event groups based on the event occurrence time of the target events in the matching event groups; and determine the scene condition events and scene action events based on the order and event type of the target events in the matching event groups.
[0180] Optionally, the condition-triggered task configuration device 50 further includes: a configuration module, the configuration module being used for:
[0181] In response to the detection that a scene condition event for a certain IFTTT task is triggered, the scene action event of the IFTTT task is displayed; in response to receiving a confirmation operation for the scene action event triggered by the user through the operation interface, the corresponding vehicle component is controlled to perform the action according to the scene action event, and the number of times the user confirms the scene action event of the IFTTT task is determined; in response to the number of confirmation operations exceeding a preset confirmation number threshold, the IFTTT task is configured as an automatically executed IFTTT task.
[0182] Optionally, the configuration module 505 also includes:
[0183] In response to a user enabling an IFTTT task via the user interface, the system monitors the scene condition events of the IFTTT task. Upon detecting that a scene condition event of the IFTTT task is triggered, a control command is sent to the corresponding vehicle component to control the corresponding vehicle component to perform actions according to the scene action events of the IFTTT task. The apparatus provided in this application embodiment can be specifically used to execute the above method embodiment; its specific functions will not be elaborated here.
[0184] Figure 6 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application, such as... Figure 6 As shown, this application also provides an electronic device 60, including: a processor 601, and a memory 602 and a transceiver 603 communicatively connected to the processor 601. The memory 602 stores computer-executable instructions; the transceiver 603 is used for sending and receiving data; the processor 601 executes the computer-executable instructions stored in the memory 602 to implement the method provided in any embodiment of this application.
[0185] Specifically, the program may include program code, which includes computer-executable instructions. Memory 602 may include high-speed RAM, and may also include non-volatile memory, such as at least one disk storage device. The computer-executable instructions are stored in memory 602 and configured to be executed by processor 601 to implement the method provided in any embodiment of this application. Related descriptions can be understood by referring to the relevant descriptions and effects corresponding to the steps in the accompanying drawings, and will not be elaborated upon here.
[0186] In this embodiment, the memory 602 and the processor 601 are connected via a bus. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 6 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.
[0187] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method provided in any embodiment of this application.
[0188] This application also provides a computer program product, including computer execution instructions, which, when executed by a processor, implement the method provided in any embodiment of this application.
[0189] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.
[0190] The modules described as separate components may or may not be physically separate. Similarly, the components shown as modules may or may not be physical modules; they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment, depending on actual needs.
[0191] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated module can be implemented in hardware or in a combination of hardware and software functional modules.
[0192] The program code used to implement the methods of this application may be written in any combination of one or more programming languages. This program code may be provided to the processor or controller of a general-purpose computer, special-purpose computer, or other programmable full-path fusion device, such that when executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.
[0193] In the context of this application, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.
[0194] Furthermore, although the operations are described in a specific order, this should be understood as requiring that such operations be performed in the specific order shown or in sequential order, or requiring that all illustrated operations be performed to achieve the desired result. In certain environments, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this application. Certain features described in the context of individual embodiments may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented individually or in any suitable sub-combination in multiple implementations.
[0195] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.
[0196] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.
Claims
1. A method for configuring condition-triggered tasks, characterized in that, include: Obtain the reported information sent by each component of the vehicle; Based on the reported information, the corresponding target vehicle atomic capabilities are determined, and based on the mapping relationship between vehicle atomic capabilities and event identifiers, the events to be screened corresponding to the target vehicle atomic capabilities are determined. Determine whether the event to be filtered is an event in the preset scenario list; The list of preset scenarios includes configured listening events; If so, the reporting parameters in the reported information are converted into the current event parameters of the event to be filtered; If it is determined that the current event parameter is different from the last event parameter of the corresponding event in the event occurrence information, then the event to be filtered is determined as the target event, and the receiving time of the reported information is determined as the event occurrence time of the target event; Multiple event groups are formed based on the occurrence time of the target events; each event group includes multiple target events that are related in time. Scene condition events and scene action events are determined based on multiple matching event groups; The IFTTT task is triggered based on the conditions generated by the scene condition events and scene action events.
2. The method according to claim 1, characterized in that, The process of forming multiple event groups based on the occurrence time of the target event includes: Obtain multiple pre-configured preset time ranges; For each preset time range, multiple target events occurring within that preset time range are grouped into an event group.
3. The method according to claim 1, characterized in that, The process of forming multiple event groups based on the occurrence time of the target event includes: Retrieve key target events and their corresponding event types from pre-configured target events; the event types include: conditions and actions; Based on the event type, the event occurrence time, and the preset event time interval, the associated target events are determined, forming multiple event groups.
4. The method according to claim 3, characterized in that, The process involves determining associated target events based on the event type, the event occurrence time, and a preset time interval between events, forming multiple event groups, including: In response to the key target event, the event type is action. Based on the preset event time interval and the event occurrence time, among the target events that occurred before the key target event, the first associated event that is related to the key target event and whose event type is condition is determined. The first related event, the key target event, and the target events that occur between the first related event and the key target event are identified as related target events, forming an event group; In response to the key target event, the event type is used as a condition. Based on the preset time interval and the time of occurrence of the event, among the target events that occur after the key target event, the last associated event that is associated with the key target event and whose event type is action is determined. Key target events, last-ranking related events, and target events occurring between key target events and last-ranking related events are identified as related target events, forming event groups.
5. The method according to claim 4, characterized in that, The method of determining the first associated event that is related to the key target event and whose event type is a condition, based on the preset event time interval and the event occurrence time, includes: Determine at least one candidate first target event from the key target event and the target events that occurred consecutively before it, wherein the time interval between any two adjacent target events is less than a preset event time interval; From at least one candidate primary target event, determine the primary associated event that is furthest from the key target event and whose event relationship type is conditional; The method of determining the last associated event of type action among target events occurring after the key target event based on a preset time interval and the event occurrence time includes: Determine at least one candidate last target event from the key target event and subsequent consecutive target events, wherein the time interval between any two adjacent target events is less than a preset event time interval; From at least one candidate last target event, determine the last associated event that is furthest from the key target event and whose event relationship type is action.
6. The method according to claim 1, characterized in that, The event occurrence information also includes an event identifier; Before determining scene condition events and scene action events based on multiple matching event groups, the process also includes: The event similarity between event groups is calculated based on the event occurrence information corresponding to the target event in multiple event groups, and the event similarity in the preset dimensions includes: event identifier similarity, event quantity similarity, and event triggering order similarity. The event similarity of the preset dimensions is weighted and summed, and the weighted summation result is determined as the event group similarity between event groups; Multiple event groups whose event group similarity is greater than a preset similarity threshold are identified as multiple matching event groups.
7. The method according to any one of claims 1-6, characterized in that, The determination of scene condition events and scene action events based on multiple matched event groups includes: The order and time interval of the target events in the matched event groups are determined based on the occurrence times of the target events in the matched event groups. The scene condition events and scene action events are determined based on the sequence and event type of the target events in the matched event groups.
8. The method according to any one of claims 1-6, characterized in that, After generating conditions to trigger the IFTTT task based on the scene condition events and scene action events, the process further includes: In response to the detection that a scene condition event of a certain IFTTT task is triggered, the scene action event of the IFTTT task is displayed; In response to receiving a confirmation operation from the user through the operation interface for a scene action event, control the corresponding vehicle components to perform actions according to the scene action event, and determine the number of times the user confirms the scene action event for the IFTTT task. In response to the number of confirmation operations exceeding a preset confirmation threshold, the IFTTT task is configured as an automatically executed IFTTT task.
9. The method according to claim 8, characterized in that, After configuring the IFTTT task as an automatically executed IFTTT task in response to the number of confirmation operations exceeding a preset confirmation threshold, the following steps are included: In response to the user's activation of the IFTTT task through the operation interface, the scene condition events of the IFTTT task are monitored. In response to the detection that a scene condition event of the IFTTT task is triggered, a control command is sent to the corresponding vehicle component to control the corresponding vehicle component to perform actions according to the scene action event of the IFTTT task.
10. A condition-triggered task configuration device, characterized in that, include: The monitoring module is used to acquire the reported information sent by various vehicle components; Based on the reported information, the corresponding target vehicle atomic capabilities are determined, and based on the mapping relationship between vehicle atomic capabilities and event identifiers, the events to be screened corresponding to the target vehicle atomic capabilities are determined. Determine whether the event to be filtered is an event in the preset scenario list; The list of preset scenarios includes configured listening events; If so, the reporting parameters in the reported information are converted into the current event parameters of the event to be filtered; If it is determined that the current event parameter is different from the last event parameter of the corresponding event in the event occurrence information, then the event to be filtered is determined as the target event, and the receiving time of the reported information is determined as the event occurrence time of the target event; The event group determination module is used to form multiple event groups based on the occurrence time of the target event; the event group includes multiple target events that are related in time. The event splitting module is used to determine scene condition events and scene action events based on multiple matching event groups; The task generation module is used to generate conditions to trigger IFTTT tasks based on the scene condition events and scene action events.
Citation Information
Patent Citations
Method for carrying out aggregation recommendation on events recommended on vehicle-mounted equipment and storage medium
CN116701748A
