Intelligent scene control method, device and system and storage medium

Abstract

The invention provides an intelligent scene control method, device and system and a storage medium, and belongs to the technical field of intelligent cabin scene control, and the method comprises the steps: firstly responding to the triggering of an intelligent scene, and determining whether a user account of the intelligent scene is matched with a current login account of a vehicle; if so, carrying out conflict detection on a plurality of scenes triggered by the current user; and when a conflict is detected, judging a conflict scene based on a preset hierarchical arbitration rule so as to determine a final execution scene, and executing a vehicle state control instruction defined by the scene. According to the invention, the security of intelligent scene execution and the user intention conformity are improved.

Description

Technical Field

[0001] This invention relates to the field of intelligent cockpit scene control technology, specifically to an intelligent scene control method, device, system, and storage medium. Background Technology

[0002] With the deep integration of automotive intelligence and connectivity technologies, intelligent scene functions aimed at enhancing driving comfort and convenience are gradually becoming a core component of the user experience. Intelligent scenes (such as "rest mode" and "pet mode") essentially involve pre-programming and combining various vehicle control capabilities (such as air conditioning, seats, windows, and media) to form complex operation sequences that can be triggered with a single click or executed automatically based on conditions. Currently, intelligent scenes are used by users to flexibly create and edit personal scenes through various sources such as user-end applications (such as mobile apps) and in-vehicle central control screens, and can be authorized for use by other family members, achieving personalized vehicle control modes of "one scene per person" or even "multiple scenes per person."

[0003] Currently, intelligent scenarios based on multi-user, multi-scenario editing and triggering mechanisms have led to significant execution conflicts in practice. First, scenario conflicts between different users are difficult to avoid. For example, when a vehicle is driven by user A, scenarios set under user A's account and scenarios set by user B may simultaneously meet their triggering conditions, causing state confusion (e.g., one scenario requires closing the window while another requires opening it). Second, multiple scenarios created by the same user may experience direct operational conflicts (e.g., mutually exclusive commands to open / close windows) or implicit goal conflicts (e.g., the maximum power cooling of the "rapid cooling" scenario contradicts the power-saving goal of the "ultimate energy saving" scenario). Currently, the industry generally adopts single, fixed strategies such as "first-come, first-served" or "last-come overwrites first-come" to handle these conflicts.

[0004] In the process of realizing this invention, the inventors found that the existing approach has at least the following problems: such strategies lack a detailed identification of the root causes of conflict and fail to consider key factors such as security, user intent, and real-time environment, which can easily lead to the execution results deviating from the user's actual needs and may even cause security risks and energy waste. Summary of the Invention

[0005] In view of this, it is necessary to provide an intelligent scene control method, device, system and storage medium to solve the technical problems of low execution result security and inaccurate understanding of user intent caused by the use of a single and fixed conflict handling strategy in the existing methods.

[0006] To address the aforementioned technical problems, in a first aspect, the present invention provides an intelligent scene control method, comprising:

[0007] In response to the triggering of a smart scene in the vehicle, it is determined whether the user account to which the triggered smart scene belongs matches the currently logged-in user account of the vehicle, and a matching result is obtained; If the matching result is a match, conflict detection is performed on multiple intelligent scenarios triggered by the currently logged-in user account; If a conflict is detected, the multiple intelligent scenarios of the conflict are arbitrated based on the preset hierarchical arbitration rules to determine the execution scenario. Execute the vehicle state control commands defined in the execution scenario.

[0008] In one possible implementation, the conflict detection of multiple intelligent scenarios triggered by the currently logged-in user account includes: Multiple triggered intelligent scenarios are parsed into a set of operations for vehicle atomic capability items, where the vehicle atomic capability item is the smallest operational unit that independently controls the vehicle's functions. Each of the operation sets is compared with a pre-built capability item relation library, which defines the mutual exclusion relationships between vehicle atomic capability items; If two smart scenarios have operation sets containing mutually exclusive atomic capability operations, then a conflict is detected.

[0009] In one possible implementation, after determining whether the user account to which the triggered intelligent scene belongs matches the currently logged-in user account of the vehicle, and obtaining a matching result, the intelligent scene control method includes: If the matching result is a mismatch, the subsequent conflict detection and arbitration process for the intelligent scenario will be terminated, and a blocking or suspension operation will be performed for the intelligent scenario.

[0010] In one possible implementation, the step of determining whether the user account to which the triggered smart scene belongs matches the currently logged-in user account of the vehicle is performed on a cloud server, and the smart scene and the user account that created the smart scene are bound and stored on the cloud server.

[0011] In one possible implementation, the arbitration based on preset hierarchical arbitration rules includes performing at least one of the following adjudication operations in priority order: The decision is made based on safety and regulatory rules, with the highest priority. If the conflict cannot be resolved by the preceding adjudication, a second priority adjudication will be made based on the predefined mutual exclusion or dependency relationship between vehicle atomic capability items; If the conflict cannot be resolved by the preceding rulings, a third-priority ruling will be made based on the scenario attributes and user preferences. If the conflict cannot be resolved by the preceding rulings, a fourth priority ruling will be made based on real-time vehicle data or environmental data.

[0012] In one possible implementation, the second priority decision based on predefined mutual exclusion or dependency relationships between vehicle capability items includes: When the operation of the first intelligent scenario depends on a vehicle atomic capability operation, and the operation of the second intelligent scenario is mutually exclusive with that vehicle capability operation, the decision prioritizes ensuring the execution of the first intelligent scenario or the necessary pre-operation.

[0013] In one possible implementation, the third priority decision based on scenario attributes and user preferences includes at least one of the following: The decision is made based on the basic weights corresponding to the type of intelligent scenario. The decision is made based on the priority of the trigger source of the intelligent scene. Among them, the priority of in-vehicle voice or physical button trigger is higher than the vehicle screen touch trigger, the vehicle screen touch trigger is higher than the mobile application remote trigger, and the mobile application remote trigger is higher than the automatic condition trigger. The adjudication is based on user-defined conflict resolution rules.

[0014] On the other hand, the present invention also provides an intelligent scene control device, comprising: The account matching module is used to determine whether the user account to which the triggered intelligent scene belongs matches the currently logged-in user account of the vehicle in response to the intelligent scene of the vehicle being triggered, and to obtain the matching result. The conflict detection module is used to perform conflict detection on multiple intelligent scenarios triggered by the currently logged-in user account if the matching result is a match. The conflict arbitration module is used to arbitrate multiple intelligent scenarios of the conflict based on preset hierarchical arbitration rules if a conflict is detected, in order to determine the execution scenario. The control execution module is used to execute the vehicle state control commands defined in the execution scenario.

[0015] Thirdly, the present invention also provides a system comprising a cloud server and a vehicle controller, wherein, Cloud servers are used to store programs, user accounts, and smart scenarios bound to each user account; The vehicle control unit is used to store programs and communicates with the cloud server. The cloud server and / or the vehicle controller execute the stored program to implement the steps in the above-mentioned intelligent scene control method.

[0016] Fourthly, the present invention also provides a computer-readable storage medium for storing a computer-readable program or instructions, which, when executed by a processor, can implement the steps of the intelligent scene control method described in any of the above implementations.

[0017] The beneficial effects of this invention are as follows: The intelligent scene control method provided by this invention effectively filters out the legitimate scenes of the current user by responding to scene triggers and performing user account matching verification, avoiding interference and misexecution of unauthorized scenes; then, it performs conflict detection on the legitimate scenes to identify scene combinations with operational contradictions; based on this, it uses preset hierarchical arbitration rules to adjudicate conflicting scenes, thereby intelligently determining the scene to be executed; finally, it executes the control commands defined by the scene, ensuring that the vehicle status is accurately adjusted according to the user's expectations, which is conducive to improving the security of intelligent scene execution and the accuracy of conforming to the user's intentions. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 A schematic flowchart of an embodiment of the intelligent scene control method provided by the present invention; Figure 2 For the present invention Figure 1 A schematic diagram of an embodiment of S102; Figure 3 For the present invention Figure 1 A schematic diagram of an embodiment of S103; Figure 4 This is a schematic diagram of an embodiment of the intelligent scene control device provided by the present invention. Detailed Implementation

[0020] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0021] In the description of the embodiments of the present invention, unless otherwise stated, "multiple" means two or more. "And / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0022] The terms "first," "second," etc., used in the embodiments of this invention are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a technical feature defined with "first" or "second" may explicitly or implicitly include at least one of that feature.

[0023] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of the invention. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0024] This invention provides an intelligent scene control method, device, system, and storage medium. The technical solutions of the embodiments of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0025] Figure 1 This is a schematic flowchart of an embodiment of the intelligent scene control method provided by the present invention, as shown below. Figure 1 As shown, the intelligent scene control method includes: S101. In response to the triggering of a vehicle's intelligent scene, determine whether the user account to which the triggered intelligent scene belongs matches the vehicle's currently logged-in user account, and obtain the matching result. S102. If the matching result is a match, perform conflict detection on multiple intelligent scenarios triggered by the currently logged-in user account; S103. If a conflict is detected, the multiple intelligent scenarios of the conflict are arbitrated based on the preset hierarchical arbitration rules to determine the execution scenario. S104. Execute the vehicle state control instructions defined in the execution scenario.

[0026] It should be noted that the intelligent scenario in this embodiment refers to a pre-programmed vehicle state control program that can be triggered automatically or manually. Its core lies in integrating the dispersed vehicle function controls into a coherent sequence of operations with a specific objective.

[0027] Specifically, a complete intelligent scenario includes the following elements: Triggering conditions: the logical prerequisites for starting the scenario. These can be set in various ways, for example: Scheduled trigger: such as "12:00 on weekdays"; Vehicle status triggers: such as "vehicle speed is 0 and driver's seatbelt is unfastened"; Environmental conditions trigger the event: such as "in-vehicle temperature > 40℃" or "rainfall detected"; User-initiated activation: Manually started via voice command, physical button, or screen touch; Set of Execution Actions: After a scenario is triggered, the vehicle will execute a series of specific control commands in sequence. These commands correspond to operations on the vehicle's "atomic capabilities," such as "closing the windows to 100%", "adjusting the air conditioning to 25°C with recirculation", "adjusting the driver's seat to zero-gravity mode", and "playing specified white noise," etc. User binding attribute: Each smart scene is uniquely bound to its creator's user account on the cloud server, forming a "My Scenes" list. This attribute is fundamental to resolving cross-user conflicts, ensuring that the scene's execution permissions match the vehicle's currently logged-in user; Parametric and goal-oriented: Actions within a scenario are usually parametric (such as specific temperature values ​​or seat angles) and collectively serve a clear comfort or functional goal (such as "taking a nap", "rapid cooling", or "extreme energy saving").

[0028] For example, a typical "lunch break" smart scenario can be defined as follows: when the vehicle is in P gear and the time is 12 noon on a weekday, automatically (execute actions) close all windows, set the air conditioner to 25°C recirculation, recline the driver's seat to a preset angle, and start playing soothing music to create a suitable cabin environment for rest.

[0029] Specifically, this embodiment provides an intelligent scene control method for performing permission verification, conflict identification, and arbitration execution on multiple concurrently triggered intelligent scenes in a vehicle, including the following steps: First, after the vehicle detects that a certain intelligent scene has been triggered, the user account to which the intelligent scene belongs is obtained and compared with the user account currently logged into the vehicle.

[0030] Each intelligent scenario is submitted to the cloud server by its creator via a user terminal (such as a mobile app) during creation, and is uniquely bound to the creator's user account on the cloud server. When a scenario trigger event occurs, the cloud server or vehicle controller reads the current user's login account and verifies whether it matches the account bound to the triggered scenario. If they match, the intelligent scenario passes the user permission verification and enters the subsequent processing flow; if they do not match, the execution request for the scenario is rejected, filtered, or suspended and not executed.

[0031] If, provided the user verification is successful, there are multiple smart scenarios that have been triggered and belong to the same logged-in user, the system will further perform conflict detection.

[0032] Among them, conflict refers to two or more scenarios issuing mutually exclusive operation commands for the same hardware resource or state target of the vehicle, such as simultaneously requesting to open and close the same window, or setting the air conditioning temperature to different values.

[0033] For a set of scenarios where conflicts are detected, a ruling is made according to the preset hierarchical arbitration rules to determine the unique target scenario that should be executed.

[0034] The pre-defined hierarchical arbitration rules include multiple arbitration levels arranged in descending order of priority, such as the security and regulatory rules layer, the functional logic rules layer, the scenario attribute and user preference rules layer, and the dynamic context arbitration rules layer.

[0035] Arbitration will be attempted layer by layer in the above hierarchical order. Once a clear ruling is reached at a certain level, the subsequent levels of judgment will be terminated, and the scenario to which the ruling points will be determined as the final enforcement scenario.

[0036] Finally, execute all vehicle control commands defined in the winning scenario to complete the state adjustment of the relevant functional modules.

[0037] In a specific example, a user pre-configured a "Commuter Mode" (trigger condition: weekday 08:00; actions: close windows, set air conditioning to 23℃, play news) and a "Rainy Mode" (trigger condition: windshield wipers continuously working; actions: close windows, close sunroof sunshade). At 08:00 on a certain weekday, when the windshield wipers are working, both scenarios are triggered simultaneously. User verification confirms both belong to the currently logged-in user, and conflict detection reveals that both contain the "close windows" instruction, indicating no mutually exclusive operations. However, in the dynamic context arbitration layer, "Rainy Mode" is given higher context priority due to its response to real-time rainfall, and is therefore selected as the execution scenario. Simultaneously, the system can integrate the "play news" operation from "Commuter Mode," which does not conflict with it, to achieve coordinated execution of some instructions.

[0038] This embodiment achieves permission isolation for multi-user scenarios by triggering and executing user account matching verification in response scenarios, avoiding interference and erroneous execution by unauthorized scenarios. It then performs conflict detection on legitimate scenarios, identifying scenario combinations with operational contradictions. Based on this, it uses preset hierarchical arbitration rules to adjudicate conflicting scenarios, intelligently determining the final scenario to be executed. Finally, it executes the control commands defined in that scenario, ensuring that the vehicle status is accurately adjusted according to the user's expectations. By replacing simple time-series or random selection strategies with a structured, hierarchical arbitration mechanism, vehicle status changes are comprehensively optimized in terms of security, functional consistency, and alignment with user intent, improving the reliability of the intelligent scenario system and the user experience.

[0039] In some embodiments of the present invention, such as Figure 2 As shown, step S102 performs conflict detection on multiple intelligent scenarios triggered by the currently logged-in user account, including: S201. The multiple triggered intelligent scenarios are parsed into operation sets of vehicle atomic capability items, where the vehicle atomic capability item is the smallest operation unit that independently controls the vehicle's functions. S202. Compare each set of operations with a pre-built capability item relation library, which defines the mutual exclusion relationship between vehicle atomic capability items; S203. If there are two smart scenarios whose operation sets contain mutually exclusive atomic capability operations, then a conflict is detected.

[0040] This embodiment describes the specific implementation of conflict detection in step S102.

[0041] After user verification is successful, if multiple triggered smart scenarios belong to the currently logged-in user, the system performs conflict detection, which includes the following steps: First, each triggered intelligent scenario is parsed into a set of operations for a group of vehicle atomic capability items.

[0042] Among them, the vehicle atomic capability item refers to the smallest functional unit in the vehicle that can be independently controlled, which is uniquely determined by the object being operated on and the operating instructions.

[0043] For example, atomic capability items may include: {Air conditioning switch: On}, {Air conditioning temperature: Set to 25℃}, {Driver's window: Open to 50%}, {Door lock: Lock}, {Seat heating (Driver's seat): On to level 3}, etc. This parsing process converts high-level semantic scene definitions (such as "lunch break mode" or "pet care") into standardized sequences of low-level control commands, facilitating subsequent logic comparison.

[0044] Secondly, the set of atomic capability items corresponding to each scenario is compared with a pre-built capability item relationship database. This database stores predefined logical relationships between different atomic capability items, with mutual exclusion relationships being particularly important. Mutual exclusion relationships are used to identify that two or more atomic capability items cannot logically be effective simultaneously, specifically including: The opposite operation for the same object, such as {window (driver's side): close} and {window (driver's side): open to any degree}; Functional modes are mutually exclusive, such as {Air Circulation Mode: Internal Circulation} and {Air Circulation Mode: External Circulation}; Implicit mutual exclusion based on system design or user experience constraints, such as {Air conditioning mode: Cooling} and {Seat heating (driver's seat): On} (defined as mutually exclusive under specific models or configurations).

[0045] The aforementioned mutually exclusive relationships are stored in the relation database as rule entries, supporting exact matching or semantically based extended matching.

[0046] During the comparison process, if the operation sets of any two scenarios contain at least one pair of atomic capability items marked as mutually exclusive by the relational database, the system determines that there is a conflict between the two scenarios. For example, the "Comfortable Homecoming" scenario contains the atomic capability items {Window: Closed} and {Air Conditioning: Heating}, while the "Quick Ventilation" scenario contains {Window: Open 50%} and {Air Conditioning: Off}. After parsing and querying the relational database, {Window: Closed} and {Window: Open 50%} are identified as mutually exclusive operations, therefore the system determines that there is a conflict between the two scenarios.

[0047] Through the above mechanism, this embodiment achieves structured identification of contradictions in underlying control commands under concurrent triggering scenarios. By using atomized decomposition and relational database-driven comparison, the conflict detection achieves standardization, scalability, and logical rigor, providing accurate and readable conflict information input for the subsequent arbitration stage, thereby improving the reliability of the intelligent scene control system and the accuracy of automated decision-making under complex operating conditions.

[0048] In some embodiments of the present invention, after determining whether the user account to which the triggered intelligent scene belongs matches the currently logged-in user account of the vehicle, and obtaining the matching result, the intelligent scene control method includes: If the matching result is a mismatch, the subsequent conflict detection and arbitration process for that smart scenario will be terminated, and a blocking or suspension operation will be performed for that smart scenario.

[0049] In some embodiments of the present invention, the step of determining whether the user account to which the triggered smart scene belongs matches the currently logged-in user account of the vehicle is performed on a cloud server, and the smart scene and the user account that created the smart scene are bound and stored on the cloud server.

[0050] This embodiment specifically describes the handling mechanism when the user account belonging to the intelligent scenario is inconsistent with the user account currently logged into the vehicle, and the specific implementation of the user matching judgment.

[0051] When a vehicle detects that a smart scene has been triggered, it sends the scene's identification information to the cloud server. The cloud server stores the binding relationship between each smart scene and its creator's user account. Specifically, in the database, each smart scene record contains a field that associates it with its unique user account identifier (e.g., Scene ID: "Scene_123", corresponding to user "User_P"). This binding relationship is submitted by the user terminal (such as a mobile app) or the vehicle's infotainment system when the scene is created and is persistently stored by the cloud server, constituting the basis for scene ownership.

[0052] After receiving a scenario trigger request, the cloud server retrieves the currently logged-in user account of the vehicle (e.g., "User_C") and compares it with the account associated with the triggered smart scenario. If the two do not match, the user is deemed to be mismatched.

[0053] In the event of a user mismatch, the subsequent processing flow for that scenario, including conflict detection, arbitration decision-making, and vehicle control command generation, will be terminated, and a preset interception operation will be executed.

[0054] Interception operations include, but are not limited to, blocking and suspending. Blocking means directly discarding the execution request of the intelligent scenario without issuing any related instructions to the vehicle controller; suspending means temporarily storing the request in a waiting queue, logging it but not triggering a change in vehicle status, and not automatically resuming execution without further authorization.

[0055] The interception logic can be completed by the cloud server before the instruction is issued, or it can be executed by the vehicle controller based on the verification result returned by the cloud.

[0056] In a specific example, User A (username User_P) created a smart scenario called "High-Speed ​​Cruise" for their family-shared vehicle and shared this scenario configuration with User B (username User_C) through the application platform. When User B uses the vehicle alone and logs into the vehicle's infotainment system using their own account User_C, if the vehicle's operating status meets the trigger conditions for "High-Speed ​​Cruise," a trigger request is uploaded to the cloud. The cloud query reveals that the scenario is bound to the account User_P, which does not match the currently logged-in account User_C. Therefore, it refuses to issue the execution command, and the vehicle's controller will not perform operations such as closing the windows, adjusting the air conditioning, or playing news.

[0057] This embodiment implements user-identity-based scene execution permission control. By moving permission verification to the initial stage of the process, it effectively prevents accidental triggering or unauthorized execution of scenes created by non-current users. Simultaneously, by centrally managing the binding relationship between intelligent scenes and accounts in the cloud, it ensures data consistency and security while reducing the storage and computing burden on the vehicle. This enables clear definition of control permission boundaries in multi-user shared vehicle application scenarios, improving the reliability of intelligent scene execution and user isolation.

[0058] In some embodiments of the present invention, such as Figure 3 As shown, step S103 arbitrates multiple conflicting smart scenarios based on preset hierarchical arbitration rules, including performing at least one of the following adjudication operations in priority order: S301. Make a first-priority decision based on safety and regulatory rules; S302. If the conflict cannot be resolved by the preceding decision, a second priority decision shall be made based on the predefined mutual exclusion or dependency relationship between vehicle atomic capability items. S303. If the conflict cannot be resolved by the preceding rulings, a third-priority ruling shall be made based on the scenario attributes and user preferences. S304. If the conflict cannot be resolved by the preceding rulings, a fourth priority ruling shall be made based on real-time vehicle data or environmental data.

[0059] In a preferred embodiment, the hierarchical arbitration rules include multiple arbitration levels arranged in descending order of priority. The first priority arbitration level is the security and regulatory rules level, the second priority arbitration level is the functional logic rules level, the third priority arbitration level is the scenario attribute and user preference rules level, and the fourth priority arbitration level is the dynamic context arbitration rules level.

[0060] Among them, the safety and regulatory rules layer prioritizes operations involving driving safety or legal compliance, such as prohibiting unlocking car doors while driving; Among them, the functional logic rule layer makes judgments based on the inherent logical relationships between vehicle functions (such as mutual exclusion, dependency, and overriding), for example, the sunroof should be kept closed when the windshield wipers are working; Among them, the scene attributes and user preference rules layer are static attributes such as the preset weights of the scene, the triggering method (timed / event-driven), and the user-defined priority; Among them, the dynamic context arbitration rule layer combines real-time vehicle status data (such as vehicle speed, ambient temperature, and windshield wiper working status) and external environmental information to make context-aware judgments.

[0061] Specifically, after detecting multiple intelligent scenarios that have passed user verification and have operational conflicts, the rules at each level are tried in turn to make a decision. Once a unique executable scenario is found at a certain level, the subsequent level judgments are terminated and the scenario is executed.

[0062] The first arbitration level is the safety and regulatory rules level, which contains pre-defined mandatory binding rules and has the highest priority.

[0063] For example, if the vehicle's current speed is greater than 5 km / h, any scenario involving "unlocking doors" or "fully opening windows" is prohibited; or, under certain driving conditions, activating multiple entertainment functions that may distract the driver simultaneously is prohibited. If a conflict scenario violates these rules, the relevant scenario is directly excluded, and the compliant vehicle is retained as a candidate.

[0064] If the first level cannot make a decision (i.e., all conflict scenarios meet safety and regulatory requirements), the second arbitration level—the functional logic rule level—is invoked. This level makes judgments based on predefined mutual exclusion or dependency relationships between vehicle atomic capability items.

[0065] For example, if the operation set of scenario A includes "fragrance system: turn on", and this function depends on "air conditioner switch: turn on"; while scenario B includes "air conditioner switch: turn off", then according to the logic of "dependencies must be satisfied", the system can prioritize retaining scenario A, or adjust the execution order to ensure that its dependency conditions are met.

[0066] If the first two layers still cannot determine a unique execution scenario, the system proceeds to the third arbitration layer—the scenario attribute and user preference rule layer. This layer introduces static configuration information for decision-making, including but not limited to: the system's preset weights for each scenario (e.g., "driving safety" scenarios have a higher weight than "comfort and convenience" scenarios); the priority of triggering methods (e.g., scenarios actively triggered by the user via voice or manual button take precedence over scenarios triggered automatically by timed events or events); and user-defined custom priority rules in the settings interface (e.g., "pet mode > nap mode"). The system sorts or filters conflicting scenarios based on these attributes.

[0067] If the above three levels fail to reach a clear resolution, the fourth arbitration level—the dynamic context arbitration level—is activated. This level makes context-aware judgments based on real-time collected vehicle status data or environmental sensor data.

[0068] For example, when a conflict arises between the "powerful cooling" and "ultimate energy saving" scenarios, the system reads the current in-vehicle temperature sensor readings: if the measured temperature is above 30°C, powerful cooling is prioritized; if the temperature is within a comfortable range (e.g., 22–26°C), energy saving mode is preferred. Other available contexts include light intensity, wiper status, battery level, and ambient temperature.

[0069] Through the above-mentioned four-level progressive arbitration mechanism, this embodiment achieves structured and intelligent processing of conflicts in multiple scenarios, ensuring that the arbitration result first meets the rigid constraints of safety and regulations, secondly follows the inherent logic of vehicle functions, then combines the user's long-term configuration preferences, and finally adapts to the real-time operating environment, thereby providing reasonable, reliable and user-expected execution decisions in complex concurrent scenarios.

[0070] In some embodiments of the present invention, a second priority decision is made based on predefined mutual exclusion or dependency relationships between vehicle capability items, including: When the operation of the first intelligent scenario depends on a vehicle atomic capability operation, and the operation of the second intelligent scenario is mutually exclusive with that vehicle capability operation, the decision prioritizes ensuring the execution of the first intelligent scenario or the necessary pre-operation.

[0071] Specifically, the second priority adjudication mainly uses two types of logical relationships (dependency and mutual exclusion) predefined in the capability item relationship library to analyze and adjudicate the set of operations in the conflict scenario.

[0072] In this context, dependency means that the effectiveness of one atomic capability operation is contingent upon the execution of another atomic capability operation.

[0073] For example, "Air purifier: On" depends on "Air conditioner switch: On", because the former needs the airflow generated by the air conditioner fan to achieve air circulation and purification functions.

[0074] Mutual exclusion refers to the fact that two atomic capability operations cannot be performed simultaneously on the same controlled object or state. For example, "Window (driver's side): Open to 50%" and "Window (driver's side): Close completely" are mutually exclusive.

[0075] During the adjudication process, if the system identifies that an operation in the first intelligent scenario depends on a specific atomic capability item A, and the operation set of the second intelligent scenario contains an atomic capability item B that is mutually exclusive with A, then according to the rules of this embodiment, priority is given to ensuring that the dependency condition of the first intelligent scenario is met.

[0076] Specifically, the system will retain or execute atomic capability item A and exclude or adjust conflicting operation B, thereby maintaining the integrity of the functional logic chain.

[0077] In a specific example: A user simultaneously triggers both the "Air Purification" scenario (the operation set includes: {Air Conditioner Switch: On}, {Air Purifier: On}, {Air Circulation Mode: Recirculation}) and the "Power Off for Energy Saving" scenario (the operation set includes: {Air Conditioner Switch: Off}, {Non-essential Appliances: Off}). In the second priority decision, the system recognizes that "Air Purifier: On" depends on "Air Conditioner Switch: On", while the "Power Off for Energy Saving" scenario contains the mutually exclusive "Air Conditioner Switch: Off". Based on the preset dependency priority rule, the system decides to maintain the "Air Conditioner Switch: On" state to ensure the effective execution of the air purification function, thereby avoiding the logical contradiction or functional failure of the purifier starting but with no airflow.

[0078] This embodiment accurately identifies deep logical conflicts caused by inter-operation dependencies and mutual exclusions, and makes decisions based on the inherent operating principles of the vehicle system. This effectively prevents ineffective control, resource waste, or system anomalies caused by instruction combinations violating functional constraints, and improves the consistency of intelligent scene execution functions.

[0079] In some embodiments of the present invention, a third priority decision is made based on scenario attributes and user preferences, including at least one of the following: The decision is made based on the basic weights corresponding to the type of intelligent scenario. The decision is made based on the priority of the trigger source of the intelligent scene. Among them, the priority of in-vehicle voice or physical button trigger is higher than the vehicle screen touch trigger, the vehicle screen touch trigger is higher than the mobile application remote trigger, and the mobile application remote trigger is higher than the automatic condition trigger. The adjudication is based on user-defined conflict resolution rules.

[0080] Specifically, in the tiered arbitration process, when a conflict scenario has passed through the first priority (security and regulatory rules layer) and the second priority (functional logic rules layer) but still has not reached a single execution decision, it proceeds to the third priority adjudication, namely the rules layer based on scenario attributes and user preferences. This level adjudicates through the following three parallel and superimposed judgment dimensions: First, the comparison is made based on the basic weights corresponding to the types of intelligent scenarios.

[0081] During the initialization or configuration phase, the system presets numerical weight labels for different categories of scenarios to characterize their relative importance.

[0082] For example, "safety and comfort" scenarios (such as "high temperature protection" and "child lock activation") are given high weight; "exclusive function" scenarios (such as "rest mode" and "pet care mode") are given medium weight; and "convenience and entertainment" scenarios (such as "music and ambient lighting linkage") are given low weight. When two conflicting scenarios have different weights, the system prioritizes the scenario with the higher weight as the execution target.

[0083] Second, the system determines the priority based on the trigger source type of the intelligent scenario. Different triggering methods reflect the clarity and immediacy of the user's intent. The system's preset trigger source priority order is as follows: in-vehicle voice command or physical button trigger (highest priority) > vehicle touchscreen manual trigger > mobile application remote trigger > automatic conditional trigger based on time, location, or sensor data (lowest priority). If the trigger sources of conflicting scenarios belong to different priority categories, the scenario with the higher trigger source priority will be executed first.

[0084] Third, the system makes decisions based on user-defined conflict rules. These rules allow users to specify execution priorities for particular scenarios within the system settings interface.

[0085] For example, a configuration rule could be set such that when both "Pet Mode" and "Nap Mode" are triggered simultaneously, "Pet Mode" is always executed. Such rules are stored in the user configuration file as key-value pairs or policy tables and are directly invoked during arbitration.

[0086] The above three dimensions can be used individually or in combination to evaluate the information in each dimension sequentially or comprehensively, and generate the final ruling result.

[0087] This embodiment introduces a configurable subjective judgment dimension into the arbitration logic, so that conflict resolution is not only based on objective constraints, but also reflects the user's long-term preferences and real-time interaction intentions, thereby improving the personalized adaptation capability and user experience consistency of the intelligent scene control system in multi-user and multi-scenario environments.

[0088] This embodiment effectively filters out the current user's legitimate scenarios by triggering and executing user account matching verification in response to scenarios, avoiding interference and erroneous execution by unauthorized scenarios. It then performs conflict detection on the legitimate scenarios, identifying scenario combinations with operational contradictions. Based on this, it uses preset hierarchical arbitration rules to adjudicate conflicting scenarios, intelligently determining the final scenario to be executed. Finally, it executes the control commands defined in that scenario, ensuring that the vehicle status is accurately adjusted according to the user's expectations. This improves the security of intelligent scenario execution and the accuracy of conforming to user intent.

[0089] To better implement the intelligent scene control method in the embodiments of the present invention, based on the intelligent scene control method, correspondingly, such as Figure 4As shown, this embodiment of the invention also provides an intelligent scene control device, the intelligent scene control device 400 including: The account matching module 401 is used to determine whether the user account to which the triggered intelligent scene belongs matches the currently logged-in user account of the vehicle in response to the intelligent scene of the vehicle being triggered, and to obtain the matching result. The conflict detection module 402 is used to perform conflict detection on multiple intelligent scenarios triggered by the currently logged-in user account if the matching result is a match. The conflict arbitration module 403 is used to arbitrate multiple intelligent scenarios of the conflict based on preset hierarchical arbitration rules if a conflict is detected, so as to determine the execution scenario. The control execution module 404 is used to execute the vehicle state control instructions defined in the execution scenario.

[0090] The intelligent scene control device 400 provided in the above embodiments can implement the technical solutions described in the above intelligent scene control method embodiments. The specific implementation principles of each module or unit can be found in the corresponding content in the above intelligent scene control method embodiments, and will not be repeated here.

[0091] Accordingly, embodiments of this application also provide an intelligent scene control system, including a cloud server and a vehicle controller, wherein, Cloud servers are used to store programs, user accounts, and smart scenarios bound to each user account; The vehicle control unit is used to store programs and communicates with the cloud server. The cloud server and / or the vehicle controller execute the stored program to implement the steps or functions in the above-mentioned intelligent scene control method.

[0092] Accordingly, this application also provides a computer-readable storage medium for storing computer-readable programs or instructions. When the programs or instructions are executed by a processor, they can implement the steps or functions of the intelligent scene control methods provided in the above-described method embodiments.

[0093] Those skilled in the art will understand that all or part of the processes of the methods described in the above embodiments can be implemented by a computer program instructing related hardware (such as a processor, controller, etc.), and the computer program can be stored in a computer-readable storage medium. The computer-readable storage medium may be a disk, optical disk, read-only memory, or random access memory, etc.

[0094] The intelligent scene control method, device, system, and storage medium provided by the present invention have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. An intelligent scene control method, characterized in that, include: In response to the triggering of a smart scene in the vehicle, it is determined whether the user account to which the triggered smart scene belongs matches the currently logged-in user account of the vehicle, and a matching result is obtained; If the matching result is a match, conflict detection is performed on multiple intelligent scenarios triggered by the currently logged-in user account; If a conflict is detected, the multiple intelligent scenarios of the conflict are arbitrated based on the preset hierarchical arbitration rules to determine the execution scenario. Execute the vehicle state control commands defined in the execution scenario.

2. The intelligent scene control method according to claim 1, characterized in that, The conflict detection of multiple intelligent scenarios triggered by the currently logged-in user account includes: Multiple triggered intelligent scenarios are parsed into a set of operations for vehicle atomic capability items, where the vehicle atomic capability item is the smallest operational unit that independently controls the vehicle's functions. Each of the operation sets is compared with a pre-built capability item relation library, which defines the mutual exclusion relationships between vehicle atomic capability items; If two smart scenarios have operation sets containing mutually exclusive atomic capability operations, then a conflict is detected.

3. The intelligent scene control method according to claim 1, characterized in that, After determining whether the user account to which the triggered intelligent scene belongs matches the currently logged-in user account of the vehicle, and obtaining the matching result, the intelligent scene control method includes: If the matching result is a mismatch, the subsequent conflict detection and arbitration process for the intelligent scenario will be terminated, and a blocking or suspension operation will be performed for the intelligent scenario.

4. The intelligent scene control method according to claim 3, characterized in that, The step of determining whether the user account to which the triggered smart scene belongs matches the currently logged-in user account of the vehicle is executed on the cloud server, and the smart scene and the user account that created the smart scene are bound and stored on the cloud server.

5. The intelligent scene control method according to any one of claims 1 to 4, characterized in that, The arbitration based on preset hierarchical arbitration rules arbitrates multiple intelligent scenarios of conflict, including performing at least one of the following adjudication operations in priority order: The decision is made based on the highest priority of safety and regulatory rules. If the conflict cannot be resolved by the preceding ruling, a second priority ruling will be made based on the predefined mutual exclusion or dependency relationship between vehicle atomic capability items; If the conflict cannot be resolved by the preceding rulings, a third-priority ruling will be made based on the scenario attributes and user preferences. If the conflict cannot be resolved by the preceding rulings, a fourth priority ruling will be made based on real-time vehicle data or environmental data.

6. The intelligent scene control method according to claim 5, characterized in that, The second priority decision based on the predefined mutual exclusion or dependency relationships between vehicle capability items includes: When the operation of the first intelligent scenario depends on a vehicle atomic capability operation, and the operation of the second intelligent scenario is mutually exclusive with that vehicle capability operation, the decision prioritizes ensuring the execution of the first intelligent scenario or the necessary pre-operation.

7. The intelligent scene control method according to claim 5, characterized in that, The third priority decision based on scenario attributes and user preferences includes at least one of the following: The decision is made based on the basic weights corresponding to the type of intelligent scenario. The decision is made based on the priority of the trigger source of the intelligent scene. Among them, the priority of in-vehicle voice or physical button trigger is higher than the vehicle screen touch trigger, the vehicle screen touch trigger is higher than the mobile application remote trigger, and the mobile application remote trigger is higher than the automatic condition trigger. The adjudication is based on user-defined conflict resolution rules.

8. An intelligent scene control device, characterized in that, include: The account matching module is used to determine whether the user account to which the triggered intelligent scene belongs matches the currently logged-in user account of the vehicle in response to the intelligent scene being triggered, and to obtain the matching result. The conflict detection module is used to perform conflict detection on multiple intelligent scenarios triggered by the currently logged-in user account if the matching result is a match. The conflict arbitration module is used to arbitrate multiple intelligent scenarios of the conflict based on preset hierarchical arbitration rules if a conflict is detected, in order to determine the execution scenario. The control execution module is used to execute the vehicle state control commands defined in the execution scenario.

9. An intelligent scene control system, characterized in that, This includes cloud servers and vehicle controllers, among which, Cloud servers are used to store programs, user accounts, and smart scenarios bound to each user account; The vehicle control unit is used to store programs and communicates with the cloud server. The cloud server and / or the vehicle controller executes the stored program to implement the steps in the intelligent scene control method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, Used to store computer-readable programs or instructions, which, when executed by a processor, can implement the steps in the intelligent scene control method according to any one of claims 1 to 7.

Images